How to reset a single host
This section contains instructions on how to gracefully reset a software malfunctioned Security Event Manager 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 is follows a naming convention: blade-10-0-{chass ID}-{blade ID}. A blade named "blade-10-0-1-3" means that "1" represents the chassis ID and the "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 10.0.1.3. |
To reset a single host:
- Access the bootloader of the malfunctioned host (see Bootloader), enter the Reset OS option and wait until it finishes rebooting.
- Monitor the status of the blade from the DMM (see Remotely control blades via CMM) Wait until the host OS completes booting. This may take 5-10 minutes.
Cluster failover
When resetting the Controller host, 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.
- After the host reboots and joins the cluster, it will appear in Cluster Manager > Hosts.
- 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.
- (Recommended) After the Assign Role job is completed, rebalance the data across the cluster. See How to rebalance the data