20500148UA08.1 - V1 - Alcatel-Lucent 9370 Radio Network Controller - Software Upgrade Procedure Using OAM 8.1 - Inter Release Upgrade

NN-20500-148
Wireless Service Provider Solutions

W-CDMA
Upgrade Procedure
Alcatel-Lucent 9300 W-CDMA Product Family
Alcatel-Lucent 9370 Radio Network Controller
Software Upgrade Procedure Using OAM 8.1: Inter
Release Upgrade
NN-20500-148 07.07/EN Standard December 2012

W-CDMA
Upgrade Procedure
Alcatel-Lucent 9370 Radio Network Controller
Software Upgrade Procedure Using OAM 8.1: Inter
Release Upgrade

Document number: NN-20500-148
Document issue: 07.07/EN
Document status: Standard
Product release: OAM08.1
Date: December 2012
Alcatel-Lucent Internal Proprietary Use pursuant to Company instruction

Copyright 2003-2012 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-2012 Alcatel-Lucent Alcatel-Lucent 9300 W-CDMA Product Family - Alcatel-Lucent 9370 Radio Network
Controller Software Upgrade Procedure Using OAM 8.1: Inter Release Upgrade
PUBLICATION HISTORY
SYSTEM RELEASE: OAM08.1
December 2012
Issue 07.07/EN, Standard
Updated according to review comments of BRIAC ION.

October 2012

October 2012

April 2012
Issue 07.04/EN, Preliminary

August 2011
Issue 07.03/EN, Preliminary

August 2011
Issue 07.02/EN, Draft

June 2011
Issue 07.01/EN, Draft
Document creation

Table of content iii
TABLE OF CONTENTS
1. INTRODUCTION ............................................................................................. 1
1.1. OBJECT & 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. RNC UPGRADE .............................................................................................. 2
3.1. IMPORTANT INFORMATION ......................................................................................................... 2
3.1.1 WARNINGS ........................................................................................................................ 2
3.2. UPGRADE PREREQUISITES ........................................................................................................ 3
3.2.1 WARNINGS ....................................................................................................................... 3
3.2.2 HUMAN RESOURCES ......................................................................................................... 3
3.2.3 SUPPORTED HARDWARE CONFIGURATION .......................................................................... 4
3.2.4 WMS CLIENT .................................................................................................................... 4
3.2.5 SOFTWARE LINE UP ........................................................................................................... 4
3.2.6 SOFTWARE TOOLS ............................................................................................................ 4
3.2.7 LOGINS AND PASSWORDS .................................................................................................. 4
3.3. UPGRADE WITH NEW MIB OVERVIEW ......................................................................................... 4
3.4. UPGRADE DURATION ................................................................................................................. 5
3.5. MAINTENANCE WINDOW ............................................................................................................ 6
3.6. OUTAGE DURATION ................................................................................................................... 6
3.7. TWO KINDS OF UPGRADE SEQUENCE .......................................................................................... 7
3.7.1 UPGRADE SEQUENCES ...................................................................................................... 7
3.7.2 HOW TO PERFORM SINGLE LEAP UPGRADE PROCESS ....................................................... 7
3.8. UPGRADE SEQUENCE TABLE ...................................................................................................... 9
3.9. FALLBACK SEQUENCE TABLE ...................................................................................................10
4. SHEETS ..................................................................................................... 11
HOW TO .......................................................................................................................................12
DOWNLOAD RNC SOFTWARE FROM DVD-ROM/LOCAL FILES TO SRS ............................................................18
RNC CHECK.......................................................................................................................................23
REMOVE UNUSED SOFTWARE FROM RNC .................................................................................................32
BACKUP RNC IN OAM DATABASE .........................................................................................................35
BACKUP RNC IMAGE ..........................................................................................................................36
EXPORT RNC TO CM XML FILE ............................................................................................................38
UPGRADE CM XML FILE ......................................................................................................................40
DOWNLOAD SOFTWARE TO RNC ...........................................................................................................46
ACTIVATE THE NEW SOFTWARE ON RNC .................................................................................................53
iv
NN-20500-148 07.07/EN Standard December 2012 2003-2012 Alcatel-Lucent
BACKUP THE MIB PROTO PATCH FILE .................................................................................................58
PATCH THE MIB PROTO .................................................................................................................60
RESTORE THE MIB PROTO PATCH ..................................................................................................63
UPGRADE THE RNC FABRIC FIRMWARE IF NEEDED .....................................................................................64
SOFTWARE FALLBACK ON RNC .............................................................................................................66
RESTORE RNC IN OAM DATABASE ........................................................................................................69
HOW TO USE THE WAUT UPGRADE REPORT............................................................................................70
Table of content v
LIST OF FIGURES
Figure 1. Upgrade prerequisites ............................................................................................................... 3
Figure 2. Upgrade with new mib overview(UA7.1 to UA8.1 as an example) ........................................... 5
Figure 3. Do Single Leap upgrade ......................................................................................................... 8
Figure 4. Show alarms associated with RNC .........................................................................................12
Figure 5. Launch the Set NEs OAM Link Administrative State window ................................................13
Figure 6. Set NEs OAM Link Administrative State Action Window .......................................................13
Figure 7. Launch the Equipment Monitor ...............................................................................................14
Figure 8. How to get the neId parameter value of the I-Node ................................................................15
Figure 9. How to get the value of the mibState ......................................................................................15
Figure 10. Check active calls in progress on RNC .................................................................................17
Figure 11. Check active calls in progress on FDDCell ...........................................................................17
Figure 12. SRM GUI ...............................................................................................................................18
Figure 13. SRM install software page ....................................................................................................19
Figure 14. SRM install software page for Local Software Delivery Files ...............................................20
Figure 15. SRM install software data transfer page ...............................................................................20
Figure 16. SRM installation successful page .........................................................................................20
Figure 17. SRM installation details and result ........................................................................................21
Figure 18. SRM delete software page ....................................................................................................21
Figure 19. Set Maintenance Mode On ...................................................................................................23
Figure 20. How to open Audit window ....................................................................................................25
Figure 21. Audit Action Window .............................................................................................................25
Figure 22. Command Manager...............................................................................................................26
Figure 23. Sun Management Center home page ...................................................................................26
Figure 24. Sun Management Center login window ................................................................................27
Figure 25. Set Home Domain window ....................................................................................................27
Figure 26. Sun Management Center main window ................................................................................28
Figure 27. Sun Management Center host details window ......................................................................29
Figure 28. Sun Management Center OAM IP group window .................................................................30
Figure 29. OSI State Reporting window .................................................................................................31
Figure 30. RNC Backup Action window ................................................................................................36
Figure 31. Confirm Dialog for RNC Backup ..........................................................................................36
Figure 32. command manager window ...............................................................................................37
Figure 33. How to open Export NE Grouping .........................................................................................38
Figure 34. CM XML Export window ........................................................................................................39
Figure 35. Launch Wireless Access Upgrade Tool ................................................................................40
Figure 36. Select Import and export .......................................................................................................41
Figure 37. Import and Export Wizard window ........................................................................................41
Figure 38. Import snapshot(Local file system) .......................................................................................42
Figure 39. Select the initial RNC CM XML file........................................................................................42
Figure 40. Save workspace option window ............................................................................................43
Figure 41. Import progress window ........................................................................................................43
Figure 42. Select the NE Provisioning Upgrade Operation ....................................................................44
Figure 43. NE Provisioning Upgrade Operation window ........................................................................44
Figure 44. Upgrade report window .........................................................................................................45
Figure 45. CM XML file ...........................................................................................................................45
Figure 46. Download wizard: Introduction ..............................................................................................46
Figure 47. Download wizard: Select the Network Element type (from menu bar) .................................47
Figure 48. Download wizard: Select the Network Element type(from right-click menu) ........................47
Figure 49. Download wizard: Select Software Version to Download .....................................................47
Figure 50. Download wizard: Retrieved Node(s) ...................................................................................48
Figure 51. Download wizard: Retrieved Node(s) ...................................................................................48
Figure 52. Download wizard: Upgrade Type Selection ..........................................................................49
Figure 53. Download wizard: Search Criteria Summary ........................................................................49
Figure 54. Download wizard: Complete .................................................................................................49
Figure 55. Download:Command Manager .............................................................................................50
Figure 56. How to open Inventory & Upgrade Session ..........................................................................51
Figure 57. Select the current running software ......................................................................................51
vi
Figure 58. Select NE with status DOWNLOAD_COMPLETED .............................................................52
Figure 59. The inventory after execute Abort upgrade session .............................................................52
Figure 60. Activation wizard: Introduction ..............................................................................................54
Figure 61. Activation wizard: Select the Network Element type .............................................................54
Figure 62. Activation wizard: Select the Network Element type .............................................................54
Figure 63. Activation wizard: Retieved Node(s) .....................................................................................55
Figure 64. Activation wizard: Search Criteria Summary .........................................................................55
Figure 65. Activation wizard: Complete ..................................................................................................56
Figure 66. Activation: Command Manager .............................................................................................56
Figure 67. Blue icon ................................................................................................................................57
Figure 68. Brown icon .............................................................................................................................57
Figure 69. WAUT upgrade report1 .........................................................................................................70
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...................................................................................................................10
1

