30-3006 (Alcatel-Lucent 9370 RNC UA08.1 Integration) 01.01 Draft July 2011

DRAFT
Title page
Alcatel-Lucent 9370
Radio Network Controller | UA08.1
Integration
DRAFT
30-3006
Issue 1.01
July 2011
Legal notice
DRAFT
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2011 Alcatel-Lucent. All rights reserved.
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be altered only by authorized
persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to the current issue. Any hardcopies taken
must be regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except as expressly authorized in
writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need
to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the
holder is granted no rights to use the information contained herein. If you have received this document in error, please notify the sender and destroy it
immediately.
DRAFT
Contents
DRAFT
About this document
Purpose ............................................................................................................................................................................................. xi
xi
Reason for revision ...................................................................................................................................................................... xi

xi
New in this release ....................................................................................................................................................................... xi

xi
Intended audience ......................................................................................................................................................................... xi

xi
Supported systems ........................................................................................................................................................................ xi

xi
How to use this document ......................................................................................................................................................... xi

xi
Prerequisites .................................................................................................................................................................................. xii

xii
Conventions used ........................................................................................................................................................................ xii

xii
Related information .................................................................................................................................................................... xii

xii
Document support ...................................................................................................................................................................... xiii

xiii
Technical support ....................................................................................................................................................................... xiii

xiii
How to order ................................................................................................................................................................................ xiii

xiii
How to comment ........................................................................................................................................................................ xiii

xiii
1 Material Requirements
Overview ...................................................................................................................................................................................... 1-1

1-1
System requirements ................................................................................................................................................................ 1-2

1-2
Precautions and preparation .................................................................................................................................................. 1-3

1-3
General overview ...................................................................................................................................................................... 1-4

1-4
2 Integration preparation
Overview ...................................................................................................................................................................................... 2-1

2-1
Precautions and preparation .................................................................................................................................................. 2-2

2-2
DRAFT
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC iii
30-3006 UA08.1
Issue 1.01 July 2011
DRAFT Contents
....................................................................................................................................................................................................................................
3 Integration procedures
Overview ...................................................................................................................................................................................... 3-1

3-1
RNC IN attributes checks
Overview ...................................................................................................................................................................................... 3-3

3-3
RNC-IN Parameters Checks ................................................................................................................................................. 3-4

3-4
Session Manager: RNC declaration, validation, and activation
Overview ...................................................................................................................................................................................... 3-6

3-6
Session Creation for INode Declaration, Validation, and Activation .................................................................... 3-8
3-8
CNode Activation Session
Overview ................................................................................................................................................................................... 3-16

3-16
Activation Session ................................................................................................................................................................. 3-17

3-17
Equipment Monitor checks
Overview ................................................................................................................................................................................... 3-21

3-21
Equipment Monitor Checks ................................................................................................................................................ 3-22

3-22
Iub, Iur Validation: ATM Interfaces
Overview ................................................................................................................................................................................... 3-25

3-25
Iub, Iur Validation .................................................................................................................................................................. 3-26

3-26
Communication Tests
Overview ................................................................................................................................................................................... 3-30

3-30
CS Tests ..................................................................................................................................................................................... 3-31

3-31
Voice Call on the Unlocked Cell ....................................................................................................................................... 3-33

3-33
Video Call on the Unlocked Cell (Optional) ................................................................................................................ 3-35

3-35
Dial-up Connection ................................................................................................................................................................ 3-36

3-36
IP Address Allocation ........................................................................................................................................................... 3-37

3-37
Ping the GGSN ........................................................................................................................................................................ 3-38

3-38
Open a FTP Session (Optional) ......................................................................................................................................... 3-40

3-40
DRAFT
....................................................................................................................................................................................................................................
iv Alcatel-Lucent 9370 RNC
30-3006 UA08.1
Contents
DRAFT
....................................................................................................................................................................................................................................
Iux Validation: IP Interfaces
Overview ................................................................................................................................................................................... 3-42

3-42
Iux validation ........................................................................................................................................................................... 3-43

3-43
Optional operations regarding layout operations and UTRAN checks
Overview ................................................................................................................................................................................... 3-49

3-49
Attributes check with CAS commands ........................................................................................................................... 3-50

3-50
Layout operations ................................................................................................................................................................... 3-51

3-51
Opening a Layout in Edit Mode ........................................................................................................................................ 3-52

3-52
Insert the NEs in the Layout ............................................................................................................................................... 3-53

3-53
RNC Operations ...................................................................................................................................................................... 3-56

3-56
RNC MIB Audit ...................................................................................................................................................................... 3-58

3-58
4 RNC Counters
Overview ...................................................................................................................................................................................... 4-1

4-1
RNC Counters
Overview ...................................................................................................................................................................................... 4-2

4-2
Enabling the RNC Counters .................................................................................................................................................. 4-3

4-3
A Glossary
Glossary of terms ..................................................................................................................................................................... A-1

A-1
B Report Sheet
Overview ..................................................................................................................................................................................... B-1

B-1
Integration report sheet .......................................................................................................................................................... B-2

B-2
Index
DRAFT
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC v
30-3006 UA08.1
DRAFT Contents
....................................................................................................................................................................................................................................
DRAFT
....................................................................................................................................................................................................................................
vi Alcatel-Lucent 9370 RNC
30-3006 UA08.1
List of tables
DRAFT
B-1 BTS Parameters ......................................................................................................................................................... B-2
B-2
B-2 RNC Parameters ........................................................................................................................................................ B-2

B-2
B-3 Communication Tests .............................................................................................................................................. B-2

B-2
B-4 Antennae Positions ................................................................................................................................................... B-2

B-2
B-5 RNC Software ............................................................................................................................................................ B-2

B-2
B-6 Sequence of Operations .......................................................................................................................................... B-3
DRAFT
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC vii
30-3006 UA08.1
DRAFT List of tables
....................................................................................................................................................................................................................................
DRAFT
....................................................................................................................................................................................................................................
viii Alcatel-Lucent 9370 RNC
30-3006 UA08.1
List of figures
DRAFT
3-1 Hosts file ....................................................................................................................................................................... 3-8
3-8
3-2 Session Creation ......................................................................................................................................................... 3-9

3-9
3-3 Workorder Selection .............................................................................................................................................. 3-10

3-10
3-4 Workorder Steps ...................................................................................................................................................... 3-11

3-11
3-5 Session Launched .................................................................................................................................................... 3-12

3-12
3-6 Validation Step ......................................................................................................................................................... 3-12

3-12
3-7 Summary Session .................................................................................................................................................... 3-13

3-13
3-8 Validation Report .................................................................................................................................................... 3-13

3-13
3-9 Activation Step ......................................................................................................................................................... 3-14

3-14
3-10 9370 RNC Layout ................................................................................................................................................... 3-15

3-15
3-11 Administrative State: Unlock Window ........................................................................................................... 3-15
3-12 RNC Pre Activation ................................................................................................................................................ 3-17

3-17
3-13 RNC Activation ....................................................................................................................................................... 3-18

3-18
3-14 Command Manager ................................................................................................................................................ 3-18

3-18
3-15 RNC Session Manager .......................................................................................................................................... 3-19
3-16 Summary RNC and PP(INode) Activated ...................................................................................................... 3-20
3-17 RNC Equipment Monitor ..................................................................................................................................... 3-22
3-18 RNC INode Equipment Monitor ....................................................................................................................... 3-23
3-19 Access to "Alarm Command" ............................................................................................................................. 3-23
3-20 Alarm Manager Window ...................................................................................................................................... 3-24
3-21 Iur Link ....................................................................................................................................................................... 3-29

3-29
3-22 FDD Cells .................................................................................................................................................................. 3-31

3-31
3-23 FDD Cell Administrative State .......................................................................................................................... 3-32

DRAFT
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC ix
30-3006 UA08.1
DRAFT List of figures
....................................................................................................................................................................................................................................
3-24 Command Manager ................................................................................................................................................ 3-32
3-32
3-25 Voice Call Test .......................................................................................................................................................... 3-34

3-34
3-26 Video Call Test ......................................................................................................................................................... 3-35

3-35
3-27 Dial-up Connection ................................................................................................................................................ 3-36

3-36
3-28 IP address Allocation ............................................................................................................................................. 3-37

3-37
3-29 Ping Way .................................................................................................................................................................... 3-38

3-38
3-30 Ping Command ......................................................................................................................................................... 3-39

3-39
3-31 Ping Message ............................................................................................................................................................ 3-39

3-39
3-32 FTP Connection ....................................................................................................................................................... 3-40

3-40
3-33 Downlink Transfer .................................................................................................................................................. 3-41

3-41
3-34 Uplink Transfer ........................................................................................................................................................ 3-41

3-41
3-35 Layout Selector ........................................................................................................................................................ 3-51

3-51
3-36 Edit Mode .................................................................................................................................................................. 3-52

3-52
3-37 NE Find ....................................................................................................................................................................... 3-53

3-53
3-38 NE Store ..................................................................................................................................................................... 3-54

3-54
3-39 NE Store ..................................................................................................................................................................... 3-54

3-54
3-40 File Menu ................................................................................................................................................................... 3-55

3-55
3-41 OAM Link ................................................................................................................................................................. 3-56

3-56
3-42 NE's Administrative State .................................................................................................................................... 3-56

3-56
3-43 RNC Status ................................................................................................................................................................ 3-57

3-57
3-44 RNC Object Audit ................................................................................................................................................... 3-58

3-58
3-45 Action Window ........................................................................................................................................................ 3-58

3-58
3-46 Command Manager ................................................................................................................................................ 3-59

