Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

e1 coming up but serial interface down

Status
Not open for further replies.

suranji

Technical User
Jul 5, 2002
20
0
0
LK
Hi

We are in the process of configuring channalised E1 for leased circuits for remote locations. We hired a E1 link from a local telco and connected to our E1 interface in a CISCO 3660 router. As the first stage we did a loop (physical loop)test for the e1 interface. Then E1 contoller came up but serial interface not coming up even we loop the serial interface ( in command line) also.

When we connect the e1 to customer site router also we can see e1 coming up and serial interface up but line protocol is down.


e1 controller configuration
=====================================
controller E1 4/0
framing NO-CRC4
channel-group 0 timeslots 1-4
!
=====================================
serial port config
=====================================
interface Serial4/0:0
ip address 172.22.53.1 255.255.255.0
!
=====================================
sh controller information
=====================================
#sh controllers e1 4/0
E1 4/0 is up.
Applique type is Channelized E1 - balanced
No alarms detected.
Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
Data in current interval (260 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
Data in Interval 1:
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
Data in Interval 2:
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
Data in Interval 3:
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
Data in Interval 4:
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
Data in Interval 5:
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 5 15 minute intervals):
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
===========================================================
sh int information
===========================================================
#sh int s4/0:0
Serial4/0:0 is up, line protocol is down
Hardware is DSX1
Internet address is 172.22.53.1/24
MTU 1500 bytes, BW 256 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, loopback not set
Keepalive set (10 sec)
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 602
Queueing strategy: weighted fair
Output queue: 1/1000/64/0 (size/max total/threshold/drops)
Conversations 1/2/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
299 packets output, 8378 bytes, 0 underruns
0 output errors, 0 collisions, 151 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
Timeslot(s) Used:1-4, Transmitter delay is 0 flags
#
===========================================================

please help me to find where is the problem !!

thanks
 
I noticed that you're deriving clock from the line. Anytime that you isolate yourself from the point in the circuit where the timing originates, you need to switch to an internal source. I don't think most Cisco controllers automatically revert to an internal source when line timing isn't present.

May be other issues, but there is one to think about. Are you certain that the telco will be providing timing for the circuit?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top