07-20-2008 08:33 AM - edited 03-03-2019 10:48 PM
Hi,
I will configure the hsrp for auto failover when one circuit down. Attached file is the hardware installation.
Those are the requirements
- the default circuit is provider B
- default gateway of all users is 192.168.12.10
- when circuit B down, it will failover to provider A, all traffic via circuit A.
- when circuit B comes up again, router B is active, router A is hot standby. All traffic vai circuit B.
I configure router setting, pls check any missing or need to amendy
Any suggestion is welcome
rdgs
R1
interface Fastethernet 0
ip address 192.168.10.1 255.255.255.0
no ip route-cache
no ip proxy-arp
standby 1 ip 192.168.10.10
standby 1 preempt
interface Fastethernet 1
description Provider A, 10M cct
ip address 210.x.x.x 255.255.255.252
R2
interface Fastethernet 0
ip address 192.168.10.2 255.255.255.0
no ip route-cache
no ip proxy-arp
standby 1 ip 192.168.10.10
standby 1 preempt
standby 1 priority 105
standby 1 track Fastethernet 1
interface Fastethernet 1
description Provider B, 10M cct
ip address 216.x.x.x 255.255.255.252
07-20-2008 08:39 AM
07-20-2008 11:41 AM
This seems to be quite a working solution.
Few comments:
Just "standby 1 ip" would suffice in R1(Backup) and it will learn the vIP from the primary even if you didn't specify it.(Try and see for yourself).
To protect against HSRP-spoofing you could add HSRP(MD5) authentication.
e.g.
"standby 1 authentication md5 key-string xxxx"
Please check the documentation for additional options.
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gthsrpau.html#wp1027129
HTH
07-20-2008 01:42 PM
HSRP Configuration is correct.
07-20-2008 02:50 PM
The track will only kick-in when the interface is down/down.
With ethernet WAN that is rare unless the provider shuts their router down causing your router to be hard down.
I suggest using track with SLA and ping a remote interface in order to verify connectivity via that link. Pinging the next hop on that link sounds like a reasonable target.
HTH,
__
Edison.
07-21-2008 12:15 AM
Hi Edison,
"With ethernet WAN that is rare unless the provider shuts their router down causing your router to be hard down"
I have a question regarding this statement. In practice there are switches sit between the Ethernet WAN connecting routers or gateways, right?
In such situations isn't it just the Ethernet interface of the immediate device which could be effectively tracked/monitored ?
07-23-2008 01:20 PM
In practice there are switches sit between the Ethernet WAN connecting routers or gateways, right?
Yes.
In such situations isn't it just the Ethernet interface of the immediate device which could be effectively tracked/monitored ?
The recommendation is monitoring Layer3 reachability instead of the status of the physical link as the physical link does not provide a true indication of remote connectivity.
HTH,
__
Edison.
07-23-2008 01:47 PM
This is the a good document for 'Static Routing Backup Using Object Tracking'
http://www.cisco.com/en/US/docs/ios/12_3/12_3x/12_3xe/feature/guide/dbackupx.html
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: