0w-cdma product family alcatel-lucent 9313 micro node b and 9314 pico node b - software upgrade...

8/12/2019 0W-CDMA Product Family Alcatel-Lucent 9313 Micro Node B and 9314 Pico Node B - Software Upgrade Procedure

1/44

NN-20500-151

Wireless Service Provider Solutions

W-CDMA

Upgrade Procedure

Alcatel-Lucent 9300 W-CDMA Product Family

Alcatel-Lucent 9313 Micro Node B and 9314 PicoNode B - Software Upgrade Procedure UsingOAM7.1.3

NN-20500-151 05.03/EN Approved-Standard April 2011


2/44


3/44

Publication history i

Copyright 2003-2011 Alcatel-Lucent Alcatel-Lucent 9300 W-CDMA Product Family - Alcatel-Lucent 9313 Micro Node B and9314 Pico Node B - Software Upgrade Procedure Using OAM7.1.3

PUBLICATION HISTORY

SYSTEM RELEASE: OAM07.1.3

April 2011

Issue 05.03/EN, Approved-Standard

January 2011

Issue 05.02/EN, Approved-Preliminary

December 2010

Issue 05.01/EN, DraftDocument creation


4/44


5/44

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. 9313 MICRO/9314 PICO NODE B UPGRADE ..............................................................3

3.1.

IMPORTANT INFORMATION .........................................................................................................33.2.

UPGRADE PREREQUISITES ........................................................................................................3

3.2.1

RECOMMENDATION...........................................................................................................4

3.2.2

MANDATORY RESOURCES NEEDED FOR THE UPGRADE ........................................................4

3.3.

UPGRADE OVERVIEW ................................................................................................................4

3.3.1

SOFTWARE UPGRADE PROCEDURE STEPS ..........................................................................5

3.3.2

FALLBACK STEPS (IF NEEDED) ...........................................................................................6

3.4.

TWO KINDS OF UPGRADE SEQUENCE..........................................................................................8

3.5.

UPGRADE SEQUENCE TABLE......................................................................................................9

3.6.

FALLBACK SEQUENCE TABLE .....................................................................................................9

4. SHEETS ........................................................................................................10

HOW TO .......................................................................................................................................11

DOWNLOAD SOFTWARE FROM DVD-ROM/LOCAL FILES TO SRS......................................................12

CHECK 9313MICRO/9314PICO NODE BALARMS ............................................................................17

DOWNLOAD SOFTWARE TO 9313MICRO/9314PICO NODE B............................................................20

ACTIVATE THE SOFTWARE ....................................................................................................................25

FALLBACK 9313MICRO/9314PICO NODE BSOFTWARE ..................................................................30

APPENDIX A: UPGRADE MESSAGES...............................................................................33


6/44


7/44

Table of content v


LIST OF FIGURES

Figure 1. Alarm CONFIGURATION NOT SYNCHRONIZED...................................................................3

Figure 2. Launch the Equipment Monitor ...............................................................................................11Figure 3. SRM GUI .................................................................................................................................12Figure 4. SRM install software page ......................................................................................................13Figure 5. SRM install software page for Local Software Delivery Files .................................................14Figure 6. SRM install software data transfer page .................................................................................14Figure 7. SRM installation successful page ...........................................................................................14Figure 8. SRM installation details and result..........................................................................................15Figure 9. SRM delete software page......................................................................................................15Figure 10. How to open Alarm window...................................................................................................17Figure 11. OSI State Reporting window .................................................................................................18Figure 12. Check calls at RNC side .......................................................................................................18Figure 13. Check calls on linked FDDCells ............................................................................................19Figure 14. Launch the LMT ....................................................................................................................20

Figure 15. Select software and Executing..............................................................................................21Figure 16. Office Data Migration Result window ....................................................................................21Figure 17. Edit Planned Office Data window..........................................................................................22Figure 18. Fill the Originatinga2ea field..................................................................................................23Figure 19. Planned office data display as valid in the LMT....................................................................24Figure 20. Launch the LMT ....................................................................................................................25Figure 21. Install new software confirmation..........................................................................................26Figure 22. Apply and Commit status ......................................................................................................26Figure 23. Commit of the new changes after restart..............................................................................27Figure 24. Executing view after changes commit ................................................................................28Figure 25. Check the ALCAP status in LMT...........................................................................................28Figure 26. Rollback view in LMT..........................................................................................................30Figure 27. Apply and Commit status ......................................................................................................31

Figure 28. Commit of the new changes after restart..............................................................................31Figure 29. Fallback result .......................................................................................................................32


8/44


9/44

Table of content vii


LIST OF TABLES

Table 1. Upgrade total duration................................................................................................................6

Table 2. Maintenance Window duration...................................................................................................6Table 3. Outage duration..........................................................................................................................6Table 4. Upgrade sequence.....................................................................................................................9Table 5. Fallback sequence......................................................................................................................9Table 6. Upgrade messages ..................................................................................................................33


10/44


11/44

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 9313 Micro Node B and 9314 Pico Node B using the OAM7.1.3.

The present procedure supports the following upgrade path:

UA6.0 -> UA6.0

1.2. AUDIENCE FOR THIS DOCUMENT

- Alcatel-Lucent customers.

- Anyone who performs 9313 Micro/9314 Pico NodeB software upgrade.

2. RELATED DOCUMENTS

2.1. APPLICABLE DOCUMENTS

[A1] UMT/SYS/INF/029801 V06/EN UA7.1 UTRAN Release Note

[A2] UMT/SYS/INF/025496 V01/EN UA6.0.1 Access Network Release Note

[A3] NN-20500-053 UMTS BTS 1120 (Micro) Description

[A4] NN-20500-094 UMTS BTS 1010 (Pico) Description

[A5] NN-20500-058 UMTS BTS 1120 and BTS 1010 Operation and

Maintenance Manual

[A6] UMT/IRC/APP/007147 V01/EN UA06 UMTS BTS Product Engineering

Information - EXTERNAL

[A7] NN-20500-057 Alcatel-Lucent 9313 Micro Node B and 9314

Pico Node B: Local Maintenance Tool Manual

[A8] NN-20500-124 UMTS BTS 1120 and BTS 1010: CommandLine Tool Manual

[A9] UMT/SYS/INF/028042 V01/EN UMTS Access UA7.0 Release Notes

[A10] UMT/SYS/INF/025701 V01/EN UA6.0.2 Access Network Release Note

[A11] UMT/SYS/INF/026109 V22/EN UA6.0.5 UTRAN Release Note

2.2. REFERENCE DOCUMENTS

[R1] NN-10300-036 Alcatel-Lucent 9353 Management System -Workstation Client/Application Installation

[R2] UMT/OAM/DD/000072 FN: BTS 1120 support in WMS


12/44

2

NN-20500-151 05.03/EN Approved-Standard April 2011 Copyright 2003-2011 Alcatel-Lucent

[R3] UMT/BSS/DD/000005 UMTS IP BTS 1010 system description


13/44

3


3. 9313 MICRO/9314 PICO 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 in

parallel with this upgrade procedure.

Operations such as hardware intervention, upgrade using the LMT or configurationchanges 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 9313 Micro/9314 Pico

Node B.

WARNING 4:

The alarm CONFIGURATION NOT SYNCHRONIZED will raised on LMT, which indicates that

LMT has detected a mismatch between the reference Software package version and theexecuting version.

Figure 1. Alarm CONFIGURATION NOT SYNCHRONIZED

To clear the alarm, please refers to UMTS BTS 1120 and BTS 1010: LMT Manual [A7]

3.2. UPGRADE PREREQUISITES

WARNING 5555:

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


14/44

4


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

to the [A1] documents.

WARNING 6666:

All the prerequisites described in this chapter must be fulfilled at least one day beforethe upgrade starts.

WARNING 7777:

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

and the 9313 Micro/9314 Pico Node B to upgrade is setup in correspondence with

Engineering rules (OAM-NE network configuration and routing tables at WMS). See

[A5][A6]

WARNING 8:

Before to start any upgrade operation, verify that the firmware currently running on the

