If you have an existing VLAN attachment for a Partner Interconnect connection, you can create a second one to build redundancy. We recommend redundancy so that if one VLAN attachment fails, the other one can continue to serve traffic.
To create a redundant VLAN attachment, it must connect to Google Cloud in the same metropolitan area (city) as the existing VLAN attachment but in a different edge availability domain (metro availability zone).
In the Google Cloud Console, go to the Cloud Interconnect VLAN attachments tab.
Click Add VLAN attachment.
Select Partner Interconnect, and then click Continue.
Click I already have a service provider.
Under Redundancy, select Add a redundant VLAN to an existing VLAN.
In the Select VLAN attachment field, select the attachment that you want to build redundancy for. The new redundant attachment uses the same VPC network and region as the existing one.
Specify the details of your VLAN attachments:
- Cloud Router: Choose the Cloud Router that's associated
with the existing attachment. The Cloud Router must have an
16550. If you don't have an existing Cloud Router that you can use, create one with an ASN of
- VLAN attachment name: A name for the attachment. This name
is displayed in the Cloud Console and is used by the
gcloudcommand-line tool to reference the attachment, such as
- Cloud Router: Choose the Cloud Router that's associated with the existing attachment. The Cloud Router must have an ASN of
Click Create to create the attachments, which takes a few minutes.
After creation is complete, copy the pairing keys. You need to share these keys with your service provider when you request a connection with them.
Click OK to view a list of your VLAN attachments.
Use the existing Cloud Router in the network and region
that contains the existing VLAN attachment. The Cloud Router must
have an ASN of
16550. If you don't have an existing Cloud Router
that you can use,
before you create a VLAN attachment. When you create the
Cloud Router, use
16550 for the BGP ASN.
Describe your existing VLAN attachment to view its details. Record its edge availability domain (metro availability zone).
Create a VLAN attachment of type
PARTNER, specifying the name of your duplicate Cloud Router and a different edge availability domain from the existing VLAN attachment.
The following example creates a VLAN attachment in edge availability domain
availability-domain-2and is associated with the Cloud Router
my-router, which is in the region
gcloud compute interconnects attachments partner create my-second-attachment \ --region us-central1 \ --router my-router \ --edge-availability-domain availability-domain-2
Describe the attachment to retrieve its pairing key; you need to share this key with your service provider when you request a connection with them:
gcloud compute interconnects attachments describe my-second-attachment \ --region us-central1
adminEnabled: false edgeAvailabilityDomain: AVAILABILITY_DOMAIN_2 creationTimestamp: '2017-12-01T08:29:09.886-08:00' id: '7976913826166357434' kind: compute#interconnectAttachment labelFingerprint: 42WmSpB8rSM= name: my-second-attachment pairingKey: 7e51371e-72a3-40b5-b844-2e3efefaee59/us-central1/2 region: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1 router: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1/routers/my-router selfLink: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1/interconnectAttachments/my-second-attachment state: PENDING_PARTNER type: PARTNER
pairingKeyfield contains the pairing key that you need to share with your service provider. Treat the pairing key as sensitive information until your VLAN attachment is configured.
The state of the VLAN attachment is
PENDING_PARTNERuntil you request a connection with your service provider and they complete its configuration. After the configuration is complete, the state of the attachment changes to
To request a connection from your service provider, see Requesting connections.
To create an Interconnect connection, see the Partner Interconnect provisioning overview.
To learn more about Cloud Interconnect options, see the Cloud Interconnect overview.
To help you solve common issues that you might encounter when using Partner Interconnect, see Troubleshooting.