07b RNC Integration Dn03471554 4 en Global PDF Paper a4 d

7/28/2019 07b RNC Integration Dn03471554 4 en Global PDF Paper a4 d

http://slidepdf.com/reader/full/07b-rnc-integration-dn03471554-4-en-global-pdf-paper-a4-d 1/183

RNC Integration

dn03471554Issue 4 en

# Nokia CorporationNokia Proprietary and Confidential

1 (183)

RNC3059

Nokia WCDMA RNC, RN2.1, ProductDocumentation (PDF)



The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for the useof Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means without theprior written permission of Nokia. The document has been prepared to be used by professionaland properly trained personnel, and the customer assumes full responsibility when using it.Nokia welcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the document areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors.NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTOR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARYLOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according tothe applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2005. All rights reserved.

2 (183) # Nokia CorporationNokia Proprietary and Confidential


RNC Integration



Contents

Contents 3

1 Integration 5

2 Configuring IP for O&M backbone (RNC - NetAct) 112.1 Configuring IP for O&M backbone (RNC NetAct) 112.2 Creating MMI user profiles and user IDs for remote connections to

NetAct 142.3 Configuring IP stack in OMU 152.4 Configuring IP routing 182.4.1 Creating OSPF configuration for O&M connection to NetAct 182.4.2 Configuring static routes for the O&M connection to NetAct 232.5 Configuring LAN switch 25

2.5.1 Configuring ESA12 252.5.2 Configuring ESA24 282.6 Configuring NEMU for DCN 312.6.1 Configuring NEMU for DCN 312.6.2 Configuring DHCP server in NEMU 322.6.3 Configuring DNS client and server in NEMU 332.6.4 Configuring NEMU to RNC 372.6.5 NemuRegEdit 382.6.6 Configuring Tardis 2000 NT in NEMU 432.6.7 Configuring IP address for NEMU 452.7 Configuring external IP connections 472.7.1 Connecting to O&M backbone via Ethernet 472.7.2 Configuring IP over ATM interfaces 48

3 Integrating NEMU 513.1 Setting log size and overwriting parameters for NEMU logs 513.2 Supervising NEMU software 523.3 Configuring NEMU system identifier (systemId) 533.4 Configuring the RNC object 543.5 Configuring Nokia NetAct interface with NEMU 55

4 Configuring heartbeat interval for RNC 59

5 Configuring RNC level parameters 615.1 Defining external time source for network element 61

5.2 Creating local signalling configuration for RNC 62

6 Configuring transmission and transport interfaces 676.1 Configuring PDH for ATM transport 676.2 Creating IMA group 706.3 Configuring SDH for ATM transport 726.4 Creating SDH protection group 756.5 Creating phyTTP 776.6 Creating ATM resources in RNC 79



3 (183)

Contents



7 Configuring synchronisation inputs 87

8 Creating Iub interface (RNC-BTS) 938.1 Configuring transmission and transport resources 93

8.2 Creating radio network connection configuration 938.3 Creating ATM termination point for IP over ATM connection 958.4 Configuring IP for BTS O&M (RNC-BTS/AXC) 97

9 Creating Iu-CS interface (RNC-MGW) 1039.1 Configuring transmission and transport resources 1039.2 Configuring signalling channels 1039.2.1 Creating remote MTP configuration 1039.2.2 Activating MTP configuration 1079.2.3 Setting MTP level signalling traffic load sharing 1099.2.4 Creating remote SCCP configuration 1109.2.5 Activating SCCP configuration 114

9.3 Configuring Iu-CS parameters of RNC 1159.4 Creating routing objects and digit analysis for Iu interface in RNC 117

10 Creating Iu-PS interface (RNC-SGSN) 12310.1 Configuring transmission and transport resources 12310.2 Configuring signalling channels 12310.3 Configuring Iu-PS parameters of RNC 12310.4 Configuring IP for Iu-PS (RNC-SGSN) 124

11 Creating Iur interface (RNC-RNC) 13711.1 Configuring transmission and transport resources 13711.2 Configuring signalling channels 13711.3 Configuring Iur parameters of RNC 137

11.4 Creating routing objects and digit analysis for Iur interface in RNC 138

12 Creating Iu-BC interface (RNC-CBC) 14312.1 Configuring transmission and transport resources 14312.2 Configuring Iu-BC parameters of RNC 14312.3 Configuring IP for Iu-BC (RNC-CBC) 144

13 Configuring radio network objects 14913.1 Creating frequency measurement control 14913.2 Creating handover path 15013.3 Creating a WCDMA BTS site 15113.4 Creating a WCDMA cell 154

13.5 Creating an internal adjacency for a WCDMA cell 15513.6 Creating an external adjacency for a WCDMA cell 158

14 Printing alarms 16114.1 Printing alarms using LPD protocol 16114.2 Printing alarms via Telnet terminal or Web browser 163

Related Topics 167



RNC Integration



1 Integration

You can start the integration of a network element after the network element has

been successfully installed and commissioned. During the commissioning phase,

the network elements have been configured and tested as stand-alone entities.

During the integration phase the interconnections between the network elements

are configured and their parameters are customised. After successful integration

the network element is ready for commercial use.

Integration overview

Integration consists of the following steps:

1. configuring internet protocol (IP) for operation and maintenance (O&M)

backbone (radio network controller (RNC) - NetAct)

a. configuring IP for O&M backbone (RNC - NetAct)

b. creating man-machine interface (MMI) user profiles and user IDs for

remote connections to NetAct

c. configuring IP stack in OMU

d. configuring IP routing

e. configuring local area network (LAN) switch

f. configuring network element management unit (NEMU) for data

communication network (DCN)

g. configuring external IP connections

2. integrating NEMU

a. setting log size and overwriting parameters for NEMU logs

b. supervising NEMU softwarec. configuring network element system identifier (systemId) to NEMU

d. configuring the RNC object

e. configuring Nokia NetAct interface with NEMU

3. configuring heartbeat interval for RNC

4. configuring RNC level parameters



5 (183)

Integration



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

asynchronous transfer mode (ATM) transport

b. creating inverse multiplexing for ATM (IMA) group

c. configuring synchronous digital hierarchy (SDH) for ATM transport

d. creating SDH protection group

e. creating physical layer trail termination point (phyTTP)

f. creating ATM resources in RNC

6. configuring synchronisation inputs

7. creating Iub interface (RNC - base transceiver station (BTS))

a. configuring transmission and transport resources

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


b. configuring signalling channels

c. configuring Iu-CS parameters of RNC

d. creating routing objects and digit analysis for Iu interface in RNC

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



c. configuring Iu-PS parameters of RNC

d. configuring IP for Iu-PS (RNC-SGSN)

10. creating Iur interface (RNC-RNC)



c. configuring signalling channels

d. configuring Iur parameters of RNC

e. creating routing objects and digit analysis for lur interface in RNC

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



RNC Integration




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

network:



7 (183)

Integration



Figure 1. Example network and logical interfaces between network elements

The logical interfaces for the RNC in the 3rd generation network are presented in

the following list.

Iu-CS logical interface between the RNC and the core network. TheIu interface provides signalling means to establish, maintain

and release links and recover fault situations and generic

bearer services over its user plane.

Iu-PS logical interface between the RNC and the SGSN

Iur logical interface for the interconnection of two RNC

components of the UMTS terrestrial radio access network

(UTRAN) system

RNC

RNC

MultimediaGateway Rel. 4

SGSN

Iu-PSIur

Iub

Iub

Iu-CS

NetAct

BTS

BTS

Iu-BC

CBC

MSC Server



RNC Integration



Iub logical interface between the RNC and the WBTS

Iu-BC logical interface between the RNC and the cell broadcast

centre (CBC)

Required integration planning information

The network planning process delivers all required information for network

element installation, commissioning and integration. Network planning can be

divided into the following phases: transmission & transport and radio network

planning.

The following planning activities must be accomplished before the integration

phase starts:

1. radio network planning

2. transport/transmission network planning (in Nokia terminology,

transmission is related to the PDH/SDH network and transport to the ATM/

AAL2 network).

3. IP network planning



9 (183)

Integration





RNC Integration



2 Configuring IP for O&M backbone (RNC -

NetAct)

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

Purpose

This chapter shows the procedure to configure the Network Element Management

Unit (NEMU), ESA12/ESA24 Ethernet switch and the Operation and

Maintenance Unit (OMU) for the data communication network (DCN). After this,

you can use the Element Manager to manage the RNC remotely.

The O&M backbone can be configured either via Ethernet or via ATM virtual

connections, or via both if OSPF is used.

For more information, see Integrating NEMU to RNC (available in NOLS).

Before you start

Check that:

. you have the IP address plan and IP parameters for OMU, NEMU, and

ESA12/ESA24.

. your computer has the following:

- DHCP client

- Connection to the Element Manager and remote management

application for NEMU

For more information, see Installing Element Manager .

- Ethernet interface connected to a port of ESA12/ESA24

If O&M backbone towards NetAct is connected via ATM virtual connection, the

transport and transmission network plan for the interface in question is also

required. Usually, this interface is Iu-CS.



11 (183)

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



Figure 2. Preconfigured settings for O&M network

Note

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

Steps

1. Create MMI user profiles and user IDs for remote connection to

NetAct

See Creating MMI user profiles and user IDs for remote connections to

NetAct for detailed instructions.

2. Configure IP stack in OMU

See instructions in Configuring IP stack in OMU .

3. Configure IP routing

192.168.1.5/28

192.168.1.1/28 (logical)

RNC

OMU

192.168.1.10/28

Computer with

Element Manager

RNC LAN192.168.1.0/28

NEMUESA12/ESA24192.168.1.9/28



RNC Integration



There are two ways to configure routing information:

. by creating OSPF configuration

See instructions in Creating OSPF configuration for O&M connection to NetAct .

. by configuring static routes

See instructions in Configuring static routes for O&M connection to

NetAct .

4. Configure the Ethernet/LAN switch

Configure the Ethernet (LAN) switch according to instructions in

Configuring ESA12 or Configuring ESA24, depending on which one you

have in your configuration.

5. Configure NEMU

Configure NEMU according to instructions in Configuring NEMU for

DCN .

6. Configure external IP connections

Configure the connection to NetAct for O&M traffic. There are two ways

to connect the RNC to NetAct:

. by configuring the O&M backbone via Ethernet

Refer to instructions in Connecting to O&M backbone via Ethernet .

. by configuring the O&M backbone via ATM virtual connections

Refer to instructions in Configuring IP over ATM interfaces.

The recommended way of connecting RNC to NetAct is via Ethernet. The

connection via ATM should only be used as a backup. O&M connections

can be configured to use both ways, if OSPF is used for routing.



13 (183)




2.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 to create

users NUPADM and NEMUAD and their profiles in the RNC. NetAct

application (service user management) accesses RNC with NUPADM profile.

NUPADM profile is mandatory to create other service users in NetAct

application. NEMUAD profile is created to enable communication between

NEMU and OMU. For example, without NEMUAD profile, PM data cannot be

transferred to NEMU and therefore affects the transfer measurement to NetAct.

See the example below for detailed instructions.

Before you start

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

Steps

1. Establish a telnet connection to RNC OMU

Enter the preconfigured IP address to OMU (the default IP address is

192.168.1.1):

telnet <IP address of OMU>

2. Create new MMI user profiles

Create the user profiles for NUPADM and NEMUAD. Refer to Creating

MMI user profiles in Information Security for details.

3. Create new MMI user IDs

Create the NUPADM and NEMUAD user IDs. Refer to Creating MMI

user IDs in Information Security for details.

Example 1. Creating MMI user profiles and user IDs in the RNC

This example shows how to create the NUPADM and NEMUAD MMI profiles

and user IDs in the RNC.

1. Create the user profiles.

ZIAA:NUPADM:ALL=250:VTIME=FOREVER,UNIQUE=YES;



RNC Integration



ZIAA:NEMUAD:ALL=250:VTIME=FOREVER,UNIQUE=YES::

FTP=W;

2. Create the user IDs.

ZIAH:NUPADM:NUPADM;

ZIAH:NEMUAD:NEMUAD;

When creating a new user ID, the system prompts you for a password. The

password created here is used for communication between the NEMU or

the NetAct and the RNC. The system displays the following output:

/ * I D E N T IF Y P A S S W OR D :

M I NI M UM P A SS W OR D L E NG T H I S 6

M A XI M UM P A SS W OR D L E NG T H I S 1 6 * /

N E W P A S S W OR D : * * ** * * * *

VERIFICATION:********C O M M A ND E X E C U TE D

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

2.3 Configuring IP stack in OMU

Purpose

The purpose of this procedure is to configure OMU for data communication

network (DCN).

Before you start

A telnet connection to RNC OMU must be open.

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

configuration.

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



15 (183)




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 the maximum

time-to-live value and define if the subnets are considered to be local

addresses in both OMU units.

For IPv4:

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

are local>]);

For IPv6:

