Skip to main content
moby
New Member
April 18, 2018
Question

HA and Remote Link Failover

  • April 18, 2018
  • 1 reply
  • 15718 views
Hi All,   Running an active passive Fortigate cluster and OS 5.4.8 - -we need to have remote link failover working so that if a ping target cannot be reached x times then the cluster fails over. We cannot make any sense of the results, when the ping target fails the cluster takes several minutes to failover and this has no relation to our timers. Has any one else seen strange results like this? Is anyone else running it with good predictable and reliable results? If so in which firmware version. The config for HA and link-monitor is below:   config system ha     set group-name "xxxxxxx"     set mode a-p     set password ENC xxxxxxx     set hbdev "port1" 100 "port2" 50     set ha-mgmt-status enable     set ha-mgmt-interface "mgmt1"     set ha-mgmt-interface-gateway 10.200.254.250     set override enable     set priority 200     set monitor "port16" "port40"     set pingserver-monitor-interface "port20"     set pingserver-failover-threshold 5     config system link-monitor     edit "HA_Ping_Failover"         set srcintf "port20"         set server "10.10.10.1"         set interval 3         set timeout 3         set failtime 3         set recoverytime 3         set ha-priority 10   Any feedback appreciated.   Thanks, Moby.

1 reply

emnoc
New Member
April 19, 2018

Do you have the the flip imeout variable set

 

"set pingserver-flip-timeout"

 

But no, I have not seem any issues with HA failover due to remote-target  being unreachable. We like to set a  high threshold to avoid premature failover due to glitch or bump in our network.

 

Ken

 

 

moby
mobyAuthor
New Member
April 19, 2018

Hi Ken,

 

Ok thanks for the feedback - -yes we have tried it with the Flip Timeout set too -- but our problem is that it takes several minutes to fail over once the target is down. And that does not make any sense to me since our timers should mean it should failover in approx 9 seconds. We have a TAC case open and waiting....................

 

Thanks, Moby

emnoc
New Member
April 19, 2018

IIRC  link monitor had some issues back in v5.2.x maybe this rolled into 5.4.x ;)

 

Did you do any based level diagnostics  and  if so  what did it state?

 

   diag sys link-monitor interface <interface name >

 

 

Also did you execute log display and look for the sys event at the failure

 

  e.g

 

     execute log filter cat  1

     execute log display

 

Ken