SONET Transmission Products S/DMS TransportNode …npatrick/nortel-sdms-docs/N3S2N3GW.pdf · SONET...

NT7E65DJ 323-1111-303

SONET Transmission Products

S/DMS TransportNodeOC-3/OC-12 NE TBM

Software Administration Procedures

Standard Rel 14 February 2001

Whats inside...

Software administration overviewLoading software on a spare OPCRebooting and loading network element softwareUpgrading network element and OPC softwareDelivering OPTera Metro 3000 network element softwareTransport bridging between TL1 MOA and OPTera Metro 3000Managing baseline hardware release information

Copyright

19922001 Nortel Networks, All Rights Reserved

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Nortel Networks and S/DMS TransportNode are trademarks of Nortel Networks. VT100 is a trademark of Digital Equipment Corporation. UNIX is a trademark of X/Open Company Ltd.

Printed in Canada

iii

ContentsAbout this document vReferences in this document v

Software administration overview 1-1

Loading software on a spare OPC 2-1Restrictions and limitations 2-2Chapter task list 2-3

Initializing the OPC hard disk (OPC equipped with a tape or cartridge drive) 2-3Removing the existing software load (OPC equipped with a tape or cartridge

drive) 2-3Removing the existing software load (OPC not equipped with a tape or cartridge

drive) 2-3

List of procedures2-1 Verifying the software release of the spare OPC 2-42-2 Initializing the OPC hard disk 2-82-3 Removing a software load from a spare OPC equipped with a tape or

cartridge drive 2-152-4 Installing software on a spare OPC equipped with a tape or cartridge

drive 2-192-5 Removing a software load from a spare OPC not equipped with a tape or

cartridge drive 2-232-6 Installing a software load on a spare OPC not equipped with a tape or

cartridge drive 2-29

Rebooting and loading network element software 3-1Software releases and firmware loads 3-1Software reboots 3-2Chapter task list 3-2

List of procedures3-1 Sending new software to a shelf processor 3-33-2 Querying the current software release on the OPC or network element 3-7

Upgrading network element and OPC software 4-1Electronic software delivery over FTAM 4-2Network Upgrade Manager tool 4-2

Software Administration Procedures 323-1111-303 Rel 14 Standard Feb 2001

iv

Contents

Delivering OPTera Metro 3000 network element software 5-1Handling and storing digital data storage tapes 5-2Software cartridges 5-2Tool restrictions 5-2Chapter task list 5-2

List of procedures5-1 Transferring a load from tape or cartridge to disk (OPTera Metro 3000 series

only) 5-35-2 Deleting a load from the local OPC (OPTera Metro 3000 series only) 5-65-3 Viewing the OPTera Metro 3000 series software load (on tape, cartridge or

disk) 5-7

Transport bridging between TL1 MOA and OPTera Metro 3000 6-1Transport Bridge (TPB) 6-1Chapter task list 6-2

List of procedures6-1 Listing existing OPC TPB commissioning information 6-36-2 Modifying or adding OPC TPB commissioning information 6-6

Managing baseline hardware release information 7-1Chapter task list 7-3

List of procedures7-1 Checking the product engineering code (PEC) and hardware release on

circuit packs 7-47-2 Modifying the hardware baseline 7-87-3 Scheduling or disabling the hardware baseline audit 7-13

S/DMS TransportNode OC-3/OC-12 NE TBM Vol 4 323-1111-303 Rel 14 Standard Feb 2001

v

About this documentThis document is for software administrators who are administering software for both the operations controller (OPC) and the network elements in an S/DMS TransportNode OC-3/OC-12 system.

This document is structured as follows:

Chapter 1 gives an overview of software administration.

Chapter 2 contains procedures for loading the current software release on a spare OPC that is equipped with a tape drive.

Chapter 3 contains procedures that use the Reboot/Load Manager tool to download software to any network element in the OPC span of control.

Chapter 4 describes the Network Upgrade Manager tool that you use to upgrade software for some or all network elements in an OPC span of control. Procedures for using this tool are covered by a separate Change Application Procedure (CAP).

Chapter 5 contains procedures that use the OC-3 Load Manager tool of the operations controller (OPC) to manage Express network element loads.

Chapter 6 contains procedures that use the OPC OC-3 TPB Config tool to manage services that exist between the TL1 MOA and the Express network processor (NP).

Chapter 7 contains procedures that use the Hardware Baseline tool to manage baseline hardware release information.

References in this documentThis document refers to the following documents:

About the OC-12 NE Library, 323-1111-090

Ordering Information, 323-1111-151

Commissioning Procedures, 323-1111-220

System Testing Procedures, 323-1111-222

User Interfaces Description, 323-1111-301

System Administration Procedures, 323-1111-302

Provisioning and Operations Procedures, 323-1111-310


vi

About this document

Alarm Clearing Procedures, 323-1111-543

Recovery Procedures, 323-1111-545

Routine Maintenance Procedures, 323-1111-546

Log Report Manual, 323-1111-840

Common Procedures, 323-1111-846


1-1

Software administration overview 1-This chapter provides an overview of software administration in S/DMS TransportNode OC-3/OC-12 systems.

Operations controller (OPC) software and network element (NE) software are administered independently, and are described in different chapters in this document. For a full set of procedures, contact Nortel Networks Technical Assistance for a copy of the appropriate software upgrade Change Application Procedure (CAP).

Network element software is designated by release (such as OC-12 Rel 9 for the OC-12 product) and by load (a version of software for a given release). One release can have a number of different loads. For example, OC-12 Rel 9 contains the following loads: OPCAL16xx, HMU09xx and TBM14xx. (OPCAL16xx is the OPC load, HMU09xx is the HMU processor load, and TBM14xx is the APU processor load, where xx is a version code.)

Chapter 2- Loading software on a spare OPC, describes the procedures for loading the current software release on a spare OPC. These procedures can be done by either initializing the OPC hard disk or removing the OPC load, and then installing the new software load.

Chapter 3- Rebooting and loading network element software, describes the Reboot/Load Manager tool used to download software to any network element in the OPC span of control. The Reboot/Load Manager is also used to define which software load is sent to each network element

Chapter 4- Rebooting and loading network element software, introduces the Network Upgrade Manager tool, that allows you to upgrade software for some or all network elements in an OPC span of control. Procedures for using the tool are not contained in the NTPs. Instead, contact your next level of support or your Nortel Networks support group for the appropriate Change Application Procedure (CAP) for your system.


1-2

Software administration overview

Chapter 5- Delivering OPTera Metro 3000 network element software, describes the managing of Express network element loads using the OC-3 Load Manager tool of the operations controller (OPC).

Chapter 6- Transport bridging between TL1 MOA and OPTera Metro 3000, describes the management services that exist between the TL1 MOA and the Express network processor (NP). The NP acts as a gateway for the TL1 MOA allowing access to the Express network elements.

Chapter 7- Managing baseline hardware release information, describes the hardware release baseline file. This file specifies the circuit packs supported in a release by product engineering code (PEC) and baseline number (hardware release number).


2-1

Loading software on a spare OPC 2-This chapter describes how to install the current software release on a spare operations controller (OPC). You can install the software in either of the following ways:

Initialize the spare OPC hard disk and then install the new release.

As the root user, remove the existing software release with the rmopcld command, and then install the new release.

The disk initialization process involves overwriting the current software release and UNIX base loads. You overwrite the loads by reformatting the disk and installing a new UNIX base load.

CAUTIONRisk of destroying dataThe OPC software installation procedure completely redefines the contents of the disk.The OPC loses all the information currently on the disk. Before beginning the procedures in this chapter, back up all OPC data to tape or cartridge (see Data Administration Procedures, 323-1111-304).

