Dsbssapp000010_17 05en_BSS Upgrade Procedure

BSS UPGRADE PROCEDURE Document number: DS/BSS/APP/0010 Document issue: 17.05 / EN Document status: Standard Date: 01/SEP/2009

External document

Copyright 1997 - 2009 Nortel Networks, All Rights Reserved

Printed in France

NORTEL CONFIDENTIAL

The information contained in this document is the property of Nortel Networks. Except as specifically authorized in writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation and maintenance purposes only.

The content of this document is provided for information purposes only and is subject to modification. It does not constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information contained herein, including but not limited to the suitability and performances of the product or its intended application.

This is the Way. This is Nortel, Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All other trademarks are the property of their owners.

without notice. Nortel Networks assumes no responsibility for errors that might appear in t.All other brand and

BSS UPGRADE PROCEDURE

Nortel confidential

DS/BSS/APP/0010 17.05 / EN Standard 01/SEP/2009 Page 2/142

PUBLICATION HISTORY 01/SEP/2009

Issue 17.05 / EN, Standard

CR Q02061621

iPOR Review: 503307

27/AUG/2009 Issue 17.04/ EN, Standard

CR Q02063950

iPOR Review: 502396

11/AUG/2009 Issue 17.03/ EN, Standard

RFF 35240

iPOR Review: 498522

07/JUL/2009 Issue 17.02/ EN, Standard

CR Q02043379

iPOR Review: 490687

02/JUL/2009 Issue 17.01 / EN, Standard

CRs Q02039111, Q02036901

iPOR Review: 489479

22/MAY/2009 Issue 15.25 / EN, Standard

CRs Q02020218, Q01849534

iPOR Review: 478290


Nortel confidential



CR Q02029475

iPOR Review: 475638


CR Q02013162

iPOR Review: 474860

10/APR/2009 Issue 15.22 / EN, Standard

CR Q02005152

iPOR Review: 463684

24/MAR/2009 Issue 15.21 / EN, Standard

CR Q01972377

iPOR Review: 457185


CRs Q01992910, Q01994600

12/JAN/2009 Issue 15.19 / EN, Standard

RFF 44444

13/NOV/2008 Issue 15.18 / EN, Standard

CR Q01956857


Nortel confidential



CR Q01954691


CR Q01954040, Q01954133

31/OCT/2008 Issue 15.15 / EN, Standard

CR Q01951192


CR Q01916497


CR Q01933433

11/SEP/2008 Issue 15.12 / EN, Standard

CR Q01915797


CR Q01923986


CR Q01860190-01


Nortel confidential



RFF 34634


CR Q01905933


CR Q01879111


CR Q01851642-01

25/JUN/2008 Issue 15.05 / EN, Standard

RFF 34634


CR Q01855584-01

29/FEB/2008 Issue 15.03 / EN, Standard

CR Q01836387 (Global Merge -> RFF 33303, 34652, CR Q01747930, Q01750680-01, Q01754307)


CR Q01748979


Nortel confidential



Update for V18.0, Q01737378, RFF 32092


CR Q01738078

30/AUG/2007 Issue 14.21 / EN, Standard

CR Q01736121


Additional correction for CR Q01648581


CR Q01657053-01


CR Q01658641


CR Q01648581


CR Q01620315


Nortel confidential



CR Q01614612


CR Q01613350


CR Q01598397-01


CRs Q01587647, Q01564216


CR Q01592819


RFF 32352


Update for RFF 30685, 30686


CR Q01463876-01


Nortel confidential



Update for RFF 29718


CR Q01448536-01


RFF 32736, CR Q01411911, CR Q01377191, CR Q01371974


RFF 32361, 32362


CR Q01426528


Update for V17.0


CR Q01346181


CR Q01319250


Nortel confidential



CR Q01334118-01


CR Q01328441, Q01328627


CR Q01322261


CR Q01310189


CR Q01310071


CR Q01292583-01


CR Q01280836-16, Q01295567-13


Update for RFF 25316


Nortel confidential


20/DEC/2005 Issue 13.08 / EN, Standard

CR Q01278850


CR Q01263571, Q01273676, Q01273764


Update for RFFs 20365, 27689, 28602, 27891, 27892, 16411


CR Q01013314 additional correction


CRs Q01217426-01, Q01207481-01


Update after review, CR Q01013314


CRs Q01182763, Q01182743, Q01181194


Update for V16.0, CR Q01183672


Nortel confidential



CR Q01148400


CR Q01079139, CR Q01065449-01 additional correction


NFI 308, NFI 319, NFI 329, RFF 28839


Update for V15.1.1, CRs Q01063764-01, Q01065449-01


CR Q01083145


CR Q01078551


CR Q01070379-02


CRs Q00954779-01, Q00959273-01


Nortel confidential



CR Q01000519-01


BTS18000 high power RM system introduction


BSC e3 upgrade improvement feature implementation

CRs Q00939168, Q00931594, Q00919016-01, Q00943427, Q00943422, Q00927662, Q00906307, Q00935280, Q00932282, Q00936387, Q00928661, Q00939208, Q00927655, Q00970538


CR Q00897109-01


CR Q00946695


CR Q00944693


BTS background downloading feature implementation


Nortel confidential



CR Q00927430


CR Q00892954, Q00907440-01, Q00907453-01, Q00910188, Q00927430


CR Q00865036


Update for V15.1


CR Q00858403


CR Q00853958, Q00853388


CR Q00843661 Additional corrections


CR Q00843661


Nortel confidential



CR Q00839667


CR Q00834522, Q00836018


CR Q00822475-01


CR Q00817239, Q00823511


CR Q00808175-01


CRs Q00713993-02, Q00759710-01, Q00782613


CRs Q00726649-08, Q00740588


V15


Nortel confidential



V14


V13


V12


V11


V10


V9


Creation


Nortel confidential


CONTENTS

1. INTRODUCTION .........................................................................................................................19 1.1. SUBJECT................................................................................................................................19 1.2. SCOPE...................................................................................................................................19 1.3. PRELIMINARIES FOR ALL UPGRADES ........................................................................................19 1.4. BSC UPGRADE ......................................................................................................................19

1.4.1 BSC Counter List ..........................................................................................................20 1.4.2 BSC DataConfig modification .......................................................................................20 1.4.3 Context of Circuit Group Block .....................................................................................20

1.5. TCU UPGRADE.......................................................................................................................20 1.5.1 TCU e3 upgrade ...........................................................................................................20

1.6. BTS UPGRADE WITHOUT BACKGROUND DOWNLOADING ............................................................21 1.7. BTS UPGRADE WITH BACKGROUND DOWNLOADING ..................................................................21 1.8. BTS UPGRADE PROCEDURES COMPARED ................................................................................23

2. RELATED DOCUMENTS............................................................................................................24 2.1. APPLICABLE DOCUMENTS........................................................................................................24 2.2. REFERENCE DOCUMENTS .......................................................................................................24

3. GENERAL DESCRIPTION..........................................................................................................25 3.1. READ CAREFULLY...................................................................................................................25 3.2. PREREQUISITES .....................................................................................................................25 3.3. IMPORTANT NOTES .................................................................................................................25

3.3.1 The order of upgrade ....................................................................................................25 3.3.2 BTS software downloading ...........................................................................................25 3.3.3 Synchronization ............................................................................................................26 3.3.4 Call drop analysis .........................................................................................................26 3.3.5 Interference matrix ........................................................................................................26 3.3.6 Software versions compatibility ....................................................................................26

