Skip to content

Commit a639e00

Browse files
committed
Learn Editor: Update configure-vsan-esa.md
1 parent c9a8abc commit a639e00

File tree

1 file changed

+10
-15
lines changed

1 file changed

+10
-15
lines changed

articles/azure-vmware/configure-vsan-esa.md

Lines changed: 10 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -38,17 +38,13 @@ __Set VMware vSAN TRIM/UNMAP__
3838

3939
Guest Trim/Unmap is enabled by default and cannot be disabled for cluster with vSAN ESA. Run command Set-AVSVSANClusterUNMAPTRIM is not applicable for vSAN ESA based clusters.
4040

41-
__Note__
41+
>[!NOTE]
42+
>Run commands are executed one at a time in the order submitted.
4243
43-
Run commands are executed one at a time in the order submitted.
44-
45-
__Note__
46-
47-
vSAN TRIM/UNMAP is enabled by default on vSAN ESA based clusters. To disable UNMAP at the VM level, the following additional requirements are needed for it to function as intended.
48-
49-
- All VMs in vSAN ESA cluster(s) are set by default to use UNMAP inherited from the cluster level. UNMAP can be disabled using the disk.scsiUnmapAllowed flag with a value of 'false' at the virtual machine level, should you wish to disable this behavior on a per-VM basis. VMX file changes require a reboot to take effect.
50-
51-
- The guest operating system must be able to identify the virtual disk as thin.
44+
>[!NOTE]
45+
>vSAN TRIM/UNMAP is enabled by default on vSAN ESA based clusters. To disable UNMAP at the VM level, the following additional requirements are needed for it to function as intended.
46+
>- All VMs in vSAN ESA cluster(s) are set by default to use UNMAP inherited from the cluster level. UNMAP can be disabled using the disk.scsiUnmapAllowed flag with a value of 'false' at the virtual machine level, should you wish to disable this behavior on a per-VM basis. VMX file changes require a reboot to take effect.
47+
>- The guest operating system must be able to identify the virtual disk as thin.
5248
5349
__Set VMware vSAN Space Efficiency__
5450

@@ -58,9 +54,8 @@ __Set VMware vSAN Data-In-Transit Encryption__
5854

5955
Run the Set-vSANDataInTransitEncryption cmdlet to enable or disable data-in-transit encryption for all clusters or specified clusters of a SDDC.
6056

61-
__Note__
62-
63-
Changing this setting will cause a performance impact. See [VMware KB](https://blogs.vmware.com/virtualblocks/2021/08/12/storageminute-vsan-data-encryption-performance/).
57+
>[!NOTE]
58+
>Changing this setting will cause a performance impact. See [VMware KB](https://blogs.vmware.com/virtualblocks/2021/08/12/storageminute-vsan-data-encryption-performance/).
6459
6560
1. Sign in to the [Azure portal](https://portal.azure.com/).
6661

@@ -80,11 +75,11 @@ comma separated list of names.|
8075

8176
1. Check Notifications to see the progress.
8277

83-
__Note__
78+
>[!NOTE]
8479
8580
You can also use the Get-vSANDataInTransitEncryptionStatus command to check for the current status or status after performing the Set-vSANDataInTransitEncryptionStatus operation and verify the cluster's current encryption state.
8681

87-
__Next steps__
82+
>[!NOTE]
8883
8984
Now that you learned how to configure VMware vSAN, learn more about:
9085

0 commit comments

Comments
 (0)