OID reference

lcsSNMPv3UserConfEngineID

1.3.6.1.4.1.2356.14.1.6.6.1.2

Description

An octet string identifying the engine ID that this entry should belong to. The string must contain an even number(in hexadecimal format) with number of digits between 10 and 64, but all-zeros and all-'F's are not allowed. The SNMPv3 architecture uses the User-based Security Model (USM) for message security and the Vi…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2356.14.1.6.6.1 (lcsSNMPv3UserConfEntry)
Node code
2
Node name
lcsSNMPv3UserConfEngineID
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2356.14.1.6.6.1.2
URN notation
urn:oid:1.3.6.1.4.1.2356.14.1.6.6.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2356 14 1 6 6 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) elsa(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) lancomSystems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) elsa(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) lancomSystems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) elsa(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) lancomSystems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) elsa(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) lancomSystems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) elsa(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) lancomSystems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) lancom-systems(2356) lcosSX(14) lcsSystem(1) lcsSnmp(6) lcsSNMPv3UserConfTable(6) lcsSNMPv3UserConfEntry(1) lcsSNMPv3UserConfEngineID(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2356/14/1/6/6/1/2
  • /ISO/Identified-Organization/6/1/4/1/2356/14/1/6/6/1/2
  • /ISO/3/6/1/4/1/2356/14/1/6/6/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/ELSA/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/enterprise/lancom-systems/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/enterprise/elsa/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/enterprise/lancomSystems/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/enterprises/ELSA/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/enterprises/lancom-systems/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/enterprises/elsa/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/enterprises/lancomSystems/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ELSA/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lancom-systems/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/elsa/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/lancomSystems/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/vendor-objects/ELSA/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/vendor-objects/lancom-systems/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/vendor-objects/elsa/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • /iso/identified-organization/dod/internet/private/vendor-objects/lancomSystems/lcosSX/lcsSystem/lcsSnmp/lcsSNMPv3UserConfTable/lcsSNMPv3UserConfEntry/lcsSNMPv3UserConfEngineID
  • Additional combinations skipped.

SNMP properties

Value type
DisplayString
Maximum access defined by MIB
read-write
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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

lcsSNMPv3UserConfEngineID · current

lcsSNMPv3UserConfEngineID OBJECT-TYPE
   SYNTAX       DisplayString
   MAX-ACCESS   read-write
   STATUS       current
   DESCRIPTION
       "An octet string identifying the engine ID that this entry should belong to.
       The string must contain an even number(in hexadecimal format) with
       number of digits between 10 and 64, but all-zeros and all-'F's are not allowed.
       The SNMPv3 architecture uses the User-based Security Model (USM)
       for message security and the View-based Access Control Model (VACM) for access control.
       For the USM entry, the usmUserEngineID and usmUserName are the entry's keys.
       In a simple agent, usmUserEngineID is always that agent's own snmpEngineID value.
       The value can also take the value of the snmpEngineID of a remote SNMP engine with
       which this user can communicate. In other words, if user engine ID equal system engine ID
       then it is local user; otherwise it's remote user. "
   ::= { lcsSNMPv3UserConfEntry 2 }

lcsSNMPv3UserConfEngineID · current

lcsSNMPv3UserConfEngineID OBJECT-TYPE
   SYNTAX       DisplayString
   MAX-ACCESS   read-write
   STATUS       current
   DESCRIPTION
       "An octet string identifying the engine ID that this entry should belong to.
       The string must contain an even number(in hexadecimal format) with
       number of digits between 10 and 64, but all-zeros and all-'F's are not allowed.
       The SNMPv3 architecture uses the User-based Security Model (USM)
       for message security and the View-based Access Control Model (VACM) for access control.
       For the USM entry, the usmUserEngineID and usmUserName are the entry's keys.
       In a simple agent, usmUserEngineID is always that agent's own snmpEngineID value.
       The value can also take the value of the snmpEngineID of a remote SNMP engine with
       which this user can communicate. In other words, if user engine ID equal system engine ID
       then it is local user; otherwise it's remote user. You may write the special value
       'system' to copy the snmp engine id of the local system at the time of writing."
   ::= { lcsSNMPv3UserConfEntry 2 }

Meaning

Descriptions

2 unique

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

Description 1

An octet string identifying the engine ID that this entry should belong to. The string must contain an even number(in hexadecimal format) with number of digits between 10 and 64, but all-zeros and all-'F's are not allowed. The SNMPv3 architecture uses the User-based Security Model (USM) for message security and the View-based Access Control Model (VACM) for access control. For the USM entry, the usmUserEngineID and usmUserName are the entry's keys. In a simple agent, usmUserEngineID is always that agent's own snmpEngineID value. The value can also take the value of the snmpEngineID of a remote SNMP engine with which this user can communicate. In other words, if user engine ID equal system engine ID then it is local user; otherwise it's remote user.

Sources for this description

LANCOM official release MIBsLANCOM MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Description 2

An octet string identifying the engine ID that this entry should belong to. The string must contain an even number(in hexadecimal format) with number of digits between 10 and 64, but all-zeros and all-'F's are not allowed. The SNMPv3 architecture uses the User-based Security Model (USM) for message security and the View-based Access Control Model (VACM) for access control. For the USM entry, the usmUserEngineID and usmUserName are the entry's keys. In a simple agent, usmUserEngineID is always that agent's own snmpEngineID value. The value can also take the value of the snmpEngineID of a remote SNMP engine with which this user can communicate. In other words, if user engine ID equal system engine ID then it is local user; otherwise it's remote user. You may write the special value 'system' to copy the snmp engine id of the local system at the time of writing.

Sources for this description

LANCOM official release MIBs

See 1 matching source record

Evidence

Source records

2 records

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

Records for description 1LANCOM official release MIBs, LANCOM MIB copies (LibreNMS/Observium Community)1 record · 18 sources

Description 1

lcsSNMPv3UserConfEngineID · currentLANCOM official release MIBs, LANCOM MIB copies (LibreNMS/Observium Community)18 sources

Status in source: current.

Names: lcsSNMPv3UserConfEngineID

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "lcsSNMPv3UserConfEngineID",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"An octet string identifying the engine ID that this entry should belong to. The string must contain an even number(in hexadecimal format) with number of digits between 10 and 64, but all-zeros and all-'F's are not allowed. The SNMPv3 architecture uses the User-based Security Model (USM) for message security and the View-based Access Control Model (VACM) for access control. For the USM entry, the usmUserEngineID and usmUserName are the entry's keys. In a simple agent, usmUserEngineID is always that agent's own snmpEngineID value. The value can also take the value of the snmpEngineID of a remote SNMP engine with which this user can communicate. In other words, if user engine ID equal system engine ID then it is local user; otherwise it's remote user. \"",
    "::=",
    "{",
    "lcsSNMPv3UserConfEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "DisplayString"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "An octet string identifying the engine ID that this entry should belong to. The string must contain an even number(in hexadecimal format) with number of digits between 10 and 64, but all-zeros and all-'F's are not allowed. The SNMPv3 architecture uses the User-based Security Model (USM) for message security and the View-based Access Control Model (VACM) for access control. For the USM entry, the usmUserEngineID and usmUserName are the entry's keys. In a simple agent, usmUserEngineID is always that agent's own snmpEngineID value. The value can also take the value of the snmpEngineID of a remote SNMP engine with which this user can communicate. In other words, if user engine ID equal system engine ID then it is local user; otherwise it's remote user."
    ],
    null,
    null,
    null,
    null
  ]
}

Browse all 18 supporting sources

Records for description 2LANCOM official release MIBs1 record · 5 sources

Description 2

lcsSNMPv3UserConfEngineID · currentLANCOM official release MIBs5 sources

Status in source: current.

Names: lcsSNMPv3UserConfEngineID

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "lcsSNMPv3UserConfEngineID",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"An octet string identifying the engine ID that this entry should belong to. The string must contain an even number(in hexadecimal format) with number of digits between 10 and 64, but all-zeros and all-'F's are not allowed. The SNMPv3 architecture uses the User-based Security Model (USM) for message security and the View-based Access Control Model (VACM) for access control. For the USM entry, the usmUserEngineID and usmUserName are the entry's keys. In a simple agent, usmUserEngineID is always that agent's own snmpEngineID value. The value can also take the value of the snmpEngineID of a remote SNMP engine with which this user can communicate. In other words, if user engine ID equal system engine ID then it is local user; otherwise it's remote user. You may write the special value 'system' to copy the snmp engine id of the local system at the time of writing.\"",
    "::=",
    "{",
    "lcsSNMPv3UserConfEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "DisplayString"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "An octet string identifying the engine ID that this entry should belong to. The string must contain an even number(in hexadecimal format) with number of digits between 10 and 64, but all-zeros and all-'F's are not allowed. The SNMPv3 architecture uses the User-based Security Model (USM) for message security and the View-based Access Control Model (VACM) for access control. For the USM entry, the usmUserEngineID and usmUserName are the entry's keys. In a simple agent, usmUserEngineID is always that agent's own snmpEngineID value. The value can also take the value of the snmpEngineID of a remote SNMP engine with which this user can communicate. In other words, if user engine ID equal system engine ID then it is local user; otherwise it's remote user. You may write the special value 'system' to copy the snmp engine id of the local system at the time of writing."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2356)

Udo Brocker

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2356.14.1.6.6.1.1 lcsSNMPv3UserConfIndex00
1.3.6.1.4.1.2356.14.1.6.6.1.3 lcsSNMPv3UserConfUserName00
1.3.6.1.4.1.2356.14.1.6.6.1.4 lcsSNMPv3UserConfSecurityLevel00
1.3.6.1.4.1.2356.14.1.6.6.1.5 lcsSNMPv3UserConfAuthenticationProtocol00
1.3.6.1.4.1.2356.14.1.6.6.1.6 lcsSNMPv3UserConfAuthenticationPassword00
1.3.6.1.4.1.2356.14.1.6.6.1.7 lcsSNMPv3UserConfPrivacyProtocol00
1.3.6.1.4.1.2356.14.1.6.6.1.8 lcsSNMPv3UserConfPrivacyPassword00
1.3.6.1.4.1.2356.14.1.6.6.1.9 lcsSNMPv3UserConfRowStatus00
1.3.6.1.4.1.2356.14.1.6.6.1.150 lcsSNMPv3UserConfAuthenticationPasswordClearText00
1.3.6.1.4.1.2356.14.1.6.6.1.151 lcsSNMPv3UserConfAuthenticationPasswordEncrypted00
1.3.6.1.4.1.2356.14.1.6.6.1.152 lcsSNMPv3UserConfPrivacyPasswordClearText00
1.3.6.1.4.1.2356.14.1.6.6.1.153 lcsSNMPv3UserConfPrivacyPasswordEncrypted00
1.3.6.1.4.1.2356.14.1.6.6.1.154 lcsSNMPv3UserConfAuthenticationPasswordNonLocalized00
1.3.6.1.4.1.2356.14.1.6.6.1.155 lcsSNMPv3UserConfPrivacyPasswordNonLocalized00