If you are using the current version of Cumulus NetQ, the content on this page may not be up to date. The current version of the documentation is available here. If you are redirected to the main page of the user guide, then this page may have been renamed; please search for it there.

Validation Checks

NetQ periodically runs default validations to verify whether devices, hosts, network protocols, and services are operating as expected. These validations measure what NetQ expects from a healthy network against the data it receives from the network it is monitoring. When NetQ detects an anomaly or inconsistency, the system will broadcast an event.

NetQ excludes certain checks from running by default. You can run an on-demand validation or schedule a validation to view validation results for those protocols and services.

The following table displays the validation categories. Refer to the Validation Reference for a comprehensive breakdown of each test included in each category.

Item NetQ UI NetQ CLI Run by Default Frequency
Addresses Yes Yes No on-demand, as scheduled
Agents Yes Yes Yes 60 mins
BGP Yes Yes Yes 60 mins
Cumulus Linux version No Yes No on-demand, as scheduled
EVPN Yes Yes Yes 60 mins
Interfaces Yes Yes Yes 60 mins
MLAG (CLAG) Yes Yes Yes 60 mins
MTU Yes Yes Yes 60 mins
NTP Yes Yes Yes 60 mins
OSPF Yes Yes Yes 60 mins
RoCE Yes Yes No on-demand, as scheduled
Sensors Yes Yes Yes 60 mins
Topology (beta) Yes Yes No on-demand
VLAN Yes Yes Yes 60 mins
VXLAN Yes Yes Yes 60 mins

After logging in, it can take up to an hour for NetQ to display accurate validation data.

View and Run Validations in the UI

The Validation Summary card displays the results from the subset of hourly validation checks that NetQ runs by default. Select Validation in the header to create or schedule new validation checks, as well as view previous checks.

Validation with the NetQ CLI

The NetQ CLI uses the netq check commands to validate the various elements of your network fabric, looking for inconsistencies in configurations across your fabric, connectivity faults, missing configurations, and so forth. You can run commands from any node in the network.