IP Connection Configuration for RNC

IP Connection Configuration forRNC

DN02143138Issue 11-2 en17/09/2007

# Nokia Siemens Networks 1 (137)

RNC3267Nokia WCDMA RAN, Rel. RAS06, SystemLibrary, v. 3

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

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

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

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

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

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

Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (137) # Nokia Siemens Networks DN02143138Issue 11-2 en

17/09/2007

IP Connection Configuration for RNC

Contents

Contents 3

Summary of changes 5

1 Overview of IP connection configuration 111.1 IP connection configuration for RNC O&M 111.2 OMS TCP/IP network 131.3 IP configuration for Iu-PS interface 161.4 IP configuration for Iu-BC interface 19

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

NetAct 242.3 Configuring IP stack in OMU 252.4 Creating OSPF configuration for O&M connection to NetAct 292.5 Configuring static routes for the O&M connection to NetAct 352.6 Configuring ESA12 372.7 Configuring ESA24 392.8 Configuring OMS for DCN 432.8.1 Configuring OMS for DCN 432.8.2 Checking the calendar time in OMS 472.8.3 Configuring the DHCP server in OMS 482.8.4 Configuring the DNS client in OMS 492.8.5 Configuring OMS to RNC 502.8.6 Configuring NTP services in OMS 532.8.7 Configuring OMS system identifier 542.8.8 Configuring IP addresses for OMS 562.9 Connecting to O&M backbone via Ethernet 582.10 Connecting to O&M backbone via ATM interfaces 59

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

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

5 Configuring Signalling Transport over IP for Control Plane 79

6 Configuring IP for Iu-BC (RNC-CBC) 81

7 Creating and modifying DNS configuration 87

8 Creating and modifying IP interfaces 91

9 Modifying IP parameters 97

10 Creating and modifying IP over ATM interfaces 101

11 Modifying OSPF configuration 105

DN02143138Issue 11-2 en17/09/2007


Contents

12 Creating and modifying static routes 109

13 Creating and modifying IP QoS configuration 113

14 IP configuration files 11714.1 IP configuration files 11714.2 Modifying IP configuration files 122

15 Connection to IP application from remote host fails 125

Related Topics 133


17/09/2007


Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes between issues 11-0 and 11-2

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

"QMF" MML command was updated.

Changes between issues 11-0 and 11-1

IP connection configuration for RNC O&M

. In the figure information on NEMU has been replaced withcorresponding information on OMS.

. In 'Instructions' section NEMU has been replaced with OMS in link.

. Standalone SMLC (SAS) has been added to the second chapter.

OMS TCP/IP network

. Title changed

. In 'Purpose' section information on NEMU has been replaced withOMS.

. In Figures information on NEMU has been replaced withcorresponding information on OMS.

. Text between figures have been updated with information on OMS.

. In Step 2-3. NEMU has been replaced with OMS.

. "Nokia IP Backbone information" has been replace by “Ethernet,ATM and SDH”:

DN02143138Issue 11-2 en17/09/2007


Summary of changes

. Information and figure of redundant ESA24 configuration have beenadded.

. In step 3, the first chapter has been modified and information aboutIPSec added.

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

. In 'Purpose' section information on NEMU has been replaced withOMS.

. In 'Before you start' section NEMU has been replaced with OMS.

. In Figure information on NEMU has been replaced withcorresponding information on OMS.

. In NOTE under Figure NEMU has been replaced with OMS.

. In Step 5. NEMU has been replaced with OMS. Also replaced in link.

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

. In 'Purpose' section information on NEMU has been replaced withcorresponding information on OMS.

. In Step 2-3. NEMU has been replaced with OMS.

. In Example 1. NEMU has been replaced with OMS. NEMUcommands have been replaced with OMS commands.

Configuring IP stack in OMU

. Original step 4 about "Modify interface priority" was deleted.

. A note about redundant ESA24 configuration has been added.

Creating OSPF configuration for O&M connection to NetAct

. In Figure information on NEMU has been replaced withcorresponding information on OMS.

. A note about redundant ESA24 configuration has been added.

Configuring OMS for DCN

new section

Checking the calendar time in OMS

new section


17/09/2007


Configuring DHCP server in OMS

new section

Configuring DNS client and server in OMS

new section

Configuring OMS to RNC

new section

Configuring NTP services in OMS

new section

Configuring IP address for OMS

new section

Finalising SQL server configuration

removed from document

Connecting to the O&M backbone via Ethernet

. In 'Purpose' section information on NEMU has been replaced withcorresponding information on OMS.

. In 'Before you start' section NEMU has been replaced with OMS.

Changes between issues 9 and 11-0

The configuration of the whole document is rearranged.

IP configuration for Iu-PS interface

. Contents of summary and notes are modified.

. Figure "Dedicate VCC for real time IP traffic" is added.

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

Content of purpose is modified.


DN02143138Issue 11-2 en17/09/2007


Summary of changes

Syntax of "Q6" and "QRN" commands are modified.

Creating OSPF configuration for O&M connection to NetAct

Example of "OSPF configuration for RNC", step 1 and step 5 are modified.

Configuring static routes for O&M connection to NetAct

. Content of purpose is modified.

. Syntax of "QKC" command is modified.

Connecting to O&M backbone via ATM interfaces

. Title is changed from "Configuring IP over ATM interfaces".

. Note "The destination of IP address ..." is added and steps arearranged.

. Sytax of "Q6N" command is modified.

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

Syntax "QKC" command is modified.


The whole chapter is rewritten.

Configuring Signalling Transport over IP for Control Plane

Syntax of "QKC" command is modified.

Configuring IP for Iu-BC (RNC-CBC)

Syntax "QKC" command is modified and "Q7C" command is added.

Creating and modifying IP interfaces

Syntax of "Q6N" command is modified.

Creating and modifying IP over ATM interfaces

Example of "configuring two IPoA connections to one IP over ATMinterfaces" is added.

Modifying OSPF configuration


17/09/2007


Syntax of "QKH" command is modified.

Creating and modifying static routes

. Steps 5, 6 and 7 are modified.

. Example of "Configuring redundant static routes in OMU" is added.

Creating and modifying IP QoS configuration

This is a new chapter containing instructions of creating and modifyingIPQoS configuration.

IP configuration files

Content about "DiffServ codepoint configuration data" is deleted from tableof "configuration files in the IP protocol environment" and the relevantcontents in this chapter are also deleted.

Modifying IP configuration files

Steps are rearranged and modified.

DN02143138Issue 11-2 en17/09/2007


Summary of changes


17/09/2007


1 Overview of IP connection configuration

1.1 IP connection configuration for RNC O&M

Purpose

It is important to plan the network carefully before starting theconfiguration. The network administrator has to plan and maintain acoherent view of the network and its components in order to make itcontinuously work smoothly and reliably. Issues to be considered are thenetwork structure, hardware needed, and security issues.

In RNC, IP connections are used for O&M traffic towards backbone orbase station (BTS) and for user plane and control plane traffic towards theServing GPRS Support Node (SGSN), the Cell Broadcast Center (CBC),and the Standalone SMLC (SAS).

IPv6 is not in use for O&M connections.

The following figure shows an example of IP configuration for O&Mnetwork of RNC.

DN02143138Issue 11-2 en17/09/2007


Overview of IP connection configuration

Figure 1. Example of IP configuration for RNC O&M network

For more information on data communication networks (DCN), see Datacommunication network for operation and maintenance in the NokiaWCDMA RAN System Information Set.

10.1.1.5/28

10.1.1.2/28 (logical)

RNC

10.1.1.10/28

ComputerwithElement Manager

(10.1.1.4/28)

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.3/28)

10.1.1.2/32

RAN BTS sitesaddress range10.1.2.0

RNC LAN10.1.1.0/28

OMU

10.3.2.1/24

AA255 10.3.2.2/32

ESA12/ESA2410.1.1.9/28 OMS


17/09/2007


Steps

1. Plan DHCP addresses

Assign a range of IP addresses to DHCP. The client computers onthe local area network (LAN) request the IP address from the DHCPserver.

2. Draw a map of your network

The easiest way to plan your network and determine the naming is todraw a map of the network. The map should contain at least thefollowing:. Existing networks, network elements, routers, and remote

hosts which are going to be connected.. Those units of the network element which have the IP stack.. The IP addresses, subnetwork structure, host names, and the

domain name.. The names for the servers.

3. Plan IP routing and OSPF areas

There are no specified guidelines for the number of routers in anarea or the number of the neighbours per segment or what is thebest way to plan a network. The following list gives you somesubjects which you should consider when planning the network:. the number of routers per area. the number of neighbours. the number of areas per Area Border Routers. the number of sub areas

1.2 OMS TCP/IP network

Purpose

OMS has to be physically connected to the managed network element andexternal networks. The connections are done through ESA12 or ESA24Ethernet switch. The compact OMS has redundant Ethernet interfaces,which have to be connected to the ESA12/ESA24 switch. The Ethernetinterfaces of the RNC are also connected to the same ESA12/ESA24switch.

DN02143138Issue 11-2 en17/09/2007



The local network also has to be connected to the DCN network thatenables the connections towards Nokia NetAct and other externalsystems.

In RNC there are two main DCN connectivity alternatives for theconnection between OMS and NetAct, IP over ATM connectivity andEthernet connectivity.

If IP over ATM connectivity is used, OMS uses OMU unit as its default IProuter. OMU unit routes the IP traffic between OMS and NetAct using ATMvirtual circuits and IP over ATM. The connection between OMS and OMUis always Ethernet.

The following figure describes the IP over ATM based connectivityalternative on general level.

Figure 2. IP over ATM based connectivity between OMS and NetAct

If Ethernet connectivity is used, OMS uses an external IP router as itsdefault router. The IP router routes the IP traffic between OMS and NetActover the LAN/WAN IP network. The connection between OMS and theexternal IP router is always Ethernet and the LAN/WAN network can beany type of IP network, for instance Ethernet, ATM or SDH network.

The following figure describes the Ethernet based connectivity alternativeon general level.

It is possible to add high level of redundancy to the RNC’s Ethernetnetwork by installing an optional redundant ESA24 switch. It should benoted that it is allowed to add the redundant ESA24, if the existing switch isESA24. If ESA12 switch exists, it must be replaced by ESA24. Whenredundant ESA24 exists, OMS and OMU will be physically connected toboth ESA24 switches, as shown in figure 7.

RNC

NetAct ATM SW

OMS

OMU

ESA12/ESA24


17/09/2007


Figure 3. Ethernet based connectivity between OMS and NetAct

Figure 4. Ethernet based connectivity between OMS and NetAct, withredundant ESA24

Steps

1. Plan physical network connection

2. Create an addressing scheme for OMS

The OMS needs one IP address. The address should be from thesame subnetwork as the other addresses in the same physicalnetwork.

a. Make a drawing of the RNC subnetwork. Include all the units,routers and switches that need data communicationsconnections.

b. Define the address space for the subnetwork.

c. Select addresses for the IP interfaces of the devices in thenetwork.

3. Plan the network security for OMS

RNCOMS

OMU

ESA12/ESA24 IP Router NetActLAN/WAN

RNC

IP Router NetActLAN/WAN

OMS

OMU

ESA24

ESA24

DN02143138Issue 11-2 en17/09/2007



Security aspects should be taken into consideration when planningthe TCP/IP network for OMS. In other words, the transport networkbetween the RNC and the NetAct should be a part of a trustedprivate intranet. If some external insecure networks are used astransport networks, you should be aware of the TCP/IP securityissues.

It is possible to add strong network-level security to communicationbetween RNC and NetAct by using optional IP Security (IPSec)feature. IPSec can be used in both OMS and OMU unit to encryptand integrity-protect all or only selected traffic between RNC andNetAct. For more information about IPSec, refer to documentRAN33: IP Security for O&M Traffic Between RNC and NetAct,Feature Activation Manual.

There are username/password mechanisms for application levelconnections to OMS.

1.3 IP configuration for Iu-PS interface

Purpose

The Iu-PS interface connects the RNC and the Serving GPRS SupportNode (SGSN). The IP connection is used for user plane and control planetraffic.

Before you start

For more information on the Iu-PS interface, see Iu interface specificationin the Nokia WCDMA RAN System Information Set in NOLS.

Summary

In Iu-PS interface, the traffic goes through NIS1 and GTPU units. In GTPUunits, all users and packets are treated equally regardless of the service,Quality of Service (QoS) requirement, and packet size. However, you candedicate two or more GTPUs to serve only real-time IP traffic between theRNC and the SGSN. Dedication is done by configuring IP over ATM VCCsso that their usage is IP over ATM real-time user data (IPOART). With aGTPU dedicated to real-time IP traffic, there is a separate real-timeoptimised Iu-PS PVC (CBR or rt-VBR) for Packet Switched Radio AccessBearers (RABs) between the GTPU and the SGSN and a separate internalreal-time optimised VCC between the GTPU and the DMCU. Anothersolution is to use layer-two segregation functionality of GTPU. By thissolution, you can use two VCCs under one IPoA interface of GTPU. One ofthese two VCCs is dedicated to real-time IP traffic.


17/09/2007


It is also possible to configure QoS DiffServ traffic classification to GTPUunits. You can prioritise the throughput real time (rt) traffic rather than non-real time (nrt) traffic in the GTPU TCP/IP stack. Such configuration is donewith MML command Q8. For more detailed instructions, refer to Creatingand modifying IP QoS configuration.

Note

If you want to dedicate a GTPU for real-time IP traffic, configure theusage of all IP over ATM interfaces of the unit as IPOART.

If you want to use layer-two segregation functionality, configure twoVCCs to one IPoA interface, configure the usage of one VCC asIPOART and the other VCC's usage as IPOAUD.

The following figures show the difference between non-dedicated anddedicated GTPUs.

Figure 5. All GTPUs used for real-time and non-real time traffic

