[Nagios-users] Check for the IBM ds4000 series totalstorage cabinett - FIX
Hi,
after the latest firmware upgrade to a IBM DS 4700, the Check for the IBM
ds4000 series totalstorage cabinet stopped working.
I made a small fix to the perl plugin, just 2 lines. To have the plugin
working with the latest cli, make this substitutions:
Line 164
Change
if($line=~/Array status:\s*([^\s]*)/i) {
with
if(($line=~/Array status:\s*([^\s]*)/i) || ($line=~/Status:\s*([^\s]*)/i)) {
Line 167
Change
if(!defined($array_status) || !($array_status=~/online/i)) {
with
if(!defined($array_status) || !(($array_status=~/online/i) ||
($array_status=~/optimal/i))) {
Done, now it should work. The latest upgrade changes the output of cli
messages, that's why the script doesn't work anymore. The fix traps the
old and new status messages.
Hope it helps
Cheers,
Giorgio Zarrelli
--
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] Check for the IBM ds4000 series totalstorage cabinett - FIX
Hi at all, I'm newbie on nagios and I'm writing here to ask you for suggestions abut how to structure my monitoring situation. I've to monitor linux servers for about 15/20 customers, from 1 to 5 server for each customer. We aren't on vpn with customers, so this servers are all behind NAT. That isn't a problem because we are the administrator of the firewall (other linux server) so we can manage any kind of DNAT and filter rule. I read on official documentation that suggest to use NCSA addon for distributed monitoring, but we choose to use NRPE addon for different motivations like: -customer force us to do that -the number of monitored servers for each customer will never grow up -the services to monitor for each server are the same (raid hw/sw, disk usage etc) -we need a completly centralized monitoring structure For last sentence I thought to use the arguments option on NRPE (yes, I read the SECURITY document). Besides, to solve the problem of NAT with NRPE I'll do DNAT on firewall and the port parameter on check_nrpe plugin (is there problems to do that? I did little tests but I prefear a confirm) To manage this structure I need to organized a well-formed config file structure on nagios server. I thinked to structure it like this obj--| |--templatelinuxserversgeneral.cfg | |--customer_1_directory|-templateserver.cfg | |-server1.cfg | |-server2.cfg | |-servern.cfg | |--customer_2_directory|-templateserver.cfg |-server1.cfg |-servern.cfg Where: -templatelinuxserversgeneral.cfg is a very basic template for server -customer_1_directory in wich there is 1 file for each customer's server -templateserver.cfg will use templatelinuxserversgeneral and will add more specific common variabiles for that customer's server like the public IPAddress that will be the same for each customer's server. -servern.cfg in wich there will be some very specific server variables like nrpe port (read up). What do you think? How can I organize that service-server combination? Thank's so much P.S. sorry for my bad english -- Enrico Zimol -- ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] Check for the IBM ds4000 series totalstorage cabinett - FIX
Hi, yes you can. I splitted all the major files in smaller files and nested directories, so it's easier for me to manage all the services and hosts. And I assure you, I have an heavy split configuration. quota chi=Enrico Zimol Hi at all, I'm newbie on nagios and I'm writing here to ask you for suggestions abut how to structure my monitoring situation. I've to monitor linux servers for about 15/20 customers, from 1 to 5 server for each customer. We aren't on vpn with customers, so this servers are all behind NAT. That isn't a problem because we are the administrator of the firewall (other linux server) so we can manage any kind of DNAT and filter rule. I read on official documentation that suggest to use NCSA addon for distributed monitoring, but we choose to use NRPE addon for different motivations like: -customer force us to do that -the number of monitored servers for each customer will never grow up -the services to monitor for each server are the same (raid hw/sw, disk usage etc) -we need a completly centralized monitoring structure For last sentence I thought to use the arguments option on NRPE (yes, I read the SECURITY document). Besides, to solve the problem of NAT with NRPE I'll do DNAT on firewall and the port parameter on check_nrpe plugin (is there problems to do that? I did little tests but I prefear a confirm) To manage this structure I need to organized a well-formed config file structure on nagios server. I thinked to structure it like this obj--| |--templatelinuxserversgeneral.cfg | |--customer_1_directory|-templateserver.cfg | |-server1.cfg | |-server2.cfg | |-servern.cfg | |--customer_2_directory|-templateserver.cfg |-server1.cfg |-servern.cfg Where: -templatelinuxserversgeneral.cfg is a very basic template for server -customer_1_directory in wich there is 1 file for each customer's server -templateserver.cfg will use templatelinuxserversgeneral and will add more specific common variabiles for that customer's server like the public IPAddress that will be the same for each customer's server. -servern.cfg in wich there will be some very specific server variables like nrpe port (read up). What do you think? How can I organize that service-server combination? Thank's so much P.S. sorry for my bad english -- Enrico Zimol -- ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null -- ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
