Replace the SD-WAN enabled Panorama HA Peer

1. Configure Firewalls and Export Data.

   1. Configure the faulty firewall (to be replaced) as a secondary passive firewall, and set the other firewall as the primary active firewall.
   2. After configuring the faulty firewall as secondary passive, shut it down and remove it from the network configuration.
   3. In Panorama, go to Managed DevicesSummary and Export the CSV file from the active firewall.

2. Configure the new Panorama management server.

   1. Install the same OS version as the primary active firewall.
   2. Configure the same IP address as the old secondary passive firewall.
   3. Install all the required plugins, application version, and antivirus version same as the primary active firewall.
   4. Execute the commit force CLI command to commit the changes forcefully.
3. Configure High Availability (HA).

   1. On the primary active firewall:
      1. Update the HA peer serial number with the new Panorama serial number.
      2. Navigate to PanoramaHigh AvailabilityElection Settings, disable Preemptive, set priority to primary (if not already configured), and commit the changes.
   2. On the newly deployed Panorama management server:
      1. Navigate to PanoramaHigh AvailabilityElection Settings, disable Preemptive, set priority to secondary, and commit the changes.

   3. Once HA is committed, the new Panorama joins the HA cluster. Initially, the running configuration will not be synchronized, and differences will appear in the HA dashboard.
   4. Address the configuration differences by ensuring the correct versions of applications, antivirus, SD-WAN plugins, and any other required plugins are installed.
4. Resolve initial synchronization issues.

   1. Synchronization from active to passive Panorama will fail initially, showing an error message.
      Despite the failure, the authentication key (auth-key), templates, and device groups will be synchronized.
   2. Verify the synchronization by refreshing the passive Panorama web interface. The Templates and Device Groups tabs should now be visible.

   3. Delete any duplicate entries under "No device group assigned".
5. Configure Serial Numbers and Finalize Panorama Setup.

   1. Suspend the new Panorama management server using PanoramaHigh AvailabilityOperational Commands and Suspend local Panorama for high availability.

   2. Copy the serial numbers from the previously exported CSV file and add them to the newly deployed Panorama.
      Adding serial numbers does not generate the authentication key or trigger a commit.
   3. Wait for all firewalls to reflect their connection status (connected/disconnected) as seen in the active Panorama.
   4. Once statuses match, make the new Panorama functional by selecting Make local Panorama functional for high availability from PanoramaHigh AvailabilityOperational Commands.

6. Synchronize Databases.

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

   2. Reconnect the active Panorama and rerun the synchronization command. If successful, the active and passive Panorama Mongo databases will be synchronized.

7. Synchronize and Verify.

   1. Synchronize the running configuration from active Panorama to passive Panorama to apply all settings.

   2. Verify both active and passive Panorama details in the HA dashboard.

   3. Check the Mongo database status by running:
      debug plugins sd_wan mongo-db sync-status

   4. Perform a force commit on the passive Panorama to finalize the setup.