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
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to use Elastic SAN with Azure VMware Solution.
4
4
ms.topic: how-to
5
5
ms.service: azure-vmware
6
6
ms.author: v-suzuber
7
-
ms.date: 05/05/2025
7
+
ms.date: 05/21/2025
8
8
ms.custom: references_regions, engagement-fy23
9
9
---
10
10
@@ -21,10 +21,11 @@ To accompany the steps below, you can use this [interactive demo](https://regale
21
21
The following prerequisites are required to continue.
22
22
23
23
- Have a fully configured Azure VMware solution private cloud in a [region that Elastic SAN is available in](../storage/elastic-san/elastic-san-create.md).
24
+
- Ensure that your ExpressRoute gateways are sized to handle your elastic SAN's bandwidth capabilities. For example, a single ultra performance ExpressRoute gateway supports a bandwidth of 1,280 mbps. If you're using an individual elastic SAN datastore to its full potential, it'll consume the entirety of that bandwidth. Multiple gateways may be required depending on your needs.
24
25
- Know the availability zone your private cloud is in.
25
26
- In the UI, select an Azure VMware Solution host.
26
27
> [!NOTE]
27
-
> The host exposes its Availability Zone. You should use that AZ when deploying other Azure resources for the same subscription.
28
+
> The host exposes its availability zone. Use that availability zone when deploying other Azure resources for the same subscription.
28
29
29
30
- Have permission to set up new resources in the subscription your private cloud is in.
30
31
- Reserve a dedicated address block for your external storage.
@@ -44,7 +45,7 @@ You can use the following host types when Azure Elastic SAN is the backing stora
44
45
45
46
## Configuration recommendations
46
47
47
-
Use multiple private endpoints to establish multiple sessions between an Elastic SAN and each volume group you intend to connect to your software defined data center (SDDC). Having multiple sessions provides better performance due to parallelization, and better reliability to handle single session disconnects from unexpected factors. When you establish multiple sessions, it also mitigates the impact of session disconnects, as long as the connection is re-established within a few seconds, your other sessions help load-balance traffic.
48
+
Use multiple private endpoints to establish multiple sessions between an Elastic SAN and each volume you intend to connect to your software defined data center (SDDC). Having multiple sessions provides better performance due to parallelization, and better reliability to handle single session disconnects. When you establish multiple sessions, it also mitigates the impact of session disconnects, as long as the connection is re-established within a few seconds, your other sessions help load-balance traffic.
48
49
49
50
> [!NOTE]
50
51
> 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 shows the identifier of a device or filesystem, and states it entered the All Paths Down state.
0 commit comments