WilliamLam.com

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...]

Supported chipsets for the USB Network Native Driver for ESXi Fling

by // 4 Comments

A longtime community favorite, the USB Network Native Driver for ESXi Fling makes it super easy for users to expand additional networking capabilities for ESXi-x86.

While helping a customer recently, I realized that we did not have a published list of supported USB Network adaptors (VID/DID) for the Fling anywhere, especially after transitioning into the Broadcom system post Day 2.

Note: A quick heads up, the Fling downloads will be re-homed to the Broadcom Support Portal (BSP) under the Free Downloads next month. For more details, please see the announcement posted on the Flings Community.

[Read more...]

Quick Tip - Auditing ESXi boot firmware type

by // Leave a Comment

I had a customer that recently reached out asking how they could easily audit their entire ESXi infrastructure to determine which hosts was still booting using the legacy BIOS firmware, which has been deprecated and will be removed in a future vSphere release, in favor of the industry standard UEFI firmware type.

In vSphere 8.0 Update 2, a new vSphere API property called firmwareType was introduced and added to the ESXi Hardware BIOS info object that makes it very simple to retrieve with the following PowerCLI 1-Liner:

(Get-VMHost).ExtensionData.Hardware.BiosInfo

Here is an example output for an ESXi host booting with UEFI firmware:


Here is an example output for an ESXi host booting with BIOS firmware:


Since this vSphere API property was recently introduced in vSphere 8.0 Update 2, if you attempt to use this on an ESXi host that is not running 8.0 Update 2, then you will see the field being blank if you are using a newer release of PowerCLI that understands this new property or it will simply not show if you are using an older version of PowerCLI.


Alternatively, if you still need to retrieve this information, you can go directly to ESXi host via SSH, not ideal but you can use the following VSISH command to retrieve this exact information:

vsish -e get /hardware/firmwareType