ZQ6T:<unit type>,<unit index>:([IPF=<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 Q6N for

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>:[<IP

address>],[<address type>]:[<prefix length>]:

[<destination IP address>];

4. Configure IP routing

There are two ways to configure routing information:

. by creating OSPF configuration

Refer to instructions in Creating OSPF configuration for O&M

connection to NetAct .



RNC Integration



. by configuring static routes

Refer to instructions in Configuring static routes for O&M


5. Remove the preconfigured IP address

Remove the preconfigured IP address from both OMU units by QRN

command for IPv4, by Q6G command for IPv6.

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

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

Note

If the unit index for 2N type logical IP address is specified, the logical addresses

will be deleted both from WO and SP unit.

Example 2. Configuring IPv4 stack in OMU

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

1. Configure DNS parameter data. The IPV4 address of the primary DNS

server is 10.1.1.5 and the local domain name RNC1.NETACT.

OPERATOR.COM.

ZQRK:10.1.1.5,,,"RNC1.NETACT.OPERATOR.COM";

2. Modify IPv4 parameters for both OMU units separately. Set the host name

to OMU, set IP forwarding on, and specify that subnets are not local.

ZQRT:OMU,0:HOST="OMU",IPF=YES,SNL=NO;

ZQRT:OMU,1:HOST="OMU",IPF=YES,SNL=NO;

3. Add a new logical IPv4 address (10.1.1.2) to the OMU units. The interface

name is EL0 and the netmask is length 28.

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



17 (183)




4. Configure IPv4 routing. For examples, see Creating OSPF configuration

for O&M connection to NetAct and Configuring static routes for O&M


5. Remove the preconfigured IPv4 address (198.168.1.1) from both OMUunits.

ZQRN:OMU:EL0:192.168.1.1,,DEL;

Example 3. 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 primary DNS

server is 3FEE::1 and the local domain name RNC1.NETACT.

OPERATOR.COM.

ZQ6K:"3FEE::1",,,"RNC1.NETACT.OPERATOR.COM";

2. Modify IPv6 parameters for both OMU units separately. Set the host name

to OMU, set IP forwarding on, set hoplimit value as 70, and set router

advertisement OFF.

ZQ6T:OMU,0:IPF=ON,HLIM=70,RADV=OFF;

ZQ6T:OMU,1:IPF=ON,HLIM=70,RADV=OFF;

3. Add a new logical IPv6 address (3FFE:1200:3012:C020:380:6FFF:

FE5A:5BB7) to the OMU units. The interface name is EL0 and 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 OMU units.

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

2.4 Configuring IP routing

2.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 ATM virtual

connection, the IP over ATM interface for OMU must be created before OSPF is

configured. Refer to instructions in Configuring IP over ATM interfaces.

You must remove the existing default routes before creating the OSPF

configuration. If the default routes are not removed, the RNC might advertise

itself, incorrectly, as an alternative default route to other routers. For instructions

on how to remove default routes, see Configuring static routes for O&M


Steps

1. Configure OSPF router parameters (QKS)

If the OMU units have physical IP addresses in addition to a logical IP

address, the OMU units must have a different router ID. Give the physical

address of the OMU unit as the value for the router ID parameter, to avoid

having two routers with the same router ID, in the network.

ZQKS:<unit type>, <unit index> :<router id>:

<rfc1583compatibility>:<spf delay>:<spf hold time>;

2. Configure OSPF area parameters (QKE)

Define the OSPF area (both backbone and other area) parameters of anOSPF router.

ZQKE:<unit type>,<unit index>:<area

identification>:<stub area>,[<stub area routecost>],<totally stubby area>;

The area identification specifies the area ID for a new OSPF. The area ID is

entered as a dotted-quad. The area ID of 0.0.0.0 is reserved for the

backbone. The IP network number of a subnetted network may be used as

the area ID.

Note

The area parameters do not become effective (written into the configuration file)

until the area has been attached to an interface.

3. Interrogate IP interfaces (QRI)



19 (183)




You must know the interface identification of the network interfaces

when you are configuring OSPF interfaces.

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

If you do not give any parameter values, network interface information of

all computer units of the network element is listed.

4. Configure OSPF interfaces (QKF)

ZQKF:<unit type>,<unit index> :<interface

specification>:<area identification>:[<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 routing information 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 connection to the

backbone area, use a virtual link to provide a logical path from the

disconnected area to the backbone area. Virtual links have to be configured

to both ends of the link. The QKV command has to be entered separately for

both border routers using the virtual link.

ZQKV:<unit type>,<unit index>:<routeridentification>:<transit area>:<hello interval>:

<router dead interval>:<authentication>;

Example 4. Creating OSPF configuration for O&M DCN



RNC Integration



The following example illustrates OSPF configuration for O&M DCN. The

corresponding IP network interfaces have been configured before this procedure.

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

Computer

withElement 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


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



21 (183)




This example presents the configuration of OSPF parameters in the OMU unit.

The OMU unit in RNC is a border router. The unit has three interfaces: EL0,

AA0, and AA255. The EL0 interface is attached to the backbone area through an

Ethernet connection. The AA0 and AA255 interfaces are attached to the

backbone area through an IP over ATM connection.

1. Obtain the numbers of the default routes of OMU-0 and OMU-1.

ZQKB:OMU;

The following output is displayed:

U NI T D ES TI NA TI ON G AT EW AY AD DR E SS R OU TE TY PE NB R

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

OMU-0 DEFAULT ROUTE 10.1.1.1 LOG 1

2. Remove the default route from both units.

ZQKA:1;

or

ZQKA::OMU,0;

3. Configure OSPF router parameters.

Configure the OSPF parameter data for the OMU with the router ID

10.1.1.2 and accept the default values for the remaining parameters.

ZQKS:OMU,0:10.1.1.2;

ZQKS:OMU,1:10.1.1.2;

4. Configure OSPF area parameters.

Configure the backbone area information for the OMU.

ZQKE:OMU,0:0.0.0.0;

ZQKE:OMU,1:0.0.0.0;

5. Inquire the attached interfaces.

ZQRI:OMU;

The following output is displayed:

IF ADM IF ADDR

UNIT NAM E STATE M TU TYPE TYPE IP ADDRESS

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

OMU-0 AA0 UP 1500 L 10.3.1.2/32

->10.3.1.1



RNC Integration



AA2 55 UP 1500 L 10.3.2.2/32

->10.3.2.1

EL0 UP 1500 L 10.1.1.2/28

OMU-1 AA0 U P 1500 L (10.3 .1.2)/32

->10.3.1.1AA2 55 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 AA255 interfaces.

The EL0 interface is attached to the backbone area through an Ethernet

connection. Accept default values for the hello interval and

router dead interval parameters and set the ospf cost to 10.

ZQKF:OMU,0:EL0:0.0.0.0:::10;

ZQKF:OMU,1:EL0:0.0.0.0:::10;

The AA0 and AA255 interfaces are attached to the backbone area through

an IPoA connection. Set the hello interval to 30, router deadinterval 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=;

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

Purpose

Static routes are used when dynamic routing (OSPF in this case, see Creating

OSPF configuration for O&M connection to NetAct ) does not provide any useful

functionality over the static routes. In other words, they are used when

configuring a simple static route achieves the same objective as using a more

complicated dynamic routing. Static routes can be used with dynamic routing

when creating a host route to a host that does not run dynamic routing.



23 (183)




For the IP over ATM connections towards NetAct, static routes are not used.

Configure OSPF to OMU for both connections towards the NetAct router. For

instructions, see Creating OSPF configuration for O&M connection to NetAct .

Before you start

You must create a default static route in the unit to define a default gateway for IP

connections. If the default route cannot be used, you need to delete it and create

other routes.

Note

You can only configure one default route for each unit.

A logical route must use a logical address to reach its gateway, and it follows thelogical address if a switchover occurs.

Steps

1. Configure the default static route

You do not need to specify the destination IP address for the default route.

Note

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

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

type>];

2. If the default route cannot be used

Then

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. Set IP forwarding off for the unit in which you are deleting the route.

ZQRT:<unit type>,<unit index...>:IPF=NO;



RNC Integration



c. Delete the route by identifying it by its route number or by its

identification.

ZQKA:<route number>;

ZQKA::<unit type>,<unit index>;d. Set IP forwarding back on, if needed

ZQRT:<unit type>,<unit index...>:IPF=YES;

3. If the default route cannot be used and you deleted it, or if you need to

create more routes

Then

Create new static routes (QKC)

You may create new static routes by QKC command.

ZQKC:<unit type>,<unit index>:[<destination IP

address>],[<netmask length>]:<ip address>:[<routetype>];

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

2.5 Configuring LAN switch

2.5.1 Configuring ESA12

Purpose

The purpose of this procedure is to configure the ESA12 Ethernet switch for

O&M DCN.

Steps

1. Establish a telnet connection to ESA12

a. Enter the preconfigured IP address to ESA12 (the default IP address

is 192.168.1.9).

telnet <ip address of ESA12>

b. Enter your login ID and password.



25 (183)




The default password is empty. Therefore, press Enter to continue. If

you have already changed your password during commissioning,

enter your new password.

N O K I A E S A - 1 2.

Username:nokia

Password:********

Expected outcome

All the other parameters:

ESA12

M a in M e nu

1 . G e n e r al C o n f i gu r a t i on

2 . S N M P C o n f i g u r a t io n3 . P o r t s C o n f i g u r a t io n

4 . P o rt s S t at u s

5 . L o ad F a ct o ry D e fa u lt s

6 . S o ft w ar e U p gr a de

7 . R e se t

8 . L o go u t

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.

G e n e r al C o n f i gu r a t i on

MAC addr ess 00 A0 12 0B 02 74

1. Agent IP Address : 192. 168.0 01 .00 9

2. Agent Netmask : 2 55 .25 5. 255 .2 40

3. Default Gateway : 192.168.0 01.00 1

4 . S u p e r vi s o r / Te r m i n al P a s s w or d :

5. System Name :

6 . A d v a n ce d F e a t u re s

9 . M ai n M en u

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

Expected outcome

The selected parameter row with the current settings is printed below the

menu.

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



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 6. Changing the default gateway in ESA12

This example shows how to change the default gateway in ESA12.

1. Establish a telnet connection to ESA12. In this example, the password has

not been changed yet.

telnet 192.168.1.9

Username:nokia

Password:

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

3. Press 3 to select Default Gateway. The current address is displayed on 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:

G e n e r al C o n f i gu r a t i on

MAC addr ess 00 A0 12 0B 02 74

1. Agent IP Address : 192. 168.0 01 .00 9

2. Agent Netmask : 2 55 .25 5. 255 .2 40

3. Default Gateway : 10.001.00 1.002

4 . S u p e r vi s o r / Te r m i n al P a s s w or d :

5. System Name :

6 . A d v a n ce d F e a t u re s

9 . M ai n M en u



27 (183)




2.5.2 Configuring ESA24

Purpose

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

Before you start

Before you start the configuration, check the following:

. The PC or laptop that you are using is connected to one of the Ethernet

ports of the ESA24 switch with an Ethernet cable.

. The ESA24 Ethernet switch is powered up (the LED on the front panel of

the switch is green).

Steps

1. Connect to the IP address of ESA24 via Telnet

Note

If connection to the IP address of ESA24 is via Telnet, the IP address will change

to the given address by the command IP address X.X.X.X/x.x and the

Telnet connection will stop responding. The initial configuration has to be done

by the serial connection. See ESA24 User Guide for the detailed information.

a. Start a Telnet session by selecting Start -> Run on the Windows

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:

U s e r A c c e s s V e r i f i c a t i on

Password:

2. Log in to ESA24

Enter the default password "nokia", or the new password if the password

has been changed, and press Enter.



RNC Integration



Expected outcome

After successful login, the ESA24 prompt is displayed:

ESA24>

3. Enable RSTP or MSTP for ESA24

Enable the Rapid Spanning Tree Protocol (RSTP) or the Multiple Spanning

Tree Protocol (MSTP) for ESA24. For more information, see ESA24 User

Guide in PDF format in NOLS and Cable Lists and Use of ATM Links and

LAN Connections in Site documents.

4. Change to a privileged mode in BiNOS

Enable the privileged mode in ESA24 operating system with the command

ESA24> enable

The privileged mode allows advanced viewing and configuration for the

unit.

Note

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

By default, the enable command does not ask for a password. It is

possible to protect the administrator's rights with a password. See the

ESA24 User Guide for more information.

5. Change to configuration mode in BiNOS

Enable the configuration mode in ESA24 operating system with the

command

ESA24#configure terminal

6. Set the IP address and netmask for ESA24

ESA24(config)#ip address <ip address>/<netmask>

7. Set the default gateway for ESA24



29 (183)




Delete the existing default route before add new route.

ESA24(config)#no ip route 0.0.0.0/0

ESA24(config)#ip route <destination address>/<destination network mask> <ip gateway address>

8. Enable DHCP, if necessary

ESA24(config)#ip address dhcp

9. Save the configuration

ESA24#write

Further information

To view information on the commands, enter ? in the ESA24 command prompt.

To view more information on the syntax of a specific command, enter

<command> ?.

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

U s e r A c c e s s V e r i f i c a t i on

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.



RNC Integration



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

2.6 Configuring NEMU for DCN

2.6.1 Configuring NEMU for DCN

Purpose

The procedure describes how to configure NEMU for DCN.

Steps

1. Open the remote management application for NEMU

Use Communication profile Internet (TCP).

Give a NEMU computer name as a domain. It is recommended to change

the default user ID and/or password immediately after the first login, for

information security reasons.

For more information, see the instructions in NetOp remote access to

NEMU and Configuring NetOp Guest in Network Element Management

Unit .

2. Configure the DHCP server

Refer to the instructions in Configuring DHCP server in NEMU .

3. Configure the DNS client and server data

Refer to the instructions in Configuring DNS client and server in NEMU .

4. Configure NEMU to RNC



31 (183)




Refer to the instructions in Configuring NEMU to RNC .

5. Configure the NTP server

Refer to the instructions in Configuring Tardis 2000 NT in NEMU .

6. Define the IP address for NEMU according to the IP plan

Refer to the instructions in Configuring IP address for NEMU .

2.6.2 Configuring DHCP server in NEMU

Purpose

The DHCP server is used for configuring IP hosts automatically. The DHCPclient in an IP host sends a broadcast query to the network, where a DHCP server

receives it. The DHCP server answers the client by returning its IP address and

other parameters. The returned values have been saved in the DHCP server's

database.

With the RNC, DHCP is used to distribute IP parameters to IP devices that have

been locally attached to the RNC. An example of such a device is a PC that has

the Element Manager running.

The DHCP server is configured according to the IP plan. The DHCP server is

needed because the PC in which the RNC Element Manager is running receivesthe IP parameters from the DHCP server of the NEMU. PC is not needed for

configuring, but a standard DHCP can be used to configure the PC. However, this

requires that the DHCP client is configured to the PC.

See also the IETF's RFC 2136.

Steps

1. Open the DHCP manager of the managed NEMU

Select Start -> Programs -> Administrative Tools -> DHCP.

2. Add a new local management scope for NEMU

a. In the list of DHCP servers, select the DHCP server for which you

want to create a new scope.

b. Select Action -> New Scope.

c. Enter the name of the scope. For example, Local Management.



RNC Integration



d. Enter the IP addresses and masks for the new scope according to the

IP plan.

Note

If you have static IP addresses configured on non-DHCP clients (for example,

NEMU), you must use the IP address pool that does not contain those IP

addresses. If you use an IP address pool that contains those addresses, you must

configure the Exclusion Range list on DHCP Scope.

e. When the system asks you if you want to configure the DHCP

options for this scope, answer No.

3. Delete the old local management scope

a. Under the server, select the old management scope (192.168.1.0).

b. Select Action -> Delete.

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 NTPServers as required.

5. Activate the new local management scope

a. Under the server, select the new local management scope.

b. Select Action -> Activate.

2.6.3 Configuring DNS client and server in NEMU

Purpose

This section describes how to create a DNS server to the NEMU server (Windows

2000), and how to configure primary and secondary servers.

Creating the DNS server to the NEMU server does not require any sofware

installations because the DNS server is installed in NEMU by default. Only a new

DNS zone needs to be activated and created.



33 (183)




The Domain Name System (DNS) is a distributed database which maps

hostnames and IP addresses. DNS servers are needed to enable the use of DNS

names (for example, nemu.rnc1.netct.operator.com) instead of IP

addresses. The DNS management server is the primary server (Master name

server) of the zone. Servers in the network are secondary servers. This means that

DNS information is managed in the DNS management server and the secondary

servers automatically update their DNS databases from the management server.

DNS servers in the network are authoritative for their zone, so they handle the

DNS queries concerning the zone.

Figure 4. DNS architecture

ZONEtransfers

RNSDCN

BTS

BTS

SecondaryDNS server

Nokia NetAct

DNSmanagement

server

DNSqueries

RNC

ElementManager

BTSElementManager

DNSqueries



RNC Integration



The DNS management server is located in the Nokia NetAct. All the RNC

NEMUs have a secondary DNS server, which updates its information from the

DNS management server. The updating is normally controlled by the DNS

management server (see the DNS Notify RFC 1996 by the IETF). If there is no

Nokia NetAct, one NEMU is configured as the primary server, which the

secondary servers use to update their information.

See also the IETF's documents RFC 1034 and 1035.

The primary server is configured according to the IP plan.

Steps

1. Configure the DNS client data

a. Select Start -> Settings -> Network and Dial-Up Connections. b. Right-click Local Area Connection 3 and select Properties.

c. On the General tab, select Internet Protocol (TCP/IP).

d. Select Properties -> Advanced -> DNS.

e. Edit the address(es) of the DNS server(s) and set the search order, if

necessary.

f. Click OK -> OK -> OK ->OK-> NO to apply the changes.

g. Select Start -> Programs -> Administrative tools -> Services.

h. Select Workstation Service

i. In Action menu select Start.

j. Close Service window.

k. Select Start -> Settings -> Control Panel.

l. Double-click the System icon.

m. On the Network Identification tab, select Properties.

n. Enter the name of the computer and click More.

o. Enter the primary DNS suffix.

p. Click OK -> OK -> OK -> OK to apply the changes.

q. If you want to restart the computer when prompted, click YES.

During RNC integration, restarting is not needed.

2. Start and check the DNS service

a. Select Start -> Settings -> Control Panel -> Administrative tools

-> Services -> DNS Server.

b. Select Action -> Properties

c. Click Start.

d. Change the current status to 'Automatic'.

3. Start the DNS manager



35 (183)




Start the DNS manager from Start -> Programs -> Administrative tools -

> DNS.

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

To add a new secondary DNS zone to the server:

a. In the list of DNS servers, select the server to which you want to add

the new zone.

b. Select Action -> New Zone.

c. Select Standard secondary as the zone type.

d. Select Forward lookup zone.

e. Enter the zone name according to the IP plan. The zone name is the

end part of the computer name. For example, if the name of the

NEMU is nemu.rnc1.nokia.com, the zone name is thenrnc1.nokia.com.

f. Enter the IP address of the master server according to the IP plan.

Zone information is refreshed when the secondary server has a

connection to the master server.

g. Select Action -> Properties -> Forwarders.

h. Select Enable Forwarders and add the IP address of the master

DNS server.

To add a new primary DNS zone to the server:

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

b. Select Action -> New Zone.

c. Select Standard primary as the zone type.

d. Select Forward lookup zone.

e. Enter the zone name according to the IP plan. The zone name is the

end part of the computer name. For example, if the name of the

NEMU is nemu.rnc1.nokia.com, the zone name is then

rnc1.nokia.com.

f. Accept the default zone file name.

g. Repeat steps from b to f for each zone.

5. If you added a primary DNS zone to the server

Then

Create the DNS domains and hosts according to the IP plan

a. In the list of the server's Forward lookup zones, select the zone for

which you want to create the DNS domain.

b. Enter the name of the domain. For example, wbts1.



RNC Integration



c. To create a new host, select Action -> New Host. Enter the name of

the NEMU server, for example nemu, and the corresponding IP

address.

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

6. Update the data files of the server

Select Action -> Update Server Data File.

7. Check that the DNS service configuration succeeded, if necessary

Use Nslookup to check that the configuration was successful.

Note

The Nslookup only works after the RNC integration is completed.

8. If a preconfigured IP address is used, delete the server

a. In the list of DNS servers, select the server that has the

preconfigured IP address.

b. Select Action -> Delete.

Expected outcome

The DNS server should now be up and running. When installing the Application

Launcher, use the IP address and domain (zone name) of this DNS server. These

settings can be changed afterwards in the Element Manager's home directory by

adding the correct values to the dns.properties file. The added NEMU

servers can be found using the Search NE function in the Network Element

Login.

2.6.4 Configuring NEMU to RNCPurpose

The External Message Transfer (EMT) connection requires that the Win2000

registry includes the IP address of OMU and the user ID and password of the

network element. The user ID and password have been defined in the network

element for the EMT connection.



37 (183)




The IP address of the NEMU and the FTP username and password also have to be

defined for measurement bulk data transfer.

Any NEMU username and password can be used for NEMU FTP.

Note

The network element must have a user ID that the EMT and the FTP connections

can use.

Note

If the parameters are changed, you must restart the Platform Manager.

Summary

To enable FTP connection from the NEMU to RNC, you must define OMU FTP

user ID for the NEMU connection. To enable Telnet connection from the NEMU

to RNC, you must define OMU Telnet user ID and password for the NEMU

connection.

Steps

1. Open the Command Prompt from Start -> Run

2. Type NemuRegEdit, and click Enter

3. See further instructions in NemuRegEdit

2.6.5 NemuRegEdit

The operator can add network elements to NEMU by using the command line

tool NemuRegEdit. The NEMU platform setup executes NemuRegEdit. This tool

writes the information that the operator has entered to a Windows register. The

operator can start NemuRegEdit after the setup by entering the command

NemuRegEdit in a command prompt window. When starting the

NemuRegEdit, it prints out the current values, and asks if you want to change

them.



RNC Integration



Note

If OMU FTP, OMU Telnet or EMT passwords or username are changed on the

managed element side, same changes must be done also on NEMU side.

BASEID

BaseID is a name for a network element, for example HELSINKI.

NemuRegEdit asks the following questions from the user:

BaseId of managed network element

. Insert baseId of managed network element: HELSINKI

Type of managed network element

. Insert the type of managed network element. Type in one of the following

network element types (RNC, MGW, HLR, HLRi, MSC, SRR, MSS):

MSC

IP address of Network element

. Insert logical IP address of OMU unit of managed network element:

192.168.12.1

Printing network element information

. Given network element [HELSINKI] information:

- baseID: HELSINKI

- typeID: MSC

- IP address: 192.168.12.1

- Is this correct (Y/N)?

Add more managed network elements

. Add more managed network elements (Y/N)?

- If you want to add more network elements, NemuRegEdit asks the

questions from 1 to 5 again.



39 (183)




Select default network element:

. If you do not want to add more network elements, NemuRegEdit asks you

to select a default network element

- Select default network element: 1. HELSINKI, 2.TAMPERE

Printing the information of the default network element

. You selected [HELSINKI] as the default network element

- Type: MSC

- IP address: 192.168.12.1

- Default Network element set OK.

IP address of NEMU

. Enter an IP address of a NEMU here. Press Enter if current value is OK.

- NEMU IP address [STRING] current value: 10.12.17.123

- NEMU IP address [STRING] new value: 192.168.17.1

EMT UserName

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

- EMT UserName [STRING] current value: SYSTEM

- EMT UserName [STRING] new value: myusername

EMT Password

. Enter EMT Password and press Enter .

- EMT Password [STRING] new value: ******

When you press Enter , Value set OK message appears.

OMU FTP UserName

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

- OMU FTP UserName [STRING] current value: SYSTEM

- OMU FTP UserName [STRING] new value: myusername

OMU FTP Password

. Enter OMU FTP Password and press Enter .

- OMU FTP Password [STRING] new value: ******



RNC Integration




OMU Telnet UserName

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

- OMU Telnet UserName [STRING] current value: SYSTEM

- OMU Telnet UserName [STRING] new value: myusername

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 current value is OK.

- NEMU FTP UserName [STRING] current value: SYSTEM

- NEMU FTP UserName [STRING] new value: myusername

NEMU FTP Password

. Enter NEMU FTP Password and press Enter .

- NEMU FTP Password [STRING] new value: ******


Registration Account UserName

. Enter Registration Account UserName and press Enter . When you press

Enter , Value set OK message appears.

- Registration Account UserName [STRING] new value: SYSTEM

Registration Account Password

. Enter Registration Account Password and press Enter .

- Registration Account Password [STRING] new value:******


NEMU ID

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



41 (183)




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

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

Network Management's Registration IOR (RSIOR)

. Enter Network Management's Registration IOR (RSIOR). If you do not

want to set value, press Enter .

- Network Management's Registration IOR new value:

IOR:12345678910111213141516

- Is this correct (Y/N)?

If the value is correct, select Y. Value set OK message appears. If the

value is not correct, select N.

Press any key to exit.

Note

If the computer is restarted after NEMU integration is finished, the NEMU

software restart is not needed.

Configuration changes do not take effect until NEMU software is restart.

NEMU software restart can be done with the NEMU Platform Manager User

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 Manager not

running .

4. Click Start PM .

5. Wait until the status of the Platform Manager is NEMU software Running .

6. Close the NEMU Platform Manager User Interface.



RNC Integration



2.6.6 Configuring Tardis 2000 NT in NEMU

Purpose

Nokia makes the default settings in Tardis, so you can normally use it without any

modifications. Tardis can be found from the Control Panel.

Choose what kind of modifications you want to make from the following

procedure.

Steps

1. Set Tardis to automatically change servers

a. Select the General tab in Tardis.

b. Edit the settings as required.Select Automatically change servers on failure to set Tardis to

automatically change to a different server if it cannot contact the one

currently selected. Tardis will cycle through all the servers in the list.

Select Automatically change servers on success to set Tardis to

automatically change to a different server if it successfully contacts

the one currently selected. Tardis will cycle through all the servers in

the list. This may be useful as a way of checking which servers are

active.

2. Add NEMU time servers

a. Select the Main tab in Tardis.

b. To add a new time server, click Add. The Server details dialog

opens.

c. Enter the address of the time server.

Enter the address as a name or as an IP address. When using the

Network Time Protocol (NTP) the address may be left blank in

which case Tardis will listen to any broadcasts. If an address is

entered then Tardis will only listen to broadcasts from that machine.

d. Enter a descriptive name of the server.

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



43 (183)




e. Enter the protocol used by your time server:

. Simple Network Time Protocol (SNTP) is used in NEMU. It

is the standard way to synchronise computer clocks.

. HTTP protocol may be required if you are using a firewall/

proxy and have no time servers on your LAN.

. NTP broadcast protocol is a choice if you have an NTP server

on your LAN. It can be configured to broadcast time

information. Tardis will listen for these broadcasts if you use

this protocol. NTP broadcast is not used in NEMU domain.

f. If you want Tardis to reject time information from NTP servers that

claim to be unsynchronised, Select Reject unsynchronized NTP.

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

3. Modify NEMU time server settingsa. 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 (see the

previous step for details).

4. Set the system time in NEMU

a. Select the Setting the time tab in Tardis.

b. Select Set the time and adjust the scales as required.

If you do not initially trust the server you are connecting to, do not

set the system time. This gives you a chance to see first what kind of

time it is going to give you without setting NEMU's time to, for

example, 10:61 77 Jan. 1914 accidentally.

5. Set the time zone and daylight saving time

Select Set Timezone. It opens the Control Panel for Date and Time where

you can set up your timezone and whether you use daylight saving time or

not.

6. Set the HTTP proxy firewall address

Tardis may need to know the settings of the proxy server to work with the

HTTP protocol.

a. Select the HTTP proxy settings tab.

b. Enter the address of the HTTP proxy firewall.

Enter the name or IP address of the proxy/firewall server. You can

omit the http:// prefix.



RNC Integration



c. Enter the port number of the HTTP proxy firewall.

d. Set the authorisation requirements

Select User name and password needed if the proxy/firewall

requires authentication. Enter the username and password.

Example 8. Configuring Tardis for RNC

This example shows what you need to configure in Tardis during RNC

integration.

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

depends on your configuration, the name you can freely choose, 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 located and

whether you use daylight saving time or not.

2.6.7 Configuring IP address for NEMU

Purpose

The initial IP configuration has to be done locally. You only need to configure the

IP address and the subnetwork mask of NEMU. Initial configuration can also be

done via the remote management application, when preconfigured IP addresses

are in use in NEMU.

Note that you must shut down and restart the computer before the new settings

will take effect.

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



45 (183)




5. Enter the correct IP address

6. Enter the correct subnet mask

7. Enter the default gateway

8. Click OK -> OK

When you are configuring RNC NEMU via a remote management

application, the connection closes when you click OK the second time and

you lose the remote session to NEMU. If that happens, refresh the DHCP

client before continuing.

If you are configuring RNC NEMU via a local connection, refresh DHCP

client only after restarting NEMU.

9. If you lost connection to NEMU

Then

Refresh the DHCP client of the computer

Refreshing of the DHCP client of the computer depends on the operating

system:

. In Windows NT/2000:

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

menu.

b. Enter ipconfig /release and press Enter.

c. Enter ipconfig /renew and press Enter.

. In Windows 95/98:

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

menu.

b. Enter winipcfg /release_all and press Enter.

c. Enter winipcfg /renew_all and press Enter.

.

In other operating systems, refer to the instructions for the system.

10. If you are configuring RNC NEMU remotely

Then

Open the remote management application for NEMU

Enter the IP address of the NEMU server to the target address.



RNC Integration



11. Restart the computer

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

> Shut Down -> Restart.

2.7 Configuring external IP connections

2.7.1 Connecting to O&M backbone via Ethernet

Purpose

This procedure describes how to connect RNC to the external network for O&M

connections using an external router connected to the ESA12 or ESA24 Ethernet switch.

O&M connections from the RNC to the O&M backbone can also be created via

ATM virtual connections, but Ethernet is the preferred way. The O&M

connection via ATM should only be used as a backup.

Note

Even if the IP over ATM connection has been configured, the O&M traffic does

not automatically switch to using it when the Ethernet connection is down.

Before you start

Because the IP addresses for OMU, the Ethernet switch, and NEMU have been

preconfigured in the RNC, you must change the IP addresses before connecting

the RNC to the external network. Several elements in the network can have the

same preconfigured IP addresses, so if you do not change the preconfigured

addresses, there will be problems in the network.

For instructions, see Configuring IP for O&M backbone (RNC

NetAct).

Steps

1. Connect the RNC physically to the external router via ESA12/ESA24

Ethernet switch

2. Configure external router according to instructions provided by the

router vendor



47 (183)




2.7.2 Configuring IP over ATM interfaces

Purpose

For O&M connections towards NetAct, IP over ATM interfaces for OMU are

only required if the RNC is connected to the external network via ATM virtual

connections. The preferred way to connect RNC to NetAct is via Ethernet (see

Connecting to O&M backbone via Ethernet ). The IP over ATM connection

should only be used as a backup.

Note

Even if the IP over ATM connection has been configured, the O&M traffic does

not automatically switch to using it when the Ethernet connection is down.

IP over ATM interfaces must be configured in GTPU units for Iu-PS interface

between the RNC and the SGSN, and in OMU units for BTS O&M between the

RNC and the BTS/AXC.

Before you start

ATM resources must be created before this procedure is commenced. For

instructions, see Creating ATM resources in RNC in ATM Resource

Management.

Steps

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

Check that the units for which you are going to create network interfaces

are in working or spare state (WO-EX or SP-EX).

ZUSI:<unit type>;

2. Configure IP over ATM interface to the functional unit (QMF)

ZQMF:<unit type>,[<unit index>],<logical/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

in the commands of creating ATM resources.



RNC Integration



The encapsulation method can be LLC/SNAP or VCmux. If Inverse

ATM ARP is needed on this IPoA interface, the encapsulationmethod should be LLC/SNAP.

3. Assign IP addresses to the interfaces

Defining the destination IP address creates a static route in the routing table

for the IP interface.

Note

The destination IP address parameter is always mandatory.

For IPv4:

ZQRN:<unit type>,<unit index>:<interface name>,

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

For IPv6:

ZQ6N:<unit type>,<unit index>:<interface name>:[<IP

address>]:[<prefix length>]:[<destination IPaddress>];



49 (183)






RNC Integration



3 Integrating NEMU

3.1 Setting log size and overwriting parameters for NEMU logs

Purpose

The log size is changed using the Windows 2000 Event Log viewer.

You can select whether or not you wish to overwrite the log events. If you choose

not to overwrite the events, the log file will eventually fill up; to avoid this the log

information must be manually cleared every now and then (save the log

information before clearing all events, if you still need the information).

You will also receive error messages if the log file is full and the writing of log

information is therefore interrupted.

You do not have to monitor the consumption of the log file space if the log events

are overwritten. Before the log events are overwritten, NEMU log information is

automatically saved into a file in XML format, and NetAct is notified about the

new file. You may also save the information, you wish to keep, to a file at certain

intervals. For more information, see Periodic maintenance for NEMU .

Note that you are recommended to overwrite log events.

Steps

1. Set the log size

You can check and change the log size by starting the Windows 2000

Event Viewer from Start -> Settings -> Control Panel -> Administrative

Tools > Event Viewer, and then selecting Application Log and from the

Action menu selecting Properties. If log settings need to be changed, enter

new size to Maximum log size box.

Do not set the log size smaller than 1024 kB.



51 (183)

Integrating NEMU



2. Set the overwriting parameters

You can select the Overwrite Events mode locally from Application Log

Properties of your NEMU Windows 2000 Event Viewer. You must have

administrator rights in order to change the mode.

3.2 Supervising NEMU software

Purpose

NEMU SW supervision helps to keep SW processes alive and indicates stopped

or jammed applications or processes.

The supervision interval defines the time between checks on the status of processes. There are two parameters for supervision interval. Both of them have

default settings, but the parameters can be altered.

If the supervision interval is too short, it consumes too much processor time. If

the interval is too long, there is a chance that the jammed state of a process

remains unnoticed for a long time.

Note

If you change the supervision intervals, you need to shut down NEMU platform by using the Platform Manager User Interface, and then restart the NEMU

platform. See the following instructions.

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 Manager not

running

4. Click Start PM

5. Wait until the status of Platform Manager is Nemu software Running

6. Close the NEMU Platform Manager User Interface

Steps

1. Select Start -> Run



RNC Integration



2. Start the regedit by typing regedit and click OK

3. Change the interval for recovering stopped/died processes, change

LooksAliveInterval parameter

Registry address for the parameter is HKEY_LOCAL_MACHINE

\SOFTWARE\Nokia\NEMU\InstalledModules\c_core\NemuSupervision

\NemuSupervisor\CurrentVersion\Settings\LooksAliveInterval

The parameter value is in seconds, with the maximum of two digits.

4. Change the interval for recovering jammed processes, change

IsAliveInterval parameter

Registry address for the parameter is HKEY_LOCAL_MACHINE\SOFTWARE\Nokia\NEMU\InstalledModules\c_core\NemuSupervision

\NemuSupervisor\CurrentVersion\Settings\IsAliveInterval

The parameter value is in seconds, with the maximum of two digits.

3.3 Configuring NEMU system identifier (systemId)

Purpose

This procedure configures the system identifier of NEMU.

If there is only one network element under NEMU, the systemId has to have the

same value as the identifier of the network element (for example systemId = NE-

RNC-'rnc_id' or in case of MGW, for example systemId = NE-MGW-'1'). In this

scenario, the system consists of a managed network element and NEMU, which is

logically seen as part of network element itself. In this case, system identifier,

NEMU identifier and network element identifier are all the same.

Note

In MGW, the systemId value must be chosen between 1 - 4095.



53 (183)

Integrating NEMU



If there are multiple network elements under NEMU, the systemId of NEMU

must be different than the identifier of any managed network elements (for

example systemId = MD-SITE-1). In this scenario, the system consists of number

of managed network elements and NEMU, which is logically seen as separate

mediator device and not as part of any network element. In this case, system

identifier and NEMU identifier are the same and each network element has its

own identifier.

Make sure that the systemId is configured correctly, otherwise there can be

problems in sending notifications to the NetAct. Note also that the systemId must

be unique in the whole network.

Steps

1. Open %NEMUWWWROOT%\systemid.txt file to NOTEPAD editor

The value between % marks refers to an environment variable. For example

%NEMUWWWROOT% means that there is an environment variable

NEMUWWWROOT in the system.

2. Add value of the systemId to the file

The value could be for example NE-RNC-'rnc_id' or MD-SITE-'number'.

In MGW, the value must be chosen between 1 - 4095, for example NE-

MGW-'1'

3. Save the file

3.4 Configuring the RNC object

Purpose

When the RNC RNW Object Browser is first taken into use after commissioning,

the very first task is to configure the RNC by setting the required parameters. This

is done because the RNC object is the topmost object in the hierarchy, and so it

has to be created first. Please note that the RNC RNW Object Browser provides

online help to assist you in carrying out the tasks. You can access the online help

by clicking the Help button in the RNC dialogue window.

Note

If this initial phase of the configuration is not successful, the user cannot proceed

with the rest of the configuration tasks.



RNC Integration



Steps

1. Open the RNC RNW Object Browser.

A dialogue appears indicating that the RNC has not been configured.

2. Click OK.

The RNC dialogue appears.

3. Configure the RNC.

Enter values at least for the obligatory parameters marked with yellow. For

more information on parameters, see WCDMA RAS05 Parameter

Dictionary .

Note

You cannot change the value of RNC identifier afterwards.

4. Click OK to confirm operation.

Expected outcome

The general parameters of the RNC have been set.

Unexpected outcome

If in any phase of the configuration an error occurs, you must acknowledge it by

clicking OK . The parameter window where the error occurred is displayed, and

you can either modify the parameters and try again or cancel the operation.

3.5 Configuring Nokia NetAct interface with NEMU

Purpose

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

NetAct.

Steps



55 (183)

Integrating NEMU



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

Open the Task Manager in NEMU from Start -> Run -> taskmgr (or press

Ctrl+Alt+Delete and click Task Manager). Check that CORBA/IIOP

(orbixd.exe) and Session Manager (Nwi3SessionManager.exe) are up and

running.

2. Define the system identifier in NEMU

The system identifier attribute (systemId) has to be defined in the NEMU

commissioning. The systemId attribute has been saved to the text file

whose location is defined in Windows 2000 registry

[HKEY_LOCAL_MACHINE\SOFTWARE\Nokia\NEMU

\InstalledModules\c_services\nemucorbasupserv\NWI3MDCorba

\CurrentVersion\Settings].

3. Setup the required NetAct parameters to the INI-file (Nwi3MDCorba.

ini) in NEMU

a. Configure the NetAct parameters for NEMU.

i. Open %NEMUPLATFORMDATADIR%\c_services

\nemucorbasupserv\nwi3mdcorba\NWI3MDCORBA.ini file

in, for example NOTEPAD editor.

The value between % marks refers to an environment variable.

For example %NEMUPLATFORMDATADIR% means that

there is an environment variable NEMUPLATFORMDATADIR in the system.

ii. Add the value of the stringfield IOR to the

registrationServiceIOR field. (This could have been set during

setup, otherwise you can add it directly to the file.)

iii. Set the values of the registrationServiceUsername and

registrationServicePassword with NemuRegEdit tool. (These

could have been set during setup. Values are encrypted and

stored into Windows Registry.)

iv. Add value of the takeIntoUseNext parameter. This value must

be changed to 1.

v. Save the file.

b. Restart the registering service of NEMU to activate new parameter

values. There are two alternative methods to activate parameters.



RNC Integration



. Immediate activation:

i. Start NEMU Platform Manager User Interface (Start ->

Programs -> NEMU Platform Manager User Interface -

> PMUI ).

ii. Select NemuRegServApp from the list of Nonstop

Processes and click the Stop Process button.

iii. Wait until the status of NemuRegServApp is Stopped .

iv. Select again NemuRegServApp from the list of

Nonstop Processes and click the Start Process button.

v. Wait until the status of NemuRegServApp is Running .

vi. Close NEMU Platform Manager User Interface.

. Long time activation:

i. The registering service of NEMU makes theregistration itself after a variable period (usually the

default random period is approximately 10-20

minutes).

4. Check entries from the registering service of NEMU

Check from the Windows 2000 Event Viewer if there are entries from the

registering service of NEMU (NemuRegServ.dll). If there is a log writing

"NemuRegServ: Getting the IOR of the Registration service failed.", the

registering service of NEMU did not manage to get rsIOR which is needed

for registering in Nokia NetAct.

When the registering service of NEMU is up and running, there is a log

writing "NemuRegServ: Successfully registered to registration service of

NetAct."



57 (183)

Integrating NEMU





RNC Integration



4 Configuring heartbeat interval for RNC

Purpose

The management plane connections between Nokia NetAct and RNCs are

supervised with heartbeat (HB) alarms from the RNCs. Nokia NetAct uses the

heartbeat alarm from the RNC to supervise the connection in desired intervals. By

configuring the heartbeat interval, the user can change the supervision interval tocorrespond to the actual network environment.

Note

Changing the HB interval locally in the RNC MML interface is only needed if

Nokia NetAct support is not available for this feature.

Steps

1. Check the heartbeat interval value.

ZWOI:16,8;

2. Configure the heartbeat interval value.

ZWOC:16,8,<value in minutes>;

Note

The scope of the heartbeat interval value is 0~0x5A0 (HEX) in minutes. If the

heartbeat interval is configured above its scope, the system will cut it down to the

allowed maximum (0x5A0). For information on how to check the heartbeat

interval in NetAct, see Integrating RNC to NetAct in Nokia Online Services

(NOLS).



59 (183)

Configuring heartbeat interval for RNC



Expected outcome

A successful heartbeat configuration results in that the RNC sends the alarm 0599

HEARTBEAT NOTICE FOR ALARM FLOW SUPERVISION to the Nokia

NetAct.



RNC Integration



5 Configuring RNC level parameters

5.1 Defining external time source for network element

Purpose

The IP addresses used in the Commissioning stage for setting the time and date

are predefined and temporary. You will need to configure the time source IP

address again, using the DCM command, after the internal DCN network has been

configured during the integration stage.

When you have defined the external time source, in 15 minutes all the clocks in

the network element will have the same time as the external time source has. The

external time source is located in the Nokia NetAct time server. IPA2800-based

network elements check the time and date every 15 minutes, preferably against

the NEMU time server, using NTP messages.

Note

IP connections must be created before you can define the external time source in

Nokia NetAct time server.

Steps

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



61 (183)

Configuring RNC level parameters



ZDCM:<ip version>,<ip address block 1>;

Expected outcome

When you have defined the external time source, in 15 minutes all the clocks in

the network element will have the same time as the external time source has. The

internal clock located in the network element gives a time stamp for all the

functions that the computer unit does.

5.2 Creating local signalling configuration for RNC

Before you start

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

Note

Note the following in relation to the NPC command when using Nodal Function

to connect two adjacent RNCs via MGW Rel.4:

Since the signalling links are used for SCCP signalling, the value of both the

service existing for STP messages and the service existing for user part of own

signalling point parameter must be Y.

ZNPC:<signalling network>,03,SCCP:Y:Y,208,10F;

Note

In Japan, you must read the subfields of the signalling point code for commands

NRP, NSC and NRC in reverse order. This differs from the standard procedure

elsewhere. For example, in Japan, 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 be transmitted to

the network element's own user parts, or they can be switched forwards, or both.

Depending on the services configured to the network element, some of the

signalling messages are unnecessary. Data on service information determines how

the signalling messages coming into the network element are received and

switched.

Steps

a. Check that all necessary services exist (NPI)

Check that all needed services exist on the network element by using

the NPI command. The services SNM and SNT usually exist

automatically on the network element.

The needed services depends on the type and use of the network

element. In Radio Network Controller (RNC) or Multimedia

Gateway Rel.4 (MGW Rel.4) type of network elements at least the

following services are needed:

. SNM signalling network management messages

. SNT signalling network testing and maintenance messages

. SCCP signalling connection control part

. AAL2 AAL type 2 signalling protocol

b. Create the necessary services (NPC)

Use the parameters service existing for STP messagesand service existing for user part of ownsignalling point to choose whether the service is active for

the STP messages and/or to the user parts of the own signalling

point.

Check the process family identifiers from the Site Specific

Documents as there can be some exceptions to the values given in

the following example commands.

ZNPC:<signalling network>,00,SNM:Y:Y,07F,06D;

ZNPC:<signalling network>,01,SNT:Y:Y,07F,;

ZNPC:<signalling network>,03,SCCP:Y:Y,208,10F;

ZNPC:<signalling network>,0C,AAL2:Y:Y,452;



63 (183)

Configuring RNC level parameters



2. Create own MTP signalling point (NRP)

The own signalling point has to be defined before we can create the other

objects of the signalling network. Use the command NRP to create the own

MTP signalling point. A network element can be connected to several

signalling networks. The NRI command displays all existing signalling

points.

There are special network-specific parameters related to the signalling

networks, and you can output them using the NMO command. These

parameters define, for example, the congestion method used in the

signalling network. For more information about the network-specific

parameters, see SS7 signalling network parameters.

Note

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

ZNRP:<signalling network>,<signalling point code>,<signalling point name>,STP:<ss7 standard>:<numberof spc subfields>:<spc subfield lengths>;

3. Create own SCCP signalling point (NFD)

Before you start creating the signalling point, check what is the Signalling

Point Code (SPC) of the system's own signalling point by 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 only

when the parameter WHITE_BOOK_MGMT_USED (12) of the used SCCP

signalling point parameter set has value YES (check this with the OCI

command).



RNC Integration







RNC Integration



6 Configuring transmission and transport

interfaces

6.1 Configuring PDH for ATM transport

Purpose

This procedure describes how you can configure PDH/ATM interface for the

NIP1 interface unit. The mode of the PDH interface must be the same for all the

exchange terminals in the plug-in unit. That is why the NIP1 unit must be given

as a parameter when the PDH mode is configured.

Usually the existing default values for the PDH supervision are adequate and you

do not have to change them. If needed, you can configure and modify the

exchange terminal supervision parameters.

When you have configured new PETs, you may have to modify their functional

modes. Choose either E1, ETSI specific functional modes, or T1, ANSI specific

functional modes. In a fractional E1/T1/JT1 you can select the timeslots that are

used to carry user data.

Note

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

The network elements provide a synchronisation interface for external timing

reference signals. For information on synchronisation, see Configuring

synchronisation inputs in Synchronisation and Timing.



67 (183)

Configuring transmission and transport interfaces



Before you start

You must have created a functional unit description for the exchange terminals

(PET). For the instructions, refer to Creating and attaching functional unit

description in Hardware Configuration Management.

Steps

1. Interrogate the PET's current configuration (YAI)

ZYAI:PET;

2. Set the interface operation mode of NIP1 (YAE)

Set the operation mode if you want to change it. The impedance

parameter can be given only if the operation mode given is E1.

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

If you change the impedance or the operation mode, you must restart the

unit so that the changes are taken into use. See the instructions in

Restarting functional unit in Recovery and Unit Working State

Administration.

3. Modify E1 functional modes if needed (YEC)

You can first output the ETSI specific frame modes with the command

ZYEI;

If the current frame mode does not match with the frame mode of the

interface unit that is connected to the remote end of this line, you can

modify it with the command

ZYEC:<unit type>,<unit index>:NORM,(DBLF|CRC4);

Note

Double framing does not support SSM. For more information, see Configuring


4. Modify T1 functional modes if needed (YEG)



RNC Integration



You can output the ANSI specific T1 functional modes with the command

ZYEH;

If the current frame mode does not match with the frame mode of the

interface unit that is connected to the remote end of this line, you can

modify it with the command

ZYEG:<unit type>,<unit index>:(ESF|SF),(B8ZS|AMI),(0|7.5|15|22.5);

Note

T1 does not support SSM. For more information, see Configuring


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 create an

IMA group for the physical links. Configure PET (YAM) and Modify PET

timeslot usage (YAW) are repeated for each link which is selected to the

IMA group. See instructions in Creating IMA group for more information.

8. Create physical layer Trail Termination Point

See instructions in Creating PhyTTP for more information.

Example 9. Configuring PDH for ATM transport



69 (183)




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

5. Create a phyTTP with ID 2 of PET with index 9.

ZYDC:2:PET=9;

6.2 Creating IMA group

Purpose

This procedure describes how you can create an IMA group and add exchange

terminals to it. You can later connect an external ATM interface to the phyTTP

that has been created for the IMA group.

The bandwidth of the IMA group is approximately the sum of the link

bandwidths. In case of a link failure the effects of the failure depend on the

amount of bandwidth used from the IMA group and on the type of traffic, but

only if, after the link failure, the number of working links is higher than the

minimum number of links. If the number of working links is lower than the

minimum number of links after the link failure, dimensioning or type of traffic do

not matter.

If you are using the entire bandwidth of the IMA group and the traffic is

continuous, a link failure affects the traffic. If you are not using the entire

bandwidth or the traffic is not intensive, a link failure does not necessarily affect

the traffic.

The maximum allowed number for each IMA group is 8 exchange terminals. The

IMA group must be created at both ends of the physical links.

Note

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



RNC Integration



Before you start

You must have configured the PDH exchange terminals (PETs) before you create

an IMA group. For the instructions, see Configuring PDH for ATM transport .

The PETs to be combined to an IMA group must belong to the same NIP1

functional unit. Check which functional unit a PET belongs to with the USI

command.

Each PET is identified by its exchange terminal index, which is a system-wide

unique numerical value. In addition, the system assigns a link ID to each PET.

This link ID is unique in the IMA group.

One of the physical links functions as the Timing Reference Link (TRL) of the

IMA group, which is identified by its link ID PET index. 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>;

Further information

You can add more PETs later on to the group with the YBA command. The

maximum number of PETs in an IMA group is 8.

2. Create phyTTP for the IMA group

See the instructions in Creating phyTTP .

Further information

You can interrogate IMA groups with the YBI command, modify with the YBM

command, and delete with the YBD command.

It is possible to remove exchange terminals from IMA group with the YBR

command. Note that the capacity of the IMA group, that is, the system requires

the total number of links, must equal or be greater than the used capacity of the

ATM interface.

Adding/removing links automatically affects the bandwidth of the access profile

of the ATM interface.



71 (183)




Example 10. 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 group

combines PDH exchange terminals 0, 5 and 14. The minimum required

number of links in the group is 2.

ZYBC::,0&5&14:2;

2. Add the exchange terminal 12 to the IMA group 3.

ZYBA:3:12;

3. Create phyTTP for the IMA group.

ZYDC:2:IMA=3;

6.3 Configuring SDH for ATM transport

Purpose

This procedure describes how to configure the SDH/ATM interface and modify

the SDH exchange terminal (SET) configuration. You can define how the

transmission capacity is divided, and change the threshold levels for perfomance

monitoring to meet the expected quality of the transmission network.

Before you start

You must create the functional unit description for the SETs. For the instructions,

see Creating and attaching functional unit description in Hardware Configuration

Management.

Steps

1. Interrogate the SET (YAI)

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

ZYAI:<SET>,<SET index>;

2. Configure the SET (YAN)



RNC Integration



Note

This step is only necessary if you want to modify the default settings.

Note

When VC mapping is changed, the affected higher and lower order paths get their

default values.

Note that for the NIS1 and NIS1P units only one loopback status(diagnostic or line) can be on at a time.

Currently the SES BIP, SD BER, and SF BER parameters are not used for

the higher or lower order paths. The SES BIP threshold for the higher order

paths is the same as the one used for the multiplex section of the SET.

From the ATM traffic point of view the mapping mode parameter values

VC3VC11, VC3VC12, VC4VC11, and VC4VC12, and the payload

mapping mode parameter values ASYNCH, BITSYCH and BYTESYNCH

are irrelevant.

ZYAN:<SDH exchange terminal index>...,[<higher orderpath number>|<higher order path number>,<lower order

path 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|BYTESYCH];

3. Set the SDH trace (YAS)

You can set the SDH trace already during integration or later on, if

necessary. The SDH trace trail must be configured identically to both thetrails related to a specific phyTTP (logical path) in a protection group.

When you configure a trace for a trail that is part of a protection group, the

system automatically applies the changes also to the other trail of the pair

and sends a notification on this.



73 (183)




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

4. Create SDH protection group, if necessary

If you want to secure the traffic even when a line fails, you need to create

an SDH protection group. Refer to the instructions in Creating SDH

protection group.

5. Create phyTTP

Refer to the instructions in Creating PhyTTP .

Further information

You can interrogate the incoming SDH traces with the YAT command.

Example 11. Configuring SDH for ATM transport

1. Modify the SES BIP threshold of the SET 1 to 2300 frames per second. Set

the VC mapping to VC-3.

ZYAN:1:2300::::VC3;

2. Modify the SES BIP threshold of the SET 2 to 2300 frames per seconds.

Set the VC mapping to VC-3

ZYAN:2:2300::::VC3;

3. Modify the outgoing path trace of the VC path 2 of SET 1. Use 16 byte

format.

ZYAS:1,2:OUTPATH,SET16,"OUT PATH TRACE";

4. Modify the outgoing path trace of the VC path 2 of SET 2. Use 16 byte

format.

ZYAS:2,2:OUTPATH,SET16,"OUT PATH TRACE";



RNC Integration



5. Create the SDH protection group from SET 1 and SET 2 with protection

group id 4.

ZYWC:4:1,2;

6. Create phyTTP with id 10 for the path 2 of the protection group 4.

ZYDC:10:PROTGROUP=4:2:;

6.4 Creating SDH protection group

Purpose

You can create a protection group which is formed by two SDH exchange

terminals (SET). Multiplex Section trail linear protection is used to protect asingle multiplex section trail by replacing a working MS trail if it fails or if the

performance falls below required level. The supported protection protocols are

linear, bi-directional Multiplex Section Protection (MSP) 1+1 compatible with 1:

n protocol and linear, bi-directional Automatic Protection Switching (APS) 1+1.

Both of the protocols can be used either in revertive or in non-revertive mode.

The SDH trace trail must be configured identically to both trails related to a

specific logical path in a protection group. If this is not the case, the system

prevents the protection group creation.

Steps

1. Create the SDH protection group (YWC)

ZYWC:[<protection group id>|<system select> def],[<protection switching mode>|NONREV def],[<protocolvariant>|MSP def]:<Working section SDH exchange

terminal index>,<Protection section SDH exchangeterminal index>:[<wait to restore time>|300 secondsdef];

The system will ensure that both trails of a pair must be configured

identically in a protection group.

2. Create the phyTTP, if necessary

If the protected SDH interfaces are for ATM traffic transport, you need to

create a phyTTP.

See the instructions for creating the physical layer Trail Termination Point

in Creating phyTTP .



75 (183)




Expected outcome

The system generates a 0101 SDH PROTECTION SWITCHING EXECUTED

notice if the protection switch operation succeeds.

Unexpected outcome

The system generates a 3183 SDH PROTECTION SWITCHING FAILED alarm

if the protection switch operation fails.

If the far end has not been configured to support the correct SONET APS

configuration, the system generates a 3307 MISMATCH IN SONET APS

CONFIGURATIO alarm.

Further information

You can interrogate the protection group configuration and the protection

switching status information with the YWI command, modify the configuration

with the YWM command and delete the configuration with the YWD command.

Note that a protection group cannot be deleted if a phyTTP has been created for

it.

Example 12. Configuring the SDH protection group with default protectionprotocol parameter values

1. Create a protection group of SET 7 (working section) of NIS1P-1 and SET

4 (protection section) of NIS1P-0 with protection group ID 3.

Default non-revertive mode and MSP 1+1 variant are used.

ZYWC:3,,:7,4;

2. Create a phyTTP with id 3 for the path 1 of the protection group 3.


Example 13. Configuring the SDH protection group with SONET APSvariant of the protection protocol and with revertive mode

1. Create a protection group of SET 6 (working section) of NIS1P-1 and SET

3 (protection section) of NIS1P-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:6,3;



RNC Integration



2. Create phyTTP with id 4 for the path 1 of the protection group 4.


6.5 Creating phyTTP

Purpose

The Physical layer Trail Termination Point (phyTTP) is configured between the

physical layer and the ATM layer. The phyTTP ID is used when creating the

ATM interface.

You can create a phyTTP for a single PET, an IMA group, a single SDH VC path,

or a VC path of an SDH protection group.

Note

You cannot create a phyTTP for a single SDH VC path of a 2N redundant

network interface unit. The phyTTP for a 2N redundant unit must be created for

the VC path of the SDH protection group that has been created for the unit.

Before you start

You must configure the PDH or SDH interfaces (PET, SET, an IMA group, a

single SDH VC path or a VC path of an SDH protection group) before you can

create the phyTTP for them. For configuration instructions, see Configuring PDH

for ATM transport and Configuring SDH for ATM transport .

If you need to interrogate the phyTTP configuration or the operational state of the

phyTTP, use the YDI command.

Steps

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

If you created an IMA group, give the ID of the IMA group for the IMA

parameter. If you created an SDH protection group, give the ID of the

protection group for the PROTGROUP parameter.



77 (183)




Note

The MML command for creating the phyTTP includes a parameter, payload

type, for separating ATM traffic from PPP traffic. However, only ATM traffic issupported in this release.

ZYDC:<phyTTP>:(PET=<PDH exchange terminal>|IMA=<IMA

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

Further information

You can delete a phyTTP with the YDD command. After the deletion its physical

resources are free to be used again, for example, you can add PET to an existing

IMA group or you can protect SET by creating a protection group. On the other

hand, IMA/protection group can be deleted if there is no phyTTP related to it.

The phyTTP cannot be deleted if it is used by the upper layer, that is, if there is an

ATM interface created on it. You can use the YDI command to check whether the

phyTTP is in use or not.

Example 14. 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 15. Creating a phyTTP for a PET

Create a phyTTP with ID 1 of the PET with index 10.

ZYDC:1:PET=10;

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



6.6 Creating ATM resources in RNC

Purpose

This procedure provides instructions for creating ATM resources on the following

interfaces:

. Iu-CS between RNC and MGW

. Iu-PS between RNC and SGSN

. Iu-BC between RNC and CBC

. Iur between two RNCs

. Iub between RNC and BTS

Note

Use the Object Browser or NetAct when creating termination points for the Iub

interface. Normally you need the MMLs only for creating the ATM interface and

its access profile.

RNC uses MTP3 as the AAL type 2 signalling transport on all other interfaces

except on the Iub interface where SAAL UNI signalling is used.

For creating the access profile, see the information in ATM interface access

profile.

When creating termination points of CBR type, see also Basic guideline for

calculating CDVT .

Caution

When defining traffic parameter values, take into account the capacity limitations

of an ATM interface. If the resources are misconfigured, the system will reject the

creation of VP/VC connections later. See also Taking termination point into use

fails.



79 (183)




Before you start

Configure the hardware (including exchange terminals) and the physical

resources. See Physical interfaces in ATM network .

Steps

1. Create an ATM interface connected to a physical layer Trail

Termination Point (LAC)

ZLAC:<interface id>:<interface type>,<phyTTP>;

Note that the interface will be unlocked.

Table 1. Parameters and values for creating an ATM interface connected to a

physical layer Trail Termination Point

Parameter Value

interface id Select a numerical value.

If you do not set the value manually, the

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

Table 2. Parameters and values for creating the access profile of the ATM

interface

Parameter Value

interface ID As defined in step 1.

max VPI bits Select a suitable value, for example 5,

that is, the allowing VPI values from 0 to

31 to be used..



RNC Integration



Table 2. Parameters and values for creating the access profile of the ATM

interface (cont.)

Parameter Value

max VCI bits Select a value equal or greater than 6, for

example 7, that is, the allowing VCI values

from 32 to 127 to be used.

UPC/NPC mode Select whether UPC/NPC (policing) is to

be enabled or disabled for this interface.

Expected outcome

The system will select the bandwidth to fully use the capacity of the

physical resource. The printout tells the Maximum ingress

bandwidth value and Maximum egress bandwidth value used.

3. If you are creating ATM resources for the Iub interface

Then

Create ATM termination points using RNC RNW Object Browser

You have two possibilities:

When creating connection configuration for the Iub interface, see Creating

Radio Network Connection Configuration.

When creating ATM TP for IPoA connection, see Creating ATM

termination point for IP over ATM connection.

Note

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

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

You need to create VPLtps for UBR traffic (IP over ATM connection) for

the following:



81 (183)




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

ZLCC:<interface id>, <tp type>, <VPI>,,<VPL servicelevel>:<segment endpoint info>,<VP level trafficshaping>::<egress service category>,,,<egress QoSclass>:;

Table 3. 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 defined

in 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 network

planning

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 over ATM

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 defined Peak Cell Rate.

The VP level traffic shaping should be enabled to limit the peak cell rate of the

VP and thus avoid cell loss due to policing in the ATM network.

. In Iur interface, the necessary number for SS7 (MTP3SL) signalling

and routing AAL type 2 user data (AAL2UD).

ZLCC:<interface id>, <tp type>, <VPI>,,<VPL servicelevel>:<segment end point info>,<VP level trafficshaping>::<egress service category>,,,<egress QoSclass>:::<egress PCR>,<egress PCR unit>;

Table 4. 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 network

planning

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

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

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



83 (183)




. In Iu-CS interface, one VCLtp for SS7 (MTP3SL) signalling traffic.

Depending on the network planning, this may not be necessary.

. In Iu-PS interface, the necessary number for data traffic. You need at

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

traffic. You need at least one IP over ATM connection per ICSU

unit.

ZLCC:<interface id>,<tp type>,<VPI>,<VCI>::<ingressservice category>,<ingress EPD>,<ingress PPD>,

<ingress QoS class>:<egress service category>,<egress EPD>,<egress PPD>,<egress QoS class>;

Table 5. 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 the

following:



RNC Integration



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

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



85 (183)






RNC Integration



7 Configuring synchronisation inputs

Purpose

You can configure and control synchronisation with MML commands. Usually

synchronisation-related MML commands are used for setting the synchronisation

system-related parameters and also for getting information from the

synchronisation system.

By using the correct MML command, you can force the system clock to use a

synchronised operating mode or a free-run operating mode. Under certain

operating conditions, for example calibration, this is a necessary action.

You must always create synchronisation inputs when taking a network element

into use. You can change the inputs later, if needed. The following order of steps

is not obligatory.

You can check the available synchronisation references with the DYI command.

Use the DYS command to set a synchronisation reference as the forced reference

of the system clock. Notice that the forced reference can even be lost and the

operation mode of the system clock is changed to Holdover. The changes in the

quality of the other references do not affect the forced reference setting.

Whenever a synchronisation reference that is used in the synchronisation of the

system clocks, is lost, the reference is considered to be available after the WTR

(Wait To Restore) time has expired. The default WTR is five minutes.

Enable the distribution of the outgoing signal if you want to distribute the signal

outside the network element.

Set the operation mode when testing the network element. Usually this is done

automatically by the system.

Note

If you have set the operation mode to FREE, when testing the system for instance,

you have to set the mode back to SYNC. This is not done by the system.



87 (183)

Configuring synchronisation inputs



Steps

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

The highest priority value (PRI) is 1. The highest synchronisation status

message value (SSM) is 1, the lowest is 14. In addition, value 0 is used

when the quality of the reference is unknown, and value 15 is used when

the reference must not be used in synchronisation.

The SSM value is entered manually to external references. All line

references, including the PDH line interfaces, get their SSM values on line

from the frame structure of the incoming signal. You have to set parameters

for at least one synchronisation reference.

Note

PRI value must be removed from the references (it should be set to PRI=X) that

have not been actually connected to a so-called connected NIU through which the

synchronisation references are connected to the system.

Note

The Framing mode for the incoming PDH references must support the transfer of

the SSM values. For instructions about configuring the Framing mode, see

Configuring PDH for TDM transport and Configuring PDH for ATM transport .

If the Framing mode for the incoming PDH references does not support the

transfer of SSM values, the references can be set with the PRI value.

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

SSM=<ssm value>;

2. Check the automatic synchronisation setting (DYI)

When the parameters for at least one synchronisation reference with OK

status are set for the first time during system start-up, the system will

synchronise automatically. In this case you do not have to manually set the

operation mode.



RNC Integration



ZDYI:<identification of information>,

<identification of reference>;

3. Set the operation mode (DYT)

If the system clock has not locked into the reference even though the

reference is available, it can be forced to lock into the reference by using

the DYT command. This command is not normally used in the

commissioning phase and it must not be used instead of entering

parameters for a synchronisation reference.

ZDYT:MODE=<operation mode>;

4. Check the values of the WTR timers for the references (DYI)

ZDYI;

5. Modify the values of WTR timers (DYL)

The default value for the WTR timer is 5 minutes. If you want to change it,

use the parameter SET. If you want to switch it off, you need to give the

RESET command. If you want that the WTR timer is not set at all when the

used synchronisation reference is lost, use SET parameter to change the

value of the WTR timer to 0.

ZDYL: <synchronisation reference>, <reference

index>: <action>, <value>;

Note

RESET option means that the running WTR timer for a synchronisation reference

will be initialised immediately to 0 but if you want to disable the WTR timer, you

must SET the value of WTR timer to 0.

6. Check which references have been enabled

ZDYP;

7. Enable the distribution of outgoing synchronisation (DYE)

Enable the distribution of outgoing synchronisation if you want to

distribute the signal outside the network element.



89 (183)




Give the ENA value for the ACT parameter.

Note

The Framing mode for the outgoing PDH references must be such that the SSM

values can be written into it. For instructions on configuring the Framing mode,

see Configuring PDH for TDM transport and 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 of system

clock (DYS)

Use the DYS command to set a synchronisation reference as the forced

reference of the system clock. Notice that the forced reference can even be

lost and the operation mode of the system clock is changed to Holdover.

The changes in the quality of the other references do not affect the forced

reference setting.

Give the value Y for the ACT parameter.

You can release synchronisation reference as the forced reference of

system clock by giving the value N for the ACT parameter.

ZDYS:<synchronisation reference>,<reference index>:ACT=<action>;

11. Control general settings for the synchronisation system (DYR)



RNC Integration



Note

With the command DYR you can reset the switching type of references, set special

configuration, cut the outgoing external reference, or include or remove SSMvalue as selection criteria. The SSM value of the reference can be included or

removed from the selection criteria when the best reference is selected to be used

in the synchronisation of the system clocks. By default, the SSM and priority

values are used when the references are ordered. You can control whether the

SSM value is used or not during the reference selection.

Note

You must enter the parameters for the connected references to make them

available for the synchronisation system. The PRI value other than PRI=X tells

the system that the synchronisation reference is ready to be used in the

synchronisation of the system clocks. Before using it, make sure that the status of

the reference is OK.

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



91 (183)






RNC Integration



8 Creating Iub interface (RNC-BTS)

8.1 Configuring transmission and transport resources

For information on configuring transmission and transport resources, refer to

Configuring transmission and transport interfaces.

8.2 Creating radio network connection configuration

Purpose

A new logical connection configuration object (COCO) is created in order to

reserve local transmission resources for WCDMA BTS (WBTS). The COCO

object displays the transmission resources in the Iub interface but not the actual

network topology.

Note

It is possible to create a COCO without relating it to a WBTS. In such a case,

only the ATM layer is configured.

Before you start

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

Steps

1. Start creating connection configuration.

a. Select Object New Connection Configuration Iub.

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



93 (183)

Creating Iub interface (RNC-BTS)



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

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

Alternatively, connection configuration can be created using an existingconnection configuration as reference.

a. Select the connection configuration whose structure and parameters

should be used in the new connection configuration.

b. Select Object Use as reference

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

2. Click OK to continue.

Expected outcome

The RNW Connection Configuration dialogue appears.

3. Fill in parameters for each link category.

For more information on connection configuration, see Operation and

Maintenance in RN2.1.

For more information on parameters, see WCDMA RAS05 Parameter

Dictionary .

4. Click OK in the parameter dialogue to confirm the operation.

Expected outcome

The data is sent to the RNC RNW database. The data is stored in the RNC

RNW database and the ATM layer is created into the system. Control and

user plane-related resources are created into the system if the COCO object

was related to the WBTS.

5. Check the outcome of the operation and click OK.

Expected outcome

The COCO object and the corresponding ATM layer configuration is found

in the system. If the COCO creation was successful and the WBTS that the

user wanted to relate to the COCO was found, the system relates the

COCO and the WBTS objects.



RNC Integration



The WBTS object does not have to be created before the COCO object is

created. Also when the WBTS object is created afterwards, the system

relates the objects to each other in the same way that it does if the WBTS

already exists when the COCO object is created. Once the COCO and the

WBTS have been related in the RNC RNW database, the Control/User

plane configuration is done.

Unexpected outcome

Any errors are displayed in the Operation Information dialogue. If the

creation fails, continue modifying the COCO or delete the failed COCO

and start again with step 1.

Further information

Note

If the ATM layer is created with MML commands, make sure that the

administrative state of the VP/VC Link termination points is unlocked. The usage

information of the related ATM termination points should be free . If you use the

automatic ATM configuration option, the termination points are created unlocked

by default.

For further information, see Creating ATM resources in RNC and Digit analysis

and routing in RNC .

8.3 Creating ATM termination point for IP over ATMconnection

Purpose

A new ATM termination point is created in order to configure ATM layer for IP

over ATM (IPoA) connection. Please note that the RNC RNW Object Browser

provides online help to assist you in carrying out the tasks. You can access theonline help via the Help menu in the main window or by clicking the Help button

in the dialogue windows.



95 (183)




Before you start

Note

The IP over ATM configuration has to be completed with the commands defined

in the example Configuring IP over ATM interface in Creating and modifying IP

over ATM interfaces.

If the connection configuration object (COCO) and IPoA have the same VPLtp,

the COCO has to be created first. This is to ensure that the underlying VPLtp is

created for CBR traffic class

Steps

1. Select Object New Connection Configuration IP over ATM

TP.

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

3. Set the wanted PCR value for defining the desired bandwidth for 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 created in the

system. The IPoA link is not, however, working as a result of this.

Unexpected outcome

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



RNC Integration



8.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). The alternate ways to configure IP for BTS O&M are detailed below:

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

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

By using star topology, O&M connections can use the same VPI as control plane

traffic. The VPI connection must then be configured as CBR class. This also

means that if the O&M VCI is configured to UBR class, it can use the same

maximum capacity that is the bit rate for VPI.

You should use the dedicated VPI for O&M traffic in the tree model so that the

O&M connection can use the free capacity of the link more easily.

For more information on the topologies, see the Nokia WCDMA RAN System

Information Set.

You can use either static routing or dynamic routing (OSPF) for BTS O&M. If

you use OSPF, you do not need to configure static routes towards the BTSs.

When you create the OSPF configuration, the routes are automatically created

after the configuration.

With OSPF, you must use unnumbered interfaces towards the BTS, because the

AXC only supports unnumbered interfaces. If you have numbered point-to-point

interfaces with static routing in use and you want to activate OSPF also to these

interfaces, you must modify the interface type. For instructions on how to modify

point-to-point interfaces, see Creating and modifying IP interfaces in IP

Connection Configuration for RNC.

Before you start

You need to create ATM resources for the Iub interface before this procedure is

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

O&M connection for dedicated BTS in OMU. Check if the VPI/VCI termination

point is already created for the control plane. By default, the same VPI

termination point is used as the control plane traffic for BTS. The VPI is

configured as CBR class.



97 (183)




You also should have ATM plans available for the tree or star model DCN for

O&M. For more information, see Creating ATM resources in RNC in ATM

Resource Management.

Steps

1. Start the MMI Window from the Element Manager

For instructions, see Using EM MMI window in Element Manager

Administration.

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

It is recommended to use unnumbered interfaces towards BTS because

point-to-point links do not need IP subnets specified for the link. This also

helps in planning and configuring the IP network when IP subnets are not used with point-to-point links.

For instructions, see Configuring IP over ATM interfaces.

3. If you are using static routing

Then

Create static route for BTS O&M

For O&M connections towards BTS, configure the route from OMU to the

IP address of the gateway that is on the other side of the point-to-point

ATM connections (AXC address of BTS site).

All static routes configured for active units must also be created in the

spare unit.

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

type>];

4. If you are using OSPF

Then

Configure OSPF area parameters and interfaces



RNC Integration



a. Define the OSPF parameters of an OSPF router.

The area identification specifies the area ID for a new OSPF. The

area ID is entered as a dotted-quad. The IP network number of a

subnetted network may be used as the area ID. It is recommendedthat all OSPF areas except the backbone be configured as totally

stubby areas.



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

The default value for router dead interval parameter in AXC

is 120. Because the value must be the same in both AXC and RNC,

change the value of the router dead interval parameter to

120 in RNC.ZQKF:<unit type>,<unit index>:<interfacespecification>:<area identification>:[<hello

interval>]:[<router dead interval>]:[<ospfcost>]:<[election priority>]:[<passive>]:[<authentication> | <password>];

Further information

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

This example presents IP for BTS O&M configuration in RNC when star

topology ATM layer and dynamic routing (OSPF) is used.



99 (183)




Figure 5. Example of IP configuration for BTS O&M when star topology and

OSPF are used

1. Create IP interfaces towards every BTS in OMU.

Assign logical IP addresses to the unnumbered point-to-point network

interfaces of the OMU unit, with MTU value 1500.

ZQRN:OMU: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;

...

NEMU

RNC

RNC Element

Manager

EL0 10.1.1.2/28 (logical)

AA1 10.1.1.2/32

unnumbered lines


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



ZQRN:OMU:AA31,U:10.1.1.2,L::10.1.32.1:1500:UP;

ZQRN:OMU:AA32,U:10.1.1.2,L::10.1.33.1:1500:UP;

2. Create an IP over ATM interface between the IP interface and the ATMtermination point.

Configure an IP over ATM interface with network interface names AA1...

AA32 using the same VPI as control plane traffic, and with VCI 32.

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


...



3. Configure OSPF area parameters of an OSPF router for the BTS branch.

ZQKE:OMU,0:10.1.2.0:Y,,Y;

ZQKE:OMU,1:10.1.2.0:Y,,Y;

4. Configure the OSPF interface parameters of an OSPF router.

ZQKF:OMU,0:AA1:10.1.2.0::120;

ZQKF:OMU,1:AA2:10.1.2.0::120;

...

ZQKF:OMU,0:AA31:10.1.2.0::120;

ZQKF:OMU,1:AA32:10.1.2.0::120;

Example 18. Configuring IP for BTS O&M using tree topology ATM layer

This example presents IP for BTS O&M configuration in RNC when tree

topology ATM layer and static routing are used.

1. Create IP interfaces towards the BTS in OMU.

Assign logical IP addresses and destination IP addresses to the

unnumbered point-to-point network interfaces of the OMU unit, with MTU

value 1500, and accept default values for the rest of the parameters.

ZQRN:OMU:AA1,U:10.1.1.2,L::10.1.2.1:1500:UP;

ZQRN:OMU:AA2,U:10.1.1.2,L::10.1.3.1:1500:UP;



101 (183)




2. Create an IP over ATM interface between the IP interface and the ATM

termination point.

Configure a TCP/IP ATM interface with network interface names AA1 (to

OMU from ATM interface 1) and AA2 (to OMU from ATM interface 2)using VPI 0 and VCI 32 and accept default values for the rest of the

parameters.



3. Create static routes for the BTS branch.

Create static routes for OMU to the IP subnetworks 10.1.2.0/24 and

10.1.3.0/24 via the router with IP addresses 10.1.2.1 and 10.1.3.1.

ZQKC:OMU,0:10.1.2.0,24:10.1.2.1:LOG;

ZQKC:OMU,0:10.1.3.0,24:10.1.3.1:LOG;



RNC Integration



9 Creating Iu-CS interface (RNC-MGW)




9.2 Configuring signalling channels

9.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 with great care,

see SS7 network planning principles.

The SS7 signalling configuration is needed for the following interfaces.

. Iu-CS interface, between MGW and RNC. The configuration is based on

ATM.

. Iur interface, between RNC and RNC; nodal functionality in MGW (see

Figure AAL bearer establishment from RNC 1 to RNC 2 for illustration).

The configuration is based on ATM.

. Iu-PS interface, between RNC and SGSN. The configuration is based on

ATM.

Before you start

Before you start to create signalling links, check that the SS7 services and the

MTP signalling point have been created. For instructions, see Creating local

signalling configuration for RNC .



103 (183)

Creating Iu-CS interface (RNC-MGW)



Steps

1. Check that the signalling links are distributed evenly between different

ISUs

Use the following command to display the existing signalling links.

ZNCI;

It is recommended that you allocate signalling links between all working

ISU units to distribute the load. Also, it is very important that signalling

links belonging to the same linkset are allocated to different ISU units to

avoid the whole linkset to become unavailable in an ISU switchover

2. Create signalling links (NCN/NCS)

To create ATM signalling links, give the command:

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

Note

Before creating ATM signalling links, check that there are free VCLtps available

and that they are correctly configured. For instructions, see Create VCLtps for CBR traffic in Creating ATM resources in RNC .

Remember to use the WFI command to check that the network element is

adequately equipped before you start creating signalling links.

It is advisable to create the signalling links belonging to the same

signalling link set into different signalling units, if this is possible. This

way a switchover of the signalling unit does not cause the whole signalling

link set to become unreachable.

The parameter set related to the signalling link can be used to handle

several of the signalling link timers and functions. If the ready-made

parameter packages do not cover all occurring situations, you can create

more parameter sets, modify the relevant parameters and then attach the

new parameter set to the signalling link. It is advisable to find out if there



RNC Integration



will be such special situations before you start configuring the MTP. See

Signalling link parameters. The following are two examples of special

situations in TDM signalling links that require modifications in the

parameter set:

. One of the signalling links goes via satellite, and the level 2 error

correction method has to be preventive_cyclic_retransmission

instead of the usual basic_method.

. National SS7 specification defines some of the timer values so that

they are different from the general recommendations.

Note

The Signalling Link Code (SLC) and the Time Slot (TSL) have to be defined so

that they are the same at both ends of the signalling link.

You can number the signalling links within the network element as you wish. The

default value for the number is always the next free number.

To interrogate existing signalling links, use the NCI or NEL command.

The parameter set related to the signalling link can be used to handle

several of the signalling link timers and functions. If the predefined

parameter sets do not cover all occurring situations, you can create more

parameter sets, modify the relevant parameters and then attach the new parameter set to the signalling link.

3. Create SS7 signalling link set (NSC)

Create a signalling link set for each destination.

A signalling link set consists of one or several links. The signalling links

belonging to the signalling link set cannot be activated until the signalling

link set is connected to a signalling route set.

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

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



105 (183)




To interrogate the existing signalling link sets, use the NSI or NES

command.

4. Create signalling route set to MGW (NRC)

When a signalling route set is created, a parameter set is attached to it. The

parameter set can be used to handle several MTP3 level functions. If the

predefined parameter sets do not cover all occurring situations, you can

create more parameter sets, modify the relevant parameters and then attach

the new parameter set to the signalling route set. See Signalling route set

parameters.

Create a signalling route set for each destination.

You can create all signalling routes that belong to the same route set at the

same time with the same command. Later you can add signalling routes to

a route set with the NRA command.

ZNRC:<signalling network>,<signalling point code>,<signalling point name>,<parameter set number>,<loadsharing status>,<restriction status>:<signalling

transfer point code>,<signalling transfer pointname>,<signalling route priority>;

The parameters signalling transfer point code and

signalling transfer point name are used when the created

signalling route is indirect, that is the route goes via signalling transfer point (STP). There is no need to use those two parameters when the RNC

is directly connected to the MGW.

Note

A signalling point cannot be used as an STP unless it is first equipped with a

direct signalling route.

For more information about signalling route set priorities, see SS7 network

planning principles.

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

5. Create signalling route set to MSS via MGW (NRC)

Create a signalling route set for each destination.



RNC Integration



You can create all signalling routes that belong to the same route set at the

same time with the same command. Later you can add signalling routes to

a route set with the NRA command.

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

The route goes via MGW which is working as a signalling transfer point

(STP) when the created signalling route is indirect.

The parameters signalling transfer point code and

signalling transfer point name are the same as the MGW's

signalling point code and the name of the MGW.

9.2.2 Activating MTP configuration

Steps

1. Allow activation of the signalling links (NLA)

Use the following command to allow the activation of previously created

signalling links:

ZNLA:<signalling link numbers>;

2. Activate the signalling links (NLC)

Use the following command to activate the previously created signalling

links:

ZNLC:<signalling link numbers>,ACT;

The signalling links assume either state AV-EX (active) or UA-INS in case

the activation did not succeed. Activation may fail because links at theremote end are inactive or the transmission link is not working properly.

For more information, see States of signalling links.

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

NEL.

3. Allow activation of the signalling routes (NVA)



107 (183)




Use the following command to allow the activation of previously created

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 signalling routes:

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

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

commands.

When you are dealing with a direct signalling route, the signalling route set

assumes the state AV-EX if the related link set is active; otherwise it

assumes the state UA-INS. A signalling route going through an STP can

also assume the state UA-INR if the STP has sent a Transfer Prohibited

(TFP) message concerning the destination point of the route set. For more

information, see States of signalling routes.

Example 19. Example of activating an MTP configuration

In this example, you change the state of a signalling route which is leading to the

signalling point 302. The route is defined in the signalling point 301 that is

located in the national signalling network NA0.

First, you change the signalling route state to ACTIVATION ALLOWED, and

then you can take the signalling route into service.

ZNVA:NA0,302:;

The execution printout can be as follows:

A L LO W IN G A C TI V AT I O N O F S I GN A LL I NG R O U TE

DESTINATION : SP RO UTE S: SP

NET SP C ODE H /D NAME NET SP C OD E H/D NAME

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

NA0 03 02/ 00 77 0 MSS2 NA0 03 02 /0 077 0 MSS2 ACTIVATION A LLOWE D

C O M M A ND E X E C U TE D

After this, you use the NVC command to activate the route:



RNC Integration



ZNVC:NA0,302::ACT;

The execution printout can be as follows:

C H A N G IN G S I G N A LL I N G R O U T E S T A T E

DESTINATION: SP ROU TE S: S P OLD NEW

NET SP CODE H/D NAME NET SP CODE H /D NAME STATE STATE PRI O

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

NA0 0302/ 00770 MSS2 NA0 03 02/00 77 0 MSS2 UA-INU AV-EX 2


9.2.3 Setting MTP level signalling traffic load sharing

Purpose

With MTP level signalling traffic load sharing you can share the signalling traffic between signalling routes and between signalling links belonging to the same link

set.

Within a signalling link set, load sharing is implemented so that it automatically

covers all links that are in active state.

Load sharing between signalling routes takes effect only after you have allowed

load sharing by defining the same priority for all signalling routes and by

allowing load sharing in that route set.

Before you start

Before setting the load sharing, plan carefully which kind of load sharing is

suitable in the signalling network. For more information, see MTP level

signalling network .

See also Modifying MTP level signalling traffic load sharing .

Steps

1. Check signalling route priorities and load sharing status, if needed

(NRI)

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

2. Check MTP load sharing data (NEO)

Check which signalling links transmit each of the Signalling Link

Selection Field (SLS) values.



109 (183)




You can use this command to separately interrogate the load sharing data

concerning either messages generated by the own signalling point or STP

signalling traffic.

Notice that the load sharing system is different for STP traffic according to

the ANSI standards.

ZNEO:;

3. Modify signalling route priority, if needed (NRE)

The priority can vary between 0-7, the primary priority being 7.

ZNRE:<signalling network>,<signalling point code>:<signalling transfer point network>,<signallingtransfer point code>,<new signalling route priority>;

4. Allow load sharing in the signalling route set, if needed (NRB)

If you want to activate the load sharing, and it is not allowed in the

signalling route set (output of the NRI command), you have to change the

load sharing status.

ZNRB:<signalling network>,<signalling point codes>:

LOAD=<load sharing status>;

9.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 all necessary

hardware has been installed on the network element, and that the Message

Transfer Part (MTP) has already been configured.

Verify the following items:



RNC Integration



. Check that the signalling points have been created on the MTP (the NRI

command) and the services are available for the SCCP (the NPIcommand).

.

Check which parameter set is used, and whether there is need to modify thevalues of the existing parameter sets to meet the present conditions and

requirements (the OCI command).

. Check which subsystems are used.

. Check the data on subsystem parameter sets (the OCJ command), and the

possible modifications on them (the OCN command).

. Check that the SCCP service has been created on the MTP level.

Before you can create the SCCP to the network element, the SCCP service

has to be created first. To check that the service has been created, use the

NPI command. If there is no SCCP service created on the MTP level,create it with the NPC command (more information in Creating remote

MTP configuration).

Note

The SCCP management subsystem (SCMG) is automatically created when you

create the SCCP for the signalling point.

Note

The subsystems which use the Transaction Capabilities are configured in a similar

way, and no further configuration is needed (as the TC is automatically used for

suitable subsystems).

Steps

1. Create remote SCCP signalling points and subsystems (NFD)

In addition to creating the SCCP signalling point and its subsystems, you

also need to define the other SCCP signalling points and the subsystems of

the other SCCP signalling points of the network, which are involved in

SCCP level traffic.



111 (183)




ZNFD:<signalling network>, <signalling point code>,

<signalling point parameter set>: <subsystem number>,<subsystem name>, <subsystem parameter set number>,Y;

You can later add more subsystems to a signalling point by using the NFBcommand. The system may need new subsystems for example when new

services are installed, software is upgraded or network expanded.

When you are adding subsystems, you need to know which parameter set

you want the subsystems to use or which one has to be used.

You can display the existing parameter sets by using the OCJ command.

When you want to modify the parameters, use the OCN command, and to

create a new parameter set, use the OCA command.

2. Create translation results, if necessary (NAC)

The translation result refers to those routes where messages can be

transmitted. All the signalling points that are meant to handle SCCP level

traffic must be defined at a signalling point.

At this stage you have to decide whether the routing is based on global title

(GT) or on subsystem number.

ZNAC:NET=<primary network>,DPC=<primary destination

point code>,RI=<primary routing indicator>;

If you want to have a back-up system for routes or the network, you can

create alternative routes that will then be taken into service in case the

primary route fails. Also it is possible to use load sharing for up to 16

destinations by giving value YES for parameter <load sharing>.

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

Before creating the global title analysis, check the number of the

translation result so you can attach the analysis to a certain result. Use the

NAI command.

For more information about global title analysis, see SS7 network planning

principles.

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



RNC Integration



4. Set broadcast status (OBC, OBM)

Note

This step is not used for MGW.

There are two different kind of broadcasts you can set (it is recommended

that you set both of them):

. The local broadcast status (the OBC command) is used to inform the

subsystems of the own signalling point about changes in the

subsystems of the remote signalling points.

.

The remote broadcast status (the OBM command) is used to informother signalling points about changes in the subsystems of the own

signalling point or the subsystems of the signalling points connected

to the own signalling point.

When you set local broadcasts, remember that the remote network

elements also have to be configured so that they send the status data to

your network element.

Note

When setting the broadcasts, consider carefully what broadcasts are needed.

Incorrect or unnecessary broadcasts can cause problems and/or unnecessary

traffic in the signalling network.

Depending on the network element, the subsystems needing the broadcast

function are the following:

. BSSAP Base Station System Application Part

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



113 (183)




Remote broadcasts:

ZOBM:<network of affected subsystem>,<signallingpoint code of affected subsystem>,<affected subsystem

number>:<network of concerned signalling point>,<concerned signalling point code>:<status>;

For more information, see SCCP level signalling network .

9.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, only remote

SCCP signalling points have to be activated.

To check that the signalling point really is active, use the NFI command.

In the command printout, the state of the signalling point should be AV-

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

MTP level. You can also display the states of SCCP signalling points also

by using the NGI command. Notice that if you use the default values in thecommand, only the signalling points of network NA0 are shown. For more

information, see States of SCCP signalling points.

Example 20.

When you examine an example system using the NFI or NGI commands, all

signalling points should be in normal state AV-EX. Note that the signalling point

101H cannot be seen because the SCCP is not defined in it.

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

S C C P S T A T E S

DESTINATION : SP RO UT ING : SP

NET S P COD E H/ D NAME S T AT E RM N ET S P CODE H/D NAME S TATE

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

NA0 0 10 2/002 58 PSTN2 A V - NA0 0102/ 00258 PSTN2 AV-EX

NA0 0 30 1/007 69 RNC1 OWN SP

NA0 0 30 2/007 70 MSS2 AV - NA0 03 02/ 00 770 MSS2 AV-EX

NA0 0 31 1/007 85 RNC1 AV - NA0 03 11/ 00 785 RNC1 AV-EX



RNC Integration



NA0 0 312 /0 07 86 BSC2 A V - NA0 0312/ 00786 BSC2 AV-EX


2. Activate remote SCCP subsystems (NHC)

ZNHC:<signalling network>, <signalling point codes>:<subsystem>:ACT;

To display the subsystem states, use the NHI or NFJ command.

When remote subsystems are being activated, their status is not checked

from the remote node. The remote subsystem status becomes AV-EX if the

remote node is available, although the actual subsystem may be

unavailable or even missing. The status of the unavailable subsystem will

be corrected with the response method as soon as a message is sent to it.

Use the NHI command to check that the subsystems have assumed state

AV-EX. If not, the reason may be faulty or missing distribution data.

Correct the distribution data and check the state again. Another reason for

the subsystems not to be operating is that the subsystem at the remote end

is out of service.

For more information, see States of SCCP subsystems.

3. Set the SS7 network statistics, if needed

By setting the SS7 network statistics, you can monitor the performance of

the SS7 network. You do not have to do it in the integration phase, you can

do it later.

9.3 Configuring Iu-CS parameters of RNC

Before you start

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

Note

If the Nokia multi-operator RAN feature is in use, you have to create and

configure one Iu-CS interface per operator.



115 (183)




Note

If the IMSI-based handover is in use, you can configure up to four PLMN 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 signalling

parameters and the identification parameter of the core network element.

Also fill in all RANAP-related parameters. For more information on

parameters, see WCDMA RAS05 Parameter Dictionary .

Note

If there are cells under this core network that are already using the Global

PLMNid parameter, their value cannot be changed.

3. Check the value of the digit analysis tree.

Note

Once you have created digit analyses with an MML, do not change the value of

digit analysis tree from the GUI.



RNC Integration



9.4 Creating routing objects and digit analysis for Iuinterface in RNC

Purpose

This procedure describes how to create routing objects for the Iu interface with

MML commands. The associated signalling used is broadband MTP3 signalling.

The routing objects must be created at both ends of the Iu interface between two

network elements before any user plane connections can be built between them.

The analysis tree for configuring the Iu interface is set by using the RNC RNW

Object Browser application.

Note

When creating digit analysis, you must add an Authority and Format Identifier

(AFI) before the digit sequence in order to avoid conflicts with different number

formats. AFI indicates the format of AESA number (the first byte of AESA). If,

for example, AFI is 49, add digits 4 and 9.

Before you start

Before you create routing objects, make sure that the appropriate signalling

(broadband MTP3) has been created and the associated VC link termination

points (VCLtps) for the endpoints have been created. Furthermore, the route

under which the endpoints are to be created must allow these type of the

endpoints.

Steps

1. Create an AAL type 2 route (RRC)

ZRRC:ROU=<route number>,TYPE=<route type>:PRO=<protocol>:NET=<signalling network>,SPC=<signalling point code>,ANI=<aal2 node

identifier>;

The ANI must be identical for all routes with the same SPC and the same

signalling network.

2. Create an endpoint group (LIC)

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



117 (183)




The ingress and egress service categories should always be Constant Bit

Rate (CBR).

3. Check that there is a free VCLtp (LCI)

ZLCI:<interface id>,VC:<VPI>:FREE;

Of these VCIs, all those with the service category CBR in both directions

can be used in the next step.

4. Create an endpoint (LJC)

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

The system will automatically sort this endpoint into the endpoint group of

step 2 since their service categories match.

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

Note

You must create a corresponding routing structure (steps 1-4) in the remote

(PEER) network element before you can proceed to step 5. The ownership

property of a certain AAL type 2 path must be different in both ends of theconnection; if this end of the connection has LOCAL ownership value, the other

end must have PEER ownership value and vice versa. The AAL type 2 pathidentifier must have the same value in both ends of a certain connection.

5. Unblock the AAL type 2 path (LSU)

The endpoints must have been created at both ends of the interface before

the AAL type 2 path between them can be unblocked.

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

Expected outcome

The execution printout followed by the unblocking should indicate that

both the local end and the remote end of the AAL type 2 path are in an

unblocked state.



RNC Integration



Unexpected outcome

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

command.

Unexpected outcome

If the remote end has not agreed unblocking,

Then

verify that the remote end is working properly and that it can be

reached. Then repeat the command. As long as the remote end cannot

agree to unblocking an AAL type 2 path, the system will not select it.

6. Create digit analysis (RDC)

Create a digit analysis for a specific digit sequence. Add an AFI before the

digit sequence in order to avoid conflicts with different number formats.

Check that the analysis tree has been set for the Iu interface by using the

RNC RNW object browser.

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

Note

The address identifies the location of a network termination point. ATM End

System Adresses (AESAs) are defined by ATM Forum. AESA consists of Initial

Domain Part (IDP) and Domain Specific Part (DSP) and it is always 40 digits

long. The IDP specifies an administration authority which has the responsibility

for allocating and assigning values of the DSP.

The first two digits of IDP are called Authority and Format Identifier (AFI). The

AFI indicates the type of AESA that will follow. The last part of IDP is the actual

IDP address. The leading zeroes of AESA numbers are used as padding digits to

fill up the address. A trailing F(s) are used to obtain octet (2 digits) alignment or

to make the number left justified.

The leading zeroes and trailing F(s) are removed before creating a digit analysis.

This is important because, when system analyses received digits a corresponding

conversion is made. If digit analyses are created otherwise, the correct, matching

analysis result cannot be found.



119 (183)




. E.164 AESA

E.164 part of E.164 AESA is the 16 digits after AFI (45). E.164 part

may include leading zeroes and/or a trailing F. The rest of the

number is DSP part.. DCC AESA

DCC part of DCC AESA is 4 digit ISO country code after AFI (39).

DCC part may include F(s). The rest of the number is DSP part.

. ICD AESA

ICD part of ICD AESA is 4 digits after AFI (47). ICD part may

include F(s). The rest of the number is DSP part.

The following changes in the format of numbers must be taken into account when

handling analyses:

.

E.164 ATM format (AFI = 0 x 45)

- Zeros between AFI and the following non-zero digit are

removed.

- The 16th digit of E.164 part (F digit) is removed.

- Example: 45000000358951121F --> 45358951121

. DCC ATM format (AFI = 0 x 39)

- The fourth digit (F digit) is removed.

- Example: 39123F1234 --> 391231234

. ICD ATM format (0 x 47)

- Possible F digits are removed from the ICD part of the

number (F digits are removed from digits 1-4).

- Example: 47123F1234 --> 471231234

Example 21. Create routing objects for Iu interface

1. Create an AAL type 2 route. The route number is 13, the protocol is

Message Transfer Part Level 3, the signalling network is NA0, the

signalling point code is 24, and the AAL type 2 node identifier 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 is

automatically selected by the system. The termination points in this group

have the Constant Bit Rate service category for both ingress and egress

directions.



RNC Integration



ZLIC:13:C,C;

3. Check that there is a free VCLtp under the VPLtp(s).

ZLCI:5,VC:<VPI>:FREE;

Note that you can check all the available VPIs. Out of these VCIs all those

with service category CBR in both directions can be used in the next step.

4. Create a VCC endpoint (VCCep) under the route 13 created in the first

step. The AAL type 2 path is 11. The interface ID is 5, VPI 12, and VCI

1045. The current network element owns the AAL type 2 path. The AAL

type 2 loss ratio is 10 5 and the AAL type 2 multiplexing delay 3 ms.

ZLJC:VC,13,11:5,12,1045:LOCAL:5,30;



Note



property of a certain AAL type 2 path must be different in both ends of the

connection; if this end of the connection has LOCAL ownership value, the other

end must have PEER ownership value and vice versa. The AAL type 2 path

identifier must have the same value in both ends of a certain connection.

5. Unblock the AAL type 2 path 11. The ANI is AAL2HEL1 and the allowed

waiting time for the execution of the blocking command is 18 seconds.

ZLSU:AAL2HEL1:11:18;

6. Create digit analysis without charging for a digit sequence 491234 in

analysis tree 25.

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



121 (183)






RNC Integration



10 Creating Iu-PS interface (RNC-SGSN)





Please refer to Configuring signalling channels.

10.3 Configuring Iu-PS parameters of RNC

Before you start


Note

If the Nokia multi-operator RAN feature is in use, you have to create and

configure one Iu-PS interface per operator.

Note


core item.



123 (183)

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 signalling

parameters and the identification parameter of the core network element.

Also fill in all RANAP-related parameters. For more information on


Note

If there are cells under this core network that are already using the Global

PLMNid parameter, their value cannot be changed.

10.4 Configuring IP for Iu-PS (RNC-SGSN)

Purpose

The purpose of this procedure is to configure IP for the Iu-PS interface between

the RNC and the Serving GPRS Support Node (SGSN).

Before you start

The ATM resources must be created before the interface can be configured. For

instructions, see Creating ATM resources in RNC in ATM Resource

Management.

Steps

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

Check that the units for which you are going to create network interfacesare in working state (WO-EX).

ZUSI:<unit type>;

2. Create IP over ATM interfaces to all GTPUs



RNC Integration



Create IPoA interfaces to all GTPUs (at least one ATM VCCs per GTPU)

according to instructions in Configuring IP over ATM interfaces. Set the

value of the encapsulation method parameter to LLC/SNAP.

If dedicate a GTPU for real-time IP traffic, set the value of usage parameter to IPOART (this is an optional feature) for all IPoA interfaces of

the unit. If not, set the value to IPOAUD.

3. Configure the default static routes

You do not need to specify the destination IP address for the default route.

For IPv4:

ZQKC:<unit type>,<unit index>::<IP address>:[<routetype>];

For IPv6:

ZQ6C:<unit type>,<unit index>:[<destination IPaddress>],[<prefix length>]:[<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>]:<ip address>:[<routetype>];

For IPv6:

ZQ6C:<unit type>,<unit index>:[<destination IP

address>],[<prefix length>]:[<next hop type>]:<address type>:(IP=<ip address> | MAC=<link level mac

address>);

5. Create OSPF configuration, if necessary

Currently, OSPF only supports IPv4. If you want to use OSPF routing on

the Iu-PS interface, create the configuration as follows:



125 (183)




a. Set the IP address for loopback.

ZQRN:<unit type>,<unit index>:<interface name>:<IP address>;

b. Configure the OSPF to inform other OSPF routers of the loopback

address.

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

c. Configure the area(s) that include also the neighbouring routers.



d. Configure an interface for that area.

ZQKF:<unit type>,<unit index>:<interface

specification>:<area identification>:[<hellointerval>]:[<router dead interval>]:[<ospfcost>]:<[election priority>]:[<passive>]:

[<authentication> | <password>];

6. Create QoS DiffServ configuration (GTPU), if needed (with service

terminal extension)

It is also possible to configure QoS DiffServ traffic classification to GTPU

units. The main function for IP QoS DiffServ is to assure that real time (rt)

traffic has a higher throughput priority than non-real time (nrt) traffic in the

GTPU TCP/IP stack. It checks that the traffic is real time or non-real timeand processes the traffic with the desired ratio.The configuration is done

with the service terminal extension QMDSTEGX in OMU.

If you decided to use QoS DiffServ for the Iu-PS interface, make the

configuration as follows:

a. Take a service terminal session to working OMU with MML.

ZDDS:OMU,<unit index>;

b. Load service terminal extension QMDSTEGX.

ZLE:<desired number>, QMDSTEGX;

c. Configure desired NRT/RT ratio.

ZxB: <NRT/RT ratio>;

d. Configure desired DSCP values.

ZxC:<DSCP>,<traffic class>;

Example 22. QoS DiffServ configuration for Iu-PS with each GTPU



RNC Integration



connected to one SGSN unit

This example shows how to configure QoS DiffServ classification to GTPU

units. The default traffic class for all DSCPs is non-real time (nrt). The

configuration in the example DSCPs will be set to real time. The same

configuration will be set for all GTPU units. After DSCP is configured, the values

2, 15, 21, 33, 39 and 54 are real time (rt) and the remaining values are non-real

time (nrt). Real time (rt) and non-real time (nrt) packet ratio will be set with the

value 8. This means that 8 real time packets are processed with one non-real time

packet. If the number of real time packets is less than 8, the non-real time packets

will be processed after all the real time packets have been processed.

a. Take a service terminal session to OMU and load QMDSTEGX

ZDDS:OMU,0;

ZLE:7,QMDSTEGX; b. 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:28

Example 23. IP configuration for Iu-PS with each GTPU connected to oneSGSN unit

This example shows how to configure the Iu-PS interface between the RNC and

SGSN using two STM-1 interfaces in both RNC and SGSN. In the example, four

GTPU units are deployed to handle the Packet Switched Radio Access Bearers in

the RNC in load sharing mode. Each GTPU is logically connected to one of the

SGSN units, GPLCs. Two IP subnets are used:

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

. 10.1.2.0/32 for hosts connected to the second GPLC.



127 (183)




Figure 6. 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, see Creating

ATM resources in RNC in ATM Resource Management):

