Skip to content

Commit 7993168

Browse files
Merge pull request #263529 from b-ahibbard/avs-remove-reg
Avs remove reg
2 parents 90c1d2a + eb86f40 commit 7993168

File tree

1 file changed

+1
-35
lines changed

1 file changed

+1
-35
lines changed

articles/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md

Lines changed: 1 addition & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -28,19 +28,11 @@ Before you begin the prerequisites, review the [Performance best practices](#per
2828
1. [Deploy Azure VMware Solution](./deploy-azure-vmware-solution.md) private cloud and a dedicated virtual network connected via ExpressRoute gateway. The virtual network gateway should be configured with the Ultra performance or ErGw3Az SKU and have FastPath enabled. For more information, see [Configure networking for your VMware private cloud](tutorial-configure-networking.md) and [Network planning checklist](tutorial-network-checklist.md).
2929
1. Create an [NFSv3 volume for Azure NetApp Files](../azure-netapp-files/azure-netapp-files-create-volumes.md) in the same virtual network created in the previous step.
3030
1. Verify connectivity from the private cloud to Azure NetApp Files volume by pinging the attached target IP.
31-
2. Verify the subscription is registered to the `ANFAvsDataStore` feature in the `Microsoft.NetApp` namespace. If the subscription isn't registered, register it now.
32-
33-
`az feature register --name "ANFAvsDataStore" --namespace "Microsoft.NetApp"`
34-
35-
`az feature show --name "ANFAvsDataStore" --namespace "Microsoft.NetApp" --query properties.state`
3631
1. Based on your performance requirements, select the correct service level needed for the Azure NetApp Files capacity pool. Select option **Azure VMware Solution Datastore** listed under the **Protocol** section.
3732
1. Create a volume with **Standard** [network features](../azure-netapp-files/configure-network-features.md) if available for ExpressRoute FastPath connectivity.
3833
1. Under the **Protocol** section, select **Azure VMware Solution Datastore** to indicate the volume is created to use as a datastore for Azure VMware Solution private cloud.
3934
1. If you're using [export policies](../azure-netapp-files/azure-netapp-files-configure-export-policy.md) to control access to Azure NetApp Files volumes, enable the Azure VMware private cloud IP range, not individual host IPs. Faulty hosts in a private cloud could get replaced. If the IP isn't enabled, connectivity to datastore is impacted.
4035

41-
>[!NOTE]
42-
>Azure NetApp Files datastores for Azure VMware Solution are generally available. To use it, you must register Azure NetApp Files datastores for Azure VMware Solution.
43-
4436
## Supported regions
4537

4638
Azure NetApp Files datastores for Azure VMware Solution are currently supported in the following regions:
@@ -99,13 +91,6 @@ For performance benchmarks that Azure NetApp Files datastores deliver for VMs on
9991
To attach an Azure NetApp Files volume to your private cloud using Portal, follow these steps:
10092

10193
1. Sign in to the Azure portal.
102-
1. Select **Subscriptions** to see a list of subscriptions.
103-
1. From the list, select the subscription you want to use.
104-
1. Under Settings, select **Resource providers**.
105-
1. Search for **Microsoft.AVS** and select it.
106-
1. Select **Register**.
107-
1. Under **Settings**, select **Preview features**.
108-
1. Verify you're registered for both the `CloudSanExperience` and `AnfDatstoreExperience` features.
10994
1. Navigate to your Azure VMware Solution.
11095
Under **Manage**, select **Storage**.
11196
1. Select **Connect Azure NetApp Files volume**.
@@ -123,25 +108,6 @@ Under **Manage**, select **Storage**.
123108

124109
To attach an Azure NetApp Files volume to your private cloud using Azure CLI, follow these steps:
125110

126-
1. Verify the subscription is registered to `CloudSanExperience` feature in the **Microsoft.AVS** namespace. If it's not, register it.
127-
128-
`az feature show --name "CloudSanExperience" --namespace "Microsoft.AVS"`
129-
130-
`az feature register --name "CloudSanExperience" --namespace "Microsoft.AVS"`
131-
1. The registration should take approximately 15 minutes to complete. You can also check the status.
132-
133-
`az feature show --name "CloudSanExperience" --namespace "Microsoft.AVS" --query properties.state`
134-
1. If the registration is stuck in an intermediate state for longer than 15 minutes, unregister, then re-register the flag.
135-
136-
`az feature unregister --name "CloudSanExperience" --namespace "Microsoft.AVS"`
137-
138-
`az feature register --name "CloudSanExperience" --namespace "Microsoft.AVS"`
139-
1. Verify the subscription is registered to `AnfDatastoreExperience` feature in the **Microsoft.AVS** namespace. If it's not, register it.
140-
141-
`az feature register --name " AnfDatastoreExperience" --namespace "Microsoft.AVS"`
142-
143-
`az feature show --name "AnfDatastoreExperience" --namespace "Microsoft.AVS" --query properties.state`
144-
145111
1. Verify the VMware extension is installed. If the extension is already installed, verify you're using the latest version of the Azure CLI extension. If an older version is installed, update the extension.
146112

147113
`az extension show --name vmware`
@@ -155,7 +121,7 @@ To attach an Azure NetApp Files volume to your private cloud using Azure CLI, fo
155121
1. Create a datastore using an existing ANF volume in Azure VMware Solution private cloud cluster.
156122

157123
`az vmware datastore netapp-volume create --name MyDatastore1 --resource-group MyResourceGroup –-cluster Cluster-1 --private-cloud MyPrivateCloud –-volume-id /subscriptions/<Subscription Id>/resourceGroups/<Resourcegroup name>/providers/Microsoft.NetApp/netAppAccounts/<Account name>/capacityPools/<pool name>/volumes/<Volume name>`
158-
1. If needed, you can display the help on the datastores.
124+
1. If needed, display the help on the datastores.
159125

160126
`az vmware datastore -h`
161127
1. Show the details of an ANF-based datastore in a private cloud cluster.

0 commit comments

Comments
 (0)