Standard view Table view

TIMETRA-OES-MIB

        This document is the SNMP MIB module to manage and provision the
Optical Extension Shelf (OES) components of the Nokia SROS
device.
        
Copyright (c) 2013-2016 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-OES-MIB
Last revised: 1 Jan 2016, 00:00 UTC
Identity: timetraOesMIBModule
Base OID: 1.3.6.1.4.1.6527.1.1.3.98

Imported Objects

INET-ADDRESS-MIB	InetAddress InetAddressPrefixLength InetAddressType
SNMP-FRAMEWORK-MIB	SnmpAdminString
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	DateAndTime DisplayString RowStatus TEXTUAL-CONVENTION (no object page) TruthValue
TIMETRA-CHASSIS-MIB	TmnxDeviceState tmnxHwClass TmnxHwIndexOrZero
TIMETRA-GLOBAL-MIB	timetraSRMIBModules tmnxSRConfs tmnxSRNotifyPrefix tmnxSRObjs
TIMETRA-TC-MIB	TmnxActionType TmnxDisplayStringURL TmnxOperState TNamedItemOrEmpty

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-OES-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-OES-MIB::timetraOesMIBModule'

Walk the MIB subtree

/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'TIMETRA-OES-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-OES-MIB::timetraOesMIBModule'

How SNMP, Net-SNMP, MIB paths, and variants work

Objects (33)

timetraOesMIBModule		`.1.3.6.1.4.1.6527.1.1.3.98`
tmnxOesConformance		`.1.3.6.1.4.1.6527.3.1.1.98`
tmnxOesCompliances		`.1.3.6.1.4.1.6527.3.1.1.98.1`
tmnxOesGroups		`.1.3.6.1.4.1.6527.3.1.1.98.2`
tmnxOesV14v0Groups		`.1.3.6.1.4.1.6527.3.1.1.98.2.1`
tmnxOesObjs		`.1.3.6.1.4.1.6527.3.1.2.98`
tmnxOesConfigObjs		`.1.3.6.1.4.1.6527.3.1.2.98.1`
tmnxOesCfCache r/w	Enumeration	`.1.3.6.1.4.1.6527.3.1.2.98.1.1`
tmnxOesReboot r/w	Enumeration	`.1.3.6.1.4.1.6527.3.1.2.98.1.2`
tmnxOesSwUpgrade r/w	TIMETRA-TC-MIBTmnxActionType	`.1.3.6.1.4.1.6527.3.1.2.98.1.3`
tmnxOesSoftwareRepository r/w	TIMETRA-TC-MIBTNamedItemOrEmpty	`.1.3.6.1.4.1.6527.3.1.2.98.1.4`
tmnxOesCtlCommsVRtrName r/w	TIMETRA-TC-MIBTNamedItemOrEmpty	`.1.3.6.1.4.1.6527.3.1.2.98.1.5`
tmnxOesCtlCommsAddressType r/w	INET-ADDRESS-MIBInetAddressType	`.1.3.6.1.4.1.6527.3.1.2.98.1.6`
tmnxOesCtlCommsAddress r/w	OctetString	`.1.3.6.1.4.1.6527.3.1.2.98.1.7`
tmnxOesCtlCommsTimeout r/w	secondsUnsigned32	`.1.3.6.1.4.1.6527.3.1.2.98.1.8`
tmnxOesCtlCommsRetryLimit r/w	Unsigned32	`.1.3.6.1.4.1.6527.3.1.2.98.1.9`
tmnxOesStatObjs		`.1.3.6.1.4.1.6527.3.1.2.98.2`
tmnxOesRunningSwImage	SNMPv2-TCDisplayString	`.1.3.6.1.4.1.6527.3.1.2.98.2.1`
tmnxOesSwUpgradeLastStatus	TmnxOesSWMgmtStatus	`.1.3.6.1.4.1.6527.3.1.2.98.2.10`
tmnxOesSwUpgradeLastTime	SNMPv2-TCDateAndTime	`.1.3.6.1.4.1.6527.3.1.2.98.2.11`
tmnxOesSwUpgradeCleanupLstStatus	TmnxOesSWMgmtStatus	`.1.3.6.1.4.1.6527.3.1.2.98.2.12`
tmnxOesSwUpgradeLastCompleteTime	SNMPv2-TCDateAndTime	`.1.3.6.1.4.1.6527.3.1.2.98.2.13`
tmnxOesExpectedSwImage	SNMPv2-TCDisplayString	`.1.3.6.1.4.1.6527.3.1.2.98.2.14`
tmnxOesCtlCommsStatus	Enumeration	`.1.3.6.1.4.1.6527.3.1.2.98.2.2`
tmnxOesStatus	Enumeration	`.1.3.6.1.4.1.6527.3.1.2.98.2.3`
tmnxOesNtpStatus	Enumeration	`.1.3.6.1.4.1.6527.3.1.2.98.2.4`
tmnxOesUserPanelHwIndex	TIMETRA-CHASSIS-MIBTmnxHwIndexOrZero	`.1.3.6.1.4.1.6527.3.1.2.98.2.5`
tmnxOesUserPanelState	TIMETRA-CHASSIS-MIBTmnxDeviceState	`.1.3.6.1.4.1.6527.3.1.2.98.2.6`
tmnxOesCtlCommsDownReason	Enumeration	`.1.3.6.1.4.1.6527.3.1.2.98.2.7`
tmnxOesNotifyObjs		`.1.3.6.1.4.1.6527.3.1.2.98.3`
tmnxOesEventReason	TmnxOesEventReason	`.1.3.6.1.4.1.6527.3.1.2.98.3.1`
tmnxOesMIBNotifyPrefix		`.1.3.6.1.4.1.6527.3.1.3.98`
tmnxOesNotifications		`.1.3.6.1.4.1.6527.3.1.3.98.0`

