If you have not setup traffic shaping properly and you try to push more
traffic over the PVC than what the PVC is actually configured for then that
will show up as a CRC Error. I would verify the CIR and Burst are set right
on the link.
Patrick
-----Original Message-----
From: Carmen Chow
To: cisco-nsp@puck.nether.net
Sent: 2/16/2001 9:41 PM
Subject: [nsp] OverSizedSDU and CrCErrors
Hello,
I got on PA-A3 on VIP2-50 (128M DRAM). There are 3 pvc to diff.
destination.
The first two pvc seems normal and fine but the third one got
oversizedSDU
and Crc Errors as below:-
ATM10/0/0.3: VCD: 103, VPI: 2, VCI: 36, etype:0x800, AAL5 - MUX, Flags:
0x40033
PeakRate: 120000, Average Rate: 80000, Burst Cells: 300, VCmode: 0x0
OAM frequency: 10 second(s), InARP DISABLED
InPkts: 252648441, OutPkts: 564716, InBytes: 2862013575, OutBytes:
185027861
InPRoc: 156262, OutPRoc: 0, Broadcasts: 31837
InFast: 195, OutFast: 5, InAS: 252491984, OutAS: 532874
InPktDrops: 5, OutPktDrops: 0
CrcErrors: 410563, SarTimeOuts: 0, OverSizedSDUs: 15665
OAM F5 cells sent: 3153, OAM cells received: 3138
Status: ACTIVE
I've double checked the ATM PVC details with the end user but still got
increment on CRC and Oversizedsdus intermittently. I've recorded 1000s
on
the counter increment. PVC utilization is around 50% full.
Did anybody have the same experience before? Pls give me some hints.
Thanks.
Regards,
Carmen Chow
Email Address: carmenc@hkt.net
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:29 EDT