Nagaraja Thanthry Mon, 08/02/2010 - 08:22
User Badges:
  • Cisco Employee,


Typically this happens when the communication between the firewall through

failover link fails. If you are using a switch to connect the failover

ports, you need to see if they are active and are in forwarding state. If

you are using cable based failover method, then you need to check if the

cable is working.

Hope this helps.



Jitendriya Athavale Mon, 08/02/2010 - 09:20
User Badges:
  • Cisco Employee,

both go active during the following scenarios

**1 failover communications are not working well and the secondary reboots and finds that there is no active device and becomes active

**2 if all sorts of failover communication is lost. i mean the devices cannot communicate with each other from either the failover link nor the interfaces which are being monitored, so the standby thinks there is no active is as it does not get any hearbeat packets on ip port 107 on any of the interfaces

          ## to continue point 2, if at all you have a common switch (all the interface of firewall including failover are connected to this switch) and it crashed or rebooted


This Discussion