[c-nsp] HDLC Keepalive time mismatch & T1 bouncing

Eric Cables ecables at gmail.com
Thu Aug 16 14:19:55 EDT 2012


I'm hoping someone in the community can draw from their experience and
assist.  I am extending a T1 using a pair of TC Communications 1630
units, and on the far end is a Cisco 1941W router.  When I connect the
router at the far end my T1 continuously bounces, with debug output as
follows:

Aug 16 09:59:57.847 PST: Serial0/1/0:0 - Keepalive time mismatch -
should be 10 secs, is 7
Aug 16 09:59:58.103 PST: Serial0/1/0:0: HDLC myseq 2, mineseen 17*,
yourseen 1345133287, line down
Aug 16 10:00:08.103 PST: Serial0/1/0:0: HDLC myseq 3, mineseen 17*,
yourseen 1345133288, line up
Aug 16 10:00:18.103 PST: Serial0/1/0:0: HDLC myseq 4, mineseen 17*,
yourseen 1345133289, line up
Aug 16 10:00:28.103 PST: Serial0/1/0:0: HDLC myseq 5, mineseen 17*,
yourseen 1345133290, line down
Aug 16 10:00:38.103 PST: Serial0/1/0:0: HDLC myseq 6, mineseen 17*,
yourseen 1345133291, line up
Aug 16 10:00:41.847 PST: Serial0/1/0:0 - Keepalive time mismatch -
should be 10 secs, is 7
Aug 16 10:00:48.103 PST: Serial0/1/0:0: HDLC myseq 7, mineseen 17*,
yourseen 1345133292, line up
Aug 16 10:00:53.847 PST: Serial0/1/0:0 - Keepalive time mismatch -
should be 10 secs, is 12

When I connect the 1941W directly to the smartjack it works fine, and
I can pass traffic to the service provider; when I connect the router
at the far end via this T1/fiber extender I get the above.  Has anyone
ever experienced something like this?  It appears that the TC1630 is
mucking things up, but maybe it's a setting on the router that I'm
missing somewhere.

Here is a link to the product detail sheet for the TC1630:
http://www.tccomm.com/Fiber-Optic-Products/default.aspx/Fiber-Optic-Modems/T1-T3-E3-Trunks/31/TC1630R

My configuration is pretty straight forward, and like I said it works
fine when I plug directly into the carrier's jack:
!
card type t1 0 1
controller T1 0/1/0
 cablelength long 0db
 channel-group 0 timeslots 1-24
!
interface Serial0/1/0:0
 ip address 192.168.0.42 255.255.255.252
end
!

Here's output of 'show controllers t1 0/1/0':
T1 0/1/0 is up.
  Applique type is Channelized T1
  Cablelength is long 0db
  No alarms detected.
  alarm-trigger is not set
  Soaking time: 3, Clearance time: 10
  AIS State:Clear  LOS State:Clear  LOF State:Clear
  Version info Firmware: 20100222, FPGA: 13, spm_count = 0
  Framing is ESF, Line Code is B8ZS, Clock Source is Line.
  CRC Threshold is 320. Reported from firmware  is 320.
  Data in current interval (402 seconds elapsed):
     0 Line Code Violations, 3 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 1 Degraded Mins
     1 Errored Secs, 1 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 1:
     16994 Line Code Violations, 11 Path Code Violations
     7 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins
     5 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs, 36 Unavail Secs
  Total Data (last 1 15 minute intervals):
     16994 Line Code Violations, 11 Path Code Violations,
     7 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,
     5 Errored Secs, 0 Bursty Err Secs, 2 Severely Err Secs, 36 Unavail Secs

And output from 'show interface serial 0/1/0:0' (line protocol keeps
bouncing between up/down):
Serial0/1/0:0 is up, line protocol is down
  Hardware is DSX1
  Internet address is 192.168.0.42/30
  MTU 1500 bytes, BW 1536 Kbit/sec, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation HDLC, loopback not set
  Keepalive set (10 sec)
  Last input 00:00:04, output 00:00:01, output hang never
  Last clearing of "show interface" counters 00:08:32
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 15
  Queueing strategy: Class-based queueing
  Output queue: 0/1000/0 (size/max total/drops)
  30 second input rate 0 bits/sec, 0 packets/sec
  30 second output rate 0 bits/sec, 0 packets/sec
     60 packets input, 1340 bytes, 0 no buffer
     Received 60 broadcasts (0 IP multicasts)
     2 runts, 0 giants, 0 throttles
     16 input errors, 16 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     173 packets output, 24080 bytes, 0 underruns
     0 output errors, 0 collisions, 16 interface resets
     2 unknown protocol drops
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions
  Timeslot(s) Used:1-24, SCC: 0, Transmitter delay is 0 flags

Any help is appreciated.

-- Eric Cables


More information about the cisco-nsp mailing list