SVM Operations System Events

The table explains system event messages for service VM (SVM) operations of major, critical, or high severity.

Event Code	Event Severity	Alarm Triggered	Event Message	Description
280002	High	Yes	Some of the events for this agent were missed by NSX. Probably reason could be reboot or temporary connectivity loss with Vcenter Server.Warning: Resolving the alarm will delete the VM and raise another indicating agent VM is missing. Resolving same will redeploy the VM.	A deployed service VM experienced an internal error. Action: Resolving the alarm deletes the VM and reports a second alarm about the deletion. Resolving the second alarm reinstalls the VM. If redeploying the VM fails, the original alarm is again reported. If the alarm reappears, collect the SVM logs using the procedure in KB http://kb.vmware.com/kb/2144624, and contact VMware technical support.
280003	High	Yes	Some of the events for this agent were missed by NSX. Probably reason could be reboot or temporary connectivity loss with vCenter Server.Warning: Resolving the alarm will restart the VM.	A deployed service VM has been restarted. Action: Resolving the alarm restarts the VM. If the restart fails, the alarm reappears. Collect the SVM logs using the procedure in KB http://kb.vmware.com/kb/2144624, and contact VMware technical support.
280006	High	Yes	Failed to mark agent as available.	An internal error occurred while marking the ESX agent VM as available. Action: Resolve the alarm using the action=resolve parameter in the systemalarms API . If the alarm cannot be resolved, collect the SVM logs using the procedure in KB http://kb.vmware.com/kb/2144624, and contact VMware technical support.