1_V1_Alcatel-Lucent 9311, 9312, 9322, 9326, 9332 Node B - Software Upgrade Procedure Using OAM 8.1_ Inter Release Upgrade

NN-20500-149

Wireless Service Provider Solutions

W-CDMA

Upgrade Procedure

Alcatel-Lucent 9300 W-CDMA Product Family

Alcatel-Lucent Node B - Software Upgrade Procedure Using OAM8.1: Inter Release Upgrade

NN-20500-149 07.09/EN Standard January 2013


W-CDMA Upgrade Procedure



Document number: NN-20500-149 Document issue: 07.09/EN Document status: Standard Product release: OAM08.1 Date: January 2013

Alcatel-Lucent Internal Proprietary Use pursuant to Company instruction

Copyright 2003-2013 Alcatel-Lucent. All rights reserved.

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is write

protected; it may be altered only by authorized persons. While copies may be printed, it is not recommended.

Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be

regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent.

Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained

herein confidential, shall disclose the information only to its employees with a need to know, and shall protect

the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by

Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have received

this document in error, please notify the sender and destroy it immediately.

Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marks of

Alcatel-Lucent, Alcatel and Lucent Technologies.

All other trademarks are the property of their owners.

Publication history i

Copyright 2003-2013 Alcatel-Lucent Alcatel-Lucent 9300 W-CDMA Product Family - Alcatel-Lucent Node B - Software Upgrade Procedure Using OAM8.1: Inter Release Upgrade

PUBLICATION HISTORY

SYSTEM RELEASE: OAM08.1

January 2013

Issue 07.09/EN, Standard

Updated according to the remark from odile.

December 2012


Updated according the review comments from Briac Ion.

October 2012


October 2012


September 2012

Issue 07.05/EN, Preliminary

April 2012


August 2011


August 2011

Issue 07.02/EN, Draft Updated according the review comments from Briac Ion.

June 2011

Issue 07.01/EN, Draft Document creation

Table of content iii


TABLE OF CONTENTS

1. INTRODUCTION ............................................................................................. 1

1.1. OBJECT AND SCOPE OF THIS DOCUMENT .................................................................................... 1 1.2. AUDIENCE FOR THIS DOCUMENT ................................................................................................ 1

2. RELATED DOCUMENTS .................................................................................... 1

2.1. APPLICABLE DOCUMENTS .......................................................................................................... 1 2.2. REFERENCE DOCUMENTS .......................................................................................................... 1

3. NODE B UPGRADE .......................................................................................... 2

3.1. IMPORTANT INFORMATION ......................................................................................................... 2 3.2. UPGRADE PREREQUISITES ........................................................................................................ 2

3.2.1 WARNINGS ....................................................................................................................... 2 3.2.2 RECOMMENDATION ........................................................................................................... 3 3.2.3 MANDATORY RESOURCES NEEDED FOR THE UPGRADE ........................................................ 3

3.3. UPGRADE OVERVIEW ................................................................................................................ 4 3.3.1 SOFTWARE UPGRADE PROCEDURE STEPS .......................................................................... 4 3.3.2 FALLBACK STEPS (IF NEEDED) ........................................................................................... 6

3.4. TWO KINDS OF UPGRADE SEQUENCE .......................................................................................... 7 3.4.1 UPGRADE SEQUENCES ...................................................................................................... 7 3.4.2 HOW TO PERFORM SINGLE LEAP UPGRADE PROCESS ....................................................... 8

3.5. UPGRADE SEQUENCE TABLE ...................................................................................................... 9 3.6. FALLBACK SEQUENCE TABLE ...................................................................................................10

4. SHEETS ..................................................................................................... 11

HOW TO .......................................................................................................................................12

DOWNLOAD SOFTWARE FROM DVD-ROM/LOCAL FILES TO SRS ..................................................................13 CHECK NODE B ALARMS ......................................................................................................................18 BACKUP NODE B IN THE OAM DATABASE ................................................................................................21

EXPORT NODE B CM XML FILE FROM OAM DATABASE ..............................................................................23 UPGRADE THE NODE B CM XML FILE ....................................................................................................26 DOWNLOAD SOFTWARE TO NODE B........................................................................................................32 SET THE NODE B MAINTENANCE MODE ON OR OFF (OPTIONAL) ....................................................................41

ACTIVATE THE SOFTWARE AND THE NEW MIB ...........................................................................................42

FALLBACK THE NODE B SOFTWARE ........................................................................................................48 HOW TO USE THE WAUT UPGRADE REPORT............................................................................................51

APPENDIX A: UPGRADE MESSAGES ............................................................................ 54

Table of content v


LIST OF FIGURES

Figure 1. Node B upgrade procedure (UA7.1 to UA8.1 as an example) .................................................. 4 Figure 2. Do Single Leap upgrade ......................................................................................................... 8 Figure 3. Launch the Equipment Monitor ...............................................................................................12 Figure 4. SRM GUI .................................................................................................................................13 Figure 5. SRM install software page ......................................................................................................14 Figure 6. SRM install software page for Local Software Delivery Files .................................................15 Figure 7. SRM install software data transfer page .................................................................................15 Figure 8. SRM installation successful page ...........................................................................................15 Figure 9. SRM installation details and result ..........................................................................................16 Figure 10. SRM delete software page ....................................................................................................16 Figure 11. How to open Alarm window ...................................................................................................18 Figure 12. OSI State Reporting window .................................................................................................19 Figure 13. Check calls at RNC side .......................................................................................................20 Figure 14. Check calls on linked FDDCells ............................................................................................20 Figure 15. Export NE Grouping ..............................................................................................................23 Figure 16. CM XML Export window ........................................................................................................24 Figure 17. Command Manager...............................................................................................................24 Figure 18. Launch Wireless Access Upgrade Tool ................................................................................26 Figure 19. Import and export ..................................................................................................................27 Figure 20. Select the Import snapshot option.........................................................................................27 Figure 21. Select the Replace initial snapshot and discard existing workorders mode .........................28 Figure 22. Select the initial RNC CM XML file........................................................................................28 Figure 23. Save the workspace option ...................................................................................................29 Figure 24. Import progress window ........................................................................................................29 Figure 25. Select the NE Provisioning Upgrade Operation ....................................................................30 Figure 26. NE Provisioning Upgrade Operation window ........................................................................30 Figure 27. Download wizard: Introduction ..............................................................................................32 Figure 28. Download wizard: Select the Network Element type(from menu bar) ..................................33 Figure 29. Download wizard: Select the Network Element type (from right-click menu) .......................33 Figure 30. Download wizard: Select Software Version to Download .....................................................33 Figure 31. Download wizard: Select Search Method .............................................................................34 Figure 32. Download wizard: Set Active Version Filter ..........................................................................34 Figure 33. Download wizard: Set RNC filter ...........................................................................................35 Figure 34. Download wizard: Search Criteria Summary ........................................................................35 Figure 35. Download wizard: Retrieved Node(s) ...................................................................................35 Figure 36. Download wizard: Retrieved Node(s) ...................................................................................36 Figure 37. Download wizard: Download Action Require ........................................................................36 Figure 38. Download wizard: Node B MIB Modification .........................................................................37 Figure 39. Download wizard: Search Criteria Summary ........................................................................37 Figure 40. Download:Command Manager .............................................................................................38 Figure 41. How to open Inventory & Upgrade Session ..........................................................................39 Figure 42. Select the current running software ......................................................................................39 Figure 43. Select NE with status DOWNLOAD_COMPLETED .............................................................40 Figure 44. The inventory after execute Abort upgrade session .............................................................40 Figure 45. Set Maintenance Mode On ...................................................................................................41 Figure 46. Activation wizard: Introduction ..............................................................................................42 Figure 47. Activation wizard: Select the Network Element type .............................................................43 Figure 48. Activation wizard: Select the Network Element type .............................................................43 Figure 49. Activation wizard: Select Search Method ..............................................................................43 Figure 50. Activation wizard: Set Passive Version Filter ........................................................................44 Figure 51. Activation wizard: Set RNC filter ...........................................................................................44 Figure 52. Activation wizard: Search Criteria Summary .........................................................................44 Figure 53. Activation: Retrieved Node(s) ...............................................................................................45 Figure 54. Activation: Retrieved Node(s) ...............................................................................................45 Figure 55. Activation wizard: Search Criteria Summary .........................................................................46 Figure 56. Activation: Command Manager .............................................................................................46 Figure 57. Launch Equipment Monitor ...................................................................................................48

