Guest

Preview Tool

Cisco Bug: CSCur88990 - Delay in interface down event post MSTP status change

Last Modified

Apr 29, 2016

Products (7)

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

Known Affected Releases

6.2(2a)

Description (partial)

Symptom:
Scenario 1: ASR9000 Rack Reload ? Event transitions delayed by 14 seconds

	On N7K per item#729 below in EthPM traces, port goes to BLK which is as expected, and the port cleanup for PoCH200 happened at the same time Fri Oct 31 08:52:13 2014, however the PoCH200 went down after 14 seconds as per Item#725 during the timestamp: Fri Oct 31 08:52:27 2014


725) Event:(null), length:160, at 817206 usecs after Fri Oct 31 08:52:27 2014
stp_common_im_protocol_state_change_handler(2423): IM L2 Port Proto DOWN Notif : port_mode 0x100000, speed 10000, duplex 2, primary 1, port Po200, vlans ,


726) Event:(null), length:110, at 823938 usecs after Fri Oct 31 08:52:13 2014
stp_ethpm_complete_port_logical_cleanup(): EthPM logical cleanup for port Po200 complete with status 0x0


727) Event:(null), length:102, at 260695 usecs after Fri Oct 31 08:52:13 2014
stp_port_logical_cleanup_delete_vlan_ports(3843): EthPM logical down for port Po200 vlans 1-3967


728) Event:(null), length:130, at 257567 usecs after Fri Oct 31 08:52:13 2014
vb_vlan_shim_set_vlans_multi_port_state(3045): Req (type=5) to PIXM vdc 2, inst 0, num ports 1, state DIS [Po200 v 1-3966]


729) Event:(null), length:128, at 257279 usecs after Fri Oct 31 08:52:13 2014 vb_vlan_shim_set_vlans_multi_port_state(3045): Req (type=5) to PIXM vdc 2, inst 0, num ports 1, state BLK  [Po200 v 3967]

	Now looking from vPC view from output of 'show system internal vpcm event-history interactions', why is Item#27 still showing Port-State Down at Oct 31 08:52:27 2014 when the interface was put to BLK state at Fri Oct 31 08:52:13 2014 (14 seconds)


26) Event:E_DEBUG, length:104, at 310154 usecs after Fri Oct 31 09:06:30 2014 (after ASR9K Rack0 restore)
    [104] Sending Local SCN for vpc: 200 Port Mode: 0x100000, Port State:0x1, Up vlans: 1-3967, Down vlans: 



27) Event:E_DEBUG, length:98, at 817221 usecs after Fri Oct 31 08:52:27 2014 (when ASR9K Rack0 was down)
    [104] Sending Local SCN for vpc: 200 Port Mode: 0x100000, Port State:0x2, Up vlans: , Down vlans: 



28) Event:E_DEBUG, length:105, at 172308 usecs after Fri Oct 31 08:52:13 2014 (when ASR9k Rack0 was triggered to go down)
    [104] Sending Local SCN for vpc: 200 Port Mode: 0x100000, Port State:0x10, Up vlans: , Down vlans: 1-3967

	From Finite State Machine logs for MCEC: (Mcec:0xc8 == Port-ch 200), I don't see anything abnormal as the PoCh status went DOWN as per Item#99 at Fri Oct 31 08:52:13 2014

96) FSM:<Mcec:0xc8> Transition at 126127 usecs after Fri Oct 31 08:52:13 2014
    Previous state: [MCEC_ST_MCEC_PHY_UP]
    Triggered event: [MCEC_EV_LAST_MEM_DOWN]
    Next state: [MCEC_ST_MCT_MSHIP_CHG]

97) FSM:<Mcec:0xc8> Transition at 164387 usecs after Fri Oct 31 08:52:13 2014
    Previous state: [MCEC_ST_MCT_MSHIP_CHG]
    Triggered event: [MCEC_EV_MSHIP_CHG_DONE]
    Next state: [MCEC_ST_HW_CLNUP_SNT]

98) FSM:<Mcec:0xc8> Transition at 167370 usecs after Fri Oct 31 08:52:13 2014
    Previous state: [MCEC_ST_HW_CLNUP_SNT]
    Triggered event: [MCEC_EV_CLNUP_DONE]
    Next state: [MCEC_ST_DOWN]

99) FSM:<Mcec:0xc8> Transition at 827154 usecs after Fri Oct 31 08:52:13 2014
    Previous state: [MCEC_ST_DOWN]
    Triggered event: [MCEC_EV_LOG_DOWN]
    Next state: [FSM_ST_NO_CHANGE]

Conditions:
Any reload or fiber pull on ASR9000 triggering PoCH-200 membership change on N7K.
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.