VMware SD-WAN Virtual Edge Hosted by Megaport - Overview; Planning a Deployment; Creating and Connecting Megaport Virtual Edges (MVE)s; Creating a Virtual Cross Connect (VXC)

Products

• VMware SD-WAN by VeloCloud

Issue/Introduction

Introduction

Megaport Limited "Megaport", a global leading Network as a Service (NaaS) provider, offers the ability to deploy a VMware SD-WAN Virtual Edge that is hosted by Megaport. Megaport calls this a VMware SD-WAN on Megaport Virtual Edge (MVE). As with other Virtual Edges hosted by third parties (for example, Azure or AWS) the VMware SD-WAN Service is fully interoperable with an MVE to allow branch-to-cloud connectivity on Megaport’s global Software Defined Network (SDN). Megaport's SDN is an ecosystem of more than 700 enabled data centers worldwide and over 360 service providers, including 220+ cloud on-ramps from the world's leading clouds such as Alibaba Cloud, AWS, Google Cloud, Microsoft Azure, IBM Cloud, Oracle Cloud, and Salesforce.

This KB article will first provide an overview of a VMware SD-WAN Virtual Edge hosted by Megaport, (which will be referred to as a Megaport Virtual Edge (MVE) going forward), before providing details about planning  customer deployment with MVE's, creating an MVE Integrated with VMware SD-WAN, creating a VXC (Virtual Cross Connect) to an MVE Integrated with VMware, and finally connecting MVEs Integrated with VMware SD-WAN.

Note: For details on connecting an MVE to third party endpoints with AWS, Microsoft Azure, or Google Cloud, see the follow-up KB article VMware SD-WAN Virtual Edge Hosted by Megaport - Connecting a Megaport Virtual Edge (MVE) to any Endpoint: Including AWS, Azure, and Google Cloud Endpoints.

VMware SD-WAN with Megaport Virtual Edge Overview

VMware SD-WAN creates the private overlay network and manages the network connections and network policies. You use the VMware SASE Orchestrator management console to create an Edge profile and Virtual Edge, and then you can apply the Profile to the Edge.

You use the Megaport Portal to create and order the MVE and create and manage the virtual cross connects (VXCs) to the cloud OnRamps and other services in the Megaport SDN. The VMware SD-WAN fabric acts as the overlay, and the Megaport SDN acts as the underlay.

 

Environment

VMware SD-WAN by VeloCloud

Resolution

Topics in this section include:

• Planning A Customer Deployment

• Creating an MVE Integrated with VMware SD-WAN

• Creating a VXC to an MVE Integrated with VMware

• Connecting MVEs Integrated with VMware SD-WAN

Planning A Customer Deployment

This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
 

SD-WAN Vendors

The MVE is integrated with VMware SD-WAN, which uses VMware’s SASE Orchestrator management console to create the private overlay network.

MVE locations

Before a customer creates an Megaport Virtual Edge (MVE), the customer needs to determine the best location,  one that supports the MVE and one that is in the most compatible metro area.

MVE instances are located in key metro areas to maintain low latency from your cloud and SaaS workloads to MVE.

Transit gateway functionality is built into each MVE that enables traffic flow to and from branch locations using SD-WAN technologies through internet connections. The customer uses pre-existing internet connectivity from their premises to securely access the MVE that is geographically located closest to those premises.

In general, a customer should provision MVEs at the metro locations nearest to their branch sites and on-premises locations to benefit from the lowest latency and highest throughput.

A customer can connect multiple locations to an individual MVE, and can also deploy multiple instances within a metro area and load-balance their branch sites.

We recommend two MVE host systems per metro area for resiliency.
 

Sizing Your MVE Instance

The instance size determines the MVE capabilities, such as how many concurrent connections it can support. The MVE instances are consolidated into three sizes.

Size	Maximum Throughput	SD-WAN Endpoints	DRAM	HDD
Small (2vCPUs)	500 Mbps	40	4 GB	8 GB
Medium (4vCPUs)	1 Gbps	300	8 GB	8 GB
Large (8vCPUs)	5 Gbps	600	16 GB	8 GB

 

