Cloud Interconnect for dedicated connections in GCP - Commands & Configuration

Introduction

Sometimes your business needs a fast and private connection between your own data center and Google Cloud. Cloud Interconnect for dedicated connections lets you create a direct link that is more reliable and secure than the internet.

When you want to connect your office network directly to Google Cloud without using the public internet.

When you need a stable and fast connection for transferring large amounts of data to your cloud servers.

When your applications require low delay and high security between your data center and cloud resources.

When you want to avoid internet traffic costs by using a private connection.

When you need to connect multiple cloud regions with your own network securely.

Config File - interconnect-config.yaml

interconnect-config.yaml

apiVersion: compute.cnrm.cloud.google.com/v1beta1
kind: ComputeInterconnect
metadata:
  name: example-dedicated-interconnect
spec:
  location: "equinix-ashburn"
  linkType: DEDICATED
  requestedLinkCount: 1
  adminEnabled: true
  description: "Dedicated Interconnect connection to Ashburn"
  mtu: 1500
  customerName: "example-customer"
  interconnectType: DEDICATED
  nocContactEmail: "[e-mail]"
  partnerMetadata:
    partnerName: "equinix"
    partnerInterconnectName: "example-partner-interconnect"

This YAML file defines a dedicated Cloud Interconnect connection in Google Cloud.

• location: The physical location of the interconnect, here Equinix Ashburn.
• linkType: Set to DEDICATED for a direct physical connection.
• requestedLinkCount: Number of physical links requested.
• adminEnabled: Enables the interconnect.
• mtu: Maximum transmission unit size for packets.
• customerName: Your company name for identification.
• nocContactEmail: Email for network operations contact.
• partnerMetadata: Information about the partner providing the connection.

Commands

This command creates a dedicated Cloud Interconnect connection in the Ashburn location with one physical link. It sets your company name and contact email for network operations and enables the interconnect.

Terminal

gcloud compute interconnects create example-dedicated-interconnect --description="Dedicated Interconnect connection to Ashburn" --location=equinix-ashburn --link-type=DEDICATED --requested-link-count=1 --customer-name=example-customer --noc-contact-email=[e-mail] --mtu=1500 --admin-enabled

Expected Output

