Commissioning Checklist of M14 NE.pdf

Commissioning Checklist M14(MSS Server and CDS)

DN0254488Issue 3-0 en

# Nokia Siemens Networks 1 (70)

MSSIHWDOC.20MSC Server

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 2007. All rights reserved.

2 (70) # Nokia Siemens Networks DN0254488Issue 3-0 en

Commissioning Checklist M14 (MSS Server and CDS)

Contents

Contents 3

List of tables 6

List of figures 7

Summary of changes 9

1 Background information 111.1 Purpose 111.2 Scope 111.3 Tasks responsibility 121.4 Procedure 131.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 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 Power supply 192.3.4 Installing the plug-in units in the cartridge 252.3.5 Peripheral units 252.3.6 Hard disk units 252.3.7 Using several CHUs in the MSC 262.3.8 Start-up of the exchange 262.3.9 Inspection of hardware configuration 272.3.10 LAN (Ethernet) switches 272.4 Inspection of authority data, software versions and I/O system 282.4.1 Opening of the first session, verification of the authority data 282.4.2 Inspection of software versions 282.4.3 Inspection of the I/O devices 292.4.4 Output control 302.4.5 Backup devices 302.4.6 MO91 drive 302.5 Inspection of maintenance system 312.5.1 Supervision system 312.5.2 Testing the wired alarms 312.5.3 Testing the external alarms 34



Contents

2.5.4 Fuse fault in supply cable 352.6 Unit diagnostics and working states 352.6.1 State transitions and diagnostics of the OMU 352.6.2 State transitions and diagnostics of the CLS 362.6.3 State transitions and diagnostics of the CLAB units 362.6.4 State transitions and diagnostics of the other duplicated units 362.6.5 State transitions and diagnostics of N+1 redundant units 372.6.6 State transitions and diagnostics of the BDCU 382.6.7 State transitions and diagnostics of the CMM 392.6.8 State transitions and diagnostics of the ET 392.6.9 Testing the spare part plug-in units 392.6.10 Inspecting the FTRB units 402.7 Checking the EMB 402.8 Additional inspections 402.8.1 Clock equipment inspection 402.8.2 Synchronisation unit inspection (optional) 412.9 Finishing 422.10 MSS commissioning certificate of completion 42

3 CDS commissioning work checklist, site folder 453.1 Introduction to commissioning MSS and CDS 453.2 Preparation of commissioning 453.3 Initial inspections at commissioning 463.3.1 Inspection of hardware material 463.3.2 Inspection of jumper settings and the PROM versions 473.3.3 Message bus connections 483.3.4 Power supply 503.3.5 Installing the plug-in units in the cartridge 533.3.6 Peripheral units 533.3.7 Message bus address of processor units 543.3.8 Inspecting the condition of MB cables and MBIF plug-in units 553.3.9 Hard disk units 553.3.10 Start-up of the exchange 563.3.11 Inspection of hardware configuration 563.3.12 Inspecting LAN (Ethernet) switches 573.4 Inspection of authority data, software versions and I/O system 573.4.1 Opening of the first session, verification of the authority data 573.4.2 Inspection of software versions 583.4.3 Inspection of the I/O devices 583.4.4 Output control 593.4.5 Back-up devices 593.4.6 MO91 drive 603.5 Inspection of maintenance system 603.5.1 Testing the wired alarms 603.5.2 Testing the external alarms 633.5.3 Fuse fault in supply cable 643.6 Unit diagnostics and working states 643.6.1 State transitions and diagnostics of the OMU 653.6.2 State transitions and diagnostics of the other duplicated units 653.6.3 State transitions and diagnostics of N+1 redundant units 653.6.4 State transitions and diagnostics of the CMM 663.6.5 State transitions and diagnostics of the ET and CDSU 66



3.6.6 Testing the spare part plug-in units 673.6.7 Inspecting the FTRB units 673.7 Additional inspections 683.7.1 Clock equipment inspection 683.7.2 Synchronisation unit inspection 693.8 Finishing 693.9 CDS commissioning certificate of completion 69



Contents

List of tables



List of figures

Figure 1. Share of responsibilities between sites in the MSS/CDS CommissioningProcess 12

Figure 2. MSS commissioning certificate of completion 43

Figure 3. CDS commissioning certificate of completion 70



List of figures

Summary of changes

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

Changes made between issues 3-0 and 2-2

Updated for M14 release.

Section Checking the EMB added to MSS commissioning checklist.

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 folder and 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 CP5xxplug-in units).

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



Summary of changes

Editorial corrections have been made.


Information on GCS has been updated.



1 Background information

1.1 Purpose

The purpose of this document is to give instructions to the network in theform of checklists for the commissioning of the new MSS or CDS.

The purpose of commissioning is:

. to prepare the MSS/CDS and the site for the integration test

. to ensure that the hardware is tested and that the hardwaredatabase is configured 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 thefollowing chapters. The checklist of the work phases and the Certificate ofCompletion have been enclosed in this document. The checklist isupdated after each work phase. If problems occur, a Failure Report or SiteDeficiency Report is made and the number of the report is updated withregard to the checklist.

1.2 Scope

The document is applied to the commissioning work by Nokia NetworksCustomer Services for Nokia MSS/CDS i-series. It is assumed that theinstallation of the exchange has been completed and the deficienciesnoticed during the installation have been corrected.



Background information

1.3 Tasks responsibility

Figure 1. Share of responsibilities between sites in the MSS/CDSCommissioning Process

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 Procedure

1.4.1 Preparation of commissioning

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

1.4.2 Initial inspections at commissioning

Purpose: checking that both the hardware and the software of theexchange are ready for commissioning.

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

Purpose: verifying the passwords, authority classes and software versionsof the exchange. Checking the states, state changes and back-upspecifications of the I/O devices. Checking that the output control issuitable for the commissioning.

1.4.4 Inspection of maintenance system

Purpose: ensuring that the supervision, alarm and recovery functions ofthe exchange are in order.

The supervision functions are tested in connection with the inspection ofthe alarm system.

The alarm system is tested in connection with the other commissioningtests and therefore the alarm printouts are monitored during the entirecommissioning phase.

The user interface of the recovery is tested in connection with theinspection of the diagnostics and the automatic recovery functions inconnection with the inspection 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.



Background information

1.4.6 Additional inspections

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

1.4.7 Finishing

Purpose: finishing commissioning and getting MSS/CDS and the siteready for integration.

1.5 Related documents

. Commissioning M14.0 (MSCi, Transit MSCi, Compact MSCi, HLRi,MSC Server, CDS)

. Installing the i-Series Network Elements

. Site Specific Documentation (Equipment List, Intercabinet CablesList, Use of GSW, Instructions for Additional Wirings and JumperSettings)

. 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 and CDS

These instructions describe the commissioning of the Nokia DX 200 MSSand Nokia DX 200 CDS. GCS is no longer a separate network element buta functionality of the MSS. The purpose of the commissioning tests is tomake sure that the network element is in the same condition as after thefirst delivery testing (FDT). The same software is used both in thecommissioning and first delivery testing. After commissioning, the networkelement is integrated with the other elements of the network.

The commissioning starts with initial inspections during which thecondition of the hardware and software is checked. After theseinspections, the order of the tests can be determined freely. The testermarks 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 M14 (MSS andCDS) (given separately).



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

14AC 14BC 0 14BC 1 14BC 2




14CC

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


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:

14AC VLRU 0-0 STU 0 CHU 0-0 SD CHU/

*SU

CHU 0HD

VLRU 0-1 STU 1 CHU 0-1

*SU CHU 1HD

LANU 0 LANU 1

CLSU 0,1 CLBU 0.1 CMM 0 CMM 1

OMU 0 OMU 1 OMU MO CMU 0

CMU 1 *SU *SU *SU

*SU *SU *SU *SU

*SU *SU BDCU 0 BDCU 1

14BC 0 VLRU 1-0 VLRU 2-0 CHU 1-0 SD CHU

CHU 0HD

VLRU 1-1 VLRU 2-1 CHU 1-1

Empty CHU 1HD

LANU 2 LANU 3

CLBU 2,3 CLBU 4,5 BDCU 2 *SU

*SU *SU *SU *SU

*SU *SU *SU *SU





*SU *SU *SU *SU

*SU *SU *SU *SU

*SU *SU *SU *SU


CHU 0HD


Empty CHU 1HD

LANU 4 LANU 5

CLBU 6,7 CLBU 8,9 *SU *SU

*SU *SU *SU *SU

*SU *SU *SU *SU

*SU *SU *SU *SU

*SU *SU *SU *SU

*SU *SU *SU *SU


CHU 0HD


Empty CHU 1HD

LANU 6 LANU 7

CLBU10,11

CLBU12,13

*SU *SU

*SU *SU *SU *SU

*SU *SU *SU *SU

*SU *SU *SU *SU

*SU *SU *SU *SU

*SU *SU *SU *SU

14CC ET/STM GSW2KB0

GSW2KB1

ET/STM

LANU 12 LANU 13 CLBU22,23

CLBU24,25

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU

CCSU/PAU




CCSU/PAU

CCSU/PAU

PROM versions (Service terminal command for CPU: WDI;)

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

2.3.3 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 beforethe plug-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:

14AC V 14BC 0 V

14BC 1 V 14BC 2 V

14CC V

Power source unit voltages

PIUs disconnected


PIUs connected





Cartridge/functional unit

–5 V +3.3 V +5 V +12 V –5 V +3.3 V +5 V +12 V

14AC

VLRU 0-0 — —

STU 0 — —

CHU 0-0 — —

SD CHU/

*SU

— —

CHU 0 HD — —

VLRU 0-1 — —

STU 1 — —

CHU 0-1 — —

*SU — —

CHU 1 HD — —

LANU 0 — —

LANU 1 — —

CLSU 0,1 — —

CLBU 0,1 — —

CMM 0 — —

CMM 1 — —

OMU 0 — —

OMU 1 — —

OMU MO — —

CMU 0 — —

CMU 1 — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

BDCU 0 — —




BDCU 1 — —

14BC 0

VLRU 1-0 — —

VLRU 2-0 — —

CHU 1-0 — —

SD CHU — —

CHU 0 HD — —

VLRU 1-1 — —

VLRU 2-1 — —

CHU 1-1 — —

Empty — —

CHU 1 HD — —

LANU 2 — —

LANU 3 — —

CLBU 2,3 — —

CLBU 4,5 — —

BDCU 2 — — — —

*SU — — — —

*SU — —

*SU — —

*SU — — — —

*SU — — — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —





*SU — —

*SU — —

*SU — —

*SU — —

14BC 1

VLRU 3-0 — —

VLRU 4-0 — —

CHU 2-0 — —

SD CHU — —

CHU 0 HD — —

VLRU 3-1 — —

VLRU 4-1 — —

CHU 2-1 — —

Empty — —

CHU 1 HD — —

LANU 6 — —

LANU 7 — — — —

CLBU 10,11 — — — —

CLBU 12,13 — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —




*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

14BC 2

VLRU 5-0 — —

VLRU 6-0 — —

CHU 3-0 — —

SD CHU — —

CHU 0 HD — —

VLRU 5-1 — —

VLRU 6-1 — —

CHU 3-1 — —

Empty — —

CHU 1 HD — —

LANU 6 — —

LANU 7 — — — —

CLBU 10,11 — — — —

CLBU 12,13 — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —





*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

*SU — —

14CC

ET/STM — —

GSW2KB 0 — —

GSW2KB 1 — —

ET/STM — —

LANU 12 — —

LANU 13 — —

CLBU 22,23 — —

CLBU 24,25 — —

CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — — — —

CCSU/PAU — — — —

CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — —




CCSU/PAU — —

CCSU/PAU — —

CCSU/PAU — —

2.3.4 Installing the plug-in units in the cartridge

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

2.3.5 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 VDUand fasten the Rx and Tx pin on the male connector. Type any text on the keyboard andcheck if it appears on the screen.


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


2.3.6 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.7 Using several CHUs in the MSC

You can add new CHU units (unit pairs) in the MSC during its normal use.After creating one or several new CHU pairs, you can define their taskswithin the charging functions in the MSC.

2.3.8 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 allunits receive 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.




2.3.9 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 areavailable.


2.3.10 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 hasno authority are not accessible.


2.4.2 Inspection of software versions


Verify that the correct software package is on the hard disk and that it gets loaded intoall the 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

CHU-2 WDU-0 CHU-3 WDU-0

WDU-1 WDU-1




2.4.4 Output control


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

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

Commissioning (MSS, GCS and CDS)

2.4.5 Backup devices


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


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 Z IBC) 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-basedunits (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 thelists with the configuration.


14AC 14BC 0

14BC 1 14BC 2

14CC

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 textare correct. Check in the alarm printouts that the unit data and the coordinate datacorrespond to the Equipment List. In the 14AC cabinet check if both OMUs are active. Inall other cabinets 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

14AC 14BC 0

14BC 1 14BC 2

14CC

Alarm `2758 POWER SUPPLY ADAPTER FAILURE` tested:

OMU/CLAB OMU/CLAB

x x+1 x x+1

14AC 14BC 0

14BC 1 14BC 2

14CC

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

VLRU 0-0 STU 0 CHU 0-0

SD CHU/

*SU

CHU 0 HD VLRU 0-1

STU 1 CHU 0-1 *SU

CHU 1 HD LANU 0 LANU 1

CLSU 0,1 CLBU 0,1 CMM 0

CMM 1 OMU 0 OMU 1

SD OMU CMU 0 CMU 1

*SU *SU *SU

*SU *SU *SU

*SU *SU *SU

BDCU 0 BDCU 1 VLRU 1-0

VLRU 2-0 CHU 1-0 SD CHU

CHU 0 HD VLRU 1-1 VLRU 2-1

CHU 1-1 Empty CHU 1 HD

LANU 2 LANU 3 CLBU 2,3

CLBU 4,5 BDCU 2 *SU

*SU *SU *SU

*SU *SU *SU

*SU *SU *SU

*SU *SU *SU

*SU *SU *SU

*SU *SU *SU




*SU *SU VLRU 3-0

VLRU 4-0 CHU 2-0 SD CHU

CHU 0 HD VLRU 3-1 VLRU 4-1

CHU 2-1 Empty CHU 1 HD

LANU 4 LANU 5 CLBU 6,7

CLBU 8,9 *SU *SU

*SU *SU *SU

*SU *SU *SU

*SU *SU *SU

*SU *SU *SU

*SU *SU *SU

*SU *SU *SU

*SU *SU


SD CHU CHU 0 HD VLRU 5-1

VLRU 6-1 CHU 3-1 Empty

CHU 1 HD LANU 6 LANU 7

CLBU 10,11 CLBU 12,13

*SU

*SU *SU *SU

*SU *SU *SU

*SU *SU *SU

*SU *SU

ET/STM GSW2KB 0 GSW2KB 1

ET/STM LANU 12 LANU 13

CLBU 22,23

CLBU 24,25

CCSU/PAU

CCSU/PAU CCSU/PAU CCSU/PAU





CCSU/PAU CCSU/PAU

Alarm `2051 POWER FAILURE IN SWITCHING NETWORK` tested:

OMU OMU





0 1 0 1

GSW2KB 0 GSW2KB 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,device type, 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 thesupply cables one by one.



Observations:

2.6 Unit diagnostics and working states


Print out the working states of the units (USI) and check that all units of the exchangeare on 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-24 CLAB-25

2.6.4 State transitions and diagnostics of the other duplicated units


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





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

VLRU 0-0 VLRU 1-0

VLRU 0-1 VLRU 1-1

CMU 0 CMU 1

STU 0 STU 1

OMU 0 OMU 1

CHU 0-0 CHU 0-1

VLRU 2-0 VLRU 3-0

VLRU 4-0 VLRU 2-1

VLRU 3-1 VLRU 4-1

CHU 1-0 CHU 1-1

VLRU 5-0 VLRU 6-0

VLRU 5-1 VLRU 6-1

CHU 2-0 CHU 2-1

CHU 3-0 CHU 3-1

2.6.5 State transitions and diagnostics of N+1 redundant units


Inspect the state transitions and perform diagnostics for signalling units (*SU = CCSU/PAU/SIGU/BSU). Mark the tested units in the following table.


M0 M1 M0 M1

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

xSU-32 xSU-33

xSU-34 xSU-35

xSU-36 xSU-37

xSU-38 xSU-39

xSU-40 xSU-41

xSU-42 xSU-43

xSU-44 xSU-45

xSU-46 xSU-47

xSU-48 xSU-49

xSU-50 xSU-51

xSU-52 xSU-53

xSU-54 xSU-55

xSU-56 xSU-57

xSU-58 xSU-59

xSU-60 xSU-61

xSU-62 xSU-63

xSU-64 xSU-65

xSU-66 xSU-67

xSU-68 xSU-69

xSU-70 xSU-71

xSU-72 xSU-73

xSU-74 xSU-75

2.6.6 State transitions and diagnostics of the BDCU


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






BDCU-0

BDCU-1

BDCU-2

xSU/BDCU (IPCD)

2.6.7 State transitions and diagnostics of the CMM


Perform diagnostics for both CMMs. Mark the tested CMMs in thefollowing table.


diagnostics

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 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.10 Inspecting the FTRB units

Check that the Fan Trays work. A red LED indicates if the FTRB is faulty.

2.7 Checking the EMB


Check the EMB LAN connections and the MAC addresses of the computers with thecommands of the EBSTER service terminal extension.

Commissioning (MSS)

Results:

2.8 Additional inspections

2.8.1 Clock equipment inspection




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


Unit Not redLED

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-20 CLAB-21

CLAB-22 CLAB-23

CLAB-24 CLAB-25

2.8.2 Synchronisation unit inspection (optional)


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,2M3 and 2M4) are in CONNECTED state, synchronisation input 2M1 is in use (USEDINPUT) 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 bothsynchronisation units start to use the synchronisation input with the next highest priority(DRI) after a time delay. After you have disconnected the incoming signal from thesynchronisation input 2M4, wait until both synchronisation units start to use thePLESIOCHRONOUS OPERATION mode (DRI).


Connect the incoming signal to the synchronisation inputs one by one, starting frominput that has the lowest priority (2M4). After you have reconnected the incoming signalto the synchronisation 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 timedelay.


2.9 Finishing


Read the configuration data of the MSS.

Fill in the MSS Commissioning Certificate of Completion.

2.10 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




3 CDS commissioning work checklist, sitefolder

SITE NUMBER: _______________________________

SITE NAME: _______________________________

3.1 Introduction to commissioning MSS and CDS

These instructions describe the commissioning of the Nokia DX 200 MSSand Nokia DX 200 CDS. GCS is no longer a separate network element buta functionality of the MSS. The purpose of the commissioning tests is tomake sure that the network element is in the same condition as after thefirst delivery testing (FDT). The same software is used in thecommissioning and first delivery testing. After commissioning, the networkelement is integrated with the other elements of the network.

The commissioning starts with initial inspections during which thecondition of the hardware and software is checked. After that the order ofthe tests is 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 M14 (MSS andCDS) (given separately).

3.2 Preparation of commissioning


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



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.


3.3 Initial inspections at commissioning

3.3.1 Inspection of hardware material


Inspect the hardware material visually.


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

cartridges and plug-in units.

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

Site Documents; Equipment List.

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

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

Commissioning (MSS 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



3.3.2 Inspection of jumper settings and the PROM versions


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

Note

The wrist strap grounding device has to be used.



Site documents; Equipment List.

Software Release Binder. Program Catalogue.

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

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

ET4C-0 ET4C-1

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

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



















PROM versions (Service terminal command for CPU: WDI;)

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

3.3.3 Message bus connections


MBIF-B in use

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

Note

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

The nominal values are the following:

MD0x..MD15x, MDPx, MWRx , PACKEDx = 33 Ω + (couple of ohms × number ofcabinets)

Note that a couple of ohms means 3 Ω - 6 Ω.

MREx, MRE2x, MACx, MSYx, MAEx = 47 Ω + (couple of ohms × number of cabinets)


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

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 numberof computer cabinets.

Measured resistance:

PIN-name Cable pos MB-0 MB-1

MRE2 a Ω Ω

PACKED Ω Ω

MD0 b Ω Ω

MD1 Ω Ω

MD2 c Ω Ω

MD3 Ω Ω

MD4 d Ω Ω

MD5 Ω Ω

MD6 e Ω Ω

MD7 Ω Ω

MD8 f Ω Ω

MD9 Ω Ω

MD10 g Ω Ω

MD11 Ω Ω

MD12 h Ω Ω

MD13 Ω Ω

MD14 j Ω Ω

MD15 Ω Ω

MSY k Ω Ω

MAC Ω Ω

MAE l Ω Ω

MRE Ω Ω

MWR m Ω Ω





MDP Ω Ω

3.3.4 Power supply


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

Check and measure the power source unit voltage at the back of the cartridge beforethe plug-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

Cartridge/functional unit

–5 V +3.3 V +5 V +12 V –5 V +3.3 V +5 V +12 V

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

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

3.3.5 Installing the plug-in units in the cartridge

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

3.3.6 Peripheral units


Set the required parameters for peripheral devices.


Check the mains outlets used for I/O devices. The protective ground connection has tobe in order and at the same potential as the exchange ground. Measure the voltagebetween the 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 VDUand fasten the Rx and Tx pin on the male connector. Type any text on the keyboard andcheck if it appears on the screen.


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





3.3.7 Message bus address of processor units


Connect the VDU to the upper (J7) service terminal interface of the processor unit.Press the RESET switch of the processor unit. Check that the text `RESET MESSAGEOK` appears on the screen. Check the message bus address and the version of 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 menuis 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-

sage viaMB-0sent andre-

ceived

Mes-


ceived

Resetand de-

bugg-

er on

Mes-


ceived

Mes-

sage viaMB-1 sentand re-

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

CDSU-51 CDSU-52

CDSU-53 CDSU-54

CDSU-55

3.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 theMBIF plug-in units, by making random tests (for example with cartridges),or by making one end-to-end test. However, the correct and completefunctionality of all MBIF units is verified if they are tested unit by unit.

3.3.9 Hard disk units


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)


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

OMU WDU-0

WDU-1




3.3.10 Start-up of the exchange


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

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

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.


3.3.11 Inspection of hardware configuration


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.


3.3.12 Inspecting LAN (Ethernet) switches


Check the functionality of the LED in the front panel.

Check that the HotSwap functionality of the Ethernet switch works.

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

Check the Ethernet switch software versions.

Check that the Ethernet switches have been assigned passwords.

Check that 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 otherLAN device is connected to the Ethernet switch.

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

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

3.4.1 Opening of the first session, verification of the authority 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 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 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.


3.4.2 Inspection of software versions


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 modulescontain flawless data (WQB).



3.4.3 Inspection of the I/O devices


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.


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

VDU/LPT-0 VDU/LPT-8

VDU/LPT-1 VDU/LPT-9







3.4.4 Output control


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


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





3.4.6 MO91 drive


Insert 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 checkthe contents of the MO disks ( IWX).


Unit WO-ID copy to MO91 read from MO91

OMU FDU-0 (MO91)

FDU-1

INDU

3.5 Inspection of maintenance system

3.5.1 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 created alarm groups. Compare the data in thelists with the configuration.


IPCC IWC-0

IWC-1 IWC-2

IWC-3

Test wired alarms. Check that they are printed out and cancelled when the situation isback to normal. Check in the alarm printouts that the alarm number and the alarm textare right. Check in the alarm printouts that the unit data and the coordinates correspondto the Equipment 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, ...).


Alarm `2759 POWER SUPPLY FUSE FAILURE` tested:

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

Alarm `2758 POWER SUPPLY ADAPTER FAILURE` tested:

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

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

OMU/CLAB OMU/CLAB OMU/CLAB

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






















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

CDSU-50 CDSU-51

CDSU-52 CDSU-53

CDSU-54 CDSU-55

3.5.2 Testing the external alarms


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,device type, urgency level, unit data and coordinates.


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 are checked by setting a certain alarm output to `ON` or`OFF` 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.






Alarm Output Alarm Output

AEO00 AEO08

AEO01 AEO09

AEO02 AEO10

AEO03 AEO11

AEO04 AEO12

AEO05 AEO13

AEO06 AEO14

AEO07 AEO15

3.5.3 Fuse fault in supply cable


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



Observations:

3.6 Unit diagnostics and working states


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


Site Documents, Equipment List



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



OMU-0

OMU-1

3.6.2 State transitions and diagnostics of the other duplicated units


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


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

CMM-0 CMM-1

SBUS

3.6.3 State transitions and diagnostics of N+1 redundant units


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




3.6.4 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

3.6.5 State transitions and diagnostics of the ET and CDSU


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..63 ET 64..127

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 CDSU-51

CDSU-52 CDSU-53

CDSU-54 CDSU-55

3.6.6 Testing the spare part plug-in units


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


Results:

3.6.7 Inspecting the FTRB units

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




3.7 Additional inspections

3.7.1 Clock equipment inspection


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


Unit Not redLED


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



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

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 bothsynchronisation units start to use synchronisation input with the next highest priority(DRI) after a time delay. After you have disconnected the incoming signal from thesynchronisation input 2M4, wait until both synchronisation units start to usePLESIOCHRONOUS OPERATION mode (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 signalto the 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.


3.8 Finishing


Read the configuration data of the CDS.

Fill in the CDS Commissioning Certificate of Completion.

3.9 CDS commissioning certificate of completion




Figure 3. CDS 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



Commissioning Checklist of M14 NE.pdf

Documents

Transcript of Commissioning Checklist of M14 NE.pdf