To view the enrollment status from the Central Management appliance:

Log in to the CLI of the Central Management appliance that manages the cluster.
Enable the CLI enable mode:
```
cm-hostname > enable
```

View the enrollment status:

cm-hostname # show cmc mvx cluster enrollment status

Examples

The following example shows the enrollment status for the nx-1 sensor.

nx-1 # show mvx cluster enrollment status

MVX Cluster Enrollment Status

    Enrollment Client:
        Status ok : yes
        Status description : enrolled
        Last checked at : 2019/07/26 20:42:01

    Enrollment Service:
        Auto enabled : yes
        Service address : CMS (DTIUser@10.11.121.13 : singleport)
        Preferred cluster : any (less loaded)
        Cloud enabled : no
        Cloud License enabled : no
        Connect on demand : no

Broker Info:
        Cluster Name : Cluster-Acme
        Broker Name : vx-1
        Broker ID : 002XXXXXXXX7
        Broker Address : 10.11.121.12
        Broker State : Connected
        Failure Reason : None
        Last Connection Attempt : 2019/06/27 18:14:04
        Connection Last Formed : 2019/06/27 18:14:04
        Connection Last Broken :

The following example shows the enrollment status for the vx-1 broker.

vx-1 # show mvx cluster enrollment status

MVX Cluster Enrollment Status

    Enrollment Client:
        Status ok : yes
        Status description : Ok
        Last checked at : 2019/07/26 20:42:01

    Enrollment Service:
        Auto enabled : yes
        Service address : CMS (DTIUser@10.11.121.13 : singleport)
        Preferred cluster :
        Cluster Name : Cluster-Acme
        Broker Name : vx-1 (self)
        Broker ID : 002XXXXXXXX7 (self)
        Broker Address : 10.11.121.12 (self)
        Broker State : N/A
        Failure Reason : N/A
        Last Connection Attempt : N/A
        Connection Last Formed : N/A
        Connection Last Broken : N/A
        Connect on demand : no

The following example shows the enrollment status for the fx-1 hybrid appliance.

fx-1 # show mvx cluster enrollment status

MVX Cluster Enrollment Status

    Enrollment Client:
        Status ok : yes
        Status description : enrolled
        Last checked at : 2019/07/26 20:42:01
        
    Enrollment Service:
        Auto enabled : yes
        Service address : CMS (DTIUser@10.11.121.13 : singleport)
        Preferred cluster : any (less loaded)
        Cloud enabled : no
        Cloud License enabled : no
        Connect on demand : no

    Broker Info:
        Cluster Name : Cluster-Acme
        Broker Name : vx-1
        Broker ID : 002XXXXXXXX7
        Broker Address : 10.11.121.12
        Broker State : Connected
        Failure Reason : None
        Last Connection Attempt : 2019/06/27 18:14:04
        Connection Last Formed : 2019/06/27 18:14:04
        Connection Last Broken :

The following example shows that the nx-1 and nx-2 sensors are enrolled with Cluster-
Acme and are connected to the vx-1 broker.

cm-5 (config) # show cmc mvx cluster enrollment status

SENSOR NAME     CLUSTER NAME     BROKER NAME     BROKER ADDRESS
===========     ============     ===========     ==============
nx-1            Cluster-Acme     vx-1            10.11.121.12
nx-2            Cluster-Acme     vx-1            10.11.121.12

Output fields

Field	Description
Enrollment Client
Status ok	Whether the enrollment client status is acceptable.
Status description	Description of the status (enrolled or unenrolled). If the appliance is not a sensor, local is the description, because the appliance uses its own MVX engine for analysis.
Last checked at	Date and time the enrollment client was last checked.
Enrollment Service
Auto enabled	Whether automatic enrollment is enabled.
Service address	Enrollment service type and address. The Central Management appliance manages the enrollment service for the sensors, hybrid appliances, and IVX clusters it manages.
Preferred cluster	The name of a preferred cluster, if one was configured as described in Enrolling with a preferred cluster . If none was configured, the value of this field is any (less loaded) to indicate that the sensor was enrolled with the cluster with the most capacity. (This field does not apply to brokers.)
Cloud enabled	Whether the sensor is able to send submissions to the FireEye Cloud MVX service for analysis. (This functionality is enabled by default when the Cloud License enabled field is yes).
Cloud License enabled	Whether the sensor has a valid and active CLOUD_MVX license.
Connect on demand	Whether the sensor or hybrid appliance connects to the enrollment service only when it has objects to submit for analysis. This field is yes for FireEye Cloud MVX deployments. This field is no for on-premises IVX cluster deployments.
Cluster Name	Name of the cluster with which the sensor or hybrid appliance is enrolled.
Broker Name	Hostname of the broker with which the sensor or hybrid appliance is connected.
Broker ID	Appliance ID of the broker.
Broker Address	IP address of the broker.
Broker State	State of the connection between the sensor or hybrid appliance and the broker node or between two broker nodes. Connected—The sensor or hybrid appliance and the broker node or the two broker nodes are connected. Disconnected—The sensor or hybrid appliance and the broker node or the two broker nodes are disconnected.
Failure Reason	Reason the connection failed, if any. Authentication Failure—The DTI credentials on the sensor or hybrid appliance are invalid. Authorization Failure—The sensor or hybrid appliance is using an invalid or inactive license. Enrollment Service Unavailable—The sensor or hybrid appliance cannot reach the enrollment service. Otherwise, the value of this field is none.
Last Connection Attempt	Date and time the sensor or hybrid appliance and broker or two brokers last tried to connect.
Connection Last Formed	Date and time the sensor or hybrid appliance and broker or the two brokers last connected.
Connection Last Broken	Date and time the sensor or hybrid appliance and broker or the two brokers last lost their connection.
Other Failure Reason	Other reasons the connection between the sensor or hybrid appliance and broker or between two brokers failed. Other reasons include Enrollment Service Error, Params missing or invalid, and Server error.