Guest

Preview Tool

Cisco Bug: CSCvt36085 - Port-channel member goes error disabled during ISSU but still is sent frames which are discarded

Last Modified

Jun 25, 2020

Products (1)

  • Cisco MDS 9000 Series Multilayer Switches

Known Affected Releases

6.2(29)

Description (partial)

Symptom:
Port-channel member not removed from port-channel frame scheduling when it fails during ISSU.

When this occurs the port is down but output discards are incrementing on the interface.
<pre>
fc3/1 is down (Error disabled - bit error rate too high)                        <<<<<< Port is down
    Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
    Port WWN is 20:81:00:2a:6a:65:5a:80
    Admin port mode is E, trunk mode is on
    snmp link state traps are enabled
    Port vsan is 1
    Receive data field Size is 2112
    Beacon is turned off
    Belongs to port-channel214
    5 minutes input rate 0 bits/sec,0 bytes/sec, 0 frames/sec
    5 minutes output rate 0 bits/sec,0 bytes/sec, 0 frames/sec
      7047445326214 frames input,13677158732739772 bytes
        1370 discards,2624 errors                                
        1248 invalid CRC/FCS,0 unknown class 
        0 too long,6 too short
      2274764298912 frames output,3998839305943640 bytes
        505582 discards,0 errors       <<<<<< Output discards increasing
      4 input OLS,6  LRR,3 NOS,0 loop inits
      12 output OLS,6 LRR, 1 NOS, 0 loop inits
    Last clearing of "show interface" counters  :never
</pre>

Note: In the reported case, the port that failed during ISSU was in "Error disabled" prior to the ISSU. The ISSU process itself
reinitialized the port and brought it up. However, since there was still an underlying physical link issue the port failed
quickly do to " bit error rate too high". Reference the following bug for more information on an  "Error disabled" port
being reinitialized during ISSU:
CSCuq78930 Error disabled ports reinitialized after supervisor switchover

Conditions:
Ongoing ISSU or ISSD.
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.