OID reference

ldapUserSearchBaseDN

1.3.6.1.4.1.2.3.51.2.4.9.3.6.8

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.2.3.51.2.4.9.3.6 (ldapClientCfg)
Node code: 8
Node name: ldapUserSearchBaseDN
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.2.3.51.2.4.9.3.6.8
URN notation: urn:oid:1.3.6.1.4.1.2.3.51.2.4.9.3.6.8
Type: OBJECT-TYPE

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 2 3 51 2 4 9 3 6 8}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) configureSP(4) networkConfiguration(9) tcpProtocols(3) ldapClientCfg(6) ldapUserSearchBaseDN(8)}
Additional combinations skipped.

OID-IRI notation

/1/3/6/1/4/1/2/3/51/2/4/9/3/6/8
/ISO/Identified-Organization/6/1/4/1/2/3/51/2/4/9/3/6/8
/ISO/3/6/1/4/1/2/3/51/2/4/9/3/6/8

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/enterprises/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/enterprises/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/enterprises/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/ldap-enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/ldap-enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/ldap-enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/vendor-objects/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/vendor-objects/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/identified-organization/dod/internet/private/vendor-objects/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/org/dod/internet/private/enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/org/dod/internet/private/enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/org/dod/internet/private/enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
/iso/org/dod/internet/private/enterprises/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/configureSP/networkConfiguration/tcpProtocols/ldapClientCfg/ldapUserSearchBaseDN
Additional combinations skipped.

SNMP properties

Value type: OCTET STRING
Maximum access defined by MIB: read-write
Status in MIB: deprecated, mandatory

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — IBM MIB copies (LibreNMS/Observium Community)

Value type: OCTET STRING
Maximum access defined by MIB: read-write
Status in MIB: deprecated
Allowed size (octets): 0–255

Variant 2 — Circitor

Value type: OCTET STRING
Maximum access defined by MIB: read-write
Status in MIB: mandatory
Allowed size (octets): 0–64

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.2.3.51.2.4.9.3.6.8.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

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.

ldapUserSearchBaseDN OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255))
ACCESS read-write
STATUS deprecated
DESCRIPTION
"As part of the user authentication process, it is necessary to search
the LDAP server for one or more attributes associated with a particular
user. Any search request must specify the base DN for the actual search.
This field specifies the base DN which should be used to search the User
directory. This is a NULL terminated 255 byte string.
An example might look like cn=users,dn=foobar,dn=com. If this
field is left blank, the Root DN will be used as the search base instead.
As mentioned, user searches are part of the authentication process. They
are carried out to retrieve information about the user such as login
permissions, callback number, and group memberships. For Version 2.0 LDAP
clients, it is strongly encouraged that this parameter be configured,
otherwise a search using the root DN may not succeed (as seen on Active
Directory servers).

NOTE: This MIB object is for MM only.
NOTE: This Mib object is deprecated and no longer supported."
::= { ldapClientCfg 8 }

Meaning

Descriptions

2 unique

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

Description 1

As part of the user authentication process, it is necessary to search
the LDAP server for one or more attributes associated with a particular
user. Any search request must specify the base DN for the actual search.
This field specifies the base DN which should be used to search the User
directory. An example might look like cn=users,dn=foobar,dn=com. If this
field is left blank, the Root DN will be used as the search base instead.
As mentioned, user searches are part of the authentication process. They
are carried out to retrieve information about the user such as login
permissions, callback number, and group memberships. For Version 2.0 LDAP
clients, it is strongly encouraged that this parameter be configured,
otherwise a search using the root DN may not succeed (as seen on Active
Directory servers).

Sources for this description

Circitor

Parsed from BLADE-MIB.mib · BLADE-MIB

