> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Planning Your 6WIND Deployment

> This help topic describes 6WIND deployment considerations for the Megaport Virtual Edge (MVE).

export const Anchor = ({name}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Anchor -';
  if (name === undefined || name === null || name === 'undefined') {
    console.error(`${errorPrefix} \`name\` must have a value — rendering an empty string instead`);
    return <></>;
  }
  const raw = typeof name === 'string' ? name : JSON.stringify(name);
  const id = raw.replace(/\s+/g, '-').replace(/[^A-Za-z0-9_-]/g, '').replace(/-+/g, '-').replace(/^-+|-+$/g, '');
  if (!id) {
    console.error(`${errorPrefix} \`name\` "${name}" sanitizes to an empty id — rendering an empty string instead`);
    return <></>;
  }
  return <a style={{
    scrollMarginTop: 'var(--scroll-mt)'
  }} id={id}></a>;
};

export const Gloss = ({term, anchor, langDir = 'en'}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Gloss -';
  if (typeof term !== 'string') {
    term = String(term);
  }
  if (typeof anchor !== 'string') {
    anchor = String(anchor);
  }
  if (!term || term === 'undefined') {
    console.error(`${errorPrefix} the \`term\` property is required — rendering an empty string instead`);
    return <></>;
  }
  if (!anchor || anchor === 'undefined') {
    console.error(`${errorPrefix} the \`anchor\` property is required — rendering an empty string instead`);
    return <></>;
  }
  const lang = langDir === 'en' ? '/' : '/' + langDir + '/';
  const glossaryPage = lang + 'glossary/#' + anchor;
  return <a href={glossaryPage}>{term}</a>;
};

export const Image = ({src, alt = '', caption, width, height, shadow}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Image -';
  if (typeof src !== 'string') {
    src = String(src);
  }
  if (!src || src === 'undefined') {
    console.error(`${errorPrefix} \`src\` is required — rendering an empty string instead`);
    return <></>;
  }
  const img = <img className={['mega-image-style', shadow ? 'shadow' : ''].join(' ')} src={src} alt={alt} width={width} height={height} style={{
    display: 'block'
  }} />;
  return caption ? <figure>
      {img}
      <figcaption style={{
    textAlign: 'center',
    width
  }}>{caption}</figcaption>
    </figure> : img;
};

export const Link = ({href, children}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Link -';
  if (typeof href !== 'string') {
    href = String(href);
  }
  if (!href || href === 'undefined') {
    console.error(`${errorPrefix} the \`href\` property is required — rendering an empty string instead`);
    return <></>;
  }
  if (href.includes('{') || href.toUpperCase().includes('%7B')) {
    console.error(`${errorPrefix} could not resolve a variable in href "${href}" — rendering an empty string instead`);
    return <></>;
  }
  const isExternal = (/^https?:\/\//).test(href);
  return <a href={href} className="link" target={isExternal ? '_blank' : undefined} rel={isExternal ? 'noreferrer' : undefined}>
      {children ?? href}
      {isExternal && <span className="sr-only"> (opens in a new tab)</span>}
    </a>;
};

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

| **You Provide**                                       | **Megaport Provides**                                                                                                                     |
| ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Internet connection from branch                       | Platform to host virtual 6WIND Virtual Service Router (VSR) appliances                                                                    |
| Network and Security vendor enabled at branch         | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet                                           |
| 6WIND software license to use on Megaport SDN         | Access to the Megaport ecosystem                                                                                                          |

## Deployment considerations

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

For information about the 6WIND-specific settings, see [6WIND - Virtual Service Router](https://doc.6wind.com/turbo-router-3.x/index.html).

### Network and Security vendors

MVE is integrated with 6WIND Virtual Service Router (VSR), which uses the 6WIND command line interface (CLI) and/or the Netconf API to create the private overlay network.

For information about all supported <Gloss term="NFVs" anchor="nfv" /> on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).

### Console access

MVE Console access from the Megaport Portal is not available for 6WIND VSR. Plan to provision internet connectivity (either a Megaport Internet connection or a third-party internet connection using a private VXC) as part of your deployment, as this is required to access and manage your 6WIND MVE. For more information, see [Console Access button is disabled](/mve/console-access#console-access-button-is-disabled).

### MVE locations

For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).

<Anchor name="size" />

### 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 <Link href="https://portal.megaport.com">Megaport Portal</Link>, go to the **Services** page.

2. Click **Add Services**, then select **MVE**.
   <Image src="/images/snippets/add-services-button.png" alt="Add Services button" shadow={true} width={150} />

3. Select **6WIND VSR**.

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.

   <Note>
     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.
   </Note>

**What if I need more MVE capacity in the future?**

To increase your MVE capacity, you have these options:

* If your MVE compute still has capacity, you can upgrade your 6WIND license in terms of network throughput and function components, for example, IPsec tunnels, NAT connections, and so on. Contact your 6WIND Sales Representative directly.

* You can provision another MVE instance, add it to your  overlay network, and split the workload between the two MVEs.

* You can provision a larger MVE instance, add it to your  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.

### 6WIND VSR performance matrix

This table summarizes the matrix of performance expected for each of the 6WIND VSR network functions in relation to each of the MVE sizes.

| **MVE Sizes / VSR Functions** | **Virtual Border Router (vBR)** | **Virtual L3/L4 Firewall (vFW)** | **Virtual Carrier Grade NAT (vCGNAT)**   | **Virtual Security Gateway (vSecGW)** |
| ----------------------------- | ------------------------------- | -------------------------------- | ---------------------------------------- | ------------------------------------- |
| 2 CPU / 8 GB RAM              | Up to:<br />1M Routes           | Up to:<br />100K CPS             | Up to:<br />100K CPS<br />5M sessions    | Up to:<br />25K IPsec tunnels         |
| 4 CPU / 16 GB RAM             | Up to:<br />2M Routes           | Up to:<br />\~250K CPS           | Up to:<br />\~250K CPS<br />15M sessions | Up to:<br />50K IPsec tunnels         |
| 8 CPU / 32 GB RAM             | Up to:<br />4M Routes           | Up to:<br />\~600K CPS           | Up to:<br />\~600K CPS<br />30M sessions | Up to:<br />100K IPsec tunnels        |
| 16 CPU / 64 GB RAM            | Up to:<br />6M Routes           | Up to:<br />\~1M CPS             | Up to:<br />\~1M CPS<br />50M sessions   | Up to:<br />150K IPsec tunnels        |
| 32 CPU / 128 GB RAM           | Up to:<br />8M Routes           | Up to:<br />\~1.5M CPS           | Up to:<br />\~1.5M CPS<br />80M sessions | Up to:<br />250K IPsec tunnels        |

<Note>
  The default 6WIND VSR option requires 2 CPU cores (one for the control plane and one for the data plane) and 2 GB RAM. Depending on the selected network function and the expected performance outcome, additional CPU cores and RAM are associated with the VSR. These figures consider 1 CPU core for the control plane and the rest for the data plane.
</Note>

### Security

MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN.

### Licensing

Before you create an MVE in the Megaport Portal, you need user accounts with ordering permissions that provide access to the Megaport Portal. For more information, see [Creating an Account](/setting-up/registering).

In addition, you need a valid license from 6WIND. To request an evaluation license key, raise your request through the [6WIND VSR evaluation page](https://portal.6wind.com/mve-register.php), fill in the form and select the product of interest. Alternatively, for more information about obtaining a 6WIND license, contact your 6WIND Sales Associate or Reseller, or your Megaport Sales Representative for guidance.

### VLAN tagging

Megaport uses <Gloss term="Q-in-Q" anchor="qinq" /> 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](/connections/q-in-q).

### vNICs

Each MVE can have up to five vNICs. An MVE is created with one vNIC by default. You can add up to four more, making a total of five.

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.

<Note>
  If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
</Note>

For more information, see [Types of vNIC Connections](/mve/vnic-connections).