3.4. HUMAN RESOURCES...............................................................................................................26 3.5. OMC-R ACCESS ....................................................................................................................26

4. PRELIMINARIES FOR ALL UPGRADES...................................................................................28 4.1. PRELIMINARIES SEQUENCE TABLE ...........................................................................................28

5. E3 BSC UPGRADE.....................................................................................................................29 5.1. REQUIREMENTS .....................................................................................................................29 5.2. E3 BSC UPGRADE SEQUENCE TABLE ......................................................................................30 5.3. FILES GENERATED BY THE UPGRADE TOOL...............................................................................32

5.3.1 Shell file: .......................................................................................................................32 5.3.2 Command file:...............................................................................................................32 5.3.3 Log file: .........................................................................................................................32

5.4. FALLBACK AFTER UPGRADE COMPLETION.................................................................................32


Nortel confidential


5.5. E3 BSC FALLBACK SEQUENCE TABLE......................................................................................33

6. BTS UPGRADE WITH BACKGROUND DOWNLOADING........................................................35 6.1. REQUIREMENTS .....................................................................................................................35 6.2. BTS UPGRADE BY BACKGROUND DOWNLOADING WITHOUT THE IMMEDIATE ACTIVATION SEQUENCE TABLE 36 6.3. BTS UPGRADE BY BACKGROUND DOWNLOADING WITH THE IMMEDIATE ACTIVATION SEQUENCE TABLE 38 6.4. FILES GENERATED BY THE UPGRADE TOOL...............................................................................39

6.4.1 Shell files:......................................................................................................................39 6.4.2 Command files: .............................................................................................................39 6.4.3 Log file: .........................................................................................................................39 6.4.4 Configuration file: ..........................................................................................................39

6.5. FALLBACK AFTER UPGRADE COMPLETION.................................................................................40 6.6. BTS BACKGROUND DOWNLOADING FALLBACK SEQUENCE TABLE...............................................41

7. BTS UPGRADE WITHOUT BACKGROUND DOWNLOADING ................................................43 7.1. UPGRADE METHODS ...............................................................................................................43 7.2. THE INTERFACE OF THE BTS UPGRADE TOOL...........................................................................44 7.3. BTS UPGRADE WITHOUT BACKGROUND DOWNLOADING SEQUENCE TABLE .................................46 7.4. FILES GENERATED BY THE UPGRADE TOOL...............................................................................47

7.4.1 Shell files:......................................................................................................................47 7.4.2 Command files: .............................................................................................................47 7.4.3 Log file: .........................................................................................................................48

7.5. FALLBACK AFTER UPGRADE COMPLETION.................................................................................48 7.6. BTS UPGRADE WITHOUT BACKGROUND DOWNLOADING FALLBACK SEQUENCE TABLE .................49

8. E3 TCU UPGRADE .....................................................................................................................50 8.1. E3 TCU UPGRADE SEQUENCE TABLE ........................................................................................50 8.2. FILES GENERATED BY THE UPGRADE TOOL...............................................................................52

8.2.1 E3 log file: .....................................................................................................................52 8.3. FALLBACK AFTER UPGRADE COMPLETION.................................................................................52 8.4. E3 TCU FALLBACK .................................................................................................................52

9. IPM UPGRADE............................................................................................................................53 9.1. FILES GENERATED BY THE UPGRADE TOOL...............................................................................54

9.1.1 Log file: .........................................................................................................................54 9.2. FALLBACK AFTER UPGRADE COMPLETION.................................................................................55

10. SHEETS.......................................................................................................................................56

ABBREVIATIONS AND DEFINITIONS...............................................................................................132 10.1. ABBREVIATIONS ...................................................................................................................132 10.2. DEFINITIONS ........................................................................................................................135


Nortel confidential


11. TYPOGRAPHIC CONVENTIONS.............................................................................................139 11.1. GENERAL CONVENTIONS.......................................................................................................139 11.2. INTERACTIVE TERMINAL SESSIONS.........................................................................................139 11.3. INTERACTIVE GRAPHIC SESSIONS ..........................................................................................140 11.4. SEQUENCE TABLE CONVENTIONS...........................................................................................141


Nortel confidential


1. INTRODUCTION

1.1. SUBJECT This document provides a description of the procedures aiming at version/edition/patch upgrade of BSS network elements. Every procedure is performed remotely from the OMC-R site and allows executing necessary actions in a more secure mode. The following operations are available:

The preparatory phase called Preliminaries for all upgrades. It is performed before upgrade itself and is run once for the whole upgrade campaign.

BSC upgrade*. TCU upgrade**. BTS upgrade. BTS upgrade by background downloading.

Every upgrade procedure contains a mandatory preparation phase which must be executed in advance before the maintenance window. *This procedure is not applicable to upgrade BSC with architecture changing. Within this procedure BSC e3 refers to all possible BSC architectures as well. **This procedure is not applicable to upgrade TCU with architecture changing. Within this procedure TCU e3 refers to all possibleTCU architectures as well.

1.2. SCOPE This procedure is applicable from OMC-R V18.0 P&C1 release

1.3. PRELIMINARIES FOR ALL UPGRADES This operation deals with deliveries. At this phase, unused deliveries can be deleted and all necessary new deliveries are installed on MD. Delivery configuration files are created to be used by upgrade procedures later on. For more information, see 4.

1.4. BSC UPGRADE This NRP performs e3 BSC upgrade. The whole upgrade process is split into three main phases:

1. New BSC EFT downloading from the MD to the BSC. 2. BSC software activation and tracking the software activation process. 3. On the operators demand, the third step is available: automatic fallback to the initial

software version and tracking the software fallback process. Several options are linked to the procedure and should be taken into account during BSC upgrade; they are: BSC Counter List, BSC DataConfig, Circuit Group Block. For more information, see 5.


Nortel confidential


Note: It is possible to upgrade the software of up to ten BSCs in parallel.

1.4.1 BSC COUNTER LIST The BSC counter list file is required by the BSC upgrade procedure. This file must take into account any new BSC Counter List in case of version/edition upgrade of a BSC. In case of patch upgrade application, the counters may be updated or not. The following choices are provided:

The counters are not updated: -FPATCH option must be chosen which does not update the bscCounterList;

The counters are updated and the default BSC Counter List file should be used: -FD option must be chosen;

The counters are updated, and the customized BSC Counter List file should be used: -F option must be chosen, where is the name of the customized BSC counter list file (with its complete path).

In case of upgrade (that is not a patch upgrade), it is recommended to use -FD or -F on the upgrade tool. It makes the counters be deleted and recreated by reset/build of the BSC during the upgrade. The -FPATCH, that does not update the BSC Counter List and that does not require reset/build of the BSC, is also authorized in this case of upgrade; it assumes, that these counters will be updated later. It should be checked before upgrade, that Vn and Vn+1 BSC counter list files are available. NOTE: Default or customized counter list application requires reset, then build during the upgrade.

1.4.2 BSC DATACONFIG MODIFICATION Several modes of BSC upgrade imply BDA build. In order to avoid additional downtime after the upgrade, there is a pause in the BSC upgrade tool which allows BSC DataConfig modification while the BDA is not built. If the BSC DataConfig is changed during the upgrade and if the automatic fallback is chosen, the modified data may be restored during the fallback.

1.4.3 CONTEXT OF CIRCUIT GROUP BLOCK The procedure provides an ability to perform Circuit Group Block update during BSC upgrade. NOTE: If the Circuit Group Block is updated, then the reset and build on-line will be performed during the upgrade.

