> ## 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 Cisco MVE Deployment > This help topic describes 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 ; }; 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 {term}; }; 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 = {alt}; return caption ?
{img}
{caption}
: 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 {children ?? href} {isExternal && (opens in a new tab)} ; }; This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE). ## Appliance modes Cisco MVE offers these appliance modes, each tailored to different deployment needs. Selecting the appropriate mode determines how you configure, manage, and use your Cisco MVE. * **Autonomous Mode** – Supports Cisco IOS XE non-SD-WAN deployment for traditional routing without SD-WAN functionality. This mode provides access to the full Cisco IOS XE software features and technologies. For more information, see [Creating a Cisco MVE in Autonomous Mode](/mve/cisco/creating-mve-autonomous). To learn more about Cisco Catalyst Edge software, see: * [Cisco Catalyst 8000V Edge Software Data Sheet](https://www.cisco.com/c/en/us/products/collateral/routers/catalyst-8000v-edge-software/datasheet-c78-744101.html) * [Cisco Catalyst 8000V Edge Software Installation And Configuration Guide](https://www.cisco.com/c/en/us/td/docs/routers/C8000V/Configuration/c8000v-installation-configuration-guide/day0-bootstrap-configuration.html) * **SD-WAN Mode (vManage)** – Supports the Cisco SD-WAN solution. This mode uses the existing SD-WAN functionality with no changes. To operate with Cisco SD-WAN, a new MVE must be provisioned in SD-WAN mode. For more information, see [Creating a Cisco SD-WAN MVE in vManage](/mve/cisco/creating/creating-mve) and [Creating a Cisco SD-WAN MVE Using a Bootstrap Configuration File](/mve/cisco/creating/creating-mve-bootstrap). * **Cisco Meraki Mode** – Enables a cloud-managed SD-WAN deployment, managed through the Cisco Meraki platform. This mode is ideal for users preferring a simplified, cloud-based SD-WAN solution for branch connectivity. Requires a Cisco Meraki authorization token for configuration. For more information, see [Creating an MVE with Cisco Meraki](/mve/cisco/creating-mve-meraki). * **Cisco Secure Firewall Threat Defense Virtual (FTDv) Mode** – Provides integrated security with Cisco FTDv for customers needing firewall protection as part of their deployment. It is configured through Cisco FMC, with a focus on consistent security policies across network environments. For more information, see [Creating an MVE with Cisco Secure Firewall Threat Defense Virtual](/mve/cisco/creating-mve-firewall). | **Appliance Mode** | **Features** | | --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Autonomous | | | SD-WAN | | | Cisco Meraki | | | Secure Firewall Threat Defense Virtual (FTDv) | | You select the appliance mode when you configure the MVE. After selecting a mode and deploying the MVE, you cannot change the appliance mode. ## Deployment considerations This section provides an overview of the MVE deployment options and features. ### SD-WAN vendors Cisco offers a range of solutions for MVE, providing both advanced routing capabilities and robust security options. Depending on your needs, you can deploy a Cisco MVE C8000V for routing and SD-WAN functionalities, use Cisco Meraki for cloud-managed SD-WAN with simplified management, or use Cisco Secure Firewall Threat Defense Virtual to ensure consistent security policies across various environments. For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/). ### MVE locations For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/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 Megaport Portal, go to the **Services** page. 2. Click **Add Services**, then select **MVE**. Add Services button 3. Select **the relevant Cisco 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 **Cisco C8000 licensing** You bring your own Cisco Interconnect Gateway (Cisco Catalyst 8000V Edge Software) Smart License for Cisco for use with MVE. The Catalyst 8000V license is part of Cisco DNA and is based on bandwidth tiers. New customers need a Catalyst 8000v license with Tier 2 bandwidth (DNA-C8KV-T2-A-SDCI) for small and medium MVE instances, or a Catalyst 8000V license with Tier 3 bandwidth (DNA-C8KV-T3-A-SDCI) for large MVE instances. If you already have Catalyst 8000V licenses and subscriptions, MVE requires Cisco DNA Premier or Cisco DNA Advantage subscriptions and Tier 2 (for small and medium instances) or Tier 3 (for large instances) bandwidth. You can order the solution through Cisco partners, who can order all components through Cisco Commerce Workspace (CCW). For more information, discuss licensing with your Account Manager and see the [Cisco Catalyst 8000V Edge Software Ordering Guide](https://www.cisco.com/c/en/us/products/collateral/routers/catalyst-8000v-edge-software/nb-06-cat8000v-edge-sw-og-cte-en.pdf). **Cisco Meraki licensing** For Cisco Meraki you need to create a valid authorization token in the Cisco Meraki SD-WAN portal. For more information, discuss licensing with your Account Manager and see the [Cisco Secure Access Meraki SD-WAN Configuration Guide](https://documentation.meraki.com/MX/Security_Service_Edge_Integrations/Cisco_Secure_Access_Meraki_SD-WAN_Configuration_Guide). **Cisco Secure Firewall Threat Defense Virtual licensing** For Cisco Secure Firewall Threat Defense Virtual, you need an [FMC Registration Key from the Cisco Portal](https://www.cisco.com/c/en/us/support/docs/security/firepower-management-center/215838-fmc-and-ftd-smart-license-registration-a.html). ### 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](/connections/q-in-q). **Cisco Meraki VLAN tagging** Since Cisco Meraki does not support VLAN tagging, set the **Preferred A-End VLAN** to **Untagged** to ensure proper connectivity. For more information, see [Creating an MVE with Cisco Meraki](/mve/cisco/creating-mve-meraki). ### 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. Each MVE for Cisco Secure Firewall Threat Defense Virtual is configured with four vNICs by default. The vNICs are: * 0: Management * 1: Diagnostic * 2: Data1 * 3: Data2 Each MVE for Cisco Meraki is configured with two vNICs by default. The vNICs are: * 0: WAN * 1: LAN 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. 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. For more information, see [Types of vNIC Connections](/mve/vnic-connections).