BSC ETIP1-A Implementation for IP PWE Ver1 7 0

DN09114063 BSC ETIP1-A implementation for IP/PWECopyright 2013 Nokia Solutions and Networks. All rights reserved.CONFIDENTIALAPPROVED 1.7

1 (114)

BSC ETIP1-Aimplementation forIP/PWERelease Delivery: HW UpgradeProduct Family: Radio ControllersProduct: BSC3i, Flexi BSCRelease: S16 onwards

Approval date: 14-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.


2 (114)

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

3.1 General info ....................................................................................................................................................... 63.2 Upgrade macro .................................................................................................................................................. 6

3.2.1 Structure ...................................................................................................................................... 63.2.2 Communication ............................................................................................................................ 7

4 Introduction ............................................................................................................................................. 95 Pre-requirements .................................................................................................................................. 12

5.1 Pre-requirements & Actions needed prior upgrade ............................................................................................ 125.2 Restrictions ..................................................................................................................................................... 125.3 Needed documentation .................................................................................................................................... 135.4 Needed equipment .......................................................................................................................................... 135.5 HIT and upgrade macros.................................................................................................................................. 13

5.5.1 System requirements for HIT ...................................................................................................... 135.5.2 Installing HIT .............................................................................................................................. 135.5.3 Installing HIT upgrading macros .................................................................................................. 145.5.4 HIT settings................................................................................................................................ 145.5.5 Connection settings .................................................................................................................... 145.5.6 Starting the HIT application / macro execution ............................................................................. 26

6 Fallback copying of the current package ................................................................................................ 327 BSC configuration printout (pre-check) .................................................................................................. 338 BSC ETIP1-A implementation for IP/PWE in case of transmission (line) redundancy ............................. 34

8.1 Re-host traffic from concerning STMU/ET16 unit............................................................................................... 348.2 Delete old configurations & equipment .............................................................................................................. 358.3 Make cabling changes, install ETIP1-A plug-in unit and connect cables related to MCMU,0 ............................... 368.4 Make DIP-switch changed to SW256B in MCMU,0 ........................................................................................... 378.5 Make cabling changes, connect cables related to MCMU-1 .............................................................................. 378.6 Make DIP-switch changed to SW256B in MCMU-1 ........................................................................................... 378.7 New ETIP configuration & equipment with transmission/line protection .............................................................. 37

8.7.1 Equip new redundant ETIP units ................................................................................................. 378.7.2 Create new ET units ................................................................................................................... 388.7.3 Change new ETIP units to WO-EX state ..................................................................................... 388.7.4 Configuring the IP ...................................................................................................................... 388.7.5 Configuring the PW .................................................................................................................... 38

8.8 MCMU diagnostic ............................................................................................................................................ 389 BSC ETIP1-A implementation for IP/PWE in case of HW redundancy .................................................... 40

9.1 Re-host traffic from concerning unit (STMU/ETIP with transmission redundancy or ET16) .................................. 419.2 Delete old configurations & equipment .............................................................................................................. 429.3 Make cabling changes, install redundant ETIP1-A plug-in unit and install new cables related to MCMU-0 439.4 Make DIP-switch changes to SW256B in MCMU,0 ............................................................................................ 449.5 Make cabling changes, install new cables related to MCMU-1 ........................................................................... 449.6 Make DIP-switch changes to SW256B in MCMU,1 ............................................................................................ 449.7 New ETIP configuration & equipment with HW redundancy ............................................................................... 45

9.7.1 Equip new ETIP units ................................................................................................................. 459.7.2 Create new ET units ................................................................................................................... 459.7.3 Change new ETIP units to WO-EX state ..................................................................................... 45

9.8 Configuring the IP ............................................................................................................................................ 469.9 Configuring the PW .......................................................................................................................................... 469.10 MCMU diagnostic ............................................................................................................................................ 46

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

11.1 BSS Integration ............................................................................................................................................... 4811.2 BSC configuration printout (post-check) ............................................................................................................ 48


3 (114)

11.3 Return to the old HW configuration ................................................................................................................... 4812 Appendix ............................................................................................................................................... 49

12.1 Appendix1: MCMU,0 related cablings in BSC3i 1000/2000 or upgraded FlexiBSC3i ........................................... 4912.2 Appendix2: MCMU,1 related cablings in BSC3i 1000/2000 or upgraded FlexiBSC3i ........................................... 5312.3 Appendix3: MCMU,0 related cablings in New Delivery FlexiBSC3i ..................................................................... 5612.4 Appendix4: MCMU,1 related cablings in New Delivery FlexiBSC3i ..................................................................... 6112.5 Appendix5: SW256B jumper settings ................................................................................................................ 64

12.5.1 PCM mode settings (SW1) ......................................................................................................... 6412.5.2 Interchangeability code settings (SW2) ....................................................................................... 6412.5.3 Serial Broadband SB1 settings (SW3) ......................................................................................... 6512.5.4 Serial Broadband SB2 settings (SW4) ......................................................................................... 6612.5.5 Serial Broadband SB3 settings (SW5) ......................................................................................... 6612.5.6 Serial Broadband SB4 settings (SW6) ......................................................................................... 6612.5.7 SW256B jumper settings in new delivery Flexi BSC ..................................................................... 6712.5.8 SW256B jumper settings in a combined BSC/TCSM installation where the BSC part isnew delivery Flexi BSC ............................................................................................................................... 7112.5.9 SW256B jumper settings in a combined BSC/TCSM installation where the BSC part isupgraded Flexi BSC ................................................................................................................................... 7412.5.10 SW256B jumper settings in upgraded Flexi BSC ......................................................................... 7812.5.11 SW256 settings in a combined BSC3i/TCSM installation where the BSC part is BSC3i1000 or BSC3i 2000 and TCSM part is S12-S14 HW ................................................................................... 8312.5.12 SW256B jumper settings in a combined BSC/TCSM installation where the BSC part isBSC3i 1000 or BSC3i 2000 and TCSM part is S15 HW TCSM3i .................................................................. 8812.5.13 SW256B jumper settings in BSC3i .............................................................................................. 92

12.6 Appendix6: GTIC & ETC PCM usage in case of BSC3i 1000/2000 .................................................................... 9712.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 SGC1C-A cartridges locking pegs ................................ 10412.10 Appendix10: Initial Flexi BSC SGC1C-A cartridges locking pegs ..................................................................... 10512.11 Appendix11.1: ETIP&EET&ET indices and control PCM(s) when transmission/line redundancy is in use .......... 10612.12 Appendix11.2: ETIP&EET&ET indices and control PCM(s) when Hardware redundancy is in use..................... 10912.13 Appendix12: GTIC & ETC PCM usage in case of BSC3i 1000/2000 and upgraded Flexi BSCtransmission/line redundancy ..................................................................................................................................... 11112.14 Appendix13: GTIC & ETC PCM usage in case of new delivery Flexi BSC transmission/line redundancy ........... 113

Contact:

Contact your local Nokia Solutions and Networks support

Summary of changes:

14-Dec-2012 0.1-0 Creation date14-Dec-2012 1.1-0 Approval date, Corrected appendix 5 SW256B jumper

settings of Initial Flexi BSC

18-Jan-2013 1.2-0 Added CR75 details

06-Feb-2013 1.3-0 Added connection settings for Linux in chapter 5.5.5.225-Feb-2013 1.4-0 Added note regarding COM issue in HIT3.3 in chapter

5.5.5.1.2 and 5.5.5.2.2.

04-Apr-2013 1.5-0 Removed note regarding COM issue from chapters5.5.5.1.2 and 5.5.5.2.2.Also updated the hit version as3.4-0.

18-Sep-2013 1.6-0 Template update05-Mar-2014 1.7-0 Updated appendix 12.5: SW256B jumper settings


4 (114)

1 PURPOSE

This document describes the implementation of changing line or hardware protection of ETS2 plug-in unit toETIP1-A equipment protection. The procedure supports also installation of new ETIP plug-in unit with equipmentprotection.

This document can be used with following environments: BSC3i1000/2000 upgraded Flexi BSC new delivery Flexi BSC


5 (114)

2 SCOPE OF APPLICATIONS

The BSC ETIP1-A implementation for IP/PWE is available for third generation DX200 BSC in S16 releaseonwards.

The procedure cannot be executed without traffic interruption. Traffic must be moved from concerning ET16,ETS2 or ETIP (with transmission redundancy) plug-in unit before the actual upgrade.

Procedure must be performed locally at BSC site.


6 (114)

3 USING THE DOCUMENT

3.1 General info

The BSC ETIP1-A implementation for IP/PWE can be done using the HIT (Holistic Integration Tester) softwaretool. 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.HIT Select wanted upgrade:

o SOFTWARE UPGRADES SW upgrade S15 -> S16

o HARDWARE UPGRADES

HW upgrade 1 HW upgrade 2


7 (114)

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

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

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

3.2.2.1 Log filesThe 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)o This log contains all the information of the macro execution (each MML command and the

whole output of the macro execution)o User can accept the default log-file name or specify a new one. Macro gives following pop-up

window for selection:


8 (114)

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)

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) The contents of the message window are saved after macro execution. 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:

Starting an execution step in macro Execution status (Done). 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.


9 (114)

4 INTRODUCTION

The BSC ETIP1-A implementation for IP/PWE procedure consists of the following tasks:

Fallback copying of the current software BSC configuration printout (pre-check) BSC ETIP1-A implementation for IP/PWE in case of ETIP transmission/line redundancy BSC ETIP1-A implementation for IP/PWE in case of ETIP HW redundancy 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 only for BSC3i orFlexi BSC.

Line protection cannot be used after equipment protection has been taken in use. So, the upgrade will be done forwhole GTIC cartridge at the time even each ETIP unit is handled one by one.

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

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 ETS2 cards with 2 interfaces , two active + two standby Use ETS2 cards with one interface, one active + one standby Use ETIP cards with transmission redundancy Use mixed ET16, ETS2 and ETIP in the cartridges (ETS2 either 2+2 or 1+1)

With this procedure also following possibility is to be added: Use ETIP cards with line or hardware redundancy

Each GTIC cartridges track will be handled separately. The possibility is that the upgraded track can effect alsoalready existing ET16/ETS2/ETIP PCM areas. In this case, the traffic must be moved from these units,interface(s) must be removed because the plug-in unit needs to be deleted from equipment database.

