Guest

Preview Tool

Cisco Bug: CSCum68863 - Nexus 5000- FCoE VFCs stuck in VSAN Initializing after upgrade/Reload!

Last Modified

Feb 02, 2017

Products (7)

  • Cisco Nexus 5000 Series Switches
  • Cisco Nexus 5548P Switch
  • Cisco Nexus 5596UP Switch
  • Cisco Nexus 5020 Switch
  • Cisco Nexus 5548UP Switch
  • Cisco Nexus 5010 Switch
  • Cisco Nexus 5596T Switch

Known Affected Releases

5.2(1)N1(6)

Description (partial)

Symptom:
FCOE VFCs configured with FIP Mac address in a Nexus 5000 may get stuck in VSAN initializing state after a NX-OS code upgrade performed or reload of Nexus 5000 with the below messages in syslogs.

###
2014 Jan  8 09:02:21 N-5010  PORT-5-IF_TRUNK_DOWN  %$VSAN 6%$ Interface vfc2612, vsan 6 is down (waiting for flogi)   
2014 Jan  8 09:02:21 N-5010  PORT-5-IF_TRUNK_DOWN  %$VSAN 6%$ Interface vfc2069, vsan 6 is down (waiting for flogi)   
2014 Jan  8 09:02:21 N-5010  PORT-5-IF_TRUNK_DOWN  %$VSAN 6%$ Interface vfc2622, vsan 6 is down (waiting for flogi)  
###

Also the affected VFCs can't be removed from the configuration. The below error message may be seen.

!
N-5-1-(config)# no int vfc 5508
Error: vfc5508 (null)   ------------>> Error
!

Conditions:
Nexus 5000 having more than 50 VFCs bound to mac-address, hosts connected to a fip-snooping bridge (Nexus 4000), after a Nexus Os code upgrade in Nexus 5000 or after a reload.
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.