Installing a ClusterXL Cluster

Notes:

  • This procedure applies to both Check Point Appliances and Open Servers.

  • This procedure does not apply to Check Point Small Office Appliance models lower than 3000.

  • You must install and configure at least two Cluster Members.

Procedure:

  1. Step

    Instructions

    1

    Install the Gaia Operating System:

    2

    Follow Configuring Gaia for the First Time.

    3

    During the First Time Configuration Wizard, you must configure these settings:

    • In the Installation Type window, select Security Gateway and/or Security Management.

    • In the Products window:

      1. In the Products section, select Security Gateway only.

      2. In the Clustering section, select these two options:

        • Unit is a part of a cluster

        • ClusterXL

    • In the Secure Internal Communication window, enter the applicable Activation Key (between 4 and 127 characters long).

    4

    Install a valid license.

    See Working with Licenses.

  2. You can configure the ClusterXL object in either Wizard Mode, or Classic Mode.

    • Step

      Instructions

      1

      Connect with SmartConsole to the Security Management Server or Domain Management Server that should manage this ClusterXL.

      2

      From the left navigation panel, click Gateways & Servers.

      3

      Create a new Cluster object in one of these ways:

      • From the top toolbar, click the New () > Cluster > Cluster.

      • In the top left corner, click Objects menu > More object types > Network Object > Gateways and Servers > Cluster > New Cluster.

      • In the top right corner, click Objects Pane > New > More > Network Object > Gateways and Servers > Cluster > Cluster.

      4

      In the Check Point Security Gateway Cluster Creation window, click Wizard Mode.

      5

      On the Cluster General Properties page:

      1. In the Cluster Name field, enter the applicable name for this ClusterXL object.

      2. Configure the main Virtual IP address(es) for this ClusterXL object.

        • In the Cluster IPv4 Address section, enter the main Virtual IPv4 address for this ClusterXL object.

        • In the Cluster IPv6 Address section, enter the main Virtual IPv6 address for this ClusterXL object.

        Note - You can configure the Cluster Virtual IP address to be on a different network than the physical IP addresses of the Cluster Members. In this case, you must configure the required static routes on the Cluster Members.

      3. In the Choose the Cluster's Solution field, select Check Point ClusterXL and select the cluster mode - either High Availability, or Load Sharing.

      4. Click Next.

      6

      On the Cluster members' properties page, add the objects for the Cluster Members.

      1. Click Add > New Cluster Member.

        The Cluster Member Properties window opens.

      2. In the Name field, enter the applicable name for this Cluster Member object.

      3. Configure the main physical IP address(es) for this Cluster Member object.

        In the IPv4 Address and IPv6 Address fields, configure the same IPv4 and IPv6 addresses that you configured on the Management Connection page of the Cluster Member's First Time Configuration Wizard.

        Make sure the Security Management Server or Multi-Domain Server can connect to these IP addresses.

        Note - You can configure the Cluster Virtual IP address to be on a different network than the physical IP addresses of the Cluster Members. In this case, you must configure the required static routes on the Cluster Members.

      4. In the Activation Key and Confirm Activation Key fields, enter the same Activation Key you entered during the Cluster Member's First Time Configuration Wizard.

      5. Click Initialize.

      6. Click OK.

      7. Repeat Steps a-f to add the second Cluster Member, and so on.

       

      If the Trust State field does not show Trust established, perform these steps:

      1. Connect to the command line on the Cluster Member.

      2. Make sure there is a physical connectivity between the Cluster Member and the Management Server (for example, pings can pass).

      3. Run:

        cpconfig

      4. Enter the number of this option:

        Secure Internal Communication

      5. Follow the instructions on the screen to change the Activation Key.

      6. In SmartConsole, click Reset.

      7. Enter the same Activation Key you entered in the cpconfig menu.

      8. In SmartConsole, click Initialize.

      7

      On the Cluster Topology page, configure the roles of the cluster interfaces:

      1. Examine the IPv4 Network Address at the top of the page.

      2. Select the applicable role:

        • For cluster traffic interfaces, select Representing a cluster interface and configure the Cluster Virtual IPv4 address and its Net Mask.

          Note - You can configure the Cluster Virtual IP address to be on a different network than the physical IP addresses of the Cluster Members. In this case, you must configure the required static routes on the Cluster Members.

        • For cluster synchronization interfaces, select Cluster Synchronization and select Primary only. Check Point cluster supports only one synchronization network.

        • For interfaces that do not pass the traffic between the connected networks, select Private use of each member (don't monitor members interfaces).

      3. Click Next

      8

      On the Cluster Definition Wizard Complete page:

      1. Examine the Configuration Summary.

      2. Select Edit Cluster's Properties.

      3. Click Finish

      The Gateway Cluster Properties window opens.

      9

      On the General Properties page > Machine section:

      1. In the Name field, make sure you see the configured applicable name for this ClusterXL object.

      2. In the IPv4 Address and IPv6 Address fields, configure the same IPv4 and IPv6 addresses that you configured on the Management Connection page of the Cluster Member's First Time Configuration Wizard.

        Make sure the Security Management Server or Multi-Domain Server can connect to these IP addresses.

      10

      On the General Properties page > Platform section, select the correct options:

      1. In the Hardware field:

        If you install the Cluster Members on Check Point Appliances, select the correct appliances series.

        If you install the Cluster Members on Open Servers, select Open server.

      2. In the Version field, select R80.40.

      3. In the OS field, select Gaia.

      11

      On the General Properties page:

      1. On the Network Security tab, make sure the ClusterXL Software Blade is selected.

      2. Enable the additional applicable Software Blades on the Network Security tab and on the Threat Prevention tab.

      12

      On the Cluster Members page:

      1. Click Add > New Cluster Member.

        The Cluster Member Properties window opens.

      2. In the Name field, enter the applicable name for this Cluster Member object.

      3. Configure the main physical IP address(es) for this Cluster Member object.

        In the IPv4 Address and IPv6 Address fields, configure the same IPv4 and IPv6 addresses that you configured on the Management Connection page of the Cluster Member's First Time Configuration Wizard.

        Make sure the Security Management Server or Multi-Domain Server can connect to these IP addresses.

        Note - You can configure the Cluster Virtual IP address to be on a different network than the physical IP addresses of the Cluster Members. In this case, you must configure the required static routes on the Cluster Members.

      4. Click Communication.

      5. In the One-time password and Confirm one-time password fields, enter the same Activation Key you entered during the Cluster Member's First Time Configuration Wizard.

      6. Click Initialize.

      7. Click Close.

      8. Click OK.

      9. Repeat Steps a-h to add the second Cluster Member, and so on.

       

      If the Trust State field does not show Trust established, perform these steps:

      1. Connect to the command line on the Cluster Member.

      2. Make sure there is a physical connectivity between the Cluster Member and the Management Server (for example, pings can pass).

      3. Run:

        cpconfig

      4. Enter the number of this option:

        Secure Internal Communication

      5. Follow the instructions on the screen to change the Activation Key.

      6. In SmartConsole, click Reset.

      7. Enter the same Activation Key you entered in the cpconfig menu.

      8. In SmartConsole, click Initialize.

      13

      On the ClusterXL and VRRP page:

      1. In the Select the cluster mode and configuration section, select the applicable mode:

        • High Availability and ClusterXL

        • Load Sharing and Multicast or Unicast

        • Active-Active

      2. In the Tracking section, select the applicable option.

      3. In the Advanced Settings section:

       

      • If you selected the High Availability mode, then:

        1. Optional: Select Use State Synchronization.

          This configures the Cluster Members to synchronize the information about the connections they inspect.

          Best Practice - Enable this setting to prevent connection drops after a cluster failover.

        2. Optional: Select Start synchronizing [  ] seconds after connection initiation and enter the applicable value.

          This option is available only for clusters R80.20 and higher.

          To prevent the synchronization of short-lived connections (which decreases the cluster performance), you can configure the Cluster Members to start the synchronization of all connections a number of seconds after they start.

          Range: 2 - 60 seconds

          Default: 3 seconds

          Notes:

          • This setting in the cluster object applies to all connections that pass through the cluster.

            You can override this global cluster synchronization delay in the properties of applicable services - see the R80.40 ClusterXL Administration Guide.

          • The greater this value, the fewer short-lived connections the Cluster Members have to synchronize.

          • The connections that the Cluster Members did not synchronize, do not survive a cluster failover.

          Best Practice - Enable and configure this setting to increase the cluster performance.

        3. Optional: Select Use Virtual MAC.

          This configure all Cluster Members to associate the same virtual MAC address with the Virtual IP address on the applicable interfaces (each Virtual IP address has its unique Virtual MAC address).

          For more information, see sk50840.

        4. Select the Cluster Member recovery method - which Cluster Member to select as Active during a fallback (return to normal operation after a cluster failover):

          • Maintain current active Cluster Member

            1. The Cluster Member that is currently in the Active state, remains in this state.

            2. Other Cluster Members that return to normal operation, remain the Standby state.

          • Switch to higher priority Cluster Member

            1. The Cluster Member that has the highest priority (appears at the top of the list on the Cluster Members page of the cluster object) becomes the new Active.

            2. The state of the previously Active Cluster Member changes to Standby.

            3. Other Cluster Members that return to normal operation remain the Standby state.

       

      • If you selected the Load Sharing > Multicast mode, then:

        1. Optional: Select Use Sticky Decision Function.

          This option is available only for clusters R80.10 and lower.

          For more information, click the (?) button in the top right corner.

        2. Optional: Select Start synchronizing [  ] seconds after connection initiation and enter the applicable value.

          This option is available only for clusters R80.20 and higher.

          To prevent the synchronization of short-lived connections (which decreases the cluster performance), you can configure the Cluster Members to start the synchronization of all connections a number of seconds after they start.

          Range: 2 - 60 seconds

          Default: 3 seconds

          Notes:

          • This setting in the cluster object applies to all connections that pass through the cluster.

            You can override this global cluster synchronization delay in the properties of applicable services - see the R80.40 ClusterXL Administration Guide.

          • The greater this value, the fewer short-lived connections the Cluster Members have to synchronize.

          • The connections that the Cluster Members did not synchronize, do not survive a cluster failover.

          Best Practice - Enable and configure this setting to increase the cluster performance.

        3. Select the connection sharing method between the Cluster Members:

          • IPs, Ports, SPIs

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address, the same Source and Destination ports, and the same IPsec SPI numbers.

            This is the least "sticky" sharing configuration that provides the best sharing distribution between Cluster Members.

            This method decreases the probability that a certain connection passes through the same Cluster Member in both inbound and outbound directions

            We recommend this method.

          • IPs, Ports

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address and the same Source and Destination ports, regardless of the IPsec SPI numbers.

            Use this method only if there are problems when distributing IPsec packets between Cluster Members.

          • IPs

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address, regardless of the Source and Destination ports and IPsec SPI numbers.

            This is the most "sticky" sharing configuration that provides the worst sharing distribution between Cluster Members.

            This method increases the probability that a certain connection passes through the same Cluster Member in both inbound and outbound directions

            Use this method only if there are problems when distributing packets with different port numbers or distributing IPsec packets between Cluster Members.

       

      • If you selected the Load Sharing > Unicast mode, then:

        1. Optional: Select Use Sticky Decision Function.

          This option is available only for clusters R80.10 and lower.

          For more information, click the (?) button in the top right corner.

        2. Optional: Select Start synchronizing [  ] seconds after connection initiation and enter the applicable value.

          This option is available only for clusters R80.20 and higher.

          To prevent the synchronization of short-lived connections (which decreases the cluster performance), you can configure the Cluster Members to start the synchronization of all connections a number of seconds after they start.

          Range: 2 - 60 seconds

          Default: 3 seconds

          Notes:

          • This setting in the cluster object applies to all connections that pass through the cluster.

            You can override this global cluster synchronization delay in the properties of applicable services - see the R80.40 ClusterXL Administration Guide.

          • The greater this value, the fewer short-lived connections the Cluster Members have to synchronize.

          • The connections that the Cluster Members did not synchronize, do not survive a cluster failover.

          Best Practice - Enable and configure this setting to increase the cluster performance.

        3. Optional: Select Use Virtual MAC.

          This configure all Cluster Members to associate the same virtual MAC address with the Virtual IP address on the applicable interfaces (each Virtual IP address has its unique Virtual MAC address).

          For more information, see sk50840.

        4. Select the connection sharing method between the Cluster Members:

          • IPs, Ports, SPIs

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address, the same Source and Destination ports, and the same IPsec SPI numbers.

            This is the least "sticky" sharing configuration that provides the best sharing distribution between Cluster Members.

            This method decreases the probability that a certain connection passes through the same Cluster Member in both inbound and outbound directions

            We recommend this method.

          • IPs, Ports

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address and the same Source and Destination ports, regardless of the IPsec SPI numbers.

            Use this method only if there are problems when distributing IPsec packets between Cluster Members.

          • IPs

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address, regardless of the Source and Destination ports and IPsec SPI numbers.

            This is the most "sticky" sharing configuration that provides the worst sharing distribution between Cluster Members.

            This method increases the probability that a certain connection passes through the same Cluster Member in both inbound and outbound directions

            Use this method only if there are problems when distributing packets with different port numbers or distributing IPsec packets between Cluster Members.

      14

      On the Network Management page:

      1. Select each interface and click Edit. The Network: <Name of Interface> window opens.

      2. From the left tree, click the General page.

      3. In the General section, in the Network Type field, select the applicable type:

        • For cluster traffic interfaces, select Cluster.

          Make sure the Cluster Virtual IPv4 address and its Net Mask are correct.

        • For cluster synchronization interfaces, select Sync or Cluster+Sync.

          Notes:

          • We do not recommend the configuration Cluster+Sync.

          • Check Point cluster supports only one synchronization network.

          • For Check Point Appliances or Open Servers:

            The Synchronization Network is supported only on the lowest VLAN tag of a VLAN interface.

        • For interfaces that do not pass the traffic between the connected networks, select Private.

      4. In the Member IPs section, make sure the IPv4 address and its Net Mask are correct on each Cluster Member.

        Note - For cluster traffic interfaces, you can configure the Cluster Virtual IP address to be on a different network than the physical IP addresses of the Cluster Members. In this case, you must configure the required static routes on the Cluster Members. See the R80.40 ClusterXL Administration Guide.

      5. In the Topology section:

        • Make sure the settings are correct in the Leads To and Security Zone fields.

        • Make sure to enable the Anti-Spoofing.

      15

      Click OK.

      16

      Publish the SmartConsole session.

    • Step

      Instructions

      1

      Connect with SmartConsole to the Security Management Server or Domain Management Server that should manage this ClusterXL.

      2

      From the left navigation panel, click Gateways & Servers.

      3

      Create a new Cluster object in one of these ways:

      • From the top toolbar, click the New () > Cluster > Cluster.

      • In the top left corner, click Objects menu > More object types > Network Object > Gateways and Servers > Cluster > New Cluster.

      • In the top right corner, click Objects Pane > New > More > Network Object > Gateways and Servers > Cluster > Cluster.

      4

      In the Check Point Security Gateway Creation window, click Classic Mode.

      The Gateway Cluster Properties window opens.

      5

      On the General Properties page > Machine section:

      1. In the Name field, make sure you see the configured applicable name for this ClusterXL object.

      2. In the IPv4 Address and IPv6 Address fields, configure the same IPv4 and IPv6 addresses that you configured on the Management Connection page of the Cluster Member's First Time Configuration Wizard.

        Make sure the Security Management Server or Multi-Domain Server can connect to these IP addresses.

      6

      On the General Properties page > Platform section, select the correct options:

      1. In the Hardware field:

        If you install the Cluster Members on Check Point Appliances, select the correct appliances series.

        If you install the Cluster Members on Open Servers, select Open server.

      2. In the Version field, select R80.40.

      3. In the OS field, select Gaia.

      7

      On the General Properties page:

      1. On the Network Security tab, make sure the ClusterXL Software Blade is selected.

      2. Enable the additional applicable Software Blades on the Network Security tab and on the Threat Prevention tab.

      8

      On the Cluster Members page:

      1. Click Add > New Cluster Member.

        The Cluster Member Properties window opens.

      2. In the Name field, enter the applicable name for this Cluster Member object.

      3. Configure the main physical IP address(es) for this Cluster Member object.

        In the IPv4 Address and IPv6 Address fields, configure the same IPv4 and IPv6 addresses that you configured on the Management Connection page of the Cluster Member's First Time Configuration Wizard.

        Make sure the Security Management Server or Multi-Domain Server can connect to these IP addresses.

        Note - You can configure the Cluster Virtual IP address to be on a different network than the physical IP addresses of the Cluster Members. In this case, you must configure the required static routes on the Cluster Members.

      4. Click Communication.

      5. In the One-time password and Confirm one-time password fields, enter the same Activation Key you entered during the Cluster Member's First Time Configuration Wizard.

      6. Click Initialize.

      7. Click Close.

      8. Click OK.

      9. Repeat Steps a-h to add the second Cluster Member, and so on.

       

      If the Trust State field does not show Trust established, perform these steps:

      1. Connect to the command line on the Cluster Member.

      2. Make sure there is a physical connectivity between the Cluster Member and the Management Server (for example, pings can pass).

      3. Run:

        cpconfig

      4. Enter the number of this option:

        Secure Internal Communication

      5. Follow the instructions on the screen to change the Activation Key.

      6. In SmartConsole, click Reset.

      7. Enter the same Activation Key you entered in the cpconfig menu.

      8. In SmartConsole, click Initialize.

      9

      On the ClusterXL and VRRP page:

      1. In the Select the cluster mode and configuration section, select the applicable mode:

        • High Availability and ClusterXL

        • Load Sharing and Multicast or Unicast

        • Active-Active

      2. In the Tracking section, select the applicable option.

      3. In the Advanced Settings section:

       

      • If you selected the High Availability mode, then:

        1. Optional: Select Use State Synchronization.

          This configures the Cluster Members to synchronize the information about the connections they inspect.

          Best Practice - Enable this setting to prevent connection drops after a cluster failover.

        2. Optional: Select Start synchronizing [  ] seconds after connection initiation and enter the applicable value.

          This option is available only for clusters R80.20 and higher.

          To prevent the synchronization of short-lived connections (which decreases the cluster performance), you can configure the Cluster Members to start the synchronization of all connections a number of seconds after they start.

          Range: 2 - 60 seconds

          Default: 3 seconds

          Notes:

          • This setting in the cluster object applies to all connections that pass through the cluster.

            You can override this global cluster synchronization delay in the properties of applicable services - see the R80.40 ClusterXL Administration Guide.

          • The greater this value, the fewer short-lived connections the Cluster Members have to synchronize.

          • The connections that the Cluster Members did not synchronize, do not survive a cluster failover.

          Best Practice - Enable and configure this setting to increase the cluster performance.

        3. Optional: Select Use Virtual MAC.

          This configure all Cluster Members to associate the same virtual MAC address with the Virtual IP address on the applicable interfaces (each Virtual IP address has its unique Virtual MAC address).

          For more information, see sk50840.

        4. Select the Cluster Member recovery method - which Cluster Member to select as Active during a fallback (return to normal operation after a cluster failover):

          • Maintain current active Cluster Member

            1. The Cluster Member that is currently in the Active state, remains in this state.

            2. Other Cluster Members that return to normal operation, remain the Standby state.

          • Switch to higher priority Cluster Member

            1. The Cluster Member that has the highest priority (appears at the top of the list on the Cluster Members page of the cluster object) becomes the new Active.

            2. The state of the previously Active Cluster Member changes to Standby.

            3. Other Cluster Members that return to normal operation remain the Standby state.

       

      • If you selected the Load Sharing > Multicast mode, then:

        1. Optional: Select Use Sticky Decision Function.

          This option is available only for clusters R80.10 and lower.

          For more information, click the (?) button in the top right corner.

        2. Optional: Select Start synchronizing [  ] seconds after connection initiation and enter the applicable value.

          This option is available only for clusters R80.20 and higher.

          To prevent the synchronization of short-lived connections (which decreases the cluster performance), you can configure the Cluster Members to start the synchronization of all connections a number of seconds after they start.

          Range: 2 - 60 seconds

          Default: 3 seconds

          Notes:

          • This setting in the cluster object applies to all connections that pass through the cluster.

            You can override this global cluster synchronization delay in the properties of applicable services - see the R80.40 ClusterXL Administration Guide.

          • The greater this value, the fewer short-lived connections the Cluster Members have to synchronize.

          • The connections that the Cluster Members did not synchronize, do not survive a cluster failover.

          Best Practice - Enable and configure this setting to increase the cluster performance.

        3. Select the connection sharing method between the Cluster Members:

          • IPs, Ports, SPIs

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address, the same Source and Destination ports, and the same IPsec SPI numbers.

            This is the least "sticky" sharing configuration that provides the best sharing distribution between Cluster Members.

            This method decreases the probability that a certain connection passes through the same Cluster Member in both inbound and outbound directions

            We recommend this method.

          • IPs, Ports

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address and the same Source and Destination ports, regardless of the IPsec SPI numbers.

            Use this method only if there are problems when distributing IPsec packets between Cluster Members.

          • IPs

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address, regardless of the Source and Destination ports and IPsec SPI numbers.

            This is the most "sticky" sharing configuration that provides the worst sharing distribution between Cluster Members.

            This method increases the probability that a certain connection passes through the same Cluster Member in both inbound and outbound directions

            Use this method only if there are problems when distributing packets with different port numbers or distributing IPsec packets between Cluster Members.

       

      • If you selected the Load Sharing > Unicast mode, then:

        1. Optional: Select Use Sticky Decision Function.

          This option is available only for clusters R80.10 and lower.

          For more information, click the (?) button in the top right corner.

        2. Optional: Select Start synchronizing [  ] seconds after connection initiation and enter the applicable value.

          This option is available only for clusters R80.20 and higher.

          To prevent the synchronization of short-lived connections (which decreases the cluster performance), you can configure the Cluster Members to start the synchronization of all connections a number of seconds after they start.

          Range: 2 - 60 seconds

          Default: 3 seconds

          Notes:

          • This setting in the cluster object applies to all connections that pass through the cluster.

            You can override this global cluster synchronization delay in the properties of applicable services - see the R80.40 ClusterXL Administration Guide.

          • The greater this value, the fewer short-lived connections the Cluster Members have to synchronize.

          • The connections that the Cluster Members did not synchronize, do not survive a cluster failover.

          Best Practice - Enable and configure this setting to increase the cluster performance.

        3. Optional: Select Use Virtual MAC.

          This configure all Cluster Members to associate the same virtual MAC address with the Virtual IP address on the applicable interfaces (each Virtual IP address has its unique Virtual MAC address).

          For more information, see sk50840.

        4. Select the connection sharing method between the Cluster Members:

          • IPs, Ports, SPIs

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address, the same Source and Destination ports, and the same IPsec SPI numbers.

            This is the least "sticky" sharing configuration that provides the best sharing distribution between Cluster Members.

            This method decreases the probability that a certain connection passes through the same Cluster Member in both inbound and outbound directions

            We recommend this method.

          • IPs, Ports

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address and the same Source and Destination ports, regardless of the IPsec SPI numbers.

            Use this method only if there are problems when distributing IPsec packets between Cluster Members.

          • IPs

            Configures each Cluster Member to inspect all connections with the same Source and Destination IP address, regardless of the Source and Destination ports and IPsec SPI numbers.

            This is the most "sticky" sharing configuration that provides the worst sharing distribution between Cluster Members.

            This method increases the probability that a certain connection passes through the same Cluster Member in both inbound and outbound directions

            Use this method only if there are problems when distributing packets with different port numbers or distributing IPsec packets between Cluster Members.

      10

      On the Network Management page:

      1. Select each interface and click Edit. The Network: <Name of Interface> window opens.

      2. From the left tree, click the General page.

      3. In the General section, in the Network Type field, select the applicable type:

        • For cluster traffic interfaces, select Cluster.

          Make sure the Cluster Virtual IPv4 address and its Net Mask are correct.

        • For cluster synchronization interfaces, select Sync or Cluster+Sync.

          Notes:

          • We do not recommend the configuration Cluster+Sync.

          • Check Point cluster supports only one synchronization network.

          • For Check Point Appliances or Open Servers:

            The Synchronization Network is supported only on the lowest VLAN tag of a VLAN interface.

        • For interfaces that do not pass the traffic between the connected networks, select Private.

      4. In the Member IPs section, make sure the IPv4 address and its Net Mask are correct on each Cluster Member.

        Note - For cluster traffic interfaces, you can configure the Cluster Virtual IP address to be on a different network than the physical IP addresses of the Cluster Members. In this case, you must configure the required static routes on the Cluster Members. See the R80.40 ClusterXL Administration Guide.

      5. In the Topology section:

        • Make sure the settings are correct in the Leads To and Security Zone fields.

        • Make sure to enable the Anti-Spoofing.

      11

      Click OK.

      12

      Publish the SmartConsole session.

  3. Step

    Instructions

    1

    Connect with SmartConsole to the Security Management Server or Domain Management Server that manages this ClusterXL Cluster.

    2

    From the left navigation panel, click Security Policies.

    3

    Create a new policy and configure the applicable layers:

    1. At the top, click the + tab (or press CTRL T).

    2. On the Manage Policies tab, click Manage policies and layers.

    3. In the Manage policies and layers window, create a new policy and configure the applicable layers.

    4. Click Close.

    5. On the Manage Policies tab, click the new policy you created.

    4

    Configure and install the applicable Access Control Policy on the ClusterXL object.

    5

    Configure and install the applicable Threat Prevention Policy on the ClusterXL object.

  4. Step

    Instructions

    1

    Connect to the command line on each Cluster Member.

    2

    Examine the cluster state in one of these ways:

    • In Gaia Clish, run:

      show cluster state

    • In the Expert mode, run:

      cphaprob state

    3

    Examine the cluster interfaces in one of these ways:

    • In Gaia Clish, run:

      show cluster members interfaces all

    • In the Expert mode, run:

      cphaprob -a if

For more information, see the: