Re: [Nagios-users] check_snmp - warning numbers
I can`t see that information.
I don`t have 0.0.0.0:161
The problem is that I can`t add the port exeption in winxp, because some
admin had block it by policies from active directory.
I have acces to ActDir but I don`t know what is the policy blocks it
Sorry for my bad English
Matias...
-Mensaje original-
De: Jones, Stuart [mailto:stuart.jo...@health.wa.gov.au]
Enviado el: Domingo, 10 de Mayo de 2009 20:55
Para: Matias Blanco
Asunto: RE: [Nagios-users] check_snmp - warning numbers
When you do a
netstat -an
on the PC in question do you see something similar to:
0.0.0.0:161
i.e. the PC is listening on port 161 UDP?
Rgds Stuart
-Original Message-
From: Matias Blanco [mailto:mat...@valastro.com.ar]
Sent: Saturday, 9 May 2009 12:02 AM
To: 'Alejandro Sánchez Meroño'; Nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] check_snmp - warning numbers
Hello,
When i made an snmpwalk to a ip computer there is no response.
The snmpwalk to a switch,router or printer works ok.
Does any body know the reason?
Cristian...
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar] Enviado el: Jueves, 07
de Mayo de 2009 17:02
Para: 'Alejandro Sánchez Meroño'; Nagios-users@lists.sourceforge.net
Asunto: Re: [Nagios-users] check_snmp - warning numbers
Hello,
How can i do an snmpwalk on my switch?
Thanks,
Cristian...
-Mensaje original-
De: Alejandro Sánchez Meroño [mailto:alejandro.sanc...@ite.es] Enviado
el: Jueves, 07 de Mayo de 2009 05:44
Para: Matias Blanco; Nagios-users@lists.sourceforge.net
Asunto: RE: [Nagios-users] check_snmp - warning numbers
Hola de nuevo...
I'll answer you in English so that anybody in the list can understand
and participate in this subject.
I think that if you don't know exactly which parameter to monitor you
should browse the whole OID list that you receive when you do a snmpwalk
on your switch, and identify the ones that fit your needs, with the help
of the website I said yesterday, or any other OIDs reference.
My case: The only thing I want to detect is if there is any damaged port
in any of my switches. So what I did was to snmpwalk on a switch which I
positively knew that had its port #2 damaged, and discover which OID was
significantly different for this port. And the one I found is:
iso.3.6.1.2.1.10.7.2.1.7
(maybe you can find it as its equivalent: SNMPv2-SMI::mib-2.10.7.2.1.7)
defined as: a count of frames for which the first transmission attempt
on a particular interface is delayed because the medium is busy.
The thing is that it's the only OID I found that gave a very high value
for port #2 (about 65,000 or so) and 0 for the rest of ports that work
properly.
The command I defined for this was like this:
define command {
command_name check_port
command_line $USER1$/check_snmp -H $HOSTADDRESS$ -C password -O
iso.3.6.1.2.1.10.7.2.1.7.$ARG1$ -w 1 -c 10 -u retries }
For sure there must be somebody else in the list who can give to you a
more detailed or a more formally correct answer...
Hasta la proxima,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es Valencia - Spain
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar]
Enviado el: miércoles, 06 de mayo de 2009 19:27
Para: Alejandro Sánchez Meroño; Nagios-users@lists.sourceforge.net
Asunto: RE: [Nagios-users] check_snmp - warning numbers
Hola Alejandro,
Ahora otra cosa:
De que manera crees que pueda chequear los puertos de mi switch con
nagios para tener una idea más clara de lo que está sucediendo?
Porque esos paquetes entrantes con errores no se si son por causa de la
PC o de los puerto del switch...
Muchas Gracias...
Cristian
Hola Matías... :-) and hola everyone...
There exists a magical website where to identify every OID you can check
with SNMP, the link is:
http://support.ipmonitor.com/mibs_byoidtree.aspx
For your particular issue, if you type RFC1213-MIB at the Search
for: form, click the result given (RFC1213-MIB), and then View:
Oid-tree, you'll be able to locate ifInErrors(14) at the tree shown,
and clicking it you'll find its Description, which reads literally:
The number of inbound packets that contained errors preventing them
from being deliverable to a higher-layer protocol.
That's the answer to your question!!
Now some other questions appear...
Wouldn't it be nicer to know what exactly are you monitoring before you
monitor it, so you could properly interpret the results?
Is that parameter (number of inbound packets that contained errors and
blah blah blah...) significant enough to determine if a port is working
properly or not?
Hope this helps...
Best regards,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es Valencia - Spain
-Mensaje original
Re: [Nagios-users] check_snmp - warning numbers
Hello,
When i made an snmpwalk to a ip computer there is no response.
The snmpwalk to a switch,router or printer works ok.
Does any body know the reason?
Cristian...
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar]
Enviado el: Jueves, 07 de Mayo de 2009 17:02
Para: 'Alejandro Sánchez Meroño'; Nagios-users@lists.sourceforge.net
Asunto: Re: [Nagios-users] check_snmp - warning numbers
Hello,
How can i do an snmpwalk on my switch?
Thanks,
Cristian...
-Mensaje original-
De: Alejandro Sánchez Meroño [mailto:alejandro.sanc...@ite.es]
Enviado el: Jueves, 07 de Mayo de 2009 05:44
Para: Matias Blanco; Nagios-users@lists.sourceforge.net
Asunto: RE: [Nagios-users] check_snmp - warning numbers
Hola de nuevo...
I'll answer you in English so that anybody in the list can understand
and participate in this subject.
I think that if you don't know exactly which parameter to monitor you
should browse the whole OID list that you receive when you do a snmpwalk
on your switch, and identify the ones that fit your needs, with the help
of the website I said yesterday, or any other OIDs reference.
My case: The only thing I want to detect is if there is any damaged port
in any of my switches. So what I did was to snmpwalk on a switch which I
positively knew that had its port #2 damaged, and discover which OID was
significantly different for this port. And the one I found is:
iso.3.6.1.2.1.10.7.2.1.7
(maybe you can find it as its equivalent: SNMPv2-SMI::mib-2.10.7.2.1.7)
defined as: a count of frames for which the first transmission attempt
on a particular interface is delayed because the medium is busy.
The thing is that it's the only OID I found that gave a very high value
for port #2 (about 65,000 or so) and 0 for the rest of ports that work
properly.
The command I defined for this was like this:
define command {
command_name check_port
command_line $USER1$/check_snmp -H $HOSTADDRESS$ -C password -O
iso.3.6.1.2.1.10.7.2.1.7.$ARG1$ -w 1 -c 10 -u retries
}
For sure there must be somebody else in the list who can give to you a
more detailed or a more formally correct answer...
Hasta la proxima,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es
Valencia - Spain
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar]
Enviado el: miércoles, 06 de mayo de 2009 19:27
Para: Alejandro Sánchez Meroño; Nagios-users@lists.sourceforge.net
Asunto: RE: [Nagios-users] check_snmp - warning numbers
Hola Alejandro,
Ahora otra cosa:
De que manera crees que pueda chequear los puertos de mi switch con
nagios para tener una idea más clara de lo que está sucediendo?
Porque esos paquetes entrantes con errores no se si son por causa de la
PC o de los puerto del switch...
Muchas Gracias...
Cristian
Hola Matías... :-) and hola everyone...
There exists a magical website where to identify every OID you can check
with SNMP, the link is:
http://support.ipmonitor.com/mibs_byoidtree.aspx
For your particular issue, if you type RFC1213-MIB at the Search
for: form, click the result given (RFC1213-MIB), and then View:
Oid-tree, you'll be able to locate ifInErrors(14) at the tree shown,
and clicking it you'll find its Description, which reads literally:
The number of inbound packets that contained errors preventing them
from being deliverable to a higher-layer protocol.
That's the answer to your question!!
Now some other questions appear...
Wouldn't it be nicer to know what exactly are you monitoring before you
monitor it, so you could properly interpret the results?
Is that parameter (number of inbound packets that contained errors and
blah blah blah...) significant enough to determine if a port is working
properly or not?
Hope this helps...
Best regards,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es Valencia - Spain
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar] Enviado el: miércoles,
06 de mayo de 2009 17:49
Para: Nagios-users@lists.sourceforge.net
Asunto: [Nagios-users] check_snmp - warning numbers
Hi, I am using the check_snmp nagios`s plugin. And when we check the
ports status of a 3com Baseline 2250 Plus, we recibe many ports results:
SNMP OK - 0
SNMP WARNING - *1*
SNMP WARNING - *84*
SNMP WARNING - *2*
SNMP WARNING - *2*
SNMP WARNING - *4*
The question is, what´s the meaning of the warning numbers?
Other information:
--
# 'check_snmp' command definition
define command{
command_namecheck_snmp
command_line$USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
}
Example of service
---
define service {
use service-15x3x5-switchs
host_name 3COM2250P
service_description
Re: [Nagios-users] check_snmp - warning numbers
1. Make sure snmpd is running on the host. (classic mistake)
2. Make sure your community string and/or credentials are the same on the
host and client.
3. Make sure you're using the same snmp version on client and server (v1,
v2c, or v3)
4. Try running a tcpdump on the host while you're attempting the snmpwalk
to verify that the snmp requests are reaching the host. At the same time
verify that the host is trying to send out responses.
# tcpdump udp port 161
I'm sure there are more tests you can do but this is a start.
-f
On Fri, 8 May 2009, Matias Blanco wrote:
Date: Fri, 8 May 2009 13:02:28 -0300
From: Matias Blanco mat...@valastro.com.ar
To: 'Alejandro S?nchez Mero?o' alejandro.sanc...@ite.es,
Nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] check_snmp - warning numbers
Hello,
When i made an snmpwalk to a ip computer there is no response.
The snmpwalk to a switch,router or printer works ok.
Does any body know the reason?
Cristian...
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar]
Enviado el: Jueves, 07 de Mayo de 2009 17:02
Para: 'Alejandro S?nchez Mero?o'; Nagios-users@lists.sourceforge.net
Asunto: Re: [Nagios-users] check_snmp - warning numbers
Hello,
How can i do an snmpwalk on my switch?
Thanks,
Cristian...
-Mensaje original-
De: Alejandro S?nchez Mero?o [mailto:alejandro.sanc...@ite.es]
Enviado el: Jueves, 07 de Mayo de 2009 05:44
Para: Matias Blanco; Nagios-users@lists.sourceforge.net
Asunto: RE: [Nagios-users] check_snmp - warning numbers
Hola de nuevo...
I'll answer you in English so that anybody in the list can understand
and participate in this subject.
I think that if you don't know exactly which parameter to monitor you
should browse the whole OID list that you receive when you do a snmpwalk
on your switch, and identify the ones that fit your needs, with the help
of the website I said yesterday, or any other OIDs reference.
My case: The only thing I want to detect is if there is any damaged port
in any of my switches. So what I did was to snmpwalk on a switch which I
positively knew that had its port #2 damaged, and discover which OID was
significantly different for this port. And the one I found is:
iso.3.6.1.2.1.10.7.2.1.7
(maybe you can find it as its equivalent: SNMPv2-SMI::mib-2.10.7.2.1.7)
defined as: a count of frames for which the first transmission attempt
on a particular interface is delayed because the medium is busy.
The thing is that it's the only OID I found that gave a very high value
for port #2 (about 65,000 or so) and 0 for the rest of ports that work
properly.
The command I defined for this was like this:
define command {
command_name check_port
command_line $USER1$/check_snmp -H $HOSTADDRESS$ -C password -O
iso.3.6.1.2.1.10.7.2.1.7.$ARG1$ -w 1 -c 10 -u retries
}
For sure there must be somebody else in the list who can give to you a
more detailed or a more formally correct answer...
Hasta la proxima,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es
Valencia - Spain
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar]
Enviado el: mi?rcoles, 06 de mayo de 2009 19:27
Para: Alejandro S?nchez Mero?o; Nagios-users@lists.sourceforge.net
Asunto: RE: [Nagios-users] check_snmp - warning numbers
Hola Alejandro,
Ahora otra cosa:
De que manera crees que pueda chequear los puertos de mi switch con
nagios para tener una idea m?s clara de lo que est? sucediendo?
Porque esos paquetes entrantes con errores no se si son por causa de la
PC o de los puerto del switch...
Muchas Gracias...
Cristian
Hola Mat?as... :-) and hola everyone...
There exists a magical website where to identify every OID you can check
with SNMP, the link is:
http://support.ipmonitor.com/mibs_byoidtree.aspx
For your particular issue, if you type RFC1213-MIB at the Search
for: form, click the result given (RFC1213-MIB), and then View:
Oid-tree, you'll be able to locate ifInErrors(14) at the tree shown,
and clicking it you'll find its Description, which reads literally:
The number of inbound packets that contained errors preventing them
from being deliverable to a higher-layer protocol.
That's the answer to your question!!
Now some other questions appear...
Wouldn't it be nicer to know what exactly are you monitoring before you
monitor it, so you could properly interpret the results?
Is that parameter (number of inbound packets that contained errors and
blah blah blah...) significant enough to determine if a port is working
properly or not?
Hope this helps...
Best regards,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es Valencia - Spain
-Mensaje original
Re: [Nagios-users] check_snmp - warning numbers
Hola de nuevo...
I'll answer you in English so that anybody in the list can understand and
participate in this subject.
I think that if you don't know exactly which parameter to monitor you should
browse the whole OID list that you receive when you do a snmpwalk on your
switch, and identify the ones that fit your needs, with the help of the website
I said yesterday, or any other OIDs reference.
My case: The only thing I want to detect is if there is any damaged port in any
of my switches. So what I did was to snmpwalk on a switch which I positively
knew that had its port #2 damaged, and discover which OID was significantly
different for this port. And the one I found is:
iso.3.6.1.2.1.10.7.2.1.7
(maybe you can find it as its equivalent: SNMPv2-SMI::mib-2.10.7.2.1.7)
defined as: a count of frames for which the first transmission attempt on a
particular interface is delayed because the medium is busy.
The thing is that it's the only OID I found that gave a very high value for
port #2 (about 65,000 or so) and 0 for the rest of ports that work properly.
The command I defined for this was like this:
define command {
command_name check_port
command_line $USER1$/check_snmp -H $HOSTADDRESS$ -C password -O
iso.3.6.1.2.1.10.7.2.1.7.$ARG1$ -w 1 -c 10 -u retries
}
For sure there must be somebody else in the list who can give to you a more
detailed or a more formally correct answer...
Hasta la proxima,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es
Valencia - Spain
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar]
Enviado el: miércoles, 06 de mayo de 2009 19:27
Para: Alejandro Sánchez Meroño; Nagios-users@lists.sourceforge.net
Asunto: RE: [Nagios-users] check_snmp - warning numbers
Hola Alejandro,
Ahora otra cosa:
De que manera crees que pueda chequear los puertos de mi switch con nagios para
tener una idea más clara de lo que está sucediendo?
Porque esos paquetes entrantes con errores no se si son por causa de la PC o de
los puerto del switch...
Muchas Gracias...
Cristian
Hola Matías... :-) and hola everyone...
There exists a magical website where to identify every OID you can check with
SNMP, the link is:
http://support.ipmonitor.com/mibs_byoidtree.aspx
For your particular issue, if you type RFC1213-MIB at the Search for: form,
click the result given (RFC1213-MIB), and then View:
Oid-tree, you'll be able to locate ifInErrors(14) at the tree shown, and
clicking it you'll find its Description, which reads literally:
The number of inbound packets that contained errors preventing them from being
deliverable to a higher-layer protocol.
That's the answer to your question!!
Now some other questions appear...
Wouldn't it be nicer to know what exactly are you monitoring before you monitor
it, so you could properly interpret the results?
Is that parameter (number of inbound packets that contained errors and blah
blah blah...) significant enough to determine if a port is working properly or
not?
Hope this helps...
Best regards,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es Valencia - Spain
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar] Enviado el: miércoles, 06 de
mayo de 2009 17:49
Para: Nagios-users@lists.sourceforge.net
Asunto: [Nagios-users] check_snmp - warning numbers
Hi, I am using the check_snmp nagios`s plugin. And when we check the ports
status of a 3com Baseline 2250 Plus, we recibe many ports results:
SNMP OK - 0
SNMP WARNING - *1*
SNMP WARNING - *84*
SNMP WARNING - *2*
SNMP WARNING - *2*
SNMP WARNING - *4*
The question is, what´s the meaning of the warning numbers?
Other information:
--
# 'check_snmp' command definition
define command{
command_namecheck_snmp
command_line$USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
}
Example of service
---
define service {
use service-15x3x5-switchs
host_name 3COM2250P
service_description Port 03 [In Errors]
check_command check_snmp!-C public -o ifInErrors.3 -w
0 -m RFC1213-MIB
notifications_enabled 0
}
THANKS...
Matías Blanco.
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
Nagios-users mailing list
Nagios-users
Re: [Nagios-users] check_snmp - warning numbers
Hello,
How can i do an snmpwalk on my switch?
Thanks,
Cristian...
-Mensaje original-
De: Alejandro Sánchez Meroño [mailto:alejandro.sanc...@ite.es]
Enviado el: Jueves, 07 de Mayo de 2009 05:44
Para: Matias Blanco; Nagios-users@lists.sourceforge.net
Asunto: RE: [Nagios-users] check_snmp - warning numbers
Hola de nuevo...
I'll answer you in English so that anybody in the list can understand
and participate in this subject.
I think that if you don't know exactly which parameter to monitor you
should browse the whole OID list that you receive when you do a snmpwalk
on your switch, and identify the ones that fit your needs, with the help
of the website I said yesterday, or any other OIDs reference.
My case: The only thing I want to detect is if there is any damaged port
in any of my switches. So what I did was to snmpwalk on a switch which I
positively knew that had its port #2 damaged, and discover which OID was
significantly different for this port. And the one I found is:
iso.3.6.1.2.1.10.7.2.1.7
(maybe you can find it as its equivalent: SNMPv2-SMI::mib-2.10.7.2.1.7)
defined as: a count of frames for which the first transmission attempt
on a particular interface is delayed because the medium is busy.
The thing is that it's the only OID I found that gave a very high value
for port #2 (about 65,000 or so) and 0 for the rest of ports that work
properly.
The command I defined for this was like this:
define command {
command_name check_port
command_line $USER1$/check_snmp -H $HOSTADDRESS$ -C password -O
iso.3.6.1.2.1.10.7.2.1.7.$ARG1$ -w 1 -c 10 -u retries
}
For sure there must be somebody else in the list who can give to you a
more detailed or a more formally correct answer...
Hasta la proxima,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es
Valencia - Spain
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar]
Enviado el: miércoles, 06 de mayo de 2009 19:27
Para: Alejandro Sánchez Meroño; Nagios-users@lists.sourceforge.net
Asunto: RE: [Nagios-users] check_snmp - warning numbers
Hola Alejandro,
Ahora otra cosa:
De que manera crees que pueda chequear los puertos de mi switch con
nagios para tener una idea más clara de lo que está sucediendo?
Porque esos paquetes entrantes con errores no se si son por causa de la
PC o de los puerto del switch...
Muchas Gracias...
Cristian
Hola Matías... :-) and hola everyone...
There exists a magical website where to identify every OID you can check
with SNMP, the link is:
http://support.ipmonitor.com/mibs_byoidtree.aspx
For your particular issue, if you type RFC1213-MIB at the Search
for: form, click the result given (RFC1213-MIB), and then View:
Oid-tree, you'll be able to locate ifInErrors(14) at the tree shown,
and clicking it you'll find its Description, which reads literally:
The number of inbound packets that contained errors preventing them
from being deliverable to a higher-layer protocol.
That's the answer to your question!!
Now some other questions appear...
Wouldn't it be nicer to know what exactly are you monitoring before you
monitor it, so you could properly interpret the results?
Is that parameter (number of inbound packets that contained errors and
blah blah blah...) significant enough to determine if a port is working
properly or not?
Hope this helps...
Best regards,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es Valencia - Spain
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar] Enviado el: miércoles,
06 de mayo de 2009 17:49
Para: Nagios-users@lists.sourceforge.net
Asunto: [Nagios-users] check_snmp - warning numbers
Hi, I am using the check_snmp nagios`s plugin. And when we check the
ports status of a 3com Baseline 2250 Plus, we recibe many ports results:
SNMP OK - 0
SNMP WARNING - *1*
SNMP WARNING - *84*
SNMP WARNING - *2*
SNMP WARNING - *2*
SNMP WARNING - *4*
The question is, what´s the meaning of the warning numbers?
Other information:
--
# 'check_snmp' command definition
define command{
command_namecheck_snmp
command_line$USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
}
Example of service
---
define service {
use service-15x3x5-switchs
host_name 3COM2250P
service_description Port 03 [In Errors]
check_command check_snmp!-C public -o ifInErrors.3 -w
0 -m RFC1213-MIB
notifications_enabled 0
}
THANKS...
Matías Blanco.
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak
[Nagios-users] check_snmp - warning numbers
Hi, I am using the check_snmp nagios`s plugin. And when we check the
ports status of a 3com Baseline 2250 Plus, we recibe many ports results:
SNMP OK 0
SNMP WARNING - *1*
SNMP WARNING - *84*
SNMP WARNING - *2*
SNMP WARNING - *2*
SNMP WARNING - *4*
The question is, what´s the meaning of the warning numbers?
Other information:
--
# 'check_snmp' command definition
define command{
command_namecheck_snmp
command_line$USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
}
Example of service
---
define service {
use service-15x3x5-switchs
host_name 3COM2250P
service_description Port 03 [In Errors]
check_command check_snmp!-C public -o ifInErrors.3 -w
0 -m RFC1213-MIB
notifications_enabled 0
}
THANKS...
Matías Blanco.
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
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_snmp - warning numbers
Comments below --
On May 6, 2009, at 10:49 AM, Matias Blanco wrote:
Hi, I am using the check_snmp nagios`s plugin. And when we check the
ports status of a 3com Baseline 2250 Plus, we recibe many ports
results:
SNMP OK – 0
SNMP WARNING - *1*
SNMP WARNING - *84*
SNMP WARNING - *2*
SNMP WARNING - *2*
SNMP WARNING - *4*
The question is, what´s the meaning of the warning numbers?
Depends on what you're checking...
[snip]
Example of service
---
define service {
use service-15x3x5-switchs
host_name 3COM2250P
service_description Port 03 [In Errors]
check_command check_snmp!-C public -o ifInErrors.3 -w
0 -m RFC1213-MIB
notifications_enabled 0
}
Assuming the numbers above are related to this service --
From the RFC1213-MIB --
ifInErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
The number of inbound packets that contained
errors preventing them from being deliverable to a
higher-layer protocol.
::= { ifEntry 14 }
For this example service, the number being returned is the number of
input errors since last counter reset, roll or device restart for the
interface with SNMP index 3. Note that this does not necessarily
correspond to Port 3 thanks to the joys of various SNMP
implementations and device types. You can identify the specific
interface that currently has an index of 3 using 'snmpwalk -C public -
v1 ip of device ifDescr'. You may need to substitute '-v2c' for '-
v1' if you're using SNMP version 2.
--
Marc
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
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_snmp - warning numbers
Hola Matías... :-) and hola everyone...
There exists a magical website where to identify every OID you can check with
SNMP, the link is:
http://support.ipmonitor.com/mibs_byoidtree.aspx
For your particular issue, if you type RFC1213-MIB at the Search for: form,
click the result given (RFC1213-MIB), and then View: Oid-tree, you'll be
able to locate ifInErrors(14) at the tree shown, and clicking it you'll find
its Description, which reads literally:
The number of inbound packets that contained errors preventing them from being
deliverable to a higher-layer protocol.
That's the answer to your question!!
Now some other questions appear...
Wouldn't it be nicer to know what exactly are you monitoring before you monitor
it, so you could properly interpret the results?
Is that parameter (number of inbound packets that contained errors and blah
blah blah...) significant enough to determine if a port is working properly or
not?
Hope this helps...
Best regards,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es
Valencia - Spain
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar]
Enviado el: miércoles, 06 de mayo de 2009 17:49
Para: Nagios-users@lists.sourceforge.net
Asunto: [Nagios-users] check_snmp - warning numbers
Hi, I am using the check_snmp nagios`s plugin. And when we check the ports
status of a 3com Baseline 2250 Plus, we recibe many ports results:
SNMP OK - 0
SNMP WARNING - *1*
SNMP WARNING - *84*
SNMP WARNING - *2*
SNMP WARNING - *2*
SNMP WARNING - *4*
The question is, what´s the meaning of the warning numbers?
Other information:
--
# 'check_snmp' command definition
define command{
command_namecheck_snmp
command_line$USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
}
Example of service
---
define service {
use service-15x3x5-switchs
host_name 3COM2250P
service_description Port 03 [In Errors]
check_command check_snmp!-C public -o ifInErrors.3 -w
0 -m RFC1213-MIB
notifications_enabled 0
}
THANKS...
Matías Blanco.
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image processing
features enabled. http://p.sf.net/sfu/kodak-com
___
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
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
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_snmp - warning numbers
Hola Alejandro,
Ahora otra cosa:
De que manera crees que pueda chequear los puertos de mi switch con
nagios para tener una idea más clara de lo que está sucediendo?
Porque esos paquetes entrantes con errores no se si son por causa de la
PC o de los puerto del switch...
Muchas Gracias...
Cristian
Hola Matías... :-) and hola everyone...
There exists a magical website where to identify every OID you can check
with SNMP, the link is:
http://support.ipmonitor.com/mibs_byoidtree.aspx
For your particular issue, if you type RFC1213-MIB at the Search
for: form, click the result given (RFC1213-MIB), and then View:
Oid-tree, you'll be able to locate ifInErrors(14) at the tree shown,
and clicking it you'll find its Description, which reads literally:
The number of inbound packets that contained errors preventing them
from being deliverable to a higher-layer protocol.
That's the answer to your question!!
Now some other questions appear...
Wouldn't it be nicer to know what exactly are you monitoring before you
monitor it, so you could properly interpret the results?
Is that parameter (number of inbound packets that contained errors and
blah blah blah...) significant enough to determine if a port is working
properly or not?
Hope this helps...
Best regards,
Alejandro
==
Alejandro Sanchez Merono
Area de Informatica y Comunicaciones
Instituto de Tecnologia Electrica - http://www.ite.es
Valencia - Spain
-Mensaje original-
De: Matias Blanco [mailto:mat...@valastro.com.ar]
Enviado el: miércoles, 06 de mayo de 2009 17:49
Para: Nagios-users@lists.sourceforge.net
Asunto: [Nagios-users] check_snmp - warning numbers
Hi, I am using the check_snmp nagios`s plugin. And when we check the
ports status of a 3com Baseline 2250 Plus, we recibe many ports results:
SNMP OK - 0
SNMP WARNING - *1*
SNMP WARNING - *84*
SNMP WARNING - *2*
SNMP WARNING - *2*
SNMP WARNING - *4*
The question is, what´s the meaning of the warning numbers?
Other information:
--
# 'check_snmp' command definition
define command{
command_namecheck_snmp
command_line$USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$
}
Example of service
---
define service {
use service-15x3x5-switchs
host_name 3COM2250P
service_description Port 03 [In Errors]
check_command check_snmp!-C public -o ifInErrors.3 -w
0 -m RFC1213-MIB
notifications_enabled 0
}
THANKS...
Matías Blanco.
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
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
