Technical data

Introduction to VSX Clusters
Check Point VSX Administration Guide NGX R67 | 88
Virtual System States
VSLS adds a backup state to the existing active and standby states. The backup state contains the latest
configuration settings for each Virtual System, but does not receive state table synchronization. The
relationship between Virtual System states is illustrated in the below figure.
Figure 5-23 State synchronization
Each Virtual System peer in a VSLS cluster is replicated on all cluster members, and each copy exists in a
different state. The active and standby states are synchronized so that the standby peer can immediately
become active in the event of a failure of the active Virtual System or member. When this happens, the
backup peer becomes the standby, and immediately synchronizes with the new active Virtual System.
VSLS reduces the load on the synchronization network by not synchronizing the backup Virtual System
state tables with the active Virtual System until a failover occurs.
Normalized VSLS Deployment Scenario
The figure below illustrates a typical deployment scenario with three cluster members three, each containing
three Virtual Systems. In this configuration, a an equalized load sharing deployment could have one active
Virtual System on each cluster member.
Figure 5-24 Normalized VSLS deployment
In the above figure, three Virtual Systems have been created and a different cluster member hosts the
Active state of each. This distribution of Virtual Systems spreads the load among the clustered machines.
Once a Virtual System has been created, the system automatically creates Standby and Backup states and
distributes them among the other cluster members.
Member Failure Scenario
In the event that a member fails or experiences a connectivity problem, VSLS detects the problem and
routes traffic for the affected Virtual Systems to their respective standby Virtual Systems. Standby Virtual