0W-CDMA Product Family Alcatel-Lucent 9313 Micro Node B and 9314 Pico Node B - Software Upgrade Procedure Using OAM7.1.3

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 Pico
Node B - Software Upgrade Procedure Using
OAM7.1.3
NN-20500-151 05.03/EN Approved-Standard April 2011

W-CDMA
Upgrade Procedure
Alcatel-Lucent 9313 Micro Node B and 9314 Pico
Node B - Software Upgrade Procedure Using
OAM7.1.3

Document number: NN-20500-151
Document issue: 05.03/EN
Document status: Approved-Standard
Product release: OAM07.1.3
Date: April 2011
Alcatel-Lucent Internal Proprietary Use pursuant to Company instruction

Copyright 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 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-2011 Alcatel-Lucent Alcatel-Lucent 9300 W-CDMA Product Family - Alcatel-Lucent 9313 Micro Node B and
9314 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, 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. 9313 MICRO/9314 PICO NODE B UPGRADE ..............................................................3
3.1. IMPORTANT INFORMATION .........................................................................................................3
3.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 9313 MICRO/9314 PICO NODE B ALARMS............................................................................17
DOWNLOAD SOFTWARE TO 9313 MICRO/9314 PICO NODE B............................................................20
ACTIVATE THE SOFTWARE ....................................................................................................................25
FALLBACK 9313 MICRO/9314 PICO NODE B SOFTWARE ..................................................................30
APPENDIX A: UPGRADE MESSAGES............................................................................... 33
Table of content v
LIST OF FIGURES
Figure 1. Alarm CONFIGURATION NOT SYNCHRONIZED...................................................................3
Figure 2. Launch the Equipment Monitor ...............................................................................................11
Figure 3. SRM GUI .................................................................................................................................12
Figure 4. SRM install software page ......................................................................................................13
Figure 5. SRM install software page for Local Software Delivery Files .................................................14
Figure 6. SRM install software data transfer page .................................................................................14
Figure 7. SRM installation successful page ...........................................................................................14
Figure 8. SRM installation details and result ..........................................................................................15
Figure 9. SRM delete software page......................................................................................................15
Figure 10. How to open Alarm window...................................................................................................17
Figure 11. OSI State Reporting window.................................................................................................18
Figure 12. Check calls at RNC side .......................................................................................................18
Figure 13. Check calls on linked FDDCells............................................................................................19
Figure 14. Launch the LMT ....................................................................................................................20
Figure 15. Select software and Executing..............................................................................................21
Figure 16. Office Data Migration Result window....................................................................................21
Figure 17. Edit Planned Office Data window..........................................................................................22
Figure 18. Fill the Originatinga2ea field..................................................................................................23
Figure 19. Planned office data display as valid in the LMT....................................................................24
Figure 20. Launch the LMT ....................................................................................................................25
Figure 21. Install new software confirmation..........................................................................................26
Figure 22. Apply and Commit status ......................................................................................................26
Figure 23. Commit of the new changes after restart ..............................................................................27
Figure 24. Executing view after changes commit ................................................................................28
Figure 25. Check the ALCAP status in LMT...........................................................................................28
Figure 26. Rollback view in LMT..........................................................................................................30
Figure 27. Apply and Commit status ......................................................................................................31
Figure 28. Commit of the new changes after restart ..............................................................................31
Figure 29. Fallback result .......................................................................................................................32
Table of content vii
LIST OF TABLES
Table 1. Upgrade total duration................................................................................................................6
Table 2. Maintenance Window duration...................................................................................................6
Table 3. Outage duration..........................................................................................................................6
Table 4. Upgrade sequence .....................................................................................................................9
Table 5. Fallback sequence......................................................................................................................9
Table 6. Upgrade messages ..................................................................................................................33
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: Command
Line 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
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
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 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 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 the
executing 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 5 55 5:
Before executing this procedure, ask the support team for any special actions (bulletin,
4

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

WARNING 6 66 6:
All the prerequisites described in this chapter must be fulfilled at least one day before
the upgrade starts.

WARNING 7 77 7:
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 New software release you are going to upgrade your
Micro Node B to. In order to do so:
1) Determine the firmware/software/hardware present on the Node B using the
document "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 Release
Notes, 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.

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.
6

