bsc implementation for etp_etp-a_in initial flexi bsc_ver 1_12

DN09124902BSCImplementationforETP/ETP-AininitialFlexiBSCCopyright2013NokiaSolutionsandNetworks.Allrightsreserved.CONFIDENTIALAPPROVED1.121 (207)

BSC Implementat ion forETP/ETP-A in Initial FlexiBSCRelease Delivery: HW UpgradeProduct Family: Radio ControllersProduct: Flexi BSCRelease: S16 onwards

Approval date: 12-Dec-2013

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 .................................................................................................................................................. 52 Scope of applications .............................................................................................................................. 63 Using the document ................................................................................................................................ 7

3.1 General info ....................................................................................................................................................... 73.2 Upgrade macro .................................................................................................................................................. 8

3.2.1 Structure ...................................................................................................................................... 83.2.2 Communication ............................................................................................................................ 8

4 Introduction ........................................................................................................................................... 105 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 Licence installation and feature activation .............................................................................................. 349 ETPLAN CONFIGURATION .................................................................................................................. 35

9.1 Make SWU units to passive state ..................................................................................................................... 369.2 Make SWU units to SE-NH state ...................................................................................................................... 369.3 Cabling changes .............................................................................................................................................. 36

9.3.1 Move and reconnect following cables .......................................................................................... 369.3.2 Add new configurations to ESB cards manually. .......................................................................... 36

9.4 Change topology ............................................................................................................................................. 379.5 Configure SWU 6 and 7 to the hw database...................................................................................................... 389.6 Check internal LAN index with command .......................................................................................................... 389.7 Add SWUs to the internal LAN ......................................................................................................................... 389.8 Change all SWUs state to the WO-EX .............................................................................................................. 389.9 Activate all SWU s back to use ......................................................................................................................... 38

10 Create ETPSIG-I IP address to MCMU and BCSU ................................................................................ 3911 Packet Abis over Ethernet(ETPE), PIU type ETP ................................................................................... 40

11.1 Creation of ETPE unit with transmission/line protection ..................................................................................... 4011.1.1 Install Plug-in units, terminators and cables ................................................................................. 4111.1.2 Create HW configuration ............................................................................................................ 5211.1.3 Check Plug-in unit software ........................................................................................................ 5511.1.4 Diagnostic .................................................................................................................................. 5711.1.5 Check PCU configuration ........................................................................................................... 58

11.2 Creation of ETPE unit with hardware protection ................................................................................................ 5811.2.1 Install Plug-in units, terminators and cables ................................................................................. 5811.2.2 Create HW Configuration ............................................................................................................ 7611.2.3 Check Plug-in unit software ........................................................................................................ 8211.2.4 Diagnostic .................................................................................................................................. 8411.2.5 Check PCU configuration ........................................................................................................... 84

12 Packet Abis over TDM (ETPT), PIU type ETP........................................................................................ 8612.1 Creation of ETPT unit with transmission/line protection. .................................................................................... 86

12.1.1 Install Plug-in units, terminators and cables ................................................................................. 8712.1.2 Create HW configuration .......................................................................................................... 10012.1.3 Check Plug-in unit software ...................................................................................................... 11012.1.4 Diagnostic ................................................................................................................................ 11212.1.5 STMU s to WO-EX state ........................................................................................................... 11212.1.6 Check PCU configuration ......................................................................................................... 113


12.2 Creation of ETPT unit with hardware protection .............................................................................................. 11312.2.1 Install Plug-in units, terminators and cables ............................................................................... 11412.2.2 Create HW configuration .......................................................................................................... 13912.2.3 Check Plug-in unit software ...................................................................................................... 15312.2.4 Diagnostic ................................................................................................................................ 15512.2.5 STMU s to WO-EX state ........................................................................................................... 15512.2.6 Check PCU configuration ......................................................................................................... 156

13 A over IP (ETPA), PIU type ETP-A ...................................................................................................... 15713.1 Creation of ETPA unit .................................................................................................................................... 157

13.1.1 Install Plug-in units and cables .................................................................................................. 15713.1.2 Create HW configuration .......................................................................................................... 16313.1.3 Check Plug-in unit software ...................................................................................................... 16413.1.4 Diagnostic ................................................................................................................................ 167

14 A over IP (ETPA), PIU type ETP .......................................................................................................... 16814.1 Creation of ETP(A) unit .................................................................................................................................. 168

14.1.1 Check the source configuration for overlapping Plug-in units...................................................... 16814.1.2 Deleting the interface and unit In case the upgrade is done to swap existing ETP-A withETP 16814.1.3 Install Plug-in units and cables .................................................................................................. 16814.1.4 Create HW configuration .......................................................................................................... 17814.1.5 Check Plug-in unit software ...................................................................................................... 18114.1.6 Diagnostic ................................................................................................................................ 183

15 Copy the HW equipment database information to the disk (DBC) ......................................................... 18516 Actions after upgrade & Post conditions .............................................................................................. 186

16.1 BSS Integration ............................................................................................................................................. 18616.2 BSC configuration printout (post-check) .......................................................................................................... 18616.3 Return to the old HW configuration ................................................................................................................. 186

17 Appendix : ........................................................................................................................................... 18717.1 Appendix 1: SW 256B Dip switch settings ....................................................................................................... 187

17.1.1 SW256B jumper settings .......................................................................................................... 18717.1.2 PCM mode settings (SW1) ....................................................................................................... 18717.1.3 Interchangeability code settings (SW2) ..................................................................................... 18817.1.4 Serial Broadband SB1 settings (SW3) ....................................................................................... 18817.1.5 Serial Broadband SB2 settings (SW4) ....................................................................................... 19017.1.6 Serial Broadband SB3 settings (SW5) ....................................................................................... 19117.1.7 Serial Broadband SB4 settings (SW6) ....................................................................................... 191

17.2 Appendix 2: GTIC & ETC PCM usage in case of initial delivery Flexi BSC ....................................................... 19217.3 Appendix 3: Update ESBs with latest software ................................................................................................ 198

17.3.1 Update ESB Software............................................................................................................... 19817.3.2 Enabling or disabling the automatic loading of configuration files ............................................... 198

17.4 Appendix 4: ETP/STMU strapping settings. .................................................................................................... 19917.4.1 ETP-A C111828 ....................................................................................................................... 19917.4.2 ETP C111826 .......................................................................................................................... 20117.4.3 ETS2 ....................................................................................................................................... 202

17.5 Appendix 5: ETP username & password settings ............................................................................................ 204

Contact:

Contact your local Nokia Solutions and Networks support

Summary of changes:

12-Dec-2012 0.1-0 Creation date12-Dec-2012 1.0-0 Approval date21-Dec-2012 1.1-0 Added PIU update for mate STMUs in chapters 12.1.5

and 12.2.5.Updated subchapter titles under chapters11.1.1 ,11.2.1 ,12.1.1,12.2.1,13.1.1and 14.1.3.


Removed chapters 9.4 and 9.11 as part of CR1004implementation.

16-Jan-2013 1.2-0 Added CR75 details01-Feb-2013 1.3-0 Added connection settings for Linux in chapter 5.5.5.218-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.227-Feb-2013 1.5-0 Updated chapter 9.4 with topology details.Added note

on IuA messaging configuration for all ETP variants04-Apr-2013 1.6-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.Updated appendix 5

