When I added an extra SCSI card to my ESX 3.5 test system I could not get it to reconnect again with VirtualCenter. After a close inspection I noticed that vmnic0 did not exist anymore(esxcfg-nics -l), it got renamed to vmnic1. Because of that my vSwitch0 did not have a NIC linked to it anymore. I linked the new vmnic1 [...]

The last couple of weeks more blogs and topics appeared around the warning VirtualCenter gives when there’s no service console redundancy. Several people posted about a workaround to clear this warning. The workaround is very easy: temporarily assign an additional nic to the service console vSwitch and reconfigure your HA. Notice that I used ” workaround” cause I definitely don’t [...]

When live migrating from ESX 3.0.2 to ESX 3.5 VMware gives an error:”Migration will cause the virtual machine’s configuration to be modified, to preserve the CPU feature requirements for its guest OS.” This error indicates that the .vmx file is about to be changed.

VMware updated the PDF about High Availability with extra advanced options for ESX 3.5/VC 2.5. They’ve also added recommendations for additional Service Console redundancy. Until now I’ve always worked with a two nic based Service Console instead of a second Service Console on the VMKernel network, will test with the second Service Console to see if it works like expected… [...]

An often made mistake when trying to open up or close a port range with the ESX(3.0.2 and 3.5) firewall is using the dash(-) as a divider. Using the dash unfortunately does not always result in an error. To open up or close a port range you should use a collon(:) as a divider: esxcfg-firewall –openport 6000:6010,tcp,in,test