CAUTIONRisk of software load corruptionNortel Networks recommends that you install the current software release on spare OPCs only when you need to use the spare OPCs immediately. Software on a spare OPC left sitting for a long period of time can become corrupt.

CAUTIONRisk of damaging circuit packsElectrostatic discharge can damage electrostatic-sensitive devices. Always ground yourself before handling the OPC or any other circuit pack.


2-2

Loading software on a spare OPC

Handling and storing digital data storage Keep digital data storage (DDS) away from moisture, extreme hot and cold temperatures, and magnetic fields and devices.

Handle DDS tape carefully. Electrostatic discharge can damage DDS tapes. Always ground yourself before handling the tape.

For solid-state cartridges, always ground yourself before inserting the cartridges into the OPC, as you will be in contact with the network element.

Restrictions and limitationsYou must understand and meet the following requirements and limitations before you attempt to perform the procedures in this chapter:

Do not attempt these procedures unless you are familiar with the OPC and the network element interfaces.

Inform all OPC users and surveillance personnel before you initialize the OPC disk.

You must have the password for the root userID for the OPC before you start the installation.

Enter the UNIX commands exactly as shown in the procedures. UNIX commands are case sensitive (UPPER CASE, lower case).

The default SCSI ID is 1. Do not change it.

The disk initialization procedures apply to all S/DMS TransportNode OPCs equipped with a tape drive and a minimum firmware release of OPCREL02 (NT8E2460 Rel. 04). The OPCs with the following PEC codes satisfy these criteria:

NT7E24BA Rel. 15 and higher

NT7E24BC Rel. 1 and higher

NT7E24CA Rel. 8 and higher

NT7E24CC Rel. 1 and higher

Note: You can find the PEC codes and release numbers of the OPC by removing the cover of the OC-12 shelf that contains the OPC. Then check the faceplate of the OPC.

The disk initialization procedures also apply to S/DMS TransportNode OPCs equipped with a cartridge drive.

NT7E24FA



2-3

Chapter task listInitializing the OPC hard disk (OPC equipped with a tape or cartridge drive)

Perform the following tasks, in the order shown, to install the current software release on a spare OPC (equipped with a tape or cartridge drive) when the spare OPC firmware supports the disk initialization process (see the Restrictions and limitations section at the beginning of this chapter) and you have the disk initialization tape or cartridge.

Removing the existing software load (OPC equipped with a tape or cartridge drive)

Perform the following tasks, in the order shown, to install the current software release on a spare OPC (equipped with a tape or cartridge drive), either when the spare OPC firmware does not support the disk initialization process (see the Restrictions and limitations section at the beginning of this chapter) or when you do not have the disk initialization tape or cartridge.

Removing the existing software load (OPC not equipped with a tape or cartridge drive)

Perform the following tasks, in the order shown, to install the current software release on a spare OPC not equipped with a tape or cartridge drive.

Task Page

Initializing the OPC hard disk 2-8

Installing software on a spare OPC equipped with a tape or cartridge drive

2-19

Task Page

Verifying the software release of the spare OPC 2-4

Removing a software load from a spare OPC equipped with a tape or cartridge drive

2-15

Installing software on a spare OPC equipped with a tape or cartridge drive

2-19

Task Page

Verifying the software release of the spare OPC 2-4

Removing a software load from a spare OPC not equipped with a tape or cartridge drive

2-23

Installing a software load on a spare OPC not equipped with a tape or cartridge drive

2-29


2-4


Procedure 2-1Verifying the software release of the spare OPC

Use this procedure to determine if the current software load can be installed on the spare operations controller (OPC).

Table 2-1 lists the upgrade support based on the OPC software version and software release.

continued

Table 2-1Upgrade support based on OPC software version & software release

Replacement OPC software version

PEC code Corresponding software release

Upgrade to Release 14 supported?

OPCAL04DM2 NT7E85BA OC12 TSS 4.00 yes (see Note 1)

OPCAL0AEC NT7E85BB OC12 TSS 4.01 yes (see Note 1)

OPCAL08BD NT7E85EA OC12 TSS 5.00 yes (see Note 1)

OPCAL04DM2 NT7E85CA OC3/12 TBM 4.00 yes (see Note 1)

OPCAL04EC NT7E85CC OC3/12 TBM 4.01 yes (see Note 1)

OPCAL04EC NT7E85CD OC3/12 TBM 4.21 yes (see Note 1)

OPCAL04EE NT7E85CE OC3/12 TBM 4.31 yes (see Note 1)

OPCAL08BD NT7E85DA OC3/12 TBM 5.00 yes

OPCAL09AZ NT7E85FA OC3/12 TBM 6.01 yes

OPCAL11AW NT7E85GB OC3/12 TBM 7.10 yes

OPCAL13BC NT7E85HB OC3/12 TBM 8.10 yes

OPCAL16BH NT7E85JA OC3/12 TBM 9.01 yes

OPCAL17BM NT7E85KA OC3/12 TBM 10.03 yes

OPCAL18CO NT7E85LC OC3/12 TBM 11.2 yes

Note 1: The system supports an upgrade to Release 14 provided you initialize the disk.

Note 2: If the replacement OPC has a software release of 8.10 or earlier and is not equipped with a tape or cartridge drive, you cannot upgrade the load on the replacement OPC. You cannot use this OPC as a replacement in the system. Return the OPC to Nortel Networks for reprogramming.



2-5

Procedure 2-1 (continued)Verifying the software release of the spare OPC

If the replacement OPC has a software version not listed in the preceding table, the system supports an upgrade to the current software release under the following conditions:

if the OPC software version is of the form OPCALxxyy

Note: The preceding recommendation is a general guideline only.

RequirementsBefore starting this procedure, you must:

obtain the slat and root userIDs and passwords for the OPC

have a VT100-compatible terminal

read the command conventions for the type of interface you are using (CMT or graphical) in Common Procedures, 323-1111-846

Use step 1 through step 12 determine the software load currently installed on the spare OPC. If you already know what release is installed on the spare OPC, go to step 13.

continued

where

xx is a two digit number greater than or equal to 16yy is any combination of alphabetic characters


2-6



Action

Step Action

Determining the OPC software version on the spare OPC

1 Insert the spare OPC into any available shelf that has no OPC installed.

2 Connect a VT100-compatible terminal to the OPC port 1 of the shelf housing the spare OPC.

3 Log in to the spare OPC using the root userID and password.

If you do not know how to do this, see the procedure in Common Procedures, 323-1111-846Common Procedures, 323-1111-846.

TERM=(vt100) appears.

4 Press the Return key.

The opc> prompt appears. If the OPC prompt does not appear, this OPC has failed and cannot be used to install the current software. Insert another OPC in the shelf and go to step 2.

5 Display the User Session Manager. Enter:

opcui

6 At the opc> prompt enter:

ll /iwsThe message /iws not found appears, then the opc> prompt appears.

7 Physically remove the OPC from the shelf.

8 Continue with the procedure to remove the OPC load, using disk initialization or the software tape or cartridge of the load you want to install on the spare OPC.

You have completed this procedure.

9 Tab to the Open tools list and use the arrow keys to move to the OPC Status tool. Select the tool. Press Ctrl_A (or Keypad 0).

The OPC status window appears.

10 Record the contents of the SW Version field. continued

If the User Session Manager

Then

appears go to step 9

does not appear one of the following messages appears:

/iws/usm/usmstart: Command not found. opcui: Command not found.

Go to step 6.


Loading software on a spare OPC 2-7


Step Action

11 Display the User Session Manager. Press Ctrl_T 0.

The User Session Manager appears.

12 Shut down the spare OPC using the Halt option on the OPC Shutdown tool and physically remove the OPC from the shelf.

If you do not know how to do this, see the procedure in Common Procedures, 323-1111-846.

Determining whether the release can be installed on the spare OPC