Micro Node B is compliant with the Newsoftware release you are going to upgrade yourMicro Node B to. In order to do so:1) Determine the firmware/software/hardware present on the Node B using thedocument "NN-20500-124 UMTS BTS 1120 and BTS 1010: Command Line Tool Manual",section 5.2.1 "Collect Firmware Inventory".2) Determine if the firmware needs to be upgraded referring to the Micro Node B ReleaseNotes, section 3.1 "Load Lineup". See [A1]

If a firmware upgrade is required, then you need to follow section 5.2.2 "Firmware

Upgrade" of the document "NN-20500-124 UMTS BTS 1120 and BTS 1010: Command

Line Tool Manual". See [A8]

3.2.1 RECOMMENDATION

For ease of use it is recommended to perform bulk 9313 Micro/9314 Pico Node B

upgrade on a RNS basis.

3.2.2 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 resource:one OAM site operator.

PC client:one client OAM PC or workstation.

DVD-ROM:One DVD-ROM of the new 9313 Micro/9314 Pico Node B software.

All the software (9313 Micro/9314 Pico Node B and OAM loads) used during this

procedure must be compliant with the software line-up defined in [A1] document.

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.

3.3. UPGRADE OVERVIEW

The Micro/Pico upgrade will be done using LMT launched from the WMS GUI.


15/44

5


The upgrade will be done by using the planned view: the outage will occur only at

activation by the apply command on LMT.

3.3.1 SOFTWARE UPGRADE PROCEDURE STEPS

The upgrade is composed of four main steps:

- Download the 9313 Micro/9314 Pico Node B software from DVD-ROM to the SRS.

- Using LMT, download load UA6.0 on 9313 Micro/9314 Pico Node B using LMT

launched from NSP in a planned view.

- Edit office data and modify it in the planned view to set parameter

Originatinga2ea to the correct value provided by engineering team.

- Activate the software on 9313 Micro/9314 Pico using LMT by selecting Apply

on planned session.

Note: Please note that the upgrade could only be done using the LMT on NSP

because it is the only way to set the ALCAP parameter Originatinga2ea.


16/44

6


3.3.1.1 DURATIONS

Taking into account the pre/post checks and all the steps needed to complete theupgrade (see section 3.4page 8), the global upgrade duration should be as follow.

Upgrade total duration for

100 9313 Micro/9314 Pico

Node Bs

255minutes

Table 1. Upgrade total duration

3.3.1.2

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.

Maintenance Window

duration

50minutes

+

40minutes for the fallback

=

90minutes

Table 2. Maintenance Window duration

3.3.1.3 OUTAGE

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

Micro/9314 Pico Node B restarts (this takes about 5minutes).

Outage duration

(whatever the number of9313Micro/9314 Pico Node B)

5minutes

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.


17/44

7


The fallback operation requires a downgrade to be performed on 9313 Micro/9314

Pico Node B.


18/44

8


3.4. TWO KINDS OF UPGRADE SEQUENCE

The NE upgrade (RNC or Node B) procedure follows 2 upgrade sequencingaccording to the period of the upgrade:

1 Multiple leaps upgrade process

For upgrade performed during the VO 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.

RNC Vnfeatures xyz

RNC Vn+1features xyzabc

Time

Upgrade RNC Vn --> Vn+1 And feature abc

WAUT WO + WPS WO merged

Build

Node B Vnfeatures xyz

Node B Vn+1features xyz

Node B Vn+1features xyzabc

Node B Vn+1features xyza

Node B Vn+1features xyzab

Time

UpgradeNode B VnVn+1

Add feature a Add feature b Add feature c

WAUT WO

Build

WPS WO

Depends

WPS WO

Depends

WPS WO

Depends


19/44

9


3.5. UPGRADE SEQUENCE TABLE

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

9313 Micro/9314 Pico Node B upgrade. None of them should be skipped unless

otherwise specified. All these steps must be performed one after the other. 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.

Upgrade Steps Duration(minutes)

Sheetpage

NOKstep

Check all prerequisites are ok one day before the upgrade - 3 -

