import from default-vrf & advertise-as-vpn possible bug
I am experiencing something similar to CSCut04689, where by imported prefix fails to be advertised to vrf when route to BGP next hop for the prefix changes.
For example prefix 10.1.1.1/32 is leaked from Global to vrf A, and 10.1.1.1/32 is know via BGP with its NH reachable via 192.168.10.1 in global. When I make a routing change (IGP metric), so that BGP NH is reachable via 192.168.20.1, then 10.1.1.1/32 is no longer leaked to vrf.
Workaround I plan to test is to reapply the vrf definition with its import export policies, without actually removing it. As well as clear route in global....then trace labels.
This issue is seen on ASR9010 running 5.3.4
Anyone seen similar issues or has good suggestions ?
Cisco recently announced the availability of the IOS-XE train – IOS-XE Cupertino 17.7.1. This is a standard maintenance release supporting switching, wireless, SP-Access, Routing as well as IoT (Internet of things) platforms with a sustaining support life...
What is AppQoE?
AppQoE is a WAN optimization stack and optimizes WAN traffic for different use cases for applications that are deployed on-prem or in cloud.
What are the benefits of using AppQoE?
AppQoE improves application experience by d...
The application delivery challenges have been the enemy of network since the advent of Internet. So, what are these application delivery challenges that can bring down a network to its heels?
Above are some of the common problems faced not only by tradit...
It is our pleasure to officially announce the finalists in the 2021 IT Blog Awards. Now we are looking to YOU, our amazing tech community, to weigh in. Check out the amazing educational content we've uncovered and vote for your favorites before Friday, Fe...