Modifying an alarm "vCenter HA Cluster Health Alarm"
Article ID: 316002
Updated On:
Products
Issue/Introduction
There are four rulesets for the alarm vCenter HA Cluster Health Alarm.
In this, rule number 3 in the Ui shows the status as unknown
Environment
VMware vCenter Server 8.0.0
Cause
This is a cosmetic issue. The engineering team is aware of this and the code fix is in progress.
Resolution
VCHA team from engineering is working to fix it in future releases.
This issue is noticed in vSphere 8.0 Build 20513097.
Workaround:
1) From the default alarm, they can actually delete the 3rd ruleset, which makes the alarm with two rules, and two possible outcomes. When either of the condition is met, they will receive the warning or critical event/email notification, and they can get to know which condition caused the alarm.
2) They can manually create a new alarm and name it something different (as per their choice), and define the condition as it was there in the 3rd ruleset of the above alarm, so if this condition is met, they will be notified via a separate alarm name altogether.
Additional Information
Impact/Risks:
The alarm won't trigger for the defined rule.
If someone tries to modify the alarm they get an error
Error: Operation Failed
"A Specified parameter was not correct: spec"
vpxd.log
YYYY-MM-DDTHH:MM:SS info vpxd[06887] [Originator@6876 sub=vpxLro opID=lbftn4g5-987-auto-rg-h5:70000409-43] [VpxLRO] -- BEGIN task-1014 -- alarm-159 -- vim.alarm.Alarm.reconfigure -- 522fdcfa-236b-1942-bdf9-xxxxxxxxxxxxxx(52299541-6fea-4d95-d160-xxxxxxxxxxxxxx)
YYYY-MM-DDTHH:MM:SS info vpxd[06887] [Originator@6876 sub=vpxLro opID=lbftn4g5-987-auto-rg-h5:70000409-43] [VpxLRO] -- FINISH task-1014
YYYY-MM-DDTHH:MM:SS info vpxd[06887] [Originator@6876 sub=Default opID=lbftn4g5-987-auto-rg-h5:70000409-43] [VpxLRO] -- ERROR task-1014 -- alarm-159 -- vim.alarm.Alarm.reconfigure: vmodl.fault.InvalidArgument:
--> Result:
--> (vmodl.fault.InvalidArgument) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> invalidProperty = "spec"
--> msg = ""
--> }
--> Args:
-->
--> Arg spec:
--> (vim.alarm.AlarmInfo) {
--> name = "alarm.VCHAHealthAlarm",
--> systemName = "alarm.VCHAHealthAlarm",
--> description = "alarm.VCHAHealthAlarm",
--> enabled = true,
--> expression = (vim.alarm.OrAlarmExpression) {
--> expression = (vim.alarm.AlarmExpression) [
--> (vim.alarm.EventAlarmExpression) {
--> comparisons = <unset>,
--> eventType = "vim.event.EventEx",
--> eventTypeId = "com.vmware.vcha.cluster.state.degraded",
--> objectType = "vim.Folder",
--> status = "yellow"
--> },
--> (vim.alarm.EventAlarmExpression) {
--> comparisons = <unset>,
--> eventType = "vim.event.EventEx",
--> eventTypeId = "com.vmware.vcha.cluster.state.isolated",
--> objectType = "vim.Folder",
--> status = "red"
--> },
--> (vim.alarm.EventAlarmExpression) {
--> comparisons = <unset>,
--> eventType = "vim.event.EventEx",
--> eventTypeId = "com.vmware.vcha.cluster.state.destroyed",
--> objectType = "vim.Folder",
--> status = <unset> <------------------------ This is the place that will highlight the exception.
--> },
--> (vim.alarm.EventAlarmExpression) {
--> comparisons = <unset>,
--> eventType = "vim.event.EventEx",
--> eventTypeId = "com.vmware.vcha.cluster.state.healthy",
--> objectType = "vim.Folder",
--> status = "green"
--> }
--> ]
--> },
--> action = (vim.alarm.GroupAlarmAction) {
--> action = (vim.alarm.AlarmAction) [
--> (vim.alarm.AlarmTriggeringAction) {
--> action = (vim.action.SendEmailAction) {
--> toList = "XXXXXXXXXXXXXXXXXXXXXXXXX",
--> ccList = "",
--> subject = "Alarm {alarmName} on vCenter Server : {targetName} is {newStatus}",
--> body = ""
--> },
--> transitionSpecs = (vim.alarm.AlarmTriggeringAction.TransitionSpec) [
--> (vim.alarm.AlarmTriggeringAction.TransitionSpec) {
--> startState = "green",
--> finalState = "yellow",
--> repeats = true
--> },
--> (vim.alarm.AlarmTriggeringAction.TransitionSpec) {
--> startState = "red",
--> finalState = "yellow",
Feedback
