Guest

Preview Tool

Cisco Bug: CSCuq56034 - IPFIB crash due to segmentation fault

Last Modified

Feb 01, 2017

Products (6)

  • Cisco Nexus 3000 Series Switches
  • Cisco Nexus 3064 Switch
  • Cisco Nexus 3016 Switch
  • Cisco Nexus 3064-T Switch
  • Cisco Nexus 3048 Switch
  • Cisco Nexus 3132Q Switch

Known Affected Releases

6.0(2)U2(1)

Description (partial)

Symptom:
In certain scenarios a Nexus 3000 running Fiji code might experience an IPFIB crash with the following message - "VDC-1 %$ %SYSMGR-2-SERVICE_CRASHED: Service "ipfib" (PID xxxx) hasn't caught signal 11 (core will be saved)."

Conditions:
This happens under a very specific set of conditions

The crash is triggered when the following two conditions are satisfied:
 
1) Presence of a IPv6 prefix a1/m1 and a covering prefix a1/m2, where the 128-bits of the IPv6-address part of the prefix match exactly
2) The following two route update sequences are triggered due to network events
   a) At point in time x, Add/Update a1/m1 and a1/m2 in the same MTS buffer
   b) At a later point in time y (x and y could be quite apart, as long as there are no further updates for a1/m1 or a1/m2 during the interim), another event with Add/Update of a1/m2 and Delete of a1/m1 is triggered in the same MTS buffer
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.