I’ll open with a statement: 3rd party VMWare management packs have their own benefits and you may find this post too light for your monitoring definition.
monitoring ESX Servers could be done in few ways… all based syslog, snmp & DB querying because no agent is available…
After short research I’ve found it very convenient to use VMWare vCenter’s monitoring capabilities…
so… a quick brief:
VMware vSphere has a powerful alerting \ notification system built in called “Alarms”. Alarms can be configured to trigger when specific events, conditions, or states occur in the vSphere infrastructure.
Alarms can be configured at various levels of the VMware host, VM, datacenter, and cluster level.
more about vCenter Alrams you could read here:
To the job !
- Configure the SNMP Service on vCenter Server.
- Discover the vCenter server as SNMP device.
- Configure the SNMP target in the vCenter UI.
- Configure Alarms to be sent to SCOM.
- Create New SNMP Alerting rule for vCenter
Step 1, make sure you have installed the SNMP service on the vCenter server and configure it to send traps to SCOM Server
Step 2, Discover the vCenter server as SNMP device. Administration -> Discovery Wizard -> Network Devices:
Step 3, Configure the SNMP target in the vCenter UI:
Navigate to “home” tab, under “administration” choose “vCenter Server Settings” -> Choose SNMP from the settings and config the Receiver URL with the SCOM server FQDN and the community string you have set in your SCOM server’s SNMP service:
Step 4, Ready ? Steady, GO ! … Let’s monitor !
Navigate back to “VMs and Templates”, choose the node type you wish to start with, in my screenshots I’ve chosen Datacenter node. after choosing the relevant node, in the right side of the pane navigate to “Alarms”, click the definitions button and.. WALLA !
by default, not all of these alarms are configured to alert so now you have to review all of these and decide what is important to you and tune it as you need, double clicking alarm will open a configuration windows which let you configure thresholds for alert triggering :
As you can see, you can configure Warning & Critical conditions. after done with tuning the alarm, navigate to “Actions” tab to configure the action for alert :
After choosing “send a notification trap” configure in what condition trap would be sent and how (once \ repeated) :
- from: Healthy —> Warning
- from: Warning —> Critical
- from: Critical —> Warning
- from: Warning —> Healthy
Step 5, Create New SNMP Alerting rule for vCenter:
Choose SNMP Network Device as a Target. uncheck the “Rule is enabled” and enable the rule only for the vCenter network device we have discovered before by overriding the rule:
Because we tuning the alerts in the vCenter side I could feel good with myself while checking the “All Traps” checkbox:
Last step is to configure the alert context… you can wait for alert (or simulate one) to see what information in the alert context is needed for you and format it like in the image below:
That’s it. You could use this mechanism to create Monitors which will impact the vCenter state but I found it useless because we have one single object (vCenter as a network device) which represent a big infrastructure.