Nokia RNC Integration

RNC Integration

DN03471554Issue 9-0 en

# Nokia Siemens Networks 1 (240)

Nokia WCDMA RNC, Rel. RN2.2, ProductDocumentation, v. 3

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia 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 DN03471554Issue 9-0 en

RNC Integration

Contents

Contents 3

1 Documentation changes in RNC Integration 71.1 Changes between issues 8-0 and 9-0 71.2 Changes between issues 7 and 8-0 81.3 Changes in issue 7 10

2 Integration overview 15

3 Configuring IP for O&M backbone (RNC - NetAct) 213.1 Configuring IP for O&M backbone (RNC — NetAct) 213.2 Creating MMI user profiles and user IDs for remote connections to

NetAct 233.3 Configuring IP stack in OMU 253.4 Configuring IP routing 283.4.1 Creating OSPF configuration for O&M connection to NetAct 283.4.2 Configuring static routes for the O&M connection to NetAct 333.5 Configuring LAN switch 353.5.1 Configuring ESA12 353.5.2 Configuring ESA24 383.6 Configuring NEMU for DCN 413.6.1 Configuring NEMU for DCN 413.6.2 Configuring DHCP server in NEMU 423.6.3 Configuring DNS client and server in NEMU 443.6.4 Configuring NEMU to RNC 483.6.5 NemuRegEdit 503.6.6 NemuRUIMConfiguration 553.6.7 Configuring NTP services in NEMU 603.6.8 Finalising SQL server configuration 643.6.9 Configuring IP address for NEMU 663.7 Configuring external IP connections 683.7.1 Connecting to O&M backbone via Ethernet 683.7.2 Configuring IP over ATM interfaces 69

4 Integrating NEMU 714.1 Configuring NEMU system identifier (systemId) 714.2 Configuring the RNC object 724.3 Configuring Nokia NetAct interface with NEMU 73

5 Configuring heartbeat interval for RNC 77

6 Configuring RNC level parameters 796.1 Defining external time source for network element 796.2 Creating local signalling configuration for RNC 80

7 Configuring transmission and transport interfaces 857.1 Configuring PDH for ATM transport 857.2 Creating IMA group 88



Contents

7.3 Configuring SDH for ATM transport 907.4 Creating SDH protection group 927.5 Creating phyTTP 947.6 Creating ATM resources in RNC 97

8 Configuring synchronisation inputs 105

9 Creating Iub interface (RNC-BTS) 1119.1 Configuring transmission and transport resources 1119.2 Creating radio network connection configuration 1119.3 Creating ATM termination point for IP over ATM connection 1139.4 Configuring IP for BTS O&M (RNC-BTS/AXC) 115

10 Creating Iu-CS interface (RNC-MGW) 12110.1 Configuring transmission and transport resources 12110.2 Configuring ATM-based signalling channels 12110.2.1 Creating remote MTP configuration 12110.2.2 Activating MTP configuration 12610.2.3 Setting MTP level signalling traffic load sharing 12810.2.4 Creating remote SCCP configuration 12910.2.5 Activating SCCP configuration 13310.3 Configuring IP-based signalling channels 13410.4 Configuring Iu-CS parameters of RNC 13810.5 Creating routing objects and digit analysis for Iu interface in RNC 14010.6 Creating routing objects and digit analysis with subdestinations and

routing policy for Iu interface 145

11 Creating Iu-PS interface (RNC-SGSN) 15311.1 Configuring transmission and transport resources 15311.2 Configuring signalling channels 15311.3 Configuring Iu-PS parameters of RNC 15311.4 Configuring IP for Iu-PS User Plane (RNC-SGSN) 154

12 Creating Iur interface (RNC-RNC) 16712.1 Configuring transmission and transport resources 16712.2 Configuring signalling channels 16712.3 Configuring Iur parameters of RNC 16712.4 Creating routing objects and digit analysis for Iur interface in RNC 168

13 Creating Iu-BC interface (RNC-CBC) 17513.1 Configuring transmission and transport resources 17513.2 Configuring Iu-BC parameters of RNC 17513.3 Configuring IP for Iu-BC (RNC-CBC) 176

14 Configuring radio network objects 18314.1 Creating frequency measurement control 18314.2 Creating handover path 18414.3 Creating a WCDMA BTS site 18514.4 Creating a WCDMA cell 18814.5 Creating an internal adjacency for a WCDMA cell 18914.6 Creating an external adjacency for a WCDMA cell 192


RNC Integration

15 Integrating location services 19515.1 Overview of location services 19515.2 Creating TCP/IP configuration in RRMU units 19515.2.1 Overview of TCP/IP configuration in RRMU units 19515.2.2 Defining IP addresses and IP routes to RRMU units 19715.3 Configuring ESA24 switches 20015.3.1 Configuring ESA24-0 20015.3.2 Configuring ESA24-1 20615.4 Activating location services 21315.4.1 Activating the Location Services feature 21315.4.2 Activating the ADIF interface 21315.4.3 Activating the Iupc interface 214

16 Printing alarms 21716.1 Printing alarms using LPD protocol 21716.2 Printing alarms via Telnet terminal or Web browser 219

Related Topics 223



Contents


RNC Integration

1 Documentation changes in RNCIntegration

1.1 Changes between issues 8-0 and 9-0

Modified chapters

Table 1. Modified chapters

Title of the modifiedchapter

Description of thechange

See

Configuring IP stack inOMU

A paragraph about IP layerconfiguration added beforethe step text. A link to ATMand IP plan interfacesadded.

Configuring IP stack inOMU

Configuring static routesfor the O&M connection toNetAct

A paragraph about staticroute configuration addedbefore the step text. A linkto ATM and IP planinterfaces added.

Configuring static routes forthe O&M connection toNetAct

Creating ATM resources inRNC

Note text on using theObject Browser or NetActedited and replaced bynormal text. A link to ATMand IP plan interfacesadded.

Creating ATM resources inRNC

Creating ATM terminationpoint for IP over ATMconnection

A paragraph added toPurpose. A link to ATM andIP plan interfaces added.

Creating ATM terminationpoint for IP over ATMconnection

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

A paragraph about IP overATM connectionconfiguration added beforethe steps. A link to ATMand IP plan interfacesadded.

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



Documentation changes in RNC Integration

Table 1. Modified chapters (cont.)


Description of thechange

See

Configuring IP-basedsignalling channels

A paragraph about IP overATM connectionconfiguration added beforethe steps. A link to ATMand IP plan interfacesadded.


Configuring IP for lu-PSUser Plane (RNC-SGSN)

A paragraph about lu-PSinterface ATM and IP basicresources configurationadded before the steps. Alink to ATM and IP planinterfaces added.

Configuring IP for lu-PSUser Plane (RNC-SGSN)

Activating the locationservices feature

A document reference toNOLS added.

Activating the locationservices feature

1.2 Changes between issues 7 and 8-0

New chapters

Table 2. New chapters

Title of the newchapter

Description of the change See

NemuRUIMConfiguration In this release, RNC supports theRemote User InformationManagement (RUIM) feature. Thissections provides instructions forconfiguring NEMU when the RUIMfeature is used.

NemuRUIMConfiguration


RNC Integration

Modified chapters




NemuRegEdit Registration Account user namecorrected.

NEMUFTP user name corrected.

NemuRegEdit

Creating routing objectsand digit analysis withsubdestinations androuting policy for Iuinterface

It has been mentioned thatalternative routing is the defaultrouting policy and if alternativerouting is used for the subdestination,new subdestination type andpercentages should not be defined.

Creating routing objects and digitanalysis with subdestinations androuting policy for Iu interface

Configuring NEMU forDCN

Steps for configuring the RUIMfeature in NEMU and finalising theSQL server configuration have beenadded.

Configuring NEMU for DCN

Configuring NEMU to RNC The NEMU registry variables usedwhen configuring NEMU for RNCconnection have been added.

Information on the user accounts thatmust be created in NEMU has beenadded.

Configuring NEMU to RNC

Configuring IP for O&Mbackbone (RNC-NetAct)

The note about improving theredundancy of the RNC Ethernetnetwork by installing a redundantESA24 has been removed.

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

Configuring IP for Iu-PSUser Plane (RNC – SGSN)

Instructions for creating UMTS trafficclassification mapping configuration(GTPU) have been added.

Configuring IP for Iu-PS UserPlane (RNC – SGSN)

Overview of TCP/IPconfiguration in RRMUunits

Sales item kit information updated. Overview of TCP/IP configurationin RRMU units

Configuring ESA24-0 BiNOS version updated.

Information about the standard-compatible implementation of theIEEE 802.1s MSTP protocol updated.

Configuration instructions updated.

Configuring ESA24-0

Configuring ESA24-1 BiNOS version updated.

Information about the standard-compatible implementation of theIEEE 802.1s MSTP protocol updated.

Configuration instructions updated.

Configuring ESA24-1







Activating the ADIFinterface

ADIF activation instructions updated. Activating the ADIF interface

Activating the Iu-PCinterface

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. New chapters


Description the change See

Creating routing objectsand digit analysis withsubdestinations androuting policy for Iuinterface

In this release, alternative routing canbe used in the Iu-CS interface if theconnection to the primary direction isbroken or the subdestination selectedbefore is congested.

Creating routing objects and digitanalysis with subdestinations androuting policy for Iu interface


In this release, SS7 signalling overIP is supported in the Iu-PS, Iu-CS,and Iur interfaces.

Configuring IP-based signallingchannels


RNC Integration

Table 4. New chapters (cont.)


Description the change See

Integrating locationservices

In this release, the Nokia RNCimplementation of the locationservices includes two differentinterfaces, Iu-PC and ADIF, to theexternal LCS server for additionallocationing methods.

Overview of location services

Overview of TCP/IP configurationin RRMU units

Defining IP addresses and IProutes to RRMU units

Configuring ESA24-0

Configuring ESA24-1

Activating the Location Servicesfeature

Activating the ADIF interface

Activating the Iu-PC interface

Configuring IP addresses to OMUunits

Overview of O&M IP networkconfiguration

Configuring OSPF routing to OMUunits

Modified chapters




Integration Iu-PC and ADIF interface informationhas been added.

Integration overview

NEMURegEdit Release upgrade related note aboutproviding the RNC baseID, typeID,and OMU IP address forNemuRegEdit has been removed asthis information is no longer requiredin RN2.1 to RN2.2 upgrade.

NEMURegEdit

Configuring IP for O&Mbackbone (RNC - NetAct)

A note about improving theredundancy of the Ethernet networkhas been added.

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

Configuring static routesfor O&M connection toNetAct

The syntax of the QKC command hasbeen changed. This change is relatedto Multiple Default Route/IP routing(OSPFv2 in Chorus).

Configuring static routes for O&Mconnection to NetAct







Configuring ESA24 More information has been added tothe step for configuring RSTP andMSTP.

Configuring ESA24

Configuring DNS client andserver in NEMU

DNS query has been removed fromapplication launcher; therefore,references to DNS query have beenremoved from this chapter.

Configuring DNS client and serverin NEMU

Finalising SQL serverconfiguration

A screenshot has been added. Finalising SQL serverconfiguration

Configuring IP for BTSO&M (RNC – BTS/AXC)


In this release, FlexiBTSs aresupported. Therefore, two notes aboutthe IP and ATM configurations ofFlexiBTS have been added.

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

Creating remote MTPconfiguration

The syntax of the NRC command hasbeen corrected.

In RN2.2, SIGTRAN can be used asan alternative to the ATM-basedMTP3 in the Iu-PS, Iur, and Iu-CSinterfaces. Information about SS7over IP has been added to thischapter.

Creating remote MTPconfiguration

Configuring IP for Iu-PSUser Plane (RNC – SGSN)


Configuring IP for Iu-PS UserPlane (RNC – SGSN)

Configuring IP for Iu-BC(RNC – CBC)


Configuring IP for Iu-BC (RNC –CBC)

Creating frequencymeasurement control

First step on creating frequencymeasurement control has beenmodified.

Creating frequency measurementcontrol

Creating handover path First step on creating handover pathhas been modified.

Creating handover path

Creating a WCDMA BTSsite

A step on Site Creation Confirmationhas been deleted.

Creating a WCDMA BTS site

Creating a WCDMA cell A step on creating the cell unlockedhas been added to WCDMA cellcreation.

Creating a WCDMA cell


RNC Integration




Creating an externaladjacency for a WCDMAcell

The internal adjacency creation step2 has been modified.

Creating an external adjacency fora WCDMA cell





RNC Integration

2 Integration overview

You can start the integration of a network element after the networkelement has been successfully installed and commissioned. During thecommissioning phase, the network elements have been configured andtested as stand-alone entities. During the integration phase theinterconnections between the network elements are configured and theirparameters are customised. After successful integration the networkelement is ready for commercial use.

Note

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


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 userIDs 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) fordata communication network (DCN)

g. configuring external IP connections

2. integrating NEMU




a. configuring network element system identifier (systemId) toNEMU

b. configuring the RNC object

c. configuring Nokia NetAct interface with NEMU

3. configuring heartbeat interval for RNC

4. configuring RNC level parameters

a. defining external time source for network element

b. creating local signalling configuration for RNC

5. configuring transmission and transport interfaces

a. configuring plesiochronous digital hierarchy (PDH) forasynchronous transfer mode (ATM) transport

b. creating inverse multiplexing for ATM (IMA) group

c. configuring synchronous digital hierarchy (SDH) for ATMtransport

d. creating SDH protection group

e. creating physical layer trail termination point (phyTTP)

f. creating ATM resources in RNC

6. configuring synchronisation inputs

7. 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))

8. 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 inRNC

f. creating routing objects and digit analysis with subdestinationsand routing policy for Iu interface

9. creating Iu-PS interface (RNC-serving GPRS support node (SGSN))

a. configuring transmission and transport resources




RNC Integration

d. configuring Iu-PS parameters of RNC

e. configuring IP for Iu-PS User Plane (RNC-SGSN)

10. creating Iur interface (RNC-RNC)




d. configuring Iur parameters of RNC

e. creating routing objects and digit analysis for lur interface inRNC

11. creating Iu-BC interface (RNC-cell broadcast centre (CBC))


b. configuring Iu-BC parameters of RNC

c. configuring IP for Iu-BC (RNC-CBC)

12. 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

13. 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

14. printing alarms

a. printing alarms using LPD protocol

b. printing alarms via a Telnet terminal or a web browser

Example network

The integration instructions are based on the following third generationexample network:




Figure 1. Example network and logical interfaces between network elements

The logical interfaces for the RNC in the 3rd generation network arepresented in the following list.

Iu-CS logical interface between the RNC and the corenetwork. The Iu interface provides signalling meansto establish, maintain and release links and recoverfault situations and generic bearer services over itsuser plane.

Iu-PS logical interface between the RNC and the SGSN

Iur logical interface for the interconnection of two RNCcomponents of the UMTS terrestrial radio accessnetwork (UTRAN) system

Iub logical interface between the RNC and the WBTS

RNC

RNC

MultimediaGateway Rel. 4

SGSN

Iu-PSIur

Iub

Iub

Iu-CS

NetAct

BTS

BTS

Iu-BC

CBC

MSC Server

A-GPSServer

SAS

Iu-PC

ADIF


RNC Integration

Iu-BC logical interface between the RNC and the cellbroadcast centre (CBC)

ADIF Logical interface between the RNC and the A-GPSServer

Iupc Logical interface between the RNC and the Stand-alone SMLC

Required integration planning information

The network planning process delivers all required information for networkelement installation, commissioning and integration. Network planning canbe divided into the following phases: transmission & transport and radionetwork planning.

The following planning activities must be accomplished before theintegration phase starts:

1. radio network planning

2. transport/transmission network planning (in Nokia terminology,transmission is related to the PDH/SDH network and transport to theATM/AAL2 network).

3. IP network planning





RNC Integration

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

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

Purpose

This chapter shows the procedure to configure the Network ElementManagement Unit (NEMU), ESA12/ESA24 Ethernet switch and theOperation and Maintenance Unit (OMU) for the data communicationnetwork (DCN). After this, you can use the Element Manager to managethe RNC remotely.

The O&M backbone can be configured either via Ethernet or via ATMvirtual 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 isalso required. Usually, this interface is Iu-CS.



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

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 toNetAct

See Creating MMI user profiles and user IDs for remote connectionsto 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&Mconnection to NetAct.

192.168.1.5/28

192.168.1.1/28 (logical)

RNC

OMU

192.168.1.10/28

ComputerwithElement Manager

RNC LAN192.168.1.0/28

NEMUESA12/ESA24192.168.1.9/28


RNC Integration

. by configuring static routes

See instructions in Configuring static routes for O&Mconnection to NetAct.

4. Configure the Ethernet/LAN switch

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

5. Configure NEMU

Configure NEMU according to instructions in Configuring NEMU forDCN.

6. Configure external IP connections

Configure the connection to NetAct for O&M traffic. There are twoways to connect the RNC to NetAct:. by configuring the O&M backbone via Ethernet

Refer to instructions in Connecting to O&M backbone viaEthernet.

. 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&Mconnections can be configured to use both ways, if OSPF is used forrouting.

3.2 Creating MMI user profiles and user IDs for remoteconnections to NetAct

Purpose

To enable remote connections from the NetAct to the RNC, you need tocreate users NUPADM and NEMUAD and their profiles in the RNC. NetActapplication (service user management) accesses RNC with NUPADMprofile. NUPADM profile is mandatory to create other service users inNetAct application. NEMUAD profile is created to enable communicationbetween NEMU and OMU. For example, without NEMUAD profile, PMdata cannot be transferred to NEMU and therefore affects the transfermeasurement to NetAct.




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 addressis 192.168.1.1):

telnet <IP address of OMU>

2. Create new MMI user profiles

Create the user profiles for NUPADM and NEMUAD. Refer toCreating MMI user profiles in Information Security for details.

3. Create new MMI user IDs

Create the NUPADM and NEMUAD user IDs. Refer to Creating MMIuser 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 MMIprofiles 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 apassword. The password created here is used for communicationbetween the NEMU or the NetAct and the RNC. The system displaysthe following output:


RNC Integration

