These are ATM CRC's. You can take a look at each PVC to see if CRC errors
are associated with a specific PVC:
sh atm pvc x/y
Mike
BTW, I do not believe that there is a CRC in a DS3 frame - I think if you
are using ADM - ATM direct mapping
in DS3 M-frame (as opposed to PLCP),
ADM calculates a CRC based on ATM header, but not sure if these CRC's are
reported by the interface.
Mike
From: "james edwards" <hack...@cybermesa.com>
To: <cisc...@puck.nether.net>
Sent: Thursday, January 13, 2005 2:22 PM
Subject: [c-nsp] CRC errors on DS3 interface
If I am seeing DS3 errors on the main interface (PA-A3-T3) are these DS3
CRC's or AAL5 CRC's ?
ATM4/0 is up, line protocol is up
Hardware is ENHANCED ATM PA
Description: Qwest 54/HFGJ/000332//ACSO
MTU 4470 bytes, sub MTU 4470, BW 44210 Kbit, DLY 190 usec,
reliability 255/255, txload 19/255, rxload 5/255
Encapsulation ATM, loopback not set
Encapsulation(s): AAL5
4095 maximum active VCs, 544 current VCCs
VC Auto Creation Disabled.
VC idle disconnect time: 300 seconds
0 carrier transitions
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 2d01h
Input queue: 0/75/16/0 (size/max/drops/flushes); Total output drops: 4
Queueing strategy: Per VC Queueing
5 minute input rate 926000 bits/sec, 500 packets/sec
5 minute output rate 3370000 bits/sec, 716 packets/sec
61096504 packets input, 3481150315 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
5395 input errors, 4286 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
88573704 packets output, 2959003499 bytes, 0 underruns
4 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
6 messages in net.nether.puck.cisco-nsp[c-nsp] CRC errors on DS3 interface