Non-dedicated VCCs

GTPU

GTPU

GTPU

GTPU

GTPU

MXU SGSNSFU

DN02143138Issue 11-2 en17/09/2007



Figure 6. Certain GTPUs dedicated for real-time IP traffic

Figure 7. Dedicate VCC for real-time IP traffic (Layer-two segregation solution)

NRT-VCCs

MXU SGSNSFU

RT-VCCs

GTPU

GTPU

GTPU

GTPU

GTPU

SFU MXU

GTPU

SGSN

NRT_VCC

RT_VCC

GTPU

GTPU

GTPU

GTPU


17/09/2007


Note

If you decide to dedicate some GTPUs for real-time traffic, configure atleast two units for real-time traffic and two units for non-real time traffic.This way traffic does not stop if one unit fails.

For more detailed instructions on how to dedicate GTPUs for real-timetraffic, see the Feature Activation Manual for Dedicated GTPU for RT PSSupport.

Steps

1. Draw a map of your network

The easiest way to plan your network and determine the naming is todraw a map of the network. The map should contain at least thefollowing:. Existing networks, network elements, routers, and remote

hosts which are going to be connected.. Those units of the network element which have the IP stack.. The IP addresses, subnetwork structure, host names, and the

domain name.. The names for the servers.

2. Plan routing

You can use either static routes or OSPF for routing. If you use onlystatic routes, see the examples in Configuring IP for Iu-PS UserPlane (RNC— SGSN) for instructions on how to create redundancyfor the Iu-PS interface.

1.4 IP configuration for Iu-BC interface

The Iu-BC interface is the logical interface between a radio networkcontroller (RNC) in the radio access network (RAN) and a cell broadcastcentre (CBC) in the core network.

The Iu-BC is one instance of an Iu interface and is used for cell broadcastservices.For more information on the Iu-BC interface, see Iu interfacespecification in the Nokia WCDMA RAN System Information Set.

DN02143138Issue 11-2 en17/09/2007



All user data and signalling (SABP) traffic goes through the same ICSUunits. You need to select only one working ICSU unit (WO-EX) as activeone and configure IP address, IPoA VCC and static route on it. For moreinformation, see Configuring IP for Iu-BC (RNC-CBC).


17/09/2007


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 Operation andMaintenance Server (OMS), ESA12/ESA24 Ethernet switch and theOperation and Maintenance Unit (OMU) for the data communicationnetwork (DCN). After this, you can use the Element Manager to managethe RNC remotely.

The O&M backbone can be configured either via Ethernet or via ATMvirtual connections, or via both.

Note

You can improve the redundancy of the RNC Ethernet network byinstalling a redundant ESA24 Ethernet switch and redundant Ethernetcabling.

Before you start

Check that:

. you have the IP address plan and IP parameters for OMU, OMS,and ESA12/ESA24.

. your computer has the following:. DHCP client. Connection to the Element Manager and remote management

application for OMS

DN02143138Issue 11-2 en17/09/2007



. Ethernet interface connected to a port of ESA12/ESA24

. Network settings to match the preconfigured settings

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

Figure 8. Preconfigured settings for O&M network

Note

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

Steps

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

See Creating MMI user profiles and user IDs for remote connectionsto NetAct for detailed instructions.

2. Configure IP stack in OMU

192.168.1.5/28

192.168.1.1/28 (logical)

RNC

OMU

192.168.1.10/28


RNC LAN192.168.1.0/28

OMSESA12/ESA24192.168.1.9/28


17/09/2007


See instructions in Configuring IP stack in OMU.

3. Configure IP routing

There are two ways to configure routing information:. by creating OSPF configuration

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

. by configuring static routes

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

4. Configure the Ethernet/LAN switch

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

5. Configure OMS

Configure OMS according to instructions in Configuring OMS forDCN.

6. Configure external IP connections

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

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

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

Refer to instructions in Connecting to the O&M backbone viaATM interfaces.

The recommended way of connecting RNC to NetAct is via Ethernet.The connection via ATM should only be used as a backup. O&Mconnections can be configured to use both ways.

DN02143138Issue 11-2 en17/09/2007



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 tocreate users NUPADM and NEMUAD and their profiles in the RNC. NetActapplication (service user management) accesses RNC with NUPADMprofile. NUPADM profile is mandatory to create other service users inNetAct application. NEMUAD profile is created to enable communicationbetween OMS and OMU. For example, without NEMUAD profile, PM datacannot be transferred to OMS and therefore affects the transfermeasurement to NetAct.

See the example below for detailed instructions.

Before you start

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

Steps

1. Establish a telnet connection to RNC OMU

Enter the preconfigured IP address to OMU (the default IP addressis 192.168.1.1):

telnet <IP address of OMU>

2. Create new MMI user profiles

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

3. Create new MMI user IDs

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

Example Creating MMI user profiles and user IDs in the RNC

This example shows how to create the NUPADM and NEMUAD MMIprofiles and user IDs in the RNC.


17/09/2007


1. Create the user profiles.

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

ZIAA:NEMUAD:ALL=250:VTIME=FOREVER,UNIQUE=YES::FTP=W;

2. Create the user IDs.

ZIAH:NUPADM:NUPADM;

ZIAH:NEMUAD:NEMUAD;

When creating a new user ID, the system prompts you for apassword. The password created here is used for communicationbetween the OMS or the NetAct and the RNC. The system displaysthe following output:

/* IDENTIFY PASSWORD:

MINIMUM PASSWORD LENGTH IS 6

MAXIMUM PASSWORD LENGTH IS 16 */

NEW PASSWORD:********

VERIFICATION:********

COMMAND EXECUTED

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

2.3 Configuring IP stack in OMU

Purpose

The purpose of this procedure is to configure OMU for data communicationnetwork (DCN).

Before you start

A telnet connection to RNC OMU must be open.

For IPv4:

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

For IPv6:

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

DN02143138Issue 11-2 en17/09/2007



Steps

1. Configure DNS parameter data

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

For IPv4:

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

For IPv6:

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

2. Modify TCP/IP parameters

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

For IPv4:

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

For IPv6:

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

3. Add a new logical IP address

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


17/09/2007


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

ZQ6N:OMU:<interface name>,[<point to point interfacetype>]:[<IP address>],[<address type>]:[<prefixlength>]:[<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&Mconnection to NetAct.

. by configuring static routes

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

5. Remove the preconfigured IP address

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

ZQRG:OMU,<unit index>:<interface name...>,:<IPaddress>;

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

Note

Interface name can be a specific one or a range, for example: AA0 toAA10.

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

Example Configuring IPv4 stack in OMU

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

DN02143138Issue 11-2 en17/09/2007



1. Configure DNS parameter data. The IPV4 address of the primaryDNS server is 10.1.1.5 and the local domain name RNC1.NETACT.OPERATOR.COM.

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

2. Modify IPv4 parameters for both OMU units separately. Set the hostname to OMU, set IP forwarding on, and specify that subnets are notlocal.

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

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

3. Add a new logical IPv4 address (10.1.1.2) to the OMU units. Theinterface name is EL0 and the netmask is length 28.

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

If the optional redundant ESA24 switch has been installed, thefollowing example command is used instead. In that case, the logicalIP address (10.1.1.2) is added to both EL0 and EL1 interfaces at thesame time.

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

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

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

ZQRG:OMU,0:EL0:192.168.1.1;

Example Configuring IPv6 stack in OMU

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

1. Configure DNS parameter data. The IPv6 address of the primaryDNS server is 3FEE::1 and the local domain name RNC1.NETACT.OPERATOR.COM.

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

2. Modify IPv6 parameters for both OMU units separately. Set the hostname to OMU, set IP forwarding on, set hoplimit value as 70, and setrouter advertisement OFF.

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



17/09/2007


3. Add a new logical IPv6 address (3FFE:1200:3012:C020:380:6FFF:FE5A:5BB7) to the OMU units. The interface name is EL0 and thenetmask is length 20.

ZQ6N:OMU,0:EL0:"3FFE:1200:3012:C020:380:6FFF:FE5A:5BB7",L:20;

4. Remove the preconfigured IPv6 address (3FEE::1) from both OMUunits.

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

2.4 Creating OSPF configuration for O&M connectionto NetAct

Purpose

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

Before you start

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

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

Steps

1. Configure OSPF router parameters (QKS)

If the OMU units have physical IP addresses in addition to a logicalIP address, the OMU units must have a different router ID. Give thephysical address of the OMU unit as the value for the router IDparameter, to avoid having two routers with the same router ID, inthe network.

ZQKS:<unit type>,<unit index>:[MOD|DEL],<routerid>:<rfc1583compatibility>:<spf delay>:<spf holdtime>;

DN02143138Issue 11-2 en17/09/2007



2. Configure OSPF area parameters (QKE)

Define the OSPF area (both backbone and other area) parametersof an OSPF router.

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

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

Note

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

3. Interrogate IP interfaces (QRI)

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

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

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

4. Configure OSPF interfaces (QKF)

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

5. Configure redistribute parameters (QKU)

Usually static routes to BTSs are redistributed to OSPF byredistribution configuration.


17/09/2007


ZQKU:<unit type>,<unit index>:<redistribute type andidentification>:<metric>;

6. Configure network prefix, if required (QKH)

This command defines a network prefix in the OSPF area.Configuring the network prefix is optional to reduce the routinginformation exchange between different areas.

ZQKH:<unit type>,<unit index>:<areaidentification>:<operation>:<network prefix>,<network prefix mask length>:<network prefixrestriction>;

7. Configure virtual link parameters, if required (QKV)

If there is an OSPF area which does not have a physical connectionto the backbone area, use a virtual link to provide a logical path fromthe disconnected area to the backbone area. Virtual links have to beconfigured to both ends of the link. The QKV command has to beentered separately for both border routers using the virtual link.

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

Example Creating OSPF configuration for O&M DCN

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

DN02143138Issue 11-2 en17/09/2007



Figure 9. Example of OSPF configuration for RNC

This example presents the configuration of OSPF parameters in the OMUunit. The OMU unit in RNC is a border router. The unit has three interfaces:EL0, AA0, and AA255. The EL0 interface is attached to the backbone areathrough an Ethernet connection. The AA0 and AA255 interfaces areattached to the backbone area through an IP over ATM connection.

10.1.1.5/28

10.1.1.2/28 (logical)

RNC

10.1.1.10/28


(10.1.1.4/28)

10.1.1.2/32

unnumbered lines


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.3/28)

10.1.1.2/32

RAN BTS sitesaddress range10.1.2.0

RNC LAN10.1.1.0/28

OMU

10.3.2.1/24

AA255 10.3.2.2/32

ESA12/ESA2410.1.1.9/28 OMS


17/09/2007


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

ZQKB:OMU;

The following output is displayed:

RNC IPA2800 2006-10-11 17:17:09

INTERROGATED STATIC ROUTES

ROUTE

UNIT DESTINATION GATEWAY ADDRESS TYPE PREFERENCE NBR

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

OMU-0 DEFAULT ROUTE 172.28.107.1 LOG 0 1

COMMAND EXECUTED

2. Remove the default route from both units.

ZQKA:1;

or

ZQKA::OMU,0;

3. Configure OSPF router parameters.

Configure the OSPF parameter data for the OMU with the router ID10.1.1.2 and accept the default values for the remaining parameters.

ZQKS:OMU,0:,10.1.1.2;

ZQKS:OMU,1:,10.1.1.2;

4. Configure OSPF area parameters.

Configure the backbone area information for the OMU.

ZQKE:OMU,0:0.0.0.0;

ZQKE:OMU,1:0.0.0.0;

5. Inquire the attached interfaces.

ZQRI:OMU;

The following output is displayed:

IF ADM IF ADDR

UNIT NAME STATE MTU PRIORITY TYPE TYPE IP ADDRESS

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

OMU-0 AA0 UP 1500 L 10.3.1.2/32

->10.3.1.1

AA255 UP 1500 L 10.3.2.2/32

->10.3.2.1

EL0 UP 1500 L 10.1.1.2/28

DN02143138Issue 11-2 en17/09/2007



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

->10.3.1.1

AA255 UP 1500 L (10.3.2.2)/32

->10.3.2.1

EL0 UP 1500 L (10.1.1.2)/28

6. Configure OSPF interfaces.

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

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

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

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

The AA0 and AA255 interfaces are attached to the backbone areathrough an IPoA connection. Set the hello interval to 30, routerdead interval to 120, and ospf cost to 100.

ZQKF:OMU,0:AA0:0.0.0.0:30:120:100;

ZQKF:OMU,1:AA0:0.0.0.0:30:120:100;

ZQKF:OMU,0:AA255:0.0.0.0:30:120:100;

ZQKF:OMU,1:AA255:0.0.0.0:30:120:100;

If an optional redundant ESA24 switch has been installed and theQRI command printout in step 5 shows that OMU’s EL1 interfacesare configured with the same IP addresses as the EL0 interfaces,then the EL1 interfaces are also configured as OSPF interfaces withthe following commands:

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

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

7. Configure redistribute parameters.

Configure the OSPF to redistribute all valid static routes.

ZQKU:OMU,0:ST=;

ZQKU:OMU,1:ST=;


17/09/2007


2.5 Configuring static routes for the O&M connectionto NetAct

Purpose

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

Static routing is extremely suitable when there is only one connection(Ethernet or IP over ATM) towards NetAct. When there are two or moreconnections towards NetAct, OSPF is the recommended solution.Redundant static routing is also the alternative. With redundant staticrouting, multiple static routes via different gateways in differentpreferences can be configured for a same destination. If the primary routegoes down, the backup route will take the duty. For more details aboutOSPF solution, see Creating OSPF configuration for O&M connection toNetAct and refer Creating and modifying static routes for more detailsabout redundant static routing.

Before you start

Note

Usually a default route on OMU is enough to connect to NetAct.