13 Depending on the software release originally installed on the spare OPC, you recorded either the OPC software version, or the software release in step 10. An OPC software version is of the form OPCALxxyy, where xx is a two digit number and yy is any combination of alphabetic characters. A software release lists the product name and the release number (for example, OC-3/OC-12 TBM Rel. 9.01).

From the recorded information determine whether the upgrade of the spare OPC is supported referring to Table 2-1.

end


2-8 Loading software on a spare OPC

Procedure 2-2Initializing the OPC hard disk

Use this procedure to initialize the operations controller (OPC) hard disk or solid-state drive using a disk initialization tape or cartridge. This initialization can be done when the OPC firmware supports the disk initialization process (see the Restrictions and limitations section at the beginning of this chapter) and when you have the disk initialization tape or cartridge.

Note: Once the disk initialization process has started, it cannot be aborted.

Requirements Before starting this procedure, you must:

have a spare OPC equipped with a tape or cartridge drive

Note: An OPC module already commissioned for another span of control (SOC) within the same system must be decommissioned before starting this procedure. If you do not know how to do this, see the procedure in Commissioning Procedures, 323-1111-220.

ensure that an NT7E44RA or RB cable is connected between a VT100- compatible terminal and the OPC port 1 (LTE)

ensure that an NT7E44FA or FB cable is connected between a VT100-compatible terminal and the network element port 2 (only if you need to log into the OPC through the local NE)

have one copy of the disk initialization tape or cartridge (DDS tape or cartridge) NT7E86BT 0101, Boot Tape Release 1.00

have a TBM shelf with no OPCcontinued

CAUTIONRisk of destroying dataThe disk initialization process completely redefines the contents of the disk. Any information currently on the disk is lost. Before beginning the procedures in this chapter, make sure all OPC data is backed up to tape or cartridge.

CAUTIONRisk of damaging circuit packsElectrostatic discharge can damage electrostatic-sensitive devices. Always ground yourself with an antistatic wrist strap before handling the circuit pack.



Procedure 2-2 (continued)Initializing the OPC hard disk

obtain root access to the OPC and admin level access to the local network element

know the name of the OPC undergoing the disk initialization

observe the Restrictions and limitations section at the beginning of this chapter


Action

Step Action

1 If it has not already been done, insert the OPC into any OC-3/OC-12 shelf that does not currently have an OPC installed.

The OPC login prompt appears after several minutes.

2 After the login prompt appears, insert the disk initialization tape or cartridge in the OPC tape or cartridge drive. The tape must be inserted with the white latch facing you. The latch is located on the upper half of the tape when it is being inserted. If the OPC is equipped with a cartridge drive, insert the cartridge with the Nortel Networks logo facing toward the left.

The green LED on the tape or cartridge drive comes on, indicating that there is a tape or cartridge in the tape or cartridge drive.

3 Attempt to log in to the OPC.

4 Log in to the OPC using the root userID and password.

If you do not know how to do this, see the procedures in Common Procedures, 323-1111-846.


5 Press the Return key and go to step 7.

The opc> prompt appears.

continued

If the login prompt Then

appears go to step 4

not appear ensure that the VT100-type terminal is set up correctly. If the setup is incorrect and the login prompt now appears, go to step 4. If the login prompt still does not appear, go to step 6.




Step Action

6 Try to access the OPC from the local network element in which the OPC is inserted.

a. Connect an NT7E44FA or FB cable to the 25-pin RS-232 connector of the local craft access panel (LCAP) at the top of the shelf.

b. Connect the other end of the cable directly to the VT100-type terminal to be used for the network element user interface.

c. Press the Break key.

The prompt ? appears.

d. Enter the command:

login e. Log in to the network element using the admin userID and password.

The network element user interface screen appears.

f. Remotely log in to the OPC. Enter:

rlogin

g. Log in to the OPC using the root userID and password.

7 Open the User Session Manager. Enter:

opcui The User Session Manager appears.

If the User Session Manager does not appear, go to step 9.

continued

where

is the name of the OPC you are initializing

If the remote login attempt Then go to

is successful and the opc> prompt appears step 7

is unsuccessful step 9




Step Action

8 Perform an OPC shutdown using the Restart option.


The OPC boots from the disk initialization tape or cartridge. After several minutes, the login prompt appears.

Note: Ignore the red FAIL LED on the OPC if it lights up. The LED lights up because the OPC resides in a network element shelf that it cannot communicate with (the network element has not been commissioned in the OPC).

Go to step 10.

9 Read this caution before you remove the OPC from the shelf.

Physically remove the OPC from the shelf. Wait 30 seconds and then reinsert the OPC.

The OPC boots from the disk initialization tape or cartridge. After several minutes, the login prompt appears.

Note: Ignore the red FAIL LED on the OPC, if it lights up. The LED lights up because the OPC resides in a network element shelf that it cannot communicate with (the network element has not been commissioned in the OPC).

10 At the login prompt (login:), log in to the OPC.

a. Enter the userID:

opc You are prompted to enter the password.

b. Enter the password:

cpo continued

CAUTIONRisk of damaging the OPC hard diskIf a proper shutdown is not performed, physical damage can occur on the OPC. A physical fault on the hard disk is unrecoverable using the disk initialization process. Do not perform this step if a proper shutdown can be initiated from the User Session Manager.




Step Action

The OPC Disk Initialization menu appears.FW-21734 (R11 ph 1)

11 Initialize the disk. Enter:

i The following message appears.

About to initialize disk with SCSI ID 1, ok? [y/n] ->

continued

OPC Disk Initialization Ver. 2 ===============================

Current SCSI ID is 1

S - Select a SCSI ID for disk initialization

I - Initialize the disk

R - Reboot from disk

D - Display disk vendor/model information

H - Help information

Q - Quit

Please enter response > _

FW-21734(R11 ph1)




Step Action

12 Confirm the hard disk initialization. Enter:

y Progress messages similar to the following may appear. These messages can be ignored.

Executing: GetTapeID...

SCSI 011> Open: Requested device ID - 0 - not availableSCSI 011> Open: Requested device is not of expected typeSCSI 011> Open: Encountered device type - 0

Executing: GetNoBasesys 2

After the progress messages, the following message appears to determine which UNIX base software load (HP-UX 6.5 or HP-UX 8.0) needs to be installed on the OPC.

OC3 5.00OC12 5.00RNL08AN07

Is your software release prior to a release in the above list? [y/n] ->

Note: Enter n in step 13 if your software release is after the releases shown in the list. Enter y in step 13 if your software release is before those shown or is in the list.

13 Install HP-UX 8.0 UNIX base load. Enter:

n The following message appears, indicating which UNIX base load is about to be installed.

About to install opc_basesys80.tar...

The disk initialization process begins and takes about 10 minutes to complete. A long series of initialization messages appear on the screen, describing what is happening in the initialization process. After the final message appears, you are prompted to press the Return key.


The Disk Initialization menu appears.

15 Select the Reboot from disk option from the menu. Enter:

r The following message appears.

About to reboot from disk, ok? [y/n] ->

continued




Step Action

16 Confirm that you want to reboot the OPC from the OPC hard disk. Enter:

y The OPC reboot takes approximately 5 minutes to complete. Messages like the following may appear. The messages can be ignored.

Executing: GetTapeID...SCSI 011> open: Requested device ID - 0 - not availableSCSI 011> open: Requested device is not of expected typeSCSI 011> open: Encountered device type - 0

Ejecting Tape in device number 2.SCSI 011> Tape not ready - medium not present, device 2SCSI 011> Decode sense - Key 2, Code 3a, Qual 00, dev 2, cmd 01.Shutdown at 11:23 (in 0 minutes)

The OPC disk initialization tape is ejected. Store the tape for safekeeping. The disk initialization session is terminated and after a few minutes the login prompt appears.

