TIMETRA-OES-HARDWARE-MIB: View SNMP OID List / Download MIB

This document is the SNMP MIB module to manage and provision the Optical Extension Shelf (OES) hardware 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.

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

The group of objects supporting management of OES on Nokia SROS series systems in release 14.0.

The group of objects supporting OES notifications on Nokia SROS series systems in release 14.0.

The group of notifications supporting the OES hardware capabilities on Nokia SROS series systems in release 14.0.

The chassis type table has an entry for each Nokia SROS EOS series chassis model.

Each row entry represents an Nokia SROS OES series chassis model. Rows in this table are created by the agent at initialization and cannot be created or destroyed by SNMP Get or Set requests.

The value of tmnxOesChassisTypeIndex specifies the type of Nokia SROS series OES chassis model.

The value of tmnxOesChassisTypeName indicates the administrative name that identifies this type of Nokia SROS series OES chassis model. This name string may be used in CLI commands to specify a particular OES chassis model type.

The value of tmnxOesChassisTypeDescription indicates the detailed description of this Nokia SROS series OES chassis model.

The value of tmnxOesChassisTypeStatus indicates the chassis type support. When tmnxOesChassisTypeStatus has a value of 'true' it indicates that this chassis model is supported in this revision of the management software. When it has a value of 'false' there is no support.

The value of tmnxOesChassisLastChange indicates the time, since system startup, when tmnxOesChassisTable last changed configuration.

The tmnxOesChassisTable contains configuration information for OES chassis.

The tmnxOesChassisEntry consists of the configurable objects for a given OES chassis.

The value of tmnxOesChassisNumber specifies a unique value which identifies the OES chassis.

The value of tmnxOesChassisRowStatus specifies the row status. It allows the creation and deletion of rows in tmnxOesChassisTable. When creating an OES Chassis entry, tmnxOesChassisRowStatus and tmnxOesChassisAssignedType must be set together in the same SNMP SET request PDU.

The value of tmnxOesChassisRowLastChanged indicates the time this row was last changed.

The value of tmnxOesChassisAssignedType specifies the administratively assigned type of the OES chassis. tmnxOesChassisRowStatus and tmnxOesChassisAssignedType must be set together in the same SNMP SET request PDU.

The value of tmnxOesChassisEquippedType indicates the OES chassis type that is equipped.

The value of tmnxOesChassisActivitySwitch specifies the activity switch action for the OES chassis. When the value is set to 'doAction (1)', the OES chassis causes an activity switchover between this chassis's controller (i.e. EC) cards.

The value is a unique index that identifies common management information for Nokia SROS series manufactured hardware components within the specified chassis.

The table tmnxOesPFTable contains information about the OES power filter cards.

A row in tmnxOesPFTable is created/destroyed by the SYSTEM when there is a row created/destroyed in the tmnxHwTable for an OES power filter card.

The value of tmnxOesSlotNumber specifies the slot number of an OES power filter card.

The value of tmnxOesPFType indicates the type of an OES power filter card. Enumeration: 'ac': 1, 'dc': 2.

The value of tmnxOesPFAmpRating indicates the amperage rating of an OES power filter.

The value of tmnxOesPFInputCurrent indicates the input current of an OES power filter.

The value of tmnxOesPFInputVoltage indicates the input voltage of an OES power filter.

The value of tmnxOesPFInputPower indicates the input power of an OES power filter.

The value of tmnxOesPFClkA indicates the frequency offset of clock A of the OES power filter.

The value of tmnxOesPFClkB indicates the frequency offset of clock B of the OES power filter.

The value of tmnxOesPFClkDelta indicates the difference between the frequency offset of clock A and that of clock B

The value of tmnxOesPFState indicates an OES power filter's operational state.

The value of tmnxOesPFHwIndex indicates a unique index of common management information for hardware components within the specified chassis.

The value of sysUpTime when tmnxOesFanTable was last changed.

The table tmnxOesFanTable contains the information pertaining to the fan tray(s) of OES chassis.

Rows in tmnxOesFanTable are created/destroyed by the SYSTEM when tmnxOesChassisEntry rows are created/destroyed. Only certain slots can contain a fan in each OES chassis type.

The value of tmnxOesFanSlotNumber specifies the slot number of the fan in OES chassis.

The value of tmnxOesFanState indicates the fan's operational state.

The value of tmnxOesFanSpeedControl specifies the level of the fan speed. Enumeration: 'maximum': 2, 'normal': 1.

The value of tmnxOesFanHwIndex indicates a unique index that identifies common management information for Nokia SROS series manufactured hardware components within the specified chassis.

The card type table has an entry for each Nokia SROS EOS series card model.

Each row entry represents an Nokia SROS series Card model. Rows in this table are created by the agent at initialization and cannot be created or destroyed by SNMP Get or Set requests.

The unique index value which identifies this type of Nokia SROS series OES card model.

The administrative name that identifies this type of Nokia SROS series OES card model. This name string may be used in CLI commands to specify a particular card model type.

A detailed description of this Nokia SROS series OES card model.

When tmnxOesCardTypeStatus has a value of 'true' it indicates that this card model is supported in this revision of the management software. When it has a value of 'false' there is no support.

The value indicates the number of vertical slots this card type occupies.

The value indicates the number of horizontal slots this card type occupies.

The value indicates the number of ports that this card type contains.

The value of tmnxOesCardLastChange indicates the time since system startup this table was last changed.

The tmnxOesCardTable has an entry for each OES card slot in each chassis.

Each row entry represents an OES card slot in an OES chassis in the system. Entries cannot be created and deleted via SNMP SET operations. When tmnxOesChassisEntry is created, a tmnxOesCardEntry is created for each OES card slot in that chassis.

The value of tmnxOesCardAssignedType specifies the administratively assigned OES card type that should occupy this fabric slot in this chassis.

The value of tmnxOesCardEquippedType indicates the OES card type that is physically inserted into this slot in this chassis.

The value of tmnxOesCardSupportedTypes indicates what OES card types can be configured in this slot in this chassis.

The value of tmnxOesCardReboot specifies the reboot type and executes the reboot. Setting this variable to 'cardReboot' causes the OES card to execute a soft-reboot. Setting this variable to 'cardPowerCycle' causes the OES card to turn off and turn on power to the card initiating a hard-reboot.

The value of tmnxOesCardHwEntryIndex indicates a unique index that identifies common management information for Nokia SROS series manufactured hardware components within the specified chassis.

The value of tmnxOesCardRowLastChanged indicates the time since system startup this row was last changed.

The value of tmnxOesCardMemorySize indicates the amount of memory populated on this OES card.

The table tmnxOesControlCardTable contains information pertaining to the OES equipment controller (EC).

A row in tmnxOesControlCardTable is created/destroyed by the SYSTEM when there is a row created/destroyed in tmnxOesChassisTable for each OES chassis.

The value of tmnxOesControlCardActState indicates whether or not this control card is active. Enumeration: 'active': 2, 'unknown': 1, 'unequipped': 4, 'standby': 3.

The value of tmnxOesControlCardHwIndex indicates a unique index that identifies common management information for Nokia SROS series manufactured hardware components within the specified chassis.

The table tmnxOesCmnEqpPortTable contains the information pertaining to the ports of the common equipment cards of the OES chassis. The common equipment represents the hardware which includes the shelf, shelf controller, user panel (USPNL), equipment controller (EC), first level controller (FLC), PSS power distribution units, power filter card (PFD), fans, etc.

A Row in tmnxOesCmnEqpPortTable is created/destroyed by the SYSTEM when there is a row created/destroyed in the tmnxHwTable for each OES common equipment, e.g. equipment controller (EC) and user panel.

The value of tmnxOesCmnEqpPortNumber specifies the index of the tmnxOesCmnEqpPortTable table. It is a number that represents a port of the common equipment card uniquely within the card. This index along with the other indexes of the table are used to map this port uniquely within the equipment cards in an OES chassis.

The value of tmnxOesCmnEqpPortCardType indicates the type of the common equipment card that the port belongs to.

