Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Setelah membuat lampiran VLAN untuk koneksi Partner Interconnect,
Anda dapat meminta koneksi dari
penyedia layanan yang didukung dengan
pengguna yang sudah memiliki konektivitas. Penyedia layanan harus mengonfigurasi
lampiran VLAN Anda sebelum lampiran dapat mulai meneruskan traffic. Untuk meminta
koneksi Partner Interconnect, hubungi penyedia layanan atau hubungi portal
mereka.
Untuk membantu memecahkan masalah umum yang mungkin Anda alami saat menggunakan
Partner Interconnect, lihat
Pemecah masalah.
Saat Anda meminta koneksi, penyedia layanan Anda memerlukan informasi
berikut:
Kunci penyambungan lampiran VLAN Anda.
Kunci penyambungan ini dibuat saat Anda membuat lampiran VLAN.
Region lampiran VLAN. Region yang
Anda pilih harus didukung oleh lokasi Partner Interconnect,
yang merupakan kota tempat jaringan penyedia layanan bertemu dengan jaringan
Google Cloud. Traffic antara jaringan Virtual Private Cloud (VPC) Anda dan jaringan
penyedia layanan akan melewati lokasi ini. Biasanya, Anda akan
memilih lokasi yang dekat dengan pusat data Anda untuk mengurangi latensi terhadap
workload Google Cloud .
Setiap lokasi penyedia layanan hanya mendukung beberapa region. Hubungi penyedia layanan
Anda untuk menentukan region mana yang didukung oleh setiap lokasi.
Kapasitas koneksi lampiran VLAN Anda. Kapasitas ini dapat berkisar dari
50 Mbps hingga 50 Gbps. Kapasitas bergantung pada persyaratan bandwidth dan
apa yang ditawarkan oleh penyedia layanan Anda. Selain itu,
harga untuk setiap lampiran VLAN
didasarkan pada kapasitasnya.
Setelah Anda meminta koneksi, tunggu hingga penyedia layanan menyelesaikan
konfigurasi lampiran VLAN. Setelah konfigurasi selesai, Anda
akan menerima notifikasi email dari Google. Status lampiran Anda berubah
dari PENDING_PARTNER menjadi PENDING_CUSTOMER. Jika Anda
mengaktifkan terlebih dahulu, lampiran akan berubah menjadi ACTIVE.
Jika Anda telah mengaktifkan lebih dulu lampiran VLAN sebelumnya dan menggunakan koneksi Lapisan 3,
lampiran dapat langsung mulai meneruskan traffic. Jika tidak, Anda harus mengaktifkan
lampiran sebelum dapat meneruskan traffic.
Saat penyedia layanan Anda menyelesaikan konfigurasi lampiran VLAN, Google
secara otomatis mengonfigurasi antarmuka dan sesi peering BGP di
Cloud Router yang terkait. Jangan mengubah konfigurasi yang ditentukan
Google ini karena akan menonaktifkan sesi BGP. Namun, jika lampiran dihapus
Anda dapat menghapus konfigurasi ini.
Untuk koneksi Lapisan 3, penyedia layanan menyediakan ASN mereka, yang
otomatis ditambahkan ke sesi BGP Cloud Router Anda dan memungkinkan BGP
untuk membuat sesi.
[[["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,["# Request connections\n\nAfter you create VLAN attachments for a Partner Interconnect connection,\nyou can request connections from a\n[supported service provider](/network-connectivity/docs/interconnect/concepts/service-providers) with\nwhom you already have connectivity. The service provider must configure your\nVLAN attachments before the attachments can start passing traffic. To request\na Partner Interconnect connection, contact your service provider or visit their\nportal.\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 Interconnect, see\n[Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting#partner).\n\nWhen you request a connection, your service provider 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 Interconnect\n location](/network-connectivity/docs/interconnect/concepts/partner-overview#provisioning),\n which is a city where the service provider's network meets Google Cloud's\n network. Traffic between your Virtual Private Cloud (VPC) network and the\n service provider's network passes through this location. Typically, you would\n choose a location that's close to your data center to reduce the latency to\n your Google Cloud workloads.\n\n Each service provider location supports only some regions. Check with your\n service provider to determine which regions each location supports.\n- **Your VLAN attachment's connection capacity.** This capacity can range from\n 50 Mbps to 50 Gbps. The capacity depends on your bandwidth requirements and\n what's offered by your service provider. Also,\n [pricing](/network-connectivity/docs/interconnect/pricing#partner-pricing) for each VLAN attachment is\n based on its capacity.\n\nAfter you request a connection, wait until the service provider completes the\nVLAN attachment configuration. After their 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 encrypted VLAN attachment remains in the `PENDING_PARTNER` or `Waiting for service provider` state for an extended period of time, contact your service provider for assistance.\n\nIf you pre-activated your VLAN attachment and are using a Layer 3 connection,\nthe attachment can immediately start passing traffic. If not, you must activate\nthe attachment before it can pass traffic.\n\nWhen your service provider completes the VLAN attachment configuration, Google\nautomatically configures an interface and a BGP peering session on the\nassociated Cloud Router. Do not modify these Google-defined\nconfigurations because doing so shuts down the BGP session. However, if you delete\nyour attachment, you can delete these configurations.\n\nFor Layer 3 connections, the service provider supplies their ASN, which is\nautomatically added to your Cloud Router's BGP session and allows BGP\nto establish a session."]]