A logical route must use a logical address to reach its gateway, and itfollows the logical address if a switchover occurs.

Steps

1. Configure the default static route

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

Note

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

DN02143138Issue 11-2 en17/09/2007



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

Note

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

2. If the default route cannot be used

Then

Delete the default static route for IP configuration

a. Obtain the number of the static route to be deleted.

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

b. Delete the route by identifying it by its route number or by itsidentification.

ZQKA:<route number>;

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

3. If the default route cannot be used and you deleted it, or if you needto create more routes

Then

Create new static routes (QKC)

You create new static routes by using the QKC command.

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

Example Creating a default static route in RNC OMU

The same default route is used for both OMU-0 and OMU-1.

ZQKC:OMU,0::10.1.1.1,:LOG;


17/09/2007


2.6 Configuring ESA12

Purpose

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

Steps

1. Establish a telnet connection to ESA12

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

telnet <ip address of ESA12>

b. Enter your login ID and password.

The default password is empty. Therefore, press Enter tocontinue. If you have already changed your password duringcommissioning, enter your new password.

NOKIA ESA-12.

Username:nokia

Password:********

Expected outcome

The following options are displayed:

ESA12

Main Menu

1. General Configuration

2. SNMP Configuration

3. Ports Configuration

4. Ports Status

5. Load Factory Defaults

6. Software Upgrade

7. Reset

8. Logout

2. Press 1 to select General Configuration from the menu

The General Configuration menu shows the current settings.

Expected outcome

The General Configuration menu is printed on the command line.

General Configuration

MAC address 00 A0 12 0B 02 74

1. Agent IP Address : 192.168.001.009

DN02143138Issue 11-2 en17/09/2007



2. Agent Netmask : 255.255.255.240

3. Default Gateway : 192.168.001.001

4. Supervisor/Terminal Password :

5. System Name :

6. Advanced Features

9. Main Menu

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

Expected outcome

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

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

5. Enter the new value for the parameter and press Enter

Expected outcome

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

Expected outcome

The session is interrupted immediately after you change the IP address.Change the IP address only after having changed all other parameters.

Example Changing the default gateway in ESA12

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

1. Establish a telnet connection to ESA12. In this example, thepassword has not been changed yet.

telnet 192.168.1.9

Username:nokia

Password:

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

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

Default Gateway : 192.168.1.1


17/09/2007


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

5. Enter the new value for the parameter and press Enter:

Default Gateway : 10.1.1.2

The new value is shown in the General Configuration menu:

General Configuration

MAC address 00 A0 12 0B 02 74

1. Agent IP Address : 192.168.001.009

2. Agent Netmask : 255.255.255.240

3. Default Gateway : 10.001.001.002

4. Supervisor/Terminal Password :

5. System Name :

6. Advanced Features

9. Main Menu

2.7 Configuring ESA24

Purpose

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

Before you start

Before you start the configuration, check the following:

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

. The ESA24 Ethernet switch is powered up (the LED on the frontpanel of the switch is green).

Steps

1. Connect to the IP address of ESA24 via Telnet

DN02143138Issue 11-2 en17/09/2007



Note

If connection to the IP address of ESA24 is via Telnet, the IP addresswill change to the given address by the command IP address X.X.X.

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

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

b. Connect to the IP address of ESA24:

telnet <IP address of ESA24>

c. Press Enter.

Expected outcome

The system prompts for a password:

User Access Verification

Password:

2. Log in to ESA24

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

Expected outcome

After successful login, the ESA24 prompt is displayed:

ESA24>

3. Enable RSTP or MSTP for ESA24, if necessary

If you want to prevent cabling loops, enable the Rapid SpanningTree Protocol (RSTP) or the Multiple Spanning Tree Protocol(MSTP) for ESA24.

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

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

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


17/09/2007


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

4. Change to a privileged mode in BiNOS

Enable the privileged mode in ESA24 operating system with thecommand

ESA24> enable

The privileged mode allows advanced viewing and configuration forthe unit.

Note

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

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

5. Change to configuration mode in BiNOS

Enable the configuration mode in ESA24 operating system with thecommand

ESA24#configure terminal

6. Set the IP address and netmask for ESA24

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

7. Set the default gateway for ESA24

Delete the existing default route before add new route.

ESA24(config)#no ip route 0.0.0.0/0

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

8. Enable DHCP, if necessary

DN02143138Issue 11-2 en17/09/2007



ESA24(config)#ip address dhcp

9. Save the configuration

ESA24#write

Further information

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

Example Configuring ESA24

This example shows how to configure ESA24.

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

a. Select Start -> Run on the Windows Taskbar.

b. Connect to the IP address of ESA24:

telnet 192.168.1.9

c. Press Enter.

The following prompt is displayed:

User Access Verification

Password:

2. Enter nokia and press Enter to log in to ESA24.

After successful log in, the ESA24 prompt is displayed:

ESA24>

3. Change to privileged mode.

ESA24> enable

4. Change to configuration mode.

ESA24#configure terminal

5. Set the IP address and netmask for ESA24.

ESA24(config)#ip address 192.168.0.5/28

6. Set the default gateway for ESA24.

ESA24(config)#ip route 0.0.0.0/0 192.168.0.1

7. Save the configuration.


17/09/2007


ESA24#write

2.8 Configuring OMS for DCN

2.8.1 Configuring OMS for DCN

Purpose

To get OMS fully integrated to the DCN, the default settings of OMS areconfigured so that they match the current network environment.

Steps

1. Open the remote management application for OMS

Use SSH for remote management.

Note

You can download the SSH client from the EM Homepage. Go to theEM Homepage with your Internet browser by entering the followingaddress: https://192.168.1.5. Use Nemuadmin / nemuuser usenameand password for logging into the EM homepage.

Download PuTTY from the link and save it to your computer (forexample to C:/temp). Then open putty.exe from your computer andgive an OMS IP address for the hostname (the default is192.168.1.5), and click Open.

Log in with the username Nemuadmin / nemuuser

Change permissions to root user by giving the following command:

su -

Then provide the root user password (the default one isanonymous). The root user is the only username who has thenecessary rights to execute the following configuring steps.

2. Change the time zone settings

DN02143138Issue 11-2 en17/09/2007



For changing the time zone settings, refer to the instructions inChanging time zone settings in OMS.

3. Check the calendar time

For checking the correct calendar time, refer to the instructions inChecking the calendar time in OMS.

4. Password for the root user

If you want to change the password for the root user, give thefollowing command:

passwd

For enabling the new password to LDAP, the following command hasto executed:

fsdistribute /etc/shadow

5. Configure the FTP user

If you want to change the default FTP user password, execute thefollowing command:

/opt/Nokia/SS_OMSINST/script/modifyOMSSettings.sh

You will see the following printout:

OMS FTP server IP address is 192.168.1.5

which is the user's own IP address

Type omsFtpUser password [press ENTER to use default]:

Here you have to add the new password for the FTP user.

You have to set the following settings: FTP Password = ******

OMS FTP IP = 192.168.1.5

FTP Username = omsFtpUser

FTP Password = ******

Are these parameters correct (yes/no)?


17/09/2007


Check whether these parameters are correct, and then answer 'yes'.

6. Configure the NWI3 user

a. If you only want to change the default NWI3 user password,execute the following command:

passwd Nemuadmin

b. If you want to create a new NWI3 user, execute the followingcommand:

fsuseradd -g 557 <your_nwi3_username> -G pmgRootforexample:

fsuseradd -g 557 nwi3user -G pmgRoot

where 557 is the group number where the user will be added.

c. Set a password for the new user:

passwd <your_nwi3_username>

d. If you want to take the new account into use immediately,update the new user to the registry with the followingcommand:

fshascli –r /NWI3Adapter

7. Add/remove MMI mapping to/from users

If you want to give MMI mapping, use the zmmimapping command.MMI mapping is used by the MMI Window application to log OMSusers into the OMU. All users who have MMI mapping are printed.

a. Print existing mapping.

Example

zmmimapping -p

b. If OMS user already has mapping, delete mapping.

Example

zmmimapping -d Nemuadmin

c. Add new mapping.

Example

zmmimapping -a Nemuadmin NEMUAD

For more information about MMI, see Using Element Manager inRNC OMS.

8. Configure OMS to RNC

DN02143138Issue 11-2 en17/09/2007



For configuring OMS to RNC, refer to the instructions in ConfiguringOMS to RNC.

9. Configure the OMS system identifier

For configuring the OMS system ID, refer to the instructions inConfiguring the OMS system identifier.

10. Define the IP address for OMS

For defining the network settings for OMS, refer to the instructions inConfiguring IP address for OMS.

11. Configure the DHCP server

For configuring the DHCP server, refer to the instructions inConfiguring the DHCP server in OMS.

Further information

The following table lists the OMS LDAP variables used when configuringOMS for RNC connection.

Table 1. RNC data in OMS registry

Variable Data

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

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

OMS's IP address As configured in Configuring IP addressesfor OMS.

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

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

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

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


17/09/2007


Table 1. RNC data in OMS registry (cont.)

Variable Data

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

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

Note

All usernames and passwords are only examples.

Table 2. RNC data in OMS registry

Variable Data

OMS FTP UserName The name of the service user with OMSFTP Access, this is omsFtpUser.

OMS FTP Password The password for the OMS FTP user asdefined in Configuring OMS for DCN.

OMS Registration Account Username The NetAct NWI3 Access accountusername.

OMS Registration Account Password The NetAct NWI3 Access accountpassword.

Network Management’s Registration IOR(RSIOR)

The Network Management's RegistrationIOR (RSIOR) in NetAct

2.8.2 Checking the calendar time in OMS

Purpose

You have to make sure that the calendar time in OMS is set correctly.

DN02143138Issue 11-2 en17/09/2007



Note

Change of date and time might terminate the SSH connection becauseof connection timeout. In this case, reopen the SSH connection to theOMS and gain root access with su- command.

Steps

1. Check date and time settings

Enter the following command:

date

Check that the printout matches your local date and time.

2. Modify time settings

If the time settings are not correct, modify them with the followingcommand:

date

Give the new time in the following format: MMDDhhmm[[CC]YY] (forexample, date 05220822 or date 052208222007).

2.8.3 Configuring the DHCP server in OMS

Before you start

Before activating the DHCP service on OMS, you have to configure it.Proper DHCP operation requires a valid IP address pool, where DHCPcan give an IP address when requested. Also, the DHCP address must bein the same network as OMS. For example, if the OMS network interfacesare in the 10.8.122.0 network, trying to give an IP address of 10.8.118.0network will fail, since the network interface giving the IP address andgiven address are in different networks.

You must have a root access to modify the DHCP settings and/or changeits status.

Steps

1. Modifying DHCP address pool


17/09/2007


a. Open /opt/Nokia/SS_OMSINST/dhcpd/dhcpd.conf in a texteditor. The file contains an example configuration, which youhave to modify to match the current network and wantedaddress pool.

b. Change the subnet and netmask to the correct settings.Consult OMS networks settings for the correct subnet andnetmask.

In the range line, type the first and last IP address of the IPrange that is defined to the DHCP IP pool.

For example:

range 10.1.1.10 10.1.1.12

gives a pool of three IP addresses starting with 10.1.1.10.

c. Exit the editor with saving the settings.

2. Using DHCP

Start DHCP by executing the following command:

chmod 544 /opt/Nokia/SS_OMSINST/dhcpd/zstart_dhcpd.sh

/opt/Nokia/SS_OMSINST/dhcpd/zstart_dhcpd.sh

The DHCPD is now started. Booting OMS will deactivate theDHCPD.

To deactivate DHCP, execute the following command:

/opt/Nokia/SS_OMSINST/dhcpd/zstop_dhcpd.sh

To gain more information, use man DHCP.

2.8.4 Configuring the DNS client in OMS

Before you start

The DNS client configuration is distributed into the FlexiPlatform, and it ispresent after system restart. Restarting the ClusterDNS service activatesthe new configuration.

Steps

1. Open the /etc/clusterdns.conf file with an editor.

Open the configuration file with an editor you are familiar with, forexample nano as shown in the example below:

DN02143138Issue 11-2 en17/09/2007



nano /etc/clusterdns.conf

2. Find forwarders { 192.168.1.1; }; line and replace the defaultaddress with the correct DNS IP

3. Save and close the clusterdns.conf file.

4. Distribute the configured file into the FlexiPlatform.

Run the following command for distributing the configured file intothe FlexiPlatform:

fsdistribute /etc/clusterdns.conf

5. Restart the ClusterDNS service.

Run the following command for restarting the ClusterDNS service.After this command, the new configuration is in use. Enter:fshascli -r /ClusterDNS

Note

NEMU used to act as a secondary DNS service to the network. In OMS,NEMU DNS is no longer available, as it was removed to improvesecurity and cleanup architecture.

2.8.5 Configuring OMS to RNC

Purpose

The External Message Transfer (EMT) connection between OMS andOMU requires the following:

. the LDAP registry includes the IP address of OMU and the user IDand password of the network element

. the user ID and password have been defined in the network elementfor the EMT connection

. the IP address of the OMS and the FTP username and passwordalso have to be defined for measurement bulk data transfer

. the network element must have a user ID that the EMT, Telnet andFTP connections can use.


17/09/2007


Before you start

The following user accounts have to be created to OMS:

. OMS FTP user (the default is omsFtpUser)

. NWI3 user (the default is Nemuadmin)

Note

The NWI3 user must be the same as defined in the NetAct maintenanceregion to which the OMS belongs.

Steps

1. Start the zmodifyOMUSettings script

Start the zmodifyOMUSettings script by entering the followingcommand:

zmodifyOMUSettings

2. See further instructions in zmodifyOMUSettings

You can change the OMU IP by using the zmodifyOMUSettings tool.The zmodifyOMUSettings tool writes the entered information to theLDAP register.

Note

