Zenoss handles traps, as well as graphing, plus a lot of other nagios-like functionality, including the plugins.
www.zenoss.org Dustin Puryear wrote: > Okay, I was wondering. AFAIK, Cacti just does graphing of SNMP data. I'm > sure tools like Nagios, etc do work with SNMP traps though. > > Didn't someone come up with a Big Brother + Cacti integration dealie? > > Adam Melancon wrote: > >> Sorry, looks like I got caught in a "trap" and misunderstood the >> request. I'm just using cacti to monitor SNMP, not to catch traps. >> >> Adam Melancon >> >> >> >> On Thu, Jan 15, 2009 at 9:27 AM, Dustin Puryear <[email protected] >> <mailto:[email protected]>> wrote: >> >> Wait. Cacti can do SNMP traps? What does it do with that data? Maybe I'm >> missing something.. :) >> >> -ray wrote: >> > We use cacti too. Have you set it up to catch snmp traps? >> > >> > ray >> > >> > >> > On Wed, 14 Jan 2009, Adam Melancon wrote: >> > >> >> I use Cacti for all my SNMP monitoring. It works great! >> >> http://cacti.net/ >> >> >> >> Adam Melancon >> >> >> >> >> >> >> >> On Wed, Jan 14, 2009 at 1:42 PM, Brad Bendily <[email protected] >> <mailto:[email protected]>> wrote: >> >> >> >>>> I am an SNMP newbie. I've started a project at work to monitor >> >>> availability >> >>>> of services on a server. These services support SNMP v1, but >> the docs are >> >>>> pretty slim. >> >>>> >> >>>> I've been playing around with Net-SNMP and can do a simple SNMP >> get from >> >>> my >> >>>> workstation for the server's name and so on, so I know SNMP >> works on >> >>>> it. However, I can't figure out how to receive a trap from the >> app's >> >>> agent >> >>>> on the server. There are too many factors with that >> configuration to >> >>> mention >> >>>> now, so I'd like to pose a simple question. >> >>>> >> >>>> What is the simplest demonstration of a trap (both sending and >> receiving) >> >>>> using the Net-SNMP (http://www.net-snmp.org) tools? Can this be >> done >> >>> using >> >>>> only Net-SNMP tools? I'm using Net-SNMP as it is >> cross-platform. And yes, >> >>> it >> >>>> is open source. ;) >> >>>> >> >>> We have dell servers at work and usually install the dell open >> manage >> >>> package. This adds the dell MIBs so we can get all kinds of info >> off the >> >>> server via snmp. We use SuSE servers, the problem I have had >> with snmp >> >>> is that for different versions of the net-snmp rpm i have to have a >> >>> different snmpd.conf. This partly due to the open manage stuff. >> To get >> >>> open manage to work you have to enable "smuxpeer". For one rpm >> version, >> >>> the smuxpeer needs a password and you have to set the password >> in dell >> >>> open manage. For another snmp rpm you don't need the password at >> all. >> >>> for traps you need to enable them via the conf file, which will be: >> >>> >> >>> trapsink 10.1.1.1 public >> >>> >> >>> The man page says you should also use: >> >>> trapcommunity STRING >> >>> defines the default community string to be used when sending >> >>> traps. Note that this directive >> >>> must be used prior to any community-based trap destination >> >>> directives that need to use it. >> >>> >> >>> trapsink HOST [COMMUNITY [PORT]] >> >>> >> >>> >> >>> However, our config doesn't use trapcommunity. This may be part of >> >>> something open manage does for us. But this sends traps to our >> >>> open manage monitor server. Now we just need someone to monitor that >> >>> server! >> >>> >> >>> Hope this helps, let me know if I can do anything else. >> >>> b >> >>> >> >>> >> >>> _______________________________________________ >> >>> General mailing list >> >>> [email protected] <mailto:[email protected]> >> >>> http://mail.brlug.net/mailman/listinfo/general_brlug.net >> >>> >> > >> >> -- >> Dustin Puryear >> President and Sr. Consultant >> Puryear Information Technology, LLC >> 225-706-8414 x112 >> http://www.puryear-it.com >> >> Author, "Best Practices for Managing Linux and UNIX Servers" >> http://www.puryear-it.com/pubs/linux-unix-best-practices/ >> >> _______________________________________________ >> General mailing list >> [email protected] <mailto:[email protected]> >> http://mail.brlug.net/mailman/listinfo/general_brlug.net >> >> >> >> -- >> This message was scanned by ESVA and is believed to be clean. >> Click here to report this message as spam. < >> http://esva.puryear-it.com/cgi-bin/learn-msg.cgi?id= > >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> General mailing list >> [email protected] >> http://mail.brlug.net/mailman/listinfo/general_brlug.net >> > > _______________________________________________ General mailing list [email protected] http://mail.brlug.net/mailman/listinfo/general_brlug.net
