tmnxOesCfgBlocked
TIMETRA-OES-MIB ·
.1.3.6.1.4.1.6527.3.1.3.98.0.15
Object
notification
[CAUSE] This event tmnxOesCfgBlocked notification is generated when a
configuration being made in the OES is blocked.
[EFFECT] The configuration is not active in the OES.
[RECOVERY]
One possible reason for this configuration failure is if there is a card
present in the OES that is a supported card type but the router was not yet
aware of its presence. This condition should clear as soon as the router
becomes aware of the card. A second reason is when the supported card is
present and is misaligned with the configuration (e.g. card present in slot
3 and 4, yet configuration is oes-1/2 where the width of card is two slots).
This condition cannot be cleared automatically as the card has to be moved
to the correct slot (or the configuration has to be removed for card oes-1/3
via cli command ). A third reason is when there is an unsupported card type
in the OES that the router cannot manage. This condition cannot be cleared
automatically and the OES will need to be recommissioned to clear the
condition.
Note: services on cards not impacted by the unknown card type are not
affected.
Context
- MIB
- TIMETRA-OES-MIB
- OID
.1.3.6.1.4.1.6527.3.1.3.98.0.15- Type
- notification
- Status
- current
- Parent
- tmnxOesNotifications
- 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-OES-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-OES-MIB::tmnxOesCfgBlocked'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-OES-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-OES-MIB::tmnxOesCfgBlocked'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of