Loading...
Loading...
Depending on traffic flow, constant increment of input discards on various interfaces. All traffic, including control-plane packets (e.g. LACP), do not egress interfaces sharing the same port ASIC. -This will result in adjacency loss, LACP suspended interfaces, etc.
Nexus 7000 with F3 Modules -First seen on 6.2(12) with N7K-F348XP-25 module
Reload the module that logged ERR_U_PLEN_MP_N_ZRO_EOS exceptions.
For an egress buffer (EB) to lockup we need a corrupt header with a valid CRC which generally happens on ingress instance. These occurrences are extremely rare. This defect is aimed to provide a hardening mechanism to avoid traffic black hole. If the device in question is impacted by this defect you'll find the following exceptions on the egress module: # show module internal exceptionlog module | i i ERR_U_PLEN_MP Error Description : FLN_QUE_INTR_EB_P4_ERR_U_PLEN_MP_N_ZRO_EOS Error Description : FLN_QUE_INTR_EB_P5_ERR_U_PLEN_MP_N_ZRO_EOS Error Description : FLN_QUE_INTR_EB_P2_ERR_U_PLEN_MP_N_ZRO_EOS Error Description : FLN_QUE_INTR_EB_P3_ERR_U_PLEN_MP_N_ZRO_EOS Error Description : FLN_QUE_INTR_EB_P6_ERR_U_PLEN_MP_N_ZRO_EOS Error Description : FLN_QUE_INTR_EB_P1_ERR_U_PLEN_MP_N_ZRO_EOS Error Description : FLN_QUE_INTR_EB_P0_ERR_U_PLEN_MP_N_ZRO_EOS Error Description : FLN_QUE_INTR_EB_P7_ERR_U_PLEN_MP_N_ZRO_EOS Also, you could see arbiter timeouts on various ingress modules depending on traffic flow: # show module internal exceptionlog module | i i TIMEOUT Error Description : FLN_AX_INT_ERR_TIMEOUT_EXPIRED
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.