Thanks for responding.
I don't find any of the second triggers you mentioned.
My first alarm rule is Lost Storage Path Redundancy
The second is Degraded Storage Path Redundancy
My Reset rule is IF Lost Storage Connectivity
I believe that is the default. maybe on purpose as normally it doesn't resolve on its own
Original Message:
Sent: Aug 05, 2025 04:15 PM
From: Lubomir Tobek
Subject: Cannot Connect to Storage Alarm Reset
You can try the following:
*Edit the Alarm Definition (from the vSphere Client):
*Go to Monitor > Alarm Definitions.
*Find "Cannot connect to storage" (or whatever custom alarm it is).
*Under Triggers, review what event(s) fire the alarm.
*Then add a second trigger for an event like All paths restored to storage device or Storage path redundancy restored.
Original Message:
Sent: Aug 05, 2025 08:59 AM
From: ChrisLeblanc
Subject: Cannot Connect to Storage Alarm Reset
Hi all,
we had our storage team doing some work the other night where hosts had lost partial connection to the storage array.
This triggered an alarm and the condition was temporary. The alarms triggered did not reset to green.
I was looking at the Cannot Connect To Storage alarm definition and I find the default reset to green condition seems to be a partial rule that doesn't make sense. I don't find any options i can set that would reset this to green.
I can see us wanting to be aware but we also run a vCheck report and it does list errors seen during the day.
Has anyone been able to tweak this alarm to reset? (It is a rare case so maybe not worth me pursuing it)
Thoughts?
-------------------------------------------