FortiADC HA Both Primary/No Peers

[theOtherPadawan]

Anyone have an issue setting up an active-passive HA on FortiADC where both devices want to be Primary?
Neither see any peers.

Mac address spoofing is enabled on our virtual switches.
The thing that's weird is a 169.x.x.x IP is being assigned.
The devices cannot ping the other 169.x.x.x IP. 

(P) FORTIADCP001 # get system ha
mode                          : active-passive
hbdev                         : port4 
datadev                       : 
group-id                      : 14
group-name                    : group1
mgmt-status                   : disable
priority                      : 1
config-priority               : 10
override                      : enable
hb-interval                   : 2
arps                          : 5
hb-lost-threshold             : 6
arps-interval                 : 6
l7-persistence-pickup         : enable
l4-persistence-pickup         : enable
l4-session-pickup             : enable
auto-config-sync              : enable
monitor                       : port6 
remote-ip-monitor             : disable
boot-time                     : 30
ha-eth-type                   : 8890
hatrans-eth-type              : 8892
l2ep-eth-type                 : 8893
hb-type                       : multicast
 
(P) FORTIADCP001 # get system ha-status
Group ID: 14
Mode: active-passive
State: Primary
Config-Sync Source: N/A
Config-Sync: N/A
Init Done: Yes
Serial-Number: blah blah
Node Id: 0
IP Address: 169.x.x.x
MAC Address: blah blah
Last Change Time: Thu Jul 11 08:00:17 2024
Last Change Reason: Device initialization
 
Monitor Status
  System
    Harddisk: pass
  Link
    Up: port6
    Down:
 
Sync statistics:
                                           Sent           Received
L4 session and persistence sync pkts:      0              0
L7 persistence sync pkts:                  0              0
 
Device management errors:
Duplicate node id:     0
Image Version mismatch:      0
HA Version mismatch:      0
Group id mismatch:      0
Ha mode mismatch:      0
Ha node list mismatch:      0
Duplicate SN:      0
Basic Errors:      0
 
Peer Count: 0
 
(P) FORTIADCP001 #  



(P) FORTIADCP002 # get system ha
mode                          : active-passive
hbdev                         : port4 
datadev                       : 
group-id                      : 14
group-name                    : group1
mgmt-status                   : disable
priority                      : 9
config-priority               : 100
override                      : enable
hb-interval                   : 2
arps                          : 5
hb-lost-threshold             : 6
arps-interval                 : 6
l7-persistence-pickup         : enable
l4-persistence-pickup         : enable
l4-session-pickup             : enable
auto-config-sync              : enable
monitor                       : port6 
remote-ip-monitor             : disable
boot-time                     : 30
ha-eth-type                   : 8890
hatrans-eth-type              : 8892
l2ep-eth-type                 : 8893
hb-type                       : multicast
 
(P) FORTIADCP002 # get system ha-status
Group ID: 14
Mode: active-passive
State: Primary
Config-Sync Source: N/A
Config-Sync: N/A
Init Done: Yes
Serial-Number: blah blah
Node Id: 0
IP Address: 169.x.x.x
MAC Address: blah blah
Last Change Time: Thu Jul 11 08:00:33 2024
Last Change Reason: Device initialization
 
Monitor Status
  System
    Harddisk: pass
  Link
    Up: port6
    Down:
 
Sync statistics:
                                           Sent           Received
L4 session and persistence sync pkts:      0              0
L7 persistence sync pkts:                  0              0
 
Device management errors:
Duplicate node id:     0
Image Version mismatch:      0
HA Version mismatch:      0
Group id mismatch:      0
Ha mode mismatch:      0
Ha node list mismatch:      0
Duplicate SN:      0
Basic Errors:      0
 
Peer Count: 0
 
(P) FORTIADCP002 #  

[Anthony_E]

Hello,

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

Thanks,

[theOtherPadawan · Accepted solution]

For those having the same issue.

Disabling igmp snooping on our physical network switches (for just the HA vlan), resolved the issue for us. 

[Anthony_E]

Thanks a lot for sharing the solution!