vCenter not showing triggered alarm during planned storage controller maintenance
Article ID: 440944
Updated On:
Products
Issue/Introduction
Storage maintenance performed causing single controller to go down temporarily.
Alarm “Cannot connect to storage” enabled and configured to send emails.
VCSA journalctl logs show the alarm triggered and email sent.
May 13 20:50:18 <vcsa_fqdn> vpxd[6108]: Event [48563093] [1-1] [2026-05-13T11:50:18.616664Z] [vim.event.AlarmEmailCompletedEvent] [info] [] [####)] [48563093] [Alarm 'Cannot connect to storage' on
<esx_host_FQDN> sent email to <email_address>]
ESX hostd logs show the event.
2026-05-13T11:50:11.979Z In(166) Hostd[####]: --> eventTypeId = "esx.problem.storage.redundancy.degraded",
Emails received but no Event/Triggered alarm listed for the event in the VC vSphere client UI to reset to Green.
Cause
The default vCenter alarm "Cannot connect to storage" is a “Stateless” alarm and will not be tracked for it to be reset to green in the VC vSphere client.
Resolution
vSphere is working as expected and no changes need to be made.
- Preconfigured vSphere Alarms > Alarm “Cannot connect to storage” is a Stateless alarm per the asterisk (“*”) next to its name.
Additional Information
If it is desired, a custom alarm to show a banner/event/triggered alarm within the vSphere UI for storage status, that requires to be reset to Green before disappearing from the UI, can be created to perform the actions when the conditions selected are triggered.
Feedback
