V 85561974

WCDMA RAN, Rel. RU50, Operating Documentation

Commissioning Checklist for IPA-RNC

DN0939536 Issue 05

Approval date 2014-02-28

Disclaimer Commissioning Checklist for IPA-RNC

2 /40 Copyright © 2013 Nokia Solutions and Networks. All rights reserved.

DN0939536 Issue 05

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Solutions and Networks customers only for the purposes of the agreement under which 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 Solutions and Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and 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 all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary Nokia Solutions and Networks, explain issues which may not be covered by the document. Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Solutions and Networks 2014. All rights reserved.

Nokia Solutions and Networks are continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Solutions and Networks for additional information.

Commissioning Checklist for IPA-RNC Table of Contents

DN0939536 Issue 05

Copyright © 2013 Nokia Solutions and Networks. All rights reserved.

3 /40

Table of Contents This document has 40 pages.

Table of Contents Commissioning Checklist for IPA-RNC


DN0939536 Issue 05

1 Commissioning checklist .................................................................... 7 1.1 Using this checklist document ................................................................ 7 1.2 Preparation of commissioning ................................................................ 7

2 Safecopying FBEMPTY SW build ........................................................ 9

3 Inspecting hardware .......................................................................... 10

4 Verifying system startup ................................................................... 12 4.1 Powering on ......................................................................................... 12 4.2 Logging into the MMI system for the first time ...................................... 12 4.3 Verifying functional units’ start-up ......................................................... 13

5 Managing network element specific data ......................................... 14 5.1 Changing system name........................................................................ 14 5.2 Setting the calendar date and time ....................................................... 14 5.3 Enabling CPLD upgrade....................................................................... 15

6 Inspecting SW build and HW data..................................................... 16 6.1 Creating Telnet or HTTP connection to OMU ....................................... 16 6.2 Inspecting Hardware Management System .......................................... 17 6.3 Interrogating SW build information ....................................................... 18 6.4 Interrogating equipment database ........................................................ 20 6.5 Verifying hardware data consistency with actual configuration ............. 21 6.6 Checking the memory size of the CCP1D-A plug-in unit....................... 21 6.7 Inspecting I/O system ........................................................................... 21 6.8 Inspecting unit diagnostics and working states ..................................... 22 6.9 Inspecting messaging system .............................................................. 28

7 Inspecting synchronization system .................................................. 31

8 Configuring VDS device .................................................................... 33

9 Connecting RNC to standalone RNC OMS ....................................... 34

10 Verifying OMS system startup .......................................................... 35 10.1 Verifying OMS BIOS system time ......................................................... 35 10.2 Testing TCP/IP connections for OMS ................................................... 35 10.3 Testing OMS software startup .............................................................. 35 10.4 Testing Element Manager applications ................................................. 36 10.5 Testing secure Element Manager MMI window .................................... 36

11 Finalizing commissioning ................................................................. 37 11.1 Checking the delivery dependent functionalities ................................... 37 11.2 Performing SW update ......................................................................... 38 11.3 Safecopying SW build again ................................................................ 38 11.4 Recording item code and serial number ............................................... 38

Commissioning Checklist for IPA-RNC Table of Contents

DN0939536 Issue 05


5 /40

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

Commissioning Checklist for IPA-RNC


DN0939536 Issue 05

Summary of changes

Changes between issues 04A (2013-04-26, RU40) and 05 (RU50, 2014-02-28) • RNC196 and RNC450 related documents reference are removed.

• CCP10, NI16P1A, NI4S1-B, SF10, SF10E are RNC196/450 specific and removed from Table 15. Interrogating SW build information.

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 supported

plug-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 accordance with the document Commissioning IPA-RNC, issue 17.

Changes between issues 03A and 03B The cover page and references have been updated.

Commissioning Checklist for IPA-RNC Commissioning checklist

DN0939536 Issue 05


7 /40

1 Commissioning checklist

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

1.1 Using this checklist document

Use this checklist document for recording the success and completion of commissioning procedures. Always carry out the procedures as instructed in the document Commissioning IPA-RNC and mark down the completed steps and procedures in this document.

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

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

1.2 Preparation of commissioning

Commissioning phase / related documents Completed

Check the Installation Certificate of Completion and Site Deficiency Reports. Clear out correction requirements for commissioning.

