SNMP-USER-BASED-SM-MIB

Object (OID)

Access

Syntax

Value range

Description

Implementation

usmStatsUnsupportedSecLevels (1.3.6.1.6.3.15.1.1.1)

read-only

Counter32

Standard MIB values

Total number of packets received but dropped by the SNMP engine because they requested a security level unknown to the SNMP engine or not available.

As per the MIB.

Object (OID)

Access

Syntax

Value range

Description

Implementation

usmStatsNotInTimeWindows (1.3.6.1.6.3.15.1.1.2)

read-only

Counter32

Standard MIB values

Total number of packets received but dropped by the SNMP engine because they appeared outside of the authoritative SNMP engine's window.

As per the MIB.

Object (OID)

Access

Syntax

Value range

Description

Implementation

usmStatsUnknownUserNames (1.3.6.1.6.3.15.1.1.3)

read-only

Counter32

Standard MIB values

Total number of packets received but dropped by the SNMP engine because they referenced a user unknown to the SNMP engine.

As per the MIB.

Object (OID)

Access

Syntax

Value range

Description

Implementation

usmStatsUnknownEngineIDs (1.3.6.1.6.3.15.1.1.4)

read-only

Counter32

Standard MIB values

Total number of packets received but dropped by the SNMP engine because they referenced an SNMP Engine ID unknown to the SNMP engine.

As per the MIB.

Object (OID)

Access

Syntax

Value range

Description

Implementation

usmStatsWrongDigests (1.3.6.1.6.3.15.1.1.5)

read-only

Counter32

Standard MIB values

Total number of packets received but dropped by the SNMP engine because they did not contain the expected digest value.

As per the MIB.

Object (OID)

Access

Syntax

Value range

Description

Implementation

usmStatsDecryptionErrors (1.3.6.1.6.3.15.1.1.6)

read-only

Counter32

Standard MIB values

Total number of packets received but dropped by the SNMP engine because they could not be decrypted.

As per the MIB.

Object (OID)

Access

Syntax

Value range

Description

Implementation

usmUserSpinLock (1.3.6.1.6.3.15.1.2.1)

read-write

TestAndIncr

Standard MIB values

An advisory lock used to allow several cooperating command generator applications to coordinate their use of facilities to alter secrets in the usmUserTable.

As per the MIB.

Create

Edit/Modify

Delete

Read

Supported

Supported

Supported

Supported

usmUserEngineID (1.3.6.1.6.3.15.1.2.2.1.1)

not-accessible

SnmpEngineID

OCTET STRING (5..32)

Administratively unique identifier for the SNMP engine.

As per the MIB.

usmUserName (1.3.6.1.6.3.15.1.2.2.1.2)

not-accessible

SnmpAdminString

OCTET STRING (1..32)

Use name. It is the (user-based security) model dependent security ID.

The value can contain only displayable characters except question marks.

usmUserSecurityName (1.3.6.1.6.3.15.1.2.2.1.3)

read-only

SnmpAdminString

OCTET STRING (0..255)

A human readable string representing the user in security model independent format.

The default transformation of the user-based security model dependent security ID to the security name and vice versa is the identity function so that the security name is the same as the user name.

As per the MIB.

usmUserCloneFrom (1.3.6.1.6.3.15.1.2.2.1.4)

read-create

RowPointer

Standard MIB values

A pointer to another conceptual row in this usmUserTable. The user in this other conceptual row is called the clone-from user.

This object must be specified for creating an instance.

If the object corresponds to a user created by the command line, this operation succeeds but does not take effect.

When a new user is created (a new conceptual row is instantiated in this table), the privacy and authentication parameters of the new user must be cloned from its clone-from user. These parameters are:

·     authentication protocol (usmUserAuthProtocol)

·     privacy protocol (usmUserPrivProtocol)

They will be copied regardless of what the current value is.

Cloning also causes the initial values of the secret authentication key (authKey) and the secret encryption key (privKey) of the new user to be set to the same values as the corresponding secrets of the clone-from user to allow the KeyChange process to occur as required during user creation.

The first time an instance of this object is set by a management operation (either at or after its instantiation), the cloning process is invoked.

Subsequent writes are successful but invoke no action to be taken by the receiver.

The cloning process fails with an inconsistentName error if the conceptual row representing the clone-from user does not exist or is not in an active state when the cloning process is invoked.

When this object is read, the ZeroDotZero OID is returned.

usmUserAuthProtocol (1.3.6.1.6.3.15.1.2.2.1.5)

read-create

AutonomousType

Standard MIB values

Indicates whether messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID can be authenticated and the authentication protocol to be used.

As per the MIB.

usmUserAuthKeyChange (1.3.6.1.6.3.15.1.2.2.1.6)

read-create

KeyChange

-- typically (SIZE (0 | 32)) for HMACMD5

-- typically (SIZE (0 | 40)) for HMACSHA

An object, which when modified, causes the secret authentication key used for messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, to be modified via a one-way function.

When read, this object returns a zero-length string.

usmUserOwnAuthKeyChange (1.3.6.1.6.3.15.1.2.2.1.7)

read-create

KeyChange

-- typically (SIZE (0 | 32)) for HMACMD5

-- typically (SIZE (0 | 40)) for HMACSHA

Functions exactly as usmUserAuthKeyChange, with one notable difference: in order for the set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation.

When read, this object returns a zero-length string.

usmUserPrivProtocol (1.3.6.1.6.3.15.1.2.2.1.8)

read-create

AutonomousType

Standard MIB values

An indication of whether messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID can be protected from disclosure, and the type of privacy protocol to be used.

As per the MIB.

usmUserPrivKeyChange (1.3.6.1.6.3.15.1.2.2.1.9)

read-create

KeyChange

-- typically (SIZE (0 | 32)) for DES

An object, which when modified, causes the secret encryption key used for messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, to be modified via a one-way function.

When read, this object returns a zero-length string.

usmUserOwnPrivKeyChange (1.3.6.1.6.3.15.1.2.2.1.10)

read-create

KeyChange

Standard MIB values

Functions exactly as usmUserPrivKeyChange, with one notable difference: in order for the Set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation.

When read, this object returns a zero-length string.

usmUserPublic (1.3.6.1.6.3.15.1.2.2.1.11)

read-create

OCTET STRING

OCTET STRING (0..32)

A publicly-readable value that can be written as part of the procedure for changing a user's secret authentication and/or privacy key, and later read to determine whether the change of the secret was effected.

As per the MIB.

usmUserStorageType (1.3.6.1.6.3.15.1.2.2.1.12)

read-create

StorageType

other(1),

volatile(2),

nonVolatile(3),

permanent(4),

readOnly(5)

Storage type for this conceptual row.

Supports only nonVolatile(3).

usmUserStatus (1.3.6.1.6.3.15.1.2.2.1.13)

read-create

RowStatus

active(1),

notInService(2),

notReady(3),

createAndGo(4),

createAndWait(5),

destroy(6)

Row status.

As per the MIB.