Skip to content

Commit 6ec38b4

Browse files
JLansdaalroygara
andauthored
Update articles/azure-vmware/configure-azure-elastic-san.md
Co-authored-by: rogara <[email protected]>
1 parent 3999f3e commit 6ec38b4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-vmware/configure-azure-elastic-san.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ You should use multiple private endpoints to establish multiple sessions between
6969
> [!NOTE]
7070
> 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.
7171
72-
Each private endpoint will provide 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.
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.
7373

7474
> [!IMPORTANT]
7575
> 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.

0 commit comments

Comments
 (0)