tmnxLdapOperStateChange
TIMETRA-LDAP-MIB ·
.1.3.6.1.4.1.6527.3.1.3.106.0.1
Object
notification
[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'.
Context
- MIB
- TIMETRA-LDAP-MIB
- OID
.1.3.6.1.4.1.6527.3.1.3.106.0.1- Type
- notification
- Status
- current
- Parent
- tmnxLdapNotifications
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workNotifications are emitted by an agent; they cannot be read with snmpget or walked.
Inspect the notification definition
/usr/bin/snmptranslate -Pud -Ir -Td -m 'TIMETRA-LDAP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-LDAP-MIB::tmnxLdapOperStateChange'
More examples
Translate to a numeric OID
/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::tmnxLdapOperStateChange'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of