17 If the OPC is equipped with a cartridge drive, manually eject the cartridge by pressing the button above the cartridge. The cartridge may be left in the cartridge drive or removed for storage.

end



Procedure 2-3Removing a software load from a spare OPC equipped with a tape or cartridge drive

Use this procedure to remove the software load from the spare operations controller (OPC), when the spare OPC is equipped with a tape or cartridge drive and when either the OPC firmware does not support the disk initialization process, or you do not have the disk initialization tape or cartridge.


have a spare OPC equipped with a tape or cartridge drive and that has been verified as compatible in accordance with the procedure Verifying the software release of the spare OPC on page 2-4

Note: An OPC module already commissioned for another span of control within the same system must be decommissioned before using it as a spare OPC. If you do not know how to do this, see the procedure in Commissioning Procedures, 323-1111-220.

obtain the root userID and password for the spare OPC

have a tape or cartridge containing the software release currently installed on the spare OPC


Note: In some of the following steps, you must execute UNIX commands. Type bold text exactly as shown at the opc> prompt. Press the Return key when you see the character.

ensure that an NT7E44RA or RE cable is connected between a VT100-compatible terminal and the OPC port 1 (LTE)

have a TBM shelf with no OPC

continued

CAUTIONRisk of damaging circuit packsElectrostatic discharge can damage electrostatic-sensitive devices. Always ground yourself before handling the circuit pack.



Procedure 2-3 (continued)Removing a software load from a spare OPC equipped with a tape or cartridge drive

Action

Step Action

1 If it has not already been done, insert the OPC into any OC-3/OC-12 shelf that does not currently have an OPC installed.






4 Insert the software tape or cartridge containing the load currently installed on the spare OPC into the OPC tape or cartridge drive. This tape or cartridge contains the rmopcld utility required to remove existing OPC software from the OPC. The tape must be inserted with the white latch facing you. The latch is located on the upper half of the tape when it is being inserted. If the OPC is equipped with a cartridge drive, insert the cartridge with the Nortel Networks logo facing toward the left.

5 Set the directory. Enter:

cd /tmp The opc> prompt appears.

6 Verify that the correct directory has been obtained. Enter:

pwd The following identifier appears. If this identifier does not appear, repeat step 5.

/tmp

7 Retrieve the rmopcld utility from the software tape or cartridge. Enter:

dd if=/dev/rdt/tape2 bs=20b | tar xvf - Each file appears as it is retrieved. The entire process can take up to 5 minutes. When the retrieval is complete, either the message Broken pipe or a message similar to the following appears.

439+4 records in 439+4 records out


Note 1: The numbers shown in the preceding message can vary.

Note 2: The message Broken pipe does not indicate a problem. Ignore this message and continue with this procedure.

continued




Step Action

8 Set the directory where the rmopcld utility was transferred. Enter:

cd /tmp/install The opc> prompt appears.

9 Verify that the correct directory has been set. Enter:


/tmp/install

10 Begin removing the software load from the spare OPC. Enter:

rmopcld A warning message, similar to the following, appears and you are prompted to confirm the removal of the OPC load.

************* WARNING *************

This tool removes the OPC load. If you choose to continue,ensure that the tool completes successfully before proceedingwith further operations.

Failure to do so could leave the OPC in an UNSTABLE state.

Do you want to remove the OPC load? (y/n)

11 Confirm the removal of the load. Enter:

y OPC processes are stopped.

continued

If the software load being removed is Then

release 7, or earlier a message appears, giving you the option of aborting the removal of the OPC load.Go to step 12.

release 8, or later the rmopcld utility removes the software load from the OPC. When the load is completely removed, the OPC reboots and the login prompt appears.Go to step 13.




Step Action

12 Continue removing the software load. Enter:

c The rmopcld utility removes the existing software load from the spare OPC. When the load is completely removed, the OPC reboots and the login prompt appears.

13 Eject the software tape from the tape drive and place it in a safe location. If the OPC is equipped with a cartridge drive, manually eject the cartridge by pressing the button above the cartridge. The cartridge may be left in the cartridge drive or removed for storage

end



Procedure 2-4Installing software on a spare OPC equipped with a tape or cartridge drive

Use this procedure to install the current software on the spare operations controller (OPC) either after the hard disk is initialized or after the existing software load is removed using the rmopcld utility.


successfully complete either Procedure 2-2, Initializing the OPC hard disk or Procedure 2-3, Removing a software load from a spare OPC equipped with a tape or cartridge drive

obtain a tape or cartridge containing the desired software load

observe the Restrictions and limitations section at the beginning of this chapter


have a TBM shelf with no OPC

Action

Step Action

1 Insert the current software tape or cartridge in the OPC tape or cartridge drive. The tape must be inserted with the white latch facing you. The latch is on the upper half of the tape when it is being inserted. If the OPC is equipped with a cartridge drive, insert the cartridge with the Nortel Networks logo facing toward the left.

2 Log in to the OPC using the root userID and password.


Note: After performing a disk initialization or a software load removal, the root password is reset to root.


continued



Procedure 2-4 (continued)Installing software on a spare OPC equipped with a tape or cartridge drive

Step Action



4 Set the directory. Enter:

cd /tmp The opc> prompt appears.



/tmp

6 Retrieve the Release Installation tool from the software tape or cartridge. Enter:

dd if=/dev/rdt/tape2 bs=20b | tar xvf - Each file appears as it is retrieved. The entire process can take up to 5 minutes. When the retrieval is complete, either the message Broken pipe or a message similar to the following appears.

439 + 4 records in439 + 4 records out


Note 1: The numbers shown in the preceding message can vary.

Note 2: The message Broken pipe does not indicate a problem. Ignore this message and continue with this procedure.

7 Set the directory where the Release Installation tool was transferred. Enter:


8 Verify that the correct directory has been set. Enter:


/tmp/install

continued




Step Action

9 Access the Release Installation tool by entering:

install_release The main screen of the utility appears.

10 Install the release by entering:

1 Various messages appear.

On the final message a prompt asks you to confirm the release installation on the local OPC.

11 Confirm the software installation by entering:

y The installation begins and release installation progress messages appear. At the end of the initialization, the OPC reboots. The current log-in session terminates, but the installation software automatically restarts after the OPC finishes rebooting.

continued

RELEASE INSTALLATION TOOL

Main Menu---------------1. Install release2. Query available release on removable media3. Query available release on disk4. Exit

Please enter the number of the operation to perform (1-4):_

Release installation

Release to install: OC-12 Rel xx.xxDestination OPC: Source: removable media

Do you want to proceed with this installation (Y/N)?_

--------------------------




Step Action

12 Wait at least 15 minutes after the reboot, then log in to the OPC using the userID root and the password root. For instructions, see Common Procedures, 323-1111-846.

The following screen appears.

13 To acknowledge the completion of the release installation, enter:

y TERM=(vt100) appears.


The prompt opc> appears.

15 Log out from the OPC. For instructions, see Common Procedures, 323-1111-846.

16 Remove the software tape or cartridge from the Primary OPC by pressing the small button beside the OPC tape or above the cartridge on the cartridge drive.

end

Use, duplication, or disclosure by the Government is subject to restrictionsas set forth in subdivision (b) (3) (ii) of the Rights in Technical Data and Computer Software clause at 52.227-7013.

RESTRICTED RIGHTS LEGEND

NORTEL NETWORKS

Welcome to FWUX on the Series.

************************************************************************************The installation of release OC-12 on the local opc OPC has completed. Please refer to Event Browser logs to make sure the installation was successful.************************************************************************************

Do you want to acknowledge the completion of the release installation?

Enter y to acknowledge the completion of the release installation and stop the above message from being displayed.Enter n to proceed with the normal login.=>_



Procedure 2-5Removing a software load from a spare OPC not equipped with a tape or cartridge drive

Use this procedure to remove the software load from a spare operations controller (OPC) when the spare OPC is not equipped with a tape or cartridge drive.


have a spare OPC not equipped with a tape or cartridge drive that has been verified as compatible in accordance with Procedure 2-1, Verifying the software release of the spare OPC

Note: An OPC module already commissioned for another span of control within the same system must be decommissioned before starting this procedure. If you do not know how to do this, see the procedure in Commissioning Procedures, 323-1111-220.

have a TBM shelf with no OPC where the shelf (that is NE) must be commissioned in a primary OPC span of control with this OPC active

ensure that an NT7E44RA or RB cable is connected between a VT100- compatible terminal and the OPC port 1 (LTE)

obtain the root userID and password for the primary and the spare OPC

have a tape or cartridge containing the software release that you want to install on the spare OPC


continued

CAUTIONRisk of damaging circuit packsElectrostatic discharge can damage electrostatic-sensitive devices. Always ground yourself before handling the circuit pack.



Procedure 2-5 (continued)Removing a software load from a spare OPC not equipped with a tape or cartridge drive

ActionStep Action

1

2 Log in to the OPC being replaced with root access privileges.

Note: If the existing OPC is not operable, contact your system administrator to obtain the IP address.

3 Identify the IP address of the existing OPC by entering the following commands at the UNIX prompt (opc>):

uname -a Characters similar to the following appear:

HP-UX one B.08.00 B 9000/399 b17e0113

The first word after HP-UX is the OPCs host name.

4 Record the OPCs host name, then enter it at the UNIX prompt as follows:

grep /etc/hosts The IP and hostname appear in that order.

5 Record the IP address to assign it when you initialize the OPC Ethernet port. For instructions, see Initializing the OPC Ethernet port in System Administration Procedures, 323-1111-302.

6 Record the serial number of the replacement OPC. The serial number is located on the large circuit board inside the OPC. Holding the OPC upright with the faceplate to your left, look along the bottom of the circuit board, about halfway back. The serial number is next to the bar code.

7 If you have not already done so, insert the OPC into the desired shelf slots. If you are replacing an OPC, install the replacement in place of the existing OPC. If you are just preparing a spare, you can use any available network element.

8 Log in to the primary OPC using the root userID and password. For instructions, see Common Procedures, 323-1111-846.

9 Identify the area addresses of the replacement and primary OPC.

continued

If you Then go to

do not know the Internet Protocol (IP) address of the OPC being replaced

step 10

know the IP address of the OPC being replaced step 10

If Then go to

the area address of the replacement OPC is the same as the area address of the primary OPC

step 10

otherwise step 13




Step Action

10 Obtain the address of the replacement OPC by entering:

/iws/upr/util/uprobj -v -serno Note: The serial number is located on the large circuit board inside the OPC. Hold the OPC upright with the faceplate to your left. Look along the bottom of the circuit board, about halfway back. The serial number is next to the bar code. For further instructions, see Commissioning Procedures, 323-1111-220.

Three fields appear that each contain a series of numbers and characters, such as the following example.

49+000000750354C500 49+000000003054C500 49+0000

11 Record the address of the replacement OPC from the second field.

12 Go to step 17.

13 Obtain the address of the replacement OPC by entering:

/iws/upr/util/uprobj -v -area -serno

Note: You can enter a command of more than 80 characters, even though the command line can display only 80 characters. In the last character position of the line, each further character entered overwrites the previous character. However, the OPC accepts the full command as entered.

Three fields appear that each contain a series of numbers and characters, such as the following example.

39840+000000753054C500 39840+000000753054C500 39840+00

14 Record the address of the replacement OPC from the second field.

15 Insert the software tape or cartridge that contains the software release you want to install on the spare OPC in the primary OPC tape or cartridge drive. This tape or cartridge contains the rmopcld utility that is required to remove the existing OPC software from an OPC.

continued

where

is the area address of the OPC

is the serial number of the OPC




Step Action

16 In the Open tools list, use the arrow keys to move to the UNIX shell tool. Select the tool. Press Ctrl_A (or Keypad 0).


17 Extract the rmopcld utility from the tape or cartridge and transfer it to the spare OPC. Enter:

dd if=/dev/rdt/tape2 bs=20b | remotsh OPC9999P cd /tmp; tar xvf - Note: OPC9999P is replaced by the OPC assigned in step 9 if it differs from OPC9999P.

The install files are displayed on the screen. After about 5 minutes, the transfer completes and the opc> prompt appears.

18 Display the User Session Manager. Press Ctrl_T 0.

19 Log out of the primary OPC.







22 Set the directory where the rmopcld utility was transferred. Enter:




/tmp/install

If this identifier does not appear, repeat step 22.

continued




Step Action

24 Execute the rmopcld utility. Enter:

rmopcld The following warning message appears and you are prompted to confirm the removal of the OPC load.

************* WARNING *************

This tool removes the OPC load. If you choose to continue,ensure that the tool completes successfully before proceeding with further operations.

Failure to do so could leave the OPC in an UNSTABLE state.

Do you want to remove the OPC load? (y/n)

Note: If an error message appears after you execute the rmopcld utility, log out of the spare OPC and log in to the primary OPC again. Repeat step 17 to step 24.

25 Confirm the removal of the load. Enter:

y OPC processes are stopped.

26 Continue removing the software load. Enter:

c The rmopcld utility removes the existing software load from the spare OPC. When the load is completely removed, the OPC reboots and the login prompt appears.

continued

If the software load being removed is

Then

release 7, or earlier a message appears, giving you the option of aborting the removal of the OPC load.Go to step 26.

release 8, or later the rmopcld utility removes the software load from the OPC. When the load is completely removed, the OPC reboots and the login prompt appears.You have completed this procedure.




Step Action

27 If necessary, eject the software tape from the primary OPC tape drive and place it in a safe location. If the OPC is equipped with a cartridge drive, manually eject the cartridge by pressing the button above the cartridge. Leave the software tape or cartridge in the tape or cartridge drive if you are continuing with Procedure 2-6, Installing a software load on a spare OPC not equipped with a tape or cartridge drive.

end



Procedure 2-6Installing a software load on a spare OPC not equipped with a tape or cartridge drive

Use this procedure to install the current software on the spare operations controller (OPC) that is not equipped with a tape or cartridge drive, after the existing software load has been removed using the rmopcld utility.


successfully complete Procedure 2-5, Removing a software load from a spare OPC not equipped with a tape or cartridge drive

have a TBM shelf with no OPC where the shelf (that is NE) must be commissioned in a primary OPC SOC with this OPC active

obtain a tape or cartridge containing the desired software load

obtain the root userID and password for the primary OPC

read the command conventions for the type of interface you are using (CMT or graphical) in Common Procedures, 323-1111-846Common Procedures, 323-1111-846 Common Procedures, 323-1111-846

Action

Step Action

1 Insert the current software tape or cartridge in the primary OPC tape or cartridge drive. The tape must be inserted with the white latch facing you. The latch is on the upper half of the tape when it is being inserted. If the OPC is equipped with a cartridge drive, insert the cartridge with the Nortel Networks logo facing toward the left.

Note: This step is unnecessary if the current software tape or cartridge is already in the primary OPC tape or cartridge drive.

2 Log in to the primary OPC using the root userID and password.





continued



Procedure 2-6 (continued)Installing a software load on a spare OPC not equipped with a tape or cartridge drive

Step Action

4 Access the Release Installation tool by entering:

install_release The main screen of the Release Installation tool appears.

5 Start the installation of the release by entering:

1 A list of destination OPCs appears.

Note: The backup OPC only appears in the list if the backup OPC is equipped in the system.

6 Select the other OPC from the list of destination OPCs by entering:

3 A request to enter the name of the desired destination OPC appears.

