[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 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 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 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 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 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.

[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.