02-Jul-2013 1.7-0 Updated chapter 1025-Sep-2013 1.8-0 Template update21-Feb-2013 1.9-0 Updated chapter 9.4, 11.2 and 12.2 related to pronto

81810ESPE03. Added note Create the PEP link toETPGID 0 first if you want to get the ETP object ID forthe ETPGID to match in NetAct in chapter 11.1.2,11.2.2, 12.1.2 and 12.2.2.

20-Mar-2014 1.10-0 Updated note in chapter 5.407-Oct-2014 1.11-0 The purpose text in Appendix 5 updated.23-Oct-2014 1.12-0 Chapter 9.4 updated.


1 PURPOSE

This document describes the implementation of ETP/ETP-A plug-in unit to the BSC environment. This documentdoes not support Combined TCSM3i part. That upgrade can be handled with TCSM implementation forETP/ETP-A procedure.

This document can be used with following environments:x FlexiBSC3000 (initial delivery)x FlexiBSC4200 (initial delivery)


2 SCOPE OF APPLICATIONS

The BSC implementation for ETP/ETPA in Initial Flexi BSC is available for Initial Flexi BSC 3000/4200 in S16release onwards.

The procedure cannot be executed without traffic interruption. Traffic must be moved from concerningETS2/ET16/ETIP plug-in unit before the actual upgrade.

Procedure must be performed locally at BSC site.


3 USING THE DOCUMENT

3.1 General info

The BSC implementation for ETP/ETP-A can be done using the HIT (Holistic Integration Tester) software tool.Optional way is to make the upgrade manually by following this documentation.

The SWU6 and SWU7 upgrade is done manually with the HIT macro. However procedure must be performedlocally at BSC site as there are cabling changes and IP address reallocation.

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

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

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

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


3.2 Upgrade macro

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

UPGMAIN.HITx Select wanted upgrade:

o SOFTWARE UPGRADES SW upgrade S15 -> S16

o HARDWARE UPGRADES

HW upgrade 1 HW upgrade 2

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

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

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

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

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

Note!Once, user enters from main menu to upgrade menu, only way to get back to the main menu is to restartwhole macro.3.2.2 CommunicationThe macro communicates with user by using the HIT Pop-up windows.

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

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

3.2.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:x Log file from HIT Response window (.log)

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


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

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

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

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

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

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

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


4 INTRODUCTION

The BSC implementation for ETP/ETP-A in Initial Flexi BSC procedure consists of the following tasks:

- Fallback copying of the current software

- BSC configuration printout (pre-check)

- Licence installation and feature activation

- BSC implementation for ETPE in case of transmission/line redundancy or HWredundancy

- BSC implementation for ETPT in case of transmission/line redundancy or HWredundancy

- BSC implementation for ETPA in case of Pool redundancy

- MCMU diagnostic

- 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 Initial FlexiBSC.

In case when old configuration needs to be removed, the traffic must be moved, interface(s) removed becausethe plug-in unit needs to be deleted from equipment database. After successful upgrade and interfaces has beencreated back, the traffic can be moved back.

Note: The ETPLAN configuration will affect BSCs IP related connectivity and existing traffic in Gb over IP,Sigtran, DFCA.

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 effected unit(s) willbe blocked and state changed to TE-EX or SE-NH.

There is a choice of several options how the GTIC and ETC cartridges has been equipped before upgrade. Thechoices depend on the PIU types and configurations, like following:x use ETP (either for ETPE or ETPT) plug-in unit with line or hardware redundancy.x use ETPA Plug-in unit with Pool redundancy.

Background Picture below describes the functioning of ETP plugin units:


Packet Abis and AoIP implementations are needed in BSC3i. These features require new ETP PIUs. In practisethe HW will be a couple of ETP variants (e.g. ETP and ETP-A), because of the variety of requirements concerninginterfaces and functions. Packet Abis makes possible to use a packet switched based transmission of signalingand traffic (payload) between BTS and BSC.

This allows cellular network operators to migrate from traditional static TDM to PSN, and the low-cost transport ofIP and Ethernet, in a more efficient and cost effective way than with the already available solution adopting PWE3CESoPSN.

The concept is anyway valid regardless of the underlying Layer 1 solution being TDM based or Ethernet based.As a matter of fact, most of the gains provided by Packet Abis will also be capitalized in case legacy TDMnetworks have still to be supported (e.g. smooth migration path); especially the bandwidth saving achieved byonly transferring packets that contain data, compared with the previous technology that required empty packets tomaintain a constant bit rate.

ETP terminates Packet Abis in the BSC

AoIP provides A-interface u-plane and c-plane connections between BSS and CN over IP. SIGTRAN signalling isused for the c-plane. RTP payload formats for different speech codecs and CS data/fax are used in the u-plane.A over IP is standardized in 3GPP.

There are two architecture options:

1. The Transcoder function is located in the BSS (that is, the standard GSM architecture). The Transcoder is theA over IP termination point.

2. The Transcoder function is located in the Core Network (that is, the 3G network architecture). The BSC is the Aover IP termination point. At the same time, the BSC hides the mobility from the Core Network

In both cases the ETP terminates the A over IP u-plane.

PCU2-D

BSC

IP-BTSPacket Abisover TDM

(STM-1/OC-3)

GSWB

A over IPTC in MGW

TCSM3i

MGW

A over IPTC in BSS

IP-BTS

Packet Abisover Ethernet

ETTCSM2i,TCSM3ior MGW

TDMAter

ET

TDMAter

MGWESB24s

ETBTSDynamic Abis

PCU2-E* )

*) PCU2-E uses internalLAN for ETP

connectivity.

SET

SET

TCSM3i

MGW

A over IPTC in BSS

BCSUsm/c planeto ETPs

Packet-switchednetwork

Packet-switchednetwork

Sn+pair

Sn+group

SBMUX

TR3sETPT

ETPE

ETP

ETPA

ETP-A

ETS2

STMUETP

ETPTETPE1/

T1

GigE

GigE

GigE

GigE

ETP

Sn+pair

Sn+pair

Sn+pair

ETPC

ETP-A

Sn+pair

ETPC

ETP-A

Sn+pair


5 PRE-REQUIREMENTS

5.1 Pre-requirements & Actions needed prior upgrade

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

Note!1. L3 configuration in BSC is mandatory when ETPA,ETPE and/or ETPT are used.2. SW licence and licence for L3 functionality for SWU unit is needed to be installed before actual

upgrade can be started.3. T5 topology should be active in Initial Flexi delivery BSC before starting upgrade.4. Following configurations should be ready before starting upgrade to minimise downtime.5. 1. IP Address Plan.6. 2. SWU configurations from SWU-0 to SWU-7. Which includes Vlan, MSTP, OSPF/Static route; VRRP

and interface configurations to equip ETPs as well as other IP based applications.7. 3. Site Switch configuration.8. 4. All required upgrade cable kits.

IMPORTANT!Re-direct traffic from STMU/ETIP/ET16 cards in GTIC and ETC cat ridges before actual upgrade. Each ETPunit must be handled case by case and PCM areas which are affected during upgrade may vary. In caseupgrade causes disturbances to some other unit, the traffic needs to be re-directed, interfaces removedand unit needs to be deleted (PCM areas released to new ETP unit usage) from hardware database beforenew 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 / Net Actrepresentatives.

5.2 Restrictions

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 ETP unit the traffic can be re-directed back.


5.3 Needed documentation

To perform the upgrade successfully, the following documentation is required:x BSC implementation for ETP/ETP-A in Initial Flexi BSC (this document).x L3 BSC IP Site Connectivity upgradex Plug-in unit software upgrade procedurex Creating and managing BSC hardware (NED)x Cabling Instructions for Flexi BSC(NED)x Equipment list for Flexi BSC (NED)x Pre-Processor Program Informationx Fallback copying instructions of DX200 BSC for S16 (NED)x Technical Support Note: Minimum HW Requirements for BSC S1xx Releasex HIT Users manualx BSC Site IP Connectivity Guidelines and BSC Site IP Configuration Examples (NED documents).x Firmware change and memory upgrade document

5.4 Needed equipment

To perform the upgrade successfully, the following HW are required:x PC with installed HIT and upgrading macrosx Upgrade Set for upgrading transmission redundancy to HW redundancy for ETP plug in units in

BSC installation

x Set required to implement either transmission redundancy or HW redundancy for ETP plug in unitsin BSC installation for the first time

x Note: ETP card is used as ETPE ( Packet Abis over ETH) and ETPT (Packet Abis over ETH)x Needed amount of ETP/ETP-A plug in unitsx Note: Interchangeability E of ETS2 unit brings support for Packet Abis over TDM-

functionality.

5.5 HIT and upgrade macros

5.5.1 System requirements for HITHIT 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 HITIt 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 SW Release Binder found from NOLS (Nokia Online Services). Theinstallation of the software is done by executing the SETUP.EXE -program and following the instructions of theinstallation program.


5.5.3 Installing HIT upgrading macros

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

To install the macros into PC, specify the folder to which the macros will be installed, press Unzip and the macroswill be installed.This zipped executable file includes the whole upgrade macro and the needed directory structure. The only userexecutable file, UPGMAIN.HIT, is extracted to root directory of macro folder HIT settings

5.5.4 HIT settings

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

1. Start Control Panel

2. From Control Panel select System

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

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

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

6. In Port Settings select Advanced

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

8. Close all the opened dialogs by pressing OK

When opening the HIT program the first time, remember to check/create the used device (ref. Hitguide.doc). It isrecommended to use the network element name for the devices.5.5.5 Connection settingsWhen opening the HIT program the first time, remember to check/create the used devices (ref. Hitguide.doc).When the macro is started, the available devices are listed to select device to be connected.

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

Note: in S16 level, via Netact (SSH) is only allowed.5.5.5.1 Connection settings for Windows5.5.5.1.1 Configuration example for creating Telnet / SSH / NetAct connection

Select Device > Set Configuration from menu.Following window appears


Select New

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


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

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


Select Terminal sheet and define the MML log file.

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


After defining SSH related parameters, Press OK.

5.5.5.1.2 Configuration example for creating COM connection

Select Device > Set Configuration from menu.Following window appears


Note! COM connection is selected

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



Press OK.


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

Select Edit> Devices > from menuFollowing window appears

Select New

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

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


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


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


If connection type is Telnet, press OK.

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


After defining SSH related parameters, Press OK.

5.5.5.2.2 Configuration example for creating COM connection

Select Edit> Devices > from menuFollowing window appears


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


Press OK.


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

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

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


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

Select ini file from the list.


Select target network element from the list.

Note!

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

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


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

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

ZWQO:RUN;

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

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


The status can be changed to BU with command:

ZWSC:STAT=NW:STAT=BU;

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

ZAHO;ZABO;ZEOL;ZEOE;

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

Some environment information (status) is checked with following commands:

ZQRI;ZIWQ:,OMU:WS=0,;ZDCD;ZUSI:ALL;ZWTI:P:OMU;ZUSI:BCSU;ZWTI:P:GSW,0;ZYE?

This information is gathered for BSC type analysis.

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


The procedure dialog is divided in main chapters, which may also contain sub-chapters. Chapters and their sub-chapters correspond directly to the document. Select the chapter to run and press OK.Note!In order to complete upgrade successfully, the chapters and steps must be executed in ascending order.

Select a step to run and press OK.


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.

Take running configurations from each SWU units seperately. Refer BSC Site IP Connectivity Guidelines for this.


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 S1xx Release Binder.

For macro execution, choose the BSC configuration printout (pre) step in BSC implementation for ETP/ETP-A inInitial Flexi BSC procedure. Follow then the macro execution according the BSC configuration printout document.


8 LICENCE INSTALLATION AND FEATURE ACTIVATION

SW licence is needed to be installed before actual upgrade can be started.Macro checks the licence status and if licence is not installed properly the licence needs to be installed manuallyaccording to following instructions.

x ZW7M: FEA=1533:ON; (PA over Ethernet)x ZW7M: FEA=1535:ON; (PA over TDM)x ZW7M: FEA=899:ON;( L-NWP IUA)x ZW7M: FEA=1234:ON;(L3 functionality for ESB switch)x ZW7M: FEA=1753:CONF; (Ao IP, TC in MGW)

Note: - The feature 1753 should be put in CONF state.The feature can be turned ON once the installation ofETPA/ETP(A) and MSS/MGW configurations are completed.

Licence state can be printed with following command:ZW7I:FEA,FULL:FEA=1533;

ZW7I:FEA,FULL:FEA=1533;FlexiBSC LION 12345 2010-09-13 14:50:48FEATURE INFORMATION:---------------------------------------------- FEATURE CODE:..............1533 FEATURE NAME:..............Packet Abis over IP/Ethernet FEATURE STATE:.............ON COMMAND EXECUTED If licence state is OFF, change the state to ON with following command:

ZW7I:FEA=1533:ON;

If licence is not installed, install the new licence file with the command:ZW7L::ON;


9 ETPLAN CONFIGURATION

This step introduces how to install SWU-6 and SWU-7 if not installed.

Install ESB24-D cards to the LANU-0 and LANU-1 cartridges to track

for ini Flexi BSC.

Install ESB24-D cards to LANU-0 and LANU-1:

Initial flexi BSC

SWU indexCartridgeposition

Unit Cartridge/ Slots

6 1A4-3 LANU-0 15

7 1A5-3 LANU-1 15

Note: The traffic will be impacted during ESB configuration and cabling changes. IP plan for each SWU unitsshould be ready before proceeding next step. All SWU units needs to be configured when making ETPLANcabling changes.

Following applications will not be available during upgrade. Please plan the traffic accordingly.

1. LDI2. Sigtran3. GBoverIP4. BBI(DFCA)5. Lb6. VNP7. OSI(Q3)8. Telnet & FTP9.

Traffic will be resumed after completion of chapter 9.This activity will take approximately 6 hours to complete.

The following topology is required for BSC type.

1. Initial flexi BSC - T5 to T9 topology

Note:

Make sure that the SWUs are updated with latest software. Refer Appendix 3 for more details.

Also restore automatic configuration download settings if software upgrade is done for ESB cards manually. Donot do restore factory defaults when doing new configuration to ESB cards manually. This again will disable thealready enabled L3 license on the ESBs. If you wish to start doing new configurations by doing restore factorydefaults first, then you need to enable the L3 license.


9.1 Make SWU units to passive state

ZW6E:SWU,0:P; ZW6E:SWU,1:P; ZW6E:SWU,2:P; ZW6E:SWU,3:P; ZW6E:SWU,4:P; ZW6E:SWU,5:P;

9.2 Make SWU units to SE-NH state

ZUSC:SWU,:TE-EX; ZUSC:SWU,:SE-OU; ZUSC:SWU,:SE-NH;

9.3 Cabling changes

Mark outgoing uplink cables in top of CPRJ45-A and take those out from connectors.

Install needed cables (management, redundant etc) to new ESB24-D cards.

9.3.1 Move and reconnect following cablesEquipping CABLE FROM CABLE TO

No FU Old Position NewPosition

FU Old Position NewPosition

Type Use Note

BSCC_116 LANU 0 4.0B 12.1A 4.0B 13.1C LANU 0 4.0B 13.1A 4.0B 15.2V CHES007 LAN LDI

BSCC_146 LANU 1 5.0B 12.1A 5.0B 13.1A LANU 1 5.0B 13.1A 5.0B 15.2T CHES007 LAN LDI

BSCC_450 LANU 0 4.0F13.ETH2

- LANU 0 4.0F14.ETH2

4.0F14.ETH1

CNIX006 LAN LDI


- LANU 1 5.0F14.ETH2

5.0F14.ETH1

CNIX006 LAN LDI


4.0F14.ETH23

LANU 1 5.0F12.ETH24

5.0F14.ETH23

CLC017 LAN Redund.


4.0F14.ETH24

LANU 1 5.0F13.ETH24

5.0F14.ETH24

CLC017 LAN Redund.

9.3.2 Add new configurations to ESB cards manually.

Refer BSC Site IP Connectivity Guidelines and BSC Site IP Configuration Examples document for this.

Add following cables

Equipping CABLE FROM CABLE TO

No FU Position FU Position Type Use Note

BSCC_3480 LANU 0 4.0B 12.1A LANU 0 4.0B 15.1A CHES008 LAN LDI


BSCC_3481 LANU 0 4.0B 13.1A LANU 0 4.0B 15.2T CHES006 LAN LDI

BSCC_3483 LANU 1 5.0B 12.1A LANU 1 5.0B 15.1A CHES008 LAN LDI

BSCC_3485 LANU 1 5.0B 13.1C LANU 1 5.0B 15.2V CHES006 LAN LDI

BSCC_3486 LANU 0 4.0B 12.1E LANU 1 5.0B 12.1E CHES017 LAN Redund.

BSCC_3488 LANU 0 4.0B 13.1E LANU 1 5.0B 13.1E CHES017 LAN Redund.

BSCC_3489 LANU 0 4.0B 13.1G LANU 1 5.0B 13.1G CHES017 LAN Redund.

BSCC_3491 LANU 0 4.0F 13.ETH24

LANU 0 4.0F 14.ETH2

CNIX006 LAN LDI2)


LANU 1 5.0F 14.ETH2

CNIX006 LAN LDI2)


LANU 1 5.0 F15.ETH1

CLC017 LAN Redund.2)


LANU 1 5.0 F15.ETH2



LANU 1 5.0 F15.ETH23



LANU 1 5.0 F15.ETH24


Reconnect outgoing uplink cables back to top of CPRJ45-A.

9.4 Change topology

If the topology is not T9 in Initial Flexi BSC, change it with following command

ZW6G:T9;

There has been a recommendation that when ETPLAN is configured the O&M IP address of OMU is reconfiguredon VLAN-10 interface. Note that if host port VLAN tagging is used in OMU Ethernet interface then also the switchside port has to be configured as tagged. O&M IP address reconfiguration on VLAN interface when configuringETPLAN is not recommended anymore in the BSC site IP connectivity guidelines. O&M IP address on OMU cankeep on using the physical EL0 and EL1 interfaces.

In case of O&M traffic separation:

Enable OMU separation from O&M LAN using following command

ZW6K:ENA;


9.5 Configure SWU 6 and 7 to the hw database

ZWTU:SWU,6:1A4-3;ZWTP:SWU,6:ESB24_D,3,15;ZWTU:SWU,7:1A5-3;ZWTP:SWU,7:ESB24_D,3,15;

9.6 Check internal LAN index with command

ZWYI:L;

9.7 Add SWUs to the internal LAN

ZWYC::SWU,6:MCMU,;ZWYC::SWU,7:MCMU,;

9.8 Change all SWUs state to the WO-EX

ZUSC:SWU,:SE;ZUSC:SWU,:TE;ZUSC:SWU,:WO;

9.9 Activate all SWU s back to use

ZW6E:SWU,:A:;


10 CREATE ETPSIG-I IP ADDRESS TO MCMU AND BCSU

ETPE, ETPT and ETPA cards provide an untagged interface for ETP management (ETPSIG-m) and control(ETPSIG-c) traffic.MCMU will be DCHP server and mainitains FTP server connection.

Create ETPSIG-I in MCMUs.ZQRA:MCMU,::EL0;ZQRA:MCMU,::EL1;ZQRA:MCMU,::,,EL0,,::;ZQRA:MCMU,::,,EL1,,::;ZQRN:MCMU,::,:"",,L,IM;

Example,ZQRA:MCMU,0::EL0;ZQRA:MCMU,0::EL1;ZQRA:MCMU,0::VLAN20,20,EL0,,::;ZQRA:MCMU,0::VLAN21,20,EL1,,::;ZQRN:MCMU,0::VLAN20,VLAN21:"10.0.1.11",26,L,IM;

Configure ETPSIG-M&C IP address to BCSU(s) / EL0 & EL1 interfaces ZQRN:BCSU,::EL0,EL1:"",,L,IMC::

Configure ETPSIG-M&C IP address to BCSU(s)/VLAN interfacesZQRA:BCSU,::,,EL0,::;ZQRA:BCSU,:: ,,EL1,::;ZQRN:BCSU,::,:"",,L,IMC::

Example,ZQRA:BCSU,0::VLAN20,20,EL0,:::;ZQRA:BCSU,0::VLAN21,20,EL1,:::;ZQRN:BCSU,0::VLAN20,VLAN21:"10.0.1.1",26,L,IMC:;


11 PACKET ABIS OVER ETHERNET(ETPE), PIU TYPE ETP

The following pop up will be displayed by macro for each BSC variants.

Select the required application and tracks to proceed further.

11.1 Creation of ETPE unit with transmission/line protection

Check the source configuration for overlapping PCM areas and Plug-in units.

Note!Macro ask in this point redundancy type and Plug-in Unit location. After that macro check possibleunit/PCM overlapping.If there is overlapping PCM areas move or remove resources from them. Macro will remove unit and Plug-in Unitsautomatically after needed recourses are moved or removed.

Note:- Refer Appendix 2 to check overlapping PCMs used by existing units in BSCs. Please note to shift existingtraffic from the plug in unit. Once traffic is shifted remove the units and cables and then insert ETP cards to


required tracks. Please note to turn off jumper settings in GSW units if PCMs are not used. Refer Appendix 1 tocheck jumpers settings used for existing ETP cards.

Note:-There are two options for Installing ETPE in Initial flexi BSC-Normal and Flexible.x Normal option: Configurations supported before S15 EP 2.1 releases.x Flexible option: New flexible ETP layout in Flexi BSC.The implementation of flexible option in

initial flexi BSC will be supported only from software S15 EP2.1.

11.1.1 Install Plug-in units, terminators and cables

11.1.1.1 Terminators and setting modules

Remove PCMC8A connectors

Normal option.

Position ID Name FU Use Note ETPEINDEX

1.0B 22.2M C111523 PCMC8A ETC 0 PCM connector module 1)ETPE 11-0








Notes:1) When ETP PIU is used in this slot.

Flexible option.

Position ID Name FU Use NoteETPEINDEX














Notes:1) When ETP PIU is used in this slot.

Add Terminators and setting modules

Normal option.


1.0B 224E C108719 ADMOD00 ETC 0 For ETPE 1) ETPE 11-01.0B 254E C108719 ADMOD00 ETC 0 For ETPE 1) ETPE 12-01.0B 294E C108719 ADMOD00 ETC 1 For ETPE 1) ETPE 13-02.0B 224E C108719 ADMOD00 ETC 2 For ETPE 1) ETPE 3-02.0B 254E C108719 ADMOD00 ETC 2 For ETPE 1) ETPE 4-02.0B 294E C108719 ADMOD00 ETC 3 For ETPE 1) ETPE 5-0

1.0B 181A C101501 CABID1A ETC 0

CABID forETP /ETP-A

ETPE11-0/ETPE12-0

1.0B 273D C101501 CABID1A ETC 1

CABID forETP /ETP-A ETPE 13-0

1.0B 181C C101530 CARID11 ETC 0

CARID forETP /ETP-A

ETPE 11-0/ETPE 12-0

1.0B 271A C101530 CARID11 ETC 1

CARID forETP /ETP-A ETPE 13-0

2.0B 181A C101501 CABID1A ETC 2

CABID forETP /ETP-A

ETPE 3-0/ETPE 4-0

2.0B 273D C101501 CABID1A ETC 3

CABID forETP /ETP-A ETPE 5-0

2.0B 181C C101536 CARID21 ETC 2

CARID forETP /ETP-A

ETPE 3-0 /ETPE 4-0

2.0B 271A C101536 CARID21 ETC 3

CARID forETP /ETP-A ETPE 5-0

Notes:1) When ETP PIU is used as ETPE in this slot.

Flexible option.

Position ID Name FU Use Note ETPEIndex

1.0B 194E

C108719ADMOD00

ETC 0 ForETPE

1)ETPE 11-0

1.0B 224E

C108719ADMOD00

ETC 0 ForETPE

1)ETPE 12-0

1.0B 254E

C108719ADMOD00

ETC 0 ForETPE

1)ETPE 13-0

2.0B 194E

C108719ADMOD00

ETC 2 ForETPE

1)ETPE 3-0


2.0B 224E

C108719ADMOD00

ETC 2 ForETPE

1)ETPE 4-0

2.0B 254E

C108719ADMOD00

ETC 2 ForETPE

1)ETPE 5-0

1.0B 181A

C101501 CABID1A ETC 0 CABIDfor ETP /ETP-A

ETPE11-0/ETPE12-0/ETPE 13-0

1.0B 181C

C101530 CARID11 ETC 0 CARIDfor ETP /ETP-A

ETPE11-0/ETPE12-0/ETPE 13-0

2.0B 181A

C101501 CABID1A ETC 2 CABIDfor ETP /ETP-A

ETPE 3-0/ETPE 4-0/ETPE 5-0

2.0B 181C

C101536 CARID21 ETC 2 CARIDfor ETP /ETP-A

ETPE 3-0/ETPE 4-0/ETPE 5-0

Notes:1) When ETP PIU is used as ETPE in this slot.

11.1.1.2 Plug-in unit installation

Normal option.

Cartridge SGC1Cposition

Unit Cartridge /Slots

ETPEgroupindex

1.3 ETC-0 22&23 11-0

2.3 ETC-2 22&23 3-0

1.3 ETC-0 25&26 12-0

2.3 ETC-2 25&26 4-0

1.3 ETC-1 29&30 13-0

2.3 ETC-3 29&30 5-0

Note: Check Appendix 4 for ETP strappings.


Flexible option.

CartridgeSGC1Cposition

Unit Cartridge /Slots

ETPE groupindex

1.3 ETC-0 19&20 11-0

2.3 ETC-2 19&20 3-0

1.3 ETC-0 22&23 12-0

2.3 ETC-2 22&23 4-0

1.3 ETC-0 25&26 13-0

2.3 ETC-2 25&26 5-0

Note: Check Appendix 4 for ETP strappings.


11.1.1.3 Cabling

11.1.1.3.1 Change MCMU-0, SWU-0, SWU-2, SWU-4 and SWU-6 SE-NH state

ZUSC:MCMU,0:SP; If neededZUSC:MCMU,0:TE;ZUSC:MCMU,0:SE;ZUSC:MCMU,0:SE;

ZUSC:EMB,0:SP; If neededZUSC:EMB,0:TE;

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

ZUSC:SWU,0:TE;ZUSC:SWU,0:SE;ZUSC:SWU,0:SE;





11.1.1.3.1.1 For Normal Option

Note:- Please check whether CHFX or CHES cables(Starting from cable numbers BSCC_480 to BSCC_495) arepresent in back side of BSC from beginning of upgrade itself. Note to remove this if not required. CHFX andCHES cables are needed in case of HW redundancy part of ETP as mentioned in cabling part of upgradeprocedure.

Move and reconnect or Add following cables if needed.


ETPEINDEX

No FU OldPosition

NewPosition

FU OldPosition

NewPosition

Type Use Note

BSCC_416 ETC 0 1.0F14.SB1-0

1.0F23.SB2-0

GSW2KB-A 0

1.0F02.SB1-0

1.0F8.SB4-0

CSB007 Hotlink ETPE11-0

Add needed ETPLAN and Hotlink cables from GSW-0 and LANU-0 to required tracks

Equipping CABLE FROM CABLE TOETPE

INDEXNo FU Position FU Position Type Use Note

BSCC_3301 LANU0

4.0B 15.1E ETC 0 1.0B22.4G

CHES025 ETPLAN ETPE11-0

BSCC_3302 LANU0

4.0B 15.1G ETC 0 1.0B25.4G


BSCC_3303 LANU0

4.0B 15.1J ETC 1 1.0B29.4G


BSCC_3307 LANU0

4.0B 15.2A ETC 2 2.0B22.4G


BSCC_3308 LANU0

4.0B 15.2C ETC 2 2.0B25.4G


BSCC_3309 LANU0

4.0B 15.2E ETC 3 2.0B29.4G


BSCC_3400 ETC2

2.0F26.SB2-0

GSW2KB0

1.0F01.SB2-0

CSB016 Hotlink 1) ETPE4-0

BSCC_3402 ETC3

2.0F30.SB2-0

GSW2KB0

1.0F04.SB1-0


BSCC_3404 ETC2

2.0F23.SB2-0

GSW2KB0

1.0F05.SB1-0


BSCC_3406 ETC0

1.0F26.SB2-0

GSW2KB0

1.0F03.SB1-0


BSCC_3408 ETC1

1.0F30.SB2-0

GSW2KB0

1.0F02.SB1-0


Notes:1) These cables are installed and tied with soft cable ties to the front side of the cabinet to be ready for connecting

plug in units


Check SW256B dips switching. See appendix 1

11.1.1.3.1.2 For Flexible option


Remove cables if needed.



BSCC_417 GTIC 0 1.0F14.SB2-0

GSW2KB-A 0

1.0F02.SB2-0

CSB012 Hotlink 1)

BSCC_432 GTIC 1 2.0F13.SB1-0

GSW2KB-A 0

1.0F03.SB1-0

CSB011 Hotlink 2)

BSCC_433 GTIC 1 2.0F13.SB2-0

GSW2KB-A 0

1.0F03.SB2-0

CSB012 Hotlink 3)

BSCC_412 GTIC 0 1.0F13.SB1-0

GSW2KB-A 0

1.0F06.SB1-0

CSB005 Hotlink 4)

BSCC_413 GTIC 0 1.0F13.SB2-0

GSW2KB-A 0

1.0F06.SB2-0

CSB005 Hotlink 5)

Notes:1) These cables have to be removed only in case an ETP is taken in use in ETC 2 slot 19 (ETPT/E)2) These cables have to be removed only in case an ETP is taken in use in ETC 0 slot 22 (ETPT/E)3) These cables have to be removed only in case an ETP is taken in use in ETC 2 slot 22 (ETPT/E)4) These cables have to be removed only in case an ETP is taken in use in ETC 0 slot 25 (ETPT/E)5) These cables have to be removed only in case an ETP is taken in use in ETC 2 slot 25 (ETPT/E)

Move and reconnect or Add following cables if needed.Equipping CABLE FROM CABLE TO ETPE

IndexNo old FU Old

PositionNew

Positionold FU Old

PositionNewPosition

Type Use Note

new FU new FU

BSCC_416 GTIC 0 1.0F14.SB1-0

1.0F23.SB2-0

GSW2KB0

1.0F02.SB1-0

1.0F03.SB1-0


ETC 0

Note:1) These cables shall only be moved and re-connected, if an ETP PIU is taken in use in this slot(s).

Add needed ETPLAN and Hotlink cables from GSW-0 and LANU-0 to required tracks

Equipping CABLE FROM CABLE TO ETPEIndex


BSCC_3300 LANU 0 4.0B15.1C

ETC 0 1.0B19.4G


BSCC_3301 LANU 0 4.0B15.1E

ETC 0 1.0B22.4G


BSCC_3302 LANU 0 4.0B15.1G

ETC 0 1.0B25.4G



BSCC_3306 LANU 0 4.0B15.1P

ETC 2 2.0B19.4G


BSCC_3307 LANU 0 4.0B15.2A

ETC 2 2.0B22.4G


BSCC_3308 LANU 0 4.0B15.2C

ETC 2 2.0B25.4G


BSCC_5040 ETC 0 1.0F20.SB2-0

GSW2KB0

1.0F02.SB1-0


BSCC_5046 ETC 0 1.0F26.SB2-0

GSW2KB0

1.0F06.SB1-0


BSCC_5042 ETC 2 2.0F20.SB2-0

GSW2KB0

1.0F02.SB2-0


BSCC_5044 ETC 2 2.0F23.SB2-0

GSW2KB0

1.0F03.SB2-0


BSCC_5048 ETC 2 2.0F26.SB2-0

GSW2KB0

1.0F06.SB2-0


Note:1) These cables are included in partlist but shall only be connected in case an ETPE is taken in use in ETC 0 slot

19/20.2) These cables are included in partlist but shall only be connected in case an ETPE is taken in use in ETC 2 slot




25/26.

Check SW256B dip switching. See appendix 1

11.1.1.3.2 Change MCMU-0, SWU-0, SWU-2, SWU-4 and SWU-6 to WO-EX 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:SWU,0:SE;ZUSC:SWU,0:TE;ZUSC:SWU,0:WO;



ZUSC:SWU,6:SE;


ZUSC:SWU,6:TE;ZUSC:SWU,6:WO;

11.1.1.3.3 Change MCMU-1, SWU-1, SWU-3, SWU-5 and SWU-7 SE-NH state

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

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

ZUSC:SWU,1:TE; ZUSC:SWU,1:SE;

ZUSC:SWU,1:SE;




11.1.1.3.3.1 For Normal Option


Move and reconnect or add following cable if needed.Equipping CABLE FROM CABLE TO

No FU OldPosition

NewPosition

FU OldPosition

NewPosition

Type Use Note ETPEINDEX

BSCC_418 ETC 0 1.0F14.SB1-1

1.0F23.SB2-1

GSW2KB-A 1

2.0F02.SB1-0

2.0F8.SB4-0

CSB011 Hotlink ETPE11-0

Add needed ETPLAN, Hotlink cables from GSW-1 and LANU-1 side to required tracks.

Equipping CABLE FROM CABLE TO ETPEINDEX


BSCC_3321 LANU 1 5.0B 15.1E ETC 0 1.0B22.4J


BSCC_3322 LANU 1 5.0B 15.1G ETC 0 1.0B25.4J


BSCC_3323 LANU 1 5.0B 15.1J ETC 1 1.0B29.4J


BSCC_3327 LANU 1 5.0B 15.2A ETC 2 2.0B22.4J



BSCC_3328 LANU 1 5.0B 15.2C ETC 2 2.0B25.4J


BSCC_3329 LANU 1 5.0B 15.2E ETC 3 2.0B29.4J


BSCC_3401 ETC 2 2.0F26.SB2-1

GSW2KB1

2.0F01.SB2-0


BSCC_3403 ETC 3 2.0F30.SB2-1

GSW2KB1

2.0F04.SB1-0


BSCC_3405 ETC 2 2.0F23.SB2-1

GSW2KB1

2.0F05.SB1-0


BSCC_3407 ETC 0 1.0F26.SB2-1

GSW2KB1

2.0F03.SB1-0


BSCC_3409 ETC 1 1.0F30.SB2-1

GSW2KB1

2.0F02.SB1-0


Notes:1) These cables are installed and tied with soft cable ties to the front side of the cabinet to be ready for connecting plug-

in unit


11.1.1.3.3.2 For Flexible option


Remove following cables if needed.Equipping CABLE FROM CABLE TO


BSCC_419 GTIC 0 1.0F14.SB2-1

GSW2KB-A 1

2.0F02.SB2-0

CSB012 Hotlink 1)

BSCC_434 GTIC 1 2.0F13.SB1-1

GSW2KB-A 1

2.0F03.SB1-0

CSB007 Hotlink 2)

BSCC_435 GTIC 1 2.0F13.SB2-1

GSW2KB-A 1

2.0F03.SB2-0

CSB007 Hotlink 3)

BSCC_414 GTIC 0 1.0F13.SB1-1

GSW2KB-A 1

2.0F06.SB1-0

CSB011 Hotlink 4)

BSCC_415 GTIC 0 1.0F13.SB2-1

GSW2KB-A 1

2.0F06.SB2-0

CSB011 Hotlink 5)

Notes:1) These cables have to be removed only in case an ETP is taken in use in ETC 2 slot 19 (ETPT/E)2) These cables have to be removed only in case an ETP is taken in use in ETC 0 slot 22 (ETPT/E)3) These cables have to be removed only in case an ETP is taken in use in ETC 2 slot 22 (ETPT/E)4) These cables have to be removed only in case an ETP is taken in use in ETC 0 slot 25 (ETPT/E)5) These cables have to be removed only in case an ETP is taken in use in ETC 2 slot 25 (ETPT/E)

Move and reconnect or add following cable if needed.

Equipping CABLE FROM CABLE TO ETPEIndex