continued

RELEASE INSTALLATION TOOL

Main Menu---------------1. Install release2. Query available release on removable media3. Query available release on disk4. Exit

Please enter the number of the operation to perform (1-4): _


Here is the list of valid destination OPCs:1. Primary OPC2. Backup OPC3. Other4. Return to Main Menu

Please enter the number corresponding to the desired OPC (1-3)

--------------------------

or enter 4 to return to the Main Menu:_




Step Action

7 Enter the name (or the IP address) of the destination OPC (see note). The name is case-sensitive.

Note: The name of the destination OPC is either OPC9999P or the name given in step 9 of Procedure 2-5 with a P appended to the end of the name.

The Release Installation tool confirms the OPC as a valid destination and the following request to confirm the release installation appears.

8 Confirm the software installation by entering:

y The installation begins and release installation progress messages appear. At the end of the initialization, the OPC reboots. The reboot does not affect the tool. The OPC continues to monitor the progress from the same log-in session.

When the release installation completes, the following screen appears.


You have made the following selections

Release to install: OC-3/OC-12 Rel xx.xxDestination OPC: Source: removable media

Do you want to proceed with this installation (Y/N)?_

--------------------------


The installation of release OC-3/OC-12 Rel xx.xx on the

destination OPC to ensure there were no errors during the releaseinstallation.

--------------------------

OPC has completed. Please see the Event Browser logs on the

Press Return to go to the Main Menu: _




Step Action

9 Press the Return key to go to the main menu.

10 Exit the Release Installation tool by entering:

4 TERM=(vt100) appears.


The prompt opc> appears.

12 Log out from the OPC. For instructions, see Common Procedures, 323-1111-846.

Note: To check the logs to make sure no errors occurred during the release installation, log in to the destination OPC. Then, access the User Session Manager by entering the command opcui. Open the Event Browser tool by moving the cursor to the tool name and pressing Ctrl_A (or Keypad 0). You can only access the User Session Manager when the OPC is commissioned.

13 Remove the software tape or cartridge from the Primary OPC by pressing the small button beside the OPC tape or above the cartridge on the cartridge drive.

end


3-1

Rebooting and loading network element software 3-

This chapter contains procedures for the Reboot/Load Manager tool.

The Reboot/Load Manager is one of several operations controller (OPC) tools you use to manage the software for the OPC and network elements. This tool lets you do the following:

identify the software release installed on the OPC

monitor software downloads to shelf processors in the span of control

manually send the software release to a shelf processor (requesting a software download causes the shelf processor to restart)

The Reboot/Load Manager installs the network element application software and firmware according to the release catalog file. You cannot change this file.

You cannot delete releases from the OPC using this tool. The software installation or upgrade process automatically installs and deletes software.

Software releases and firmware loadsA software release specifies the software loads to deliver to network elements in the OPC span of control. The current release is OC-12 Release 13. You specify the initial release during the commissioning process. Under normal circumstances, the OPC stores a single software release for each TransportNode product (for example, OC-12 network element software). However, during software upgrades, the OPC temporarily stores two releases per product.

In addition, the OPC stores the current firmware loads for each type of circuit pack that currently supports downloadable firmware.

Procedures for upgrading software can differ according to the S/DMS TransportNode System product and release involved. Specific upgrade procedures for your system are described in a Change Application Procedure (CAP), available from your Nortel Networks representative.


3-2 Rebooting and loading network element software

Software rebootsThe Reboot/Load Manager sends firmware and software loads to network elements in two ways:

manually, when you initiate a software download with the Reboot/Load Manager

automatically during a release upgrade, when a shelf processor reboot triggers firmware and software downloads

Note: The Reboot/Load Manager tool sends firmware to any downloadable circuit packs and software to the shelf processor one network element at a time. Wait until one download completes successfully before you start another. In addition, Nortel Networks recommends that you load the shelf processors beginning with the network element farthest from the OPC. Doing so prevents the OPC from showing the status of downloads as failed.

Chapter task list This chapter includes the following procedures. Find the procedure you require and go to the specified page.

Procedure Title Page

3-1 Sending new software to a shelf processor 3-3

3-2 Querying the current software release on the OPC or network element

3-7


Rebooting and loading network element software 3-3

Procedure 3-1Sending new software to a shelf processor

Use this procedure to download software to a shelf processor. A software download request causes the shelf processor to reboot. After the shelf processor runs its diagnostics, the current software release downloads from the operations controller (OPC). The shelf processor then performs a restart (sometimes called a restart reload).

The shelf processor restart includes a download of the current network element provisioning data to the maintenance interface. A restart has a number of effects, such as the clearing of log buffers and resetting the performance-monitoring counters. For details of the effects of a restart, see Recovery Procedures, 323-1111-545.

This procedure makes only one attempt to reboot a shelf processor. If the software download fails, the OPC does not attempt the download again.

If you need to reboot several shelf processors, begin at the network element farthest from the OPC and move closer to the OPC. For example, the network element farthest from the OPC is the far-end terminal in a linear system. If you begin at the farthest network element, you prevent the OPC as showing the status of loads as failed.

Requirements Before you start, log in to the OPC with access privileges for the Reboot/Load Manager tool. For log-in instructions and an overview of the OPC user interface, see Common Procedures, 323-1111-846.

Action

Step Action

1 From the User Session Manager, open the Reboot/Load Manager tool by moving the cursor to the tool name and pressing Ctrl_A (or Keypad 0).

continued



Procedure 3-1 (continued)Sending new software to a shelf processor

Step Action

The Reboot/Load Manager main window appears. OS.0245

2 From the Network Element list, use the arrow keys to move to the network element you want and select it by pressing Ctrl_A (or Keypad 0).

The network element is highlighted.

continued

> Reboot/Load Manager .

Network Element

35 Chicago36 London

Type

1 OC-12 Term1 OC-12 Term

DefaultReleaseRel x.xxRel x.xx

LastAction - -

ActionStatus - -

C 0 M 0 m 0 w 0 FailProt 0 Lckt 0 ActProt 0 PrfAlrt 0 09:26




Step Action

3 Display the list item menu by pressing Ctrl _L (or Keypad Enter).

The list item menu appears. OS.0845

4 Choose the Load Shelf command by pressing Space (or Keypad 0).

The Load Shelf dialog appears.OS.0844

5 Tab to the OK button and select it by pressing Ctrl_A (or Keypad 0).

The Load Shelf dialog closes and the appropriate software transfers to the shelf processor.

continued




Network Element35 Ottawa36 London

ShelfOC-12 TermOC-12 Term

Last Action - -

ActionStatus - -

1 Load shelf

2 Select3 Deselect

4 Help H

[ Cancel Del ]

Load ShelfNetwork Element: 1205 Shelf: OC-12 TermYou are about to initiate a download of theentire NE. Are you sure you want tocontinue?

[ OK Return ]




Step Action

6 Close the tool by pressing Esc ).

Note: If you are rebooting a terminal in an unprotected system (0:1), you must insert a spare OC-12 demultiplexer circuit pack in the OC-12 G2 position. Allow the demultiplexer to autoprovision, and then remove it. You must then deprovision the OC-12 G2 equipment and facility according to Provisioning and Operations Procedures, 323-1111-310.

end



Procedure 3-2Querying the current software release on the OPC or network element

Use this procedure to identify the software release currently installed on the OPC or an OC-12 network element. The software release appears in three OPC tools: the OPC Status, Reboot/Load Manager, and Commissioning Manager tools. You can open any one of these tools to view the release number. You can also use the network element user interface to display the release number.

If you cannot find the required software release using this procedure, it is not present on the operations controller (OPC). You must then install the required release on the OPC disk. For more information on transferring network element software to the OPC, see the appropriate release upgrade Change Application Procedure (CAP).

