USEC-MIB
The MIB module for configuring the USEC security and privacy services.
Main OID:
usecMIB.1.3.6.1.6.3.1135
27
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
27 total| Object Name |
|---|
usecMIBThe MIB module for configuring the USEC security and privacy
services. MODULE-IDENTITY .1.3.6.1.6.3.1135 |
usecScalars OBJECT IDENTIFIER .1.3.6.1.6.3.1135.1 |
snmpBootsThe number of times the management system on a device has
been re-initialized since its initial configuration.ro Integer32 (-1..2147483647) .1.3.6.1.6.3.1135.1.1 |
snmpTimeThe number of seconds since the SNMPv2 protocol entity
last incremented the snmpBoots object.ro Integer32 .1.3.6.1.6.3.1135.1.2 |
usecStats OBJECT IDENTIFIER .1.3.6.1.6.3.1135.2 |
usecStatsNotInTimeWindowsA count of the number of packets that were deemed
unauthentic due to the authSnmpBoots or authSnmpTime values
being out of lifetime.ro Counter32 .1.3.6.1.6.3.1135.2.1 |
usecStatsUnknownUserNamesA count of the number of packets containing an SPI
associated with usecNoAuth(4), usecAuth(5), or usecPriv(6),
but whose userNames were not found in the
userNameTable.ro Counter32 .1.3.6.1.6.3.1135.2.2 |
usecStatsWrongDigestValuesA count of the number of packets that were deemed
unauthentic due to the digest value being incorrect.ro Counter32 .1.3.6.1.6.3.1135.2.3 |
usecStatsBadPrivacysA count of the number of packets received which were
encrypted incorrectly.ro Counter32 .1.3.6.1.6.3.1135.2.4 |
usecUser OBJECT IDENTIFIER .1.3.6.1.6.3.1135.3 |
userSpinLockAn advisory lock used to allow several cooperating SNMPv2
entities, all acting in a manager role, to coordinate their
use of SNMPv2 set operations to entries in the userNameTable.
A manager application should include the value of
userSpinLock in every set operation which accesses the
userNameTable. Since this is an advisory lock, entities
acting in an agent role do not enforce the use of
userSpinLock.rw TestAndIncr (SNMPv2-TC) .1.3.6.1.6.3.1135.3.1 |
maxUserNameLengthThe maximum length of userName allowed by this implementation.
This value can be probed by a management application prior
to attempting a row creation operation in the userNameTable.
A value of 0 indicates that the userNameTable does not allow
row creation or deletion operations.ro Integer32 .1.3.6.1.6.3.1135.3.2 |
userNameTableThe SNMPv2 database for usecNoAuth(4), usecAuth(5), and
usecPriv(6) users. SEQUENCE OF UserNameEntry .1.3.6.1.6.3.1135.3.3 |
userNameEntryInformation about a particular SNMPv2 user. UserNameEntry .1.3.6.1.6.3.1135.3.3.1 |
userAuthSnmpIDThe node's administratively-unique identifier.
In a simple agent, this value will always be equal to the
agent's snmpID object.
In a manager which does not send or receive inform requests,
this value will be equal to the snmpID object of the
agent with which this user can communicate.
In a manager which sends or receives inform requests, this
object will be equal to one of three things:
- The snmpID of the agent with which this user
can communicate.
- The snmpID of the manager's local protocol engine.
- The snmpID of a remote manager which this user
can send inform requests to or receive inform requests
from.
In a dual-role entity, this value will be some combination
of those specified for agents and managers above. SnmpID (V2ADMIN-MIB) .1.3.6.1.6.3.1135.3.3.1.1 |
userNameThis variable contains the textual name of a user. AuthName .1.3.6.1.6.3.1135.3.3.1.2 |
userGroupNameThis variable contains the textual name of the group to
which a user belongs.rw AuthName .1.3.6.1.6.3.1135.3.3.1.3 |
userAuthChangeAn object, which when modified, causes the user's secret
authentication key to be modified via a one-way function.
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 value of userCloneFrom.rw KeyChange (V2ADMIN-MIB) .1.3.6.1.6.3.1135.3.3.1.4 |
userPrivChangeAn object, which when modified, causes the user's secret
privacy key to be modified via a one-way function.
When creating a new user, it is a '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 value of userCloneFrom.rw KeyChange (V2ADMIN-MIB) .1.3.6.1.6.3.1135.3.3.1.5 |
userNovelThis object may be used by a manager as a part of its
procedure for altering secret information about a user.
By altering the value of an instance of this object in
the same SNMPv2 Set-Request used to update secret information,
a subsequent Get-Request can determine if the Set-Request
was successful in the event that no response to the
Set-Request is received.
When an instance of this object is created, its value is
initialized to a random value.
This object need not be stored in non-volatile storage and
should be initialized to an unpredictable value upon system
re-initialization.rw OCTET STRING .1.3.6.1.6.3.1135.3.3.1.6 |
userTransportLabelThis object specifies a set of transport endpoints from which
an agent will accept management requests. If a management
request generated by this user is received on a transport
endpoint other than the transport endpoints identified
by this object, the request is deemed unauthentic.
The transports identified by this object are specified in
the transportTable. Entries in the transportTable whose
transportLabel value are equal to this object are identified.
If the value of this object has zero-length, or if the
transportTable is not implemented, then transport endpoints
are not checked when authenticating messages generated
by this user.rw TransportLabel (V2ADMIN-MIB) .1.3.6.1.6.3.1135.3.3.1.7 |
userCloneFromAn indication of the user to clone authentication and privacy
parameters from. When read, the value { 0 0 } is returned.
This object must be written exactly once, when the associated
instance of userStatus either does not exist or has the
value `notReady'. Subsequent set operations to this object
will succeed, but will not cause the agent to take any action.
When first written, the value identifies an instance of
a user, the cloning user, whose status column has the value
'active' or 'not in service'.
For implementations which support both authentication and
privacy, the authentication and privacy secrets of the cloning
user are copied to the corresponding authentication and
privacy secrets of the user being created.
For implementations which support only authentication, the
authentication secret of the cloning user is copied to the
corresponding authentication secret of the user being created.
For implementations which support neither authentication nor
privacy, this object has no effect (and need not be
implemented).rw RowPointer .1.3.6.1.6.3.1135.3.3.1.8 |
userMemoryTypeThe storage type for this conceptual row in the userNameTable.
Conceptual rows having the value 'permanent' must allow
write-access at a minimum to:
userAuthChange and userNovel for users employing
authentication; and userPrivChange and userNovel
for users employing privacy.
Note that any user which employs authentication or privacy
must allow its secrets to be updated and thus
cannot be 'readOnly'.rw MemoryType (V2ADMIN-MIB) .1.3.6.1.6.3.1135.3.3.1.9 |
userStatusThe status of this conceptual row in the userNameTable.
A user is not qualified for activation until instances of
all columns of its userNameEntry row have an appropriate
value. In particular, one or more management set operations
are required to configure the entry:
a value must be written to the user's userCloneFrom
object, and ... update of secrets
Until instances of all corresponding columns and secrets are
appropriately configured, the value of the corresponding
instance of the userStatus column is `notReady'.rw RowStatus (SNMPv2-TC) .1.3.6.1.6.3.1135.3.3.1.10 |
usecMIBConformance OBJECT IDENTIFIER .1.3.6.1.6.3.1135.4 |
usecMIBCompliances OBJECT IDENTIFIER .1.3.6.1.6.3.1135.4.1 |
usecMIBGroups OBJECT IDENTIFIER .1.3.6.1.6.3.1135.4.2 |