I have to confess that I have always thought of NFS for vSphere as being a second-tier choice. Even the best solutions from well known vendors using 10GbE and SSD, NFS datastores always seem to under-perform and be more problematic as compared to block-storage SAN devices. Even with the theoretical reduction of overhead per payload (per Ethernet Frame), I’ve never found an enterprise NFS device that I wouldn’t gladly trade for a block-storage SAN when used for vSphere-specific applications. Continue reading
In an ideal world, management would provide unlimited funding to upgrade hardware continuously! We all know that’s not going to happen! Sometimes it is necessary to prolong the lifespan of servers as long as possible, particularly when they are extremely well-provisioned devices, even by today’s standards!
Such is the case with our HP BL460 G7 Blades. They are each equipped with a dual-port 10Gb onboard NIC adapter (Emulex HP NC553i) and a dual-port Mezzanine NIC adapter (Emulex HP NC551m), rendering a total of four 10Gb ports.
Recently, after running HP Service Pack for Proliant (SPP), we lost network connectivity to the Emulex HP NC551m adapter. It wasn’t simply that no network traffic was being passed, but rather the entire adapter disappeared from the configuration in ESXi 6, and the adapters were not visible using the SSH CLI command: esxcli network nic list It’s as if the NC551m adapter simply wasn’t there! Continue reading
I was designing a customer vSAN deployment and I came across the guidelines and formula for calculating the required ESXi Coredump partition size: https://kb.vmware.com/s/article/2147881
Right away, I started working the formula for my customers deployment, when it occurred to me; this is WAY more complicated than it needs to be!
VMware actually wants you to take a number (the size of SSD in GB), divide by 100, multiply by 0.181 and then multiply by 0.25. Ridiculous!
- Why not just multiply by 0.0045, it is exactly the same thing!
For years, I have dismissed Virtual Machine Hardware version as unimportant. In fact, in this very blog, I may have advocated for leaving VM Hardware Version set at 8, to maintain full compatibility with both the vSphere C# Client and the vSphere Web Client.
Unfortunately, thanks to Spectre and Meltdown, things have changed. Updating your VM Hardware Version also updates the VM BIOS, and that’s an important part in the remediation of Speculative Execution Vulnerabilities, specifically: CVE-2017-5715 ‘Spectre Variant 2’. Continue reading
Many people are under the incorrect belief that it is hardware-level firmware updates from companies like HPE and Dell that will protect our Virtual Machines from Speculative Execution Vulnerabilities. This is NOT TRUE.
- As far as your VMs are concerned, the VM BIOS and Hypervisor are the hardware!
As we are all aware, recent updates to Shockwave Flash caused the vSphere Web Client to crash on most browser platforms. The interim solution was to install an outdated version of Shockwave Flash, just to access the Web Client. More recently, Adobe Shockwave Flash version 22.214.171.124 was pushed out in updates to Google Chrome (and other browser platforms) that fixes the problem.
- Gone is the choice between “Allow Flash” and “Ask First,”
- Now there is the choice between “Ask First” and “Block sites from running Flash.”
- What’s new is the ability to add allowed sites, including the use of wildcard characters, where Shockwave Flash will run unprompted.
Over the weekend Google pushed out an update to Flash (126.96.36.199) with an update to Chrome (61.0.3163.100) and now vSphere Web Client is broken once again! Continue reading
Being successful with VMware vSphere is largely about understanding “Who’s on first, What’s on second and Idunno’s on third,” at any given point in time. This is especially true with the VMware vCenter Server Appliance (VCSA), as it presents a several new console choices to the administrator. Continue reading
From time to time, you will find it necessary to transfer files to or from your VMware vCenter Server Appliance (VCSA) or ESXi Servers. If you are working from a Windows desktop or server, there’s no more convenient utility than WinSCP for copying files securely between Windows and Linux Systems.
There are a few issues, however, when it comes to connecting to the VCSA with WinSCP that I will show you how to work around without reconfiguring the default shell of your VCSA! Continue reading
I recently went looking for information on password security for the VCSA 6.0 & 6.5 and ESXi 6.0 & 6.5. Most specifically, I was interest in the number of passwords remembered, so I could define that in documentation for a client.
Try as I might, I couldn’t find documentation for VCSA number of passwords remembered or how to configure it anywhere! Continue reading