Cloud Interconnect for dedicated connections in GCP - Step-by-Step Execution

Process Flow - Cloud Interconnect for dedicated connections

Request Dedicated Connection

↓

Google Provisioning Link

↓

Customer Sets Up Router

↓

Establish BGP Sessions

↓

Traffic Flows Over Dedicated Link

↓

Monitor & Manage

This flow shows how a dedicated Cloud Interconnect connection is requested, provisioned by Google, configured by the customer, and then used for traffic.

Execution Sample

GCP

1. Request dedicated connection
2. Google provisions physical link
3. Customer configures router
4. Establish BGP sessions
5. Traffic flows securely

Steps to set up a dedicated Cloud Interconnect connection between customer network and Google Cloud.

Process Table

Step	Action	Result	Next Step
1	Customer requests dedicated connection	Google schedules physical link provisioning	Google provisions link
2	Google provisions physical link	Physical fiber link established	Customer configures router
3	Customer configures router with VLAN and BGP	Router ready to exchange routes	Establish BGP sessions
4	BGP sessions established	Routing information exchanged	Traffic flows over link
5	Traffic flows over dedicated link	Secure, high-bandwidth connection active	Monitor and manage connection
6	Monitor and manage connection	Connection health and usage tracked	Ongoing operation

💡 Process completes when dedicated connection is active and monitored

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
Physical Link Status	Not provisioned	Provisioned	Provisioned	Provisioned and active
Router Configured	No	No	Yes	Yes
BGP Session	Not established	Not established	Established	Established
Traffic Flow	None	None	Active	Active

Key Moments - 2 Insights

Why does the customer need to configure their router after Google provisions the link?

Because Google only provides the physical link; the customer must set up VLANs and BGP sessions to exchange routing information, as shown in steps 3 and 4 of the execution_table.

What happens if BGP sessions are not established?

Without BGP sessions (step 4), routing information won't be exchanged, so traffic cannot flow over the dedicated link (step 5).

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the physical fiber link established?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Check the 'Result' column for step 2 in the execution_table.

According to variable_tracker, when does the BGP session become established?

A After Step 2

B After Step 4

C After Step 3

D At Start

💡 Hint

Look at the 'BGP Session' row and see when it changes to 'Established'.

If the customer skips router configuration, what will be the impact on traffic flow?

A Traffic will flow normally

B Google will configure the router automatically

C Traffic flow will be blocked

D Physical link will not be provisioned

💡 Hint

Refer to steps 3 and 5 in execution_table and router config status in variable_tracker.

Concept Snapshot

Cloud Interconnect dedicated connections provide a private, high-speed link between your network and Google Cloud.
1. Request connection
2. Google provisions physical link
3. Customer configures router with VLAN and BGP
4. BGP sessions exchange routes
5. Traffic flows securely
Monitor connection health continuously.

Full Transcript

Cloud Interconnect for dedicated connections involves requesting a private physical link from Google. Google provisions the fiber link. The customer then configures their router with VLANs and BGP sessions to exchange routing information. Once BGP is established, traffic flows securely over the dedicated link. The connection is monitored for health and usage. This process ensures a reliable, high-bandwidth connection between customer infrastructure and Google Cloud.