All MIBs › BLADE-MIB › ldapDomainSource
ldapDomainSource
Module: BLADE-MIB
OID (symbolic): BLADE-MIB::ldapDomainSource
OID (numeric): 1.3.6.1.4.1.2.3.51.2.4.9.3.6.17
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: The DNS SRV request sent to the DNS server must specify a domain name. The LDAP client will determine where to get this domain name based on one of the following three options:
- extractSearchDomainFromLoginID: With this option, the LDAP client will use the domain name in the login id. For example, if the login id is joesmith@mycompany.com, the domain name equals mycompany.com. If the domain name cannot be extracted, the DNS SRV will fail, causing the user authentication to fail automatically.
- useOnlyConfiguredSearchDomainBelow: With this option, the LDAP client will use the domain name configured in the Search Domain parameter.
- tryLoginFirstThenConfiguredValue: With this option, the LDAP client will first attempt to extract the domain name from the login id. If this succeeds, this domain name will be used in the DNS SRV request. If there is no domain name present in the login id, the LDAP client will instead use the configured Search Domain parameter as the domain name in the DNS SRV request. If nothing is configured, user authentication will fail immediately.
What is ldapDomainSource?
This read-write setting controls how the LDAP client determines the domain name to use in its DNS SRV lookup: pulling it from the part of the login ID after the '@' sign, always using the configured Search Domain value, or trying the login ID first and falling back to the configured Search Domain. It matters for authentication reliability -- for example, if a user logs in as 'joesmith@mycompany.com' with 'extractSearchDomainFromLoginID' selected, the domain used is 'mycompany.com'.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.4.9.3.6.17 snmpwalk -v2c -c public <target> BLADE-MIB::ldapDomainSource
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.4.9.3.6.17.1 snmpget -v2c -c public <target> BLADE-MIB::ldapDomainSource.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.2.3.51.2.4.9.3.6.17.1 i <value>
Start monitoring IBM BladeCenter Management Module (MM) (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BLADE-MIB::ldapDomainSource OID value, configure state conditions and alerts, and monitor any IBM BladeCenter Management Module (MM) (legacy) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2 | ibm | BLADE-MIB |
| 1.3.6.1.4.1.2.3 | ibmAgents | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51 | netfinitySupportProcessorAgent | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2 | bladeCenterSnmpMIB | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.4 | configureSP | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.9 | networkConfiguration | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.9.3 | tcpProtocols | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.9.3.6 | ldapClientCfg | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.4.9.3.6.17 | ldapDomainSource | BLADE-MIB |