3.3.1.1 DURATIONS
Taking into account the pre/post checks and all the steps needed to complete the
upgrade (see section 3.4 page 8), the global upgrade duration should be as follow.
Upgrade total duration for
100 9313 Micro/9314 Pico
Node Bs
255 minutes
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
50 minutes
+
40 minutes for the fallback
=
90 minutes
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 5 minutes).
Outage duration
(whatever the number of9313
Micro/9314 Pico 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.
7

The fallback operation requires a downgrade to be performed on 9313 Micro/9314
Pico Node B.
8

3.4. TWO KINDS OF UPGRADE SEQUENCE
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 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 Vn
features xyz
RNC Vn+1
features xyzabc
Time
Upgrade RNC 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 Vn Vn+1

Add feature a Add feature b Add feature c
WAUT WO
Build
WPS WO
Depends
WPS WO
Depends
WPS WO
Depends
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)
Sheet
page
NOK
step
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 -
N
O
N

D
I
S
R
U
P
T
I
V
E

O
P
E
R
A
T
I
O
N
S
.

S
H
O
U
L
D

B
E

P
E
R
F
O
R
M
E
D

O
U
T
S
I
D
E

T
H
E

M
A
I
N
T
E
N
A
N
C
E

W
I
N
D
O
W
.

Download by using LMT the new UA6.0 software to 9313
Micro/9314 Pico Node B from the executing view to a planned
view. Set the Originatinga2ea parameter.
10 to 130* 20 -
P
R
E
C
H
E
C
K
S

,

D
O
W
N
L
O
A
D

a
n
d

U
P
G
R
A
D
E

Beginning of the Maintenance Window
O
U
T
A
G
E

5

m
i
n
u
t
e
s

Activate the 9313 Micro/9314 Pico Node B software by applying
planned view.

15 25 See
sectio
n 3.6
Check the Operational State for ALCAP Component is
Enableb in the LMT and check the Vp/Vc in RNC side.
5 - -

M
A
I
N
T
E
N
A
N
C
E

W
I
N
D
O
W

P
O
S
T

C
H
E
C
K
S

Check 9313 Micro/9314 Pico Node Bs alarms

30 17 See
sectio
n 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

F
A
L
L
B
A
C
K

5
0

m
i
n

Check 9313 Micro/9314 Pico Node B alarms 30 17
Table 5. Fallback sequence
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.

11

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 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.

P2. To launch the Equipment Monitor:

- Log into WMS OAM GUI and open the corresponding layout embedding the RNC to
be 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.

12
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.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 have
at least 5 MB of free space.
Free space on
SRS server
Install
Software
Release
13

If there is not enough free space, see the troubleshooting section to know how to
remove 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-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.

14

Figure 5. 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 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:

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 or
McAfee, 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 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 the SRS
using 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 (active
or passive).
16
FINAL STATUS
The software has been downloaded from DVD-ROM/Local Files to SRS disk.
17

CHECK 9313 MICRO/9314 PICO NODE B ALARMS

PRESENTATION
The purpose of this sheet is to describe how to check 9313 Micro/9314 Pico 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 9313 Micro/9314 Pico 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 10. How to open Alarm window

There should be no alarms on the 9313 Micro/9314 Pico 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.

18

Figure 11. OSI State Reporting window

