Cisco SD-WAN Cloud Interconnect with Megaport Ordering Guide

 

What’s inside

●     At a glance: The Cisco SD-WAN Cloud Interconnect with Megaport solution

●     Components of the solution

●     Product ordering information

●     Product purchasing reference

1. At a glance: The Cisco SD-WAN Cloud Interconnect with Megaport solution

As businesses accelerate adoption of hybrid, multicloud network environments, managing multiple network providers and connecting branches to clouds and data centers can be complicated and time consuming. Cisco^® SD-WAN’s integration with Megaport allows customers to provision secure, highly reliable connections from any branch to Amazon Web Services (AWS), Microsoft Azure, and Google Cloud, as well as to other branches, directly from Cisco vManage. All Megaport components (Megaport Virtual Edge [MVE] and Virtual Cross Connects [VXC]) can be provisioned through vManage.

This solution is cloud agnostic and data center agnostic, so regardless of where a customer’s branch or data center is located, they will be able to connect to the nearest Megaport Point of Presence (PoP) through their SD-WAN controller and then ride Megaport’s private backbone to AWS, Azure, Google Cloud, or another Megaport PoP.

As part of the solution, we have enabled the two major use cases detailed below.

Use cases

1.1. Site to multicloud

This use case enables customers to provision direct connections from their branch or data center locations to their cloud deployments at AWS, Microsoft Azure, or Google Cloud using the Megaport underlay backbone. All connections can be provisioned directly through vManage. For the site-to-cloud use case, customers need to purchase at least one Megaport Virtual Edge (MVE) and one Virtual Cross Connect (VXC). The MVE would be hosted at a Megaport PoP based on the region for which the customer purchases it. A list of SKUs available for the MVE is provided in the “Ordering the Interconnect Gateway (or Megaport Virtual Edge)” section. A list of SKUs for the VXCs is provided in the “Ordering a VXC” section. Each MVE needs a Cisco DNA Advantage or Cisco DNA Premier license (bring your own license or purchase it a la carte) along with the HSEC license.

1.2. Site to site

This use case enables customers to provision connections between their branches or data center locations using the Megaport underlay backbone. It is a much cheaper alternative to using Multiprotocol Label Switching (MPLS) circuits to provision connectivity between sites, and all connections can be enabled directly through vManage. For the site-to-site use case, customers need to purchase at least two MVEs and one VXC. The MVEs would be hosted at a Megaport PoP based on the regions for which the customer purchased them. A list of SKUs for the MVEs is provided in the “Ordering the Interconnect Gateway (or Megaport Virtual Edge)” section. A list of SKUs for the VXCs is provided in the “Ordering a VXC” section. Each MVE needs a Cisco DNA Advantage or Cisco DNA Premier license (bring your own license or purchase it a la carte), along with the HSEC license.

2. Solution and deployment building blocks

The Cisco SD-WAN Cloud Interconnect solution with Megaport consists of the following components. All SKUs for these components can be ordered under CLD-INTCNT-MPT-C ATO. This ATO is part of a Major Line Bundle offer CLD-INTRCNT-MPT-BN which includes the HSEC license for use with this solution.

2.1. Cisco Interconnect Gateway (aka Megaport Virtual Edge)

The Cisco Interconnect Gateway (Megaport Virtual Edge) is the virtual compute instance of the Cisco Catalyst^® 8000V router that is brought up at the Megaport PoP. Customers purchase this compute instance through Cisco Commerce (CCW).

●     Offered in different sizes (small – 500 Mbps, medium – 1 Gbps, and large – 5 Gbps)

●     Each MVE can be shared across multiple VXCs

●     Includes IP transit (internet connection at the MVE for branches to reach the MVE)

●     Price varies by size and region of deployment

2.2. Virtual Cross Connect (VXC)

The VXC is the connection provisioned from the MVE to the customer’s cloud instance or to another MVE. Two types of cross-connects can be purchased. Prices vary based on bandwidth and region of connection. Both types of routes are reserved-bandwidth connections that are dedicated to the customer.

●     Inter/intra region routes (long-haul routes)

●     InMetro routes (short-haul routes)

2.3. Catalyst 8000V Edge Software license

The Catalyst 8000V license is required for the Interconnect Gateway (MVE) hosted at the Megaport site. Customers can bring their own Cisco DNA Advantage or Premier license, which allows them to instantiate a Catalyst 8000V device on the MVE hosted at the Megaport site.

Building blocks of Cisco SD-WAN Cloud Interconnect with Megaport

The following sections walk through the ordering of these elements to deploy the Cisco SD-WAN Cloud Interconnect solution with Megaport.

3. Solution ordering

All components of this solutions can be ordered through CCW under the CLD-INTRCNT-MPT-BN ATO product ID. Once they have been ordered, customers will receive an email from Megaport to set up their Megaport credentials for use within vManage. After logging in to vManage, customers will then be able to provision the Megaport components (MVE and VXC) through vManage under the Cloud OnRamp for Multicloud (Interconnect tab) flows. All the SKUs are available for a 1-year minimum commit term.

3.1. Ordering the Interconnect Gateway (or Megaport Virtual Edge)

Each MVE SKU is based on the size and location of the MVE. The MVE is offered in three different sizes (small – 500 Mbps, medium – 1 Gbps, and large – 5 Gbps) and can be deployed in the six regions detailed below. There are multiple MVE-enabled metros within a region, and within each metro there are multiple MVE-enabled data centers for redundancy. A particular MVE SKU allows customers to bring up an MVE of that size at any Megaport PoP location within the entire region. For connections to cloud environments, customers need one MVE hosted at the Megaport PoP closest to the branch and one VXC connecting to the cloud of their choice. For site-to-site connections, customers will need two MVEs, ideally hosted at the PoPs closest to the branches or data centers they would like to interconnect, and one VXC connecting the two MVEs together.

3.1.1. MVE metro locations in each region

●     NA (North America): Ashburn, Atlanta, Bay Area, Chicago, Dallas, Denver, Los Angeles, New York, Phoenix, Seattle, Toronto

●     EU (Europe): Amsterdam, Frankfurt

●     ASIA (Asia): Hong Kong, Singapore, Osaka, Tokyo

●     AU (Australia): Melbourne, Perth, Sydney

●     NZ (New Zealand): Auckland

●     UK (United Kingdom): London

Table 1.           List of SKUs for MVE

3.1.2. Choosing the MVE SKU based on bandwidth and region

The MVE SKU should be chosen based on proximity to branches and sized based on the amount of traffic that is anticipated to arrive at the MVE over the internet. Multiple SD-WAN-enabled branches can connect to one MVE. It is recommended that the aggregate bandwidth of all sites connecting to an MVE not exceed the maximum bandwidth of the MVE on the branch-facing side. The small MVE (2-core instance) can receive up to 500 Mbps of internet traffic. The medium MVE (4-core instance) can receive up to 1 Gbps of internet traffic. The large MVE (8-core instance) can receive up to 5 Gbps of internet traffic.

3.1.3. Automatic attach of IP transit to MVE

Regional MVE pricing is a bundle of MVE and IP transit (the local internet connection to MVE). The appropriate IP transit SKU is automatically expanded when a MVE is selected in CCW. IP transit is a mandatory component of the MVE and is priced separately to keep customers aware of IP transit charges in each region.

Table 2.           List of SKUs for IP transit

3.2. Ordering a Virtual Cross Connect (VXC)

There are two types of VXCs that can be purchased as part of the solution. These are described in the following sections.

3.2.1. InMetro VXC (short haul)

This VXC allows customers to connect from an MVE to a Cloud OnRamp instance located in the same metro or to another MVE in the same metro. These VXCs act as the direct connects to the cloud service provider (AWS Direct Connect, Azure Express Route, Google Partner Interconnect). They are available in two bandwidths: 1 Gbps and 10 Gbps. The price varies depending on the region where the customer wants to connect.

Table 3.           List of SKUs for InMetro VXCs

3.2.2. Inter/intra region VXC (long haul)

This VXC allows customers to connect from an MVE to a Cloud OnRamp instance located in a different metro within or outside the region, or to another MVE in a different metro within or outside the region. These types of VXCs are typically used for site-to-site connectivity but can also be used as direct connects that connect to the cloud service provider (AWS, Azure or Google Cloud) in different regions. The price varies depending on the region of origin and destination of the VXC. These cross connects are available in 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, and 10 Gbps. Customers can order one VXC per order. To purchase multiple inter/intra region VXCs, customers must place multiple orders.

Table 4.           List of SKUs for inter/intra region VXCs

3.2.3. AWS Hosted Connection add-on

The AWS Hosted Connection is a popular mechanism to connect to an AWS Transit Gateway. The AWS Hosted Connection SKUs can be added on for an additional surcharge to any type of VXC. Choose the AWS-HC-IIVXC-C SKU to use the inter or intra region VXC as a Hosted Connection. The quantity of the AWS-HC-IIVXC-C should match the quantity of the VXC-II-^* SKU chosen.

Choose the AWS-HC-IMVXC-1G-C or AWS-HC-IMVXC-10G-C SKU for using the InMetro VXC as an AWS Hosted Connection. The quantity of the AWS-HC-IMVXC-^* SKU should match the quantity of the corresponding InMetro VXC-IM-^* SKU chosen.

Table 5.           List of SKUs for AWS Hosted Connection

3.3. Ordering Cisco SD-WAN DNA licenses for Cisco SD-WAN Cloud Interconnect

As part of this solution, customers need a Cisco DNA Advantage or Premier license (Tier 2 or Tier 3) for bringing up the Catalyst 8000V on the MVE at the Megaport site. The Cisco DNA license is used to generate the Catalyst 8000V template from Cisco’s licensing portal. Customers can bring their own Cisco DNA licenses to this solution or purchase the license to use specifically with this solution. The following SKUs are available for purchase as part of this solution. The Tier 2 Cisco DNA license must be used with the small or medium MVE versions. The Tier 3 Cisco DNA license must be used with the large MVE version.

