show ha configuration

Prev Next

Displays the configuration settings for a Central Management System High Availability (HA) cluster.

Note

For more information about Central Management System HA, see the Central Management System High Availability Guide.

Syntax

show ha configuration

Parameters

None

Output fields

The following table describes the output fields for this command.

Field

Description

CMS HA Cluster Settings

License installed

Whether the license is installed.

Virtual IP address

The virtual IP (VIP) address used to access the Web UI.

NOTE: The value for this field is 0.0.0.0 if no VIP address is configured.

Authkey md5sum

The authentication key used to encrypt the traffic between the two nodes. The same key is shown for both nodes because the key is shared.

Auto-failover

Whether the primary node will automatically fail over to the secondary node if certain conditions are met.

Split-brain auto-shutdown

Whether the secondary node's cluster engine will automatically be stopped in a split-brain condition after the cluster manager selects the primary node.

Replicating

Configuration—Whether the replication of configuration data is enabled.

Alerts—Whether replication of alert data is enabled.

Security content—Whether replication of software downloads from the DTI network is enabled.

Cluster Communications

Default Interface

The name of the default HA interface, whether it is enabled, and the IP address and hostname of each node in the cluster for which the interface is configured.

Backup Interface

The name of the backup HA interface, whether it is enabled, and the IP address and hostname of each node in the cluster for which the interface is configured.

Cluster Resources

sys_disk_monitor enabled

Whether the resource agent that monitors available disk space is enabled.

sys_ether1_monitor enabled

Whether the resource agent that monitors the management (ether1) interface is enabled.

fe_address enabled

Whether the resource agent that monitors and manages the cluster virtual IP (VIP) address is enabled.

fe_correlator enabled

Whether the resource agent that monitors and manages the correlation of malicious URL events detected by a managed Network Security appliance with email events detected by a managed EX Series appliance is enabled.

fe_cmsapi enabled

Whether the resource agent that monitors and manages the Central Management System API process is enabled.

fe_dbmgd enabled

Whether the resource agent that monitors and manages a database management process is enabled.

fe_aggregator enabled

Whether the resource agent that monitors and manages the aggregation of alert data from managed appliances is enabled.

fe_aggr enabled

Whether the resource agent that monitors and manages the alert aggregation from Email Security - Cloud to an on-premises Central Management System appliance is enabled.

fe_fedb enabled

Whether the resource agent that monitors and manages the FireEye database service is enabled.

fe_webui enabled

Whether the resource agent that monitors and manages the Web UI service is enabled.

fe_redis enabled

Whether the resource agent that monitors the Redis server on the Central Management System appliance is enabled.

fe_peer_service enabled

Whether the resource agent that monitors and manages the service that handles interactions among Central Management System appliances in different domains that are licensed to use the CMS Peer Service is enabled.

fe_notification enabled

Whether the resource agent that monitors and manages the service that sends malware alert notifications is enabled.

fe_http enabled

Whether the resource agent that monitors and manages Central Management System Web services is enabled.

fe_appmgrd enabled

Whether the resource agent that monitors and manages the appliance update orchestration process is enabled.

Examples

The following example displays the cluster configuration on node1 in the default single-interface configuration. In this configuration, ether1 is the default HA interface, and there is no backup HA interface, VIP address, or IP routing.

node1 # show ha configuration
CMS HA Cluster Settings:
   License installed:             yes
   Authkey md5sum:                XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
   Virtual IP address:            0.0.0.0
   Auto-failover:                 yes
   Split-brain auto-shutdown:     no
   Replicating:
      Configuration:              yes
      Alerts:                     yes
      Security content:           yes

Cluster Communications:

   Default Interface:      ether1
     Enabled:              yes
     Members (ether1):     10.0.1.1/node1, 10.0.1.2/node2
   Backup Interface:       ether3
     Enabled:              no
     Members (ether3):     0.0.0.0/node1,

Cluster Resources:
   sys_disk_monitor enabled:    yes
   sys_ether1_monitor enabled:  yes
   fe_address enabled:          no
   fe_correlator enabled:       yes
   fe_cmsapi enabled:           yes
   fe_dbmgd enabled:            yes
   fe_aggregator enabled:       yes
   fe_aggr enabled:             yes
   fe_fedb enabled:             yes
   fe_webui enabled:            yes
   fe_redis enabled:            yes
   fe_peer_service enabled:     yes
   fe_notification enabled:     yes
   fe_http enabled:             yes
   fe_appmgrd enabled:          yes

The following example displays the cluster configuration on node1 in the dual-interface LAN configuration.

node1 # show ha configuration
CMS HA Cluster Settings:
   License installed:          yes
   Authkey md5sum:             XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
   Virtual IP address:         0.0.0.0
   Auto-failover:              yes
   Split-brain auto-shutdown:  no
   Replicating:
     Configuration:            yes
     Alerts:                   yes 
     Security content:         yes

Cluster Communications:

  Default Interface:      ether3
     Enabled:             yes
     Members (ether1):    10.0.0.1/node1, 10.0.0.2/node2,
  Backup Interface:       ether3
     Enabled:             yes
     Members (ether3):    10.0.1.1/node1, 10.0.1.2/node2,

Cluster Resources:  
   sys_disk_monitor enabled:    yes
   sys_ether1_monitor enabled:  yes
   fe_address enabled:          no
   fe_correlator enabled:       yes
   ...

User role

Admin, Operator, or Monitor

Command mode

Enable

Supported appliances

This command is supported on the following appliances running the specified releases or later:

  • Central Management System: Before Release 6.4.0. The output fields changed in Release 7.7.0 and Release 8.3.0.