---
title: "Event Reference"
description: "• Event AccountCreatedEvent This event records that an account was created on a host. Since VI API 2.0. For more information, see the VMware API reference • Event AccountRemovedEvent This event records that an account was removed from a host."
canonical: "https://helpcenter.veeam.com/docs/mp/vmware_reference/vceventsdoc.html"
breadcrumb: "Veeam MP for VMware Reference > vCenter Events > Event Reference"
dateModified: "2026-09-10"
---

# Event Reference

<a id="ACCOUNTCREATEDEVENT"></a>

• Event **AccountCreatedEvent**

This event records that an account was created on a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AccountCreatedEvent.html)

<a id="ACCOUNTREMOVEDEVENT"></a>

• Event **AccountRemovedEvent**

This event records that an account was removed from a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AccountRemovedEvent.html)

<a id="ACCOUNTUPDATEDEVENT"></a>

• Event **AccountUpdatedEvent**

This event records that an account was updated on a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AccountUpdatedEvent.html)

<a id="AD.EVENT.IMPORTCERTEVENT"></a>

• Event **ad.event.ImportCertEvent**

Import certificate succeeded

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="AD.EVENT.IMPORTCERTFAILEDEVENT"></a>

• Event **ad.event.ImportCertFailedEvent**

Import certificate failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="AD.EVENT.JOINDOMAINEVENT"></a>

• Event **ad.event.JoinDomainEvent**

Join domain succeeded

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="AD.EVENT.JOINDOMAINFAILEDEVENT"></a>

• Event **ad.event.JoinDomainFailedEvent**

Join domain failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="AD.EVENT.LEAVEDOMAINEVENT"></a>

• Event **ad.event.LeaveDomainEvent**

Leave domain succeeded

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="AD.EVENT.LEAVEDOMAINFAILEDEVENT"></a>

• Event **ad.event.LeaveDomainFailedEvent**

Leave domain failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ADMINPASSWORDNOTCHANGEDEVENT"></a>

• Event **AdminPasswordNotChangedEvent**

Default password for the Admin user on the host has not been changed.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AdminPasswordNotChangedEvent.html)

<a id="ALARMACKNOWLEDGEDEVENT"></a>

• Event **AlarmAcknowledgedEvent**

Alarm acknowledged

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmAcknowledgedEvent.html)

<a id="ALARMACTIONTRIGGEREDEVENT"></a>

• Event **AlarmActionTriggeredEvent**

This event records that an alarm was triggered.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmActionTriggeredEvent.html)

<a id="ALARMCLEAREDEVENT"></a>

• Event **AlarmClearedEvent**

Alarm cleared manually

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmClearedEvent.html)

<a id="ALARMCREATEDEVENT"></a>

• Event **AlarmCreatedEvent**

This event records the creation of an alarm.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmCreatedEvent.html)

<a id="ALARMEMAILCOMPLETEDEVENT"></a>

• Event **AlarmEmailCompletedEvent**

This event records the completion of an alarm email notification.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmEmailCompletedEvent.html)

<a id="ALARMEMAILFAILEDEVENT"></a>

• Event **AlarmEmailFailedEvent**

This event records a failure to complete an alarm email notification.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmEmailFailedEvent.html)

<a id="ALARMRECONFIGUREDEVENT"></a>

• Event **AlarmReconfiguredEvent**

This event records the reconfiguration of an alarm.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmReconfiguredEvent.html)

<a id="ALARMREMOVEDEVENT"></a>

• Event **AlarmRemovedEvent**

This event records the removal of an alarm.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmRemovedEvent.html)

<a id="ALARMSCRIPTCOMPLETEEVENT"></a>

• Event **AlarmScriptCompleteEvent**

This event records the completion of an alarm-triggered script.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmScriptCompleteEvent.html)

<a id="ALARMSCRIPTFAILEDEVENT"></a>

• Event **AlarmScriptFailedEvent**

This event records a failure to complete an alarm-triggered script.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmScriptFailedEvent.html)

<a id="ALARMSNMPCOMPLETEDEVENT"></a>

• Event **AlarmSnmpCompletedEvent**

This event records the completion of an alarm SNMP notification.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmSnmpCompletedEvent.html)

<a id="ALARMSNMPFAILEDEVENT"></a>

• Event **AlarmSnmpFailedEvent**

This event records a failure to complete an alarm SNMP notification.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmSnmpFailedEvent.html)

<a id="ALARMSTATUSCHANGEDEVENT"></a>

• Event **AlarmStatusChangedEvent**

This event records that an entity (such as a host or VM) has changed its overall status because an alarm was triggered. The event will show which entity and will indicate which alarm was triggered.

A host or VM alarm status changing from "green"/ "yellow" / "red" to "gray" may indicate that the host or VM has been shutdown.

If the alarm status is "yellow" or "red" then the icons in the VI Client will change.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlarmStatusChangedEvent.html)

<a id="ALLVIRTUALMACHINESLICENSEDEVENT"></a>

• Event **AllVirtualMachinesLicensedEvent**

This event records that the previously unlicensed virtual machines on the specified host are now licensed. After this event is entered into the event log, we expect to see that the configuration issue removed from the host managed object.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AllVirtualMachinesLicensedEvent.html)

<a id="ALREADYAUTHENTICATEDSESSIONEVENT"></a>

• Event **AlreadyAuthenticatedSessionEvent**

This event records a failed user logon due to the user already being logged on.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.AlreadyAuthenticatedSessionEvent.html)

<a id="BADUSERNAMESESSIONEVENT"></a>

• Event **BadUsernameSessionEvent**

This event records a failed user logon. Failed logons are due to no match existing between the provided user name and password combination and the combinations stored for authentication.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.BadUsernameSessionEvent.html)

<a id="CANCELEDHOSTOPERATIONEVENT"></a>

• Event **CanceledHostOperationEvent**

An operation performed on the host was canceled. Typically, a previous event in the sequence of events contains more information about the cause of this cancellation.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CanceledHostOperationEvent.html)

<a id="CHANGEOWNEROFFILEEVENT"></a>

• Event **ChangeOwnerOfFileEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ChangeOwnerOfFileEvent.html)

<a id="CHANGEOWNEROFFILEFAILEDEVENT"></a>

• Event **ChangeOwnerOfFileFailedEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ChangeOwnerOfFileFailedEvent.html)

<a id="CLUSTERCOMPLIANCECHECKEDEVENT"></a>

• Event **ClusterComplianceCheckedEvent**

This event records that a compliance check was triggered on the cluster.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ClusterComplianceCheckedEvent.html)

<a id="CLUSTERCREATEDEVENT"></a>

• Event **ClusterCreatedEvent**

This event records when a cluster is created.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ClusterCreatedEvent.html)

<a id="CLUSTERDESTROYEDEVENT"></a>

• Event **ClusterDestroyedEvent**

This event records when a cluster is destroyed.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ClusterDestroyedEvent.html)

<a id="CLUSTEROVERCOMMITTEDEVENT"></a>

• Event **ClusterOvercommittedEvent**

This event records when a cluster host capacity cannot satisfy resource configuration constraints.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ClusterOvercommittedEvent.html)

<a id="CLUSTERRECONFIGUREDEVENT"></a>

• Event **ClusterReconfiguredEvent**

This event records when a cluster is reconfigured.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ClusterReconfiguredEvent.html)

<a id="CLUSTERSTATUSCHANGEDEVENT"></a>

• Event **ClusterStatusChangedEvent**

This event records when a cluster overall status changed.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ClusterStatusChangedEvent.html)

<a id="COM.VMWARE.LICENSE.ADDLICENSEEVENT"></a>

• Event **com.vmware.license.AddLicenseEvent**

Added License

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.LICENSE.ASSIGNLICENSEEVENT"></a>

• Event **com.vmware.license.AssignLicenseEvent**

Assigned License

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.LICENSE.DLFDOWNLOADFAILEDEVENT"></a>

• Event **com.vmware.license.DLFDownloadFailedEvent**

Download License Information

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.LICENSE.LICENSEASSIGNFAILEDEVENT"></a>

• Event **com.vmware.license.LicenseAssignFailedEvent**

License assignment faults

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.LICENSE.LICENSECAPACITYEXCEEDEDEVENT"></a>

• Event **com.vmware.license.LicenseCapacityExceededEvent**

License usage exceeds the license capacity

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.LICENSE.LICENSEEXPIRYEVENT"></a>

• Event **com.vmware.license.LicenseExpiryEvent**

License Expiry

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.LICENSE.LICENSEUSERTHRESHOLDEXCEEDEDEVENT"></a>

• Event **com.vmware.license.LicenseUserThresholdExceededEvent**

License User Threshold Exceeded

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.LICENSE.REMOVELICENSEEVENT"></a>

• Event **com.vmware.license.RemoveLicenseEvent**

Removed License

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.LICENSE.UNASSIGNLICENSEEVENT"></a>

• Event **com.vmware.license.UnassignLicenseEvent**

Unassigned License

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.CIM.CIMGROUPHEALTHSTATECHANGED"></a>

• Event **com.vmware.vc.cim.CIMGroupHealthStateChanged**

Hardware Health Changed

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.DATASTORE.UPDATEDVMFILESEVENT"></a>

• Event **com.vmware.vc.datastore.UpdatedVmFilesEvent**

Updated VM files

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.DATASTORE.UPDATEVMFILESFAILEDEVENT"></a>

• Event **com.vmware.vc.datastore.UpdateVmFilesFailedEvent**

Failed to update VM files

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.DATASTORE.UPDATINGVMFILESEVENT"></a>

• Event **com.vmware.vc.datastore.UpdatingVmFilesEvent**

Updating VM Files

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.DVS.LACPCONFIGINCONSISTENTEVENT"></a>

• Event **com.vmware.vc.dvs.LacpConfigInconsistentEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.FT.VMAFFECTEDBYDASDISABLEDEVENT"></a>

• Event **com.vmware.vc.ft.VmAffectedByDasDisabledEvent**

VMware HA has been disabled

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.GUESTOPERATIONS.GUESTOPERATION"></a>

• Event **com.vmware.vc.guestOperations.GuestOperation**

Guest operation performed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.GUESTOPERATIONS.GUESTOPERATIONAUTHFAILURE"></a>

• Event **com.vmware.vc.guestOperations.GuestOperationAuthFailure**

Authentication failed for guest operation

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.ALLHOSTADDRSPINGABLE"></a>

• Event **com.vmware.vc.HA.AllHostAddrsPingable**

All vSphere HA isolation addresses are reachable by host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.ALLISOADDRSPINGABLE"></a>

• Event **com.vmware.vc.HA.AllIsoAddrsPingable**

All vSphere HA isolation addresses are reachable by host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.ANSWEREDVMLOCKLOSTQUESTIONEVENT"></a>

• Event **com.vmware.vc.HA.AnsweredVmLockLostQuestionEvent**

Lock-lost question was answered by vSphere HA

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.ANSWEREDVMTERMINATEPDLEVENT"></a>

• Event **com.vmware.vc.HA.AnsweredVmTerminatePDLEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.AUTOSTARTDISABLED"></a>

• Event **com.vmware.vc.HA.AutoStartDisabled**

The automatic Virtual Machine Startup/Shutdown feature has been disabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.CANNOTRESETVMWITHINACCESSIBLEDATASTORE"></a>

• Event **com.vmware.vc.HA.CannotResetVmWithInaccessibleDatastore**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.CLUSTERCONTAINSINCOMPATIBLEHOSTS"></a>

• Event **com.vmware.vc.HA.ClusterContainsIncompatibleHosts**

vSphere HA Cluster contains ESX/ESXi 3.5 hosts and more recent host versions, which isn't fully supported.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.CLUSTERFAILOVERACTIONCOMPLETEDEVENT"></a>

• Event **com.vmware.vc.HA.ClusterFailoverActionCompletedEvent**

HA completed a failover action

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.CLUSTERFAILOVERACTIONINITIATEDEVENT"></a>

• Event **com.vmware.vc.HA.ClusterFailoverActionInitiatedEvent**

HA initiated a failover action

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.DASAGENTRUNNINGEVENT"></a>

• Event **com.vmware.vc.HA.DasAgentRunningEvent**

HA Agent is running

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.DASFAILOVERHOSTFAILEDEVENT"></a>

• Event **com.vmware.vc.HA.DasFailoverHostFailedEvent**

HA failover host has failed

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.DASFAILOVERHOSTISOLATEDEVENT"></a>

• Event **com.vmware.vc.HA.DasFailoverHostIsolatedEvent**

Host has been isolated from cluster

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.DASFAILOVERHOSTPARTITIONEDEVENT"></a>

• Event **com.vmware.vc.HA.DasFailoverHostPartitionedEvent**

Failover Host is in a different network partition than the master

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.DASFAILOVERHOSTUNREACHABLEEVENT"></a>

• Event **com.vmware.vc.HA.DasFailoverHostUnreachableEvent**

The vSphere HA agent on the failover host is not reachable from vCenter Server

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.DASHOSTCOMPLETEDATASTOREFAILUREEVENT"></a>

• Event **com.vmware.vc.HA.DasHostCompleteDatastoreFailureEvent**

Host complete datastore failure

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.DASHOSTCOMPLETENETWORKFAILUREEVENT"></a>

• Event **com.vmware.vc.HA.DasHostCompleteNetworkFailureEvent**

Host complete network failure

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.DASHOSTFAILEDEVENT"></a>

• Event **com.vmware.vc.HA.DasHostFailedEvent**

A possible host failure has been detected by HA

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.DASHOSTISOLATEDEVENT"></a>

• Event **com.vmware.vc.HA.DasHostIsolatedEvent**

Host has been isolated from cluster

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.DASHOSTMONITORINGDISABLEDEVENT"></a>

• Event **com.vmware.vc.HA.DasHostMonitoringDisabledEvent**

No virtual machine failover will occur until Host Monitoring is enabled

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.DASTOTALCLUSTERFAILUREEVENT"></a>

• Event **com.vmware.vc.HA.DasTotalClusterFailureEvent**

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.FAILEDRESTARTAFTERISOLATIONEVENT"></a>

• Event **com.vmware.vc.HA.FailedRestartAfterIsolationEvent**

Failed to restart VM after isolation

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.HEARTBEATDATASTORECHANGED"></a>

• Event **com.vmware.vc.HA.HeartbeatDatastoreChanged**

Datastore heartbeat changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.HEARTBEATDATASTORENOTSUFFICIENT"></a>

• Event **com.vmware.vc.HA.HeartbeatDatastoreNotSufficient**

Number of heartbeat datastores is less than required

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.HOSTAGENTERROREVENT"></a>

• Event **com.vmware.vc.HA.HostAgentErrorEvent**

Host HA Agent has an error

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.HOSTDASAGENTHEALTHYEVENT"></a>

• Event **com.vmware.vc.HA.HostDasAgentHealthyEvent**

HA Agent on host is healthy

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.HOSTDASERROREVENT"></a>

• Event **com.vmware.vc.HA.HostDasErrorEvent**

Host HA has an error

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.HOSTDOESNOTSUPPORTVSAN"></a>

• Event **com.vmware.vc.HA.HostDoesNotSupportVsan**

Since VI API 5.55.. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.HOSTHASNOISOLATIONADDRSDEFINED"></a>

• Event **com.vmware.vc.HA.HostHasNoIsolationAddrsDefined**

Host has no isolation addresses defined as required by vSphere HA

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.HOSTHASNOMOUNTEDDATASTORES"></a>

• Event **com.vmware.vc.HA.HostHasNoMountedDatastores**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.HOSTHASNOSSLTHUMBPRINT"></a>

• Event **com.vmware.vc.HA.HostHasNoSslThumbprint**

vSphere HA cannot be configured because its SSL thumbprint has not been verified

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.HOSTINCOMPATIBLEWITHHA"></a>

• Event **com.vmware.vc.HA.HostIncompatibleWithHA**

The product version of host is incompatible with HA

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.HOSTPARTITIONEDFROMMASTEREVENT"></a>

• Event **com.vmware.vc.HA.HostPartitionedFromMasterEvent**

Host is in a different network partition than the master

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.HOSTSTATECHANGEDEVENT"></a>

• Event **com.vmware.vc.HA.HostStateChangedEvent**

Host HA state has changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.HOSTUNCONFIGUREDWITHPROTECTEDVMS"></a>

• Event **com.vmware.vc.HA.HostUnconfiguredWithProtectedVms**

Host with protected VMs is disconnected

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.HOSTUNCONFIGUREERROR"></a>

• Event **com.vmware.vc.HA.HostUnconfigureError**

Error unconfiguring HA agent on host. To solve this problem, connect the host to a vCenter Server of version 5.0 or later.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.INVALIDMASTER"></a>

• Event **com.vmware.vc.HA.InvalidMaster**

HA Agent on host is an invalid master

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.NOTALLHOSTADDRSPINGABLE"></a>

• Event **com.vmware.vc.HA.NotAllHostAddrsPingable**

Host HA Agent cannot reach some of the management network addresses of other hosts

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.STARTFTSECONDARYFAILEDEVENT"></a>

• Event **com.vmware.vc.HA.StartFTSecondaryFailedEvent**

Host HA agent failed to start Fault Tolerance secondary VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.STARTFTSECONDARYSUCCEEDEDEVENT"></a>

• Event **com.vmware.vc.HA.StartFTSecondarySucceededEvent**

Host HA agent successfully started Fault Tolerance secondary VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.USERHEARTBEATDATASTOREREMOVED"></a>

• Event **com.vmware.vc.HA.UserHeartbeatDatastoreRemoved**

Datastore is removed from inventory

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.VCCANNOTFINDMASTEREVENT"></a>

• Event **com.vmware.vc.HA.VcCannotFindMasterEvent**

vCenter Server is unable to find a master vSphere HA Agent

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.VCCONNECTEDTOMASTEREVENT"></a>

• Event **com.vmware.vc.HA.VcConnectedToMasterEvent**

vCenter Server is connected to the master vSphere HA Agent

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.VCDISCONNECTEDFROMMASTEREVENT"></a>

• Event **com.vmware.vc.HA.VcDisconnectedFromMasterEvent**

vCenter Server is disconnected from the master vSphere HA Agent

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HA.VMISHADISABLEDISOLATIONEVENT"></a>

• Event **com.vmware.vc.HA.VMIsHADisabledIsolationEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.VMISHADISABLEDRESTARTEVENT"></a>

• Event **com.vmware.vc.HA.VMIsHADisabledRestartEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.VMNOTPROTECTEDEVENT"></a>

• Event **com.vmware.vc.HA.VmNotProtectedEvent**

VM failed to become vSphere HA Protected

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.VMPROTECTEDEVENT"></a>

• Event **com.vmware.vc.HA.VmProtectedEvent**

VM is vSphere HA Protected

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.VMRESTARTEDBYHAEVENT"></a>

• Event **com.vmware.vc.ha.VmRestartedByHAEvent**

VM was restarted by HA

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.VMUNPROTECTEDEVENT"></a>

• Event **com.vmware.vc.HA.VmUnprotectedEvent**

VM is not HA Protected

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HA.VMUNPROTECTEDONDISKSPACEFULL"></a>

• Event **com.vmware.vc.HA.VmUnprotectedOnDiskSpaceFull**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HOST.AUTOSTARTRECONFIGUREFAILEDEVENT"></a>

• Event **com.vmware.vc.host.AutoStartReconfigureFailedEvent**

Failed to reconfigure autostart rules for virtual machines

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HOST.CLEAR.VFLASHRESOURCE.INACCESSIBLE"></a>

• Event **com.vmware.vc.host.clear.vFlashResource.inaccessible**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HOST.CLEAR.VFLASHRESOURCE.REACHTHRESHOLD"></a>

• Event **com.vmware.vc.host.clear.vFlashResource.reachthreshold**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HOST.PROBLEM.VFLASHRESOURCE.INACCESSIBLE"></a>

• Event **com.vmware.vc.host.problem.vFlashResource.inaccessible**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HOST.PROBLEM.VFLASHRESOURCE.REACHTHRESHOLD"></a>

• Event **com.vmware.vc.host.problem.vFlashResource.reachthreshold**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HOST.VFLASH.DEFAULTMODULECHANGEDEVENT"></a>

• Event **com.vmware.vc.host.vFlash.defaultModuleChangedEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HOST.VFLASH.MODULESLOADEDEVENT"></a>

• Event **com.vmware.vc.host.vFlash.modulesLoadedEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HOST.VFLASH.SSDCONFIGURATIONFAILEDEVENT"></a>

• Event **com.vmware.vc.host.vFlash.SsdConfigurationFailedEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.HOST.VFLASH.VFLASHRESOURCECAPACITYEXTENDEDEVENT"></a>

• Event **com.vmware.vc.host.vFlash.VFlashResourceCapacityExtendedEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HOST.VFLASH.VFLASHRESOURCECONFIGUREDEVENT"></a>

• Event **com.vmware.vc.host.vFlash.VFlashResourceConfiguredEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.HOST.VFLASH.VFLASHRESOURCEREMOVEDEVENT"></a>

• Event **com.vmware.vc.host.vFlash.VFlashResourceRemovedEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.NPT.VMADAPTERENTEREDPASSTHROUGHEVENT"></a>

• Event **com.vmware.vc.npt.VmAdapterEnteredPassthroughEvent**

Virtual NIC entered passthrough mode

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.NPT.VMADAPTEREXITEDPASSTHROUGHEVENT"></a>

• Event **com.vmware.vc.npt.VmAdapterExitedPassthroughEvent**

Virtual NIC exited passthrough mode

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.OVFCONSUMERS.CLONEOVFCONSUMERSTATEERROREVENT"></a>

• Event **com.vmware.vc.ovfconsumers.CloneOvfConsumerStateErrorEvent**

