Skip to content
Megaport Documentation
Creating an MVE for Routing

Creating a Cisco MVE in Autonomous Mode

This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Cisco in autonomous mode for routing. Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal. You also need a Cisco Smart account for licensing.

For information on setting up a Megaport account, see Creating an Account.

Tip

Cisco provides documentation in the Catalyst 8000V Edge Software Installation And Configuration Guide.

Basic steps

This section summarizes the configuration steps using CLI commands and the Megaport Portal. Detailed procedures follow this basic step summary.

The basic steps are:

  • Obtain a C8000V Smart License from Cisco.
  • Generate an SSH key pair for authentication.
  • Select autonomous mode in the Megaport Portal while creating the MVE.
  • Enter an SSH key for full access to the MVE.
  • Enter the MVE details.
  • Order the Cisco MVE in the Megaport Portal.
  • Activate the Cisco Smart License on the MVE using CLI commands.

Licensing

Before you create an MVE in the Megaport Portal, you need a valid C8000V Smart License from Cisco. Smart Licensing is a license manager on a Cisco IOS XE device. You can place the order for Smart Licensing in the Cisco Portal.

The next step is to generate an SSH key pair for authentication.

Generating an SSH key pair

MVE and Cisco connect through a public/private SSH key pair to establish secure connections. The public SSH key allows you to use SSH to access the MVE.

Megaport supports the 2048-bit RSA key type.

To generate an SSH key pair (Linux/Mac OSX)

  • Enter the SSH keygen command.
     ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048

The key generator command creates an SSH key pair and adds two files to your ~/.ssh directory:

  • megaport-mve-instance-1-2048 - contains the private key.
  • megaport-mve-instance-1-2048.pub - contains the public key that is authorized to log in to the Cisco account.

To generate an SSH key pair (Windows, using PuTTYgen)

  1. Open PuTTYgen.
  2. In the Key section, choose RSA 2048 bit and click Generate.
  3. Move your mouse randomly in the small screen to generate the key pairs.
  4. Enter a key comment to identify the key.
    This is convenient when you use several SSH keys.
  5. Enter a Key passphrase, and re-enter to confirm.
    The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
  6. Click Save private key, choose a location, and click Save.
  7. Click Save public key, choose a location, and click Save.

You’ll copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.

Creating an MVE in the Megaport Portal

Before you create an MVE, you need to determine the best location - one that supports MVE and one that is in the most compatible metro area. You can connect multiple locations to an individual MVE. For location details, see Planning your Cisco MVE Deployment.

You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons.

To create an MVE

  1. In the Megaport Portal, go to the Services page.

  2. Click Create MVE.
    Create MVE button

  3. Select the MVE location.

    Select a location geographically close to your target branch and/or on-premises locations.

    The country you choose must be a market in which you have already registered.

    If you haven’t registered a billing market in the location where you will deploy the MVE, follow the procedure in Enabling Billing Markets.

    To search for your local market in the list, enter a country in the Country Filter or a metro region detail in the Search filter.

  4. Select a diversity zone.
    You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the summary page at the end.
    For more information, see MCR and MVE Diversity.

    Select MVE location

  5. Click Next.

  6. Select Cisco and the software version.
    The MVE will be configured to be compatible with this software version from Cisco.

  7. Specify the MVE details:

    • MVE Name – Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.

    • Size – Select a size from the drop-down list. The list displays all sizes that match the CPU capacity at the selected location. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly. For more information, see Planning your Cisco MVE Deployment.

      Note

      Partner-managed accounts can associate a Partner Deal to a service with a minimum 12-month subscription. For more information, see Associating a Deal With a Service.

    • Service Level Reference (optional) – Specify a unique identifying number for the MVE to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.

    • Appliance Mode – Select Autonomous from the Appliance Mode drop-down list.

    • SSH Key – Copy and paste the contents of your public SSH key here. You can find the public key in the megaport-mve-instance-1-2048.pub file generated earlier. Must be RSA 2048 bits. We support both RFC4716 and RFC4253/OpenSSH formats.

    • Virtual Interfaces (vNICs) – Each MVE is configured with one vNIC named Data Plane by default. To change the name, type over the name text in the box.

      You can add a total of five vNICs to the MVE, including the two added by default. For more information, see Types of vNIC Connections.

      To add a vNIC:

      • Click + Add.

        Add vNIC

      • Enter a name for the vNIC.

        Add name for vNIC

      Note

      If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You can’t add or delete vNICs on a deployed MVE.

    • Minimum Term – Select No Minimum Term, 12 Months, 24 Months, or 36 Months. Longer terms result in a lower monthly rate. 12 Months is selected by default.
      For more information on contract terms, see MVE Pricing and Contract Terms.

      Note

      Partner and partner-managed accounts select MVE subscriptions instead of MVE contract terms.

    MVE details

  8. Click Next to view the Summary page.
    The monthly rate is based on location and size.
    MVE summary

  9. Confirm the configuration and pricing then click Add MVE.
    You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with the Cisco SD-WAN overlay network.
    Create Megaport Internet connection

