[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-08-12 UTC。"],[],[],null,["# Request connections\n\nAfter you configure your Google Cloud resources, configure your\nOracle Cloud Infrastructure (OCI) resources.\nThis page provides instructions about how to configure OCI\nresources to connect with Google Cloud.\n\nAfter you create VLAN attachments for a Partner Cross-Cloud Interconnect for OCI connection,\nconfigure your OCI resources by creating an\nOCI FastConnect virtual circuit to establish connectivity\ninto your OCI virtual cloud network (VCN).\n\nOCI configures your VLAN attachments after the virtual circuit\nis created. To request a Partner Cross-Cloud Interconnect for OCI connection, contact\nOracle or visit their portal.\n\nFor definitions of terms used on this page, see\n[Cloud Interconnect key terms](/network-connectivity/docs/interconnect/concepts/terminology).\n\nTo help you solve common issues that you might encounter when using\nPartner Cross-Cloud Interconnect for Oracle Cloud Infrastructure (OCI), see\n[Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting#partner).\n\nWhen you request a connection, OCI requires the following\ninformation:\n\n- **Your VLAN attachment's [pairing key](/network-connectivity/docs/interconnect/concepts/terminology#pairingkey)**:\n this pairing key is generated when you create the VLAN attachment.\n\n- **The VLAN attachment's [region](/compute/docs/regions-zones)** : the region\n that you select must be supported by a [Partner Cross-Cloud Interconnect for OCI\n location](/network-connectivity/docs/interconnect/concepts/partner-overview#provisioning),\n which is a city where OCI's network meets Google Cloud's\n network. Traffic between your Virtual Private Cloud (VPC) network and the\n OCI's network passes through this location. You must\n [choose an OCI location that's paired with the Google Cloud location](/network-connectivity/docs/interconnect/how-to/partner-cci-for-oci/paired-locations).\n\n- **Your VLAN attachment's connection capacity** : this capacity can range from\n 1 Gbps to 50 Gbps. The capacity depends on your bandwidth requirements and\n what's offered by OCI. [Pricing](/network-connectivity/docs/interconnect/pricing#partner-pricing) for\n each VLAN attachment is based on its capacity.\n\nAfter you request a connection and the OCI\nVLAN attachment configuration is complete, you\nreceive an email notification from Google. The state of your attachment changes\nfrom `PENDING_PARTNER` to `PENDING_CUSTOMER`. If you\n[pre-activated](/network-connectivity/docs/interconnect/concepts/partner-overview#pre-activate) your\nattachment, it changes to `ACTIVE`.\n| **Note:** If your VLAN attachment remains in the `PENDING_PARTNER` or `Waiting for service provider` state for an extended period of time, contact OCI assistance.\n\nIf you pre-activated your VLAN attachment,\nthe attachment can immediately start passing traffic. If not, you must activate\nthe attachment before it can pass traffic.\n\nConfigure OCI resources\n-----------------------\n\nOCI resources must be created in the OCI location paired with the\nGoogle Cloud location. For a list of paired locations, see\n[Paired locations](/network-connectivity/docs/interconnect/how-to/partner-cci-for-oci/paired-locations).\n| **Note:** For the most up-to-date information about how to configure OCI resources, see [Access to Google Cloud Platform](https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/access-to-google-cloud-platform.htm#unique_1638782181) in the OCI documentation.\n\nCreate a VCN\n------------\n\nCreate a virtual cloud network (VCN) that's in the same region and\ntenancy as your FastConnect ports. \n\n### OCI console\n\n| **Note:** For the most up-to-date information about how to create a VCN, see [Creating a VCN](https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/create_vcn.htm) in the OCI documentation.\n\n1. Sign in to the OCI console.\n2. Make sure that the **Regions** list shows the region where your FastConnect port is located.\n3. In the menumenu, select **Networking \\\u003e Virtual cloud networks**.\n4. Click **Create VCN**.\n5. Fill in the required fields, and then define at least one IPv4 CIDR block.\n6. Click **Create VCN**.\n\nCreate a subnet\n---------------\n\nIn your VCN, create a subnet. \n\n### OCI console\n\n| **Note:** For the most up-to-date information about how to create a subnet, see [Creating a VCN](https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/create_vcn.htm) in the OCI documentation.\n\n1. In the OCI console, go to the VCN that you just created.\n2. Click **Add subnet**.\n3. Fill in the required fields, and then define at least one IPv4 CIDR block.\n4. Click **Create Subnet**.\n\nCreate a DRG and attach it to your VCN\n--------------------------------------\n\nA Dynamic Routing Gateway (DRG) is a virtual router. Create a\nDRG and attach it to your VCN. \n\n### OCI console\n\n| **Note:** For the most up-to-date information about how to create a DRG, see [Creating a DRG](https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/drg-create.htm) in the OCI documentation.\n\n1. In the OCI console, on the menumenu, select **Networking**.\n2. In the **Customer connectivity** section, select **Dynamic routing\n gateway**.\n\n3. Click **Create Dynamic Routing Gateway**.\n\n4. Enter a name.\n\n5. Click **Create Dynamic Routing Gateway**. OCI displays a\n page that represents the DRG; you might have to wait a\n few minutes for the system to provision the resource.\n While it does so, the controls on the page are disabled.\n When the controls become active, continue to the next step.\n\n6. Click **Create Virtual Cloud Network Attachment**.\n\n7. Enter an attachment name.\n\n8. Select the **VCN network** that you created previously.\n\n | **Note:** Don't change any of the values listed in the **Advanced options** section.\n9. Click **Create Virtual Cloud Network Attachment**.\n\nCreate a private virtual circuit\n--------------------------------\n\nCreate a private virtual circuit for each FastConnect resource. If you created a pair of VLAN attachments, complete the following steps for each one. \n\n### OCI console\n\n1. Choose a compartment. If you're not sure which one, choose the compartment that contains the DRG to connect to. This compartment, along with a corresponding IAM policy, controls who can access the virtual circuit.\n2. On the main menu, click **Networking**.\n3. In the **Customer connectivity** section, click **FastConnect**.\n4. Click **Create Connection**.\n5. In the **Connection types** section, select **FastConnect partner** , and then choose **Google Cloud: OCI Interconnect**.\n6. In the **Name** field, enter a name for the circuit. The value doesn't need to be unique across your virtual circuits, and you can change it later.\n7. Leave the **Create in compartment** list as it is (the compartment you're in).\n8. For **Virtual circuit type** , select **Private virtual circuit**.\n9. In the **Dynamic routing gateway** list, the DRG you set up earlier is shown. If not, change the compartment to the one that stores the DRG, and then select the DRG.\n10. In the **Provisioned bandwidth** list, select the capacity that you chose for your VLAN attachment (or the closest value available).\n11. In the **Partner service key** field, enter the pairing key you received from Google Cloud when you created the VLAN attachment.\n12. In the **MTU** field, enter `1500` as the MTU value.\n13. Click **Continue**. The virtual circuit is provisioned.\n14. Click **Close**.\n\nAfter the virtual circuit is provisioned, the connection to Google Cloud\nis active. Then you can activate any VLAN attachments that you didn't\npre-activate when you created them. Check the status of provisioning virtual\ncircuits in FastConnect.\n\nAfter the OCI virtual circuit is created, Google\nautomatically configures an interface and a BGP peering session on the\nassociated Cloud Router. Don't modify these Google-defined\nconfigurations because doing so shuts down the BGP session. However, if you delete\nyour attachment, you can delete these configurations."]]
