Constant errors on WAN interface

Unanswered Question
Mar 3rd, 2009

I receive constant errors on the WAN interface, I have completely replaced the router, however still see errors. Telcom says the circuit is fine, I not sure.

Could this be a result of an overscribed T-1 circuit?

Ver:Cisco Internetwork Operating System Software

IOS (tm) C2600 Software (C2600-IPBASE-M), Version 12.3(6a), RELEASE SOFTWARE (fc4)

Copyright (c) 1986-2004 by cisco Systems, Inc.

Compiled Fri 02-Apr-04 19:17 by kellythw

Image text-base: 0x80008098, data-base: 0x80ECF498

ROM: System Bootstrap, Version 12.2(8r) [cmong 8r], RELEASE SOFTWARE (fc1)

Output:Serial0/0 is up, line protocol is up

Hardware is PQUICC with Fractional T1 CSU/DSU

Description: $ES_WAN$$FW_OUTSIDE$

Internet address is 192.168.179.14/28

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation PPP, LCP Open

Open: IPCP, loopback not set

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters 2d10h

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 3

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 1000 bits/sec, 1 packets/sec

5 minute output rate 1000 bits/sec, 2 packets/sec

4306351 packets input, 2388270494 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

20541 input errors, 645 CRC, 19220 frame, 0 overrun, 0 ignored, 676 abort

2329135 packets output, 149119737 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

2 carrier transitions

DCD=up DSR=up DTR=up RTS=up CTS=up

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Adam Frederick Tue, 03/03/2009 - 11:07

You could try a 12.4 IOS image as I've seen bugs in IOS' with certain VWIC/WIC cards.

On a different note, I see you cleared the counters 2 days ago. The errors on your interface really aren't that significant over that time frame.

Are you experiencing any data loss? Timeouts?

Also, I show 2 carrier transitions, those can usually be blamed on the carrier depending on setup.

Could you print the info from your t1 controller so we can see exact error info?

FWWITINET Tue, 03/03/2009 - 11:26

Here is the print out of "sh cont serial":

sh contr serial0/0

Interface Serial0/0

Hardware is PowerQUICC MPC860 with Integrated FT1 CSU/DSU module

TX and RX clocks detected.

idb at 0x8198F2B8, driver data structure at 0x81997054

SCC Registers:

General [GSMR]=0x2:0x00000030, Protocol-specific [PSMR]=0x8

Events [SCCE]=0x0000, Mask [SCCM]=0x001F, Status [SCCS]=0x06

Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E

Interrupt Registers:

Config [CICR]=0x00367F80, Pending [CIPR]=0x00008000

Mask [CIMR]=0x40204000, In-srv [CISR]=0x00000000

Command register [CR]=0x600

Port A [PADIR]=0x0000, [PAPAR]=0xFFFF

[PAODR]=0x0000, [PADAT]=0xE7FC

Port B [PBDIR]=0x0180F, [PBPAR]=0x0000E

[PBODR]=0x00000, [PBDAT]=0x3E77D

Port C [PCDIR]=0x00C, [PCPAR]=0x000

[PCSO]=0x020, [PCDAT]=0xFC2, [PCINT]=0x00F

Receive Ring

rmd(680126B0): status 9000 length 34 address 5D6C424

rmd(680126B8): status 9000 length 34 address 5D6AA24

rmd(680126C0): status 9000 length 34 address 5D6FEA4

rmd(680126C8): status 9000 length 34 address 5D6CAA4

rmd(680126D0): status 9000 length 36 address 5D6CAA4

rmd(680126D8): status 9000 length 34 address 5D6D124

rmd(680126E0): status 9000 length 34 address 5D6A3A4

rmd(680126E8): status 9000 length 36 address 5D6BDA4

rmd(680126F0): status 9000 length 124 address 5D6D7A4

rmd(680126F8): status 9000 length 5E2 address 5D6EB24

rmd(68012700): status 9000 length 5E2 address 5D69D24

