McDATA 316095-B21 - StorageWorks Edge Switch 2/24, Руководство пользователя

Страница: 516 / 684

G
G-16
E/OS SNMP Support Manual
SNMPv3 MIB
When a set is received and the usmUserName of the requester is not
the same as the umsUserName that indexes the row which is targeted
by this operation, then a 'noAccess' error must be returned.
When a set is received and the security model in use is not USM, then
a 'noAccess' error must be returned.
DEFVAL { ''H } -- the empty string
Sequence
::= { usmUserEntry 7 }
usmUserPrivProtocol
Syntax
AutonomousType
Max Access
read-create
Status
current
Description
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 if so, the type of privacy protocol
which is used.
An instance of this object is created concurrently with the creation of
any other object instance for the same user (i.e., as part of the
processing of the set operation which creates the first object instance
in the same conceptual row). If an initial set operation (i.e. at row
creation time) tries to set a value for an unknown or unsupported
protocol, then a 'wrongValue' error must be returned. The value will
be overwritten/set when a set operation is performed on the
corresponding instance of usmUserCloneFrom.
Once instantiated, the value of such an instance of this object can only
be changed via a set operation to the value of the
usmNoPrivProtocol. If a set operation tries to change the value of an
existing instance of this object to any value other than
usmNoPrivProtocol, then an 'inconsistentValue' error must be
returned.
Note that if any privacy protocol is used, then you must also use an
authentication protocol. In other words, if usmUserPrivProtocol is set
to anything else than usmNoPrivProtocol, then the corresponding
instance of usmUserAuthProtocol cannot have a value of
usmNoAuthProtocol. If it does, then an 'inconsistentValue' error
must be returned.
DEFVAL { usmNoPrivProtocol }