Connecting to Google Cloud ServicesMegaport supports these private and public options to access Google

Cloud offerings.

Partner Interconnect – to access the private address space (RFC

1918) to access a Virtual Private Cloud (VPC)

Direct Peering – for public access

Partner Interconnect

Megaport makes it easy to provision fast, secure, and private

connections between a customer’s data center and Google Cloud

Platform. As part of the Google Cloud Interconnect (GCI) Partner

program, Megaport provides users with dedicated access to Google

Cloud Platform (GCP) and enables customers to create private

connections between their remote network environments and their

Virtual Private Cloud (VPC) deployments.

The benefits of creating GCI Partner Connections with Megaport

include:

Enhanced security and higher network performance

Connectivity reach beyond Google’s existing network locations

Scalable connectivity for those who do not require the full

bandwidth of Google’s Dedicated Interconnect

•

•

•

•

•

1

Savings on egress traffic costs from the customer’s VPC network to

their on-premises network

API integration between Megaport and Google Cloud which

simplifies the provisioning of connections for a fast and seamless

experience

When connecting to Google Cloud Platform (GCP) through Partner

Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the

Layer 2 component of the connection and Layer 3 BGP is established

directly between the customer and GCP. Through Partner Interconnect,

a customer can access VMs (Virtual Machines) built within a VPC.

Creating a VXC to the Google Cloud Platform

  Watch a 13-minute video overview of connecting to the Google

Cloud.

Before you begin, make sure you’ve performed these tasks:

Created a Partner Interconnect attachment in Google Cloud

Console or gcloud CLI.

Copied the pairing key that is provided as part of the attachment

creation.

To deploy a VXC to Google Cloud Platform

Log in to your Google Cloud Console and create a pairing key.

•

•

•

•

1.

2

From the main menu in the console, select Hybrid Connectivity >

Interconnect.

Click Get Started.

2.

3.

3

Select Partner Interconnect and click Continue.

4.

4

Click I already have a service provider.

5.

5

Configure your attachment.

Provide in the following details:

Redundancy – Review the options for redundancy and select.

You can create redundant Attachments or single Attachment.

VPC Network – Select VPC network you want your VPC to

connect.

Region – Select region where your attachment will connect.

Cloud Router – A Cloud Router to associate with this

attachment. You can only choose a Cloud Router in the VPC

network and region that you selected with an ASN of 16550. If

you don’t have an existing Cloud Router, create one with an

ASN of 16550. For redundancy, each VLAN attachment must

6.

•

•

•

•

6

be associated with a unique Cloud Router. Google

automatically adds an interface and a BGP peer on the Cloud

Router.

VLAN attachment name – Lowercase letters only.

Description – An optional field.

Click Create.

A pairing key appears.

Copy the pairing key and click OK.

In the Megaport Portal, create a VXC to your Google peering

location: click +Connection on the Port for your VXC.

This example has Google GCI Partner as the selected Port.

•

•

7.

8.

9.

7

Click the Cloud tile.

Select Google as the provider.

Copy and paste the pairing key from the Google Cloud console into

the field in the right-hand panel.

10.

11.

12.

8

The relevant Google targets appear based on the region of your GCI

Partner connection.

Select your chosen target location for your first connection and click

Next.

Provide these connection details:

Name Your Connection – This is a free text field allowing you to

assign an easily identifiable name for this connection.

Rate Limit – Enter the same rate you selected for your Google

port speed.

Preferred A-End VLAN – This is the VLAN for this connection

that you will receive through the Port. This must be a unique

VLAN ID on this Port 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 but also means that only one VXC can

be deployed on this Port.

Add the VXC to your cart and configure further VXCs or proceed

through the checkout process.

Once you have completed and deployed the VXC, go back to your

attachment in the Google Cloud Console and accept the attachment.

You will be provided your private IP address from Google to configure

your BGP.

This completes your Layer 2 VXC deployment.

13.

14.

•

•

•

15.

Note

The Google ASN will always be 16550.

9

Google recommends implementing a redundant solution. If you want to

deploy a second GCI Partner connection, you need to create a second

attachment in the Google Console, copy the new paring key into the

Portal, and repeat these steps.

For additional details, see the Google documentation on Google Partner

Interconnects.

Direct Peering

Direct Peering allows Google Cloud Platform (GCP) customers to

connect to Google through carrier-grade connections that can reduce

latency and increase availability versus best-effort internet connections.

Direct Peering with Google is achieved by exchanging BGP routes

between Google and the customer network. Once Direct Peering is in

place, customers can reach all of Google’s services including the full

suite of GCP products.

Features and benefits:

Reduced latency, increase availability

Reduce data egress cost

Secure connectivity

Access to all Google Cloud services and Google apps for business

across one connection

When connecting to GCP Direct Peering with Megaport, the Virtual

Cross Connect (VXC) forms a Layer 2 VXC between the customer’s Port

and Mega-IX or AMS-IX.

Direct Peering Requirements:

Publicly routable ASN

•

•

•

•

•

10

Publicly routable address space (at least one /24 of IPv4 and/or one

/48 of IPv6 space)

Megaport - Google IX Peering Locations:

MegaIX: Ashburn, Dallas, Los Angeles, Seattle, Singapore, Sofia,

Sydney

AMS-IX: Chicago, New York, Bay Area

See PeeringDB for additional details.

To deploy a Google Direct peering VXC connection

Create a VXC in the Megaport Portal to a MegaIX or AMS-IX

Peering location. Click +Connection on the Port to which you want

to attach your VXC.

Select the Internet Exchange tile.

•

Note

Not all customers meet Google’s Direct Peering requirements. Customers are not

required to have 24/7 NOC, but must meet remaining requirements outlined by Google.

•

•

1.

2.

11

Select the MegaIX location where a peer will be set up with Google

and click Next.

3.

12

13

Provide the details for your VXC.

Name your connection - The name of your VXC to be shown in

the Megaport Portal.

Invoice Reference. This is an optional field. It can be any text,

such as a PO number or billing reference number.

Rate Limit - This is the speed of your connection in Mbps.

Accepted values are in 1 Mbps increments up to the Port rate

size.

Click Next.

4.

•

•

•

5.

14

Provide the connection details for the service.

Preferred VLAN – The VLAN for this connection that you will

receive via the Port. This must be a unique VLAN ID on this Port

and can range from 2 to 4093. You can also select the toggle to

“untag” this VXC. This will remove the VLAN tagging for this

connection but will also mean only one VXC can be deployed on

this Port.

6.

•

15

ASN – You must own a registered Publicly routable ASN.

MAC Address – MAC address of your device used to peer.

Graph Visibility – You can select Public or Private visibility. If

Public is selected, the usage graph will be visible on the

MegaIX. If Private is selected, the usage graph will not be

visible.

Click Next and add the VXC and proceed through the checkout

process.

To complete the Google Direct Peering process, you need to register

with Google.

•

•

•

7.

Last update:

16