HSRP Configure

[_Ratha_]

Base on diagram attached bellow:

R1 Configure

interface FastEthernet0/0
ip address 172.1.1.1 255.255.255.0
no shutdown
duplex half
standby version 2
standby 1 ip 172.1.1.254
standby 1 track fa0/0

standby 1 track fa1/0
standby 1 preempt

interface FastEthernet1/0
ip address 172.2.2.1 255.255.255.0
no shutdown
duplex auto
speed auto
standby version 2
standby 1 ip 172.2.2.254
standby 1 priority 120
standby 1 preempt

standby 1 track fa0/0

standby 1 track fa1/0

R2 Configure

interface FastEthernet0/0
ip address 172.1.1.2 255.255.255.0
no shutdown
duplex half
standby version 2
standby 1 ip 172.1.1.254

standby 1 track fa0/0

standby 1 track fa1/0

interface FastEthernet1/0
ip address 172.2.2.2 255.255.255.0
no shutdown
duplex auto
speed auto
standby version 2
standby 1 ip 172.2.2.254

standby 1 track fa0/0

standby 1 track fa1/0

Problem is that when one of interface on R1(active) down, PC connect to cloud 3 cannot access to ESW1.

if interface fa0/0 down then show standby

show standby 

R1                                     R2

fa0/0                            fa0/0

standby                   Active

fa1/0                            fa1/0

active                        standby

so both side cannot communicate each other( PC connected to cloud 3 cannot contact to ESW1)

Q: How to fix this issue? How to make fa1/0 to standby if FA0/0 down?

Thank for support

Ratha

[Philip D'Ath · Accepted solution]

Change the standby priority from 120 to 105.

I'm not sure what platform or version you are using, but you would normally have some track commands, like:

track 1 interface fa0/0 ip routing

Then you tell the interface to use the tracked object above.

int fa1/0
  standby track 1

[Richard Burts · Accepted solution]

Philip has correctly identified an issue about tracking interfaces for HSRP. HSRP track looks for the interface status to change to down to trigger the track event. That works for point to point serial interfaces. But frequently for Ethernet interfaces you may lose connectivity over the interface but the interface status remains up. So frequently we need to use track commands to force the Ethernet interface into the down state when connectivity is lost.

But there is a more fundamental problem with this config. Even with the track command HSRP would not fail over as the original poster wants it to. The issue is that HSRP on R2 does not include the preempt command. Without preempt the router can not take over the active role even if the priority has changed. So the original poster needs to add the preempt command in HSRP on both interfaces of R2.

HTH

Rick

[_Ratha_]

Dear Philip & Richard,

Thank for your great solution.

[Richard Burts]

You are quite welcome. I am glad that our suggestions were helpful. Thank you for using the rating system to mark this question as answered. This will help other readers in the forum to identify discussions that have helpful information.

HTH

Rick

[Genius.ashraff]

Hi,

    Did after changing the Standby Priority value did it works

[_Ratha_]

after changing the Standby Priority value it not completely work, I have to add preempt on R2. However priority is a part of corrected answer.