03-27-2013 12:12 PM - edited 03-04-2019 07:25 PM
Hi,
Below is my HSRP configuration in distribution switch 1 and 2.
distribution switch 1:
!
interface Vlan100
description Interface Vlan 100
ip address 192.168.100.251 255.255.255.0
no ip proxy-arp
standby 100 ip 192.168.100.1
standby 100 timers 1 2
standby 100 preempt
!
distribution switch 1:
!
interface Vlan100
description Interface Vlan 100
ip address 192.168.100.252 255.255.255.0
no ip proxy-arp
standby 100 ip 192.168.100.1
standby 100 timers 1 2
standby 100 priority 110
standby 100 preempt
!
I could see below logs in distribution switch 1:
Mar 1 09:49:05.051: %HSRP-5-STATECHANGE: Vlan100 Grp 100 state Speak -> Standby
Mar 1 09:49:10.079: %HSRP-5-STATECHANGE: Vlan100 Grp 100 state Standby -> Active
Mar 1 09:49:10.135: %HSRP-5-STATECHANGE: Vlan100 Grp 100 state Active -> Speak
What should be the reason for above logs? Is it related to less hsrp timers? Please help...
Regards,
Musthafa
Solved! Go to Solution.
03-27-2013 01:08 PM
Pretty aggresive timers for version 1.
take the timers off, or come up with a ratio of hold down = 3x hello time.
or
take a look at hsrp version 2, it supports more aggressive timers.
03-27-2013 05:34 PM
Hi,
Yes I agree with all the timers which you have configure is aggressive.
Kindly check the following if you still see the HSRP:
There could be of many reason the HSRP flapping:
1- Check the CPU utilizaton on the device?
2- Check for STP changes (show spanning tree vlan 100 detail | in last|occur|ieee|exec
3- Check for logs at both the ends
4- Change the timers value to atleast min 2 & 6 respectively.
5- Check if there is any loop in the network.
HTH
Regards
Inayath
03-27-2013 01:08 PM
Pretty aggresive timers for version 1.
take the timers off, or come up with a ratio of hold down = 3x hello time.
or
take a look at hsrp version 2, it supports more aggressive timers.
03-27-2013 01:29 PM
Your HSRP timers are definitely aggressive. How frequent are you getting these error messages? If you just noticed them once or twice, you will have to troubleshoot what could have happened during that time.
If you see these messages frequently, you will have to increase the timers. timers 2 - 6 should be good enough. But it despends on how fast you would like to converge.
03-27-2013 02:35 PM
I noticed this once (today) , not frequently , i dont know what happened during that time, Is there any way to understand the real cause ?
03-27-2013 05:34 PM
Hi,
Yes I agree with all the timers which you have configure is aggressive.
Kindly check the following if you still see the HSRP:
There could be of many reason the HSRP flapping:
1- Check the CPU utilizaton on the device?
2- Check for STP changes (show spanning tree vlan 100 detail | in last|occur|ieee|exec
3- Check for logs at both the ends
4- Change the timers value to atleast min 2 & 6 respectively.
5- Check if there is any loop in the network.
HTH
Regards
Inayath
04-03-2013 12:07 AM
Thanks all , I moved hsrp hold timer from 2 to 4 sec for all vlans, I guess this would be more stable , I will be monitoring the status for few more days,
for eg:
distribution switch 1:
!
interface Vlan100
description Interface Vlan 100
ip address 192.168.100.251 255.255.255.0
no ip proxy-arp
standby 100 ip 192.168.100.1
standby 100 timers 1 4
standby 100 preempt
!
distribution switch 1:
!
interface Vlan100
description Interface Vlan 100
ip address 192.168.100.252 255.255.255.0
no ip proxy-arp
standby 100 ip 192.168.100.1
standby 100 timers 1 4
standby 100 priority 110
standby 100 preempt
!
04-03-2013 12:08 AM
HI mohammed,
Could you mark this as solved and close this thread.
Regards
Inayath
04-03-2013 12:26 AM
Yes , this is solved , cisco also recommending , do not configure hold timer below 4 seconds.
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094afd.shtml#topic14
once again , thanks all for help.
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