Merge pull request #165019 from roygara/netNote

Adding more info to planning guide and next steps for troubleshooting

Author: ShannonLeavitt

articles/virtual-machines/disks-pools-deploy.md

@@ -10,7 +10,7 @@ ms.subservice: disks
 ---
 # Deploy a disk pool (preview)
 
-This article covers how to deploy and configure a disk pool (preview). Before deploying a disk pool, read the [conceptual](disks-pools.md) and [planning](disks-pools-planning.md) articles.
+This article covers how to deploy and configure an Azure disk pool (preview). Before deploying a disk pool, read the [conceptual](disks-pools.md) and [planning](disks-pools-planning.md) articles.
 
 In order for a disk pool to work correctly, you must complete the following steps:
 - Register your subscription for the preview.

articles/virtual-machines/disks-pools-deprovision.md

@@ -11,7 +11,7 @@ ms.subservice: disks
 
 # Deprovision an Azure disk pool (preview)
 
-This article covers the deletion process for a disk pool (preview) and how to disable iSCSI support.
+This article covers the deletion process for an Azure disk pool (preview) and how to disable iSCSI support.
 
 ## Stop a disk pool
 

articles/virtual-machines/disks-pools-manage.md

@@ -11,7 +11,7 @@ ms.subservice: disks
 
 # Manage a disk pool (preview)
 
-Once you've deployed a disk pool (preview), there are two management actions available to you. You can:
+Once you've deployed an Azure disk pool (preview), there are two management actions available to you. You can:
 - Add a disk to a disk pool
 - Disable iSCSI support on a disk
 

articles/virtual-machines/disks-pools-move-resource.md

@@ -11,7 +11,7 @@ ms.subservice: disks
 
 # Move a disk pool (preview) to a different subscription
 
-Moving a disk pool (preview) involves moving the disk pool itself, the disks contained in the disk pool, the disk pool's managed resource group, and all the resources contained in the managed resource group. Currently, Azure doesn't support moving multiple resource groups to another subscription at once. 
+Moving an Azure disk pool (preview) involves moving the disk pool itself, the disks contained in the disk pool, the disk pool's managed resource group, and all the resources contained in the managed resource group. Currently, Azure doesn't support moving multiple resource groups to another subscription at once. 
 
 - Export the template of your existing disk pool.
 - Delete the old disk pool.

articles/virtual-machines/disks-pools-planning.md

@@ -11,7 +11,7 @@ ms.subservice: disks
 
 # Disk pools (preview) planning guide
 
-It's important to understand the performance requirements of your workload before you deploy a disk pool. Determining your requirements in advance allows you to get the most performance out of your disk pool. The performance of a disk pool is determined by three main factors: The disk pool's scalability target, the scalability targets of individual disks contained in the disk pool, and the networking connection between the client machines to the disk pool. Adjusting these three factors will tweak the performance you get from a disk pool.
+It's important to understand the performance requirements of your workload before you deploy an Azure disk pool (preview). Determining your requirements in advance allows you to get the most performance out of your disk pool. The performance of a disk pool is determined by three main factors: The disk pool's scalability target, the scalability targets of individual disks contained in the disk pool, and the networking connection between the client machines to the disk pool. Adjusting these three factors will tweak the performance you get from a disk pool.
 
 ## Optimize for low latency
 
