Jump to content


Photo

Understand the cause of HA failover in Barracuda NG-FW

HA failover NG-FW Barracuda VF1000

  • Please log in to reply
3 replies to this topic

#1 Harilal B

Harilal B
  • Members
  • 4 posts

Posted 02 March 2019 - 12:39 AM

Hello Members,
 
I'm a newbie with Barracuda NG-FW, I’m using model VF1000 configured as cluster for HA. Boxes are managed by control center.
 
From where I can find the reason for automatically fail back between boxes to understand the causes of failover. I tried to look into the events, but I couldn’t find anything related.
 
Many thanks for your help.
 
Regards,
Harilal B
 


#2 Michael Zoller

Michael Zoller
  • Barracuda Team Members
  • 205 posts

Posted 04 March 2019 - 08:53 AM

a takeover is triggered after a 10-15 second delay in answering the heartbeat connection. Check out the documentation on the takeover procedure here :

https://campus.barra...-availability/



#3 Harilal B

Harilal B
  • Members
  • 4 posts

Posted 04 March 2019 - 09:07 AM

Please advice from where I can find the heartbeat connection logs to understand the cause of failover.

#4 Michael Zoller

Michael Zoller
  • Barracuda Team Members
  • 205 posts

Posted 04 March 2019 - 09:11 AM

Check the Firewall Live or Firewall History for the UDP 801 connection between your HA pair. But the reason for the failover will most likely be a network interruption that blocked this connection. It could of course also be caused by misconfigurations of the virtual server or in very rare cases a bug.  If you configured virtual server monitoring, if one of the configured monitoring checks fails, that would also result in a failover.