Solved

Cisco 1720 keeps loosing conectivity

Posted on 2007-03-19
6
281 Views
Last Modified: 2010-04-17
I have a cisco 1720 router with a csu/dsu card.  We use the router to connect to our wan and configure our VOIP phones.  Lately, the router has been loosing contectivity intermittely.  It will be down for about 10 seconds, just long enough to knock the phones out and know them off of an application that we use.  Does anyone have any idea why this is happening or how to prevent it.

The frequency has increased since they replaced a transformer on the main power line.

Nancy
0
Comment
Question by:Nancy Villa
  • 3
  • 3
6 Comments
 
LVL 13

Expert Comment

by:Dr-IP
ID: 18748678
Do you have the router on a UPS? Have you checked the AC line voltage?
0
 

Author Comment

by:Nancy Villa
ID: 18750004
I will check that as soon as I can get a key.  It happened again but the router didn't reset or reboot.  However I do see errors on the serial interface.  I don't know if this is related.

Serial0 is up, line protocol is up
  Hardware is PQUICC with Fractional T1 CSU/DSU
  Internet address is 192.168.1.18/30
  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
     reliability 255/255, txload 17/255, rxload 48/255
  Encapsulation HDLC, loopback not set
  Keepalive set (10 sec)
  Last input 00:00:04, output 00:00:00, output hang never
  Last clearing of "show interface" counters 3d00h
  Input queue: 0/75/0 (size/max/drops); Total output drops: 718
  Queueing strategy: priority-list 1
  Output queue (queue priority: size/max/drops):
     high: 0/20/0, medium: 0/40/0, normal: 0/60/0, low: 0/80/0
  5 minute input rate 294000 bits/sec, 74 packets/sec
  5 minute output rate 108000 bits/sec, 64 packets/sec
     3807237 packets input, 882801182 bytes, 0 no buffer
     Received 30530 broadcasts, 0 runts, 48 giants, 0 throttles
     171289 input errors, 47386 CRC, 85882 frame, 0 overrun, 0 ignored, 38016 abort
     3678850 packets output, 522017753 bytes, 0 underruns
     0 output errors, 0 collisions, 14 interface resets
     0 output buffer failures, 0 output buffers swapped out
     24 carrier transitions
     DCD=up  DSR=up  DTR=up  RTS=up  CTS=up
0
 
LVL 13

Accepted Solution

by:
Dr-IP earned 500 total points
ID: 18750780
Do a “show controller T1 0”, I think that's the command for your router, but it might be slightly different depending on the hardware, and post the results. You have had 24 carrier transitions, which is way to many for just 3 days, and indicates to me the line is bouncing.
0
How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

 

Author Comment

by:Nancy Villa
ID: 18751052
Here is the show controller output for the serial interface with integrated T1.   I resent the counters after the last post to so I am re-posting that also;

Serial0 is up, line protocol is up
  Hardware is PQUICC with Fractional T1 CSU/DSU
  Internet address is 192.168.1.18/30
  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
     reliability 255/255, txload 8/255, rxload 22/255
  Encapsulation HDLC, loopback not set
  Keepalive set (10 sec)
  Last input 00:00:01, output 00:00:00, output hang never
  Last clearing of "show interface" counters 02:01:31
  Input queue: 0/75/0 (size/max/drops); Total output drops: 0
  Queueing strategy: priority-list 1
  Output queue (queue priority: size/max/drops):
     high: 0/20/0, medium: 0/40/0, normal: 0/60/0, low: 0/80/0
  5 minute input rate 134000 bits/sec, 21 packets/sec
  5 minute output rate 52000 bits/sec, 20 packets/sec
     408311 packets input, 160212414 bytes, 0 no buffer
     Received 851 broadcasts, 0 runts, 1 giants, 0 throttles
     815 input errors, 211 CRC, 369 frame, 0 overrun, 0 ignored, 235 abort
     386723 packets output, 86482739 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions
     DCD=up  DSR=up  DTR=up  RTS=up  CTS=up


Interface Serial0
Hardware is PowerQUICC MPC860 with Integrated FT1 CSU/DSU module
 TX and RX clocks detected.
idb at 0x808084C4, driver data structure at 0x8080DA3C
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]=0x00365F80, Pending [CIPR]=0x04008000
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]=0x0E00E
       [PBODR]=0x0000E, [PBDAT]=0x0047C
Port C [PCDIR]=0x000, [PCPAR]=0x000
       [PCSO]=0x020,  [PCDAT]=0xFCC, [PCINT]=0x000
Receive Ring
        rmd(FF002230): status 9000 length 1A9 address D29664
        rmd(FF002238): status 9000 length 11E address D234E4
        rmd(FF002240): status 9000 length 3A address D25BE4
        rmd(FF002248): status 9000 length 3E address D2A364
        rmd(FF002250): status 9000 length 11E address D26F64
        rmd(FF002258): status 9000 length 11E address D23B64
        rmd(FF002260): status 9000 length 11E address D282E4
        rmd(FF002268): status 9000 length 11E address D28964
        rmd(FF002270): status 9000 length 11E address D268E4
        rmd(FF002278): status 9000 length 11E address D29CE4
        rmd(FF002280): status 9000 length 11E address D241E4
        rmd(FF002288): status 9000 length 11E address D26264
        rmd(FF002290): status 9000 length 45 address D2B064
        rmd(FF002298): status 9000 length 11E address D275E4
        rmd(FF0022A0): status 9000 length 2E address D27C64
        rmd(FF0022A8): status B000 length 2E address D2A9E4
