It is often useful to know on a per AFI/SAFI basis, the number of paths that have been selected from a peer as best paths.

This feature provides a mechanism to mark specific routes as resilient ECMP (RECMP) eligible using BGP RCF policies. A policy based mechanism provides a lot of flexibility in choosing the RECMP eligible routes using criteria such as:

Routes covered by a resilient equal-cost multi-path (RECMP) prefix are types of routes that make use of hardware tables dedicated for equal-cost multi-path (ECMP) routing.

ECMP Hash visibility CLI determines the output interface for an ECMP set based on the flow parameters supplied by the user. Ingress interface, source IP address, destination IP address and IP protocol are the required parameters.

ECMP Hash visibility CLI determines the output interface for an ECMP set based on the flow parameters supplied by the

As of 4.22.1F Load Balance Profiles can be used to explicitly configure ECMP Load Balance parameters. In addition,

On network devices, when a route is programmed, a certain portion of hardware resources is allocated and associated

EOS version 4.24.1F introduces support for specifying multiple vias to form ECMP in MPLS static tunnels. A new

Multipath color is a new multicast multipath mode for controlling PIM RPF selection. In the default multipath

Routes covered by a resilient equal cost multi path (RECMP) prefix are types of routes that make use of hardware tables

This feature adds support for source interface based load-balancing with Dynamic Load-Balancing ( DLB ) and Hash based Load-Balancing on Equal Cost Multi Path ( ECMP ) groups

This feature adds the support for learning multiple equal cost routes for a destination in the RIP protocol. This

ECMP 4.24.F RIP

Nexthop groups is a routing mechanism where users can configure a set of nexthops by specifying their nexthop

In the ribd routing protocol model, the “maximum paths … ecmp …” command allows restricting the number of BGP