OID reference

bosUsmUserTable

1.3.6.1.4.1.1411.102.102.11.1.1

Description

The table of users configured in the SNMP engine's Local Configuration Datastore (LCD). To create a new user (i.e., to instantiate a new conceptual row in this table), it is recommended to follow this procedure: 1) GET(usmUserSpinLock.0) and save in sValue. 2) SET(usmUserSpinLock.0=sValue, usmUserCloneFrom=templateUse…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1411.102.102.11.1 (bosUsmUser)
Node code
1
Node name
bosUsmUserTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1411.102.102.11.1.1
URN notation
urn:oid:1.3.6.1.4.1.1411.102.102.11.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
SEQUENCE OF BosUsmUserEntry
Maximum access defined by MIB
not-accessible
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.

bosUsmUserTable     OBJECT-TYPE
    SYNTAX       SEQUENCE OF BosUsmUserEntry
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION "The table of users configured in the SNMP engine's
                 Local Configuration Datastore (LCD).

                 To create a new user (i.e., to instantiate a new
                 conceptual row in this table), it is recommended to
                 follow this procedure:

                   1)  GET(usmUserSpinLock.0) and save in sValue.

                   2)  SET(usmUserSpinLock.0=sValue,
                           usmUserCloneFrom=templateUser,
                           usmUserStatus=createAndWait)
                       You should use a template user to clone from
                       which has the proper auth/priv protocol defined.

                 If the new user is to use privacy:

                   3)  generate the keyChange value based on the secret
                       privKey of the clone-from user and the secret key
                       to be used for the new user. Let us call this
                       pkcValue.
                   4)  GET(usmUserSpinLock.0) and save in sValue.
                   5)  SET(usmUserSpinLock.0=sValue,
                           usmUserPrivKeyChange=pkcValue
                           usmUserPublic=randomValue1)
                   6)  GET(usmUserPulic) and check it has randomValue1.
                       If not, repeat steps 4-6.

                 If the new user will never use privacy:

                   7)  SET(usmUserPrivProtocol=usmNoPrivProtocol)

                 If the new user is to use authentication:

                   8)  generate the keyChange value based on the secret
                       authKey of the clone-from user and the secret key
                       to be used for the new user. Let us call this
                       akcValue.
                   9)  GET(usmUserSpinLock.0) and save in sValue.
                   10) SET(usmUserSpinLock.0=sValue,
                           usmUserAuthKeyChange=akcValue
                           usmUserPublic=randomValue2)
                   11) GET(usmUserPulic) and check it has randomValue2.
                       If not, repeat steps 9-11.

                 If the new user will never use authentication:

                   12) SET(usmUserAuthProtocol=usmNoAuthProtocol)

                 Finally, activate the new user:

                   13) SET(usmUserStatus=active)

                 The new user should now be available and ready to be
                 used for SNMPv3 communication. Note however that access
                 to MIB data must be provided via configuration of the
                 SNMP-VIEW-BASED-ACM-MIB.

                 The use of usmUserSpinlock is to avoid conflicts with
                 another SNMP command generator application which may
                 also be acting on the usmUserTable.
                "
    ::= { bosUsmUser 1 }

Meaning

Descriptions

1 unique

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

The table of users configured in the SNMP engine's Local Configuration Datastore (LCD). To create a new user (i.e., to instantiate a new conceptual row in this table), it is recommended to follow this procedure: 1) GET(usmUserSpinLock.0) and save in sValue. 2) SET(usmUserSpinLock.0=sValue, usmUserCloneFrom=templateUser, usmUserStatus=createAndWait) You should use a template user to clone from which has the proper auth/priv protocol defined. If the new user is to use privacy: 3) generate the keyChange value based on the secret privKey of the clone-from user and the secret key to be used for the new user. Let us call this pkcValue. 4) GET(usmUserSpinLock.0) and save in sValue. 5) SET(usmUserSpinLock.0=sValue, usmUserPrivKeyChange=pkcValue usmUserPublic=randomValue1) 6) GET(usmUserPulic) and check it has randomValue1. If not, repeat steps 4-6. If the new user will never use privacy: 7) SET(usmUserPrivProtocol=usmNoPrivProtocol) If the new user is to use authentication: 8) generate the keyChange value based on the secret authKey of the clone-from user and the secret key to be used for the new user. Let us call this akcValue. 9) GET(usmUserSpinLock.0) and save in sValue. 10) SET(usmUserSpinLock.0=sValue, usmUserAuthKeyChange=akcValue usmUserPublic=randomValue2) 11) GET(usmUserPulic) and check it has randomValue2. If not, repeat steps 9-11. If the new user will never use authentication: 12) SET(usmUserAuthProtocol=usmNoAuthProtocol) Finally, activate the new user: 13) SET(usmUserStatus=active) The new user should now be available and ready to be used for SNMPv3 communication. Note however that access to MIB data must be provided via configuration of the SNMP-VIEW-BASED-ACM-MIB. The use of usmUserSpinlock is to avoid conflicts with another SNMP command generator application which may also be acting on the usmUserTable.

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

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

Status in source: current.

Names: bosUsmUserTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bosUsmUserTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "BosUsmUserEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The table of users configured in the SNMP engine's Local Configuration Datastore (LCD). To create a new user (i.e., to instantiate a new conceptual row in this table), it is recommended to follow this procedure: 1) GET(usmUserSpinLock.0) and save in sValue. 2) SET(usmUserSpinLock.0=sValue, usmUserCloneFrom=templateUser, usmUserStatus=createAndWait) You should use a template user to clone from which has the proper auth/priv protocol defined. If the new user is to use privacy: 3) generate the keyChange value based on the secret privKey of the clone-from user and the secret key to be used for the new user. Let us call this pkcValue. 4) GET(usmUserSpinLock.0) and save in sValue. 5) SET(usmUserSpinLock.0=sValue, usmUserPrivKeyChange=pkcValue usmUserPublic=randomValue1) 6) GET(usmUserPulic) and check it has randomValue1. If not, repeat steps 4-6. If the new user will never use privacy: 7) SET(usmUserPrivProtocol=usmNoPrivProtocol) If the new user is to use authentication: 8) generate the keyChange value based on the secret authKey of the clone-from user and the secret key to be used for the new user. Let us call this akcValue. 9) GET(usmUserSpinLock.0) and save in sValue. 10) SET(usmUserSpinLock.0=sValue, usmUserAuthKeyChange=akcValue usmUserPublic=randomValue2) 11) GET(usmUserPulic) and check it has randomValue2. If not, repeat steps 9-11. If the new user will never use authentication: 12) SET(usmUserAuthProtocol=usmNoAuthProtocol) Finally, activate the new user: 13) SET(usmUserStatus=active) The new user should now be available and ready to be used for SNMPv3 communication. Note however that access to MIB data must be provided via configuration of the SNMP-VIEW-BASED-ACM-MIB. The use of usmUserSpinlock is to avoid conflicts with another SNMP command generator application which may also be acting on the usmUserTable. \"",
    "::=",
    "{",
    "bosUsmUser",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "BosUsmUserEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The table of users configured in the SNMP engine's Local Configuration Datastore (LCD). To create a new user (i.e., to instantiate a new conceptual row in this table), it is recommended to follow this procedure: 1) GET(usmUserSpinLock.0) and save in sValue. 2) SET(usmUserSpinLock.0=sValue, usmUserCloneFrom=templateUser, usmUserStatus=createAndWait) You should use a template user to clone from which has the proper auth/priv protocol defined. If the new user is to use privacy: 3) generate the keyChange value based on the secret privKey of the clone-from user and the secret key to be used for the new user. Let us call this pkcValue. 4) GET(usmUserSpinLock.0) and save in sValue. 5) SET(usmUserSpinLock.0=sValue, usmUserPrivKeyChange=pkcValue usmUserPublic=randomValue1) 6) GET(usmUserPulic) and check it has randomValue1. If not, repeat steps 4-6. If the new user will never use privacy: 7) SET(usmUserPrivProtocol=usmNoPrivProtocol) If the new user is to use authentication: 8) generate the keyChange value based on the secret authKey of the clone-from user and the secret key to be used for the new user. Let us call this akcValue. 9) GET(usmUserSpinLock.0) and save in sValue. 10) SET(usmUserSpinLock.0=sValue, usmUserAuthKeyChange=akcValue usmUserPublic=randomValue2) 11) GET(usmUserPulic) and check it has randomValue2. If not, repeat steps 9-11. If the new user will never use authentication: 12) SET(usmUserAuthProtocol=usmNoAuthProtocol) Finally, activate the new user: 13) SET(usmUserStatus=active) The new user should now be available and ready to be used for SNMPv3 communication. Note however that access to MIB data must be provided via configuration of the SNMP-VIEW-BASED-ACM-MIB. The use of usmUserSpinlock is to avoid conflicts with another SNMP command generator application which may also be acting on the usmUserTable."
    ],
    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

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1411.102.102.11.1.1.1 bosUsmUserEntry1313