Test Serial to Serial Connection, Protocol Down...
DComTalk.com Forum Index DComTalk.com
Discussion of VoIP, VPN, Video Conferencen, DSL and other data commucations.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web dcomtalk.com
Test Serial to Serial Connection, Protocol Down...

 
Post new topic   Reply to topic    DComTalk.com Forum Index -> Cisco
Author Message
Scooter
Guest
Posted: Mon Dec 13, 2004 10:38 pm    Post subject: Test Serial to Serial Connection, Protocol Down... Reply with quote
I have a few Cisco routers that I'd like to use to connect up a remote
office via 24 channel T1.

One end is a 4500M with 4port Serial Card that already has 1 T1
Connection. The other end is a 2501.

Inbetween the two routers I have Adtran TSU100 units. Between the two
Adtrans (for testing purposes) I have a T1 crossover cable. The
Cisco's are conneted to the v.34 ports.

Quote:
From either CDU/DSU I can loop up the far end CSU/DSU through the
Crossover cable. So I'm pretty sure that the CDU/DSU to CDU/DSU is

working fine.

On each of the routers I have Line Up, Protocol Down. If I look one
end or the other. The Far End Router shows Protocol Up. So that is
working.

The Config for the Serial interfaces is pretty simple. HDSL Encap (the
Default) and an IP Address. its the same that I have for my other
Serial T1 Connection.

Any Sugggestions?

Thanks,
Scott<-=
Back to top
Ivan Ostreš
Guest
Posted: Tue Dec 14, 2004 12:10 am    Post subject: Re: Test Serial to Serial Connection, Protocol Down... Reply with quote
In article <1102959526.014128.295530@c13g2000cwb.googlegroups.com>,
scott@serra.com says...
Quote:
The Config for the Serial interfaces is pretty simple. HDSL Encap (the

This would be HDLC, wouldn't it?

Quote:
Default) and an IP Address. its the same that I have for my other
Serial T1 Connection.

Any Sugggestions?


I would do 'debug interface serial x/x' (x/x of course is your serial
interface) and see how keepalive packets are going. You will see which
end see which packets and possibly found which side has errors.

--
-Ivan.

*** Use Rot13 to see my eMail address ***
Back to top
Scooter
Guest
Posted: Tue Dec 14, 2004 1:05 am    Post subject: Re: Test Serial to Serial Connection, Protocol Down... Reply with quote
Thank you for the Reply.

Yes. HDLC. Getting my Acronyms Mixed up... HDSL is the T1 Protocol to
the CO.


Debug is below... Here are the Configs for the Serial Ports...

4500M: - (C4500-I-M), Version 12.0(25)
interface Serial0
description T1 Connection to SF - 55 Francisco
ip address 10.254.0.37 255.255.255.252
no ip directed-broadcast
no ip route-cache
no ip mroute-cache

2501: (C2500-I-L), Version 11.2(3)P

interface Serial0
description Connection to Healdsburg - 86HCGS594121PT
ip address 10.254.0.38 255.255.255.252
no ip directed-broadcast
no ip mroute-cache
no ip route-cache

So on the 2501 I'm getting:

5d22h: Serial0: HDLC myseq 50510, mineseen 9, yourseen 11, line down
5d22h: Serial0: attempting to restart
5d22h: HD(0): Reset from 0x3026C1A
5d22h: HD(0): got an interrupt state = 0x814F
5d22h: HD(0): New serial state = 0x014F

5d22h: HD(0): DCD is up.
5d22h: HD(1): New serial state = 0x0600

5d22h: HD(1): Cable is unplugged.
5d22h: HD(0): got an interrupt state = 0x815F
5d22h: HD(0): New serial state = 0x015F

5d22h: HD(0): DCD is up.
5d22h: HD(1): New serial state = 0x0600

5d22h: HD(1): Cable is unplugged.
5d22h: Serial0: HDLC myseq 50511, mineseen 9, yourseen 11, line down
5d22h: Serial0: HDLC myseq 50512, mineseen 9, yourseen 11, line down
5d22h: Serial0: HDLC myseq 50513, mineseen 9, yourseen 11, line down
5d22h: Serial0: attempting to restart
5d22h: HD(0): Reset from 0x3026C1A
5d22h: Serial0: HDLC myseq 50514, mineseen 9, yourseen 11, line down
5d22h: Serial0: HDLC myseq 50515, mineseen 9, yourseen 11, line down
5d22h: Serial0: HDLC myseq 50516, mineseen 9, yourseen 11, line down
5d22h: Serial0: attempting to restart
5d22h: HD(0): Reset from 0x3026C1A
5d22h: HD(0): got an interrupt state = 0x814F
5d22h: HD(0): New serial state = 0x014F

