Objectives
The simulator ticks each one as soon as the network meets it.
On F1, read show high-availability state: Peer: not connected, with the reason.
F2 has its HA settings, but high availability is not enabled. Enable it, and commit.
Now both units have priority 100, so both want to be primary. Give F2 priority 200, and commit.
Now the HA1 addresses don’t match: F2’s peer-ip must be F1’s HA1 address, 10.255.255.1. Commit.
show high-availability state on both: F1 is active and F2 is passive, F2 has F1’s zones, and PC1 reaches 198.51.100.1.
Before you start
While the units are apart, each one is active and accepts a commit. Fix F2 one fault at a time, and read the state on F1 after each commit: the reason changes. The lower priority number is preferred, and each unit’s peer-ip is the other unit’s HA1 address.
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.
