Guest

Preview Tool

Cisco Bug: CSCuq41377 - CST: Port inconsistency when port is recovered from err disabled state

Last Modified

Mar 10, 2018

Products (1)

  • Cisco MDS 9000 Series Multilayer Switches

Known Affected Releases

6.2(9)S32

Description (partial)

The F port is in initializing state because the link is up, but it is waiting on first flogi to be received. This is expected.

Here are the logs:
2) FSM:<fc10/2> Transition at 65370 usecs after Fri Aug 15 12:17:28 2014
    Previous state: [PI_FSM_ST_F_PORT_UP]
    Triggered event: [PI_FSM_EV_LC_EXT_LINK_STATUS_RCVD]
    Next state: [FSM_ST_NO_CHANGE]

3) FSM:<fc10/2> Transition at 65403 usecs after Fri Aug 15 12:17:28 2014
    Previous state: [PI_FSM_ST_F_PORT_UP]
    Triggered event: [PI_FSM_EV_LCP_LINK_FAILURE_BIT_ERR_RATE]
    Next state: [FSM_ST_NO_CHANGE]

Line card sends a link status event to port manager declares the reason to mark the port as error disabled.

After sh/ no shut on the port, laser is turned on and waiting for logins and remain in initializing state.
35) FSM:<fc10/2> Transition at 304040 usecs after Fri Aug 15 12:17:58 2014
    Previous state: [PI_FSM_ST_LINK_INIT]
    Triggered event: [PI_FSM_EV_LCP_LINK_STATUS_RCVD]
    Next state: [FSM_ST_NO_CHANGE]

36) FSM:<fc10/2> Transition at 304150 usecs after Fri Aug 15 12:17:58 2014
    Previous state: [PI_FSM_ST_LINK_INIT]
    Triggered event: [PI_FSM_EV_LCP_INIT_STATUS_SUCCESS]
    Next state: [FSM_ST_NO_CHANGE]

37) FSM:<fc10/2> Transition at 304535 usecs after Fri Aug 15 12:17:58 2014
    Previous state: [PI_FSM_ST_LINK_INIT]
    Triggered event: [PI_FSM_EV_LCP_INIT_STATUS_7]
    Next state: [PI_FSM_ST_F_PORT_INIT_1]

38) FSM:<fc10/2> Transition at 302072 usecs after Fri Aug 15 12:18:18 2014
    Previous state: [PI_FSM_ST_F_PORT_INIT_1]
    Triggered event: [PI_FSM_EV_PACER_TIMER_EXPIRED]
    Next state: [FSM_ST_NO_CHANGE]

    Curr state: [PI_FSM_ST_F_PORT_INIT_1]

Symptom:
The port is marked error disabled because of IF_DOWN_BIT_ERR_RT_THRES_EXCEEDED.

After sh/ no shut on the port, laser is turned and the port is waiting for logins.

Conditions:
After device logs in, the port will come up. It is working as expected.
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.