Transmit Ring
        tmd(FF0022B0): status 5C00 length 11C address D05AEA
        tmd(FF0022B8): status 5C00 length 11C address D126EA
        tmd(FF0022C0): status 5C00 length 11C address D0DA6A
        tmd(FF0022C8): status 5C00 length 11C address D0ED8A
        tmd(FF0022D0): status 5C00 length 11C address D113CA
        tmd(FF0022D8): status 5C00 length 32 address D1A00A
        tmd(FF0022E0): status 5C00 length 11C address D1B98A
        tmd(FF0022E8): status 5C00 length 3C address D1208A
        tmd(FF0022F0): status 5C00 length 32 address D0A10A
        tmd(FF0022F8): status 5C00 length 32 address D0BA8A
        tmd(FF002300): status 5C00 length 32 address D1070A
        tmd(FF002308): status 5C00 length 11C address D0746A
        tmd(FF002310): status 5C00 length 11C address D0F3EA
        tmd(FF002318): status 5C00 length 11C address D100AA
        tmd(FF002320): status 5C00 length 11C address D0812A
        tmd(FF002328): status 7C00 length 11C address D0ADCA

SCC GENERAL PARAMETER RAM (at 0xFF003C00)
Rx BD Base [RBASE]=0x2230, Fn Code [RFCR]=0x18
Tx BD Base [TBASE]=0x22B0, Fn Code [TFCR]=0x18
Max Rx Buff Len [MRBLR]=1548
Rx State [RSTATE]=0x18008440, BD Ptr [RBPTR]=0x22A8
Tx State [TSTATE]=0x18000548, BD Ptr [TBPTR]=0x22D8

SCC HDLC PARAMETER RAM (at 0xFF003C38)
CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8
Errors: CRC [CRCEC]=215, Aborts [ABTSC]=238, 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]=39484
User-defined Address 0000/0000/0000/0000
User-defined Address Mask 0x0000


buffer size 1524

PowerQUICC SCC specific errors:
58075 input aborts on receiving flag sequence
0 throttles, 0 enables
0 overruns
0 transmitter underruns
0 transmitter CTS losts
0
 
LVL 13

Expert Comment

by:Dr-IP
ID: 18751767
What about a "show controllers T1", or is that what you got from it? Because I am used to getting something like this below. This was from an E1, but it’s very similar to a T1.  

Bru#show controllers e1
E1 0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  Version info of Slot 0:  HW: 2, Firmware: 4, PLD Rev: 2
Manufacture Cookie is not programmed.
Framing is CRC4, Line Code is HDB3, Clock Source is Line Primary.
Data in current interval (251 seconds elapsed):
  0 Line Code Violations, 0 Path Code Violations
  0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
  0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
  0 Line Code Violations, 0 Path Code Violations,
  0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
  0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
E1 1 is down.
  Applique type is Channelized E1 - balanced
  Transmitter is sending remote alarm.
  Receiver has loss of signal.
  Version info of Slot 0:  HW: 2, Firmware: 4, PLD Rev: 2
Manufacture Cookie is not programmed.
Framing is CRC4, Line Code is HDB3, Clock Source is Line Secondary.    
 Data in current interval (200 seconds elapsed):
  0 Line Code Violations, 0 Path Code Violations
  0 Slip Secs, 200 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
  0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 200 Unavail Secs
Total Data (last 24 hours)
  0 Line Code Violations, 0 Path Code Violations,
  0 Slip Secs, 86400 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
  0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 86400 Unavail Secs

E1 2 is administratively down.
Applique type is Channelized E1 - balanced
Transmitter is sending remote alarm.
Receiver has loss of signal.
Version info of Slot 0:  HW: 2, Firmware: 4, PLD Rev: 2
 
Manufacture Cookie is not programmed.
 
Framing is CRC4, Line Code is HDB3, Clock Source is Internal.
Data in current interval (249 seconds elapsed):
  0 Line Code Violations, 0 Path Code Violations
  0 Slip Secs, 249 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
  0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 249 Unavail Secs
Total Data (last 24 hours)
  0 Line Code Violations, 0 Path Code Violations,
  0 Slip Secs, 86400 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
  0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 86400 Unavail Secs
0
 

Author Comment

by:Nancy Villa
ID: 18859238
I opened a case with the provider and it was a bad section of the cable, once they fixed it, the errors went away.
0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

There are two basic ways to configure a static route for Cisco IOS devices. I've written this article to highlight a case study comparing the configuration of a static route using the next-hop IP and the configuration of a static route using an outg…
I recently attended Cisco Live! in Las Vegas, a conference that boasted over 28,000 techies in attendance, and a week of hands-on learning hosted by a solid partner with which Concerto goes to market.  Every year, Cisco displays cutting-edge technol…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now