Google Partner Interconnect
Google Partner Interconnect hosted ports
To create a new Google Partner Interconnect service, customers need to create a VLAN attachment via the Google Cloud Platform portal. Once a VLAN attachment has been requested, customers will receive a pairing key. This pairing key is then used to create the Google cloud port via the Colt On Demand platform.
The pairing key is associated with a region which in turn is associated with a continent (e.g. Europe) – customers will need to select a Google partner interconnect location in the same continent as the pairing key. For example, a pairing key based in a European region will require a European partner interconnect location.
Google Partner Interconnect PoPs are not associated with a specific cloud region – Google provide network connectivity between all regions in the same continent (Europe, APAC, etc.).
Google support bandwidths between 50Mbps and 10Gbps via the partner interconnect service, and are handed over on a shared NNI between Colt and Google.
Resilient connections can be provided – Google support a dual circuit (99.9% SLA) package and a four circuit (99.99% SLA) resilient package which require two and four VLAN attachment and pairing keys respectively. The two VLAN attachments for the dual circuit package requires the Google interconnects to be in the same metro city, in different Edge Availability Domains (zones). The four circuit package is based on two dual circuit packages.
Connections to Google Partner Interconnect ports
Connections to Google Partner Interconnect ports are based on a 1:1 circuit connection to hosted port mapping. The cloud B end configuration is always based on single 802.1Q VLAN* – this is automatically configured when the default “Cloud VLAN” option is selected. * The Ethertype is 8100, although this is not visible to customers
|Application||Open port||Circuit occupies whole A end port||Port based handover, all traffic on the customer port is mapped to the Google cloud port|
|Add VLAN||Customer uses single tagged VLAN to map traffic to Google||VLAN added on egress, towards customer (in translation mode). VLAN can be S-VLAN (88a8) or C-VLAN (8100). Standard H&S config. VLAN contains three “inner” VLANs. Customer needs to map inner VLANs to “outer” tag|
Google Partner Interconnect Configuration
The below diagram summarises the configuration:
Handoff to Google is via a VLAN on a single NNI - based on 802.1Q tagging. Colt automatically assigns a VLAN address on NNI
Ethernet circuit between Google NNI and A end customer site
Handoff to customer is via a dedicated port (open mode) or via an NNI/hub (Add VLAN)
Customer responsible for establishing BGP peering between their router & Google
Google Partner Interconnect customer journey
The customer journey to establish end to end connectivity to a Google Partner Interconnect port is illustrated below:
Google Cloud Dedicated Ports
Connections to 10Gbps Google Cloud dedicated ports can be supported via a standard DCNet On Demand port – providing a DC cross connect is requested via the On Demand portal (the Google LOA should be attached to the cross connect request).