cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Join Customer Connection to register!
274
Views
5
Helpful
1
Replies
David A.
Beginner

T1 Circuit Bouncing

Hello,

 

I have a bundled T1 circuit that keeps bouncing.. I was hoping to narrow it down a further by determining if I am facing a hardware issue, or if this is more service provider related. Any input on this is appreciated.

 

Here is the output from the show controllers t1 command:

T1 0/1/0 is up.
Applique type is Channelized T1
Cablelength is long gain36 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Framing is ESF, FDL is ansi, Line Code is B8ZS, Clock Source is Line.
Data in current interval (824 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, 204 Path Code Violations,
0 Slip Secs, 7066 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
41 Errored Secs, 8 Bursty Err Secs, 33 Severely Err Secs, 7054 Unavail Secs
T1 0/1/1 is up.
Applique type is Channelized T1
Cablelength is long gain36 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Framing is ESF, FDL is ansi, Line Code is B8ZS, Clock Source is Line.
Data in current interval (823 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, 159 Path Code Violations,
1 Slip Secs, 7066 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
30 Errored Secs, 8 Bursty Err Secs, 22 Severely Err Secs, 7063 Unavail Secs
T1 0/1/2 is up.
Applique type is Channelized T1
Cablelength is long gain36 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Framing is ESF, FDL is ansi, Line Code is B8ZS, Clock Source is Line.
Data in current interval (822 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, 105 Path Code Violations,
2 Slip Secs, 7077 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
31 Errored Secs, 12 Bursty Err Secs, 18 Severely Err Secs, 7097 Unavail Secs

 

Here is the output from the show logs command:

*Jan 1 19:48:44.550: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
*Jan 1 19:48:44.562: %BGP-5-NBR_RESET: Neighbor 10.10.4.50 reset (Interface flap)
*Jan 1 19:48:44.565: %LINK-3-UPDOWN: Interface Multilink1, changed state to down
*Jan 1 19:48:44.571: %BGP-5-ADJCHANGE: neighbor 10.10.4.50 Down Interface flap
*Jan 1 19:48:44.571: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.4.50 IPv4 Unicast topology base removed from session Interface flap
*Jan 1 20:06:27.957: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to up
*Jan 1 20:06:27.962: %CONTROLLER-5-UPDOWN: Controller T1 0/1/1, changed state to up
*Jan 1 20:06:28.954: %CONTROLLER-5-UPDOWN: Controller T1 0/1/2, changed state to up
*Jan 1 20:06:29.958: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to up
*Jan 1 20:06:29.962: %LINK-3-UPDOWN: Interface Serial0/1/1:0, changed state to up
*Jan 1 20:06:30.956: %LINK-3-UPDOWN: Interface Serial0/1/2:0, changed state to up
*Jan 1 20:06:38.357: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up
*Jan 1 20:06:38.358: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:0, changed state to up
*Jan 1 20:06:38.375: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
*Jan 1 20:06:38.377: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
*Jan 1 20:06:39.028: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/2:0, changed state to up
*Jan 1 20:06:42.670: %BGP-5-NBR_RESET: Neighbor 10.10.4.50 active reset (BGP Notification sent)
*Jan 1 20:06:42.670: %BGP-5-ADJCHANGE: neighbor 10.10.4.50 Up
*Jan 1 20:46:31.862: %CONTROLLER-5-UPDOWN: Controller T1 0/1/1, changed state to down
*Jan 1 20:46:31.867: %CONTROLLER-5-UPDOWN: Controller T1 0/1/2, changed state to down
*Jan 1 20:46:32.857: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to down
*Jan 1 20:46:33.864: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:0, changed state to down
*Jan 1 20:46:33.864: %LINK-3-UPDOWN: Interface Serial0/1/1:0, changed state to down
*Jan 1 20:46:33.877: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/2:0, changed state to down
*Jan 1 20:46:33.879: %LINK-3-UPDOWN: Interface Serial0/1/2:0, changed state to down
*Jan 1 20:46:34.857: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to down
*Jan 1 20:46:34.857: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to down
*Jan 1 20:46:34.861: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
*Jan 1 20:46:34.869: %BGP-5-NBR_RESET: Neighbor 10.10.4.50 reset (Interface flap)
*Jan 1 20:46:34.870: %LINK-3-UPDOWN: Interface Multilink1, changed state to down
*Jan 1 20:46:34.876: %BGP-5-ADJCHANGE: neighbor 10.10.4.50 Down Interface flap
*Jan 1 20:46:34.876: %BGP_SESSION-5-ADJCHANGE: neighbor 10.10.4.50 IPv4 Unicast topology base removed from session Interface flap
*Jan 1 21:04:13.113: %CONTROLLER-5-UPDOWN: Controller T1 0/1/0, changed state to up
*Jan 1 21:04:13.118: %CONTROLLER-5-UPDOWN: Controller T1 0/1/1, changed state to up
*Jan 1 21:04:15.113: %LINK-3-UPDOWN: Interface Serial0/1/0:0, changed state to up
*Jan 1 21:04:15.118: %LINK-3-UPDOWN: Interface Serial0/1/1:0, changed state to up
*Jan 1 21:04:23.109: %CONTROLLER-5-UPDOWN: Controller T1 0/1/2, changed state to up
*Jan 1 21:04:25.110: %LINK-3-UPDOWN: Interface Serial0/1/2:0, changed state to up
*Jan 1 21:04:25.204: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:0, changed state to up
*Jan 1 21:04:25.205: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:0, changed state to up
*Jan 1 21:04:25.226: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
*Jan 1 21:04:25.228: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
*Jan 1 21:04:31.731: %BGP-5-ADJCHANGE: neighbor 10.10.4.50 Up
*Jan 1 21:04:33.204: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/2:0, changed state to up

1 REPLY 1
Leo Laohoo
VIP Community Legend


@David A.  wrote:

Total Data (last 24 hours)
0 Line Code Violations, 204 Path Code Violations,
0 Slip Secs, 7066 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
41 Errored Secs, 8 Bursty Err Secs, 33 Severely Err Secs, 7054 Unavail Secs


Contact the ISP and get a BER (bit error rate) test.  

Understanding the show controllers e1 Command


@David A.  wrote:

*Jan 1 20:46:31.862: %CONTROLLER-5-UPDOWN: Controller T1 0/1/1, changed state to down
*Jan 1 20:46:31.867: %CONTROLLER-5-UPDOWN: Controller T1 0/1/2, changed state to down


The links go down simultaneously.  This is an ISP-side issue.