Quickie tutorial on what I am guessing is a common error encountered in vmware:
“Alarm settings are read-only except when accessed through the object where they were defined”"
After figuring this out I almost felt foolish how much time I looked at this one. Enjoy!
The VMware Error
“Alarm settings are read-only except when accessed through the object where they were defined”
“View Settings” vs. “Edit Settings”
You can tell right away when you right click on the alarm and “View Settings” shows up instead of “Edit Settings”
Find Where The Error Is Defined
The error itself is descriptive. You just have to read it carefully (which I did not). Check out the column to the right to see where the error was defined. In this case it is defined in “vcenter” (cut off in my snapshot) which is my datacenter.
Select Where The Error Is Defined
So in the left navigation bar, left click on the datacenter (or wherever your alarm is defined)
Now You Can Edit The Alarm1h>
Defining New Alarms
So if you choose not to edit the alarm at the datacenter level (which affects all VMs in that hierarchy), you can always define a new alarm at different levels, even down to the host level.
In this example, just drill down to the host in the left navigation pane
In the area on the right, right-click on a blank space and “New Alarm” will show up as a choice
Setting up a new alarm for the most part is pretty straightforward. However, if you need some guidance, that will be a blog post in the near future as that is all I have time for today.