The value of tmnxOesCmnEqpPortOperStatus indicates the operational status of the port of the OES common equipment card.

The table tmnxOesCmnEqpPortTypeTable contains the information pertaining to the type of the ports of the common equipment cards, e.g. equipment control (EC) and user panel, of the OES chassis.

Rows in table tmnxOesCmnEqpPortTypeEntry are created by the SYSTEM at initialization and can not be created or destroyed by SNMP set requests. Each row represents an OES port within a common equipment OES card of a certain type.

The value of tmnxOesCmnEqpPortTypeName indicates the administrative name that describes the OES common equipment port type.

The value of tmnxOesCmnEqpPortTypeDescr indicates the detailed description of the OES common equipment port type.

The value of tmnxOesNotifyFailureReason is used by OES card or common equipment failure notifications to indicate the reason of failure.

The value of tmnxOesPortNotifyError indicates the error conditions on this OES port.

[CAUSE] The tmnxOesCtlCardPortDown notification is generated when a port (e.g. ES 1 or AUX) on an OES Control Card (e.g. EC card) is not operational. The reason may be a misconnected, disconnected or faulty cable, a faulty port or Control Card. [EFFECT] If an ES (Extension Shelf) port is down then one of the control plane communication paths between EC (Equipment Controller) cards in different OES Chassis is not available. The control communications with one or more OES subtending chassis may be affected rendering the Chassis unmanageable. Other control paths may be available. If an AUX port is down then one of the control plane communication paths between the router and the OES Master Chassis is not available and control communications with the OES may be affected rendering the OES unmanageable. Other control paths may be available. [RECOVERY] Check that the cable is correctly connected and test the cable.

[CAUSE] The tmnxOesCtlCardPortUp notification is generated when the port on the OES Control Card (e.g. EC card) is operational. [EFFECT] If an ES port is up then a control plane communication path between EC cards in different OES Chassis has been established. If an AUX port is up then a control plane communication path between the router and the OES Master Chassis has been established and the OES can be managed by the router. [RECOVERY] No recovery required

[CAUSE] The tmnxOesUsrpnlPortDown notification is generated when a port (E1 or E2) on an OES USRPNL card is not operational. The reason may be a misconnected, disconnected or faulty cable, or a faulty port or USRPNL. [EFFECT] If an E1 or E2 port is down then one of the control plane communication paths between the router and the OES Master Chassis is not available. The control communications with the OES may be affected rendering the OES chassis unmanageable. Other control communications paths may be available. [RECOVERY] Check that the cable is correctly connected and test the cable.

[CAUSE] The tmnxOesUsrpnlPortUp notification is generated when the OES USRPNL port is now operational. [EFFECT] If an E1 or E2 port is up then a control plane communication path between the router and the OES Master Chassis has been established and the OES can be managed by the router. [RECOVERY] No recovery required.

[CAUSE] The tmnxOesFanRemoved notification is generated when the OES fan unit is removed from its slot in the OES chassis. [EFFECT] The function of OES fan unit is not available. [RECOVERY] Insert OES fan unit into its slot.

[CAUSE] The tmnxOesFanInserted notification is generated when the OES fan unit is inserted into its slot in the OES chassis. [EFFECT] The OES chassis is now equipped with a fan unit. [RECOVERY] No recovery required.

[CAUSE] The tmnxOesFan32HReqd notification is generated when the OES chassis in a PSS32 shelf requires high speed fan (FAN32H), but the fan inserted is not the right type. [EFFECT] The OES chassis is not operating with required fan type. [RECOVERY] Replace the OES fan unit with the correct one for 1830 PSS32 shelf.

[CAUSE] The tmnxOesFan32HReqdClear notification is generated when the OES chassis is equipped with FAN32H or when the alarmed fan unit with tmnxOesFan32HReqd condition is removed from the slot. [EFFECT] The OES chassis is operating with required fan type for 1830 PSS32 shelf (FAN32H), or the incorrect fan unit has been removed. [RECOVERY] No recovery required.

[CAUSE] The tmnxOesFanFailure notification is generated when the fan unit in an OES chassis has failed. tmnxOesNotifyFailureReason contains the reason for fan failure. [EFFECT] The fan unit in the OES chassis is out of service. [RECOVERY] If the condition causing fan failure can not be removed, replace the faulty fan unit.

[CAUSE] The tmnxOesFanFailureClear notification is generated when fan failure in an OES chassis is cleared. tmnxOesNotifyFailureReason contains the reason for fan failure being cleared. [EFFECT] The fan unit in the OES chassis is in service. [RECOVERY] No recovery required.

[CAUSE] The tmnxOesPowerSupplyRemoved notification is generated when an OES power supply unit is removed from its slot in the OES chassis. [EFFECT] The power supply unit is not present in the indicated OES chassis slot. [RECOVERY] Insert OES power supply unit into its slot.

[CAUSE] The tmnxOesPowerSupplyInserted notification is generated when the OES power supply unit is inserted into its slot in the OES chassis. [EFFECT] The indicated slot of the OES chassis is now equipped with the power supply unit. [RECOVERY] No recovery required.

[CAUSE] The tmnxOesPowerSupplyFailure notification is generated when the power supply unit in the indicated slot of the OES chassis has failed. tmnxOesNotifyFailureReason contains the reason for the failure. [EFFECT] The indicated OES power supply unit is out of service. [RECOVERY] If the condition causing the power supply failure can not be removed, replace the faulty power supply unit.

[CAUSE] The tmnxOesPowerSupplyFailureClear notification is generated when the power supply failure in the indicated slot of the OES chassis is cleared. tmnxOesNotifyFailureReason contains the reason for the power supply failure being cleared. [EFFECT] The indicated power supply unit in the OES chassis is in service. [RECOVERY] No recovery required.

[CAUSE] The tmnxOesPortError notification is generated when an error condition listed in tmnxOesPortNotifyError is detected on the OES port. [EFFECT] The OES port is experiencing errors that could be service affecting. [RECOVERY] tmnxOesPortError is cleared by taking the port out of service, eg. shutdown, or try a soft reset, hard reset, then replacement of the card if the error condition persists.

[CAUSE] The tmnxOesPortErrorClear notification is generated when all error conditions on the OES port are cleared. [EFFECT] The OES port error conditions are cleared. [RECOVERY] No recovery required.

[CAUSE] The tmnxOesCtlCardActivityChange notification is generated when the active Equipment Controller has changed to the card specified by the tmnxHwIndex. [EFFECT] The active Equipment Controller has moved to the previously standby card. [RECOVERY] No recovery is required.

[CAUSE] The tmnxOesFpgaFail notification is generated during an out-of-service upgrade when the FPGA file downloaded to the card was corrupt or the FPGA failed to program correctly. [EFFECT] The OES card shall automatically cold reboot and the card shall attempt to recover. While the condition exists the card remains out-of-service. [RECOVERY] If the card has rebooted and the condition did not clear, then first reseat the card and see if the condition clears. If the condition remains, then replace the card and follow the return and repair process for the problem card.

[CAUSE] The tmnxOesFpgaFailClear notification is generated when the FPGA is successfully programmed. [EFFECT] The FPGA is successfully programmed. [RECOVERY] No recovery is required.

[CAUSE] The tmnxOesFpgaTimeout notification is generated when the FPGA file download and reprogramming took longer than expected (about 45 minutes). [EFFECT] The FPGA on the indicated card was not reprogrammed in the time window. [RECOVERY] If the OES card is operational, wait for a maintenance window and reset the OES card.

[CAUSE] The tmnxOesFpgaTimeoutClear notification is generated when the OES FPGA timeout condition is cleared. [EFFECT] The FPGA is successfully programmed. [RECOVERY] No recovery is required.