vi

NN-20500-149 07.09/EN January 2013 Copyright 2003-2013 Alcatel-Lucent

Figure 58. Equipment Monitor window ...................................................................................................49 Figure 59. Inventory & Upgrade Session window ..................................................................................50 Figure 60. WAUT upgrade report1 .........................................................................................................51 Figure 61. WAUT upgrade report2 .........................................................................................................52 Figure 62. WAUT upgrade report3 .........................................................................................................52

Table of content vii


LIST OF TABLES

Table 1. Upgrade total duration ................................................................................................................ 5 Table 2. Maintenance Window duration ................................................................................................... 6 Table 3. Outage duration .......................................................................................................................... 6 Table 4. Upgrade sequence ..................................................................................................................... 9 Table 5. Fallback sequence....................................................................................................................10 Table 6. Upgrade messages ..................................................................................................................54

1


1. INTRODUCTION

1.1. OBJECT AND SCOPE OF THIS DOCUMENT

The aim of this document is to describe how to perform a software upgrade of

Alcatel-Lucent Node Bs using the OAM8.1.

The present procedure supports the following upgrade path:

UA7.1.3 to UA8.1

The Alcatel-Lucent Radio Network Controllers to which the Alcatel-Lucent Node Bs

to be upgraded are parented should have been upgraded to target release prior to

beginning the upgrade.

Note: This document is applicable to Node B product numbers: 9311, 9312, 9322,

9326, 9332, 9944 Smart Base station.

1.2. AUDIENCE FOR THIS DOCUMENT

Alcatel-Lucent customers.

Anyone who performs Node B software upgrade.

2. RELATED DOCUMENTS

2.1. APPLICABLE DOCUMENTS

[A1] UMT/SYS/INF/034683 UA8.1 UTRAN Release Notes

[A2] UMT/SYS/INF/033614 UA7.1.3 UTRAN Release Note

[A3] NN-20500-046 Management System - Engineering Guide

[A4] NN-20500-052P1 Alcatel-Lucent 9300 W-CDMA Product

Family UA07 / OAM07 Release Operational Impacts

[A5] NN-20500-154 Alcatel-Lucent 9300 W-CDMA Product

Family Capacity and Feature Licensing

[A6] UMT/OAM/DJD/033992 Release Notes for UMTS OAM08.1

2.2. REFERENCE DOCUMENTS

[R1] NN-10300-036 Alcatel-Lucent 9353 Management System -

Workstation Client/Application Installation

2


3. NODE B UPGRADE

3.1. IMPORTANT INFORMATION

WARNING 1:

Make sure that the present document is the latest version of the upgrade procedure.

WARNING 2:

Feature activation and any kind of configuration changes must not be performed on

NodeB in parallel with this upgrade procedure.

Operations such as hardware intervention (for example CCM module change), upgrade

using the TIL or configuration changes from the OAM are not allowed during this

procedure.

Failing to comply with this instruction will lead to increased upgrade duration and

potentially to its failure.

WARNING 3:

During the upgrade, all the counters generated are lost on the Node Bs.

3.2. UPGRADE PREREQUISITES

3.2.1 WARNINGS

WARNING 4:

Before executing this procedure, ask the support team for any special actions (bulletin,

workaround, patch ...) to perform before, during and after the procedure. Please refer

to the [A1] and [A2] documents.

WARNING 5:

All the prerequisites described in this chapter must be fulfilled at least one day before

the upgrade starts.

WARNING 6:

Before executing the upgrade, it is required to verify that OAM IP network between WMS

and the Node Bs to upgrade is setup in correspondence with Engineering rules (OAM-NE

network configuration and routing tables at WMS). See [A3]

WARNING 7:

Please ensure that all RNCs associated with your Node Bs have been upgraded to target

release before executing the NodeBs upgrade. For more information, please see the

corresponding ALTP (NN-20500-148).

WARNING 8:

About CPRI + HSSL mixity, one IC parameter RRH Type is used to judge whether HSSL

or CPRI link is activated or not. And this parameter can be modified by TIL.

Value "0" means: link 1, 2 and 3 can connect to CPRI RE (RRH11, 21 and 31); link4, 5 and

6 can connect to HSSL RRH (RRH41, 51 and 61).

3


Value "1" means: all the 6 links are connected to CPRI RE (RRH11, 21 ... 61).

3.2.2 RECOMMENDATION

For ease of use it is recommended to perform bulk Node B upgrade on a RNS basis.

3.2.3 MANDATORY RESOURCES NEEDED FOR THE UPGRADE

Please make sure before starting the upgrade that the following resources are

available.

If any of them are missing the upgrade cannot be performed.

Human resources: one OAM site operator.

PC client: one client OAM PC or workstation.

Wireless Access Upgrade Tool (WAUT) to be used in order to perform the CM XML

files upgrade. This tool is available on the ACCESS OAM DVD-ROM and must be

installed on the PC client.

WCF file: This file is used by WAUT when performing provisioning upgrade. It

should be put in WCF subdirectory of WAUT installed directory, and should be only

one WCF file in that directory.

DVD-ROM: One DVD-ROM of the new Node B software.

All the software (RNC and OAM loads) used during this procedure must be

