From: Duy Nguyen (net_port@xxxxxxxxxxx)
Date: Thu Nov 29 2001 - 00:47:03 GMT-3
Could be your ios. I have the 11.2 version and it works fine. This is a
7000 right?
Absolutely Positively Continuously Sincerely,
Duy Nguyen CCNP
net_port@hotmail.com
Cell (817) 707-7451
>From: "Scott Decker" <sdecker@bellsouth.net>
>Reply-To: "Scott Decker" <sdecker@bellsouth.net>
>To: <ccielab@groupstudy.com>
>Subject: Serial encap and clock rate failed HDLC
>Date: Wed, 28 Nov 2001 18:46:12 -0500
>
>Hi gang:
>
>I've solved this issue in my lab already, but I'm wondering if any of
>you can comment on WHY it happened?
>
>Two routers, standard V.35 DCE to DTE on standard serial ports (FSIP-8
>to WIC-1T). If I leave the encap to HDLC and set DCE end to clock rate
>56000, I get the following messages from debug serial events:
>
>Router-C#debug serial int
>Serial network interface debugging is on
>Router-C#debug serial
>4d02h: Illegal HDLC serial type code 776, PC=0x600D56A4
>packet
>4d02h: Serial1/5: HDLC myseq 7, mineseen 0, yourseen 0, line down
>Serial network packets debugging is on
>Router-C#
>4d02h: Illegal HDLC serial type code 776, PC=0x600D56A4
>
>4d02h: Serial1/5: HDLC myseq 8, mineseen 0, yourseen 0, line down
>4d02h: Serial1/5: attempting to restart
>4d02h: Serial1/5: Reset from PC 0x600D7FB4
>4d02h: Illegal HDLC serial type code 776, PC=0x600D56A4
>
>4d02h: Serial1/5: HDLC myseq 9, mineseen 0, yourseen 0, line down
>4d02h: Illegal HDLC serial type code 776, PC=0x600D56A4
>
>4d02h: Serial1/5: HDLC myseq 10, mineseen 0, yourseen 0, line down
>4d02h: Illegal HDLC serial type code 776, PC=0x600D56A4
>
>4d02h: Serial1/5: HDLC myseq 11, mineseen 0, yourseen 0, line down
>4d02h: Illegal HDLC serial type code 776, PC=0x600D56A4
>
>4d02h: Serial1/5: HDLC myseq 12, mineseen 0, yourseen 0, line down
>4d02h: Illegal HDLC serial type code 776, PC=0x600D56A4
>
>4d02h: Serial1/5: HDLC myseq 13, mineseen 0, yourseen 0, line down
>4d02h: Illegal HDLC serial type code 776, PC=0x600D56A4
>
>Changing encap to PPP makes it work fine. And here's the fun part: I
>changed the clock rate to 64000 and it came right up! What gives? It
>doesn't matter really, it only took about 1 minute to t-shoot and fix,
>but it's bugging me.
>
>Sorry to be AR! It's the geek in me, I guess. :-)
>
>Scott
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:25 GMT-3