BSC3i_TCSM3i Upgrade for SDH_Sonet Equipment Protection (S12 - S14 TCSM HW)_ver1_4

DN09114099BSC3i/TCSM3iupgradeforSDH/Sonetequipmentprotection(S12S14TCSMHW)Copyright2013NokiaSolutionsandNetworks.Allrightsreserved.CONFIDENTIALAPPROVED1.41 (120)

BSC3i/TCSM3i upgradefor SDH/Sonet equipmentprotection (S12 - S14TCSM HW)Release Delivery: HW UpgradeProduct Family: Radio ControllersProduct: BSC3i 1000/2000, UpgradedFlexi BSCRelease: S16 onwards

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 .................................................................................................................................................. 62 Scope of applications .............................................................................................................................. 73 Using the document ................................................................................................................................ 8

3.1 General info ....................................................................................................................................................... 83.2 Upgrade macro .................................................................................................................................................. 8

3.2.1 Structure ...................................................................................................................................... 83.2.2 Communication ............................................................................................................................ 93.2.3 Log files ..................................................................................................................................... 10

4 Introduction ........................................................................................................................................... 124.1 Combined TCSM3i equipment before upgrade.................................................................................................. 14

4.1.1 TCSA-0 cabinet .......................................................................................................................... 144.1.2 TCSA-1 cabinet .......................................................................................................................... 154.1.3 TCSA-2 cabinet .......................................................................................................................... 15

4.2 Combined TCSM3i equipment after upgrade .................................................................................................... 164.2.1 TCSA-0 cabinet .......................................................................................................................... 164.2.2 TCSA-1 cabinet .......................................................................................................................... 164.2.3 TCSA-2 cabinet .......................................................................................................................... 17

5 Pre-requirements .................................................................................................................................. 185.1 Pre-requirements & Actions needed prior upgrade ............................................................................................ 185.2 Restrictions ..................................................................................................................................................... 185.3 Needed documentation .................................................................................................................................... 195.4 Needed equipment .......................................................................................................................................... 195.5 HIT and upgrade macros.................................................................................................................................. 20

5.5.1 System requirements for HIT ...................................................................................................... 205.5.2 Installing HIT .............................................................................................................................. 205.5.3 Installing HIT upgrading macros .................................................................................................. 205.5.4 HIT settings................................................................................................................................ 215.5.5 Connection settings .................................................................................................................... 215.5.6 Starting the HIT application / macro execution ............................................................................. 41

6 Fallback copying of the current package ................................................................................................ 497 BSC configuration printout (pre-check) .................................................................................................. 508 SDH/Sonet equipment protection upgrade for combined TCSM3i (OFFLINE) ........................................ 51

8.1 Choose TCSA cabinet to be upgraded .............................................................................................................. 538.2 Move traffic from STMU which will be upgraded ................................................................................................ 538.3 Delete old configurations & equipment .............................................................................................................. 538.4 Install redundant ETS2 plug-in unit(s) ............................................................................................................... 548.5 Make cabling changes and install new cables ................................................................................................... 548.6 New configuration & equipment with HW protection .......................................................................................... 54

8.6.1 BSC3i 1000/2000 or upgraded Flexi BSC.................................................................................... 558.6.2 New Delivery Flexi BSC.............................................................................................................. 63

9 SDH/Sonet equipment protection upgrade for combined TCSM3i (LIVE) ............................................... 719.1 TCSA-0 ........................................................................................................................................................... 73

9.1.1 Remove protection groups .......................................................................................................... 739.1.2 Remove interfaces from SET-144 and disconnect effected TCSM(s) ............................................ 739.1.3 Change SET-144 to SE-NH state ................................................................................................ 739.1.4 Delete SET-144 ......................................................................................................................... 739.1.5 Create SET-138 ......................................................................................................................... 749.1.6 Make cabling changes ................................................................................................................ 749.1.7 Change SET-138 to WO-EX state ............................................................................................... 759.1.8 Create interface(s) from SET-138 and connect related TCSM(s) .................................................. 759.1.9 Remove interfaces from SET-146 and disconnect effected TCSM(s) ............................................ 759.1.10 Change STMU-36 SE-NH state .................................................................................................. 759.1.11 Delete SET-146 and STMU-36 ................................................................................................... 769.1.12 Insert a new ETS2 plug-in unit to GTIC-2 and GTIC-3 track 7 ...................................................... 769.1.13 Create STMU-36 to GTIC-2 ........................................................................................................ 76


9.1.14 Create SET-144 ......................................................................................................................... 779.1.15 Make cabling changes ................................................................................................................ 779.1.16 Create interface(s) from SET-144 and connect related TCSM(s) .................................................. 789.1.17 Change STMU-36 to WO-EX state .............................................................................................. 789.1.18 Remove interfaces from SET-152 and disconnect effected TCSM(s) ............................................ 789.1.19 Change STMU-38 SE-NH state .................................................................................................. 789.1.20 Delete SET-152 ......................................................................................................................... 799.1.21 Create SET-146 ......................................................................................................................... 799.1.22 Make cabling changes ................................................................................................................ 809.1.23 Create interface(s) from SET-146 and connect related TCSM(s) .................................................. 809.1.24 Change SET-146 to WO-EX state ............................................................................................... 819.1.25 Delete STMU-38 ........................................................................................................................ 819.1.26 Create STMU-33/35/37 .............................................................................................................. 819.1.27 Install new cables and modules .................................................................................................. 829.1.28 Create protection groups ............................................................................................................ 839.1.29 Change STMU-33/35/37 to WO-EX ............................................................................................ 84

9.2 TCSA-1 ........................................................................................................................................................... 849.2.1 Remove protection groups .......................................................................................................... 849.2.2 Remove interfaces from SET-160, SET-162 and disconnect effected TCSM(s) ............................ 849.2.3 Change STMU-40 SE-NH state .................................................................................................. 859.2.4 Delete SET-160 and SET- 162 ................................................................................................... 859.2.5 Delete STMU-40 ........................................................................................................................ 869.2.6 Create STMU-38 to GTIC-5 ........................................................................................................ 869.2.7 Create SET-152 and SET-154 .................................................................................................... 869.2.8 Create interface(s) from SET-152, SET-154 and connect related TCSM(s)................................... 879.2.9 Change STMU-38 to WO-EX ...................................................................................................... 879.2.10 Remove interfaces from SET-168 and disconnect effected TCSM(s) ............................................ 879.2.11 Change STMU-42 SE-NH state .................................................................................................. 879.2.12 Delete SET-168 ......................................................................................................................... 879.2.13 Delete STMU-42 ........................................................................................................................ 889.2.14 Create STMU-40 ........................................................................................................................ 889.2.15 Create SET-160 ......................................................................................................................... 899.2.16 Create interface(s) from SET-160 and connect related TCSM(s) .................................................. 899.2.17 Change STMU-40 to WO-EX ...................................................................................................... 899.2.18 Change SET-176 to SE-NH state ................................................................................................ 899.2.19 Delete SET-176 ......................................................................................................................... 909.2.20 Create SET-162 ......................................................................................................................... 909.2.21 Make cabling changes ................................................................................................................ 919.2.22 Change SET-162 to WO-EX state ............................................................................................... 919.2.23 Create interface(s) from SET-162 and connect related TCSM(s) .................................................. 919.2.24 Remove interfaces from SET-178 and disconnect effected TCSM(s) ............................................ 929.2.25 Change STMU-44 to SE-NH ....................................................................................................... 929.2.26 Delete SET-178 ......................................................................................................................... 929.2.27 Delete STMU-44 ........................................................................................................................ 929.2.28 Insert a new ETS2 plug-in unit to GTIC-5 and GTIC-6 track 7 ...................................................... 939.2.29 Create STMU-42 to GTIC-5 ........................................................................................................ 939.2.30 Create SET-168 ......................................................................................................................... 939.2.31 Make cabling changes ................................................................................................................ 949.2.32 Create interface(s) from SET-168 and connect related TCSM(s) .................................................. 949.2.33 Change STMU-42 WO-EX state ................................................................................................. 949.2.34 Remove interfaces from SET-184 and disconnect effected TCSM(s) ............................................ 949.2.35 Change STMU-46 to SE-NH state............................................................................................... 959.2.36 Delete SET-184 ......................................................................................................................... 959.2.37 Create SET-170 ......................................................................................................................... 959.2.38 Make cabling changes ................................................................................................................ 969.2.39 Create interface(s) from SET-170 and connect related TCSM(s) .................................................. 969.2.40 Change SET-170 to WO-EX state ............................................................................................... 969.2.41 Delete STMU-46 ........................................................................................................................ 979.2.42 Create STMU-39/41/43 .............................................................................................................. 979.2.43 Install new cables and modules .................................................................................................. 98


9.2.44 Create protection groups ............................................................................................................ 999.2.45 Change STMU-39/41/43 to WO-EX ............................................................................................ 99

9.3 TCSA-2 ......................................................................................................................................................... 1009.3.1 Remove protection groups ........................................................................................................ 1009.3.2 Remove interfaces from SET-192, SET-194 and disconnect effected TCSM(s) .......................... 1009.3.3 Change STMU-48 SE-NH state ................................................................................................ 1009.3.4 Delete SET-192 and SET- 194 ................................................................................................. 1009.3.5 Delete STMU-48 ...................................................................................................................... 1019.3.6 Create STMU-44 ...................................................................................................................... 1019.3.7 Create SET-176 and SET-178 .................................................................................................. 1029.3.8 Create interface(s) from SET-176, SET-178 and connect related TCSM(s)................................. 1029.3.9 Change STMU-44 to WO-EX .................................................................................................... 1029.3.10 Remove interfaces from SET-200 and disconnect effected TCSM(s) .......................................... 1029.3.11 Change STMU-50 SE-NH state ................................................................................................ 1039.3.12 Delete SET-200 ....................................................................................................................... 1039.3.13 Delete STMU-50 ...................................................................................................................... 1039.3.14 Create STMU-46 ...................................................................................................................... 1049.3.15 Create SET-184 ....................................................................................................................... 1049.3.16 Create interface(s) from SET-184 and connect related TCSM(s) ................................................ 1049.3.17 Change STMU-46 to WO-EX .................................................................................................... 1059.3.18 Change SET-208 to SE-NH state .............................................................................................. 1059.3.19 Delete SET-208 ....................................................................................................................... 1059.3.20 Create SET-186 ....................................................................................................................... 1059.3.21 Make cabling changes .............................................................................................................. 1069.3.22 Change SET-186 to WO-EX state ............................................................................................. 1079.3.23 Create interface(s) from SET-186 and connect related TCSM(s) ................................................ 1079.3.24 Remove interfaces from SET-210 and disconnect effected TCSM(s) .......................................... 1079.3.25 Change STMU-52 SE-NH ......................................................................................................... 1079.3.26 Delete SET-210 ....................................................................................................................... 1079.3.27 Delete STMU-52 ...................................................................................................................... 1089.3.28 Insert a new ETS2 plug-in unit to GTIC-8 and GTIC-9 track 7 .................................................... 1089.3.29 Create STMU-48 to GTIC-8 ...................................................................................................... 1089.3.30 Create SET-192 ....................................................................................................................... 1089.3.31 Make cabling changes .............................................................................................................. 1099.3.32 Create interface(s) from SET-192 and connect related TCSM(s) ................................................ 1099.3.33 Change STMU-48 WO-EX state ............................................................................................... 1099.3.34 Remove interfaces from SET-216 and disconnect effected TCSM(s) .......................................... 1109.3.35 Change STMU-54 SE-NH state ................................................................................................ 1109.3.36 Delete SET-216 ....................................................................................................................... 1109.3.37 Create SET-194 ....................................................................................................................... 1119.3.38 Make cabling changes .............................................................................................................. 1119.3.39 Create interface(s) from SET-194 and connect related TCSM(s) ................................................ 1129.3.40 Change SET-194 to WO-EX state ............................................................................................. 1129.3.41 Delete STMU-54 ...................................................................................................................... 1129.3.42 Create STMU-45/47/49 ............................................................................................................ 1129.3.43 Install new cables and modules ................................................................................................ 1139.3.44 Create protection groups .......................................................................................................... 1149.3.45 Change STMU-45/47/49 to WO-EX .......................................................................................... 115

10 Copy the HW equipment database information to the disk (DBC) ......................................................... 11611 Actions after upgrade & Post conditions .............................................................................................. 117

11.1 BSS Integration ............................................................................................................................................. 11711.2 BSC configuration printout (post-check) .......................................................................................................... 11711.3 Return to the old HW configuration ................................................................................................................. 117

12 Appendix ............................................................................................................................................. 11812.1 Appendix1: Combined TCSM3i cables ............................................................................................................ 118

Contact:

Contact your local Nokia Solutions and Networks support


Summary of changes:

1.0-0 1st approved version1.1-0 Added CR75 details1.2-0 Added connection settings for Linux in chapter 5.5.5.2.1.3-0 Added note regarding COM issue in HIT3.3 in chapter

5.5.5.1.2 and 5.5.5.2.2.1.4-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.


1 PURPOSE

This document describes the implementation of changing line protection of ETS2 plug-in unit to equipmentprotection. The SDH/Sonet equipment protection implementation is available for third generation DX200 BSC3iwith following options:

- Combined BSC3i1000/TCSM3i

- Combined Flexi BSC/TCSM3i

The upgrade can be done either the whole TCSA cabinet at a time or one STM-1/OC-3 at a time. During theactual upgrade the traffic needs to be re-directed and units cannot carry traffic. With one STM-1/OC-3 at the timeoption, the traffic lost will be lower.


2 SCOPE OF APPLICATIONS

The BSC/TCSM upgrade for SDH/Sonet equipment protection implementation is available for third generationDX200 BSC3i 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 plug-in unit before the actual upgrade.With this procedure user can choose upgrade to be done as whole TCSA Cabinet at a time or one STM-1/OC3 ata time. The whole TCSA cabinet at a time means that the traffic is re-directed from the whole cabinet. The oneSTM-1/OC-3 at a time means that only minor traffic re-directions are needed (from old configurations unit(s)which are needed to be deleted).Procedure must be performed locally at BSC site.


3 USING THE DOCUMENT

3.1 General info

The BSC/TCSM upgrade for SDH/Sonet equipment protection can be done using the HIT (Holistic IntegrationTester) 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 commands presented inthe manual. This is because sometimes the automated tasks of the HIT macro require more commands anddifferent 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.HITo Select wanted upgrade:

SOFTWARE UPGRADES

x SW upgrade S15 -> S16


x

HARDWARE UPGRADES

x HW upgrade 1

x HW upgrade 2

x

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)o Select wanted step

Make fallback

Check Firmware

Make pre-check

Copy SW

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.

- Asking the user to give information (e.g. paths, file names, etc.) & other userselections.

- Error situations

- Manual execution steps (i.e. when macro expects user to do some actionsmanually (e.g. copy some files, install new HW /cabling etc.)

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

- Log file from HIT Response window (.log)

x This log contains all the information of the macro execution (each MMLcommand and the whole output of the macro execution)

x User can accept the default log-file name or specify a new one. Macrogives following pop-up window for selection:

x Macro writes separate log files for following steps:

9 Configuration printout (PRE)

9 Firmware

9 Plug-in unit software upgrade

9 Safecopy


9 Transfer software to BSC

9 Configuration printout (PRE)

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

- 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

- Log print of HIT (TimeTable.log) This is a shorter description of the execution ofthe 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.


4 INTRODUCTION

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

- Fallback copying of the current software

- BSC configuration printout (pre-check)

- SDH/Sonet equipment protection upgrade for combined TCSM3i (the wholeTCSA cabinet at a time)

- SDH/Sonet equipment protection upgrade for combined TCSM3i (the one STM-1/OC-3 at a time)

- Actions after upgrade and post conditions

o BSS Integrationo 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 for combinedTCSM3i cabinets.The user can choose the upgrade to be performed as TCSA cabinet or STM-1/OC-3 at a time. Either way, theupgrade is done for one STMU pair individually. In some STMU cases, the upgrade may concern also ETIP orother STMU PCM areas. In this case, the traffic must be moved from these units, interface(s) must be removedbecause the plug-in unit needs to be deleted 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.

Cartridge and functional unit positions in combined TCSM3i cabinets:


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

- Use only ETIP

- Use mixed ETIP and ETS2 in the cartridges

- Use ETS2 cards with 2 interfaces , two active + two standby

- Use ETS2 cards with one interface, one active + one standby

With this procedure also following possibility is to be added:- 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. In case of equipment protection workingand protection sections of the same STM-1/OC-3 optical interface are located in different ETS2 plug-in units.

FTRB 1

FTRB 3 FTRB 2

FTRB 0

PDFU 1PDFU-B

1

2

3

4

0

5

PDFU-B

PDFU 0

TC2C-A

TC2C 0

REAR SIDE

0

0

0

6

0

6

9

TCSA 0

06

CLA

C-B

CLA

Cx

6

3

GT4C-A

GTIC4

AIR GUIDE

6

GT4C-A

GTIC2

GT4C-A

GTIC3

TC2C-A

TC2C 1

TC2C-A

TC2C 4

TC2C-A

TC2C 5

TC2C-A

TC2C 2

TC2C-A

TC2C 3

CPGO

8

FTRB 1

FTRB 3 FTRB 2

FTRB 0

PDFU 1PDFU-B

1

2

3

4

0

5

PDFU-B

PDFU 0

TC2C-A

TC2C 6

REAR SIDE

0

0

0

6

0

6

9

TCSA 1

06

CLA

C-B

CLA

C2

6

3

GT4C-A

GTIC7

AIR GUIDE

6

GT4C-A

GTIC5

GT4C-A

GTIC6

TC2C-A

TC2C 7

TC2C-A

TC2C 10

TC2C-A

TC2C 11

TC2C-A

TC2C 8

TC2C-A

TC2C 9

CPGO

8

FTRB 1

FTRB 3 FTRB 2

FTRB 0

PDFU 1PDFU-B

1

2

3

4

0

5

PDFU-B

PDFU 0

TC2C-A

TC2C 12

REAR SIDE

0

0

0

6

0

6

9

TCSA 2

06

CLA

C-B

CLA

C3

6

3

GT4C-A

GTIC10

AIR GUIDE

6

GT4C-A

GTIC8

GT4C-A

GTIC9

TC2C-A

TC2C 13

TC2C-A

TC2C 16

TC2C-A

TC2C 17

TC2C-A

TC2C 14

TC2C-A

TC2C 15

CPGO

8

x = 1 when BSC3i part isBSC3i 1000 or Flexi BSCx = 2 when BSC3i part isBSC3i 2000


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 for all ETS2 units, four new ETS2 plug-in unitsmust be added for both GTIC-0 and GTIC-1 to gain same capacity as in the originalconfiguration.

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 or upgraded FlexiBSC.

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 Combined TCSM3i equipment before upgrade

4.1.1 TCSA-0 cabinet


4.2 Combined TCSM3i equipment after upgrade




5 PRE-REQUIREMENTS

5.1 Pre-requirements & Actions needed prior upgrade

The procedure can be implemented for S16 software onwards. It is recommended to install all available changedeliveries prior to the upgrade.IMPORTANT!Re-direct traffic from upgraded TCSA cabinet or STM-1/OC-3 before actual upgrade. Each STMU unitmust be handled case by case and PCM areas which are affected during upgrade may vary. It is possiblethat new protected STMU unit uses some other STMU unit area or in case of mixed configuration theGTIC-1 cartridges track may contain ETIP plug-in units. In this case effected units traffic needs to be re-directed, interfaces removed and unit needs to be deleted (PCM areas released to new STMU unit usage)from hardware database before new configuration 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.

IMPORTANT!

When operating in Flexi BSC, make sure that OCTFIL parameter SEL_OCTFIL_VARIANT_TO (class 2,parameter 1554) value is correct:

Upgraded Flexi BSC 3000/4200 0000Initial Flexi BSC 3000/4200 0001

If OCTFIL value is incorrect, it may cause upgrade procedure to work wrongly. The OCTFIL information is one ofthe input information which macro uses (when macro is started) for analyse the used BSC type. When value isincorrect for some reason, the macro may execute the wrong steps during procedure execution.

5.2 Restrictions

STMU unit (ETS2 plug-in unit) which is to be upgraded can handle following interfaces:x A interface (including A-SIGTRAN)

When STMU unit protection is changed, the unit will be blocked, meaning that the interfaces which controlling unitis 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 been finished successfully for one STMU unitpair, the traffic can be re-directed back to old STMU unit.In case of upgrade to whole TCSA cabinet, the traffic must be re-directed while upgrading and after successfulupgrade, the traffic can be re-hosted back to that same TCSA cabinet.Always, all the existing STMU units need to be upgraded at once. Macro starts from first STMU index and keepsgoing until every STMU unit has been upgraded. It is not allowed to use both line protected and HW protectedSTMU units in same GTIC-cartridge.

5.3 Needed documentation

To perform the upgrade successfully, the following documentation is required:x BSC/TCSM 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 Fallback copying instructions of DX200 BSC (NED)x Technical Support Note: Minimum HW Requirements for BSC S1xx Releasex HIT Users manualx Cabling Instructions for i-series Network Elements DN0094395x Labels of the IC209-A/IC209-B Equipment Cabinet CAN104723

5.4 Needed equipment

To perform the upgrade successfully, the following HW are required:x PC with installed HIT and upgrading macrosx Cabinet Upgrade Set (ETS2/ETIP equipment protection TCSM/BSC3i/FlexiBSC) for

upgrading Transmission protection to HW protection. Note that the upgrade set is for

one TCSA cabinet in combined BSC/TCSM installation. So 3 peaces are needed for

3 x TCSA cabinets (TCSA 0 & 1 & 2).

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 S14 TCSM3i: HW redundancy: 5000871 ETS2/ETIP equipment protection TCSMx S15 TCSM3i : HW redundancy: 5000888 Equipment Protection Cabling TCSM

(S15)


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 Release Binder which can be found from NOLS (Nokia Online Services). Release bindercontains all the macros used in different upgrades related to SW.

To install the macros into PC, execute the macros.exe program. When the exe file is run the following dialog willappear:

Specify the folder to which the macros will be installed, press Unzip and the macros will 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.


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) anddouble-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 pressOK

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)

5.5.5.1 Connection settings for Windows1.1.1.1.1 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.


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.

1.1.1.1.2 5.5.5.1.2 Configuration example for creating COM connection

Select Device > Set Configuration from menu.Following 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.5.2 Connection settings for Linux1.1.1.1.3 5.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.1.1.1.1.4 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 execution

First 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 toexecute. Clicking CANCEL in main menu aborts the macro execution.


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

Select ini file from the list.


Select target network element from the list.

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 packagemust be with status BU before the actual upgrade can be started. The software status is to bechecked with command:

ZWQO:RUN;


Check from the output that all the computer units which are currently in use are running on correctsoftware package with the status BU. If the software package status is FB or NW, find out the causefor 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 followingcommands:

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.


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/TCSM upgrade for SDH/Sonetequipment protection procedure. Follow then the macro execution according the BSC configuration printout document.


8 SDH/SONET EQUIPMENT PROTECTION UPGRADE FOR COMBINEDTCSM3I (OFFLINE)

In this chapter, the upgrade will be done to whole TCSA cabinet at a time (OFFLINE)sothat the cabinet cannot be handle traffic during upgrade.

HW redundant STMU units will be equipped according to following pictures.


8.1 Choose TCSA cabinet to be upgraded

TCSA-0 cabinet must be upgrade first. TCSA-1 cabinet must be upgrade second. TCSA-2 cabinet must beupgrade third.

Choose a correct TCSA cabinet which STMU units will be upgraded. Upgrade must be made for whole TCSAcabinet at once.

8.2 Move traffic from STMU which will be upgraded

Move traffic from STMU units located in TCSA cabinet to be upgraded.

Change TCSM units to SE-NH state located in TCSA cabinet to be upgraded.

8.3 Delete old configurations & equipment

In this step, all the old STMU configurations and equipment will be deleted.

Delete all STMU interface(s) located in chosen TCSA-cabinet.Change STMU unit which are going to be upgraded (in both cartridges ifexists) to SE-NH state.

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

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

Delete existing transmission protection groups from all STMU(s).

ZYWD:;

Remove through connected channel (manually):ZWGR::;

Delete transcoder PCM (manually):ZWGD: :,;

Set number of through connected channels (manually):ZWGS::0;

Disconnect TCSM units (manually):ZWUD:TCSM,:TR3E,;


Delete ET equipment related to STMU unit(s).Disconnect ET unit(s)

ZWUD:ET,&&:ETS2,0;

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

Delete unitsZWTV:ET,&&;

Delete STMU equipment with following commands:ZWUD:STMU,:ETS2,0;ZWTQ:STMU,:ETS2,0;ZWTV:STMU,;

8.4 Install redundant ETS2 plug-in unit(s)

Install ETS2 plug-in unit(s) into track 7 for HW protection usage if unit does not exist. One ETS2 plug-in unit mustexists in same track in both GTIC-cartridges.

8.5 Make cabling changes and install new cables

Change spare MCMU state to SE-NH.ZUSC:MCMU,,TE-EX;ZUSC:MCMU,,SE-OU;ZUSC:MCMU,,SE-NH;

Make cabling and setting modules changes according to Appendix1: Combined TCSM3i cablings.

After cabling changes has been finished to first MCMU, change the unit back to SP-EX, make a switchover andchange other MCMU to SE-NH state. After second MCMU cabling changes, raise MCMU back to working state.

8.6 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 chapter 9.1.


8.6.1 BSC3i 1000/2000 or upgraded Flexi BSC

8.6.1.1 Equip new redundant STMU units

Create redundant STMU unit(s) for correct TCSA cabinet

TCSA-0

ZWTU:STMU,32:;ZWTU:STMU,34: ;ZWTU:STMU,36: ;

ZWTU:STMU,33: ;ZWTU:STMU,35: ;ZWTU:STMU,37: ;

TCSA-1



TCSA-2



Create redundant ETS2 plug-in unit

TCSA-0

For BSC 3i 1000/2000

ZWTP:STMU,32:ETS2,0,5::LAPD,8,882,TSL,0&&15;ZWTP:STMU,34:ETS2,0,6::LAPD,8,882,TSL,16&&31;


ZWTP:STMU,36:ETS2,0,7::LAPD,8,883,TSL,0&&15;

ZWTP:STMU,33:ETS2,0,5::LAPD,8,890,TSL,0&&15;ZWTP:STMU,35:ETS2,0,6::LAPD,8,890,TSL,16&&31;ZWTP:STMU,37:ETS2,0,7::LAPD,8,891,TSL,0&&15;

For Upgraded Flexi BSC



TCSA-1

For BSC 3i 1000/2000


ZWTP:STMU,39:ETS2,0,5::LAPD,8,1082,TSL,0&&15;ZWTP:STMU,41:ETS2,0,6::LAPD,8,1082TSL,16&&31;ZWTP:STMU,43:ETS2,0,7::LAPD,8,1083,TSL,0&&15;

For Upgraded Flexi BSC



TCSA-2 For BSC 3i 1000/2000,Upgraded Flexi BSC




Connect ETS2 plug-in unit

TCSA-0

ZWUC:STMU,32:ETS2,0::BCSU,;ZWUC:STMU,34:ETS2,0::BCSU,;ZWUC:STMU,36:ETS2,0::BCSU,;


TCSA-1



TCSA-2



8.6.1.2 Create new ET units

Create ET plug-in units for ANSI or ETSI mode.

ETSI

TCSA-0

ZWTU:ET,3560&&3622:< LOCATION >:UNIT=STMU,IND=32,IF=0;ZWTU:ET,3624&&3686: < LOCATION >:UNIT=STMU,IND=32,IF=1;

ZWTU:ET,3688&&3750: < LOCATION >:UNIT=STMU,IND=34,IF=0;


ZWTU:ET,3752&&3814: < LOCATION >:UNIT=STMU,IND =34,IF=1;

ZWTU:ET,3816&&3878: < LOCATION >:UNIT=STMU,IND =36,IF=0;ZWTU:ET,3880&&3942::UNIT=STMU,IND=36,IF=1;

ZWTP:ET,3560&&3622:ETS2,0,5::ETT00,8,3560&&3622,TSL,0:;ZWTP:ET,3624&&3686:ETS2,0,5::ETT00,8,3624&&3686,TSL,0:;



TCSA-1ZWTU:ET,3944&&4006::UNIT=STMU,IND=38,IF=0;ZWTU:ET,4008&&4070::UNIT=STMU,IND=38,IF=1;

ZWTU:ET,4072&&4134::UNIT=STMU,IND=40,IF=0;ZWTU:ET,4136&&4198::UNIT=STMU,IND=40,IF=1;












ANSI




















Connect ET plug-in units

ETSIZWUC:ET,3560&&3622:ETS2,0:IF=A:BCSU,:;ZWUC:ET,3624&&3686:ETS2,0:IF=A:BCSU,:;ZWUC:ET,3688&&3750:ETS2,0:IF=A:BCSU,:;ZWUC:ET,3752&&3814:ETS2,0:IF=A:BCSU,:;ZWUC:ET,3816&&3878:ETS2,0:IF=A:BCSU,:;ZWUC:ET,3880&&3942:ETS2,0:IF=A:BCSU,:;

