Modify a cross-site network

This page describes how to modify a cross-site network by updating or adding wire groups.

Before you begin

Consider the following before you modify a cross-site network:

  • Bandwidth quotas and limits

    • Increasing bandwidth usage between two metros by updating an existing wire group or adding a new wire group requires that you have enough bandwidth quota between the two metros. You can't add bandwidth if doing so exceeds your quota for the Wire groups unmetered bandwidth per Cloud Interconnect location pair.

      Consider an example in which you want to upgrade your wire group from a single-wire topology to a box-and-cross topology, which includes four wires. The new wire group requires four times the current bandwidth between the metros.

    • The bandwidth that you specify when updating or adding a wire group must not exceed the limit for the Maximum bandwidth per wire.

    Review Check bandwidth quotas and limits and request an increase if necessary.

  • Connection capacity and support for multiple wire groups

    • Increasing bandwidth usage by updating an existing wire group or adding a new wire group requires that you have Cross-Site Interconnect connections with sufficient capacity. If you plan to use existing connections, you must ensure that their capacity isn't already fully used by existing wire groups.

      To view both the provisioned and effective capacity of a connection, see View connection details. If necessary, order new connections.

    • You can create multiple wire groups that use the same Cross-Site Interconnect connections if the wire groups are in VLAN mode. In port mode, you can't use the same Cross-Site Interconnect connection for more than one wire group. For more information, see Traffic modes.

  • Duration of operations that add or remove wires

    • When you initiate an operation that adds or removes a wire, the operation can take several minutes to complete. For example, if you are adding a wire group to your cross-site network, then running the Google Cloud CLI commands to add connections B1 and B2 can take several minutes to complete because Google Cloud provisions the wires A1-B1 and A2-B2.

Add a wire group

This section describes how to add a wire group to an existing cross-site network.

Console

To add a wire group to an existing cross-site network, do the following:

  1. In the Google Cloud console, go to the Interconnect page.

    Go to Interconnect

  2. On the Cross-site networks tab, click the name of the cross-site network to which you want to add a wire group.

  3. Click Add wire group.

  4. Specify the basic details of the wire group to add to the cross-site network.

    • Name: a name for the wire group
    • Description: an optional description of the wire group

  5. Select either VLAN mode or Port mode for your wire group. If necessary, review Traffic modes.

  6. Select a wire group type:

    • Box and cross: Google recommends this type for VLAN mode configurations. For more information, see Box-and-cross topology.
    • Redundant: Google recommends this type for port mode configurations. For more information, see Redundant topology.
    • Single wire: This type is best for non-critical usage where some downtime is acceptable. For more information, see Single-wire topology.

  7. If you configured Port mode, review the Failure detection field. To enable failure detection, select the Disable port checkbox.

    When you enable failure detection, Google Cloud continuously monitors each wire and disables a wire if it loses connectivity so that you can failover to an alternate path, such as another healthy wire in the group.

  8. In the Unmetered bandwidth field, enter the unmetered bandwidth, in Gbps, for the wire group. The bandwidth that you specify is allocated to each wire in the group.

    You can't configure bandwidth that exceeds the following:

    • Your quota between a given pair of metros or the limit for a given wire. If you haven't already, follow the instructions to check quotas and limits for bandwidth.
    • The Cross-Site Interconnect connection capacity.

    For additional considerations for configuring this field, see Wire bandwidth.

  9. Click Next.

  10. Specify the Cross-Site Interconnect connections over which to create your cross-site network.

    1. Depending on your topology, select the connection or redundant connections that you created for your first site, Site A.
    2. Depending on your topology, select the connection or redundant connections that you created for your second site, Site B.

  11. Click Next.

  12. If you configured VLAN mode, specify VLAN tags for each wire in your wire group by entering an integer from 2 to 4093.

    You can't enter a VLAN tag value that is already in use on the same Cross-Site Interconnect connection.

  13. Review the configuration of your wire group, and then click Create wire group.

gcloud

Google Cloud CLI procedure overview

