Main HA-Cluster CLI commands
In the primary (master) and secondary (primary slave) node, you must enable interface port1 so that they can communicate with each other.
hc-settings |
Configure the unit as a HA-Cluster mode unit. Configure cluster failover IP set. |
hc-status -l |
List the status of HA-Cluster units. |
hc-slave |
|
hc-master -s<10-100> |
Turn on file scan on the primary node with 10% to 100% processing capacity. |
hc-master -r<slave serial number> |
Remove the worker unit with the specified serial number from the primary node. |
After removing a worker node, use hc-status -l
on the primary node to verify that the worker unit has been removed.
Example configuration
This example shows the steps for setting up an HA-Cluster using three FortiSandbox 3000D units.
Step 1 - Prepare the hardware:
The following hardware will be required:
- Nine cables for network connections.
- Three 1/10 Gbps switches.
- Three FortiSandbox 3000D units with proper power connections (units A, B, and C).
Put the primary and secondary nodes on different power circuits. |
Step 2 - Prepare the subnets:
Prepare three subnets for your cluster (customize as needed):
- Switch A: 192.168.1.0/24: For system management.
- Switch B: 192.168.2.0/24: For internal cluster communications.
- Switch C: 192.168.3.0/24: For the outgoing port (port 3) on each unit.
- Gateway address: 192.168.3.1
Step 3 - Setup the physical connections:
- Connect port 1 of each FortiSandbox device to Switch A.
- Connect port 2 of each FortiSandbox device to Switch B.
- Connect port 3 of each FortiSandbox device to Switch C.
Step 4 - Configure the primary (master):
- Power on the device (Unit A), and log into the CLI (see Connecting to the Command Line Interface).
- Configure the port IP addresses and gateway address with the following commands:
- Configure the device as the primary node and its cluster failover IP for Port1 with the following commands:
- Review the cluster status with the following command:
set port1-ip 192.168.1.99/24
set port2-ip 192.168.2.99/24
set port3-ip 192.168.3.99/24
hc-settings -sc -tM -nMasterA -cTestHCsystem -ppassw0rd -iport2
hc-settings -si -iport1 -a192.168.1.98/24
For information about CLI commands, see the FortiSandbox CLI Reference Guide on the Fortinet Document Library.
hc-status -l
Other ports on the device can be used for file inputs.
Step 5 - Configure the secondary (primary slave):
- Power on the device (Unit B), and log into the CLI.
- Configure the port IP addresses and gateway address with the following commands:
- Configure the device as the secondary node with the following commands:
- Review the cluster status with the following command:
set port1-ip 192.168.1.100/24
set port2-ip 192.168.2.100/24
set port3-ip 192.168.3.100/24
hc-settings -sc -tP -nPslaveB -cTestHCsystem -ppassw0rd -iport2
hc-settings -l
hc-slave -a -s192.168.2.99 -ppassw0rd
hc-status -l
Step 6 - Configure the worker (regular slave):
- Power on the device (Unit C), and log into the CLI.
- Configure the port IP addresses and gateway address with the following commands:
- Configure the device as a worker node with the following commands:
- Review the cluster status with the following command:
set port1-ip 192.168.1.101/24
set port2-ip 192.168.2.101/24
set port3-ip 192.168.3.101/24
hc-settings -sc -tR -cTestHCsystem -ppassw0rd -nSlaveC -iport2
hc-settings -l
hc-slave -a -s192.168.2.99 -ppassw0rd
hc-status -l
Step 7 - Configure other settings:
VM Image settings and network settings, such as default gateway, static route, and DNS servers etc., should be configured on each unit individually. Scan related settings, such as the scan profile, should be set on primary unit only; they will be synchronized to the worker node. For details, see Role of the primary (master) and worker (slave) node.
Step 8 - Finish:
The HA-Cluster can now be treated like a single, extremely powerful standalone FortiSandbox unit.
In this example, files are submitted to, and reports and logs are available over IP address 192.168.1.99.
FortiSandbox 3500D is configured as a cluster system, with blade 1 configured as the primary node, blade 2 as the secondary node, and the other blades as worker nodes. |
If you use the GUI to change a role from worker to standalone, you must remove the worker from the primary using the CLI command |