rmd(68012708): status 9000 length 31A address 5D6E4A4

rmd(68012710): status 9000 length 34 address 5D689A4

rmd(68012718): status 9000 length 34 address 5D6F1A4

rmd(68012720): status 9000 length E address 5D70524

rmd(68012728): status 9000 length 4A address 5D68324

rmd(68012730): status 9000 length 34 address 5D6DE24

rmd(68012738): status 9000 length 34 address 5D696A4

rmd(68012740): status 9000 length 34 address 5D66924

rmd(68012748): status 9000 length 34 address 5D67624

rmd(68012750): status 9000 length 34 address 5D6B724

rmd(68012758): status 9000 length 36 address 5D6F824

rmd(68012760): status 9000 length 34 address 5D662A4

rmd(68012768): status B000 length 34 address 5D66FA4

Transmit Ring

tmd(68012770): status 5C00 length 244 address 5C04594

tmd(68012778): status DC00 length 244 address 5C04BD4

tmd(68012780): status 5C00 length EF address 5DA2554

tmd(68012788): status 5C00 length 2C address 5D1D06A

tmd(68012790): status 5C00 length C address 5D6DE24

tmd(68012798): status 5C00 length 2C address 5D1A96A

tmd(680127A0): status 5C00 length 34 address 5D2046A

tmd(680127A8): status 5C00 length 2C address 5D2936A

tmd(680127B0): status 5C00 length 2C address 5D376EA

tmd(680127B8): status 5C00 length 34 address 5D439EA

tmd(680127C0): status 5C00 length 2C address 5D3636A

tmd(680127C8): status 5C00 length 2C address 5D3086A

tmd(680127D0): status 5C00 length C9 address 5D28CEA

tmd(680127D8): status 5C00 length 2C address 5D42CEA

tmd(680127E0): status 5C00 length 2C address 5D3AAEA

tmd(680127E8): status 7C00 length 2C address 5D25F6A

tx_limited=0(16)

SCC GENERAL PARAMETER RAM (at 0x68013C00)

Rx BD Base [RBASE]=0x26B0, Fn Code [RFCR]=0x18

Tx BD Base [TBASE]=0x2770, Fn Code [TFCR]=0x18

Max Rx Buff Len [MRBLR]=1548

Rx State [RSTATE]=0x18008440, BD Ptr [RBPTR]=0x2740

Tx State [TSTATE]=0x18000548, BD Ptr [TBPTR]=0x27A0

SCC HDLC PARAMETER RAM (at 0x68013C38)

CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8

Errors: CRC [CRCEC]=1326, Aborts [ABTSC]=1733, Discards [DISFC]=0

Nonmatch Addr Cntr [NMARC]=0

Retry Count [RETRC]=0

Max Frame Length [MFLR]=1608

Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=38554

User-defined Address 0000/0000/0000/0000

User-defined Address Mask 0x0000

buffer size 1524

PowerQUICC SCC specific errors:

1102 input aborts on receiving flag sequence

0 throttles, 0 enables

0 overruns

0 transmitter underruns

0 transmitter CTS losts

631 aborted short frames

WAT_Sec_Cisco1841_01#

Paolo Bevilacqua Tue, 03/03/2009 - 12:11

Hi, despite whatever telco swears, it's a faulty circuit. Have them test it using a BERT generator in front of you.

FWWITINET Tue, 03/03/2009 - 12:13

Is that from past experience or from my description and past experience?

Leo Laohoo Tue, 03/03/2009 - 12:46

Paulo is right. Carriers will always swear by their mother/grandmother that their gears are OK ... until one demands a Bit Error Rate (BER) test.

Paolo Bevilacqua Tue, 03/03/2009 - 13:18

Hi,

22 years of experience of which almost 10 at cisco, in multiple countries.

And I've heard telcos "lying" at least once a week.

Actually it's not that they lie purposely, it's just that they think they know better.

Actions

This Discussion