// lag1 connects LEAF2A to server-3
and is associated to an all-active Ethernet Segment.
--{ candidate shared default }--[ ]--
A:LEAF2A# info interface lag*
interface lag1 {
admin-state enable
vlan-tagging true
subinterface 10 {
type bridged
vlan {
encap {
single-tagged {
vlan-id 10
}
}
}
}
lag {
lag-type static
// lag-type could also be lacp, in which case the
system-id/key must match on lag1 of LEAF2B
member-speed 10G
}
}
// lag2 connects LEAF2A to LEAF3A and LEAF3B.
This LAG is an access LAG (does not carry vxlan) associated to
an all-active Ethernet Segment
interface lag2 {
admin-state enable
vlan-tagging true
subinterface 10 {
type bridged
vlan {
encap {
single-tagged {
vlan-id 10
}
}
}
}
lag {
lag-type static
// lag-type could also be lacp, in which case the
system-id/key must match on lag2 of LEAF2B
member-speed 10G
}
}
// A vxlan-interface is created for the inter-chassis traffic
--{ candidate shared default }--[ ]-
A:LEAF2A# info tunnel-interface vxlan1 vxlan-interface 10
tunnel-interface vxlan1 {
vxlan-interface 10 {
type bridged
ingress {
vni 10
}
}
}
// the Ethernet Segments associated to lag1 and lag2
--{ candidate shared default }--[ ]--
A:LEAF2A# info system network-instance protocols evpn
system {
network-instance {
protocols {
evpn {
ethernet-segments {
bgp-instance 1 {
ethernet-segment ES-leaf1-leaf2.CE1 {
admin-state enable
esi 00:12:12:12:12:12:12:00:00:01
interface lag1
}
ethernet-segment ES-leaf1-leaf2.Spines {
admin-state enable
esi 00:12:12:12:12:12:12:00:00:02
interface lag2
}
}
}
}
}
}
}
// the mac-vrf uses lag sub-interfaces for the connectivity to rest of
the leaf nodes and servers, and a vxlan-subinterface for the connectivity
to LEAF2B
--{ candidate shared default }--[ ]--
A:LEAF2A# info network-instance Blue-MAC-VRF-10
network-instance Blue-MAC-VRF-10 {
type mac-vrf
interface ethernet-1/1.10 {
!!! this is connected to a single-homed access server-1
}
interface lag1.10 {
!!! access lag - multi-homed to access server-3
}
interface lag2.10 {
!!! multi-homed to spines
}
vxlan-interface vxlan1.10 {
!!! vxlan-interface used for inter-chassis connectivity only
}
protocols {
bgp-evpn {
bgp-instance 1 {
admin-state enable
vxlan-interface vxlan1.10
evi 10
}
}
bgp-vpn {
}
}
}
// lag1 connects LEAF2B to server-3 and is associated to
an all-active Ethernet Segment
--{ candidate shared default }--[ ]--
A:LEAF2B# info interface lag*
interface lag1 {
admin-state enable
vlan-tagging true
subinterface 10 {
type bridged
vlan {
encap {
single-tagged {
vlan-id 10
}
}
}
}
lag {
lag-type static
// lag-type could also be lacp, in which case the
system-id/key must match on lag1 of LEAF2A
member-speed 10G
}
}
// lag2 connects LEAF2B to LEAF3A and LEAF3B.
This LAG is an access LAG (does not carry vxlan) associated to
an all-active Ethernet Segment
interface lag2 {
admin-state enable
vlan-tagging true
subinterface 10 {
type bridged
vlan {
encap {
single-tagged {
vlan-id 10
}
}
}
}
lag {
lag-type static
// lag-type could also be lacp, in which case the
system-id/key must match on lag2 of LEAF2B
member-speed 10G
}
}
// A vxlan-interface is created for the inter-chassis traffic
--{ candidate shared default }--[ ]--
A:LEAF2B# info tunnel-interface vxlan1 vxlan-interface 10
tunnel-interface vxlan1 {
vxlan-interface 10 {
type bridged
ingress {
vni 10
}
}
}
// the Ethernet Segments associated to lag1 and lag2
--{ candidate shared default }--[ ]--
A:LEAF2B# info system network-instance protocols evpn
system {
network-instance {
protocols {
evpn {
ethernet-segments {
bgp-instance 1 {
ethernet-segment ES-leaf1-leaf2.CE1 {
admin-state enable
esi 00:12:12:12:12:12:12:00:00:01
interface lag1
}
ethernet-segment ES-leaf1-leaf2.Spines {
admin-state enable
esi 00:12:12:12:12:12:12:00:00:02
interface lag2
}
}
}
}
}
}
}
// the mac-vrf uses lag sub-interfaces for the connectivity to rest of the
leaf nodes and servers, and a vxlan-subinterface for the connectivity
to LEAF2B
--{ candidate shared default }--[ ]--
A:LEAF2B# info network-instance Blue-MAC-VRF-10
network-instance Blue-MAC-VRF-10 {
type mac-vrf
interface ethernet-1/2.10 {
!!! this is connected to a single-homed access server-2
}
interface lag1.10 {
!!! access lag - multi-homed to access server-3
}
interface lag2.10 {
!!! multi-homed to spines
}
vxlan-interface vxlan1.10 {
!!! vxlan-interface used for inter-chassis connectivity only
}
protocols {
bgp-evpn {
bgp-instance 1 {
admin-state enable
vxlan-interface vxlan1.10
evi 10
}
}
bgp-vpn {
}
}
}