Failed to clone extension entity state

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.OVFCONSUMERS.GETOVFENVIRONMENTSECTIONSERROREVENT"></a>

• Event **com.vmware.vc.ovfconsumers.GetOvfEnvironmentSectionsErrorEvent**

Failed to retrieve OVF environment sections from extension

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.OVFCONSUMERS.POWERONAFTERCLONEERROREVENT"></a>

• Event **com.vmware.vc.ovfconsumers.PowerOnAfterCloneErrorEvent**

Extension has blocked powering on of cloned VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.OVFCONSUMERS.REGISTERENTITYERROREVENT"></a>

• Event **com.vmware.vc.ovfconsumers.RegisterEntityErrorEvent**

Failed to register entity on extension

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.OVFCONSUMERS.UNREGISTERENTITIESERROREVENT"></a>

• Event **com.vmware.vc.ovfconsumers.UnregisterEntitiesErrorEvent**

Failed to unregister entities on extension

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.OVFCONSUMERS.VALIDATEOSTERROREVENT"></a>

• Event **com.vmware.vc.ovfconsumers.ValidateOstErrorEvent**

Failed to validate OVF descriptor on extension

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.PROFILE.ANSWERFILEEXPORTEDEVENT"></a>

• Event **com.vmware.vc.profile.AnswerFileExportedEvent**

Answer file has been exported

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.PROFILE.ANSWERFILEUPDATEDEVENT"></a>

• Event **com.vmware.vc.profile.AnswerFileUpdatedEvent**

Answer file has been updated

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.RP.RESOURCEPOOLRENAMEDEVENT"></a>

• Event **com.vmware.vc.rp.ResourcePoolRenamedEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SDRS.CANCELEDDATASTOREMAINTENANCEMODEEVENT"></a>

• Event **com.vmware.vc.sdrs.CanceledDatastoreMaintenanceModeEvent**

The datastore maintenance mode operation has been canceled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.CONFIGUREDSTORAGEDRSONPODEVENT"></a>

• Event **com.vmware.vc.sdrs.ConfiguredStorageDrsOnPodEvent**

Storage DRS configured on datastore cluster

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.CONSISTENCYGROUPVIOLATIONEVENT"></a>

• Event **com.vmware.vc.sdrs.ConsistencyGroupViolationEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.DATASTOREENTEREDMAINTENANCEMODEEVENT"></a>

• Event **com.vmware.vc.sdrs.DatastoreEnteredMaintenanceModeEvent**

Datastore has entered maintenance mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.DATASTOREENTERINGMAINTENANCEMODEEVENT"></a>

• Event **com.vmware.vc.sdrs.DatastoreEnteringMaintenanceModeEvent**

Datastore is entering maintenance mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.DATASTOREEXITEDMAINTENANCEMODEEVENT"></a>

• Event **com.vmware.vc.sdrs.DatastoreExitedMaintenanceModeEvent**

Datastore has exited maintenance mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.DATASTOREINMULTIPLEDATACENTERSEVENT"></a>

• Event **com.vmware.vc.sdrs.DatastoreInMultipleDatacentersEvent**

Datastore cluster has one or more datastores shared across multiple datacenters

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SDRS.DATASTOREMAINTENANCEMODEERRORSEVENT"></a>

• Event **com.vmware.vc.sdrs.DatastoreMaintenanceModeErrorsEvent**

Datastore encountered errors while entering maintenance mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.STORAGEDRSDISABLEDEVENT"></a>

• Event **com.vmware.vc.sdrs.StorageDrsDisabledEvent**

Storage DRS disabled on datastore cluster

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.STORAGEDRSENABLEDEVENT"></a>

• Event **com.vmware.vc.sdrs.StorageDrsEnabledEvent**

Storage DRS enabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SDRS.STORAGEDRSINVOCATIONFAILEDEVENT"></a>

• Event **com.vmware.vc.sdrs.StorageDrsInvocationFailedEvent**

Storage DRS invocation failed on datastore cluster

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.STORAGEDRSNEWRECOMMENDATIONPENDINGEVENT"></a>

• Event **com.vmware.vc.sdrs.StorageDrsNewRecommendationPendingEvent**

A new storage DRS recommendation has been generated on datastore cluster

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.STORAGEDRSNOTSUPPORTEDHOSTCONNECTEDTOPODEVENT"></a>

• Event **com.vmware.vc.sdrs.StorageDrsNotSupportedHostConnectedToPodEvent**

Datastore cluster is connected to one or more hosts that do not support storage DRS

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SDRS.STORAGEDRSRECOMMENDATIONAPPLIED"></a>

• Event **com.vmware.vc.sdrs.StorageDrsRecommendationApplied**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.STORAGEDRSSTORAGEMIGRATIONEVENT"></a>

• Event **com.vmware.vc.sdrs.StorageDrsStorageMigrationEvent**

VM disks migrated by storage DRS

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.STORAGEDRSSTORAGEPLACEMENTEVENT"></a>

• Event **com.vmware.vc.sdrs.StorageDrsStoragePlacementEvent**

Storage DRS placed disks of VM on specified datastore

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SDRS.STORAGEPODCREATEDEVENT"></a>

• Event **com.vmware.vc.sdrs.StoragePodCreatedEvent**

Datastore cluster created

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SDRS.STORAGEPODDESTROYEDEVENT"></a>

• Event **com.vmware.vc.sdrs.StoragePodDestroyedEvent**

Datastore cluster removed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SIOC.NOTSUPPORTEDHOSTCONNECTEDTODATASTOREEVENT"></a>

• Event **com.vmware.vc.sioc.NotSupportedHostConnectedToDatastoreEvent**

SIOC has detected that a host is running an older version of ESX that does not support SIOC

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SMS.DATASTORE.COMPLIANCESTATUSCOMPLIANTEVENT"></a>

• Event **com.vmware.vc.sms.datastore.ComplianceStatusCompliantEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SMS.DATASTORE.COMPLIANCESTATUSNONCOMPLIANTEVENT"></a>

• Event **com.vmware.vc.sms.datastore.ComplianceStatusNonCompliantEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SMS.DATASTORE.COMPLIANCESTATUSUNKNOWNEVENT"></a>

• Event **com.vmware.vc.sms.datastore.ComplianceStatusUnknownEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SMS.LUNCAPABILITYINITEVENT"></a>

• Event **com.vmware.vc.sms.LunCapabilityInitEvent**

Storage provider system default capability event

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SMS.LUNCAPABILITYMETEVENT"></a>

• Event **com.vmware.vc.sms.LunCapabilityMetEvent**

Storage provider system capability requirements met

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SMS.LUNCAPABILITYNOTMETEVENT"></a>

• Event **com.vmware.vc.sms.LunCapabilityNotMetEvent**

Storage provider system capability requirements not met

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SMS.PROVIDER.HEALTH.EVENT"></a>

• Event **com.vmware.vc.sms.provider.health.event**

SMS Provider health event

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SMS.PROVIDER.SYSTEM.EVENT"></a>

• Event **com.vmware.vc.sms.provider.system.event**

SMS Provider system event

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SMS.THINPROVISIONEDLUNTHRESHOLDCLEAREDEVENT"></a>

• Event **com.vmware.vc.sms.ThinProvisionedLunThresholdClearedEvent**

Storage provider thin provisioning capacity threshold reached

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SMS.THINPROVISIONEDLUNTHRESHOLDCROSSEDEVENT"></a>

• Event **com.vmware.vc.sms.ThinProvisionedLunThresholdCrossedEvent**

Storage provider thin provisioning capacity threshold crossed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SMS.THINPROVISIONEDLUNTHRESHOLDINITEVENT"></a>

• Event **com.vmware.vc.sms.ThinProvisionedLunThresholdInitEvent**

Storage provider thin provisioning default capacity event

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.SMS.VM.COMPLIANCESTATUSCOMPLIANTEVENT"></a>

• Event **com.vmware.vc.sms.vm.ComplianceStatusCompliantEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SMS.VM.COMPLIANCESTATUSNONCOMPLIANTEVENT"></a>

• Event **com.vmware.vc.sms.vm.ComplianceStatusNonCompliantEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SMS.VM.COMPLIANCESTATUSUNKNOWNEVENT"></a>

• Event **com.vmware.vc.sms.vm.ComplianceStatusUnknownEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.SPBM.PROFILEASSOCIATIONFAILEDEVENT"></a>

• Event **com.vmware.vc.spbm.ProfileAssociationFailedEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.STATS.HOSTQUICKSTATESNOTUPTODATEEVENT"></a>

• Event **com.vmware.vc.stats.HostQuickStatesNotUpToDateEvent**

Host quick stats is not up-to-date

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VCHEALTHSTATECHANGEDEVENT"></a>

• Event **com.vmware.vc.VCHealthStateChangedEvent**

vCenter Service Overall Health Changed

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VCP.FTDISABLEDVMTREATASNONFTEVENT"></a>

• Event **com.vmware.vc.vcp.FtDisabledVmTreatAsNonFtEvent**

HA VM Component Protection protects virtual machine as non-FT virtual machine because the FT state is disabled

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VCP.FTFAILOVEREVENT"></a>

• Event **com.vmware.vc.vcp.FtFailoverEvent**

FT Primary VM is going to fail over to Secondary VM due to component failure

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VCP.FTFAILOVERFAILEDEVENT"></a>

• Event **com.vmware.vc.vcp.FtFailoverFailedEvent**

FT virtual machine failed to failover to secondary

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VCP.FTSECONDARYRESTARTEVENT"></a>

• Event **com.vmware.vc.vcp.FtSecondaryRestartEvent**

HA VM Component Protection is restarting FT secondary virtual machine

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VCP.FTSECONDARYRESTARTFAILEDEVENT"></a>

• Event **com.vmware.vc.vcp.FtSecondaryRestartFailedEvent**

FT Secondary VM failed to restart

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VCP.NEEDSECONDARYFTVMTREATASNONFTEVENT"></a>

• Event **com.vmware.vc.vcp.NeedSecondaryFtVmTreatAsNonFtEvent**

HA VM Component Protection protects virtual machine as non-FT virtual machine because it has been in the needSecondary state too long

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VCP.TESTENDEVENT"></a>

• Event **com.vmware.vc.vcp.TestEndEvent**

VM Component Protection test ends

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VCP.TESTSTARTEVENT"></a>

• Event **com.vmware.vc.vcp.TestStartEvent**

VM Component Protection test starts

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VCP.VCPNOACTIONEVENT"></a>

• Event **com.vmware.vc.vcp.VcpNoActionEvent**

HA VM Component Protection did not take action on VM

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VCP.VMDATASTOREFAILEDEVENT"></a>

• Event **com.vmware.vc.vcp.VmDatastoreFailedEvent**

Virtual machine lost datastore access

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VCP.VMNETWORKFAILEDEVENT"></a>

• Event **com.vmware.vc.vcp.VmNetworkFailedEvent**

Virtual machine lost VM network accessibility

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VCP.VMPOWEROFFHANGEVENT"></a>

• Event **com.vmware.vc.vcp.VmPowerOffHangEvent**

VM power off hang

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VCP.VMRESTARTEVENT"></a>

• Event **com.vmware.vc.vcp.VmRestartEvent**

HA VM Component Protection is restarting virtual machine due to component failure

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VCP.VMRESTARTFAILEDEVENT"></a>

• Event **com.vmware.vc.vcp.VmRestartFailedEvent**

Virtual machine affected by component failure failed to restart

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VCP.VMWAITFORCANDIDATEHOSTEVENT"></a>

• Event **com.vmware.vc.vcp.VmWaitForCandidateHostEvent**

No candidate host to restart

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VM.VMREGISTERFAILEDEVENT"></a>

• Event **com.vmware.vc.vm.VmRegisterFailedEvent**

VM registration failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VM.VMSTATEFAILEDTOREVERTTOSNAPSHOT"></a>

• Event **com.vmware.vc.vm.VmStateFailedToRevertToSnapshot**

Failed to revert the execution state of the virtual machine to snapshot

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VM.VMSTATEREVERTEDTOSNAPSHOT"></a>

• Event **com.vmware.vc.vm.VmStateRevertedToSnapshot**

The execution state of the virtual machine has been reverted to the state of snapshot

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VMAM.APPMONITORINGNOTSUPPORTED"></a>

• Event **com.vmware.vc.vmam.AppMonitoringNotSupported**

Application monitoring is not supported

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VMAM.VMAPPHEALTHMONITORINGSTATECHANGEDEVENT"></a>

• Event **com.vmware.vc.vmam.VmAppHealthMonitoringStateChangedEvent**

Application heartbeat status changed

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VMAM.VMAPPHEALTHSTATECHANGEDEVENT"></a>

• Event **com.vmware.vc.vmam.VmAppHealthStateChangedEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VMAM.VMDASAPPHEARTBEATFAILEDEVENT"></a>

• Event **com.vmware.vc.vmam.VmDasAppHeartbeatFailedEvent**

Application heartbeat failed

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VMCLONEFAILEDINVALIDDESTINATIONEVENT"></a>

• Event **com.vmware.vc.VmCloneFailedInvalidDestinationEvent**

Cannon clone a VM to invalid or non-existent destination

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VMCLONETORESOURCEPOOLFAILEDEVENT"></a>

• Event **com.vmware.vc.VmCloneToResourcePoolFailedEvent**

Cannot clone a VM to resource pool

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VMDISKCONSOLIDATEDEVENT"></a>

• Event **com.vmware.vc.VmDiskConsolidatedEvent**

VM disks successfully consolidated

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VMDISKCONSOLIDATIONNEEDED"></a>

• Event **com.vmware.vc.VmDiskConsolidationNeeded**

VM disks consolidation is needed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VMDISKCONSOLIDATIONNOLONGERNEEDED"></a>

• Event **com.vmware.vc.VmDiskConsolidationNoLongerNeeded**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VMDISKFAILEDTOCONSOLIDATEEVENT"></a>

• Event **com.vmware.vc.VmDiskFailedToConsolidateEvent**

VM disks consolidation failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VSAN.DATASTORENOCAPACITYEVENT"></a>

• Event **com.vmware.vc.vsan.DatastoreNoCapacityEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VSAN.HOSTCOMMUNICATIONERROREVENT"></a>

• Event **com.vmware.vc.vsan.HostCommunicationErrorEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VC.VSAN.HOSTNOTINCLUSTEREVENT"></a>

• Event **com.vmware.vc.vsan.HostNotInClusterEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VSAN.HOSTNOTINVSANCLUSTEREVENT"></a>

• Event **com.vmware.vc.vsan.HostNotInVsanClusterEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VSAN.HOSTVENDORPROVIDERDEREGISTRATIONFAILEDEVENT"></a>

• Event **com.vmware.vc.vsan.HostVendorProviderDeregistrationFailedEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VSAN.HOSTVENDORPROVIDERDEREGISTRATIONSUCCESSEVENT"></a>

• Event **com.vmware.vc.vsan.HostVendorProviderDeregistrationSuccessEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VSAN.HOSTVENDORPROVIDERREGISTRATIONFAILEDEVENT"></a>

• Event **com.vmware.vc.vsan.HostVendorProviderRegistrationFailedEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VSAN.HOSTVENDORPROVIDERREGISTRATIONSUCCESSEVENT"></a>

• Event **com.vmware.vc.vsan.HostVendorProviderRegistrationSuccessEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VSAN.NETWORKMISCONFIGUREDEVENT"></a>

• Event **com.vmware.vc.vsan.NetworkMisConfiguredEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VC.VSAN.ROGUEHOSTFOUNDEVENT"></a>

• Event **com.vmware.vc.vsan.RogueHostFoundEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENCY.CREATE"></a>

• Event **com.vmware.vim.eam.agency.create**

EAM Agency created

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENCY.DESTROYED"></a>

• Event **com.vmware.vim.eam.agency.destroyed**

EAM Agency destroyed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENCY.GOALSTATE"></a>

• Event **com.vmware.vim.eam.agency.goalstate**

EAM Agency goal state changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENCY.STATUSCHANGED"></a>

• Event **com.vmware.vim.eam.agency.statusChanged**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENCY.UPDATED"></a>

• Event **com.vmware.vim.eam.agency.updated**

EAM Agency configuration updated

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.CREATED"></a>

• Event **com.vmware.vim.eam.agent.created**

EAM Agent added to host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.DESTROYED"></a>

• Event **com.vmware.vim.eam.agent.destroyed**

EAM Agent removed from host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.DESTROYEDNOHOST"></a>

• Event **com.vmware.vim.eam.agent.destroyedNoHost**

EAM Agent removed from host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.MARKAGENTVMASAVAILABLEAFTERPOWERON"></a>

• Event **com.vmware.vim.eam.agent.markAgentVmAsAvailableAfterPowerOn**

Agent VM has been powered on.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.MARKAGENTVMASAVAILABLEAFTERPROVISIONING"></a>

• Event **com.vmware.vim.eam.agent.markAgentVmAsAvailableAfterProvisioning**

Agent VM has been powered on.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.STATUSCHANGED"></a>

• Event **com.vmware.vim.eam.agent.statusChanged**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.TASK.DELETEVM"></a>

• Event **com.vmware.vim.eam.agent.task.deleteVm**

Agent VM is deleted

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.TASK.DEPLOYVM"></a>

• Event **com.vmware.vim.eam.agent.task.deployVm**

Agent VM is provisioned

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.TASK.POWEROFFVM"></a>

• Event **com.vmware.vim.eam.agent.task.powerOffVm**

Agent VM powered off

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.TASK.POWERONVM"></a>

• Event **com.vmware.vim.eam.agent.task.powerOnVm**

Agent VM powered on

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.TASK.VIBINSTALLED"></a>

• Event **com.vmware.vim.eam.agent.task.vibInstalled**

VIB installed on host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.AGENT.TASK.VIBUNINSTALLED"></a>

• Event **com.vmware.vim.eam.agent.task.vibUninstalled**

VIB uninstalled from host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.CANNOTACCESSAGENTOVF"></a>

• Event **com.vmware.vim.eam.issue.cannotAccessAgentOVF**

Unable to access agent OVF package

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.CANNOTACCESSAGENTVIB"></a>

• Event **com.vmware.vim.eam.issue.cannotAccessAgentVib**

Unable to access agent VIB module

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.HOSTINMAINTENANCEMODE"></a>

• Event **com.vmware.vim.eam.issue.hostInMaintenanceMode**

Agent cannot complete an operation since the host is in maintenance mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.HOSTINSTANDBYMODE"></a>

• Event **com.vmware.vim.eam.issue.hostInStandbyMode**

Agent cannot complete an operation since the host is in standby mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.HOSTPOWEREDOFF"></a>

• Event **com.vmware.vim.eam.issue.hostPoweredOff**

Agent cannot complete an operation since the host is powered off

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.INCOMPATIBLEHOSTVERSION"></a>

• Event **com.vmware.vim.eam.issue.incompatibleHostVersion**

Agent is not deployed due to incompatible host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.INSUFFICIENTIPADDRESSES"></a>

• Event **com.vmware.vim.eam.issue.insufficientIpAddresses**

Insufficient IP addresses in IP pool in agent VM network

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.INSUFFICIENTRESOURCES"></a>

• Event **com.vmware.vim.eam.issue.insufficientResources**

Agent cannot be provisioned due to insufficient resources on host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.INSUFFICIENTSPACE"></a>

• Event **com.vmware.vim.eam.issue.insufficientSpace**

Agent on cannot be provisioned due to insufficient space on datastore

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.MISSINGAGENTIPPOOL"></a>

• Event **com.vmware.vim.eam.issue.missingAgentIpPool**

No IP pool in agent VM network

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.MISSINGDVFILTERSWITCH"></a>

• Event **com.vmware.vim.eam.issue.missingDvFilterSwitch**

dvFilter switch is not configured

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.NOAGENTVMDATASTORE"></a>

• Event **com.vmware.vim.eam.issue.noAgentVmDatastore**

No agent datastore configuration

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.NOAGENTVMNETWORK"></a>

• Event **com.vmware.vim.eam.issue.noAgentVmNetwork**

No agent network configuration

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.NOCUSTOMAGENTVMDATASTORE"></a>

• Event **com.vmware.vim.eam.issue.noCustomAgentVmDatastore**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.NOCUSTOMAGENTVMNETWORK"></a>

• Event **com.vmware.vim.eam.issue.noCustomAgentVmNetwork**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.ORPHANDEDDVFILTERSWITCH"></a>

• Event **com.vmware.vim.eam.issue.orphandedDvFilterSwitch**

Unused dvFilter switch

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.ORPHANEDAGENCY"></a>

• Event **com.vmware.vim.eam.issue.orphanedAgency**

Orphaned agency found

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.OVFINVALIDFORMAT"></a>

• Event **com.vmware.vim.eam.issue.ovfInvalidFormat**

OVF used to provision agent has invalid format

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.OVFINVALIDPROPERTY"></a>

• Event **com.vmware.vim.eam.issue.ovfInvalidProperty**

OVF environment has one or more invalid properties

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.RESOLVED"></a>

• Event **com.vmware.vim.eam.issue.resolved**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.UNKNOWNAGENTVM"></a>

• Event **com.vmware.vim.eam.issue.unknownAgentVm**

Unknown agent VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VIBCANNOTPUTHOSTINMAINTENANCEMODE"></a>

• Event **com.vmware.vim.eam.issue.vibCannotPutHostInMaintenanceMode**

Cannot put host into maintenance mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VIBINVALIDFORMAT"></a>

• Event **com.vmware.vim.eam.issue.vibInvalidFormat**

Invalid format for VIB module

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VIBNOTINSTALLED"></a>

• Event **com.vmware.vim.eam.issue.vibNotInstalled**

