TIMETRA-LDAP-MIB

        This document is the SNMP MIB module for the Nokia SROS implementation
of LDAP.
        
Copyright 2003-2018 Nokia. All rights reserved. Reproduction of this
document is authorized on the condition that the foregoing copyright
notice is included.
        
This SNMP MIB module (Specification) embodies Nokia's
proprietary intellectual property.  Nokia retains all
title and ownership in the Specification, including any
revisions.
        
Nokia grants all interested parties a non-exclusive license to use and
distribute an unmodified copy of this Specification in connection with
management of Nokia products, and without fee, provided this copyright
notice and license appear on all copies.
        
This Specification is supplied `as is', and Nokia makes no warranty,
either express or implied, as to the use, operation, condition, or
performance of the Specification.
    
Source file
TIMETRA-LDAP-MIB
Last revised
Identity
timetraLdapMIBModule
Base OID
1.3.6.1.4.1.6527.1.1.3.106
Imported Objects
INET-ADDRESS-MIB InetAddress InetAddressType
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString RowStatus TimeStamp TruthValue
TIMETRA-GLOBAL-MIB timetraSRMIBModules tmnxSRConfs tmnxSRNotifyPrefix tmnxSRObjs
TIMETRA-TC-MIB TmnxAdminState TmnxLongDisplayString TmnxOperState TNamedItemOrEmpty TTcpUdpPort
Net-SNMP examples using the nokia MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-LDAP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-LDAP-MIB::timetraLdapMIBModule'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'TIMETRA-LDAP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-LDAP-MIB::timetraLdapMIBModule'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (36)
.1.3.6.1.4.1.6527.1.1.3.106
.1.3.6.1.4.1.6527.3.1.1.106
.1.3.6.1.4.1.6527.3.1.1.106.1
.1.3.6.1.4.1.6527.3.1.1.106.2
.1.3.6.1.4.1.6527.3.1.1.106.2.1
.1.3.6.1.4.1.6527.3.1.2.106
.1.3.6.1.4.1.6527.3.1.2.106.1
.1.3.6.1.4.1.6527.3.1.2.106.1.1
.1.3.6.1.4.1.6527.3.1.2.106.1.1.1
.1.3.6.1.4.1.6527.3.1.2.106.1.2
.1.3.6.1.4.1.6527.3.1.2.106.1.2.1
.1.3.6.1.4.1.6527.3.1.2.106.1.2.2
Unsigned32
.1.3.6.1.4.1.6527.3.1.2.106.1.2.3
SecondsUnsigned32
.1.3.6.1.4.1.6527.3.1.2.106.1.2.4
.1.3.6.1.4.1.6527.3.1.2.106.1.2.5
.1.3.6.1.4.1.6527.3.1.2.106.1.2.6
.1.3.6.1.4.1.6527.3.1.2.106.10
.1.3.6.1.4.1.6527.3.1.2.106.2
.1.3.6.1.4.1.6527.3.1.2.106.2.1
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1
Unsigned32
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.1
OctetString
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.10
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.11
OctetString
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.12
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.13
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.2
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.3
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.4
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.5
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.6
OctetString
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.7
Integer32
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.8
OctetString
.1.3.6.1.4.1.6527.3.1.2.106.2.1.1.9
.1.3.6.1.4.1.6527.3.1.2.106.3
.1.3.6.1.4.1.6527.3.1.3.106
.1.3.6.1.4.1.6527.3.1.3.106.0
Dependencies (6) 6 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. INET-ADDRESS-MIBrfc
  4. SNMPv2-CONFrfc
  5. TIMETRA-GLOBAL-MIBnokia
  6. TIMETRA-TC-MIBnokia
  7. TIMETRA-LDAP-MIBnokiaselected
Compliance Statements (1)

OID .1.3.6.1.4.1.6527.3.1.1.106.1.1
The compliance statement for the management of the LDAP feature on
Nokia SROS series systems.
Required groups
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.6527.3.1.3.106.0.1
[CAUSE]The tmnxLdapOperStateChange notification is generated when the
tmnxLdapOperState has transitioned either from 'outOfService' to
'inService' or from 'inService' to 'outOfService' state.

[EFFECT]If tmnxLdapOperState has transitioned to 'outOfService' state
then the LDAP protocol is not available for use. If tmnxLdapOperState
has transitioned to 'inService' state then the LDAP protocol is
available for use.

[RECOVERY]If the new state corresponds to the value of
tmnxLdapAdminState, then this is desirable behavior and no recovery is
needed. If the new state of the tmnxLdapOperState object is
'outOfService' while the value of the object tmnxLdapAdminState is
'inService', make sure that the value of tmnxLdapServerOperState of at
least one LDAP server connection is 'inService'.
.1.3.6.1.4.1.6527.3.1.3.106.0.2
[CAUSE]The tmnxLdapServerOperStateChange notification is generated
when the tmnxLdapServerOperState has transitioned either from
'outOfService' to 'inService' or from 'inService' to 'outOfService'
state.

[EFFECT]If tmnxLdapServerOperState has transitioned to 'outOfService'
state then the particular LDAP server connection is not available for
use. If tmnxLdapServerOperState has transitioned to 'inService' state
then the particular LDAP server connection is available for use.

[RECOVERY]If the new state corresponds to the
tmnxLdapServerAdminState, then this is the desirable behavior and no
recovery is needed. If the new state of the tmnxLdapServerOperState
object is 'outOfService' while the value of the object
tmnxLdapServerAdminState is 'inService', make sure that the LDAP
server connection parameters are properly configured and the LDAP
server is reachable.