BSC3i Upgrade for SDH_Sonet Equipment Protection_ver1_6

DN09114087BSCupgradeforSDH/SonetequipmentprotectionCopyright2013NokiaSolutionsandNetworks.Allrightsreserved.CONFIDENTIALAPPROVED1.61 (107)

BSC upgrade forSDH/Sonet equipmentprotectionRelease Delivery: HW UpgradeProduct Family: Radio ControllersProduct: BSC3i 1000/2000, UpgradedFlexi BSCRelease: S16 onwards

Approval date: 12-Dec-2012

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us inworking towards a cleaner, safer environment. Please recycle product packaging and follow therecommendations for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental serviceswe offer, please contact us at Nokia Solutions and Networks for additional information.


Table of Contents1 Purpose .................................................................................................................................................. 42 Scope of applications .............................................................................................................................. 53 Using the document ................................................................................................................................ 6

3.1 General info ....................................................................................................................................................... 63.2 Upgrade macro .................................................................................................................................................. 7

3.2.1 Structure ...................................................................................................................................... 73.2.2 Communication ............................................................................................................................ 73.2.3 Log files ....................................................................................................................................... 8

4 Introduction ........................................................................................................................................... 104.1 BSC3i equipment before upgrade ..................................................................................................................... 114.2 BSC3i equipment after upgrade........................................................................................................................ 12

5 Pre-requirements .................................................................................................................................. 145.1 Pre-requirements & Actions needed prior upgrade ............................................................................................ 145.2 Restrictions ..................................................................................................................................................... 145.3 Needed documentation .................................................................................................................................... 155.4 Needed equipment .......................................................................................................................................... 155.5 HIT and upgrade macros.................................................................................................................................. 15

5.5.1 System requirements for HIT ...................................................................................................... 155.5.2 Installing HIT .............................................................................................................................. 155.5.3 Installing HIT upgrading macros .................................................................................................. 165.5.4 HIT settings................................................................................................................................ 165.5.5 Connection settings .................................................................................................................... 165.5.6 Starting the HIT application / macro execution ............................................................................. 28

6 Fallback copying of the current package ................................................................................................ 357 BSC configuration printout (pre-check) .................................................................................................. 368 SDH/Sonet equipment protection upgrade for BSC in case of STMU full capacity configuration(2+2) 37

8.1 Re-host traffic from concerning STMU/ET16/ETIP unit ...................................................................................... 388.2 Delete old configurations & equipment .............................................................................................................. 398.3 Install redundant ETS2 plug-in unit ................................................................................................................... 408.4 Make cabling changes and install new cables related to MCMU-0 ..................................................................... 408.5 Make DIP-switch changed to SW256B in MCMU,0 ........................................................................................... 418.6 Make cabling changes and install new cables related to MCMU-1 ..................................................................... 418.7 Make DIP-switch changed to SW256B in MCMU-1 ........................................................................................... 418.8 New configuration & equipment with HW protection .......................................................................................... 41

8.8.1 BSC3i 1000/2000 or upgraded Flexi BSC.................................................................................... 428.8.2 New Delivery Flexi BSC.............................................................................................................. 45

8.9 MCMU diagnostic ............................................................................................................................................ 499 SDH/Sonet equipment protection upgrade for BSC in case of STMU half capacity configuration(1+1) 51

9.1 In case of STMU indexes between 0 to 6 .......................................................................................................... 529.1.1 Re-host traffic from concerning STMU/ET16/ETIP unit ................................................................ 529.1.2 Delete interfaces from affected STMU, ET16/ETIP units .............................................................. 529.1.3 Change STMU units states to SE-NH and delete ET16/ETIP equipment ...................................... 529.1.4 Remove old protection groups .................................................................................................... 529.1.5 Delete ET sets from GTIC-0 units ............................................................................................... 539.1.6 Make cabling changes and install new cables related to MCMU,0 ................................................ 539.1.7 Make DIP-switch changes to SW256B in MCMU,0 ...................................................................... 539.1.8 Make cabling changes and install new cables related to MCMU-1 ................................................ 539.1.9 Make DIP-switch changes to SW256B in MCMU-1 ...................................................................... 549.1.10 Create new ET sets for upgraded STMU unit .............................................................................. 549.1.11 Change upgraded STMU unit to WO-EX state ............................................................................. 55

9.2 In case of STMU indexes between 8 to 16 ........................................................................................................ 569.2.1 Re-host traffic from concerning STMU/ET16/ETIP unit ................................................................ 569.2.2 Delete interfaces from affected STMU, ET16/ETIP units .............................................................. 56


9.2.3 Change STMU units states to SE-NH and delete ET16/ETIP equipment ...................................... 569.2.4 Remove old protection groups .................................................................................................... 579.2.5 Delete ET sets from GTIC-1 units ............................................................................................... 579.2.6 Delete old STMU unit equipment ................................................................................................ 579.2.7 Make cabling changes and install new cables related to MCMU,0 ................................................ 579.2.8 Make DIP-switch changes to SW256B in MCMU,0 ...................................................................... 589.2.9 Make cabling changes and install new cables related to MCMU-1 ................................................ 589.2.10 Make DIP-switch changes to SW256B in MCMU-1 ...................................................................... 589.2.11 Create new STMU unit to GTIC/ETC cartridge ............................................................................ 589.2.12 Create new ET sets for upgraded STMU unit .............................................................................. 599.2.13 Change upgraded STMU unit to WO-EX state ............................................................................. 60

9.3 Install redundant ETS2 plug-in unit ................................................................................................................... 609.4 Make cabling changes for redundant STMU...................................................................................................... 619.5 Create Hardware Protection Groups configuration ............................................................................................ 61

9.5.1 Equip new redundant STMU units ............................................................................................... 619.5.2 Create new protection group ....................................................................................................... 629.5.3 Change new STMU units to WO-EX state ................................................................................... 63

9.6 MCMU diagnostic ............................................................................................................................................ 6310 Copy the HW equipment database information to the disk (DBC) ........................................................... 6411 Actions after upgrade & Post conditions ................................................................................................ 65

11.1 BSS Integration ............................................................................................................................................... 6511.2 BSC configuration printout (post-check) ............................................................................................................ 6511.3 Return to the old HW configuration ................................................................................................................... 65

12 Appendix ............................................................................................................................................... 6612.1 Appendix1: MCMU,0 related cablings in BSC3i 1000/2000 or upgraded FlexiBSC3i ........................................... 6612.2 Appendix2: MCMU,1 related cablings in BSC3i 1000/2000 or upgraded FlexiBSC3i ........................................... 7112.3 Appendix3: MCMU,0 related cablings in New Delivery FlexiBSC3i ..................................................................... 7512.4 Appendix4: MCMU,1 related cablings in New Delivery FlexiBSC3i ..................................................................... 8012.5 Appendix5: SW256B jumper settings ................................................................................................................ 85

12.5.1 SW256B jumper settings in New Delivery Flexi BSC ................................................................... 8512.5.2 SW256B jumper settings in upgraded Flexi BSC ......................................................................... 8912.5.3 SW256B jumper settings in BSC3i .............................................................................................. 94

12.6 Appendix6: GTIC & ETC PCM usage in case of BSC3i 1000/2000 .................................................................... 9812.7 Appendix7: GTIC & ETC PCM usage in case of upgraded Flexi BSC .............................................................. 10012.8 Appendix8: GTIC & ETC PCM usage in case of initial delivery Flexi BSC ........................................................ 10212.9 Appendix9: BSC3i 1000/2000 or upgraded Flexi BSC SW10C_A and CC4C_A cartridges locking pegs ........... 10512.10 Appendix10: Initial Flexi BSC SGC1C-Acartridges locking pegs...................................................................... 106

Contact:

Contact your local Nokia Solutions and Networks support

Summary of changes:

1.0-0 1st approved version1.1-0 Corrected appendix 5 DIP switch settings for Initial

flexi BSC1.2-0 Added CR75 details1.3-0 Added connection settings for Linux in chapters 5.5.5.21.4-0 Added note regarding COM issue in HIT3.3 in chapter

5.5.5.1.2 and 5.5.5.2.204-Apr-2013 1.5-0 Removed note regarding COM issue from chapters

5.5.5.1.2 and 5.5.5.2.2.Also updated the hit version as3.4-0.

04-Mar-2014 1.6-0 Template update. Updated appendix 12.5: SW256Bjumper settings.


1 PURPOSE

This document describes the implementation of changing line protection of ETS2 plug-in unit to equipmentprotection in case of BSC environment. This document does not support Combined TCSM3i part. That upgradecan be handled with BSC/TCSM upgrade for SDH/Sonet equipment protection procedure.

This document can be used with following environments:- BSC3i1000/2000

- Upgraded Flexi BSC 3000/4200

- New delivery Flexi BSC 3000/4200


2 SCOPE OF APPLICATIONS

The BSC upgrade for SDH/Sonet equipment protection implementation is available for third generation DX200BSC3i and Flexi BSC in S16 release level onwards.

The procedure cannot be implemented to STMU (ETS2 plug-in unit) unit without traffic interruption. Traffic mustbe moved from concerning ETS2 (or effected ET16/ETIP) plug-in unit before the actual upgrade.

Procedure must be performed locally at BSC site.


3 USING THE DOCUMENT

3.1 General info

The BSC upgrade for SDH/Sonet equipment protection can be done using the HIT (Holistic Integration Tester)software tool. Optional way is to make the upgrade manually by following this documentation.

The HIT software automates most of the tasks necessary for the software or hardware upgrade. The HIT softwareand the instructions are included in this manual. It is recommended that the HIT User's Manual is gone throughbefore starting the program.

When using the HIT for upgrading BSC, these instructions should be followed for a more detailed description ofthe different phases, which take place during the upgrade. The upgrade macro menu dialog is designed to followclosely this document.

NOTE: The commands executed by the HIT macro do not always match exactly with the commandspresented in the manual. This is because sometimes the automated tasks of the HIT macro require morecommands and different command syntaxes, than are presented in the manual.

When using the HIT, the MML commands are executed automatically. It is not necessary to type any commandsuntil it is specifically requested by HIT.


3.2 Upgrade macro

3.2.1 Structure

All the SW & HW macros are gathered under one main macro (UPGMAIN.HIT), from which the wanted SW / HWupgrade can be selected. Regardless of which macro (SW or HW upgrade) is wanted to run, the user alwaysstarts with the same main macro.Example of macro structure:

UPGMAIN.HITx Select wanted upgrade:

o SOFTWARE UPGRADES SW upgrade S15 -> S16

o HARDWARE UPGRADES

HW upgrade 1 HW upgrade 2

Under each upgrade / tool there is a upgrade specific menu which describes the steps which can be executedindividually:

SW upgrade S15 -> S16 (selected from main menu)x Select wanted step

o Make fallbacko Check Firmwareo Make pre-checko Copy SWo o

When a step is completed successfully, the user is brought back to upgrade menu and a Done. -sign will appearat beginning of the name of the step. If step execution fails for some reason, macro stops and user can correctthe error manually and then continue macro execution normally.

If macro or computer freezes totally during step execution and macro needs to be restarted, user cannot re-runthe incomplete step from the menu. In this case, the user must complete that certain step manually, using thisdocumentation as guide. When the step has been completed manually, user can continue the macro executionfrom next available step. Note, that in the upgrade menu, there will be Man. sign instead of Done. sign atbeginning of name of the manually executed step.

Note!Once, user enters from main menu to upgrade menu, only way to get back to the main menu is to restartwhole macro.

3.2.2 Communication

The macro communicates with user by using the HIT Pop-up windows.

x Asking the user to give information (e.g. paths, file names, etc.) & other user selections.x Error situationsx Manual execution steps (i.e. when macro expects user to do some actions manually (e.g. copy some

files, install new HW /cabling etc.)x Macro completion


3.2.3 Log files

The upgrade macro provides different log files, from where the user can verify the executed steps in macro andthe success of the different steps & commands executed in the macro. There are three different kind ofinformation / log files:x Log file from HIT Response window (.log)

o This log contains all the information of the macro execution (each MML command and thewhole output of the macro execution)

o User can accept the default log-file name or specify a new one. Macro gives following pop-upwindow for selection:

x Macro writes separate log files for following steps:o Configuration printout (PRE)o Firmwareo Plug-in unit software upgradeo Safecopyo Transfer software to BSCo Configuration printout (PRE)

x The same information can be found from both from a main log file and from these specified smaller logfiles.

o Log file from HIT Message window (Messages.log)x The contents of the message window are saved after macro execution.x Information about errors in macro execution

o Log print of HIT (TimeTable.log) This is a shorter description of the execution of the macro,and the log contains information about:

x Starting an execution step in macrox Execution status (Done).x Completion of execution step in macro

If macro execution is stopped for some reason, the log files still remain in the folder the user has specified. Whenmacro execution is started again, the log writing is continued from the end of existing log files. All previouslywritten log information remains intact and nothing is overwritten.


When macro is started at a first time, also two .INI files are created:x WORKDIR.inix .ini

WORKDIR.ini contains information about log file directories. Same macro - from the same directory - can be usedmany times for example for different BSC SW/HW upgrades and user may define different log file directory foreach BSC. This folder information is saved to WORKDIR.ini file and saved to same directory where macro exists..ini file contains information about statuses of executed macro steps and also some importantvariable information which is collected from user (e.g. package name and directory). This variable information arethe one which are needed when for example macro execution is stopped for some reason and needs to bestarted again using same main information. The file contains the latest execution statuses. If same steps are forsome reason executed many times, the last execution status remains (DONE/MAN).

IMPORTANT!When user gives for example wrong package or directory name and stops the macro execution, user must delete.ini file from log file directory and start macro again. When .ini file is deleted from log file directory andstarted again, the macro will ask same main information from user again. Otherwise, the macro uses the alreadygiven information which is saved to .ini file.

Normally, actions from user to any .ini file or to any other created macro file (in log file directory) is NOTneeded.


4 INTRODUCTION

The BSC upgrade for SDH/Sonet equipment protection procedure consists of the following tasks:

x Fallback copying of the current softwarex BSC configuration printout (pre-check)x SDH/Sonet equipment protection upgrade for BSC in case of STMU full configuration (2+2)x SDH/Sonet equipment protection upgrade for BSC in case of STMU half configuration (1+1)x Actions after upgrade and post conditions

a. BSS Integration

b. BSC configuration printout (post-check)

Fallback copying, BSC configuration printout tasks can be executed during daytime.

Actual upgrade is recommended to be executed during night-time. This procedure can be done only for BSC3i1000/2000 or Flexi BSC. Line protection cannot be used after equipment protection has been taken in use. So,the upgrade will be done for whole GTIC cartridge at the time even each STMU unit is handled one by one.

If STMU units has been configured prior the upgrade, then choose the either full or half option depending on theused configuration.

In some STMU cases, the upgrade may concern also ET16/ETIP or other STMU PCM areas. In this case, thetraffic must be moved from these units, interface(s) must be removed because the plug-in unit needs to bedeleted from equipment database.

The estimated time for HW upgrade depends on the configuration of the BSC.

The upgrade cannot be executed with traffic and traffic needs to be re-hosted. During upgrade STMU(s) unit willbe blocked and state changed to TE-EX or SE-NH.

There is a choice of several options how the GTIC-0 and GTIC-1 cartridges has been equipped before upgrade.The choices depend on the PIU types and configurations, like followingx Use ETS2 cards with optical interface redundancy.x Use mixed ET16 and ETS2 in the cartridges.x Use mixed ET16 and ETIP in the cartridges.

With this procedure also following possibility is to be added:x Use ETS2 cards with hardware redundancy

Background:One STMU unit (that is, one ETS2 plug-in unit) has four SETs in use in the default configuration and in the otheralternative one STMU unit (that is, one ETS2 plug-in unit) has two SETs in use. In optical interface redundancy,only even STMU indexes are used; either four (by default) or eight (alternative) in both cartridges (GTIC 0 andGTIC 1).

In S12 and S13 releases only transmission protection for STMU units is implemented. I.e. the protection switchingis done by between two fibres connected to the same ETS2 unit. The main disadvantage of the transmissionprotection is that if e.g. unit computer fails, all the traffic handled by the unit may be prevented until the unit isrestarted.

Equipment protection of SDH/SONET interfaces is introduced in S15 onwards. In case of equipment protectionworking and protection sections of the same STM-1/OC-3 optical interface are located in different ETS2 plug-inunits.


Full capacity means that four ETS2 plug-in units are equipped to both GTIC cartridges (GTIC cartridges poweredby different PDFU-Bs) and both STM-1/OC-3 interfaces (two active and two standby SET(s) per STM-1/OC-3interface) of ETS2 plug-in units are in use.

STMU indexes before redundancy upgrade are following:STMU(s) in GTIC-0: 0 & 2 & 4 & 6STMU(s) in GTIC-1: 16 & 18 & 20 & 22

When HW redundancy upgrade is done , four new ETS2 plug-in units must be added for both GTIC-0 and GTIC-1to gain same capacity as in the original configuration.

Half capacity means that eight ETS2 plug-in units are equipped to both GTIC cartridges (GTIC cartridgespowered by different PDFU-Bs) and only the first one of the STM-1/OC-3 interfaces (active SET + standby SET)of ETS2 plug-in units are in use. This configuration can be used only in BSC3i 1000/2000.

STMU indexes before redundancy upgrade are following:STMU(s) in GTIC-0: 0 & 2 & 4 & 6 & 8 & 10 & 12 & 14STMU(s) in GTIC-1: 16 & 18 & 20 & 22 & 24 & 26 & 28 & 30

When HW redundancy upgrade is done for all ETS2 units, if same capacity as in the original configuration iswanted, the second interface of the ETS2 plug-in unit must be taken in use.

4.1 BSC3i equipment before upgrade

When Hardware Redundancy Upgrade:

Half capacity is in use before upgrade:


4.2 BSC3i equipment after upgrade

Configuration after HW upgrade:

ActiveHotlinks (16 pcs)

STMU

GTIC 0

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

10

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

S B1 -0

S B1 -1

S B2 -0

S B2 -1

OPR

Tx/R xFAIL

S TM- 1/OC -3

S TM- 1/OC -3

S TM- 1/OC -3

S TM- 1/OC -3

T x0MR x

T x0RR x

T x1MR x

T x1RR x

ETS2

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

STM -1/ OC-3

STM -1/ OC-3

STM -1/ OC-3

STM -1/ OC-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

S B1 -0

S B1 -1

S B2 -0

S B2 -1

OPR

Tx/R xFAIL

ST M-1/OC -3

ST M-1/OC -3

ST M-1/OC -3

ST M-1/OC -3

T x0MR x

T x0RR x

T x1MR x

T x1RR x

ETS2

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

GTIC 1

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

10

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

S B1 -0

S B1 -1

S B2 -0

S B2 -1

OPR

Tx/R xFAIL

S TM- 1/OC -3

S TM- 1/OC -3

S TM- 1/OC -3

S TM- 1/OC -3

T x0MR x

T x0RR x

T x1MR x

T x1RR x

ETS2

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

STM -1/ OC-3

STM -1/ OC-3

STM -1/ OC-3

STM -1/ OC-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

S B1 -0

S B1 -1

S B2 -0

S B2 -1

OPR

Tx/R xFAIL

ST M-1/OC -3

ST M-1/OC -3

ST M-1/OC -3

ST M-1/OC -3

T x0MR x

T x0RR x

T x1MR x

T x1RR x

ETS2

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

STMU 0

STMU 2

STMU 4

STMU 6

STMU 8

STMU 10

STMU 12

STMU 14

STMU 16

STMU 18

STMU 20

STMU 22

STMU 24

STMU 26

STMU 28

STMU 30

01

89

1617

2425

3233

4041

4849

5657

6465

7273

8081

8889

9697

104105

112113

120121

!!! Concerns only BSC3i 1000/2000 !!!Current situation - without equipment redundancy i.e. transmission

redundancy, only 1st STM-1/OC-3 interface per ETS2 used

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

SET (active)0

SET (standby)1

ActiveHotlinks (16 pcs)

STMU

GTIC 0

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

10

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

S B1 -0

S B1 -1

S B2 -0

S B2 -1

OPR

Tx/R xFAIL

S TM- 1/OC -3

S TM- 1/OC -3

S TM- 1/OC -3

S TM- 1/OC -3

T x0MR x

T x0RR x

T x1MR x

T x1RR x

ETS2

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

STM -1/ OC-3

STM -1/ OC-3

STM -1/ OC-3

STM -1/ OC-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

S B1 -0

S B1 -1

S B2 -0

S B2 -1

OPR

Tx/R xFAIL

ST M-1/OC -3

ST M-1/OC -3

ST M-1/OC -3

ST M-1/OC -3

T x0MR x

T x0RR x

T x1MR x

T x1RR x

ETS2

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

GTIC 1

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

10

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

S B1 -0

S B1 -1

S B2 -0

S B2 -1

OPR

Tx/R xFAIL

S TM- 1/OC -3

S TM- 1/OC -3

S TM- 1/OC -3

S TM- 1/OC -3

T x0MR x

T x0RR x

T x1MR x

T x1RR x

ETS2

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

STM -1/ OC-3

STM -1/ OC-3

STM -1/ OC-3

STM -1/ OC-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

S B1 -0

S B1 -1

S B2 -0

S B2 -1

OPR

Tx/R xFAIL

ST M-1/OC -3

ST M-1/OC -3

ST M-1/OC -3

ST M-1/OC -3

T x0MR x

T x0RR x

T x1MR x

T x1RR x

ETS2

SB 1-0

SB 1-1

SB 2-0

SB 2-1

OP R

Tx /RxFAIL

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

STM -1/O C-3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

SB1-0

SB1-1

SB2-0

SB2-1

O PR

T x/RxF AIL

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

ST M -1/ OC- 3

Tx0MRx

Tx0RRx

Tx1MRx

Tx1RRx

ETS2

STMU 0

STMU 2

STMU 4

STMU 6

STMU 8

STMU 10

STMU 12

STMU 14

STMU 16

STMU 18

STMU 20

STMU 22

STMU 24

STMU 26

STMU 28

STMU 30

01

89

1617

2425

3233

4041

4849

5657

6465

7273

8081

8889

9697

104105

112113

120121

!!! Concerns only BSC3i 1000/2000 !!!Current situation - without equipment redundancy i.e. transmission

redundancy, only 1st STM-1/OC-3 interface per ETS2 used

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

SET (active)0

SET (standby)1


5 PRE-REQUIREMENTS

5.1 Pre-requirements & Actions needed prior upgrade

The procedure can be implemented only for S16 software onwards. It is recommended to install all availablechange deliveries prior to the upgrade.

IMPORTANT!Re-direct traffic from upgraded ET16 or ETS2 or ETIP plug-in unit (STMU unit) before actual upgrade.Each STMU unit must be handled case by case and PCM areas which are affected during upgrade mayvary. It is possible that new protected STMU unit uses some other STMU unit area or in case of mixedconfiguration the GTIC-1 cartridges track may contain ET16 or ETIP or ETP/ETP-A plug-in units. In thiscase effected ET16 and ETIP units traffic needs to be re-directed, interfaces removed and unit needs tobe deleted (PCM areas released to new STMU unit usage) from hardware database before newconfiguration is created.

BSS Split tool offers automated process to support BSC renewal. This is extremely useful, when older BSC(s) aremodernised to BSC3i(s). This process includes the automation of labor-intensive re-hosting of BTS to new BSC(s)including data and parameter updates to name a few. The downtime of operational BTS(s) is this way minimisedduring re-homing. If re-homing speed is the key driver, more than 100 sites can be moved to the new BSC duringone night by using .XML files for data transfer between the BSC(s) assisted by CM tools (CM Plan Manager, CMEditor and CM Analyser). Further information about BSS Split tools is available from Nokia OSS / NetActrepresentatives.

5.2 Restrictions

The whole GTIC cartridge must be upgraded at the same time.. Also it is required that full capacity of ETS2units is taken in used with this upgrade procedure.

IMPORTANT!During redundancy upgrade, alarm 1340 Hotlink Failure will be raised until the whole upgrade is finishedsuccessfully. Macro asks user to block this alarm during upgrade and unblocking can be done after the last unithas been upgraded. The alarm is caused because of changed cablings and it can be cancelled with correctSW256B DIP-switch settings.

ETS2 plug-in unit which is to be upgraded can handle following interfaces:x A interface (including A-SIGTRAN)x Abis interfacex Gb (both Gb over IP and FR must be taken into account)x BBI (BSC BSC interface for DFCA)

Which ETS2 unit is going to be upgraded to equipment protection, that unit will be blocked, meaning that theinterfaces which the controlling unit is upgraded will be affected. Macro informs user about affected PCM areas(and units handling that area) which are needed to be deleted. After the HW redundancy upgrade has beenfinished successfully for one ETS2 unit pair, the traffic can be re-directed back to old ETS2 unit.

In case of full capacity:When HW redundancy upgrade is done for all ETS2 units, four new ETS2 plug-in units must be added for bothGTIC-0 and GTIC-1 to gain same capacity as in the original configuration.

In case of half capacity:When HW redundancy upgrade is done for all ETS2 units, if same capacity as in the original configuration iswanted, the second interface of the ETS2 plug-in unit must be taken in use.Always, all the existing ETS2 units need to be upgraded at once.


Note!Upgrade must be started from lowest ETS2 index. It is not allowed to use both line protected and HW protectedETS2 units in same GTIC-cartridge.

5.3 Needed documentation

To perform the upgrade successfully, the following documentation is required:x BSC upgrade for SDH/Sonet equipment protection (this document)x Creating and managing BSC hardware (NED)x Cabling Instructions for BSC3i (NED)x Equipment list for BSC3i (NED)x Pre-Processor Program Informationx Jumper Settings of the Plug-in Units in BSC3i and in TCSM3ix Fallback copying instructions of DX200 BSC for BSC (NED)x Technical Support Note: Minimum HW Requirements for BSC S1xx Releasex HIT Users manualx Cabling Instructions for i-series Network Elements

5.4 Needed equipment

To perform the upgrade successfully, the following HW are required:x PC with installed HIT and upgrading macrosx ETS2/ETIP1 card redundancy cables, BSC3i (BSCC-C02 Upgrade Set STM HW Protection) or ETS2/ETIP1

card red. Cables, Flexi BSC (BSCC-E01 Upgrade Set)

x Needed amount of ETS2 plug-in units. Note! In case of STMU full configuration, same amount of ETS2 plug-in units needs to be added to gain same capacity as in the original configuration.

x Initial Flexi BSC3215 ETS2/ETIP1 card red. Cables, (Flexi BSC )x 1000/2000 & upg Flexi: BSC3203 ETS2/ETIP1 card redundancy cables (BSC3i)

5.5 HIT and upgrade macros

5.5.1 System requirements for HIT

HIT 3.4-0 swup is designed to operate on Windows and Linux.The HIT installation requires approximately 20MB disk space, of which the documentation occupies approximately5MB.

5.5.2 Installing HIT

It is necessary to go through this section only if the HIT release 3.4-0 swup has not been installed. If the softwarehas already been installed, proceed to the next section: Installing HIT upgrading macros.

HIT release 3.4-0 swup is delivered in Release Binder found from NOLS (Nokia Online Services). The installationof the software is done by executing the SETUP.EXE -program and following the instructions of the installationprogram.


5.5.3 Installing HIT upgrading macros

After the HIT program has been installed, it is necessary to install the upgrading macros. The upgrading macrosare included in the SW Release Binder which can be found from NOLS (Nokia Online Services). Release bindercontains all the macros used in different upgrades related to the SW Release.

To install the macros into PC, specify the folder to which the macros will be installed, press Unzip and the macroswill be installed.

This zipped executable file includes the whole upgrade macro and the needed directory structure. The only userexecutable file, UPGMAIN.HIT, is extracted to root directory of macro folder HIT settings

5.5.4 HIT settings

Before running HIT, it is recommended that the 'use of FIFO buffers' be turned off from the used communicationsport. This needs to be done, because some PCs communications port handling is unreliable with this settingactive.It is recommended that you contact your local PC support for instructions on how to turn off the use of FIFObuffers.If you are familiar with the settings of the PC, here's an example of how to turn the use of FIFO buffers off. InWindows 2000, the use of FIFO buffers is turned off in the following way:

1. Start Control Panel

2. From Control Panel select System

3. In the System Properties dialog select Hardware/Device Manager

4. In Device Manager select desired communications port (usually COM1) and double-click it

5. In Communications Port (COMx) Properties dialog select Port Settings

6. In Port Settings select Advanced

7. In Advanced Port Settings dialog deactivate the 'Use FIFO buffers' and press OK

8. Close all the opened dialogs by pressing OK

When opening the HIT program the first time, remember to check/create the used device (ref. Hitguide.doc). It isrecommended to use the network element name for the devices.

5.5.5 Connection settings

When opening the HIT program the first time, remember to check/create the used devices (ref. Hitguide.doc).When the macro is started, the available devices are listed to select device to be connected.

Following connection types are supported:x Local connection (COM)x Telnetx SSHx Via Netact (SSH)

Note: in S16 level onwards , via Netact (SSH) is only allowed.

5.5.5.1 Connection settings for Windows

5.5.5.1.1 Configuration example for creating Telnet / SSH / NetAct connection


Select Device > Set Configuration from menu.Following window appears

Select New

Give name for connection and IP address of OMU or NetAct server.Note!DX_TELNET is selected for telnet connection and SSH is selected for SSH connection inType/Protocol: field. Default port for telnet is 23 and for SSH is 22.


In case of Telnet or SSH connection option, select Login,Q/A sheet and define the username and password ofBSC MML session.

Note!In case of NetAct via SSH connection option, select Login sheet and define the username and password ofNetAct communication server and BSC MML session.


Select Terminal sheet and define the MML log file.

If connection type is Telnet, press OK. In SSH connection, define also settings of SSH sheet. Define security level to medium or low level.


After defining SSH related parameters, Press OK.

5.5.5.1.2 Configuration example for creating COM connection

Select Device > Set Configuration from menu.Following window appears


Note! COM connection is selected

Select Login,Q/A sheet and define the username and password of BSC MML session.



Press OK.


5.5.5.2 Connection settings for Linux5.5.5.2.1 Configuration example for creating Telnet / SSH / NetAct connection

Select Edit> Devices > from menuFollowing window appears

Select New

Give name for connection and IP address of OMU or Net Act server.

Note! DX_TELNET is selected for telnet connection and SSH is selected for SSH connection inType/Protocol: field. Default port for telnet is 23 and for SSH is 22.


In case of Telnet or SSH connection option, select Login,Q/A sheet and define the username and password ofBSC MML session.


In case of NetAct via SSH connection option, select Login sheet and define the username and password ofNetAct communication server and BSC MML session.


If connection type is Telnet, press OK.

In SSH connection, define also settings of SSH sheet. Define security level to medium or low level.


After defining SSH related parameters, Press OK.

5.5.5.2.2 Configuration example for creating COM connection

Select Edit> Devices > from menuFollowing window appears


Note! COM connection is selectedSelect Login,Q/A sheet and define the username and password of BSC MML session.


Press OK.


5.5.6 Starting the HIT application / macro executionFirst of all, close List and Macro windows, as those are not needed. In Response window all MML commands areprinted out. It is recommended to keep Messages window as big as possible to able to follow up the macroexecution. The important information is printed out to the messages window.

Open file UPGMAIN.HIT from the location it was extracted and press Green Arrow to start the execution.

At the beginning, the main menu is shown and macro prompts user to choose which upgrade to execute. ClickingCANCEL in main menu aborts the macro execution.


The macro informs user about the chosen procedure with following pop-up window:

Select ini file from the list.

Select target network element from the list.

Note!If NetAct connection has been chosen, choose the correct device which contains IP address definition toNetAct server.


User may choose the location where the macro log files should be saved.

Also, user can define whether to use default log file name or define own.


The status of the current BSC software package is checked. Note that the current software package must be withstatus BU before the actual upgrade can be started. The software status is to be checked with command:

ZWQO:RUN;

Check from the output that all the computer units which are currently in use are running on correct softwarepackage with the status BU. If the software package status is FB or NW, find out the cause for the setting.

If the status of the package is something else than BU, macro gives following pop-up window:

The status can be changed to BU with command:

ZWSC:STAT=NW:STAT=BU;

The active and blocked alarms (DX200 and BTS alarms) can be printed out with following commands:

ZAHO;ZABO;ZEOL;ZEOE;

Alarm printings can be skipped and macro asks user about the wanted action with following pop-up:


Some environment information (status) is checked with following commands:ZQRI;ZIWQ:,OMU:WS=0,;ZDCD;ZUSI:ALL;ZWTI:P:OMU;ZUSI:BCSU;ZWTI:P:GSW,0;ZYE?

This information is gathered for BSC type analysis.

IMPORTANT!If MML session is needed during upgrade, open another MML connection than specified for the upgradeexecution. The same MML connection usage for interrogate or modification purposes may confuse the macroexecution.

The procedure dialog is divided in main chapters, which may also contain sub-chapters. Chapters and their sub-chapters correspond directly to the document. Select the chapter to run and press OK.

Note!In order to complete upgrade successfully, the chapters and steps must be executed in ascending order.


Select a step to run and press OK.


Multi-selections is also possible to do in menu windows. When using multi selections, it is recommended tochoose the steps which do not contain any sub menus. Sub menus cannot be directly seen from macros menuwindow but can be mapped to document structure and verified from there.

If multi-selection contains step which have sub menu, the sub menu window will be opened to user in the correctmacro execution phase. In this case, user should multi-select the sub menu steps and press OK button forexecution of sub steps. Cancel button causes macro to skip all the sub steps.

IMPORTANT!However, when using multi selections the user must always analyse the reasonability. For example in most of theHW procedures which contain manual steps, its not reasonable to use multi-selections. If multi selection is usedwithout sureness of reasonability, it can cause a lot of different kind of problems related macro execution (notactual faults).


6 FALLBACK COPYING OF THE CURRENT PACKAGE

A fallback copying of the running software package must be made before the upgrade.

A fallback copying from the old SW can be made by running macro step Fallback copying of the currentpackage.

Manually, the fallback copying can be made following the document: Fallback copying in BSC. The documentcan be found from NED.


7 BSC CONFIGURATION PRINTOUT (PRE-CHECK)

The information about the BSC configurations and conditions are collected.

Precondition checking is recommended to do during the daytime before the actual upgrade will be started. Thechecking can be made by using the macro (UPGMAIN.HIT) or manually following the instructions from BSCconfiguration printout-document delivered in Release Binder.

For macro execution, choose the BSC configuration printout (pre) step in BSC upgrade for SDH/Sonet equipmentprotection procedure. Follow then the macro execution according the BSC configuration printout document.


8 SDH/SONET EQUIPMENT PROTECTION UPGRADE FOR BSC IN CASE OF STMUFULL CAPACITY CONFIGURATION (2+2)

HW redundant STMU unit will be equipped to corresponding track in other cartridge according to following picture:

Macro upgrades all the STMU units one by one, starting from the lowest STMU index.Each STMU units upgrade may effect to PCM areas which are e.g. already used by ET16/ETIP or some otherSTMU unit. Following table shows the effected PCM areas and units related to each upgraded STMU index.


Fig-1The above figure displays the destination configuration with 9-STMUIMPORTANT!When traffic lost is wanted to stay as minimum as possible, then the order of upgraded STMU indexes should befollowing:1. STMU-02. STMU-83. STMU-24. STMU-105. STMU-46. STMU-127. STMU-68. STMU-149. STMU-24

8.1 Re-host traffic from concerning STMU/ET16/ETIP unit

Move traffic from STMU, ET16, ETIP unit which is going to be upgraded also from up-coming HW protectedSTMU unit. More information about traffic restrictions can be found from chapter 5.1. The traffic can be re-directedback to upgraded STMU unit right after the upgrade has been completed successfully.

Note!Verify the effected PCM area(s) (which needs to be deleted) from Appendix 6, 7, 8. PCM areas are marked withsame colour.

Note!In case of ETPs having the overlapping PCMs with destination STMU, macro will give a pop-up saying the PCMalready in use by ETP cards and these ETP card deletion is not supported.


8.2 Delete old configurations & equipment

In this step, all the old STMU interface configurations and equipment will be deleted. If affected PCM area areused by old configuration in ET16/ETIP, the interface(s) and hardware configuration from these units needs to bedeleted.

Note!If chosen STMU index is between 0-6, skip this interface/unit deletion phase and delete only protectiongroup with ZYWD command. Units are not needed to be deleted.

Delete only interfaces from corresponding STMU unit in GTIC-1 cartridge (if exists) before actual HW redundancyupgrade. More instruction can be found from NED document Creating and managing BSC configuration.


Change GTIC-1 cartridges STMU (or ET16/ETIP) located in track which is going to be upgraded to SE-NH state.

ZUSC:,:BL;ZUSC: ,:TE;ZUSC: ,:SE;ZUSC:,:SE;

When mixed configuration is used and GTIC-1 cartridges track where HW redundant STMU unit will be addedcontains already ET16/ETIP, delete also units interfaces and equipment.

ZWUD:ET,&&:BCSU,;ZWTQ:ET,&&:BCSU,;ZWTV:ET,&&;

Transmission protection groups can be checked with following command:ZYWI;

Delete existing transmission protection groups from STMU(s) which are planned to be upgraded (also from STMUlocated in GTIC-1 cartridge).ZYWD:;

Delete ET equipment (SET) related to STMU unit. If STMU index is between 0-6, the delete only ETs which arerelated to STMU located in GTIC-1 cartridge. If index is something else, delete both cartridge STMU(s) ETgroups.

Note!STMU indexes 0-6 ET (SET) equipment is not needed to be deleted.


Disconnect unit(s)ZWUD:ET,&&:ETS2,0;

Delete plug-in unit(s)ZWTQ:ET,&&:ETS2,0;

Delete unit(s)ZWTV:ET,&&;

If STMU index is between 0-6, delete STMU located in GTIC-1 cartridge in corresponding track.ZWUD:STMU,:ETS2,;ZWTQ:STMU,:ETS2,;ZWTV:STMU,;

8.3 Install redundant ETS2 plug-in unit

In this step, install ETS2 plug-in unit for HW protection usage if unit does not exist. One ETS2 plug-in unit mustexists in same track in both GTIC-cartridges in case of 9-ETS2 install ETS2 plug-in unit for HW protection usagein track 21

8.4 Make cabling changes and install new cables related to MCMU-0

Alarm 1340 (Hotlink failure) is blocked during the whole upgrade. Unblocking can be done after last unit has beenupgraded successfully (in the end of chapter 8.8.1.4 or 8.8.2.4).

Blocking can be done with commandZABB:1340;

Change MCMU-0 and EMB-0 to SE-NH.ZUSC:MCMU,0,TE;ZUSC:MCMU,0,SE;ZUSC:MCMU,0,SE;

ZUSC:EMB,0,TE;ZUSC:EMB,0,SE;ZUSC:EMB,0,SE;

Make cabling changes to MCMU-0 according to appendixes:- MCMU,0 related cablings in BSC3i 1000/2000 or upgraded Flexi BSC

- MCMU,0 related cablings in New Delivery Flexi BSC


8.5 Make DIP-switch changed to SW256B in MCMU,0

Check and make changes to SW256B DIP-switches related to upgraded track according to appendix5.

8.6 Make cabling changes and install new cables related to MCMU-1

Change MCMU-0 and EMB-0 state to WO-EX and MCMU-1 and EMB-1 to SE-NH state.

ZUSC:MCMU,0,SE;ZUSC:MCMU,0,TE;ZUSC:MCMU,0,SP;ZUSC:MCMU,0,WO;

ZUSC:EMB,0,SE;ZUSC:EMB,0,TE;ZUSC:EMB,0,WO;

ZUSC:MCMU,1,TE;ZUSC:MCMU,1,SE;ZUSC:MCMU,1,SE;


Make cabling changes to MCMU according to appendixes:

- MCMU,1 related cablings in BSC3i 1000/2000 or upgraded Flexi BSC

- MCMU,1 related cablings in New Delivery Flexi BSC

8.7 Make DIP-switch changed to SW256B in MCMU-1


Change MCMU-1 state back to SP-EX state.

ZUSC:MCMU,1,SE;ZUSC:MCMU,1,TE;ZUSC:MCMU,1,SP;

8.8 New configuration & equipment with HW protection

In this chapter, all the equipment commands for creating HW redundant STMU unit with corresponding ET unitsare given. In case of manual execution, choose the correct STMU index to be equipped according the picturepresented in the beginning of chapter 8.


8.8.1 BSC3i 1000/2000 or upgraded Flexi BSC

8.8.1.1 Equip new redundant STMU unitsCreate redundant STMU unit

ZWTU:STMU,1:1A5-9;ZWTU:STMU,3:1A5-9;ZWTU:STMU,5:1A5-9;ZWTU:STMU,7:1A5-9;



Create redundant ETS2 plug-in unit

ZWTP:STMU,1:ETS2,0,1::LAPD,8,896,TSL,0&&15;ZWTP:STMU,3:ETS2,0,2::LAPD,8,896,TSL,16&&31;ZWTP:STMU,5:ETS2,0,3::LAPD,8,897,TSL,0&&15;ZWTP:STMU,7:ETS2,0,4::LAPD,8,897,TSL,16&&31;



Connect ETS2 plug-in unit

Note!If equipment protection is in use, the user needs to connect both STMU units to the same controlling unit.

ZWUC:STMU,0:ETS2,0::BCSU,;ZWUC:STMU,2:ETS2,0::BCSU,;ZWUC:STMU,4:ETS2,0::BCSU,;ZWUC:STMU,6:ETS2,0::BCSU,;



ZWUC:STMU,9:ETS2,0::BCSU,;


ZWUC:STMU,11:ETS2,0::BCSU,;ZWUC:STMU,13:ETS2,0::BCSU,;ZWUC:STMU,15:ETS2,0::BCSU,;

8.8.1.2 Create new ET unitsSTMU indexes 0 6 already exist and do not need to be created. In this step, STMU ET sets for GTIC-1 and forGTIC-0 cartridges new STMU units (which are protecting STMU indexes 8-16).

Create ET units

ETSI

ZWTU:ET,1344&&1406:1A5-9:UNIT=STMU,IND=8,IF=0:;ZWTU:ET,1600&&1662:1A5-9:UNIT=STMU,IND=8,IF=1:;




ANSI





Create ET plug-in units

ETSI

ZWTP:ET,1344&&1406:ETS2,0,5::ETT00,8,1344&&1406,TSL,0:;ZWTP:ET,1600&&1662:ETS2,0,5::ETT00,8,1600&&1662,TSL,0:;ZWTP:ET,1664&&1726:ETS2,0,6::ETT00,8,1664&&1726,TSL,0:;ZWTP:ET,1728&&1790:ETS2,0,6::ETT00,8,1728&&1790,TSL,0:;ZWTP:ET,1792&&1854:ETS2,0,7::ETT00,8,1792&&1854,TSL,0:;ZWTP:ET,1856&&1918:ETS2,0,7::ETT00,8,1856&&1918,TSL,0:;ZWTP:ET,1920&&1982:ETS2,0,8::ETT00,8,1920&&1982,TSL,0:;ZWTP:ET,1984&&2046:ETS2,0,8::ETT00,8,1984&&2046,TSL,0:;

ANSI

ZWTP:ET,2720&&2803:ETS2,0,5::ETT00,8,2720&&2803,TSL,0:;ZWTP:ET,2804&&2887:ETS2,0,5::ETT00,8,2804&&2887,TSL,0:;ZWTP:ET,2888&&2971:ETS2,0,6::ETT00,8,2888&&2971,TSL,0:;ZWTP:ET,2972&&3055:ETS2,0,6::ETT00,8,2972&&3055,TSL,0:;ZWTP:ET,3056&&3139:ETS2,0,7::ETT00,8,3056&&313,TSL,0:;


ZWTP:ET,3140&&3223:ETS2,0,7::ETT00,8,3140&&3223,TSL,0:;ZWTP:ET,3224&&3307:ETS2,0,8::ETT00,8,3224&&3307,TSL,0:;ZWTP:ET,3308&&3391:ETS2,0,8::ETT00,8,3308&&3391,TSL,0:;

Connect ET plug-in units (manually):

ETSI

ZWUC:ET,1344&&1406:ETS2,0:IF=:BCSU,:;ZWUC:ET,1600&&1662:ETS2,0:IF=:BCSU,:;ZWUC:ET,1664&&1726:ETS2,0:IF=:BCSU,:;ZWUC:ET,1728&&1790:ETS2,0:IF=:BCSU,:;ZWUC:ET,1792&&1854:ETS2,0:IF=:BCSU,:;ZWUC:ET,1856&&1918:ETS2,0:IF=:BCSU,:;ZWUC:ET,1920&&1982:ETS2,0:IF=:BCSU,:;ZWUC:ET,1984&&2046:ETS2,0:IF=:BCSU,:;

ANSI

ZWUC:ET,2720&&2803:ETS2,0:IF=:BCSU,:;ZWUC:ET,2804&&2887:ETS2,0:IF=:BCSU,:;ZWUC:ET,2888&&2971:ETS2,0:IF=:BCSU,:;ZWUC:ET,2972&&3055:ETS2,0:IF=:BCSU,:;ZWUC:ET,3056&&3139:ETS2,0:IF=:BCSU,:;ZWUC:ET,3140&&3223:ETS2,0:IF=:BCSU,:;ZWUC:ET,3224&&3307:ETS2,0:IF=:BCSU,:;ZWUC:ET,3308&&3391:ETS2,0:IF=:BCSU,:;

8.8.1.3 Create new protection groupCreate new HW protection groups

ANSI:

ZYWC:,,,APS:0,4;ZYWC:,,,APS:2,6;


ZYWC:,,,APS:16,20;ZYWC:,,,APS:18,22;

ZYWC:,,,APS:24,28;ZYWC:,,,APS:26,30;

ZYWC:,,,APS:32,36;ZYWC:,,,APS:34,38;

ZYWC:,,,APS:40,44;ZYWC:,,,APS:42,46;

ZYWC:,,,APS:48,52;ZYWC:,,,APS:50,54;

ZYWC:,,,APS:56,60;ZYWC:,,,APS:58,62;

ETSI:

ZYWC:,,,MSP:0,4;ZYWC:,,,MSP:2,6;



ZYWC:,,,MSP:16,20;ZYWC:,,,MSP:18,22;

ZYWC:,,,MSP:24,28;ZYWC:,,,MSP:26,30;

ZYWC:,,,MSP:32,36;ZYWC:,,,MSP:34,38;

ZYWC:,,,MSP:40,44;ZYWC:,,,MSP:42,46;

ZYWC:,,,MSP:48,52;ZYWC:,,,MSP:50,54;

ZYWC:,,,MSP:56,60;ZYWC:,,,MSP:58,62;

8.8.1.4 Change new STMU units to WO-EX stateNote!

STMU indexes 0-6 are already in WO-EX state and this step can be skipped.

Change STMU units state back to WO-EX state with following commands:

ZUSC:STMU,:SE;ZUSC:STMU,:TE;ZUSC:STMU,:WO;

IMPORTANT!

If more STMU units are planned to be upgraded, do the chapters 8.1-8.5 again. In case of last STMUupgrade, remember to unblock the alarm 1340 manually.

Unblock alarm 1340 (Hotlink failure) with following command:

ZABU:1340;

8.8.2 New Delivery Flexi BSC

8.8.2.1 Equip new redundant STMU units

Create redundant STMU unit(s)


ZWTU:STMU,8:1A2-3;ZWTU:STMU,10:1A2-3;ZWTU:STMU,12:1A2-3;


ZWTU:STMU,14:1A2-3;ZWTU:STMU,25:1A2-3; New requirement STMU 9th

ZWTU:STMU,9:1A1-3;ZWTU:STMU,11:1A1-3;ZWTU:STMU,13:1A1-3;ZWTU:STMU,15:1A1-3;ZWTU:STMU,24:1A1-3; New requirement STMU 9th

Create redundant ETS2 plug-in unit(s)


ZWTP:STMU,8:ETS2,0,14::LAPD,8,386,TSL,0&&15;ZWTP:STMU,10:ETS2,0,15::LAPD,8,386,TSL,16&&31;ZWTP:STMU,12:ETS2,0,16::LAPD,8,387,TSL,0&&15;ZWTP:STMU,14:ETS2,0,17::LAPD,8,387,TSL,16&&31;ZWTP:STMU,24:ETS2,0,21::LAPD,8,397,TSL,0&&15; New requirement STMU 9th

ZWTP:STMU,9:ETS2,0,14::LAPD,8,394,TSL,0&&15;ZWTP:STMU,11:ETS2,0,15::LAPD,8,394,TSL,16&&31;ZWTP:STMU,13:ETS2,0,16::LAPD,8,395,TSL,0&&15;ZWTP:STMU,15:ETS2,0,17::LAPD,8,395,TSL,16&&31;ZWTP:STMU,25:ETS2,0,21::LAPD,8,389,TSL,0&&15; New requirement STMU 9th

Connect ETS2 plug-in unit manually to needed interface.

Note!If equipment protection is in use, the user need to connect both STMU units to the same controlling unit.


ZWUC:STMU,8:ETS2,0::BCSU,;ZWUC:STMU,10:ETS2,0::BCSU,;ZWUC:STMU,12:ETS2,0::BCSU,;ZWUC:STMU,14:ETS2,0::BCSU,;ZWUC:STMU,24:ETS2,0::BCSU,; New requirement STMU 9th

ZWUC:STMU,9:ETS2,0::BCSU,;ZWUC:STMU,11:ETS2,0::BCSU,;ZWUC:STMU,13:ETS2,0::BCSU,;ZWUC:STMU,15:ETS2,0::BCSU,;ZWUC:STMU,25:ETS2,0::BCSU,; New requirement STMU 9th

8.8.2.2 Create new ET unitsSTMU indexes 0 6 already exists and does not needed to be created. In this step, STMU ET sets for GTIC-1and for GTIC-0/ETC-0/ETC-2 cartridges new STMU units (which are protecting STMU indexes 8-16).

Create ET units


ETSI





ZWTU:ET,256&&318:1A1-3:UNIT=STMU,IND=24,IF=0:; New requirement STMU9thZWTU:ET,320&&382:1A1-3:UNIT=STMU,IND=24,IF=1:;

ANSIZWTU:ET,2720&&2803:1A2-0:UNIT=STMU,IND=8,IF=0:;ZWTU:ET,2804&&2887:1A2-0:UNIT=STMU,IND=8,IF=1:;




ZWTU:ET, 3392&&3475:1A1-0:UNIT=STMU,IND=24,IF=0:; New requirement STMU9thZWTU:ET, 3392&&3475:1A1-0:UNIT=STMU,IND=24,IF=1:;

Create ET plug-in units

ETSI

ZWTP:ET,1920&&1982:ETS2,0,14::ETT00,8,1920&&1982,TSL,0:;ZWTP:ET,1984&&2046:ETS2,0,14::ETT00,8,1984&&2046,TSL,0:;ZWTP:ET,768&&830:ETS2,0,15::ETT00,8,768&&830,TSL,0:;ZWTP:ET,832&&894:ETS2,0,15::ETT00,8,832&&894,TSL,0:;ZWTP:ET,1024&&1086:ETS2,0,16::ETT00,8,1024&&1086,TSL,0:;ZWTP:ET,1088&&1150:ETS2,0,16::ETT00,8,1088&&1150,TSL,0:;ZWTP:ET,512&&574:ETS2,0,17::ETT00,8,512&&574,TSL,0:;ZWTP:ET,576&&638:ETS2,0,17::ETT00,8,576&&638,TSL,0:;ZWTP:ET,256&&318:ETS2,0,21::ETT00,8,256&&318,TSL,0:; New requirement STMU9thZWTP:ET,320&&382:ETS2,0,21::ETT00,8,320&&382,TSL,0:;

ANSI

ZWTP:ET,2720&&2803:ETS2,0,14::ETT00,8,2720&&2803,TSL,0:;ZWTP:ET,2804&&2887:ETS2,0,14::ETT00,8,2804&&2887,TSL,0:;ZWTP:ET,2888&&2971:ETS2,0,15::ETT00,8,2888&&2971,TSL,0:;ZWTP:ET,2972&&3055:ETS2,0,15::ETT00,8,2972&&3055,TSL,0:;ZWTP:ET,3056&&3139:ETS2,0,16::ETT00,8,3056&&3139,TSL,0:;ZWTP:ET,3140&&3223:ETS2,0,16::ETT00,8,3140&&3223,TSL,0:;ZWTP:ET,3224&&3307:ETS2,0,17::ETT00,8,3224&&3307,TSL,0:;ZWTP:ET,3308&&3391:ETS2,0,17::ETT00,8,3308&&3391,TSL,0:;ZWTP:ET, 3392&&3475:ETS2,0,21::ETT00,8,3392&&3475,TSL,0:; New requirement STMU9th ZWTP:ET, 3476&&3559:ETS2,0,21::ETT00,8,3476&&3559,TSL,0:;


Connect ET plug-in units

ETSI

ZWUC:ET,1920&&1982:ETS2,0:IF=:BCSU,:;ZWUC:ET,1984&&2046:ETS2,0:IF=:BCSU,:;ZWUC:ET,768&&830:ETS2,0:IF=:BCSU,:;ZWUC:ET,832&&894:ETS2,0:IF=:BCSU,:;ZWUC:ET,1024&&1086:ETS2,0:IF=:BCSU,:;ZWUC:ET,1088&&1150:ETS2,0:IF=:BCSU,:;ZWUC:ET,512&&574:ETS2,0:IF=:BCSU,:;ZWUC:ET,576&&638:ETS2,0:IF=:BCSU,:;ZWUC:ET,256&&318:ETS2,0:IF=:BCSU,:; New requirement STMU9thZWUC:ET,320&&382:ETS2,0:IF=:BCSU,:;

ANSI

ZWUC:ET,2720&&2803:ETS2,0:IF=:BCSU,:;ZWUC:ET,2804&&2887:ETS2,0:IF=:BCSU,:;ZWUC:ET,2888&&2971:ETS2,0:IF=:BCSU,:;ZWUC:ET,2972&&3055:ETS2,0:IF=:BCSU,:;ZWUC:ET,3056&&3139:ETS2,0:IF=:BCSU,:;ZWUC:ET,3140&&3223:ETS2,0:IF=:BCSU,:;ZWUC:ET,3224&&3307:ETS2,0:IF=:BCSU,:;ZWUC:ET,3308&&3391:ETS2,0:IF=:BCSU,:;ZWUC:ET,3392&&3475:ETS2,0:IF=:BCSU,:; New requirement STMU9thZWUC:ET,3476&&3559:ETS2,0:IF=:BCSU,:;

8.8.2.3 Create new HW protection setsCreate HW protection sets

ETSI:



ZYWC:,,,MSP:16,20;ZYWC:,,,MSP:18,22;

ZYWC:,,,MSP:24,28;ZYWC:,,,MSP:26,30;

ZYWC:,,,MSP:32,36;ZYWC:,,,MSP:34,38;

ZYWC:,,,MSP:40,44;ZYWC:,,,MSP:42,46;

ZYWC:,,,MSP:48,52;ZYWC:,,,MSP:50,54;

ZYWC:,,,MSP:56,60;ZYWC:,,,MSP:58,62;

ZYWC:,,,MSP:96,100;ZYWC:,,,MSP:98,102;


ANSI:



ZYWC:,,,APS:16,20;ZYWC:,,,APS:18,22;

ZYWC:,,,APS:24,28;ZYWC:,,,APS:26,30;

ZYWC:,,,APS:32,36;ZYWC:,,,APS:34,38;

ZYWC:,,,APS:40,44;ZYWC:,,,APS:42,46;

ZYWC:,,,APS:48,52;ZYWC:,,,APS:50,54;

ZYWC:,,,APS:56,60;ZYWC:,,,APS:58,62;

ZYWC:,,,ASP:96,100;ZYWC:,,,ASP:98,102;

8.8.2.4 Change new STMU units to WO-EX stateNote!

STMU indexes 0-6 are already in WO-EX state and this step can be skipped.

Change both GTIC cardridges STMU to WO-EX state


IMPORTANT!

If more STMU units are planned to be upgraded, do the chapters 8.1-8.5 again. In case of last STMUupgrade, remember to unblock the alarm 1340 manually.

Unblock alarm 1340 (Hotlink failure) with following command:

ZABU:1340;

8.9 MCMU diagnostic

In this step, after all the MCMU diagnostic is run.


Note!MCMU diagnostic to one unit can take 40-60 minutes.

Change the MCMU-0 to TE-EX:ZUSC:MCMU,0:SP;ZUSC:MCMU,0:TE;

Run diagnostic to MCMU-0:ZUDU:MCMU,0;

After successful diagnostic change the MCMU-0 to WO-EX state:ZUSC:MCMU,0:SP;ZUSC:MCMU,0:WO;

Change the MCMU-1 to TE-EX:ZUSC:MCMU,1:SP;ZUSC:MCMU,1:TE;

Run diagnostic to MCMU-1:ZUDU:MCMU,1;

After successful diagnostic change the MCMU-1 to SP-EX state:ZUSC:MCMU,1:SP;


9 SDH/SONET EQUIPMENT PROTECTION UPGRADE FOR BSC IN CASE OF STMUHALF CAPACITY CONFIGURATION (1+1)

HW redundant STMU unit will be equipped to corresponding track in other cartridge according to following picture:

Macro upgrades all the existing STMU units one by one. The upgrade starts upgrading STMU indexes 0-6 inascending order, the other four STMU indexes (8-14) will be upgraded using descending order.

Each STMU units upgrade may effect to PCM areas which are e.g. already used by ET16/ETIP or some otherSTMU unit. Following table shows the effected PCM areas and units related to each upgraded STMU index.

In case of STMU half configuration, the STMU units must be handled separately. This is needed because of theSTMU indexes 8-14 needs different deletions than the first STMU indexes 0-6. Also STMU plug-in units needs tobe deleted for STMU indexes 8-14, and created again with new indexes to GTIC-1 cartridge.

IMPORTANT!When traffic lost is wanted to stay as minimum as possible, then the order of upgraded STMU indexes should befollowing:1. STMU-02. STMU-23. STMU-44. STMU-65. STMU-146. STMU-127. STMU-10


8. STMU-8

9.1 In case of STMU indexes between 0 to 6

9.1.1 Re-host traffic from concerning STMU/ET16/ETIP unit

Move traffic from STMU unit which is going to be upgraded also from up-coming HW protected STMU unit oraffected ET16/ETIP unit (see table above). More information about traffic restrictions can be found from chapter5.1. The traffic can be re-directed back to upgraded STMU unit right after the upgrade has been completedsuccessfully.



9.1.2 Delete interfaces from affected STMU, ET16/ETIP units

In this step, delete interfaces from affected STMU, ET16 or ETIP units (see tables in Appendix 6, 7, 8). Interfacesrelated to STMU unit indexes 0-6, are not needed to be deleted.

More instruction can be found from NED document Creating and managing BSC configuration.

9.1.3 Change STMU units states to SE-NH and delete ET16/ETIP equipment

In this step the STMU unit, which is going to be upgraded, is changed to SE-NH state. Also affected STMU unit(s)state needs to be changed to SE-NH. See effected STMU units from tables presented in Appendix 6, 7, 8.


If ET16 units exist in effected tracks (see table in chapter 9), the hardware from equipment database is deletedwith following commands:

ZWUD:ET,:BCSU,;ZWTQ:ET,:BCSU,;ZWTV:ET,;

9.1.4 Remove old protection groups

In this step old protection group from STMU to be upgraded will be deleted. Also affected STMU units protectiongroup needs to be deleted.


Delete existing transmission protection groups with following command:ZYWD:;


9.1.5 Delete ET sets from GTIC-0 units

In this step, delete old ET set configurations from affected STMU units (see table in Appendix 6, 7, 8).

Delete ET equipment related to STMU unit(s) with following commands:

Disconnect unitsZWUD:ET,&&:ETS2,0;

Delete plug-in unitsZWTQ:ET,&&:ETS2,0;

Delete unitsZWTV:ET,&&;

9.1.6 Make cabling changes and install new cables related to MCMU,0

Alarm 1340 (Hotlink failure) is blocked during the whole upgrade. Unblocking can be done after last unit has beenupgraded successfully (in the end of chapter 8.8.1.4 or 8.8.2.4).

Blocking can be done with commandZABB:1340;

Change MCMU-0 and EMB-0 state to SE-NH.ZUSC:MCMU,0,TE;ZUSC:MCMU,0,SE;ZUSC:MCMU,0,SE;

ZUSC:EMB,0,TE;ZUSC:EMB,0,SE;ZUSC:EMB,0,SE;Make cabling changes to MCMU-0 according to appendixes:- MCMU,0 related cablings in BSC3i 1000/2000 or upgraded Flexi BSC

Note: In 1+1 configuration please refer cablings for BSC3i 1000/2000.

9.1.7 Make DIP-switch changes to SW256B in MCMU,0


9.1.8 Make cabling changes and install new cables related to MCMU-1

Change MCMU-0 and EMB-0 state to WO-EX and MCMU-1 and EMB-1to SE-NH state.

ZUSC:MCMU,0,SE;ZUSC:MCMU,0,TE;ZUSC:MCMU,0,SP;ZUSC:MCMU,0,WO;

ZUSC:EMB,0,SE;ZUSC:EMB,0,TE;ZUSC:EMB,0,WO;

ZUSC:MCMU,1,TE;ZUSC:MCMU,1,SE;


ZUSC:MCMU,1,SE;


Make cabling changes to MCMU according to appendixes:- MCMU,1 related cablings in BSC3i 1000/2000 or upgraded Flexi BSC

Note: In 1+1 configuration please refer cablings for BSC3i 1000/2000.

9.1.9 Make DIP-switch changes to SW256B in MCMU-1


Change MCMU-1 and EMB-1 state back to SP-EX state.

ZUSC:MCMU,1,SE;ZUSC:MCMU,1,TE;ZUSC:MCMU,1,SP;

ZUSC:EMB,1,SE;ZUSC:EMB,1,TE;ZUSC:EMB,1,SP;

9.1.10 Create new ET sets for upgraded STMU unit

In this step, the new ET sets will be created for STMU which is upgraded. STMU unit and plug-in unit alreadyexists (and already connected to some interface) and does not needed to be created.

Create ET set units with following commands:ETSIZWTU:ET,64&&126:1A5-6:UNIT=STMU,IND=0,IF=0:;ZWTU:ET,192&&254:1A5-6:UNIT=STMU,IND=0,IF=1:;




ANSIZWTU:ET,2048&&2131:1A5-6:UNIT=STMU,IND=0,IF=0:;ZWTU:ET,2132&&2215:1A5-6:UNIT=STMU,IND=0,IF=1:;



ZWTU:ET,2552&&2635:1A5-6:UNIT=STMU,IND=6,IF=0:;


ZWTU:ET,2636&&2719:1A5-6:UNIT=STMU,IND=6,IF=1:;

Create ET plug-in unitsETSIZWTP:ET,64&&126:ETS2,0,1::ETT00,8,64&&126,TSL,0:;ZWTP:ET,192&&254:ETS2,0,1::ETT00,8,192&&254,TSL,0:;ZWTP:ET,320&&382:ETS2,0,2::ETT00,8,320&&382,TSL,0:;ZWTP:ET,448&&510:ETS2,0,2::ETT00,8,448&&510,TSL,0:;ZWTP:ET,1088&&1150:ETS2,0,3::ETT00,8,1088&&1150,TSL,0:;ZWTP:ET,1216&&1278:ETS2,0,3::ETT00,8,1216&&1278,TSL,0:;ZWTP:ET,1408&&1470:ETS2,0,4::ETT00,8,1408&&1470,TSL,0:;ZWTP:ET,1472&&1534:ETS2,0,4::ETT00,8,1472&&1534,TSL,0:;

ANSIZWTP:ET,2048&&2131:ETS2,0,1::ETT00,8,2048&&2131,TSL,0:;ZWTP:ET,2132&&2215:ETS2,0,1::ETT00,8,2132&&2215,TSL,0:;ZWTP:ET,2216&&2299:ETS2,0,2::ETT00,8,2216&&2299,TSL,0:;ZWTP:ET,2300&&2383:ETS2,0,2::ETT00,8,2300&&2383,TSL,0:;ZWTP:ET,2384&&2467:ETS2,0,3::ETT00,8,2384&&2467,TSL,0:;ZWTP:ET,2468&&2551:ETS2,0,3::ETT00,8,2468&&2551,TSL,0:;ZWTP:ET,2552&&2635:ETS2,0,4::ETT00,8,2552&&2635,TSL,0:;ZWTP:ET,2636&&2719:ETS2,0,4::ETT00,8,2636&&2719,TSL,0:;

Connect ET plug-in units (manually):ETSIZWUC:ET,64&&126:ETS2,0:IF=:BCSU,:;ZWUC:ET,192&&254:ETS2,0:IF=:BCSU,:;ZWUC:ET,320&&382:ETS2,0:IF=:BCSU,:;ZWUC:ET,448&&510:ETS2,0:IF=:BCSU,:;ZWUC:ET,1088&&1150:ETS2,0:IF=:BCSU,:;ZWUC:ET,1216&&1278:ETS2,0:IF=:BCSU,:;ZWUC:ET,1408&&1470:ETS2,0:IF=:BCSU,:;ZWUC:ET,1472&&1534:ETS2,0:IF=:BCSU,:;

ANSIZWUC:ET,2048&&2131:ETS2,0:IF=:BCSU,:;ZWUC:ET,2132&&2215:ETS2,0:IF=:BCSU,:;ZWUC:ET,2216&&2299:ETS2,0:IF=:BCSU,:;ZWUC:ET,2300&&2383:ETS2,0:IF=:BCSU,:;ZWUC:ET,2384&&2467:ETS2,0:IF=:BCSU,:;ZWUC:ET,2468&&2251:ETS2,0:IF=:BCSU,:;ZWUC:ET,2552&&2635:ETS2,0:IF=:BCSU,:;ZWUC:ET,2636&&2719:ETS2,0:IF=:BCSU,:;

9.1.11 Change upgraded STMU unit to WO-EX state

In this step, the upgraded STMU unit needs to be changed to WO-EX state. The up-coming redundant STMU unitwill be upgraded in later phase.

Change upgraded STMU to WO-EX state


After unit is up, the traffic through upgraded STMU unit should start normally.


Go back to chapter 9.1 and start the upgrade for next STMU index until all even index STMU units hasbeen upgraded successfully.

Odd STMU indexes 1-15 will be created after even units has been finished (chapter 9.5).

9.2 In case of STMU indexes between 8 to 16

Note!STMU units must be upgraded in descending order.

9.2.1 Re-host traffic from concerning STMU/ET16/ETIP unit

Move traffic from STMU unit which is going to be upgraded also from up-coming HW protected STMU unit oraffected ET16/ETIP unit (see table above). More information about traffic restrictions can be found from chapter5.1. The traffic can be re-directed back to upgraded STMU unit right after the upgrade has been completedsuccessfully.



9.2.2 Delete interfaces from affected STMU, ET16/ETIP units

In this step, delete interfaces from affected STMU, ET16 or ETIP units (see tables in Appendix 6, 7, 8).

More instruction can be found from NED document Creating and managing BSC configuration.

9.2.3 Change STMU units states to SE-NH and delete ET16/ETIP equipment

In this step the STMU unit, which is going to be upgraded, is changed to SE-HN state. Also affected STMU unit(s)state needs to be changed to SE-NH. See effected STMU units from tables presented in Appendix 6, 7, 8.


If ET16 plug-in units exist in effected tracks (see table in chapter 9), the hardware from equipment database isdeleted with following commands:

ZWUD:ET,:BCSU,;ZWTQ:ET,:BCSU,;ZWTV:ET,;


9.2.4 Remove old protection groups

In this step old protection group from STMU to be upgraded will be deleted. Also affected STMU units protectiongroup needs to be deleted.


Delete existing transmission protection groups with following command:ZYWD:;

9.2.5 Delete ET sets from GTIC-1 units

In this step, delete old ET set configurations from STMU to be upgraded and affected STMU unit(s) (see table inchapter 9).

Delete ET equipment related to STMU unit(s) with following commands:

Disconnect unitsZWUD:ET,&&:ETS2,0;

Delete plug-in unitsZWTQ:ET,&&:ETS2,0;

Delete unitsZWTV:ET,&&;

9.2.6 Delete old STMU unit equipment

In this step, delete old STMU unit equipment from STMU to be upgraded in GTIC-1 cartridge. Delete alsoequipment from same track in GTIC-0 cartridge.Deletion can be done with following commands:

ZWUD:STMU,:ETS2,;ZWTQ:STMU,:ETS2,;ZWTV:STMU,;

9.2.7 Make cabling changes and install new cables related to MCMU,0

Alarm 1340 (H

BSC3i Upgrade for SDH_Sonet Equipment Protection_ver1_6

Documents

prior upgrade

upgrade macro

bsc3i equipment

environmental policy

nokia solutions

adverse environmental

environmental serviceswe

requirements actions