Connect Open-E DSS V7 to a NIS Server
Got 12 minutes to spare? You can tune in to our new webcast and explore…
Read MoreSystem monitoring is an important part of daily administrative tasks. Following our recent webinars, showing the ways we can monitor our Open-E DSS V7, we decided to prepare a how-to instruction for you.
This article is outdated as the functionality has been improved. In order to get the updated information, go to the article: Monitoring Open-E DSS V7 and Open-E JovianDSS with Check_MK
We will show you how to configure the necessary tools, update your Open-E DSS V7 and finally, access and use the monitoring interface.
Before we jump into a configuration process, you may need a quick introduction to the tools we will mention in this post.
Nagios is one of the most popular open-source monitoring software applications. It offers monitoring and alerting for servers, switches, applications and services.
OMD (Open Monitoring Distribution) bundles Nagios together with many important add-ons and can easily be installed on every major Linux distribution. Using it, we can avoid compiling and integrating Nagios add-ons manually.
Check_mk is a status GUI written in Python which supports user definable views and is able to display the status of several sites in one combined view. A very intuitive design and an easy operation are one of the strongest points of this tool.
The following instruction was made in Ubuntu. However, a similar configuration can be made in other Linux distributions.
We start with the installation and configuration of OMD packages. Please follow the steps below:
apt-get update
apt-get upgrade
In addition you can upgrade your distribution’s kernel:
apt-get dist-upgrade
*You may need to use “sudo su –” command, as Ubuntu do not login root by default.
gpg --keyserver keys.gnupg.net --recv-keys F8C1CA08A57B9ED7
gpg --armor --export F8C1CA08A57B9ED7 | apt-key add -
echo 'deb http://labs.consol.de/OMD/ubuntu precise main' >> /etc/apt/sources.list
apt-get update
apt-get install omd-0.56
Following the installation of OMD repository, we go to our Open-E DSS V7 server to perform an additional configuration and install a small update.
To install the necessary update, we need to log in to our Open-E DSS V7 GUI and do the following:
After the installation, the small update will be visible in the menu (it can be removed by clicking on the trash bin).
mkdir /mnt/test
mount –t nfs 192.168.232.60:/test /mnt/test
omd create dssmonitor
What you get is:
omd start
We are now ready to perform an additional configuration of OMD.
mcedit /opt/omd/sites/dssmonitor/etc/check_mk/main.mk
all_hosts = [‘192.168.232.60|ssh’]
datasource_programs = [ (“ssh –p default port number – i ssh key's location path –l username for API + host IP + command that will be run over API to DSS, [‘protocol used’] , in which section our monitoring statuses will be shown), ]
In our case, it will be:
datasource_programs = [ (“ssh –p 22223 –i /omd/dss60.key –l api 192.168.232.60 check_mk_agent”, [‘ssh’], ALL_HOSTS ), ]
chown dssmonitor /omd/dss60.key
chmod 500 /cmd/dss.key
su dssmonitor
ssh –p 22223 –i /omd/dss60.key –l api 192.168.232.60 check_mk_agent
When prompted to continue connecting type yes.
The output will be returned in the terminal, which will later be interpreted in check_mk tool.
check_mk -I
The second, will reload the OMD configuration and validate that it is working properly:
check_mk -O
192.168.232.58/dssmonitor
*you can check the IP of your Ubuntu using the ifconfig command
Username: omdadmin
Password: omd
You will then see the statuses of all available services (that are being monitored by the tool):
You will also have access to detailed statistics (including graphs) about each service:
The services that you can monitor with the tool include:
Check out the videos below and watch our engineers performing the same configuration (English and German version).
15 Comments
Denny
March 20, 03 2013 01:03:59hi,
I have already a fully install Icinga server and installed the small updated (check_mk_agent) plugin for DSS7, but the first test fails:
icinga@icinga:~/.ssh$ ssh -p 22223 -i id_dsa_iscihead-s -l api 192.168.1.100 check_mk_agent
CLI/API: method not found
So, what could be the problem?
cu denny
Denny
March 20, 03 2013 01:36:34hi,
fixed it by myself. I missed the reboot 🙂
Kasia Kolodziej
March 20, 03 2013 01:50:05Hey Denny! Glad you found a solution! A lot of people forget to reboot the server after applying the small update.
rajmundo
April 10, 04 2013 08:34:19The link to SU is broken!!! Please correct it…
regards!
Dominik Niewiadomy
April 12, 04 2013 12:40:35Hi rajmundo! Many thanks for your info, the link is now updated. In case of any issues, please contact our technical support.
martin
July 03, 07 2013 09:05:53Hi.
Thank you so much for adding nagios support – finally!!!
However there are two problems here, (installing small update and configuring nagios or icinga in this case is no problem), setup is a active-active cluster (of course both servers are identical), both problems on both servers.
1) check_mk reports a critical state for drbd:
“DRBD drbd8 status”
“CRIT – Connection State: WFConnection, Roles: Secondary/Unknown, Disk States: UpToDate/Outdated”
But in open-e dashboards all resources are “OK” (volumes, replication and so on, nor error logs).
So How do I see which ope-e volume is DRDB8? and how can I fix it? why does check_mk report a problem that is not visible in open-e webfrontend?
2) check_mk reports a “unknown” status for something:
“RAID Unit 0 Optimal”
“UNKNOWN – invalid output from agent, invalid check parameters or error in implementation of check dss_raid. Please set debug_log to a filename in main.mk for enabling exception logging.”
Logfile:
Invalid output from plugin or error in check:
Check_MK Version: 1.2.2p2
Date: 2013-03-07 10:49:37
Host: 10.0.0.12
Service: RAID Unit 0 Optimal
Check type: dss_raid
Item: ‘0 Optimal’
Parameters: None
Traceback (most recent call last):
File “/var/lib/check_mk/precompiled/10.0.0.12”, line 702, in do_all_checks_on_host
^A^N^A^R^B^F^A^F^A^F^A^C^A^U^A1^B^R^A^Q^B^L^B^R^A^Q^B^L^B^P^A^R^A^F^A^Q^A^R^A^F^A^Q^B^F^A^O^A
File “/var/lib/check_mk/precompiled/10.0.0.12”, line 1484, in check_dss_raid
IndexError: list index out of range
Agent info: [[‘LSI;0’, ‘0;Optimal’, ‘Drives#;2’],
[‘0;Optimal’, ‘Drives#;2’],
[‘0;Optimal’, ‘Drives#;15’]]
So what is going on here? Which RAID unit is this? The checks of the Logical Volumes of the RAID Controller ae somewhere else…
Thank you so far
Regards
Martin
Kasia Kolodziej
July 04, 07 2013 08:17:55Hello Martin! Nagios lists all volumes that have drbd enabled. Any chances one of them is not configured in failover or not connected at the moment?
Open-E DSS failover manager monitors only volumes that have been configured in your cluster.
If you are still having issues, please open a support ticket with up-to-date logs so our team can investigate if everything is set up correctly.
martin
July 04, 07 2013 12:45:36Hello Kasia.
Yes, quite sure that all volumes are (or should be?) configured in failover setup.
Who can I see the assignments DRBDopen-e volume names? With only the DRBD name, and no hint which open-e volume is meant, the information is quite useless…
Any ideas for the second problem?
Another question: I recognized that you are using a very, very old megacli ” Ver 1.01.09 May 25, 2006″. Is there any plan to upgrade to a current version?
Thank you for your help
Regards
Martin
Kasia Kolodziej
July 09, 07 2013 02:13:41Martin,
In regards to you first issue, the check is an original check of check_mk and was not modified by our team. Name is drbd minor and can be found in logs in /drbd directory log files. We can improve this check to be more user friendly if requested in a support ticket.
As for the second problem, please make sure you are using the same version of Small Update as check files for nagios. Link to the most recent one can be found in the post.
Checks are still being developed and constantly improved.
It is also possible that your RAID is returning some strange state that was not recognized during the implementation. Please open a support ticket with logs from your system to confirm.
Finally, yes there is new MegaCli available. Please open a support ticket to receive this small update.
Matthias Raithel
August 13, 08 2013 10:44:57Ok.. am I right in thinking that there’s no way aound check_mk here if i want my open-E monitored by nagios?
I’m also very interested in knowing about the low level state of things (raid controller)
Any chances there?
Kasia Kolodziej
August 20, 08 2013 07:26:50Hey Matthias. There is a plugin available for check_mk and for RAID support. Please open a support ticket to receive it.
You can also use basic SNMP MIBs.
Joey Hazlett
January 12, 01 2016 05:30:18Is it possible to gather RAID information with raw SNMP? It looks like check_mk is a “comprehensive IT monitoring solution.” I already have my own IT monitoring solution in a custom configuration of Nagios that is monitoring the rest of my network. I just want to know immediately if one of my disks has failed without having to constantly log into the web GUI. If I can just figure out what OIDs I need to read to get this information from SNMP, I can use check_snmp to gather and report the information. Is this possible without completely changing my monitoring architecture?
karolina.pletnia
January 14, 01 2016 01:24:23Hey Joey! We recently prepared an LSI SNMP Agent for Open-E DSS V7. It is not yet included in an official release, but if a customer opens the support ticket, he may receive Small Update with this functionality. For other RAID brands fetching SNMP data is not available.
Michael Wahlbrink
August 08, 08 2016 09:43:47Hi,
is the SNMP support for the LSI Raid adapters included in the current Version? At a customer site we introduce a new SNMP solution and I was asked if we can monitor the 3 Open-E DSS V7 Servers they have.
(Or is it only available via a charged support request?)
Regards
Micha
Karolina Pletnia
August 10, 08 2016 11:29:34Hello Michael,
the SNMP support for the LSI Raid adapters is included in the current version of the software – up56 build 19059.