of 240

Nokia RNC Integration

Published on December 2016 | Categories: Documents | Downloads: 105 | Comments: 0
760 views

RNC Integration

Comments

Content

Nokia WCDMA RNC, Rel. RN2.2, Product Documentation, v. 3

RNC Integration

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

1 (240)

RNC Integration

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Siemens Networks 2007. All rights reserved.

2 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Contents

Contents
Contents 3 1 1.1 1.2 1.3 2 3 3.1 3.2 3.3 3.4 3.4.1 3.4.2 3.5 3.5.1 3.5.2 3.6 3.6.1 3.6.2 3.6.3 3.6.4 3.6.5 3.6.6 3.6.7 3.6.8 3.6.9 3.7 3.7.1 3.7.2 4 4.1 4.2 4.3 5 6 6.1 6.2 7 7.1 7.2 Documentation changes in RNC Integration 7 Changes between issues 8-0 and 9-0 7 Changes between issues 7 and 8-0 8 Changes in issue 7 10 Integration overview 15 Configuring IP for O&M backbone (RNC - NetAct) 21 Configuring IP for O&M backbone (RNC — NetAct) 21 Creating MMI user profiles and user IDs for remote connections to NetAct 23 Configuring IP stack in OMU 25 Configuring IP routing 28 Creating OSPF configuration for O&M connection to NetAct 28 Configuring static routes for the O&M connection to NetAct 33 Configuring LAN switch 35 Configuring ESA12 35 Configuring ESA24 38 Configuring NEMU for DCN 41 Configuring NEMU for DCN 41 Configuring DHCP server in NEMU 42 Configuring DNS client and server in NEMU 44 Configuring NEMU to RNC 48 NemuRegEdit 50 NemuRUIMConfiguration 55 Configuring NTP services in NEMU 60 Finalising SQL server configuration 64 Configuring IP address for NEMU 66 Configuring external IP connections 68 Connecting to O&M backbone via Ethernet 68 Configuring IP over ATM interfaces 69 Integrating NEMU 71 Configuring NEMU system identifier (systemId) Configuring the RNC object 72 Configuring Nokia NetAct interface with NEMU Configuring heartbeat interval for RNC 77 Configuring RNC level parameters 79 Defining external time source for network element 79 Creating local signalling configuration for RNC 80 Configuring transmission and transport interfaces 85 Configuring PDH for ATM transport 85 Creating IMA group 88 71 73

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

3 (240)

RNC Integration

7.3 7.4 7.5 7.6 8 9 9.1 9.2 9.3 9.4 10 10.1 10.2 10.2.1 10.2.2 10.2.3 10.2.4 10.2.5 10.3 10.4 10.5 10.6 11 11.1 11.2 11.3 11.4 12 12.1 12.2 12.3 12.4 13 13.1 13.2 13.3 14 14.1 14.2 14.3 14.4 14.5 14.6

Configuring SDH for ATM transport 90 Creating SDH protection group 92 Creating phyTTP 94 Creating ATM resources in RNC 97 Configuring synchronisation inputs 105 Creating Iub interface (RNC-BTS) 111 Configuring transmission and transport resources 111 Creating radio network connection configuration 111 Creating ATM termination point for IP over ATM connection Configuring IP for BTS O&M (RNC-BTS/AXC) 115

113

Creating Iu-CS interface (RNC-MGW) 121 Configuring transmission and transport resources 121 Configuring ATM-based signalling channels 121 Creating remote MTP configuration 121 Activating MTP configuration 126 Setting MTP level signalling traffic load sharing 128 Creating remote SCCP configuration 129 Activating SCCP configuration 133 Configuring IP-based signalling channels 134 Configuring Iu-CS parameters of RNC 138 Creating routing objects and digit analysis for Iu interface in RNC 140 Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface 145 Creating Iu-PS interface (RNC-SGSN) 153 Configuring transmission and transport resources 153 Configuring signalling channels 153 Configuring Iu-PS parameters of RNC 153 Configuring IP for Iu-PS User Plane (RNC-SGSN) 154 Creating Iur interface (RNC-RNC) 167 Configuring transmission and transport resources 167 Configuring signalling channels 167 Configuring Iur parameters of RNC 167 Creating routing objects and digit analysis for Iur interface in RNC Creating Iu-BC interface (RNC-CBC) 175 Configuring transmission and transport resources Configuring Iu-BC parameters of RNC 175 Configuring IP for Iu-BC (RNC-CBC) 176 175

168

Configuring radio network objects 183 Creating frequency measurement control 183 Creating handover path 184 Creating a WCDMA BTS site 185 Creating a WCDMA cell 188 Creating an internal adjacency for a WCDMA cell 189 Creating an external adjacency for a WCDMA cell 192

4 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Contents

15 15.1 15.2 15.2.1 15.2.2 15.3 15.3.1 15.3.2 15.4 15.4.1 15.4.2 15.4.3 16 16.1 16.2

Integrating location services 195 Overview of location services 195 Creating TCP/IP configuration in RRMU units 195 Overview of TCP/IP configuration in RRMU units 195 Defining IP addresses and IP routes to RRMU units 197 Configuring ESA24 switches 200 Configuring ESA24-0 200 Configuring ESA24-1 206 Activating location services 213 Activating the Location Services feature 213 Activating the ADIF interface 213 Activating the Iupc interface 214 Printing alarms 217 Printing alarms using LPD protocol 217 Printing alarms via Telnet terminal or Web browser Related Topics 223

219

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

5 (240)

RNC Integration

6 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Documentation changes in RNC Integration

1
1.1

Documentation changes in RNC Integration
Changes between issues 8-0 and 9-0
Modified chapters

Table 1.

Modified chapters Description of the change
A paragraph about IP layer configuration added before the step text. A link to ATM and IP plan interfaces added. A paragraph about static route configuration added before the step text. A link to ATM and IP plan interfaces added. Note text on using the Object Browser or NetAct edited and replaced by normal text. A link to ATM and IP plan interfaces added.

Title of the modified chapter
Configuring IP stack in OMU

See
Configuring IP stack in OMU

Configuring static routes for the O&M connection to NetAct

Configuring static routes for the O&M connection to NetAct

Creating ATM resources in RNC

Creating ATM resources in RNC

Creating ATM termination point for IP over ATM connection Configuring IP for BTS O&M (RNC-BTS/AXC)

A paragraph added to Creating ATM termination Purpose. A link to ATM and point for IP over ATM IP plan interfaces added. connection A paragraph about IP over ATM connection configuration added before the steps. A link to ATM and IP plan interfaces added. Configuring IP for BTS O&M (RNC-BTS/AXC)

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

7 (240)

RNC Integration

Table 1.

Modified chapters (cont.) Description of the change
A paragraph about IP over ATM connection configuration added before the steps. A link to ATM and IP plan interfaces added. A paragraph about lu-PS interface ATM and IP basic resources configuration added before the steps. A link to ATM and IP plan interfaces added. A document reference to NOLS added.

Title of the modified chapter
Configuring IP-based signalling channels

See
Configuring IP-based signalling channels

Configuring IP for lu-PS User Plane (RNC-SGSN)

Configuring IP for lu-PS User Plane (RNC-SGSN)

Activating the location services feature

Activating the location services feature

1.2

Changes between issues 7 and 8-0
New chapters

Table 2. Title of the new chapter
NemuRUIMConfiguration

New chapters See
NemuRUIMConfiguration

Description of the change
In this release, RNC supports the Remote User Information Management (RUIM) feature. This sections provides instructions for configuring NEMU when the RUIM feature is used.

8 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Documentation changes in RNC Integration

Modified chapters

Table 3. Title of the modified chapter
NemuRegEdit

Modified chapters See
NemuRegEdit

Description of the change
Registration Account user name corrected. NEMUFTP user name corrected.

Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface Configuring NEMU for DCN

Creating routing objects and digit It has been mentioned that analysis with subdestinations and alternative routing is the default routing policy for Iu interface routing policy and if alternative routing is used for the subdestination, new subdestination type and percentages should not be defined. Steps for configuring the RUIM feature in NEMU and finalising the SQL server configuration have been added. Configuring NEMU for DCN

Configuring NEMU to RNC The NEMU registry variables used when configuring NEMU for RNC connection have been added. Information on the user accounts that must be created in NEMU has been added. Configuring IP for O&M backbone (RNC-NetAct) The note about improving the redundancy of the RNC Ethernet network by installing a redundant ESA24 has been removed.

Configuring NEMU to RNC

Configuring IP for O&M backbone (RNC-NetAct)

Configuring IP for Iu-PS Instructions for creating UMTS traffic User Plane (RNC – SGSN) classification mapping configuration (GTPU) have been added. Overview of TCP/IP configuration in RRMU units Configuring ESA24-0 Sales item kit information updated.

Configuring IP for Iu-PS User Plane (RNC – SGSN) Overview of TCP/IP configuration in RRMU units Configuring ESA24-0

BiNOS version updated. Information about the standardcompatible implementation of the IEEE 802.1s MSTP protocol updated. Configuration instructions updated.

Configuring ESA24-1

BiNOS version updated. Information about the standardcompatible implementation of the IEEE 802.1s MSTP protocol updated. Configuration instructions updated.

Configuring ESA24-1

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

9 (240)

RNC Integration

Table 3. Title of the modified chapter
Activating the ADIF interface Activating the Iu-PC interface

Modified chapters (cont.) See
Activating the ADIF interface

Description of the change
ADIF activation instructions updated.

Iu-PC activation instructions updated. Activating the Iu-PC interface

Removed chapters
.

Configuring O&M IP network

1.3

Changes in issue 7
New chapters

Table 4. Title of the new chapter
Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface Configuring IP-based signalling channels

New chapters See

Description the change

In this release, alternative routing can Creating routing objects and digit analysis with subdestinations and be used in the Iu-CS interface if the connection to the primary direction is routing policy for Iu interface broken or the subdestination selected before is congested. In this release, SS7 signalling over IP is supported in the Iu-PS, Iu-CS, and Iur interfaces. Configuring IP-based signalling channels

10 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Documentation changes in RNC Integration

Table 4. Title of the new chapter
Integrating location services

New chapters (cont.) See
Overview of location services Overview of TCP/IP configuration in RRMU units Defining IP addresses and IP routes to RRMU units Configuring ESA24-0 Configuring ESA24-1 Activating the Location Services feature Activating the ADIF interface Activating the Iu-PC interface Configuring IP addresses to OMU units Overview of O&M IP network configuration Configuring OSPF routing to OMU units

Description the change
In this release, the Nokia RNC implementation of the location services includes two different interfaces, Iu-PC and ADIF, to the external LCS server for additional locationing methods.

Modified chapters

Table 5. Title of the modified chapter
Integration NEMURegEdit

Modified chapters See
Integration overview NEMURegEdit

Description of the change
Iu-PC and ADIF interface information has been added. Release upgrade related note about providing the RNC baseID, typeID, and OMU IP address for NemuRegEdit has been removed as this information is no longer required in RN2.1 to RN2.2 upgrade. A note about improving the redundancy of the Ethernet network has been added.

Configuring IP for O&M backbone (RNC - NetAct) Configuring static routes for O&M connection to NetAct

Configuring IP for O&M backbone (RNC - NetAct)

The syntax of the QKC command has Configuring static routes for O&M been changed. This change is related connection to NetAct to Multiple Default Route/IP routing (OSPFv2 in Chorus).

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

11 (240)

RNC Integration

Table 5. Title of the modified chapter
Configuring ESA24

Modified chapters (cont.) See
Configuring ESA24

Description of the change
More information has been added to the step for configuring RSTP and MSTP.

Configuring DNS client and DNS query has been removed from server in NEMU application launcher; therefore, references to DNS query have been removed from this chapter. Finalising SQL server configuration Configuring IP for BTS O&M (RNC – BTS/AXC) A screenshot has been added.

Configuring DNS client and server in NEMU

Finalising SQL server configuration

The syntax of the QKC command has Configuring IP for BTS O&M (RNC been changed. This change is related – BTS/AXC) to Multiple Default Route/IP routing (OSPFv2 in Chorus). In this release, FlexiBTSs are supported. Therefore, two notes about the IP and ATM configurations of FlexiBTS have been added.

Creating remote MTP configuration

The syntax of the NRC command has Creating remote MTP configuration been corrected. In RN2.2, SIGTRAN can be used as an alternative to the ATM-based MTP3 in the Iu-PS, Iur, and Iu-CS interfaces. Information about SS7 over IP has been added to this chapter.

Configuring IP for Iu-PS The syntax of the QKC command has Configuring IP for Iu-PS User User Plane (RNC – SGSN) been changed. This change is related Plane (RNC – SGSN) to Multiple Default Route/IP routing (OSPFv2 in Chorus). Configuring IP for Iu-BC (RNC – CBC) The syntax of the QKC command has Configuring IP for Iu-BC (RNC – been changed. This change is related CBC) to Multiple Default Route/IP routing (OSPFv2 in Chorus). First step on creating frequency measurement control has been modified. First step on creating handover path has been modified. A step on Site Creation Confirmation has been deleted. A step on creating the cell unlocked has been added to WCDMA cell creation. Creating frequency measurement control Creating handover path Creating a WCDMA BTS site Creating a WCDMA cell

Creating frequency measurement control Creating handover path Creating a WCDMA BTS site Creating a WCDMA cell

12 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Documentation changes in RNC Integration

Table 5. Title of the modified chapter
Creating an external adjacency for a WCDMA cell

Modified chapters (cont.) See
Creating an external adjacency for a WCDMA cell

Description of the change
The internal adjacency creation step 2 has been modified.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

13 (240)

RNC Integration

14 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integration overview

2

Integration overview
You can start the integration of a network element after the network element has been successfully installed and commissioned. During the commissioning phase, the network elements have been configured and tested as stand-alone entities. During the integration phase the interconnections between the network elements are configured and their parameters are customised. After successful integration the network element is ready for commercial use.

Note
IPv6 is not supported in current releases in WCDMA RAN even if it is included in some IP configuration intructions.

Integration overview

Integration consists of the following steps: 1. configuring internet protocol (IP) for operation and maintenance (O&M) backbone (radio network controller (RNC) - NetAct) a. configuring IP for O&M backbone (RNC - NetAct) b. creating man-machine interface (MMI) user profiles and user IDs for remote connections to NetAct c. configuring IP stack in OMU d. configuring IP routing e. configuring local area network (LAN) switch f. configuring network element management unit (NEMU) for data communication network (DCN) g. configuring external IP connections integrating NEMU

2.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

15 (240)

RNC Integration

a. b. c. 3. 4.

configuring network element system identifier (systemId) to NEMU configuring the RNC object configuring Nokia NetAct interface with NEMU

configuring heartbeat interval for RNC configuring RNC level parameters a. defining external time source for network element b. creating local signalling configuration for RNC configuring transmission and transport interfaces a. configuring plesiochronous digital hierarchy (PDH) for asynchronous transfer mode (ATM) transport b. creating inverse multiplexing for ATM (IMA) group c. configuring synchronous digital hierarchy (SDH) for ATM transport d. creating SDH protection group e. creating physical layer trail termination point (phyTTP) f. creating ATM resources in RNC configuring synchronisation inputs creating Iub interface (RNC - base transceiver station (BTS)) a. configuring transmission and transport resources (see step 5) b. creating radio network connection configuration c. creating ATM termination point for IP over ATM connection d. configuring IP for BTS O&M (RNC-BTS/ATM cross-connection (AXC)) creating Iu-CS interface (RNC - multimedia gateway (MGW)) a. configuring transmission and transport resources (see step 5) b. configuring ATM-based signalling channels c. configuring IP-based signalling channels d. configuring Iu-CS parameters of RNC e. creating routing objects and digit analysis for Iu interface in RNC f. creating routing objects and digit analysis with subdestinations and routing policy for Iu interface creating Iu-PS interface (RNC-serving GPRS support node (SGSN)) a. configuring transmission and transport resources b. configuring ATM-based signalling channels c. configuring IP-based signalling channels

5.

6. 7.

8.

9.

16 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integration overview

d. e. 10.

configuring Iu-PS parameters of RNC configuring IP for Iu-PS User Plane (RNC-SGSN)

creating Iur interface (RNC-RNC) a. configuring transmission and transport resources b. configuring ATM-based signalling channels c. configuring IP-based signalling channels d. configuring Iur parameters of RNC e. creating routing objects and digit analysis for lur interface in RNC creating Iu-BC interface (RNC-cell broadcast centre (CBC)) a. configuring transmission and transport resources b. configuring Iu-BC parameters of RNC c. configuring IP for Iu-BC (RNC-CBC) configuring radio network objects a. creating frequency measurement control (FMC) b. creating handover path c. creating a WCDMA BTS (WBTS) site d. creating a WCDMA cell (WCEL) e. creating an internal adjacency for a WCDMA cell f. creating an external adjacency for a WCDMA cell integrating location services a. creating TCP/IP configuration in RRMU units b. configuring ESA24 switches c. activating location services d. configuring O&M IP network printing alarms a. printing alarms using LPD protocol b. printing alarms via a Telnet terminal or a web browser

11.

12.

13.

14.

Example network

The integration instructions are based on the following third generation example network:

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

17 (240)

RNC Integration

BTS

Iub Iu-CS Multimedia Gateway Rel. 4

MSC Server

Iub BTS RNC Iu-BC

Iu-PC

NetAct

Iur CBC

Iu-PS ADIF SAS

SGSN RNC

A-GPS Server

Figure 1.

Example network and logical interfaces between network elements

The logical interfaces for the RNC in the 3rd generation network are presented in the following list. Iu-CS logical interface between the RNC and the core network. The Iu interface provides signalling means to establish, maintain and release links and recover fault situations and generic bearer services over its user plane. logical interface between the RNC and the SGSN logical interface for the interconnection of two RNC components of the UMTS terrestrial radio access network (UTRAN) system logical interface between the RNC and the WBTS

Iu-PS Iur

Iub

18 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integration overview

Iu-BC ADIF Iupc

logical interface between the RNC and the cell broadcast centre (CBC) Logical interface between the RNC and the A-GPS Server Logical interface between the RNC and the Standalone SMLC

Required integration planning information

The network planning process delivers all required information for network element installation, commissioning and integration. Network planning can be divided into the following phases: transmission & transport and radio network planning. The following planning activities must be accomplished before the integration phase starts: 1. 2. radio network planning transport/transmission network planning (in Nokia terminology, transmission is related to the PDH/SDH network and transport to the ATM/AAL2 network). IP network planning

3.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

19 (240)

RNC Integration

20 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

3
3.1

Configuring IP for O&M backbone (RNC NetAct)
Configuring IP for O&M backbone (RNC — NetAct)
Purpose

This chapter shows the procedure to configure the Network Element Management Unit (NEMU), ESA12/ESA24 Ethernet switch and the Operation and Maintenance Unit (OMU) for the data communication network (DCN). After this, you can use the Element Manager to manage the RNC remotely. The O&M backbone can be configured either via Ethernet or via ATM virtual connections, or via both if OSPF is used.
Before you start

Check that:
.

you have the IP address plan and IP parameters for OMU, NEMU, and ESA12/ESA24. your computer has the following: . DHCP client . Connection to the Element Manager and remote management application for NEMU For more information, see Installing Element Manager. . Ethernet interface connected to a port of ESA12/ESA24

.

If O&M backbone towards NetAct is connected via ATM virtual connection, the transport and transmission network plan for the interface in question is also required. Usually, this interface is Iu-CS.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

21 (240)

RNC Integration

Computer with Element Manager 192.168.1.10/28

ESA12/ESA24 192.168.1.9/28

192.168.1.5/28

NEMU

OMU

192.168.1.1/28 (logical)

RNC LAN
192.168.1.0/28 RNC

Figure 2.

Preconfigured settings for O&M network

The default gateway in NEMU and ESA12/ESA24 is 192.168.1.1.

Steps
1. Create MMI user profiles and user IDs for remote connection to NetAct See Creating MMI user profiles and user IDs for remote connections to NetAct for detailed instructions. 2. Configure IP stack in OMU See instructions in Configuring IP stack in OMU. 3. Configure IP routing There are two ways to configure routing information: . by creating OSPF configuration See instructions in Creating OSPF configuration for O&M connection to NetAct.

22 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

.

by configuring static routes See instructions in Configuring static routes for O&M connection to NetAct.

4.

Configure the Ethernet/LAN switch Configure the Ethernet (LAN) switch according to instructions in Configuring ESA12 or Configuring ESA24, depending on which one you have in your configuration.

5.

Configure NEMU Configure NEMU according to instructions in Configuring NEMU for DCN.

6.

Configure external IP connections Configure the connection to NetAct for O&M traffic. There are two ways to connect the RNC to NetAct: . by configuring the O&M backbone via Ethernet Refer to instructions in Connecting to O&M backbone via Ethernet. . by configuring the O&M backbone via ATM virtual connections Refer to instructions in Configuring IP over ATM interfaces. The recommended way of connecting RNC to NetAct is via Ethernet. The connection via ATM should only be used as a backup. O&M connections can be configured to use both ways, if OSPF is used for routing.

3.2

Creating MMI user profiles and user IDs for remote connections to NetAct
Purpose

To enable remote connections from the NetAct to the RNC, you need to create users NUPADM and NEMUAD and their profiles in the RNC. NetAct application (service user management) accesses RNC with NUPADM profile. NUPADM profile is mandatory to create other service users in NetAct application. NEMUAD profile is created to enable communication between NEMU and OMU. For example, without NEMUAD profile, PM data cannot be transferred to NEMU and therefore affects the transfer measurement to NetAct.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

23 (240)

RNC Integration

See the example below for detailed instructions.
Before you start

If you do not know the password, contact your NetAct administrator.

Steps
1. Establish a telnet connection to RNC OMU Enter the preconfigured IP address to OMU (the default IP address is 192.168.1.1):
telnet <IP address of OMU>

2.

Create new MMI user profiles Create the user profiles for NUPADM and NEMUAD. Refer to Creating MMI user profiles in Information Security for details.

3.

Create new MMI user IDs Create the NUPADM and NEMUAD user IDs. Refer to Creating MMI user IDs in Information Security for details.

Example

Creating MMI user profiles and user IDs in the RNC

This example shows how to create the NUPADM and NEMUAD MMI profiles and user IDs in the RNC. 1. Create the user profiles. ZIAA:NUPADM:ALL=250:VTIME=FOREVER,UNIQUE=YES; ZIAA:NEMUAD:ALL=250:VTIME=FOREVER,UNIQUE=YES:: FTP=W; 2. Create the user IDs. ZIAH:NUPADM:NUPADM; ZIAH:NEMUAD:NEMUAD; When creating a new user ID, the system prompts you for a password. The password created here is used for communication between the NEMU or the NetAct and the RNC. The system displays the following output:

24 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

/* IDENTIFY PASSWORD: MINIMUM PASSWORD LENGTH IS 6 MAXIMUM PASSWORD LENGTH IS 16 */ NEW PASSWORD:******** VERIFICATION:******** COMMAND EXECUTED

Enter the same password as used in the NEMU and the NetAct.

3.3

Configuring IP stack in OMU
Purpose

The purpose of this procedure is to configure OMU for data communication network (DCN).
Before you start

Note
In addition to the MML based configuration the IP layer can be configured via the IP plan interface from the NetAct. The IP plan support does not contain the OSPF configuration. For further details on the IP plan interface see IP plan interface in document RNC Operation and Maintenance.

A telnet connection to RNC OMU must be open. For IPv4: You can use the QRJ, QRH, QRI, and QRS commands to interrogate the configuration. For IPv6: You can use the Q6J, Q6H, Q6I, and Q6S commands to interrogate the configuration.

Steps
1. Configure DNS parameter data Define whether or not the DNS service is utilised in IP data transfer.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

25 (240)

RNC Integration

For IPv4: ZQRK:[<primary DNS server>],[<secondary DNS server>],[<third DNS server>],[<local domain name>], [<sortlist>],[<netmask>]:[<resolver cache>], [<round robin>]; For IPv6: ZQ6K:[<primary DNS server>],[<secondary DNS server>],[<third DNS server>],[<local domain name>], [<network sortlist>],[<prefix length>]:[<resolver cache>],[<round robin>]; 2. Modify TCP/IP parameters Set host names, define if the OMU forwards IP packets, set the maximum time-to-live value and define if the subnets are considered to be local addresses in both OMU units. For IPv4: ZQRT:<unit type>, <unit index>:(HOST=<host name>, [IPF=<IP forwarding>],[TTL=<IP TTL>],[SNL=<subnets are local>]); For IPv6: ZQ6T:<unit type>,<unit index>:([IPF=<IP forwarding>],[HLIM=<hoplimit>],[RADV=<router advertisement>]); 3. Add a new logical IP address Assign the IP address to both OMU units by QRN for IPv4 and Q6N for IPv6. ZQRN:OMU:<interface name>,[<point to point interface type>]:[<IP address>],[<IP address type> ]:[<netmask length>]:[<destination IP address>]:[<MTU>]: [<state>]; ZQ6N:OMU,<unit index>:<interface name>:[<IP address>],[<address type>]:[<prefix length>]: [<destination IP address>];

26 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

4.

Configure IP routing There are two ways to configure routing information: . by creating OSPF configuration Refer to instructions in Creating OSPF configuration for O&M connection to NetAct. . by configuring static routes Refer to instructions in Configuring static routes for O&M connection to NetAct.

5.

Remove the preconfigured IP address Remove the preconfigured IP address from both OMU units by QRN command for IPv4, by Q6G command for IPv6. ZQRN:OMU:<interface name...>,:<IP address>,,DEL; ZQ6G:OMU,<unit index>:<interface name>:<IP address>:;

Note
If the unit index for 2N type logical IP address is specified, the logical addresses will be deleted both from WO and SP unit.

Example

Configuring IPv4 stack in OMU

This example shows how to configure the IPv4 stack in OMU for DCN. 1. Configure DNS parameter data. The IPV4 address of the primary DNS server is 10.1.1.5 and the local domain name RNC1.NETACT. OPERATOR.COM. ZQRK:10.1.1.5,,,"RNC1.NETACT.OPERATOR.COM"; 2. Modify IPv4 parameters for both OMU units separately. Set the host name to OMU, set IP forwarding on, and specify that subnets are not local. ZQRT:OMU,0:HOST="OMU",IPF=YES,SNL=NO; ZQRT:OMU,1:HOST="OMU",IPF=YES,SNL=NO; 3. Add a new logical IPv4 address (10.1.1.2) to the OMU units. The interface name is EL0 and the netmask is length 28.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

27 (240)

RNC Integration

ZQRN:OMU:EL0:10.1.1.2,L:28:::UP; 4. Configure IPv4 routing. For examples, see Creating OSPF configuration for O&M connection to NetAct and Configuring static routes for O&M connection to NetAct. Remove the preconfigured IPv4 address (198.168.1.1) from both OMU units. ZQRN:OMU:EL0:192.168.1.1,,DEL; Example Configuring IPv6 stack in OMU

5.

This example shows how to configure the IPv6 stack in OMU for DCN. 1. Configure DNS parameter data. The IPv6 address of the primary DNS server is 3FEE::1 and the local domain name RNC1.NETACT. OPERATOR.COM. ZQ6K:"3FEE::1",,,"RNC1.NETACT.OPERATOR.COM"; 2. Modify IPv6 parameters for both OMU units separately. Set the host name to OMU, set IP forwarding on, set hoplimit value as 70, and set router advertisement OFF. ZQ6T:OMU,0:IPF=ON,HLIM=70,RADV=OFF; ZQ6T:OMU,1:IPF=ON,HLIM=70,RADV=OFF; 3. Add a new logical IPv6 address (3FFE:1200:3012:C020:380:6FFF: FE5A:5BB7) to the OMU units. The interface name is EL0 and the netmask is length 20. ZQ6N:OMU,0:EL0:"3FFE:1200:3012:C020:380:6FFF: FE5A:5BB7",L:20; 4. Remove the preconfigured IPv6 address (3FEE::1) from both OMU units. ZQ6G:OMU,0:EL0:"3FEE::1":;

3.4
3.4.1

Configuring IP routing
Creating OSPF configuration for O&M connection to NetAct
Purpose

The purpose of this procedure is to create OSPF configuration in OMU.

28 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

Before you start

If O&M connections towards NetAct use also backup connection via ATM virtual connection, the IP over ATM interface for OMU must be created before OSPF is configured. Refer to instructions in Configuring IP over ATM interfaces. You must remove the existing default routes before creating the OSPF configuration. If the default routes are not removed, the RNC might advertise itself, incorrectly, as an alternative default route to other routers. For instructions on how to remove default routes, see Configuring static routes for O&M connection to NetAct.

Steps
1. Configure OSPF router parameters (QKS) If only logical IP addresses are configured for the OMUs, the same router ID can be configured to both OMUs. If the OMU units have physical IP addresses in addition to a logical IP address, the OMU units must have different router IDs. In this case, give the physical address of the OMU unit as the value for the router ID parameter to avoid having two routers with the same router ID in the network. ZQKS:<unit type>, <unit index> :<router id>: <rfc1583compatibility>:<spf delay>:<spf hold time>; 2. Configure OSPF area parameters (QKE) Define the OSPF area (both backbone and other area) parameters of an OSPF router. ZQKE:<unit type>,<unit index>:<area identification>:<stub area>,[<stub area route cost>],<totally stubby area>; The area identification specifies the area ID for a new OSPF. The area ID is entered as a dotted-quad. The area ID of 0.0.0.0 is reserved for the backbone. The IP network number of a subnetted network may be used as the area ID.

Note
The area parameters do not become effective (written into the configuration file) until the area has been attached to an interface.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

29 (240)

RNC Integration

3.

Interrogate IP interfaces (QRI) You must know the “interface identification” of the network interfaces when you are configuring OSPF interfaces. ZQRI:<unit type>,<unit index>:<interface name>; If you do not give any parameter values, network interface information of all computer units of the network element is listed.

4.

Configure OSPF interfaces (QKF) ZQKF:<unit type>,<unit index> :<interface specification>:<area identification>:[<hello interval>]:[<router dead interval>]:[<ospf cost>]:< [election priority>]:[<passive>]:[<authentication> | <password>];

5.

Configure redistribute parameters (QKU) ZQKU:<unit type>,<unit index>:<redistribute type and identification>:<metric>;

6.

Configure network prefix, if required (QKH) This command defines a network prefix in the OSPF area. Configuring the network prefix is optional to reduce the routing information exchange between different areas. ZQKH:<unit type>,<unit index>:<area identification>:ADD:<network prefix>:<network prefix mask length>:<network prefix restriction>;

7.

Configure virtual link parameters, if required (QKV) If there is an OSPF area which does not have a physical connection to the backbone area, use a virtual link to provide a logical path from the disconnected area to the backbone area. Virtual links have to be configured to both ends of the link. The QKV command has to be entered separately for both border routers using the virtual link. ZQKV:<unit type>,<unit index>:<router identification>:<transit area>:<hello interval>: <router dead interval>:<authentication>;

Example

Creating OSPF configuration for O&M DCN

30 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

The following example illustrates OSPF configuration for O&M DCN. The corresponding IP network interfaces have been configured before this procedure.

NetAct

10.3.1.1/24

O&M backbone

RAN O&M backbone address range 10.0.0.0/14 OSPF Area 0 Computer with Element Manager 10.1.1.10/28

IP over ATM virtual connection

10.3.2.1/24 10.1.1.1/28

MGW

ESA12/ESA24 10.1.1.9/28

10.1.1.5/28

NEMU

AA255 10.3.2.2/32 10.1.1.2/28 (logical) AA0 10.3.1.2/32 OMU

RNC LAN
10.1.1.0/28 10.1.1.2/32 10.1.1.2/32 unnumbered lines RAN BTS sites address range 10.1.3.0 RAN BTS sites address range 10.1.2.0 RNC

Figure 3.

Example of OSPF configuration for RNC

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

31 (240)

RNC Integration

This example presents the configuration of OSPF parameters in the OMU unit. The OMU unit in RNC is a border router. The unit has three interfaces: EL0, AA0, and AA255. The EL0 interface is attached to the backbone area through an Ethernet connection. The AA0 and AA255 interfaces are attached to the backbone area through an IP over ATM connection. 1. Obtain the numbers of the default routes of OMU-0 and OMU-1. ZQKB:OMU; The following output is displayed:
UNIT DESTINATION GATEWAY ADDRESS ROUTE TYPE NBR ----- ------------- --------------- ---------- ---OMU-0 DEFAULT ROUTE 10.1.1.1 LOG 1

2.

Remove the default route from both units. ZQKA:1; or ZQKA::OMU,0;

3.

Configure OSPF router parameters. Configure the OSPF parameter data for the OMU with the router ID 10.1.1.2 and accept the default values for the remaining parameters. ZQKS:OMU,0:10.1.1.2; ZQKS:OMU,1:10.1.1.2;

4.

Configure OSPF area parameters. Configure the backbone area information for the OMU. ZQKE:OMU,0:0.0.0.0; ZQKE:OMU,1:0.0.0.0;

5.

Inquire the attached interfaces. ZQRI:OMU; The following output is displayed:
IF UNIT NAME ------- -----OMU-0 AA0 AA255 ADM IF STATE MTU TYPE ----- ----- ---UP 1500 UP 1500 ADDR TYPE IP ADDRESS ---- ------------L 10.3.1.2/32 ->10.3.1.1 L 10.3.2.2/32 ->10.3.2.1

32 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

OMU-1

EL0 AA0 AA255 EL0

UP UP UP UP

1500 1500 1500 1500

L L L L

10.1.1.2/28 (10.3.1.2)/32 ->10.3.1.1 (10.3.2.2)/32 ->10.3.2.1 (10.1.1.2)/28

6.

Configure OSPF interfaces. Configure an OSPF interface for the EL0, AA0, and AA255 interfaces. The EL0 interface is attached to the backbone area through an Ethernet connection. Accept default values for the hello interval and router dead interval parameters and set the ospf cost to 10. ZQKF:OMU,0:EL0:0.0.0.0:::10; ZQKF:OMU,1:EL0:0.0.0.0:::10; The AA0 and AA255 interfaces are attached to the backbone area through an IPoA connection. Set the hello interval to 30, router dead interval to 120, and ospf cost to 100. ZQKF:OMU,0:AA0:0.0.0.0:30:120:100; ZQKF:OMU,1:AA0:0.0.0.0:30:120:100; ZQKF:OMU,0:AA255:0.0.0.0:30:120:100; ZQKF:OMU,1:AA255:0.0.0.0:30:120:100;

7.

Configure redistribute parameters. Configure the OSPF to redistribute all valid static routes. ZQKU:OMU,0:ST=; ZQKU:OMU,1:ST=;

3.4.2

Configuring static routes for the O&M connection to NetAct
Purpose

Static routes are used when dynamic routing (OSPF in this case, see Creating OSPF configuration for O&M connection to NetAct) does not provide any useful functionality over the static routes. In other words, they are used when a simple static route works as efficient as a more complicated dynamic routing. Static routes can be used with dynamic routing when creating a host route to a host that does not run dynamic routing.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

33 (240)

RNC Integration

Static routes are not used for the IP over ATM connections towards NetAct. Configure OSPF to OMU for both connections towards the NetAct router. For instructions, see Creating OSPF configuration for O&M connection to NetAct.
Before you start

Note
You can only configure one default route for each unit. A logical route must use a logical address to reach its gateway, and it follows the logical address if a switchover occurs. The static route configuration can be done via the IP plan interface from the NetAct. For further details on the IP plan interface see IP plan interface in document RNC Operation and Maintenance.

Steps
1. Configure the default static route You do not need to specify the destination IP address for the default route.

Note
If you cannot use the default route, see the next step.

ZQKC:<unit type>,<unit index>::<gateway IP address>, [<local IP address>]:[<route type>];

Note
The parameter local IP address is only valid for local IP address based default route. For normal static routes, you do not need to give the local IP address. For more information about local IP address based default routes, refer to Creating and modifying static routes. 2.

If the default route cannot be used Then

34 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

Delete the default static route for IP configuration a. Obtain the number of the static route to be deleted. ZQKB:<unit type>,<unit index>; b. Delete the route by identifying it by its route number or by its identification. ZQKA:<route number>; ZQKA::<unit type>,<unit index>; 3.

If the default route cannot be used and you deleted it, or if you need to create more routes Then
Create new static routes (QKC) You create new static routes by using the QKC command. ZQKC:<unit type>,<unit index>:<destination IP address>,[<netmask length>]:<gateway IP address>: [<route type>];

Example

Creating a default static route in RNC OMU

The same default route is used for both OMU-0 and OMU-1. ZQKC:OMU,0::10.1.1.1,:LOG;

3.5
3.5.1

Configuring LAN switch
Configuring ESA12
Purpose

The purpose of this procedure is to configure the ESA12 Ethernet switch for O&M DCN.

Steps
1. Establish a telnet connection to ESA12 a. Enter the preconfigured IP address to ESA12 (the default IP address is 192.168.1.9).
telnet <ip address of ESA12>

b.

Enter your login ID and password.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

35 (240)

RNC Integration

The default password is empty. Therefore, press Enter to continue. If you have already changed your password during commissioning, enter your new password.
NOKIA ESA-12. Username:nokia Password:********

Expected outcome

The following options are displayed:
ESA12 Main Menu 1. General Configuration 2. SNMP Configuration 3. Ports Configuration 4. Ports Status 5. Load Factory Defaults 6. Software Upgrade 7. Reset 8. Logout

2.

Press 1 to select General Configuration from the menu The General Configuration menu shows the current settings.
Expected outcome

The General Configuration menu is printed on the command line.
General Configuration MAC address Agent IP Address : Agent Netmask : Default Gateway : Supervisor/Terminal Password : System Name : Advanced Features Main Menu 00 A0 12 0B 02 74 192.168.001.009 255.255.255.240 192.168.001.001

1. 2. 3. 4. 5. 6. 9.

3.

Press the number of the parameter you want to change
Expected outcome

The selected parameter row with the current settings is printed below the menu. 4. Use the backspace key to remove the current parameter value

36 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

5.

Enter the new value for the parameter and press Enter
Expected outcome

The General Configuration menu is printed on the command line. The menu shows the new settings.
Expected outcome

The session is interrupted immediately after you change the IP address. Change the IP address only after having changed all other parameters. Example Changing the default gateway in ESA12

This example shows how to change the default gateway in ESA12. 1. Establish a telnet connection to ESA12. In this example, the password has not been changed yet.
telnet 192.168.1.9 Username:nokia Password:

2. 3.

Press 1 to select General Configuration in the main menu. Press 3 to select Default Gateway. The current address is displayed on the command line:
Default Gateway : 192.168.1.1

4. 5.

Use the backspace key to remove the current parameter value. Enter the new value for the parameter and press Enter:
Default Gateway : 10.1.1.2

The new value is shown in the General Configuration menu:
General Configuration MAC address Agent IP Address : Agent Netmask : Default Gateway : Supervisor/Terminal Password : System Name : Advanced Features Main Menu 00 A0 12 0B 02 74 192.168.001.009 255.255.255.240 10.001.001.002

1. 2. 3. 4. 5. 6. 9.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

37 (240)

RNC Integration

3.5.2

Configuring ESA24
Purpose

This procedure describes how to configure the ESA24 Ethernet/LAN switch.
Before you start

Before you start the configuration, check the following:
.

The PC or laptop that you are using is connected to one of the Ethernet ports of the ESA24 switch with an Ethernet cable. The ESA24 Ethernet switch is powered up (the LED on the front panel of the switch is green).

.

Steps
1. Connect to the IP address of ESA24 via Telnet

Note
If connection to the IP address of ESA24 is via Telnet, the IP address will change to the given address by the command IP address X.X.X. X/x.x and the Telnet connection will stop responding. The initial configuration has to be done by the serial connection. See ESA24 10/ 100 Mbit Ethernet Switch User Guide for the detailed information. a. b. c. Start a Telnet session by selecting Start -> Run on the Windows Taskbar. Connect to the IP address of ESA24:
telnet <IP address of ESA24>

Press Enter.

Expected outcome

The system prompts for a password:
User Access Verification Password:

2.

Log in to ESA24

38 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

Enter the default password "nokia", or the new password if the password has been changed, and press Enter.
Expected outcome

After successful login, the ESA24 prompt is displayed:
ESA24>

3.

Enable RSTP or MSTP for ESA24, if necessary If you want to prevent cabling loops, enable the Rapid Spanning Tree Protocol (RSTP) or the Multiple Spanning Tree Protocol (MSTP) for ESA24. a. Plan the STP role of each LAN switch in the L2 broadcast domain area. b. Check that all LAN switches in the L2 broadcast domain area are running compatible STP versions. c. Configure the bridge priority of the STP root switch and configure all the links directly connected to computer units as edge ports. For more information, see ESA24 10/100 Mbit Ethernet Switch User Guide in PDF format in NOLS and Cable Lists and Use of ATM Links and LAN Connections in Site documents.

4.

Change to a privileged mode in BiNOS Enable the privileged mode in ESA24 operating system with the command
ESA24> enable

The privileged mode allows advanced viewing and configuration for the unit.

Note
The command prompt in privileged mode is the hash(#).

By default, the enable command does not ask for a password. It is possible to protect the administrator's rights with a password. See the ESA24 10/100 Mbit Ethernet Switch User Guide for more information.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

39 (240)

RNC Integration

5.

Change to configuration mode in BiNOS Enable the configuration mode in ESA24 operating system with the command
ESA24#configure terminal

6.

Set the IP address and netmask for ESA24
ESA24(config)#ip address <ip address>/<netmask>

7.

Set the default gateway for ESA24 Delete the existing default route before add new route.
ESA24(config)#no ip route 0.0.0.0/0 ESA24(config)#ip route <destination address>/ <destination network mask> <ip gateway address>

8.

Enable DHCP, if necessary
ESA24(config)#ip address dhcp

9.

Save the configuration
ESA24#write

Further information

To view information on the commands, enter ? in the ESA24 command prompt. To view more information on the syntax of a specific command, enter <command> ?. Example Configuring ESA24

This example shows how to configure ESA24. 1. Connect to the IP address of ESA24 via Telnet. a. Select Start -> Run on the Windows Taskbar. b. Connect to the IP address of ESA24:
telnet 192.168.1.9

c. Press Enter. The following prompt is displayed:

40 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

User Access Verification Password:

2.

Enter nokia and press Enter to log in to ESA24. After successful log in, the ESA24 prompt is displayed:
ESA24>

3.

Change to privileged mode.
ESA24> enable

4.

Change to configuration mode.
ESA24#configure terminal

5.

Set the IP address and netmask for ESA24.
ESA24(config)#ip address 192.168.0.5/28

6.

Set the default gateway for ESA24.
ESA24(config)#ip route 0.0.0.0/0 192.168.0.1

7.

Save the configuration.
ESA24#write

3.6
3.6.1

Configuring NEMU for DCN
Configuring NEMU for DCN
Purpose

To get NEMU fully integrated to the DCN, NEMU's default settings are configured to match current network environment.

Steps
1. Open the remote management application for NEMU Use Communication profile Internet (TCP). Give a NEMU computer name as a domain. For information security reasons, it is recommended to change the default user ID and/or password immediately after the first login.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

41 (240)

RNC Integration

For more information, see the instructions in NetOp remote access to NEMU and Configuring NetOp Guest in Network Element Management Unit. 2. Configure the DHCP server Refer to the instructions in Configuring DHCP server in NEMU. 3. Configure the DNS client and server data Refer to the instructions in Configuring DNS client and server in NEMU. 4. Configure NEMU to RNC Refer to the instructions in Configuring NEMU to RNC. 5. Configure the RUIM feature in NEMU Refer to the instructions in NemuRUIMConfiguration. 6. Configure the NTP server Refer to the instructions in Configuring NTP services in NEMU. 7. Finalise the SQL server configuration Refer to the instructions in Finalising SQL server configuration. 8. Define the IP address for NEMU according to the IP plan Refer to the instructions in Configuring IP address for NEMU.

3.6.2

Configuring DHCP server in NEMU
Purpose

The DHCP server is used for configuring IP hosts automatically. The DHCP client in an IP host sends a broadcast query to the network, where a DHCP server receives it. The DHCP server answers the client by returning its IP address and other parameters. The returned values have been saved in the DHCP server's database.

42 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

With the RNC, DHCP is used to distribute IP parameters to IP devices that have been locally attached to the RNC. An example of such a device is a PC that has the Element Manager running. The DHCP server is configured according to the IP plan. The DHCP server is needed because the PC in which the RNC Element Manager is running receives the IP parameters from the DHCP server of the NEMU. PC is not needed for configuring, but a standard DHCP can be used to configure the PC. However, this requires that the DHCP client is configured to the PC. See also the IETF's RFC 2136.

Steps
1. Open the DHCP manager of the managed NEMU Select Start -> Programs -> Administrative Tools -> DHCP. 2. Add a new local management scope for NEMU a. In the list of DHCP servers, select the DHCP server for which you want to create a new scope. b. Select Action -> New Scope. c. Enter the name of the scope. For example, Local Management. d. Enter the IP addresses and masks for the new scope according to the IP plan.

Note
If you have static IP addresses configured on non-DHCP clients (for example, NEMU), you must use the IP address pool that does not contain those IP addresses. If you use an IP address pool that contains those addresses, you must configure the Exclusion Range list on DHCP Scope. e. When the system asks you if you want to configure the DHCP options for this scope, answer No.

3.

Delete the old local management scope a. Under the server, select the old management scope (192.168.1.0). b. Select Action -> Delete. Modify the DHCP options according to the IP plan

4.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

43 (240)

RNC Integration

a. b.

Under the server, select Server Options -> Action –> Configure Options. Modify the Router, DNS server, DNS Domain Name, and NTP Servers as required.

5.

Activate the new local management scope a. Under the server, select the new local management scope. b. Select Action -> Activate.

3.6.3

Configuring DNS client and server in NEMU
Purpose

This section describes how to create a DNS server to the NEMU server (Windows 2000), and how to configure primary and secondary servers. Creating the DNS server to the NEMU server does not require any sofware installations because the DNS server is installed in NEMU by default. Only a new DNS zone needs to be activated and created. The Domain Name System (DNS) is a distributed database which maps hostnames and IP addresses. DNS servers are needed to enable the use of DNS names (for example, nemu.rnc1.netct.operator.com) instead of IP addresses. The DNS management server is the primary server (Master name server) of the zone. Servers in the network are secondary servers. This means that DNS information is managed in the DNS management server and the secondary servers automatically update their DNS databases from the management server. DNS servers in the network are authoritative for their zone, so they handle the DNS queries concerning the zone.

44 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

Nokia NetAct
DNS management server

ZONE transfers

Secondary DNS server

RNC

DNS queries

Element Manager

BTS

DNS queries
BTS Element Manager

BTS RNS DCN

Figure 4.

DNS architecture

The DNS management server is located in the Nokia NetAct. All the RNC NEMUs have a secondary DNS server, which updates its information from the DNS management server. The updating is normally controlled by the DNS management server (see the DNS Notify RFC 1996 by the IETF). If there is no Nokia NetAct, one NEMU is configured as the primary server, which the secondary servers use to update their information. See also the IETF's documents RFC 1034 and 1035. The primary server is configured according to the IP plan.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

45 (240)

RNC Integration

Steps
1. Configure the DNS client data a. Select Start -> Settings -> Network and Dial-Up Connections. b. Right-click Local Area Connection 3 and select Properties. c. On the General tab, select Internet Protocol (TCP/IP). d. Select Properties -> Advanced -> DNS. e. Edit the address(es) of the DNS server(s) and set the search order, if necessary. f. Click OK -> OK -> OK ->OK-> NO to apply the changes. g. Select Start -> Programs -> Administrative tools -> Services. h. Select Workstation Service. i. In Action menu select Start. j. Close Service window. k. Select Start -> Settings -> Control Panel. l. Double-click the System icon. m. On the Network Identification tab, select Properties. n. Enter the name of the computer and click More Write down the original name of the computer as you will need it when running the SQL script. See Finalising SQL server configuration. o. Enter the primary DNS suffix. p. Click OK -> OK -> OK -> OK to apply the changes. q. If computer name was changed, restart is required before running sqlnamefix script. See Finalising SQL server configuration. Start and check the DNS service a. Select Start -> Settings -> Control Panel -> Administrative tools -> Services -> DNS Server. b. Select Action -> Properties. c. Click Start. d. Change the current status to 'Automatic'. Start the DNS manager Start the DNS manager from Start -> Programs -> Administrative tools -> DNS. 4. Add a new secondary or primary DNS zone to the server To add a new secondary DNS zone to the server:

2.

3.

46 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

a. b. c. d. e.

f.

g. h.
Or

In the list of DNS servers, select the server to which you want to add the new zone. Select Action -> New Zone. Select Standard secondary as the zone type. Select Forward lookup zone. Enter the zone name according to the IP plan. The zone name is the end part of the computer name. For example, if the name of the NEMU is nemu.rnc1.nokia.com, the zone name is then rnc1.nokia.com. Enter the IP address of the master server according to the IP plan. Zone information is refreshed when the secondary server has a connection to the master server. Select Action -> Properties -> Forwarders. Select Enable Forwarders and add the IP address of the master DNS server.

To add a new primary DNS zone to the server: a. In the list of DNS servers, select the server to which you want to add the new zone. b. Select Action -> New Zone. c. Select Standard primary as the zone type. d. Select Forward lookup zone. e. Enter the zone name according to the IP plan. The zone name is the end part of the computer name. For example, if the name of the NEMU is nemu.rnc1.nokia.com, the zone name is then rnc1.nokia.com. f. Accept the default zone file name. g. Repeat steps from b to f for each zone. 5.

If you added a primary DNS zone to the server Then
Create the DNS domains and hosts according to the IP plan a. In the list of the server's Forward lookup zones, select the zone for which you want to create the DNS domain. b. Enter the name of the domain. For example, wbts1. c. To create a new host, select Action -> New Host. Enter the name of the NEMU server, for example nemu, and the corresponding IP address. d. Repeat steps b and c for each domain and host according to the IP plan.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

47 (240)

RNC Integration

6.

Update the data files of the server Select Action -> Update Server Data File.

7.

Check that the DNS service configuration succeeded, if necessary Use Nslookup to check that the configuration was successful.

Note
The Nslookup only works after the RNC integration is completed.

8.

If a preconfigured IP address is used, delete the server a. In the list of DNS servers, select the server that has the preconfigured IP address. b. Select Action -> Delete.

Expected outcome

The DNS server should now be up and running.

3.6.4

Configuring NEMU to RNC
Purpose

The External Message Transfer (EMT) connection between NEMU and OMU requires that the Win2000 registry includes the IP address of OMU and the user ID and password of the network element. The user ID and password have been defined in the network element for the EMT connection. The IP address of the NEMU and the FTP username and password also have to be defined for measurement bulk data transfer. Any NEMU username and password can be used for NEMU FTP. The network element must have a user ID that the EMT, Telnet and FTP connections can use.
Before you start

The following user accounts have to be created to NEMU:

48 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

.

NEMU FTP user (for example NEMUFTP) NWI3 user

.

Note that the NWI3 user must be the same as defined in the NetAct maintenance region to which the NEMU belongs. For instructions on creating user accounts, see Creating a new EM user in Element Manager Administration.

Tip
Create a new EM (Element Manager) user to the Users group.

The following table lists the NEMU registry variables used when configuring NEMU for RNC connection:

Table 6. Variable

RNC data in NEMU registry Data
NE-RNC-<id>, where the <id> must be within the range 1 - 4095. As configured in Configuring IP stack in OMU. As configured in Checking IP address for NEMU. The NEMUAD user ID created in Creating MMI user profiles and user IDs for remote connections to NetAct. The NEMUAD user password created in Creating MMI user profiles and user IDs for remote connections to NetAct. The NEMUAD user ID created in Creating MMI user profiles and user IDs for remote connections to NetAct. The NEMUAD user password created in Creating MMI user profiles and user IDs for remote connections to NetAct. The NEMUAD user ID created in Creating MMI user profiles and user IDs for remote connections to NetAct. The NEMUAD user password created in Creating MMI user profiles and user IDs for remote connections to NetAct.

Base identifier of RNC OMU's IP address NEMU's IP address EMT UserName

EMT Password

OMU FTP Username

OMU FTP Password

OMU Telnet UserName

OMU Telnet Password

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

49 (240)

RNC Integration

Table 6. Variable

RNC data in NEMU registry (cont.) Data
The name of the service user with NEMU FTP Access (for example, NEMUFTP) as defined in Creating a new EM user in Element Manager Administration. The password for the NEMU FTP user as defined in Creating a new EM user in Element Manager Administration. The NetAct NWI3 Access account username. The NetAct NWI3 Access account password. The host name of NEMU. For example: NEMU-2. The Network Management's Registration IOR (RSIOR) in NetAct

NEMU FTP UserName

NEMU FTP Password

NEMU Registration Account Username NEMU Registration Account Password NEMU ID Network Management’s Registration IOR (RSIOR)

Summary

To enable FTP connection from the NEMU to RNC, you must define OMU FTP user ID for the NEMU connection. To enable Telnet connection from the NEMU to RNC, you must define OMU Telnet user ID and password for the NEMU connection.

Steps
1. 2. 3. Open the Command Prompt from Start -> Run Type NemuRegEdit, and click Enter See further instructions in NemuRegEdit

3.6.5

NemuRegEdit
You can add network elements to NEMU by using the NemuRegEdit command line tool. The NEMU platform setup executes NemuRegEdit. The NemuRegEdit tool writes the entered information to the Windows register.

50 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

Note
If OMU FTP, OMU Telnet, or EMT passwords or username are changed on the managed element side, the same changes must also be done on the NEMU side.

Start NemuRegEdit

Start NemuRegEdit by entering the command NemuRegEdit in a command prompt window. When NemuRegEdit is started, it shows the current configuration settings from NEMU and asks if you want to change them:
.

Are the current managed network elements settings OK (Y/N)? If the settings are correct, select Yes and press any key to continue. If something must be changed, select No. You can perform the following actions: . To modify the default network element settings, select Modify (M). If you select modify (M), NemuRegEdit prompts you to enter the number of the network element: Enter the number of network element you wish to modify and press <enter>, or <0> + <enter> to cancel? After this, continue from BaseId of managed network element. . If you do not want to change the current configuration settings, select Cancel (C). Then continue from Printing the information of the default network element.

BaseId of managed network element
.

Insert the baseId of the managed network element: NE-RNC-1 BaseID is a name for a network element, for example, NE-RNC-1.

Type of managed network element
.

Insert the type of managed network element: RNC

IP address of Network element
.

Insert the logical IP address of the OMU unit of the managed network element: 192.168.12.1

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

51 (240)

RNC Integration

Printing network element information

Given network element [NE-RNC-1] information:
.

baseID: NE-RNC-1 typeID: RNC IP address: 192.168.12.1 Is this correct (Y/N)?

.

.

.

Check the given information and select Y/N. Then enter 1 to select the default network element.
Printing the information of the default network element

You selected [NE-RNC-1] as the default network element:
.

Type: RNC IP address: 192.168.12.1 Default Network element set OK.

.

.

NemuRegEdit asks the following question:
.

Are current managed network element settings OK? (Y/N) ? If the settings are correct, select Y and press any key to continue.

NemuRegEdit shows the current network element settings from NEMU and asks the following question:
.

Are current NEMU settings OK (Y/N)? If the settings are correct, select Yes and press any key to continue. If something must be changed, select No. NemuRegEdit then prompts you to modify the settings again.

IP address of NEMU

Enter the IP address of NEMU. Press ENTER if the current value is OK.
.

NEMU IP address [STRING] current value: 10.12.17.123 NEMU IP address [STRING] new value: 192.168.17.1

.

52 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

EMT UserName

Enter EMT UserName. Press ENTER if the current value is OK.
.

EMT UserName [STRING] current value: SYSTEM EMT UserName [STRING] new value: NEMUAD

.

EMT Password

Enter EMT Password and press ENTER.
.

EMT Password [STRING] new value: ****** Give the current password for NEMUAD.

OMU FTP UserName

Enter OMU FTP UserName. Press ENTER if the current value is OK.
.

OMU FTP UserName [STRING] current value: SYSTEM OMU FTP UserName [STRING] new value: NEMUAD

.

OMU FTP Password

Enter OMU FTP Password and press ENTER.
.

OMU FTP Password [STRING] new value: ****** Give the current password for NEMUAD.

OMU Telnet UserName

Enter OMU Telnet UserName. Press ENTER if the current value is OK.
.

OMU Telnet UserName [STRING] current value: SYSTEM OMU Telnet UserName [STRING] new value: NEMUAD

.

OMU Telnet Password

Enter OMU Telnet Password and press ENTER.
.

OMU Telnet Password [STRING] new value: ****** Give the current password for NEMUAD.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

53 (240)

RNC Integration

NEMU FTP UserName

Enter NEMU FTP UserName. Press ENTER if the current value is OK.
.

NEMU FTP UserName [STRING] current value: SYSTEM NEMU FTP UserName [STRING] new value: NemuFTP

.

NEMU FTP Password

Enter NEMU FTP Password and press ENTER.
.

NEMU FTP Password [STRING] new value: ****** Give the current password for NemuFTP.

Registration Account UserName

Enter Registration Account UserName and press ENTER. When you press ENTER, the 'Value set OK' message is shown.
.

Registration Account UserName [STRING] new value: neregn

Registration Account Password

Enter Registration Account Password and press ENTER.
.

Registration Account Password [STRING] new value:****** Give the current password for neregn.

NEMU ID

Enter NEMU ID. Press ENTER if the current value is OK.
.

NEMU ID [STRING] current value: NEMU-1 NEMU ID [STRING] new value: NEMU-2

.

Network Management's Registration IOR (RSIOR)

Enter Network Management's Registration IOR (RSIOR). If you do not want to set a value, press ENTER.
.

Network Management's Registration IOR new value: IOR:12345678910111213141516 Is this correct (Y/N)?

.

54 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

If the value is correct, select Y. The 'Value set OK' message is shown. If the value is not correct, select N. Network Management's Registration IOR new value.
Exit NemuRegEdit

Press any key to exit NemuRegEdit.

Note
Configuration changes do not take effect until NEMU software is restarted. If the computer is restarted after the NEMU integration is finished, the NEMU software does not need to be restarted. NEMU software restart can be done with the NEMU Platform Manager User Interface in the following way: 1. 2. 3. 4. 5. 6. Start the NEMU Platform Manager User Interface from Start > Programs > NEMU Platform Manager User Interface > PMUI. Click Stop PM. Wait until the status of the Platform Manager is 'Platform Manager not running'. Click Start PM. Wait until the status of the Platform Manager is 'NEMU software Running'. Close NEMU Platform Manager User Interface.

3.6.6

NemuRUIMConfiguration
If the Remote User Information Management (RUIM) feature is used in the system, follow the instructions below to configure NEMU. RUIM is supported by NetAct version OSS4.1 CD set 1. Remote User Information Management (RUIM) feature requires that configuration data of the centralised authentication servers are set into NEMU.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

55 (240)

RNC Integration

The user can do the configuration settings of RUIM feature with NemuRUIMConfiguration.exe tool. This tool is run during the setup, but it is also possible to run it later to modify the configuration settings of RUIM. The tool can be found from the path:
E:\nemu\platform\active\apps

The state and authentication order of RUIM is stored into the following path in the Windows register:
HKEY_LOCAL_MACHINE\SOFTWARE\Nokia\NEMU \InstalledModules \System\Network\CUAccess\NEMU \CurrentVersion\settings

IP address, port, the user base entry, and the configuration base entry of primary and secondary LDAP servers are stored in the nwi3MDCorba.ini file in the folder:
E:\NEMU\data_area\platform\active\c_services \nemucorbasupserv\nwi3MDCorba Parameters required for starting the NemuRUIMConfiguration.exe

Use the NemuRUIMConfiguration.exe as follows:
.

View configuration data: NemuRUIMConfiguration.exe <give status file path and name here> -view For example: NemuRUIMConfiguration.exe c:\temp \ruimConfigStatus.txt -view

.

Modify or insert configuration data: NemuRUIMConfiguration.exe <give status file path and name here> -upgrade/-install/-uninstall For example insert (install) configuration data: NemuRUIMConfiguration. exe c:\temp\ruimConfigStatus.txt -install

You can define the status file name and location (path) freely. The status file contains the status information about the execution. If the execution fails, the errors can be found from the status file. The questions NemuRUIMConfiguration asks from the user when install option is used:
Do you want to insert/modify configuration settings of RUIM (Y/N)?
.

Y(es)/N(o)

56 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

.

Ensure that you want to insert/modify the RUIM configuration settings.

The state of RUIM is disabled/enabled. RUIM State value is: 0/1/2 Give the new value or press ENTER:
.

Tells the current status of the RUIM state and requests a new status value. If the current status value is preferred, press ENTER. Possible RUIM state values are: . Value 0 = RUIM is disabled. Authentication mode: local . Value 1 = RUIM is enabled. Authentication mode: remote/local . Value 2 = RUIM is enabled. Authentication mode: local/remote

.

Note that it is recommended that RUIM is disabled until the NE account information to NEMU is sent successfully. Also note that with RUIM enabled, the NEMU can use both authentication methods, local: local user database, and remote: remote user database, the LDAP server. The authentication mode tells in which order these authentication methods are used in order to authenticate the user.
Please, select the instance you want to modify (A=currently active, N=next to be activated, B=both)?

Note that only one instance can be active at a time. If the instance is active, its configurationActive attribute is 1, otherwise it is 0.
.

A (currently active) After NemuRUIMConfiguration has quit, the RUIM configuration settings are taken into use immediately. This option is usually used when the RUIM feature is enabled the first time after the NEMU setup. Usually there should be at least one instance in the nwi3MDCorba. ini file after the NEMU setup. If the existing instance is not active, the user is asked to set the takeIntoUseNext parameter value to 1 in the nwi3MDCorba.ini file. For setting the required parameter in nwi3MDCorba.ini file, see Configuring Nokia NetAct interface with NEMU. Remember to restart the NemuRegServApp process after the parameter setting.

.

N (next to be activated) After NemuRUIMConfiguration has quit, the RUIM configuration settings are taken into use after these steps:

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

57 (240)

RNC Integration

1. 2. 3. 4.

Open the nwi3MDCorba.ini file Change the takeIntoUseNext to 0 in the currently active instance Change the same parameter to 1 in the next instance Close the file. Restart the NemuRegServApp process. For more information, see Configuring Nokia NetAct interface with NEMU.

.

B (both) The configuration settings are set to both existing instances (active and next to be activated). The changes are taken into use immediately in the active instance. After the RegServApp restart (see active processes in NEMU Platform Manager UI), the changes are taken into use in the next to be activated instance.

When RUIM is enabled, it is possible to configure two instances of RUIM configuration attributes. If you have for example two different NetAct manager instances, you can define registration attributes for both of them to NEMU (registration username and password, and registration IOR). In the same way, both NetAct manager instances have their own LDAP configuration attributes, which can be configured to NEMU at the same time. All these attributes are stored into the nwi3MDCorba.ini file. Note that if the requested instance does not exist, NemuRUIMConfiguration informs you about it. The instances must be created by NetAct.
Give the IP address of Primary LDAP server
.

Insert value: . Give the IP address of Primary LDAP server. If a value is not given the rest of the values are not questioned. Example: 11.11.11.11

.

Give the Port of Primary LDAP server
.

Insert value: . Give the port of Primary LDAP server. If a value is not given the rest values are not questioned. Example: 389

.

58 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

Give the PrimaryPeopleRootDN of the LDAP server
.

Insert value: . Give the PrimaryPeopleRootDN (User Base Entry) of the LDAP server. Example: ou=People, dc=labra, dc=tieto, dc=com:

.

Give the name of the Primary configuration entry of the Primary LDAP server
.

Insert value: . Give the name of the Primary configuration entry of the Primary LDAP server. Example: cn=NEMU, ou=LDAPconfData, dc=labra, dc=tieto, dc=com

.

Do you want to configure backup server in use? (Y/N) - Y(es)/N(o) Give the IP address of the Secondary LDAP server
.

Insert value: . Give the IP address and port of the Secondary LDAP Server. If a value is not given, the rest values are not questioned. Example: 11.11.11.11

.

Give the port of the Secondary LDAP server
.

Insert value: . Give the port of the Secondary LDAP server. If a value is not given, the rest values are not questioned. Example: 389

.

Give the SecondaryPeopleRootDN of the LDAP server
.

Insert value: . Give the SecondaryPeopleRootDN (User Base Entry) of the LDAP server. Example: ou=People, dc=labra, dc=tieto, dc=com:

.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

59 (240)

RNC Integration

Give the name of the configuration entry of the Secondary LDAP server
.

Insert value: . Give the name of the configuration entry of the Secondary LDAP Server. (This question is asked if the IP address of the Secondary LDAP Server is given.) Example: cn=NEMU, ou=LDAPconfData, dc=labra,dc=tieto,dc=com

.

The upgrade option is used when the existing RUIM configuration data in NEMU needs to be changed. If the upgrade option is used, NemuRUIMConfiguration asks the same questions that in the install option, but in every configuration value NemuRUIMConfiguration displays the existing value and asks whether to update, keep, or delete it. For example the IP address of the LDAP server:
IP address of the Primary LDAP server is: 11.22.33.44 Select U/K/D: Update the value (U), Keep the old value (K), Delete the value (D):

If U (update the value) is selected, NemuRUIMConfiguration asks the new value:
.

Give the new value: If K (keep the old value) is selected, NemuRUIMConfiguration keeps the current value. If D (delete the value) is selected, NemuRUIMConfiguration deletes the current value. NemuRUIMConfiguration goes through all the existing RUIM configuration values in this way in upgrade option.

3.6.7

Configuring NTP services in NEMU
Purpose

Nokia makes the default NTP settings in Tardis, so you can normally use Tardis services without any modifications. However, if you need to change any settings, follow the instructions below. Tardis can be found in the Control Panel.

Steps
1. Set Tardis to automatically change servers

60 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

a. b.

Select the General tab in Tardis. Edit the settings as required. Select Automatically change servers on failure to set Tardis to automatically change to a different server if it cannot contact the one currently selected. Tardis will cycle through all the servers in the list. Select Automatically change servers on success to set Tardis to automatically change to a different server if it successfully contacts the one currently selected. Tardis will cycle through all the servers in the list. This is useful as a way of checking which servers are active.

2.

Add NEMU time servers a. Select the Main tab in Tardis. b. To add a new time server, click Add. The Server details dialog opens. c. Enter the address of the time server. Enter the address as a name or as an IP address. When using the Network Time Protocol (NTP), the address may be left blank in which case Tardis will listen to any broadcasts. If an address is entered, Tardis will only listen to broadcasts from that machine. d. Enter a descriptive name of the server. If you do not enter a name, the address of the server is used instead. e. Enter the protocol used by your time server: . Simple Network Time Protocol (SNTP) is used in NEMU. It is the standard way to synchronise computer clocks. . HTTP protocol may be required if you are using a firewall/proxy and have no time servers on your LAN. . NTP broadcast protocol is a choice if you have an NTP server on your LAN. It can be configured to broadcast time information. Tardis will listen for these broadcasts if you use this protocol. NTP broadcast is not used in NEMU domain. f. If you want Tardis to reject time information from NTP servers that claim to be unsynchronised, select Reject unsynchronized NTP. This can happen if the server has lost touch with its time source. Modify NEMU time server settings

3.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

61 (240)

RNC Integration

a. b. c.

Select the Main tab in Tardis. Double-click the name of the server you wish to modify. Edit the time server settings in the Server details dialog (see the previous step for details).

4.

Set the system time in NEMU a. Select the Setting the time tab in Tardis. b. Select Set the time and adjust the scales as required. If you do not initially trust the server you are connecting to, do not set the system time. This gives you a chance to see first what kind of time it is going to give you without accidentally setting NEMU's time to, for example, 10:61 77 Jan. 1914. Set the time zone and daylight saving time Select Set Timezone. It opens the Control Panel for Date and Time where you can set up your timezone and whether you use daylight saving time or not.

5.

Note
Timezone and daylight saving time (DST) must be configured in the same way both in NEMU and in RNC. This is because RNC uses local time (which includes timezone and DST) in its time stamps while NEMU uses its own timezone and DST settings when it sends events to Nokia NetAct via NWI3 interface. If the timezone and DST are configured differently in NEMU and RNC, the alarm time stamps will not be correct between NetAct and RNC.

Tip
You can view the RNC settings with the DCD command and change them with the DCS command. If the NEMU clock is automatically adjusted to DST changes in the Control Panel for Date and Time dialog (default), change the RNC DST setting with the DCT command. This is needed because RNC does not support automatic adjustment for DST changes.

62 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

Note
In certain situations, it is possible that the time stamps of the RNC alarms are different in NetAct and in RNC. If the NEMU clock is automatically adjusted to DST changes but the corresponding DST change is not done in RNC, all alarms are affected. This also affects the alarms that were generated before the DST change even if the DST change was configured at the same time in RNC and NEMU. To prevent this kind of problem, it is recommended not to use DST time in RNC and automatic DST adjustment in NEMU.

6.

Set the HTTP proxy firewall address Tardis may need to know the settings of the proxy server to work with the HTTP protocol. a. Select the HTTP proxy settings tab. b. Enter the address of the HTTP proxy firewall. Enter the name or IP address of the proxy/firewall server. You can omit the http:// prefix. c. Enter the port number of the HTTP proxy firewall. d. Set the authorisation requirements. Select User name and password needed if the proxy/firewall requires authentication. Enter the username and password.

Example

Configuring Tardis for RNC

This example shows what you need to configure in Tardis during RNC integration. 1. 2. 3. 4. Open Tardis by selecting Start -> Control Panel -> Tardis. Go to the main menu by selecting the Main tab. Click Add to add a new time server. The Server details dialog opens. Enter the address, name, and protocol of the time server. The address depends on your configuration, the name you can freely choose, and the protocol is SNTP. Go to the time menu by selecting the Setting the time tab. Select Set the time and set the scales to default values. Select Set Timezone. Choose the time zone where you are located and whether you use daylight saving time or not.

5. 6. 7.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

63 (240)

RNC Integration

3.6.8

Finalising SQL server configuration
Purpose

This chapter describes how to finalise the Microsoft SQL Server configuration. This is required because after you change the computer name according to the instructions in Configuring DNS client and server in NEMU, the old computer name is not updated in SQL.

Steps
1. Log on to Windows Log on to Windows using the Nemuadmin account. 2. 3. Execute updatesql.bat from C:\temp\sqlnamefix Follow the instructions in updatesql.bat Updatesql opens instructions window, follow the instructions. 4. Open SQL Server Enterprise Manager When updatesql has completed open Enterprise Manager from Start -> Programs -> Microsoft SQL Server-> Enterprise Manager. 5. 6. 7. 8. 9. Expand Microsoft SQL Servers from tree view Expand SQL Server Group from tree view Expand Local SQL Expand Security/Logins from local SQL Check the computer name of the nemuadmin account In the logins list, there is a computer name before the nemuadmin account. For example, NEMU-012345/nemuadmin. Check the computer name has been replaced by the new computer name introduced in Configuring DNS client and server in NEMU. If the computer name has been changed, close the Enterprise manager.

64 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

Example If the computer name is NEMU-012345, login is NEMU-012345/ Nemuadmin.

Figure 5.

Computer name and nemuadmin account

10.

If the nemuadmin account has a computer name that does not match the current NEMU computer name Then
Create a new nemuadmin login for SQL a. Delete the nemuadmin account with the computer name (rightclick it and select Delete). Confirm deletion by clicking Yes. b. Click the new login icon and then click the name browse button. c. Select Nemuadmin to the name field, then click Add and OK. d. Insert language.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

65 (240)

RNC Integration

e. f.

Go to the Server roles tab, select System Administrators and click OK. Close SQL Server Enterprise Manager.

Further information

Sometimes MCC is known to crash, presenting an error popup on the screen and SQL update script loses sync. In such a case, click OK error popup and open SQL Server Enterprise Manager from Start -> Programs -> Microsoft SQL Server -> Enterprise Manager. 1. 2. 3. 4. Expand SQL Server Group from tree view. Expand Local SQL. Right-click the SQL Server group icon and select Delete SQL Server Registration. Click Yes. Add NEMU's name. Select New SQL Server Registration from Action menu and click Next. Choose NEMU's name from the servers list and click Add and then Next, Next, Finish and finally Close. 5. Close SQL Server Enterprise Manager.

3.6.9

Configuring IP address for NEMU
Purpose

The initial IP configuration has to be done locally. You only need to configure the IP address and the subnetwork mask of NEMU. However, if preconfigured IP addresses are in use in NEMU, initial configuration can also be done via the remote management application.

Steps
1. 2. 3. 4. 5. 6. Select Start -> Settings -> Network and Dial-Up connections Double-click Local Area Connection 3 Click Properties Select Internet Protocol (TCP/IP) and click Properties Enter the correct IP address Enter the correct subnet mask

66 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

7. 8.

Enter the default gateway Click OK -> OK When you are configuring RNC NEMU via a remote management application, the connection closes when you click OK the second time and you lose the remote session to NEMU. If that happens, refresh the DHCP client before continuing. If you are configuring RNC NEMU via a local connection, refresh DHCP client only after restarting NEMU.

9.

If you lost connection to NEMU Then
Refresh the DHCP client of the computer Refreshing of the DHCP client of the computer depends on the operating system: . In Windows NT/2000: a. Open the command prompt from the Start -> Programs menu. b. Enter ipconfig /release and press Enter. c. Enter ipconfig /renew and press Enter. . In Windows 95/98: a. Open the command prompt from the Start -> Programs menu. b. Enter winipcfg /release_all and press Enter. c. Enter winipcfg /renew_all and press Enter. . In other operating systems, refer to the instructions for the system.

10.

If you are configuring RNC NEMU remotely Then
Open the remote management application for NEMU Enter the IP address of the NEMU server to the target address.

11.

Restart the computer Click Close. If prompted, click Yes to restart the computer or select Start -> Shut Down -> Restart.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

67 (240)

RNC Integration

3.7
3.7.1

Configuring external IP connections
Connecting to O&M backbone via Ethernet
Purpose

This procedure describes how to connect RNC to the external network for O&M connections using an external router connected to the ESA12 or ESA24 Ethernet switch. O&M connections from the RNC to the O&M backbone can also be created via ATM virtual connections, but Ethernet is the preferred way. The O&M connection via ATM should only be used as a backup.

Note
Even if the IP over ATM connection has been configured, the O&M traffic does not automatically switch to using it when the Ethernet connection is down.

Before you start

Because the IP addresses for OMU, the Ethernet switch, and NEMU have been preconfigured in the RNC, you must change the IP addresses before connecting the RNC to the external network. Several elements in the network can have the same preconfigured IP addresses, so if you do not change the preconfigured addresses, there will be problems in the network. For instructions, see Configuring IP for O&M backbone (RNC — NetAct).

Steps
1. Connect the RNC physically to the external router via ESA12/ ESA24 Ethernet switch Configure external router according to instructions provided by the router vendor

2.

68 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring IP for O&M backbone (RNC - NetAct)

3.7.2

Configuring IP over ATM interfaces
Purpose

For O&M connections towards NetAct, IP over ATM interfaces for OMU are only required if the RNC is connected to the external network via ATM virtual connections. The preferred way to connect RNC to NetAct is via Ethernet (see Connecting to O&M backbone via Ethernet). The IP over ATM connection should only be used as a backup.

Note
Even if the IP over ATM connection has been configured, the O&M traffic does not automatically switch to using it when the Ethernet connection is down.

IP over ATM interfaces must be configured in GTPU units for Iu-PS interface between the RNC and the SGSN, and in OMU units for BTS O&M between the RNC and the BTS/AXC.
Before you start

ATM resources must be created before this procedure is commenced. For instructions, see Creating ATM resources in RNC in ATM Resource Management.

Steps
1. Interrogate the states of the units in the system (USI) Check that the units for which you are going to create network interfaces are in working or spare state (WO-EX or SP-EX). ZUSI:<unit type>; 2. Configure IP over ATM interface to the functional unit (QMF) ZQMF:<unit type>,[<unit index>],<logical/physical unit>:<IP interface>:<ATM interface>,<VPI number>, <VCI number>:[<encapsulation method>],[<usage | IPOAM def>];
ATM interface, VPI number and VCI number are the values given in

the commands of creating ATM resources.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

69 (240)

RNC Integration

The encapsulation method can be LLC/SNAP or VCmux. If Inverse ATM ARP is needed on this IPoA interface, the encapsulation method should be LLC/SNAP. 3. Assign IP addresses to the interfaces Defining the destination IP address creates a static route in the routing table for the IP interface.

Note
The destination IP address parameter is always mandatory.

For IPv4: ZQRN:<unit type>,<unit index>:<interface name>, [<point to point interface type>]:[<IP address>],[<IP address type>]:[<netmask length>]:[<destination IP address>]:[<MTU>]:[<state>]; For IPv6: ZQ6N:<unit type>,<unit index>:<interface name>:[<IP address>]:[<prefix length>]:[<destination IP address>];

70 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating NEMU

4
4.1

Integrating NEMU
Configuring NEMU system identifier (systemId)
Purpose

This procedure configures the system identifier of NEMU. The systemId has to have the same value as the identifier of the network element (for example, systemId = NE-RNC-'rnc_id'). In this scenario, the system consists of a managed network element and NEMU, which is logically seen as part of network element itself. In this case, system identifier and network element identifier are all the same.

Note
The systemId value must be chosen between 1 - 4095.

Make sure that the systemId is configured correctly, otherwise there can be problems in sending notifications to the NetAct. Note also that the systemId must be unique in the whole network.

Steps
1. Open %NEMUWWWROOT%\systemid.txt file to NOTEPAD editor The value between % marks refers to an environment variable. For example, %NEMUWWWROOT% means that there is an environment variable NEMUWWWROOT in the system. 2. Add value of the systemId to the file

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

71 (240)

RNC Integration

The value could be for example NE-RNC-'rnc_id' or MD-SITE'number'. The value must be chosen between 1 - 4095, for example NE-RNC-'1' 3. Save the file

4.2

Configuring the RNC object
Purpose

When the RNC RNW Object Browser is first taken into use after commissioning, the very first task is to configure the RNC by setting the required parameters. This is done because the RNC object is the topmost object in the hierarchy, and so it has to be created first. Please note that the RNC RNW Object Browser provides online help to assist you in carrying out the tasks. You can access the online help by clicking the Help button in the RNC dialogue.

Note
If this initial phase of the configuration is not successful, the user cannot proceed with the rest of the configuration tasks.

Steps
1. Open the RNC RNW Object Browser. A dialogue appears indicating that the RNC has not been configured. 2. Click OK. The RNC dialogue appears. 3. Configure the RNC. Enter values at least for the obligatory parameters marked with yellow. For more information on parameters, see WCDMA RAN Parameter Dictionary.

72 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating NEMU

Note
You cannot change the value of RNC identifier afterwards.

4.

Click OK to confirm operation.

Expected outcome

The general parameters of the RNC have been set.
Unexpected outcome

If in any phase of the configuration an error occurs, you must acknowledge it by clicking OK. The parameter window where the error occurred is displayed, and you can either modify the parameters and try again or cancel the operation.

4.3

Configuring Nokia NetAct interface with NEMU
Purpose

This procedure instructs you to configure the connection from NEMU to Nokia NetAct.

Steps
1. Check that CORBA/IIOP and Session Manager are running Open the Task Manager in NEMU from Start -> Run -> taskmgr (or press Ctrl+Alt+Delete and click Task Manager). Check that CORBA/ IIOP (orbixd.exe) and Session Manager (Nwi3SessionManager.exe) are up and running. 2. Define the system identifier in NEMU The system identifier attribute (systemId) has to be defined in the NEMU commissioning. The systemId attribute has been saved to the text file whose location is defined in Windows 2000 registry [HKEY_LOCAL_MACHINE\SOFTWARE\Nokia\NEMU \InstalledModules\c_services\nemucorbasupserv\NWI3MDCorba \CurrentVersion\Settings]. 3. Setup the required NetAct parameters to the INI-file (Nwi3MDCorba.ini) in NEMU

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

73 (240)

RNC Integration

a.

b.

Configure the NetAct parameters for NEMU. i. Open %NEMUPLATFORMDATADIR%\c_services \nemucorbasupserv\nwi3mdcorba\NWI3MDCORBA.ini file in, for example NOTEPAD editor. The value between % marks refers to an environment variable. For example %NEMUPLATFORMDATADIR% means that there is an environment variable NEMUPLATFORMDATADIR in the system. ii. Add the value of the stringfield IOR to the registrationServiceIOR field. (This could have been set during setup, otherwise you can add it directly to the file.) iii. Set the values of the registrationServiceUsername and registrationServicePassword with NemuRegEdit tool. (These could have been set during setup. Values are encrypted and stored into Windows Registry.) iv. Add value of the takeIntoUseNext parameter. This value must be changed to 1. v. Save the file. Restart the registering service of NEMU to activate new parameter values. There are two alternative methods to activate parameters. . Immediate activation: i. Start NEMU Platform Manager User Interface (Start -> Programs -> NEMU Platform Manager User Interface -> PMUI). ii. Select NemuRegServApp from the list of Nonstop Processes and click the Stop Process button. iii. Wait until the status of NemuRegServApp is Stopped. iv. Select again NemuRegServApp from the list of Nonstop Processes and click the Start Process button. v. Wait until the status of NemuRegServApp is Running. vi. Close NEMU Platform Manager User Interface. . Long time activation: i. The registering service of NEMU makes the registration itself after a variable period (usually the default random period is approximately 10-20 minutes).

4.

Check entries from the registering service of NEMU

74 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating NEMU

Check from the Windows 2000 Event Viewer if there are entries from the registering service of NEMU (NemuRegServ.dll). If there is a log writing "NemuRegServ: Getting the IOR of the Registration service failed.", the registering service of NEMU did not manage to get rsIOR which is needed for registering in Nokia NetAct. When the registering service of NEMU is up and running, there is a log writing "NemuRegServ: Successfully registered to registration service of NetAct."

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

75 (240)

RNC Integration

76 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring heartbeat interval for RNC

5

Configuring heartbeat interval for RNC
Purpose

The management plane connections between Nokia NetAct and RNCs are supervised with heartbeat (HB) alarms from the RNCs. Nokia NetAct uses the heartbeat alarm from the RNC to supervise the connection in desired intervals. By configuring the heartbeat interval, the user can change the supervision interval to correspond to the actual network environment.

Note
Changing the HB interval locally in the RNC MML interface is only needed if Nokia NetAct support is not available for this feature.

Steps
1. Check the heartbeat interval value. ZWOI:16,8; 2. Configure the heartbeat interval value. ZWOC:16,8,<value in minutes>;

Note
The scope of the heartbeat interval value is 0~0x5A0 (HEX) in minutes. If the heartbeat interval is configured above its scope, the system will cut it down to the allowed maximum (0x5A0). For information on how to check the heartbeat interval in NetAct, see Integrating RNC to NetAct in Nokia Online Services (NOLS).

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

77 (240)

RNC Integration

Expected outcome

A successful heartbeat configuration results in that the RNC sends the alarm 0599 HEARTBEAT NOTICE FOR ALARM FLOW SUPERVISION to the Nokia NetAct.

78 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring RNC level parameters

6
6.1

Configuring RNC level parameters
Defining external time source for network element
Purpose

The IP addresses used in the Commissioning stage for setting the time and date are predefined and temporary; therefore, you need to configure the time source IP address again, using the DCM command, after the internal DCN network has been configured during the integration stage. The external time source is located in the Nokia NetAct time server. IPA2800-based network elements check the time and date every 15 minutes, preferably against the NEMU time server, using NTP messages.

Note
IP connections must be created before you can define the external time source in Nokia NetAct time server.

Steps
1. Check the current date and time in the network element (DCD) ZDCD; 2. Check the NTP server IP address (DCI) ZDCI; 3. Set the IP address to the NTP time server (DCM) ZDCM:<ip version>,<ip address block 1>;

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

79 (240)

RNC Integration

Expected outcome

When you have defined the external time source, in 15 minutes all the clocks in the network element will have the same time as the external time source has. The internal clock located in the network element gives a time stamp for all the functions that the computer unit does.

6.2

Creating local signalling configuration for RNC
Before you start

Check that the network element has all the necessary equipment and software.

Note
Note the following in relation to the NPC command when using Nodal Function to connect two adjacent RNCs via MGW Rel.4: Since the signalling links are used for SCCP signalling, the value of both the service existing for STP messages and the service existing for user part of own signalling point parameter must be Y. ZNPC:<signalling network>,03,SCCP:Y:Y,208,10F;

Note
In Japan, you must read the subfields of the signalling point code for commands NRP, NSC and NRC in reverse order. This differs from the standard procedure used elsewhere in the world. For example, in Japan, the signalling point code 23–8–115, would be read as 115–8– 23.

Steps
1. Create SS7 services

80 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring RNC level parameters

Before you start

The signalling messages coming into the network element can be transmitted to the network element's own user parts, or they can be switched forwards, or both. Depending on the services configured to the network element, some of the signalling messages are unnecessary. Data on service information determines how the signalling messages coming into the network element are received and switched.

Steps
a. Check that all necessary services exist (NPI) Check that all needed services exist in the network element by using the NPI command. The services SNM and SNT usually exist automatically in the network element. The needed services depend on the type and use of the network element. In Radio Network Controller (RNC) or Multimedia Gateway Rel.4 (MGW Rel.4) type of network elements at least the following services are needed: . SNM — signalling network management messages . SNT — signalling network testing and maintenance messages . SCCP — signalling connection control part . AAL2 — AAL type 2 signalling protocol b. Create the necessary services (NPC) Use the parameters service existing for STP messages and service existing for user part of own signalling point to choose whether the service is active for the STP messages and/or to the user parts of the own signalling point. Check the process family identifiers from the Site Specific Documents as there can be some exceptions to the values given in the following example commands. ZNPC:<signalling network>,00,SNM:Y:Y,07F,06D; ZNPC:<signalling network>,01,SNT:Y:Y,07F,; ZNPC:<signalling network>,03,SCCP:Y:Y,208,10F; ZNPC:<signalling network>,0C,AAL2:Y:Y,452;

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

81 (240)

RNC Integration

2.

Create own MTP signalling point (NRP) The own signalling point has to be defined before you can create the other objects of the signalling network. Use the command NRP to create the own MTP signalling point. A network element can be connected to several signalling networks. The NRI command displays all existing signalling points. There are special network-specific parameters related to the signalling networks, and you can output them using the NMO command. These parameters define, for example, the congestion method used in the signalling network. For more information about the network-specific parameters, see SS7 signalling network parameters.

Note
The same NRP command is used to create a new signalling network.

ZNRP:<signalling network>,<signalling point code>, <signalling point name>,STP:<ss7 standard>:<number of spc subfields>:<spc subfield lengths>; 3. Create own SCCP signalling point (NFD) Before you start creating the signalling point, check what the Signalling Point Code (SPC) of the system's own signalling point is by using the NRI command. ZNFD:<signalling network>, <signalling point code>, <signalling point parameter set number>:<subsystem number>,<subsystem name>,<subsystem parameter set number>,[<subsystem status test>]: ... ;

Note
The value YES for the subsystem status test parameter is valid only when the parameter WHITE_BOOK_MGMT_USED (12) of the used SCCP signalling point parameter set has value YES (check this with the OCI command).

82 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring RNC level parameters

When an SCCP signalling point and SCCP subsystems are created, a parameter set is attached to them. In most cases the predefined parameter sets are the most suitable, but if the predefined parameter sets do not cover all occurring situations, you can create more parameter sets, modify the relevant parameters and then attach the new parameter set to the SCCP signalling point and SCCP subsystem. For more information, see SCCP signalling point parameters and SCCP subsystem parameters. 4. Add local subsystems to the signalling point (NFB), if necessary ZNFB:[<signalling network>],<signalling point codes>:<subsystem number>,<subsystem name>, <subsystem parameter set number>,[<subsystem status test>]; 5. Activate local SCCP subsystems (NHC), if necessary ZNHC:<signalling network>, <signalling point codes>: <subsystem>:ACT; To display the subsystem states, use the NHI or NFJ command. For more information, see States of SCCP subsystems.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

83 (240)

RNC Integration

84 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring transmission and transport interfaces

7
7.1

Configuring transmission and transport interfaces
Configuring PDH for ATM transport
Purpose

This procedure describes how to configure the PDH/ATM interface for the NIP1 interface unit. The mode of the PDH interface must be the same for all the exchange terminals in the plug-in unit. That is why the NIP1 unit must be given as a parameter when the PDH mode is configured. Usually the existing default values for the PDH supervision are adequate and you do not have to change them. If needed, you can configure and modify the exchange terminal supervision parameters. When you have configured new PDH exchange terminals (PET), you may have to modify their functional modes. Choose either E1, ETSI-specific functional modes, or T1, ANSI-specific functional modes. In a fractional E1/T1/JT1, you can select the timeslots that are used to carry user data.

Note
IMA functionality is not supported over fractional E1/T1/JT1 lines.

The network elements provide a synchronisation interface for external timing reference signals. For information on synchronisation, see Configuring synchronisation inputs in Synchronisation and Timing.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

85 (240)

RNC Integration

Before you start

Make sure that you have created a functional unit description for the PETs. For instructions, refer to Creating and attaching functional unit description in Hardware Configuration Management.

Steps
1. Interrogate the PET's current configuration (YAI) ZYAI:PET; 2. Set the interface operation mode of NIP1 (YAE) Set the operation mode if you want to change it. The impedance parameter can be given only if the operation mode given is E1. ZYAE:NIP1,<network interface unit index>,<interface operation mode>:[<impedance>]; If you change the impedance or the operation mode, you must restart the unit so that the changes are taken into use. See the instructions in Restarting functional unit in Recovery and Unit Working State Administration. 3. Modify E1 functional modes if needed (YEC) You can first output the ETSI-specific frame modes with the command: ZYEI; If the current frame mode does not match with the frame mode of the interface unit that is connected to the remote end of this line, you can modify it with the command: ZYEC:<unit type>,<unit index>:NORM,(DBLF|CRC4);

Note
Double framing does not support synchronisation status message (SSM). For more information, see Configuring synchronisation inputs in Synchronisation and Timing.

4.

Modify T1 functional modes if needed (YEG)

86 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring transmission and transport interfaces

You can output the ANSI-specific T1 functional modes with the command: ZYEH; If the current frame mode does not match with the frame mode of the interface unit that is connected to the remote end of this line, you can modify it with the command: ZYEG:<unit type>,<unit index>:(ESF|SF),(B8ZS|AMI), (0|7.5|15|22.5);

Note
T1 does not support SSM. For more information, see Configuring synchronisation inputs in Synchronisation and Timing.

5.

Configure PET (YAM) ZYAM:PET,<PET index>...:[ON|OFF]:[DIA=(ON|OFF)| LINE=ON|OFF)]...:[<SA bit number SSM>];

6.

Modify PET timeslot usage (YAW) You can modify PET timeslot usage with the command: ZYAW:<PET index>...:<timeslot number>...,[ON|OFF def];

7.

Create an IMA group, if necessary If you want to use more than one transmission line, you must create an IMA group for the physical links. Configure PET (YAM) and Modify PET timeslot usage (YAW) are repeated for each link which is selected to the IMA group. See the instructions in Creating IMA group for more information.

8.

Create physical layer Trail Termination Point (phyTTP) See the instructions in Creating phyTTP for more information.

Example

Configuring PDH for ATM transport

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

87 (240)

RNC Integration

1.

Set the interface operation mode of NIP1 with index number 9 to T1. ZYAE:NIP1,9,T1;

2.

Restart the unit. ZUSU:NIP1,9;

3.

Modify the frame alignment mode of the T1 PET with index 9. ZYEG:PET,9:ESF,B8ZS,0;

4.

Disable scrambling for PETs with indexes between 9 and 15. ZYAM:PET,9&&15:OFF::;

7.2

Creating IMA group
Purpose

This procedure describes how you can create an IMA group and add exchange terminals to it. You can later connect an external ATM interface to the phyTTP that has been created for the IMA group. You must create an IMA group if you want to use more than one PDHbased transmission lines for additional capacity or for securing traffic even in line failure situations. For example, if one E1 line is used in transmission, you can create an IMA group of two E1 lines and give value 1 to the minimum number of links parameter. Even if one line fails, the ATM interface stays up. The maximum allowed number for each IMA group is 8 exchange terminals. The IMA group must be created at both ends of the physical links.

Note
IMA functionality is not supported over fractional E1/T1/JT1 lines.

Before you start

Make sure that you have configured the PDH exchange terminals (PETs) before you create an IMA group. For the instructions, see Configuring PDH for ATM transport.

88 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring transmission and transport interfaces

The PETs to be combined to an IMA group must belong to the same NIP1 functional unit. Check which functional unit a PET belongs to with the USI command. Each PET is identified by its exchange terminal index, which is a systemwide unique numerical value. In addition, the system assigns a link ID to each PET. This link ID is unique in the IMA group. One of the physical links functions as the Timing Reference Link (TRL) of the IMA group, which is identified by its link ID. The system assigns the TRL to the IMA group.

Steps
1. Create IMA group (YBC) ZYBC:[<IMA group id>] | <system select> def: [<exchange terminal type> | PET def],<exchange terminal index>...:<minimum number of links>;

Note
Define the IMA group size, which is the total number of the links, so that the IMA group capacity will be equal to or greater than the planned capacity of the ATM interface.

Further information

You can add more PETs later on to the group with the YBA command. The maximum number of PETs in an IMA group is 8. 2. Create phyTTP for the IMA group See the instructions in Creating phyTTP.
Further information

You can interrogate IMA groups with the YBI command, modify them with the YBM command, and delete an IMA group with the YBD command. It is possible to remove exchange terminals from an IMA group with the YBR command. Adding or removing links automatically affects the bandwidth of the access profile of the ATM interface.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

89 (240)

RNC Integration

Example 1.

Creating IMA group

Create an IMA group using the IMA group ID selected by the system. The type of exchange terminal is PET by default. The IMA group combines PDH exchange terminals 0, 5 and 14. The minimum required number of links in the group is 2. ZYBC::,0&5&14:2;

2.

Add the exchange terminal 12 to the IMA group 3. ZYBA:3:12;

7.3

Configuring SDH for ATM transport
Purpose

This procedure describes how to configure the SDH/ATM interface and modify the SDH exchange terminal (SET) configuration. You can define how the transmission capacity is divided, and change the threshold levels for performance monitoring to meet the expected quality of the transmission network.
Before you start

You must create the functional unit description for the SETs. For instructions, see Creating and attaching functional unit description in Hardware Configuration Management.

Steps
1. Interrogate the SET (YAI) With the following command you can find out the current exchange terminal configuration. ZYAI:<SET>,<SET index>; 2. If you want to modify the default settings, configure the SET (YAN)

90 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring transmission and transport interfaces

Note
When VC mapping is changed, the affected higher and lower order paths get their default values.

Note that for the NIS1 and NIS1P units only one loopback status (diagnostic or line) can be on at a time. Currently the SES BIP, SD BER, and SF BER parameters are not used for the higher or lower order paths. The SES BIP threshold for the higher order paths is the same as the one used for the multiplex section of the SET. The following parameter values are irrelevant to the ATM traffic: . mapping mode parameter values VC3VC11, VC3VC12, VC4VC11, and VC4VC12 and . payload mapping mode parameter values ASYNCH, BITSYNCH, and BYTESYNCH. ZYAN:<SDH exchange terminal index>...,[<higher order path number>|<higher order path number>,<lower order path number>]:[<SES BIP threshold>]:[<SD BER threshold>]:[<SF BER threshold>]:[DIA=(ON|OFF)| LINE=(ON|OFF)|LASER=(ON|OFF)]...:[VC3|VC4|VC3VC11| VC3VC12|VC4VC11|VC4VC12]:[SDH|ATMML|SONET]: [ASYNCH|BITSYNCH|BYTESYNCH]; 3. Set the SDH trace (YAS) You can set the SDH trace already during integration or later on, if necessary. The SDH trace trail must be configured identically to both the trails related to a specific phyTTP (logical path) in a protection group. When you configure a trace for a trail that is part of a protection group, the system automatically applies the changes also to the other trail of the pair and sends a notification on this.

Note
Trace types EXPPATH and EXPREG are not currently supported.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

91 (240)

RNC Integration

ZYAS:<SDH exchange terminal index>,[<higher order path number>|<higher order path number>,<lower order path number>]:(OUTPATH|EXPPATH|OUTREG|EXPREG), (RESET|SET1|SET16|SET64),<trace value>; For more information on the trails, see Creating SDH protection group. 4. Create SDH protection group, if necessary If you want to secure the traffic even when a line fails, you need to create an SDH protection group. Refer to the instructions in Creating SDH protection group. 5. Create phyTTP Refer to the instructions in Creating phyTTP.
Further information

You can interrogate the incoming SDH traces with the YAT command. Example 1. Configuring SDH for ATM transport

Modify the SES BIP threshold of the SET 1 to 2300 frames per second. Set the VC mapping to VC-3. ZYAN:1:2300::::VC3;

2.

Modify the outgoing path trace of the VC path 2 of SET 1. Use the 16-byte format. ZYAS:1,2:OUTPATH,SET16,"OUT PATH TRACE";

7.4

Creating SDH protection group
Purpose

You can create a protection group which is formed by two SDH exchange terminals (SET). Multiplex Section (MS) trail linear protection is used to protect a single multiplex section trail by replacing a working MS trail if the working trail fails or if the performance falls below the required level. There are two supported protection protocols:

92 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring transmission and transport interfaces

.

linear, bi-directional Multiplex Section Protection (MSP) 1+1 compatible with 1:n protocol, and linear, bi-directional Automatic Protection Switching (APS) 1+1. Both protocols can be used either in revertive or in non-revertive mode.

.

The SDH trace trail must be configured identically to both trails related to the same logical path in a protection group. Otherwise, the system prevents the protection group creation.

Steps
1. Create SDH protection group (YWC) ZYWC:[<protection group id>|<system select> def], [<protection switching mode>|NONREV def],[<protocol variant>|MSP def]:<Working section SDH exchange terminal index>,<Protection section SDH exchange terminal index>:[<wait to restore time>|300 seconds def]; The system will ensure that both trails of a pair are configured identically in a protection group. 2. Create Physical Layer Trail Terminal Point (phyTTP), if necessary If the protected SDH interfaces are for ATM traffic transport, you need to create phyTTP. See the instructions for creating the physical layer Trail Termination Point in Creating phyTTP.
Expected outcome

The system generates the 0101 SDH PROTECTION SWITCHING EXECUTED notice if the protection switch operation succeeds.
Unexpected outcome

The system generates the 3183 SDH PROTECTION SWITCHING FAILED alarm if the protection switch operation fails. If the far end has not been configured to support the correct SONET APS configuration, the system generates the 3307 MISMATCH IN SONET APS CONFIGURATION alarm.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

93 (240)

RNC Integration

If the far end of the protected multiplex section is not able to use the protection section, the system generates the 3334 FAR END PROTECTION SECTION FAILURE alarm.
Further information

You can interrogate the protection group configuration and protection switching status information with the YWI command, modify the configuration with the YWM command and delete the configuration with the YWD command. Note that a protection group cannot be deleted if a phyTTP has been created for it. Example Configuring SDH protection group with default protection protocol parameter values

1.

Create a protection group of SET 7 (working section) of NIS1P-1 and SET 4 (protection section) of NIS1P-0 with protection group ID 3. The default protection switching mode, bidirectional non-revertive, and protocol variant MSP 1+1 are used. ZYWC:3,,:7,4:;

Example

Configuring SDH protection group with SONET APS variant of the protection protocol and with revertive mode

1.

Create a protection group of SET 8 (working section) and SET 9 (protection section) of IWS1T-0 with protection group ID 4. Revertive mode and APS 1+1 variant are used. Default of wait to restore time is used. ZYWC:4,REV,APS:8,9;

7.5

Creating phyTTP
Purpose

The Physical layer Trail Termination Point (phyTTP) is configured between the physical layer and the ATM layer. The phyTTP ID is used when creating the ATM interface.

94 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring transmission and transport interfaces

You can create a phyTTP for a single PDH exchange terminal (PET), an IMA group, a single SDH VC path, or a VC path of an SDH protection group.

Note
You cannot create a phyTTP for a single SDH VC path of a 2N redundant network interface unit. The phyTTP for a 2N redundant unit must be created for the VC path of the SDH protection group that has been created for the unit.

Before you start

You must configure the PDH or SDH interfaces (PET, SET, an IMA group, a single SDH VC path or a VC path of an SDH protection group) before you can create the phyTTP for them. For configuration instructions, see Configuring PDH for ATM transport and Configuring SDH for ATM transport. If you need to interrogate the phyTTP configuration or the operational state of the phyTTP, use the YDI command.

Steps
1. Create a physical layer Trail Termination Point (YDC)

Note
The MML command for creating the phyTTP includes a parameter, payload type, for separating ATM traffic from PPP traffic. However, only ATM traffic is supported in this release.

ZYDC:<phyTTP>:(PET=<PDH exchange terminal>|IMA=<IMA group>|SET= <SDH exchange terminal>|PROTGROUP= <protection group>):[<VC path number>| <default>def]:[ATM def|PPP],[ON def|OFF];

Table 7. Parameter
If you are creating phyTTP to a SET:

Parameters and values for creating phyTTP Value

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

95 (240)

RNC Integration

Table 7. Parameter
SET VC path number
If you are creating phyTTP to a PET:

Parameters and values for creating phyTTP (cont.) Value
index of the SET VC path number

PET
If you are creating phyTTP to an IMA group:

index of the PET

IMA
If you are creating phyTTP to an SDH protection group:

ID of the IMA group

PROTGROUP VC path number

ID of the protection group VC path number

Further information

You can delete a phyTTP with the YDD command. After the deletion, its physical resources are free to be used again; for example, you can add PET to an existing IMA group or you can protect SET by creating a protection group. On the other hand, IMA/protection group can be deleted if there is no phyTTP related to it. The phyTTP cannot be deleted if it is used by the upper layer, that is, if there is an ATM interface created on it. You can use the YDI command to check whether the phyTTP is in use or not. Example Creating a phyTTP for a SET

Create a phyTTP with ID 1 of the SET with index 0 and VC path number 1. ZYDC:1:SET=0:1:; Example Creating a phyTTP for a PET

Create a phyTTP with ID 1 of the PET with index 10. ZYDC:1:PET=10; Example Creating a phyTTP for an IMA group

Create a phyTTP with ID 2 of the IMA with index 20. ZYDC:2:IMA=20;

96 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring transmission and transport interfaces

Example

Creating a phyTTP for an SDH protection group

Create a phyTTP with ID 4 for path 1 of protection group 4. ZYDC:4:PROTGROUP=4:1:;

7.6

Creating ATM resources in RNC
Purpose

This procedure provides instructions for creating ATM resources on the following interfaces:
.

Iu-CS between RNC and MGW Iu-PS between RNC and SGSN Iu-BC between RNC and CBC Iur between two RNCs Iub between RNC and BTS

.

.

.

.

Note
Use the MMLs or ATM plan interface from the NetAct for the ATM layer configuration in the RNC. At the Iub interface use the RNC RNW Object Browser or the RNW Plan interface from the NetAct for BTS related signalling link and the AAL2 user plane VCC configuration. In the Iub interface configuration of the ATM interface and its access profile needs to be created via the MMLs or ATM plan interface before creating the Iub connection configuration (COCO managed object). For further details see ATM plan interface in document RNC Operation and Maintenance.

RNC uses MTP3 as the AAL type 2 signalling transport on all interfaces except on the Iub interface where SAAL UNI signalling is used.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

97 (240)

RNC Integration

Caution
When defining traffic parameter values, take into account the capacity limitations of an ATM interface. If the resources are misconfigured, the system will reject the creation of VP/VC connections later. See also Taking termination point into use fails.

Before you start

Configure the hardware (including exchange terminals) and the physical resources. See Physical interfaces in ATM network.

Steps
1. Create an ATM interface connected to a physical layer Trail Termination Point (LAC) ZLAC:<interface id>:<interface type>,<phyTTP>; Note that the interface will be unlocked.

Table 8.

Parameters and values for creating an ATM interface connected to a physical layer Trail Termination Point Value
Select a numerical value. If you do not set the value manually, the system will choose a free numerical value.

Parameter
interface id

interface type

UNI for Iub interface NNI for all other interfaces

phyTTP

the identifier of the phyTTP

2.

Create the access profile of the ATM interface (LAF) ZLAF:<interface id>:<max VPI bits>:<max VCI bits>: <UPC/NPC mode>;

98 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring transmission and transport interfaces

Table 9.

Parameters and values for creating the access profile of the ATM interface Value
As defined in step 1. Select a suitable value, for example 5. Setting the value to 5 allow VPI values from 0 to 31 to be used. Select a suitable value equal to or greater than 6, for example, 7. Setting the value to 7 allow VCI values from 32 to 127 to be used. Select whether UPC/NPC (policing) is to be enabled or disabled for this interface.

Parameter
interface ID max VPI bits

max VCI bits

UPC/NPC mode

For details on creating the access profile, refer to ATM interface access profile.
Expected outcome

The system will set the bandwidth to fully use the capacity of the physical resource. The printout tells the Maximum ingress bandwidth value and Maximum egress bandwidth value used. 3.

If you are creating ATM resources for the Iub interface Then
Create ATM termination points using RNC RNW Object Browser You have two possibilities: When creating connection configuration for the Iub interface, see Creating Radio Network Connection Configuration. When creating ATM termination points for IPoA connection, see Creating ATM termination point for IP over ATM connection.

Note
The rest of the steps in this procedure are not necessary for Iub interface.

4.

Create VPLtps for UBR traffic, if necessary (LCC)

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

99 (240)

RNC Integration

You need to create VPLtps for UBR traffic (IP over ATM connection) for the following: . In Iu-CS interface, one VPLtp for O&M traffic. Depending on the network planning, this may not be necessary. . In Iu-PS interface, the necessary number for data traffic. . In Iu-BC interface, the necessary number for IP traffic and data traffic. ZLCC:<interface id>, <tp type>, <VPI>,,<VPL service level>:<segment endpoint info>,<VP level traffic shaping>::<egress service category>,,,<egress QoS class>:;

Table 10. Parameter
interface id tp type VPI

Parameters and values for creating a VPLtp for UBR traffic Value
Same as in steps 1 and 2. VP Select VPI value within the range defined in step 2. VC Depends on network planning For Iu-BC, NO For other interfaces, depends on network planning

VPL service level segment endpoint info VP level traffic shaping

egress service category egress QoS class

U (UBR) U (Unspecified Class)

5.

Create VPLtps for CBR traffic (LCC) You need to create VPLtps for CBR traffic for the following: . In Iu-CS interface, the necessary number for SS7 (MTP3SL) signalling and routing AAL type 2 user data (AAL2UD). . In Iu-PS interface, the necessary number for SS7 (MTP3SL) signalling traffic.

100 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring transmission and transport interfaces

.

In Iu-BC interface, the necessary number for IP traffic (IP over ATM connections).

Note
If an ATM Virtual Path Leased Line service is used to implement the IuBC interface, a VPLtp should be created as CBR type with defined Peak Cell Rate. VP level traffic shaping should be enabled to limit the peak cell rate of the VP and thus avoid cell loss due to policing in the ATM network.
.

In Iur interface, the necessary number for SS7 (MTP3SL) signalling and routing AAL type 2 user data (AAL2UD).

ZLCC:<interface id>, <tp type>, <VPI>,,<VPL service level>:<segment end point info>,<VP level traffic shaping>::<egress service category>,,,<egress QoS class>:::<egress PCR>,<egress PCR unit>;

Table 11. Parameter
tp type

Parameters and values for creating a VPLtps for CBR traffic Value
VP VC Depends on network planning For Iu-BC, FULL For other interfaces, depends on network planning

VPL service level segment endpoint info VP level traffic shaping

egress service category egress QoS class egress PCR egress PCR unit

C (CBR) C1 (QoS Class number 1) Depends on network planning Depends on network planning

For details on creating termination points of CBR type, refer to Basic guideline for calculating CDVT. 6. Create VCLtps for UBR traffic, if necessary (LCC) You need to create VCLtps for UBR traffic for the following:

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

101 (240)

RNC Integration

.

.

.

In Iu-CS interface, one VCLtp for SS7 (MTP3SL) signalling traffic. Depending on the network planning, this may not be necessary. In Iu-PS interface, the necessary number for data traffic. You need at least one IP over ATM connection per GTPU unit. In Iu-BC interface, the necessary number for IP traffic and data traffic. You need at least one IP over ATM connection per ICSU unit.

ZLCC:<interface id>,<tp type>,<VPI>,<VCI>::<ingress service category>,<ingress EPD>,<ingress PPD>, <ingress QoS class>:<egress service category>, <egress EPD>,<egress PPD>,<egress QoS class>;

Table 12. Parameter
tp type VPI

Parameters and values for creating VCLtp for UBR connection Value
VC The same as in step 4. U (UBR) E (enabled) E (enabled) U U (UBR) E (enabled) E (enabled) U

ingress service category ingress EPD ingress PPD ingress QoS class egress service category egress EPD egress PPD egress QoS class

7.

Create VCLtps for CBR traffic (LCC) You need to create VCLtps under the VPLtp(s) for CBR traffic for the following: . In Iu-CS interface, the necessary number of VCLtp for SS7 (MTP3SL) signalling and routing AAL type 2 user data (AAL2UD) traffic. . In Iu-PS interface, the necessary number for SS7 (MTP3SL) signalling and data traffic (IPOAUD). . In Iur interface, the necessary number of VCLtp for SS7 (MTP3SL) signalling and routing AAL type 2 user data (AAL2UD) traffic.

102 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring transmission and transport interfaces

ZLCC:<interface id>,<tp type>,<VPI>,<VCI>::<ingress service category>,<ingress EPD>,<ingress PPD>, <ingress QoS class>:<egress service category>, <egress EPD>,<egress PPD>,<egress QoS class>:: <ingress PCR>,<ingress PCR unit>:<egress PCR>, <egress PCR unit>;

Table 13. Parameter
tp type

Parameters and values for creating VCLtps for CBR traffic Value
VC C (CBR) E (enabled) E (enabled) C1 C (CBR) E (enabled) E (enabled) C1 Depends on network planning Depends on network planning Depends on network planning Depends on network planning

ingress service category ingress EPD ingress PPD ingress QoS class egress service category egress EPD egress PPD egress QoS class ingress PCR ingress PCR unit egress PCR egress PCR unit

For details on creating termination points of CBR type, refer to Basic guideline for calculating CDVT.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

103 (240)

RNC Integration

104 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring synchronisation inputs

8

Configuring synchronisation inputs
Purpose

You can configure and control synchronisation with MML commands. Usually synchronisation-related MML commands are used for setting the synchronisation system-related parameters and also for getting information from the synchronisation system. By using the correct MML command, you can force the system clock to use a synchronised operating mode or a free-run operating mode. Under certain operating conditions, for example calibration, this is a necessary action. You must always create synchronisation inputs when taking a network element into use. You can change the inputs later, if needed. The following order of steps is not obligatory. You can check the available synchronisation references with the DYI command. Use the DYS command to set a synchronisation reference as the forced reference of the system clock. Notice that the forced reference can even be lost and the operation mode of the system clock is changed to Holdover. The changes in the quality of the other references do not affect the forced reference setting. Whenever a synchronisation reference that is used in the synchronisation of the system clocks, is lost, the reference is considered to be available after the WTR (Wait To Restore) time has expired. The default WTR is five minutes. Enable the distribution of the outgoing signal if you want to distribute the signal outside the network element. Set the operation mode when testing the network element. Usually this is done automatically by the system.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

105 (240)

RNC Integration

Note
If you have set the operation mode to FREE, when testing the system for instance, you have to set the mode back to SYNC. This is not done by the system.

Steps
1. Set the parameters for all synchronisation references (DYM) The highest priority value (PRI) is 1. The highest synchronisation status message value (SSM) is 1, the lowest is 14. In addition, value 0 is used when the quality of the reference is unknown, and value 15 is used when the reference must not be used in synchronisation. The SSM value is entered manually to external references. All line references, including the PDH line interfaces, get their SSM values on line from the frame structure of the incoming signal. You have to set parameters for at least one synchronisation reference.

Note
PRI value must be removed from the references (it should be set to PRI=X) that have not been actually connected to a so-called connected NIU through which the synchronisation references are connected to the system.

Note
The Framing mode for the incoming PDH references must support the transfer of the SSM values. For instructions about configuring the Framing mode, see Configuring PDH for ATM transport. If the Framing mode for the incoming PDH references does not support the transfer of SSM values, the references can be set with the PRI value.

ZDYM:<synchronisation reference>,<reference index>, <mode of external reference>:PRI=<priority value>, SSM=<ssm value>; 2. Check the automatic synchronisation setting (DYI)

106 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring synchronisation inputs

When the parameters for at least one synchronisation reference with OK status are set for the first time during system start-up, the system will synchronise automatically. In this case you do not have to manually set the operation mode. ZDYI:<identification of information>, <identification of reference>; 3. Set the operation mode (DYT) If the system clock has not locked into the reference even though the reference is available, it can be forced to lock into the reference by using the DYT command. This command is not normally used in the commissioning phase and it must not be used instead of entering parameters for a synchronisation reference. ZDYT:MODE=<operation mode>; 4. Check the values of the WTR timers for the references (DYI) ZDYI; 5. Modify the values of WTR timers (DYL) The default value for the WTR timer is 5 minutes. If you want to change it, use the parameter SET. If you want to switch it off, you need to give the RESET command. If you want that the WTR timer is not set at all when the used synchronisation reference is lost, use SET parameter to change the value of the WTR timer to 0. ZDYL: <synchronisation reference>, <reference index>: <action>, <value>;

Note
RESET option means that the running WTR timer for a synchronisation reference will be initialised immediately to 0 but if you want to disable the WTR timer, you must SET the value of WTR timer to 0.

6.

Check which references have been enabled ZDYP;

7.

Enable the distribution of outgoing synchronisation (DYE)

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

107 (240)

RNC Integration

Enable the distribution of outgoing synchronisation if you want to distribute the signal outside the network element. Give the ENA value for the ACT parameter.

Note
The Framing mode for the outgoing PDH references must be such that the SSM values can be written into it. For instructions on configuring the Framing mode, see Configuring PDH for ATM transport.

ZDYE:<synchronisation reference>,<reference index>...:ACT=<action>; 8. Check the SSM generation values ZDYI:SSMGEN; 9. Change the SSM generation values if necessary ZDYK:<synchronisation reference>,<reference index>: <SSM generation>; 10. Use the synchronisation reference as the forced reference of system clock (DYS) Use the DYS command to set a synchronisation reference as the forced reference of the system clock. Notice that the forced reference can even be lost and the operation mode of the system clock is changed to Holdover. The changes in the quality of the other references do not affect the forced reference setting. Give the value Y for the ACT parameter. You can release synchronisation reference as the forced reference of system clock by giving the value N for the ACT parameter. ZDYS:<synchronisation reference>,<reference index>: ACT=<action>; 11. Control general settings for the synchronisation system (DYR)

108 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring synchronisation inputs

Note
With the command DYR you can reset the switching type of references, set special configuration, cut the outgoing external reference, or include or remove SSM value as selection criteria. The SSM value of the reference can be included or removed from the selection criteria when the best reference is selected to be used in the synchronisation of the system clocks. By default, the SSM and priority values are used when the references are ordered. You can control whether the SSM value is used or not during the reference selection.

Note
You must enter the parameters for the connected references to make them available for the synchronisation system. The PRI value other than PRI=X tells the system that the synchronisation reference is ready to be used in the synchronisation of the system clocks. Before using it, make sure that the status of the reference is OK.

ZDYR:<command identification>,<command action>;

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

109 (240)

RNC Integration

110 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iub interface (RNC-BTS)

9
9.1

Creating Iub interface (RNC-BTS)
Configuring transmission and transport resources
For information on configuring transmission and transport resources, refer to Configuring transmission and transport interfaces.

9.2

Creating radio network connection configuration
Purpose

A new logical connection configuration object (COCO) is created in order to reserve local transmission resources for WCDMA BTS (WBTS). The COCO object displays the transmission resources in the Iub interface but not the actual network topology.

Note
It is possible to create a COCO without relating it to a WBTS. In such a case, only the ATM layer is configured.

Before you start

The ATM interface should be created along with an access profile. For information on creating the ATM resources, see Creating ATM resources in RNC.

Steps
1. Start creating connection configuration. a. Select Object → New → Connection Configuration → Iub. b. Set an identifier for the COCO (Connection Configuration ID).

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

111 (240)

RNC Integration

c. d.
Or

Set the ATM interface identifier (Interface ID). Set the wanted virtual path identifier (VPI).

Alternatively, connection configuration can be created using an existing connection configuration as reference. a. Select the connection configuration whose structure and parameters should be used in the new connection configuration. b. Select Object → Use as reference c. Set an identifier for the new COCO (Connection configuration id) 2. Click OK to continue.
Expected outcome

The RNW Connection Configuration dialogue appears. 3. Fill in parameters for each link category. For more information on connection configuration, see Operation and Maintenance in RN2.2. For more information on parameters, see WCDMA RAN Parameter Dictionary. 4. Click OK in the parameter dialogue to confirm the operation.
Expected outcome

The data is sent to the RNC RNW database. The data is stored in the RNC RNW database and the ATM layer is created into the system. Control and user plane-related resources are created into the system if the COCO object was related to the WBTS. 5. Check the outcome of the operation and click OK.
Expected outcome

The COCO object and the corresponding ATM layer configuration is found in the system. If the COCO creation was successful and the WBTS that the user wanted to relate to the COCO was found, the system relates the COCO and the WBTS objects.

112 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iub interface (RNC-BTS)

The WBTS object does not have to be created before the COCO object is created. Also when the WBTS object is created afterwards, the system relates the objects to each other in the same way that it does if the WBTS already exists when the COCO object is created. Once the COCO and the WBTS have been related in the RNC RNW database, the Control/User plane configuration is done.
Unexpected outcome

Any errors are displayed in the Operation Information dialogue. If the creation fails, continue modifying the COCO or delete the failed COCO and start again with step 1.
Further information

Note
If the ATM layer is created with MML commands, make sure that the administrative state of the VP/VC Link termination points is unlocked. The usage information of the related ATM termination points should be free. If you use the automatic ATM configuration option, the termination points are created unlocked by default. For further information, see Creating ATM resources in RNC and Digit analysis and routing in RNC.

9.3

Creating ATM termination point for IP over ATM connection
Purpose

A new ATM termination point is created in order to configure ATM layer for IP over ATM (IPoA) connection. Please note that the RNC RNW Object Browser provides online help to assist you in carrying out the tasks. You can access the online help via the Help menu in the main window or by clicking the Help button in the dialogue windows. These instructions refer to the configuration with the RNC RNW Object Browser GUI. In addition to the GUI-based ATM termination point configuration for the IP over ATM connection, the MML interface and the ATM plan interface towards the NetAct can also be used.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

113 (240)

RNC Integration

For more information on the IP plan interface, see ATM and IP plan interfaces.
Before you start

Note
The IP over ATM configuration has to be completed with the commands defined in the example Configuring IP over ATM interface in Creating and modifying IP over ATM interfaces. If the connection configuration object (COCO) and IPoA have the same VPLtp, the COCO has to be created first. This is to ensure that the underlying VPLtp is created for CBR traffic class

Steps
1. Select Object → New → Connection Configuration → IP over ATM TP. Set the ATM interface identifier, VPI and VCI values. Set the wanted PCR value for defining the desired bandwidth for IPoA connection. Click OK to confirm operation.
Expected outcome

2. 3.

4.

The progression of the operation is displayed.
Expected outcome

An ATM layer configured to handle an IP over ATM connection is created in the system. The IPoA link is not, however, working as a result of this.
Unexpected outcome

Any errors are displayed in the Operation Information dialogue. If the creation fails, try again by starting from step 1.

114 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iub interface (RNC-BTS)

9.4

Configuring IP for BTS O&M (RNC-BTS/AXC)
Purpose

The purpose of this procedure is to configure IP for BTS O&M (RNC-BTS/ AXC and RNC-FlexiBTS). The alternative ways to configure IP for BTS O&M are detailed below:
.

tree topology ATM layer for O&M network to BTS, or star topology ATM layer for O&M network to BTS.

.

By using star topology, O&M connections can use the same Virtual Path (VP) as control plane traffic. The VPI connection must then be configured as CBR class. This also means that if the O&M VCI is configured to UBR class, it can use the same maximum capacity that is the bit rate for the shaped VPC.

Note
Currently, FlexiBTS does not support ATM cross-connecting. Therefore, a FlexiBTS can be configured only in a star topology or as the last BTS in a tree topology.

For more information on the topologies, see the Nokia WCDMA RAN System Information Set. You can use either static routing or dynamic routing (OSPF) for BTS O&M. If you use OSPF, you do not need to configure static routes towards the BTSs. When you create the OSPF configuration, the routes are automatically created after the configuration. With OSPF, you must use unnumbered interfaces towards the BTS, because the AXC only supports unnumbered interfaces. If you have numbered point-to-point interfaces with static routing in use and you want to activate OSPF also to these interfaces, you must modify the interface type. For instructions on how to modify point-to-point interfaces, see Creating and modifying IP interfaces in IP Connection Configuration for RNC.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

115 (240)

RNC Integration

Note
Currently, FlexiBTS does not support dynamic (OSPF) routing and numbered IP interfaces. Therefore, only static routing must be used towards a FlexiBTS and the IP interface type must be unnumbered.

Before you start

Note
In addition to the MML based configuration the IP layer can be configured via the IP plan interface from the NetAct. The IP plan support does not contain the OSPF configuration. For further details on the IP plan interface see IP plan interface in document RNC Operation and Maintenance.

You need to create ATM resources for the Iub interface before starting this procedure. When using tree topology, the VPI/VCI termination point with default 0/32 must be created for the O&M connection in OMU. When using star topology, you need to create VPI/VCI termination point for O&M connection for dedicated BTS in OMU. Check if the VPI/VCI termination point is already created for the control plane. By default, the same VPI termination point is used as the control plane traffic for BTS. The VPI is configured as CBR class. You also should have ATM plans available for the tree or star model DCN for O&M. For more information, see Creating ATM resources in RNC in ATM Resource Management.

Steps
1. Start the MMI Window in the Element Manager For instructions, see Using EM MMI window in Element Manager Administration. 2. Create an IP over ATM interface towards BTS in OMU It is recommended to use unnumbered interfaces towards BTS because point-to-point links do not need IP subnets specified for the link. This also helps in planning and configuring the IP network when IP subnets are not used with point-to-point links.

116 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iub interface (RNC-BTS)

For instructions, see Configuring IP over ATM interfaces. 3.

If you are using static routing Then
Create static route for BTS O&M For O&M connections towards BTS, configure the route from OMU to the IP address of the gateway that is on the other side of the pointto-point ATM connections (AXC address of BTS site). ZQKC:<unit type>,<unit index>:[<destination IP address>],[<netmask length>]:<gateway IP address>, [<local IP address>]:[<route type>];

Note
The parameter local IP address is only valid for local IP address based default routes. For normal static routes, you do not need to give the local IP address. For more information about local IP address based default routes, refer to Creating and modifying static routes. 4.

If you are using OSPF Then
Configure OSPF area parameters and interfaces a. Define the OSPF parameters of an OSPF router. The area identification specifies the area ID for a new OSPF. The area ID is entered as a dotted-quad. The IP network number of a subnetted network may be used as the area ID. It is recommended that all OSPF areas except the backbone be configured as totally stubby areas. ZQKE:<unit type>,<unit index>:<area identification>:<stub area>,[<stub area route cost>],<totally stubby area>; b. Define the OSPF interface parameters of an OSPF router. The default value for router dead interval parameter in AXC is 120. Because the value must be the same in both AXC and RNC, change the value of the router dead interval parameter to 120 in RNC.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

117 (240)

RNC Integration

ZQKF:<unit type>,<unit index>:<interface specification>:<area identification>:[<hello interval>]:[<router dead interval>]:[<ospf cost>]:[<election priority>]:[<passive>]: [<authentication> | <authentication>, <password>];
Further information

Example

Configuring IP for BTS O&M using star topology ATM layer

This example presents IP for BTS O&M configuration in RNC when star topology ATM layer and dynamic routing (OSPF) is used.

O&M backbone

RNC Element Manager

ESA12/ESA24

NEMU

EL0 10.1.1.2/28 (logical)

OMU

RNC LAN
10.1.1.0/28 AA1 10.1.1.2/32 unnumbered lines

AA2 10.1.1.2/32

RNC

RAN BTS sites address range 10.1.3.0/29

RAN BTS sites address range 10.1.2.0/29

Figure 6.

Example of IP configuration for BTS O&M when star topology and OSPF are used

118 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iub interface (RNC-BTS)

1.

Create IP interfaces towards every BTS in OMU. Assign logical IP addresses to the unnumbered point-to-point network interfaces of the OMU unit, with MTU value 1500. ZQRN:OMU:EL0:10.1.1.2,L:28; ZQRN:OMU:AA1,U:10.1.1.2,L::10.1.2.1:1500:UP; ZQRN:OMU:AA2,U:10.1.1.2,L::10.1.3.1:1500:UP; ... ZQRN:OMU:AA31,U:10.1.1.2,L::10.1.32.1:1500:UP; ZQRN:OMU:AA32,U:10.1.1.2,L::10.1.33.1:1500:UP;

2.

Create an IP over ATM interface between the IP interface and the ATM termination point. Configure an IP over ATM interface with network interface names AA1...AA32 using the same VPI as control plane traffic, and with VCI 32. ZQMF:OMU,,L:AA1:1,1,32; ZQMF:OMU,,L:AA2:2,2,32; ... ZQMF:OMU,,L:AA31:1,31,32; ZQMF:OMU,,L:AA32:2,32,32;

3.

Configure OSPF area parameters of an OSPF router for the BTS branch. ZQKE:OMU,0:10.1.2.0:Y,,Y; ZQKE:OMU,1:10.1.2.0:Y,,Y;

4.

Configure the OSPF interface parameters of an OSPF router. ZQKF:OMU,0:AA1:10.1.2.0::120; ZQKF:OMU,1:AA1:10.1.2.0::120; ZQKF:OMU,0:AA2:10.1.2.0::120; ZQKF:OMU,1:AA2:10.1.2.0::120; ...

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

119 (240)

RNC Integration

ZQKF:OMU,0:AA31:10.1.2.0::120; ZQKF:OMU,1:AA31:10.1.2.0::120; ZQKF:OMU,0:AA32:10.1.2.0::120; ZQKF:OMU,1:AA32:10.1.2.0::120; Example Configuring IP for BTS O&M using tree topology ATM layer

