Objectives
The simulator ticks each one as soon as the network meets it.
Add cluster CL1: members GW1 and GW2, sync interface eth4.
Virtual addresses: 192.168.1.1 on eth1 (internal), and 203.0.113.1 on eth2 (external).
Network object LAN with hide NAT, and a rule LAN to any, Accept, Track Log. Publish and install on CL1: both members get the one policy.
On GW1, cphaprob state shows GW1 active. PC1 reaches 8.8.8.8.
On GW1: clusterXL_admin down. GW2 becomes active, and PC1 still reaches 8.8.8.8.
Before you start
Rules name the cluster, not its members, and the logs show which member handled the traffic. This model is active/standby with no fail-back: GW1 stays standby after clusterXL_admin up, until GW2 fails. mgmt_cli add simple-cluster is the real command in a short teaching form: the real one lists each member’s name, address and one-time password, and each interface with its type (cluster, sync) and topology.
Concept
A cluster shares virtual addresses
Two gateways act as one. Each keeps its own address, and the active member answers on the shared virtual ones, which is what hosts and routers use. A direct sync cable lets each see the other. Without it, each thinks it is alone and both stay active.