. STM-1 ATM interface (with interface ID 1). This interface is

connected to SGSN (GPLC-1) via a direct physical connection or

via the SDH transmission network.

.

In ATM interface 1, one VPLtp with VPI=0.. In ATM interface 1, two VCLtps with VPI=0 and VCI=40, 41.




. In ATM interface 2, one VPLtp with VPI=0.

. In ATM interface 2, two VCLtps with VPI=0 and VCI=42, 43.

2. Create IP over ATM interfaces to all GTPUs.

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



a. Create IP over ATM interfaces connected to subnet 10.1.1.0/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.0/32

(GPLC-2).



3. Assign IP addresses to the network interfaces.

a. Configure interfaces connected to subnet 10.1.1.0/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.0/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 GPLC unit

in the SGSN.

ZQKC:GTPU,0::10.1.1.1:PHY;




Example 24. IP configuration for Iu-PS with GTPUs connected to bothSGSN units


SGSN using two STM-1 interfaces in RNC and SGSN. In this example, four

GTPU units are deployed to handle the Packet Switched Radio Access Bearers in

RNC in load sharing mode. Each GTPU is logically connected to both GPLCunits in the SGSN so that even if one link fails, the interface capacity between the

RNC and SGSN remains the same. Note that the same redundancy can be

achieved by using OSPF instead of static routing (see the next example).

