Showing posts with label DRS. Show all posts
Showing posts with label DRS. Show all posts

Saturday, August 23, 2008

Resolution - ESX hosts unexpected disconnect from Virtual Center ( ESX 3.5 update 2 )

When I try to log in to my virtual center to verify my VM farm today, the virtual center show my ESX host had been disconnected from the virtual center by itself. The ESX host itself should be running in critical mode as production and had HA and DRS enable on the cluster. The 1st thing I try to verify is to ensure all my VM and the ESX host is still in production mode, and yes, all the VM is not been down and it still run as normal while it disconnected.

Here is what I did to reconfigure my ESX host and re-join it back to the HA and DRS cluster in my production farm.

Disable the HA and DRS features from the cluster, and totally remove the ESX host from the inventory on Virtual Center server. Follow by that, I SSH in to the ESX host with su -, then I path to the /etc/init.d and look for the services mgmt-vmware status command

It show the services is running. Then I issue the command services mgmt-vmware restart. This will take couple of minutes to get the service fully restarted. At the same time I had actually Remote log on to 1 of the VM to ensure no impact on the VM guest which sit on the ESX host. The result is perfectly work without any downtime on the VM guests, and should credit to the ability from VMware technology.

Once the services restarted, you can easily add host to the virtual center and reconfigure the HA and DRS cluster mode again. The ESX host is back to normal now and work perfectly as usual.

Monday, August 18, 2008

High Availability (HA) and DRS in ESX

The HA and DRS features become an important and a must for enterprise usage in production. For the latest updated patch release from VMware, you will realize some changes had been made in the way the HA communicated.

there is an incident for myself that the HA keep disconnect and reconnect automatically for every couple of minutes. The work around is you need to make sure the hostname that you configure for your esx server is still with lower case or upper cases. If you do have mix environment with upper case and lower case in the physical cluster for ESX, you will experience this technical issue due to the way of the HA communication had been tie to the DNS name. In linux, case sensitive is always apply

For DRS, is not recommend to configure to aggressive level as during the vmotion, it do generate the overhead and network traffic for vmkernel port for both original host and destination host. 1 of the test I had done previously, I Vmotion 20 VM to another host in 1 time, and I do face the CPU bottleneck which stop the vmotion activity. Advice here is to Vmotion 1 by 1 if you are not in rush as it will generate less overhead for the vmotion activity and of course higher success rate.
 
Site Meter