Objectives
The simulator ticks each one as soon as the network meets it.
F1: HA1 on ethernet1/4 at 10.255.255.1/30, peer 10.255.255.2, priority 100, enabled. Commit.
F2: HA1 on ethernet1/4 at 10.255.255.2/30, peer 10.255.255.1, priority 200, enabled. Nothing else. Commit.
show high-availability state on both: F1 is active and F2 is passive, and F2’s show interface all has F1’s zones.
PC1 reaches 198.51.100.1.
On F1: request high-availability state suspend. F2 is active, PC1 still reaches 198.51.100.1, and F2’s log has the switch.
Before you start
Each unit keeps its own HA settings, management address and host name, and copies everything else. A commit on the passive unit is refused: configure the active unit. A unit that comes back doesn’t take the role back by itself. The group ID (1 here) is the same on both units, and the device priority decides the role: the lower number is preferred.
Concept
One active unit, and the addresses move with the role
Two units watch each other over an HA1 link. The active one answers on the interface addresses, and the passive one copies its configuration and keeps its links quiet. If the active unit fails or is suspended, the passive one takes over with the same addresses, so hosts keep their gateway. Each unit keeps its own HA settings, management address and host name.
