ECMP Support on ICL in Multinode High Availability
Equal-Cost Multi-Path (ECMP) allows the distribution of traffic across multiple paths that have the same cost, thereby increasing throughput and providing path redundancy. In a Multinode High Availability setups, you can use ECMP to enhance the ICL (Interchassis Link) by configuring it to utilize multiple links. This is achieved by enabling ECMP on the ICL, allowing traffic to be distributed across multiple paths, thereby optimizing the performance and redundancy of the ICL. In an MNHA configuration, where the reliability and efficiency of network traffic are paramount, ECMP ensures that no single path becomes a congestion, and that network resources are utilized effectively.
Configure ICL to Use ECMP
For the ICL configuration, follow the standard MNHA ICL setup process. Use the lo0 interface as the local and peer endpoints. See Example: Configure Multinode High Availability in a Layer 3 Network.
IEnable the
l4-key-ecmpunder the[edit security flow]hierarchy on both devices in MNHA setup:[edit] set security flow l4-key-ecmp
Ensure ICL peer reachability through routing protocols or static routes with ECMP policy enabled.
Configure load-balancing policies to efficiently distribute traffic across multiple paths.
The following configuration snippets set up a static route with two possible next-hop paths for destination
11.0.1.1and applies per-packet load balancing to distribute traffic evenly across these paths.user@host# show routing-options autonomous-system 300; static { route 11.0.1.1/32 next-hop [ 22.0.0.2 23.0.0.2 ]; } forwarding-table { export lb; }- ECMP load-balancing
policy:
user@host# show policy-options policy-statement lb then { load-balance per-packet; }
Use the
show route forwarding-table destinationcommand to check if the multiple paths or interfaces for ICL peer are installed in forwarding table due to ECMP configuration.user@host> show route forwarding-table destination 11.0.1.1 Routing table: default.inet Internet: Destination Type RtRef Next hop Type Index NhRef Netif 11.0.1.1/32 user 0 ulst 262143 2 23.0.0.2 ucst 617 3 xe-1/0/6.0 22.0.0.2 ucst 620 3 xe-1/0/7.0
If an ECMP next-hop is removed and later re-added, the added interface or next hop will not be updated in ECMP for RTO sync sessions because flowd already has an existing next-hop. As a result, RTO sync sessions will use only the existing next-hop even when ECMP is updated with additional next hops or interfaces.
Check Feature Explorer for support on different platforms.