> 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/cortex-cloud-posture-management/migrate-to-a-new-broker-vm-image/broker-vm-high-availability-cluster-node.md).

# Broker VM high availability cluster node

You can migrate a broker node in a High Availability (HA) cluster to the latest broker VM image.

#### How To

1. Install and configure a new Broker VM using the new image from your tenant. For detailed instructions, see [Set up and configure Broker VM](/cortex-cloud-posture-management/data-management/broker-vm/set-up-and-configure-broker-vm.md).

   Remember to perform the following if applicable:

   * Add SSL Server Certificates to the new broker.
   * Add Trusted CA Certificate to the new broker.
   * Configure your NTP servers for the new broker.
2. Add the new broker to the cluster. For instructions, see [Add Broker VM to cluster](/cortex-cloud-posture-management/data-management/broker-vm/broker-vm-high-availability-cluster/manage-broker-vm-clusters/add-broker-vm-to-cluster.md).
3. Update your Load Balancer configuration to send logs to the new cluster node.
4. Shutdown the old cluster node that you are replacing.
5. (Optional) Update your Load Balancer configuration to stop sending logs to the old cluster node.
6. (Optional) Remove the old Broker VM from your tenant.
7. (Optional) Delete the old Broker VM from your hypervisor infrastructure.


---

# 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/cortex-cloud-posture-management/migrate-to-a-new-broker-vm-image/broker-vm-high-availability-cluster-node.md?ask=<question>&goal=<endgoal>
```

`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.