VIB module for agent is not installed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VIBREQUIRESHOSTINMAINTENANCEMODE"></a>

• Event **com.vmware.vim.eam.issue.vibRequiresHostInMaintenanceMode**

Host must be put into maintenance mode to complete agent VIB installation

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VIBREQUIRESHOSTREBOOT"></a>

• Event **com.vmware.vim.eam.issue.vibRequiresHostReboot**

Host must be rebooted to complete agent VIB installation

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VIBREQUIRESMANUALINSTALLATION"></a>

• Event **com.vmware.vim.eam.issue.vibRequiresManualInstallation**

VIB requires manual installation

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VIBREQUIRESMANUALUNINSTALLATION"></a>

• Event **com.vmware.vim.eam.issue.vibRequiresManualUninstallation**

VIB requires manual uninstallation

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VMCORRUPTED"></a>

• Event **com.vmware.vim.eam.issue.vmCorrupted**

Agent VM is corrupted

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VMDEPLOYED"></a>

• Event **com.vmware.vim.eam.issue.vmDeployed**

Agent VM is provisioned on host when it should be removed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VMMARKEDASTEMPLATE"></a>

• Event **com.vmware.vim.eam.issue.vmMarkedAsTemplate**

Agent VM is marked as template

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VMNOTDEPLOYED"></a>

• Event **com.vmware.vim.eam.issue.vmNotDeployed**

Agent VM is missing on host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VMORPHANED"></a>

• Event **com.vmware.vim.eam.issue.vmOrphaned**

Orphaned agent VM detected

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VMPOWEREDOFF"></a>

• Event **com.vmware.vim.eam.issue.vmPoweredOff**

Agent VM is expected to be powered on

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VMPOWEREDON"></a>

• Event **com.vmware.vim.eam.issue.vmPoweredOn**

Agent VM is expected to be powered off

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VMSUSPENDED"></a>

• Event **com.vmware.vim.eam.issue.vmSuspended**

Agent VM is expected to be powered on but is suspended

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VMWRONGFOLDER"></a>

• Event **com.vmware.vim.eam.issue.vmWrongFolder**

Agent VM is in the wrong VM folder

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.ISSUE.VMWRONGRESOURCEPOOL"></a>

• Event **com.vmware.vim.eam.issue.vmWrongResourcePool**

Agent VM is in wrong resource pool

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.LOGIN.INVALID"></a>

• Event **com.vmware.vim.eam.login.invalid**

Failed login to vSphere ESX Agent Manager

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VIM.EAM.LOGIN.SUCCEEDED"></a>

• Event **com.vmware.vim.eam.login.succeeded**

User logged into vSphere ESX Agent Manager

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.LOGOUT"></a>

• Event **com.vmware.vim.eam.logout**

User logged out of vSphere ESX Agent Manager by logging out of the vCenter server

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.TASK.SCANFORUNKNOWNAGENTVMSCOMPLETED"></a>

• Event **com.vmware.vim.eam.task.scanForUnknownAgentVmsCompleted**

Scan for unknown agent VMs completed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VIM.EAM.TASK.SCANFORUNKNOWNAGENTVMSINITIATED"></a>

• Event **com.vmware.vim.eam.task.scanForUnknownAgentVmsInitiated**

Scan for unknown agent VMs initiated

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="COM.VMWARE.VIM.EAM.TASK.SETUPDVFILTER"></a>

• Event **com.vmware.vim.eam.task.setupDvFilter**

DvFilter switch is setup on host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.TASK.TEARDOWNDVFILTER"></a>

• Event **com.vmware.vim.eam.task.tearDownDvFilter**

DvFilter switch is teared down on host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.UNAUTHORIZED.ACCESS"></a>

• Event **com.vmware.vim.eam.unauthorized.access**

Unauthorized access in vSphere ESX Agent Manager

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.EAM.VUM.FAILEDTOUPLOADVIB"></a>

• Event **com.vmware.vim.eam.vum.failedtouploadvib**

Failed to upload VIB to VMware Update Manager

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.BIND.VAPP"></a>

• Event **com.vmware.vim.vsm.dependency.bind.vApp**

VSM Dependency bind - vApp

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.BIND.VM"></a>

• Event **com.vmware.vim.vsm.dependency.bind.vm**

VSM Dependency bind - VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.CREATE.VAPP"></a>

• Event **com.vmware.vim.vsm.dependency.create.vApp**

VSM Dependency create - vApp

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.CREATE.VM"></a>

• Event **com.vmware.vim.vsm.dependency.create.vm**

VSM Dependency create - VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.DESTROY.VAPP"></a>

• Event **com.vmware.vim.vsm.dependency.destroy.vApp**

VSM Dependency destroy - vApp

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.DESTROY.VM"></a>

• Event **com.vmware.vim.vsm.dependency.destroy.vm**

VSM Dependency destroy - VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.RECONFIGURE.VAPP"></a>

• Event **com.vmware.vim.vsm.dependency.reconfigure.vApp**

VSM Dependency reconfigure - vApp

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.RECONFIGURE.VM"></a>

• Event **com.vmware.vim.vsm.dependency.reconfigure.vm**

VSM Dependency reconfigure - VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.UNBIND.VAPP"></a>

• Event **com.vmware.vim.vsm.dependency.unbind.vApp**

VSM Dependency unbind - vApp

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.UNBIND.VM"></a>

• Event **com.vmware.vim.vsm.dependency.unbind.vm**

VSM Dependency unbind - VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.UPDATE.VAPP"></a>

• Event **com.vmware.vim.vsm.dependency.update.vApp**

VSM Dependency update - vApp

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.DEPENDENCY.UPDATE.VM"></a>

• Event **com.vmware.vim.vsm.dependency.update.vm**

VSM Dependency update - vApp

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.PROVIDER.REGISTER"></a>

• Event **com.vmware.vim.vsm.provider.register**

VSM Provider register

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.PROVIDER.UNREGISTER"></a>

• Event **com.vmware.vim.vsm.provider.unregister**

VSM Provider unregister

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="COM.VMWARE.VIM.VSM.PROVIDER.UPDATE"></a>

• Event **com.vmware.vim.vsm.provider.update**

VSM Provider update

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="CUSTOMFIELDDEFADDEDEVENT"></a>

• Event **CustomFieldDefAddedEvent**

This event records the addition of a custom field definition.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomFieldDefAddedEvent.html)

<a id="CUSTOMFIELDDEFEVENT"></a>

• Event **CustomFieldDefEvent**

This event records a custom field definition event.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomFieldDefEvent.html)

<a id="CUSTOMFIELDDEFREMOVEDEVENT"></a>

• Event **CustomFieldDefRemovedEvent**

This event records the removal of a custom field definition.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomFieldDefRemovedEvent.html)

<a id="CUSTOMFIELDDEFRENAMEDEVENT"></a>

• Event **CustomFieldDefRenamedEvent**

This event records the renaming of a custom field definition.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomFieldDefRenamedEvent.html)

<a id="CUSTOMFIELDVALUECHANGEDEVENT"></a>

• Event **CustomFieldValueChangedEvent**

This event records a change to a custom field value for a particular entity.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomFieldValueChangedEvent.html)

<a id="CUSTOMIZATIONFAILED"></a>

• Event **CustomizationFailed**

The customization sequence completed unsuccessfully in the guest.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomizationFailed.html)

<a id="CUSTOMIZATIONLINUXIDENTITYFAILED"></a>

• Event **CustomizationLinuxIdentityFailed**

Failed to set Linux identity. see the log file specified in the event message for more information.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomizationLinuxIdentityFailed.html)

<a id="CUSTOMIZATIONNETWORKSETUPFAILED"></a>

• Event **CustomizationNetworkSetupFailed**

Network setup failed in the guest during customization. see the log file specified in the event message for more information.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomizationNetworkSetupFailed.html)

<a id="CUSTOMIZATIONSTARTEDEVENT"></a>

• Event **CustomizationStartedEvent**

The customization sequence has started in the VM guest.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomizationStartedEvent.html)

<a id="CUSTOMIZATIONSUCCEEDED"></a>

• Event **CustomizationSucceeded**

The customization sequence completed successfully in the guest.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomizationSucceeded.html)

<a id="CUSTOMIZATIONSYSPREPFAILED"></a>

• Event **CustomizationSysprepFailed**

Sysprep failed to run in the guest during customization. This will most like have been caused by the fact that the wrong sysprep was used for the guest, so we include the version information in the event. see the log file specified in the event message for more information.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomizationSysprepFailed.html)

<a id="CUSTOMIZATIONUNKNOWNFAILURE"></a>

• Event **CustomizationUnknownFailure**

The customization sequence failed unexpectedly in the guest. see the log file specified in the event message for more information.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.CustomizationUnknownFailure.html)

<a id="DASADMISSIONCONTROLDISABLEDEVENT"></a>

• Event **DasAdmissionControlDisabledEvent**

This event records when admission control checks have been disabled in a HA cluster.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DasAdmissionControlDisabledEvent.html)

<a id="DASADMISSIONCONTROLENABLEDEVENT"></a>

• Event **DasAdmissionControlEnabledEvent**

This event records when admission control checks have been enabled in a HA cluster.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DasAdmissionControlEnabledEvent.html)

<a id="DASAGENTFOUNDEVENT"></a>

• Event **DasAgentFoundEvent**

This event records that vCenter has re-established contact with a primary host in this HA cluster.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DasAgentFoundEvent.html)

<a id="DASAGENTUNAVAILABLEEVENT"></a>

• Event **DasAgentUnavailableEvent**

This event records that vCenter cannot contact any primary host in this HA cluster. HA designates some hosts as primary hosts in the HA cluster. When adding a new host to an existing cluster, HA needs to contact one of the primary hosts to finish the configuration. vCenter has lost contact with all primary nodes in the connected state. Attempts to configure HA on a host in this cluster will fail until a DasAgentFoundEvent is logged or unless this is the first node to be configured. For example, if all the other hosts are disconnected first.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DasAgentUnavailableEvent.html)

<a id="DASCLUSTERISOLATEDEVENT"></a>

• Event **DasClusterIsolatedEvent**

This event records that all hosts have been isolated from the network in a HA cluster.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DasClusterIsolatedEvent.html)

<a id="DASDISABLEDEVENT"></a>

• Event **DasDisabledEvent**

This event records when a cluster has been disabled for HA.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DasDisabledEvent.html)

<a id="DASENABLEDEVENT"></a>

• Event **DasEnabledEvent**

This event records when a cluster has been enabled for HA.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DasEnabledEvent.html)

<a id="DASHOSTFAILEDEVENT"></a>

• Event **DasHostFailedEvent**

This event records when a host failure has been detected by HA.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DasHostFailedEvent.html)

<a id="DASHOSTISOLATEDEVENT"></a>

• Event **DasHostIsolatedEvent**

This event records that a host has been isolated from the network in a HA cluster. Since an isolated host cannot be distinguished from a failed host except by the isolated host itself, this event is logged when the isolated host regains network connectivity.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DasHostIsolatedEvent.html)

<a id="DATACENTERCREATEDEVENT"></a>

• Event **DatacenterCreatedEvent**

This event records when a datacenter object has been created.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatacenterCreatedEvent.html)

<a id="DATACENTERRENAMEDEVENT"></a>

• Event **DatacenterRenamedEvent**

This event is generated whenever a datacenter is renamed.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatacenterRenamedEvent.html)

<a id="DATASTORECAPACITYINCREASEDEVENT"></a>

• Event **DatastoreCapacityIncreasedEvent**

This event records when increase in a datastore capacity is observed. It may happen due to different reasons, like extending or expanding a datastore.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastoreCapacityIncreasedEvent.html)

<a id="DATASTOREDESTROYEDEVENT"></a>

• Event **DatastoreDestroyedEvent**

This event records when a datastore is removed from vCenter.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastoreDestroyedEvent.html)

<a id="DATASTOREDISCOVEREDEVENT"></a>

• Event **DatastoreDiscoveredEvent**

This event records when a host is added to vCenter and datastores are discovered.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastoreDiscoveredEvent.html)

<a id="DATASTOREDUPLICATEDEVENT"></a>

• Event **DatastoreDuplicatedEvent**

This event records when a duplicate datastore name is found. This event is used in vCenter 1.x and is included for backward compatibility.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastoreDuplicatedEvent.html)

<a id="DATASTOREFILECOPIEDEVENT"></a>

• Event **DatastoreFileCopiedEvent**

This event records copy of a file or directory.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastoreFileCopiedEvent.html)

<a id="DATASTOREFILEDELETEDEVENT"></a>

• Event **DatastoreFileDeletedEvent**

This event records deletion of a file or directory.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastoreFileDeletedEvent.html)

<a id="DATASTOREFILEMOVEDEVENT"></a>

• Event **DatastoreFileMovedEvent**

This event records move of a file or directory.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastoreFileMovedEvent.html)

<a id="DATASTOREIORMRECONFIGUREDEVENT"></a>

• Event **DatastoreIORMReconfiguredEvent**

This event records that the configuration of storage I/O resource management for a datastore has changed

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.DatastoreIORMReconfiguredEvent.html)

<a id="DATASTOREPRINCIPALCONFIGURED"></a>

• Event **DatastorePrincipalConfigured**

This event records that a datastore principal was configured on a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastorePrincipalConfigured.html)

<a id="DATASTOREREMOVEDONHOSTEVENT"></a>

• Event **DatastoreRemovedOnHostEvent**

This event records when a datastore is removed from a host but not from vCenter.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastoreRemovedOnHostEvent.html)

<a id="DATASTORERENAMEDEVENT"></a>

• Event **DatastoreRenamedEvent**

This event records the renaming of a datastore.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastoreRenamedEvent.html)

<a id="DATASTORERENAMEDONHOSTEVENT"></a>

• Event **DatastoreRenamedOnHostEvent**

This event records when a datastore is added to vCenter and is renamed by vCenter because this datastore already exists in vCenter with a different name, or because the name conflicts with another datastore in vCenter.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DatastoreRenamedOnHostEvent.html)

<a id="DRSDISABLEDEVENT"></a>

• Event **DrsDisabledEvent**

This event records when DRS is disabled on a cluster.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsDisabledEvent.html)

<a id="DRSENABLEDEVENT"></a>

• Event **DrsEnabledEvent**

This event records when DRS is enabled on a cluster.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsEnabledEvent.html)

<a id="DRSENTEREDSTANDBYMODEEVENT"></a>

• Event **DrsEnteredStandbyModeEvent**

This event records that the host has completely put into standby mode by Distributed Power Management. A host in this mode has no running virtual machines and no provisioning operations are occurring.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsEnteredStandbyModeEvent.html)

<a id="DRSENTERINGSTANDBYMODEEVENT"></a>

• Event **DrsEnteringStandbyModeEvent**

This event records that a host has begun the process of entering standby mode initiated by Distributed Power Management.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsEnteringStandbyModeEvent.html)

<a id="DRSEXITEDSTANDBYMODEEVENT"></a>

• Event **DrsExitedStandbyModeEvent**

This event records that Distributed Power Management has brought this host out of standby mode.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsExitedStandbyModeEvent.html)

<a id="DRSEXITINGSTANDBYMODEEVENT"></a>

• Event **DrsExitingStandbyModeEvent**

This event records that a host has begun the process of exiting standby mode initiated by Distributed Power Management.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsExitingStandbyModeEvent.html)

<a id="DRSEXITSTANDBYMODEFAILEDEVENT"></a>

• Event **DrsExitStandbyModeFailedEvent**

This event records that Distributed Power Management tried to bring a host out from standby mode, but the host failed to exit standby mode.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsExitStandbyModeFailedEvent.html)

<a id="DRSINVOCATIONFAILEDEVENT"></a>

• Event **DrsInvocationFailedEvent**

This event records DRS invocation failure.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsInvocationFailedEvent.html)

<a id="DRSRECOVEREDFROMFAILUREEVENT"></a>

• Event **DrsRecoveredFromFailureEvent**

This event records that DRS has recovered from failure. It is triggered by a successful DRS invocation after repeated failure.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsRecoveredFromFailureEvent.html)

<a id="DRSRESOURCECONFIGUREFAILEDEVENT"></a>

• Event **DrsResourceConfigureFailedEvent**

This event records when resource configuration specification synchronization fails on a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsResourceConfigureFailedEvent.html)

<a id="DRSRESOURCECONFIGURESYNCEDEVENT"></a>

• Event **DrsResourceConfigureSyncedEvent**

This event records when resource configuration specification returns to synchronized from previous failure.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsResourceConfigureSyncedEvent.html)

<a id="DRSRULECOMPLIANCEEVENT"></a>

• Event **DrsRuleComplianceEvent**

This event records when a virtual machine comes into compliance with DRS rules

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.DrsRuleComplianceEvent.html)

<a id="DRSRULEVIOLATIONEVENT"></a>

• Event **DrsRuleViolationEvent**

This event records when a virtual machine violates a DRS rule

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.DrsRuleViolationEvent.html)

<a id="DRSVMMIGRATEDEVENT"></a>

• Event **DrsVmMigratedEvent**

This event records a virtual machine migration that was recommended by DRS.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsVmMigratedEvent.html)

<a id="DRSVMPOWEREDONEVENT"></a>

• Event **DrsVmPoweredOnEvent**

This event records when a virtual machine is powered on by DRS.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DrsVmPoweredOnEvent.html)

<a id="DUPLICATEIPDETECTEDEVENT"></a>

• Event **DuplicateIpDetectedEvent**

This event records that a duplicate IP address has been observed in conflict with the vMotion or IP storage interface configured on the host.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DuplicateIpDetectedEvent.html)

<a id="DVPGIMPORTEVENT"></a>

• Event **DvpgImportEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvpgImportEvent.html)

<a id="DVPGRESTOREEVENT"></a>

• Event **DvpgRestoreEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvpgRestoreEvent.html)

<a id="DVPORTGROUPCREATEDEVENT"></a>

• Event **DVPortgroupCreatedEvent**

Distributed virtual port group was created

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DVPortgroupCreatedEvent.html)

<a id="DVPORTGROUPDESTROYEDEVENT"></a>

• Event **DVPortgroupDestroyedEvent**

Distributed virtual port group was destroyed

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DVPortgroupDestroyedEvent.html)

<a id="DVPORTGROUPRECONFIGUREDEVENT"></a>

• Event **DVPortgroupReconfiguredEvent**

Distributed virtual port group was reconfigured

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DVPortgroupReconfiguredEvent.html)

<a id="DVPORTGROUPRENAMEDEVENT"></a>

• Event **DVPortgroupRenamedEvent**

Distributed virtual port group was renamed

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DVPortgroupRenamedEvent.html)

<a id="DVSCREATEDEVENT"></a>

• Event **DvsCreatedEvent**

A distributed virtual switch was created

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsCreatedEvent.html)

<a id="DVSDESTROYEDEVENT"></a>

• Event **DvsDestroyedEvent**

A distributed virtual switch was destroyed

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsDestroyedEvent.html)

<a id="DVSEVENT"></a>

• Event **DvsEvent**

These are dvs-related events.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsEvent.html)

<a id="DVSHEALTHSTATUSCHANGEEVENT"></a>

• Event **DvsHealthStatusChangeEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsHealthStatusChangeEvent.html)

<a id="DVSHOSTBACKINSYNCEVENT"></a>

• Event **DvsHostBackInSyncEvent**

The DVS configuration on the host was synchronized with that of the vCenter Server and the configuration is the same on the host and vCenter Server.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsHostBackInSyncEvent.html)

<a id="DVSHOSTJOINEDEVENT"></a>

• Event **DvsHostJoinedEvent**

A host joined the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsHostJoinedEvent.html)

<a id="DVSHOSTLEFTEVENT"></a>

• Event **DvsHostLeftEvent**

A host left the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsHostLeftEvent.html)

<a id="DVSHOSTSTATUSUPDATED"></a>

• Event **DvsHostStatusUpdated**

A host has its status or statusDetail updated

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.DvsHostStatusUpdated.html)

<a id="DVSHOSTWENTOUTOFSYNCEVENT"></a>

• Event **DvsHostWentOutOfSyncEvent**

The DVS configuration on the host diverged from that of the Virtual Center Server.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsHostWentOutOfSyncEvent.html)

<a id="DVSIMPORTEVENT"></a>

• Event **DvsImportEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsImportEvent.html)

<a id="DVSMERGEDEVENT"></a>

• Event **DvsMergedEvent**

Two distributed virtual switches was merged.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsMergedEvent.html)

<a id="DVSPORTBLOCKEDEVENT"></a>

• Event **DvsPortBlockedEvent**

A port is blocked in the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortBlockedEvent.html)

<a id="DVSPORTCONNECTEDEVENT"></a>

• Event **DvsPortConnectedEvent**

A port is connected in the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortConnectedEvent.html)

<a id="DVSPORTCREATEDEVENT"></a>

• Event **DvsPortCreatedEvent**

New ports are created in the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortCreatedEvent.html)

<a id="DVSPORTDELETEDEVENT"></a>

• Event **DvsPortDeletedEvent**

Existing ports are deleted in the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortDeletedEvent.html)

<a id="DVSPORTDISCONNECTEDEVENT"></a>

• Event **DvsPortDisconnectedEvent**

A port is disconnected in the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortDisconnectedEvent.html)

<a id="DVSPORTENTEREDPASSTHRUEVENT"></a>

• Event **DvsPortEnteredPassthruEvent**

A port has entered passthrough mode on the distributed virtual switch

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.DvsPortEnteredPassthruEvent.html)

<a id="DVSPORTEXITEDPASSTHRUEVENT"></a>

• Event **DvsPortExitedPassthruEvent**

A port has exited passthrough mode on the distributed virtual switch

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.DvsPortExitedPassthruEvent.html)

