commissioning check list ru40

8/9/2019 Commissioning Check List RU40

1/40

DN0939536Issue 04A

© Nokia Siemens Networks 1 (40)

WCDMA RAN, Rel. RU40, OperatingDocumentation

Commissioning Checklist for IPA-

RNC

DN0939536Issue 04A

Approval date 2013-04-26


2/40

Commissioning Checklist for IPA-RNC

2 (40) © Nokia Siemens Networks DN0939536Issue 04A

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 forthe use of Nokia Siemens Networks customers only for the purposes of the agreement underwhich the document is submitted, and no part of it may be used, reproduced, modified or

transmitted in any form or means without the prior written permission of Nokia SiemensNetworks. The documentation has been prepared to be used by professional and properlytrained personnel, and the customer assumes full responsibility when using it. Nokia SiemensNetworks 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,or performance of the mentioned hardware or software products are given “as is” and allliability arising in connection with such hardware or software products shall be definedconclusively and finally in a separate agreement between Nokia Siemens Networks and thecustomer. However, Nokia Siemens Networks has made all reasonable efforts to ensure thatthe instructions contained in the document are adequate and free of material errors andomissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks,explain issues which may 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 TOSPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESSINTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THEUSE OF THIS DOCUMENT OR THE INFORMATION 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 trademarkof Nokia Corporation. Siemens is a registered trademark of Siemens AG.

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

Copyright © Nokia Siemens Networks 2013. All rights reserved.


3/40


4/40



11.2

Performing SW update ......................................................................... 38

11.3 Safecopying SW build again ................................................................ 38 11.4 Recording item code and serial number ............................................... 38

12 Commissioning certificate of completion ........................................ 39


5/40


DN0939536Issue 04A


Summary of changes

Changes between issues 04 (RU40, 2013-02-22) and 04A (2013-04-26, RU40)

Interrogating SW build information (6.3)

• Table 16 Boot-SW versions checklist is updated to all supportedplug-in units in RN7.0.

Verifying hardware data consistency with actual configuration (6.5)

• The section title is changed from “Interrogating hardware data”.

Checking the memory size of the CCP1D-A plug-in unit (6.6)• This is a new section.

Changes between issues 03B (2012-10-24, RU30) and 04 (2013-02-22, RU40)

Document structure and contents have been changed in accordancewith the document Commissioning IPA-RNC, issue 17.

Changes between issues 03A and 03B

The cover page and references have been updated.


6/40



1 Commissioning checklist Note

The hardware product names in the checklists are written without thevariant designation unless it is specifically required.

1.1 Using this checklist document

Use this checklist document for recording the success and completion ofcommissioning procedures. Always carry out the procedures asinstructed in the document Commissioning IPA-RNC and mark down thecompleted steps and procedures in this document.

The checklist tables contain references to other product documentswhich may be necessary during each particular procedure. Also, keepthe Commissioning IPA-RNC document available at all times.

The last section of this document, Commissioning Certificate ofCompletion, can be used for acceptance.

1.2 Preparation of commissioning

Commissioning phase / related documents Completed

Check the Installation Certificate of Completionand Site Deficiency Reports. Clear out correctionrequirements for commissioning.

Check the availability of the tools andmeasurement devices that you need forcommissioning. Acquire the needed tools andmeasurement devices.

Commissioning IPA-RNC


7/40


DN0939536Issue 04A



Check the availability of the site documents

delivered online. Acquire the missing sitedocuments.

Hardware Configuration Management in IPA-RNC

Cable Lists for RNC196



Equipment Lists for RNC196



MGW and IPA-RNC, Jumper Settings of the Plug-in Units and Hard Disk Drives

Software Release Binder

Installing the MGW and IPA-RNC

Hardware Revision List for WCDMA IPA-RNC

Managing IPA-RNC Software Configuration

ATM Links and LAN Connections in RNC196



Managing I/O System in IPA-RNC

Diagnostics and Testing in IPA-RNC

Administering Recovery and Unit Working States

in IPA-RNC

Synchronization and Timing in IPA-RNC

Database Administration in IPA-RNC

Change Note installation instruction (deliveredwith each Change Note Set)

IPA-RNC Engineering Description

Table 1. Preparation of commissioning


8/40



2 Safecopying FBEMPTY SW build Commissioning phase / related documents Completed

Make a fallback copy of the SW build and verify it.Make FB build backup copies on OMU hard disksand/or USB stick

Table 2. Safecopying SW build


9/40


DN0939536Issue 04A


3 Inspecting hardware Commissioning phase / related documents Completed

Inspect the door grounding.Check the inter-cabinet cables of the networkelement by comparing them with the cable lists insite documentation. Check all connectors forproper contact (for example, no plugs are loose).





Check the locations of the plug-in units bycomparing them with equipment lists in sitedocumentation.





Check the interchangeability versions of the sub-

racks by comparing them with the equipment listsin site documentation.







10/40




Check the interchangeability versions of the plug-

in units by comparing them with the equipmentlists in site documentation.






Inspect the power supply:

Measure the input voltages to the Cabinet PowerDistributors (CDP80). The voltages must bewithin the range of -40 V ... -57 V DC.

Record all the values in the table Measuredvoltages below. Check that the voltages meet thetolerance requirements.

Check the polarities of the supply lines asinstructed in Installing the MGW and RNC .

Installing the MGW and IPA-RNC

Inspect the hardware material visually. Payattention to mechanical damage and scratches,for example.

Inspect accordance with approved site drawings.

Table 3. Inspecting hardware

Cabinet Voltage (V) Polarity checked

RNAC (UB1)

RNAC (UB2)RNBC (UB1)

RNBC (UB2)

Table 4. Measured voltages


11/40


DN0939536Issue 04A


4 Verifying system startup

4.1 Powering onCommissioning phase / related documents Completed

Power on the cabinet(s).

Check that the LEDs on each unit are eitherblinking green, solid green, or yellow.

Table 5. Powering on

4.2 Logging into the MMI system for the first time


Attach a computer by RJ-45 to the OMU serialport. Log into the MMI system by using the default

administrator user ID and password SYSTEM.

Create a new MMI user profile (ZIAA).

Create a new administrator user ID (ZIAH).

Delete the default administrator user ID

(SYSTEM)(ZIAD).

Table 6. Logging into the MMI system for the first time

The preset IP addresses are changed during integration.


12/40



4.3 Verifying functional units’ start-up


Check that all units have the correct workingstates and that there are no major alarms

Table 7. Verifying functional units’ start-up


13/40


DN0939536Issue 04A


5 Managing network element specificdata

5.1 Changing system name


Change the system name and then verify the newname from the NECONF file.

Table 8. Changing system name

5.2 Setting the calendar date and time


Set the correct date and time (and optionally time

zone) for the network element (ZDCS).

Set the correct NTP server IP address (ZDCM).

NTP IP address:

Table 9. Setting the calendar date and time


14/40



5.3 Enabling CPLD upgrade


Check the status of the CPLD remote upgrade. Ifit is disabled, enable it.

Table 10. Enabling CPLD upgrade


15/40


DN0939536Issue 04A


6 Inspecting SW build and HW data

6.1 Creating Telnet or HTTP connection to OMUCommissioning phase / related documents Completed

Establish a Telnet or HTTP connection to theOMU IP address, port 11111.

Check that the logical files that are used inprinting out alarms are connected to the correct

VPP devices (ZIID).

If not, connect the corresponding logical files to

the correct VPP devices (ZIIS).

Record the devices in table Logical files and VPPdevice connections.

Check that the state of the corresponding VPP

devices is WO-EX (ZIHI).

Check that you can see alarms on the Telnetterminal or the web browser.

Table 11. Creating a Telnet or HTTP connection to OMU

Logical file VPP device Logical file VPP device

ALARMS ALACOMM2

ALACOMM1 ALAQUAL2

ALAQUAL1 ALAPROC2

ALAPROC1 ALAEQUI2

ALAEQUI1 ALAENVI2


16/40



Logical file VPP device Logical file VPP device

ALAENVI1

Table 12. Logical files and VPP device connections

6.2 Inspecting Hardware Management System


Activate the HMEXTE service terminal extension

(ZLP:2,HME).

List the system configuration (Z2DP). Check that

the information on the location of the plug-in unitsis correct.

Make sure that each plug-in unit has a respectiveHMS slave node.

Check that the version number of the HMSsoftware is the same for each plug-in unit thatbelongs to the same node type (master node, Avariant master node, bridge node, slave node, Avariant slave node).

1. Block the following alarms: 1183, 1186,1291, 2689, 3287, and 3290.

2. Ensure that all HMS slave nodes havethe same level of software version.

3. Disable HMS independent switchover.

4. Check the active HMS transmission line.

5. Interrogate the software version of theHMS bridge nodes.

6. Perform a switchover of the HMStransmission line and check that the

transmission line switchover issuccessful.

7. Interrogate the software version of theHMS bridge nodes.

8. Enable HMS independent switchover andcheck that the status of HMSindependent switchover is ENABLED.

9. Interrogate the software version of theHMS master nodes.


17/40


DN0939536Issue 04A



10. Unblock the alarms you blocked in step 1.

Record version numbers to the table HMSsoftware versions.

Check that the version matches the requirementfor software level.


Table 13. Inspecting Hardware Management System

HMS node type All corresponding unitschecked

Version number

HMS master node

HMS A variant masters

HMS bridges

HMS slaves

HMS A variant slaves

Table 14. HMS software versions

6.3 Interrogating SW build information


Verify that the correct software build is on thehard disk and loaded for every unit needed

(ZWQO).

Managing IPA-RNC Software ConfigurationSoftware Release Binder

Default software package:

Package-ID:

Change Note ID:


18/40




Check the software build versions (ZWQB) to find

any erroneous modules.Managing IPA-RNC Software Configuration

Compare the versions with the site-specificdocuments.

Software Configuration Management


Check the version of the flash memory bootpackage of the unit against the SW package. Seethe table Boot-SW versions checklist .

Table 15. Interrogating SW build information

Plug-in unit SW version Plug-in unit SW version

CCP10 CCP18*

CCP1D-A CDSP-DH

MX1G6* MX622*

NI16P1A NI4S1-B

NP2GE-B NP8S1-B

SF10 SF10E

SF20H* refers to the plug-in unit itself or/and its variants

Table 16. Boot-SW versions checklist


19/40


DN0939536Issue 04A


6.4 Interrogating equipment database


Check the state and integrity of the equipmentdatabase and copy database files to disk.


Inquire cabinet information (ZWFI:J:..). Check

that the cabinet information in the databasemeets the physical configuration. Correct any

discrepancies (ZWFJ, ZWFK).


Inquire sub-rack information (ZWFI:C:..). Check

that the sub-rack information in the databasemeets the physical configuration. Correct any

discrepancies (ZWFC, ZWFD).


Inquire plug-in unit information (ZWFI:P:..).Check that the plug-in unit information in thedatabase meets the physical configuration.

Correct any discrepancies (ZWFP, ZWFQ).


Inquire connection information on plug-in unit

ports (ZWFI:S:..). Check that the plug-in unit

port connections in the database meet thephysical configuration. Correct any discrepancies

(ZWFS, ZWFT).





Inquire functional unit information (ZWFI:U:..).

Check that the functional unit information in thedatabase meets the physical configuration.


20/40




Correct any discrepancies (ZWFU, ZWFV).


Table 17. Interrogating equipment database

6.5 Verifying hardware data consistency with actualconfiguration


Interrogate all hardware data of plug-in units

(ZWFL). Verify that the printed data are the same

as on the labels of the plug-in units.

Interrogate all hardware data of subracks (ZWFL).

Verify that the printed data are the same as onthe subrack labels.

Table 18. Verifying hardware data consistency with actual configuration

6.6 Checking the memory size of the CCP1D-A plug-in unit

Commissioning phase/Related documents Completed

Check the memory pool size of the CCP1D-A

plug-in unit (ZDOI). Ensure that the displayed

memory pool size of the CCP1D-A unit is biggerthan 3000 MB.

Table 19. Checking the memory size of the CCP1D-A plug-in unit


21/40


DN0939536Issue 04A


6.7 Inspecting I/O system


Display the I/O devices (ZWFI). Check their

operating states and state transitions (ZIHI).


Diagnose hard disks (ZUDD).

• OMU (WDU-0)

• OMU (WDU-1)


Optional:

1. Change the operating state of an opticaldisk or a USB memory stick to TE-EX

and diagnose it (ZUDD).

2. Display a list of running and queuing tests

(ZUDQ).

3. Display the history of the diagnostic

reports (ZUDH).


Table 20. Inspecting I/O system

6.8 Inspecting unit diagnostics and working states


Print out the working states of the units (ZUSI).

Check that the units are in the WO-EX or SP-EXstate. Check that all units of the network elementare on the list (compare with the equipment list).





Run unit diagnostics and perform change of unitstates.


22/40




Note

There are differinginstructions for 2N redundantunits, N+1 redundant units,SN+ units and non-redundantunits in Commissioning IPA-RNC .

First run diagnostics on SFUs, then continue withMXUs. Then perform diagnostics for all otherunits.

Note

The TBU units (connected to

OMU 0/1) and all unitsconnected to SFU and MXUunits must be tested twice:First when the state of theOMU 0 / SFU 0 / MXU x isWO-EX, then when the stateof the OMU 1 / SFU 1 / MXU1 is WO-EX. MXU x is theMXU connected to the unit tobe tested.


Note

In some cases, one sub-rack slot may house different functional unitsdepending on the configuration of the network element. For detailed informationon the equipping of sub-racks in different configurations, see IPA-RNCEngineering Description, Equipment Lists for RNC196, Equipment Lists forRNC450, and Equipment Lists for RNC2600 .

Table 21. Inspecting unit diagnostics and working states

Functional unit OMU 0 (WO-EX) OMU 1 (WO-EX)

TBU 0

TBU 1

Table 22. TBU 0 and TBU 1 units


23/40


DN0939536Issue 04A


Functional unit MXU 0 (WO-EX) MXU 1 (WO-EX)

SFU 0

SFU 1

Table 23. SFU 0 and SFU 1 units RNAC

Functional unit SFU 0 (WO-EX) SFU 1 (WO-EX)

MXU 0

MXU 1

MXU 2

MXU 3

MXU 4

MXU 5

MXU 6

MXU 7

MXU 8

MXU 9

MXU 10

MXU 11

MXU 12

MXU 13

MXU 14

MXU 15

Table 24. MXU units in RNAC and RNBC


DMCU 0

DMCU 1

DMCU 2

DMCU 3

ICSU 0

OMU 0


24/40




RSMU 0

SFU 0

TBU 0

TBU 1

SWU 0

OMS

Table 25. Functional units in sub-rack 1 (RNAC)


DMCU 4

DMCU 5

DMCU 6

DMCU 7

ICSU 1

ICSU 2

OMU 1

RSMU 1

SFU 1

TBU 0

TBU 1



DMCU 8

DMCU 9

DMCU 10

DMCU 11

DMCU 12

EHU

ICSU 3


25/40


DN0939536Issue 04A



ICSU 4

ICSU 5

ICSU 6

ICSU 7

TBU 0

TBU 1



DMCU 13

DMCU 14

DMCU 15

DMCU 16

DMCU 17

ICSU 8

ICSU 9

ICSU 10

ICSU 11

ICSU 12

ICSU 13

TBU 0

TBU 1



DMCU 18

DMCU 19

DMCU 20

DMCU 21

DMCU 22


26/40




ICSU 14

ICSU 15

ICSU 16

ICSU 17

ICSU 18

ICSU 19

TBU 0

TBU 1

Table 29. Functional units in sub-rack 1 (RNBC)


DMCU 23

DMCU 24

DMCU 25

DMCU 26

DMCU 27

ICSU 20

ICSU 21

ICSU 22

ICSU 23

ICSU 24

ICSU 25

TBU 0

TBU 1

Table 30. Functional units in sub-rack 2 (RNBC)


DMCU 28

DMCU 29

DMCU 30


27/40


28/40



6.9 Inspecting messaging system


Print out the working states of units (ZUSI).

Check that all units are on the list (compare withthe equipment list).

Run messaging system test. In detail, do thefollowing:

• Open a service terminal connectionRS232 to the active OMU or, if notpossible, open a new MMI terminal

session (ZDDS).

Note

The service terminalconnection or the secondMMI terminal connection isused for executing andmonitoring the test. The firstMMI terminal session is usedfor changing the states of theactive SFU and MXU unitsduring the test.

• Load a post office service terminalextension in the active OMU

(ZLP:1,POH).

• List all computing units in the messaging

system (Z1F:::1).

• Start messaging system test (Z1YY).

Monitor the output for a minimum of 5minutes.

• Print the working state SFU unit (ZUSI).

• Print the working states of all MXU units

(ZUSI). Record the index numbers of the

active units in the table Checklist 1 for

active MXU units. Mark the status of theactive MXUs for the active SFU in thetable Checklist 1 for active MXU units.

• Change the state of the working stateSFU unit to SP-EX, (WO-EX -> SP-EX),

(ZUSC). Monitor the output for a minimum

of 5 minutes.

• Print the working states of all MXU units

(ZUSI). Record the index numbers of the


29/40


DN0939536Issue 04A



active units in table Checklist 2 for activeMXU units. Compare with Checklist 1 for

active MXU units that the index numberof each MXU is now different within eachMXU pair. Mark the status of the activeMXU units in the table Checklist 2 foractive MXU units for the active SFU.

• Change the states of working state SFUunits to SP-EX (WO-EX -> SP-EX),

(ZUSC). Monitor the output for a minimum

of 5 minutes. Record the status of theactive MXU units in the table Checklist 2for active MXU units for the new activeSFU unit.

• Stop the test (CTRL + C) and monitor theoutput.

Table 33. Inspecting messaging system

MXU index SFU 0

WO-EX

SFU 1

WO-EX

MXU

MXU

MXU

MXU

MXU

MXU

MXU

MXU

Table 34. Checklist 1 for active MXU units

MXU index SFU 0

WO-EX

SFU 1

WO-EX

MXU

MXU

MXU


30/40



MXU index SFU 0

WO-EX

SFU 1

WO-EX

MXU

MXU

MXU

MXU

MXU

Table 35. Checklist 2 for active MXU units


31/40


32/40




Use ZDYR if you need to control general

synchronization system settings.Synchronization and Timing in IPA-RNC

Check outgoing references (ZDYP). If outgoing

synchronization is not given, set it with the

command ZDYE.


Check system clock operating modes, andchange them if needed.


Table 36. Inspecting synchronization system


33/40


DN0939536Issue 04A


8 Configuring VDS device Commissioning phase / related documents Completed

Define the size and number, and the overwrite,skipping, and compression mode of disk files

(ZIFF).


Connect the desired logical file to the VDS device

(ZIID, ZIIS).


Set alarm limits for the file group (ZIFA).

Set time control for closing the data file of the

VDS device (ZIFT).


Back up the VDS device.


Table 37. Configuring the VDS device


34/40



9 Connecting RNC to standalone RNCOMS


Set up the RUOSTEQX service terminalextension.

Set the OMS southbound IP address for the RNCO&M connection, and check that the connection

works (ZQRS).

If BTS O&M connection is not established, restartBOI (506) and BOR (A0F) processes

Table 38. Connecting RNC to standalone RNC OMS


35/40


DN0939536Issue 04A


10 Verifying OMS system startup

10.1 Verifying OMS BIOS system timeCommissioning phase/ Related documents Completed

Check the time (#date) and change it if needed.

Table 39. Verifying OMS BIOS system time

10.2 Testing TCP/IP connections for OMSCommissioning phase/ Related documents Completed

Ping all IP addresses as specified in Commissioning IPA-RNC.

Table 40. Testing TCP/IP connections for OMS

10.3 Testing OMS software startup


Log into OMS and check that all the services tostart.


36/40




Check that the status returns no disabled

processes.

Table 41. Testing OMS software startup

10.4 Testing Element Manager applications


Install the Application Launcher (EM client).

Start the Application Launcher and log into theElement Manager.

Start and close each Element Managerapplication.

Check OMS Syslog (master-syslog) for errormessages.

Table 42. Testing Element Manager applications

10.5 Testing secure Element Manager MMI window


Start the Application Launcher and log into theElement Manager.

Open the MMI window by double-clicking theicon. Give MML commands to test the MMIwindow application.

Make a switchover to the OMU.

Give MML commands to test the MMI windowapplication.

Log out from the Application Launcher.

Check OMS Syslog for error messages.

Table 43. Testing Element Manager's MMI window


37/40


38/40



11.2 Performing SW update


If the pre-installed package is not compatible withthe network CD level, update the SW.

Table 45. Performing SW update

11.3 Safecopying SW build again


Make a fallback copy of the SW build and verify it.

Make FB build backup copies on OMU hard disksand/or USB stick

Table 46. Safecopying SW build

11.4 Recording item code and serial number

Table 47. Recording item code and serial number


Record the item codes and serial numbers of thenetwork element.


39/40


DN0939536Issue 04A


12 Commissioning certificate ofcompletion CUSTOMER NAME

CONTRACT NO.

NETWORK ELEMENT TYPE

DELIVERY NO.

SITE NAME

SITE NO.

SITE ADDRESS

SOFTWARE RELEASE

SOFTWARE VERSION / BUILD

CHANGE NOTES / CN SETS

COMMISSIONING STAGE COMPLETE / OK (initials)

Preparation of commissioning

Safecopying FBEMPTY SW build

Inspecting hardware

Verifying system startup

Managing network element specific data

Inspecting SW build and HW data

Inspecting synchronization system

Configuring VDS device

Connecting RNC to standalone RNC OMS

Verifying OMS system startup

Finalizing commissioning

COMMENTS / DEFICIENCIES

Nokia Siemens Networks hereby states that the whole of the supplies detailed above have been inspected, tested and, unlessotherwise stated, conform to the specified requirements in the contract or order identified above.

Date: _______________________________________________________________________________________________

Signature of site responsible: ____________________________________________________________________________


40/40


commissioning check list ru40

Documents