I have a router running 12.2(33) SRE2 that is leaking a prefix from a VRF RIB into the Global RIB. For example's sake, the prefix is 10.10.10.x/24. The global RIB says that it is originating the 10.10.10.x/24 via BGP with a next-hop of null0. The strange part is that 10.10.10.x/24 and more specific compoent prefixes are nowhere to be found the in the router's global IGP process, global static routes, nor global connected routes. There are, however, other IPv4 VRFs that are redistributing their connected VRF interfaces (within the 10.10.10.x/24 address space) into their own IPv4 BGP VRF tables that are then subsequently aggregated to a 10.10.10.x/24 under their own VRF's BGP process. Regardless, I should not see the router originating the 10.10.10.x/24 prefix via BGP in its own global routing table. Is there a bug on 12.2(33)SRE2 that would cause this issue?
Crosswork Cloud - Crosswork Traffic Analysis - FAQ
Crosswork Cloud - Crosswork Traffic Analysis is a Cloud-hosted Software as a Service platform that provides Netflow based Traffic Analytics. The Crosswork Traffic Analysis platform Traffic Analysis, Peeri...
Cisco Champion Radio · S8|E9 Innovations to Achieve a Trustworthy Infrastructure
How do you know for certain that a router in your network has not been altered with since you deployed it? Wouldn’t it be great if you can cryptographically challenge your r...
IOS upgrade on asr9xx mandates rommon upgrades sometimes while they can be optional at other times. You may land up in unwanted situation if proper procedure is not followed during upgrades.
This article will include complete details about rommon ...
In some situation NCS560 RP become unresponsive after reload or powercycle.
In many NCS560 deployments are in remote location, deployment might be large and human intervention should be kept at minimum
Engineering team have been working on a str...
In simple terms, 'Route Churn' is defined as the 'rate of change of prefixes'. Different XR versions across 4.x to 7.x have differing behavior & support for the BGP churn handling and some enhancements made from 6.5.3 onwards (listed in appendix) mak...