To complete the procedure for adding a wire group to an existing cross-site network by using the Google Cloud CLI, do the following:

  1. Add a wire group to your cross-site network
  2. Add an endpoint and connections for site A to the wire group:
    1. Add an endpoint that represents site A
    2. Add connection A1
    3. Add connection A2 (for redundant and box-and-cross topologies)
  3. Add an endpoint and connections for site B to the wire group:
    1. Add an endpoint that represents site B
    2. Add connection B1
    3. Add connection B2 (for redundant and box-and-cross topologies)

1. Add a wire group

To add a wire group, use the gcloud beta compute interconnects wire-groups create command.

  gcloud beta compute interconnects wire-groups create WIRE_GROUP_NAME \
      --cross-site-network=CROSS_SITE_NETWORK_NAME \
      --type=WIRE_GROUP_TYPE \
      --bandwidth-unmetered=UNMETERED_BANDWIDTH \
      --fault-response=FAILURE_DETECTION \
      [--description=DESCRIPTION]

Replace the following:

  • WIRE_GROUP_NAME: the name of the wire group.
  • CROSS_SITE_NETWORK_NAME: the name of the cross-site network to add the wire group to.
  • WIRE_GROUP_TYPE: the wire group type that corresponds to the topology that you want to create:

  • UNMETERED_BANDWIDTH: the unmetered bandwidth for the wire group in Gbps. The bandwidth that you specify is allocated to each wire in the group.

    You can't configure bandwidth that exceeds the following:

    • Your quota between a given pair of metros or the limit for a given wire. If you haven't already, follow the instructions to check quotas and limits for bandwidth.
    • The Cross-Site Interconnect connection capacity.

    For additional considerations for configuring this field, see Wire bandwidth.

  • FAILURE_DETECTION: Use this flag for port mode configurations only. To enable failure detection, enter DISABLE_PORT. Otherwise, enter NONE.

    When you enable failure detection, Google Cloud continuously monitors each wire and disables a wire if it loses connectivity so that you can failover to an alternate path, such as another healthy wire in the group.

  • DESCRIPTION: an optional description of the wire group.

2a. Add an endpoint for site A

To add an endpoint to the wire group that represents your first site, or site A, use the gcloud beta compute interconnects wire-groups add-endpoint command.

  gcloud beta compute interconnects wire-groups add-endpoint WIRE_GROUP_NAME \
      --cross-site-network=CROSS_SITE_NETWORK_NAME \
      --endpoint-label=ENDPOINT_A_LABEL

Replace the following:

  • WIRE_GROUP_NAME: the name of the wire group that you created previously
  • CROSS_SITE_NETWORK_NAME: the name of the cross-site network to which you are adding a wire group
  • ENDPOINT_A_LABEL: a label for the endpoint, such as ashburn

2b. Add connection A1

To add the first Cross-Site Interconnect connection to the wire group for site A, or connection A1, use the gcloud beta compute interconnects wire-groups add-interconnect command.

  gcloud beta compute interconnects wire-groups add-interconnect WIRE_GROUP_NAME \
      --cross-site-network=CROSS_SITE_NETWORK_NAME \
      --endpoint-label=ENDPOINT_A_LABEL \
      --interconnect-label=INTERCONNECT_CONNECTION_A1_LABEL \
      --interconnect=INTERCONNECT_CONNECTION_A1 \
      --vlan-tags=TRAFFIC_MODE