This example presents IP for BTS O&M configuration in RNC when tree topology ATM layer and static routing are used. 1. Create IP interfaces towards the BTS in OMU. Assign logical IP addresses and destination IP addresses to the unnumbered point-to-point network interfaces of the OMU unit, with MTU value 1500, and accept default values for the rest of the parameters. ZQRN:OMU:AA1,U:10.1.1.2,L::10.1.2.1:1500:UP; ZQRN:OMU:AA2,U:10.1.1.2,L::10.1.3.1:1500:UP; 2. Create an IP over ATM interface between the IP interface and the ATM termination point. Configure a TCP/IP ATM interface with network interface names AA1 (to OMU from ATM interface 1) and AA2 (to OMU from ATM interface 2) using VPI 0 and VCI 32 and accept default values for the rest of the parameters. ZQMF:OMU,,L:AA1:1,0,32; ZQMF:OMU,,L:AA2:2,0,32; 3. Create static routes for the BTS branch. Create static routes for OMU to the IP subnetworks 10.1.2.0/24 and 10.1.3.0/24 via the router with IP addresses 10.1.2.1 and 10.1.3.1. ZQKC:OMU,0:10.1.2.0,24:10.1.2.1,:LOG; ZQKC:OMU,0:10.1.3.0,24:10.1.3.1,:LOG;

120 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

10
10.1

Creating Iu-CS interface (RNC-MGW)
Configuring transmission and transport resources
For information on configuring transmission and transport resources, refer to Configuring transmission and transport interfaces.

10.2
10.2.1

Configuring ATM-based signalling channels
Creating remote MTP configuration
Purpose

In most cases the MTP needs to be configured to the network element. Before configuring the MTP, the signalling network has to be planned with great care. See SS7 network planning principles. The SS7 signalling configuration is needed for the following interfaces:

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

121 (240)

RNC Integration

.

Iu-CS interface, between MGW and RNC. The configuration is based on ATM or IP (SIGTRAN). For the ATM configuration, see the instructions in this chapter. For information on configuring SS7 signalling over IP (SIGTRAN), refer to Configuring IP-based signalling channels. Iur interface, between RNC and RNC; nodal functionality in MGW (see Figure AAL bearer establishment from RNC 1 to RNC 2 for illustration). The configuration is based on ATM or IP (SIGTRAN). For the ATM configuration, see the instructions in this chapter. For information on configuring SS7 signalling over IP (SIGTRAN), refer to Configuring IP-based signalling channels.
MSC Server RANAP MSC Server

.

BICC

Iu-CS RNC 1 H.248

Iur

Iur Nb MGW 1 MGW 2 Nb MGW 3

RNC 2 Iu-CS

Figure 7.
.

AAL bearer establishment from RNC 1 to RNC 2

Iu-PS interface, between RNC and SGSN. The configuration is based on ATM or IP (SIGTRAN). For the ATM configuration, see the instructions in this chapter. For information on configuring SS7 signalling over IP (SIGTRAN), refer to Configuring IP-based signalling channels.

Before you start

Before you start to create signalling links, check that the SS7 services and the MTP signalling point have been created. For instructions, see Creating local signalling configuration for RNC.

122 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

The parameter set related to the signalling link can be used to handle several signalling link timers and functions. If the ready-made parameter packages do not cover all occurring situations, you can create more parameter sets, modify the relevant parameters and then attach the new parameter set to the signalling link. It is advisable to find out if there will be such special situations before you start configuring the MTP. See Signalling link parameters. The following are two examples of special situations in which TDM signalling links require modifications in the parameter set:
.

One of the signalling links goes via satellite, and the level 2 error correction method has to be preventive_cyclic_retransmission instead of the usual basic_method. National SS7 specification defines some of the timer values so that they are different from the general recommendations.

.

Steps
1. Check that the signalling links are distributed evenly between different ICSUs Use the following command to display the existing signalling links. ZNCI; It is recommended that you allocate signalling links between all working ICSU units to distribute the load.

Caution
It is very important that signalling links belonging to the same linkset are allocated to different ICSU units to avoid the whole linkset to become unavailable in an ICSU switchover.

2.

Create signalling links (NCS)

Note
Before creating ATM signalling links, check that there are free VCLtps available and that they are correctly configured. For instructions, see Create VCLtps for CBR traffic in Creating ATM resources in RNC.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

123 (240)

RNC Integration

Note
Remember to check that the network element is adequately equipped before you start creating signalling links. You can do this with the WFI command.

To create ATM signalling links, give the command: ZNCS:<signalling link number>:<external interface id number>,<external VPI-VCI>:<unit type>,<unit number>:<parameter set number>; It is advisable to create the signalling links belonging to the same signalling link set into different signalling units, if this is possible. This way a switchover of the signalling unit does not cause the whole signalling link set to become unreachable.

Note
The Signalling Link Code (SLC) and the Time Slot (TSL) have to be defined so that they are the same at both ends of the signalling link. You can number the signalling links within the network element as you wish. The default value for the number is always the next free number. To interrogate existing signalling links, use the NCI or NEL command.

3.

Create SS7 signalling link set (NSC) Create a signalling link set for each destination. A signalling link set consists of one or several links. The signalling links belonging to the signalling link set cannot be activated until the signalling link set is connected to a signalling route set. You can reserve more links for a link set with the NSC command. You can later add links to a signalling link set with the NSA command. ZNSC:<signalling network>,<signalling point code>, <signalling link set name>:<signalling link number>, <signalling link code>;

124 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

The parameters signalling network and signalling point code define the network element where the signalling link set leads to. To interrogate the existing signalling link sets, use the NSI or NES command. 4. Create signalling route set to MGW (NRC) When a signalling route set is created, a parameter set is attached to it. The parameter set can be used to handle several MTP3 level functions. If the predefined parameter sets do not cover all occurring situations, you can create more parameter sets, modify the relevant parameters and then attach the new parameter set to the signalling route set. See Signalling route set parameters. Create a signalling route set for each destination. You can create all signalling routes that belong to the same route set at the same time with the same command. ZNRC:<signalling network>,<signalling point code>, <signalling point name>,<parameter set number>,<load sharing status>,<restriction status>:<signaling transfer point network>,<signalling transfer point code>,<signalling transfer point name>,<signalling route priority>; The parameters signalling transfer point code and signalling transfer point name are used when the created signalling route is indirect, that is the route goes via signalling transfer point (STP). There is no need to use those two parameters when the RNC is directly connected to the MGW.

Note
A signalling point cannot be used as an STP unless it is first equipped with a direct signalling route. For more information about signalling route set priorities, see SS7 network planning principles. To add signalling routes to an existing signalling route set, use the NRA command.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

125 (240)

RNC Integration

5.

Create signalling route set to MSS via MGW (NRC) Create a signalling route set for each destination. You can create all signalling routes that belong to the same route set at the same time with the same command. Later you can add signalling routes to a route set with the NRA command. ZNRC:<signalling network>,<signalling point code>, <signalling point name>,<parameter set number>,<load sharing status>,<restriction status>:<signaling transfer point network>,<signalling transfer point code>,<signalling transfer point name>,<signalling route priority>; The route goes via MGW which is working as a signalling transfer point (STP) when the created signalling route is indirect. The parameters signalling transfer point code and signalling transfer point name are the same as the MGW's signalling point code and the name of the MGW.

10.2.2

Activating MTP configuration Steps
1. Allow activation of the signalling links (NLA) Use the following command to allow the activation of the previously created signalling links: ZNLA:<signalling link numbers>; 2. Activate the signalling links (NLC) Use the following command to activate the previously created signalling links: ZNLC:<signalling link numbers>,ACT; The signalling links assume either state AV-EX (active) or UA-INS if the activation did not succeed. Activation may fail because links at the remote end are inactive or the transmission link is not working properly. For more information, see States of signalling links.

126 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

Note
To interrogate the states of signalling links, use the commands NLI or NEL.

3.

Allow activation of the signalling routes (NVA) Use the following command to allow the activation of the previously created signalling routes: ZNVA:<signalling network>,<signalling point code>: <signalling transfer point network>,<signalling transfer point code>;

4.

Activate signalling routes (NVC) The following command activates the previously created signalling routes: ZNVC:<signalling network>,<signalling point code>: <signalling transfer point network>,<signalling transfer point code>:ACT;

Note
To interrogate the states of signalling routes, use the NVI, NER or NRI commands.

When you are dealing with a direct signalling route, the signalling route set assumes the state AV-EX if the related link set is active; otherwise it assumes the state UA-INS. A signalling route going through an STP can also assume the state UA-INR if the STP has sent a Transfer Prohibited (TFP) message concerning the destination point of the route set. For more information, see States of signalling routes. Example Example of activating an MTP configuration

In this example, you change the state of a signalling route which is leading to the signalling point 302. The route is defined in the signalling point 301 that is located in the national signalling network NA0.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

127 (240)

RNC Integration

First, you change the signalling route state to ACTIVATION ALLOWED, and then you can take the signalling route into service. ZNVA:NA0,302:; The execution printout can be as follows:

ALLOWING ACTIVATION OF DESTINATION: NET SP CODE H/D --- -----------------NA0 0302/00770 COMMAND EXECUTED

SIGNALLING ROUTE SP ROUTES: NAME NET SP CODE H/D ----- --- --------------MSS2 NA0 0302/00770

SP NAME ----MSS2

ACTIVATION ALLOWED

After this, you use the NVC command to activate the route: ZNVC:NA0,302::ACT; The execution printout can be as follows:
CHANGING SIGNALLING ROUTE STATE DESTINATION: SP ROUTES: NET SP CODE H/D NAME NET SP CODE H/D --- ------------------ ----- --- -------------NA0 0302/00770 MSS2 NA0 0302/00770 COMMAND EXECUTED

SP NAME ------MSS2

OLD STATE ------UA-INU

NEW STATE PRIO ------ ---AV-EX 2

10.2.3

Setting MTP level signalling traffic load sharing
Purpose

With MTP level signalling traffic load sharing you can share the signalling traffic between signalling routes and between signalling links belonging to the same link set. Within a signalling link set, load sharing is implemented so that it automatically covers all links that are in active state. Load sharing between signalling routes takes effect only after you have allowed load sharing by defining the same priority for all signalling routes and by allowing load sharing in that route set.
Before you start

Before setting the load sharing, plan carefully which kind of load sharing is suitable in the signalling network. For more information, see MTP level signalling network.

128 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

See also Modifying MTP level signalling traffic load sharing.

Steps
1. Check signalling route priorities and load sharing status, if needed (NRI) ZNRI:<signalling network>,<signalling point code>; 2. Check MTP load sharing data (NEO) Check which signalling links transmit each of the Signalling Link Selection Field (SLS) values. You can use this command to separately interrogate the load sharing data concerning either messages generated by the own signalling point or STP signalling traffic. Notice that the load sharing system is different for STP traffic according to the ANSI standards. ZNEO:; 3. Modify signalling route priority, if needed (NRE) The priority can vary between 0-7, the primary priority being 7. ZNRE:<signalling network>,<signalling point code>: <signalling transfer point network>,<signalling transfer point code>,<new signalling route priority>; 4. Allow load sharing in the signalling route set, if needed (NRB) If load sharing is not allowed in the signalling route set (output of the NRI command), you have to change the load sharing status. ZNRB:<signalling network>,<signalling point codes>: LOAD=<load sharing status>;

10.2.4

Creating remote SCCP configuration
Purpose

The SCCP is needed on a network element if the element:

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

129 (240)

RNC Integration

.

is used for switching calls is used for switching IN services acts as SCCP-level Signalling Transfer Point (STP).

.

.

Before you start

Check that the whole network has been carefully planned, that all necessary hardware has been installed on the network element, and that the Message Transfer Part (MTP) has already been configured. Verify the following items:
.

Check that the signalling points have been created on the MTP (the NRI command). Check which parameter set is used, and whether it is necessary to modify the values of existing parameter sets to meet the present conditions and requirements (the OCI command). Check which subsystems are used. Check the data on subsystem parameter sets (the OCJ command), and the possible modifications on them (the OCN command). Check that the SCCP service has been created on the MTP level (the NPI command). Before you can create the SCCP to the network element, the SCCP service has to be created. To check that the service has been created, use the NPI command. If there is no SCCP service created on the MTP level, create it with the NPC command (more information in Creating remote MTP configuration).

.

.

.

.

Note
The SCCP management subsystem (SCMG) is automatically created when you create the SCCP for the signalling point.

Note
The subsystems which use the Transaction Capabilities are configured in a similar way, and no further configuration is needed (as the TC is automatically used for suitable subsystems).

130 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

Steps
1. Create remote SCCP signalling points and subsystems (NFD) In addition to creating the SCCP signalling point and its subsystems, you need to define the other SCCP signalling points and the subsystems of the other SCCP signalling points of the network, which are involved in SCCP level traffic. ZNFD:<signalling network>, <signalling point code>, <signalling point parameter set>: <subsystem number>, <subsystem name>, <subsystem parameter set number>,Y; You can add more subsystems to a signalling point later by using the NFB command. The system may need new subsystems, for example, when new services are installed, software is upgraded or network is expanded. When you are adding subsystems, you need to know which parameter set you want the subsystems to use or which one has to be used. You can display the existing parameter sets by using the OCJ command. When you want to modify the parameters, use the OCN command, and to create a new parameter set, use the OCA command. 2. Create translation results, if necessary (NAC) The translation result refers to those routes where messages can be transmitted. All the signalling points that are meant to handle SCCP level traffic must be defined at a signalling point. At this stage you have to decide whether the routing is based on global title (GT) or on subsystem number. ZNAC:NET=<primary network>,DPC=<primary destination point code>,RI=<primary routing indicator>; If you want to have a back-up system for routes or the network, you can create alternative routes that will then be taken into service if the primary route fails. Also it is possible to use load sharing for up to 16 destinations by giving value YES for parameter <load sharing>. 3. Create global title analysis, if necessary (NBC)

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

131 (240)

RNC Integration

Before creating the global title analysis, check the number of the translation result so you can attach the analysis to a certain result. Use the NAI command. For more information about global title analysis, see SS7 network planning principles. ZNBC:ITU=<itu-t global title indicator>,LAST=<last global title to be analysed>:TT=<translation type>, NP=<numbering plan>,NAI=<nature of address indicator>:<digits>:<result record index>; 4. Set broadcast status (OBC) It is recommended to add local broadcast status of SCCP subsystem to RNC. The local broadcast status (using the OBC command) informs the subsystems of the own signalling point about changes in the subsystems of the remote signalling points.

Note
When setting the broadcasts, consider carefully what broadcasts are needed. Incorrect or unnecessary broadcasts can cause problems and/ or unnecessary traffic in the signalling network. Depending on the network element, the subsystems needing the broadcast function are the following: . RANAP Radio Access Network Application Part . RNSAP Radio Network Subsystem Application Part

Local broadcasts: ZOBC:<network of affected subsystem>,<signalling point code of affected subsystem>,<affected subsystem number>:<network of local subsystem>,<local subsystem number>:<status>; 'BROADCAST STATUS OF SCCP SIGNALLING POINTS' definitions (using the OBM and OBI commands) are not needed in the RNSAP and RANAP interfaces connected to RNC, because they cause too much unnecessary signalling. For more information, see SCCP level signalling network.

132 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

10.2.5

Activating SCCP configuration Steps
1. Activate remote SCCP signalling points (NGC) ZNGC:<signalling network>, <signalling point codes>: ACT; You do not have to activate the own SCCP signalling point. 2. Check that the signalling point is active (NFI/NGI) ZNFI; OR ZNGI; Notice that if you use the default values in this command, only the signalling points of network NA0 are shown. For more information, see States of SCCP signalling points.
Expected outcome

In the command printout, the state of signalling point should be AVEX.
Unexpected outcome

If the signalling point assumes state UA-INS, there is a fault on the MTP level. Example When you examine an example system using the NFI or NGI commands, all signalling points should be in normal state AV-EX. Note that the signalling point 101H cannot be seen because the SCCP is not defined in it. For command ZNGI:NA0,:N; the execution printout can be as follows:
SCCP STATES DESTINATION: NET SP CODE H/D SP NAME ROUTING: NET SP CODE H/D SP NAME

STATE RM

STATE

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

133 (240)

RNC Integration

--NA0 NA0 NA0 NA0 NA0

-----------------0102/00258 0301/00769 0302/00770 0311/00785 0312/00786

----- ----- -PSTN2 AV RNC1 OWN SP MSS2 AV RNC1 BSC2 AV AV -

--NA0 NA0 NA0 NA0

-----------------0102/00258 0302/00770 0311/00785 0312/00786

----- ------PSTN2 AV-EX MSS2 RNC1 BSC2 AV-EX AV-EX AV-EX

COMMAND EXECUTED

3.

Activate remote SCCP subsystems (NHC) ZNHC:<signalling network>, <signalling point codes>: <subsystem>:ACT; To display the subsystem states, use the NHI or NFJ command. When remote subsystems are being activated, their status is not checked from the remote node. The remote subsystem status becomes AV-EX if the remote node is available, although the actual subsystem may be unavailable or even missing. The status of the unavailable subsystem will be corrected with the response method as soon as a message is sent to it. Use the NHI command to check that the subsystems have assumed state AV-EX. If not, the reason may be faulty or missing distribution data. Correct the distribution data and check the state again. Another reason for the subsystems not to be operating is that the subsystem at the remote end is out of service. For more information, see States of SCCP subsystems.

4.

Set the SS7 network statistics, if needed By setting the SS7 network statistics, you can monitor the performance of the SS7 network. You do not have to do it in the integration phase; you can do it later.

10.3

Configuring IP-based signalling channels
Purpose

As SCCP/M3UA/SCTP/IP/AAL5/ATM are implemented to RNC, IP-based Iu-PS, Iu-CS and Iur SS7 signalling stack can be used. SS7 over IP signalling link set is configured in the RNC using IPoA (IP over ATM).

134 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

Before you start

Configure ATM resources. See Creating ATM resources in RNC.

Note
In addition to the MML based configuration the IP over ATM connection can configured via the IP plan interface from the NetAct. The IP plan support covers the basic support for the MML commands QMF, QRN and QKC and does not contain the OSPF configuration. For further details see IP plan interface in document RNC Operation and Maintenance.

Steps
1. Configure two IP over ATM interfaces to the signalling unit (QMF)

Note
Signalling unit shall be an active state before configuration.

ZQMF:<unit type>,[<unit index>],<logical/physical unit>:<IP interface>:<ATM interface>,<VPI number>, <VCI number>:[<encapsulation method>],[<usage | IPOAM def>];

The following example configures two IP interfaces (AA0 and AA1) over the VCLtp created during configuring ATM resources:
ZQMF:ICSU,0,L:AA0:2,20,30:1,IPOAM; ZQMF:ICSU,0,L:AA1:2,20,31:1,IPOAM; 2. Assign IP addresses to both ATM interfaces of signalling unit (QRN)

Note
IP addresses shall be assigned from different subnetwork.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

135 (240)

RNC Integration

ZQRN:<unit type>,[<unit index>]:<interface name>, [<point to point interface type>]:<IP address>,[<IP address type>]:[<netmask length>]:[<destination IP address>]:[<MTU>]:[<state>];

The following example configures IP addresses for interfaces configured in step 1:
ZQRN:ICSU,0:AA0:1.2.3.4:32:1.2.3.1; ZQRN:ICSU,0:AA1:2.2.3.4:32:2.2.3.1; 3. Create static routes if needed (QKC)

Note
When the destination address (OYA) associated with signaling point is just the destination address (QRN) of IPoA connection, it is unnecessary to create static routes.

ZQKC:<unit type>,<unit index>:[<destination IP address>],[<netmask length>]:<gateway IP address>, [<local IP address>]:[<route type>];

Following are examples:
ZQKC:ICSU,0:10.2.3.0,:1.2.3.1:LOG:; ZQKC:ICSU,0:20.2.3.0,:2.2.3.1:LOG:; 4. Create own signalling point, if signalling point does not exist (NRP) ZNRP:<signalling network>,<signalling point code>, <signalling point name>,<own signalling point handling>:<ss7 standard>:<number of spc subfields>: <spc subfield lengths>;

Following is the example:
ZNRP:NA0,200,SP200,STP:STAND=ITU-T:3::; 5. Create association set (Role Client) (OYC)

136 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

ZOYC:<association set name>:<role>;

Following is the example:
ZOYC:TOMGW100:C:; 6. Add SCTP association to the association set (OYA) ZOYA:<association set name>:<unit identification>, [source port number]:<primary destination IP address>,[netmask length]:[secondary destination IP address],[netmask length]:<parameter set name>:;

Following is the example:
ZOYA:TOMGW100:ICSU,0:"10.2.3.4",8:"20.2.3.4",8: SS7; 7. Add source IP addresses to signalling unit (OYN)

Note
IP addresses should be from different subnetwork.

ZOYN:<unit type>,<unit index>:<IP address version>: <primary source IP address>,[secondary source IP address];

Following is the example:
ZOYN:ICSU,0:IPV4:"1.2.3.4","2.2.3.4":; 8. Create signalling link set for M3UA (NSP) ZNSP:<signalling network>,<signalling link point code>,<signalling link set name>:<signalling link number>:<association set>;

Following is the example:
ZNSP:NA0,100,IP100:10:TOMGW100:; 9. Create signalling route set (NRC)

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

137 (240)

RNC Integration

ZNRC:<signalling network>,<signalling point code>, <signalling point name>,<parameter set number>, [<load sharing status>],[<restriction status>]: [<signalling transfer point network>],[<signalling transfer point code>],[<signalling transfer point name>],<signalling route priority>;

Following is the example:
ZNRC:NA0,100,IP100,6,,:,,,7; 10. Activate route set and signalling link set (NVA/NVC/NLA/NLC) ZNVA:<signalling network>,<signalling point code>: <signalling transfer point network>,<signalling transfer point code>; ZNVC:<signalling network>,<signalling point code>: <signalling transfer point network>,<signalling transfer point code>:ACT; ZNLA:<signalling link numbers>; ZNLC:<signalling link numbers>,ACT;

Following are examples:
ZNVA:NA0,100:,:; ZNVC:NA0,100:,:ACT; ZNLA:10:; ZNLC:10,ACT;

10.4

Configuring Iu-CS parameters of RNC
Before you start

The RNC object has to be opened before the procedure can take place.

138 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

Note
If the Nokia multi-operator RAN feature is in use, you have to create and configure one Iu-CS interface per operator.

Note
If the IMSI-based handover is in use, you can configure up to four PLMN IDs per core item.

Steps
1. 2. Select the Core Network tab from the RNC dialogue. Fill in and check core network related parameters. Fill in and check the core network related data, that is, SS7 signalling parameters and the identification parameter of the core network element. Also fill in all RANAP-related parameters. For more information on parameters, see WCDMA RAN Parameter Dictionary.

Note
If there are cells under this core network that are already using the Global PLMNid parameter, their value cannot be changed.

3.

Check the value of the digit analysis tree.

Note
Once you have created digit analyses with an MML, do not change the value of digit analysis tree from the GUI.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

139 (240)

RNC Integration

10.5

Creating routing objects and digit analysis for Iu interface in RNC
Purpose

This procedure describes how to create routing objects for the Iu interface with MML commands. The associated signalling used is broadband MTP3 signalling. The routing objects must be created at both ends of the Iu interface between two network elements before any user plane connections can be built between them. The analysis tree for configuring the Iu interface is set by using the RNC RNW Object Browser application.

Note
When creating digit analysis, you must add an Authority and Format Identifier (AFI) before the digit sequence in order to avoid conflicts with different number formats. AFI indicates the format of AESA number (the first byte of AESA). If, for example, AFI is 49, add digits 4 and 9.

Before you start

Before you create routing objects, make sure that the appropriate signalling (broadband MTP3) has been created and the associated VC link termination points (VCLtps) for the endpoints have been created. Furthermore, the route under which the endpoints are to be created must allow these type of the endpoints.

Steps
1. Create an AAL type 2 route (RRC) ZRRC:ROU=<route number>,TYPE=<route type>: PRO=<protocol>:NET=<signalling network>, SPC=<signalling point code>,ANI=<aal2 node identifier>; The ANI must be identical for all routes with the same SPC and the same signalling network. 2. Create an endpoint group (LIC) ZLIC:<route number>,<ep group index>:<ingress service category>,<egress service category>;

140 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

The ingress and egress service categories should always be Constant Bit Rate (CBR). 3. Check that there is a free VCLtp (LCI) ZLCI:<interface id>,VC:<VPI>:FREE; Of these VCIs, all those with the service category CBR in both directions can be used in the next step. 4. Create an endpoint (LJC) ZLJC:<ep type>,<route number>,<connection id>: <interface id>,<VPI>,<VCI>:<ownership>:[<loss ratio>,<mux delay>]; The system will automatically sort this endpoint into the endpoint group of step 2 since their service categories match. Repeat steps 1-4 in the MGW before continuing with step 5.

Note
You must create a corresponding routing structure (steps 1-4) in the remote (PEER) network element before you can proceed to step 5. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if this end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifier must have the same value in both ends of a certain connection.

5.

Unblock the AAL type 2 path (LSU) The endpoints must have been created at both ends of the interface before the AAL type 2 path between them can be unblocked. ZLSU:<ANI>:<AAL type 2 path identifier>:<execution time>;
Expected outcome

The execution printout followed by the unblocking should indicate that both the local end and the remote end of the AAL type 2 path are in an unblocked state.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

141 (240)

RNC Integration

Unexpected outcome

The AAL type 2 path is still in blocked state. Repeat the unblocking command.
Unexpected outcome

If the remote end has not agreed unblocking, Then
verify that the remote end is working properly and that it can be reached. Then repeat the command. As long as the remote end cannot agree to unblocking an AAL type 2 path, the system will not select it. 6. Create digit analysis (RDC) Create a digit analysis for a specific digit sequence. Add an AFI before the digit sequence in order to avoid conflicts with different number formats. Check that the analysis tree has been set for the Iu interface by using the RNC RNW object browser. ZRDC:DIG=<digits>,TREE=<analysis tree>:ROU=<route number>;

Note
The address identifies the location of a network termination point. ATM End System Adresses (AESAs) are defined by ATM Forum. AESA consists of Initial Domain Part (IDP) and Domain Specific Part (DSP) and it is always 40 digits long. The IDP specifies an administration authority which has the responsibility for allocating and assigning values of the DSP. The first two digits of IDP are called Authority and Format Identifier (AFI). The AFI indicates the type of AESA that will follow. The last part of IDP is the actual IDP address. The leading zeroes of AESA numbers are used as padding digits to fill up the address. A trailing F(s) are used to obtain octet (2 digits) alignment or to make the number left justified. The leading zeroes and trailing F(s) are removed before creating a digit analysis. This is important because, when system analyses received digits a corresponding conversion is made. If digit analyses are created otherwise, the correct, matching analysis result cannot be found.

142 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

.

.

.

E.164 AESA E.164 part of E.164 AESA is the 16 digits after AFI (45). E.164 part may include leading zeroes and/or a trailing F. The rest of the number is DSP part. DCC AESA DCC part of DCC AESA is 4 digit ISO country code after AFI (39). DCC part may include F(s). The rest of the number is DSP part. ICD AESA ICD part of ICD AESA is 4 digits after AFI (47). ICD part may include F(s). The rest of the number is DSP part.

The following changes in the format of numbers must be taken into account when handling analyses: . E.164 ATM format (AFI = 0 x 45) . Zeros between AFI and the following non-zero digit are removed. . The 16th digit of E.164 part (F digit) is removed. . Example: 45000000358951121F --> 45358951121 . DCC ATM format (AFI = 0 x 39) . The fourth digit (F digit) is removed. . Example: 39123F1234 --> 391231234 . ICD ATM format (0 x 47) . Possible F digits are removed from the ICD part of the number (F digits are removed from digits 1-4). . Example: 47123F1234 --> 471231234

Example 1.

Create routing objects for Iu interface

Create an AAL type 2 route. The route number is 13, the protocol is Message Transfer Part Level 3, the signalling network is NA0, the signalling point code is 24, and the AAL type 2 node identifier is AAL2HEL1. ZRRC:ROU=13,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=24, ANI=AAL2HEL1;

2.

Create an endpoint group under route 13. The endpoint group ID is automatically selected by the system. The termination points in this group have the Constant Bit Rate service category for both ingress and egress directions.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

143 (240)

RNC Integration

ZLIC:13:C,C; 3. Check that there is a free VCLtp under the VPLtp(s). ZLCI:5,VC:<VPI>:FREE; Note that you can check all the available VPIs. Out of these VCIs all those with service category CBR in both directions can be used in the next step. 4. Create a VCC endpoint (VCCep) under the route 13 created in the first step. The AAL type 2 path is 11. The interface ID is 5, VPI 12, and VCI 1045. The current network element owns the AAL type 2 path. The AAL type 2 loss ratio is 10–3 and the AAL type 2 multiplexing delay is 10 ms. ZLJC:VC,13,11:5,12,1045:LOCAL:3,100; The system will automatically sort this endpoint into the endpoint group of step 2 since their service categories match.

Note
You must create a corresponding routing structure (steps 1-4) in the remote (PEER) network element before you can proceed to step 5. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if this end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifier must have the same value in both ends of a certain connection. 5. Unblock the AAL type 2 path 11. The ANI is AAL2HEL1 and the allowed waiting time for the execution of the blocking command is 18 seconds. ZLSU:AAL2HEL1:11:18; 6. Create digit analysis without charging for a digit sequence 491234 in analysis tree 25. ZRDC:DIG=491234,TREE=25:ROU=13;

144 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

10.6

Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface
Purpose

There are two different approaches in creating digit analysis for the Iu interface:
.

creating (basic) digit analysis, where each destination has only one subdestination creating digit analysis, where each destination can have more than one subdestination.

.

Creating subdestinations for a destination and defining routing policy (the latter approach above) are optional features. In general, creating basic digit analysis is sufficient, and it is recommended that the latter approach be used only if there is a definite need (for example, alternative routing) for several subdestinations and routing policy measures. The routing policy function allows you to utilise alternative routing and percentage call distribution (also known as load sharing). With alternative routing, another subdestination can be used if connection to primary direction is broken or the subdestination selected before is congested. With percentage call distribution, traffic to a destination can be distributed among two or more subdestinations in predefined proportions.

Note
The system can use alternative routing only if you have purchased this feature.

The following figure illustrates the alternative routing and the percentage call distribution between RNC and MGW:

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

145 (240)

RNC Integration

Route 2

MGW / ATM Switch Gothenburg

Route 11 RNC Oulu Route 3 TREE 55, DIGITS 4535840114 MGW / ATM Switch Helsinki1 MGW London Address = 4535840114

Digit analysis

MGW / ATM Switch Hamburg

Destination London Primary Secondary 50 % Subdestination Helsinki1 Subdestination Gothenburg 50 % Subdestination Hamburg

Route 11

Route 2

Route 3

Figure 8.

Alternative and percentage routing between RNC and MGW

Before you start

Before you create routing objects, make sure that the appropriate (broadband MTP3) signalling has been created and the associated VC link termination points (VCLtps) for the endpoints have been created. You can print the analysis and the components by using the commands of the RI command group.

146 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

Tip
If the RNC owns the AAL type 2 path, it starts the AAL2 channel identifier (CID) reservation from 8. If the MGW owns the AAL type 2 path, it starts the reservation from 255. Therefore make sure to set the ownership consistently: one NE owns the AAL 2 path (OWNERSHIP=LOCAL), the other gets the indicator that its peer is the owner (OWNERSHIP=PEER). With this mechanism you avoid the CID reservation collision.

