...
Both lines match in the source, but the description Management Loopback line appears between them. Strict mode requires the matching lines to be consecutive, so the condition fails.
Choosing the right Match mode
...
Requirement
...
Recommended match mode
...
Required lines can appear anywhere and in any order
...
Loose
...
Required lines must appear in a specific order, but may have other lines between them
...
Sequential
...
Required lines must appear in a specific order with no lines between them
...
Strict
Common use cases:
The following are some example scenarios where each match mode is particularly useful:
| Use case | Match mode | Rationale |
|---|---|---|
| Baseline configuration - NTP, DNS, syslog, ... Security hardening - telnet disabled, HTTP disabled, ... | Loose | The required lines are independent of each other and may appear in different parts of the configuration. Only their presence matters. |
| Firewall and ACL rules, route-maps | Sequential | The required lines must appear in a specific order, while other configuration lines may appear between them. |
| Multiline MOTD banner, interface configuration | Strict | The required lines form a specific configuration block and must appear consecutively without any other lines between them. |