Blog: vCenter

You should avoid using the same LUN on more than one VMware vCenter environments. If this rule is not followed, deleting a datastore from one vCenter will cause it to appear as "dead" on the other vCenter when using the following command: esxcli storage core device list [more]

If a rescan HBA's is performed at this point, all management tools may become unresponsive.  To avoid this, the LUN needs to be marked as disabled, rescanned, then removed from the disabled list:

  1.   esxcli storage core device set -steate=off -d <NAA ID> (whatever the worldwide name is for that LUN)
  2. rescan HBA's 
  3. esxcli storage core device detached remove -d <NAA ID>

If everything is already unresponsive, "localcli" may be substituted for "esxcli."


Here are some items to consider when upgrading to vSphere/vCenter 4.1:

  1. vCenter 4.1 requires a 64-bit OS.
  2. Windows 2008 R2 is now officially supported with vSphere 4.1.
  3. When asked what account to use for the service, the local system option was greyed out.  I had to enter my current credentials, then go back after the installation completed and change the service account to local system.
  4. The Update Manager can upgrade VM hosts.  I had to get the hosts up to version 4.0 before it would work, though.