David Hill

I now have an updated VMware Home Lab, which you can read by clicking here. Here is my VMware Home Lab. People have been asking me to write about what I use in my VMware home lab that I use for a while. Finally one Saturday night, I have had the chance. Lets start off and talk about the physical hardware in my lab. 1 x HP ML115 G5 – Quad Core AMD Opteron 8GB RAM 2 x 256GB HD – RAID 1 2GB USB 2 x 1GB NIC 1 x 1GB On-board NIC 2 x HP Microserver N54L – 2.2Ghz 16GB RAM 4 x 256GB HD – RAID 5 2GB USB 2 x 1GB NIC 1 x 1GB On-board NIC 1 x Iomega PX4 2 x 1GB NIC 4 x 2TB HD – RAID 10 1 x Buffalo Linkstation Duo 2 x 500GB HD – Raid 1 2 x […]

This is a script I wrote a while ago to enumerate network adapters Powershell (PowerCLI) and add the total amount to a variable. I thought some people may find it useful. enumerate network adapters Powershell What I am achieving here is actually enumerating (count) the number of vmnic’s in a host. Why? Well if you think about automating your ESXi deployment, not all physical hosts have the same configurations, some have 4 1GB Nic’s others have 2 10GB nics, however you want to have a standard build for all configurations. This is an easy way to be able to automatically create the portgroups required without having to change your builds for different configurations. The script below shows how you can easily count the total number of vmnics and add to the variable no_nics. [powershell] $no_nics = get-vmhostnetworkadapter -Physical ##Sets Physical NIC count to -1 to match VMware NIC names, eg, […]

Deploying a new VMware vCenter Virtual Appliance today, I received the error ” Failed to communicate with the vCenter Single Sign On server https://xxx.xxx.xxx.xxx:7444…. ” This error has the same resolution as my previous article Failed to connect to VMware Lookup Service Failed to communicate with the vCenter Single Sign on server   Now the issue I have found with both of these problems, is after the first power on, the appliance does an automatic configuration, including assigning a DHCP IP address.  If you then re-configure the appliance and chang the hostname or IP address of the vCenter Virtual Appliance.  The certificate that was created on initial configuration is no longer valid.  To resolve this issue, follow the steps below: Login into vCenter VA Configuration https://[hostname/IP]:5480 Select the Admin tab Click Toggle certificate setting, you will see Certificate regeneration enabled change to Yes. Re-boot the Virtual Appliance During the bootup procedure […]