---
title: "Configuring Check Point Cluster VIP Redundant IPsec Tunnel"
slug: "configuring-check-point-cluster-vip-redundant-ipsec-tunnel"
updated: 2026-04-07T09:02:12Z
published: 2026-04-07T09:02:12Z
canonical: "support.perimeter81.com/configuring-check-point-cluster-vip-redundant-ipsec-tunnel"
stale: true
---
> ## Documentation Index
> Fetch the complete documentation index at: https://support.perimeter81.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Configuring Check Point Cluster VIP Redundant IPsec Tunnel
## Introduction
This topic explains how to establish a redundant Site-to-Site VPN tunnel between your Check Point SASE Network and Check Point Firewall cluster VIP.
## Pre-requisites
- Check Point SASE Administrator Portal account.
- Device with Check Point SASE Agent installed.
- Administrator account with Firewall, Router, and the Cloud Management Portal.
- A cluster of two Quantum gateways, behind a single VIP.
- Configuration with ISP redundancy PMTR-68991 is not supported.
## Part 1 - Configuration in SmartConsole
### Step 1: Creating Interoperable Device Object in the Check Point SmartConsole
1. Log in to the Check Point SmartConsole.
2. Click **Security Policies**.
3. In the Objects pane, click **New** and select **More** > **Network Object**> **More** > **Interoperable Device**.
The**Interoperable Device** window appears.
4. In the **Name** field, enter a name for the Check Point SASE gateway, for example, *Harmony_SASE_Gateway*.
5. In the **IPv4 Address** field, enter the Check Point SASE gateway public IP address.
To find the Check Point SASE Gateway public IP Address:
1. Access the Check Point SASE Administrator Portal and click **Networks**.
2. Select the network.
3. Go to the **Gateways** section to find the Public IP address for setting up the single IPsec tunnel.
6. Click **OK**.
### Step 2: Adding Check Point SASE Gateway IP Address and Remote Subnet To The Interoperable Device Object
1. Log in to the Check Point SASE Administrator Portal.
2. Click **Networks**.
3. Verify the assigned network:
1. Select a network, scroll to the end of the row and click.
2. Select **Edit Network**.
3. In the **Edit Network** section, check the **Subnet** field to verify the assigned network. The default value is 10.255.0.0/16.
****
4. Open the Interoperable Device object that you created.
5. Click **Topology** > **New**.
6. In the **General**tab, enter these:
1. **Name** – Name of the topology, for example, *Check Point SASE Network*.
2. **IP Address** – 10.255.0.0
3. **Net Mask**– 255.255.0.0
7. In the **Topology** tab, select **Internal (leads to the local network)** and then select **Network defined by the interface IP and Net Mask**.
Note:
If the gateway is configured with an interface topology that includes a network range or a group overlapping with the encryption domain of the remote VPN peer, incoming decrypted traffic may be seen as coming from the wrong interface. This could trigger anti-spoofing measures, causing traffic to be dropped. To create an anti-spoofing exception, see [sk151774](https://support.checkpoint.com/results/sk/sk157074).
8. Click **OK**.
9. Click **Topology** > **New**.
10. In the **General**tab, enter these:
1. **Name**– Name for the topology, for example, Harmony_SASE_Gateway
2. **IP Address** – Public IP address of the Check Point SASE gateway
3. **Net Mask** – 255.255.255.255
11. Click the **Topology**tab.
12. Select **External (leads out to the internet)**. 
12. Click **OK**.
13. In the **VPN Domain**section, select **User defined** and click 
. .
14. Click **New** and go to **Group** > **Simple****Group**.
The **New Network Group** window appears.
15. In the **Enter Object Comment** field, enter a name, for example, HSASE_VTI, and click **OK**.
16. For the other Check Point SASE Gateway and Check Point Gateway, follow the same procedure in **Creating Interoperable Device Objects in the Check Point SmartConsole** and **Adding Check Point SASE Gateway IP Address and Remote Subnet To The Interoperable Device Object** sections.
17. Publish and install the policy.
### Step 3: Creating VPN Star community
1. Log in to the Check Point SmartConsole.
2. Click **Security Policies**.
3. Go to **Access Tools** > **VPN Communities**.
4. Select an object, click **New** and go to **More** > **VPN Community** > **Star Community**.
The **New Star Community** window appears.
.png)
5. In the **Enter Object Name** field, enter an object name for the VPN Star Community, for example, *Harmony_SASE_VPN*.
6. In the **Link Selection Mode**section, select one of these:
- **Enhanced (Recommended)**- Uses dynamic, intelligent, probe-based logic to choose the optimal VPN link. It evaluates:
- Interface status
- Multiple external IP addresses
- Multiple ISP circuits
- Reachability through Next-Hop Probing
- SLA-like behavior for tunnel selection
- **Legacy**- Uses static or basic logic to select the VPN interface or IP address. Selection is based on:
- Main IP (default)
- Selected interface
- Selected IP
- IP address determined by topology
7. In the **Centre Gateways** section, click  and add the Check Point Gateway.
8. In the **Satellite Gateways** section, click  and add both Interoperable Device Object created for the Check Point Gateway. See [Step 1](/v1/docs/configuring-check-point-redundant-ipsec-tunnel#step-1-creating-interoperable-device-object-in-the-check-point-smartconsole).
.png)
9. Go to **Shared Secret**and click to edit the shared key.
.png)
10. In the **Enter secret**field, enter an appropriate key.Notes:
- Check Point recommends that the shared secret key is at least 20 characters in length.
- Copy the key as it is required while configuring the IPsec Tunnel in the Check Point SASE Administrator Portal.
11. Click **OK**.
12. From the left navigation pane, click **Encryption**and do these:
1. In the **Encryption Settings** section, from the **Encryption Method**list, select**IKEv2 only**.
2. In the **Encryption Suite**section, select **Custom encryption suite**.
3. In the **IKE Security Association (Phase 1)**section:
1. From the **Encryption Algorithm** list, select **AES-256**.
2. From the **Data Integrity** list, select **SHA256**.
3. From the **Diffie Hellman group** list, select **Group 14 (2048 bit)**.
4. In the **IKE Security Association (Phase 2)**section:
1. From the **Encryption Algorithm** list, select **AES-256**.
2. From the **Data Integrity** list, select **SHA256**.
3. Select **Use Perfect Forward Secrecy**.
4. From the **Diffie Hellman group** list, select **Group 14 (2048 bit)**.
13. Go to **Tunnel Management**.
14. In the **Permanent Tunnels** section, select the **Set Permanent Tunnels** checkbox and then select **On all tunnels in the community**.
.png)
15. In the **VPN Tunnel Sharing**section, select **One VPN tunnel per Gateway pair**.
Note:Make sure that you enter the remote subnets specified here in the Check Point SASE Administrator Portal. A mismatch can disconnect the tunnel.
16. Go to **Advanced**.
17. In the **IKE (Phase 1)** section, set the **Renegotiate IKE security associations every (minutes)** field to **480**.
18. In the **IPsec (Phase 2)** section, set the **Renegotiate IPsec security associations every (seconds)** field to **3600**.
19. Click **OK**.
20. Publish and install the policy.
### Step 4: Additional settings in Check Point SmartConsole
1. To set up a Check Point firewall policy, add a rule for VPN traffic for the specific VPN Domain in the Check Point SmartConsole.
In the example below, we have created a policy to allow traffic from the Check Point SASE Network 10.255.0.0/16 to specific destinations and services. Note that the network configuration may differ if you have not changed the default settings during Check Point SASE network creation. For testing purposes, you should initially allow any/any or allow before making the firewall policy more restrictive.
Note:The network configuration differs if you have not changed the default settings during Check Point SASE network creation. For testing purposes, you should initially allow any/any or allow ping before making the firewall policy more restrictive.
2. Publish and install the policy.
### Step 5: Configuring VPN Tunnel Interface
1. Log in to the Check Point Gaia Portal of the first Check Point Gateway.
2. Click **Network Interfaces.**
3. From the**Add**list, select**VPN Tunnel**.
The**Add VPN Tunnel**page appears.
4. Enter these:
1. **VPN Tunnel ID** - Select a unique ID.
2. **Peer**- Name of the interoperable device previously created for the first Check Point SASE Gateway.
3. **VPN Tunnel Type** - Numbered.
4. **Local Address** - Internal address for the Quantum Gateway (within 169.254.x.x ranges).
5. **Remote Address** - Internal address for the Check Point SASE Gateway (within 169.254.x.x ranges, corresponding to the above).
5. Click **OK**.
6. Repeat steps 3 through 5 and create the second VPN Tunnel.
7. Perform steps 1 through 6 on the second Check Point Gateway Gaia Portal.
8. Log in to the Check Point SmartConsole.
9. Open the Gateway Cluster Properties.
10. Go to **Network Management**.
11. From the **Get Interfaces** list, select **Get interfaces Without Topology**.
12. Once the two VPN Tunnel Interfaces are added, click the first tunnel interface.
13. Go to **General.**
14. In the **IPv4** field, add the Virtual IP (VIP) that matches the member IP addresses.
15. Repeat steps 12 through 14 on the second tunnel interface.
16. Publish and install the policy.
### Step 6: Configuring BGP Configuration
1. Log in to the Check Point Gaia Portal of the first Check Point Gateway.
2. Go to **Advanced Routing** and select **BGP**.
3. In the **Peer Groups** section, click **Add**.
4. Enter these:
1. **Peer AS Number** - The AS Number of the Check Point SASE network. If not set already, enter 64512
2. **Peer Group Type** - External
3. **Local Address** - The local address of one VPN Tunnel Interface entered while configuring VPN Tunnel Interface. See step 4 in [Step 5: Configuring VPN Tunnel Interface and BGP](/v1/docs/configuring-check-point-cluster-vip-redundant-ipsec-tunnel#step-5-configuring-vpn-tunnel-interface-and-bgp-configuration).
5. Click **Add Peers.**
6. Enter these:
1. In the **Peer** field, enter the Remote Address set under the VTI configuration in step 4 and click **Show Advanced Settings**.****
2. Select the **Graceful Restart** checkbox.
3. Select the **eBGP Multihop**checkbox and click **Save**.
Note:Without Multihop enabled, the BGP session cannot be established.
7. Repeat step 6 and add the address of the second interface remote address.
8. From the **View mode**list, select **Advanced Routing** and click **Inbound Route Filter.**
9. From the**Add**list**,**select **Add BGP Policy Filter (Based on AS)**.
The **Add BGP Policy Filter based on AS**window appears.
10. Specify these:
1. **Add BGP Policy** - Set a number from the available range
2. **AS Number** - Set the AS Number of the Check Point SASE Network
3. **Action** - **Accept******
11. Click **Save**.
12. From the **View mode**list, select **Advanced Routing**, click **Route Redistribution.******
13. Click **Add Redistribution Form,**and select the method of BGP route advertising from the list.
****The **Add****Redistributio****n from**window appears.
1. From the **To Protocol** list, select **Harmony's ASN** and from the **Static Route** list, select any route you need to advertise to it.
2. Repeat this process and add any other routes you wish to advertise to the Check Point SASE environment based on the desired redistribution method.
3. Click **Save.**
Note - For BGP, no routes are accepted from a peer by default. You must configure an explicit Inbound BGP Route Filter to accept a BGP route from a peer.
14. Repeat the steps for the second Check Point Gateway Gaia Portal.
## Part 2 - Configuration in Check Point SASE Administrator Portal
### Step 1 : Configuring Tunnel and Routes Table
1. Access the Check Point SASE Administrator Portal and click **Networks**..png)
2. Select the network.
3. Click .
4. Select **Add Tunnel**for the gateway from which you want to add the IPSec Site-2-Site VPN tunnel.
1. Click **IPSec Site-2-Site Tunnel** and click **Continue**.
2. Click **Redundant****Tunnels**and****click**Continue.**
3. In the **Tunnel name** field, enter a logical name.
4. Expand **Tunnel 1**and specify these:
- **Shared Secret** – The value previously set on the first star policy.
- **Check Point SASE Gateway Internal IP** - The remote address of the first Check Point Gateway used under the VTI settings.
- **Remote Public IP** - The public IP of the first Quantum Gateway.
- **Remote Gateway Internal IP** - The VIP of the first VTI interface.
- **Remote Gateways ASN** - The ASN of the first Quantum Gateway.
- **Remote ID** - The router ID of the first Quantum Gateway used under the BGP settings above.
5. Expand **Tunnel 2**and specify these:
- **Gateway** - Select the second Check Point SASE Gateway for the tunnel.
- **Shared Secret** - The value previously set on the second star policy.
- **Check Point SASE Gateway Internal IP** - The remote address of the second Quantum Gateway used under the VTI settings.
- **Remote Public IP** - The public IP of the second Quantum Gateway.
- **Remote Gateway Internal IP** - The VIP of the second VTI interface.
- **Remote Gateways ASN** - The ASN of the second Quantum Gateway.
- **Remote ID** - The router ID of the second Quantum Gateway used under the BGP settings above.
6. Expand **Shared Settings**and specify these:
- **Check Point SASE Gateway Proposal Subnets**- Leave **Any (0.0.0.0/0)**selected.
- **Remote Gateway Proposal Subnets** - Leave **Any (0.0.0.0/0)**selected.
- **Autonomous System Number (ASN) -**Default value is **64512**, if not set, enter the AS Number for the Check Point SASE network.
7. In the **Advanced Settings** section, specify these:
- **IKE Version:** V2
- **IKE Lifetime:** 8h
- **Tunnel Lifetime:** 1h
- **Dead Peer Detection Delay:** 10s
- **Dead Peer Detection Timeout:** 30s
- **Phase 1**:
- **Encryption****(Phase 1):** aes256
- **Integrity (Phase 1):** sha256
- **Key Exchange Method:** modp2048
- **Phase 2**:
- **Encryption****(Phase 2):** aes256
- **Integrity (Phase 2):** sha256
- **Key Exchange Method****:**modp2048
8. Click **Add Tunnel**.
5. Select **Routes Table**:
1. Click **Add Route.**
**T**he **Add Route** window appears.
2. Enter all the subnets on the remote side of the tunnel and then click **Add Route**.Note:Make sure that in the Tunnel list, you have selected the previously entered Tunnel name.
6. Click **Apply Configuration**.
### Step 2: Verifying the Setup
Once you complete the above steps, your tunnel should be active.
1. Verify the setup in the Check Point SASE Administrator Portal:
1. Click **Networks**.
2. Locate the tunnel you created, and check the tunnel status.
It should indicate that the tunnel is **Up**, signifying a successful connection.
2. Verify the setup in the Check Point SASE Agent:
1. Connect to your network using the Check Point SASE Agent.
2. Access one of the resources in your environment.
## Troubleshooting
If you encounter issues during or after the setup, review your settings to ensure everything matches the instructions. Check the IP addresses and other details you entered during setup. If issues persist, please consult our dedicated support.
## Support Contacts
If you have any difficulties or questions, contact Check Point SASE's support team. We offer 24/7 chat support on our website at [sase.checkpoint.com](https://www.sase.checkpoint.com/), or you can email us at sase-support@checkpoint.com.