OID reference

usmUserCloneFrom

1.3.6.1.6.3.4.1.2.2.1.4

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.6.3.4.1.2.2.1 (usmUserEntry)
Node code: 4
Node name: usmUserCloneFrom
Category: SNMP management object
Numeric OID: 1.3.6.1.6.3.4.1.2.2.1.4
URN notation: urn:oid:1.3.6.1.6.3.4.1.2.2.1.4

ASN.1, OID-IRI and named path variants

ASN.1 notation

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

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

OID-IRI notation

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

Named path variants

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

SNMP properties

Value type: RowPointer
Maximum access defined by MIB: read-create
Status in MIB: current

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.

usmUserCloneFrom OBJECT-TYPE
    SYNTAX       RowPointer
    MAX-ACCESS   read-create
    STATUS       current
    DESCRIPTION "A pointer to another conceptual row in this
                 usmUserTable.  The user in this other conceptual
                 row is called the clone-from user.

                 When a new user is created (i.e., a new conceptual
                 row is instantiated in this table), the privacy and
                 authentication parameters of the new user are cloned
                 from its clone-from user.

                 The first time an instance of this object is set by
                 a management operation (either at or after its
                 instantiation), the cloning process is invoked.
                 Subsequent writes are successful but invoke no
                 action to be taken by the receiver.
                 The cloning process fails with an 'inconsistentName'









                 error if the conceptual row representing the
                 clone-from user is not in an active state when the
                 cloning process is invoked.

                 Cloning also causes the initial values of the secret
                 authentication key and the secret encryption key of
                 the new user to be set to the same value as the
                 corresponding secret of the clone-from user.

                 When this object is read, the ZeroDotZero OID
                 is returned.
                "
    ::= { usmUserEntry 4 }

Meaning

Descriptions

1 unique

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

A pointer to another conceptual row in this usmUserTable. The user in this other conceptual row is called the clone-from user. When a new user is created (i.e., a new conceptual row is instantiated in this table), the privacy and authentication parameters of the new user are cloned from its clone-from user. The first time an instance of this object is set by a management operation (either at or after its instantiation), the cloning process is invoked. Subsequent writes are successful but invoke no action to be taken by the receiver. The cloning process fails with an 'inconsistentName' error if the conceptual row representing the clone-from user is not in an active state when the cloning process is invoked. Cloning also causes the initial values of the secret authentication key and the secret encryption key of the new user to be set to the same value as the corresponding secret of the clone-from user. When this object is read, the ZeroDotZero OID is returned.

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

usmUserCloneFrom · currentRFC Editor1 source

Status in source: current.

Names: usmUserCloneFrom

Technical details

{
"smi_kind": "OBJECT-TYPE",
"definition": [
"usmUserCloneFrom",
"OBJECT-TYPE",
"SYNTAX",
"RowPointer",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"A pointer to another conceptual row in this usmUserTable. The user in this other conceptual row is called the clone-from user. When a new user is created (i.e., a new conceptual row is instantiated in this table), the privacy and authentication parameters of the new user are cloned from its clone-from user. The first time an instance of this object is set by a management operation (either at or after its instantiation), the cloning process is invoked. Subsequent writes are successful but invoke no action to be taken by the receiver. The cloning process fails with an 'inconsistentName' error if the conceptual row representing the clone-from user is not in an active state when the cloning process is invoked. Cloning also causes the initial values of the secret authentication key and the secret encryption key of the new user to be set to the same value as the corresponding secret of the clone-from user. When this object is read, the ZeroDotZero OID is returned. \"",
"::=",
"{",
"usmUserEntry",
"4",
"}"
],
"syntax_tree": [
[
"row",
"RowPointer"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"A pointer to another conceptual row in this usmUserTable. The user in this other conceptual row is called the clone-from user. When a new user is created (i.e., a new conceptual row is instantiated in this table), the privacy and authentication parameters of the new user are cloned from its clone-from user. The first time an instance of this object is set by a management operation (either at or after its instantiation), the cloning process is invoked. Subsequent writes are successful but invoke no action to be taken by the receiver. The cloning process fails with an 'inconsistentName' error if the conceptual row representing the clone-from user is not in an active state when the cloning process is invoked. Cloning also causes the initial values of the secret authentication key and the secret encryption key of the new user to be set to the same value as the corresponding secret of the clone-from user. When this object is read, the ZeroDotZero OID is returned."
],
null,
null,
null,
null
]
}

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.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.10	usmUserOwnPrivKeyChange	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