<a id="DVSPORTJOINPORTGROUPEVENT"></a>

• Event **DvsPortJoinPortgroupEvent**

A port was moved into the distributed virtual port group.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortJoinPortgroupEvent.html)

<a id="DVSPORTLEAVEPORTGROUPEVENT"></a>

• Event **DvsPortLeavePortgroupEvent**

A port was moved out of the distributed virtual port group.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortLeavePortgroupEvent.html)

<a id="DVSPORTLINKDOWNEVENT"></a>

• Event **DvsPortLinkDownEvent**

A port of which link status is changed to down in the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortLinkDownEvent.html)

<a id="DVSPORTLINKUPEVENT"></a>

• Event **DvsPortLinkUpEvent**

A port of which link status is changed to up in the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortLinkUpEvent.html)

<a id="DVSPORTRECONFIGUREDEVENT"></a>

• Event **DvsPortReconfiguredEvent**

Existing ports are reconfigured in the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortReconfiguredEvent.html)

<a id="DVSPORTRUNTIMECHANGEEVENT"></a>

• Event **DvsPortRuntimeChangeEvent**

DVS runtime information changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortRuntimeChangeEvent.html)

<a id="DVSPORTUNBLOCKEDEVENT"></a>

• Event **DvsPortUnblockedEvent**

A port is blocked in the distributed virtual switch.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortUnblockedEvent.html)

<a id="DVSPORTVENDORSPECIFICSTATECHANGEEVENT"></a>

• Event **DvsPortVendorSpecificStateChangeEvent**

Vendor specific state changed in the DVS

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsPortVendorSpecificStateChangeEvent.html)

<a id="DVSRECONFIGUREDEVENT"></a>

• Event **DvsReconfiguredEvent**

A distributed virtual switch was reconfigured.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsReconfiguredEvent.html)

<a id="DVSRENAMEDEVENT"></a>

• Event **DvsRenamedEvent**

A distributed virtual switch was renamed.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsRenamedEvent.html)

<a id="DVSRESTOREEVENT"></a>

• Event **DvsRestoreEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsRestoreEvent.html)

<a id="DVSUPGRADEAVAILABLEEVENT"></a>

• Event **DvsUpgradeAvailableEvent**

An upgrade for the distributed virtual switch is available.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsUpgradeAvailableEvent.html)

<a id="DVSUPGRADEDEVENT"></a>

• Event **DvsUpgradedEvent**

The distributed virtual switch was upgraded.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsUpgradedEvent.html)

<a id="DVSUPGRADEINPROGRESSEVENT"></a>

• Event **DvsUpgradeInProgressEvent**

An upgrade for the distributed virtual switch is in progress.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsUpgradeInProgressEvent.html)

<a id="DVSUPGRADEREJECTEDEVENT"></a>

• Event **DvsUpgradeRejectedEvent**

An upgrade for the distributed virtual switch is rejected.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.DvsUpgradeRejectedEvent.html)

<a id="ENTEREDMAINTENANCEMODEEVENT"></a>

• Event **EnteredMaintenanceModeEvent**

This event records that the host has completely entered maintenance mode. A host in this mode has no running virtual machines and no provisioning operations are occurring.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EnteredMaintenanceModeEvent.html)

<a id="ENTEREDSTANDBYMODEEVENT"></a>

• Event **EnteredStandbyModeEvent**

This event records that the host has completely entered standby mode. A host in this mode has no running virtual machines and no provisioning operations are occurring.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EnteredStandbyModeEvent.html)

<a id="ENTERINGMAINTENANCEMODEEVENT"></a>

• Event **EnteringMaintenanceModeEvent**

This event records that a host has begun the process of entering maintenance mode. All virtual machine operations are blocked, except for the following:

- MigrateVM
- PowerOffVM
- SuspendVM
- ShutdownGuest
- StandbyGuest

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EnteringMaintenanceModeEvent.html)

<a id="ENTERINGSTANDBYMODEEVENT"></a>

• Event **EnteringStandbyModeEvent**

This event records that a host has begun the process of entering standby mode. All virtual machine operations are blocked, except for the following:

- MigrateVM
- PowerOffVM
- SuspendVM
- ShutdownGuest
- StandbyGuest

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EnteringStandbyModeEvent.html)

<a id="ERRORUPGRADEEVENT"></a>

• Event **ErrorUpgradeEvent**

This event is a general error event from upgrade.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ErrorUpgradeEvent.html)

<a id="ESX.AUDIT.DCUI.DEFAULTS.FACTORYRESTORE"></a>

• Event **esx.audit.dcui.defaults.factoryrestore**

The host has been restored to default factory settings

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.DCUI.DISABLED"></a>

• Event **esx.audit.dcui.disabled**

The DCUI has been disabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.DCUI.ENABLED"></a>

• Event **esx.audit.dcui.enabled**

The DCUI has been enabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.DCUI.HOST.REBOOT"></a>

• Event **esx.audit.dcui.host.reboot**

The host is being rebooted through the Direct Console User Interface (DCUI)

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.DCUI.HOST.SHUTDOWN"></a>

• Event **esx.audit.dcui.host.shutdown**

The host is being shut down through the Direct Console User Interface (DCUI)

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.DCUI.HOSTAGENTS.RESTART"></a>

• Event **esx.audit.dcui.hostagents.restart**

The management agents on the host are being restarted

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.DCUI.LOGIN.FAILED"></a>

• Event **esx.audit.dcui.login.failed**

Authentication has failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.DCUI.LOGIN.PASSWD.CHANGED"></a>

• Event **esx.audit.dcui.login.passwd.changed**

Login password has been changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.DCUI.NETWORK.FACTORYRESTORE"></a>

• Event **esx.audit.dcui.network.factoryrestore**

The host has been restored to factory network settings

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.DCUI.NETWORK.RESTART"></a>

• Event **esx.audit.dcui.network.restart**

A management interface has been restarted

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.ESXCLI.HOST.POWEROFF"></a>

• Event **esx.audit.esxcli.host.poweroff**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.ESXCLI.HOST.RESTART"></a>

• Event **esx.audit.esxcli.host.restart**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.ESXIMAGE.HOSTACCEPTANCE.CHANGED"></a>

• Event **esx.audit.esximage.hostacceptance.changed**

Host acceptance level changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.ESXIMAGE.INSTALL.NOVALIDATION"></a>

• Event **esx.audit.esximage.install.novalidation**

Attempting to install an image profile with validation disabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.ESXIMAGE.INSTALL.SECURITYALERT"></a>

• Event **esx.audit.esximage.install.securityalert**

SECURITY ALERT: Installing image profile

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.ESXIMAGE.PROFILE.INSTALL.SUCCESSFUL"></a>

• Event **esx.audit.esximage.profile.install.successful**

Successfully installed image profile

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.ESXIMAGE.PROFILE.UPDATE.SUCCESSFUL"></a>

• Event **esx.audit.esximage.profile.update.successful**

Successfully updated host to image profile

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.ESXIMAGE.VIB.INSTALL.SUCCESSFUL"></a>

• Event **esx.audit.esximage.vib.install.successful**

Successfully installed VIBs

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.ESXIMAGE.VIB.REMOVE.SUCCESSFUL"></a>

• Event **esx.audit.esximage.vib.remove.successful**

Successfully removed VIBs

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.HOST.BOOT"></a>

• Event **esx.audit.host.boot**

Host has booted

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.HOST.MAXREGISTEREDVMSEXCEEDED"></a>

• Event **esx.audit.host.maxRegisteredVMsExceeded**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.HOST.STOP.REBOOT"></a>

• Event **esx.audit.host.stop.reboot**

Host is rebooting

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.HOST.STOP.SHUTDOWN"></a>

• Event **esx.audit.host.stop.shutdown**

Host is shutting down

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.LOCKDOWNMODE.DISABLED"></a>

• Event **esx.audit.lockdownmode.disabled**

Administrator access to the host has been enabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.LOCKDOWNMODE.ENABLED"></a>

• Event **esx.audit.lockdownmode.enabled**

Administrator access to the host has been disabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.MAINTENANCEMODE.CANCELED"></a>

• Event **esx.audit.maintenancemode.canceled**

The host has canceled entering maintenance mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.MAINTENANCEMODE.ENTERED"></a>

• Event **esx.audit.maintenancemode.entered**

The host has entered maintenance mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.MAINTENANCEMODE.ENTERING"></a>

• Event **esx.audit.maintenancemode.entering**

The host has begun entering maintenance mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.MAINTENANCEMODE.EXITED"></a>

• Event **esx.audit.maintenancemode.exited**

The host has exited maintenance mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.NET.FIREWALL.CONFIG.CHANGED"></a>

• Event **esx.audit.net.firewall.config.changed**

Firewall configuration has changed.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.NET.FIREWALL.DISABLED"></a>

• Event **esx.audit.net.firewall.disabled**

Firewall has been disabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.NET.FIREWALL.ENABLED"></a>

• Event **esx.audit.net.firewall.enabled**

Firewall has been enabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.NET.FIREWALL.PORT.HOOKED"></a>

• Event **esx.audit.net.firewall.port.hooked**

Port is now protected by Firewall

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.NET.FIREWALL.PORT.REMOVED"></a>

• Event **esx.audit.net.firewall.port.removed**

Port is no longer protected with Firewall.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.NET.LACP.DISABLE"></a>

• Event **esx.audit.net.lacp.disable**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.NET.LACP.ENABLE"></a>

• Event **esx.audit.net.lacp.enable**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.NET.LACP.UPLINK.CONNECTED"></a>

• Event **esx.audit.net.lacp.uplink.connected**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.NET.VDL2.IP.CHANGE"></a>

• Event **esx.audit.net.vdl2.ip.change**

VDL2 IP changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.NET.VDL2.MAPPINGTABLE.FULL"></a>

• Event **esx.audit.net.vdl2.mappingtable.full**

Mapping table entries of VDL2 network exhausted

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.NET.VDL2.ROUTE.CHANGE"></a>

• Event **esx.audit.net.vdl2.route.change**

VDL2 IP interface default route changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.SHELL.DISABLED"></a>

• Event **esx.audit.shell.disabled**

The ESX command line shell has been disabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.SHELL.ENABLED"></a>

• Event **esx.audit.shell.enabled**

The ESX command line shell has been enabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.SSH.DISABLED"></a>

• Event **esx.audit.ssh.disabled**

SSH access has been disabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.SSH.ENABLED"></a>

• Event **esx.audit.ssh.enabled**

SSH access has been enabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.USB.CONFIG.CHANGED"></a>

• Event **esx.audit.usb.config.changed**

USB configuration has changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.UW.SECPOLICY.ALLDOMAINS.LEVEL.CHANGED"></a>

• Event **esx.audit.uw.secpolicy.alldomains.level.changed**

The enforcement level for all security domains has been changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.UW.SECPOLICY.DOMAIN.LEVEL.CHANGED"></a>

• Event **esx.audit.uw.secpolicy.domain.level.changed**

The enforcement level for security domain has been changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.VMFS.LVM.DEVICE.DISCOVERED"></a>

• Event **esx.audit.vmfs.lvm.device.discovered**

One or more LVM devices have been discovered

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.AUDIT.VMFS.VOLUME.MOUNTED"></a>

• Event **esx.audit.vmfs.volume.mounted**

File system has been mounted

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.VMFS.VOLUME.UMOUNTED"></a>

• Event **esx.audit.vmfs.volume.umounted**

The volume has been safely unmounted

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.AUDIT.VSAN.CLUSTERING.ENABLED"></a>

• Event **esx.audit.vsan.clustering.enabled**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.CLEAR.COREDUMP.CONFIGURED"></a>

• Event **esx.clear.coredump.configured**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.CLEAR.NET.CONNECTIVITY.RESTORED"></a>

• Event **esx.clear.net.connectivity.restored**

Restored network connectivity to port groups

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.NET.DVPORT.CONNECTIVITY.RESTORED"></a>

• Event **esx.clear.net.dvport.connectivity.restored**

Restored Network Connectivity to DVPorts

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.NET.DVPORT.REDUNDANCY.RESTORED"></a>

• Event **esx.clear.net.dvport.redundancy.restored**

Restored Network Redundancy to DVPorts

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.NET.LACP.LAG.TRANSITION.UP"></a>

• Event **esx.clear.net.lacp.lag.transition.up**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.NET.LACP.UPLINK.TRANSITION.UP"></a>

• Event **esx.clear.net.lacp.uplink.transition.up**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.NET.LACP.UPLINK.UNBLOCKED"></a>

• Event **esx.clear.net.lacp.uplink.unblocked**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.NET.REDUNDANCY.RESTORED"></a>

• Event **esx.clear.net.redundancy.restored**

Restored uplink redundancy to port groups

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.NET.VMNIC.LINKSTATE.UP"></a>

• Event **esx.clear.net.vmnic.linkstate.up**

Link state up

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.SCSI.DEVICE.IO.LATENCY.IMPROVED"></a>

• Event **esx.clear.scsi.device.io.latency.improved**

Device performance has improved

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.SCSI.DEVICE.STATE.ON"></a>

• Event **esx.clear.scsi.device.state.on**

Device has been turned on administratively

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.SCSI.DEVICE.STATE.PERMANENTLOSS.DEVICEONLINE"></a>

• Event **esx.clear.scsi.device.state.permanentloss.deviceonline**

Device that was permanently inaccessible is now online. No data consistency guarantees

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.STORAGE.APD.EXIT"></a>

• Event **esx.clear.storage.apd.exit**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.STORAGE.CONNECTIVITY.RESTORED"></a>

• Event **esx.clear.storage.connectivity.restored**

Restored connectivity to storage device

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.STORAGE.REDUNDANCY.RESTORED"></a>

• Event **esx.clear.storage.redundancy.restored**

Restored path redundancy to storage device

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.VSAN.CLUSTERING.ENABLED"></a>

• Event **esx.clear.vsan.clustering.enabled**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.CLEAR.VSAN.NETWORK.AVAILABLE"></a>

• Event **esx.clear.vsan.network.available**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.CLEAR.VSAN.VMKNIC.READY"></a>

• Event **esx.clear.vsan.vmknic.ready**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.3RDPARTY.ERROR"></a>

• Event **esx.problem.3rdParty.error**

A 3rd party component running on ESXi has reported an error

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.3RDPARTY.INFO"></a>

• Event **esx.problem.3rdParty.info**

A 3rd party component running on ESXi has reported an info message

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.3RDPARTY.WARNING"></a>

• Event **esx.problem.3rdParty.warning**

A 3rd party component running on ESXi has reported a warning

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.APEI.BERT.MEMORY.ERROR.CORRECTED"></a>

• Event **esx.problem.apei.bert.memory.error.corrected**

A corrected memory error occurred

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.APEI.BERT.MEMORY.ERROR.FATAL"></a>

• Event **esx.problem.apei.bert.memory.error.fatal**

A fatal memory error occurred

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.APEI.BERT.MEMORY.ERROR.RECOVERABLE"></a>

• Event **esx.problem.apei.bert.memory.error.recoverable**

A recoverable memory error occurred

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.APEI.BERT.PCIE.ERROR.CORRECTED"></a>

• Event **esx.problem.apei.bert.pcie.error.corrected**

A corrected PCIe error occurred

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.APEI.BERT.PCIE.ERROR.FATAL"></a>

• Event **esx.problem.apei.bert.pcie.error.fatal**

A fatal PCIe error occurred

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.APEI.BERT.PCIE.ERROR.RECOVERABLE"></a>

• Event **esx.problem.apei.bert.pcie.error.recoverable**

A recoverable PCIe error occurred

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.APPLICATION.CORE.DUMPED"></a>

• Event **esx.problem.application.core.dumped**

An application running on ESXi host has crashed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.COREDUMP.UNCONFIGURED"></a>

• Event **esx.problem.coredump.unconfigured**

No vmkcore disk partition is available and no network coredump server has been configured. Host core dumps cannot be saved.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.CPU.AMD.MCE.DRAM.DISABLED"></a>

• Event **esx.problem.cpu.amd.mce.dram.disabled**

DRAM ECC not enabled

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.CPU.INTEL.IOAPIC.LISTING.ERROR"></a>

• Event **esx.problem.cpu.intel.ioapic.listing.error**

Not all IO-APICs are listed in the DMAR

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.CPU.MCE.INVALID"></a>

• Event **esx.problem.cpu.mce.invalid**

MCE monitoring will be disabled as an unsupported CPU was detected

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.CPU.SMP.HT.INVALID"></a>

• Event **esx.problem.cpu.smp.ht.invalid**

Disabling HyperThreading due to invalid configuration

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.CPU.SMP.HT.NUMPCPUS.MAX"></a>

• Event **esx.problem.cpu.smp.ht.numpcpus.max**

CPU limit reached

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.CPU.SMP.HT.PARTNER.MISSING"></a>

• Event **esx.problem.cpu.smp.ht.partner.missing**

Disabling HyperThreading due to invalid configuration: HT partner is missing from PCPU

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.DHCLIENT.LEASE.NONE"></a>

• Event **esx.problem.dhclient.lease.none**

Unable to obtain a DHCP lease

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.DHCLIENT.LEASE.OFFERED.ERROR"></a>

• Event **esx.problem.dhclient.lease.offered.error**

dhclient reported an error

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.DHCLIENT.LEASE.PERSISTENT.NONE"></a>

• Event **esx.problem.dhclient.lease.persistent.none**

No working DHCP leases in persistent database

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.ESXIMAGE.INSTALL.ERROR"></a>

• Event **esx.problem.esximage.install.error**

Image profile could not be installed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.ESXIMAGE.INSTALL.INVALIDHARDWARE"></a>

• Event **esx.problem.esximage.install.invalidhardware**

Host doesn't meet hardware requirements

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.ESXIMAGE.INSTALL.STAGE.ERROR"></a>

• Event **esx.problem.esximage.install.stage.error**

Could not stage image profile

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.HARDWARE.ACPI.INTERRUPT.ROUTING.DEVICE.INVALID"></a>

• Event **esx.problem.hardware.acpi.interrupt.routing.device.invalid**

BIOS bug, skipping interrupt routing entry with bad device number

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.HARDWARE.ACPI.INTERRUPT.ROUTING.PIN.INVALID"></a>

• Event **esx.problem.hardware.acpi.interrupt.routing.pin.invalid**

BIOS bug, skipping interrupt routing entry with bad device pin

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.HARDWARE.IOAPIC.MISSING"></a>

• Event **esx.problem.hardware.ioapic.missing**

IOAPIC is missing. Check BIOS settings.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.HOST.COREDUMP"></a>

• Event **esx.problem.host.coredump**

An unread host kernel core dump has been found

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.HOSTD.CORE.DUMPED"></a>

• Event **esx.problem.hostd.core.dumped**

hostd crashed with a core file created

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.IORM.BADVERSION"></a>

• Event **esx.problem.iorm.badversion**

Host cannot participate in SIOC because of incompatible version number

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.IORM.NONVIWORKLOAD"></a>

• Event **esx.problem.iorm.nonviworkload**

External/Uncontrolled workload detected on a datastore

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.MIGRATE.VMOTION.DEFAULT.HEAP.CREATE.FAILED"></a>

• Event **esx.problem.migrate.vmotion.default.heap.create.failed**

Default migration heap creation failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.MIGRATE.VMOTION.SERVER.PENDING.CNX.LISTEN.SOCKET.SHUTDOWN"></a>

• Event **esx.problem.migrate.vmotion.server.pending.cnx.listen.socket.shutdown**

The ESXi host vMotion network server encountered an error while monitoring incoming network connections. Shutting down listener socket. vMotion may not be possible with this host until vMotion is manually re-enabled.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.CONNECTIVITY.LOST"></a>

• Event **esx.problem.net.connectivity.lost**

Network connectivity lost on vSwitch

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.DVPORT.CONNECTIVITY.LOST"></a>

• Event **esx.problem.net.dvport.connectivity.lost**

Network connectivity lost on DVPorts

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.DVPORT.REDUNDANCY.DEGRADED"></a>

• Event **esx.problem.net.dvport.redundancy.degraded**

Network Redundancy Degraded on DVPorts

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.DVPORT.REDUNDANCY.LOST"></a>

• Event **esx.problem.net.dvport.redundancy.lost**

Network Redundancy Lost on DVPorts

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.E1000.TSO6.NOTSUPPORTED"></a>

• Event **esx.problem.net.e1000.tso6.notsupported**

Guest-initiated IPv6 TCP Segmentation Offload (TSO) packets ignored. Manually disable TSO inside the guest operating system, or use a different virtual adapter.

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.FENCE.PORT.BADFENCEID"></a>

• Event **esx.problem.net.fence.port.badfenceid**

VMkernel failed to set fenceId

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.FENCE.RESOURCE.LIMITED"></a>

• Event **esx.problem.net.fence.resource.limited**

Maximum number of fence networks or ports have been reached

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.FENCE.SWITCH.UNAVAILABLE"></a>

• Event **esx.problem.net.fence.switch.unavailable**

dvSwitch fence property is not set

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.FIREWALL.CONFIG.FAILED"></a>

• Event **esx.problem.net.firewall.config.failed**

Firewall configuration failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.FIREWALL.PORT.HOOKFAILED"></a>

• Event **esx.problem.net.firewall.port.hookfailed**

Adding port to Firewall failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.GATEWAY.SET.FAILED"></a>

• Event **esx.problem.net.gateway.set.failed**

Cannot connect to the specified gateway

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.HEAP.BELOWTHRESHOLD"></a>

• Event **esx.problem.net.heap.belowthreshold**

Heap free size dropped

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.LACP.LAG.TRANSITION.DOWN"></a>