compliant with the software line-up defined in [A1] and [A2] documents.

Logins and passwords: The OAM site operator performing the upgrade must have

the password for the WMS Client administrator account with full access to the

OAM.

4


3.3. UPGRADE OVERVIEW

The following diagram describes the Node B upgrade procedure:

Figure 1. Node B upgrade procedure (UA7.1 to UA8.1 as an example)

In the figure above, the CM XML file export, upgrade, and download with import

(steps 1, 2 and 3) are performed without any impact on the Node B service. The

outage occurs at activation (step 4).

3.3.1 SOFTWARE UPGRADE PROCEDURE STEPS

The upgrade is composed of three main steps:

- The provisioning upgrade at OAM level

- The software download with import of CM XML file

- The activation

Download and activation steps should be performed separately. The download

should first be performed (no impact on service) and then, during the

maintenance window, the activation (with loss of service).

Note that it is also possible to perform those two steps as one but in that case

provisions must be made for a longer maintenance window to take into account

the download duration.

Note: if operator upgrade V813 load from any older release, need to collect all the

IMT for previous issues before upgrade, activate and reset. During some upgrade

OAM data base

RNC RNC NodeB

21

22

23

24

2 5

Parallel

Download

Uptp

Node-B CM XML file export

-Bfile import

UA 4.2 Node BCM XML file

WirelessAccess

Upgrade Tool

OAMOAM UTRAN

Upgrade application

OAM data base

RNC RNC Node B

2 12 3

2221

2322

2423

2 52 4

Node B CM XML export

UA 4.2 Node BCM XML file

UA8.1CM XML file

WirelessAccess

Upgrade Tool

XML file

OAMOAM UTRAN

Upgrade Application

Para

llel D

ow

nlo

ad &

CM XM

L im

port

Up to

10

00 No

de B

in

para

llel

Para

llel A

ctiv

atio

n.

Up to

10

00 No

de B

in

para

llel

UA7.1 CM XMLfile

Node B CM XML import

Up to 1000 in parallel

5


cases, IMT logs are unusable like this: No EEC due to EEC version change. Please

ignore it.

3.3.1.1 PROVISIONING UPGRADE

As the MIB format changes between UA7.1 and UA8.1, the OAM data format also

changes during the upgrade to UA8.1. Therefore the OAM data needs to be

upgraded to fit with the new MIB model of the UA8.1 Node B software. This is

performed using the Wireless Access Upgrade Tool. The data is extracted from the

OAM and upgraded.

3.3.1.2 SOFTWARE DOWNLOAD WITH IMPORT

The operator can select up to 1000 Node Bs to download. 48 downloads(The number of downloads performed in parallel is limited through OAM configuration; by default, its set to 48) are performed in parallel. When the operator has selected 1000 Node Bs to download, the first 48 Node B downloads start and the others are

queued. Each time a download (from the 48 current commands) is complete a new

Node B download is automatically started from the queued Node B list. This

principle applies also to the activation phase (see below).

The download with import starts a session. Note that during this phase, no

configuration changes can be made to the Node Bs.

3.3.1.3 ACTIVATION

Once the download with import has been completed, the activation can be

performed.

Note also that during this activation phase, there is a service and supervision

loss. This phase must therefore be performed during the maintenance window.

3.3.1.4 DURATIONS

Taking into account the pre/post checks and all the steps needed to complete the

upgrade (see section 3.5 page 9), the global upgrade duration should be as follows.

Upgrade total duration for

48 Node Bs

255 minutes

Table 1. Upgrade total duration

3.3.1.5 MAINTENANCE WINDOW

The maintenance window is the timeframe during which disruptive operations are

performed on the network that affect the service or the network configuration.

All operations that have a low or no impact on the service or on the network are

performed before the maintenance window. The maintenance window duration

also includes the duration for a fallback.

6


Maintenance Window

duration

55 minutes

+

40 minutes for the fallback

=

95 minutes

Table 2. Maintenance Window duration

3.3.1.6 OUTAGE

The impact on service occurs at the end of the software activation when the Node

Bs restart (this takes about 5 minutes).

Outage duration

(whatever the number of Node B)

5 minutes

Table 3. Outage duration

3.3.2 FALLBACK STEPS (IF NEEDED)

The fallback steps allow the operator to go back to the previous release if the

newly activated software does not work correctly.

The fallback operation requires a downgrade of the Node Bs in the OAM database

and downgrade to be performed on these Node Bs.

7


3.4. TWO KINDS OF UPGRADE SEQUENCE

3.4.1 UPGRADE SEQUENCES

The NE upgrade (RNC or Node B) procedure follows 2 upgrade sequencing

according to the period of the upgrade:

1 Multiple leaps upgrade process

For upgrade performed during the FOA period (between DR4/CuR DR5/ChR), the

multiple leaps upgrade process is kept to de-correlate the potential problems

and allow an efficient troubleshooting. First bond corresponds to the NE version n

with features xyz activated to NE version n+1 with features xyz activated,

following bonds corresponding to NE version n+1 with features xyz activated to NE

version n+1 with features xyzabc activated.

2 Single leap upgrade process

For the upgrade performed after the DR5/ChR declaration, the single leap upgrade

process is introduced to minimize the service impacts. This single bond

corresponds to the NE version n with features xyz activated to NE version n+1 with

features xyzabc activated.

Node B Vn features xyz

Node B Vn+1

features xyzabc

Time

Upgrade Node B Vn Vn+1 and feature abc

WAUT WO + WPS WO Merged

Build

Node B Vn features xyz

Node B Vn+1 features xyz

Node B Vn+1 features xyzabc

Node B Vn+1 features xyza

Node B Vn+1 features xyzab

Time

Upgrade Node B VnVn+

Add feature a Add feature b Add feature c

WAUT WO

Build

WPS WO

Depends

WPS WO

Depends

WPS WO

Depends

8

3.4.2 HOW TO PERFORM SINGLE LEAP UPGRADE PROCESS

The 'Single Leap' upgrade would be used by customers after they have successfully

upgraded a BTSEquipment to the new release, have used multiple feature

activation steps/work orders on the upgraded BTSEquipment and they are satisfied

that both the upgrade and new features are working correctly. With this level of

confidence, they can then perform a 'Single Leap' upgrade so that they can

simultaneously upgrade and activate the new features on all other BTSEquipment

upgrades.

The customers have either already used WPS or used a sanitized provisioning tool to

successfully activate the new features on the first BTSEquipment and generated

the Single Leap work order.

When performing a 'Single Leap' upgrade, the user 1) selects the target BTSEquipment

to be upgraded, 2) selects the target release that they want the BTSEquipment

upgraded to and 3) selects the Single Leap work order that contains additional

provisioning that they would like to have added to the configuration during the

upgrade.

Figure 2. Do Single Leap upgrade

All of the provisioning changes contained in the Single Leap work order will be