Steps
1. Create an AAL type 2 route (RRC) ZRRC:ROU=<route number>,TYPE=AAL2:PRO=MTP3: NET=<signalling network>,SPC=<signalling point code>,ANI=<AAL2 node identifier>; 2. Create an endpoint group (LIC) ZLIC:<route number>,<ep group index>:<ingress service category>, <egress service category>; The ingress and egress service categories should always be Constant Bit Rate (CBR). 3. Check that there is a free VCLtp (LCI) ZLCI:<interface id>,VC:<VPI>:FREE; All those VCIs with service category CBR in both directions can be used in the next step. 4. Create an endpoint (LJC) ZLJC:<ep type>,<route number>,<AAL type 2 path identifier>:<interface id>,<VPI>,<VCI>:(LOCAL| PEER):[<loss ratio>,<mux delay>]; The system will automatically place this endpoint into the endpoint group of step 2 since their service categories match.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

147 (240)

RNC Integration

You must create a corresponding routing structure (steps 1-4) in the MGW (PEER) network element before you can proceed to step 5. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if one end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifier must have the same value at both ends of a certain connection. 5. Unblock the AAL type 2 path (LSU) Unblock the AAL type 2 path in both RNC and MGW. ZLSU:<ANI>:<AAL type 2 path identifier>:<execution time>;
Expected outcome

The execution printout should indicate that both the local end and the remote end of the AAL type 2 path are in unblocked state.
Unexpected outcome

The AAL type 2 path is still in blocked state. Make sure that the configuration of the AAL type 2 path is done correspondingly at the other end of the connection. Then repeat the unblocking command. 6. Create subdestinations (RDE) ZRDE:NSDEST=<name of subdestination>:ROU=<route number>; You can attach from 1 to 5 subdestinations to each destination. Repeat the command to create the required number of subdestinations. 7. Create a destination and define an alternative routing for the destination (RDE) ZRDE:NDEST=<name of destination>,ALT=<alternative>: NSDEST=<name of subdestination>; Repeat this command separately for all the subdestinations that you want to attach to the same destination (NSDEST). 8. Create digit analysis (RDC)

148 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

Create a digit analysis for a specific digit sequence. The specific digit sequence is the MGW AAL type 2 Service Endpoint Address of the remote end. The number of the analysis tree must be the same as the tree number set for the desired Virtual Media Gateway (VMGW) with the JVC command. When creating digit analysis, you must add an Authority and Format Identifier (AFI) before the digit sequence in order to avoid conflicts with different number formats. AFI indicates the format of AESA number (the first byte of AESA). If, for example, AFI is 45 add digits 4 and 5. ZRDC:TREE=<analysis tree>,DIG=<digits>:NDEST=<name of destination>; 9. Define the subdestination selection order and percentage call distribution (RMM) By setting a percentage to an alternative, you could change the subdestination type to percentage routing. The sum of all the percentage values entered for subdestinations must be 100. Alternative routing can be chosen by giving 'A' instead of percentage value. This sets the subdestination type to alternative routing. If you want to use alternative routing for the subdestinations, do not define new subdestination type and percentages (by RMM). Alternative routing is the default routing policy. ZRMM:NDEST=<destination name>:SELO=<selection order>,CHECK=<check associated analyses>: SPERC0=<percentage value of subdestination 0>, SPERC1=<percentage value of subdestination 1>, SPERC2=<percentage value of subdestination 2>, SPERC3=<percentage value of subdestination 3>, SPERC4=<percentage value of subdestination 4>; Example Create routing objects and digit analysis for Iu interface with percentage routing

In the following example routing objects and digit analysis with several subdestinations are created. The example also describes how traffic flow over several subdestinations can be manipulated with percentage routing and alternative routing.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

149 (240)

RNC Integration

1.

Create an AAL type 2 route between RNC and MGW. The route number is 11, the protocol is Message Transfer part 3, the signalling network is NA0, the signalling point code is 701, and the identifier of the AAL type 2 destination node is AAL2MGW1. ZRRC:ROU=11,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=701, ANI=AAL2MGW1;

2.

Create an endpoint group under route 11. The endpoint group id is automatically selected by the system. The termination points in this group have the Constant Bit Rate service category for both ingress and egress directions. ZLIC:11,1:C,C;

3.

Check that there is a free VCLtp. ZLCI:<interface id>,VC:<VPI>:FREE; Note that you can check all the VPIs available. All the VCIs with service category CBR in both directions can be used in the next step.

4.

Create an endpoint of VC level (VCCep) under route 11 created in the first step. AAL type 2 path is 5. It is based on the TPI with interface id 2, VPI 1, and VCI 33. The current network element owns the AAL type 2 path. The AAL type 2 loss ratio is 10–3 and the AAL type 2 multiplexing delay is 10 ms. ZLJC:VC,11,5:2,1,33:LOCAL:3,100; The system will automatically place this endpoint into the endpoint group of step 2 since their service categories match. You must create a corresponding routing structure (steps 1-4) in the MGW (PEER) network element before you can proceed to step 5. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if one end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifier must have the same value at both ends of a certain connection.

5.

Unblock the AAL type 2 path 5 in RNC. The ANI is AAL2MGW1 and the allowed waiting time for the execution of the blocking commands is 18 seconds. ZLSU:AAL2MGW1:5:18; You must also unblock the AAL type 2 path in the MGW.

6.

Create three subdestinations, 'HELSINKI1', 'GOTHENBURG' and 'HAMBURG' leading to outside routes:

150 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-CS interface (RNC-MGW)

ZRDE:NSDEST=HELSINKI1:ROU=11; ZRDE:NSDEST=GOTHENBURG:ROU=2; ZRDE:NSDEST=HAMBURG:ROU=3; In this example, it is assumed that routes 2 and 3 have been created separately by following steps 1 to 5 above. 7. Create the destination LONDON, define three subdestinations for it and define HELSINKI1 as the primary routing subdestination, GOTHENBURG as the first alternative and HAMBURG as the second alternative: ZRDE:NDEST=LONDON,ALT=0:NSDEST=HELSINKI1; ZRDE:NDEST=LONDON,ALT=1:NSDEST=GOTHENBURG; ZRDE:NDEST=LONDON,ALT=2:NSDEST=HAMBURG; 8. Create digit analysis for the digit sequence 4535840114 in analysis tree 55. ZRDC:DIG=4535840114,TREE=55:NDEST=LONDON; 9. Create the subdestination selection order and percentage call distibution. Define the selection order and percentage call distribution values of routing alternatives so that the primary subdestination uses alternative routing and the first and the second alternatives use percentage routing. The overflow traffic of the primary alternative is shared out between the first and the second alternatives: ZRMM:NDEST=LONDON:SELO=A-P,CHECK=Y:SPERC0=A, SPERC1=50,SPERC2=50; Once you have created subdestinations and defined percentage call distribution or alternative routing for these, you can modify these settings with the RMM command.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

151 (240)

RNC Integration

152 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-PS interface (RNC-SGSN)

11
11.1

Creating Iu-PS interface (RNC-SGSN)
Configuring transmission and transport resources
For information on configuring transmission and transport resources, refer to Configuring transmission and transport interfaces.

11.2

Configuring signalling channels
Please refer to Configuring ATM-based signalling channels and Configuring IP-based signalling channels.

11.3

Configuring Iu-PS parameters of RNC
Before you start

The RNC object has to be opened before the procedure can take place.

Note
If the Nokia multi-operator RAN feature is in use, you have to create and configure one Iu-PS interface per operator.

Note
If the IMSI-based handover is in use, you can configure up to four PLMN IDs per core item.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

153 (240)

RNC Integration

Steps
1. 2. Select the Core Network tab from the RNC dialogue. Fill in and check core network related parameters. Fill in and check the core network related data, that is, SS7 signalling parameters and the identification parameter of the core network element. Also fill in all RANAP-related parameters. For more information on parameters, see WCDMA RAN Parameter Dictionary.

Note
If there are cells under this core network that are already using the Global PLMNid parameter, their value cannot be changed.

11.4

Configuring IP for Iu-PS User Plane (RNC-SGSN)
Purpose

The purpose of this procedure is to configure IP for the Iu-PS interface between the RNC and the Serving GPRS Support Node (SGSN).
Before you start

Note
In addition to the MML based configuration the Iu-PS interface ATM and IP basic resources can be configured via the IP and ATM plan interface from the NetAct. The ATM plan interface contains the basic support for ATM interface, VPLtp and VCLtp creation while the IP plan support covers the basic support for the MML commands QMF, QRN and QKC. The IP plan support does not cover the OSPF configuration or IP QoS configuration. For more information on the IP plan interface, see IP plan interface in document RNC Operation and Maintenance.

The ATM resources must be created before the interface can be configured. For instructions, see Creating ATM resources in RNC in ATM Resource Management.

154 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-PS interface (RNC-SGSN)

Steps
1. Interrogate the states of the units in the system (USI) Check that the units for which you are going to create network interfaces are in working state (WO-EX). ZUSI:<unit type>; 2. Create IP over ATM interfaces to all GTPUs Create IPoA interfaces to all GTPUs (at least one ATM VCCs per GTPU) according to instructions in Configuring IP over ATM interfaces. Set the value of the encapsulation method parameter to LLC/SNAP. If you want to dedicate a GTPU for real-time IP traffic, set the value of usage parameter to IPOART (this is an optional feature) for all IPoA interfaces of the unit. If not, set the value to IPOAUD. 3. Configure the default static routes You do not need to specify the destination IP address for the default route. The parameter local IP address is only valid for the local IP address based default routes. For normal static routes, you do not need to give the local IP address. For more information about local IP address based default routes, refer to Creating and modifying static routes. For IPv4: ZQKC:<unit type>,<unit index>::<gateway IP address>, [<local IP address>]:[<route type>]; For IPv6: ZQ6C:<unit type>,<unit index>::[<next hop type>]: <address type>:(IP=<ip address> | MAC=<link level mac address>); 4. Create other static routes, if needed For IPv4:

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

155 (240)

RNC Integration

ZQKC:<unit type>,<unit index>:<destination IP address>,[<netmask length>]:<gateway IP address>: [<route type>]; For IPv6: ZQ6C:<unit type>,<unit index>:<destination IP address>,[<prefix length>]:[<next hop type>]: <address type>:(IP=<ip address> | MAC=<link level mac address>); 5. Create OSPF configuration, if necessary Currently, OSPF only supports IPv4. If you want to use OSPF routing on the Iu-PS interface, create the configuration as follows: a. Set the IP address for loopback. ZQRN:<unit type>,<unit index>:<interface name>: <IP address>; b. Configure the OSPF to inform other OSPF routers of the loopback address. ZQKU:<unit type>,<unit index>:<redistribute type and identification>:<metric>; c. Configure the area(s) that include also the neighbouring routers. ZQKE:<unit type>,<unit index>:<area identification>:<stub area>,[<stub area route cost>],<totally stubby area>; d. Configure an interface for that area. ZQKF:<unit type>,<unit index>:<interface specification>:<area identification>:[<hello interval>]:[<router dead interval>]:[<ospf cost>]:[<election priority>]:[<passive>]: [<authentication> | <authentication>, <password>]; 6. Create QoS DiffServ configuration (GTPU), if needed (with service terminal extension) It is also possible to configure QoS DiffServ traffic classification to GTPU units. The main function for IP QoS DiffServ is to assure that real time (rt) traffic has a higher throughput priority than non-real time (nrt) traffic in the GTPU TCP/IP stack. It checks that the traffic is real time or non-real time and processes the traffic with the desired ratio. The configuration is done with the service terminal extension QMDSTEGX in OMU.

156 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-PS interface (RNC-SGSN)

An example of the mapping between DSCP to traffic class is presented in the following table: . Real Time (RT) . Non-Real Time (NRT)

Table 14.

Example of the mapping between DSCP to traffic class Traffic Class

101110 001010, 001100, 001110 010010, 010100, 010110 011010, 011100, 011110 100010, 100100, 100110 000000

RT RT

NRT

NRT

NRT

NRT

If you decided to use QoS DiffServ for the Iu-PS interface, make the configuration as follows: a. Take a service terminal session to working OMU with MML. ZDDS:OMU,<unit index>; b. Load service terminal extension QMDSTEGX.
ZLE:<desired number>, QMDSTEGX;

c.

Configure desired NRT/RT ratio. Replace the x in the following command with the value of the desired number parameter in the previous step.
ZxB:<NRT/RT ratio>;

d.

Configuration desired DSCP values.
ZxC:DSCP,<traffic class>;

Example

IP configuration for Iu-PS with each GTPU connected to one

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

157 (240)

RNC Integration

SGSN unit This example shows how to configure the Iu-PS interface between the RNC and SGSN using two STM-1 interfaces in both RNC and SGSN. In the example, four GTPU units are deployed to handle the Packet Switched Radio Access Bearers in the RNC in load sharing mode. Each GTPU is logically connected to one of the SGSN units, GPLCs. Two IP subnets are used:
.

10.1.1.0/32 for hosts connected to the first GPLC and 10.1.2.0/32 for hosts connected to the second GPLC.
SGSN

.

RNC

GTPU-0

AA1

10.1.1.10

VPI=0, VCI=40
10.1.1.1

10.2.0.0

VPI=0, VCI=41

GPLC1

GTPU-1

AA1

10.1.1.11

STM-1 line #1

GTPU-2

AA2

10.1.2.12

VPI=0, VCI=42
10.1.2.1

10.3.0.0

VPI=0, VCI=43

GPLC2

GTPU-3

AA2

10.1.2.13

STM-1 line #2

= subnet 10.1.1.0/32 = subnet 10.1.2.0/32

Figure 9.

ATM virtual channel connections and IP addresses with each GTPU connected to one GPLC unit

1.

Create ATM resources. Create the following ATM configuration (for instructions, see Creating ATM resources in RNC in ATM Resource Management):

158 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-PS interface (RNC-SGSN)

.

. . .

. .

STM-1 ATM interface (with interface ID 1). This interface is connected to SGSN (GPLC-1) via a direct physical connection or via the SDH transmission network. In ATM interface 1, one VPLtp with VPI=0. In ATM interface 1, two VCLtps with VPI=0 and VCI=40, 41. STM-1 ATM interface (with interface ID 2). This interface is connected to SGSN (GPLC-2) via a direct physical connection or via the SDH transmission network. In ATM interface 2, one VPLtp with VPI=0. In ATM interface 2, two VCLtps with VPI=0 and VCI=42, 43.

2.

Create IP over ATM interfaces to all GTPUs. a. Create IP over ATM interfaces connected to subnet 10.1.1.1/ 32 (GPLC-1). ZQMF:GTPU,0,P:AA1:1,0,40:1,IPOAUD; ZQMF:GTPU,1,P:AA1:1,0,41:1,IPOAUD; b. Create IP over ATM interfaces connected to subnet 10.1.2.1/ 32 (GPLC-2). ZQMF:GTPU,2,P:AA2:2,0,42:1,IPOAUD; ZQMF:GTPU,3,P:AA2:2,0,43:1,IPOAUD; Assign IP addresses to the network interfaces. a. Configure interfaces connected to subnet 10.1.1.1/32 (GPLC1). ZQRN:GTPU,0:AA1:10.1.1.10,P:32:10.1.1.1; ZQRN:GTPU,1:AA1:10.1.1.11,P:32:10.1.1.1; b. Configure the interfaces connected to subnet 10.1.2.1/32 (GPLC-2). ZQRN:GTPU,2:AA2:10.1.2.12,P:32:10.1.2.1; ZQRN:GTPU,3:AA2:10.1.2.13,P:32:10.1.2.1; Create static routes for GTPUs. With the following default routes, all traffic is forwarded to the GPLC unit in the SGSN. ZQKC:GTPU,0::10.1.1.1,:PHY; ZQKC:GTPU,1::10.1.1.1,:PHY; ZQKC:GTPU,2::10.1.2.1,:PHY; ZQKC:GTPU,3::10.1.2.1,:PHY;

3.

4.

Example

IP configuration for Iu-PS with GTPUs connected to both

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

159 (240)

RNC Integration

SGSN units This example shows how to configure the Iu-PS interface between the RNC and SGSN using two STM-1 interfaces in RNC and SGSN. In this example, four GTPU units are deployed to handle the Packet Switched Radio Access Bearers in RNC in load sharing mode. Each GTPU is logically connected to both GPLC units in the SGSN so that even if one link fails, the interface capacity between the RNC and SGSN remains the same. Note that the same redundancy can be achieved by using OSPF instead of static routing (see the next example: configuring Iu-PS when OSPF is in use). Two IP subnets are used:
.

10.2.0.1/32 for hosts connected to the first GPLC unit and 10.3.0.1/32 for hosts connected to the second GPLC unit.

.

In this configuration, RNC always has a connection to the IP addresses of the GPLC units (10.2.0.1 and 10.3.0.1) even if one of the interfaces of a GTPU fails.

160 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-PS interface (RNC-SGSN)

RNC
AA0 10.1.1.10 10.2.0.1 10.3.0.1

SGSN

GTPU-0

AA1 10.1.2.10

VPI=0, VCI=40 VPI=0, VCI=41
10.1.1.1

10.2.0.1

AA0 10.1.1.11

10.3.0.1 10.2.0.1

GTPU-1

AA1 10.1.2.11

VPI=0, VCI=42 VPI=0, VCI=43 STM-1 line #1 VPI=0, VCI=40 VPI=0, VCI=41
10.1.2.1

GPLC-1

AA0 10.1.1.12

10.2.0.1 10.3.0.1

GTPU-2

AA1 10.1.2.12

10.3.0.1

AA0 10.1.1.13

10.3.0.1 10.2.0.1

GTPU-3

VPI=0, VCI=42 VPI=0, VCI=43 STM-1 line #2

GPLC-2

AA1 10.1.2.13

= subnet 10.2.0.1/32 = subnet 10.3.0.1/32 = primary route

Figure 10.

ATM virtual channel connections and IP addresses with GTPUs connected to both GPLC units

1.

Create ATM resources. Create the following ATM configuration (for instructions, see Creating ATM resources in RNC in ATM Resource Management): . STM-1 ATM interface (with interface ID 0). This interface is connected to SGSN (GPLC-1) via a direct physical connection or via the SDH transmission network. . In ATM interface 1, one VPLtp with VPI=0. . In ATM interface 1, four VCLtps with VPI=0 and VCI=40...43. . STM-1 ATM interface (with interface ID 1). This interface is connected to SGSN (GPLC-2) via a direct physical connection or via the SDH transmission network. . In ATM interface 2, one VPLtp with VPI=0. . In ATM interface 2, four VCLtps with VPI=0 and VCI=40...43.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

161 (240)

RNC Integration

2.

Create IP over ATM interfaces to all GTPUs. a. Create IP over ATM interfaces connected to subnet 10.1.1.0/ 32 (GPLC-1). ZQMF:GTPU,0,P:AA0:1,0,40:1,IPOAUD; ZQMF:GTPU,1,P:AA0:1,0,41:1,IPOAUD; ZQMF:GTPU,2,P:AA0:1,0,42:1,IPOAUD; ZQMF:GTPU,3,P:AA0:1,0,43:1,IPOAUD; b. Create IP over ATM interfaces connected to subnet 10.1.2.0/ 32 (GPLC-2). ZQMF:GTPU,0,P:AA1:2,0,40:1,IPOAUD; ZQMF:GTPU,1,P:AA1:2,0,41:1,IPOAUD; ZQMF:GTPU,2,P:AA1:2,0,42:1,IPOAUD; ZQMF:GTPU,3,P:AA1:2,0,43:1,IPOAUD; Assign IP addresses to the network interfaces. Note that the destination address of the IP over ATM interface does not have to be the IP address of the next hop. The IP address and destination IP address of the IP over ATM interface can be in different subnets. a. Configure interfaces connected to subnet 10.2.0.1/32 (GPLC1). ZQRN:GTPU,0:AA0:10.1.1.10,P:32:10.2.0.1; ZQRN:GTPU,1:AA1:10.1.2.11,P:32:10.2.0.1; ZQRN:GTPU,2:AA0:10.1.1.12,P:32:10.2.0.1; ZQRN:GTPU,3:AA1:10.1.2.13,P:32:10.2.0.1; b. Configure interfaces connected to subnet 10.3.0.1/32 (GPLC2). ZQRN:GTPU,0:AA1:10.1.2.10,P:32:10.3.0.1; ZQRN:GTPU,1:AA0:10.1.1.11,P:32:10.3.0.1; ZQRN:GTPU,2:AA1:10.1.2.12,P:32:10.3.0.1; ZQRN:GTPU,3:AA0:10.1.1.13,P:32:10.3.0.1;

3.

4.

Create default static routes for GTPUs. ZQKC:GTPU,0::10.3.0.1,:PHY; ZQKC:GTPU,1::10.3.0.1,:PHY; ZQKC:GTPU,2::10.3.0.1,:PHY; ZQKC:GTPU,3::10.3.0.1,:PHY; There should be one connection and route between GPLC-1 and GPLC-2.

162 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-PS interface (RNC-SGSN)

Example

Configuring Iu-PS when OSPF is in use

This example shows how to configure the Iu-PS interface between the RNC and SGSN using OSPF for routing. When OSPF is in use and a link fails, the user plane traffic is switched to the working link.
RNC
LO0 10.1.1.2 10.1.1.1 10.1.2.1

SGSN

GTPU-0

AA0 10.1.1.10 AA1 10.1.2.10 LO0

VPI=0, VCI=40 VPI=0, VCI=41
10.1.1.1

10.2.0.1

10.1.1.3 10.1.1.1 10.1.2.1

GTPU-1

AA0 10.1.1.11 AA1 10.1.2.11 LO0

VPI=0, VCI=42 VPI=0, VCI=43 STM-1 line #1 VPI=0, VCI=40 VPI=0, VCI=41
10.1.2.1

GPLC-1

10.1.1.4 10.1.1.1 10.1.2.1

GTPU-2

AA0 10.1.1.12 AA1 10.1.2.12 LO0

10.3.0.1

10.1.1.5 10.1.1.1 10.1.2.1

GTPU-3

AA0 10.1.1.13 AA1 10.1.2.13

VPI=0, VCI=42 VPI=0, VCI=43 STM-1 line #2

GPLC-2

= subnet 10.2.0.1/32 = subnet 10.3.0.1/32 = primary route

Figure 11.

Iu-PS configuration with OSPF in use

1.

Create ATM resources. Create the following ATM configuration (for instructions, see Creating ATM resources in RNC in ATM Resource Management): . STM-1 ATM interface (with interface ID 0). This interface is connected to SGSN (GPLC-1) via a direct physical connection or via the SDH transmission network. . In ATM interface 1, one VPLtp with VPI=0. . In ATM interface 1, four VCLtps with VPI=0 and VCI=40...43.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

163 (240)

RNC Integration

.

. .

STM-1 ATM interface (with interface ID 1). This interface is connected to SGSN (GPLC-2) via a direct physical connection or via the SDH transmission network. In ATM interface 2, one VPLtp with VPI=0. In ATM interface 2, four VCLtps with VPI=0 and VCI=40...43.

2.

Create IP over ATM interfaces to all GTPUs. a. Create IP over ATM interfaces connected to subnet 10.1.1.0/ 32 (GPLC-1). ZQMF:GTPU,0,P:AA0:1,0,40:1,IPOAUD; ZQMF:GTPU,1,P:AA0:1,0,41:1,IPOAUD; ZQMF:GTPU,2,P:AA0:1,0,42:1,IPOAUD; ZQMF:GTPU,3,P:AA0:1,0,43:1,IPOAUD; b. Create IP over ATM interfaces connected to subnet 10.1.2.0/ 32 (GPLC-2). ZQMF:GTPU,0,P:AA1:2,0,40:1,IPOAUD; ZQMF:GTPU,1,P:AA1:2,0,41:1,IPOAUD; ZQMF:GTPU,2,P:AA1:2,0,42:1,IPOAUD; ZQMF:GTPU,3,P:AA1:2,0,43:1,IPOAUD; Assign IP addresses to the network interfaces. Note that the destination address of the IP over ATM interface does not have to be the IP address of the next hop. The IP address and destination IP address of the IP over ATM interface can be from different subnets. a. Configure interfaces connected to subnet 10.2.0.1/32 (GPLC1). ZQRN:GTPU,0:AA0:10.1.1.10,P:32:10.1.1.1; ZQRN:GTPU,1:AA0:10.1.2.11,P:32:10.1.1.1; ZQRN:GTPU,2:AA0:10.1.1.12,P:32:10.1.1.1; ZQRN:GTPU,3:AA0:10.1.2.13,P:32:10.1.1.1; b. Configure interfaces connected to subnet 10.3.0.1/32 (GPLC2). ZQRN:GTPU,0:AA1:10.1.2.10,P:32:10.1.2.1; ZQRN:GTPU,1:AA1:10.1.1.11,P:32:10.1.2.1; ZQRN:GTPU,2:AA1:10.1.2.12,P:32:10.1.2.1; ZQRN:GTPU,3:AA1:10.1.1.13,P:32:10.1.2.1; c. Set the loopback IP address for each unit. ZQRN:GTPU,0:LO0:10.1.1.2; ZQRN:GTPU,1:LO0:10.1.1.3; ZQRN:GTPU,2:LO0:10.1.1.4; ZQRN:GTPU,3:LO0:10.1.1.5;

3.

164 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-PS interface (RNC-SGSN)

4.

Create the OSPF configuration. a. Configure the area(s) that include also the neighbouring routers. ZQKE:GTPU,0:0.0.0.1; ZQKE:GTPU,1:0.0.0.1; ZQKE:GTPU,2:0.0.0.1; ZQKE:GTPU,3:0.0.0.1; b. Configure two interfaces for that area. The values for parameters area identification, hello interval and router dead interval must be the same as in the SGSN. You can select AA0 or AA1 as the primary route for user traffic by giving different ospf costs. The interface with lower cost will be preferred. ZQKF:GTPU,0:AA0:0.0.0.1:::10; ZQKF:GTPU,0:AA1:0.0.0.1:::20; ZQKF:GTPU,1:AA0:0.0.0.1:::20; ZQKF:GTPU,1:AA1:0.0.0.1:::10; ZQKF:GTPU,2:AA0:0.0.0.1:::10; ZQKF:GTPU,2:AA1:0.0.0.1:::20; ZQKF:GTPU,3:AA0:0.0.0.1:::20; ZQKF:GTPU,3:AA1:0.0.0.1:::10; c. Configure the OSPF to inform other OSPF routers of the loopback address. ZQKJ:GTPU,0:0.0.0.1:ADD:10.1.1.2:; ZQKJ:GTPU,1:0.0.0.1:ADD:10.1.1.3:; ZQKJ:GTPU,2:0.0.0.1:ADD:10.1.1.4:; ZQKJ:GTPU,3:0.0.0.1:ADD:10.1.1.5:; If the area in step 4.a is not configured as stub area, redistribution can be also used to inform the address of LO0. ZQKU:GTPU,0:IF=LO0; ZQKU:GTPU,1:IF=LO0; ZQKU:GTPU,2:IF=LO0; ZQKU:GTPU,3:IF=LO0; QoS DiffServ configuration for Iu-PS with each GTPU connected to one SGSN unit

Example

This example shows how to configure QoS DiffServ classification to GTPU units. The default traffic class for all DSCPs in non-real time(nrt). The configuration in the example DSCPs will be set to real time. The same configuration will be set for all GTPU units. After DSCP is configured, the values 2, 15, 21, 33, 39 and 54 are real time (rt) and the remaining values

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

165 (240)

RNC Integration

are non-real time(nrt). Real time (rt) and non-real (nrt) packet ratio will be set with value 8 by default. This means that 8 real time packets are processed with one non-real time packet. If the number of real time packets is less than 8, the non-real time packets will be processed after all the real time packets have been processed. 1. Take a service terminal session to OMU and load QMDSTEGX. ZDDS:OMU,0;
ZLE:7,QMDSTEGX;

2.

Configure DSCP traffic classes and NRT/RT ratio.
Z7C:2,RT Z7C:15,RT Z7C:21,RT Z7C:33,RT Z7C:39,RT Z7C:54,RT Z7B:8

166 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iur interface (RNC-RNC)

12
12.1

Creating Iur interface (RNC-RNC)
Configuring transmission and transport resources
For information on configuring transmission and transport resources, refer to Configuring transmission and transport interfaces.

12.2

Configuring signalling channels
Please refer to Configuring ATM-based signalling channels and Configuring IP-based signalling channels.

12.3

Configuring Iur parameters of RNC
Before you start

The Iur interface must be created for each neighbouring RNC. The maximum amount of RNC Iur interfaces is 32. The RNC object has to be opened before the procedure can take place.

Steps
1. 2. Select the neighbouring RNCs tab from the RNC dialogue. Fill in and check the parameters of the neighbouring RNCs. Fill in and check the identification parameters of the neighbouring RNCs as well as the SS7 related signalling parameters. For more information on parameters, see WCDMA RAN Parameter Dictionary. 3. Check the value of the digit analysis tree.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

167 (240)

RNC Integration

Note
Once you have created digit analyses with an MML, do not change the value of the digit analysis tree from the GUI.

12.4

Creating routing objects and digit analysis for Iur interface in RNC
Purpose

This procedure describes how to create routing objects and digit analyses for the Iur interface with MML commands. The analysis tree used for configuring the Iur interface is set by using the RNC RNW object browser application.

Note
When creating digit analysis, you must add an Authority and Format Identifier (AFI) before the digit sequence in order to avoid conflicts with different number formats. AFI indicates the format of AESA number (the first byte of AESA). If, for example, AFI is 49, add digits 4 and 9.

Before you start

Before you create routing objects, make sure that the appropriate signalling (broadband MTP3) has been created and the associated VC link termination points (VCLtps) for the endpoints have been created. Additionally, the route under which the endpoints are to be created must allow the type of the endpoints.

Steps
1. Create an AAL type 2 route (RRC) ZRRC:ROU=<route number>,TYPE=AAL2:PRO=<protocol>: NET=<signalling network>,SPC=<signalling point code>,ANI=<aal2 node identifier>; The ANI is to be identical for all routes with the same SPC and the same signalling network. 2. Create an endpoint group (LIC)

168 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iur interface (RNC-RNC)

ZLIC:<route number>,<ep group index>:<ingress service category>,<egress service category>; The ingress and egress service categories should always be Constant Bit Rate (CBR). 3. Check that there is a free VCLtp (LCI) ZLCI:<interface id>,VC:<VPI>:FREE; Out of these VCIs all these with the service category CBR in both directions can be used in the next step. 4. Create an endpoint (LJC) ZLJC:<ep type>,<route number>,<connection id>: <interface id>,<VPI>,<VCI>:<ownership>:[<loss ratio>,<mux delay>]; The system will automatically sort this endpoint into the endpoint group of step 2 since their service categories match. Repeat steps 1-4 in the remote RNC before continuing with step 5.

Note
You must create a corresponding routing structure (steps 1-4) in the remote (PEER) network element before you can proceed to step 5. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if this end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifier must have the same value in both ends of a certain connection.

5.

Unblock the AAL type 2 path (LSU) The endpoints must have been created at both ends of the interface before the AAL type 2 path between them can be unblocked. ZLSU:<ANI>:<AAL type 2 path identifier>:<execution time>;
Expected outcome

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

169 (240)

RNC Integration

The execution printout followed by the unblocking should indicate that both the local end and the remote end of the AAL type 2 path are in unblocked state and the state has been agreed with the remote end.
Unexpected outcome

If the AAL type 2 path is still in blocked state, Then
repeat the unblocking command
Unexpected outcome

If the remote end has not agreed to unblocking, Then
verify that the remote end is working properly and it can be reached. Then repeat the command. As long as the remote end cannot agree to unblocking an AAL type 2 path, the system will not select it. 6. Create digit analysis (RDC) Create a digit analysis without charging for a specific digit sequence. Add an AFI before the digit sequence in order to avoid conflicts with other number formats. The analysis tree has been set for the Iur interface by using the RNC RNW object browser. ZRDC:DIG=<digits>,TREE=<analysis tree>:ROU=<route number>;

170 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iur interface (RNC-RNC)

