Peter HOLZLEITNER wrote:
> > some people believe 
> So what's YOUR opinion?
> 
> > that SNMP is the work of the devil and creates another security 
> hackable avenue.
> I say it can't be beat for querying status parameters (hint: stateless 
> ...)
> You don't have to allow any writing whatsoever ... the security for this 
> really sucks (in SNMPv1 that is).
> 
> What else?  Just hack a monitor that does what snmpvar.monitor does but 
> calls local scripts.
> Downside?  Monitors local machine only.  Need to feed values into MRTG 
> or similar separately.

No, we do a lot of monitoring of remote servers simply by setting up inetd
entries which run a command as nobody to return something like a "df"
output, a "ps" output, a "metastat" output (Solaris), etc.  Then the mon
modules simply connect to the remote systems on a pre-determined port
number and obtain status information back.  Really easy and can even be
kept from outsiders by use of TCP wrappers (/etc/hosts.allow) entries,
restricting access to only the mon server.  Works slick.  We have several
mon modules which utilize this mechanism:

        df.monitor (uses "df" to monitor disk space -- we don't use
                freespace.monitor since it requires NFS mounts)
        ps.monitor (uses "ps" to monitor process counts, sizes, CPU util.)
        metastat.monitor (uses "metstat" to check for broken mirrors, etc.)

There are other, less generic ones as well that I won't mention.
You get the idea...  (and no, we don't presently utilize SNMP)

> And of course your network equipment will also want to tell you how warm 
> it feels .. via SNMP only.
> 
> TANSTAAFL.
> 
> --Peter
> 
> 
> 
> > 
> > Are there any other options out there?
> > 
> > Thanks,
> > Tom
> > 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED]] On
> > Behalf Of Peter HOLZLEITNER
> > Sent: Monday, August 20, 2001 12:57 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: CPU Temps
> > 
> > Doing that all the time ... and a bunch of other parameters, too (fan 
> > speed, RAID drive status, redundant PSU status, temp of UPS, line 
> > voltage, mail queue length, ...)
> > 
> > I wrote snmpvar.monitor which queries any variable accessible 
> > via SNMP.
> > See 
> > http://ftp.kernel.org/pub/software/admin/mon/contrib/monitors/
> snmpvar/ .
> 
> I have also used the ucd-snmp extension exec feature to make some of 
> these parameters available via SNMP in the first place on Linux 
> machines.  It's fairly trivial to stick (lm_)sensors into this (first 
> make sure the sensors stuff works and gives correct readings!).
> 
> E-mail and paging are of course standard mon alert actions.
> 
> Repetition is also standard unless you use alertevery.
> 
> watch environment
>       service snmpval
>               interval 15m
>               monitor snmpval.monitor
>               alert mail.alert [EMAIL PROTECTED]
>               alert qpage.alert oper_pager
> 
> This will check all configured variables against high & low limits and 
> complain every 15min by pager and E-mail until the values are back in 
> range.
> 
> 
> --Peter
> 
> 
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, August 20, 2001 4:40 PM
> > To: [EMAIL PROTECTED]
> > Subject: CPU Temps
> > 
> > 
> > Is it possible to have Mon monitor the temperature of a computer?
> > 
> > Also would be nice to have it send emails, and use Qpage to notify
> > people if a CPU temperature gets to a certain level.
> > 
> > Maybe even repeatedly send the emails and pages until the temperature
> > drops.
> > 
> > Thanks,
> > 
> > Tom
> > 
> > 
> 
> 
> 


-- 

Steven F. Siirila                       Office: Lind Hall, Room 130B
Internet Services                       E-mail: [EMAIL PROTECTED]
Office of Information Technology        Voice: (612) 626-0244
University of Minnesota                 Fax: (612) 626-7593

Reply via email to