850b982f2a
The handling of BVI is awkward, with the autoderived interface name "bviXX" based on the bridgedomain bd_id. Lots of special casing happens on account of this decision, and to make matters worse there is poor interaction (leading to VPP crashes) when BVIs and Loopbacks are used at the same time: https://lists.fd.io/g/vpp-dev/message/21116 This is step one of a refactor of the logic. In this commit, I'm removing all of the BVI logic from the codebase, rendering bridgedomains unable to have IP interfaces. In the next commit, I will introduce new behavior in the schema, allowing for 'bvi' to be a loopback interfacename which will be used as BVI for a bridgedomain, restoring the ability to use bridgedomains with IP interfaces (using a loop).
54 lines
1.1 KiB
YAML
54 lines
1.1 KiB
YAML
bondethernets:
|
|
BondEthernet0:
|
|
interfaces: [ GigabitEthernet3/0/0, GigabitEthernet3/0/1 ]
|
|
|
|
interfaces:
|
|
GigabitEthernet1/0/0:
|
|
mtu: 3000
|
|
GigabitEthernet1/0/1:
|
|
mtu: 3000
|
|
|
|
GigabitEthernet2/0/0:
|
|
mtu: 9000
|
|
sub-interfaces:
|
|
100:
|
|
mtu: 2000
|
|
GigabitEthernet2/0/1:
|
|
mtu: 9000
|
|
sub-interfaces:
|
|
100:
|
|
mtu: 2000
|
|
|
|
GigabitEthernet3/0/0:
|
|
mtu: 9000
|
|
sub-interfaces:
|
|
100:
|
|
description: "Also not in a bridgedomain"
|
|
GigabitEthernet3/0/1:
|
|
mtu: 9000
|
|
|
|
GigabitEthernet4/0/0:
|
|
mtu: 9000
|
|
GigabitEthernet4/0/1:
|
|
mtu: 9000
|
|
|
|
BondEthernet0:
|
|
mtu: 3000
|
|
sub-interfaces:
|
|
100:
|
|
mtu: 2000
|
|
|
|
bridgedomains:
|
|
bd10:
|
|
description: "Bridge Domain 10"
|
|
mtu: 3000
|
|
interfaces: [ GigabitEthernet1/0/0, GigabitEthernet1/0/1, BondEthernet0 ]
|
|
bd11:
|
|
description: "Bridge Domain 11, with sub-interfaces"
|
|
mtu: 2000
|
|
interfaces: [ GigabitEthernet2/0/0.100, GigabitEthernet2/0/1.100, BondEthernet0.100 ]
|
|
bd12:
|
|
description: "Bridge Domain 12, invalid because it has Gi1/0/0 as well"
|
|
mtu: 9000
|
|
interfaces: [ GigabitEthernet4/0/0, GigabitEthernet1/0/0 ]
|