Replace the following:

  • WIRE_GROUP_NAME: the name of the wire group that you created previously.
  • CROSS_SITE_NETWORK_NAME: the name of the cross-site network to which you are adding a wire group.
  • ENDPOINT_A_LABEL: the existing label that you specified when you created the endpoint for site A.
  • INTERCONNECT_CONNECTION_A1_LABEL: a new label for the first Cross-Site Interconnect connection that you created for site A.
  • INTERCONNECT_CONNECTION_A1: the connection that you created for site A. You can specify the connection by its name, partial URI, or full URI. See the following examples:
    • my-connection
    • projects/my-project/global/interconnects/my-connection
    • https://compute.googleapis.com/compute/beta/projects/my-project/global/interconnects/my-connection

  • TRAFFIC_MODE: the traffic mode configuration for the wires that use this Cross-Site Interconnect connection:

    • To configure port mode, enter -1.

    • To configure VLAN mode, choose one of the following:

      • To auto-allocate VLAN tag values, enter 0.

      • To specify VLAN tag values manually:

        • For single-wire and redundant configurations, enter one tag value, such as 1000. This VLAN tag is used for the wire between connections A1 and B1 (wire A1-B1).
        • For box-and-cross configurations, enter two tag values separated by a comma, such as 1000,2000. The first VLAN tag is used for the wire between connections A1 and B1 (wire A1-B1), and the second VLAN tag is used for the wire between connections A1 and B2 (wire A1-B2).

        A VLAN tag value must be an integer from 2 to 4093. VLAN tags must be the same for both endpoints of a wire. You can't enter a VLAN tag value that is already in use on the Cloud Interconnect connection.

2c. Add connection A2

If you configured a wire group type of REDUNDANT or BOX_AND_CROSS, then add the redundant Cross-Site Interconnect connection to the wire group for site A, or connection A2.

If you configured a wire group type of WIRE, you can skip this step.

  gcloud beta compute interconnects wire-groups add-interconnect WIRE_GROUP_NAME \
      --cross-site-network=CROSS_SITE_NETWORK_NAME \
      --endpoint-label=ENDPOINT_A_LABEL \
      --interconnect-label=INTERCONNECT_CONNECTION_A2_LABEL \
      --interconnect=INTERCONNECT_CONNECTION_A2 \
      --vlan-tags=TRAFFIC_MODE

Replace the following:

  • WIRE_GROUP_NAME: the name of the wire group that you created previously.
  • CROSS_SITE_NETWORK_NAME: the name of the cross-site network to which you are adding a wire group.
  • ENDPOINT_A_LABEL: the existing label that you specified when you created the endpoint for site A.
  • INTERCONNECT_CONNECTION_A2_LABEL: a new label for the redundant Cross-Site Interconnect connection that you created for site A.
  • INTERCONNECT_CONNECTION_A2: the redundant connection that you created for site A. You can specify the connection by its name, partial URI, or full URI. See the following examples:
    • my-connection
    • projects/my-project/global/interconnects/my-connection
    • https://compute.googleapis.com/compute/beta/projects/my-project/global/interconnects/my-connection

  • TRAFFIC_MODE: the traffic mode configuration for the wires that use this Cloud Interconnect connection:

    • To configure port mode, enter -1.

    • To configure VLAN mode, choose one of the following:

      • To auto-allocate VLAN tag values, enter 0.

      • To specify VLAN tag values manually:

        • For redundant configurations, enter one tag value, such as 1000. This VLAN tag is used for the wire between connections A2 and B2 (wire A2-B2).
        • For box-and-cross configurations, enter two tag values separated by a comma, such as 1000,2000. The first VLAN tag is used for the wire between connections A2 and B2 (wire A2-B2), and the second VLAN tag is used for the wire between connections A2 and B1 (wire A2-B1).

        A VLAN tag value must be an integer from 2 to 4093. VLAN tags must be the same for both endpoints of a wire. You can't enter a VLAN tag value that is already in use on the Cloud Interconnect connection.

3a. Add an endpoint for site B

To add an endpoint to the wire group that represents your second site, or site B, use the gcloud beta compute interconnects wire-groups add-endpoint command.

  gcloud beta compute interconnects wire-groups add-endpoint WIRE_GROUP_NAME \
      --cross-site-network=CROSS_SITE_NETWORK_NAME \
      --endpoint-label=ENDPOINT_B_LABEL

Replace the following: Cloud Interconnect connection B1_ * WIRE_GROUP_NAME: the name of the wire group that you created previously * CROSS_SITE_NETWORK_NAME: the name of the cross-site network to which you are adding a wire group * ENDPOINT_B_LABEL: a label for the endpoint, such as chicago

3b. Add connection B1

