According to the Cisco documentation the "standby preempt delay reload" command is used to delay preemption after a reload. It also states that the "standby delay reload" is only used to delay HSRP group initialization.
standby preempt delay reload
http://www.cisco.com/en/US/docs/ios/ha/command/reference/ha_s3.html#wp1116351
reload seconds | (Optional) Specifies the preemption delay, in seconds, after a reload only. This delay period applies only to the first interface-up event after the router has reloaded. |
standby delay reload
http://www.cisco.com/en/US/docs/ios/ha/command/reference/ha_s3.html#wp1115877
The standby delay minimum reload interface configuration command delays HSRP groups from initializing for the specified time after the interface comes up.
This command is separate from the standby preempt delay interface configuration command, which enables HSRP preemption delay.
This does not make any mention that using the "standby delay reload" command and not using the reload option in the "standby preempt delay" command would disable preemtion on a reload but this is what I'm observing in testing. When I reload the active router it does not preempt but when I bounce the interface it does. I'm really looking for some documentation that confirms this rather than base production on an assumption.
Following is the configurations of my two standby interfaces.
R1
interface GigabitEthernet0/2
ip address 10.2.2.6 255.255.255.248
standby delay reload 120
standby 0 ip 10.2.2.1
standby 0 priority 110
standby 0 preempt
standby 0 name external
standby 0 track GigabitEthernet0/1 20
crypto map pfg-map redundancy external stateful
R2
interface GigabitEthernet0/2
ip address 10.2.2.4 255.255.255.248
standby delay reload 120
standby 0 ip 10.2.2.1
standby 0 priority 110
standby 0 preempt
standby 0 name external
standby 0 track GigabitEthernet0/1 20
crypto map pfg-map redundancy external stateful
I understand that my priorities are the same but the active router should be selected based on the higher IP address (10.2.2.6) when the HSRP coup (preemption) is sent.
Why am I doing this you might ask. You'll see I have the crypto map statement for stateful IPSec failover and according to that documentation this is the recommended configuration and the desired action of the configuration.
http://www.cisco.com/en/US/docs/ios/sec_secure_connectivity/configuration/guide/sec_failover_ipsec.html#wp1027195
The devices are acting according to this document but it does not appear to be acting according to the command documents.
The IP addresses on the HSRP-tracked interfaces of the standby and active routers should both be either lower or higher on one router than the other. In the case of equal priorities (an HA requirement), HSRP will assign the active state on the basis of the IP address. If an addressing scheme exists so that the public IP address of Router A is lower than the public IP address of Router B, but the opposite is true for their private interfaces, an active/standby-standby/active split condition could exist which will break connectivity.
According to the RFC 2281 the router "may" send a coup message if configured to preemmp indicating it is optional.
Preemption capability
If a router has higher priority than the active router and preemption is configured, it MAY take over as the active router using a Coup message.
To recap my question is; Where is the Cisco documentation that indicates a coup is not sent on reload in a configuration like mine?
Any help would be greatly appreciated.