3-59
3-47 Audit Logs ................................................................................................................................................................. 3-59

3-59
3-48 MIB Rebuild ............................................................................................................................................................. 3-60

3-60
DRAFT
....................................................................................................................................................................................................................................
x Alcatel-Lucent 9370 RNC
30-3006 UA08.1
DRAFT
About this document
About this document
Purpose
The purpose of this document is to describe the operations performed to integrate new
Alcatel-Lucent 9370 RNC in an UTRAN.
Equipment/application: This method is Applicable for 9370 RNC with UA08.x software
release.
Reason for revision

The reissue reasons are:
Issue number Issue Date Reason for reissue

1.01 July 2010 Draft issue
New in this release

New features:
• None
Other changes:
• Reformat to comply with current documentation standards.
Intended audience
The audience for this document is Installation personnel and Commissioning personnel.
Supported systems
This document applies to Alcatel-Lucent W-CDMA UA08.1 system release.
This document applies to Alcatel-Lucent 9370 RNC.
How to use this document

DRAFT
Complete the procedures in the order presented.

...................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC xi
30-3006 UA08.1
DRAFT About this document
....................................................................................................................................................................................................................................
Prerequisites
This method is to be performed after the following procedures:
• IM 24-6223 Alcatel-Lucent 9370 RNC UA08.x Commissioning
Conventions used
Vocabulary conventions
None
Typographical conventions
Appearance Description
italicized text • File and directory names
• Emphasized information
graphical user interface text Text that is displayed in a graphical user interface or in a
hardware label
variable A value that the user supplies
key name The name of a key on the keyboard
command-syntax Command names that the user types
input text Text that the user types or selects as input to a system
output text Text that a system displays or prints
IP reference, IP number Related document that is referenced in the document
Related information
For information on subjects related to the content of this document, refer to the
documents listed in the following table:
Refer to this document At this location For more information on

Alcatel-Lucent 9353 Contact Alcatel-Lucent Overview of the Universal
Management System - Online Customer Support Terrestrial Radio Access
Overview, NN-20500-031 (OLCS) Network (UTRAN) and of
theWireless Management
System (WMS).
Alcatel-Lucent 9353 Contact Alcatel-Lucent How to operate the
Management System - User Online Customer Support commands available in the
Guide, NN-20500-032 (OLCS) 9353Wireless Management
System (9353 WMS)
Graphical User Interface
DRAFT
(GUI).
....................................................................................................................................................................................................................................
xii Alcatel-Lucent 9370 RNC
30-3006 UA08.1
About this document
DRAFT
....................................................................................................................................................................................................................................
Refer to this document At this location For more information on

