I have a E1 controller that keeps bouncing.
I suspect a clocking issue or even a hardware problem, but I'm new to WAN support, so I'm looking for some direction to take fault finding.
1-1#sh controllers e1 2/0 br
E1 2/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20050620, FPGA: 15, spm_count = 0
Framing is UNFRAMED, Line Code is HDB3, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Current port master clock: recovered from E1 2/0
Data in current interval (683 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)
39 Line Code Violations, 0 Path Code Violations,
58 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
58 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 280 Unavail Secs
1-1#sh int serial 2/0:0
Serial2/0:0 is up, line protocol is up
Hardware is DSCC4 Serial
Description: Serial Link to R2-1
MTU 1500 bytes, BW 2000 Kbit, DLY 20000 usec,
reliability 255/255, txload 14/255, rxload 13/255
Encapsulation PPP, LCP Open, multilink Open
Link is a member of Multilink bundle Multilink1, 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 23:53:23
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 5250
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 106000 bits/sec, 177 packets/sec
30 second output rate 116000 bits/sec, 171 packets/sec
6144512 packets input, 619546737 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
1005 input errors, 241 CRC, 710 frame, 0 overrun, 0 ignored, 54 abort
6726235 packets output, 1299234004 bytes, 0 underruns
0 output errors, 0 collisions, 21 interface resets
0 output buffer failures, 0 output buffers swapped out
108 carrier transitions
Timeslot(s) Used: UNFRAMED, SCC: 2, Transmitter delay is 0 flags
Solved! Go to Solution.
It looks to me that your problem is at the controller level:
1) Double-check the line coding
I'm not sure if you have this command, but try "sh service-module serial 2/0:0 performance-statistics 1 - 4" and look for "Line Code violations" and "Path Code Violations".
Those parameters might give you and idea of problems with the encoding or the line itself.
Also, you may find some additional information at:
Please rate posts
first of all this is E1 and no T1, then there in "service module commands" for E1 hardware.
Please specify which router and E1 hardware is this, together with the controller config you have currently.
It interfaces with a Digital Radio System - Microwave link.
Interface in question:
3660 Chassis type: ENTERPRISE
4 FastEthernet interfaces
35 Serial interfaces
4 Channelized E1/PRI ports
Cisco IOS Software, 3600 Software (C3660-IS-M), Version 12.3(11)T10, RELEASE SOFTWARE (fc4)
controller E1 2/0
channel-group 0 unframed
description Link to R2-1
ip address XXX.XXX.XXX.XXX 255.255.255.252
ip flow ingress
ip pim sparse-dense-mode
service-policy output R2-1-OUT
ppp multilink fragment delay 10
ppp multilink interleave
ppp multilink group 1
description Serial Link to R2-1
no ip address
ppp multilink group 1
Nov 5 04:27:33: %CONTROLLER-5-UPDOWN: Controller E1 2/0, changed state to down (10 SES)
Nov 5 04:27:35: %LINK-3-UPDOWN: Interface Serial2/0:0, changed state to down
Nov 5 04:27:35: %LINK-3-UPDOWN: Interface Multilink1, changed state to down
Nov 5 04:27:35: %DUAL-5-NBRCHANGE: IP-EIGRP(0) XX: Neighbor XXX.XXX.XXX.XXX (Multilink1) is down: interface down
Nov 5 04:27:35: %PIM-5-NBRCHG: neighbor XXX.XXX.XXX.XXX DOWN on interface Multilink1 (vrf default) non DR
Nov 5 04:27:35: %CONTROLLER-5-UPDOWN: Controller E1 2/0, changed state to up
Nov 5 04:27:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0:0, changed state to down
Nov 5 04:27:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
Nov 5 04:27:37: %LINK-3-UPDOWN: Interface Serial2/0:0, changed state to up
Nov 5 04:27:38: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
Nov 5 04:27:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0:0, changed state to up
Nov 5 04:27:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
Nov 5 04:27:42: %DUAL-5-NBRCHANGE: IP-EIGRP(0) XX: Neighbor XXX.XXX.XXX.XXX (Multilink1) is up: new adjacency
Nov 5 04:28:07: %PIM-5-NBRCHG: neighbor XXX.XXX.XXX.XXX UP on interface Multilink1 (vrf default)
Nov 5 04:54:59: %CONTROLLER-5-UPDOWN: Controller E1 2/0, changed state to down (10 SES)
Nov 5 04:55:00: %CONTROLLER-5-UPDOWN: Controller E1 2/0, changed state to up
not sure why the low rating to my previous post simply asking for a bit more information.
Considering the attitude is not of fair appreciation to contributions made in good will, I wish you good luck with the issue.
I'm extremely sorry paolo, the rating result was a finger slip problem (did not mean to offend), no problem with your response.
But that said, if you are upset over the rating, I'm sorry.
That's life, I'll move on.
Hi, too bad the 'rating' cannot be corrected for mistakes. I take fairness into great consideration, that's all.
Now for the problem, your microwave circuit appears errored. From you side you should:
- check with the circuit provider if you are supposed to provide clock, on one side. If so, configure 'clock internal' under controller E1, unless already configured on the other end.
second, your 3660 might be equipped with a MIX module. If so, heck that you have configured network-clock-participate slot X
network-clock-select E1 X/Y 1 (or other appropraote value).
Failure to get results from the two items above means the circuit is faulty and must be reported as so to the provider.
The current config at both ends is the same (line), I'm new to routers, but I was thinking that one end should at least be internal. (But like you said, depending on what the link should be expecting)
Waiting to hear from microwave system vendors. Will post an update.
Again, your assistance is greatly appreciated.
Confirmed with the Vendor, clocking should at least be internal on one end, line the other.
It now appears we have a Degraded Radio Path.
Thanks very much for your assistance.