Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Router appliance adalah fitur Network Connectivity Center yang memungkinkan Anda menggunakan
appliance virtual jaringan pihak ketiga di Google Cloud. Saat Anda menggunakan pendekatan
ini, appliance dapat bertukar rute dengan Cloud Router dengan
menggunakan Border Gateway Protocol (BGP).
Dengan menggunakan Router appliance dan Network Connectivity Center, Anda dapat melakukan hal berikut:
Hubungkan beberapa jaringan VPC satu sama lain. Jaringan VPC
dapat ditempatkan di berbagai project dalam organisasi Google Cloud yang sama atau
organisasi yang berbeda.
Menghubungkan beberapa jaringan VPC ke jaringan lokal atau penyedia cloud
lainnya.
Jaringan eksternal ini dapat dijangkau melalui semua jenis spoke hybrid.
Pendekatan ini dikenal sebagai konektivitas site-to-cloud.
Gunakan VM Router appliance untuk mengelola konektivitas antar jaringan
VPC.
Gunakan jaringan VPC Google Cloud sebagai jaringan area luas (WAN)
perusahaan untuk menghubungkan jaringan yang berada di luar Google Cloud.
Anda dapat membuat konektivitas antar-situs eksternal menggunakan jenis spoke hybrid apa pun. Pendekatan ini dikenal sebagai konektivitas
site-to-site.
Cara kerjanya
Anda dapat mengonfigurasi instance router appliance dengan menginstal
image di VM Compute Engine. Anda dapat menggunakan image yang disediakan oleh
partner Network Connectivity Center yang didukung. Anda juga dapat menggunakan gambar kustom, seperti gambar yang telah Anda buat.
Setelah instance router appliance telah terpasang,
selanjutnya adalah mengonfigurasi antar muka pada
Cloud Router untuk melakukan peering Border Gateway Protocol (BGP) dengan instance router appliance. BGP memungkinkan pertukaran rute dinamis
antara Cloud Router dengan instance router appliance. Pertukaran
rute, pada saatnya, memberikan izin konektivitas dari situs melalui instance
router appliance ke jaringan VPC. Artinya, rute
yang diterapkan oleh instance router appliance dapat digunakan oleh VM dan resource
lain yang memiliki alamat IP dalam jaringan VPC yang sama.
Cloud Router menggunakan antarmuka yang dikonfigurasi dengan alamat IP internal
RFC 1918 untuk melakukan peering BGP dengan instance router appliance.
Tidak ada API atau resource atau izin Google Cloud terpisah untuk
Router appliance. Untuk menggunakan Router appliance, Anda harus menggunakan
Compute Engine, dan resource Cloud Router beserta izin.
Kasus penggunaan: Transfer data antar-lokasi lokal
Topologi berikut menunjukkan jaringan VPC dan dua lokasi
lokal. Setiap situs lokal terhubung ke Google Cloud dengan menggunakan
spoke Router appliance. Kedua lokasi lokal tersebut dapat menggunakan jaringan Google
untuk bertukar data satu sama lain.
Topologi router appliance (klik untuk memperbesar)
Customer network A dan Customer network B lokal masing-masing terhubung
melalui peralatan lokal pelanggan (CPE) ke instance router appliance.
CPE biasanya menggunakan mekanisme konektivitas, seperti tunnel overlay SD-WAN
atau tunnel VPN IPsec, untuk membuat konektivitas dengan
instance router appliance.
Setiap instance router yang ada di
wilayahGoogle Cloud yang paling dekat dengan jaringan pelanggan terkait miliknya. Kedua
instance router appliance berada dalam satu jaringan VPC.
Namun, instance router appliance berada di region yang berbeda. Karena alasan
ini, jaringan VPC menetapkan
mode pemilihan rute dinamis
menjadi global.
Kedua instance router appliance terpasang sebagai spoke ke
hub Network Connectivity Center. Karena Customer network A dan Customer network B
perlu saling mengirim data, kedua spoke kolom transfer data
site-to-site aktif.
Di masing-masing wilayah, instance router appliance melakukan peering
Border Gateway Protocol (BGP) dengan Cloud Router yang sesuai. Setiap
Cloud Router menerima dan memberitahukan imbuhan rute dari
lokasi lokal yang sesuai.
Cloud Router secara dinamis bertukar semua rute
yang diterima satu sama lain. Konfigurasi ini memberikan pertukaran rute dinamis
menyeluruh dan konektivitas bidang data antaraCustomer network A dengan
Customer network B.
Untuk langkah-langkah konfigurasi mendetail topologi lokasi tunggal dengan yang dilengkapi dengan load balance,
lihat
Membuat instance router appliance.
Persyaratan
Ikuti persyaratan ini saat men-deploy instance router appliance.
Konfigurasi BGP
Image router appliance yang Anda instal harus mendukung protokol routing
BGP.
Untuk mengaktifkan peering BGP antara instance router appliance dengan
Cloud Router, lampirkan setiap instance router
sebagai spoke ke hub Network Connectivity Center.
Buat Cloud Router di wilayah yang sama dengan
subnet
yang berisi antarmuka peering dari instance router appliance.
Buat antarmuka BGP secara manual pada instance router appliance. Antarmuka
ini harus berada dalam subnet yang sama dengan instance router appliance.
Buat sesi BGP dengan Cloud Router dari
instance router appliance secara manual.
Untuk VM yang sudah dikonfigurasi untuk beberapa antarmuka jaringan sebagai bagian dari
instance router appliance, Anda dapat membuat sesi BGP dengan
Cloud Routers yang sama dengan subnet antarmuka VM.
Untuk informasi lebih lanjut tentang antarmuka VM, lihat
Ringkasan dan contoh antarmuka beberapa jaringan.
Rekomendasi ketersediaan
Perjanjian tingkat layanan (SLA) standar untuk VM Compute Engine juga
berlaku pada ketersediaan instance router appliance. SLA
ketersediaannya adalah 99,5% untuk VM tunggal dan 99,99% untuk VM di beberapa
zona. Untuk informasi lebih lanjut, lihat SLA Compute Engine.
Untuk sepasang instance router appliance, masing-masing untuk lokasi
lokal yang berbeda, jalankan paling tidak dua VM di zona yang berbeda. Setiap VM harus
melakukan peering dengan sepasang antarmuka Cloud Router redundan.
Untuk informasi lebih lanjut tentang zona, lihat
Wilayah dan zona.
Pertimbangan
Sebelum menggunakan Router appliance, tinjau bagian berikut.
Pertimbangan umum
Router appliance memerlukan Network Connectivity Center agar dapat beroperasi. Artinya, Anda
tidak dapat mengonfigurasi router instance mandiri yang melakukan peering dengan
Cloud Router atau dengan peer router lainnya. Anda harus mengonfigurasi instance
router appliance sebagai bagian dari spoke Network Connectivity Center.
Peralatan router hanya didukung dalam model VPC Bersama saat di-deploy di project host. Instance peralatan router harus di-deploy
di project host dan semua resource terkait lainnya, seperti hub,
spoke, dan Cloud Router.
Peralatan router tidak mendukung VPC Bersama saat VM peralatan Router di-deploy di project layanan.
Pertimbangan pemilihan rute
Jika beberapa instance router appliance mengumumkan awalan pemilihan rute yang sama
dengan MED yang sama, Google Cloud akan menggunakan pemilihan rute equal-cost multipath (ECMP)
di seluruh instance router appliance.
Sebaiknya tidak memberitahukan imbuhan yang sama melalui campuran dari beberapa
jenis spoke (instance router appliance, gateway Cloud VPN,
dan lampiran VLAN) yang berbeda. Apabila imbuhan yang sama dapat dicapai melalui perpaduan
jenis spoke, menggunakan ECMP pada jenis spoke campuran dapat mengakibatkan terjadinya traffic
yang tidak seimbang pada setiap link.
Apabila Cloud Router tunggal mempelajari imbuhan dengan beberapa next hop,
Cloud Router memilih next hop yang memiliki panjang jalur AS paling pendek
terlebih dahulu, kemudian menggunakan MED untuk. tie break. Untuk informasi lebih lanjut, lihat
panjang jalur AS di
dokumentasi Cloud Router.
[[["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,["# Router appliance overview\n\nRouter appliance is a Network Connectivity Center feature that lets you use a\nthird-party network virtual appliance in Google Cloud. When you use this\napproach, the appliance can exchange routes with Cloud Router by\nusing Border Gateway Protocol (BGP).\n\nUsing Router appliance and Network Connectivity Center, you can do the following:\n\n- Connect multiple VPC networks to one another. The VPC networks can be located across different projects in the same Google Cloud organization or different organizations.\n- Connect multiple VPC networks to on-premise or other cloud provider networks. These external networks can be reachable through any type of hybrid spoke. This approach is known as *site-to-cloud connectivity.*\n- Use Router appliance VMs to manage connectivity between your VPC networks.\n- Use a Google Cloud VPC network as an enterprise wide area network (WAN) to connect networks that are outside of Google Cloud. You can establish connectivity between your external sites by using any type of hybrid spoke. This approach is known as *site-to-site\n connectivity*.\n\nHow it works\n------------\n\nYou can configure a router appliance instance by installing\nan image on a Compute Engine VM. You can use an image provided by a\n[supported Network Connectivity Center partner](/network-connectivity/docs/network-connectivity-center/partners). You can also use a custom image, such as an image that you\ncreated.\n\nAfter the router appliance instance is installed, you configure interfaces on\nthe Cloud Router to establish Border Gateway Protocol (BGP) peering\nwith the router appliance instance. BGP enables the dynamic exchange of routes\nbetween the Cloud Router and the router appliance instance. Route\nexchange, in turn, permits connectivity from the site through the router\nappliance instance to the VPC network. That is, the routes\npropagated by the router appliance instance can be used by VMs and other\nresources that have IP addresses in the same VPC network.\n\nCloud Router uses interfaces configured with RFC 1918 internal IP\naddresses to establish BGP peering with router appliance instances.\n\nThere are no separate APIs or Google Cloud resources or permissions for\nRouter appliance. To work with Router appliance, you use\nCompute Engine and Cloud Router resources and permissions.\n\nUse case: Data transfer between on-premises sites\n-------------------------------------------------\n\nThe following topology shows a VPC network and two on-premises\nsites. Each on-premises site connects to Google Cloud by using a\nRouter appliance spoke. The two on-premises sites can use Google's network\nto exchange data with each other.\n[](/static/network-connectivity/docs/network-connectivity-center/images/router-appliance-topology.svg) Router appliance topology (click to enlarge)\n\n1. On-premises `Customer network A` and `Customer network B` are each connected\n through *customer premises equipment (CPE)* to a router appliance instance.\n CPEs typically use a connectivity mechanism, such as an SD-WAN overlay tunnel\n or an IPsec VPN tunnel, to establish connectivity with the\n router appliance instance.\n\n Each router appliance instance is located in the\n Google Cloud region closest to its associated customer network. Both\n router appliance instances are in a single VPC network.\n However, the router appliance instances are in different regions. For this\n reason, the VPC network has its\n [dynamic routing mode](/vpc/docs/create-modify-vpc-networks#switch-dynamic-routing)\n set to `global`.\n2. Both router appliance instances are attached as spokes to the\n Network Connectivity Center hub. Because `Customer network A` and `Customer network B`\n need to send data to each other, both spokes have the site-to-site data\n transfer field enabled.\n\n *You can use site-to-site data transfer only in supported locations.* For\n more information, see\n [Locations supported for data transfer](/network-connectivity/docs/network-connectivity-center/concepts/locations).\n3. In each region, a router appliance instance establishes Border Gateway\n Protocol (BGP) peering with the appropriate Cloud Router. Each\n Cloud Router receives and advertises route prefixes from the\n corresponding on-premises location.\n\n4. The Cloud Routers dynamically exchange all received\n routes with each other. This configuration provides end-to-end dynamic route\n exchange and data plane connectivity between `Customer network A` and\n `Customer network B`.\n\n | **Important:** For Cloud Routers in different regions to exchange routes with each other, you must enable global dynamic routing mode in your VPC network. For more information, see [Dynamic routing](/vpc/docs/vpc#routing_for_hybrid_networks).\n\nFor detailed configuration steps for a load-balanced single-site topology,\nsee\n[Create router appliance instances](/network-connectivity/docs/network-connectivity-center/how-to/creating-router-appliances).\n\nRequirements\n------------\n\nFollow these requirements when deploying router appliance instances.\n\n### BGP configuration\n\n- The router appliance image that you install must support the BGP routing protocol.\n- To enable BGP peering between a router appliance instance and a Cloud Router, attach each router appliance instance as a spoke to a Network Connectivity Center hub.\n- Create a Cloud Router in the same region as the [subnet](/vpc/docs/vpc#subnets_vs_subnetworks) that contains the peering interface of the router appliance instance.\n- Manually create BGP interfaces on the router appliance instance. These interfaces must be in the same subnet as the router appliance instance.\n- Manually create BGP sessions with Cloud Router from the router appliance instance.\n- For VMs that have multiple network interfaces configured as part of the router appliance instance, you can establish BGP sessions with Cloud Routers that are in the same subnet as the VM interface. For more information about VM interfaces, see [Multiple network interfaces overview and examples](/vpc/docs/multiple-interfaces-concepts).\n\n### Availability recommendations\n\n- The standard service-level agreement (SLA) for Compute Engine VMs also applies to the availability of router appliance instances. This availability SLA is 99.5% for a single VM and 99.99% for VMs in multiple zones. For more information, see the [Compute Engine SLA](/compute/sla).\n- For a pair of router appliance instances, each for a different on-premises location, run at least two VMs in different zones. Each VM must peer with a pair of redundant Cloud Router interfaces. For more information about zones, see [Regions and zones](/compute/docs/regions-zones).\n\nConsiderations\n--------------\n\nBefore using Router appliance, review the following sections.\n\n### General considerations\n\n- *Router appliance requires Network Connectivity Center to operate.* That is, you can't configure standalone router appliance instances that peer with a Cloud Router or with other peer routers. You must configure router appliance instances as part of a Network Connectivity Center spoke.\n- Router appliance is only supported in the Shared VPC model when\n deployed in the host project. The router appliance instance must be deployed\n in the host project and all the other associated resources, such as hub,\n spoke, and Cloud Router.\n\n Router appliance does not support Shared VPC when the\n Router appliance VM is deployed in the service project.\n\n### Routing considerations\n\n- If multiple router appliance instances announce the same routing prefixes with the same MED, Google Cloud uses equal-cost multipath (ECMP) routing across all the router appliance instances.\n- *We recommend not advertising the same prefixes through a mix of different\n spoke types (router appliance instances, Cloud VPN gateways,\n and VLAN attachments).* If the same prefixes are reachable through a mix of spoke types, using ECMP across the mixed spoke types can lead to imbalanced traffic across each link.\n- If a single Cloud Router learns a prefix with multiple next hops, Cloud Router selects the next hops with the shortest AS path length first, and then uses the MED to break ties. For more information, see [AS path length](/router/concepts/learned-routes#as-path-length-considerations) in the Cloud Router documentation.\n\nWhat's next\n-----------\n\n- To set up Google Cloud resources for your router appliance instance, see [Create router appliance instances](/network-connectivity/docs/network-connectivity-center/how-to/creating-router-appliances).\n- To view a list of partners whose solutions are integrated with Network Connectivity Center, see [Network Connectivity Center partners](/network-connectivity/docs/network-connectivity-center/partners).\n- To view Router appliance monitoring and logging information, see [Viewing logs and metrics](/network-connectivity/docs/network-connectivity-center/how-to/viewing-logs-metrics).\n- To find solutions for Router appliance issues, see [Troubleshooting](/network-connectivity/docs/network-connectivity-center/support/troubleshooting#troubleshooting-ra).\n- To get details about API and `gcloud` commands, see [APIs and reference](/network-connectivity/docs/network-connectivity-center/apis)."]]
