[Leaf-user] SNMP Monitoring of Dachstein

2001-12-06 Thread rmcclurg

I have some basic SNMP monitoring of my Dachstein machines working using
the old SNMP package and MRTG. With these I keep a constant graph of the
activities of eth0, eth1 and ipsec0 on both ends of my test VPN tunnel. I
converted to net-snmp and everything is still working (thanks people for
standards). My next task is to add monitoring of the memory, CPU, and RAM
disks. The result would be a single web page which provides a continuous
graph of the health of the LEAF boxes. You can see at a glance where
something may be going wrong. Since MRTG also does such a nice job of
keeping a running summary of the data on a daily, weekly, monthly and
yearly basis. You can also use the data to predict when you may need to
make changes on a system.

Others have setup MRTG to do this kind of thing on their Linux servers. I
was wondering if anyone here have already done something similar and have
some MRTG scripts that work with the net-snmp mibs that they can share, or
maybe just some pointers. When I'm done I'll give what I have to Charles.
He needs some more packages to fill up that Dachstein CD. ;-)

Roger


___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user



Re: [Leaf-user] SNMP Monitoring of Dachstein

2001-12-06 Thread Charles Steinkuehler

 I have some basic SNMP monitoring of my Dachstein machines working using
 the old SNMP package and MRTG. With these I keep a constant graph of the
 activities of eth0, eth1 and ipsec0 on both ends of my test VPN tunnel. I
 converted to net-snmp and everything is still working (thanks people for
 standards). My next task is to add monitoring of the memory, CPU, and RAM
 disks. The result would be a single web page which provides a continuous
 graph of the health of the LEAF boxes. You can see at a glance where
 something may be going wrong. Since MRTG also does such a nice job of
 keeping a running summary of the data on a daily, weekly, monthly and
 yearly basis. You can also use the data to predict when you may need to
 make changes on a system.

 Others have setup MRTG to do this kind of thing on their Linux servers. I
 was wondering if anyone here have already done something similar and have
 some MRTG scripts that work with the net-snmp mibs that they can share, or
 maybe just some pointers. When I'm done I'll give what I have to Charles.
 He needs some more packages to fill up that Dachstein CD. ;-)

I've setup minimal monitoring of memory and disk usage using OID's already
supported by the older SNMP package (do an snmpwalk to find interesting
things to monitor).  I haven't actually switched to net-snmp yet (although I
have verified it's working), although the intent is to be able to monitor
things like CPU  web-server load.

I've also started playing with OpenNMS (http://www.opennms.org), but don't
have anything working yet...looks pretty cool, though.

Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)



___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user



Re: [Leaf-user] SNMP Monitoring of Dachstein

2001-12-06 Thread David Douthitt

[EMAIL PROTECTED] wrote:

 I have some basic SNMP monitoring of my Dachstein machines working using
 the old SNMP package and MRTG. With these I keep a constant graph of the
 activities of eth0, eth1 and ipsec0 on both ends of my test VPN tunnel. I
 converted to net-snmp and everything is still working (thanks people for
 standards). My next task is to add monitoring of the memory, CPU, and RAM
 disks.

 Others have setup MRTG to do this kind of thing on their Linux servers. I
 was wondering if anyone here have already done something similar and have
 some MRTG scripts that work with the net-snmp mibs that they can share, or
 maybe just some pointers.

Maybe this is out of line here, or maybe not.

Here we use NetSaint to monitor many systems.  It would be quite simple
to set up a monitoring system to check for CPU, disk space, memory -
whatever you want.  All you need is an ssh server on the LEAF side and
scripts that give one line of info and return 0 for OK, 1 for WARNING,
and 2 for CRITICAL  Then you run your script using SSH.

Of course, NetSaint is for system critical conditions, and isn't for
performance monitoring, though the latest versions offer the ability to
store performance data (but not process it).

MRTG is more of a history, and NetSaint is a snapshot in time.  Sort of
like the difference between a balance sheet and an income statement :)

___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user