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

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

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

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

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

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

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

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

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

 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.

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

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

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

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

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

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