SNMP-USER-BASED-SM-MIB :: usmUserStorageType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsSNMP-USER-BASED-SM-MIBusmUserStorageType

usmUserStorageType

Module: SNMP-USER-BASED-SM-MIB

OID (symbolic): SNMP-USER-BASED-SM-MIB::usmUserStorageType

OID (numeric): 1.3.6.1.6.3.15.1.2.2.1.12

Node type: OBJECT-TYPE

Type: StorageType

Access: read-create

Description: The storage type for this conceptual row.

Conceptual rows having the value 'permanent' must allow write-access at a minimum to:

- usmUserAuthKeyChange, usmUserOwnAuthKeyChange and usmUserPublic for a user who employs authentication, and - usmUserPrivKeyChange, usmUserOwnPrivKeyChange and usmUserPublic for a user who employs privacy.

Note that any user who employs authentication or privacy must allow its secret(s) to be updated and thus cannot be 'readOnly'.

If an initial set operation tries to set the value to 'readOnly' for a user who employs authentication or privacy, then an 'inconsistentValue' error must be returned. Note that if the value has been previously set (implicit or explicit) to any value, then the rules as defined in the StorageType Textual Convention apply.

It is an implementation issue to decide if a SET for a readOnly or permanent row is accepted at all. In some contexts this may make sense, in others it may not. If a SET for a readOnly or permanent row is not accepted at all, then a 'wrongValue' error must be returned.

What is usmUserStorageType?

This StorageType value indicates how a usmUserTable row is persisted, for example volatile, nonVolatile, or permanent, and it defaults to nonVolatile. A row marked permanent must still allow writes to usmUserAuthKeyChange, usmUserOwnAuthKeyChange, usmUserPrivKeyChange, usmUserOwnPrivKeyChange, and usmUserPublic for any user that uses authentication or privacy, since those secrets must remain changeable even on a row that can't be deleted. An admin trying to set a privacy-enabled user's storage type to readOnly would get an inconsistentValue error, because a user with privacy configured must always be able to update its secret keys.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.6snmpV2DASAN-DHCP-MIB
1.3.6.1.6.3snmpModulesRAPID-CITY
Numeric OIDNameModule
1.3.6.1.6.3.15snmpUsmMIBSNMP-USER-BASED-SM-MIB
1.3.6.1.6.3.15.1usmMIBObjectsSNMP-USER-BASED-SM-MIB
1.3.6.1.6.3.15.1.2usmUserSNMP-USER-BASED-SM-MIB
1.3.6.1.6.3.15.1.2.2usmUserTableSNMP-USER-BASED-SM-MIB
1.3.6.1.6.3.15.1.2.2.1usmUserEntrySNMP-USER-BASED-SM-MIB
1.3.6.1.6.3.15.1.2.2.1.12usmUserStorageTypeSNMP-USER-BASED-SM-MIB