Trusted Managers - 3Com V7122 User Manual

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):
If v3 user is associated with a trap destination, follow the procedure for associating a
1
different user to that trap destination. (See below.)
Delete the vacmSecurityToGroupTable row for SecurityName v3user, GroupName
2
ReadGroup1, and SecurityModel usm.
Delete the row in the usmUserTable for v3user.
3
To add a read-write, authPriv SNMPv3 user (v3user):
Clone the row with the same security level.
1
Change the authentication key and privacy key.
2
Activate the row. That is, set the row status to active(1).
3
Add a row to the vacmSecurityToGroupTable for SecurityName v3admin1, GroupName
4
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):
If v3admin1 is associated with a trap destination, follow the procedure for associating a
1
different user to that trap destination. (See below.)
Delete the vacmSecurityToGroupTable row for SecurityName v3admin1, GroupName
2
ReadWriteGroup1, and SecurityModel usm.
Delete the row in the usmUserTable for v3admin1.
3

Trusted Managers

By default, the agent accepts 'get' and 'set' requests from any IP address, as long as the
correct community string is used in the request. Security can be enhanced using the use of
Trusted Managers. A Trusted Manager is an IP address from which the SNMP Agent
accepts and processes 'get' and 'set' requests. An EM can be used to configure up to five
Trusted Managers.
If Trusted Managers are defined, all community strings work from all Trusted
Managers. That is, there is no way to associate a community string with particular
trusted managers.
V7122 Gateway User Guide
379