HDLC invalid serial type code message

I'm trying to connect a WIC-1T on 3660 (IOS 12.1) to a WIC-1T on a 2811 (IOS 12.3) via a fraction of a T-1. Our interal telco guys are using some MCK multiplexers to peel off 8 channels for voice and giving me the rest for data (using V.35 connections to the WICs) so we should have a data rate of 1024000.

On the 2811, I get this:

Serial0/0/0 is up, line protocol is down Hardware is GT96K Serial Description: WAN connection to main building Internet address is 192.168.3.1/24 MTU 1500 bytes, BW 1544 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 00:00:05, output hang never Last clearing of "show interface" counters never 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/1/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 1158 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 93 packets output, 5613 bytes, 0 underruns 0 output errors, 0 collisions, 21 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

And in debug, I get this:

*May 9 16:09:14.967: Serial0/0/0: attempting to restart *May 9 16:09:14.967: gt96k_mbrd_serial_mode_reg_init:: was DTE, now set to DTE *May 9 16:09:14.967: DTE idb->dte_interface = DTE *May 9 16:09:14.967: Dscc4(0/0): DCD is up. *May 9 16:09:23.967: Serial0/0/0: HDLC myseq 51, mineseen 0, yourseen 0, line down *May 9 16:09:33.967: Serial0/0/0: HDLC myseq 52, mineseen 0, yourseen 0, line down *May 9 16:09:43.967: Serial0/0/0: HDLC myseq 53, mineseen 0, yourseen 0, line down *May 9 16:09:44.967: Serial0/0/0: attempting to restart

On the 3660, I see this:

Serial2/0 is up, line protocol is down Hardware is DSCC4 Serial Internet address is 192.168.3.2/24 MTU 1500 bytes, BW 2048 Kbit, 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:01, output 00:00:06, output hang never Last clearing of "show interface" counters 00:01:46 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/1/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 1536 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 51 packets input, 1122 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 10 packets output, 240 bytes, 0 underruns 0 output errors, 0 collisions, 4 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

And in debug, get this output:

6d05h: Serial2/0: attempting to restart 6d05h: Illegal HDLC serial type code 2609, PC=0x6001C3EC 6d05h: Illegal HDLC serial type code 2609, PC=0x6001C3EC 6d05h: Illegal HDLC serial type code 2609, PC=0x6001C3EC 6d05h: Illegal HDLC serial type code 2609, PC=0x6001C3EC 6d05h: Illegal HDLC serial type code 2609, PC=0x6001C3EC 6d05h: Serial2/0: HDLC myseq 21, mineseen 0, yourseen 0, line down

I thought that on a V.35 interface, the router will set its rate automatically based upon the clocking it sees coming from the DSU/CSU. The available bandwidth on the 2811 sh interface command looks reasonable, but the 3660 is clearly too high. This connection was working until the telco guys started messing with the clocking. From what they are saying, it sounds like the MCK mux by the 2811 is generating clocking, but I am wondering if that is not coming across correctly at the 3660 end. Thoughts?

--Randy--

Reply to
randy.smith
Loading thread data ...

I'll answer my own question just in case someone else runs into this. Ended up the problem was with the T-1. Our telco installed a 2-wire T-1 instead of a 4-wire and that apparently was the source of the problem. Once they switched us to a 4-wire T-1, everything worked fine.

Reply to
randy.smith

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.