Table 6.           List of SKUs for Cisco DNA Catalyst 8000V SDCI license

3.3.1. Ordering the HSEC license for Catalyst 8000V

As per U.S government regulations and export restrictions, for a product to have full crypto functionality, a mandatory High Security (HSEC) license needs to be enforced. Without a HSEC license, only 1000 secure tunnels and a unidirectional crypto throughput of up to 250 Mbps is available. When one of the above Cisco DNA subscription bandwidth licenses are chosen, the C8000V-HSEC license is automatically expanded into the offer. This is not an HSEC license by itself; rather, it entitles the customer to an HSEC license. The HSEC license (C8000V-HSEC=) gets attached as a Major Line Bundle (MLB) offer under the CLD-INTRNCT-MPT-BN bundle. The CLD-INTRCNT-MPT-C and the HSEC product ID make up the MLB offer.

4. Ordering Solution Support

Since this is an SD-WAN-enabled solution, the support for the product is a joint effort between Megaport and Cisco. Solution Support is automatically expanded with the purchase of an MVE, since the MVE is the compute instance for hosting the Catalyst 8000V. The Solution Support SKUs are detailed below and are automatically expanded based on the MVE instance size.

Table 7.           List of SKUs for Solution Support

Cisco front-ends all support for the solution through the Cisco Solution Support program

●     Initial triage; support and product entitlement verification

●     Support ticketing and triage (identify Cisco SD-WAN or Megaport issue)

●     Troubleshooting of Cisco SD-WAN components provided by Cisco Technical Assistance Center (TAC)

Customers will receive Solution Support contract information when they order this solution directly from Cisco.

Joint support for Megaport components

●     Cisco TAC creates a case with Megaport TAC if an issue is found with Megaport devices

●     Ticketing integration and transfer is automated between Cisco and Megaport

●     Engineering support, expert lab, bug fixes, patches, maintenance releases, etc.

Megaport support information is provided in the section below.

5. Warranty coverage and technical service options

All support, warranty, and End User License Agreement (EULA) related to the SolutionsPlus offers are provided directly by third-party vendors.

Megaport GSA/EULA: https://www.megaport.com/legal/global-services-agreement/

Megaport customer support alias: support@megaport.com

Megaport phone support: +61 7 3062 7601

6. Sample Bill of Materials (BOM)

A sample BOM is provided below. Prices shown are Cisco list prices for the components.

Use case

Customer has multiple branches on the U.S. West Coast that need to connect to AWS-West

Customer has multiple branches on the U.S. East Coast that need to connect to AWS-East

Branches in Seattle need to connect to branches in London

BOM

1 and 2. Two small North America MVEs + two IP transits in North America

3 and 4. One small UK MVE + one IP transit in UK

5. Two 1 Gbps InMetro connections to AWS-West and AWS-East

6. One VXC from North America to UK (500 Mbps)

7. One Cisco DNA Catalyst 8000V license

Network topology for sample BOM

Order 1: Two small NA MVEs (Seattle + Ashburn) + two small NA IP transits (Seattle + Ashburn) + one small UK MVE (London) + two InMetro <1 Gbps VXCs (Seattle and Ashburn) + one NA-UK intra/inter region VXC – 500 Mbps (Seattle to London) + three Tier 2 Catalyst 8000V licenses + Solution Support for three small MVEs.

If the customer wants to use AWS Hosted Connections to AWS, the appropriate AWS Hosted Connection SKU must be added for each VXC.

Table 8.           Pricing details for BOM

7. Additional documentation

Cisco SD-WAN Cloud Interconnect FAQ

Cisco SD-WAN Cloud Interconnect At-a-Glance

Cisco SD-WAN Cloud OnRamp Configuration Guide

Deal Registration

8. SolutionsPlus additional discount approval process

If the requested discount is greater than 20% of list price, the following approval steps must be taken:

Step 1. The Cisco account representative (AM/PSS) requests vendor approval via email to sales@megaport.com, including the following data:

1.     Deal opportunity (SolutionsPlus revenue only)

2.     Customer/reseller name

3.     Date of installation

4.     Discount needed/net price needed

5.     Cisco part numbers included in the deal

6.     Justification for additional discount

7.     Cisco SKU description

8.     Cisco unit price

9.     Pricing term (for subscription deals)

10.  Quantity

11.  Cisco unit net price

12.  Cisco discount (this is the total discount approved off Cisco MRSP)

13.  Cisco extended net price

14.  Currency used in the quote

Step 2. The vendor responds within ONE (1) business day by sending an email to the Cisco AM/PSS with an approved quote with the following information:

1.     All the items above from the original request

2.     Date of approval

3.     Expiration date of approval (valid for a minimum of 90 days from date of Cisco deal approval)

4.     Vendor approval ID #

Step 3. After the AM/PSS receives the approved quote from the vendor, the AM/PSS will follow the Cisco DSA (Deal Support Automation) process.

Step 4. The AM enters the solutions.

9. Credit memos

Note:       All SolutionsPlus products are discount restricted and are NOT eligible for any additional discounts, including applying credit memos.