I am trying to work on the input errors and CRCs on the second interface below. The only difference I can see is the queueing strategy and the autovc creation on the second interface. The IOS for the top router is 12.2(8)T5 and the second one is 12.3(1).
ATM1/0 is up, line protocol is up
Hardware is ENHANCED ATM PA
MTU 4470 bytes, sub MTU 4470, BW 40704 Kbit, DLY 190 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
4095 maximum active VCs, 85 current VCCs
VC idle disconnect time: 300 seconds
2 carrier transitions
Last input 00:00:04, output 00:00:00, output hang never
Last clearing of "show interface" counters 7w1d
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 71755
the CRC error counter shown in this command is AAL 5 errors , what happens is you exceed your contracted rate and some cells are dropped. When the SAR is reassembling the cells in to ip packets there is some cells missing and the IP packet fails the CRC check. hence the crc counter increments ,
The only thing is that the crc's that are listed under your PVC does not match what your interface shows . Did you clear the counters prior to collecting these stats ?
You may want to look at the pvc's on the remote side also.
most of the time you can fix this issue by applying PCR & SCR values on the ATM PVC
I was just using 6000 as an example , you should traffic shape each side to match your contracted rate . This way you do not exceed your contracted rate , If you do not exceed your contracted rate then you will not get your cells tagged . refer to this URL
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...