Download the 9313 Micro/9314 Pico Node B software from

DVD-ROM/Local Files to SRS

20 12 -

Check 9313 Micro/9314 Pico Node Bs alarms 30 17 -

NONDISRUPTIVE

OPERAT

IONS.

SHOULDBEP

ERFORMED

OUTSIDETHE

MAINTENANCEWINDOW.

Download by using LMT the new UA6.0 software to 9313Micro/9314 Pico Node B from the executing view to a plannedview. Set the Originatinga2ea parameter.

10 to 130* 20 -

PRECHECKS,DOW

NLOADand

UPGRAD

E

Beginning of the Maintenance Window

OUTAGE

5minutes Activate the 9313 Micro/9314 Pico Node B software by applying

planned view.15 25 See

section 3.6

Check the Operational State for ALCAP Component is

Enableb in the LMT and check the Vp/Vc in RNC side.

5 - -

M

AINTENANCE

WINDOW

POST

CHECKS

Check 9313 Micro/9314 Pico Node Bs alarms 30 17 Seesection 3.6

Table 4. Upgrade sequence

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

3.6. FALLBACK SEQUENCE TABLE

FALLBACK STEPS Duration(minutes) Sheet page

Fallback the 9313 Micro/9314 Pico Node B 10 30

FALLBACK

50m

in

Check 9313 Micro/9314 Pico Node B alarms 30 17

Table 5. Fallback sequence


20/44

10


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.


21/44

11


HOW TO

PRESENTATIONThe purpose of this sheet is to describe how to perform some basic operations, which haveto 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 Sessions Manager console:

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

The console displays the currently active sessions.

P2. To launch the Equipment Monitor:

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

Figure 2. Launch the Equipment Monitor

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


22/44

12


DOWNLOAD SOFTWARE FROM DVD-ROM/LOCALFILES TO SRS

PRESENTATION

The purpose of this sheet is to describe how to download the new software version fromthe 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 SoftwareDelivery Files present on the WMS OAM Client.

ACTIONS

ON THE OAM CLIENT:

1.Open the SRM GUI:

- If not already done, log in on the WMS 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 for the WMS OAM Client administrator account.

The following page will be displayed:

Figure 3. 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 SRS server (see the screen above). SRS must haveat least 5 MB of free space.

Free space on

SRS server

InstallSoftware

Release
http://hostnamesrs:8080/srm/http://hostnamesrs:8080/srm/http://hostnamesrs:8080/srm/http://hostnamesrs:8080/srm/


23/44

13


If there is not enough free space, see the troubleshooting section to know how toremove unused software from SRS.

3.Click Install Software Release...- the following window appears:

Figure 4. 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-ROMfor the delivery data input then select theDVD-ROM drive (Note that on a Windows client all drive roots are listedalphabetically, 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 OKon 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 Filesfor the delivery data inputthen click Add

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

files will be added to the file list field.


24/44

14


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

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

The status of the data transfer is displayed as follows:

Figure 6. SRM install software data transfer page

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

Figure 7. SRM installation successful page

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


25/44

15


Figure 8. SRM installation details and result

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

WARNING:For PC Windows XP SP2, if the PC is equipped with a firewall like Cyberarmor orMcAfee, the software download operation may (will) 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 McAfeeplease contact PC administrator).

TROUBLESHOOTING

1- In case of problem when connecting to http://hostnameSRS:8080/srm/,make sure thatthe 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 the SRSusing SRM. To do this, the operator can:

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

Select the unneeded deliveries

And remove them from the SRS by clicking Delete Selected:

Figure 9. SRM delete software page

Warning: do not remove any software version being used on the network (activeor passive).
http://hostnamesrs:8080/srm/http://hostnamesrs:8080/srm/http://hostnamesrs:8080/srm/http://hostnamesrs:8080/srm/http://hostnamesrs:8080/srm/http://hostnamesrs:8080/srm/


26/44

16


FINAL STATUS

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


27/44

17


CHECK 9313 MICRO/9314 PICO NODE B ALARMS

