Process to disconnect ESX host from vCenter with DVSwitch

Posted on September 8th, 2010 in Tips, vCenter, Virtualization | No Comments »

It been quite some times I did not migrate the ESX host from 1 vCenter to another. For most of the deployment recently, we were either deploy our vSphere 4 with DVswitch or Nexus 1000V from Cisco. Here are some steps you may want to consider when you migrate the ESX host from 1 vCenter to another if you are using DVswitch. Usually we can disconnect the ESX host from vCenter and remove it from inventory, and reconnect to the new vCenter. If you are follow this way for standard vSwitch, it shouldn’t cause you any problem, but if you deploy this way for the environment which using DVswitch, the new vCenter will give you error which shown the previous DVswitch record are still tie to the ESX host on a different vCenter. Do not get panic as the Network connectivity are still working as usual, but you will not able to connect the ESX host to the new DVSwitch.

Read more »

Storage vMotion with VAAI on EMC

Posted on August 16th, 2010 in Storage, Tips, vCenter, Virtualization, vSphere | No Comments »

In 1 of the demo video, I had seen the storage vMotion performance significant improve as much as 25% of the time and reduce the storage processor overhead at roughly 20% which offload the ESX performance during the storage vMotion execution. Previously, you may aware that the storage vMotion will usually take a long time and consume a lot of resource from Host & Storage. With vStorage API Array Integration, you will able to offload this to the storage array to handle directly which reduce the system overhead from ESX host itself.

Here is the option to turn on or off the VAAI, Value of Zero meant off, and 1 refer to ON.

Read more »

VMware VMFS Versioning

Posted on August 4th, 2010 in Tips, vSphere | No Comments »

VMware VMFS VMware VMFS (Virtual Machine File System) is VMware, Inc.’s cluster file system designed for VMware Infrastructure or VMware vSphere. Basically VMFS used to store virtual machine disk images, including snapshots.

According to Wikipedia,

  • VMFS version 1 was used by ESX Server v1.x, which is no longer sold. It didn’t feature the cluster filesystem properties and was used only by a single server at a time. VMFS1 is a flat filesystem with no directory structure. — Officially named “VMware File System”
  • VMFS version 2 is used by ESX Server v2.x and (in a limited capacity) v3.x. VMFS2 is a flat filesystem with no directory structure. — Officially named “VMware File System”
  • VMFS version 3 is used by ESX Server v3.x and vSphere (4.x). As a most noticeable feature, it introduced directory structure in the filesystem. Older versions of ESX Server cannot read or write VMFS3 volumes. Beginning from ESX 3 and VMFS3, virtual machine configuration files are stored in the VMFS partition by default. — Officially named “VMware Virtual Machine File System”

In order to know the exact VMFS version number, see below:
Read more »

Windows 2008 R2 officially supported on vCenter 4.1

Posted on July 14th, 2010 in Announcement, Tips, vCenter, vSphere | No Comments »

With the VMware vSphere 4.1 release, VMware had officially supported the Windows 2008 R2 with the latest release of the official document. It had taken such a long period for VMWare to officially announce in the compatibility matrix documentation.

Please find the full information from here.

Read more »

Surprise Finding on ESX Host after SAN switch outage

Posted on July 1st, 2010 in Server, Storage, Virtualization, vSphere | 2 Comments »

I was busy setup the demo solution for the Cisco summit yesterday. The Demo we had were displaying the VMware, Cisco UCS, Nexus 5000, MDS 9124 & Netapp Storage Solution. 1 of the Surprise thing happened during the setup, which the power source for our MDS 9124 had been tripped during the installation yesterday. In this scenerio, all our connection to ESX host and VM were disconnected. It took us for 25 mins to recovered the power failure and the MDS Switch was back on line after that. I was thought to reboot all the ESX host as we are performing BOOT FROM SAN for all the ESX hosts that we setup. Surprise happened here, which I found all the ESX host were still continue running. I did the command uptime and check the system uptime from vcenter, it showed that the ESX host were not rebooted during the SAN connection drop from UCS to our Netapp FAS storage.

I further checked the virtual machines been power on in the ESX servers, which show all the VM were continue running without system crash or rebooted. Now I realize that the failure on SAN switch may not necessary result system crash or hung, in fact it may allow you resume the system state once the SAN switch are back online, of course, this is no guarantee assumption, just some surprise finding experienced yesterday would like to share here. Read more »