How to Check for CRC Errors on an Interface
109877
Created On 09/25/18 17:46 PM - Last Modified 07/14/26 08:14 AM
Objective
To identify and diagnose potential physical layer issues, faulty cabling, or hardware defects on Palo Alto Networks device interfaces by checking for Cyclic Redundancy Check (CRC) errors.
Environment
-
Hardware: Palo Alto Networks Next-Generation Firewalls
-
Software: PAN-OS
Procedure
To check for CRC errors across the interfaces on a Palo Alto Networks device, run the following CLI command:
> show system state filter sys.s1.* | match crc
If an interface has experienced CRC errors, the 'bad_crc' counter will appear in the output. For example, the following sample output shows that interface s1.p6 (ethernet1/6) has recorded errors:
sys.s1.p6.detail: {'bad crc': 0x6c1, ...
If the command returns no output, none of the interfaces have encountered CRC errors.
owner: mvenkatesan