TOI Author :: Gary McCarthy

Prior to release EOS 4.29.1, a statically configured BGP neighbor, listen range or interface peer could reference a single peer group for inheriting configuration parameters. EOS 4.29.1 adds the ability for that peer group to inherit configuration from up to 8 additional “ancestor” peer groups. The term “leaf peer group” is given to the peer group which is directly referenced by the BGP neighbor, listen range or interface peer.

Prior to EOS 4.24.1F, per-destination steering into an SR Policy was only supported for IP unicast BGP routes in the default VRF. Support for additional AFI/SAFIs were added as follows: EOS 4.24.2F: L2 EVPN — EOS 4.27.2F: BGP Labeled Unicast

BGP out delay is an existing feature in EOS where an optional delay could be applied prior to advertising a route. The

The aggregate address advertise only feature adds the capability of NOT installing the Null0 route in the FIB/kernel

The default policy behavior is to permit/accept all routes when a BGP neighbor or peer group is configured with a route