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

# Creating a Cisco SD-WAN MVE Using a Bootstrap Configuration File

> This help topic describes how to deploy a Cisco SD-WAN Megaport Virtual Edge (MVE) using a vManage device template and a bootstrap (cloud-init) configuration file.

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 describes how to deploy a Cisco SD-WAN MVE using a bootstrap (cloud-init) configuration file. In this method, you build a device template in the Cisco vManage console, generate and download a bootstrap configuration file, then create the MVE in the Megaport Portal and upload that file.

This is a manual deployment method. It is separate from the automated Cloud OnRamp for Multi-Cloud method, in which vManage uses your Megaport Portal account details to make an API call to Megaport and create the interconnect gateway for you. For the automated method, see [Creating a Cisco SD-WAN MVE in vManage](/mve/cisco/creating/creating-mve).

<Note>
  In vManage, a Megaport MVE is called a Cisco interconnect gateway. The terms interconnect gateway and MVE are used interchangeably in this topic.
</Note>

## Basic steps

This section provides an overview of the configuration steps. You configure the device template in vManage, generate the bootstrap file, then upload the file when you create the MVE in the Megaport Portal.

For more information about Cisco SD-WAN, see the [Cisco SD-WAN Cloud OnRamp Configuration Guide](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/ios-xe-17/cloud-onramp-book-xe/m-cloud-onramp-sdci.html).

The basic steps are:

* Attach a device to a template
* Configure the device template
* Configure the device
* Generate the bootstrap configuration file
* Provision the MVE in the Megaport Portal

The MVE with Cisco integration requires vManage platform version 20.5 or later. Before you begin, verify the vManage platform version.

**To view the vManage platform version**

* In the vManage console, click the question mark icon, choose About, and verify the version number.\
  If your version is earlier than 20.5, upgrade to 20.5 or later.

## Attaching a device to a template

Log in to your Cisco vManage console and follow these steps.

**To attach a device to a Megaport template**

1. From the Configuration menu, choose Templates.

   <Image src="/images/mve/cisco/vmanage-configuration-templates.png" alt="vManage templates" shadow={true} width={950} />

2. Select Default from the Template Type drop-down menu.

3. Select a template.\
   This example uses the **Default\_MEGAPORT\_ICGW\_C8000V\_template\_V01** template, but you should first create a copy of the default template and then add to or modify the clone, as required.

4. Click the ellipsis (**...**).

5. Select Attach Devices.

   <Image src="/images/mve/cisco/vmanage-attach-device.png" alt="vManage attach device" shadow={true} width={950} />

6. Select a device from the list of available devices.\
   If no devices are available, use your vSmart account to access the certificates for the devices.

7. Click the right arrow to move the device to the Selected Devices list then click **Attach**.

## Configuring the device template

Configure the device template, including the color, system IP, site ID, and hostname. The color is a Cisco SD-WAN attribute that identifies the individual WAN transport tunnel. The color labels the transport, and the router uses that label for policy and path selection.

**To configure the device template**

1. After the device is attached, click the ellipsis (**...**) and select **Edit Device Template**.

   <Image src="/images/mve/cisco/vmanage-edit-device-template.png" alt="vManage edit device template" shadow={true} width={950} />

2. Select a color from the drop-down list.\
   A *color* is a Cisco SD-WAN attribute that identifies the individual WAN transport tunnel. The color can provide restrictions such as VPN and assigns how other branches address the connection. Select the color that best represents the underlying transport.

3. Enter a System IP address.\
   Each interconnect gateway/MVE needs a unique System IP within the SD-WAN fabric. For example, 1.1.1.32. The System IP is not a routable IP address, but it must be unique among your edge devices.

4. Enter a site ID.\
   Each interconnect gateway/MVE needs a site ID within the SD-WAN fabric. For example, 123132.

5. Enter a hostname.\
   Each interconnect gateway/MVE needs a unique hostname within the SD-WAN fabric. For example, mve-atl-eq2.

6. Click **Update**.

## Configuring the device

Configure the device pushes the operational configuration to the MVE, including its interfaces, routing, VPNs, and SD-WAN settings.

**To configure the device**

1. Click the device name in the Device List.
2. Click **Configure Devices**.

   <Image src="/images/mve/cisco/vmanage-configure-device.png" alt="vManage configure device" shadow={true} width={950} />

## Generating the bootstrap configuration file

<Callout icon="triangle-exclamation" color="red">
  Keep the template minimal and use the default settings. Do not configure any specific settings, because the purpose of the bootstrap file is onboarding only.
</Callout>

**To generate the bootstrap configuration file**

1. Select Configuration > Devices and open the WAN Edge list.

2. Click the ellipsis (**...**) for the device and select **Generate Bootstrap Configuration**.

   <Image src="/images/mve/cisco/vmanage-generate-bootstrap-config.png" alt="vManage generate bootstrap configuration" shadow={true} width={950} />

3. Click **Download** to save the bootstrap file.

   <Image src="/images/mve/cisco/vmanage-download-bootstrap-config.png" alt="vManage download bootstrap configuration" shadow={true} width={950} />

   The bootstrap configuration file contains:

   * System IP
   * Site ID
   * Organization name
   * vBond information
   * Certificates and authentication data

## Creating an MVE in the Megaport Portal

After you download the bootstrap file, create the MVE in the Megaport Portal and upload the file as the cloud-init file.

**To provision the MVE in the Megaport Portal**

1. Log in to the <Link href="https://portal.megaport.com">Megaport Portal</Link> and go to the **Services** page.

2. Click **Add Services**, then select **MVE**.

3. Select **Cisco C8000** and select the software version, then click **Next**.

4. Select the MVE details, including the **Location** and **Size**, then click **Next**.\
   Three sizes are available (small, medium, and large) to support varying numbers of concurrent connections. For more information, see [Planning Your Cisco MVE Deployment](/mve/cisco/plan-deployment).

5. Specify the Cisco SD-WAN-specific settings:

   * **Appliance Mode** -- Select SD-WAN from the Appliance Mode drop-down list.

   * **Cloud-init File** -- Click **Choose file** and upload the bootstrap configuration file you downloaded from vManage.

   <Image src="/images/mve/cisco/mve-cloud-init-upload-portal.png" alt="Upload the cloud-init file in the Megaport Portal" shadow={true} width={950} />

6. Complete the provisioning steps to create the MVE.

Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. After deployment, the MVE:

* Boots up
* Uses the bootstrap configuration
* Establishes a connection to vBond
* Joins the SD-WAN fabric

vManage then recognizes the device and pushes the full configuration.

## Next steps

Once the MVE is provisioned with an Active status, the next steps are to:

* Configure WAN (VPN 0) if it is not template-driven.
* Configure BGP if required.
* Connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. 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 more information, see [Creating a VXC](/mve/cisco/creating-mve-vxc).
* Verify the control connections.