1.5. TCU UPGRADE This NRP performs e3 TCU upgrade. Depending on TCU architecture, different actions are done during upgrade execution.

1.5.1 TCU E3 UPGRADE TCU e3 upgrade is performed in three phases:


Nortel confidential


1. New TCU EFT downloading from the MD to the BSC. 2. TCU software activation and tracking the software activation process. 3. On the operators demand, automatic fallback to the initial software version and

tracking the software fallback process. Depending on the TCU software, two types of TCU e3 upgrade are possible: off-line upgrade (upgrade with TCU restart) and on-line upgrade (upgrade without TCU restart). The first one leads to short downtime, while the second one does not lead to service interruption. For more information, see 8.1.

1.6. BTS UPGRADE WITHOUT BACKGROUND DOWNLOADING BTS upgrade without background downloading is performed in four steps:

1. UNIX shells and MMI command files are generated. 2. All necessary EFTs are downloaded to the BSC. 3. Software is activated. At this step, the impacted equipment is locked, then

ActivateNewVersion is performed, then the object is unlocked. When an object becomes unlocked, new software downloading from the BSC begins. After that, the entity restarts with new software. Thus, the time when the object is out of service is the sum of downloading and restart times.

4. If required, software fallback is executed. It is possible to manage how TRXs are brought into service:

All TRXs are unlocked one after another. One TRX (one RM in case of GSM/UMTS combo BTS, BTS18000, BTS6000,

BTS9000) per each cell is unlocked first and then the rest of TRXs are unlocked. The possibility to unlock one TRX per cell allows restoring network coverage more quickly. The drawback of this method is decreased traffic capacity until all TRXs are unlocked. For more information, see 7.

1.7. BTS UPGRADE WITH BACKGROUND DOWNLOADING BTS background downloading consists in loading the BTS software from the BSC to the BTS while the BTS is in service. This decreases downtime duration to the time required for BTS restart. It is possible to upgrade IPM in the same time. The following main phases represent this type of BTS upgrade:

1. New BTS EFT downloading from the MD to the BSC and new IPM EFT downloading from the IBOS to the IPM (if needed). BTS background downloading. Configuration file creation for the fallback purpose. This phase is not service impacting and may be done in advance.

2. Activation of the software previously downloaded in the background. Impacted objects restart with the new software; therefore this phase must be done during the maintenance window.

3. If necessary, fallback to the initial software version. It is possible to perform background downloading with immediate activation. In this case the BTS restarts automatically when downloading finishes. IPM software activation performed during BTS restart phase. BSC DataConfig parameter "centralized BTS downloading inhibition" (label 51) should be set to 0 in order to allow background downloading.


Nortel confidential


It may occur that background downloading of some sites should be restarted. It is necessary in two following cases:

BSC restart. In this case the BSC is unable to continue background downloading and the tool launches downloading of all impacted sites again after BSC restart;

TMU serving a group of sites is unable to process background downloading. In this case the tool waits for all sites downloading termination and then restarts downloading of the sites whose processing has failed.

In both cases, if the immediate activation mode is not used, three attempts to perform background downloading are taken. If the immediate activation mode is used, offline downloading of new software is performed, so there is no need to re-launch background downloading.

For more information, see 6.


Nortel confidential


1.8. BTS UPGRADE PROCEDURES COMPARED The table below compares main points of different types of BTS upgrade methods.

Procedure Method Advantages Disadvantages TRX management

BTS upgrade by background downloading

Background downloading

The downtime is minimal

The download time is maximum Not available

BTS upgrade without background downloading

MMI command files

Low service impact

Long duration of command files execution

Available


Nortel confidential


2. RELATED DOCUMENTS

2.1. APPLICABLE DOCUMENTS [A1] DS/BSS/DPL/0003 Operational index list [A2] PE/BSS/DJD/0xxx BSS Vxx Release Definition [A3] DS/BSS/APP/0001 BSS Maintenance checks from OMC-R [A4] 0000003-24-9476 Univity GSM BSC e3 & TCU e3 Commissioning Method

2.2. REFERENCE DOCUMENTS [R1] 411-9001-034 Nortel GSM BSS Configuration Operating Procedures

[R2] PE/SYS/DD/014492 BSC/TCU e3 GET DATA enhancement for IN and TCU (RFF 29718) [R3] Bulletin 591 BSCe3/TCUe3 upgrade pre-check [R4] DS/OMC/APP/000016 OMC-R Preventive Maintenance Backup [R5] DS/OMC/APP/000017 OMC-R System Global Restoration


Nortel confidential


3. GENERAL DESCRIPTION

3.1. READ CAREFULLY Before executing this procedure, ask your support for any special actions (workaround, patch...) to perform before and after the procedure.

3.2. PREREQUISITES All prerequisites and supplies are described in document [A1]. They must be checked long time before the upgrade day. For all hardware and software references, please refer to the following documents: see RELEASE DEFINITION [A2]. In order to detect potential hardware issues as quickly as possible, the operator should execute the upgrade pre-checks twice (for more information see [R3]): - The first time, several days before the upgrade in order to anticipate potential hardware

or network issues which can not be solve quickly.

- the second time, several hours before the beginning of the upgrade in order to be sure that the conditions of the upgrade are still correct.

Warning: Unexpected errors may occur in case of parallel execution of this procedure with any other NRP plug-in on the same equipment.

3.3. IMPORTANT NOTES

3.3.1 THE ORDER OF UPGRADE The OMCR must be successfully upgraded to V18 P&C1 before executing this procedure. In case of unitary upgrade with BSC e3 and/or TCU e3 the upgrade must be performed in the following order:

1. Upgrade of BSC e3 (see 5). 2. Upgrade of TCU e3 (see 8.1).

Note: It is impossible to launch BSC upgrade and BTS with background downloading on the same BSC simultaneously.

3.3.2 BTS SOFTWARE DOWNLOADING Only one software with a unique s/w trigram can be downloaded to the BSC at the same time. As a result, BTS (BTSSM and/or TRX) software with equal trigrams (but different full software names) must be upgraded to a unique software version. If the upgrade implies several new


Nortel confidential


software versions with equal trigrams then it must be done by several campaigns, one per version.

3.3.3 SYNCHRONIZATION In case of BTS upgrade without background downloading, if the synchronization feature is activated on involved BTSs and if master and slave ones are not upgraded at the same time, the slave BTS will be out of service twice: while the master reset and during its own downloading.

3.3.4 CALL DROP ANALYSIS In case when the BSC is upgraded and the call drop analysis feature is activated on BTSs under the BSC, it is recommended to deactivate this feature before upgrade. It can be done by setting the callDropActivation parameter of the corresponding BTS objects to Disabled.

3.3.5 INTERFERENCE MATRIX Upgrade of BSC, BTS Site Manager and TRX is forbidden if the interference matrix is running. There is a step in the preparation phase of every procedure (except 8.1 TCU e3 upgrade) concerning BSC e3 which consists in checking that the interference matrix is not running on the impacted BSS.

3.3.6 SOFTWARE VERSIONS COMPATIBILITY Software versions compatibility rules do not allow the sub-object to have its version higher than the version of its parent object. During the BTS upgrade with the use of any method described above, it may occur that the target version of TRX becomes greater than the target version of BTS site manager. In this case, the following options are possible: either to continue the procedure execution and to upgrade only the objects, whose target versions do not break compatibility rules, or to cancel the procedure execution and to change delivery configuration files. BTS upgrade tools display a corresponding message if such a situation takes place. Note: It is not possible to upgrade a BTS Site Manager in Vn and to leave the TRX (DRX or RM) in Vn-1.