• Event **esx.problem.net.lacp.lag.transition.down**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.LACP.PEER.NORESPONSE"></a>

• Event **esx.problem.net.lacp.peer.noresponse**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.LACP.POLICY.INCOMPATIBLE"></a>

• Event **esx.problem.net.lacp.policy.incompatible**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.LACP.POLICY.LINKSTATUS"></a>

• Event **esx.problem.net.lacp.policy.linkstatus**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.LACP.UPLINK.BLOCKED"></a>

• Event **esx.problem.net.lacp.uplink.blocked**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.LACP.UPLINK.DISCONNECTED"></a>

• Event **esx.problem.net.lacp.uplink.disconnected**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.LACP.UPLINK.FAIL.DUPLEX"></a>

• Event **esx.problem.net.lacp.uplink.fail.duplex**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.LACP.UPLINK.FAIL.SPEED"></a>

• Event **esx.problem.net.lacp.uplink.fail.speed**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.LACP.UPLINK.INACTIVE"></a>

• Event **esx.problem.net.lacp.uplink.inactive**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.LACP.UPLINK.TRANSITION.DOWN"></a>

• Event **esx.problem.net.lacp.uplink.transition.down**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.MIGRATE.BINDTOVMK"></a>

• Event **esx.problem.net.migrate.bindtovmk**

Invalid vmknic specified in the ESX configuration

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.MIGRATE.UNSUPPORTED.LATENCY"></a>

• Event **esx.problem.net.migrate.unsupported.latency**

High vMotion network latency detected

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.PORTSET.PORT.FULL"></a>

• Event **esx.problem.net.portset.port.full**

Maximum number of ports has been reached. Cannot apply for any more free ports.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.PORTSET.PORT.VLAN.INVALIDID"></a>

• Event **esx.problem.net.portset.port.vlan.invalidid**

Invalid VLANID. VLAN ID must be between 0 and 4095.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.PROXYSWITCH.PORT.UNAVAILABLE"></a>

• Event **esx.problem.net.proxyswitch.port.unavailable**

Virtual NIC connection to switch failed

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.REDUNDANCY.DEGRADED"></a>

• Event **esx.problem.net.redundancy.degraded**

Network redundancy degraded on vSwitch

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.REDUNDANCY.LOST"></a>

• Event **esx.problem.net.redundancy.lost**

Network redundancy lost on vSwitch

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.UPLINK.MTU.FAILED"></a>

• Event **esx.problem.net.uplink.mtu.failed**

Failed to set MTU on an uplink

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VDL2.INSTANCE.INITIALIZATION.FAIL"></a>

• Event **esx.problem.net.vdl2.instance.initialization.fail**

VDL2 instance initialization failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VDL2.INSTANCE.NOTEXIST"></a>

• Event **esx.problem.net.vdl2.instance.notexist**

VDL2 overlay instance is not created on DVS

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VDL2.MCASTGROUP.FAIL"></a>

• Event **esx.problem.net.vdl2.mcastgroup.fail**

VDL2 IP interface on vmknic failed to join multicast group

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VDL2.NETWORK.INITIALIZATION.FAIL"></a>

• Event **esx.problem.net.vdl2.network.initialization.fail**

VDL2 network initialization failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VDL2.PORT.INITIALIZATION.FAIL"></a>

• Event **esx.problem.net.vdl2.port.initialization.fail**

VDL2 initialization failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VDL2.VMKNIC.FAIL"></a>

• Event **esx.problem.net.vdl2.vmknic.fail**

VDL2 IP interface failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VDL2.VMKNIC.NOTEXIST"></a>

• Event **esx.problem.net.vdl2.vmknic.notexist**

VDL2 IP interface does not exist

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VMKNIC.IP.DUPLICATE"></a>

• Event **esx.problem.net.vmknic.ip.duplicate**

A duplicate IP address was detected on a vmknic interface

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VMNIC.LINKSTATE.DOWN"></a>

• Event **esx.problem.net.vmnic.linkstate.down**

Link state down

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VMNIC.LINKSTATE.FLAPPING"></a>

• Event **esx.problem.net.vmnic.linkstate.flapping**

NIC link is unstable. Taking down.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NET.VMNIC.WATCHDOG.RESET"></a>

• Event **esx.problem.net.vmnic.watchdog.reset**

Nic Watchdog Reset

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.NTPD.CLOCK.CORRECTION.ERROR"></a>

• Event **esx.problem.ntpd.clock.correction.error**

NTP daemon stopped.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.PAGERETIRE.PLATFORM.RETIRE.REQUEST"></a>

• Event **esx.problem.pageretire.platform.retire.request**

Memory page retirement requested by platform firmware

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.PAGERETIRE.SELECTEDMPNTHRESHOLD.HOST.EXCEEDED"></a>

• Event **esx.problem.pageretire.selectedmpnthreshold.host.exceeded**

Number of host physical memory pages that have been selected for retirement exceeds threshold

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.PAGERETIRE.SELECTEDMPNTHRESHOLD.KERNEL.EXCEEDED"></a>

• Event **esx.problem.pageretire.selectedmpnthreshold.kernel.exceeded**

Number of kernel physical memory pages that have been selected for retirement exceeds threshold

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.PAGERETIRE.SELECTEDMPNTHRESHOLD.USERCLIENT.EXCEEDED"></a>

• Event **esx.problem.pageretire.selectedmpnthreshold.userclient.exceeded**

Number of physical memory pages belonging to (user) memory client that have been selected for retirement exceeds threshold

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.PAGERETIRE.SELECTEDMPNTHRESHOLD.USERPRIVATE.EXCEEDED"></a>

• Event **esx.problem.pageretire.selectedmpnthreshold.userprivate.exceeded**

Number of private user physical memory pages that have been selected for retirement exceeds threshold

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.PAGERETIRE.SELECTEDMPNTHRESHOLD.USERSHARED.EXCEEDED"></a>

• Event **esx.problem.pageretire.selectedmpnthreshold.usershared.exceeded**

Number of shared user physical memory pages that have been selected for retirement exceeds threshold

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.PAGERETIRE.SELECTEDMPNTHRESHOLD.VMMCLIENT.EXCEEDED"></a>

• Event **esx.problem.pageretire.selectedmpnthreshold.vmmclient.exceeded**

Number of physical memory pages belonging to (vmm) memory client that have been selected for retirement exceeds threshold

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.APD.EVENT.DESCRIPTOR.ALLOC.FAILED"></a>

• Event **esx.problem.scsi.apd.event.descriptor.alloc.failed**

No memory to allocate APD (All Paths Down) event subsystem

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.CLOSE.FAILED"></a>

• Event **esx.problem.scsi.device.close.failed**

Failed to close the device properly

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.DETACH.FAILED"></a>

• Event **esx.problem.scsi.device.detach.failed**

Exceeded the number of devices that can be detached, detach failed.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.FILTER.ATTACH.FAILED"></a>

• Event **esx.problem.scsi.device.filter.attach.failed**

Failed to attach filters to device '%s' during registration. Plugin load failed or the filter rules are incorrect.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.IO.BAD.PLUGIN.TYPE"></a>

• Event **esx.problem.scsi.device.io.bad.plugin.type**

Bad plugin type for device

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.IO.INQUIRY.FAILED"></a>

• Event **esx.problem.scsi.device.io.inquiry.failed**

Failed to get standard inquiry for device

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.IO.INVALID.DISK.QFULL.VALUE"></a>

• Event **esx.problem.scsi.device.io.invalid.disk.qfull.value**

QFullSampleSize should be bigger than QFullThreshold

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.IO.LATENCY.HIGH"></a>

• Event **esx.problem.scsi.device.io.latency.high**

Device I/O latency increased

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.IO.QERR.CHANGE.CONFIG"></a>

• Event **esx.problem.scsi.device.io.qerr.change.config**

SCSI ChangeQErrSetting configuration value has been changed. This may cause unexpected behavior.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.IO.QERR.CHANGED"></a>

• Event **esx.problem.scsi.device.io.qerr.changed**

QErr configuration value has been changed. This may cause unexpected behavior.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.IS.LOCAL.FAILED"></a>

• Event **esx.problem.scsi.device.is.local.failed**

Failed to verify if the device from plugin is a local - not shared - device

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.IS.PSEUDO.FAILED"></a>

• Event **esx.problem.scsi.device.is.pseudo.failed**

Failed to verify if the device from plugin is a pseudo device

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.IS.SSD.FAILED"></a>

• Event **esx.problem.scsi.device.is.ssd.failed**

Failed to verify if the device from plugin is a Solid State Disk device

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.LIMITREACHED"></a>

• Event **esx.problem.scsi.device.limitreached**

The maximum number of supported devices has been reached

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.STATE.OFF"></a>

• Event **esx.problem.scsi.device.state.off**

Device has been turned off administratively

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.STATE.PERMANENTLOSS"></a>

• Event **esx.problem.scsi.device.state.permanentloss**

Device has been removed or is permanently inaccessible

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.STATE.PERMANENTLOSS.NOOPENS"></a>

• Event **esx.problem.scsi.device.state.permanentloss.noopens**

Permanently inaccessible device has no more opens

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.STATE.PERMANENTLOSS.PLUGGEDBACK"></a>

• Event **esx.problem.scsi.device.state.permanentloss.pluggedback**

Device has been plugged back in after being marked permanently inaccessible

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.STATE.PERMANENTLOSS.WITHRESERVATIONHELD"></a>

• Event **esx.problem.scsi.device.state.permanentloss.withreservationheld**

Device has been removed or is permanently inaccessible, while holding a reservation.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.DEVICE.THINPROV.ATQUOTA"></a>

• Event **esx.problem.scsi.device.thinprov.atquota**

Thin Provisioned Device Nearing Capacity

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.SCSIPATH.LIMITREACHED"></a>

• Event **esx.problem.scsi.scsipath.limitreached**

Maximum number of storage paths

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SCSI.UNSUPPORTED.PLUGIN.TYPE"></a>

• Event **esx.problem.scsi.unsupported.plugin.type**

SCSI Device Allocation not supported for plugin type

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.APD.START"></a>

• Event **esx.problem.storage.apd.start**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.APD.TIMEOUT"></a>

• Event **esx.problem.storage.apd.timeout**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.CONNECTIVITY.DEVICEPOR"></a>

• Event **esx.problem.storage.connectivity.devicepor**

Frequent PowerOn Reset Unit Attention of storage device

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.CONNECTIVITY.LOST"></a>

• Event **esx.problem.storage.connectivity.lost**

Storage connectivity lost

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.CONNECTIVITY.PATHPOR"></a>

• Event **esx.problem.storage.connectivity.pathpor**

Frequent PowerOn Reset Unit Attention of Storage Path

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.CONNECTIVITY.PATHSTATECHANGES"></a>

• Event **esx.problem.storage.connectivity.pathstatechanges**

Frequent State Changes of Storage Path

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.ISCSI.DISCOVERY.CONNECT.ERROR"></a>

• Event **esx.problem.storage.iscsi.discovery.connect.error**

iSCSI discovery failed. The iSCSI Initiator could not establish a network connection to the discovery address.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.ISCSI.DISCOVERY.LOGIN.ERROR"></a>

• Event **esx.problem.storage.iscsi.discovery.login.error**

iSCSI discovery failed. The Discovery target returned a login error

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.ISCSI.TARGET.CONNECT.ERROR"></a>

• Event **esx.problem.storage.iscsi.target.connect.error**

Login to iSCSI target failed. The iSCSI initiator could not establish a network connection to the target

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.ISCSI.TARGET.LOGIN.ERROR"></a>

• Event **esx.problem.storage.iscsi.target.login.error**

Login to iSCSI target failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.ISCSI.TARGET.PERMANENTLY.LOST"></a>

• Event **esx.problem.storage.iscsi.target.permanently.lost**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.REDUNDANCY.DEGRADED"></a>

• Event **esx.problem.storage.redundancy.degraded**

Storage redundancy degraded

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.STORAGE.REDUNDANCY.LOST"></a>

• Event **esx.problem.storage.redundancy.lost**

Storage redundancy lost

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.SYSLOG.CONFIG"></a>

• Event **esx.problem.syslog.config**

System logging is not configured on host

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.SYSLOG.NONPERSISTENT"></a>

• Event **esx.problem.syslog.nonpersistent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.VFAT.FILESYSTEM.FULL.OTHER"></a>

• Event **esx.problem.vfat.filesystem.full.other**

The VFAT filesystem is full

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VFAT.FILESYSTEM.FULL.SCRATCH"></a>

• Event **esx.problem.vfat.filesystem.full.scratch**

The host scratch partition, which is the VFAT filesystem, is full

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VISORFS.FAILURE"></a>

• Event **esx.problem.visorfs.failure**

An operation on the root filesystem has failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.VISORFS.INODETABLE.FULL"></a>

• Event **esx.problem.visorfs.inodetable.full**

The root filesystem file table is full

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VISORFS.RAMDISK.FULL"></a>

• Event **esx.problem.visorfs.ramdisk.full**

The ramdisk is full

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VISORFS.RAMDISK.INODETABLE.FULL"></a>

• Event **esx.problem.visorfs.ramdisk.inodetable.full**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VM.KILL.UNEXPECTED.FAULT.FAILURE"></a>

• Event **esx.problem.vm.kill.unexpected.fault.failure**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VM.KILL.UNEXPECTED.FORCEFULPAGERETIRE"></a>

• Event **esx.problem.vm.kill.unexpected.forcefulPageRetire**

The VM contains host physical page which was scheduled for immediate retirement

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VM.KILL.UNEXPECTED.NOSWAPRESPONSE"></a>

• Event **esx.problem.vm.kill.unexpected.noSwapResponse**

The VM did not respond to swap actions and is forcefully powered off to prevent system instability

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VM.KILL.UNEXPECTED.VMTRACK"></a>

• Event **esx.problem.vm.kill.unexpected.vmtrack**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.ATS.SUPPORT.LOST"></a>

• Event **esx.problem.vmfs.ats.support.lost**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.ERROR.VOLUME.IS.LOCKED"></a>

• Event **esx.problem.vmfs.error.volume.is.locked**

Volume is locked

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.EXTENT.OFFLINE"></a>

• Event **esx.problem.vmfs.extent.offline**

Attached device is offline

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.EXTENT.ONLINE"></a>

• Event **esx.problem.vmfs.extent.online**

Backing file system came online

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.HEARTBEAT.RECOVERED"></a>

• Event **esx.problem.vmfs.heartbeat.recovered**

Access to volume successfully restored

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.HEARTBEAT.TIMEDOUT"></a>

• Event **esx.problem.vmfs.heartbeat.timedout**

Volume connectivity lost

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.HEARTBEAT.UNRECOVERABLE"></a>

• Event **esx.problem.vmfs.heartbeat.unrecoverable**

Volume connectivity lost and subsequent recovery attempts have failed

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.JOURNAL.CREATEFAILED"></a>

• Event **esx.problem.vmfs.journal.createfailed**

No space for journal. Opening volume in read-only metadata mode with limited write support.

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.LOCK.CORRUPTONDISK"></a>

• Event **esx.problem.vmfs.lock.corruptondisk**

Corrupt on-disk lock was detected on volume. Other regions of the volume may be damaged too.

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.NFS.MOUNT.CONNECT.FAILED"></a>

• Event **esx.problem.vmfs.nfs.mount.connect.failed**

Unable to connect to NFS server

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.NFS.MOUNT.LIMIT.EXCEEDED"></a>

• Event **esx.problem.vmfs.nfs.mount.limit.exceeded**

NFS has reached the maximum number of supported volumes

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.NFS.SERVER.DISCONNECT"></a>

• Event **esx.problem.vmfs.nfs.server.disconnect**

NFS Server disconnected

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.NFS.SERVER.RESTORED"></a>

• Event **esx.problem.vmfs.nfs.server.restored**

NFS Server reconnected

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.RESOURCE.CORRUPTONDISK"></a>

• Event **esx.problem.vmfs.resource.corruptondisk**

Corrupt resource metadata region was detected

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMFS.VOLUME.LOCKED"></a>

• Event **esx.problem.vmfs.volume.locked**

Volume locked

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMSYSLOGD.REMOTE.FAILURE"></a>

• Event **esx.problem.vmsyslogd.remote.failure**

Hose has become unreachable

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMSYSLOGD.STORAGE.FAILURE"></a>

• Event **esx.problem.vmsyslogd.storage.failure**

Logging to storage has failed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.VMSYSLOGD.STORAGE.LOGDIR.INVALID"></a>

• Event **esx.problem.vmsyslogd.storage.logdir.invalid**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VMSYSLOGD.UNEXPECTED"></a>

• Event **esx.problem.vmsyslogd.unexpected**

Log daemon has failed for an unexpected reason

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VPXA.CORE.DUMPED"></a>

• Event **esx.problem.vpxa.core.dumped**

Application crashed and a core file may have been created.

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VSAN.CLUSTERING.DISABLED"></a>

• Event **esx.problem.vsan.clustering.disabled**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="ESX.PROBLEM.VSAN.NET.NOT.READY"></a>

• Event **esx.problem.vsan.net.not.ready**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VSAN.NET.REDUNDANCY.LOST"></a>

• Event **esx.problem.vsan.net.redundancy.lost**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VSAN.NET.REDUNDANCY.REDUCED"></a>

• Event **esx.problem.vsan.net.redundancy.reduced**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VSAN.NO.NETWORK.CONNECTIVITY"></a>

• Event **esx.problem.vsan.no.network.connectivity**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="ESX.PROBLEM.VSAN.VMKNIC.NOT.READY"></a>

• Event **esx.problem.vsan.vmknic.not.ready**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="EXITEDSTANDBYMODEEVENT"></a>

• Event **ExitedStandbyModeEvent**

This event records that the host is no longer in standby mode.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExitedStandbyModeEvent.html)

<a id="EXITINGSTANDBYMODEEVENT"></a>

• Event **ExitingStandbyModeEvent**

This event records that a host has begun the process of exiting standby mode.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExitingStandbyModeEvent.html)

<a id="EXITMAINTENANCEMODEEVENT"></a>

• Event **ExitMaintenanceModeEvent**

This event records that the host is no longer in maintenance mode.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExitMaintenanceModeEvent.html)

<a id="EXITSTANDBYMODEFAILEDEVENT"></a>

• Event **ExitStandbyModeFailedEvent**

This event records that the host failed to exit standby mode.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExitStandbyModeFailedEvent.html)

<a id="FAILOVERLEVELRESTORED"></a>

• Event **FailoverLevelRestored**

This event records that the amount of cluster resources has increased and is now sufficient to satisfy the configured HA failover level.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.FailoverLevelRestored.html)

<a id="GENERALEVENT"></a>

• Event **GeneralEvent**

This is actually the base class for general events and should not be seen. The derived general events are the ones that will be generated. See VMware documentation for the complete list of these events.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GeneralEvent.html)

<a id="GENERALHOSTERROREVENT"></a>

• Event **GeneralHostErrorEvent**

This event is the general error event for a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GeneralHostErrorEvent.html)

<a id="GENERALHOSTINFOEVENT"></a>

• Event **GeneralHostInfoEvent**

This event is the general information event for a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GeneralHostInfoEvent.html)

<a id="GENERALHOSTWARNINGEVENT"></a>

• Event **GeneralHostWarningEvent**

This event is the general warning event for a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GeneralHostWarningEvent.html)

<a id="GENERALUSEREVENT"></a>

• Event **GeneralUserEvent**

This event is the general user event type.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GeneralUserEvent.html)

<a id="GENERALVMERROREVENT"></a>

• Event **GeneralVmErrorEvent**

This event is the general error event for a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GeneralVmErrorEvent.html)

<a id="GENERALVMINFOEVENT"></a>

• Event **GeneralVmInfoEvent**

This event is the general information event for a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GeneralVmInfoEvent.html)

<a id="GENERALVMWARNINGEVENT"></a>

• Event **GeneralVmWarningEvent**

This event is the general warning event for a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GeneralVmWarningEvent.html)

<a id="GHOSTDVSPROXYSWITCHDETECTEDEVENT"></a>

• Event **GhostDvsProxySwitchDetectedEvent**

This event records when vCenter server found DVS proxy switches on the host that don't match any DVS defined in vCenter.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GhostDvsProxySwitchDetectedEvent.html)

<a id="GHOSTDVSPROXYSWITCHREMOVEDEVENT"></a>

• Event **GhostDvsProxySwitchRemovedEvent**

This event records when the ghost DVS proxy switches (a.k.a host proxy switches that don't match any DVS defined in vCenter) were removed on the host.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GhostDvsProxySwitchRemovedEvent.html)

<a id="GLOBALMESSAGECHANGEDEVENT"></a>

• Event **GlobalMessageChangedEvent**

This event records a change to the global message.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.GlobalMessageChangedEvent.html)

<a id="HBR.PRIMARY.APPQUIESCEDDELTACOMPLETEDEVENT"></a>

• Event **hbr.primary.AppQuiescedDeltaCompletedEvent**

Application consistent delta completed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.CONNECTIONRESTOREDTOHBRSERVEREVENT"></a>

• Event **hbr.primary.ConnectionRestoredToHbrServerEvent**

Connection to replication server restored for virtual machine

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="HBR.PRIMARY.DELTAABORTEDEVENT"></a>

• Event **hbr.primary.DeltaAbortedEvent**

Delta aborted for virtual machine

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.DELTACOMPLETEDEVENT"></a>

• Event **hbr.primary.DeltaCompletedEvent**

Delta completed for virtual machine

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.DELTASTARTEDEVENT"></a>

• Event **hbr.primary.DeltaStartedEvent**

Delta for VM started

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="HBR.PRIMARY.FAILEDTOSTARTDELTAEVENT"></a>

