Starts or restarts the cluster engine on a node. When you use the CLI to configure a new cluster, you must manually start the cluster engine on each node. When you use the configuration wizard to configure a new cluster, the cluster engine on each node starts automatically. The node that starts first takes the primary role.
You cannot restart the cluster engine on the primary node if the secondary node is running. You must either stop the cluster engine on the secondary node first, or fail over to the secondary node, which changes the role of the primary node to secondary.
Important
When you restart the cluster engine on the secondary node, if alert replication is enabled, alert data is replicated from the primary node to the secondary node. During this process, do not perform any cluster operation or add or remove appliances from the Central Management System appliance. Use the
show ha statuscommand to confirm that the synchronization is finished. See the second example below for the status messages to expect during this process.
Syntax
ha engine restart
Parameters
None
Examples
The following example restarts the cluster engine on the primary node.
node1 (config) # ha engine restart success Please check the status with CLI 'show status' in a few seconds. node1 (config) # show ha status ...
The following example restarts the cluster engine on the secondary node, and monitors the status as alert data is synchronized from the primary node.
node2 (config) # ha engine restart success Please check the status with CLI 'show status' in a few seconds. node2 (config) # show ha status --------------- ALERT: Base database synchronization in progress The database synchronization from primary node (node1) to the secondary node (node2) is in progress. This process may take several minutes depending on the size of aggregated data on the primary node. During this process please do NOT restart HA engine or any other process on any of the CMS HA nodes. Also, please do not add or remove any appliance. You may continue reviewing alerts on the primary node. The rsync process started on node2 at Wed Oct 28 23:50:01 UTC 2015. -------------------- Cluster Status: Status: running Primary Node: node1 ... node2 (config) # show ha status --------------------- INFO: CMS HA cluster is ready The database synchronization from primary node (node1) to node2 is completed and CMS HA cluster is ready for normal CMS operations. All activities must be performed on the primary node i.e node1. You may use CLI on secondary node (node2) to review CMS configuration and aggregated alerts. The cluster was formed on Thu Oct 29 01:37:07 UTC 2015. Please review the primary status to make sure CMS HA cluster is healthy. ------------ Cluster Status ... Status: running Primary Node: node1 ...
User role
Admin
Command mode
Config
Supported appliances
This command is supported on the following appliances running the specified releases or later:
Central Management System: Before Release 6.4.0.
Note
For more information about Central Management System HA, see the Central Management System High Availability Guide.