MSS Commisioning Checklist M13 Dn0254488x2x2xen

Commissioning Checklist M13(MSS Server, GCS and CDS)

dn0254488Issue 2-2 en

# Nokia CorporationNokia Proprietary and Confidential

1 (129)

The information in this documentation 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's customers only for the purposes of the agreement under which the documentationis submitted, and no part of it may be reproduced or transmitted in any form or means without theprior written permission of Nokia. The documentation has been prepared to be used byprofessional and properly trained personnel, and the customer assumes full responsibility whenusing it. Nokia welcomes customer comments as part of the process of continuous developmentand improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the documentation areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.

Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or theinformation in it.

This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

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

Copyright © Nokia Corporation 2005. All rights reserved.

2 (129) # Nokia CorporationNokia Proprietary and Confidential


Commissioning Checklist M13 (MSS Server, GCS and CDS)

Contents

Contents 3

List of tables 7

List of figures 8

Summary of changes 9

1 Background information 111.1 Purpose 111.2 Scope 111.3 Tasks responsibility 121.4 Procedure 121.4.1 Preparation of commissioning 131.4.2 Initial inspections at commissioning 131.4.3 Inspection of authority data, SW versions and I/O system 131.4.4 Inspection of maintenance system 131.4.5 Unit diagnostics and working states 131.4.6 Additional inspections 141.4.7 Finishing 141.5 Related documents 141.6 Records 14

2 MSS commissioning work checklist, site folder 152.1 Introduction to commissioning MSS, GCS and CDS 152.2 Preparation of commissioning 162.3 Initial inspections at commissioning 162.3.1 Inspection of hardware material 162.3.2 Inspection of jumper settings and the PROM versions 172.3.3 Message bus connections 202.3.4 Power supply 232.3.5 Installing the plug-in units in the cartridge 282.3.6 Peripheral units 282.3.7 Message bus address of processor units 292.3.8 Inspecting the condition of MB cables and MBIF plug-in units 322.3.9 Hard disk units 322.3.10 Using several CHUs in the MSC 332.3.11 Start-up of the exchange 332.3.12 Inspection of hardware configuration 342.3.13 LAN (Ethernet) switches 342.4 Inspection of authority data, software versions and I/O system 352.4.1 Opening of the first session, verification of the authority data 352.4.2 Inspection of software versions 362.4.3 Inspection of the I/O devices 362.4.4 Output control 372.4.5 Backup devices 372.4.6 MO91 drive 382.5 Inspection of maintenance system 38



3 (129)

Contents

2.5.1 Supervision system 382.5.2 Testing the wired alarms 392.5.3 Testing the external alarms 422.5.4 Fuse fault in supply cable 432.6 Unit diagnostics and working states 442.6.1 State transitions and diagnostics of the OMU 442.6.2 State transitions and diagnostics of the CLS 442.6.3 State transitions and diagnostics of the CLAB units 452.6.4 State transitions and diagnostics of the other duplicated units 462.6.5 State transitions and diagnostics of N+1 redundant units 472.6.6 State transitions and diagnostics of the BDCU 482.6.7 State transitions and diagnostics of the CMM 482.6.8 State transitions and diagnostics of the ET 492.6.9 State transitions and diagnostics of the MB 492.6.10 TCP/IP Interface Connection 502.6.11 Testing the spare part plug-in units 512.6.12 Inspecting the FTRB units 512.7 Additional inspections 512.7.1 Clock equipment inspection 512.7.2 Synchronisation unit inspection 532.7.3 Inspection of TGFP 532.8 Finishing 542.9 MSS commissioning certificate of completion 55

3 GCS commissioning work checklist, site folder 573.1 Introduction to commissioning MSS, GSC, and CDS 573.2 Preparation of commissioning 583.3 Initial inspections at commissioning 583.3.1 Inspection of hardware material 583.3.2 Inspection of jumper settings and the PROM versions 593.3.3 Message bus connections 623.3.4 Power supply 653.3.5 Installing the plug-in units in the cartridge 703.3.6 Peripheral units 703.3.7 Message bus address of processor units 713.3.8 Inspecting the condition of MB cables and MBIF plug-in units 733.3.9 Hard disk units 733.3.10 Using several CHUs in the MSC 743.3.11 Start-up of the exchange 743.3.12 Inspection of hardware configuration 753.3.13 LAN (Ethernet) switches 753.4 Inspection of authority data, software versions and I/O system 763.4.1 Opening of the first session, verification of the authority data 763.4.2 Inspection of software versions 773.4.3 Inspection of the I/O devices 773.4.4 Output control 783.4.5 Back-up devices 793.4.6 MO91 drive 793.5 Inspection of maintenance system 803.5.1 Supervision system 803.5.2 Testing wired alarms 80




3.5.3 Testing the external alarms 833.5.4 Fuse fault in supply cable 843.6 Unit diagnostics and working states 853.6.1 State transitions and diagnostics of the OMU 853.6.2 State transitions and diagnostics of the CLS 853.6.3 State transitions and diagnostics of the CLAB units 863.6.4 State transitions and diagnostics of the other duplicated units 863.6.5 State transitions and diagnostics of N+1 redundant units 873.6.6 State transitions and diagnostics of the BDCU 883.6.7 State transitions and diagnostics of the CMM 883.6.8 State transitions and diagnostics of the ET 893.6.9 State transitions and diagnostics of the MB 893.6.10 TCP/IP Interface Connection 903.6.11 Testing the spare part plug-in units 913.7 Additional inspections 913.7.1 Clock equipment inspection 913.7.2 Synchronisation unit inspection 923.7.3 Inspection of TGFP 923.8 Finishing 933.9 GCS commissioning certificate of completion 94

4 CDS commissioning work checklist, site folder 954.1 Introduction to commissioning MSS, GSC, and CDS 954.2 Preparation of commissioning 964.3 Initial inspections at commissioning 964.3.1 Inspection of hardware material 964.3.2 Inspection of jumper settings and the PROM versions 974.3.3 Message bus connections 1004.3.4 Power supply 1034.3.5 Installing the plug-in units in the cartridge 1074.3.6 Peripheral units 1074.3.7 Message bus address of processor units 1084.3.8 Inspecting the condition of MB cables and MBIF plug-in units 1104.3.9 Hard disk units 1104.3.10 Start-up of the exchange 1104.3.11 Inspection of hardware configuration 1114.3.12 Inspecting LAN (Ethernet) switches 1124.4 Inspection of authority data, software versions and I/O system 1124.4.1 Opening of the first session, verification of the authority data 1124.4.2 Inspection of software versions 1134.4.3 Inspection of the I/O devices 1144.4.4 Output control 1144.4.5 Back-up devices 1154.4.6 MO91 drive 1154.5 Inspection of maintenance system 1154.5.1 Testing the wired alarms 1154.5.2 Testing the external alarms 1204.5.3 Fuse fault in supply cable 1214.6 Unit diagnostics and working states 1224.6.1 State transitions and diagnostics of the OMU 1224.6.2 State transitions and diagnostics of the other duplicated units 122



5 (129)

Contents

4.6.3 State transitions and diagnostics of N+1 redundant units 1234.6.4 State transitions and diagnostics of the CMM 1234.6.5 State transitions and diagnostics of the ET and CDSU 1234.6.6 TCP/IP Interface Connection 1254.6.7 Testing the spare part plug-in units 1254.6.8 Inspecting the FTRB units 1264.7 Additional inspections 1264.7.1 Clock equipment inspection 1264.7.2 Synchronisation unit inspection 1274.7.3 Inspection of TGFP 1284.8 Finishing 1284.9 CDS commissioning certificate of completion 129




List of tables



7 (129)

List of tables

List of figures

Figure 1. Share of responsibilities between sites in the MSCi/HLRi CommissioningProcess 12

Figure 2. MSS commissioning certificate of completion 55

Figure 3. GCS commissioning certificate of completion 94

Figure 4. CDS commissioning certificate of completion 129




Summary of changes

Summary of changes

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

Changes made between issues 2�2 and 2�1

Nominal values in MBIF-A/B have been updated in Table Message busconnections .

MBIF-C has been added to Table Message bus connections .

INDU has been added to Sections GCS commissioning work checklist, site folderand CDS commissioning work checklist, site folder .


Editorial corrections have been made.


The document has been updated for M13:

. Added new CP8 plug-in units (in MSS, also removed old CP5xx plug-inunits).

. Updated list of tasks in each chapter in Section LAN (Ethernet) switches.

Editorial corrections have been made.


Information on GCS has been updated.



9 (129)

Summary of changes




1 Background information

1.1 Purpose

The purpose of this document is to give instructions to the network in the form ofchecklists for the commissioning of the new MSCi/HLRi.

The purpose of commissioning is:

. to prepare the MSCi/HLRi and the site for the integration test

. to ensure that the hardware is tested and that the hardware database isconfigured according to the site specific documentation.

The procedure is further illustrated in a flowchart in Figure 1.

The purpose and the definition of main work phases are given in the followingchapters. The checklist of the work phases and the Certificate of Completion havebeen enclosed in this document. The checklist is updated after each work phase.If problems occur, a Failure Report or Site Deficiency Report is made and thenumber of the report is updated with regard to the checklist.

1.2 Scope

The document is applied to the commissioning work by Nokia NetworksCustomer Services for Nokia MSC/HLR i-series. It is assumed that theinstallation of the exchange has been completed and the deficiencies noticedduring the installation have been corrected.



11 (129)

Background information

1.3 Tasks responsibility

Figure 1. Share of responsibilities between sites in the MSCi/HLRiCommissioning Process

1.4 Procedure

Preparation ofcommissioning

Initial inspections atcommissioning

Inspection of authority data,SW versions and I/O system

Inspection ofmaintenance system

Signing of Certificate ofCompletion

Unit diagnostics andworking states

Additional Inspections

Finishing

COMMISSIONINGGROUP

PERSON RESPONSIBLEFOR THE NOKIA SITE




1.4.1 Preparation of commissioning

Purpose: checking that all documents, tools and devices needed forcommissioning are available and the deficiencies noticed during the installationhave been corrected.

1.4.2 Initial inspections at commissioning

Purpose: checking that both the hardware and the software of the exchange areready for commissioning.

1.4.3 Inspection of authority data, SW versions and I/O system

Purpose: verifying the passwords, authority classes and software versions of theexchange. Checking the states, state changes and back-up specifications of the I/O devices. Checking that the output control is suitable for the commissioning.

1.4.4 Inspection of maintenance system

Purpose: ensuring that the supervision, alarm and recovery functions of theexchange are in order.

The supervision functions are tested in connection with the inspection of thealarm system.

The alarm system is tested in connection with the other commissioning tests andtherefore the alarm printouts are monitored during the entire commissioningphase.

The user interface of the recovery is tested in connection with the inspection ofthe diagnostics and the automatic recovery functions in connection with theinspection of the alarm system.

1.4.5 Unit diagnostics and working states

Purpose: inspecting the state transitions of the units and performing thediagnostics on each unit to ensure the proper condition of the hardware.



13 (129)

Background information

1.4.6 Additional inspections

Purpose: checking the connection between OMU and synchronisation units.Checking that the synchronisation units work correctly in the event of an error.The PCM connection to the distribution frame is also tested.

1.4.7 Finishing

Purpose: finishing commissioning and getting MSCi/HLRi and the site ready forintegration.

1.5 Related documents

. Commissioning Manual (MSCi, Transit MSCi, Compact MSCi, HLRi)

. Installing the i-Series Network Elements

. Site Specific Documentation (Equipment List, Intercabinet Cables List,Use of GSW, Instructions for Additional Wirings and Jumper Settings)

. Software Release Binder

. Jumper Settings of the Plug-in Units in i-Series Network Elements

. Jumper Settings of the Cartridges in i-Series Network Elements

1.6 Records

A list of logs, reports and certificates generated during the work.

. Checklist

. Certificate of Completion

. Site Deficiency Report

. Failure Report (Nokia standard form)




2 MSS commissioning work checklist, sitefolder

SITE NUMBER: _______________________________

SITE NAME: _______________________________

2.1 Introduction to commissioning MSS, GCS and CDS

These instructions describe the commissioning of the Nokia DX 200 MSS, NokiaDX 200 GCS, and Nokia DX 200 CDS. The purpose of the commissioning testsis to make sure that the network element is in the same condition as after the firstdelivery testing (FDT). The same software is used both in the commissioning andfirst delivery testing. After commissioning, the network element is integrated withthe other elements of the network.

The commissioning starts with initial inspections during which the condition ofthe hardware and software is checked. After these inspections, the order of thetests can be determined freely. The tester marks the results in the test logs.

We recommend reading the instructions before starting the tests.

After the tests, you can fill in the Commissioning Checklist M13 (MSS, GCS andCDS) (given separately).



15 (129)

MSS commissioning work checklist, site folder

2.2 Preparation of commissioning

Commissioning phase/related instructions Completed

Check the Installation Certificate of Completion and Site Deficiency Reports. Fillcorrection requirements to start commissioning.

Check the availability of the tools and measurement devices for commissioning. Acquiremissing ones.

Commissioning (MSS, GCS and CDS)

Check the availability of the instructions. Acquire missing ones.


2.3 Initial inspections at commissioning

2.3.1 Inspection of hardware material


Inspect the hardware material visually.


Inspect the interchangeability, versions and number of all cabinets,

cartridges and plug-in units.

Commissioning (MSS, GCS and CDS); Installing the i-series network elements;

Site documents; Equipment List.

Check the location of the cartridges and plug-in units in the exchange.

Ensure that their coordinates match those in the Equipment List in the site document.

Commissioning (MSS, GCS and CDS);

Installing the i-series network elements;

Site documents; Equipment List;

HW Configuration instructions





Inspect all intra-cabinet and inter-cabinet cables one by one according to the cable list.Check the possible contacts of connectors.

Installing the i-series Network Elements

Site specific documentation

Intercabinet cables list

Cables checked:

IPCH IPCF IPCG-0 IPCG-1

IPCG-2

2.3.2 Inspection of jumper settings and the PROM versions


Check the jumper settings and the location of the plug-in units. Check the version ofPROM circuits according to the `Pre-processor PROM-list`. Leave plug-in unitsunplugged.

Note

the wrist strap grounding device has to be used

Commissioning (MSS, GCS, and CDS)

Installing the i-series network elements


Software Release Binder; Program Catalogue;

Jumper settings of the plug-in units in i-series network elements

Jumper Checked:

IPCH MFSU-0 CLBU-26 CLBU-27 CLBU-28

CLBU-29 ET5C-0 MFSU-1 CCSU/

CASU-0

LANU-13 LANU-14 ET5C-1 CCSU/

CASU-1



17 (129)



GSW-0 GSW-1 ET4C-0 CCSU/

CASU-2

CCSU/

CASU-3

CCSU/

CASU-4

CCSU/

CASU-5

CCSU/

CASU-6

CCSU/

CASU-7

CCSU/

CASU-8

CCSU/

CASU-9

IPCF STU-0 CMU-0 CLSU-0 CLSU-1

CLBU-0 STU-1 CMU-1 VLRU-00

VLRU-10 LANU-0 LANU-1 VLRU-01

VLRU-11 CHU-00 SD-0

CHU-0

SD-1

CHU-0

CHU-01 OMU-0 SD-0OMU SD-1OMU

OMU-1 CMM-0 CMM-1 BDCU-0

BDCU-1

IPCG-0 xSU-0 xSU-1 xSU-2 xSU-3

xSU-4 xSU-5 LANU-2 LANU-3

xSU-6 xSU-7 CHU-10 SD-0CHU

SD-1CHU CHU-11 xSU-8 xSU-9

xSU-10 xSU-11 xSU-12 xSU-13

VLRU-20 VLRU-30 VLRU-40 VLRU-21

VLRU-31 VLRU-41






VLRU-50 VLRU-60 VLRU-70 VLRU-51





VLRU-61 VLRU-71






VLRU-80 VLRU-90 VLRU-100

VLRU-81

VLRU-91 VLRU-101

PROM versions (Service terminal command for CPU: 00-MAN>DD:FFC00014,+1B )

CP7xx

CP8xx

CLxTG

CLAB

ET2E

SWCOP

AC25

Check the jumper settings of HWAT (W2).

Check the jumper settings of the cartridges.

Instructions:


Jumper settings of the cartridges in i-series network elements

Cartridge jumper checked:

ET4C CLAC



19 (129)


2.3.3 Message bus connections


MBIF-A/B inuse

Remove TRM9B terminators from the end of the MB. Measure the resistance betweenground (GND) and pins behind the MB terminator.

Note

The MBIF plug-in unit must be pulled out.

The nominal values are the following:

MD0x..MD15x, MDPx, MWRx, PACKEDx = 33 © + (4.0 & + 6.5 © × number of IPCGcabinets)

MREx, MRE2x, MACx, MSYx, MAEx = 47 © + (3 © × number of cabinets)


MBIF-C in use

Remove TRM9C terminators at the end of the MB (on the back side of the track where theMBIF-CR is installed) and pull out all the plug-in units from the cartridge.

Note

ALL MBIF-CRs have to be pulled out of their cartridge.

Measure the resistance between beams A and B of each signal at the front side of thecartridge.

Measurements are taken in the lower part of the MBIF-CR track, pin rows 15�1.

The nominal values are 100 © + the resistance of intercabinet cables on the bus.

Resistance deviations may vary between 100 © and 108 ©, depending on the number ofcomputer cabinets.

Measured resistance:

PIN-name Cable pos MB-0 MB-1





MRE2 A a © ©

MRE2 B © ©

PACKED A © ©

PACKED B © ©

MD0 A b © ©

MD0 B © ©

MD1 A © ©

MD1 B © ©

MD2 A c © ©

MD2 B © ©

MD3 A © ©

MD3 B © ©

MD4 A d © ©

MD4 B © ©

MD5 A © ©

MD5 B © ©

MD6 A e © ©

MD6 B © ©

MD7 A © ©

MD7 B © ©

MD8 A f © ©

MD8 B © ©

MD9 A © ©

MD9 B © ©

MD10 A g © ©



21 (129)



MD10 B © ©

MD11 A © ©

MD11 B © ©

MD12 A h © ©

MD12 B © ©

MD13 A © ©

MD13 B © ©

MD14 A j © ©

MD14 B © ©

MD15 A © ©

MD15 B © ©

MSY A k © ©

MSY B © ©

MAC A © ©

MAC B © ©

MAE A l © ©

MAE B © ©

MRE A © ©

MRE B © ©

MWR A m © ©

MWR B © ©

MDP A © ©

MDP B © ©




2.3.4 Power supply


Measure the power supply voltage at cabinet-specific power supply points.

Check and measure the power source unit voltages at the back of the cartridge before theplug-in units are connected.

Repeat the above step with plug-in units attached.

Record all the values in the next table and check that the voltages meet tolerancerequirements.



Measured voltages:

IPCH V IPCF V

IPCG-0 V IPCG-1 V

IPCG-2 V

Power source unit voltages

PIUs disconnected


PIUs connected

Cartridge/functional unit

�5 V +3.3V

+5 V +12 V �5 V +3.3V

+5 V +12 V

IPCH

MFSU-0 � �

CLBU-26 � �

CLBU-27 � �

CLBU-28 � �

CLBU-29 � �

ET5C-0 � �

MFSU-1 � �

CCSU/CASU-0 � �

LANU-13 � �

LANU-14 � �



23 (129)



ET5C-1 � �

CCSU/CASU-1 � �

GSW-0 � �

GSW-1 � �

ET4C-0 � �

CCSU/CASU-2 � �

CCSU/CASU-3 � �

CCSU/CASU-4 � �

CCSU/CASU-5 � �

CCSU/CASU-6 � �

CCSU/CASU-7 � �

CCSU/CASU-8 � �

CCSU/CASU-9 � �

IPCF

STU-0 � �

CMU-0 � �

CLSU-0 � �

CLSU-1 � �

CLBU-0 � �

STU-1 � �

CMU-1 � �

VLRU-00 � �

VLRU-10 � �

LANU-0 � �

LANU-1 � �

VLRU-01 � �





VLRU-11 � �

CHU-00 � �

SD-0CHU-0 � � � �

SD-1CHU-0 � � � �

CHU-01 � �

OMU-0 � �

SD-0OMU � � � �

SD-1OMU � � � �

OMU-1 � �

CMM-0 � �

CMM-1 � �

BDCU-0 � �

BDCU-1 � �

IPCG-0

xSU-0 � �

xSU-1 � �

xSU-2 � �

xSU-3 � �

xSU-4 � �

xSU-5 � �

LANU-2 � �

LANU-3 � �

xSU-6 � �

xSU-7 � �

CHU-10 � �

SD-0CHU � � � �



25 (129)



SD-1CHU � � � �

CHU-11 � �

xSU-8 � �

xSU-9 � �

xSU-10 � �

xSU-11 � �

xSU-12 � �

xSU-13 � �

VLRU-20 � �

VLRU-30 � �

VLRU-40 � �

VLRU-21 � �

VLRU-31 � �

VLRU-41 � �

IPCG-1

xSU-14 � �

xSU-15 � �

xSU-16 � �

xSU-17 � �

xSU-18 � �

xSU-19 � �

LANU-4 � �

LANU-5 � �

xSU-20 � �

xSU-21 � �

CHU-20 � �





SD-0CHU � � � �

SD-1CHU � � � �

CHU-21 � �

xSU-22 � �

xSU-23 � �

xSU-24 � �

xSU-25 � �

xSU-26 � �

xSU-27 � �

VLRU-50 � �

VLRU-60 � �

VLRU-70 � �

VLRU-51 � �

VLRU-61 � �

VLRU-71 � �

IPCG-2

xSU-28 � �

xSU-29 � �

xSU-30 � �

xSU-31 � �

xSU-32 � �

xSU-33 � �

LANU-6 � �

LANU-7 � �

xSU-34 � �

xSU-35 � �



27 (129)



CHU-30 � �

SD-0CHU � � � �

SD-1CHU � � � �

CHU-31 � �

xSU-36 � �

xSU-37 � �

xSU-38 � �

xSU-39 � �

xSU-40 � �

xSU-41 � �

VLRU-80 � �

VLRU-90 � �

VLRU-100 � �

VLRU-81 � �

VLRU-91 � �

VLRU-101 � �

2.3.5 Installing the plug-in units in the cartridge

Install each plug-in unit in the appropriate position in the cartridges.

2.3.6 Peripheral units


Set the required parameters for peripheral devices.






Check the mains outlets for I/O devices. The protective ground connection must be inorder and at the same potential as the exchange ground. Measure the voltage betweenthe I/O device chassis and the exchange ground.


Measured voltage: ________V

Test the VDUs by connecting the female connector of the interface cable to the VDU andfasten the Rx and Tx pin on the male connector. Type any text on the keyboard and checkif it appears on the screen.


Check the printer settings and perform internal tests on those printers that are equippedwith test functions.


2.3.7 Message bus address of processor units


Connect the VDU to the upper (J7) service terminal interface of the processor unit. Pressthe RESET switch of the processor unit. Check that the text `RESET MESSAGE OKàppears on the screen. Check the message bus address and the version of the BootSoftware (if a FLASH, record version under item 2.3. If FLASH is in use and does notcontain the correct version, download it to CPU.).

Press the DEBUG switch of the processor unit until the following text appears on thescreen: `DEBUGGER READY`. Type the password and check that the debugger menu isshown.

Check the conditions of MBIFs by sending messages via the message bus. Do this forevery computer unit and for both MB-0 and MB-1.

Resetand de-

buggeron

Mes-

sagevia MB-0 sentand re-

ceived

Mes-

sage viaMB-1sent andre-

ceived

Resetandde-

buggeron

Mes-


ceived

Mes-


ceived

CCSU/

CASU-0

CCSU/

CASU-1

CCSU/

CASU-2

CCSU/

CASU-3



29 (129)



CCSU/

CASU-4

CCSU/

CASU-5

CCSU/

CASU-6

CCSU/

CASU-7

CCSU/

CASU-8

CCSU/

CASU-9

MFSU-0 MFSU-1

OMU-0 OMU-1

VLRU-00

VLRU-10

VLRU-01

VLRU-11

CMU-0 CMU-1

STU-0 STU-1

CHU-00 CHU-01

CMM-0 CMM-1

BDCU-0 BDCU-1

VLRU-20

VLRU-30

VLRU-40

VLRU-21

VLRU-31

VLRU-41

CHU-10 CHU-11

xSU-0 xSU-1

xSU-2 xSU-3

xSU-4 xSU-5

xSU-6 xSU-7

xSU-8 xSU-9





xSU-10 xSU-11

xSU-12 xSU-13

VLRU-50

VLRU-60

VLRU-70

VLRU-51

VLRU-61

VLRU-71

CHU-20 CHU-21

xSU-14 xSU-15

xSU-16 xSU-17

xSU-18 xSU-19

xSU-20 xSU-21

xSU-22 xSU-23

xSU-24 xSU-25

xSU-26 xSU-27

VLRU-80

VLRU-90

VLRU-100

VLRU-81

VLRU-91

VLRU-101

CHU-30 CHU-31

xSU-28 xSU-29

xSU-30 xSU-31

xSU-32 xSU-33

xSU-34 xSU-35

xSU-36 xSU-37

xSU-38 xSU-39



31 (129)



xSU-40 xSU-41

2.3.8 Inspecting the condition of MB cables and MBIF plug-in units

The inspection is performed in one of the following ways: by testing all the MBIFplug-in units, by making random tests (for example with cartridges), or bymaking one end-to-end test. However, the correct and complete functionality ofall MBIF units is verified if they are tested unit by unit.

2.3.9 Hard disk units


Check if the disk can be read. Iinitialise it, if necessary. Record disk size and the numberof bad tracks noticed in P-list and G-list (debugger commands: ZMBLP and ZMBLG)


Unit Size initialized read o.k. P-list G-list

OMU WDU-0

WDU-1

CHU-0 WDU-0

WDU-1

CHU-1 WDU-0

WDU-1

CHU-2 WDU-0

WDU-1

CHU-3 WDU-0

WDU-1




2.3.10 Using several CHUs in the MSC

You can add new CHU units (unit pairs) in the MSC during its normal use. Aftercreating one or several new CHU pairs, you can define their tasks within thecharging functions in the MSC.

2.3.11 Start-up of the exchange


Check if the software package is installed in the OMU hard disks, if not, copy it.

If a package directory with the same name is already on the disk, it has to be deletedbefore the new empty package is copied.


Software Release Binder

Restart the entire exchange. Monitor the start-up of the exchange and check that all unitsreceive correct working states. Record recovery times.

Phase Recovery Time

MML Ready

Units to WO-EX

Units to SP-EX

First Alarm to LPT

Check that all units reach the correct working states.




33 (129)


2.3.12 Inspection of hardware configuration


Print the hardware configuration using the following commands:

ZWTI:J;

ZWTI:C;

ZWTI:U;

ZWTI:P;

Check the hardware configuration according to the site documents. Correctdiscrepancies.


Site documents; Equipment List

Check that all functional units are connected. If not, use the WUC command to connectthem.


Check that the TONES (CGR=152) circuit group is created and necessary circuits arepresent.


Check that circuit groups used for CDSU are created and necessary circuits are available.


2.3.13 LAN (Ethernet) switches


Check the functionality of the LED in the frontpanel.

Check that the HotSwap functionality of the Ethernet switch works.

Check that the service terminal interface (RS232 serial interface) works.

Check the software versions of the Ethernet switch.

Check that the Ethernet switches have been assigned passwords.

Check that the Ethernet switch identification (label information) is correct.

Check that each Ethernet switch has been assigned a correct IP-address.

Make sure that the most important settings for the Ethernet switches are correct.





Check that each link is activated with the correct connection when the CPU or anotherLAN device is connected to the Ethernet switch.

Check that the Autonegotiation functionality works. Check that each Ethernet switch porttransmits and receives data.

2.4 Inspection of authority data, software versions andI/O system

2.4.1 Opening of the first session, verification of the authority data


Connect VDU to exchange as an MML terminal and open the first MML-session.

USERNAME <SYSTEM> ;

PASSWORD <SYSTEM> ;


Connect the printer to the exchange and check that the printer interface is in order byprinting out, for example, the states of I/O-devices.


Create a new username with restricted authority. Start a session with the new usernameand verify that the commands for which the username has no authority are notaccessible.


Change the authority class of the terminal interface. Start the session through thechanged terminal interface and verify that the commands for which the username has noauthority are not accessible.




35 (129)


2.4.2 Inspection of software versions


Verify that the correct software package is on the hard disk and that it gets loaded into allthe necessary units (WQO ).


Software Release Binder, Program Catalogue

Software Release:

Software Version/

Build:

Change Notes/

Sets:

Check the version of the software package and verify that the software modules containflawless data (WQB ).



2.4.3 Inspection of the I/O devices


Check the number and the states of OMU I/O devices.


Connect a VDU to all VDU and printer ports in the CPRS-A panel one by one and checkthe states of the I/O ports after every change (ISI ). Open the MML-session to each VDUport. Print out test data to each LPT port.


OMU-0 OMU-1 OMU-0 OMU-1

VDU/LPT-0 VDU/LPT-8

VDU/LPT-1 VDU/LPT-9





VDU/LPT-2 VDU/LPT-10






Check the states of the CHU hard disks.


WO-BU WO-BU

CHU-0 WDU-0 CHU-1 WDU-0

WDU-1 WDU-1


WDU-1 WDU-1

2.4.4 Output control


The permanent output control definitions are not set until the commissioning test is ready.During the commissioning the following logical files have to be connected to the localprinter:

SWITCH1, OPERMA1, TRANSM1, POWER1, EXTERN1, SWITCH2, OPERMA2,TRANSM2, POWER2, EXTERN2, DIAGNOS.


2.4.5 Backup devices


Check the backup device specifications of the output devices and test the functioning ofthe backup system.




37 (129)


2.4.6 MO91 drive


Insert the MO disk to all MO91s (magneto-optical disk). Check that the state of theMO91s changes to WO-ID. Copy files from WDU to FDU (IWY and ZIBC ) and checkthe contents of the MO disks (IWX ).


Unit WO-ID copy to MO91 read from MO91

OMU FDU-0

FDU-1

CHU-0 FDU-0

FDU-1

CHU-1 FDU-0

FDU-1

CHU-2 FDU-0

FDU-1

CHU-3 FDU-0

FDU-1

2.5 Inspection of maintenance system

2.5.1 Supervision system


Check the supervision parameters of the time-slot-based units (YTO ). Check the finalalarm printouts. If necessary, change the supervision interval of the time-slot-based units(YTM ).


Unit type: Supervision Intensity





CDSU

2.5.2 Testing the wired alarms


Check the state alarms. Find out the reason for all alarms.


Check that OMU is in WO-EX state (USI ). Output the alarms with the command WAE foreach cabinet. The command tests all the alarm groups created. Compare data in the listswith the configuration.


IPCH IPCF

IPCG-0 IPCG-1

IPCG-2

Test wired alarms. Check that the they are printed and cancelled when the situation isback to normal. Check in the alarm printouts that the alarm number and the alarm text arecorrect. Check in the alarm printouts that the unit data and the coordinate data correspondto the Equipment List. In the MOMC cabinet check if both OMUs are active. In all othercabinets perform a CLAB switchover. Mark the tested units in the following table (x=0, 2,4, ...).


Alarm `2759 POWER SUPPLY FUSE FAILURE` tested:

OMU/CLAB OMU/CLAB

x x+1 x x+1

IPCH IPCF

IPCG-0 IPCG-1

IPCG-2

Alarm `2758 POWER SUPPLY ADAPTER FAILURE` tested:



39 (129)



OMU/CLAB OMU/CLAB

x x+1 x x+1

IPCH IPCF

IPCG-0 IPCG-1

IPCG-2

Alarm `2757 CARTRIDGE NON-REDUNDANT POWER SUPPLY FAILURE` tested:

OMU/CLAB OMU/CLAB OMU/CLAB

x x+1 x x+1 x x+1

MFSU-0 CLBU-26 CLBU-27

CLBU-28 CLBU-29 ET5C-0

MFSU-1 CCSU/

CASU-0

LANU-13

LANU-14 ET5C-1 CCSU/

CASU-1

GSW-0 GSW-1 ET4C-0

CCSU/

CASU-2

CCSU/

CASU-3

CCSU/

CASU-4

CCSU/

CASU-5

CCSU/

CASU-6

CCSU/

CASU-7

CCSU/

CASU-8

CCSU/

CASU-9

STU-0 CMU-0 CLSU-0

CLSU-1 CLBU-0 STU-1

CMU-1 VLRU-00 VLRU-10

LANU-0 LANU-1 VLRU-01

VLRU-11 CHU-00 SD-0CHU-0

SD-1CHU-0 CHU-01 OMU-0





SD-0OMU SD-1OMU OMU-1

CMM-0 CMM-1 BDCU-0

BDCU-1

xSU-0 xSU-1 xSU-2

xSU-3 xSU-4 xSU-5

LANU-2 LANU-3 xSU-6

xSU-7 CHU-10 SD-0CHU

SD-1CHU CHU-11 xSU-8

xSU-9 xSU-10 xSU-11

xSU-12 xSU-13 VLRU-20


VLRU-31 VLRU-41

xSU-14 xSU-15 xSU-16


LANU-4 LANU-5 xSU-20






VLRU-61 VLRU-71



LANU-6 LANU-7 xSU-34





41 (129)





VLRU-90 VLRU-100

VLRU-81

VLRU-91 VLRU-101

Alarm `2051 POWER FAILURE IN SWITCHING NETWORK` tested:

OMU OMU

0 1 0 1

GSW-0 GSW-1

2.5.3 Testing the external alarms


Output the external alarms (WAP ). Check that they are printed according to the sourcedata. If there are no external alarms specified, you have to create one for testing all theexternal alarm inputs (WAA , WAI ).


Site Documents

Test the external alarm inputs one by one at the cross connection or at the cablingcabinet. Check the following data in the alarm printouts: alarm number, alarm text, devicetype, urgency level, unit data, and coordinates.

Installing the i-series network elements/Connector panels and external cables in i-seriesnetwork elements

Alarm Input Alarm Input Alarm Input

AEI00 AEI08 AEI16

AEI01 AEI09 AEI17

AEI02 AEI10 AEI18

AEI03 AEI11 AEI19

AEI04 AEI12 AEI20

AEI05 AEI13 AEI21





AEI06 AEI14 AEI22

AEI07 AEI15 AEI23

Test the external alarm outputs one by one at the cross connection or at the cablingcabinet. The alarm outputs can be checked by setting a certain alarm output to ON orOFF state using the following commands: ZALU:UPD; and ZALS:x:ON; . The change ofstate has to appear as a change in voltage 0 V � 5 V at the pin.


Alarm Output Alarm Output

AEO00 AEO08

AEO01 AEO09

AEO02 AEO10

AEO03 AEO11

AEO04 AEO12

AEO05 AEO13

AEO06 AEO14

AEO07 AEO15

2.5.4 Fuse fault in supply cable


Test the backup of the power supply of the exchange by removing the fuses of the supplycables one by one.



Observations:



43 (129)



2.6 Unit diagnostics and working states


Print out the working states of the units (USI ) and check that all units of the exchange areon the list (compare with Equipment List).


Site Documents, Equipment List

2.6.1 State transitions and diagnostics of the OMU


Inspect the state transitions and perform diagnostics for both OMUs. Mark the testedOMUs in the following table.


M-0 active M-1 active

OMU-0

OMU-1

2.6.2 State transitions and diagnostics of the CLS


Inspect the state transitions and perform diagnostics for both CLSs. Mark the testedCLSs in the following table.



CLS-0

CLS-1




2.6.3 State transitions and diagnostics of the CLAB units

Commissioning phase/related documents Completed

Inspect the state transitions and perform diagnostics for CLAB units. Mark the testedCLABs in the following table.

CLAB-0 CLAB-1 CLAB-2 CLAB-3

















CLAB-68 CLAB-69



45 (129)


2.6.4 State transitions and diagnostics of the other duplicated units


Inspect the state transitions and perform diagnostics for units VLRU, CMU, STU, CHU,and MFSU. Mark the tested units in the following table.


Unit-0 Unit-1 Unit-0 Unit-1

MFSU-0 MFSU-1

VLRU-00 VLRU-10

VLRU-01 VLRU-11

CMU-0 CMU-1

STU-0 STU-1

CHU-00 CHU-01

VLRU-20 VLRU-30

VLRU-40 VLRU-21

VLRU-31 VLRU-41

CHU-10 CHU-11

VLRU-50 VLRU-60

VLRU-70 VLRU-51

VLRU-61 VLRU-71

CHU-20 CHU-21

VLRU-80 VLRU-90

VLRU-100 VLRU-81

VLRU-91 VLRU-101

CHU-30 CHU-31




2.6.5 State transitions and diagnostics of N+1 redundant units


Inspect the state transitions and perform diagnostics for units xSU, CASU/CCSU, andBSU/SIGU. Mark the tested units in the following table.


M0 M1 M0 M1

CCSU/CASU-0 CCSU/CASU-1





xSU-0 xSU-1

xSU-2 xSU-3

xSU-4 xSU-5

xSU-6 xSU-7

xSU-8 xSU-9

xSU-10 xSU-11

xSU-12 xSU-13

xSU-14 xSU-15

xSU-16 xSU-17

xSU-18 xSU-19

xSU-20 xSU-21

xSU-22 xSU-23

xSU-24 xSU-25

xSU-26 xSU-27

xSU-28 xSU-29

xSU-30 xSU-31



47 (129)



xSU-32 xSU-33

xSU-34 xSU-35

xSU-36 xSU-37

xSU-38 xSU-39

xSU-40 xSU-41

2.6.6 State transitions and diagnostics of the BDCU


Inspect the state transitions and perform diagnostics for BDCU. Mark the tested units inthe following table.



BDCU-0

BDCU-1

BDCU-2

xSU/BDCU (IPCD)

2.6.7 State transitions and diagnostics of the CMM


Inspect the state transitions and perform diagnostics for both CMMs. Mark the testedCMMs in the following table.


diagnostics SPLRT-test

CMM-0

CMM-1




2.6.8 State transitions and diagnostics of the ET


Inspect the state transitions and perform diagnostics for ETs on both markers. Enter thetested units in the following table.


Unit range M0 M1 Unit range M0 M1

ET 0..7 ET 8..15

ET 16..23 ET 24..31

ET 32..63 ET 64..94

2.6.9 State transitions and diagnostics of the MB


Inspect the state transitions and perform diagnostics for the message buses. Mark thetested message bus in the following table.


MB-0 MB-1



49 (129)


2.6.10 TCP/IP Interface Connection

Commissioning phase Completed

1. Create the TCP/IP interface in all the units supporting the Ethernet connection andchange the interface state to ÙP` (command QRN ).

2. Make sure the Ethernet interface works properly by connecting a PC (equipped with aLAN card) or two different computer units together, for example OMU 0 and BDCU 0. Theinterface state in both units has to change from`DOWN` to ÙP` as soon as the connectionhas been made (QRI ).

Note

A crossed Ethernet cable has to be used for testing.

If SIGTRAN is in use, CCSU has to be checked.

If IP Trunk is in use, TGSU has to be checked.

Unit-0 Unit-1

OMU-0

OMU-1

CHU-00

CHU-01

BDCU-0

BDCU-1

CHU-10

CHU-11

CHU-20

CHU-21

CHU-30

CHU-31

STU-0

STU-1




2.6.11 Testing the spare part plug-in units


Equip the exchange with spare plug-in units and perform diagnostics on them as well.


Results:

2.6.12 Inspecting the FTRB units

Check that the Fan Trays (FTRB, not used in Compact MSCi) work. A red LEDindicates if the FTRB is faulty.

2.7 Additional inspections

2.7.1 Clock equipment inspection


Check that the red alarm indicator light is off on the CL2TG or CLAB plug-in units. First, testthe switchover control of the duplicated CL2TGs and CLABs on the front panel switch andthen by removing the power cable from the unit.




51 (129)


Unit NotredLED

Switchover byFCTRLswitch

Switchover byre-

movingpower

Unit No redLED


Switchover byre-

movingpower

CLS-0 CLS-1

CLAB-0 CLAB-1

CLAB-2 CLAB-3

CLAB-4 CLAB-5

CLAB-6 CLAB-7

CLAB-8 CLAB-9

CLAB-10 CLAB-11

CLAB-12 CLAB-13

CLAB-14 CLAB-15

CLAB-16 CLAB-17

CLAB-18 CLAB-19

CLAB-32 CLAB-33

CLAB-34 CLAB-35

CLAB-36 CLAB-37

CLAB-38 CLAB-39

CLAB-40 CLAB-41

CLAB-64 CLAB-65

CLAB-66 CLAB-67

CLAB-68 CLAB-69




2.7.2 Synchronisation unit inspection


Check the connection between the OMU and synchronisation units by issuing the DRIcommand. The command is not likely to result in error messages.


Check that all the four synchronisation ETs are connected to an upper exchange orlooped in the front plate of the ET. Check that all synchronisation inputs (2M1, 2M2, 2M3and 2M4) are in CONNECTED state, synchronisation input 2M1 is in use (USED INPUT)and both synchronisation units use HIERARCHIC OPERATION mode (DRI ).


Disconnect the incoming signal from the synchronisation inputs one by one, starting withthe input that has the highest priority (2M1). After you have disconnected the incomingsignal from the synchronisation inputs 2M1, 2M2 and 2M3, wait until both synchronisationunits start to use the synchronisation input with the next highest priority (DRI ) after a timedelay. After you have disconnected the incoming signal from the synchronisation input2M4, wait until both synchronisation units start to use the PLESIOCHRONOUSOPERATION mode (DRI ).


Connect the incoming signal to the synchronisation inputs one by one, starting from inputthat has the lowest priority (2M4). After you have reconnected the incoming signal to thesynchronisation input 2M4, wait until both synchronisation units start to use theHIERARCHIC OPERATION mode (DRI ). After you have reconnected the incomingsignal to the synchronisation inputs 2M3, 2M2 and 2M1, wait until both synchronisationunits start to use the synchronisation input with the higher priority (DRI ) after a time delay.


2.7.3 Inspection of TGFP


Connect the VDU to the service terminal interface of the TGFP plug-in unit. Check that thetones are set correctly (use service terminal command ZFD ). Correct discrepancies (useservice terminal command ZFA ).

Operating instructions; Software Release Binder



53 (129)


2.8 Finishing


Read the configuration data of the MSS.

Fill in the MSS Commissioning Certificate of Completion.




2.9 MSS commissioning certificate of completion

Figure 2. MSS commissioning certificate of completion

CUSTOMER NAME:

CONTRACT NO.:

DELIVERY NO.:

SITE NAME:

SITE NO.:

SITE ADDRESS:

SOFTWARE RELEASE:

SOFTWARE VERSION/BUILD:

CHANGE NOTES/CN SETS:

STAGE

Preparation of commissioning

COMPLETE/OK(Initials)

COMMENTS/DEFICIENCY

Initial inspections

Inspection of user interfaces & SW versions

Inspection of maintenance system

Finishing

Additional inspections

Nokia Networks hereby states that the whole of supplies detailed above have beeninspected, tested and unless otherwise stated confirm to the specifiedrequirements in the contract or order indentified above.

Date:

Signature of Nokia's site responsible:

Signature of Customer:

(Also Print Name)

Unit diagnostics and working states



55 (129)





3 GCS commissioning work checklist, sitefolder

SITE NUMBER: _______________________________

SITE NAME: _______________________________

3.1 Introduction to commissioning MSS, GSC, andCDS

These instructions describe the commissioning of the Nokia DX 200 MSS, NokiaDX 200 GCS, and Nokia DX 200 CDS. The purpose of the commissioning testsis to make sure that the network element is in the same condition as after the firstdelivery testing (FDT). The same software is used both in the commissioning andfirst delivery testing. After commissioning, the network element is integrated withthe other elements of the network.

The commissioning starts with initial inspections during which the condition ofthe hardware and software is checked. After these inspections, the order of thetests is determined freely. The tester marks the results in the test logs.





57 (129)

GCS commissioning work checklist, site folder




Check the availability of the tools and necessary measurement devices forcommissioning. Acquire missing ones.


Check the availability of the instructions needed. Acquire missing ones.







Inspect the interchangeability, versions and the number of all the cabinets,



Site Documents, Equipment List.

Check the location of cartridges and plug-in units in the exchange.


Commissioning instructions; Installing the i-series network elements;

Site Documents, Equipment List.

Inspect all intra-cabinet and inter-cabinet cables one by one according to the cable lists.Check the probable contact of the connectors.

MSCi/HLRi Installation Manual

Site Specific Documentation

Inter-cabinet cables list

Cables checked:





IPCH IPCF

IPCG-0 IPCG-1


Commissioning phase/related instructions Co-m-pl-et-ed

Check the jumper settings and the location of the plug-in units. Check the version of PROM circuitsaccording to `Pre-processor PROM-list`. Leave plug-in units unplugged.

Note

The wrist strap grounding device has to be used




Software Release Binder. Program Catalogue.


Jumper Checked:

IPCH CLBU-13 CLBU-14 ET5C-0 CCSU-0

LANU-13 LANU-14 ET5C-1 CCSU-1

GSW-0 GSW-1 ET4C-0 CCSU-2

CCSU-3 CCSU-4 CCSU-5 CCSU-6

CCSU-7 CCSU-8 CCSU-9



59 (129)



IPCF STU-0 CMU-0 CLSU-0 CLSU-1

CLBU-0 STU-1 CMU-1 SIGU-0

SIGU-1 LANU-0 LANU-1 SIGU-2

SIGU-3 CHU-00 SD-0

CHU-0

SD-1

CHU-0

CHU-01 OMU-0 SD-0OMU SD-1OMU

OMU-1 CMM-0 CMM-1 BDCU-0

BDCU-1

IPCG-0 SIGU-4 SIGU-5 SIGU-6 SIGU-7

SIGU-8 SIGU-9 LANU-2 LANU-3

SIGU-10 SIGU-11 SD-0

CHU-1

SD-1

CHU-1

CHU-10 SIGU-12 SIGU-13 CHU-11

SIGU-14 SIGU-15 SIGU-16 SIGU-17


SIGU-22 SIGU-23

INDU-0 INDU-1 INDUSD-0

INDUSD-1





IPCG-1 SIGU-24 SIGU-25 SIGU-26 SIGU-27

SIGU-28 SIGU-29 LANU-4 LANU-5

SIGU-30 SIGU-31 CHU-20 SD-0

CHU-2

SD-1

CHU-2

CHU-21 SIGU-32 SIGU-33



SIGU-42 SIGU-43

INDU-0 INDU-1 INDUSD-0

INDUSD-1


CP7xx

CP8xx

CLxTG

CLAB

ET2E

SWCOP

AC25

Check the jumper settings of HWAT (W2)

Check the jumper settings of the cartridges

Instructions:






61 (129)



ET4C CLAC



MBIF-A/B inuse

Remove TRM9B terminators from the end of the MB. Measure the resistance betweenground (GND) and pins behind the MB terminator.

Note

The MBIF plug-in unit has to be pulled out.


MD0x...MD15x, MDPx, MWRx, PACKEDx = 33 © + (4.0 © + 6.5 © × number of IPCGcabinets)



MBIF-C in use





Remove TRM9C terminators from the end of the MB (on the back side of the track where the MBIF-CR isinstalled) and pull out all the plug-in units from the cartridge.

Note


Measure the resistance between beams A and B of each signal at the front side of the cartridge.



Resistance deviations may vary between 100 © and 108 ©, depending on the number of computer cabinets.



MRE2 A a © ©

MRE2 B © ©

PACKED A © ©

PACKED B © ©

MD0 A b © ©

MD0 B © ©

MD1 A © ©

MD1 B © ©

MD2 A c © ©

MD2 B © ©

MD3 A © ©

MD3 B © ©

MD4 A d © ©

MD4 B © ©

MD5 A © ©



63 (129)



MD5 B © ©

MD6 A e © ©

MD6 B © ©

MD7 A © ©

MD7 B © ©

MD8 A f © ©

MD8 B © ©

MD9 A © ©

MD9 B © ©

MD10 A g © ©

MD10 B © ©

MD11 A © ©

MD11 B © ©

MD12 A h © ©

MD12 B © ©

MD13 A © ©

MD13 B © ©

MD14 A j © ©

MD14 B © ©

MD15 A © ©

MD15 B © ©

MSY A k © ©

MSY B © ©

MAC A © ©

MAC B © ©





MAE A l © ©

MAE B © ©

MRE A © ©

MRE B © ©

MWR A m © ©

MWR B © ©

MDP A © ©

MDP B © ©

3.3.4 Power supply



Check and measure the power source unit voltages at the back of the cartridge before theplug-in units are connected.

Repeat the above step with plug-in units connected.

Record all the values in the next table and check that the voltages meet the tolerancerequirements.



Measured voltages:

IPCH V IPCF V

IPCG-0 V IPCG-1 V


PIUs disconnected


PIUs connected


�5 V +3.3V

+5 V +12 V �5 V +3.3V

+5 V +12 V

IPCH



65 (129)



MFSU-0 � �

CLBU-26 � �

CLBU-27 � �

CLBU-28 � �

CLBU-29 � �

ET5C-0 � �

MFSU-1 � �

CCSU-0 � �

LANU-13 � �

LANU-14 � �

ET5C-1 � �

CCSU-1 � �

GSW-0 � �

GSW-1 � �

ET4C-0 � �

CCSU-2 � �

CCSU-3 � �

CCSU-4 � �

CCSU-5 � �

CCSU-6 � �

CCSU-7 � �

CCSU-8 � �

CCSU-9 � �

IPCF

STU-0 � �

CMU-0 � �





CLSU-0 � �

CLSU-1 � �

CLBU-0 � �

STU-1 � �

CMU-1 � �

SIGU-0 � �

SIGU-1 � �

LANU-0 � �

LANU-1 � �

SIGU-2 � �

SIGU-3 � �

CHU-00 � �

SD-0CHU-0 � � � �

SD-1CHU-0 � � � �

CHU-01 � �

OMU-0 � �

SD-0OMU � � � �

SD-1OMU � � � �

OMU-1 � �

CMM-0 � �

CMM-1 � �

BDCU-0 � �

BDCU-1 � �

IPCG-0

SIGU-4 � �

SIGU-5 � �



67 (129)



SIGU-6 � �

SIGU-7 � �

SIGU-8 � �

SIGU-9 � �

LANU-2 � �

LANU-3 � �

SIGU-10 � �

SIGU-11 � �

SD-0CHU-1 � � � �

SD-0CHU-2 � � � �

SD-1CHU-1 � � � �

SD-1CHU-2 � � � �

CHU-10 � �

CHU-20 � �

SIGU-12 � �

SIGU-13 � �

CHU-11 � �

CHU-21 � �

SIGU-14 � �

SIGU-15 � �

SIGU-16 � �

SIGU-17 � �

SIGU-18 � �

SIGU-19 � �





INDU-0

INDU-1

INDU SD-0

INDU SD-1

IPCG-1

SIGU-20 � �

SIGU-21 � �

SIGU-22 � �

SIGU-23 � �

SIGU-24 � �

SIGU-25 � �

LANU-4 � �

LANU-5 � �

SIGU-26 � �

SIGU-27 � �

SD-0CHU-3 � � � �

SD-1CHU-3 � � � �

SIGU-28 � �

SIGU-29 � �

SIGU-30 � �

SIGU-31 � �

SIGU-32 � �

SIGU-33 � �



69 (129)



SIGU-34 � �

SIGU-35 � �

SIGU-36 � �

SIGU-37 � �

SIGU-38 � �

SIGU-39 � �

SIGU-40 � �

SIGU-41 � �

SIGU-42 � �

SIGU-43 � �

INDU-0

INDU-1

INDU SD-0

INDU SD-1


Install each plug-in unit in the appropriate position in the cartridges.









Check the mains outlets used for I/O devices. The protective ground connection has to bein order and at the same potential as the exchange ground. Measure the voltage betweenthe I/O device chassis and the exchange ground.



Test the VDUs by connecting the female connector of the interface cable to the VDU andfasten the Rx and Tx pins on the male connector. Type any text on the keyboard andcheck if it appears on the screen.






Connect the VDU to the upper (J7) service terminal interface of the processor unit. Pressthe RESET switch of the processor unit. Check that the text `RESET MESSAGE OKàppears on the screen. Check the message bus address and the version of Boot Software(If a FLASH, record version under item 2.3., is in use and does not contain the correctversion, download it to CPU.).

Press the DEBUG switch of the processor until the following text appears on the screen:`DEBUGGER READY`. Type the password and check that the debugger menu is shown.

Check the conditions of MBIFs by sending messages via the message bus. Do this forevery computer unit and both MB-0 and MB-1.

Resetand de-

buggeron

Mes-


ceived

Mes-


ceived

Resetandde-

buggeron

Mes-


ceived

Mes-


ceived

CCSU-0 CCSU-1

CCSU-2 CCSU-3

CCSU-4 CCSU-5

CCSU-6 CCSU-7



71 (129)



CCSU-8 CCSU-9

OMU-0 OMU-1

CMU-0 CMU-1

STU-0 STU-1

CHU-00 CHU-01

CMM-0 CMM-1

BDCU-0 BDCU-1

SIGU-0 SIGU-1

SIGU-2 SIGU-3

CHU-10 CHU-20

CHU-11 CHU-21

SIGU-4 SIGU-5

SIGU-6 SIGU-7

SIGU-8 SIGU-9

SIGU-10 SIGU-11

SIGU-12 SIGU-13

SIGU-14 SIGU-15

SIGU-16 SIGU-17

SIGU-18 SIGU-19

SIGU-20 SIGU-21

SIGU-22 SIGU-23

SIGU-24 SIGU-25

SIGU-26 SIGU-27

SIGU-28 SIGU-29

SIGU-30 SIGU-31

SIGU-32 SIGU-33





SIGU-34 SIGU-35

SIGU-36 SIGU-37

SIGU-38 SIGU-39

SIGU-40 SIGU-41

SIGU-42 SIGU-43

INDU-0 INDU-1


The inspection is performed in one of the following ways: by testing all the MBIFplug-in units, by making random tests (for example by cartridges), or by makingone end-to-end test. However, the correct and complete functionality of all MBIFunits is verified if they are tested unit by unit.


Commissioning phase/related instructions Comple-ted

Check if the disk can be read. Initialise it, if necessary. Record the disk size and the number ofbad tracks noticed in P-list and G-list (debugger commands: ZMBLP and ZMBLG)



OMU WDU-0

WDU-1

CHU-0 WDU-0

WDU-1

CHU-1 WDU-0

WDU-1

CHU-2 WDU-0



73 (129)


Commissioning phase/related instructions Comple-ted

WDU-1

INDU WDU-0

WDU-1

3.3.10 Using several CHUs in the MSC

You can add new CHU units (unit pairs) in the MSC during its normal use. Aftercreating one or several new CHU pairs, you can define their tasks within thecharging functions in the MSC.



Check that the software package is installed into the OMU hard disks, if not, copy it.



Software Release Binder

Restart the entire exchange. Monitor the start-up of the exchange and check that all theunits reach the correct working states. Record recovery times.

Phase Recovery Time

MML Ready

Units to WO-EX

Units to SP-EX

First Alarm to LPT

Check that all the units reach the correct working states.







Print the hardware configuration using the following commands:

ZWTI:J;

ZWTI:C;

ZWTI:U;

ZWTI:P;

Check the hardware configuration according to site documents. Correct discrepancies.



Check that all functional units are connected. If not, use theWUC command to connectthem.


Check that the TONES (CGR=152) circuit group is created and necessary circuits areavailable.


Check that the circuit groups used for CDSU are created and necessary circuits are inavailable.


3.3.13 LAN (Ethernet) switches


Check the functionality of the LED in the frontpanel.



Check the Ethernet switch software versions.


Check that Ethernet switch identification (label information) is correct.





75 (129)



Check that each link is activated with the correct connection when the CPU or anotherLAN device is connected to the Ethernet switch.

Check that the Autonegotiation functionality works.

Check that each Ethernet switch port transmits and receives data.




Connect VDU to the exchange as an MML terminal and open the first MML-session.

USERNAME <SYSTEM>

PASSWORD <SYSTEM>


Connect the printer to the exchange and check that the printer interface works properly byprinting out for example the states of I/O-devices.


Create a new username with restricted authority. Start a session with the new usernameand verify that the commands for which the username has no authority for are notaccessible.


Change the authority class of the terminal interface. Start the session through the changedterminal interface and verify that the commands for which the username has no authorityfor are not accessible







Verify that the correct software package is on the hard disks and loaded into all thenecessary units (WQO ).



Software Release:

Software Version/

Build:

Change Notes/

Sets:

Check the version of the software package and verify that the software modules containflawless data (WQB ).





Check the number and states of OMU I/O devices.


Connect a VDU to all VDU and printer ports in the CPRS-A panel one by one and check thestates of the I/O ports after every change (ISI ). Open the MML-session at each VDU port.Print out test data to each LPT port.



VDU/LPT-0 VDU/LPT-8

VDU/LPT-1 VDU/LPT-9



77 (129)









Check the states of CHU hard disks.


WO-BU WO-BU


WDU-1 WDU-1

CHU-2 WDU-0

WDU-1

INDU WDU-0

WDU-1



The permanent output control definitions are not set until after the commissioning test.During the commissioning the following logical files have to be connected to the localprinter:

SWITCH1, OPERMA1, TRANSM1, POWER1, EXTERN1, SWITCH2, OPERMA2,TRANSM2, POWER2, EXTERN2, DIAGNOS





3.4.5 Back-up devices




3.4.6 MO91 drive

Commissioning (MSS, GCS and CDS) Completed

Insert the MO disks to all MO91s (magneto-optical disk). Check that the state of theMO91s changes to WO-ID. Copy files from WDU to FDU (IWY and IBC ) and check thecontents of the MO disks (IWX ).



OMU FDU-0(MO91)

FDU-1(MO91)

CHU-0 FDU-0

FDU-1

CHU-1 FDU-0

FDU-1

CHU-2 FDU-0

FDU-1

INDU FDU-0

FDU-1



79 (129)



3.5.1 Supervision system


Check the supervision parameters of the time-slot-based units (YTO ). Check the eventualalarm print-outs. If necessary change the supervision interval of the time-slot-based units(YTM ).


Unit type: Supervision Intensity

CDSU

3.5.2 Testing wired alarms

Commissioning phase/related instructions Com-pleted



Check that OMU is in WO-EX state (USI ). Output the alarms with the command WAE for eachcabinet. The command also tests all created alarm groups. Compare data in the lists with theconfiguration.


IPCH IPCF

IPCG-0 IPCG-1





Test the wired alarms. Check that they are printed out and cancelled when the situation is back tonormal. Check in the alarm print-outs that the alarm number and the alarm text are correct. Checkin the alarm printouts that unit data and coordinates correspond to the Equipment List. In theMOMC cabinet check if both OMUs are active. In all other cabinets perform a CLAB switchover.Mark the tested units in the following table (x=0, 2, 4, ...).



OMU/CLAB OMU/CLAB

x x+1 x x+1

IPCH IPCF

IPCG-0 IPCG-1


OMU/CLAB OMU/CLAB

x x+1 x x+1

IPCH IPCF

IPCG-0 IPCG-1



x x+1 x x+1 x x+1

MFSU-0 CLBU-26 CLBU-27

CLBU-28 CLBU-29 ET5C-0

MFSU-1 CCSU-0 LANU-13

LANU-14 ET5C-1 CCSU-1

GSW-0 GSW-1 ET4C-0



CCSU-8 CCSU-9



81 (129)



STU-0 CMU-0 CLSU-0

CLSU-1 CLBU-0 STU-1

CMU-1 SIGU-0 SIGU-1

LANU-0 LANU-1 SIGU-2

SIGU-3 CHU-00 SD-0CHU-0

SD-1CHU-0 CHU-01 OMU-0

SD-0OMU SD-1

OMU

OMU-1

CMM-0 CMM-1 BDCU-0

BDCU-1

SIGU-4 SIGU-5 SIGU-6



SIGU-11 SD-0

CHU-1

SD-0CHU-2

SD-1CHU-1 SD-1

CHU-2

CHU-10

CHU-20 SIGU-12 SIGU-13

CHU-11 CHU-21 SIGU-14


SIGU-18 SIGU-19




SIGU-27 SD-0CHU-3

SD-1CHU-3










SIGU-43

INDU-0 INDU-1

INDU SD-0

INDU SD-1

Alarm `2051 POWER FAILURE IN SWITCHING NETWORK` tested:

OMU OMU

0 1 0 1

GSW-0 GSW-1



Output external alarms (WAP ). Check that they are printed out according to the sourcedata. If there are no external alarms specified, you have to create one for testing all theexternal alarm inputs (WAA , WAI ).


Site Documents

Test the external alarm inputs one by one at the cross connection or at the cabling cabinet.Check the following data in the alarm printouts: alarm number, alarm text, device type,urgency level, unit data, and coordinates.



AEI00 AEI08 AEI16

AEI01 AEI09 AEI17



83 (129)



AEI02 AEI10 AEI18

AEI03 AEI11 AEI19

AEI04 AEI12 AEI20

AEI05 AEI13 AEI21

AEI06 AEI14 AEI22

AEI07 AEI15 AEI23

Test the external alarm outputs one by one at the cross connection or at the cablingcabinet. The alarm outputs can be checked by setting a certain alarm output to ÒN` orÒFF` state using the following commands: ZALU:UPD; and ZALS:x:ON; . The change ofstate appears as a change in voltage 0 V � 5 V at the pin.



AEO00 AEO08

AEO01 AEO09

AEO02 AEO10

AEO03 AEO11

AEO04 AEO12

AEO05 AEO13

AEO06 AEO14

AEO07 AEO15



Test the backup power supply of the exchange by removing the fuses of the supply cablesone by one.



Observations:







Print out the working states of the units (USI ) and check that all units of the exchange areon the list (compare with Equipment List).








OMU-0

OMU-1

3.6.2 State transitions and diagnostics of the CLS


Inspect the state transitions and perform diagnostics for both CLSs. Mark the tested CLSsin the following table.




85 (129)




CLS-0

CLS-1

3.6.3 State transitions and diagnostics of the CLAB units

Commissioning phase/related documents Completed

Inspect the state transitions and perform diagnostics for CLAB units. Mark the testedCLABs in the following table.

CLAB-0 CLAB-1



Inspect the state transitions and perform diagnostics for units CMU, CHU, STU, VLRU,SBUS, and INDU. Mark the tested units in the following table.



CMU-0 CMU-1

STU-0 STU-1

CHU-00 CHU-01

CHU-10 CHU-11

CHU-20 CHU-21

INDU-0 INDU-1






Inspect the state transitions and perform diagnostics for units SIGU and xSU (IPCD). Markthe tested units in the following table.


M0 M1 M0 M1

CCSU-0 CCSU-1

CCSU-2 CCSU-3

CCSU-4 CCSU-5

CCSU-6 CCSU-7

CCSU-8 CCSU-9

SIGU-0 SIGU-1

SIGU-2 SIGU-3

SIGU-4 SIGU-5

SIGU-6 SIGU-7

SIGU-8 SIGU-9

SIGU-10 SIGU-11

SIGU-12 SIGU-13

SIGU-14 SIGU-15

SIGU-16 SIGU-17

SIGU-18 SIGU-19

SIGU-20 SIGU-21

SIGU-22 SIGU-23

SIGU-24 SIGU-25

SIGU-26 SIGU-27

SIGU-28 SIGU-29

SIGU-30 SIGU-31



87 (129)



SIGU-32 SIGU-33

SIGU-34 SIGU-35

SIGU-36 SIGU-37

SIGU-38 SIGU-39

3.6.6 State transitions and diagnostics of the BDCU


Inspect the state transitions and perform diagnostics for BDCU. Mark the tested units inthe following table.



BDCU-0

BDCU-1






CMM-0

CMM-1




3.6.8 State transitions and diagnostics of the ET





ET 0..7 ET 8..15

ET 16..23 ET 24..31

ET 32..63 ET 64..94

3.6.9 State transitions and diagnostics of the MB


Inspect the state transitions and perform diagnostics for message buses. Mark the testedmessage bus in the following table.


MB-0 MB-1



89 (129)




1. Create the TCP/IP interface in all the units supporting Ethernet connection and changethe interface state to ÙP` (command QRN ).

2. Make sure the Ethernet interface works properly by connecting a PC (equipped with aLAN card) or two different computer units together, for example OMU 0 and BDCU 0. Theinterface state in both units must change from `DOWN` to ÙP` as soon as the connectionhas been made (QRI ).

Note

A crossed Ethernet cable has to be used for testing.

If SIGTRAN is in use, CCSU has to be checked.

Unit-0 Unit-1

OMU-0

OMU-1

STU-0

STU-1

CHU-00

CHU-01

BDCU-0

BDCU-1

CHU-10

CHU-20

CHU-11

CHU-21

INDU-0

INDU-1








Results:




Check that the red alarm indicator light is off on the CL2TG or CLAB plug-in units. First, test theswitchover control of the duplicated CL2TGs and CLABs with the front panel switch and thenby removing the power cable from the unit.


Unit No redLED

Switch-

over byFCTRLswitch

Switch-

over byre-

movingpower

Unit No redLED

Switch-

over byFCTRLswitch

Switch-

over by re-

movingpower

CLS-0 CLS-1

CLAB-0 CLAB-1



91 (129)






Check that all the four synchronisation ETs are connected to an upper exchange or loopedin the front plate of ET. Check that all the synchronisation inputs (2M1, 2M2, 2M3 and 2M4)are in CONNECTED state, synchronisation input 2M1 is in use (USED INPUT) and thatboth synchronisation units use HIERARCHIC OPERATION mode (DRI ).


Disconnect the incoming signal from the synchronisation inputs one by one, starting withthe input that has the highest priority (2M1). After you have disconnected the incomingsignal from the synchronisation inputs 2M1, 2M2 and 2M3, wait until both synchronisationunits start to use synchronisation input with the next highest priority (DRI ) after a timedelay. After you have disconnected the incoming signal from the synchronisation input2M4, wait until both synchronisation units start to use PLESIOCHRONOUS OPERATIONmode (DRI ).


Reconnect the incoming signal to the synchronisation inputs one by one, starting from theinput that has the lowest priority (2M4). After you have reconnected the incoming signal tothe synchronisation input 2M4, wait until both synchronisation units start to useHIERARCHIC OPERATION mode (DRI ). After you have reconnected the incoming signalto the synchronisation inputs 2M3, 2M2 and 2M1, wait until both synchronisation units startto use synchronisation input with the higher priority (DRI ) after a time delay.




Connect the VDU to the service terminal interface of the TGFP plug in unit. Check that thetones are set correctly (use service terminal command ZFD ). Correct discrepancies (useservice terminal command ZFA ).





3.8 Finishing


Read the configuration data of the GCS.

Fill in the GCS Commissioning Certificate of Completion.



93 (129)


3.9 GCS commissioning certificate of completion

Figure 3. GCS commissioning certificate of completion

CUSTOMER NAME:

CONTRACT NO.:

DELIVERY NO.:

SITE NAME:

SITE NO.:

SITE ADDRESS:

SOFTWARE RELEASE:



STAGE



COMMENTS/DEFICIENCY

Initial inspections



Finishing



Date:



(Also Print Name)





4 CDS commissioning work checklist, sitefolder

SITE NUMBER: _______________________________

SITE NAME: _______________________________

4.1 Introduction to commissioning MSS, GSC, andCDS

These instructions describe the commissioning of the Nokia DX 200 MSS, NokiaDX 200 GSC, and Nokia DX 200 CDS. The purpose of the commissioning testsis to make sure that the network element is in the same condition as after the firstdelivery testing (FDT). The same software is used in the commissioning and firstdelivery testing. After commissioning, the network element is integrated with theother elements of the network.

The commissioning starts with initial inspections during which the condition ofthe hardware and software is checked. After that the order of the tests isdetermined freely. The tester marks the results in the test logs.





95 (129)

CDS commissioning work checklist, site folder




Check the availability of the tools and measurement devices needed for commissioning.Acquire missing ones.


Check the availability of the instructions needed. Acquire missing ones.







Inspect the interchangeability, versions and the number of all the cabinets,



Site Documents; Equipment List.

Check the location of cartridges and plug-in units in the exchange.


Commissioning (MSS, GCS and CDS);

Installing the i-series network elements;


HW Configuration instructions





Inspect all intra-cabinet and inter-cabinet cables one by one according to the cable list.Check the possible contact of the connectors.

MSCi/HLRi Installation Manual

Site Specific Documentation

Inter-cabinet cables list

Cables checked:

IPCC IWC-0 IWC-1

IWC-2 IWC-3



Check the jumper settings and location of the plug-in units. Check the version of PROMcircuits according to `Pre-processor PROM-list`. Leave plug-in units unplugged.

Note

The wrist strap grounding device has to be used.




Software Release Binder. Program Catalogue.


Jumper Checked:

IPCC LANU-0 LANU-1 CLSU-0 CLSU-1

GSU-0

OMU-0 SD-0OMU SD-1OMU OMU-1

GSU-1 GSU-2 CMM-0 CMM-1

GSW-00 GSW-01 GSW-10 GSW-11



97 (129)



ET4C-0 ET4C-1

IWC-0 CDSU-0 CDSU-1 CLBU-32 CLBU-33

CDSU-2 CDSU-3 CDSU-4 CDSU-5

CDSU-6 CDSU-7 CDSU-8 CDSU-9

CDSU-10

CDSU-11

CDSU-12

CDSU-13

IWC-1 CDSU-14

CDSU-15

CLBU-34 CLBU-35

CDSU-16

CDSU-17

CDSU-18

CDSU-19

CDSU-20

CDSU-21

CDSU-22

CDSU-23

CDSU-24

CDSU-25

CDSU-26

CDSU-27

IWC-2 CDSU-28

CDSU-29

CLBU-36 CLBU-37

CDSU-30

CDSU-31

CDSU-32

CDSU-33

CDSU-34

CDSU-35

CDSU-36

CDSU-37

CDSU-38

CDSU-39

CDSU-40

CDSU-41

IWC-3 CDSU-42

CDSU-43

CLBU-38 CLBU-39

CDSU-44

CDSU-45

CDSU-46

CDSU-47

CDSU-48

CDSU-49

CDSU-50

CDSU-51

CDSU-52

CDSU-53

CDSU-54

CDSU-55


CP7xx





CP8xx

CLxTG

CLAB

ET2E

SWCOP

AC25

Check the jumper settings of HWAT (W2)

Check the jumper settings of the cartridges

Instructions:




ET4C CLAC



99 (129)




MBIF-A/B inuse

Remove the TRM9B terminators from the end of the MB. Measure the resistance betweenground (GND) and pins behind the MB terminator.

Note

The MBIF plug-in unit has to be pulled out.


MD0x..MD15x, MDPx, MWRx , PACKEDx = 33 © + (4 © + 6.5 © × number of IPCGcabinets)



MBIF-C in use

Remove the TRM9C terminators from the end of the MB (on the back side of the trackwhere the MBIF-CR is installed) and pull out all the plug-in units from the cartridge.

Note


Measure the resistance between beams A and B of each signal at the front side of thecartridge.



Resistance deviations may vary between 100 © and 108 ©, depending on the number ofcomputer cabinets.







MBIF-A/B inuse

MRE2 A a © ©

MRE2 B © ©

PACKED A © ©

PACKED B © ©

MD0 A b © ©

MD0 B © ©

MD1 A © ©

MD1 B © ©

MD2 A c © ©

MD2 B © ©

MD3 A © ©

MD3 B © ©

MD4 A d © ©

MD4 B © ©

MD5 A © ©

MD5 B © ©

MD6 A e © ©

MD6 B © ©

MD7 A © ©

MD7 B © ©

MD8 A f © ©

MD8 B © ©

MD9 A © ©



101 (129)



MBIF-A/B inuse

MD9 B © ©

MD10 A g © ©

MD10 B © ©

MD11 A © ©

MD11 B © ©

MD12 A h © ©

MD12 B © ©

MD13 A © ©

MD13 B © ©

MD14 A j © ©

MD14 B © ©

MD15 A © ©

MD15 B © ©

MSY A k © ©

MSY B © ©

MAC A © ©

MAC B © ©

MAE A l © ©

MAE B © ©

MRE A © ©

MRE B © ©

MWR A m © ©

MWR B © ©





MBIF-A/B inuse

MDP A © ©

MDP B © ©

4.3.4 Power supply



Check and measure the power source unit voltage at the back of the cartridge before theplug-in units are connected.

Repeat the above step with plug-in units connected.

Record all the values in the next table and check that the voltages meet the tolerancerequirements.



Measured voltages:

IPCC V IWC-0 V

IWC-1 V IWC-2 V

IWC-3 V


PIUs disconnected


PIUs connected


�5 V +3.3V

+5 V +12 V �5 V +3.3V

+5 V +12 V

IPCC

LANU-0 � �

LANU-1 � �

CLSU-0 � �

CLSU-1 � �



103 (129)



GSU-0 �

OMU-0 � �

SD-0OMU � �

SD-1OMU � �

OMU-1 � �

GSU-1 � �

GSU-2 � �

CMM-0 � �

CMM-1 � �

GSW-00 � �

GSW-01 � �

GSW-10 � �

GSW-11 � �

ET4C-0 � �

ET4C-1 � �

IWC-0

CDSU-0 � �

CDSU-1 � �

CLBU-32 � �

CLBU-33 � �

CDSU-2 � �

CDSU-3 � �

CDSU-4 � �

CDSU-5 � �

CDSU-6 � �

CDSU-7 � �





CDSU-8 � �

CDSU-9 � �

CDSU-10 � �

CDSU-11 � �

CDSU-12 � �

CDSU-13 � �

IWC-1

CDSU-14 � �

CDSU-15 � �

CLBU-34 � �

CLBU-35 � �

CDSU-16 � �

CDSU-17 � �

CDSU-18 � �

CDSU-19 � �

CDSU-20 � �

CDSU-21 � �

CDSU-22 � �

CDSU-23 � �

CDSU-24 � �

CDSU-25 � �

CDSU-26 � �

CDSU-27 � �

IWC-2

CDSU-28 � �

CDSU-29 � �



105 (129)



CLBU-36 � �

CLBU-37 � �

CDSU-30 � �

CDSU-31 � �

CDSU-32 � �

CDSU-33 � �

CDSU-34 � �

CDSU-35 � �

CDSU-36 � �

CDSU-37 � �

CDSU-38 � �

CDSU-39 � �

CDSU-40 � �

CDSU-41 � �

IWC-3

CDSU-42 � �

CDSU-43 � �

CLBU-38 � �

CLBU-39 � �

CDSU-44 � �

CDSU-45 � �

CDSU-46 � �

CDSU-47 � �

CDSU-48 � �

CDSU-49 � �

CDSU-50 � �





CDSU-51 � �

CDSU-52 � �

CDSU-53 � �

CDSU-54 � �

CDSU-55 � �


Install the plug-in units in the appropriate positions in the cartridges.





Check the mains outlets used for I/O devices. The protective ground connection has to bein order and at the same potential as the exchange ground. Measure the voltage betweenthe I/O device chassis and the exchange ground.



Test the VDUs by connecting the female connector of the interface cable to the VDU andfasten the Rx and Tx pin on the male connector. Type any text on the keyboard and checkif it appears on the screen.






107 (129)




Connect the VDU to the upper (J7) service terminal interface of the processor unit. Pressthe RESET switch of the processor unit. Check that the text `RESET MESSAGE OKàppears on the screen. Check the message bus address and the version of Boot Software(If a FLASH, record version under item 2.3. If FLASH is in use and does not contain thecorrect version, download it to CPU.).

Press the DEBUG switch of the processor unit until the following text appears on thescreen: `DEBUGGER READY`. Type the password and check that the debugger menu isshown.

Check the conditions of MBIFs by sending messages via the message bus. Do this forevery computer unit and both MB-0 and MB-1.

Resetand de-

buggeron

Mes-


ceived

Mes-


ceived

Resetandde-

bugg-

er on

Mes-


ceived

Mes-


ceived

GSU-0 OMU-0

OMU-1 GSU-1

GSU-2 CMM-0

CMM-1 CDSU-0

CDSU-1 CDSU-2

CDSU-3 CDSU-4

CDSU-5 CDSU-6

CDSU-7 CDSU-8

CDSU-9 CDSU-10

CDSU-11

CDSU-12

CDSU-13

CDSU-14

CDSU-15

CDSU-16





CDSU-17

CDSU-18

CDSU-19

CDSU-20

CDSU-21

CDSU-22

CDSU-23

CDSU-24

CDSU-25

CDSU-26

CDSU-27

CDSU-28

CDSU-29

CDSU-30

CDSU-31

CDSU-32

CDSU-33

CDSU-34

CDSU-35

CDSU-36

CDSU-37

CDSU-38

CDSU-39

CDSU-40

CDSU-41

CDSU-42

CDSU-43

CDSU-44

CDSU-45

CDSU-46

CDSU-47

CDSU-48

CDSU-49

CDSU-50



109 (129)



CDSU-51

CDSU-52

CDSU-53

CDSU-54

CDSU-55


The inspection is performed in one of the following ways: by testing all the MBIFplug-in units, by making random tests (for example with cartridges), or bymaking one end-to-end test. However, the correct and complete functionality ofall MBIF units is verified if they are tested unit by unit.



Check if the disk can be read. Initialise it, if necessary. Record the disk size and thenumber of bad tracks in the P-list and G-list (debugger commands: ZMBLP and ZMBLG)



OMU WDU-0

WDU-1



Check that the software package is installed on the OMU winchester disks, if not, copy it.






Print the hardware configuration using commands:

ZWTI:J;

ZWTI:C;

ZWTI:U;

ZWTI:P;

Check the hardware configuration according to site documents; Correct discrepancies.





Check that the TONES (CGR=152) circuit group is created and necessary circuits areavailable.




Print the hardware configuration using commands:

ZWTI:J;

ZWTI:C;

ZWTI:U;

ZWTI:P;

Check the hardware configuration according to site documents; Correct discrepancies.





Check that TONES (CGR=152) circuit group is created and necessary circuits areavailable.




111 (129)


4.3.12 Inspecting LAN (Ethernet) switches


Check the functionality of the LED in the front panel.



Check the Ethernet switch software versions.


Check that Ethernet switch identification (label information) is correct.



Check that each link is activated with the correct connection when the CPU or other LANdevice is connected to the Ethernet switch.

Check that the Autonegotiation functionality works. Check that each Ethernet switch porttransmits and receives data.




Connect VDU to the exchange as an MML terminal and open the first MML-session.

USERNAME <SYSTEM>

PASSWORD <SYSTEM>


Connect the printer to exchange and check that the printer interface is in order by printingout for example the states of I/O-devices.






Create a new username with restricted authority. Start a session with the new usernameand verify that commands for which the username has no authority are not accessible.


Change the authority class of the terminal interface. Start the session through thechanged terminal interface and verify that commands for which the username has noauthority are not accessible.




Verify that the correct software package is on the hard disks and is loaded into all thenecessary units (WQO ).



Software Release:

Software Version/

Build:

Change Notes/

Sets:

Check the versions of the software package and verify that the software modules containflawless data (WQB ).





113 (129)




Check the number and states of OMU I/O devices.


Connect a VDU to all VDU and printer ports in the CPRS-A panel one by one and checkthe states of the I/O ports after every change (ISI ). Open the MML session at each VDUport. Print out test data to each LPT port.



VDU/LPT-0 VDU/LPT-8

VDU/LPT-1 VDU/LPT-9









The permanent output control definitions are not set until after the commissioning test.During the commissioning the following logical files have to be connected to the localprinter:

SWITCH1, OPERMA1, TRANSM1, POWER1, EXTERN1, SWITCH2, OPERMA2,TRANSM2, POWER2, EXTERN2, DIAGNOS





4.4.5 Back-up devices




4.4.6 MO91 drive


Insert MO disks to all MO91s (magneto-optical disk). Check that the state of the MO91schanges to WO-ID. Copy files from WDU to FDU (IWY and IBC ) and check thecontents of the MO disks (IWX ).



OMU FDU-0(MO91)

FDU-1

INDU


4.5.1 Testing the wired alarms




Check that OMU is in WO-EX state (USI ). Output the alarms with the command WAE foreach cabinet. The command tests all the created alarm groups. Compare the data in thelists with the configuration.




115 (129)



IPCC IWC-0

IWC-1 IWC-2

IWC-3

Test wired alarms. Check that they are printed out and cancelled when the situation is backto normal. Check in the alarm printouts that the alarm number and the alarm text are right.Check in the alarm printouts that the unit data and the coordinates correspond to theEquipment List. In the MOMC cabinet check that both OMUs are active. In all othercabinets perform a CLAB switchover. Mark the tested units in the following table (x=0, 2, 4,...).



OMU/CLAB OMU/CLAB

x x+1 x x+1

MOMC VLRC-0

VLRC-1 VLRC/

GSC-2

VLRC/

GSC-3

GSWC-0

GSWC-1 IWC-1

IWC-2


OMU/CLAB OMU/CLAB

x x+1 x x+1

VLRC-0 VLRC-1

VLRC/

GSC-2

VLRC/

GSC-3

GSWC-0

GSWC-1 IWC-1

IWC-2







x x+1 x x+1 x x+1

OMU-0 OMU-1 GSU-0

GSU-1 GSU-2 CMM-0

CMM-1 CDSU-0 CDSU-1

CDSU-2 CDSU-3 CDSU-4



CDSU-11 CDSU-12

CDSU-13

CDSU-14 CDSU-15

CDSU-16

CDSU-17 CDSU-18

CDSU-19

CDSU-20 CDSU-21

CDSU-22

CDSU-23 CDSU-24

CDSU-25

CDSU-26 CDSU-27

CDSU-28

CDSU-29 CDSU-30

CDSU-31

CDSU-32 CDSU-33

CDSU-34

CDSU-35 CDSU-36

CDSU-37

CDSU-38 CDSU-39

CDSU-40

CDSU-41 CDSU-42

CDSU-43



117 (129)



CDSU-44 CDSU-45

CDSU-46

CDSU-47 CDSU-48

CDSU-49

CDSU-50 CDSU-51

CDSU-52

CDSU-53 CDSU-54

CDSU-55

Alarm `2051 POWER FAILURE IN SWITCHING NETWOR` tested:

OMU OMU

0 1 0 1

GSW-00

GSW-01

GSW-10

GSW-11

Alarm `2755 CARTRIDGE CLOCK FAILURE` tested:

CLAB CLAB

0 1 0 1

CDSU-0 CDSU-1

CDSU-2 CDSU-3

CDSU-4 CDSU-5

CDSU-6 CDSU-7

CDSU-8 CDSU-9

CDSU-10 CDSU-11

CDSU-12 CDSU-13

CDSU-14 CDSU-15





CDSU-16 CDSU-17

CDSU-18 CDSU-19

CDSU-20 CDSU-21

CDSU-22 CDSU-23

CDSU-24 CDSU-25

CDSU-26 CDSU-27

CDSU-28 CDSU-29

CDSU-30 CDSU-31

CDSU-32 CDSU-33

CDSU-34 CDSU-35

CDSU-36 CDSU-37

CDSU-38 CDSU-39

CDSU-40 CDSU-41

CDSU-42 CDSU-43

CDSU-44 CDSU-45

CDSU-46 CDSU-47

CDSU-48 CDSU-49



119 (129)



CDSU-50 CDSU-51

CDSU-52 CDSU-53

CDSU-54 CDSU-55



Output external alarms (WAP ). Check that they are printed out according to the sourcedata. If there are no external alarms specified, you have to create one for testing all theexternal alarm inputs (WAA , WAI ).


Site Documents

Test the external alarm inputs one by one at the cross connection or at the cablingcabinet. Check the following data in the alarm printouts: alarm number, alarm text, devicetype, urgency level, unit data and coordinates.



AEI00 AEI08 AEI16

AEI01 AEI09 AEI17

AEI02 AEI10 AEI18

AEI03 AEI11 AEI19

AEI04 AEI12 AEI20

AEI05 AEI13 AEI21

AEI06 AEI14 AEI22

AEI07 AEI15 AEI23





Test the external alarm outputs one by one at the cross connection or at the cablingcabinet. The alarm outputs are checked by setting a certain alarm output to ÒN` orÒFF` state using the following commands: ZALU:UPD; and ZALS:x:ON; . The changeof state appears as a change in voltage 0 V � 5 V at the pin.



AEO00 AEO08

AEO01 AEO09

AEO02 AEO10

AEO03 AEO11

AEO04 AEO12

AEO05 AEO13

AEO06 AEO14

AEO07 AEO15



Test the backup power supply of the exchange by removing the fuses of the supplycables one by one.



Observations:



121 (129)




Print out the working states of the units (USI ) and check that all the units of the exchangeare on the list (compare with Equipment List).








OMU-0

OMU-1



Inspect the state transitions and perform diagnostics for units CMM and SBUS. Mark thetested units in the following table.



CMM-0 CMM-1

SBUS






Inspect the state transitions and perform diagnostics for units GSU. Mark the tested unitsin the following table.


M0 M1 M0 M1

GSU-0 GSU-1

GSU-2






CMM-0

CMM-1

4.6.5 State transitions and diagnostics of the ET and CDSU





ET 0..63 ET 64..127

CDSU-0 CDSU-1

CDSU-2 CDSU-3



123 (129)



CDSU-4 CDSU-5

CDSU-6 CDSU-7

CDSU-8 CDSU-9

CDSU-10 CDSU-11

CDSU-12 CDSU-13

CDSU-14 CDSU-15

CDSU-16 CDSU-17

CDSU-18 CDSU-19

CDSU-20 CDSU-21

CDSU-22 CDSU-23

CDSU-24 CDSU-25

CDSU-26 CDSU-27

CDSU-28 CDSU-29

CDSU-30 CDSU-31

CDSU-32 CDSU-33

CDSU-34 CDSU-35

CDSU-36 CDSU-37

CDSU-38 CDSU-39

CDSU-40 CDSU-41

CDSU-42 CDSU-43

CDSU-44 CDSU-45

CDSU-46 CDSU-47

CDSU-48 CDSU-49

CDSU-50 CDSU-51

CDSU-52 CDSU-53

CDSU-54 CDSU-55






1. Create the TCP/IP interface in all the units supporting the Ethernet connection andchange the interface state to ÙP` (command QRN ).

2. Make sure the Ethernet interface works properly by connecting a PC (equipped with aLAN card) or two different computer units together, for example OMU 0 and BDCU 0. Theinterface state in both units has to change from `DOWN` to ÙP` as soon as the connectionhas been made (QRI ).

Note

A crossed Ethernet cable should be used for testing

If SIGTRAN is in use, CCSU has to be checked. If Ithe IP Trunk is in use, TGSU has to bechecked.

Unit-0 Unit-1

OMU





Results:



125 (129)



4.6.8 Inspecting the FTRB units

Check that the Fan Trays (FTRB, not used in Compact MSCi) work. A red LEDindicates if the FTRB is faulty.




Check that the red alarm indicator light is off on the CL2TG or CLAB plug-in units. First, testthe switchover control of the duplicated CL2TGs and CLABs with the front panel switchand then by removing the power cable from the unit.


Unit NotredLED


Switchover byre-

movingpower

Unit No redLED


Switchover byre-

movingpower

CLS-0 CLS-1

CLAB-0 CLAB-1

CLAB-2 CLAB-3

CLAB-4 CLAB-5

CLAB-6 CLAB-7

CLAB-8 CLAB-9

CLAB-10 CLAB-11

CLAB-12 CLAB-13





CLAB-14 CLAB-15

CLAB-16 CLAB-17

CLAB-18 CLAB-19

CLAB-20 CLAB-21

CLAB-22 CLAB-23

CLAB-24 CLAB-25

CLAB-26 CLAB-27

CLAB-28 CLAB-29

CLAB-30 CLAB-31

CLAB-32 CLAB-33

CLAB-34 CLAB-35

CLAB-36 CLAB-37

CLAB-38 CLAB-39

CLAB-40 CLAB-41

CLAB-42 CLAB-43





Check that all the four synchronisation ETs are connected to an upper exchange orlooped in the front plate of ET. Check also that all the synchronisation inputs (2M1, 2M2,2M3 and 2M4) are in CONNECTED state, synchronisation input 2M1 is in use (USEDINPUT) and both synchronisation units use HIERARCHIC OPERATION mode (DRI ).




127 (129)



Disconnect the incoming signal from the synchronisation inputs one by one, starting withthe input that has the highest priority (2M1). After you have disconnected the incomingsignal from the synchronisation inputs 2M1, 2M2 and 2M3, wait until both synchronisationunits start to use synchronisation input with the next highest priority (DRI ) after a timedelay. After you have disconnected the incoming signal from the synchronisation input2M4, wait until both synchronisation units start to use PLESIOCHRONOUS OPERATIONmode (DRI ).


Reconnect the incoming signal to the synchronisation inputs one by one, starting withinput that has the lowest priority (2M4). After you have reconnected the incoming signal tothe synchronisation input 2M4, wait until both synchronisation units start to useHIERARCHIC OPERATION mode (DRI ). After you have reconnected the incomingsignal to the synchronisation inputs 2M3, 2M2 and 2M1, wait until both synchronisationunits start to use synchronisation input with the higher priority (DRI ) after a time delay.




Connect the VDU to the service terminal interface of the TGFP plug-in unit. Check that thetones are set correctly (use service terminal command ZFD ). Correct discrepancies (useservice terminal command ZFA ).


4.8 Finishing


Read the configuration data of the MSC.

Fill in the MSC Commissioning Certificate of Completion.




4.9 CDS commissioning certificate of completion

Figure 4. CDS commissioning certificate of completion

CUSTOMER NAME:

CONTRACT NO.:

DELIVERY NO.:

SITE NAME:

SITE NO.:

SITE ADDRESS:

SOFTWARE RELEASE:



STAGE



COMMENTS/DEFICIENCY

Initial inspections



Finishing



Date:



(Also Print Name)




129 (129)
