When you add diagnosis to a Network Intent, you can define a variety of diagnosis logic to make the NI more flexible and verify the network design more accurately.

Table/Paragraph/Collector Variable

A variable can be a single variable such as $state or a table (paragraph, collector) variable. For the table/paragraph/collector variable, you can select the Loop Table Rows for the system to loop through each table's row. Take the OSPF neighbor table as an example. There are seven lines of neighbor information in the CLI result (the blue rows on the left). The diagnosis execution will determine whether the state contains full line by line (7 lines in total).

Different Variable Types

Different types of variables have various operations such as Equals, Does not equal, Contains, etc. Compound variables and compound tables can be used in diagnosis definition as well.

Different Data Source

For each variable defined in diagnosis, you can select its data sources:

▪Current: retrieved from the live data.

▪Baseline: the baseline data.

▪Last: the system will retrieve the data twice and compare the current data with the last data.

The following diagnosis compares the current state with the baseline state:

The following diagnosis compares the current CRC value with the last CRC value:

Check Device Pair

You can compare the variables from the different devices. The following compares MTU from two neighbor devices.

Use Compound Condition

You can have multiple simple conditions and combine them to a Boolean expression (and/or).