vCenter Server alarms trigger without any actions taken

Products

• VMware vCenter Server

Issue/Introduction

This article helps resolve issues with alarm actions

Symptoms:

• Alarms in vCenter server trigger, but configured actions such as email or commands are not completed.
• Only some objects in the inventory are affected
• In verbose logging mode, /var/log/vmware/vpxd/vpxd.log contains entries similar to:
  
  2022-09-04T13:09:20.719Z verbose vpxd[60254] [Originator@6876 sub=alarmMo opID=ProcessEventNotifications-581f4da5] [CheckAndFireActionInt] Did not fire disabled action for entity esxi1.vmware.local
  2022-09-04T13:09:20.719Z verbose vpxd[60254] [Originator@6876 sub=alarmMo opID=ProcessEventNotifications-581f4da5] [CheckAndFireActionInt] Did not fire disabled action for entity esxi1.vmware.local

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This will occur if alarm actions are disabled on the specific inventory object.

Resolution

To resolve this, right click on the affected inventory object and select Alarm > Enable Alarm Actions.

Additional Information

For more information, see Enable and Disable Alarm Actions in the vSphere Documentation