Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini membahas konfigurasi jaringan dan persyaratan resource IP untuk
Filestore.
Dukungan konektivitas
Filestore terhubung ke jaringan VPC Anda menggunakan Peering Jaringan VPC atau akses layanan pribadi.
Diagram berikut menunjukkan metode koneksi yang mendukung skenario tertentu:
SCENARIO
Peering Jaringan VPC
Akses layanan pribadi
Buat instance dengan jaringan VPC mandiri.
✓
✓
Buat instance di jaringan VPC Bersama dari project host.
✓
✓
Membuat instance di jaringan VPC Bersama dari project layanan.
✓
Menggunakan pengelolaan rentang IP terpusat untuk beberapa layanan Google.
✓
Mengakses instance dari jaringan lokal menggunakan Cloud VPN atau Cloud Interconnect.
✓
✓
Filestore mendukung skenario konektivitas berikut:
Sebagian besar VM Compute Engine atau cluster GKE dapat mengakses
instance Filestore yang berada di jaringan VPC
yang sama. Semua alamat IP internal di jaringan VPC yang dipilih dapat terhubung ke instance Filestore, kecuali jika akses dibatasi menggunakan kontrol akses berbasis IP.
Klien dengan alamat IP dalam rentang 172.17.0.0/16 tidak dapat terhubung ke
instance Filestore. Untuk mengetahui informasi selengkapnya, baca
Masalah umum.
Anda dapat menghubungkan instance Filestore ke klien di jaringan jarak jauh
menggunakan Cloud VPN atau Cloud Interconnect, termasuk klien
dari project lain atau klien lokal Anda.
Anda dapat menghubungkan klien
non-RFC 1918
ke Filestore. Dalam hal ini, Anda harus secara eksplisit memberi mereka akses ke instance Filestore menggunakan kontrol akses berbasis IP.
Filestore tidak mendukung peering transitif.
Misalnya, jika jaringan VPC N1 di-peering ke jaringan internal Filestore, dan jaringan VPC lain, N2, di-peering ke N1, N2 tidak akan memiliki konektivitas ke instance Filestore. Hanya
klien di N1 yang dapat mengakses instance Filestore.
Aturan firewall
Anda mungkin perlu membuat aturan firewall dalam skenario berikut:
Untuk mengaktifkan penguncian file NFS, Anda mungkin perlu membuka port yang digunakan oleh
daemon statd dan nlockmgr. Untuk mengetahui informasi selengkapnya, lihat
Mengonfigurasi aturan firewall.
Dalam skenario VPC Bersama, akses NFS tidak dibatasi untuk
project layanan secara default. Anda dapat menetapkan aturan firewall atau menggunakan kontrol akses berbasis IP untuk membatasi akses, tetapi solusi ini tidak secara khusus menerapkan batas project.
Dukungan jaringan lama
Anda tidak dapat menggunakan jaringan lama dengan instance Filestore. Jika
perlu, buat jaringan VPC baru untuk digunakan dengan mengikuti
petunjuk di
Membuat jaringan VPC baru dengan subnet kustom.
Persyaratan resource IP
Setiap instance Filestore harus memiliki rentang alamat IP yang terkait dengannya. Rentang alamat IP RFC 1918
dan non-RFC 1918 (GA)
didukung.
Pengguna sebaiknya mengizinkan Filestore menentukan secara otomatis
rentang alamat IP yang tersedia dan menetapkannya ke instance. Jika memilih rentang Anda sendiri, lihat Mengonfigurasi rentang alamat IP yang dicadangkan untuk persyaratan Filestore tertentu.
[[["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-25 UTC."],[[["\u003cp\u003eFilestore connects to your VPC network using either VPC Network Peering or private services access, supporting various scenarios including standalone VPC networks, Shared VPC networks, and on-premises network access via Cloud VPN or Cloud Interconnect.\u003c/p\u003e\n"],["\u003cp\u003eMost Compute Engine VMs or GKE clusters on the same VPC network can access Filestore instances, but clients with IP addresses in the \u003ccode\u003e172.17.0.0/16\u003c/code\u003e range are an exception.\u003c/p\u003e\n"],["\u003cp\u003eFilestore does not support transitive peering, meaning if one VPC network is peered to another which is then peered to Filestore's internal network, the initial VPC network will not have connectivity.\u003c/p\u003e\n"],["\u003cp\u003eEach Filestore instance requires an IP address range, and while both RFC 1918 and non-RFC 1918 IP ranges are supported, it's recommended to let Filestore automatically determine and assign the free range.\u003c/p\u003e\n"],["\u003cp\u003eFirewall rules may be necessary to enable NFS file locking or to restrict access in Shared VPC scenarios, although the provided solutions do not specifically enforce project boundaries.\u003c/p\u003e\n"]]],[],null,["# Network configuration and IP resource requirements\n\nThis page discusses network configuration and IP resource requirements for\nFilestore.\n\nConnectivity support\n--------------------\n\nFilestore connects to your VPC network using\neither [VPC Network Peering](/vpc/docs/vpc-peering) or\n[private services access](/vpc/docs/private-services-access).\nThe following chart shows which connection method supports which scenarios:\n\nFilestore supports the following connectivity scenarios:\n\n- Most any Compute Engine VM or GKE cluster can access any Filestore instance that's on the same VPC network. All internal IP addresses in the selected VPC network can connect to the Filestore instance unless access is restricted using IP-based access control.\n - Clients with an IP address in the `172.17.0.0/16` range can't connect to Filestore instances. For more information, see [Known issues](/filestore/docs/known-issues#clients_cant_have_an_ip_address_from_the_172170016_range).\n- You can connect Filestore instances to clients in remote networks using Cloud VPN or Cloud Interconnect, including clients from another project or your on-premises clients.\n- You can connect non-[RFC 1918](https://tools.ietf.org/html/rfc1918) clients to Filestore. In this case, you must explicitly grant them access to the Filestore instance using [IP-based access control](/filestore/docs/creating-instances#configure_ip-based_access_control).\n\nFilestore doesn't support [transitive peering](/vpc/docs/vpc-peering#transit-network).\nFor example, if VPC network N1 is peered to Filestore's\ninternal network, and another VPC network, N2, is peered to N1,\nN2 won't have connectivity to the Filestore instance. Only\nclients on N1 can access the Filestore instance.\n\nFirewall rules\n--------------\n\nYou may need to create firewall rules in the following scenarios:\n\n- To enable NFS file locking, you may need to open up the ports used by the `statd` and `nlockmgr` daemons. For more information, see [Configuring firewall rules](/filestore/docs/configuring-firewall).\n- In the Shared VPC scenario, NFS access is not restricted to the service project by default. You can set firewall rules or use [IP-based access control](/filestore/docs/creating-instances#configure_ip-based_access_control) to restrict access, but these solutions don't specifically enforce project boundaries.\n\nLegacy network support\n----------------------\n\nYou can't use a legacy network with Filestore instances. If\nnecessary, create a new VPC network to use by following the\ninstructions at\n[Creating a new VPC network with custom subnets](/vpc/docs/create-modify-vpc-networks#create-custom-network).\n\nIP resource requirements\n------------------------\n\nEach Filestore instance must have an IP address range associated\nwith it. Both [RFC 1918](https://tools.ietf.org/html/rfc1918) and non-RFC 1918 IP address ranges ([GA](/products#product-launch-stages)) are supported.\n\nDuring instance creation, Filestore can automatically allocate an IP address range and assign IP addresses from that range to the instance. You can also manually provide a specific IP address range for your instance.\n\nAfter you create the instance, you can't change the assigned IP addresses. If you want to introduce changes, delete and recreate the instance with a new IP address range.\n\nFor more information, see [Configure a reserved IP address range](/filestore/docs/creating-instances#configure_a_reserved_ip_address_range).\n\nWhat's next\n-----------\n\n- [Acquire the Identity and Access Management roles and permissions](/filestore/docs/iam) needed to use Filestore.\n- Try one of the Filestore quickstarts:\n - Using the [Google Cloud console](/filestore/docs/quickstart-console)\n - Using the [Google Cloud CLI](/filestore/docs/quickstart-gcloud)\n- Learn more about [Virtual Private Cloud (VPC) networks and subnets](/vpc/docs/subnets#valid-ranges).\n- Troubleshoot [common Filestore networking issues](/filestore/docs/troubleshooting).\n- [Create a Filestore instance on a Shared VPC network in service projects](/filestore/docs/shared-vpc)."]]
