McDATA 316095-B21 - StorageWorks Edge Switch 2/24 Manual page 514

SNMPv3 MIB
G
If a set operation tries to change the value of an existing instance of
this object to any value other than usmNoAuthProtocol, then an
'inconsistentValue' error must be returned.
If a set operation tries to set the value to the usmNoAuthProtocol
while the usmUserPrivProtocol value in the same row is not equal to
usmNoPrivProtocol, then an 'inconsistentValue' error must be
returned. That means that an SNMP command generator application
must first ensure that the usmUserPrivProtocol is set to the
usmNoPrivProtocol value before it can set the usmUserAuthProtocol
value to usmNoAuthProtocol.
DEFVAL { usmNoAuthProtocol }
Sequence
::= { usmUserEntry 5 }
usmUserAuthKeyChange
KeyChange -- typically (SIZE (0 | 32)) for HMACMD5 -- typically
Syntax
(SIZE (0 | 40)) for HMACSHA
read-create
Max Access
current
Status
An object, which when modified, causes the secret authentication key
Description
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.
The associated protocol is the usmUserAuthProtocol. The associated
secret key is the user's secret authentication key (authKey). The
associated hash algorithm is the algorithm used by the user's
usmUserAuthProtocol.
When creating a new user, it is an 'inconsistentName' error for a set
operation to refer to this object unless it is previously or concurrently
initialized through a set operation on the corresponding instance of
usmUserCloneFrom.
When the value of the corresponding usmUserAuthProtocol is
usmNoAuthProtocol, then a set is successful, but effectively is a
no-op. When this object is read, the zero-length (empty) string is
returned.
The recommended way to do a key change is as follows:
1. GET(usmUserSpinLock.0) and save in sValue.
E/OS SNMP Support Manual
G-14