Technical data

Managing VSX Clusters
Check Point VSX Administration Guide NGX R67 | 110
Notes to the Upgrade Process
 You only need to run the vsx_util upgrade command once for each VSX cluster. You must,
however, run the vsx_util reconfigure command for each cluster member.
For example, for a deployment with two clusters, each cluster having three members, run vsx_util
upgrade twice, once for each cluster object, and the vsx_util reconfigure six times, once for
each cluster member.
 To ensure stability of the VSX deployment, run the vsx_util upgrade and vsx_util
reconfigure consecutively. For example, run the vsx_util upgrade command for the cluster
object first and then run the vsx_util reconfigure for the first member. Run vsx_util
reconfigure for the second and subsequent members immediately thereafter·
 Verify that each upgraded member is fully operational before upgrading the remaining members.
 You cannot install policies until the upgrade process has completed successfully for all members.
Changing the Cluster Type
This section presents procedures for converting cluster members from one cluster type (High Availability or
VSLS) to the other. Changing the cluster mode involves the use of the vsx_util convert_cluster
command.
Converting from VSLS to High Availability
The process of converting a cluster from VSLS to High Availability consists the following procedures:
1. Redistributing all active Virtual Systems to one member
2. Disabling VSLS options
3. Converting the cluster to High Availability
Redistributing Active Virtual Systems to One Member
To redistribute all active Virtual Systems to one member:
1. Close SmartDashboard.
2. Enter the Expert mode.
3. Execute the vsx_util vsls command.
4. Enter the Security Management Server or Multi-Domain Security Management Domain Management
Server IP address.
5. From the Load Sharing menu, enter "3. Set all VSs active on one member".
6. Enter the administrator user name and password.
7. Enter the VSX cluster name.
8. Enter the number corresponding to the member designated to host all active members.
9. Enter "y" to save and apply the configuration.
10. Exit the Load Sharing menu.
When the convert_cluster command finishes, there should be only one active member on which all
Virtual Systems are in the active state, and one standby member on which all Virtual Devices are in the
standby state. Any additional members should be in standby mode and their Virtual Devices in the down
state.
Disabling VSLS Options
To convert existing cluster members to the VSX gateway high availability mode:
1. On each member, execute the cpconfig command and do the following:
a) Disable the Per Virtual System State for each member.
b) Disable ClusterXL for Bridge Active/Standby for each member.