No old FU OldPosition

NewPosition

old FU OldPosition

NewPosition

Type Use Note

new FU new FU


BSCC_418 GTIC 0 1.0F14.SB1-1

1.0F23.SB2-1

GSW2KB1

2.0F03.SB1-0


ETC 0

Note:1) These cables, shall only be moved and re-connected, if an ETP PIU is taken in use in this slot(s).

Add needed ETPLAN, Hotlink cables from GSW-1 and LANU-1 side to required tracks.

Equipping CABLE FROM CABLE TO ETPE Index


BSCC_3320 LANU 1 5.0B 15.1C ETC 0 1.0B 19.4J CHES027 ETPLAN

ETPE 11-0BSCC_3321 LANU 1 5.0B 15.1E ETC 0 1.0B 22.4J CHES026 ETPLAN

ETPE 12-0BSCC_3322 LANU 1 5.0B 15.1G ETC 0 1.0B 25.4J CHES026 ETPLAN

ETPE 13-0BSCC_3326 LANU 1 5.0B 15.1P ETC 2 2.0B 19.4J CHES024 ETPLAN

ETPE 3-0BSCC_3327 LANU 1 5.0B 15.2A ETC 2 2.0B 22.4J CHES022 ETPLAN

ETPE 4-0BSCC_3328 LANU 1 5.0B 15.2C ETC 2 2.0B 25.4J CHES021 ETPLAN

ETPE 5-0BSCC_5041 ETC 0 1.0F

20.SB2-1GSW2KB1

2.0F02.SB1-0

CSB014 Hotlink 1)


26.SB2-1GSW2KB1

2.0F06.SB1-0

CSB013 Hotlink 4)


20.SB2-1GSW2KB1

2.0F02.SB2-0

CSB011 Hotlink 2)


23.SB2-1GSW2KB1

2.0F03.SB2-0

CSB009 Hotlink 3)


26.SB2-1GSW2KB1

2.0F06.SB2-0

CSB011 Hotlink 5)

ETPE 5-0

Note:1) These cables are included in partlist but shall only be connected in case an ETPT is taken in use in ETC 0 slot

19/20.2) These cables are included in partlist but shall only be connected in case an ETPT is taken in use in ETC 2 slot




25/26.


11.1.1.3.4 Change MCMU-1 to SP-EX, SWU-1, SWU-3, SWU-5 and SWU-7 to WO-EX state.

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

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






11.1.2 Create HW configuration

Create cartridges if not existGTIC-0, ETC-0 and ETC-1 cartridge:ZWTC:SGC1C_A,1A1-3,,:AL=1A1-11-12;

GTIC-1, ETC-2 and ETC-3 cartridge:ZWTC:SGC1C_A,1A2-3,,:AL=1A1-11-13;

Create ETPE functional unitNormal option.

ZWTU:ETPE,11,0:1A1-3;ZWTU:ETPE,12,0:1A1-3;ZWTU:ETPE,13,0:1A1-3;ZWTU:ETPE,3,0:1A2-3;ZWTU:ETPE,4,0:1A2-3;ZWTU:ETPE,5,0:1A2-3;

Flexible option.ZWTU:ETPE,11,0:1A1-3;ZWTU:ETPE,12,0:1A1-3;ZWTU:ETPE,13,0:1A1-3;ZWTU:ETPE,3,0:1A2-3;ZWTU:ETPE,4,0:1A2-3;ZWTU:ETPE,5,0:1A2-3;

Create ETPE plug-in unit

Normal option.ZWTP:ETPE,11,0:ETP,0,22::ETPCS,8,1984&&2047,TSL,0&&31;ZWTP:ETPE,12,0:ETP,0,25::ETPCS,8,512&&575,TSL,0&&31;ZWTP:ETPE,13,0:ETP,0,29::ETPCS,8,256&&319,TSL,0&&31;ZWTP:ETPE,3,0:ETP,0,22::ETPCS,8,1024&&1087,TSL,0&&31;ZWTP:ETPE,4,0:ETP,0,25::ETPCS,8,64&&127,TSL,0&&31;ZWTP:ETPE,5,0:ETP,0,29::ETPCS,8,768&&831,TSL,0&&31;

Flexible option.ZWTP:ETPE,11,0:ETP,0,19::ETPCS,8,256&&319,TSL,0&&31;ZWTP:ETPE,12,0:ETP,0,22::ETPCS,8,512&&575,TSL,0&&31;ZWTP:ETPE,13,0:ETP,0,25::ETPCS,8,1280&&1343,TSL,0&&31;

ZWTP:ETPE,3,0:ETP,0,19::ETPCS,8,320&&383,TSL,0&&31; ZWTP:ETPE,4,0:ETP,0,22::ETPCS,8,576&639,TSL,0&&31;


ZWTP:ETPE,5,0:ETP,0,25::ETPCS,8,1344&&1407,TSL,0&&31;

Note:For legacy A-interface: Hotlinks are connected from port 0&1 to GSWs. ETPCS functionality is created in plugin unit to support legacy A interface.For A over IP: Traffic will be routed though EEP interface created (via ETPA card).For PS via PCU2_E cards: No separate PCMs are required. This will use PEPeth link created in ETP cards tocommunicate with PCU2_E cards in BCSU.This will support CS calls in (A over IP,A over TDM) and PS calls if PCU2_E cards are used in BSCs.

Connect functional unitsZWUC:ETPE,,:ETP,0:IF=ABIS:;

Note: This command is required only if PCMs are created in ETP plug in units

Connect hotlink ports

ZWTA:GSW,0:SW256B,:HOTLINK,:ETPE,,:ETP,:HOTLINK,:;

ZWTA:GSW,1:SW256B,:HOTLINK,:ETPE,,:ETP,:HOTLINK,:;

Normal option.ETPE 11-0

ZWTA:GSW,0:SW256B,7:HOTLINK,6:ETPE,11,0:ETP,0:HOTLINK,0:;ZWTA:GSW,1:SW256B,7:HOTLINK,6:ETPE,11,0:ETP,0:HOTLINK,1:;

ETPE 3-0


ETPE 12-0


ETPE 4-0


ETPE 13-0


ETPE 5-0


Flexible option.ETPE 11-0



ETPE 3-0


ETPE 12-0


ETPE 4-0


ETPE 13-0


ETPE 5-0


Configure ETPSIG-M TCP/IP stack configuration for ETPE (SE-NH).ZQRA:ETPE, ,::IL0::UP;ZQRA:ETPE, ,::IL1::UP;ZQRA:ETPE, ,::BOND0,IL0,IL1,::UP:;

Configure ETPSIG-M IP address with parameters PDM to BOND0 interface. ZQRN:ETPE,,::BOND0:"",,P,IDM:;

Create ETPSIG-C IP address ZQRN:ETPE,,>unit_index>::BOND0:"",,L,ICV::;

Create IuA messaging configuration for ETPSIG-M and ETPSIG-CZD2C:M:BCSU,::ETPE,,:::;ZD2C:C,NOR:BCSU,::ETPE,,:::;

Note!ETPSIG-M is created only to Gateway BCSU and ETPSIG-C must be created to all BCSUs for all ETP/ETP-Aunits

Create EL0 IP address to ETPE ZQRA:ETPE,,::EL0::UP; ZQRN:ETPE,,::EL0,:"",,P,:;

