Routing Trouble

[KeithKessler]

I've been beating my head agains the wall for a day no trying to get this to work. I'm in the process of upgrading our WAN by replacing the core router and all the remote routers and adding additional T1s. I'm working on the first remote site now and can't get the routing correct. Relevant parts of the remote config below:

interface FastEthernet0/0
description "Lakewood Ethernet"
ip address 192.168.3.4 255.255.255.0
duplex half
speed auto
no mop enabled
!
interface Serial0/0/0
description "AT&T T1 XXXXXXXXXX"
ip address 192.168.51.1 255.255.255.0
encapsulation ppp
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.50.1

Show ip route on the remote is:
Gateway of last resort is 192.168.50.1 to network 0.0.0.0

C 192.168.51.0/24 is directly connected, Serial0/0/0
192.168.50.0/32 is subnetted, 1 subnets
C 192.168.50.1 is directly connected, Serial0/0/0
C 192.168.3.0/24 is directly connected, FastEthernet0/0
S* 0.0.0.0/0 [1/0] via 192.168.50.1


Relevant parts of the new core router config:


controller T1 0/0/0
framing esf
linecode b8zs
channel-group 0 timeslots 1-24
description "Lakewood T1 CktID XXXXXXX"
!
interface GigabitEthernet0/0
description "Chester LAN"$ETH-LAN$
ip address 192.168.1.254 255.255.255.0
duplex auto
speed auto
no mop enabled
!
interface Serial0/0/0:0
description "Lakewood T1"
ip address 192.168.50.1 255.255.255.0
encapsulation ppp
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.1.1
ip route 192.168.3.0 255.255.255.0 192.168.51.1

Show ip route looks like this:
Gateway of last resort is 192.168.1.1 to network 0.0.0.0

192.168.51.0/32 is subnetted, 1 subnets
C 192.168.51.1 is directly connected, Serial0/0/0:0
C 192.168.50.0/24 is directly connected, Serial0/0/0:0
C 192.168.1.0/24 is directly connected, GigabitEthernet0/0
S 192.168.3.0/24 [1/0] via 192.168.51.1
S* 0.0.0.0/0 [1/0] via 192.168.1.1

From the new core I can ping and trace 192.168.3.4 just fine, from the remote I can ping and trace 192.168.1.254 just fine the problem is I can't ping anything else on the network (other WAN locations or Internet sites) from the remote. The default route on the new core should just send everything to the old core router (192.168.1.1). Everything works fine when logged into the new core (can ping all locations and Internet sites)

I'm a total noob in need of some help please..

Thanks,

--Keith

 

[baddos]

interface Serial0/0/0
description "AT&T T1 XXXXXXXXXX"
ip address 192.168.51.1 255.255.255.0

interface Serial0/0/0:0
description "Lakewood T1"
ip address 192.168.50.1 255.255.255.0

Those addresses aren't in the same subnet.

 

[KeithKessler]

You're right they are not. Origionally I had them on the same subnet 192.168.15.1 & 15.2 but read somewhere that they had to be on a different subnet - I've tried it both ways with the same result.

 

[KeithKessler]

Okay, I've chanted them back to the same subnet and changed the route in the core too:

ip route 192.168.3.0 255.255.255.0 192.168.50.2

interface Serial0/0/0
description "AT&T T1 XXXXXXXXX"
ip address 192.168.50.2 255.255.255.0
encapsulation ppp
!
interface Serial0/0/0:0
description "Lakewood T1"
ip address 192.168.50.1 255.255.255.0
encapsulation ppp
!

Same result - still can't ping 192.168.1.1 (old core) or anything else from the remote router.

Any other ideas? - Thanks!

 

[baddos]

Post a show ip route from both routers.

 

[KeithKessler]

New core:

Gateway of last resort is 192.168.1.1 to network 0.0.0.0

192.168.50.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.50.2/32 is directly connected, Serial0/0/0:0
C 192.168.50.0/24 is directly connected, Serial0/0/0:0
C 192.168.1.0/24 is directly connected, GigabitEthernet0/0
S 192.168.3.0/24 [1/0] via 192.168.50.2
S* 0.0.0.0/0 [1/0] via 192.168.1.1

New remote:

Gateway of last resort is 192.168.50.1 to network 0.0.0.0

192.168.50.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.50.0/24 is directly connected, Serial0/0/0
C 192.168.50.1/32 is directly connected, Serial0/0/0
C 192.168.3.0/24 is directly connected, FastEthernet0/0
S* 0.0.0.0/0 [1/0] via 192.168.50.1

 

[baddos]

Change the default route on the new remote to 192.168.50.2.

 

[KeithKessler]

