Commissioning RNC.pdf

WCDMA IPA-RNC

Commissioning Checklist for IPA-RNC DN0939536 Issue 03A Approval Date 2011-6-15

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 Siemens 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 Siemens 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 Siemens 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 Siemens Networks and the customer. However, Nokia Siemens 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 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 NO EVENT WILL NOKIA SIEMENS 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. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia 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 2011. All rights reserved.

DN0939536 Issue 03A

2 (43)

Table of Contents

Table of Contents Summary of Changes.............................................................................................5

DN0939536 Issue 03A

1 1.1 1.2

Commissioning checklist ......................................................................6 Using this checklist document ..................................................................6 Preparation of commissioning ..................................................................6

2

Safecopying FBEMPTY SW build .........................................................8

3

Inspecting hardware ..............................................................................9

4 4.1 4.2 4.3

Verifying system startup .....................................................................11 Powering on ...........................................................................................12 Logging into the MMI system for the first time........................................12 Verifying functional units' start-up ..........................................................13

5 5.1 5.2 5.3

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

6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8

Inspecting SW build and HW data ......................................................16 Creating Telnet or HTTP connection to OMU ........................................16 Inspecting the Hardware Management System .....................................17 Interrogating SW build information .........................................................18 Interrogating equipment database..........................................................19 Interrogating hardware data ...................................................................20 Inspecting I/O system.............................................................................21 Inspecting unit diagnostics and working states ......................................21 Inspecting messaging system ................................................................27

7

Inspecting synchronization system ...................................................30

8

Configuring VDS device ......................................................................31

9 9.1 9.2 9.3 9.4 9.5

Verifying OMS system startup ............................................................32 Verifying OMS BIOS system time ..........................................................32 Testing TCP/IP connections for OMS ....................................................32 Testing OMS software startup................................................................32 Testing Element Manager applications ..................................................33 Testing secure Element Manager MMI window .....................................33

10 10.1 10.2

Finalizing commissioning ...................................................................35 Checking the delivery dependent functionalities ....................................35 Performing the SW update .....................................................................36

3 (43)

DN0939536 Issue 03A

10.3 10.4

Safecopying SW build again.................................................................. 36 Reporting item code and serial number................................................. 36

11 11.1 11.2 11.3 11.4 11.5 11.6

Additional Inspections ........................................................................ 37 Formatting and initializing spare hard disk ............................................ 37 Testing replaced plug-in unit ................................................................. 38 Troubleshooting functional unit start-up ................................................ 38 Inspecting PCM Connection to Distribution Frame................................ 39 Inspecting Database Integrity ................................................................ 39 Installing the Change Notes .................................................................. 40

12

Certificate of completion .................................................................... 42

4 (43)

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

Changes between issues 03 and 03A

Please note that the issue safety information and product naming practice are changing. For more information, see Guide to WCDMA RAN and I-HSPA Operating Documentation. Title of the document changed from Commissioning Checklist for RNC to Commissioning Checklist for IPA-RNC. The safety information in this document has been revised on the basis of ANSI Z535.6-2006 and ISO 3864-2:2004.

Changes between issues 2-1 and 03

Document structure has been changed in accordance with the main commissioning document.

Changes between issues 2-0 and 2-1

TSS3-A plug-in unit has been added.

Changes between issues 1-0 and 2-0

PRFILE parameter value has changed in section Checking the Delivery Dependent Functionalities in RNC.

DN0939536 Issue 03A

5 (43)

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 RNC and mark down the completed steps and procedures in this document. The tables contain references to other product documents which may be necessary during each particular procedure. 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 missing tools and measurement devices. Commissioning RNC Check the availability of the site documents delivered online. Acquire the missing site documents. DN0939536 Issue 03A

6 (43)