3.4. HUMAN RESOURCES Depending on the operation, one or two OMC-R site operators are necessary.

3.5. OMC-R ACCESS The OMC-R site operator performing the upgrade should have:

The password of the UNIX omc user. The password of the OMC-R administrator account with full access to the OMC-R.


Nortel confidential


Note: If there is a need of execution on OMC-R of command files generated by the tool(s), it is necessary to log on to the OMC-R under the oam user.


Nortel confidential


4. PRELIMINARIES FOR ALL UPGRADES This operation must be performed before any upgrade described in this document and is executed only once for all upgrades. It should be done at least one day before the upgrade day. In case of version system upgrade, this procedure should be carried out after the OMC-R upgrade. To prepare these preliminaries, there is a step which lists the DELIVERY. It is useful to prepare the next upgrade and to download all necessary new DELIVERY in advance. Such case should be useful when BSC 3G and TCU 3G are not available (e.g.using a gigatape).

4.1. PRELIMINARIES SEQUENCE TABLE

Step | Operation description (Total 7 + ? mn) mn Sheet

page OK / NOK

NOK step

Input Parameters PREPARATION OF PRELIMINARIES

S1 How to ...

5 57 No

S2 List the DELIVERY to be upgraded

1 96 No

list = YES

END OF THE PREPARATION OF PRELIMINARIES BEGINNING OF PRELIMINARIES

S3 Check EFT

? 116 No

S4 Delete useless DELIVERY/executableSoftwareObjects

? 109 No

S5 Select and download the DELIVERY to the OMC-R

? 96 No list = NO

S6 If needed purge oam user files

1 107 No

END OF PRELIMINARIES


Nortel confidential


5. E3 BSC UPGRADE

Main phases and key moments of the upgrade: 1. The initial state of the BSS to be upgraded is verified. BSC backup is performed. 2. The new BSC software is copied onto the OMC-R and downloaded to the BSC. 3. The new software is activated. 4. The final state of the BSC is checked. Any problems detected may lead to the use of

the fallback procedure in order to return to the previous software.

5.1. REQUIREMENTS UPGRADE CHECK of BSS Maintenance checks from OMC-R [A3] must be finished at least one day before upgrade operations.


Nortel confidential


5.2. E3 BSC UPGRADE SEQUENCE TABLE


page OK / NOK

NOK steps

Input Parameters

ALL PREREQUISITES HAVE BEEN CHECKED PREPARATION FOR UPGRADE

S1 Check the alarms

5 64 F15 bscList = the list of the BSC numbers to process

S2 Check that Interference Matrix is not running on the BSC

5 111 F15

objId = every BSC number on the bscList

S3 If the impacted BSC version is V17 or higher, and the new BSC version is less than V17, check that no adjacentCellUTRAN objects exist under any bts

5 118 F15

bscId = every BSC number on the bscList

S4 If the impacted BSC architecture is e3optical_ip or e3electrical_ip and version is V18.0_PC1.2.0 or higher, and the new BSC version is less than V18.0_PC1.2.0, check that no Smlc pcmCircuit objects exist under the BSC

5 128

F15


S5 Check PCM links state

5 122 F15


S6 Display the BSC state

2 59 F15

bscList = the list of the BSC numbers to process param = M S

S7 Audit the BDA

15 61 F15

bscList = the list of the BSC numbers to process

S8 Perform upgrade pre-checks

15* [R3] F15

S9 Perform OMC-R environment data archiving according to OMC-R Preventive Maintenance Backup procedure

15 [R4] F15

S10 Back up each impacted BSC

? 68 F15 actionType = backup

bscList =the list of the BSC numbers to process

S11 If needed (see 1.4.3 Context of Circuit Group Block), update the Circuit Group Block

2 105 F15

bscList = the list of the BSC numbers to process param = ON


Nortel confidential


S12 Download the BSC DELIVERY to the BSC

150 113 F15


END OF PREPARATION FOR UPGRADE

THE BSC IS READY TO BE UPGRADED BEGINNING OF THE MAINTENANCE WINDOW

S13 Upgrade the BSC

? 70 F1 bscList = the list of the BSC numbers to process

bscCounterList = (see 1.4.1 BSC Counter List) param = Y [CGB :if the circuit group block has been previously updated ]

S14 Check the alarms

5 64 No


S15 Check PCM links state

5 122 No


S16 Audit the BDA

15 61 No


S17 Finish with the BSC upgrade tool (accept or fall back)

10 70 F1


THE 2 NEXT STEPS ARE PERFORMED ONLY IF RETURNING TO THE PREVIOUS SOFTWARE VERSION IS CHOSEN IN THE PREVIOUS STEP AND THE OLD BSC COUNTER LIST HAS TO BE RESTORED

S18 Restore impacted BSCs

? 68 No actionType = restore


S19 Rebuild the BDA on impacted BSCs

30 62 No

ModeLine = On-line commanded bscList = the list of the BSC numbers to process

THE BSC IS VALIDATED

S20 If upgrade type=4 or 7 with BDA building or upgrade type = 6, if the SMS-CB service has been used and if there has been a broadcasting message before the upgrade: Restart the SMS-CB service

2 66 No



15 [R4] No


1 107 No

THE UPGRADE IS SUCCESSFULLY COMPLETED * - total time of step execution depends on the BSC/TCU configuration.


Nortel confidential


5.3. FILES GENERATED BY THE UPGRADE TOOL

5.3.1 SHELL FILE: None

5.3.2 COMMAND FILE: None

5.3.3 LOG FILE: The "ds_remoteBscUpgrade.sh" tool generates the following log file: /var/local/oam/bscNumber.ds_remoteBscUpgrade.log This log file has to be checked if problems occur.

5.4. FALLBACK AFTER UPGRADE COMPLETION After a successful upgrade, you may find something wrong in your system and want to return to the previous version. You can do this by executing again this procedure from the beginning, but with oldDELIVERY instead of newDELIVERY (e.g. the BSC upgrade with oldDELIVERY).

NOTE: If any other operation has been performed on the BSC after the upgrade (e.g. activation of a new feature), it is mandatory to undo it before downgrading.


Nortel confidential


5.5. E3 BSC FALLBACK SEQUENCE TABLE

Fallback Operation description (Total 168 + ? mn) mn Sheet

page OK / NOK

NOK step

Input Parameters

AN UNEXPLAINED PROBLEM DURING THE UPGRADE CONCERNING E3 BSC

F1 If the fallback with the TML has been done, reset the BSC software

? 108 No bscList = the list of the BSC numbers to process

F2 If previously updated, fall back the circuit Group Block


param = OFF

F3 Rebuild the BDA on the impacted BSCs

30 62 No


F4 Audit the BDA

15 61 F5


IF ANY OF THE STEPS (F1-F4) IS NOT OK : F5 Return to the previous version and build


F6 Audit the BDA

15 61 F7


IF ANY OF THE STEPS (F5-F6) IS NOT OK : F7 Restore impacted BSCs

? 68 No actionType = restore


F8 Audit the BDA

15 61 F9


IF ANY OF THE STEPS (F7-F8) IS NOT OK : F9 Rebuild the BDA on impacted BSCs