These performance and capacity metrics are estimates and your speeds will vary. When choosing an MVE instance size, keep in mind these items:

•  The maximum throughput numbers are characterized using a pure SD-WAN hub for hub-and-spoke connections.
•  Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI)can impact the maximum throughput speed.
•  Plans to scale the network.

What If More MVE Capacity is Needed in the Future?

A customer has two options:

•  Provision another MVE instance, add it to your SD-WAN overlay network, and split the workload between the two MVEs.
•  Provision a larger MVE instance, add it to the existing VMware SD-WAN overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.

Security

MVE provides capacity to and from your internet-enabled branch locations securely, to any endpoint or service provider on Megaspore’s. CSP-hosted instances of partner SD-WAN products route critical traffic across Megaport’s SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.

Each MVE subscription includes distributed denial-of-service (DDoS)attack protection for no additional charge.

Licensing

A customer provides a VMware SD-WAN license for use with the MVE. It is the customer's responsibility to have the appropriate licenses for the SD-WAN endpoints created on the Megaport network. For details on obtaining a VMware SD-WAN license, see Edge Licensing Documentation, or ask your VMware Sales Associate or Reseller.

VLAN Tagging

Megaport uses Q-in-Q to differentiate between customer MVEs on a host hardware system. The tenant MVE receives an untagged VLAN on the internet-facing link, and single-tagged 802.1Q traffic toward other destinations on the Megaport network (such as CSP onramps or otherers). For details, see Configuring Q-in-Q.

Creating an MVE Integrated with VMware SD-WAN

This topic describes how to create and configure a Megaport Virtual Edge (MVE). Once a customer has a Megaport account, they would use the VMware SASE Orchestrator, which is a centralized management console to create and configure a Profile and an Edge. In the Megaport Portal, a customer can create, administer, maintain, monitor, and terminate the MVE.

Before beginning, a customer needs to create a Megaport account:

• New Megaport customers: Log in to the Megaport Portal, create an account, and proceed to the  VMware SASE Orchestrator account. For details on setting up a Megaport account, see Registering an Account.
• Existing Megaport customers: Proceed to Creating a VMware Edge Profile and Provisioning an Edge to start creating a new MVE.

Before creating an MVE in the Megaport Portal, a customer needs a valid license from VMware SD-WAN. For details on obtaining a VMware license, see Edge Licensing and consult with your VMware Sales Associate or Reseller.

Basic Steps

This section provides an overview of the configuration steps on the VMware SASE Orchestrator and the Megaport Portal.

The basic steps are:

• Create a VMware SD-WAN Profile and Provision a New Edge on the Orchestrator.
• Configure the VMware Edge and apply the Profile to the Edge.
• Generate an SSH public key.
• Create an MVE instance in the Megaport Portal.

Creating a VMware Virtual Edge Profile and Provisioning an Edge

To get started, a customer creates a default profile so that when the Edge registers to the Orchestrator, it retrieves its base configuration, connects to the Orchestrator, and enables some specific firewall rules. After that you can manage the MVE through the Orchestrator.

To Create an Edge Profile on the Orchestrator

1. Log in to the VMware SASE Orchestrator.
2. Click the link for the Customer Profile account.
3. Choose Configure > Profiles.
4. Click New Profile.
5. Enter a Profile Name and an optional Description. For example, megaport-default-profile.
   
6. Click Create

To Create a New Virtual Edge on the Orchestrator

1. Select the Device tab.
2. Select Global Segment from the Configure Segment drop-down.
3. Set Cloud VPN to On.

4. Unselect all device types, except for Virtual Edge.
5. Under Device Settings: Virtual Edge, click Edit next to GE1 and GE2 and configure those those interfaces to not enabled sequentially.
6. Ensure that GE3 is enabled. GE3 becomes the first available routed interface. Other ports do not need to be disabled and may be let in their current state.
    
   
    