PRESENTATIONThe purpose of this sheet is to describe how to check 9313 Micro/9314 Pico Node B activealarms. This sheet can be executed periodically during the upgrade in order to detectpending alarms, but is especially aimed at verifying any new alarms that could have beenraised 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 9313 Micro/9314 Pico Node Bs on which the alarms must be checked.- Right-click on the selection and select Show Alarmsfrom the context menu.

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

Figure 10. How to open Alarm window

There should be no alarms on the 9313 Micro/9314 Pico Node Bs before and afterthe upgrade. If there are some residual alarms, each one must be investigatedbefore making the decision to proceed with the upgrade.

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


28/44

18


Figure 11. OSI State Reporting window

A faulty FDDCell occurs on a 9313 Micro/9314 Pico Node B that is not workingproperly. After the upgrade, compare the faulty FDDCells list to the one before theupgrade. All extra faulty FDDCells might be caused by a problem during the 9313Micro/9314 Pico Node B upgrade and will need to be investigated.

3. Check active calls in progress on 9313 Micro/9314 Pico Node B or FDDCell to verifyoverall call processing executed by 9313 Micro/9314 Pico Node B(For all 9313Micro/9314 Pico Node B upgraded in parallel you check calls at RNC side and for one9313 Micro/9314 Pico Node B upgrade then on its linked FDDCells located at the RNCside as well. This checking via dynamic data is only applicable if the lower software

release of the RNC is UA6.0.):

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

Figure 12. Check calls at RNC side

RNC tab

Dynamic Data tab


29/44

19


Figure 13. Check calls on linked FDDCells

FINAL STATUS

9313 Micro/9314 Pico Node B alarms and faulty FDDCells have been analysed and noted.

Some 9313 Micro/9314 Pico Node B upgrades have been postponed if needed.

RNC tab

Dynamic Data tab


30/44

20


DOWNLOAD SOFTWARE TO 9313 MICRO/9314 PICONODE B

PRESENTATION

The purpose of this sheet is to describe the download process to apply when upgrading9313 Micro/9314 Pico Node Bs to UA6.0 load. This particular download will be processedwith help of LMT tool available from the WMS GUI. The restriction is that software upgradecan be done only Node B per Node B and not several at the same time.

INITIAL STATUS

The new 9313 Micro/9314 Pico Node B software to be downloaded is available on SRS.The WMS GUI Client is available.

ACTIONS

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

2. Select the 9313 Micro/9314 Pico Node B to be downloaded.

3. To launch the LMT, an exceed session has first to be launched. Then launch LMT byselecting LMT by right-clicking on the selected 9313 Micro/9314 Pico Node B.

Figure 14. Launch the LMT


31/44

21


4. After LMT is launched, then select Configuration thumbnail and Select Software.Then choose application (the UA6.0 software version to be downloaded) and selectExecuting in Choose office data to base your new configuration on

Figure 15. Select software and Executing

5. As the ALCAP is not completely configured, and particularly the Originatinga2eaparameter, one warning message will appear. Then select Edit Office Data.

Figure 16. Office Data Migration Result window


32/44

22


6. Then, Office Data will be automatically opened and select ALCAP thumbnail with thefield Originatinga2ea to be filled.

Figure 17. Edit Planned Office Data window

7. Then fill the Originatinga2ea field with the value provided by engineering team.Take care that the format to be used for parameter originatingA2ea is not the samethat the one provided by engineering team.

So, if value given is originatingA2ea =

470000FFFFFFFFFFFFF0001033AAAAAAAAAA0300, the value to be filled will beoriginatingA2ea =0x47,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xF0,0x00,0x10,0x33,0xAA,0xAA,0xAA,0xAA,0xAA,0x03,0x00.

Note:You can copy/paste the value by a middle-clicking.Vp and Vc may appear without value or with default values. Fill in Vp, Vc values withthe one given by engineering team or customer information.Consistency of PeakCellRate and Service Category values will have also to be checked


33/44

23


Figure 18. Fill the Originatinga2ea field

8. After having set the originatinga2ea parameter, planned office data can be seen asvalid in the LMT. The download has been done and the new software is ready to beactivated.


34/44

24


