Support Center > Search Results > SecureKnowledge Details
How to Reconfigure a VSX Cluster member Technical Level

For R80.10 and higher versions, refer to the Installation and Upgrade Guide of the version, to which you upgrade. (R80.10, R80.20, R80.30, R80.40, R81)

For R77.30 and lower versions, Refer to the main sk97552 (VSX Reconfigure and Upgrade Matrix to R77.10 / R77.20 / R77.30).


When to use this procedure

  • After unrecoverable hardware or software failure.
  • Adding a new cluster member.



Note: Renewable in the procedure below denotes a VSX cluster member, which should be reconfigured.

    1. Backup the involved machines at the same time:

      • Security Management Server / Multi-Domain Security Management Server
      • Renewable VSX cluster member

      Note: Refer to "Related Documentation" section below - "How to Backup".

    2. After a hardware failure on VSX machine, install replacement machine with identical hardware configuration.

      • Install additional memory on the appliance (if needed)
      • Verify that all cluster members have same physical components
      • Make sure the CPUSE Agent is installed with the latest build

    1. Remove all the DATA ports and Sync interfaces and leave only the MGMT interface for the 'vsx_util reconfigure'.

    2. Perform clean installation of R77.30 / R80.10 / R80.20 / R80.30 / R80.40 / R81 on the Renewable VSX cluster member (refer to "Related Documentation" section below).

    3. Run Gaia First Time Configuration Wizard on the Renewable VSX cluster member (refer to sk71000 and sk69701).

      In case of recovery from a failure, you must use the same Management IP address as was used by the previous cluster member (prior to the failure).

      In case of adding new member, you will need to set the member IP address as specified in the 'vsx_util add_member' procedure.

      Note: You do not need to establish SIC with the gateway - the vsx_util reconfigure process will do this for you.

    4. If any hotfixes were installed, then install them on the Renewable VSX cluster member.
      For hotfix installation instructions, refer to the release notes that were provided with the hotfix, or contact Check Point Support.
      Important Note: Installation of Jumbo Hotfixes requires an active Software-Blades License and cannot be completed with the default Trial License Configuration.

    5. Merging configuration files with cluster nodes:

      1. $FWDIR/boot/modules/fwkern.conf
      2. $FWDIR/boot/modules/vpnkern.conf - For versions R80.20 and higher, add the content of this file to $FWDIR/boot/modules/fwkern.conf (sk166179)
      3. $PPKDIR/boot/modules/simkern.conf
      4. $PPKDIR/boot/modules/sim_aff.conf
      5. $FWDIR/conf/fwaffinity.conf
      6. $FWDIR/conf/fwauthd.conf
      7. $FWDIR/conf/local.arp
      8. $FWDIR/conf/discntd.if
      9. $FWDIR/conf/cpha_bond_ls_config.conf
      10. $FWDIR/conf/resctrl - relevant only for versions R80.30 and lower (sk162434)
      11. $FWDIR/conf/vsaffinity_exception.conf
      12. $FWDIR/database/qos_policy.C
      13. $FWDIR/conf/trac_client_1.ttm
      14. $FWDIR/conf/ipassignment.conf

    6. Configure same number of CPUs for SND and configure MultiQ (If configured).

    7. Validation of number of CPUs and Hyper Threaded

      Note: Please make sure CoreXL is disabled on VS0.

    8. Prevent the Renewable VSX cluster member from becoming Active before the reconfigure process ends:

      [Expert@HostName]# cphastop
      [Expert@HostName]# cphaconf fini
      [Expert@HostName]# touch /dev/shm/during_vsx_reconfigure

    1. Install the required licenses on the Renewable VSX cluster member using the cplic put command.


    2. In case Bonding, SNMP, IPV6 need to be configured, then configure it now on the Renewable VSX cluster member. Refer to the R77 Gaia Administration Guide.


    3. Make sure that nobody is logged into any of the CMAs/MGMT which are being managed.

    4. Start the reconfigure process on the Security Management Server / Main Domain Management Server.

      In case of recovery from a failure, Run the 'vsx_util reconfigure' command and follow on screen instructions.

      In case of adding new member, Run the 'vsx_util add_member_reconf' command and follow on screen instructions. (Make sure you run 'vsx_util add_member' procedure before, as mentioned in step 4.)


    5. Before reboot the Renewable VSX cluster member:

      If you have vital configuration in Gaia OS / FireWall / SecureXL / CoreXL / etc. e.g:

      • Relevant Only for R80.10:

        • In case we are using 64 bit per VS - align the configuration before reboot (It Should be same as other cluster members) - refer to sk94627.

          # vsenv
          # vs_bits 64

      • Relevant to all R80.X versions:

          • In case of using Dynamic Routing / DHCP relay / Proxy ARP reconfigure the required Gaia OS settings in Clish.
          • Verify that reconfigured cluster member should not be an active member for VSs
          • For VSLS cluster - Enabling VSLS on Renewable VSX cluster member via cpconfig - Check Point Per Virtual System State

        • Validation of custom configuration file on VS and VSX level: each file must be validated with existing cluster member:

          1. $FWDIR/boot/modules/fwkern.conf
          2. $FWDIR/boot/modules/vpnkern.conf
          3. $PPKDIR/boot/modules/simkern.conf
          4. $PPKDIR/boot/modules/sim_aff.conf
          5. $FWDIR/conf/fwaffinity.conf
          6. $FWDIR/conf/fwauthd.conf
          7. $FWDIR/conf/local.arp
          8. $FWDIR/conf/discntd.if
          9. $FWDIR/conf/cpha_bond_ls_config.conf
          10. $FWDIR/conf/resctrl
          11. $FWDIR/conf/vsaffinity_exception.conf
          12. $FWDIR/database/qos_policy.C
          13. $FWDIR/conf/trac_client_1.ttm
          14. $FWDIR/conf/ipassignment.conf

  1. Reboot the Renewable VSX cluster member

  2. Validations:

    1. Connect Data and SYNC interfaces
    2. Validate cluster state
    3. Configuration (include configuration that was manually added to VS level)
    4. Failover to this member, verify traffic flow - depends on customer permission
    5. Check for hidden drops using "# fw ctl zdebug drop" - Depends on customer permission
    6. Check failover from this cluster node - depends on customer permission


Related Documentation

Show / Hide documentation





How to Backup:

Give us Feedback
Please rate this document