Threshold woes monitoring license expiry with SNMP
Posted: Thu May 26, 2016 9:35 am
Hi all,
I'm trying to monitor the license expiry on one of my Digium Switchvox using SNMP. There are two OIDs one for the expiry date and the other for the number of days left. I have used the SNMP wizard to create a monitor but I have a big challenge with the thresholds. When I configure the thresholds with 60 as the warning and 30 as the critical I get CRITICAL alerts with the current value read from the device being 563. I have tried ranges for the warning and critical but with the same result. The result is always CRITICAL 563;warning_threshod;critical_threshold. I'm not sure if there is a bug in the script or am doing something wrong with the thresholds. I'd be grateful if anyone can help me figure out what I'm doing wrong.
The result is
I am miffed.
Kind regards
Osay
I'm trying to monitor the license expiry on one of my Digium Switchvox using SNMP. There are two OIDs one for the expiry date and the other for the number of days left. I have used the SNMP wizard to create a monitor but I have a big challenge with the thresholds. When I configure the thresholds with 60 as the warning and 30 as the critical I get CRITICAL alerts with the current value read from the device being 563. I have tried ranges for the warning and critical but with the same result. The result is always CRITICAL 563;warning_threshod;critical_threshold. I'm not sure if there is a bug in the script or am doing something wrong with the thresholds. I'd be grateful if anyone can help me figure out what I'm doing wrong.
Code: Select all
$USER1$/check_snmp -o .1.3.6.1.4.1.22736.10.7.2 -C <community string> -P 2c -u Days -w 6o -c 30Code: Select all
COMMAND: /usr/local/nagios/libexec/check_snmp -H myhost -o .1.3.6.1.4.1.22736.10.7.2 -C <community string> -P 2c -u Days -w 60 -c 30
OUTPUT: SNMP CRITICAL - *563* Days | iso.3.6.1.4.1.22736.10.7.2=563Days;60;30;
CloseKind regards
Osay