/* 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 communicationnetwork (DCN).

Before you start

Note

In addition to the MML based configuration the IP layer can beconfigured via the IP plan interface from the NetAct. The IP plansupport does not contain the OSPF configuration. For further details onthe IP plan interface see IP plan interface in document RNC Operationand Maintenance.

A telnet connection to RNC OMU must be open.

For IPv4:

You can use the QRJ, QRH, QRI, and QRS commands to interrogate theconfiguration.

For IPv6:

You can use the Q6J, Q6H, Q6I, and Q6S commands to interrogate theconfiguration.

Steps

1. Configure DNS parameter data

Define whether or not the DNS service is utilised in IP data transfer.




For IPv4:

ZQRK:[<primary DNS server>],[<secondary DNSserver>],[<third DNS server>],[<local domain name>],[<sortlist>],[<netmask>]:[<resolver cache>],[<round robin>];

For IPv6:

ZQ6K:[<primary DNS server>],[<secondary DNSserver>],[<third DNS server>],[<local domain name>],[<network sortlist>],[<prefix length>]:[<resolvercache>],[<round robin>];

2. Modify TCP/IP parameters

Set host names, define if the OMU forwards IP packets, set themaximum time-to-live value and define if the subnets are consideredto be local addresses in both OMU units.

For IPv4:

ZQRT:<unit type>, <unit index>:(HOST=<host name>,[IPF=<IP forwarding>],[TTL=<IP TTL>],[SNL=<subnetsare local>]);

For IPv6:

ZQ6T:<unit type>,<unit index>:([IPF=<IPforwarding>],[HLIM=<hoplimit>],[RADV=<routeradvertisement>]);

3. Add a new logical IP address

Assign the IP address to both OMU units by QRN for IPv4 and Q6Nfor IPv6.

ZQRN:OMU:<interface name>,[<point to point interfacetype>]:[<IP address>],[<IP address type> ]:[<netmasklength>]:[<destination IP address>]:[<MTU>]:[<state>];

ZQ6N:OMU,<unit index>:<interface name>:[<IPaddress>],[<address type>]:[<prefix length>]:[<destination IP address>];


RNC Integration

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&Mconnection to NetAct.

. by configuring static routes

Refer to instructions in Configuring static routes for O&Mconnection to NetAct.

5. Remove the preconfigured IP address

Remove the preconfigured IP address from both OMU units by QRNcommand for IPv4, by Q6G command for IPv6.

ZQRN:OMU:<interface name...>,:<IP address>,,DEL;

ZQ6G:OMU,<unit index>:<interface name>:<IPaddress>:;

Note

If the unit index for 2N type logical IP address is specified, the logicaladdresses 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 primaryDNS 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 hostname to OMU, set IP forwarding on, and specify that subnets are notlocal.

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. Theinterface name is EL0 and the netmask is length 28.




ZQRN:OMU:EL0:10.1.1.2,L:28:::UP;

4. Configure IPv4 routing. For examples, see Creating OSPFconfiguration for O&M connection to NetAct and Configuring staticroutes for O&M connection to NetAct.

5. Remove the preconfigured IPv4 address (198.168.1.1) from bothOMU units.

ZQRN:OMU:EL0:192.168.1.1,,DEL;

Example Configuring IPv6 stack in OMU

This example shows how to configure the IPv6 stack in OMU for DCN.

1. Configure DNS parameter data. The IPv6 address of the primaryDNS 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 hostname to OMU, set IP forwarding on, set hoplimit value as 70, and setrouter 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 thenetmask 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 OMUunits.

ZQ6G:OMU,0:EL0:"3FEE::1":;

3.4 Configuring IP routing

3.4.1 Creating OSPF configuration for O&M connection to NetAct

Purpose

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


RNC Integration

Before you start

If O&M connections towards NetAct use also backup connection via ATMvirtual connection, the IP over ATM interface for OMU must be createdbefore OSPF is configured. Refer to instructions in Configuring IP overATM interfaces.

You must remove the existing default routes before creating the OSPFconfiguration. If the default routes are not removed, the RNC mightadvertise itself, incorrectly, as an alternative default route to other routers.For instructions on how to remove default routes, see Configuring staticroutes for O&M connection to NetAct.

Steps

1. Configure OSPF router parameters (QKS)

If only logical IP addresses are configured for the OMUs, the samerouter ID can be configured to both OMUs. If the OMU units havephysical IP addresses in addition to a logical IP address, the OMUunits must have different router IDs. In this case, give the physicaladdress of the OMU unit as the value for the router ID parameter toavoid 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) parametersof an OSPF router.

ZQKE:<unit type>,<unit index>:<areaidentification>:<stub area>,[<stub area routecost>],<totally stubby area>;

The area identification specifies the area ID for a new OSPF. Thearea ID is entered as a dotted-quad. The area ID of 0.0.0.0 isreserved for the backbone. The IP network number of a subnettednetwork may be used as the area ID.

Note

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




3. Interrogate IP interfaces (QRI)

You must know the “interface identification” of the network interfaceswhen you are configuring OSPF interfaces.

ZQRI:<unit type>,<unit index>:<interface name>;

If you do not give any parameter values, network interfaceinformation of all computer units of the network element is listed.

4. Configure OSPF interfaces (QKF)

ZQKF:<unit type>,<unit index> :<interfacespecification>:<area identification>:[<hellointerval>]:[<router dead interval>]:[<ospf cost>]:<[election priority>]:[<passive>]:[<authentication>| <password>];

5. Configure redistribute parameters (QKU)

ZQKU:<unit type>,<unit index>:<redistribute type andidentification>:<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 routinginformation exchange between different areas.

ZQKH:<unit type>,<unit index>:<areaidentification>:ADD:<network prefix>:<networkprefix 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 connectionto the backbone area, use a virtual link to provide a logical path fromthe disconnected area to the backbone area. Virtual links have to beconfigured to both ends of the link. The QKV command has to beentered separately for both border routers using the virtual link.

ZQKV:<unit type>,<unit index>:<routeridentification>:<transit area>:<hello interval>:<router dead interval>:<authentication>;

Example Creating OSPF configuration for O&M DCN


RNC Integration

The following example illustrates OSPF configuration for O&M DCN. Thecorresponding IP network interfaces have been configured before thisprocedure.

Figure 3. Example of OSPF configuration for RNC

10.1.1.5/28

10.1.1.2/28 (logical)

RNC

10.1.1.10/28

ComputerwithElement Manager

10.1.1.2/32

unnumbered lines

RAN BTS sitesaddress range

10.1.3.0

10.1.1.1/28

10.3.1.1/24

IP over ATMvirtualconnection

MGW

AA0 10.3.1.2/32

O&Mbackbone

RAN O&M backbone address range10.0.0.0/14OSPF Area 0

NetAct

10.1.1.2/32

RAN BTS sitesaddress range10.1.2.0

RNC LAN10.1.1.0/28

OMU

10.3.2.1/24

AA255 10.3.2.2/32

ESA12/ESA2410.1.1.9/28

NEMU




This example presents the configuration of OSPF parameters in the OMUunit. 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 areathrough an Ethernet connection. The AA0 and AA255 interfaces areattached 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 ID10.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 ADM IF ADDR

UNIT NAME STATE MTU TYPE TYPE IP ADDRESS

------- ------ ----- ----- ---- ---- -------------

OMU-0 AA0 UP 1500 L 10.3.1.2/32

->10.3.1.1

AA255 UP 1500 L 10.3.2.2/32

->10.3.2.1


RNC Integration

EL0 UP 1500 L 10.1.1.2/28

OMU-1 AA0 UP 1500 L (10.3.1.2)/32

->10.3.1.1

AA255 UP 1500 L (10.3.2.2)/32

->10.3.2.1

EL0 UP 1500 L (10.1.1.2)/28

6. Configure OSPF interfaces.

Configure an OSPF interface for the EL0, AA0, and AA255interfaces.

The EL0 interface is attached to the backbone area through anEthernet connection. Accept default values for the hello intervaland router dead interval parameters and set the ospf cost to10.

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 areathrough an IPoA connection. Set the hello interval to 30, routerdead 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, seeCreating OSPF configuration for O&M connection to NetAct) does notprovide any useful functionality over the static routes. In other words, theyare used when a simple static route works as efficient as a morecomplicated dynamic routing. Static routes can be used with dynamicrouting when creating a host route to a host that does not run dynamicrouting.




Static routes are not used for the IP over ATM connections towardsNetAct. Configure OSPF to OMU for both connections towards the NetActrouter. For instructions, see Creating OSPF configuration for O&Mconnection 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 itfollows the logical address if a switchover occurs.

The static route configuration can be done via the IP plan interface fromthe NetAct. For further details on the IP plan interface see IP planinterface 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 defaultroute.

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 baseddefault route. For normal static routes, you do not need to give the localIP address. For more information about local IP address based defaultroutes, refer to Creating and modifying static routes.

2. If the default route cannot be used

Then


RNC Integration

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 itsidentification.

ZQKA:<route number>;

ZQKA::<unit type>,<unit index>;

3. If the default route cannot be used and you deleted it, or if you needto 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 IPaddress>,[<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 Configuring LAN switch

3.5.1 Configuring ESA12

Purpose

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

Steps

1. Establish a telnet connection to ESA12

a. Enter the preconfigured IP address to ESA12 (the default IPaddress is 192.168.1.9).

telnet <ip address of ESA12>

b. Enter your login ID and password.




The default password is empty. Therefore, press Enter tocontinue. If you have already changed your password duringcommissioning, 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 00 A0 12 0B 02 74

1. Agent IP Address : 192.168.001.009

2. Agent Netmask : 255.255.255.240

3. Default Gateway : 192.168.001.001

4. Supervisor/Terminal Password :

5. System Name :

6. Advanced Features

9. Main Menu

3. Press the number of the parameter you want to change

Expected outcome

The selected parameter row with the current settings is printedbelow the menu.

4. Use the backspace key to remove the current parameter value


RNC Integration

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, thepassword has not been changed yet.

telnet 192.168.1.9

Username:nokia

Password:

2. Press 1 to select General Configuration in the main menu.

3. Press 3 to select Default Gateway. The current address is displayedon the command line:

Default Gateway : 192.168.1.1

4. Use the backspace key to remove the current parameter value.

5. 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 00 A0 12 0B 02 74

1. Agent IP Address : 192.168.001.009

2. Agent Netmask : 255.255.255.240

3. Default Gateway : 10.001.001.002

4. Supervisor/Terminal Password :

5. System Name :

6. Advanced Features

9. Main Menu




3.5.2 Configuring ESA24

Purpose

This procedure describes how to configure the ESA24 Ethernet/LANswitch.

Before you start

Before you start the configuration, check the following:

. The PC or laptop that you are using is connected to one of theEthernet ports of the ESA24 switch with an Ethernet cable.

. The ESA24 Ethernet switch is powered up (the LED on the frontpanel 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 addresswill change to the given address by the command IP address X.X.X.

X/x.x and the Telnet connection will stop responding. The initialconfiguration has to be done by the serial connection. See ESA24 10/100 Mbit Ethernet Switch User Guide for the detailed information.

a. Start a Telnet session by selecting Start -> Run on theWindows Taskbar.

b. Connect to the IP address of ESA24:

telnet <IP address of ESA24>

c. Press Enter.

Expected outcome

The system prompts for a password:

User Access Verification

Password:

2. Log in to ESA24


RNC Integration

Enter the default password "nokia", or the new password if thepassword 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 SpanningTree Protocol (RSTP) or the Multiple Spanning Tree Protocol(MSTP) for ESA24.

a. Plan the STP role of each LAN switch in the L2 broadcastdomain area.

b. Check that all LAN switches in the L2 broadcast domain areaare running compatible STP versions.

c. Configure the bridge priority of the STP root switch andconfigure all the links directly connected to computer units asedge ports.

For more information, see ESA24 10/100 Mbit Ethernet Switch UserGuide in PDF format in NOLS and Cable Lists and Use of ATM Linksand LAN Connections in Site documents.

4. Change to a privileged mode in BiNOS

Enable the privileged mode in ESA24 operating system with thecommand

ESA24> enable

The privileged mode allows advanced viewing and configuration forthe unit.

Note

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

By default, the enable command does not ask for a password. It ispossible to protect the administrator's rights with a password. Seethe ESA24 10/100 Mbit Ethernet Switch User Guide for moreinformation.




5. Change to configuration mode in BiNOS

Enable the configuration mode in ESA24 operating system with thecommand

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 commandprompt. 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:


RNC Integration


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 Configuring NEMU for DCN

3.6.1 Configuring NEMU for DCN

Purpose

To get NEMU fully integrated to the DCN, NEMU's default settings areconfigured 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 securityreasons, it is recommended to change the default user ID and/orpassword immediately after the first login.




For more information, see the instructions in NetOp remote accessto NEMU and Configuring NetOp Guest in Network ElementManagement 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 inNEMU.

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. TheDHCP client in an IP host sends a broadcast query to the network, where aDHCP server receives it. The DHCP server answers the client by returningits IP address and other parameters. The returned values have beensaved in the DHCP server's database.


RNC Integration

With the RNC, DHCP is used to distribute IP parameters to IP devices thathave been locally attached to the RNC. An example of such a device is aPC that has the Element Manager running.

The DHCP server is configured according to the IP plan. The DHCP serveris needed because the PC in which the RNC Element Manager is runningreceives the IP parameters from the DHCP server of the NEMU. PC is notneeded for configuring, but a standard DHCP can be used to configure thePC. 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 whichyou want to create a new scope.

b. Select Action -> New Scope.

c. Enter the name of the scope. For example, LocalManagement.

d. Enter the IP addresses and masks for the new scopeaccording to the IP plan.

Note

If you have static IP addresses configured on non-DHCP clients (forexample, NEMU), you must use the IP address pool that does notcontain those IP addresses. If you use an IP address pool that containsthose addresses, you must configure the Exclusion Range list onDHCP Scope.

e. When the system asks you if you want to configure the DHCPoptions 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.

4. Modify the DHCP options according to the IP plan




a. Under the server, select Server Options -> Action –>Configure Options.

b. 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 sofwareinstallations because the DNS server is installed in NEMU by default. Onlya new DNS zone needs to be activated and created.

The Domain Name System (DNS) is a distributed database which mapshostnames and IP addresses. DNS servers are needed to enable the useof DNS names (for example, nemu.rnc1.netct.operator.com) insteadof IP addresses. The DNS management server is the primary server(Master name server) of the zone. Servers in the network are secondaryservers. This means that DNS information is managed in the DNSmanagement server and the secondary servers automatically update theirDNS databases from the management server. DNS servers in the networkare authoritative for their zone, so they handle the DNS queries concerningthe zone.


RNC Integration

Figure 4. DNS architecture

The DNS management server is located in the Nokia NetAct. All the RNCNEMUs have a secondary DNS server, which updates its information fromthe DNS management server. The updating is normally controlled by theDNS management server (see the DNS Notify RFC 1996 by the IETF). Ifthere 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.

ZONEtransfers

RNSDCN

BTS

BTS

SecondaryDNS server

Nokia NetAct

DNSmanagement

server

DNSqueries

RNC

ElementManager

BTSElementManager

DNSqueries




Steps

1. Configure the DNS client data

a. Select Start -> Settings -> Network and Dial-UpConnections.

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 searchorder, 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 MoreWrite down theoriginal name of the computer as you will need it when runningthe 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 beforerunning sqlnamefix script. See Finalising SQL serverconfiguration.

2. Start and check the DNS service

a. Select Start -> Settings -> Control Panel -> Administrativetools -> Services -> DNS Server.

b. Select Action -> Properties.

c. Click Start.

d. Change the current status to 'Automatic'.

3. Start the DNS manager

Start the DNS manager from Start -> Programs -> Administrativetools -> DNS.

4. Add a new secondary or primary DNS zone to the server

To add a new secondary DNS zone to the server:


RNC Integration

a. In the list of DNS servers, select the server to which you wantto add the new zone.

b. Select Action -> New Zone.

c. Select Standard secondary as the zone type.

d. Select Forward lookup zone.

e. Enter the zone name according to the IP plan. The zone nameis the end part of the computer name. For example, if the nameof the NEMU is nemu.rnc1.nokia.com, the zone name is thenrnc1.nokia.com.

f. Enter the IP address of the master server according to the IPplan. Zone information is refreshed when the secondary serverhas a connection to the master server.

g. Select Action -> Properties -> Forwarders.

h. Select Enable Forwarders and add the IP address of themaster DNS server.

Or

To add a new primary DNS zone to the server:

a. In the list of DNS servers, select the server to which you wantto 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 nameis the end part of the computer name. For example, if the nameof the NEMU is nemu.rnc1.nokia.com, the zone name is thenrnc1.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 thezone 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 thename of the NEMU server, for example nemu, and thecorresponding IP address.

d. Repeat steps b and c for each domain and host according tothe IP plan.




6. Update the data files of the server

Select Action -> Update Server Data File.

7. Check that the DNS service configuration succeeded, ifnecessary

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 thepreconfigured 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 andOMU requires that the Win2000 registry includes the IP address of OMUand the user ID and password of the network element. The user ID andpassword have been defined in the network element for the EMTconnection.

The IP address of the NEMU and the FTP username and password alsohave 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 FTPconnections can use.

Before you start

The following user accounts have to be created to NEMU:


RNC Integration

. NEMU FTP user (for example NEMUFTP)

. NWI3 user

Note that the NWI3 user must be the same as defined in the NetActmaintenance region to which the NEMU belongs. For instructions oncreating user accounts, see Creating a new EM user in Element ManagerAdministration.

Tip

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

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

Table 6. RNC data in NEMU registry

Variable Data

Base identifier of RNC NE-RNC-<id>, where the <id> must bewithin the range 1 - 4095.

OMU's IP address As configured in Configuring IP stack inOMU.

NEMU's IP address As configured in Checking IP address forNEMU.

EMT UserName The NEMUAD user ID created in CreatingMMI user profiles and user IDs for remoteconnections to NetAct.

EMT Password The NEMUAD user password created inCreating MMI user profiles and user IDsfor remote connections to NetAct.

OMU FTP Username The NEMUAD user ID created in CreatingMMI user profiles and user IDs for remoteconnections to NetAct.

OMU FTP Password The NEMUAD user password created inCreating MMI user profiles and user IDsfor remote connections to NetAct.

OMU Telnet UserName The NEMUAD user ID created in CreatingMMI user profiles and user IDs for remoteconnections to NetAct.

OMU Telnet Password The NEMUAD user password created inCreating MMI user profiles and user IDsfor remote connections to NetAct.




Table 6. RNC data in NEMU registry (cont.)

Variable Data

NEMU FTP UserName The name of the service user with NEMUFTP Access (for example, NEMUFTP) asdefined in Creating a new EM user inElement Manager Administration.

NEMU FTP Password The password for the NEMU FTP user asdefined in Creating a new EM user inElement Manager Administration.

NEMU Registration Account Username The NetAct NWI3 Access accountusername.

NEMU Registration Account Password The NetAct NWI3 Access accountpassword.

NEMU ID The host name of NEMU. For example:NEMU-2.

Network Management’s Registration IOR(RSIOR)

The Network Management's RegistrationIOR (RSIOR) in NetAct

Summary

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

Steps

1. Open the Command Prompt from Start -> Run

2. Type NemuRegEdit, and click Enter

3. See further instructions in NemuRegEdit

3.6.5 NemuRegEdit

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


RNC Integration

Note

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

Start NemuRegEdit

Start NemuRegEdit by entering the command NemuRegEdit in a commandprompt window.

When NemuRegEdit is started, it shows the current configuration settingsfrom 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 thefollowing actions:. To modify the default network element settings, select Modify

(M).

If you select modify (M), NemuRegEdit prompts you to enterthe number of the network element:

Enter the number of network element you wish to modify andpress <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 informationof 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 managednetwork element: 192.168.12.1




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 thedefault 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 NEMUand 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 thenprompts 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


RNC Integration

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: ******


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: ******





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 youpress 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 notwant to set a value, press ENTER.

. Network Management's Registration IOR new value:IOR:12345678910111213141516

. Is this correct (Y/N)?


RNC Integration

If the value is correct, select Y. The 'Value set OK' message isshown.

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 isrestarted. If the computer is restarted after the NEMU integration isfinished, the NEMU software does not need to be restarted.

NEMU software restart can be done with the NEMU Platform ManagerUser Interface in the following way:

1. Start the NEMU Platform Manager User Interface from Start >Programs > NEMU Platform Manager User Interface > PMUI.

2. Click Stop PM.

3. Wait until the status of the Platform Manager is 'Platform Managernot running'.

4. Click Start PM.

5. Wait until the status of the Platform Manager is 'NEMU softwareRunning'.

6. Close NEMU Platform Manager User Interface.

3.6.6 NemuRUIMConfiguration

If the Remote User Information Management (RUIM) feature is used in thesystem, 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 thatconfiguration data of the centralised authentication servers are set intoNEMU.




The user can do the configuration settings of RUIM feature withNemuRUIMConfiguration.exe tool. This tool is run during the setup, but itis 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 pathin 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 ofprimary and secondary LDAP servers are stored in the nwi3MDCorba.inifile 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 statusfile 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 statusfile contains the status information about the execution. If the executionfails, the errors can be found from the status file.

The questions NemuRUIMConfiguration asks from the user when installoption is used:

Do you want to insert/modify configuration settings of RUIM (Y/N)?

. Y(es)/N(o)


RNC Integration

. Ensure that you want to insert/modify the RUIM configurationsettings.

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

. Tells the current status of the RUIM state and requests a new statusvalue. 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 accountinformation to NEMU is sent successfully.

Also note that with RUIM enabled, the NEMU can use both authenticationmethods, local: local user database, and remote: remote user database,the LDAP server. The authentication mode tells in which order theseauthentication methods are used in order to authenticate the user.

Please, select the instance you want to modify (A=currently active, N=nextto be activated, B=both)?

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

. A (currently active)

After NemuRUIMConfiguration has quit, the RUIM configurationsettings are taken into use immediately. This option is usually usedwhen the RUIM feature is enabled the first time after the NEMUsetup.

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 inthe nwi3MDCorba.ini file. For setting the required parameter innwi3MDCorba.ini file, see Configuring Nokia NetAct interface withNEMU. Remember to restart the NemuRegServApp process afterthe parameter setting.

. N (next to be activated)

After NemuRUIMConfiguration has quit, the RUIM configurationsettings are taken into use after these steps:




1. Open the nwi3MDCorba.ini file

2. Change the takeIntoUseNext to 0 in the currently activeinstance

3. Change the same parameter to 1 in the next instance

4. Close the file. Restart the NemuRegServApp process. Formore information, see Configuring Nokia NetAct interface withNEMU.

. B (both)

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

When RUIM is enabled, it is possible to configure two instances of RUIMconfiguration attributes. If you have for example two different NetActmanager instances, you can define registration attributes for both of themto NEMU (registration username and password, and registration IOR). Inthe same way, both NetAct manager instances have their own LDAPconfiguration attributes, which can be configured to NEMU at the sametime. 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 becreated 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


RNC Integration

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 LDAPserver

. 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:




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 theSecondary 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 inNEMU needs to be changed.

If the upgrade option is used, NemuRUIMConfiguration asks the samequestions that in the install option, but in every configuration valueNemuRUIMConfiguration displays the existing value and asks whether toupdate, 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: Updatethe value (U), Keep the old value (K), Delete the value (D):

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

. Give the new value:

If K (keep the old value) is selected, NemuRUIMConfiguration keepsthe current value. If D (delete the value) is selected,NemuRUIMConfiguration deletes the current value.

NemuRUIMConfiguration goes through all the existing RUIMconfiguration 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 useTardis services without any modifications. However, if you need to changeany settings, follow the instructions below.

Tardis can be found in the Control Panel.

Steps

1. Set Tardis to automatically change servers


RNC Integration

a. Select the General tab in Tardis.

b. Edit the settings as required.

Select Automatically change servers on failure to set Tardisto automatically change to a different server if it cannot contactthe one currently selected. Tardis will cycle through all theservers in the list.

Select Automatically change servers on success to setTardis to automatically change to a different server if itsuccessfully contacts the one currently selected. Tardis willcycle through all the servers in the list. This is useful as a wayof 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 dialogopens.

c. Enter the address of the time server.

Enter the address as a name or as an IP address. When usingthe Network Time Protocol (NTP), the address may be leftblank in which case Tardis will listen to any broadcasts. If anaddress is entered, Tardis will only listen to broadcasts fromthat machine.

d. Enter a descriptive name of the server.

If you do not enter a name, the address of the server is usedinstead.

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 broadcasttime information. Tardis will listen for these broadcasts ifyou use this protocol. NTP broadcast is not used inNEMU domain.

f. If you want Tardis to reject time information from NTP serversthat claim to be unsynchronised, select Rejectunsynchronized NTP.

This can happen if the server has lost touch with its timesource.

3. Modify NEMU time server settings




a. Select the Main tab in Tardis.

b. Double-click the name of the server you wish to modify.

c. Edit the time server settings in the Server details dialog (seethe 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, donot set the system time. This gives you a chance to see firstwhat kind of time it is going to give you without accidentallysetting NEMU's time to, for example, 10:61 77 Jan. 1914.

5. Set the time zone and daylight saving time

Select Set Timezone. It opens the Control Panel for Date and Timewhere you can set up your timezone and whether you use daylightsaving time or not.

Note

Timezone and daylight saving time (DST) must be configured in thesame way both in NEMU and in RNC. This is because RNC uses localtime (which includes timezone and DST) in its time stamps while NEMUuses its own timezone and DST settings when it sends events to NokiaNetAct 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 changethem with the DCS command. If the NEMU clock is automaticallyadjusted to DSTchanges in the Control Panel for Date and Time dialog(default), change the RNC DST setting with the DCT command. This isneeded because RNC does not support automatic adjustment for DSTchanges.


RNC Integration

Note

In certain situations, it is possible that the time stamps of the RNCalarms are different in NetAct and in RNC. If the NEMU clock isautomatically adjusted to DST changes but the corresponding DSTchange is not done in RNC, all alarms are affected. This also affects thealarms that were generated before the DST change even if the DSTchange was configured at the same time in RNC and NEMU. Toprevent this kind of problem, it is recommended not to use DST time inRNC 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 withthe 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. Youcan 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/firewallrequires authentication. Enter the username and password.

Example Configuring Tardis for RNC

This example shows what you need to configure in Tardis during RNCintegration.

1. Open Tardis by selecting Start -> Control Panel -> Tardis.

2. Go to the main menu by selecting the Main tab.

3. Click Add to add a new time server. The Server details dialog opens.

4. Enter the address, name, and protocol of the time server. Theaddress depends on your configuration, the name you can freelychoose, and the protocol is SNTP.

5. Go to the time menu by selecting the Setting the time tab.

6. Select Set the time and set the scales to default values.

7. Select Set Timezone. Choose the time zone where you are locatedand whether you use daylight saving time or not.




3.6.8 Finalising SQL server configuration

Purpose

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

Steps

1. Log on to Windows

Log on to Windows using the Nemuadmin account.

2. Execute updatesql.bat from C:\temp\sqlnamefix

3. 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 fromStart -> Programs -> Microsoft SQL Server-> EnterpriseManager.

5. Expand Microsoft SQL Servers from tree view

6. Expand SQL Server Group from tree view

7. Expand Local SQL

8. Expand Security/Logins from local SQL

9. Check the computer name of the nemuadmin account

In the logins list, there is a computer name before the nemuadminaccount. For example, NEMU-012345/nemuadmin. Check thecomputer name has been replaced by the new computer nameintroduced in Configuring DNS client and server in NEMU.

If the computer name has been changed, close the Enterprisemanager.


RNC Integration

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 matchthe current NEMU computer name

Then

Create a new nemuadmin login for SQL

a. Delete the nemuadmin account with the computer name (right-click it and select Delete). Confirm deletion by clicking Yes.

b. Click the new login icon and then click the name browsebutton.

c. Select Nemuadmin to the name field, then click Add and OK.

d. Insert language.




e. Go to the Server roles tab, select System Administratorsand click OK.

f. Close SQL Server Enterprise Manager.

Further information

Sometimes MCC is known to crash, presenting an error popup on thescreen and SQL update script loses sync. In such a case, click OK errorpopup and open SQL Server Enterprise Manager from Start ->Programs -> Microsoft SQL Server -> Enterprise Manager.

1. Expand SQL Server Group from tree view.

2. Expand Local SQL.

3. Right-click the SQL Server group icon and select Delete SQLServer Registration. Click Yes.

4. Add NEMU's name.

Select New SQL Server Registration from Action menu and clickNext. Choose NEMU's name from the servers list and click Add andthen 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 toconfigure the IP address and the subnetwork mask of NEMU. However, ifpreconfigured IP addresses are in use in NEMU, initial configuration canalso be done via the remote management application.

Steps

1. Select Start -> Settings -> Network and Dial-Up connections

2. Double-click Local Area Connection 3

3. Click Properties

4. Select Internet Protocol (TCP/IP) and click Properties

5. Enter the correct IP address

6. Enter the correct subnet mask


RNC Integration

7. Enter the default gateway

8. Click OK -> OK

When you are configuring RNC NEMU via a remote managementapplication, the connection closes when you click OK the secondtime 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, refreshDHCP 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 theoperating system:. In Windows NT/2000:

a. Open the command prompt from the Start -> Programsmenu.

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 -> Programsmenu.

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 selectStart -> Shut Down -> Restart.




3.7 Configuring external IP connections

3.7.1 Connecting to O&M backbone via Ethernet

Purpose

This procedure describes how to connect RNC to the external network forO&M connections using an external router connected to the ESA12 orESA24 Ethernet switch.

O&M connections from the RNC to the O&M backbone can also becreated via ATM virtual connections, but Ethernet is the preferred way. TheO&M connection via ATM should only be used as a backup.

Note

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

Before you start

Because the IP addresses for OMU, the Ethernet switch, and NEMU havebeen preconfigured in the RNC, you must change the IP addresses beforeconnecting the RNC to the external network. Several elements in thenetwork can have the same preconfigured IP addresses, so if you do notchange the preconfigured addresses, there will be problems in thenetwork.

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

2. Configure external router according to instructions provided bythe router vendor


RNC Integration

3.7.2 Configuring IP over ATM interfaces

Purpose

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

Note

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

IP over ATM interfaces must be configured in GTPU units for Iu-PSinterface between the RNC and the SGSN, and in OMU units for BTSO&M between the RNC and the BTS/AXC.

Before you start

ATM resources must be created before this procedure is commenced. Forinstructions, see Creating ATM resources in RNC in ATM ResourceManagement.

Steps

1. Interrogate the states of the units in the system (USI)

Check that the units for which you are going to create networkinterfaces 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/physicalunit>:<IP interface>:<ATM interface>,<VPI number>,<VCI number>:[<encapsulation method>],[<usage |IPOAM def>];

ATM interface, VPI number and VCI number are the values given inthe commands of creating ATM resources.




The encapsulation method can be LLC/SNAP or VCmux. If InverseATM 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 therouting 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>],[<IPaddress type>]:[<netmask length>]:[<destination IPaddress>]:[<MTU>]:[<state>];

For IPv6:

ZQ6N:<unit type>,<unit index>:<interface name>:[<IPaddress>]:[<prefix length>]:[<destination IPaddress>];


RNC Integration

4 Integrating NEMU

4.1 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 networkelement (for example, systemId = NE-RNC-'rnc_id'). In this scenario, thesystem consists of a managed network element and NEMU, which islogically seen as part of network element itself. In this case, systemidentifier 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 canbe problems in sending notifications to the NetAct. Note also that thesystemId must be unique in the whole network.

Steps

1. Open %NEMUWWWROOT%\systemid.txt file to NOTEPADeditor

The value between % marks refers to an environment variable. Forexample, %NEMUWWWROOT% means that there is anenvironment variable NEMUWWWROOT in the system.

2. Add value of the systemId to the file



Integrating NEMU

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

3. Save the file

4.2 Configuring the RNC object

Purpose

When the RNC RNW Object Browser is first taken into use aftercommissioning, the very first task is to configure the RNC by setting therequired parameters. This is done because the RNC object is the topmostobject in the hierarchy, and so it has to be created first. Please note thatthe RNC RNW Object Browser provides online help to assist you incarrying out the tasks. You can access the online help by clicking the Helpbutton in the RNC dialogue.

Note

If this initial phase of the configuration is not successful, the user cannotproceed 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 withyellow. For more information on parameters, see WCDMA RANParameter Dictionary.


RNC Integration

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 acknowledgeit by clicking OK. The parameter window where the error occurred isdisplayed, and you can either modify the parameters and try again orcancel the operation.

4.3 Configuring Nokia NetAct interface with NEMU

Purpose

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

Steps

1. Check that CORBA/IIOP and Session Manager are running

Open the Task Manager in NEMU from Start -> Run -> taskmgr (orpress 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 theNEMU commissioning. The systemId attribute has been saved to thetext 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



Integrating NEMU

a. Configure the NetAct parameters for NEMU.

i. Open %NEMUPLATFORMDATADIR%\c_services\nemucorbasupserv\nwi3mdcorba\NWI3MDCORBA.inifile in, for example NOTEPAD editor.

The value between % marks refers to an environmentvariable. For example %NEMUPLATFORMDATADIR%means that there is an environment variableNEMUPLATFORMDATADIR in the system.

ii. Add the value of the stringfield IOR to theregistrationServiceIOR field. (This could have been setduring setup, otherwise you can add it directly to the file.)

iii. Set the values of the registrationServiceUsername andregistrationServicePassword with NemuRegEdit tool.(These could have been set during setup. Values areencrypted and stored into Windows Registry.)

iv. Add value of the takeIntoUseNext parameter. This valuemust be changed to 1.

v. Save the file.

b. Restart the registering service of NEMU to activate newparameter values. There are two alternative methods toactivate parameters.. Immediate activation:

i. Start NEMU Platform Manager User Interface(Start -> Programs -> NEMU Platform ManagerUser Interface -> PMUI).

ii. Select NemuRegServApp from the list of NonstopProcesses and click the Stop Process button.

iii. Wait until the status of NemuRegServApp isStopped.

iv. Select again NemuRegServApp from the list ofNonstop Processes and click the Start Processbutton.

v. Wait until the status of NemuRegServApp isRunning.

vi. Close NEMU Platform Manager User Interface.. Long time activation:

i. The registering service of NEMU makes theregistration itself after a variable period (usuallythe default random period is approximately 10-20minutes).

4. Check entries from the registering service of NEMU


RNC Integration

Check from the Windows 2000 Event Viewer if there are entries fromthe registering service of NEMU (NemuRegServ.dll). If there is a logwriting "NemuRegServ: Getting the IOR of the Registration servicefailed.", the registering service of NEMU did not manage to get rsIORwhich is needed for registering in Nokia NetAct.

When the registering service of NEMU is up and running, there is alog writing "NemuRegServ: Successfully registered to registrationservice of NetAct."



Integrating NEMU


RNC Integration

5 Configuring heartbeat interval for RNCPurpose

The management plane connections between Nokia NetAct and RNCs aresupervised with heartbeat (HB) alarms from the RNCs. Nokia NetAct usesthe heartbeat alarm from the RNC to supervise the connection in desiredintervals. By configuring the heartbeat interval, the user can change thesupervision interval to correspond to the actual network environment.

Note

Changing the HB interval locally in the RNC MML interface is onlyneeded 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 willcut it down to the allowed maximum (0x5A0). For information on how tocheck the heartbeat interval in NetAct, see Integrating RNC to NetAct inNokia Online Services (NOLS).



Configuring heartbeat interval for RNC

Expected outcome

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


RNC Integration

6 Configuring RNC level parameters

6.1 Defining external time source for network element

Purpose

The IP addresses used in the Commissioning stage for setting the timeand date are predefined and temporary; therefore, you need to configurethe time source IP address again, using the DCM command, after theinternal 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 15minutes, preferably against the NEMU time server, using NTP messages.

Note

IP connections must be created before you can define the external timesource 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>;



Configuring RNC level parameters

Expected outcome

When you have defined the external time source, in 15 minutes all theclocks in the network element will have the same time as the external timesource has. The internal clock located in the network element gives a timestamp 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 andsoftware.

Note

Note the following in relation to the NPC command when using NodalFunction to connect two adjacent RNCs via MGW Rel.4:

Since the signalling links are used for SCCP signalling, the value ofboth the service existing for STP messages and the service existing foruser 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 forcommands NRP, NSC and NRC in reverse order. This differs from thestandard procedure used elsewhere in the world. For example, inJapan, the signalling point code 23–8–115, would be read as 115–8–23.

Steps

1. Create SS7 services


RNC Integration

Before you start

The signalling messages coming into the network element can betransmitted to the network element's own user parts, or they can beswitched forwards, or both. Depending on the services configured to thenetwork element, some of the signalling messages are unnecessary. Dataon service information determines how the signalling messages cominginto 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 byusing the NPI command. The services SNM and SNT usuallyexist automatically in the network element.

The needed services depend on the type and use of thenetwork element. In Radio Network Controller (RNC) orMultimedia Gateway Rel.4 (MGW Rel.4) type of networkelements 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 messagesand service existing for user part of own signalling

point to choose whether the service is active for the STPmessages and/or to the user parts of the own signalling point.

Check the process family identifiers from the Site SpecificDocuments as there can be some exceptions to the valuesgiven 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;




2. Create own MTP signalling point (NRP)

The own signalling point has to be defined before you can create theother objects of the signalling network. Use the command NRP tocreate the own MTP signalling point. A network element can beconnected to several signalling networks. The NRI commanddisplays all existing signalling points.

There are special network-specific parameters related to thesignalling networks, and you can output them using the NMOcommand. These parameters define, for example, the congestionmethod used in the signalling network. For more information aboutthe network-specific parameters, see SS7 signalling networkparameters.

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>:<numberof spc subfields>:<spc subfield lengths>;

3. Create own SCCP signalling point (NFD)

Before you start creating the signalling point, check what theSignalling Point Code (SPC) of the system's own signalling point isby using the NRI command.

ZNFD:<signalling network>, <signalling point code>,<signalling point parameter set number>:<subsystemnumber>,<subsystem name>,<subsystem parameter setnumber>,[<subsystem status test>]: ... ;

Note

The value YES for the subsystem status test parameter is valid onlywhen the parameter WHITE_BOOK_MGMT_USED (12) of the used SCCPsignalling point parameter set has value YES (check this with the OCIcommand).


RNC Integration

When an SCCP signalling point and SCCP subsystems are created,a parameter set is attached to them. In most cases the predefinedparameter sets are the most suitable, but if the predefined parametersets do not cover all occurring situations, you can create moreparameter sets, modify the relevant parameters and then attach thenew parameter set to the SCCP signalling point and SCCPsubsystem. For more information, see SCCP signalling pointparameters and SCCP subsystem parameters.

4. Add local subsystems to the signalling point (NFB), ifnecessary

ZNFB:[<signalling network>],<signalling pointcodes>:<subsystem number>,<subsystem name>,<subsystem parameter set number>,[<subsystem statustest>];

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.





RNC Integration

7 Configuring transmission and transportinterfaces

7.1 Configuring PDH for ATM transport

Purpose

This procedure describes how to configure the PDH/ATM interface for theNIP1 interface unit. The mode of the PDH interface must be the same forall the exchange terminals in the plug-in unit. That is why the NIP1 unitmust be given as a parameter when the PDH mode is configured.

Usually the existing default values for the PDH supervision are adequateand you do not have to change them. If needed, you can configure andmodify the exchange terminal supervision parameters.

When you have configured new PDH exchange terminals (PET), you mayhave to modify their functional modes. Choose either E1, ETSI-specificfunctional modes, or T1, ANSI-specific functional modes. In a fractionalE1/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 externaltiming reference signals. For information on synchronisation, seeConfiguring synchronisation inputs in Synchronisation and Timing.



Configuring transmission and transport interfaces

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 descriptionin 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 impedanceparameter can be given only if the operation mode given is E1.

ZYAE:NIP1,<network interface unit index>,<interfaceoperation mode>:[<impedance>];

If you change the impedance or the operation mode, you mustrestart the unit so that the changes are taken into use. See theinstructions in Restarting functional unit in Recovery and UnitWorking State Administration.

3. Modify E1 functional modes if needed (YEC)

You can first output the ETSI-specific frame modes with thecommand:

ZYEI;

If the current frame mode does not match with the frame mode of theinterface unit that is connected to the remote end of this line, you canmodify 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 inSynchronisation and Timing.

4. Modify T1 functional modes if needed (YEG)


RNC Integration

You can output the ANSI-specific T1 functional modes with thecommand:

ZYEH;

If the current frame mode does not match with the frame mode of theinterface unit that is connected to the remote end of this line, you canmodify 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 Configuringsynchronisation 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|OFFdef];

7. Create an IMA group, if necessary

If you want to use more than one transmission line, you must createan IMA group for the physical links. Configure PET (YAM) andModify PET timeslot usage (YAW) are repeated for each link which isselected to the IMA group. See the instructions in Creating IMAgroup 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




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 addexchange terminals to it. You can later connect an external ATM interfaceto the phyTTP that has been created for the IMA group.

You must create an IMA group if you want to use more than one PDH-based transmission lines for additional capacity or for securing traffic evenin line failure situations. For example, if one E1 line is used intransmission, you can create an IMA group of two E1 lines and give value1 to the minimum number of links parameter. Even if one line fails, theATM interface stays up.

The maximum allowed number for each IMA group is 8 exchangeterminals. The IMA group must be created at both ends of the physicallinks.

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 PDHfor ATM transport.


RNC Integration

The PETs to be combined to an IMA group must belong to the same NIP1functional unit. Check which functional unit a PET belongs to with the USIcommand.

Each PET is identified by its exchange terminal index, which is a system-wide unique numerical value. In addition, the system assigns a link ID toeach PET. This link ID is unique in the IMA group.

One of the physical links functions as the Timing Reference Link (TRL) ofthe IMA group, which is identified by its link ID. The system assigns theTRL to the IMA group.

Steps

1. Create IMA group (YBC)

ZYBC:[<IMA group id>] | <system select> def:[<exchange terminal type> | PET def],<exchangeterminal index>...:<minimum number of links>;

Note

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

Further information

You can add more PETs later on to the group with the YBAcommand. 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 withthe YBM command, and delete an IMA group with the YBD command.

It is possible to remove exchange terminals from an IMA group with theYBR command.

Adding or removing links automatically affects the bandwidth of the accessprofile of the ATM interface.




Example Creating IMA group

1. Create an IMA group using the IMA group ID selected by the system.

The type of exchange terminal is PET by default. The IMA groupcombines PDH exchange terminals 0, 5 and 14. The minimumrequired 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 andmodify the SDH exchange terminal (SET) configuration. You can definehow the transmission capacity is divided, and change the threshold levelsfor performance monitoring to meet the expected quality of thetransmission network.

Before you start

You must create the functional unit description for the SETs. Forinstructions, see Creating and attaching functional unit description inHardware Configuration Management.

Steps

1. Interrogate the SET (YAI)

With the following command you can find out the current exchangeterminal configuration.

ZYAI:<SET>,<SET index>;

2. If you want to modify the default settings, configure the SET(YAN)


RNC Integration

Note

When VC mapping is changed, the affected higher and lower orderpaths 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 notused for the higher or lower order paths. The SES BIP threshold forthe higher order paths is the same as the one used for the multiplexsection 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 orderpath number>|<higher order path number>,<lower orderpath number>]:[<SES BIP threshold>]:[<SD BERthreshold>]:[<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, ifnecessary. The SDH trace trail must be configured identically to boththe trails related to a specific phyTTP (logical path) in a protectiongroup. When you configure a trace for a trail that is part of aprotection group, the system automatically applies the changes alsoto the other trail of the pair and sends a notification on this.

Note

Trace types EXPPATH and EXPREG are not currently supported.




ZYAS:<SDH exchange terminal index>,[<higher orderpath number>|<higher order path number>,<lower orderpath number>]:(OUTPATH|EXPPATH|OUTREG|EXPREG),(RESET|SET1|SET16|SET64),<trace value>;

For more information on the trails, see Creating SDH protectiongroup.

4. Create SDH protection group, if necessary

If you want to secure the traffic even when a line fails, you need tocreate an SDH protection group. Refer to the instructions in CreatingSDH 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 Configuring SDH for ATM transport

1. Modify the SES BIP threshold of the SET 1 to 2300 frames persecond. 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 the16-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 exchangeterminals (SET). Multiplex Section (MS) trail linear protection is used toprotect a single multiplex section trail by replacing a working MS trail if theworking trail fails or if the performance falls below the required level. Thereare two supported protection protocols:


RNC Integration

. linear, bi-directional Multiplex Section Protection (MSP) 1+1compatible 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 tothe same logical path in a protection group. Otherwise, the systemprevents the protection group creation.

Steps

1. Create SDH protection group (YWC)

ZYWC:[<protection group id>|<system select> def],[<protection switching mode>|NONREV def],[<protocolvariant>|MSP def]:<Working section SDH exchangeterminal index>,<Protection section SDH exchangeterminal index>:[<wait to restore time>|300 secondsdef];

The system will ensure that both trails of a pair are configuredidentically in a protection group.

2. Create Physical Layer Trail Terminal Point (phyTTP), ifnecessary

If the protected SDH interfaces are for ATM traffic transport, youneed to create phyTTP.

See the instructions for creating the physical layer Trail TerminationPoint in Creating phyTTP.

Expected outcome

The system generates the 0101 SDH PROTECTION SWITCHINGEXECUTED notice if the protection switch operation succeeds.

Unexpected outcome

The system generates the 3183 SDH PROTECTION SWITCHINGFAILED alarm if the protection switch operation fails.

If the far end has not been configured to support the correct SONET APSconfiguration, the system generates the 3307 MISMATCH IN SONETAPSCONFIGURATION alarm.




If the far end of the protected multiplex section is not able to use theprotection section, the system generates the 3334 FAR ENDPROTECTION SECTION FAILURE alarm.

Further information

You can interrogate the protection group configuration and protectionswitching status information with the YWI command, modify theconfiguration with the YWM command and delete the configuration with theYWD command. Note that a protection group cannot be deleted if a phyTTPhas been created for it.

Example Configuring SDH protection group with default protectionprotocol parameter values

1. Create a protection group of SET 7 (working section) of NIS1P-1 andSET 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 SONETAPS variant ofthe 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 betweenthe physical layer and the ATM layer. The phyTTP ID is used whencreating the ATM interface.


RNC Integration

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

Note

You cannot create a phyTTP for a single SDH VC path of a 2Nredundant network interface unit. The phyTTP for a 2N redundant unitmust be created for the VC path of the SDH protection group that hasbeen 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) beforeyou can create the phyTTP for them. For configuration instructions, seeConfiguring PDH for ATM transport and Configuring SDH for ATMtransport.

If you need to interrogate the phyTTP configuration or the operational stateof 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, onlyATM traffic is supported in this release.

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

Table 7. Parameters and values for creating phyTTP

Parameter Value

If you are creating phyTTP to a SET:




Table 7. Parameters and values for creating phyTTP (cont.)

Parameter Value

SET index of the SET

VC path number VC path number

If you are creating phyTTP to a PET:

PET index of the PET

If you are creating phyTTP to an IMA group:

IMA ID of the IMA group

If you are creating phyTTP to an SDH protection group:

PROTGROUP ID of the protection group

VC path number VC path number

Further information

You can delete a phyTTP with the YDD command. After the deletion, itsphysical resources are free to be used again; for example, you can addPET to an existing IMA group or you can protect SET by creating aprotection group. On the other hand, IMA/protection group can be deletedif there is no phyTTP related to it.

The phyTTP cannot be deleted if it is used by the upper layer, that is, ifthere is an ATM interface created on it. You can use the YDI command tocheck 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;


RNC Integration

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 thefollowing 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 layerconfiguration in the RNC. At the Iub interface use the RNC RNW ObjectBrowser or the RNW Plan interface from the NetAct for BTS relatedsignalling link and the AAL2 user plane VCC configuration. In the Iubinterface configuration of the ATM interface and its access profile needsto be created via the MMLs or ATM plan interface before creating theIub connection configuration (COCO managed object).

For further details see ATM plan interface in document RNC Operationand Maintenance.

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




Caution

When defining traffic parameter values, take into account the capacitylimitations of an ATM interface. If the resources are misconfigured, thesystem will reject the creation of VP/VC connections later. See alsoTaking termination point into use fails.

Before you start

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

Steps

1. Create an ATM interface connected to a physical layer TrailTermination 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 aphysical layer Trail Termination Point

Parameter Value

interface id Select a numerical value.

If you do not set the value manually, thesystem will choose a free numerical value.

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>;


RNC Integration

Table 9. Parameters and values for creating the access profile of the ATMinterface

Parameter Value

interface ID As defined in step 1.

max VPI bits Select a suitable value, for example 5.Setting the value to 5 allow VPI valuesfrom 0 to 31 to be used.

max VCI bits Select a suitable value equal to or greaterthan 6, for example, 7. Setting the valueto 7 allow VCI values from 32 to 127 to beused.

UPC/NPC mode Select whether UPC/NPC (policing) is tobe enabled or disabled for this interface.

For details on creating the access profile, refer to ATM interfaceaccess profile.

Expected outcome

The system will set the bandwidth to fully use the capacity of thephysical 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, seeCreating Radio Network Connection Configuration.

When creating ATM termination points for IPoA connection, seeCreating ATM termination point for IP over ATM connection.

Note

The rest of the steps in this procedure are not necessary for Iubinterface.

4. Create VPLtps for UBR traffic, if necessary (LCC)




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 servicelevel>:<segment endpoint info>,<VP level trafficshaping>::<egress service category>,,,<egress QoSclass>:;

Table 10. Parameters and values for creating a VPLtp for UBR traffic

Parameter Value

interface id Same as in steps 1 and 2.

tp type VP

VPI Select VPI value within the range definedin step 2.

VPL service level VC

segment endpoint info Depends on network planning

VP level traffic shaping For Iu-BC, NO

For other interfaces, depends on networkplanning

egress service category U (UBR)

egress QoS class 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.


RNC Integration

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

Note

If an ATM Virtual Path Leased Line service is used to implement the Iu-BC interface, a VPLtp should be created as CBR type with definedPeak Cell Rate. VP level traffic shaping should be enabled to limit thepeak cell rate of the VP and thus avoid cell loss due to policing in theATM 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 servicelevel>:<segment end point info>,<VP level trafficshaping>::<egress service category>,,,<egress QoSclass>:::<egress PCR>,<egress PCR unit>;

Table 11. Parameters and values for creating a VPLtps for CBR traffic

Parameter Value

tp type VP

VPL service level VC

segment endpoint info Depends on network planning

VP level traffic shaping For Iu-BC, FULL

For other interfaces, depends on networkplanning

egress service category C (CBR)

egress QoS class C1 (QoS Class number 1)

egress PCR Depends on network planning

egress PCR unit Depends on network planning

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

6. Create VCLtps for UBR traffic, if necessary (LCC)

You need to create VCLtps for UBR traffic for the following:




. In Iu-CS interface, one VCLtp for SS7 (MTP3SL) signallingtraffic. Depending on the network planning, this may not benecessary.

. In Iu-PS interface, the necessary number for data traffic. Youneed at least one IP over ATM connection per GTPU unit.

. In Iu-BC interface, the necessary number for IP traffic and datatraffic. You need at least one IP over ATM connection per ICSUunit.

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

Table 12. Parameters and values for creating VCLtp for UBR connection

Parameter Value

tp type VC

VPI The same as in step 4.

ingress service category U (UBR)

ingress EPD E (enabled)

ingress PPD E (enabled)

ingress QoS class U

egress service category U (UBR)

egress EPD E (enabled)

egress PPD E (enabled)

egress QoS class U

7. Create VCLtps for CBR traffic (LCC)

You need to create VCLtps under the VPLtp(s) for CBR traffic for thefollowing:. 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.


RNC Integration

ZLCC:<interface id>,<tp type>,<VPI>,<VCI>::<ingressservice 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. Parameters and values for creating VCLtps for CBR traffic

Parameter Value

tp type VC

ingress service category C (CBR)

ingress EPD E (enabled)

ingress PPD E (enabled)

ingress QoS class C1

egress service category C (CBR)

egress EPD E (enabled)

egress PPD E (enabled)

egress QoS class C1

ingress PCR Depends on network planning

ingress PCR unit Depends on network planning

egress PCR Depends on network planning

egress PCR unit Depends on network planning

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





RNC Integration

8 Configuring synchronisation inputsPurpose

You can configure and control synchronisation with MML commands.Usually synchronisation-related MML commands are used for setting thesynchronisation system-related parameters and also for gettinginformation from the synchronisation system.

By using the correct MML command, you can force the system clock touse a synchronised operating mode or a free-run operating mode. Undercertain operating conditions, for example calibration, this is a necessaryaction.

You must always create synchronisation inputs when taking a networkelement into use. You can change the inputs later, if needed. The followingorder of steps is not obligatory.

You can check the available synchronisation references with the DYIcommand.

Use the DYS command to set a synchronisation reference as the forcedreference of the system clock. Notice that the forced reference can evenbe lost and the operation mode of the system clock is changed toHoldover. The changes in the quality of the other references do not affectthe forced reference setting.

Whenever a synchronisation reference that is used in the synchronisationof the system clocks, is lost, the reference is considered to be availableafter the WTR (Wait To Restore) time has expired. The default WTR is fiveminutes.

Enable the distribution of the outgoing signal if you want to distribute thesignal outside the network element.

Set the operation mode when testing the network element. Usually this isdone automatically by the system.



Configuring synchronisation inputs

Note

If you have set the operation mode to FREE, when testing the systemfor instance, you have to set the mode back to SYNC. This is not doneby the system.

Steps

1. Set the parameters for all synchronisation references (DYM)

The highest priority value (PRI) is 1. The highest synchronisationstatus message value (SSM) is 1, the lowest is 14. In addition, value0 is used when the quality of the reference is unknown, and value 15is used when the reference must not be used in synchronisation.

The SSM value is entered manually to external references. All linereferences, including the PDH line interfaces, get their SSM valueson line from the frame structure of the incoming signal. You have toset parameters for at least one synchronisation reference.

Note

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

Note

The Framing mode for the incoming PDH references must support thetransfer of the SSM values. For instructions about configuring theFraming mode, see Configuring PDH for ATM transport.

If the Framing mode for the incoming PDH references does not supportthe transfer of SSM values, the references can be set with the PRIvalue.

ZDYM:<synchronisation reference>,<reference index>,<mode of external reference>:PRI=<priority value>,SSM=<ssm value>;

2. Check the automatic synchronisation setting (DYI)


RNC Integration

When the parameters for at least one synchronisation reference withOK status are set for the first time during system start-up, the systemwill synchronise automatically. In this case you do not have tomanually 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 thereference is available, it can be forced to lock into the reference byusing the DYT command. This command is not normally used in thecommissioning phase and it must not be used instead of enteringparameters 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 tochange it, use the parameter SET. If you want to switch it off, youneed to give the RESETcommand. If you want that the WTR timer isnot set at all when the used synchronisation reference is lost, useSET parameter to change the value of the WTR timer to 0.

ZDYL: <synchronisation reference>, <referenceindex>: <action>, <value>;

Note

RESEToption means that the running WTR timer for a synchronisationreference will be initialised immediately to 0 but if you want to disablethe 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)




Enable the distribution of outgoing synchronisation if you want todistribute 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 thatthe SSM values can be written into it. For instructions on configuring theFraming mode, see Configuring PDH for ATM transport.

ZDYE:<synchronisation reference>,<referenceindex>...: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 ofsystem clock (DYS)

Use the DYS command to set a synchronisation reference as theforced reference of the system clock. Notice that the forcedreference can even be lost and the operation mode of the systemclock is changed to Holdover. The changes in the quality of the otherreferences do not affect the forced reference setting.

Give the value Y for the ACT parameter.

You can release synchronisation reference as the forced referenceof 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)


RNC Integration

Note

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

Note

You must enter the parameters for the connected references to makethem available for the synchronisation system. The PRI value otherthan PRI=X tells the system that the synchronisation reference is readyto 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>;





RNC Integration

9 Creating Iub interface (RNC-BTS)

9.1 Configuring transmission and transport resources

For information on configuring transmission and transport resources, referto Configuring transmission and transport interfaces.

9.2 Creating radio network connection configuration

Purpose

A new logical connection configuration object (COCO) is created in orderto reserve local transmission resources for WCDMA BTS (WBTS). TheCOCO object displays the transmission resources in the Iub interface butnot the actual network topology.

Note

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

Before you start

The ATM interface should be created along with an access profile. Forinformation on creating the ATM resources, see Creating ATM resources inRNC.

Steps

1. Start creating connection configuration.

a. Select Object → New → Connection Configuration → Iub.

b. Set an identifier for the COCO (Connection Configuration ID).



Creating Iub interface (RNC-BTS)

c. Set the ATM interface identifier (Interface ID).

d. Set the wanted virtual path identifier (VPI).

Or

Alternatively, connection configuration can be created using anexisting connection configuration as reference.

a. Select the connection configuration whose structure andparameters should be used in the new connectionconfiguration.

b. Select Object → Use as reference

c. Set an identifier for the new COCO (Connection configurationid)

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 Operationand Maintenance in RN2.2.

For more information on parameters, see WCDMA RAN ParameterDictionary.

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 inthe RNC RNW database and the ATM layer is created into thesystem. Control and user plane-related resources are created intothe 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 isfound in the system. If the COCO creation was successful and theWBTS that the user wanted to relate to the COCO was found, thesystem relates the COCO and the WBTS objects.


RNC Integration

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

Unexpected outcome

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

Further information

Note

If the ATM layer is created with MML commands, make sure that theadministrative state of the VP/VC Link termination points is unlocked.The usage information of the related ATM termination points should befree. If you use the automatic ATM configuration option, the terminationpoints are created unlocked by default.

For further information, see Creating ATM resources in RNC and Digitanalysis and routing in RNC.

9.3 Creating ATM termination point for IP over ATMconnection

Purpose

A new ATM termination point is created in order to configure ATM layer forIP over ATM (IPoA) connection. Please note that the RNC RNW ObjectBrowser provides online help to assist you in carrying out the tasks. Youcan access the online help via the Help menu in the main window or byclicking the Help button in the dialogue windows.

These instructions refer to the configuration with the RNC RNW ObjectBrowser GUI. In addition to the GUI-based ATM termination pointconfiguration for the IP over ATM connection, the MML interface and theATM plan interface towards the NetAct can also be used.




For more information on the IP plan interface, see ATM and IP planinterfaces.

Before you start

Note

The IP over ATM configuration has to be completed with the commandsdefined in the example Configuring IP over ATM interface in Creatingand modifying IP over ATM interfaces.

If the connection configuration object (COCO) and IPoA have the sameVPLtp, the COCO has to be created first. This is to ensure that theunderlying VPLtp is created for CBR traffic class

Steps

1. Select Object → New → Connection Configuration → IP overATM TP.

2. Set the ATM interface identifier, VPI and VCI values.

3. Set the wanted PCR value for defining the desired bandwidthfor IPoA connection.

4. Click OK to confirm operation.

Expected outcome

The progression of the operation is displayed.

Expected outcome

An ATM layer configured to handle an IP over ATM connection is createdin 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 thecreation fails, try again by starting from step 1.


RNC Integration

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 BTSO&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 configuredas CBR class. This also means that if the O&M VCI is configured to UBRclass, it can use the same maximum capacity that is the bit rate for theshaped 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 BTSin a tree topology.

For more information on the topologies, see the Nokia WCDMA RANSystem 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 theBTSs. When you create the OSPF configuration, the routes areautomatically created after the configuration.

With OSPF, you must use unnumbered interfaces towards the BTS,because the AXC only supports unnumbered interfaces. If you havenumbered point-to-point interfaces with static routing in use and you wantto activate OSPF also to these interfaces, you must modify the interfacetype. For instructions on how to modify point-to-point interfaces, seeCreating and modifying IP interfaces in IP Connection Configuration forRNC.




Note

Currently, FlexiBTS does not support dynamic (OSPF) routing andnumbered IP interfaces. Therefore, only static routing must be usedtowards 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 beconfigured via the IP plan interface from the NetAct. The IP plansupport does not contain the OSPF configuration. For further details onthe IP plan interface see IP plan interface in document RNC Operationand Maintenance.

You need to create ATM resources for the Iub interface before starting thisprocedure. When using tree topology, the VPI/VCI termination point withdefault 0/32 must be created for the O&M connection in OMU.

When using star topology, you need to create VPI/VCI termination point forO&M connection for dedicated BTS in OMU. Check if the VPI/VCItermination point is already created for the control plane. By default, thesame VPI termination point is used as the control plane traffic for BTS. TheVPI is configured as CBR class.

You also should have ATM plans available for the tree or star model DCNfor O&M. For more information, see Creating ATM resources in RNC inATM Resource Management.

Steps

1. Start the MMI Window in the Element Manager

For instructions, see Using EM MMI window in Element ManagerAdministration.

2. Create an IP over ATM interface towards BTS in OMU

It is recommended to use unnumbered interfaces towards BTSbecause point-to-point links do not need IP subnets specified for thelink. This also helps in planning and configuring the IP network whenIP subnets are not used with point-to-point links.


RNC Integration

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 OMUto the IP address of the gateway that is on the other side of the point-to-point ATM connections (AXC address of BTS site).

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

Note

The parameter local IP address is only valid for local IP address baseddefault routes. For normal static routes, you do not need to give thelocal IP address. For more information about local IP address baseddefault 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 networknumber of a subnetted network may be used as the area ID. Itis recommended that all OSPF areas except the backbone beconfigured as totally stubby areas.


b. Define the OSPF interface parameters of an OSPF router.

The default value for router dead interval parameter inAXC is 120. Because the value must be the same in both AXCand RNC, change the value of the router dead intervalparameter to 120 in RNC.




ZQKF:<unit type>,<unit index>:<interfacespecification>:<area identification>:[<hellointerval>]:[<router dead interval>]:[<ospfcost>]:[<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 startopology ATM layer and dynamic routing (OSPF) is used.

Figure 6. Example of IP configuration for BTS O&M when star topology andOSPF are used

NEMU

RNC

RNC ElementManager

EL0 10.1.1.2/28 (logical)

AA1 10.1.1.2/32

unnumbered lines

RAN BTS sitesaddress range

10.1.3.0/29

O&Mbackbone

AA2 10.1.1.2/32

OMU

RAN BTS sitesaddress range10.1.2.0/29

RNC LAN10.1.1.0/28

ESA12/ESA24


RNC Integration

1. Create IP interfaces towards every BTS in OMU.

Assign logical IP addresses to the unnumbered point-to-pointnetwork 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 theATM termination point.

Configure an IP over ATM interface with network interface namesAA1...AA32 using the same VPI as control plane traffic, and with VCI32.

ZQMF:OMU,,L:AA1:1,1,32;


...



3. Configure OSPF area parameters of an OSPF router for the BTSbranch.

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;

...




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 treetopology 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 theunnumbered point-to-point network interfaces of the OMU unit, withMTU value 1500, and accept default values for the rest of theparameters.

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 theATM termination point.

Configure a TCP/IPATM interface with network interface names AA1(to OMU from ATM interface 1) and AA2 (to OMU from ATM interface2) using VPI 0 and VCI 32 and accept default values for the rest ofthe parameters.



3. Create static routes for the BTS branch.

Create static routes for OMU to the IP subnetworks 10.1.2.0/24 and10.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;


RNC Integration

10 Creating Iu-CS interface (RNC-MGW)



10.2 Configuring ATM-based signalling channels

10.2.1 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 withgreat care. See SS7 network planning principles.

The SS7 signalling configuration is needed for the following interfaces:



Creating Iu-CS interface (RNC-MGW)

. Iu-CS interface, between MGW and RNC. The configuration isbased on ATM or IP (SIGTRAN). For the ATM configuration, see theinstructions in this chapter. For information on configuring SS7signalling over IP (SIGTRAN), refer to Configuring IP-basedsignalling channels.

. Iur interface, between RNC and RNC; nodal functionality in MGW(see Figure AAL bearer establishment from RNC 1 to RNC 2 forillustration). The configuration is based on ATM or IP (SIGTRAN).For the ATM configuration, see the instructions in this chapter. Forinformation on configuring SS7 signalling over IP (SIGTRAN), referto Configuring IP-based signalling channels.

Figure 7. AAL bearer establishment from RNC 1 to RNC 2

. Iu-PS interface, between RNC and SGSN. The configuration isbased on ATM or IP (SIGTRAN). For the ATM configuration, see theinstructions in this chapter. For information on configuring SS7signalling over IP (SIGTRAN), refer to Configuring IP-basedsignalling channels.

Before you start

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

MGW 1

RNC 1

MGW 2

RNC 2

Iur

Iu-CS

Iu-CS

MGW 3

Nb Nb

H.248

RANAP

BICC

Iur

MSCServer

MSCServer


RNC Integration

The parameter set related to the signalling link can be used to handleseveral signalling link timers and functions. If the ready-made parameterpackages do not cover all occurring situations, you can create moreparameter sets, modify the relevant parameters and then attach the newparameter set to the signalling link. It is advisable to find out if there will besuch special situations before you start configuring the MTP. SeeSignalling link parameters. The following are two examples of specialsituations in which TDM signalling links require modifications in theparameter set:

. One of the signalling links goes via satellite, and the level 2 errorcorrection method has to be preventive_cyclic_retransmissioninstead of the usual basic_method.

. National SS7 specification defines some of the timer values so thatthey are different from the general recommendations.

Steps

1. Check that the signalling links are distributed evenly betweendifferent ICSUs

Use the following command to display the existing signalling links.

ZNCI;

It is recommended that you allocate signalling links between allworking ICSU units to distribute the load.

Caution

It is very important that signalling links belonging to the same linkset areallocated to different ICSU units to avoid the whole linkset to becomeunavailable in an ICSU switchover.

2. Create signalling links (NCS)

Note

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




Note

Remember to check that the network element is adequately equippedbefore you start creating signalling links. You can do this with the WFIcommand.

To create ATM signalling links, give the command:

ZNCS:<signalling link number>:<external interface idnumber>,<external VPI-VCI>:<unit type>,<unitnumber>:<parameter set number>;

It is advisable to create the signalling links belonging to the samesignalling link set into different signalling units, if this is possible. Thisway a switchover of the signalling unit does not cause the wholesignalling link set to become unreachable.

Note

The Signalling Link Code (SLC) and the Time Slot (TSL) have to bedefined so that they are the same at both ends of the signalling link.

You can number the signalling links within the network element as youwish. 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 signallinglinks belonging to the signalling link set cannot be activated until thesignalling link set is connected to a signalling route set.

You can reserve more links for a link set with the NSC command. Youcan 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>;


RNC Integration

The parameters signalling network and signalling pointcode define the network element where the signalling link set leadsto.

To interrogate the existing signalling link sets, use the NSI or NEScommand.

4. Create signalling route set to MGW (NRC)

When a signalling route set is created, a parameter set is attached toit. The parameter set can be used to handle several MTP3 levelfunctions. If the predefined parameter sets do not cover all occurringsituations, you can create more parameter sets, modify the relevantparameters and then attach the new parameter set to the signallingroute 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 setat the same time with the same command.

ZNRC:<signalling network>,<signalling point code>,<signalling point name>,<parameter set number>,<loadsharing status>,<restriction status>:<signalingtransfer point network>,<signalling transfer pointcode>,<signalling transfer point name>,<signallingroute priority>;

The parameters signalling transfer point code andsignalling transfer point name are used when the createdsignalling route is indirect, that is the route goes via signallingtransfer point (STP). There is no need to use those two parameterswhen the RNC is directly connected to the MGW.

Note

A signalling point cannot be used as an STP unless it is first equippedwith a direct signalling route.

For more information about signalling route set priorities, see SS7network planning principles.

To add signalling routes to an existing signalling route set, use the NRAcommand.




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 setat the same time with the same command. Later you can addsignalling routes to a route set with the NRA command.

ZNRC:<signalling network>,<signalling point code>,<signalling point name>,<parameter set number>,<loadsharing status>,<restriction status>:<signalingtransfer point network>,<signalling transfer pointcode>,<signalling transfer point name>,<signallingroute priority>;

The route goes via MGW which is working as a signalling transferpoint (STP) when the created signalling route is indirect.

The parameters signalling transfer point code andsignalling transfer point name are the same as the MGW'ssignalling 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 previouslycreated signalling links:

ZNLA:<signalling link numbers>;

2. Activate the signalling links (NLC)

Use the following command to activate the previously createdsignalling links:

ZNLC:<signalling link numbers>,ACT;

The signalling links assume either state AV-EX (active) or UA-INS ifthe activation did not succeed. Activation may fail because links atthe remote end are inactive or the transmission link is not workingproperly.

For more information, see States of signalling links.


RNC Integration

Note

To interrogate the states of signalling links, use the commands NLI orNEL.

3. Allow activation of the signalling routes (NVA)

Use the following command to allow the activation of the previouslycreated signalling routes:

ZNVA:<signalling network>,<signalling point code>:<signalling transfer point network>,<signallingtransfer point code>;

4. Activate signalling routes (NVC)

The following command activates the previously created signallingroutes:

ZNVC:<signalling network>,<signalling point code>:<signalling transfer point network>,<signallingtransfer point code>:ACT;

Note

To interrogate the states of signalling routes, use the NVI, NER or NRIcommands.

When you are dealing with a direct signalling route, the signallingroute set assumes the state AV-EX if the related link set is active;otherwise it assumes the state UA-INS. A signalling route goingthrough an STP can also assume the state UA-INR if the STP hassent a Transfer Prohibited (TFP) message concerning thedestination point of the route set. For more information, see States ofsignalling routes.

Example Example of activating an MTP configuration

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




First, you change the signalling route state to ACTIVATIONALLOWED, and then you can take the signalling route into service.

ZNVA:NA0,302:;

The execution printout can be as follows:

ALLOWING ACTIVATION OF SIGNALLING ROUTE

DESTINATION: SP ROUTES: SP

NET SP CODE H/D NAME NET SP CODE H/D NAME

--- ------------------ ----- --- --------------- -----

NA0 0302/00770 MSS2 NA0 0302/00770 MSS2 ACTIVATION ALLOWED

COMMAND EXECUTED

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: SP OLD NEW

NET SP CODE H/D NAME NET SP CODE H/D NAME STATE STATE PRIO

--- ------------------ ----- --- -------------- ------- ------- ------ ----

NA0 0302/00770 MSS2 NA0 0302/00770 MSS2 UA-INU AV-EX 2

COMMAND EXECUTED

10.2.3 Setting MTP level signalling traffic load sharing

Purpose

With MTP level signalling traffic load sharing you can share the signallingtraffic between signalling routes and between signalling links belonging tothe same link set.

Within a signalling link set, load sharing is implemented so that itautomatically covers all links that are in active state.

Load sharing between signalling routes takes effect only after you haveallowed load sharing by defining the same priority for all signalling routesand by allowing load sharing in that route set.

Before you start

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


RNC Integration

See also Modifying MTP level signalling traffic load sharing.

Steps

1. Check signalling route priorities and load sharing status, ifneeded (NRI)

ZNRI:<signalling network>,<signalling point code>;

2. Check MTP load sharing data (NEO)

Check which signalling links transmit each of the Signalling LinkSelection Field (SLS) values.

You can use this command to separately interrogate the load sharingdata concerning either messages generated by the own signallingpoint or STP signalling traffic.

Notice that the load sharing system is different for STP trafficaccording 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>,<signallingtransfer 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 theNRI 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:




. 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 allnecessary hardware has been installed on the network element, and thatthe Message Transfer Part (MTP) has already been configured.

Verify the following items:

. Check that the signalling points have been created on the MTP (theNRI command).

. Check which parameter set is used, and whether it is necessary tomodify the values of existing parameter sets to meet the presentconditions 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 SCCPservice has to be created. To check that the service has beencreated, use the NPI command. If there is no SCCP service createdon the MTP level, create it with the NPC command (more informationin Creating remote MTP configuration).

Note

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

Note

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


RNC Integration

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 thesubsystems 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 theNFB command. The system may need new subsystems, forexample, when new services are installed, software is upgraded ornetwork is expanded.

When you are adding subsystems, you need to know whichparameter set you want the subsystems to use or which one has tobe used.

You can display the existing parameter sets by using the OCJcommand. When you want to modify the parameters, use the OCNcommand, and to create a new parameter set, use the OCAcommand.

2. Create translation results, if necessary (NAC)

The translation result refers to those routes where messages can betransmitted. All the signalling points that are meant to handle SCCPlevel traffic must be defined at a signalling point.

At this stage you have to decide whether the routing is based onglobal title (GT) or on subsystem number.

ZNAC:NET=<primary network>,DPC=<primary destinationpoint code>,RI=<primary routing indicator>;

If you want to have a back-up system for routes or the network, youcan create alternative routes that will then be taken into service if theprimary route fails. Also it is possible to use load sharing for up to 16destinations by giving value YES for parameter <load sharing>.

3. Create global title analysis, if necessary (NBC)




Before creating the global title analysis, check the number of thetranslation result so you can attach the analysis to a certain result.Use the NAI command.

For more information about global title analysis, see SS7 networkplanning principles.

ZNBC:ITU=<itu-t global title indicator>,LAST=<lastglobal title to be analysed>:TT=<translation type>,NP=<numbering plan>,NAI=<nature of addressindicator>:<digits>:<result record index>;

4. Set broadcast status (OBC)

It is recommended to add local broadcast status of SCCPsubsystem to RNC. The local broadcast status (using the OBCcommand) informs the subsystems of the own signalling point aboutchanges in the subsystems of the remote signalling points.

Note

When setting the broadcasts, consider carefully what broadcasts areneeded. Incorrect or unnecessary broadcasts can cause problems and/or unnecessary traffic in the signalling network.

Depending on the network element, the subsystems needing thebroadcast function are the following:

. RANAP Radio Access Network Application Part

. RNSAP Radio Network Subsystem Application Part

Local broadcasts:

ZOBC:<network of affected subsystem>,<signallingpoint code of affected subsystem>,<affected subsystemnumber>:<network of local subsystem>,<localsubsystem number>:<status>;

'BROADCAST STATUS OF SCCP SIGNALLING POINTS'definitions (using the OBM and OBI commands) are not needed in theRNSAP and RANAP interfaces connected to RNC, because theycause too much unnecessary signalling.

For more information, see SCCP level signalling network.


RNC Integration

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 thesignalling 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 AV-EX.

Unexpected outcome

If the signalling point assumes state UA-INS, there is a fault on theMTP level.

Example

When you examine an example system using the NFI or NGIcommands, all signalling points should be in normal state AV-EX.Note that the signalling point 101H cannot be seen because theSCCP is not defined in it.

For command ZNGI:NA0,:N; the execution printout can be asfollows:

SCCP STATES

DESTINATION: SP ROUTING: SP

NET SP CODE H/D NAME STATE RM NET SP CODE H/D NAME STATE




--- ------------------ ----- ----- -- --- ------------------ ----- -------

NA0 0102/00258 PSTN2 AV - NA0 0102/00258 PSTN2 AV-EX

NA0 0301/00769 RNC1 OWN SP

NA0 0302/00770 MSS2 AV - NA0 0302/00770 MSS2 AV-EX

NA0 0311/00785 RNC1 AV - NA0 0311/00785 RNC1 AV-EX

NA0 0312/00786 BSC2 AV - NA0 0312/00786 BSC2 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 notchecked from the remote node. The remote subsystem statusbecomes AV-EX if the remote node is available, although the actualsubsystem may be unavailable or even missing. The status of theunavailable subsystem will be corrected with the response methodas soon as a message is sent to it.

Use the NHI command to check that the subsystems have assumedstate AV-EX. If not, the reason may be faulty or missing distributiondata. Correct the distribution data and check the state again.Another reason for the subsystems not to be operating is that thesubsystem 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 theperformance of the SS7 network. You do not have to do it in theintegration 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-basedIu-PS, Iu-CS and Iur SS7 signalling stack can be used. SS7 over IPsignalling link set is configured in the RNC using IPoA (IP over ATM).


RNC Integration

Before you start

Configure ATM resources. See Creating ATM resources in RNC.

Note

In addition to the MML based configuration the IP over ATM connectioncan configured via the IP plan interface from the NetAct. The IP plansupport covers the basic support for the MML commands QMF, QRNand QKC and does not contain the OSPF configuration. For furtherdetails see IP plan interface in document RNC Operation andMaintenance.

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/physicalunit>:<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.




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

The following example configures IP addresses for interfacesconfigured 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 isjust the destination address (QRN) of IPoA connection, it is unnecessaryto create static routes.

ZQKC:<unit type>,<unit index>:[<destination IPaddress>],[<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 pointhandling>:<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)


RNC Integration

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


ZOYC:TOMGW100:C:;

6. Add SCTP association to the association set (OYA)

ZOYA:<association set name>:<unit identification>,[source port number]:<primary destination IPaddress>,[netmask length]:[secondary destination IPaddress],[netmask length]:<parameter set name>:;


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 IPaddress];


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 pointcode>,<signalling link set name>:<signalling linknumber>:<association set>;


ZNSP:NA0,100,IP100:10:TOMGW100:;

9. Create signalling route set (NRC)




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


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>,<signallingtransfer point code>;

ZNVC:<signalling network>,<signalling point code>:<signalling transfer point network>,<signallingtransfer 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.


RNC Integration

Note

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

Note

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

Steps

1. Select the Core Network tab from the RNC dialogue.

2. Fill in and check core network related parameters.

Fill in and check the core network related data, that is, SS7 signallingparameters and the identification parameter of the core networkelement. Also fill in all RANAP-related parameters. For moreinformation on parameters, see WCDMA RAN Parameter Dictionary.

Note

If there are cells under this core network that are already using theGlobal 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 thevalue of digit analysis tree from the GUI.




10.5 Creating routing objects and digit analysis for Iuinterface in RNC

Purpose

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

Note

When creating digit analysis, you must add an Authority and FormatIdentifier (AFI) before the digit sequence in order to avoid conflicts withdifferent number formats. AFI indicates the format of AESA number (thefirst 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 appropriatesignalling (broadband MTP3) has been created and the associated VC linktermination points (VCLtps) for the endpoints have been created.Furthermore, the route under which the endpoints are to be created mustallow 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 nodeidentifier>;

The ANI must be identical for all routes with the same SPC and thesame signalling network.

2. Create an endpoint group (LIC)

ZLIC:<route number>,<ep group index>:<ingressservice category>,<egress service category>;


RNC Integration

The ingress and egress service categories should always beConstant 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 bothdirections can be used in the next step.

4. Create an endpoint (LJC)

ZLJC:<ep type>,<route number>,<connection id>:<interface id>,<VPI>,<VCI>:<ownership>:[<lossratio>,<mux delay>];

The system will automatically sort this endpoint into the endpointgroup 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 theremote (PEER) network element before you can proceed to step 5. Theownership property of a certain AAL type 2 path must be different inboth ends of the connection; if this end of the connection has LOCALownership value, the other end must have PEER ownership value andvice versa. The AAL type 2 path identifier must have the samevalue 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 interfacebefore the AAL type 2 path between them can be unblocked.

ZLSU:<ANI>:<AAL type 2 path identifier>:<executiontime>;

Expected outcome

The execution printout followed by the unblocking should indicatethat both the local end and the remote end of the AAL type 2 path arein an unblocked state.




Unexpected outcome

The AAL type 2 path is still in blocked state. Repeat the unblockingcommand.

Unexpected outcome

If the remote end has not agreed unblocking,

Then

verify that the remote end is working properly and that it can bereached. Then repeat the command. As long as the remote endcannot agree to unblocking an AAL type 2 path, the system willnot select it.

6. Create digit analysis (RDC)

Create a digit analysis for a specific digit sequence. Add an AFIbefore the digit sequence in order to avoid conflicts with differentnumber formats. Check that the analysis tree has been set for the Iuinterface by using the RNC RNW object browser.

ZRDC:DIG=<digits>,TREE=<analysis tree>:ROU=<routenumber>;

Note

The address identifies the location of a network termination point. ATMEnd System Adresses (AESAs) are defined by ATM Forum. AESAconsists of Initial Domain Part (IDP) and Domain Specific Part (DSP)and it is always 40 digits long. The IDP specifies an administrationauthority which has the responsibility for allocating and assigningvalues 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 partof IDP is the actual IDP address. The leading zeroes of AESA numbersare used as padding digits to fill up the address. A trailing F(s) are usedto obtain octet (2 digits) alignment or to make the number left justified.

The leading zeroes and trailing F(s) are removed before creating a digitanalysis. This is important because, when system analyses receiveddigits a corresponding conversion is made. If digit analyses are createdotherwise, the correct, matching analysis result cannot be found.


RNC Integration

. E.164 AESA

E.164 part of E.164 AESA is the 16 digits after AFI (45). E.164part may include leading zeroes and/or a trailing F. The rest ofthe 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 isDSP part.

. ICD AESA

ICD part of ICD AESA is 4 digits after AFI (47). ICD part mayinclude F(s). The rest of the number is DSP part.

The following changes in the format of numbers must be taken intoaccount 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 Create routing objects for Iu interface

1. Create an AAL type 2 route. The route number is 13, the protocol isMessage Transfer Part Level 3, the signalling network is NA0, thesignalling point code is 24, and the AAL type 2 node identifier isAAL2HEL1.

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 isautomatically selected by the system. The termination points in thisgroup have the Constant Bit Rate service category for both ingressand egress directions.




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 allthose with service category CBR in both directions can be used inthe next step.

4. Create a VCC endpoint (VCCep) under the route 13 created in thefirst 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 2path. The AAL type 2 loss ratio is 10–3 and the AAL type 2multiplexing delay is 10 ms.

ZLJC:VC,13,11:5,12,1045:LOCAL:3,100;


Note


5. Unblock the AAL type 2 path 11. The ANI is AAL2HEL1 and theallowed waiting time for the execution of the blocking command is 18seconds.

ZLSU:AAL2HEL1:11:18;

6. Create digit analysis without charging for a digit sequence 491234 inanalysis tree 25.

ZRDC:DIG=491234,TREE=25:ROU=13;


RNC Integration

10.6 Creating routing objects and digit analysis withsubdestinations and routing policy for Iu interface

Purpose

There are two different approaches in creating digit analysis for the Iuinterface:

. creating (basic) digit analysis, where each destination has only onesubdestination

. creating digit analysis, where each destination can have more thanone subdestination.

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

Note

The system can use alternative routing only if you have purchased thisfeature.

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




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 linktermination points (VCLtps) for the endpoints have been created.

You can print the analysis and the components by using the commands ofthe RI command group.

RNCOulu

MGW / ATM SwitchGothenburg

MGW / ATM SwitchHelsinki1

MGW / ATM SwitchHamburg

MGWLondon

Address =4535840114

Digit analysis

DestinationLondon

Route 11 Route 2 Route 3

SecondaryPrimary

TREE 55, DIGITS 4535840114

50 % 50 %

Route 2

Route 11

Route 3

SubdestinationGothenburg

SubdestinationHamburg

SubdestinationHelsinki1


RNC Integration

Tip

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

Steps


ZRRC:ROU=<route number>,TYPE=AAL2:PRO=MTP3:NET=<signalling network>,SPC=<signalling pointcode>,ANI=<AAL2 node identifier>;


ZLIC:<route number>,<ep group index>:<ingressservice category>, <egress service category>;




All those VCIs with service category CBR in both directions can beused in the next step.


ZLJC:<ep type>,<route number>,<AAL type 2 pathidentifier>:<interface id>,<VPI>,<VCI>:(LOCAL|PEER):[<loss ratio>,<mux delay>];

The system will automatically place this endpoint into the endpointgroup of step 2 since their service categories match.




You must create a corresponding routing structure (steps 1-4) in theMGW (PEER) network element before you can proceed to step 5.The ownership property of a certain AAL type 2 path must bedifferent in both ends of the connection; if one end of the connectionhas LOCAL ownership value, the other end must have PEERownership value and vice versa. The AAL type 2 path identifiermust have the same value at both ends of a certain connection.


Unblock the AAL type 2 path in both RNC and MGW.


Expected outcome

The execution printout should indicate that both the local end andthe 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 theconfiguration of the AAL type 2 path is done correspondingly at theother end of the connection. Then repeat the unblocking command.

6. Create subdestinations (RDE)

ZRDE:NSDEST=<name of subdestination>:ROU=<routenumber>;

You can attach from 1 to 5 subdestinations to each destination.Repeat the command to create the required number ofsubdestinations.

7. Create a destination and define an alternative routing for thedestination (RDE)

ZRDE:NDEST=<name of destination>,ALT=<alternative>:NSDEST=<name of subdestination>;

Repeat this command separately for all the subdestinations that youwant to attach to the same destination (NSDEST).



RNC Integration

Create a digit analysis for a specific digit sequence. The specific digitsequence is the MGW AAL type 2 Service Endpoint Address of theremote end.

The number of the analysis tree must be the same as the treenumber set for the desired Virtual Media Gateway (VMGW) with theJVC command.

When creating digit analysis, you must add an Authority and FormatIdentifier (AFI) before the digit sequence in order to avoid conflictswith different number formats. AFI indicates the format of AESAnumber (the first byte of AESA). If, for example, AFI is 45 add digits 4and 5.

ZRDC:TREE=<analysis tree>,DIG=<digits>:NDEST=<nameof destination>;

9. Define the subdestination selection order and percentage calldistribution (RMM)

By setting a percentage to an alternative, you could change thesubdestination type to percentage routing. The sum of all thepercentage values entered for subdestinations must be 100.

Alternative routing can be chosen by giving 'A' instead of percentagevalue. This sets the subdestination type to alternative routing.

If you want to use alternative routing for the subdestinations, do notdefine new subdestination type and percentages (by RMM).Alternative routing is the default routing policy.

ZRMM:NDEST=<destination name>:SELO=<selectionorder>,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 withpercentage routing

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




1. Create an AAL type 2 route between RNC and MGW. The routenumber is 11, the protocol is Message Transfer part 3, the signallingnetwork is NA0, the signalling point code is 701, and the identifier ofthe 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 isautomatically selected by the system. The termination points in thisgroup have the Constant Bit Rate service category for both ingressand egress directions.

ZLIC:11,1:C,C;

3. Check that there is a free VCLtp.


Note that you can check all the VPIs available. All the VCIs withservice category CBR in both directions can be used in the nextstep.

4. Create an endpoint of VC level (VCCep) under route 11 created inthe first step. AAL type 2 path is 5. It is based on the TPI withinterface id 2, VPI 1, and VCI 33. The current network element ownsthe AAL type 2 path. The AAL type 2 loss ratio is 10–3 and the AALtype 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 endpointgroup of step 2 since their service categories match.

You must create a corresponding routing structure (steps 1-4) in theMGW (PEER) network element before you can proceed to step 5.The ownership property of a certain AAL type 2 path must bedifferent in both ends of the connection; if one end of the connectionhas LOCAL ownership value, the other end must have PEERownership value and vice versa. The AAL type 2 path identifiermust 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 andthe allowed waiting time for the execution of the blocking commandsis 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:


RNC Integration

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 createdseparately by following steps 1 to 5 above.

7. Create the destination LONDON, define three subdestinations for itand define HELSINKI1 as the primary routing subdestination,GOTHENBURG as the first alternative and HAMBURG as thesecond 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 analysistree 55.

ZRDC:DIG=4535840114,TREE=55:NDEST=LONDON;

9. Create the subdestination selection order and percentage calldistibution.

Define the selection order and percentage call distribution values ofrouting alternatives so that the primary subdestination usesalternative routing and the first and the second alternatives usepercentage routing. The overflow traffic of the primary alternative isshared 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 calldistribution or alternative routing for these, you can modify these settingswith the RMM command.





RNC Integration

11 Creating Iu-PS interface (RNC-SGSN)



11.2 Configuring signalling channels

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

11.3 Configuring Iu-PS parameters of RNC

Before you start


Note

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

Note




Creating Iu-PS interface (RNC-SGSN)

Steps


2. Fill in and check core network related parameters.

Fill in and check the core network related data, that is, SS7 signallingparameters and the identification parameter of the core networkelement. Also fill in all RANAP-related parameters. For moreinformation on parameters, see WCDMA RAN Parameter Dictionary.

Note

If there are cells under this core network that are already using theGlobal 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 interfacebetween 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 andIP basic resources can be configured via the IP and ATM plan interfacefrom the NetAct. The ATM plan interface contains the basic support forATM interface, VPLtp and VCLtp creation while the IP plan supportcovers the basic support for the MML commands QMF, QRN and QKC.The IP plan support does not cover the OSPF configuration or IP QoSconfiguration.

For more information on the IP plan interface, see IP plan interface indocument RNC Operation and Maintenance.

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


RNC Integration

Steps

1. Interrogate the states of the units in the system (USI)

Check that the units for which you are going to create networkinterfaces 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 perGTPU) according to instructions in Configuring IP over ATMinterfaces. Set the value of the encapsulation method parameter toLLC/SNAP.

If you want to dedicate a GTPU for real-time IP traffic, set the valueof usage parameter to IPOART (this is an optional feature) for all IPoAinterfaces 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 defaultroute.

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

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 macaddress>);

4. Create other static routes, if needed

For IPv4:




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

For IPv6:

ZQ6C:<unit type>,<unit index>:<destination IPaddress>,[<prefix length>]:[<next hop type>]:<address type>:(IP=<ip address> | MAC=<link level macaddress>);

5. Create OSPF configuration, if necessary

Currently, OSPF only supports IPv4. If you want to use OSPF routingon 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 theloopback address.

ZQKU:<unit type>,<unit index>:<redistributetype and identification>:<metric>;

c. Configure the area(s) that include also the neighbouringrouters.


d. Configure an interface for that area.

ZQKF:<unit type>,<unit index>:<interfacespecification>:<area identification>:[<hellointerval>]:[<router dead interval>]:[<ospfcost>]:[<election priority>]:[<passive>]:[<authentication> | <authentication>,<password>];

6. Create QoS DiffServ configuration (GTPU), if needed (withservice terminal extension)

It is also possible to configure QoS DiffServ traffic classification toGTPU units. The main function for IP QoS DiffServ is to assure thatreal 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 realtime or non-real time and processes the traffic with the desired ratio.The configuration is done with the service terminal extensionQMDSTEGX in OMU.


RNC Integration

An example of the mapping between DSCP to traffic class ispresented 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 RT

001010,

001100,

001110

RT

010010,

010100,

010110

NRT

011010,

011100,

011110

NRT

100010,

100100,

100110

NRT

000000 NRT

If you decided to use QoS DiffServ for the Iu-PS interface, make theconfiguration 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 thedesired 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




SGSN unit

This example shows how to configure the Iu-PS interface between theRNC and SGSN using two STM-1 interfaces in both RNC and SGSN. Inthe example, four GTPU units are deployed to handle the Packet SwitchedRadio Access Bearers in the RNC in load sharing mode. Each GTPU islogically connected to one of the SGSN units, GPLCs. Two IP subnets areused:

. 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.

Figure 9. ATM virtual channel connections and IP addresses with each GTPUconnected to one GPLC unit

1. Create ATM resources.

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

10.1.1.10AA1GTPU-0

10.1.1.11AA1GTPU-1

10.1.2.12AA2GTPU-2

10.1.2.13AA2GTPU-3

10.1.1.1

10.1.2.1

10.2.0.0

10.3.0.0

GPLC1

GPLC2

RNC SGSN

VPI=0, VCI=40

STM-1 line #1

STM-1 line #2

VPI=0, VCI=42

VPI=0, VCI=43

= subnet 10.1.1.0/32

= subnet 10.1.2.0/32

VPI=0, VCI=41


RNC Integration

. STM-1 ATM interface (with interface ID 1). This interface isconnected to SGSN (GPLC-1) via a direct physical connectionor 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.



. 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;


b. Create IP over ATM interfaces connected to subnet 10.1.2.1/32 (GPLC-2).



3. Assign IP addresses to the network interfaces.

a. Configure interfaces connected to subnet 10.1.1.1/32 (GPLC-1).

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;

4. Create static routes for GTPUs.

With the following default routes, all traffic is forwarded to the GPLCunit in the SGSN.

ZQKC:GTPU,0::10.1.1.1,:PHY;




Example IP configuration for Iu-PS with GTPUs connected to both




SGSN units

This example shows how to configure the Iu-PS interface between theRNC and SGSN using two STM-1 interfaces in RNC and SGSN. In thisexample, four GTPU units are deployed to handle the Packet SwitchedRadio Access Bearers in RNC in load sharing mode. Each GTPU islogically connected to both GPLC units in the SGSN so that even if onelink fails, the interface capacity between the RNC and SGSN remains thesame. Note that the same redundancy can be achieved by using OSPFinstead of static routing (see the next example: configuring Iu-PS whenOSPF 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 ofthe GPLC units (10.2.0.1 and 10.3.0.1) even if one of the interfaces of aGTPU fails.


RNC Integration

Figure 10. ATM virtual channel connections and IP addresses with GTPUsconnected to both GPLC units


Create the following ATM configuration (for instructions, seeCreating 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 connectionor via the SDH transmission network.


. In ATM interface 1, four VCLtps with VPI=0 and VCI=40...43.




RNC SGSN

VPI=0, VCI=41

VPI=0, VCI=40

VPI=0, VCI=43

VPI=0, VCI=42

STM-1 line #1

STM-1 line #2

VPI=0, VCI=41

VPI=0, VCI=40

VPI=0, VCI=43

VPI=0, VCI=42

= subnet 10.2.0.1/32

= subnet 10.3.0.1/32

= primary route

10.3.0.1

GPLC-2

10.1.2.1

AA0

AA1GTPU-0

AA0

AA1GTPU-2

10.1.2.10 10.3.0.1

10.1.1.10 10.2.0.1

10.1.1.12 10.2.0.1

10.1.2.12 10.3.0.1

AA0

AA1GTPU-1

10.1.1.11 10.3.0.1

10.1.2.11 10.2.0.1

AA0

AA1GTPU-3

10.1.1.13 10.3.0.1

10.1.2.13 10.2.0.1

10.1.1.1

10.2.0.1

GPLC-1
















Note that the destination address of the IP over ATM interface doesnot have to be the IP address of the next hop. The IP address anddestination IP address of the IP over ATM interface can be indifferent subnets.


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 (GPLC-2).

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;

4. Create default static routes for GTPUs.





There should be one connection and route between GPLC-1 andGPLC-2.


RNC Integration

Example Configuring Iu-PS when OSPF is in use

This example shows how to configure the Iu-PS interface between theRNC and SGSN using OSPF for routing. When OSPF is in use and a linkfails, the user plane traffic is switched to the working link.

Figure 11. Iu-PS configuration with OSPF in use


Create the following ATM configuration (for instructions, seeCreating 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 connectionor via the SDH transmission network.



RNC SGSN

VPI=0, VCI=41

VPI=0, VCI=40

VPI=0, VCI=43

VPI=0, VCI=42

STM-1 line #1

STM-1 line #2

VPI=0, VCI=41

VPI=0, VCI=40

VPI=0, VCI=43

VPI=0, VCI=42

= subnet 10.2.0.1/32

= subnet 10.3.0.1/32

= primary route

10.1.2.110.3.0.1

GPLC-2

10.1.1.1

10.2.0.1

GPLC-1

AA1GTPU-0

AA0

AA1GTPU-1

AA0

AA1

GTPU-2

AA0

AA1

GTPU-3

10.1.2.10 10.1.2.1

AA0 10.1.1.10 10.1.1.1

10.1.1.11 10.1.1.1

10.1.2.11 10.1.2.1

10.1.1.12 10.1.1.1

10.1.2.12 10.1.2.1

10.1.1.13 10.1.1.1

10.1.2.13 10.1.2.1

LO0 10.1.1.2

LO0 10.1.1.3

LO0 10.1.1.4

LO0 10.1.1.5



















Note that the destination address of the IP over ATM interface doesnot have to be the IP address of the next hop. The IP address anddestination IP address of the IP over ATM interface can be fromdifferent subnets.


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 (GPLC-2).

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;





RNC Integration

4. Create the OSPF configuration.

a. Configure the area(s) that include also the neighbouringrouters.

ZQKE:GTPU,0:0.0.0.1;




b. Configure two interfaces for that area. The values forparameters area identification, hello interval androuter dead interval must be the same as in the SGSN.

You can select AA0 or AA1 as the primary route for user trafficby giving different ospf costs. The interface with lower cost willbe 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 theloopback 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;

Example QoS DiffServ configuration for Iu-PS with each GTPUconnected to one SGSN unit

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




are non-real time(nrt). Real time (rt) and non-real (nrt) packet ratio will beset with value 8 by default. This means that 8 real time packets areprocessed with one non-real time packet. If the number of real timepackets is less than 8, the non-real time packets will be processed after allthe 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


RNC Integration

12 Creating Iur interface (RNC-RNC)



12.2 Configuring signalling channels

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

12.3 Configuring Iur parameters of RNC

Before you start

The Iur interface must be created for each neighbouring RNC. Themaximum amount of RNC Iur interfaces is 32.


Steps

1. Select the neighbouring RNCs tab from the RNC dialogue.

2. Fill in and check the parameters of the neighbouring RNCs.

Fill in and check the identification parameters of the neighbouringRNCs as well as the SS7 related signalling parameters. For moreinformation on parameters, see WCDMA RAN Parameter Dictionary.

3. Check the value of the digit analysis tree.



Creating Iur interface (RNC-RNC)

Note

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

12.4 Creating routing objects and digit analysis for Iurinterface in RNC

Purpose

This procedure describes how to create routing objects and digit analysesfor the Iur interface with MML commands. The analysis tree used forconfiguring the Iur interface is set by using the RNC RNW object browserapplication.

Note

When creating digit analysis, you must add an Authority and FormatIdentifier (AFI) before the digit sequence in order to avoid conflicts withdifferent number formats. AFI indicates the format of AESA number (thefirst 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 appropriatesignalling (broadband MTP3) has been created and the associated VC linktermination points (VCLtps) for the endpoints have been created.Additionally, the route under which the endpoints are to be created mustallow the type of the endpoints.

Steps


ZRRC:ROU=<route number>,TYPE=AAL2:PRO=<protocol>:NET=<signalling network>,SPC=<signalling pointcode>,ANI=<aal2 node identifier>;

The ANI is to be identical for all routes with the same SPC and thesame signalling network.



RNC Integration

ZLIC:<route number>,<ep group index>:<ingressservice category>,<egress service category>;




Out of these VCIs all these with the service category CBR in bothdirections can be used in the next step.


ZLJC:<ep type>,<route number>,<connection id>:<interface id>,<VPI>,<VCI>:<ownership>:[<lossratio>,<mux delay>];


Repeat steps 1-4 in the remote RNC before continuing with step 5.

Note



The endpoints must have been created at both ends of the interfacebefore the AAL type 2 path between them can be unblocked.


Expected outcome




The execution printout followed by the unblocking should indicatethat both the local end and the remote end of the AAL type 2 path arein unblocked state and the state has been agreed with the remoteend.

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 bereached. Then repeat the command. As long as the remote endcannot agree to unblocking an AAL type 2 path, the system willnot select it.


Create a digit analysis without charging for a specific digit sequence.Add an AFI before the digit sequence in order to avoid conflicts withother number formats. The analysis tree has been set for the Iurinterface by using the RNC RNW object browser.

ZRDC:DIG=<digits>,TREE=<analysis tree>:ROU=<routenumber>;


RNC Integration

Note

The address identifies the location of a network termination point. ATMEnd System Adresses (AESAs) are defined by ATM Forum. AESAconsists of Initial Domain Part (IDP) and Domain Specific Part (DSP)and it is always 40 digits long. The IDP specifies an administrationauthority which has the responsibility for allocating and assigningvalues 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 partof IDP is the actual IDP address. The leading zeroes of AESA numbersare used as padding digits to fill up the address. A trailing F(s) are usedto obtain octet (2 digits) alignment or to make the number left justified.

The leading zeroes and trailing F(s) are removed before creating a digitanalysis. This is important because, when system analyses receiveddigits a corresponding conversion is made. If digit analyses are createdotherwise, 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.164part may include leading zeroes and/or a trailing F. The rest ofthe 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 isDSP part.

. ICD AESA

ICD part of ICD AESA is 4 digits after AFI (47). ICD part mayinclude F(s). The rest of the number is DSP part.

The following changes in the format of numbers must be taken intoaccount 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 thenumber (F digits are removed from digits 1-4).

. Example: 47123F1234 --> 471231234

Example Create routing objects and digit analysis for Iur interface

1. Create an AAL type 2 route between two RNCs. The route number is13, the protocol is Message Transfer Part Level 3, the signallingnetwork is NA0, the signalling point code is 35, and AAL type 2 nodeidentifier 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 isautomatically selected by the system. The termination points in thisgroup have the Constant Bit Rate service category for both ingressand 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 allthose with service category CBR in both directions can be used inthe next step.

4. Create an endpoint of VC level (VCCep) under the route 13 createdin 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 2path. The AAL type 2 loss ratio is 10–3 and the AAL type 2multiplexing delay is 10 ms.

ZLJC:VC,13,11:5,12,1045:LOCAL:3,100;



RNC Integration

Note


5. Unblock the AAL type 2 path 11. The ANI is AAL2HEL1 and theallowed waiting time for the execution of the blocking command is 18seconds.

ZLSU:AAL2HEL1:11:18;

6. Create digit analysis without charging for a digit sequence 491234 inanalysis tree 24.

ZRDC:DIG=491234,TREE=24:ROU=13;





RNC Integration

13 Creating Iu-BC interface (RNC-CBC)



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 BroadcastProtocol (SABP) is in use.

Note

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

Note




Creating Iu-BC interface (RNC-CBC)

Steps


2. Fill in and check CBC-related parameters.

Fill in and check CBC-related data, that is, IP addresses and GlobalPLMN IDs. For more information on parameters, see WCDMA RANParameter Dictionary.

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

Purpose

The purpose of this procedure is to configure IP for the Iu-BC interfacebetween the RNC and the Cell Broadcast Centre (CBC).

All user data and signalling (SABP) traffic goes through the same InterfaceControl and Signalling Unit (ICSU). You must configure one VCC and onestatic route towards the CBC for the selected ICSU. Static routes areneeded only in the case when the CBC is not directly connected to theRNC (for example, router is connected between the RNC and the CBC). Incase of ICSU switchover, IP over ATM interface, IP address and staticroutes will move to the new unit.

Before you start

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

Steps

1. Check the selected ICSU unit towards the CBC

The RNC allocates the ICSU unit for the CBC when the CBCreference data is created to the RNC configuration. You can checkthe selected ICSU (logical address for the selected ICSU) from theRNC RNW Object Browser's RNC dialog and core network tab.

For further information of the parameter please refer to the WCDMARAN04 Parameter Dictionary documentation: RNC - CBList -CBCItem - ICSUforCBC.


RNC Integration

Check the ICSU-id based on the logical address selected towardsthe CBC.

ZUSI:ICSU;

2. Create the IP over ATM interface to selected ICSU

Create the IP over ATM interface to selected ICSU towards the CBCaccording 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 (oneseparate IP over ATM interface for each used ICSU) towards theCBC. In this case, only selected ICSU unit is sending RNCoriginated Restart and Failure messages towards the CBC. TheCBC must be configured to send data to different IP addresses, thatis, to different ICSU units.

When assigning an IP address to the ICSU unit, assign a logical IPaddress to the unit by giving value L to the IP address typeparameter.

If you want to configure several IP over ATM interfaces towards theCBC (distributing incoming traffic between several ICSU units), givethe network interface parameter a different value in all units,value L to the IP address type parameter, and assign a different IPaddress to each unit.

The destination IP address is the address of the router interfaceor 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 routewith route type "LOG" for selected ICSU to the IP address of therouter terminating IP over ATM PVCs. Static routes are needed onlyin the case when the CBC is not directly connected to the RNC.

Note

Only static routes can be configured for ICSU units. Static routes areonly required for ICSUs if any of the IP packets have a differentdestination address than the IP address of the CBC (for example, if arouter is used between the RNC and CBC), and they are to betransferred via the VCC.




For IPv4:

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

Note

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

For IPv6:

ZQ6C:<unit type>,<unit index>:[<destination IPaddress>],[<prefix length>]:[<next hop type>]:<address type>:(IP=<ip address> | MAC=<link level macaddress>);

Example Configuring IP for Iu-BC through ICSU units

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


RNC Integration

Figure 12. Example of IPv4 configuration for Iu-BC

The following examples show how to configure the IP for the Iu-BCinterface between the RNC and the CBC. The ICSU-0 is selected to beused towards the CBC. The Iu-BC PVCs are configured to the STM-1interface between the RNC and the MGW. The IPoA PVCs are terminatedin a router. The PVCs can also be terminated in the CBC, if it is located inthe same site.

For IPv4 case:

1. Create ATM resources as instructed in Creating ATM resources inRNC in ATM Resource Management.

2. Create IP over ATM interfaces connected to subnetwork 10.1.1.1/32to selected ICSU.

ZQMF:ICSU,0,L:AA1:1,0,40:1,IPOAUD;

ICSU-1

ICSU-2

ICSU-18

...

RNC

NIS

STM-1

MGW

VPcross

connects

NIS

VPI=x

NIS

VPI=y

Router terminatingIP over ATM PVCs(can also be anextra ATM Interface)

anymedia

Core siteRNC site

ICSU-010.1.1.1

CBC

subnet 10.1.1.0/32

10.1.1.200




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 routerterminating 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 theIPv4 address "10.1.1.200" with IPv6 address "3FFE:1200:3012:C020:580:8FFF:FE7A:4BB4".

1. Create ATM resources as instructed in Creating ATM resources inRNCin ATM Resource Management.

2. Create IPv6 over ATM interfaces connected to subnetwork toselected 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 routerterminating IP over ATM PVCs. A static route is needed for eachICSU because during the ICSU switchover static route is notswitching to the new unit.

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


...


RNC Integration


RNC Integration

14 Configuring radio network objects

14.1 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 inWCDMA cell definitions.

Steps

1. Select Object → New → Freq. Meas. Control → intra-freq./inter-freq./inter-system.

2. Fill in parameters.

For information on parameters, see WCDMA RAN ParameterDictionary.


Expected outcome

The data is sent to the RNC RNW database. An OperationInformation dialogue appears indicating the status of the operationand possible errors.

4. Check the outcome of the operation and click OK to close theOperation Information dialogue.

Expected outcome

A new FMC object is created.

Unexpected outcome



Configuring radio network objects

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

14.2 Creating handover path

Purpose

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

Steps

1. Select Object → New → Handover Path →intra-freq./inter-freq./inter-system.




Expected outcome

The data is sent to the RNC RNW database.

An Operation Information dialogue appears indicating the status ofthe operation and possible errors.


Expected outcome

A new handover path object is created.

Unexpected outcome

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


RNC Integration

14.3 Creating a WCDMA BTS site

Purpose

A new logical WBTS object is created in order to manage a physicalWCDMA 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 systemdefaults and the other is to use a reference site. The step-by-stepinstructions 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 usedin order to speed up the WBTS creation procedure. You still have tofill in identification information for the WCDMA BTS and otherrequired parameters for which there are no default values. You arenot limited to default values; once a parameter has been given adefault 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 witha 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 arecopied from the reference site to the new one. You still have tofill in values for those required parameters which could not becopied from the reference WBTS. You are not limited to thecopied values; once a parameter value has been copied fromthe reference WBTS, you can change it if necessary. Whenyou use a reference WBTS site to set up a new site, thetopology of the reference site (WCDMA cells and theirparameters) is also copied to the new site as an initialconfiguration. The new site does not have to have the samenumber of cells as the reference site, that is, the user may addand delete cells as needed.




Note

The logical objects in the RNC RNW database are hierarchically relatedto each other, and the hierarchy dictates the order in which it is possibleto create new objects. WCEL objects are always created under acertain WBTS object, never independently. However, the user does nothave 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 byadding WCEL objects to a WBTS object.

Note

A frequency measurement control (FMC) object has to be created inadvance, 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. If you want to, select a reference WBTS site.



Note

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

4. If you want to add a WCDMA cell

Then


RNC Integration

Click Add WCEL.

Fill in parameters. For information on parameters, see WCDMA RANParameter Dictionary.

Note

If you add WCDMA cells in a locked state, the WCDMA BTS is nottaken into active traffic before the WCDMA cell states are changed toan unlocked state. For more information, see Locking and unlocking aWCDMA cell.

5. If you want to remove a WCDMA cell

Then

Select WCEL from the WBTS Site tree.

Click Remove WCEL.


Expected outcome


A Site Creation Confirmation dialogue appears.


Expected outcome

The new WBTS site is created. The WCDMA BTS can be taken intoactive traffic once it has been successfully connected to the logicalCOCO object (that is, transmission resources).

Unexpected outcome

If the user gives a reference to a COCO object, the reference shouldonly point to a COCO object which is not in use at the time. In otherwords, no reference to a COCO object which is already related to aWBTS will be made.




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

14.4 Creating a WCDMA cell

Purpose

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

Before you start

WCEL objects can only be created under a WBTS. The WCDMA cellremains locked and is not used in active traffic until you have changed itsstate 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 existingWCDMA cell as reference.

a. Select the WCDMA cell whose parameters should be used inthe new cell.

b. Select Object → Use as reference.

c. Select the WCDMA BTS to which the WCDMA cell should becreated.


a. Browse through the parameter tabs and fill in every mandatoryparameter.

b. Specify FMCS, FMCI and FMCG for real time, non-real timeand HSDPA separately on the HC tab. Note that FMCG canonly be defined if the inter-system handover feature isactivated and HSDPA FMCs only if the HSDPA feature hasbeen activated.


RNC Integration



4. Select Yes from Automatic Unlock Confirmation dialogue, if youwant to create the cell unlocked.

Expected outcome




Expected outcome

A new WCDMA cell is created.

Unexpected outcome

Any errors are displayed in the Operation Information dialogue. If thecreation fails, you are asked if you want to return to the creation dialogueto modify the parameters and try again. You can also click Cancel tocancel 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 todefine a new neighbouring cell. Adjacencies for cells controlled by thesame RNC are called internal adjacencies.

Before you start

Note

The ADJG object can only act as an external adjacency.




Note

There is a limitation in sending neighbour cell information in systeminformation block (SIB) type 11 and 12. SIB11 and SIB12 messagescan contain information on a maximum of 96 cells, but the physical sizeof SIB data (no more than 3552 bits) has capacity only for 47 cells whenall used optional information elements in SIB11 are in use and 35 cells ifHCS is used.

If the system information data exceeds 3552 bits, the scheduling of thesystem information blocks fails. The cell is blocked by the system andan alarm 7771 WCDMA CELL OUT OF USE (BCCH scheduling error)is reported for the cell.

Steps

1. Select a parent WCDMA cell for the adjacent WCDMA cell.

2. Select Object → New → Adjacency → intra-freq./inter-freq.

Expected outcome

A New ADJS/ADJI dialogue appears.


Steps

a. Select the target WCDMA cell from the Available cells list.

Target UTRAN cell identity and other target cell relatedparameters are automatically defined. You can also insertTarget UTRAN Cell identity of the target cell as well asidentification parameters for the RNC manually.

b. Specify whether the adjacency should be bidirectional ornot.

The default value is outgoing. The selected WCDMA cell isacting as source cell in case of adjacencies.

c. Specify handover paths for real time, non-real time andHSDPA separately.


RNC Integration

Note

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

d. Specify whether the adjacency should be included in thesystem information messages or not.

All adjacent cells are used in measurement control even if theadjacency is not included in the system information.

Further information



Expected outcome




Expected outcome

If you chose to create a bidirectional adjacency, both an outgoing and anincoming adjacency are created; otherwise only an outgoing adjacency iscreated.

Unexpected outcome





14.6 Creating an external adjacency for a WCDMA cell

Purpose

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

Before you start

Note

There is a limitation in sending neighbour cell information in systeminformation block (SIB) type 11 and 12. SIB11 and SIB12 messagescan contain information on a maximum of 96 cells, but the physical sizeof SIB data (no more than 3552 bits) has capacity only for 47 cells whenall used optional information elements in SIB11 are in use and 35 cells ifHCS is used.

If the system information data exceeds 3552 bits, the scheduling of thesystem information blocks fails. The cell is blocked by the system andan alarm 7771 WCDMA CELL OUT OF USE (BCCH scheduling error)is reported for the cell.

Steps

1. Select a parent WCDMA cell for the adjacent WCDMA cell.

2. Select Object → New → Adjacency → intra-freq./inter-freq./inter-system.

Expected outcome

A New ADJS/ADJI/ADJG (optional) dialogue appears.


Steps

a. Insert the Target Cell identity of the target cell as well asidentification parameters for the external RNC manually.

b. For external adjacencies, define only the outgoingadjacencies.


RNC Integration

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 thesystem information messages or not.

All adjacent cells are used in measurement control even if theadjacency is not included in the system information.

Further information



Expected outcome




Expected outcome

An outgoing adjacency is created.

Unexpected outcome






RNC Integration

15 Integrating location services

15.1 Overview of location services

RAN Location Services (LCS) provides the means to identify and reportthe current location of a UE using geographical co-ordinates.

In addition to the RNC-centric cell-based locationing, the Nokia RNCimplementation of the location services includes two different interfaces,Iupc and ADIF, to the external LCS server for additional locationingmethods. Iupc is a 3GPP standard interface between an RNC and aStandalone Serving Mobile Location Centre (SAS). ADIF is a proprietaryinterface between an RNC and an A-GPS Server.

Iupc data transmission is based on SIGTRAN (M3UA/SCTP), and ADIFdata transmission is based on TCP. RNC connectivity is based on Ethernetin both Iupc and ADIF.

Note

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

15.2 Creating TCP/IP configuration in RRMU units

15.2.1 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 itemkit has been installed.



Integrating location services

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

Figure 13. Example of IP network configuration between an RNC and aredundant A-GPS Server

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

Figure 14. Example of IP network and signalling configuration between an RNCand a SAS

IntermediateIP Network

10.10.1.1/24

10.10.1.2/24 10.10.2.2/24

RRMU

EL0 EL1

10.10.2.1/24

10.10.4.1/24

A-GPSServer 2

10.10.3.1/24

A-GPSServer 1

Primary datapath Secondary datapath

10.10.3.2/24 10.10.4.2/24


10.10.1.1/24

10.10.1.2/24 10.10.2.2/24

RRMU

EL0 EL1

10.10.2.1/24

10.10.4.1/2410.10.3.1/24


10.10.3.2/24 10.10.4.2/24

Network = NA0SPC = 111


SAS


RNC Integration

In Figures Example of IP network configuration between an RNC and aredundant A-GPS Server and Example of IP network and signallingconfiguration between an RNC and a SAS, the RRMU unit is connected totwo different IP subnetworks. The RRMU’s EL0 interface is connected tothe 10.10.1.0 /24 subnetwork, and the EL1 interface is connected to the10.10.2.0 /24 subnetwork.

Static IP routes are configured so that there are two different logicaldatapaths between the RRMU unit and the A-GPS Servers or SAS. Thehighest possible connection redundancy is achieved when the datapathsare transported through different network paths between the RRMU andthe A-GPS Servers or SAS.

When the ADIF interface is used, all traffic to the A-GPS Server 1originates from the RRMU’s EL0 interface, and all traffic to the A-GPSServer 2 originates from the RRMU’s EL1 interface.

When the Iupc interface is used, all traffic to the first network interface ofthe SAS originates from the RRMU’s EL0 interface and all traffic to thesecond network interface of the SAS originates from the RRMU’s EL1interface.

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 itemkit has been installed.

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




Figure 15. Example of IP network configuration between an RNC and aredundant A-GPS Server

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

Figure 16. Example of IP network and signalling configuration between an RNCand a SAS


10.10.1.1/24

10.10.1.2/24 10.10.2.2/24

RRMU

EL0 EL1

10.10.2.1/24

10.10.4.1/24

A-GPSServer 2

10.10.3.1/24

A-GPSServer 1


10.10.3.2/24 10.10.4.2/24


10.10.1.1/24

10.10.1.2/24 10.10.2.2/24

RRMU

EL0 EL1

10.10.2.1/24

10.10.4.1/2410.10.3.1/24


10.10.3.2/24 10.10.4.2/24



SAS


RNC Integration

In Figures Example of IP network configuration between an RNC and aredundant A-GPS Server and Example of IP network and signallingconfiguration between an RNC and a SAS, the RRMU unit is connected totwo different IP subnetworks. The RRMU’s EL0 interface is connected tothe 10.10.1.0 /24 subnetwork, and the EL1 interface is connected to the10.10.2.0 /24 subnetwork.

Static IP routes are configured so that there are two different logicaldatapaths between the RRMU unit and the A-GPS Servers or SAS. Thehighest possible connection redundancy is achieved when the datapathsare transported through different network paths between the RRMU andthe A-GPS Servers or SAS.

When the ADIF interface is used, all traffic to the A-GPS Server 1originates from the RRMU’s EL0 interface, and all traffic to the A-GPSServer 2 originates from the RRMU’s EL1 interface.

When the Iupc interface is used, all traffic to the first network interface ofthe SAS originates from the RRMU’s EL0 interface and all traffic to thesecond network interface of the SAS originates from the RRMU’s EL1interface.

The IP addresses in the following examples are only valid for theconfiguration examples shown in Figures Example of IP networkconfiguration between RNC and redundant A-GPS Server and Example ofIP 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 theor 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.




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

15.3 Configuring ESA24 switches

15.3.1 Configuring ESA24-0

Before you start

It is recommended that you configure the ESA24 switches using a serialcable connection instead of telnet connection to avoid the loss ofconnectivity to the ESA24.

It is recommended that the ESA24 operating system (BiNOS) version is3.14.7 or higher.

ESA24-0 is physically located in subrack 1, slot 12 and ESA24-1 is locatedin subrack 2, slot 6.

In the following example, it is assumed that the ETH0 (1/1/1) ports of theESA24 switches are connected to Cisco Ethernet switches, which supportthe new standard-compatible implementation of the IEEE 802.1s MSTPprotocol and are configured respectively on MSTP and VLAN level. Formore information, see Configuring external IP routers and switches for A-GPS use in RNC, dn0736868, available in NOLS.

The VLAN IDs and names in the following examples apply only to anEthernet network, which is built for A-GPS LCS use. In other cases, theVLAN IDs and other parameters may overlap with existing parameters andcause Ethernet connectivity problems.

Steps

1. Connect to ESA24-0 using a serial cable.

2. Log in to ESA24-0 using the default password “nokia” or thenew password if the password has been changed.


Password:

3. Switch to privileged mode.

ESA24-0>enable


RNC Integration

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



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


11. Add ports 1/1/7 and 1/1/8 to VLAN “LCS1” in “untagged” modeand exit.

ESA24-0(config-vlan LCS1)#add ports 1/1/7 untagged


ESA24-0(config-vlan LCS1)#exit








13. Add ports 1/1/1 and 1/1/6 to VLAN “LCS2” in “tagged” modeand exit.





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


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)#exit

ESA24-0(config vlan)#exit


RNC Integration

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


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




ESA24-0(config-if 1/1/1)#exit

ESA24-0(config)#

23. Switch to interface 1/1/2 configuration mode, modify MSTP linktype and default VLAN, then exit.


ESA24-0(config-if 1/1/2)#mstp edge-port



ESA24-0(config)#






ESA24-0(config)#






ESA24-0(config)#



RNC Integration





ESA24-0(config)#






ESA24-0(config)#






ESA24-0(config)#

29. Switch to interface 1/1/6 configuration mode, modify MSTP linktype, MSTP path cost, and default VLAN, then exit.



ESA24-0(config-if 1/1/6)#mstp 0 path-cost 400000






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 serialcable connection instead of telnet connection to avoid the loss ofconnectivity to the ESA24.

It is recommended that the ESA24 operating system (BiNOS) version is3.14.7 or higher.

ESA24-0 is physically located in subrack 1, slot 12 and ESA24-1 is locatedin subrack 2, slot 6.

In the following example, it is assumed that the ETH0 (1/1/1) ports of theESA24 switches are connected to Cisco Ethernet switches, which supportthe new standard-compatible implementation of the IEEE 802.1s MSTPprotocol and are configured respectively on MSTP and VLAN level. Formore information, see Configuring external IP routers and switches for A-GPS use in RNC, dn0736868, available in NOLS.

The VLAN IDs and names in the following examples apply only to anEthernet network, which is built for A-GPS LCS use. In other cases, theVLAN IDs and other parameters may overlap with existing parameters andcause Ethernet connectivity problems.


RNC Integration

Steps

1. Connect to the ESA24-1 using a serial cable.

2. Log in to ESA24-1 using the default password “nokia” or thenew password if the password has been changed.


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






8. Add a new VLAN with the name “OAM” and id number “30”.

ESA24-1(config vlan)#create OAM 30







10. Add ports 1/1/1 and 1/1/6 to VLAN “LCS1” in “tagged” modeand exit.








12. Add ports 1/1/1 and 1/1/6 to VLAN “LCS2” in “tagged” mode.



13. Add ports 1/1/7 and 1/1/8 to VLAN “LCS2” in “untagged” modeand exit.





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.




RNC Integration

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)#exit

ESA24-1(config vlan)#exit

ESA24-1(config)#

17. Switch to protocol configuration mode.

ESA24-1(config)#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


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




ESA24-1(config)#

21. Switch to interface 1/1/1 configuration mode.


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)#






ESA24-1(config)#






ESA24-1(config)#


RNC Integration






ESA24-1(config)#






ESA24-1(config)#






ESA24-1(config)#









ESA24-1(config)#

29. Switch to interface 1/1/6 configuration mode, modify MSTP linktype, MSTP path cost, and default VLAN, then exit.



ESA24-1(config-if 1/1/6)#mstp 0 path-cost 400000



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#


RNC Integration

15.4 Activating location services

15.4.1 Activating the Location Services feature

Summary

Location Services, Iupc interface, and ADIF interface are optional features.

Steps

1. Open the RNC RNW Object Browser application.

2. Select and open the RNC object.

3. For the “LCS functionality” parameter, select value “Enabled”from the drop-down list.

4. Click "OK".

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 FigureExample of IP network configuration between RNC and redundant A-GPSServer in Overview of TCP/IP configuration in RRMU units.

You have to create a WSMLC object in the RNC object before you canconfigure the ADIF parameters of the WSMLC. For more information oncreating a WSMLC object, see Creating WSMLC object.

Steps

1. Open the RNC RNW Object Browser application.

2. In the RNC dialogue box, open the WSMLC tab.

3. For the "UE based AGPS" option, select "Enabled" from thedrop-down list.




4. For the "Preferred A-GPS method" option , select "UE BasedMethod" from the drop-down list.

5. For the "LCS Interface" option, select value "ADIF" from thedrop-down list.

6. Under “A-GPS Data Server”, type “10.10.3.2” in the “IPaddress” field and “43460” in the “Data Port ID” field.

7. Under “Redundant A-GPS Data Server”, type “10.10.4.2” in the“IP address” field and “43460” in the “Data Port ID” field.

8. Click “OK” to save the configuration.

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 stateand that the RNC’s own signalling point and SCCP service have alreadybeen configured.

The IP addresses, signalling network indicators, and signalling point codes(SPCs) in the following example are only valid for the exampleconfiguration shown in Figure Example of IP network and signallingconfiguration between RNC and SAS in Overview of TCP/IP configurationin RRMU units.

Refer to your IP and SS7 network plans of the RNC and the SAS inquestion for the correct IP addresses, signalling network indicators, andSPCs used in your configuration.

Note that the IP and SS7 values are SAS-specific and may need to bechanged 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:;


RNC Integration

d. Enable “ASP messages in IPSP”.

ZOYM:PCAP:IPSP=Y:;

e. Disable the dynamic routing key registration.

ZOYM:PCAP:REG=N:;

f. Set the value of the first datastream number as “1”.

ZOYM:PCAP:FIRST=1:;

g. Set the value of the network appearance as “1”.

ZOYM:PCAP:NETWORK=1:;

h. 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. Create the signalling route set.

ZNRC:NA0,222,PCAP,6,,:,,,0:;

c. Disable the signalling link test.

ZNST:NA0,222,PCAP:N:;

d. Create a new SCCP signalling point parameter set.

ZOCC:3,PCAP;

e. Allow the use of white book management procedures.

ZOCM:3:12,1:;

f. Allow the use of extended unitdata (XTUD) messages.

ZOCM:3:14,1:;

g. Allow the connection-oriented segmentation.

ZOCM:3:27,1:;

h. Create a new SCCP subsystem parameter set.

ZOCA:2,PCAP:;

i. Enable immediate sending of subsystem state information.

ZOCN:2:14,1;

j. Allow the activation of the signalling link.

ZNLA:20:;

k. Activate the signalling link.

ZNLC:20,ACT:;

l. Allow the activation of the signalling route.

ZNVA:NA0,222;

m. Activate the signalling route.

ZNVC:NA0,222::ACT;

n. Add a new subsystem to RNC's own signalling point.




ZNFB:NA0,111:F9,PCAP,2,;

o. Add a new subsystem to SAS's signalling point.

ZNFD:NA0,222,3:F9,PCAP,2,;

p. Allow broadcasting of subsystem states to the localsubsystem.

ZOBC:NA0,222,F9:NA0,F9:Y:;

q. Activate SCCP for RNC’s own signalling point.

ZNGC:NA0,111:ACT;

r. Activate SCCP for SAS’s signalling point.

ZNGC:NA0,222:ACT;

s. Activate SCCP subsystem for RNC’s own signalling point.

ZNHC:NA0,111:F9:ACT;

t. 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 objectbefore you can configure the Iupc (SAS) parameters of the WSMLC.For more information on creating a WSMLC object, see CreatingWSMLC 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 thedrop-down list.

d. For the "Network based AGPS" option, select "Enabled" fromthe drop-down list.

e. For the "Preferred A-GPS method" option, select the preferredmethod from the drop-down list.

f. For the "LCS Interface" option, select value "Iupc" from thedrop-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 decimalvalue of SAS's SPC (0x222), "546"

i. Click OK to save configuration.


RNC Integration

16 Printing alarms

16.1 Printing alarms using LPD protocol

Before you start

To print out the alarms, you must first configure the LPD printers and definetheir 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 thesettings are correct. IP address should be set and the functionalstate should be NORMAL.

If the LPD is not shown in the printout, continue to step 2. If thesettings 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 indexnumber of the LPD given when configuring the printers.

It is recommended to direct the alarms to the VPP devices whose indexis less than 50.

ZINI;

2. If the LPD is not shown in the printout

Then



Printing alarms

Create the LPD device

For instructions, see Creating a printer.

3. Check that the printer state, the LPD index and the IP addressare correct (INI)

The field FUNCTIONAL STATE in the printout shows the printerstate. The printer state in the execution printout should be NORMAL.

The LPD index number should be the same as the VPP indexnumber.

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 thedesired I/O device.

To print out all the alarms to the desired I/O device, connect thelogical file ALARMS to the I/O device. To print out only a certain kindof alarms to the desired I/O device, connect the suitable logical filesto the I/O device. For more information on the logical files used withalarms, see Alarm printing and its management.

If you are directing the alarms to VPP, pay special attention that theVPP index in the command is the same as the LPD index givenwhen configuring the printers.


RNC Integration

Note

To print out the alarms via LPD, it is recommended to direct the alarmsto the VPP devices whose index is less than 50.

ZIIS:,:<logical file name>,:DEV=<current objectidentification>: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 toVPP-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).

1. Display the printer state and check that the value of the fieldFUNCTIONAL STATE in the printout is NORMAL.

2. Check that the TCP/IP address is correct.

3. As you want to direct the alarms to VPP-1, check that the indexnumber of LPD is 1.

4. Connect ALACOMM1 to the correct alarm output device.

The alarm system writes two- and three-star communications alarmsto the logical file ALACOMM1.

When giving the command, pay special attention to the correct indexnumber.

ZIIS:,:ALACOMM1,:DEV=VPP-99:DEV=VPP-1;

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. Thisis a convenient way to continuously monitor alarms on the computerscreen over TCP/IP.



Printing alarms

Before you start

To display the alarms on a Telnet terminal or in a Web browser, you needto be familiar with the logical files used with alarms, and their tasks.

Steps

1. Check that the IP address of the computer unit has beendefined (QRI)

ZQRI;

If the IP connection is not defined, see Creating and modifying IPinterfaces.

2. Check that the logical files used in printing out alarms areconnected to correct VPP devices (IID)

To ensure that all alarms are printed out via a Telnet terminal or aWeb browser, check the connection between each of the logical filesand 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 foralarm printing can be established. If the logical files are connected totwo VPPs, for example, VPP-99 and VPP-98, two simultaneoussessions for alarm printing can be established.

VPP-99 serves the first connection that is established and VPP-98serves the second connection and so on.

3. Connect the logical files used in printing out alarms to correctVPP devices (IIS)


RNC Integration

If you want to print out all the alarms to the same window, connectVPP-99 to every alarm-related logical file.

If you want to print out only certain alarms, for example, two- andthree-star alarms, connect the logical files used with these alarmsand the correct VPP devices (VPP-99, VPP-98, VPP-97, VPP-96 orVPP-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 theparameter IND=<current object index>. If this parameter is notgiven, the new I/O device is simply added but does not replace theprevious I/O device.

ZIIS::<logical file name>::DEV=VPP-<I/O deviceindex>;

ZIIS::<logical file name>:IND=<current objectindex>:DEV=VPP-<I/O device index>;

Note that after connecting the logical files associated with alarms tothe correct devices, you do not need to change these connectionsduring the lifetime of the software build. You can print out the alarmsas described in step 4.

4. Establish a Telnet or HTTP connection to OMU IP address, port11111

If you are using a Telnet terminal, press the Enter key once, after youhave connected to the correct address and port.

If you are using a Web browser, connect to the correct address andport; no extra keystrokes are needed.

Expected outcome

The alarms that occur in the network element from that moment onare 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 stateof the VPP devices corresponding to the Telnet or HTTP sessions isWO-EX.

The working state of the VPP devices not reserved for anyconnection is BL-EX.



Printing alarms

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 orWeb browser.

6. End the session when you are ready

You can stop the printing of alarms via Telnet or HTTP by closing theTelnet terminal or the Web browser.


RNC Integration

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 remoteconnections to NetAct

Instructions


Configuring IP stack in OMU

Instructions


Creating and modifying DNS configuration

Modifying IP parameters

Creating and modifying IP interfaces



Related Topics

Creating OSPF configuration for O&M connectionto NetAct

Instructions


Modifying OSPF configuration

Configuring static routes for the O&M connectionto NetAct

Instructions


Creating and modifying static routes

Configuring ESA12

Instructions

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

Configuring ESA24

Instructions



RNC Integration


Instructions

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

NEMU TCP/IP network

Configuring DHCP server in NEMU

Instructions


Configuring DNS client and server in NEMU

Instructions


Configuring NEMU to RNC

Instructions

NEMU TCP/IP network

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




Related Topics

Configuring NTP services in NEMU

Instructions


Descriptions

Time management in NEMU

Configuring IP address for NEMU

Instructions


Connecting to O&M backbone via Ethernet

Instructions


Configuring IP over ATM interfaces

Instructions


Creating and modifying IP over ATM interfaces

Creating and modifying IP interfaces


RNC Integration

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



Related Topics

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


RNC Integration

Creating SDH protection group

Descriptions

ATM over SDH

Creating phyTTP

Descriptions

Physical layer Trail Termination Point (phyTTP)


Instructions

Inspecting synchronisation system

Synchronisation fails

Configuring transmission and transport resources


Creating IMA group



Creating phyTTP

Creating ATM resources in RNC



Related Topics

Creating radio network connection configuration

Instructions


Modifying radio network connection configuration parameters

Creating ATM termination point for IP over ATMconnection

Instructions


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

Instructions

IP connection configuration for RNC



Creating IMA group



Creating phyTTP



RNC Integration


Instructions

Creating local signalling configuration for RNC

Setting MTP level signalling traffic load sharing

Activating MTP configuration


Instructions



Instructions



Instructions

Creating local signalling configuration

Activating SCCP configuration



Related Topics


Instructions

Creating local signalling configuration


Configuring Iu-CS parameters of RNC

Instructions


Descriptions

RNC interfaces

Digit analysis and routing in RNC

Creating routing objects and digit analysis for Iuinterface in RNC

Descriptions

Analysis and routing objects in ATM network


Instructions

Creating routing objects and digit analysis for Iur interface in RNC


RNC Integration

Creating routing objects and digit analysis withsubdestinations and routing policy for Iu interface

Descriptions



Instructions

Creating routing objects and digit analysis for Iu interface in RNC



Creating IMA group



Creating phyTTP


Configuring signalling channels

Instructions

Configuring ATM-based signalling channels




Related Topics





Configuring IP-based signalling channels


Configuring Iu-PS parameters of RNC

Instructions


Descriptions

RNC interfaces

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

Instructions

IP configuration for Iu-PS interface




RNC Integration

Creating IMA group



Creating phyTTP


Configuring signalling channels

Instructions

Configuring ATM-based signalling channels










Related Topics

Configuring Iur parameters of RNC

Instructions


Descriptions

RNC interfaces


Creating routing objects and digit analysis for Iurinterface in RNC

Descriptions



Instructions

Creating routing objects and digit analysis for Iu interface in RNC



Creating IMA group




RNC Integration

Creating phyTTP


Configuring Iu-BC parameters of RNC

Instructions


Descriptions

RNC interfaces

Configuring IP for Iu-BC (RNC-CBC)

Descriptions

IP configuration for Iu-BC interface

Creating frequency measurement control

Instructions


Modifying frequency measurement control parameters



Related Topics

Creating handover path

Instructions


Modifying handover path parameters

Creating a WCDMA BTS site

Instructions



Locking and unlocking a WCDMA cell

Modifying WCDMA BTS parameters

Deleting radio network managed objects


Instructions


Modifying WCDMA cell parameters

Creating an internal adjacency for a WCDMA cell

Creating an external adjacency for a WCDMA cell


RNC Integration


Instructions




Modifying WCDMA cell adjacencies


Instructions




Modifying WCDMA cell adjacencies

Overview of location services

Instructions

Activating the Location Services feature

Activating the ADIF interface

Activating the Iupc interface



Related Topics

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


RNC Integration

Nokia RNC Integration

Documents

Transcript of Nokia RNC Integration