...
The line description WAN does not exist in the source.
Source matches regex
The following examples demonstrate how Loose mode evaluates input lines when using the Source matches regex condition type treats each input line as a separate regular expression. Loose mode requires each regex to match somewhere in the source, but the matches can occur in any order.
Condition 3:
| Code Block | ||
|---|---|---|
| ||
router ospf hostname R[0-9]+ |
...
The following examples demonstrate how Sequential mode evaluates input lines when using the Source contains condition type.
Condition 5:
| Code Block | ||
|---|---|---|
| ||
interface Ethernet1 ip address 10.0.0.1/24 |
...
The input lines appear in the source in reverse order.
Source matches regex
When using Source matches regex, each input line is treated as a separate regular expression. Sequential mode requires the regexes to match lines in the specified order, but additional lines may appear between the matchesThe following examples demonstrate how Sequential mode evaluates input lines when using the Source matches regex condition type.
Condition 7:
| Code Block | ||
|---|---|---|
| ||
router ospf network [0-9]+\.[0-9]+\.[0-9]+\.[0-9]+/([0-9]+) area [0-9]+ |
...
The source contains the line "description Uplink" between the two input lines. Strict mode therefore fails.
Source matches regex
When using The following examples demonstrate how Strict mode evaluates input lines when using the Source matches regex, each input line is treated as a separate regular expression. Strict mode requires the regexes to match consecutive lines in the specified order. condition type.
Condition 11:
| Code Block | ||
|---|---|---|
| ||
interface Loopback[0-9]+ description Management Loopback ip address 10\.255\.255\.[0-9]+ 255\.255\.255\.255 |
...