All I have is the MIB file.
Ran the above and got hte attached file as a result.
Search found 30 matches
- Wed Jun 26, 2013 9:04 am
- Forum: Open Source Nagios Projects
- Topic: Monitoring IT Watchdogs Temp Monitors
- Replies: 17
- Views: 10968
- Mon Jun 24, 2013 1:43 pm
- Forum: Open Source Nagios Projects
- Topic: Monitoring IT Watchdogs Temp Monitors
- Replies: 17
- Views: 10968
Re: Monitoring IT Watchdogs Temp Monitors
My folder path was slightly different (I'm running ubuntu, not sure if that makes a difference). But here is the output: iso.3.6.1.2.1.1.1.0 = STRING: "MicroGoose" iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.17373.3 iso.3.6.1.2.1.1.3.0 = Timeticks: (34852655) 4 days, 0:48:46.55 iso.3.6.1.2.1....
- Mon Jun 24, 2013 12:31 pm
- Forum: Open Source Nagios Projects
- Topic: Monitoring IT Watchdogs Temp Monitors
- Replies: 17
- Views: 10968
Re: Monitoring IT Watchdogs Temp Monitors
Attached above.
- Mon Jun 24, 2013 12:19 pm
- Forum: Open Source Nagios Projects
- Topic: Monitoring IT Watchdogs Temp Monitors
- Replies: 17
- Views: 10968
Re: Monitoring IT Watchdogs Temp Monitors
Funny you should mention that. I was clicking around in the device web interface and I can download the MIB in a .zip file. What do I do with it? IT included the attached .csv file and a .mib file.
- Mon Jun 24, 2013 12:07 pm
- Forum: Open Source Nagios Projects
- Topic: Monitoring IT Watchdogs Temp Monitors
- Replies: 17
- Views: 10968
Re: Monitoring IT Watchdogs Temp Monitors
snmpwalk -v1 -c <community> <device ip> iso.3.6.1.2.1.1.1.0 = STRING: "MicroGoose" iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.17373.3 iso.3.6.1.2.1.1.3.0 = Timeticks: (34270781) 3 days, 23:11:47.81 iso.3.6.1.2.1.1.4.0 = STRING: "serverteam@brakebush.com" iso.3.6.1.2.1.1.5.0 = &quo...
- Mon Jun 24, 2013 11:48 am
- Forum: Open Source Nagios Projects
- Topic: Monitoring IT Watchdogs Temp Monitors
- Replies: 17
- Views: 10968
Re: Monitoring IT Watchdogs Temp Monitors
I'm using what I believe is the OID for the Microgoose monitor: http://oid-info.com/get/1.3.6.1.4.1.17373. I'm not sure it's correct though.
As for your second question I don't know how to do that or how to check if it's already done.
As for your second question I don't know how to do that or how to check if it's already done.
- Mon Jun 24, 2013 11:17 am
- Forum: Open Source Nagios Projects
- Topic: Monitoring IT Watchdogs Temp Monitors
- Replies: 17
- Views: 10968
Re: Monitoring IT Watchdogs Temp Monitors
After a couple of days of frustration I've switched to trying just the straignt check_snmp plugin. So, scrap the above complaint and replace it with the following. What I'm trying to do: Using Nagios I am trying to monitor two different IT Watchdog "Microgoose" Temperature Monitors via the...
- Fri Jun 21, 2013 3:50 pm
- Forum: Open Source Nagios Projects
- Topic: Monitoring IT Watchdogs Temp Monitors
- Replies: 17
- Views: 10968
Re: Monitoring IT Watchdogs Temp Monitors
The plugin is located in the libexec folder along with all the other plugins.
I made the file executable and am now getting "Return code of 127 is out of bounds - plugin may be missing" link Nagios doesn't see the plugin.
I made the file executable and am now getting "Return code of 127 is out of bounds - plugin may be missing" link Nagios doesn't see the plugin.
- Fri Jun 21, 2013 11:32 am
- Forum: Open Source Nagios Projects
- Topic: Monitoring IT Watchdogs Temp Monitors
- Replies: 17
- Views: 10968
Monitoring IT Watchdogs Temp Monitors
I am trying to use a plugin (http://exchange.nagios.org/directory/Plugins/Hardware/Environmental/check_temp_weathergoose/details) to monitor our 2 Microgoose temp monitors. I am getting a "Return code of 126 is out of bounds - plugin may not be executable" in Nagios and don't believe I've ...
- Tue Mar 26, 2013 12:43 pm
- Forum: Open Source Nagios Projects
- Topic: Monitoring Windows Event Logs
- Replies: 39
- Views: 22804
Re: Monitoring Windows Event Logs
Yay, got it figured! :ugeek: Used the following: define command{ command_name check_eventlog command_line $USER1$/check_nrpe -H $HOSTNAME$ -p 5666 -c CheckEventLog -a filter file=system MaxWarn=1 MaxCrit=1 "filter=generated gt -1h AND severity NOT IN ('success', 'informational','warning')"...