topic Re: Check error on interface in General Topics

Check error on interface

MohamedSharief — Tue, 15 Nov 2016 11:32:01 GMT

Hi,

I was playing around with CLI and typed the command:

>show system state filter sys.s1.* | match crc

Then got this details:
sys.s1.p5.detail: { 'bad_crc': 0x157352, 'fragments_pkts': 0x1247, 'mac_rcv_error': 0x228b09, 'pkts1024tomax_octets': 0x13e0fad85, 'pkts128to255_octets': 0x237e24c6, 'pkts256to511_octets': 0x31eb1cec, 'pkts512to1023_octets': 0x27d0456f, 'pkts64_octets': 0x12a1280fa, 'pkts65to127_octets': 0x4be94111, }

Can anyone explain what is bad_crc is and how did it happens usually?

Also please share with me any articles or official document to help me identify the logs for PA. e.g. Interface logs, system logs, traffic logs

Regards,

Re: Check error on interface

reaper — Tue, 15 Nov 2016 13:30:42 GMT

Hi Mohamad

a CRC error (cyclic redundancy check) is a collision or transmission error at the interface level, this can be caused by mismatched speed or duplex between the 2 connected interfaces.

fixing the 2 sides so they match up should fix the issue. if it doesn't, there might be noise on the cable if it is not properly shielded, so swapping the cable may help also

for information on log files, please check this page in the admin guide

Re: Check error on interface

TranceforLife — Tue, 15 Nov 2016 16:34:00 GMT

in additional to the comment above we could try to change a cable, if this is an SFP interface, try to replace it