--- title: "To view the enrollment status from a sensor:" slug: "to-view-the-enrollment-status-from-a-sensor" tags: ["Product Usage", "IVX Cloud", "Sec Ops and Analytics"] updated: 2026-09-04T14:05:43Z published: 2026-09-04T14:05:43Z canonical: "docs.trellix.com/to-view-the-enrollment-status-from-a-sensor" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # To view the enrollment status from a sensor: 1. Log in to the sensor CLI. 2. Enable the CLI enable mode: appl-hostname > **enable** 3. View the enrollment status: appl-hostname # **show mvx cluster enrollment status** **Example** 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/08/11 22:51:01 Enrollment Service:    Auto enabled:                yes    Service address:             DTI (DTIUser@cloud.fireeye.com)    Preferred cluster:           any (less loaded)    Cloud enabled:               yes    Cloud License enabled:       yes    Connect on demand:           yes Broker Info:    Cluster Name:                Cloud-MVX    Broker Name:                 Cloud-MVX-Broker    Broker ID:                   N/A    Broker Address:              mvx.fireeyecloud.com    Broker State:                Connected    Failure Reason:              None    Last Connection Attempt:     2019/08/07 22:13:58    Connection Last Formed:      2019/08/07 22:13:59    Connection Last Broken: ``` **Output Fields** | **Field** | **Description** | | --- | --- | | **Enrollment Client** | | | Status ok | Whether the enrollment client status is acceptable. | | **Field** | **Description** | | --- | --- | | 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 public address. | | 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 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 MVX cluster deployments. | | Cluster Name | Name of the cluster with which the sensor is enrolled (IVX cluster). | | Broker Name | Hostname of the broker with which the sensor is connected (Cloud-MVX- Broker). | | Broker ID | Appliance ID of the broker. | | Broker Address | Cloud broker URL (mvx.fireeyecloud.com). | | Broker State | State of the connection between the sensor and the cloud broker. - **Connected**—The sensor is connected to the cloud broker. - **Inactive**—The sensor is connected to the cloud broker, but the sensor currently has no objects to submit for analysis. - **Disconnected**—The sensor is disconnected from the cloud broker. | | **Field** | **Description** | | --- | --- | | Failure Reason | Reason the connection failed, if any. - **Authentication Failure**—The DTI credentials on the sensor are invalid. - **Authorization Failure**—The sensor is using an invalid or inactive license. - **Enrollment Service Unavailable**—The sensor cannot reach the enrollment service. Otherwise, the value of this field is none. | | Last Connection Attempt | Date and time the sensor and cloud broker last tried to connect. | | Connection Last Formed | Date and time the sensor and cloud broker last connected. | | Connection Last Broken | Date and time the sensor and cloud broker last lost their connection. | | Other Failure Reason | Other reasons the connection between the sensor and the cloud broker failed. Other reasons include Enrollment Service Error, Params missing or invalid, and Server error. | :