Re: [Nagios-users] Monitor Thin Clients with Nagios
Thank you for your input and pointing me in some kind of direction. I will give it a try. On 3/31/10, Matt Simmons wrote: > Like anything else, the thin clients have to be able to report, > somehow. Given the fact that there is a Wyse MIB ( > http://www.oidview.com/mibs/714/WYSE-MIB.html ), I'd wager they > support SNMP, and thus could probably be set up like any other network > accessible host. > > Also, there's a chance (though I'm unfamiliar with the equipment, so I > don't know how good of a chance) that they could be setup for SNMP > traps, in which case you can probably be alerted for hardware faults. > > Good luck. Get it done, then write some documentation! ;-) > > --Matt > > > On Wed, Mar 31, 2010 at 4:06 PM, Victor Lanza wrote: >> Hi, >> >> Has anyone tried to monitor Thin Clients with Nagios..as far as hardware >> health or anything other than just ping? Specifically with Wyse thin >> clients >> and Nagios 3.0.6. I'm curious to see what can be monitored. >> >> Thanks, >> >> Victor >> >> -- >> Download Intel® 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 >> > > > > -- > LITTLE GIRL: But which cookie will you eat FIRST? > COOKIE MONSTER: Me think you have misconception of cookie-eating process. > > COOKIE MONSTER: Boy, I wish I were a sysadmin so I could go to the > NJ-PICC Sysadmin Conference! http://www.picconf.org > > -- > Download Intel® 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 > -- Sent from my mobile device Best Regards, Victor Lanza -- Download Intel® 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] Monitor Thin Clients with Nagios
Like anything else, the thin clients have to be able to report, somehow. Given the fact that there is a Wyse MIB ( http://www.oidview.com/mibs/714/WYSE-MIB.html ), I'd wager they support SNMP, and thus could probably be set up like any other network accessible host. Also, there's a chance (though I'm unfamiliar with the equipment, so I don't know how good of a chance) that they could be setup for SNMP traps, in which case you can probably be alerted for hardware faults. Good luck. Get it done, then write some documentation! ;-) --Matt On Wed, Mar 31, 2010 at 4:06 PM, Victor Lanza wrote: > Hi, > > Has anyone tried to monitor Thin Clients with Nagios..as far as hardware > health or anything other than just ping? Specifically with Wyse thin clients > and Nagios 3.0.6. I'm curious to see what can be monitored. > > Thanks, > > Victor > > -- > Download Intel® 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 > -- LITTLE GIRL: But which cookie will you eat FIRST? COOKIE MONSTER: Me think you have misconception of cookie-eating process. COOKIE MONSTER: Boy, I wish I were a sysadmin so I could go to the NJ-PICC Sysadmin Conference! http://www.picconf.org -- Download Intel® 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
[Nagios-users] Monitor Thin Clients with Nagios
Hi, Has anyone tried to monitor Thin Clients with Nagios..as far as hardware health or anything other than just ping? Specifically with Wyse thin clients and Nagios 3.0.6. I'm curious to see what can be monitored. Thanks, Victor -- Download Intel® 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