To add a Cross-Site Interconnect connection to the wire group for site B, or connection B1, use the gcloud beta compute interconnects wire-groups add-interconnect command.

  gcloud beta compute interconnects wire-groups add-interconnect WIRE_GROUP_NAME \
      --cross-site-network=CROSS_SITE_NETWORK_NAME \
      --endpoint-label=ENDPOINT_B_LABEL \
      --interconnect-label=INTERCONNECT_CONNECTION_B1_LABEL \
      --interconnect=INTERCONNECT_CONNECTION_B1 \
      --vlan-tags=TRAFFIC_MODE

Replace the following:

  • WIRE_GROUP_NAME: the name of the wire group that you created previously
  • CROSS_SITE_NETWORK_NAME: the name of the cross-site network to which you are adding a wire group
  • ENDPOINT_B_LABEL: the existing label that you specified when you created the endpoint for site B
  • INTERCONNECT_CONNECTION_B1_LABEL: a new label for the Cross-Site Interconnect connection that you created for site B
  • INTERCONNECT_CONNECTION_B1: the connection that you created for site B. You can specify the connection by its name, partial URI, or full URI. See the following examples:
    • my-connection
    • projects/my-project/global/interconnects/my-connection
    • https://compute.googleapis.com/compute/beta/projects/my-project/global/interconnects/my-connection

  • TRAFFIC_MODE: the traffic mode configuration for the wires that use this Cloud Interconnect connection:

    • To configure port mode, enter -1.

    • To configure VLAN mode, choose one of the following:

      • To auto-allocate VLAN tag values, enter 0.

      • To specify VLAN tag values manually:

        • For single-wire and redundant configurations, enter the same tag value that you specified previously for wire A1-B1.
        • For box-and-cross configurations, enter the same tag values that you specified previously for wire A1-B1 and wire A2-B1 in the following order: A1_B1_TAG, A2_B1_TAG.

3c. Add connection B2

If you configured a wire group type of REDUNDANT or BOX_AND_CROSS, then add the redundant Cross-Site Interconnect connection to the wire group for site B, or connection B2.

If you configured a wire group type of WIRE, you can skip this step.

  gcloud beta compute interconnects wire-groups add-interconnect WIRE_GROUP_NAME \
      --cross-site-network=CROSS_SITE_NETWORK_NAME \
      --endpoint-label=ENDPOINT_B_LABEL \
      --interconnect-label=INTERCONNECT_CONNECTION_B2_LABEL \
      --interconnect=INTERCONNECT_CONNECTION_B2 \
      --vlan-tags=TRAFFIC_MODE

Replace the following:

  • WIRE_GROUP_NAME: the name of the wire group that you created previously
  • CROSS_SITE_NETWORK_NAME: the name of the cross-site network to which you are adding a wire group
  • ENDPOINT_B_LABEL: the existing label that you specified when you created the endpoint for site A
  • INTERCONNECT_CONNECTION_B2_LABEL: a new label for the redundant Cross-Site Interconnect connection that you created for site B.
  • INTERCONNECT_CONNECTION_B2: the redundant connection that you created for site B. You can specify the connection by its name, partial URI, or full URI. See the following examples:
    • my-connection
    • projects/my-project/global/interconnects/my-connection
    • https://compute.googleapis.com/compute/beta/projects/my-project/global/interconnects/my-connection

  • TRAFFIC_MODE: the traffic mode configuration for the wires that use this Cloud Interconnect connection:

    • To configure port mode, enter -1.

    • To configure VLAN mode, choose one of the following:

      • To auto-allocate VLAN tag values, enter 0.

      • To specify VLAN tag values manually:

        • For redundant configurations, enter the same tag value that you specified previously for wire A2-B2.
        • For box-and-cross configurations, enter the same tag values that you specified previously for wire A2-B2 and wire A1-B2 in the following order: A2_B2_TAG, A1_B2_TAG.

Update a wire group

This section describes how to update the following properties of an existing wire group:

  • The description
  • The unmetered bandwidth
  • Whether failure detection is enabled or disabled (applies to port mode only)