Hardware Configuration Management Cable Lists for RNC Equipment Lists for RNC Hardware Revision List (NOLS) MGW and RNC, Jumper Settings of the Plug-in Units Software Release Binder Installing the MGW and RNC Software Configuration Management Use of ATM Links and LAN Connections in RNC I/O System Diagnostics and Testing Recovery and Unit Working State Administration Synchronisation and Timing Database Administration Change Note installation instruction (delivered with each Change Note Set) RNC Engineering Description

Table 1 Preparation of commissioning

DN0939536 Issue 03A

7 (43)

2

Safecopying FBEMPTY SW build


Completed

Prepare Performing Safecopying and Restoring Operations document for reference. Make fallback copy software build See Fallback Copying Software Build. Verify fallback build See Verifying Fallback Build. BMake a FB build backup copy on OMU hard disks See Backup Copying FB Build on OMU Hard Disks. Make a FB build backup copy on a USB stick See Backup Copying FB Build on MO Disk or USB Memory Stick.

Table 2 Safecopying SW build.

DN0939536 Issue 03A

8 (43)

3

Inspecting hardware


Completed

Inspect the hardware material visually. Pay attention to mechanical damage and scratches, for example. Check the inter-cabinet cables of the network element by comparing them with the cable lists in site documentation. Check all connectors for proper contact (for example, no plugs are loose). Hardware Configuration Management Cable Lists for RNC Check the locations of the plug-in units by comparing them with equipment lists in site documentation. Hardware Configuration Management Equipment Lists for RNC Check the interchangeability versions of the subracks by comparing them with the equipment lists in site documentation. Hardware Configuration Management Equipment Lists for RNC Hardware Revision List Check the interchangeability versions of the plug-in units by comparing them with the equipment lists in site documentation. Hardware Configuration Management Equipment Lists for RNC Hardware Revision List

DN0939536 Issue 03A

9 (43)


Completed

Check the jumper settings of the plug-in units.

CAUTION! Risk of equipment damage When handling hardware units, wear an ESD wrist strap or use a corresponding protection method, and do not touch the connector surfaces. MGW and RNC, Jumper Settings of the Plug-in Units Software Release Binder 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 to the table Measured voltages. Check that the voltages meet the tolerance requirements. Check the polarities of the supply lines as instructed in Installing the MGW and RNC. Hardware Configuration Management Installing the MGW and RNC

Table 3 Inspecting hardware

Cabinet

Voltage (V)

Polarity Checked

RNAC (UB1) RNAC (UB2) RNBC (UB1) RNBC (UB2)

Table 4 Measured voltages

DN0939536 Issue 03A

10 (43)

4

Verifying system startup


Completed

Check that units are in the states WO-EX or SP-EX (ZUSI). If a unit is not in the appropriate state, change the state (ZUSC). Recovery and Unit Working State Administration Disconnect power from the system. Recovery and Unit Working State Administration Connect power to the system. Check that the text 0689 SYSTEM RESTARTED is printed on the alarm printer. Check how long it takes for the system to show the alarm. Alarm 0689 to printer __________. Recovery and Unit Working State Administration Wait until the active OMU is in the state WOEX. Start a session from an MML terminal. Output working states of units from the MML terminal and monitor that every unit starts in the state it had before the power break (ZUSI). Record the time the functional units need to recover to their states. Units to WO-EX and SP-EX ________________. Recovery and Unit Working State Administration Monitor the alarm printout. All the starting units should cause a notice: 0691 WORKING STATE ACTIVATED BY SYSTEM. Recovery and Unit Working State Administration Check that no relevant alarms are on (ZAAP). Recovery and Unit Working State DN0939536 Issue 03A

11 (43)

Administration

Table 5 Verifying system start-up

4.1

Powering on


Completed

Power on the cabinet(s). Switch is at the top of the rack. Check if LEDs on each starting up functional units are either blinking green, solid green or yellow.

Table 6 Powering the system on.

4.2

Logging into the MMI system for the first time


Completed