A faulty FDDCell occurs on a 9313 Micro/9314 Pico 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 9313
Micro/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 verify
overall call processing executed by 9313 Micro/9314 Pico Node B(For all 9313
Micro/9314 Pico Node B upgraded in parallel you check calls at RNC side and for one
9313 Micro/9314 Pico Node B upgrade then on its linked FDDCells located at the RNC
side 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
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
20
DOWNLOAD SOFTWARE TO 9313 MICRO/9314 PICO
NODE B

PRESENTATION
The purpose of this sheet is to describe the download process to apply when upgrading
9313 Micro/9314 Pico Node Bs to UA6.0 load. This particular download will be processed
with help of LMT tool available from the WMS GUI. The restriction is that software upgrade
can 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 by
selecting LMT by right-clicking on the selected 9313 Micro/9314 Pico Node B.

Figure 14. Launch the LMT

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 select
Executing 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 Originatinga2ea
parameter, one warning message will appear. Then select Edit Office Data.

Figure 16. Office Data Migration Result window

22
6. Then, Office Data will be automatically opened and select ALCAP thumbnail with the
field 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 same
that the one provided by engineering team.

So, if value given is originatingA2ea =
470000FFFFFFFFFFFFF0001033AAAAAAAAAA0300, the value to be filled will be
originatingA2ea =
0x47,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xF0,0x00,0x10,0x33,0xAA,0xAA,0xA
A,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 with
the one given by engineering team or customer information.
Consistency of PeakCellRate and Service Category values will have also to be checked

23


Figure 18. Fill the Originatinga2ea field

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

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.
25

ACTIVATE THE SOFTWARE

PRESENTATION
The 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 successfully
completed 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 the
Planned view and then Apply. Then following message will appear. Click
OK.
26

Figure 21. Install new software confirmation

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

Figure 22. Apply and Commit status

27


6. After restart, 9313 Micro/9314 Pico Node B needs a commit of the new changes in
the executing view. Then, the following dialog box will open. Click on Manual
Commit 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.0
software version and the ALCAP on the left box shall be green.

28

Figure 24. Executing view after changes commit

8. Open LMT, check the ALCAP status. Operational Status should be "Enabled" and no
alarms 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 ALCAP
PVC toward the RNC.
29

- Telnet the RNC INode
- Type the following command to find VCC regarding the 9313 Micro/9314 Pico
Node 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) for
the 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 the
9313 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 the Check 9313 Micro/9314
Pico Node Bs alarms on page 17.
30
FALLBACK 9313 MICRO/9314 PICO NODE B SOFTWARE

PRESENTATION
This sheet describes how to fallback the 9313 Micro/9314 Pico Node Bs software. The
restore is performed on a 9313 Micro/9314 Pico Node B by 9313 Micro/9314 Pico Node B
basis. This sheet is therefore to be executed once for each 9313 Micro/9314 Pico Node B to
be 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 the
Configuration thumbnail.

Figure 26. Rollback view in LMT

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

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.

32

Figure 29. Fallback result

33

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 9313
Micro/9314 Pico 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 9313
Micro/9314 Pico 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 9313
Micro/9314 Pico 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 9313 Micro/9314 Pico
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 9313 Micro/9314 Pico Node
B serial number sent by OAM
does not match the true 9313
Micro/9314 Pico 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 9313 Micro/9314 Pico Node B
serial number has already been
exchanged and checked during first
messages exchanged between OMC and
9313 Micro/9314 Pico Node B.
The RAM disk of the
BTS is full even after 40
retries.
There is no room in 9313
Micro/9314 Pico Node B CCM
Ram disk to store the file
(already 40 retries done).
Reset the 9313 Micro/9314 Pico
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 9313
Micro/9314 Pico Node B running version,
or the 9313 Micro/9314 Pico Node B ram
disk already contains too many files. A
9313 Micro/9314 Pico 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 9313 Micro/9314 Pico Node
B cannot read the software
delivery.
The 9313 Micro/9314 Pico 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
9313 Micro/9314 Pico 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 9313 Micro/9314 Pico

Table 6. Upgrade messages
34
W-CDMA
Upgrade Procedure
Alcatel-Lucent 9313 Micro Node B and 9314 Pico Node B - Software Upgrade
Procedure 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 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-151
Document issue: 05.03/EN
Document status: Approved-Standard
Product release: OAM07.1.3
Date: April 2011

0W-CDMA Product Family Alcatel-Lucent 9313 Micro Node B and 9314 Pico Node B - Software Upgrade Procedure Using OAM7.1.3

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

0W-CDMA Product Family Alcatel-Lucent 9313 Micro Node B and 9314 Pico Node B - Software Upgrade Procedure Using OAM7.1.3

Transféré par

Droits d'auteur :

Formats disponibles

NN-20500-151

Wireless Service Provider Solutions

Vous aimerez peut-être aussi