Create EEP interface for traffic between ETPE and ETPAZQRA:ETPE,,::,,BOND0,;ZQRN:ETPE,,::,:"",,L,VI:;ZQRP:ETPE,,:::"":TAG,"EEP":;

Note: EEP interface creation is required only if A over IP is used.


Note: Create the PEP link to ETPGID 0 first if you want to get the ETP object ID for the ETPGID to match inNetAct.

Create PEP interface if PCU2-Es are in useZQRA:ETPE, ,::,,BOND0,;ZQRN:ETPE,,::,:"",,L,VI:;ZQRP:ETPE, ,:::"":TAG,"PEP":;

Create IN0 interface( Internal Octeon-DSP interface)ZQRA:ETPE,,:IN0::UP;ZQRN:ETPE,,::IN0,,P,I::;

Create static routeZQKC:ETPE, ,:::"":PHY:;

Change state of ETPE to TE-EXZUSC:ETPE,,:SE;ZUSC:ETPE,,:TE;

11.1.3 Check Plug-in unit softwareNote: The flashing does not succeed if the username and password in the ETP card does not match the BSCsusername & password. Refer Appendix 5 to see an example how to update the username & password via ETPservice terminal.

Check the flash software of ETP cards:-ZWDM:UT=,UI=,MODE=ACTIVE;ZWDM:UT=,UI=,MODE=STANDBY;

Check the CBUHAN version in BSC package.ZDDE::"ZMXP:W0-MMDIRE/CBU*.*";

Macro will choose a valid option (option1 or option2 or option3) based on the output of above interrogationcommands.

Option 1:- When existing ETP version is same or older than the versions mentioned below and ETPsoftware in OMU DISK is newer than PAC versions mentioned below. If CBUHAN version is older than theversion mentioned below, then option 1 needs to be selected.

Image Name PAC Version existing on ETP

GGNCOMAB 2.3-0GGNETPET 3.30-0GGNETPAA 3.29-0GGNETPAB 4.29-0

CBUHAN 12.95-1

Upgrade the ETP software on the Active flash of the ETP card using following MML command:ZWDL:UT=,UI=0,SERVER=,SW=W0-LFILES/,MODE=ACTIVE;

Note: For FTP server IP address, check MCMU ETPSIG-I IP address. Image file is GGNETPET.IMG forETPE.

Restart the ETP card. Note that after this point, the upgraded software will be running on ETP card.ZUSU:UT=,UI=;


Verify that the new software version has been upgraded on active flash using following command :ZWDM:UT=,UI=,MODE=ACTIVE;

Upgrade the ETP software on the Standby flash of the ETP card using following MML command:ZWDL:UT=,UI=0,SERVER=,SW=W0-LFILES/,MODE=STANDBY;


Verify that the new software version has been upgraded on standby flash using following command :ZWDM:UT=,UI=,MODE=STANDBY;

Option 2:- When existing ETP version is newer than PAC versions mentioned below and also if CBUHANversion is newer than the version mentioned.



CBUHAN 12.95-1

Upgrade the ETP software on the STANDBY flash of the ETP card using following MML command:ZWDL:UT=,UI=0,SERVER=,SW=W0-LFILES/,MODE=STANDBY;


Use command ZWDS to switch upgraded flash as ACTIVE flash on the ETP card:ZWDS:UT=,UI=,PT=,PI=:;

Restart the ETP card. Note that after this point, the upgraded software will be running on ETP card. This will verifyif flash upgrade was successful.

ZUSU:UT=,UI=;

Upgrade the ETP software on the new STANDBY flash of the ETP card using following MML command:ZWDL:UT=,UI=0,SERVER=,SW=W0-LFILES/,MODE=STANDBY;


Use command ZWDS to switch upgraded flash as ACTIVE flash on the ETP card:ZWDS:UT=,UI=,PT=,PI=:;

Restart the ETP card. Note that after this point, the upgraded software will be running on ETP card from theoriginal flash.

ZUSU:UT=,UI=;

Option 3:- When existing ETP version is same or older than the versions mentioned below and ETPsoftware in OMU DISKis also same or older than PAC versions mentioned below.




CBUHAN 12.95-1

Upgrade the ETP software on the Active flash of the ETP card using following MML command:ZWDL:UT=,UI=0,SERVER=,SW=W0-LFILES/,MODE=ACTIVE;



After card restart, log-in to the card using following MML commands -ZDDS;ZRS:switch_flash ctot

After the card comes up, upgrade the ETP software on the this new flash of the ETP card using following MMLcommand:

ZWDL:UT=,UI=0,SERVER=,SW=W0- LFILES/,MODE=ACTIVE;





To restore to the original default flash, we need to switch flash again. So as the ETP card comes up, log-in to thecard using following MML commands -

ZDDSZRS:

Switch to other flash using below command ST command -switch_flash ctot

NOTE: This command will switch flash and restart the ETP card as well. After the card comes up, open anew MML session.



11.1.4 Diagnostic

Run diagnostic to the ETPEZUDU:ETPE,,;


Note: The diagnostic part will be run on both MCMUs.

Change working state of ETPE to WO-EXZUSC:ETPE,,:WO;

11.1.5 Check PCU configuration

If Packet Abis interface is also used in PS traffic check PCU configuration. PCU2-D or PCU2-E must be created tothe PCUPAB function that it can carry Packet Abis PS data.

For PCU2_E cards PEP interface creation is required to support PEP Eth link. These creations are mentioned inthe below document.

PCU configuration can be checked with following command:ZWTI:BCSU,;

Use BSCPCU HW implementation for PS traffic procedure if PCU configurations need to change.

ETP- PCU connection.

ZESK:ETPE,:BCSU,:PCU,:;

Note :This is required for both PCU2_E and PCU2_D cards.

11.2 Creation of ETPE unit with hardware protection

Note!Macro asks in this point Plug-in redundancy type and Unit location. After that macro check possibleunit/PCM overlapping.If there is overlapping PCM areas move or remove resources from them. Macro will remove unit and Plug-in Units automatically after needed resources are install Plug-in units, terminators and cables

Note: - Refer Appendix 2 to check overlapping PCMs used by existing units in BSCs. Please note to shift existingtraffic from the plug in unit. Once traffic is shifted remove the units and cables and then insert ETP cards torequired tracks. Please note to turn off jumper settings in GSW units if PCMs are not used. Refer Appendix 1 tocheck jumpers settings used for existing ETP cards.

Note:-There are two options for Installing ETPE in Initial flexi BSC-Normal option and Flexible option.

Normal option: Configurations supported before S15 EP 2.1 releases.

Flexible option: New flexible ETP layout in Flexi BSC. The implementation of flexible option in initial flexi BSC willbe supported only from software S15 EP2.1. If flexible option is taken to use, the supported topology is T29.Change it with following command: ZW6G:T29;

11.2.1 Install Plug-in units, terminators and cables

11.2.1.1 Terminators and setting modules

Remove PCMC8A connectors


11.2.1.1.1 Normal option


1.0B14.2M

C111523 PCMC8A GTIC 0 PCM connector module 1)ETPE 0,0

1.0B15.2M

bsc implementation for etp_etp-a_in initial flexi bsc_ver 1_12

Documents

environmental policy

nokia solutions

prior upgrade

upgrade macros

needed documentation

needed equipment

adverse environmental

environmental serviceswe