Source file: Download BLADE-MIB — archive MIB indexed for IBM (https://w3.ibm.com/standards ) · Publisher's file IBM (https://w3.ibm.com/standards ) archived MIB undated archived revision

Vendor MIB copy from the MibBrowser.online archive. IBM (https://w3.ibm.com/standards ) support.

Related source files and packages:

Source file: Download BLADE-MIB.mib

Browse all files from Circitor

Description 2

As part of the user authentication process, it is necessary to search the LDAP server for one or more attributes associated with a particular user. Any search request must specify the base DN for the actual search. This field specifies the base DN which should be used to search the User directory. This is a NULL terminated 255 byte string. An example might look like cn=users,dn=foobar,dn=com. If this field is left blank, the Root DN will be used as the search base instead. As mentioned, user searches are part of the authentication process. They are carried out to retrieve information about the user such as login permissions, callback number, and group memberships. For Version 2.0 LDAP clients, it is strongly encouraged that this parameter be configured, otherwise a search using the root DN may not succeed (as seen on Active Directory servers). NOTE: This MIB object is for MM only. NOTE: This Mib object is deprecated and no longer supported.

Sources for this description

IBM 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 2IBM MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

ldapUserSearchBaseDN · deprecatedIBM MIB copies (LibreNMS/Observium Community)1 source

Status in source: deprecated.

Names: ldapUserSearchBaseDN

Technical details

{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ldapUserSearchBaseDN",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"0",
".",
".",
"255",
")",
")",
"ACCESS",
"read-write",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"As part of the user authentication process, it is necessary to search the LDAP server for one or more attributes associated with a particular user. Any search request must specify the base DN for the actual search. This field specifies the base DN which should be used to search the User directory. This is a NULL terminated 255 byte string. An example might look like cn=users,dn=foobar,dn=com. If this field is left blank, the Root DN will be used as the search base instead. As mentioned, user searches are part of the authentication process. They are carried out to retrieve information about the user such as login permissions, callback number, and group memberships. For Version 2.0 LDAP clients, it is strongly encouraged that this parameter be configured, otherwise a search using the root DN may not succeed (as seen on Active Directory servers). NOTE: This MIB object is for MM only. NOTE: This Mib object is deprecated and no longer supported.\"",
"::=",
"{",
"ldapClientCfg",
"8",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"As part of the user authentication process, it is necessary to search the LDAP server for one or more attributes associated with a particular user. Any search request must specify the base DN for the actual search. This field specifies the base DN which should be used to search the User directory. This is a NULL terminated 255 byte string. An example might look like cn=users,dn=foobar,dn=com. If this field is left blank, the Root DN will be used as the search base instead. As mentioned, user searches are part of the authentication process. They are carried out to retrieve information about the user such as login permissions, callback number, and group memberships. For Version 2.0 LDAP clients, it is strongly encouraged that this parameter be configured, otherwise a search using the root DN may not succeed (as seen on Active Directory servers). NOTE: This MIB object is for MM only. NOTE: This Mib object is deprecated and no longer supported."
],
null,
null,
null,
null
]
}

IBM MIB copies (LibreNMS/Observium Community) · Publisher's source file: BLADE-MIB
Vendor MIB copy from the LibreNMS archive. IBM support.

Module: BLADE-MIB

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises', 'IpAddress']}
```
· Download BLADE-MIB
Related source files and packages:
Same file in Observium Community.

Historical records

Additional source information

Information from OID Repository

Vendor: IBM
Module: BLADE-MIB

[Automatically extracted from oidview.com]

Information from Circitor

ldapUserSearchBaseDN     OBJECT-TYPE
                      SYNTAX  OCTET STRING (SIZE(0..64))
                      ACCESS  read-write
                      STATUS  mandatory
                      DESCRIPTION
                      "As part of the user authentication process, it is necessary to search 
                      the LDAP server for one or more attributes associated with a particular 
                      user. Any search request must specify the base DN for the actual search. 
                      This field specifies the base DN which should be used to search the User 
                      directory. An example might look like cn=users,dn=foobar,dn=com. If this 
                      field is left blank, the Root DN will be used as the search base instead.
                      As mentioned, user searches are part of the authentication process. They 
                      are carried out to retrieve information about the user such as login 
                      permissions, callback number, and group memberships. For Version 2.0 LDAP 
                      clients, it is strongly encouraged that this parameter be configured, 
                      otherwise a search using the root DN may not succeed (as seen on Active 
                      Directory servers)."
                      ::= { ldapClientCfg 8 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2)

Bob Moore

Siblings (25)

OID	Name	Description
1.3.6.1.4.1.2.3.51.2.4.9.3.6.1	ldapServer1NameOrIPAddress	A NULL terminated 64 byte string that contains the LDAP server host name or IP address (a.b.c.d).
1.3.6.1.4.1.2.3.51.2.4.9.3.6.2	ldapServer1PortNumber	LDAP server port number.
1.3.6.1.4.1.2.3.51.2.4.9.3.6.3	ldapServer2NameOrIPAddress	A NULL terminated 64 byte string that contains the LDAP server host name or IP address (a.b.c.d).
1.3.6.1.4.1.2.3.51.2.4.9.3.6.4	ldapServer2PortNumber	LDAP server port number.
1.3.6.1.4.1.2.3.51.2.4.9.3.6.5	ldapServer3NameOrIPAddress	A NULL terminated 64 byte string that contains the LDAP server host name or IP address (a.b.c.d).
1.3.6.1.4.1.2.3.51.2.4.9.3.6.6	ldapServer3PortNumber	LDAP server port number.
1.3.6.1.4.1.2.3.51.2.4.9.3.6.7	ldapRootDN	Distinguished Name for root entry of directory tree. An example might look like dn=foobar,dn=com.
1.3.6.1.4.1.2.3.51.2.4.9.3.6.9	ldapGroupFilter	This filter is used for group authentication. It specifies what group or groups that this MM belongs to. If left blank, group au…
1.3.6.1.4.1.2.3.51.2.4.9.3.6.10	ldapBindingMethod	On initial binds to the LDAP server during user authentication, there are three options: Anonymous authentication: Bind attempt i…
1.3.6.1.4.1.2.3.51.2.4.9.3.6.11	ldapClientAuthenticationDN	The initial bind to the LDAP server during user authentication can be performed with anonymous authentication, client based auth…
1.3.6.1.4.1.2.3.51.2.4.9.3.6.12	ldapClientAuthenticationPassword	The client authentication password
1.3.6.1.4.1.2.3.51.2.4.9.3.6.13	ldapUIDsearchAttribute	When the binding method selected is Anonymous authentication or Client authentication, the initial bind to the LDAP server is fo…
1.3.6.1.4.1.2.3.51.2.4.9.3.6.14	ldapGroupSearchAttribute	When the MM Group Filter name is configured, it is necessary to retrieve from the LDAP server the list of groups that a particul…
1.3.6.1.4.1.2.3.51.2.4.9.3.6.15	ldapLoginPermissionAttribute	When a user successfully authenticates via a LDAP server, it is necessary to retrieve the login permissions for this user. In or…
1.3.6.1.4.1.2.3.51.2.4.9.3.6.16	ldapUseDNSOrPreConfiguredServers	The MM contains a Version 2.0 LDAP Client that may be configured to provide user authentication through one or more LDAP servers…
1.3.6.1.4.1.2.3.51.2.4.9.3.6.17	ldapDomainSource	The DNS SRV request sent to the DNS server must specify a domain name. The LDAP client will determine where to get this domain n…
1.3.6.1.4.1.2.3.51.2.4.9.3.6.18	ldapSearchDomain	This parameter may be used as the domain name in the DNS SRV request, depending on how the Domain Source parameter is configured.
1.3.6.1.4.1.2.3.51.2.4.9.3.6.19	ldapServiceName	The DNS SRV request sent to the DNS server must also specify a service name. The configured value will be used for this purpose.…
1.3.6.1.4.1.2.3.51.2.4.9.3.6.20	ldapRBSModelCfg
1.3.6.1.4.1.2.3.51.2.4.9.3.6.21	ldapTargetName
1.3.6.1.4.1.2.3.51.2.4.9.3.6.22	ldapAuthCfg
1.3.6.1.4.1.2.3.51.2.4.9.3.6.23	ldapForestName
1.3.6.1.4.1.2.3.51.2.4.9.3.6.24	ldapDomainName
1.3.6.1.4.1.2.3.51.2.4.9.3.6.25	ldapServer4NameOrIPAddress
1.3.6.1.4.1.2.3.51.2.4.9.3.6.26	ldapServer4PortNumber