Recently, I have upgraded my homelab – yet again. There will be an oncoming post about the hardware I chose and how it is set up. This time, my lab is mobile. I can take it with me on the road or leave it at home. One of the features that I wanted to be able to capture and utilize
I was onsite this past weekend doing a vSphere 5.1 turnkey install. The turnkey consisted of a C7000 Blade Chassis, and two ESXi 5.1U3 hosts. With this new installation, the customer was adding to a new 10Gbe environment to his network. There were also a few settings that needed to be made, specifically, disabling Flow Control on the ESXi Hosts
Recently, I had to install ESXi 4.1 on an IBM x3850 X5. Once the install was completed and I started configuring the host, I noticed something odd. I had a new vswitch and a network adapter that was defined as vusb0. WTF? At first, I thought I was imagining things. I opened the network adapters view, and sure enough there
I ran into a new situation. Here’s the setup, I’m at a customer’s location performing a migration of VMs from one SAN array to another (svmotion). Ok, Not that hard – not really. As soon as you let your guard down — even on the simplest of things, that’s when you get bit by something or you discover a new
Last week I had performed a semi-automatic (scripted) turn key installation. Before going out to the customer site, I had set the install script to set the SATP and the PSP for an Equallogic Array (SATP = VMW_SATP_EQL, PSP = DELL_PSP_EQL_ROUTED) during the installation. Unfortunately, I found out after the fact, that they had a Compellent Array. Because of this,