2003-2012 Alcatel-Lucent Alcatel-Lucent 9300 W-CDMA Product Family - Alcatel-Lucent 9370 Radio Network Controller
Software Upgrade Procedure Using OAM 8.1: Inter Release Upgrade
1. INTRODUCTION
1.1. OBJECT & SCOPE OF THIS DOCUMENT
The aim of this document is to describe how to perform a software remote
upgrade of an Alcatel-Lucent 9370 Radio Network Controller.
The described upgrade path is:
UA7.1 to UA8.1
The OAM8.1 is to be used to perform this upgrade.
Note mentioning that UA7.1 in this document refers strictly to UA7.1.3
1.2. AUDIENCE FOR THIS DOCUMENT
Alcatel-Lucent customers.
Anyone who performs RNC software upgrade.
2. RELATED DOCUMENTS
2.1. APPLICABLE DOCUMENTS
[A1] NN-10300-036 Alcatel-Lucent 9353 Management System -
Workstation Client/Application Installation
[A2] UMT/SYS/INF/034683 UA8.1 UTRAN Release Notes
[A3] UMT/SYS/INF/033614 UA7.1.3 UTRAN Release Note
[A4] UMT/OAM/DJD/033992 Release Notes for UMTS OAM08.1
2.2. REFERENCE DOCUMENTS
[R1] NN-20500-233 Alcatel-Lucent 9300 W-CDMA Product
Family - Access Network Elements Overview
[R2] NN-20500-021 Alcatel-Lucent 9370 Radio Network
Controller Technical Description
[R3] 4118111-534 Performance Management for Access
Network
[R4] 411-8111-232 UMTS Upgrade and Patches RNC1500
Patching Procedures
[R5] 241-5701-272 Passport 7400, 15000, 20000 Software
Upgrade
[R6] NN-20500-023 Alcatel-Lucent 9370 Radio Network
Controller Maintenance Guide

2
3. RNC UPGRADE
3.1. IMPORTANT INFORMATION
3.1.1 WARNINGS

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

WARNING 2:
If RNC MIB is rebuilt at least once after the software activation is completed (for
activation of features to be tested), the "old MIB" stored in the RNC could not match any
MIBs after the software fallback initiated by the reloadcp. So a MIB rebuild has to be
done at the end of the fallback procedure (see Section "Software Fallback on the RNC").

3

3.2. UPGRADE PREREQUISITES
Figure 1 summarizes all the requirements that must be fulfilled before starting the
upgrade:

Figure 1. Upgrade prerequisites
The information needed for the upgrade is retrieved from different locations.
Note that documents [A2] and [A3] are the most important since they are used to
define the upgrade strategy (Upgrade type to perform, build requirement ). The
following sections give more details about the requirements.

3.2.1 WARNINGS

WARNING 3:
See documents [A2] and [A3] to determine if this procedure is applicable to the upgrade
being performed.

WARNING 4:
All the Call Trace Sessions related to the RNCs to be upgraded need to be deleted prior
to starting the upgrade. See [R3] to know how to delete the sessions.

WARNING 5:
Before executing this procedure, ask the support team for any special action (bulletin,
workaround, patch ...) to perform before, during and after the procedure. Please refer
to documents [A2] and [A3].

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

3.2.2 HUMAN RESOURCES
An OAM site operator with RNC expertise is required.
[A2] documents
Special actions to perform before, during
and after the procedure available
Latest version of the upgrade
procedure is used

RNC in a supported hardware configuration
checked
All the DVDs are available
Start the upgrade
- Pre-
chec
ks
Upgrad
e
Post-
chec
ks
Upgrade
Operation
Supported Software line up checked
All
prerequisite
s complete
On-site coordinator
[R2] document
Users and passwords available
www.alcatel-lucent.com

4
3.2.3 SUPPORTED HARDWARE CONFIGURATION
The supported hardware configurations are described in the document referenced
in [R2].
It is mandatory for the RNC to be upgraded to be in a supported hardware
configuration before proceeding with the upgrade. If this is not the case, contact
your next level of support.
3.2.4 WMS CLIENT
A client OAM PC or workstation is needed.
3.2.5 SOFTWARE LINE UP
All the software (RNC and OAM loads) used during this procedure must be
compliant with the software line-up defined in document [A2] and [A3].
3.2.6 SOFTWARE TOOLS
- The installation disk (1 DVD-ROM) of the new UA8.1 9370 RNC software version.
- Wireless Access Upgrade Tool (WAUT): This software tool must be installed on
the PC client. It is used to perform the provisioning upgrade of CM XML files. It is
available on the ACCESS OAM DVD-ROM.
- 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.
3.2.7 LOGINS AND PASSWORDS
- Required OAM login information:
The OAM site operator performing the upgrade must have:
The password for the Alcatel-Lucent UNIX user (Main and NPO servers).
The password for the WMS OAM Client administrator account with full
access to the OAM.
- Required RNC login information:
The operator performing the upgrade must have, for each RNC:
The IP address of the RNC.
The password for the Passport system administrator of the RNC.

3.3. UPGRADE WITH NEW MIB OVERVIEW
The following diagram gives the high-level view of the upgrade procedure:

5


Figure 2. Upgrade with new mib overview(UA7.1 to UA8.1 as an example)

Step 3 line between UA8.1 Non-Passport CM XMLfile and OAM database is C-
NODE CM XML file import. Between OAM UTRAN Upgrade application and 9370
RNC is Software download. To save time, Software Download can be performed
in parallel with C-NODE CM XMLfile import (provisioning upgrade).
In figure 2, step 1 and 3 has no impact on the RNC service.
Step 4 (on-line build) is invoked automatically as a precursor to step 5 when an
activation is launched.
Step 6 handles the provisioning upgrade of the RNC INode. This step is skipped for
UA7.1 to UA8.1 upgrade, since RNC INode has no change.
The outage occurs during Step 4 and Step 5.

3.4. UPGRADE DURATION
The global operational duration for a successful upgrade is approximately 12
hours and 15 minutes for a maximal network configuration. During this time up to
4 RNCs can be upgraded in parallel.
Upgrade total duration
735 minutes
(for a maximal network
configuration)
OAM
data
base
2
1
2
2
Wireless
Access
Upgrade Too
l
UA3.1/4.0
CM XML
file
OAM
OAM
data
base
RNC RNC
RNC
RNC RNC
9370 RNC
2
1
2
2
Wireless
Access
Upgrade Tool
UA3.1/4.0
CM XML
fil
e
UA7.1
CM XML
file

2
2
4
2
3
RNC CM XML
file export (all
RNCs in 1 file)
S
o
f
t
w
a
r
e

a
c
t
i
v
a
t
i
o
n

A
u
t
o
m
a
t
i
c

o
n
-
l
i
n
e

2
2
2
3
2
2
2
4
b
u
i
l
d

OAM UTRAN
Upgrade
application
S
o
f
t
w
a
r
e

d
o
w
n
l
o
a
d

&

C
-
N
O
D
E

C
M

X
M
L

f
i
l
e

i
m
p
o
r
t

2
2
2
5
UA8.1
Non-
Passport
CM XML
file
UA8.1
Passport
CM XML
file 2
2
4
2
6
6
Table 1. Upgrade total duration
This duration does not take into account the duration of the fallback.
3.5. MAINTENANCE WINDOW
The maintenance window starts when disruptive operations that affect the service
are performed on the network and ends when all checks and critical tests have
been successfully performed after the upgrade.
If the checks and critical tests failed then a fallback is needed. In this case the
maintenance window ends when the fallback is complete and the service is back.
Maintenance Window
duration
230 minutes (for a
maximal network
configuration)
+
60 minutes for the fallback
Table 2. Maintenance Window duration
3.6. OUTAGE DURATION
During the upgrade, the service is lost at the restart of the RNC nodes at the
software activation phase and is recovered at the end of this step.
The start time of the outage duration is when the alarm Rebooting LP/0 rises,
and the end time is when the alarm The first C-Bearer (cell) set-up is completed
successfully rises associated to OSI State Reporting On Whole Layout global
status checks FDDCell availability on RNC object from Fault | RadioAccess WMS
operator command verification.
Execute How to, action P8 to check active calls in progress on RNC or FDDCell to
verify overall call processing executed by RNC.
Below is the fault number for the two alarms:
- 70780300 The first C-Bearer (cell) set-up is completed successfully.
- 70120200 Rebooting LP/0. --- Reason --- Forcing CP to boot using an alternate
provisioning file due to ACTIVATE PROV operator command.
Outage duration
29 minutes
(for a maximal network
configuration)
Table 3. Outage duration

7

3.7. TWO KINDS OF UPGRADE SEQUENCE
3.7.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.

3.7.2 HOW TO PERFORM SINGLE LEAP UPGRADE PROCESS
The 'Single Leap' upgrade would be used by customers after they have successfully
upgraded a single RNC to the new release, have used multiple feature activation
steps/work orders on this upgrade RNC and they are satisfied that both the
upgrade and new features are working correctly. With this level of confidence,
they would then perform a 'Single Leap' upgrade so that they could simultaneously
upgrade and activate the new features on all other RNC upgrades.
RNC Vn
features xyz
RNC Vn+ 1
features xyzabc
Time
Upgrade RNC Vn - - > Vn+ 1 And feature abc
WAUT WO + WPS WO merged
Build
RNC Vn
features xyz
RNC Vn+1
features xyz
RNC Vn+1
features xyzabc
RNC Vn+1
features xyza
RNC Vn+1
features xyzab
Time
Upgrade
RNC Vn --> Vn+1
Add feature a Add feature b Add feature c
WAUT WO
Build
WPS WO
Depends
WPS WO
Depends
WPS WO
Depends
8
The customers has either already used WPS or used a sanitized provisioning tool to
successfully activate the new features on the first RNC and generated the Single
Leap work order.

When performing a 'Single Leap' upgrade, the user 1) selects the target RNC to be
upgraded, 2) selects the target release that they want the RNC 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 3. 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.8. UPGRADE SEQUENCE TABLE
The following table describes all the steps to be performed in order to complete the
RNC upgrade. None of the steps should be skipped, unless otherwise indicated.
The steps must be performed in the order shown below. The table indicates for
each step its duration and at which page the detailed description can be found.
The fallback step is also indicated if applicable.
The operator may opt to perform an additional full back-up before the upgrade (see
[R6]), but this is not required as part of the upgrade procedure.
Table 4. Upgrade sequence
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
M
R
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
.

P
R
E
R
E
Q
U
I
S
I
S
T
E
S
,

C
H
E
C
K
S
,

B
A
C
K
U
P
S
,

D
O
W
N
L
O
A
D

u
p

t
o

4
2
0

m
i
n
u
t
e
s

Step Duration
minutes

Page Fallback

Upgrade preparation : to be performed at least 24h before starting the upgrade
Check all prerequisites are ok - 3 -
How to - 12 -
Download the RNC software from DVD-
ROM/Local Files to SRS
25 18 -
Checks & Backup
RNC Check 100 23 -
Remove unused software from the RNC *
Input Parameters: targetNode = RNC
90 32 -
Backup RNC in the OAM Database is
mandatory
10 35 -
Backup RNC Image is mandatory 15 36 -
If exists Backup MiB proto Patch 5 58 -
Download on the RNC
Export RNS to the CM XML file 20 38 -
Upgrade the CM XML file 20 40 -
Download Software and Import the C-Node
CM XML file
66 46 -
M
A
I
N
T
E
N
A
N
C
E

W
I
N
D
O
W

2
7
5

m
i
n
u
t
e
s

B
U
I
L
D

5
0
*
*

m
i
n
u
t
e
s
ACTIVATION -> BEGINNING OF THE OUTAGE
Activate the new software on the RNC 60 53
See section
3.9 page
10
O
U
T
A
G
E

2
9

m
i
n
u
t
e
s

If needed Patch the MIB Proto 15-20 60
See section
3.9 page
10
END OF THE OUTAGE
Upgrade the RNC fabric firmware *** 20 64
P
O
S
T

C
H
E
C
K

If needed, apply TAP patches by following
RNC Patching procedure[R4]
30 -
RNC Check 100 23
See section
3.9 page
10
Backup RNC in the OAM Database is
mandatory
10 35 -
Backup RNC Image is mandatory 15 36 -

10
NB: the durations are given for a maximal network configuration.
* This is the average duration but could be longer (up to 180 minutes) if there is a lot of software
to be removed from the passports.
** The operator launches the activation command at OAM level. This command automatically
manages the online build and software activation. The outage begins when the build is complete
(and activation starts).
*** If the fabric firmware requires upgrade, then one or more alarms (70020005 and/or 70020007)
may be issued approximately 20 minutes following a successful software upgrade.

3.9. FALLBACK SEQUENCE TABLE
These steps are used for fallback purposes. They have to be applied only on the
RNCs on which a fallback is needed.
Important: Fallback can be performed only during the maintenance window and
probative phase.
If fallback is required out of the probative period, and if any configuration update
happened between upgrade and fallback, contact your next-level support (the
global WO needs to be applied and the MIB needs to be built).

M
A
I
N
T
E
N
A
N
C
E

W
I
N
D
O
W

2
7
5

m
i
n
u
t
e
s

F
A
L
L
B
A
C
K

U
p

t
o

8
5

m
i
n
u
t
e
s

FALLBACK STEPS
Duration
(minutes)
Sheet
page
If the fallback is to the initial version (UA7.1), backup the configuration in
case reverse fallback is needed.
10 35
If it is needed for the recovery of the configuration in UA7.1, backup the
RNC. *
15 36
If needed, manual fallback to previous software version on the RNC
Input Parameters: targetNode = RNC
20 66
If needed, restore the MIB Proto Patch 15-20 63
Restore RNCs in the OAM Database 20 69

RNC Check 100 23
Table 5. Fallback sequence

NB: the durations are given for a maximal network configuration.
* The duration for backup the RNC depends on the network performance since it is a FTP transfer.
11

4. SHEETS

TO PERFORM THE UPGRADE OPERATIONS,
REFER TO THE APPROPRIATE 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 WMS OAM Client.
ACTIONS

P1. To display the alarms associated with RNC:

- Log into WMS OAM GUI and open the corresponding layout.
- Select the RNC on which the alarms must be checked.
- Right click on the selection and select Show Alarms from the context menu.

Figure 4. Show alarms associated with RNC

The Alarm Manager window appears. It allows the operator to investigate the alarms
that could prevent him/her from starting the upgrade operation on the network
element.
13

P2. To display the RNC OAM link administrative state:

- Select the RNC on which the OAM link administrative state is to be checked.
- Right click on the selection and choose Configuration | Set NEs OAM Link
Administrative State from the context menu.

Figure 5. Launch the Set NEs OAM Link Administrative State window

A dialog box appears. It indicates the current RNC OAM link administrative state
(LOCKED or UNLOCKED) of the selected RNC:

Figure 6. Set NEs OAM Link Administrative State Action Window

It is possible to modify the current value (LOCKED or UNLOCKED) by selecting the
RNC then clicking the desired button (Lock or Unlock button).

NB: After Unlock the link is fully open when the RNC icon in the layout is no longer
blue. Wait for the icon to change from blue before proceeding.
14
P3. To launch the WICL console:

- From the WMS OAM GUI, choose Configuration | Wireless Internet Command
Language (WICL) menu item.

A console window appears. It allows the user to enter any WICL command.

P4. To launch the Equipment Monitor:

- Log into WMS OAM GUI and open the corresponding layout containing 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 7. Launch the Equipment Monitor

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

15

Here is how to get the neId parameter value of the I-Node. To do this, select the
INode tab, then the Mod object from the Equipment Monitor. The neId is the
nodeName value:

Figure 8. How to get the neId parameter value of the I-Node

Here is how to get the value of the mibState: select the RNC tab, check the box
Display whole objects tree, and then select the RncMIB object in the tree. The
mibState value is displayed in the lower pane:

Figure 9. How to get the value of the mibState
INode tab
Mod object
RNC tab
RncMIB
mibState
16

P5. To launch ZAP tool:

- From a telnet/SSH session with the Alcatel-Lucent user on the Main Server:
- Launch the following command (note that the -h option gives the available
options of the tool):

In the OAM Main Server window under Alcatel-Lucent unix user:
(Alcatel-Lucent) % /opt/nortel/shell/sysmgt/wam_zap.sh a f

The ZAP trace files are then generated in the /opt/nortel/data/sysmgt/zap
directory.

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

Note: First check that if there is WCF file under directory: C:/Program
Files/WAUT/WCF. If not, put the file in the following directory: C:/Program
Files/WAUT/WCF (create it if necessary).

Note: There should be only one WCF file in WCF directory; otherwise WAUT will
raise an error message.

P7. To launch the Sessions Manager:

- From the WMS OAM GUI, choose the Configuration | Sessions Manager menu
item.

The Sessions Manager window appears. It allows the user to view the currently active
sessions.

P8. Check active calls in progress on RNC or FDDCell.
To verify overall call progressing executed by RNC or a dedicated FDDCell:

- Execute P4 To launch the Equipment Monitor
- Select RNC Tab and Dynamic Data lower right tab