successfully included in the WAUT generated work order used during upgrades. The

result is that after the NE has been upgraded, the new provisioning changes will

have been automatically implemented.

Requirements:

The Single Leap work order must only contain provisioning changes specific to the

new target release. (i.e when upgrading from UA7.1 to UA8.1, the Single Leap

work order must be configured for the UA8.1 release.)

Single Leap work orders only apply to the RNC and BTSEquipment objects and must

not contain any INode provisioning changes.

9


3.5. UPGRADE SEQUENCE TABLE

The following table describes all the steps to be performed in order to complete the

Node B upgrade. None of them should be skipped unless otherwise specified. All

these steps must be performed one after the other (except for CM XML file

upgrade phase that can be performed in parallel with the download step). The

table indicates for each step its duration and on which page the detailed

description can be found. The fallback step is also indicated if applicable.

NON D

ISRUPTIV

E O

PERATIO

NS.

SHOULD B

E P

ERFORM

ED O

UTSID

E T

HE

MAIN

TENANCE W

INDOW

.

PRECHECKS , D

OW

NLOAD a

nd P

ROVIS

IONIN

G

UPGRADE

Upgrade Steps Duration (minutes)

Sheet page

NOK step

Check all prerequisites are ok one day before the upgrade

- 2 -

Download Node B software from DVD-ROM/Local Files to SRS

20 13 -

Check Node B alarms 30 18 -

Backup Node B in the OAM database is mandatory 5 21 -

Export the Node B CM XML file from OAM database 5 23 -

Upgrade the Node B CM XML file 10 26 -

Download the new software with new MIB to Node Bs 10 to 130* 32 -

Beginning of the Maintenance Window

M

AIN

TENANCE

WIN

DOW

Set the Node B maintenance mode On (optional) 5 41 -

OUTAGE

5

min

ute

s Activate the Node B software and MIB

15 42 See section 3.6

POST

CHECKS

Set the Node B maintenance mode Off (optional) 5 41 -

Check Node B alarms

30 18 See section 3.6

Backup Node B in the OAM database is mandatory 5 21 -

Table 4. Upgrade sequence

* See the table given in section 3.3.1.4 for more details about the durations

10


3.6. FALLBACK SEQUENCE TABLE

FALLBACK

50 m

in

FALLBACK STEPS Duration (minutes)

Sheet page

Backup the upgraded configuration in case reverse fallback is needed 10 21

Fallback Node Bs 10 48

Check Node Bs alarms 30 18

Table 5. Fallback sequence

* See the table given in section 3.3 for more details about the durations

11


4. SHEETS

TO PERFORM THE UPGRADE OPERATIONS,

REFER TO THE SEQUENCE TABLE.

Operations sheets are not always in execution order. Always refer to the operations sequence table to determine the correct sheet and the correct input parameter values.

12

HOW TO

PRESENTATION

The purpose of this sheet is to describe how to perform some basic operations, which have to be performed during the execution of the procedure.

INITIAL STATUS

The OAM Main Server is running and the GUI is accessible from a WMS OAM Client.

ACTIONS

P1. To launch the Wireless Access Upgrade Tool (WAUT):

- WAUT is supplied with an installer utility which will typically install to a disk location such as C:/Program Files/WAUT. Launch the executable file (wips.exe) in this directory.

P2. To launch the Sessions Manager console:

- Log into WMS OAM GUI and open the corresponding layout. - From the WMS OAM GUI, choose Configuration | Sessions Manager menu option.

The console displays the currently active sessions. P3. To launch the Equipment Monitor:

- Log into WMS OAM GUI and open the corresponding layout embedding the BTS to be checked. - Select the BTS on which the equipment monitor is to be launched. - Right click on the selection and select Equipment Monitor.

Figure 3. Launch the Equipment Monitor

The BTS Equipment monitor window then appears. It displays the BTS module states.

13

DOWNLOAD SOFTWARE FROM DVD-ROM/LOCAL FILES TO SRS

PRESENTATION

The purpose of this sheet is to describe how to download the new software version from the DVD-ROM/Local Files to the SRS (Software Repository Service) disk.

INITIAL STATUS

The OAM Main Server is operational and WMS GUI is accessible on a Client. The SRS is operational. The DVD-ROM drive must be local on the WMS OAM Client or the Local Software Delivery Files present on the WMS OAM Client.

ACTIONS

ON THE OAM CLIENT:

1.On the PC OAM Client: - Open a web browser. - Connect to the following Web Site: http://hostnameSRS:8080/srm/ (where hostnameSRS is the hostname of the SRS server). - Enter the username and password of the WMS OAM Client administrator account. The following page will be displayed:

Figure 4. SRM GUI

On this first page, it is possible to see the available free space on the SRS server. 2.Check the available free space on the SRS server (see the screen above). The SRS must have at least 1 GB of free space.

Free space on the SRS

server

Install Software

Release...

14


If there is not enough free space, see the troubleshooting section to know how to remove unused software from the SRS. 3.Click Install Software Release... - the following window appears:

Figure 5. SRM install software page

4.Download software to SRS. There are two types of delivery installation: (a) CD-ROM/DVD-ROM (b) Local Software Delivery Files CD-ROM/DVD-ROM

- Select the option CD-ROM/DVD-ROM for the delivery data input then select the DVD-ROM drive (Note that on a Windows client all drive roots are listed alphabetically, with the first item in the list [e.g. A:\] being displayed by default. So choose the right DVD-ROM drive according to the Client configuration).

- Insert the DVD-ROM into the SRM client DVD-ROM drive and wait for a few seconds. Then click OK on the window. The data transfer page will be displayed.

Local Software Delivery Files Note: Supported format file: *.zip, *.tar.Z, *.tar.gz

- Select the option Local Software Delivery Files for the delivery data input then click Add

- In the popup file choose window, select the compressed files. The selected

files will be added to the file list field.

15


Figure 6. SRM install software page for Local Software Delivery Files

- Then click OK on the window. The data transfer page will be displayed.

The status of the data transfer is displayed as follows:

Figure 7. SRM install software data transfer page

- The following message is displayed when the installation completes successfully:

Figure 8. SRM installation successful page

- Installation details and result are also displayed in the monitor window:

16


Figure 9. SRM installation details and result

- Close the window above, then eject and remove the DVD-ROM from the DVD-ROM drive.

WARNING: For PC Windows XP SP2, if the PC is equipped with a firewall like Cyberarmor or McAfee, the software download operation can be blocked by the firewall. As a consequence, immediate stopping the Cyberarmor Profile is recommended. (Please right click on the Cyberarmor, select menu "Stop Profile" and for McAfee please contact PC administrator).

TROUBLESHOOTING

1- In case of problem when connecting to http://hostnameSRS:8080/srm/, make sure that the java.policy file has been properly updated as described the document referenced in [R1]. 2- If there is not enough free space, it is possible to remove old deliveries from SRS using SRM. To do this, the operator can:

