Edit Your Broker VM Configuration

From the Cortex® XDR™ management console you can edit the configuration of any broker VM as needed.
After configuring and registering your broker VM, select
Settings ( )
Broker VM
to edit existing configurations and define additional settings.
  1. In the
    Broker VMs
    table, locate your broker VM, right-click and select
    Broker Management
    If the broker VM is disconnected, you can only
    the configurations.
  2. In the
    Broker VM Configurations
    window, define the following settings:
    • Edit the exiting
      Network Interfaces
      Proxy Server
      NTP Server
      , and
      SSH Access
    • (
      Requires Broker VM 8.0 and later
      Device Name
      Device Name
      —Change the name of your broker VM device name by selecting the pencil icon. The new name will appear in the Broker VMs table.
      —Set your
      Broker VM FQDN
      as it will be defined in your Domain Name System (DNS). This enables connection between the WEF and WEC, acting as the subscription manager. The
      Broker VM FQDN
      settings affect the WEC and Agent Installer and Content Caching.
    • (
      Requires Broker VM 8.0 and later
      ) (
      Internal Network
      Enter a network subnet to avoid the broker VM dockers colliding with your internal network. By default, the
      Network Subnet
      is set to
      Internal IP must be:
      • Formatted as
        , for example
      • Must be within
      • Cannot be configured to end with a zero.
      For Broker VM version 9.0 and lower, Cortex XDR will accept only
    • Auto Upgrade
      automatic upgrade of the broker VM. By default, auto upgrade is enabled. If you disable auto-upgrade, new features and improvements will require manual upgrade.
    • Monitoring
      of local monitoring of the broker VM usage statistics in Prometheus metrics format, allowing you to tap in and export data by navigating to
      . By default, monitoring your broker VM is disabled.
    • (
      For Broker VM 7.4.5 and earlier
      Enable/Disable ssh
      Palo Alto Networks support team SSH access by using a Cortex XDR token.
      Enabling allows Palo Alto Networks support team to connect to the broker VM remotely, not the customer, with the generated password. Ensure the broker can validate a self-signed CA configuring
      on the broker VM.
      Make sure you save the password before closing the window. The only way to re-generate a password is to disable ssh and re-enable.
    • Broker UI Password
      Reset your current Broker VM Web UI password.
      your new password. Password must be at least 8 characters.
  3. Save
    your changes.

Recommended For You