http://journey2ccie.blogspot.com/2010/03/tuning-hsrp-gns3.html

configure PC, R1, R2 and R4 as below
PC
PC(config)#no ip routing
PC(config)#int fa 0/0
PC(config-if)#ip add 10.1.1.10 255.255.255.0
PC(config-if)#no shut

R1
R1(config)#interface fastEthernet 0/0
R1(config-if)#ip add 10.1.1.1 255.255.255.0
R1(config-if)#no shut
R1(config)#int serial 0/0
R1(config-if)#ip add 172.16.1.2 255.255.255.252
R1(config-if)#clock rate 64000
R1(config-if)#no shut
R1(config)#router eigrp 1
R1(config-router)#no auto-summary
R1(config-router)#net 0.0.0.0
R2
R2(config)#int fa 0/0
R2(config-if)#ip add 10.1.1.2 255.255.255.0
R2(config-if)#no shut
R2(config)#int ser 0/0
R2(config-if)#ip add 172.16.2.2 255.255.255.252
R2(config-if)#clock rate 64000
R2(config-if)#no shut
R2(config)#router eigrp 1
R2(config-router)#no auto-summary
R2(config-router)#net 0.0.0.0
R4
R4(config)#int ser 0/0
R4(config-if)#ip add 172.16.1.1 255.255.255.252
R4(config-if)#no shut
R4(config-if)#int ser 0/1
R4(config-if)#ip add 172.16.2.1 255.255.255.252
R4(config-if)#no shut
R4(config-if)#int lo 0
R4(config-if)#ip add 192.168.1.1 255.255.255.255
R4(config-if)#
R4(config)#router eigrp 1
R4(config-router)#no auto-summary
R4(config-router)#net 0.0.0.0

make sure PC can ping all the interfaces on R1, R2 and R4 !! if can’t, troubleshoot it accordingly

create standby interface for PC and point the PC’s gateway to this address
R1(config)#interface fastEthernet 0/0
R1(config-if)#standby 1 ip 10.1.1.99
R1(config-if)#standby 1 priority 150
done for R1. 3rd line is to set R1 to have the higher priority, default value is 100. Configure same for R2 accept the 3rd line, leave default value for R2
R2(config)#interface fastEthernet 0/0
R2(config-if)#standby 1 ip 10.1.1.99

configure default-gateway for PC
PC(config)#ip default-gateway 10.1.1.99

let’s verify our configuration are working correctly
1st let check the priority, traceroute from PC to 172.16.2.1 result should showing as below, since we set Interface 10.1.1.1 to have the higher priority
PC#traceroute 172.16.2.1
1 10.1.1.1 20 msec 16 msec
2 172.16.1.1 40 msec 100 msec *
R1#sh stan
FastEthernet0/0 - Group 1
State is Active
17 state changes, last state change 00:00:47
Virtual IP address is 10.1.1.99
Active virtual MAC address is 0000.0c07.ac01
Local virtual MAC address is 0000.0c07.ac01 (default)
Hello time 3 sec, hold time 10 sec
Next hello sent in 0.224 secs
Preemption disabled
Active router is local
Standby router is 10.1.1.2, priority 100 (expires in 8.972 sec)
Priority 150 (configured 150)
IP redundancy name is "hsrp-Fa0/0-1" (default)

then make sure failover are working fine, do continuous ping to 172.16.2.1, then shutdown Int Fa 0/0 on R1, Fa 0/0 on R2 (10.1.1.2) should be the active standby router now, there should be about 10 second of down time. that’s is the default hold time before interface considered as death. later we’ll tune this value to make it shorter
Protocol [ip]:
Target IP address: 172.16.2.1
Repeat count [5]: 99999
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 99999, 100-byte ICMP Echos to 172.16.2.1, timeout is 2 seconds:
.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.....!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.
Success rate is 93 percent (104/111), round-trip min/avg/max = 24/60/100 ms
traceroute again to verify the path is thru 10.1.1.2
1 10.1.1.2 24 msec 8 msec 16 msec
2 172.16.2.1 52 msec 64 msec *

bring up again the 10.1.1.1 interface, then issue command show standby on R1, notice that 10.1.1.2 still the active standby router even we already set 10.1.1.1 to have the higher priority
R1#show standby
FastEthernet0/0 - Group 1
State is Listen
18 state changes, last state change 00:04:12
Virtual IP address is 10.1.1.99
Active virtual MAC address is 0000.0c07.ac01
Local virtual MAC address is 0000.0c07.ac01 (default)
Hello time 3 sec, hold time 10 sec
Preemption disabled
Active router is 10.1.1.2, priority 100 (expires in 9.888 sec)
Standby router is unknown
Priority 150 (configured 150)
IP redundancy name is "hsrp-Fa0/0-1" (default)

to make sure the active standby go back to the primary everytime it’s come back alive again, configure as below
R1(config)#int fa 0/0
R1(config-if)#standby 1 preempt
use all the method that we already discuss above to verify all the configuration are running as it should

tune hello and holdtime, Cisco recommended to set the value of holdtime three time more than hello time
R1(config)#int fa 0/0
R1(config-if)#standby 1 timers 1 3
set the same on R2 Int Fa 0/0

verify this by continuous ping then shutdown 10.1.1.1, you’ll see shorter down time
Sending 99999, 100-byte ICMP Echos to 172.16.2.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!..!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.
Success rate is 97 percent (97/100), round-trip min/avg/max = 12/58/104 ms


http://journey2ccie.blogspot.com/2010/03/tuning-hsrp-gns3.html

Hi,
thanks for your tutorial. Really helpful.
You wrote:



Yes, R2 is active but R1 is in Listen state and not in Standby yet. Try to wait some time and tell me if R1 stops at Standby state or goes to Active state.

In theory router (or MLS) should stay in Active state even the router with higher priority without configured preempt comes up.
In my case the router with higher priority always goes to Active state even when preemption is not configured on both routers. This is valid for GNS3 (I use 3725 and 3640 used for test with last IOS 124-15.T13, NM-16SW).

I tried to test it on real CAT3550 and 2621Xm and it worked like in theory - router with higher priority went to Active state only if Standby failed or when preempt was configured on higher priority router (switch).

I would like to know if anyone else noticed this behaviour with GNS3.

Thanks,

_________________
Brezular

http://brezular.wordpress.com

Hi,
I did some research and this is my update:

1.


it works as you said. R1 goes to STANDBY state and R2 sits in Active state.

2. See my topology in attachment, please.

I use NM-SW modul on both R1 and R2 routers. Routers are connected via L2 ports and are in standby group 1. There is SVI 1 configured on both routers with IP addresses according to topology. Preemption is not configured on R1 nor R2 router. R1 is in active state because of priority 150.

TEST1:

1) shutdown FA 2/0 R1:
R2 goes to Active state after the dead timer is reached. Now R1 is in Init state and R2 is in Active state.

2)no shutdown FA 2/0 R1
R1 goes from Init trough Listen, Speak to Active state and R2 goes from Active to Speak and from Speak to Standby state.

Is it OK? According to the theory R2 should sit in Active state and R1 should go to STANDBY state. But it is not true here.

TEST2:

R1 is in active state and R2 in STANDBY state. Now we can do:

1) shutdown SVI 1 R1

R2 goes to Active state after the dead timer is reached. Now R1 is in Init state and R2 is in Active state

2) no shutdown SVI 1 R1
R1 goes from Init through Listen, Speak to STANDBY state and R2 sits in ACTIVE state. This behaviour is OK according to theory.


Is here someone who understand the result in TEST1 ? ;-)

Thanks,

_________________
Brezular

http://brezular.wordpress.com