TOI Author :: Matthew Carrington-Fair

This feature allows configuring backup nexthop group entries to be used if their corresponding primary entries are unable to forward traffic due to being unresolved or with outgoing interfaces that are marked as down. By default, any configured backup entries will not be activated to forward traffic until all primary nexthop group entries are unavailable. Backup nexthop group entries are a tool used to achieve fast failover when forwarding traffic via nexthop groups.

EOS 4.15.0F added support for a CLI knob to determine whether the L3 forwarding agent (responsible for programming FECs and routes into hardware) would react to BFD status events for an interface to update next-hop programming for FECs programmed in hardware. This required two events, one for the BFD session to transition to an “Up” status and a subsequent transition to a “Down” status. This is identical to how various protocols in EOS (i.e. BGP, IS-IS) leverage BFD for faster down detection, and is useful to allow the L3 forwarding agent to preemptively remove next hops that would later be deprogrammed due to protocol session status state.

This feature allows the export of IP FIB (Forwarding Information Base) through the OpenConfig AFT YANG models.

Prior to EOS 4.27.0F, MPLS tunnel egress counters could only be enabled for all MPLS tunnels present in the system

Prior to 4.25.2F, support for BGP PIC was restricted to locally identifiable failures such as link failures. If a

EOS 4.23.1F introduces the ability to configure the color extended community in route map set clauses and in an