[c-nsp] RE: Interfaces going into loop

Joseph Jackson JJackson at nos.com
Thu Jun 23 11:39:17 EDT 2005


Here are the show interfaces for 2 of the interfaces in the multilink that
go down.

The t1s in the multilink (there are 7) are split off of a DS3 that we use
for voice.  3 of the t's NEVER go down while 4 of them go down atleast once
a week.  The t's are all part of the same ds3


Serial3/0 is up, line protocol is down (looped)
  Hardware is M4T
  Description: T1 Las Vegas to New York member of MultiLink 646
  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation PPP, crc 16, loopback not set
  Keepalive set (10 sec)
  Restart-Delay is 0 secs
  LCP REQsent, multilink Closed
  Closed: CDPCP
  Last input 00:00:01, output 00:00:01, output hang never
  Last clearing of "show interface" counters 1w6d
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue :0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     10708661 packets input, 1850413765 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     2434 input errors, 2423 CRC, 0 frame, 9 overrun, 4 ignored, 2 abort
     9923522 packets output, 3434561634 bytes, 0 underruns
     0 output errors, 0 collisions, 1735 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1775 carrier transitions     DCD=up  DSR=up  DTR=up  RTS=up  CTS=up

Serial3/1 is up, line protocol is down (looped)
  Hardware is M4T
  Description: T1 Las Vegas to New York member of MultiLink 646
  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation PPP, crc 16, loopback not set
  Keepalive set (10 sec)
  Restart-Delay is 0 secs
  LCP REQsent, multilink Closed
  Closed: CDPCP
  Last input 00:00:01, output 00:00:01, output hang never
  Last clearing of "show interface" counters 1w6d
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue :0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     5268589 packets input, 911768050 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     3733 input errors, 3679 CRC, 0 frame, 6 overrun, 8 ignored, 48 abort
     5208779 packets output, 4165167690 bytes, 0 underruns
     0 output errors, 0 collisions, 11509 interface resets
     0 output buffer failures, 0 output buffers swapped out
     11547 carrier transitions     DCD=up  DSR=up  DTR=up  RTS=up  CTS=up

-----Original Message-----
From: Andriy A. Yerofyeyev [mailto:andriy.yerofyeyev at gmail.com] 
Sent: Thursday, June 23, 2005 8:11 AM
To: JJackson at nos.com
Subject: Re: Interfaces going into loop

Joseph Jackson wrote:

>I have 7 t1's in a ppp multi link going to a remote site.  Once a week the
>serial interfaces will recivie enough errors from the t's to cause them to
>shutdown and go into loop back.  
>
Are You received errors from particular T1 or your errors came from all 
T1's ?
Can you put here show interfaces after these interfaces going into loop ?

>The telcom provider is currently working on
>the issue but I would still like to ask you all if theres any way I can
keep
>these interfaces from going into loop?  Once they go into loop I have to
set
>the csu (external to the router) into loop and then remove it before the
>interfaces will come out of loop.
>
> 
>
> 
>
>Thanks
>
> 
>
>Joseph
>
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>  
>


More information about the cisco-nsp mailing list