Browse through the deliveries on SRS (from http://hostnameSRS:8080/srm/ page).

Select the unneeded deliveries.

And remove them from the SRS by clicking Delete Selected:

Figure 10. SRM delete software page

WARNING: Do not remove any software version being used on the network (active or passive).

17


FINAL STATUS

The software has been downloaded from DVD-ROM/Local Files to the SRS disk.

18

CHECK NODE B ALARMS

PRESENTATION

The purpose of this sheet is to describe how to check Node B active alarms. This sheet can be executed periodically during the upgrade in order to detect pending alarms, but is especially aimed at verifying any new alarms that could have been raised just after the upgrade.

INITIAL STATUS

The OAM Main Server is running and the GUI client is accessible.

ACTIONS

1. To display the alarms: - Log into WMS GUI and open the corresponding layouts. - Select the Node Bs on which the alarms must be checked. - Right-click on the selection and select Show Alarms from the context menu.

The Alarm window will then appear. It allows the operator to investigate the alarms that could prevent starting the upgrade on the network element.

Figure 11. How to open Alarm window

There should be no outstanding alarms on the Node Bs before and after the upgrade. If there are some residual alarms, each one must be investigated before making the decision to proceed with the upgrade.

2. Before the upgrade, using the OSI State Reporting window available in the menu Fault | Radio Access | OSI State reporting on whole layout, to see the FDDCells locked, select the RNC parent and note all faulty FDDCells.

19


Figure 12. OSI State Reporting window

A faulty FDDCell occurs on a Node B that is not working properly. After the upgrade, compare the faulty FDDCells list to the one before the upgrade. All extra faulty FDDCells might be caused by a problem during the Node B upgrade and will need to be investigated.

WARNING: All BTSCells locked before an upgrade remained locked after upgrade.

3. Check active calls in progress on Node B or FDDCell to verify overall call processing

executed by Node B(For all Node B upgraded in parallel you check calls at RNC side and for one Node B upgrade then on its linked FDDCells located at the RNC side as well.):

- Execute "How to" action P3 To launch the Equipment Monitor - Select RNC Tab and Dynamic Data lower right tab

20

Figure 13. Check calls at RNC side

Figure 14. Check calls on linked FDDCells

FINAL STATUS

Node B alarms and faulty FDDCells have been analysed and noted. Some Node B upgrades have been postponed if needed.

RNC tab

Dynamic Data tab

RNC tab

Dynamic Data tab

21


BACKUP NODE B IN THE OAM DATABASE

PRESENTATION

This sheet describes how to backup the initial OAM data. The backup is performed on a RNS basis: all the Node Bs present under a given RNC will be backed up. If the Node Bs to be upgraded are scattered on several RNS, this sheet is to be performed for each one of these RNS. The restoration of this data (if needed) will be performed on a Node B by Node B basis.

INITIAL STATUS

The OAM Main Server is running and the GUI is accessible from WMS OAM Client.

ACTIONS

1. If not already done, open a WICL console. To do so perform the following:

- Log into WMS OAM GUI and choose the Configuration | Wireless Internet Command Language (WICL) menu item.

2. Backup the RNS OAM database: In the WICL console type:

0 # RNC DbBackupRNS

3. When the command is complete a message similar to the following is displayed:

DbBackupRNS OK

The backup result was stored at:

dfs:/utran/neBackup/backup.rnc_RNC_333.08_00_00.2011.01.27..13.41.09+0100.17258.lst

The command generates one .lst file where is stored the .bkp files that will be used to restore BTSEquipment. To retrieve the backup file, replace dfs by /opt/nortel/data directory and display the file under a UNIX console. For instance:

# cat /opt/nortel/data/utran/neBackup/backup.rnc_RNC_333.08_00_00.2011.01.27..13.41.09+0100.17258.lst dfs:utran/neBackup/RNC-/backup.08_00_00.20110127134124.bkp

dfs:utran/neBackup/BTSEquipment-/backup.07_01_00.20110127134135.bkp

The file used to restore BTS is:

dfs:utran/neBackup/BTSEquipment-/backup.07_01_00.20110127134135.bkp

22


FINAL STATUS

The Node Bs data is backed up and available in case a fallback is needed.

23

EXPORT NODE B CM XML FILE FROM OAM DATABASE

PRESENTATION

The purpose of this sheet is to describe how to export from the OAM database the Node B data to be upgraded. This sheet must be performed once whatever the number of Node B being upgraded.

INITIAL STATUS

The WMS OAM Client GUI is available.

ACTIONS

1. If not already done, log in to the WMS OAM Client. 2. Select all the RNCs managing the Node Bs to be upgraded, right-click on them and

choose the Configuration | CM XML | Export NE Grouping option like this:

Figure 15. Export NE Grouping

3. The following window appears, listing the RNCs to be exported; it allows selection of:

The output directory relative path (from /opt/nortel/data/cmXML/) on the primary main server. This directory is referred to as in the rest of the procedure.

The CM XML Export file. A single .xcm file will be generated.

24

Figure 16. CM XML Export window

Select all the RNCs in the top of the window, enter the target directory, the CM XML file name, check the Provisioning and the Customer boxes then launch the Export command by clicking on Export now.

The export progress is displayed in the Command Manager window:

Figure 17. Command Manager

Provisioning parameter to

check

Target directory

Target CM

XML file

Customer parameter to check

25


Once the progress bar reaches 100%, check in the generated report that there is no error, then close the command manager and CmXML windows.

4. Using a FTP client, transfer the exported CM XML file from the Main server /opt/nortel/data/cmXML/ directory to a directory on the PC.

This directory on the PC will be referred as the in the rest of the procedure.

FINAL STATUS

A single CM XML file is available in the directory on the PC.

26


UPGRADE THE NODE B CM XML FILE

PRESENTATION

This sheet describes how to upgrade the initial CM XML file. For this purpose the Wireless Access Upgrade Tool (WAUT) and WCF file are used. Note: The WAUT tool and WCF file should be in line according to the used OAM release note.

INITIAL STATUS

The initial CM XML file is available in the directory on the PC.

ACTIONS

1. If not already done, launch the WAUT. Important: All the following operations must be executed on a blank network. Save and exit all opened workorders and start with a new workspace as shown below:

Figure 18. Launch Wireless Access Upgrade Tool

2. Import the initial CM XML file: - Choose the File | Import and Export menu option:

27

Figure 19. Import and export

- Select the Import snapshot option, and then click Next:

Figure 20. Select the Import snapshot option

- Select the Replace initial snapshot and discard existing workorders option, then click Next:

28


Figure 21. Select the Replace initial snapshot and discard existing workorders mode

- Using the Browse button, select the initial CM XML file from the directory, then click Next:

Figure 22. Select the initial RNC CM XML file

- Ignore the filter (click next) and then select No, proceed without saving if nothing is to be saved or Yes, save the workspace if some data is to be saved, then click Start:

29


Figure 23. Save the workspace option

- The window indicating the import progress appears:

Figure 24. Import progress window

Once the progress bar reaches 100% (Done), check in the generated report that there are no errors, and then close the window.

3. Perform the CM XML file upgrade: - Click on the Network tab, select the specific Node B that you want to upgrade, and select the NE Provisioning Upgrade Operation.

- Click on the Network tab, select the Network tree, and select the NE Provisioning Upgrade Operation. This will upgrade all of the BTSs.

30

Figure 25. Select the NE Provisioning Upgrade Operation

- The NE Provisioning Upgrade Operation window appears.

Figure 26. NE Provisioning Upgrade Operation window

The upgraded CM XML file should be generated in the selected output directory. The full directory is indicated in the WAUT window. Select the target release (Upgrade to version field): 08_01_00. Click OK to launch the operation. This will takes a few minutes to complete. Since the RNCs will already have been upgraded, the output file only has the upgraded BTS data independent of RNC version.

Ensure the NE Provisioning Upgrade Operation completes without errors. To close this window, click Close.

1- Click on the Network tab

3- Click on the NE Provisioning Upgrade Operation

2- Select the

specific Node-B

2- Select the Upgrade target

version

1- Output directory (click Browse to

change)

31


In the output directory, WAUT will generate one new file NonPassportWO__.xwo.

4. Using a FTP client, transfer from the PC /upgraded directory the upgraded CM XML

file to the /opt/nortel/data/cmXML//upgraded directory on the Main server.

FINAL STATUS

The CM XML file with the new provisioning is ready to be imported into the OAM database.

32


DOWNLOAD SOFTWARE TO NODE B

PRESENTATION

The purpose of this sheet is to describe the download command. This command allows the user to download the new software to Node Bs.

INITIAL STATUS

The new Node B software to be downloaded is available on SRS. The WMS GUI Client is available. Check that no Session is currently active for the Node Bs (See the sheet "How to", action P2 for details on how to open the Sessions Manager).

ACTIONS

1. If not already done, log in to the WMS GUI under administrator user.

2. There are two ways to launch Download wizard:1)From the menu bar, choose Configuration | Radio Access | Software | Download.2)From network layout right-click the selected nodes or group ,choose Configuration | Software | Download.

