Increase vSphere Lifecycle Manager (LCM) and vSphere Update Manager (VUM) log levels

Products

• VMware vSphere ESXi

Issue/Introduction

On rare occasions it may be necessary to increase the default logging level of vSphere Lifecycle Manager (vLCM) or vSphere Update Manager (VUM) to troubleshoot an issue.

Symptoms:

• Default logging levels may not provide enough detail to determine the cause of an issue.

Environment

VMware vCenter Server 

Resolution

Changes should only be in place long enough to capture the necessary logging then reverted back to default once troubleshooting is complete. 

The vLCM/VUM service consists of multiple subcomponents and has the ability to granularly increase log levels for specific components.  This is accomplished  by editing the /usr/lib/vmware-updatemgr/bin/vci-integrity.xml on the VCSA

   1.  Stop the vmware-updatemgr service
              service-control --stop  vmware-updatemgr
  
   2.  Make a backup of the original vci-integrity.xml file

             cp /usr/lib/vmware-updatemgr/bin/vci-integrity.xml /usr/lib/vmware-updatemgr/bin/vci-integrity.orig

   3.  Modify the logLevel of the component(s) necessary (see list below)  

   4.  Save file

   5.  Start the vmware-updatemgr service

              service-control --start vmware-updatemgr
 

Example:
Change the <logLevel> of the HostUpgrade component from verbose -> trivia

Some components that may be helpful based on the operation being investigated

Upgrades/Patching
   HostUpgrade
  HostUpgradeMetadata
  HostUpgradeRemediate
  SingleHostRemediateTask
  VciRemediateTask

Scanning
  SingleHostScanTask​
  SingleLinuxScanTask​
  SingleOnlineScanTask​
  SingleOfflineScanTask​
  VciScanTask

Service/Misc
 ConfigurationMgr​
 DownloadMgr​
 InternalScheduledTasksMgr​
 JobDispatcher​
 ScheduledTaskMgr​
 SessionMgr​
 VcIntegrity​
 VcTaskMonitor