<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1705902170274878&amp;ev=PageView&amp;noscript=1">
Skip to content
Talk to Us
  • There are no suggestions because the search field is empty.

Multi Cloud Connect Flex— Google Cloud: Virtual Cloud Connection, Order & Connection

For Google Cloud on Multi Cloud Connect Flex: first create a Partner Interconnect VLAN attachment in the Google Cloud console and copy the pairing key; configure the Virtual Cloud Connection with that key, complete the order, then activate the VLAN attachment.

Unlike Direct, Flex captures your BGP addressing on the Virtual Cloud Connection — interface IP, neighbour IP, subnet (/30), ASN and a BGP key. 

This continues Placing a Multi Cloud Connect Flex Order at the Virtual Cloud Connection step for Google Cloud. Complete the prerequisite below first, then configure the Virtual Cloud Connection, complete the order and finish on the Google Cloud side.

Prerequisite — create the VLAN attachment and copy the pairing key

Prerequisite — before you start

Google Cloud requires a Partner Interconnect VLAN attachment before Tata Communications can provision the connection. Create it in the Google Cloud console and copy the pairing key — you enter that key in the Virtual Cloud Connection. This is the Google Cloud equivalent of the Azure ExpressRoute service key.

  1. In the Google Cloud console, search for Interconnect and open Network Connectivity → Interconnect.

  2. Select Partner Interconnect, click Continue, then choose “I already have a service provider”.

  3. Enter the details below, then click Create.


    Field

    Information

    What it is / Sample Value

    Mandatory

    Redundancy

    Whether to create a single or a redundant pair of VLAN attachments for high availability.

    Create a redundant pair of VLAN attachments

    Yes

    Network

    The VPC network the VLAN attachment is attached to.

    your VPC network

    Yes

    Region

    The region where the VLAN attachment is created (not editable after creation).

    your GCP region

    Yes

    Cloud Router

    Required for dynamic routing over BGP; select an existing Cloud Router or create one.

    your Cloud Router

    Yes

    Name

    A unique name for the VLAN attachment.

    unique name

    Yes

    Description

    Optional context for the attachment.

    optional

    No

    IP Stack Type

    The IP protocol support for the VLAN attachment.

    IPv4 (single stack)

    Yes

    MTU

    Maximum Transmission Unit size for the connection.

    Default

    No

    BGP IPv4 Address Allocation

    How BGP peering addresses are assigned. Google can auto-allocate the link-local range.

    Automatically allocate link-local range

    Yes

  4. Once the VLAN attachment is created, copy the Pairing Key from the Pairing keys section — you share it with Tata Communications and enter it in the Virtual Cloud Connection.

 

Virtual Cloud Connection — Google Cloud

Double-click the Virtual Cloud Connection icon and enter the required configuration details as shown in the screenshots. Once completed, click Save and Validate.

Field

Information

What it is / Sample Value

Mandatory

MCC Flavor

Virtual Cloud Connect supports MCC Flavors:

  • Direct: Direct connection from Tata Communications PoP to the Cloud Service Provider (CSP).

  • Flex: Includes a Virtual Network Function (VNF) between the PoP and CSP for advanced networking (e.g., firewall, SD-WAN). 

 Flex 

Yes

CSP

Select the Cloud Service Provider (CSP) with which you intend to establish Direct Connectivity.

Google Cloud

Yes

Alias Name

Alias Name acts as a unique identifier to link components, enabling easy reference throughout the solution.

 GCP_Delhi_VC 

Yes

Location

Select the desired CSP Direct Connect location based on your deployment requirements.

 Delhi 

Yes

Data Center

Select the data center corresponding to the CSP Direct Connect location where you want to establish connectivity.

STT Delhi DC1 – TF, VSB, India

Yes

Link Type

Specifies the connection setup between the VNF and the CSP:

  1. Single Link - Establishes a single logical connection between the Fabric Port/VNF and the CSP.

  2. Dual Link - Provides two independent connections between the Fabric Port/VNF and the CSP to ensure redundancy and high availability.

Single 

Yes

Select or Add Port

Select the Fabric port

Router_Delhi 

No

Bandwidth

Specify the bandwidth for the Virtual Cloud Connect link between the Fabric Port/VNF and the CSP.

50 Mbps

Yes

Redundancy Type

Choose Primary or Secondary in case of Dual Connectivity.

Primary

Yes

Pairing Key

Enter the GCP Pairing Key generated in the Google Cloud console to establish the Partner Interconnect; this key uniquely identifies your VLAN attachment.

Use the GCP Pairing Key created at the beginning of the demo guide.

Yes

AS Number (Local)

Specify the Autonomous System (AS) number assigned to your local network for BGP configuration.

—

No

AS Number (Global)

Provide the global AS number if a unified AS is used across multiple regions or locations.

64566

Yes

Peer Type

Select the desired CSP Peer Type:

  • Private - A private virtual interface should be used to access an VPC/VNet using private IP addresses

  • Public - A public virtual interface can access all public services using public IP addresses.

  • Transit - A transit virtual interface should be used to access one or more VPC/VNet Transit Gateways associated with Direct Connect/ExpressRoute gateways.

Private

Yes

Enable BFD

Enable Bidirectional Forwarding Detection (BFD) to quickly detect link failures in the BGP session.

No

No

BFD Multiplier

Set the BFD detection multiplier, which defines how many missed messages indicate a failure.

3

No

BFD Transmit Interval

Specify the time interval (in milliseconds) between sending BFD packets to the peer.

300

No

BFD Receive Interval

Specify the minimum time (in milliseconds) the system expects between receiving BFD packets from the peer.

300

No

IP address for Interface

Provide the IP address to be configured on your interface for BGP peering.

192.168.1.1

Yes

Neighbor IP

Enter the IP address of the BGP peer (CSP interface) to establish the connection.

192.168.1.2

Yes

Subnet

Specify the subnet mask for the IP address used in the BGP interface configuration.

30

Yes

BGP Key

Enter the shared password (authentication key) used to secure the BGP session.

a customer-chosen secret

Yes

On Google Cloud you do not enter an ASN or a BGP key — Google allocates the BGP link-local addressing automatically.

Complete the order

  1. Set the Contract Term. The Total Contract Value (TCV) refreshes automatically; click Price Breakup to see the component-wise charges.

  2. On the Price Breakup screen, review the charges. You can download the draft quote and click Get Ask Price for specific pricing.

  3. Enter the expected ARC and NRC, then Submit.

  4. Click Checkout to place the order.

  5. Enter the Customer Contracting Entity details, then click Generate Order Form.

    Field

    Information

    What it is / Sample Value

    Mandatory

    Select number of legal entities

    Whether the service is contracted under a single legal entity or split across multiple.

    Single or Multiple

    Yes

    Name

    The contracting legal entity the order is raised under.

    your legal entity

    Yes

    Address

    The registered address of the contracting entity.

    entity address

    Yes

    Email ID

    Contact email for the order and order-form correspondence.

    contact email

    Yes

    Contact name

    The person Tata Communications should contact about the order.

    contact name

    Yes

    Contact number

    A phone number for that contact.

    contact number

    Yes




  6. Review the Order Form — Terms and Conditions, Total Charges, Billing and Payments, Contracting Information and Order Summary — and check the agreement box.

  7. Click Order as You Click to submit directly, or choose DocuSign / Delegate Signature to send the Customer Order Form to another approver.

  8. Click Preview eCOF to view or download the draft Customer Order Form. Provisioning begins once the order is signed.

Get Network Config

Once the order is provisioned, open Inventory → IZO™+ Multi Cloud Connect to view the provisioned components — Fabric Port, Fabric Edge, Connections and the full Solution Inventory.

  1. Open the Connections inventory and confirm your Virtual Cloud Connection reaches Active state — when it is Active, the BGP connection has established successfully.

Note
Unlike Direct on Google Cloud (where Google auto-allocates the BGP link-local addressing), Flex captures the interface IP, neighbour IP and BGP key on the Virtual Cloud Connection, so those are the addresses used for peering. 

Google Cloud side — activate the VLAN attachment

These steps are completed in the Google Cloud console 

1. Activate the VLAN attachment

Once Tata Communications has provisioned the connection, open Network Connectivity → Interconnect and activate the pending VLAN attachment so the Cloud Router can establish BGP. Google assigns the BGP peering addresses automatically — there is nothing to enter from Get Network Config.

2. Confirm BGP is up

When the VLAN attachment is active and the Cloud Router session establishes, BGP is up — the end-to-end connection is complete. You can confirm the connection is in Active state in the TCx Portal inventory.

For the full Google Cloud-side reference, see Google Cloud Connection Setup.

Related pages