@@ -45,7 +45,19 @@ Refer to the [Networking planning checklist for Azure VMware Solution](../azure-
 
 The following example should give you an idea of how the different performance factors work together:
 
-As an example, if we added two 1-TiB premium SSDs (P30, with a provisioned target of 5000 IOPS and 200 Mbps) into a disk pool, we could achieve 2 x 5000  = 10,000 IOPS but our throughput would be capped at 384 MBps by the disk pool. To exceed this 384-MBps limit, we can deploy more disk pools to scale out for extra throughput.
+As an example, if we added two 1-TiB premium SSDs (P30, with a provisioned target of 5000 IOPS and 200 Mbps) into a disk pool, we could achieve 2 x 5000  = 10,000 IOPS but our throughput would be capped at 384 MBps by the disk pool. To exceed this 384-MBps limit, we can deploy more disk pools to scale out for extra throughput. The throughput of your network will limit the effectiveness of scaling out.
+
+## Availability
+
+Disk pools are currently in preview, and shouldn't be used for production workloads.
+
+If your disk pool becomes inaccessible to your Azure VMware Solution cloud for any reason, you will experience the following:
+
+- All datastores associated to the disk pool will no longer be accessible.
+- All VMware VMs hosted in this Azure VMware Solution cloud what is using the impacted datastores will be in an unhealthy state.
+- The health of clusters in this Azure VMware Solution cloud won't be impacted, except for one operation: You won't be able to place a host into maintenance mode. Azure VMware Solution will handle this failure and attempt recovery by disconnecting the impacted datastores.
+
+If you enter this state, follow these [steps](disks-pools-troubleshoot.md#recover-a-disk-pool-or-an-iscsi-target) to recover your disk pool.
 
 ## Next steps
 

articles/virtual-machines/disks-pools-troubleshoot.md

@@ -11,16 +11,20 @@ ms.subservice: disks
 
 # Troubleshoot Azure disk pools (preview)
 
-This article lists some common failure codes related to Azure disk pools. It also provides possible resolutions and some clarity on disk pool statuses.
+This article lists some common failure codes related to Azure disk pools (preview). It also provides possible resolutions and some clarity on disk pool statuses.
 
 ## Disk pool status
 
 Disk pools and iSCSI targets each have four states: **Unknown**, **Running**, **Updating**, and **Stopped (deallocated)**.
 
 **Unknown** means that the resource is in a bad or unknown state. To attempt recovery, perform an update operation on the resource (such as adding or removing disks/LUNS) or delete and redeploy your disk pool.
 
+**Running** means the resource is running and in a healthy state.
+
 **Updating** means that the resource is going through an update. This usually happens during deployment or when applying an update like adding disks or LUNs.
 
+**Stopped (deallocated)** means that the resource is stopped and its underlying resources have been deallocated. You can restart the resource to recover your disk pool or iSCSI target.
+
 ## Recover a disk pool or an iSCSI target
 
 First, stop the disk pool and restart it. Then check the status of the disk pool and the iSCSI target. If they have recovered, then any Azure VMware clusters connected to the disk pool will recover automatically unless the disk pool has been inaccessible for more than 24 hours. If it has been more than 24 hours, then you need to contact Azure support to forcibly disconnect the inaccessible datastores associated with the disk pool. After that, you can reconnect the VS clusters to the disk pool and configure the datastores.
@@ -44,4 +48,8 @@ If the disk pool didn't recover after this process, contact Azure support and pr
 |---------|---------|
 |GoalStateApplicationError     |Occurs when the iSCSI target configuration is invalid and cannot be applied to the disk pool. Retry the deployment. If the issue persists, contact Azure support and provide the tracking ID of the error.         |
 |GoalStateApplicationTimeoutError     |Occurs when the disk pool infrastructure stops responding to the resource provider. Retry the deployment. If the issue persists, contact Azure support and provide the tracking ID of the error.         |
-|OngoingOperationInProgress     |An ongoing operation is in-progress on the disk pool. Wait until that operation completes, then retry deployment.         |
+|OngoingOperationInProgress     |An ongoing operation is in-progress on the disk pool. Wait until that operation completes, then retry deployment.         |
+
+## Next steps
+
+[Manage a disk pool (preview)](disks-pools-manage.md)

articles/virtual-machines/disks-pools.md

@@ -12,7 +12,7 @@ ms.custom: references_regions
 
 # Azure disk pools (preview)
 
-A disk pool (preview) is a top-level Azure resource that allows your applications and workloads to access all disks under one single endpoint. A disk pool can expose an Internet Small Computer Systems Interface (iSCSI) target to enable data access to disks inside this pool over iSCSI. Each disk pool can have one iSCSI target and each disk can be exposed as an iSCSI LUN. You can connect disks under the disk pool to Azure VMware Solution hosts as datastores. This allows you to scale your storage independent of your Azure VMware Solution hosts. Once a datastore is configured, you can create volumes on it and attach them to your VMware instances.
+An Azure disk pool (preview) is a top-level Azure resource that allows your applications and workloads to access all disks under one single endpoint. A disk pool can expose an Internet Small Computer Systems Interface (iSCSI) target to enable data access to disks inside this pool over iSCSI. Each disk pool can have one iSCSI target and each disk can be exposed as an iSCSI LUN. You can connect disks under the disk pool to Azure VMware Solution hosts as datastores. This allows you to scale your storage independent of your Azure VMware Solution hosts. Once a datastore is configured, you can create volumes on it and attach them to your VMware instances.
 
 ## How it works
 
@@ -37,11 +37,8 @@ Disk pools are currently available in the following regions:
 - Canada Central
 - East US
 - West US 2
-- Central US
 - Japan East
 - North Europe
-- West Europe
-- UK South
 
 
 ## Billing