Ahh, an opinion I would agree with, if those systems did what I wanted :) I dislike the interfaces of all of the existing NMSes. This is a rewrite of something I encountered at a previous company that I found to be more useful than the other NMSes I tried. It certainly won't do all of the same things though, as I'm not really interested in all of the things the others do.
The developers of OpenNMS/JFFNMS/etc are, without a doubt, far more skilled coders than I am, but they just haven't produced something that I want to use! One of the design goals of the project is to produce something which is mostly automatic with the minimum amount of management required. The most notable place this fails for me is with our m0n0/pfSense firewalls, where it can only identify them as FreeBSD and thinks it should be able to graph all sorts of things that it can't, resulting in horribly inefficient polling :( Someone earlier suggested creating a "monitoring appliance". I think this would be a good end goal, to create a pfSense-like appliance that people can pop into their network, tell about ip ranges and community strings and it goes away and discovers everything without too much configuration file editing and the like. But, this is all off-topic for this list... Except, Still no suggestions on how to identify a pfSense needle in a haystack of FreeBSD servers. :\ Thanks, Adam. -----Original Message----- From: Tom Müller-Kortkamp [mailto:[EMAIL PROTECTED] Sent: 25 January 2007 10:31 To: [email protected] Subject: Re: [pfSense Support] pfSense SNMP identification hi there, shouldn't it be more easy to customise OpenNMS instead of writing a new jffnms,cricket,nagios-tool? From my moint of view, there are just two files which has to be edited: ./opennms/etc/datacollection-config.xml For collecting data from SNMP ./opennms/etc/snmp-graph.properties for drawing nice graphs !? Adam, I don't want to attack your work, It looks very nice indeed. Nevertheless I'm of the opinion that there is work done again and again ... Yours tmueko Am 24.01.2007 um 15:03 schrieb Adam Armstrong: > Hi, > > I'm currently writing an NMS (http://www.pimpmynetwork.org/ > observer/) which > uses SNMP to automatically guess the operating system of hosts and > setup > graphing/monitoring accordingly. > > The cut-down SNMP daemon in m0n0/pfsense massively reduces the > number of > things I can monitor on m0n0, and I can't see a way to easily > identify them > via SNMP using version strings or similar. I'm currently manually > identifying m0n0 boxes in the database, which then limits the > amount of > information the application tries to poll/display. > > Does anyone have any suggestions on how to identify m0n0wall and > pfSense via > SNMP? > > Could a simple change be made to allow them to be easily > identified? (a > custom OID for pfSense giving out its version would be great!) > > Perhaps an identifier and version could be appended to the FreeBSD > kernel > version? > > (sorry for cross-posting, and for those of you who've seen > something very > similar on the m0n0 list!) > > Thanks, > Adam. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- kommunity GmbH & Co.KG Tom Müller-Kortkamp Netzwerke & Internet Goseriede 4 D-30159 Hannover Phone +49 (0)5 11 - 80 72 58 0 Fax +49 (0)5 11 - 80 72 58 10 http://www.kommunity.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
