mirror of
https://github.com/ranl/monitor-utils.git
synced 2024-11-04 15:33:42 +01:00
Cisco-Status Check: PowerSupply, Fan, Status, Memory, Module
c9271972a6
Hello Ran This is Laurent DUFOUR (laurent.dufour@havas.com) from Paris France I propose a small little change to the handling of timeouts in this check-netapp-ng script, in order to avoid the message "Return code of 142 is out of bounds" from Nagios. In fact we have to deal with two type of timeouts as I explain below, feel free to contact me if you need more explanations CLARIFICATION FOR TIMEOUTS There are multiples timeouts we depend on Perl plugins timeout (utils.pm)--- > $TIMEOUT --- > originally 15 sec --> recommandation to raise it to 180 Net::SNMP timeout --- > Used in Net::SNMP->session --- > originally 5 sec --> recommandation to raise it to 60 Beware that the max value 60 seconds. If set above you get the error message "Can't create snmp session" Do not forget that in nagios you need to increase service_check_timeout to a value above $TIMEOUT_PLUGINS Nagios service check timeout (nagios.cfg) --- > service_check_timeout=240 --- > originally 30 sec |
||
---|---|---|
cacti | ||
nagios | ||
zabbix | ||
.gitignore | ||
LICENSE | ||
README.md |
monitor-utils
Monitoring script for Zabbix / Nagios