Two IP subnets are used:



129 (183)




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

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

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

Figure 7. ATM virtual channel connections and IP addresses with GTPUs

connected to both GPLC units








. 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

= default route

10.1.2.1

10.3.0.1

GPLC-2

10.1.1.1

10.2.0.1

GPLC-1

AA0

AA1GTPU-0

AA0

AA1GTPU-1

AA0

AA1GTPU-2

AA0

AA1GTPU-3

10.1.2.10 10.3.0.1

10.1.1.10 10.2.0.1

10.1.1.11 10.3.0.1

10.1.2.11 10.2.0.1

10.1.1.12 10.2.0.1

10.1.2.12 10.3.0.1

10.1.1.13 10.3.0.1

10.1.2.13 10.2.0.1



RNC Integration






.

In ATM interface 2, one VPLtp with VPI=0.. In ATM interface 2, four VCLtps with VPI=0 and VCI=40...43.



(GPLC-1).






(GPLC-2).






Note that the destination address of the IP over ATM interface does not

have to be the IP address of the next hop. The IP address and destination IPaddress of the IP over ATM interface can be from different 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.




131 (183)







Note

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

Example 25. Configuring Iu-PS when OSPF is in use


SGSN using OSPF for routing. When OSPF is in use and a link fails, the user

plane traffic is switched to the working link.



