...
| Code Block | ||
|---|---|---|
| ||
hostname R1 ! interface Ethernet1 description Uplink ip address 10.0.0.1/24 no shutdown ! interface Ethernet2 description LAN ip address 192.168.1.1/24 no shutdown ! interface Loopback0 description Management Loopback ip address 10.255.255.1 255.255.255.255 ! router ospf router-id 1.1.1.1 network 10.0.0.0/24 area 0 ! |
Note: The Compliance engine can validate MCP automation outputs in addition to device configurations. To validate an automation output, select Source → Mass Config Push Result. The same condition types and matching principles described in this article apply when evaluating automation output.
Suppose the Condition type is "Source contains" and the Condition input is:
| Code Block | ||
|---|---|---|
| ||
interface Ethernet1
ip address 10.0.0.1/24 |
The table below shows the Condition evaluation status for each match mode using the example source and Condition input:
...
Match mode
...
Condition Status
...
Explanation
...
Loose
...
Successful
...
Both lines exist in the source.
...
Sequential
...
Successful
...
The lines appear in the correct order.
...
Strict
...
Failed
...
The "description Uplink" line appears between them.
...
Text matching condition types:
Loose Mode
Loose mode verifies that all input lines exist somewhere in the source. Their order is ignored, and any content may appear between matching lines in the source.
...
Sequential mode requires all input lines to appear in the source in the same order as entered. Other Additional text/lines may appear between them.
...
Result: Condition successful
The two Both input lines appear in the source in the correct order. The "description Uplink" line between them is ignored.
...
Strict Mode
Strict mode requires the input lines to appear consecutively in the source. No additional text/lines may exist between the matching lines in the source.
...
Result: Condition successful
These All three lines appear consecutively in the source.
Example Input 2:
| Code Block | ||
|---|---|---|
| ||
interface Ethernet1 ip address 10.0.0.1/24 |
...
The source contains the line "description Uplink" between the two input lines. Strict mode therefore fails.
Regex matching condition types:
The same three match modes apply when using regex matching condition types. Each regular expression in the input is evaluated against lines in the source, and the match mode governs whether the matches must occur in order and whether intervening unmatched lines are permitted.
Loose Mode
| Code Block | ||
|---|---|---|
| ||
(?m)^router ospf$
(?m)^hostname R[0-9]+$ |
This verifies that the device follows the R<number> hostname convention and has OSPF enabled. The two matches are independent, so their order does not matter.
Sequential Mode
| Code Block | ||
|---|---|---|
| ||
(?m)^router ospf$
(?m)^ network [0-9]+\.[0-9]+\.[0-9]+\.[0-9]+/([0-9]+) area [0-9]+$ |
This verifies that an OSPF configuration section is followed by an OSPF network statement. Other OSPF configuration, such as a router-id, may appear between the matches.
Strict Mode
| Code Block | ||
|---|---|---|
| ||
(?m)^interface Loopback[0-9]+$
(?m)^ description Management Loopback$
(?m)^ ip address 10\.255\.255\.[0-9]+ 255\.255\.255\.255$ |
This verifies that a Loopback interface with a variable interface number has the required "Management Loopback" description and uses a /32 address from the 10.255.255.0/24 management subnet.
Choosing the Right Match Mode
Use case | Recommended mode |
|---|---|
Verify several independent configuration lines exist in the source | Loose |
Verify the presence and order of configuration commands in the source | Sequential |
Verify an exact the presence of a configuration block | Strict |