Reference record for OID 1.3.6.1.6.3.15.1.2.2.1.9



parent
1.3.6.1.6.3.15.1.2.2.1 (usmUserEntry)
node code
9
node name
usmUserPrivKeyChange
dot oid
1.3.6.1.6.3.15.1.2.2.1.9
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpUsmMIB(15) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserPrivKeyChange(9)}
  • {iso(1) org(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpUsmMIB(15) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserPrivKeyChange(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpUsmMIB(15) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserPrivKeyChange(9)}
  • iri oid
  • /iso/identified-organization/dod/internet/snmpV2/snmpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserPrivKeyChange
  • /iso/org/dod/internet/snmpV2/snmpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserPrivKeyChange
  • /iso/iso-identified-organization/dod/internet/snmpV2/snmpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserPrivKeyChange
  • iri by oid_info
    /ISO/Identified-Organization/6/1/6/3/15/1/2/2/1/9

    Description by circitor

    An object, which when modified, causes the secret
    encryption key 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 usmUserPrivProtocol.
    The associated secret key is the user's secret
    privacy key (privKey). 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 usmUserPrivProtocol
    is usmNoPrivProtocol, then a set is successful, but
    effectively is a no-op.

    When this object is read, the zero-length (empty)
    string is returned.
    See the description clause of usmUserAuthKeyChange for
    a recommended procedure to do a key change.

    Parsed from file SNMP-USER-BASED-SM-MIB.mib
    Module: SNMP-USER-BASED-SM-MIB

    Description by cisco_v1

    An object, which when modified, causes the secret
    encryption key 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 usmUserPrivProtocol.
    The associated secret key is the user's secret
    privacy key (privKey). 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 usmUserPrivProtocol
    is usmNoPrivProtocol, then a set is successful, but
    effectively is a no-op.

    When this object is read, the zero-length (empty)
    string is returned.
    See the description clause of usmUserAuthKeyChange for
    a recommended procedure to do a key change.

    Description by oid_info

    usmUserPrivKeyChange OBJECT-TYPE
    SYNTAX KeyChange -- typically (SIZE (0 | 32)) for DES
    MAX-ACCESS read-create
    STATUS current
    DESCRIPTION "An object, which when modified, causes the secret
    encryption key 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 usmUserPrivProtocol.
    The associated secret key is the users secret
    privacy key (privKey). The associated hash
    algorithm is the algorithm used by the users
    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 usmUserPrivProtocol
    is usmNoPrivProtocol, then a set is successful, but
    effectively is a no-op.
    When this object is read, the zero-length (empty)
    string is returned.
    See the description clause of usmUserAuthKeyChange for
    a recommended procedure to do a key change.
    "
    DEFVAL { H } -- the empty string

    View at oid-info.com

    Description by mibdepot

    An object, which when modified, causes the secret
    encryption key 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 usmUserPrivProtocol.
    The associated secret key is the user's secret
    privacy key (privKey). 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 usmUserPrivProtocol
    is usmNoPrivProtocol, then a set is successful, but
    effectively is a no-op.

    When this object is read, the zero-length (empty)
    string is returned.
    See the description clause of usmUserAuthKeyChange for
    a recommended procedure to do a key change.

    Parsed from file rfc3414.mib.txt
    Company: None
    Module: SNMP-USER-BASED-SM-MIB

    Description by cisco

    An object, which when modified, causes the secret
    encryption key 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 usmUserPrivProtocol.
    The associated secret key is the user's secret
    privacy key (privKey). 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 usmUserPrivProtocol
    is usmNoPrivProtocol, then a set is successful, but
    effectively is a no-op.

    When this object is read, the zero-length (empty)
    string is returned.
    See the description clause of usmUserAuthKeyChange for
    a recommended procedure to do a key change.

    Information by circitor

    usmUserPrivKeyChange OBJECT-TYPE SYNTAX KeyChange MAX-ACCESS read-create STATUS current DESCRIPTION "An object, which when modified, causes the secret encryption key 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 usmUserPrivProtocol. The associated secret key is the user's secret privacy key (privKey). 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 usmUserPrivProtocol is usmNoPrivProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. See the description clause of usmUserAuthKeyChange for a recommended procedure to do a key change. " DEFVAL { ''H } ::= { usmUserEntry 9 }

    Information by cisco_v1

    usmUserPrivKeyChange OBJECT-TYPE SYNTAX KeyChange ACCESS read-write STATUS mandatory DESCRIPTION "An object, which when modified, causes the secret encryption key 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 usmUserPrivProtocol. The associated secret key is the user's secret privacy key (privKey). 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 usmUserPrivProtocol is usmNoPrivProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. See the description clause of usmUserAuthKeyChange for a recommended procedure to do a key change." DEFVAL { ''H } ::= { usmUserEntry 9 }

    Information by oid_info

    Automatically extracted from RFC3414

    Information by mibdepot

    usmUserPrivKeyChange OBJECT-TYPE SYNTAX KeyChange MAX-ACCESS read-create STATUS current DESCRIPTION "An object, which when modified, causes the secret encryption key 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 usmUserPrivProtocol. The associated secret key is the user's secret privacy key (privKey). 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 usmUserPrivProtocol is usmNoPrivProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. See the description clause of usmUserAuthKeyChange for a recommended procedure to do a key change. " DEFVAL { ''H } ::= { usmUserEntry 9 }

    Information by cisco

    usmUserPrivKeyChange OBJECT-TYPE SYNTAX KeyChange MAX-ACCESS read-create STATUS current DESCRIPTION "An object, which when modified, causes the secret encryption key 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 usmUserPrivProtocol. The associated secret key is the user's secret privacy key (privKey). 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 usmUserPrivProtocol is usmNoPrivProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. See the description clause of usmUserAuthKeyChange for a recommended procedure to do a key change. " DEFVAL { ''H } ::= { usmUserEntry 9 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6)

    US DoD

    Brothers (12)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.6.3.15.1.2.2.1.1 usmUserEngineID 0 0 An SNMP engine's administratively-unique identifier.

    In a simple agent, this value is always that agent's
    own snmpEngineID value.…
    1.3.6.1.6.3.15.1.2.2.1.2 usmUserName 0 0 A human readable string representing the name of
    the user.

    This is the (User-based Security) Model dependent
    security ID.
    1.3.6.1.6.3.15.1.2.2.1.3 usmUserSecurityName 0 0 A human readable string representing the user in
    Security Model independent format.

    The default transformation of the User-based …
    1.3.6.1.6.3.15.1.2.2.1.4 usmUserCloneFrom 0 0 A pointer to another conceptual row in this
    usmUserTable. The user in this other conceptual
    row is called the clone-from user.

    Wh…
    1.3.6.1.6.3.15.1.2.2.1.5 usmUserAuthProtocol 0 0 An indication of whether messages sent on behalf of
    this user to/from the SNMP engine identified by
    usmUserEngineID, can be authe…
    1.3.6.1.6.3.15.1.2.2.1.6 usmUserAuthKeyChange 0 0 An object, which when modified, causes the secret
    authentication key used for messages sent on behalf
    of this user to/from the SN…
    1.3.6.1.6.3.15.1.2.2.1.7 usmUserOwnAuthKeyChange 0 0 Behaves exactly as usmUserAuthKeyChange, with one
    notable difference: in order for the set operation
    to succeed, the usmUserName …
    1.3.6.1.6.3.15.1.2.2.1.8 usmUserPrivProtocol 0 0 An indication of whether messages sent on behalf of
    this user to/from the SNMP engine identified by
    usmUserEngineID, can be prote…
    1.3.6.1.6.3.15.1.2.2.1.10 usmUserOwnPrivKeyChange 0 0 Behaves exactly as usmUserPrivKeyChange, with one
    notable difference: in order for the Set operation
    to succeed, the usmUserName …
    1.3.6.1.6.3.15.1.2.2.1.11 usmUserPublic 0 0 A publicly-readable value which can be written as part
    of the procedure for changing a user's secret
    authentication and/or privac…
    1.3.6.1.6.3.15.1.2.2.1.12 usmUserStorageType 0 0 The storage type for this conceptual row.

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

    - …
    1.3.6.1.6.3.15.1.2.2.1.13 usmUserStatus 0 0 The status of this conceptual row.

    Until instances of all corresponding columns are
    appropriately configured, the value of the
    cor…