Attach a computer to an Ethernet port of the ESA24. Open a Telnet session to the OMU by using the OMU’s preconfigured IP address. Log into the MMI system by using the default administrator user ID SYSTEM. Commissioning RNC Create a new MMI user profile (ZIAA). Commissioning RNC Create a new administrator user ID (ZIAH). Commissioning RNC Delete the default administrator user ID (SYSTEM)(ZIAD). Commissioning RNC

Table 7 Logging into the MMI system for the first time

The preset IP addresses are changed during integration. DN0939536 Issue 03A

12 (43)

4.3

Verifying functional units' start-up


Completed

Check that units are in WO-EX and SP-EX states (USI). ZUSI; Alarm Administration in RNC Check that no unnecessary alarms are on (AAP). ZAAP;

Table 8 Verifying functional units’ start-up

DN0939536 Issue 03A

13 (43)

5 5.1

Managing network element specific data Changing system name


Completed

Take a backup of the NECONF file. Commissioning RNC Change the system name in the NECONF file (ZDFS). Commissioning RNC Verify the system name (ZDFD). Commissioning RNC Take a printout of alarms (ZAAP). In the printout, you should see the new system name.

Table 9 Changing system name of the network element

5.2

Setting the calendar date and time


Completed

Set the correct date and time for the network element (ZDCS). DN0939536 Issue 03A

14 (43)


Completed

Commissioning RNC Set the correct NTP server IP address (ZDCM). Commissioning RNC NTP-IP address:

Table 10 Setting the calendar time and date for the network element

5.3

Enabling CPLD upgrade


Completed

Check the status of the CPLDs remote upgrade. D9Q; If the CPLDs remote upgrade is disabled, enable it ZD9S:E;

Table 11 Enabling CPLD upgrade

DN0939536 Issue 03A

15 (43)

6

Inspecting SW build and HW data

6.1

Creating Telnet or HTTP connection to OMU

6.1.1.1 Commissioning Phase/Related Documents

Completed

Establish a Telnet or HTTP connection to the OMU IP address, port 11111. Commissioning RNC 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 the table Logical files and VPP device connections. Commissioning RNC Check that the state of the corresponding VPP devices is WO-EX (ZIHI). Commissioning RNC Check that you can see alarms on the Telnet terminal or the web browser. Commissioning RNC

Table 12 Creating a telnet or HTTP connection to print alarms

Logical File

VPP Device

Logical File

ALARMS

ALACOMM2

ALACOMM1

ALAQUAL2

ALAQUAL1

ALAPROC2

DN0939536 Issue 03A

VPP Device

16 (43)

ALAPROC1

ALAEQUI2

ALAEQUI1

ALAENVI2

ALAENVI1

Table 13 Logical files and VPP device connections

6.2

Inspecting the Hardware Management System


Completed

Activate the HMEXTE service terminal extension (ZLP:2,HME). Commissioning RNC List the system configuration (Z2DP). Check that the information on the location of the plugin units is correct. Commissioning RNC 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. DN0939536 Issue 03A

17 (43)


Completed

10. Unblock the alarms you blocked in step 1. Record version numbers to the table HMS software versions. Check that the version matches the requirement for software level. Commissioning RNC Software Release Binder

Table 14 Inspecting the 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 15 HMS software versions

6.3

Interrogating SW build information


Completed

Verify that the correct software build is on the hard disk and loaded for every unit needed (ZWQO). Software Configuration Management Software Release Binder Default software package: Package-ID: Change Note ID: Verify that the software modules contain DN0939536 Issue 03A

18 (43)


Completed

flawless data (ZWQB). Software Configuration Management Compare the versions with the site-specific documents. Software Configuration Management Software Release Binder Check the version of the flash memory boot package of the unit against the SW package. See the table Boot-SW versions checklist.

Table 16 Interrogating software build information

Plug-in Unit

SW Version

Plug-in Unit

CCP18-A