The upgrade cannot be executed with traffic and traffic needs to be re-hosted. During upgrade effected unit will beblocked and state changed to TE-EX or SE-NH.

Background:ETIP1-A plug-in unit is a unit, which implements IETF pseudo wire emulation edge to edge (PWE3) functionalityin DX 200. Basically this means E1/T1 over Ethernet. The ETIP1-A plug-in unit has one redundant Gigabitethernet interface in front panel.The Gigabit ethernet interfaces are provided by hot-pluggable SFP modules, which are not part of the ETIP1-APIUs structure.As a GSW interface the unit uses either thirty-two 8 Mbit/s TDM interfaces or two Hotlink interfaces. There areactually four physical Hotlink interfaces, due to 2N redundancy support.ETIP1 can be installed into dedicated TC2C-A, GT4C-A and GT6C-A cartridges. ETIP1 supports alsosynchronous ethernet and timing over packet (IEEE1588v2) for synchronization purposes.


10 (114)

Redundancy for ETIP & EET units:

Transmission/line redundancy as a base, HW redundancy as optionalTransmission/line redundancy (base):Number of ETIP units having transmission/line redundancy (only even ETIP indices are used):

Either 0 8 (in step of 1 pcs at a time) when maximum PWE capacity in use (both Hotlink pairs cabled)per ETIP1-A plug-in unit

Transmission redundant EET units are equipped so, that active & standby EET units are on same ETIP1-A plug-in units. All EETs have a unique index of their own. Both even and odd EET indices are used.In transmission/line redundancy maximum of either 4 pcs ETIP1-A pius are equipped to both GTIC parts &maximum PWE capacity in use (both Hotlink pairs cabled) per ETIP1-A plug-in unit.

HW redundancy (optional):Number of ETIP units having HW redundancy (both even and odd ETIP indices are used):

0 16 (in step of 1 pair at a time)

Number of EET units having HW redundancy in S14 upgraded Flexi BSC: 0 16 (in step of 2 pcs at a time; 1 pcs in working ETIP + 1 pcs in protecting ETIP)

HW redundant EET units are equipped so, that active & standby EET units are on different ETIP1-A plug-in units(active EET on active ETIP1-A and standby EET on redundant ETIP1-A). All EETs have a unique index of theirown. Only even EET indices are used.

BSC3i 1000/2000 and upgraded Flexi BSC:In HW redundancy maximum of 8 pcs ETIP1-A pius are equipped to both GTIC cartridges and maximum PWE inuse (both Hotlink pairs cabled) per ETIP1-A plug-in unit. Only the 1st EET from the ETIP1-A plug-in units is usedin HW redundancy. 4 first active ETIPs are equipped to GTIC 0 slots 01 04 & their redundant ETIPs areequipped to GTIC slots 01 04, and 4 last active ETIPs are equipped to GTIC 1 slots 05 08 & their redundantETIPs are equipped to GTIC 0 slots 05 08.

Initial Flexi BSC:In HW redundancy maximum of 8 pcs ETIP1-A pius are equipped to both GTIC parts and maximum PWEcapacity in use (both Hotlink pairs cabled) per ETIP1-A plug-in unit. Only the 1st EET from the ETIP1-A plug-inunits is used in HW redundancy. 4 first active ETIPs are equipped to GTIC 0 slots 10 13 & their redundantETIPs are equipped to GTIC slots 10 13, and 4 last active ETIPs are equipped to GTIC 1 slots 14 17 & theirredundant ETIPs are equipped to GTIC 0 slots 14 17.


11 (114)

Configuration after HW upgrade in case of transmission/line redundancy:

Configuration after HW upgrade in case of HW redundancy:

GTIC 1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

Flexi BSCWithout equipment redundancy i.e. transmission redundancy,

maximum capacity per ETIP1-A usedGTIC 0

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

ETIP 0

ETIP 2

ETIP 4

ETIP 6

ETIP 16

ETIP 18

ETIP 20

ETIP 22

0

1

ActiveHotlinks (16 pcs)

EET (active)

ETIP0

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

4

5

8

9

12

13

32

33

36

37

40

41

44

45

EET (standby)1

GTIC 1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

GTIC 0

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

1st four activeHotlinks and correspondingspare Hotlinks (8 + 8 pcs)

EET

ETIP

ETIP 0

ETIP 2

ETIP 4

ETIP 6

ETIP 9

ETIP 11

ETIP 13

ETIP 15

ETIP 1

ETIP 3

ETIP 5

ETIP 7

ETIP 8

ETIP 10

ETIP 12

ETIP 140

2nd four activeHotlinks and correspondingspare Hotlinks (8 + 8 pcs)

Flexi BSCS14 equipment redundancy #1 for ETIP1-A: moving 16 pcs old Hotlink cables /4 last redundancy pairs & 16 pcs old Hotlink cables remain / 4 first redundancy

pairs & adding 32 new Hotlink cables

ETIP2

Active

Spare

Active

Spare

Active Spare

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

0 4 8 12 18 22 26 30 2 6 10 14 16 20 24 28


12 (114)

5 PRE-REQUIREMENTS

5.1 Pre-requirements & Actions needed prior upgrade

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