If the OMU FTP, OMU Telnet, or EMT passwords or usernames arechanged on the managed element side, the same changes must alsobe done on the OMS side.

Start zmodifyOMUsettingsCurrent OMU IP can be checked by enteringthe command zomuip and press enter.

Start zmodifyOMUSettings by entering thecommand zmodifyOMUSettings in a SSHclient window.

DN02143138Issue 11-2 en17/09/2007



When zmodifyOMUSettings is started, it asksfor new values. For the new values, see theentries below:

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

OMU EMT UserNameEnter OMU EMT UserName. Press ENTER ifthe current value is OK.. EMT UserName [STRING] current value:

SYSTEM. EMT UserName [STRING] new value:

NEMUAD

EMT Password Enter EMT Password and press ENTER.

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

Give the current password for NEMUAD.

OMU FTP UserNameEnter OMU FTP UserName. Press ENTER ifthe current value is OK.. OMU FTP UserName [STRING] current

value: SYSTEM. OMU FTP UserName [STRING] new

value: NEMUAD

OMU FTP PasswordEnter OMU FTP Password and press ENTER.

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


OMU Telnet UserNameEnter OMU Telnet UserName. Press ENTER ifthe current value is OK.

OMU Telnet UserName [STRING] currentvalue: SYSTEM

OMU Telnet UserName [STRING] new value:NEMUAD

OMU Telnet PasswordEnter OMU Telnet Password and pressENTER.

OMU Telnet Password [STRING] new value:******



17/09/2007


Changes to be updatedCheck the information which will be updated.

You have to set the following:

OMU IP = 10.1.1.2

EMT Username = NEMUAD

EMT Password = ******

FTP Username = NEMUAD

FTP Password = ******

Telnet Username = NEMUAD

Telnet Password = ******

Are these parameters correct (yes/no)?

Answer: yes

Do you want to restart NWI3Adapter and OMS SW's (postConfig CHOOSE NO)? (yes/no)

Answer: no

2.8.6 Configuring NTP services in OMS

Purpose

The NTP configuration file is distributed into the FlexiPlatform. It is presentafter system restart. Restarting ClusterNTP service activates the newconfiguration.

Before you start

You need root access to modify NTP settings and to restart NTP service.

Steps

1. Open and edit the /etc/ntp_master.conf file with a text editorfor example nano

nano /etc/ntp_master.conf

2. Modify OUR TIMESERVERS and NTP server IP address

DN02143138Issue 11-2 en17/09/2007



Replace the IP address in the restrict line to match the correctNTP server settings. For example: 10.0.0.5

restrict 10.0.0.5 mask 255.255.255.255 nomodify notrapnoquery

Replace the IP address in the server line with correct IP address:

server 10.0.0.5 iburst minpoll 4

3. Save, then close the editor

4. Distribute the configured file into the FlexiPlatform

Run the following command for distributing the configured file intothe FlexiPlatform:

fsdistribute /etc/ntp_master.conf

5. Restart the ClusterNTP service

Run the following command for restarting ClusterNTP service.

fshascli -r /ClusterNTP

After executing this command, the new configuration is in use.

6. Check that primary NTP server is configured correctly

Enter the following command:

ntpq -c pe

2.8.7 Configuring OMS system identifier

Purpose

This procedure configures the system identifier of OMS. The systemId hasto have the same value as the identifier of the network element, forexample, (systemId = NE-RNC-'rnc_id'). In this scenario, the systemconsists of a managed network element and OMS, which is logically seenas part of the network element itself. In this case, the system identifier andnetwork element identifier are the same.


17/09/2007


Note

The systemId value must be chosen between 1 - 4095.

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

Steps

1. Start the zchangecluster-id script

Entering the following command:

zchangecluster-id

2. See further instructions in zchangecluster-id below:

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

The value must be chosen between 1 - 4095,for example, NE-RNC-'1'.

Give new RNC id number <1-4095>:

NWI3Adapter restartThe new clusterid will be valid after theNWI3Adapter restart.

Do you want restart NWI3Adapter and OMS SW's? (yes/no)

Answer: no

Note

The cluster id will not change during default/current session. It is validfrom new sessions onward.

DN02143138Issue 11-2 en17/09/2007



2.8.8 Configuring IP addresses for OMS

Purpose

OMS network settings can be modified afterwards by thezmodifyNetworkSettings command. The DNS client and NTPconfiguration files are distributed into the FlexiPlatform. Newconfigurations are present after system restart.

Before you start

Gather the following information:

. OMS IP address

. Netmask, in bits. For more information, see the conversion tablebelow

. Gateway (usually it is OMU address)

. NTP IP address

. DNS IP address

Table 3. Bits/Subnet conversion table

24 255.255.255.0

25 255.255.255.128

26 255.255.255.192

27 255.255.255.224

28 255.255.255.240

29 255.255.255.248

Script will query information listed above and confirm that enteredinformation is correct. After script has run OMS will restart itself to activatenew settings.

Note

NEMU used to act as a secondary DNS service to the network. In OMS,NEMU DNS is no longer available, as it was removed to improvesecurity and cleanup architecture.


17/09/2007


Steps

1. Enter zmodifyNetworkSettings

Executing the zmodifyNetworkSettings starts query for newnetwork settings, confirm changes and then change values to theOMS and restart to take new settings to the use.

Command print capture:

# zmodifyNetworkSettings

Modifying network settings...

Enter parameters

OMS IP:

10.1.1.5

NETMASK: (in bits e.g. 24)

28

DNS IP:

10.0.0.5

NTP IP:

10.0.0.5

DEFAULT GATEWAY:

10.1.1.2

Parameters

OMS IP: 10.1.1.5

NETMASK: /28

DNS IP: 10.0.0.5

NTP IP: 10.0.0.5

DEFAULT GATEWAY: 10.1.1.2

These are used variables, continue? (yes/no)?

After answering yes, zmodifyNetworkSettings will modify valuesand ask to restart OMS.

Answer: y

/ is the cluster. The request will restart all the nodes in it.

Are you sure you want to proceed? [y/n] y

2. Modify computer network settings to match new OMS networksettings

Configuring computer network settings depends on the operatingsystem.

DN02143138Issue 11-2 en17/09/2007



2.9 Connecting to O&M backbone via Ethernet

Purpose

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

Figure 10. Ethernet connection for O&M traffic

O&M connections from the RNC to the O&M backbone can also becreated via ATM virtual connections, but Ethernet is the preferred way.

Note

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

Before you start

Because the IP addresses for OMU, ESA12/ESA24 and OMS have beenpreconfigured in the RNC, you must first change the IP addresses. Severalelements in the network can have the same preconfigured IP addresses,so if you do not change the preconfigured addresses, there will beproblems in the network.

O&MEthernetconnection

NetAct RNC

Computer withElement Manager

OMS

OMUESA24


17/09/2007


Steps

1. Connect the network element physically to the external routervia ESA12/ESA24 Ethernet switch

Connect the router to the ESA12/ESA24 switch.

2. Configure the external router according to instructionsprovided by the router vendor

2.10 Connecting to O&M backbone via ATM interfaces

Purpose

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

Note

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

Before you start

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

Steps

1. Configure IP over ATM interface to the functional unit

Refer the instructions in Creating and modifying IP over ATMinterfaces.

2. Assign IP addresses to the interfaces

Defining the destination IP address creates a static route in therouting table for the IP interface.

DN02143138Issue 11-2 en17/09/2007



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>,[<point to point interface type>]:[<IP address>],[<IPaddress type>]:[<prefix length>]:[<destination IPaddress>];


17/09/2007


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

Purpose

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

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

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

By using star topology, O&M connections can use the same VPI as controlplane 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 usethe 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 thatthe O&M connection can use the free capacity of the link more easily.

Note

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

For more information on the topologies, see the Nokia WCDMA RANSystem Information Set.

You can use either static routing or dynamic routing (OSPF) for BTS O&M.If you use OSPF, you do not need to configure static routes towards theBTSs. When you create the OSPF configuration, the routes areautomatically created after the configuration.

DN02143138Issue 11-2 en17/09/2007



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

Note

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

Before you start

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

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

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

Steps

1. Start the MMI Window in the Element Manager

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

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

For instructions, see Creating and modifying IP over ATM interfaces.

3. If you are using static routing

Then


17/09/2007


Create static route for BTS O&M

For O&M connections towards BTS, configure the route from OMUto the IP address of the gateway that is on the other side of the point-to-point ATM connections (AXC address of BTS site).

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

Note

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

4. If you are using OSPF

Then

Configure OSPF area parameters and interfaces

a. Define the OSPF parameters of an OSPF router.

The area identification specifies the area ID for a new OSPF.The area ID is entered as a dotted-quad. The IP networknumber of a subnetted network may be used as the area ID. Itis recommended that all OSPF areas except the backbone beconfigured as totally stubby areas.


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

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

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

DN02143138Issue 11-2 en17/09/2007



Further information

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

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

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

1. Create IP interfaces towards every BTS in OMU.

Assign logical IP addresses to the unnumbered point-to-pointnetwork interfaces of the OMU unit, with MTU value 1500.

OMS

RNC

RNC ElementManager

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


17/09/2007


Note

Unnumbered IP address should be the same as IP address of ELinterface. If you don't know what IP address is in use on EL interface,check the configuration first by QRI command, for example:

ZQRI:OMU:EL0;

ZQRN:OMU:AA1,U:10.1.1.2,L::10.1.2.1:1500:UP;

ZQRN:OMU:AA2,U:10.1.1.2,L::10.1.3.1:1500:UP;

...

ZQRN:OMU:AA31,U:10.1.1.2,L::10.1.32.1:1500:UP;

ZQRN:OMU:AA32,U:10.1.1.2,L::10.1.33.1:1500:UP;

2. Create an IP over ATM interface between the IP interface and theATM termination point.

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

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


...



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

ZQKE:OMU,0:10.1.2.0:Y,,Y;

ZQKE:OMU,1:10.1.2.0:Y,,Y;

4. Configure the OSPF interface parameters of an OSPF router.

ZQKF:OMU,0:AA1:10.1.2.0::120;

ZQKF:OMU,1:AA1:10.1.2.0::120;

ZQKF:OMU,0:AA2:10.1.2.0::120;

ZQKF:OMU,1:AA2:10.1.2.0::120;

DN02143138Issue 11-2 en17/09/2007



...

ZQKF:OMU,0:AA31:10.1.2.0::120;

ZQKF:OMU,1:AA31:10.1.2.0::120;

ZQKF:OMU,0:AA32:10.1.2.0::120;

ZQKF:OMU,1:AA32:10.1.2.0::120;

Example Configuring IP for BTS O&M using tree topology ATM layer

This example presents IP for BTS O&M configuration in RNC when treetopology ATM layer and static routing are used.

1. Create IP interfaces towards the BTS in OMU.

Assign logical IP addresses and destination IP addresses to theunnumbered point-to-point network interfaces of the OMU unit, withMTU value 1500, and accept default values for the rest of theparameters.

ZQRN:OMU:AA1,U:10.1.1.2,L::10.1.2.1:1500:UP;

ZQRN:OMU:AA2,U:10.1.1.2,L::10.1.3.1:1500:UP;

2. Create an IP over ATM interface between the IP interface and theATM termination point.

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



3. Create static routes for the BTS branch.

Create static routes for OMU to the IP subnetworks 10.1.2.0/24 and10.1.3.0/24 via the router with IP addresses 10.1.2.1 and 10.1.3.1.

ZQKC:OMU,0:10.1.2.0,24:10.1.2.1,:LOG;

ZQKC:OMU,0:10.1.3.0,24:10.1.3.1,:LOG;


17/09/2007


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

Purpose

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

Before you start

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

Steps

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

Check that the units for which you are going to create networkinterfaces are in working state (WO-EX).

ZUSI:<unit type>;

2. Create IP over ATM interfaces to all GTPUs

Create IPoA interfaces to all GTPUs (at least one ATM VCCs perGTPU) according to instructions in Creating and modifying IP overATM interfaces. Set the value of the encapsulation methodparameter to LLC/SNAP.

If you want to dedicate a GTPU for real-time IP traffic, set the valueof usage parameter to IPOART (this is an optional feature) for all IPoAinterfaces of the unit.

DN02143138Issue 11-2 en17/09/2007



IPoA interfaces can support 2 VCCs under one interface. TheseVCCs have different usage parameters. So you can dedicate oneVCC to real-time IP traffic under a given IPoA interface. For moreinformation about configuring 2 VCCs for one IPoA interface, refer toCreating and modifying IP over ATM interfaces.

3. Configure the default static routes

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

For IPv4:

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

Note

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

For IPv6:

ZQ7C:<unit type>,<unit index>:<destination IPaddress>,[<prefix length>]:<gateway IP address>:[<route type>]:[<route preference>];

4. Create other static routes, if needed

For IPv4:

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

For IPv6:



17/09/2007


5. Create OSPF configuration, if necessary

Currently, OSPF only supports IPv4. If you want to use OSPF routingon the Iu-PS interface, create the configuration as follows:

a. Set the IP address for loopback.

ZQRN:<unit type>,<unit index>:<interface name>:<IP address>;

b. Configure the OSPF to inform other OSPF routers of theloopback address.

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

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


d. Configure an interface for that area.

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

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

It is also possible to configure QoS DiffServ traffic classification toGTPU units. The main function for IP QoS DiffServ is to assure thatreal time (RT) traffic has a higher throughput priority than non-realtime (NRT) traffic in the GTPU TCP/IP stack. It checks that the trafficis real time or non-real time and processes the traffic base on thedesired ratio. For detailed instructions, refer to Creating andmodifying IP QoS configuration.

Example IP configuration for Iu-PS with each GTPU connected to oneSGSN unit

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

DN02143138Issue 11-2 en17/09/2007



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

1. Create ATM resources.

