To troubleshoot the cluster configuration
If the cluster members list and the dashboard does not display information for both cluster units the FortiGate units are not functioning as a cluster. See Troubleshooting full mesh HA on page 1463 to troubleshoot the cluster.
To add basic configuration settings and the redundant interfaces
Use the following steps to add a few basic configuration settings. Some steps use the CLI and some the web- based manager.
1. Log into the cluster CLI.
2. Add a password for the admin administrative account.
config system admin edit admin
set password <password_str>
end
3. Temporarily delete the default route.
You cannot add an interface to a redundant interface if any settings (such as the default route) are configured for it.
config router static delete 1
end
4. Go to System > Network > Interface and select Create New to add the redundant interface to connect to the
Internet.
5. Add the redundant interface to connect to the Internet.
config system interface edit Port1_Port2
set type redundant
set member port1 port2 end
6. Add the redundant interface to connect to the internal network.
config system interface edit Port3_Port4
set type redundant
set member port3 port4 end
The virtual MAC addresses of the FortiGate interfaces change to the following. Note that port1 and port2 both have the port1 virtual MAC address and port3 and port4 both have the port3 virtual MAC address:
- port1 interface virtual MAC: 00-09-0f-09-00-00
- port10 interface virtual MAC: 00-09-0f-09-00-01 l port11 interface virtual MAC: 00-09-0f-09-00-02 l port12 interface virtual MAC: 00-09-0f-09-00-03 l port13 interface virtual MAC: 00-09-0f-09-00-04 l port14 interface virtual MAC: 00-09-0f-09-00-05 l port15 interface virtual MAC: 00-09-0f-09-00-06 l port16 interface virtual MAC: 00-09-0f-09-00-07 l port17 interface virtual MAC: 00-09-0f-09-00-08 l port18 interface virtual MAC: 00-09-0f-09-00-09
- port19 interface virtual MAC: 00-09-0f-09-00-0a
- port2 interface virtual MAC: 00-09-0f-09-00-00 (same as port1)
- port20 interface virtual MAC: 00-09-0f-09-00-0c
- port3 interface virtual MAC: 00-09-0f-09-00-0d
- port4 interface virtual MAC: 00-09-0f-09-00-0d (same as port3)
- port5 interface virtual MAC: 00-09-0f-09-00-0f l port6 interface virtual MAC: 00-09-0f-09-00-10 l port7 interface virtual MAC: 00-09-0f-09-00-11 l port8 interface virtual MAC: 00-09-0f-09-00-12 l port9 interface virtual MAC: 00-09-0f-09-00-13
7. Go to Router > Static > Static Routes.
8. Add the default route.
config router static edit 1
set dst 0.0.0.0 0.0.0.0 set gateway 172.20.120.2 set device Port1_Port2
end
To configure HA port monitoring for the redundant interfaces
1. Enter the following command to configure port monitoring for the redundant interfaces:
config system ha
set monitor Port1_Port2 Port3_Port4 end
Troubleshooting full mesh HA
Troubleshooting full mesh HA clusters is similar to troubleshooting any cluster (see FGCP configuration examples and troubleshooting on page 1354 or Troubleshooting virtual clustering on page 1448). The configuration and operation of a full mesh HA cluster is very similar to the configuration and operation of a standard cluster. The only differences relate to the configuration, connection, and operation of the redundant interfaces and redundant switches.
- Make sure the redundant interfaces and switches are connected correctly. With so many connections it is possible to make mistakes or for cables to become disconnected.
- Confirm that the configuration of the cluster unit 802.3ad Aggregate or Redundant interfaces is correct according to the configuration procedures in this chapter.
- In some configurations with some switch hardware, MAC-learning delays on the inter-switch links on the surrounding topologies may occur. The delays occur if the gratuitous ARP packets sent by the cluster after a failover are delayed by the switches before being sent across the inter-switch link. If this happens the surrounding topologies may be delayed in recognizing the failover and will keep sending packets to the MAC address of the failed primary unit resulting in lost traffic. Resolving this problem may require changing the configuration of the switch or replacing them with switch hardware that does not delay the gratuitous ARP packets.