OPERATIONAL DEFECT DATABASE
...
...
Route is is not advertising in any IPv4/IPv6 space out to the providers that are locally attached.
Customer has the mixed RD configuration in their network. They will see this issue often. dcpe using one RD and mspe uisng another RD for the same VRF. The recommendation is that either using the same RD for the same vrf on all PEs or use different RD on all PEs.
There is no acceptable workaround
We have a bug in the soft-reconfigure path when the local RD is marked as Same RD and we have different RD imported path. If the RD is the SAME RD node which means it is locally configured and it is also a received RD from remote), Then for net which has different RD imported path, we will wrongly create the path with net RD as source RD whenever route-policy change. This only happens for net which has different RD imported path and the RD is marked as Has remote net. During the soft-reconfigure processing if the path is different RD imported path, we should not create the modified path. Since the net's sourced path will be changed according to policy, we should just let the import to update the path. We have the Customer's configuration loaded. And create a local vrf test using the same RD as 12200:1000000005 on dcpe1. On MSPE RD 12200:1000000005 will be SAME RD case. The net will has path imported from different RD (src RD 12200:1000000001) and same RD imported path. Do few set/unset CM-BLEED community (change the inbound policy on mspe for neighbor RR1). You will see extra path which is from different RD imported path but the src RD is local RD. You can remove the test vrf, you will still see the issue. The issue can be reproduced even without dcpe2 node.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