7. Configure the following options for the GE3 interface:

• Interface Enabled: Select this option.
• Capability: Choose Routed from the drop-down list.
• Addressing Type: Choose DHCP from the drop-down list.
• WAN Overlay: Enable this option and choose Auto-Detect Overlay from the drop-down list.
• All other interfaces: Use the default values.

8. Click Update GE3.
9. Under Wi-Fi Radio, ensure that the Radio Enabled checkbox is not selected (there are no wireless interfaces).
10. Click Save Changes in the upper-right corner.
11. Select the Firewall tab and enter comma-separated IP values for any customer-side Management IPs that require access to the Edge.

12. Ensure that the Firewall Status option is set to On.
13. Next to Support Access, enter the trusted IP addresses that are allowed to access the Edge.
14. Next to SNMP Access, optionally allow SNMP access to the WAN public interface. Enter the trusted IP addresses to allow.
15. Next to Local Web UI Access, enter the trusted IP addresses to allow access to the WAN interface. This is important because you are configuring a VMware Virtual Edge with no LAN ports and no console.
16. Accept Port 80 as the Local Web UI Port Number or change it to suit the customer environment.
17. Click Save Changes in the upper-right corner.

Once this is completed, the next step is to configure and assign the Profile to the Edge.

Configuring the VMware Virtual Edge

After creating the profile, configure the Virtual Edge to get it connected to the internet.

To Configure a VMware Edge on the Orchestrator

1. On the Orchestrator, click the link for the Customer Profile.
2. Choose Configure > Edges.
3. In the upper-right corner, click New Edge….
4. Populate the fields as required for your network.

• Name – Enter a name for the Edge.
• Model – Choose Virtual Edge from the drop-down list.
• Profile – Select the recently created profile to assign to the new Edge.
• Authentication – Choose an authentication option for the Edge. For details on the authentication options, see the VMware SD-WAN documentation .
• Edge License – Choose the license to apply to this Edge. The list displays the licenses assigned to your enterprise. Licenses are grouped by the Edge throughput limit (1Gbps or 10 Gbps), region, and length of contract. For details on obtaining a VMware license, see Edge Licensing or ask your VMware Sales Associate or Reseller.
• Custom Info (optional) – Enter a description for the Edge.
• Contact Name and Contact Email – Enter a contact name and email address for this Edge.
  

5. Click Create
6. The Edge Overview tab lists an activation key. Save the activation key for use in the Megaport Portal.
   
7. Make any Edge-specific changes to the Device, Business Policy, or Firewall parameters. Or use a Edge-specific Profile to use predefined Profile settings.
8. Click Save Changes in the upper-right corner.

The next step is to generate an SSH key for authentication.

Administrative Access to the Megaport Virtual Edge

Megaport MVE and Orchestrator connect through a public/private SSH key pair to establish secure connections. The public SSH key allows you to SSH into Orchestrator and set the administrative password, enable HTTPS access, and optionally register the MVE to Orchestrator.

Megaport supports the 2048-bit RSA key type.

To Generate an SSH Key Pair (Linux/Mac OSX)

• Run the SSH keygen command:

ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048

The key generator command creates an SSH key pair and adds two files to the ~/.ssh directory:

• megaport-mve-instance-1-2048 - contains the private key.
• megaport-mve-instance-1-2048.pub - contains the public key that is authorized to log in to the VMware account.

To Generate an SSH Key Pair (Windows, using PuTTYgen):

1. Open PuTTYGen.
2. In the Key section, choose RSA 2048 bit and click Generate.
3. Move your mouse randomly in the small screen to generate the keypairs.
4. Enter a key comment, which will identify the key. This is convenient when you use several SSH keys.
5. Enter a key passphrase, and re-enter to confirm. The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click Save private key, choose a location, and click Save.
7. Click Save public key, choose a location, and click Save.

Public Keys: Copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the Edge. This private key will match the public key to grant access. Only a single private key has access to the Edge for SSH access.