• Event **hbr.primary.FailedToStartDeltaEvent**

Failed to start delta for virtual machine

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.FAILEDTOSTARTSYNCEVENT"></a>

• Event **hbr.primary.FailedToStartSyncEvent**

Failed to start full sync for virtual machine

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.FSQUIESCEDDELTACOMPLETEDEVENT"></a>

• Event **hbr.primary.FSQuiescedDeltaCompletedEvent**

File system consistent delta completed for virtual machine

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.INVALIDDISKREPLICATIONCONFIGURATIONEVENT"></a>

• Event **hbr.primary.InvalidDiskReplicationConfigurationEvent**

VM replication configuration is invalid

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.INVALIDVMREPLICATIONCONFIGURATIONEVENT"></a>

• Event **hbr.primary.InvalidVmReplicationConfigurationEvent**

VM replication configuration is invalid

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.NOCONNECTIONTOHBRSERVEREVENT"></a>

• Event **hbr.primary.NoConnectionToHbrServerEvent**

No connection to replication server

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.NOPROGRESSWITHHBRSERVEREVENT"></a>

• Event **hbr.primary.NoProgressWithHbrServerEvent**

Replication server error

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.QUIESCENOTSUPPORTED"></a>

• Event **hbr.primary.QuiesceNotSupported**

Quiescing is not supported for VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="HBR.PRIMARY.SYNCCOMPLETEDEVENT"></a>

• Event **hbr.primary.SyncCompletedEvent**

VM full sync completed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.SYNCSTARTEDEVENT"></a>

• Event **hbr.primary.SyncStartedEvent**

Full sync started for VM

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ExtendedEvent.html)

<a id="HBR.PRIMARY.UNQUIESCEDDELTACOMPLETEDEVENT"></a>

• Event **hbr.primary.UnquiescedDeltaCompletedEvent**

Delta completed for virtual machine

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HBR.PRIMARY.VMREPLICATIONCONFIGURATIONCHANGEDEVENT"></a>

• Event **hbr.primary.VmReplicationConfigurationChangedEvent**

VM replication configuration changed

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="HEALTHSTATUSCHANGEDEVENT"></a>

• Event **HealthStatusChangedEvent**

Event used to report change in health status of vCenter components.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HealthStatusChangedEvent.html)

<a id="HOSTADDEDEVENT"></a>

• Event **HostAddedEvent**

This event records the addition of a host to vCenter.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostAddedEvent.html)

<a id="HOSTADDFAILEDEVENT"></a>

• Event **HostAddFailedEvent**

This event records that adding a host failed.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostAddFailedEvent.html)

<a id="HOSTADMINDISABLEEVENT"></a>

• Event **HostAdminDisableEvent**

This event records that the permission on the host has been changed such that only the user account used for vCenter operation will have Administrator permission.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostAdminDisableEvent.html)

<a id="HOSTADMINENABLEEVENT"></a>

• Event **HostAdminEnableEvent**

This event records that the administrator permission has been restored.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostAdminEnableEvent.html)

<a id="HOSTCNXFAILEDACCOUNTFAILEDEVENT"></a>

• Event **HostCnxFailedAccountFailedEvent**

This event records a failure to connect to a host due to a failure to set up a management account.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedAccountFailedEvent.html)

<a id="HOSTCNXFAILEDALREADYMANAGEDEVENT"></a>

• Event **HostCnxFailedAlreadyManagedEvent**

This event records a failure to connect to a host due to the host being managed by a different vCenter server.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedAlreadyManagedEvent.html)

<a id="HOSTCNXFAILEDBADCCAGENTEVENT"></a>

• Event **HostCnxFailedBadCcagentEvent**

This event records a failure to connect to a host due to no response being received from the host agent.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedBadCcagentEvent.html)

<a id="HOSTCNXFAILEDBADUSERNAMEEVENT"></a>

• Event **HostCnxFailedBadUsernameEvent**

This event records a failure to connect to a host due to an invalid user name and password combination.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedBadUsernameEvent.html)

<a id="HOSTCNXFAILEDBADVERSIONEVENT"></a>

• Event **HostCnxFailedBadVersionEvent**

This event records a failure to connect to a host due to an incompatible client version.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedBadVersionEvent.html)

<a id="HOSTCNXFAILEDCCAGENTUPGRADEEVENT"></a>

• Event **HostCnxFailedCcagentUpgradeEvent**

This event records a failure to connect to a host due to a conflict with an upgrade or installation of the host agent.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedCcagentUpgradeEvent.html)

<a id="HOSTCNXFAILEDEVENT"></a>

• Event **HostCnxFailedEvent**

This event records a failure to connect to a host due to an unspecified condition.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedEvent.html)

<a id="HOSTCNXFAILEDNETWORKERROREVENT"></a>

• Event **HostCnxFailedNetworkErrorEvent**

This event records a failure to connect to a host due to a network error.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedNetworkErrorEvent.html)

<a id="HOSTCNXFAILEDNOACCESSEVENT"></a>

• Event **HostCnxFailedNoAccessEvent**

This event records a failure to connect to a host due to insufficient account privileges.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedNoAccessEvent.html)

<a id="HOSTCNXFAILEDNOCONNECTIONEVENT"></a>

• Event **HostCnxFailedNoConnectionEvent**

This event records a failure to connect to a host due to a host not being present on the network.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedNoConnectionEvent.html)

<a id="HOSTCNXFAILEDNOLICENSEEVENT"></a>

• Event **HostCnxFailedNoLicenseEvent**

This event records a failure to connect to a host due to a licensing issue.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedNoLicenseEvent.html)

<a id="HOSTCNXFAILEDNOTFOUNDEVENT"></a>

• Event **HostCnxFailedNotFoundEvent**

This event records a failure to connect to a host due to a failure to resolve the host name.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedNotFoundEvent.html)

<a id="HOSTCNXFAILEDTIMEOUTEVENT"></a>

• Event **HostCnxFailedTimeoutEvent**

This event records a failure to connect to a host due to a timeout on the connection attempt.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCnxFailedTimeoutEvent.html)

<a id="HOSTCOMPLIANCECHECKEDEVENT"></a>

• Event **HostComplianceCheckedEvent**

This event records that a compliance check was triggered on the host.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostComplianceCheckedEvent.html)

<a id="HOSTCOMPLIANTEVENT"></a>

• Event **HostCompliantEvent**

This event records that host is in compliance.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostCompliantEvent.html)

<a id="HOSTCONFIGAPPLIEDEVENT"></a>

• Event **HostConfigAppliedEvent**

This event records that a configuration was applied on a host.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostConfigAppliedEvent.html)

<a id="HOSTCONNECTEDEVENT"></a>

• Event **HostConnectedEvent**

This event records a successful host connection. After this event is generated, there will also be a [VmConnectedEvent](#VMCONNECTEDEVENT) generated for each VM on the host, regardless of the VM power state.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostConnectedEvent.html)

<a id="HOSTCONNECTIONLOSTEVENT"></a>

• Event **HostConnectionLostEvent**

This event records the (unexpected) loss of a host connection. This may occur if a ESX system was powered down, for example. After this event is generated, there will also be a [VmDisconnectedEvent](#VMDISCONNECTEDEVENT) generated for each VM on the host, regardless of the VM power state.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostConnectionLostEvent.html)

<a id="HOSTDASDISABLEDEVENT"></a>

• Event **HostDasDisabledEvent**

This event records when HA has been disabled on a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostDasDisabledEvent.html)

<a id="HOSTDASDISABLINGEVENT"></a>

• Event **HostDasDisablingEvent**

This event records when HA is being disabled on a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostDasDisablingEvent.html)

<a id="HOSTDASENABLEDEVENT"></a>

• Event **HostDasEnabledEvent**

This event records when HA has been enabled on a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostDasEnabledEvent.html)

<a id="HOSTDASENABLINGEVENT"></a>

• Event **HostDasEnablingEvent**

This event records when HA has been enabled on a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostDasEnablingEvent.html)

<a id="HOSTDASERROREVENT"></a>

• Event **HostDasErrorEvent**

This event records when there is a HA error on a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostDasErrorEvent.html)

<a id="HOSTDASOKEVENT"></a>

• Event **HostDasOkEvent**

This event records when HA on a host returns to normal after an error.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostDasOkEvent.html)

<a id="HOSTDISCONNECTEDEVENT"></a>

• Event **HostDisconnectedEvent**

This event records the completion of a user requested disconnect of a host. Following this event, there will be a [VmDisconnectedEvent](#VMDISCONNECTEDEVENT) generated for each VM on the host, regardless of the VM power state.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostDisconnectedEvent.html)

<a id="HOSTDVPORTEVENT"></a>

• Event **HostDVPortEvent**

dvPort connected to host changed status

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/)

<a id="HOSTENABLEADMINFAILEDEVENT"></a>

• Event **HostEnableAdminFailedEvent**

This event records the failure to restore some of the administrator's permissions.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostEnableAdminFailedEvent.html)

<a id="HOSTEXTRANETWORKSEVENT"></a>

• Event **HostExtraNetworksEvent**

This event records the fact that a host has extra networks not used by other hosts for HA communication.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostExtraNetworksEvent.html)

<a id="HOSTGETSHORTNAMEFAILEDEVENT"></a>

• Event **HostGetShortNameFailedEvent**

This event records that hostname -s failed or returned a name containing '.'.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostGetShortNameFailedEvent.html)

<a id="HOSTINAUDITMODEEVENT"></a>

• Event **HostInAuditModeEvent**

Host is running in audit mode

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostInAuditModeEvent.html)

<a id="HOSTINVENTORYFULLEVENT"></a>

• Event **HostInventoryFullEvent**

This event records if the inventory of hosts has reached the capacity of the current version of vCenter.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostInventoryFullEvent.html)

<a id="HOSTINVENTORYUNREADABLEEVENT"></a>

• Event **HostInventoryUnreadableEvent**

Event indicating that the virtual machine inventory file on the host is damaged or unreadable.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostInventoryUnreadableEvent.html)

<a id="HOSTIPCHANGEDEVENT"></a>

• Event **HostIpChangedEvent**

This event records a change in host IP address.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostIpChangedEvent.html)

<a id="HOSTIPINCONSISTENTEVENT"></a>

• Event **HostIpInconsistentEvent**

This event records that the IP address resolution returned different addresses on the host. Check your host network configuration.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostIpInconsistentEvent.html)

<a id="HOSTIPTOSHORTNAMEFAILEDEVENT"></a>

• Event **HostIpToShortNameFailedEvent**

This event records that the host IP address could not be resolved to a short name.

Since VI API 2. . For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostIpToShortNameFailedEvent.html)

<a id="HOSTISOLATIONIPPINGFAILEDEVENT"></a>

• Event **HostIsolationIpPingFailedEvent**

This event records that the isolation address could not be pinged. The default isolation address is the service console default gateway.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostIsolationIpPingFailedEvent.html)

<a id="HOSTLICENSEEXPIREDEVENT"></a>

• Event **HostLicenseExpiredEvent**

This event records an expired host license.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostLicenseExpiredEvent.html)

<a id="HOSTLOCALPORTCREATEDEVENT"></a>

• Event **HostLocalPortCreatedEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostLocalPortCreatedEvent.html)

<a id="HOSTMISSINGNETWORKSEVENT"></a>

• Event **HostMissingNetworksEvent**

This event records the fact that a host is missing networks that other hosts are using for HA communication.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostMissingNetworksEvent.html)

<a id="HOSTMONITORINGSTATECHANGEDEVENT"></a>

• Event **HostMonitoringStateChangedEvent**

This event records when host monitoring state has changed.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostMonitoringStateChangedEvent.html)

<a id="HOSTNOAVAILABLENETWORKSEVENT"></a>

• Event **HostNoAvailableNetworksEvent**

This event records the fact that a host does not have any available networks for HA communication.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostNoAvailableNetworksEvent.html)

<a id="HOSTNOHAENABLEDPORTGROUPSEVENT"></a>

• Event **HostNoHAEnabledPortGroupsEvent**

This event records the fact that a host does not have any HA-enabled port groups.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostNoHAEnabledPortGroupsEvent.html)

<a id="HOSTNONCOMPLIANTEVENT"></a>

• Event **HostNonCompliantEvent**

This event records that host went out of compliance.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostNonCompliantEvent.html)

<a id="HOSTNOREDUNDANTMANAGEMENTNETWORKEVENT"></a>

• Event **HostNoRedundantManagementNetworkEvent**

This event records the fact that a host does not have a redundant management network. It is recommended that host management networks be configured with redundancy.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostNoRedundantManagementNetworkEvent.html)

<a id="HOSTNOTINCLUSTEREVENT"></a>

• Event **HostNotInClusterEvent**

This event records that the host is not a cluster member.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostNotInClusterEvent.html)

<a id="HOSTOVERCOMMITTEDEVENT"></a>

• Event **HostOvercommittedEvent**

This event records when a host capacity cannot satisfy resource configuration constraints.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostOvercommittedEvent.html)

<a id="HOSTPRIMARYAGENTNOTSHORTNAMEEVENT"></a>

• Event **HostPrimaryAgentNotShortNameEvent**

This event records that the primary agent specified is not a short name. The name of the primary agent is usually stored as a short name. You should not normally see this error. Check the network configurations of your hosts.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostPrimaryAgentNotShortNameEvent.html)

<a id="HOSTPROFILEAPPLIEDEVENT"></a>

• Event **HostProfileAppliedEvent**

This event records that a Profile application was done on the host.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostProfileAppliedEvent.html)

<a id="HOSTRECONNECTIONFAILEDEVENT"></a>

• Event **HostReconnectionFailedEvent**

This event records a failed attempt to re-establish a host connection.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostReconnectionFailedEvent.html)

<a id="HOSTREMOVEDEVENT"></a>

• Event **HostRemovedEvent**

This event records the removal of a host from vCenter.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostRemovedEvent.html)

<a id="HOSTSHORTNAMEINCONSISTENTEVENT"></a>

• Event **HostShortNameInconsistentEvent**

This event records that host name resolution returned different names on the host. Check your host network configuration and your DNS configuration. There may be duplicate entries.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostShortNameInconsistentEvent.html)

<a id="HOSTSHORTNAMETOIPFAILEDEVENT"></a>

• Event **HostShortNameToIpFailedEvent**

This event records that host name resolution returned different names on the host. Check your host network configuration and your DNS configuration. There may be duplicate entries.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostShortNameToIpFailedEvent.html)

<a id="HOSTSHUTDOWNEVENT"></a>

• Event **HostShutdownEvent**

This event records the shutdown of a host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostShutdownEvent.html)

<a id="HOSTSTATUSCHANGEDEVENT"></a>

• Event **HostStatusChangedEvent**

This event records when a host overall status changed.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostStatusChangedEvent.html)

<a id="HOSTSYNCFAILEDEVENT"></a>

• Event **HostSyncFailedEvent**

This event records a failure to sync up with the vCenter agent on the host.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostSyncFailedEvent.html)

<a id="HOSTUPGRADEFAILEDEVENT"></a>

• Event **HostUpgradeFailedEvent**

This event records a failure to connect to a host due to an installation or upgrade issue.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostUpgradeFailedEvent.html)

<a id="HOSTUSERWORLDSWAPNOTENABLEDEVENT"></a>

• Event **HostUserWorldSwapNotEnabledEvent**

This event records that the userworld swap is not enabled on the host. HA needs userworld swap to be configured on embedded ESX hosts to function.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostUserWorldSwapNotEnabledEvent.html)

<a id="HOSTVNICCONNECTEDTOCUSTOMIZEDDVPORTEVENT"></a>

• Event **HostVnicConnectedToCustomizedDVPortEvent**

This event records when some host vnics were reconfigured to use DVPorts with port level configuration, which may be different from the DVportgroup.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostVnicConnectedToCustomizedDVPortEvent.html)

<a id="HOSTWWNCHANGEDEVENT"></a>

• Event **HostWwnChangedEvent**

This event records a change in a host WWN (World Wide Name).

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostWwnChangedEvent.html)

<a id="HOSTWWNCONFLICTEVENT"></a>

• Event **HostWwnConflictEvent**

This event records a conflict of host WWNs (World Wide Name).

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.HostWwnConflictEvent.html)

<a id="INCORRECTHOSTINFORMATIONEVENT"></a>

• Event **IncorrectHostInformationEvent**

This event records if the host did not provide the information needed to acquire the correct set of licenses.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.IncorrectHostInformationEvent.html)

<a id="INFOUPGRADEEVENT"></a>

• Event **InfoUpgradeEvent**

This event is a general information event from upgrade.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.InfoUpgradeEvent.html)

<a id="INSUFFICIENTFAILOVERRESOURCESEVENT"></a>

• Event **InsufficientFailoverResourcesEvent**

This event records that the cluster resources are insufficient to satisfy the configured HA failover level.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.InsufficientFailoverResourcesEvent.html)

<a id="INVALIDEDITIONEVENT"></a>

• Event **InvalidEditionEvent**

This event records if the license edition is set to an invalid value.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.InvalidEditionEvent.html)

<a id="ISCSIBOOTFAILUREEVENT"></a>

• Event **IScsiBootFailureEvent**

Could not boot from iScsi

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.iScsiBootFailureEvent.html)

<a id="LICENSEEXPIREDEVENT"></a>

• Event **LicenseExpiredEvent**

This event records the expiration of a license.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.LicenseExpiredEvent.html)

<a id="LICENSENONCOMPLIANCEEVENT"></a>

• Event **LicenseNonComplianceEvent**

This event records that the inventory is not license compliant.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.LicenseNonComplianceEvent.html)

<a id="LICENSERESTRICTEDEVENT"></a>

• Event **LicenseRestrictedEvent**

This event records if the required licenses could not be reserved because of a restriction in the option file.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.LicenseRestrictedEvent.html)

<a id="LICENSESERVERAVAILABLEEVENT"></a>

• Event **LicenseServerAvailableEvent**

This event is reported if the LicenseServer was previously unreachable and is now reachable.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.LicenseServerAvailableEvent.html)

<a id="LICENSESERVERUNAVAILABLEEVENT"></a>

• Event **LicenseServerUnavailableEvent**

This event is reported if the LicenseServer becomes unreachable.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.LicenseServerUnavailableEvent.html)

<a id="LOCALDATASTORECREATEDEVENT"></a>

• Event **LocalDatastoreCreatedEvent**

This event records when a local datastore is created.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.LocalDatastoreCreatedEvent.html)

<a id="LOCALTSMENABLEDEVENT"></a>

• Event **LocalTSMEnabledEvent**

Local Tech Support Mode for the host has been enabled

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.LocalTSMEnabledEvent.html)

<a id="LOCKERMISCONFIGUREDEVENT"></a>

• Event **LockerMisconfiguredEvent**

Locker has not been configured properly. This event is fired when the datastore configured to back the locker does not exist or when connectivity to the datastore is lost.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.LockerMisconfiguredEvent.html)

<a id="LOCKERRECONFIGUREDEVENT"></a>

• Event **LockerReconfiguredEvent**

Locker has not been configured properly. This event is fired when the datastore configured to back the locker does not exist or when connectivity to the datastore is lost.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.LockerReconfiguredEvent.html)

<a id="MIGRATIONERROREVENT"></a>

• Event **MigrationErrorEvent**

A migration error occurred.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.MigrationErrorEvent.html)

<a id="MIGRATIONHOSTERROREVENT"></a>

• Event **MigrationHostErrorEvent**

This records a migration error that includes the destination host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.MigrationHostErrorEvent.html)

<a id="MIGRATIONHOSTWARNINGEVENT"></a>

• Event **MigrationHostWarningEvent**

This records a migration warning that includes the destination host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.MigrationHostWarningEvent.html)

<a id="MIGRATIONRESOURCEERROREVENT"></a>

• Event **MigrationResourceErrorEvent**

This records a migration error that includes both the destination host and resource pool.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.MigrationResourceErrorEvent.html)

<a id="MIGRATIONRESOURCEWARNINGEVENT"></a>

• Event **MigrationResourceWarningEvent**

This records a migration warning that includes both the destination host and resource pool.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.MigrationResourceWarningEvent.html)

<a id="MIGRATIONWARNINGEVENT"></a>

• Event **MigrationWarningEvent**

This records a migration warning.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.MigrationWarningEvent.html)

<a id="MTUMATCHEVENT"></a>

• Event **MtuMatchEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.MtuMatchEvent.html)

<a id="MTUMISMATCHEVENT"></a>

• Event **MtuMismatchEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.MtuMismatchEvent.html)

<a id="NASDATASTORECREATEDEVENT"></a>

• Event **NASDatastoreCreatedEvent**

This event records when a NAS datastore is created.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.NASDatastoreCreatedEvent.html)

<a id="NETWORKROLLBACKEVENT"></a>

• Event **NetworkRollbackEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.NetworkRollbackEvent.html)

<a id="NOACCESSUSEREVENT"></a>

• Event **NoAccessUserEvent**

This event records a failed user logon due to insufficient access permission.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.NoAccessUserEvent.html)

<a id="NODATASTORESCONFIGUREDEVENT"></a>

• Event **NoDatastoresConfiguredEvent**

No datastores have been configured on the host.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.NoDatastoresConfiguredEvent.html)

<a id="NOLICENSEEVENT"></a>

• Event **NoLicenseEvent**

A NoLicenseEvent is reported if the required licenses could not be reserved. Each feature that is not fully licensed is reported.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.NoLicenseEvent.html)

<a id="NOMAINTENANCEMODEDRSRECOMMENDATIONFORVM"></a>

• Event **NoMaintenanceModeDrsRecommendationForVM**