Note
The address identifies the location of a network termination point. ATM End System Adresses (AESAs) are defined by ATM Forum. AESA consists of Initial Domain Part (IDP) and Domain Specific Part (DSP) and it is always 40 digits long. The IDP specifies an administration authority which has the responsibility for allocating and assigning values of the DSP. The first two digits of IDP are called Authority and Format Identifier (AFI). The AFI indicates the type of AESA that will follow. The last part of IDP is the actual IDP address. The leading zeroes of AESA numbers are used as padding digits to fill up the address. A trailing F(s) are used to obtain octet (2 digits) alignment or to make the number left justified. The leading zeroes and trailing F(s) are removed before creating a digit analysis. This is important because, when system analyses received digits a corresponding conversion is made. If digit analyses are created otherwise, the correct, matching analysis result cannot be found. . E.164 AESA E.164 part of E.164 AESA is the 16 digits after AFI (45). E.164 part may include leading zeroes and/or a trailing F. The rest of the number is DSP part. . DCC AESA DCC part of DCC AESA is 4 digit ISO country code after AFI (39). DCC part may include F(s). The rest of the number is DSP part. . ICD AESA ICD part of ICD AESA is 4 digits after AFI (47). ICD part may include F(s). The rest of the number is DSP part. The following changes in the format of numbers must be taken into account when handling analyses: . E.164 ATM format (AFI = 0 x 45) . Zeros between AFI and the following non-zero digit are removed. . The 16th digit of E.164 part (F digit) is removed. . Example: 45000000358951121F --> 45358951121 . DCC ATM format (AFI = 0 x 39) . The fourth digit (F digit) is removed. . Example: 39123F1234 --> 391231234 . ICD ATM format (0 x 47)

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

171 (240)

RNC Integration

.

.

Possible F digits are removed from the ICD part of the number (F digits are removed from digits 1-4). Example: 47123F1234 --> 471231234

Example 1.

Create routing objects and digit analysis for Iur interface

Create an AAL type 2 route between two RNCs. The route number is 13, the protocol is Message Transfer Part Level 3, the signalling network is NA0, the signalling point code is 35, and AAL type 2 node identifier is AAL2HEL1. ZRRC:ROU=13,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=35, ANI=AAL2HEL1;

2.

Create an endpoint group under route 13. The endpoint group ID is automatically selected by the system. The termination points in this group have the Constant Bit Rate service category for both ingress and egress directions. ZLIC:13:C,C;

3.

Check that there is a free VCLtp. ZLCI:5,VC:<VPI>:FREE; Note that you can check all the VPIs available. Out of these VCIs all those with service category CBR in both directions can be used in the next step.

4.

Create an endpoint of VC level (VCCep) under the route 13 created in the first step. AAL type 2 path is 11. The interface ID is 5, VPI 12, and VCI 1045. The current network element owns the AAL type 2 path. The AAL type 2 loss ratio is 10–3 and the AAL type 2 multiplexing delay is 10 ms. ZLJC:VC,13,11:5,12,1045:LOCAL:3,100; The system will automatically sort this endpoint into the endpoint group of step 2 since their service categories match.

172 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iur interface (RNC-RNC)

Note
You must create a corresponding routing structure (steps 1-4) in the remote (PEER) network element before you can proceed to step 5. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if this end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifier must have the same value in both ends of a certain connection. 5. Unblock the AAL type 2 path 11. The ANI is AAL2HEL1 and the allowed waiting time for the execution of the blocking command is 18 seconds. ZLSU:AAL2HEL1:11:18; 6. Create digit analysis without charging for a digit sequence 491234 in analysis tree 24. ZRDC:DIG=491234,TREE=24:ROU=13;

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

173 (240)

RNC Integration

174 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-BC interface (RNC-CBC)

13
13.1

Creating Iu-BC interface (RNC-CBC)
Configuring transmission and transport resources
For information on configuring transmission and transport resources, refer to Configuring transmission and transport interfaces.

13.2

Configuring Iu-BC parameters of RNC
Before you start

The RNC object has to be opened before this procedure can take place.

Note
You can configure Iu-BC parameters only if Service Area Broadcast Protocol (SABP) is in use.

Note
If several operators share an RNC, the number of cell broadcast centres (CBC) that can be configured for the RNC is 4. In case there is only one operator, there is only one CBC.

Note
If the IMSI-based handover is in use, you can configure up to four PLMN IDs per core item.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

175 (240)

RNC Integration

Steps
1. 2. Select the Core Network tab from the RNC dialogue. Fill in and check CBC-related parameters. Fill in and check CBC-related data, that is, IP addresses and Global PLMN IDs. For more information on parameters, see WCDMA RAN Parameter Dictionary.

13.3

Configuring IP for Iu-BC (RNC-CBC)
Purpose

The purpose of this procedure is to configure IP for the Iu-BC interface between the RNC and the Cell Broadcast Centre (CBC). All user data and signalling (SABP) traffic goes through the same Interface Control and Signalling Unit (ICSU). You must configure one VCC and one static route towards the CBC for the selected ICSU. Static routes are needed only in the case when the CBC is not directly connected to the RNC (for example, router is connected between the RNC and the CBC). In case of ICSU switchover, IP over ATM interface, IP address and static routes will move to the new unit.
Before you start

The ATM resources for Iu-BC need to be created before this procedure is commenced. For instructions, see Creating ATM resources in RNC in ATM Resource Management.

Steps
1. Check the selected ICSU unit towards the CBC The RNC allocates the ICSU unit for the CBC when the CBC reference data is created to the RNC configuration. You can check the selected ICSU (logical address for the selected ICSU) from the RNC RNW Object Browser's RNC dialog and core network tab. For further information of the parameter please refer to the WCDMA RAN04 Parameter Dictionary documentation: RNC - CBList CBCItem - ICSUforCBC.

176 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-BC interface (RNC-CBC)

Check the ICSU-id based on the logical address selected towards the CBC. ZUSI:ICSU; 2. Create the IP over ATM interface to selected ICSU Create the IP over ATM interface to selected ICSU towards the CBC according to the instructions in Configuring IP over ATM interfaces. If you want to distribute incoming traffic between several ICSU units, then create as many IP over ATM interfaces as needed (one separate IP over ATM interface for each used ICSU) towards the CBC. In this case, only selected ICSU unit is sending RNC originated Restart and Failure messages towards the CBC. The CBC must be configured to send data to different IP addresses, that is, to different ICSU units. When assigning an IP address to the ICSU unit, assign a logical IP address to the unit by giving value L to the IP address type parameter. If you want to configure several IP over ATM interfaces towards the CBC (distributing incoming traffic between several ICSU units), give the network interface parameter a different value in all units, value L to the IP address type parameter, and assign a different IP address to each unit. The destination IP address is the address of the router interface or the CBC interface which terminates the VCC. 3. Create a static route for Iu-BC For Iu-BC connections towards the CBC, configure one static route with route type "LOG" for selected ICSU to the IP address of the router terminating IP over ATM PVCs. Static routes are needed only in the case when the CBC is not directly connected to the RNC.

Note
Only static routes can be configured for ICSU units. Static routes are only required for ICSUs if any of the IP packets have a different destination address than the IP address of the CBC (for example, if a router is used between the RNC and CBC), and they are to be transferred via the VCC.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

177 (240)

RNC Integration

For IPv4: ZQKC:<unit type>,<unit index>:[<destination IP address>],[<netmask length>]:<gateway IP address>, [<local IP address>]:<route type>;

Note
The parameter local IP address is only valid for the local IP address based default routes. For normal static routes, you do not need to give the local IP address. For more information about local IP address based default routes, refer to Creating and modifying static routes.

For IPv6: ZQ6C:<unit type>,<unit index>:[<destination IP address>],[<prefix length>]:[<next hop type>]: <address type>:(IP=<ip address> | MAC=<link level mac address>); Example Configuring IP for Iu-BC through ICSU units

The following figure shows an example of IP configuration for Iu-BC interface with IPv4 and IPv6 addresses. The ICSU-0 is selected to be used towards the CBC.

178 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-BC interface (RNC-CBC)

RNC site RNC

Core site MGW Router terminating IP over ATM PVCs (can also be an extra ATM Interface) NIS
10.1.1.200

ICSU-0
10.1.1.1

ICSU-1

NIS

NIS

CBC any media

ICSU-2

...
ICSU-18

STM-1

VPI=x VP cross connects

VPI=y

subnet 10.1.1.0/32

Figure 12.

Example of IPv4 configuration for Iu-BC

The following examples show how to configure the IP for the Iu-BC interface between the RNC and the CBC. The ICSU-0 is selected to be used towards the CBC. The Iu-BC PVCs are configured to the STM-1 interface between the RNC and the MGW. The IPoA PVCs are terminated in a router. The PVCs can also be terminated in the CBC, if it is located in the same site. For IPv4 case: 1. 2. Create ATM resources as instructed in Creating ATM resources in RNC in ATM Resource Management. Create IP over ATM interfaces connected to subnetwork 10.1.1.1/32 to selected ICSU. ZQMF:ICSU,0,L:AA1:1,0,40:1,IPOAUD;

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

179 (240)

RNC Integration

Note
Note: The ICSU-0 is selected to be used towards the CBC. 3. Assign an IPV4 address to the selected ICSU. ZQRN:ICSU,0:AA1:10.1.1.1,L:32:10.1.1.200; 4. Create a static route for selected ICSU. With the following default routes, all traffic is forwarded to the router terminating IP over ATM PVCs. ZQKC:ICSU,0::10.1.1.200,:LOG; For IPv6 case: with the same figure, replace the IPv4 address "10.1.1.1" with IPv6 address "3FFE:1200:3012:C020:580:8FFF:FE7A:7BB7" and the IPv4 address "10.1.1.200" with IPv6 address "3FFE:1200:3012: C020:580:8FFF:FE7A:4BB4". 1. 2. Create ATM resources as instructed in Creating ATM resources in RNCin ATM Resource Management. Create IPv6 over ATM interfaces connected to subnetwork to selected ICSU. ZQMF:ICSU,0,L:AA1:1,0,40:1,IPOAUD; Note: The ICSU-0 is selected to be used towards the CBC. 3. Assign an IPv6 address to the selected ICSU. ZQ6N:ICSU,0:AA1:"3FFE:1200:3012:C020:580:8FFF: FE7A:7BB7",L:128:"3FFE:1200:3012:C020:580:8FFF: FE7A:4BB4"; 4. Create a static route for each ICSU. With the following default routes, all traffic is forwarded to the router terminating IP over ATM PVCs. A static route is needed for each ICSU because during the ICSU switchover static route is not switching to the new unit. ZQ6C:ICSU,0::GW:IP="3FFE:1200:3012:C020:580:8FFF: FE7A:4BB4"; ZQ6C:ICSU,1::GW:IP="3FFE:1200:3012:C020:580:8FFF: FE7A:4BB4"; ...

180 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Creating Iu-BC interface (RNC-CBC)

ZQ6C:ICSU,18::GW:IP="3FFE:1200:3012:C020:580:8FFF: FE7A:4BB4";

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

181 (240)

RNC Integration

182 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring radio network objects

14
14.1

Configuring radio network objects
Creating frequency measurement control
Purpose

A new logical frequency measurement control (FMC) object (FMCS, FMCI, FMCG (optional)) is created so that its parameters can be utilised in WCDMA cell definitions.

Steps
1. Select Object → New → Freq. Meas. Control → intra-freq./interfreq./inter-system. Fill in parameters. For information on parameters, see WCDMA RAN Parameter Dictionary. 3. Click OK in the parameter dialogue to confirm the operation.
Expected outcome

2.

The data is sent to the RNC RNW database. An Operation Information dialogue appears indicating the status of the operation and possible errors. 4. Check the outcome of the operation and click OK to close the Operation Information dialogue.
Expected outcome

A new FMC object is created.
Unexpected outcome

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

183 (240)

RNC Integration

Any errors are displayed in the Operation Information dialogue. If the creation fails, you are asked if you want to return to the creation dialogue to modify the parameters and try again. You can also click Cancel to cancel the operation.

14.2

Creating handover path
Purpose

A new logical handover path object (HOPS, HOPI, HOPG (optional)) is created so that its parameters can be utilised in adjacent WCDMA cell definitions.

Steps
1. Select Object → New → Handover Path →intra-freq./inter-freq./ inter-system. Fill in parameters. For information on parameters, see WCDMA RAN Parameter Dictionary. 3. Click OK in the parameter dialogue to confirm the operation.
Expected outcome

2.

The data is sent to the RNC RNW database. An Operation Information dialogue appears indicating the status of the operation and possible errors. 4. Check the outcome of the operation and click OK to close the Operation Information dialogue.
Expected outcome

A new handover path object is created.
Unexpected outcome

Any errors are displayed in the Operation Information dialogue. If the creation fails, you are asked if you want to return to the creation dialogue to modify the parameters and try again. You can also click Cancel to cancel the operation.

184 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring radio network objects

14.3

Creating a WCDMA BTS site
Purpose

A new logical WBTS object is created in order to manage a physical WCDMA BTS (WBTS) site and to increase the system capacity.
Before you start

There are two ways of creating a WCDMA BTS site: one is to use system defaults and the other is to use a reference site. The step-by-step instructions below apply to both kinds of creation procedures. 1. Creating a WCDMA BTS site using system defaults: System defaults refer to a range of predefined values which are used in order to speed up the WBTS creation procedure. You still have to fill in identification information for the WCDMA BTS and other required parameters for which there are no default values. You are not limited to default values; once a parameter has been given a default value, you can change it if necessary. 2. Creating a WCDMA BTS site using a reference site: . To use a reference WCDMA BTS site to aid you in the creation of a WBTS, click the Site References button. A dialogue with a list of existing WCDMA BTS sites will appear. . Select the WCDMA BTS that you want to use from the list. When you use a reference site, all possible parameters are copied from the reference site to the new one. You still have to fill in values for those required parameters which could not be copied from the reference WBTS. You are not limited to the copied values; once a parameter value has been copied from the reference WBTS, you can change it if necessary. When you use a reference WBTS site to set up a new site, the topology of the reference site (WCDMA cells and their parameters) is also copied to the new site as an initial configuration. The new site does not have to have the same number of cells as the reference site, that is, the user may add and delete cells as needed.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

185 (240)

RNC Integration

Note
The logical objects in the RNC RNW database are hierarchically related to each other, and the hierarchy dictates the order in which it is possible to create new objects. WCEL objects are always created under a certain WBTS object, never independently. However, the user does not have to create all WCEL objects that should belong to a WBTS at once; it is possible to change the configuration at a later stage, for example by adding WCEL objects to a WBTS object.

Note
A frequency measurement control (FMC) object has to be created in advance, if WCDMA cells are created in the WBTS creation procedure.

Steps
1. Select Object → New → WCDMA BTS.
Expected outcome

A New WBTS Site dialogue appears. 2. 3. If you want to, select a reference WBTS site. Fill in parameters. For information on parameters, see WCDMA RAN Parameter Dictionary.

Note
Identify the transmission resources by giving the desired COCO identification or the ATM interface/VPI/C-NBAP VCI triplet. If the COCO is found in the system, the WBTS is connected to it during the creation procedure. The COCO can also be created later on. The reference to COCO object can also be left empty. 4.

If you want to add a WCDMA cell Then

186 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring radio network objects

Click Add WCEL. Fill in parameters. For information on parameters, see WCDMA RAN Parameter Dictionary.

Note
If you add WCDMA cells in a locked state, the WCDMA BTS is not taken into active traffic before the WCDMA cell states are changed to an unlocked state. For more information, see Locking and unlocking a WCDMA cell. 5.

If you want to remove a WCDMA cell Then
Select WCEL from the WBTS Site tree. Click Remove WCEL.

6.

Click OK in the parameter dialogue to confirm the operation.
Expected outcome

The data is sent to the RNC RNW database. A Site Creation Confirmation dialogue appears. 7. Check the outcome of the operation and click OK to close the Operation Information dialogue.
Expected outcome

The new WBTS site is created. The WCDMA BTS can be taken into active traffic once it has been successfully connected to the logical COCO object (that is, transmission resources).
Unexpected outcome

If the user gives a reference to a COCO object, the reference should only point to a COCO object which is not in use at the time. In other words, no reference to a COCO object which is already related to a WBTS will be made.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

187 (240)

RNC Integration

Any errors are displayed in the Operation Information dialogue. The parameter window where the error occurred is displayed, and you can either modify the parameters and try again or cancel the operation.

14.4

Creating a WCDMA cell
Purpose

A new WCDMA cell is created in order to change the configuration of the WCDMA BTS (WBTS) site.
Before you start

WCEL objects can only be created under a WBTS. The WCDMA cell remains locked and is not used in active traffic until you have changed its state to unlocked.

Steps
1. Start creating the WCDMA cell. a. Select a parent WCDMA BTS for the WCDMA cell. b. Select Object → New → WCDMA cell.
Or

Alternatively, the WCDMA cell can be created using an existing WCDMA cell as reference. a. Select the WCDMA cell whose parameters should be used in the new cell. b. Select Object → Use as reference. c. Select the WCDMA BTS to which the WCDMA cell should be created. 2. Fill in parameters. a. Browse through the parameter tabs and fill in every mandatory parameter. b. Specify FMCS, FMCI and FMCG for real time, non-real time and HSDPA separately on the HC tab. Note that FMCG can only be defined if the inter-system handover feature is activated and HSDPA FMCs only if the HSDPA feature has been activated.

188 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring radio network objects

For information on parameters, see WCDMA RAN Parameter Dictionary. 3. 4. Click OK in the parameter dialogue to confirm the operation. Select Yes from Automatic Unlock Confirmation dialogue, if you want to create the cell unlocked.
Expected outcome

The data is sent to the RNC RNW database. An Operation Information dialogue appears indicating the status of the operation and possible errors. 5. Check the outcome of the operation and click OK to close the Operation Information dialogue.

Expected outcome

A new WCDMA cell is created.
Unexpected outcome

Any errors are displayed in the Operation Information dialogue. If the creation fails, you are asked if you want to return to the creation dialogue to modify the parameters and try again. You can also click Cancel to cancel the operation.

14.5

Creating an internal adjacency for a WCDMA cell
Purpose

A new logical adjacency object [ADJS/ADJI] for WCDMA cell is created to define a new neighbouring cell. Adjacencies for cells controlled by the same RNC are called internal adjacencies.
Before you start

Note
The ADJG object can only act as an external adjacency.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

189 (240)

RNC Integration

Note
There is a limitation in sending neighbour cell information in system information block (SIB) type 11 and 12. SIB11 and SIB12 messages can contain information on a maximum of 96 cells, but the physical size of SIB data (no more than 3552 bits) has capacity only for 47 cells when all used optional information elements in SIB11 are in use and 35 cells if HCS is used. If the system information data exceeds 3552 bits, the scheduling of the system information blocks fails. The cell is blocked by the system and an alarm 7771 WCDMA CELL OUT OF USE (BCCH scheduling error) is reported for the cell.

Steps
1. 2. Select a parent WCDMA cell for the adjacent WCDMA cell. Select Object → New → Adjacency → intra-freq./inter-freq.
Expected outcome

A New ADJS/ADJI dialogue appears. 3. Fill in parameters.

Steps
a. Select the target WCDMA cell from the Available cells list. Target UTRAN cell identity and other target cell related parameters are automatically defined. You can also insert Target UTRAN Cell identity of the target cell as well as identification parameters for the RNC manually. b. Specify whether the adjacency should be bidirectional or not. The default value is outgoing. The selected WCDMA cell is acting as source cell in case of adjacencies. c. Specify handover paths for real time, non-real time and HSDPA separately.

190 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring radio network objects

Note
HSDPA HOP can be specified only if the HSDPA feature is activated.

d.

Specify whether the adjacency should be included in the system information messages or not. All adjacent cells are used in measurement control even if the adjacency is not included in the system information.

Further information

For more information on parameters, see WCDMA RAN Parameter Dictionary. 4. Click OK in the parameter dialogue to confirm the operation.
Expected outcome

The data is sent to the RNC RNW database. An Operation Information dialogue appears indicating the status of the operation and possible errors. 5. Check the outcome of the operation and click OK to close the Operation Information dialogue.

Expected outcome

If you chose to create a bidirectional adjacency, both an outgoing and an incoming adjacency are created; otherwise only an outgoing adjacency is created.
Unexpected outcome

Any errors are displayed in the Operation Information dialogue. If the creation fails, you are asked if you want to return to the creation dialogue to modify the parameters and try again. You can also click Cancel to cancel the operation.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

191 (240)

RNC Integration

14.6

Creating an external adjacency for a WCDMA cell
Purpose

A new logical adjacency object [ADJS/ADJI/ADJG (optional)] for WCDMA cell is created to define a new neighbouring cell. External adjacencies refer to adjacency relationships between cells controlled by different RNCs.
Before you start

Note
There is a limitation in sending neighbour cell information in system information block (SIB) type 11 and 12. SIB11 and SIB12 messages can contain information on a maximum of 96 cells, but the physical size of SIB data (no more than 3552 bits) has capacity only for 47 cells when all used optional information elements in SIB11 are in use and 35 cells if HCS is used. If the system information data exceeds 3552 bits, the scheduling of the system information blocks fails. The cell is blocked by the system and an alarm 7771 WCDMA CELL OUT OF USE (BCCH scheduling error) is reported for the cell.

Steps
1. 2. Select a parent WCDMA cell for the adjacent WCDMA cell. Select Object → New → Adjacency → intra-freq./inter-freq./ inter-system.
Expected outcome

A New ADJS/ADJI/ADJG (optional) dialogue appears. 3. Fill in parameters.

Steps
a. Insert the Target Cell identity of the target cell as well as identification parameters for the external RNC manually. For external adjacencies, define only the outgoing adjacencies.

b.

192 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Configuring radio network objects

c.

Specify handover paths.

Note
HSDPA HOP can be specified only if the HSDPA feature is activated.

d.

Specify whether the adjacency should be included in the system information messages or not. All adjacent cells are used in measurement control even if the adjacency is not included in the system information.

Further information

For more information on parameters, see WCDMA RAN Parameter Dictionary. 4. Click OK in the parameter dialogue to confirm the operation.
Expected outcome

The data is sent to the RNC RNW database. An Operation Information dialogue appears indicating the status of the operation and possible errors. 5. Check the outcome of the operation and click OK to close the Operation Information dialogue.

Expected outcome

An outgoing adjacency is created.
Unexpected outcome

Any errors are displayed in the Operation Information dialogue. If the creation fails, you are asked if you want to return to the creation dialogue to modify the parameters and try again. You can also click Cancel to cancel the operation.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

193 (240)

RNC Integration

194 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

15
15.1

Integrating location services
Overview of location services
RAN Location Services (LCS) provides the means to identify and report the current location of a UE using geographical co-ordinates. In addition to the RNC-centric cell-based locationing, the Nokia RNC implementation of the location services includes two different interfaces, Iupc and ADIF, to the external LCS server for additional locationing methods. Iupc is a 3GPP standard interface between an RNC and a Standalone Serving Mobile Location Centre (SAS). ADIF is a proprietary interface between an RNC and an A-GPS Server. Iupc data transmission is based on SIGTRAN (M3UA/SCTP), and ADIF data transmission is based on TCP. RNC connectivity is based on Ethernet in both Iupc and ADIF.

Note
Iupc and ADIF are mutually exclusive. Only one of these interfaces may be active at a time.

15.2
15.2.1

Creating TCP/IP configuration in RRMU units
Overview of TCP/IP configuration in RRMU units
Preconditions for TCP/IP configuration in RRMU units

Verify that an optional 'LAN Redundancy for A-GPS and cables' sales item kit has been installed.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

195 (240)

RNC Integration

The following figure shows a simplified example of IP network configuration between an RNC and a redundant A-GPS Server pair.

RRMU 10.10.1.2/24 EL0 EL1 10.10.2.2/24

10.10.1.1/24 Intermediate IP Network 10.10.3.1/24 Primary datapath 10.10.3.2/24 A-GPS Server 1

10.10.2.1/24

10.10.4.1/24 Secondary datapath A-GPS Server 2 10.10.4.2/24

Figure 13.

Example of IP network configuration between an RNC and a redundant A-GPS Server

The following figure shows a simplified example of IP network and signalling configuration between an RNC and a SAS.

RRMU 10.10.1.2/24 EL0 EL1

Network = NA0 SPC = 111 10.10.2.2/24

10.10.1.1/24 Intermediate IP Network 10.10.3.1/24 Primary datapath 10.10.3.2/24 SAS

10.10.2.1/24

10.10.4.1/24 Secondary datapath 10.10.4.2/24 Network = NA0 SPC = 222

Figure 14.

Example of IP network and signalling configuration between an RNC and a SAS

196 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

In Figures Example of IP network configuration between an RNC and a redundant A-GPS Server and Example of IP network and signalling configuration between an RNC and a SAS, the RRMU unit is connected to two different IP subnetworks. The RRMU’s EL0 interface is connected to the 10.10.1.0 /24 subnetwork, and the EL1 interface is connected to the 10.10.2.0 /24 subnetwork. Static IP routes are configured so that there are two different logical datapaths between the RRMU unit and the A-GPS Servers or SAS. The highest possible connection redundancy is achieved when the datapaths are transported through different network paths between the RRMU and the A-GPS Servers or SAS. When the ADIF interface is used, all traffic to the A-GPS Server 1 originates from the RRMU’s EL0 interface, and all traffic to the A-GPS Server 2 originates from the RRMU’s EL1 interface. When the Iupc interface is used, all traffic to the first network interface of the SAS originates from the RRMU’s EL0 interface and all traffic to the second network interface of the SAS originates from the RRMU’s EL1 interface.

15.2.2

Defining IP addresses and IP routes to RRMU units
Before you start

Verify that an optional 'LAN Redundancy for A-GPS and cables' sales item kit has been installed. The following figure shows a simplified example of IP network configuration between an RNC and a redundant A-GPS Server pair.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

197 (240)

RNC Integration

RRMU 10.10.1.2/24 EL0 EL1 10.10.2.2/24

10.10.1.1/24 Intermediate IP Network 10.10.3.1/24 Primary datapath 10.10.3.2/24 A-GPS Server 1

10.10.2.1/24

10.10.4.1/24 Secondary datapath A-GPS Server 2 10.10.4.2/24

Figure 15.

Example of IP network configuration between an RNC and a redundant A-GPS Server

The following figure shows a simplified example of IP network and signalling configuration between an RNC and a SAS.

RRMU 10.10.1.2/24 EL0 EL1

Network = NA0 SPC = 111 10.10.2.2/24

10.10.1.1/24 Intermediate IP Network 10.10.3.1/24 Primary datapath 10.10.3.2/24 SAS

10.10.2.1/24

10.10.4.1/24 Secondary datapath 10.10.4.2/24 Network = NA0 SPC = 222

Figure 16.

Example of IP network and signalling configuration between an RNC and a SAS

198 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

In Figures Example of IP network configuration between an RNC and a redundant A-GPS Server and Example of IP network and signalling configuration between an RNC and a SAS, the RRMU unit is connected to two different IP subnetworks. The RRMU’s EL0 interface is connected to the 10.10.1.0 /24 subnetwork, and the EL1 interface is connected to the 10.10.2.0 /24 subnetwork. Static IP routes are configured so that there are two different logical datapaths between the RRMU unit and the A-GPS Servers or SAS. The highest possible connection redundancy is achieved when the datapaths are transported through different network paths between the RRMU and the A-GPS Servers or SAS. When the ADIF interface is used, all traffic to the A-GPS Server 1 originates from the RRMU’s EL0 interface, and all traffic to the A-GPS Server 2 originates from the RRMU’s EL1 interface. When the Iupc interface is used, all traffic to the first network interface of the SAS originates from the RRMU’s EL0 interface and all traffic to the second network interface of the SAS originates from the RRMU’s EL1 interface. The IP addresses in the following examples are only valid for the configuration examples shown in Figures Example of IP network configuration between RNC and redundant A-GPS Server and Example of IP network and signalling configuration between RNC and SAS. Refer to your IP plans for the correct IP addresses. The basic IP configuration is the same regardless of whether you use the or ADIF or Iupc interface.

Steps
1. Define the IP address to the EL0 interface of the RRMU.
ZQRN:RRMU:EL0:10.10.1.2,L,:24:;

2.

Define the IP address to the EL1 interface of the RRMU.
ZQRN:RRMU:EL1:10.10.2.2,L,:24:;

3.

Define the static destination route to the primary destination.
ZQKC:RRMU,0:10.10.3.0,24:10.10.1.1:LOG:;

4.

Define the static default route to the secondary destination.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

199 (240)

RNC Integration

ZQKC:RRMU,0::10.10.2.1,:LOG:;

15.3
15.3.1

Configuring ESA24 switches
Configuring ESA24-0
Before you start

It is recommended that you configure the ESA24 switches using a serial cable connection instead of telnet connection to avoid the loss of connectivity to the ESA24. It is recommended that the ESA24 operating system (BiNOS) version is 3.14.7 or higher. ESA24-0 is physically located in subrack 1, slot 12 and ESA24-1 is located in subrack 2, slot 6. In the following example, it is assumed that the ETH0 (1/1/1) ports of the ESA24 switches are connected to Cisco Ethernet switches, which support the new standard-compatible implementation of the IEEE 802.1s MSTP protocol and are configured respectively on MSTP and VLAN level. For more information, see Configuring external IP routers and switches for AGPS use in RNC, dn0736868, available in NOLS. The VLAN IDs and names in the following examples apply only to an Ethernet network, which is built for A-GPS LCS use. In other cases, the VLAN IDs and other parameters may overlap with existing parameters and cause Ethernet connectivity problems.

Steps
1. 2. Connect to ESA24-0 using a serial cable. Log in to ESA24-0 using the default password “nokia” or the new password if the password has been changed.
User Access Verification Password:

3.

Switch to privileged mode.
ESA24-0>enable

200 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

ESA24-0#

4.

Switch to configuring mode.
ESA24-0#configure terminal ESA24-0(config)#

5.

Switch to VLAN configuration mode.
ESA24-0(config)#vlan ESA24-0(config vlan)#

6.

Add a new VLAN with the name “LCS1” and id number “10”.
ESA24-0(config vlan)#create LCS1 10

7.

Add a new VLAN with the name “LCS2” and id number “20”.
ESA24-0(config vlan)#create LCS2 20

8.

Add a new VLAN with the name “OAM” and id number “30”.
ESA24-0(config vlan)#create OAM 30

9.

Switch to VLAN “LCS1” configuration mode.
ESA24-0(config vlan)#config LCS1 ESA24-0(config-vlan LCS1)#

10.

Add ports 1/1/1 and 1/1/6 to VLAN “LCS1” in “tagged” mode.
ESA24-0(config-vlan LCS1)#add ports 1/1/1 tagged ESA24-0(config-vlan LCS1)#add ports 1/1/6 tagged

11.

Add ports 1/1/7 and 1/1/8 to VLAN “LCS1” in “untagged” mode and exit.
ESA24-0(config-vlan LCS1)#add ports 1/1/7 untagged ESA24-0(config-vlan LCS1)#add ports 1/1/8 untagged ESA24-0(config-vlan LCS1)#exit

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

201 (240)

RNC Integration

ESA24-0(config vlan)#

12.

Switch to VLAN “LCS2” configuration mode.
ESA24-0(config vlan)#config LCS2 ESA24-0(config-vlan LCS2)#

13.

Add ports 1/1/1 and 1/1/6 to VLAN “LCS2” in “tagged” mode and exit.
ESA24-0(config-vlan LCS2)#add ports 1/1/1 tagged ESA24-0(config-vlan LCS2)#add ports 1/1/6 tagged ESA24-0(config-vlan LCS2)#exit ESA24-0(config vlan)#

14.

Switch to VLAN “OAM” configuration mode.
ESA24-0(config vlan)#config OAM ESA24-0(config-vlan OAM)#

15.