Created [https://www.googleapis.com/compute/v1/projects/my-project/global/interconnects/example-dedicated-interconnect].

→

--location - Specifies the physical location of the interconnect.

→

--link-type - Defines the type of connection, here DEDICATED for direct physical link.

→

--requested-link-count - Number of physical links requested for redundancy or bandwidth.

This command shows details about the dedicated interconnect you created, including status and configuration.

Terminal

gcloud compute interconnects describe example-dedicated-interconnect

Expected Output

name: example-dedicated-interconnect

location: equinix-ashburn

linkType: DEDICATED

requestedLinkCount: 1

adminEnabled: true

mtu: 1500

customerName: example-customer

nocContactEmail: [e-mail]

state: ACTIVE

This command lists all your Cloud Interconnect connections so you can check their status and details.

Terminal

gcloud compute interconnects list

Expected Output

NAME                          LOCATION          LINK_TYPE  STATE   REQUESTED_LINK_COUNT

example-dedicated-interconnect equinix-ashburn   DEDICATED ACTIVE  1

Key Concept

If you remember nothing else from this pattern, remember: Dedicated Cloud Interconnect creates a private, fast, and reliable link between your data center and Google Cloud.

Common Mistakes

Using the wrong location name for the interconnect.

The interconnect will fail to create because the location must match a supported physical site.

Check the list of supported locations with 'gcloud compute interconnects locations list' and use an exact match.

Not specifying the requested link count or setting it to zero.

The interconnect requires at least one physical link to function.

Always set --requested-link-count to 1 or more depending on your bandwidth needs.

Forgetting to enable the interconnect after creation.

If adminEnabled is false, the interconnect will not be active and traffic won't flow.

Use --admin-enabled flag or update the interconnect to enable it.

Summary

Use 'gcloud compute interconnects create' to set up a dedicated physical connection to Google Cloud.

Verify the connection status with 'gcloud compute interconnects describe' and 'gcloud compute interconnects list'.

Ensure you use correct location and link count values to avoid creation errors.

Practice

1. What is the main purpose of Cloud Interconnect in Google Cloud?

easy

A. To provide a private and fast connection between your on-premises network and Google Cloud

B. To host virtual machines in Google Cloud

C. To store data in Google Cloud Storage

D. To manage user permissions in Google Cloud

Solution

1. Step 1: Understand Cloud Interconnect's role

   Cloud Interconnect is designed to create private network connections between your physical data center and Google Cloud.

2. Step 2: Identify the correct purpose

   Among the options, only private and fast connection matches Cloud Interconnect's function.

3. Final Answer:

   To provide a private and fast connection between your on-premises network and Google Cloud -> Option A

4. Quick Check:

   Cloud Interconnect = Private fast connection [OK]

Hint: Cloud Interconnect connects your network privately to Google Cloud [OK]

Common Mistakes:

• Confusing Cloud Interconnect with storage or VM services
• Thinking it manages user permissions
• Assuming it hosts virtual machines

2. Which of the following is the correct order to set up a Dedicated Cloud Interconnect connection?

easy

A. Create a Cloud Router, then an Interconnect, then an Interconnect Attachment

B. Create an Interconnect, then a Cloud Router, then an Interconnect Attachment

C. Create an Interconnect Attachment, then a Cloud Router, then an Interconnect

D. Create a Cloud Router, then an Interconnect Attachment, then an Interconnect

Solution

1. Step 1: Recall the setup sequence

   First, you create the physical Interconnect, then the Cloud Router to manage routes, and finally attach them with an Interconnect Attachment.

2. Step 2: Match the correct order

   Create an Interconnect, then a Cloud Router, then an Interconnect Attachment correctly lists: Interconnect, Cloud Router, Interconnect Attachment.

3. Final Answer:

   Create an Interconnect, then a Cloud Router, then an Interconnect Attachment -> Option B

4. Quick Check:

   Setup order = Interconnect, Router, Attachment [OK]

Hint: Remember: Interconnect first, then Router, then Attachment [OK]

Common Mistakes:

• Mixing up the order of creating components
• Creating Attachment before Interconnect
• Skipping Cloud Router creation

3. Given the following setup code snippet for a Dedicated Interconnect, what will be the state of the Interconnect Attachment after creation?

interconnect = createInterconnect('my-interconnect')
cloudRouter = createCloudRouter('my-router')
attachment = createInterconnectAttachment(interconnect, cloudRouter)
print(attachment.state)

medium

A. ACTIVE

B. UNKNOWN

C. PENDING

D. FAILED

Solution

1. Step 1: Understand Interconnect Attachment lifecycle

   When an Interconnect Attachment is first created, it starts in a PENDING state until the physical connection is verified and established.

2. Step 2: Determine the initial state after creation

   Since the snippet just created the attachment, it will be in PENDING state before becoming ACTIVE.

3. Final Answer:

   PENDING -> Option C

4. Quick Check:

   New attachment state = PENDING [OK]

Hint: New attachments start as PENDING until connection is active [OK]

Common Mistakes:

• Assuming attachment is ACTIVE immediately
• Confusing FAILED with initial state
• Thinking UNKNOWN is default

4. You created a Dedicated Interconnect and an Interconnect Attachment, but the attachment state remains in PENDING for hours. What is the most likely cause?

medium

A. The physical connection is not yet provisioned by the provider

B. The Cloud Router is misconfigured with wrong BGP settings

C. The Interconnect Attachment was deleted accidentally

D. The Google Cloud project quota is exceeded

Solution

1. Step 1: Analyze the PENDING state meaning

   PENDING means the physical link is not yet active or provisioned by the provider.

2. Step 2: Identify the cause of delay

   If the attachment stays PENDING for hours, it usually means the provider has not completed the physical connection setup.

3. Final Answer:

   The physical connection is not yet provisioned by the provider -> Option A

4. Quick Check:

   PENDING long time = Physical link not ready [OK]

Hint: Long PENDING means physical link not ready from provider [OK]

Common Mistakes:

• Blaming Cloud Router misconfiguration immediately
• Assuming attachment was deleted
• Thinking quota issues cause PENDING state

5. You want to maximize bandwidth and redundancy using Dedicated Cloud Interconnect. Which setup should you choose?

hard

A. Create one Interconnect with multiple Interconnect Attachments in the same location

B. Use VPN tunnels instead of Dedicated Interconnect for redundancy

C. Create one Interconnect and one Cloud Router, then attach multiple VPC networks to it

D. Create two Interconnects in different locations, each with its own Cloud Router and Interconnect Attachment

Solution

1. Step 1: Understand bandwidth and redundancy needs

   To maximize bandwidth and have redundancy, you need multiple physical connections in different locations.

2. Step 2: Evaluate options for redundancy

   Create two Interconnects in different locations, each with its own Cloud Router and Interconnect Attachment creates two Interconnects in different locations, each with its own Cloud Router and Attachment, providing both bandwidth aggregation and failover.

3. Step 3: Rule out other options

   Create one Interconnect with multiple Interconnect Attachments in the same location lacks location diversity; Create one Interconnect and one Cloud Router, then attach multiple VPC networks to it does not increase physical bandwidth; Use VPN tunnels instead of Dedicated Interconnect for redundancy uses VPN, which is slower and not Dedicated Interconnect.

4. Final Answer:

   Create two Interconnects in different locations, each with its own Cloud Router and Interconnect Attachment -> Option D

5. Quick Check:

   Max bandwidth + redundancy = Multiple Interconnects different locations [OK]

Hint: Use multiple Interconnects in different locations for best redundancy [OK]

Common Mistakes:

• Using multiple attachments in one location only
• Relying on single Interconnect for redundancy
• Confusing VPN with Dedicated Interconnect