Activate connections

After Oracle Cloud Infrastructure (OCI) configures your VLAN attachment for a Partner Cross-Cloud Interconnect for OCI connection, you must activate it before the attachment can start passing traffic. Activating a VLAN attachment lets you check that you're connecting successfully with OCI before the attachment starts passing traffic. It also lets you control when the attachment starts passing traffic.

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

For definitions of terms used on this page, see Cloud Interconnect key terms.

To help you solve common issues that you might encounter when using Partner Cross-Cloud Interconnect for Oracle Cloud Infrastructure (OCI), see Troubleshooting.

To activate your VLAN attachment, follow these steps.

Console

In the Google Cloud console, go to the VLAN attachments tab.

Go to VLAN attachments
Select the VLAN attachment to view its details page.
If the status of your attachment is Waiting for service provider, make sure that you have created a FastConnect virtual circuit using the attachments pairing key.

Note: If you have created a valid virtual circuit and the attachment status continues in the PENDING_PARTNER or Waiting for service provider state, open a support ticket with OCI.
Review the Interconnect information to check that OCI has configured the VLAN attachment.

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

Note: The VLAN ID for the connection is for the Google Cloud side of the connection.
Click Activate.

gcloud

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 ATTACHMENT_NAME \
    --region=REGION

Replace the following:

ATTACHMENT_NAME: the name of your VLAN attachment
REGION: the region that your VLAN attachment is located in

The output is similar to the following for IPv4 VLAN attachments:

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: ATTACHMENT_NAME
pairingKey: 7e51371e-72a3-40b5-b844-2e3efefaee59/REGION/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/REGION
router: https://www.googleapis.com/compute/v1/projects/customer-project/regions/REGION/routers/my-router
selfLink: https://www.googleapis.com/compute/v1/projects/customer-project/regions/REGION/interconnectAttachments/my-attachment
stackType: IPV4_ONLY
state: PENDING_CUSTOMER
type: PARTNER
vlanTag8021q: 1000

The output is similar to the following for IPv4 and IPv6 (dual stack) VLAN attachments:

adminEnabled: false
edgeAvailabilityDomain: AVAILABILITY_DOMAIN_1
bandwidth: BPS_1G
cloudRouterIpAddress: 169.254.67.201/29
cloudRouterIpv6Address: 2600:2d00:0:1::1/125
creationTimestamp: '2017-12-01T08:31:11.580-08:00'
customerRouterIpAddress: 169.254.67.202/29
customerRouterIpv6Address: 2600:2d00:0:1::2/125
description: Interconnect for Customer 1
id: '7193021941765913888'
interconnect: https://www.googleapis.com/compute/alpha/projects/partner-project/global/interconnects/lga-2
kind: compute#interconnectAttachment
labelFingerprint: 42WmSpB8rSM=
name: ATTACHMENT_NAME
partnerMetadata:
  interconnectName: New York (2)
  partnerName: Partner Inc
  portalUrl: https://partner-portal.com
region: https://www.googleapis.com/compute/alpha/projects/partner-project/regions/REGION
selfLink: https://www.googleapis.com/compute/alpha/projects/partner-project/regions/REGION/interconnectAttachments/customer-attachment
stackType: IPV4_IPV6
state: PENDING_CUSTOMER
type: PARTNER
vlanTag8021q: 1000

After OCI has 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 OCI has completed the VLAN configuration.

View the partnerMetadata field to check that it shows OCI.

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

Activate the attachment by using the --adminEnabled flag:

gcloud compute interconnects attachments partner update ATTACHMENT_NAME \
    --region=REGION \
    --admin-enabled

After activation, your VLAN attachment can start passing traffic. OCI supplies their autonomous system number (ASN) when configuring your VLAN attachment, and then Google automatically adds the ASN to the Border Gateway Protocol (BGP) session on your Cloud Router.

To configure Cloud Router, follow these steps.

Console

In the Google Cloud console, go to the VLAN attachments tab.

Go to VLAN attachments
Select the VLAN attachment that you activated to view its details page.
Click Configure BGP.
In the Peer ASN field, add the ASN of your on-premises router.
Click Save and continue.

gcloud

For each of the BGP peers associated with your VLAN attachments, describe the Cloud Router associated with your VLAN attachment, and then find the name of the automatically created BGP peer that's associated with your VLAN attachment.

Run the following command:

gcloud compute routers describe ROUTER_NAME \
    --region=REGION

Replace the following:

ROUTER_NAME: the name of your Cloud Router
REGION: the region in which your Cloud Router is located

The output is similar to the following for IPv4 VLAN attachments:

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/REGION/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/REGION
selfLink: https://www.googleapis.com/compute/v1/projects/customer-project/regions/REGION/routers/my-router

The output is similar to the following for IPv4 and IPv6 (dual stack) VLAN attachments:

bgp:
 advertiseMode: DEFAULT
 asn: 16550
bgpPeers:
- enableIpv4: true
 enableIpv6: false
 ipAddress: 169.254.67.201
 interfaceName: auto-ia-if-my-attachment-0098154607ecb20
 managementType: MANAGED_BY_ATTACHMENT
 name: auto-ia-bgp4-my-attachment-0098154607ecb20
 peerIpAddress: 169.254.67.202
- enableIpv4: false
 enableIpv6: true
 ipAddress: 2600:2d00:0:1::1
 interfaceName: auto-ia-if6-my-attachment-0098154607ecb20
 managementType: MANAGED_BY_ATTACHMENT
 name: auto-ia-bgp6-my-attachment-0098154607ecb20
 peerIpAddress: 2600:2d00:0:1::2
creationTimestamp: '2018-03-29T09:58:25.476-07:00'
description: ''
id: '466013140766729694'
interfaces:
- ipRange: 169.254.67.201/29
 linkedInterconnectAttachment: https://www.googleapis.com/compute/alpha/projects/customer-project/regions/REGION/interconnectAttachments/customer-attachment
 managementType: MANAGED_BY_ATTACHMENT
 name: auto-ia-if-customer-attach-0098154607ecb20
- ipRange: 2600:2d00:0:1::1/125
 linkedInterconnectAttachment: https://www.googleapis.com/compute/alpha/projects/customer-project/regions/REGION/interconnectAttachments/customer-attachment
 managementType: MANAGED_BY_ATTACHMENT
 name: auto-ia-if6-customer-attach-0098154607ecb20
kind: compute#router
name: customer-router
network: https://www.googleapis.com/compute/alpha/projects/customer-project/global/networks/default
region: https://www.googleapis.com/compute/alpha/projects/customer-project/regions/REGION
selfLink: https://www.googleapis.com/compute/alpha/projects/customer-project/regions/REGION/routers/customer-router

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

For the IPv4 BGP peer, run the following command:
```
gcloud compute routers update-bgp-peer ROUTER_NAME \
    --peer-name=IPV4_PEER_NAME \
    --peer-asn=ON_PREM_ASN \
    --region=REGION
```
Replace the following:
- IPV4_PEER_NAME: the name of the bgpPeers entry with enableIpv4: true from the output from the gcloud compute routers describe command
- ON_PREM_ASN: your on-premises router's ASN
For the IPv6 BGP peer, run the following command:
```
gcloud compute routers update-bgp-peer ROUTER_NAME \
    --peer-name=IPV6_PEER_NAME \
    --peer-asn=ON_PREM_ASN \
    --region=REGION
```
Replace IPV6_PEER_NAME with the name of the bgpPeers entry with enableIpv6: true from the output from the gcloud compute routers describe command.

Troubleshooting

For additional guidance, see Troubleshooting.

Request OCI connections