WilliamLam.com

Considerations for future vSphere Homelabs due to upcoming removal of SD card/USB support for ESXi

by // 16 Comments

In case you have not heard the news, VMware had recently published a new knowledge base article (KB 85685) outlining details for the future removal of SD card/USB as a standalone boot device for ESXi.

If you have not read the KB, please take a few minutes and carefully read the article, especially as you think about future hardware upgrades and purchases.

There has certainly been no shortage of discussions and debates since the publishing of the VMware KB. One topic that I know many of you have been wondering and asking about is what is the impact to vSphere Homelabs? This was something that had already crossed my mind after I first read the KB and I was thinking about this a bit more this week and specifically some of the potential options that are available to customers right now but also some of the considerations you may want to account for in with future homelab upgrades.

Disclaimer: These are my own personal opinions and do not reflect any official guidance or recommendations from VMware.

[Read more...]

Quick Tip - How to deploy NSX Advanced Load Balancer (NSX-ALB) with a single Service Engine

by // 1 Comment

I saw an interesting question today from Robert Kloosterhuis in the private vExpert App Modernization Slack Channel who working with vSphere with Tanzu using NSX Advanced Load Balancer (NSX-ALB) and wanted to know if it was possible to deploy NSX-ALB with just a single Service Engine (SE)?

The default behavior of NSX-ALB is to deploy two SE for availability purpose but for testing and/or homelab usage, it could certainly help with resources and time to spin up an environment using NSX-ALB. I was also curious if this was possible and reached out to NSX-ALB Engineering team and within a few minutes, I got a response that not only was this possible to do but pretty easy to configure.

To modify this default behavior, we need to update the Service Engine group prior to SE VMs being deployed. To do so, login to NSX-ALB UI and under Infrastructure->Service Engine Group and then click on the Advanced tab and change the default Buffer Service Engines value of 1 to 0 which will will have NSX-ALB deploy just a single SE VM rather than the default two.


To confirm that our NSX-ALB have been configured correctly, I have enabled vSphere with Tanzu using NSX-ALB and as you can see from the screenshot below, only a single SE VM has been deployed rather than the default behavior of two SE.

ESXi on SimplyNUC Ruby and Topaz

by // 5 Comments


Ruby and Topaz is the latest in SimplyNUC's custom lineup of NUC-like systems which they started to build and sell a couple of years ago. The Ruby platform is based on the AMD Ryzen 4000 Series and the Topaz platform is based on Intel 11th Gen Tiger Lake Series.

Given the current global chip shortage that may last a couple more years, it may take some time before everyone can get their hands on either of these platforms, but I have slowly been seeing new inquiries about these platforms as folks are starting to receive their units. Of course, the most popular inquiry that I have received is whether these systems can be used with ESXi? 😀

Topaz

Since Topaz uses the same Intel 11th Gen Tiger Lake CPU, it works exactly the same as the Intel NUC 11 Performance (Panther Canyon) and Intel NUC 11 Pro (Tiger Canyon), which requires the Community Networking Driver for ESXi to enable both the 2.5GbE and 1GbE onboard network adapters when installing ESXi on Topaz. One really nice feature of Topaz is that all three models (i7, i5 and i3) include dual onboard network adapters, where as this option is only available on Intel NUC 11 Pro as an add-on card that must be purchased separately.

Here is screenshot of the latest ESXi 7.0 Update 2 release running on Topaz

Ruby

Although there was quite a bit of community interests in running ESXi on the Ruby platform, I was not particularly optimistic mainly because both the onboard network adapters are from Realtek. Since there are no ESXi networking drivers from Realtek, ESXi would not be able to detect either of the network adapters which is the same behavior that I have seen for other AMD-NUC like kits such as the ASRock Gen 1 and Gen 2 systems.

Unfortunately, there has been no progress with Realtek joining VMware's I/O Vendor Partner (IOVP), which would enable the development of an official network driver for ESXi. Although folks can add networking to these platforms leveraging the USB Network Native Driver for ESXi, it is less than ideal. At this point in time, I can not recommend Ruby or other AMD-based NUCs that uses Realtek-based network adapters.

Here is screenshot of ESXi 7.0 with USB network adapter running on Ruby