Alcatel-Lucent 9952 Contact Alcatel-Lucent The user manual of the
Provisioning System User Online Customer Support Wireless Provisioning System
Guide, NN-20500-036 (OLCS) (WPS) for UMTS Access
Network.
Alcatel-Lucent 9300 Contact Alcatel-Lucent Global view of the
W-CDMA Product Family Online Customer Support Configuration Management
Configuration Management., (OLCS) inside the Access Network.
NN-20500-169 For each facet of the network
configuration, this document
gives the key information to
configure and manage the
UTRAN.
Document support
For support in using this or any other Alcatel-Lucent document, contact Alcatel-Lucent at
one of the following telephone numbers:
• 1-888-582-3688 (for the United States)
• 1-317-377-8618 (for all other countries)
Technical support
For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/) for contact
information.
How to order
To order Alcatel-Lucent documents, contact your local sales representative or use Online
Customer Support (OLCS) (http://support.alcatel-lucent.com)
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/enus/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
DRAFT
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC xiii
30-3006 UA08.1
DRAFT About this document
....................................................................................................................................................................................................................................
DRAFT
....................................................................................................................................................................................................................................
xiv Alcatel-Lucent 9370 RNC
30-3006 UA08.1
DRAFT
1 Material Requirements
1
Overview
Purpose
This chapter describes the software, hardware and login requirements.
Contents
System requirements 1-2

Precautions and preparation 1-3
General overview 1-4
DRAFT
...................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC 1-1
30-3006 UA08.1
DRAFT Material Requirements System requirements
....................................................................................................................................................................................................................................
System requirements
Operating systems and Software
Following are the supported by OAM 8.1 client are:
• Operating Systems (OS): Windows XP, Windows 7, and Windows Vista
• Java version for OAM Client is Java Runtime Environment (JRE) 1.5 or higher
• User is expected to have Exceed available (for running MDM)
• WEB browser: Internet explorer 6 or higher, Mozilla Firefox 1.7 or higher
• Telnet VT100
Hardware requirements
• 3G Mobile (for CS calls)
• PC setup with Mobile Driver
• PC Dial up connection ready (for PS data Calls)
No other materials are required to perform this method.
Login credentials
WMS OAM Client administrator account login and password with full access is required.
DRAFT
....................................................................................................................................................................................................................................
1-2 Alcatel-Lucent 9370 RNC
30-3006 UA08.1
Material Requirements Precautions and preparation
DRAFT
....................................................................................................................................................................................................................................
Precautions and preparation

Precautions
Check that all the prerequisites have been done and that the input parameters regarding
the dedicated site operations are correctly filled, refer to Appendix B, “Report Sheet”.
Preparations
It is strongly recommended that this method be read in its entirety before starting the
operations described in this document.
Checklist
Verify that the following items have been received and/or accomplished before
proceeding with the procedure.
• The Node B has been commissioned using Node B Commissioning Procedure, IM
24-6253.
• The RNC has been commissioned using Alcatel-Lucent 9370 RNC Commissioning
Method, IM 24-6223.
• The valid JRE already downloaded to access to the first GUI URL.
• An Exceed version running before the MDM start.
• The NSP GUI with access plug-in on OAM PC client have been installed and are
operational. At least one user should be created in the NSP administrator group, the
correct access rights have to be set to allow the user to create a layout.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Material Requirements General overview
....................................................................................................................................................................................................................................
General overview
UTRAN introduction of the UA08 / OAM08 system release
The UTRAN is composed of several Radio Network Subsystems (RNS). An RNS covers
a certain geographical area. It is equivalent to the GSM BSS. Each RNS is composed of
one Radio Network Controller (RNC) and several Node Bs. RNSs are interconnected
through the Iur interface of each RNC to form a network.
Alcatel-Lucent UTRAN
The Alcatel-Lucent UTRAN of the UA08 / OAM08 system release is based on the
following components:
• UMTS RNC
• UMTS BTS
• WMS for the OAM part
• UTRAN release is UA08 / OAM08
RNC Main Functions

The main functions of the RNC are to control and manage:
• Radio Access Network (RAN)
• Signaling between Core Network (CN) components and the Radio Network System
(RNS)
• Node Bs and their radio resources
The RNC provides the following interfaces:
• Iub towards a Node B
• Iu towards the Core Network
• Iur towards another RNC
• Iupc towards a Standalone A-GPS SMLC (SAS)
WMS General principles

The Wireless Network Management System (WMS) is the solution for network planning,
building, operation and maintenance. WMS is built on Network Services Platform (NSP)
technology. The NSP window is the window from which you launch and display other
applications. The Layout Selector enables to open network layouts for viewing or editing.
The Navigator window opens automatically when you open a layout and shows a
hierarchical tree display of the resource groups in the opened layout.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Material Requirements General overview
DRAFT
....................................................................................................................................................................................................................................
WPS General Principles
WPS is a high-performance kernel which provides support to design and configure
Alcatel-Lucent networks. It offers a centralized view and configuration of all Network
Elements (NE) & parameters. WPS applications can be used for configuration at every
stage of a network management:
• Data engineering of a new network
• Data engineering for network expansion, densification
• Data engineering for network optimization
• Data engineering for upgrade provisioning
WPS manages configuration data coming from various sources. The file format used is
CM XML. Very large networks are supported in a workable and acceptable performances.
WPS supports multiple W-NMS Main Servers within a Regional Operational Center
(ROC).
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Material Requirements General overview
....................................................................................................................................................................................................................................
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
2 Integration preparation
2
Overview
Purpose
This chapter describes the precautions and preparations and provides a checklist of items
for verification.
Contents
Precautions and preparation 2-2
DRAFT
...................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration preparation Precautions and preparation
....................................................................................................................................................................................................................................
Precautions and preparation

Precautions
Check that all the prerequisites have been done and that the input parameters regarding
the dedicated site operations are correctly filled, refer to Appendix B, “Report Sheet”.
Preparations
It is strongly recommended that this method be read in its entirety before starting the
operations described in this document.
Checklist
Verify that the following items have been received and/or accomplished before
proceeding with the procedure.
• The Node B has been commissioned using Node B Commissioning Procedure, IM
24-6253.
• The RNC has been commissioned using Alcatel-Lucent 9370 RNC Commissioning
Method, IM 24-6223.
• The valid JRE already downloaded to access to the first GUI URL.
• An Exceed version running before the MDM start.
• The NSP GUI with access plug-in on OAM PC client have been installed and are
operational. At least one user should be created in the NSP administrator group, the
correct access rights have to be set to allow the user to create a layout.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
3 Integration procedures
3
Overview
Purpose
This chapter describes the procedures involved in the integration process.
Contents
RNC IN attributes checks 3-3

RNC-IN Parameters Checks 3-4
Session Manager: RNC declaration, validation, and activation 3-6
Session Creation for INode Declaration, Validation, and Activation 3-8
CNode Activation Session 3-16
Activation Session 3-17
Equipment Monitor checks 3-21
Equipment Monitor Checks 3-22
Iub, Iur Validation: ATM Interfaces 3-25
Iub, Iur Validation 3-26
Communication Tests 3-30
CS Tests 3-31
Voice Call on the Unlocked Cell 3-33
Video Call on the Unlocked Cell (Optional) 3-35
Dial-up Connection 3-36
IP Address Allocation 3-37
Ping the GGSN 3-38
Open a FTP Session (Optional) 3-40
DRAFT
Iux Validation: IP Interfaces 3-42
...................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Overview
....................................................................................................................................................................................................................................
Iux validation 3-43

Optional operations regarding layout operations and UTRAN checks 3-49
Attributes check with CAS commands 3-50
Layout operations 3-51
Opening a Layout in Edit Mode 3-52
Insert the NEs in the Layout 3-53
RNC Operations 3-56
RNC MIB Audit 3-58
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Overview
DRAFT
....................................................................................................................................................................................................................................
Overview
Purpose
The objective of this procedure is to check the attributes in RNC-IN.
Contents
RNC-IN Parameters Checks 3-4
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures RNC-IN Parameters Checks
....................................................................................................................................................................................................................................
RNC-IN Parameters Checks

Purpose
This procedure details the method to check the RNC-IN parameters.
Procedure
...................................................................................................................................................................................................
1 Note: On the commissioning procedure, the userId normally match with userId =
debug and password = debug, refer to Alcatel-Lucent 9370 RNC UA08.x
Commissioning, IM: 24-6223 .
In the RNC window, check the RNC-IN parameters, open a telnet session on the CP.
> d -p Ac userid/debug
Example:
==|===========================================
| INODE11 Ac Userid/DEBUG
==|===================(A)=====================
1|customerIdentifier 0
2|commandScope network
3|commandImpact debug
4|allowedAccess local remote fmip ftp
5|allowedOutAccess telnet
6|loginDirectory /
7|timeoutProtocol enabled
8|remoteAuth disabled
==|===========================================
The following attributes should be match with this parameters: allowedAccess > local
telnet fmip ftp, commandScope > network commandImpact > debug.
Note: If the attributes do not match, they should be changed. See “Attributes check
with CAS commands” (p. 3-50).
...................................................................................................................................................................................................
2 Verify RNC node name (RNC-IN has a node name which should not be empty).
> d -p mod
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures RNC-IN Parameters Checks
DRAFT
....................................................................................................................................................................................................................................
Result: Output example:
==|===================================================
| INODE11 Mod
==|========================(A)========================
1|nodeId 11
2|nodeName INODE11
3|namsId 257
4|regionId 0
4|regionId 0
5|nodePrefix 47FFFFFFFFFFFFFFFFFFFFFFFF
6|alternatePorsPrefixes 0 ""
==|===================================================
...................................................................................................................................................................................................
3 Note: The node name of the RNC must be the same during all steps of the RNC
Commissioning, Provisioning (under ex: WPS) and RNC Integration.
Verify the software release of the 9370 RNC, presence of RI7xxxx.
> d sw avl
avList = atmNetworking_RI70040, base_RI70040, genericUtilities_RI70040,

ip_RI70040, iRNC_RI70040, networking_RI70040, ss7_RI70040, wanDte_
RI70040, wirelessCommon_RI70040, secureShell_RI70040, apcBase_
RI7004081903, baseExt_RI7004081903, iRNCApc_RI7004081903, ss7Apc_
RI7004081903, cnp_RI7004081903, cRNCApc_RI7004081903, RNCCiph_
RI7004081903
ok 2010-04-14 13:45:43.48
...................................................................................................................................................................................................
4 Check that the current and commit view have the same name.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures RNC-IN Parameters Checks
....................................................................................................................................................................................................................................
> display pr
Prov
adminState = unlocked
operationalState = enabled
usageState = idle
provisioningActivity = none
activityProgress = n/a
standbyCpActivity = none
standbyCpActivityProgress = n/a
committedFileName = Export_StartupView.full.002
currentViewFileName = Export_StartupView.full.002
lastUsedFileName = Export_StartupView.full.003
provisioningSession =
provisioningUser = none
checkRequired = no
confirmRequired = no
editViewName = Export_StartupView.full.003
editViewAddedComponents = 0
editViewDeletedComponents = 0
editViewChangedComponents = 0
currentJournal = 0
journalDisabledReason = not disabled
...................................................................................................................................................................................................
5 Back-up the 9370 RNC provisioning view.
> start pr
PROV > copy pr
PROV > save -f(Initial_Prov_Name) pr
PROV> end pr
E...................................................................................................................................................................................................
N D O F S T E P S
Session Manager: RNC declaration, validation, and

activation
Overview
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
Session Manager: RNC declaration, validation, and
activation
....................................................................................................................................................................................................................................
Purpose
This procedure create, validate, and activate the RNC Workorder on NSP through Session
Manager.
Contents
Session Creation for INode Declaration, Validation, and Activation 3-8
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Session Creation for INode Declaration, Validation, and
Session Manager: RNC declaration, validation, and Activation
activation
....................................................................................................................................................................................................................................
Session Creation for INode Declaration, Validation, and

Activation
Purpose
The RNC Workorder (.xwo) and the reverse file must be available on a main server
dedicated directory. This procedure create, validate, and activate the RNC Workorder on
NSP
Procedure
...................................................................................................................................................................................................
1
1. Start web browser. In the URL field of the web browser, enter:
http://server's name:8080/NSP/ or
http://server's ip@:8080/NSP/
2. Run Launch to start the GUI. (If the J2SE Runtime Environment 5.0 update x is not
installed on the PC, download and install it by clicking on Download the Windows
32-bit JRE installer)
Note: In case of error message, open the hosts file located under c:/WINNT/system32/
drivers/etc using notepad and add the name and IP address and servername of
the WMS server as shown in the figure Hosts file.
Figure 3-1 Hosts file

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Session Creation for INode Declaration, Validation, and
DRAFT
activation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Log in as an admin user or user with the admin privileges. Click Accept on Warning
window and wait for the NSP load.
...................................................................................................................................................................................................
3 On the NSP, click Configuration > Session Manager and Create new session.
Figure 3-2 Session Creation
...................................................................................................................................................................................................
4 Select the appropriate Workorder, click Add to list and click Next to continue.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
activation
....................................................................................................................................................................................................................................
Figure 3-3 Workorder Selection
...................................................................................................................................................................................................
5 Wait until Analysis completed, on the left field, select steps to be excluded (if there are),
then click Launch.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
activation
....................................................................................................................................................................................................................................
Figure 3-4 Workorder Steps
...................................................................................................................................................................................................
6 Wait until Progress Status completed, check Error message and Warning message if
any.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
activation
....................................................................................................................................................................................................................................
Figure 3-5 Session Launched
...................................................................................................................................................................................................
7 In the main Sessions manager window, expand the Actions part to show the entire
actions panel. Select Validation.
Validation operation includes the execution of semantic checks and the execution of
service impact analysis to define the activation type.
Figure 3-6 Validation Step

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
activation
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
8 After the completion, check the summary session given by the Validation report.
Figure 3-7 Summary Session
...................................................................................................................................................................................................
9 Click on the Validation Report to see the status of the INode and verify the provisioning.
Figure 3-8 Validation Report
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
activation
....................................................................................................................................................................................................................................
Note: The INode is pre-activated, run the next step to activate it.
...................................................................................................................................................................................................
10 The activation operation applies the configuration changes on the node running
configuration and updates WMS running configuration accordingly.
On the Actions session launch the Activation step.
Figure 3-9 Activation Step
...................................................................................................................................................................................................
11 Once the Activation is done, check if the INode is staying in state successful in activation
part.
...................................................................................................................................................................................................
12 INode Layout Check

On NSP menu, select File > Network Layout and click the network to display the layout.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
activation
....................................................................................................................................................................................................................................
Figure 3-10 9370 RNC Layout
...................................................................................................................................................................................................
13 Right-click on the RNC, and select Configuration > Set NE's OAM Link Administrative
State. To unlock, select the NE and click the Unlock button.
Figure 3-11 Administrative State: Unlock Window
Note: The PP (INode) is completely integrated on the network.

E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
....................................................................................................................................................................................................................................
Overview
Purpose
The procedure aim is to execute the activation and validation operation for the CNode.
Contents
Activation Session 3-17

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Activation Session
DRAFT
....................................................................................................................................................................................................................................
Activation Session
Purpose
The purpose of this procedure is to describe steps to activate CNode.
Procedure
...................................................................................................................................................................................................
1 On the layout view, select the RNC and launch a Session Manager for running the CNode
pre-activate function.
Figure 3-12 RNC Pre Activation
...................................................................................................................................................................................................
2 Once this action is completed, run the Activate function to build the RNC (CNode).
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Activation Session
....................................................................................................................................................................................................................................
Figure 3-13 RNC Activation
...................................................................................................................................................................................................
3 During this action, the Command Manager could display the course of operations.
Figure 3-14 Command Manager

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Activation Session
DRAFT
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Once the CNode Activation is successful, the RNC is totally integrated on the network.
The Session Manager display the successful operations for the NE.
The activation operation consists in switching the pending configuration of the node to its
running configuration (MIB passive to MIB active).
Note: The activation operation run the build action for the RNC which has been
locked.
Figure 3-15 RNC Session Manager
...................................................................................................................................................................................................
5 The action on the Summary Window displays the Activation Status for the CNode and
INode.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Activation Session
....................................................................................................................................................................................................................................
Figure 3-16 Summary RNC and PP(INode) Activated
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
....................................................................................................................................................................................................................................
Overview
Purpose
The procedure aim is to execute the RNC object monitoring.
Contents
Equipment Monitor Checks 3-22
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Equipment Monitor Checks
....................................................................................................................................................................................................................................
Equipment Monitor Checks

Purpose
The purpose of this procedure is to describe the steps involved in Equipment Monitor
checks.
Procedure
...................................................................................................................................................................................................
1
• Right-click the RNC and select Equipment Monitor, a new window appears.
Note: The Equipment Monitor allows to display the CNode (left tree) and INode
(right tree) characteristics and alarms.
Figure 3-17 RNC Equipment Monitor

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Equipment Monitor Checks
DRAFT
....................................................................................................................................................................................................................................
Figure 3-18 RNC INode Equipment Monitor
...................................................................................................................................................................................................
2 For the CNode and the INode, you can display the alarms for each element either by
clicking it on the left view, or by clicking directly on the element on the right view.
Figure 3-19 Access to "Alarm Command"
...................................................................................................................................................................................................
DRAFT
3 The Alarm Manager Window appears.

....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Equipment Monitor Checks
....................................................................................................................................................................................................................................
Figure 3-20 Alarm Manager Window
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
....................................................................................................................................................................................................................................
Overview
Purpose
The objective of this procedure is to validate the Iux links on the RNC-IN side.
Contents
Iub, Iur Validation 3-26
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Iub, Iur Validation
....................................................................................................................................................................................................................................
Iub, Iur Validation

Purpose
The objective of this procedure is to validate the Iux links on the RNC-IN side.
Procedure
...................................................................................................................................................................................................
1 On the RNC-IN, check that the ATM interface is in an operational state.

> d atmif/*
d atmif/*
AtmIf/*
Use -noTabular to see the many hidden attributes.
+=====+-----+----+-----+----------+-----
|AtmIf|osiAd|osiO|osiUs|txCellMemo|txCel
| | min |per | age | ryUsage |lCcSt
| | | | | cells| ate
+=====+-----+----+-----+----------+-----
| 800|unlck|ena |activ| 0| 3
| 813|unlck|dis |idle | 0| 3
ok 2010-04-16 13:53:55.75
Note: ATM interface should be unlocked, enabled, and active.

...................................................................................................................................................................................................
2 Iub:
For each concerned Node B, type the following in the RNC window:
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Iub, Iur Validation
DRAFT
....................................................................................................................................................................................................................................
> d atmif/<interface> vcc/* rxcell, txcell
Where <Interface> is the atmif number associated with each Node B

Output example for Interface=800
IN204> d atmif/800 vcc/* rxcell, txcell
Context: .. -prov Tm Vcd Nep
| IN204 Atm IN204 Atm IN204 Atm IN204 Atm IN204 Atm IN204 Atm
| If/800 If/800 If/800 If/800 If/800 If/800
| Vcc/0.33 Vcc/0.34 Vcc/0.35 Vcc/0.36 Vcc/0.50 Vcc/
0.51
==|=======(A)========(B)========(C)========(D)========(E)========(F)==
==|=======(A)========(B)========(C)========(D)========(E)========
(F)========
1|rxCell 1057488 984078 242211 243343 3558824 2957643
2|txCell 1416298 999341 242188 242815 3128353 2957694
==|===================================================================
IN204> d atmif/800 vcc/* rxcell, txcell
==|===================================================================
| IN204 Atm IN204 Atm IN204 Atm IN204 Atm IN204 Atm IN204 Atm
| If/800 If/800 If/800 If/800 If/800 If/800
| Vcc/0.33 Vcc/0.34 Vcc/0.35 Vcc/0.36 Vcc/0.50 Vcc/
0.51
==|=======(A)========(B)========(C)========(D)========(E)========(F)===
1|rxCell 1057492 984082 242215 243347 3558828 2957647
2|txCell 1416302 999345 242192 242819 3128357 2957698
==|====================================================================
Note: The command displays for every ATM link the number of cells transmitted and
received on all the concerned VCCs. The number of cells transmitted and received
should be increasing for the concerned Node B.
...................................................................................................................................................................................................
3 Repeat this action for each Node B.

...................................................................................................................................................................................................
4 Note: “Integration report sheet” (p. B-2), search the Aal2If regarding the Iur.
In our example in, the concerned aal2If regarding the Iur link is the Aal2If 350.
Check that the Iuxfs on the local and on the remote RNC-IN are unblocked.
> d -o -c Aal2If/350 Path/*
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Iub, Iur Validation
....................................................................................................................................................................................................................................
==|=====================================================
| IN204 Aal2If/350 Path/4433-4435
==|=====================(A)=============================
1|adminState unlocked
2|operationalState enabled
3|usageState active
4|remoteBlockingStatus unblocked
5|localBlockingStatus unblocked
Note: The remoteBlockingStatus for remote RNC and localBlockingStatus for

local RNC should be in an unblocked state.
...................................................................................................................................................................................................
5 Check that the ATM interface between each RNC-IN is in an operational state. This ATM
interface should be unlocked, enabled, active.
> d -o -c atmif/*
Atmif port 807 concerns the Iur link.
d atmif/*
AtmIf/*
Use -noTabular to see the many hidden attributes.
+=====+-----+----+-----+----------+-----
|AtmIf|osiAd|osiO|osiUs|txCellMemo|txCel
| | min |per | age | ryUsage |lCcSt
| | | | | cells| ate
+=====+-----+----+-----+----------+-----
| 807|unlck|dis |activ| 0| 3
ok 2010-04-21 13:53:55.75
...................................................................................................................................................................................................
6 Repeat this operation for the other RNC-IN.

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Iub, Iur Validation
DRAFT
....................................................................................................................................................................................................................................
Figure 3-21 Iur Link
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Communication Tests
....................................................................................................................................................................................................................................
Communication Tests
Overview
Purpose
The objective of this chapter is to check the UTRAN integration and capabilities.
Important: For all these communication tests CS and PS, the ON SITE engineer should
go away from the BTS site (100 meters if possible), in the area covered by the sector to
test (FDD CELL).
Contents
CS Tests 3-31
Voice Call on the Unlocked Cell 3-33
Video Call on the Unlocked Cell (Optional) 3-35
Dial-up Connection 3-36
IP Address Allocation 3-37
Ping the GGSN 3-38
Open a FTP Session (Optional) 3-40
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures CS Tests
DRAFT
Communication Tests
....................................................................................................................................................................................................................................
CS Tests
Voice Call Tests
The objective of these procedures is to lock all the untested cells in order to make a voice
call on the unlocked cells. These procedures should be repeated for each cell and for each
frequency to be tested.
Procedure
...................................................................................................................................................................................................
1 Check that the ON SITE engineer is well positioned in the area covered by the sector to
test.
Refer to Table B-4, “Antennae Positions” (p. B-2) for the azimuth of the concerned sector.
...................................................................................................................................................................................................
2 Lock the cells that are not tested. Right-click the concerned RNC, select Equipment
Monitor. A new window appears, select the concerned Node B, then on the concerned
FDD Cell, right-click FDD Cell and select Configuration > Set Administrative State.
Figure 3-22 FDD Cells
...................................................................................................................................................................................................
3 The FDDCell window appears in an UNLOCKED state. Select the object and click Lock.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures CS Tests
Communication Tests
....................................................................................................................................................................................................................................
Figure 3-23 FDD Cell Administrative State
...................................................................................................................................................................................................
4 The lock command opens the Command Manager. In the Command Manager, click log
and check that all the tasks perform normally.
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Voice Call on the Unlocked Cell
DRAFT
Communication Tests
....................................................................................................................................................................................................................................
Voice Call on the Unlocked Cell

Purpose
The objective of this procedure is to make a voice call on the unlocked cells
Procedure
...................................................................................................................................................................................................
1 The on-site engineer is well positioned in the area covered by the sector to test. All the
untested cells are locked, refer to Table B-4, “Antennae Positions” (p. B-2) for the
azimuth of the concerned sector.
...................................................................................................................................................................................................
2 Once the untested cells are locked, the On-site engineer should make one call to the OMC
via the PSTN using the 3G mobile, see Figure 3-25, “Voice Call Test” (p. 3-34). In our
example, the FDD CELL 1 is unlocked, the FDD CELL 0 and 2 are locked.
...................................................................................................................................................................................................
3 Once the call has been performed on the unlocked cell, ask the on-site engineer to move
to another area in order to test another sector.
...................................................................................................................................................................................................
4 Repeat “CS Tests” (p. 3-31) and “Voice Call on the Unlocked Cell” (p. 3-33), for each
cell to be tested and for each frequency.
Once all the sectors and frequencies have been tested, note the results in Table B-3,
“Communication Tests” (p. B-2).
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Voice Call on the Unlocked Cell
Communication Tests
....................................................................................................................................................................................................................................
Figure 3-25 Voice Call Test
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Video Call on the Unlocked Cell (Optional)
DRAFT
Communication Tests
....................................................................................................................................................................................................................................
Video Call on the Unlocked Cell (Optional)

Purpose
Important! The video streaming test is recommended to be done only on the first cell
of a given RNC. Once a video call has been verified on a given RNC, it validates the
function of all its other cells located on the other Node Bs.
Execute “CS Tests” (p. 3-31) to lock untested cells.
The objective of this procedure is to make a video call between the 2 mobiles located on
the unlocked cell(s).
Procedure
...................................................................................................................................................................................................
1 The 2 site engineers are well positioned in the area covered by the sector to test. All the
untested cells are locked, refer to Table B-4, “Antennae Positions” (p. B-2) for the
azimuth of the concerned sector.
...................................................................................................................................................................................................
2 Once the untested cells are locked, one engineer should call the other via a video call. The
video call quality is evaluated on both sides.
Figure 3-26 Video Call Test
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Dial-up Connection
Communication Tests
....................................................................................................................................................................................................................................
Dial-up Connection
Purpose
Important! The PS tests (ping GGSN and files transfer) are recommended to be done
only on the first cell of a given RNC. Once a PS call has been verified on a given
RNC, it validates the PS function of all its other cells located on the other Node BS.
Consequently, this test is not required systematically: time consuming and require a
PC on site.
The objective of this procedure is to launch a dial-up connection.
Important! The dial-up connection should be configured and its parameters checked
using the “Dial-up Connection” (p. 3-36).
Procedure
...................................................................................................................................................................................................
1 Open the dial-up connection window, once the dial-up connection window is open, enter
the password and click on Dial. This action opens a connection between the PC and the
UTRAN. The mobile is now used as a modem
Figure 3-27 Dial-up Connection
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures IP Address Allocation
DRAFT
Communication Tests
....................................................................................................................................................................................................................................
IP Address Allocation
Purpose
The objective of this procedure is to check that the network sent a dedicated IP address.
Procedure
...................................................................................................................................................................................................
1
• Click on Start, then Run. In the Run window, type cmd and OK to open the command
prompt window and type ipconfig inside this one, refer to Figure 3-28, “IP address
Allocation” (p. 3-37).
...................................................................................................................................................................................................
2
• Check that the UTRAN has allocated an IP address number. refer to Figure 3-28, “IP
address Allocation” (p. 3-37) It validates the PDP context activation.
Figure 3-28 IP address Allocation
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Ping the GGSN
Communication Tests
....................................................................................................................................................................................................................................
Ping the GGSN

Purpose
The objective of this procedure is to make a ping on the GGSN in order to validate the PS
way.
Important! The ON-SITE engineer should make only one GGSN ping per RNC
located in the UTRAN.
Procedure
...................................................................................................................................................................................................
1 The on-site engineer is well positioned in the area covered by the sector to test.
...................................................................................................................................................................................................
2 The on-site engineer brings the dial up connection using the Figure 3-27, “Dial-up
Connection” (p. 3-36).
Once the negotiation is over (it can take around one minute), the connection should be
established between the PC (connected to the UMTS mobile) and the UMTS network, see
Figure 3-29, “Ping Way” (p. 3-38).
Figure 3-29 Ping Way

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Ping the GGSN
DRAFT
Communication Tests
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Once the call has been established, the on-site engineer should ping the GGSN via its PC.
In our example, the GGSN IP address is 47.164.96.112, see Figure 3-30, “Ping
Command” (p. 3-39).
Figure 3-30 Ping Command
...................................................................................................................................................................................................
4 The ping test between the PC and the GGSN should be OK. This ping test is sufficient to
validate the PS function. Each ping command should return with a message indicating
that the entity is alive, refer to Figure 3-31, “Ping Message” (p. 3-39).
Once the Ping has been completed, note the results in Table B-3, “Communication Tests”
(p. B-2).
Figure 3-31 Ping Message
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Open a FTP Session (Optional)
Communication Tests
....................................................................................................................................................................................................................................
Open a FTP Session (Optional)

Purpose
The objective of this procedure is to download and to send files via a FTP Session in
order to validate a transfer file on the uplink and downlink channels of the PS way.
Important!
• The ON-SITE engineer should make only one uplink and downlink file transfer
per RNC located in the UTRAN.
• The FTP server should be installed and operational.
• The Sim card should be declared in the HLR, it is preferable that the SIM card
have all the services declared.
Procedure
...................................................................................................................................................................................................
1 On the test PC, type Start then Run, execute cmd command, this action opens a new
window.
Once the window is open, ping the FTP server. Type Ping IP@ FTP server
The FTP server should be reach via a ping session.
...................................................................................................................................................................................................
2 Once you ping the FTP server, open a FTP session on it, type: ftp IP@ FTP server,
then once connected enter your login and password.
Once you are logged in, type the following command: dir, see Figure 3-32, “FTP
Connection” (p. 3-40).
Figure 3-32 FTP Connection

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Open a FTP Session (Optional)
DRAFT
Communication Tests
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Download a concerned file type: hash, then get name of file, see Figure 3-33, “Downlink
Transfer” (p. 3-41).
Check the downlink rate conforms to the one expected.
Figure 3-33 Downlink Transfer
...................................................................................................................................................................................................
4 Transfer a concerned file, type the following command: put name of file, see Figure
3-34, “Uplink Transfer” (p. 3-41).
Check the uplink rate conforms to the one expected.
Figure 3-34 Uplink Transfer
...................................................................................................................................................................................................
5 Once the transfer file has been completed, note the results in Table B-3, “Communication
Tests” (p. B-2) and close the window. Refer to Appendix B, “Report Sheet”.
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
....................................................................................................................................................................................................................................
Overview
Purpose
The objective of this procedure is to validate the Iux links on the RNC-IN side: IP
interfaces.
Contents
Iux validation 3-43

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Iux validation
DRAFT
....................................................................................................................................................................................................................................
Iux validation
Purpose
The purpose of this procedure is to describe the steps involved in validation of Iux, an IP
interface.
Procedure
...................................................................................................................................................................................................
1 Check the IP route to the NodeBs.

• From the RNC ping the next hop router vlan ip addresses:
> ping -ip(<Facing_Router_Next_HopIP>)-trace vr/x ip icmp
Output example:
ping -ip(10.69.1.18) -trace vr/x ip icmp

Note: vr/x refers to the virtual router assigned for the interface.
• From the RNC ping the NodeB IP address:
> ping -ip(iBTS_IP_address) -trace vr/x ip icmp
Output example:

...................................................................................................................................................................................................
2 Check the PDR

Note: Instead of the port lock command, it is possible to test PDR using: optical fiber
disconnection or active gigaEthernet card reset (ca/14 or ca/15)
To test the PDR, it is simpler to display the following nexthop table than the actual
routing table. During the active route change, only alarms for the GigaEthernet port being
locked down (or fiber disconnection) are generated in the telnet session.
PS call traffic impact during that PDR test should be limited to:
• a lost ping
• FTP data transfer impact (DuMeter application for instance). Control plane SCTP
associations remain up and running (no alarm is generated from them during PDR
testing).
> d Vr/1 Ip Static Route/* nh/*
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Iux validation
....................................................................................................................................................................................................................................
Output example:
Vr/1 Ip Static Route/*,*,* Nh/*

+===============+===============+===+===============+-----+----+-----+-
| addr | mask |tos| Nh |osiAd|osiO|osiUs| hbS
| | | | | min |per | age |
+===============+===============+===+===============+-----+----+
|0.0.0.0 |0.0.0.0 | 0|10.12.1.18 |unlck|ena |activ|up
|0.0.0.0 |0.0.0.0 | 0|10.12.1.22 |unlck|ena |idle |up
|172.24.4.0 |255.255.255.192| 0|10.11.12.2 |unlck|ena
|activ|disabl
ok 2010-05-02 15:40:29.30
• Lock lp/14 eth/0.

> d Vr/1 Ip Static Route/* nh/*
Output example:
+===============+===============+===+===============+-----+----+-----+-
| addr | mask |tos| Nh |osiAd|osiO|osiUs| hbS
| | | | | min |per | age |
+===============+===============+===+===============+-----+----+-----+-
|0.0.0.0 |0.0.0.0 | 0|10.12.1.18 |unlck|ena |activ|up
|0.0.0.0 |0.0.0.0 | 0|10.12.1.22 |unlck|ena |idle |up
|172.24.4.0 |255.255.255.192| 0|10.11.12.2 |unlck|ena
|activ|disabl
ok 2010-05-02 15:46:50.09
...................................................................................................................................................................................................
3 Iur
Confirm IuR over IP is up on both RNCs.
• Check if SCTP is up on both RNCs : all of the paths you created should be active in
RNC command.
> d ss7 m3ua/1 pmp/* assoc/* path/*
• Confirm if RNCs can ping each others Control Plane.
Note: You can not ping sctp endpoints, only the vr pp ip address is externally
routable.
Example:
> ping -ip(10.69.4.46) –src(10.32.4.46) –trace vr/6 ip
icmp > ping -ip(10.32.4.46) –src(10.69.4.46) –trace vr/6 ip
icmp
• Confirm RNCs can ping each others User Plane.
DRAFT
Example:
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
....................................................................................................................................................................................................................................
> ping -ip(10.69.4.62) -src(10.32.4.62) -trace vr/6 ip
icmp > ping -ip(10.32.4.62) –src(10.69.4.62) –trace vr/6
ip icmp
Note: If any of the above checks fail carry out the following:
– Confirm 1st RNC can ping 7750 vlans – if not, possibly fibers are crossed, or
provisioning is crossed.
Example:
> ping -ip(10.33.4.2) –trace vr/6 ip icmp > ping -
ip(10.33.4.6) –trace vr/6 ip icmp
– Confirm 2nd RNC can ping 7750 vlans – if not, possibly fibers are crossed, or
provisioning is crossed.
Example:
> ping -ip(10.69.4.2) –trace vr/6 ip icmp > ping -
ip(10.69.4.6) –trace vr/6 ip icmp
– Confirm 7750s can ping both RNCs IuRoIP cplane and uplane (perform on both
7750-1 and 7750-2 … using router 4 in this example if segmented VR config on
the RNC).
Example:
> ping 10.32.4.46 router 4 > ping 10.69.4.46 router 4 >
ping 10.32.4.62 router 4 > ping 10.69.4.62 router 4
Note: If that fails, probably missing a static route on the 7750.
– Lock the primary GigE path from RNC#1 to 7750s. i.e. on RNC232.
> lock lp/14 eth/2
– Repeat steps 1-3 to confirm IuRoIP still works using RNC232 protection path.
Lock the primary GigE path from RNC#2 to 7750s. i.e. on RNC4369.
Example:
> lock lp/14 eth/0
– Repeat steps 1-3 to confirm IuRoIP still works using RNC4369 & RNC232
protection path.
Unlock the primary GigE path from RNC#1 to 7750s. i.e. on RNC232.
Example:
> unlock lp/14 eth/2
– Repeat steps 1-3 to confirm IuRoIP still works using only RNC4369 protection
path.
Unlock the primary GigE path from RNC#2 to 7750s. i.e. on RNC4369.
Example:
> unlock lp/14 eth/0
...................................................................................................................................................................................................
4 IuCS
• Check if RAAP is up: check CsCoreNetworkAccess/<instance#> status on SP
GUI.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
....................................................................................................................................................................................................................................
Check if M3UA is up.
> d ss7 m3ua/1*
Output Example
SI_IN2> d ss7 m3ua/1*

==|===================================
| SI_IN2 Ss7 M3ua/1
==|=================(A)===============
3|usageState active
4|m3uaMsgTx 3097143
5|m3uaDataMsgTx 55
6|m3uaMsgRx 3097865
7|m3uaDataMsgRx 44
==|===================================
• Check if the SCTP associations are up.In the RNC window:

> d ss7 m3ua/1 pmp/* assoc/*
• Display status of SCTP association path.
> d ss7 m3ua/1 pmp/* assoc/* path/*
• Check that the RNC ping next hop router vlan ip addresses.
> ping -ip(<Facing_Router_Next_HopIP>)-trace VR/x ip icmp
Example:
> ping -ip(10.69.1.18) -trace VR/x ip icmp > ping -
ip(10.69.1.22) -trace VR/x ip icmp
• Check that the RNC ping MSC control plane.
> ping -ip(MSC_CPlane_IP) -src(<SS7_CPlane ProtocolPort_IP>
) - trace VR/x ip icmp
Example:
> ping -ip(10.0.1.2) -src(10.69.1.14) -trace VR/x ip icmp >
ping -ip(10.0.1.3) -src(10.69.1.14) -trace VR/x ip icmp
• Check that the RNC ping MSC user plane.In the RNC window:
> ping -ip (<MSC_IP1_Uplane>
Example:
> ping -ip(172.24.4.47) -src(172.253.69.126) -trace VR/x ip
icmp > ping -ip(172.24.4.54) -src(172.253.69.126) -trace VR/
x ip icmp
• List the provisioned peerIpAddresses.
> d -p ss7 m3ua/1 pmp/*
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
....................................................................................................................................................................................................................................
Example:
==|=============================================================
| pmpLinkToPmes peerType peerIpAddress
peerSctpPort umtsInterfacesForPeerEp
==|========================(1)==============(2)======(3)===============
==========(4)==========(5)=====================
A|SI_IN2 Ss7 M3ua/1 PMP/0 Ss7 M3ua/1 PME/0 ipsp
172.24.71.166,172.24.72.166 2905
B|SI_IN2 Ss7 M3ua/1 PMP/1 Ss7 M3ua/1 PME/0 ipsp
172.24.72.167,172.24.71.167 2905
C|SI_IN2 Ss7 M3ua/1 PMP/2 Ss7 M3ua/1 PME/1 ipsp
172.23.71.166,172.23.72.166 2905
D|SI_IN2 Ss7 M3ua/1 PMP/3 Ss7 M3ua/1 PME/1 ipsp
172.23.71.167,172.23.72.167 2905
E|SI_IN2 Ss7 M3ua/1 PMP/4 Ss7 M3ua/1 PME/2 ipsp
10.88.88.87,10.88.88.103 2905 Iucs/2
F|SI_IN2 Ss7 M3ua/1 PMP/5 Ss7 M3ua/1 PME/2 ipsp
10.88.88.88,10.88.88.104 2905 Iucs/2
==|=============================================================
...................................................................................................................................................................................................
5 IuPS
• Check that the RANAP is up: check PsCoreNetworkAccess/<instance#> status
on NSP GUI.
Check if M3UA is up.
> d ss7 m3ua/1*
Output Example:
SI_IN2> d ss7 m3ua/1*

3|usageState active
4|m3uaMsgTx 3104819
5|m3uaDataMsgTx 55
6|m3uaMsgRx 3105541
7|m3uaDataMsgRx 44
==|===================================
• Check if the SCTP associations are up.

> d ss7 m3ua/1 pmp/* assoc/*
• Check if the RNC ping next hop router vlan ip addresses.
DRAFT
> ping -ip(<Facing_Router_Next_HopIP>)-trace vr/1 ip icmp

....................................................................................................................................................................................................................................
30-3006 UA08.1
....................................................................................................................................................................................................................................
Example:
> ping -ip(10.69.1.18) -trace vr/1 ip icmp > ping -
ip(10.69.1.22) -trace vr/1 ip icmp
• Check that the RNC ping SGSN control plane.
> ping -ip(SGSN_CPlane_IP) -src(<SS7_CPlane ProtocolPort_IP>
) - trace vr/1 ip icmp
Example:
> ping -ip(10.0.1.2) -src(10.69.1.14) -trace vr/1 ip icmp >
ping -ip(10.0.1.3) -src(10.69.1.14) -trace vr/1 ip icmp
• Check if the RNC ping SGSN user plane.
> ping -ip (<SGSN_IP1_Uplane>
Example
> ping -ip(172.24.4.47) -src(172.253.69.126) -trace vr/1 ip
icmp > ping -ip(172.24.4.54) -src(172.253.69.126) -trace vr/1
ip icmp
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
Optional operations regarding layout operations and UTRAN
checks
....................................................................................................................................................................................................................................
Optional operations regarding layout operations

and UTRAN checks
Overview
Purpose
The objective of this chapter is to describe the procedures regarding layout operations and
UTRAN checks.
Contents
Attributes check with CAS commands 3-50

Layout operations 3-51
Opening a Layout in Edit Mode 3-52
Insert the NEs in the Layout 3-53
RNC Operations 3-56
RNC MIB Audit 3-58
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Attributes check with CAS commands
checks
....................................................................................................................................................................................................................................
Attributes check with CAS commands

Purpose
This procedure applies only when the RNC-IN attributes are not correct. Refer to
Appendix B, “Report Sheet” in order to know the RNC's attributes.
Procedure - CAS Commands (Optional)

...................................................................................................................................................................................................
1 Open a Telnet session on the RNC-IN.

...................................................................................................................................................................................................
2 In the RNC Telnet window (add debug & mdmadmin users):

> d -p ac userid/*
> start pr
PROV> add ac userid/debug

PROV> set ac userid/debug password debug, commandscope network
PROV> set ac userid/debug allowedaccess local telnet fmip ftp
PROV> set ac userid/debug commandImpact systemAdministration
PROV> ch prov
PROV> act prov
PROV> confirm prov
PROV> add ac userid/mdmadmin
PROV> set ac userid/mdmadmin password mdmadmin, commandscope
network
PROV> set ac userid/mdmadmin allowedaccess local telnet fmip ftp
PROV> set ac userid/mdmadmin commandImpact systemAdministration
PROV> ch prov
PROV> act prov
PROV> confirm prov
PROV > save -f(new_view_name) pr
PROV> commit pr
PROV> end pr
...................................................................................................................................................................................................
3 Exit Telnet session.

E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Layout operations
DRAFT
checks
....................................................................................................................................................................................................................................
Layout operations
Purpose
The objective of this procedure is to create a new layout if it was not already done.
This procedure applies only if the concerned layout was not already created.
Layout Creation (Optional)

...................................................................................................................................................................................................
1 On the NSP menu, click File > Select Network Layout.

This action opens the Layout Selector.
...................................................................................................................................................................................................
2 Click Layout Management, click New. Enter the layout name and click OK.
Figure 3-35 Layout Selector
Result: The new layout appears in the Layout selector window.

E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Opening a Layout in Edit Mode
checks
....................................................................................................................................................................................................................................
Opening a Layout in Edit Mode

Purpose
The objective of this procedure is to open the new or existing layout in edit mode and
then to move the concerned NEs inside it
Procedure
...................................................................................................................................................................................................
1 In the NSP window, click File > Select Network Layout.

...................................................................................................................................................................................................
2 In Figure 3-36, “Edit Mode” (p. 3-52), select the concerned layout, then click Edit. This
action opens the navigator window.
In the navigator window, double-click the concerned layout, the layout is now open in
edit mode, refer to Figure 3-36, “Edit Mode” (p. 3-52).
Figure 3-36 Edit Mode
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Insert the NEs in the Layout
DRAFT
checks
....................................................................................................................................................................................................................................
Insert the NEs in the Layout

Purpose
The objective of this procedure is to insert the concerned NEs in the layout and to save
this new layout.
Procedure
...................................................................................................................................................................................................
1 Open the layout by double-clicking on the layout name, once the Navigator Layout is
open, right-click on NE store and select Find.
Figure 3-37 NE Find
...................................................................................................................................................................................................
2 Select the NE(s), click Move To. Select the layout's name that appears.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures Insert the NEs in the Layout
checks
....................................................................................................................................................................................................................................
Figure 3-38 NE Store
...................................................................................................................................................................................................
3 In the NE store, check the BTS(s) status pass from NE Store to MOVED in the Containing
Group column.
Figure 3-39 NE Store

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures Insert the NEs in the Layout
DRAFT
checks
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 In the File menu of the NSP, click Save Network Layout > Close Network Layout.
Figure 3-40 File Menu
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures RNC Operations
checks
....................................................................................................................................................................................................................................
RNC Operations
Purpose
The objective for this procedure is to change the administrative state of the RNC.
Procedure - Changing the RNC’s Administrative State (optional)

...................................................................................................................................................................................................
1 Right-click the concerned RNC. Select Configuration > Set NEs OAM Link
Administrative State.
Figure 3-41 OAM Link
...................................................................................................................................................................................................
2 Once the NE administrative state window is open, select the NE by right-clicking on it

and choose Unlock. Check that the RNC status passes from LOCKED to UNLOCKED.
Figure 3-42 NE's Administrative State

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures RNC Operations
DRAFT
checks
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 The color of the concerned NE turns RED as shown inFigure 3-43, “RNC Status”
(p. 3-57).
Figure 3-43 RNC Status
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures RNC MIB Audit
checks
....................................................................................................................................................................................................................................
RNC MIB Audit

Purpose
The objective of this procedure is to check the MIB's consistency.
Procedure
...................................................................................................................................................................................................
1 Right-click the concerned RNC. Select Configuration > MIB > Audit. This action opens a
new window as shown in Figure 3-45, “Action Window” (p. 3-58).
Figure 3-44 RNC Object Audit
...................................................................................................................................................................................................
2 Select the concerned NE and click Audit Now. The Command Manager window is
opened.
Figure 3-45 Action Window

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
Integration procedures RNC MIB Audit
DRAFT
checks
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 In the Command Manager, check if the audit performs normally.
...................................................................................................................................................................................................
4 Once the audit operation is completed, click Logs tab.
Figure 3-47 Audit Logs
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT Integration procedures RNC MIB Audit
checks
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 In the Logs as shown in Figure 3-47, “Audit Logs” (p. 3-59), check if the following
message appears: "Verdict consistent "
...................................................................................................................................................................................................
6 In case if any issues, perform the Rebuild action as shown inFigure 3-48, “MIB Rebuild”
(p. 3-60).
Figure 3-48 MIB Rebuild
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
4 RNC Counters
4
Overview
Purpose
This chapter details you on the list of RNC counters and lists and details the procedure to
check if the counters are present in the WMS server or not.
Contents
RNC Counters 4-2

Enabling the RNC Counters 4-3
DRAFT
...................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT RNC Counters Overview
RNC Counters
....................................................................................................................................................................................................................................
RNC Counters
Overview
Purpose
The objective of this section is to describe the RNC counters and the procedure to enable
it.
Filters and Lists

The design of the RNC 9370 allows for a large number of counters, however, only certain
counters are used or required by different customers. Therefore, a specific counter list is
used to identify the counters that the RNC needs to keep. The specific counters which are
enabled on a given RNC are provided as part of a counter list. Each RNC can have a
different list, but in general it is expected that all RNCs for a given customer will be set
identically.
Counter Filters
To limit the number of counters that need to be enabled and disabled, a counter filter file
contains a list of families and counters that should be filtered when generating the generic
load list of counters. This file impacts the counters that are retrieved when exporting a
counter list.
Counter Lists
The counters lists on the RNC are defined by a semi-colon delimited CSV file that
identifies each of the counters and whether the individual counter is enabled or not on that
particular RNC. The WMS uses a set of scripts which allow the list to be imported,
validated, and exported to specified RNCs
Contents
Enabling the RNC Counters 4-3

DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
RNC Counters Enabling the RNC Counters
DRAFT
RNC Counters
....................................................................................................................................................................................................................................
Enabling the RNC Counters

Purpose
The following provides a set of steps to ensure that the counters are enabled. It consists of
two main parts. The verification/change of the counter filter file on the WMS and the
verification/import/export of the counter list to the RNC, note that the filter applied is
AT&T example.
Procedure
...................................................................................................................................................................................................
1 Perform the following to check if the correct counter file is already located on the WMS
server:
• Connect to the WMS Main server.
• Change directories to the location of the counter list file and list the current files.
cd /opt/nortel/data/counterlist/import
ls -l
...................................................................................................................................................................................................
2 Look through the returned list of files. If the filename ATT_rnc_06_00_00.csv is seen,
then the correct counter file is already available. In this case, log out of the WMS server,
and skip to the ACTIVATE THE RNC COUNTER LIST step. If the filename above is not
seen, continue on the followings steps to check the current counter filter file.
...................................................................................................................................................................................................
3
• Change directories to the location of the counter filter file.
cd /opt/nortel/data/custom/counterlists
• Check to see if there are any individual counters listed in the filter configuration file.
cat filters.cfg
If there is any data (numbers) listed between the [counters] and [/counters] lines
then the filter file must be modified; go on to the Modify Counter Filter File step.If there
is NO data between the two tags, then skip to the ACTIVATE THE RNC COUNTER LIST
step.
Example of a filter file that must be modified:
$ cat filters.cfg
[families]
softSofterHandovers
statistic
DRAFT
cdmaHandover
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT RNC Counters Enabling the RNC Counters
RNC Counters
....................................................................................................................................................................................................................................
rabRbMgmtKorea
handoversKorea
userPlaneKorea
[/families]
[counters]
57
58
59
60
61
.
.
2813
2814
/counters]
...................................................................................................................................................................................................
4 Modify Counter Filter File: Perform the following steps to modify the counter filter file.
Note: This step is only need to be executed if the previous check requires it. The file
will only need to be modified once per WMS.
• Edit the counter filter file.
vi /opt/nortel/data/custom/counterlists/filters.cfg
• In the file, remove all number entries which are between the [counters] and
[/counters] tags. When finished, the file should look like the following:
[families]
softSofterHandovers
statistic
cdmaHandover
rabRbMgmtKorea
handoversKorea
userPlaneKorea
[/families]
[counters]
[/counters]
• Save the modified file.
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
RNC Counters Enabling the RNC Counters
DRAFT
RNC Counters
....................................................................................................................................................................................................................................
Note: Do not modify any of the data located between the [families] and [/families]
tags.
...................................................................................................................................................................................................
5 Obtain the RNC Counter List File

This step can be used to obtain the default UA8.0 counter file with all counters which are
not filtered active. The procedures only need to be performed if the counter file is not
already located on the WMS as determined by the previous steps.
Perform the following to obtain the default counter list.
Note: Only one copy of the AT&T counter list file is required per WMS ROC. Once
the file is located on the machine, it can be used by any of the connected RNCs.
• From a client machine start the NSP GUI client and log in.
• From the Configuration menu, select Wireless Internet Command Language
(WICL).
• In the WICL window, enter the following command:
PM exportCounterList –type RNC -utranRelease 06_00_00
• Wait for the command to complete successfully and note the full filename of the
exported counterlist. This filename will be required during the import.
Example output:
Export counter list successfully!
dfs:/counterlists/export/export_6061_20080618_095848_rnc_06_
00_00.csv
• Connect to the WMS Main server.
• Change directories to the location of the exported counter list file.
cd /opt/nortel/data/counterlists/export
• Copy the exported file to the import directory.
cp <file> ../import/ATT_rnc_06_00_00.csv
Where <file> is the filename of the exported counterlist.
• Log out of the WMS server.
...................................................................................................................................................................................................
6 RNC Counter Activation

• From a client machine start the NSP GUI client and log in.
• From the Configuration menu, select Wireless Internet Command Language.
• In the WICL window, enter the following command on a single line:
PM importCounterList –type RNC –dn <fdn> -file dfs:/
counterlists/import/ATT_rnc_06_00_00.csv
Where <fdn> is the distinguished name of the RNC to be updated
Example: To change the counter list to RNC27.csv for RNC DENVCORNC27
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT RNC Counters Enabling the RNC Counters
RNC Counters
....................................................................................................................................................................................................................................
PM importCounterList –type RNC –dn {RNC DENVCORNC27} –file
dfs:/counterlists/import/ATT_rnc_06_00_00.csv
• Wait for the command to complete successfully. A response similar to the following
will be seen.
Counter List has been imported successfully.
• Exit from the WICL window.
• Log out of the NSP.
E...................................................................................................................................................................................................
N D O F S T E P S
DRAFT
....................................................................................................................................................................................................................................
30-3006 UA08.1
DRAFT
Appendix A: Glossary
Glossary of terms
Acronyms and abbreviations
This topic lists the acronyms, abbreviations, and terms specific to the RNC UA08.1
Integration
Terminology Definition or Meaning

ATM Asynchronous Transfer Mode
BTS Base Transceiver Station
CN Core Network
C-Node Control Node
CP Control Processor
FDD Frequency Division Duplex
FTP File Transfer Protocol
GGSN Gateway GPRS Support Node
I-Node Interface Node (RNC 1000) or Integrated Node (9070 RNC)
IP Internet Protocol
JRE Java Runtime Environment
NE Network Elements
NSP Network Services Platform
OAM Operation Administration and Maintainance
OS Operating System
RAN Radio Access Network
RNC Radio Network Controller
RNS Radio Network Subsystems
DRAFT
ROC Regional Operational Center

...................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC A-1
30-3006 UA08.1
DRAFT Glossary Glossary of terms
....................................................................................................................................................................................................................................
Terminology Definition or Meaning

SAS Stand-Alone SMLC
UMTS Universal Mobile Telecommunication System
UTRAN UMTS Terrestrial Radio Access Network
WICL Wireless Internet Command Language
WMS Wireless Management System
WPS Wireless Provisioning System
DRAFT
....................................................................................................................................................................................................................................
A-2 Alcatel-Lucent 9370 RNC
30-3006 UA08.1
DRAFT
Appendix B: Report Sheet
Overview
Purpose
This appendix provides a site report template.
Contents
Integration report sheet B-2
DRAFT
...................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC B-1
30-3006 UA08.1
DRAFT Report Sheet Integration report sheet
....................................................................................................................................................................................................................................
Integration report sheet

Purpose
The following parts must be filled by the coordinator before the site intervention.
Table B-1 BTS Parameters
BTS IP Address:........................ Configuration:................................

OMC-B IP address:............................... Software version:..........................
Sub-network mask:.............................. Hardware reference:..........................
Software upgrade on BTS:
Table B-2 RNC Parameters
Parameter RNC-IN
Node Name
IP@
User Id
Password
ATMIF employed
IUXIF employed
Table B-3 Communication Tests
CS call validation PS call validation status

Voice Call Test:............ Ping Test:............
Iur link validation Test:............ FTP Uplink Test:............
Video Streaming Test:............ FTP Downlink Test:............
Table B-4 Antennae Positions
Cell 0 1 2 3 4 5 6
Azimuth
Table B-5 RNC Software

DRAFT
....................................................................................................................................................................................................................................
B-2 Alcatel-Lucent 9370 RNC
30-3006 UA08.1
Report Sheet Integration report sheet
DRAFT
....................................................................................................................................................................................................................................
The column "To apply" must be filled by the coordinator before the site intervention.
The columns "Ok" and "Nok" must be filled by the OMC technician during site
intervention.
Table B-6 Sequence of Operations
To
Step Procedure Condition Ok Nok
apply
1 “RNC-IN Parameters Checks” This procedure applies Yes
(p. 3-4). for check IN attributes
2 “Session Creation for INode Session Manager for Yes
Declaration, Validation, and INode
Activation” (p. 3-8)
3 “Activation Session” (p. 3-17) Session Manager for Yes
CNode
4 “Equipment Monitor Checks” Equipment Monitor for Yes
(p. 3-22) IN/ CNode
5 “Iub, Iur Validation” (p. 3-26) Links Validation: ATM Yes/
Interfaces ATM
6 “CS Tests” (p. 3-31) Communication tests Yes
7 “Voice Call on the Unlocked Communication tests Yes
Cell” (p. 3-33)
8 “Video Call on the Unlocked Links Validation: ATM Yes/
Cell (Optional)” (p. 3-35) Interfaces ATM
9 “Dial-up Connection” (p. 3-36) Communication tests Yes
10 “IP Address Allocation” (p. 3-37) Communication tests Yes
15 “Ping the GGSN” (p. 3-38) Links Validation: ATM Yes/
Interfaces ATM
17 “Open a FTP Session (Optional)” Communication tests Yes
(p. 3-40)
18 “Iux validation” (p. 3-43) Iux Validation: IP Yes
Interfaces
19 “Attributes check with CAS This procedure applies Opt
commands” (p. 3-50) in case of passport's
attributes are incorrect.
20 “Layout operations” (p. 3-51) Applies for Layout Opt
Operations
22 “Opening a Layout in Edit Applies for Layout Opt
Mode” (p. 3-52) Operations
DRAFT
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC B-3
30-3006 UA08.1
DRAFT Report Sheet Integration report sheet
....................................................................................................................................................................................................................................
Table B-6 Sequence of Operations (continued)
To
Step Procedure Condition Ok Nok
apply
23 “Insert the NEs in the Layout” Applies for Layout Opt
(p. 3-53) Operations
24 “RNC Operations” (p. 3-56) Applies for check if no Opt
datafilling problem on
the RNC
25 “RNC MIB Audit” (p. 3-58) Applies for check if no Yes
datafilling problem on
the RNC
26 “Enabling the RNC Counters” RNC Counter example. Opt
(p. 4-3)
Comments:
DRAFT
....................................................................................................................................................................................................................................
B-4 Alcatel-Lucent 9370 RNC
30-3006 UA08.1
Index
DRAFT
A ATM Interfaces Iub, Iur validation login credentials, 1-2
Iub, Iur validation, 3-25 validation procedure, 3-26 OS and software, 1-2
............................................................. .............................................................
C CNode activation, 3-16 O optional operations
activation procedure, 3-17 CAS commands, 3-50

communication tests, 3-30 insert NEs, 3-53
CS tests, 3-31 layout creation, 3-51
dial-up connection, 3-36 layout operations, UTRAN
checks, 3-49
IP address allocation, 3-37
opening layout in edit mode,
open FTP session, 3-40
3-52
ping GGSN, 3-38
RNC, 3-56
video call, 3-35
RNC MIB audit, 3-58
.............................................................
.............................................................
E Equipment Monitor checks, 3-21
R RNC counters, 4-2
check procedure, 3-22
enabling, 4-3
.............................................................
RNC IN attributes checks, 3-3
I integration preparation, 1-3, 2-2 parameters checks, 3-4
checklist, 1-3, 2-2 .............................................................
precautions, 1-3, 2-2
S session manager
preparation, 1-3, 2-2
Creation for INode declaration,
integration procedures, 3-1 validation, and activation, 3-8
IP Interfaces RNC declaration, validation
and activation, 3-6
Iux validation, 3-42
system requirements, 1-2
IP interfaces
hardware, 1-2
DRAFT
Iux validation, 3-43
....................................................................................................................................................................................................................................
Alcatel-Lucent 9370 RNC IN-1
30-3006 UA08.1
DRAFT Index
....................................................................................................................................................................................................................................
DRAFT
....................................................................................................................................................................................................................................
IN-2 Alcatel-Lucent 9370 RNC
30-3006 UA08.1

30-3006 (Alcatel-Lucent 9370 RNC UA08.1 Integration) 01.01 Draft July 2011

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

30-3006 (Alcatel-Lucent 9370 RNC UA08.1 Integration) 01.01 Draft July 2011

Încărcat de

Drepturi de autor:

Formate disponibile

DRAFT

Reason for revision ...................................................................................................................................................................... xi

New in this release ....................................................................................................................................................................... xi

Intended audience ......................................................................................................................................................................... xi

Supported systems ........................................................................................................................................................................ xi

How to use this document ......................................................................................................................................................... xi

Prerequisites .................................................................................................................................................................................. xii

Conventions used ........................................................................................................................................................................ xii

Related information .................................................................................................................................................................... xii

Document support ...................................................................................................................................................................... xiii

Technical support ....................................................................................................................................................................... xiii

How to order ................................................................................................................................................................................ xiii

How to comment ........................................................................................................................................................................ xiii

Overview ...................................................................................................................................................................................... 1-1

System requirements ................................................................................................................................................................ 1-2

Precautions and preparation .................................................................................................................................................. 1-3

General overview ...................................................................................................................................................................... 1-4

Overview ...................................................................................................................................................................................... 2-1

Precautions and preparation .................................................................................................................................................. 2-2

Overview ...................................................................................................................................................................................... 3-1

RNC IN attributes checks

Overview ...................................................................................................................................................................................... 3-3

RNC-IN Parameters Checks ................................................................................................................................................. 3-4

Session Manager: RNC declaration, validation, and activation

Overview ...................................................................................................................................................................................... 3-6

CNode Activation Session

Overview ................................................................................................................................................................................... 3-16

Activation Session ................................................................................................................................................................. 3-17

Equipment Monitor checks

Overview ................................................................................................................................................................................... 3-21

Equipment Monitor Checks ................................................................................................................................................ 3-22

Iub, Iur Validation: ATM Interfaces

Overview ................................................................................................................................................................................... 3-25

Iub, Iur Validation .................................................................................................................................................................. 3-26

Overview ................................................................................................................................................................................... 3-30

CS Tests ..................................................................................................................................................................................... 3-31

Voice Call on the Unlocked Cell ....................................................................................................................................... 3-33

Video Call on the Unlocked Cell (Optional) ................................................................................................................ 3-35

Dial-up Connection ................................................................................................................................................................ 3-36

IP Address Allocation ........................................................................................................................................................... 3-37

Ping the GGSN ........................................................................................................................................................................ 3-38

Open a FTP Session (Optional) ......................................................................................................................................... 3-40

Overview ................................................................................................................................................................................... 3-42

Iux validation ........................................................................................................................................................................... 3-43

Optional operations regarding layout operations and UTRAN checks

Overview ................................................................................................................................................................................... 3-49

Attributes check with CAS commands ........................................................................................................................... 3-50

Layout operations ................................................................................................................................................................... 3-51

Opening a Layout in Edit Mode ........................................................................................................................................ 3-52

Insert the NEs in the Layout ............................................................................................................................................... 3-53

RNC Operations ...................................................................................................................................................................... 3-56

RNC MIB Audit ...................................................................................................................................................................... 3-58

Overview ...................................................................................................................................................................................... 4-1

Overview ...................................................................................................................................................................................... 4-2

Enabling the RNC Counters .................................................................................................................................................. 4-3

Glossary of terms ..................................................................................................................................................................... A-1

Overview ..................................................................................................................................................................................... B-1

Integration report sheet .......................................................................................................................................................... B-2

B-2 RNC Parameters ........................................................................................................................................................ B-2

B-3 Communication Tests .............................................................................................................................................. B-2

B-4 Antennae Positions ................................................................................................................................................... B-2

B-5 RNC Software ............................................................................................................................................................ B-2

B-6 Sequence of Operations .......................................................................................................................................... B-3

3-2 Session Creation ......................................................................................................................................................... 3-9