Set up Critical Alarms in Vcenter

Set up Critical Alarms in Vcenter

We have Network Operations users who work after business hours. I want to set up alarm notifications to be forwarded to  them, but just for very critical alarms, so that they can call the On-call person at night.

I wonder which Alarms should be considered as very critical and deserves a wake up call.

we have Vcenter and 6 ESX hosts and 150 VMs. DRS and HA enabled.

Actually  I do not want to set the alarms for VMs since there is Nagios used for that purpose.
I want to set up Critical alarms just for ESX servers, for instance if one of them crashes completely and  other ESXs did not pick up the High Avalibility, or CPU and/or RAM was High for quite a long time and the VMotion did not happen

Any help will be very much appreciated.

Thanks
jskfanAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
There are two levels, yellow (amber) and red.

We have a traffic light system which is green, yellow, red.

We use RED as critical, and Operations Staff in the DCs call us immediately.

AMBER, it's recorded, and they wait.....

Some alerts are either on of off, e.g. Snapshots, RED - Critical...

Storage Amber and Red, so you will need to adjust accordingly.

e.g.

CPU Amber - 75%
CPU Red - 95%
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Are you On-call person trained in VMware vSphere and know what todo, if these Critical Alarms are triggered?

e.g. if you define Host Disconnected is Critical, does the On-Call person know what to do, and how to fault find, or do you have a document which covers that?
0
 
jskfanAuthor Commented:
The On-Call person knows what to do with Alarms, but he is not allowed to set up Alarms...
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
I would set critical alarms for:-

1. Host Storage - datastore would zero storage would cause VMs to fail.
2. Host CPU - would cause performance issues with VMs
3. Host Memory - - would cause performance issues with VMs
4. Snapshots - would cause VM to fail.
5. Networking - would cause VMs to fail.

These would be based on our Critical errors list. (however, they may not be critical to your organisations, and SLAs and Service Delivery)
0
 
jskfanAuthor Commented:
*** Host CPU and Host Memory would not that cause Vmotion of the VMs to another host(s) ?
***I believe Vmware Vcenter when installed has some Default alarms already set up..among them Memory and CPU usage.. I could be wrong though
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
There are default alarms for Host CPU and Memory.

I would still have them enabled, we've seen times, when a VM gets stuck, or Host does not respond to any more vMotion (DRS) requests, and CPU and Memory goes high causing performance issues on the host, causing performance issues for ALL VMs on that host.
0
 
jskfanAuthor Commented:
Hancock:

Do you screenshots on how they are configured ? especially the Triggers are a little bit no clear.
0
 
jskfanAuthor Commented:
for some events Triggers are not intuitive
0
 
jskfanAuthor Commented:
Thanks
0
All Courses

From novice to tech pro — start learning today.