• Author : Gary McCarthy

 
 

VPN and IPv6 Provider Edge (6PE) Traffic Steering into SR-TE Policy

Description 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. EOS 4.24.1F adds support for traffic steering into SR-TE policy for non IP unicast services including: IPv6 Provider Edge (6PE), MPLS L3 VPN, L3 EVPN, and EVPN VPWS. The following enhancements are also included with this feature: Allow a color extended community to be added to a route using an inbound/outbound route-map so that any BGP route (on supported unicast services) can leverage SR-TE policies. A new tunnel-rib called the system-colored-tunnel-rib is introduced. The system-colored-tunnel-rib is used...
Continue reading →

BGP Out-Delay Changes/Withdrawals

Description BGP out-delay is an existing feature in EOS where an optional delay could be applied prior to advertising a route. The delay was only applied to newly learned routes. Options are now provided to also apply out-delay to route changes and withdrawals. The purpose of this enhancement is to coalesce frequent oscillation in a route to protect downstream routers from unnecessary load. Out-delay is applied when a route enters the rib-out stage of the system after outbound policy is applied prior to transmission. Advertisements that are not subject to out-delay are typically transmitted immediately (although some delay may occur...
Continue reading →

BGP Aggregate Address Advertise-only

The aggregate address advertise-only feature adds the capability of NOT installing the Null0 route in the FIB/kernel for an aggregate route while still advertising it to BGP peers. By default, BGP aggregates are installed as a drop/Null0 route which will blackhole destinations in the aggregate prefix’s range that don’t have a more specific route. With this feature enabled, the drop/Null0 route is not installed thereby allowing a covering route (say the default route) to route such traffic. Configuration The CLI option will appear under the “aggregate-address” command in router-bgp mode.  The full syntax of the CLI is given below with...
Continue reading →

BGP Missing Policy Action

Description The default policy behavior is to permit/accept all routes when a BGP neighbor or peer group is configured with a route-map which is misconfigured (e.g. the route-map is either empty or referencing a non-existing route-map). This type of misconfiguration can go undetected causing undesirable issues (such as hitting the peer max prefix limit). A route-map is considered “empty” when it is referenced by a neighbor or peer group but not defined by the CLI (or perhaps has been deleted). A route-map is considered “non-empty” once a sequence is defined for the route-map. It does not need to have any...
Continue reading →

Follow

Get every new post on this blog delivered to your Inbox.

Join other followers: