OID reference

usmUserOwnPrivKeyChange

1.3.6.1.6.3.4.1.2.2.1.10

Description

Behaves exactly as usmUserPrivKeyChange, with one notable difference: in order for the Set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. The idea here is that access to this column can be public, since it will only …

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.6.3.4.1.2.2.1 (usmUserEntry)
Node code: 10
Node name: usmUserOwnPrivKeyChange
Category: SNMP management object
Numeric OID: 1.3.6.1.6.3.4.1.2.2.1.10
URN notation: urn:oid:1.3.6.1.6.3.4.1.2.2.1.10

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 6 3 4 1 2 2 1 10}

{iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpUsmMIB(4) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserOwnPrivKeyChange(10)}
{iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) smnpModules(3) snmpUsmMIB(4) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserOwnPrivKeyChange(10)}
{iso(1) org(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpUsmMIB(4) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserOwnPrivKeyChange(10)}
{iso(1) org(3) dod(6) internet(1) snmpV2(6) smnpModules(3) snmpUsmMIB(4) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserOwnPrivKeyChange(10)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpUsmMIB(4) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserOwnPrivKeyChange(10)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) snmpV2(6) smnpModules(3) snmpUsmMIB(4) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserOwnPrivKeyChange(10)}
{iso(1) iso-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpUsmMIB(4) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserOwnPrivKeyChange(10)}
{iso(1) iso-organization(3) dod(6) internet(1) snmpV2(6) smnpModules(3) snmpUsmMIB(4) usmMIBObjects(1) usmUser(2) usmUserTable(2) usmUserEntry(1) usmUserOwnPrivKeyChange(10)}

OID-IRI notation

/1/3/6/1/6/3/4/1/2/2/1/10
/ISO/Identified-Organization/6/1/6/3/4/1/2/2/1/10
/ISO/3/6/1/6/3/4/1/2/2/1/10

Named path variants

/iso/identified-organization/dod/internet/snmpV2/snmpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserOwnPrivKeyChange
/iso/identified-organization/dod/internet/snmpV2/smnpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserOwnPrivKeyChange
/iso/org/dod/internet/snmpV2/snmpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserOwnPrivKeyChange
/iso/org/dod/internet/snmpV2/smnpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserOwnPrivKeyChange
/iso/iso-identified-organization/dod/internet/snmpV2/snmpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserOwnPrivKeyChange
/iso/iso-identified-organization/dod/internet/snmpV2/smnpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserOwnPrivKeyChange
/iso/iso-organization/dod/internet/snmpV2/snmpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserOwnPrivKeyChange
/iso/iso-organization/dod/internet/snmpV2/smnpModules/snmpUsmMIB/usmMIBObjects/usmUser/usmUserTable/usmUserEntry/usmUserOwnPrivKeyChange

SNMP properties

Value type: KeyChange
Maximum access defined by MIB: read-create
Status in MIB: current
Default value: ''H

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Published definition

The displayed source records contain one distinct definition. Compare its source records.

usmUserOwnPrivKeyChange OBJECT-TYPE
    SYNTAX       KeyChange  -- typically (SIZE (0..32))
    MAX-ACCESS   read-create
    STATUS       current
    DESCRIPTION "Behaves exactly as usmUserPrivKeyChange, with one
                 notable difference: in order for the Set operation
                 to succeed, the usmUserName of the operation
                 requester must match the usmUserName that indexes
                 the row which is targeted by this operation.

                 The idea here is that access to this column can be
                 public, since it will only allow a user to change
                 his own secret privacy key (privKey).
                "









    DEFVAL      { ''H }    -- the empty string
    ::= { usmUserEntry 10 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Sources for this description

RFC Editor

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1RFC Editor1 record · 1 source

Description 1

usmUserOwnPrivKeyChange · currentRFC Editor1 source

Status in source: current.

Names: usmUserOwnPrivKeyChange

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "usmUserOwnPrivKeyChange",
    "OBJECT-TYPE",
    "SYNTAX",
    "KeyChange",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Behaves exactly as usmUserPrivKeyChange, with one notable difference: in order for the Set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. The idea here is that access to this column can be public, since it will only allow a user to change his own secret privacy key (privKey). \"",
    "DEFVAL",
    "{",
    "'",
    "'",
    "H",
    "}",
    "::=",
    "{",
    "usmUserEntry",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "KeyChange"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Behaves exactly as usmUserPrivKeyChange, with one notable difference: in order for the Set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. The idea here is that access to this column can be public, since it will only allow a user to change his own secret privacy key (privKey)."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "''H"
    ]
  ]
}

RFC Editor · RFC 2264 · RFC errata · Publisher's source file: User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)

Module: SNMP-USER-BASED-SM-MIB

See published definition above

Module imports

{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TestAndIncr', 'RowStatus', 'RowPointer', 'StorageType', 'AutonomousType'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'snmpModules', 'Counter32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString', 'SnmpEngineID', 'snmpAuthProtocols', 'snmpPrivProtocols']}

· Download User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6)

US DoD

Siblings (12)

OID	Name	Direct children	Descendants	Description
1.3.6.1.6.3.4.1.2.2.1.1	usmUserEngineID	0	0
1.3.6.1.6.3.4.1.2.2.1.2	usmUserName	0	0
1.3.6.1.6.3.4.1.2.2.1.3	usmUserSecurityName	0	0
1.3.6.1.6.3.4.1.2.2.1.4	usmUserCloneFrom	0	0
1.3.6.1.6.3.4.1.2.2.1.5	usmUserAuthProtocol	0	0
1.3.6.1.6.3.4.1.2.2.1.6	usmUserAuthKeyChange	0	0
1.3.6.1.6.3.4.1.2.2.1.7	usmUserOwnAuthKeyChange	0	0
1.3.6.1.6.3.4.1.2.2.1.8	usmUserPrivProtocol	0	0
1.3.6.1.6.3.4.1.2.2.1.9	usmUserPrivKeyChange	0	0
1.3.6.1.6.3.4.1.2.2.1.11	usmUserPublic	0	0
1.3.6.1.6.3.4.1.2.2.1.12	usmUserStorageType	0	0
1.3.6.1.6.3.4.1.2.2.1.13	usmUserStatus	0	0