This event records that DRS did not recommend a migration for a powered on virtual machine, even though its host is going into maintenance mode. DRS may not be able to recommend a migration for a virtual machine for reasons, include but not limited to:

- No other connected host is compatible with this virtual machine.
- None of the other compatible hosts have sufficient resources to satisfy the reservation requirements of this virtual machine.
- Moving to any other host may violate a DRS rule. For example, all other compatible hosts have some incompatible virtual machines running.
- DRS is disabled on this virtual machine.
- This virtual machine was still in the process of migrating into the host going into maintenance mode and was not considered by DRS.
- This virtual machine was in the process of migrating to another host when the host tried to enter maintenance mode.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.NoMaintenanceModeDrsRecommendationForVM.html)

<a id="NONVIWORKLOADDETECTEDONDATASTOREEVENT"></a>

• Event **NonVIWorkloadDetectedOnDatastoreEvent**

This event records that non-VI workload is detected on the datastore

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.NonVIWorkloadDetectedOnDatastoreEvent.html)

<a id="NOTENOUGHRESOURCESTOSTARTVMEVENT"></a>

• Event **NotEnoughResourcesToStartVmEvent**

This event records when the HA does not find sufficient resources to failover a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.NotEnoughResourcesToStartVmEvent.html)

<a id="OUTOFSYNCDVSHOST"></a>

• Event **OutOfSyncDvsHost**

The list of hosts that have the DVS configuration on the host diverged from that of the vCenter Server.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.OutOfSyncDvsHost.html)

<a id="PERMISSIONADDEDEVENT"></a>

• Event **PermissionAddedEvent**

This event records the creation of a permission.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.PermissionAddedEvent.html)

<a id="PERMISSIONREMOVEDEVENT"></a>

• Event **PermissionRemovedEvent**

This event records the removal of a permission.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.PermissionRemovedEvent.html)

<a id="PERMISSIONUPDATEDEVENT"></a>

• Event **PermissionUpdatedEvent**

This event records the update of a permission.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.PermissionUpdatedEvent.html)

<a id="PROFILEASSOCIATEDEVENT"></a>

• Event **ProfileAssociatedEvent**

This event records that a Profile was associated with a managed entity.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ProfileAssociatedEvent.html)

<a id="PROFILECHANGEDEVENT"></a>

• Event **ProfileChangedEvent**

This event records that the profile has been edited.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ProfileChangedEvent.html)

<a id="PROFILECREATEDEVENT"></a>

• Event **ProfileCreatedEvent**

This event records that a Profile was created.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ProfileCreatedEvent.html)

<a id="PROFILEDISSOCIATEDEVENT"></a>

• Event **ProfileDissociatedEvent**

This event records that a Profile was disassociated from a managed entity.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ProfileDissociatedEvent.html)

<a id="PROFILEEVENT"></a>

• Event **ProfileEvent**

This event records a Profile specific event.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ProfileEvent.html)

<a id="PROFILEREFERENCEHOSTCHANGEDEVENT"></a>

• Event **ProfileReferenceHostChangedEvent**

This event records that the reference host associated with this profile has changed.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ProfileReferenceHostChangedEvent.html)

<a id="PROFILEREMOVEDEVENT"></a>

• Event **ProfileRemovedEvent**

This event records that a Profile was removed.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ProfileRemovedEvent.html)

<a id="RECOVERYEVENT"></a>

• Event **RecoveryEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.RecoveryEvent.html)

<a id="REMOTETSMENABLEDEVENT"></a>

• Event **RemoteTSMEnabledEvent**

Remote Tech Support Mode for the host has been enabled

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.RemoteTSMEnabledEvent.html)

<a id="RESOURCEPOOLCREATEDEVENT"></a>

• Event **ResourcePoolCreatedEvent**

This event records when a new resource pool is created.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ResourcePoolCreatedEvent.html)

<a id="RESOURCEPOOLDESTROYEDEVENT"></a>

• Event **ResourcePoolDestroyedEvent**

This event records when a resource pool is destroyed.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ResourcePoolDestroyedEvent.html)

<a id="RESOURCEPOOLMOVEDEVENT"></a>

• Event **ResourcePoolMovedEvent**

This event records when a resource pool is moved.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ResourcePoolMovedEvent.html)

<a id="RESOURCEPOOLRECONFIGUREDEVENT"></a>

• Event **ResourcePoolReconfiguredEvent**

This event records when a resource pool configuration is changed.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ResourcePoolReconfiguredEvent.html)

<a id="RESOURCEVIOLATEDEVENT"></a>

• Event **ResourceViolatedEvent**

This event records when a conflict with a resource pool resource configuration is detected.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ResourceViolatedEvent.html)

<a id="ROLEADDEDEVENT"></a>

• Event **RoleAddedEvent**

This event records the creation of a role.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.RoleAddedEvent.html)

<a id="ROLEREMOVEDEVENT"></a>

• Event **RoleRemovedEvent**

This class records the removal of a role.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.RoleRemovedEvent.html)

<a id="ROLEUPDATEDEVENT"></a>

• Event **RoleUpdatedEvent**

This event records the creation of a role.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.RoleUpdatedEvent.html)

<a id="ROLLBACKEVENT"></a>

• Event **RollbackEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.RollbackEvent.html)

<a id="SCHEDULEDTASKCOMPLETEDEVENT"></a>

• Event **ScheduledTaskCompletedEvent**

This event records the completion of a scheduled task.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ScheduledTaskCompletedEvent.html)

<a id="SCHEDULEDTASKCREATEDEVENT"></a>

• Event **ScheduledTaskCreatedEvent**

This event records the creation of a scheduled task.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ScheduledTaskCreatedEvent.html)

<a id="SCHEDULEDTASKEMAILCOMPLETEDEVENT"></a>

• Event **ScheduledTaskEmailCompletedEvent**

This event records the sending of a notification through email for a scheduled task.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ScheduledTaskEmailCompletedEvent.html)

<a id="SCHEDULEDTASKEMAILFAILEDEVENT"></a>

• Event **ScheduledTaskEmailFailedEvent**

This event records the failure of an attempt to send a notification through email for a scheduled task.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ScheduledTaskEmailFailedEvent.html)

<a id="SCHEDULEDTASKEVENT"></a>

• Event **ScheduledTaskEvent**

This event records the completion of a scheduled task. The name of the task is indicated.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ScheduledTaskEvent.html)

<a id="SCHEDULEDTASKFAILEDEVENT"></a>

• Event **ScheduledTaskFailedEvent**

This event records the failure of a scheduled task.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ScheduledTaskFailedEvent.html)

<a id="SCHEDULEDTASKRECONFIGUREDEVENT"></a>

• Event **ScheduledTaskReconfiguredEvent**

This event records the reconfiguration of a scheduled task.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ScheduledTaskReconfiguredEvent.html)

<a id="SCHEDULEDTASKREMOVEDEVENT"></a>

• Event **ScheduledTaskRemovedEvent**

This event records the removal of a scheduled task.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ScheduledTaskRemovedEvent.html)

<a id="SCHEDULEDTASKSTARTEDEVENT"></a>

• Event **ScheduledTaskStartedEvent**

This event records when a scheduled task started.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ScheduledTaskStartedEvent.html)

<a id="SERVERLICENSEEXPIREDEVENT"></a>

• Event **ServerLicenseExpiredEvent**

This event records an expired vCenter server license.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ServerLicenseExpiredEvent.html)

<a id="SERVERSTARTEDSESSIONEVENT"></a>

• Event **ServerStartedSessionEvent**

This event records the starting of the vCenter server.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.ServerStartedSessionEvent.html)

<a id="SESSIONTERMINATEDEVENT"></a>

• Event **SessionTerminatedEvent**

This event records the termination of a session.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.SessionTerminatedEvent.html)

<a id="TASKEVENT"></a>

• Event **TaskEvent**

This event records the completion of a manually triggered task. The name of the task is indicated.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.TaskEvent.html)

<a id="TASKTIMEOUTEVENT"></a>

• Event **TaskTimeoutEvent**

This event records when a task is cleaned up because of a timeout.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.TaskTimeoutEvent.html)

<a id="TEAMINGMATCHEVENT"></a>

• Event **TeamingMatchEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.TeamingMatchEvent.html)

<a id="TEAMINGMISMATCHEVENT"></a>

• Event **TeamingMisMatchEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.TeamingMisMatchEvent.html)

<a id="TEMPLATEBEINGUPGRADEDEVENT"></a>

• Event **TemplateBeingUpgradedEvent**

This event records the start of a template upgrade.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.TemplateBeingUpgradedEvent.html)

<a id="TEMPLATEUPGRADEDEVENT"></a>

• Event **TemplateUpgradedEvent**

This event records that the template upgrade succeeded.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.TemplateUpgradedEvent.html)

<a id="TEMPLATEUPGRADEFAILEDEVENT"></a>

• Event **TemplateUpgradeFailedEvent**

This event records that the template upgrade failed.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.TemplateUpgradeFailedEvent.html)

<a id="TIMEDOUTHOSTOPERATIONEVENT"></a>

• Event **TimedOutHostOperationEvent**

This event indicates that an operation performed on the host timed out. Typically, a previous event in the sequence of events contains more information about the cause of the operation timing out.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.TimedOutHostOperationEvent.html)

<a id="UNLICENSEDVIRTUALMACHINESEVENT"></a>

• Event **UnlicensedVirtualMachinesEvent**

This event records that we have unlicensed virtual machines on the specified host. This can be both a Config issue and an entry in the event log.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UnlicensedVirtualMachinesEvent.html)

<a id="UNLICENSEDVIRTUALMACHINESFOUNDEVENT"></a>

• Event **UnlicensedVirtualMachinesFoundEvent**

This event records that we discovered unlicensed virtual machines on the specified host. After this event is entered into the event log, we expect to see an UnlicensedVirtualMachinesEvent configIssue on the host.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UnlicensedVirtualMachinesFoundEvent.html)

<a id="UPDATEDAGENTBEINGRESTARTEDEVENT"></a>

• Event **UpdatedAgentBeingRestartedEvent**

This event records that the agent has been patched and will be restarted.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UpdatedAgentBeingRestartedEvent.html)

<a id="UPGRADEEVENT"></a>

• Event **UpgradeEvent**

This event records that the agent has been patched and will be restarted.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UpdatedAgentBeingRestartedEvent.html)

<a id="UPLINKPORTMTUNOTSUPPORTEVENT"></a>

• Event **UplinkPortMtuNotSupportEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UplinkPortMtuNotSupportEvent.html)

<a id="UPLINKPORTMTUSUPPORTEVENT"></a>

• Event **UplinkPortMtuSupportEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UplinkPortMtuSupportEvent.html)

<a id="UPLINKPORTVLANTRUNKEDEVENT"></a>

• Event **UplinkPortVlanTrunkedEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UplinkPortVlanTrunkedEvent.html)

<a id="UPLINKPORTVLANUNTRUNKEDEVENT"></a>

• Event **UplinkPortVlanUntrunkedEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UplinkPortVlanUntrunkedEvent.html)

<a id="USERASSIGNEDTOGROUP"></a>

• Event **UserAssignedToGroup**

This event records that a user account membership was added to a group.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UserAssignedToGroup.html)

<a id="USERLOGINSESSIONEVENT"></a>

• Event **UserLoginSessionEvent**

This event records a user logon. Because these are so prolific, they are ignored (by default) by the Veeam VMware Collector.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UserLoginSessionEvent.html)

<a id="USERLOGOUTSESSIONEVENT"></a>

• Event **UserLogoutSessionEvent**

This event records a user logout. Because these are so numerous, they are ignored (by default) by the Veeam VMware Collector.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UserLogoutSessionEvent.html)

<a id="USERPASSWORDCHANGED"></a>

• Event **UserPasswordChanged**

This event records that a user password changed.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UserPasswordChanged.html)

<a id="USERUNASSIGNEDFROMGROUP"></a>

• Event **UserUnassignedFromGroup**

This event records that a user account membership was removed from a group.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UserUnassignedFromGroup.html)

<a id="USERUPGRADEEVENT"></a>

• Event **UserUpgradeEvent**

This event is a general user event from upgrade.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.UserUpgradeEvent.html)

<a id="VCAGENTUNINSTALLEDEVENT"></a>

• Event **VcAgentUninstalledEvent**

This event records when the vCenter agent on a host is uninstalled.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VcAgentUninstalledEvent.html)

<a id="VCAGENTUNINSTALLFAILEDEVENT"></a>

• Event **VcAgentUninstallFailedEvent**

This event records when the vCenter agent on a host failed to uninstall.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VcAgentUninstallFailedEvent.html)

<a id="VCAGENTUPGRADEDEVENT"></a>

• Event **VcAgentUpgradedEvent**

This event records when the vCenter agent on a host upgraded.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VcAgentUpgradedEvent.html)

<a id="VCAGENTUPGRADEFAILEDEVENT"></a>

• Event **VcAgentUpgradeFailedEvent**

This event records when the vCenter agent on a host failed to upgrade.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VcAgentUpgradeFailedEvent.html)

<a id="VIM.EVENT.LICENSEDOWNGRADEDEVENT"></a>

• Event **vim.event.LicenseDowngradedEvent**

License downgrade

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VIMACCOUNTPASSWORDCHANGEDEVENT"></a>

• Event **VimAccountPasswordChangedEvent**

Password for the Vim account user on the host has been changed. This is an account created by vCenter and used to manage the host.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VimAccountPasswordChangedEvent.html)

<a id="VMACQUIREDMKSTICKETEVENT"></a>

• Event **VmAcquiredMksTicketEvent**

This event records a user successfully acquiring an MKS ticket (for example, a mouse-keyboard-screen connection ticket).

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmAcquiredMksTicketEvent.html)

<a id="VMACQUIREDTICKETEVENT"></a>

• Event **VmAcquiredTicketEvent**

This event records a user successfully acquiring a ticket

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.VmAcquiredTicketEvent.html)

<a id="VMAUTORENAMEEVENT"></a>

• Event **VmAutoRenameEvent**

This event records that a virtual machine was automatically renamed because of a name conflict.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmAutoRenameEvent.html)

<a id="VMBEINGCLONEDEVENT"></a>

• Event **VmBeingClonedEvent**

This event records a virtual machine being cloned.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmBeingClonedEvent.html)

<a id="VMBEINGCLONEDNOFOLDEREVENT"></a>

• Event **VmBeingClonedNoFolderEvent**

This event records a virtual machine being cloned

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.VmBeingClonedNoFolderEvent.html)

<a id="VMBEINGCREATEDEVENT"></a>

• Event **VmBeingCreatedEvent**

This event records a virtual machine being created.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmBeingCreatedEvent.html)

<a id="VMBEINGDEPLOYEDEVENT"></a>

• Event **VmBeingDeployedEvent**

This event records a virtual machine being deployed from a template.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmBeingDeployedEvent.html)

<a id="VMBEINGHOTMIGRATEDEVENT"></a>

• Event **VmBeingHotMigratedEvent**

This event records that a virtual machine is being hot-migrated.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmBeingHotMigratedEvent.html)

<a id="VMBEINGMIGRATEDEVENT"></a>

• Event **VmBeingMigratedEvent**

This event records that a virtual machine is being migrated.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmBeingMigratedEvent.html)

<a id="VMBEINGRELOCATEDEVENT"></a>

• Event **VmBeingRelocatedEvent**

This event records that a virtual machine is being relocated.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmBeingRelocatedEvent.html)

<a id="VMCLONEDEVENT"></a>

• Event **VmClonedEvent**

This event records the completion of a virtual machine cloning operation.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmClonedEvent.html)

<a id="VMCLONEFAILEDEVENT"></a>

• Event **VmCloneFailedEvent**

This event records a failure to clone a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmCloneFailedEvent.html)

<a id="VMCONFIGMISSINGEVENT"></a>

• Event **VmConfigMissingEvent**

This event records if the configuration file cannot be found.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmConfigMissingEvent.html)

<a id="VMCONNECTEDEVENT"></a>

• Event **VmConnectedEvent**

This event is generated by the VC for each VM on a host whenever the host is reconnected to the VC. One event per VM will be generated, regardless of the power state of the VM.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmConnectedEvent.html)

<a id="VMCREATEDEVENT"></a>

• Event **VmCreatedEvent**

This event records that a virtual machine was successfully created.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmCreatedEvent.html)

<a id="VMDASBEINGRESETEVENT"></a>

• Event **VmDasBeingResetEvent**

This event records when a virtual machine is reset by HA VM Health Monitoring on hosts that do not support the create screenshot api or if the createscreenshot api fails.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDasBeingResetEvent.html)

<a id="VMDASBEINGRESETWITHSCREENSHOTEVENT"></a>

• Event **VmDasBeingResetWithScreenshotEvent**

This event records when a virtual machine is reset by HA VM Health Monitoring on hosts that support the create screenshot api.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDasBeingResetWithScreenshotEvent.html)

<a id="VMDASRESETFAILEDEVENT"></a>

• Event **VmDasResetFailedEvent**

This event records when HA VM Health Monitoring fails to reset a virtual machine after failure.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDasResetFailedEvent.html)

<a id="VMDASUPDATEERROREVENT"></a>

• Event **VmDasUpdateErrorEvent**

The event records that an error occurred when updating the HA agents with the current state of the virtual machine. If this occurs during a powerOn operation, the virtual machine will not be failed over in the event of a host failure. If it occurs during a powerOff, the virtual machine will be automatically powered on if the host it was last running on crashes.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDasUpdateErrorEvent.html)

<a id="VMDASUPDATEOKEVENT"></a>

• Event **VmDasUpdateOkEvent**

This event records that HA agents have been updated with the current state of the virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDasUpdateOkEvent.html)

<a id="VMDATEROLLEDBACKEVENT"></a>

• Event **VmDateRolledBackEvent**

This event records when the vCenter server date rolled back.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDateRolledBackEvent.html)

<a id="VMDEPLOYEDEVENT"></a>

• Event **VmDeployedEvent**

This event records the completion of a virtual machine deployment operation.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDeployedEvent.html)

<a id="VMDEPLOYFAILEDEVENT"></a>

• Event **VmDeployFailedEvent**

This event records a failure to deploy from a template.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDeployFailedEvent.html)

<a id="VMDISCONNECTEDEVENT"></a>

• Event **VmDisconnectedEvent**

This event is generated by the VC for each VM on a host whenever the host becomes disconnected from the VC. One event per VM will be generated, regardless of the power state of the VM.

"Disconnection" of the host includes both planned disconnections (indicated by [HostDisconnectedEvent](#HOSTDISCONNECTEDEVENT)) and unplanned disconnections (indicated by [HostConnectionLostEvent](#HOSTCONNECTIONLOSTEVENT)).

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDisconnectedEvent.html)

<a id="VMDISCOVEREDEVENT"></a>

• Event **VmDiscoveredEvent**

This event records a virtual machine discovery.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDiscoveredEvent.html)

<a id="VMDISKFAILEDEVENT"></a>

• Event **VmDiskFailedEvent**

This event records a failure to create a virtual disk in a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmDiskFailedEvent.html)

<a id="VMDVPORTEVENT"></a>

• Event **VmDVPortEvent**

dvPort connected to VM changed status

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/)

<a id="VMEMIGRATINGEVENT"></a>

• Event **VmEmigratingEvent**

This event records a virtual machine migration.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmEmigratingEvent.html)

<a id="VMENDRECORDINGEVENT"></a>

• Event **VmEndRecordingEvent**

This event indicates the end of a recording session on a virtual machine.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmEndRecordingEvent.html)

<a id="VMENDREPLAYINGEVENT"></a>

• Event **VmEndReplayingEvent**

This event indicates the end of a replay session on a virtual machine.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmEndReplayingEvent.html)

<a id="VMEVENT"></a>

• Event **VmEvent**

This is a catch-all event for various VM events (the type of event is listed in the event). See VMware documentation for the list of possible events.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmEvent.html)

<a id="VMFAILEDMIGRATEEVENT"></a>

• Event **VmFailedMigrateEvent**

This event records a failure to migrate a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedMigrateEvent.html)

<a id="VMFAILEDRELAYOUTEVENT"></a>

• Event **VmFailedRelayoutEvent**

This event records a specific failure to re-layout a virtual machine, such as a failure to access the disk. "Layout" refers to the reformatting of the data on the disk to match VMware latest VMFS3 structure.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedRelayoutEvent.html)

<a id="VMFAILEDRELAYOUTONVMFS2DATASTOREEVENT"></a>

• Event **VmFailedRelayoutOnVmfs2DatastoreEvent**

This event records a failure to re-layout a virtual machine when the virtual machine still has disks on a VMFS2 volume. "Layout" refers to the reformatting of the data on the disk to match VMware latest VMFS3 structure.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedRelayoutOnVmfs2DatastoreEvent.html)

<a id="VMFAILEDSTARTINGSECONDARYEVENT"></a>

• Event **VmFailedStartingSecondaryEvent**

This event records vMotion failure when starting a secondary VM.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedStartingSecondaryEvent.html)

<a id="VMFAILEDTOPOWEROFFEVENT"></a>

• Event **VmFailedToPowerOffEvent**

This event records a failure to power off a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedToPowerOffEvent.html)

<a id="VMFAILEDTOPOWERONEVENT"></a>

• Event **VmFailedToPowerOnEvent**

This event records a failure to power on a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedToPowerOnEvent.html)

<a id="VMFAILEDTOREBOOTGUESTEVENT"></a>

• Event **VmFailedToRebootGuestEvent**

This event records a failure to reboot the guest on a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedToRebootGuestEvent.html)

<a id="VMFAILEDTORESETEVENT"></a>

• Event **VmFailedToResetEvent**

This event records a failure to reset a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedToResetEvent.html)

