Configuring Anycast MH
Anycast Multi-Homing (MH) is enabled per Ethernet Segment (ES) on egress leaf nodes (such as Leaf1 and Leaf2 in EVPN Anycast MH).
The ingress leaf node (such as Leaf3 in EVPN Anycast MH) requires no specific configuration to enable the Anycast MH mode. For backward compatibility within the same MAC-VRF, the ingress leaf supports two types of overlay ECMP.
- ECMP to all egress leaf nodes advertising the Anycast VTEP
- Ethernet Aliasing to all nodes of the same ES that advertise A-D per EVI routes and are operating in a non-anycast mode.
To configure Anycast MH per ES on the egress leaf node, use the command ethernet-segment.anycast-multi-homing. The configuration of ethernet-segment.anycast-multi-homing.ip-address <ip-address> is mandatory.
The IP address parameter (ip-address <ip-address>) should match an IPv4 address configured on a loopback interface in the default network instance. The system does not verify that the address exists on a loopback interface; you must ensure the correct IP address is configured.
The Anycast MH mode is supported in the following scenarios:
- All-active multihoming ES
- ES associated with Ethernet or LAG interfaces
The following configuration example enables Anycast MH for the ES named srl_ES within BGP instance 1, assigning 12.12.12.12 as the shared Anycast IP address for that segment.
--{ * candidate shared default }--[ ]--
# info with-context system network-instance protocols evpn ethernet-segments
system {
network-instance {
protocols {
evpn {
ethernet-segments {
bgp-instance 1 {
ethernet-segment srl_ES {
anycast-multi-homing {
ip-address 12.12.12.12
}
}
}
}
}
}
}
}