Stay organized with collections
Save and categorize content based on your preferences.
You can temporarily disable a VLAN attachment so that it stops forwarding
packets. This can be useful, for example, for testing failover. Disable one
Dedicated Interconnect connection to test that the redundant connection
can successfully serve traffic.
You can enable VLAN attachments, typically after testing for failover.
Drain traffic from a VLAN attachment
Shut down BGP
We recommend that you disable a VLAN attachment by disabling its Border Gateway
Protocol (BGP) session. Disabling only the BGP session instead of disabling the
entire VLAN attachment avoids packet loss. After making this configuration
change, it can take a few minutes for traffic to completely move away. For more
information, see Disable a BGP
session.
Disable a VLAN attachment
If you need to disable your VLAN attachment more rapidly, or if you need to
ensure that zero packets are sent over your VLAN attachment, you can disable the
entire VLAN attachment. This process can incur packet loss. To disable a VLAN
attachment, do the following:
Console
In the Google Cloud console, go to the VLAN attachments tab.
On the VLAN attachments tab, select a VLAN attachment to disable.
On the VLAN attachment details page, click Disable. The
attachment stops forwarding packets within a minute or two. To re-enable
the attachment, click Enable.
gcloud
To disable an existing active attachment, use the --no-admin-enabled
flag:
The attachment stops forwarding packets within a minute or two.
To enable the attachment, use the --admin-enabled flag.
Restore traffic to a VLAN attachment
To restore traffic to your VLAN attachment, you must either enable its BGP
session or enable the VLAN attachment, depending on how you drained traffic
from your VLAN attachment.
Enable BGP
If you disabled your VLAN attachment by disabling its BGP session,
then you must re-enable BGP to make your attachment work again.
Enabling BGP takes a few minutes to take effect. For more information, see
Enable a BGP
session.
Enable a VLAN attachment
If you shut down your VLAN attachment by disabling your VLAN attachment, then
you must enable your VLAN attachment to restore traffic to your attachment.
Do the following:
Console
In the Google Cloud console, go to the VLAN attachments tab.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Disable or enable VLAN attachments\n\nYou can temporarily disable a VLAN attachment so that it stops forwarding\npackets. This can be useful, for example, for testing failover. Disable one\nDedicated Interconnect connection to test that the redundant connection\ncan successfully serve traffic.\n\nYou can enable VLAN attachments, typically after testing for failover.\n\nDrain traffic from a VLAN attachment\n------------------------------------\n\n### Shut down BGP\n\nWe recommend that you disable a VLAN attachment by disabling its Border Gateway\nProtocol (BGP) session. Disabling only the BGP session instead of disabling the\nentire VLAN attachment avoids packet loss. After making this configuration\nchange, it can take a few minutes for traffic to completely move away. For more\ninformation, see [Disable a BGP\nsession](/network-connectivity/docs/router/how-to/disabling-removing-bgp#disable_a_bgp_session).\n\n### Disable a VLAN attachment\n\nIf you need to disable your VLAN attachment more rapidly, or if you need to\nensure that zero packets are sent over your VLAN attachment, you can disable the\nentire VLAN attachment. This process can incur packet loss. To disable a VLAN\nattachment, do the following: \n\n### Console\n\n1. In the Google Cloud console, go to the **VLAN attachments** tab.\n\n [Go to VLAN attachments](https://console.cloud.google.com/hybrid/interconnects/list?tab=attachments)\n2. On the **VLAN attachments** tab, select a VLAN attachment to disable.\n\n3. On the **VLAN attachment details** page, click **Disable** . The\n attachment stops forwarding packets within a minute or two. To re-enable\n the attachment, click **Enable**.\n\n### gcloud\n\nTo disable an existing active attachment, use the `--no-admin-enabled`\nflag:\n\n\u003cbr /\u003e\n\n```\n gcloud compute interconnects attachments dedicated update my-attachment\n --region us-central1\n --no-admin-enabled\n \n```\n\n\u003cbr /\u003e\n\nThe attachment stops forwarding packets within a minute or two.\n\nTo enable the attachment, use the `--admin-enabled` flag.\n\nRestore traffic to a VLAN attachment\n------------------------------------\n\nTo restore traffic to your VLAN attachment, you must either enable its BGP\nsession or enable the VLAN attachment, depending on how you drained traffic\nfrom your VLAN attachment.\n\n### Enable BGP\n\nIf you disabled your VLAN attachment by disabling its BGP session,\nthen you must re-enable BGP to make your attachment work again.\n\nEnabling BGP takes a few minutes to take effect. For more information, see\n[Enable a BGP\nsession](/network-connectivity/docs/router/how-to/disabling-removing-bgp#enable_a_bgp_session).\n\n### Enable a VLAN attachment\n\nIf you shut down your VLAN attachment by disabling your VLAN attachment, then\nyou must enable your VLAN attachment to restore traffic to your attachment.\n\nDo the following: \n\n### Console\n\n1. In the Google Cloud console, go to the **VLAN attachments** tab.\n\n [Go to VLAN attachments](https://console.cloud.google.com/hybrid/interconnects/list?tab=attachments)\n2. On the **VLAN attachments** tab, select a VLAN attachment to enable.\n\n3. On the **VLAN attachment details** page, click **Enable**. The\n attachment starts forwarding packets within a minute or two.\n\n### gcloud\n\nTo enable an existing active attachment, use the `--admin-enabled`\nflag:\n\n\u003cbr /\u003e\n\n```\n gcloud compute interconnects attachments dedicated update my-attachment\n --region us-central1\n --admin-enabled\n \n```\n\n\u003cbr /\u003e\n\nThe attachment starts forwarding packets within a minute or two.\n\nWhat's next\n-----------\n\n- To create an Dedicated Interconnect connection, see the\n [Dedicated Interconnect provisioning overview](/network-connectivity/docs/interconnect/how-to/dedicated/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 Cloud Interconnect, see\n [Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting)."]]