CDSP-DH

MX1G6-A

NP2GE-B

SF20H

NP8S1-B

SW Version

Table 17 Boot SW versions checklist

6.4

Interrogating equipment database


Completed

Check the state and integrity of the equipment database and copy database files to disk. Hardware Configuration Management Inquire cabinet information (ZWFI:J:..). Check that the cabinet information in the database meets the physical configuration. Correct any discrepancies (ZWFJ, ZWFK). Hardware Configuration Management Inquire subrack information (ZWFI:C:..). Check that the subrack information in the database meets the physical configuration. Correct any discrepancies (ZWFC, ZWFD). Hardware Configuration Management DN0939536 Issue 03A

19 (43)


Completed

Inquire plug-in information (ZWFI:P:..). Check that the plug-in information in the database meets the physical configuration. Correct any discrepancies (ZWFP, ZWFQ). Hardware Configuration Management 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). Hardware Configuration Management Use of ATM Links and LAN Connections in RNC Inquire functional unit information (ZWFI:U:..). Check that the functional unit information in the database meets the physical configuration. Correct any discrepancies (ZWFU, ZWFV). Hardware Configuration Management

Table 18 Interrogating equipment database

6.5

Interrogating hardware data


Completed

Interrogate all hardware data of plug-in units (ZWFL:P;). Verify that the printed data are the same as on the labels of the plug-in units. Commissioning RNC Interrogate all hardware data of subracks (ZWFL:S;). Verify that the printed data are the same as on the subrack labels. Commissioning RNC

Table 19 Interrogating hardware data

DN0939536 Issue 03A

20 (43)

6.6

Inspecting I/O system

Inspecting Mass Memory Devices Commissioning Phase/Related Documents

Completed

Display the I/O devices (ZWFI). Check their operating states and state transitions (ZIHI). I/O System Diagnose hard disks (ZUDD). 

OMU (WDU-0)



OMU (WDU-1)

I/O System Change the operating state of an optical disk or a USB memory stick to TE-EX and diagnose it (ZUDD). Display a list of running and queuing tests (ZUDQ). Display the history of the diagnostic reports (ZUDH). I/O System

Table 20 Inspecting mass memory devices

6.7

Inspecting unit diagnostics and working states


Completed

Print out the working states of the units (ZUSI). Check that the units are in the WO-EX or SPEX state. Check that all units of the network element are on the list (compare with the equipment list). Equipment Lists for RNC Diagnostics and Testing Run unit diagnostics and perform change of unit states.

DN0939536 Issue 03A

21 (43)


Completed

Note There are differing instructions for 2N redundant units, N+1 redundant units, SN+ units and non-redundant units in Commissioning RNC. First run diagnostics on SFUs, then continue with MXUs. Then perform diagnostics for all other units.

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. Diagnostics and Testing

Table 21 Inspecting unit diagnostics and working states

Note In some cases, one subrack slot may house different functional units depending on the configuration of the RNC. In the tables below, the alternative functional unit equipping options are presented in the same row. For detailed information on the equipping of subracks in different configurations, see Engineering for Radio Network Controller (RNC) and Equipment Lists for RNC, both delivered in the Site Documents binder. Functional Unit

OMU 0 (WO-EX)

OMU 1 (WO-EX)

TBU 0 TBU 1

Table 22 TBU 0 and TBU 1 units

DN0939536 Issue 03A

22 (43)

Functional Unit

MXU 0 (WO-EX)

MXU 1 (WO-EX)

SFU 0 SFU 1

Table 23 SFU 0 and SFU 1 units in 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

Functional Unit

MXU 0 (WO-EX)

MXU 1 (WO-EX)

DMCU 0 DMCU 1 DMCU 2 DMCU 3 ICSU 0 OMU 0 RSMU 0 DN0939536 Issue 03A

23 (43)

SFU 0 TBU 0 TBU 1 SWU 0 OMS

