Carrier transitions and remote alarm on T1
John Sasso
carrier transitions on the serial interface (which is for a T1 that carries
a Frame Relay circuit to our ISP). Also, I noticed the "Remote alarm"
counter in "sh service-module serial0/2" increase. Routers, T1 WICs, cables,
and even smartjacks have been changed out, but to no avail. Our site is
dual-homed, and we are having a problem with the circuit to ISP A; no
problems with ISP B (we have a router for each ISP's circuit). I know it
cannot be our router since if I connect the ISP B router into ISP A's
smartjack, it also starts logging carrier transitions. In fact, this
problem cropped up when my company relocated to another city - still using
the same ISPs but got new 3640 routers. At the old site, our connection to
ISP A were fine (no carrier transitions). Even when I grabbed the old 3640
out of storage from the old site - which I know for a fact never had a
problem - and connected it to ISP A's smartjack, it started logging carrier
transitions!
Spoke with ISP A, local carrier and long-distance carriers. Variety of
loopbacks were done, but all resulted in NO carrier transitions. Very
puzzled and frustrated. ISP A and the carriers have been no help. Could
the reason for the carrier transitions be a T1 timing problem (we've always
gotten the timing from the network)? What would the increase in "Remote
alarm" counter indicate? Any suggestions would be greatly appreciated.
--john
Dave Phelps
With frame-relay, you won't get carrier transitions unless the problem is
a local loop problem. Who you report it to depends on who you pay for the
circuit. The local loop is most likely the responsibility of the local
ILEC. Unfortunately, you can't report the trouble directly to them, you
have to report the trouble to the carrier that provisioned the circuit
(the carrier that you pay for the circuit), and they will report it to
the ILEC.
You mention timing problems also. Can you post a sh ser s0/2?
In article <Q7oV7.26213$Bd.72...@typhoon.nyroc.rr.com>,
jsas...@nycap.rr.com says...
--
Dave Phelps
Phone Masters Ltd.
deadspam=tippenring
John Sasso
output (latter is just after I shut down the interface, as the bouncing was
causing route issues). BTW, note in the second output the Remote alarm
counter that increments. I read that this increments when a Yellow Alarm is
encountered. Can this help me here?
gateway#sh interface serial0/2
Serial0/2 is administratively down, line protocol is down
Hardware is DSCC4 with integrated T1 CSU/DSU
MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,
reliability 254/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY IETF, loopback not set
Keepalive set (10 sec)
LMI enq sent 54, LMI stat recvd 52, LMI upd recvd 0, DTE LMI down
LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE
Broadcast queue 0/64, broadcasts sent/dropped 23/0, interface broadcasts 0
Last input 01:13:07, output 01:13:06, output hang never
Last clearing of "show interface" counters 01:22:35
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/4/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 1152 kilobits/sec
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
15931 packets input, 7028207 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 1 abort
13331 packets output, 1682368 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
8 carrier transitions
DCD=up DSR=up DTR=down RTS=down CTS=up
gateway#sh service-module serial0/2
Module type is T1/fractional
Hardware revision is 0.88, Software revision is 0.2,
Image checksum is 0x70F47262, Protocol revision is 0.1
Transmitter is sending AIS.
Receiver has no alarms.
Framing is ESF, Line Code is B8ZS, Current clock source is line,
Fraction has 24 timeslots (64 Kbits/sec each), Net bandwidth is 1536
Kbits/sec.
Last user loopback performed:
no loopback
duration 00:00:25
Last module self-test (done at startup): Passed
Last clearing of alarm counters 21:49:56
loss of signal : 1, last occurred 21:49:56
loss of frame : 1, last occurred 21:49:56
AIS alarm : 0,
Remote alarm : 5, last occurred 21:27:04
Module access errors : 0,
Total Data (last 96 15 minute intervals):
719 Line Code Violations, 1035 Path Code Violations
49 Slip Secs, 1091 Fr Loss Secs, 55 Line Err Secs, 18 Degraded Mins
7 Errored Secs, 4 Bursty Err Secs, 5 Severely Err Secs, 1087 Unavail
Secs
Data in current interval (68 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
"Dave Phelps" <tippe...@deadspam.com> wrote in message
news:MPG.168fdd357...@news.charter.net...
Dave Phelps
AMI rather than B8ZS)? That's my first impression. Also, are you sure
you're frame circuit is provisioned for full T1 and not fractional?
You are getting a LOT of T1 carrier errors.
You should see no errors. Here is sh ser s 1/0 from one of mine...
Module type is T1/fractional
Hardware revision is 0.96, Software revision is 1.09,
Image checksum is 0xE4616EAD, Protocol revision is 0.1
Receiver has no alarms.
Framing is ESF, Line Code is B8ZS, Current clock source is line,
Fraction has 24 timeslots (64 Kbits/sec each), Net bandwidth is 1536
Kbits/sec.
Last module self-test (done at startup): Passed
Last clearing of alarm counters 1w2d
loss of signal : 0,
loss of frame : 0,
AIS alarm : 0,
Remote alarm : 0,
Module access errors : 0,
Total Data (last 96 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
Data in current interval (663 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
In article <oarV7.26286$Bd.74...@typhoon.nyroc.rr.com>,
jsas...@nycap.rr.com says...