Configuring SNMPv3 Users via SNMP
To configure SNMPv3 users, the EMS must use the standard snmpUsmMIB and the snmpVacmMIB.
| ➢ | To add a read-only, noAuthNoPriv SNMPv3 user, v3user: |
| 1. | Clone the row with the same security level. After the clone step, the status of the row will be notReady(3). |
| 2. | Activate the row. That is, set the row status to active(1). |
| 3. | Add a row to the vacmSecurityToGroupTable for SecurityName v3user, GroupName ReadGroup1 and SecurityModel usm(3). |
A row with the same security level (noAuthNoPriv) must already exist in the usmUserTable. (see the usmUserTable for details).
| ➢ | To delete the read-only, noAuthNoPriv SNMPv3 user, v3user: |
| 1. | If v3user is associated with a trap destination, follow the procedure for associating a different user to that trap destination. (See below.) |
| 2. | Delete the vacmSecurityToGroupTable row for SecurityName v3user, GroupName ReadGroup1 and SecurityModel usm. |
| 3. | Delete the row in the usmUserTable for v3user. |
| ➢ | To add a read-write, authPriv SNMPv3 user, v3admin1: |
| 1. | Clone the row with the same security level. |
| 2. | Change the authentication key and privacy key. |
| 3. | Activate the row. That is, set the row status to active(1). |
| 4. | Add a row to the vacmSecurityToGroupTable for SecurityName v3admin1, GroupName ReadWriteGroup3 and SecurityModel usm(3). |
A row with the same security level (authPriv) must already exist in the usmUserTable (see the usmUserTable for details).
| ➢ | To delete the read-write, authPriv SNMPv3 user, v3admin1: |
| 1. | If v3admin1 is associated with a trap destination, follow the procedure for associating a different user to that trap destination. (See below.) |
| 2. | Delete the vacmSecurityToGroupTable row for SecurityName v3admin1, GroupName ReadWriteGroup1 and SecurityModel usm. |
| 3. | Delete the row in the usmUserTable for v3admin1. |