WilliamLam.com

Automating the vSAN Data Migration Pre-check using vSAN API

by // Leave a Comment

I was chatting with a customer yesterday on various automation topics and one of the questions was about automating the vSAN Data Migration Pre-Check capablitity, which is available in the vSphere UI under vSAN Cluster->Monitor->vSAN->Data Migration Pre-check as shown in the screenshot below.


The specific vSAN API that you will need to use is both the VsanPerformResourceCheck to perform the operation and then VsanGetResourceCheckStatus to retrieve the results as the operation can take some time depending on the size of your environment.

[Read more...]

Programmatically accessing the Broadcom Compatibility Guide (BCG)

by // 1 Comment

The Broadcom Compatibility Guide (formerly VMware Compatibility Guide) is where users would go to check hardware (new or existing) compatibility with VMware software.


There are a number of different compatibility guides that you can search through from CPU processors to servers to the various of I/O devices including accelerators and graphics cards. For users with a small number of hardware devices, search is pretty straight forward but if you have a variety of different hardware to check, the web interface may not be the quickest.

One thing that I was pleasantly surprised to learn was that the Broadcom Compatibility Guide (BCG) could easily be consumed programmatically, unlike the previous VMware Compatibility Guide (VCG) which had a different backend system.

While there is not an official BCG API, which would include documentation, support and backwards compatibility, users can interact with the BCG using the same API as the BCG web interface.

[Read more...]

Enable TRIM/UNMAP from Nested vSAN OSA/ESA to physical vSAN OSA

by // Leave a Comment

If you are running Nested vSAN Original Storage Architecture (OSA) or vSAN Express Storage Architecture (ESA) workloads on top of a physical vSAN OSA setup, you may want to enable the Guest TRIM/UNAMP capability, which would allow your the "inner" (Nested) workloads to pass the TRIM/UNMAP requests down into your physical vSAN OSA deployment for space reclamation.

It was recently observed that storage utilization may continue to increase on a physical vSAN OSA setup even when the Nested vSAN ESA/OSA workloads have already freed up their storage, which is due to the fact that the TRIM/UNAMP commands are not being passed down into the physical vSAN OSA. If you are using vSAN ESA for your physical setup, Guest TRIM/UNMAP is already enabled by default, so this is only applicable if you are using vSAN OSA.

To enable the Guest TRIM/UNMAP capability, you need apply the following ESXi Advanced Setting to your physical vSAN OSA.

[Read more...]