RNC Integration



Figure 8. Iu-PS configuration with OSPF in use




. STM-1 ATM interface (with interface ID 0). This interface isconnected to SGSN (GPLC-1) via a direct physical connection or







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

SGSN

10.1.2.1

10.3.0.1

GPLC-2

10.1.1.1

10.2.0.1

GPLC-1

= subnet 10.2.0.1/32

= subnet 10.3.0.1/32

= default route

RNC

AA0

AA1GTPU-0

10.1.2.10 10.1.2.1

10.1.1.10 10.1.1.1

LO0 10.1.1.2

AA0

AA1GTPU-2

10.1.2.12 10.1.2.1

10.1.1.12 10.1.1.1

LO0 10.1.1.4

AA0

AA1GTPU-3

10.1.1.13

10.1.2.13

10.1.1.1

10.1.2.1

LO0 10.1.1.5

AA0

AA1GTPU-1

10.1.1.11 10.1.1.1

10.1.2.11 10.1.2.1

LO0 10.1.1.3



133 (183)








(GPLC-1).






(GPLC-2).






Note that the destination address of the IP over ATM interface does not

have to be the IP address of the next hop. The IP address and destination IP

address of the IP over ATM interface can be from different subnets.


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;

4. Create the OSPF configuration.

a. Set the loopback IP address for each unit.

