Re: [opennms-discuss] provisioning/snmp communities?

[Roskens, R. <Ron...@bi...>]

But if you use ip-match, that means that you can't support two different snmp communities for the same host. With a <filter> rule, you could.

From: David Hustace [mailto:da...@op...]
Sent: Thursday, April 26, 2012 8:56 AM
To: General OpenNMS Discussion
Subject: Re: [opennms-discuss] provisioning/snmp communities?


On Apr 25, 2012, at 7:08 PM, Les Mikesell wrote:

Not exactly - I still haven't converted to provisioning yet but
thought that it would be an advantage if I could set up different
groups that would include the community instead of having to figure
out which IPs belong to which kind of equipment and configure the
community for the IP separately.

I would suggest an enhancement to the SNMP configuration to support filter rules:

        <definition version="v2c" read-community="abc" >
          <filter>foreignsource == 'Group1'</filter.
        </definition>

BTW: If you look in etc/examples/snmp-config.xml, you'll find something that most folks don't realize which is definitions support our IPLIKE syntax from filter rules with the <ip-match/> element.

        <definition version="v2c" read-community="abc" >
                <ip-match>77.5-12,15.1-255.255</ip-match>
                <ip-match>10.*.*.*</ip-match>
        </definition>

Which, by adding a filter element, would make this redundant because we could use IPLIKE.


David


This e-mail message is being sent solely for use by the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by phone or reply by e-mail, delete the original message and destroy all copies. Thank you.