- Written by Gary McCarthy
- Posted on January 3, 2023
- Updated on January 11, 2023
- 1483 Views
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.
- Written by Gary McCarthy
- Posted on June 29, 2020
- Updated on July 12, 2023
- 3688 Views
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
- Written by Gary McCarthy
- Posted on January 22, 2019
- Updated on February 5, 2022
- 3208 Views
BGP out delay is an existing feature in EOS where an optional delay could be applied prior to advertising a route. The
- Written by Gary McCarthy
- Posted on November 22, 2017
- Updated on February 6, 2022
- 3513 Views
The aggregate address advertise only feature adds the capability of NOT installing the Null0 route in the FIB/kernel
- Written by Gary McCarthy
- Posted on February 8, 2017
- Updated on October 13, 2021
- 3494 Views
The default policy behavior is to permit/accept all routes when a BGP neighbor or peer group is configured with a route