Creating the VMware MVE in the Megaport Portal

Before creating an MVE, determine the best location, one that supports the MVE and one that is in the most compatible metro area. You can connect multiple locations to an individual MVE. For location details, see Planning Your Deployment.

You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons.

To create an MVE in the Megaport Portal

1. In the Megaport Portal, go to the Services page.
2. Click Create MVE.

3. Select the MVE location.

Select a location geographically close to your target branch and/or on-premises locations.

The country you choose must be a market in which you have already registered. To search for your local market in the list, enter a country in the Country Filter or a metro region detail in the Search filter.

If you haven’t registered a billing market in the location where you will deploy the MVE, follow the procedure in Enabling a Billing Market.

4. Click Next.
5. Select VMware SD-WAN and the software version. The MVE will be configured to be compatible with this software version from VMware.
6. Specify the MVE details:

• MVE Name – Specify a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
• Invoice Reference (optional) – Specify an identifying number for the MVE to be used for billing purposes, such as a purchase order or cost center number.
• Size – Select a size from the drop-down list: Small, Medium, or Large. Three sizes are available to support varying numbers of concurrent connections. Individual partner product metrics vary slightly, but in general the small size can handle greater than 30 concurrent branch connections and up to 500 Mbps of traffic, a medium size up to 300 connections and 1 Gbps, and a large size approximately 600 connections and approximately 5 Gbps of traffic.
• Orchestrator Address – Enter an FQDN (Fully Qualified Domain Name) or IPv4 or IPv6 address for the Orchestrator where you created the Edge.
• Activation Code – Enter the activation key provided to you by the Orchestrator after creating the Edge.
• SSH Key – Copy and paste the contents of your public SSH key here. You can find the public key in the megaport-mve- instance-1-2048.pub file generated earlier.

7. Click Next to view the Summary screen.

The monthly rate is based on location and size.

8. Confirm the configuration and pricing and click Add MVE. Click Create MVE to add more MVEs in other locations.
9. Click Order.
10. Review the Order Services agreement and click Order Now.

• Click Save to save the configured MVE before placing the order.
• Click Add Promo Code to enter a promotional code and click Add Code.

Ordering the MVE provisions the instance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete.

Viewing the MVE in the Megaport Portal

After creating the MVE, you can view it in the Megaport Portal.

To view an MVE in the Megaport Portal

Go the Services page.
 

Important: As part of the MVE provisioning, Megaport creates a transit Virtual Cross Connect (VXC) to provide internet connectivity and to allow MVE to register and communicate with the SD-WAN overlay network. The overlay network is created and maintained by VMware SD-WAN to provide secure tunnels from the branch locations. The transit VXC is a fixed size, based on the size of the MVE. You cannot modify or delete the transit VXC. Click the gear icon to view its details. The transit VXC icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.
 

The Public IP Addresses (IPv4 or IPv6) are the addresses of the MVE.  By this time, the new MVE should be registered to your Orchestrator and ready for additional configuration.

Validating Your Connection

On the Orchestrator under Test & Troubleshoot > Remote Diagnostics, select the MVE and click Run for Troubleshoot BGP – Show BGP Summary to verify the BGP session and ensure the Edge is up.

Viewing the MVE on the Orchestrator

After creating the MVE, you can monitor the status on the VMware SASE Orchestrator.

To view an MVE on the Orchestrator:

1. Log in to the Orchestrator.
2. Choose Monitor > Network Overview.
3. Click the MVE Edge from the list.

The Link Status and Bandwidth Usage metrics are displayed.

Next Steps

Once the MVE is provisioned with an Active status, the next step is to create VXCs to connect the Megaport backbone to other MVEs or cloud service providers. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.

For details, see Creating a VCX .

Deleting an MVE

Before deleting an MVE, ensure that you delete all VXCs connected to the MVE. For details on deleting a VXC, see Deleting a VXC.

To Delete an MVE

