> ## 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.

# Types of vNIC Connections

> This help topic describes the different types of vNIC connections depending on the service you are connecting to.

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;
};

A Virtual Network Interface Card (vNIC) is a virtual version of a physical network card. It connects an MVE to the Megaport network, functioning like a physical NIC to enable the MVE to communicate with other services.

When an MVE has multiple vNICs, you must specify either an A-End or B-End vNIC when creating new connections. You can add multiple vNICs while deploying an MVE. You can also rename a vNIC later, after the MVE is deployed. To rename a vNIC, simply type the new name directly into the Virtual Interfaces (vNICs) field in the Portal.

You can configure a maximum of five vNICs on an MVE.  After the MVE has been created, you cannot add or remove vNICs.

Other considerations include:

* You can have one or more VXCs per vNIC, up to the maximum permitted for the MVE. The maximum number of VXCs allowed per MVE is determined by its size.  For more information, see [Megaport Limits and Quotas](/limits-quotas).

* Each VXC can be configured as either tagged or untagged, based on your <Gloss term="MACsec" anchor="macsec" /> requirements.  For more information, see [Using tagged or untagged VXCs](/encryption/macsec#tagged-or-untagged-vxc).

* You can configure a single untagged VXC with one or more tagged VXCs per vNIC.

* Each vNIC supports only one untagged VXC, allowing a maximum of five untagged VXCs per MVE across all five vNICs.

Each overlay vendor has specific rules for vNIC usage. Before creating your MVE, refer to the vendor’s documentation. These rules might include requirements for orchestrator vNICs and tagging, LAN and WAN vNIC selection, and High Availability (HA) configurations.

## MVE to Megaport Internet

You can use a Megaport Internet connection to connect your MVE to the internet. This connection supports various use cases, such as connecting an MVE overlay device to an orchestrator, linking branch offices, or enabling VPN access.

When creating a Megaport Internet connection for an overlay orchestrator, most vendors typically require the interface to be configured as untagged on vNIC-0. However, some vendors have different requirements, so always refer to their documentation.

<Image src="/images/mve/mve-to-internet.png" alt="MVE to Megaport Internet connection" shadow={true} width={500} />

## MVE to MVE

When connecting two MVEs, you must specify both the A-End and B-End vNICs. The VXCs for each vNIC can be either tagged or untagged. Note that a single tagged vNIC can have multiple VXCs configured on it.

<Image src="/images/mve/mve-to-mve.png" alt="MVE to MVE" shadow={true} width={500} />

## MVE to Port

When connecting an MVE to a Port, you must specify an A-End vNIC, which can be either tagged or untagged. Tagged VXCs can be assigned a VLAN for the MVE side. Similarly, a tagged Port can be assigned a VLAN.

The following example shows that the A-End vNIC is untagged, and the B-End Port is tagged.

<Image src="/images/mve/mve-to-port.png" alt="MVE to Port" shadow={true} width={500} />

## MVE to MCR

When connecting an MVE to an MCR, you must specify an A-End vNIC, which can be tagged or untagged. Tagged VXCs can be assigned a VLAN for the MVE side, while assigning a VLAN for the MCR side is not required.

<Image src="/images/mve/mve-to-mcr.png" alt="MVE to MCR" shadow={true} width={500} />