Guest

Preview Tool

Cisco Bug: CSCvv48130 - F3 interfaces goes to "faulty" state because of few new fatal interrupts

Last Modified

Oct 19, 2020

Products (2)

  • CiscoPro Workgroup EtherSwitch Software
  • Cisco Nexus 7000 Series Switches

Known Affected Releases

8.3(2)

Description (partial)

Symptom:
F3 module interfaces might go to faulty state with the below log messages:

Modules reported faulty interfaces:
2020 Jan 26 05:00:47 ZURSWHCDC001A %MODULE-2-MOD_SOMEPORTS_FAILED: Module 4 (Serial number: JAE2141023L) reported failure on ports Ethernet4/3 (Ethernet) due to fatal error in device DEV_FLN_QUE (device error 0xcbe016a7)
2020 Jan 26 05:02:32 ZURSWHCDC001A %MODULE-2-MOD_SOMEPORTS_FAILED: Module 3 (Serial number: JAE21400AC9) reported failure on ports Ethernet3/4 (Ethernet) due to fatal error in device DEV_FLN_QUE (device error 0xcbe016a7)
2020 Jan 26 05:06:58 ZURSWHCDC001A %MODULE-2-MOD_SOMEPORTS_FAILED: Module 2 (Serial number: JAE21400ABW) reported failure on ports Ethernet2/19 (Ethernet) due to fatal error in device DEV_FLN_QUE (device error 0xcbe096a7)


ZURSWHCDC001A-VDC-1# show int status | in faulty
Eth3/9           to ZURSWHCDC105 faulty    f-path    auto    auto    QSFP-40G-SR
Eth3/10          to ZURSWHCDC105 faulty    f-path    auto    auto    QSFP-40G-SR
Eth3/19          to ZURSWHCDC110 faulty    f-path    auto    auto    QSFP-40G-SR
Eth3/20          to ZURSWHCDC110 faulty    f-path    auto    auto    QSFP-40G-SR


exception information --- exception instance 4 ----

Module Slot Number: 3

Device Id         : 190

Device Name       : Flanker Queue Driver

Device Errorcode  : 0xcbe09666

Device ID         : 190 (0xbe)

Device Instance   : 09 (0x09)

Dev Type (HW/SW)  : 06 (0x06)

ErrNum (devInfo)  : 102 (0x66)

System Errorcode  : 0x427a001d fatal error

Error Type        : Minor error

PhyPortLayer      : Ethernet

Port(s) Affected  : Ethernet3/19, Ethernet3/20

Error Description : FLN_QUE_INTR_EB_PAGE_U_FIFO_OVFL

DSAP              : 0 (0x0)

UUID              : 0 (0x0)

Time              : Sun Jul 19 02:46:05 2020

                    (Ticks: 5F13FA3D jiffies)

Conditions:
This can happen in a very corner case when there is a loop of some BUM (Uncredited) traffic in the network.
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.