adding site w/1720 via T1 p2p to existing 2610

[dbyteman]

I have a client with an existing 2610 connecting via T1 to the world. We just switched from FR to T1 with minimal problems and it works. We are adding a second location via T1 (all serial connections via T1 WIC) that will need to go through the existing server for web filtering. I cannot get the two locations to talk and am in dire need of direction. I am not against burning it down and starting over, and any help is greatly appreciated. Following are the configs:

2610
ip subnet-zero
no ip domain-lookup
!
!
!
interface Ethernet0/0
description connected to EthernetLAN_1
ip address x.x.x.57 255.255.255.248
no ip directed-broadcast
no keepalive
!
interface Serial0/0
description connected to In
ip address x.x.x.22 255.255.255.252
no ip directed-broadcast
no ip mroute-cache
no fair-queue
service-module t1 remote-alarm-enable
!
interface Serial0/1
description connected to BTHrouter
ip address 172.28.2.1 255.255.255.0
no ip directed-broadcast
!
router rip
version 2
passive-interface Serial0/0
network 65.0.0.0
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0/0
!
snmp-server community public RO
snmp-server location xxxxxxxxxx


1720
memory-size iomem 25
ip subnet-zero
no ip domain-lookup
!
modemcap entry mt56k:MSC=&f1s0=1
!
!
!
interface FastEthernet0
description connected to EthernetLAN
ip address 10.1.1.2 255.255.255.0
no keepalive
speed auto
!
interface Serial0
description connected to UnknownDevice
ip address 172.28.2.2 255.255.255.0
no fair-queue
service-module t1 remote-alarm-enable
!
router rip
version 2
network 10.0.0.0
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.28.2.1
no ip http server
!
!
snmp-server community public RO

 

[marsd]

The 1720 is at the remote end?
An easy way to tshoot this at l3 would be to disable no-auto summary and then see what rip2 has to say. You can enable auth beforehand if you are worried about screwing
up routes.

 

[dbyteman]

Would I be better off with the 2610 at the remote site?

 

[marsd]

That's funny. That was my mind mumbling to itself as
I wrote the original post. Of course it makes no difference.
In return:
Did you try the idea or debug ip rip, or debug ip traffic,
or post sh ip route, or really provide any actual, even if
obfuscated, information about your routing? Did you tell us
what encap you are using now?
Hmm.

 

[scraig84]

First things first - Which interface connects to the 1720? When you have them connected, are the interfaces on both sides in an "up/up" state when you do a "sh int"? All routing aside, can you at least ping the neighbor interface? All routing aside, if you can't ping the interface of the other router it doesn't matter what RIP has to say.

 

[dbyteman]

Everything shows up/up... Serial0/1 on the 2610 connects to serial0 on the 1720. I can ping from 1 router to the other, but can't get beyond the connected interfaces (using HDLC). show cdp neighbors on either router shows the other router, but that's it.

 

[scraig84]

OK - good to know. I looked back over your original post and see that on the 2610 under rip you have the statement:

network 65.0.0.0

and on the 1720 you have

network 10.0.0.0

Therefore, the 2610 is not receiving 10.0.0.0 routes and has no idea where 10.1.1.0 (Ethernet network off of 1720) is, so it cannot respond to it.

What I would do is add the "network 10.0.0.0" statement to the 2610 under the RIP config. I haven't worked with RIP in a while, so I can't remember if you will need to add "network 172.28.0.0" to both routers as well so that they start talking over that network as well. A sure fire way to get it to work would be to address the serial network with a network inside the 10.0.0.0 range (I would think you have enough space here to grab a network for it). The other option of course would be to simply add a static route to the 10.1.1.0 network on the 2610.

 

[marsd]

"Everything shows up/up... Serial0/1 on the 2610 connects to serial0 on the 1720. I can ping from 1 router to the other, but can't get beyond the connected interfaces (using HDLC). show cdp neighbors on either router shows the other router, but that's it."

Static routes are already configured.
You need to add the networks you would like RIP to advertise. The 172.28.2 network, the 65.x.x.x network,
etc. Your routers know how to get to each other but have no routes for any other destination. RIP needs to adver-
tise for all networks right now.

Look at the output of sh ip route and see what networks show up and how they are known.

Good Luck