The messages for alarms forwarded from vcenter do not contain enough information

Document ID : KB000010640
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

Alarms and events generated by the Vcenter Monitoring feature can be Monitored by the vmware probe and it can publish alarms for these in UIM

The default message for these alarms is MonitorError which has the following definition

The monitor $monitor on $host:$port is outside expected limits ($value $oper $thr) 

This results in a message similar to the following:

The monitor esx51.voonair.inc.local.Event on esx51:443 is outside expected limits (1 >= 0) 

This does not provide enough information to allow the admin to take effective action.

Background:

TEC1052889 details the variables that can be added to the vmware probe messages and with these the alarm can be made much more useable.

Instructions:

Adding the $info variable to the message defnitiion will include the actual alarm or event seen in vcenter

eg The monitor $monitor on $host:$port is outside expected limits ($value $oper $thr) $info

will result in the message

The monitor esx51.voonair.inc.local.Event on esx51:443 is outside expected limits (1 >= 0) Message on svr2012 on esx51.forward.inc.local in ha-datacenter: Running VMware ESX in a virtual machine will result in degraded performance. Do you want to continue?

 

Admin Console (AC)

  • Raw configure the vmware probe
  • Select Messages 
  • scroll to MonitorError
  • edit the value for the key msn_err

Infrastructure Manager (IM)

Additional Information:

If the Vmware probe is configured for Bulk Configuration Mode (templates) then the IM cannot be used to configure the probe and you must use AC.