10-05-2018 01:47 AM
Hi,
In 6.1.4, I have noticed that the default-route injected to bgp via the default-originate command associated to the neighbor (in a vrf), is updated in the receiving end (CPE), when the default route is added to the bgp RIB from the WAN. The default-originate command is not tied to a route-policy, so it should be advertised totally independent of any presence of the default route in the RIB. So in short, if I add/remove/add/remove the default route in the WAN, the default route gets new timestamps in the CPE at every occurence in 6.1.4. This is not seen in 6.4.2. Is anyone aware of any difference in the behavior between the two versions regarding this?
Best Regards
Per
10-05-2018 06:16 AM
Are you seeing this?
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCve41797/?rfs=iqvred
10-05-2018 07:01 AM
I don't have a route-policy attached to 'default-originate' command. And it's only the default route from the WAN that flaps the originated (by the router) default route. Any other route update is not affecting the default route.
10-05-2018 11:25 AM
It is expected behavior and it is documented in bug:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide