By default, the preemptive capability on Panorama
allows the primary Panorama to resume functioning as the active
peer as soon as it becomes available. However, if preemption is
disabled, the only way to force the primary Panorama to become active
after recovering from a failure, a non-functional, or a suspended
state, is by suspending the secondary Panorama peer.
Before
the active-secondary Panorama goes into a suspended state, it transfers
the candidate configuration to the passive Panorama so that all
your uncommitted configuration changes are saved and can be accessed
on the other peer.
