Stay organized with collectionsSave and categorize content based on your preferences.
After you order your Cross-Cloud Interconnect connections, order
your Oracle Cloud Infrastructure (OCI) ports.
Before you begin
Make sure that you have sufficient quota to order the FastConnect resources
that you need.
Order FastConnect ports
For each of your Cross-Cloud Interconnect connections, you need
an OCI port.
Console
Sign in to the OCI console.
Make sure that theRegionslist shows the region where you
want to purchase OCI ports.
In themenumenu, selectNetworking. UnderCustomer connectivity, selectFastConnect.
ClickCreate FastConnect.
On theConnection typepage, select theFastConnect directbox,
and then clickNext.
Fill out theConfigurationpage:
Enter a name for the connection.
Select aCompartment.
UnderCross-connect type, select theCross-connect groupbox.
It's important to make this choice even if you do not plan to use LACP.
After you do, the page updates to include additional fields.
Enter theNumber of cross-connectsto use for the connection.
Choose the same number of links that you specified when ordering your
Cross-Cloud Interconnect ports. For example, if you
ordered a connection of size 20 Gb/s (2 x 10 Gb/s), enter2in this field. If you ordered a 100-Gb/s connection, set this field
to1.
Enter aPort speed. Use the same capacity that you selected
when ordering your Cross-Cloud Interconnect
connections. Valid options are10 Gbpsand100 Gbps. The OCI
console might list other options, but they can't be used with
Cross-Cloud Interconnect.
Leave theEnable MACsec encryptionfield cleared.
Cloud Interconnect doesn't support MACsec.
Select aPhysical location.
Specify whether to use the same OCI router as other
FastConnect connections by checking theSpecify router proximitybox. This step is important when you order the redundant port. Make
sure to place the redundant port on a different router than the
primary port. If both ports are placed on the same router, you would
lose both connections during maintenance work on the router.
Then fill in the related fields that are displayed.
Optional: Use theTag namespace,Tag key, andTag valuefields to create tags that represent the resource.
ClickCreate.
Generate LOAs
For Google to provision your connection, it must have a letter of authorization
(LOA) for each of your OCI ports.
Use the following procedure for each link that you created. In the
OCI interface, links are known ascross-connects.
For example, suppose you ordered two FastConnect connections, each of which
has two links. In this case, you need four LOA documents.
Console
Sign in to the OCI console.
Make sure that theRegionslist shows the region where you
purchased your FastConnect resources.
In themenumenu, selectNetworking. In theCustomer connectivitysection,
selectFastConnect.
Click the name of the appropriate connection.
In theCross-connectssection, click the name of the appropriate
link.
On theCross-connectstab, locate theLetter of Authorizationfield. Click the correspondingViewlink.
ClickPrintand follow prompts to print the LOA to a PDF to save it
locally.
Send the LOAs to Google
After you order your Cross-Cloud Interconnect connections, you
should receive confirmation email messages from Google. Each of these
messages includes instructions for sending your OCI LOAs to Google. Now that
you have the LOAs, do the following:
Decide which OCI port should be connected to each
Cross-Cloud Interconnect connection.
Locate the LOA documents for that port. The number of relevant LOAs
depends on the number of links that you specified for each port.
For example, if the port has two links
(or cross-connects), then you have two LOAs.
Respond to each of the Google emails, and attach the appropriate LOA
documents.
Make a note of the instructions that you provide to Google regarding which
Cross-Cloud Interconnect port connects to which OCI port. You need this
information later in the process when you configure your OCI resources.
After you respond to both emails, Google sends you an email acknowledging
receipt of the LOAs.
Still later, after Google provisions your
Cross-Cloud Interconnect connections, you receive another set of
emails stating that the work is complete. At that point, the
Cross-Cloud Interconnect ports are active, although the OCI
ports are not.
When you receive this confirmation, you can finish the required
configuration.
Check the status of your Google Cloud ports
Console
In the Google Cloud console, go to the Cloud InterconnectPhysical connectionstab.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Order OCI ports\n\nAfter you order your Cross-Cloud Interconnect connections, order\nyour Oracle Cloud Infrastructure (OCI) ports.\n\nBefore you begin\n----------------\n\nMake sure that you have sufficient quota to order the FastConnect resources\nthat you need.\n\nOrder FastConnect ports\n-----------------------\n\nFor each of your Cross-Cloud Interconnect connections, you need\nan OCI port.\n**Caution:** Use the following procedure twice---once to create the primary port and again to create the redundant port. \n\n### Console\n\n| **Note:** For the most up-to-date information about how to order a FastConnect port, see [FastConnect: Colocation with Oracle](https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/fastconnectcolocate.htm) in the OCI documentation.\n\n1. Sign in to the OCI console.\n\n2. Make sure that the **Regions** list shows the region where you\n want to purchase OCI ports.\n\n3. In the menu menu, select\n **Networking** . Under **Customer connectivity** , select **FastConnect**.\n\n4. Click **Create FastConnect**.\n\n5. On the **Connection type** page, select the **FastConnect direct** box,\n and then click **Next**.\n\n6. Fill out the **Configuration** page:\n\n 1. Enter a name for the connection.\n 2. Select a **Compartment**.\n 3. Under **Cross-connect type** , select the **Cross-connect group** box. It's important to make this choice even if you do not plan to use LACP. After you do, the page updates to include additional fields.\n 4. Enter the **Number of cross-connects** to use for the connection.\n Choose the same number of links that you specified when ordering your\n Cross-Cloud Interconnect ports. For example, if you\n ordered a connection of size 20 Gb/s (2 x 10 Gb/s), enter **2**\n in this field. If you ordered a 100-Gb/s connection, set this field\n to **1**.\n\n | **Note:** Set this field to reflect the number of links in this cross-connect group. *Setting the number of cross-connects to 2 does not\n | set up redundancy*. To set up redundancy, order two cross-connect groups by following the cross-connect group ordering process twice.\n 5. Enter a **Port speed** . Use the same capacity that you selected\n when ordering your Cross-Cloud Interconnect\n connections. Valid options are **10 Gbps** and **100 Gbps**. The OCI\n console might list other options, but they can't be used with\n Cross-Cloud Interconnect.\n\n 6. Leave the **Enable MACsec encryption** field cleared.\n Cloud Interconnect doesn't support MACsec.\n\n 7. Select a **Physical location**.\n\n 8. Specify whether to use the same OCI router as other\n FastConnect connections by checking the **Specify router proximity**\n box. This step is important when you order the redundant port. Make\n sure to place the redundant port on a different router than the\n primary port. If both ports are placed on the same router, you would\n lose both connections during maintenance work on the router.\n Then fill in the related fields that are displayed.\n\n 9. Optional: Use the **Tag namespace** , **Tag key** , and **Tag value**\n fields to create tags that represent the resource.\n\n7. Click **Create**.\n\nGenerate LOAs\n-------------\n\nFor Google to provision your connection, it must have a letter of authorization\n(LOA) for each of your OCI ports.\n\nUse the following procedure for each link that you created. In the\nOCI interface, links are known as *cross-connects*.\n\nFor example, suppose you ordered two FastConnect connections, each of which\nhas two links. In this case, you need four LOA documents. \n\n### Console\n\n1. Sign in to the OCI console.\n\n2. Make sure that the **Regions** list shows the region where you\n purchased your FastConnect resources.\n\n3. In the menu menu, select\n **Networking** . In the **Customer connectivity** section,\n select **FastConnect**.\n\n4. Click the name of the appropriate connection.\n\n5. In the **Cross-connects** section, click the name of the appropriate\n link.\n\n6. On the **Cross-connects** tab, locate the **Letter of Authorization**\n field. Click the corresponding **View** link.\n\n7. Click **Print** and follow prompts to print the LOA to a PDF to save it\n locally.\n\nSend the LOAs to Google\n-----------------------\n\nAfter you order your Cross-Cloud Interconnect connections, you\nshould receive confirmation email messages from Google. Each of these\nmessages includes instructions for sending your OCI LOAs to Google. Now that\nyou have the LOAs, do the following:\n\n1. Decide which OCI port should be connected to each\n Cross-Cloud Interconnect connection.\n\n2. Locate the LOA documents for that port. The number of relevant LOAs\n depends on the number of links that you specified for each port.\n For example, if the port has two links\n (or cross-connects), then you have two LOAs.\n\n3. Respond to each of the Google emails, and attach the appropriate LOA\n documents.\n\nMake a note of the instructions that you provide to Google regarding which\nCross-Cloud Interconnect port connects to which OCI port. You need this\ninformation later in the process when you configure your OCI resources.\n\nAfter you respond to both emails, Google sends you an email acknowledging\nreceipt of the LOAs.\n\nStill later, after Google provisions your\nCross-Cloud Interconnect connections, you receive another set of\nemails stating that the work is complete. At that point, the\nCross-Cloud Interconnect ports are active, although the OCI\nports are not.\n\nWhen you receive this confirmation, you can finish the required\nconfiguration.\n\nCheck the status of your Google Cloud ports\n-------------------------------------------\n\n### Console\n\n1. In the Google Cloud console, go to the Cloud Interconnect\n **Physical connections** tab.\n\n [Go to Physical connections](https://console.cloud.google.com/hybrid/interconnects/list?tab=interconnects)\n2. Click the name of your Cross-Cloud Interconnect\n connection.\n\n3. On the **Interconnect details** page, locate the\n **Link circuit info** table.\n\n4. Check the **Receiving Optical Power** and the\n **Transmitting Optical Power** columns. The value in these columns\n should be **OK**.\n\nAt this point, it is normal to see a red checkmark in the **Link State**\ncolumn.\n\nVerify and enable OCI ports\n---------------------------\n\nCheck to see whether your OCI links are all receiving a signal from Google. If\nthey are, enable them. \n\n### Console\n\nFor each of your links, complete the following steps:\n\n1. Sign in to the OCI console.\n\n2. Make sure that the **Regions** list shows the region where you\n want to purchase OCI ports.\n\n3. In the menu menu, select\n **Networking** . In the **Customer connectivity** section,\n select **FastConnect**.\n\n4. Click the name of the appropriate FastConnect resource.\n\n5. Under **Cross-connects**, click the name of the link that you want\n to verify.\n\n6. In the **Cross-Connection Information** box, locate the\n **Light Level Indicator**. Verify that a\n green checkmark appears next to the field.\n\n7. If all of the fields appear as expected, click **Activate**.\n\n8. In the **Confirmation** dialog, click **Activate**.\n\n9. To verify the activation, go back to the previous page and review\n the **Cross-connects** table. The value in the **Life Cycle** column\n should be **Provisioning**."]]