Check the availability of the tools and measurement devices that you need for commissioning. Acquire the needed tools and measurement devices.

Commissioning IPA-RNC

Commissioning checklist Commissioning Checklist for IPA-RNC


DN0939536 Issue 05


Check the availability of the hardware documents in Operating Documentation delivered online. Acquire the missing hardware documents.

Hardware Configuration Management in IPA-RNC

Cable Lists for RNC2600

Equipment Lists for RNC2600

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 RNC2600

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 (delivered with each Change Note Set)

IPA-RNC Engineering Description

Table 1. Preparation of commissioning

Commissioning Checklist for IPA-RNC Safecopying FBEMPTY SW build

DN0939536 Issue 05


9 /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 disks and/or USB stick

Table 2. Safecopying SW build

Inspecting hardware Commissioning Checklist for IPA-RNC


DN0939536 Issue 05

3 Inspecting hardware Commissioning phase / related documents Completed

Inspect the door grounding.

Check the inter-cabinet cables of the network element by comparing them with the cable lists in Operating Documentation. Check all connectors for proper contact (for example, no plugs are loose).



Check the locations of the plug-in units by comparing them with equipment lists in Operating Documentation.



Check the interchangeability versions of the sub-racks by comparing them with the equipment lists in Operating Documentation.




Check the interchangeability versions of the plug-in units by comparing them with the equipment lists in Operating Documentation.




Commissioning Checklist for IPA-RNC Inspecting hardware

DN0939536 Issue 05


11 /40


Inspect the power supply:

Measure the input voltages to the Cabinet Power Distributors (CDP80). The voltages must be within the range of -40 V ... -57 V DC.

Record all the values in the table Measured voltages below. Check that the voltages meet the tolerance requirements.

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

Installing the MGW and IPA-RNC

Inspect the hardware material visually. Pay attention 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

Verifying system startup Commissioning Checklist for IPA-RNC


DN0939536 Issue 05

4 Verifying system startup 4.1 Powering on


Power on the cabinet(s).

Check that the LEDs on each unit are either blinking 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 serial port. 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.

Commissioning Checklist for IPA-RNC Verifying system startup

DN0939536 Issue 05


13 /40

4.3 Verifying functional units’ start-up


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

Table 7. Verifying functional units’ start-up

Managing network element specific data Commissioning Checklist for IPA-RNC


DN0939536 Issue 05

5 Managing network element specific data

5.1 Changing system name


Change the system name and then verify the new name 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

Commissioning Checklist for IPA-RNC Managing network element specific data

DN0939536 Issue 05


15 /40

5.3 Enabling CPLD upgrade


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

Table 10. Enabling CPLD upgrade

Inspecting SW build and HW data Commissioning Checklist for IPA-RNC


DN0939536 Issue 05

6 Inspecting SW build and HW data 6.1 Creating Telnet or HTTP connection to OMU


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

Check that the logical files that are used in printing 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 VPP device connections.

Check that the state of the corresponding VPP devices is WO-EX (ZIHI).

Check that you can see alarms on the Telnet terminal 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

Commissioning Checklist for IPA-RNC Inspecting SW build and HW data

DN0939536 Issue 05


17 /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 units is correct.

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

Check that the version number of the HMS software is the same for each plug-in unit that belongs to the same node type (master node, A variant master node, bridge node, slave node, A variant slave node).

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

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

3. Disable HMS independent switchover.

4. Check the active HMS transmission line.

5. Interrogate the software version of the HMS bridge nodes.

6. Perform a switchover of the HMS transmission line and check that the transmission line switchover is successful.

7. Interrogate the software version of the HMS bridge nodes.

8. Enable HMS independent switchover and check that the status of HMS independent switchover is ENABLED.

9. Interrogate the software version of the HMS master nodes.

10. Unblock the alarms you blocked in step 1.



DN0939536 Issue 05


Record version numbers to the table HMS software versions.

Check that the version matches the requirement for software level.


Table 13. Inspecting Hardware Management System

HMS node type All corresponding units

checked 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 the hard disk and loaded for every unit needed (ZWQO).



Default software package:

Package-ID:

Change Note ID:


DN0939536 Issue 05


19 /40


Check the software build versions (ZWQB) to find any erroneous modules.


Compare the versions with the hardware specific documents.

Software Configuration Management


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

Table 15. Interrogating SW build information

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

CCP1D-A CCP18*

SF20H CDSP-DH

MX1G6* MX622*

NP2GE-B NP8S1-B * refers to the plug-in unit itself or/and its variants

Table 16. Boot-SW versions checklist



DN0939536 Issue 05

6.4 Interrogating equipment database


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


Inquire cabinet information (ZWFI:J:..). Check that the cabinet information in the database meets the physical configuration. Correct any discrepancies (ZWFJ, ZWFK).


Inquire sub-rack information (ZWFI:C:..). Check that the sub-rack information in the database meets the physical configuration. Correct any discrepancies (ZWFC, ZWFD).


Inquire plug-in unit information (ZWFI:P:..). Check that the plug-in unit information in the database 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 the physical configuration. Correct any discrepancies (ZWFS, ZWFT).


ATM Links and LAN Connections in RNC2600

Inquire functional unit information (ZWFI:U:..). Check that the functional unit information in the database meets the physical configuration.

Correct any discrepancies (ZWFU, ZWFV).



DN0939536 Issue 05


21 /40

Table 17. Interrogating equipment database

6.5 Verifying hardware data consistency with actual configuration


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 on the 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 bigger than 3000 MB.

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

6.7 Inspecting I/O system


Display the I/O devices (ZWFI). Check their operating states and state transitions (ZIHI).




DN0939536 Issue 05


Diagnose hard disks (ZUDD).

• OMU (WDU-0)

• OMU (WDU-1)


Optional:

1. Change the operating state of an optical disk 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-EX state. Check that all units of the network element are on the list (compare with the equipment list).



Run unit diagnostics and perform change of unit states.

Note

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

First run diagnostics on SFUs, then continue with MXUs. Then perform diagnostics for all other units.


DN0939536 Issue 05


23 /40


Note

The TBU units (connected to OMU 0/1) and all units connected to SFU and MXU units must be tested twice: First when the state of the OMU 0 / SFU 0 / MXU x is WO-EX, then when the state of the OMU 1 / SFU 1 / MXU 1 is WO-EX. MXU x is the MXU connected to the unit to be tested.


Note

In some cases, one sub-rack slot may house different functional units depending on the configuration of the network element. For detailed information on the equipping of sub-racks in different configurations, see IPA-RNC Engineering Description, 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

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



DN0939536 Issue 05

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

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

RSMU 0

SFU 0

TBU 0

TBU 1

SWU 0

OMS


DN0939536 Issue 05


25 /40

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

ICSU 4

ICSU 5

ICSU 6

ICSU 7

TBU 0

TBU 1



DN0939536 Issue 05



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

ICSU 14

ICSU 15

ICSU 16

ICSU 17

ICSU 18

ICSU 19

TBU 0

TBU 1


DN0939536 Issue 05


27 /40

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



DMCU 28

DMCU 29

DMCU 30

DMCU 31

DMCU 32

ICSU 26

ICSU 27

ICSU 28

ICSU 29

ICSU 30

ICSU 31

TBU 0

TBU 1



DN0939536 Issue 05



DMCU 33

DMCU 34

DMCU 35

DMCU 36

DMCU 37

ICSU 32

ICSU 33

ICSU 34

ICSU 35

ICSU 36

ICSU 37

TBU 0

TBU 1


6.9 Inspecting messaging system


Print out the working states of units (ZUSI). Check that all units are on the list (compare with the equipment list).

Run messaging system test. In detail, do the following:

• Open a service terminal connection RS232 to the active OMU or, if not possible, open a new MMI terminal session (ZDDS).


DN0939536 Issue 05


29 /40


Note

The service terminal connection or the second MMI terminal connection is used for executing and monitoring the test. The first MMI terminal session is used for changing the states of the active SFU and MXU units during the test.

• Load a post office service terminal extension 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 5 minutes.

• 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 the active MXUs for the active SFU in the table Checklist 1 for active MXU units.

• Change the state of the working state SFU 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 active units in table Checklist 2 for active MXU units. Compare with Checklist 1 for active MXU units that the index number of each MXU is now different within each MXU pair. Mark the status of the active MXU units in the table Checklist 2 for active MXU units for the active SFU.

• Change the states of working state SFU units to SP-EX (WO-EX -> SP-EX), (ZUSC). Monitor the output for a minimum of 5 minutes. Record the status of the active MXU units in the table Checklist 2 for active MXU units for the new active SFU unit.



DN0939536 Issue 05


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

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

MXU

MXU

MXU

MXU

MXU

Table 35. Checklist 2 for active MXU units

Commissioning Checklist for IPA-RNC Inspecting synchronization system

DN0939536 Issue 05


31 /40

7 Inspecting synchronization system Commissioning phase / related documents Completed

Check the synchronization cabling (external timing / line timing) connections against documentation. Make changes to the cabling if needed.




Cabinet Interfaces and External Cables of MGW and IPA-RNC

Recovery and Working State Administration

Replacing Plug-in Units


Check SSM values for external references and synchronization (ZDYI). Change them with ZDYK if needed.


Check available references and parameters (ZDYI), changing the WTR timer values if needed (ZDYL).

Use ZDYR if you need to control general synchronization system settings.


Inspecting synchronization system Commissioning Checklist for IPA-RNC


DN0939536 Issue 05


Check outgoing references (ZDYP). If outgoing synchronization is not given, set it with the command ZDYE.


Check system clock operating modes, and change them if needed.


Table 36. Inspecting synchronization system

Commissioning Checklist for IPA-RNC Configuring VDS device

DN0939536 Issue 05


33 /40

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

Connecting RNC to standalone RNC OMS Commissioning Checklist for IPA-RNC


DN0939536 Issue 05

9 Connecting RNC to standalone RNC OMS


Set up the RUOSTEQX service terminal extension.

Set the OMS southbound IP address for the RNC O&M connection, and check that the connection works (ZQRS).

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

Table 38. Connecting RNC to standalone RNC OMS

Commissioning Checklist for IPA-RNC Verifying OMS system startup

DN0939536 Issue 05


35 /40

10 Verifying OMS system startup 10.1 Verifying OMS BIOS system time

Commissioning 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 OMS

Commissioning 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 to start.

Check that the status returns no disabled processes.

Verifying OMS system startup Commissioning Checklist for IPA-RNC


DN0939536 Issue 05

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 the Element Manager.

Start and close each Element Manager application.

Check OMS Syslog (master-syslog) for error messages.

Table 42. Testing Element Manager applications

10.5 Testing secure Element Manager MMI window


Start the Application Launcher and log into the Element Manager.

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

Make a switchover to the OMU.

Give MML commands to test the MMI window application.

Log out from the Application Launcher.

Check OMS Syslog for error messages.

Table 43. Testing Element Manager's MMI window

Commissioning Checklist for IPA-RNC Finalizing commissioning

DN0939536 Issue 05


37 /40

11 Finalizing commissioning 11.1 Checking the delivery dependent functionalities

Note By default, NSN pre-configures the delivery dependent functionalities for each customer. During commissioning, it is recommendable to check the pre-configured delivery dependent functionalities.


Find out the local configuration requirements for the IPA-RNC.

For detailed information on Configurations and capacity steps, see IPA-RNC Engineering Description.

Interrogate parameter value (ZWOI:2,1248;).

If necessary, use the command ZWOC to change the parameter value as defined in Commissioning IPA-RNC.

Restart the system with the ZUSS command only if the parameter value was changed.

Mark here the parameter value used in the IPA-RNC in question: _____

Table 44. Checking the delivery dependent functionalities in RNC

Finalizing commissioning Commissioning Checklist for IPA-RNC


DN0939536 Issue 05

11.2 Performing SW update


If the pre-installed package is not compatible with the 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 disks and/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 the network element.

Commissioning Checklist for IPA-RNC Commissioning certificate of completion

DN0939536 Issue 05


39 /40

12 Commissioning certificate of completion

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 Solutions and Networks hereby states that the whole of the supplies detailed above have been inspected, tested and, unless otherwise stated, conform to the specified requirements in the contract or order identified above.

Date: _______________________________________________________________________________________________

Signature of site responsible: ____________________________________________________________________________

Commissioning certificate of completion Commissioning Checklist for IPA-RNC


DN0939536 Issue 05

V 85561974

Documents

Transcript of V 85561974