SW licence 1380 (Integrated IP Card) is needed to be installed before actual upgrade can be started.

IMPORTANT!Re-direct traffic from upgraded ET16 or ETS2 plug-in unit before actual upgrade.Each EET must be handled case by case and PCM areas which are affected duringupgrade may vary. In case upgrade causes disturbances to some other unit, thetraffic needs to be re-directed, interfaces removed and unit needs to be deleted(PCM areas released to new ETIP unit usage) from hardware database before newconfiguration is created.

BSS Split tool offers automated process to support BSC renewal. This is extremelyuseful, when older BSC(s) are modernised to BSC3i(s). This process includes theautomation of labor-intensive re-hosting of BTS to new BSC(s) including data andparameter updates to name a few. The downtime of operational BTS(s) is this wayminimised during re-homing. If re-homing speed is the key driver, more than 100 sitescan be moved to the new BSC during one night by using .XML files for data transferbetween the BSC(s) assisted by CM tools (CM Plan Manager, CM Editor and CMAnalyser). Further information about BSS Split tools is available from Nokia OSS /NetAct representatives.

5.2 Restrictions

The whole GTIC cartridge must be upgraded at the same time. This means that line protection cannot beused for some ETIP units and same time other ETIP units are already upgraded as hardware redundancy.ETIP unit which is to be upgraded can handle following interfaces:

A interface (including A-SIGTRAN)

Abis interface

Gb (both Gb over IP and FR must be taken into account)

BBI (BSC BSC interface for DFCA)

During upgrade, the unit will be blocked, meaning that the interfaces which controlling unit is upgraded will beaffected. Macro informs user about affected PCM areas (and units handling that area) which are needed to bedeleted. After the upgrade has been finished successfully for one ETIP unit (in case of HW redundancy ETIP unitpair), the traffic can be re-directed back.

Note!It is not allowed to use both line protected and HW protected ETIP units in same GTIC-cartridge.


13 (114)

5.3 Needed documentation

To perform the upgrade successfully, the following documentation is required: BSC ETIP1-A implementation for IP/PWE (this document)

Creating and managing BSC hardware (NED)

Cabling Instructions for BSC3i (NED)

Equipment list for BSC3i (NED)

S1xx Pre-Processor Program Information

Jumper Settings of the Plug-in Units in BSC3i and in TCSM3i

Fallback copying instructions of DX200 BSC for S1xx(NED)

Technical Support Note: Minimum HW Requirements for BSC S1xx Release

HIT Users manual

Cabling Instructions for i-series Network Elements

5.4 Needed equipment

To perform the upgrade successfully, the following HW are required: PC with installed HIT and upgrading macros

ETS2/ETIP1 card redundancy cables, BSC3i (BSCC-C02 Upgrade Set STM HW Protection) orETS2/ETIP1 card red. Cables, Flexi BSC (BSCC-E01 Upgrade Set)

Needed amount of ETIP1-A plug-in units. Note! When ETIP has line protection as source configurationand HW redundancy is planned to be upgraded, same amount of ETIP plug-in units are needed to gainsame capacity as before upgrade.

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.

http://www.online.nokia.com/


14 (114)

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.

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: Local connection (COM)

Telnet

SSH

Via Netact (SSH)

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

http://www.online.nokia.com/


15 (114)

5.5.5.1 Connection settings for Windows5.5.5.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!


16 (114)

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.


17 (114)

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.


18 (114)

After defining SSH related parameters, Press OK.

5.5.5.1.2 5.5.5.1.2 Configuration example for creating COM connection

Select Device > Set Configuration from menu.Following window appears


19 (114)

Note! COM connection is selected

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


20 (114)


Press OK.


21 (114)

5.5.5.2 Connection settings for Linux5.5.5.2.1 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.


22 (114)

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


23 (114)

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.


24 (114)

After defining SSH related parameters, Press OK.5.5.5.2.2 5.5.5.2.2 Configuration example for creating COM connection

Select Edit> Devices > from menuFollowing window appears


25 (114)

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


Press OK.


26 (114)

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 to execute. ClickingCANCEL in main menu aborts the macro execution.


27 (114)

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

Select ini file from the list.


28 (114)

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.


29 (114)

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:


30 (114)

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.


31 (114)

Select a step to run and press OK.


32 (114)

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.


33 (114)

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 ETIP1-A implementation forIP/PWE procedure. Follow then the macro execution according the BSC configuration printout document.


34 (114)

8 BSC ETIP1-A IMPLEMENTATION FOR IP/PWE IN CASE OFTRANSMISSION (LINE) REDUNDANCY

Transmission/line redundant ETIP unit will be implemented according to following picture:

Note!After ETIP installation (upgrade) as line protected mode, only ET16 plug-in units can be installed to GTIC-0/-1cartridges tracks 05-08.

8.1 Re-host traffic from concerning STMU/ET16 unit

Move traffic from old unit (ETS2/ET16) from where the new ETIP plug-in unit will be upgraded. More informationabout traffic restrictions can be found from chapter 5.1. The traffic can be re-directed back to new ETIP unit rightafter 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.


35 (114)

Note!In case of ETPs having the overlapping PCMs with destination ETIP, 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/ET16 interface configurations and equipment will be deleted.If affected PCM area is used by old configuration in ET16/STMU the interface(s) and hardware configuration fromthese units needs to be deleted. More instruction can be found from NED document Creating and managing BSCconfiguration.

Note!If chosen ETIP index is between 0-6 in GTIC-0, skip this interface/unit .Units are not needed to be deleted.

Note: In case of STMU/ET16/ETIP-as source the following window will be displayed.

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

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

Change ET16 / STMU located in track which is going to be upgraded to SE-NH state.


36 (114)

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

Check transmission protection groups with following command:ZYWI;

Delete existing transmission protection groups from STMU(s).ZYWD:;

Delete ET equipment related to ETS2 or ET16 unit.

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

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

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

Delete STMU unit.ZWUD:STMU,:ETS2,;ZWTQ:STMU,:ETS2,;ZWTV:STMU,;

8.3 Make cabling changes, install ETIP1-A plug-in unit and connect cables related toMCMU,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).

Blocking can be done with commandZABB:1340;

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

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

Install ETIP1-A plug-in unit to correct GTICs track. This step needs to be done manually. Replace ETS2/ET16plug-in unit with ETIP1-Aif it exists:

Temporarily remove hotlink cables from ETS2 plug-in unit. Remove ETS2 plug- in unit and install new ETIP1-Aplug-in unit to correct GTICs track.

Make cabling changes to MCMU-0 according to appendixes:

GTIC & ETC PCM usage in case of BSC3i 1000/2000 and upgraded Flexi BSC transmission/lineredundancy

GTIC & ETC PCM usage in case of new delivery Flexi BSC transmission/line redundancy


37 (114)

8.4 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.5 Make cabling changes, connect cables related to MCMU-1

Change MCMU-0 and EMB-0 state to WO-EX and make MCMU-1, 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:SP;ZUSC:EMB,0:WO;

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


Make cabling changes to MCMU-1 according to appendixes:

GTIC & ETC PCM usage in case of BSC3i 1000/2000 and upgraded Flexi BSC transmission/lineredundancyGTIC & ETC PCM usage in case of new delivery Flexi BSC transmission/line redundancy

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

Check and make changes to SW256B DIP-switches related to upgraded track according to appendix5.ZUSC:MCMU,1:SE;ZUSC:MCMU,1:TE;ZUSC:MCMU,1:SP;

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

8.7 New ETIP configuration & equipment with transmission/line protection

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

8.7.1 Equip new redundant ETIP units

Create ETIP unitZWTU:ETIP,:;

Create ETIP1-A plug-in unitZWTP:ETIP,:ETIP1_A,0,::LAPD,8,,TSL,;


38 (114)

See Appendix11: ETIP&EET/ET indices & control PCM(s) when transmission redundancy is in usefor plug-in unit PCM information.

Connect ETIP plug-in unitZWUC:ETIP,:ETIP1_A,0::BCSU,;

8.7.2 Create new ET units

In this step, ETIP ET eets are created.Use Appendix11: ETIP&EET/ET indices & control PCM(s) when transmission redundancy is in use for plug-in unitPCM information.

Create ET unitsZWTU:ET,::UNIT=ETIP,IND=;

Create ET plug-in unitsZWTP:ET,:ETIP1_A,0,::ETT00,8,,TSL,0:;

Connect ET plug-in units (manually):ZWUC:ET,:ETIP1_A,0:IF=:BCSU,:;

8.7.3 Change new ETIP units to WO-EX state

Change ETIP units state back to WO-EX state with following commands:ZUSC:ETIP,:SE;ZUSC:ETIP,:TE;ZUSC:ETIP,:WO;

Check ETIP units software version with following command:ZDDE::"ZMXP:W0-BLCODE/LNX*.IMG"

IMPORTANT!If more ETIP units are planned to be upgraded, do the chapters 8.1-8.7 again. In case of last ETIP upgrade,remember to unblock the alarm 1340 manually.

Unblock alarm 1340 (Hotlink failure) with following command:ZABU:1340;

8.7.4 Configuring the IPManually, configuring the IP can be made following the document: PWT User Guide (chapter 4). The documentcan be found from NED.

8.7.5 Configuring the PWManually, configuring the IP can be made following the document: PWT User Guide (chapter 5). The documentcan be found from NED.

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


39 (114)

ZUDU:MCMU,0;

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


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

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


40 (114)

9 BSC ETIP1-A IMPLEMENTATION FOR IP/PWE IN CASE OF HW REDUNDANCY

HW redundant ETIP unit will be implemented according to following picture:

Macro upgrades all the ETIP units one by one, starting from the lowest ETIP index.Each ETIP units upgrade may effect to PCM areas which are e.g. already used by ET16, ETS2 or transmissionredundant ETIP. See Appendix 6,7,8 for more information. Overlapping PCM areas are marked with same colour.

GTIC 1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

GTIC 0

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

OPR

ETIP

1

1st four activeHotlinks and correspondingspare Hotlinks (8 + 8 pcs)

EET

ETIP

ETIP 0

ETIP 2

ETIP 4

ETIP 6

ETIP 9

ETIP 11

ETIP 13

ETIP 15

ETIP 1

ETIP 3

ETIP 5

ETIP 7

ETIP 8

ETIP 10

ETIP 12

ETIP 140

2nd four activeHotlinks and correspondingspare Hotlinks (8 + 8 pcs)

Flexi BSCS14 equipment redundancy #1 for ETIP1-A: moving 16 pcs old Hotlink cables /4 last redundancy pairs & 16 pcs old Hotlink cables remain / 4 first redundancy

pairs & adding 32 new Hotlink cables

ETIP2

Active

Spare

Active

Spare

Active Spare

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

GSW 0GSW 1

0 4 8 12 18 22 26 30 2 6 10 14 16 20 24 28


41 (114)

Fig-1The above figure displays the destination configuration with 9-ETIP

IMPORTANT!When traffic lost is wanted to stay as minimum as possible, then the order of upgraded ETIP indexes should befollowing:1. ETIP-02. ETIP-83. ETIP-24. ETIP-105. ETIP-46. ETIP-127. ETIP-68. ETIP-149.ETIP-24

9.1 Re-host traffic from concerning unit (STMU/ETIP with transmission redundancyor ET16)

Move traffic from old unit (ETS2/ET16/ETIP) from where the new ETIP plug-in unit will be upgraded. Moreinformation about traffic restrictions can be found from chapter 5.1. The traffic can be re-directed back to newETIP 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 ETIP, macro will give a pop-up saying the PCMalready in use by ETP cards and these ETP card deletion is not supported.


42 (114)

9.2 Delete old configurations & equipment

In this step, all the old STMU/ET16/ETIP interface configurations and equipment will be deleted.

If affected PCM area is used by old configuration in ET16/STMU/ETIP the interface(s) and hardware configurationfrom these units needs to be deleted. More instruction can be found from NED document Creating andmanaging BSC configuration.

NOTE: the following Pop-up window is an example .Select the respective track from the GTIC-0 to make it HW-Redundant

Note: In case of STMU/ET16/ETIP-as source the following window will be displayed.

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


43 (114)

Change ET16, STMU or ETIP located in track which is going to be upgraded to SE-NH state.ZUSC:,:BL;ZUSC:,:TE;ZUSC:,:SE;ZUSC:,:SE;

If ET16 units exist in effected tracks (see table in chapter 9), the hardware from equipment database is deletedwith following commandsZWUD:ET,&&:ZWTQ:ET,&&:ZWTV:ET,&&;

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

Delete existing transmission protection groups from STMU(s) - also from STMU located in GTIC-1 cartridge.ZYWD:;

Delete ET equipment (SET) related to STMU unit. Delete both cartridge STMUs ET groups.

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

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

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

Disconnect ETIP unit(s)ZWUD:ETIP,:ETIP1_A,0;

Delete plug-in unit(s)ZWTQ:ETIP,:ETIP1_A,0;

Delete unit(s). ZWTV:ETIP,;

Note :- If Source configuration is ETIP Transmission redundancy then delete ETIP unit from GTIC-1 firstand then proceed for 9.3.

9.3 Make cabling changes, install redundant ETIP1-A plug-in unit and install newcables 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 9).

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;


44 (114)

ZUSC:EMB,0,SE;

Install ETIP1-A plug-in unit to correct GTICs track. This step needs to be done manually. Replace ETS2 /ET16plug-in unit with ETIP1-Aif it exists.


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

MCMU,0 related cablings in New Delivery Flexi BSC

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

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

9.5 Make cabling changes, install new cables related to MCMU-1

Change MCMU-0 and EMB-0state 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:SP;ZUSC:EMB,0:WO;

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


Install ETIP1-A plug-in unit to correct GTICs track. This step needs to be done manually. Replace ETS2 /ETIPplug-in unit with ETIP1-A if it exists.


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

9.6 Make DIP-switch changes to SW256B in MCMU,1

Check and make changes to SW256B DIP-switches related to upgraded track according to appendix5.ZUSC:MCMU,1:SE;ZUSC:MCMU,1:TE;ZUSC:MCMU,1:SP;

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


45 (114)

9.7 New ETIP configuration & equipment with HW redundancy

In this chapter, all the equipment commands for creating HW redundant ETIP unit with corresponding ET units aregiven. In case of manual execution, choose the correct ETIP index to be equipped according the picturepresented in the beginning of chapter 9.

9.7.1 Equip new ETIP units

Create ETIP unitZWTU:ETIP,:;

Create ETIP1-A plug-in unitZWTP:ETIP,:ETIP1_A,0,::LAPD,8,,TSL,;


Connect ETIP plug-in unitZWUC:ETIP,:ETIP1_A,0::BCSU,;

Create redundant ETIP unitZWTU:ETIP,:;

Create redundant ETIP1-A plug-in unitZWTP:ETIP,:ETIP1_A,0,::LAPD,8,,TSL,;


Connect redundant ETIP plug-in unitZWUC:ETIP,:ETIP1_A,0::BCSU,;

9.7.2 Create new ET units

In this step, ETIP ET eets are created for GTIC-0 and for GTIC-1 cartridges new ETIP units.

Use Appendix11: ETIP&EET/ET indices & control PCM(s) when transmission redundancy is in use for plug-in unitPCM information.

Create ET unitsZWTU:ET,::UNIT=ETIP,IND=;

Create ET plug-in unitsZWTP:ET,:ETIP1_A,0,::ETT00,8,,TSL,0:;

Connect ET plug-in units (manually):ZWUC:ET,:ETIP1_A,0:IF=:BCSU,:;

9.7.3 Change new ETIP units to WO-EX state

Change ETIP units state in both cartridges to WO-EX state with following commands:ZUSC:ETIP,:SE;ZUSC:ETIP,:TE;ZUSC:ETIP,:WO;


46 (114)

IMPORTANT!If more ETIP units are planned to be upgraded, do the chapters 9.1-9.7 again. In case of last ETIP upgrade,remember to unblock the alarm 1340 manually.

Unblock alarm 1340 (Hotlink failure) with following command:ZABU:1340;

9.8 Configuring the IP

Manually, configuring the IP can be made following the document: PWT User Guide (chapter 4). The documentcan be found from NED.

9.9 Configuring the PW

Manually, configuring the IP can be made following the document: PWT User Guide (chapter 5). The documentcan be found from NED.

9.10 MCMU diagnostic

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

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



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



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


47 (114)

10 COPY THE HW EQUIPMENT DATABASE INFORMATION TO THE DISK (DBC)

ZDBC:EQUIPM,0;


48 (114)

11 ACTIONS AFTER UPGRADE & POST CONDITIONS

11.1 BSS Integration

After BSC ETIP1-A implementation for IP/PWE upgrade, make BSC integration for upgraded units according BSSintegration. The document can be found from NED.

11.2 BSC configuration printout (post-check)

The information about the BSC configurations and conditions are collected.

The checking 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 (post) step in BSC ETIP1-A implementation forIP/PWE procedure. Follow then the macro execution according the BSC configuration printout document.

11.3 Return to the old HW configuration

If return to old HW configuration is needed, follow the instructions in this document in the reverse order. Oractivate fallback build taken before HW upgrade and change cablings according the Cablings instructions forBSC3i which can be found from NED.


49 (114)

12 APPENDIX

12.1 Appendix1: MCMU,0 related cablings in BSC3i 1000/2000 or upgraded FlexiBSC3i

Note!Part List includes only four Hotlink cables. The cables will be delivered to the site and added to cabinet accordingto upgrading procedure.

BSCC_1200 -BSCC_1203 cable markings/labels are attached as default to the cables included in parts list. OtherBSCC cabinet related cable markings (28 pcs) are delivered unattached and will be delivered to the site andadded to cabinet according to upgrading procedure.

1) Track 1

Remove following cables from GTIC-side:Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use Note

BSCC_726 GTIC 1 5.9F 01.SB1-0 GSW2KB 0 1.0F 06.SB2-0 CSB027 HotlinkBSCC_727 GTIC 1 5.9F 01.SB2-0 GSW2KB 0 1.0F 07.SB2-0 CSB027 Hotlink

Add following new cablings and change SW256B DIP-switches according to appendix 5:Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use Note


Connect redundancy cable as following:Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use Note

BSCC_1240 GTIC 0 5.6B 01.4A GTIC 1 5.9B 01.4A CHFX006 2NBSCC_1241 GTIC 0 5.6B 01.4G GTIC 1 5.9B 01.4G CHES006 2N

NOTE: Connect ADMOD23 setting modules (in GTIC 0 connector positions B 10.4E B 13.4E and GTIC 1connector positions B 14.4E B 17.4E)

Note!Use locking pegs according to appendix9 or appendix10 if needed.

2) Track 2

Remove following cables from GTIC-side: Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use Note




Connect redundancy cable as following:


50 (114)

Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use Note



3) Track 3








4) Track 4Remove following cables from GTIC-side: Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use Note







51 (114)


5) Track 5

Re-connect following cablings:Equipping CABLE FROM CABLE TONo FU Old Position New Position FU Position Type Use Note

BSCC_726 GTIC 1 5.9F 01.SB1-0 5.9F 05.SB1-0 GSW2KB 0 1.0F 06.SB2-0 CSB027 HotlinkBSCC_727 GTIC 1 5.9F 01.SB2-0 5.9F 05.SB2-0 GSW2KB 0 1.0F 07.SB2-0 CSB027 Hotlink



Connect redundancy cables as following:Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use NoteBSCC_1248 GTIC 0 5.6B 05.4A GTIC 1 5.9B 05.4A CHFX006 2NBSCC_1249 GTIC 0 5.6B 05.4G GTIC 1 5.9B 05.4G CHES006 2N


6) Track 6



Add following new cablings and change SW256B DIP-switches according to appendix 5:



Connect redundancy cables as following:Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use NoteBSCC_1250 GTIC 0 5.6B 06.4A GTIC 1 5.9B 06.4A CHFX006 2NBSCC_1251 GTIC 0 5.6B 06.4G GTIC 1 5.9B 06.4G CHES006 2N


7) Track 7


52 (114)





Connect redundancy cables as following:Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use Note



8) Track 8









53 (114)

12.2 Appendix2: MCMU,1 related cablings in BSC3i 1000/2000 or upgraded FlexiBSC3i

Note!Part List includes only four Hotlink cables. The cables will be delivered to the site and added to cabinet accordingto upgrading procedure.

BSCC_1200 -BSCC_1203 cable markings/labels are attached as default to the cables included in parts list. OtherBSCC cabinet related cable markings (28 pcs) are delivered unattached and will be delivered to the site andadded to cabinet according to upgrading procedure.

1) Track 1






2) Track 2






3) Track 3




54 (114)




4) Track 4Remove following cables from GTIC-side: Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use Note





5) Track 5






6) Track 6




55 (114)




7) Track 7





Note!Use locking pegs according to appendix 9 or appendix10 if needed.

8) Track 8



Add following new cablings and change SW256B DIP-switches according to appendix 5:





56 (114)

12.3 Appendix3: MCMU,0 related cablings in New Delivery FlexiBSC3i

Note!BSCC_3000 -_ 3003 cable markings/labels are attached as default to the cables included in parts list. OtherBSCC cabinet related cable markings (28 pcs) are delivered unattached and will be delivered to the site andadded to cabinet according to upgrading procedure.

Notes:1) These cables are not included in part list.2) These cables have been delivered with Cabinet Type. Slot by slot i.e. redundancy pair by redundancy

pair the GTIC 1 ends of these cables (redundancy pair specific 1 pcs CHFX and 1 pcs CHES) are to beconnected if transmission redundancy is upgraded to HW redundancy.

Remove following cables from GTIC-side:Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use NoteBSCC_420 GTIC 1 2.0F 10.SB1-0 GSW2KB-A 0 1.0F 08.SB3-0 CSB012 HotlinkBSCC_421 GTIC 1 2.0F 10.SB2-0 GSW2KB-A 0 1.0F 08.SB4-0 CSB012 Hotlink




BSCC_470 GTIC 0 1.0B 10.4A GTIC 1 2.0B 10.4A CHFX020 2N 1),2)BSCC_471 GTIC 0 1.0B 10.4G GTIC 1 2.0B 10.4G CHES020 2N 1),2)

2) Track 11


BSCC_424 GTIC 1 2.0F 11.SB1-0 GSW2KB-A 0 1.0F 04.SB1-0 CSB010 HotlinkBSCC_425 GTIC 1 2.0F 11.SB2-0 GSW2KB-A 0 1.0F 04.SB2-0 CSB011 Hotlink


BSCC_3004 GTIC 1 2.0F 11.SB1-0 GSW2KB 0 1.0F 07.SB1-1 CSB012 Hotlink 1)BSCC_3005 GTIC 1 2.0F 11.SB2-0 GSW2KB 0 1.0F 07.SB2-1 CSB013 Hotlink 1)




57 (114)

3) Track 12





Connect redundancy cable as following:Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use NoteBSCC_474 GTIC 0 1.0B 12.4A GTIC 1 2.0B 12.4A CHFX020 2N 1),2)BSCC_475 GTIC 0 1.0B 12.4G GTIC 1 2.0B 12.4G CHES020 2N 1),2)

4) Track 13







5) Track 14

Re-connect following cables:Equipping CABLE FROM CABLE TONo FU Old Position New Position FU Position Type Use Note

BSCC_420 GTIC 1 2.0F 10.SB1-0 2.0F 14.SB1-0 GSW2KB-A 0 1.0F 08.SB3-0 CSB012 HotlinkBSCC_421 GTIC 1 2.0F 10.SB2-0 2.0F 14.SB2-0 GSW2KB-A 0 1.0F 08.SB4-0 CSB012 Hotlink


58 (114)





6) Track 15

Re-connect following cablings:Equipping CABLE FROM CABLE TONo FU Old Position New Position FU Position Type Use NoteBSCC_424 GTIC 1 2.0F 11.SB1-0 2.0F 15.SB1-0 GSW2KB-A 0 1.0F 04.SB1-0 CSB010 HotlinkBSCC_425 GTIC 1 2.0F 11.SB2-0 2.0F 15.SB2-0 GSW2KB-A 0 1.0F 04.SB2-0 CSB011 Hotlink





7) Track 16






59 (114)



8) Track 17







9) Track 21


BSCC_416 ETC 0 1.0F 14.SB1-0 1.0F 21.SB1-0 GSW2KB-A 0 1.0F 02.SB1-0 CSB007 Hotlink 1)BSCC_417 ETC 0 1.0F 14.SB2-0 1.0F 21.SB2-0 GSW2KB-A 0 1.0F 02.SB2-0 CSB012 Hotlink 1)


BSCC_3032 ETC 2 2.0F 21.SB1-0 GSW2KB 0 1.0F 02.SB1-1 CSB006 Hotlink 1), 11)BSCC_3033 ETC 2 2.0F 21.SB2-0 GSW2KB 0 1.0F 02.SB2-1 CSB006 Hotlink 1), 11)



60 (114)

Equipping CABLE FROM CABLE TONo FU Position FU Position Type Use NoteBSCC_486 ETC 0 1.0B 21.4A ETC 2 2.0B 21.4A CHFX017 2N 1),2)BSCC_487 ETC 0 1.0B 21.4G ETC 2 2.0B 21.4G CHES017 2N 1),2)


61 (114)

12.4 Appendix4: MCMU,1 related cablings in New Delivery FlexiBSC3

Documents

BSC ETIP1-A Implementation for IP PWE Ver1 7 0