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.
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.
Log in to the Panorama peer that you want
to place in a suspended state.
, and click
Suspend local Panorama
link in the Operational
Verify that the status indicates that the Panorama was
suspended at user request.
widget, verify that the
A failover is triggered
when you suspend a peer, and the other Panorama takes over as the
Restore the suspended Panorama to a functional state.
Commands section, click the
Make local Panorama functional
widget, confirm that the Panorama has transitioned to
either the active or passive state.