- Written by Gary McCarthy
- Posted on 1月 30, 2024
- Updated on 1月 30, 2024
- 2137 Views
VRF redirection often requires matching packets’ source addresses against one or more sets of IP prefixes. This can become difficult to manage when the prefix sets need to be consistently maintained on several devices and either change too frequently or are very large. When the prefixes for the prefix sets are learned by BGP, this feature provides an alternative to maintaining unwieldy sets of statically configured IP prefixes.
- Written by Gary McCarthy
- Posted on 1月 3, 2023
- Updated on 4月 29, 2024
- 4754 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 6月 29, 2020
- Updated on 7月 12, 2023
- 7014 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 1月 22, 2019
- Updated on 2月 5, 2022
- 6109 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 11月 22, 2017
- Updated on 2月 6, 2022
- 6748 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 2月 8, 2017
- Updated on 10月 13, 2021
- 7077 Views
The default policy behavior is to permit/accept all routes when a BGP neighbor or peer group is configured with a route