Create and manage interconnect attachments

This page describes how to create and manage Google Distributed Cloud interconnect attachment resources in a Distributed Cloud connected zone.

This functionality is only available on Distributed Cloud connected racks. Distributed Cloud connected servers don't support interconnect attachment resources.

For more information about Distributed Cloud interconnect attachments, see How Distributed Cloud works.

Keep the following in mind:

• We recommend that you create an interconnect attachment along with its corresponding router at the same time. For more information, see Create a router.
• You can optionally specify a VLAN ID to use to tag the packets that pass through the interconnect attachment.
• The VLAN ID that you specify for packet tagging is local to the interconnect attachment. In other words, a given interconnect attachment is not part of the same Layer 2 domain as the interconnect attachments associated with other interconnects, or subnetworks that are not associated with any interconnect attachments. Therefore, while the VLAN ID specified for packet tagging must be unique across all interconnect attachments created on the target interconnect, it can be reused on other interconnects and on subnetworks not associated with an interconnect attachment.

Create an interconnect attachment

To create a Distributed Cloud interconnect attachment, complete the steps in this section.

To complete this task, you must have the Edge Network Admin role (roles/edgenetwork.admin) in your Google Cloud project.

gcloud edge-cloud networking interconnects attachments dedicated create ATTACHMENT_NAME \
    --interconnect=INTERCONNECT_NAME \
    --network=NETWORK_NAME \
    --location=REGION \
    --zone=ZONE_NAME \
    --vlan-id=VLAN_ID \
    --mtu=MTU_SIZE

POST /v1/projects/PROJECT_ID/locations/REGION/zones/ZONE_NAME/interconnectAttachments?interconnectAttachmentId=ATTACHMENT_ID
 {
  "labels": { LABELS,
   },
  "interconnect": { INTERCONNECT_NAME,
   },
  "network": { NETWORK_NAME,
   },
  "vlanId": { VLAN_ID,
   },
  "mtu": { MTU_SIZE,
   },       
 }   

List interconnect attachments

To list the Distributed Cloud interconnect attachments in a Distributed Cloud connected zone, complete the steps in this section.

To complete this task, you must have the Edge Network Viewer role (roles/edgenetwork.viewer) in your Google Cloud project.

gcloud edge-cloud networking interconnects attachments list \
    --location=REGION \
    --zone=ZONE_NAME

GET /v1/projects/PROJECT_ID/locations/REGION/zones/ZONE_NAME/interconnectAttachments?filter=FILTER&pageSize=PAGE_SIZE&orderBy=SORT_BY&pageToken=PAGE_TOKEN

Get information about an interconnect attachment

To get information about a Distributed Cloud interconnect attachment, complete the steps in this section.

To complete this task, you must have the Edge Network Viewer role (roles/edgenetwork.viewer) in your Google Cloud project.

gcloud edge-cloud networking interconnects attachments describe ATTACHMENT_NAME \
    --location=REGION \
    --zone=ZONE_NAME

GET /v1/projects/PROJECT_ID/locations/REGION/zones/ZONE_NAME/interconnectAttachments/ATTACHMENT_ID

This operation returns detailed information about the resource, including its provisioning state as follows:

• PENDING: the resource has not yet begun provisioning and has not yet been propagated throughout the zone.
• PROVISIONING: the resource is being provisioned; you must wait until it has been propagated throughout the zone.
• RUNNING: the resource has been successfully provisioned and propagated throughout the zone; it is ready to use.
• FAILED: the provisioning of the resource was not successful; the resource has not been propagated throughout the zone.

Delete an interconnect attachment

To delete a Distributed Cloud interconnect attachment, complete the steps in this section.

To complete this task, you must have the Edge Network Admin role (roles/edgenetwork.admin) in your Google Cloud project.

gcloud edge-cloud networking interconnects attachments delete ATTACHMENT_NAME \
    --location=REGION \
    --zone=ZONE_NAME

DELETE /v1/projects/PROJECT_ID/locations/REGION/zones/ZONE_NAME/subnets/SUBNETWORK_ID

What's next

• Deploy workloads on Distributed Cloud connected
• Manage interconnects
• Create and manage networks
• Create and manage routers
• Create and manage subnetworks
• Create and manage VPN connections
• Manage zones