HSRP time out

[hemadri37]

Dear All,

i have two cisco switches 4948 in high availabilty. there is time out when one server trying to connect HSRP IP. 172.31.248.6 is HSRP IP.

logs are as below

07-Sep-2016 00:33:16 cohosted2.SCORING Info 00070 00017 SCORING: timeout with errno = 110, on attempt to connect to IP 172.31.248.6.
07-Sep-2016 00:33:16 cohosted2.SCORING Info 00070 00019 SCORING: A new score 0 reported to dr process.
07-Sep-2016 00:33:25 cohosted2.SCORING Info 00070 00020 SCORING: Connection to 172.31.248.6 restored.
07-Sep-2016 00:33:25 cohosted2.SCORING Info 00070 00019 SCORING: A new score 15 reported to dr process.
07-Sep-2016 11:26:15 cohosted2.SCORING Info 00070 00017 SCORING: timeout with errno = 110, on attempt to connect to IP 172.31.248.6.
07-Sep-2016 11:26:15 cohosted2.SCORING Info 00070 00019 SCORING: A new score 0 reported to dr process.
07-Sep-2016 11:26:24 cohosted2.SCORING Info 00070 00020 SCORING: Connection to 172.31.248.6 restored.
07-Sep-2016 11:26:24 cohosted2.SCORING Info 00070 00019 SCORING: A new score 15 reported to dr process.
07-Sep-2016 14:09:15 cohosted2.SCORING Info 00070 00017 SCORING: timeout with errno = 110, on attempt to connect to IP 172.31.248.6

HSRP configuration of SW1

interface Vlan105
ip address 172.31.248.4 255.255.255.0
ip access-group ICMP in
ip access-group DENY out
no ip redirects
no ip proxy-arp
no ip route-cache cef
no ip route-cache
standby 101 ip 172.31.248.6
standby 101 timers 1 2
standby 101 priority 105
standby 101 preempt
standby 101 track GigabitEthernet1/5
standby 101 track GigabitEthernet1/4
arp timeout 5
end

HSRP configuration in SW2

interface Vlan105
ip address 172.31.248.5 255.255.255.0
ip access-group ICMP in
ip access-group DENY out
no ip redirects
no ip proxy-arp
no ip route-cache cef
no ip route-cache
standby 101 ip 172.31.248.6
standby 101 timers 1 2
standby 101 preempt
standby 101 track GigabitEthernet1/4
standby 101 track GigabitEthernet1/5
arp timeout 5
end

Also i checked interfaces and didnot find any errors.

please advise

[Richard Bradfield]

Can you post the HSRP config  for each switch

[hemadri37]

configuration appended above

[Richard Bradfield]

Hi,

Please see notes below about timers it is not recommended to have the hold timer less than 4 seconds. what happens if you leave the default of 3 and 10 seconds?

Each router only uses three timers in HSRP. The timers time hello messages. The HSRP converges, when a failure occurs, depend on how the HSRP hello and hold timers are configured. By default, these timers are set to 3 and 10 seconds, respectively, which means that a hello packet is sent between the HSRP standby group devices every 3 seconds, and the standby device becomes active when a hello packet has not been received for 10 seconds. You can lower these timer settings to speed up the failover or preemption, but, to avoid increased CPU usage and unnecessary standby state flapping, do not set the hello timer below one (1) second or the hold timer below 4 seconds. Note that, if you use the HSRP tracking mechanism and the tracked link fails, the failover or preemption occurs immediately, regardless of the hello and hold timers. When a timer expires, the router transitions to a new HSRP state

HTH Richard

[hemadri37]

Dear Richard,

Thanks for posting. In my case both tracking interfaces are also down.

but in logs i didnot find any flaps or state changes of HSRP.

Is this related to timeout by server

[Richard Bradfield]

the arp timeout of only 5 seconds cannot help, can you put that back to default

[hemadri37]

Dear Richards,

Thanks. i will try with the option you suggested.

will update once i finish.

[rasmus.elmholt]

Hi

As i see it the timers are dangorous as Richard said. If it misses one Hello HSRP could change states.

Could you share the output from "show standby" command?

I see you have disabled CEF on the interface as well, is this a lab environment? The problems could be caused by high CPU utilization as well.

What does the "show proc cpu hist" command say?

[hemadri37]

Hi,

It is live system and not lab environment.

output of show standby

SW1

SW1#sh standby
Vlan105 - Group 101
  State is Active
    268 state changes, last state change 4y29w
  Virtual IP address is 172.31.248.6
  Active virtual MAC address is 0000.0c07.ac65
    Local virtual MAC address is 0000.0c07.ac65 (v1 default)
  Hello time 1 sec, hold time 2 sec
    Next hello sent in 0.352 secs
  Preemption enabled
  Active router is local
  Standby router is 172.31.248.5, priority 80 (expires in 1.584 sec)
  Priority 85 (configured 105)
    Track interface GigabitEthernet1/5 state Down decrement 10
    Track interface GigabitEthernet1/4 state Down decrement 10
  Group name is "hsrp-Vl105-101" (default)

SW2

SW2#sh standby
Vlan105 - Group 101
  State is Standby
    337 state changes, last state change 4y29w
  Virtual IP address is 172.31.248.6
  Active virtual MAC address is 0000.0c07.ac65
    Local virtual MAC address is 0000.0c07.ac65 (v1 default)
  Hello time 1 sec, hold time 2 sec
    Next hello sent in 0.016 secs
  Preemption enabled
  Active router is 172.31.248.4, priority 85 (expires in 1.184 sec)
  Standby router is local
  Priority 80 (default 100)
    Track interface GigabitEthernet1/4 state Down decrement 10
    Track interface GigabitEthernet1/5 state Down decrement 10
  Group name is "hsrp-Vl105-101" (default)

Also there is no high utilization of CPU as i checked.

[Richard Bradfield]

Hmm,

looks like might be a server problem, can you connect from another device,can you do continual pings to the 172.31.248.6 address..any timeouts? if so is it the same if you ping the individual address .4 and .5

[hemadri37]

Dear Richard,

I had done continous pings from server and found no time outs. can you please tell whether the command in HSRP (ARP timeout 5 seconds) has got any thing to do with the timeout in server when tries to access HSRP ip.

[Richard Bradfield]

very likely, many years ago I had a problem where the ARP had been set very low,this caused all sorts of problems across the network, please set it to default