Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

After Upgrading From VMware vCenter Lab Manager 4.0.0.1140, Unable to Upgrade Agent if VMs are Using Host Spanning. (1023159)

Details

If you have virtual machines deployed in cross-host fenced mode, after you upgrade from vCenter Lab Manager 4.0.0.1140, you will see the following
  • When you try to upgrade the agent using the Upgrade Agent option, the error message The following virtual machines deployed on this host require Host Spanning. In order to disable Host Spanning on this Host you must first undeploy these virtual machines:XYZ, ABC appears.
Additionally, when you undeploy all the virtual machines, the error message The agent running on host XYZ is not compatible, pending upgrade. appears.
  • When you try to manually uninstall the old agent, the error message vmkload_mod: Can not remove module vsla-fence: module symbols in use. appears.

Solution

You can use one of the following solutions: 

 Solution #1
-----------------
You must undeploy cross-host fenced configurations so that the agent upgrade can continue the upgrade process:

  1. Stop the monitoring service.
  2. On the Lab Manager machine, run the following command and restart the monitoring service:
    osql -E -S localhost\LabManager -d LabManager –Q "UPDATE ManagedServer SET agent_interface_version = 2"
  3. Undeploy all cross-host fenced configurations.
  4. Stop the monitoring service.
  5. On the Lab Manager database, run the following command and restart the monitoring service:
    osql -E -S localhost\LabManager -d LabManager –Q "UPDATE ManagedServer SET agent_interface_version = 1"
  6. Upgrade Lab Manager agent on all the hosts using the Upgrade Agent menu option.

Solution #2
-----------------
This solution allows zero downtime by taking advantage of the vMotion feature of VMware ESX.

  1. Disable DRS if it is enabled on the cluster, it must be disabled before proceeding. You can enable it again after you upgrade the agents.

    Note: Ensure that Lab Manager is using the cluster as the resource pool before disabling DRS. For additional information relating to disabling DRS, see page 85 of the vSphere Resource Management Guide
  2. Stop the monitoring service, and on the Lab Manager machine, run the following command:
    osql -E -S localhost\LabManager -d LabManager –Q "UPDATE ManagedServer
    SET agent_interface_version = 2"
  3. Restart the monitoring service.
  4. In VMware vCenter, select an ESX host and vMotion off all the VMs on it (except the Lab Manager Service VM) to other hosts.
  5. In vCenter Lab Manager, upgrade the agent on this host.
  6. Repeat steps 4 and 5 for every ESX host.

In step #4, you need to vMotion ideally only cross-host fenced configuration virtual machines and their vRouters. However, it may not be easy to determine which virtual machines are cross-host fenced and the vRouters that belong to those fenced configurations.

Alert: You must back up your database before you make any changes.

Keywords

VMware vCenter Lab Manager 4.0

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 2 Ratings
Actions
KB: