ip route statements to connect three routers (two via atm)

[ChuckHaynes]

Router 1 ---------- Switch 1 ----------  Switch 2 ---------- Router 2 ---------- Router 3

Router 1 (main)

interface 1 - 10.110.47.254

interface 43 - 10.110.43.254

Router 2 (DSL CO)

vlan 43 - 10.110.43.207

atm0.1 - 10.110.125.1

Router 3 (DSL CPE)

vlan 150 - 10.110.150.1

atm0.1 - 10.110.125.2

currently I have the following ip route statements:

Router 1

10.110.125.0 255.255.255.0 10.110.43.207

10.110.150.0 255.255.255.0 10.110.43.207

Router 2

0.0.0.0 0.0.0.0 10.110.43.254

10.110.150.0 255.255.255.0 10.110.125.2

Router 3

0.0.0.0 0.0.0.0 10.110.125.1

The problem is that I can't ping the far side CPE (10.110.150.1) from the Main router or the CO router. I can ping back to the Main router from the CPE router. This makes me think the 10.110.150.0 255.255.255.0 10.110.125.2 statement isn't doing anything. Can anyone identify the problem here? Thanks

[Reza Sharifi]

10.110.150.0/24 is part of vlan 150.  Is vlan 150 configured correctly and it is up and running?

Has the interface been added to vlan 150?

HTH

[ChuckHaynes]

Here is part of the config from the CPE:

interface BRI0
 no ip address
 encapsulation hdlc
 shutdown
 isdn termination multidrop
!
interface ATM0
 no ip address
 no atm ilmi-keepalive
!
interface ATM0.1 point-to-point
 ip address 10.110.125.2 255.255.255.0
 cdp enable
 pvc 8/35
  encapsulation aal5snap
 !
!         
interface FastEthernet0
 switchport access vlan 150
 no ip address
!
interface FastEthernet1
 switchport access vlan 150
 no ip address
!
interface FastEthernet2
 switchport access vlan 150
 no ip address
!
interface FastEthernet3
 switchport access vlan 150
 no ip address
!
interface Vlan1
 no ip address
 no ip route-cache
 shutdown
!
interface Vlan150
 ip address 10.110.150.1 255.255.255.0
!
!
ip forward-protocol nd
no ip http server
no ip http secure-server
!
!
ip route 0.0.0.0 0.0.0.0 10.110.125.1

When I do a: sh int vlan150, it says:

Vlan150 is down, line protocol is down  (so, no, it isn't up)

[Reza Sharifi]

So, couple of items to check

1-Did you create the layer-2 vlan

config 1

vlan 150

name test-vlan

exit

also, I see interfaces 0-3 are part of vlan 150.  Is any device (PC, laptop, printer, etc) connected to any of these ports?

sh ip int bri fa0 or fa1

If there is no device connected to one of these ports with an IP the vlan will not come up

HTH

[ChuckHaynes]

These units are just in a test environment right now. There is not anything plugged into Ethernet ports 0-3.

Regarding the Layer 2 question... are you asking if I created vlan 150 on the switches? The CPE is the only device that has vlan 150.

[Reza Sharifi]

These units are just in a test environment right now. There is not anything plugged into Ethernet ports 0-3.

Then if there is no device connected to any of the ports, the vlan interface is not going to come up.  It will stay down until a device (PC, laptop, etc..) is connected to one of the ports. For test purpose, you can connect a laptop to one of these ports and give it an IP address in 10.110.150.0 range and see if the vlan interface comes up.  sh ip int bri vlan 150

Regarding the Layer 2 question... are you asking if I created vlan 150 on the switches? The CPE is the only device that has vlan 150.

Correct on the same device where you have the layer-3 interface

nterface Vlan150
 ip address 10.110.150.1 255.255.255.0)

you also need to create a layer-2 interface.

HTH

[ChuckHaynes]

If I use the "no autostate" command, will it force the interface up and allow me to ping/access it?

Also, I am confused about the Layer 2 vlan requirement. Are you saying that I need to add the commands you provided to the CPE Router? If so, can you please explain why? Thanks

[Reza Sharifi]

You can try the "no autostate"command.  The other way you can test is by creating a loopback interface and move the ip from vlan 150 to loopback and test

config t

inter vlan 150

no ip address

int lo0

ip add 10.110.150.1 255.255.255.0

no sh

then sh ip int bri lo0

now try to ping this IP from router 2.

HTH

[ChuckHaynes]

I will try this and report back. It probably won't be until Monday though. Thanks.

[ChuckHaynes]

Yes, the "no autostate" command worked. I can now access the CPE successfully (even when nothing is connected). I also applied the command to the CO side in case we are ever in a situation in the work environment where the CO side may be disconnected and we are on the CPE trying to verify the connection.

One more thing... (and please excuse my ignorance) while the connection does work correctly inside my location (main router), there is no access to anything other than the LAN side of the CO from the outside. I assume the other routers (at other locations on our WAN) don't know the route. If I'm on the CPE end, I can get to our main router, but nothing else. I may be getting out, but nothing knows how to get back in?

[Reza Sharifi]

Glad to hear that the "no autostate"worked for you. And yes, that is correct the router in other location most likely don't have the routes to get back in.

HTH

[ChuckHaynes]

What are my options to get the route into the other routers?

We have several of these Cisco 888 DSL routers connected at different sites. Most of the other 888 units can be accessed from all the other locations in the WAN (each location has it's own main 2911 router). I have tried to compare any static routes in the routers, but I don't see any. So how can the other 888's be seen from other locations? Thanks.

[ChuckHaynes]

I figured it out. I just needed to add the "redistribute static" command.