liveBook · Manning

Interconnect attachment

As explained in Google Anthos in Action

An interconnect attachment is an isolated virtual link provisioned over an interconnect between a GDCE network and a customer network.

An interconnect attachment is an isolated virtual link provisioned over an interconnect to connect a GDCE network with a customer network. It can carry untagged packets or packets tagged with a customer-specified VLAN ID. section 8.3.1

Deployment considerations include:

  • Use the attachment to provide a separate connection, such as a VRF, over the bundled logical link between GDCE and the customer network. section 8.3.1
  • Pair attachments with routers when configuring BGP peering or advertising selected Pod prefixes to GDCE. section 8.3.1
  • Plan interconnect capacity and availability at site initiation; multiple interconnects are typically configured for high availability. section 8.3.1
  • Have system administrators create and maintain the network resources; application owners receive view access only. section 8.3.1
Figure 8.5 Google Distributed Cloud Edge network resource model
08-05

Use the network resource model to relate attachments to GDCE networks, subnetworks, interconnects, and routers. section 8.3.1

How Google Anthos in Action covers it

How deep it goes
Explains isolation, VLAN tagging, routing integration, availability planning, and administrative ownership, but not attachment creation commands.
Examples
Uses VRF isolation, customer VLAN tagging, BGP peering, and Pod prefix advertisement as operational examples.
What you can do after
Operate/configure isolated GDCE-to-customer connectivity and integrate routing through a virtual router.
How it connects
Connects GDCE networks, customer networks, interconnects, VLANs, VRFs, routers, BGP, and Pod subnets.

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.