Draft version 1/20

D900/D1800/D1900

Mobile Communication System

SYSTEM UPGRADE SBS

From BR7.0/70 to BR9.0/003

Draft version 2/20

Table of Contents

1. Scope................................................................................................................................................................... 32.General ................................................................................................................................................................. 4

2.1 Project ........................................................................................................................................................... 42.2 SW/FW/HW.................................................................................................................................................. 6

2.2.1 Changes .................................................................................................................................................. 62.2.2 To be ordered ......................................................................................................................................... 62.2.3 SW Overview Table ............................................................................................................................... 7

2.3 Hints related to the BR9.0/003 ...................................................................................................................... 82.3.1 New attribute must be st during the patch handling .................................... Erreur ! Signet non défini.2.3.2 Upgrade – Fallback procedure for BSC / BTSE..................................................................................... 82.3.3 Upgrade – Download of new BR9.0 SW TRAU.................................................................................... 8

2.4 Outage Time.................................................................................................................................................. 82.5 Manuals ......................................................................................................................................................... 8

2.5.1 Extra Manuals needed ............................................................................................................................ 82.5.2 Manual Delta .......................................................................................................................................... 8

2.6 Data Storage Media ....................................................................................................................................... 82.7 Aspects of Quality......................................................................................................................................... 9

3. Upgrade Procedure.............................................................................................................................................. 93.1 Prerequisites .................................................................................................................................................. 93.2 BR9.0 SW Import from CD-ROM to RC..................................................................................................... 9

3.2.1 Import BSC SW Load and BSC patches ................................................................................................ 93.2.2 Import BTSE SW Load ........................................................................................................................ 103.2.3 Import TRAU SW Load ....................................................................................................................... 10

3.3 Download SW from RC to BSC.................................................................................................................. 103.3.1 Download BSC SW Load..................................................................................................................... 103.3.2 Download BTSE SW Load .................................................................................................................. 113.3.3 Download TRAU SW Load ................................................................................................................. 11

3.4 Download SW from BSC to NEY............................................................................................................... 113.4.1 Download SW from BSC to BTSE ..................................................................................................... 113.4.2 Download SW from BSC to TRAU .................................................................................................... 11

3.5 Patch Handling ............................................................................................................................................ 123.6 DB conversion from BR7.0/70 to BR9.0/003 ............................................................................................. 13

3.6.1 Database conversion without Modification of SWLH of BTSE and TRAU ........................................ 133.6.2 Database conversion without Modification of SWLH of BTSE and TRAU ........................................ 15

3.7 BSS Upgrade ............................................................................................................................................... 163.7.1 Setting of BSC SW load as “NEW” one .............................................................................................. 163.7.3 Scanner Handling ................................................................................................................................. 163.7.4 BSC Initialisation ................................................................................................................................. 163.7.5 BTSE, TRAU SW Activation .............................................................................................................. 173.7.6 Scanner Handling after BSC Upgrade.................................................................................................. 18

4. Fallback............................................................................................................................................................. 184.1 BSS Downgrade .......................................................................................................................................... 184.2 BTSE Downgrade ....................................................................................................................................... 184.3 TRAU Downgrade ...................................................................................................................................... 19

5. Documentation .................................................................................................................................................. 196. Abbreviations .................................................................................................................................................... 20

Draft version 3/20

1. ScopeThis manual describes how to change the SW of the SBS BR7.0/70, documented in Release Discription SBSBR7.0/70 to SBS BSS BR9.0/003, Release Description SBS BR9.0/003. The upgrade is done via RC.Please note: the RC will require an extra manual..All expressions are explained in the last chapter and should be read before.

IMPORTANT NOTE FOR BR9.0

New Right-toUse License PolicyStarting from BR9.0 the general mechanism

- to enable/disable usage of each optional feature- to control the capacity of the SBS (both CS and PS)

is completely implemented in the BSC.

Within a System Upgrade done be RC / LMT / OTS, the offline process of DB file conversion consists of 3major steps:

(1) Database of BSC <BR9: conversion BINARY File via DBAEM tool to ASCII File.(2) Converting the ASCII File <BR9.0 with Licenses File via CONVFILE tool to ASCII FILE = BR9.0.(3) If all license key are available: DBAEM tool converts ASCII File BR9.0 to BINARY File BR9.0.

If minimum 1 license key is misseing:

BINARY FILE BR9.0 cannot be generated. >> Upgrade notperformed

Draft version 4/20

2.General

2.1 ProjectPlease take care of the Operator Hints and the Restriction List contained in the Release Description SBSBR9.0/003.

Operation Hint: OG700TRAU1 GE0003Titel: BSCI Reset cause.Description: If bsci board is equipped in a BSVCIV4 with a issue less than 7, the software activation must beperformed only if the BSMS standby copy is ENABLED or its power supply is turned off (if it exists) or it isextracted from the rack.