17

Figure 10. Check active calls in progress on RNC

Figure 11. Check active calls in progress on FDDCell

RNC tab
Dynamic Data tab
RNC tab
Dynamic Data tab
18
DOWNLOAD RNC SOFTWARE FROM DVD-ROM/LOCAL FILES
TO SRS

PRESENTATION
The purpose of this sheet is to describe how to download the new software version
available on the DVD-ROM/Local Files to the SRS (Software Repository Service) disk.
Note that this process only needs to be performed once, regardless of the number of RNCs
being upgraded.
INPUT PARAMETERS
hostnameSRS: The hostname of the SRS server.
INITIAL STATUS
The OAM Main Server is operational and WMS OAM GUI is accessible on a WMS OAM 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 12. SRM GUI

Free space
on the SRS
server Install
Software
Release...
19

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.

The SRS must have at least 1 GB of free space. If there is not enough free space, see
the troubleshooting section to find out how to remove unused software from the SRS.

3. Download process:

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

Figure 13. SRM install software page

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

Figure 14. 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 15. SRM install software data transfer page

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

Figure 16. SRM installation successful page

- At the end of the download, click OK.

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

21


Figure 17. SRM installation details and result

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

4. Download TAP patches software to the SRS as explained in [R4] in Patch installation
procedures part.

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 or McAfee Profile is
recommended. (Please right click on the Cyberarmor or McAfee, select menu "Stop
Profile").
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 in the document referenced
in [A1].

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
Remove them from the SRS by clicking Delete Selected:

Figure 18. SRM delete software page

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

WARNING:
Do not remove an RNC load being used (either active or passive).

23

RNC CHECK

PRESENTATION
The purpose of this sheet is to describe how to check the RNC before starting the upgrade.

Note that this task should be performed for each RNC to be upgraded.
INITIAL STATUS
The OAM Main Server is running and the GUI is accessible from WMS OAM Client.
ACTIONS
1. Import the UA7.1 snapshot into WIPS and run the network check. Ensure all UPGRADE
errors are corrected and cleared prior to proceeding.

2. Check and note all active alarms for the RNC being upgraded.
(See the sheet "How to", action P1 to know how to check the alarms)

There should be no outstanding (i.e. uninvestigated) active alarms on the RNC
before the upgrade. Each alarm found must be investigated before taking the
decision to launch the upgrade procedure.

Repeat the alarm check immediately after the upgrade, ensuring that any new
alarm is investigated.

3. Before starting the upgrade, the RNCs can optionally be set to maintenance mode. To
do this, select the RNC and select Set Maintenance Mode On. This will indicate to all
other users that an important operation is being carried out on the RNC.

Figure 19. Set Maintenance Mode On

After the upgrade is complete, the RNC should be set back to normal mode. To do so,
select Set Maintenance Mode Off.

Note: Alarms are not displayed when set maintenance mode on. Set an NE to
maintenance mode will prevent any further alarms from being displayed in the Alarm
Manager, and in the Resource Browser for NE.

24
4. Check the OAM-RNC link is open (RNC OAM link administrative state = unlocked).
(See the sheet "How to" action P2 to find out how to check the RNC OAM link
administrative state)

5. Check on the RNC that the committed and the current views are identical. To do this,
the following commands must be performed on each node:

- From a telnet/SSH session under Passport system administrator on the
Passport:
- Display the provisioning state and check that the committed and current
views are identical:
In the targetNode Telnet/SSH window under Passport system administrator:
> d pr

Output example:

> d pr

1> d pr
Prov
adminState = unlocked
operationalState = enabled
usageState = idle
provisioningActivity = none
activityProgress = n/a
standbyCpActivity = none
standbyCpActivityProgress = n/a
committedFileName = UA71_RQ01_before_upgrade full.001
currentViewFileName = UA71_RQ01_before_upgrade full.001
lastUsedFileName = ExportDrf_GetPpAsciiView.full.095
provisioningSession =
provisioningUser = none
checkRequired = no
confirmRequired = no
editViewName = ExportDrf_GetPpAsciiView.full.095
editViewAddedComponents = 0
editViewDeletedComponents = 0
editViewChangedComponents = 0
currentJournal = 0
journalDisabledReason = not disabled
restorePossible = no
ok 2007-03-07 21:34:43.57

Check the following attribute values, added, deleted and changed meaning, are 0:


Check the following attribute values, provisioningUser is none, checkRequired and
confirmRequired are no.

checkRequired = no
25

If any of the previously executed provisioning checks cannot be explained and
solved, contact your next-level support.

6 IMPORTANT: Note the RNC committed view name (identical to the current view
name). The operator should record the name of the active view for an eventual
FallBack (See section Software fallback on RNC for details).

7. Perform RNC MIB audit:

- Select the target RNCs, right-click on the selection and select the Audit command:

Figure 20. How to open Audit window

- The Audit Action window will appear.

Figure 21. Audit Action Window

- Click Audit now.

- Check in the Command Manager that there are no errors:

26

Figure 22. Command Manager

Investigate each error, and if needed call your next-level support.

8. Launch the ZAP tool on OAM before starting the RNC upgrade. This will help the
support team in case a problem occurs during the upgrade. (See the sheet "How to",
action P5 to find out how to launch the ZAP tool).

9. Check at least one interface in OAM_NE IP group is OK status before starting upgrade.

Note: if you dont configure OAM_NE IP group during installation, ignore this step.

In the web browser such as Firefox, open the Sun Management Center of OAM server
by input the URL http://<mainserver-hostname>:1500. For example, if Main Server
hostname is zwjb2s76, the URL is http://zwjb2s76:1500.

After click Enter, the Sun Management Center homepage will appear.

Figure 23. Sun Management Center home page

27

Click Launch Java Console to login the Sun Management Center. The login window
will appear.

Figure 24. Sun Management Center login window

Login as oamops user, input the user name and password (oamops/oam_oamops), and
input the Server Host for example zwjb2s76. Then click Login button.

If this is the first time to login Sun Management Center, the Set Home Domain
window will appear. If not the first login, this window will not appear.

Figure 25. Set Home Domain window

Select OAM Supervision and click Set Home button, then the Close button will
be enabled. Click Close button to close the window.

The Sun Management Center main window will appear.

28

Figure 26. Sun Management Center main window

Double click zwjb2s76 icon, the details window for host zwjb2s76 will appear.

29


Figure 27. Sun Management Center host details window

Double click the Operating System | Redundancy Monitoring | Ethernet in turn,
the OAM IP group window will appear.

30

Figure 28. Sun Management Center OAM IP group window

In the right panel of OAM IP group window, check the interface status of OAM_NE IP
group. Before the upgrade, make sure at least one interface in OAM_NE group is OK
status.

If no one interface status in OAM_NE group is OK, call your next level support.

10. After the upgrade right after warning alarm 70780300 The first C-Bearer (cell) set-
up is completed successfully is received, using the OSI State Reporting On Whole
Layout window available in the menu Fault | Radio Access | OSI State Reporting On
Whole Layout, select the RNC parent, to see the FDDCells locked, and note all faulty
FDDCells.

Execute How to, action P8 to check active calls in progress on RNC or FDDCell to
verify overall call processing executed by RNC.

31


Figure 29. OSI State Reporting window

A faulty FDDCell occurs on a RNC 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 RNC upgrade and will need to be
investigated.

WARNING:
All FDDCells are UNLOCKED after upgrade and will be needed to be LOCKED again
according to the initial OSI reporting recorded or the file generated by the following
WICL script before the upgrade:

>: exec dfs:/wicl/utran/NEUpgrade/lockedFDDCellBackup.wcl -dn {RNC UserLabel} -file
<filename>

When the command is completed, all the locked FDDCells are backuped in the file
<filename>.

After upgrade, the following WICL script will lock all the FDDCells in the file
<filename>:

>: exec dfs:/wicl/utran/NEUpgrade/lockedFDDCellRestore.wcl -dn {RNC UserLabel} -file
<filename>

FINAL STATUS
The RNC is operational.
32
REMOVE UNUSED SOFTWARE FROM RNC

PRESENTATION
The purpose of this sheet is to describe how to remove unused software from the RNC disks.

Note that this task should be performed for each RNC to be upgraded.
INPUT PARAMETERS
targetNode the RNC on which unused software should be removed.
INITIAL STATUS
The OAM Main Server is running and the GUI is accessible from a WMS OAM Client.
ACTIONS

ON THE OAM CLIENT:

1. From a telnet/SSH session under Passport system administrator on the targetNode:

2. Run the following CAS commands in the targetNode Telnet/SSH window:

> d Fs part/0
Fs Part/0
capacity = 4.294770 Gbyte
freeSpace = 1.206059 Gbyte
usage = 71 %
mode = shadowed
usageState = active
ok 2007-05-04 15:12:33.43

2.1 The targetNode should not exceed 70% of File System disk usage.

2.2 If there is enough available disk space, continue the upgrade.
Else, remove unused software and provisioning files:

- Remove unused provisioning files:
> l pr v/*
> tidy -remove(<file_name1> <file_name2>... <file_nameN>) Prov
(Where <file_name1> <file_name2>... <file_nameN> are the names of the unused
provisioning files that should be removed)

- Remove unused software:
> list Software ApplicationVersion/*
> tidy -query Software
> tidy Software
33

> list Software ApplicationVersion/*
> display FileSystem Part/0 freeSpace
- Repeat the above sequence until there is enough available disk space.

- The following command can also be used:
> tidy -fromDate(yyyy-mm-dd) -toDate(yyyy-mm-dd) pr

Note 1: It is possible to remove CTBL log files from the
/spooled/closed/appl/rncInCTBinaryLogging directory of the targetNode. Before
removing these log files you can save them in another place than the targetNode
(e.g. on the OAM server).

Here is a command example for removing the logfiles from the tagetNode disk:
> ls -path("/spooled/closed/appl/rncInCTBinaryLogging") fs
Fs
Type Prot Size Date Time Name
dir no 0 2004-10-14 20:56:56 .
dir no 0 2001-01-03 15:04:18 ..
file no 9999252 2010-08-12 12:28:56 CtblLog.0001.20100812T122539.018.0010
file no 9999579 2010-08-12 12:31:58 CtblLog.0001.20100812T122857.019.0010
file no 9999934 2010-08-12 12:35:10 CtblLog.0001.20100812T123159.020.0010
file no 9999327 2010-08-12 13:16:30 CtblLog.0001.20100812T123510.021.0010
file no 9999358 2010-08-12 13:37:06 CtblLog.0001.20100812T131631.022.0010
file no 9998986 2010-08-12 13:55:44 CtblLog.0001.20100812T133707.023.0010
file no 9999932 2010-08-12 14:32:08 CtblLog.0001.20100812T135545.024.0010
file no 9999323 2010-08-12 14:33:58 CtblLog.0001.20100812T143209.025.0010
file no 9999987 2010-08-12 14:35:42 CtblLog.0001.20100812T143359.026.0010
file no 9999941 2010-08-12 14:38:36 CtblLog.0001.20100812T143543.027.0010
file no 9999931 2010-08-12 14:53:34 CtblLog.0001.20100812T143837.028.0010
file no 9998517 2010-08-12 15:02:16 CtblLog.0001.20100812T145335.029.0010
file no 9999908 2010-08-12 15:12:48 CtblLog.0001.20100812T150217.030.0010
file no 9999949 2010-08-12 15:28:06 CtblLog.0001.20100812T151248.031.0010
file no 9999814 2010-08-12 15:44:44 CtblLog.0001.20100812T152806.032.0010
file no 9999636 2010-08-12 15:54:42 CtblLog.0001.20100812T154444.033.0010

ok 2010-12-07 11:33:35.71

> remove -
p("/spooled/closed/appl/rncInCTBinaryLogging/CtblLog.0001.20100812T122539.018.0010") fs
Fs
ok 2010-12-07 11:38:16.98
>

Note 2: It is possible to remove log files from the /spooled/closed/log directory of
the targetNode. Before removing these log files you can save them in another
place than the targetNode (e.g. on the OAM server).

Here is a command example for removing the logfiles from the tagetNode disk:
> ls -path("/spooled/closed/log") Fs
Fs
Type Prot Size Date Time Name
dir no 0 2001-04-18 18:00:00 .
dir no 0 2001-04-18 18:00:00 ..
file no 77666 2004-01-03 00:00:04 ppc_log.20040102T203708.044.1
file no 78269 2004-01-04 00:00:04 ppc_log.20040103T203704.046.1
file no 502288 2004-01-03 20:37:04 ppc_log.20040103T000004.045.1
file no 500889 2004-01-04 20:36:58 ppc_log.20040104T000004.047.1
34
file no 79739 2004-01-05 00:00:04 ppc_log.20040104T203657.048.1
file no 503060 2003-12-31 20:37:08 ppc_log.20031231T000004.039.1
file no 77503 2004-01-01 00:00:04 ppc_log.20031231T203708.040.1
file no 503045 2004-01-01 20:37:06 ppc_log.20040101T000003.041.1
file no 77500 2004-01-02 00:00:04 ppc_log.20040101T203706.042.1
file no 502945 2004-01-02 20:37:08 ppc_log.20040102T000004.043.1
ok 2004-01-05 14:11:24.63
> remove -path("/spooled/closed/log/ppc_log.20031231T000004.039.1") Fs
Fs
ok 2004-01-05 14:30:50.97
>

FINAL STATUS
All unused software is now removed from the targetNode disk.

35

BACKUP RNC IN OAM DATABASE

PRESENTATION
This sheet describes how to backup the initial OAM data and to prepare this data in case a fallback
is needed.

This task must be executed for each RNC to be backed up.
INITIAL STATUS
ACTIONS

1. If not already done, open a WICL console.
(See the sheet "How to", action P3 to know how to open a WICL console)

2. Backup the RNC OAM database:
In the WICL console, enter the following command:

0 # RNC <RNC user label> dbBackup

3. When the command is complete the following message is displayed:

dbBackup OK! The result was stored at dfs:utran/neBackup/RNC-
RNC37158/backup.04_02_0K.20050616133849.bkp

4. Note the backup file name. It will be used if a fallback is needed.

For information, the full path to the backup file is

/opt/nortel/data/utran/neBackup/RNC-<RNC user label>/<Backup file name>

FINAL STATUS
The RNC OAM data in OAM database are backed up and available in case a fallback is needed.

36
BACKUP RNC IMAGE

PRESENTATION
The purpose of this sheet is to describe how to backup the RNC Image.
INITIAL STATUS
The RNC is operational.
ACTIONS

1. If not already done, log in to the WMS OAM GUI.

2. Right-click on the RNC nodes ,and select Configuration | RNC Backup, The RNC
Backup Action window is opened as follows:

Figure 30. RNC Backup Action window
3. When operator select RNCs, and click the RNC Backup button, some checks will be
applied on the selected RNCs. After that, a confirm dialog will pop up as below.

Figure 31. Confirm Dialog for RNC Backup
4. Click OK button to continue back up operation. Then the cancel option and the
progress bar will be managed directly through the command manager window:
37

Figure 32. command manager window

Note: The RNCBackup provides a full backup of the RNC. This means that both view
and MIB are backed up. In a standard fallback sequence (described later in this
procedure) a reload of the view is sufficient to completely restore the 9370 RNC and
the above backup need not to be used. They will be used by the support team in case
a major issue occurs during the upgrade.
FINAL STATUS
The RNC committed view is backed up on OAM
The RNC MIB and views are backed up on OAM.
38
EXPORT RNC TO CM XML FILE

PRESENTATION
The CM XML file export window (at WMS OAM GUI level) allows the user to dump part of (or the
whole) OAM database into CM XML files.

The purpose of this sheet is to describe how to export from the OAM the database object sub-tree
related to the RNC to be upgraded.

This sheet is executed once whatever the number of RNC to be upgraded. All the RNCs to be
upgraded should be exported in the same CM XML file.
INITIAL STATUS
The WMS OAM Client GUI is available.
ACTIONS

1. If not already done, log in to the WMS OAM Client.

2. After having selected all the RNCs to be upgraded, right-click on a RNC icon and select the
Configuration | CM XML | Export NE Grouping menu option like this:

Figure 33. How to open Export NE Grouping
NB: It is possible to select RNC from different groups or resource browsers. (Shift-click to
select multiple NEs)

39

3. The following window appears, listing the RNCs to be exported:

Figure 34. CM XML Export window

This window allows the selection of:

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

The CM XML Export file. Note that such files are generated with a .xcm extension. A
single .xcm file is generated for all the RNCs to be upgraded.

Select the RNCs in the NE Name list, check the provisioning parameters box, select the target
directory (using the Browse button), enter the CM XML filename, and then launch the export
command by clicking Export now.

The export duration depends on the RNC configuration. The export progress is displayed in the
Command Manager window. Once the progress bar is at 100%, check in the generated report
that there were no errors, and then close the command manager and CmXML windows.

FINAL STATUS
The exported CM XML file is available in the <Exported_cmXML_DIR> directory. This file contains
the configuration of all the selected RNCs with all its associated BTS.

Customer
to check
Provisioning
parameter to
select
Target CM
XML file
Output
directory
40
UPGRADE CM XML FILE

PRESENTATION
This sheet describes how to upgrade the initial CM XML file to the target CM XML format.
To do this, the Wireless Access Upgrade Tool (WAUT) and WCF file are used.

Where the initial CM XML file contains data for several RNCs and their associated BTS, this
sheet can be performed for a subset (one or more) of the RNSs, or for all of them together.
Each execution of the Tool results in one output file, regardless of whether the upgrade is
for one or several RNSs.

Note: The WAUT tool and WCF file should be in line with OAM release.

INITIAL STATUS
The initial RNS (RNC + all associated BTS) CM XML file is available in the <Local_directory>
directory on the PC.
ACTIONS

1. First check that if there is WCF file under directory: C:/Program
Files/WAUT/WCF"(create it if necessary). If not, put the file in the following
directory: C:/Program Files/WAUT/WCF ".

Note: The directory can be changed if we choose another directory during the
installation. And there should be only one WCF file in WCF directory; otherwise,
WAUT will raise an error message.

2. If not already done, launch Wireless Access Upgrade Tool. (See How-To P6)

Important: All the following operations must be executed on a blank network.
Save and exit all opened work orders and start with a new workspace as shown
below:

Figure 35. Launch Wireless Access Upgrade Tool

41

3. Import the RNS (and NOT ONLY RNC) initial CM XML file:

- Choose the File | Import and export menu option:

Figure 36. Select Import and export

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

Figure 37. Import and Export Wizard window

- Select the Replace initial snapshot and discard existing work orders mode,
then click Next:

42

Figure 38. Import snapshot(Local file system)

- Using the Browse button, select the initial RNC CM XML file from
<Local_directory>, then click Next:

Figure 39. Select the initial RNC CM XML file

The optional Edit Filter operation that then appears is not used with RNC
Upgrade; proceed by clicking Next.

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

43


Figure 40. Save workspace option window

- A new window indicating the import progress appears:

Figure 41. Import progress window
Once the progress bars reaches 100% (Done), check in the generated report that
there are no errors, and then click Close.

4. Perform the RNC CM XML file upgrade:

- Click on Network tab, select the Network tree, and select the NE Provisioning Upgrade
Operation. (This will automatically include all RNCs in the initial CM XML file.
To select one available RNC under the network tree, select the given RNC and select the NE
Provisioning Upgrade Operation, this will perform the given RNC CM XML FILE upgrade.)

44

Figure 42. Select the NE Provisioning Upgrade Operation

- The NE Provisioning Upgrade Operation window appears.

Figure 43. NE Provisioning Upgrade Operation window

Select the target directory (using the Browse button). The upgraded RNC CM XML
files should be exported in the <Local_directory>/upgraded directory of the PC.

Select the target release (Upgrade to version field): 08_01_00.

Click OK. The following window is displayed during processing, and can be used
to save a summary report of the upgrade.

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

3- Select the NE
Provisioning
Upgrade
Operation

2- Select the
Network tree
1- Click on
Network tab

45


Figure 44. Upgrade report window

Two CM XML files (Inode and NonPassportWO) will be generated.

Figure 45. CM XML file

Note: The INode Workorder is not used for UA7.1 to UA8.1 upgrade.

For the generated NonPassportWO CM XML (NonPassportWO_<date>_<time>.xwo),
follow the opened GPS bulletins if any to update it to guarantee the propagation
of the UA8.1 configuration.

5. Check the WAUT output. Correct all the remaining issues under the right WAUT
workorder. All Workorders are generated in the directory <WAUT Installation
directory>/Upgraded

6. Using a FTP client, transfer the upgraded CM XML files from the PC
<Local_directory>/Upgraded directory to the
/opt/nortel/data/cmXML/<Exported_cmXML_DIR>/upgraded directory on the Main
server.
FINAL STATUS
The CM XML files with the new provisioning are ready to be imported into the OAM
database.
46
DOWNLOAD SOFTWARE TO RNC

PRESENTATION
The purpose of this sheet is to describe how to use the download tool available via the
Configuration | Radio Access | Software | Download menu option of the WMS OAM GUI.
This command allows the user to download the new software to the RNC to be upgraded.

Note: This task is performed once whatever the number of RNC to be upgraded.
INITIAL STATUS
The RNC MIBs are built (check alarms and icons to make sure they are built).
The new RNC software to be downloaded has been downloaded to the SRS.
Check that no session is currently active for the RNC to be upgraded (See the sheet "How
to", action P7 for details on how to open the Sessions Manager).
ACTIONS
1. If not already done, log in to the WMS OAM GUI.

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

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

Figure 46. 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 Rnc option and click Next:

47


Figure 47. 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 48. Download wizard: Select the Network Element type(from right-click menu)

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

Figure 49. Download wizard: Select Software Version to Download

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

Figure 50. Download wizard: Retrieved Node(s)
When launch from right-click menu, select the RNCs(the available nodes just are the
right-click selected RNC nodes) on which the download operation should be
performed, add them to the right-hand pane and click Next. Following figure shows
the selected RNC is RNC501.

Figure 51. Download wizard: Retrieved Node(s)
Note that the RNCs to be upgraded must have the status IDLE.
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

7. On the Upgrade Type Selection page, select the upgrade type with new MIB. Click
the Select CM_XML File button, and select the CNode CM XML file
(NonPassportWO_<data>_<time>.xwl file generated by WAUT). Click Select and then
Next:

49


Figure 52. Download wizard: Upgrade Type Selection

8. On the Search Criteria Summary page, check the summary of the RNC list. Check
the selection and click Download to validate it. Otherwise, click Back to modify the
selection.

Figure 53. Download wizard: Search Criteria Summary

9. The last page of the wizard shows a success message. Check the Launch Command
Manager, on close box, and click Finish to exit the wizard:

Figure 54. Download wizard: Complete

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.
50
10. Once the download wizard is closed, the Command Manager is displayed and allows
you to monitor the download progress:

Figure 55. Download:Command Manager

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

11. Wait for the end of the download. When a download on a RNC ends, the status
indicates Successful for each selected Network Element.

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. For instance when RNC is in upgrade session,
lock/unlock of FDDCell is not allowed.

Note:
An upgrade session encapsulates a series of operations in order to perform a NE
upgrade (RNC or Node B). 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 passport in order to prepare its 9370
RNC with new MIB- type 6 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.

51

- 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 passport software download is differential.

Software Download Exit Step:
If the software download has been completed, but the RNC 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 56. How to open Inventory & Upgrade Session

Then select the current running software.

Figure 57. Select the current running software

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

52

Figure 58. Select NE with status DOWNLOAD_COMPLETED

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

Figure 59. The inventory after execute Abort upgrade session

FINAL STATUS
The software is downloaded to the RNCs.
53

ACTIVATE THE NEW SOFTWARE ON RNC

PRESENTATION
The purpose of this sheet is to describe the activate command available from the
Configuration | Radio Access | Software | Activate menu option of the WMS OAM GUI.
The operator is allowed to perform activation after downloading the software has been
successful completed. It is not mandatory to perform this command straight after the
download. The activation command should be postponed to the maintenance window.

Note: This task is performed once whatever the number (up to 4) of RNCs to be upgraded.

Before launching the activation, ensure that the passport (I-Node) is not in provisioning
mode and also ensure there is no scheduled export at the same time.
INPUT PARAMETERS
None
INITIAL STATUS
The software to activate has been downloaded to the RNC.
The MIB of each RNC is built.
ACTIONS
1. From a telnet/SSH session under Passport system administrator on the I-Node.

Display the file system and check that the 2 CP disks are synchronized. To check if
the syncStatus is set to synchronized, use d fs command:

Output example:

> d fs
Fs
usageState = active
volumeName = volumeNotSe
activeDisk = Fs Disk/1
syncStatus = synchronized
syncProgress = 100 %
ok 2005-03-28 14:58:04.99

If they are not, launch the following command.

> sync fs

2. If not already done, log in to the WMS OAM GUI under administrator user.
54
3. There are two ways to launch Activate wizard:1),Choose Configuration | Radio
Access | Software | Activate.2)From network layout right-click the selected nodes
or group ,choose Configuration | Software | Activate:
Then, different pages guide the user through the different steps.

4. The first page introduces the software activation wizard. Click Next.

Figure 60. Activation wizard: Introduction

5. On the Select the Network Element type page, when Launch from menu bar, select
the Rnc option and click Next:

Figure 61. Activation wizard: Select the Network Element type
When launch from right-click menu, the network element type cant be chosen,
click Next:

Figure 62. Activation wizard: Select the Network Element type
55

6. On the Retrieved Node(s) page, select the RNCs(the available nodes are all RNCs
detected in network when launching from menu bar; the available nodes just are the
right-click selected RNCs when launching from right-click menu) on which the activate
operation should be performed, add them to the right-hand pane and click Next:

Figure 63. Activation wizard: Retieved Node(s)

Note that the RNCs to be activated must have the status DOWNLOAD_COMPLETED.
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.

7. On the Search Criteria Summary page, check the summary of the RNCs on which
the activation will be performed:

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

Figure 64. Activation wizard: Search Criteria Summary

8. The last page of the wizard shows a success message. Click Finish to exit the wizard.

56

Figure 65. Activation wizard: Complete
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.

9. Once the activation wizard is closed, the Command Manager is displayed and allows
you to monitor the activation progress:

Figure 66. Activation: Command Manager

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

10. Wait for the end of the activations. When activation on RNC ends, the status
indicates Successful for each selected Network Element.

11. Wait for the end of the RNC reset sequence. At the GUI level, the RNC icon may
change appearance during this process, depending on the Maintenance mode.
If Maintenance mode is Off, the RNC icon becomes blue when the connection is
lost:
57

.
Figure 67. Blue icon

Note that when the supervision is lost, the critical alarm Loss of supervision is
also generated.

Wait until the RNC icon changes to a color other than blue.

If Maintenance mode is On, the RNC icon remains brown while the connection is
lost:
.
Figure 68. Brown icon

Note that if the activation command is not finished within 90 minutes, the following
error message is displayed at the upgrade application GUI:

Passport Activation timeout reached

If this error message occurs, call the next level of support for investigations.

FINAL STATUS
The activate operation has been performed.

58
BACKUP THE MIB PROTO PATCH FILE

PRESENTATION
This sheet describes the procedure to backup RNC MIB Proto patch file.
INPUT PARAMETERS
targetNode the RNC on which MiB proto patch file should be backuped.
IP_TargetNode the IP address of the targetNode.
admin_pwd the password for the Passport system administrator.
INITIAL STATUS
ACTIONS
1. Open a Telnet/SSH session on the targetNode:
In the OAM main Server window under Alcatel-Lucent unix user:
% telnet IP_TargetNode
login: Passport system administrator
password: admin_pwd

2. Identify the RNC software version of the targetNode:
> d sw avl
Sw
avList = base_RI60611, atmNetworking_RI60611,
genericUtilities_RI60611,ip_RI60611,
wanDte_RI60611, iRNC_RI60611,
networking_RI60611, ss7_RI60611,
wirelessCommon_RI60611, fabric_RI60611,
ethernet_RI60611, ipsec_RI60611,
secureShell_RI60611, baseExt_RI606110A0202,
apcBase_RI606110A0202, iRNCApc_RI606110A0202,
ss7Apc_RI606110A0202, cnp_RI606110A0202,
cRNCApc_RI606110A0202, patch_RI6061102w08D,
RNCCiph_RI606110A0202
ok 2010-06-28 13:56:28.55
Select the extension of cRNCApc module to retrieve software version:
The software version is RI606110A0202.

3. Backup MiB proto Patch if any:
% ftp IP_TargetNode
password: admin_pwd

Check if a patch file already exists:
ftp> cd /sfs2/share/rw_data
250 Changed directory to "/sfs2/share/rw_data"
ftp>
ftp> ls
59

200 Port set okay
150 Opening ASCII data connection
Mib1
Mib2
mibDirLinks.txt
committedMibFile.txt
Assoc_0_1
..
Assoc_6_15
FileStatWriten
SAVE_mibDirLinks.txt
mibPatch_SWversion.txt
hwCapability.txt

226 Transfer complete
287 bytes received in 0.089 seconds (3.13 Kbytes/s)
ftp>

Save patch file on a SUN machine:
ftp> get mibPatch_SWversion.txt
200 Port set okay
local: mibPatch_SWversion.txt remote: mibPatch_SWversion.txt
64 bytes received in 0.076 seconds (0.83 Kbytes/s)
ftp>

Note: This file needs to be attached to the case and sent to GPS before upgrade to check
whether a modification is necessary in the new SW version.

FINAL STATUS
The RNC MIB Proto is backuped.

60
PATCH THE MIB PROTO

PRESENTATION
This sheet describes the procedure to patch the RNC MIB Proto:
1) Apply the patch(es)( only 1 MIB patch can be active / activated at a moment in time)
2) At the OAM, Build Online the RNC

All MIB proto patches will survive until a new MIB Proto is delivered (upgrade). In case of
an upgrade, the patches need to be re-applied (and maybe re-formulated if objects change
in the new MIB). Contact UTRAN GPS SYSTEM team or refer to the following URL before the
upgrade to check whether the patched are still applicable:

https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=31324984&objAction=browse&sort=name&v
iewType=1

Note: In case of upgrade this procedure must be applied after the software activation to
take into account the new mibproto installed. Operational Impact: outage of 15-20
minutes.

INITIAL STATUS
The RNC has been activated and need patch the MIB Proto.
ACTIONS
In the following procedure, <mibPatch_NewSWversion> refers to the patch youve been
given by GPS SYSTEM team.

password: admin_pwd

2. Check the name of MIB patch matches the RNC load name.
> d sw avl
Sw
avList = base_RI71224, atmNetworking_RI71224,
genericUtilities_RI71224,ip_RI71224,
wanDte_RI71224, iRNC_RI71224,
networking_RI71224, ss7_RI71224,
wirelessCommon_RI71224, fabric_RI71224,
patch_RI71224, ethernet_RI71224,
secureShell_RI71224, ipsec_RI71224,
baseExt_RI712240A3302, apcBase_RI712240A3302,
iRNCApc_RI712240A3302, ss7Apc_RI712240A3302,
cnp_RI712240A3302, cRNCApc_RI712240A3302,
RNCCiph_RI712240A3302
ok 2010-09-20 15:00:05.03

61

The extension of cRNCApc module is load name; it is RI712240A3302 in this
example. And the MIB patch file should be mibPatch_RI712240A3302.txt.

If the name does not match the cRNCApc module extension, you need to rename the
MIB patch file to the new load name.

3. Put MIB Proto patch file:
ftp>

ftp> put mibPatch_NewSWversion.txt
200 Port set okay
local: mibPatch_SWversion.txt remote: mibPatch_NewSWversion.txt
64 bytes sent in 0.00077 seconds (81.23 Kbytes/s)
ftp>

4. Go to the OAM and build (Online) your RNC (typical downtime: 15-20 minutes).

5. Patch application check
password: admin_pwd

6. Retrieve the active OMU:
> d lp/* ap/* rnc role, instance
Lp/* Ap/* RncAp
+==+==+-------+----------+----------------------------------------
|Lp|Ap| role | instance |Response
+==+==+-------+----------+----------------------------------------
| 2| 0|aMaste | 0|
| 2| 1|tmu | 0|
| 2| 2|rab | 0|
...
| 4| 5|sOmu | 0|

| 5| 5|aOmu | 1|
ok 2010-06-28 14:53:19.98

Instance of the active OMU (aOmu) is 1.

7. Connect to the active OMU:
telci omu(1) rncin

Trying 127.1.5.7...
Connected to 127.1.5.7.
Escape character is '^]'

Telnet CI commands:
Q - quit telci
G - redirect global output.

62
telci(omu)>

8. Read Static parameter MIB change:
Mib read your_static_parameter
Result of: mib read your_static_parameter
your_static_parameter new_value
telci(omu)>
telci(omu)> Q
Bye...

Connection closed by foreign host.
RncIn
ok 2010-06-28 15:10:06.70

FINAL STATUS
The RNC MIB Proto is patched.

63

RESTORE THE MIB PROTO PATCH

PRESENTATION
This sheet describes the procedure to restore the MIB Proto patch file. Operational Impact:
typical downtime 15-20 minutes. This procedure has to be used in case of fallback (running
SW = SWversion).
INITIAL STATUS
The RNC is patched.
ACTIONS
In the following procedure, < mibPatch_NewSWversion> refers to the patch youve been
given by GPS.

password: admin_pwd

2. Remove new MIB Proto patch file:
ftp>

ftp> del mibPatch_NewSWversion.txt
250 File "mibPatch_NewSWversion.txt" deleted
ftp>

3. Restore the old MIB Proto patch file:
If the original MIB Proto path file (mibPatch_SWversion.txt) is still present in RNC, skip
this step.
ftp> put mibPatch_SWversion.txt
200 Port set okay
local: mibPatch_SWversion.txt remote: mibPatch_SWversion.txt
64 bytes sent in 0.00077 seconds (81.23 Kbytes/s)
ftp>

4. Go to the OAM and build (Online) your RNC (typical downtime: 15-20 minutes).

FINAL STATUS
The RNC MIB Proto is restored.

64
UPGRADE THE RNC FABRIC FIRMWARE IF NEEDED

PRESENTATION
The Passport platform includes two switching fabric card packs that provide fully
redundant connections for all card to card (FP and CP) traffic routing. These fabric cards
are programmed through firmware that is updated periodically to address new features
and bug fixes.

A fabric firmware upgrade is required after the RNC upgrade if the following alarms are
present on the I-Node: 7002 0005 and / or 7002 0007.

The upgrade of the Fabric firmware is performed on a Fabric card by Fabric card basis
without service interruption. This is possible as each fabric card has sufficient reserve
capacity to handle the full committed shelf switching bandwidth.

Fabric card firmware upgrade is required infrequently (typically several major releases will
be deployed between Fabric FW Upgrades).

The upgrade of the fabric firmware ensures that the version in the control processors (CPs)
is compatible with the new software version the RNC has been upgraded to.

The fabric that receives the new firmware version is locked and the fabric that does not
receive the new firmware version must be unlocked and enabled.

Note: The new fabric card firmware can be installed at any time during normal switch
operation.

INPUT PARAMETERS
None
INITIAL STATUS
The RNC has been upgraded and is running the new software version.
Fabrics on the RNC are installed and operational.
The following alarms are raised on the I-Node: 7002 0005 and / or 7002 0007.
ACTIONS
1. From a telnet/SSH session under Passport system administrator on the I-Node.
Type the following command to get the recommendedVersionToInstall.

> d shelf fabric/x recommendedVersionToInstall
Shelf FabricCard/x
recommendedVersionToInstall = RI41036
ok 2004-11-26 15:21:52.47

The response (a load number) means that you need to upgrade the firmware.

2. Lock the fabric that will receive the new firmware.

> lock shelf fabricCard/<fabcard_inst>
65


Where <fabcard_inst> is the instance of the fabric card, X for a fabric in the upper cage or Y
for a fabric in the lower cage.
A Passport 15000 has 2 rows of slots used for the CPs and FPs. Slots 0-7 are on the top half
of the card cage and slots 8-15 are on the lower portion of the card cage. if you look at the
back of a Passport 15000, then you will see that the 2 fabric cards are mounted flat to the
back of the card cage with one behind slots 0-7 (upper fabric X) and the other behind slots
8-15 (lower fabric Y).

3. Install the new firmware on the fabric.

> install -file(<load>) shelf fabricCard/<fabcard_inst>

Where <load> is the software load version of the firmware. For example, install CE01B for
fabric_CE01B and the <fabcard_inst> is the one used in step 2.

Wait a few minutes for the firmware to be installed, and for the system to notify
the operator of any errors.

4. Display the attributes of the fabric banks:

> display shelf fabricCard/<fabcard_inst> banks

Where the <fabcard_inst> is the one used in step 2.

5. Verify that the fabric operates correctly with the new firmware:

> start shelf fabricCard/<fabcard_inst> test

The test results show whether the fabric is operating correctly.

6. If there are problems with the upgraded fabric, it might be necessary tomake the
fixed bank the bankOnShelfRestart using the following command:

> set shelf fabricCard/<fabcard_inst> bankOnShelfRestart
fixed

If the writable bank is set as the committed bank and it becomes corrupt, the fabric
might not come up. If the writable bank is corrupt, it must be replaced. Contact
your Alcatel-Lucent representative.

7. Unlock the fabric to return it to service:

> unlock shelf fabricCard/<fabcard_inst>

FINAL STATUS
The fabric firmware has been upgraded.

66
SOFTWARE FALLBACK ON RNC

PRESENTATION
This sheet describes the procedure for performing a manual fallback of the RNC to an older
version, and to the previous provisioning views.

Note that if the upgraded node experiences a problem either during the upgrade or
directly following the upgrade, the fallback will be handled automatically.
INPUT PARAMETERS
targetNode the Node on which to perform the software fallback.
IP_TargetNode the IP address of the targetNode.
admin_pwd the password for the Passport system administrator.
INITIAL STATUS
The targetNode has been upgraded, but the operator wants to undo the upgrade on this
node.
The old provisioning view is still on the CP disk.
ACTIONS
(See the sheet How to, action P3 to know how to open a WICL console)

2. Backup the RNC in case it is needed for the recovery of the configuration(See page 36
for details).

3. On the RNC to fallback, delete all calltrace session using NSP GUI menu Performance
| Radio Access | Call Trace Wizzard for UMTS.

See [R3] for details on how to delete the call trace sessions

password: admin_pwd

5. Reload the OLD provisioning view of the targetNode:

Check the saved views of the targetNode:
> ls p(provisioning) fs

Reload the OLD provisioning view using the name that was noted before the upgrade:
> reloadCp -file(<OLD_provisioning_view>) Lp/0
Where <OLD_provisioning_view> is the named of the view to restore (noted prior to the
upgrade)
67


After the command is issued:
The standby CP will be restarted. It will switch over when the file system is
synchronized after some minutes.

To get synchronization status of the two CP, open a new Telnet/SSH session on
the RNC, type the following command:
In the targetNode Telnet/SSH window under "Passport system administrator":
> d fs

Output example:
Fs
usageState = active
volumeName = volumeNotSe
activeDisk = Fs Disk/1
syncStatus = synchronized
syncProgress = 100 % ok 2005-03-28 14:58:04.99

The new provisioning has to be confirmed within 20 minutes.

The Telnet/SSH session disconnects. Open a new one after the targetNode has
started (this could take several minutes).

6. To confirm the provisioning and commit the new software, type the following
commands:
Confirm the provisioning:
> confirm prov

Commit the provisioning:
> commit prov

Check the value of usageState is idle.
Check the value:
> d pr

Output example:
> d pr
Prov
usageState = idle
provisioningActivity = none
activityProgress = n/a
standbyCpActivity = none
standbyCpActivityProgress = n/a
committedFileName = RI60505_PROV_111120091545.full.002
currentViewFileName = RI60505_PROV_111120091545.full.002
lastUsedFileName = RI60505_PROV_111120091545.full.002
68
provisioningSession =
checkRequired = no
editViewName = RI60505_PROV_111120091545.full.002
currentJournal = 0
journalDisabledReason = not disabled
restorePossible = no
ok 2009-11-26 16:46:55.76

Display and check that the current software (and patch level if applicable) is the one
targeted for the fallback:
> d p sw avl

FINAL STATUS
The targetNode is now downgraded to the old version and operational.

69

RESTORE RNC IN OAM DATABASE

PRESENTATION
This sheet describes how to restore the OAM data during a fallback operation.
This task must be executed for each RNC to be restored.
INITIAL STATUS
ACTIONS
1. Wait until OAM-RNC link is opened again for successful RNC supervision means RNC
has exited its previous blue color state of loss of supervision.

2. Lock the OAM-RNC link (RNC OAM link administrative state = locked).
(See the sheet "How to", action P2 to know how to check the RNC OAM link
administrative state)

(See the sheet "How to", action P3 to know how to open a WICL console)

4. Restore the RNC OAM database using the backup file (several files may be present in
/opt/nortel/data/utran/neBackup/<RNC user label>, one is from the initial
configuration and others are from the upgraded configuration)

In the WICL console:
0# RNC <RNC user label> dbRestore dfs:utran/neBackup/RNC-<RNC user label>/<Backup file
name>

When the command is complete the following message is displayed:
dbRestore OK, the file used for restoration is dfs:utran/neBackup/RNC-
RNCM1_410/backup.04_01_00.20050630174535.bkp

5. Unlock the OAM-RNC link (RNC OAM link administrative state = unlocked).
(See the sheet "How to", action P2 on how to check the RNC OAM link administrative
state)

6. Wait until OAM-RNC link is opened again for successful RNC supervision means RNC
has exited its previous blue color of loss of supervision.

7. To make sure that OAM database restoration operation completed successfully check
in the equipment monitor that the MIB state is buildUpToDate (see the sheet "How
to", action P4 on how to find the mibState parameter value of the RNC). Check for
alarm in the Alarm Manager (see the sheet How to, action P1 on how to find the
alarms associated with a RNC). If the MIB state is not buildUpToDate, and the alarm
is MIB not build, then MIB rebuild is necessary.
FINAL STATUS
The backed-up RNC OAM data has been restored in the OAM database.

70
HOW TO USE THE WAUT UPGRADE REPORT

PRESENTATION
This sheet describes how to use the WAUT upgrade report.

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 69. 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' in
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
the values are set by the WAUT Template and that the original parameter value has
been preserved.
71




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

73

W-CDMA
Upgrade Procedure
Alcatel-Lucent 9370 Radio Network Controller Software Upgrade Procedure Using
OAM 8.1: Inter Release Upgrade
Alcatel-Lucent Internal Proprietary Use pursuant to Company instruction

Copyright 2003-2012 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-148
Document issue: 07.07/EN
Document status: Standard
Product release: OAM08.1
Date: December 2012

20500148UA08.1 - V1 - Alcatel-Lucent 9370 Radio Network Controller - Software Upgrade Procedure Using OAM 8.1 - Inter Release Upgrade

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

20500148UA08.1 - V1 - Alcatel-Lucent 9370 Radio Network Controller - Software Upgrade Procedure Using OAM 8.1 - Inter Release Upgrade

Încărcat de

Drepturi de autor:

Formate disponibile

NN-20500-148

Wireless Service Provider Solutions

S-ar putea să vă placă și