SW Upgrade 846

Software Upgrade ProcedureMarconi OMS 846 R1.5

UPGRADE INSTRUCTIONS

1/153 72-CRA 119 0511/15 Uen C

Copyright

Ericsson AB 2011. All rights reserved. No part of this document may bereproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due tocontinued progress in methodology, design and manufacturing. Ericsson shallhave no liability for any error or damage of any kind resulting from the useof this document.

1/153 72-CRA 119 0511/15 Uen C | 2011-09-29

Contents

Contents

1 Introduction 11.1 General Important Information 1

2 Software Upgrade in CRAFT 52.1 Preparations 52.2 Upgrade Procedure 62.3 Verification 82.4 Rollback Procedure 8

3 Software Upgrade in OSS 113.1 Prerequisites 113.2 Upgrade Procedure 12

Reference List 17

1/153 72-CRA 119 0511/15 Uen C | 2011-09-29

Software Upgrade Procedure

1/153 72-CRA 119 0511/15 Uen C | 2011-09-29

Introduction

1 Introduction

The purpose of this document is to describe the upgrade procedure for theOMS 846 Release 1.5.

1.1 General Important InformationThis section provides general important information of upgrading procedures.

1.1.1 Terminology

Terminologies for the OMS 846 system upgrading used in this document aregiven as follows:

NR OMS 846 device network release which contains the two items below.

Software System Controller Software

Firmware Module Firmware

Each of them is a collections of loadable items running in the OMS 846 R1.5.

1.1.2 Traffic Interruption

No traffic will be interrupted while downloading OMS 846 NR without restartingthe Network Element (NE).

No traffic will be interrupted while downloading OMS 846 software.

All traffic will be interrupted while downloading OMS 846 firmware.

Approximately 90 seconds traffic interruption can be expected for mostupgrades.

1.1.3 Active and Inactive Banks Consistencies

The OMS 846 supports both active and inactive bank. It is recommended tokeep consistent versions of NR, software, or firmware for both banks. So therepetitive upgrade operation procedures are needed for both the active andinactive banks.

11/153 72-CRA 119 0511/15 Uen C | 2011-09-29


1.1.4 Network Release Content

Table 1 shows network release file and patch information for all the OMS 800series software upgrade.

Table 1 OMS 800 Series Software Upgrade Files

UpgradeSuit

Suit FileName

ApplicableVersion

FileType

File Name

NR 1_19089-CXP9013872_13END.zipOMS 846

R1.3 Patch 2_19089-CXP9013872_13ENC.zip

NR 1_19089-CXP9013871_22END.zipOMS 860


OMS 870R3.2

NR 19089-CXP9014402_32ENE.zip

OMS 800R3.2

LZY 2144375/32 R1BSW CD

OMS 800Craft R1.1

LCTInstall

1_19003-CXP9015678_11END.exe

NR 1_19089-CXP9013872_14ENC.zipOMS 846


NR 1_19089-CXP9013871_23ENC.zipOMS 860


OMS 870R3.3

NR 19089-CXP9014402_33ENC.zip

OMS 800R3.3

LZY 2144375/33 R1CSW CD

OMS 800Craft R1.2

LCTInstall

19003-CXP9015678_12ENC.exe

2 1/153 72-CRA 119 0511/15 Uen C | 2011-09-29

Introduction

UpgradeSuit

Suit FileName

ApplicableVersion

FileType

File Name

NR 1_19089-CXP9013872_15ENC.zip

OMS 846R1.5

Patch 2_19089-CXP9013872_15ENC.zip

NR 1_19089-CXP9013871_24ENC.zip

OMS 860R2.4

Patch 2_19089-CXP9013871_24ENC.zip

OMS 870R3.4

NR 19089-CXP9014402_34ENC.zip

OMS 800R3.4

LZY 2144375/34 R1ASW CD

OMS 800Craft R1.3

LCTInstall

19003-CXP9015678_13ENC.exe

The Table 2 shows network release and patch files available in CD.

Table 2 OMS 846 Network Release Files

Files Description Location1_19089-CXP9013872_15ENC.zip

OMS846_NR OMS800 R3.4 LCT andESW CD

2_19089-CXP9013872_15ENC.zip

OMS846_NR_patch_fromR1.1toR1.5

OMS800 R3.4 LCT andESW CD

The Table 3 shows the network releases contained in the file 1_19089-CXP9013872_15ENC.zip and the patch 2_19089-CXP9013872_15ENC.zip, whichare stored in OMS800 R3.4 LCT and ESW CD. Items in BOLD are new inthis release (compared to R.1.4, R-state R1F). See the file package.xml forthe code of each item.

Table 3 Network Release Content

Network Release definition filepackage.xmlSYSTEM SWMain Card FW

Note: The file 2_19089-CXP9013872_15ENC.zip is required when upgradingthe system from a version earlier than R1.3 to R1.5.There is no patch required when upgrading the system from OMS 846R1.3 or R1.4 to R1.5.

31/153 72-CRA 119 0511/15 Uen C | 2011-09-29


4 1/153 72-CRA 119 0511/15 Uen C | 2011-09-29

Software Upgrade in CRAFT

2 Software Upgrade in CRAFT

This chapter describes how to upgrade the software by using an OMS 800CRAFT terminal.

2.1 PreparationsThis section presents the preparations needed for a successful completionof the procedures in this instruction.

2.1.1 Required Tools and Access Information

The following tools and access information is required:

A PC with OMS 800 Craft installed.

Note: OMS 800 CRAFT R1.3 is the minimum required for operating thisNR of OMS 846 R1.5. For more information about how to installand upgrade CRAFT, refer to OMS 800 CRAFT 1.3 User Guide,Reference [2].

A LAN cable for local access to a Network Element (NE). The IP address of the NE.

The password for the administrator.

2.1.2 Additional Preparations

Consider the following additional preparations:

Relevant network release files and patches listed in Table 2 are available.

Ensure that the NE is in a suitable state for upgrading by checking thefollowing status:

NE Current Version

Bank Status and Versions

Network Release Validity

Backup the current CDB file.

Note: Refer to OMS 800 CRAFT 1.3 User Guide, Reference [2] forinstructions.

51/153 72-CRA 119 0511/15 Uen C | 2011-09-29


2.2 Upgrade ProcedureThis section describes the upgrade procedures.

For how to upgrade the system from a release earlier than OMS 846 R1.3,see Section 2.2.1 on page 6.

For how to upgrade the system from OMS 846 R1.3 or R1.4, see Section2.2.2 on page 6.

2.2.1 Upgrade from a Release Earlier than R1.3

When upgrading from a release earlier than OMS 846 R1.3, perform the stepsbelow:

1. Download the patch 2_19089-CXP9013872_14ENC.zip.

2. Download the network release file 1_19089-CXP9013872_14ENC.zip.

2.2.2 Upgrade from OMS 846 R1.3 or R1.4 to R1.5

To unpack and install the packages mentioned in Table 3, perform the followingsteps:

1. Launch OMS 800 CRAFT and logon as an administrator user.

2. On the Equipment menu, click NE Maintenance. . . . This opens theNE Maintenance window.

3. Click the TFTP Server in the Information panel of the left navigation bar.

4. Ensure the Enabled check box is checked and remain other settings asdefault.Note: The value of the Host can only be set as 0.0.0.0 when the computeris connected to the device directly. In this case, 0.0.0.0 represents thecomputer's IP address. Otherwise, the Host value should be set accordingto the network address.

5. Click Device in the Network Release panel of the left navigation bar.

6. On the toolbar, click Download to open the Download wizard window,then click Next.

7. Click Add file to repository to open the Package Installer window, thenclick Next.

8. Click Browser to select the package file that mentioned in Section 1.1.4on page 2.

9. Click Next, and then click Finish.

10. When the package installation process is finished, click Close to close thePackage Installer window.

6 1/153 72-CRA 119 0511/15 Uen C | 2011-09-29


11. In the Download wizard window, select the desired network release fromthe repository list and click Next.

12. Select the Restart NE Time from the drop down list.

Note: The selected time will overwrite the scheduled restart time thatwas set before.

13. Click Next, and then click Finish.You may close the Download wizard window and view the downloadprogress in the NE Maintenance window.In the OMS 800 Craft window, the TFTP events during the network releasedownload are shown in the Event Trace page of the Notification Listpanel.

Note: If a scheduled restart is selected, the status panel in the NEMaintenance window displays the restart time after the downloadis finished. This information is kept until the NE restart completes.

14. If a scheduled NE restart is initiated, the "Connection Lost" is reported.When the NE restart finishes, the "Equipment Reconnected" is reported.Click OK when the massage boxes show.

71/153 72-CRA 119 0511/15 Uen C | 2011-09-29


2.3 VerificationTo verify the upgrade is successful, perform the following steps:

1 In the OMS 800 Craft window, click the device node in the ManagementTree panel.

2 Check the value of the Network Release Validity. If the upgrade issuccessful, the value is OK.

Note: If the current configuration is not at NR level, click the link ofNetwork Release Validation to view the details.

2.4 Rollback ProcedureWhen rollback from OMS 846 R1.4 to a previous release, following the stepsbelow:

1. Backup the current CDB file, Refer to OMS 800 CRAFT 1.3 User Guide,Reference [2] for detailed information.

2. Download the patch file of previous release.

Note: This is necessary for rollback to a release earlier than R1.3 only.

3. Restart the device manually.

4. Configure the IP address and the Community-handler. Refer to CLIDescription, Reference [1] for detailed information.

8 1/153 72-CRA 119 0511/15 Uen C | 2011-09-29


5. Restore the CDB file again.

Note: Check the Serial port's status while downloading the NR package.Ensure that the device is re-powered manually during restart.

91/153 72-CRA 119 0511/15 Uen C | 2011-09-29