1. In the Megaport Portal, go to the Services page.
2. Click the trash can icon next to the MVE you want to delete.
   A list of all services connected to the MVE appear.

3. Click Yes - Terminate Services to confirm the MVE termination, or click No, Keep Services to cancel.
4. On the Orchestrator, choose Configure > Edges.
5. Select the Edge to delete.
6. Click Actions in the upper-right corner and then click Delete Edge.
7. Follow the prompts on the Orchestrator to delete the Edge.

Creating a VXC to an MVE Integrated with VMware

This topic describes how to connect a Virtual Cross Connect (VXC) that terminates on a Megaport Virtual Edge (MVE).

With an MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types). As VXCs are Layer 2, they are mapped with a VLAN ID on each end.

You can order VXCs to reach any destination in the Megaport network. You can connect up to 24 VXCs on a single MVE.

To Create a VXC

1. In the Megaport Portal, go to the Services page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page. Alternatively, click +Connection and select a cloud destination:
    

Cloud – Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
 

For specific CSP configuration details:
AWS Direct Connect – See Creating MVE Connections to AWS .
Azure Express Route – See Creating MVE Connections to Azure using ExpressRoute .
Google Cloud – See Creating MVE Connections to Google.
Other cloud connections – See Creating MVE Connections to Generic Endpoints

Connecting a VXC between MVEs

In the Megaport Portal, you can create a VXC (interconnect connectivity)between MVEs at two or more Megaport locations. The VXC links the SD-WAN branch locations connected to these edge MVEs via the Megaport fabric, without traversing the public internet for the MVE to MVE connectivity. For specific configuration details, see Connecting MVEs.

Deleting a VXC

A VXC can be terminated directly from the Megaport Portal.

Note: A transit Virtual Cross Connect (VXC) provides internet connectivity and allows MVE to register and communicate with the VMware SD-WAN overlay network. You cannot modify or delete the transit VXC. Deleting an MVE automatically deletes its associated transit VXC. For details on deleting an MVE, see Deleting an MVE.

To Delete a VCX

In the Megaport Portal, go to the Services page.

Click the trash can icon next to the VCX you want to delete.

Click Yes - Terminate Service to confirm the VXC termination, or click No, Keep Services to cancel.

Connecting MVEs Integrated with VMware SD-WAN

This section describes how to connect a Megaport Virtual Edge (MVE) integrated with VMware SD-WAN to another MVE. This deployment uses the Megaport private software defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.

With two MVEs configured, you can create a private Virtual Cross Connect (VXC) to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (MVE) and a B-End (another MVE).

Before You Begin

Provision two MVEs in different locations. If you have not already created MVEs, see Creating an MVE with VMware SD-WAN .

Creating a VXC Between Two MVEs

Private VXC deployment between two VMware MVEs starts in the Megaport Portal where you will create the VXC. Then, you will configure the A-End and B-End MVEs on the Orchestrator management console.

To Create a VXC

1. In the Megaport Portal, go to the Services page and click +Connection next to the originating A-End MVE.
2. Select Private VXC and click Next.

3. Select the destination B-End MVE and location. Use the Country filter to narrow the selection.
4. Click Next.
5. Specify the VXC details:

• Connection Name – Specify a name for the VXC that is easily identifiable. For example: LA MVE 2 to Dallas MVE 4. The name may be changed later, as needed.
• Invoice Reference (optional) – Specify an identifying number for the VXC to be used for billing purposes, such as a purchase order or cost center number.
• Rate Limit – Specify a rate limit, in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to 10 Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. Consult VMware's SD-WAN documentation for details.
• Preferred VLAN – Specify the 802.1q VLAN tag for this connection. Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. Megaport will attempt to use the same VLAN ID at both MVE instances. If you specify a VLAN ID that is already in use, you will be notified when placing the MVE order.

6. Click Next to view the Summary screen.
7. Confirm the configuration and click Add VXC to save the VXC.
8. Click Order to proceed through the checkout process.

Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.

The next step is to configure the A-End and B-End MVEs on the Orchestrator.

Note: The next procedure configures IP connectivity with BGP, providing just one solution out of many. Consult VMware SD-WAN documentation or specific network design and configuration options before configuring interfaces for the MVEs.

Adding Edge Details to the Orchestrator

After you create the VXC between your MVEs, you need to configure it on the Orchestrator. This involves configuring IP addresses and VLAN tags for the interface.

To Configure the A-End Edge

1. On the Orchestrator, go to Configure > Edges.
2. Click the first Edge to configure (the A-End MVE).
3. Select the Device tab and scroll down to the Interface Settings.
4. Click +Add Subinterface.
    

The Select Interface dialog box appears.

5. From the Select Interface menu, choose GE3 and for the Subinterface ID enter the A-End VLAN ID configured on the MVE in the Megaport Portal.

The subinterface settings appear.

6. Click Next.
7. Ensure that Sub Interface Enabled is enabled.
8. Modify segments as needed for your SD-WAN configuration.
9. Change the Addressing Type to Static and provide the A-End IP Address, CIDR prefix, and Gateway.
10. Update other options as needed for your SD-WAN configuration.
11. Ensure Enable VLAN Tagging is enabled.
    The VLAN field is automatically populated with the VLAN ID you specified for the subinterface ID.
    
    
     
12. Click Update GE3:vlan-id.
13. In the upper-right corner of the Configure > Edges window, click Save Changes and then confirm.
    This configures the interface, VLAN tags, and IP addresses so you can test with ping commands through the CLI. (BGP is not yet configured.)

Note: Adding the subinterface momentarily disrupts the connection.

To set up the MVEs to exchange routing information, follow the steps in To configure BGP on the Orchestrator .

To Configure the B-End Edge

1. On the Orchestrator, go to Configure > Edges.
2. Click the second Edge to configure (the B-End MVE).
3. Select the Device tab and scroll down to the Interface Settings.
4. Click +Add Subinterface.
    
   

The Select Interface dialog box appears.

1. From the Select Interface menu, choose GE3 and for the Subinterface ID enter the A-End VLAN ID configured on the MVE in the Megaport Portal.

The subinterface settings appear.

6. Click Next.
7. Ensure that Sub Interface Enabled is enabled.
8. Modify segments as needed for your SD-WAN configuration.
9. Change the Addressing Type to Static and provide the B-End IP Address, CIDR prefix, and Gateway.
10. Update other options as needed for your SD-WAN configuration.
11. Ensure Enable VLAN Tagging is enabled.
    The VLAN field is automatically populated with the VLAN ID you specified for the subinterface ID.
    
    
     
12. Click Update GE3:vlan-id.
13. In the upper-right corner of the Configure > Edges window, click Save Changes and then confirm.
    This configures the interface, VLAN tags, and IP addresses so you can test with ping commands through the CLI. (BGP is not yet configured).

Note: Adding the subinterface momentarily disrupts the connection.

At this point, the interface is created. The next step is to optionally create the Border Gateway Protocol (BGP) session.

To Configure BGP on the Orchestrator (optional)

1. On the Orchestrator, go to Configure > Edges and click the MVE.
2. Click the Device tab and in the Configure Segments section click Enable Edge Override for BGP Settings. This override lets you define BGP values specific for this Edge beyond the Profile definition.

3. Click the toggle button to turn on BGP and click Edit and the BGP Editor appears.

4. Enter the Local ASN for the A-End Edge. Each Edge has its own unique ASN.

5. For the Neighbor IP, add the IP address from the B-End MVE.
6. Add the B-End Edge ASN to the ASN field for the neighbor.
7. View all Additional Options and enable BGP options as needed.
   For details on BGP options on the Orchestrator, see the VMware SD-WAN Documentation.
8. Click OK and then click Save Changes.

Validating Your Connection

On the Orchestrator under Test & Troubleshoot > Remote Diagnostics, select the MVE and click Run for Troubleshoot BGP - Show BGP Summary to verify the BGP session and ensure the Edge is up.