ZQRN:GTPU,0:LO0:10.1.1.2;




RNC Integration





b. Configure the OSPF to inform other OSPF routers of the loopback

address.

ZQKU:GTPU,0:IF=LO0;

ZQKU:GTPU,1:IF=LO0;

ZQKU:GTPU,2:IF=LO0;

ZQKU:GTPU,3:IF=LO0;

c. Configure the area(s) that include also the neighbouring routers.

ZQKE:GTPU,0:0.0.0.1;

d. Configure two interfaces for that area. The values for parameters

area identification, hello interval, and routerdead interval must be the same as in the SGSN.

ZQKF:GTPU,0:AA0:0.0.0.1;

ZQKF:GTPU,0:AA1:0.0.0.1;



135 (183)






RNC Integration



11 Creating Iur interface (RNC-RNC)





Please refer to Configuring signalling channels.

11.3 Configuring Iur parameters of RNC

Before you start

The Iur interface must be created for each neighbouring RNC. The maximum

amount of RNC Iur interfaces is 32.


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 neighbouring RNCs

as well as the SS7 related signalling parameters. For more information on


3. Check the value of the digit analysis tree.



137 (183)

Creating Iur interface (RNC-RNC)



Note

Once you have created digit analyses with an MML, do not change the value of

the digit analysis tree from the GUI.

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