5d22h: HD(0): DCD is up.
5d22h: HD(1): New serial state = 0x0600

5d22h: HD(1): Cable is unplugged.
5d22h: HD(0): got an interrupt state = 0x815F
5d22h: HD(0): New serial state = 0x015F

5d22h: HD(0): DCD is up.
5d22h: HD(1): New serial state = 0x0600

5d22h: HD(1): Cable is unplugged.
5d22h: Serial0: HDLC myseq 50517, mineseen 9, yourseen 11, line down
5d22h: Serial0: HDLC myseq 50518, mineseen 9, yourseen 11, line down
5d22h: Serial0: HDLC myseq 50519, mineseen 9, yourseen 11, line down
5d22h: Serial0: attempting to restart
5d22h: HD(0): Reset from 0x3026C1A




On the 4500M I'm getting: (Serial 0 is the one I'm having issues with)

5d21h: Serial2: HDLC myseq 42767, mineseen 42767*, yourseen 42717, line
up
5d21h: Serial0: attempting to restart
5d21h: MK5(0): Deasserting DTR
5d21h: MK5(0): Deasserting DTR
5d21h: MK5(0): Reset
5d21h: MK5(0): Asserting DTR
5d21h: MK5(0): Deasserting LTST
5d21h: MK5(0): New serial state = 0x6105
5d21h: MK5(0): DCD is up.
5d21h: MK5(0): New serial state = 0x6104
5d21h: MK5(0): DCD is up.
5d21h: Serial0: HDLC myseq 50573, mineseen 0, yourseen 0, line down
5d21h: Serial2: HDLC myseq 42768, mineseen 42768*, yourseen 42718, line
up
5d21h: MK5(0): New serial state = 0x6104
5d21h: MK5(0): DCD is up.
5d21h: Serial0: HDLC myseq 50574, mineseen 0, yourseen 0, line down
5d21h: Serial2: HDLC myseq 42769, mineseen 42769*, yourseen 42719, line
up
5d21h: MK5(0): New serial state = 0x6104
5d21h: MK5(0): DCD is up.
5d21h: Serial0: HDLC myseq 50575, mineseen 0, yourseen 0, line down
5d21h: Serial2: HDLC myseq 42770, mineseen 42770*, yourseen 42720, line
up
5d21h: Serial0: attempting to restart
5d21h: MK5(0): Deasserting DTR
5d21h: MK5(0): Deasserting DTR
5d21h: MK5(0): Reset
5d21h: MK5(0): Asserting DTR
5d21h: MK5(0): Deasserting LTST
5d21h: MK5(0): New serial state = 0x6105
5d21h: MK5(0): DCD is up.
5d21h: MK5(0): New serial state = 0x6104
5d21h: MK5(0): DCD is up.
5d21h: Serial0: HDLC myseq 50576, mineseen 0, yourseen 0, line down
5d21h: Serial2: HDLC myseq 42771, mineseen 42771*, yourseen 42721, line
up
5d21h: MK5(0): New serial state = 0x6104
5d21h: MK5(0): DCD is up.
5d21h: Serial0: HDLC myseq 50577, mineseen 0, yourseen 0, line down
5d21h: Serial2: HDLC myseq 42772, mineseen 42772*, yourseen 42722, line
up
5d21h: MK5(0): New serial state = 0x6104
5d21h: MK5(0): DCD is up.
5d21h: Serial0: HDLC myseq 50578, mineseen 0, yourseen 0, line down
5d21h: Serial2: HDLC myseq 42773, mineseen 42773*, yourseen 42723, line
up
5d21h: Serial0: attempting to restart
5d21h: MK5(0): Deasserting DTR
5d21h: MK5(0): Deasserting DTR
5d21h: MK5(0): Reset
5d21h: MK5(0): Asserting DTR
5d21h: MK5(0): Deasserting LTST
5d21h: MK5(0): New serial state = 0x6105
5d21h: MK5(0): DCD is up.
5d21h: MK5(0): New serial state = 0x6104
5d21h: MK5(0): DCD is up.
5d21h: Serial0: HDLC myseq 50579, mineseen 0, yourseen 0, line down
5d21h: Serial2: HDLC myseq 42774, mineseen 42774*, yourseen 42724, line
up
5d21h: MK5(0): New serial state = 0x6104
5d21h: MK5(0): DCD is up.
Back to top
Ivan Ostreš
Guest
Posted: Tue Dec 14, 2004 1:02 pm    Post subject: Re: Test Serial to Serial Connection, Protocol Down... Reply with quote
In article <1102968322.558736.218350@f14g2000cwb.googlegroups.com>,
scott@serra.com says...
[snip: bunch of output]
Quote:
5d22h: HD(1): Cable is unplugged.


