Create a cross-site network

You can create cross-site networks over connections that have passed all tests and are ready to use.

To create a cross-site network, follow these steps:

Console

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

    Go to Interconnect

  2. On the Cross-site networks tab, click Create cross-site network.

  3. Specify the details of the cross-site network:

    • Name: a name for the cross-site network
    • Description: an optional description of the cross-site network

  4. Click Next.

  5. 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.

  6. Select either VLAN mode or Port mode for your wire group. If necessary, review Traffic modes in the Cross-Site Interconnect overview.

  7. 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.

  8. 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.

  9. 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.

  10. Click Next.

  11. 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.

  12. Click Next.

  13. 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.

  14. Review the configuration of your cross-site network, and then click Create network.

  15. If necessary, create additional wire groups in the cross-site network by following the instructions to add a wire group. You might want to add a wire group for the following reasons:

    • To add more bandwidth between site A and site B.

    • To connect additional sites. For example, you can add wire groups that connect an additional site, site C, to site A and site B.

gcloud

Google Cloud CLI procedure overview

To complete the procedure for creating a cross-site network by using the Google Cloud CLI, do the following:

  1. Create a cross-site network
  2. Add a wire group to the cross-site network
  3. 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)
  4. 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)

You can create additional wire groups in the cross-site network depending on your use case:

  • To add more bandwidth between site A and site B, repeat the steps for creating a wire group and adding endpoints and connections.

  • To connect additional sites, repeat the steps for each pair of sites that you want to connect. For example, you can create an additional wire group that connects site A to site C, and another that connects site B to site C.

You can also add more wire groups later.

1. Create a cross-site network

To create a cross-site network, use the gcloud beta compute interconnects cross-site-networks create command.

  gcloud beta compute interconnects cross-site-networks create CROSS_SITE_NETWORK_NAME \
      [--description=DESCRIPTION]

Replace the following values:

  • CROSS_SITE_NETWORK_NAME: the name of the cross-site network
  • DESCRIPTION: an optional description for the cross-site network

2. 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 values:

  • 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.

3a. 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 values:

  • 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

3b. 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 values:

  • 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. One VLAN tag is used for the wire between connections A1 and B1 (wire A1-B1), and the other 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.

3c. 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 values:

  • 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 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 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. One VLAN tag is used for the wire between connections A2 and B2 (wire A2-B2), and the other 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.

4a. 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 values:

  • 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

4b. Add connection B1

To add a Cross-Site Interconnect connection to the wire group for site B, or Interconnect 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 values:

  • 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 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 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.

4c. 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 Interconnect 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 values:

  • 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 add the wire group to.
  • 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 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 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.
Previous
Test connections
Next
Configure on-premises routers