Here's how my migration alarm is set up. Because the "Status" is still at default to "Unset", I would think that if a VM failed to relocate, a trap would NOT be sent. However it does, because the VM status becomes gray. Please dont ask why I dont change "Unset" to "Warning" or "Alert"...still trying to figure out these dam alarms.
| Alarm Name | Description | Triggers | Reporting | Actions | ||||||
| Event | Status | Conditions | Action | G>Y | Y>R | R>Y | Y>G | |||
| Migration error | Default alarm to monitor if a virtual machine cannot migrate, relocate, or is orphaned | Cannot migrate VM Migration error Migration host error Cannot relocate VM VM orphaned | Unset Unset Unset Unset Unset | trap | once | |||||
Here's my trap...
Short description: NOTIFICATION-VMWARE-VC-EVENT_VCENTER.DOMAIN.COM__AM-COMPANY_vpxdAlarmInfo
Event summary: VCENTER ALERT Object "VM_NAME" new status is "Gray". Additional information is "alarm.MigrationErrorAlarm - Event: Cannot relocate VM (119844) Summary: Cannot relocate virtual machine 'VM_NAME' in LOCATION Date: 9/16/2013 10:05:16 AM User name: DOMAIN\USER VM: VM_NAME Host: ESXHOST.DOMAIN.COM Resource pool: CLUSTER Datastore: DATASTORE Data center: DATACENTER Arguments: destDatacenter.name = DATACENTER destDatastore.name = DATASTORE destHost.name = ESXHOST.DOMAIN.COM"