Activating Connections

After your service provider configures your VLAN attachment, you must activate it before the attachment can start passing traffic. Activating a VLAN attachment allows you to check that you're connecting with an expected service provider before the attachment starts passing traffic. It also enables you to control when the attachment starts passing traffic.

If you pre-activate your VLAN attachment, the attachment is automatically activated after it's configured.

Console

  1. Go to the VLAN attachments tab in the Google Cloud Platform Console.
    Go to VLAN attachments tab
  2. Select the VLAN attachment to view its details page.
  3. If the status of your attachment is Waiting for service provider, wait until your service provider has completed the VLAN configuration.
  4. Review the Interconnect information to check that the expected service provider configured the VLAN attachment.

  5. Click Activate to activate it.

gcloud

  1. Describe the VLAN attachment to view its details. The state of the attachment must be PENDING_CUSTOMER before you can activate it.

    gcloud compute interconnects attachments describe my-attachment \
      --region us-central1

    adminEnabled: false
    edgeAvailabilityDomain: AVAILABILITY_DOMAIN_1
    bandwidth: BPS_1G
    cloudRouterIpAddress: 169.254.67.201/29
    creationTimestamp: '2017-12-01T08:29:09.886-08:00'
    customerRouterIpAddress: 169.254.67.202/29
    id: '7976913826166357434'
    kind: compute#interconnectAttachment
    labelFingerprint: 42WmSpB8rSM=
    name: my-attachment
    pairingKey: 7e51371e-72a3-40b5-b844-2e3efefaee59/us-central1/2
    partnerMetadata:
      interconnectName: New York (2)
      partnerName: My Service Provider Inc
      portalUrl: https://service-provider-portal.com
    region: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1
    router: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1/routers/my-router
    selfLink: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1/interconnectAttachments/my-attachment
    state: PENDING_CUSTOMER
    type: PARTNER
    vlanTag8021q: 1000

    If your service provider configured your VLAN attachment, the state of your attachment changes from PENDING_PARTNER to PENDING_CUSTOMER. If the state is still PENDING_PARTNER, wait until your service provider has completed the VLAN configuration.

  2. View the partnerMetadata field to check that it shows your expected service provider.

    If an unexpected third party pairs with your VLAN attachment, delete the attachment and then create a new one, which generates a new pairing key. Use the new pairing key to request another connection from your service provider.

  3. Activate the attachment by using the --adminEnabled flag.

    gcloud compute interconnects attachments partner update my-attachment \
    --region us-central1 \
    --admin-enabled

After activation, your VLAN attachment can start passing traffic. For layer 3 connections, you don't need to do any additional configuration. Your service provider supplies their ASN when configuring your VLAN attachment, and then Google automatically adds the ASN to the BGP session on your Cloud Router.

For layer 2 connections, you must add the ASN of your on-premises router to your Cloud Router.

To configure Cloud Router:

Console

  1. Go to the VLAN attachments tab in the Google Cloud Platform Console.
    Go to VLAN attachments tab
  2. Select the VLAN attachment that you activated to view its detail page.
  3. Click Configure BGP.
  4. In the Peer ASN field, add the ASN of your on-premises router.
  5. Click Save and continue.

gcloud

  1. Describe the Cloud Router that's associated with your VLAN attachment, and then find the name of the automatically created BGP peer that's associated with your VLAN attachment. The values of ipAddress and peerIpAddress of the BGP peer must match the values of cloudRouterIpAddress and customerRouterIpAddress of your attachment.

    gcloud compute routers describe my-router \
      --region us-central1

    bgp:
      advertiseMode: DEFAULT
      asn: 16550
    bgpPeers:
    - interfaceName: auto-ia-if-my-attachment-c2c53a710bd6c2e
      ipAddress: 169.254.67.201
      managementType: MANAGED_BY_ATTACHMENT
      name: auto-ia-bgp-my-attachment-c2c53a710bd6c2e
      peerIpAddress: 169.254.67.202
    creationTimestamp: '2018-01-25T07:14:43.068-08:00'
    description: 'test'
    id: '4370996577373014668'
    interfaces:
    - ipRange: 169.254.67.201/29
      linkedInterconnectAttachment: https://www.googleapis.com/compute/alpha/projects/customer-project/regions/us-central1/interconnectAttachments/my-attachment-partner
      managementType: MANAGED_BY_ATTACHMENT
      name: auto-ia-if-my-attachment-c2c53a710bd6c2e
    kind: compute#router
    name: partner
    network: https://www.googleapis.com/compute/v1/projects/customer-project/global/networks/default
    region: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1
    selfLink: https://www.googleapis.com/compute/v1/projects/customer-project/regions/us-central1/routers/my-router

  2. Update the BGP peer with your on-premises router's ASN.

    gcloud compute routers update-bgp-peer my-router \
      --peer-name auto-ia-bgp-my-attachment-c2c53a710bd6c2e \
      --peer-asn [ON-PREM ASN] \
      --region us-central1

What's next?

For layer 2 connections, configure a BGP session from your on-premises router to Cloud Router. For more information, see Configuring On-premises Routers.

Var denne side nyttig? Giv os en anmeldelse af den:

Send feedback om...