Planning Your Juniper Deployment

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

​

Deployment considerations

This section provides an overview of the MVE deployment options and features.

​

Juniper products

Juniper Session Smart Router (SSR) delivers advanced routing capabilities, using Secure Vector Routing (SVR) to remove the complexity of traditional tunnel-based overlays. With session-aware routing, enhanced security, and simplified operations through cloud-based management on the Juniper Mist platform, the SSR provides a smarter approach to SD-WAN. Juniper vSRX is a virtualized that provides the security capabilities of Juniper’s physical SRX Series platforms on Megaport’s global private network. For information about all supported on the MVE platform, see the Megaport Virtual Edge (MVE) product page.

​

MVE locations

For a list of global locations where you can connect to an MVE, see Megaport Virtual Edge Locations.

​

Sizing your MVE instance

The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor’s sizing documentation to ensure it aligns with the number and type of features you plan to enable. When choosing an MVE instance size, keep in mind these items:

• 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 affect the maximum throughput speed.
• Future plans to scale the network.

To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location. To check the MVE instance sizes in the Megaport Portal

1. In the , go to the Services page.
2. Click Add Services, then select MVE.
3. Select the relevant Juniper product.
4. Select the software version.
5. Click Next.
6. Select an MVE location. Select a location geographically close to your target branch and/or on-premises locations. You can use the Search field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled Available. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
   If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.

What if I need more MVE capacity in the future? To increase your MVE capacity, you have these options:

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

You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.

​

Security

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

​

Licensing

You bring your own Juniper license for use with MVE. Licensing requirements vary depending on the Juniper product you deploy. Juniper licensing is subscription-based and managed through Juniper’s licensing portal. You will need valid subscriptions based on your deployment size and feature requirements. For more information, discuss licensing with your Account Manager and see the Juniper Licensing User Guide or contact Juniper support.

​

VLAN tagging

Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see Configuring Q-in-Q.

​

vNICs

Each MVE can have up to five vNICs. The number and default configuration of vNICs varies by Juniper product. Juniper SSR: Each MVE for Juniper SSR is configured with three vNICs by default. Megaport recommends a minimum configuration of three vNICs:

• 0: Management
• 1: WAN
• 2: LAN

Juniper vSRX: Each MVE for Juniper vSRX deploys with two vNICs by default. You can add up to three more, for a total of five. The default vNICs are:

• 0: Management
• 1: Data Plane

Before specifying the number of vNICs on your MVE:

• Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
• Consult your service provider to make sure that functionality won’t be affected if you add a vNIC.

For more information, see Types of vNIC Connections.