Check_SNMP_INT.PL help needed

[Sam Reynolds]

Thanks!

-----Original Message-----
From: Patrick Proy [mailto:nagios-user at proy.org] 
Sent: Friday, February 11, 2005 8:27 AM
To: Sam Reynolds; nagios-users at lists.sourceforge.net
Subject: RE: [Nagios-users] Check_SNMP_INT.PL help needed

Hi,

The "No usable data on file (3 rows)" means the script can't make an average
because he hasn't got enough data.

By default (or use the -d option) he will look at the last value and a value
between 4'30 and 15' earlier. So you just have to wait 5 minutes between 2
checks (when doing it by hand) and it will give you the bandwidth.


Patrick
nagios AT proy.org

________________________________

De : nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] De la part de Sam Reynolds
Envoyé : jeudi 10 février 2005 19:22 À : nagios-users at lists.sourceforge.net
Objet : [Nagios-users] Check_SNMP_INT.PL help needed



Thanks for the help!  That was the issue.  Although I am now having an issue
that says "Serial5/2:UP No usable data on file (3 rows) :(1 UP): UNKNOWN".
I look in the tmp file that was created and there is data there.  The
command I am using is check_snmp_int.pl -H 127.0.0.1 -C <community name> -n
Serial5/2 -k -w 200,400 -c 0,0 (IP and community name are real when I put in
the command).  I was expecting to determine what kind of bandwidth I am
using on this interface.  

 

If I am using the wrong tool for this please let me know.

 

Thanks,

 

Sam




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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