> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/data-security-documentation/data-management/broker-vm/manage-broker-vm.md). # Manage Broker VM After you configure the Broker VMs, you can manage these brokers from the Cortex Data Security management console in the Broker VMs page. When managing a Broker VM, the options differ for a standalone Broker VM versus a Broker VM node that is added to a high availability (HA) cluster. Certain configuration options that are only relevant for a Broker VM cluster node, such as Remove from Cluster, are only displayed when the Broker VM is a cluster peer. Select Settings → Configurations → Data Broker → Broker VMs to view detailed information regarding your registered Broker VMs in the Brokers tab. ### Understanding the Broker VM table The Broker VMs table enables you to monitor and mange your Broker VM and applet connectivity status, version management, device details, and usage metrics. A status icon is displayed in the following columns, where the colors can indicate different statuses: * Device Name: Indicates whether the Broker machine is registered and connected to Cortex Data Security. * Black: Disconnected to Cortex Data Security * Red: Disconnected from Cortex Data Security * Green: Connected * Version: Indicates whether the Broker VM is running the latest version. * Orange: Past Version * Green: Latest Version * Apps: Indicates whether the available Broker VM data collector applets are connected to Cortex Data Security and up-to-date.. * Green (Connected): Indicates the applet has no issues and is running the latest version. * Orange (Warning): * Indicates the applet has minor connectivity or configuration issues, such as a new applet version is available. * During an active update, the indicator flashes orange and the status displays as **Updating**. * Red (Error): Indicates the applet has errors. {% hint style="info" %} #### Note For more information on troubleshooting errors and warnings for these broker applets, see [Troubleshoot Broker VM applet errors](/data-security-documentation/data-management/broker-vm/troubleshoot-broker-vm-applet-errors.md). {% endhint %} ### Broker VM table field descriptions The following table describes common fields that you can add to the Brokers table using the column manager and lists the fields in alphabetical order. {% hint style="info" %} #### Note Certain fields are also exposed in the Clusters tab, when a Broker VM node is added to a High Availability (HA) cluster, and each cluster node is expanded to view the Broker VM nodes table. An asterisk (\*) is beside every field that is also included in the Broker VM nodes table for each HA cluster. {% endhint %} | Field | Description | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ALL interfaces | All IP addresses of the different interfaces on the device. | | APPS\* | List of active or inactive applets and the connectivity status for each. | | CLUSTER NAME\* | Indicates the name of the HA cluster that the Broker VM has been added to. For a standalone Broker VM, which isn't added to any HA cluster, this field is empty. | | CPU USAGE\* | CPU usage percentage of the Broker VM device that is synced every 5 minutes. | | CONFIGURATION STATUS\* |

Broker VM configuration status. Status is defined by the following according to changes made to any of the Broker VM configurations:

| | DEVICE ID | Device ID allocated to the Broker VM by Cortex Data Security after registration. | | DEVICE NAME\* |

Same as the Device ID.

A ⚠ icon notifies of an expired Broker VM. To reconnect, generate a new token and re-register your Broker VM as described in steps 1 through 7 of Set up and configure the Broker VM. Once registered, all previous Broker VM configurations are reinstated.

| | DISK USAGE\* |

Disk usage percentage from the total allocated for data caching in the Broker VM. Inside the brackets is displayed how much this is in GB from the total disk size in GB.

A notification is added to the Notification Center whenever the disk space is low disk and whenever the disk size is increased.

| | EXTERNAL INTERFACE |

The IP interface the Broker VM is using to communicate with the server.

For AWS and Azure cloud environments, the field displays the Internal IP value.

| | LAST SEEN | Indicates when the Broker VM was last seen on the network. | | MEMORY USAGE\* | Memory usage percentage of the Broker VM that is synced every 5 minutes. | | STATUS\* | Connection status of the Broker VM. Status is defined by either Connected or Disconnected. Disconnected Broker VMs do not display CPU Usage, Memory Usage, and Disk Usage information. Notifications about the Broker VM losing connectivity to Cortex Data Security appear in the Notification Center. | | UPGRADE TIME | Timestamp of when the Broker VM was upgraded. | | VERSION\* |

Version number of the Broker VM.

Notifications about the available new Broker VM version appear in the Notification Center.

| ### Maintenance releases Cortex Cloud updates and enhances the Broker VM automatically through maintenance releases. The Broker VM version release process uses several security measures and tools to ensure that every released version is highly secure. These include the following. * CIS Server Level 1 and 2 benchmarks (using a 3rd party product) * Vulnerability scanning for containers running on the Broker VM * Vulnerability scanning for the host kernel * Periodic 3rd party penetration testing --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/data-security-documentation/data-management/broker-vm/manage-broker-vm.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.