Talk:Snmp Issues
Subscribe

From OpenNMS

Jump to: navigation, search

Perhaps we can offer these changed to the snmp-config.xml:

<snmp-config default-version="v1" default-port="161" default-retry="3" default-timeout="800" default-read-community="public" persist-version="true" >

  <versions>
    <version specification="v3"  protocol="tcp" port="161" security-name="opennms" auth-passphrase="opennms" use-get-bulk="true" />
    <version specification="v2c" protocol="udp" port="161" read-community="whatzup" use-get-bulk="true" />
    <version specification="v1"  protocol="udp" port="161" read-community="whatzup" />
  </versions>

  <definition>
    <ip-match>10.*.*.*</ip-match>
    <versions>
      <version specification="v3"  protocol="tcp" port="161" security-name="opennms" auth-passphrase="opennms" use-get-bulk="true" />
      <version specification="v2c" protocol="udp" port="161" read-community="whatzup" use-get-bulk="true" />
      <version specification="v1"  protocol="udp" port="161" read-community="whatzup" />
    </versions>
  </definition>

</snmp-config>

I'm also noodling thoughts about putting <agent> tags in this config. This way agents could be identified independently from nodes. We would want the ability to have many-to-one agents to nodes relationship. Thoughts?