10 1/153 72-CRA 119 0511/15 Uen C | 2011-09-29

Software Upgrade in OSS

3 Software Upgrade in OSS

This chapter describes how to upgrade the software by using an OSS inan HP-UX system. The OSS can be a ServiceOn Microwave (SOM) or aServiceOn Element Manger (ServiceOn EM).Note: ServiceOn EM R1.4 with EM-AXX plug-in in 12.10.1W is the minimum

required for operating this upgrade.

Only the NR upgrade is supported in OSS.

The OMS 800 family members have the same upgrade procedure. Theupgrade for OMS 870 is shown as an example in this chapter.

3.1 PrerequisitesBefore upgrading the software in the OSS, perform the following procedures:

1. Log on HP-UX system as the root user.

2. Create an empty directory in the root directory and name it as swkeep.

3. Save the software to this directory.

Note: Because the swinstall directory for the current user will beemptied after the Load Software Version Complete command isexecuted, it is recommended to backup the software directory for futurereuse.

4. Choose an user group that is in use.

5. Set the ownership to user.

Note: The user group and the ownership can be changed using the chown command. The following is an example:

chown ax5:nmc CXP9012544_1V10_R1F.package.zip

6. Grant the read, write, and execute permissions to all users in all the usergroups by running chmod 777 command.

7. Copy the software file to the swinstall directory for the current userusing the following commands:

csh

cp -p /opt/mv36/core/nmc/users//swinstall

111/153 72-CRA 119 0511/15 Uen C | 2011-09-29


Note: The p flag must be used to ensure that the permissions are copiedwith the file.

3.2 Upgrade ProcedureTo upgrade the software in the OSS, perform the following steps:

1 Navigate to the swinstall directory for the current user.2 Check and ensure that the software file exists with the correct ownership

and permissions.3 Click Download > Load on main menu. This opens the Load Software

Download window.

4 Select the Node Type of the node to be upgraded.5 Select the row of the desired node in the Software Version area.6 Type the desired software version in the Load Version textbox at the

bottom (For example, 3.2.6.0).Note: If a package file has been downloaded before, the textbox isOverload Version instead.

7 Click OK.

12 1/153 72-CRA 119 0511/15 Uen C | 2011-09-29


8 Ensure that the Details column for the Load Software VersionComplete command is blank. It can be found at the bottom of theCommands area.

Note: If a Compliance: Failed, Error in storing fileserror occurs for the Load Software Version Complete command, thereare three possible causes:

The file has not been stored in the swinstall directory for the currentuser.

Incorrect permissions.

Incorrect ownership.9 View the swinstall directory for the current user and ensure it is empty.10 Click Download > Jobs > Schedule on the main menu. This opens the

Schedule Software Download Jobs window.

11 Select the Node Type.12 Select the Node from the Card Type drop-down menu.

131/153 72-CRA 119 0511/15 Uen C | 2011-09-29


13 Select the software name.

Note: The software name must be consistent with the name given in theLoad version (the same as the software version) or Overload Versionabove.

14 Select the desired Start On time and date by performing the followingsteps:

a. Click at the end of the Start On textbox.

b. Click to increase or decrease the time.

c. Click .

d. Click OK to confirm the adjustment.Note: This is an optional step. If the Start-On time and date has not beenselected, the start time for the download rounds up to the next full quarterof the hour. For example, if the system time is 12:32, the download willstart at 12:45.

15 Click Download > Jobs > View from the main menu to view the progressstatus. This is an optional step.

Note: This view window does not refresh automatically. Close and reopenthe window to view the status changes. When the download is completed,the Status will change from Wait to Run.

14 1/153 72-CRA 119 0511/15 Uen C | 2011-09-29


16 A message alert box will pop up in the main OSS screen after download.Click Open to view whether the download is successfully completed.

17 Click OK to confirm and close the alert box.

151/153 72-CRA 119 0511/15 Uen C | 2011-09-29


16 1/153 72-CRA 119 0511/15 Uen C | 2011-09-29

Reference List

Reference List

[1] CLI Description, 1/1543-CSA 113 57/4[2] OMS 800 CRAFT 1.3 User Guide, 1553-CRA 119 0986/13

171/153 72-CRA 119 0511/15 Uen C | 2011-09-29

toc1 Introduction1.1 General Important Information1.1.1 Terminology1.1.2 Traffic Interruption1.1.3 Active and Inactive Banks Consistencies1.1.4 Network Release Content

2 Software Upgrade in CRAFT2.1 Preparations2.1.1 Required Tools and Access Information2.1.2 Additional Preparations

2.2 Upgrade Procedure2.2.1 Upgrade from a Release Earlier than R1.32.2.2 Upgrade from OMS 846 R1.3 or R1.4 to R1.5

2.3 Verification2.4 Rollback Procedure

3 Software Upgrade in OSS3.1 Prerequisites3.2 Upgrade Procedure

SW Upgrade 846

Documents

Transcript of SW Upgrade 846