ochmAnoRBStatusDisconnectionSuccess
OXO-CALL-HANDLING-MIB ·
.1.3.6.1.4.1.6486.64.4200.1.2.3.0.73
Object
notification
Change in the RB connection state: RB disconnection success ------------- Byte 1: Cause 00: No cause 0x01: First OXO startup 0x02: OXO startup 0x03: RB Agent startup 0x04: RB disabled 0x05: RB enabled 0x06: RB reconnection after a disconnection due to network troubles 0x07: RB reconnection after a disconnection due to a ping timeout 0x08: RB Agent stop ----------------------- Byte 2: RB account type 00: No type 01: Activation account 02: Final account
Context
- MIB
- OXO-CALL-HANDLING-MIB
- OID
.1.3.6.1.4.1.6486.64.4200.1.2.3.0.73- Type
- notification
- Status
- current
- Parent
- ochmNotifications
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 'OXO-CALL-HANDLING-MIB' -M '/opt/observium/mibs/alcatel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'OXO-CALL-HANDLING-MIB::ochmAnoRBStatusDisconnectionSuccess'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'OXO-CALL-HANDLING-MIB' -M '/opt/observium/mibs/alcatel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'OXO-CALL-HANDLING-MIB::ochmAnoRBStatusDisconnectionSuccess'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.