Operation Hint: OG700TRAUP GE0004Titel: TRAU Download impossible in „FORCED“ mode.Description:Because of lack of room into the TRAU (BSCI) mass storage it is only possible to download a newSW using the option that copies just the files different by the ones present in flash. Morever not all the TRAUexecutable files can be changed simultaneously; at least one executable file must be equal to the previous one.i.e.: from the BSC LMT the attribute “MODE” MUST BE “UNFORCED”. From the TRAU LMT the attribute“OVERWRITE” MUST BE “NO”. From RC the attribute “MODE” of the command NEDOWNLOAD for theTRAU must be “UNFORCED”.Also refer to Service Info BO 126 Problem with TRAU SW download.

Operation Hint: OG900TRAUP OM0001Titel: Upgrade TRAU SW to BR90.Description: In order to install the BR90 TRAU SW is mandatory that the running TRAU SW LOAD containsat least two (of four) processor files equal to new BR90 files. If this condition is not satisfied a TRAU BRIDGEload must be used. Also for downgrade from BR90 to BRxx the same rule is valid.

Operation Hint: OG800RC OM0018Titel: X25 Primary link failure recovery.Description: On a redundant link, when for an hardware problem the primary link becomes unavailable after areboot or during normal operations, you have to wait that the system resolves itself the failure with an automaticswitch, before manual intervention.If still operator wants to manually resolve the situation, care must be taken to avoid to put Olinks in ainconsistent state, follow this rule:

- first lock primary link- operate on secondary- delete and after failue resolution the original link- unlock the original primary which acts as secondary now

Operational Impact: Problem on primary link.

Operation Hint: OG800RC OM0019Titel: Problem on set OLINK.Description: If you want to change O-link port parameters (like port number and local address) you not onlyhave to lock the Olink, and apply needed SETs on port object, but also wait at least 30 seconds before unlockungthe O-link. The X.25 connection in fact is not ceased immediately after lock, but only after 30 seconds. If youchange port attribute and unlock before, the old parameters will be used instead of new ones, since theconnection is still the same as before.Change Olink parameters needs 30 second before is running.

Draft version 5/20

Operation Hint: OG700BSC OM0011Titel: BSC full init after running CLI from RC.Description: Due to the fact that LOCK command is immediately executed, the subsequent SET commandrequires a rework of the channel idle lists. Unfortunately, if the LOCKED channel is busy, the procedure torelease take more time than the LOCK+SET+UNLOCK, so that it causes a mismatch in the affected idle lists.No problem if the affected channel is idle in that moment. So, the unique way to avoid the problem (that is nosystematic but depends on channel usage during command execution) is to insert in the scipt a delay ( at least 5secs) between the LOCK and the SET commands.

Operation Hint: OG900RC OM0001Titel: Parallel download of the SW on BSSs.Description: When you perform the parallel SW download on the 84 BSSs someone fails soon and on the CLIwe have the message “Communication with the fileserver failed”, instead the other take a lot of time and itseems that the FTC server are hanged. If you perform the download of SW only on 10 BSSs each time, all worksvery well.

Draft version 6/20

2.2 SW/FW/HW

2.2.1 ChangesAs a minimum, the following changes occur; explanations see next chapter.

BSC SW,BTSE SW,TRAU SW,LMT SW,DBAEM SW

Only the version MPCCV9 and TDPCV9 are supported.SN16, PPLD and PPCC boards are no more supported; the High Capacity boards PPXX and SNAP have to beused.The admitted PPXXV1 issue for BR9.0 must be equal or greater than 16 or H7.The rack S30861-C14-X is no more supportedThe BS242 (picoBTS) is no more supported

2.2.2 To be orderedSW, BSS

BSC HB010080.SWL 2 CD-ROM / OMS

BSC Patches M1380A00, 01, 02, 03, 04, 06, 07, 09, 10, 11

TRAU Patches T1380000, 01, 02, 03, 04, 05, 06, 07, 08, 09, 10,11, 12, 13, 14, 16

PPXU Patches V1380000, 01, 02, 03, 04, 05, 06, 07,, 09, 10

PPXL Patches Y1380000, 01

BTS-PlusLoad A5.0 & A5.1 & 5.2 HS 01181303 2 CD-ROM / OMS

TRAU HT 030035 2 CD-ROM / OMSTRAU (bridge Load) HT 030021 (BR8.0) 2 CD-ROM / OMS

SW, Tools

LMT 290-1-38-02 1 CD-ROM / LMTDBAEM / Convfile 290-1-38-01 1 CD-ROM / LMTDBAEM / Convfile 290-1-38-01 1 CD-ROM / RCIDF Editor Evolution 290-1-02-00 1 CD-ROM

HW, BSCMPCCV9 mandatory S30861-Q494-X-xxTDPCV9 mandatory S30861-Q495-X-xxPPXXV1 mandatory S30861-Q462-X-xxSNAP mandatory S30861-Q463-X-xxSTLP optional S30861-Q466-X-xxCPEX optional S30861-Q479-X-xxPPXXV2 preferred S30861-Q486-X-xxESAM optional S30861-Q480-X-xx

Draft version 7/20

HW, TRAUBSCIV6 optional S30861-Q507-X-xxMSCIV6 optional S30861-Q508-X-xx

FW, BSCPPXXV1 sfv2114.hexPPXXV2 sfv4102.fwiESAM sfa4100.fwi

2.2.3 SW Overview Table

SW/FW/HWBR70/70 BR90/003

BSC, SW Load HB010103 HB010080.SWL

patch MPCC M1340200, 02, 03, 04, 06, 07, 08,09, 10, 11, 12, 13, 15, 16, 17, 18, 19,20, 21, 22,23, 24, 25, 26, 27, 28, 29,31, 32, 33, 36, 37, 39

M1380A00, 01, 02, 03, 04, 06, 07,09, 10, 11

patch TDPC T1340200, 01, 02, 03, 04, 05, 06, 07,08, 11, 13, 14, 15, 16, 17, 18, 19, 20,21, 22, 23, 24, 25, 26, 29, 30, 31, 32,33, 34, 35, 36, 37, 38, 39, 40, 41, 42,43, 46, 47, 48, 49, 52, 53, 54, 55, 56,57, 58, 59, 60, 62, 63, 68, 69, 71, 72,73, 74, 75, 76, 77

T1380000, 01, 02, 03, 04, 05, 06, 07,08, 09, 10, 11, 12, 13, 14, 16

patch PPXU V1340000, 01, 02, 03, 04, 06, 07,08, 09, 10, 11, 12, 13, 14, 15, 16, 17,18, 19, 20, 21, 22, 23, 24, 27, 28, 29,30, 33, 35, 36, 39

V1380000, 01, 02, 03, 04, 05, 06,07,, 09, 10

patch PPXL Y1340000, 02, 03, 04, 05, 06, 07,08, 09, 10,11

Y1380000, 01

BTS-Plus, SWLoad A5.0 & A5.1 & A5.2

HS 01169305 HS 01181303

TRAU, SW Load HT 030035 HT 030035

LMT, Load SW 271-1-34-14 290-1-38-02

LMT, driver SW 271-1-29-00 290-1-38-02

DBAEM SW 271-1-34-06 290-1-38-01

OMS/RC, SW Load omc_52_10_00 rc90_0.72

Draft version 8/20

2.3 Hints related to the BR9.0/003

2.3.1 Upgrade – Fallback procedure for BSC / BTSEBefore downgrade to previous version, all boards, which are not allowed with BR7.0 have to be replaced (e. g.PPXXV2) and the required boards (here PPXXV1) should be kept on stock.

2.3.2 Upgrade – Download of new BR9.0 SW TRAUDue to a missing room in the TRAU Bsci flash the TRAU upgrade must be carefully evaluated every time inBR8.0 and BR9.0 releases.It is possible download (without problems) the new BR9.0 load into TRAU, if the running TRAU load isHT030021 (BR8.0) or newer. In case the running SW on TRAU is older, a first upgrade to the so called TRAUBRIDGE SW (HT030021) is to be performed.In order to reduce the service downtime in the case the TRAU bridge load must be loaded first, adopt theupgrade strategy of splitting in two the whole set of TRAU configured on a BSC, avoiding whole SS/ linkinterruption.

2.4 Outage TimeThe minimum upgrade to BR9.0 will consist of 3 blocks, which have to be done one after the other:

1) Installation of new Radio Commander. No call affecting outage. Separate manual is necessary.

2) SW change within BSC. This leads to a call affecting outage of 6 minutes for initialisation.

3) SW change within BTSE and TRAU. This needs about 10 minutes (or 12 minutes by using of old TPU1 forBTS1) in case it is done in parallel.

So, the sum of call affecting outages will be about 16 minutes in minimum. Due to alignments, outage time willincrease in lerge networks.

2.5 Manuals

2.5.1 Extra Manuals needed

OMN:BSS/OMS-B/RC Item numbers A30808-X3247-M*-*-76*UMN:BSC Item numbers A30808-X3247-M2*-*-76*UMN:TRAU Item numbers A30808-X3247-M4*-*-76*

2.5.2 Manual Delta

Refer to the manuals of BR9.0, please. For details see Release Description SBS BR9.0.

2.6 Data Storage Media

See Release Description SBS BR9.0..

Draft version 9/20

2.7 Aspects of Quality

When working on HW always ensure that static electricity is discharged- Put on wrist strap and connect it to ground before pulling or plugging.- Use a conductive, grounded surface when working on modules.- Use appropriate protective bags for transport only.

3. Upgrade Procedure

3.1 PrerequisitesIn the Application launches, you can make various settings, including how to sort the commands:In the menu, select Option→ Preferences → Dialog settings → Representation of Service Menu toSpecify the sorting. If you select:

1. Area, all software-related commands except Create commands will be listed under SoftwareManagement.

2. Actions, all commands except Create commands will be listed under action.

Note: All procedures are described in this Manual for the Actions setting

3.2 BR9.0 SW Import from CD-ROM to RCIn the menu, select Option→ Preferences → Dialog settings → Representation of Service Menu to

3.2.1 Import BSC SW Load and BSC patchesTo import the BSC SW load perform the command mountDevice inserting a new directory where you wantTo mount cdrom:

V RC, 1 “action → muontDevice” mountDirectory /mnt/cdrom0

and Import inserting as source directory the local directory of the external device where the filerelnotes.txt is stored in (e.g.: if you find the file relnotes.txt in the directory “/mnt/cdrom0/bsc”,the source directory must be set to “bsc”.

VRC, 1 “action → import” source Dir /mnt/cdrom0/bsc/importData swLoadnetworkEntity bscswVersion 02-09-00-01-00-80_06-12-20force TRUEtargetHost [workstation name]

VRC, 1 “action → unmountDevice”

VRC, 1 “action → mountDevice” mountDirectory /mn/cdrom0

VRC, 1 “action → import” source Dir /mnt/cdrom0/patchimportData swPatchnetworkEntity bscpatchList ADD

#0 M1380A00.PCH

Draft version 10/20

#1 M1380A021.PCH…

#x T1380000.PCH…

#x V1380000.PCH…

#x Y1380000.PCH…

Force TRUEtargetHost [workstation name}

VRC, 1 “action → unmountDevice

3.2.2 Import BTSE SW LoadTo import the BTSE SW load perform the commands Mountdevice and Import from CD-ROM icon.

VRC, 1 “action → mountDevice” mountDirectory /mnt/cdrom0

VRC, 1 “action → import sourceDir /mnt/cdrom0/btsplusimportData swLoad networkEntity btse swVersion 01-01-18-00-13-03_07-01-12

force TRUE targetHost [workstation name]

3.2.3 Import TRAU SW LoadTo import the Trau SW load perform the commands Mountdevice and Import from CD-ROM icon.

VRC, 1 “action → mountDevice” mountDirectory /mnt/cdrom0

VRC, 1 “action → import” sourceDir /mnt/sdrom0importData swLoad networkEntity traue loadVersion 02−07−01−03−00−35_05−10−19 force TRUE targetHost [workstation name]

VRC, 1 “action → unmountDevice

3.3 Download SW from RC to BSC

3.3.1 Download BSC SW LoadTo download the BSC load perform the command download/SwLoad from the BSS Sum icon. Insert as loadVersion the string retrieved from file relnotes.txt. The value of the parameter userLabel is a label suitable forThe operator to identify the SW version.

VRC, 5 “action → downloadSWLoad” networkEntity bscSwVersion 02−09−00−01−00−80_06−12−20

Draft version 11/20

sourceHostName [workstation neme]userLabel [user defined]withPatch TRUEbestEffort TRUEforced FALSE

3.3.2 Download BTSE SW LoadTo download the BTSE load perform the command download/SwLoad from the BSS Sum icon.

VRC, 5 “action → downloadSwLoad networkEntity btse (for BTS-Plus)swVersion 01-04-18-01-13-03_07-01-12sourceHost [workstation name]userLabel [user defined]withPatch FALSEbestEffort TRUE

3.3.3 Download TRAU SW LoadTo download the TRAU load perform the command download/SwLoad from the BSS Sum icon.

VRC, 5 “action → downloadSwLoad networkEntity traueswVersion 02−09−00−03−00−18_06−11−17sourceHost [workstation name]userLabel [user defined]withPatch FALSEbestEffort TRUEforced FALSE

3.4 Download SW from BSC to NEY

Initiate a download from BSC disk to BTSE and TRAU. In case of failure repeat download.

3.4.1 Download SW from BSC to BTSEOpen the SWLoad list in the BSS SW sum panel and select the record of the SW load you want to download.Click with the right button of the mouse and perform the command Nedownload:

VRC, 3 select the required SW “action → NeDownload” NTWEL BTSE 0…xNELIST NE_NumberULAB [user defined name]MODE UNFORCED

If you have to download several BTS with the same load on the same BSC you can select more instances ofBTSEIn the GUI command.

3.4.2 Download SW from BSC to TRAUAttention please to the Operator Hint OG900TRAUP OM0001 and to the chapter:2.3.2. Upgrade – Download of new BR9.0 SW TRAU.

Open the SW Load list in the BSS SW sum panel and select the record of the SW load you want to download.

Draft version 12/20

Click with the right button of the mouse and perform the command Nedownload:

VRC, 3 select the required SW “action → NeDownload” NTWEL TRAU 0…xNELIST NE_NumberULAB [user defined name]MODE UNFORCED

If you have to download several TRAUs with the same load on the same BSC you can select more instances ofTRAUin the GUI command.

3.5 Patch Handling

The following patches have to be downloaded now to disk (if already loaded – see step 3.3.1 Download BSCSW Load), and have to be enabled for the file system. Enter data according to the cross-reference list below andcompare again with the list in the Patch description of related Release Dokumentation.

Processor Patchversion

File ID

mpcc M1380A00.PCHmpcc M1380A01.PCHmpcc M1380A02.PCHmpcc M1380A03.PCHmpcc M1380A04.PCHmpcc M1380A05.PCHmpcc M1380A06.PCHmpcc M1380A07.PCHmppc M1380A09.PCHmppc M1380A10.PCHmppc M1380A11.PCH

tdpc T1380000.PCHtdpc T1380001.PCHtdpc T1380002.PCHtdpc T1380003.PCHtdpc T1380004.PCHtdpc T1380005.PCHtdpc T1380006.PCHtdpc T1380007.PCHtdpc T1380008.PCHtdpc T1380009.PCHtdpc T1380010.PCHtdpc T1380011.PCHtdpc T1380012.PCHtdpc T1380013.PCHtdpc T1380014.PCHtdpc T1380016.PCH

ppxu V1380000.PCHppxu V1380001.PCHppxu V1380002.PCHppxu V1380003.PCHppxu V1380004.PCHppxu V1380005.PCHppxu V1380006.PCHppxu V1380007.PCH

Draft version 13/20

ppxu V1380009.PCHppxu V1380010.PCH

ppxl Y1380000.PCHppxl Y1380001.PCH

Download the patches to BSC\NEW (patch version see above).

VRC, 5 “action → downloadSWPatch swVersion 02-09-00-01-00-80_06-12-2sourceHost [workstation name]patchName M1360A00.PCHuserLabel [use defined, e.g. M1380A00]

Repeat this step fo each patch and enable afterwards all patche with the following command:

VRC, 5 select the related patch “set→ set…” pemanent TRUEpriortitySlotNumber #value

The operation must set the Patch Permanent Status of TRUE and the PRIOSLOTN is given the same value as the lastsignificant digits of patch no.

Example:

mpcc1380A00.PCH prioritySlotNumber 0tpcc1380000.PCH prioritySlotNumber 0ppxu1380001.PCH prioritySlotNumber 1

3.6 DB conversion from BR7.0/70 to BR9.0/003

Precondition:

1. O-link object must be ENABLED to perform the communication between BSC and RC2. Old and new DBAEM- and CONVFILE versions are installed on new RC2. Save DB to be sure to upload the running configuration

(BSS SUM / BSS SW SUM / SAVE DB)

3.6.1 Database conversion without Modification of SWLH of BTSE and TRAU

In a more safe procedure the BSC is first upgraded with the BSC SW BR9.0/003. The expected SWversions of all the connected NEs are not modified, so that the previous SW versions of all connectedBTSEs and TRAUs are activated. After the BSC is up and running well with BR9.0/003 then it is possible tochange the expected SW version of a limited number of NEs, while the others are still operational, and so on tillthe whole NEs are upgraded.This has the advantage to reduce the BSS service downtime, to check the BSC correctness before the NE update,to improve the control of the progress of the BTSM and TRAU SW activation.

A faster way for the NE SW activation is to use a scipt file, which allows upgrading all the NE in a single Step.After the BSC is up and running well with BR7.0/70 start the just created before script file, which could includethe following sequence:

Lock BTSM:NAME=BTSM:0;Lock BTSM:NAME=BTSM:1;Lock BTSM:NAME=BTSM:2;

Draft version 14/20

…Set BTSM:NAME:BTSM:0,EXPSWV=”xx-xx-xx-xx-xx-xx_xx-xx-xx”Set BTSM:NAME:BTSM:1,EXPSWV=”xx-xx-xx-xx-xx-xx_xx-xx-xx”Set BTSM:NAME:BTSM:2,EXPSWV=”xx-xx-xx-xx-xx-xx_xx-xx-xx”…Unlock BTSM:NAME=BTSM:0;Unlock BTSM:NAME=BTSM:1;Unlock BTSM:NAMA=BTSM:2;…

The “unlock” command causes an Abis alignment, which triggers the activation of the new SW load. ThisCommand receives an immediate acknowledgementy by BSC, thus the BTSM activations are performed inparallel.

The following database conversion procedure can be used to convert the database from BR7.0/70 to the newBR9.0/003 version without modification of SWLH of BTSE and Trau.

Upload BR7.0/70 Database and Generate BR9.0/003 ASCII format

This command is executable if the BSC DB to be uploaded has been selected from the list opened by“seeEsuDb” command. It allows to transfer the Database from the BSC disk to the RC d isk, converts the Binaryfile into the corresponding BR7.0/70 command ASCII file and converts the command ASCII file BR7.0/70 tothe command ASCII file BR9.0/003.

On RC Sum panel, perform the command:

VRC, 16 “action → uploadDbAndConvertCmd” bssId ntargetRelease 29038targetFile /export/local/OMC/DATA/…

…<SBS name>/BACKUP/……cmd29038.asc

Snap sn used (snap or snapStlp)confType capacity configuration (basic or

high)licFile path where the license key file is

availablebscType basic or enhanced

n- Number of the BSS for which dbfile.dba has to be migrated

Modify the new ASCII file

In the case is necessary to modify some database parameters, open a terminal shell and connect to OMP withtelnet.Using an text editot (VI) open the file cm29038.asc and axecute the modifications.

Generate binary DB format

The command allows generating a binary file representing a BSS configuration database processing acommand ASCII file. On RC Sum panel, from Offline Tools icon, perform the command:

VRC, 16 “action → makeDbofCmd” sourceFile cmd29038.asctargetRelease 29038targetFile [insert complete path]/Dbfile.dba

(for ex./export/local/OMC/DATA/SBS_5/NEW/…]

Download DB

Draft version 15/20

This service allows the operator to download a binary BSS configuration database file from the RC to the BSS.On RC Sum panel, from OfflineTools icon, perform the command:

VRC, 16 “action → downloadDB” bssld [BSS number]sourceFile [insert complete path]Dbfile.dba

(for ex./export/local/OMC/DATA/SBS_5/NEW/…]targetLabel [user defined]

3.6.2 Database conversion with Modification of SWLH of BTSE and TRAUAfter BSC initialisation with BR9.0/003 SW all BTSE and TRAU arecoming with the new BR9.0/003 SWversion. For that all the SWLH for BTSE and TRAU must be modified during the database conversion.

Upload BR7.0/70 Database and Generate BR9.0/003 ASCII format

This command is executable if the BSC DB to be uploaded has been selected from the list opened by“seeEsuDb” command. It allows transferring the Database from the Bsc disk to the RC disk, converts theBinary file into the corresponding BR7.0/04 command ASCII dile and converts it info the command ASCII fileBR9.0/003.On RC Sum panel, perform the command:

VRC, 16 “action → uploadDbAndConvertCmd” bssld ntargetRelease 29038targetFile /export/local/OMC/DATA/…

…<SBS name>/BACKUP/cmd29038.asc

n – Number of the BSS for which dbfile.dba to be migrated.

Modify the new ASCII file

In order to open the ASCII file you must connect to OMP executing Telnet on a terminal shell.Open the ASCII file with a text editor and set new SW version for all BTSE and TRAU.

BTSE-x:SWVERS=”01-01-18-00-13-03_07-01-12” (for BTS-Plus as in 2.2.3)TRAU-x:SWVERS=”02−09−00−03−00−20_06−12−06” (for all TRAU as in 2.2.3)

Save the changes (e.g. save as cmd29038new.asc).

Generate binary DB format

The command allows generating a binary file representing a BSS configuration database. On RC Sum panel,from Offline Tools icon, perform the command:

VRC, 16 “action → makeDbofCmd” sourceFile cmd29038.asctargetRelease 29038targetFile [insert complete path]/Dbfile.dba

(for ex./export/local/OMC/DATA/SBS_5/NEW/…]

Download DB

Draft version 16/20

This service allows the operator to download a BSS configuration database binary file from the RC to theBSS. On RC Sum panel, from OfflineTools icon, perform the command:

VRC, 16 “action → downloadDB” bssld [BSS number]sourceFile [insert complete path]Dbfile.dba

(for ex./export/local/OMC/DATA/SBS_5/NEW/…]targetLabel [user defined]

3.7 BSS Upgrade

3.7.1 Setting of BSC SW load as “NEW” one

Perform the command SetNewEsu and select the load you want to activate from BSC SW icon ( in BSSSW Sum panel). Then the user must select the SW load to be downloaded and set the ACTN attribute toNEW_ESU.

VRC, 0 “action → setNewEsu…” sWMRelatedGSMObject related Object

3.7.2 Setting of new DB File as “NEW” one

Perform the commans SetNewEsu and select the database you want to activate (database without modification ofSWLH of BTSE and TRA should be preferred) from BSC DB icon (in BSS SW sum panel). Then the user mustselect the SW load to be downloaded and set the ACTN attribute to NEW_ESU.

VRC, 10 “action → setNewEsu…” sWMRelatedGSMObject related Object

3.7.3 Scanner Handling

Upload the last scanner results. This should be done at least before the BSC will be initialised.

VRC, 8 “action → Upload MeasFile”

3.7.4 BSC Initialisation

Prerequisites on command loadNewEsu

1. The system must be in normal state ( no other operation is in progress).2. The operation will be performed only if all configured BSC cards are redundant.3. The OperationalState attribute of BSCOSUDB.newESU must be ENABLED.4. The Data Base version has to be compatible to the SW to load.

For additional “prerequisites” please refer to the corresponding “Application Guidelines” in the CML, and thedescription of Charge Version procedure in OMN:BSC

Start the Change Version procedure

FromBSC SW icons perform the command LoadNewEsu. At the end of the operation the state for BSCOSUSWwill be waiting for AcceptNewEsu and BSC Sw icon will be yellow again.

> BE AWARE THAT THERE WILL BE NO ACCESS TO BSS FOR AROUND 6 MINFOR BSC BRING-UP (plus additional time for NE alignment)<

Draft version 17/20

VRC, 0 “action → loadNewEsu”

The Change Version of BSC takes at least 6 min.

Note 1: If the SW Upgrade is performed via RC and the OMAL connection cannot be re-establishedWithin one hour an automatic rollback to theold version is performed.During this period of time the BSC is accessible via the LMT; however the “End Change Version”Command is refused, while the “Rollback” command and the “SYSINIT” command are accepted.Also it is possible to enter DB commands in case the OMAL link is not connected because of badConfiguration parameters.

Note 2: If the SW version set as NEW is the sames as in BACKUP a bring-up will be performed and theFinal state of BSCOSUSW will be IDLE.

After BSC initialisation, all BTSE and TRAUS will come up with the old BR7.0/70 SW version (if theDatabase conversion without modification of SWLH was performed).The activation of new BR9.0/003 SWversion of all connected NE must be done afterwards separately.The links to BTSE, TRAU and MSC are coming up automatically. Verify it by setting up calls; check on RC ifthe alignment to the new BSS load is completed. Check the state of the running SW in BSC.

Terminate the Change Version procedure

After successful upgrade of BSS, if the BSCOSUSW state is “Waiting for AcceptNewEsu”, from the BSCSW icon perform the command AcceptNewEsu. At the end of the operation the BSCOSUSW state will beIDLE and the new SW load instance will also be the BACKUP one (perform the command GetBackupEsufrom BSC SW icon).

VRC, 0 “action → acceptNewESU”

Rollback procedure

If the system behaviour is not satisfactory, fall back to the previous SW version with the followingCommand:

VRC, 0 “action → LoadBackupEsu BSC_SW”

3.7.5 BTSE, TRAU SW Activation

Step by step the user can change the sofrware version of BTSE and TRAU equipment, grouping them intogroups of Network elements. This can avoid the complete loss of service.

From the icon BTS in the BSS Sum/BTSE Site Sum/ icon BTSM, selrct the following commands:

VRC, 14 “action → Lock BTSM”VRC, 14 “action → Set…” expectedSwVersion 01-01-18-01-13-03_07-01-12 (BR9.0/003 for BTS-Plus)

VRC, 14 “action → Unlock BTSM”

The “Unlock command causes an Abis alignment, which triggers the activation of the new SW load. Thelinks to BTSE come up automatically. Verify it by setting up calls. Check the state of the running SW.

From the icon TRAU in the BSS Sum/TRAUE site Sum/TRAUE Sum, select the following commands:

Draft version 18/20

VRC, 11 “action → Set…” expectedSwVersion 02−09−00−03−00−20_06−12−06 (BR9.0 TRAU)

Attention: SW activation of that TRAU which is handling the OMAL, will lead to a loss of BSC-RCconnection. From the icon TRAUE SW perform the command LoadBackupEsu.

VRC, 12 “action → LoadBackupEsu”

The Links to MSC and RC come automatically. Verify it by setting up calls. Check the state of therunning SW.

3.7.6 Scanner Handling after BSC Upgrade

Check after successful upgrade if all scanners started again automatically.If script file “measdelta” is used see procedure in RC Upgrade manual to start it again.

4. Fallback

4.1 BSS Downgrade

Before downgrade the BSS to the previous version, please pay attention to the Hint on page 9: Fallbackprocedure for BSC/BTS.To save outage time during TRAU activation download old TRAU SW (also AMR-TRAU SWif necessary) into the TRAU by performing the command:

VRC, 3 select the required SW “action → NEDownload” NTWEL TRAU 0…XNELIST NE_NumberULAB [user defined=userLabel]MODE UNFORCED

Set the old BSC SW and the old database file as “BACKUP” and initialise the BSC with the followingcommand:

VRC , 0 “action → setBackupEsu…” sWMRElatedGSMObject related Object

VRC , 10 “action → setBackupEsu…” sWMRElatedGSMObject related Object

VRC. 0 “action → LoadBackupEsu”

Thelinks come up automatically: Verify it by setting up calls.Check the state of the running SW in all the NE.

4.2 BTSE Downgrade

In case the BTSE has to be downgraded only (4.1 has not been performed before) set the SW loadheaders in the DB to the old SW versions and activate the old SW in all the BTSE. From the icon BTS inthe BSS Sum/BTSE Sum panel, select Set command.The outage time foe a BTSE depends on BTSE type. For BTS-1 an outage time of 8 – 12 minutes will beexpected (depending of TPU type).

VRC, 14 “action → LockBTSM”

Draft version 19/20

VRC, 14 “Set → Set…” expectedSwVersion 02-04-16-01-69-00_04-02-24(BR7.0/04 for BTS-PLUS)

VRC, 14 “action → UnlockBTSM”

The links to BTSE come up automatically. Verify it by setting up calls. Check the state of the running SWin all the NE.

4.3 TRAU Downgrade

Attention please to the Operator Hint OG900TRAU OM0001 and chapter 2.3.2 Upgrade – Download of newBR9.0 SW TRAU

In case the BTSE has to be downgraded only (4.1 has not been performed before) set the SW loadheaders in the DB to the old SW versions and activate the old SW in all the BTSE. From the icon BTS

inthe BSS Sum/BTSE Sum panel, select Set command.The outage time foe a BTSE depends on BTSE type. For BTS-1 an outage time of 8 – 12 minutes will

beexpected (depending of TPU type).

VRC, 14 “action → LockBTSM”

VRC, 14 “Set → Set…” expectedSwVersion 02-04-16-01-69-00_04-02-24(BR7.0/04 for BTS-PLUS)

VRC, 14 “action → UnlockBTSM”

The links to BTSE come up automatically. Verify it by setting up calls. Check the state of the runningSW

in all the NE.

5. Documentation

Please refer to:

SBS Operation Dokumentation, BR9.0Item number A30808-X3247-M*-*-76*

Nonstandard Maintenance, BR9.0Item Numbers A30808-X3247-M*-*-76*

Release Description SBS BR70/xx and BR 9.0/003

Draft version 20/20

6. Abbreviations

BR BaseStationSystem ReleaseBSC Base Station ControllerBSS Base Station SystemBTS-Plus BS40, BS41, BS240, BS241, BS240XLBTSE Base Transceiver Station EquipmentDB DatabaseFD Floppy DiskFW FirmwareHW HardwareLMT Local Maintenance TerminalNE Network EntityOMC Operation and Maintenance CentreOMS Operation and Maintenance SystemOMT Operation and Maintenance TerminalRC Radio CommanderSBS SIEMENS BaseStation SystemTRAU Transcoder and Rate Adaption Unit

VRC, 0 Enter at RC Window Regional Sum /BSS Sum /BSS SW SumIcon BSC SW

VRC, 1 Enter at RC Window Regional Sum /RC Sum /OMT SumIcon Floppy0 or CD-ROM

VRC, 3 Enter at RC Window Regional Sum /BSS Sum /BSS SW SumIcon SW Loads

VRC, 5 Enter at RC Window Regional Sum /BSS SumIcon BSS SW

VRC, 8 Enter at RC Window Regional Sum /BSS SumIcon Scan Sum

VRC, 10 Enter at RC Window Regional Sum /BSS Sum /BSS SW SumIcon BSC DB

VRC, 11 Enter at RC Window Reg. Sum /BSS Sum /TRAU Site Sum /TRAUESum

Icon TRAUVRC, 12 Enter at RC Window Regional Sum /BSS SW Sum

Icon TRAUE SWVRC, 14 Enter at RC Window Regional Sum /BSS Sum /BTSE Site Sum

Icon BTSMVRC, 16 Enter at RC Window Regional Sum /RC Sum

Icon Offline ToolsVRC, 17 Enter at RC Window Regional Sum /RC Sum

Icon File Admin