Create the following ATM configuration (for instructions, seeCreating ATM resources in RNC in ATM Resource Management):. STM-1 ATM interface (with interface ID 1). This interface is

connected to SGSN (GPLC-1) via a direct physical connectionor via the SDH transmission network.

. In ATM interface 1, one VPLtp with VPI=0.

. In ATM interface 1, two VCLtps with VPI=0 and VCI=40, 41.

. STM-1 ATM interface (with interface ID 2). This interface isconnected to SGSN (GPLC-2) via a direct physical connectionor via the SDH transmission network.


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

10.1.2.13AA1GTPU-3

10.1.1.1

10.1.2.1

GPLC1

GPLC2

RNC SGSN

VPI=0, VCI=40

STM-1 line #1

STM-1 line #2

VPI=0, VCI=42

VPI=0, VCI=43

GPLC-1

GPLC-2

VPI=0, VCI=41


17/09/2007


a. Create IP over ATM interfaces connected to GPLC-1.

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


b. Create IP over ATM interfaces connected to GPLC-2.



3. Assign IP addresses to the network interfaces.

a. Configure interfaces connected to 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 GPLC-2.

ZQRN:GTPU,2:AA1:10.1.2.12,P:32:10.1.2.1;

ZQRN:GTPU,3:AA1:10.1.2.13,P:32:10.1.2.1;

4. Create static routes for GTPUs.

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

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




Example IP configuration for Iu-PS with GTPUs connected to bothSGSN units

This example shows how to configure the Iu-PS interface between theRNC and SGSN using two STM-1 interfaces in RNC and SGSN. In thisexample, four GTPU units are deployed to handle the Packet SwitchedRadio Access Bearers in RNC in load sharing mode. Each GTPU islogically connected to both GPLC units in the SGSN so that even if onelink fails, the interface capacity between the RNC and SGSN remains thesame. In this example, redundant static routes are deployed to archive thepurpose. Redundant static routing is an new feature in RNC3.0. Note thatthe same redundancy can be achieved by using OSPF instead of staticrouting (see the next example: configuring Iu-PS when OSPF is in use).

On each GTPU, 2 default routes with different preferences are configured.When both links are working, the default route with higher preference(lower preference value), also called primary route in this chapter, will beselected to forward Iu-PS packets. Whenever the link used by the primaryroute fails, the other route, for example, the one with lower preference, willbe activated.

DN02143138Issue 11-2 en17/09/2007



The redundant static routes in this example are designed that the load canbe shared between the two links if both of them are working. The primaryroutes of GTPU-0 and GTPU-2 use the link to GPLC1, while the one toGPLC2 is preferred by GTPU-1 and GTPU-3.

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


Create the following ATM configuration (for instructions, seeCreating ATM resources in RNC in ATM Resource Management):. STM-1 ATM interface (with interface ID 0). This interface is

connected to SGSN (GPLC-1) via a direct physical connectionor via the SDH transmission network.


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


RNC SGSN

VPI=0, VCI=41

VPI=0, VCI=40

VPI=0, VCI=43

VPI=0, VCI=42

STM-1 line #1

STM-1 line #2

VPI=0, VCI=41

VPI=0, VCI=40

VPI=0, VCI=43

VPI=0, VCI=42

GPLC-1

GPCL-2

= primary route

GPLC-2

10.1.2.1

AA0

AA1GTPU-0

AA0

AA1GTPU-2

AA0

AA1GTPU-1

AA0

AA1GTPU-3

10.1.1.1

GPLC-1

10.1.1.13 10.1.1.1

10.1.2.12 10.1.2.1

10.1.1.11 10.1.1.1

10.1.2.10 10.1.2.1

10.1.1.10 10.1.1.1

10.1.2.11 10.1.2.1

10.1.1.12 10.1.1.1

10.1.2.13 10.1.2.1


17/09/2007

















ZQRN:GTPU,0:AA0:10.1.1.10,P:32:10.1.1.1;

ZQRN:GTPU,1:AA0:10.1.1.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.1.13,P:32:10.1.1.1;

b. Configure interfaces connected to GPLC-2.

ZQRN:GTPU,0:AA1:10.1.2.10,P:32:10.1.2.1;

ZQRN:GTPU,1:AA1:10.1.2.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.2.13,P:32:10.1.2.1;

4. Create default static routes for GTPUs.

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

ZQKC:GTPU,0::10.1.2.1,:PHY:1;

ZQKC:GTPU,1::10.1.2.1,:PHY:0;

ZQKC:GTPU,1::10.1.1.1,:PHY:1;

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

ZQKC:GTPU,2::10.1.2.1,:PHY:1;

ZQKC:GTPU,3::10.1.2.1,:PHY:0;

ZQKC:GTPU,3::10.1.1.1,:PHY:1;

DN02143138Issue 11-2 en17/09/2007



Example Configuring Iu-PS when OSPF is in use

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

In this example, the address of Lo0 interface, which will be used as GTPendpoint on GTPUs, will be distributed to SGSN by either configuring it asa stub host, or redistribute Lo0 interface into ospf routing domain. Similarly,the address used as GTP endpoint on SGSN should be imported to ospfproperly to be learnt by GTPU. Refer to the manual of SGSN for moredetails.

Figure 14. Iu-PS configuration with OSPF in use


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

RNC SGSN

VPI=0, VCI=41

VPI=0, VCI=40

VPI=0, VCI=43

VPI=0, VCI=42

STM-1 line #1

STM-1 line #2

VPI=0, VCI=41

VPI=0, VCI=40

VPI=0, VCI=43

VPI=0, VCI=42

= subnet 10.2.0.1/32

= subnet 10.3.0.1/32

= primary route

10.1.2.110.3.0.1

GPLC-2

10.1.1.1

10.2.0.1

GPLC-1

AA1GTPU-0

AA0

AA1GTPU-1

AA0

AA1

GTPU-2

AA0

AA1

GTPU-3

10.1.2.10 10.1.2.1

AA0 10.1.1.10 10.1.1.1

10.1.1.11 10.1.1.1

10.1.2.11 10.1.2.1

10.1.1.12 10.1.1.1

10.1.2.12 10.1.2.1

10.1.1.13 10.1.1.1

10.1.2.13 10.1.2.1

LO0 10.1.1.2

LO0 10.1.1.3

LO0 10.1.1.4

LO0 10.1.1.5


17/09/2007





















ZQRN:GTPU,0:AA0:10.1.1.10,P:32:10.1.1.1;

ZQRN:GTPU,1:AA0:10.1.1.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.1.13,P:32:10.1.1.1;

b. Configure interfaces connected to GPLC-2.

ZQRN:GTPU,0:AA1:10.1.2.10,P:32:10.1.2.1;

ZQRN:GTPU,1:AA1:10.1.2.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.2.13,P:32:10.1.2.1;

c. Set the loopback IP address for each unit.

ZQRN:GTPU,0:LO0:10.1.1.2;




4. Create the OSPF configuration.

DN02143138Issue 11-2 en17/09/2007



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

ZQKE:GTPU,0:0.0.0.1;




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

Note

we can select AA0 or AA1 as the primary route for user traffic by givingdifferent ospf costs. The interface with lower cost will be preferred.

ZQKF:GTPU,0:AA0:0.0.0.1:::10;

ZQKF:GTPU,0:AA1:0.0.0.1:::20;

ZQKF:GTPU,1:AA0:0.0.0.1:::20;

ZQKF:GTPU,1:AA1:0.0.0.1:::10;

ZQKF:GTPU,2:AA0:0.0.0.1:::10;

ZQKF:GTPU,2:AA1:0.0.0.1:::20;

ZQKF:GTPU,3:AA0:0.0.0.1:::20;

ZQKF:GTPU,3:AA1:0.0.0.1:::10;

c. Configure the OSPF to inform other OSPF routers of theloopback address.

ZQKJ:GTPU,0:0.0.0.1:ADD:10.1.1.2:;

ZQKJ:GTPU,1:0.0.0.1:ADD:10.1.1.3:;

ZQKJ:GTPU,2:0.0.0.1:ADD:10.1.1.4:;

ZQKJ:GTPU,3:0.0.0.1:ADD:10.1.1.5:;

Note

If the area in step 4.a is not configured as stub area, redistribution canbe also used to inform the address of LO0.

ZQKU:GTPU,0:IF=LO0;

ZQKU:GTPU,1:IF=LO0;

ZQKU:GTPU,2:IF=LO0;

ZQKU:GTPU,3:IF=LO0;


17/09/2007


Example IP configuration for Iu-PS with dedicated VCC for RT traffic

This example shows how to configure the Iu-PS interface between RNCand SGSN using dedicated VCC for RT traffic. In the example, every IPoAinterface have 2 VCCs, one is for RT traffic, the other is for NRT traffic.

From RNC’s point of view, the egress traffic is treated according to its QoSattribute. But for ingress traffic, which VCC will be chosen is determined bySGSN.

Figure 15. ATM virtual channel connections and IP addresses with 2 VCCsunder one IPoA interface

1. Create ATM resources

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

STM-1 ATM interface (with interface ID 1). This interface isconnected to SGSN (GPLC-1) via a direct physical connection or viathe SDH transmission network.

10.1.1.10AA1GTPU-0

10.1.1.11AA1GTPU-1

10.1.1.12AA1GTPU-2

10.1.1.13AA1GTPU-3

10.1.1.1

10.1.2.1

GPLC1

GPLC2

RNC SGSN

VPI=0, VCI=39

STM-1 line #1

STM-1 line #2

VPI=0, VCI=43

VPI=0, VCI=44

NRT

RT

VPI=0, VCI=40

VPI=0, VCI=38

VPI=0, VCI=41

VPI=0, VCI=42

VPI=0, VCI=45

DN02143138Issue 11-2 en17/09/2007



In ATM interface 1, one VPLtp with VPI=0.

In ATM interface 1, four VCLtps with VPI=0 and VCI=38, 39, 40, 41.

STM-1 ATM interface (with interface ID 2). This interface isconnected to SGSN (GPLC-2) via a direct physical connection or viathe SDH transmission network.

In ATM interface 2, one VPLtp with VPI=0.

In ATM interface 2, four VCLtps with VPI=0 and VCI=42, 43, 44, 45.

2. Create IP over ATM interfaces to all GTPUs

a. Create IP over ATM interfaces connected to GPLC-1


ZQMF:GTPU,0,L:AA1:1,0,39:1,IPOART;



b. Create IP over ATM interfaces connected to GPLC-2





3. Assign IP addresses to the network interfaces

a. Configure interfaces connected to 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 GPLC-2

ZQRN:GTPU,2:AA1:10.1.2.12,P:32:10.1.2.1;

ZQRN:GTPU,3:AA1:10.1.2.13,P:32:10.1.2.1;

4. Create static routes for GTPUs

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






17/09/2007


5 Configuring Signalling Transport over IPfor Control Plane

Purpose

The purpose of this procedure is to configure the IP-based signallingtransport over ATM connection for RNC control plane. IP-based Iu-PS, Iu-CS and Iur SS7 signalling stack can be used. For more detaileddescription, refer to Configuring IP-based signalling channels.

Before you start

ATM resources must be created before starting this procedure. Signallingunit shall be in active state before configuration starts.

Steps

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

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

Note

Signalling unit should be an active state before configuration.

2. Assign IP addresses to both ATM interfaces of a signalling unit(QRN).

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

DN02143138Issue 11-2 en17/09/2007


Configuring Signalling Transport over IP for Control Plane

Note

IP addresses must be assigned from different sub-networks.

3. Create Static Routes if needed (QKC).

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

Note

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

Example

The following example shows how to configure ICSU-0 to connect toSGSN with IP over ATM connection. Suppose the subnet address for Iu-PS signaling of SGSN is 10.2.3.0/24. The ATM AAL5 connection shouldbe configured properly beforehand.

ZQMF:ICSU,0,L:AA0:1,0,40:1,IPOAM;

ZQRN:ICSU,0:AA0,N:10.20.1.1,L::10.20.1.2:;

ZQKC:ICSU,0:10.2.3.0,24:10.20.1.2,:LOG:;


17/09/2007


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

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

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

Before you start

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

Steps

1. Check the selected ICSU unit towards the CBC

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

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

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

ZUSI:ICSU;

DN02143138Issue 11-2 en17/09/2007



2. Create the IP over ATM interface to selected ICSU

Create the IP over ATM interface to selected ICSU towards the CBCaccording to the instructions in Creating and modifying IP over ATMinterfaces.

If you want to distribute incoming traffic between several ICSU units,then create as many IP over ATM interfaces as needed (oneseparate IP over ATM interface for each used ICSU) towards theCBC. In this case, only selected ICSU unit is sending RNCoriginated Restart and Failure messages towards the CBC. TheCBC must be configured to send data to different IP addresses, thatis, to different ICSU units.

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

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

The destination IP address is the address of the router interfaceor the CBC interface which terminates the VCC.

3. Create a static route for Iu-BC

For Iu-BC connections towards the CBC, configure one static routewith route type "LOG" for selected ICSU to the IP address of therouter terminating IP over ATM PVCs. Static routes are needed onlyin the case when the CBC is not directly connected to the RNC.

Note

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

For IPv4:


17/09/2007


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

Note

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

For IPv6:


Example Configuring IP for Iu-BC through ICSU units

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

DN02143138Issue 11-2 en17/09/2007



Figure 16. Example of IPv4 configuration for Iu-BC

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

For IPv4 case:

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

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

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

ICSU-1

ICSU-2

ICSU-18

...

RNC

NIS

STM-1

MGW

VPcross

connects

NIS

VPI=x

NIS

VPI=y

Router terminatingIP over ATM PVCs(can also be anextra ATM Interface)

anymedia

Core siteRNC site

ICSU-010.1.1.1

CBC

subnet 10.1.1.0/32

10.1.1.200


17/09/2007


Note

Note: The ICSU-0 is selected to be used towards the CBC.

3. Assign an IPV4 address to the selected ICSU.

ZQRN:ICSU,0:AA1:10.1.1.1,L:32:10.1.1.200;

4. Create a static route for selected ICSU.

With the following default routes, all traffic is forwarded to the routerterminating IP over ATM PVCs.

ZQKC:ICSU,0::10.1.1.200,:LOG;

For IPv6 case: with the same figure, replace the IPv4 address "10.1.1.1"with IPv6 address "3FFE:1200:3012:C020:580:8FFF:FE7A:7BB7" and theIPv4 address "10.1.1.200" with IPv6 address "3FFE:1200:3012:C020:580:8FFF:FE7A:4BB4".

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

2. Create IPv6 over ATM interfaces connected to subnetwork toselected ICSU.

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

Note: The ICSU-0 is selected to be used towards the CBC.

3. Assign an IPv6 address to the selected ICSU.

ZQ6N:ICSU,0:AA1:"3FFE:1200:3012:C020:580:8FFF:FE7A:7BB7",L:128:"3FFE:1200:3012:C020:580:8FFF:FE7A:4BB4";

4. Create a static route for each ICSU.

With the following default routes, all traffic is forwarded to the routerterminating IP over ATM PVCs. A static route is needed for eachICSU because during the ICSU switchover static route is notswitching to the new unit.

ZQ7C:ICSU,0::"3FFE:1200:3012:C020:580:8FFF:FE7A:4BB4":LOG;


...

DN02143138Issue 11-2 en17/09/2007





17/09/2007


7 Creating and modifying DNSconfiguration

Purpose

You can create the DNS configuration with the QRK command in IPv4, andQ6K command in IPv6. The interface-specific instructions for configuringthe DNS can be found in the integration instructions.

Before you start

Note

In addition to the MML based configuration the IP layer can beconfigured via the IP plan interface from the NetAct. The IP plansupport does not contain the OSPF configuration.

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

Steps

1. Interrogate DNS parameter data

You can interrogate current DNS parameters with QRJ in IPv4, andQ6J in IPv6. These commands have no parameters.

ZQRJ;

ZQ6J;

Expected outcome

DN02143138Issue 11-2 en17/09/2007


Creating and modifying DNS configuration

If the DNS service is utilised in IP data transfer, a common domainname of the local environment and the DNS server addresses aredisplayed. All the computer units of the network element that have IPservices belong to the same domain.

2. Modify DNS configuration

This command defines whether or not the DNS service is utilised inIP data transfer. You can also use this command to add a DNS nameserver address.

For IPv4:

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

For IPv6:

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

3. Remove DNS name server address from use

For IPv4:

ZQRK:0.0.0.0,0.0.0.0,0.0.0.0,<local domain name>;

For IPv6:

ZQ6K:"::",,,<local domain name>;

If you want to leave the primary DNS server unchanged, do not giveany values for the first parameters. If the first DNS nameserver set to0.0.0.0, then all those three DNS servers will be disabled.

Example Enabling and disabling DNS service for IPv4 data transfer

This example shows how to set DNS service for IPv4 data transfer.

ZQRK:172.23.69.12,172.23.69.13,172.23.69.14,"HOST.NET",10.0.1.0,24:YES,YES:;


17/09/2007


If you want to disable DNS only in the third DNS server, and keep others,give the command

ZQRK:,,0.0.0.0,"HOST.NET",10.0.1.0,24:YES,YES:;

Example Enabling and disabling DNS service for IPv6 data transfer

This example shows how to set DNS service for IPv6 data transfer.

1. Enable DNS and use IPv6 address3FFE:1200:333A:444B:555C:666D:777E:888F as primary server,IP address 3FFE:1200:888A:777B:666C:555D:444E:333F assecondary server, and3FFE:1200:333F:444E:555D:666C:777B:888A as the third server.The domain name is HOST.NET. Network sortlist is3FFE:1200:3012:C020:0280:5FFF:222A:4BB5 and prefix is 32.Resolver cache and round robin are in USE status.

ZQ6K: "3FFE:1200:333A:444B:555C:666D:777E:888F","3FFE:1200:888A:777B:666C:555D:444E:333F","3FFE:1200:333F:444E:555D:666C:777B:88A", "HOST.NET", "3FFE:1200:3012:C020:0280:5FFF:222A:4BB5",32:YES,YES;

2. Disable DNS, change the domain name to STARDUST.COM, andleave the network sortlist unchanged.

ZQ6K:"::",,,"STARDUST.COM";

DN02143138Issue 11-2 en17/09/2007




17/09/2007


8 Creating and modifying IP interfacesPurpose

You can configure a new network interface or IP address with the QRNcommand in IPv4, and Q6N in IPv6. You can find the interface-specificinstructions for configuring IP interfaces in the integration instructions.

Summary

Choose from the steps below the one or the ones that you need.

The last step, Change existing IP configuration for a point-to-pointinterface, gives detailed instructions for situations when the destinationaddress for the IP over ATM interface changes in interfaces whereInATMARP is in use. If you do not block the IPoA interface beforechanging the configuration in the IPA2800 network element, theInATMARP creates a new entry in the routing table and the QRN commandreturns error messages.

Steps

1. Interrogate network interfaces

Check the configured network interfaces of the computer unit beforeconfiguring new ones.

For IPv4:

ZQRI:<unit type>,<unit index>::YES;

For IPv6:

ZQ6I:<unit type>,<unit index>::YES:;

2. Create IP interfaces

For IPv4:

DN02143138Issue 11-2 en17/09/2007




For IPv6:

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

Table 4. MTU values for different units

ISU, ICSU, GTPUand OMU units

TCU units IPFGE units

EL AA IFETH AI IFETH IFFGE AI AA

Min MTU 1500 1 1500 1500 1500 1500 1500 1500

Max MTU 1500 9180 1500 1500 1500 1500 1500 1500

DefaultMTU

1500 9180 1500 1500 1500 1500 1500 1500

Note

The MTU value should be set according to the table when you create ormodify the interfaces for the ISU, ICSU, GTPU, OMU, TCU and IPFE(P), IPGE(P), IPFGE units.

3. Modify IP interfaces

Identify the IP interface you want to modify with the parameters unittype, unit index and interface name.

For IPv4:


For IPv6:


17/09/2007


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

The numbered or unnumbered point to point interface typeparameter is valid only for ATM point-to-point interfaces. If you wantto change the point-to-point interface type you must remove theinterface by using QRG command for IPv4, Q6G command for IPv6and configure it to another point-to-point interface type.

N A numbered interface has a unique IP address.This value is the default.

U An unnumbered interface does not have aunique IP address. It shares its IP address withthe Ethernet interface IP address.

4. Delete IP interface

Before deleting all IP addresses from the network interface, deleteall the static routes that have been configured for the interface. Fordetailed instructions, see Creating and modifying static routes.

For IPv4:

ZQRG:<unit type>,<unit index>:<interface name...>;

For IPv6:

ZQ6G:<unit type>,<unit index>:<interface name...>;

5. Change existing IP configuration for a point-to-point interface

If you want to change the IP configuration in a point-to-point interfacewhere InATMARP is used, follow the steps below:

a. Block the IPoA VCC (QMG)

ZQMG:UNIT=<unit type> | <ATM=<ATM interface> |USAGE=<usage> | INDEX=<unit index>:[<VPI> | alldef,<VCI> | all def]:<change>;

b. Delete the existing routing.

If OSPF is in use, delete the OSPF interface:

ZQKL:<unit type>,<unit index>: [<interfaceidentification>];

DN02143138Issue 11-2 en17/09/2007



If static routing is in use, delete all the static routes that havebeen configured for the interface. For detailed instructions, seeCreating and modifying static routes.

c. Delete the IP address (QRG)

ZQRG:<unit type>,<unit index>:<interfacename...>;

d. Create the new IP address (QRN)

ZQRN:<unit type>,<unit index>:<interface name>,(<point to point interface type>):(<IPaddress>),(<IP address type> ):(<netmasklength>):(<destination IP address>):(<MTU>):(<state>);

e. Unblock the IPoA VCC (QMG)

ZQMG:UNIT=<unit type> | <ATM=<ATM interface> |USAGE=<usage> | INDEX=<unit index>:[<VPI> | alldef,<VCI> | all def]:<change>;

f. Reconfigure routing.

If OSPF is in use, reconfigure the OSPF parameters:

ZQKF:<unit type>,<unit index>:<interfaceidentification>:<area identification>;

If static routing is in use, create new static routes. For detailedinstructions, see Creating and modifying static routes.

Example Adding a new IPv4 address to OMU

This example shows how to add a new IP address to the EL0 interface ofthe OMU unit with index 0. The IP address of the interface is 10.20.41.130and netmask length is 24.

ZQRN:OMU,0:EL0:10.20.41.130:24;

Example Creating a logical IPv4 address for a 2N redundant unit

If you want to create a logical IPv4 address for a 2N redundant unit, do notgive the unit index parameter and set the IP address type parameterwith value L. In this example, the netmask length is 27 and the status is setto UP.

ZQRN:OMU:EL0:131.228.45.179,L:27:::UP;

Example Changing the existing IPv4 configuration for a point-to-pointinterface

This example changes the IPv4 configuration for OMU interface AA11.


17/09/2007


1. Block the IPoA VCC (QMG)

ZQMG:ATM=11:0,32:2;

2. Delete the OSPF interface in OMU-1 (QKL)

ZQKL:OMU,1:AA11;

3. Delete the IP address in OMU-1 (QRG)

ZQRG:OMU,1:AA11;

4. Create the new IP address (QRN)

ZQRN:OMU:AA11,U:10.1.1.2,L::10.1.12.1:1500:UP;

5. Unblock the IPoA VCC (QMG)

ZQMG:ATM=11:0,32:1;

6. Reconfigure the OSPF parameters (QKF)

ZQKF:OMU,1:AA11:10.1.12.0;

ZQKF:OMU,0:AA11:10.1.12.0;

Example Creating a logical IPv6 address for a 2N redundant unit

This example shows how to add a logical IPv6 address to the EL0interface of OMU unit.

ZQ6N:OMU:EL0:"3FFE:1200:3:12:C020:280:5FFF:FE4A:4BB7",L;

DN02143138Issue 11-2 en17/09/2007




17/09/2007


9 Modifying IP parametersPurpose

You can specify the parameters specific to the IP protocol stack with theQRT command in IPv4. You can set host names, define if the unit forwardsIP packets, set the maximum time-to-live value and define if the subnetsare considered to be local addresses. The IP parameters can be deletedusing QRV command.

You can specify the parameters specific to the IP protocol stack with theQ6Tcommand in IPv6. You can define if the unit forwards IPv6 packets, setthe hop limit value and define if the unit receives router advertisements.The IP parameters can be deleted with the Q6V command.

Before you start

Note

In addition to the MML based configuration the IP layer can beconfigured via the IP plan interface from the NetAct. For further detailson the IP plan interface see IP plan interface in document RNCOperation and Maintenance.

Steps

1. Interrogate TCP/IP parameters

For IPv4:

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

For IPv6:

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

DN02143138Issue 11-2 en17/09/2007


Modifying IP parameters

2. Modify TCP/IP parameters

For IPv4:

The default value for TTL is 64, and for SNL is YES.

Chorus units do not support local subnets (SNL).

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

For IPv6:

ZQ6T:<unit type>,<unit index>:(IPF=<IP forwarding>,[HLIM=<hoplimit>],[RADV=<router advertisment>]);

3. Delete TCP/IP parameters

For IPv4:

ZQRV:<unit type>,[<unit index>];

For IPv6:

ZQ6V:<unit type>,[<unit index>];

Example Modifying IPv4 parameters in OMU

This example shows how to modify the IP parameters in the OMU unit. Setthe unit type parameter to OMU, and the HOST parameter to what isdetailed in the IP address plan (for example, OMU). In the MGW, set theIPF parameter to NO and in the RNC to YES. Set the TTL parameter todefault and the SNL parameter to NO.

In the MGW:

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

In the RNC:

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


17/09/2007


Example Modifying IPv6 parameters in OMU

This example shows how to modify the IP parameters in the OMU unit. Setthe unit type parameter to OMU. In the MGW, set the IPF parameter toOFF and in the RNC to ON. Set the HLIM parameter to default and theRADV parameter to OFF.

In the MGW:

ZQ6T:OMU,0:IPF=OFF,HLIM=64,RADV=OFF;

In the RNC:


DN02143138Issue 11-2 en17/09/2007




17/09/2007


10 Creating and modifying IP over ATMinterfaces

Purpose

This procedure describes how to interrogate, create, and modify bothinternal and external IP over ATM (IPoA) interfaces. The interface-specificinstructions for configuring IP interfaces can be found in the integrationinstructions.

Before you start

The ATM interfaces and external termination points have to be configuredbefore you can configure external IPoA interfaces. For more information,refer to ATM resources in ATM Resource Management.

You need the ATM virtual channel configuration information when youcreate external IPoA interfaces. You have to know the “interfaceidentification” values of the network interface units, virtual path identifiers(VPI), and virtual channel identifiers (VCI). If you do not have thisinformation, you can use LAI and LCI commands to interrogate ATMinterfaces and external termination points.

Steps

1. Interrogate external IP over ATM interfaces (QMI)

ZQMI:[<unit type>],[<unit index>],[<logical/physical connection type>]:[<IP interface>]:[<ATMinterface>],[<VPI>],[<VCI>]:[<encapsulation>]:[<state>];

2. Create external IP over ATM interfaces (QMF)

The QMF command creates a VC from an external termination pointat the unit to the internal termination point in the computer unit andattaches the new VC to an IP interface.

DN02143138Issue 11-2 en17/09/2007



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

3. Delete IP over ATM interfaces (QMD)

The ATM interface, VPI number, VCI number parameters definewhich external termination point is disconnected from the IPinterface of the unit. These parameters are only needed whendeleting an external connection.

The unit_2 type, unit_2 index and IP interface_2 parametersare in use only when deleting an internal connection.

ZQMD:<remove type>:<unit type>,[<unit index>]:<IPinterface>:[<ATM interface>],[<VPI number>],[<VCInumber>]:[<unit_2 type>],[<unit_2 index>]:[<IPinterface_2>];

Example Configuring IP over ATM interface

Configure IP over ATM interface with network interface AA2 to OMU-0from ATM interface 3 (NIU-1), VPI 20, and VCI 30 with encapsulationmethod VCMUX.

ZQMF:OMU,,L:AA2:3,20,30:2;

Configure IP over ATM interface with network interface AA3 to OMU-0from ATM interface 4 (NIU-2), VPI 20, and VCI 30 with encapsulationmethod VCMUX.

ZQMF:OMU,0,P:AA3:4,20,30:2;

Example Configuring two IPoA connections to one IP over ATMinterfaces

Configure two IPoA connections to IPoA interface AA0 of GTPU-0. Thefirst IPoA connection is from ATM interface 4(NIU-2), VPI 20 and VCI 30with encapsulation method LLC/SNAP. The second IPoA connection isfrom ATM interface 4(NIU-2), VPI 20 and VCI 31 with encapsulationmethod LLC/SNAP.




17/09/2007


Only GTPU can support two IPoA connections under one IPoA interface.These two IPoA connections’ usages must be different. Usually one is forIPOAUD, the other is for IPOART.

Example Interrogate external IP over ATM interfaces

ZQMI:OMU;

Expected outcome

INTERFACE CONFIGURED FOR EXTERNAL USE:

OPER ADMIN

UNIT&INDEX TYPE IP INT ATM IF VPI VCI ENC METHOD USAGE STATE STATE

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

OMU LOG AA2 3 20 30 VCMUX IPOAM RUN UP

OMU-0 PHY AA3 3 20 30 VCMUX IPOAM RUN UP

DN02143138Issue 11-2 en17/09/2007




17/09/2007


11 Modifying OSPF configurationPurpose

You can modify the OSPF router parameters, area parameters, andinterface parameters of an OSPF router after the OSPF configuration hasbeen created. You can also define a network prefix in the OSPF area,configure virtual link parameters and define a stub host in the OSPF area.

The interface-specific instructions for configuring OSPF can be found inthe integration instructions.

Steps

1. Configure OSPF router parameters (QKS)

This command defines the OSPF parameters of an OSPF router.

ZQKS:<unit type>,<unit index>:[MOD|DEL],<routerid>:<rfc1583compatibility>:<spf delay>:<spf holdtime>;

Remove the router parameters with route id 0.0.0.0.

2. Configure OSPF area parameters (QKE)

This command defines the OSPF area (both backbone and otherarea) parameters of an OSPF router.


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

DN02143138Issue 11-2 en17/09/2007



Note

The area parameters do not become effective (written into theconfiguration file) until there exists an interface which has the areaattached to itself.

3. Configure OSPF interface parameters (QKF)

This command defines the OSPF interface parameters of an OSPFrouter.

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

4. Configure redistribute parameters (QKU)

Configure the redistribute parameters of an OSPF router.

ZQKU:<unit type>,[<unit index>:<redistribute typeand identification>:<metric>;

5. Configure network prefix, if required (QKH)

This command defines a network prefix in the OSPF area.Configuring the network prefix is optional.

ZQKH:<unit type>,<unit index>:<areaidentification>:<operation>:<network prefix>:<network prefix mask length>:<network prefixrestriction>;

6. Configure virtual link parameters, if required (QKV)

If there is an OSPF area which does not have a physical connectionto the backbone area, use a virtual link to provide a logical path fromthe disconnected area to the backbone area. Virtual links have to beconfigured to both ends of the link. The command QKV has to beentered separately for both border routers using the virtual link.


17/09/2007


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

Figure 17. Use of virtual link

7. Configure stub host, if required (QKJ)

This command defines a stub host in the OSPF area. Configuringthe stub host is optional.

ZQKJ:<unit type>,<unit index>:<areaidentification>:ADD:<stub host>:[<stub host cost>];

Area 0Backbone

Area 2

Area 1

Virtual link

Border router B

Border router A

DN02143138Issue 11-2 en17/09/2007




17/09/2007


12 Creating and modifying static routesPurpose

Static routes are used when dynamic routing (for example, OSPF) doesnot provide any useful function over the static routes. In other words theyare used when configuring a simple static route achieves the sameobjective as using the more complicated dynamic routing. Static routescan be used with dynamic routing when creating a host route to a host thatdoes not run dynamic routing.

Particularly, local IP based default routes are a special kind of static routes.An outgoing IP packet matching a local IP address based default route willbe sent according to its local IP address instead of its destination address.They usually cooperate with SCTP multihoming to ease the configurationof static routes on signalling units. Currently, only IPv4 is supported.

Steps

1. Interrogate IPv4 static routes (QKB)

The display level specifies how to display the search results. Thiscommand displays all possible static routes if the display level is"ALL"; it only displays current active static routes if it is "ACTIVE". Thedefault value is "ACTIVE".

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

If you do not enter any parameter values, the route information of allunits is listed.

2. Add IPv4 static routes (QKC)

DN02143138Issue 11-2 en17/09/2007



a. Add destination IP address based static routes.

The static route is identified with unit identification, destinationIP address, and next hop address. Unit identification identifiesthe unit where the information of unit type and unit index isused. Destination IP address and netmask length define thetarget.

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

b. Add local IP address based static routes.

The local IP address based default route is identified with unitidentification, local IP address, and next hop address. Unitidentification identifies the unit where the information of unittype and unit index is used.

ZQKC:<unit type>,<unit index>::<gateway IPaddress>,<local IP address>;

3. Delete IPv4 static routes (QKA)

a. Obtain the route number.

ZQKB:[<unit type>,[<unit index>]];

b. Delete the route by identifying it by its route number or bysource unit identification.

ZQKA:<route number>; or

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

You can delete the route by identifying it by its route number. Youcan obtain the route number with the QKB command.

ZQKA:<route number>:<unit type>,[<unit index>];

4. Interrogate IPv6 static routes (Q7B)

ZQ7B:[unit type,[<unit index>]];

If you do not enter any parameter values, the route information of allunits is listed.

5. Add IPv6 static routes (Q7C)

The static route is identified with unit identification, destination IPaddress and next hop address. Unit identification identifies the unitwhere this information is used. Destination IP address and prefixlength define the target.


17/09/2007



Note

Logical route is not supported for IPv6. If logical IPv6 address is used,the same IPv6 static route should be configured on all redundant units.

6. Delete IPv6 static routes (Q7A)

ZQ7A:<route number>:<unit type>,<unit index>;

Example Configuring the default static route in OMU

This example shows how to configure the default static route in OMU.

ZQKC:OMU,0::10.20.41.1,:;

Example Creating the default IPv6 static route for OMU

The same default route is used for both OMU-0 and OMU-1.

ZQ7C:OMU,0&&1::"3FFE:701:33:1A::1";

Example Configuring redundant static routes in OMU

This example shows how to configure multiple static routes to a samedestination in OMU. Each static route has a different preference. Lowerpreference value means higher preference.

ZQKC:OMU,0::10.2.10.1::0;

ZQKC:OMU,0::10.2.20.1::1;

In this example, when the gateway 10.2.10.1 is operational, only the firststatic route is used to forward packets. Whenever 10.2.10.1 becomesdown, the second one will take the duty.

DN02143138Issue 11-2 en17/09/2007




17/09/2007


13 Creating and modifying IP QoSconfiguration

Purpose

Differentiated Services (DiffServ) is the recommended IP QoS technologyin the UMTS networks and it is supported on GTPUs for Iu-PS user traffic.There are two traffic classes (TC) supported: RT is for real time and NRT isfor non real time traffic. The IP QoS handling mechanism is different fordownlink and uplink traffic:

. For downlink traffic, GTPU can classify IP traffic into RT and NRTand give different scheduling treatment during congestion based ontheir weights.

. For uplink traffic, GTPU can classify IP traffic into RT and NRT, andtransmit them through different VCCs based on the correspondingIPoA interface parameter (ATM usage tag, refer to IPoAconfiguration). It is so-called layer-two segregation.

Before you start

IP QoS configuration is only in GTPU for Iu-PS user plane. The sameconfiguration is for all GTPUs and Iu-PS user plane traffic.

Steps

1. Interrogate IP QoS configuration (Q8I)

ZQ8I;

2. Enable or disable DiffServ handling (Q8F)

Set the status of DiffServ handling separately by given DiffServswitches. There are three diffserv switches:

DN02143138Issue 11-2 en17/09/2007



ING : Switch to enable/disable DiffServ for Iu-PS downlink usertraffic. If it is disabled, all downlink IP traffic will get same treatmenton GTPUs.

SEG: Switch to enable/disable the layer-two segregation feature forIu-PS uplink user traffic.

DVCC: Switch to enable/disable using default VCC. This switch ismeaningful only if SEG switch is enabled. If it is disabled, when thereis no corresponding VCC configured for a sending IP packet, thepacket will be dropped. Otherwise, the traffic will be sent through thedefault VCC (VCC for NRT traffic if it exists, or VCC for RT traffic).

ZQ8F:[ING=<INGRESS DIFFSERV>|ENA/DIS],[SEG=<Layer 2SEGREGATION>|ENA/DIS],[DVCC=<USE DEFAULT VCC>|ENA/DIS];

3. Create or modify DSCP to traffic Class mapping (Q8C)

Operator can define the mapping from DiffServ code points (DSCP)to TC. The same mapping is used both for downlink and uplinktraffic.

ZQ8C:<traffic class>:[<data type>]:<DSCP number...>;

4. Modify RT and NRT ratio (Q8N)

Basically, this ratio is used for RT and NRT traffic throughput ofdownlink traffic. It will probably be adjusted according to the realtraffic situation. It can range from 1 to 50 (decimal). The default valueis 1.

ZQ8N:<BW>;

5. Configure UMTS traffic class to DSCP (Q8M)

Use this command to configure UMTS traffic class to DSCPmapping. Operator should give both UNTS TC and DSCP values inone parameter block. Operator should also give at least one pair ofthe mapping data.

UMTS TC value: This parameter identifies the UMTS traffic class.The value range is from 0 to 6 and it is obligatory.


17/09/2007


DSCP value: This parameter identifies the DSCP value. The valuerange is from 0 to 63 and it is obligatory.

ZQ8M:<UMTS TC>,<DSCP>:[<UMTS TC>,<DSCP>:<...>];

6. Interrogate the UMTS traffic class to DCSP (Q8Q)

ZQ8Q;

Example IP QoS configuration on GTPU for downlink traffic

Configure the IP QoS configuration for downlink traffic including DSCP totraffic class mapping. Enable or disable DiffServ handling and RT & NRTratio.

1. Interrogate IP QoS configuration and get the current IP QoSconfiguration.

ZQ8I;

2. Configure the DSCP to traffic class mapping.

ZQ8C:NRT:HEX:"2A";

ZQ8C:RT:DEC:"50,51";

3. Enable DiffServ for Iu-PS downlink user traffic and use the defaultVCC.

ZQ8F:ING=ENA;

4. Modify RT and NRT ratio.

ZQ8N:7;

Example IP QoS configuration on GTPU for uplink traffic

Configure the IP QoS configuration for uplink traffic including DSCP totraffic class mapping. Enable or disable DiffServ handling.

1. Interrogate IP QoS configuration and get the current IP QoSconfiguration.

ZQ8I;

2. Configure the DSCP to traffic class mapping.

ZQ8C:NRT:HEX:"2A";

ZQ8C:RT:DEC:"50,51";

DN02143138Issue 11-2 en17/09/2007



3. Enable layer-two segregation feature for Iu-PS uplink user traffic anduse the default VCC.

ZQ8F:SEG=ENA,DVCC=ENA;

Example IP QoS configuration on GTPU for UMTS traffic class to DCSPmapping

1. Configure the UMTS TC to DCSP mapping

ZQ8M:0,12:1,15:2,20;

2. Interrogate the UMTS TC to DCSP mapping

ZQ8Q;


17/09/2007


14 IP configuration files

14.1 IP configuration files

The configuration files for the IP protocol environment are:

Table 5. Configuration files in the IP protocol environment

Disk file Data file Description

POCPROZZ.IMG /etc/protocols Known (IP) protocols data.

POCSERZZ.IMG /etc/services Known network services data.

POCHOSZZ.IMG /etc/hosts Known hosts data.

POCRESZZ.IMG /etc/resolv.conf DNS resolver configuration data.

POCFTPZZ.IMG /etc/ftp.conf FTP server configuration data.

Note

IP configuration files should be initialized first and can not be modifiedby MML commands directly.

Protocols file (/etc/protocols)

The protocols file contains information regarding the known protocols usedon the Internet. The following information is presented for each protocol:

. official protocol name

. protocol number

. aliases

DN02143138Issue 11-2 en17/09/2007



Items are separated by any number of blanks and/or tab characters. '#'indicates the beginning of a comment; characters up to the end of the lineare not interpreted by routines which search the file. Protocol names maycontain any printable character other than a field delimiter, new line orcomment character.

The protocol file contains no tags or criticality information. The field iscommon for the file and can be determined in advance from AssignedNumbers and there should be no need to modify the file.

Example Protocol file

#

# Internet (IP) protocols

#

ip 0 IP # internet protocol, pseudo

icmp 1 ICMP # internet control message protocol

igmp 2 IGMP # internet group management protocol

ggp 3 GGP # gateway-gateway protocol

tcp 6 TCP # transmission control protocol

pup 12 PUP # PARC universal packet protocol

udp 17 UDP # user datagram protocol

ipv6 41 IPv6 # Internet Protocol, version 6

esp 50 ESP # Encapsulating Security Payload

ah 51 AH # Authentication Header

icmpv6 58 ICMPV6 # Internet Control Message Protocol v6

ospf 89 OSPFIGP # Open Shortest Path First IGP

...

Services file (/etc/services)

The services file contains information regarding the known servicesavailable in the Internet. The following information is presented for eachservice:

. official service name

. port number

. protocol name

. aliases

Items are separated by any number of blanks and/or tab characters. Theport number and protocol name are considered a single item; '/' is used toseparate the port and protocol (for example, 512/tcp). '#' indicates thebeginning of a comment; subsequent characters up to the end of the lineare not interpreted by the routines which search the file.

Service names may contain any printable character other than a fielddelimiter, new line, or comment character.


17/09/2007


The services file contains no tags or criticality information. The file iscommon to the whole network element. The contents of the file can bedetermined in advance from Assigned Numbers and there should be verylittle need to modify the file.

Example Services file

#

# Network services, Internet style

#

tcpmux 1/tcp # TCP port multiplexer (RFC1078)

echo 7/tcp

echo 7/udp

discard 9/tcp sink null

discard 9/udp sink null

systat 11/tcp users

daytime 13/tcp

daytime 13/udp

netstat 15/tcp

qotd 17/tcp quote

msp 18/tcp # message send protocol

msp 18/udp

chargen 19/tcp ttytst source

chargen 19/udp ttytst source

ftp-data 20/tcp # default ftp data port

ftp 21/tcp # File Transfer Protocol

ssh 22/tcp # Secure Shell

ssh 22/udp

telnet 23/tcp

...

Hosts file (/etc/hosts)

The hosts file contains information regarding some hosts on the network.The following information is presented for each host:

. internet address

. official host name

. aliases

Items are separated by any number of blanks and/or tab characters. '#'indicates the beginning of a comment; characters up to the end of the lineare not interpreted by routines which search the file.

When using the name server this file provides a backup when the nameserver is not running. It is suggested that only a few addresses be includedin this file. These include address for the local interfaces that ifconfigmay need at boot time and a few machines on the local network.

DN02143138Issue 11-2 en17/09/2007



Addresses are specified in the conventional dot notation. Host names maycontain any printable character other than a field delimiter, newline, orcomment character.

The hosts file contains no tags or criticality information. The file is commonto the whole network element. The contents of the file cannot bedetermined in advance but a stub file with a localhost entry andcommented examples can be packaged.

Example Host file

#

# Host Database

#

127.0.0.1 localhost loopback

131.228.45.176 ws20027.ntc.nokia.com ws20027

131.228.118.232 axl01it.ntc.nokia.com axl01it

3ffe:1200:3012:c020::52 L052.ntc.nokia.com L052

DNS resolver configuration file (/etc/resolv.conf)

The file contains information on DNS resolver configuration. The followinginformation is presented:

. name server

. search list for hostname lookup


Addresses are specified in the conventional dot notation. Names maycontain any printable character other than a field delimiter, newline, orcomment character.

The DNS resolver configuration file contains no tags or criticalityinformation. The file is common to the whole network element. Thecontents of the file cannot be determined in advance but a stub file with alocalhost entry and commented examples can be packaged.

Example DNS resolver file

#

# resolv.conf - DNS resolver configuration

#

# The different configuration options are:

#

# nameserver Internet address (in dot notation) of a name server that the


17/09/2007


# resolver should query.

#

# search Search list for host-name lookup (typically own domain name)

#

nameserver 131.228.118.232

nameserver 3ffe:1200:3012:c020:0:0:0:e574

search NOKIA.COM

sortlist 172.0.0.0 3ffe:1200:3012:c020:0:0:0:0/64

nocache

noround_robin

FTP server configuration file (/etc/ftp.conf)

The FTP server configuration file contains computer-specific initialisationparameters for the FTP servers.


For each unit, the options are in between unit and endunit tags.

Note

FTP server is on OMU only.

The following options can be specified:

Table 6. FTP server configuration file parameters

Option tag Parameters Description

log Log file name (optional,default is /RUNNING/

ASWDIR/FTPSERVR.XML,backup is /RUNNING/

ASWDIR/FTPSERVER.OLD)

If log file name is specified, the FTP events arerecorded into this file.

logwrap Bytes count (decimalinteger)

When this amount of bytes has been written tologfile, the log file is closed and renamed with anew extension, .OLD (for example FTPSERVR.

XML -> FTPSERVR.OLD). A new log is started,with the name specified in the log option(default is /RUNNING/ASWDIR/FTPSERVR.XML).

If the option is not specified, log wraps after500000 bytes.

Note that this option is not effective unless thelog option tag has also been specified.

DN02143138Issue 11-2 en17/09/2007



Table 6. FTP server configuration file parameters (cont.)

Option tag Parameters Description

inact Inactivity timer (decimalinteger)

The value of control connection inactivity time-out, in seconds.

If the option is not specified, inactivity timer of600 seconds is used.

checkport If specified, the parameters of received PORTcommand are checked.

Example FTP server configuration file

#ftp.conf

#

# start in OMU with logging and inactivity timer of 600 seconds

#

unit OMU

log /RUNNING/ASWDIR/FTPSERVER.XML

inact 600

logwrap 500000

endunit

#

#

#

14.2 Modifying IP configuration files

Purpose

The configuration files for the IP protocol environment rarely need to bemodified, but if necessary, use an internal or external text editor formodifications. These files cannot be modified by using MML commands.

Note

Be careful when editing the configuration files manually.

The files POCPROZZ.IMG, POCSERZZ.IMG and POCHOSZZ.IMG can beconfigured manually.


17/09/2007


Steps

1. Modify the file in an internal or external text editor

Note

Modify files in OMU RAM (for example, under directory /etc/) instead offiles in hard disk (for example, POCPROZZ.IMG). A file can bedownloaded from OMU by FTP, modifed by an external text editor anduploaded to OMU by FTP finally.

2. Propagate a configuration file within a network element

ZQRF:<file name>;

Or

ZQ6F:<file name>;

The command will also save the changed file to hard disk.

3. Modify the file in an internal or external text editor

Example Propagating hosts file

ZQRF:"/etc/hosts";

DN02143138Issue 11-2 en17/09/2007




17/09/2007


15 Connection to IP application from remotehost fails

Description

The following problems are divided according to the output you get whenyou try to contact an IP application in the network element. If you receiveno output or you receive some other output than the ones described below,you can use the checking and inquiring commands.

Symptoms

The remote host is unable to establish a connection to the IP application.

Recoveryprocedures

The following steps will help to locate/solve the problem.

In addition, there are several error messages, which may appear when theconnection to IP application from a remote host fails. If you get an errormessage, you can check the corresponding procedure directly.

. Connection refused

For more information, see Check the state of the EMT (832), Telnetor FTP service.

. No route to host

For more information, see Check the routing information.

. Connection closed by foreign host

For more information, see Investigating the reason for ConnectionClosed by Foreign Host error Message.

DN02143138Issue 11-2 en17/09/2007


Connection to IP application from remote host fails

Check IP-Layer Communication

Steps

1. Check connection

Use the ping (or traceroute) command from the remoteworkstation or node to check the connection. In the QRX commandthe unit type and unit index parameters specify the unit whichsends the PING. The host or IP address parameter specifies theunit to be pinged.

ZQRX:<unit type>,<unit index>:HOST=<host name>|IP=<IP address>:<PING | TRACE>;

Expected outcome

The output should contain lines that state the following:

----x.x.x.x PING Statistics----

1 packets transmitted, 1 packets received, 0% packet loss

Further information

If the IP-Layer Communication failed, the reason might be:. DNS Server not configured properly

For more information, see Check the configuration of yourDNS server.

. IP Routing failed

For more information, see Check the routing information andCheck the IP routing settings.

. Network interface status

For more information, see Check the connected networkinterface.

If IP-Layer communication is ok, then we need check the status ofupper-layer (TCP/UDP) communcation and IP application. Thepossible problems are as follows:. IP application is not running

For more information, see Check the state of the EMT (832),Telnet or FTP service.

. Connection refused by IP application

For more information, see Check the state of the EMT (832),Telnet or FTP service.

. Connection closed by IP application


17/09/2007


For more information, see Investigating the reason forConnection Closed by Foreign Host error Message.

Check the DNS configuration

Purpose

If an error message such as “hostname resolution failure” shows on yourworkstation, check the DNS configuration on the workstation and DNSserver.

Steps

1. Check the DNS Configuration on your workstation

Refer to the guideline provided by workstation vender for moredetails.

Expected outcome

The IP address of the RNC's hostname should be resolved correctlyon the workstation.

Check the routing information

Purpose

This is applied when getting an error message, for example, “No route tohost”.

Steps

1. Check the routing table in your workstation when errormessage comes from your workstation.

Refer to the guideline provided by workstation vender for moredetails.

Expected outcome

There should exist a route to the RNC in question.

2. If the error message is from RNC,

Then

QRS command can be used to check the routing table in RNCunit.

DN02143138Issue 11-2 en17/09/2007



ZQRS:<unit type>,<unit index>:ROU;

Check whether the concerned IP address appears in the output. Ifnot, check whether routing is configured correctly on RNC. For moreinformation, see Check the IP routing settings.

Check the IP routing settings (only in RNC)

Steps

1. If Check dynamic routes and OSPF settings defined in the networkelement are configured properly

Then

a. Interrogate OSPF parameters.

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

b. Interrogate OSPF area parameters.

ZQKN:[<unit type>,<unit index>]:[<areaidenitification>];

c. Interrogate OSPF interface parameters.

ZQKR:[<unit type>,<unit index>]:[<interfaceidentification>];

d. Interrogate virtual link parameters.

ZQKW:[<unit type>,<unit index>];

e. Interrogate redistribute parameters.

ZQKY:[<unit type>,<unit index>]:[<redistributetype>];

f. Check the OSPF settings defined in the other nodes accordingto instructions provided by the node vendor.

Else

Interrogate static routes configurations

ZQKB:[<unit type>,[<unit index>]];

For more information, see Creating and modifying static routes.


17/09/2007


Check the connected network interface

Purpose

Check the administrative and operational state of connected networkinterface. Also, check that the connected network interface has the sameIP address assigned to it as shown by the QRI command (QRS).

Steps

1. Check network interface (QRS)

ZQRS:<unit type>,<unit index>:INS,<interface name>;

Expected outcome

UNIT:<unit type>-<unit index>

ifname: flags=XXXX<UP,...,RUNNING,...> mtu xxx

inet a.b.c.d netmask 0xyyyyyyyy broadcast e.f.g.h

The administrative state should be UP and operational state RUNNING.The address a.b.c.d and netmask yyyyyyyy should be the same as shownby the QRI command. Also check that the IP address tried from the clientis correct.

Check the state of the EMT (832), Telnet or FTP service (QRS)

Purpose

This is applied when an error message “Connection refused” is received.

Steps

1. Check the state (QRS)

The error message means that there is no working IP application inthe contacted port, or the maximum number of connections is in use(FTP - 16, Telnet - 15).

In RNC, check also the state of BS-O&M.

ZQRS:<unit type>,<unit index>:ALL;

Expected outcome

There should be an application server in the LISTEN state and the numberof active connections for that application type should not exceed themaximum number of connections:

DN02143138Issue 11-2 en17/09/2007



UNIT: <unit type>-<unit index>

Active Internet connections (including servers)

Proto Recv-Q Send-Q Local Address Foreign Address (state)

tcp 0 35 x.x.x.x.telnet y.y.y.y.y.zzzz ESTABLISHED

.

.

tcp 0 0 *.832 *.* LISTEN

tcp 0 0 *.ftp *.* LISTEN

tcp 0 0 *.telnet *.* LISTEN

If you checked the state of BS-O&M in RNC, the output also contains theline

tcp 0 0 *.BS-O&M *.* LISTEN

Unexpected outcome

If the contacted IP application does not exist in the network element or if itsstate is other than LISTEN, contact Nokia Customer Service.

Investigating the reason for Connection Closed by Foreign Host errormessage

Purpose

The IP application in the network element has for some reason closed theconnection, for example, the computer unit with the IP application hasrestarted.

Steps

1. Try to re-establish the connection to be sure that there was notjust a temporary breakdown

2. Check the states of the applications (QRS)

Check the states of the applications by QRS command according toCheck the state of the EMT (832), Telnet or FTP service (QRS).

ZQRS:<unit type>,<unit index>:ALL;

Expected outcome

The state of the application server should be LISTEN.


17/09/2007


Note

If step 1 and step 2 still failed to resolve the problem, it might be due toIP layer communication failure. Refer to Check IP layer communication.

DN02143138Issue 11-2 en17/09/2007




17/09/2007


Related Topics


Instructions

OMS TCP/IP network

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

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

Descriptions


OMS TCP/IP network

Instructions


DN02143138Issue 11-2 en17/09/2007


Related Topics

IP configuration for Iu-BC interface

Instructions

Configuring IP for Iu-BC (RNC — CBC)



Instructions


Creating MMI user profiles and user IDs for remoteconnections to NetAct

Instructions



Instructions






17/09/2007


Creating OSPF configuration for O&M connectionto NetAct

Instructions



Configuring static routes for the O&M connectionto NetAct

Instructions



Configuring ESA12

Instructions

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

Configuring ESA24

Instructions


DN02143138Issue 11-2 en17/09/2007


Related Topics

Connecting to O&M backbone via ATM interfaces

Instructions





Instructions

IP connection configuration for RNC


Instructions

IP configuration for Iu-PS interface


Descriptions

IP configuration for Iu-BC interface


17/09/2007



Instructions



Instructions


Modifying IP configuration files

Descriptions


DN02143138Issue 11-2 en17/09/2007


Related Topics

Documents

IP Connection Configuration for RNC