07-06-2026 02:49 AM
Hi all,
sanity check needed.
Standalone Panorama, SD-WAN plugin 3.2.2-h1, existing mesh cluster with two sites (two HA pairs) running fine in production.
This weekend I onboarded a third site into the existing cluster. Commit to Panorama went fine, but before pushing, Preview Changes on the two production sites showed all the auto generated SD-WAN objects being DELETED: loopback.901, tunnel.900, tunnel.901, sdwan.901, sdwan.902. It looked like the push would tear down the production overlay, so I stopped and rolled back. Nothing was pushed, production untouched.
Strange part: after rollback and a clean commit, the preview still shows the same deletions. Digging further I found that these auto generated objects do not exist in any stored Panorama config version, that every push job starts with an "Autogenerated SDWAN configuration" step, and that successful pushes happened two days earlier with tunnels surviving.
My theory: the plugin generates the SD-WAN config at push time, so the preview (stored config vs running config) will always show these objects as deletions. Scary but cosmetic.
Questions:
thanks for your support.
BR
Me
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
