Procedure 5-87: Clear "NVM" alarms

- Overview

This procedure is used to clear the following alarms:

  • NVM failed

  • NVM removed or NVM failed

Important!

Performing this procedure under the following scenarios may cause transmission losses and/or require a restore from a remote backup file.

  • While the SYSCTL is removed, DO NOT remove or replace either Main circuit pack (M1, M2).

  • If an equipped Main (M1 or M2) is removed from the NE, DO NOT replace the SYSCTL.

- Before you begin

Prior to performing this procedure:

  1. Refer to Before you begin and Required equipment in this chapter.

  2. Refer to Laser safety and Electrostatic discharge in Chapter 1, Safety.

  3. If field replacement of NVM modules is allowed, obtain the necessary factory-supplied replacement NVM modules.

    Factory-supplied replacement NVM modules are correctly formatted; NVMs supplied with an LNW2 have "factory-fresh" software to support maintenance mode.

  4. If field replacement of NVM modules is not allowed, obtain a replacement LNW2 SYSCTL circuit pack with "factory-fresh" NVM modules.

Steps

Complete the following steps to clear an NVM-related alarm.

 
1

From the WaveStar® CIT System View,

  • Click the Alarm List button and locate the NVM-related alarm in the resulting alarm list and note the corresponding AID of the failed/missing NVM module.

  • Select View ⇒ Software Generic and record the Active Generic Release from the window and the TID from the title bar.

2

Important!

When a failed/missing NVM module is detected, automatic writes to the NVM modules are stopped. Any database changes made after a failed/missing NVM module is detected are stored only in volatile memory.

If field replacement of NVM modules is not allowed or if both NVM modules are failed/missing, it is recommended that the network element database be backed up to a remote OS (for example, OMS). This creates a current backup copy of the database that includes all database changes made after a failed/missing NVM module is detected. This backup copy may be used to restore the network element database.

If required, back up the network element database using the Configuration → Software → Remote Backup command.

Reference:

3

Important!

If field replacement of NVM modules is allowed and only one NVM module is failed/missing, it is recommended that the OPR-NVM TL1 command be used to write database changes to the remaining NVM module.

If both NVM modules are failed/missing, the OPR-NVM TL1 command is denied. The database changes made after a failed/missing NVM module is detected will not be written on the NVM modules.

If required, perform the following to access the TL1 Cut Through Mode and execute the OPR-NVM TL1 command.

  1. From the WaveStar® CIT System View, select File → NE Disconnect and click Yes in the resulting confirmation window.

  2. From the Network View, log back into the NE but this time click TL1, not Graphical.

  3. Select the Cut Through Execution Mode and click OK.

  4. Enter your user ID and password. Defaults are LUC01 and DMXTND2.5G, respectively.

  5. Execute the OPR-NVM TL1 command until a COMPLD response is received.

Result:

This causes the database changes made after a failed/missing NVM module is detected to be written on the remaining NVM module, if possible.

Reference:

Alcatel-Lucent 1665 Data Multiplexer Extend (DMXtend) TL1 Message Details, 365-372-328

4

Important!

If field replacement of NVM modules is allowed, observe the IND display on the SYSCTL circuit pack faceplate before removing the SYSCTL circuit pack from the shelf. N01 indicates the NVM-1 module failed, and N02 indicates the NVM-2 module failed.

Remove the SYSCTL circuit pack from the shelf.

Reference:

Procedure 6-10: Upgrade or replace SYSCTL (LNW2) circuit pack

5

If field replacement of NVM module is...

Then...

allowed,

single failed NVM

Obtain the necessary factory-supplied replacement NVM module and replace the required failed/missing NVM module in the SYSCTL circuit pack.

double failed NVMs

If both NVMs are replaced with factory-supplied replacement NVM modules, the SYSCTL IND displays E10. E10 indicates that there is no software from which to boot.

In the case of double failure, refer to Procedure 6-10: Upgrade or replace SYSCTL (LNW2) circuit pack.

not allowed,

Obtain a replacement LNW2 SYSCTL circuit pack with factory-fresh NVM modules.

6

Install the SYSCTL circuit pack.

Result:

If a valid generic and/or database is not found when the SYSCTL circuit pack starts up, the network element enters the Maintenance Mode state and the IND display on the SYSCTL circuit pack faceplate shows MPx.x (where x.x is the generic number).

If in Maintenance Mode, continue with Step 7.

If NOT in Maintenance Mode, proceed to Step 9.

Reference:

Procedure 6-10: Upgrade or replace SYSCTL (LNW2) circuit pack

7

Important!

In the Maintenance Mode state, the default User IDs/passwords must be used to login to the network element. LUC01, LUC02, and LUC03 are the default privileged User IDs, and DMXTND2.5G is the default privileged password.

Log in to the network element.

Result:

If the network element is in the Maintenance Mode state, the Maintenance Mode Wizard appears.

Reference:

Procedure 6-2: Connect Personal Computer (PC) and establish WaveStar® CIT session

8

If required, perform the following to choose/download and install the required valid generic and database using the Maintenance Mode Wizard.

  1. Follow the Maintenance Mode Wizard (Screen 1 of 4) instructions to set the date and time and click Next.

  2. Follow the Maintenance Mode Wizard (Screen 2 of 4) instructions to choose or download the correct generic on the NVM that was not replaced (as noted in Step 1) and click Next. Downloading a different generic is not an in-service procedure.

  3. Follow the Maintenance Mode Wizard (Screen 3 of 4) instructions to verify the TID (as noted in Step 1) and choose or download the current database on the NVM that was not replaced and click Next. Selecting the default database will interrupt service

  4. Follow the Maintenance Mode Wizard (Screen 4 of 4) instructions and verify that the correct generic and database were selected. Then click Finish.

Note:

If the correct generic and current database are chosen, the circuit packs will not experience any downloads or service interruptions.

Result:

The system resets and you are logged off the system.

A flashing b in the IND display on the SYSCTL indicates that a boot is in progress. During the boot, the b may extinguish for up to 20 seconds and then resume flashing.

Reference:

9

Important!

If a default database was selected/installed, the default User IDs/passwords must be used to log in to the network element. LUC01, LUC02, and LUC03 are the default privileged User IDs, and DMXTND2.5G is the default privileged password.

If a valid (non-default) database was selected/installed, the provisioned User IDs/passwords may be used to log in to the network element.

If required, log back into the network element when the system reset is complete.

Reference:

Procedure 6-2: Connect Personal Computer (PC) and establish WaveStar® CIT session

10

If a default database was selected/installed using the Maintenance Mode Wizard, restore the most recent network element database using the Configuration → Software → Remote Restore command.

Reference:

11

From the WaveStar® CIT System View, click the Alarm List button and click Refresh.

Result:

The NVM alarms are no longer present.

End of steps

November 2011Copyright © 2011 Alcatel-Lucent. All rights reserved.