<a id="VMFAILEDTOSHUTDOWNGUESTEVENT"></a>

• Event **VmFailedToShutdownGuestEvent**

This event records a failure to shut down the guest on a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedToShutdownGuestEvent.html)

<a id="VMFAILEDTOSTANDBYGUESTEVENT"></a>

• Event **VmFailedToStandbyGuestEvent**

This event records a failure to set the guest on a virtual machine to a standby state.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedToStandbyGuestEvent.html)

<a id="VMFAILEDTOSUSPENDEVENT"></a>

• Event **VmFailedToSuspendEvent**

This event records a failure to suspend a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedToSuspendEvent.html)

<a id="VMFAILEDUPDATINGSECONDARYCONFIG"></a>

• Event **VmFailedUpdatingSecondaryConfig**

This event records after a failover the new primary failed to update the config of the secondary vm.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailedUpdatingSecondaryConfig.html)

<a id="VMFAILOVERFAILED"></a>

• Event **VmFailoverFailed**

This event records when a virtual machine failover was unsuccessful.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFailoverFailed.html)

<a id="VMFAULTTOLERANCESTATECHANGEDEVENT"></a>

• Event **VmFaultToleranceStateChangedEvent**

This event records a fault tolerance state change. A default alarm will be triggered upon this event, which can change the vm state: the vm state is red if the newState is needSecondary; the vm state is yellow if the newState is disabled; the vm state is green if the newState is notConfigured, starting, enabled or running.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFaultToleranceStateChangedEvent.html)

<a id="VMFAULTTOLERANCETURNEDOFFEVENT"></a>

• Event **VmFaultToleranceTurnedOffEvent**

This event records that all secondary virtual machines have been removed and fault tolerance protection turned off for this virtual machine.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFaultToleranceTurnedOffEvent.html)

<a id="VMFAULTTOLERANCEVMTERMINATEDEVENT"></a>

• Event **VmFaultToleranceVmTerminatedEvent**

This event records a secondary or primary VM is terminated. The reason could be: divergence, lost connection to secondary, partial hardware failure of secondary, or by user.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmFaultToleranceVmTerminatedEvent.html)

<a id="VMFSDATASTORECREATEDEVENT"></a>

• Event **VMFSDatastoreCreatedEvent**

This event records when a VMFS datastore is created.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VMFSDatastoreCreatedEvent.html)

<a id="VMFSDATASTOREEXPANDEDEVENT"></a>

• Event **VMFSDatastoreExpandedEvent**

This event records when a datastore is expanded.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VMFSDatastoreExpandedEvent.html)

<a id="VMFSDATASTOREEXTENDEDEVENT"></a>

• Event **VMFSDatastoreExtendedEvent**

This event records when a datastore is extended.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VMFSDatastoreExtendedEvent.html)

<a id="VMGUESTREBOOTEVENT"></a>

• Event **VmGuestRebootEvent**

This is a virtual machine guest reboot request event.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmGuestRebootEvent.html)

<a id="VMGUESTSHUTDOWNEVENT"></a>

• Event **VmGuestShutdownEvent**

This is a virtual machine guest shutdown request event.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmGuestShutdownEvent.html)

<a id="VMGUESTSTANDBYEVENT"></a>

• Event **VmGuestStandbyEvent**

This is a virtual machine guest standby request event.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmGuestStandbyEvent.html)

<a id="VMHEALTHMONITORINGSTATECHANGEDEVENT"></a>

• Event **VmHealthMonitoringStateChangedEvent**

This event records when host monitoring state has changed.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmHealthMonitoringStateChangedEvent.html)

<a id="VMINSTANCEUUIDASSIGNEDEVENT"></a>

• Event **VmInstanceUuidAssignedEvent**

This event records the assignment of a new instance UUID to a virtual machine.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmInstanceUuidAssignedEvent.html)

<a id="VMINSTANCEUUIDCHANGEDEVENT"></a>

• Event **VmInstanceUuidChangedEvent**

This event records a change in a virtual machine instance UUID.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmInstanceUuidChangedEvent.html)

<a id="VMINSTANCEUUIDCONFLICTEVENT"></a>

• Event **VmInstanceUuidConflictEvent**

This event records a conflict of virtual machine instance UUIDs.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmInstanceUuidConflictEvent.html)

<a id="VMMACASSIGNEDEVENT"></a>

• Event **VmMacAssignedEvent**

This event records the assignment of a new MAC address to a virtual network adapter.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmMacAssignedEvent.html)

<a id="VMMACCHANGEDEVENT"></a>

• Event **VmMacChangedEvent**

This event records a change in a virtual machine MAC address.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmMacChangedEvent.html)

<a id="VMMACCONFLICTEVENT"></a>

• Event **VmMacConflictEvent**

This event records a MAC address conflict for a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmMacConflictEvent.html)

<a id="VMMAXFTRESTARTCOUNTREACHED"></a>

• Event **VmMaxFTRestartCountReached**

This event is fired when FT VM reached the max restart count.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmMaxFTRestartCountReached.html)

<a id="VMMAXRESTARTCOUNTREACHED"></a>

• Event **VmMaxRestartCountReached**

This event is fired when the VM reached the max restart count.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmMaxRestartCountReached.html)

<a id="VMMESSAGEERROREVENT"></a>

• Event **VmMessageErrorEvent**

This event records when an error message (consisting of a collection of "observations") is thrown by the virtual machine. This is a generic event for such messages.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmMessageErrorEvent.html)

<a id="VMMESSAGEEVENT"></a>

• Event **VmMessageEvent**

This event records when a message is thrown by the virtual machine. This is a generic event for such messages.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmMessageEvent.html)

<a id="VMMESSAGEWARNINGEVENT"></a>

• Event **VmMessageWarningEvent**

This event records when a warning message (consisting of a collection of "observations") is thrown by the virtual machine. This is a generic event for such messages.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmMessageWarningEvent.html)

<a id="VMMIGRATEDEVENT"></a>

• Event **VmMigratedEvent**

This event records a virtual machine migration.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmMigratedEvent.html)

<a id="VMNOCOMPATIBLEHOSTFORSECONDARYEVENT"></a>

• Event **VmNoCompatibleHostForSecondaryEvent**

This event records that no compatible host was found to place a secondary VM. A default alarm will be triggered upon this event, which by default will trigger a SNMP trap.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmNoCompatibleHostForSecondaryEvent.html)

<a id="VMNONETWORKACCESSEVENT"></a>

• Event **VmNoNetworkAccessEvent**

This event records a migration failure when the destination host is not on the same network as the source host.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmNoNetworkAccessEvent.html)

<a id="VMORPHANEDEVENT"></a>

• Event **VmOrphanedEvent**

This event records a virtual machine for which no host is responsible.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmOrphanedEvent.html)

<a id="VMOTIONLICENSEEXPIREDEVENT"></a>

• Event **VMotionLicenseExpiredEvent**

This event records an expired VMotion license.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VMotionLicenseExpiredEvent.html)

<a id="VMPOWEREDOFFEVENT"></a>

• Event **VmPoweredOffEvent**

This event records when a virtual machine finished powering off.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmPoweredOffEvent.html)

<a id="VMPOWEREDONEVENT"></a>

• Event **VmPoweredOnEvent**

This event records when a virtual machine finished powering on.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmPoweredOnEvent.html)

<a id="VMPOWERINGONWITHCUSTOMIZEDDVPORTEVENT"></a>

• Event **VmPoweringOnWithCustomizedDVPortEvent**

This event records when a virtual machine was powering on using DVPorts with port level configuration, which may be different from the DVportgroup.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmPoweringOnWithCustomizedDVPortEvent.html)

<a id="VMPOWEROFFONISOLATIONEVENT"></a>

• Event **VmPowerOffOnIsolationEvent**

This event records when a virtual machine has been powered off on an isolated host in a HA cluster.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmPowerOffOnIsolationEvent.html)

<a id="VMPRIMARYFAILOVEREVENT"></a>

• Event **VmPrimaryFailoverEvent**

This event records an fault tolerance failover. The reason could be : lost connection to primary, partial hardware failure of primary or by user.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmPrimaryFailoverEvent.html)

<a id="VMRECONFIGUREDEVENT"></a>

• Event **VmReconfiguredEvent**

This event records a reconfiguration of the virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmReconfiguredEvent.html)

<a id="VMREGISTEREDEVENT"></a>

• Event **VmRegisteredEvent**

This event records that a virtual machine was successfully registered.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRegisteredEvent.html)

<a id="VMRELAYOUTSUCCESSFULEVENT"></a>

• Event **VmRelayoutSuccessfulEvent**

This event records that a virtual machine was successfully converted to the new virtual machine format on a VMFS3 volume.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRelayoutSuccessfulEvent.html)

<a id="VMRELAYOUTUPTODATEEVENT"></a>

• Event **VmRelayoutUpToDateEvent**

This event records that a virtual machine is already in the correct format. No re-layout is necessary. "Layout" refers to the reformatting of the data on the disk to match VMware latest VMFS3 structure.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRelayoutUpToDateEvent.html)

<a id="VMRELOADFROMPATHEVENT"></a>

• Event **VmReloadFromPathEvent**

This event records that a virtual machine was successfully reloaded from a new configuration path

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.VmReloadFromPathEvent.html)

<a id="VMRELOADFROMPATHFAILEDEVENT"></a>

• Event **VmReloadFromPathFailedEvent**

This event records that a virtual machine reload from a new configuration path failed

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.event.VmReloadFromPathFailedEvent.html)

<a id="VMRELOCATEDEVENT"></a>

• Event **VmRelocatedEvent**

This event records the completion of a virtual machine relocation.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRelocatedEvent.html)

<a id="VMRELOCATEFAILEDEVENT"></a>

• Event **VmRelocateFailedEvent**

This event records a failure to relocate a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRelocateFailedEvent.html)

<a id="VMREMOTECONSOLECONNECTEDEVENT"></a>

• Event **VmRemoteConsoleConnectedEvent**

This event records that a remote console was connected to the VM.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRemoteConsoleConnectedEvent.html)

<a id="VMREMOTECONSOLEDISCONNECTEDEVENT"></a>

• Event **VmRemoteConsoleDisconnectedEvent**

This event records that a remote console was disconnected from the VM.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRemoteConsoleDisconnectedEvent.html)

<a id="VMREMOVEDEVENT"></a>

• Event **VmRemovedEvent**

This event records a virtual machine removed from vCenter management.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRemovedEvent.html)

<a id="VMRENAMEDEVENT"></a>

• Event **VmRenamedEvent**

This event records the renaming of a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRenamedEvent.html)

<a id="VMREQUIREMENTSEXCEEDCURRENTEVCMODEEVENT"></a>

• Event **VmRequirementsExceedCurrentEVCModeEvent**

Since VI API 5.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRequirementsExceedCurrentEVCModeEvent.html)

<a id="VMRESETTINGEVENT"></a>

• Event **VmResettingEvent**

This event records a virtual machine resetting.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmResettingEvent.html)

<a id="VMRESOURCEPOOLMOVEDEVENT"></a>

• Event **VmResourcePoolMovedEvent**

This event records when a virtual machine is moved from one resource pool to another.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmResourcePoolMovedEvent.html)

<a id="VMRESOURCEREALLOCATEDEVENT"></a>

• Event **VmResourceReallocatedEvent**

This event records a change in resource allocation of a virtual machine.

The name of the virtual machine is in the event. This event is generated typically in DRS configurations when VC detects that the available resources (such as CPU) are changing.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmResourceReallocatedEvent.html)

<a id="VMRESTARTEDONALTERNATEHOSTEVENT"></a>

• Event **VmRestartedOnAlternateHostEvent**

This event records that the virtual machine was restarted on a host, since its original host had failed.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmRestartedOnAlternateHostEvent.html)

<a id="VMRESUMINGEVENT"></a>

• Event **VmResumingEvent**

This event records a virtual machine resuming.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmResumingEvent.html)

<a id="VMSECONDARYADDEDEVENT"></a>

• Event **VmSecondaryAddedEvent**

This event records a secondary VM is added.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmSecondaryAddedEvent.html)

<a id="VMSECONDARYDISABLEDBYSYSTEMEVENT"></a>

• Event **VmSecondaryDisabledBySystemEvent**

This event records that a fault tolerance secondary VM has been disabled by vCenter because the VM could not be powered on.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmSecondaryDisabledBySystemEvent.html)

<a id="VMSECONDARYDISABLEDEVENT"></a>

• Event **VmSecondaryDisabledEvent**

This event records a secondary VM is disabled.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmSecondaryDisabledEvent.html)

<a id="VMSECONDARYENABLEDEVENT"></a>

• Event **VmSecondaryEnabledEvent**

This event records a secondary VM is enabled.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmSecondaryEnabledEvent.html)

<a id="VMSECONDARYSTARTEDEVENT"></a>

• Event **VmSecondaryStartedEvent**

This event records a secondary VM is started successfully.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmSecondaryStartedEvent.html)

<a id="VMSHUTDOWNONISOLATIONEVENT"></a>

• Event **VmShutdownOnIsolationEvent**

This event records when a virtual machine has been shut down on an isolated host in a HA cluster.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmShutdownOnIsolationEvent.html)

<a id="VMSTARTINGEVENT"></a>

• Event **VmStartingEvent**

This event records a virtual machine powering on. It typically will be followed by a [VmPoweredOnEvent](#VMPOWEREDONEVENT).

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmStartingEvent.html)

<a id="VMSTARTINGSECONDARYEVENT"></a>

• Event **VmStartingSecondaryEvent**

This event records a vMotion to start a secondary VM.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmStartingSecondaryEvent.html)

<a id="VMSTARTRECORDINGEVENT"></a>

• Event **VmStartRecordingEvent**

This event indicates the start of a recording session on a virtual machine.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmStartRecordingEvent.html)

<a id="VMSTARTREPLAYINGEVENT"></a>

• Event **VmStartReplayingEvent**

This event indicates the start of a replay session on a virtual machine.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmStartReplayingEvent.html)

<a id="VMSTATICMACCONFLICTEVENT"></a>

• Event **VmStaticMacConflictEvent**

This event records a static MAC address conflict for a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmStaticMacConflictEvent.html)

<a id="VMSTOPPINGEVENT"></a>

• Event **VmStoppingEvent**

This event records a virtual machine stopping.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmStoppingEvent.html)

<a id="VMSUSPENDEDEVENT"></a>

• Event **VmSuspendedEvent**

This event records when a virtual machine finished suspending.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmSuspendedEvent.html)

<a id="VMSUSPENDINGEVENT"></a>

• Event **VmSuspendingEvent**

This event records a virtual machine suspending.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmSuspendingEvent.html)

<a id="VMTIMEDOUTSTARTINGSECONDARYEVENT"></a>

• Event **VmTimedoutStartingSecondaryEvent**

This event records timeout when starting a secondary VM. A default alarm will be triggered upon this event, which by default will trigger a SNMP trap.

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmTimedoutStartingSecondaryEvent.html)

<a id="VMUNSUPPORTEDSTARTINGEVENT"></a>

• Event **VmUnsupportedStartingEvent**

This event records when an unsupported guest is powering on.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmUnsupportedStartingEvent.html)

<a id="VMUPGRADECOMPLETEEVENT"></a>

• Event **VmUpgradeCompleteEvent**

This event records the successful completion of an upgrade operation.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmUpgradeCompleteEvent.html)

<a id="VMUPGRADEFAILEDEVENT"></a>

• Event **VmUpgradeFailedEvent**

This event records a failure to upgrade virtual hardware.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmUpgradeFailedEvent.html)

<a id="VMUPGRADINGEVENT"></a>

• Event **VmUpgradingEvent**

This event records the process of upgrading the virtual hardware on a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmUpgradingEvent.html)

<a id="VMUUIDASSIGNEDEVENT"></a>

• Event **VmUuidAssignedEvent**

This event records the assignment of a new BIOS UUID to a virtual machine.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmUuidAssignedEvent.html)

<a id="VMUUIDCHANGEDEVENT"></a>

• Event **VmUuidChangedEvent**

This event records a change in a virtual machine BIOS UUID. Veeam has observed that during migrations this event may be generated even though the UUID is not changing.

A sample event is included below (note that on this version of ESX the name of the VM is missing after the word "for", and the UUID is actually not changing).

*Changed BIOS UUID from 500e3054-23fd-6ff6-58a7-037500940891 to 500e3054-23fd-6ff6-58a7-037500940891 for on esx04.seattle.veeam.local in SEATTLE VmUuidChangedEvent*

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmUuidChangedEvent.html)

<a id="VMUUIDCONFLICTEVENT"></a>

• Event **VmUuidConflictEvent**

This event records a conflict of virtual machine BIOS UUIDs. That is, a virtual machine has been detected with a duplicate UUID (Universally Unique Identifier).

When a VM is cloned, its UUID is also clone and will remain with the same UUID until 2 VMs with the same UUID are powered on. Only when the VM is running is the uniqueness of UUIDs assured. When the hypervisor detects a VM powering up has a duplicate UUID it will change it and issue this event.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmUuidConflictEvent.html)

<a id="VMVNICPOOLRESERVATIONVIOLATIONCLEAREVENT"></a>

• Event **VmVnicPoolReservationViolationClearEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmVnicPoolReservationViolationClearEvent.html)

<a id="VMVNICPOOLRESERVATIONVIOLATIONRAISEEVENT"></a>

• Event **VmVnicPoolReservationViolationRaiseEvent**

Since VI API 5.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmVnicPoolReservationViolationRaiseEvent.html)

<a id="VMWWNASSIGNEDEVENT"></a>

• Event **VmWwnAssignedEvent**

This event records the assignment of a new WWN (World Wide Name) to a virtual machine.

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmWwnAssignedEvent.html)

<a id="VMWWNCHANGEDEVENT"></a>

• Event **VmWwnChangedEvent**

This event records a change in a virtual machine WWN (World Wide Name).

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmWwnChangedEvent.html)

<a id="VMWWNCONFLICTEVENT"></a>

• Event **VmWwnConflictEvent**

This event records a conflict of virtual machine WWNs (World Wide Name).

Since VI API 2.5. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.VmWwnConflictEvent.html)

<a id="VPROB.NET.CONNECTIVITY.LOST"></a>

• Event **vprob.net.connectivity.lost**

Lost Network Connectivity

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.NET.E1000.TSO6.NOTSUPPORTED"></a>

• Event **vprob.net.e1000.tso6.notsupported**

No IPv6 TSO support

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.NET.MIGRATE.BINDTOVMK"></a>

• Event **vprob.net.migrate.bindtovmk**

Invalid vmknic specified in /Migrate/Vmknic

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.NET.PROXYSWITCH.PORT.UNAVAILABLE"></a>

• Event **vprob.net.proxyswitch.port.unavailable**

VNic connect to switch failed

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.NET.REDUNDANCY.DEGRADED"></a>

• Event **vprob.net.redundancy.degraded**

Network Redundancy Degraded

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.NET.REDUNDANCY.LOST"></a>

• Event **vprob.net.redundancy.lost**

Lost Network Redundancy

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.SCSI.DEVICE.THINPROV.ATQUOTA"></a>

• Event **vprob.scsi.device.thinprov.atquota**

Space utilization on thin-provisioned device exceeded configured threshold

Since VI API 4.1. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.STORAGE.CONNECTIVITY.LOST"></a>

• Event **vprob.storage.connectivity.lost**

Lost Storage Connectivity

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.STORAGE.REDUNDANCY.DEGRADED"></a>

• Event **vprob.storage.redundancy.degraded**

Degraded Storage Path Redundancy

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.STORAGE.REDUNDANCY.LOST"></a>

• Event **vprob.storage.redundancy.lost**

Lost Storage Path Redundancy

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.ERROR.VOLUME.IS.LOCKED"></a>

• Event **vprob.vmfs.error.volume.is.locked**

Volume is locked

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.EXTENT.OFFLINE"></a>

• Event **vprob.vmfs.extent.offline**

Device is offline

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.EXTENT.ONLINE"></a>

• Event **vprob.vmfs.extent.online**

Device is online

Since VI API 5.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.HEARTBEAT.RECOVERED"></a>

• Event **vprob.vmfs.heartbeat.recovered**

VMFS Volume Connectivity Restored

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.HEARTBEAT.TIMEDOUT"></a>

• Event **vprob.vmfs.heartbeat.timedout**

VMFS Volume Connectivity Degraded

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.HEARTBEAT.UNRECOVERABLE"></a>

• Event **vprob.vmfs.heartbeat.unrecoverable**

VMFS Volume Connectivity Lost

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.JOURNAL.CREATEFAILED"></a>

• Event **vprob.vmfs.journal.createfailed**

No Space To Create VMFS Journal

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.LOCK.CORRUPTONDISK"></a>

• Event **vprob.vmfs.lock.corruptondisk**

VMFS Lock Corruption Detected

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.NFS.SERVER.DISCONNECT"></a>

• Event **vprob.vmfs.nfs.server.disconnect**

Lost connection to NFS server

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.NFS.SERVER.RESTORED"></a>

• Event **vprob.vmfs.nfs.server.restored**

Restored connection to NFS server

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.RESOURCE.CORRUPTONDISK"></a>

• Event **vprob.vmfs.resource.corruptondisk**

VMFS Resource Corruption Detected

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="VPROB.VMFS.VOLUME.LOCKED"></a>

• Event **vprob.vmfs.volume.locked**

VMFS Locked By Remote Host

Since VI API 4.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.EventEx.html)

<a id="WARNINGUPGRADEEVENT"></a>

• Event **WarningUpgradeEvent**

This event is a general warning event from upgrade.

Since VI API 2.0. For more information, see the [VMware API reference](http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.event.WarningUpgradeEvent.html)