mays at win
Jul 26, 2012, 9:25 AM
Post #1 of 3
(407 views)
Permalink
|
|
Serial interface stuck in "reset" status.
|
|
Okay. Trying to bring up a T1 on a channel on a channelized t3 card in an AS5400. I've done this more than once and have other working T1's on the same t3 card.
I have the config on both ends; it's very simple.
On the AS5400...
controller T1 1/0:26
shutdown
framing esf
channel-group 0 timeslots 1-20
[...]
interface Serial1/0:26:0
description Glass Doctor (K1.HCFU.417839..SC)
no ip address
encapsulation ppp
no cdp enable
ppp multilink
ppp multilink group 180025
One the remote side ...
controller T1 0/0
framing esf
linecode b8zs
channel-group 0 timeslots 1-20 speed 56
[...]
interface Serial0/0:0
no ip address
encapsulation ppp
ppp multilink
ppp multilink group 1
The problem I am having is that the t1 controller seems to come up fine and error free...
ArmoryPl-AS5400#show controller t1 1/0:26
T1 1/0:26 is up.
Applique type is Channelized T1
No alarms detected.
alarm-trigger is not set
Version info of slot 1: HW: 768, PLD Rev: 4
Framer Version: 0x28
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x01,
Board Hardware Version 3.0, Item Number 73-4089-03,
Board Revision B0, Serial Number JAE050301LR,
PLD/ISP Version <unset>, Manufacture Date 18-Jan-2001.
Framing is ESF, Clock Source is Line.
Data in current interval (293 seconds elapsed):
0 Line Code Violations, 1 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
1 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:
... but the serial interface is stuck in "reset" status.
ArmoryPl-AS5400#show int Serial1/0:26:0
Serial1/0:26:0 is reset, line protocol is down
Hardware is DSX1
Description: Glass Doctor (K1.HCFU.417839..SC)
MTU 1500 bytes, BW 1120 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP Closed, multilink Closed
Closed: BACP, loopback not set
Last input never, output never, output hang never
Last clearing of "show interface" counters 13:01:00
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 840 kilobits/sec
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
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Strangely, it stays in reset status even if I turn the t1 down.
ArmoryPl-AS5400#show controller t1 1/0:26
T1 1/0:26 is administratively down.
Applique type is Channelized T1
Transmitter is sending AIS.
Receiver has remote alarm.
alarm-trigger is not set
Version info of slot 1: HW: 768, PLD Rev: 4
Framer Version: 0x28
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x01,
Board Hardware Version 3.0, Item Number 73-4089-03,
Board Revision B0, Serial Number JAE050301LR,
PLD/ISP Version <unset>, Manufacture Date 18-Jan-2001.
Framing is ESF, Clock Source is Line.
Data in current interval (334 seconds elapsed):
0 Line Code Violations, 1 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 1 Degraded Mins
1 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
ArmoryPl-AS5400#show int Serial1/0:26:0
Serial1/0:26:0 is reset, line protocol is down
Hardware is DSX1
Description: Glass Doctor (K1.HCFU.417839..SC)
MTU 1500 bytes, BW 1120 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, LCP Closed, multilink Closed
Closed: BACP, loopback not set
Last input never, output never, output hang never
Last clearing of "show interface" counters 13:05:11
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 840 kilobits/sec
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
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
I tried clear interface Serial1/0:26:0, to no avail. Still in reset status. What exactly does reset status mean and how could one channel on a t3 controller get stuck in that state?
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
|