Your router can't talk right on layer 1. It is probably a problem with
cable or clocking. I think that here would help 'show controller serial
0' to determine what is actually wrong.

--
-Ivan.

*** Use Rot13 to see my eMail address ***
Back to top
Toby
Guest
Posted: Tue Dec 14, 2004 10:00 pm    Post subject: Re: Test Serial to Serial Connection, Protocol Down... Reply with quote
"Ivan Ostres" <vina.bfgerf@mt.ugarg.ue> wrote in message
news:MPG.1c28bc842489a74298979d@news.individual.net...
Quote:
In article <1102968322.558736.218350@f14g2000cwb.googlegroups.com>,
scott@serra.com says...
[snip: bunch of output]
5d22h: HD(1): Cable is unplugged.


Your router can't talk right on layer 1. It is probably a problem with
cable or clocking. I think that here would help 'show controller serial
0' to determine what is actually wrong.

--
-Ivan.

*** Use Rot13 to see my eMail address ***
Sounds about right. from the config I can see that you have no clock rate

set on the interfaces, so I am assuming you are using DTE cables. SH
Controllers to confirm. If that is the case then one of your adtran TSU
boxes should be setup to provide the clock as a master. The other should be
set as slave.

Toby
Back to top
krycheq
Guest
Posted: Thu Dec 16, 2004 9:38 pm    Post subject: Re: Test Serial to Serial Connection, Protocol Down... Reply with quote
Scooter wrote:
Quote:
I have a few Cisco routers that I'd like to use to connect up a remote
office via 24 channel T1.

One end is a 4500M with 4port Serial Card that already has 1 T1
Connection. The other end is a 2501.

Inbetween the two routers I have Adtran TSU100 units. Between the two
Adtrans (for testing purposes) I have a T1 crossover cable. The
Cisco's are conneted to the v.34 ports.

From either CDU/DSU I can loop up the far end CSU/DSU through the
Crossover cable. So I'm pretty sure that the CDU/DSU to CDU/DSU is
working fine.

On each of the routers I have Line Up, Protocol Down. If I look one
end or the other. The Far End Router shows Protocol Up. So that is
working.

The Config for the Serial interfaces is pretty simple. HDSL Encap (the
Default) and an IP Address. its the same that I have for my other
Serial T1 Connection.

Any Sugggestions?

Thanks,
Scott<-=


you need to set one of the adtrans to clock for the line... and then
both provide dte xmit clock to their own connected router. Both routers
are set as dte with no clocking config necessary. set the line-buildout
to auto and the channels to 24x64.

also, make sure your cable is good... 1/2 to 4/5 is the roll-over... T1
is supposed to be tip/ring insensitive, so it shouldn't matter if you
botch that, but I've seen CSU/DSUs that do care somehow when going
back-2-back. i've seen providers swear everything is good and that
they're able to loop-up their equipment, but then it turns out that the
circuit is no good and there's issues on their side of the link.

I assume you mean v.35 ports as that's what's on the back of those
tsu-100s. you can do a show controllers serial on your routers to
ensure you have dte cables and not dce cables.

good luck...

-sak
Back to top
 
Post new topic   Reply to topic    DComTalk.com Forum Index -> Cisco All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




VoIP Solutions: Telephone Systems Electronics Satellite TV Tech & Gadgets
Powered by phpBB