02-24-2012 08:28 AM - edited 03-07-2019 05:09 AM
Hi All,
Can some please help us in finding the error here , this is our serial interface which is keep bouncing regularly , our telco provider are not able to see any issues on their end .
==
ukld-pop-e-1> show int serial 6/0:1
Serial6/0:1 is up, line protocol is up
Hardware is PA-MC-8TE1 Plus
Description: BOC-Spoke_LDN/CU-ZAB/CUMV001_2011-2781
Internet address is 21.234.15.25/30
MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec,
reliability 255/255, txload 2/255, rxload 3/255
Encapsulation HDLC, crc 16, loopback not set
Keepalive set (10 sec)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 227902
Queueing strategy: Class-based queueing
Output queue: 0/1000/64/227902 (size/max total/threshold/drops)
Conversations 0/4/256 (active/max active/max total)
Reserved Conversations 2/2 (allocated/max allocated)
Available Bandwidth 0 kilobits/sec
5 minute input rate 32000 bits/sec, 47 packets/sec
5 minute output rate 18000 bits/sec, 14 packets/sec
421016468 packets input, 2193675308 bytes, 0 no buffer
Received 2049546 broadcasts, 13701265 runts, 164 giants, 0 throttles
47499988 input errors, 2259193 CRC, 0 frame, 0 overrun, 0 ignored, 17426852 abort
355412056 packets output, 2922733315 bytes, 0 underruns
0 output errors, 0 collisions, 328 interface resets
0 output buffer failures, 0 output buffers swapped out
107 carrier transitions no alarm present
Timeslot(s) Used:UNFRAMED, transmit delay is 0 flags
ukld-pop-e-1>
Here is the log:
006877: Feb 10 21:56:34.184 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006888: Feb 13 15:05:45.956 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006889: Feb 13 15:06:25.956 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006909: Feb 15 18:31:56.279 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006910: Feb 15 18:34:16.279 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006933: Feb 20 19:20:17.775 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006944: Feb 20 23:26:17.821 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006945: Feb 20 23:29:37.821 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006946: Feb 20 23:30:27.821 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006947: Feb 20 23:43:37.821 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006948: Feb 21 00:05:57.825 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006951: Feb 21 06:41:17.858 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006952: Feb 21 06:41:27.858 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006953: Feb 21 06:51:17.858 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006954: Feb 21 07:02:07.862 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006955: Feb 21 07:06:47.862 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006956: Feb 21 09:54:47.868 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006957: Feb 21 16:27:47.931 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006958: Feb 21 16:30:37.931 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006961: Feb 21 18:20:17.937 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006962: Feb 21 22:34:07.951 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006965: Feb 21 22:39:17.951 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006966: Feb 21 22:55:57.951 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006967: Feb 21 22:59:07.951 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006968: Feb 21 23:23:17.951 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006969: Feb 21 23:40:47.951 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006976: Feb 22 05:59:08.115 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006977: Feb 22 06:12:18.115 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006978: Feb 22 06:22:08.115 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006981: Feb 22 06:42:28.123 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006982: Feb 22 15:06:48.145 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006983: Feb 22 15:55:58.172 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006984: Feb 22 15:56:08.172 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006985: Feb 22 15:57:08.172 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006986: Feb 22 15:58:08.172 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006987: Feb 22 16:16:28.172 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006988: Feb 22 16:29:08.172 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
006991: Feb 23 01:58:38.220 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
006992: Feb 23 03:13:18.252 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
ukld-pop-e-1> show int serial 6/0:1
Serial6/0:1 is up, line protocol is up
Hardware is PA-MC-8TE1 Plus
Description: BOC-Spoke_LDN/CU-ZAB/CUMV001_2011-2781
Internet address is 21.234.15.25/30
MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec,
reliability 255/255, txload 2/255, rxload 3/255
Encapsulation HDLC, crc 16, loopback not set
Keepalive set (10 sec)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 227902
Queueing strategy: Class-based queueing
Output queue: 0/1000/64/227902 (size/max total/threshold/drops)
Conversations 0/4/256 (active/max active/max total)
Reserved Conversations 2/2 (allocated/max allocated)
Available Bandwidth 0 kilobits/sec
5 minute input rate 32000 bits/sec, 47 packets/sec
5 minute output rate 18000 bits/sec, 14 packets/sec
421016468 packets input, 2193675308 bytes, 0 no buffer
Received 2049546 broadcasts, 13701265 runts, 164 giants, 0 throttles
47499988 input errors, 2259193 CRC, 0 frame, 0 overrun, 0 ignored, 17426852 abort
355412056 packets output, 2922733315 bytes, 0 underruns
0 output errors, 0 collisions, 328 interface resets
0 output buffer failures, 0 output buffers swapped out
107 carrier transitions no alarm present
Timeslot(s) Used:UNFRAMED, transmit delay is 0 flags
ukld-pop-e-1>
router1> show int serial 6/0:1
Serial6/0:1 is up, line protocol is up
Hardware is PA-MC-8TE1 Plus
Description: **removed **
Internet address is x.x.x.x
MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec,
reliability 255/255, txload 2/255, rxload 3/255
Encapsulation HDLC, crc 16, loopback not set
Keepalive set (10 sec)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 227902
Queueing strategy: Class-based queueing
Output queue: 0/1000/64/227902 (size/max total/threshold/drops)
Conversations 0/4/256 (active/max active/max total)
Reserved Conversations 2/2 (allocated/max allocated)
Available Bandwidth 0 kilobits/sec
5 minute input rate 32000 bits/sec, 47 packets/sec
5 minute output rate 18000 bits/sec, 14 packets/sec
421016468 packets input, 2193675308 bytes, 0 no buffer
Received 2049546 broadcasts, 13701265 runts, 164 giants, 0 throttles
47499988 input errors, 2259193 CRC, 0 frame, 0 overrun, 0 ignored, 17426852 abort
355412056 packets output, 2922733315 bytes, 0 underruns
0 output errors, 0 collisions, 328 interface resets
0 output buffer failures, 0 output buffers swapped out
107 carrier transitions no alarm present
Timeslot(s) Used:UNFRAMED, transmit delay is 0 flags
== Logs ==
Feb 10 21:56:34.184 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
Feb 13 15:05:45.956 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
Feb 13 15:06:25.956 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
Feb 15 18:31:56.279 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to down
Feb 15 18:34:16.279 PRC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial6/0:1, changed state to up
Feb 20 19:20:17.775 PRC: %LINEPROTO
Solved! Go to Solution.
02-24-2012 01:56 PM
There are 107 carrier transitions and 328 interface resets along wirh a bunch of other errors and output drops that are likely caused by the bouncing circuit. This appears to be a circuit issue - contact your service provider and ask them to perform an intrusive line test as soon as possible. Keep in mind that when they run the intrusive line test, your circuit will be down, so do it after hours.
I've encountered similar issue many, many times where the provider kept telling me it's my equipment problem and their tests were clean, but it always turned out it's a bad connection from the street or at the MPOE. Request them to dispatch a tech to check it out if you know with certainty that your equipment/cable is fine.
02-24-2012 08:38 AM
02-24-2012 01:07 PM
Hi Alex ,
thanks for the response , crc 16 is default setting isnt it ? please also advised it is necessary to have the same crc on both the side?
02-24-2012 08:40 AM
Is your cable good?
Have you tried replacing it?
02-24-2012 01:07 PM
Hi Reza,
yes we have replaced the cable but still flapping
02-24-2012 01:56 PM
There are 107 carrier transitions and 328 interface resets along wirh a bunch of other errors and output drops that are likely caused by the bouncing circuit. This appears to be a circuit issue - contact your service provider and ask them to perform an intrusive line test as soon as possible. Keep in mind that when they run the intrusive line test, your circuit will be down, so do it after hours.
I've encountered similar issue many, many times where the provider kept telling me it's my equipment problem and their tests were clean, but it always turned out it's a bad connection from the street or at the MPOE. Request them to dispatch a tech to check it out if you know with certainty that your equipment/cable is fine.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide