Use this table to create users.
\r\n\r\nCreate：Supported
\r\n\r\nEdit/Modify：Supported
\r\n\r\nDelete：Supported
\r\n\r\nRead：Supported
\r\n\r\nThe table indexes are usmUserEngineID and\r\nusmUserName.
\r\n\r\n| \r\n Object (OID) \r\n | \r\n \r\n Access \r\n | \r\n \r\n Syntax \r\n | \r\n \r\n Value range \r\n | \r\n \r\n Description \r\n | \r\n \r\n Implementation \r\n | \r\n \r\n
| \r\n usmUserEngineID\r\n (1.3.6.1.6.3.15.1.2.2.1.1) \r\n | \r\n \r\n not-accessible \r\n | \r\n \r\n SnmpEngineID \r\n | \r\n \r\n OCTET STRING (5..32) \r\n | \r\n \r\n Administratively unique identifier for\r\n the SNMP engine. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
| \r\n usmUserName (1.3.6.1.6.3.15.1.2.2.1.2) \r\n | \r\n \r\n not-accessible \r\n | \r\n \r\n SnmpAdminString \r\n | \r\n \r\n OCTET STRING (1..32) \r\n | \r\n \r\n Use name. It is the (user-based security)\r\n model dependent security ID. \r\n | \r\n \r\n The value can contain only displayable\r\n characters except question marks. \r\n | \r\n \r\n
| \r\n usmUserSecurityName\r\n (1.3.6.1.6.3.15.1.2.2.1.3) \r\n | \r\n \r\n read-only \r\n | \r\n \r\n SnmpAdminString \r\n | \r\n \r\n OCTET STRING (0..255) \r\n | \r\n \r\n A human readable string representing the\r\n user in security model independent format. \r\nThe default transformation of the\r\n user-based security model dependent security ID to the security name and vice\r\n versa is the identity function so that the security name is the same as the\r\n user name. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
| \r\n usmUserCloneFrom\r\n (1.3.6.1.6.3.15.1.2.2.1.4) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n RowPointer \r\n | \r\n \r\n Standard MIB values \r\n | \r\n \r\n A pointer to another conceptual row in\r\n this usmUserTable. The user in this other conceptual row is called the\r\n clone-from user. \r\n | \r\n \r\n This object must be specified for\r\n creating an instance. \r\nIf the object corresponds to a user\r\n created by the command line, this operation succeeds but does not take\r\n effect. \r\nWhen a new user is created (a new\r\n conceptual row is instantiated in this table), the privacy and authentication\r\n parameters of the new user must be cloned from its clone-from user. These\r\n parameters are: \r\nauthentication protocol (usmUserAuthProtocol) \r\nprivacy protocol (usmUserPrivProtocol) \r\nThey will be copied regardless of what\r\n the current value is. \r\nCloning also causes the initial values of\r\n the secret authentication key (authKey) and the secret encryption key\r\n (privKey) of the new user to be set to the same values as the corresponding\r\n secrets of the clone-from user to allow the KeyChange process to occur as\r\n required during user creation. \r\nThe first time an instance of this object\r\n is set by a management operation (either at or after its instantiation), the\r\n cloning process is invoked. \r\nSubsequent writes are successful but\r\n invoke no action to be taken by the receiver. \r\nThe cloning process fails with an\r\n inconsistentName error if the conceptual row representing the clone-from user\r\n does not exist or is not in an active state when the cloning process is\r\n invoked. \r\nWhen this object is read, the ZeroDotZero\r\n OID is returned. \r\n | \r\n \r\n
| \r\n usmUserAuthProtocol\r\n (1.3.6.1.6.3.15.1.2.2.1.5) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n AutonomousType \r\n | \r\n \r\n Standard MIB values \r\n | \r\n \r\n Indicates whether messages sent on behalf\r\n of this user to/from the SNMP engine identified by usmUserEngineID can be\r\n authenticated and the authentication protocol to be used. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
| \r\n usmUserAuthKeyChange\r\n (1.3.6.1.6.3.15.1.2.2.1.6) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n KeyChange \r\n | \r\n \r\n -- typically (SIZE (0 | 32)) for HMACMD5 \r\n-- typically (SIZE (0 | 40)) for HMACSHA \r\n | \r\n \r\n An object, which when modified, causes\r\n the secret authentication key used for messages sent on behalf of this user\r\n to/from the SNMP engine identified by usmUserEngineID, to be modified via a\r\n one-way function. \r\n | \r\n \r\n When read, this object returns a\r\n zero-length string. \r\n | \r\n \r\n
| \r\n usmUserOwnAuthKeyChange\r\n (1.3.6.1.6.3.15.1.2.2.1.7) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n KeyChange \r\n | \r\n \r\n -- typically (SIZE (0 | 32)) for HMACMD5 \r\n-- typically (SIZE (0 | 40)) for HMACSHA \r\n | \r\n \r\n Functions exactly as\r\n usmUserAuthKeyChange, with one notable difference: in order for the set\r\n operation to succeed, the usmUserName of the operation requester must match\r\n the usmUserName that indexes the row which is targeted by this operation. \r\n | \r\n \r\n When read, this object returns a\r\n zero-length string. \r\n | \r\n \r\n
| \r\n usmUserPrivProtocol\r\n (1.3.6.1.6.3.15.1.2.2.1.8) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n AutonomousType \r\n | \r\n \r\n Standard MIB values \r\n | \r\n \r\n An indication of whether messages sent on\r\n behalf of this user to/from the SNMP engine identified by usmUserEngineID can\r\n be protected from disclosure, and the type of privacy protocol to be used. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
| \r\n usmUserPrivKeyChange\r\n (1.3.6.1.6.3.15.1.2.2.1.9) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n KeyChange \r\n | \r\n \r\n -- typically (SIZE (0 | 32)) for DES \r\n | \r\n \r\n An object, which when modified, causes\r\n the secret encryption key used for messages sent on behalf of this user\r\n to/from the SNMP engine identified by usmUserEngineID, to be modified via a\r\n one-way function. \r\n | \r\n \r\n When read, this object returns a\r\n zero-length string. \r\n | \r\n \r\n
| \r\n usmUserOwnPrivKeyChange\r\n (1.3.6.1.6.3.15.1.2.2.1.10) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n KeyChange \r\n | \r\n \r\n Standard MIB values \r\n | \r\n \r\n Functions exactly as\r\n usmUserPrivKeyChange, with one notable difference: in order for the Set\r\n operation to succeed, the usmUserName of the operation requester must match\r\n the usmUserName that indexes the row which is targeted by this operation. \r\n | \r\n \r\n When read, this object returns a\r\n zero-length string. \r\n | \r\n \r\n
| \r\n usmUserPublic (1.3.6.1.6.3.15.1.2.2.1.11) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n OCTET STRING \r\n | \r\n \r\n OCTET STRING (0..32) \r\n | \r\n \r\n A publicly-readable value that can be\r\n written as part of the procedure for changing a user's secret authentication\r\n and/or privacy key, and later read to determine whether the change of the\r\n secret was effected. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
| \r\n usmUserStorageType\r\n (1.3.6.1.6.3.15.1.2.2.1.12) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n StorageType \r\n | \r\n \r\n other(1), \r\nvolatile(2), \r\nnonVolatile(3), \r\npermanent(4), \r\nreadOnly(5) \r\n | \r\n \r\n Storage type for this conceptual row. \r\n | \r\n \r\n Supports only nonVolatile(3). \r\n | \r\n \r\n
| \r\n usmUserStatus (1.3.6.1.6.3.15.1.2.2.1.13) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n RowStatus \r\n | \r\n \r\n active(1), \r\nnotInService(2), \r\nnotReady(3), \r\ncreateAndGo(4), \r\ncreateAndWait(5), \r\ndestroy(6) \r\n | \r\n \r\n Row status. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
\r\n\r\n
\r\n\r\n\r\n\r\n
Use this table to create users.
\r\n\r\nCreate：Supported
\r\n\r\nEdit/Modify：Supported
\r\n\r\nDelete：Supported
\r\n\r\nRead：Supported
\r\n\r\nThe table indexes are usmUserEngineID and\r\nusmUserName.
\r\n\r\n| \r\n Object (OID) \r\n | \r\n \r\n Access \r\n | \r\n \r\n Syntax \r\n | \r\n \r\n Value range \r\n | \r\n \r\n Description \r\n | \r\n \r\n Implementation \r\n | \r\n \r\n
| \r\n usmUserEngineID\r\n (1.3.6.1.6.3.15.1.2.2.1.1) \r\n | \r\n \r\n not-accessible \r\n | \r\n \r\n SnmpEngineID \r\n | \r\n \r\n OCTET STRING (5..32) \r\n | \r\n \r\n Administratively unique identifier for\r\n the SNMP engine. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
| \r\n usmUserName (1.3.6.1.6.3.15.1.2.2.1.2) \r\n | \r\n \r\n not-accessible \r\n | \r\n \r\n SnmpAdminString \r\n | \r\n \r\n OCTET STRING (1..32) \r\n | \r\n \r\n Use name. It is the (user-based security)\r\n model dependent security ID. \r\n | \r\n \r\n The value can contain only displayable\r\n characters except question marks. \r\n | \r\n \r\n
| \r\n usmUserSecurityName\r\n (1.3.6.1.6.3.15.1.2.2.1.3) \r\n | \r\n \r\n read-only \r\n | \r\n \r\n SnmpAdminString \r\n | \r\n \r\n OCTET STRING (0..255) \r\n | \r\n \r\n A human readable string representing the\r\n user in security model independent format. \r\nThe default transformation of the\r\n user-based security model dependent security ID to the security name and vice\r\n versa is the identity function so that the security name is the same as the\r\n user name. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
| \r\n usmUserCloneFrom\r\n (1.3.6.1.6.3.15.1.2.2.1.4) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n RowPointer \r\n | \r\n \r\n Standard MIB values \r\n | \r\n \r\n A pointer to another conceptual row in\r\n this usmUserTable. The user in this other conceptual row is called the\r\n clone-from user. \r\n | \r\n \r\n This object must be specified for\r\n creating an instance. \r\nIf the object corresponds to a user\r\n created by the command line, this operation succeeds but does not take\r\n effect. \r\nWhen a new user is created (a new\r\n conceptual row is instantiated in this table), the privacy and authentication\r\n parameters of the new user must be cloned from its clone-from user. These\r\n parameters are: \r\nauthentication protocol (usmUserAuthProtocol) \r\nprivacy protocol (usmUserPrivProtocol) \r\nThey will be copied regardless of what\r\n the current value is. \r\nCloning also causes the initial values of\r\n the secret authentication key (authKey) and the secret encryption key\r\n (privKey) of the new user to be set to the same values as the corresponding\r\n secrets of the clone-from user to allow the KeyChange process to occur as\r\n required during user creation. \r\nThe first time an instance of this object\r\n is set by a management operation (either at or after its instantiation), the\r\n cloning process is invoked. \r\nSubsequent writes are successful but\r\n invoke no action to be taken by the receiver. \r\nThe cloning process fails with an\r\n inconsistentName error if the conceptual row representing the clone-from user\r\n does not exist or is not in an active state when the cloning process is\r\n invoked. \r\nWhen this object is read, the ZeroDotZero\r\n OID is returned. \r\n | \r\n \r\n
| \r\n usmUserAuthProtocol\r\n (1.3.6.1.6.3.15.1.2.2.1.5) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n AutonomousType \r\n | \r\n \r\n Standard MIB values \r\n | \r\n \r\n Indicates whether messages sent on behalf\r\n of this user to/from the SNMP engine identified by usmUserEngineID can be\r\n authenticated and the authentication protocol to be used. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
| \r\n usmUserAuthKeyChange\r\n (1.3.6.1.6.3.15.1.2.2.1.6) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n KeyChange \r\n | \r\n \r\n -- typically (SIZE (0 | 32)) for HMACMD5 \r\n-- typically (SIZE (0 | 40)) for HMACSHA \r\n | \r\n \r\n An object, which when modified, causes\r\n the secret authentication key used for messages sent on behalf of this user\r\n to/from the SNMP engine identified by usmUserEngineID, to be modified via a\r\n one-way function. \r\n | \r\n \r\n When read, this object returns a\r\n zero-length string. \r\n | \r\n \r\n
| \r\n usmUserOwnAuthKeyChange\r\n (1.3.6.1.6.3.15.1.2.2.1.7) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n KeyChange \r\n | \r\n \r\n -- typically (SIZE (0 | 32)) for HMACMD5 \r\n-- typically (SIZE (0 | 40)) for HMACSHA \r\n | \r\n \r\n Functions exactly as\r\n usmUserAuthKeyChange, with one notable difference: in order for the set\r\n operation to succeed, the usmUserName of the operation requester must match\r\n the usmUserName that indexes the row which is targeted by this operation. \r\n | \r\n \r\n When read, this object returns a\r\n zero-length string. \r\n | \r\n \r\n
| \r\n usmUserPrivProtocol\r\n (1.3.6.1.6.3.15.1.2.2.1.8) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n AutonomousType \r\n | \r\n \r\n Standard MIB values \r\n | \r\n \r\n An indication of whether messages sent on\r\n behalf of this user to/from the SNMP engine identified by usmUserEngineID can\r\n be protected from disclosure, and the type of privacy protocol to be used. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
| \r\n usmUserPrivKeyChange\r\n (1.3.6.1.6.3.15.1.2.2.1.9) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n KeyChange \r\n | \r\n \r\n -- typically (SIZE (0 | 32)) for DES \r\n | \r\n \r\n An object, which when modified, causes\r\n the secret encryption key used for messages sent on behalf of this user\r\n to/from the SNMP engine identified by usmUserEngineID, to be modified via a\r\n one-way function. \r\n | \r\n \r\n When read, this object returns a\r\n zero-length string. \r\n | \r\n \r\n
| \r\n usmUserOwnPrivKeyChange\r\n (1.3.6.1.6.3.15.1.2.2.1.10) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n KeyChange \r\n | \r\n \r\n Standard MIB values \r\n | \r\n \r\n Functions exactly as\r\n usmUserPrivKeyChange, with one notable difference: in order for the Set\r\n operation to succeed, the usmUserName of the operation requester must match\r\n the usmUserName that indexes the row which is targeted by this operation. \r\n | \r\n \r\n When read, this object returns a\r\n zero-length string. \r\n | \r\n \r\n
| \r\n usmUserPublic (1.3.6.1.6.3.15.1.2.2.1.11) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n OCTET STRING \r\n | \r\n \r\n OCTET STRING (0..32) \r\n | \r\n \r\n A publicly-readable value that can be\r\n written as part of the procedure for changing a user's secret authentication\r\n and/or privacy key, and later read to determine whether the change of the\r\n secret was effected. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
| \r\n usmUserStorageType\r\n (1.3.6.1.6.3.15.1.2.2.1.12) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n StorageType \r\n | \r\n \r\n other(1), \r\nvolatile(2), \r\nnonVolatile(3), \r\npermanent(4), \r\nreadOnly(5) \r\n | \r\n \r\n Storage type for this conceptual row. \r\n | \r\n \r\n Supports only nonVolatile(3). \r\n | \r\n \r\n
| \r\n usmUserStatus (1.3.6.1.6.3.15.1.2.2.1.13) \r\n | \r\n \r\n read-create \r\n | \r\n \r\n RowStatus \r\n | \r\n \r\n active(1), \r\nnotInService(2), \r\nnotReady(3), \r\ncreateAndGo(4), \r\ncreateAndWait(5), \r\ndestroy(6) \r\n | \r\n \r\n Row status. \r\n | \r\n \r\n As per the MIB. \r\n | \r\n \r\n
\r\n\r\n
\r\n\r\n\r\n\r\n