Creating MVE Connections to Generic Endpoints

This topic provides generic steps to configure and deploy a Megaport VXC connection in the Megaport Portal and integrate it with an MVE (the interconnect gateway) in Cisco SD-WAN. The VXC can connect to a Cloud Service Provider, a Port, or an MCR.

Tip

Although you can create MVE-to-MVE and AWS connections from the MVE in the Portal, Megaport strongly recommends creating these connections in vManage for seamless integration with your Cisco SD-WAN environment.

Step 1 – Create an MVE

  • Create an MVE (Cisco interconnect gateway) in vManage.
    For details, see Creating an MVE. The MVE needs to be in the active state.

Step 2 – Create a VXC from the MVE

  1. In the Megaport Portal, select the MVE created in Step 1.
  2. Create a VXC to a Port, MCR, or Cloud Service Provider.
    For details, see Creating a VXC.
  3. In the connection details, note the A-End VLAN.

Step 3 – Copy the default device template

  1. In Cisco vManage, go to Configuration > Templates and select the Device tab.
  2. Make a copy of Default_MEGAPORT_ICGW_C8000V_Template_V01.
    Click the ellipsis () at the end of the row and choose Copy from the dropdown menu.
  3. Provide a name for the copied template and click Copy.
    This name can contain only uppercase and lowercase letters, the digits 0 through 9, hyphens, and underscores. It cannot contain spaces or any other characters.

Step 4 – Create a VPN feature template

  1. On the Templates page, select the Feature tab and click +Add Template.
  2. In Select Devices, select the C8000v.
  3. Under Select Template > VPN, click Cisco VPN.
  4. Enter a template name and description.
  5. In the Basic Configuration section, enter the VPN (VRF) ID for the VXC.
    The VPN ID can be any number 1 – 511 or 513 – 65530. VPN 0 is reserved for Transport VPN and VPN 512 is reserved for Managed VPN. The number is normally identical to the VPN ID assigned for corporate networks to communicate between the corporate network and cloud service.
  6. Click Save.

Step 5 – Create a BGP feature template

  1. On the Templates page, select the Feature tab and click +Add Template.
  2. In Select Devices, select the C8000v.
  3. In Select Template > OTHER TEMPLATES click Cisco BGP.
  4. Enter a template name and description.
  5. In the Neighbor section, click +New Neighbor.
  6. Enter device details for the non-MVE side of the connection for IP address, description, and remote AS.
    Enter the IP address and subnet mask in dotted quad format and not CIDR notation. For example, specify 169.254.x.y 255.255.255.248 instead of a.b.c.d/29.
  7. Click Add and click Save.

Step 6 – Create a CLI add-on feature template

  1. On the Templates page, select the Feature tab and click +Add Template.
  2. In Select Devices, select the C8000v.
  3. In Select Template > OTHER TEMPLATES click Cli Add-On Template.
  4. Enter a template name and description.
  5. Copy the following configuration into the CLI CONFIGURATION field.

    interface GigabitEthernet1.{{interface-tag}}
    encapsulation dot1Q {{dot1Q-tag}}
    vrf forwarding {{vrf-number}}
    ip address {{ip-address-subinterface}}
    ip mtu 1500
    !
    
  6. Click Save.

Step 7 – Apply the feature templates to the device template

  1. Go to Configuration > Templates select the Device tab.
  2. Select the MVE template that was copied from the default in Step 1.
  3. Click the ellipses () in the last column and choose Edit.
  4. In the Transport & Management VPN section, from the Cisco VPN 512 dropdown menu, choose Factory_Default_Cisco_VPN_512_Template.
  5. In Service VPN, click +Add VPN.
  6. Select the VPN template created in Step 4 and click the arrow to move it to the Selected VPN Templates pane and click Next.
    The select sub-templates step appears.
  7. In Additional Cisco VPN Templates, click Cisco BGP.
  8. From the Cisco BGP dropdown menu, choose the BGP template created in Step 5 and click Add.
  9. In Additional Templates, from the CLI Add-On Template dropdown menu choose the CLI template created in Step 6.
  10. Click Update.

Step 8 – Apply the device template to MVE

  1. Go to Configuration > Templates select the Device tab.
  2. Select the MVE template that was copied from the default in Step 1.
  3. Click the ellipses () in the last column and choose Attach Devices.
  4. Select the live MVE that was created before starting Step 1 and move it to the right pane and click Attach.
    Next, enter device-specific information,
  5. Click the ellipses () in the last column and click Edit Device Template.
  6. Enter the following fields:
    • vrf-number – Specify the VRF number (VPN ID) for the interface.
    • ip-address-subinterface – Specify the IP address and mask of the interface.
    • interface-tag – This value is the same as dot-1q-tag.
    • dot-1q-tag – This value is the same as interface-tag. You can find this value in the VXC connection details on the Megaport Portal: click the VXC name, choose Details, and use the A-End VLAN value.
    • Remote AS - Enter the ASN for the remote BGP peer.
    • Description – Enter a meaningful description for the BGP peer.
    • Address – Specify the remote BGP peer IP address.
    • AS Number – Specify the AS number of the MVE.
  7. Click Update.
  8. Click Next.
    vManage displays the Config Preview and Config Diff. Use these features to ensure the correct configuration will be applied.
  9. Select the MVE in the left hand section.
  10. Click Configure Devices.
    vManage pushes the configuration to the MVE. When complete, the status indicates success.

Step 9 – Verify the connection

  1. In vManage, go to Tools > SSH Terminal.
  2. Select the MVE in the device group.
    An SSH terminal opens.
  3. Enter your login details.
  4. Enter the following command to ping the other end of the Megaport VXC from the MVE.

    ping vrf <VPN ID> <IP address>

  5. Enter the following command to confirm the BGP session is up:

    show ip bgp vpnv4 vrf <VPN ID> summary


Last update: