Commissioning BSC3i - yugten.files.wordpress.com · Commissioning BSC3i DN02199145 Issue 5-1 en 04/06/2008 # Nokia Siemens Networks 1 (112) BSC3126-5.0 Nokia BSC3i, Rel. S12, Site

Commissioning BSC3i

DN02199145Issue 5-1 en04/06/2008

# Nokia Siemens Networks 1 (112)

BSC3126-5.0Nokia BSC3i, Rel. S12, Site Documentation, v.5

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (112) # Nokia Siemens Networks DN02199145Issue 5-1 en04/06/2008

Commissioning BSC3i

Contents

Contents 3

List of tables 5

List of figures 7

Summary of changes 9

1 Overview of BSC3i commissioning 11

2 Checking the hardware functions of BSC3i 152.1 Required hardware 152.2 Peripheral units 17

3 Opening the first MML session in BSC3i 19

4 Monitoring the BSC3i start-up 214.1 Monitoring the start-up of the OMU 214.2 Monitoring the start-up of the MCMU 244.3 Monitoring the start-up of the BCSU 26

5 Checking the I/O system of BSC3i 295.1 Checking the power handling of the mass memory devices 295.1.1 Testing the MO drive power system 295.1.2 Testing the power system of the WDU: HDPU-A 305.1.3 Testing the power system of the WDU: HDSAM-A 315.2 Checking the state of the I/O devices 32

6 Checking the EMB in BSC3i 37

7 Checking the clock equipment in BSC3i 397.1 Checking the switchover of the clock synchronisation unit and the clock

and alarm buffer 397.2 Checking the synchronisation unit 407.2.1 Simulating the synchronisation inputs 407.2.2 Checking the synchronisation unit with a changeover 41

8 Checking the hardware configuration of BSC3i 45

9 Checking the maintenance system of BSC3i 479.1 Testing the alarm system 479.1.1 Testing wired alarms 479.1.2 Testing external alarms 509.1.3 Testing alarm outputs 529.2 Testing the recovery from power breaks 549.2.1 Testing the recovery from a complete power break in the system 549.2.2 Testing a power break in the PDFU 569.2.3 Testing a fuse fault in the supply cable 58

DN02199145Issue 5-1 en04/06/2008


Contents

9.3 Testing state transitions and unit diagnostics 599.4 Diagnostics of the I/O devices: FDU 669.5 Diagnostics of the I/O devices: UMS 679.6 Testing the spare units 68

10 Checking the ESB switch in BSC3i 6910.1 Local reset and the Hotswap button in the ESB switch 6910.2 Checking the built-in self test of the ESB26 switch 70

11 Verifying the software versions of BSC3i 73

12 Copying additional software and setting the time zone in BSC3i 75

13 BSC3i commissioning test logs 77


Commissioning BSC3i

List of tables

Table 1. Voltage requirements in BSC3i 16

Table 2. VDU settings in BSC3i 17

Table 3. Printer settings in BSC3i 17

Table 4. Voltage-controlled external alarm pins on the connector panel of thefemale D25 connector (connector 21) 50

Table 5. Alarm output pins on the connector panel of the female D25 connector(connector 22) 53

Table 6. Terminal settings for CLI 70

Table 7. BSS specifications 77

Table 8. Preparation of commissioning 77

Table 9. Checking the BSC3i internal cabling 78

Table 10. Checking the functioning of the BSC3i hardware 78

Table 11. Checking strappings, DIP switches, memory, and EPROMs of theOMU 78

Table 12. Checking strappings, DIP switches, memory, and EPROMs of theMCMUs 79

Table 13. Checking the strappings of GSW2KB 79

Table 14. Checking strappings, DIP switches, memory, and EPROMs of BCSUs 80

Table 15. Checking EPROMs, DIP switches, and the jumpers of the ESB units of theLANUs 81

Table 16. Checking strappings, DIP switches, and FLASH of ETs in ETCcartridges 81

Table 17. Checking strappings, DIP switches, and FLASH of ETS2s and ET16s inGTIC cartridges 82

Table 18. Checking the strappings and EPROMs of the clock equipment 83

Table 19. Checking the strappings of the clock cartridges 83

Table 20. Testing the power supply 84

Table 21. Testing the peripheral units 84

Table 22. Opening the first MML session in the BSC 85

Table 23. Monitoring the start-up of units 85

Table 24. Checking the I/O system of the BSC 85

DN02199145Issue 5-1 en04/06/2008


List of tables

Table 25. Testing the EMB connections of the BSC 86

Table 26. Checking the switchover and the alarms from the clock synchronisationunit 86

Table 27. Checking the clock synchronisation unit 86

Table 28. Checking the hardware configuration of the BSC 87

Table 29. Testing the wired alarms 87

Table 30. Testing the voltage controlled external alarms 88

Table 31. Testing alarm outputs 89

Table 32. Testing the recovery from a complete power break in the system 89

Table 33. Testing a power break in the PDFU 90

Table 34. Testing a fuse fault in the power cable 90

Table 35. Testing the state transition and unit diagnostics of the BSC's units 90

Table 36. Testing the state transition and unit diagnostics of the units 90

Table 37. Testing the state transition and unit diagnostics of the SETs in ETS2 92

Table 38. Testing the state transition and unit diagnostics of ET16s, part 1 93




Table 42. Testing the state transition and unit diagnostics of ETS2s 110

Table 43. I/O device diagnostics 110

Table 44. Checking the ESB switch 111

Table 45. Verifying the software versions of the BSC 111

Table 46. Copying additional software 111

Table 47. Finishing the commissioning 112


Commissioning BSC3i

List of figures

DN02199145Issue 5-1 en04/06/2008


List of figures


Commissioning BSC3i

Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes between issues 5-1 and 5

New mass memory units included in chapters Overview of BSC3icommissioning, Checking the I/O system of BSC3i, Checking themaintenance system of BSC3i and Copying additional software andsetting the time zone in BSC3i.

Changes between issues 5 and 4–1

Information related to the BSC3i variant BSC3i 660 has been removedfrom the document.

Information on the BSC3i variants BSC3i 1000/2000 has been added tochapter Overview of BSC3i commissioning and the commissioningprocedure list has been updated. In addition, an estimate on thecommissioning time has been added.

The references in chapter Checking the hardware functions of BSC3i havebeen updated.

The procedures in chapter Monitoring BSC3i start-up have been updatedto follow the steps performed in BSC3i 1000/2000.

Chapter Inspecting MBIF in BSC3i has been removed.

Chapter Checking the EMB in BSC3i has been added.

Information on how to check the hardware configuration has been movedfrom chapter Checking the clock equipment and hardware configuration inBSC3i to a new chapter Checking the hardware configuration of BSC3i. Inaddition, information on the default values of ET16 has been added.

DN02199145Issue 5-1 en04/06/2008


Summary of changes

The alarm output in chapter Checking the maintenance system of BSC3iand the alarm output pins of connector 22 have been updated. In addition,steps related to CLAB, SBUS, EMB, STMU, SWU, and SET have beenadded to section Testing state transitions and unit diagnostics.

Sections Inspecting the built-in self test of the ESB20 switch in BSC3iandInspecting the built-in self test of the ESB20–A switch in BSC3i have beenremoved from chapter Checking the ESB switch in BSC3i, and sectionChecking the built-in self test of the ESB26 switch has been added.

The tables in chapter BSC3i commissioning test logs have been updatedto apply to the BSC3i variants BSC3i 1000/2000.

The order of some chapters and sub-chapters has been changed so thatthe document is more in line with the actual commissioning process.

Changes made between issues 4–1 and 4

Editorial changes.


Commissioning BSC3i

1 Overview of BSC3i commissioning

These instructions are intended to be used in the commissioning of thesystem in the final location of the BSC3i. They can be used with the ANSIor ETSI environment BSC3i 1000/2000 variants. (For information on thecommissioning of BSC3i 660, see Commissioning BSC3i in Nokia BSC/TCSM S11.5 Product Documentation.)

Prerequisites for the successful commissioning according to theseinstructions are that:

. the BSC has passed the factory acceptance tests

. the installation has to be accepted

. at least the files associated with the configuration are ready on thehard disks of the BSC

. the site has been built and prepared according to Nokia BSC BaseStation Controller, Rel. S12, Site Documentation for BSC3i

. in a two-cabinet configuration, the cabling has been done during theinstallation phase

All the software that belongs to the BSC must be ready on the hard disksof the system before starting the commissioning tests. If there is newer SWavailable than what is installed in the BSC disk, the BSC must becommissioned with the same SW that is installed on the disks. The newerSW is installed before the integration of the BSC.

In the final BSC site the tests which, according to the test logs deliveredwith the hardware, have already been performed at the test field of NokiaCorporation, do not necessarily have to be performed.

The purpose of the commissioning tests is to ensure that the BSC willoperate correctly in the GSM network. When the commissioning tests havebeen performed in an acceptable manner, the BSC can be taken intotraffic. Depending on the configuration, the commissioning of BSC3i 1000/2000 takes around 3-5 working days.

DN02199145Issue 5-1 en04/06/2008


Overview of BSC3i commissioning

The Serial Number and Identification codes of the network element (NE)must be filled during commissioning of NEs (at least) according to Creatingand Managing BSC Hardware. This is normally done during factory testingbefore the delivery for new deliveries, but in extensions this must be doneon site before commissioning testing.

It is important to have an overall view of the commissioning. Therefore, werecommend that you read the instructions carefully before starting.

Commissioning test arrangements

The commissioning testing of the BSC3i can be started when theinstallation has been checked. Any detected faults are reported with theNokia problem report which is sent to the Customer Service Centre.

Measurement devices and tools

The following is a summary of all the tools required in the testing of a DX200 BSC3i 1000/2000:

1. Two terminals

2. Hex calculator

3. Tool set for commissioning engineer, NSN code: CS77580.05

4. Jumper links

5. Release documentation on PC

6. New software on a MO disk or an USB memory

7. All delivered Change Deliveries (installed after the commissioning)

8. Customer Specific Disk including PRFILE, FIFILE, and licence files

9. Empty rewritable magneto-optical disk or an empty USB memorystick

BSC3i commissioning procedure

1. Checking the hardware functions of BSC3i

2. Opening the first MML session in BSC3i

3. Monitoring the BSC3i start-up

4. Checking the I/O system of BSC3i

5. Checking the EMB in BSC3i


Commissioning BSC3i

6. Checking the clock equipment in BSC3i

7. Checking the hardware configuration of BSC3i

8. Checking the maintenance system of BSC3i

9. Checking the ESB switch in BSC3i

10. Verifying the software versions of BSC3i

11. Copying additional software and setting the time zone in BSC3i

Test logs are filled in during the testing. The test logs can be found inBSC3i commissioning test logs.

Troubleshooting information can be found in Start-up fault conditions inPrintouts of Starting Phases.

DN02199145Issue 5-1 en04/06/2008


Overview of BSC3i commissioning


Commissioning BSC3i

2 Checking the hardware functions ofBSC3i

2.1 Required hardware

This procedure enables you to check the hardware functioning in thecommissioning tests.

The following items are checked in BSC3i:

. internal cabling

. interchangeability codes

. EPROM versions

. jumpers

. DIP switches

. FLASH versions

. power supply

Steps

1. Check the internal cabling.

Compare the internal cabling to the interconnection cables list inInterconnection Cables in BSC3i in Nokia BSC Base StationController, Rel. S12, Site Documentation for BSC3i to make surethat. the cables are connected to the right position. the connections are made properly. the cables are installed and locked correctly

2. Check the interchangeability codes.

DN02199145Issue 5-1 en04/06/2008


Checking the hardware functions of BSC3i

Compare the interchangeability codes of cartridges and plug-in unitsto the hardware type list in Hardware Revision List for BSC3i inNokia BSC Base Station Controller, Rel. S12, Site Documentation tomake sure that they are correct.

3. Check the EPROM versions.

Compare the EPROM versions of the plug-in units to the version listin Pre-Processor Program Information in Nokia BSC Base StationController, Rel. S12, Release Documentation.

4. Check the FLASH versions.

Compare the FLASH versions of the plug in units to the version list inPre-Processor Program Information in Nokia BSC Base StationController, Rel. S12, Release Documentation.

5. Check the jumper settings.

The jumper settings can be found in Jumper Settings of theCartridges in BSC3i and TCSM3i and Jumper Settings of the Plug-inUnits in BSC3i and TCSM3i in Nokia BSC Base Station Controller,Rel. S12, Site Documentation for BSC3i.

6. Check the settings of the DIP switches.

The settings of the DIP switches can be found in Jumper Settings ofthe Plug-in Units in BSC3i and TCSM3i in Nokia BSC Base StationController, Rel. S12, Site Documentation for BSC3i.

7. Test the power supply of the BSC3i.

The voltage requirements are as in table Voltage requirements inBSC3i.

Table 1. Voltage requirements in BSC3i

Voltage Nominal Tolerance

Feed voltage to DC/DCconverters

-48V or -60V -40.5V to -72V


Commissioning BSC3i

2.2 Peripheral units

The purpose of the test is to check the strappings and settings made in thefactory. Other required parameters are set.

Perform internal tests in units which are equipped with test functions.

Send faulty units to service.

Steps

1. Set the visual display units (VDU).

When the power is switched on, the selectable parameters areautomatically given their default values. The settings in the VDUshould be as in table VDU settings in BSC3i.

Table 2. VDU settings in BSC3i

Baud rate 9600

Data bits 7

Stop bits 2

Parity Even

Page length 23

Line length 80

Connect the female connector to the VDU and join the free pins onthe male connector with strapping wire. Type some text on thekeyboard. The terminal is OK if the typed text is echoed to thescreen. If no text is displayed, the VDU is faulty.

To enable scrolling of the screen, set Lines per Page as 75.

2. Check the printer settings.

The settings are as in table Printer settings in BSC3i.

Table 3. Printer settings in BSC3i

Baud rate 9600

Data bits 7

DN02199145Issue 5-1 en04/06/2008


Checking the hardware functions of BSC3i

Table 3. Printer settings in BSC3i (cont.)

Stop bits 2

Parity even

Page length 65

Line length 80

Correct any incorrect settings.

Perform internal tests on those printers that are equipped with testfunctions.

If there are problems with connections, check the interface cable bymeasuring the resistance with a multimeter. At least the connectionsindicated in the installation documents in BSC Base StationController, Rel. S12, Site Documentation for BSC3i must beavailable in the cable.

Further information

For an overview, see Overview of BSC3i commissioning.


Commissioning BSC3i

3 Opening the first MML session in BSC3i

When a system is delivered from Nokia, the user identifier of the systemhas been defined as <SYSTEM> and the password as <SYSTEM>.

These user identifier and password definitions are of general nature andthey are intended to be used only in factory acceptance testing. The mainuser of the system or the system administrator makes the actual authoritydefinitions for the terminals and users with MML commands.

The procedure for setting up the first session and for defining and testingthe user identifier and password is presented here. Examples are alsoprovided.

Before you start

Check that the display unit is connected to the system as an MML terminaland that the printer has been connected to the systems LPT printer port.

Steps

1. Switch the power on to the display terminal and printer andpress a key.

The following text is displayed on the screen:

ENTER USERNAME <

2. Enter the user identifier SYSTEM and press <CR>.

The following text is displayed:

ENTER PASSWORD <

3. Enter the password SYSTEM and press <CR>.

If the setting up of the session is successful, the following messageis displayed:

DN02199145Issue 5-1 en04/06/2008


Opening the first MML session in BSC3i

WELCOME TO THE DX 200 SERIES DIALOGUE

MAIN LEVEL COMMAND <___>

<

Possible error messages:

/*** PASSWORD TOO SHORT ***/

The password is too short. Minimum length is six characters.

/*** USER AUTHORISATION FAILURE ***/

The user identifier entered has not been programmed into thesystem or the password has been given incorrectly. Enter thepassword again.

4. Check that the printer interface is working properly.

Print out, for example, the states of the I/O devices:

ZISI:::,LPT0;

If the printing is not successful, proceed as described in Checkingthe I/O system of BSC3i.

Further information



Commissioning BSC3i

4 Monitoring the BSC3i start-up

This section describes the monitoring of system start-up and enables thesolving of possible disturbances.

The start-up of the whole system depends on the start-up priorities of thesystem's units. A unit with higher priority is given loading permissionbefore a unit with lower priority.

Within the system, the units are started up according to their respectivepriorities. For example, all the base station controller signaling units(BCSU) are given permission to load simultaneously, as they all have thesame priority. In the case of doubled units, the working units are givenloading permission before the spare units.

The start-up order of the whole system is as follows:

1. Operation and Maintenance Unit (OMU)

2. Marker and Cellular Management Unit (MCMU)

3. Other units

For more information on system start-up, see:

. Monitoring the starting of the exchange

. Loading the files

. Monitoring the starting of the computer


4.1 Monitoring the start-up of the OMU

Monitor the start-up of the Operation and Maintenance Unit (OMU). Afailure in the OMU start up may lead to a similar failure in all other units.

DN02199145Issue 5-1 en04/06/2008


Monitoring the BSC3i start-up

When the start-up of the OMU has reached the stage where the serviceterminal software is started up, the Recovery Service Terminal (RCBUGG)extension is taken into use.

RCBUGG is an extension of the service terminal software which enablesthe monitoring of unit states. It is started up with a service terminalsoftware command.

The RCBUGG contains commands that correspond with those of theWorking State and Restart Handling MML (command group US). Even ifthe start-up of the MMI system fails, the working states of the units can becontrolled with the RCBUGG extension. A prerequisite for the successfulrunning of the RCBUGG is that the recovery system itself has been startedup.

For information on how to use the service terminal, see the followingcommand references:

. Service Terminal Commands

. RCBUGG

Before you start

Check that the working state of the OMU is WO-EX during the start-up ofthe system.

If the state of OMU is TE or SE, the maintenance programs will be startedup in the Marker and Cellular Management Unit (MCMU) and the start-upis monitored in the MCMU.

Steps

1. Connect the MML terminal.

2. Connect the alarm printer.

3. Connect the service terminal.

Connect the service terminal to the J7 connector of the centralprocessing unit (CP816-A).

4. Monitor the start-up.

Monitor the start-up of units with the RCBUGG extension.

a. Take the RCBUGG into use:

ZLE:U,RCBUGGGX


Commissioning BSC3i

b. Monitor the states of the computer units:

ZUSIC:COMP;

5. Reset the unit.

Reset the unit by pressing the reset button of the processor unit.

6. Monitor the start-up of the OMU.

a. The first phase output indicates the start-up of the boot loaderprogram block (BOLERO):

DMX SYSTEM START-UP TESTS

b. Message bus configuration:

GONFIGURING EMB ETHERS

c. Flash version of CPU is shown:

BOP816GX.PAC <ver>

d. Choosing software package in the OMU successful:

CHOOSING PACKET

e. Loading of the computer configuration table successful:

LOADING NET CONFIG...

f. Loading of the load list successful:

LOADING LOAD LIST FROM <source>

g. Loading of the load modules successful:

MODULE LOADING STARTS

LOADING MODULES FROM <source>

ALL MODULES LOADED

h. Debugger software started up:

DEBUGGER READY

i. The type of the unit is clarified:

DEFINING UNIT TYPE

j. First 'PROCESSING FAMILIES' notice is output on theterminal:

PROCESSING FAMILIES

k. The FISLIB Library Manager (FIZSLM) is started up:

PROCESSING FAMILIES FIZ ...

l. Initialisation of work files:

INITIALIZING WORK FILES

m. Loading of the first load group:

LOADING STARTED 0003..

n. The FUNLIB Library Manager (FUZNLM) start-up:

PROCESSING FAMILIES FUZ ...

DN02199145Issue 5-1 en04/06/2008



o. The unit state administration program block (USAPRO) isgiven permission to load:

READY - PHASE 2

FILE LOADING ACTIVATED

p. Loading of a load group OK. All remaining load groups areloaded:

LOADING STARTED ...

q. The USAPRO is given permission to start the program blocks:

READY - PHASE 3

r. Start-up of program blocks:

PROCESSING FAMILIES...

s. Running SW package information:

RUNNING PACKAGE

t. Start-up of unit is terminated:

READY - WO

Further information

Monitoring the start-up of the MCMU

Monitoring the start-up of the BCSU


4.2 Monitoring the start-up of the MCMU

Before you start

Check that the working state of the MCMU is WO-EX or SP-EX during thestart-up of the system.

Steps


Connect the service terminal to the J7 connector of the centralprocessing unit.

2. Reset the unit.

Reset the unit by pressing the reset button of the processor unit

3. Monitor the start-up of the MCMU.


Commissioning BSC3i

a. The first phase output indicates the start-up of the BOLERO:





BOP816GX.PAC <ver>

d. Loading of the computer configuration table successful:


e. Loading of the load list successful:


f. Loading of the load modules successful:



ALL MODULES LOADED

g. Debugger software started up:

DEBUGGER READY

h. The type of the unit is clarified:

DEFINING UNIT TYPE

i. The FIZSLM is started up:


j. Initialisation of work files:


k. The FUZNLM start-up:


l. The USAPRO is given permission to load:

READY - PHASE 2


m. Loading of first loading group:

LOADING STARTED 0008...

n. Start-up of program blocks:


o. Loading of a loading group:

LOADING STARTED...

All remaining loading groups are loaded.

p. The USAPRO is given permission to start up program blocks:

READY - PHASE 3

q. Start-up of program blocks:


All remaining program blocks are created and started up.

DN02199145Issue 5-1 en04/06/2008



r. Running SW package information:

RUNNING PACKAGE

s. Start-up of unit is terminated:

READY - WO

or

READY - SP

Repeat the start-up monitoring with the other MCMU.

Further information

Monitoring the start-up of the OMU

Monitoring the start-up of the BCSU


4.3 Monitoring the start-up of the BCSU

Before you start

Check that the working state of the BCSU is SP-EX during the start-up ofthe system.

Steps


Connect the service terminal to the J7 connector of the centralprocessing unit.

2. Reset the unit.

Reset the unit by pressing the reset button of the processor unit.

3. Monitor the start-up of the BCSU.

a. The first phase output indicates the start-up of the BOLERO:





BOP816GX.PAC <ver>

d. Loading of the computer configuration table successful:



Commissioning BSC3i

e. Loading of the load list successful:


f. Loading of the load modules successful:



ALL MODULES LOADED

g. Debugger software started up:

DEBUGGER READY

h. The type of the unit is clarified:

DEFINING UNIT TYPE

i. The FIZSLM is started up:


j. Initialisation of work files:


k. The USAPRO is given permission to load:

READY - PHASE 2


l. The FUZNLM start-up:


m. Loading of first loading group:

LOADING STARTED 0009...

n. Start-up of program blocks:


o. Loading of a loading group:

LOADING STARTED...

All remaining loading groups are loaded.

p. The USAPRO is given permission to start up program blocks:

READY - PHASE 3

q. Start-up of program blocks:


All remaining program blocks are created and started.

r. Running SW package information:

RUNNING PACKAGE

s. Start-up of unit is terminated:

READY - SP

Repeat the start-up monitoring with the rest of the BCSUs.

Further information

Monitoring the start-up of the OMU

DN02199145Issue 5-1 en04/06/2008



Monitoring the start-up of the MCMU



Commissioning BSC3i

5 Checking the I/O system of BSC3i

This procedure specifies how the I/O system of BSC3i should be checkedin the commissioning tests and how the functioning of the I/O system anddevices is checked.

5.1 Checking the power handling of the mass memorydevices

In S12, there are two mass memory concepts available: either a MagnetoOptical drive or an USB memory connected to a DCAR1-A carrier unit.This section gives the instructions for testing the MO drive power systemand the power systems of hard disk units (WDU) for both concepts. Thereis no need to test the USB memory power handling.

5.1.1 Testing the MO drive power system

Steps

1. Check the MO disk state (ISI).

ZISI::FDU,0;

The state of the MO drive should be WO-BU.

2. Disconnect the power.

Press the power off button on the front panel of the MO drive. After afew seconds, the red power indicator is lit.

3. Remove the MO drive.

Now it is safe to remove the MO disk from the OMU cartridge.

DN02199145Issue 5-1 en04/06/2008


Checking the I/O system of BSC3i

4. Check the state and the alarms in the MO drive (ISI).

ZISI::FDU,0;

The MO state is BL_SY and the alarm 2692 is set.

5. Reconnect the power.

Set the MO drive into the OMU cartridge. The power reconnectsautomatically.

6. Check the state and the alarm in the MO drive (ISI).

After a few seconds, the state of the MO drive should be WO-BU andthe alarm 2692 should be cancelled.

5.1.2 Testing the power system of the WDU: HDPU-A

Steps

1. Check the state of WDU 0 (ISI).

ZISI::WDU,0;

The WDU state should be WO-BU.

2. Prevent file updates to disk (DUP).

ZDUP:OMU:NO,:;


Press the power off button on the front panel of the WDU. After a fewseconds, the red power indicator is lit.

4. Remove the WDU.

Now it is safe to remove the WDU disk from the OMU cartridge.

5. Check the state of the alarm in the WDU (ISI).

ZISI::WDU,0;

The state of the WDU is TE-ID and the alarm 2692 is set.


Commissioning BSC3i


Set the WDU 0 back into the OMU cartridge. The power isreconnected automatically.

7. Change the state of the WDU (ISC).

ZISC::WDU,0:WO-ID;

ZISC::WDU,0:WO-BU;

8. Resume file updates to disk (DUR).

ZDUR:OMU;

9. Check the state and the alarm of the WDU (ISI).

The state of the WDU should be WO-BU and the alarm 2692 shouldbe cancelled.

10. Repeat steps 1 to 9 with WDU 1.

5.1.3 Testing the power system of the WDU: HDSAM-A

Steps

1. Check the state of WDU 0 (ISI).

ZISI::WDU,0;

The WDU state should be WO-BU.

2. Prevent file updates to disk (DUP).

ZDUP:OMU:NO,:;


Pull the switch in HDSAM-A one step out. Within a few seconds theblue hot swap LED should lit solid. Also red out of service LEDshould lit.

4. Remove the WDU.

DN02199145Issue 5-1 en04/06/2008



Now it is safe to pull out the HDSAM-A disk from the DCAR1-Acartridge.

5. Check the state of the alarm in the WDU (ISI).

ZISI::WDU,0;

The state of the WDU is TE-ID and the alarm 2692 is set.


Push the HDSAM-A back into the DCAR1-A cartridge. Wait until bluehot swap LED is solid. Push the switch in HDSAM-A to bottom. Thepower is reconnected and green power good LED should lit. Theblue and red LED should not lit anymore.

7. Change the state of the WDU (ISC).

ZISC::WDU,0:WO-ID;

ZISC::WDU,0:WO-BU;

8. Resume file updates to disk (DUR).

ZDUR:OMU;

9. Check the state and the alarm of the WDU (ISI).

The state of the WDU should be WO-BU and the alarm 2692 shouldbe cancelled.

10. Repeat steps 1 to 9 with WDU 1.

5.2 Checking the state of the I/O devices

The procedure is used for checking the number and states of the I/Oequipment and the output controls (that is, correspondence with thesource data).

Note that the printouts included provide examples only, the actual printoutsmay differ from the ones presented here.


Commissioning BSC3i

Before you start

Check that the correct number of the I/O devices has been packaged forthe system. Check their states and state transitions.

Steps

1. Connect the MML terminal to the VDU connector.

2. Display the I/O devices (ISI).

Display the I/O devices of all the units of the system.

ZISI:;

3. Compare the number of the devices with the source data.

4. Compare the states of the devices with the source data.

Expected outcome

Example of an output following the command:

Example

ZISI:;

I/O DEVICE WORKING STATE AND SPARE DEVICE

SYSTEM = PALLAS UNIT = OMU

DEVICE STATE SPARE DEVICE DEVICE STATE TAPE STATE TAPE TYPE

FDU-00 WO-BU - -

WDU-00 WO-BU - -

WDU-01 WO-BU - -

LPT-00 WO-ID PALLAS OMU LPT-01 -

LPT-01 BL-SY PALLAS OMU LPT-00 -

LPT-02 BL-SY - -

LPT-03 BL-SY - -

VDU-00 WO-ID - -

VDU-01 BL-SY - -

VDU-02 BL-SY - -

VDU-03 BL-SY - -

VDU-04 BL-SY - -

VDU-05 BL-SY - -

VDU-06 BL-SY - -

VDU-07 BL-SY - -

VTP-00 BL-SY - -

VTP-01 BL-SY - -

VTP-02 BL-SY - -

VTP-03 BL-SY - -

VTP-04 BL-SY - -

DN02199145Issue 5-1 en04/06/2008



VTP-05 BL-SY - -

VTP-06 BL-SY - -

VTP-07 BL-SY - -

VTP-08 BL-SY - -

VTP-09 BL-SY - -

VTP-10 BL-SY - -

VTP-11 BL-SY - -

VTP-12 BL-SY - -

VTP-13 BL-SY - -

VTP-14 BL-SY - -

VTP-15 BL-SY - -

VTP-16 BL-SY - -

VTP-17 BL-SY - -

VTP-18 BL-SY - -

VTP-19 BL-SY - -

VTP-20 BL-SY - -

VTP-21 BL-SY - -

VTP-22 BL-SY - -

VTP-23 BL-SY - -

VTP-24 BL-SY - -

VTP-25 BL-SY - -

VTP-26 BL-SY - -

VTP-27 BL-SY - -

VTP-28 BL-SY - -

VTP-29 BL-SY - -

VTP-30 BL-SY - -

VTP-31 BL-SY - -

VTP-32 BL-SY - -

VTP-33 BL-SY - -

VTP-34 BL-SY - -

VTP-35 BL-SY - -

VTP-36 BL-SY - -

VTP-37 BL-SY - -

VTP-38 BL-SY - -

VTP-39 BL-SY - -

VTP-40 BL-SY - -

VTP-41 BL-SY - -

VTP-42 BL-SY - -

VTP-43 BL-SY - -

VTP-44 BL-SY - -

VPP-00 BL-SY - -

VPP-01 BL-SY - -

VPP-02 BL-SY - -

VPP-03 BL-SY - -

VPP-04 BL-SY - -

VPP-05 BL-SY - -

VPP-06 BL-SY - -

VPP-07 BL-SY - -

VPP-08 BL-SY - -

VPP-09 BL-SY - -

VPP-10 BL-SY - -

VPP-11 BL-SY - -

VPP-12 BL-SY - -

VPP-13 BL-SY - -

VPP-14 BL-SY - -

VDS-00 WO-BU - -


Commissioning BSC3i

VDS-01 WO-BU - -

VDS-02 WO-BU - -

VDS-03 WO-BU - -

VDS-04 WO-BU - -

VDS-05 WO-BU - -

VDS-06 WO-BU - -

VDS-07 WO-BU - -

VDS-08 WO-BU - -

VDS-09 WO-BU - -

VDS-10 WO-BU - -

VDS-11 WO-BU - -

VDS-12 WO-BU - -

VDS-13 WO-BU - -

VDS-14 WO-BU - -

VDS-15 WO-BU - -

COMMAND EXECUTED

where

FDU = Magneto-optical disk unit

LPT = Line printer

VDU = Display unit

WDU = hard disk unit

VTP = Virtual Terminal

VPP = Virtual Printer Protocol

VDS = Virtual Data Storing device

Not included in the printout example, but may appear with DCAR-1 carrierunit and USB memory:

UMS = USB Mass Storage

The disk drives should enter the state WO-BU and remain in it. The VDUand LPT units are in WO-ID or BL-SY state, depending on whether theterminal equipment is connected or not. The printer remains in the stateWO-BU only for the period during which it is printing.

The state of the units can be changed with the ISC command.

Unexpected outcome

DN02199145Issue 5-1 en04/06/2008



If some peripheral devices cannot be brought into the state WO-BU, checkthe operation and cabling of the peripheral devices. The disk drives havediagnostics of their own. The printers and display units have been tested inconnection with preparatory measures.


Commissioning BSC3i

6 Checking the EMB in BSC3i

The purpose of the checking of the message bus connections is to verifythe Ethernet message bus (EMB) LAN connections and the MACaddresses of the computers in the LAN. The test is executed with thecommands of the EBSTER service terminal extension. For moreinformation on EBSTER, see EBSTER.

Before you start

The EMB LAN switches (ESB26 plug-in units) are configured automaticallywhen they receive an IP address from the dynamic host configurationprotocol (DHCP) server. Check the configuration of switches with the W6RMML command.

Steps

1. Go to the service terminal.

ZDDS;

2. Load EBSTER.

ZLP:1,EBS;

3. Start EBSTER.

Z1;

4. Send a test message using EMB-0.

The printout is the configuration of the related BSC.

00:EBS> AT:0x007F,0

Message sent Received test messages using EMB-0 from following units:

==================================================================================

0000, 0004, 0005, 0030, 0031, 0032, 0033, 0034, 0035, 0036, 0037, 0038, 0039, 003A

DN02199145Issue 5-1 en04/06/2008


Checking the EMB in BSC3i

5. Send a test message using EMB-1.


00:EBS> AT:0x007F,1

Message sent

Received test messages using EMB-1 from following units:

==================================================================================

0000, 0004, 0005, 0030, 0031, 0032, 0033, 0034, 0035, 0036, 0037, 0038, 0039, 003A

6. Check the MAC addresses of all computer units.


00:EBS> A:0x000:0xFFFF

EMB-0 OK, EMB-1 OK

Unit MAC addr 0 Mac addr 1 MB CID EMB0 EMB1 CPU SCD

=======================================================================

0000 02:00:00:80:00:20 02:00:00:80:00:30 0000 0000 OK OK CP816-A OK

0004 02:00:00:80:01:20 02:00:00:80:01:30 0001 0001 OK OK CP816-A OK

0005 02:00:00:80:02:20 02:00:00:80:02:30 0002 0002 OK OK CP816-A OK

0030 02:00:00:80:03:20 02:00:00:80:03:30 0003 0003 OK OK CP816-A OK

Check that all computer units are listed and that there are two MACaddresses for each computer.

7. Exit EBSTER.

Z;

8. Unload EBSTER.

ZL:1;

Further information



Commissioning BSC3i

7 Checking the clock equipment in BSC3i

The purpose of the test is to verify that the switchover of the ClockSynchronisation Unit and Clock works, and that the Clock SynchronisationUnits provide the required clock signals.

7.1 Checking the switchover of the clocksynchronisation unit and the clock and alarmbuffer

Steps

1. Check the alarm indicator.

Make sure that the red alarm indicator light is not lit on either of theCL3TG plug-in units.

If the alarm light is on, the fault lies in the CL3TGs or in the CLOCcartridge.

2. Check the active unit indicator.

Make sure that the active unit indicator LED of the active CL3TG unitis on.

The CL3TG consists of two duplicated units which supervise eachother: when one detects any serious alarm condition in the otherunit, it can activate itself as the master.

3. Test the switchover control.

Test the switchover control of the duplicated CL3TG.

DN02199145Issue 5-1 en04/06/2008


Checking the clock equipment in BSC3i

First, test the control with the front panel switch (FCTRL) and then byremoving the fuse of the unit. Do this first to the active and then tothe passive unit.

Further information

Checking the synchronisation unit


7.2 Checking the synchronisation unit

The purpose of this check is to check the functionality of the connectionbetween the clock synchronisation units and the Operation andMaintenance Unit (OMU). Make sure that both clock synchronisation unitsautomatically perform switchover of synchronisation signals if errors occur.

Before you start

The connection between the OMU and the clock synchronisation unitsmust operate. Check the connection with the DRI command. Thecommand should not cause any error messages. For the connection tooperate, the OMU must be ready for use.

If there are no synchronisation connections to a higher-level exchange, theunit should be in PLESIOCHRONOUS MODE (DRI command).


7.2.1 Simulating the synchronisation inputs

Steps

1. Make a loop-back.

Make a loop-back in the four synchronisation input ET16s using theRJ45 connector. The default values of ET16s are 512, 576, 528, and592. Make the loop-back to the following connection:

-1 => 4

-2 => 5


Commissioning BSC3i

This enables the synchronisation tests to be executed with thesimulated synchronisation inputs.

2. Connect the loop-backs to the ETs.

3. Set all synchronisation inputs to the state CONNECTED.

4. Open new synchronisation input (DRC).

Open the new synchronisation input with the DRC command, forexample:

ZDRC:2M2;

5. Delete the synchronisation inputs (DRD).

ZDRD:2M2;

The synchronisation input 2M1 should be in the state CONNECTEDand in use (USED INPUT). Check this with the DRI command:

ZDRI;

The other synchronisation inputs should also be in theCONNECTED state.

7.2.2 Checking the synchronisation unit with a changeover

Steps

1. Check the indicator lamp.

Check that on both CL3TG plug-in units the indicator lamp number 1is lit.

2. Make a changeover to the backup connection (DRS, DRI).

Disconnect the first loop-back at the connector of the ET16.

The clock synchronisation unit changes over to the clock input of thenext priority within the fault toleration time (TP). TP can be modifiedwith the DRS command:

ZDRS;

DN02199145Issue 5-1 en04/06/2008



The default value of the time is 5 minutes. The LEDs on the CL3TGplug-in units indicate the new synchronisation input.

The 2M1 synchronisation input is in the state FAULTY and the nextinput in the state CONNECTED and in use. This can be checkedwith the DRI command:

ZDRI;

The following messages are displayed on the alarm printer:

2641 FAILURE IN SYNCHRONISATION SIGNAL

0630 SYNCHRONISATION SIGNAL CHANGED

3. Disconnect the second loop-back.

The procedure and results are the same as in step 2.

4. Make a changeover to internal oscillator (DRI).

Disconnect the loop-back of the last synchronisation input.

The clock synchronisation unit should switch to plesiochronousoperation within the time TP. All the synchronisation input indicatorson the active CL3TG unit are switched off and all indicators on thepassive CL3TG unit are lit.

The DRI command gives the following result:

SYNCHRONIZATION UNIT WORKING MODE.............. PLESIOCHRONOUS MODE

5. Make a synchronisation with external clock.

Return the loop-backs one by one, starting from the lowest priority.

Expected outcome

CL3TGs have four synchronisation inputs. The clock synchronisation unitswitches over to use the input 2M1 first, then 2M2, 2M3, and 2M4respectively, within the time TR. The default time value is 10 minutes. Tomodify the time TR, use the DRS command.

On both CL3TG plug-in units, the indicator lamp for the synchronisationinput in question is lit.


Commissioning BSC3i

Verify with the DRI command that the input is in the state CONNECTEDand in use (USED INPUT).

Faults can be corrected with MML commands.

A CL3TG in state PLESIOCHRONOUS searches for the incoming signalfrom the entire adjustment range by forcing the desired input into use withthe DRS command, for example

ZDRS:U=2M1;

When the clock synchronisation unit has been synchronised to this input,the forced control can be removed with the DRS command, for example

ZDRS:U=OFF;

Further information


DN02199145Issue 5-1 en04/06/2008




Commissioning BSC3i

8 Checking the hardware configuration ofBSC3i

Steps

1. Print the hardware configuration (WTI).

ZWTI:J;

ZWTI:C;

ZWTI:U;

ZWTI:P;

Compare the hardware configuration to the Equipment List forBSC3i in Nokia BSC Base Station Controller, Rel. S12, SiteDocumentation for BSC3i.

Further information


DN02199145Issue 5-1 en04/06/2008


Checking the hardware configuration of BSC3i


Commissioning BSC3i

9 Checking the maintenance system ofBSC3i

The maintenance system is checked to ensure that the supervision, alarm,and recovery functions of the system are working properly. Thesupervision functions are mainly system-internal and they are tested inconnection with the checking of the alarm system.

Since the outputs presented here are examples only, the actual outputsmay in some cases differ from them.

Before you start

A prerequisite for the checking of the BSC3i maintenance system is thatthe checks connected with the system start-up have been successfullyperformed.

9.1 Testing the alarm system

The checking of the alarm system covers the testing of the wired alarmsand the external alarms. Software alarms are monitored during the testing.

9.1.1 Testing wired alarms

The purpose of the test is to ensure that the alarm files have been correctlypackaged and that the wired alarms have been correctly cabled anddefined in the database.

The following wired alarms are tested:

. Cartridge power alarms

(2757 CARTRIDGE NON REDUNDANT POWER SUPPLYFAILURE)

DN02199145Issue 5-1 en04/06/2008


Checking the maintenance system of BSC3i

. PDFU (power distribution and fuse unit) panel alarms

(2758 POWER SUPPLY ADAPTER FAILURE)

. PDFU (power distribution and fuse unit) panel alarms

(2759 POWER SUPPLY FUSE FAILURE)

. FAN units alarms

(3146 FAN UNIT FAILURE)

Before you start

Before the test, check that the Operation and Maintenance Unit (OMU) isin the state WO-EX.

Steps

1. Output the alarms.

Output the alarms with the command WAE. The command also testsall created alarm groups. Compare the data in the lists with theconfiguration.

ZWAE:1A;

LOADING PROGRAM VERSION 5.7-0

BSC3i KARHU 2006-11-14 08:43:24

CONNECTION PLUG-IN UNIT: HWAT

MASTER UNIT: OMU 1A002-06

ALARM CARTRIDGE CARTRIDGE INPUTS OF ALARM GROUP INFO

GROUP TYPE COORDINATES 0 1 2 3

-----------------------------------------------------------------------------

1 PSAD & PSFP 1A 2759 - 2758 -

2 CC4C_A 1A002-00 2757 2755 - -

3 CC4C_A 1A002-03 2757 2755 - -

4 NOT CONFIG - - - -

5 CC3C_A 1A003-00 2757 2755 - -

6 CC3C_A 1A003-04 2757 2755 - -

7 CC3C_A 1A003-08 2757 2755 - -

8 CC3C_A 1A004-00 2757 2755 - -

9 CC3C_A 1A004-04 2757 2755 - -

10 CC3C_A 1A004-08 2757 2755 - -

11 CM2C_A 1A002-06 2757 2755 - -

12 GT6C_A 1A001-08 - 2755 - -

13 GT6C_A 1A001-10 - 2755 - -

14 FTRB_A 1A021-00 3146 3146 3146 3146

15 NOT CONFIG - - - -


Commissioning BSC3i

USED ALARMS:

2755 CARTRIDGE CLOCK FAILURE

2757 CARTRIDGE NON-REDUNDANT POWER SUPPLY FAILURE

2758 POWER SUPPLY ADAPTER FAILURE

2759 POWER SUPPLY FUSE FAILURE

3146 FAN UNIT FAILURE

IN FAULT CONDITIONS THE PRINT-OUT CONTAINS INFORMATION AFTER THE

ALARM NUMBER WHETHER THE WIRED ALARM INPUT IS PERMANENTLY "0" OR "1".

COMMAND EXECUTED

2. Test the alarms.

The alarms are tested as follows:

Alarm 2757

a. Switch off the power from the computer unit PSC6 plug-in unitand verify the alarm from the alarm printer.

b. Turn the power back on and verify the cancelling of the alarm.

c. Wait until all recovery functions have been completed.

d. Check the diagnostics results from the printer.

e. Repeat the same procedure for every cartridge (except OMU).

Alarm 2758

a. Switch off one switch from the PDFU and verify the alarm fromthe alarm printer.

b. Turn the switch on and verify the cancelling of the alarm.

c. Repeat the same procedure one by one for every switch in allPDFUs.

Alarms 2759 and 3146

a. Remove one fuse from the PDFU panel and verify alarm 2759from the alarm printer.

b. When the fan unit's fuse is removed, alarm 3146 is set and theother fan units start to run faster.

c. Put the fuse back and verify the cancelling of the alarm.

d. Wait until all recovery functions have been completed.

e. Repeat the same procedure for every fuse one by one (exceptOMUs).

Further information

Testing external alarms

DN02199145Issue 5-1 en04/06/2008



Testing alarm outputs

9.1.2 Testing external alarms

Steps

1. Output wired alarms (WAP).

2. Check external alarms (WAT).

Check that the external alarms specified in the source data havebeen printed out.

If there are no external alarms specified, you have to create one fortesting all external alarm inputs:

ZWAA:4000:EX:"TEST";

3. Connect alarm inputs (WAI).

Connect the alarm inputs one by one to the test alarm.

ZWAI:HWAT:OMU:<alarm input>,4000,”TEST”:;

where

alarm input: the input to be tested (0-23)

4. Cause the alarm.

Cause the alarm by wiring the alarm input to the ground.

AEI = voltage-controlled external alarm input signal

The table below shows the position of voltage-controlled externalalarm pins on the connector panel CPRJ45-A of the female D25connector (no 21):

Table 4. Voltage-controlled external alarm pins on the connector panel of thefemale D25 connector (connector 21)

Pin Alarm no

1 AEI0


Commissioning BSC3i

Table 4. Voltage-controlled external alarm pins on the connector panel of thefemale D25 connector (connector 21) (cont.)

Pin Alarm no

2 AEI1

3 AEI2

4 AEI3

5 AEI4

6 AEI5

7 AEI6

8 AEI7

9 AEI8

10 AEI9

11 AEI10

12 AEI11

13 AEI12

14 AEI13

15 AEI14

16 AEI15

17 AEI16

18 AEI17

19 AEI18

20 AEI19

21 AEI20

22 AEI21

23 AEI22

24 AEI23

25 GND

When you wire all the alarm inputs (AEI0-AEI23) one by one, youshould receive an alarm printout concerning each alarm and thecancelling of the alarm. In this example, the alarm number 4000 andtext TEST should appear on the alarm printer.

The polarity of the alarm input can be changed with the WAXcommand:

ZWAX:HWAT:OMU:<alarm input>:POL=0,TEXT=”TEST”:;

DN02199145Issue 5-1 en04/06/2008



5. Delete the alarms.

After testing, delete the alarms you created:

a. Close the alarm input:

ZWAD:HWAT:OMU:<alarm input>;

b. Remove the external alarm:

ZWAR:4000;

c. Check the external alarms:

ZWAT;

Further information

Testing wired alarms

Testing alarm outputs

9.1.3 Testing alarm outputs

Steps

1. Set an alarm output to ON or OFF state (ALU, ALS).

ZALU:UPD;

ZALS:<alarm output>:ON;

where

alarm output: the identity of the alarm output

The easiest way to test the alarm outputs is to use the lamp panel,provided that the lamp panel is installed.

Another way to test the alarm outputs is to measure the output ofAEO0-AEO15 from the connector panel (see Testing externalalarms). The change of the state should appear as a change ofvoltage from 0V to 5V.

The table below illustrates the position of alarm output pins on theconnector panel of the female D25 connector (no 22).


Commissioning BSC3i

Table 5. Alarm output pins on the connector panel of the female D25connector (connector 22)

Pin Alarm output no

1 AEO0

2 AEO1

3 AEO2

4 AEO3

5 AEO4

6 AEO5

7 AEO6

8 AEO7

9 AEO8

10 AEO9

11 AEO10

12 AEO11

13 AEO12

14 AEO13

15 AEO14

16 AEO15

17 –

18 –

19 –

20 –

21 –

22 –

23 –

24 –

25 GND

Further information

Testing wired alarms

Testing external alarms

DN02199145Issue 5-1 en04/06/2008



9.2 Testing the recovery from power breaks

The purpose of the tests is to test the recovery of the system from differentpower breaks. The system automatically disables those units which arewithout power after a power break. The system starts the units in theircorrect working state after the power is on again.

It is recommended that the external synchronisation is connected to theBSC3i before the power break tests or that the ET used forsynchronisation is looped during this test. Remember to disconnect theloop immediately after the test.

If the loop is not disconnected, the oscillators of the CLSs will drift to theend of their control range. If the BSC3i is not getting any synchronisation,alarms 1010 and 1598 are issued. They are cancelled automatically afterthe recovery actions which take approximately 10 minutes.

9.2.1 Testing the recovery from a complete power break in the system

Steps

1. Connect alarm printer and the MML terminal to the BSC.

2. Check that all units are in states WO-EX or SP-EX (USI, ISI).

If a unit is not in the appropriate state, change the state with the USCcommand.

ETs may be in SE-NH states.

3. Disconnect power from the system.

4. Connect power to the system.

The system is started and it begins loading from the disks.

5. Wait until OMU starts in state WO-EX.

Monitor the alarm printer. All the starting computer units shouldcause a notice:

0691 AUTOMATIC RECOVERY ACTION WO-RE TO WO-EX

or


Commissioning BSC3i

0691 AUTOMATIC RECOVERY ACTION SP-RE TO SP-UP

or

0691 AUTOMATIC RECOVERY ACTION SP-UP TO SP-EX

Duplicated pre-processor units (for example, the synchronisationunit CLS) independently determine which unit is active and which ispassive.

The following notice is displayed:

MMI SYSTEM READY

6. Start a session from an MML terminal.

During the start-up of the OMU, the recovery system analyses thecondition of the BSC and starts the control of the system start-up.

The following text is printed on the alarm printer:

0689 SYSTEM RESTARTED

7. Output the working states of the units from the MML terminal.

8. Monitor the unit states (USI).

Check that every unit starts in the state it had before the powerbreak:

ZUSI;

9. Monitor the alarm printer.

All the starting units should cause a notice (one of the following):

0691 AUTOMATIC RECOVERY ACTION WO-RE TO WO-EX

0691 AUTOMATIC RECOVERY ACTION SP-RE TO SP-UP

0691 AUTOMATIC RECOVERY ACTION SP-UP TO SP-EX

10. Print out the states (USI, USL).

Print out the states of all the units and check that they are in thecorrect working state. Use the following commands to output theworking states of the units:

DN02199145Issue 5-1 en04/06/2008



ZUSI:ALL;

or alternatively,

ZUSL:,INCO;

which outputs all those units whose state is incorrect.

11. Update the date and time (DCS).

ZDCS:<date>,<time>:ST=OFF/ON;

12. Check the states of WDU devices (ISI, ISC).

ZISI;

If the states are not WO, change them:

ZISC;

Further information

Testing a power break in the PDFU

Testing fuse fault in supply cable

9.2.2 Testing a power break in the PDFU

Steps

1. Connect the alarm printer and the MML terminal to the BSC.

2. Check that the units are in states WO-EX and SP-EX (USL, USC,ISC).

To output the units which are in an incorrect state:

ZUSL:,INCO;

Change the state with the USC command, if necessary.

Change the I/O unit's state with the ISC command, if necessary.

ETs may be in SE-NH states.


Commissioning BSC3i


To monitor the recovery functions, connect the service terminal tothe MCMU.

When the power is disconnected from the OMU, the MML terminaland the alarm printer are not functional. The system, however,recovers also in this condition as the recovery functions of thesystem are then handled in the active MCMU. In this case, you canmonitor the recovery functions with the service terminal from theactive MCMU as follows:

a. Connect the service terminal to the active MCMU.

b. Take into use the debugger software used for testing therecovery system.

ZLE:U,RCBUGGGX;

c. Output the states of the units in a normal way as from an MMLterminal (USI or USIC).

ZUSI:COMP;

or

ZUSIC:COMP;

4. Disconnect the power from the PDFU.

This should be done one by one so that both switches of the PDFUare switched off at the same time.

If the PDFUs are disconnected too long (more than 5 seconds), thetest does not pass the computers and the PDFUs are found to befaulty (SE-OU). Depending on the power break time, it is possiblethat the unit is not ready for diagnostics. If so, it does not answer thediagnostics message the first time. On the second time, the recoverybrings the unit up and the diagnostics succeeds.

5. Wait until all the recovery functions have been completed.

6. Check the states of the WDU devices (ISI, ISC).

ZISI;

If the states are not WO, change them:

ZISC::WDU,<ind>:WO-BU;

Expected outcome

DN02199145Issue 5-1 en04/06/2008



1. When the alarm is repeated, the unit without power is separated andthe backup unit is taken into use, provided that the unit type inquestion has a backup unit. The units without backup stay in thestate WO-EX FAULTY.

If a faulty unit remains in use, the following alarm is printed out:

2693 WO-EX UNIT FAULTY

If a unit is in TE-ID or in SE-OU, the following alarm is printed out:

2692 INCORRECT WORKING STATE

2. When the unit enters the TE state, the testing of the unit is started. Ifthe test proves that the unit is in order, the state of the unit isautomatically changed into WO-EX or SP-EX.

3. Check that there are appropriate notifications on state changes.

4. Check that there are diagnostics reports which indicate that the unitis in working order:

3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK

After the execution of every partial diagnosis the following text isdisplayed:

3996 PARTIAL DIAGNOSIS EXECUTED

In fault conditions, see Failure Printouts.

Further information

Testing the recovery from a complete power break in the system

Testing a fuse fault in the supply cable

9.2.3 Testing a fuse fault in the supply cable

Steps

1. Connect the alarm printer and MML terminal to the BSC.

2. Check that the units are in states WO-EX and SP-EX (USI).

ZUSI;

3. Remove the fuse of the supply cable.


Commissioning BSC3i

4. Connect the fuse.

5. Wait until the recovery measures have been completed.

6. Repeat steps 1 to 4 for all the supply fuses.

Expected outcome

1. If there is only one supply cable in the system, the system isrestarted.

2. If there are several supply cables in the system, the operation of thesystem must not totally cease during the power break.

3. If the power supply of the system has been secured with a batteryand an emergency power supply, no action takes place. If the powerdisappears from the system, the functioning of the battery andemergency power supply must be checked.

Further information

Testing the recovery from a complete power break in the system

Testing a power break in the PDFU

9.3 Testing state transitions and unit diagnostics

Steps

1. Connect the alarm printer and MML terminal to the BSC.

2. Change the state of the OMU unit from WO to TE to SE to TE(USC).

Example

ZUSC:OMU:TE;

ZUSC:OMU:SE;

ZUSC:OMU:TE;

3. Run diagnostics on the OMU (UDU).

ZUDU:OMU;

DN02199145Issue 5-1 en04/06/2008



The diagnostics reports indicate that the unit is in working order:


4. Change the state of OMU to WO (USC).

ZUSC:OMU:WO;

Note

During the OMU restart, the MML and LPT connection is lost.

5. After the OMU recovery, change the state of the SP MCMU to TEto SE to TE (USC).

Example

ZUSC:MCMU,<ind>:TE;

ZUSC:MCMU,<ind>:SE;

ZUSC:MCMU,<ind>:TE;

6. After the MCMU recovery, run total diagnostics (UDU).

ZUDU:MCMU,<te>;



7. Change the state of the MCMU from TE to SP (UDU).

ZUDU:MCMU,<te>:SP;

8. Change the state of the SP BCSU from SP to TE to SE to TE(USC).

Example

ZUSC:BCSU,<ind>:TE;

ZUSC:BCSU,<ind>:SE;


Commissioning BSC3i

ZUSC:BCSU,<ind>:TE;

9. After the BCSU recovery, run total diagnostics (UDU).

ZUDU:BCSU,<te>;



10. Change the state of the BCSU from TE to SP (USC).

ZUSC:BCSU,<ind>:SP;

11. Change the state of the WO BCSU from WO to SP (USC).

ZUSC:BCSU,<ind>:SP;

12. Repeat steps 8 to 11 until all BCSU units are tested.

13. Change the state of the SP CLS to TE to SE to TE (USC).

Example

ZUSC:CLS,<ind>:TE;

ZUSC:CLS,<ind>:SE;

ZUSC:CLS,<ind>:TE;

14. Run total diagnostics for the CLS unit (UDU).

ZUDU:CLS,<te>;



15. Change the state of the CLS unit to SP (USC).

ZUSC:CLS,<ind>:SP;

16. Change the state of the WO CLS unit to SP (USC).

ZUSC:CLS,<ind>:SP;

DN02199145Issue 5-1 en04/06/2008



17. Repeat steps 13 to 15.

18. Change the state of the SP CLAB to TE to SE to TE in the CLAC0 cartridge (USC).

Example

ZUSC:CLAB,<ind>:TE;

ZUSC:CLAB,<ind>:SE;

ZUSC:CLAB,<ind>:TE;

19. Run total diagnostics for the CLAB (UDU).

ZUDU:CLAB,<te>;



20. Change the state of the CLAB to SP (USC).

ZUSC:CLAB,<ind>:SP;

21. Change the state of the WO CLAB unit to SP (USC).

ZUSC:CLAB,<ind>:SP;


23. Repeat steps 18 to 22 with the CLAC 1 cartridge.

24. Change the state of the SP SBUS to TE to SE to TE (USC).

Example

ZUSC:SBUS,<ind>:TE;

ZUSC:SBUS,<ind>:SE;

ZUSC:SBUS,<ind>:TE;

25. Run total diagnostics for the SBUS (UDU).

ZUDU:SBUS,<te>;


Commissioning BSC3i



26. Change the state of the SBUS to SP (USC).

ZUSC:SBUS,<ind>:SP;

27. Change the state of the WO SBUS unit to SP (USC).

ZUSC:SBUS,<ind>:SP;


29. Change the state of the SP EMB to TE to SE to TE (USC).

Example

ZUSC:EMB,<ind>:TE;

ZUSC:EMB,<ind>:SE;

ZUSC:EMB,<ind>:TE;

30. Run total diagnostics for the EMB (UDU).

ZUDU:EMB,<te>;



31. Change the state of the EMB to SP (USC).

ZUSC:EMB,<ind>:SP;

32. Change the state of the WO EMB unit to SP (USC).

ZUSC:EMB,<ind>:SP;


34. Connect the ETs (WUC).

DN02199145Issue 5-1 en04/06/2008



The ETs have to be connected with the WUC command beforetesting. For more information, see Configuring and managing ET4s/ET16s in Creating and Managing BSC Hardware under Install andupgrade/Hardware in the PDF view or BSS Integration underIntegrate in the PDF view for details.

35. Change the state of the ETs from SE to TE one by one (USC).

Example

ZUSC:ET,<ind>:SE;

ZUSC:ET,<ind>:TE;

36. Run diagnostics on the ET units (UDU, UDQ).

ZUDU:ET,<ind>;

With the UDQ command you can monitor the diagnostics being run.



37. Change the state of the ETs to WO or SE (USC).

ZUSC:ET,<ind>:WO;

or

ZUSC:ET,<ind>:SE

38. Change the state of the STMUs from WO to TE (USC).

ZUSC:STMU,<ind>:TE;

39. Run diagnostics on the STMU units (UDU).

ZUDU:STMU,<ind>;



40. Change the state of the STMUs from TE to WO (USC).


Commissioning BSC3i

ZUSC:STMU,<ind>:WO;

41. Change the state of the SWUs from WO to TE (USC).

ZUSC:SWU,<ind>:TE;

42. Run diagnostics on the SWU units (UDU).

ZUDU:SWU,<ind>;



43. Change the state of the SWUs from TE to WO (USC).

ZUSC:SWU,<ind>:WO;

44. Change the state of the SETs to TE (USC).

ZUSC:SET,<ind>:TE;

45. Run diagnostics on the SET units (UDU).

ZUDU:SET,<ind>;



46. Change the state of the SETs to their original state (USC).

ZUSC:SET,<ind>:<original_state>;

47. Make a MCMU switchover (USC).

ZUSC: MCMU,<wo>:SP;


49. If a PIU unit fails in the diagnostics test, change the unit.

DN02199145Issue 5-1 en04/06/2008



Further information

9.4 Diagnostics of the I/O devices: FDU

When performing magneto-optical disk unit (FDU) diagnostics, follow thisprocedure.

Steps

1. Check the state of the I/O devices (ISI).

2. Change the state of the FDU to TE-ID (ISC).

ZISC::FDU,0:WO-ID;

ZISC::FDU,0:TE-ID;

3. Run diagnostics for the FDU (UDD).

ZUDD:OMU:FDU,0;



4. Change the FDU to the original state (ISC).

ZISC::FDU,0:WO-ID;

ZISC::FDU,0:WO-BU;

5. Repeat steps 1 to 4 with the rest of the I/O devices.

The devices are:

LPT ... LINE PRINTER

WDU ... HARD DISC UNIT

Further information

When testing the FDU, the initialised MO disk should be in the driver.


Commissioning BSC3i

9.5 Diagnostics of the I/O devices: UMS

When performing USB mass storage (UMS) diagnostics, follow thisprocedure.

Steps

1. Check the state of the I/O devices (ISI).

2. Change the state of the UMS to TE-ID (ISC).

ZISC::UMS,0:WO-ID;

ZISC::UMS,0:TE-ID;

3. Run diagnostics for the UMS (UDD).

ZUDD:OMU:UMS,0;



4. Change the UMS to the original state (ISC).

ZISC::UMS,0:WO-ID;

ZISC::UMS,0:WO-BU;

5. Repeat steps 1 to 4 with the rest of the I/O devices.

The devices are:

LPT ... LINE PRINTER

WDU ... HARD DISC UNIT

Further information

UMS device must be connected when running the diagnostics.

DN02199145Issue 5-1 en04/06/2008



9.6 Testing the spare units

Steps

1. Equip the BSC with spare plug-in units and performdiagnostics.

Follow the instructions in Testing state transitions and unitdiagnostics.

2. Write a problem report if faulty plug-in units are found.

3. Change the faulty plug-in units.

Further information


Commissioning BSC3i

10 Checking the ESB switch in BSC3i

The ESB switches are located in the MCMU and LANU units.

10.1 Local reset and the Hotswap button in the ESBswitch

The ESB switch gets power from the MCMU or LANU unit. The ESB switchcan be disconnected without switching the power off from other PIUs in theMCMU or LANU.

Steps

1. Check the Operation Indicator.

The Operation Indicator (OPR) is a single two-colour led (green/red)in the front panel of the ESB switch.

Explanations on the indicator light:. Green indicates that the unit is operational.. Red is lit during the power up and in fault conditions.. If the light is blinking, it means that no image software is

loaded.. If there is no light, it means that the power is off.

Green is the default colour for the OPR.

2. Perform the local restart and the hotswap.

To perform the hotswap, press the Hotswap reset button (RST) twicewithin two seconds before removing the card. The power is turnedoff for 20 seconds, during which the card can be removed safely.

3. Set the ESB switch.

DN02199145Issue 5-1 en04/06/2008


Checking the ESB switch in BSC3i

Set the ESB switch back to its position. The OPR should be first redand after a while change to green.

4. Repeat steps 1 to 3 with every ESB switch.

Further information


10.2 Checking the built-in self test of the ESB26 switch

The ESB26 switch uses the Command Line Interface (CLI) forcommunication. The terminal should be VT-100 or compatible.

Steps

1. Configure the terminal.

Before the CLI connection can be made, a PC or laptop terminalneeds to be configured.

Table 6. Terminal settings for CLI

Baud rate 9600

Data bits 8

Stop bits 1

Parity None

Flow control X on/X off

2. Open the ESB26 switch service terminal session.

To open the ESB26 switch service terminal session, a serial cableshould be connected between the PC/laptop serial port and theESB26 switch serial RJ45 port (SER1).

If the power of the ESB26 switch is on, the service terminal sessionopens automatically after the physical connection is set. Thepassword is “nokia”, remember to press <CR> after giving thepassword.


Commissioning BSC3i

User Access Verification

Password:

SWU-0>

3. Check the built-in self test.

After giving the password, type “enable” and press <CR> to turn onthe privileged mode command. After that you can execute the selftest by typing “self-test” and pressing <CR>.

SWU-0>enable

SWU-0#self-test

CPU Core Test :

CPU Validation - Passed

CPU Notify RAM Test :

RAM Validation - Passed

CPU Interface Test :

UART Existence - Passed

Testing Switch Core :

Crossbar Existence - Passed

Data Buffer Test :

Boot Loader Image Validity - Passed

Application Image Validity - Passed

Startup Configuration Validity - Passed

Script File System Validity - Passed

PROM Device Access Validity - Passed

On-board Power Test :

On-board Power PHY - Passed

On-board Power CPU - Passed

On-board Power OC - Passed

Temperature Test :

Temperature - Passed

4. Check the boot and software version.

You can see the switch boot and software version by typing “reload”and pressing <CR>. If you want to logout at this moment, you cantype “exit” and press <CR>.

SWU-0#reload

Save current configuration and reboot the Switch ? [y/n] : y

Building the configuration ...

Rebooting ...

DN02199145Issue 5-1 en04/06/2008


Checking the ESB switch in BSC3i

Press any key to stop auto-boot...

0

Verifying validity of primary application.....OK

Start primary application...

BUILT-IN SELF TEST

------------------

CPU Core Test : Passed

CPU Notify RAM Test : Passed

CPU Interface Test : Passed

Testing Switch Core : Passed

Data Buffer Test : Passed

On-board Power Test : Passed

////////////////////////////////////////////////////////////////////////

// //

// N O K I A //

// //

// //

// Switch model : NOKIA ESB26 //

// SW version : 3.13.1.4 created Mar 7 2005 - 13:30:39 //

// //

////////////////////////////////////////////////////////////////////////

User Access Verification

Password:

5. Repeat steps 2 to 4 with every ESB switch.

Further information



Commissioning BSC3i

11 Verifying the software versions of BSC3i

The purpose of this check is to verify the software (SW) versions,comparing them with the Delivery Catalogue, and making sure that thedata in the modules is not corrupted.

Steps

1. Start an MML session.

2. Print out all SW packages (WQO).

Print out all SW packages installed on disks.

ZWQO;

and

ZWQO:CR;

3. Perform a verification (WQB).

Perform a verification for each SW package.

The display prints out on the printer during the execution of thecommand

ZWQB:STAT=<running_packet_status>;

4. Check if any faults have been detected.

Compare the printout with the Delivery Catalogue.

Expected outcome

The SW verification should be faultless and the versions should be sameas those listed in the Delivery Catalogue.

DN02199145Issue 5-1 en04/06/2008


Verifying the software versions of BSC3i

Unexpected outcome

If any faulty modules are found, replace them with new ones.

Further information



Commissioning BSC3i

12 Copying additional software and settingthe time zone in BSC3i

Steps

1. Insert the Customer Specific disk to the BSC3i magneto-opticaldrive or USB stick to the carrier unit.

Whether the software is delivered on an MO disk or an USB memorydepends on the HW equipment version.

The disk / USB memory contains the definitions of all the optionalfunctionalities which are included in the software build (softwarepackage). For information on the devices and tools needed, seeMeasurement devices and tools.

2. Copy the disk or USB memory contents (IWY, IBC).

When copying from MO disk:

ZIWY:S:SYSTEM=<BSC_name>,UNIT=OMU,PATH=/,DRIVE=FDU-N0;

ZIWY:D:SYSTEM=<BSC_name>,UNIT=OMU,PATH=/<path>/LFILES,DRIVE=WDU-SB;

ZIBC;

When copying from USB memory:

ZIWY:S:SYSTEM=<BSC_name>,UNIT=OMU,PATH=/,DRIVE=UMS-N0;

ZIWY:D:SYSTEM=<BSC_name>,UNIT=OMU,PATH=/<path>/LFILES,DRIVE=WDU-SB;

ZIBC;

DN02199145Issue 5-1 en04/06/2008


Copying additional software and setting the time zone in BSC3i

where

path: the path name of the new package.

3. Install the Change Deliveries.

Check that the general Change Deliveries (CD) are installed.

Check the CD level of the software build (WNH) and install the CDsthat have not been installed. See further instructions in the CDdocument.

4. Set the time zone (DCE).

ZDCE:<direction>:<difference>;

Example

Setting the time zone for GMT +1h

ZDCE:PLUS:01-00;

In the next phase, the BSC is restarted. After that the time zone setting isin use.

The time zone information is stored in a BSC3i file. The information needsto be set when commissioning a new BSC3i. This is particularly useful in anetwork where different BSC3is may belong to different time zones.

5. Change the clock to summer time/standard time (DCT).

ZDTC;

6. Restart the system (USS).

ZUSS:SYM:C=DSK;

Further information



Commissioning BSC3i

13 BSC3i commissioning test logs

Record confirmation of the test execution and possible comments in thetest logs along with your signature and date.

Part of the logs can be used as a checklist while testing.

Table 7. BSS specifications

Customer:

BSC number:

BCS Software release (xx.yy.-zz):

Checked by:

Date:

Approved by:

Date:

Table 8. Preparation of commissioning

Commissioning phase Completed

Check that the necessary measurement devices andtools are available

OK = Everything is in order

NOK = Something is wrong

DN02199145Issue 5-1 en04/06/2008


BSC3i commissioning test logs

Table 9. Checking the BSC3i internal cabling


Compare the internal cabling with InterconnectionCables in BSC3i in Nokia BSC Base StationController, Rel. S12, Site Documentation for BSC3i.



Table 10. Checking the functioning of the BSC3i hardware


Compare the interchangeability codes of the plug-inunits and cartridges with Hardware Revision List forBSC3i in Nokia BSC Base Station Controller, Rel.S12, Site Documentation for BSC3i.

Check the jumpers and the EPROM versions of theplug-in units and cartridges by comparing them to theversion list. When ready, tick the box in the followingtables. After checking the units, connect the ETcables.



Table 11. Checking strappings, DIP switches, memory, and EPROMs of theOMU

UnitCPU DIPswitches CPU FLASH CPU memory AS7 jumpers

AS7 DIPswitches

AC25 jumpers

OMU

Unit AC25 EPROM HWATjumpers

SEROjumpers

OPDUjumpers

OPDU DIPswitches

OMU




Commissioning BSC3i

NIU = Not in use

VER xx.xx = FLASH or EPROM version

xxx MB = Amount of CPU memory

Table 12. Checking strappings, DIP switches, memory, and EPROMs of theMCMUs

UnitCPU DIPswitches CPU FLASH CPU memory ESB EPROM ESB jumpers

SWCOPjumpers

MCMU 0

MCMU 1

Unit SWCOPEPROMs

SBCON2Ajumpers

ADMODD DIPswitches

MCMU 0

MCMU 1



NIU = Not in use



Table 13. Checking the strappings of GSW2KB

Unit SW256B jumpers

GSW2KB 0

GSW2KB 1



NIU = Not in use

DN02199145Issue 5-1 en04/06/2008



Table 14. Checking strappings, DIP switches, memory, and EPROMs ofBCSUs

UnitCPU DIPswitches CPU FLASH CPU memory

AS7 DIPswitches PCU jumpers

PCU DIPswitches

BCSU 0

BCSU 1

BCSU 2

BCSU 3

BCSU 4

BCSU 5

BCSU 6

BCSU 7

BCSU 8

BCSU 9

BCSU 10

Unit PCU FLASH

BCSU 0

BCSU 1

BCSU 2

BCSU 3

BCSU 4

BCSU 5

BCSU 6

BCSU 7

BCSU 8

BCSU 9

BCSU 10



NIU = Not in use




Commissioning BSC3i

Table 15. Checking EPROMs, DIP switches, and the jumpers of the ESB unitsof the LANUs

Unit LANU 0 LANU 1 LANU 2 LANU 3

ESB EPROM

ESB DIP switches

ESB jumpers



NIU = Not in use

VER xx.xx = EPROM or SW version

Table 16. Checking strappings, DIP switches, and FLASH of ETs in ETCcartridges

UnitETs inslot 01

ETs inslot 02

ETs inslot 03

ETs inslot 04

ETs inslot 05

ETs inslot 06

ETs inslot 07

ETs inslot 08

ETC 0jumpers

------ ------ ------ ------

ETC 0 DIPswitches

------ ------ ------ ------

ETC 0FLASH

------ ------ ------ ------

ETC 1jumpers

ETC 1 DIPswitches

ETC 1FLASH

ETC 2jumpers

ETC 2 DIPswitches

ETC 2FLASH

ETC 3jumpers

DN02199145Issue 5-1 en04/06/2008



Table 16. Checking strappings, DIP switches, and FLASH of ETs in ETCcartridges (cont.)

UnitETs inslot 01

ETs inslot 02

ETs inslot 03

ETs inslot 04

ETs inslot 05

ETs inslot 06

ETs inslot 07

ETs inslot 08

ETC 3 DIPswitches

ETC 3FLASH

ETC 4jumpers

ETC 4 DIPswitches

ETC 4FLASH

ETC 5jumpers

ETC 5 DIPswitches

ETC 5FLASH



NIU = Not in use

VER xx.xx = FLASH version

Table 17. Checking strappings, DIP switches, and FLASH of ETS2s andET16s in GTIC cartridges

Unit

ETS2 /ET16 inslot 01








GTIC 0jumpers

GTIC 0 DIPswitches

GTIC 0FLASH


Commissioning BSC3i

Table 17. Checking strappings, DIP switches, and FLASH of ETS2s andET16s in GTIC cartridges (cont.)

Unit









GTIC 1jumpers

GTIC 1 DIPswitches

GTIC 1FLASH



NIU = Not in use

VER xx.xx = FLASH version

Table 18. Checking the strappings and EPROMs of the clock equipment

Unit CLS 0 CLS 1 CLAB 0 CLAB 1 CLAB 2 CLAB 3

Jumpers

EPROMs

TON FIAEPROMs

------- ------- ------- -------



NIU = Not in use

VER xx.xx = EPROM version

Table 19. Checking the strappings of the clock cartridges

Unit COLC cartridge CLAC 0 cartridge CLAC 1 cartridge

Jumpers

DN02199145Issue 5-1 en04/06/2008





NIU = Not in use

Table 20. Testing the power supply


Measure the supply voltage from the PDE powersupply lines:

Nominal voltage: -48V or -60V

Tolerance: -40.5V to -72V



Table 21. Testing the peripheral units


Check that the settings of the VDU are as follows:

Baud Rate: 9600

Data Bits: 7

Stop Bits: 2

Parity: Even

Page Length: 23

Line Length: 80

Check that the settings of the printer are as follows:

Baud Rate: 9600

Data Bits: 7

Stop Bits: 2

Parity: Even

Page Length: 65

Line Length: 80



Commissioning BSC3i


Table 22. Opening the first MML session in the BSC


USERNAME <SYSTEM>

PASSWORD <SYSTEM>



Table 23. Monitoring the start-up of units


Loading of OMU

Loading of MCMUs

Loading of BCSUs



Table 24. Checking the I/O system of the BSC


Display all I/O devices

Power check of the MO drive

Power check of the WDU 0

Power check of the WDU 1



DN02199145Issue 5-1 en04/06/2008



Table 25. Testing the EMB connections of the BSC


EMB 0

EMB 1



Table 26. Checking the switchover and the alarms from the clocksynchronisation unit


Check the alarms from the clock units.

Test the switchover of the clock units with MML.

Test the switchover of the clock units with the frontpanel switch.



Table 27. Checking the clock synchronisation unit


Open two new synchronisation inputs. Make a loop-back in the four synchronisation input ET's.

Test a changeover to backup connection.

Test a changeover to internal oscillator.

Test synchronisation with external clock.




Commissioning BSC3i

Table 28. Checking the hardware configuration of the BSC


Print the hardware configuration and compare it tothe Hardware Revision List for BSC3i in Nokia BSCBase Station Controller, Rel. S12, SiteDocumentation for BSC3i.



Table 29. Testing the wired alarms

Unit Alarm 2757 Alarm 2758 Alarm 2759 Alarm 3146

MCMU 0 ------------ ------------

MCMU 1 ------------ ------------

BCSU 0 ------------ ------------

BCSU 1 ------------ ------------

BCSU 2 ------------ ------------

BCSU 3 ------------ ------------

BCSU 4 ------------ ------------

BCSU 5 ------------ ------------

BCSU 6 ------------ ------------

BCSU 7 ------------ ------------

BCSU 8 ------------ ------------

BCSU 9 ------------ ------------

BCSU 10 ------------ ------------

PDFU 0 ------------ ------------ ------------

PDFU 1 ------------ ------------ ------------

PDFU 2 ------------ ------------ ------------

PDFU 3 ------------ ------------ ------------

FTRB 0 ------------ ------------

FTRB 1 ------------ ------------

FTRB 2 ------------ ------------

FTRB 3 ------------ ------------

GSW 0 ------------ ------------ ------------

DN02199145Issue 5-1 en04/06/2008



Table 29. Testing the wired alarms (cont.)

Unit Alarm 2757 Alarm 2758 Alarm 2759 Alarm 3146

GSW 1 ------------ ------------ ------------

CLOC ------------ ------------ ------------

CLAC 0 ------------ ------------ ------------

CLAC 1 ------------ ------------ ------------

ETC 0 ------------ ------------ ------------

ETC 1 ------------ ------------ ------------

ETC 2 ------------ ------------ ------------

ETC 3 ------------ ------------ ------------

ETC 4 ------------ ------------ ------------

ETC 5 ------------ ------------ ------------

GTIC 0 ------------ ------------ ------------

GTIC 1 ------------ ------------ ------------

LANU 0 ------------ ------------

LANU 1 ------------ ------------

LANU 2 ------------ ------------

LANU 3 ------------ ------------



NIU = Not in use

Table 30. Testing the voltage controlled external alarms

Alarm Completed Alarm Completed

AEI0 AEI1

AEI2 AEI3

AEI4 AEI5

AEI6 AEI7

AEI8 AEI9

AEI10 AEI11

AEI12 AEI13


Commissioning BSC3i

Table 30. Testing the voltage controlled external alarms (cont.)


AEI14 AEI15

AEI16 AEI17

AEI18 AEI19

AEI20 AEI21

AEI22 AEI23



Table 31. Testing alarm outputs


AEO0 AEO8

AEO1 AEO9

AEO2 AEO10

AEO3 AEO11

AEO4 AEO12

AEO5 AEO13

AEO6 AEO14

AEO7 AEO15



Table 32. Testing the recovery from a complete power break in the system


Disconnect the power from the system.

Connect the power to the system.


DN02199145Issue 5-1 en04/06/2008




Table 33. Testing a power break in the PDFU


Remove the fuse. Wait until the recovery measureshave been completed and connect the fuse. Repeatfor all fuses.



Table 34. Testing a fuse fault in the power cable


Disconnect the power from each of the PDFU one byone



Table 35. Testing the state transition and unit diagnostics of the BSC's units


Testing the state transition and diagnostics of allunits. Tick the box in the following tables when ready.



Table 36. Testing the state transition and unit diagnostics of the units

Unit MCMU 0 WO state MCMU 1 WO state

OMU

MCMU 0 ----------------

MCMU 1 ----------------


Commissioning BSC3i

Table 36. Testing the state transition and unit diagnostics of the units (cont.)


BCSU 0

BCSU 1

BCSU 2

BCSU 3

BCSU 4

BCSU 5

BCSU 6

BCSU 7

BCSU 8

BCSU 9

BCSU 10

CLS 0

CLS 1

CLAB 0

CLAB 1

CLAB 2

SBUS 0

SBUS 1

EMB 0

EMB 1

STMU 0

STMU 2

STMU 4

STMU 6

STMU 8

STMU 10

STMU 12

STMU 14

STMU 16

STMU 18

STMU 20

STMU 22

DN02199145Issue 5-1 en04/06/2008



Table 36. Testing the state transition and unit diagnostics of the units (cont.)


STMU 24

STMU 26

STMU 28

STMU 30

SWU 0

SWU 1

SWU 2

SWU 3

SWU 4

SWU 5

SWU 8

SWU 9

SWU 60

SWU 61



NIU = Not in use

Table 37. Testing the state transition and unit diagnostics of the SETs in ETS2

GTIC 0 SETsin ETS2 inslot

MCMU 0 WOstate

MCMU 1 WOstate

GTIC 1 SETsin ETS2 inslot

MCMU 0 WOstate

MCMU 1WO state

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8


Commissioning BSC3i



NIU = Not in use

Table 38. Testing the state transition and unit diagnostics of ET16s, part 1

ETC 0MCMU 0 WOstate

MCMU 1 WOstate ETC 1

MCMU 0 WOstate

MCMU 1WO state

ETs in ET16PIU in slot 1

ETs in ET16 PIUin slot 1

0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

DN02199145Issue 5-1 en04/06/2008



Table 38. Testing the state transition and unit diagnostics of ET16s, part 1(cont.)

ETC 0MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2


Commissioning BSC3i


ETC 0MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



NIU = Not in use


ETC 2MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state



0 0

1 1

2 2

3 3

4 4

5 5

6 6

DN02199145Issue 5-1 en04/06/2008




ETC 2MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2


Commissioning BSC3i


ETC 2MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15

DN02199145Issue 5-1 en04/06/2008




ETC 2MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11


Commissioning BSC3i


ETC 2MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

DN02199145Issue 5-1 en04/06/2008




ETC 2MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



NIU = Not in use


ETC 4MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11


Commissioning BSC3i


ETC 4MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

DN02199145Issue 5-1 en04/06/2008




ETC 4MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3


Commissioning BSC3i


ETC 4MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



DN02199145Issue 5-1 en04/06/2008




ETC 4MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12


Commissioning BSC3i


ETC 4MCMU 0 WOstate


MCMU 0 WOstate

MCMU 1WO state

13 13

14 14

15 15



NIU = Not in use


GTIC 0MCMU 0 WOstate

MCMU 1 WOstate GTIC 1

MCMU 0 WOstate

MCMU 1WO state



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15

DN02199145Issue 5-1 en04/06/2008






MCMU 0 WOstate

MCMU 1WO state



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11


Commissioning BSC3i




MCMU 0 WOstate

MCMU 1WO state

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

DN02199145Issue 5-1 en04/06/2008






MCMU 0 WOstate

MCMU 1WO state

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3


Commissioning BSC3i




MCMU 0 WOstate

MCMU 1WO state

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15



0 0

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8

9 9

10 10

11 11

12 12

13 13

14 14

15 15


DN02199145Issue 5-1 en04/06/2008




NIU = Not in use

Table 42. Testing the state transition and unit diagnostics of ETS2s

GTIC 0 ETS2in slot

MCMU 0 WOstate

MCMU 1 WOstate

GTIC 1 ETS2in slot

MCMU 0 WOstate

MCMU 1WO state

1 1

2 2

3 3

4 4

5 5

6 6

7 7

8 8



NIU = Not in use

Table 43. I/O device diagnostics


FDU or UMS

LPTs

MTU

WDUs

VDU




Commissioning BSC3i

Table 44. Checking the ESB switch

Unit Local reset andhotswap

Built-in self test

MCMU 0

MCMU 1

LANU 0

LANU 1

LANU 2

LANU 3

Table 45. Verifying the software versions of the BSC


Print out all SW builds installed on the disk.

Perform verification for each build and compare theprintout with the Delivery Catalogue.



Table 46. Copying additional software


Install the customer specific diskette

Install Change Deliveries

Set the time zone

Restart the system



DN02199145Issue 5-1 en04/06/2008



Table 47. Finishing the commissioning

BSC Commissioned by

Signature:

Name in block letters:

Date:



Commissioning BSC3i

Commissioning BSC3i - yugten.files.wordpress.com · Commissioning BSC3i DN02199145 Issue 5-1 en 04/06/2008 # Nokia Siemens Networks 1 (112) BSC3126-5.0 Nokia BSC3i, Rel. S12, Site

Documents