Table 25 Functional units in subrack 1 (RNAC)

Functional Unit

MXU 2 (WO-EX)

MXU 3 (WO-EX)

DMCU 4 DMCU 5 DMCU 6 DMCU 7 ICSU 1 ICSU 2 OMU 1 RSMU 1 SFU 1 TBU 0 TBU 1


Functional Unit

MXU 4 (WO-EX)

MXU 5 (WO-EX)

DMCU 8 DMCU 9 DMCU 10 DMCU 11 DMCU 12 EHU ICSU 3 ICSU 4 ICSU 5 DN0939536 Issue 03A

24 (43)

Functional Unit

MXU 4 (WO-EX)

MXU 5 (WO-EX)

ICSU 6 ICSU 7 TBU 0 TBU 1


Functional Unit

MXU 6 (WO-EX)

MXU 7 (WO-EX)

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


Functional Unit

MXU 8 (WO-EX)

MXU 9 (WO-EX)

DMCU 18 DMCU 19 DMCU 20 DMCU 21 DMCU 22 ICSU 14 ICSU 15 ICSU 16 DN0939536 Issue 03A

25 (43)

Functional Unit

MXU 8 (WO-EX)

MXU 9 (WO-EX)

ICSU 17 ICSU 18 ICSU 19 TBU 0 TBU 1

Table 29 Functional units in subrack 1 (RNBC)

Functional Unit

MXU 10 (WO-EX)

MXU 11 (WO-EX)



Functional Unit

MXU 12 (WO-EX)

MXU 13 (WO-EX)

DMCU 28 DMCU 29 DMCU 30 DMCU 31 DMCU 32 ICSU 26 DN0939536 Issue 03A

26 (43)

Functional Unit

MXU 12 (WO-EX)

MXU 13 (WO-EX)

ICSU 27 ICSU 28 ICSU 29 ICSU 30 ICSU 31 TBU 0 TBU 1


Functional Unit

MXU 14 (WO-EX)

MXU 15 (WO-EX)



DN0939536 Issue 03A

27 (43)

6.8

Inspecting messaging system


Completed

Print out the working states of units (ZUSI). Check that all units of the exchange are on the list (compare with the equipment list). Equipment Lists for RNC Commissioning RNC 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).

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

DN0939536 Issue 03A

28 (43)


Completed

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.



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

Commissioning RNC

Table 33 Inspecting messaging system

MXU index

SFU 0

SFU 1

WO-EX

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 DN0939536 Issue 03A

29 (43)

MXU MXU MXU MXU

Table 35 Checklist 2 for active MXU units

DN0939536 Issue 03A

30 (43)

7

Inspecting synchronization system


Completed

Check cablings of line interfaces according to the equipment lists. Equipment Lists for RNC Synchronisation and Timing Cable Lists for RNC Cabinet Interfaces and External Cables of MGW and RNC Recovery and Working State Administration Replacing Plug-in Units Hardware Configuration Management Check synchronization connections and SSM parameter values (ZDYI). Make sure that no alarms are on, selected inputs are OK, and other inputs are in the correct status. If the parameters of the synchronization references have to be modified, modify them with the command ZDYM. Synchronisation and Timing Check synchronization generations (GEN1 or GEN2) with the command ZDYI: SSMGEN, edit with the command ZDYK. Synchronisation and Timing Check outgoing references (ZDYP). If outgoing synchronization is not given, set it with the command ZDYE. Synchronisation and Timing

Table 36 Inspecting synchronization system

DN0939536 Issue 03A

31 (43)

8

Configuring VDS device Note In Commissioning RNC, the instructions for configuring VDS device are in a later section.


Completed

Define the size and number, and the overwrite, skipping, and compression mode of disk files (ZIFF). I/O System Connect the desired logical file to the VDS device (ZIID, ZIIS). I/O System Set alarm limits for the file group (ZIFA). Set time control for closing the data file of the VDS device (ZIFT). I/O System Back up the VDS device. I/O System

