How to match certain tagged routes using RPL when they are not the best routes
( R1 ) -ibgp-> ( R2 ) -ebgp-> ( R3 )
The scenario is that router R1 is announcing routes to R2. Those routes are tagged from R2 inbound using RPL (community is 123:123). Now the R2 has an RPL policy towards R3 which dictates to match any routes that match the community 123:123. This would match all routes that R1 is announcing.
The observed behaviour is that as long as the R1 routes are best routes in R2 BGP table they are picked up by the RPL policy that's applied towards R3. However, this does not work when those R1 routes are not the best routes in the R2 BGP table. If so, is it possible to pick routes (using the community 123:123) which are not best and announce them to R3?
The idea is that R1 routes should never be the best routes in the R2 table. The purpose is to only announce those routes towards R3.
Re: How to match certain tagged routes using RPL when they are not the best routes
You could prefer the routes from R1 via some mechanism like local preference over other routes coming from other peers. We will only announce our best path, so you have to make the routes from R1 the best route, an alternative is BGP add-path + multipath so you can have a best and backup path installed and advertise both to your R3 peer.
This guide will explain how to check where a particular directory resides within the filesystem in terms of physical disk, logical volume, volume group, etc by taking a look at where the install repository actually resides on an NCS5500.
According to the RFC 7432:
Extended Community enables split-horizon procedures for multihomed sites. The ESI Label field represents an ES by the advertising PE, and it is used in split-horizon filtering by other PEs that are connected to th...
In scaled EVPN deployments it can be wise to name ESI that way to represent the site/physical port/etc it is attached to. Thus on some remote location you can easily verify where particular route/MAC is coming from. Similar to phone numbers, where...
Want to enable Feature EPFT with “routing-protocols-enable”. However ,it is throwing an error and ask to configure the following command: “non-subscriber-interfaces mac” which once enabled drops the traffic without any penalty.
XR-vm - CLI's
look for any process crash, review time stamp[if it is too old, then no immediate action needed]
verify if standby state is Ready and NSR-Ready
show proc cpu | exclude " 0%"