Preview Tool

Cisco Bug: CSCum05295 - BGP multipath entry in uRIB does not get updated after attribute change

Last Modified

May 11, 2020

Products (4)

  • Cisco Nexus 7000 Series Switches
  • Cisco Nexus 7000 10-Slot Switch
  • Cisco Nexus 7000 18-Slot Switch
  • Cisco Nexus 7000 9-Slot Switch

Known Affected Releases


Description (partial)

There are two symptoms that can be seen for this bug.

1. The following error message can be seen in syslog and IGP redistributing BGP routes may fail.

2013 Dec 13 01:21:58 PTAINTS410 %OSPF-3-RPM_LIB_API_FAILED: bgp_lookup_ext_attr() - failed in rpm_acquire_bgp_shmem_lock()

2. A route with a stale metric in the routing table exists

`DC1-CORE-3#  sho ip bgp

BGP routing table information for VRF default, address family IPv4 Unicast
BGP routing table entry for, version 127677
Paths: (6 available, best #1)
Flags: (0x00001a) on xmit-list, is in urib, is best urib route
Multipath: eBGP iBGP

  Path type: internal, path is valid, received and used, not best reason: Router Id, multipath
  AS-Path: NONE, path sourced internal to AS (metric 101) from (
      Origin IGP, MED 409, localpref 100, weight 0  <====== MED 409 should match routing table

DC1-CORE-3# sho ip route
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>, ubest/mbest: 5/0
    *via, [200/409], 00:10:12, bgp-65001, internal, tag 65001
    *via, [200/409], 00:43:22, bgp-65001, internal, tag 65001
    *via, [200/409], 00:43:22, bgp-65001, internal, tag 65001
    *via, [200/409], 00:43:22, bgp-65001, internal, tag 65001
    *via, [200/409], 00:43:22, bgp-65001, internal, tag 65001
     via, [200/65940], 00:15:17, bgp-65001, internal, tag 65001 <<======= OLD MED 409 not updated

1. IGP (e.g., OSPF) redistributes BGP routes.
2. The redistribution uses route-map to evaluate community associated with the routes.
3. Maximum-paths command is configured.
4. BGP receives paths with only attribute (e.g., AS-PATH,MED) change.
Bug details contain sensitive information and therefore require a 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.