FW 08.01.00 McDATA E/OS SNMP Support Manual (620-000131-630, November 2005)

G
SNMPv3 MIB
G-19
SNMPv3 MIB
• 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.
DEFVAL { nonVolatile }
Sequence
::= { usmUserEntry 12 }
usmUserStatus
Syntax RowStatus
Max Access read-create
Status current
Description The status of this conceptual row. Until instances of all corresponding
columns are appropriately configured, the value of the
corresponding instance of the usmUserStatus column is 'notReady'.
In particular, a newly created row for a user who employs
authentication, cannot be made active until the corresponding
usmUserCloneFrom and usmUserAuthKeyChange have been set.
Further, a newly created row for a user who also employs privacy,
cannot be made active until the usmUserPrivKeyChange has been
set.
The RowStatus TC [RFC2579] requires that this DESCRIPTION
clause states under which circumstances other objects in this row can
be modified:
The value of this object has no effect on whether other objects in this
conceptual row can be modified, except for
usmUserOwnAuthKeyChange and usmUserOwnPrivKeyChange.
For these 2 objects, the value of usmUserStatus MUST be active.