Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menjelaskan cara menghubungkan jaringan tambahan ke volume Anda.
Google Cloud NetApp Volumes menggunakan akses layanan pribadi untuk menghosting volume Anda. Volume disediakan di VPC tenant dalam project internal layanan. VPC tenant terhubung ke VPC project Anda menggunakan peering VPC. Oleh karena itu, hanya klien yang terhubung ke VPC project Anda yang dapat mengakses volume. Jika Anda ingin memberikan akses ke
volume kepada klien di jaringan yang berbeda, Anda harus membuat koneksi
jaringan tambahan.
Berikut adalah opsi konektivitas:
VPC Bersama: pendekatan umum adalah menempatkan NetApp Volumes dan semua VM klien di VPC bersama yang sama, sambil mempertahankan VM di project layanan yang berbeda untuk tujuan isolasi beban kerja dan penagihan.
Koneksi VPN: jika Anda menghubungkan VPC tambahan ke VPC project
menggunakan VPN, bukan peering VPC,
Anda dapat mengonfigurasi perutean transitif.
Interkoneksi: jika Anda menghubungkan jaringan tambahan ke VPC project menggunakan interkoneksi, Anda dapat mengonfigurasi perutean transitif.
Menghubungkan jaringan tambahan dengan peering manual
NetApp Volumes membuat konektivitas dengan membuat project dan jaringan tenant akses layanan pribadi, yang kemudian dihubungkan dengan jaringan project yang Anda tentukan melalui peering VPC. Untuk mengizinkan klien di jaringan lain mengakses volume yang sama, Anda dapat melakukan peering VPC tambahan dari project Anda ke jaringan tenant ini.
Untuk permintaan peering VPC tambahan dengan project tenant NetApp Volumes, hubungi Customer Care Google Cloud.
Sebelum melanjutkan, sebaiknya tinjau dokumentasi peering VPC untuk mempelajari batasan, batas, dan penagihan peering VPC.
[[["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-09-04 UTC."],[],[],null,["# Connect additional networks\n\nThis page describes how to connect additional networks to your volumes.\n\nGoogle Cloud NetApp Volumes uses [private service access](/netapp/volumes/docs/get-started/configure-access/networking) to host your volumes. Volumes are provisioned on a tenant\nVPC within a service-internal project. The tenant\nVPC is connected to your project VPC using\nVPC peering. Therefore, only clients connected to your project\nVPC can access the volumes. If you want to grant access to the\nvolumes to clients on different networks, you have to establish additional\nnetwork connections.\n\nThe following are the connectivity options:\n\n- **Shared VPCs**: a common approach is to put both\n NetApp Volumes and all client VMs on the same shared\n VPC, while keeping the VMs in different service projects for\n workload isolation and billing purposes.\n\n- **VPN connection**: if you connect an additional VPC to your\n project VPC using VPN instead of VPC peering,\n you can configure transitive routing.\n\n- **VPC peering** : if you connect additional VPCs to your\n project's VPC using peering, clients on those\n VPCs can't connect to your volumes as [VPC\n peering doesn't provide transitive routing](/vpc/docs/vpc-peering#spec-general).\n However, you can establish direct peerings between these additional\n VPCs and the tenant VPC. For more information,\n see [Connect additional networks with manual peering](#connect_additional_networks_with_manual_peering).\n\n- **Interconnects**: if you connect additional networks to your project\n VPC using interconnects, you can configure transitive routing.\n\nConnect additional networks with manual peering\n-----------------------------------------------\n\nNetApp Volumes establishes connectivity by creating a\nprivate service access tenant project and network, which is then connected\nwith your specified project network by VPC peering. To enable\nclients in other networks to access the same volumes, you can peer additional\nVPCs from your projects to this tenant network.\n\nFor any requests to peer an additional VPC with a\nNetApp Volumes tenant project, contact [Google Cloud Customer Care](https://cloud.google.com/support-hub/).\n\nBefore you proceed, we recommend that you review the\n[VPC peering](/vpc/docs/vpc-peering) documentation to learn about\nVPC peering limitations, limits, and billing."]]
