jakas
Contributor
Contributor

Alarms on Vcenter

we have default Alarms setup to send traps but lately we are seeing the traps sent are "Descriptions" rather than the alarm.xxx format. Is there a setting that we might have changed?

for example, Host Connectivity Failure alarm should an trap as "alarm.hostconnectivityalarm - Event:<description>". But lately, we are seeing the trap sent as "Host Connectivity Failure - Event:<description>". Our monitoring software is setup to use the alarm.xxx format to generate tickets.  But lately, the different text is breaking the monitor software.

Any help greatly appreciated.

Wish you all a happy new year.

thanks.

0 Kudos
3 Replies
a_nut_in
Expert
Expert

Was the VC upgraded before the change was noticed? If so, from which version to which version?

Do remember to mark my post as "helpful" or "correct" if I've helped resolve or answer your query!
0 Kudos
jakas
Contributor
Contributor

vCenter server version 5.0.0 build 913577

there was no upgrade or even a patch install. Actually the vCenter server is very recent install.

0 Kudos
King_Robert
Hot Shot
Hot Shot

  • To create alarms, the vSphere Client must be connected to a vCenter Server with the appropriate user permissions on all relevant objects. After an alarm is created, it is enabled even if the user who created it no longer has permissions.

To open the Alarm Settings dialog, perform any one of these operations:

  • Click File > Prerequisites > Alarm.
  • Click Inventory > object_type > Alarm > Add Alarm.
  • Right-click the object and select Alarm > Add Alarm.
  • In the Alarms tab, click the Definitions tab, right-click in the pane, and click New > Alarm.
  • Click on the object in the inventory and press Ctrl+A.

Alarm Settings – General tab

To create a new alarm:

  1. Enter an alarm name and description.
  2. Define the type of alarm:
    1. In the Monitor list, click Virtual Machines.
    2. Select Monitor for specific conditions or state.
  3. Select Enable this alarm.

Alarm Settings – Triggers tab

State triggers are set off as soon as a state threshold or condition is achieved. You cannot define condition lengths for state alarms.

Note: You cannot use a virtual machine's Total Size on Disk or VM Snapshot Size triggers in combination with any other triggers.

To add a new alarm trigger:

  1. Click Add.
  2. In the Trigger Type dropdown, click VM Snapshot Size (GB).
  3. In the On Condition dropdown, click Is above.
  4. Double-click the Warning field and enter the desired value.
  5. Double-click the Alert field and enter the desired value.
0 Kudos