3. The first page introduces the download wizard. Click Next.

Figure 27. Download wizard: Introduction

4. On the Select the Network Element type page, when launch from menu bar, all kinds of element type can be chosen, select the Node B option and click Next:

33


Figure 28. Download wizard: Select the Network Element type(from menu bar)

When Launch from right-click menu, the network element type cant be chosen, click Next:

Figure 29. Download wizard: Select the Network Element type (from right-click menu)

5. On the Select Software Version to Download page, select the software version from the list and click Next:

Figure 30. Download wizard: Select Software Version to Download

Note: The NodeB architect type, which this software is applicable to iBTS sub-family, is added in this window. Existing or new software without a list of applicable Node B architect type (existing or new ones) will be display in the software selection tree gadget under ALL. Software restricted will be classified in the tree gadget on a per Node B type basis.

6. On the Select Search Method page, select the Define Search Filters option and click Next:

34


Figure 31. Download wizard: Select Search Method

It is possible to skip the defined filter. In this case, select Browse All Nodes

option and move directly to step 10.

7. On the Set Active Version Filter page, select the current Running release of the Node Bs to be upgraded, add it to the right-hand pane and click Next:

Figure 32. Download wizard: Set Active Version Filter

8. On the Set RNC filter page, select the RNCs to which the Node Bs to be upgraded are parented, add them to the right-hand pane and click Next:

35


Figure 33. Download wizard: Set RNC filter

9. On the Search Criteria Summary page, click Retrieve:

Figure 34. Download wizard: Search Criteria Summary

10. On the Retrieved Node(s) page, when launch from menu bar the retrieved nodes are all Node Bs detected in network, select the Node Bs on which the download operation should be performed, add them to the right-hand pane and click Next:

Figure 35. Download wizard: Retrieved Node(s)

When launch from right-click menu, the retrieved nodes just are the selected Node Bs in network layout, Following figure shows the selected Node Bs are BTS_710_1,BTS_710_9. Select the NodeBs on which the download operation should be performed, add them to the right-hand pane and click Next.

36


Figure 36. Download wizard: Retrieved Node(s)

WARNING: arrows used for selection: > (moves only selected NEs from available Node(s) panel to Selected Node(s) panel for SW download) >> (transfers ALL NEs from Available Node(s) panel to Selected Node(s) panel for SW download, independent of any selection done in the Available Node(s) panel.

11. On the Download Action Require page, select the Download option and click Next:

Figure 37. Download wizard: Download Action Require

12. On the Node B MIB Modification page, select with new MIB option and click the Select CM_XML File button. In the popup window, select the CML XML file (NonPassportWO__.xwo generated by WAUT) and click Select. Then click Next to go to the next page:

37


Figure 38. Download wizard: Node B MIB Modification

13. On the Search Criteria Summary page, check the summary of the Node Bs on which the download will be performed:

Figure 39. Download wizard: Search Criteria Summary

Check the selection and click Download to validate it. Otherwise, click Back to modify the selection.

14. The last page of the wizard shows a success message. Check the box that allows the Command Manager to be launched automatically and click Finish to exit the wizard. When launch from right-click menu ,if the selected nodes in network layout are two or more than two kinds of element type nodes , wizard will show the Next button , click Next to the Select the Network Element type page again to download the next kind of element type nodes you selected.

15. Once the download wizard is closed, the Command Manager appears allowing you to monitor the download process:

38


Figure 40. Download:Command Manager

Note that the Command Manager can also be launched from the Configuration menu of the GUI.

16. Wait for the end of the download. When the download ends, the status will indicate Successful for each selected Node B.

WARNING: No database modification could be executed until software is successfully activated or upgrade session is aborted from Configuration | Radio Access | Software | Inventory & Upgrade Session NSP menu.

Note:

An upgrade session encapsulates a series of operations in order to perform a NE upgrade (RNC or BTS). It includes the software file transferring from OAM to the network element and the software activation phases.

Pre-semantic WAUT upgraded workorder check and Pre-software download (optional):

If the user wants to download its software to the Node B in order to prepare its Node B with new MIB inter release software upgrade, it has the possibility to do it out of an upgrade session but in a software download maintenance window (due to database modification freeze during such download) by executing the following steps: - Execute all the steps of the download wizard with the with new MIB" option and pre-generated WAUT upgraded workorder for semantic check verification.

39


- VERY IMPORTANT: when software download is successfully completed, execute "Abort upgrade session", Software Download Exit Step. - At upgrade time, it will have to re-launch again all the listed steps of its download with the with new MIB" option in order to perform the MIB preparation while software download will not be performed since the Node B software download is differential.

Software Download Exit Step:

If the software download has been completed, but the Node B activation of the downloaded software is no longer required, or if a wrong software load has been downloaded, the following steps can be used to exit the DOWNLOAD_COMPLETED state. From the menu bar of WMS NSP GUI, choose Configuration | Radio Access | Software | Inventory & Upgrade Session.

Figure 41. How to open Inventory & Upgrade Session

Then select the current running software.

Figure 42. Select the current running software

Select the Node B where the upgrade status is DOWNLOAD_COMPLETED, in the "Details" lower window. Click on Abort upgrade session.

40


Figure 43. Select NE with status DOWNLOAD_COMPLETED

Check Node B status in "Details" lower window changed from DOWNLOAD_COMPLETED to IDLE.

Figure 44. The inventory after execute Abort upgrade session

TROUBLESHOOTING

In case an error message is encountered, see the Appendix A: Upgrade messages section (page 54) for the required remedial action. Most of the time, for minor issues a retry from the beginning of this sheet for the failed Node Bs will be enough to complete the Node B upgrade.

FINAL STATUS

The download operations have been performed.

41


SET THE NODE B MAINTENANCE MODE ON OR OFF (OPTIONAL)

PRESENTATION

Before proceeding with the upgrade, Node Bs can optionally be set to maintenance mode. This will indicate to all other users that an important operation is taking place on those Node Bs. After the upgrade is complete, Node Bs should be set to normal mode. NB: When a Node B is in maintenance mode, no alarms are raised on it at GUI level.

INITIAL STATUS

The OAM Main Server is running and the GUI is accessible on the local machine.

ACTIONS

Select the Node Bs, right click and select Set Maintenance Mode On. To set back to normal mode click on Set Maintenance Mode Off.

Figure 45. Set Maintenance Mode On

FINAL STATUS

Maintenance mode for the Node Bs has been turned on or off.

42


ACTIVATE THE SOFTWARE AND THE NEW MIB

PRESENTATION

The sheet describes how to activate both the new MIB and the previously downloaded software.

INITIAL STATUS

The new Node B software to be activated is downloaded successfully completed on the Node B.

The WMS GUI Client is available.

ACTIONS

1. If not already done, log in to the WMS GUI under administrator user. 2. There are two ways to launch Activate wizard:1)From the menu bar, choose

Configuration | Radio Access | Software | Activate. 2)From network layout right-click the selected nodes or group ,choose Configuration | Software | Activate.

3. The first page introduces the activation wizard. Click Next.

Figure 46. Activation wizard: Introduction

4. On the Select the Network Element Type page, when Launch from menu bar, all kinds of element type can be chosen, select the Node B option and click Next:

43


Figure 47. Activation wizard: Select the Network Element type

When launch from right-click menu, the network element type cant be chosen, click Next:

Figure 48. Activation wizard: Select the Network Element type

5. On the Select Search Method page, choose the Define Search Filters option and

click Next:

Figure 49. Activation wizard: Select Search Method

It is possible to skip the defined filter. In this case, select Browse All Nodes option and move directly to step 8.

6. On the Set Passive Version Filter page, select the passive version of the Node Bs to

be upgraded, add it to the right-hand pane and click Next:

44


Figure 50. Activation wizard: Set Passive Version Filter

7. On the Set RNC filter page, select the RNC where the Node Bs to be upgraded are

connected, add it to the right-hand pane and click Next:

Figure 51. Activation wizard: Set RNC filter

8. On the Search Criteria Summary page, click Retrieve:

Figure 52. Activation wizard: Search Criteria Summary

9. On the Retrieved Node(s) page, when launch from menu bar, the retrieved nodes

are all Node Bs can be activated detected in network. Select the Node Bs on which

45


the activate operation should be performed, add them to the right-hand pane and click Next:

Figure 53. Activation: Retrieved Node(s)

When launch from right-click menu, then the retrieved nodes just are the selected

Node Bs can be activated in network layout . Following figure shows the selected node

is BTSbj_21_1_.

Figure 54. Activation: Retrieved Node(s)

