After Hewlett Packard Enterprise has missed offering a Microserver in their 9th Generation, it is now back in Gen10. The Microserver series provides affordable servers intended to be used in SMB and as home servers. Due to its low price and power consumption, you can find this system in many virtualization home labs as ESXi hosts or Storages.

The HPE ProLiant MicroServer Gen10 is available with two different CPUs - AMD Opteron X3216 and X3421. Both models a SoC which means that the CPU cannot be changed like the Intel CPUs in Gen8. They support up to 32GB of unbuffered DDR RAM. The server can be equipped with 4 hard drive from the front.

The Get-VMLatencySensitivity, Get-VMLatencySensitivityBulk and Set-VMLatencySensitivity PowerShell functions configure can return and set the latency sensitivity level of a virtual machine. You can adjust the latency sensitivity of a virtual machine to optimize the scheduling delay for latency sensitive applications.

The function is part of my Virten.net.VimAutomation module, which is a set of PowerShell function built for managing, troubleshooting and automating VMware based platforms. The module can be easily obtained from the PowerShell Gallery and is available on GitHub.

VMware has released a critical patch for vSAN 6.0 and 6.5. This patch contains a fix for a highly critical vSAN issue that might cause IO read errors and in some cases severe symptoms such as inaccessible VMs, host failures, or stuck resyncs. The issue manifests itself only under highly specific operations and IO patterns.

The bug only affects All-Flash vSAN configurations with deduplication enabled.

Symptoms for this issues are the following messages in the Events tab:

"vSAN detected an unrecoverable medium or checksum error for component uuid on disk group uuid."

"vSAN detected and fixed a medium or checksum error for component uuid on disk group uuid."

The Get-VMHostVersion and Get-VMHostLatestVersion PowerShell functions are aimed at helping you to identify the version at which your ESXi is currently running, and whether updates are available. Both are using a JSON based ESXi Build database which is also the backend for the ESXi Build Number History provided by virten.net.

The function is part of my Virten.net.VimAutomation module, which is a set of PowerShell function built for managing, troubleshooting and automating VMware based platforms. The module can be easily obtained from the PowerShell Gallery and is available on GitHub.

The Convert-ScsiCode PowerShell function decodes SCSI sense codes found in the vmkernel.log from ESXi hosts. It uses a JSON based SCSI Code database provided by virten.net. The function works just like my web-based SCSI Sense Code Decoder but allows you to integrate it in your automation scripts.

The function is part of my Virten.net.VimAutomation module, which is a set of PowerShell function built for managing, troubleshooting and automating VMware based platforms. The module can be easily obtained from the PowerShell Gallery and is available on GitHub.

Whenever I create databases with information like ESXi Versions, vCenter Versions or VMware's HCL I try make these available to be used for automation or in scripts. JSON is my data-type of choice but I figured that another structure might be easier to handle in some circumstances. This is why I've now created separate versions where it is now possible to access the information with keys.

I've added a new feature to my online SCSI Sense Code Decoder. It is now possible to enter the Command that has been reported to be failed into the form. The command is displayed in the error message and can be important for troubleshooting:
The Command can be optionally entered in the form and will be translated:

Another small fix: Previously, Host Status and Sense Key fields were case sensitive and have to be entered in lower case. This requirement has been removed, you can now use lower or upper case letters.

The next feature I'm working on is to make the decoder to work with scripts to allow even better and faster troubleshooting. Any other feature requests are welcome.

I could get my hands on Intel's first 3D XPoint based SSD to figure out how it performs.

3D XPoint is a new non-volatile memory technology that has been developed by Intel and Micron.

With 32GB, it doesn't make sense to buy them for anything else than their intended use case: Cache device to enhance SSD/HDD Performance. If you want to use Optane technology as VM Datastore, wait a couple of months when devices with a higher capacity are available.