Monitoring the temperature in the server drains using SCOM 2007 and Sensatronics Em1, suitable for configuring any devices working on SNMP
Monitoring the temperature in the server's sinks using SCOM 2007 and Sensatronics Em1 is suitable for configuring any devices running via SNMP.
+ 
A brief note on how to configure temperature monitoring and creating alerts in the System Center Operations Manager 2007 R2 monitoring system collecting SNMP information from Sensatronics equipment, the lack of a management pack for this equipment was confirmed by both Russian salesmen and an official representative from the United States. I had a model EM1 and two sensors with the ability to take readings of temperature and humidity and is currently testing the installed version of SCOM 2007 R2.
')
I repeat that there are no management packs for Sensatronics under SCOM 07, you can view the figures through the browser by accessing the rather laconic page of the device.
It looks like this:
The page itself is updated, but to keep it constantly open and to look from time to time is still a pleasure. By the way, one of the ways to display data from a device in Nagios is based on loading the device’s web page and “cutting out” data from it. Such a scheme once worked. But now we are talking about OpsMgr and there is no such possibility in it. The conclusion itself suggests itself - the device supports SNMP version 1 - SCOM supports this method, but the path to the display was not easy.
Mainly because of the guru SCOM'a respected by me from the resource opsmgr.ru (see references 1, 2, 3), as well as a specialist from netwizard.com.ua (4) and a pair of foreign experts (5, 6). Almost convinced me of the need to develop a Management Pack (management pack), while necessarily writing it in xml, re-enjoy for a couple of evenings. I hope the manufacturers of products mating with SCOM will really help these articles to release MP along with the product being released.
Our task is somewhat simpler, just display the readings and receive notifications when exceeding the permissible indicators send warnings to responsible persons.
I will give a number of steps to configure SCOM 2007 R2.
First we need a Mib device for reading OIDs, you can usually find it on the manufacturer’s website or link number (7) will help you. You can read mibs with different programs, I used MibBrowser (8).
We load the Mib we need, we drive in all the necessary data for the connection (ip, SNMP version and community string), select the parameter we need from the forest and get its OID.
We open Operations Console we start setup.
First, you need to add devices to the console, I did not want to describe it in great detail. Everything is in the help, but for the sake of completeness, we’re looking right here.
Go to the administration section:
Open the discovery wizard via the context menu.
Select the item network devices and continue.
Fill in the parameters and run the detection.
If the search is positive, you will see all the devices found in the range you specified, check all the devices you need to add.
The device is added now proceed to the settings of monitors and rules.
Go to the section "Authoring" (Creation and configuration).
In the Rules section we make new
In order to make it easier to navigate, create a new MP:
Everything can be filled arbitrarily, in no way does it affect the work, only on its display in the console.
Created, choose it.
The rule type is selected based on performance, SNMP performance.
The next step is to choose the name of the rule, the category “other” and the target “Network devices SNMP”.
Now we will decide how often we will interrogate the device for receiving data (I left two minutes).
And also drove the OID for the temperature indicator of 3 groups of sensors on the device.
1.3.6.1.4.1.16174.1.1.3.3.3.3.0 - notice that all objects are written to SCOM without the first dot
Finished - click "Create" and wait for the wizard to complete. And so need to do for each of the sensors. I give the list of OIDs you need below.
Group1
Temperature - 1.3.6.1.4.1.16174.1.1.3.3.1.3.0
Humidity - 1.3.6.1.4.1.16174.1.1.3.3.1.6.0
Group2
Temperature - 1.3.6.1.4.1.16174.1.1.3.3.2.3.0
Humidity - 1.3.6.1.4.1.16174.1.1.3.3.2.6.0
Group3
Temperature - 1.3.6.1.4.1.16174.1.1.3.3.3.3.0
Humidity - 1.3.6.1.4.1.16174.1.1.3.3.3.6.0
Group4
Temperature - 1.3.6.1.4.1.16174.1.1.3.3.4.3.0
Humidity - 1.3.6.1.4.1.16174.1.1.3.3.4.6.0
At the end, we can be sure that data from your device is collected.
Now, all this would be displayed in some form, but first, to easily find the sensors of our device, we will create a group for it by which we will make a sample to display in the future performance view.
Go to the section "Authoring" (Creation and configuration).
And create a new group:
In the explicit members through the search wizard, we select the device we need from the list (if there are other SNMP devices).
Other steps of the wizard are skipped, not about them now, at the last step we poke to create. Thus, we have a group that contains our device, you can make sure that the device is working by clicking on the view group members.
We see what they should see.
Go to monitoring mode
And create a new performance view.
With the following parameters.
This creates such a view, you can set the time ranges to display, the color of the lines, etc.
The first task is completed.
Now we will create monitors for triggering alerts. Again, go to the section "Authoring" (Creating and setting).
And in the section Monitors for SNMP network devices we create a basic monitor in the section availability.
We will do it on the basis of SNMP checks, the translation is of course funny in the Russian version, but we are doing the monitor based on sensing and detecting simple rules.
The next step carries almost nothing except the name, the choice of the parent and the target object.
Now we specify the OID of the sensor being checked, it will be a temperature sensor from the third group with OID - 1.3.6.1.4.1.16174.1.1.3.3.3.3.0
Specify parameters
/ DataItem / SnmpVarBinds / SnmpVarBind [1] / Value , less than 28.
Which means if the parameter being taken is greater than or equal to 28 degrees, everything is bad.
Then we go through the same procedure as in the third step, indicating the OID being checked.
Again for the second expression we do the same, only the operator is now greater than or equal to 28.
Next we associate states with expressions.
And set up alerts. In the description, we can indicate the temperature that was at the time when the monitor was triggered by writing the following expression:
$ Data / Context / SnmpVarBinds / SnmpVarBind [1] / Value $
Everything. Now we can create several monitors for each of our sensors.
As a result, we have a completely visual display of what is happening in the server room.
Good luck to you monitoring.
References:
1) http://opsmgr.ru/Lists/Posts/Post.aspx?ID=157
2) http://opsmgr.ru/Lists/Posts/Post.aspx?ID=159
3) http://opsmgr.ru/Lists/Posts/Post.aspx?ID=162
4) http://netwizard.com.ua/2009/09/11/monitoring-cisco-na-platforme-microsoft-scom-2007-ch-2/
5) http://rburri.wordpress.com/2008/04/29/snmp-discovery-provider-for-opsmgr-2007/
6) http://svintinner.blogspot.com/2008/05/example-snmp-management-pack-for-scom.html
7) http://www.snmplink.org/snmpresource/mib/
8) http://www.ireasoning.com/mibbrowser.shtml
9) http://galushka.com/systemcenteroperationsmanager2007r2sensatronicsem1/
+ A brief note on how to configure temperature monitoring and creating alerts in the System Center Operations Manager 2007 R2 monitoring system collecting SNMP information from Sensatronics equipment, the lack of a management pack for this equipment was confirmed by both Russian salesmen and an official representative from the United States. I had a model EM1 and two sensors with the ability to take readings of temperature and humidity and is currently testing the installed version of SCOM 2007 R2.
')
I repeat that there are no management packs for Sensatronics under SCOM 07, you can view the figures through the browser by accessing the rather laconic page of the device.
It looks like this:
The page itself is updated, but to keep it constantly open and to look from time to time is still a pleasure. By the way, one of the ways to display data from a device in Nagios is based on loading the device’s web page and “cutting out” data from it. Such a scheme once worked. But now we are talking about OpsMgr and there is no such possibility in it. The conclusion itself suggests itself - the device supports SNMP version 1 - SCOM supports this method, but the path to the display was not easy.
Mainly because of the guru SCOM'a respected by me from the resource opsmgr.ru (see references 1, 2, 3), as well as a specialist from netwizard.com.ua (4) and a pair of foreign experts (5, 6). Almost convinced me of the need to develop a Management Pack (management pack), while necessarily writing it in xml, re-enjoy for a couple of evenings. I hope the manufacturers of products mating with SCOM will really help these articles to release MP along with the product being released.
Our task is somewhat simpler, just display the readings and receive notifications when exceeding the permissible indicators send warnings to responsible persons.
I will give a number of steps to configure SCOM 2007 R2.
First we need a Mib device for reading OIDs, you can usually find it on the manufacturer’s website or link number (7) will help you. You can read mibs with different programs, I used MibBrowser (8).
We load the Mib we need, we drive in all the necessary data for the connection (ip, SNMP version and community string), select the parameter we need from the forest and get its OID.
We open Operations Console we start setup.
First, you need to add devices to the console, I did not want to describe it in great detail. Everything is in the help, but for the sake of completeness, we’re looking right here.
Go to the administration section:
Open the discovery wizard via the context menu.
Select the item network devices and continue.
Fill in the parameters and run the detection.
If the search is positive, you will see all the devices found in the range you specified, check all the devices you need to add.
The device is added now proceed to the settings of monitors and rules.
Go to the section "Authoring" (Creation and configuration).
In the Rules section we make new
In order to make it easier to navigate, create a new MP:
Everything can be filled arbitrarily, in no way does it affect the work, only on its display in the console.
Created, choose it.
The rule type is selected based on performance, SNMP performance.
The next step is to choose the name of the rule, the category “other” and the target “Network devices SNMP”.
Now we will decide how often we will interrogate the device for receiving data (I left two minutes).
And also drove the OID for the temperature indicator of 3 groups of sensors on the device.
1.3.6.1.4.1.16174.1.1.3.3.3.3.0 - notice that all objects are written to SCOM without the first dot
Finished - click "Create" and wait for the wizard to complete. And so need to do for each of the sensors. I give the list of OIDs you need below.
Group1
Temperature - 1.3.6.1.4.1.16174.1.1.3.3.1.3.0
Humidity - 1.3.6.1.4.1.16174.1.1.3.3.1.6.0
Group2
Temperature - 1.3.6.1.4.1.16174.1.1.3.3.2.3.0
Humidity - 1.3.6.1.4.1.16174.1.1.3.3.2.6.0
Group3
Temperature - 1.3.6.1.4.1.16174.1.1.3.3.3.3.0
Humidity - 1.3.6.1.4.1.16174.1.1.3.3.3.6.0
Group4
Temperature - 1.3.6.1.4.1.16174.1.1.3.3.4.3.0
Humidity - 1.3.6.1.4.1.16174.1.1.3.3.4.6.0
At the end, we can be sure that data from your device is collected.
Now, all this would be displayed in some form, but first, to easily find the sensors of our device, we will create a group for it by which we will make a sample to display in the future performance view.
Go to the section "Authoring" (Creation and configuration).
And create a new group:
In the explicit members through the search wizard, we select the device we need from the list (if there are other SNMP devices).
Other steps of the wizard are skipped, not about them now, at the last step we poke to create. Thus, we have a group that contains our device, you can make sure that the device is working by clicking on the view group members.
We see what they should see.
Go to monitoring mode
And create a new performance view.
With the following parameters.
This creates such a view, you can set the time ranges to display, the color of the lines, etc.
The first task is completed.
Now we will create monitors for triggering alerts. Again, go to the section "Authoring" (Creating and setting).
And in the section Monitors for SNMP network devices we create a basic monitor in the section availability.
We will do it on the basis of SNMP checks, the translation is of course funny in the Russian version, but we are doing the monitor based on sensing and detecting simple rules.
The next step carries almost nothing except the name, the choice of the parent and the target object.
Now we specify the OID of the sensor being checked, it will be a temperature sensor from the third group with OID - 1.3.6.1.4.1.16174.1.1.3.3.3.3.0
Specify parameters
/ DataItem / SnmpVarBinds / SnmpVarBind [1] / Value , less than 28.
Which means if the parameter being taken is greater than or equal to 28 degrees, everything is bad.
Then we go through the same procedure as in the third step, indicating the OID being checked.
Again for the second expression we do the same, only the operator is now greater than or equal to 28.
Next we associate states with expressions.
And set up alerts. In the description, we can indicate the temperature that was at the time when the monitor was triggered by writing the following expression:
$ Data / Context / SnmpVarBinds / SnmpVarBind [1] / Value $
Everything. Now we can create several monitors for each of our sensors.
As a result, we have a completely visual display of what is happening in the server room.
Good luck to you monitoring.
References:
1) http://opsmgr.ru/Lists/Posts/Post.aspx?ID=157
2) http://opsmgr.ru/Lists/Posts/Post.aspx?ID=159
3) http://opsmgr.ru/Lists/Posts/Post.aspx?ID=162
4) http://netwizard.com.ua/2009/09/11/monitoring-cisco-na-platforme-microsoft-scom-2007-ch-2/
5) http://rburri.wordpress.com/2008/04/29/snmp-discovery-provider-for-opsmgr-2007/
6) http://svintinner.blogspot.com/2008/05/example-snmp-management-pack-for-scom.html
7) http://www.snmplink.org/snmpresource/mib/
8) http://www.ireasoning.com/mibbrowser.shtml
9) http://galushka.com/systemcenteroperationsmanager2007r2sensatronicsem1/
Source: https://habr.com/ru/post/88583/
All Articles