Requirements Before you start, log in to the OPC with access privileges for the OPC Status, Reboot/Load Manager, or Commissioning Manager tool. For log-in instructions and an overview of the OPC user interface, see Common Procedures, 323-1111-846.

Action

Step Action

1 Determine how you want to check the current software release.

2 From the User Session Manager, open the OPC Status tool by moving the cursor to the tool name and pressing Ctrl_A (or Keypad 0).

3 Tab to the Open tools list and use the arrow keys to move to the OPC Status tool. Select the tool by pressing Ctrl_A (or Keypad 0).

continued

If you want to check the current software release using Then go to

the OPC Status tool step 2

the Reboot/Load Manager tool step 6

the Commissioning Manager tool step 8

the network element user interface step 10



Procedure 3-2 (continued)Querying the current software release on the OPC or network element

Step Action

The OPC Status window appears. OS.0852

4 The software release appears in the SW Version field.

5 After viewing the contents of the OPC Status window, press Ctrl_T 0 (zero) to return to the User Session Manager.

The User Session Manager appears. The OPC Status tool remains at the top of the Open tools list.

This procedure is complete.

6 From the User Session Manager, open the Reboot/Load Manager tool by moving the cursor to the tool name and pressing Ctrl_A (or Keypad 0).

On the Reboot/Load Manager main window, the current software release appears in the Default Release column, as follows.

OS.0245

7 Close the Reboot/Load Manager tool by pressing Esc ).


continued

OPC Name:OPC Function:

OPC Status:Network Element:

SW Version:Backup OPC Status:

OPC12345PPrimaryActive27(Rel #)Inactive


Network Element

35 Chicago36 London

Type

1 OC-12 Term1 OC-12 Term


LastAction - -

ActionStatus - -




Procedure 3-2 (continued)Querying the current software release on the OPC or network element

Step Action

8 From the User Session Manager, open the Commissioning Manager tool by moving the cursor to the tool name and pressing Ctrl_A (or Keypad 0).

A screen similar to the following appears.OS.0360

The version of software currently running on the OPC appears in the top line of the OPC Commissioning Manager screen. The software version has the format OPCaannaa, where aa are letters and nn are numbers.

9 Close the OPC Commissioning Manager tool by pressing Esc ).


10 Log in to the network element. For instructions, see Common Procedures, 323-1111-846.

11 Press the Return key twice.

A line similar to the following appears on the screen:

96/09/01 01:01 ==== TT12L16A62 OC12 Rel xx.xx Sept. 15, 1996 ====

This information indicates the release of the software load on the network element.

end

> OPC Commissioning Manager (Version opcaannaa_hp_65) Options.

System: Chicago 1 OPC Serial Number: A1f3e013a

1. [ Clear commissioning data 1]

2. [ Edit system data 2]

=> 3. [ Commission new network elements 3]

Commissioned network elements

4. [ Transfer data to Primary OPC (from SLAT OPC) 4] 5. [ Transfer data to Backup OPC (from Primary OPC) 5]


NE3536

TypeOC-12OC-12

FunctionTerminalTerminal

Serial NumberA2 c 0180004A2 2 0180006

OPCPrimaryBackup


4-1

Upgrading network element and OPC software 4-

This chapter describes the software delivery features associated with the OC-12 network elements and operations controller (OPC). It also introduces the OPC Network Upgrade Manager tool.

A software release consists of both OC-12 network element software and OPC software. The software release also includes firmware loads for circuit packs that support downloadable firmware.

Before you can upgrade a software release, you must deliver the new software release to the OPC. You then use the Network Upgrade Manager to distribute the network element software and firmware loads to the network elements and circuit packs in the span of control. For a new OPC, you have the option of having the software loaded at the factory.

There are the following methods of delivering software to an in-service OPC:

You can physically deliver the software release to the OPC on a digital data storage (DDS) tape or cartridge. You then upload the software from the tape or cartridge using the OPC tape or cartridge drive.

You can deliver software electronically over a Transaction Language 1 (TL1) connection from a centralized software repository. This method uses the File Transfer, Access, and Management (FTAM) protocol.

You can deliver software electronically using the Centralized Software Manager feature of the Integrated Network Management (INM) Broadband graphical user interface.

When the OPC has the latest software release, you use the Network Upgrade Manager tool to perform the software upgrade for the OPC span of control. You use the Network Upgrade Manager tool for the upgrade regardless of the mechanism you used to deliver software to the OPC.

To perform the software or firmware upgrades, see the appropriate software upgrade Change Application Procedure (CAP). For a list of available CAPs, see Ordering Information, 323-1111-151, or your Nortel Networks representative.


4-2 Upgrading network element and OPC software

Electronic software delivery over FTAMThis feature supports electronic delivery of an OC-12 software release to an OPC using the TL1 interface. Such software delivery uses the FTAM protocol as required by the Bellcore GR-1250-CORE specification (Issue 1, June 1995).

You can use FTAM to deliver network element software, OPC software, or system software (both network element and OPC software together). You cannot use FTAM to deliver Express software to an OPC.

To accept software delivery by way of FTAM, the OPC must already contain a software release. The software release contained in the OPC cannot be the same software release as the release you are delivering. Software delivery over FTAM therefore supports only release upgrades. It does not support installation of new software on an OPC without software (for example, to load a spare OPC with software).

You must deliver the software to an active primary OPC. You cannot deliver the software to a backup OPC. The TL1 surveillance administration interface handles the software delivery requests. The surveillance interface is also known as the Network Monitoring Analysis (NMA) interface.

To use the remote target identifier (RTID) for electronic software delivery over FTAM, you must enable the target identifier address resolution protocol (TARP). For instructions, see the procedure on enabling TARP support for the OPC in System Testing Procedures, 323-1111-222.

To perform the electronic software delivery over FTAM, see the appropriate CAP.

Network Upgrade Manager toolThe Network Upgrade Manager tool performs software and firmware upgrades for operations controllers (OPCs) and all network elements in the OPC span of control. The About the OC-12 NE Library, 323-1111-090 does not contain procedures for using the tool. Instead, you must use the appropriate CAP. The CAP contains all procedures necessary to perform software and firmware upgrades.

The Network Upgrade Manager supports the following types of upgrade:

software updates for either or both the primary and backup OPCs for a span of control

software updates for any or all of the network elements in a span of control

firmware updates for any or all circuit packs in a span of control that support downloadable firmware

The Network Upgrade Manager is available only in the user interface for the character-mode terminal (CMT). There is no graphical interface for this tool.


Upgrading network element and OPC software 4-3

The Network Upgrade Manager tool performs upgrades in two stages: distribution and activation.

DistributionThe Network Upgrade Manager distributes the OPC and network element software and firmware as required while the current release is active. The tool removes the existing network element release as part of this step. You can do the distribution ahead of time, in preparation for the release activation.

ActivationThe Network Upgrade Manager has a Healthcheck feature that runs various checks before the activation step begins. Activation also requires a hardware baseline check. The activation cannot occur until the Healthcheck, baseline check, and distribution all complete successfully.

The Network Upgrade Manager then activates the new release of software or firmware.

The Network Upgrade Manager tool allows you to change the following information for each upgrade:

the order in which the tool upgrades the network elements (the tool sets the upgrade order for OPCs automatically and you cannot change the order)

before the upgrade begins, you can specify where pauses occur during an upgrade

additional pauses to an upgrade already in progress

The main window of the tool, with all menus displayed, looks like the following.

OS.0864

.

Upgrade to OC-3/OC-12 REL 14.00

[ 1-Distribute ] [ 2-Activate ] [ Resume ]


Run HealthCheck toolRun Baseline toolOrder NEs...Display distribution statusDisplay pre-upgrade status

Help H

Exit )

Help H

