Failover IP
Users are able to configure a cluster level fail-over IP, which will be set only on Master node. This fail-over IP can only be set on current Master node through the CLI. It should be in the same subnet of the port’s local IP. Clients, such as FortiGates, should point to the failover IP in order to use the HA functionality. When a fail-over occurs, failover IP will be applied on new Master node.
The Master node and Primary Slave node local IP will be kept locally during failover.
Example:
Here is an example to set a fail-over IP for port1.
> show
Configured parameters:
Port 1 IPv4 IP: 172.16.69.145/24 MAC: 14:18:77:52:37:72
Port 1 IPv6 IP: 2620:101:9005:69::145/64 MAC: 14:18:77:52:37:72
Port 2 IPv4 IP: 1.1.7.5/24 MAC: 14:18:77:52:37:73
Port 3 IPv4 IP: 192.168.199.145/24 MAC: 14:18:77:52:37:74
IPv4 Default Gateway: 172.16.69.1
> hc-settings -sc -tM -n145 -c3000d-cluster -p1234 -iport2
The unit was successfully configured.
> hc-settings -si -iport1 -a172.16.69.160/24
The external IP address 172.16.69.160 for cluster port1 was set successfully
> hc-settings -l
SN: FSA3KD3R16000xxx
Type: Master
Name: 145
HC-Name: 3000d-cluster
Authentication Code: 1234
Interface: port2
Cluster Interfaces:
port1: 172.16.69.160/255.255.255.0