See the following to make other changes:

gcloud

To update a wire group, use the gcloud beta compute interconnects wire-groups update command.

  gcloud beta compute interconnects wire-groups update WIRE_GROUP_NAME \
      --cross-site-network=CROSS_SITE_NETWORK_NAME \
      [--bandwidth-unmetered=UNMETERED_BANDWIDTH] \
      [--fault-response=FAILURE_DETECTION] \
      [--description=DESCRIPTION]

Replace the following:

  • WIRE_GROUP_NAME: the name of the wire group
  • CROSS_SITE_NETWORK_NAME: the name of the cross-site network that contains the wire group

  • Depending on which properties you want to update, use the following flags:

    • UNMETERED_BANDWIDTH: the unmetered bandwidth for the wire group in Gbps. The bandwidth that you specify is allocated to each wire in the group.

      You can't configure bandwidth that exceeds the following:

      • Your quota between a given pair of metros or the limit for a given wire. If you haven't already, follow the instructions to check quotas and limits for bandwidth.
      • The Cross-Site Interconnect connection capacity.

      For additional considerations for configuring this field, see Wire bandwidth.

    • FAILURE_DETECTION: Use this flag for port mode configurations only. To enable failure detection, enter DISABLE_PORT. Otherwise, enter NONE.

      When you enable failure detection, Google Cloud continuously monitors each wire and disables a wire if it loses connectivity so that you can failover to an alternate path, such as another healthy wire in the group.

    • DESCRIPTION: the description of the wire group

Upgrade or downgrade your wire group type

This section describes how to upgrade or downgrade your wire group type.

Don't change the traffic mode of your wire group during your upgrade or downgrade operation. If you want to change the traffic mode of your wire group, for example from port mode to VLAN mode, then you must do that before or after you upgrade or downgrade. If you are upgrading to box-and-cross, your wire group must be in VLAN mode before you upgrade.

If you need to get the details of your existing wire groups, such as their endpoint and connection labels, follow the instructions for listing and describing wire groups in View cross-site networks.

Upgrade to redundant

This section describes how to upgrade your wire group type from single-wire to redundant.

gcloud

  1. Update the wire group type by using the gcloud beta compute interconnects wire-groups update command.

    gcloud beta compute interconnects wire-groups update WIRE_GROUP_NAME \
    --type=REDUNDANT

    Replace WIRE_GROUP_NAME with the name of the wire group.

  2. Complete the following steps from the Add a wire group section:

    1. Add connection A2: add a second connection to the existing endpoint for site A.
    2. Add connection B2: add a second connection to the existing endpoint for site B.

Upgrade to box-and-cross

This section describes how to upgrade your wire group type from single-wire or redundant to box-and-cross.

gcloud

  1. If your existing wire group is in port mode, then you must change it to VLAN mode before you upgrade to box-and-cross. See Change the traffic mode of a wire group.

  2. Update the wire group type by using the gcloud beta compute interconnects wire-groups update command.

    gcloud beta compute interconnects wire-groups update WIRE_GROUP_NAME \
    --type=BOX_AND_CROSS

    Replace WIRE_GROUP_NAME with the name of the wire group.

  3. To update your connections, re-add them to your wire group using the existing labels of the connections. If you are upgrading from single-wire, update your existing connections A1 and B1, and add new connections A2 and B2.

    Complete the following steps and configure the --vlan-tags flag as described for box-and-cross wire groups:

    1. Add connection A1
    2. Add connection A2
    3. Add connection B1
    4. Add connection B2

Downgrade to redundant

This section describes how to downgrade your wire group type from box-and-cross to redundant.

gcloud

  1. Update your connections by re-adding them to your wire group using the existing labels of the connections.

    Complete the following steps and configure the --vlan-tags flag as described for redundant wire groups:

    1. Add connection A1
    2. Add connection A2
    3. Add connection B1
    4. Add connection B2

  2. Update the wire group type by using the gcloud beta compute interconnects wire-groups update command.

    gcloud beta compute interconnects wire-groups update WIRE_GROUP_NAME \
    --type=REDUNDANT

    Replace WIRE_GROUP_NAME with the name of the wire group.

