Hi Angus,
According to documentation:
http://www.cisco.com/en/US/tech/tk583/tk372/technologies_white_paper0900aecd80278edf.shtml
What your are experiencing is not a bug and it is considered as a limitation or behavior
of this feature:
" When one of the interfaces of an active router goes down, the standby router takes over
as active and handles all the operations. However, the previous active
router undergoes a reload and eventually stabilizes as the standby router (if the priority
of the router is at or below that of the current active router)."
That is why after the Gi0/0 went down the active router reloaded:
*Nov 10 13:13:54.409: %TRACKING-5-STATE: 2 interface Gi0/0 line-protocol Up->Down
%RF_INTERDEV-4-RELOAD: % RF induced self-reload
I guess that port was your IPC link. The IPC link is where the hello packets of both routers are passed.
If you shutdown the interface of the router or the port of the switch where the interface
is connected, the active router would not receive hello packets and
standby router would take the state of being active causing the active router to reload."
Also, this is "normal" when the Routers are connected back to back:
" Routers must be connected using a hub or a switch. If routers are
connected back to back, any time the active router reloads, the standby router also
reloads. This arrangement defeats the purpose of IPsec HA."
This is also documented as DDTS:
CSCee37674
IPsec HA router reloads when HSRP i/f goes down
The HA router reloads due to a 'RF induced reload' whenever the
crypto+hsrp interface is shut down. This is documented as expected behavior.
If you shutdown the interface of the router or the port of the switch
where the interface is connected, the active router would not receive hello packets and
standby router would take the state of being active causing the active router to reload.
So what you see is expected upon the IPC link going down. If you want to avoid it try to have your hello passing through L2 hub or switch.
Hope this helps,
Nik
HTH,
Niko
