OID reference

bosUsmUserCloneFrom

1.3.6.1.4.1.1411.102.102.11.1.1.1.4

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 must be cloned from its clone-from user. These …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1411.102.102.11.1.1.1 (bosUsmUserEntry)
Node code
4
Node name
bosUsmUserCloneFrom
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1411.102.102.11.1.1.1.4
URN notation
urn:oid:1.3.6.1.4.1.1411.102.102.11.1.1.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1411 102 102 11 1 1 1 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) funk(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) juniper(1411) ex2500(102) ex2500addon(102) snmpv3(11) bosUsmUser(1) bosUsmUserTable(1) bosUsmUserEntry(1) bosUsmUserCloneFrom(4)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1411/102/102/11/1/1/1/4
  • /ISO/Identified-Organization/6/1/4/1/1411/102/102/11/1/1/1/4
  • /ISO/3/6/1/4/1/1411/102/102/11/1/1/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/identified-organization/dod/internet/private/enterprise/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/identified-organization/dod/internet/private/enterprises/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/identified-organization/dod/internet/private/enterprises/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/identified-organization/dod/internet/private/vendor-objects/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/identified-organization/dod/internet/private/vendor-objects/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/org/dod/internet/private/enterprise/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/org/dod/internet/private/enterprise/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/org/dod/internet/private/enterprises/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/org/dod/internet/private/enterprises/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/org/dod/internet/private/ldap-enterprise/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/org/dod/internet/private/ldap-enterprise/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/org/dod/internet/private/vendor-objects/funk/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • /iso/org/dod/internet/private/vendor-objects/juniper/ex2500/ex2500addon/snmpv3/bosUsmUser/bosUsmUserTable/bosUsmUserEntry/bosUsmUserCloneFrom
  • Additional combinations skipped.

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.

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

bosUsmUserCloneFrom 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 must be
                 cloned from its clone-from user. These parameters are:
                   - authentication protocol (usmUserAuthProtocol)
                   - privacy protocol (usmUserPrivProtocol)
                 They will be copied regardless of what the current
                 value is.

                 Cloning also causes the initial values of the secret
                 authentication key (authKey) and the secret encryption

                 key (privKey) of the new user to be set to the same
                 values as the corresponding secrets of the clone-from
                 user to allow the KeyChange process to occur as
                 required during user creation.

                 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 does not exist or is not in an active
                 state when the cloning process is invoked.

                 When this object is read, the ZeroDotZero OID
                 is returned.
                "
    ::= { bosUsmUserEntry 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 must be cloned from its clone-from user. These parameters are: - authentication protocol (usmUserAuthProtocol) - privacy protocol (usmUserPrivProtocol) They will be copied regardless of what the current value is. Cloning also causes the initial values of the secret authentication key (authKey) and the secret encryption key (privKey) of the new user to be set to the same values as the corresponding secrets of the clone-from user to allow the KeyChange process to occur as required during user creation. 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 does not exist or is not in an active state when the cloning process is invoked. When this object is read, the ZeroDotZero OID is returned.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

bosUsmUserCloneFrom · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: bosUsmUserCloneFrom

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bosUsmUserCloneFrom",
    "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 must be cloned from its clone-from user. These parameters are: - authentication protocol (usmUserAuthProtocol) - privacy protocol (usmUserPrivProtocol) They will be copied regardless of what the current value is. Cloning also causes the initial values of the secret authentication key (authKey) and the secret encryption key (privKey) of the new user to be set to the same values as the corresponding secrets of the clone-from user to allow the KeyChange process to occur as required during user creation. 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 does not exist or is not in an active state when the cloning process is invoked. When this object is read, the ZeroDotZero OID is returned. \"",
    "::=",
    "{",
    "bosUsmUserEntry",
    "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 must be cloned from its clone-from user. These parameters are: - authentication protocol (usmUserAuthProtocol) - privacy protocol (usmUserPrivProtocol) They will be copied regardless of what the current value is. Cloning also causes the initial values of the secret authentication key (authKey) and the secret encryption key (privKey) of the new user to be set to the same values as the corresponding secrets of the clone-from user to allow the KeyChange process to occur as required during user creation. 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 does not exist or is not in an active state when the cloning process is invoked. When this object is read, the ZeroDotZero OID is returned."
    ],
    null,
    null,
    null,
    null
  ]
}
  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive.

    Module: EX2500-BASE-MIB

    See published definition above

    Module imports
    {'IF-MIB': ['ifIndex', 'InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'DisplayString', 'PhysAddress', 'MacAddress', 'RowStatus', 'TimeInterval', 'TimeStamp'], 'BRIDGE-MIB': ['BridgeId', 'dot1dTp', 'dot1dTpPort', 'dot1dBridge', 'dot1dBasePortEntry', 'dot1dBasePort'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'enterprises', 'Integer32', 'Unsigned32', 'Counter32', 'Gauge32', 'Counter64', 'TimeTicks', 'IpAddress', 'mib-2'], 'RFC1213-MIB': ['sysName', 'sysLocation', 'sysContact', 'ifIndex'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'P-BRIDGE-MIB': ['EnabledStatus'], 'Q-BRIDGE-MIB': ['PortList'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString', 'SnmpEngineID', 'SnmpMessageProcessingModel', 'SnmpSecurityModel', 'SnmpSecurityLevel'], 'SNMP-USER-BASED-SM-MIB': ['usmNoAuthProtocol', 'usmNoPrivProtocol']}
    · Download EX2500-BASE-MIB

    Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1411)

Walsh Kevin

Siblings (12)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1411.102.102.11.1.1.1.1 bosUsmUserTableIndex00
1.3.6.1.4.1.1411.102.102.11.1.1.1.2 bosUsmUserName00
1.3.6.1.4.1.1411.102.102.11.1.1.1.3 bosUsmUserSecurityName00
1.3.6.1.4.1.1411.102.102.11.1.1.1.5 bosUsmUserAuthProtocol00
1.3.6.1.4.1.1411.102.102.11.1.1.1.6 bosUsmUserAuthKeyChange00
1.3.6.1.4.1.1411.102.102.11.1.1.1.7 bosUsmUserOwnAuthKeyChange00
1.3.6.1.4.1.1411.102.102.11.1.1.1.8 bosUsmUserPrivProtocol00
1.3.6.1.4.1.1411.102.102.11.1.1.1.9 bosUsmUserPrivKeyChange00
1.3.6.1.4.1.1411.102.102.11.1.1.1.10 bosUsmUserOwnPrivKeyChange00
1.3.6.1.4.1.1411.102.102.11.1.1.1.11 bosUsmUserPublic00
1.3.6.1.4.1.1411.102.102.11.1.1.1.12 bosUsmUserStorageType00
1.3.6.1.4.1.1411.102.102.11.1.1.1.13 bosUsmUserStatus00