[CAUSE] The tmnxOesOptTrnspndrMiscFail notification is generated when a non-service affecting hardware defect is detected on the card. This condition may be declared on the card due to one of the following causes: 1) Detection of line side transmitter laser bias or optical output power nearing end-of-life. 2) Detection of line receiver ITLA (Integrated Tunable Laser Assembly) laser bias or output power nearing end-of-life. 3) Detection of board-level Analog-to-Digital Conversion Digital Signal Processor (ADC DSP) device defect. 4) A device-to-device interface communication problem. [EFFECT] The tmnxOesOptTrnspndrMiscFail alarm indicates a lower priority fault on the card that does not directly affect the traffic currently flowing through the card. However, the card should be replaced at the next available maintenance opportunity. [RECOVERY] Replace the card.

[CAUSE] The tmnxOesCardDegraded notification is generated when a fault on the card has caused the system to declare a hardware failure. This condition may be declared due to a failure in the SEEP or another hardware failure, depending on the card type the alarm is raised against. [EFFECT] The tmnxOesCardDegraded alarm indicates a lower priority fault on the card that does not directly affect the traffic currently flowing through the device. [RECOVERY] First attempt a soft reset of the card. If the card has rebooted and the condition does not clear, then try a hard reset of the card. If the card has rebooted and the condition does not clear, then remove the card and re-insert it to see if the condition clears. If the condition remains, then replace the card and follow the return and repair process for the problem card.

[CAUSE] The tmnxOesFanSpeedHigh notification is generated when the fan speed is too high, based upon the current shelf cooling requirements. [EFFECT] The fans run faster than required. [RECOVERY] Remove and re-insert the fan tray into the chassis. If the alarm does not clear then replace the fan tray.

[CAUSE] The tmnxOesFanSpeedHighClear notification is generated when the conditions causing a tmnxOesFanSpeedHigh notification have been cleared. Fan speed has returned to acceptable conditions. [EFFECT] The fan speed is normal. [RECOVERY] No recovery is required.

[CAUSE] The tmnxOesFanSpeedLow notification is generated when the fan speed is too low, based upon the current shelf cooling requirements. [EFFECT] The fans run slower than required. [RECOVERY] Check for airflow blockage or a dirty filter, and clear. If no problems are found, replace the fan tray.

[CAUSE] The tmnxOesFanSpeedLowClear notification is generated when the conditions causing a tmnxOesFanSpeedLow notification have been cleared. Fan speed has returned to acceptable conditions. [EFFECT] The fan speed is normal. [RECOVERY] No recovery is required.

[CAUSE] The tmnxOesTempLow notification is generated when the card has detected its temperature is below operational limits. [EFFECT] The card performance may degrade or may not work as expected. [RECOVERY] Ensure that no environmental issues exist where the network element resides. Resolve any existing issues.

[CAUSE] The tmnxOesFanSpeedLowClear notification is generated when the card has indicated its temperature is within operational limits. [EFFECT] The card resumes normal operation state. [RECOVERY] No recovery is required.

[CAUSE] The tmnxOesRedundancyFail notification is generated when the inactive equipment controller card in the OES is not providing redundancy protection. In some cases this is a transitory alarm that occurs as redundant Equipment Controllers discover one another and synchronize. Typical causes for the persistence of this alarm are: 1) Irreconcilable database schemas. 2) Inability to support system timing. 3) System timing is compromised. The inactive controller system timing module is not reporting the same status as the active controller or is reporting an error that the active controller does not have. 4) Subshelf link missing. Reasons that are generally transitory are: 1) Database not yet fully synchronized. 2) Software loads are not yet synchronized. Some or all of these may apply when the alarm is raised. [EFFECT] The OES is not protected against failure of the active Equipment Controller. [RECOVERY] Check for the Redundancy demerit in the detailed information of the chassis indicated.

[CAUSE] The tmnxOesRedundancyReady notification is generated when the equipment controller cards in the indicated OES chassis are providing redundant protection. The equipment controller cards are synchronized. [EFFECT] The equipment controller cards are synchronized. [RECOVERY] No recovery is required.

[CAUSE] The tmnxOesCardFirmwareErr is raised when the device installed in the shelf has an EEPROM that does not contain the correct or recognizable information. [EFFECT] The card may demonstrate other alarms due to this condition. [RECOVERY] Replace the card.