30 62 No


F10 Audit the BDA

15 61 F11

BscList = the list of the BSC numbers to process


Nortel confidential


IF ANY OF THE STEPS (F9-F10) IS NOT OK : F11 Perform server databases reinstallation & environment data

restoration according to OMC-R System Global Restoration procedure (all BSC upgrades will be lost)

? [R5] No

F12 Rebuild the BDA on impacted BSCs

30 62 No

modeLine = On-line commanded bscList = the list of the BSC numbers to process

F13 Audit the BDA

15 61 No


THE BSC IS SUCCESSFULLY RESTORED

F14 If upgrade type=4 or 7 with BDA building or upgrade type = 6, if the SMS-CB service has been used and if there has been a broadcasting message before the upgrade: Restart the SMS-CB service

2 66 No


F15 If needed purge oam user files

1 107 No

THE FALLBACK IS SUCCESSFULLY COMPLETED


Nortel confidential


6. BTS UPGRADE WITH BACKGROUND DOWNLOADING

This paragraph describes the procedure of the BTS (BCF and/or TRX, IPM) software upgrade using background downloading from V16 to any recent system versions. It may be applied to the BTS supporting the centralized downloading protocol. Only the BTS and transceiver equipment software can be downloaded in the background.

6.1. REQUIREMENTS During background downloading, it is possible to check the detailed or summary status or abort background downloading in another terminal window. Refer to the sheet BTS UPGRADE WITH BACKGROUND DOWNLOADING to use these actions.

BTS background downloading is forbidden in the following cases:

The software previously downloaded in the background is not activated. Background activation or abort must be performed first in this case.

The previous attempt to perform background downloading has failed (due to equipment failure or OMC-R restart). Background abort must be performed first in this case.

BSC DataConfig parameter "centralized BTS downloading inhibition" (label 51) should be set to 0 in order to allow background downloading.

Fallback is performed with the offline software change (with Lock/Unlock). This leads to the loss of service.

The fallback configuration file stores all necessary information to return impacted objects to their initial software version. All information corresponding to a particular site and its TRXs is rewritten every time any object is downloaded onto the site. Therefore, it is recommended to perform the fallback correctly, to upgrade all necessary objects of the site at once. Note: Information about IPM upgrade status will be printed only after background download tool finishing. For online control of IPM upgrade process use log file: /var/local/oam/bscNumber.ds_activateIPM.YYYYMMDDHHMM.log


Nortel confidential


6.2. BTS UPGRADE BY BACKGROUND DOWNLOADING WITHOUT THE IMMEDIATE ACTIVATION SEQUENCE TABLE

This sequence table is for background downloading without immediate activation.

Step | Operation description (Total 99+ ? mn) mn Sheet

page OK / NOK

NOK step

Input Parameters

ALL PREREQUISITES ARE CHECKED PREPARATION FOR UPGRADE

S1 Check the alarms

5 64 No



5 111 No


S3 Audit the BDA

15 61 No



15 [R4] No


? 68 No actionType = backup


S6 Check that no background downloading action is in progress


btsSMList = the list of the btsSM Ids to process Action = SL

S7 Perform BTS software background downloading


btsSMList = the list of the btsSM Ids to process TypeList = the list of the equipment types to upgrade Action = D


BTS ARE READY TO BE UPGRADED BEGINNING OF THE MAINTENANCE WINDOW

S8 Perform background activation


btsSMList = the list of the btsSM Ids to process Action = R

THE BTS ARE UPGRADED S9 Audit the BDA

15 61 F1



Nortel confidential


S10 Check the alarms

5 64 F1



15 [R4] No


1 107 No

THE UPGRADE IS SUCCESSFULLY COMPLETED


Nortel confidential


6.3. BTS UPGRADE BY BACKGROUND DOWNLOADING WITH THE IMMEDIATE ACTIVATION SEQUENCE TABLE

This sequence table is for background downloading with immediate activation.

Step | Operation description (Total 76+ ? mn) mn Sheet

page OK / NOK

NOK step

Input Parameters


S1 Check the alarms

5 64 No



5 111 No


S3 Audit the BDA

15 61 No



15 [R4] No




S6 Check that no background downloading action is in progress


btsSMList = the list of the btsSM Ids to process Action = SL


BTS ARE READY TO BE UPGRADED BEGINNING OF THE MAINTENANCE WINDOW

S7 Perform BTS software background downloading and activation


btsSMList = the list of the btsSM Ids to process TypeList = the list of the equipment types to upgrade Action = DA

THE BTS ARE UPGRADED S8 Audit the BDA

15 61 F1


S9 Check the alarms

5 64 F1



15 [R4] No


1 107 No


Nortel confidential




6.4.1 SHELL FILES: None

6.4.2 COMMAND FILES: The "ds_bkgdUpgBts.sh" tool generates the following command files (located in the /OMC/cmdFile/root/oam/ds_bkgdUpgBts/ directory): 1. bscNumber.DownloadToBsc.cmd

This command file downloads all the necessary software to the BSC.

2. bscNumber.Fallback.cmd

This command file returns transceiverEquipments and btsSiteManagers to their previous software version if a problem occurs during the upgrade operation.

3. bscNumber.IPM_Fallback.cmd

This command file returns IPM to its previous software version if a problem occurs during the upgrade operation.

The generated command files are launched by the tool automatically; there is no need to launch these files manually.

6.4.3 LOG FILE: The "ds_bkgdUpgBts.sh" tool generates the following log file: /var/local/oam/bscNumber.ds_bkgdUpgBts.YYYYMMDDHHMM.log This log file has to be checked if problems occur. In case of BTS and IPM upgrade the following log file is generated for track IPM activation: /var/local/oam/bscNumber.ds_activateIPM.YYYYMMDDHHMM.log

6.4.4 CONFIGURATION FILE: The "ds_bkgdUpgBts.sh" tool generates the following configuration file: /usr/local/oam/config/bscNumber.ds_bkgdUpgBts.cfg This configuration file is used by the tool to perform fallback.


Nortel confidential


6.5. FALLBACK AFTER UPGRADE COMPLETION After a successful upgrade, you may find something wrong in your system and want to return to the previous version. You can do this by executing again this procedure from the beginning, but with oldDELIVERY instead of newDELIVERY (e.g. the BTS upgrade with background downloading with oldDELIVERY).

NOTE: If any other operation has been performed on the BTS after the upgrade (e.g. activation of a new feature), it is mandatory to undo it before downgrading.


Nortel confidential


6.6. BTS BACKGROUND DOWNLOADING FALLBACK SEQUENCE TABLE

Fallback Operation description (Total 108+ ? mn) mn Sheet

page OK / NOK

NOK step

Input Parameters

AN UNEXPLAINED PROBLEM DURING THE UPGRADE

F1 If background downloading has not finished yet or if the software downloaded in the background has not been activated, perform abort of background downloading

87 No

bscList = the list of the BSC numbers to process btsSMList = the list of the btsSM Ids to process Action = A

F2 Fallback to the previous BTS (with/without IPM) software version


btsSMList = the list of the btsSM Ids to process Action = FB

F3 Audit the BDA

15 61 F4



2 68 F6 bscList = the list of the BSC numbers to process

F5 Audit the BDA

15 61 F6


IF ANY OF THE STEPS (F4-F5) IS NOT OK : F6 Rebuild the BDA on impacted BSCs

15 62 F8 modeLine = On-line commanded


F7 Audit the BDA

15 61 F8



Nortel confidential




? [R5] No

F9 Rebuild the BDA on impacted BSCs

30 62 No


F10 Audit the BDA

15 61 No


THE FALLBACK IS SUCCESSFULLY COMPLETED F11 If needed purge oam user files

1 107 No


Nortel confidential


7. BTS UPGRADE WITHOUT BACKGROUND DOWNLOADING

This paragraph describes the procedure for upgrading BTS software (BCF and TRX objects) to V16, V17 or V18 system version. It may be used to upgrade a single BTS or all BTS of a BSC or several BSC. In case of version system upgrade, this procedure must be carried out after OMC-R, BSC and TCU e3 upgrades.

7.1. UPGRADE METHODS

The main constraint for the BTS upgrade without background downloading is the limited capacity of BSC for downloading simultaneously software to equipment (BCF, TRX). Thus, choices have to be made by the operator when performing BTS upgrade, considering the 2 criteria:

The network coverage impact. The traffic capacity impact.

Two methods are available for BTS upgrade without background downloading: Unitary BTS upgrade (one site). Global BTS upgrade (all sites).

o With operators confirmation between consecutive site upgrades. o Without operators confirmation between consecutive site upgrades.

For all BTS upgrade methods (one or all sites), 2 choices are possible: All TRXs are upgraded in parallel. One TRX (RM in case of GSM/UMTS combo BTS, BTS18000, BTS6000, BTS9000)

per cell is upgraded first.


Nortel confidential


7.2. THE INTERFACE OF THE BTS UPGRADE TOOL When the upgrade tool is executed, several choices can be made according to the need of upgrading and the importance of the service interruption impact. In order to help the operator to choose the best tool option, the diagram below (fig.1) sums up the different possibilities.

(A)

Just one site upgrade ?

(n)o without confirmation

(y)es with confirmation

(a)ll TRXs

One site with

increased service impact

Unlock the first TRX

(RM)?

One site with

reduced service impact

(t)he first TRX (RM) (t)he first TRX (RM)

Site by site with

increased service impact

Unlock the first TRX (RM)

Site by site with

reduced service impact

(a)ll TRXs

The network

with increased

service impact

Unlock the first TRX (RM)

The network

with reduced service impact

(t)he first TRX (RM) (a)ll TRXs

(o)ne site upgrade

Operators confirm.

before each site

upgrade ?

(F) (E) (D) (C) (B)

(a)ll sites all sites of the same (t)ype

upgrade


Nortel confidential


Figure 1

Next site upgrade

(cases E,F)

Operator confirmation before upgrading the rest of TRXs

(cases B,D,F)

Operator confirmation before site upgrade

(cases E,F)

Operator confirmation to continue (all cases)

Upgrade of the rest of TRXs (cases B,D,F)

One site upgrade (cases A,B,E,F)

All sites upgrade (cases C,D)

Software download (all cases)


Nortel confidential


7.3. BTS UPGRADE WITHOUT BACKGROUND DOWNLOADING SEQUENCE TABLE


page OK / NOK

NOK step

Input Parameters


S1 Check the alarms

5 64 No bscList = the list of the BSC numbers to process


5 111 No


S3 Audit the BDA

15 61 No



15 [R4] No




S6 Create upgrade tools


phase = 1

FROM NOW ON, YOU MUST NOT CHANGE THE ADMINISTRATION STATE OF ANY EQUIPMENT OR YOU MUST START AGAIN FROM THE BEGINNING

S7 Download the BTS software to the BSC


phase = 2

PREPARATION FOR UPGRADE

THE BTS ARE READY TO BE UPGRADED - BEGINNING OF THE MAINTENANCE WINDOW -

S8 Activate the software new version

? 81 F1 to F3

BscList = the list of the BSC numbers to process phase = 3

S9 Audit the BDA

15 61 F1 to F3


THE BTS ARE UPGRADED S10 Check the alarms

5 64 F1 to F3



Nortel confidential



15 [R4] No


1 107 No



7.4.1 SHELL FILES: The "ds_btsUpgrade.sh" tool generates the 2 following shell files: /home/omc/oam/bscNumber.btsUpgradeDL.sh Depending on the options this shell executes some of these files: "downloadbts_bscNumber_btsSiteManagerNumber_download.cmd", "downloadbts_bscNumber_btsSiteManagerNumber_set.cmd" and "downloadtrx_bscNumber_btsSiteManagerNumber_all.cmd" to download the software for all equipment to the BSC. /home/omc/oam/bscNumber.btsUpgrade.sh This shell executes all "site_bscNumber_btsSiteManagerNumber.cmd" (and "rest_trx_bscNumber_(btsSiteManagerNumber or all).cmd, if any)" files to upgrade BTS.

7.4.2 COMMAND FILES: The "ds_btsUpgrade.sh" tool also generates the following command files (located in the /OMC/cmdFile/root/oam directory): 1. downloadbts_bscNumber_btsSiteManagerNumber_download.cmd

downloadbts_bscNumber_btsSiteManagerNumber_set.cmd

downloadtrx_bscNumber_btsSiteManagerNumber_all.cmd

These command files download the software for all equipment to the BSC.

2. site_bscNumber_btsSiteManagerNumber.cmd

This command file executes the following:

5. performs the soft shutdown of relevant cells; 6. waits for the " waiting time" of the question "Enter the waiting time for the soft

shutdown period included between 10 and 600 (in seconds) or 0 second for no soft shutdown:";

7. activates a new software version either on the transceiverEquipment (TRX), the btsSiteManager (BCF) or both objects;

8. restores cells to their original state before the shutdown is performed. 3. rest_trx_bscNumber_(btsSiteManagerNumber or all).cmd This command file downloads and activates a new software version on the rest of the transceiverEquipment (TRX) objects in case if only the first TRX of each cell (all TRXs of one RM for each cell, if the BTS is GSM/UMTS combo BTS, BTS18000, BTS6000, BTS9000) has been already upgraded; e.g. you have answered t to Question 6: "When putting the site back into service, do you want to unlock (t)he first TRX/cell, or (a)ll the TRXs ?"


Nortel confidential


4. fallbacksite_bscNumber_btsSiteManagerNumber.cmd

This command file returns the transceiverEquipment, the btsSiteManager or both objects to their previous software version if a problem occurs during the upgrade operation.

7.4.3 LOG FILE: The "ds_btsUpgrade.sh" tool also generates the following log file: /var/local/oam/bscNumber.ds_btsUpgrade.log This log file has to be checked if problems occur.

7.5. FALLBACK AFTER UPGRADE COMPLETION After a successful upgrade, you may find something wrong in your system and want to return to the previous version. You can do this by executing again this procedure from the beginning, but with oldDELIVERY instead of newDELIVERY (e.g. the BTS upgrade with oldDELIVERY). NOTE: If any other operation has been performed on the BTS after the upgrade (e.g. activation of a new feature), it is mandatory to undo it before downgrading.


Nortel confidential


7.6. BTS UPGRADE WITHOUT BACKGROUND DOWNLOADING FALLBACK SEQUENCE TABLE


page OK / NOK

NOK step

Input Parameters

AN UNEXPLAINED PROBLEM DURING THE UPGRADE

F1 Fallback to the previous BTS software version


btsList = the list of the BTS numbers to fall back

F2 Audit the BDA

15 61 F3




F4 Audit the BDA

15 61 F5


IF ANY OF THE STEPS (F3-F4) IS NOT OK : F5 Rebuild the BDA

15 62 No modeLine = On-line commanded


F6 Audit the BDA

15 61 No



1 107 No



Nortel confidential


8. E3 TCU UPGRADE

8.1. E3 TCU UPGRADE SEQUENCE TABLE


page OK / NOK

NOK step

Input Parameters


S1 Check the alarms


S2 Audit the BDA

5 61 No


S3 Perform upgrade pre-checks

15* [R3] No


15 [R4] No


? 68 No

actionType = backup bscList =the list of the BSC numbers to process


S6 Download and/or declare new TCU software on the TCU

? 92 8.4 bscList = the list of the BSC numbers to process

param = -E


THE TCU ARE READY TO BE UPGRADED - BEGINNING OF THE MAINTENANCE WINDOW -

S7 Activate the software new version

? 92 8.4 bscList = the list of the BSC numbers to process

param = -Y

S8 Audit the BDA

15 61 8.4 bscList = the list of the BSC numbers to process

THE TCU ARE UPGRADED

S9 Check the alarms

5 64 8.4 bscList = the list of the BSC numbers to process


Nortel confidential



15 [R4] No

S11 If needed, purge oam user files

1 107 No

THE UPGRADE IS SUCCESSFULLY COMPLETED * - total time of step execution depends on the BSC/TCU configuration.


Nortel confidential



8.2.1 E3 LOG FILE: The "ds_tcuUpgrade.sh" tool also generates the following log file:

See /var/local/oam/bsc.tcu.ds_tcuE3Upgrade.log for details.

This log file has to be checked if problems occur.

8.3. FALLBACK AFTER UPGRADE COMPLETION After a successful upgrade, you may find something wrong in your system and want to return to the previous version. You can do this by executing again this procedure from the beginning, but with oldDELIVERY instead of newDELIVERY (e.g. E3 TCU upgrade with oldDELIVERY). NOTE: If any other operation has been performed on the TCU after the upgrade (e.g. activation of a new feature), it is mandatory to undo it before downgrading.

8.4. E3 TCU FALLBACK There is a number of situations which may require a more detailed analysis in order to ensure that most affective and less impacting actions are performed to either complete the upgrade on a Unitary basis, or to Fallback the entire TCU. To ensure that the most appropriate actions are performed the operator is recommended depending on the impact to contact either ER or a local TAS organization.


Nortel confidential


9. IPM UPGRADE This paragraph describes the procedure for upgrading IPM software separately from BTS. It may be used to upgrade a single IPM or all IPM of a BSC. In case of version system upgrade, this procedure must be carried out after OMC-R and BSC upgrades.


page OK / NOK

NOK step

Input Parameters


S1 Check the alarms

5 64 No



5 111 No


S3 Audit the BDA

15 61 No



15 [R4] No





S6 Execute IPM upgrade

? 126 F1 bscId = the BSC number numbers to process

ipmList = the list of the IPM numbers to process

S7 Audit the BDA

15 61 F1 to F3


THE IPM ARE UPGRADED S8 Check the alarms

5 64 F1 to F3



15 [R4] No


1 107 No



Nortel confidential



9.1.1 LOG FILE: The ds_upgradeIPM.tcl" tool also generates the following log file: /var/local/oam/bscNumber.ds_upgradeIPM.YYYYMMDDHHMM.log This log file has to be checked if problems occur.


Nortel confidential


9.2. FALLBACK AFTER UPGRADE COMPLETION After a successful upgrade, you may find something wrong in your system and want to return to the previous version. You can do this by executing the steps described below.


page OK / NOK

NOK step

Input Parameters

THE NEW SOFTWARE HAS BEEN ACTIVATED

F1 Fallback to the previous IPM software version

? 126 No bscId = the BSC number numbers to process

ipmList = the list of the IPM numbers to process params = -FB

F2 Audit the BDA

15 61 F3




F4 Rebuild the BDA

15 62 No


F5 Audit the BDA

15 61 F6




? [R5] No

F7 Rebuild the BDA

15 62 No


F8 Audit the BDA

15 61 No



1 107 No



Nortel confidential


10. SHEETS The sheets of operations are presented not in the order of execution. Therefore, always refer to the sequence table of the operations to determine the sheet to execute and the values of its input parameters.

The sheets used in this specific procedure are also applicable to other procedures (other hardware configurations). Therefore, it is possible to find some conditional sections or sentences available only in other procedures.


Nortel confidential


HOW TO . . .

PRESENTATION The purpose of this sheet is to provide a detailed explanation of how you can perform some basic operations, which may become necessary as you go on through your procedure.

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation. The BSS is operational.

ACTIONS

) ON THE LOCAL OMC-R WORKSTATION:

O1. How to open an omc shell window on a workstation:

On the background menu:

SELECT Access to Terminal Console

Then, enter your username (omc, root ...) and password.

O2. How to remotely log on to the active server from a workstation:

O2.1. Open an omc shell window.

O2.2. Go to this window and remotely log on to the active server: Under omc login:

... (omc) % ssh actServerName

actServerName: hostname of the active server

O3. How to open a session log:

GOTO OMC-R Browser SET View = Logical SELECT Administration SELECT user session log...

O4. How to find the active server:

GOTO OMC-R Browser SET View = Logical SELECT_OBJ MD-R SELECT Objects - Display|Set

Locate the managerServer parameter. The value of this parameter is the hostname of the active server.


Nortel confidential


O5. How to open a notification window:

GOTO OMC-R Browser SET View = Logical SELECT Fault SELECT Notification monitor...

O6. How to change your working directory to the oam directory:

O6.1. Create the oam directory if not done yet during the previous steps. Under omc login:

... (omc) % mkdir /home/omc/oam

O6.2. Change the working directory to the oam directory. Under omc login:

... (omc) % cd /home/omc/oam

FINAL STATUS Now you know how to perform required basic operations.


Nortel confidential


DISPLAYING THE BSC STATE

PRESENTATION The purpose of this sheet is to describe how to display information on the BSC state.

INPUT PARAMETERS bscList The list of bscNumber to process. param The parameter to display specific information (-M | -S | -N).

If param = -M: The tool displays all prom markers. If param = -S: The tool displays the state of the remoteSsuState parameter. If param = -N: The tool does not display prom markers and the state of the remoteSsuState parameter.

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local machine. The BSS is operational. The bscMdInterface connected to BSC bscNumber is operational.

ACTIONS


1. If not done yet, log on to the OMC-R as the administrator user.

2. For each BSC the bscNumber of which is on bscList: {

Remotely log on to the active server if not done yet (see sheet How to...). } endfor

3. In parallel for each bscNumber on bscList: {

In the shell window dedicated to BSC bscNumber, execute the tool: Under omc login:

..(omc)% /usr/local/oam/bin/ds_displayBscConfiguration.sh -BbscNumber param

The tool displays BSC states and produces a log file. Generally, the most important information for a given context is displayed in the paragraph "INFORMATION SUMMARY".

} endfor

TROUBLESHOOTING See the log file:

/var/local/oam/bscNumber.ds_displayBscConfiguration.log.


Nortel confidential


FINAL STATUS The operational state of the BSC (chain information, software & prom markers...) is recorded.

The operational state of the BSC (chain information, software & prom markers...) is now recorded.


Nortel confidential


BDA AUDIT

PRESENTATION The purpose of this sheet is to provide a detailed explanation of how you can check reconciliation between BDE (OMC-R database) and BDA (BSC database).

INPUT PARAMETERS bscList The list of bscNumber to process

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation. The dedicated bscMdInterface object is operational on the BSC to process.

ACTIONS


1. If not done yet, log on to the OMC-R MMI as administrator.

2. For each BSC the bscNumber of which is on bscList: { Remotely log on to the active server if not done yet (see sheet How to...). } endfor

3. In parallel for each bscNumber on bscList: { In the shell window of BSC bscNumber run the audit tool:

Under omc login:

... (omc) % /usr/local/oam/bin/ds_auditBDA.sh -BbscNumber

The tool performs BDA audit and displays OK if no discrepancies are found, otherwise KO. This takes a while.

} endfor

TROUBLESHOOTING 1. See the log file: /var/local/oam/bscNumber.ds_auditBDA.log. 2. No data mismatch is acceptable. Revealed discrepancies require update.

FINAL STATUS The OMC-R database & BSC databases (BDE & BDA) are consistent.


Nortel confidential


BDA REBUILD

PRESENTATION The purpose of this sheet is to detail how you can rebuild BDA (BSC database).

INPUT PARAMETERS bscList The list of bscNumber to process. modeLine This parameter indicates the way we achieve BDA on-line reset. (On-line automatic | On-line commanded | Fallback)

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation.

ACTIONS



2. For each BSC the bscNumber of which is on bscList: { Remotely log on to the active server if not done yet (see sheet How to...). } endfor

3. In parallel for each bscNumber on bscList: { In the shell window dedicated to the BSC bscNumber,

3.1 Change the working directory to the oam directory (see sheet How to...). 3.2 Build the BDA.

3.2.1 If modeLine = On-line automatic: { Under omc login:

... (omc) % /usr/local/oam/bin/ds_buildBDAOnLine.sh -BbscNumber -A

This tool performs BDA on-line reset, builds and activates new BDA. Though, possibly out of the maintenance window at the beginning of tool execution, you may find yourself in the maintenance window at the end of BDA build. So this action is started a few minutes before the maintenance window begins.

SERVICE INTERRUPTION!!!

This takes a while. Continue with another BSC. } endif

3.2.2 If modeLine = On-line commanded: {


Nortel confidential


Under omc login:

... (omc) % /usr/local/oam/bin/ds_buildBDAOnLine.sh -BbscNumber -C

This tool resets BDA on-line and builds BDA. You may be out of the maintenance window during execution of this tool.

This takes a while. Continue with another BSC and come back into this window when the BDA is built to run the next tool. Under omc login:

... (omc) % /usr/local/oam/bin/ds_activateNewBDA.sh -BbscNumber

This tool activates the newly built BDA. So, this action must be performed inside the maintenance window.

SERVICE INTERRUPTION!!!


3.2.3 If modeLine = Fallback: { Under omc login:

... (omc)% /usr/local/oam/bin/ds_buildBDAOnLine.sh -BbscNumber -F A

This tool builds BDA and automatically activates new BDA.


} endfor

TROUBLESHOOTING 1. See the log file /var/local/oam/bscNumber.ds_buildBDAOnLine.log. 2. See the log file /var/local/oam/bscNumber.ds_activateNewBDA.log. 3. In case of trouble, investigate or perform fallback recovery.

FINAL STATUS The BDA is reset and built.


Nortel confidential


BSS ACTIVE ALARMS CHECK

PRESENTATION The purpose of this sheet is to provide a detailed explanation of how to check active alarms in BSS. Run the checks of this sheet periodically in order to detect pending alarms. Though a special objective of sheet operations is to verify if new alarms have appeared after the latest manipulations with network operation (upgrade, reconfiguration...). If this is true fallback recovery is necessary (only if fallback recovery is possible).

INPUT PARAMETERS bscList The list of bscNumber to process

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation. The dedicated bscMdInterface object is operational for the BSC to process.

ACTIONS

) ON THE LOCAL OMC-R WORKSTATION: 1. If not done yet, log on to the OMC-R MMI as administrator.

2. For each BSC the bscNumber of which is on bscList: Remotely log on to the active server if not done yet (see sheet How to...).


In the shell window dedicated to BSC bscNumber, run the alarms check tool: Under omc login:

... (omc) % /usr/local/oam/bin/ds_checkAlarm.sh -BbscNumber The tool performs the following tasks: Display the cumulated table of all alarms for the current BSS.

} endfor


Nortel confidential


TROUBLESHOOTING 1. See the log file: /var/local/oam/bscNumber.ds_checkAlarms.log for details

about alarms. 2. In case of Critical or Major active alarms investigate and fix the on-site equipment. 3. If new alarms appear after network operations (upgrade, reconfiguration...),

perform fallback recovery to neutralize the effects of the corresponding faulty equipment or operation (only if fallback recovery is possible).

4. If you face problems while performing troubleshooting, call TAS.

FINAL STATUS Remaining active alarms of the BSS are analyzed and saved in the log file.


Nortel confidential


RESTARTING SMS-CB SERVICE

PRESENTATION The purpose of this sheet is to describe how to restart SMS-CB service stopped by BDA building during a major network operation (BSC upgrade with site intervention, BSC remote version upgrade or BSC remote edition upgrade with BDA building).

WARNING: If you do not use SMS-CB service or if you have not got a broadcasting message during the upgrade operation, you should continue with the next step in the sequence table.

INPUT PARAMETERS bscList The list of BSC numbers to process.

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local machine. The BDA is built.

ACTIONS



2. For each BSC the bscNumber of which is on bscList: {

Remotely log on to the active server if not done yet (see sheet How to...). } endfor


In the shell window dedicated to BSC bscNumber,

3.1 Change the working directory to the oam directory (see sheet How to...).


Nortel confidential


3.2 Restart SMS-CB messages.

If BDA build has been run more than once: {

Under omc login:

... (omc) % /usr/local/oam/bin/ds_executeCmdFile.sh -Uadministrator -PadministratorPassword -F/root/sms_start_razGB_bscNumber.cmd.old

Else Under omc login:

... (omc) % /usr/local/oam/bin/ds_executeCmdFile.sh -Uadministrator -PadministratorPassword -F/root/sms_start_razGB_bscNumber.cmd

} endif

} endfor

TROUBLESHOOTING Check the owner and/or execution rights of the command file.

FINAL STATUS SMS-CB service is restarted.


Nortel confidential


BSC DATABASE BACKUP/RESTORATION

PRESENTATION This BSC per BSC Backup/Restoration provides a way to save and restore BDE data associated with a single BSC. Remember that the tool used here neither restores nor saves mdScanner, traceControl, callPathTrace objects and SMS-CB information. All the operations described here are performed on the command line of the UNIX OS. During BSC restoration configuration requests for the BSC are not allowed. In case of a

configuration request the system responds with the following error message "A request is already being processed for this BSC" displayed at the MMI level.

Restoration is possible only on the OMC-R where backup is done. Only one instance of the tool can run at a time.

INPUT PARAMETERS actionType The action option ( backup | restore ) bscList The list of bscNumber to process.

INITIAL STATUS An omc session is available on the active server. OMC-R tasks and the Sybase server application are active and running.

ACTIONS

) ON THE LOCAL OMC-R WORKSTATION: 1. If not done yet, log on to the OMC-R as the administrator.

2. If not done yet, remotely log on to the active server (see sheet How to...).


Nortel confidential


3. For each bscNumber on bscLi

Documents

Dsbssapp000010_17 05en_BSS Upgrade Procedure