Purpose

This procedure describes how to create routing objects and digit analyses for theIur interface with MML commands. The analysis tree used for configuring the Iur

interface is set by using the RNC RNW object browser application.

Note

When creating digit analysis, you must add an Authority and Format Identifier

(AFI) before the digit sequence in order to avoid conflicts with different number

formats. AFI indicates the format of AESA number (the first byte of AESA). If,

for example, AFI is 49, add digits 4 and 9.

Before you start

Before you create routing objects, make sure that the appropriate signalling

(broadband MTP3) has been created and the associated VC link termination

points (VCLtps) for the endpoints have been created. Additionally, the route

under which the endpoints are to be created must allow the type of the endpoints.

Steps

1. Create an AAL type 2 route (RRC)

ZRRC:ROU=<route number>,TYPE=AAL2:PRO=<protocol>:NET=<signalling network>,SPC=<signalling point

code>,ANI=<aal2 node identifier>;

The ANI is to be identical for all routes with the same SPC and the same

signalling network.



RNC Integration



2. Create an endpoint group (LIC)

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

The ingress and egress service categories should always be Constant Bit

Rate (CBR).

3. Check that there is a free VCLtp (LCI)

ZLCI:<interface id>,VC:<VPI>:FREE;

Out of these VCIs all these with the service category CBR in both

directions can be used in the next step.

4. Create an endpoint (LJC)

ZLJC:<ep type>,<route number>,<connection id>:<interface id>,<VPI>,<VCI>:<ownership>:[<loss

ratio>,<mux delay>];



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

Note






5. Unblock the AAL type 2 path (LSU)

The endpoints must have been created at both ends of the interface before

the AAL type 2 path between them can be unblocked.

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



139 (183)




Expected outcome

The execution printout followed by the unblocking should indicate that

both the local end and the remote end of the AAL type 2 path are in

unblocked state and the state has been agreed with the remote end.

Unexpected outcome

If the AAL type 2 path is still in blocked state,

Then

repeat the unblocking command

Unexpected outcome

If the remote end has not agreed to unblocking,

Then

verify that the remote end is working properly and it can be reached.

Then repeat the command. As long as the remote end cannot agree to

unblocking an AAL type 2 path, the system will not select it.

6. Create digit analysis (RDC)

Create a digit analysis without charging for a specific digit sequence. Addan AFI before the digit sequence in order to avoid conflicts with other

number formats. The analysis tree has been set for the Iur interface by

using the RNC RNW object browser.

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

Note

The address identifies the location of a network termination point. ATM End

System Adresses (AESAs) are defined by ATM Forum. AESA consists of Initial

Domain Part (IDP) and Domain Specific Part (DSP) and it is always 40 digits

long. The IDP specifies an administration authority which has the responsibility

for allocating and assigning values of the DSP.



RNC Integration



The first two digits of IDP are called Authority and Format Identifier (AFI). The

AFI indicates the type of AESA that will follow. The last part of IDP is the actual

IDP address. The leading zeroes of AESA numbers are used as padding digits to

fill up the address. A trailing F(s) are used to obtain octet (2 digits) alignment or

to make the number left justified.

The leading zeroes and trailing F(s) are removed before creating a digit analysis.

This is important because, when system analyses received digits a corresponding

conversion is made. If digit analyses are created otherwise, the correct, matching

analysis result cannot be found.

. E.164 AESA

E.164 part of E.164 AESA is the 16 digits after AFI (45). E.164 part

may include leading zeroes and/or a trailing F. The rest of the

number is DSP part.

. DCC AESA

DCC part of DCC AESA is 4 digit ISO country code after AFI (39).

DCC part may include F(s). The rest of the number is DSP part.

. ICD AESA

ICD part of ICD AESA is 4 digits after AFI (47). ICD part may

include F(s). The rest of the number is DSP part.

The following changes in the format of numbers must be taken into account when

handling analyses:

. E.164 ATM format (AFI = 0 x 45)

- Zeros between AFI and the following non-zero digit are

removed.

- The 16th digit of E.164 part (F digit) is removed.

- Example: 45000000358951121F --> 45358951121

. DCC ATM format (AFI = 0 x 39)

- The fourth digit (F digit) is removed.

- Example: 39123F1234 --> 391231234

. ICD ATM format (0 x 47)

- Possible F digits are removed from the ICD part of the

number (F digits are removed from digits 1-4).

- Example: 47123F1234 --> 471231234

Example 26. Create routing objects and digit analysis for Iur interface



141 (183)




1. Create an AAL type 2 route between two RNCs. The route number is 13,

the protocol is Message Transfer Part Level 3, the signalling network is

NA0, the signalling point code is 35, and AAL type 2 node identifier is

AAL2HEL1.

ZRRC:ROU=13,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=35,ANI=AAL2HEL1;

2. Create an endpoint group under route 13. The endpoint group ID is

automatically selected by the system. The termination points in this group

have the Constant Bit Rate service category for both ingress and egress

directions.

ZLIC:13:C,C;

3. Check that there is a free VCLtp.

ZLCI:5,VC:<VPI>:FREE;

Note that you can check all the VPIs available. Out of these VCIs all those

with service category CBR in both directions can be used in the next step.

4. Create an endpoint of VC level (VCCep) under the route 13 created in the

first step. AAL type 2 path is 11. The interface ID is 5, VPI 12, and VCI

1045. The current network element owns the AAL type 2 path. The AAL

type 2 loss ratio is 10 5 and the AAL type 2 multiplexing delay 3 ms.

ZLJC:VC,13,11:5,12,1045:LOCAL:5,30;

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

Note






5. Unblock the AAL type 2 path 11. The ANI is AAL2HEL1 and the allowed

waiting time for the execution of the blocking command is 18 seconds.

ZLSU:AAL2HEL1:11:18;

6. Create digit analysis without charging for a digit sequence 491234 in

analysis tree 24.



RNC Integration



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

12 Creating Iu-BC interface (RNC-CBC)


For information on configuring transmission and transport resources, refer toConfiguring transmission and transport interfaces.

12.2 Configuring Iu-BC parameters of RNC

Before you start

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

Note

If several operators share an RNC, the number of cell broadcast centres (CBC)

that can be configured for the RNC is 4. In case there is only one operator, there is

only one CBC.

Note


core item.

Steps




143 (183)

Creating Iu-BC interface (RNC-CBC)



2. Fill in and check CBC-related parameters.

Fill in and check CBC-related data, that is, IP addresses and Global PLMN

IDs. For more information on parameters, see WCDMA RAS05 Parameter

Dictionary .

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

Purpose

The purpose of this procedure is to configure IP for the Iu-BC interface between

the RNC and the Cell Broadcast Center (CBC).

All user data and signaling (SABP) traffic goes through the same ICSU units.You must configure one VCC and one static route towards the CBC for the

selected ICSU unit. Static routes are needed only in the case when the CBC is not

directly connected to the RNC (for example, router is connected between the

RNC and the CBC). In case of ICSU switchover IP over ATM interface, IP-

address and static route will move to the new unit.

Before you start

The ATM resources for Iu-BC need to be created before this procedure is

commenced. For instructions, see Creating ATM resources in RNC in ATM

Resource Management.

Steps

1. Check the selected ICSU unit towards the CBC

The RNC allocates the ICSU unit for the CBC when the CBC reference

data is created to the RNC configuration. You can check the selected ICSU

(logical address for the selected ICSU) from the RNC RNW Object

Browser's RNC dialog and core network tab.

For further information of the parameter please refer to the WCDMA

RAN04 Parameter Dictionary documentation: RNC - CBList - CBCItem -ICSUforCBC.

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

ZUSI:ICSU;

2. Create the IP over ATM interface to selected ICSU



RNC Integration



Create the IP over ATM interface to seleted ICSU towards the CBC

according to instructions in Configuring IP over ATM interfaces.

If you want to distribute incoming traffic between several ICSU units, then

create as many IP over ATM interfaces as needed (one separate IP over

ATM interface for each used ICSU) towards the CBC. In this case, only

selected ICSU unit is sending RNC originated Restart and Failure

messages towards the CBC. The CBC must be configured to send data to

different IP addresses, that is, to different ICSU units.

When assigning an IP address to the ICSU unit, assign a logical IP address

to the unit by giving value L to the IP address type parameter.

If you want to configure several IP over ATM interfaces towards the CBC

(distributing incoming traffic between several ICSU units), give the

network interface parameter a different value in all units, value L tothe IP address type parameter, and assign a different IP address to

each unit.

The destination IP address is the address of the router interface or

the CBC interface which terminates the VCC.

3. Create a static route for Iu-BC

For Iu-BC connections towards the CBC, configure one static route with

route type "LOG" for selected ICSU to the IP address of the router

terminating IP over ATM PVCs. Static routes are needed only in the casewhen the CBC is not directly connected to the RNC.

Note

Only static routes can be configured for ICSU units. Static routes are only

required for ICSUs if any of the IP packets have a different destination address

than the IP address of the CBC (for example, if a router is used between the RNC

and CBC), and they are to be transferred via the VCC.

For IPv4:

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

For IPv6:



145 (183)




