You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/configure-azure-elastic-san.md
+44-32Lines changed: 44 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,52 +18,61 @@ Azure Elastic storage area network (SAN) addresses the problem of workload optim
18
18
19
19
The following prerequisites are required to continue.
20
20
21
-
- Verify you have a Dev/Test private cloud in a [region that Elastic SAN is available in](../storage/elastic-san/elastic-san-create.md).
21
+
- Verify you have a private cloud in a [region that Elastic SAN is available in](../storage/elastic-san/elastic-san-create.md).
22
22
- Know the availability zone your private cloud is in.
23
-
- In the UI, select an Azure VMware Solution host.
24
-
> [!NOTE]
25
-
> The host exposes its Availability Zone. You should use that AZ when deploying other Azure resources for the same subscription.
23
+
- In the UI, select an Azure VMware Solution host.
24
+
> [!NOTE]
25
+
> The host exposes its Availability Zone. You should use that AZ when deploying other Azure resources for the same subscription.
26
26
- You have permission to set up new resources in the subscription your private cloud is in.
27
27
28
-
## Set preview feature flags
28
+
- Reserve a dedicated address block for your external storage.
29
29
30
-
To use ElasticSAN with Azure VMware Solution, you need to set three feature flags on your subscription:
30
+
## Supported host types
31
31
32
-
- earlyAccess
33
-
- iSCSIMultipath
34
-
- ElasticSanDatastore
32
+
To use Elastic SAN with Azure VMware Solution, you can use any of these three host types:
35
33
36
-
Setting a feature flag can be done in the subscription overview page in the Azure portal.
34
+
- AV36
37
35
38
-
1. Under the **Settings** section, select **Preview features**.
39
-
1. On the **Preview features** page, use the search bar to find the feature flags you need to register. Once found, select the feature flag you want to register and select **Register** at the top.
40
-
1. Verify the **State** of the feature is changed to **Registered** with a green checkmark.
36
+
- AV36P
41
37
38
+
- AV52
39
+
40
+
Using AV64 with Elastic SAN is not currently supported.
42
41
43
42
## Set up Elastic SAN
44
43
45
-
In this section, you create a virtual network for your Elastic SAN. Then you create the Elastic SAN that includes creating at least one volume group and one volume that becomes your VMFS datastore. Next, you set up a Private Endpoint for your Elastic SAN that allows your private cloud to connect to the Elastic SAN volume. Then you're ready to add an Elastic SAN volume as a datastore in your private cloud.
44
+
In this section, you create a virtual network for your Elastic SAN. Then you create the Elastic SAN that includes creating at least one volume group and one volume that becomes your VMFS datastore. Next, you set up private endpoints for your Elastic SAN that allows your private cloud to connect to the Elastic SAN volume. Then you're ready to add an Elastic SAN volume as a datastore in your private cloud.
46
45
47
46
1. Use one of the following instruction options to set up a dedicated virtual network for your Elastic SAN:
You should use multiple private endpoints to establish multiple sessions between an Elastic SAN and each volume group you intend to connect to your SDDC. Because of how Elastic SAN handles sessions, having multiple sessions comes with two benefits: increased performance thanks to parallelization, and increased reliability to handle single session disconnects due to unexpected factors like network glitches. When you establish multiple sessions, it mitigates the impact of session disconnects, as long as the connection re-established within a few seconds, your other sessions help load-balance traffic.
68
+
69
+
> [!NOTE]
70
+
> Session disconnects may still show up as "All Paths Down" or "APD" events, which can be seen in the Events section of the ESXi Host at vCenter. You can also see them in the logs: it will show the identifier of a device or filesystem, and state it has entered the All Paths Down state.
64
71
65
-
Once all three feature flags (earlyAccess, iSCSIMultipath, ElasticSanDatastore) are set on your subscription, you can use the Azure portal to add the Elastic SAN volume as a datastore in your private cloud. Use the steps in [configure external storage address block](#configure-external-storage-address-block) to add, connect, disconnect, and delete Elastic SAN.
72
+
Each private endpoint provides two sessions to Elastic SAN per host. The recommended number of sessions to Elastic SAN per host is 8, but because the maximum number of sessions an Elastic SAN datastore can handle is 128, the ideal number for your setup depends on the number of hosts in your private cloud.
66
73
74
+
> [!IMPORTANT]
75
+
> You should configure all Private Endpoints before attaching a volume as a datastore. Adding Private Endpoints after a volume is attached as a datastore will require detaching the datastore and reconnecting it to the cluster.
67
76
## Configure external storage address block
68
77
69
78
Start by providing an IP block for deploying external storage. Navigate to the **Storage** tab in your Azure VMware Solution private cloud in the Azure portal. The address block should be a /24 network.
@@ -75,19 +84,22 @@ Start by providing an IP block for deploying external storage. Navigate to the *
75
84
- The address block can't overlap any of the following restricted network blocks: 100.72.0.0/15
76
85
- The address block provided is used to enable multipathing from the ESXi hosts to the target, it can’t be edited or changed. If you do need to change it, submit a support request.
77
86
78
-
After you provide an External storage address block, you can connect to an Elastic SAN volume from the same page.
79
-
80
87
## Connect Elastic SAN
81
88
82
-
First, you need to connect your SDDC express route with the private endpoint you set up for your Elastic SAN volume group. Instructions on how to establish this connection can be found in the Tutorial, [Configure networking for your VMware private cloud in Azure](../azure-vmware/tutorial-configure-networking.md).
89
+
After you provide an External storage address block, you need to connect your private cloud express route with the private endpoint(s) you set up for your Elastic SAN volume group(s). To learn how to establish these connections, see [Configure networking for your VMware private cloud in Azure](../azure-vmware/tutorial-configure-networking.md).
90
+
91
+
> [!NOTE]
92
+
> Connection to Elastic SAN from Azure VMWare Solution happens via private endpoints to provide the highest network security. Since your private cloud connects to Elastic SAN in Azure through an ExpressRoute virtual network gateway, you may experience intermittent connectivity issues during [gateway maintenance](/azure/expressroute/expressroute-about-virtual-network-gateways).
93
+
> These connectivity issues aren't expected to impact the availability of the datastore backed by Elastic SAN as the connection will be re-established within seconds. The potential impact from gateway maintenance is covered under the [Service Level Agreement](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1) for ExpressRoute virtual network gateways and private endpoints.
94
+
## Add an Elastic SAN volume as a datastore
83
95
84
96
Once your SDDC express route is connected with the private endpoint for your Elastic SAN volume group, use the following steps to connect the volume to your SDDC:
85
97
86
98
1. From the left navigation in your Azure VMware Solution private cloud, select **Storage**, then **+ Connect Elastic SAN**.
87
99
1. Select your **Subscription**, **Resource**, **Volume Group**, **Volume(s)**, and **Client cluster**.
88
100
1. From section, "Rename datastore as per VMware requirements", under **Volume name** > **Data store name**, give names to the Elastic SAN volumes.
89
-
> [!NOTE]
90
-
> For best performance, verify that your Elastic SAN volume and private cloud are in the same Region and Availability Zone.
101
+
> [!NOTE]
102
+
> For best performance, verify that your Elastic SAN volume and private cloud are in the same Region and Availability Zone.
91
103
92
104
## Disconnect and delete an Elastic SAN-based datastore
93
105
@@ -99,5 +111,5 @@ To delete the Elastic SAN-based datastore, use the following steps from the Azur
99
111
:::image type="content" source="media/configure-azure-elastic-san/elastic-san-datastore-list-ellipsis-removal.png" alt-text="Screenshot showing Elastic SAN volume removal." border="false"lightbox="media/configure-azure-elastic-san/elastic-san-datastore-list-ellipsis-removal.png":::
100
112
101
113
1. Optionally you can delete the volume you previously created in your Elastic SAN.
102
-
> [!NOTE]
103
-
> This operation can't be completed if virtual machines or virtual disks reside on an Elastic SAN VMFS Datastore.
114
+
> [!NOTE]
115
+
> This operation can't be completed if virtual machines or virtual disks reside on an Elastic SAN VMFS Datastore.
0 commit comments