I first wrote about the tiny palm size iKOOLCORE R1 back in Spring of this year, I was pretty impressed at how capable the R1 was, especially given the tiny footprint that is slightly taller than a Lego minifigure!
It has not even been a full year since the release of the R1 and the second generation of the R-Series is now available, not surprisingly dubbed the R2.
To deploy VMware Cloud Foundation (VCF), your physical or virtual ESXi host must have at least two network adaptors to be able to migrate to Distributed Virtual Switch (VDS), which is configured as part of the VCF Bringup process. While you can technically migrate to a VDS with just a single network adaptor using this trick, it is definitely easier if you have a system that meets this basic requirement.
Earlier this year, I demonstrated that you can deploy VCF using just an Intel NUC with only 64GB of memory, which would be the minimum to run single node VCF Management Domain, however it does not leave you with much room for running other workloads due to pushing the memory limits.
The ASUS PN64-E1 is currently one of my top favorite small form factor kits, especially being able to support up 96GB of memory using the new non-binary DDR5 memory modules. After the release of VCF 5.1, I wanted to use the ASUS PN64-E1 for a VCF deployment, but there was only one problem ... my particular configuration of the PN64-E1 only had a single network adaptor!
I thought I could out smart the VCF Bringup pre-check by using a USB network adaptor and installing the popular USB Network Native Driver for ESXi 😉
However, it turns out the pre-check is looking for PCIe-based network adaptors, so while the system does have two network adaptors, it still failed the pre-check and prevented the deployment from continuing. I ended up reaching out some of the VCF Engineers to see if there were any workarounds and he was kind enough to provide me with a nice workaround that would benefit our users looking to play and explore VCF in a lab environment.
Disclaimer: This is not officially supported by Broadcom, use at your own risk.
I recently shared on how you can deploy the latest VMware Cloud Foundation (VCF) 5.1 release with vSAN Express Storage Architecture (ESA) using Nested ESXi and leveraging a custom vSAN ESA HCL JSON file, which I had created to workaround the required vSAN ESA pre-check during the VCF Bringup process.
I will admit, I actually did not the create the custom vSAN ESA HCL JSON file manually, it was auto-generated using automation 😉
My initial goal was to make it easier for anyone to play with VCF 5.1 using both Nested ESXi as well any physical system that is capable but may is not on the official VMware vSAN ESA HCL. After a lot of trial and error testing with Nested ESXi, I finally had a functional PowerCLI script that can then be used to run against a standalone ESXi host to dynamically generate a compatible custom vSAN ESA HCL JSON file that can then be used with both VCF 5.1 with vSAN ESA or even a standalone vCenter Server deployment for vSAN ESA enablement.