WCDMA RAN, Rel. RU40, Operating
Documentation
Commissioning Checklist for IPARNC
DN0939536
Issue 04A
Approval date 2013-04-26
DN0939536
Issue 04A
© Nokia Siemens Networks
1 (40)
Commissioning Checklist for IPA-RNC
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 2013. All rights reserved.
2 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Contents
Contents
DN0939536
Issue 04A
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 ......................................................................................... 11
Logging into the MMI system for the first time ...................................... 11
Verifying functional units’ start-up......................................................... 12
5
5.1
5.2
5.3
Managing network element specific data ......................................... 13
Changing system name ....................................................................... 13
Setting the calendar date and time ....................................................... 13
Enabling CPLD upgrade ...................................................................... 14
6
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
Inspecting SW build and HW data .................................................... 15
Creating Telnet or HTTP connection to OMU ....................................... 15
Inspecting Hardware Management System .......................................... 16
Interrogating SW build information ....................................................... 17
Interrogating equipment database ........................................................ 19
Verifying hardware data consistency with actual configuration ............. 20
Checking the memory size of the CCP1D-A plug-in unit ...................... 20
Inspecting I/O system........................................................................... 21
Inspecting unit diagnostics and working states ..................................... 21
Inspecting messaging system .............................................................. 28
7
Inspecting synchronization system .................................................. 31
8
Configuring VDS device .................................................................... 33
9
Connecting RNC to standalone RNC OMS ....................................... 34
10
10.1
10.2
10.3
10.4
10.5
Verifying OMS system startup .......................................................... 35
Verifying OMS BIOS system time......................................................... 35
Testing TCP/IP connections for OMS ................................................... 35
Testing OMS software startup .............................................................. 35
Testing Element Manager applications ................................................ 36
Testing secure Element Manager MMI window .................................... 36
11
11.1
Finalizing commissioning ................................................................. 37
Checking the delivery dependent functionalities ................................... 37
© Nokia Siemens Networks
3 (40)
Commissioning Checklist for IPA-RNC
4 (40)
11.2
11.3
11.4
Performing SW update ......................................................................... 38
Safecopying SW build again ................................................................ 38
Recording item code and serial number ............................................... 38
12
Commissioning certificate of completion ........................................ 39
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
Summary of changes
Changes between issues 04 (RU40, 2013-02-22) and 04A (2013-0426, 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-0222, 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.
DN0939536
Issue 04A
© Nokia Siemens Networks
5 (40)
Commissioning Checklist for IPA-RNC
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
6 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
Commissioning phase / related documents
Completed
Check the availability of the site documents
delivered online. Acquire the missing site
documents.
Hardware Configuration Management in IPA-RNC
Cable Lists for RNC196
Cable Lists for RNC450
Cable Lists for RNC2600
Equipment Lists for RNC196
Equipment Lists for RNC450
Equipment Lists for RNC2600
MGW and IPA-RNC, Jumper Settings of the Plugin 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
ATM Links and LAN Connections in RNC450
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
DN0939536
Issue 04A
© Nokia Siemens Networks
7 (40)
Commissioning Checklist for IPA-RNC
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
8 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
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
site documentation. Check all connectors for
proper contact (for example, no plugs are loose).
Hardware Configuration Management in IPA-RNC
Cable Lists for RNC196
Cable Lists for RNC450
Cable Lists for RNC2600
Check the locations of the plug-in units by
comparing them with equipment lists in site
documentation.
Hardware Configuration Management in IPA-RNC
Equipment Lists for RNC196
Equipment Lists for RNC450
Equipment Lists for RNC2600
Check the interchangeability versions of the subracks by comparing them with the equipment lists
in site documentation.
Hardware Configuration Management in IPA-RNC
Equipment Lists for RNC196
Equipment Lists for RNC450
Equipment Lists for RNC2600
Hardware Revision List for WCDMA IPA-RNC
DN0939536
Issue 04A
© Nokia Siemens Networks
9 (40)
Commissioning Checklist for IPA-RNC
Commissioning phase / related documents
Completed
Check the interchangeability versions of the plugin units by comparing them with the equipment
lists in site documentation.
Hardware Configuration Management in IPA-RNC
Equipment Lists for RNC196
Equipment Lists for RNC450
Equipment Lists for RNC2600
Hardware Revision List for WCDMA IPA-RNC
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
10 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
4
4.1
Verifying system startup
Powering on
Commissioning phase / related documents
Completed
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
Commissioning phase / related documents
Completed
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.
DN0939536
Issue 04A
© Nokia Siemens Networks
11 (40)
Commissioning Checklist for IPA-RNC
4.3
Verifying functional units’ start-up
Commissioning phase / related documents
Completed
Check that all units have the correct working
states and that there are no major alarms
Table 7. Verifying functional units’ start-up
12 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
5
5.1
Managing network element specific
data
Changing system name
Commissioning phase / related documents
Completed
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
Commissioning phase / related documents
Completed
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
DN0939536
Issue 04A
© Nokia Siemens Networks
13 (40)
Commissioning Checklist for IPA-RNC
5.3
Enabling CPLD upgrade
Commissioning phase / related documents
Completed
Check the status of the CPLD remote upgrade. If
it is disabled, enable it.
Table 10. Enabling CPLD upgrade
14 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
6
6.1
Inspecting SW build and HW data
Creating Telnet or HTTP connection to OMU
Commissioning phase / related documents
Completed
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
ALARMS
ALACOMM2
ALACOMM1
ALAQUAL2
ALAQUAL1
ALAPROC2
ALAPROC1
ALAEQUI2
ALAEQUI1
ALAENVI2
DN0939536
Issue 04A
© Nokia Siemens Networks
VPP device
15 (40)
Commissioning Checklist for IPA-RNC
Logical file
VPP device
Logical file
VPP device
ALAENVI1
Table 12. Logical files and VPP device connections
6.2
Inspecting Hardware Management System
Commissioning phase / related documents
Completed
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.
16 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
Commissioning phase / related documents
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.
Software Release Binder
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
Commissioning phase / related documents
Completed
Verify that the correct software build is on the
hard disk and loaded for every unit needed
(ZWQO).
Managing IPA-RNC Software Configuration
Software Release Binder
Default software package:
Package-ID:
Change Note ID:
DN0939536
Issue 04A
© Nokia Siemens Networks
17 (40)
Commissioning Checklist for IPA-RNC
Commissioning phase / related documents
Completed
Check the software build versions (ZWQB) to find
any erroneous modules.
Managing IPA-RNC Software Configuration
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 15. Interrogating SW build information
Plug-in unit
SW version
Plug-in unit
CCP10
CCP18*
CCP1D-A
CDSP-DH
MX1G6*
MX622*
NI16P1A
NI4S1-B
NP2GE-B
NP8S1-B
SF10
SF10E
SW version
SF20H
* refers to the plug-in unit itself or/and its variants
Table 16. Boot-SW versions checklist
18 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
6.4
Interrogating equipment database
Commissioning phase / related documents
Completed
Check the state and integrity of the equipment
database and copy database files to disk.
Hardware Configuration Management in IPA-RNC
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 in IPA-RNC
Inquire sub-rack information (ZWFI:C:..). Check
that the sub-rack information in the database
meets the physical configuration. Correct any
discrepancies (ZWFC, ZWFD).
Hardware Configuration Management in IPA-RNC
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).
Hardware Configuration Management in IPA-RNC
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 in IPA-RNC
ATM Links and LAN Connections in RNC196
ATM Links and LAN Connections in RNC450
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.
DN0939536
Issue 04A
© Nokia Siemens Networks
19 (40)
Commissioning Checklist for IPA-RNC
Commissioning phase / related documents
Completed
Correct any discrepancies (ZWFU, ZWFV).
Hardware Configuration Management in IPA-RNC
Table 17. Interrogating equipment database
6.5
Verifying hardware data consistency with actual
configuration
Commissioning phase / related documents
Completed
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 plugin 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
20 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
6.7
Inspecting I/O system
Commissioning phase / related documents
Completed
Display the I/O devices (ZWFI). Check their
operating states and state transitions (ZIHI).
Managing I/O System in IPA-RNC
Diagnose hard disks (ZUDD).
•
OMU (WDU-0)
•
OMU (WDU-1)
Managing I/O System in IPA-RNC
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).
Managing I/O System in IPA-RNC
Table 20. Inspecting I/O system
6.8
Inspecting unit diagnostics and working states
Commissioning phase / related documents
Completed
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).
Equipment Lists for RNC196
Equipment Lists for RNC450
Equipment Lists for RNC2600
Diagnostics and Testing in IPA-RNC
Run unit diagnostics and perform change of unit
states.
DN0939536
Issue 04A
© Nokia Siemens Networks
21 (40)
Commissioning Checklist for IPA-RNC
Commissioning phase / related documents
Completed
Note
There are differing
instructions for 2N redundant
units, N+1 redundant units,
SN+ units and non-redundant
units in Commissioning IPARNC.
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 in IPA-RNC
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, Equipment Lists for RNC196, Equipment Lists for
RNC450, 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
22 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
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
Functional unit
MXU 0 (WO-EX)
MXU 1 (WO-EX)
DMCU 0
DMCU 1
DMCU 2
DMCU 3
ICSU 0
OMU 0
DN0939536
Issue 04A
© Nokia Siemens Networks
23 (40)
Commissioning Checklist for IPA-RNC
Functional unit
MXU 0 (WO-EX)
MXU 1 (WO-EX)
RSMU 0
SFU 0
TBU 0
TBU 1
SWU 0
OMS
Table 25. Functional units in sub-rack 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
Table 26. Functional units in sub-rack 2 (RNAC)
Functional unit
MXU 4 (WO-EX)
MXU 5 (WO-EX)
DMCU 8
DMCU 9
DMCU 10
DMCU 11
DMCU 12
EHU
ICSU 3
24 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
Functional unit
MXU 4 (WO-EX)
MXU 5 (WO-EX)
ICSU 4
ICSU 5
ICSU 6
ICSU 7
TBU 0
TBU 1
Table 27. Functional units in sub-rack 3 (RNAC)
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
Table 28. Functional units in sub-rack 4 (RNAC)
Functional unit
MXU 8 (WO-EX)
MXU 9 (WO-EX)
DMCU 18
DMCU 19
DMCU 20
DMCU 21
DMCU 22
DN0939536
Issue 04A
© Nokia Siemens Networks
25 (40)
Commissioning Checklist for IPA-RNC
Functional unit
MXU 8 (WO-EX)
MXU 9 (WO-EX)
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)
Functional unit
MXU 10 (WO-EX)
MXU 11 (WO-EX)
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)
Functional unit
MXU 12 (WO-EX)
MXU 13 (WO-EX)
DMCU 28
DMCU 29
DMCU 30
26 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
Functional unit
MXU 12 (WO-EX)
MXU 13 (WO-EX)
DMCU 31
DMCU 32
ICSU 26
ICSU 27
ICSU 28
ICSU 29
ICSU 30
ICSU 31
TBU 0
TBU 1
Table 31. Functional units in sub-rack 3 (RNBC)
Functional unit
MXU 14 (WO-EX)
MXU 15 (WO-EX)
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
Table 32. Functional units in sub-rack 4 (RNBC)
DN0939536
Issue 04A
© Nokia Siemens Networks
27 (40)
Commissioning Checklist for IPA-RNC
6.9
Inspecting messaging system
Commissioning phase / related documents
Completed
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).
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
28 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
Commissioning phase / related documents
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.
Table 33. Inspecting messaging system
MXU index
SFU 0
SFU 1
WO-EX
WO-EX
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
MXU
MXU
MXU
DN0939536
Issue 04A
© Nokia Siemens Networks
29 (40)
Commissioning Checklist for IPA-RNC
MXU index
SFU 0
SFU 1
WO-EX
WO-EX
MXU
MXU
MXU
MXU
MXU
Table 35. Checklist 2 for active MXU units
30 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
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.
Equipment Lists for RNC196
Equipment Lists for RNC450
Equipment Lists for RNC2600
Synchronization and Timing in IPA-RNC
Cable Lists for RNC196
Cable Lists for RNC450
Cable Lists for RNC2600
Cabinet Interfaces and External Cables of MGW
and IPA-RNC
Recovery and Working State Administration
Replacing Plug-in Units
Hardware Configuration Management in IPA-RNC
Check SSM values for external references and
synchronization (ZDYI). Change them with ZDYK
if needed.
Synchronization and Timing in IPA-RNC
Check available references and parameters
(ZDYI), changing the WTR timer values if needed
(ZDYL).
DN0939536
Issue 04A
© Nokia Siemens Networks
31 (40)
Commissioning Checklist for IPA-RNC
Commissioning phase / related documents
Completed
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.
Synchronization and Timing in IPA-RNC
Check system clock operating modes, and
change them if needed.
Synchronization and Timing in IPA-RNC
Table 36. Inspecting synchronization system
32 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
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).
Managing I/O System in IPA-RNC
Connect the desired logical file to the VDS device
(ZIID, ZIIS).
Managing I/O System in IPA-RNC
Set alarm limits for the file group (ZIFA).
Set time control for closing the data file of the
VDS device (ZIFT).
Managing I/O System in IPA-RNC
Back up the VDS device.
Managing I/O System in IPA-RNC
Table 37. Configuring the VDS device
DN0939536
Issue 04A
© Nokia Siemens Networks
33 (40)
Commissioning Checklist for IPA-RNC
9
Connecting RNC to standalone RNC
OMS
Commissioning phase / related documents
Completed
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
34 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
10
10.1
Verifying OMS system startup
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
Commissioning phase / related documents
Completed
Log into OMS and check that all the services to
start.
DN0939536
Issue 04A
© Nokia Siemens Networks
35 (40)
Commissioning Checklist for IPA-RNC
Commissioning phase / related documents
Completed
Check that the status returns no disabled
processes.
Table 41. Testing OMS software startup
10.4
Testing Element Manager applications
Commissioning phase / related documents
Completed
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
Commissioning phase / related documents
Completed
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
36 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
11
11.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.
Commissioning phase / related documents
Completed
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 IPARNC in question: _____
Table 44. Checking the delivery dependent functionalities in RNC
DN0939536
Issue 04A
© Nokia Siemens Networks
37 (40)
Commissioning Checklist for IPA-RNC
11.2
Performing SW update
Commissioning phase / related documents
Completed
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
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 46. Safecopying SW build
11.4
Recording item code and serial number
Commissioning phase / related documents
Completed
Record the item codes and serial numbers of the
network element.
Table 47. Recording item code and serial number
38 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A
Commissioning Checklist for IPA-RNC
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 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 contract or order identified above.
Date: _______________________________________________________________________________________________
Signature of site responsible: ____________________________________________________________________________
DN0939536
Issue 04A
© Nokia Siemens Networks
39 (40)
Commissioning Checklist for IPA-RNC
40 (40)
© Nokia Siemens Networks
DN0939536
Issue 04A