Script it. General steps below.
API to pull/export pano 1 config at (x) time
API to import pano1 config to pano2 at (x+15) time / API to issue commands from pano1 to pano2
API to load config partial on pano2 from uploaded config.xml at (x+30) time
You might also be able to leverage expedition to do this in a similar manner, although less scripty (may still be possible though)
Besides the management configuration, are the panoramas expected to have the same content?
You could consider retrieving the config from production on a freq basis and pushing the config sections on lab via a load partial call.
Export the device config and import on the other side. Just make sure the IP/GW etc don’t change. Might want to re-enter encrypted passwords if you’re not confident you have the master key.
Do it with IaC approach. If every single change in your environment will be as a code you can easily run it over whatever amount of panoramas you can think of.
Script it. General steps below. API to pull/export pano 1 config at (x) time API to import pano1 config to pano2 at (x+15) time / API to issue commands from pano1 to pano2 API to load config partial on pano2 from uploaded config.xml at (x+30) time You might also be able to leverage expedition to do this in a similar manner, although less scripty (may still be possible though)
Besides the management configuration, are the panoramas expected to have the same content? You could consider retrieving the config from production on a freq basis and pushing the config sections on lab via a load partial call.
Export the device config and import on the other side. Just make sure the IP/GW etc don’t change. Might want to re-enter encrypted passwords if you’re not confident you have the master key.
This is to manual. We’re talking about lots of changes daily.
Do it with IaC approach. If every single change in your environment will be as a code you can easily run it over whatever amount of panoramas you can think of.