> Source: [sk184867](https://support.checkpoint.com/results/sk/sk184867)

# sk184867 - Cloud Firewall for Megaport Virtual Edge

| Property | Value |
|----------|-------|
| Solution ID | sk184867 |
| Date Created | 2026-05-24 |
| Last Modified | 2026-06-21 |
| Technical Level | General |
| Products | Cloud Firewall |
| Versions | R82.10, R81.20, R82 |

## Solution

This article describes Check Point Cloud Firewall solutions for [Megaport Virtual Edge](https://docs.megaport.com/mve/) (MVE). It includes general guidance, best practices, and solutions to known field issues.

### Overview

[Megaport](https://www.megaport.com/) is a software-defined networking platform that lets you create and manage network connections quickly and easily. Through the Megaport network, you can deploy private, point-to-point connectivity between any locations on Megaport's global network infrastructure.  

Megaport Virtual Edge (MVE) is a globally distributed, virtual network service. It simplifies and improves network connectivity by integrating Network Function Virtualization (NFV) with Megaport's private software-defined network (SDN). MVE supports virtual network functions (VNFs) that include Check Point Cloud Firewall and SD-WAN (coming soon).  

**Important Note:** This article does not cover all possible deployment scenarios. Many valid architectures exist for Megaport Virtual Edge environments. Check Point strongly recommends that you test all scenarios and architecture designs in a non-production environment before you deploy to production.

### Supported Check Point Versions

* R82.10 (coming soon)
* R82 (recommended version)
* R81.20  

### Supported Deployments

The following deployment types are supported:

* Single Gateway
* Active/Active Mode ClusterXL - supports connection state synchronization; does not support Load Sharing (see [Active/Active Mode Configuration Steps - ClusterXL Administration Guide](https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_ClusterXL_AdminGuide/Content/Topics-CXLG/Active-Active-Mode.htm))
* SD-WAN (coming soon)

### Licensing

The supported licensing model is Bring Your Own License (BYOL).

The license quantity must equal the total number of cores assigned across all Cloud Firewall Gateways.

Supported SKUs:

* CPSG-VSEC-VEN-BUN-NGTP-1Y
* CPSG-VSEC-VEN-BUN-NGTX-1Y

### Interface Support

* **Physical interfaces:** 1 (support for additional physical interfaces is on the roadmap).
* **Total interfaces (physical + virtual):** Up to 1,024.
* **VLAN support:** Full VLAN support is available on the single physical interface.

### Prerequisites

Before you deploy Check Point Cloud Firewall on MVE, make sure you have the following:

* **Megaport Account**   
  You must have an active Megaport account. If you do not have one, [sign up here](https://portal.megaport.com/signup).
* **Check Point Security Management**   
  You must have one of the following Check Point Security Management options:  
  * On-premises Security Management Server
  * Smart-1 Cloud (access it using [Check Point Portal](https://portal.checkpoint.com))
  * Multi-Domain Security Management Server

### Example Architecture

* 2 Cloud Firewall instances deployed in [Megaport Virtual Edge](https://docs.megaport.com/mve/) configured in an [Active/Active Cluster](https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_ClusterXL_AdminGuide/Content/Topics-CXLG/Active-Active-Mode.htm) with connectivity into both AWS and GCP
  * **eth0** \> Private external interface
  * **eth0.100** \> Cluster + sync \> VIP is 0.0.0.0/24 \> interface used to share connection state
  * Cluster Member #1 only
    * **eth0.300** \> Interface for AWS Connection
    * **eth0.400** \> Interface for GCP Connection
  * Cluster Member #2 only
    * **eth0.301** \> Interface for AWS Connection
    * **eth0.401** \> Interface for GCP Connection
* ![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk184867/2026-06-21_Megaport_Gateway Cluster Properties - mve-dal-aa-cluster202606211610301.png)
* Additional loopback interface created(**loop00** ) with 128.0.0.11/24 \> used as Router ID
  * ![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk184867/2026-06-21_Megaport_Gateway loopback00 interface202606211606382.png)
* Cluster member #1 BGP configuration \> GCP  
  * Local AS 65300
  * Peer AS 16550
  * Local Address 169.254.0.1
  * Peer Address 169.254.0.2
  * eBGP Multihop enabled
  * Keep Alive: 20
  * Hold Time: 60
* Cluster member #1 BGP Configuration \> AWS
  * Local AS 65300
  * Peer AS 65301
  * Peer Address 10.0.0.2
  * IP Reachability enabled \> Singlehop BFD
  * eBGP Multihop enabled
  * Keep Alive: 30
  * Hold Time: 90
  * Auth Type: MD5
* Cluster member #2 BGP Configuration \> GCP
  * Local AS 65300
  * Peer AS 16550
  * Local Address 169.254.1.1
  * Peer Address 169.254.1.2
  * eBGP Multihop enabled
  * Keep Alive: 20
  * Hold Time: 60
* Cluster member #2 BGP Configuration \> AWS
  * Local AS 65300
  * Peer AS 65301
  * Peer AS 10.0.1.2
  * IP Reachability enabled \> Singlehop BFD
  * eBGP Multihop enabled
  * Keep Alive: 30
  * Hold Time: 90
  * Auth Type: MD5
* Inbound Route Filters are configured to Accept all routes from AWS and GCP but Route Maps can be used in its place
  * ![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk184867/2026-06-21_Megaport_Gateway Inbound Route Filters202606211636591.png)
* Route Redistribution is also being used to propagate routes but Route Maps can be used in its place
  * Cluster Member #1
    * ![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk184867/2026-06-21_Megaport_Gateway Route Redistribution202606211642022.png)
  * Cluster Member #2
    * ![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk184867/2026-06-21_Megaport_Gateway Route Redistribution_2202606211644233.png)

### Related Information

* [**Check Point Advanced Routing Administration Guide**](https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_Gaia_Advanced_Routing_AdminGuide/Content/Topics-GARG/Gaia-Advanced-Routing.htm)
* [**Megaport Virtual Edge Documentation**](https://docs.megaport.com/mve/)

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
