VCenter Installation Error 28038
Posted on November 3rd, 2009 in Tips, vCenter | No Comments »
I’m getting an “error message: 28038″ just before the VMware VCenter Server installation end as screen shot below:
Workaround:
Read more »
vCenter 4.0 patch 1
Posted on August 23rd, 2009 in Virtualization | No Comments »
You experience these symptoms:
- In vCenter 4.0, VMware HA might not failover virtual machines when a host failure occurs.
- When the ESX host’s IP address in a VMware HA enabled cluster is configured with certain IP addresses, the node failure detection algorithm fails.
- You are susceptible to this issue when all of your Service Console Port(s) or Management Network IP address(s) on your ESX host fall within the following range:
3.x.x.x – 9.x.x.x
26.x.x.x – 99.x.x.x
Note: You are not affected if one of Service Console Port(s) or Management Network IP address(s) on your ESX host falls outside of this range.
vCenter 4.0 patch 1 will help to fix this issue.
mgmt-vmware service malfunction
Posted on July 8th, 2009 in Tips, vCenter, vSphere | No Comments »
Most of us may had previously experienced a VM which hung in the ESX hosts. Usually we will use the command vmware-cmd utilities to kill or stop the virtual machine. Sometimes we even need to use the vm-support command to force the VM to be stop hardly if vmware-cmd was not worked. Today I found some interesting issue with 1 of the virtual machine. I had executed the instruction to power off from vCenter 4. This virtual machine is running on vsphere 4. After 2 minutes, the virtual machine still showed power on from the vCenter, and I executed again the 2nd command to power off, the system prompted that another process was in progress, and access was denied.
VMotion compatible from ESX 3.5 to vSphere 4
Posted on June 4th, 2009 in Tips, Virtualization, vCenter, vSphere | 1 Comment »
I am currently doing some test to simulate the real update requirement for my production VMware Farm to be upgraded from ESX 3.5 to vSphere 4. To minimize the impact to our production system, we may want to do this with as minimal impact as possible. Due to the virtual hardware version and tools upgrade require, is pretty tough for us to perform the entire upgrade at 1 time. Therefore, our plan is get the host upgraded and follow by each individual virtual machine to be upgraded follow the suitable timing for different business unit. HA and DRS will need to be disable temp during the ESX upgrade.
I am able to get the ESX 3.5 to be manage by the latest vcenter. A vmotion from ESX 3.5 to vsphere 4 had been successes too, but the latest version of virtual machine which built from vSphere 4 might not compatible to vmotion back to the ESX 3.5 hosts. At the same time, if you have different processors chipset in the environment and require EVC to be turned on, it may be a little challenge to do so. You may want to ensure the EVC to be done with no down time. You may need to refer to my previous post about how to enable EVC with no down time.
New experience on vCenter 4
Posted on May 23rd, 2009 in Tips, Virtualization, vCenter, vSphere | 1 Comment »
I just got the official release of vSphere 4 today and finally got it work on my test lab. 1st thing before I upgraded my ESX servers is I need to upgrade my vCenter. If you are running RC now, you may not able to manage the official release vSphere 4 host by RC version of vCenter you had. I reinstall fresh for my vCenter 4 on Windows 2003. Since is a test lab, I do not build the DB on SQL Server as I did for production. I am using the default sql express as part of the installation.The installation process will not be much different compare to RC, but the resource utilization of the vCenter 4 will make the different.
