Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Pengurutan koneksi Cross-Site Interconnect akan memulai
proses
pembuatan koneksi Cross-Site Interconnect Anda. Saat memesan koneksi Cross-Site Interconnect,
Anda menentukan detail seperti kapasitas dan lokasi koneksi Anda.
Untuk membantu memecahkan masalah umum yang mungkin Anda alami saat menggunakan
Cross-Site Interconnect, lihat
Pemecahan masalah.
Anda dapat meminta kapasitas berikut:
1 x sirkuit 10-Gbps (10 Gbps)
1 x sirkuit 100-Gbps (100 Gbps)
Izin yang diperlukan untuk langkah ini
Untuk melakukan tugas ini, Anda harus sudah diberi izin berikut
atau peran Identity and Access Management (IAM) berikut.
Izin
compute.interconnects.create
Peran
(roles/owner) Pemilik
(roles/editor) Editor
Admin Jaringan Compute (roles/compute.networkAdmin)
Konsol
Di konsol Google Cloud , buka halaman Interconnect.
Pilih Koneksi Cross-Site Interconnect, lalu klik Lanjutkan.
Jika belum melakukannya, periksa kuota dan batas bandwidth Anda untuk memastikan bahwa Anda dapat berhasil membuat jaringan lintas situs dengan bandwidth yang diperlukan.
Setelah Anda mengonfirmasi bahwa Anda memiliki kuota yang cukup, klik
Berikutnya: Saya mengerti.
Tentukan detail koneksi Cross-Site Interconnect:
Nama: Nama untuk koneksi. Nama ini ditampilkan
di konsol Google Cloud dan digunakan oleh Google Cloud CLI untuk
mereferensikan koneksi, seperti my-interconnect.
Fasilitas kolokasi: Lokasi fisik tempat koneksi dibuat. Jaringan lokal Anda
harus memenuhi jaringan Google Clouddi lokasi ini.
Kapasitas: Total kapasitas koneksi Anda,
yang ditentukan oleh jumlah dan ukuran sirkuit yang Anda
pesan.
Pilih salah satu opsi berikut:
1 x sirkuit 10 Gbps
1 x sirkuit 100 Gbps
Klik Berikutnya.
Jika Anda berencana membuat jaringan lintas situs dengan topologi box-and-cross atau redundan, tentukan detail untuk koneksi duplikat
Anda, lalu klik Next.
Tentukan informasi kontak Anda:
Nama perusahaan: Nama organisasi Anda yang akan dimasukkan ke
LOA sebagai pihak yang diizinkan untuk meminta koneksi.
Kontak teknis: Alamat email yang digunakan untuk mengirimkan notifikasi
tentang koneksi ini. Anda tidak perlu memasukkan
alamat Anda sendiri; Anda disertakan dalam semua pemberitahuan. Anda hanya dapat
menentukan satu alamat.
Tinjau pesanan Anda. Periksa apakah detail koneksi dan
informasi kontak Anda sudah benar. Jika semuanya sudah benar, klik Pesan
. Jika tidak, kembali dan edit detail koneksi.
Di halaman konfirmasi pesanan, tinjau langkah berikutnya, lalu klik
Selesai.
Untuk memesan koneksi bagi situs kedua Anda, ulangi langkah-langkah di bagian ini.
gcloud
Buat koneksi Cross-Site Interconnect yang merupakan jenis koneksi DEDICATED dan menentukan fitur CROSS_SITE_NETWORK.
Jika Anda berencana menggunakan MACsec untuk Cloud Interconnect, sertakan MACSEC dalam daftar fitur yang diminta.
INTERCONNECT_NAME: nama untuk koneksi Cross-Site Interconnect;
nama ini ditampilkan di konsol Google Cloud dan
digunakan oleh Google Cloud CLI untuk mereferensikan koneksi, seperti
my-interconnect
NAME: nama organisasi Anda yang akan dimasukkan ke
LOA sebagai pihak yang diizinkan untuk meminta koneksi
LINK_TYPE:
Jika Anda ingin koneksi Cross-Site Interconnect terdiri dari sirkuit 10 Gbps, ganti LINK_TYPE dengan
LINK_TYPE_ETHERNET_10G_LR.
Jika Anda ingin koneksi terdiri dari sirkuit 100 Gbps, ganti LINK_TYPE dengan
LINK_TYPE_ETHERNET_100G_LR.
EMAIL_ADDRESS dan STRING:
opsional; untuk kontak NOC, Anda hanya dapat menentukan satu alamat
email—tidak perlu memasukkan alamat sendiri karena Anda
disertakan dalam semua notifikasi. Jika Anda membuat koneksi
melalui workforce identity federation,
penyediaan alamat email dengan
flag ‑‑noc-contact-email diperlukan.
Jika Anda berencana membuat jaringan lintas situs dengan topologi silang atau redundan, buat koneksi Cross-Site Interconnect duplikat yang berada di metro yang sama, tetapi di domain ketersediaan edge yang berbeda (zona ketersediaan metro).
REDUNDANT_INTERCONNECT_NAME: nama untuk koneksi Cross-Site Interconnect yang redundan
NAME: nama organisasi Anda yang akan dimasukkan ke
LOA sebagai pihak yang diizinkan untuk meminta koneksi
LINK_TYPE: kapasitas per sirkuit dari koneksi Cross-Site Interconnect; gunakan nilai yang sama dengan koneksi yang ada:
Jika koneksi yang ada terdiri dari sirkuit 10 Gbps, ganti LINK_TYPE dengan LINK_TYPE_ETHERNET_10G_LR.
Jika koneksi yang ada terdiri dari sirkuit 100 Gbps, ganti LINK_TYPE dengan LINK_TYPE_ETHERNET_100G_LR.
LOCATION_NAME: lokasi tempat koneksi Cross-Site Interconnect yang redundan dibuat
Dari daftar lokasi, pilih salah satu yang berada di metro yang sama, tetapi dalam domain ketersediaan edge yang berbeda dari koneksi yang ada.
Misalnya, jika koneksi yang ada berada di iad-zone2-1, pilih
lokasi yang berada di Ashburn tetapi di zona 1, seperti iad-zone1-1.
EMAIL_ADDRESS dan STRING:
opsional; untuk kontak NOC, Anda hanya dapat menentukan satu alamat
email—tidak perlu memasukkan alamat sendiri karena Anda
disertakan dalam semua pemberitahuan
Untuk memesan koneksi bagi situs kedua Anda, ulangi langkah-langkah di bagian ini.
Setelah Anda memesan koneksi Cross-Site Interconnect, Google akan mengirimkan email konfirmasi kepada Anda
dan mengalokasikan port untuk Anda. Setelah alokasi selesai, Google akan membuat
LOA-CFA untuk koneksi Anda dan mengirimkannya melalui email.
Semua email otomatis dikirim ke kontak NOC dan alamat email
Akun Google yang digunakan saat memesan koneksi Cross-Site Interconnect. Anda juga
bisa mendapatkan LOA-CFA dengan menggunakan konsol Google Cloud .
Anda dapat menggunakan koneksi Cross-Site Interconnect hanya setelah koneksi Anda
disediakan dan diuji untuk tingkat cahaya dan konektivitas IP.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-12 UTC."],[],[],null,["# Order Cross-Site Interconnect connections\n\nOrdering Cross-Site Interconnect connections starts the creation\n[process](/network-connectivity/docs/interconnect/how-to/cross-site/provisioning-overview)\nof your Cross-Site Interconnect connections. When you order Cross-Site Interconnect connections,\nyou specify details such as the capacity and the locations of your connections.\n|\n| **Preview**\n|\n|\n| This product is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n| **Note:** For definitions of terms used on this page, see [Cloud Interconnect key terms](/network-connectivity/docs/interconnect/concepts/terminology).\n\nTo help you solve common issues that you might encounter when using\nCross-Site Interconnect, see\n[Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting).\n\nYou can request the following capacities:\n\n- 1 x 10-Gbps (10 Gbps) circuit\n- 1 x 100-Gbps (100 Gbps) circuit\n\n| **Caution:** The link type that you select when you create a Cross-Site Interconnect connection cannot be changed later. For example, if you select a 10-Gbps link type and need a 100-Gbps link type later, you must create a new Cross-Site Interconnect connection with the higher capacity.\n\n#### Permissions required for this task\n\nTo perform this task, you must have been granted the following permissions\n*or* the following Identity and Access Management (IAM) roles.\n\n**Permissions**\n\n- `compute.interconnects.create`\n\n**Roles**\n\n- Owner (`roles/owner`)\n- Editor (`roles/editor`)\n- Compute Network Admin (`roles/compute.networkAdmin`) \n\n### Console\n\n1. In the Google Cloud console, go to the **Interconnect** page.\n\n\n [Go to Interconnect](https://console.cloud.google.com/hybrid/interconnects/list)\n\n \u003cbr /\u003e\n\n2. Click add**Set up physical connection**.\n\n3. Select **Cross-Site Interconnect connection** , and then click **Continue**.\n\n4. If you haven't already, [check your bandwidth quotas and limits](/network-connectivity/docs/interconnect/how-to/cross-site/check-bandwidth-quota) to ensure that you can successfully\n create a cross-site network with your required bandwidth.\n\n After you have confirmed that you have sufficient quota, click\n **Next: I acknowledge**.\n5. Specify the details of the Cross-Site Interconnect connection:\n\n - **Name** : A name for the connection. This name is displayed in the Google Cloud console and is used by the Google Cloud CLI to reference the connection, such as `my-interconnect`.\n - **Colocation facility** : The physical [location](/network-connectivity/docs/interconnect/concepts/cross-site-locations) where the connection is created. Your on-premises network must meet Google Cloud's network in this location.\n - **Capacity**: The total capacity of your connection,\n which is determined by the number and size of the circuits that you\n order.\n\n Select *one* of the following options:\n - 1 x 10-Gbps circuit\n - 1 x 100-Gbps circuit\n6. Click **Next**.\n\n7. If you plan to create a cross-site network with a redundant or box-and-cross topology, specify details for your duplicate\n connection, and then click **Next**.\n\n8. Specify your contact information:\n\n - **Company name**: The name of your organization to put in the LOA as the party authorized to request a connection.\n - **Technical contact**: An email address where notifications\n about this connection are sent. You don't need to enter your own\n address; you are included in all notifications. You can\n specify only one address.\n\n If you are creating a connection\n through [workforce identity federation](/iam/docs/workforce-identity-federation),\n specifying a **Technical contact** is required.\n9. Review your order. Check that your connection details and\n contact information are correct. If everything is correct, click **Place\n order**. If not, go back and edit the connection details.\n\n10. On the order confirmation page, review the next steps, and then click\n **Done**.\n\n11. To order connections for your second site, repeat the steps in this\n section.\n\n### gcloud\n\n1. Create a Cross-Site Interconnect connection that is a connection type of `DEDICATED` and specifies the `CROSS_SITE_NETWORK` feature.\n If you plan to use [MACsec for Cloud Interconnect](/network-connectivity/docs/interconnect/concepts/macsec-overview), include `MACSEC` in the list of\n requested features.\n\n ```\n gcloud beta compute interconnects create INTERCONNECT_NAME \\\n --customer-name=NAME \\\n --interconnect-type=DEDICATED \\\n --requested-features=CROSS_SITE_NETWORK[,MACSEC] \\\n --link-type=LINK_TYPE \\\n --location=LOCATION_NAME \\\n [--noc-contact-email=EMAIL_ADDRESS] \\\n [--description=STRING]\n ```\n\n Replace the following values:\n - \u003cvar translate=\"no\"\u003eINTERCONNECT_NAME\u003c/var\u003e: a name for the Cross-Site Interconnect connection; this name is displayed in the Google Cloud console and is used by the Google Cloud CLI to reference the connection, such as `my-interconnect`\n - \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e: the name of your organization to put in the LOA as the party authorized to request a connection\n - \u003cvar translate=\"no\"\u003eLINK_TYPE\u003c/var\u003e:\n - If you want your Cross-Site Interconnect connection to be made up of a 10-Gbps circuit, replace \u003cvar translate=\"no\"\u003eLINK_TYPE\u003c/var\u003e with `LINK_TYPE_ETHERNET_10G_LR`.\n - If you want your connection to be made up of a 100-Gbps circuit, replace \u003cvar translate=\"no\"\u003eLINK_TYPE\u003c/var\u003e with `LINK_TYPE_ETHERNET_100G_LR`.\n - \u003cvar translate=\"no\"\u003eLOCATION_NAME\u003c/var\u003e: specifies the location where the Cross-Site Interconnect connection is created; to list the names of locations, see [List locations for Cross-Site Interconnect](/network-connectivity/docs/interconnect/how-to/cross-site/list-locations)\n - \u003cvar translate=\"no\"\u003eEMAIL_ADDRESS\u003c/var\u003e and \u003cvar translate=\"no\"\u003eSTRING\u003c/var\u003e: optional; for the NOC contact, you can specify only one email address---you don't need to enter your own address because you are included in all notifications. If you are creating a connection through [workforce identity federation](/iam/docs/workforce-identity-federation), providing an email address with the `‑‑noc-contact-email` flag is required.\n2. If you plan to create a cross-site network with a redundant or box-and-cross\n topology, create a duplicate Cross-Site Interconnect connection that is in the same [metro](/network-connectivity/docs/interconnect/concepts/cross-site-locations)\n but in a different edge availability domain (metro availability zone).\n\n ```\n gcloud beta compute interconnects create REDUNDANT_INTERCONNECT_NAME \\\n --customer-name=NAME \\\n --interconnect-type=DEDICATED \\\n --requested-features=CROSS_SITE_NETWORK[,MACSEC] \\\n --link-type=LINK_TYPE \\\n --location=LOCATION_NAME \\\n [--noc-contact-email=EMAIL_ADDRESS] \\\n [--description=STRING]\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eREDUNDANT_INTERCONNECT_NAME\u003c/var\u003e: a name for the redundant Cross-Site Interconnect connection\n - \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e: the name of your organization to put in the LOA as the party authorized to request a connection\n - \u003cvar translate=\"no\"\u003eLINK_TYPE\u003c/var\u003e: the per-circuit capacity of your Cross-Site Interconnect connection; use the same value as the existing connection:\n - If your existing connection is made up of 10-Gbps circuits, replace \u003cvar translate=\"no\"\u003eLINK_TYPE\u003c/var\u003e with `LINK_TYPE_ETHERNET_10G_LR`.\n - If your existing connection is made up of 100-Gbps circuits, replace \u003cvar translate=\"no\"\u003eLINK_TYPE\u003c/var\u003e with `LINK_TYPE_ETHERNET_100G_LR`.\n - \u003cvar translate=\"no\"\u003eLOCATION_NAME\u003c/var\u003e: the location where the redundant\n Cross-Site Interconnect connection is created\n\n From the list of [locations](/network-connectivity/docs/interconnect/concepts/cross-site-locations#locations-table),\n select one that's in the same metro but in a different edge availability\n domain from the existing connection.\n\n For example, if the existing connection is in `iad-zone2-1`, select a\n location that's in Ashburn but in zone 1, such as `iad-zone1-1`.\n - \u003cvar translate=\"no\"\u003eEMAIL_ADDRESS\u003c/var\u003e and \u003cvar translate=\"no\"\u003eSTRING\u003c/var\u003e:\n optional; for the NOC contact, you can specify only one email\n address---you don't need to enter your own address because you\n are included in all notifications\n\n3. To order connections for your second site, repeat the steps in this section.\n\nAfter you order a Cross-Site Interconnect connection, Google emails you a confirmation\nand allocates ports for you. When the allocation is complete, Google generates\nLOA-CFAs for your connections and emails them to you.\n\nAll the automated emails are sent to the NOC contact and the email address\nof the Google Account used when ordering the Cross-Site Interconnect connection. You can\nalso get your LOA-CFAs by using the Google Cloud console.\n\nYou can use the Cross-Site Interconnect connection only after your connections have been\nprovisioned and tested for light levels and IP connectivity.\n| **Note:** [Billing](/network-connectivity/docs/interconnect/pricing) for your Cross-Site Interconnect connection starts after it's ready to use (all [tests](/network-connectivity/docs/interconnect/how-to/cross-site/testing-connections) have passed) or 30 days after your order is received. You aren't charged before then. You can cancel your order by [deleting](/network-connectivity/docs/interconnect/how-to/cross-site/deleting-interconnects) the Cross-Site Interconnect connection."]]
