Creating Custom Alert for Stale VM Objects in Aria Operations for Logs

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• A custom alert can be created in Aria Operations for Logs to detect and trigger notifications when a stale Virtual Machine (VM) object is identified on the VM/Host side

Environment

• Aria Operations for Logs 8.x

Resolution

• Create a custom alert in Aria Operations for Logs (Alerts > Alert Definitions > Create New) with the filter text contains "Failed to load virtual machine: vim.fault.FileAlreadyExists"

Additional Information

• The following event types indicate stale VM objects. And the below events may be seen in the hostd.log file on hosts where inaccessible virtual machines are registered:

  • info 'vm:/vmfs/volumes/########-########/VMname/VMname.vmx'] Failed to load virtual machine: vim.fault.FileAlreadyExists

  • warning 'vm:/vmfs/volumes/########-########/VMname/VMname.vmx'] Failed to load VM from foundry during register vim.fault.FileAlreadyExists

  • info 'vm:/vmfs/volumes/########-########/VMname/VMname.vmx'] Marking VirtualMachine invalid

  • info 'vm:/vmfs/volumes/########-########/VMname/VMname.vmx'] State Transition (VM_STATE_INITIALIZING -> VM_STATE_INVALID_LOAD)

• In the vmkernel.log file on hosts where inaccessible virtual machines are registered, the following events may be seen:

• • WARNING: NFS: ####: Failed to get attributes (Invalid handle)

  • FSS: ###: Failed to get object <ID> :Invalid handle