ZQ6C:<unit type>,<unit index>:[<destination IP

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

Example 27. Configuring IP for Iu-BC through ICSU units

The following figure shows an example of IP configuration for Iu-BC interface

with IPv4 and IPv6 addresses. The ICSU-0 is selected to be use towards the CBC.

Figure 9. Example of IPv4 configuration for Iu-BC

The following examples show how to configure the IP for the Iu-BC interface

between the RNC and the CBC. The ICSU-0 is selected to be used towards the

CBC. The Iu-BC PVCs are configured to the STM-1 interface between the RNC

and the MGW. The IPoA PVCs are terminated in a router. The PVCs can also be

terminated in the CBC, if it is located in the same site.

For IPv4 case:

ICSU-1

ICSU-2

ICSU-18

...

RNC

NIS

STM-1

MGW

VP

crossconnects

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



RNC Integration



1. Create ATM resources as instructed in Creating ATM resources in RNC in

ATM Resource Management.

2. Create IP over ATM interfaces connected to subnetwork 10.1.1.0/32 to

selected ICSU.

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

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.10,L:32:10.1.1.200;

4. Create a static route for selected ICSU.

With the following default routes, all traffic is forwarded to the router

terminating IP over ATM PVCs.

ZQKC:ICSU,0::10.1.1.200:LOG;

For IPv6 case: with the same figure, replace the IPv4 address "10.1.1.0" with

IPv6 address "3FFE:1200:3012:C020:580:8FFF:FE7A:7BB7" and the IPv4

address "10.1.1.200" with IPv6 address "3FFE:1200:3012:C020:580:8FFF:

FE7A:4BB4".

1. Create ATM resources as instructed in Creating ATM resources in RNC in

ATM Resource Management.

2. Create IPv6 over ATM interfaces connected to subnetwork to selected

ICSU.

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

Note: The ICSU-0 is selected to be used towards the CBC.

3. Assign an IPv6 address to the selected ICSU.ZQ6N:ICSU,0:AA1:"3FFE:1200:3012:C020:580:8FFF:FE7A:7BB7",L:128:"3FFE:1200:3012:C020:580:8FFF:FE7A:4BB4";

4. Create a static route for each ICSU.



147 (183)




With the following default routes, all traffic is forwarded to the router

terminating IP over ATM PVCs. A static route is needed for each ICSU

because during the ICSU switchover static route is not switching to the

new unit.

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

ZQ6C:ICSU,1::GW:IP="3FFE:1200:3012:C020:580:8FFF:

FE7A:4BB4";

...

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



RNC Integration



13 Configuring radio network objects

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

cell definitions.

Steps

1. Select Object New Freq. Meas. Control intra/inter/inter-

system.

2. Fill in parameters.

For information on parameters, see WCDMA RAS05 Parameter

Dictionary .


Expected outcome

The data is sent to the RNC RNW database. An Operation Information

dialogue appears indicating the status of the operation and possible errors.

4. Check the outcome of the operation and click OK to close the

Operation Information dialogue.

Expected outcome

A new FMC object is created.

Unexpected outcome



149 (183)

Configuring radio network objects




creation fails, you are asked if you want to return to the creation dialogue

to modify the parameters and try again. You can also click Cancel to

cancel the operation.

13.2 Creating handover path

Purpose

A new logical handover path object (HOPS, HOPI, HOPG (optional)) is created

so that its parameters can be utilised in adjacent WCDMA cell definitions.

Steps

1. Select Object New Handover Path intra/inter/inter-system.



Dictionary .


Expected outcome

The data is sent to the RNC RNW database.

An Operation Information dialogue appears indicating the status of the

operation and possible errors.



Expected outcome

A new handover path object is created.

Unexpected outcome


creation fails, you are asked if you want to return to the creation dialogue

to modify the parameters and try again. You can also click Cancel to

cancel the operation.



RNC Integration



13.3 Creating a WCDMA BTS site

Purpose

A new logical WBTS object is created in order to manage a physical WCDMA

BTS (WBTS) site and to increase the system capacity.

Before you start

There are two ways of creating a WCDMA BTS site: one is to use system

defaults and the other is to use a reference site. The step-by-step instructions

below apply to both kinds of creation procedures.

1. Creating a WCDMA BTS site using system defaults:

System defaults refer to a range of predefined values which are used in

order to speed up the WBTS creation procedure. You still have to fill in

identification information for the WCDMA BTS and other required

parameters for which there are no default values. You are not limited to

default values; once a parameter has been given a default value, you can

change it if necessary.

2. Creating a WCDMA BTS site using a reference site:

. To use a reference WCDMA BTS site to aid you in the creation of a

WBTS, click the Site References button. A dialogue with a list of

existing WCDMA BTS sites will appear.

. Select the WCDMA BTS that you want to use from the list.

When you use a reference site, all possible parameters are copied

from the reference site to the new one. You still have to fill in values

for those required parameters which could not be copied from the

reference WBTS. You are not limited to the copied values; once a

parameter value has been copied from the reference WBTS, you can

change it if necessary. When you use a reference WBTS site to set

up a new site, the topology of the reference site (WCDMA cells and

their parameters) is also copied to the new site as an initial

configuration. The new site does not have to have the same number

of cells as the reference site, that is, the user may add and delete cells

as needed.

Note

The logical objects in the RNC RNW database are hierarchically related to each

other, and the hierarchy dictates the order in which it is possible to create new



151 (183)




objects. WCEL objects are always created under a certain WBTS object, never

independently. However, the user does not have to create all WCEL objects that

should belong to a WBTS at once; it is possible to change the configuration at a

later stage, for example by adding WCEL objects to a WBTS object.

Note

A frequency measurement control (FMC) object has to be created in advance, if

WCDMA cells are created in the WBTS creation procedure.

Steps

1. Select Object New WCDMA BTS.

Expected outcome

A New WBTS Site dialogue appears.

2. If you want to, select a reference WBTS site.



Dictionary .

Note

Identify the transmission resources by giving the desired COCO identification or

the ATM interface/VPI/C-NBAPVCI triplet. If the COCO is found in the system,

the WBTS is connected to it during the creation procedure. The COCO can also

be created later on. The reference to COCO object can also be left empty.

4. If you want to add a WCDMA cell

Then

Click Add WCEL.



RNC Integration



Fill in parameters. For information on parameters, see WCDMA RAS05

Parameter Dictionary .

Note

If you add WCDMA cells in a locked state, the WCDMA BTS is not taken into

active traffic before the WCDMA cell states are changed to an unlocked state. For

more information, see Locking and unlocking a WCDMA cell .

5. If you want to remove a WCDMA cell

Then

Select WCEL from the WBTS Site tree.

Click Remove WCEL.


Expected outcome


A Site Creation Confirmation dialogue appears.

7. Click OK in the Site Creation Confirmation dialogue to confirm the

operation or CANCEL to cancel it.

Expected outcome


operation and possible errors. The progression of the operation is

displayed.



Expected outcome

The new WBTS site is created. The WCDMA BTS can be taken into active

traffic once it has been successfully connected to the logical COCO object

(that is, transmission resources).

Unexpected outcome



153 (183)




If the user gives a reference to a COCO object, the reference should only

point to a COCO object which is not in use at the time. In other words, no

reference to a COCO object which is already related to a WBTS will be

made.

Any errors are displayed in the Operation Information dialogue. The

parameter window where the error occurred is displayed, and you can

either modify the parameters and try again or cancel the operation.

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

locked and is not used in active traffic until you have changed its state to

unlocked.

Steps

1. Start creating the WCDMA cell.

a. Select a parent WCDMA BTS for the WCDMA cell.

b. Select Object New WCDMA cell.

Alternatively, the WCDMA cell can be created using an existing WCDMA

cell as reference.

a. Select the WCDMA cell whose parameters should be used in the

new cell.

b. Select Object Use as reference.

c. Select the WCDMA BTS to which the WCDMA cell should be

created.




RNC Integration



a. Browse through the parameter tabs and fill in every mandatory

parameter.

b. Specify FMCS, FMCI and FMCG for real time, non-real time and

HSDPA separately on the HC tab. Note that FMCG can only bedefined if the inter-system handover feature is activated and HSDPA

FMCs only if the HSDPA feature has been activated.


Dictionary .


Expected outcome






Expected outcome

A new WCDMA cell is created.

Unexpected outcome

Any errors are displayed in the Operation Information dialogue. If the creation

fails, you are asked if you want to return to the creation dialogue to modify the

parameters and try again. You can also click Cancel to cancel the operation.

13.5 Creating an internal adjacency for a WCDMA cell

Purpose

A new logical adjacency object [ADJS/ADJI] for WCDMA cell is created to

define a new neighbouring cell. Adjacencies for cells controlled by the same

RNC are called internal adjacencies.



155 (183)




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 system information

block (SIB) type 11 and 12. SIB11 and SIB12 messages can contain information

on a maximum of 96 cells, but the physical size of SIB data (no more than 3552

bits) has capacity only for 47 cells when all used optional information elements inSIB11 are in use and 35 cells if HCS is used.

If the system information data exceeds 3552 bits, the scheduling of the system

information blocks fails. The cell is blocked by the system and an alarm 7771

WCDMA CELL OUT OF USE (BCCH scheduling error) is reported for the cell.

Steps

1. Select a parent WCDMA cell for the adjacent WCDMA cell.

2. Select Object New Adjacency intra/inter.

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 related parameters

are automatically defined. You can also insert Target UTRAN Cell

identity of the target cell as well as identification parameters for the

RNC manually.

b. Specify whether the adjacency should be bidirectional or not.



RNC Integration



The default value is outgoing. The selected WCDMA cell is acting

as source cell in case of adjacencies.

c. Specify handover paths for real time, non-real time and HSDPA

separately.

Note

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

d. Specify whether the adjacency should be included in the system

information messages or not.

All adjacent cells are used in measurement control even if the

adjacency is not included in the system information.

Further information

For more information on parameters, see WCDMA RAS05 Parameter Dictionary .


Expected outcome






Expected outcome

If you chose to create a bidirectional adjacency, both an outgoing and an

incoming adjacency are created; otherwise only an outgoing adjacency is created.

Unexpected outcome






157 (183)




13.6 Creating an external adjacency for a WCDMA cell

Purpose

A new logical adjacency object [ADJS/ADJI/ADJG (optional)] for WCDMA cell

is created to define a new neighbouring cell. External adjacencies refer to

adjacency relationships between cells controlled by different RNCs.

Before you start

Note

There is a limitation in sending neighbour cell information in system information

block (SIB) type 11 and 12. SIB11 and SIB12 messages can contain information

on a maximum of 96 cells, but the physical size of SIB data (no more than 3552 bits) has capacity only for 47 cells when all used optional information elements in

SIB11 are in use and 35 cells if HCS is used.

If the system information data exceeds 3552 bits, the scheduling of the system

information blocks fails. The cell is blocked by the system and an alarm 7771

WCDMA CELL OUT OF USE (BCCH scheduling error) is reported for the cell.

Steps

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

identification parameters for the external RNC manually.

b. For external adjacencies, define only the outgoing adjacencies.

c. Specify handover paths.



RNC Integration



Note

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

d. Specify whether the adjacency should be included in the system

information messages or not.

All adjacent cells are used in measurement control even if the

adjacency is not included in the system information.

Further information

For more information on parameters, see WCDMA RAS05 Parameter Dictionary .


Expected outcome






Expected outcome

An outgoing adjacency is created.

Unexpected outcome






159 (183)






RNC Integration



14 Printing alarms

14.1 Printing alarms using LPD protocol

Before you start

To print out the alarms, you must first configure the LPD printers and define their

TCP/IP address.

Steps

1. Check that the needed LPD printers have been created (INI)

If the desired LPD can be found from the printout, check that the settings

are correct. IP address should be set and the functional state should be

normal.

If the LPD is not shown in the printout, continue to step 2. If the settings

are not correct, continue to step 4. If the settings are correct, continue to

step 6.

Note

Check that the index number of the VPP is the same as the index number of the

LPD given when configuring the printers.

It is recommended to direct the alarms to the VPP devices whose index is less

than 50.

ZINI;

2. If the LPD is not shown in the printout

Then



161 (183)

Printing alarms



Create the LPD device

For instructions, see Creating a printer .

3. Check that the printer state, the LPD index and the IP address are

correct (INI)

The field FUNCTIONAL STATE in the printout shows the printer state.

The printer state in the execution printout should be NORMAL.

The LPD index number should be the same as the VPP index number.

ZINI;

4. If the printer state is not NORMAL

Then

Change the printer state to NORMAL (INS)

ZINS:<device index>:NORMAL;

5. If the settings are not correct

Then

Modify the printer settings (INM)

ZINM:<device index>:;

6. Connect the logical file to the desired I/O device (IIS)

After connecting the logical file, the alarms are printed out to the desired I/

O device.

To print out all the alarms to the desired I/O device, connect the logical file

ALARMS to the I/O device. To print out only certain kind of alarms to the

desired I/O device, connect the suitable logical files to the I/O device. For

more information on the logical files used with alarms, see Alarm printing and its management .

If you are directing the alarms to VPP, pay special attention that the VPP

index in the command is the same as the LPD index given when

configuring the printers.



RNC Integration



Note

To print out the alarms via LPD, it is recommended to direct the alarms to the

VPP devices whose index is less than 50.

ZIIS:,:<logical file name>,:DEV=<current objectidentification>:DEV=<new object identification>;

Example 28. Printing out the alarms to the desired I/O device

In this example, two and three star communications alarms are directed to VPP-1.

This example assumes that the printers are configured and their TCP/IP address is

configured. And VPP-99 has been connected to logical file ALACOMM1(IIS).

1. Display the printer state and check that the value of the field

FUNCTIONAL STATE in the printout is NORMAL. Check that the TCP/

IP address is correct.

As you want to direct the alarms to VPP-1, check that the index number of

LPD is 1.

2. The alarm system writes two and three star communications alarms to the

logical file ALACOMM1. Connect ALACOMM1 to the correct alarm

output device.

When giving the command, pay special attention to the correct index

number.

ZIIS:,:ALACOMM1,:DEV=VPP-99:DEV=VPP-1;

14.2 Printing alarms via Telnet terminal or Web browser

Purpose

You can display the alarms to a Telnet terminal or to a Web browser. Use a Telnet terminal or a Web browser, when you want to display the alarms instantly on the

computer screen over TCP/IP.

Before you start

To print out the alarms via Telnet terminal or a Web browser, you need to be

familiar with the logical files used with alarms, and their tasks.

Steps



163 (183)

Printing alarms



1. Check that the IP address of the computer unit has been defined (QRI)

ZQRI;

If the IP connection is not defined, see Creating and modifying IP

interfaces.

2. Check that the logical files used in printing out alarms are connected

to correct VPP devices (IID)

To ensure that all alarms are printed out via a Telnet terminal or a Web

browser, check the connection between each of the logical files and the

desired VPP device. For more information on logical files, see Alarm

printing and its management .

ZIID::<logical file name>,:;

If all the logical files listed above are connected, to at least VPP-99, go to

step 4.

If the logical files are not connected to VPP-99, VPP-98, VPP-97, VPP-96

or VPP-95, go to step 3.

Note

Note that if all the logical files are connected to VPP-99, one remote session for alarm printing can be established. If the logical files are connected to two VPP's,

for example, VPP-99 and VPP-98, two simultaneous sessions for alarm printing

can be established.

VPP-99 serves the first connection that is established and VPP-98 serves the

second connection and so on.

3. Connect the logical files used in printing out alarms to correct VPP

devices (IIS)

If you want to print out all the alarms to the same window, connect VPP-99

to every alarm-related logical file.

If you want to print out only certain alarms, for example, two and three star

alarms, connect the logical files used with these alarms and correct VPP

devices (VPP-99, VPP-98, VPP-97, VPP-96 or VPP-95). Note that a

logical file can have a maximum of four targets.



RNC Integration



If you want to replace the existing I/O device with a new one, use the

parameter IND=<current object index>. If this parameter is not

given, the new I/O device is simply added but does not replace the

previous I/O device.

ZIIS::<logical file name>::DEV=VPP-<I/O deviceindex>;

ZIIS::<logical file name>:IND=<current object

index>:DEV=VPP-<I/O device index>;

Note that after connecting the logical files associated with alarms to the

correct devices, you do not need to touch these connections during the

lifetime of the software build. You can print out the alarms as described in

step 4.

4. Establish a Telnet or HTTP connection to OMU IP address, port

11111

If you are using a Telnet terminal, press the Enter key once, after you have

connected to the correct address and port.

If you are using a Web browser, simply connect to the correct address and

port; no extra keystrokes are needed.

Expected outcome

The alarms that occur in the network element from that moment on are

displayed on the Telnet terminal or on the Web browser.

5. Check the state of corresponding VPP devices (IHI)

The connection for alarm printing is established, if the working state of the

VPP devices corresponding to the Telnet or HTTP sessions is WO-EX.

The working state of the VPP devices not reserved for any connection is

BL-EX.

ZIHI::VPP;

If the VPP device which you connected is not in the WO-EX state, alarms

are not printed via Telnet/HTTP. The connection for alarm printing is not

established, or it is disconnected.



165 (183)

Printing alarms



To re-establish the connection for alarm printing via Telnet or HTTP, start a

new connection to OMU, port 11111 from a Telnet terminal or Web

browser.

6. End the session when you are ready

You can stop the printing of alarms via Telnet or HTTP by simply closing

the Telnet 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 remote

connections to NetAct

Instructions

Configuring IP for O&M backbone (RNC NetAct)

Configuring IP stack in OMU

Instructions


Creating and modifying DNS configuration

Modifying IP parameters

Creating and modifying IP interfaces



167 (183)

Related Topics



Creating OSPF configuration for O&M connectionto NetAct

Instructions


Modifying OSPF configuration

Configuring static routes for the O&M connection

to NetAct

Instructions


Creating and modifying static routes

Configuring ESA12

Instructions


Configuring ESA24

Instructions




RNC Integration



Configuring NEMU for DCN

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





169 (183)

Related Topics



Configuring Tardis 2000 NT 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



Setting log size and overwriting parameters for NEMU logs

Descriptions

NEMU logs

Supervising NEMU software

Descriptions

NEMU software supervision and recovery

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)



171 (183)

Related Topics



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

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



RNC Integration



Creating IMA group

Descriptions

IMA, Inverse Multiplexing for ATM

Configuring SDH for ATM transport

Descriptions

SDH transmission

Creating SDH protection group

Descriptions

SDH transmission

Creating phyTTP

Descriptions

Physical layer Trail Termination Point


Instructions

Inspecting synchronisation system



173 (183)

Related Topics



Synchronisation fails

Configuring transmission and transport resources


Creating IMA group



Creating phyTTP

Creating ATM resources in RNC

Creating radio network connection configuration

Instructions


Modifying radio network connection configuration parameters

Creating ATM termination point for IP over ATMconnection

Instructions




RNC Integration



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

Instructions

IP connection configuration for RNC



Creating IMA group



Creating phyTTP



Instructions

Creating local signalling configuration for RNC

Setting MTP level signalling traffic load sharing

Activating MTP configuration


Instructions




175 (183)

Related Topics




Instructions



Instructions

Creating local signalling configuration

Activating SCCP configuration


Instructions

Creating local signalling configuration


Configuring Iu-CS parameters of RNC

Instructions


Descriptions

RNC interfaces



RNC Integration



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



Creating IMA group



Creating phyTTP


Configuring signalling channels

Instructions




177 (183)

Related Topics







Configuring Iu-PS parameters of RNC

Instructions


Descriptions

RNC interfaces

Configuring IP for Iu-PS (RNC-SGSN)

Instructions

IP configuration for Iu-PS interface



Creating IMA group



Creating phyTTP



RNC Integration




Configuring signalling channels

Instructions






Configuring Iur parameters of RNC

Instructions


Descriptions

RNC interfaces




179 (183)

Related Topics



Creating routing objects and digit analysis for Iur interface in RNC

Descriptions

Analysis and routing objects in ATM network


Instructions

Creating routing objects and digit analysis for Iu interface in RNC



Creating IMA group



Creating phyTTP


Configuring Iu-BC parameters of RNC

Instructions




RNC Integration



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

Creating handover path

Instructions


Modifying handover path parameters

Creating a WCDMA BTS site

Instructions




181 (183)

Related Topics



Creating a WCDMA cell

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


Instructions




Modifying WCDMA cell adjacencies



RNC Integration




Instructions




Modifying WCDMA cell adjacencies

Related Topics