Status in source: current.
Names: tmnxOesCfgBlocked
Technical details
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"tmnxOesCfgBlocked",
"NOTIFICATION-TYPE",
"OBJECTS",
"{",
"tmnxHwClass",
"}",
"STATUS",
"current",
"DESCRIPTION",
"\"[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.\"",
"::=",
"{",
"tmnxOesNotifications",
"15",
"}"
],
"syntax_tree": [
[
"Objects",
[
"tmnxHwClass"
]
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"[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."
],
null
]
}
- Nokia networking MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Nokia support.
Module: TIMETRA-OES-MIB
See published definition above
Module imports
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'TIMETRA-TC-MIB': ['TmnxDisplayStringURL', 'TmnxOperState', 'TmnxActionType', 'TNamedItemOrEmpty'], 'INET-ADDRESS-MIB': ['InetAddressPrefixLength', 'InetAddressType', 'InetAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'TIMETRA-GLOBAL-MIB': ['tmnxSRObjs', 'tmnxSRConfs', 'tmnxSRNotifyPrefix', 'timetraSRMIBModules'], 'TIMETRA-CHASSIS-MIB': ['tmnxHwClass', 'TmnxHwIndexOrZero', 'TmnxDeviceState']}
Related source files and packages:
- Netdisco MIB archive copies
· Publisher's source file: timetra-oes-mib.mib
Vendor MIB copy from the Netdisco archive.
Module: TIMETRA-OES-MIB
See published definition above
Module imports
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'RowStatus', 'TruthValue', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'TIMETRA-TC-MIB': ['TmnxDisplayStringURL', 'TmnxOperState', 'TmnxActionType', 'TNamedItemOrEmpty'], 'INET-ADDRESS-MIB': ['InetAddressPrefixLength', 'InetAddressType', 'InetAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'TIMETRA-GLOBAL-MIB': ['tmnxSRObjs', 'tmnxSRConfs', 'tmnxSRNotifyPrefix', 'timetraSRMIBModules'], 'TIMETRA-CHASSIS-MIB': ['tmnxHwClass', 'TmnxHwIndexOrZero', 'TmnxDeviceState']}
Related source files and packages: