Skip to content
Megaport ONE Documentation
Google Cloud

Connecting to Google Cloud Services

Megaport ONE supports these private and public options to access Google Cloud offerings.

Partner Interconnect

Megaport ONE 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 ONE 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 ONE 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
  • Savings on egress traffic costs from the customer’s VPC network to their on-premises network
  • API integration between Megaport ONE 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 ONE, 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

Before you begin, make sure you have 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

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

  2. From the main menu in the console, select Hybrid Connectivity > Interconnect.
    Interconnect

  3. Click Get Started.

  4. Select Partner Interconnect and click Continue.
    Partner Interconnect

  5. Click I already have a service provider.
    Service provider

  6. Configure your attachment with the following details:

    • Redundancy – Review the options for redundancy and select. You can create redundant Attachments or single Attachment.

    • Network – Select the VPC network that your VPC will connect to.

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

    • Maximum Transmission Unit (MTU) – To use the 1500-byte MTU, the VPC network using the attachment must have an MTU set to 1500. In addition, the on-premises VMs and routers must have an MTU set to 1500. If your network has the default MTU of 1460, leave the field at 1440. VLAN attachment

  7. Click Create.
    A pairing key appears.

  8. Copy the pairing key and click OK.
    Pairing key

Next, you will create a VXC to your Google peering location in the Megaport ONE Portal.

To create a VXC to Google Cloud in the Megaport ONE Portal

  1. In the Megaport ONE Portal, choose Networking > Services.
    If you haven’t already created a Port, see Creating a Port.
  2. Select the Port you want to use.
  3. Click Actions and choose Add Connection.
    Add Connection
  4. Choose Cloud Virtual Cross Connect as the Connection Type.

  5. Select Google Cloud as the Cloud Provider.
    Google as the Cloud Provider

  6. Specify the Google Configuration details:

    • Google Partner Pairing Key – Copy and paste the pairing key from the Google Cloud console.
      The relevant Google targets appear in the Google Locations drop-down list based on the region of your GCI Partner connection.
    • Available Google Ports – Select your chosen target location for your first connection.

  7. Specify the VXC Configuration details:

    • Connection Name – 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.

    • 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 ONE will assign one.

    Alternatively, you can click Untag VLAN. This selection removes the VLAN tagging for this connection but also means that only one VXC can be deployed on this Port.

  8. Specify the Billing Details:

    • Service Level Reference (optional) – Specify a unique identifying number for the VXC 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.

      Note

      Partner-managed accounts can apply a Partner Deal to a service.

    • Promo Code – If you have a promo code, enter it and click Add Code.
      AWS billing details

  9. Click Create Connection to deploy the VXC.

  10. Review the connection details and click Confirm to deploy the connection.
    The deployment can take several minutes.

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

Note

The Google ASN will always be 16550.

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 pairing 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 ONE, the Virtual Cross Connect (VXC) forms a Layer 2 VXC between the customer’s Port and MegaIX.

Direct Peering Requirements:

  • Publicly routable ASN
  • Publicly routable address space (at least one /24 of IPv4 and/or one /48 of IPv6 space)

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.

Megaport - Google IX Peering Locations:

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

See PeeringDB for additional details.

To deploy a Google Direct peering VXC connection

  1. In the Megaport ONE Portal, choose Networking > Services.
  2. Select the Port you want to use.
    If you haven’t already created a Port, see Creating a Port.
  3. Click Actions and choose Add Connection.
    Add Connection
  4. Choose Internet Exchange as the Connection Type.

  5. Specify the details for your VXC:

    • Connection Name – The name of your VXC to be shown in the Megaport ONE Portal.
    • IX Location – Select the Internet Exchange location where a peer will be set up with Google.
    • Rate Limit – This is the speed of your connection in Mbps. Accepted values are in 1 Mbps increments up to the Port rate size.
      VXC details

  6. Specify the IX Configuration details for the connection:

    • Preferred VLAN (optional) – 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. Alternatively, you can click Untag VLAN. This selection removes the VLAN tagging for this connection but also means that only one VXC can be deployed on this Port.
    • ASN – You must own a registered publicly routable ASN.
    • MAC Address – The MAC address of your device used to peer.
    • BGP Password (optional) – Add a BGP password to the connection. This field can be left blank. You cannot change the BGP password after deployment.
    • Graph Visibility (optional) – 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.
    • Peer Macro (optional) – This field appears only for ECIX connections. The peer macro value defines the AS macro filter for the peer. Megaport ONE uses this value to generate a list of prefixes this AS can originate, and this list filters announcements through the route server.
      Another name for this field is AS-MACRO (or AS-SET) as it contains a list of AS numbers belonging to this peer.
      If you don’t have a Peer Macro, you can enter your ASN in this field. (You can only send routes that originate from your own AS.) Invalid prefixes won’t be announced by the route server and an incorrect configuration results in the route server rejecting all your prefixes.
      If not specified, your own ASN will be used in the filter and you can only send routes that originate from your own AS and prefixes registered to that AS.
      Connection details

  7. Specify the Billing Details:

    • Service Level Reference (optional) – Specify a unique identifying number for the VXC 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.

      Note

      Partner-managed accounts can apply a Partner Deal to a service.

    • Promo Code – If you have a promo code, enter it and click Add Code.
      Google billing details

  8. Click Create Connection to deploy the VXC.

  9. Review the peering connection details and click Confirm to deploy the connection.
    The deployment can take several minutes.

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

Last update: 2023-05-16