Mit Sammlungen den Überblick behalten
Sie können Inhalte basierend auf Ihren Einstellungen speichern und kategorisieren.
Sie haben die Möglichkeit, sich eine Liste aller VLAN-Anhänge in Ihrem Projekt und Details zu jedem einzelnen anzeigen zu lassen. So können Sie den Namen eines Anhangs und dessen zugehörigen Cloud Routers abrufen, unabhängig davon, ob es sich um einen Anhang für Dedicated Interconnect oder Partner Interconnect handelt.
Console
Wechseln Sie in der Google Cloud Console zum Cloud Interconnect-Tab VLAN-Anhänge.
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Schwer verständlich","hardToUnderstand","thumb-down"],["Informationen oder Beispielcode falsch","incorrectInformationOrSampleCode","thumb-down"],["Benötigte Informationen/Beispiele nicht gefunden","missingTheInformationSamplesINeed","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2025-08-12 (UTC)."],[],[],null,["# View VLAN attachments\n\nYou can view a list of all the VLAN attachments in your project and the details\nabout each one. For example, you can view the name of an attachment, whether\nit's an attachment for Dedicated Interconnect or\nPartner Interconnect, and its associated Cloud Router. \n\n### Console\n\n1. In the Google Cloud console, go to the Cloud Interconnect **VLAN\n attachments** tab.\n\n [Go to VLAN attachments](https://console.cloud.google.com/hybrid/interconnects/list?tab=attachments)\n2. Select a VLAN attachment to view its details.\n\n### gcloud\n\n1. List all VLAN attachments that are in your project:\n\n ```\n gcloud compute interconnects attachments list\n ```\n\n The output is similar to the following: \n\n ```\n NAME: my-attachment\n REGION: us-east1\n TYPE: PARTNER\n INTERCONNECT: some-partner-interconnect\n ROUTER: my-router\n\n NAME: my-second-attachment\n REGION: us-west1\n TYPE: DEDICATED\n INTERCONNECT: some-dedicated-interconnect\n ROUTER: my-second-router\n ...\n ```\n2. Describe the VLAN attachment to view more information about it:\n\n ```\n gcloud compute interconnects attachments describe NAME\n ```\n\n Replace \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e with the name of your VLAN attachment.\n\n The output is similar to the following for IPv4 VLAN attachments: \n\n ```\n adminEnabled: false\n edgeAvailabilityDomain: AVAILABILITY_DOMAIN_1\n bandwidth: BPS_1G\n cloudRouterIpAddress: 169.254.67.201/29\n creationTimestamp: '2017-12-01T08:29:09.886-08:00'\n customerRouterIpAddress: 169.254.67.202/29\n id: '7976913826166357434'\n kind: compute#interconnectAttachment\n labelFingerprint: 42WmSpB8rSM=\n name: NAME\n pairingKey: 7e51371e-72a3-40b5-b844-2e3efefaee59/us-central1/2\n partnerMetadata:\n interconnectName: New York (2)\n partnerName: My Service Provider Inc\n portalUrl: https://service-provider-portal.com\n region: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1\n router: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1/routers/my-router\n selfLink: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1/interconnectAttachments/NAME\n stackType: IPV4_ONLY\n state: PENDING_CUSTOMER\n type: PARTNER\n vlanTag8021q: 1000\n ```\n\n The output is similar to the following for IPv4 and IPv6 (dual stack)\n VLAN attachments: \n\n ```\n adminEnabled: true\n edgeAvailabilityDomain: AVAILABILITY_DOMAIN_1\n bandwidth: BPS_1G\n cloudRouterIpAddress: 169.254.67.201/29\n cloudRouterIpv6Address: 2600:2d00:0:1::1/125\n creationTimestamp: '2017-12-01T08:31:11.580-08:00'\n customerRouterIpAddress: 169.254.67.202/29\n customerRouterIpv6Address: 2600:2d00:0:1::2/125\n description: Interconnect for Customer 1\n id: '7193021941765913888'\n interconnect: https://www.googleapis.com/compute/alpha/projects/partner-project/global/interconnects/lga-2\n kind: compute#interconnectAttachment\n labelFingerprint: 42WmSpB8rSM=\n name: partner-attachment\n partnerMetadata:\n interconnectName: New York (2)\n partnerName: Partner Inc\n portalUrl: https://partner-portal.com\n region: https://www.googleapis.com/compute/alpha/projects/partner-project/regions/us-central1\n selfLink: https://www.googleapis.com/compute/alpha/projects/partner-project/regions/us-central1/interconnectAttachments/customer-attachment\n stackType: IPV4_IPV6\n state: ACTIVE\n type: PARTNER\n vlanTag8021q: 1000\n ```\n| **Note:** The VLAN ID for the connection is for the Google Cloud side of the connection. To configure your on-premises router for Layer 2 connections, use the VLAN ID provided by your service provider.\n\nWhat's next\n-----------\n\n- To create a Partner Interconnect connection, see the\n [Partner Interconnect provisioning overview](/network-connectivity/docs/interconnect/how-to/partner/provisioning-overview).\n\n- To learn more about Cloud Interconnect options, see the\n [Cloud Interconnect overview](/network-connectivity/docs/interconnect/concepts/overview).\n\n- To help you solve common issues that you might encounter when using\n Partner Interconnect, see\n [Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting#partner)."]]
