This article highlights the meaning of the below syslog message and how to troubleshoot it FABIO_SHIM_AIF_TX_MEM_PROTECT: Detected: AIF Parity
MQSS logs may be seen for EACHIP-based linecards ( MPC7,8,9) for which FPC major error alarm will be set along with this pfe-disable script will triggered to bring down the ports on the affected PFE, to avoid traffic blackholing and cmerror will be set for the MQSS ( memory and queuing sub-system ) block.
Below logs will be seen on the device :
MQSS(1): FABIO: SHIM AIF Tx Protect: Multiple Errors 0x0
Cmerror Op Set: MQSS(1): MQSS(1): FABIO: SHIM AIX Tx Protect: Parity error detected for SHIM asynchronous interface Tx
Below command can be used see active error for MQSS block #start shell pfe network fpc<fpc slot number>#show cmerror module brief
FABIO block is used to carry ingress and egress traffic between the fabric and EA chip. These logs are printed when parity error is detected on the TX AIF ( TX asynchronous interfaces ). TX asynchronous interfaces transfer data from FABIO to the serdes. Errors can also be seen for AIF RX interfaces, which is responsible for transferring data in the reverse direction, from serdes to FABIO. These errors are usually transient in nature. Reboot affected FPC in a service-affecting MW to clear the error and bring up the affected interfaces.If error does not clear after FPC reboot, reach out to JTAC to troubleshoot further.
NA