ZWUC:ET,3944&&4006:ETS2,0:IF=A:BCSU,:;ZWUC:ET,4008&&4070:ETS2,0:IF=A:BCSU,:;ZWUC:ET,4072&&4134:ETS2,0:IF=A:BCSU,:;ZWUC:ET,4136&&4198:ETS2,0:IF=A:BCSU,:;ZWUC:ET,4200&&4262:ETS2,0:IF=A:BCSU,:;ZWUC:ET,4264&&4326:ETS2,0:IF=A:BCSU,:;


ANSIZWUC:ET,3560&&3643:ETS2,0:IF=A:BCSU,:;ZWUC:ET,3644&&3727:ETS2,0:IF=A:BCSU,:;ZWUC:ET,3728&&3811:ETS2,0:IF=A:BCSU,:;ZWUC:ET,3812&&3895:ETS2,0:IF=A:BCSU,:;ZWUC:ET,3896&&3979:ETS2,0:IF=A:BCSU,:;ZWUC:ET,3980&&4063:ETS2,0:IF=A:BCSU,:;

ZWUC:ET,4064&&4147:ETS2,0:IF=A:BCSU,:;ZWUC:ET,4148&&4231:ETS2,0:IF=A:BCSU,:;ZWUC:ET,4232&&4315:ETS2,0:IF=A:BCSU,:;ZWUC:ET,4316&&4399:ETS2,0:IF=A:BCSU,:;


ZWUC:ET,4400&&4483:ETS2,0:IF=A:BCSU,:;ZWUC:ET,4484&&4567:ETS2,0:IF=A:BCSU,:;


8.6.1.3 Create new HW protection sets

Create HW protection sets for ANSI or ETSI mode.

ANSI:

TCSA-0ZYWC:,,APS:128,132;ZYWC:,,APS:130,134;

ZYWC:,,APS:136,140;ZYWC:,,APS:138,142;

ZYWC:,,APS:144,148;ZYWC:,,APS:146,150;


ZYWC:,,APS:160,164;ZYWC:,,APS:162,166;

ZYWC:,,APS:168,172;ZYWC:,,APS:170,174;


ZYWC:,,APS:184,188;ZYWC:,,APS:186,190;

ZYWC:,,APS:192,196;ZYWC:,,APS:194,198;


ETSI:

TCSA-0ZYWC:,,MSP:128,132;ZYWC:,,MSP:130,134;

ZYWC:,,MSP:136,140;ZYWC:,,MSP:138,142;

ZYWC:,,MSP:144,148;ZYWC:,,MSP:146,150;


ZYWC:,,MSP:160,164;ZYWC:,,MSP:162,166;

ZYWC:,,MSP:168,172;ZYWC:,,MSP:170,174;


ZYWC:,,MSP:184,188;ZYWC:,,MSP:186,190;

ZYWC:,,MSP:192,196;ZYWC:,,MSP:194,198;

8.6.1.4 Change new STMU units to WO-EX state

Change STMU(s) to WO-EX state

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

Macro executes Plug-in unit software upgrade procedure for STMU unit. After PIU software has been updatedsuccessfully,Run diagnostic:

ZUDU:STMU,;After successful loading take the unit to WO-EX state

ZUSC:STMU,:WO;


Note!If more TCSA cabinets needs to be upgraded, do the chapters 8.1-8.6 again.

8.6.2 New Delivery Flexi BSC

8.6.2.1 Equip new redundant STMU units

Create redundant STMU unit(s) for correct TCSA cabinet

TCSA-0

ZWTU:STMU,32:1C1-3;ZWTU:STMU,34:1C1-3;ZWTU:STMU,36:1C1-3;


TCSA-1



TCSA-2

ZWTU:STMU,44:1D1-3;ZWTU:STMU,46:1D1-3;ZWTU:STMU,48:1D1-3;

ZWTU:STMU,45:1D1-6;ZWTU:STMU,47:1D1-6;ZWTU:STMU,49:1D1-6;


Create redundant ETS2 plug-in unit

TCSA-0



TCSA-1



TCSA-2



Connect ETS2 plug-in unit

TCSA-0



TCSA-1




TCSA-2



8.6.2.2 Create new ET units

Create ET plug-in units for ANSI or ETSI mode.

ETSI

TCSA-0ZWTU:ET,3560&&3622:STMU,32,IF=0;ZWTU:ET,3624&&3686:STMU,32,IF=1;

ZWTU:ET,3688&&3750:STMU,34,IF=0;ZWTU:ET,3752&&3814:STMU,34,IF=1;


















ANSI




















Connect ET plug-in units


ETSIZWUC:ET,3560&&3622:ETS2,0:IF=:BCSU,:;ZWUC:ET,3624&&3686:ETS2,0:IF=:BCSU,:;ZWUC:ET,3688&&3750:ETS2,0:IF=:BCSU,:;ZWUC:ET,3752&&3814:ETS2,0:IF=:BCSU,:;ZWUC:ET,3816&&3878:ETS2,0:IF=:BCSU,:;ZWUC:ET,3712&&3744:ETS2,0:IF=:BCSU,:;

ZWUC:ET,3944&&4006:ETS2,0:IF=:BCSU,:;ZWUC:ET,4008&&4070:ETS2,0:IF=:BCSU,:;ZWUC:ET,4072&&4134:ETS2,0:IF=:BCSU,:;ZWUC:ET,4136&&4198:ETS2,0:IF=:BCSU,:;ZWUC:ET,4200&&4262:ETS2,0:IF=:BCSU,:;ZWUC:ET,4264&&4326:ETS2,0:IF=:BCSU,:;


ANSIZWUC:ET,3560&&3643:ETS2,0:IF=:BCSU,:;ZWUC:ET,3644&&3727:ETS2,0:IF=:BCSU,:;ZWUC:ET,3728&&3811:ETS2,0:IF=:BCSU,:;ZWUC:ET,3812&&3895:ETS2,0:IF=:BCSU,:;ZWUC:ET,3896&&3979:ETS2,0:IF=:BCSU,:;ZWUC:ET,3980&&4063:ETS2,0:IF=:BCSU,:;



8.6.2.3 Create new HW protection sets

Create HW protection sets for ANSI or ETSI mode.


ANSI:

TCSA-0ZYWC:,,,APS:128,132;ZYWC:,,,APS:130,134;

ZYWC:,,,APS:136,140;ZYWC:,,,APS:138,142;

ZYWC:,,,APS:144,148;ZYWC:,,,APS:146,150;


ZYWC:,,,APS:160,164;ZYWC:,,,APS:162,166;

ZYWC:,,,APS:168,172;ZYWC:,,,APS:170,174;


ZYWC:,,,APS:184,188;ZYWC:,,,APS:186,190;

ZYWC:,,,APS:192,196;ZYWC:,,,APS:194,198;

ETSI:

TCSA-0ZYWC:,,,MSP:128,132;ZYWC:,,,MSP:130,134;

ZYWC:,,,MSP,140;ZYWC:,,,MSP:138,142;

ZYWC:,,,MSP:144,148;ZYWC:,,,MSP:146,150;

TCSA-1


ZYWC:,,,MSP:152,156;ZYWC:,,,MSP:154,158;

ZYWC:,,,MSP:160,164;ZYWC:,,,MSP:162,166;

ZYWC:,,,MSP:168,172;ZYWC:,,,MSP:170,174;

TCSA-2ZYWC:,,,MSP:176,180;ZYWC:,,,MSP:178,182;

ZYWC:,,,MSP:184,188;ZYWC:,,,MSP:186,190;

ZYWC:,,,MSP:192,196;ZYWC:,,,MSP:194,198;

8.6.2.4 Change new STMU units to WO-EX state

Change both GTIC cardridges STMU to WO-EX state

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

Macro executes Plug-in unit software upgrade procedure for STMU unit. After PIU software has been updatedsuccessfully,Run diagnostic:

ZUDU:STMU,;After successful loading take the unit to WO-EX state

ZUSC:STMU,:WO;

Note!If more TCSA cabinets needs to be upgraded, do the chapters 8.1-8.6 again.


9 SDH/SONET EQUIPMENT PROTECTION UPGRADE FOR COMBINEDTCSM3I (LIVE)

In this chapter, the upgrade will be done to one STM-1/OC-3 at a time(LIVE) so thatduring upgrade, the effected SET cannot handle traffic.

HW redundant STMU units will be equipped according to following pictures.


9.1 TCSA-0

In this chapter TCSA-0 cabinets STMU units are upgraded serially starting from STMU index 34. STMU-32 unitand related ET SET(s) are not needed to be deleted and re-created. In this case only old protection groups needsto be deleted.

9.1.1 Remove protection groups

Change sets 129, 131, 137, 145, 147 and 153 to SE-NH state with following command:

ZUSC:SET,:TE,FCD:;ZUSC:SET.:SE;ZUSC:SET,:SE;

Remove protection groups from STMU-32/34/36/38 units with following command:

ZYWD:;

9.1.2 Remove interfaces from SET-144 and disconnect effected TCSM(s)

In this step, delete interfaces from SET-144 unit. Disconnect also manually related TCSM(s). TCSM unit(s)equipment is not needed to be deleted only disconnection is enough.

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

9.1.3 Change SET-144 to SE-NH state

Change SET-144 to SE-NH state with following commandsZUSC:SET,144:TE,FCD:;ZUSC:SET,144:SE;ZUSC:SET,144:SE;

9.1.4 Delete SET-144

Delete SET-144 with following commands:

Disconnect unitsETSI

ZWUD:ET,3752&&3814:ETS2,0;

ANSIZWUD:ET,3812&&3895:ETS2,0;


Delete plug-in unitsETSI

ZWTQ:ET,3752&&3814:ETS2,0;

ANSIZWTQ:ET,3812&&3895:ETS2,0;

Delete unitsETSI

ZWTV:ET,3752&&3814;ANSI

ZWTV:ET

Documents

BSC3i_TCSM3i Upgrade for SDH_Sonet Equipment Protection (S12 - S14 TCSM HW)_ver1_4