V7122 Gateway User Guide 3772 Modify the SecurityName field in the sole row of the snmpTargetParamsTable.3 Remove the row from the vacmSecurityToGroupTable with SecurityName = the old trapcommunity string.• The procedure above assumes that a row already exists in thesnmpCommunityTable for the new trap community string. The trap communitystring can be part of the TrapGroup, ReadGroup, or ReadWriteGroup. If thetrap community string is used solely for sending traps (recommended), then itshould be made part of the TrapGroup.• You must add GroupName and RowStatus on the same set.SNMP v3 USM UsersYou can define up to 10 User-based Security Model (USM) users (USM users are referred toas “v3 users”). Each v3 user can be associated with an authentication type (none, MD5, orSHA-1) and a privacy type (none, DES, 3DES, or AES).Table 75 SNMP v3 Security LevelsSecurity Level Authentication PrivacynoAuthNoPriv(1) None NoneauthNoPriv(2) MD5 or SHA-1 NoneauthPriv(3) MD5 or SHA-1 DES, 3DES, AES128, AES192, orAES256Each SNMP v3 user must be associated with one of the predefined groups listed in thefollowing table:Table 76 SNMP v3 Predefined GroupsGroup Get Access Set Access Send Traps Security LevelReadGroup1 Yes No Yes noAuthNoPriv(1)ReadWriteGroup1 Yes Yes Yes noAuthNoPriv(1)TrapGroup1 No No Yes noAuthNoPriv(1)ReadGroup2 Yes No Yes authNoPriv(2)ReadWriteGroup2 Yes Yes Yes authNoPriv(2)TrapGroup2 No No Yes authNoPriv(2)ReadGroup3 Yes No Yes authPriv(3)ReadWriteGroup3 Yes Yes Yes authPriv(3)TrapGroup3 No No Yes authPriv(3)
