2 isp links redunancy

Report Inappropriate Content · ‎12-20-2006

helloo everybody

I have 2 isp connected to my router but the link is ethernet . i have added default route for both isp. 2nd route with high metric .no when my isp1 goes down .traffic is not shifted to 2nd isp . as the link is ethernet the local gateway is reachble. can any1 help me in giving suggestion what to do . can this be done with ip sla monitor .if yes then any 1 kindly provide the configuration

Thanks in Advance

devang_etcom · ‎12-20-2006

now will you please post the configuration as well as routing table if possible... as you explained if one go down then secondary route is not appear in routing table right!!!

so what are the AD configuration???

regards

Devang

sourabhagarwal · ‎12-20-2006

floating static routes won't work with ethernet interfaces as even if ISP is down, ethernet interface will not go down and hence route will not be removed from routing table and hence traffic will not be shifted to second ISP circuit.

spremkumar · ‎12-20-2006

Hi Arshad

As you have clearly figured out Object Tracking feature is the best possible way to trigger/make the secondary link active when you have your primary link terminating on Ethernet interface.

http://www.cisco.com/en/US/products/ps6350/products_configuration_guide_chapter09186a008042fbeb.html#wp1056927

regds

jitesh1982 · ‎12-21-2006

hi Prem

i have tried configuring ip sla monitor command .

and ip sla command are working

but in track command i am not getting rtr option

.so is there any other command instead of rtr i am getting command as

track 123 ?

ip

interface

list

so any option instead of rtr

spremkumar · ‎12-21-2006

Hi Jitesh

Can you revert on the device model and the ios installed on the same where you are configuring/trying this tracking feature?

If possible do post out the output show version command here..

regds

jitesh1982 · ‎12-22-2006

Hi prem

since i was not getting that

track 123 rtr 1 reachibility command

now i am tracking

tracking 123 interface tunnel 0 line-protocol

and that is working but i need to accomplish this task using ip sla monitor

current config is like this

track 123 interface Tunnel0 line-protocol

ip route 0.0.0.0 0.0.0.0 a.b.c.d track 123

here is the sh ver for my router

7206#sh ver

Cisco IOS Software, 7200 Software (C7200-IPBASEK9-M), Version 12.4(2)T, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Compiled Thu 23-Jun-05 20:25 by kellmill

ROM: System Bootstrap, Version 12.2(1r) [dchih 1r], RELEASE SOFTWARE (fc1)

BOOTLDR: 7200 Software (C7200-BOOT-M), Version 12.0(10)S, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

7206 uptime is 2 minutes

System returned to ROM by power-on

System image file is "slot0:c7200-ipbasek9-mz.124-2.T.bin"

This product contains cryptographic features and is subject to United

States and local country laws governing import, export, transfer and

use. Delivery of Cisco cryptographic products does not imply

third-party authority to import, export, distribute or use encryption.

Importers, exporters, distributors and users are responsible for

compliance with U.S. and local country laws. By using this product you

agree to comply with applicable laws and regulations. If you are unable

to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to

export@cisco.com.

Cisco 7206VXR (NPE300) processor (revision D) with 229376K/65536K bytes of memory.

Processor board ID 16079075

R7000 CPU at 262MHz, Implementation 39, Rev 2.1, 256KB L2 Cache

6 slot VXR midplane, Version 2.0

Last reset from power-on

1 FastEthernet interface

125K bytes of NVRAM.

20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).

4096K bytes of Flash internal SIMM (Sector size 256K).

Configuration register is 0x2102

jackyoung · ‎12-20-2006

Yes, object tracking is the solution or you can simply disconnect the failure ISP Ethernet connection when there is a failure for temp. solution before you actual implement the onject tracking.

Hope this helps.