HSRP not working on Cisco ASR 1001

[Fishel Erps]

Hello,

I have two ASR routers in a multi-homed BGP scenario.  I have SLA conditions checking the reachability of an IP via a specific interface on the primary router.  Each router is connected to a specific ISP, and they have different bandwidths.  As such, router 1 is always preferred as primary, and router 2 is always preferred as secondary.  In any test that I conduct, the IP SLA Monitor function as expected.  All debugs show the conditions being met, and triggered. 

The issue that I'm having is that the active->standby never happens on R1, and the standby-active never happens on R2.  R1s value decrements correctly, resulting in R2 having a higher value.  This should be resulting in the state change, but it never does.  The configs are correct, and running identically (save for actual IPs) on many other non-ASR routers.

Can anyone advise on what the issue might be?

R1

interface GigabitEthernet0/0/1
 ip address 192.168.200.2 255.255.254.0
 no ip redirects
 standby 1 ip 192.168.200.1
 standby 1 priority 110
 standby 1 preempt
 standby 1 track 1 decrement 10
 speed 1000
 no negotiation auto
 cdp enable
end

ip sla 1
 icmp-echo 8.8.8.8 source-ip 10.10.10.1
ip sla schedule 1 life forever start-time now

track 1 ip sla 1 reachability

R1#sho stand b
                     P indicates configured to preempt.
                     |
Interface   Grp  Pri P State   Active          Standby         Virtual IP
Gi0/0/1     1    110 P Active  local           192.168.200.3   192.168.200.1
R1#

R2

interface GigabitEthernet0/0/1
 ip address 192.168.200.3 255.255.254.0
 no ip redirects
 standby 1 ip 192.168.200.1
 standby 1 priority 105
 speed 1000
 no negotiation auto
 cdp enable
end

R2#sho stand b
                     P indicates configured to preempt.
                     |
Interface   Grp  Pri P State   Active          Standby         Virtual IP
Gi0/0/1     1    105   Standby 192.168.200.2   local           192.168.200.1
R2#

[adamtodd16]

Config looks correct, as you said. 

Can you post show standby all for both devices? 

[Fishel Erps]

R1

R1#sho stand all
GigabitEthernet0/0/1 - Group 1
  State is Active
    5 state changes, last state change 5w0d
  Virtual IP address is 192.168.200.1
  Active virtual MAC address is 0000.0c07.ac01
    Local virtual MAC address is 0000.0c07.ac01 (v1 default)
  Hello time 3 sec, hold time 10 sec
    Next hello sent in 1.760 secs
  Preemption enabled
  Active router is local
  Standby router is 192.168.200.3, priority 105 (expires in 9.680 sec)
  Priority 110 (configured 110)
    Track object 1 state Up decrement 10
  Group name is "hsrp-Gi0/0/1-1" (default)
R1#

R2

136W21-DC-WAN-02#sho stand all
GigabitEthernet0/0/1 - Group 1
  State is Standby
    7 state changes, last state change 5w0d
  Virtual IP address is 192.168.200.1
  Active virtual MAC address is 0000.0c07.ac01
    Local virtual MAC address is 0000.0c07.ac01 (v1 default)
  Hello time 3 sec, hold time 10 sec
    Next hello sent in 0.064 secs
  Preemption disabled
  Active router is 192.168.200.2, priority 110 (expires in 7.808 sec)
  Standby router is local
  Priority 105 (configured 105)
  Group name is "hsrp-Gi0/0/1-1" (default)

R2#

[adamtodd16]

Just noticed you don't have R2 set to preempt. Without it, the priority really doesn't mean anything.

Should add the following on R2:

 standby 1 preempt 

[Fishel Erps]

The preempt command is supposed to just indicate that the specified router should take the VGW back once it becomes the higher value again.  R1 has it because we want R1 to take back control.  R2 shouldn't have it because there is no R3 with a lesser value that it should take back control from.  Is this not correct?

[adamtodd16 · Accepted solution]

Please see the documentation at:

http://www.cisco.com/c/en/us/support/docs/ip/hot-standby-router-protocol-hsrp/13780-6.html

Relevant line:

standby 1 preempt

!--- Allows the router to become the active router when the priority 
!--- is higher than all other HSRP-configured routers in the hot standby group. 
!--- If you do not use the standby preempt command in the configuration 
!--- for a router, that router does not become the active router, even if 
!--- the priority is higher than all other routers. 

[Fishel Erps]

Ok....I made the change, and I will test after-hours.  I'll let you know.

[adamtodd16]

Sounds good!

[Fishel Erps]

Adam,  Thank you for your help.  Adding the preempt verbiage to the config on the standby router did indeed solve the issue.  

[adamtodd16]

Happy to help! Glad you got it working.