<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <style type="text/css">body{background-color:#EEEEEE;}body{background-color:#EEEEEE;}th{font-weight:bold;background-color:#CCCCCC;}td{background-color:white;}</style> </head><body> <table> <colgroup><col/><col/><col/></colgroup> <tr><th>event</th><th>category</th><th>FullFormat</th></tr> <tr><td>ad.event.ImportCertEvent</td><td>info</td><td>ad.event.ImportCertEvent|Import certificate succeeded.</td></tr> <tr><td>ad.event.ImportCertFailedEvent</td><td>error</td><td>ad.event.ImportCertFailedEvent|Import certificate failed.</td></tr> <tr><td>ad.event.JoinDomainEvent</td><td>info</td><td>ad.event.JoinDomainEvent|Join domain succeeded.</td></tr> <tr><td>ad.event.JoinDomainFailedEvent</td><td>error</td><td>ad.event.JoinDomainFailedEvent|Join domain failed.</td></tr> <tr><td>ad.event.LeaveDomainEvent</td><td>info</td><td>ad.event.LeaveDomainEvent|Leave domain succeeded.</td></tr> <tr><td>ad.event.LeaveDomainFailedEvent</td><td>error</td><td>ad.event.LeaveDomainFailedEvent|Leave domain failed.</td></tr> <tr><td>com.vmware.license.AddLicenseEvent</td><td>info</td><td>com.vmware.license.AddLicenseEvent|License {licenseKey} added to VirtualCenter</td></tr> <tr><td>com.vmware.license.AssignLicenseEvent</td><td>info</td><td>com.vmware.license.AssignLicenseEvent|License {licenseKey} assigned to asset {entityName} with id {entityId}</td></tr> <tr><td>com.vmware.license.DLFDownloadFailedEvent</td><td>warning</td><td>com.vmware.license.DLFDownloadFailedEvent|Failed to download license information from the host {hostname} due to {errorReason.@enum.com.vmware.license.DLFDownloadFailedEvent.DLFDownloadFailedReason}</td></tr> <tr><td>com.vmware.license.LicenseAssignFailedEvent</td><td>info</td><td>com.vmware.license.LicenseAssignFailedEvent|License assignment on the host fails. Reasons: {errorMessage.@enum.com.vmware.license.LicenseAssignError}.</td></tr> <tr><td>com.vmware.license.LicenseCapacityExceededEvent</td><td>warning</td><td>com.vmware.license.LicenseCapacityExceededEvent|The current license usage ({currentUsage} {costUnitText}) for {edition} exceeds the license capacity ({capacity} {costUnitText})</td></tr> <tr><td>com.vmware.license.LicenseExpiryEvent</td><td>warning</td><td>com.vmware.license.LicenseExpiryEvent|Your host license expires in {remainingDays} days. The host will disconnect from vCenter Server when its license expires.</td></tr> <tr><td>com.vmware.license.LicenseUserThresholdExceededEvent</td><td>warning</td><td>com.vmware.license.LicenseUserThresholdExceededEvent|The current license usage ({currentUsage} {costUnitText}) for {edition} exceeds the user-defined threshold ({threshold} {costUnitText})</td></tr> <tr><td>com.vmware.license.RemoveLicenseEvent</td><td>info</td><td>com.vmware.license.RemoveLicenseEvent|License {licenseKey} removed from VirtualCenter</td></tr> <tr><td>com.vmware.license.UnassignLicenseEvent</td><td>info</td><td>com.vmware.license.UnassignLicenseEvent|License unassigned from asset {entityName} with id {entityId}</td></tr> <tr><td>com.vmware.vc.HA.AllHostAddrsPingable</td><td>info</td><td>com.vmware.vc.HA.AllHostAddrsPingable|The vSphere HA agent on the host {host.name} in cluster {computeResource.name} in {datacenter.name} can reach all the cluster management addresses</td></tr> <tr><td>com.vmware.vc.HA.AllIsoAddrsPingable</td><td>info</td><td>com.vmware.vc.HA.AllIsoAddrsPingable|All vSphere HA isolation addresses are reachable by host {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.AnsweredVmLockLostQuestionEvent</td><td>warning</td><td>com.vmware.vc.HA.AnsweredVmLockLostQuestionEvent|vSphere HA answered the lock-lost question on virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}</td></tr> <tr><td>com.vmware.vc.HA.AnsweredVmTerminatePDLEvent</td><td>warning</td><td>com.vmware.vc.HA.AnsweredVmTerminatePDLEvent|vSphere HA answered a question from host {host.name} in cluster {computeResource.name} about terminating virtual machine {vm.name}</td></tr> <tr><td>com.vmware.vc.HA.AutoStartDisabled</td><td>info</td><td>com.vmware.vc.HA.AutoStartDisabled|vSphere HA disabled the automatic Virtual Machine Startup/Shutdown feature on host {host.name} in cluster {computeResource.name} in {datacenter.name}. Automatic VM restarts will interfere with HA when reacting to a host failure.</td></tr> <tr><td>com.vmware.vc.HA.ClusterContainsIncompatibleHosts</td><td>warning</td><td>com.vmware.vc.HA.ClusterContainsIncompatibleHosts|vSphere HA Cluster {computeResource.name} in {datacenter.name} contains ESX/ESXi 3.5 hosts and more recent host versions, which isn&#39;t fully supported.</td></tr> <tr><td>com.vmware.vc.HA.ClusterFailoverActionCompletedEvent</td><td>info</td><td>com.vmware.vc.HA.ClusterFailoverActionCompletedEvent|vSphere HA completed a virtual machine failover action in cluster {computeResource.name} in datacenter {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.ClusterFailoverActionInitiatedEvent</td><td>warning</td><td>com.vmware.vc.HA.ClusterFailoverActionInitiatedEvent|vSphere HA initiated a virtual machine failover action in cluster {computeResource.name} in datacenter {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.DasAgentRunningEvent</td><td>info</td><td>com.vmware.vc.HA.DasAgentRunningEvent|vSphere HA agent on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} is running</td></tr> <tr><td>com.vmware.vc.HA.DasFailoverHostFailedEvent</td><td>error</td><td>com.vmware.vc.HA.DasFailoverHostFailedEvent|vSphere HA detected a possible failover of failover host {host.name} in cluster {computeResource.name} in {datacenter.name} has failed</td></tr> <tr><td>com.vmware.vc.HA.DasFailoverHostIsolatedEvent</td><td>error</td><td>com.vmware.vc.HA.DasFailoverHostIsolatedEvent|Host {host.name} has been isolated from cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.DasFailoverHostPartitionedEvent</td><td>warning</td><td>com.vmware.vc.HA.DasFailoverHostPartitionedEvent|Failover Host {host.name} in {computeResource.name} in {datacenter.name} is in a different network partition than the master</td></tr> <tr><td>com.vmware.vc.HA.DasFailoverHostUnreachableEvent</td><td>error</td><td>com.vmware.vc.HA.DasFailoverHostUnreachableEvent|The vSphere HA agent on the failover host {host.name} in cluster {computeResource.name} in {datacenter.name} is not reachable but host responds to ICMP pings</td></tr> <tr><td>com.vmware.vc.HA.DasHostCompleteDatastoreFailureEvent</td><td>error</td><td>com.vmware.vc.HA.DasHostCompleteDatastoreFailureEvent|All shared datastores failed on the host {hostName} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.DasHostCompleteNetworkFailureEvent</td><td>error</td><td>com.vmware.vc.HA.DasHostCompleteNetworkFailureEvent|All VM networks failed on the host {hostName} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.DasHostFailedEvent</td><td>error</td><td>com.vmware.vc.HA.DasHostFailedEvent|vSphere HA detected a possible host failure of host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.DasHostIsolatedEvent</td><td>error</td><td>com.vmware.vc.HA.DasHostIsolatedEvent|vSphere HA detected that host {host.name} is isolated from cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.DasHostMonitoringDisabledEvent</td><td>warning</td><td>com.vmware.vc.HA.DasHostMonitoringDisabledEvent|vSphere HA host monitoring is disabled. No virtual machine failover will occur until Host Monitoring is re-enabled for cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.FailedRestartAfterIsolationEvent</td><td>error</td><td>com.vmware.vc.HA.FailedRestartAfterIsolationEvent|vSphere HA was unable to restart virtual machine {vm.name} in cluster {computeResource.name} in datacenter {datacenter.name} after it was powered off in response to a network isolation event. The virtual machine should be manually powered back on.</td></tr> <tr><td>com.vmware.vc.HA.HeartbeatDatastoreChanged</td><td>info</td><td>com.vmware.vc.HA.HeartbeatDatastoreChanged|Datastore {dsName} is {changeType.@enum.com.vmware.vc.HA.HeartbeatDatastoreChange} for storage heartbeating monitored by the vSphere HA agent on host {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.HeartbeatDatastoreNotSufficient</td><td>warning</td><td>com.vmware.vc.HA.HeartbeatDatastoreNotSufficient|The number of vSphere HA heartbeat datastores for host {host.name} in cluster {computeResource.name} in {datacenter.name} is {selectedNum}, which is less than required: {requiredNum}</td></tr> <tr><td>com.vmware.vc.HA.HostAgentErrorEvent</td><td>warning</td><td>com.vmware.vc.HA.HostAgentErrorEvent|vSphere HA agent for host {host.name} has an error in {computeResource.name} in {datacenter.name}: {reason.@enum.com.vmware.vc.HA.HostAgentErrorReason}</td></tr> <tr><td>com.vmware.vc.HA.HostDasAgentHealthyEvent</td><td>info</td><td>com.vmware.vc.HA.HostDasAgentHealthyEvent|vSphere HA agent on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} is healthy</td></tr> <tr><td>com.vmware.vc.HA.HostDasErrorEvent</td><td>error</td><td>com.vmware.vc.HA.HostDasErrorEvent|vSphere HA agent on {host.name} in cluster {computeResource.name} in {datacenter.name} has an error: {reason.@enum.HostDasErrorEvent.HostDasErrorReason}</td></tr> <tr><td>com.vmware.vc.HA.HostHasNoIsolationAddrsDefined</td><td>error</td><td>com.vmware.vc.HA.HostHasNoIsolationAddrsDefined|Host {host.name} in cluster {computeResource.name} in {datacenter.name} has no isolation addresses defined as required by vSphere HA.</td></tr> <tr><td>com.vmware.vc.HA.HostHasNoMountedDatastores</td><td>error</td><td>com.vmware.vc.HA.HostHasNoMountedDatastores|vSphere HA cannot be configured on {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} because there are no mounted datastores.</td></tr> <tr><td>com.vmware.vc.HA.HostHasNoSslThumbprint</td><td>error</td><td>com.vmware.vc.HA.HostHasNoSslThumbprint|vSphere HA cannot be configured on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} because its SSL thumbprint has not been verified. Check that vCenter Server is configured to verify SSL thumbprints and that the thumbprint for {host.name} has been verified.</td></tr> <tr><td>com.vmware.vc.HA.HostIncompatibleWithHA</td><td>error</td><td>com.vmware.vc.HA.HostIncompatibleWithHA|The product version of host {host.name} in cluster {computeResource.name} in {datacenter.name} is incompatible with vSphere HA.</td></tr> <tr><td>com.vmware.vc.HA.HostPartitionedFromMasterEvent</td><td>warning</td><td>com.vmware.vc.HA.HostPartitionedFromMasterEvent|vSphere HA detected that host {host.name} is in a different network partition than the master {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.HostStateChangedEvent</td><td>info</td><td>com.vmware.vc.HA.HostStateChangedEvent|The vSphere HA availability state of the host {host.name} in cluster in {computeResource.name} in {datacenter.name} has changed to {newState.@enum.com.vmware.vc.HA.DasFdmAvailabilityState}</td></tr> <tr><td>com.vmware.vc.HA.HostUnconfigureError</td><td>warning</td><td>com.vmware.vc.HA.HostUnconfigureError|There was an error unconfiguring the vSphere HA agent on host {host.name} in cluster {computeResource.name} in {datacenter.name}. To solve this problem, connect the host to a vCenter Server of version 5.0 or later.</td></tr> <tr><td>com.vmware.vc.HA.HostUnconfiguredWithProtectedVms</td><td>error</td><td>com.vmware.vc.HA.HostUnconfiguredWithProtectedVms|Host {host.name} in cluster {computeResource.name} in {datacenter.name} is disconnected from vCenter Server, but contains {protectedVmCount} protected virtual machine(s)</td></tr> <tr><td>com.vmware.vc.HA.InvalidMaster</td><td>warning</td><td>com.vmware.vc.HA.InvalidMaster|vSphere HA agent on host {remoteHostname} is an invalid master. The host should be examined to determine if it has been compromised.</td></tr> <tr><td>com.vmware.vc.HA.NotAllHostAddrsPingable</td><td>info</td><td>com.vmware.vc.HA.NotAllHostAddrsPingable|The vSphere HA agent on the host {host.name} in cluster {computeResource.name} in {datacenter.name} cannot reach some of the management network addresses of other hosts, and thus HA may not be able to restart VMs if a host failure occurs: {unpingableAddrs}</td></tr> <tr><td>com.vmware.vc.HA.StartFTSecondaryFailedEvent</td><td>error</td><td>com.vmware.vc.HA.StartFTSecondaryFailedEvent|vSphere HA agent failed to start Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost} for primary VM {vm.name} in cluster {computeResource.name} in {datacenter.name}. Reason : {fault.msg}. vSphere HA agent will retry until it times out.</td></tr> <tr><td>com.vmware.vc.HA.StartFTSecondarySucceededEvent</td><td>info</td><td>com.vmware.vc.HA.StartFTSecondarySucceededEvent|vSphere HA agent successfully started Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost} for primary VM {vm.name} in cluster {computeResource.name}.</td></tr> <tr><td>com.vmware.vc.HA.UserHeartbeatDatastoreRemoved</td><td>warning</td><td>com.vmware.vc.HA.UserHeartbeatDatastoreRemoved|vSphere HA removed datastore {dsName} from the set of preferred heartbeat datastores selected for cluster {computeResource.name} in {datacenter.name} because the datastore is removed from inventory</td></tr> <tr><td>com.vmware.vc.HA.VMIsHADisabledIsolationEvent</td><td>info</td><td>com.vmware.vc.HA.VMIsHADisabledIsolationEvent|vSphere HA did not perform an isolation response for {vm.name} in cluster {computeResource.name} in {datacenter.name} because its VM restart priority is Disabled</td></tr> <tr><td>com.vmware.vc.HA.VMIsHADisabledRestartEvent</td><td>info</td><td>com.vmware.vc.HA.VMIsHADisabledRestartEvent|vSphere HA did not attempt to restart {vm.name} in cluster {computeResource.name} in {datacenter.name} because its VM restart priority is Disabled</td></tr> <tr><td>com.vmware.vc.HA.VcCannotFindMasterEvent</td><td>warning</td><td>com.vmware.vc.HA.VcCannotFindMasterEvent|vCenter Server is unable to find a master vSphere HA agent in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.VcConnectedToMasterEvent</td><td>info</td><td>com.vmware.vc.HA.VcConnectedToMasterEvent|vCenter Server is connected to a master HA agent running on host {hostname} in {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.VcDisconnectedFromMasterEvent</td><td>warning</td><td>com.vmware.vc.HA.VcDisconnectedFromMasterEvent|vCenter Server is disconnected from a master HA agent running on host {hostname} in {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.HA.VmNotProtectedEvent</td><td>error</td><td>com.vmware.vc.HA.VmNotProtectedEvent|Virtual machine {vm.name} in cluster {computeResource.name} in {datacenter.name} failed to become vSphere HA Protected and HA may not attempt to restart it after a failure.</td></tr> <tr><td>com.vmware.vc.HA.VmProtectedEvent</td><td>info</td><td>com.vmware.vc.HA.VmProtectedEvent|Virtual machine {vm.name} in cluster {computeResource.name} in {datacenter.name} is vSphere HA Protected and HA will attempt to restart it after a failure.</td></tr> <tr><td>com.vmware.vc.HA.VmUnprotectedEvent</td><td>info</td><td>com.vmware.vc.HA.VmUnprotectedEvent|Virtual machine {vm.name} in cluster {computeResource.name} in {datacenter.name} is not vSphere HA Protected.</td></tr> <tr><td>com.vmware.vc.HA.VmUnprotectedOnDiskSpaceFull</td><td>info</td><td>com.vmware.vc.HA.VmUnprotectedOnDiskSpaceFull|vSphere HA has unprotected virtual machine {vm.name} in cluster {computeResource.name} in datacenter {datacenter.name} because it ran out of disk space</td></tr> <tr><td>com.vmware.vc.VCHealthStateChangedEvent</td><td>info</td><td>com.vmware.vc.VCHealthStateChangedEvent|vCenter Service overall health changed from &#39;{oldState}&#39; to &#39;{newState}&#39;</td></tr> <tr><td>com.vmware.vc.VmCloneFailedInvalidDestinationEvent</td><td>error</td><td>com.vmware.vc.VmCloneFailedInvalidDestinationEvent|Cannot clone {vm.name} as {destVmName} to invalid or non-existent destination with ID {invalidMoRef}: {fault}</td></tr> <tr><td>com.vmware.vc.VmCloneToResourcePoolFailedEvent</td><td>error</td><td>com.vmware.vc.VmCloneToResourcePoolFailedEvent|Cannot clone {vm.name} as {destVmName} to resource pool {destResourcePool}: {fault}</td></tr> <tr><td>com.vmware.vc.VmDiskConsolidatedEvent</td><td>info</td><td>com.vmware.vc.VmDiskConsolidatedEvent|Virtual machine {vm.name} disks consolidated successfully on {host.name} in cluster {computeResource.name} in {datacenter.name}.</td></tr> <tr><td>com.vmware.vc.VmDiskConsolidationNeeded</td><td>warning</td><td>com.vmware.vc.VmDiskConsolidationNeeded|Virtual machine {vm.name} disks consolidation is needed on {host.name} in cluster {computeResource.name} in {datacenter.name}.</td></tr> <tr><td>com.vmware.vc.VmDiskConsolidationNoLongerNeeded</td><td>info</td><td>com.vmware.vc.VmDiskConsolidationNoLongerNeeded|Virtual machine {vm.name} disks consolidation is no longer needed on {host.name} in cluster {computeResource.name} in {datacenter.name}.</td></tr> <tr><td>com.vmware.vc.VmDiskFailedToConsolidateEvent</td><td>warning</td><td>com.vmware.vc.VmDiskFailedToConsolidateEvent|Virtual machine {vm.name} disks consolidation failed on {host.name} in cluster {computeResource.name} in {datacenter.name}.</td></tr> <tr><td>com.vmware.vc.cim.CIMGroupHealthStateChanged</td><td>info</td><td>com.vmware.vc.cim.CIMGroupHealthStateChanged|Health of [data.group] changed from [data.oldState] to [data.newState]. [data.cause]</td></tr> <tr><td>com.vmware.vc.datastore.UpdateVmFilesFailedEvent</td><td>error</td><td>com.vmware.vc.datastore.UpdateVmFilesFailedEvent|Failed to update VM files on datastore {ds.name} using host {hostName}</td></tr> <tr><td>com.vmware.vc.datastore.UpdatedVmFilesEvent</td><td>info</td><td>com.vmware.vc.datastore.UpdatedVmFilesEvent|Updated VM files on datastore {ds.name} using host {hostName}</td></tr> <tr><td>com.vmware.vc.datastore.UpdatingVmFilesEvent</td><td>info</td><td>com.vmware.vc.datastore.UpdatingVmFilesEvent|Updating VM files on datastore {ds.name} using host {hostName}</td></tr> <tr><td>com.vmware.vc.ft.VmAffectedByDasDisabledEvent</td><td>warning</td><td>com.vmware.vc.ft.VmAffectedByDasDisabledEvent|vSphere HA has been disabled in cluster {computeResource.name} of datacenter {datacenter.name}. vSphere HA will not restart VM {vm.name} or its Secondary VM after a failure.</td></tr> <tr><td>com.vmware.vc.guestOperations.GuestOperation</td><td>info</td><td>com.vmware.vc.guestOperations.GuestOperation|Guest operation {operationName.@enum.com.vmware.vc.guestOp} performed on Virtual machine {vm.name}.</td></tr> <tr><td>com.vmware.vc.guestOperations.GuestOperationAuthFailure</td><td>warning</td><td>com.vmware.vc.guestOperations.GuestOperationAuthFailure|Guest operation authentication failed for operation {operationName.@enum.com.vmware.vc.guestOp} on Virtual machine {vm.name}.</td></tr> <tr><td>com.vmware.vc.ha.VmRestartedByHAEvent</td><td>warning</td><td>com.vmware.vc.ha.VmRestartedByHAEvent|vSphere HA restarted virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}</td></tr> <tr><td>com.vmware.vc.host.AutoStartReconfigureFailedEvent</td><td>error</td><td>com.vmware.vc.host.AutoStartReconfigureFailedEvent|Reconfiguring autostart rules for virtual machines on {host.name} in datacenter {datacenter.name} failed</td></tr> <tr><td>com.vmware.vc.npt.VmAdapterEnteredPassthroughEvent</td><td>info</td><td>com.vmware.vc.npt.VmAdapterEnteredPassthroughEvent|Network passthrough is active on adapter {deviceLabel} of virtual machine {vm.name} on host {host.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.npt.VmAdapterExitedPassthroughEvent</td><td>info</td><td>com.vmware.vc.npt.VmAdapterExitedPassthroughEvent|Network passthrough is inactive on adapter {deviceLabel} of virtual machine {vm.name} on host {host.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.ovfconsumers.CloneOvfConsumerStateErrorEvent</td><td>error</td><td>com.vmware.vc.ovfconsumers.CloneOvfConsumerStateErrorEvent|Failed to clone state for the entity &#39;{entityName}&#39; on extension {extensionName}</td></tr> <tr><td>com.vmware.vc.ovfconsumers.GetOvfEnvironmentSectionsErrorEvent</td><td>error</td><td>com.vmware.vc.ovfconsumers.GetOvfEnvironmentSectionsErrorEvent|Failed to retrieve OVF environment sections for VM &#39;{vm.name}&#39; from extension {extensionName}</td></tr> <tr><td>com.vmware.vc.ovfconsumers.PowerOnAfterCloneErrorEvent</td><td>error</td><td>com.vmware.vc.ovfconsumers.PowerOnAfterCloneErrorEvent|Powering on VM &#39;{vm.name}&#39; after cloning was blocked by an extension. Message: {description}</td></tr> <tr><td>com.vmware.vc.ovfconsumers.RegisterEntityErrorEvent</td><td>error</td><td>com.vmware.vc.ovfconsumers.RegisterEntityErrorEvent|Failed to register entity &#39;{entityName}&#39; on extension {extensionName}</td></tr> <tr><td>com.vmware.vc.ovfconsumers.UnregisterEntitiesErrorEvent</td><td>error</td><td>com.vmware.vc.ovfconsumers.UnregisterEntitiesErrorEvent|Failed to unregister entities on extension {extensionName}</td></tr> <tr><td>com.vmware.vc.ovfconsumers.ValidateOstErrorEvent</td><td>error</td><td>com.vmware.vc.ovfconsumers.ValidateOstErrorEvent|Failed to validate OVF descriptor on extension {extensionName}</td></tr> <tr><td>com.vmware.vc.profile.AnswerFileExportedEvent</td><td>info</td><td>com.vmware.vc.profile.AnswerFileExportedEvent|Answer file for host {host.name} in datacenter {datacenter.name} has been exported</td></tr> <tr><td>com.vmware.vc.profile.AnswerFileUpdatedEvent</td><td>info</td><td>com.vmware.vc.profile.AnswerFileUpdatedEvent|Host customization settings for host {host.name} in datacenter {datacenter.name} has been updated</td></tr> <tr><td>com.vmware.vc.rp.ResourcePoolRenamedEvent</td><td>info</td><td>com.vmware.vc.rp.ResourcePoolRenamedEvent|Resource pool &#39;{oldName}&#39; has been renamed to &#39;{newName}&#39;</td></tr> <tr><td>com.vmware.vc.sdrs.CanceledDatastoreMaintenanceModeEvent</td><td>info</td><td>com.vmware.vc.sdrs.CanceledDatastoreMaintenanceModeEvent|The datastore maintenance mode operation has been canceled</td></tr> <tr><td>com.vmware.vc.sdrs.ConfiguredStorageDrsOnPodEvent</td><td>info</td><td>com.vmware.vc.sdrs.ConfiguredStorageDrsOnPodEvent|Configured storage DRS on datastore cluster {objectName}</td></tr> <tr><td>com.vmware.vc.sdrs.ConsistencyGroupViolationEvent</td><td>warning</td><td>com.vmware.vc.sdrs.ConsistencyGroupViolationEvent|Datastore cluster {objectName} has datastores that belong to different SRM Consistency Groups</td></tr> <tr><td>com.vmware.vc.sdrs.DatastoreEnteredMaintenanceModeEvent</td><td>info</td><td>com.vmware.vc.sdrs.DatastoreEnteredMaintenanceModeEvent|Datastore {ds.name} has entered maintenance mode</td></tr> <tr><td>com.vmware.vc.sdrs.DatastoreEnteringMaintenanceModeEvent</td><td>info</td><td>com.vmware.vc.sdrs.DatastoreEnteringMaintenanceModeEvent|Datastore {ds.name} is entering maintenance mode</td></tr> <tr><td>com.vmware.vc.sdrs.DatastoreExitedMaintenanceModeEvent</td><td>info</td><td>com.vmware.vc.sdrs.DatastoreExitedMaintenanceModeEvent|Datastore {ds.name} has exited maintenance mode</td></tr> <tr><td>com.vmware.vc.sdrs.DatastoreInMultipleDatacentersEvent</td><td>warning</td><td>com.vmware.vc.sdrs.DatastoreInMultipleDatacentersEvent|Datastore cluster {objectName} has one or more datastores {datastore} shared across multiple datacenters</td></tr> <tr><td>com.vmware.vc.sdrs.DatastoreMaintenanceModeErrorsEvent</td><td>error</td><td>com.vmware.vc.sdrs.DatastoreMaintenanceModeErrorsEvent|Datastore {ds.name} encountered errors while entering maintenance mode</td></tr> <tr><td>com.vmware.vc.sdrs.StorageDrsDisabledEvent</td><td>info</td><td>com.vmware.vc.sdrs.StorageDrsDisabledEvent|Disabled storage DRS on datastore cluster {objectName}</td></tr> <tr><td>com.vmware.vc.sdrs.StorageDrsEnabledEvent</td><td>info</td><td>com.vmware.vc.sdrs.StorageDrsEnabledEvent|Enabled storage DRS on datastore cluster {objectName} with automation level {behavior.@enum.storageDrs.PodConfigInfo.Behavior}</td></tr> <tr><td>com.vmware.vc.sdrs.StorageDrsInvocationFailedEvent</td><td>error</td><td>com.vmware.vc.sdrs.StorageDrsInvocationFailedEvent|Storage DRS invocation failed on datastore cluster {objectName}</td></tr> <tr><td>com.vmware.vc.sdrs.StorageDrsNewRecommendationPendingEvent</td><td>info</td><td>com.vmware.vc.sdrs.StorageDrsNewRecommendationPendingEvent|A new storage DRS recommendation has been generated on datastore cluster {objectName}</td></tr> <tr><td>com.vmware.vc.sdrs.StorageDrsNotSupportedHostConnectedToPodEvent</td><td>warning</td><td>com.vmware.vc.sdrs.StorageDrsNotSupportedHostConnectedToPodEvent|Datastore cluster {objectName} is connected to one or more hosts {host} that do not support storage DRS</td></tr> <tr><td>com.vmware.vc.sdrs.StorageDrsStorageMigrationEvent</td><td>info</td><td>com.vmware.vc.sdrs.StorageDrsStorageMigrationEvent|Storage DRS migrated disks of VM {vm.name} to datastore {ds.name}</td></tr> <tr><td>com.vmware.vc.sdrs.StorageDrsStoragePlacementEvent</td><td>info</td><td>com.vmware.vc.sdrs.StorageDrsStoragePlacementEvent|Storage DRS placed disks of VM {vm.name} on datastore {ds.name}</td></tr> <tr><td>com.vmware.vc.sdrs.StoragePodCreatedEvent</td><td>info</td><td>com.vmware.vc.sdrs.StoragePodCreatedEvent|Created datastore cluster {objectName}</td></tr> <tr><td>com.vmware.vc.sdrs.StoragePodDestroyedEvent</td><td>info</td><td>com.vmware.vc.sdrs.StoragePodDestroyedEvent|Removed datastore cluster {objectName}</td></tr> <tr><td>com.vmware.vc.sioc.NotSupportedHostConnectedToDatastoreEvent</td><td>warning</td><td>com.vmware.vc.sioc.NotSupportedHostConnectedToDatastoreEvent|SIOC has detected that a host: {host} connected to a SIOC-enabled datastore: {objectName} is running an older version of ESX that does not support SIOC. This is an unsupported configuration.</td></tr> <tr><td>com.vmware.vc.sms.LunCapabilityInitEvent</td><td>info</td><td>com.vmware.vc.sms.LunCapabilityInitEvent|Storage provider [{providerName}] : system capability warning for {vcIdForVasaObject} : {msgTxt}</td></tr> <tr><td>com.vmware.vc.sms.LunCapabilityMetEvent</td><td>info</td><td>com.vmware.vc.sms.LunCapabilityMetEvent|Storage provider [{providerName}] : system capability normal for {vcIdForVasaObject}</td></tr> <tr><td>com.vmware.vc.sms.LunCapabilityNotMetEvent</td><td>info</td><td>com.vmware.vc.sms.LunCapabilityNotMetEvent|Storage provider [{providerName}] : system capability alert for {vcIdForVasaObject} : {msgTxt}</td></tr> <tr><td>com.vmware.vc.sms.ThinProvisionedLunThresholdClearedEvent</td><td>info</td><td>com.vmware.vc.sms.ThinProvisionedLunThresholdClearedEvent|Storage provider [{providerName}] : thin provisioning capacity threshold normal for {vcIdForVasaObject}</td></tr> <tr><td>com.vmware.vc.sms.ThinProvisionedLunThresholdCrossedEvent</td><td>info</td><td>com.vmware.vc.sms.ThinProvisionedLunThresholdCrossedEvent|Storage provider [{providerName}] : thin provisioning capacity threshold alert for {vcIdForVasaObject}</td></tr> <tr><td>com.vmware.vc.sms.ThinProvisionedLunThresholdInitEvent</td><td>info</td><td>com.vmware.vc.sms.ThinProvisionedLunThresholdInitEvent|Storage provider [{providerName}] : thin provisioning capacity threshold warning for {vcIdForVasaObject}</td></tr> <tr><td>com.vmware.vc.sms.provider.health.event</td><td>info</td><td>com.vmware.vc.sms.provider.health.event|Storage provider [{providerName}] : health event for {vcIdForVasaObject} : {msgTxt}</td></tr> <tr><td>com.vmware.vc.sms.provider.system.event</td><td>info</td><td>com.vmware.vc.sms.provider.system.event|Storage provider [{providerName}] : system event for {vcIdForVasaObject} : {msgTxt}</td></tr> <tr><td>com.vmware.vc.stats.HostQuickStatesNotUpToDateEvent</td><td>info</td><td>com.vmware.vc.stats.HostQuickStatesNotUpToDateEvent|Quick stats on {host.name} in {computeResource.name} in {datacenter.name} is not up-to-date</td></tr> <tr><td>com.vmware.vc.vcp.FtDisabledVmTreatAsNonFtEvent</td><td>info</td><td>com.vmware.vc.vcp.FtDisabledVmTreatAsNonFtEvent|HA VM Component Protection protects virtual machine {vm.name} on {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} as non-FT virtual machine because the FT state is disabled</td></tr> <tr><td>com.vmware.vc.vcp.FtFailoverEvent</td><td>info</td><td>com.vmware.vc.vcp.FtFailoverEvent|FT Primary VM {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} is going to fail over to Secondary VM due to component failure </td></tr> <tr><td>com.vmware.vc.vcp.FtFailoverFailedEvent</td><td>error</td><td>com.vmware.vc.vcp.FtFailoverFailedEvent|FT virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} failed to failover to secondary</td></tr> <tr><td>com.vmware.vc.vcp.FtSecondaryRestartEvent</td><td>info</td><td>com.vmware.vc.vcp.FtSecondaryRestartEvent|HA VM Component Protection is restarting FT secondary virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} due to component failure</td></tr> <tr><td>com.vmware.vc.vcp.FtSecondaryRestartFailedEvent</td><td>error</td><td>com.vmware.vc.vcp.FtSecondaryRestartFailedEvent|FT Secondary VM {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} failed to restart</td></tr> <tr><td>com.vmware.vc.vcp.NeedSecondaryFtVmTreatAsNonFtEvent</td><td>info</td><td>com.vmware.vc.vcp.NeedSecondaryFtVmTreatAsNonFtEvent|HA VM Component Protection protects virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} as non-FT virtual machine because it has been in the needSecondary state too long</td></tr> <tr><td>com.vmware.vc.vcp.TestEndEvent</td><td>info</td><td>com.vmware.vc.vcp.TestEndEvent|VM Component Protection test ends on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}</td></tr> <tr><td>com.vmware.vc.vcp.TestStartEvent</td><td>info</td><td>com.vmware.vc.vcp.TestStartEvent|VM Component Protection test starts on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}</td></tr> <tr><td>com.vmware.vc.vcp.VcpNoActionEvent</td><td>info</td><td>com.vmware.vc.vcp.VcpNoActionEvent|HA VM Component Protection did not take action on virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} due to the feature configuration setting</td></tr> <tr><td>com.vmware.vc.vcp.VmDatastoreFailedEvent</td><td>error</td><td>com.vmware.vc.vcp.VmDatastoreFailedEvent|Virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} lost access to {datastore}</td></tr> <tr><td>com.vmware.vc.vcp.VmNetworkFailedEvent</td><td>error</td><td>com.vmware.vc.vcp.VmNetworkFailedEvent|Virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} lost access to {network}</td></tr> <tr><td>com.vmware.vc.vcp.VmPowerOffHangEvent</td><td>error</td><td>com.vmware.vc.vcp.VmPowerOffHangEvent|HA VM Component Protection could not power off virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} successfully after trying {numTimes} times and will keep trying</td></tr> <tr><td>com.vmware.vc.vcp.VmRestartEvent</td><td>info</td><td>com.vmware.vc.vcp.VmRestartEvent|HA VM Component Protection is restarting virtual machine {vm.name} due to component failure on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}</td></tr> <tr><td>com.vmware.vc.vcp.VmRestartFailedEvent</td><td>error</td><td>com.vmware.vc.vcp.VmRestartFailedEvent|Virtual machine {vm.name} affected by component failure on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} failed to restart</td></tr> <tr><td>com.vmware.vc.vcp.VmWaitForCandidateHostEvent</td><td>error</td><td>com.vmware.vc.vcp.VmWaitForCandidateHostEvent|HA VM Component Protection could not find a destination host for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} after waiting {numSecWait} seconds and will keep trying</td></tr> <tr><td>com.vmware.vc.vm.VmRegisterFailedEvent</td><td>error</td><td>com.vmware.vc.vm.VmRegisterFailedEvent|Virtual machine {vm.name} registration on {host.name} in datacenter {datacenter.name} failed</td></tr> <tr><td>com.vmware.vc.vm.VmStateFailedToRevertToSnapshot</td><td>error</td><td>com.vmware.vc.vm.VmStateFailedToRevertToSnapshot|Failed to revert the execution state of the virtual machine {vm.name} on host {host.name}, in compute resource {computeResource.name} to snapshot {snapshotName}, with ID {snapshotId}</td></tr> <tr><td>com.vmware.vc.vm.VmStateRevertedToSnapshot</td><td>info</td><td>com.vmware.vc.vm.VmStateRevertedToSnapshot|The execution state of the virtual machine {vm.name} on host {host.name}, in compute resource {computeResource.name} has been reverted to the state of snapshot {snapshotName}, with ID {snapshotId}</td></tr> <tr><td>com.vmware.vc.vmam.AppMonitoringNotSupported</td><td>warning</td><td>com.vmware.vc.vmam.AppMonitoringNotSupported|Application monitoring is not supported on {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.vmam.VmAppHealthMonitoringStateChangedEvent</td><td>warning</td><td>com.vmware.vc.vmam.VmAppHealthMonitoringStateChangedEvent|vSphere HA detected that the application heartbeat status changed to {status.@enum.VirtualMachine.AppHeartbeatStatusType} for {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vc.vmam.VmDasAppHeartbeatFailedEvent</td><td>warning</td><td>com.vmware.vc.vmam.VmDasAppHeartbeatFailedEvent|vSphere HA detected application heartbeat failure for {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>com.vmware.vim.eam.agency.create</td><td>info</td><td>com.vmware.vim.eam.agency.create|{agencyName} created by {ownerName}</td></tr> <tr><td>com.vmware.vim.eam.agency.destroyed</td><td>info</td><td>com.vmware.vim.eam.agency.destroyed|{agencyName} removed from the vSphere ESX Agent Manager</td></tr> <tr><td>com.vmware.vim.eam.agency.goalstate</td><td>info</td><td>com.vmware.vim.eam.agency.goalstate|{agencyName} changed goal state from {oldGoalState} to {newGoalState}</td></tr> <tr><td>com.vmware.vim.eam.agency.statusChanged</td><td>info</td><td>com.vmware.vim.eam.agency.statusChanged|Agency status changed from {oldStatus} to {newStatus}</td></tr> <tr><td>com.vmware.vim.eam.agency.updated</td><td>info</td><td>com.vmware.vim.eam.agency.updated|Configuration updated {agencyName}</td></tr> <tr><td>com.vmware.vim.eam.agent.created</td><td>info</td><td>com.vmware.vim.eam.agent.created|Agent added to host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.agent.destroyed</td><td>info</td><td>com.vmware.vim.eam.agent.destroyed|Agent removed from host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.agent.destroyedNoHost</td><td>info</td><td>com.vmware.vim.eam.agent.destroyedNoHost|Agent removed from host ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.agent.markAgentVmAsAvailableAfterPowerOn</td><td>info</td><td>com.vmware.vim.eam.agent.markAgentVmAsAvailableAfterPowerOn|Agent VM {vm.name} has been powered on. Mark agent as available to proceed agent workflow ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.agent.markAgentVmAsAvailableAfterProvisioning</td><td>info</td><td>com.vmware.vim.eam.agent.markAgentVmAsAvailableAfterProvisioning|Agent VM {vm.name} has been provisioned. Mark agent as available to proceed agent workflow ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.agent.statusChanged</td><td>info</td><td>com.vmware.vim.eam.agent.statusChanged|Agent status changed from {oldStatus} to {newStatus}</td></tr> <tr><td>com.vmware.vim.eam.agent.task.deleteVm</td><td>info</td><td>com.vmware.vim.eam.agent.task.deleteVm|Agent VM {vmName} is deleted on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.agent.task.deployVm</td><td>info</td><td>com.vmware.vim.eam.agent.task.deployVm|Agent VM {vm.name} is provisioned on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.agent.task.powerOffVm</td><td>info</td><td>com.vmware.vim.eam.agent.task.powerOffVm|Agent VM {vm.name} powered off, on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.agent.task.powerOnVm</td><td>info</td><td>com.vmware.vim.eam.agent.task.powerOnVm|Agent VM {vm.name} powered on, on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.agent.task.vibInstalled</td><td>info</td><td>com.vmware.vim.eam.agent.task.vibInstalled|Agent installed VIB {vib} on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.agent.task.vibUninstalled</td><td>info</td><td>com.vmware.vim.eam.agent.task.vibUninstalled|Agent uninstalled VIB {vib} on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.cannotAccessAgentOVF</td><td>error</td><td>com.vmware.vim.eam.issue.cannotAccessAgentOVF|Unable to access agent OVF package at {url} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.cannotAccessAgentVib</td><td>error</td><td>com.vmware.vim.eam.issue.cannotAccessAgentVib|Unable to access agent VIB module at {url} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.hostInMaintenanceMode</td><td>error</td><td>com.vmware.vim.eam.issue.hostInMaintenanceMode|Agent cannot complete an operation since the host {host.name} is in maintenance mode ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.hostInStandbyMode</td><td>error</td><td>com.vmware.vim.eam.issue.hostInStandbyMode|Agent cannot complete an operation since the host {host.name} is in standby mode ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.hostPoweredOff</td><td>error</td><td>com.vmware.vim.eam.issue.hostPoweredOff|Agent cannot complete an operation since the host {host.name} is powered off ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.incompatibleHostVersion</td><td>error</td><td>com.vmware.vim.eam.issue.incompatibleHostVersion|Agent is not deployed due to incompatible host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.insufficientIpAddresses</td><td>error</td><td>com.vmware.vim.eam.issue.insufficientIpAddresses|Insufficient IP addresses in network protocol profile in agent&#39;s VM network ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.insufficientResources</td><td>error</td><td>com.vmware.vim.eam.issue.insufficientResources|Agent cannot be provisioned due to insufficient resources on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.insufficientSpace</td><td>error</td><td>com.vmware.vim.eam.issue.insufficientSpace|Agent on {host.name} cannot be provisioned due to insufficient space on datastore ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.missingAgentIpPool</td><td>error</td><td>com.vmware.vim.eam.issue.missingAgentIpPool|No network protocol profile associated to agent&#39;s VM network ({agencyname})</td></tr> <tr><td>com.vmware.vim.eam.issue.missingDvFilterSwitch</td><td>error</td><td>com.vmware.vim.eam.issue.missingDvFilterSwitch|dvFilter switch is not configured on host {host.name} ({agencyname})</td></tr> <tr><td>com.vmware.vim.eam.issue.noAgentVmDatastore</td><td>error</td><td>com.vmware.vim.eam.issue.noAgentVmDatastore|No agent datastore configuration on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.noAgentVmNetwork</td><td>error</td><td>com.vmware.vim.eam.issue.noAgentVmNetwork|No agent network configuration on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.noCustomAgentVmNetwork</td><td>error</td><td>com.vmware.vim.eam.issue.noCustomAgentVmNetwork|Agent network(s) {customAgentVmNetworkName} not available on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.orphandedDvFilterSwitch</td><td>error</td><td>com.vmware.vim.eam.issue.orphandedDvFilterSwitch|Unused dvFilter switch on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.orphanedAgency</td><td>error</td><td>com.vmware.vim.eam.issue.orphanedAgency|Orphaned agency found. ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.ovfInvalidFormat</td><td>error</td><td>com.vmware.vim.eam.issue.ovfInvalidFormat|OVF used to provision agent on host {host.name} has invalid format ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.ovfInvalidProperty</td><td>error</td><td>com.vmware.vim.eam.issue.ovfInvalidProperty|OVF environment used to provision agent on host {host.name} has one or more invalid properties ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.resolved</td><td>info</td><td>com.vmware.vim.eam.issue.resolved|Issue {type} resolved (key {key})</td></tr> <tr><td>com.vmware.vim.eam.issue.unknownAgentVm</td><td>error</td><td>com.vmware.vim.eam.issue.unknownAgentVm|Unknown agent VM {vm.name}</td></tr> <tr><td>com.vmware.vim.eam.issue.vibCannotPutHostInMaintenanceMode</td><td>error</td><td>com.vmware.vim.eam.issue.vibCannotPutHostInMaintenanceMode|Cannot put host into maintenance mode ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vibInvalidFormat</td><td>error</td><td>com.vmware.vim.eam.issue.vibInvalidFormat|Invalid format for VIB module at {url} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vibNotInstalled</td><td>error</td><td>com.vmware.vim.eam.issue.vibNotInstalled|VIB module for agent is not installed on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vibRequiresHostInMaintenanceMode</td><td>error</td><td>com.vmware.vim.eam.issue.vibRequiresHostInMaintenanceMode|Host must be put into maintenance mode to complete agent VIB installation ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vibRequiresHostReboot</td><td>error</td><td>com.vmware.vim.eam.issue.vibRequiresHostReboot|Host {host.name} must be reboot to complete agent VIB installation ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vibRequiresManualInstallation</td><td>error</td><td>com.vmware.vim.eam.issue.vibRequiresManualInstallation|VIB {vib} requires manual installation on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vibRequiresManualUninstallation</td><td>error</td><td>com.vmware.vim.eam.issue.vibRequiresManualUninstallation|VIB {vib} requires manual uninstallation on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vmCorrupted</td><td>error</td><td>com.vmware.vim.eam.issue.vmCorrupted|Agent VM {vm.name} on host {host.name} is corrupted ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vmDeployed</td><td>error</td><td>com.vmware.vim.eam.issue.vmDeployed|Agent VM {vm.name} is provisioned on host {host.name} when it should be removed ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vmMarkedAsTemplate</td><td>error</td><td>com.vmware.vim.eam.issue.vmMarkedAsTemplate|Agent VM {vm.name} on host {host.name} is marked as template ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vmNotDeployed</td><td>error</td><td>com.vmware.vim.eam.issue.vmNotDeployed|Agent VM is missing on host {host.name} ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vmOrphaned</td><td>error</td><td>com.vmware.vim.eam.issue.vmOrphaned|Orphaned agent VM {vm.name} on host {host.name} detected ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vmPoweredOff</td><td>error</td><td>com.vmware.vim.eam.issue.vmPoweredOff|Agent VM {vm.name} on host {host.name} is expected to be powered on ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vmPoweredOn</td><td>error</td><td>com.vmware.vim.eam.issue.vmPoweredOn|Agent VM {vm.name} on host {host.name} is expected to be powered off ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vmSuspended</td><td>error</td><td>com.vmware.vim.eam.issue.vmSuspended|Agent VM {vm.name} on host {host.name} is expected to be powered on but is suspended ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vmWrongFolder</td><td>error</td><td>com.vmware.vim.eam.issue.vmWrongFolder|Agent VM {vm.name} on host {host.name} is in the wrong VM folder ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.issue.vmWrongResourcePool</td><td>error</td><td>com.vmware.vim.eam.issue.vmWrongResourcePool|Agent VM {vm.name} on host {host.name} is in the resource pool ({agencyName})</td></tr> <tr><td>com.vmware.vim.eam.login.invalid</td><td>warning</td><td>com.vmware.vim.eam.login.invalid|Failed login to vSphere ESX Agent Manager</td></tr> <tr><td>com.vmware.vim.eam.login.succeeded</td><td>info</td><td>com.vmware.vim.eam.login.succeeded|Successful login by {user} into vSphere ESX Agent Manager</td></tr> <tr><td>com.vmware.vim.eam.logout</td><td>info</td><td>com.vmware.vim.eam.logout|User {user} logged out of vSphere ESX Agent Manager by logging out of the vCenter server</td></tr> <tr><td>com.vmware.vim.eam.task.scanForUnknownAgentVmsCompleted</td><td>info</td><td>com.vmware.vim.eam.task.scanForUnknownAgentVmsCompleted|Scan for unknown agent VMs completed</td></tr> <tr><td>com.vmware.vim.eam.task.scanForUnknownAgentVmsInitiated</td><td>info</td><td>com.vmware.vim.eam.task.scanForUnknownAgentVmsInitiated|Scan for unknown agent VMs initiated</td></tr> <tr><td>com.vmware.vim.eam.task.setupDvFilter</td><td>info</td><td>com.vmware.vim.eam.task.setupDvFilter|DvFilter switch &#39;{switchName}&#39; is setup on host {host.name}</td></tr> <tr><td>com.vmware.vim.eam.task.tearDownDvFilter</td><td>info</td><td>com.vmware.vim.eam.task.tearDownDvFilter|DvFilter switch &#39;{switchName}&#39; is teared down on host {host.name}</td></tr> <tr><td>com.vmware.vim.eam.unauthorized.access</td><td>warning</td><td>com.vmware.vim.eam.unauthorized.access|Unauthorized access by {user} in vSphere ESX Agent Manager</td></tr> <tr><td>com.vmware.vim.eam.vum.failedtouploadvib</td><td>error</td><td>com.vmware.vim.eam.vum.failedtouploadvib|Failed to upload {vibUrl} to VMware Update Manager ({agencyName})</td></tr> <tr><td>com.vmware.vim.vsm.dependency.bind.vApp</td><td></td><td>com.vmware.vim.vsm.dependency.bind.vApp|event.com.vmware.vim.vsm.dependency.bind.vApp.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.bind.vm</td><td></td><td>com.vmware.vim.vsm.dependency.bind.vm|event.com.vmware.vim.vsm.dependency.bind.vm.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.create.vApp</td><td></td><td>com.vmware.vim.vsm.dependency.create.vApp|event.com.vmware.vim.vsm.dependency.create.vApp.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.create.vm</td><td></td><td>com.vmware.vim.vsm.dependency.create.vm|event.com.vmware.vim.vsm.dependency.create.vm.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.destroy.vApp</td><td></td><td>com.vmware.vim.vsm.dependency.destroy.vApp|event.com.vmware.vim.vsm.dependency.destroy.vApp.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.destroy.vm</td><td></td><td>com.vmware.vim.vsm.dependency.destroy.vm|event.com.vmware.vim.vsm.dependency.destroy.vm.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.reconfigure.vApp</td><td></td><td>com.vmware.vim.vsm.dependency.reconfigure.vApp|event.com.vmware.vim.vsm.dependency.reconfigure.vApp.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.reconfigure.vm</td><td></td><td>com.vmware.vim.vsm.dependency.reconfigure.vm|event.com.vmware.vim.vsm.dependency.reconfigure.vm.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.unbind.vApp</td><td></td><td>com.vmware.vim.vsm.dependency.unbind.vApp|event.com.vmware.vim.vsm.dependency.unbind.vApp.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.unbind.vm</td><td></td><td>com.vmware.vim.vsm.dependency.unbind.vm|event.com.vmware.vim.vsm.dependency.unbind.vm.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.update.vApp</td><td></td><td>com.vmware.vim.vsm.dependency.update.vApp|event.com.vmware.vim.vsm.dependency.update.vApp.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.dependency.update.vm</td><td></td><td>com.vmware.vim.vsm.dependency.update.vm|event.com.vmware.vim.vsm.dependency.update.vm.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.provider.register</td><td></td><td>com.vmware.vim.vsm.provider.register|event.com.vmware.vim.vsm.provider.register.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.provider.unregister</td><td></td><td>com.vmware.vim.vsm.provider.unregister|event.com.vmware.vim.vsm.provider.unregister.fullFormat</td></tr> <tr><td>com.vmware.vim.vsm.provider.update</td><td></td><td>com.vmware.vim.vsm.provider.update|event.com.vmware.vim.vsm.provider.update.fullFormat</td></tr> <tr><td>esx.audit.dcui.defaults.factoryrestore</td><td>warning</td><td>esx.audit.dcui.defaults.factoryrestore|The host has been restored to default factory settings. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.</td></tr> <tr><td>esx.audit.dcui.disabled</td><td>info</td><td>esx.audit.dcui.disabled|The DCUI has been disabled.</td></tr> <tr><td>esx.audit.dcui.enabled</td><td>info</td><td>esx.audit.dcui.enabled|The DCUI has been enabled.</td></tr> <tr><td>esx.audit.dcui.host.reboot</td><td>warning</td><td>esx.audit.dcui.host.reboot|The host is being rebooted through the Direct Console User Interface (DCUI). Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.</td></tr> <tr><td>esx.audit.dcui.host.shutdown</td><td>warning</td><td>esx.audit.dcui.host.shutdown|The host is being shut down through the Direct Console User Interface (DCUI). Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.</td></tr> <tr><td>esx.audit.dcui.hostagents.restart</td><td>info</td><td>esx.audit.dcui.hostagents.restart|The management agents on the host are being restarted. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.</td></tr> <tr><td>esx.audit.dcui.login.failed</td><td>error</td><td>esx.audit.dcui.login.failed|Authentication of user {1} has failed. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.</td></tr> <tr><td>esx.audit.dcui.login.passwd.changed</td><td>info</td><td>esx.audit.dcui.login.passwd.changed|Login password for user {1} has been changed. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.</td></tr> <tr><td>esx.audit.dcui.network.factoryrestore</td><td>warning</td><td>esx.audit.dcui.network.factoryrestore|The host has been restored to factory network settings. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.</td></tr> <tr><td>esx.audit.dcui.network.restart</td><td>info</td><td>esx.audit.dcui.network.restart|A management interface {1} has been restarted. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.</td></tr> <tr><td>esx.audit.esxcli.host.poweroff</td><td>warning</td><td>esx.audit.esxcli.host.poweroff|The host is being powered off through esxcli. Reason for powering off: {1}. Please consult vSphere Documentation Center or follow the Ask VMware link for more information.</td></tr> <tr><td>esx.audit.esxcli.host.restart</td><td></td><td>esx.audit.esxcli.host.restart|event.esx.audit.esxcli.host.restart.fullFormat</td></tr> <tr><td>esx.audit.esximage.hostacceptance.changed</td><td>info</td><td>esx.audit.esximage.hostacceptance.changed|Host acceptance level changed from {1} to {2}</td></tr> <tr><td>esx.audit.esximage.install.novalidation</td><td>warning</td><td>esx.audit.esximage.install.novalidation|Attempting to install an image profile with validation disabled. This may result in an image with unsatisfied dependencies, file or package conflicts, and potential security violations.</td></tr> <tr><td>esx.audit.esximage.install.securityalert</td><td>warning</td><td>esx.audit.esximage.install.securityalert|SECURITY ALERT: Installing image profile &#39;{1}&#39; with {2}.</td></tr> <tr><td>esx.audit.esximage.profile.install.successful</td><td>info</td><td>esx.audit.esximage.profile.install.successful|Successfully installed image profile &#39;{1}&#39;. Installed {2} VIB(s), removed {3} VIB(s). Please use &#39;esxcli software profile get&#39; or see log for more detail about the transaction.</td></tr> <tr><td>esx.audit.esximage.profile.update.successful</td><td>info</td><td>esx.audit.esximage.profile.update.successful|Successfully updated host to image profile &#39;{1}&#39;. Installed {2} VIB(s), removed {3} VIB(s). Please use &#39;esxcli software profile get&#39; or see log for more detail about the transaction.</td></tr> <tr><td>esx.audit.esximage.vib.install.successful</td><td>info</td><td>esx.audit.esximage.vib.install.successful|Successfully installed {1} VIB(s), removed {2} VIB(s). Please use &#39;esxcli software profile get&#39; or see log for more detail about the transaction.</td></tr> <tr><td>esx.audit.esximage.vib.remove.successful</td><td>info</td><td>esx.audit.esximage.vib.remove.successful|Successfully removed {1} VIB(s). Please use &#39;esxcli software profile get&#39; or see log for more detail about the transaction.</td></tr> <tr><td>esx.audit.host.boot</td><td>info</td><td>esx.audit.host.boot|Host has booted.</td></tr> <tr><td>esx.audit.host.maxRegisteredVMsExceeded</td><td>warning</td><td>esx.audit.host.maxRegisteredVMsExceeded|The number of virtual machines registered on host {host.name} in cluster {computeResource.name} in {datacenter.name} exceeded limit: {current} registered, {limit} is the maximum supported.</td></tr> <tr><td>esx.audit.host.stop.reboot</td><td>info</td><td>esx.audit.host.stop.reboot|Host is rebooting.</td></tr> <tr><td>esx.audit.host.stop.shutdown</td><td>info</td><td>esx.audit.host.stop.shutdown|Host is shutting down.</td></tr> <tr><td>esx.audit.lockdownmode.disabled</td><td>info</td><td>esx.audit.lockdownmode.disabled|Administrator access to the host has been enabled.</td></tr> <tr><td>esx.audit.lockdownmode.enabled</td><td>info</td><td>esx.audit.lockdownmode.enabled|Administrator access to the host has been disabled.</td></tr> <tr><td>esx.audit.maintenancemode.canceled</td><td>info</td><td>esx.audit.maintenancemode.canceled|The host has canceled entering maintenance mode.</td></tr> <tr><td>esx.audit.maintenancemode.entered</td><td>info</td><td>esx.audit.maintenancemode.entered|The host has entered maintenance mode.</td></tr> <tr><td>esx.audit.maintenancemode.entering</td><td>info</td><td>esx.audit.maintenancemode.entering|The host has begun entering maintenance mode.</td></tr> <tr><td>esx.audit.maintenancemode.exited</td><td>info</td><td>esx.audit.maintenancemode.exited|The host has exited maintenance mode.</td></tr> <tr><td>esx.audit.net.firewall.config.changed</td><td>info</td><td>esx.audit.net.firewall.config.changed|Firewall configuration has changed. Operation &#39;{1}&#39; for rule set {2} succeeded.</td></tr> <tr><td>esx.audit.net.firewall.disabled</td><td>warning</td><td>esx.audit.net.firewall.disabled|Firewall has been disabled.</td></tr> <tr><td>esx.audit.net.firewall.enabled</td><td>info</td><td>esx.audit.net.firewall.enabled|Firewall has been enabled for port {1}.</td></tr> <tr><td>esx.audit.net.firewall.port.hooked</td><td>info</td><td>esx.audit.net.firewall.port.hooked|Port {1} is now protected by Firewall.</td></tr> <tr><td>esx.audit.net.firewall.port.removed</td><td>warning</td><td>esx.audit.net.firewall.port.removed|Port {1} is no longer protected with Firewall.</td></tr> <tr><td>esx.audit.net.lacp.disable</td><td>info</td><td>esx.audit.net.lacp.disable|LACP for VDS {1} is disabled.</td></tr> <tr><td>esx.audit.net.lacp.enable</td><td>info</td><td>esx.audit.net.lacp.enable|LACP for VDS {1} is enabled.</td></tr> <tr><td>esx.audit.net.lacp.uplink.connected</td><td>info</td><td>esx.audit.net.lacp.uplink.connected|Lacp info: uplink {1} on VDS {2} got connected.</td></tr> <tr><td>esx.audit.shell.disabled</td><td>info</td><td>esx.audit.shell.disabled|The ESXi command line shell has been disabled.</td></tr> <tr><td>esx.audit.shell.enabled</td><td>info</td><td>esx.audit.shell.enabled|The ESXi command line shell has been enabled.</td></tr> <tr><td>esx.audit.ssh.disabled</td><td>info</td><td>esx.audit.ssh.disabled|SSH access has been disabled.</td></tr> <tr><td>esx.audit.ssh.enabled</td><td>info</td><td>esx.audit.ssh.enabled|SSH access has been enabled.</td></tr> <tr><td>esx.audit.usb.config.changed</td><td>info</td><td>esx.audit.usb.config.changed|USB configuration has changed on host {host.name} in cluster {computeResource.name} in {datacenter.name}.</td></tr> <tr><td>esx.audit.uw.secpolicy.alldomains.level.changed</td><td>warning</td><td>esx.audit.uw.secpolicy.alldomains.level.changed|The enforcement level for all security domains has been changed to {1}. The enforcement level must always be set to enforcing.</td></tr> <tr><td>esx.audit.uw.secpolicy.domain.level.changed</td><td>warning</td><td>esx.audit.uw.secpolicy.domain.level.changed|The enforcement level for security domain {1} has been changed to {2}. The enforcement level must always be set to enforcing.</td></tr> <tr><td>esx.audit.vmfs.lvm.device.discovered</td><td>info</td><td>esx.audit.vmfs.lvm.device.discovered|One or more LVM devices have been discovered on this host.</td></tr> <tr><td>esx.audit.vmfs.volume.mounted</td><td>info</td><td>esx.audit.vmfs.volume.mounted|File system {1} on volume {2} has been mounted in {3} mode on this host.</td></tr> <tr><td>esx.audit.vmfs.volume.umounted</td><td>info</td><td>esx.audit.vmfs.volume.umounted|The volume {1} has been safely un-mounted. The datastore is no longer accessible on this host.</td></tr> <tr><td>esx.clear.coredump.configured</td><td>info</td><td>esx.clear.coredump.configured|A vmkcore disk partition is available and/or a network coredump server has been configured. Host core dumps will be saved.</td></tr> <tr><td>esx.clear.net.connectivity.restored</td><td>info</td><td>esx.clear.net.connectivity.restored|Network connectivity restored on virtual switch {1}, portgroups: {2}. Physical NIC {3} is up.</td></tr> <tr><td>esx.clear.net.dvport.connectivity.restored</td><td>info</td><td>esx.clear.net.dvport.connectivity.restored|Network connectivity restored on DVPorts: {1}. Physical NIC {2} is up.</td></tr> <tr><td>esx.clear.net.dvport.redundancy.restored</td><td>info</td><td>esx.clear.net.dvport.redundancy.restored|Uplink redundancy restored on DVPorts: {1}. Physical NIC {2} is up.</td></tr> <tr><td>esx.clear.net.lacp.uplink.transition.up</td><td>info</td><td>esx.clear.net.lacp.uplink.transition.up|Lacp info: uplink {1} on VDS {2} is moved into link aggregation group.</td></tr> <tr><td>esx.clear.net.lacp.uplink.unblocked</td><td>info</td><td>esx.clear.net.lacp.uplink.unblocked|Lacp error: uplink {1} on VDS {2} is unblocked.</td></tr> <tr><td>esx.clear.net.redundancy.restored</td><td>info</td><td>esx.clear.net.redundancy.restored|Uplink redundancy restored on virtual switch {1}, portgroups: {2}. Physical NIC {3} is up.</td></tr> <tr><td>esx.clear.net.vmnic.linkstate.up</td><td>info</td><td>esx.clear.net.vmnic.linkstate.up|Physical NIC {1} linkstate is up.</td></tr> <tr><td>esx.clear.scsi.device.io.latency.improved</td><td>info</td><td>esx.clear.scsi.device.io.latency.improved|Device {1} performance has improved. I/O latency reduced from {2} microseconds to {3} microseconds.</td></tr> <tr><td>esx.clear.scsi.device.state.on</td><td>info</td><td>esx.clear.scsi.device.state.on|Device {1}, has been turned on administratively.</td></tr> <tr><td>esx.clear.scsi.device.state.permanentloss.deviceonline</td><td>info</td><td>esx.clear.scsi.device.state.permanentloss.deviceonline|Device {1}, that was permanently inaccessible is now online. No data consistency guarantees.</td></tr> <tr><td>esx.clear.storage.apd.exit</td><td>info</td><td>esx.clear.storage.apd.exit|Device or filesystem with identifer [{1}] has exited the All Paths Down state.</td></tr> <tr><td>esx.clear.storage.connectivity.restored</td><td>info</td><td>esx.clear.storage.connectivity.restored|Connectivity to storage device {1} (Datastores: {2}) restored. Path {3} is active again.</td></tr> <tr><td>esx.clear.storage.redundancy.restored</td><td>info</td><td>esx.clear.storage.redundancy.restored|Path redundancy to storage device {1} (Datastores: {2}) restored. Path {3} is active again.</td></tr> <tr><td>esx.problem.3rdParty.error</td><td>error</td><td>esx.problem.3rdParty.error|A 3rd party component, {1}, running on ESXi has reported an error. Please follow the knowledge base link ({2}) to see the steps to remedy the problem as reported by {3}. The message reported is: {4}.</td></tr> <tr><td>esx.problem.3rdParty.info</td><td></td><td>esx.problem.3rdParty.info|event.esx.problem.3rdParty.info.fullFormat</td></tr> <tr><td>esx.problem.3rdParty.warning</td><td>warning</td><td>esx.problem.3rdParty.warning|A 3rd party component, {1}, running on ESXi has reported a warning related to a problem. Please follow the knowledge base link ({2}) to see the steps to remedy the problem as reported by {3}. The message reported is: {4}.</td></tr> <tr><td>esx.problem.apei.bert.memory.error.corrected</td><td>error</td><td>esx.problem.apei.bert.memory.error.corrected|A corrected memory error occurred in last boot. The following details were reported. Physical Addr: {1}, Physical Addr Mask: {2}, Node: {3}, Card: {4}, Module: {5}, Bank: {6}, Device: {7}, Row: {8}, Column: {9} Error type: {10}</td></tr> <tr><td>esx.problem.apei.bert.memory.error.fatal</td><td>error</td><td>esx.problem.apei.bert.memory.error.fatal|A fatal memory error occurred in the last boot. The following details were reported. Physical Addr: {1}, Physical Addr Mask: {2}, Node: {3}, Card: {4}, Module: {5}, Bank: {6}, Device: {7}, Row: {8}, Column: {9} Error type: {10}</td></tr> <tr><td>esx.problem.apei.bert.memory.error.recoverable</td><td>error</td><td>esx.problem.apei.bert.memory.error.recoverable|A recoverable memory error occurred in last boot. The following details were reported. Physical Addr: {1}, Physical Addr Mask: {2}, Node: {3}, Card: {4}, Module: {5}, Bank: {6}, Device: {7}, Row: {8}, Column: {9} Error type: {10}</td></tr> <tr><td>esx.problem.apei.bert.pcie.error.corrected</td><td>error</td><td>esx.problem.apei.bert.pcie.error.corrected|A corrected PCIe error occurred in last boot. The following details were reported. Port Type: {1}, Device: {2}, Bus #: {3}, Function: {4}, Slot: {5}, Device Vendor: {6}, Version: {7}, Command Register: {8}, Status Register: {9}.</td></tr> <tr><td>esx.problem.apei.bert.pcie.error.fatal</td><td>error</td><td>esx.problem.apei.bert.pcie.error.fatal|Platform encounterd a fatal PCIe error in last boot. The following details were reported. Port Type: {1}, Device: {2}, Bus #: {3}, Function: {4}, Slot: {5}, Device Vendor: {6}, Version: {7}, Command Register: {8}, Status Register: {9}.</td></tr> <tr><td>esx.problem.apei.bert.pcie.error.recoverable</td><td>error</td><td>esx.problem.apei.bert.pcie.error.recoverable|A recoverable PCIe error occurred in last boot. The following details were reported. Port Type: {1}, Device: {2}, Bus #: {3}, Function: {4}, Slot: {5}, Device Vendor: {6}, Version: {7}, Command Register: {8}, Status Register: {9}.</td></tr> <tr><td>esx.problem.application.core.dumped</td><td>warning</td><td>esx.problem.application.core.dumped|An application ({1}) running on ESXi host has crashed ({2} time(s) so far). A core file might have been created at {3}.</td></tr> <tr><td>esx.problem.coredump.unconfigured</td><td>warning</td><td>esx.problem.coredump.unconfigured|No vmkcore disk partition is available and no network coredump server has been configured. Host core dumps cannot be saved.</td></tr> <tr><td>esx.problem.cpu.amd.mce.dram.disabled</td><td>error</td><td>esx.problem.cpu.amd.mce.dram.disabled|DRAM ECC not enabled. Please enable it in BIOS.</td></tr> <tr><td>esx.problem.cpu.intel.ioapic.listing.error</td><td>error</td><td>esx.problem.cpu.intel.ioapic.listing.error|Not all IO-APICs are listed in the DMAR. Not enabling interrupt remapping on this platform. </td></tr> <tr><td>esx.problem.cpu.mce.invalid</td><td>error</td><td>esx.problem.cpu.mce.invalid|MCE monitoring will be disabled as an unsupported CPU was detected. Please consult the ESX HCL for information on supported hardware.</td></tr> <tr><td>esx.problem.cpu.smp.ht.invalid</td><td>error</td><td>esx.problem.cpu.smp.ht.invalid|Disabling HyperThreading due to invalid configuration: Number of threads: {1}, Number of PCPUs: {2}.</td></tr> <tr><td>esx.problem.cpu.smp.ht.numpcpus.max</td><td>error</td><td>esx.problem.cpu.smp.ht.numpcpus.max|Found {1} PCPUs, but only using {2} of them due to specified limit.</td></tr> <tr><td>esx.problem.cpu.smp.ht.partner.missing</td><td>error</td><td>esx.problem.cpu.smp.ht.partner.missing|Disabling HyperThreading due to invalid configuration: HT partner {1} is missing from PCPU {2}.</td></tr> <tr><td>esx.problem.dhclient.lease.none</td><td>error</td><td>esx.problem.dhclient.lease.none|Unable to obtain a DHCP lease on interface {1}.</td></tr> <tr><td>esx.problem.dhclient.lease.offered.error</td><td></td><td>esx.problem.dhclient.lease.offered.error|event.esx.problem.dhclient.lease.offered.error.fullFormat</td></tr> <tr><td>esx.problem.esximage.install.error</td><td>error</td><td>esx.problem.esximage.install.error|Could not install image profile: {1}</td></tr> <tr><td>esx.problem.esximage.install.invalidhardware</td><td>error</td><td>esx.problem.esximage.install.invalidhardware|Host doesn&#39;t meet image profile &#39;{1}&#39; hardware requirements: {2}</td></tr> <tr><td>esx.problem.esximage.install.stage.error</td><td>error</td><td>esx.problem.esximage.install.stage.error|Could not stage image profile &#39;{1}&#39;: {2}</td></tr> <tr><td>esx.problem.hardware.acpi.interrupt.routing.device.invalid</td><td>error</td><td>esx.problem.hardware.acpi.interrupt.routing.device.invalid|Skipping interrupt routing entry with bad device number: {1}. This is a BIOS bug.</td></tr> <tr><td>esx.problem.hardware.acpi.interrupt.routing.pin.invalid</td><td>error</td><td>esx.problem.hardware.acpi.interrupt.routing.pin.invalid|Skipping interrupt routing entry with bad device pin: {1}. This is a BIOS bug.</td></tr> <tr><td>esx.problem.hardware.ioapic.missing</td><td>error</td><td>esx.problem.hardware.ioapic.missing|IOAPIC Num {1} is missing. Please check BIOS settings to enable this IOAPIC.</td></tr> <tr><td>esx.problem.host.coredump</td><td>warning</td><td>esx.problem.host.coredump|An unread host kernel core dump has been found.</td></tr> <tr><td>esx.problem.hostd.core.dumped</td><td>warning</td><td>esx.problem.hostd.core.dumped|{1} crashed ({2} time(s) so far) and a core file might have been created at {3}. This might have caused connections to the host to be dropped.</td></tr> <tr><td>esx.problem.iorm.badversion</td><td>info</td><td>esx.problem.iorm.badversion|Host {1} cannot participate in Storage I/O Control(SIOC) on datastore {2} because the version number {3} of the SIOC agent on this host is incompatible with number {4} of its counterparts on other hosts connected to this datastore.</td></tr> <tr><td>esx.problem.iorm.nonviworkload</td><td>info</td><td>esx.problem.iorm.nonviworkload|An unmanaged I/O workload is detected on a SIOC-enabled datastore: {1}.</td></tr> <tr><td>esx.problem.migrate.vmotion.default.heap.create.failed</td><td>warning</td><td>esx.problem.migrate.vmotion.default.heap.create.failed|Failed to create default migration heap. This might be the result of severe host memory pressure or virtual address space exhaustion. Migration might still be possible, but will be unreliable in cases of extreme host memory pressure.</td></tr> <tr><td>esx.problem.migrate.vmotion.server.pending.cnx.listen.socket.shutdown</td><td>error</td><td>esx.problem.migrate.vmotion.server.pending.cnx.listen.socket.shutdown|The ESXi host&#39;s vMotion network server encountered an error while monitoring incoming network connections. Shutting down listener socket. vMotion might not be possible with this host until vMotion is manually re-enabled. Failure status: {1}</td></tr> <tr><td>esx.problem.net.connectivity.lost</td><td>error</td><td>esx.problem.net.connectivity.lost|Lost network connectivity on virtual switch {1}. Physical NIC {2} is down. Affected portgroups:{3}.</td></tr> <tr><td>esx.problem.net.dvport.connectivity.lost</td><td>error</td><td>esx.problem.net.dvport.connectivity.lost|Lost network connectivity on DVPorts: {1}. Physical NIC {2} is down.</td></tr> <tr><td>esx.problem.net.dvport.redundancy.degraded</td><td>warning</td><td>esx.problem.net.dvport.redundancy.degraded|Uplink redundancy degraded on DVPorts: {1}. Physical NIC {2} is down.</td></tr> <tr><td>esx.problem.net.dvport.redundancy.lost</td><td>warning</td><td>esx.problem.net.dvport.redundancy.lost|Lost uplink redundancy on DVPorts: {1}. Physical NIC {2} is down.</td></tr> <tr><td>esx.problem.net.e1000.tso6.notsupported</td><td>error</td><td>esx.problem.net.e1000.tso6.notsupported|Guest-initiated IPv6 TCP Segmentation Offload (TSO) packets ignored. Manually disable TSO inside the guest operating system in virtual machine {1}, or use a different virtual adapter.</td></tr> <tr><td>esx.problem.net.fence.port.badfenceid</td><td>error</td><td>esx.problem.net.fence.port.badfenceid|VMkernel failed to set fenceId {1} on distributed virtual port {2} on switch {3}. Reason: invalid fenceId.</td></tr> <tr><td>esx.problem.net.fence.resource.limited</td><td>error</td><td>esx.problem.net.fence.resource.limited|Vmkernel failed to set fenceId {1} on distributed virtual port {2} on switch {3}. Reason: maximum number of fence networks or ports have been reached.</td></tr> <tr><td>esx.problem.net.fence.switch.unavailable</td><td>error</td><td>esx.problem.net.fence.switch.unavailable|Vmkernel failed to set fenceId {1} on distributed virtual port {2} on switch {3}. Reason: dvSwitch fence property is not set.</td></tr> <tr><td>esx.problem.net.firewall.config.failed</td><td>error</td><td>esx.problem.net.firewall.config.failed|Firewall configuration operation &#39;{1}&#39; failed. The changes were not applied to rule set {2}.</td></tr> <tr><td>esx.problem.net.firewall.port.hookfailed</td><td>error</td><td>esx.problem.net.firewall.port.hookfailed|Adding port {1} to Firewall failed.</td></tr> <tr><td>esx.problem.net.gateway.set.failed</td><td>error</td><td>esx.problem.net.gateway.set.failed|Cannot connect to the specified gateway {1}. Failed to set it.</td></tr> <tr><td>esx.problem.net.heap.belowthreshold</td><td>warning</td><td>esx.problem.net.heap.belowthreshold|{1} free size dropped below {2} percent.</td></tr> <tr><td>esx.problem.net.lacp.peer.noresponse</td><td>error</td><td>esx.problem.net.lacp.peer.noresponse|Lacp error: No peer response on uplink {1} for VDS {2}.</td></tr> <tr><td>esx.problem.net.lacp.policy.incompatible</td><td>error</td><td>esx.problem.net.lacp.policy.incompatible|Lacp error: Current teaming policy on VDS {1} is incompatible, supported is IP hash only.</td></tr> <tr><td>esx.problem.net.lacp.policy.linkstatus</td><td>error</td><td>esx.problem.net.lacp.policy.linkstatus|Lacp error: Current teaming policy on VDS {1} is incompatible, supported link failover detection is link status only.</td></tr> <tr><td>esx.problem.net.lacp.uplink.blocked</td><td>warning</td><td>esx.problem.net.lacp.uplink.blocked|Lacp warning: uplink {1} on VDS {2} is blocked.</td></tr> <tr><td>esx.problem.net.lacp.uplink.disconnected</td><td>warning</td><td>esx.problem.net.lacp.uplink.disconnected|Lacp warning: uplink {1} on VDS {2} got disconnected.</td></tr> <tr><td>esx.problem.net.lacp.uplink.fail.duplex</td><td>error</td><td>esx.problem.net.lacp.uplink.fail.duplex|Lacp error: Duplex mode across all uplink ports must be full, VDS {1} uplink {2} has different mode.</td></tr> <tr><td>esx.problem.net.lacp.uplink.fail.speed</td><td>error</td><td>esx.problem.net.lacp.uplink.fail.speed|Lacp error: Speed across all uplink ports must be same, VDS {1} uplink {2} has different speed.</td></tr> <tr><td>esx.problem.net.lacp.uplink.inactive</td><td>error</td><td>esx.problem.net.lacp.uplink.inactive|Lacp error: All uplinks on VDS {1} must be active.</td></tr> <tr><td>esx.problem.net.lacp.uplink.transition.down</td><td>warning</td><td>esx.problem.net.lacp.uplink.transition.down|Lacp warning: uplink {1} on VDS {2} is moved out of link aggregation group.</td></tr> <tr><td>esx.problem.net.migrate.bindtovmk</td><td>warning</td><td>esx.problem.net.migrate.bindtovmk|The ESX advanced configuration option /Migrate/Vmknic is set to an invalid vmknic: {1}. /Migrate/Vmknic specifies a vmknic that vMotion binds to for improved performance. Update the configuration option with a valid vmknic. Alternatively, if you do not want vMotion to bind to a specific vmknic, remove the invalid vmknic and leave the option blank.</td></tr> <tr><td>esx.problem.net.migrate.unsupported.latency</td><td>warning</td><td>esx.problem.net.migrate.unsupported.latency|ESXi has detected {1}ms round-trip vMotion network latency between host {2} and {3}. High latency vMotion networks are supported only if both ESXi hosts have been configured for vMotion latency tolerance.</td></tr> <tr><td>esx.problem.net.portset.port.full</td><td>error</td><td>esx.problem.net.portset.port.full|Portset {1} has reached the maximum number of ports ({2}). Cannot apply for any more free ports.</td></tr> <tr><td>esx.problem.net.portset.port.vlan.invalidid</td><td>error</td><td>esx.problem.net.portset.port.vlan.invalidid|{1} VLANID {2} is invalid. VLAN ID must be between 0 and 4095.</td></tr> <tr><td>esx.problem.net.proxyswitch.port.unavailable</td><td>warning</td><td>esx.problem.net.proxyswitch.port.unavailable|Virtual NIC with hardware address {1} failed to connect to distributed virtual port {2} on switch {3}. There are no more ports available on the host proxy switch.</td></tr> <tr><td>esx.problem.net.redundancy.degraded</td><td>warning</td><td>esx.problem.net.redundancy.degraded|Uplink redundancy degraded on virtual switch {1}. Physical NIC {2} is down. Affected portgroups:{3}.</td></tr> <tr><td>esx.problem.net.redundancy.lost</td><td>warning</td><td>esx.problem.net.redundancy.lost|Lost uplink redundancy on virtual switch {1}. Physical NIC {2} is down. Affected portgroups:{3}.</td></tr> <tr><td>esx.problem.net.uplink.mtu.failed</td><td>warning</td><td>esx.problem.net.uplink.mtu.failed|VMkernel failed to set the MTU value {1} on the uplink {2}.</td></tr> <tr><td>esx.problem.net.vmknic.ip.duplicate</td><td>warning</td><td>esx.problem.net.vmknic.ip.duplicate|A duplicate IP address was detected for {1} on the interface {2}. The current owner is {3}.</td></tr> <tr><td>esx.problem.net.vmnic.linkstate.down</td><td>warning</td><td>esx.problem.net.vmnic.linkstate.down|Physical NIC {1} linkstate is down.</td></tr> <tr><td>esx.problem.net.vmnic.linkstate.flapping</td><td>warning</td><td>esx.problem.net.vmnic.linkstate.flapping|Taking down physical NIC {1} because the link is unstable.</td></tr> <tr><td>esx.problem.net.vmnic.watchdog.reset</td><td>warning</td><td>esx.problem.net.vmnic.watchdog.reset|Uplink {1} has recovered from a transient failure due to watchdog timeout</td></tr> <tr><td>esx.problem.ntpd.clock.correction.error</td><td>error</td><td>esx.problem.ntpd.clock.correction.error|NTP daemon stopped. Time correction {1} &gt; {2} seconds. Manually set the time and restart ntpd.</td></tr> <tr><td>esx.problem.pageretire.platform.retire.request</td><td>info</td><td>esx.problem.pageretire.platform.retire.request|Memory page retirement requested by platform firmware. FRU ID: {1}. Refer to System Hardware Log: {2}</td></tr> <tr><td>esx.problem.pageretire.selectedmpnthreshold.host.exceeded</td><td>warning</td><td>esx.problem.pageretire.selectedmpnthreshold.host.exceeded|Number of host physical memory pages that have been selected for retirement ({1}) exceeds threshold ({2}).</td></tr> <tr><td>esx.problem.scsi.apd.event.descriptor.alloc.failed</td><td>warning</td><td>esx.problem.scsi.apd.event.descriptor.alloc.failed|No memory to allocate APD (All Paths Down) event subsystem.</td></tr> <tr><td>esx.problem.scsi.device.close.failed</td><td>warning</td><td>esx.problem.scsi.device.close.failed|&quot;Failed to close the device {1} properly, plugin {2}.</td></tr> <tr><td>esx.problem.scsi.device.detach.failed</td><td>warning</td><td>esx.problem.scsi.device.detach.failed|Detach failed for device :{1}. Exceeded the number of devices that can be detached, please cleanup stale detach entries.</td></tr> <tr><td>esx.problem.scsi.device.filter.attach.failed</td><td>warning</td><td>esx.problem.scsi.device.filter.attach.failed|Failed to attach filters to device &#39;%s&#39; during registration. Plugin load failed or the filter rules are incorrect.</td></tr> <tr><td>esx.problem.scsi.device.io.bad.plugin.type</td><td>warning</td><td>esx.problem.scsi.device.io.bad.plugin.type|Bad plugin type for device {1}, plugin {2}</td></tr> <tr><td>esx.problem.scsi.device.io.inquiry.failed</td><td>warning</td><td>esx.problem.scsi.device.io.inquiry.failed|Failed to get standard inquiry for device {1} from Plugin {2}.</td></tr> <tr><td>esx.problem.scsi.device.io.invalid.disk.qfull.value</td><td>warning</td><td>esx.problem.scsi.device.io.invalid.disk.qfull.value|QFullSampleSize should be bigger than QFullThreshold. LUN queue depth throttling algorithm will not function as expected. Please set the QFullSampleSize and QFullThreshold disk configuration values in ESX correctly.</td></tr> <tr><td>esx.problem.scsi.device.io.latency.high</td><td>warning</td><td>esx.problem.scsi.device.io.latency.high|Device {1} performance has deteriorated. I/O latency increased from average value of {2} microseconds to {3} microseconds.</td></tr> <tr><td>esx.problem.scsi.device.io.qerr.change.config</td><td>warning</td><td>esx.problem.scsi.device.io.qerr.change.config|QErr set to 0x{1} for device {2}. This may cause unexpected behavior. The system is not configured to change the QErr setting of device. The QErr value supported by system is 0x{3}. Please check the SCSI ChangeQErrSetting configuration value for ESX.</td></tr> <tr><td>esx.problem.scsi.device.io.qerr.changed</td><td>warning</td><td>esx.problem.scsi.device.io.qerr.changed|QErr set to 0x{1} for device {2}. This may cause unexpected behavior. The device was originally configured to the supported QErr setting of 0x{3}, but this has been changed and could not be changed back.</td></tr> <tr><td>esx.problem.scsi.device.is.local.failed</td><td>warning</td><td>esx.problem.scsi.device.is.local.failed|Failed to verify if the device {1} from plugin {2} is a local - not shared - device</td></tr> <tr><td>esx.problem.scsi.device.is.pseudo.failed</td><td>warning</td><td>esx.problem.scsi.device.is.pseudo.failed|Failed to verify if the device {1} from plugin {2} is a pseudo device</td></tr> <tr><td>esx.problem.scsi.device.is.ssd.failed</td><td>warning</td><td>esx.problem.scsi.device.is.ssd.failed|Failed to verify if the device {1} from plugin {2} is a Solid State Disk device</td></tr> <tr><td>esx.problem.scsi.device.limitreached</td><td>error</td><td>esx.problem.scsi.device.limitreached|The maximum number of supported devices of {1} has been reached. A device from plugin {2} could not be created.</td></tr> <tr><td>esx.problem.scsi.device.state.off</td><td>info</td><td>esx.problem.scsi.device.state.off|Device {1}, has been turned off administratively.</td></tr> <tr><td>esx.problem.scsi.device.state.permanentloss</td><td>error</td><td>esx.problem.scsi.device.state.permanentloss|Device {1} has been removed or is permanently inaccessible. Affected datastores (if any): {2}.</td></tr> <tr><td>esx.problem.scsi.device.state.permanentloss.noopens</td><td>info</td><td>esx.problem.scsi.device.state.permanentloss.noopens|Permanently inaccessible device {1} has no more opens. It is now safe to unmount datastores (if any) {2} and delete the device.</td></tr> <tr><td>esx.problem.scsi.device.state.permanentloss.pluggedback</td><td>error</td><td>esx.problem.scsi.device.state.permanentloss.pluggedback|Device {1} has been plugged back in after being marked permanently inaccessible. No data consistency guarantees.</td></tr> <tr><td>esx.problem.scsi.device.state.permanentloss.withreservationheld</td><td>error</td><td>esx.problem.scsi.device.state.permanentloss.withreservationheld|Device {1} has been removed or is permanently inaccessible, while holding a reservation. Affected datastores (if any): {2}.</td></tr> <tr><td>esx.problem.scsi.device.thinprov.atquota</td><td>warning</td><td>esx.problem.scsi.device.thinprov.atquota|Space utilization on thin-provisioned device {1} exceeded configured threshold. Affected datastores (if any): {2}.</td></tr> <tr><td>esx.problem.scsi.scsipath.limitreached</td><td>error</td><td>esx.problem.scsi.scsipath.limitreached|The maximum number of supported paths of {1} has been reached. Path {2} could not be added.</td></tr> <tr><td>esx.problem.scsi.unsupported.plugin.type</td><td>warning</td><td>esx.problem.scsi.unsupported.plugin.type|Scsi Device Allocation not supported for plugin type {1}</td></tr> <tr><td>esx.problem.storage.apd.start</td><td>warning</td><td>esx.problem.storage.apd.start|Device or filesystem with identifer [{1}] has entered the All Paths Down state.</td></tr> <tr><td>esx.problem.storage.apd.timeout</td><td>warning</td><td>esx.problem.storage.apd.timeout|Device or filesystem with identifer [{1}] has entered the All Paths Down Timeout state after being in the All Paths Down state for {2} seconds. I/Os will be fast failed.</td></tr> <tr><td>esx.problem.storage.connectivity.devicepor</td><td>warning</td><td>esx.problem.storage.connectivity.devicepor|Frequent PowerOn Reset Unit Attentions are occurring on device {1}. This might indicate a storage problem. Affected datastores: {2}</td></tr> <tr><td>esx.problem.storage.connectivity.lost</td><td>error</td><td>esx.problem.storage.connectivity.lost|Lost connectivity to storage device {1}. Path {2} is down. Affected datastores: {3}.</td></tr> <tr><td>esx.problem.storage.connectivity.pathpor</td><td>warning</td><td>esx.problem.storage.connectivity.pathpor|Frequent PowerOn Reset Unit Attentions are occurring on path {1}. This might indicate a storage problem. Affected device: {2}. Affected datastores: {3}</td></tr> <tr><td>esx.problem.storage.connectivity.pathstatechanges</td><td>warning</td><td>esx.problem.storage.connectivity.pathstatechanges|Frequent path state changes are occurring for path {1}. This might indicate a storage problem. Affected device: {2}. Affected datastores: {3}</td></tr> <tr><td>esx.problem.storage.iscsi.discovery.connect.error</td><td>error</td><td>esx.problem.storage.iscsi.discovery.connect.error|iSCSI discovery to {1} on {2} failed. The iSCSI Initiator could not establish a network connection to the discovery address.</td></tr> <tr><td>esx.problem.storage.iscsi.discovery.login.error</td><td>error</td><td>esx.problem.storage.iscsi.discovery.login.error|iSCSI discovery to {1} on {2} failed. The Discovery target returned a login error of: {3}.</td></tr> <tr><td>esx.problem.storage.iscsi.target.connect.error</td><td>error</td><td>esx.problem.storage.iscsi.target.connect.error|Login to iSCSI target {1} on {2} failed. The iSCSI initiator could not establish a network connection to the target.</td></tr> <tr><td>esx.problem.storage.iscsi.target.login.error</td><td>error</td><td>esx.problem.storage.iscsi.target.login.error|Login to iSCSI target {1} on {2} failed. Target returned login error of: {3}.</td></tr> <tr><td>esx.problem.storage.iscsi.target.permanently.lost</td><td>error</td><td>esx.problem.storage.iscsi.target.permanently.lost|The iSCSI target {2} was permanently removed from {1}.</td></tr> <tr><td>esx.problem.storage.redundancy.degraded</td><td>warning</td><td>esx.problem.storage.redundancy.degraded|Path redundancy to storage device {1} degraded. Path {2} is down. Affected datastores: {3}.</td></tr> <tr><td>esx.problem.storage.redundancy.lost</td><td>warning</td><td>esx.problem.storage.redundancy.lost|Lost path redundancy to storage device {1}. Path {2} is down. Affected datastores: {3}.</td></tr> <tr><td>esx.problem.syslog.config</td><td>warning</td><td>esx.problem.syslog.config|System logging is not configured on host {host.name}. Please check Syslog options for the host under Configuration -&gt; Software -&gt; Advanced Settings in vSphere client.</td></tr> <tr><td>esx.problem.syslog.nonpersistent</td><td>warning</td><td>esx.problem.syslog.nonpersistent|System logs on host {host.name} are stored on non-persistent storage. Consult product documentation to configure a syslog server or a scratch partition.</td></tr> <tr><td>esx.problem.vfat.filesystem.full.other</td><td>error</td><td>esx.problem.vfat.filesystem.full.other|The VFAT filesystem {1} (UUID {2}) is full.</td></tr> <tr><td>esx.problem.vfat.filesystem.full.scratch</td><td>error</td><td>esx.problem.vfat.filesystem.full.scratch|The host&#39;s scratch partition, which is the VFAT filesystem {1} (UUID {2}), is full.</td></tr> <tr><td>esx.problem.visorfs.failure</td><td>error</td><td>esx.problem.visorfs.failure|An operation on the root filesystem has failed.</td></tr> <tr><td>esx.problem.visorfs.inodetable.full</td><td>error</td><td>esx.problem.visorfs.inodetable.full|The root filesystem&#39;s file table is full. As a result, the file {1} could not be created by the application &#39;{2}&#39;.</td></tr> <tr><td>esx.problem.visorfs.ramdisk.full</td><td>error</td><td>esx.problem.visorfs.ramdisk.full|The ramdisk &#39;{1}&#39; is full. As a result, the file {2} could not be written.</td></tr> <tr><td>esx.problem.visorfs.ramdisk.inodetable.full</td><td>error</td><td>esx.problem.visorfs.ramdisk.inodetable.full|The file table of the ramdisk &#39;{1}&#39; is full. As a result, the file {2} could not be created by the application &#39;{3}&#39;.</td></tr> <tr><td>esx.problem.vm.kill.unexpected.fault.failure</td><td>error</td><td>esx.problem.vm.kill.unexpected.fault.failure|The VM using the config file {1} could not fault in a guest physical page from the hypervisor level swap file at {2}. The VM is terminated as further progress is impossible.</td></tr> <tr><td>esx.problem.vm.kill.unexpected.forcefulPageRetire</td><td>error</td><td>esx.problem.vm.kill.unexpected.forcefulPageRetire|The VM using the config file {1} contains the host physical page {2} which was scheduled for immediate retirement. To avoid system instability the VM is forcefully powered off.</td></tr> <tr><td>esx.problem.vm.kill.unexpected.noSwapResponse</td><td>error</td><td>esx.problem.vm.kill.unexpected.noSwapResponse|The VM using the config file {1} did not respond to {2} swap actions in {3} seconds and is forcefully powered off to prevent system instability.</td></tr> <tr><td>esx.problem.vm.kill.unexpected.vmtrack</td><td>error</td><td>esx.problem.vm.kill.unexpected.vmtrack|The VM using the config file {1} is allocating too many pages while system is critically low in free memory. It is forcefully terminated to prevent system instability.</td></tr> <tr><td>esx.problem.vmfs.ats.support.lost</td><td></td><td>esx.problem.vmfs.ats.support.lost|event.esx.problem.vmfs.ats.support.lost.fullFormat</td></tr> <tr><td>esx.problem.vmfs.error.volume.is.locked</td><td>error</td><td>esx.problem.vmfs.error.volume.is.locked|Volume on device {1} is locked, possibly because some remote host encountered an error during a volume operation and could not recover.</td></tr> <tr><td>esx.problem.vmfs.extent.offline</td><td>error</td><td>esx.problem.vmfs.extent.offline|An attached device {1} may be offline. The file system {2} is now in a degraded state. While the datastore is still available, parts of data that reside on the extent that went offline might be inaccessible.</td></tr> <tr><td>esx.problem.vmfs.extent.online</td><td>info</td><td>esx.problem.vmfs.extent.online|Device {1} backing file system {2} came online. This extent was previously offline. All resources on this device are now available.</td></tr> <tr><td>esx.problem.vmfs.heartbeat.recovered</td><td>info</td><td>esx.problem.vmfs.heartbeat.recovered|Successfully restored access to volume {1} ({2}) following connectivity issues.</td></tr> <tr><td>esx.problem.vmfs.heartbeat.timedout</td><td>info</td><td>esx.problem.vmfs.heartbeat.timedout|Lost access to volume {1} ({2}) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.</td></tr> <tr><td>esx.problem.vmfs.heartbeat.unrecoverable</td><td>error</td><td>esx.problem.vmfs.heartbeat.unrecoverable|Lost connectivity to volume {1} ({2}) and subsequent recovery attempts have failed.</td></tr> <tr><td>esx.problem.vmfs.journal.createfailed</td><td>error</td><td>esx.problem.vmfs.journal.createfailed|No space for journal on volume {1} ({2}). Opening volume in read-only metadata mode with limited write support.</td></tr> <tr><td>esx.problem.vmfs.lock.corruptondisk</td><td>error</td><td>esx.problem.vmfs.lock.corruptondisk|At least one corrupt on-disk lock was detected on volume {1} ({2}). Other regions of the volume might be damaged too.</td></tr> <tr><td>esx.problem.vmfs.nfs.server.disconnect</td><td>error</td><td>esx.problem.vmfs.nfs.server.disconnect|Lost connection to server {1} mount point {2} mounted as {3} ({4}).</td></tr> <tr><td>esx.problem.vmfs.nfs.server.restored</td><td>info</td><td>esx.problem.vmfs.nfs.server.restored|Restored connection to server {1} mount point {2} mounted as {3} ({4}).</td></tr> <tr><td>esx.problem.vmfs.resource.corruptondisk</td><td>error</td><td>esx.problem.vmfs.resource.corruptondisk|At least one corrupt resource metadata region was detected on volume {1} ({2}). Other regions of the volume might be damaged too.</td></tr> <tr><td>esx.problem.vmsyslogd.remote.failure</td><td>error</td><td>esx.problem.vmsyslogd.remote.failure|The host &quot;{1}&quot; has become unreachable. Remote logging to this host has stopped.</td></tr> <tr><td>esx.problem.vmsyslogd.storage.failure</td><td>error</td><td>esx.problem.vmsyslogd.storage.failure|Logging to storage has failed. Logs are no longer being stored locally on this host.</td></tr> <tr><td>esx.problem.vmsyslogd.storage.logdir.invalid</td><td>error</td><td>esx.problem.vmsyslogd.storage.logdir.invalid|The configured log directory {1} cannot be used. The default directory {2} will be used instead.</td></tr> <tr><td>esx.problem.vmsyslogd.unexpected</td><td>error</td><td>esx.problem.vmsyslogd.unexpected|Log daemon has failed for an unexpected reason: {1}</td></tr> <tr><td>esx.problem.vpxa.core.dumped</td><td>warning</td><td>esx.problem.vpxa.core.dumped|{1} crashed ({2} time(s) so far) and a core file might have been created at {3}. This might have caused connections to the host to be dropped.</td></tr> <tr><td>hbr.primary.AppQuiescedDeltaCompletedEvent</td><td>info</td><td>hbr.primary.AppQuiescedDeltaCompletedEvent|Application consistent delta completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({bytes} bytes transferred)</td></tr> <tr><td>hbr.primary.ConnectionRestoredToHbrServerEvent</td><td>info</td><td>hbr.primary.ConnectionRestoredToHbrServerEvent|Connection to VR Server restored for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}.</td></tr> <tr><td>hbr.primary.DeltaAbortedEvent</td><td>warning</td><td>hbr.primary.DeltaAbortedEvent|Delta aborted for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.hbr.primary.ReasonForDeltaAbort}</td></tr> <tr><td>hbr.primary.DeltaCompletedEvent</td><td>info</td><td>hbr.primary.DeltaCompletedEvent|Delta completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({bytes} bytes transferred).</td></tr> <tr><td>hbr.primary.DeltaStartedEvent</td><td>info</td><td>hbr.primary.DeltaStartedEvent|Delta started by {userName} for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}.</td></tr> <tr><td>hbr.primary.FSQuiescedDeltaCompletedEvent</td><td>warning</td><td>hbr.primary.FSQuiescedDeltaCompletedEvent|File system consistent delta completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({bytes} bytes transferred)</td></tr> <tr><td>hbr.primary.FailedToStartDeltaEvent</td><td>error</td><td>hbr.primary.FailedToStartDeltaEvent|Failed to start delta for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.fault.ReplicationVmFault.ReasonForFault}</td></tr> <tr><td>hbr.primary.FailedToStartSyncEvent</td><td>error</td><td>hbr.primary.FailedToStartSyncEvent|Failed to start full sync for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.fault.ReplicationVmFault.ReasonForFault}</td></tr> <tr><td>hbr.primary.InvalidDiskReplicationConfigurationEvent</td><td>error</td><td>hbr.primary.InvalidDiskReplicationConfigurationEvent|Replication configuration is invalid for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}, disk {diskKey}: {reasonForFault.@enum.fault.ReplicationDiskConfigFault.ReasonForFault}</td></tr> <tr><td>hbr.primary.InvalidVmReplicationConfigurationEvent</td><td>error</td><td>hbr.primary.InvalidVmReplicationConfigurationEvent|Replication configuration is invalid for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reasonForFault.@enum.fault.ReplicationVmConfigFault.ReasonForFault}</td></tr> <tr><td>hbr.primary.NoConnectionToHbrServerEvent</td><td>warning</td><td>hbr.primary.NoConnectionToHbrServerEvent|No connection to VR Server for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.hbr.primary.ReasonForNoServerConnection}</td></tr> <tr><td>hbr.primary.NoProgressWithHbrServerEvent</td><td>error</td><td>hbr.primary.NoProgressWithHbrServerEvent|VR Server error for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.hbr.primary.ReasonForNoServerProgress}</td></tr> <tr><td>hbr.primary.QuiesceNotSupported</td><td>warning</td><td>hbr.primary.QuiesceNotSupported|Quiescing is not supported for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}.</td></tr> <tr><td>hbr.primary.SyncCompletedEvent</td><td>info</td><td>hbr.primary.SyncCompletedEvent|Full sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({bytes} bytes transferred).</td></tr> <tr><td>hbr.primary.SyncStartedEvent</td><td>info</td><td>hbr.primary.SyncStartedEvent|Full sync started by {userName} for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}.</td></tr> <tr><td>hbr.primary.UnquiescedDeltaCompletedEvent</td><td>warning</td><td>hbr.primary.UnquiescedDeltaCompletedEvent|Delta completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({bytes} bytes transferred).</td></tr> <tr><td>hbr.primary.VmReplicationConfigurationChangedEvent</td><td>info</td><td>hbr.primary.VmReplicationConfigurationChangedEvent|Replication configuration changed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({numDisks} disks, {rpo} minutes RPO, VR Server is {vrServerAddress}:{vrServerPort}).</td></tr> <tr><td>AccountCreatedEvent</td><td>info</td><td>An account was created on host {host.name}</td></tr> <tr><td>AccountRemovedEvent</td><td>info</td><td>Account {account} was removed on host {host.name}</td></tr> <tr><td>AccountUpdatedEvent</td><td>info</td><td>An account was updated on host {host.name}</td></tr> <tr><td>AdminPasswordNotChangedEvent</td><td>info</td><td>The default password for the root user on the host {host.name} has not been changed</td></tr> <tr><td>AlarmAcknowledgedEvent</td><td>info</td><td>Acknowledged alarm &#39;{alarm.name}&#39; on {entity.name}</td></tr> <tr><td>AlarmActionTriggeredEvent</td><td>info</td><td>Alarm &#39;{alarm.name}&#39; on {entity.name} triggered an action</td></tr> <tr><td>AlarmClearedEvent</td><td>info</td><td>Manually cleared alarm &#39;{alarm.name}&#39; on {entity.name} from {from.@enum.ManagedEntity.Status}</td></tr> <tr><td>AlarmCreatedEvent</td><td>info</td><td>Created alarm &#39;{alarm.name}&#39; on {entity.name}</td></tr> <tr><td>AlarmEmailCompletedEvent</td><td>info</td><td>Alarm &#39;{alarm.name}&#39; on {entity.name} sent email to {to}</td></tr> <tr><td>AlarmEmailFailedEvent</td><td>error</td><td>Alarm &#39;{alarm.name}&#39; on {entity.name} cannot send email to {to}</td></tr> <tr><td>AlarmEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>AlarmReconfiguredEvent</td><td>info</td><td>Reconfigured alarm &#39;{alarm.name}&#39; on {entity.name}</td></tr> <tr><td>AlarmRemovedEvent</td><td>info</td><td>Removed alarm &#39;{alarm.name}&#39; on {entity.name}</td></tr> <tr><td>AlarmScriptCompleteEvent</td><td>info</td><td>Alarm &#39;{alarm.name}&#39; on {entity.name} ran script {script}</td></tr> <tr><td>AlarmScriptFailedEvent</td><td>error</td><td>Alarm &#39;{alarm.name}&#39; on {entity.name} did not complete script: {reason.msg}</td></tr> <tr><td>AlarmSnmpCompletedEvent</td><td>info</td><td>Alarm &#39;{alarm.name}&#39;: an SNMP trap for entity {entity.name} was sent</td></tr> <tr><td>AlarmSnmpFailedEvent</td><td>error</td><td>Alarm &#39;{alarm.name}&#39; on entity {entity.name} did not send SNMP trap: {reason.msg}</td></tr> <tr><td>AlarmStatusChangedEvent</td><td>info</td><td>Alarm &#39;{alarm.name}&#39; on {entity.name} changed from {from.@enum.ManagedEntity.Status} to {to.@enum.ManagedEntity.Status}</td></tr> <tr><td>AllVirtualMachinesLicensedEvent</td><td>info</td><td>All running virtual machines are licensed</td></tr> <tr><td>AlreadyAuthenticatedSessionEvent</td><td>info</td><td>User cannot logon since the user is already logged on</td></tr> <tr><td>AuthorizationEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>BadUsernameSessionEvent</td><td>error</td><td>Cannot login {userName}@{ipAddress}</td></tr> <tr><td>CanceledHostOperationEvent</td><td>info</td><td>The operation performed on host {host.name} in {datacenter.name} was canceled</td></tr> <tr><td>ChangeOwnerOfFileEvent</td><td>info</td><td>Changed ownership of file name {filename} from {oldOwner} to {newOwner} on {host.name} in {datacenter.name}.</td></tr> <tr><td>ChangeOwnerOfFileFailedEvent</td><td>error</td><td>Cannot change ownership of file name {filename} from {owner} to {attemptedOwner} on {host.name} in {datacenter.name}.</td></tr> <tr><td>ClusterComplianceCheckedEvent</td><td>info</td><td>Checked cluster for compliance</td></tr> <tr><td>ClusterCreatedEvent</td><td>info</td><td>Created cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>ClusterDestroyedEvent</td><td>info</td><td>Removed cluster {computeResource.name} in datacenter {datacenter.name}</td></tr> <tr><td>ClusterEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>ClusterOvercommittedEvent</td><td>error</td><td>Insufficient capacity in cluster {computeResource.name} to satisfy resource configuration in {datacenter.name}</td></tr> <tr><td>ClusterReconfiguredEvent</td><td>info</td><td>Reconfigured cluster {computeResource.name} in datacenter {datacenter.name}</td></tr> <tr><td>ClusterStatusChangedEvent</td><td>info</td><td>Configuration status on cluster {computeResource.name} changed from {oldStatus.@enum.ManagedEntity.Status} to {newStatus.@enum.ManagedEntity.Status} in {datacenter.name}</td></tr> <tr><td>CustomFieldDefAddedEvent</td><td>info</td><td>Created new custom field definition {name}</td></tr> <tr><td>CustomFieldDefEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>CustomFieldDefRemovedEvent</td><td>info</td><td>Removed field definition {name}</td></tr> <tr><td>CustomFieldDefRenamedEvent</td><td>info</td><td>Renamed field definition from {name} to {newName}</td></tr> <tr><td>CustomFieldEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>CustomFieldValueChangedEvent</td><td>info</td><td>Changed custom field {name} on {entity.name} in {datacenter.name} to {value}</td></tr> <tr><td>CustomizationEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>CustomizationFailed</td><td>info</td><td>Cannot complete customization of VM {vm.name}. See customization log at {logLocation} on the guest OS for details.</td></tr> <tr><td>CustomizationLinuxIdentityFailed</td><td>error</td><td>An error occurred while setting up Linux identity. See log file &#39;{logLocation}&#39; on guest OS for details.</td></tr> <tr><td>CustomizationNetworkSetupFailed</td><td>error</td><td>An error occurred while setting up network properties of the guest OS. See the log file {logLocation} in the guest OS for details.</td></tr> <tr><td>CustomizationStartedEvent</td><td>info</td><td>Started customization of VM {vm.name}. Customization log located at {logLocation} in the guest OS.</td></tr> <tr><td>CustomizationSucceeded</td><td>info</td><td>Customization of VM {vm.name} succeeded. Customization log located at {logLocation} in the guest OS.</td></tr> <tr><td>CustomizationSysprepFailed</td><td>error</td><td>The version of Sysprep {sysprepVersion} provided for customizing VM {vm.name} does not match the version of guest OS {systemVersion}. See the log file {logLocation} in the guest OS for more information.</td></tr> <tr><td>CustomizationUnknownFailure</td><td>error</td><td>An error occurred while customizing VM {vm.name}. For details reference the log file {logLocation} in the guest OS.</td></tr> <tr><td>DVPortgroupCreatedEvent</td><td>info</td><td>dvPort group {net.name} in {datacenter.name} was added to switch {dvs.name}.</td></tr> <tr><td>DVPortgroupDestroyedEvent</td><td>info</td><td>dvPort group {net.name} in {datacenter.name} was deleted.</td></tr> <tr><td>DVPortgroupEvent</td><td>info</td><td></td></tr> <tr><td>DVPortgroupReconfiguredEvent</td><td>info</td><td>dvPort group {net.name} in {datacenter.name} was reconfigured.</td></tr> <tr><td>DVPortgroupRenamedEvent</td><td>info</td><td>dvPort group {oldName} in {datacenter.name} was renamed to {newName}</td></tr> <tr><td>DasAdmissionControlDisabledEvent</td><td>info</td><td>vSphere HA admission control disabled for cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>DasAdmissionControlEnabledEvent</td><td>info</td><td>vSphere HA admission control enabled for cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>DasAgentFoundEvent</td><td>info</td><td>Re-established contact with a primary host in this vSphere HA cluster</td></tr> <tr><td>DasAgentUnavailableEvent</td><td>error</td><td>Unable to contact a primary vSphere HA agent in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>DasClusterIsolatedEvent</td><td>error</td><td>All hosts in the vSphere HA cluster {computeResource.name} in {datacenter.name} were isolated from the network. Check the network configuration for proper network redundancy in the management network.</td></tr> <tr><td>DasDisabledEvent</td><td>info</td><td>vSphere HA disabled for cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>DasEnabledEvent</td><td>info</td><td>vSphere HA enabled for cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>DasHostFailedEvent</td><td>error</td><td>A possible host failure has been detected by vSphere HA on {failedHost.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>DasHostIsolatedEvent</td><td>warning</td><td>Host {isolatedHost.name} has been isolated from cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>DatacenterCreatedEvent</td><td>info</td><td>Created datacenter {datacenter.name} in folder {parent.name}</td></tr> <tr><td>DatacenterEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>DatacenterRenamedEvent</td><td>info</td><td>Renamed datacenter from {oldName} to {newName}</td></tr> <tr><td>DatastoreCapacityIncreasedEvent</td><td>info</td><td>Datastore {datastore.name} increased in capacity from {oldCapacity} bytes to {newCapacity} bytes in {datacenter.name}</td></tr> <tr><td>DatastoreDestroyedEvent</td><td>info</td><td>Removed unconfigured datastore {datastore.name}</td></tr> <tr><td>DatastoreDiscoveredEvent</td><td>info</td><td>Discovered datastore {datastore.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>DatastoreDuplicatedEvent</td><td>error</td><td>Multiple datastores named {datastore} detected on host {host.name} in {datacenter.name}</td></tr> <tr><td>DatastoreEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>DatastoreFileCopiedEvent</td><td>info</td><td>File or directory {sourceFile} copied from {sourceDatastore.name} to {datastore.name} as {targetFile}</td></tr> <tr><td>DatastoreFileDeletedEvent</td><td>info</td><td>File or directory {targetFile} deleted from {datastore.name}</td></tr> <tr><td>DatastoreFileEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>DatastoreFileMovedEvent</td><td>info</td><td>File or directory {sourceFile} moved from {sourceDatastore.name} to {datastore.name} as {targetFile}</td></tr> <tr><td>DatastoreIORMReconfiguredEvent</td><td>info</td><td>Reconfigured Storage I/O Control on datastore {datastore.name}</td></tr> <tr><td>DatastorePrincipalConfigured</td><td>info</td><td>Configured datastore principal {datastorePrincipal} on host {host.name} in {datacenter.name}</td></tr> <tr><td>DatastoreRemovedOnHostEvent</td><td>info</td><td>Removed datastore {datastore.name} from {host.name} in {datacenter.name}</td></tr> <tr><td>DatastoreRenamedEvent</td><td>info</td><td>Renamed datastore from {oldName} to {newName} in {datacenter.name}</td></tr> <tr><td>DatastoreRenamedOnHostEvent</td><td>info</td><td>Renamed datastore from {oldName} to {newName} in {datacenter.name}</td></tr> <tr><td>DrsDisabledEvent</td><td>info</td><td>Disabled DRS on cluster {computeResource.name} in datacenter {datacenter.name}</td></tr> <tr><td>DrsEnabledEvent</td><td>info</td><td>Enabled DRS on {computeResource.name} with automation level {behavior} in {datacenter.name}</td></tr> <tr><td>DrsEnteredStandbyModeEvent</td><td>info</td><td>DRS put {host.name} into standby mode</td></tr> <tr><td>DrsEnteringStandbyModeEvent</td><td>info</td><td>DRS is putting {host.name} into standby mode</td></tr> <tr><td>DrsExitStandbyModeFailedEvent</td><td>error</td><td>DRS cannot move {host.name} out of standby mode</td></tr> <tr><td>DrsExitedStandbyModeEvent</td><td>info</td><td>DRS moved {host.name} out of standby mode</td></tr> <tr><td>DrsExitingStandbyModeEvent</td><td>info</td><td>DRS is moving {host.name} out of standby mode</td></tr> <tr><td>DrsInvocationFailedEvent</td><td>error</td><td>DRS invocation not completed</td></tr> <tr><td>DrsRecoveredFromFailureEvent</td><td>info</td><td>DRS has recovered from the failure</td></tr> <tr><td>DrsResourceConfigureFailedEvent</td><td>error</td><td>Unable to apply DRS resource settings on host {host.name} in {datacenter.name}. {reason.msg}. This can significantly reduce the effectiveness of DRS.</td></tr> <tr><td>DrsResourceConfigureSyncedEvent</td><td>info</td><td>Resource configuration specification returns to synchronization from previous failure on host &#39;{host.name}&#39; in {datacenter.name}</td></tr> <tr><td>DrsRuleComplianceEvent</td><td>info</td><td>{vm.name} on {host.name} in {datacenter.name} is now compliant with DRS VM-Host affinity rules</td></tr> <tr><td>DrsRuleViolationEvent</td><td>info</td><td>{vm.name} on {host.name} in {datacenter.name} is violating a DRS VM-Host affinity rule</td></tr> <tr><td>DrsVmMigratedEvent</td><td>info</td><td>DRS migrated {vm.name} from {sourceHost.name} to {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>DrsVmPoweredOnEvent</td><td>info</td><td>DRS powered On {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>DuplicateIpDetectedEvent</td><td>info</td><td>Virtual machine {macAddress} on host {host.name} has a duplicate IP {duplicateIP}</td></tr> <tr><td>DvpgImportEvent</td><td>info</td><td>Import operation with type {importType} was performed on {net.name}</td></tr> <tr><td>DvpgRestoreEvent</td><td>info</td><td>Restore operation was performed on {net.name}</td></tr> <tr><td>DvsCreatedEvent</td><td>info</td><td>A vSphere Distributed Switch {dvs.name} was created in {datacenter.name}.</td></tr> <tr><td>DvsDestroyedEvent</td><td>info</td><td>vSphere Distributed Switch {dvs.name} in {datacenter.name} was deleted.</td></tr> <tr><td>DvsEvent</td><td>info</td><td>vSphere Distributed Switch event</td></tr> <tr><td>DvsHealthStatusChangeEvent</td><td>info</td><td>Health check status was changed in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}</td></tr> <tr><td>DvsHostBackInSyncEvent</td><td>info</td><td>The vSphere Distributed Switch {dvs.name} configuration on the host was synchronized with that of the vCenter Server.</td></tr> <tr><td>DvsHostJoinedEvent</td><td>info</td><td>The host {hostJoined.name} joined the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsHostLeftEvent</td><td>info</td><td>The host {hostLeft.name} left the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsHostStatusUpdated</td><td>info</td><td>The host {hostMember.name} changed status on the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsHostWentOutOfSyncEvent</td><td>warning</td><td>The vSphere Distributed Switch {dvs.name} configuration on the host differed from that of the vCenter Server.</td></tr> <tr><td>DvsImportEvent</td><td>info</td><td>Import operation with type {importType} was performed on {dvs.name}</td></tr> <tr><td>DvsMergedEvent</td><td>info</td><td>vSphere Distributed Switch {srcDvs.name} was merged into {dstDvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsPortBlockedEvent</td><td>info</td><td>The dvPort {portKey} was blocked in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsPortConnectedEvent</td><td>info</td><td>The dvPort {portKey} was connected in the vSphere Distributed Switch {dvs.name} in {datacenter.name}</td></tr> <tr><td>DvsPortCreatedEvent</td><td>info</td><td>New ports were created in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsPortDeletedEvent</td><td>info</td><td>Deleted ports in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsPortDisconnectedEvent</td><td>info</td><td>The dvPort {portKey} was disconnected in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsPortEnteredPassthruEvent</td><td>info</td><td>The dvPort {portKey} was in passthrough mode in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsPortExitedPassthruEvent</td><td>info</td><td>The dvPort {portKey} was not in passthrough mode in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsPortJoinPortgroupEvent</td><td>info</td><td>The dvPort {portKey} was moved into the dvPort group {portgroupName} in {datacenter.name}.</td></tr> <tr><td>DvsPortLeavePortgroupEvent</td><td>info</td><td>The dvPort {portKey} was moved out of the dvPort group {portgroupName} in {datacenter.name}.</td></tr> <tr><td>DvsPortLinkDownEvent</td><td>info</td><td>The dvPort {portKey} link was down in the vSphere Distributed Switch {dvs.name} in {datacenter.name}</td></tr> <tr><td>DvsPortLinkUpEvent</td><td>info</td><td>The dvPort {portKey} link was up in the vSphere Distributed Switch {dvs.name} in {datacenter.name}</td></tr> <tr><td>DvsPortReconfiguredEvent</td><td>info</td><td>Reconfigured ports in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsPortRuntimeChangeEvent</td><td>info</td><td>The dvPort {portKey} runtime information changed in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsPortUnblockedEvent</td><td>info</td><td>The dvPort {portKey} was unblocked in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsPortVendorSpecificStateChangeEvent</td><td>info</td><td>The dvPort {portKey} vendor specific state changed in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.</td></tr> <tr><td>DvsReconfiguredEvent</td><td>info</td><td>The vSphere Distributed Switch {dvs.name} in {datacenter.name} was reconfigured.</td></tr> <tr><td>DvsRenamedEvent</td><td>info</td><td>The vSphere Distributed Switch {oldName} in {datacenter.name} was renamed to {newName}.</td></tr> <tr><td>DvsRestoreEvent</td><td>info</td><td>Restore operation was performed on {dvs.name}</td></tr> <tr><td>DvsUpgradeAvailableEvent</td><td>info</td><td> An upgrade for the vSphere Distributed Switch {dvs.name} in datacenter {datacenter.name} is available.</td></tr> <tr><td>DvsUpgradeInProgressEvent</td><td>info</td><td>An upgrade for the vSphere Distributed Switch {dvs.name} in datacenter {datacenter.name} is in progress.</td></tr> <tr><td>DvsUpgradeRejectedEvent</td><td>info</td><td>Cannot complete an upgrade for the vSphere Distributed Switch {dvs.name} in datacenter {datacenter.name}</td></tr> <tr><td>DvsUpgradedEvent</td><td>info</td><td>vSphere Distributed Switch {dvs.name} in datacenter {datacenter.name} was upgraded.</td></tr> <tr><td>EnteredMaintenanceModeEvent</td><td>info</td><td>Host {host.name} in {datacenter.name} has entered maintenance mode</td></tr> <tr><td>EnteredStandbyModeEvent</td><td>info</td><td>The host {host.name} is in standby mode</td></tr> <tr><td>EnteringMaintenanceModeEvent</td><td>info</td><td>Host {host.name} in {datacenter.name} has started to enter maintenance mode</td></tr> <tr><td>EnteringStandbyModeEvent</td><td>info</td><td>The host {host.name} is entering standby mode</td></tr> <tr><td>ErrorUpgradeEvent</td><td>error</td><td>{message}</td></tr> <tr><td>Event</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>ExitMaintenanceModeEvent</td><td>info</td><td>Host {host.name} in {datacenter.name} has exited maintenance mode</td></tr> <tr><td>ExitStandbyModeFailedEvent</td><td>error</td><td>The host {host.name} could not exit standby mode</td></tr> <tr><td>ExitedStandbyModeEvent</td><td>info</td><td>The host {host.name} is no longer in standby mode</td></tr> <tr><td>ExitingStandbyModeEvent</td><td>info</td><td>The host {host.name} is exiting standby mode</td></tr> <tr><td>FailoverLevelRestored</td><td>info</td><td>Sufficient resources are available to satisfy vSphere HA failover level in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>GeneralEvent</td><td>info</td><td>General event: {message}</td></tr> <tr><td>GeneralHostErrorEvent</td><td>error</td><td>Error detected on {host.name} in {datacenter.name}: {message}</td></tr> <tr><td>GeneralHostInfoEvent</td><td>info</td><td>Issue detected on {host.name} in {datacenter.name}: {message}</td></tr> <tr><td>GeneralHostWarningEvent</td><td>warning</td><td>Issue detected on {host.name} in {datacenter.name}: {message}</td></tr> <tr><td>GeneralUserEvent</td><td></td><td>User logged event: {message}</td></tr> <tr><td>GeneralVmErrorEvent</td><td>error</td><td>Error detected for {vm.name} on {host.name} in {datacenter.name}: {message}</td></tr> <tr><td>GeneralVmInfoEvent</td><td>info</td><td>Issue detected for {vm.name} on {host.name} in {datacenter.name}: {message}</td></tr> <tr><td>GeneralVmWarningEvent</td><td>warning</td><td>Issue detected for {vm.name} on {host.name} in {datacenter.name}: {message}</td></tr> <tr><td>GhostDvsProxySwitchDetectedEvent</td><td>info</td><td>The vSphere Distributed Switch corresponding to the proxy switches {switchUuid} on the host {host.name} does not exist in vCenter Server or does not contain this host.</td></tr> <tr><td>GhostDvsProxySwitchRemovedEvent</td><td>info</td><td>A ghost proxy switch {switchUuid} on the host {host.name} was resolved.</td></tr> <tr><td>GlobalMessageChangedEvent</td><td>info</td><td>The message changed: {message}</td></tr> <tr><td>HealthStatusChangedEvent</td><td>info</td><td>{componentName} status changed from {oldStatus} to {newStatus}</td></tr> <tr><td>HostAddFailedEvent</td><td>error</td><td>Cannot add host {hostname} to datacenter {datacenter.name}</td></tr> <tr><td>HostAddedEvent</td><td>info</td><td>Added host {host.name} to datacenter {datacenter.name}</td></tr> <tr><td>HostAdminDisableEvent</td><td>warning</td><td>Administrator access to the host {host.name} is disabled</td></tr> <tr><td>HostAdminEnableEvent</td><td>warning</td><td>Administrator access to the host {host.name} has been restored</td></tr> <tr><td>HostCnxFailedAccountFailedEvent</td><td>error</td><td>Cannot connect {host.name} in {datacenter.name}: cannot configure management account</td></tr> <tr><td>HostCnxFailedAlreadyManagedEvent</td><td>error</td><td>Cannot connect {host.name} in {datacenter.name}: already managed by {serverName}</td></tr> <tr><td>HostCnxFailedBadCcagentEvent</td><td>error</td><td>Cannot connect host {host.name} in {datacenter.name} : server agent is not responding</td></tr> <tr><td>HostCnxFailedBadUsernameEvent</td><td>error</td><td>Cannot connect {host.name} in {datacenter.name}: incorrect user name or password</td></tr> <tr><td>HostCnxFailedBadVersionEvent</td><td>error</td><td>Cannot connect {host.name} in {datacenter.name}: incompatible version</td></tr> <tr><td>HostCnxFailedCcagentUpgradeEvent</td><td>error</td><td>Cannot connect host {host.name} in {datacenter.name}. Did not install or upgrade vCenter agent service.</td></tr> <tr><td>HostCnxFailedEvent</td><td>error</td><td>Cannot connect {host.name} in {datacenter.name}: error connecting to host</td></tr> <tr><td>HostCnxFailedNetworkErrorEvent</td><td>error</td><td>Cannot connect {host.name} in {datacenter.name}: network error</td></tr> <tr><td>HostCnxFailedNoAccessEvent</td><td>error</td><td>Cannot connect host {host.name} in {datacenter.name}: account has insufficient privileges</td></tr> <tr><td>HostCnxFailedNoConnectionEvent</td><td>error</td><td>Cannot connect host {host.name} in {datacenter.name}</td></tr> <tr><td>HostCnxFailedNoLicenseEvent</td><td>error</td><td>Cannot connect {host.name} in {datacenter.name}: not enough CPU licenses</td></tr> <tr><td>HostCnxFailedNotFoundEvent</td><td>error</td><td>Cannot connect {host.name} in {datacenter.name}: incorrect host name</td></tr> <tr><td>HostCnxFailedTimeoutEvent</td><td>error</td><td>Cannot connect {host.name} in {datacenter.name}: time-out waiting for host response</td></tr> <tr><td>HostComplianceCheckedEvent</td><td>info</td><td>Host {host.name} checked for compliance.</td></tr> <tr><td>HostCompliantEvent</td><td>info</td><td>Host {host.name} is in compliance with the attached profile</td></tr> <tr><td>HostConfigAppliedEvent</td><td>info</td><td>Host configuration changes applied.</td></tr> <tr><td>HostConnectedEvent</td><td>info</td><td>Connected to {host.name} in {datacenter.name}</td></tr> <tr><td>HostConnectionLostEvent</td><td>error</td><td>Host {host.name} in {datacenter.name} is not responding</td></tr> <tr><td>HostDVPortEvent</td><td>info</td><td>dvPort connected to host {host.name} in {datacenter.name} changed status</td></tr> <tr><td>HostDasDisabledEvent</td><td>info</td><td>vSphere HA agent on {host.name} in cluster {computeResource.name} in {datacenter.name} is disabled</td></tr> <tr><td>HostDasDisablingEvent</td><td>info</td><td>vSphere HA is being disabled on {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}</td></tr> <tr><td>HostDasEnabledEvent</td><td>info</td><td>vSphere HA agent on {host.name} in cluster {computeResource.name} in {datacenter.name} is enabled</td></tr> <tr><td>HostDasEnablingEvent</td><td>warning</td><td>Enabling vSphere HA agent on {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>HostDasErrorEvent</td><td>error</td><td>vSphere HA agent on {host.name} in cluster {computeResource.name} in {datacenter.name} has an error {message}: {reason.@enum.HostDasErrorEvent.HostDasErrorReason}</td></tr> <tr><td>HostDasEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>HostDasOkEvent</td><td>info</td><td>vSphere HA agent on host {host.name} in cluster {computeResource.name} in {datacenter.name} is configured correctly</td></tr> <tr><td>HostDisconnectedEvent</td><td>info</td><td>Disconnected from {host.name} in {datacenter.name}. Reason: {reason.@enum.HostDisconnectedEvent.ReasonCode}</td></tr> <tr><td>HostEnableAdminFailedEvent</td><td>error</td><td>Cannot restore some administrator permissions to the host {host.name}</td></tr> <tr><td>HostEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>HostExtraNetworksEvent</td><td>error</td><td>Host {host.name} has the following extra networks not used by other hosts for vSphere HA communication:{ips}. Consider using vSphere HA advanced option das.allowNetwork to control network usage</td></tr> <tr><td>HostGetShortNameFailedEvent</td><td>error</td><td>Cannot complete command &#39;hostname -s&#39; on host {host.name} or returned incorrect name format</td></tr> <tr><td>HostInAuditModeEvent</td><td>info</td><td>Host {host.name} is running in audit mode. The host&#39;s configuration will not be persistent across reboots.</td></tr> <tr><td>HostInventoryFullEvent</td><td>error</td><td>Maximum ({capacity}) number of hosts allowed for this edition of vCenter Server has been reached</td></tr> <tr><td>HostInventoryUnreadableEvent</td><td>info</td><td>The virtual machine inventory file on host {host.name} is damaged or unreadable.</td></tr> <tr><td>HostIpChangedEvent</td><td>info</td><td>IP address of the host {host.name} changed from {oldIP} to {newIP}</td></tr> <tr><td>HostIpInconsistentEvent</td><td>error</td><td>Configuration of host IP address is inconsistent on host {host.name}: address resolved to {ipAddress} and {ipAddress2}</td></tr> <tr><td>HostIpToShortNameFailedEvent</td><td>error</td><td>Cannot resolve IP address to short name on host {host.name}</td></tr> <tr><td>HostIsolationIpPingFailedEvent</td><td>error</td><td>vSphere HA agent on host {host.name} in cluster {computeResource.name} in {datacenter.name} could not reach isolation address: {isolationIp}</td></tr> <tr><td>HostLicenseExpiredEvent</td><td>error</td><td>A host license for {host.name} has expired</td></tr> <tr><td>HostLocalPortCreatedEvent</td><td>info</td><td>A host local port {hostLocalPort.portKey} is created on vSphere Distributed Switch {hostLocalPort.switchUuid} to recover from management network connectivity loss on virtual NIC device {hostLocalPort.vnic} on the host {host.name}.</td></tr> <tr><td>HostMissingNetworksEvent</td><td>error</td><td>Host {host.name} does not have the following networks used by other hosts for vSphere HA communication:{ips}. Consider using vSphere HA advanced option das.allowNetwork to control network usage</td></tr> <tr><td>HostMonitoringStateChangedEvent</td><td>info</td><td>vSphere HA host monitoring state in {computeResource.name} in {datacenter.name} changed to {state.@enum.DasConfigInfo.ServiceState}</td></tr> <tr><td>HostNoAvailableNetworksEvent</td><td>error</td><td>Host {host.name} in cluster {computeResource.name} in {datacenter.name} rently has no available networks for vSphere HA Communication. The following networks are currently used by HA: {ips}</td></tr> <tr><td>HostNoHAEnabledPortGroupsEvent</td><td>error</td><td>Host {host.name} in cluster {computeResource.name} in {datacenter.name} has no port groups enabled for vSphere HA communication.</td></tr> <tr><td>HostNoRedundantManagementNetworkEvent</td><td>warning</td><td>Host {host.name} in cluster {computeResource.name} in {datacenter.name} currently has no management network redundancy</td></tr> <tr><td>HostNonCompliantEvent</td><td>error</td><td>Host {host.name} is not in compliance with the attached profile</td></tr> <tr><td>HostNotInClusterEvent</td><td>error</td><td>Host {host.name} is not a cluster member in {datacenter.name}</td></tr> <tr><td>HostOvercommittedEvent</td><td>error</td><td>Insufficient capacity in host {computeResource.name} to satisfy resource configuration in {datacenter.name}</td></tr> <tr><td>HostPrimaryAgentNotShortNameEvent</td><td>error</td><td>Primary agent {primaryAgent} was not specified as a short name to host {host.name}</td></tr> <tr><td>HostProfileAppliedEvent</td><td>info</td><td>Profile is applied on the host {host.name}</td></tr> <tr><td>HostReconnectionFailedEvent</td><td>error</td><td>Cannot reconnect to {host.name} in {datacenter.name}</td></tr> <tr><td>HostRemovedEvent</td><td>info</td><td>Removed host {host.name} in {datacenter.name}</td></tr> <tr><td>HostShortNameInconsistentEvent</td><td>error</td><td>Host names {shortName} and {shortName2} both resolved to the same IP address. Check the host&#39;s network configuration and DNS entries</td></tr> <tr><td>HostShortNameToIpFailedEvent</td><td>error</td><td>Cannot resolve short name {shortName} to IP address on host {host.name}</td></tr> <tr><td>HostShutdownEvent</td><td>info</td><td>Shut down of {host.name} in {datacenter.name}: {reason}</td></tr> <tr><td>HostStatusChangedEvent</td><td>info</td><td>Configuration status on host {computeResource.name} changed from {oldStatus.@enum.ManagedEntity.Status} to {newStatus.@enum.ManagedEntity.Status} in {datacenter.name}</td></tr> <tr><td>HostSyncFailedEvent</td><td>error</td><td>Cannot synchronize host {host.name}. {reason.msg}</td></tr> <tr><td>HostUpgradeFailedEvent</td><td>error</td><td>Cannot install or upgrade vCenter agent service on {host.name} in {datacenter.name}</td></tr> <tr><td>HostUserWorldSwapNotEnabledEvent</td><td>warning</td><td>The userworld swap is not enabled on the host {host.name}</td></tr> <tr><td>HostVnicConnectedToCustomizedDVPortEvent</td><td>info</td><td>Host {host.name} vNIC {vnic.vnic} was reconfigured to use dvPort {vnic.port.portKey} with port level configuration, which might be different from the dvPort group.</td></tr> <tr><td>HostWwnChangedEvent</td><td>warning</td><td>WWNs are changed for {host.name}</td></tr> <tr><td>HostWwnConflictEvent</td><td>error</td><td>The WWN ({wwn}) of {host.name} conflicts with the currently registered WWN</td></tr> <tr><td>IncorrectHostInformationEvent</td><td>error</td><td>Host {host.name} did not provide the information needed to acquire the correct set of licenses</td></tr> <tr><td>InfoUpgradeEvent</td><td>info</td><td>{message}</td></tr> <tr><td>InsufficientFailoverResourcesEvent</td><td>error</td><td>Insufficient resources to satisfy vSphere HA failover level on cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>InvalidEditionEvent</td><td>error</td><td>The license edition &#39;{feature}&#39; is invalid</td></tr> <tr><td>vim.event.LicenseDowngradedEvent</td><td>warning</td><td>vim.event.LicenseDowngradedEvent|License downgrade: {licenseKey} removes the following features: {lostFeatures}</td></tr> <tr><td>LicenseEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>LicenseExpiredEvent</td><td>error</td><td>License {feature.featureName} has expired</td></tr> <tr><td>LicenseNonComplianceEvent</td><td>error</td><td>License inventory is not compliant. Licenses are overused</td></tr> <tr><td>LicenseRestrictedEvent</td><td>error</td><td>Unable to acquire licenses due to a restriction in the option file on the license server.</td></tr> <tr><td>LicenseServerAvailableEvent</td><td>info</td><td>License server {licenseServer} is available</td></tr> <tr><td>LicenseServerUnavailableEvent</td><td>error</td><td>License server {licenseServer} is unavailable</td></tr> <tr><td>LocalDatastoreCreatedEvent</td><td>info</td><td>Created local datastore {datastore.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>LocalTSMEnabledEvent</td><td>info</td><td>ESXi Shell for the host {host.name} has been enabled</td></tr> <tr><td>LockerMisconfiguredEvent</td><td>warning</td><td>Datastore {datastore} which is configured to back the locker does not exist</td></tr> <tr><td>LockerReconfiguredEvent</td><td>info</td><td>Locker was reconfigured from {oldDatastore} to {newDatastore} datastore</td></tr> <tr><td>MigrationErrorEvent</td><td>error</td><td>Unable to migrate {vm.name} from {host.name} in {datacenter.name}: {fault.msg}</td></tr> <tr><td>MigrationEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>MigrationHostErrorEvent</td><td>error</td><td>Unable to migrate {vm.name} from {host.name} to {dstHost.name} in {datacenter.name}: {fault.msg}</td></tr> <tr><td>MigrationHostWarningEvent</td><td>warning</td><td>Migration of {vm.name} from {host.name} to {dstHost.name} in {datacenter.name}: {fault.msg}</td></tr> <tr><td>MigrationResourceErrorEvent</td><td>error</td><td>Cannot migrate {vm.name} from {host.name} to {dstHost.name} and resource pool {dstPool.name} in {datacenter.name}: {fault.msg}</td></tr> <tr><td>MigrationResourceWarningEvent</td><td>warning</td><td>Migration of {vm.name} from {host.name} to {dstHost.name} and resource pool {dstPool.name} in {datacenter.name}: {fault.msg}</td></tr> <tr><td>MigrationWarningEvent</td><td>warning</td><td>Migration of {vm.name} from {host.name} in {datacenter.name}: {fault.msg}</td></tr> <tr><td>MtuMatchEvent</td><td>info</td><td>The MTU configured in the vSphere Distributed Switch matches the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}</td></tr> <tr><td>MtuMismatchEvent</td><td>error</td><td>The MTU configured in the vSphere Distributed Switch does not match the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}</td></tr> <tr><td>NASDatastoreCreatedEvent</td><td>info</td><td>Created NAS datastore {datastore.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>NetworkRollbackEvent</td><td>error</td><td>Network configuration on the host {host.name} is rolled back as it disconnects the host from vCenter server.</td></tr> <tr><td>NoAccessUserEvent</td><td>error</td><td>Cannot login user {userName}@{ipAddress}: no permission</td></tr> <tr><td>NoDatastoresConfiguredEvent</td><td>info</td><td>No datastores have been configured on the host {host.name}</td></tr> <tr><td>NoLicenseEvent</td><td>error</td><td>A required license {feature.featureName} is not reserved</td></tr> <tr><td>NoMaintenanceModeDrsRecommendationForVM</td><td>info</td><td>Unable to automatically migrate {vm.name} from {host.name}</td></tr> <tr><td>NonVIWorkloadDetectedOnDatastoreEvent</td><td>info</td><td>An unmanaged I/O workload is detected on a SIOC-enabled datastore: {datastore.name}.</td></tr> <tr><td>NotEnoughResourcesToStartVmEvent</td><td>warning</td><td>Not enough resources to failover {vm.name} in {computeResource.name} in {datacenter.name}. vSphere HA will retry when resources become available.</td></tr> <tr><td>OutOfSyncDvsHost</td><td>warning</td><td>The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server.</td></tr> <tr><td>PermissionAddedEvent</td><td>info</td><td>Permission created for {principal} on {entity.name}, role is {role.name}, propagation is {propagate.@enum.auth.Permission.propagate}</td></tr> <tr><td>PermissionEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>PermissionRemovedEvent</td><td>info</td><td>Permission rule removed for {principal} on {entity.name}</td></tr> <tr><td>PermissionUpdatedEvent</td><td>info</td><td>Permission changed for {principal} on {entity.name}, role is {role.name}, propagation is {propagate.@enum.auth.Permission.propagate}</td></tr> <tr><td>ProfileAssociatedEvent</td><td>info</td><td>Profile {profile.name} attached.</td></tr> <tr><td>ProfileChangedEvent</td><td>info</td><td>Profile {profile.name} was changed.</td></tr> <tr><td>ProfileCreatedEvent</td><td>info</td><td>Profile is created.</td></tr> <tr><td>ProfileDissociatedEvent</td><td>info</td><td>Profile {profile.name} detached.</td></tr> <tr><td>ProfileEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>ProfileReferenceHostChangedEvent</td><td>info</td><td>Profile {profile.name} reference host changed.</td></tr> <tr><td>ProfileRemovedEvent</td><td>info</td><td>Profile was removed.</td></tr> <tr><td>RecoveryEvent</td><td>info</td><td>The host {hostName} network connectivity was recovered on the management virtual NIC {vnic} by connecting to a new port {portKey} on the vSphere Distributed Switch {dvsUuid}.</td></tr> <tr><td>RemoteTSMEnabledEvent</td><td>info</td><td>SSH for the host {host.name} has been enabled</td></tr> <tr><td>ResourcePoolCreatedEvent</td><td>info</td><td>Created resource pool {resourcePool.name} in compute-resource {computeResource.name} in {datacenter.name}</td></tr> <tr><td>ResourcePoolDestroyedEvent</td><td>info</td><td>Removed resource pool {resourcePool.name} on {computeResource.name} in {datacenter.name}</td></tr> <tr><td>ResourcePoolEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>ResourcePoolMovedEvent</td><td>info</td><td>Moved resource pool {resourcePool.name} from {oldParent.name} to {newParent.name} on {computeResource.name} in {datacenter.name}</td></tr> <tr><td>ResourcePoolReconfiguredEvent</td><td>info</td><td>Updated configuration for {resourcePool.name} in compute-resource {computeResource.name} in {datacenter.name}</td></tr> <tr><td>ResourceViolatedEvent</td><td>error</td><td>Resource usage exceeds configuration for resource pool {resourcePool.name} in compute-resource {computeResource.name} in {datacenter.name}</td></tr> <tr><td>RoleAddedEvent</td><td>info</td><td>New role {role.name} created</td></tr> <tr><td>RoleEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>RoleRemovedEvent</td><td>info</td><td>Role {role.name} removed</td></tr> <tr><td>RoleUpdatedEvent</td><td>info</td><td>Modifed role {role.name}</td></tr> <tr><td>RollbackEvent</td><td>info</td><td>The Network API {methodName} on this entity caused the host {hostName} to be diconnected from the vCenter Server. The configuration change was rolled back on the host.</td></tr> <tr><td>ScheduledTaskCompletedEvent</td><td>info</td><td>Task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name} completed successfully</td></tr> <tr><td>ScheduledTaskCreatedEvent</td><td>info</td><td>Created task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name}</td></tr> <tr><td>ScheduledTaskEmailCompletedEvent</td><td>info</td><td>Task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name} sent email to {to}</td></tr> <tr><td>ScheduledTaskEmailFailedEvent</td><td>error</td><td>Task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name} cannot send email to {to}: {reason.msg}</td></tr> <tr><td>ScheduledTaskEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>ScheduledTaskFailedEvent</td><td>error</td><td>Task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name} cannot be completed: {reason.msg}</td></tr> <tr><td>ScheduledTaskReconfiguredEvent</td><td>info</td><td>Reconfigured task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name}</td></tr> <tr><td>ScheduledTaskRemovedEvent</td><td>info</td><td>Removed task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name}</td></tr> <tr><td>ScheduledTaskStartedEvent</td><td>info</td><td>Running task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name}</td></tr> <tr><td>ServerLicenseExpiredEvent</td><td>error</td><td>A vCenter Server license has expired</td></tr> <tr><td>ServerStartedSessionEvent</td><td>info</td><td>vCenter started</td></tr> <tr><td>SessionEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>SessionTerminatedEvent</td><td>info</td><td>A session for user &#39;{terminatedUsername}&#39; has stopped</td></tr> <tr><td>TaskEvent</td><td>info</td><td>Task: {info.descriptionId}</td></tr> <tr><td>TaskTimeoutEvent</td><td>info</td><td>Task: {info.descriptionId} time-out</td></tr> <tr><td>TeamingMatchEvent</td><td>info</td><td>Teaming configuration in the vSphere Distributed Switch {dvs.name} on host {host.name} matches the physical switch configuration in {datacenter.name}. Detail: {healthResult.summary.@enum.dvs.VmwareDistributedVirtualSwitch.TeamingMatchStatus}</td></tr> <tr><td>TeamingMisMatchEvent</td><td>error</td><td>Teaming configuration in the vSphere Distributed Switch {dvs.name} on host {host.name} does not match the physical switch configuration in {datacenter.name}. Detail: {healthResult.summary.@enum.dvs.VmwareDistributedVirtualSwitch.TeamingMatchStatus}</td></tr> <tr><td>TemplateBeingUpgradedEvent</td><td>info</td><td>Upgrading template {legacyTemplate}</td></tr> <tr><td>TemplateUpgradeEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>TemplateUpgradeFailedEvent</td><td>info</td><td>Cannot upgrade template {legacyTemplate} due to: {reason.msg}</td></tr> <tr><td>TemplateUpgradedEvent</td><td>info</td><td>Template {legacyTemplate} upgrade completed</td></tr> <tr><td>TimedOutHostOperationEvent</td><td>warning</td><td>The operation performed on {host.name} in {datacenter.name} timed out</td></tr> <tr><td>UnlicensedVirtualMachinesEvent</td><td>info</td><td>There are {unlicensed} unlicensed virtual machines on host {host} - there are only {available} licenses available</td></tr> <tr><td>UnlicensedVirtualMachinesFoundEvent</td><td>info</td><td>{unlicensed} unlicensed virtual machines found on host {host}</td></tr> <tr><td>UpdatedAgentBeingRestartedEvent</td><td>info</td><td>The agent on host {host.name} is updated and will soon restart</td></tr> <tr><td>UpgradeEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>UplinkPortMtuNotSupportEvent</td><td>error</td><td>Not all VLAN MTU settings on the external physical switch allow the vSphere Distributed Switch maximum MTU size packets to pass on the uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}.</td></tr> <tr><td>UplinkPortMtuSupportEvent</td><td>info</td><td>All VLAN MTU settings on the external physical switch allow the vSphere Distributed Switch maximum MTU size packets to pass on the uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}.</td></tr> <tr><td>UplinkPortVlanTrunkedEvent</td><td>info</td><td>The configured VLAN in the vSphere Distributed Switch was trunked by the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}.</td></tr> <tr><td>UplinkPortVlanUntrunkedEvent</td><td>error</td><td>Not all the configured VLANs in the vSphere Distributed Switch were trunked by the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}.</td></tr> <tr><td>UserAssignedToGroup</td><td>info</td><td>User {userLogin} was added to group {group}</td></tr> <tr><td>UserLoginSessionEvent</td><td>info</td><td>User {userName}@{ipAddress} logged in as {userAgent}</td></tr> <tr><td>UserLogoutSessionEvent</td><td>info</td><td>User {userName}@{ipAddress} logged out (login time: {loginTime}, number of API invocations: {callCount}, user agent: {userAgent})</td></tr> <tr><td>UserPasswordChanged</td><td>info</td><td>Password was changed for account {userLogin} on host {host.name}</td></tr> <tr><td>UserUnassignedFromGroup</td><td>info</td><td>User {userLogin} removed from group {group}</td></tr> <tr><td>UserUpgradeEvent</td><td></td><td>{message}</td></tr> <tr><td>VMFSDatastoreCreatedEvent</td><td>info</td><td>Created VMFS datastore {datastore.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VMFSDatastoreExpandedEvent</td><td>info</td><td>Expanded VMFS datastore {datastore.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VMFSDatastoreExtendedEvent</td><td>info</td><td>Extended VMFS datastore {datastore.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VMotionLicenseExpiredEvent</td><td>error</td><td>A vMotion license for {host.name} has expired</td></tr> <tr><td>VcAgentUninstallFailedEvent</td><td>error</td><td>Cannot uninstall vCenter agent from {host.name} in {datacenter.name}. {reason.@enum.fault.AgentInstallFailed.Reason}</td></tr> <tr><td>VcAgentUninstalledEvent</td><td>info</td><td>vCenter agent has been uninstalled from {host.name} in {datacenter.name}</td></tr> <tr><td>VcAgentUpgradeFailedEvent</td><td>error</td><td>Cannot upgrade vCenter agent on {host.name} in {datacenter.name}. {reason.@enum.fault.AgentInstallFailed.Reason}</td></tr> <tr><td>VcAgentUpgradedEvent</td><td>info</td><td>vCenter agent has been upgraded on {host.name} in {datacenter.name}</td></tr> <tr><td>VimAccountPasswordChangedEvent</td><td>info</td><td>VIM account password was changed on host {host.name}</td></tr> <tr><td>VmAcquiredMksTicketEvent</td><td>info</td><td>Remote console to {vm.name} on {host.name} in {datacenter.name} has been opened</td></tr> <tr><td>VmAcquiredTicketEvent</td><td>info</td><td>A ticket for {vm.name} of type {ticketType} on {host.name} in {datacenter.name} has been acquired</td></tr> <tr><td>VmAutoRenameEvent</td><td>info</td><td>Invalid name for {vm.name} on {host.name} in {datacenter.name}. Renamed from {oldName} to {newName}</td></tr> <tr><td>VmBeingClonedEvent</td><td>info</td><td>Cloning {vm.name} on host {host.name} in {datacenter.name} to {destName} on host {destHost.name}</td></tr> <tr><td>VmBeingClonedNoFolderEvent</td><td>info</td><td>Cloning {vm.name} on host {host.name} in {datacenter.name} to {destName} on host {destHost.name} to a vApp</td></tr> <tr><td>VmBeingCreatedEvent</td><td>info</td><td>Creating {vm.name} on host {host.name} in {datacenter.name}</td></tr> <tr><td>VmBeingDeployedEvent</td><td>info</td><td>Deploying {vm.name} on host {host.name} in {datacenter.name} from template {srcTemplate.name}</td></tr> <tr><td>VmBeingHotMigratedEvent</td><td>info</td><td>Migrating {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} in {datacenter.name}</td></tr> <tr><td>VmBeingMigratedEvent</td><td>info</td><td>Relocating {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} in {datacenter.name}</td></tr> <tr><td>VmBeingRelocatedEvent</td><td>info</td><td>Relocating {vm.name} in {datacenter.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name}</td></tr> <tr><td>VmCloneEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>VmCloneFailedEvent</td><td>error</td><td>Cannot clone {vm.name}: {reason.msg}</td></tr> <tr><td>VmClonedEvent</td><td>info</td><td>Clone of {sourceVm.name} completed</td></tr> <tr><td>VmConfigMissingEvent</td><td>info</td><td>Configuration file for {vm.name} on {host.name} in {datacenter.name} cannot be found</td></tr> <tr><td>VmConnectedEvent</td><td>info</td><td>Virtual machine {vm.name} is connected</td></tr> <tr><td>VmCreatedEvent</td><td>info</td><td>Created virtual machine {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VmDVPortEvent</td><td>info</td><td>dvPort connected to VM {vm.name} on {host.name} in {datacenter.name} changed status</td></tr> <tr><td>VmDasBeingResetEvent</td><td>info</td><td>{vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name} reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}</td></tr> <tr><td>VmDasBeingResetWithScreenshotEvent</td><td>info</td><td>{vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name} reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}. A screenshot is saved at {screenshotFilePath}.</td></tr> <tr><td>VmDasResetFailedEvent</td><td>warning</td><td>vSphere HA cannot reset {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>VmDasUpdateErrorEvent</td><td>error</td><td>Unable to update vSphere HA agents given the state of {vm.name}</td></tr> <tr><td>VmDasUpdateOkEvent</td><td>info</td><td>vSphere HA agents have been updated with the current state of the virtual machine</td></tr> <tr><td>VmDateRolledBackEvent</td><td>error</td><td>Disconnecting all hosts as the date of virtual machine {vm.name} has been rolled back</td></tr> <tr><td>VmDeployFailedEvent</td><td>error</td><td>Cannot deploy template: {reason.msg}</td></tr> <tr><td>VmDeployedEvent</td><td>info</td><td>Template {srcTemplate.name} deployed on host {host.name}</td></tr> <tr><td>VmDisconnectedEvent</td><td>info</td><td>{vm.name} on host {host.name} in {datacenter.name} is disconnected</td></tr> <tr><td>VmDiscoveredEvent</td><td>info</td><td>Discovered {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VmDiskFailedEvent</td><td>error</td><td>Cannot create virtual disk {disk}</td></tr> <tr><td>VmEmigratingEvent</td><td>info</td><td>Migrating {vm.name} off host {host.name} in {datacenter.name}</td></tr> <tr><td>VmEndRecordingEvent</td><td>info</td><td>End a recording session on {vm.name}</td></tr> <tr><td>VmEndReplayingEvent</td><td>info</td><td>End a replay session on {vm.name}</td></tr> <tr><td>VmEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>VmFailedMigrateEvent</td><td>error</td><td>Cannot migrate {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} in {datacenter.name}</td></tr> <tr><td>VmFailedRelayoutEvent</td><td>error</td><td>Cannot complete relayout {vm.name} on {host.name} in {datacenter.name}: {reason.msg}</td></tr> <tr><td>VmFailedRelayoutOnVmfs2DatastoreEvent</td><td>error</td><td>Cannot complete relayout for virtual machine {vm.name} which has disks on a VMFS2 volume.</td></tr> <tr><td>VmFailedStartingSecondaryEvent</td><td>error</td><td>vCenter cannot start the Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}. Reason: {reason.@enum.VmFailedStartingSecondaryEvent.FailureReason}</td></tr> <tr><td>VmFailedToPowerOffEvent</td><td>error</td><td>Cannot power off {vm.name} on {host.name} in {datacenter.name}: {reason.msg}</td></tr> <tr><td>VmFailedToPowerOnEvent</td><td>error</td><td>Cannot power on {vm.name} on {host.name} in {datacenter.name}. {reason.msg}</td></tr> <tr><td>VmFailedToRebootGuestEvent</td><td>error</td><td>Cannot reboot the guest OS for {vm.name} on {host.name} in {datacenter.name}. {reason.msg}</td></tr> <tr><td>VmFailedToResetEvent</td><td>error</td><td>Cannot suspend {vm.name} on {host.name} in {datacenter.name}: {reason.msg}</td></tr> <tr><td>VmFailedToShutdownGuestEvent</td><td>error</td><td>{vm.name} cannot shut down the guest OS on {host.name} in {datacenter.name}: {reason.msg}</td></tr> <tr><td>VmFailedToStandbyGuestEvent</td><td>error</td><td>{vm.name} cannot standby the guest OS on {host.name} in {datacenter.name}: {reason.msg}</td></tr> <tr><td>VmFailedToSuspendEvent</td><td>error</td><td>Cannot suspend {vm.name} on {host.name} in {datacenter.name}: {reason.msg}</td></tr> <tr><td>VmFailedUpdatingSecondaryConfig</td><td>error</td><td>vCenter cannot update the Fault Tolerance secondary VM configuration for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>VmFailoverFailed</td><td>warning</td><td>vSphere HA unsuccessfully failed over {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}. vSphere HA will retry if the maximum number of attempts has not been exceeded. Reason: {reason.msg}</td></tr> <tr><td>VmFaultToleranceStateChangedEvent</td><td>info</td><td>Fault Tolerance state of {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} changed from {oldState.@enum.VirtualMachine.FaultToleranceState} to {newState.@enum.VirtualMachine.FaultToleranceState}</td></tr> <tr><td>VmFaultToleranceTurnedOffEvent</td><td>info</td><td>Fault Tolerance protection has been turned off for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>VmFaultToleranceVmTerminatedEvent</td><td>info</td><td>The Fault Tolerance VM {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} has been terminated. {reason.@enum.VmFaultToleranceVmTerminatedEvent.TerminateReason}</td></tr> <tr><td>VmGuestRebootEvent</td><td>info</td><td>Guest OS reboot for {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VmGuestShutdownEvent</td><td>info</td><td>Guest OS shut down for {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VmGuestStandbyEvent</td><td>info</td><td>Guest OS standby for {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VmHealthMonitoringStateChangedEvent</td><td>info</td><td>vSphere HA VM monitoring state in {computeResource.name} in {datacenter.name} changed to {state.@enum.DasConfigInfo.VmMonitoringState}</td></tr> <tr><td>VmInstanceUuidAssignedEvent</td><td>info</td><td>Assign a new instance UUID ({instanceUuid}) to {vm.name}</td></tr> <tr><td>VmInstanceUuidChangedEvent</td><td>info</td><td>The instance UUID of {vm.name} has been changed from ({oldInstanceUuid}) to ({newInstanceUuid})</td></tr> <tr><td>VmInstanceUuidConflictEvent</td><td>error</td><td>The instance UUID ({instanceUuid}) of {vm.name} conflicts with the instance UUID assigned to {conflictedVm.name}</td></tr> <tr><td>VmMacAssignedEvent</td><td>info</td><td>New MAC address ({mac}) assigned to adapter {adapter} for {vm.name}</td></tr> <tr><td>VmMacChangedEvent</td><td>warning</td><td>Changed MAC address from {oldMac} to {newMac} for adapter {adapter} for {vm.name}</td></tr> <tr><td>VmMacConflictEvent</td><td>error</td><td>The MAC address ({mac}) of {vm.name} conflicts with MAC assigned to {conflictedVm.name}</td></tr> <tr><td>VmMaxFTRestartCountReached</td><td>warning</td><td>vSphere HA stopped trying to restart Secondary VM {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name} because the maximum VM restart count was reached</td></tr> <tr><td>VmMaxRestartCountReached</td><td>warning</td><td>vSphere HA stopped trying to restart {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name} because the maximum VM restart count was reached</td></tr> <tr><td>VmMessageErrorEvent</td><td>error</td><td>Error message on {vm.name} on {host.name} in {datacenter.name}: {message}</td></tr> <tr><td>VmMessageEvent</td><td>info</td><td>Message on {vm.name} on {host.name} in {datacenter.name}: {message}</td></tr> <tr><td>VmMessageWarningEvent</td><td>warning</td><td>Warning message on {vm.name} on {host.name} in {datacenter.name}: {message}</td></tr> <tr><td>VmMigratedEvent</td><td>info</td><td>Migration of virtual machine {vm.name} from {sourceHost.name}, {sourceDatastore.name} to {host.name}, {ds.name} completed</td></tr> <tr><td>VmNoCompatibleHostForSecondaryEvent</td><td>error</td><td>No compatible host for the Fault Tolerance secondary VM {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>VmNoNetworkAccessEvent</td><td>warning</td><td>Not all networks for {vm.name} are accessible by {destHost.name}</td></tr> <tr><td>VmOrphanedEvent</td><td>warning</td><td>{vm.name} does not exist on {host.name} in {datacenter.name}</td></tr> <tr><td>VmPowerOffOnIsolationEvent</td><td>info</td><td>vSphere HA powered off {vm.name} on the isolated host {isolatedHost.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>VmPoweredOffEvent</td><td>info</td><td>{vm.name} on {host.name} in {datacenter.name} is powered off</td></tr> <tr><td>VmPoweredOnEvent</td><td>info</td><td>{vm.name} on {host.name} in {datacenter.name} is powered on</td></tr> <tr><td>VmPoweringOnWithCustomizedDVPortEvent</td><td>info</td><td>Virtual machine {vm.name} powered On with vNICs connected to dvPorts that have a port level configuration, which might be different from the dvPort group configuration.</td></tr> <tr><td>VmPrimaryFailoverEvent</td><td>error</td><td>Fault Tolerance VM ({vm.name}) failed over to {host.name} in cluster {computeResource.name} in {datacenter.name}. {reason.@enum.VirtualMachine.NeedSecondaryReason}</td></tr> <tr><td>VmReconfiguredEvent</td><td>info</td><td>Reconfigured {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VmRegisteredEvent</td><td>info</td><td>Registered {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VmRelayoutSuccessfulEvent</td><td>info</td><td>Relayout of {vm.name} on {host.name} in {datacenter.name} completed</td></tr> <tr><td>VmRelayoutUpToDateEvent</td><td>info</td><td>{vm.name} on {host.name} in {datacenter.name} is in the correct format and relayout is not necessary</td></tr> <tr><td>VmReloadFromPathEvent</td><td>info</td><td>{vm.name} on {host.name} reloaded from new configuration {configPath}.</td></tr> <tr><td>VmReloadFromPathFailedEvent</td><td>error</td><td>{vm.name} on {host.name} could not be reloaded from {configPath}.</td></tr> <tr><td>VmRelocateFailedEvent</td><td>error</td><td>Cannot relocate virtual machine &#39;{vm.name}&#39; in {datacenter.name}</td></tr> <tr><td>VmRelocateSpecEvent</td><td>info</td><td>&lt;internal&gt;</td></tr> <tr><td>VmRelocatedEvent</td><td>info</td><td>Completed the relocation of the virtual machine</td></tr> <tr><td>VmRemoteConsoleConnectedEvent</td><td>info</td><td>Remote console connected to {vm.name} on host {host.name}</td></tr> <tr><td>VmRemoteConsoleDisconnectedEvent</td><td>info</td><td>Remote console disconnected from {vm.name} on host {host.name}</td></tr> <tr><td>VmRemovedEvent</td><td>info</td><td>Removed {vm.name} on {host.name} from {datacenter.name}</td></tr> <tr><td>VmRenamedEvent</td><td>warning</td><td>Renamed {vm.name} from {oldName} to {newName} in {datacenter.name}</td></tr> <tr><td>VmRequirementsExceedCurrentEVCModeEvent</td><td>warning</td><td>Feature requirements of {vm.name} exceed capabilities of {host.name}&#39;s current EVC mode.</td></tr> <tr><td>VmResettingEvent</td><td>info</td><td>{vm.name} on {host.name} in {datacenter.name} is reset</td></tr> <tr><td>VmResourcePoolMovedEvent</td><td>info</td><td>Moved {vm.name} from resource pool {oldParent.name} to {newParent.name} in {datacenter.name}</td></tr> <tr><td>VmResourceReallocatedEvent</td><td>info</td><td>Changed resource allocation for {vm.name}</td></tr> <tr><td>VmRestartedOnAlternateHostEvent</td><td>info</td><td>Virtual machine {vm.name} was restarted on {host.name} since {sourceHost.name} failed</td></tr> <tr><td>VmResumingEvent</td><td>info</td><td>{vm.name} on {host.name} in {datacenter.name} is resumed</td></tr> <tr><td>VmSecondaryAddedEvent</td><td>info</td><td>A Fault Tolerance secondary VM has been added for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>VmSecondaryDisabledBySystemEvent</td><td>error</td><td>vCenter disabled Fault Tolerance on VM {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} because the Secondary VM could not be powered On.</td></tr> <tr><td>VmSecondaryDisabledEvent</td><td>info</td><td>Disabled Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>VmSecondaryEnabledEvent</td><td>info</td><td>Enabled Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>VmSecondaryStartedEvent</td><td>info</td><td>Started Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>VmShutdownOnIsolationEvent</td><td>info</td><td>vSphere HA shut down {vm.name} was shut down on the isolated host {isolatedHost.name} in cluster {computeResource.name} in {datacenter.name}: {shutdownResult.@enum.VmShutdownOnIsolationEvent.Operation}</td></tr> <tr><td>VmStartRecordingEvent</td><td>info</td><td>Start a recording session on {vm.name}</td></tr> <tr><td>VmStartReplayingEvent</td><td>info</td><td>Start a replay session on {vm.name}</td></tr> <tr><td>VmStartingEvent</td><td>info</td><td>{vm.name} on host {host.name} in {datacenter.name} is starting</td></tr> <tr><td>VmStartingSecondaryEvent</td><td>info</td><td>Starting Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}</td></tr> <tr><td>VmStaticMacConflictEvent</td><td>error</td><td>The static MAC address ({mac}) of {vm.name} conflicts with MAC assigned to {conflictedVm.name}</td></tr> <tr><td>VmStoppingEvent</td><td>info</td><td>{vm.name} on {host.name} in {datacenter.name} is stopping</td></tr> <tr><td>VmSuspendedEvent</td><td>info</td><td>{vm.name} on {host.name} in {datacenter.name} is suspended</td></tr> <tr><td>VmSuspendingEvent</td><td>info</td><td>{vm.name} on {host.name} in {datacenter.name} is being suspended</td></tr> <tr><td>VmTimedoutStartingSecondaryEvent</td><td>error</td><td>Starting the Fault Tolerance secondary VM {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} timed out within {timeout} ms</td></tr> <tr><td>VmUnsupportedStartingEvent</td><td>warning</td><td>Unsupported guest OS {guestId} for {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VmUpgradeCompleteEvent</td><td>info</td><td>Virtual machine compatibility upgraded to {version.@enum.vm.hwVersion}</td></tr> <tr><td>VmUpgradeFailedEvent</td><td>error</td><td>Cannot upgrade virtual machine compatibility.</td></tr> <tr><td>VmUpgradingEvent</td><td>info</td><td>Upgrading virtual machine compatibility of {vm.name} in {datacenter.name} to {version.@enum.vm.hwVersion}</td></tr> <tr><td>VmUuidAssignedEvent</td><td>info</td><td>Assigned new BIOS UUID ({uuid}) to {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VmUuidChangedEvent</td><td>warning</td><td>Changed BIOS UUID from {oldUuid} to {newUuid} for {vm.name} on {host.name} in {datacenter.name}</td></tr> <tr><td>VmUuidConflictEvent</td><td>error</td><td>BIOS ID ({uuid}) of {vm.name} conflicts with that of {conflictedVm.name}</td></tr> <tr><td>VmWwnAssignedEvent</td><td>info</td><td>New WWNs assigned to {vm.name}</td></tr> <tr><td>VmWwnChangedEvent</td><td>warning</td><td>WWNs are changed for {vm.name}</td></tr> <tr><td>VmWwnConflictEvent</td><td>error</td><td>The WWN ({wwn}) of {vm.name} conflicts with the currently registered WWN</td></tr> <tr><td>WarningUpgradeEvent</td><td>warning</td><td>{message}</td></tr> <tr><td>IScsiBootFailureEvent</td><td>warning</td><td>Booting from iSCSI failed with an error. See the VMware Knowledge Base for information on configuring iBFT networking.</td></tr> <tr><td>vprob.net.connectivity.lost</td><td>error</td><td>vprob.net.connectivity.lost|Lost network connectivity on virtual switch {1}. Physical NIC {2} is down. Affected portgroups:{3}.</td></tr> <tr><td>vprob.net.e1000.tso6.notsupported</td><td>error</td><td>vprob.net.e1000.tso6.notsupported|Guest-initiated IPv6 TCP Segmentation Offload (TSO) packets ignored. Manually disable TSO inside the guest operating system in virtual machine {1}, or use a different virtual adapter.</td></tr> <tr><td>vprob.net.migrate.bindtovmk</td><td>warning</td><td>vprob.net.migrate.bindtovmk|The ESX advanced config option /Migrate/Vmknic is set to an invalid vmknic: {1}. /Migrate/Vmknic specifies a vmknic that vMotion binds to for improved performance. Please update the config option with a valid vmknic or, if you do not want vMotion to bind to a specific vmknic, remove the invalid vmknic and leave the option blank.</td></tr> <tr><td>vprob.net.proxyswitch.port.unavailable</td><td>warning</td><td>vprob.net.proxyswitch.port.unavailable|Virtual NIC with hardware address {1} failed to connect to distributed virtual port {2} on switch {3}. There are no more ports available on the host proxy switch.</td></tr> <tr><td>vprob.net.redundancy.degraded</td><td>warning</td><td>vprob.net.redundancy.degraded|Uplink redundancy degraded on virtual switch {1}. Physical NIC {2} is down. {3} uplinks still up. Affected portgroups:{4}.</td></tr> <tr><td>vprob.net.redundancy.lost</td><td>warning</td><td>vprob.net.redundancy.lost|Lost uplink redundancy on virtual switch {1}. Physical NIC {2} is down. Affected portgroups:{3}.</td></tr> <tr><td>vprob.scsi.device.thinprov.atquota</td><td>warning</td><td>vprob.scsi.device.thinprov.atquota|Space utilization on thin-provisioned device {1} exceeded configured threshold.</td></tr> <tr><td>vprob.storage.connectivity.lost</td><td>error</td><td>vprob.storage.connectivity.lost|Lost connectivity to storage device {1}. Path {2} is down. Affected datastores: {3}.</td></tr> <tr><td>vprob.storage.redundancy.degraded</td><td>warning</td><td>vprob.storage.redundancy.degraded|Path redundancy to storage device {1} degraded. Path {2} is down. {3} remaining active paths. Affected datastores: {4}.</td></tr> <tr><td>vprob.storage.redundancy.lost</td><td>warning</td><td>vprob.storage.redundancy.lost|Lost path redundancy to storage device {1}. Path {2} is down. Affected datastores: {3}.</td></tr> <tr><td>vprob.vmfs.error.volume.is.locked</td><td>error</td><td>vprob.vmfs.error.volume.is.locked|Volume on device {1} is locked, possibly because some remote host encountered an error during a volume operation and could not recover.</td></tr> <tr><td>vprob.vmfs.extent.offline</td><td>error</td><td>vprob.vmfs.extent.offline|An attached device {1} might be offline. The file system {2} is now in a degraded state. While the datastore is still available, parts of data that reside on the extent that went offline might be inaccessible.</td></tr> <tr><td>vprob.vmfs.extent.online</td><td>info</td><td>vprob.vmfs.extent.online|Device {1} backing file system {2} came online. This extent was previously offline. All resources on this device are now available.</td></tr> <tr><td>vprob.vmfs.heartbeat.recovered</td><td>info</td><td>vprob.vmfs.heartbeat.recovered|Successfully restored access to volume {1} ({2}) following connectivity issues.</td></tr> <tr><td>vprob.vmfs.heartbeat.timedout</td><td>info</td><td>vprob.vmfs.heartbeat.timedout|Lost access to volume {1} ({2}) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.</td></tr> <tr><td>vprob.vmfs.heartbeat.unrecoverable</td><td>error</td><td>vprob.vmfs.heartbeat.unrecoverable|Lost connectivity to volume {1} ({2}) and subsequent recovery attempts have failed.</td></tr> <tr><td>vprob.vmfs.journal.createfailed</td><td>error</td><td>vprob.vmfs.journal.createfailed|No space for journal on volume {1} ({2}). Opening volume in read-only metadata mode with limited write support.</td></tr> <tr><td>vprob.vmfs.lock.corruptondisk</td><td>error</td><td>vprob.vmfs.lock.corruptondisk|At least one corrupt on-disk lock was detected on volume {1} ({2}). Other regions of the volume may be damaged too.</td></tr> <tr><td>vprob.vmfs.nfs.server.disconnect</td><td>error</td><td>vprob.vmfs.nfs.server.disconnect|Lost connection to server {1} mount point {2} mounted as {3} ({4}).</td></tr> <tr><td>vprob.vmfs.nfs.server.restored</td><td>info</td><td>vprob.vmfs.nfs.server.restored|Restored connection to server {1} mount point {2} mounted as {3} ({4}).</td></tr> <tr><td>vprob.vmfs.resource.corruptondisk</td><td>error</td><td>vprob.vmfs.resource.corruptondisk|At least one corrupt resource metadata region was detected on volume {1} ({2}). Other regions of the volume might be damaged too.</td></tr> <tr><td>com.vmware.rbd.activateRuleSet</td><td>info</td><td>com.vmware.rbd.activateRuleSet|Activate Rule Set</td></tr> <tr><td>com.vmware.rbd.fdmPackageMissing</td><td>warning</td><td>com.vmware.rbd.fdmPackageMissing|A host in a HA cluster does not have the &#39;vmware-fdm&#39; package in its image profile</td></tr> <tr><td>com.vmware.rbd.pxeBootNoImageRule</td><td>info</td><td>com.vmware.rbd.pxeBootNoImageRule|Unable to PXE boot host since it does not match any rules</td></tr> <tr><td>com.vmware.rbd.pxeBootUnknownHost</td><td>info</td><td>com.vmware.rbd.pxeBootUnknownHost|PXE Booting unknown host</td></tr> <tr><td>com.vmware.rbd.pxeProfileAssoc</td><td>info</td><td>com.vmware.rbd.pxeProfileAssoc|Attach PXE Profile</td></tr> <tr><td>com.vmware.vcHms.datastoreInaccessibleEvent</td><td>error</td><td>com.vmware.vcHms.datastoreInaccessibleEvent|Datastore is not accessible for VR Server [data.hbrServerName](UUID: [data.hbrServerUUID])</td></tr> <tr><td>com.vmware.vcHms.handledVmDiskAddEvent</td><td>info</td><td>com.vmware.vcHms.handledVmDiskAddEvent|vSphere Replication detected and handled the addition of a disk to virtual machine [data.vm]. Disks added are [data.disks].</td></tr> <tr><td>com.vmware.vcHms.handledVmDiskRemoveEvent</td><td>info</td><td>com.vmware.vcHms.handledVmDiskRemoveEvent|vSphere Replication detected and handled the removal of a disk from virtual machine [data.vm]. Disks removed are [data.disks].</td></tr> <tr><td>com.vmware.vcHms.hbrDisconnectedEvent</td><td>info</td><td>com.vmware.vcHms.hbrDisconnectedEvent|VR Server [data.hbrServer] disconnected</td></tr> <tr><td>com.vmware.vcHms.hbrReconnectedEvent</td><td>info</td><td>com.vmware.vcHms.hbrReconnectedEvent|VR Server [data.hbrServer] reconnected</td></tr> <tr><td>com.vmware.vcHms.hostConfiguredForHbrEvent</td><td>info</td><td>com.vmware.vcHms.hostConfiguredForHbrEvent|Host is configured for vSphere Replication</td></tr> <tr><td>com.vmware.vcHms.hostUnconfiguredForHbrEvent</td><td>info</td><td>com.vmware.vcHms.hostUnconfiguredForHbrEvent|Host with managed object ID [data.hostMoId] was unconfigured for vSphere Replication</td></tr> <tr><td>com.vmware.vcHms.remoteSiteDownEvent</td><td>error</td><td>com.vmware.vcHms.remoteSiteDownEvent|Connection to the remote vSphere Replication site &#39;[data.siteName]&#39; is down</td></tr> <tr><td>com.vmware.vcHms.remoteSiteUpEvent</td><td>info</td><td>com.vmware.vcHms.remoteSiteUpEvent|Connection to the remote vSphere Replication site &#39;[data.siteName]&#39; is established</td></tr> <tr><td>com.vmware.vcHms.replicationCleanedUpEvent</td><td>info</td><td>com.vmware.vcHms.replicationCleanedUpEvent|Virtual machine [data.vm] was removed from vCenter Server and its vSphere Replication state was cleaned up</td></tr> <tr><td>com.vmware.vcHms.replicationConfiguredEvent</td><td>info</td><td>com.vmware.vcHms.replicationConfiguredEvent|Virtual machine is configured for vSphere Replication</td></tr> <tr><td>com.vmware.vcHms.replicationUnconfiguredEvent</td><td>info</td><td>com.vmware.vcHms.replicationUnconfiguredEvent|Virtual machine was unconfigured for vSphere Replication</td></tr> <tr><td>com.vmware.vcHms.rpoRestoredEvent</td><td>info</td><td>com.vmware.vcHms.rpoRestoredEvent|Virtual machine vSphere Replication RPO is no longer violated</td></tr> <tr><td>com.vmware.vcHms.rpoViolatedEvent</td><td>error</td><td>com.vmware.vcHms.rpoViolatedEvent|Virtual machine vSphere Replication RPO is violated by [data.currentRpoViolation] minute(s)</td></tr> <tr><td>com.vmware.vcHms.vmMissingReplicationConfigurationEvent</td><td>error</td><td>com.vmware.vcHms.vmMissingReplicationConfigurationEvent|Virtual machine is experiencing problems with vSphere Replication and needs to be reconfigured</td></tr> <tr><td>com.vmware.vcHms.vmReplicationConfigurationRemovedEvent</td><td>info</td><td>com.vmware.vcHms.vmReplicationConfigurationRemovedEvent|Virtual Machine cleaned up from vSphere Replication configuration</td></tr> <tr><td>com.vmware.vcIntegrity.CancelTask</td><td>info</td><td>com.vmware.vcIntegrity.CancelTask|Canceling task on [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.CheckNotification</td><td>info</td><td>com.vmware.vcIntegrity.CheckNotification|Successfully downloaded notifications. New notifications: [data.Notifications]</td></tr> <tr><td>com.vmware.vcIntegrity.CheckNotificationFailed</td><td>error</td><td>com.vmware.vcIntegrity.CheckNotificationFailed|Could not download notifications.</td></tr> <tr><td>com.vmware.vcIntegrity.CheckPXEBootHostFailure</td><td>error</td><td>com.vmware.vcIntegrity.CheckPXEBootHostFailure|Cannot determine whether host {host.name} is PXE booted. The host will be excluded for the current operation.</td></tr> <tr><td>com.vmware.vcIntegrity.CriticallyLowDiskSpace</td><td>warning</td><td>com.vmware.vcIntegrity.CriticallyLowDiskSpace|VMware vSphere Update Manager is critically low on storage space! Location: [data.Volume]. Available space: [data.FreeSpace]MB.</td></tr> <tr><td>com.vmware.vcIntegrity.DisableToolsRemediateOnReboot</td><td>info</td><td>com.vmware.vcIntegrity.DisableToolsRemediateOnReboot|Successfully disabled the option for VMware Tools upgrade on VM power cycle for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.DisableToolsRemediateOnRebootFailed</td><td>error</td><td>com.vmware.vcIntegrity.DisableToolsRemediateOnRebootFailed|Could not disable the option for VMware Tools upgrade on VM power cycle for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadAlert</td><td>info</td><td>com.vmware.vcIntegrity.DownloadAlert|VMware vSphere Update Manager download alert (critical/total): ESX [data.esxCritical]/[data.esxTotal]</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadFailedPatchBinary</td><td>error</td><td>com.vmware.vcIntegrity.DownloadFailedPatchBinary|Could not download patch packages for following patches: [data.message].</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadGuestPackage</td><td>info</td><td>com.vmware.vcIntegrity.DownloadGuestPackage|Successfully downloaded guest patch packages. New packages: [data.Updates]</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadGuestPackageFailed</td><td>error</td><td>com.vmware.vcIntegrity.DownloadGuestPackageFailed|Could not download guest patch packages.</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadGuestUnixPackage</td><td>info</td><td>com.vmware.vcIntegrity.DownloadGuestUnixPackage|Successfully downloaded guest patch packages for UNIX. New packages: [data.Updates]</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadGuestUnixPackageFailed</td><td>error</td><td>com.vmware.vcIntegrity.DownloadGuestUnixPackageFailed|Could not download guest patch packages for UNIX.</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadGuestUnixUpdate</td><td>info</td><td>com.vmware.vcIntegrity.DownloadGuestUnixUpdate|Successfully downloaded guest patch definitions for UNIX. New patches: [data.Updates]</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadGuestUnixUpdateFailed</td><td>error</td><td>com.vmware.vcIntegrity.DownloadGuestUnixUpdateFailed|Could not download guest patch definitions for UNIX.</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadGuestUpdate</td><td>info</td><td>com.vmware.vcIntegrity.DownloadGuestUpdate|Successfully downloaded guest patch definitions. New patches: [data.Updates]</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadGuestUpdateFailed</td><td>error</td><td>com.vmware.vcIntegrity.DownloadGuestUpdateFailed|Could not download guest patch definitions.</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadHostPackage</td><td>info</td><td>com.vmware.vcIntegrity.DownloadHostPackage|Successfully downloaded host patch packages. New packages: [data.Updates]</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadHostPackageFailed</td><td>error</td><td>com.vmware.vcIntegrity.DownloadHostPackageFailed|Could not download host patch packages.</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadHostUpdate</td><td>info</td><td>com.vmware.vcIntegrity.DownloadHostUpdate|Successfully downloaded host patch definitions. New patches: [data.Updates]</td></tr> <tr><td>com.vmware.vcIntegrity.DownloadHostUpdateFailed</td><td>error</td><td>com.vmware.vcIntegrity.DownloadHostUpdateFailed|Could not download host patch definitions.</td></tr> <tr><td>com.vmware.vcIntegrity.EnableToolsRemediateOnReboot</td><td>info</td><td>com.vmware.vcIntegrity.EnableToolsRemediateOnReboot|Successfully enabled the option for VMware Tools upgrade on VM power cycle for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.EnableToolsRemediateOnRebootFailed</td><td>error</td><td>com.vmware.vcIntegrity.EnableToolsRemediateOnRebootFailed|Could not enable the option for VMware Tools upgrade on VM power cycle for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.FailToLock</td><td>warning</td><td>com.vmware.vcIntegrity.FailToLock|There are running tasks for the entity [data.name] that cannot finish within a specific time. The operation will stop.</td></tr> <tr><td>com.vmware.vcIntegrity.FtFailedEvent</td><td></td><td>com.vmware.vcIntegrity.FtFailedEvent|event.com.vmware.vcIntegrity.FtFailedEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.GADvdMountError</td><td>error</td><td>com.vmware.vcIntegrity.GADvdMountError|VMware vSphere Update Manager Guest Agent could not access the DVD drive on {vm.name}. Verify that a DVD drive is available and retry the operation.</td></tr> <tr><td>com.vmware.vcIntegrity.GAError</td><td>error</td><td>com.vmware.vcIntegrity.GAError|An internal error occurred in communication with VMware vSphere Update Manager Guest Agent on {vm.name}. Verify that the VM is powered on and retry the operation.</td></tr> <tr><td>com.vmware.vcIntegrity.GAInstallFailed</td><td>error</td><td>com.vmware.vcIntegrity.GAInstallFailed|Could not install VMware vSphere Update Manager Guest Agent on {vm.name}. Make sure that the VM is powered on.</td></tr> <tr><td>com.vmware.vcIntegrity.GAInstalled</td><td>info</td><td>com.vmware.vcIntegrity.GAInstalled|VMware vSphere Update Manager Guest Agent successfully installed on {vm.name}.</td></tr> <tr><td>com.vmware.vcIntegrity.GARuntimeError</td><td>error</td><td>com.vmware.vcIntegrity.GARuntimeError|An unknown internal error occurred during the required operation on {vm.name}. Check the logs for more details and retry the operation.</td></tr> <tr><td>com.vmware.vcIntegrity.GATimeout</td><td>error</td><td>com.vmware.vcIntegrity.GATimeout|VMware vSphere Update Manager Guest Agent could not respond in time on {vm.name}. Verify that the VM is powered on and that the Guest Agent is running.</td></tr> <tr><td>com.vmware.vcIntegrity.HostFirewallClose</td><td>info</td><td>com.vmware.vcIntegrity.HostFirewallClose|Close [data.name] firewall ports.</td></tr> <tr><td>com.vmware.vcIntegrity.HostFirewallOpen</td><td>info</td><td>com.vmware.vcIntegrity.HostFirewallOpen|Open [data.name] firewall ports.</td></tr> <tr><td>com.vmware.vcIntegrity.HostPatchBundleImportCancelledEvent</td><td></td><td>com.vmware.vcIntegrity.HostPatchBundleImportCancelledEvent|event.com.vmware.vcIntegrity.HostPatchBundleImportCancelledEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.HostPatchBundleImportSuccessfulEvent</td><td></td><td>com.vmware.vcIntegrity.HostPatchBundleImportSuccessfulEvent|event.com.vmware.vcIntegrity.HostPatchBundleImportSuccessfulEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.HostPatchBundleImportUnknownErrorEvent</td><td></td><td>com.vmware.vcIntegrity.HostPatchBundleImportUnknownErrorEvent|event.com.vmware.vcIntegrity.HostPatchBundleImportUnknownErrorEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.HostPatchInputRecalledFailure</td><td></td><td>com.vmware.vcIntegrity.HostPatchInputRecalledFailure|event.com.vmware.vcIntegrity.HostPatchInputRecalledFailure.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.HostPatchPrerequisiteRecalledFailure</td><td></td><td>com.vmware.vcIntegrity.HostPatchPrerequisiteRecalledFailure|event.com.vmware.vcIntegrity.HostPatchPrerequisiteRecalledFailure.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.HostPatchRemediateHostConflict</td><td>error</td><td>com.vmware.vcIntegrity.HostPatchRemediateHostConflict|Host patch [data.patch] conflicts with the package [data.conflictPackage] installed on the host and cannot be remediated. Remove the patch from the baseline or include any suggested additional patches in the baseline and retry remediation operation.</td></tr> <tr><td>com.vmware.vcIntegrity.HostPatchRemediateInputConflict</td><td>error</td><td>com.vmware.vcIntegrity.HostPatchRemediateInputConflict|Host patch [data.patch] conflicts with patch [data.conflictPatch] included in the baseline and cannot be remediated. Remove either of the patch from the baseline and retry the remediation.</td></tr> <tr><td>com.vmware.vcIntegrity.HostPatchStageHostConflict</td><td>error</td><td>com.vmware.vcIntegrity.HostPatchStageHostConflict|Host patch [data.patch] conflicts with the package [data.conflictPackage] installed on the host and cannot be staged. Remove the patch from the baseline or include any suggested additional patches in the baseline and retry stage operation.</td></tr> <tr><td>com.vmware.vcIntegrity.HostPatchStageInputConflict</td><td>error</td><td>com.vmware.vcIntegrity.HostPatchStageInputConflict|Host patch [data.patch] conflicts with patch [data.conflictPatch] included in the baseline and cannot be staged. Remove either of the patch from the baseline and retry the stage operation.</td></tr> <tr><td>com.vmware.vcIntegrity.HostSkippedDpmEvent</td><td>warning</td><td>com.vmware.vcIntegrity.HostSkippedDpmEvent|Cannot remediate host {host.name} because it is a part of a VMware DPM enabled cluster.</td></tr> <tr><td>com.vmware.vcIntegrity.HostSkippedDpmFtEvent</td><td>warning</td><td>com.vmware.vcIntegrity.HostSkippedDpmFtEvent|Cannot remediate host {host.name} because it is a part of a VMware DPM enabled cluster and contains one or more Primary or Secondary VMs on which FT is enabled.</td></tr> <tr><td>com.vmware.vcIntegrity.HostSkippedDpmScanEvent</td><td>warning</td><td>com.vmware.vcIntegrity.HostSkippedDpmScanEvent|Cannot scan host {host.name} because it is a part of a VMware DPM enabled cluster.</td></tr> <tr><td>com.vmware.vcIntegrity.HostSkippedDpmStageEvent</td><td>warning</td><td>com.vmware.vcIntegrity.HostSkippedDpmStageEvent|Cannot stage host {host.name} because it is a part of a VMware DPM enabled cluster.</td></tr> <tr><td>com.vmware.vcIntegrity.HostSkippedFtDiffPatchesEvent</td><td>warning</td><td>com.vmware.vcIntegrity.HostSkippedFtDiffPatchesEvent|Host {host.name} has FT enabled VMs. If you apply different patches to hosts in a cluster, FT cannot be re-enabled.</td></tr> <tr><td>com.vmware.vcIntegrity.HostSkippedFtEvent</td><td>warning</td><td>com.vmware.vcIntegrity.HostSkippedFtEvent|Cannot remediate host {host.name} because it contains one or more Primary or Secondary VMs on which FT is enabled.</td></tr> <tr><td>com.vmware.vcIntegrity.HostSkippedFtPairEvent</td><td>warning</td><td>com.vmware.vcIntegrity.HostSkippedFtPairEvent|Host {host.name} has FT enabled VMs. The host on which the Secondary VMs reside is not selected for remediation. As a result FT cannot be re-enabled.</td></tr> <tr><td>com.vmware.vcIntegrity.HostSkippedHacEvent</td><td>warning</td><td>com.vmware.vcIntegrity.HostSkippedHacEvent|Cannot remediate host {host.name} because it is a part of a HA admission control enabled cluster.</td></tr> <tr><td>com.vmware.vcIntegrity.HostSkippedPxeUpgradeUnsupported</td><td>warning</td><td>com.vmware.vcIntegrity.HostSkippedPxeUpgradeUnsupported|Upgrade operations are not supported on host {host.name} because it is PXE booted.</td></tr> <tr><td>com.vmware.vcIntegrity.HostSkippedRemovableDeviceEvent</td><td>warning</td><td>com.vmware.vcIntegrity.HostSkippedRemovableDeviceEvent|Cannot remediate host {host.name} because it has VMs with a connected removable device. Disconnect all removable devices before remediation.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorEsxFileDownload</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorEsxFileDownload|Host [data.name] cannot download files from the VMware vSphere Update Manager patch store. Check the network connectivity and firewall setup, and verify that the host can access the configured patch store.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorNotInstallable</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorNotInstallable|The selected patches [data.arg1] cannot be installed on the host.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateConflictDependencies</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateConflictDependencies|The patches selected for remediation on the host [data.name] depend on other patches that have conflicts.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateDefault</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateDefault|Remediation did not succeed for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateDeviceAttached</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateDeviceAttached|Remediation did not succeed for [data.name]. The host has virtual machines [data.arg1] with connected removable media devices. This prevents the host from entering maintenance mode. Disconnect the removable devices and try again.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateEnterMmode</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateEnterMmode|Remediation did not succeed for [data.name]. The host could not enter maintenance mode.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateExitMmode</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateExitMmode|Remediation did not succeed for [data.name]. The host could not exit maintenance mode.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateHostReboot</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateHostReboot|Remediation did not succeed for [data.name]. The host did not reboot after remediation.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateHostRebootReconnect</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateHostRebootReconnect|Remediation did not succeed for [data.name]. VMware vSphere Update Manager timed out waiting for the host to reconnect after a reboot.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateHostReconnect</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateHostReconnect|Remediation did not succeed for [data.name]. VMware vSphere Update Manager timed out waiting for the host to reconnect.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateHostRestoreVm</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateHostRestoreVm|Remediation did not succeed for [data.name]. Restoring the power state or device connection state for one or more virtual machines on the host did not succeed.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateMetadataCorrupt</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateMetadataCorrupt|Remediation did not succeed for [data.name]. The patch metadata is corrupted. This might be caused by an invalid format of metadata content. You can try to re-download the patches.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateVibDownload</td><td>error</td><td>com.vmware.vcIntegrity.HostUpdateErrorRemediateVibDownload|Remediation did not succeed for [data.name]. There were errors while downloading one or more software packages. Check the VMware vSphere Update Manager network connectivity settings.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeAgentDeployFailure</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradeAgentDeployFailure|Cannot deploy upgrade agent on host.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailConflictingVibs</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailConflictingVibs|The upgrade contains conflicting VIBs. Remove the conflicting VIBs or use Image Builder to create a custom upgrade ISO image that contains the newer versions of the conflicting VIBs, and try to upgrade again.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailDvsBreakageUnsure</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailDvsBreakageUnsure|Cannot determine whether the upgrade breaks Cisco Nexus 1000V virtual network switch feature on the host. If the host does not have the feature, you can ignore this warning.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailDvsBreaks</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailDvsBreaks|Cisco Nexus 1000V virtual network switch feature installed on the host will be removed during upgrade.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailEESXInsufficientSpaceForImage</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailEESXInsufficientSpaceForImage|Cannot create a ramdisk of size [data.expected]MB to store the upgrade image. Check if the host has sufficient memory.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailESXInsufficientSpaceForImage</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailESXInsufficientSpaceForImage|Upgrade requires at least [data.expected]MB free space on boot partition to store the upgrade image, only [data.found]MB found. Retry after freeing up sufficient space or perform a CD-based installation.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailHostHardwareMismatch</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailHostHardwareMismatch|The upgrade is not supported on the host hardware. The upgrade ISO image contains VIBs that failed the host hardware compatibility check.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailIncompatibleDPInImage</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailIncompatibleDPInImage|Cisco Nexus 1000V virtual network switch software package [data.found] in the upgrade image is incompatible with the Cisco Nexus 1000V software package [data.expected] installed on the host. Upgrading the host will remove the feature from the host.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailIncompatiblePartitionLayout</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailIncompatiblePartitionLayout|The host cannot be upgraded due to incompatible partition layout.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailIncompatiblePasswords</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailIncompatiblePasswords|The passwords cannot be migrated because the password encryption scheme is incompatible.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailIncompatibleWithDvsCP</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailIncompatibleWithDvsCP|Cisco Nexus 1000V virtual network switch software package [data.found] in the upgrade image is incompatible with the Cisco Nexus 1000V VSM. Upgrading the host will remove the feature from the host.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailInsufficientMemory</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailInsufficientMemory|Insufficient memory found on the host: [data.expected]MB required, [data.found]MB found.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailInsufficientSpaceForConfig</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailInsufficientSpaceForConfig|Upgrade requires at least [data.expected]MB free space on a local VMFS datastore, only [data.found]MB found.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailMissingDPBreaksDvsCP</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailMissingDPBreaksDvsCP|There is no Cisco Nexus 1000V virtual network switch software package in the upgrade image that is compatible with the Cisco Nexus 1000V VSM. Upgrading the host will remove the feature from the host.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailMissingDPInImage</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailMissingDPInImage|There is no Cisco Nexus 1000V virtual network switch software package in the upgrade image. Upgrading the host will remove the feature from the host.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailNoMD5RootPassword</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailNoMD5RootPassword|The root password is not using MD5 hashing, causing it to be authenticated up to only 8 characters. For instructions on how to correct this, see VMware KB 1024500 at http://kb.vmware.com/kb/1024500.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailNoMinCpuCores</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailNoMinCpuCores|New ESXi version requires a minimum of [data.expected] processor cores.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailNoVt</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailNoVt|Processor does not support hardware virtualization or it is disabled in BIOS. Virtual machine performance may be slow.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailNonVmwareSoftware</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailNonVmwareSoftware|The software modules [data.found] found on the host are not part of the upgrade image. These modules will be removed during upgrade.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailNxbitEnabled</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailNxbitEnabled|No eXecute (NX) bit is not enabled on the host. New ESXi version requires a CPU with NX/XD bit supported and enabled.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailPendingReboot</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailPendingReboot|Host software configuration requires a reboot. Reboot the host and try upgrade again.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailPowerPathBreaks</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailPowerPathBreaks|EMC PowerPath module [data.found] installed on the host will be removed during upgrade.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailScriptInitFailed</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailScriptInitFailed|Host upgrade validity checks are not successful.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailTbootRequired</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailTbootRequired|Trusted boot is enabled on the host but the upgrade does not contain the software package esx-tboot. Upgrading the host will remove the trusted boot feature.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailUnknown</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailUnknown|The upgrade precheck script returned unknown error.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailUnsupportedConfig</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailUnsupportedConfig|Error in ESX configuration file (esx.conf).</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailUnsupportedDevices</td><td>warning</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailUnsupportedDevices|Unsupported devices [data.found] found on the host.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailUnsupportedHostVersion</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailUnsupportedHostVersion|Host version [data.found] is not supported for upgrade.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailUnsupportedLongMode</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradePrecheckTestFailUnsupportedLongMode|Host CPU is unsupported. New ESXi version requires a 64-bit CPU with support for LAHF/SAHF instructions in long mode.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressAborted</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradeProgressAborted|Host upgrade installer stopped.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressAuth</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressAuth|Host upgrade in progress: Configuring authentication.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressBootloader</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressBootloader|Host upgrade in progress: Boot setup.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressClearpart</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressClearpart|Host upgrade in progress: Clearing partitions.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressComplete</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressComplete|Host upgrade installer completed.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressKeyboard</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressKeyboard|Host upgrade in progress: Setting keyboard.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressLanguage</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressLanguage|Host upgrade in progress: Setting language.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressMigrating</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressMigrating|Host upgrade in progress: Migrating ESX v3 configuration to ESX v4.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressMount</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressMount|Host upgrade in progress: Mounting file systems.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressNetworking</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressNetworking|Host upgrade in progress: Installing network configuration.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressPackages</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressPackages|Host upgrade in progress: Installing packages.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressPartphys</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressPartphys|Host upgrade in progress: Partitioning physical hard drives.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressPartvirt</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressPartvirt|Host upgrade in progress: Partitioning virtual hard drives.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressPostscript</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressPostscript|Host upgrade in progress: Running postinstallation script.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressRootpass</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressRootpass|Host upgrade in progress: Setting root password</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressTimezone</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressTimezone|Host upgrade in progress: Setting timezone.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeProgressUnknown</td><td>info</td><td>com.vmware.vcIntegrity.HostUpgradeProgressUnknown|Host upgrade in progress.</td></tr> <tr><td>com.vmware.vcIntegrity.HostUpgradeRunScriptFailure</td><td>error</td><td>com.vmware.vcIntegrity.HostUpgradeRunScriptFailure|Cannot run upgrade script on host.</td></tr> <tr><td>com.vmware.vcIntegrity.IncompatibleTools</td><td>error</td><td>com.vmware.vcIntegrity.IncompatibleTools|Could not install VMware vSphere Update Manager Guest Agent on {vm.name} because VMware Tools is not installed or is of an incompatible version. The required version is [data.requiredVersion] and the installed version is [data.installedVersion].</td></tr> <tr><td>com.vmware.vcIntegrity.InstallAddOnUpdate</td><td>info</td><td>com.vmware.vcIntegrity.InstallAddOnUpdate|The following additional patches are included to resolve a conflict for installation on [data.entityName]: [data.message].</td></tr> <tr><td>com.vmware.vcIntegrity.InstallSuggestion</td><td>info</td><td>com.vmware.vcIntegrity.InstallSuggestion|To resolve a conflict for installation on [data.entityName], the following additional patches might need to be included in the baseline: [data.message].</td></tr> <tr><td>com.vmware.vcIntegrity.InstallSuggestionNotFound</td><td>info</td><td>com.vmware.vcIntegrity.InstallSuggestionNotFound|VMware vSphere Update Manager could not find patches to resolve the conflict for installation on [data.entityName].</td></tr> <tr><td>com.vmware.vcIntegrity.InstallUpdate</td><td>info</td><td>com.vmware.vcIntegrity.InstallUpdate|Installation of patches [data.updateId] started on host [data.entityName].</td></tr> <tr><td>com.vmware.vcIntegrity.InstallUpdateComplete</td><td>info</td><td>com.vmware.vcIntegrity.InstallUpdateComplete|Installation of patches succeeded on [data.entityName].</td></tr> <tr><td>com.vmware.vcIntegrity.InstallUpdateError</td><td>error</td><td>com.vmware.vcIntegrity.InstallUpdateError|Could not install patches on [data.entityName].</td></tr> <tr><td>com.vmware.vcIntegrity.LinuxOffLineScanNotSupported</td><td>error</td><td>com.vmware.vcIntegrity.LinuxOffLineScanNotSupported|Cannot scan [data.name] for patches. Scan of powered off or suspended Linux VMs is not supported.</td></tr> <tr><td>com.vmware.vcIntegrity.LowDiskSpace</td><td>warning</td><td>com.vmware.vcIntegrity.LowDiskSpace|VMware vSphere Update Manager is running out of storage space. Location: [data.Volume]. Available space: [data.FreeSpace]MB.</td></tr> <tr><td>com.vmware.vcIntegrity.MetadataCorrupted</td><td>info</td><td>com.vmware.vcIntegrity.MetadataCorrupted|Patch definition for [data.name] is corrupt. Check the logs for more details. Re-downloading patch definitions might resolve this problem.</td></tr> <tr><td>com.vmware.vcIntegrity.MetadataNotFound</td><td>info</td><td>com.vmware.vcIntegrity.MetadataNotFound|Patch definitions for [data.name] are missing. Download patch definitions first.</td></tr> <tr><td>com.vmware.vcIntegrity.NoRequiredLicense</td><td>error</td><td>com.vmware.vcIntegrity.NoRequiredLicense|There is no VMware vSphere Update Manager license for [data.name] for the required operation.</td></tr> <tr><td>com.vmware.vcIntegrity.NotificationCriticalInfoAlertEvent</td><td></td><td>com.vmware.vcIntegrity.NotificationCriticalInfoAlertEvent|event.com.vmware.vcIntegrity.NotificationCriticalInfoAlertEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.NotificationDownloadAlertEvent</td><td></td><td>com.vmware.vcIntegrity.NotificationDownloadAlertEvent|event.com.vmware.vcIntegrity.NotificationDownloadAlertEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.NotificationImportantInfoAlertEvent</td><td></td><td>com.vmware.vcIntegrity.NotificationImportantInfoAlertEvent|event.com.vmware.vcIntegrity.NotificationImportantInfoAlertEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.NotificationModerateInfoAlertEvent</td><td></td><td>com.vmware.vcIntegrity.NotificationModerateInfoAlertEvent|event.com.vmware.vcIntegrity.NotificationModerateInfoAlertEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.NotificationRecallAlertEvent</td><td></td><td>com.vmware.vcIntegrity.NotificationRecallAlertEvent|event.com.vmware.vcIntegrity.NotificationRecallAlertEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.NotificationRecallFixAlertEvent</td><td></td><td>com.vmware.vcIntegrity.NotificationRecallFixAlertEvent|event.com.vmware.vcIntegrity.NotificationRecallFixAlertEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.PXEBootedHostEvent</td><td></td><td>com.vmware.vcIntegrity.PXEBootedHostEvent|event.com.vmware.vcIntegrity.PXEBootedHostEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.PackageImportEvent</td><td></td><td>com.vmware.vcIntegrity.PackageImportEvent|event.com.vmware.vcIntegrity.PackageImportEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.PackageImportFailureEvent</td><td></td><td>com.vmware.vcIntegrity.PackageImportFailureEvent|event.com.vmware.vcIntegrity.PackageImportFailureEvent.fullFormat</td></tr> <tr><td>com.vmware.vcIntegrity.RebootHostComplete</td><td>info</td><td>com.vmware.vcIntegrity.RebootHostComplete|Host [data.entityName] is successfully rebooted.</td></tr> <tr><td>com.vmware.vcIntegrity.RebootHostError</td><td>error</td><td>com.vmware.vcIntegrity.RebootHostError|Cannot reboot host [data.entityName].</td></tr> <tr><td>com.vmware.vcIntegrity.RebootHostStart</td><td>info</td><td>com.vmware.vcIntegrity.RebootHostStart|Start rebooting host [data.entityName].</td></tr> <tr><td>com.vmware.vcIntegrity.RebootHostWait</td><td>info</td><td>com.vmware.vcIntegrity.RebootHostWait|Waiting for host [data.entityName] to reboot.</td></tr> <tr><td>com.vmware.vcIntegrity.ReconfigureClusterFailedEvent</td><td>error</td><td>com.vmware.vcIntegrity.ReconfigureClusterFailedEvent|VMware vSphere Update Manager could not restore HA admission control/DPM settings for cluster {computeResource.name} to their original values. These settings have been changed for patch installation. Check the cluster settings and restore them manually.</td></tr> <tr><td>com.vmware.vcIntegrity.Remediate</td><td>info</td><td>com.vmware.vcIntegrity.Remediate|Remediation succeeded for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.RemediateDisconnectedHost</td><td>error</td><td>com.vmware.vcIntegrity.RemediateDisconnectedHost|Could not remediate {host.name} because the host has an invalid connection state: [data.state].</td></tr> <tr><td>com.vmware.vcIntegrity.RemediateDisconnectedVm</td><td>error</td><td>com.vmware.vcIntegrity.RemediateDisconnectedVm|Could not remediate {vm.name} because the virtual machine has an invalid connection state: [data.state].</td></tr> <tr><td>com.vmware.vcIntegrity.RemediateDpmDisableHost</td><td>error</td><td>com.vmware.vcIntegrity.RemediateDpmDisableHost|Could not remediate host {host.name} because its power state is invalid. The host is in standby mode and the individual VMware DPM settings of the host are set to Disabled or Manual.</td></tr> <tr><td>com.vmware.vcIntegrity.RemediateFailed</td><td>error</td><td>com.vmware.vcIntegrity.RemediateFailed|Remediation did not succeed for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.RemediateHostInvalidPowerState</td><td>error</td><td>com.vmware.vcIntegrity.RemediateHostInvalidPowerState|Cannot remediate the host {host.name} because its power state is [data.state].</td></tr> <tr><td>com.vmware.vcIntegrity.RemediateHostOnUnsupportedHost</td><td>error</td><td>com.vmware.vcIntegrity.RemediateHostOnUnsupportedHost|Could not remediate {host.name} because it is of unsupported version [data.version].</td></tr> <tr><td>com.vmware.vcIntegrity.RemediateOrphanedVm</td><td>info</td><td>com.vmware.vcIntegrity.RemediateOrphanedVm|Could not remediate orphaned VM {vm.name}.</td></tr> <tr><td>com.vmware.vcIntegrity.RemediateStart</td><td>info</td><td>com.vmware.vcIntegrity.RemediateStart|Remediating object [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.RemediateVmOnUnsupportedHost</td><td>error</td><td>com.vmware.vcIntegrity.RemediateVmOnUnsupportedHost|Could not remediate {vm.name} because host {host.name} is of unsupported version [data.version].</td></tr> <tr><td>com.vmware.vcIntegrity.RemediationStatusEvent</td><td>info</td><td>com.vmware.vcIntegrity.RemediationStatusEvent|Current progress of remediation: [data.noOfSucceededHosts] hosts completed successfully, [data.noOfFailedHosts] hosts completed with errors, [data.noOfHostsBeingRemediatedCurrently] hosts are being remediated, [data.noOfWaitingHosts] hosts are waiting to start remediation, and [data.noOfRetryHosts] hosts could not enter maintenance mode and are waiting to retry.</td></tr> <tr><td>com.vmware.vcIntegrity.Scan</td><td>info</td><td>com.vmware.vcIntegrity.Scan|Successfully scanned [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.ScanCancelled</td><td>error</td><td>com.vmware.vcIntegrity.ScanCancelled|Scanning of [data.name] is canceled by user.</td></tr> <tr><td>com.vmware.vcIntegrity.ScanDisconnectedHost</td><td>error</td><td>com.vmware.vcIntegrity.ScanDisconnectedHost|Could not scan {host.name} because the host has an invalid connection state: [data.state].</td></tr> <tr><td>com.vmware.vcIntegrity.ScanDisconnectedVm</td><td>error</td><td>com.vmware.vcIntegrity.ScanDisconnectedVm|Could not scan {vm.name} because the virtual machine has an invalid connection state: [data.state].</td></tr> <tr><td>com.vmware.vcIntegrity.ScanDpmDisableHost</td><td>error</td><td>com.vmware.vcIntegrity.ScanDpmDisableHost|Could not scan host {host.name} because its power state is invalid. The host is in standby mode and the individual VMware DPM settings of the host are set to Disabled or Manual.</td></tr> <tr><td>com.vmware.vcIntegrity.ScanFailed</td><td>error</td><td>com.vmware.vcIntegrity.ScanFailed|Could not scan [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.ScanHostInvalidPowerState</td><td>error</td><td>com.vmware.vcIntegrity.ScanHostInvalidPowerState|Cannot scan the host {host.name} because its power state is [data.state].</td></tr> <tr><td>com.vmware.vcIntegrity.ScanHostOnUnsupportedHost</td><td>error</td><td>com.vmware.vcIntegrity.ScanHostOnUnsupportedHost|Could not scan {host.name} for patches because it is of unsupported version [data.version].</td></tr> <tr><td>com.vmware.vcIntegrity.ScanMissingUpdate</td><td>warning</td><td>com.vmware.vcIntegrity.ScanMissingUpdate|Found a missing patch: [data.message] when scanning [data.name]. Re-downloading patch definitions might resolve this problem.</td></tr> <tr><td>com.vmware.vcIntegrity.ScanOrphanedVm</td><td>info</td><td>com.vmware.vcIntegrity.ScanOrphanedVm|Could not scan orphaned VM {vm.name}.</td></tr> <tr><td>com.vmware.vcIntegrity.ScanStart</td><td>info</td><td>com.vmware.vcIntegrity.ScanStart|Scanning object [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.ScanUnsupportedVolume</td><td>warning</td><td>com.vmware.vcIntegrity.ScanUnsupportedVolume|{vm.name} contains an unsupported volume [data.volumeLabel]. Scan results for this VM might be incomplete.</td></tr> <tr><td>com.vmware.vcIntegrity.ScanVmOnUnsupportedHost</td><td>error</td><td>com.vmware.vcIntegrity.ScanVmOnUnsupportedHost|Could not scan {vm.name} because host {host.name} is of unsupported version [data.version].</td></tr> <tr><td>com.vmware.vcIntegrity.SequentialRemediateFailedEvent</td><td>error</td><td>com.vmware.vcIntegrity.SequentialRemediateFailedEvent|An error occured during the sequential remediation of hosts in cluster {computeResource.name}. Check the related events for more details.</td></tr> <tr><td>com.vmware.vcIntegrity.SkipSuspendedVm</td><td>info</td><td>com.vmware.vcIntegrity.SkipSuspendedVm|Suspended VM {vm.name} has been skipped.</td></tr> <tr><td>com.vmware.vcIntegrity.Stage</td><td>info</td><td>com.vmware.vcIntegrity.Stage|Staging succeeded for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.StageDisconnectedHost</td><td>error</td><td>com.vmware.vcIntegrity.StageDisconnectedHost|Could not stage patches to {host.name} because the host has an invalid connection state: [data.state].</td></tr> <tr><td>com.vmware.vcIntegrity.StageDpmDisableHost</td><td>error</td><td>com.vmware.vcIntegrity.StageDpmDisableHost|Could not stage patches to host {host.name} because its power state is invalid. The host is in standby mode and the individual VMware DPM settings of the host are set to Disabled or Manual.</td></tr> <tr><td>com.vmware.vcIntegrity.StageFailed</td><td>error</td><td>com.vmware.vcIntegrity.StageFailed|Staging did not succeed for [data.name][data.message].</td></tr> <tr><td>com.vmware.vcIntegrity.StageHostInvalidPowerState</td><td>error</td><td>com.vmware.vcIntegrity.StageHostInvalidPowerState|Cannot stage patches to the host {host.name} because its power state is [data.state].</td></tr> <tr><td>com.vmware.vcIntegrity.StageHostOnUnsupportedHost</td><td>error</td><td>com.vmware.vcIntegrity.StageHostOnUnsupportedHost|Could not stage patches to {host.name} because it is of unsupported version [data.version].</td></tr> <tr><td>com.vmware.vcIntegrity.StageStart</td><td>info</td><td>com.vmware.vcIntegrity.StageStart|Staging patches to host [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.StageUpdate</td><td>info</td><td>com.vmware.vcIntegrity.StageUpdate|Started staging of patches [data.updateId] on [data.entityName].</td></tr> <tr><td>com.vmware.vcIntegrity.StageUpdateComplete</td><td>info</td><td>com.vmware.vcIntegrity.StageUpdateComplete|Staging of patch to [data.entityName] succeeded.</td></tr> <tr><td>com.vmware.vcIntegrity.StageUpdateError</td><td>error</td><td>com.vmware.vcIntegrity.StageUpdateError|Cannot stage patch [data.updateId] to [data.entityName].</td></tr> <tr><td>com.vmware.vcIntegrity.SysprepDisabled</td><td>info</td><td>com.vmware.vcIntegrity.SysprepDisabled|Sysprep is disabled during the remediation.</td></tr> <tr><td>com.vmware.vcIntegrity.SysprepEnabled</td><td>info</td><td>com.vmware.vcIntegrity.SysprepEnabled|Sysprep settings are restored.</td></tr> <tr><td>com.vmware.vcIntegrity.SysprepHandleFailure</td><td>error</td><td>com.vmware.vcIntegrity.SysprepHandleFailure|Cannot access the sysprep settings for VM {vm.name}. Retry the operation after disabling sysprep for the VM.</td></tr> <tr><td>com.vmware.vcIntegrity.SysprepNotFound</td><td>error</td><td>com.vmware.vcIntegrity.SysprepNotFound|Cannot locate the sysprep settings for VM {vm.name}. For Windows 7 and Windows 2008 R2, offline VM remediation is supported only if the system volume is present in the primary disk partition. Retry the operation after disabling sysprep for the VM.</td></tr> <tr><td>com.vmware.vcIntegrity.ToolsRemediate</td><td>info</td><td>com.vmware.vcIntegrity.ToolsRemediate|VMware Tools upgrade succeeded for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.ToolsRemediateFailed</td><td>error</td><td>com.vmware.vcIntegrity.ToolsRemediateFailed|VMware Tools upgrade did not succeed for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.ToolsScan</td><td>info</td><td>com.vmware.vcIntegrity.ToolsScan|Successfully scanned [data.name] for VMware Tools upgrades.</td></tr> <tr><td>com.vmware.vcIntegrity.ToolsScanFailed</td><td>error</td><td>com.vmware.vcIntegrity.ToolsScanFailed|Could not scan [data.name] for VMware Tools upgrades.</td></tr> <tr><td>com.vmware.vcIntegrity.ToolsScanInstallNotSupported</td><td>warning</td><td>com.vmware.vcIntegrity.ToolsScanInstallNotSupported|VMware Tools is not installed on [data.name]. VMware vSphere Update Manager supports upgrading only an existing VMware Tools installation.</td></tr> <tr><td>com.vmware.vcIntegrity.ToolsUpgradeRemediateSkippedOnHost</td><td>warning</td><td>com.vmware.vcIntegrity.ToolsUpgradeRemediateSkippedOnHost|VMware Tools upgrade was not performed on {vm.name}. VMware Tools upgrade is supported only for VMs that run on ESX/ESXi 4.0 and higher. VMware Tools upgrade is not supported for virtual appliances.</td></tr> <tr><td>com.vmware.vcIntegrity.ToolsUpgradeScanSkippedOnHost</td><td>warning</td><td>com.vmware.vcIntegrity.ToolsUpgradeScanSkippedOnHost|VMware Tools upgrade scan was not performed on {vm.name}. VMware Tools upgrade scan is supported only for VMs that run on ESX/ESXi 4.0 and higher. VMware Tools upgrade scan is not supported for virtual appliances.</td></tr> <tr><td>com.vmware.vcIntegrity.UnsupportedHostRemediateSpecialVMEvent</td><td>error</td><td>com.vmware.vcIntegrity.UnsupportedHostRemediateSpecialVMEvent|The host [data.name] has a VM [data.vm] with VMware vSphere Update Manager or VMware vCenter Server installed. The VM must be moved to another host for the remediation to proceed.</td></tr> <tr><td>com.vmware.vcIntegrity.UnsupportedLinuxAction</td><td>warning</td><td>com.vmware.vcIntegrity.UnsupportedLinuxAction|Action is not supported for Linux VM/VA {vm.name}. VMware Tools is not installed or the machine cannot start.</td></tr> <tr><td>com.vmware.vcIntegrity.UnsupportedOs</td><td>warning</td><td>com.vmware.vcIntegrity.UnsupportedOs|Scan or remediation is not supported on [data.name] because of unsupported OS [data.os].</td></tr> <tr><td>com.vmware.vcIntegrity.UnsupportedPXEBootHost</td><td>info</td><td>com.vmware.vcIntegrity.UnsupportedPXEBootHost|Scanning, remediation, and staging are not supported on PXE booted ESXi hosts.</td></tr> <tr><td>com.vmware.vcIntegrity.UnsupportedSpecialVMEvent</td><td>error</td><td>com.vmware.vcIntegrity.UnsupportedSpecialVMEvent|VM [data.name] has either VMware vSphere Update Manager or VMware vCenter Server installed. This VM will be ignored for scan and remediation.</td></tr> <tr><td>com.vmware.vcIntegrity.UnsupportedVaAction</td><td>warning</td><td>com.vmware.vcIntegrity.UnsupportedVaAction|Action is not supported for offline or suspended virtual appliance {vm.name}. </td></tr> <tr><td>com.vmware.vcIntegrity.VAAutoUpdateOn</td><td>error</td><td>com.vmware.vcIntegrity.VAAutoUpdateOn|Auto update is set to ON for virtual appliance [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.VADiscovery</td><td>info</td><td>com.vmware.vcIntegrity.VADiscovery|Successfully discovered virtual appliance [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.VADiscoveryFailed</td><td>error</td><td>com.vmware.vcIntegrity.VADiscoveryFailed|Could not discover virtual appliance [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.VADownloadGenericFailure</td><td>error</td><td>com.vmware.vcIntegrity.VADownloadGenericFailure|Could not download virtual appliance upgrade metadata.</td></tr> <tr><td>com.vmware.vcIntegrity.VADownloadInvalidUrl</td><td>error</td><td>com.vmware.vcIntegrity.VADownloadInvalidUrl|[data.name] is not a valid virtual appliance download URL.</td></tr> <tr><td>com.vmware.vcIntegrity.VADownloadMetadataFailure</td><td>error</td><td>com.vmware.vcIntegrity.VADownloadMetadataFailure|Could not download virtual appliance upgrade metadata for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.VADownloadSuccess</td><td>info</td><td>com.vmware.vcIntegrity.VADownloadSuccess|Successfully downloaded virtual appliance upgrade metadata.</td></tr> <tr><td>com.vmware.vcIntegrity.VARepositoryAddressNotSet</td><td>error</td><td>com.vmware.vcIntegrity.VARepositoryAddressNotSet|No repository address is set for virtual appliance [data.name]. The appliance does not support updates by vCenter Server.</td></tr> <tr><td>com.vmware.vcIntegrity.VAScan</td><td>info</td><td>com.vmware.vcIntegrity.VAScan|Successfully scanned [data.name] for VA upgrades.</td></tr> <tr><td>com.vmware.vcIntegrity.VAScanFailed</td><td>error</td><td>com.vmware.vcIntegrity.VAScanFailed|Could not scan [data.name] for VA upgrades.</td></tr> <tr><td>com.vmware.vcIntegrity.VMHardwareUpgradeRemediate</td><td>info</td><td>com.vmware.vcIntegrity.VMHardwareUpgradeRemediate|Virtual Hardware upgrade succeeded for [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.VMHardwareUpgradeRemediateFailed</td><td>error</td><td>com.vmware.vcIntegrity.VMHardwareUpgradeRemediateFailed|Could not perform Virtual Hardware upgrade on [data.name].</td></tr> <tr><td>com.vmware.vcIntegrity.VMHardwareUpgradeRemediateSkippedOnHost</td><td>warning</td><td>com.vmware.vcIntegrity.VMHardwareUpgradeRemediateSkippedOnHost|Virtual Hardware upgrade was not performed for {vm.name}. Virtual Hardware upgrade is supported only for VMs that run on ESX/ESXi 4.0 and higher. Virtual Hardware upgrade is not supported for virtual appliances.</td></tr> <tr><td>com.vmware.vcIntegrity.VMHardwareUpgradeScan</td><td>info</td><td>com.vmware.vcIntegrity.VMHardwareUpgradeScan|Successfully scanned [data.name] for Virtual Hardware upgrades.</td></tr> <tr><td>com.vmware.vcIntegrity.VMHardwareUpgradeScanFailed</td><td>error</td><td>com.vmware.vcIntegrity.VMHardwareUpgradeScanFailed|Could not scan [data.name] for Virtual Hardware upgrades.</td></tr> <tr><td>com.vmware.vcIntegrity.VMHardwareUpgradeScanSkippedOnHost</td><td>warning</td><td>com.vmware.vcIntegrity.VMHardwareUpgradeScanSkippedOnHost|Virtual Hardware upgrade scan was not performed for {vm.name}. Virtual Hardware upgrade scan is supported only for VMs that run on ESX/ESXi 4.0 and higher. Virtual Hardware upgrade scan is not supported for virtual appliances.</td></tr> <tr><td>com.vmware.vcIntegrity.VMHardwareUpgradeToolsNotInstalled</td><td>error</td><td>com.vmware.vcIntegrity.VMHardwareUpgradeToolsNotInstalled|Virtual Hardware upgrade did not succeed for {vm.name}, because VMware Tools is not installed. To upgrade virtual hardware, VMware Tools must be the latest version.</td></tr> <tr><td>com.vmware.vcIntegrity.VMHardwareUpgradeToolsNotLatest</td><td>error</td><td>com.vmware.vcIntegrity.VMHardwareUpgradeToolsNotLatest|Virtual Hardware upgrade did not succeed for {vm.name}, because VMware Tools is not the latest version supported by the host. To upgrade virtual hardware, VMware Tools must be the latest version.</td></tr> <tr><td>com.vmware.vcIntegrity.VMHardwareUpgradeToolsUnknown</td><td>error</td><td>com.vmware.vcIntegrity.VMHardwareUpgradeToolsUnknown|Virtual Hardware upgrade did not succeed for {vm.name}, because VMware Tools state is unknown. To upgrade virtual hardware, VMware Tools must be the latest version.</td></tr> <tr><td>com.vmware.vcIntegrity.VMHardwareUpgradeToolsUnmanaged</td><td>error</td><td>com.vmware.vcIntegrity.VMHardwareUpgradeToolsUnmanaged|Virtual Hardware upgrade did not succeed for {vm.name}, because VMware Tools state is not managed by VMware vSphere. To upgrade virtual hardware, VMware Tools must be the latest version.</td></tr> <tr><td>com.vmware.vcIntegrity.VMToolsAutoUpgradeUnsupported</td><td>error</td><td>com.vmware.vcIntegrity.VMToolsAutoUpgradeUnsupported|The version of VMware Tools installed in {vm.name} does not support automatic upgrade. Upgrade VMware Tools manually.</td></tr> <tr><td>com.vmware.vcIntegrity.VMToolsNotRunning</td><td>error</td><td>com.vmware.vcIntegrity.VMToolsNotRunning|Error while waiting for VMware Tools to respond. Verify that VMware Tools is running in VM {vm.name}.</td></tr> <tr><td>com.vmware.vcIntegrity.VibPrerequisitesMissingForInstall</td><td>warning</td><td>com.vmware.vcIntegrity.VibPrerequisitesMissingForInstall|Patch [data.inputBulletin] was excluded from the remediation because its prerequisite [data.missingPrereq] is neither installed on the host nor included in the baseline. Include the prerequisites in a Patch or Extension baseline and retry the remediation. You can also add the baselines to a baseline group for convenience and perform the remediation.</td></tr> <tr><td>com.vmware.vcIntegrity.VibPrerequisitesMissingForStage</td><td>warning</td><td>com.vmware.vcIntegrity.VibPrerequisitesMissingForStage|Patch [data.inputBulletin] was excluded from the stage operation because its prerequisite [data.missingPrereq] is neither installed on the host nor included in the baseline. Include the prerequisites in a Patch or Extension baseline and retry the stage operation. You can also add the baselines to a baseline group for convenience and perform the stage operation.</td></tr> <tr><td>com.vmware.vcIntegrity.VmDevicesRestoreFailedEvent</td><td>error</td><td>com.vmware.vcIntegrity.VmDevicesRestoreFailedEvent|VMware vSphere Update Manager could not restore the original removable device connection settings for all VMs in cluster {computeResource.name}. These settings have been changed for patch installation. You can manually restore the settings for the VMs.</td></tr> <tr><td>com.vmware.vcIntegrity.VmMigrationFailedEvent</td><td>error</td><td>com.vmware.vcIntegrity.VmMigrationFailedEvent|Cannot migrate VM {vm.name} from [data.srcHost] to [data.destHost].</td></tr> <tr><td>com.vmware.vcIntegrity.VmPowerRestoreFailedEvent</td><td>error</td><td>com.vmware.vcIntegrity.VmPowerRestoreFailedEvent|VMware vSphere Update Manager could not restore the original power state for all VMs in cluster {computeResource.name}. These settings have been changed for patch installation. You can manually restore the original power state of the VMs.</td></tr> <tr><td>com.vmware.vcIntegrity.VmotionCompatibilityCheckFailedEvent</td><td>error</td><td>com.vmware.vcIntegrity.VmotionCompatibilityCheckFailedEvent|Cannot check compatibility of the VM {vm.name} for migration with vMotion to host [data.hostName].</td></tr> </table> </body></html>