Google Cloud – Hyper Connectivity

Google Cloud under Hyper-Connectivity can be explained under four different areas:

  • Cloud VPN
  • Cloud Interconnect
  • External Peering
  • Cloud DNS

What is Cloud VPN?

  1. Google Cloud VPN connects your on-premises network to your VPC Network through IPSec VPN Connection.
  2. Traffic is encrypted between two networks at one VPN Gateway, and is decrypted at the other VPN Gateway.
  3. There are two types of Cloud VPN Gateways; HA VPN and Classic VPN.
  4. VPN supports two types of routes such as Static routes and Dynamic Routes.
  5. Let us consider an example such as a VPN tunnel which connects the Google Cloud Network and to the rack of 29 subnets in on-premises.
  6. With static routing, You need to update the VPN tunnel which in turn adds the static routes to GCP and the new subnet will be added by restarting the VPN tunnel.
  7. Dynamic routing through VPN is supported through Cloud Router.

Cloud Router

Cloud Router activates you to dynamically exchange routes between your VPC network and on-premises network. It is the router that runs on the cloud to provide BGP routing.

  • The job of a BGP is to discover and dynamically show new route changes in a network.
  • If you are peering with Google in multiple locations having several internal routes, and you want to know about new routes, Cloud Router is a good option.Example: Assume that you have a new environment called Analytics which has a new Subnet range that needs to be known to the on-premises peering network. By using Cloud Router, you can announce that a new subnet range is available. Therefore, the existing BGP router in on-premise will update its routing table and send this information to the analytics process.

Cloud Interconnect

If you want a direct physical connection between your on-premises network and VPC network then Cloud Interconnect is your choice.

  1. Google Cloud Interconnect provides direct physical connection and RFC1918 communication between on-premises and Google’s network.
  2. The traffic between on-premises and Google cloud does not touch public internet. Therefore, the traffic travels through a dedicated connection, resulting in fewer points of failure.
  3. The VPC network IP address can be accessed directly from the on-premises network over a dedicated connection, while an external IP address can be reached only through a separate connection.
  4. The speed of content delivery is 10 Gigabytes per second over one or more ethernet connections (maximum of 8).
  5. Cloud Interconnect has two options – Dedicated & Partner:
    A. Interconnect (Dedicated):
    Provides a direct connection between on-premises and Google network.B.Interconnect (Partner):
    Provides a connection between on-premises and Google cloud through a service provider.

For Interconnected Cloud Option: 
Dedicated Interconnect is used for direct physical connections between an on-premises network and Google’s network.

Dedicated Interconnected is demonstrated above – The cross connection occurs between on-premise router the google peering edge.
  • A cross-connect is provided between Google network and an on-premises router in a common co-location facility. This cross-connect is called a Dedicated Interconnect.
  • A BGP Session is arranged over the interconnect between the on-premises router and cloud router.

On-Premise Network (Partner Connected)

In Google Cloud, on-premises network can be connected with service provider network using VPC Network.
  1. An On-Premises network can be connected to a VPC Network through a Service Provider.
  2. Use Partner Interconnect in cases when a data center cannot reach a Dedicated Interconnect, or if data does not require a 10 gbps connection. (*Important)

External Peering

Direct Peering refers to a private connection between an individual and Google, or an organization and Google by exchanging Autonomous system numbers

  1. Autonomous system number is an identity on the internet that represents the block of IP Address.
  2. Internet traffic can be exchanged between a network and Google’s network at one of their broad-reaching edge network locations.
  3. Direct peering is done by exchanging routes between Google and the Peering Entity.

Carrier Peering – There is a middle-man called Service Provider.

  1. Carrier Peering enables to obtain Enterprise-grade network services that connect your infrastructure to Google by using a service provider.
  2. You will be provided with connections of High availability and Low latency.
  3. To peer with Google, you need an Autonomous System number (15169).

Key Concepts to Remember in Peering:

  • Border Gateway Protocol (BGP) – To route traffic among different internet service providers, or to entities that are assigned their own ASN’s. (*Important)
  • Private Network Interconnect (PNI) is defined as Private Peering.
  • Peering DB is a web-based database of networks that are interested in peering. It is also used to identify candidates for peering.
  • Private Google Access enables VMs on a subnet to reach Google’s API and services by using Internal IP address.
  • It allows VMs to connect to Google’s services without internet access.

What is Cloud DNS?

  1. Google Cloud DNS is the only service that provides 100 % Service Level Agreement (SLA).
  2. Cloud DNS is a Global Domain Name System which publishes domain names to global DNS in an effective way.
  3. Cloud DNS offers both public and private managed DNS Zones.
  4. Public zone is available to open internet, whereas private zone is available to one or more VPC Networks.

Leave a comment

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: