2022-09-23T04:58:14.266Z cpu23:2103354 opID=be2a0887)NFS: 161: Command: (mount)
Server: (10.245.17.21) IP: (10.245.17.21) Path: (/vol-g-shared-vmware-002) Label:
(NFS) Options: (None)
...
2022-09-23T04:58:14.270Z cpu23:2103354 opID=be2a0887)NFS: 194: NFS mount
10.245.17.21:/vol-g-shared-vmware-002 failed: The mount request was denied by the
NFS server. Check that the export exists and that the client is permitted to
mount it.
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-18。"],[],[],null,["# Using NFS volume as vSphere datastore hosted by Google Cloud NetApp Volumes\n===========================================================================\n\nYou can use Google Cloud NetApp Volumes NFS storage for Standard, Premium, and\nExtreme service levels as an external datastore for ESXi hosts in\nGoogle Cloud VMware Engine. To do so, you must create NetApp Volumes in select regions and\nthen mount them as external datastores to their existing ESXi hosts in\nVMware Engine.\n\nThis solution has the following functionality for datastores:\n\n- Availability in all regions where both VMware Engine and NetApp Volumes are available\n- Support for NFSv3 protocol\n- Data protection through crash-consistent snapshots and cross-region replication\n\nThe following limitations apply:\n\n- Copy offload ([VAAI](https://core.vmware.com/resource/vmware-vsphere-apis-array-integration-vaai)) and NFSv4.1 are not supported.\n- SnapMirror functionality to and from on-premises for disaster recovery is not supported.\n\nNetworking\n----------\n\nNetApp Volumes and VMware Engine services are connected through\n[private service access](/vpc/docs/private-services-access)\n(PSA). Network charges resulting from storage access within a region don't\napply. It is not recommended to access a datastore volume from a different\nregion. You can create NetApp Volumes in Google Cloud console and enable deletion\nprotection before mounting the volumes as datastores to their ESXi hosts.\n\nHere's a diagram that shows NetApp Volumes being used\nwith VMware Engine and Compute Engine:\n\nBefore you begin\n----------------\n\nThe steps in this document assume that you have done the following:\n\n- Earmarked a `/26` CIDR for the VMware Engine service network to be used for external NFS storage.\n\nService subnets\n---------------\n\nWhen you create a private cloud, VMware Engine creates additional\nservice subnets (for example, `service-1`, `service-2`, `service-3`). Service\nsubnets are targeted for appliance or service deployment scenarios, such as\nstorage, backup and disaster recovery, or media streaming, providing high scale,\nlinear throughput and packet processing for even the largest-scaled private\nclouds. VM communication across a service subnet travels from the VMware ESXi\nhost directly into the Google Cloud networking infrastructure, empowering\nhigh-speed communication.\n\nNSX-T gateway and distributed firewall rules don't apply to any service subnet.\n\nConfiguring service subnets\n---------------------------\n\nService subnets don't have a CIDR allocation on initial creation. Instead, you\nmust specify a non-overlapping CIDR range and prefix for service subnets using\nthe VMware Engine console or API.\n\nThe first usable address becomes the gateway address. To allocate a CIDR\nrange and prefix edit one of the service subnets.\n\nService subnets can be updated if CIDR requirements change. However, modification\nof an existing service subnet CIDR can cause network availability disruption for\nVMs attached to that service subnet.\n\nYou should add the reserved CIDR allocations for the service subnets you defined\nin the\n[VMware Engine portal](/vmware-engine/docs/howto-access-portal)\nto the NetApp Volumes Export Rules in the **Allowed Clients** section while\ncreating the volume.\n\nFailing to do so returns the following error or similar in `vmkernel.log`: \n\n 2022-09-23T04:58:14.266Z cpu23:2103354 opID=be2a0887)NFS: 161: Command: (mount)\n Server: (10.245.17.21) IP: (10.245.17.21) Path: (/vol-g-shared-vmware-002) Label:\n (NFS) Options: (None)\n ...\n 2022-09-23T04:58:14.270Z cpu23:2103354 opID=be2a0887)NFS: 194: NFS mount\n 10.245.17.21:/vol-g-shared-vmware-002 failed: The mount request was denied by the\n NFS server. Check that the export exists and that the client is permitted to\n mount it.\n\nGet VPC network details\n-----------------------\n\nWhen creating a peering connection between VMware Engine and\nNetApp Volumes, you need some details about the VPC network\nused by NetApp Volumes. To get these details, do the following:\n\n1. In the Google Cloud console, go to the **VPC Network peerings** page.\n\n [Go to VPC Network peerings](https://console.cloud.google.com/vmwareengine/network-peerings)\n2. Click **Select a project** and then select the organization, folder, or project that\n contains the peering connection.\n\n3. Select the peering connection created in NetApp Volumes for\n your project.\n The connection is named `sn-netapp-prod`.\n\n You might see multiple peering connections with the same name if you\n have more than one peered VPC network. The person who set up the\n VPC Network Peering connections can help you determine which connection\n to use for VMware Engine.\n4. Copy the **Peered VPC network** and **Peered project ID** fields, which\n begin with *netapp* and end with *-tp*, respectively.\n\nCreate a peering connection for legacy networks\n-----------------------------------------------\n\nTo establish a connection between VMware Engine and\nNetApp Volumes service, make a one-time peering between tenant\nhost projects. If your VMware Engine project and private clouds were\ncreated before Nov 12, 2023, you are using an earlier version of the\nVMware Engine network. For environments using an earlier version of\nVMware Engine network, do the following:\n\n1. In the Google Cloud console, go to the **Private connections** page.\n\n [Go to Private connections](https://console.cloud.google.com/vmwareengine/private-connections)\n2. Click **Select a project** and then select the organization, folder, or project where\n you want to create the peering connection.\n\n3. Click **Create**.\n\n4. In **Private connection name** , provide a name for your peering, for\n example, `peering-2-netapp-volumes`.\n\n5. In **VMware Engine network** , specify the VMware Engine network you\n want to peer, for example, `us-central1-default`.\n\n6. For **Private connection type** , select **Third party service**.\n\n7. In **Peered project ID**, enter the peered project ID of the\n NetApp Volumes that contains your volume.\n\n8. In **Peered VPC network**, enter the name of the peered VPC network that\n volume is in.\n\n9. Click **Create**.\n\nExpect the VPC peering status of your new private connection to stay in the\n*Inactive* state for up to 72 hours while VMware Engine\nservices and validates the peering request.\n\nCreate a peering connection\n---------------------------\n\nIf your VMware Engine project and private clouds were created after\nNov 12, 2023, do the following. For more information on how to create VPC\npeerings for such environments, see [Peer a VPC network](/vmware-engine/docs/networking/peer-vpc-network).\n\n1. In the Google Cloud console, go to the **VPC Network peerings** page.\n\n [Go to VPC Network peerings](https://console.cloud.google.com/vmwareengine/network-peerings)\n2. Click **Select a project** and then select the organization, folder, or project where\n you want to create the peering connection.\n\n3. Click **Create**.\n\n4. In the **Name** field, provide a name for your networking peering. For\n example, `peering-2-netapp-volumes`.\n\n5. In the **VMware Engine network** section, keep the default **\"In current\n project\"** selected. Specify the VMware Engine network you want to\n peer, for example `ven1`.\n\n6. For **Peering** , select **Google Cloud NetApp Volumes**.\n\n7. In the **Service tenant project ID** field, enter the *peered project ID* of\n the Google Cloud project containing your volume.\n\n8. In the **Service tenant VPC name** field, enter the name of the *peered VPC\n network* your volume is in.\n\n9. In the **Route exchange** section, keep the default settings.\n\n10. Click **Create**.\n\nCreating NetApp Volumes volumes\n-------------------------------\n\nWhen\n[creating a NetApp Volumes volume](/netapp/volumes/docs/configure-and-use/volumes/create-volume)\nfor use as a VMware Engine datastore, ensure\nthat the volume export rule allows the following:\n\n- Access from the VMware Engine ESXi hosts (or all hosts) under Allowed Clients. This is usually the service subnet range you created earlier.\n- Read \\& write access\n- Root access\n\nMarking the volumes as non-deletable\n------------------------------------\n\nBefore you can mount a NetApp Volumes volume as an external NFS datastore to\nESXi hosts in VMware Engine, these volumes must be blocked from\naccidental deletion by users to avoid disruption to the vSphere environment.\n\nYou can also use a Google Cloud CLI command to set the restricted actions delete\noption on your volume.\n\nVMware Engine mounts these volumes only if they are configured to\nbe blocked from deletion.\n\nAfter creating the volume, you can perform various volume management functions\nby using the NetApp Volumes UI/API/CLI. For more information, see\n[Volumes overview](/netapp/volumes/docs/configure-and-use/volumes/overview).\n\nMounting the volume as a datastore\n----------------------------------\n\nContact VMware Engine Support for assistance in mounting the\nvolume as a datastore. Provide the name of the private cloud, the volume mount\npath, and the service subnet.\n\nOnce the datastores are mounted and available, you can use vCenter UI to\nprovision VMs against the external datastores, view metrics and view logs\nrelated to io operations performed against external datastores.\n\nFor more information about NetApp Volumes, see\n[What is Google Cloud NetApp Volumes](/netapp/volumes/docs/discover/overview)."]]
