[Nagios-users] Antwort: Re: Antwort: Bandwidth Usage on a linux Box

2010-03-30 Thread Sascha . Runschke
 [r...@pc-fedora-1 libexec]# ./check_snmp_int.pl  -H x.x.x.x -C xxx 
 -n eth0 -r -fY -k -w 100,100 -c 200,200 -d 40
 eth0:UP (12.2KBps/20.6KBps):1 UP: OK | 'eth0_in_Bps'=12506;102400;
 204800;0;125 'eth0_out_Bps'=21068;102400;204800;0;125
 
 As you can see the output has the following: eth0_in_Bps=12506;
 102400;204800;0;125
 
 Could you explain what they indicate , i know of only in Bytes per 
 second , what are the other 4 values ?
 Is it something like in Discards , in Errors  Etc.

No, you have to activate the check for discards manually via a
parameter.
The four values in question are: Warning, Critical, Minimum, Maximum

Warning and Critical have been set by yourself via -w and -c.
Minimum and Maximum contain the theoretical values
that the interface can give by range [minimum - maximum].
Those values are supplied by the snmpd if mib. They can be overriden
in the remote snmpd.conf if desired.

Regards
Sascha



GFKL Financial Services AG
Vorstand: Jürgen Baltes, Peter Blaschkowski
Vorsitzender des Aufsichtsrats: Wilhelm Plumpe
Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
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] Antwort: Re: Antwort: Bandwidth Usage on a linux Box

2010-03-30 Thread Jatin Davey

Thanks Sascha.

Thanks
Jatin

On 3/30/2010 5:27 PM, sascha.runsc...@gfkl.com wrote:

 [r...@pc-fedora-1 libexec]# ./check_snmp_int.pl  -H x.x.x.x -C xxx
 -n eth0 -r -fY -k -w 100,100 -c 200,200 -d 40
 eth0:UP (12.2KBps/20.6KBps):1 UP: OK | 'eth0_in_Bps'=12506;102400;
 204800;0;125 'eth0_out_Bps'=21068;102400;204800;0;125

 As you can see the output has the following: eth0_in_Bps=12506;
 102400;204800;0;125

 Could you explain what they indicate , i know of only in Bytes per
 second , what are the other 4 values ?
 Is it something like in Discards , in Errors  Etc.

No, you have to activate the check for discards manually via a
parameter.
The four values in question are: Warning, Critical, Minimum, Maximum

Warning and Critical have been set by yourself via -w and -c.
Minimum and Maximum contain the theoretical values
that the interface can give by range [minimum - maximum].
Those values are supplied by the snmpd if mib. They can be overriden
in the remote snmpd.conf if desired.

Regards
Sascha


GFKL Financial Services AG
Vorstand: Jürgen Baltes, Peter Blaschkowski
Vorsitzender des Aufsichtsrats: Wilhelm Plumpe
Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522


--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev


___
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
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
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