System information

com2sec notConfigUser default public
#group notConfigGroup v1 notConfigUser
#group notConfigGroup v2c notConfigUser
group notConfigGroup usm opennmsUser
#view systemview included .1.3.6.1.2.1.1
#view systemview included .1.3.6.1.2.1.25.1.1
view all included .1
#access notConfigGroup "" any noauth exact all none none
access notConfigGroup "" usm priv exact all none none
syslocation Caledon, ON
syscontact Leif Madsen [e-mail]
#rwuser initial
master agentx
agentXSocket /var/agentx/master
agentXPerms 0660 0775 nobody root
sysObjectID .1.3.6.1.4.1.22736.1
You’ll also notice we’ve commented out the rwuser initial line as we
no longer need to permit full read/write access to the SNMP daemon.
Permitting read/write access to the initial user is only necessary when
making changes using the snmpusm application.
On the group line, we’ve configured the system to use usm (the User-based Security
Model) and permitted the opennmsUser to connect. We control how it can connect with
the access line, where we’ve enabled access via the notConfigGroup using usm and the
priv model, which makes sure we connect using both authentication and privacy set-
tings. These in turn make sure that we authenticate securely and transmit data
encrypted.
After modifying the /etc/snmp/snmpd.conf file, restart the SNMP daemon one last time:
$ sudo /etc/init.d/snmpd restart
Then verify that you can still access data via snmpwalk:
$ sudo snmpwalk -v 3 -u opennmsUser -n "" -l authPriv \
-a MD5 -A 0p3nNMSv3 \
-x DES -X 0p3nNMSv3 \
localhost ifTable
and that Asterisk is still able to connect via AgentX with snmpwalk:
$ sudo snmpwalk -v 3 -u opennmsUser -n "" -l authPriv \
-a MD5 -A 0p3nNMSv3 \
SNMP | 557