By default, the NetQ CLI is not configured during the NetQ installation. The configuration is stored in /etc/netq/netq.yml.
While the CLI is not configured, you can run only netq config commandsand netq help commands, and you must use sudo to run them.
At minimum, you need to configure the NetQ CLI and NetQ Agent to communicate with the telemetry server. To do so, configure the NetQ Agent and the NetQ CLI so that they are running in the VRF where the routing tables are set for connectivity to the telemetry server. Typically this is the management VRF.
To configure the NetQ CLI, run the following command, then restart the NetQ CLI. This example assumes the telemetry server is reachable via the IP address 10.0.1.1 over port 32000 and the management VRF (mgmt).
{{- if eq (.Get "opsys") "cl" -}}cumulus@switch:~$ sudo netq config add cli server 10.0.1.1 vrf mgmt port 32000 cumulus@switch:~$ sudo netq config restart cli{{ end }} {{- if eq (.Get "opsys") "ub" -}}
root@host:~# sudo netq config add cli server 10.0.1.1 vrf mgmt port 32000 root@host:~# sudo netq config restart cli{{ end }} {{- if eq (.Get "opsys") "rh" -}}
root@host:~# sudo netq config add cli server 10.0.1.1 vrf mgmt port 32000 root@host:~# sudo netq config restart cli{{ end }}
Restarting the CLI stops the current running instance of netqd and starts netqd in the specified VRF.
To configure the NetQ Agent, read the {{- if eq (.Get "opsys") "cl" -}} Configure Advanced NetQ Agent Settings {{ end }} {{- if eq (.Get "opsys") "ub" -}} Configure Advanced NetQ Agent Settings {{ end }} {{- if eq (.Get "opsys") "rh" -}} Configure Advanced NetQ Agent Settings {{ end }} topic.