12-13-2012 08:17 AM - edited 03-04-2019 06:24 PM
HI
we started a new branch ,there two link is there one 100mbps and 30 mbps from diffrent vendors. one link is connected to first multilayerswitch
and anoter is connected to second multilayer switch..
in this two switch i want to configure two default route pointing to our core mulitlayer switchr in datacenter
we want to configure hsrp and ipsla(if wan 100 mbps down, secondary will be up) for that i configure in gns3 ,hsrp work but wan tracking is not working
configuration of swithes
primarymulitalyerswitch(config)#interface vlan 1
ip add 10.10.16.10 255.255.252.0
no sh
standby 2 ip add 10.10.16.1
standby 2 preempt
standby 2 priority 200
exit
ip route 0.0.0.0 0.0.0.0 1.1.1.2(wan)
ip sla monitor 1
type echo protoclol ipicmpecho 50.0.0.1(loopback)
timeout 2000
thersold 2000
frequency 10
ip sla monitor shedule 1 startime now life foerver
track 1 rtr 1 reachibility
interface valn 1
standyby 2 track 1 decre 150
secondarymultilayerswitch(config)#interface valn 1
ip add 10.10.16.20 255.255.252.0
no sh
standby2 ip add 10.10.16.1
standby2 priority 100
exit
ip route 0.0.0.0 0.0.0.0 2.2.2.2(wan)
datacentermultilayerswitch(config)ip route10.10.16.0 255.255.252.0 1.1.1.1(primarymultialyerswitchinterfaceip)
ip route 10.10.16.0 255.255.252.0 2.2.2.1(secondaymultlayeswitchinterfaceip)
interface loopbak 0
ip add 50.0.0.1 255.255.2552.255
if i shoutdown vlan 1 of primary switch anoterworkig fine but if i down wan interface or shutodown loopback its not workign
thanku
,
12-13-2012 08:13 PM
Have you tried testing this on actual hardware? GNS3 is great for most things but I find that when using HSRP it can be quite unpredicatible when it comes to noticing that a link is meant to be down.
12-14-2012 02:45 AM
Hi
If you have dynamic routing setup between the two multi-layer switches, then i think the Loopback of the DC Switch never goes down, becuase it will be reachable via the secondary switch. This means object tracking will never fail. You can verify this but shutting down the loopback and check the routing table on the primary switch to see if the loopback route is still in there and pointing towards seconda Multi-Layer Switch.
So, one way to fix it, would be to add a static to route to the primary switch for the loop back via the 100Mbps circuit. If that circuit goes down, the route stays in the routing table and you will not be able to ping the loopback any more
ip route 50.0.0.1 255.255.255.255 1.1.1.2 name PERM_LOOPBACK_DC_SW permanent
Regards
Stephen
==========================
http://www.rConfig.com
A free, open source network device configuration management tool, customizable to your needs!
12-14-2012 02:47 AM
If the above does not resolve it port the following for both switches
- before you shut the Loopback
show ip route
show standby bri
sh ip sla monitor statistics
- after you shut the Loopback
show ip route
show standby bri
sh ip sla monitor statistics
==========================
http://www.rConfig.com
A free, open source network device configuration management tool, customizable to your needs!
12-14-2012 04:14 AM
Hello, this is the answer to your problem.
Your secondary switch will take over the primary role after tracking reduces the priority (in your config reduces it by 150), ONLY if you meet the following condition:
*Your secondary switch has preempt configured* This is important otherwise tracking on the primary switch is ineffective.
Good luck.
Roger
12-14-2012 07:54 AM
Well, that was a good catch, Roger is absolutley corrcet.
Regards
==========================
http://www.rConfig.com
A free, open source network device configuration management tool, customizable to your needs!
- Always vote on an answer if you found it helpful
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide