Guest

Preview Tool

Cisco Bug: CSCvv43175 - Changes inside route-map does not take effect

Last Modified

Oct 13, 2020

Products (2)

  • Cisco ASR 5000 Series
  • Cisco ASR 5000 Series

Known Affected Releases

21.11.16 21.11.9.73403

Description (partial)

Symptom:
C-SGN ASR5500
Software version - 21.11.9
The modification inside a route-map is not taken into account by the VRF which is associated with.
This is even happening without VRF

In the below sample configuration
vrf vrf_collecteb2b_test is associated with route-map "DENY"

 address-family ipv4 vrf vrf_collecteb2b_test
        redistribute connected route-map DENY 
      #exit	  
	   route-map DENY permit 10
      match ip address prefix-list DENY
    #exit	
	ip prefix-list name DENY seq 5 deny any
	ip prefix-list name PERMIT seq 5 permit any	
	
The route-map DENY is either associated to a prefix-list DENY which deny all the routes or to a prefix-list PERMIT which permits all.

ip prefix-list name DENY seq 5 deny any
ip prefix-list name PERMIT seq 5 permit any

The modification of the route-map is only taken into account if it is removed from VRF and then associated back.

For example, if we update the route-map DENY by changing the prefix-list from DENY to PERMIT or vice-versa and then do "clear ip bgp peer all" or "clear ip bgp peer <IP> soft"
the changes are not announced by staros node to remote BGP peer but after making the route-map changes if we remove the route-map and associate back in the vrf (like below) then staros is 
announcing the changes to remote bgp peer.

 router bgp 64970
 address-family ipv4 vrf vrf_collecteb2b_test
 no redistribute connected route-map DENY
 redistribute connected route-map DENY

Conditions:
modification inside a route-map is not taken into account
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.