SD-WAN Plugin 2.2.7-h5 or Later, 3.2.3-h2 or Later, and 3.3.3 or Later Versions
Workflow for converting a SD-WAN enabled Panorama management server to a Panorama HA
peer for SD-WAN plugin 2.2.7-h5 or later, 3.2.3-h2 or later, and 3.3.3 or later versions.
Configure the new Panorama management server.
- Install the same OS version as the primary active firewall.
- Configure the management IP address.
- Install all the required plugins, application version, and antivirus
version same as the primary active firewall.
- Execute the commit force CLI command to commit
the changes forcefully.
Configure high availability (HA).
- On the standalone Panorama management server:
- Navigate to and configure the IP address and serial number of
the newly deployed Panorama.
- Navigate to , enable Preemptive, set
priority to
primary and commit the changes.
- On the newly deployed Panorama management server.
- Navigate to and configure the IP address and serial number of
the standalone Panorama, which is already managing the network.
- Navigate to , disable Preemptive, set
priority to
secondary and commit the
changes.
- Once HA is committed, the new Panorama joins the HA cluster. Initially,
the running configuration won’t be synchronized, and differences will
appear in the HA dashboard.
- Address the configuration differences by ensuring the correct versions
of applications, antivirus, SD-WAN plugins, and any other required
plugins are installed.
Configure the IP address for the newly deployed Panorama as the secondary IP
address of Panorama in the Panorama settings (under device template of the
devices managed by standalone Panorama) and commit the changes.
Synchronize databases.
- Run the following synchronization command on the active Panorama HA
peer:
debug plugins sd_wan mongo-db
sync-db-to-peer
If the result shows sync-in-progress, restart the
configd process using:
debug software restart
process configd
- Reconnect the active Panorama and run the synchronization command again.
If successful, the active and passive Panorama MongoDB will be
synchronized.
Synchronize and Verify.
- Synchronize the running configuration from active Panorama to passive
Panorama to apply all settings.
- Verify both active and passive Panorama details in the HA dashboard.
- Check the MongoDB status by running:
debug plugins sd_wan
mongo-db sync-status
- Perform a force commit on the passive Panorama to finalize the
setup.
Commit and push the changes from active Panorama to all the firewalls to
configure the secondary Panorama IP address.