Table 37 Configuring the VDS device

DN0939536 Issue 03A

32 (43)

9

Verifying OMS system startup

9.1

Verifying OMS BIOS system time

Commissioning Phase/ Related Documents

Completed

Verify time. #date If time is wrong change it. #date MMDDHHMMCCYY

Table 38 Verifying OMS BIOS system time

9.2

Testing TCP/IP connections for OMS

Commissioning Phase/ Related Documents

Completed

Ping all IP addresses. Commissioning RNC

Table 39 Testing IP connections for OMS

9.3

Testing OMS software startup


Completed

Start OMS services. Commissioning RNC DN0939536 Issue 03A

33 (43)

Check that status returns no disabled processes. Commissioning RNC

Table 40 Testing the start-up of Hascli and platform processes for OMS

9.4

Testing Element Manager applications


Completed

Install the Application Launcher (EM client). Commissioning RNC Start the Application Launcher and log into the Element Manager. Commissioning RNC Start and close each Element Manager application. Commissioning RNC Check OMS Syslog for error messages. Commissioning RNC

Table 41 Testing element manager spplications

9.5

Testing secure Element Manager MMI window

Commissioning Phase/Related documents

Completed

Start the Application Launcher and log into the Element Manager. Commissioning RNC Open the MMI window by double-clicking the icon. Give MML commands to test the MMI window application. Commissioning RNC Make a switchover to the OMU. Commissioning RNC DN0939536 Issue 03A

34 (43)

Commissioning Phase/Related documents

Completed

Give MML commands to test the MMI window application. Commissioning RNC Log out from the Application Launcher. Commissioning RNC Check OMS Syslog for error messages. Commissioning RNC

Table 42 Testing element manager's MMI window

DN0939536 Issue 03A

35 (43)

10 10.1

Finalizing commissioning Checking the delivery dependent functionalities Note By default, Nokia Siemens Networks pre-configures the delivery dependent functionalities for each customer. During commissioning, it is recommendable to check the pre-configured delivery dependent functionalities.


Completed

Find out the local configuration requirements for the RNC in question in reference to the following functionalities. For detailed information on Configurations and capacity steps, see RNC Product Description and RNC Engineering Description. 

PRFILE parameter setting according to RNC capacity step

Interrogate parameter value (ZWOI:2,1248;). If necessary, use the command ZWOC to change the parameter value. The possible parameter value is 1 for RNC2600/900, RNC2600/1500 and RNC2600/2600. Restart the system with the ZUSS command only if the parameter value was changed. Mark here the parameter value used in the RNC in question: _____ Commissioning RNC

Table 43 Checking the delivery dependent functionalities in RNC

DN0939536 Issue 03A

36 (43)

10.2

Performing the SW update


Completed

Update of the SW if the preinstalled package is not compatible with the network CD CD Installation Manual

Table 44 Performing the SW update

10.3

Safecopying SW build again


Completed

If any software-related changes had been made during the commissioning, repeat the safecopying procedure.

Commissioning RNC

Table 45 Safecopying SW build again

10.4

Reporting item code and serial number


Completed

Collect the item code and serial number.

Table 46 Reporting item code and serial number

DN0939536 Issue 03A

37 (43)

11

Additional Inspections

11.1

Formatting and initializing spare hard disk


Completed

Change the SCSI state to SE (IHE). ZIHE::SCSI,:SE; Remove the disk from its place Ensure jumpers in the new disk correspond to those in the replaced disk. MGW and RNC Jumper Settings of the Plug-in Units and Hard Disk Drives Put the new unit into its place. Change the SCSI state to TE (IHE). ZIHE::SCSI,:TE; Format the new disk, if it's not formatted (IWI). ZIWI::;

Initialize the formatted WDU, if it's not initialized (IWK). ZIWK::;

Change the SCSI state to SE (IHE). ZIHE::SCSI,:SE;

Remove the initialized spare unit disk. Put the old disk back Change the SCSI state to TE (IHE). ZIHE::SCSI,:TE; DN0939536 Issue 03A

38 (43)

Change the SCSI state to WO (IHE). ZIHE::SCSI,:WO;

Table 47 Formatting and initializing spare hard disk

11.2

Testing replaced plug-in unit


Completed

Check the unit state (USI). ZUSI; 2 Start the unit test (UDU). ZUDU:::;

3 Monitor the test progress (UDQ). ZUDQ; 4 Check the test result (UDH). ZUDH:;

Table 48 Testing replaced plug-in unit

11.3

Troubleshooting functional unit start-up


Completed

Connect the service terminal or PC with service terminal program to the OMU and switch the power on. When the needed software is loaded, the service terminal programs should be ready to use. Enter the correct username and password. Software Configuration Management Commissioning RNC In the OMU, activate the RS232 service terminal extension (ZLP:J,RCJ). Monitor the DN0939536 Issue 03A

39 (43)

states of the units (ZJI:ALL;). Commissioning RNC Check that all units receive the correct working states. Commissioning RNC

Table 49 Monitoring the unit start-up

11.4

Inspecting PCM Connection to Distribution Frame


Completed

Connect a loop for the first E1/T1 on the distribution frame. Check that no alarm is shown for that E1/T1. Check that Rx and Tx cables are not swapped for the first E1/T1. Do this by feeding in a 2 MBit signal at Rx connector on the distribution frame. Check that the alarm 2915 FAULT RATE MONITORING disappears. Now you can use the first E1/T1 for testing all other E1/T1 cabling. Cross-connect E1s/T1s one by one to the first E1/T1. Check for every E1/T1 you make a connection that no alarm is shown. Results:

Table 50 Inspecting PCM connection to distribution frame

11.5

Inspecting Database Integrity


Completed

List databases (ZDBL). DN0939536 Issue 03A

40 (43)

Database Administration Check database integrity on disk and on memory; see the table Databases checklist. In detail, do the following: 

Prevent the updating of the database on disk (ZDBP).



Check that the disk log of the database is empty (ZDBX).



Check the integrity of the database. Create a report on integrity checking into a separate file (ZDBV).



Resume the updating of the database on disk (ZDBR).



Display the contents of the integrity checking report file (ZIBT). Check that no inconsistencies are shown.

Run integrity check on all listed databases. Database Administration

Table 51 Inspecting database integrity

TEST

ARFILE 1

BAIDAT 0

EQDATA 0

Check database state Check integrity on disk Check integrity on memory

Table 52 Databases checklist

11.6

Installing the Change Notes

Commissioning phase/Related documents

Completed

Install further change notes needed for the network element. Software Release Binder Change Note installation instruction DN0939536 Issue 03A

41 (43)

(delivered with each Change Note Set) Change Notes / Change Note Sets:

Table 53 Installing the change notes

DN0939536 Issue 03A

42 (43)

12

Certificate of completion

STAGE (initials)

COMPLETE / OK

Preparation of commissioning

________________________

Initial inspections

________________________

Inspection of I/O system ________________________ Inspection of maintenance system

________________________

Configuring OMS

________________________

Additional inspections ________________________ Installing the change notes

________________________

Configuring optional functionalities

CUSTOMER NAME

_____________________________________

CONTRACT NO

_____________________________________

SITE NAME _____________________________________ SITE NO.

_____________________________________

SITE ADDRESS

_____________________________________

SOFTWARE RELEASE _____________________________________

COMMENTS / DEFICIENCY

Nokia Siemens 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 order or contract identified above.

Date _____________________________________

Signature of site responsible

_____________________________________

Print name

_____________________________________

DN0939536 Issue 03A

43 (43)

Commissioning RNC.pdf

Recommend Documents