No go, when I try that I get:

Lakewood-Router(config)#ip route 0.0.0.0 0.0.0.0 192.168.50.2
%Invalid next hop address (it's this router)

192.168.50.1 is serial on core
192.168.50.2 is serial on remote

Thanks!

 

[KeithKessler]

new core is connected to
C 192.168.1.0/24 is directly connected, GigabitEthernet0/0

and default route is to 192.168.1.1 - I thought that would take care of it. From the new core I can ping 192.168.1.1 (old core internet sites - routed through the old core)

Thanks, I've changed the duplex to auto.

I've tred RIP v2 and things start to work but the routes get really funky as most of the old routers are using RIP and things start routing over ISDN rather than the new T1. I'm trying to keep everyting simple with just a few static routes.

 

[baddos]

C 192.168.50.1/32 is directly connected, Serial0/0/0
S* 0.0.0.0/0 [1/0] via 192.168.50.1

This is your problem. Your tell this router to have it's default route be one of it's interfaces.

 

[KeithKessler]

I'm not really sure what you mean so I tred to take the IPs out of the equasion. The default on the remote is now:

ip route 0.0.0.0 0.0.0.0 Serial0/0/0

and show ip route looks like:

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

192.168.50.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.50.0/24 is directly connected, Serial0/0/0
C 192.168.50.1/32 is directly connected, Serial0/0/0
C 192.168.3.0/24 is directly connected, FastEthernet0/0
S* 0.0.0.0/0 is directly connected, Serial0/0/0

Still no luck

 

[Fatty99]

Are you sure the subnet (192.168.3.0 255.255.255.0) of the remote site is known on the old router ?? and routed to your new core router ??

Can u post ip route of the old core router ??

grtz,

Fatty

 

[Jsteve]

I would suggest moving towards a routeing protocol.

------eigrp---------------
Core

interface GigabitEthernet0/0
description "Chester LAN"$ETH-LAN$
ip address 192.168.1.254 255.255.255.0
!
interface Serial0/0/0:0
description "Lakewood T1"
ip address 192.168.50.1 255.255.255.0
encapsulation ppp
!
Router eigrp 1
no auto-summ
network 192.168.1.0
network 192.168.50.0

Remote

interface FastEthernet0/0
description "Lakewood Ethernet"
ip address 192.168.3.4 255.255.255.0
!
interface Serial0/0/0
description "AT&T T1 XXXXXXXXXX"
ip address 192.168.50.2 255.255.255.0
encapsulation ppp
!
Router eigrp 1
no auto-summ
network 192.168.3.0
network 192.168.50.0
------------RIP-------------

Core

interface GigabitEthernet0/0
description "Chester LAN"$ETH-LAN$
ip address 192.168.1.254 255.255.255.0
!
interface Serial0/0/0:0
description "Lakewood T1"
ip address 192.168.50.1 255.255.255.0
encapsulation ppp
!
Router rip
ver 2
no auto-summ
network 192.168.0.0


Remote

interface FastEthernet0/0
description "Lakewood Ethernet"
ip address 192.168.3.4 255.255.255.0
!
interface Serial0/0/0
description "AT&T T1 XXXXXXXXXX"
ip address 192.168.50.2 255.255.255.0
encapsulation ppp
!
Router rip
ver 2
no auto-summ
network 192.168.0.0

---------If you must use static--

Core

interface GigabitEthernet0/0
description "Chester LAN"$ETH-LAN$
ip address 192.168.1.254 255.255.255.0
!
interface Serial0/0/0:0
description "Lakewood T1"
ip address 192.168.50.1 255.255.255.0
encapsulation ppp
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.50.2


Remote

interface FastEthernet0/0
description "Lakewood Ethernet"
ip address 192.168.3.4 255.255.255.0
!
interface Serial0/0/0
description "AT&T T1 XXXXXXXXXX"
ip address 192.168.50.2 255.255.255.0
encapsulation ppp
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.50.1

 

[Jsteve]

Also keep in mind with the staic config, If you add another site you will have to remove the default route from the core router and add individual static routes for each neighbor router.

i.e.

Core
ip classless
ip route 192.168.3.0 0.0.0.255 192.168.50.2
ip route 192.168.4.0 0.0.0.255 192.168.50.2

Remote1
ip route 0.0.0.0 0.0.0.0 192.168.50.1

Remote2
ip route 0.0.0.0 0.0.0.0 192.168.50.1

 

[KeithKessler]

Thanks for the help guys - I got it working by enabling RIP on the new core and just keeping the single default route on the new remote. I'm still not 100% sure why this worked so I'm gong to study the rip gererated routing table.

Thanks for all the help!
--KK