--- title: "Viewing node status" slug: "viewing-node-status" updated: 2026-08-24T20:40:19Z published: 2026-08-24T20:40:19Z canonical: "docs.trellix.com/viewing-node-status" stale: true --- > ## 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. # Viewing node status The following topics describe how to view information about the cluster, nodes, and brokers using the Central Management Web UI and the Virtual Execution CLI. **Prerequisites** - Monitor, Operator, or Admin access ##### Viewing node status using the Central Management Web UI Use the **Appliances** > **Nodes** page in the Central Management Web UI to view a list of the nodes this Central Management appliance manages and their overall status. You can then click a node name for more detail. The following table shows the node status fields. | **Field** | **Description** | | --- | --- | | Name | The name of the node. | | Connection | The state of the connection between the node and the IVX cluster. | | Health | The state of the health of the node. | | Cluster | The cluster of which the node is a member. | | IP | The IP address of the node's management interface. | | Appliance ID | The appliance ID of the node. | | OS | The Virtual Execution system image version running on the node. | | Guest Images | The guest images version installed on the node. | | **Node Details** | | | Last Contact | The last time the Central Management appliance contacted the node to get its status and health check data. | | Connection | The status of the connection between the Central Management appliance and the node. | | Member Groups | The groups of which the node is a member, including the reserved system group. | | EULA | Whether the terms of the Trellix End User License Agreement (EULA) were accepted when the appliance was first configured. | ###### To view node status: 1. Log in to the Central Management Web UI. 2. Select **Appliances** > **Nodes**. 3. Click the node name in the **Name** column to view additional details. ##### Viewing node status using the Virtual Execution CLI Use the commands in this section to view the status of brokers and compute nodes in an IVX cluster. ###### To view node status: 1. Log in to the Virtual Execution CLI. 2. Enable the CLI enable mode: ``` vx-hostname > enable ``` 3. To view the node status: ``` vx-hostname # show mvx node status ``` 4. To view detailed status information: ``` vx-hostname # show mvx node status full ``` ###### Examples The following example shows the status of the vx-1 broker. ``` vx-1 # show mvx node status MVX Cluster: Node Status Broker Role:    Enabled : yes    Ready : yes    SSH port : 22    Submission Interface : ether1    Cluster Interface : ether1    Key Hash : f2:xx:xx:xx:xx:xx:...    Compute Enabled : yes Health Information:    Overall Status Ok : yes    Overall Status Desc : healthy Sensor information:    Number of connected sensors : 2    Sensor ID list:        Sensor ID : 002XXXXXXXX4        Sensor Hostname : nx-2        Sensor Address : 10.13.65.14                Sensor ID : 002XXXXXXXX5        Sensor Hostname : nx-1        Sensor Address : 172.17.74.50 Node information:    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 The following example shows the status of the vx-2 compute node. vx-2 # show mvx node status MVX Cluster: Node Status Broker Role:    Enabled : no    Ready : yes    SSH port : 22    Submission Interface : ether1    Cluster Interface : ether1    Key Hash : f4:xx:xx:xx:xx:xx:...    Compute Enabled : yes Health Information:    Overall Status Ok : yes    Overall Status Desc : healthy Node information:    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/08/07 22:37:18    Connection Last Formed : 2019/08/07 22:37:18    Connection Last Broken : 2019/08/07 22:32:56 The following example shows detailed information about the vx-1 broker. vx-1 # show mvx node status full MVX Cluster: Node Status Broker Role:    Enabled : yes    Ready : yes    SSH port : 22    Submission Interface : ether1    Cluster Interface : ether1    Key Hash : f2:xx:xx:xx:xx:xx:... Health Information:    Overall Status Ok : yes    Overall Status Desc : healthy Detailed Health Information:    CCD ok : yes.    MvxClient Ok : yes. Healthy    Guest Images Ok : yes. Installed    Notification Client Ok : yes. Healthy    WSAPI Ok : yes. Running    Queuemgr Ok : yes. Healthy Sensor information:    Number of connected sensors : 2    Sensor ID list:        Sensor ID : 002XXXXXXXX4        Sensor Hostname : nx-2        Sensor Address : 10.13.65.14        Sensor ID : 002XXXXXXXX5        Sensor Hostname : nx-1        Sensor Address : 172.17.74.50 Node information:    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 ``` ###### Output fields | **Field** | **Description** | | --- | --- | | **Broker Role** | | | Enabled | Whether the node is enabled as a broker. | | Ready | Whether the node can be enabled as a broker. | | SSH port | Port used for secure shell (SSH) communication between the broker and sensors, the broker and compute nodes, and the broker and the Central Management appliance. | | Submission Interface | Name of the interface used for communication between the broker and the sensors and hybrid appliances. | | Cluster Interface | Name of the interface used for communication between the broker and compute nodes. | | Key Hash | SSH host key used to authenticate secure communication. | | Compute Enabled | Whether the node has been added to a cluster. | | **Health Information** | | | Overall Status Ok | Whether the status of the node is acceptable. | | Overall Status Desc | Description of the overall status, such as "healthy." | | **Detailed Health Information** | | | CCD Ok | Whether the cluster communication process the enrollment service uses is running on the broker nodes. If this value is no, this field includes a list of the broker nodes that are not connected and the reasons. Some reasons for failure follow: - no.Unknown - no.No route to host - no.Connection refused - no.Timeout See Sensor, Hybrid Appliance, or Compute Node Cannot Connect to Broker on page 183 for troubleshooting information. | | MvxClient Ok | Whether the submission process is running and a description. For example: - yes.Healthy - no.Broker not configured - no.Connection refused retrying !!! - no.Queues not configured | | Guest Images Ok | Whether the guest images on the compute node are installed. | | Notification Client Ok | (*Broker only*) Whether the notification process is healthy and a description. For example: no.Sensor is down. | | WSAPI Ok | (*Broker only*) Whether the Web services API process is enabled and running. | | Queuemgr Ok | (*Broker only*) Whether the queue manager process is healthy and a description. For example: no.Broker disabled. | | **Sensor information** (*Broker only*) | | | Number of connected sensors | Number of enrolled sensors that are connected to the broker. | | Sensor ID list | List of connected sensors. | | Sensor ID | Appliance ID of the sensor. | | Sensor Hostname | Hostname of the sensor. | | Sensor Address | IP address of the sensor's management interface. | | **Node information** | | | Cluster Name | Name of the cluster of which this node is a member. | | Broker Name | Hostname of the broker connected to this node. | | Broker ID | Appliance ID of the broker. | | Broker Address | IP address of the broker's management interface. | | Broker State | Status of the broker, such as "connected." (This field does not apply to brokers.) | | Failure Reason | Reason the node is not connected to the broker. (This field does not apply to brokers.) | | Last Connection Attempt | Date and time the broker and node last tried to connect. (This field does not apply to brokers.) | | Connection Last Formed | Date and time the broker and node last connected. (This field does not apply to brokers.) | | Connection Last Broken | Date and time the broker and node last lost their connection. (This field does not apply to brokers.) | | Other Failure Reason | Additional information about a failure condition. | ##### Viewing queue status on a broker using the Virtual Execution CLI Use the commands in this section to view the status of the MVX engine queue on a broker. ###### To view the queue status: 1. Log in to the broker (Virtual Execution) CLI. 2. Enable the CLI enable mode: ``` vx-hostname > enable ``` 3. View the status: ``` vx-hostname # show mvx node queuemgr status ``` ###### Examples The following example shows the status of the MVX engine queue on the vx-1 broker (the only broker in the cluster). ``` vx-1 # show mvx node queuemgr status QueueMgr Queue Stats:    Queue Name              : high    Queue Size              : 1    Running submissions     : 1        Queue Name              : low    Queue Size              : 0    Running submissions     : 0    Queue Name              : normal    Queue Size              : 116    Running submissions     : 111    Queue Name              : urgent    Queue Size              : 2    Running submissions     : 2 QueueMgr Cluster Node Status:    Ip address          : 10.11.121.12    Running             : true The following example shows the status of the MVX queue engine from the vx-3 broker (one of two brokers in the cluster). vx-3 # show mvx node queuemgr status    QueueMgr Queue Stats:        Queue Name              : high        Queue Size              : 1        Running submissions     : 1        Queue Name              : low        Queue Size              : 2        Running submissions     : 2        Queue Name              : normal        Queue Size              : 129        Running submissions     : 129        Queue Name              : urgent        Queue Size              : 2        Running submissions     : 2    QueueMgr Cluster Node Status:        Ip address      : 10.11.121.15        Running         : true        Ip address      : 10.11.121.16        Running         : true The following example shows the output of the command on a compute node that is not a broker. vx-4 # show mvx node queuemgr status QueueMgr is disabled ``` ###### Output fields | **Field** | **Description** | | --- | --- | | **QueueMgr Queue Stats** | | | Queue Name | Priority of the submissions in the named queue (high, low, normal, or urgent). | | Queue Size | Number of submissions in the queue. | | Running Submissions | Number of submissions being analyzed. | | **QueueMgr Cluster Node Status** | | | IP address | IP address of the broker. | | Running | Whether the queue process is running on the broker. |