Showing results for 
Search instead for 
Did you mean: 

import from default-vrf & advertise-as-vpn possible bug

Level 1
Level 1

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 is leaked from Global to vrf A, and is know via BGP with its NH reachable via in global. When I make a routing change (IGP metric), so that BGP NH is reachable via, then 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 ?


Thanks in advance !






0 Replies 0
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card