Antwort: RE: MRTG graphs problem - measurement units not taken into consideration

[Radu.Popa at technomatic.de]

Ok,

Here is what I got so far:

1. If I run the command: ./check_snmp_int.pl -H 192.168.2.1 -C public -2 
-n GigabitEthernet0/24 -fY -kqB -g -w 600000,600000,100,100,100000,10 -c 
800000,800000,200,200,200000,20 -d 5 , I get the following output:
GigabitEthernet0/24:UP (16.9Kbps/26.2Kbps/0.0/0.0/0.0/0.0):1 UP: OK | 
'GigabitEthernet0/24_in_bps'=16899;600000000;800000000;0;1000000000 
'GigabitEthernet0/24_out_bps'=26237;600000000;800000000;0;1000000000

Before getting a correct output I run the command several times. The 
initial output is GigabitEthernet0/24:UP No usable data on file (102 rows) 
:(1 UP): UNKNOWN

2. Defined the following command in nagios:

define command{
        command_name    check_snmp_int
        command_line    $USER1$/check_snmp_int.pl -H $HOSTADDRESS$ -C 
$USER5$ -2 -n $ARG1$ -fY -kqB -g -w $ARG2$ -c $ARG3$ -d $ARG4$
        }

Where 

And the corresponding service check:

define service{
        use                     generic-service,pnpgraphed-service      ; 
Inherit values from a template
        host_name               test_sw
        service_description     Port 24 Bandwidth Usage
        check_command 
check_snmp_int!"GigabitEthernet0/24"!600000,600000,100,100,100000,10!800000,800000,200,200,200000,20!10
        normal_check_interval   2               ; Check the service every 
2 units under normal conditions
        retry_check_interval    1               ; Re-check the service 
every 1 unit until its final/hard state is determined
        }

In nagios service status I get now: ERROR: Description table : No response 
from remote host "192.168.2.1". 

In resources I have defined $USER5$=Public

Ideas, please?

Thank you!


Von:    Radu Popa/Technomatic
An:     nagios-users at lists.sourceforge.net
Datum:  06/28/2011 05:14 PM
Betreff:        RE: MRTG graphs problem - measurement units not taken into 
consideration


I have tried the SNMP plugin a few minutes ago and here is what I get when 
running it from the command line:

./check_snmp_int.pl -H 192.168.2.1 -C public -n GigabitEthernet0/24 -k -w 
200,400 -c 0,600
GigabitEthernet0/24:UP No usable data on file (1 rows) :(1 UP): UNKNOWN

The interface name I took it from listing all available interfaces on the 
switch.

Any ideas, please?

Thanks!




Von:    Radu Popa/Technomatic
An:     nagios-users at lists.sourceforge.net
Datum:  06/28/2011 03:31 PM
Betreff:        MRTG graphs problem - measurement units not taken into 
consideration


Hello,

I am using Nagios to monitor the bandwidth usage of a couple of 
switches/routers via the check_local_mrtgtraf command. The graphs I handle 
via pnp4nagios. The problem I encounter is the following: if the monitored 
bandwidth is at one point expressed in KB/s and then I bring a lot of 
traffic through the router the, unit is changed into MB/s. The graphed 
values seem not to take into consideration the change of the measurement 
unit meaning that the 50KB/s seems to be at the same height as the 50MB/s 
value in the graph.

Can anyone please help?

Thank you!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20110629/d8119ae8/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
-------------- next part --------------
_______________________________________________
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