Relax the LCP requirements - it is OK to have an address without an LCP

This commit is contained in:
Pim van Pelt
2022-04-03 09:04:11 +00:00
parent f786a00e9a
commit d30f2d8965
3 changed files with 1 additions and 28 deletions

View File

@ -2,12 +2,10 @@ test:
description: "Interfaces put into the bridge, can't be L3 (so cannot have an address)"
errors:
expected:
- "interface .* has an address but no LCP"
- "sub-interface .* has an address but .* does not have an LCP"
- "bridgedomain .* member .* has an address"
- "interface .* is in L2 mode but has an address"
- "sub-interface .* is in L2 mode but has an address"
count: 9
count: 6
---
interfaces:
GigabitEthernet1/0/0:

View File

@ -1,18 +0,0 @@
test:
description: "Sub-interface with addresses must have an LCP. Gi1/0/0 does this wrong, while Gi2/0/0 does it correctly"
errors:
expected:
- "sub-interface .* has an address but .* does not have an LCP"
count: 1
---
interfaces:
GigabitEthernet1/0/0:
sub-interfaces:
100:
addresses: [ 192.0.2.1/24 ]
GigabitEthernet2/0/0:
lcp: "xe2-0-0"
sub-interfaces:
100:
addresses: [ 192.168.1.1/24 ]