To create the Megaport Internet connection

  1. Click Create Megaport Internet to proceed (recommended), or click Not now to provision internet access at a later time.

    Note

    MVE requires connectivity to the internet. You can either provision a Megaport Internet connection or provide your own internet access.

  2. Select the target Port (the internet router).
    The B-End of a Megaport Internet connection can be anywhere in the same country as the originating MVE.
    You can filter by diversity zone, or select to view all.

  3. Click Next.

  4. Specify the connection details:

    • Connection Name – The name of your Megaport Internet connection to be shown in the Megaport Portal.

    • Service Level Reference (optional) – Specify a unique identifying number for the Megaport Internet connection to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice.

      Tip

      Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.

    • Rate Limit – The speed of your connection in Mbps. The rate limit is adjustable from 20 Mbps to 10 Gbps in increments of 1 Mbps. You can change the speed as needed after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.

    • VXC State – Select Enabled or Shut Down to define the initial state of the connection. For more information, see Shutting Down a VXC for Failover Testing.

      Note

      If you select Shut Down, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.

    • A-End vNIC - Specify a vNIC from the drop-down list. The list reflects the vNICs that you defined when you created the MVE.

    • Preferred A-End VLAN (optional) – Specify an unused VLAN ID for this connection.
      This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport will assign one.

      Alternatively, you can click Untag. This selection removes the VLAN tagging for this connection and it will be configured without a VLAN ID.

    • Minimum Term – Select No Minimum Term, 12 Months, 24 Months, or 36 Months. Longer terms result in a lower monthly rate. 12 Months is selected by default.
      Take note of the information on the screen to avoid early termination fees (ETF). See Megaport Internet Pricing and Contract Terms and VXC, Megaport Internet, and IX Billing for more information.

    Megaport Internet connection details

  5. Click Next to proceed to the connection detail summary.

  6. Click Add VXC to order the connection. Configured services

  7. Click Order.
    Order services

  8. If you have a promotional code, click Add Promo Code, enter it, then click Add Code.

  9. Click Order Now.
    Order services

Ordering MVE provisions the instance and assigns IP addresses from the Megaport software-defined network (SDN). The MVE provisioning takes only a few minutes to complete. The provisioning process spins up an MVE. At this point, the Cisco Catalyst 8000V MVE instance is booted.

Viewing the MVE in the Megaport Portal

After creating the MVE, you can view it in the Megaport Portal on the Services page. You can also view the public IP addresses assigned.

To view an MVE in the Megaport Portal

  • Go to the Services page.

MVE and Megaport Internet connection in the Megaport Portal

The Megaport Internet icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.

For more information on the Services page, see Understanding the Services Page.

To view the public IP addresses assigned to the MVE

  1. Click the gear icon Gear icon next to the Megaport Internet connection.

  2. Click the Details tab.

  3. Locate the public IP address (IPv4 or IPv6).
    These are the public IP addresses assigned to the MVE.

The next step is to activate Cisco Smart Licensing on the MVE.

Activating the Cisco Smart License

Before you begin, you need to obtain a registration token from Cisco. After applying the token to the CLI configuration on the MVE, you can then verify the license status and configure the MVE throughput speed using CLI commands.

To activate the Cisco Smart License

  1. Obtain a token ID from Cisco using your Smart account.

  2. Use SSH to access the MVE. The default username is mveadmin.

      ssh -i <path_to_private_key> mveadmin@<IP_OF_MVE_Instance>

    Note

    Some older versions might require the ssh-rsa key type to be specified as permitted. For example, using the command:

     ssh -oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedAlgorithms=+ssh-rsa -i <path_to_private_key> mveadmin@<IP_OF_MVE_Instance>.

  3. Submit a trust request to activate the license and register the MVE with Cisco.

      license smart trust idtoken OTgyODllZjktM2UzOC00ZTIzLThjODQtN2ZiZDc2ZDMzYjZmLTE2OTg0MjE0%0AODk5MDh8YURXSzBwdm0zTWtCU05mY3VRaUhTalFLbmJOTTQ2M0hIR2Y0U1E0%0ASUpmbz0%3D%0A local force

  4. Verify that the trust token was installed. 

      show license status

    Wait for the instance to return a value for your smart and virtual accounts as well the date and time that the trust code was installed. This acknowledgement might take a couple of minutes.

  5. Enter configuration mode.

  6. Configure the throughput speed. 

      platform hardware throughput level MB <value>

    Where value is a speed in mbps (for example, 10000 for 10G, 5000 for 5G, 1000 for 1G).

    Note

    For speeds above 250 mbps, a Router US Export License for DNA (also known as an HSECK9) license must be available in your CSSM virtual account. After configuring the throughput level, the MVE instance retrieves the HSECK9 license automatically.

  7. Verify the installed licenses. 

      show license summary

  8. Check the current throughput level. 

      show platform hardware throughput level

    Example: 

      c8kv-auto-test-16#show license summary

  Account Information:  
  Smart Account: Megaport As of Nov 04 15:44:06 2022 UTC  
  Virtual Account: CSR Virtual Account

  License Usage:  
  License                 Entitlement Tag               Count Status
  -----------------------------------------------------------------------------
  Router US Export Lic... (DNA_HSEC)                        1 IN USE
  network-advantage_1G    (ESR_P_1G_A)                      1 IN USE
  dna-advantage_1G        (DNA_P_1G_A)                      1 IN USE

  c8kv-auto-test-16#show plat hardware throughput level

  The current throughput level is 2000000 kb/s

  9. Save the configuration and reboot the MVE. 

      wr mem  
  reload

Next steps

Now that you’ve deployed an MVE, the next step is to connect a VXC to a 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.

Last update: 2024-04-15