Downgrade to single-wire

This section describes how to downgrade your wire group type from box-and-cross or redundant to single-wire.

gcloud

  1. Remove the redundant connection from site A by using the gcloud beta compute interconnects wire-groups remove-interconnect command.

    gcloud beta compute interconnects wire-groups remove-interconnect WIRE_GROUP_NAME \
    --cross-site-network=CROSS_SITE_NETWORK_NAME \
    --endpoint-label=ENDPOINT_A_LABEL \
    --interconnect-label=INTERCONNECT_CONNECTION_A_LABEL

    Replace the following:

    • WIRE_GROUP_NAME: the name of the wire group
    • CROSS_SITE_NETWORK_NAME: the name of the cross-site network
    • ENDPOINT_A_LABEL: the label that you specified when you created the endpoint for site A
    • INTERCONNECT_CONNECTION_A_LABEL: the label of the redundant connection that you added previously for site A

  2. Remove the redundant connection from site B by using the gcloud beta compute interconnects wire-groups remove-interconnect command.

    gcloud beta compute interconnects wire-groups remove-interconnect WIRE_GROUP_NAME \
    --cross-site-network=CROSS_SITE_NETWORK_NAME \
    --endpoint-label=ENDPOINT_B_LABEL \
    --interconnect-label=INTERCONNECT_CONNECTION_B_LABEL

    Replace the following:

    • WIRE_GROUP_NAME: the name of the wire group
    • CROSS_SITE_NETWORK_NAME: the name of the cross-site network
    • ENDPOINT_B_LABEL: the label that you specified when you created the endpoint for site B
    • INTERCONNECT_CONNECTION_B_LABEL: the label of the redundant connection that you added previously for site B

  3. Update the wire group type by using the gcloud beta compute interconnects wire-groups update command.

    gcloud beta compute interconnects wire-groups update WIRE_GROUP_NAME \
  --type=WIRE

    Replace WIRE_GROUP_NAME with the name of the wire group.

Change the traffic mode of a wire group

This section describes how to change the traffic mode of a wire group. You can change single-wire and redundant wire groups between port and VLAN mode. You can't change the mode of a box-and-cross wire group, which must use VLAN mode.

In the following procedure, you delete your existing wires and re-create them with the mode that you want by removing and re-adding your Cross-Site Interconnect connections from and to the wire group.

If you need to get the details of your existing wire groups, such as their endpoint and connection labels, follow the instructions for listing and describing wire groups in View cross-site networks.

gcloud

  1. Remove the existing connections from your wire group by using the gcloud beta compute interconnects wire-groups remove-interconnect command.

    If you have a single-wire group, run the command two times to remove both INTERCONNECT_CONNECTION_A1 and INTERCONNECT_CONNECTION_B1.

    If you have a redundant wire group, run the command four times to remove INTERCONNECT_CONNECTION_A1, INTERCONNECT_CONNECTION_A2, INTERCONNECT_CONNECTION_B1, and INTERCONNECT_CONNECTION_B2.

    gcloud beta compute interconnects wire-groups remove-interconnect WIRE_GROUP_NAME \
    --cross-site-network=CROSS_SITE_NETWORK_NAME \
    --endpoint-label=ENDPOINT_LABEL \
    --interconnect-label=INTERCONNECT_CONNECTION_LABEL

    Replace the following:

    • WIRE_GROUP_NAME: the name of the wire group
    • CROSS_SITE_NETWORK_NAME: the name of the cross-site network
    • ENDPOINT_LABEL: the label that you specified when you created the endpoint for the site
    • INTERCONNECT_CONNECTION_LABEL: the label that you specified when you added the connection to the wire group

  2. Add the connections to your wire group again.

    Complete the following steps and configure the --vlan-tags flag according to the traffic mode that you want to use:

    1. Add connection A1
    2. Add connection A2
    3. Add connection B1
    4. Add connection B2

What's next