1 Details D2 Pause after P3 Cancel Pause N4 AutoResume after I5 Remove AutoResume R

6 Select7 Deselect

8 Help H

> Network Upgrade Manager Utilities


4-4 Upgrading network element and OPC software


5-1

Delivering OPTera Metro 3000 network element software 5-

This chapter contains procedures to manage OPTera Metro 3000 series network element loads using the Load Manager tool of the operations controller (OPC).

This tool allows you to:

view the load currently stored on the local OPC

view the load on the tape or cartridge in the tape or cartridge drive

delete the load from the local OPC

install a load on the local OPC

Use the following userIDs to access the Load Manager tool:

for an inactive OPC, the standby userID

any userID with access to the Admin toolset

The Load Manager transfers a network element load only. Install a load as follows:

during an upgrade (using the Network Upgrade Manager tool) or

during an OPC software installation

Although the OPC can store the load, it does not manage network elements. To monitor or perform administrative activities for a network element, log in to the network element user interface. You can also use Nortel Networks Preside, a network management system.

You can delete the load from the OPC by other processes, such as a software upgrade or backout of a software upgrade.

The load does not transfer to the backup OPC during data synchronization. You must install the load on the backup OPC using the Load Manager tool.

Note: The OPC stores only one load at a time. When you install a new load, the new load overwrites the previous load.


5-2 Delivering OPTera Metro 3000 network element software

Handling and storing digital data storage tapes Keep digital data storage tapes (DDS) tapes away from moisture, extreme hot and cold temperatures, and magnetic fields and devices.

Handle DDS tapes carefully. Electrostatic discharge can damage DDS tapes. Always ground yourself before handling the tape.

Software cartridgesWhen handling or installing software cartridges, observe the following precautions.

Wear a wrist strap or other static-grounding device before you insert or remove a cartridge from the cartridge drive of an OPC.

Place each cartridge in its case when you remove it from the cartridge drive of an OPC.

Ensure that the cartridge is inserted with connector facing inward and the Nortel Networks logo facing towards the left. Do not force the cartridge into the OPC cartridge drive.

Tool restrictionsElectronic software delivery requires a Transmission Control Protocol/Internet Protocol (TCP/IP) network. The TCP/IP network can use Ethernet, X.25, or Serial Line Internet Protocol (SLIP) connections.

Use a SLIP connection for electronic software delivery only. Other usages of the SLIP connection can severely reduce the speed of the communications link.

Chapter task list This chapter includes the following procedures. Find the procedure you require and go to the specified page.

Procedure Title Page

5-1 Transferring a load from tape or cartridge to disk (OPTera Metro 3000 series only)

5-3

5-2 Deleting a load from the local OPC (OPTera Metro 3000 series only)

5-6

5-3 Viewing the OPTera Metro 3000 series software load (on tape, cartridge or disk)

5-7


Delivering OPTera Metro 3000 network element software 5-3

Procedure 5-1Transferring a load from tape or cartridge to disk (OPTera Metro 3000 series only)

Use this procedure to transfer the OPTera Metro 3000 series network element software load stored on tape or cartridge to the disk of the local operations controller (OPC).

You can perform this procedure on an inactive OPC using a standby user account.

This procedure transfers an OPTera Metro 3000 series network element load only. You install the load during one of these events:

a software upgrade (using the Network Upgrade Manager tool)

an OPC software installation

Note: If you log out from the OPC while you transfer a load, the OPC cancels the transfer.

Requirements Before you start this procedure:

Read Tool restrictions on page 5-2.

Insert the tape or cartridge containing the software load for the network element in the local OPC tape or cartridge drive.

Log in to the OPC with access privileges for the Load Manager tool. For log-in instructions and an overview of the OPC user interface, see Common Procedures, 323-1111-846.

Action

Step Action

1 Open the OPC Load Manager tool. Move the cursor to the tool name and press Ctrl_A (or Keypad 0).

continued

CAUTIONRisk of damaging circuit packsElectrostatic discharge can damage electrostatic-sensitive devices. Always ground yourself before you handle the tape or cartridge.



Procedure 5-1 (continued)Transferring a load from tape or cartridge to disk (OPTera Metro 3000 series only)

Step Action

The Load Manager main window appears. OS.0849

2 Select the Display load on removable media button. Press Ctrl_A (or Keypad 0).

A dialog, similar to this, lists all files related to the load. OS.0850

3 Check the list to confirm that the files are correct.

4 Select the Done button. Press Ctrl_A (or Keypad 0).

The load list dialog closes.

continued

> Load Manager


[Display load on removable media T]

[Display load on OPC L]

[Install load from removable media I]

[Delete load from OPC R]

Loads on removable media

( )FW-26322 (OPC24)

SPB02AN.LD.SWDSPA02AN.LD.SWDPSCB03AN.LD.SWD

[ Done Return ]



Procedure 5-1 (continued)Transferring a load from tape or cartridge to disk (OPTera Metro 3000 series only)

Step Action

5 In the main window, tab to the Install load from removable media button. Select the button. Press Ctrl_A (or Keypad 0).

6 In the confirmation dialog, tab to the OK button and select it. Press Ctrl_A (or Keypad 0).

The confirmation dialog closes. The new load overwrites the existing load. When the new load has been installed, a completion dialog appears.

7 In the completion dialog, select the Done button. Press Ctrl_A (or Keypad 0).

The completion dialog closes.

8 Close the tool. Press Esc ). end

If Then

a load already exists on the OPC A confirmation dialog appears. Go to step 6.

no load exists on the OPC yet A progress dialog appears, indicating that the load is installing. When the installation completes, a dialog appears. Go to step 7.



Procedure 5-2Deleting a load from the local OPC (OPTera Metro 3000 series only)

Use this procedure to remove the OPTera Metro 3000 series network element software load stored on the hard disk of the local operations controller (OPC).

This procedure deletes the OPTera Metro 3000 series load. You cannot delete a software release from the OPC.

Requirements Before you start, log in to the OPC with access privileges for the Load Manager tool. For log-in instructions and an overview of the OPC user interface, see Common Procedures, 323-1111-846.

Action

Step Action


The Load Manager main window appears.

2 Tab to the Delete load from OPC button and select it. Press Ctrl_A (or Keypad 0).

A confirmation dialog appears.

3 Tab to the OK button and select it. Press Ctrl_A (or Keypad 0).

When the OPC deletes the load, a completion dialog appears.

4 Select the Done button. Press Ctrl_A (or Keypad 0).

The completion dialog closes.

5 Close the tool. Press Esc ).end



Procedure 5-3Viewing the OPTera Metro 3000 series software load (on tape, cartridge or disk)

Use this procedure to view the OPTera Metro 3000 series network element software load. The load is stored either on the OPC disk or on the tape or cartridge in the tape or cartridge drive of the operations controller (OPC).

Requirements Before you start, log in to the OPC with access privileges for the Load Manager tool. For log-in instructions and an overview of the OPC user interface, see Common Procedures, 323-1111-846.

Action

Step Action


The Load Manager main window appears.

2 Tab to the Display load on removable media button and select it. Press Ctrl_A (or Keypad 0).

A dialog, similar to this, lists all files related to the load. OS.0850

Go to step 4.

continued

If you want to display the load on Then go to

tape or cartridge step 2

OPC disk step 3

Loads on removable media

FW-26322 (OPC24)

SPB02AN.LD.SWDSPA02AN.LD.SWDPSCB03AN.LD.SWD

[ Done Return ]



Procedure 5-3 (continued)Viewing the OPTera Metro 3

SONET Transmission Products S/DMS TransportNode …npatrick/nortel-sdms-docs/N3S2N3GW.pdf · SONET...

Documents

Transcript of SONET Transmission Products S/DMS TransportNode …npatrick/nortel-sdms-docs/N3S2N3GW.pdf · SONET...