[c-nsp] Help configuring a Cisco 1841 with wic 1DSU-T1-v2

[Vinny Abello]

The Netopia is connected via a T1 to a Coppermountain concentration 
device. That's what CM-HDLC means. I'm guessing Coppermountain's HDLC 
is different than Cisco's which is possibly why you're having 
problems. We used to use quite a few Coppermountain DSLAMs with 
Netopia routers and still have them deployed in many areas. Never got 
or wanted to use a T1 blade in one of them so I can't help you beyond 
that, but the Coppermountain stuff had a limited number of CPE's that 
it worked with. I believe the provider should be able to switch to 
what's called hdlc-ppp on their side. It's probably on just hdlc 
right now. Other encapsulation options include frame relay (1490), 
PPP over frame, ATM, and a bunch of other similar encapsulations I've 
never touched on a Coppermountain. We typically just used RFC1483 
over SDSL lines. As an intermediary solution, see if the Netopia can 
support being changed into a bridge itself. This option is usually 
under the System Configuration menu. Then you can bridge the layer 3 
traffic to your Cisco on an Ethernet port. That could work if you 
just want the functionality of the Cisco and are running out of other 
things to try. Or, you could always simply have the Netopia have 
assigned a /30 to the LAN side and assign the Cisco to the other. Not 
the ideal solution of course... just a suggestion as I know what it's 
like to go around in circles trying to get something to work. Good luck. :)

At 07:46 PM 5/13/2005, William L. Thomson Jr. wrote:
>I have been pulling my hair out for hours trying to configure the darn
>T1 interface. It's a T1 provided by FDN and is a bridged T1. FDN
>provided a Netopia which I am trying to replace with the Cisco.
>
>This is the netopia's config that I am trying to migrate.
>
>          Operation Mode...                  CM-HDLC
>          Line Encoding...                   B8ZS
>          Framing Mode...                    ESF
>          Transmit ANSI PRMs:                No
>          AutoDetect DS0 Channels:           No
>          Number of DS0 Channels:            24
>
>
>          Buildout (-dB)...                  0-0.6
>          Channel Data Rate...               Nx64k
>          Clock Source...                    Network
>          Data Link Encapsulation...         RFC1483
>          RFC1483 Mode...                    Bridged 1483
>          PPP over Ethernet (PPPoE):         Off
>
>
>These are the errors I am getting
>
>
>*May 13 22:23:04.099: Illegal HDLC serial type code 43690, PC=0x61134FD4
>*May 13 22:23:04.951: Serial0/0/0: HDLC myseq 245, mineseen 0, 
>yourseen 0, line down
>*May 13 22:23:05.099: Illegal HDLC serial type code 43690, PC=0x61134FD4
>*May 13 22:23:05.099: Illegal HDLC serial type code 43690, PC=0x61134FD4
>*May 13 22:23:05.867: Serial0/0/0: attempting to restart
>*May 13 22:23:05.867:  gt96k_mbrd_serial_mode_reg_init:: was DTE, 
>now set to DTE
>*May 13 22:23:05.867:  DTE idb->dte_interface = DTE
>*May 13 22:23:05.867: Dscc4(0/0): DCD is up.
>*May 13 22:23:06.099: Illegal HDLC serial type code 43690, PC=0x61134FD4
>*May 13 22:23:06.099: Illegal HDLC serial type code 43690, PC=0x61134FD4
>
>
>
>Now the hdlc ones went away per someones suggestion to use ppp
>encapsulation instead of HDLC.
>
>I am not sure if I need to setup a bridge virtual interface or not.
>
>
>--
>Sincerely,
>William L. Thomson Jr.
>Support Group
>Obsidian-Studios, Inc.
>http://www.obsidian-studios.com
>
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/


Vinny Abello
Network Engineer
Server Management
vinny at tellurian.com
(973)300-9211 x 125
(973)940-6125 (Direct)
PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0  E935 5325 FBCB 0100 977A

Tellurian Networks - The Ultimate Internet Connection
http://www.tellurian.com (888)TELLURIAN

"Courage is resistance to fear, mastery of fear - not absence of 
fear" -- Mark Twain