User`s manual

H.323 User's Manual 15. SNMP-Based Management
Version 5.0 357 December 2006
15.7.2.1 Configuring SNMP v3 users via the ini File
Use the SNMPUsers ini table to add, modify, and delete SNMPv3 users. For a description
of the SNMPUsers table ini file parameters, refer to Section 6.5.6 on page 225.
Note: The SNMPUsers ini table is a hidden parameter. Therefore, when you
perform a “Get ini File” operation using the Web interface, the table will not
be included in the generated file.
You can enter keys in the form of a text password or in the form of a localized key in hex
format. If using a text password, then it should be at least eight characters in length. Below
is an example of a localized key format:
26:60:d8:7d:0d:4a:d6:8c:02:73:dd:22:96:a2:69:df
The following example configuration creates three SNMPv3 USM users:
[ SNMPUsers ]
FORMAT SNMPUsers_Index = SNMPUsers_Username, SNMPUsers_AuthProtocol,
SNMPUsers_PrivProtocol, SNMPUsers_AuthKey, SNMPUsers_PrivKey, SNMPUsers_Group;
SNMPUsers 0 = v3user, 0, 0, -, -, 0;
SNMPUsers 1 = v3admin1, 1, 0, myauthkey, -, 1;
SNMPUsers 2 = v3admin2, 2, 1, myauthkey, myprivkey, 1;
[ \SNMPUsers ]
The example above creates the following three v3 users:
 The user "v3user" is defined for a security level of noAuthNoPriv(1) and is associated
with ReadGroup1.
 The user "v3admin1" is defined for a security level of authNoPriv(2) with
authentication protocol MD5. The authentication text password is “myauthkey” and the
user will be associated with ReadWriteGroup2.
 The user "v3admin2" is defined for a security level of authPriv(3) with authentication
protocol SHA-1 and privacy protocol DES. The authentication text password is
“myauthkey”, the privacy text password is “myprivkey”, and the user will be associated
with ReadWriteGroup3.
15.7.2.2 Configuring SNMP v3 Users via SNMP
To configure SNMP v3 users, the EM must use the standard snmpUsmMIB and the
snmpVacmMIB.
¾ To add a read-only, noAuthNoPriv SNMPv3 user (v3user), take
these 3 steps:
1. Clone the row with the same security level. After the clone step, the status of the row
is notReady(3).
2. Activate the row (i.e., set the row status to active(1)).
3. Add a row to the vacmSecurityToGroupTable for SecurityName v3user, GroupName
ReadGroup1, and SecurityModel usm(3).
Note: A row with the same security level (noAuthNoPriv) must already exist in the
usmUserTable. (See the usmUserTable for details).