Figure 19. Planned office data display as valid in the LMT

FINAL STATUS

The download operation has been performed on the selected 9313 Micro/9314 Pico Node B.


35/44

25


ACTIVATE THE SOFTWARE

PRESENTATIONThe sheet describes how to activate the previously downloaded software.

INITIAL STATUS

The new 9313 Micro/9314 Pico Node B software to be activated is downloaded successfullycompleted on the 9313 Micro/9314 Pico Node B.The WMS GUI Client is available.

ACTIONS

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

2. Select the 9313 Micro/9314 Pico Node B to be activated.3. To launch the LMT, an exceed session has first to be launched. Then launch LMT

by selecting LMT by right-clicking on the selected 9313 Micro/9314 Pico Node B.

Figure 20. Launch the LMT

4. After having launched the LMT, in the configuration thumbnail, select thePlanned view and then Apply. Then following message will appear. ClickOK.


36/44

26


Figure 21. Install new software confirmation

5. Then, the window Apply in progress will appear and the 9313 Micro/9314 PicoNode B will be restarted.

Figure 22. Apply and Commit status


37/44

27


6. After restart, 9313 Micro/9314 Pico Node B needs a commit of the new changes inthe executing view. Then, the following dialog box will open. Click on ManualCommit to commit the changes.

Figure 23. Commit of the new changes after restart

7. After the changes commit, the Executing view should have the new UA6.0software version and the ALCAP on the left box shall be green.


38/44

28


Figure 24. Executing view after changes commit

8. Open LMT, check the ALCAP status. Operational Status should be "Enabled" and noalarms on ALCAP.

Figure 25. Check the ALCAP status in LMT

9. Last step is to check the Vc/Vp ALCAP is well configured by testing the ALCAPPVC toward the RNC.


39/44

29


- Telnet the RNC INode- Type the following command to find VCC regarding the 9313 Micro/9314 PicoNode B.

