static route

We have two cisco 837 routers (R1 & R2) located at our main office. Another cisco 837 router (EA) is located at remote office.

There are two tunnel interface configured. tunnel1 connects R1 and EA routers. Tunnel2 connects R2 and EA routers.

Static route table is configurate as follow:

In R1: ip route 192.9.109.0 255.255.255.0 Tunnel1 In R2: ip route 192.9.109.0 255.255.255.0 Tunnel2 (Where 192.9.109.0 is remote office network address)

In EA: ip route 192.9.200.0 255.255.255.0 Tunnel1 ip route 192.9.200.0 255.255.255.0 Tunnel2 5 (Where 192.9.200.0 is main office network address)

Usually everything works right. Both tunnels are up and we can connect to EA throught either R1 or R2.

Problems begins when adsl connections at R1 fail. We think EA must detect that tunnel1 is down and route trafic over Tunnel2, but EA didn=B4t route over tunnel2 until we manually shutdown tunnel1.

Can you help me about this?

Regards

Reply to
karlutxo
Loading thread data ...

In article , karlutxo wrote: :We have two cisco 837 routers (R1 & R2) located at our main office. :Another cisco 837 router (EA) is located at remote office.

:There are two tunnel interface configured. tunnel1 connects R1 and EA :routers. Tunnel2 :connects R2 and EA routers.

:Usually everything works right. Both tunnels are up and we can connect :to EA :throught either R1 or R2.

:Problems begins when adsl connections at R1 fail. We think EA must :detect that tunnel1 :is down and route trafic over Tunnel2, but EA didn=B4t route over :tunnel2 until we manually :shutdown tunnel1.

That's a problem. As far as the routers are concerned, GRE tunnels are -always- up (unless maybe you turn on GRE keyalives.)

Please have a look at Vincent C. Jones' web site for information on the sorts of things you have to do in order to have tunnel state track interface or connection state.

According to what I've read (and experienced a bit myself), it is fairly common for ADSL links to go down "one hop away", leaving the local interface physically up and able to send packets but the packets are not getting anywhere useful. This requires that you use an end-to-end checking strategy rather than relying on the router detecting a hardware link down.

Reply to
Walter Roberson

I am running a pix 515 with ver 6.3 and I need to create a few static routes. I searched and found the command:

ip route 172.16.0.0 255.255.255.0 192.168.150.1

but I get an "invalid keyword route". I am routing internal traffic to a VPN router for three specific IP addresses. I need to add routes for those IP's. What is the command in 6.3 to add a static route?

Thanks,

Paul

Reply to
dexteroc

"ip route" is IOS (or possibly PIX 7). For PIX 6,

route inside 172.16.0.0 255.255.255.0 192.168.150.1

Reply to
Walter Roberson

for asa/pix with v7.x it would be also route inside 172.16.0.0 255.255.255.0 192.168.150.1

Roman Nakhmanson

Reply to
nakhmanson

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.