Dependencies (8) 8 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

TIMETRA-OES-MIBnokiaselected
- INET-ADDRESS-MIBrfcdefault fallback3 symbols
  - SNMPv2-SMIrfc3 symbols
  - SNMPv2-TCrfc1 symbol
    - SNMPv2-SMIrfcshared1 symbol
- SNMP-FRAMEWORK-MIBrfcdefault fallback1 symbol
  - SNMPv2-CONFrfc2 symbols
    - SNMPv2-SMIrfcshared3 symbols
  - SNMPv2-SMIrfcshared4 symbols
  - SNMPv2-TCrfcshared1 symbol
- SNMPv2-CONFrfcdefault fallbackshared3 symbols
- SNMPv2-SMIrfcdefault fallbackshared4 symbols
- SNMPv2-TCrfcdefault fallbackshared5 symbols
- TIMETRA-CHASSIS-MIBnokia3 symbols
  - SNMP-FRAMEWORK-MIBrfcdefault fallbackshared1 symbol
  - SNMPv2-CONFrfcdefault fallbackshared3 symbols
  - SNMPv2-SMIrfcdefault fallbackshared8 symbols
  - SNMPv2-TCrfcdefault fallbackshared9 symbols
  - TIMETRA-GLOBAL-MIBnokia4 symbols
    - SNMPv2-CONFrfcdefault fallbackshared2 symbols
    - SNMPv2-SMIrfcdefault fallbackshared3 symbols
    - SNMPv2-TCrfcdefault fallbackshared1 symbol
  - TIMETRA-TC-MIBnokia23 symbols
    - INET-ADDRESS-MIBrfcdefault fallbackshared4 symbols
    - SNMPv2-SMIrfcdefault fallbackshared4 symbols
    - SNMPv2-TCrfcdefault fallbackshared3 symbols
    - TIMETRA-GLOBAL-MIBnokiashared1 symbol
- TIMETRA-GLOBAL-MIBnokiashared4 symbols
- TIMETRA-TC-MIBnokiashared4 symbols

Dependency-first compile order

Type Definitions (2)

TmnxOesEventReason	OctetString	`range: 0..80`
TmnxOesSWMgmtStatus	Enumeration	`none(0)` `unknown(1)` `inProgress(2)` `successful(3)` `failed(4)` `paused(5)`

Conformance Groups (3)

tmnxOesGroupV14v0	tmnxOesCfCache tmnxOesRunningSwImage tmnxOesCtlCommsStatus tmnxOesReboot tmnxOesStatus tmnxOesUserPanelHwIndex tmnxOesUserPanelState tmnxOesCtlCommsDownReason tmnxOesNtpStatus tmnxOesCtlCommsVRtrName tmnxOesCtlCommsAddressType tmnxOesCtlCommsAddress tmnxOesCtlCommsTimeout tmnxOesCtlCommsRetryLimit tmnxOesSwUpgrade tmnxOesSwUpgradeLastStatus tmnxOesSwUpgradeLastTime tmnxOesSwUpgradeCleanupLstStatus tmnxOesSoftwareRepository tmnxOesSwUpgradeLastCompleteTime tmnxOesExpectedSwImage The group of objects supporting management of OES on Nokia SROS series systems in release 14.0.	`.1.3.6.1.4.1.6527.3.1.1.98.2.1.1`
tmnxOesNotificationGroupV14v0	tmnxOesCtlCommsDown tmnxOesCtlCommsUp tmnxOesDbSyncFailure tmnxOesDbSyncFailureClear tmnxOesDbInvalid tmnxOesDbInvalidClear tmnxOesDbUnsync tmnxOesDbUnsyncClear tmnxOesSwUpgdCleanupFailed tmnxOesSwUpgdFailed tmnxOesNtpOutOfSync tmnxOesNtpSync tmnxOesSwBelowMinRev tmnxOesCfgFailNoMemory tmnxOesCfgBlocked tmnxOesFirmwareCondition The group of notifications supporting management of OES on Nokia SROS series systems in release 14.0.	`.1.3.6.1.4.1.6527.3.1.1.98.2.1.2`
tmnxOesNotifyObjsGroupV14v0	tmnxOesEventReason The group of notification objects supporting management of OES on Nokia SROS series systems in release 14.0.	`.1.3.6.1.4.1.6527.3.1.1.98.2.1.3`

Compliance Statements (1)

OID .1.3.6.1.4.1.6527.3.1.1.98.1.1

The compliance statement for management of OES
on Nokia SROS series systems for release 14.0.

Required groups

mandatory	tmnxOesGroupV14v0
mandatory	tmnxOesNotificationGroupV14v0
mandatory	tmnxOesNotifyObjsGroupV14v0

Notifications / Traps (16)

Name	OID	Description
tmnxOesCtlCommsDown TIMETRA-CHASSIS-MIBtmnxHwClass tmnxOesCtlCommsDownReason	`.1.3.6.1.4.1.6527.3.1.3.98.0.1`	[CAUSE] The tmnxOesCtlCommsDown notification is generated when the active CPM can't reach the OES master chassis. [EFFECT] The OES can't be managed by the router. [RECOVERY] Ensure that all control communications ports between the router and the OES master chassis are correctly connected and test the cables.
tmnxOesNtpOutOfSync TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.10`	[CAUSE] The tmnxOesNtpOutOfSync notification is generated when NTP time on the OES is not synchronized to the host router. The host router must have NTP enabled and have recovered time from external time sources (NTP to PTP). If there is no NTP time source for the router, it will not serve time to the OES. In addition, once the NE is power cycled, it takes approximately 20-30 minutes to initialize. Thereafter, time synchronization will be completed, with a maximum delay time of 2-3 minutes. [EFFECT] Timestamp of each event occurring on the OES may not be exactly aligned with the host router. [RECOVERY] Ensure the host router has NTP configured and a reachable time source. Allow 40 minutes for the condition to clear.
tmnxOesNtpSync TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.11`	[CAUSE] The tmnxOesNtpSync notification is generated when NTP on the OES is synchronized to the host router. The host router is serving acceptable time toward the OES and the OES has completed initial acquisition of time from the host. [EFFECT] None. [RECOVERY] No recovery is required.
tmnxOesSwBelowMinRev TIMETRA-CHASSIS-MIBtmnxHwClass tmnxOesRunningSwImage tmnxOesExpectedSwImage	`.1.3.6.1.4.1.6527.3.1.3.98.0.12`	[CAUSE] The tmnxOesSwBelowMinRev notification is generated when the version of the running OES software image is below the minimum expected version. [EFFECT] The OES may not be operating as expected. [RECOVERY] Upgrade the OES to a software image that is equal to or greater than the minimum expected version.
tmnxOesFirmwareCondition TIMETRA-CHASSIS-MIBtmnxHwClass tmnxOesEventReason	`.1.3.6.1.4.1.6527.3.1.3.98.0.13`	[CAUSE] The tmnxOesFirmwareCondition notification is generated when the firmware on the card has a condition that needs to be notified to network administrator. The value of tmnxOesEventReason object specifies the reason. [EFFECT] Not all the features may be available. [RECOVERY] Perform a hard reset of the card. If the condition persists, then contact Nokia customer support.
tmnxOesCfgFailNoMemory TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.14`	[CAUSE] The tmnxOesCfgFailNoMemory notification is generated when a request to obtain dynamic memory to download a configuration to the OES has failed. [EFFECT] The configuration is not active in the OES. [RECOVERY] This may be a temporary issue and the condition may clear on its own. If the event is raised periodically, then there is a permanent memory issue and the support organization should be informed.
tmnxOesCfgBlocked TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.15`	[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.
tmnxOesSwUpgdCleanupFailed TIMETRA-CHASSIS-MIBtmnxHwClass tmnxOesEventReason	`.1.3.6.1.4.1.6527.3.1.3.98.0.16`	[CAUSE] This event tmnxOesSwUpgdCleanupFailed notification is generated when the operation to clean-up a failed software upgrade fails. The reason for the failure is specified in the object tmnxOesEventReason. [EFFECT] The OES software revision cannot be determined and so the operational state of the respective OES or OES card is indeterminate. [RECOVERY] 1) Determine the reason for the upgrade failure from tmnxOesEventReason in the notification. First clear the condition indicated by the reason. 2) Re-try the upgrade procedure. 3) Contact the Nokia technical support team if the re-try does not fix the problem.
tmnxOesCtlCommsUp TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.2`	[CAUSE] The tmnxOesCtlCommsUp notification is generated when the active CPM can reach the OES master chassis. [EFFECT] The OES can be managed by the router. [RECOVERY] No recovery required.
tmnxOesDbSyncFailure TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.3`	The active Equipment Controller is unable to synchronize its database with the inactive Equipment Controller. [CAUSE] The tmnxOesDbSyncFailure notification may be raised under the following conditions: 1) An incorrectly seated Equipment Controller; 2) The software versions on the active and inactive Equipment Controllers are not compatible; 3) A hardware problem with one or both controllers. [EFFECT] The OES does not have redundancy protection between the two Equipment Controller cards. [RECOVERY] Proceed as follows to clear the Database Synchronization Failed alarm: 1) Remove the Equipment Controller with the condition and examine the connector on the back of the card for damage, including bent or broken pins; 2) Examine the connector on the backplane for damage. If there is damage to the backplane of the shelf, contact your service representative; 3) Re-insert the Equipment Controller into its original slot and allow the card to initialize; 4) Repeat Step 2) through Step 4) for the second Equipment Controller; 5) Replace the Equipment Controller with the alarm condition with a new unit. If the condition is not cleared, replace the second Equipment Controller with a new unit. Follow the return and repair process to return the faulty card to an authorized repair center for replacement.
tmnxOesDbSyncFailureClear TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.4`	[CAUSE] The tmnxOesDbSyncFailureClear notification is generated when the active Equipment Controller is able to synchronize its database with the inactive Equipment Controller. [EFFECT] The active and inactive Equipment Controller's databases are now synchronized. [RECOVERY] No recovery required.
tmnxOesDbInvalid TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.5`	[CAUSE] The tmnxOesDbInvalid notification may be raised under the following conditions: 1) During initial installation, if the OES is not properly commissioned; 2) The serial number in the database does not match that of the OES either because the controller was replaced or the alarm card was replaced; 3) A downgrade of OES software has occurred; 4) Equipment Controller is removed/reseated during a system process, causing file corruption; 5) The database audit failed indicating some type of corruption of the database. [EFFECT] The OES is not in a normal operating mode. It does not have the correct configuration and the state of its cards is unpredictable. As a result, the OES will not boot normally and not all commands are allowed. [RECOVERY] A database corruption on the OES requires that the OES be re-commissioned. The correct database is held in the host system so it will be restored to the shelf once the existing database is cleared and the host re-establishes communication with the OES.
tmnxOesDbInvalidClear TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.6`	[CAUSE] The tmnxOesDbInvalidClear notification is generated when the active Equipment Controller previously under tmnxOesDbInvalid condition now contains a valid database. [EFFECT] The OES active Equipment Controller's database is now valid. [RECOVERY] No recovery is required.
tmnxOesDbUnsync TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.7`	[CAUSE] The tmnxOesDbUnsync notification is generated when the active and standby Equipment Controllers are not in sync. [EFFECT] The OES does not have redundancy protection between the two Equipment Controller cards. If a switchover were to occur, then the database of the newly active controller might not reflect the latest configuration. [RECOVERY] Proceed as follows to clear the Database Unsynchronization alarm: 1) Perform a warm reset of the standby controller; 2) If step 1 does not clear the alarm condition, then contact the next level of technical support for help.
tmnxOesDbUnsyncClear TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.8`	[CAUSE] The tmnxOesDbUnsyncClear notification is generated when the previously out of sync database is now synchronized between the active and standby Equipment Controller cards. [EFFECT] The database is synchronized between the active and standby Equipment Controller cards. [RECOVERY] No recovery is required.
tmnxOesSwUpgdFailed tmnxOesEventReason TIMETRA-CHASSIS-MIBtmnxHwClass	`.1.3.6.1.4.1.6527.3.1.3.98.0.9`	[CAUSE] The tmnxOesSwUpgdFailed notification is generated when a failure occurs in upgrading a component in the OES. This notification is applicable at the NE (Network Element) level and/or the card level. [EFFECT] The component is not upgraded. [RECOVERY] 1) Determine the reason the upgrade failed by checking the tmnxOesEventReason. First clear the condition indicated by the reason in the object tmnxOesEventReason. 2) Perform a soft reset on the card that failed to upgrade and try the upgrade procedure again. 3) Perform a hard reset on the card that failed to upgrade and try the upgrade procedure again. 4) Remove and re-insert the card that failed to upgrade and try the upgrade procedure again. 5) Replace the card that failed to upgrade and try the upgrade procedure again. 6) Inform the Nokia technical support team.