Host Preparation System Events

The table explains all system event messages related to host preparation.

Note: Multiple ESX Agent Manager events map to a single event on NSX.

Event Code	Event Severity	Alarm Triggered	Event Message	Description
270000	Informational	Yes	A VIB module has been uploaded to the host {hostID}, but will not be fully installed until the host {hostID} has been put in maintenance mode.	ESX Agent Manager puts host in the maintenance mode. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	Critical	Yes	An agent virtual machine is expected to be deployed on a host, but the agent virtual machine cannot be deployed because the vSphere ESX Agent Manager is unable to access the OVF package for the agent. This typically happens because the Web server providing the OVF package is down. The Web server is often internal to the solution that created the Agency.	ESX Agent Manager redeploys the agent. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	Critical	Yes	An agent VIB module is expected to be deployed on a host, but the VIM module cannot be deployed because the vSphere ESX Agent Manager is unable to access the VIB package for the agent. This typically happens because the Web server providing the VIB package is down. The Web server is often internal to the solution that created the Agency.	ESX Agent Manager reinstalls the VIB module. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is expected to be deployed on a host, but the agent could not be deployed because it was incompatible with the host {hostID}.	vSphere ESX Agent Manager redeploys the agent . Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm. However, the problem is likely to persist until you upgrade either the host or the solution, so that the agent becomes compatible with the host.
270000	High	Yes	An agent virtual machine is expected to be powered on, but there are no free IP addresses in the agent's pool of virtual machine IP addresses.	Action: To resolve the issue, free some IP addresses or add some more IP addresses to the IP pool and then use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is expected to be deployed on a host, but the agent virtual machine could not be deployed because the host {hostID} does not have enough free CPU or memory resources.	ESX Agent Manager redeploys the agent virtual machine. However, the problem is likely to persist until enough CPU and memory resources are made available. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is expected to be deployed on a host, but the agent virtual machine could not be deployed because the host's agent datastore did not have enough free space.	ESX Agent Manager redeploys the agent virtual machine. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm. However, the problem is likely to persist until either: You free-up space on the host's agent virtual machine datastore. -Or- Configure a new agent virtual machine datastore with enough free space.
270000	High	Yes	An agent virtual machine is expected to be powered on, but the agent virtual machine is powered off because there there are no IP addresses defined on the agent's virtual machine network.	Action: Create an IP pool on the agent's virtual machine network and use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is expected to be deployed on a host, but the agent cannot be deployed because the agent datastore has not been configured on the host {hostID}.	Action: You must configure the agent virtual machine datastore on the host.
270000	High	Yes	An agent virtual machine is expected to be deployed on a host, but the agent cannot be deployed because the agent network has not been configured on the host.	Action: You must configure the agent virtual machine network on the host.
270000	High	Yes	An agent virtual machine is expected to be deployed on a host, but the agent cannot be deployed because the agent network has not been configured on the host. The host needs to be added to one of the networks listed in customAgentVmNetwork.	Action: You must add one of the customAgentVmNetwork networks to the host.
270000	High	Yes	An agent virtual machine is expected to be deployed on a host, but the agent cannot be deployed because the agent datastore has not been configured on the host. The host needs to be added to one of the datastores listed in customAgentVmDatastore.	You must add one of the datastores named customAgentVmDatastore to the host.
270000	High	Yes	The solution that created the agency is no longer registered with the vCenter server.	ESX Agent Manager removes the agency. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	A dvFilter switch exists on a host but no agents on the host depend on dvFilter. This typically happens if a host is disconnected when an agency configuration changed.	ESX Agent Manager removes the dvFilterSwitch. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An Agent virtual machine is expected to be provisioned on a host, but it failed to do so because the provisioning of the OVF package failed. The provisioning is unlikely to succeed until the solution that provides the OVF package has been upgraded or patched to provide a valid OVF package for the agent virtual machine.	ESX Agent Manager attempts the OVF provisioning again. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine needs to be powered on, but an OVF property is either missing or has an invalid value.	Action: Update the OVF environment in the agent configuration used to provision the agent virtual machine.
270000	High	Yes	An agent virtual machine has been found in the vCenter inventory that does not belong to any agency in this vSphere ESX Agent Manager server instance.	ESX Agent Manager powers off (if powered on) and deletes the agent virtual machine. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	A VIB module requires the host to be in maintenance mode, but the vSphere ESX Agent Manager is unable to put the host in maintenance mode. This can happen if there are virtual machines running on the host that cannot be moved and must be stopped before the host can enter maintenance mode.	ESX Agent Manager tries to put the host into maintenance mode. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm. However, the problem is likely to persist until you power off or move virtual machines to put the host into maintenance mode.
270000	Critical	Yes	A VIB module is expected to be installed on a host, but it failed to install since the VIB package is in an invalid format. The installation is unlikely to succeed until the solution providing the bundle has been upgraded or patched to provide a valid VIB package.	ESX Agent Manager attempts the VIB installation again. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	A VIB module is expected to be installed on a host, but it has not been installed. Typically, a more specific issue (a subclass of this issue) indicates the particular reason why the VIB module installation failed.	ESX Agent Manager attempts the VIB installation again. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	informational	Yes	A VIB module has been uploaded to the host, but will not be activated until the host is rebooted.	ESX Agent Manager puts the host into maintenance mode and reboots it. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	A VIB module failed to install, but failed to do so because automatic installation by vSphere ESX Agent Manager is not allowed on the host.	Action: Go to vSphere Update Manager and install the required bulletins on the host or add the bulletins to the host's image profile.For more details, refer to vSphere documentation.
270000	High	Yes	A VIB module failed to uninstall, but failed to do so because automatic uninstallation by vSphere ESX Agent Manager is not allowed on the host.	Action: Go to vSphere Update Manager and uninstall the required bulletins on the host or add the bulletins to the host's image profile.For more details, refer to vSphere documentation.
270000	High	Yes	An agent virtual machine is corrupt.	ESX Agent Manager deletes and re-provisions the agent virtual machine. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm. To resolve the issue manually: Resolve the problem related to the missing file and power on the agent virtual machine.
270000	High	Yes	An agent virtual machine is expected to be removed from a host, but the agent virtual machine has not been removed. Typically, a more specific issue (a subclass of this issue) indicates the particular reason why vSphere ESX Agent Manager was unable to remove the agent virtual machine, such as the host is in maintenance mode, powered off or in standby mode.	ESX Agent Manager redeploys the agent. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is a virtual machine template.	ESX Agent Manager converts the agent virtual machine template to a virtual machine. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is expected to be deployed on a host, but the agent virtual machine has not been deployed. Typically, a more specific issue (a subclass of this issue) indicates the particular reason why vSphere ESX Agent Manager was unable to deploy the agent, such as being unable to access the OVF package for the agent or a missing host configuration. This issue can also happen if the agent virtual machine is explicitly deleted from the host.	ESX Agent Manager redeploys the agent virtual machine. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is expected to be powered on, but the agent virtual machine is powered off.	ESX Agent Manager powers on the agent virtual machine. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is expected to be powered off, but the agent virtual machine is powered off.	ESX Agent Manager powers off the agent virtual machine. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is expected to be powered on, but the agent virtual machine is suspended.	ESX Agent Manager powers on the agent virtual machine. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is expected to be located in a designated agent virtual machine folder, but is found in a different folder.	ESX Agent Manager moves the agent virtual machine back into the designated agent folder. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	An agent virtual machine is expected to be located in a designated agent virtual machine resource pool, but is found in a different resource pool.	ESX Agent Manager moves the agent virtual machine back into the designated agent resource pool. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.
270000	High	Yes	EAM alarm received.	ESX Agent Manager detected an NSX installation or upgrade issue with either NSX VIBs or service VMs. Action: Click the Resolve option on the Host Preparation tab, or use the action=resolve parameter in the systemalarms API to resolve the alarm.