Connect the M1 and M2 interfaces for HA heartbeat communication
High Availability
Connect the M1 and M2 interfaces before enabling HA. Enabling HA moves heartbeat
communication between the FIM modules in the same chassis to the M1 and M2
interfaces. So if these interfaces are not connected before you enable HA, FIM
modules in the same chassis will not be able to communicate with each other.
Heartbeat packets are VLAN packets with VLAN ID 999 and ethertype 9890. The MTU value for the M1 and M2
interfaces is 1500. You can use the following commands to change the HA heartbeat packet VLAN ID and
ethertype values if required for your switches. You must change these settings on each FIM interface module. By
default the M1 and M2 interface heartbeat packets use the same VLAN IDs and ethertypes.
config system ha
set hbdev-vlan-id <vlan>
set hbdev-second-vlan-id <vlan>
set ha-eth-type <eth-type>
end
Using separate switches for M1 and M2 is recommended for redundancy. It is also
recommended that these switches be dedicated to HA heartbeat communication and
not used for other traffic.
If you use the same switch for both M1 and M2, separate the M1 and M2 traffic on the
switch and set the heartbeat traffic on the M1 and M2 Interfaces to have different
VLAN IDs. For example, use the following command to set the heartbeat traffic on M1
to use VLAN ID 777 and the heartbeat traffic on M2 to use VLAN ID 888:
config system ha
set hbdev-vlan-id 777
set hbdev-second-vlan-id 888
end
If you don't set different VLAN IDs for the M1 and M2 heartbeat packets q-in-q must be
enabled on the switch.
Sample switch configuration for a Cisco Catalyst switch. This configuration sets the interface speeds, configures
the switch to allow vlan 999, and enables trunk mode:
##interface config
interface TenGigabitEthernet1/0/5
description Chassis1 FIM1 M1
switchport trunk allowed vlan 999
switchport mode trunk
If you are using one switch for both M1 and M2 connections, the configuration would be the same except you
would add q-in-q support and two different VLANs, one for M1 traffic and one for M2 traffic.
59
FortiGate-7000
Fortinet Technologies Inc.