WARNING: arrows used for selection: > (moves only selected NEs from available Node(s) panel to Selected Node(s) panel for SW activation) >> (transfers ALL NEs from Available Node(s) panel to Selected Node(s) panel for SW activation, independent of any selection done in the Available Node(s) panel.

10. On the Search Criteria Summary page, consult the summary of the Node Bs on

which the activate operation will be performed:

46


Figure 55. Activation wizard: Search Criteria Summary

Check the selection and click Activate now to validate it. Otherwise, click Back to modify the selection.

11. The last window of the wizard shows a success message. Activate the check box that allows the Command Manager to be launched automatically and click Finish to exit the wizard. When launch from right-click menu, if the selected nodes in network layout are two or more than two kinds of element type nodes, wizard will show the Next button, click Next to the Select the Network Element type page again to activate the next kind of element type nodes you selected.

12. Once the activation wizard is closed, the Command Manager will appear, allowing

you to monitor the activation progress:

Figure 56. Activation: Command Manager

47


13. Wait for the end of the activation. When the activation ends, the status will indicate Successful for each selected Network Element. Please note that the Node Bs restart during the software activation, and when the activation progress indicates 100%, it does not include this Node B restart. Check the WMS GUI layout to monitor the Node Bs reconnection. Moreover, the Command Manager and the Inventory & Upgrade Session window must both indicate the completion of the activation.

Note that when the supervision is lost, the critical alarm Loss of supervision is also generated on the BTSEquipment object. Note: If the MAINTENANCE flag is set on ON, you cannot see the new alarms rose on that object, and the blue colour of LOSS OF SUPERVISION is also not seen.

TROUBLESHOOTING

In case an error message is encountered, see Appendix A: Upgrade messages (page 54) for the required remedial action. Most of the time, for minor issues a retry from the beginning of this sheet for the failed Node Bs will be enough to complete the Node B upgrade.

FINAL STATUS

The activation operations have been performed.

Note: Once the upgrade is finished, please dont forget to Check Node B alarms on page

18.

48

FALLBACK THE NODE B SOFTWARE

PRESENTATION

This sheet describes how to fallback the Node Bs software. This includes both how to restore the initial OAM data and how to downgrade the Node Bs to the initial software before the upgrade. The restore is performed on a Node B by Node B basis. This sheet is therefore to be executed once for each Node B to be restored. Note that a backup of the upgraded configuration is done in case reverse fallback is needed.

INITIAL STATUS

The OAM Main Server is running and the GUI is accessible from a WMS OAM Client.

ACTIONS

1. Lock the OAM-Node B link (Node B OAM link administrative state = locked). To do this select all Node Bs, right click, choose Configuration | Set NE's OAM Link Administrative State, click on "Lock".

2. If not already done, open a WICL console. From the menu bar, choose Configuration | Wireless Internet Common Language

(WICL).

3. Restore the Node B in the OAM database: In the WICL console:

0 # BTSEquipment dbRestore dfs:utran/neBackup/BTSEquipment-/

Note: The backup file to be used for dbRestore is the one generated before upgrade, see

Backup NodeB in the OAM database sheet.

4. When the command is complete a message similar to the following is displayed:

dbRestore OK, the file used for restoration is dfs:utran/neBackup/BTSEquipment-BTSM1_512_009/backup.04_02_00.20050706150550.bkp

5. Check if the automatic upgrade flag is enabled on the targeted Node Bs. To do so the

equipment monitor can be used:

Figure 57. Launch Equipment Monitor

49

Figure 58. Equipment Monitor window

WICL can also be used to check the flag:

If not already done, open a WICL console and enter the following command:

0 # BTSEquipment get automaticupgrade

If the automatic upgrade flag it is disabled then enable it:

0 # BTSEquipment SetOnLine automaticupgrade enabled

Note: a warning "job terminated with warning" may appear after entering the above

command. This warning is not an error, and can be ignored. 6. Unlock the OAM-Node B link (Node B OAM link administrative state = unlocked). See

action 1 above. NB: The link is fully open when the Node B icon in the layout no longer blue. Wait for the icon to change from blue before proceeding.

7. An upgrade (download + activation) is automatically triggered by the OAM if the

corresponding flag is activated on the target Node B.

To check the status of the upgrade, from the GUI menu bar, choose Configuration | Radio Access | Software | Inventory & Upgrade Session.

50


Figure 59. Inventory & Upgrade Session window

After Node B fallback, MIB rebuild required due to 2 alarms below:

- MIB state: NOT BUILT. - MIB number received from NE is different from the MIB number stored in the

active view.

FINAL STATUS

The Node B software and data in the OAM database have returned to the version before the upgrade.

51


HOW TO USE THE WAUT UPGRADE REPORT

PRESENTATION

This sheet describes how to use the WAUT upgrade report. This is just example to show the variant CM object/attribute upgrade cases in CM model. The WAUT upgrade Report allows users to review the provisioning changes performed during an upgrade and determine how the migrated values have been determined. In the figure you can see the following information:

Figure 60. WAUT upgrade report1

Parameter isNmoClass3Allowed - was set as value 'false' in the previous release, is now

set as value 'false' in the new release and the parameter value was set by the WAUT tool upgrade Wizard

Parameter inMocnActivated - was not present in the previous release and is has been set to 'false' by the WAUT Template during the upgrade.

However, it is important to note that usually when upgrade from one release to the

next, parameter names can change between the releases. In the figure below, parameter 'allowed' exists in UA6.0 but has been changed to parameter 'allowedList' from UA7.1. So when look at the provisioning for 'allowed' the user will see a value in the previous release but no value being currently set by the Upgrade Wizard. This is an easy case as both parameters show up together but there are other instances when the parameter names are not so closely aligned. In this example the user can see that parameter 'allowedList" has been changed to now contain a two element array, that

52


the values are set by the WAUT Template and that the original parameter value has been preserved.



53


In the example above, creation of the SCCPCH/2 instance was created using a 'Single

Leap' workorder at the time of the upgrade. As a result, the 'Previous version" field will contain no information regarding the source of the changes.

54


APPENDIX A: UPGRADE MESSAGES

Message displayed in

OAM

Meaning

Additional OAM action

Additional information

Software already running

The requested software is already running. No need to download. No need to activate.

No Activation is not necessary; the software is already active

Software already on passive FFS.

The requested software is already downloaded on the NODE B. It is only necessary to activate this version.

No The software is already present in the passive. Only the activation is necessary

Download already in progress on this BTS

A download is requested by the OAM while a download is already on-going on the Node B. OAM download is refused.

Retry the upgrade. This may occur when a board is plugged into the rack and must be upgraded. If the OAM operator decides to download during the automatic internal upgrade, such an error is returned to the OAM.

Download already in progress on this BTS (same id session)

A download is requested by the OAM while a download is already on-going on the Node B. OAM download is refused.

Retry the upgrade. This may occur when a board is plugged into the rack and must be upgraded. If the OAM operator decides a download during the automatic internal upgrade, such an error is returned to the OAM.

BTS internal failure This is a Node B internal error. Retry the upgrade. If the problem persists, call your next level of support.

Inconsistency between BTS ID stored in OAM database and BTS ID.

The Node B serial number sent by OAM does not match the true Node B serial number.

Check serial number. Retry a download with correct configuration. If the problem persists, call your next level of support.

Note: The Node B serial number has already been exchanged and checked during first messages exchanged between OMC and Node B.

The RAM disk of the BTS is full even after 40 retries.

There is no room in Node B CCM Ram disk to store the file (already 40 retries done).

Reset the Node B and retry the upgrade. If the problem persists, call your next level of support.

Download process is automatically aborted. Note that this error may come from the fact that a file is too big for the Node B running version, or the Node B ram disk already contains too many files. A Node B reset would clean this disk.

The size of a file to be transferred has not the expected size

Incoherence in the software delivery.


Incoherence between file size in File0 and size of the downloaded file.

File 0 parsing problem The Node B cannot read the software delivery.


The Node B cannot parse the File0. Either the file is incorrect, or the downloaded software is incompatible with the running version. Download aborted.

FTP Error A FTP error detected during the download.


Download Protocol Error

Error during Download protocol (number of files incorrect, protocol error ...)


This might also be due to a corrupted DVD-ROM software load.

FFS Error Flash File System error on the Node B.

No Contact next level support.

ERROR: "Activation failed"

Activation failed (for example due to FFS problem)


ERROR: "Activation failed: BTS not ready"

Activation failed Reset the Node B and retry the upgrade. If the problem persists, call your next level of support.

Table 6. Upgrade messages

55



W-CDMA Upgrade Procedure



Alcatel-Lucent Internal Proprietary Use pursuant to Company instruction

Copyright 2003-2013 Alcatel-Lucent. All rights reserved.

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is write

protected; it may be altered only by authorized persons. While copies may be printed, it is not recommended.

Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be

regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent.

Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained

herein confidential, shall disclose the information only to its employees with a need to know, and shall protect

the information from disclosure and dissemination to third parties. Except as expressly authorized in writing

by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have

received this document in error, please notify the sender and destroy it immediately.

All other trademarks are the property of their owners.

Document number: NN-20500-149 Document issue: 07.09/EN Document status: Standard Product release: OAM08.1 Date: January 2013

Documents

1_V1_Alcatel-Lucent 9311, 9312, 9322, 9326, 9332 Node B - Software Upgrade Procedure Using OAM 8.1_ Inter Release Upgrade