<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>RE: [Nagios-users] Nagios configuration for SAN monitoring</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi,<BR>
<BR>
recently got these working and I'll tell you what I've learned.<BR>
<BR>
i don't know if it's a bug in the brocade snmp implementation, but getsnmp and check_brocade_port both report an admin down port, even when the port is admin up and the cable is unplugged. this is a problem to me, but i just set up alarms for a WARNING.<BR>
<BR>
i use cacti for RRD monitoring. i found PNP too cumbersome.<BR>
<BR>
this command is different from the check_ping as it does not use the IP stack for availability. you have to set this up as a service and monitor accordingly. unfortunately, monitoring a FC SAN is much different from monitoring an Ethernet network.<BR>
<BR>
bill<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Jim Avery [<A HREF="mailto:jim@jimavery.me.uk">mailto:jim@jimavery.me.uk</A>]<BR>
Sent: Mon 2/23/2009 1:02 PM<BR>
To: nagios-users@lists.sourceforge.net<BR>
Subject: Re: [Nagios-users] Nagios configuration for SAN monitoring<BR>
<BR>
2009/2/21 Sonika Sachdeva <replysonika@gmail.com>:<BR>
> Hello List,<BR>
><BR>
> I have nagios basic configuration up and running as per the quickstart<BR>
> guide.<BR>
> I also have SNMP4nagios installed and running and the command works from the<BR>
> command line as follows<BR>
><BR>
> /usr/local/bin/check_brocade_port -H x.x.x.x -C mystring -T -i 5 -I addinf<BR>
> OK - Port 5: I: 527243 kFCW, 1109528922 FCF; O: 1204391 kFCW, 2066880039<BR>
> FCF|addinf;6;1;539897616;1233297068;1109528922;2066880039<BR>
> How do I integrate this command in nagios and start the logging and graphing<BR>
> functionality for brocade ports. can someone point me to a tutorial/guide.<BR>
><BR>
> Has someone used nagios for SAN monitoring?<BR>
<BR>
<BR>
Using the check_brocade_port plugin is not much different to using<BR>
check_ping in your default Nagios install. You need to define the<BR>
command, hosts and services in your Nagios configuration files.<BR>
<BR>
If you find the supplied documentation difficult to follow, there are<BR>
various books available commercially. A search for "Nagios" on the<BR>
website of your favourite bookstore will no doubt show a few to choose<BR>
from. The book I used to recommend (Nagios by Wolfgang Barth<BR>
published by No Starch Press) gives an excellent introduction but<BR>
unless it's been updated it won't include a lot of useful stuff new in<BR>
version 3. I'm not sure which book is the best today, but there was a<BR>
recent discussion on the topic here on the mailing list.<BR>
<BR>
I use Nagios to receive SNMP traps from the SAN storage manager<BR>
software. I use snmptt to receive the traps and NagTrap to store them<BR>
in a database and handle them in the web front-end. I confess I<BR>
haven't tried using the check_brocade plugins.<BR>
<BR>
<A HREF="http://www.snmptt.org/">http://www.snmptt.org/</A><BR>
<A HREF="http://nagtrap.org/doku.php/en:start">http://nagtrap.org/doku.php/en:start</A><BR>
<BR>
Cheers,<BR>
<BR>
Jim<BR>
<BR>
------------------------------------------------------------------------------<BR>
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA<BR>
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise<BR>
-Strategies to boost innovation and cut costs with open source participation<BR>
-Receive a $600 discount off the registration fee with the source code: SFAD<BR>
<A HREF="http://p.sf.net/sfu/XcvMzF8H">http://p.sf.net/sfu/XcvMzF8H</A><BR>
_______________________________________________<BR>
Nagios-users mailing list<BR>
Nagios-users@lists.sourceforge.net<BR>
<A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A><BR>
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<BR>
::: Messages without supporting info will risk being sent to /dev/null<BR>
<BR>
______________________________________________________________________<BR>
This inbound email has been scanned by the MessageLabs Email Security System.<BR>
______________________________________________________________________<BR>
<BR>
</FONT>
</P>
<DIV> </DIV><br><br>Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. <br><br><br></BODY>
</HTML>