[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-08。"],[],[],null,["# Duplicate a VLAN attachment for redundancy\n\nIf you have an existing VLAN attachment for a Partner Interconnect\nconnection, you can create a second one to build redundancy. We recommend\nredundancy so that if one VLAN attachment fails, the other one can continue\nto serve traffic.\n\nTo create a redundant VLAN attachment, it must connect to Google Cloud in the same\nmetropolitan area (city) as the existing VLAN attachment but in a different\n[edge availability domain](/network-connectivity/docs/interconnect/concepts/terminology#edge-availability-domain)\n(metro availability zone).\n**Note:** To build a redundant topology, you must create and configure additional resources. For more information, see [Redundancy and SLA](/network-connectivity/docs/interconnect/concepts/partner-overview#redundancy). \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. Click **Add VLAN attachment**.\n\n3. Select **Partner Interconnect** , and then click **Continue**.\n\n4. Click **I already have a service provider**.\n\n5. Under **Redundancy** , select **Add a redundant VLAN to an existing VLAN**.\n\n6. In the **Select VLAN attachment** field, select the attachment that you\n want to build redundancy for. The new redundant attachment uses the\n same VPC network and region as the existing one.\n\n7. Specify the details of your VLAN attachments:\n\n - **Cloud Router** : Choose the Cloud Router that's associated with the existing attachment. The Cloud Router must have an ASN of `16550`. If you don't have an existing Cloud Router that you can use, [create one](/network-connectivity/docs/router/how-to/creating-routers) with an ASN of `16550`.\n - **VLAN attachment name** : A name for the attachment. This name is displayed in the Google Cloud console and is used by the Google Cloud CLI to reference the attachment, such as `my-attachment`.\n8. Click **Create** to create the attachments, which takes a few minutes.\n\n9. After creation is complete, copy the pairing keys. You need to share\n these keys with your service provider when you request a connection with\n them.\n\n10. Click **OK** to view a list of your VLAN attachments.\n\n### gcloud\n\nUse the existing Cloud Router in the network and region\nthat contains the existing VLAN attachment. The Cloud Router must\nhave an ASN of `16550`. If you don't have an existing Cloud Router\nthat you can use,\n[create one](/network-connectivity/docs/router/how-to/creating-routers)\nbefore you create a VLAN attachment. When you create the\nCloud Router, use `16550` for the BGP ASN.\n\n1. Describe your existing VLAN attachment to view its details. Record its\n edge availability domain (metro availability zone).\n\n2. Create a VLAN attachment of type `PARTNER`, specifying the name of your\n duplicate Cloud Router and a different edge availability domain\n from the existing VLAN attachment:\n\n ```\n gcloud compute interconnects attachments partner create my-second-attachment \\\n --region=REGION \\\n --router=ROUTER_NAME \\\n --edge-availability-domain=AVAILABILITY_DOMAIN\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the region that your VLAN attachment is\n located in\n\n - \u003cvar translate=\"no\"\u003eROUTER_NAME\u003c/var\u003e: the name of your duplicate\n Cloud Router\n\n - \u003cvar translate=\"no\"\u003eAVAILABILITY_DOMAIN\u003c/var\u003e: an edge availability domain\n that's different from your existing VLAN attachment\n\n3. Describe the attachment to retrieve its pairing key; you need to share\n this key with your service provider when you request a connection with\n them:\n\n ```\n gcloud compute interconnects attachments describe my-second-attachment \\\n --region=REGION\n ```\n\n The output is similar to the following: \n\n ```\n adminEnabled: false\n edgeAvailabilityDomain: AVAILABILITY_DOMAIN_2\n creationTimestamp: '2017-12-01T08:29:09.886-08:00'\n id: '7976913826166357434'\n kind: compute#interconnectAttachment\n labelFingerprint: 42WmSpB8rSM=\n name: my-second-attachment\n pairingKey: 7e51371e-72a3-40b5-b844-2e3efefaee59/us-central1/2\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/my-second-attachment\n state: PENDING_PARTNER\n type: PARTNER\n ```\n\n The `pairingKey` field contains the pairing key that you need to\n share with your service provider. Treat the pairing key as sensitive\n information until your VLAN attachment is configured.\n\n The state of the VLAN attachment is `PENDING_PARTNER` until you\n request a connection with your service provider and they complete\n its configuration. After the configuration is complete, the state of\n the attachment changes to `ACTIVE`.\n| **Important:** When you request a redundant connection from your service provider, choose the same metropolitan area that contains your existing VLAN attachment. You can find the existing attachment's location from your service provider.\n\nWhat's next?\n------------\n\n- To request a connection from your service provider, see\n [Request connections](/network-connectivity/docs/interconnect/how-to/partner/requesting-connections).\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)."]]
