> 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-runtime-security/migration-process-for-new-broker-vm-image/standalone-broker-vm.md).

# Standalone Broker VM

You can migrate a standalone Broker VM in your environment 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-runtime-security/data-management/broker-vm/set-up-and-configure-broker-vm.md).
2. Import the Broker VM configuration from an old broker to the new broker with the new image. For more information, see [Import Broker VM Configuration](/cortex-cloud-runtime-security/data-management/broker-vm/manage-broker-vm/import-broker-vm-configuration.md).
   * During the import, use the option to shutdown the old broker (selected by default).

     <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>The shutdown process can take up to 10 minutes while the broker offloads its data cache.</p></div>
3. Update settings to keep receiving logs from external sources (Syslog, Netflow, and WEC) using the new broker. Use one of the following options:
   * (Recommended) Option 1: Change the IP address of the new broker to the IP address of the old broker.
     1. Select Settings → Configurations → Data Broker → **Broker VMs**.
     2. In the Broker VMs table, right-click the new broker VM, and select **Configure**.
     3. In the **Network Interfaces** section, edit the **IP** address by selecting the pencil icon.
     4. Click **Save**.
   * Option 2: Update your network sources to send messages to the IP address of the new broker.
     * Update your network devices to send Syslog messages to the IP address of the new broker.
     * Update your network devices to send Netflow messages to the IP address of the new broker.
     * Update the DNS record of the old broker FQDN to point to the IP address of the new broker.
4. (Optional) Remove the old broker from your tenant.
5. (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-runtime-security/migration-process-for-new-broker-vm-image/standalone-broker-vm.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.