Add ports 1/1/1 and 1/1/6 to VLAN “OAM” in “tagged” mode.
ESA24-0(config-vlan OAM)#add ports 1/1/1 tagged ESA24-0(config-vlan OAM)#add ports 1/1/6 tagged

16.

Add ports 1/1/2, 1/1/3, 1/1/4, and 1/1/5 to VLAN “OAM” in “untagged” mode and exit.
ESA24-0(config-vlan OAM)#add ports 1/1/2 untagged ESA24-0(config-vlan OAM)#add ports 1/1/3 untagged ESA24-0(config-vlan OAM)#add ports 1/1/4 untagged ESA24-0(config-vlan OAM)#add ports 1/1/5 untagged ESA24-0(config-vlan OAM)#exit ESA24-0(config vlan)#exit

202 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

ESA24-0(config)#

17.

Switch to protocol configuration mode.
ESA24-0(config)#protocol ESA24-0(cfg protocol)#

18.

Enable MSTP protocol.
ESA24-0(cfg protocol)#mstp enable

19.

Modify MSTP priority and maximum hop count, then exit.
ESA24-0(cfg protocol)#mstp 0 priority 61440 ESA24-0(cfg protocol)#mstp max-hops 30 ESA24-0(cfg protocol)#

20.

Define name and revision number for the MSTP region and exit.
ESA24-0(cfg protocol)#mstp ESA24-0(cfg protocol mstp)#name lcs ESA24-0(cfg protocol mstp)#revision 1 ESA24-0(cfg protocol mstp)#exit ESA24-0(cfg protocol)#exit ESA24-0(config)#

21.

Switch to interface 1/1/1 configuration mode.
ESA24-0(config)#interface 1/1/1 ESA24-0(config-if 1/1/1)#

22.

Modify interface 1/1/1 MSTP link type, MSTP, and default VLAN, then exit.
ESA24-0(config-if 1/1/1)#mstp link-type point-to-point ESA24-0(config-if 1/1/1)#default vlan 30

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

203 (240)

RNC Integration

ESA24-0(config-if 1/1/1)#exit ESA24-0(config)#

23.

Switch to interface 1/1/2 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-0(config)#interface 1/1/2 ESA24-0(config-if 1/1/2)#mstp edge-port ESA24-0(config-if 1/1/2)#default vlan 30 ESA24-0(config-if 1/1/2)#exit ESA24-0(config)#

24.

Switch to interface 1/1/3 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-0(config)#interface 1/1/3 ESA24-0(config-if 1/1/3)#mstp edge-port ESA24-0(config-if 1/1/3)#default vlan 30 ESA24-0(config-if 1/1/3)#exit ESA24-0(config)#

25.

Switch to interface 1/1/4 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-0(config)#interface 1/1/4 ESA24-0(config-if 1/1/4)#mstp edge-port ESA24-0(config-if 1/1/4)#default vlan 30 ESA24-0(config-if 1/1/4)#exit ESA24-0(config)#

26.

Switch to interface 1/1/5 configuration mode, modify MSTP link type and default VLAN, then exit.

204 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

ESA24-0(config)#interface 1/1/5 ESA24-0(config-if 1/1/5)#mstp edge-port ESA24-0(config-if 1/1/5)#default vlan 30 ESA24-0(config-if 1/1/5)#exit ESA24-0(config)#

27.

Switch to interface 1/1/7 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-0(config)#interface 1/1/7 ESA24-0(config-if 1/1/7)#mstp edge-port ESA24-0(config-if 1/1/7)#default vlan 10 ESA24-0(config-if 1/1/7)#exit ESA24-0(config)#

28.

Switch to interface 1/1/8 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-0(config)#interface 1/1/8 ESA24-0(config-if 1/1/8)#mstp edge-port ESA24-0(config-if 1/1/8)#default vlan 10 ESA24-0(config-if 1/1/8)#exit ESA24-0(config)#

29.

Switch to interface 1/1/6 configuration mode, modify MSTP link type, MSTP path cost, and default VLAN, then exit.
ESA24-0(config)#interface 1/1/6 ESA24-0(config-if 1/1/6)#mstp link-type point-to-point ESA24-0(config-if 1/1/6)#mstp 0 path-cost 400000 ESA24-0(config-if 1/1/6)#default vlan 30

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

205 (240)

RNC Integration

ESA24-0(config-if 1/1/6)#exit ESA24-0(config)#exit ESA24-0#

30.

Write running configuration to NVRAM with command "write".
ESA24-0#write Expected outcome

The system acknowledges that the write was succesful:
Building the configuration ... Configuration is successfully written to NVRAM ESA24-0#

15.3.2

Configuring ESA24-1
Before you start

It is recommended that you configure the ESA24 switches using a serial cable connection instead of telnet connection to avoid the loss of connectivity to the ESA24. It is recommended that the ESA24 operating system (BiNOS) version is 3.14.7 or higher. ESA24-0 is physically located in subrack 1, slot 12 and ESA24-1 is located in subrack 2, slot 6. In the following example, it is assumed that the ETH0 (1/1/1) ports of the ESA24 switches are connected to Cisco Ethernet switches, which support the new standard-compatible implementation of the IEEE 802.1s MSTP protocol and are configured respectively on MSTP and VLAN level. For more information, see Configuring external IP routers and switches for AGPS use in RNC, dn0736868, available in NOLS. The VLAN IDs and names in the following examples apply only to an Ethernet network, which is built for A-GPS LCS use. In other cases, the VLAN IDs and other parameters may overlap with existing parameters and cause Ethernet connectivity problems.

206 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

Steps
1. 2. Connect to the ESA24-1 using a serial cable. Log in to ESA24-1 using the default password “nokia” or the new password if the password has been changed.
User Access Verification Password:

3.

Switch to privileged mode.
ESA24-1>enable ESA24-1#

4.

Switch to configuring mode.
ESA24-1#configure terminal ESA24-1(config)#

5.

Switch to VLAN configuration mode.
ESA24-1(config)#vlan ESA24-1(config vlan)#

6.

Add a new VLAN with the name “LCS1” and id number “10”.
ESA24-1(config vlan)#create LCS1 10

7.

Add a new VLAN with the name “LCS2” and id number “20”.
ESA24-1(config vlan)#create LCS2 20

8.

Add a new VLAN with the name “OAM” and id number “30”.
ESA24-1(config vlan)#create OAM 30

9.

Switch to VLAN “LCS1” configuration mode.
ESA24-1(config vlan)#config LCS1 ESA24-1(config-vlan LCS1)#

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

207 (240)

RNC Integration

10.

Add ports 1/1/1 and 1/1/6 to VLAN “LCS1” in “tagged” mode and exit.
ESA24-1(config-vlan LCS1)#add ports 1/1/1 tagged ESA24-1(config-vlan LCS1)#add ports 1/1/6 tagged ESA24-1(config-vlan LCS1)#exit ESA24-1(config vlan)#

11.

Switch to VLAN “LCS2” configuration mode.
ESA24-1(config vlan)#config LCS2 ESA24-1(config-vlan LCS2)#

12.

Add ports 1/1/1 and 1/1/6 to VLAN “LCS2” in “tagged” mode.
ESA24-1(config-vlan LCS2)#add ports 1/1/1 tagged ESA24-1(config-vlan LCS2)#add ports 1/1/6 tagged

13.

Add ports 1/1/7 and 1/1/8 to VLAN “LCS2” in “untagged” mode and exit.
ESA24-1(config-vlan LCS2)#add ports 1/1/7 untagged ESA24-1(config-vlan LCS2)#add ports 1/1/8 untagged ESA24-1(config-vlan LCS2)#exit ESA24-1(config vlan)#

14.

Switch to VLAN “OAM” configuration mode.
ESA24-1(config vlan)#config OAM ESA24-1(config-vlan OAM)#

15.

Add ports 1/1/1 and 1/1/6 to VLAN “OAM” in “tagged” mode.
ESA24-1(config-vlan OAM)#add ports 1/1/1 tagged ESA24-1(config-vlan OAM)#add ports 1/1/6 tagged

208 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

16.

Add ports 1/1/2, 1/1/3, 1/1/4, and 1/1/5 to VLAN “OAM” in “untagged” mode and exit.
ESA24-1(config-vlan OAM)#add ports 1/1/2 untagged ESA24-1(config-vlan OAM)#add ports 1/1/3 untagged ESA24-1(config-vlan OAM)#add ports 1/1/4 untagged ESA24-1(config-vlan OAM)#add ports 1/1/5 untagged ESA24-1(config-vlan OAM)#exit ESA24-1(config vlan)#exit ESA24-1(config)#

17.

Switch to protocol configuration mode.
ESA24-1(config)#protocol ESA24-1(cfg protocol)#

18.

Enable MSTP protocol.
ESA24-1(cfg protocol)#mstp enable

19.

Modify MSTP priority and maximum hop count, then exit.
ESA24-1(cfg protocol)#mstp 0 priority 61440 ESA24-1(cfg protocol)#mstp max-hops 30 ESA24-1(cfg protocol)#

20.

Define name and revision number for the MSTP region and exit.
ESA24-1(cfg protocol)#mstp ESA24-1(cfg protocol mstp)#name lcs ESA24-1(cfg protocol mstp)#revision 1 ESA24-1(cfg protocol mstp)#exit ESA24-1(cfg protocol)#exit

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

209 (240)

RNC Integration

ESA24-1(config)#

21.

Switch to interface 1/1/1 configuration mode.
ESA24-1(config)#interface 1/1/1 ESA24-1(config-if 1/1/1)#

22.

Modify interface 1/1/1 MSTP link type, MSTP, and default VLAN, then exit.
ESA24-1(config-if 1/1/1)#mstp link-type point-to-point ESA24-1(config-if 1/1/1)#default vlan 30 ESA24-1(config-if 1/1/1)#exit ESA24-1(config)#

23.

Switch to interface 1/1/2 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-1(config)#interface 1/1/2 ESA24-1(config-if 1/1/2)#mstp edge-port ESA24-1(config-if 1/1/2)#default vlan 30 ESA24-1(config-if 1/1/2)#exit ESA24-1(config)#

24.

Switch to interface 1/1/3 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-1(config)#interface 1/1/3 ESA24-1(config-if 1/1/3)#mstp edge-port ESA24-1(config-if 1/1/3)#default vlan 30 ESA24-1(config-if 1/1/3)#exit ESA24-1(config)#

210 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

25.

Switch to interface 1/1/4 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-1(config)#interface 1/1/4 ESA24-1(config-if 1/1/4)#mstp edge-port ESA24-1(config-if 1/1/4)#default vlan 30 ESA24-1(config-if 1/1/4)#exit ESA24-1(config)#

26.

Switch to interface 1/1/5 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-1(config)#interface 1/1/5 ESA24-1(config-if 1/1/5)#mstp edge-port ESA24-1(config-if 1/1/5)#default vlan 30 ESA24-1(config-if 1/1/5)#exit ESA24-1(config)#

27.

Switch to interface 1/1/7 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-1(config)#interface 1/1/7 ESA24-1(config-if 1/1/7)#mstp edge-port ESA24-1(config-if 1/1/7)#default vlan 20 ESA24-1(config-if 1/1/7)#exit ESA24-1(config)#

28.

Switch to interface 1/1/8 configuration mode, modify MSTP link type and default VLAN, then exit.
ESA24-1(config)#interface 1/1/8 ESA24-1(config-if 1/1/8)#mstp edge-port

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

211 (240)

RNC Integration

ESA24-1(config-if 1/1/8)#default vlan 20 ESA24-1(config-if 1/1/8)#exit ESA24-1(config)#

29.

Switch to interface 1/1/6 configuration mode, modify MSTP link type, MSTP path cost, and default VLAN, then exit.
ESA24-1(config)#interface 1/1/6 ESA24-1(config-if 1/1/6)#mstp link-type point-to-point ESA24-1(config-if 1/1/6)#mstp 0 path-cost 400000 ESA24-1(config-if 1/1/6)#default vlan 30 ESA24-1(config-if 1/1/6)#exit ESA24-1(config)#exit ESA24-1#

30.

Write running configuration to NVRAM with command "write".
ESA24-1#write Expected outcome

The system acknowledges that the write was succesful:
Building the configuration ... Configuration is successfully written to NVRAM ESA24-1#

212 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

15.4
15.4.1

Activating location services
Activating the Location Services feature
Summary

Location Services, Iupc interface, and ADIF interface are optional features.

Steps
1. 2. 3. Open the RNC RNW Object Browser application. Select and open the RNC object. For the “LCS functionality” parameter, select value “Enabled” from the drop-down list. Click "OK".

4.

Further information

See Configuring external IP routers and switches for A-GPS use in RNC, dn0736868, available in NOLS.

15.4.2

Activating the ADIF interface
Before you start

The following example is based on the configuration shown in Figure Example of IP network configuration between RNC and redundant A-GPS Server in Overview of TCP/IP configuration in RRMU units. You have to create a WSMLC object in the RNC object before you can configure the ADIF parameters of the WSMLC. For more information on creating a WSMLC object, see Creating WSMLC object.

Steps
1. 2. 3. Open the RNC RNW Object Browser application. In the RNC dialogue box, open the WSMLC tab. For the "UE based AGPS" option, select "Enabled" from the drop-down list.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

213 (240)

RNC Integration

4.

For the "Preferred A-GPS method" option , select "UE Based Method" from the drop-down list. For the "LCS Interface" option, select value "ADIF" from the drop-down list. Under “A-GPS Data Server”, type “10.10.3.2” in the “IP address” field and “43460” in the “Data Port ID” field. Under “Redundant A-GPS Data Server”, type “10.10.4.2” in the “IP address” field and “43460” in the “Data Port ID” field. Click “OK” to save the configuration.

5.

6.

7.

8.

15.4.3

Activating the Iupc interface
Before you start

In the following example, it is assumed that RRMU-0 is in the WO-EX state and that the RNC’s own signalling point and SCCP service have already been configured. The IP addresses, signalling network indicators, and signalling point codes (SPCs) in the following example are only valid for the example configuration shown in Figure Example of IP network and signalling configuration between RNC and SAS in Overview of TCP/IP configuration in RRMU units. Refer to your IP and SS7 network plans of the RNC and the SAS in question for the correct IP addresses, signalling network indicators, and SPCs used in your configuration. Note that the IP and SS7 values are SAS-specific and may need to be changed to inter-operate with a specific SAS.

Steps
1. Create SCTP configuration. a. Create a new SCTP association set.
ZOYC:PCAP:C:;

b.

Add a SCTP association to the SCTP association set.
ZOYA:PCAP: RRMU,0,49152:"10.10.3.2",24:"10.10.4.2",24:SS7:;

c.

Set the value of the traffic mode to override.
ZOYM:PCAP:TRAFFIC=1:;

214 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Integrating location services

d. e. f. g. h.

Enable “ASP messages in IPSP”.
ZOYM:PCAP:IPSP=Y:;

Disable the dynamic routing key registration.
ZOYM:PCAP:REG=N:;

Set the value of the first datastream number as “1”.
ZOYM:PCAP:FIRST=1:;

Set the value of the network appearance as “1”.
ZOYM:PCAP:NETWORK=1:;

Configure the source IP addresses for the SCTP association.
ZOYN:RRMU,0:IPV4:"10.10.1.2","10.10.2.2":;

2.

Create signalling and SCCP configuration. a. Create the IP signalling link set.
ZNSP:NA0,222,PCAP:20:PCAP:;

b. c. d. e. f. g. h. i. j. k. l. m. n.

Create the signalling route set.
ZNRC:NA0,222,PCAP,6,,:,,,0:;

Disable the signalling link test.
ZNST:NA0,222,PCAP:N:;

Create a new SCCP signalling point parameter set.
ZOCC:3,PCAP;

Allow the use of white book management procedures.
ZOCM:3:12,1:;

Allow the use of extended unitdata (XTUD) messages.
ZOCM:3:14,1:;

Allow the connection-oriented segmentation.
ZOCM:3:27,1:;

Create a new SCCP subsystem parameter set.
ZOCA:2,PCAP:;

Enable immediate sending of subsystem state information.
ZOCN:2:14,1;

Allow the activation of the signalling link.
ZNLA:20:;

Activate the signalling link.
ZNLC:20,ACT:;

Allow the activation of the signalling route.
ZNVA:NA0,222;

Activate the signalling route.
ZNVC:NA0,222::ACT;

Add a new subsystem to RNC's own signalling point.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

215 (240)

RNC Integration

ZNFB:NA0,111:F9,PCAP,2,;

o. p.

Add a new subsystem to SAS's signalling point.
ZNFD:NA0,222,3:F9,PCAP,2,;

Allow broadcasting of subsystem states to the local subsystem.
ZOBC:NA0,222,F9:NA0,F9:Y:;

q. r. s. t.

Activate SCCP for RNC’s own signalling point.
ZNGC:NA0,111:ACT;

Activate SCCP for SAS’s signalling point.
ZNGC:NA0,222:ACT;

Activate SCCP subsystem for RNC’s own signalling point.
ZNHC:NA0,111:F9:ACT;

Activate SCCP subsystem for SAS’s signalling point.
ZNHC:NA0,222:F9:ACT;

3.

Activate Iupc application. Note that you have to create a WSMLC object in the RNC object before you can configure the Iupc (SAS) parameters of the WSMLC. For more information on creating a WSMLC object, see Creating WSMLC object. a. Open the RNC RNW Object Browser application. b. In the RNC dialogue box, open the WSMLC tab. c. For the "UE based AGPS" option, select "Enabled" from the drop-down list. d. For the "Network based AGPS" option, select "Enabled" from the drop-down list. e. For the "Preferred A-GPS method" option, select the preferred method from the drop-down list. f. For the "LCS Interface" option, select value "Iupc" from the drop-down list. g. For the “Network indicator for SAS” parameter, select value “NA0” from the drop-down list. h. In the "Signalling Point Code of SAS" field, type the decimal value of SAS's SPC (0x222), "546" i. Click OK to save configuration.

216 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Printing alarms

16
16.1

Printing alarms
Printing alarms using LPD protocol
Before you start

To print out the alarms, you must first configure the LPD printers and define their TCP/IP address.

Steps
1. Check that the needed LPD printers have been created (INI) If the desired LPD can be found from the printout, check that the settings are correct. IP address should be set and the functional state should be NORMAL. If the LPD is not shown in the printout, continue to step 2. If the settings are not correct, continue to step 4. If the settings are correct, continue to step 6.

Note
Check that the index number of the VPP is the same as the index number of the LPD given when configuring the printers. It is recommended to direct the alarms to the VPP devices whose index is less than 50.

ZINI; 2.

If the LPD is not shown in the printout Then

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

217 (240)

RNC Integration

Create the LPD device For instructions, see Creating a printer. 3. Check that the printer state, the LPD index and the IP address are correct (INI) The field FUNCTIONAL STATE in the printout shows the printer state. The printer state in the execution printout should be NORMAL. The LPD index number should be the same as the VPP index number. ZINI; 4.

If the printer state is not NORMAL Then
Change the printer state to NORMAL (INS) ZINS:<device index>:NORMAL;

5.

If the settings are not correct Then
Modify the printer settings (INM) ZINM:<device index>:;

6.

Connect the logical file to the desired I/O device (IIS) After connecting the logical file, the alarms are printed out to the desired I/O device. To print out all the alarms to the desired I/O device, connect the logical file ALARMS to the I/O device. To print out only a certain kind of alarms to the desired I/O device, connect the suitable logical files to the I/O device. For more information on the logical files used with alarms, see Alarm printing and its management. If you are directing the alarms to VPP, pay special attention that the VPP index in the command is the same as the LPD index given when configuring the printers.

218 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Printing alarms

Note
To print out the alarms via LPD, it is recommended to direct the alarms to the VPP devices whose index is less than 50.

ZIIS:,:<logical file name>,:DEV=<current object identification>:DEV=<new object identification>; Example Printing out the alarms to the desired I/O device

In this example, two- and three-star communications alarms are directed to VPP-1. This example assumes that:
.

The printers are configured, The TCP/IP addresses of the printers are configured, and VPP-99 has been connected to logical file ALACOMM1(IIS). Display the printer state and check that the value of the field FUNCTIONAL STATE in the printout is NORMAL. Check that the TCP/IP address is correct. As you want to direct the alarms to VPP-1, check that the index number of LPD is 1. Connect ALACOMM1 to the correct alarm output device. The alarm system writes two- and three-star communications alarms to the logical file ALACOMM1. When giving the command, pay special attention to the correct index number. ZIIS:,:ALACOMM1,:DEV=VPP-99:DEV=VPP-1;

.

.

1. 2. 3. 4.

16.2

Printing alarms via Telnet terminal or Web browser
Purpose

You can display the alarms on a Telnet terminal or in a Web browser. This is a convenient way to continuously monitor alarms on the computer screen over TCP/IP.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

219 (240)

RNC Integration

Before you start

To display the alarms on a Telnet terminal or in a Web browser, you need to be familiar with the logical files used with alarms, and their tasks.

Steps
1. Check that the IP address of the computer unit has been defined (QRI) ZQRI; If the IP connection is not defined, see Creating and modifying IP interfaces. 2. Check that the logical files used in printing out alarms are connected to correct VPP devices (IID) To ensure that all alarms are printed out via a Telnet terminal or a Web browser, check the connection between each of the logical files and the desired VPP device. For more information on logical files, see Alarm printing and its management. ZIID::<logical file name>,:; If all the logical files listed above are connected to at least VPP-99, go to step 4. If the logical files are not connected to VPP-99, VPP-98, VPP-97, VPP-96 or VPP-95, go to step 3.

Note
If all logical files are connected to VPP-99, one remote session for alarm printing can be established. If the logical files are connected to two VPPs, for example, VPP-99 and VPP-98, two simultaneous sessions for alarm printing can be established. VPP-99 serves the first connection that is established and VPP-98 serves the second connection and so on.

3.

Connect the logical files used in printing out alarms to correct VPP devices (IIS)

220 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Printing alarms

If you want to print out all the alarms to the same window, connect VPP-99 to every alarm-related logical file. If you want to print out only certain alarms, for example, two- and three-star alarms, connect the logical files used with these alarms and the correct VPP devices (VPP-99, VPP-98, VPP-97, VPP-96 or VPP-95). Note that a logical file can have a maximum of four targets. If you want to replace the existing I/O device with a new one, use the parameter IND=<current object index>. If this parameter is not given, the new I/O device is simply added but does not replace the previous I/O device. ZIIS::<logical file name>::DEV=VPP-<I/O device index>; ZIIS::<logical file name>:IND=<current object index>:DEV=VPP-<I/O device index>; Note that after connecting the logical files associated with alarms to the correct devices, you do not need to change these connections during the lifetime of the software build. You can print out the alarms as described in step 4. 4. Establish a Telnet or HTTP connection to OMU IP address, port 11111 If you are using a Telnet terminal, press the Enter key once, after you have connected to the correct address and port. If you are using a Web browser, connect to the correct address and port; no extra keystrokes are needed.
Expected outcome

The alarms that occur in the network element from that moment on are displayed on the Telnet terminal or on the Web browser. 5. Check the state of corresponding VPP devices (IHI) The connection for alarm printing is established, if the working state of the VPP devices corresponding to the Telnet or HTTP sessions is WO-EX. The working state of the VPP devices not reserved for any connection is BL-EX.

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

221 (240)

RNC Integration

ZIHI::VPP; In either of the following cases, alarms will not be printed via Telnet/ HTTP: . The VPP device which you connected is not in the WO-EX state. . The connection for alarm printing is not established, or it is disconnected. To re-establish the connection for alarm printing via Telnet or HTTP, start a new connection to OMU, port 11111 from a Telnet terminal or Web browser. 6. End the session when you are ready You can stop the printing of alarms via Telnet or HTTP by closing the Telnet terminal or the Web browser.

222 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Related Topics

Related Topics
Configuring IP for O&M backbone (RNC — NetAct)
Instructions
IP connection configuration for RNC O&M

Creating MMI user profiles and user IDs for remote connections to NetAct
Instructions
Configuring IP for O&M backbone (RNC — NetAct)

Configuring IP stack in OMU
Instructions
Configuring IP for O&M backbone (RNC - NetAct) Creating and modifying DNS configuration Modifying IP parameters Creating and modifying IP interfaces

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

223 (240)

RNC Integration

Creating OSPF configuration for O&M connection to NetAct
Instructions
Configuring IP for O&M backbone (RNC - NetAct) Modifying OSPF configuration

Configuring static routes for the O&M connection to NetAct
Instructions
Configuring IP for O&M backbone (RNC - NetAct) Creating and modifying static routes

Configuring ESA12
Instructions
Configuring IP for O&M backbone (RNC – NetAct)

Configuring ESA24
Instructions
Configuring IP for O&M backbone (RNC — NetAct)

224 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Related Topics

Configuring NEMU for DCN
Instructions
Configuring IP for O&M backbone (RNC-NetAct) NEMU TCP/IP network

Configuring DHCP server in NEMU
Instructions
Configuring NEMU for DCN

Configuring DNS client and server in NEMU
Instructions
Configuring NEMU for DCN

Configuring NEMU to RNC
Instructions
NEMU TCP/IP network Configuring IP for O&M backbone (RNC – NetAct) Configuring NEMU for DCN

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

225 (240)

RNC Integration

Configuring NTP services in NEMU
Instructions
Configuring NEMU for DCN

Descriptions
Time management in NEMU

Configuring IP address for NEMU
Instructions
Configuring NEMU for DCN

Connecting to O&M backbone via Ethernet
Instructions
Configuring IP for O&M backbone (RNC - NetAct)

Configuring IP over ATM interfaces
Instructions
Configuring IP for O&M backbone (RNC - NetAct) Creating and modifying IP over ATM interfaces Creating and modifying IP interfaces

226 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Related Topics

Configuring the RNC object
Instructions
Radio network management Commissioning

Descriptions
Operation and maintenance

Configuring Nokia NetAct interface with NEMU
Instructions
Configuring NEMU system identifier (systemId)

Defining external time source for network element
Instructions
Setting calendar date and time for network element Setting summer time on or off

Descriptions
Time management

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

227 (240)

RNC Integration

Creating local signalling configuration for RNC
Instructions
Creating remote MTP configuration Creating remote SCCP configuration

Configuring PDH for ATM transport
Descriptions
ATM over PDH PDH supervision

Creating IMA group
Descriptions
IMA, Inverse Multiplexing for ATM

Configuring SDH for ATM transport
Descriptions
ATM over SDH

228 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Related Topics

Creating SDH protection group
Descriptions
ATM over SDH

Creating phyTTP
Descriptions
Physical layer Trail Termination Point (phyTTP)

Configuring synchronisation inputs
Instructions
Inspecting synchronisation system Synchronisation fails

Configuring transmission and transport resources
Configuring PDH for ATM transport Creating IMA group Configuring SDH for ATM transport Creating SDH protection group Creating phyTTP Creating ATM resources in RNC

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

229 (240)

RNC Integration

Creating radio network connection configuration
Instructions
Radio network management Modifying radio network connection configuration parameters

Creating ATM termination point for IP over ATM connection
Instructions
Radio network management

Configuring IP for BTS O&M (RNC-BTS/AXC)
Instructions
IP connection configuration for RNC

Configuring transmission and transport resources
Configuring PDH for ATM transport Creating IMA group Configuring SDH for ATM transport Creating SDH protection group Creating phyTTP Creating ATM resources in RNC

230 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Related Topics

Creating remote MTP configuration
Instructions
Creating local signalling configuration for RNC Setting MTP level signalling traffic load sharing Activating MTP configuration

Activating MTP configuration
Instructions
Creating remote MTP configuration

Setting MTP level signalling traffic load sharing
Instructions
Creating remote MTP configuration

Creating remote SCCP configuration
Instructions
Creating local signalling configuration Activating SCCP configuration

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

231 (240)

RNC Integration

Activating SCCP configuration
Instructions
Creating local signalling configuration Creating remote SCCP configuration

Configuring Iu-CS parameters of RNC
Instructions
Radio network management

Descriptions
RNC interfaces Digit analysis and routing in RNC

Creating routing objects and digit analysis for Iu interface in RNC
Descriptions
Analysis and routing objects in ATM network Digit analysis and routing in RNC

Instructions
Creating routing objects and digit analysis for Iur interface in RNC

232 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Related Topics

Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface
Descriptions
Analysis and routing objects in ATM network Digit analysis and routing in RNC

Instructions
Creating routing objects and digit analysis for Iu interface in RNC

Configuring transmission and transport resources
Configuring PDH for ATM transport Creating IMA group Configuring SDH for ATM transport Creating SDH protection group Creating phyTTP Creating ATM resources in RNC

Configuring signalling channels
Instructions

Configuring ATM-based signalling channels
Creating remote MTP configuration

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

233 (240)

RNC Integration

Activating MTP configuration Setting MTP level signalling traffic load sharing Creating remote SCCP configuration Activating SCCP configuration

Configuring IP-based signalling channels

Configuring IP-based signalling channels

Configuring Iu-PS parameters of RNC
Instructions
Radio network management

Descriptions
RNC interfaces

Configuring IP for Iu-PS User Plane (RNC-SGSN)
Instructions
IP configuration for Iu-PS interface

Configuring transmission and transport resources
Configuring PDH for ATM transport

234 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Related Topics

Creating IMA group Configuring SDH for ATM transport Creating SDH protection group Creating phyTTP Creating ATM resources in RNC

Configuring signalling channels
Instructions

Configuring ATM-based signalling channels
Creating remote MTP configuration Activating MTP configuration Setting MTP level signalling traffic load sharing Creating remote SCCP configuration Activating SCCP configuration

Configuring IP-based signalling channels

Configuring IP-based signalling channels

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

235 (240)

RNC Integration

Configuring Iur parameters of RNC
Instructions
Radio network management

Descriptions
RNC interfaces Digit analysis and routing in RNC

Creating routing objects and digit analysis for Iur interface in RNC
Descriptions
Analysis and routing objects in ATM network Digit analysis and routing in RNC

Instructions
Creating routing objects and digit analysis for Iu interface in RNC

Configuring transmission and transport resources
Configuring PDH for ATM transport Creating IMA group Configuring SDH for ATM transport Creating SDH protection group

236 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Related Topics

Creating phyTTP Creating ATM resources in RNC

Configuring Iu-BC parameters of RNC
Instructions
Radio network management

Descriptions
RNC interfaces

Configuring IP for Iu-BC (RNC-CBC)
Descriptions
IP configuration for Iu-BC interface

Creating frequency measurement control
Instructions
Radio network management Modifying frequency measurement control parameters

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

237 (240)

RNC Integration

Creating handover path
Instructions
Radio network management Modifying handover path parameters

Creating a WCDMA BTS site
Instructions
Radio network management Creating a WCDMA cell Locking and unlocking a WCDMA cell Modifying WCDMA BTS parameters Deleting radio network managed objects

Creating a WCDMA cell
Instructions
Radio network management Modifying WCDMA cell parameters Creating an internal adjacency for a WCDMA cell Creating an external adjacency for a WCDMA cell

238 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Related Topics

Creating an internal adjacency for a WCDMA cell
Instructions
Radio network management Creating a WCDMA cell Creating an external adjacency for a WCDMA cell Modifying WCDMA cell adjacencies

Creating an external adjacency for a WCDMA cell
Instructions
Radio network management Creating a WCDMA cell Creating an internal adjacency for a WCDMA cell Modifying WCDMA cell adjacencies

Overview of location services
Instructions
Activating the Location Services feature Activating the ADIF interface Activating the Iupc interface

DN03471554 Issue 9-0 en

# Nokia Siemens Networks

239 (240)

RNC Integration

Overview of TCP/IP configuration in RRMU units
Instructions
Defining IP addresses and IP routes to RRMU units

Defining IP addresses and IP routes to RRMU units
Descriptions
Overview of TCP/IP configuration in RRMU units

240 (240)

# Nokia Siemens Networks

DN03471554 Issue 9-0 en

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close