Snmpv3 Usm Users - AudioCodes Mediant 800 Reference Manual

CHAPTER 2 SNMP Overview
➢ To delete the read-write v2admin community string:
1. If v2admin is being used as the trap community string, follow the procedure for changing
the trap community string. (See below.)
2. Delete the snmpCommunityTable row with a CommunityName of v2admin and
GroupName of ReadWriteGroup.
➢ To change the only read-write community string from v2admin to v2mgr:
1. Follow the procedure above to add a read-write community string to a row for v2mgr.
2.
Set up the EM such that subsequent set requests use the new community string, v2mgr.
3. If v2admin is being used as the trap community string, follow the procedure to change the
trap community string. (See below.)
4. Follow the procedure above to delete a read-write community name in the row for
v2admin.
The following procedure assumes that a row already exists in the snmpCommunityTable for
the new trap community string. The trap community string can be part of the TrapGroup,
ReadGroup, or ReadWriteGroup. If the trap community string is used solely for sending traps
(recommended), then it should be made part of the TrapGroup.
➢ To change the trap community string:
1. Add a row to the vacmSecurityToGroupTable with these values: SecurityModel=2,
SecurityName=the new trap community string, GroupName=TrapGroup, ReadGroup or
ReadWriteGroup. The SecurityModel and SecurityName objects are row indices.
You must add GroupName and RowStatus on the same set.
2. Modify the SecurityName field in the appropriate row of the snmpTargetParamsTable.
3.
Remove the row from the vacmSecurityToGroupTable with SecurityName=the old trap
community string.

SNMPv3 USM Users

You can configure up to 10 User-based Security Model (USM) users (referred to as SNMPv3
user). Each SNMPv3 user can be configured to one of the following security levels:
Security Levels
noAuthNoPriv(1)
authNoPriv(2)
Table 2-2: SNMPv3 Security Levels
Authentication
none
MD5 or SHA-1
- 10 -
Mediant 800 SBC | SNMP Reference Guide
Privacy
none
none