Manually fails over the primary node to the secondary node. After the failover completes, the nodes switch roles. The original primary node becomes the secondary node, and the original secondary node becomes the primary node. The following configurations fail over:
Central Management System appliance management configuration (except interface, licensing, and host-specific configurations)
Aggregated alerts database (if alert data replication is enabled)
Security content updates (if security content replication is enabled)
Syntax
ha engine failover
Parameters
None
Example
The following example fails over the primary node (node1) to node2. It then monitors the failover as node1's role changes from primary, to unknown, and finally to secondary.
node1 (config) # ha engine failover Type 'YES' to confirm failover: YES success Please check the status with CLI 'show ha status' in few seconds. node1 (config) # show ha status Cluster Status ... Status: running Primary Node: node1 (self) ... node1 (config) show ha status Cluster status: ... Status: stopped Primary Node: unknown ... node1 (config) # show ha status Cluster Status ... Status: running Primary Node: node2 ...
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 High Availability Guide.