> d -p atmif/* vcc/* vcd tag

Then type the following command :

> d atmif/X vcc/*.Z rxcell, txcell

where:- X: is the atmif ID(s) of the Iub holding your ALCAP VCCs- Z: the VCI reserved for ALCAP VCCs. The method is worth being used only

in case it has been decided of a fix VCI (or PVI) for all ALCAP VCCs. In case

it is the PVI that is fixed, the command will be the following:

Output example:

4> d atmif/807 vcc/*.100 rxcell,txcell

AtmIf/807 Vcc/*.100+==========+--------------------+--------------------| Vcc | rxCell | txCell+==========+--------------------+--------------------|0.100 | 145162| 145162

|10.100 | 79626| 79626|11.100 | 145173| 145173

Run the command several times in a row, and if the rxcell, txcell figures are increasing,then packets are going trough and it can be assumed that the connection is successful.

TROUBLESHOOTING

In case an error message is encountered, see Appendix A: Upgrade messages(page 33)forthe required remedial action. Most of the time, for minor issues a retry from the beginning

of this sheet for the failed 9313 Micro/9314 Pico Node Bs will be enough to complete the9313 Micro/9314 Pico Node B upgrade.

FINAL STATUS

The activation operations have been performed.

Note:Once the upgrade is finished, please dont forget to do theCheck 9313 Micro/9314Pico Node Bs alarmson page 17.


40/44

30


FALLBACK 9313 MICRO/9314 PICO NODE B SOFTWARE

PRESENTATION

This sheet describes how to fallback the 9313 Micro/9314 Pico Node Bs software. Therestore is performed on a 9313 Micro/9314 Pico Node B by 9313 Micro/9314 Pico Node Bbasis. This sheet is therefore to be executed once for each 9313 Micro/9314 Pico Node B tobe restored.

INITIAL STATUS

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

ACTIONS

Fallback can be done by using LMT and selecting Rollback view and then Apply in theConfiguration thumbnail.

Figure 26. Rollback viewin LMT

Then the same process will apply as the one for the software activation:


41/44

31


Figure 27. Apply and Commit status

Figure 28. Commit of the new changes after restart

FINAL STATUS

The 9313 Micro/9314 Pico Node B software has returned to the version before the upgrade.


42/44

32


Figure 29. Fallback result


43/44

33


APPENDIX A: UPGRADE MESSAGES

Message displayed inOAM

Meaning Additional OAM action Additional information

Software alreadyrunning

The requested software isalready running. No need todownload. No need to activate.

No Activation is not necessary; the softwareis already active

Software already onpassive FFS.

The requested software isalready downloaded on the 9313Micro/9314 Pico NODE B. It isonly necessary to activate thisversion.

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

Download already inprogress on this BTS

A download is requested by theOAM while a download isalready on-going on the 9313Micro/9314 Pico Node B. OAMdownload is refused.

Retry the upgrade. This may occur when a board is pluggedinto the rack and must be upgraded. Ifthe OAM operator decides to downloadduring the automatic internal upgrade,such an error is returned to the OAM.

Download already inprogress on this BTS(same id session)

A download is requested by theOAM while a download isalready on-going on the 9313Micro/9314 Pico Node B. OAMdownload is refused.

Retry the upgrade. This may occur when a board is pluggedinto the rack and must be upgraded. Ifthe OAM operator decides a downloadduring the automatic internal upgrade,such an error is returned to the OAM.

BTS internal failure This is a 9313 Micro/9314 PicoNode B internal error.

Retry the upgrade. If the problempersists, call your next level ofsupport.

Inconsistency betweenBTS ID stored in OAMdatabase and BTS ID.

The 9313 Micro/9314 Pico NodeB serial number sent by OAMdoes not match the true 9313Micro/9314 Pico Node B serialnumber.

Check serial number. Retry adownload with correctconfiguration. If the problempersists, call your next level ofsupport.

Note: The 9313 Micro/9314 Pico Node Bserial number has already beenexchanged and checked during firstmessages exchanged between OMC and9313 Micro/9314 Pico Node B.

The RAM disk of theBTS is full even after 40

retries.

There is no room in 9313Micro/9314 Pico Node B CCM

Ram disk to store the file(already 40 retries done).

Reset the 9313 Micro/9314 PicoNode B and retry the upgrade. If

the problem persists, call yournext level of support.

Download process is automaticallyaborted.

Note that this error may come from thefact that a file is too big for the 9313Micro/9314 Pico Node B running version,or the 9313 Micro/9314 Pico Node B ramdisk already contains too many files. A9313 Micro/9314 Pico Node B resetwould clean this disk.

The size of a file to betransferred has not theexpected size

Incoherence in the softwaredelivery.

Reset the 9313 Micro/9314 PicoNode B and retry the upgrade. Ifthe problem persists, call yournext level of support.

Incoherence between file size in File0and size of the downloaded file.

File 0 parsing problem The 9313 Micro/9314 Pico NodeB cannot read the softwaredelivery.


The 9313 Micro/9314 Pico Node B cannotparse the File0. Either the file isincorrect, or the downloaded software isincompatible with the running version.Download aborted.

FTP Error A FTP error detected during thedownload.


Download ProtocolError

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


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

FFS Error Flash File System error on the9313 Micro/9314 Pico Node B.

No Contact next level support.

ERROR: "Activationfailed"

Activation failed (for exampledue to FFS problem)


ERROR: "Activation

failed: BTS not ready"

Activation failed Reset the 9313 Micro/9314 Pico

Node B and retry the upgrade. Ifthe problem persists, call yournext level of support.

Table 6. Upgrade messages


44/44

34

Wireless Service Provider Solutions

W-CDMAUpgrade Procedure

Alcatel-Lucent 9300 W-CDMA Product FamilyAlcatel-Lucent 9313 Micro Node B and 9314 Pico Node B - Software UpgradeProcedure Using OAM7.1.3

Alcatel-Lucent Internal Proprietary Use pursuant to Company instruction

2003-2011 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 havereceived 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-151Document issue: 05.03/ENDocument status: Approved-StandardProduct release: OAM07.1.3Date: April 2011

0w-cdma product family alcatel-lucent 9313 micro node b and 9314 pico node b - software upgrade...

Documents