Adding Nodes: multiple versions and community strings
Ron Skantz <[email protected]>
| Newsgroups | gmane.network.opennms.install |
|---|---|
| Message-ID | <[email protected]> |
I recently came into an environment where we have 2 different community strings (sometimes in the same ip range) and v1 or v2 of snmp - across our systems. I have successfully installed openNMS and now I'm at the add nodes stage. I successfully generated a new snmp-config.xml file with all the hosts that respond to snmp queries using this method: http://www.opennms.org/wiki/Script:_Multiple_SNMP_Community_String I had previously just auto-discovered our systems by IP range, but that collected a lot of stuff I don't care about including work stations - it seems to include anything that responds to a ping. I have since removed all of those nodes. I'm hoping I can easily limit the monitored nodes to just what is in snmp-config.xml. Is there a way to do this? Or do I need to rescan for nodes and manually remove the superfluous nodes to consolidate with the snmp-config.xml? Thanks for any help/advice, ron ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-install mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-install