How to reset a single host

This section contains instructions on how to gracefully reset a software malfunctioned host in a running system. In order to allow the high availability mechanism to take effect, only one host can be reset at a time.

Finding a blade's location A blade’s host name uses the following naming convention: blade-198-18-{chassis ID}-{blade ID} For example, in a blade named blade-198-18-1-3, the number 1 represents the chassis ID and 3 represents the blade ID. Therefore, the blade is the third blade to the left on the first chassis. The internal IP of the blade is 198.18.1.3.

Finding the correct virtual machine instance A virtual machine instance’s host name is follows a naming convention: blade-10-0-{chassis ID}-{blade ID}. A host named "blade-10-0-1-3" means that "1" represents the chassis ID and the "3" represents the blade ID. The internal IP of the blade is 10.0.1.3. The chassis ID and blade ID can be viewed in the bootloader menu (see Bootloader). It’s recommended to name the virtual machine instances accordantly during the cluster deployment process.

To reset a single host:

1. Access the bootloader of the malfunctioned host (see Bootloader), enter the Reset OS option and wait until it finishes rebooting.
2. Monitor the status of the blade or host.
   1. If it is a FortiAnalyzer-BigData unit, monitor the status of the blade from the DMM (see Remotely control blades via CMM in Connect to the Chassis Management Module). Wait until the host OS completes booting. This may take 5-10 minutes.
   2. If it is a FortiAnalyzer-BigData-VM, monitor the status of the host from the web remote console. Wait until the host OS completes booting. This may take 5-10 minutes.

      Cluster failover When resetting the Controller host in either scenario, allow up to 15 minutes for the failover mechanism to take effect. Once the mechanism is in effect, the Security Event Manager IP and Cluster Manager can be accessed with the GUI.

3. After the host reboots and joins the cluster, it will appear in Cluster Manager > Hosts.
4. From the Hosts page, click Assign Role to recover the role on the host. The new host should display a pending label. When the Assign Role job is complete, the host reset is done.
5. (Recommended) After the Assign Role job is completed, rebalance the data across the cluster. See How to rebalance the data