Configuring IP Connection for RNC

Configuring IP Connection forRNC

DN02143138Issue 13-0 en30/01/2009

# Nokia Siemens Networks 1 (201)

Nokia Siemens Networks WCDMA RAN, Rel.RU10, System Library, v. 1

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 2009. All rights reserved.

2 (201) # Nokia Siemens Networks DN02143138Issue 13-0 en

30/01/2009

Configuring IP Connection for RNC

Contents

Contents 3

Summary of changes 5

1 Overview of IP connection configuration 151.1 RNC logical interfaces 151.2 RNC physical network connectivity 161.3 IP connection configuration for RNC O&M 181.4 OMS TCP/IP network 201.5 IP configuration for Iu-PS interface with GTPU 231.6 IP configuration for Iu-PS interface with NPS1(P) 261.7 IP configuration with NPGE(P) 291.8 IP configuration for Iu-BC interface 32

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

NetAct 362.3 Configuring IP stack in OMU 382.4 Creating OSPF configuration for O&M connection to NetAct 402.5 Configuring static routes for the O&M connection to NetAct 462.6 Configuring ESA12 482.7 Configuring ESA24 502.8 Configuring OMS for DCN 542.8.1 Configuring OMS for DCN 542.8.2 Checking the calendar time in OMS 552.8.3 Configuring the DHCP server in OMS 562.8.4 Configuring the DNS client in OMS 582.8.5 Configuring OMS to RNC 582.8.6 Configuring NTP services in OMS 622.8.7 Configuring OMS system identifier 632.8.8 Configuring IP addresses for OMS 642.9 Connecting to O&M backbone via Ethernet interfaces on ESA 662.10 Connecting to O&M backbone via Ethernet interfaces on NPGE(P) 682.11 Connecting to O&M backbone via ATM interfaces on OMU 702.12 Connecting to O&M backbone via ATM interfaces on NPS1(P) 71

3 Configuring IP for BTS O&M (RNC-BTS/AXC) 753.1 Configuring IP for BTS O&M (RNC-BTS/AXC) 753.2 Configuring IP for BTS O&M (RNC-BTS/AXC) via ATM 763.3 Configuring IP for BTS O&M (RNC-BTS/AXC) via Ethernet 84

4 Configuring IP for user plane 874.1 Configuring IP for Iu-PS user plane with GTPU 874.2 Configuring IP for Iu-PS user plane with NPS1(P) 1064.3 Configuring IP for user plane with NPGE(P) 112

5 Configuring signalling transport over IP for control plane 121

DN02143138Issue 13-0 en30/01/2009


Contents

5.1 Configuring signalling transport over IP over ATM for control plane 1215.2 Configuring signalling transport over IP over Ethernet for control

plane 1235.3 Configuring IP resources for Iub control plane (RNC-BTS/AXC) 129

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

7 Creating and modifying DNS configuration 137

8 Modifying IP parameters 141

9 Configuring IP interfaces 1439.1 Creating and modifying internal IP over ATM interfaces 1439.2 Creating and modifying external IP over ATM interfaces 1459.3 Configuring Ethernet interface 1509.4 Creating and modifying VLAN interfaces 1529.5 Configuring IP parameters and addresses of interfaces 154

10 Modifying OSPF configuration 159

11 Creating and modifying static routes 163

12 Creating and modifying IP QoS configuration on NPS1/NPGEunit 167

12.1 Configuring DSCP to PHB mapping profile 16712.2 Configuring PHB profile 16912.3 Configuring and interrogating IP interface QoS parameters 171

13 IP based route configuration 173

14 IP configuration files 177

15 IP connection configuration troubleshooting 18315.1 Connection to IP application from remote host fails 18315.2 NP2GE connectivity lost 18915.3 IP configuration files are corrupted 193

Related Topics 195


30/01/2009


Summary of changes

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

Changes between issues 11-4 and 13-0

The name of this document has been changed from IP ConnectionConfiguration for RNC to Configuring IP Connection for RNC.

The document was rearranged and many chapters were added anddeleted.

RNC Logical Interfaces

This is a new chapter introducing the content about 'the RNC LogicalInterfaces'.

RNC Physical Network Connectivity

This is a new chapter introducing the content about 'RNC PhysicalNetwork Connectivity'.

IP configuration for Iu-PS interface with NPS1(P)

This is a new chapter introducing the content about 'IP configuration for Iu-PS interface with NPS1(P)'.

IP configuration with NPGE(P)

This is a new chapter introducing the content about 'IP configuration withNPGE(P)'.

Configuring OMS for DCN

SSH client is not available in EM home page anymore, reference to PuTTYinternet page has been added in this chapter.

DN02143138Issue 13-0 en30/01/2009


Summary of changes

This is a new chapter introducing the content about 'IP configuration withNPGE(P)'.

Configuring the DHCP server in OMS

Information that the DHCP server is not mandatory has been added.

Configuring OMS to RNC

New parameters and instructions entries in step 2 have been added.

Current OMU IP checking instruction have been moved to section Beforeyou start.

Configuring NTP services in OMS

ATip about reconfiguring NTP by executing zmodifyNetworkSettings scripthas been added in section Purpose.

Connecting to O&M backbone via Ethernet interfaces on NPGE(P)

This is a new chapter introducing the content about 'connecting to O&Mbackbone via Ethernet interfaces on NPGE(P)'.

Connecting to O&M backbone via ATM interfaces on NPS1(P)

This is a new chapter introducing the content about 'connecting to O&Mbackbone via ATM interfaces on NPS1(P)'.

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

This is a new chapter introducing the content about 'configuring IP for BTSO&M (RNC-BTS/AXC) via ATM'.

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

This is a new chapter introducing the content about 'configuring IP for BTSO&M (RNC-BTS/AXC) via Ethernet'.

Configuring IP for Iu-PS User Plane with GTPU

The parameter of QM MML command was updated.

Configuring IP for Iu-PS User Plane with NPS1(P)


30/01/2009


This is a new chapter introducing the content about 'configuring IP for Iu-PS with NPS1(P)'.

Configuring IP for User Plane with NPGE(P)

This is a new chapter introducing the content about 'configuring IP for UserPlane with NPGE(P)'.

Configuring Signalling Transport over IP over ATM for Control Plane

The parameter of QM MML command was updated.

Configuring Signalling Transport over IP over Ethernet for Control Plane

This is a new chapter introducing the content about 'configuring SignallingTransport over IP over Ethernet'.

Configuring IP resources for Iub Control Plane (RNC-BTS/AXC)

This is a new chapter introducing the content about 'configuring IPresources for Iub Control Plane'.

Creating and modifying internal IP over ATM interfaces

This is a new chapter introducing the content about 'creating andmodifying internal IP over ATM interfaces'.

Creating and modifying external IP over ATM interfaces

This is a new chapter introducing the content about 'creating andmodifying external IP over ATM interfaces'.

Configuring Ethernet interfaces

This is a new chapter introducing the content about 'configuring Ethernetinterfaces'.

Creating and modifying VLAN interfaces

This is a new chapter introducing the content about 'creating andmodifying external IP over ATM interfaces'.

Configuring DSCP to PHB mapping profile

This is a new chapter introducing the content about 'creating andmodifying VLAN interfaces'.

DN02143138Issue 13-0 en30/01/2009


Summary of changes

Configuring PHB profile

This is a new chapter introducing the content about 'configuring PHBprofile'.

Configuring and interrogating IP interface QoS parameters

This is a new chapter introducing the content about 'configuring andinterrogating IP interface QoS parameters'.

IP based route configration

This is a new chapter introducing the content about 'configuring IP basedroute'.

NP2GE connectivity lost

This is a new chapter introducing how to do while NP2GE connectivitylosts.


Configuring IP stack in OMU

A note "To make sure that the primary domain name server (DNS) serverworks, do not use the operation and maintenance server (OMS) IPaddress as a primary DNS IP address." was added.

Creating and modifying DNS configuration

A note "To make sure that the primary domain name server (DNS) serverworks, do not use the operation and maintenance server (OMS) IPaddress as a primary DNS IP address." was added.


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

Added the introduction of GTPU selection principle and the relatedexamples.

Added one example "IP configuration for Iu-PS with GTPUs connected todifferent SGSNs".




30/01/2009


"QMF" MML command was updated.


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

. 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

DN02143138Issue 13-0 en30/01/2009


Summary of changes

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


. 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

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


30/01/2009


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.


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

DN02143138Issue 13-0 en30/01/2009


Summary of changes

. 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

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.


30/01/2009


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 13-0 en30/01/2009


Summary of changes


30/01/2009


1 Overview of IP connection configuration

1.1 RNC logical interfaces

3GPP has defined a set of logical interfaces for the RNC NE as depicted inthe figure Logical interfaces of the RNC NE as defined by 3GPP.

Figure 1. Logical interfaces of the RNC NE as defined by 3GPP

The Iub interface connects an RNC with its base stations and Iur is aninter-RNC connection. Iu-CS and Iu-PS connect RNC with the voice andpacket data related parts of the core network, respectively. Iu-PC providesRNC connectivity to the positioning center while Iu-BC is the connection tothe broadcast center. Finally, RNC provides means for O&M (for example,NetAct) connection.

lub

O&M

lu-PC

lu-CS

lu-PS

lu-BC

NodeBs

SAS

RNC

CoreNetwork

D-RNCs

lur

DN02143138Issue 13-0 en30/01/2009


Overview of IP connection configuration

Iub & Iur interfaces

The RNC base station interface Iub was originally designed to be based onATM technology. With 3GPP Release 5, IP transport option for Iub wasintroduced (native IP support). As an intermediate step, an externalsolution was provided with “Hybrid BTS Backhaul” pseudo wire emulation.

Related to Iur (inter-RNC interface), the same history applies.

Iu-PS interface

Packet data on the Iu-PS interface is based on IP over ATM since Release99 of 3GPP UTRAN. SGSNs can be connected either via STM-1 directlyor by converting the IP over ATM traffic via an ATM-capable switch (foruser plane) and via a signalling converter for control plane traffic. WithRelease 4, 3GPP introduced native IP on Iu-PS.

Iu-CS interface

Circuit switched data between RNC and MGW can be transmitted viaATM, or since Release 5 also using native IP.

Iu-BC interface

The RNC interface to CBC is based on IP over ATM. SABP messages aretransmitted via TCP/IP and can be routed via MGW/SGSN. The maximumnumber of Iu-BC instances is 4, usually one CBC per operator is used.

O&M interface

Operation and maintenance communication between RNC and NetAct isbased on TCP/IP via LAN or IP over ATM alternatively.

1.2 RNC physical network connectivity

The various logical interfaces are provided by different units in the RNCand thus mapped to different physical network connections.

NP2GE

This interface unit is introduced with RN4.0 RNC and is specially designedfor IP transport in packet environment. It provides Gigabit Ethernetconnectivity for the following logical RNC interfaces:


30/01/2009


. Iub

. Iur

. Iu-PS

. Iu-CS

NP2GE provides the following physical network interfaces:

. 2x 1000 Base-LX. Optical transmission. Long-haul (up to 5000m with SMF)

. 2x 1000 Base-T. Electrical transmission. Cabling at least Cat. 5

Selection of optical/electrical interface is fully automatic and based on portactivity sensing and priority (if both ports show activity, optical is preferred).Both interfaces will operate in 1Gbit Ethernet mode only.

It is possible to duplicate the NP2GE unit in an RNC towards MGW toprovide redundancy.

RNC2600 can be equipped with up to 14 NP2GE units, creating a total of28 Gbit Ethernet ports configurable for use with Iu-CS, Iu-PS, Iub, and Iur.

Finally, NPGE provides two FE ports on the backplane, which areconfigured for use towards DCN (O&M connectivity).

NP8S1

NP8S1 is the Network Processor Unit STM-1, which is used for providingATM connectivity for the RNC, but nonetheless it also provides someEthernet (FE) ports. Altogether, NP8S1 can facilitate Iu-BC, Iu-PC, and Iu-PS in IP over ATM mode.

For user plane transport, NP8S1 is mainly used to replace original GTPU +NIS solution for Iu-PS user plane. For DCN connection, NP8S1 can beconnected to BTS in ATM based Iub case and FE ports can be used toforward the BTS O&M traffic to OMU/NetAct.

DN02143138Issue 13-0 en30/01/2009



ESA24

ESA actually is an Ethernet switch, providing backbone connectivitytowards NetAct for O&M and assisted GPS features (Iu-PC) towards SAS.It features 24x 10/100Base-T Ethernet ports, two of which are located onthe front plane and serve as uplink. The remaining 22 ports are connectedto other subsystems in the RNC via backplane connections (typicallyOMU, OMS, and NP2GE/NP8S1).

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

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


30/01/2009


Figure 2. 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 NokiaSiemens Networks WCDMA RAN System Information Set in NOLS.

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

DN02143138Issue 13-0 en30/01/2009



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, sub-network 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.4 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.


30/01/2009


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

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

DN02143138Issue 13-0 en30/01/2009



Figure 4. Ethernet based connectivity between OMS and NetAct

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


30/01/2009


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.5 IP configuration for Iu-PS interface with GTPU

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 Siemens Networks WCDMA RAN System Information Set inNOLS.

Summary

In Iu-PS interface, the traffic can go through NIS1 and GTPU units. InGTPU units, all users and packets are treated equally regardless of theservice, Quality of Service (QoS) requirement, and packet size. However,you can dedicate two or more GTPUs to serve only real-time IP trafficbetween the RNC and the SGSN. Dedication is done by configuring IPover ATM VCCs so that their usage is IP over ATM real-time user data(IPOART). With a GTPU dedicated to real-time IP traffic, there is aseparate real-time optimised Iu-PS PVC (CBR or rt-VBR) for PacketSwitched Radio Access Bearers (RABs) between the GTPU and theSGSN and a separate internal real-time optimised VCC between the

DN02143138Issue 13-0 en30/01/2009



GTPU and the DMCU. Another solution is to use layer-two segregationfunctionality of GTPU. By this solution, you can use two VCCs under oneIPoA interface of GTPU. One of these two VCCs is dedicated to real-timeIP traffic.

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 the commands of the Q8 MML command group. For more detailedinstructions, refer to Configuring DSCP to PHB mapping profile,Configuring PHB profile, and Configuring and interrogating IP interfaceQoS parameters.

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 6. All GTPUs used for real-time and non-real time traffic

Non-dedicated VCCs

GTPU

GTPU

GTPU

GTPU

GTPU

MXU SGSNSFU


30/01/2009


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

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

DN02143138Issue 13-0 en30/01/2009



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



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


2. Plan routing

You can use either static routes or OSPF for routing, see ActivatingOSPF for redundancy with GTPU. If you use only static routes, seethe examples in Configuring IP for Iu-PS User Plane with GTPU forinstructions on how to create redundancy for the Iu-PS interface.

1.6 IP configuration for Iu-PS interface with NPS1(P)

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.


30/01/2009


Before you start

For more information on the Iu-PS interface, see Iu interface specificationin the Nokia Siemens Networks WCDMA RAN System Information Set inNOLS.

Summary

In Iu-PS interface, the traffic can go through NPS1(P) units.

It is possible to configure QoS DiffServ traffic classification to NPS1(P)units. You can prioritise the throughput real time (rt) traffic rather than non-real time (nrt) traffic in the NPS1(P) units. Such configuration is done withthe commands of the Q8 MML command group. For more detailedinstructions, refer to Configuring DSCP to PHB mapping profile,Configuring PHB profile, and Configuring and interrogating IP interfaceQoS parameters.

It is possible to isolate different IP domains from each other by configuringone IP based route for each SGSN and attaching IP based route to the IPaddresses.

The following figures show the different configurations of IP based route.

Figure 9. One IP based route with single NPS1

One IP based route (Iu-PS #1) is attached to 10.1.1.1.

NPS1-0 IFAE-0 GPLC-0

RNC SGSN

10.1.1.1>10.1.1.2 10.1.1.2IP based route

Iu-PS #1

DN02143138Issue 13-0 en30/01/2009



Figure 10. One IP based route across multiple NPS1s

One IP based route (Iu-PS #1) is attached to 10.1.1.1 and 10.1.2.1.

Two IP addresses added to different NPS1s will be selected in a round-robin mode.

Figure 11. Multiple IP based routes (for example, SGSNs) with single NPS1

One IP based route (Iu-PS #1) is configured for SGSN1 and is attached to10.1.1.1.

Another IP based route (Iu-PS #2) is configured for SGSN2 and isattached to 10.1.2.1.

GPLC-0

RNC SGSN

10.2.1.1

IP based routeIu-PS #1

NPS1-1 IFAE-0

GPLC-1

10.1.2.1>10.2.1.2 10.2.1.2

NPS1-0 IFAE-0 10.1.1.1>10.2.1.1

RNC SGSN1

IP base routeIu-PS #1



IFAE-0

IFAE-1

10.1.1.1>10.2.1.1

10.1.2.1>10.2.1.2

10.2.1.1

10.2.1.2

GPLC-0

GPLC-0

NPS1-0

SGSN2


30/01/2009


For more detailed instructions on how to configure IP based route, seeConfiguring IP for Iu-PS user plane with NPS1(P) and IP based routeconfiguration.

Steps





2. Plan routing

You can use either static routes or OSPF for routing, see ActivatingOSPF for redundancy with NPS1(P). If you use only static routes,see the examples in Configuring IP for Iu-PS user plane with NPS1(P) for instructions on how to create redundancy for the Iu-PSinterface.

1.7 IP configuration with NPGE(P)

Purpose

NPGE(P) can be used for Iub, Iur, Iu-CS, and Iu-PS interfaces. The IPconnection is used for user plane and control plane traffic.

Before you start

For more information on the logical interface, see Nokia SiemensNetworks WCDMA RAN System Information Set in NOLS.

Summary

User plane and control plane can go through NPGE(P) units. There aretwo 1 Gbit Ethernet interfaces in one unit. They can work in load sharing,redundancy or standalone mode.

DN02143138Issue 13-0 en30/01/2009



It is possible to configure QoS DiffServ traffic classification to NPS1(P)units. You can prioritize the throughput real time (rt) traffic rather than non-real time (nrt) traffic in the NPS1(P) units. Such configuration is done withthe commands of the Q8 MML command group. For more detailedinstructions, refer to Configuring DSCP to PHB mapping profile,Configuring PHB profile, and Configuring and interrogating IP interfaceQoS parameters.

It is possible to isolate different IP domains from each other by configuringone IP based route for each logical interface and attaching IP based routeto the IP addresses.

The following figures show the different configurations of IP based route.

Figure 12. One IP based route with single pair NPGE(P)

One IP based route (Iub #1) is attached to 10.1.1.1.

RNC BTS

IP based routeIub #1

NPGEP-0(WO) IFGE0 10.1.1.1

10.1.1.2

NPGEP-1(SP) IFGE0 10.1.1.1


30/01/2009


Figure 13. One IP based route across multiple NPGEs

One IP based route (Iu-CS #1) is attached to 10.1.1.1 and 10.1.1.2.

NPGEs will work in load sharing mode. Two IP addresses added todifferent NPGEs will be selected in a round-robin mode.

Figure 14. Multiple IP based routes (for example, neighbor RNCs) with singleNPGE

One IP based route (Iur #1) is configured for RNC1 and is attached to10.1.1.1.

RNC MGW

IP based routeIu-CS #1

NPGE-0 IFGE0

NPGE-1 IFGE0

NPGE-0

NPGE-1

10.1.1.1

10.1.1.2

10.2.1.1

10.2.1.2

RNC RNC1

IP based routeIur #2

IP based routeIur #1

NPGE-0

NPGE-0

10.1.1.1IFGE0

10.1.2.1IFGE1

10.2.1.1

10.2.2.1

NPGE-0

RNC2

DN02143138Issue 13-0 en30/01/2009



Another IP based route (Iur #2) is configured for RNC2 and is attached to10.1.2.1.

For more detailed instructions on how to configure IP based route, seeConfiguring IP for Iu-PS user plane with NPGE(P) and IP based routeconfiguration.

Steps





2. Plan routing

You can use either static routes or OSPF for routing, see ActivatingOSPF for redundancy with NPGE(P). If you use only static routes,see the examples in Configuring IP for Iu-PS user plane with NPGE(P) for instructions on how to the create the configuration for the IPbased logical interface with NPGE(P).

1.8 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 Siemens Networks WCDMA RAN SystemInformation Set in NOLS.

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


30/01/2009


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.

There are four kinds of methods to connect to O&M backbone:

. Connecting to O&M backbone via Ethernet interface on ESA

. Connecting to O&M backbone via Ethernet interface on NPGE(P)

. Connecting to O&M backbone via ATM interface on OMU

. Connecting to O&M backbone via ATM interface on NPS1(P)

Note

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

DN02143138Issue 13-0 en30/01/2009



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. 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 15. Preconfigured settings for O&M network

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


30/01/2009


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

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 twoalternatives to connect the RNC to NetAct:

DN02143138Issue 13-0 en30/01/2009



. Configuring the O&M backbone via Ethernet interface onESA24 or NPGE(P)

Refer to instructions in Connecting to O&M backbone viaEthernet interfaces on ESA.

Refer to instructions in Connecting to O&M backbone viaEthernet interfaces on NPGE(P).

. Configuring the O&M backbone via ATM interfaces on OMU orNPS1(P)

Refer to instructions in Connecting to O&M backbone via ATMinterfaces on OMU.

Refer to instructions in Connecting to O&M backbone via ATMinterfaces on NPS1(P).

The recommended way of connecting RNC to NetAct is via Etherneton ESA. The connection via ATM or NPGE(P) should only be usedas a backup. The O&M connections can be configured with both twoways.

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


30/01/2009


telnet <IP address of OMU>

2. Create new MMI user profiles

Create the user profiles for NUPADM and NEMUAD. Refer toCreating and modifying an MMI user profile in Managing InformationSecurity document for details.

3. Create new MMI user IDs

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

Example Creating MMI user profiles and user IDs in the RNC

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

1. Create the user profiles.

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

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

2. Create the user IDs.

ZIAH:NUPADM:NUPADM;

ZIAH:NEMUAD:NEMUAD;

When creating a new user ID, the system prompts you for apassword. The password created here is used for communicationbetween the 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.

DN02143138Issue 13-0 en30/01/2009



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.

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

Note

To make sure that the primary domain name server (DNS) serverworks, do not use the operation and maintenance server (OMS) IPaddress as a primary DNS IP address.

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:


30/01/2009


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

3. Add a new logical IP address

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

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

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,

ZQRG: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 13-0 en30/01/2009



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;

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.


30/01/2009


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

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.

DN02143138Issue 13-0 en30/01/2009



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.

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


30/01/2009


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.

Figure 16. Example of OSPF configuration for RNC

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

DN02143138Issue 13-0 en30/01/2009



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

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

ZQKB:OMU;

The following output is displayed:

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:


30/01/2009


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

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.

DN02143138Issue 13-0 en30/01/2009



ZQKU:OMU,0:ST=;

ZQKU:OMU,1:ST=;

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.


30/01/2009


Note

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

ZQKC:<unit type>,<unit index>::<gateway IP address>,[<local IP address>]:[<route type>]:[<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.

DN02143138Issue 13-0 en30/01/2009



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

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.


30/01/2009


General Configuration

MAC address 00 A0 12 0B 02 74

1. Agent IP Address : 192.168.001.009

2. Agent Netmask : 255.255.255.240

3. Default Gateway : 192.168.001.001

4. Supervisor/Terminal Password :

5. System Name :

6. Advanced Features

9. Main Menu

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

Expected outcome

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

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

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:

DN02143138Issue 13-0 en30/01/2009



Default Gateway : 192.168.1.1

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

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

Default Gateway : 10.1.1.2

The new value is shown in the General Configuration menu:

General Configuration

MAC address 00 A0 12 0B 02 74

1. Agent IP Address : 192.168.001.009

2. Agent Netmask : 255.255.255.240

3. Default Gateway : 10.001.001.002

4. Supervisor/Terminal Password :

5. System Name :

6. Advanced Features

9. Main Menu

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


30/01/2009


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.

DN02143138Issue 13-0 en30/01/2009



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


30/01/2009


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.

DN02143138Issue 13-0 en30/01/2009



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 network settings ofOMS are configured 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 PuTTY web page byentering the following adress in your Internet browser:

http://www.chiark.greenend.org.uk/~sgtatham/putty/.

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 (defined during the OMSinstallation procedure or default for factory installed OMS isanonymous). The root user is the only username who has thenecessary rights to execute the following configuring steps.

2. Change the time zone settings


30/01/2009


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. Configure users and passwords for OMS

For configuring users and passwords, refer to the instructions inConfiguring users and passwords for OMS

5. Configure OMS to RNC

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

6. Configure the OMS system identifier

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

7. Define the IP address for OMS

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

8. Configure the DHCP server

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

2.8.2 Checking the calendar time in OMS

Purpose

To make sure that the calendar time in OMS matches local date and time.

DN02143138Issue 13-0 en30/01/2009



Note

Pre-installed OMS has its hardware clock set to UTC time and afterchanging time zone, time should be correct. If time is offset only by fewminutes, or OMS time is in the past, time difference is acceptable.

Moving time to backward will cause that OMS LDAP replication is notworking.

After performing Configuring IP addresses for OMS part, OMSconnects to the NTP and resynchronises time. Since system hastimestamps both in files and database entries, it refuses to overwritenewer settings with older ones. Therefore if after changing time zoneOMS time is in the future, system has newer timestamps thancommissioning time, and setting modifications will fail.

Steps

1. Check date and time settings

Enter the following command:

date

Check that the printout matches your local date and time.

If time is correct or is in the past, continue integration.

If time is in the future, reinstall OMS according to the installationinstructions in Installing and commissioning RNC.

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.


30/01/2009


NED?action=retrieve&library=ru_rel_10_v1_2009_01_27&identifier=dn70558635&edition=111&language=en&coverage=global&encoding=pdf_online_a4&component=data&item=data

Tip

DHCP server is not mandatory, server provides IP adresses for userswho can only use dynamic IP settings in their computers.

Steps

1. Modifying DHCP address pool

a. Open /opt/nokiasiemens/SS_OMSINST/dhcpd/dhcpd.confin a text editor. The file contains an example configuration,which you have to modify to match the current network andwanted address 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/nokiasiemens/SS_OMSINST/dhcpd/zstart_dhcpd.sh

/opt/nokiasiemens/SS_OMSINST/dhcpd/zstart_dhcpd.sh

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

To deactivate DHCP, execute the following command:

/opt/nokiasiemens/SS_OMSINST/dhcpd/zstop_dhcpd.sh

DN02143138Issue 13-0 en30/01/2009



2.8.4 Configuring the DNS client in OMS

Before you start

The DNS client configuration is distributed into the OMS, and it is presentafter system restart. Restarting the ClusterDNS service activates the newconfiguration.

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:

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

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

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

2.8.5 Configuring OMS to RNC

Purpose

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


30/01/2009


. 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, SSHand FTP connections can use.

Before you start

The following user accounts have to be created to OMS:

. OMS FTP user (this is omsFtpUser)

. NWI3 user (defined during step 3 in Configuring users andpasswords for OMS)

Current OMU IP can be checked by entering the command zomuip andpressing ENTER.

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 in a SSH client window.

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. When zmodifyOMUSettings is started, it asks for newvalues.

DN02143138Issue 13-0 en30/01/2009



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. For more information, see Creating MMI userprofiles and user IDs for remote connections to NetAct.

OMU IP address Enter OMU IP address as configured inConfiguring IP stack in OMU, for example10.1.1.2 and press ENTER

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

For example:

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

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

For example:

. OMU FTP UserName [STRING] currentvalue: SYSTEM

. OMU FTP UserName [STRING] newvalue: 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.

For example:

. OMU Telnet UserName [STRING] currentvalue: SYSTEM

. OMU Telnet UserName [STRING] newvalue: NEMUAD


30/01/2009


OMU Telnet PasswordEnter OMU Telnet Password and pressENTER.

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

OMU Hostname Enter OMU Hostname, for example omu, andpress ENTER.

OMU DomainnameEnter OMU Domainame, for example rnc<rncid>.ran.netact.<operator>.<com>, and pressENTER.

OMS IP Address Enter OMS IP address, for example 10.1.1.5,and press ENTER.

OMS DomainnameEnter OMS Domainname, for example rnc<rncid>.ran.netact.<operator>.<com>, and pressENTER.

OMS Hostname Enter OMS Hostname, for example oms, andpress ENTER.

Changes to be updatedCheck the information which will be updated.

You set following settings:

OMU IP = 10.1.1.2

EMT Username = NEMUAD

EMT Password = ******

FTP Username = NEMUAD

FTP Password = ******

Telnet Username = NEMUAD

Telnet Password = ******

OMU Hostname = omu

OMU Domainname = rnc1.ran.netact.done.fi

OMS IP Address = 10.1.1.5

OMS Hostname = oms

OMS Domainname = rnc1.ran.netact.done.fi

Are these parameters correct (yes/no)?

Answer: yes

DN02143138Issue 13-0 en30/01/2009



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

OMS NTP can be configured to external NTP. Restarting ClusterNTPservice activates the new configuration.

Tip

Note that NTP can also be reconfigured by executingzmodifyNetworkSettings script. However usingzmodifyNetworkSettings requires also the following data beside theNTP IP address: OMS IP address, subnet mask, gateway address andDNS IP address. Also executing zmodifyNetworkSettings resetssystem in order to apply new settings.

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

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


30/01/2009


4. Distribute the configured file

Run the following command for distributing the configured file:

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.

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:

DN02143138Issue 13-0 en30/01/2009



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.

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 OMS. New configurations arepresent after system restart.

Before you start

Gather the following information:

. OMS IP address

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


30/01/2009


. Gateway (usually it is OMU address)

. NTP IP address

. DNS IP address

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

Steps

1. Enter zmodifyNetworkSettings

Executing the zmodifyNetworkSettings starts query for newnetwork settings, confirm changes. Change values to the OMS andrestart to take new settings in 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

DN02143138Issue 13-0 en30/01/2009



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.

2.9 Connecting to O&M backbone via Ethernetinterfaces on ESA

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.


30/01/2009


Figure 17. Ethernet connection for O&M traffic via ESA

O&M connections from the RNC to the O&M backbone can also becreated via other virtual connections, for the details refer to chapterConfiguring IP for O&M backbone (RNC-NetAct). However, thisconnection via ESA is the preferred way.

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.

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

O&MEthernetconnection

NetAct RNC

Computer withElement Manager

OMS

OMUESA24

DN02143138Issue 13-0 en30/01/2009



2.10 Connecting to O&M backbone via Ethernetinterfaces on NPGE(P)

Purpose

If you can not connect to O&M backbone via ESA, for instance, the ESAunit is not connected to the site router directly, another method ofconnection via Ethernet interface is provided.

This procedure describes how to connect RNC to the external network forO&M connections using an external router connected to the NPGE(P).

Figure 18. Ethernet connection for O&M traffic via interface on NPGE(P) viaESA


NetAct

RNC


NPGE

OMU

ESA24

OMS


30/01/2009


Figure 19. Ethernet connection for O&M traffic via interface on NPGE(P) viainternal IPoA

Note

The internal IPoA is used to connect OMU and NPGE(P) only whenthere is no ESA24, or NPGE(P) and ESA12 do not match.

Before you start

Because the IP addresses for OMU, 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.

Steps

1. Connect the network element physically to the external routervia NPGE(P)

Connect the router to the NPGE(P).

2. Connect OMU and NPGE(P)


NetAct

RNC


ESA12

OMS

Internal IPoAconnection

OMU

NPGE

DN02143138Issue 13-0 en30/01/2009



There are two alternatives to connect OMU and NPGE(P). by connecting NPGE(P) and OMU via ESA. by connecting NPGE(P) and OMU via internal IPoA

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

2.11 Connecting to O&M backbone via ATM interfaceson OMU

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 the O&M backbone via Ethernet interfaces onESA). The IP over ATM connection should only be used as a backup.

Note

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

Figure 20. Virtual ATM connection for O&M traffic via ATM interface on OMU

O&M

NetAct

RNC

IP over ATMvirtual

connection

ExternalIPoA

connection

NIP1/NIS1/NPS1

OMU


30/01/2009


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 internal IP over ATMinterfaces and Creating and modifying external IP over ATMinterfaces.

2. Assign IP addresses to the interfaces on OMU

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

Note

The destination IP address parameter is always mandatory.

For IPv4:

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

2.12 Connecting to O&M backbone via ATM interfaceson NPS1(P)

Purpose

For O&M connections towards NetAct, IP over ATM interfaces for NPS1(P)are 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 on ESA). The IPover ATM connection should only be used as a backup.

DN02143138Issue 13-0 en30/01/2009



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.

Figure 21. Virtual ATM connection for O&M traffic via ATM interface on NPS1(P)

Before you start

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

IFFE0 interface's MTU is permanent 1500 and NPS1 unit can not supportfragmentation. To support the topology described in the above figure, youshould make sure that the MTU of IPoA interface between NPS1 and BTSis 1500.

Steps

1. Make sure that the NPS1(P) and the OMU are connected via theEthernet on ESA24

2. Configure IP over ATM interface to the functional unit

Refer to the instructions in Creating and modifying internal IP overATM interfaces and Creating and modifying external IP over ATMinterfaces.

O&M

NetAct

RNC

NPS1

OMU

ESA24IP over ATM

virtualconnection


30/01/2009


3. Assign IP addresses to the interfaces on NPS1(P) and OMU

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

Note

The destination IP address parameter is always mandatory.

For IPv4:

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

DN02143138Issue 13-0 en30/01/2009




30/01/2009


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

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

Purpose

The purpose of this chapter is to configure IP for BTS O&M (RNC-BTS/AXC and RNC-FlexiBTS). You can configure the connection towards BTSvia Ethernet or ATM on different unit.

There are two alternatives to connect the RNC to BTS for O&M traffic.

. Configuring the connection to BTS by OMU or NPS1(P)

Refer to instructions in chapter Configuring IP for BTS O&M (RNC-BTS/AXC) via ATM.

. Configuring the connection to BTS Via Ethernet interface on NPGE(P)

Refer to instructions in chapter Configuring IP for BTS O&M (RNC-BTSAXC) via Ethernet.

Steps

1. Configure the connection to BTS for O&M traffic

There are two alternatives to connect the RNC to BTS.. By configuring the connection to BTS Via Ethernet interface on

NPGE(P)

Refer to instructions in Configuring IP for BTS O&M (RNC-BTS) via Ethernet

. By configuring the connection to BTS by OMU or NPS1(P)

DN02143138Issue 13-0 en30/01/2009



Refer to instructions in Configuring IP for BTS O&M (RNC-BTSAXC) via ATM

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

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 Siemens NetworksWCDMA RAN System Information Set in NOLS.

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.


30/01/2009


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, seeConfiguring IP parameters and addresses of interfaces in IP ConnectionConfiguration for RNC.

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 can configure O&M network towards BTS via the ATM interfaces onOMU or NPS1(P).

Figure 22. Configuring O&M network towards BTS via the ATM interface onOMU

In the above figure, the external IPoA interface is configured in OMU.NPS1 is used in the same way as NIPI and NIS1.

O&M

BTS

RNC


ESA24/ESA12

OMU

NIPI/NIS1/NPS1IP over ATM

virtualconnection

OMS

DN02143138Issue 13-0 en30/01/2009



Figure 23. Configuring O&M network towards BTS via the ATM interface onNPS1(P)

The above configuration supports to connect to BTS via the two functionunits (OMU and NPS1(P)) together.

IFFE0 interface's MTU is permanent 1500 and NPS1 unit can not supportfragmentation. To support the topology like above figure, you should makesure that the MTU of IPoA interface between NPS1 and BTS is 1500.

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 or NPS1(P).

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

You also should have ATM plans available for the tree or star model 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

O&M

IP over ATMvirtual

connection

RNC


OMU

NPS1 ESA24

BTSOMS


30/01/2009


2. Create an IP over ATM interface towards BTS in OMU or NPS1(P)

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 internal IP over ATMinterfaces and Creating and modifying external IP over ATMinterfaces.

3. If you are using static routing

Then

Create static route for BTS O&M

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

ZQKC:<unit type>,<unit index>:[<destination IPaddress>],[<netmask length>]:<gateway IP address>,[<local IP address>]:[<route type>]:[<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.

DN02143138Issue 13-0 en30/01/2009




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

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

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

Further information

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

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


30/01/2009


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

DN02143138Issue 13-0 en30/01/2009



Note

Unnumbered IP address should be the same as IP address of ELinterface. If you do not 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;


30/01/2009


...

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;

DN02143138Issue 13-0 en30/01/2009



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

Purpose

The purpose of this procedure is to configure IP for BTS O&M (RNC-BTS/AXC and RNC-FlexiBTS) via Ethernet.

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.

Figure 25. Configuring IP for BTS O&M (RNC-BTS) via Ethernet, case A


RNC


OMU

NPGE ESA24

BTSOMS


30/01/2009


Figure 26. Configuring IP for BTS O&M (RNC-BTS) via Ethernet, case B

Note

The second connection in case B is used only when there is no ESA24for the connection between OMU and NPGE(P), or NPGE(P) andESA12 do not match.

Steps


2. Create an IP over Ethernet interface towards BTS in NPGE(P)

3. If you are using static routing

Then

Create static route for BTS O&M

For O&M connections towards BTS, normally you can set the siterouter as the default gateway.

O&M

Ethernetconnection

RNC

OMU

NPGE ESA12

BTSOMS


Internal IPoAconnection

DN02143138Issue 13-0 en30/01/2009




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 sub-netted network may be used as the area ID. Itis recommended that all OSPF areas except the backbone areconfigured as totally stubby areas.


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



30/01/2009


4 Configuring IP for user plane

4.1 Configuring IP for Iu-PS user plane with GTPU

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

You should know the GTP-U endpoint address in SGSN. The address willbe in RAB assignment. The GTPU selection is based on the followingmechanism:

1. Try to find the GTPU which can fulfill the following two requirementsat the same time:

a. One of this GTPU's IPoA interfaces has the same destinationIP address as the IP address received in RAB assignment.

b. At least one of this GTPU’s IPoA interfaces is in good workingstate.

If more than one GTPU can fulfill these requirements, the GTPU willbe selected round-robin among these GTPUs.

2. If no GTPU can fulfill the requirements in step 1, try to find the GTPUwhich can fulfill the following requirement:

a. At least one of this GTPU’s IPoA interfaces is in good workingstate.

If more than one GTPU can fulfill this requirement, the GTPU will beselected round-robin among these GTPUs.

3. If no GTPU can be selected in step 2, the GTPU selection is failed.

DN02143138Issue 13-0 en30/01/2009


Configuring IP for user plane

Note

In addition to the MML based configuration the Iu-PS interface ATM andIP basic resources can be configured via the IP and ATM plan interfacefrom the NetAct. The ATM plan interface contains the basic support forATM interface, VPLtp and VCLtp creation while the IP plan supportcovers the basic support for the MML commands QMF, QRN and QKC.The IP plan support does not cover the OSPF configuration or IP QoSconfiguration.

For more information on the IP plan interface, see IP plan interface.

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 VCC perGTPU) according to instructions in Creating and modifying internalIP over ATM interfaces and Creating and modifying external 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.

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 internal IP over ATM interfaces and Creatingand modifying external IP over ATM interfaces.

3. Configure the default static routes


30/01/2009


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.

4. Create other static routes, if needed

For IPv4:


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.

DN02143138Issue 13-0 en30/01/2009



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 Configuring DSCP toPHB mapping profile, Configuring PHB profile, and Configuring andinterrogating IP interface QoS parameters.

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. Two GTP-Uendpoint addresses are used in SGSN:

. 10.2.0.1 in GPLC-1

. 10.3.0.1 in GPLC-2


30/01/2009


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



2. Create IP over ATM interfaces to all GTPUs.

10.1.1.10AA1GTPU-0

10.1.1.11AA1GTPU-1

10.1.2.12AA2GTPU-2

10.1.2.13AA2GTPU-3

10.1.1.1

10.1.2.1

10.2.0.1

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

DN02143138Issue 13-0 en30/01/2009



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:AA2:10.1.2.12,P:32:10.1.2.1;

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

4. Create static routes for GTPUs.

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

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




Example IP Configuration for Iu-PS when a GTPU can serve only oneSGSN endpoint address

In this example, two GTP-U endpoint addresses are used in SGSN:

. 10.2.0.1 in GPLC-1

. 10.3.0.1 in GPLC-2

GTPU-0 and GTPU-1 are connected to GPLC-1, while GTPU-2 andGTPU-3 are connected to GPLC-2. There is no route or IP forwardingbetween GPLC-1 and GPLC-2, that means GTPU-0 and GTPU-1 canserve only 10.2.0.1; meanwhile, GTPU-2 and GTPU-3 can serve only10.3.0.1.

To archive that kind of dedication, configure IP address of AA interface inGTPU-0 and GTPU-1 to 10.2.0.1; meanwhile, configure that of GTPU-2and GTPU-3 to 10.3.0.1.


30/01/2009


When RNC receives RAB assignment with IP address 10.2.0.1, GTPU-0and GTPU-1 will be selected in a round-robin mode. Similarly, when RABassignment with IP address 10.3.0.1 is received, GTPU-2 and GTPU-3 willbe selected in a round-robin mode.

Figure 28. GTPUs connected to only one GPLC

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



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


AA1GTPU-0

10.1.1.11AA1GTPU-1

10.1.2.12AA2GTPU-2

AA2GTPU-3

10.1.1.1

10.1.2.1

10.2.0.1

10.3.0.1

GPLC1

GPLC2

RNC SGSN

VPI=0, VCI=40

No forwardingbetween GPLCs

STM-1 line #2

VPI=0, VCI=42

VPI=0, VCI=43

= GPLC1

= GPLC2

VPI=0, VCI=41

STM-1 line #1

10.1.1.10

10.1.2.13

DN02143138Issue 13-0 en30/01/2009










3. Assign IP addresses to the network interfaces

a. Configure GTPU-0 and GTPU-1 to serve SGSN address10.2.0.1

ZQRN:GTPU,0:AA1:10.1.1.10,P:32:10.2.0.1;

ZQRN:GTPU,1:AA1:10.1.1.11,P:32:10.2.0.1;

b. Configure GTPU-2 and GTPU-3 to serve SGSN address10.3.0.1

ZQRN:GTPU,2:AA2:10.1.2.12,P:32:10.3.0.1;

ZQRN:GTPU,3:AA2:10.1.2.13,P:32:10.3.0.1;

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, two GTP-U endpoint addresses are used in SGSN:

. 10.2.0.1 in GPLC-1

. 10.3.0.1 in GPLC-2

Four GTPU units are divided into two groups and each group is deployedto handle the Packet Switched Radio Access Bearers in RNC in loadsharing mode. When RNC receives RAB assignment with IP address10.2.0.1, GTPU-0 and GTPU-1 will be selected in a round-robin mode.Similarly, when RAB assignment with IP address 10.3.0.1 is received,GTPU-2 and GTPU-3 will be selected in a round-robin mode.

Each GTPU is logically connected to both GPLC units in the SGSN so thateven if one link fails, the interface capacity between the RNC and SGSNremains the same. Note that the same redundancy can be achieved byusing OSPF instead of static routing (see the next example: configuring Iu-PS when OSPF is in use).


30/01/2009


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

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





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


RNC SGSN

VPI=0, VCI=41

VPI=0, VCI=40

VPI=0, VCI=43

VPI=0, VCI=42

STM-1 line #1

STM-1 line #2

VPI=0, VCI=41

VPI=0, VCI=40

VPI=0, VCI=43

VPI=0, VCI=42

= GPLC-1

= GPLC-2

= primary route

10.3.0.1

GPLC-2

10.1.2.1

AA0

AA1GTPU-0

AA0

AA1GTPU-2

10.1.2.10 10.1.2.1

10.1.1.10 10.2.0.1

10.1.1.12 10.1.1.1

10.1.2.12 10.3.0.1

AA0

AA1GTPU-1

10.1.1.11 10.1.2.1

10.1.2.11 10.2.0.1

AA0

AA1GTPU-3

10.1.1.13 10.3.0.1

10.1.2.13 10.1.1.1

10.1.1.1

10.2.0.1

GPLC-1

DN02143138Issue 13-0 en30/01/2009

















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


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

ZQRN:GTPU,1:AA1:10.1.2.11,P:32:10.2.0.1;

ZQRN:GTPU,2:AA0:10.1.1.12,P:32:10.1.1.1;

ZQRN:GTPU,3:AA1:10.1.2.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:AA0:10.1.1.11,P:32:10.1.2.1;

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

ZQRN:GTPU,3:AA0:10.1.1.13,P:32:10.3.0.1;

4. Create default static routes for GTPUs.





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


30/01/2009


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

This example shows how to configure the Iu-PS interface between theRNC and SGSNs using two GTPUs connected to different SGSN. In thisexample, two GTP-U endpoint addresses are used in each SGSN:

. 10.2.1.1 and 10.2.1.2 in SGSN1

. 10.2.2.1 and 10.2.2.2 in SGSN2

Two GTPU units are separately deployed to handle the Packet SwitchedRadio Access Bearers originated from different SGSN in RNC. When theRNC receives RAB assignment with IP address 10.2.1.1 or 10.2.1.2, onlyGTPU-0 will be possibly selected. Similarly, when RAB assignment with IPaddress 10.2.2.1 or 10.2.2.2 is received, only GTPU-1 will be possiblyselected.

Figure 30. ATM virtual channel connections and IP addresses with GTPUsconnected to different SGSNs


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

RNC SGSN1

VPI=0, VCI=40

STM-1 line #1

STM-1 line #2

SGSN1

SGSN2

AA0

GTPU-0

GTPU-1

10.1.1.1 10.2.1.1 GTP-0 10.2.1.1

GTP-1 10.2.1.2

SGSN2

AA0 10.1.2.1 10.2.2.1 GTP-0 10.2.2.1

GTP-1 10.2.2.2

VPI=0, VCI=41

10.1.1.2 10.2.1.2

10.1.2.2 10.2.2.2

DN02143138Issue 13-0 en30/01/2009



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


. In ATM interface 1, one VCLtp with VPI=0 and VCI=40.

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


. In ATM interface 2, one VCLtp with VPI=0 and VCI=41.


a. Create IP over ATM interfaces connected to SGSN1


b. Create IP over ATM interfaces connected to SGSN2



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

a. Configure interfaces connected to SGSN1

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

ZQRN:GTPU,0:AA0:10.1.1.2,P:32:10.2.1.2;

b. Configure interfaces connected to SGSN2

ZQRN:GTPU,1:AA0:10.1.2.1,P:32:10.2.2.1;

ZQRN:GTPU,1:AA0:10.1.2.2,P:32:10.2.2.2;

4. Create default static routes for GTPUs



Example Configuring Iu-PS by using static routes for redundancy

This example shows another way to configure Iu-PS by using static routesto archieve the redundancy purpose.

In this example, there are two GTP-U endpoint addresses belonging to asame sub-net in SGSN: 10.10.1.1/24 and 10.10.1.2/24:


30/01/2009


. 10.10.1.1 in GPLC-1

. 10.10.1.2 in GPLC-2

The network topology enables each GTPU in RNC to reach the twoaddresses in SGSN. In this example, each GTPU is configured to serveboth two addresses in a load sharing mode.

Figure 31. GTPUs connected to SGSN by ATM and Ethernet


Create the following ATM configuration. For instructions, seeCreating ATM resources in RNC in ATM Resource Management.. STM-1 ATM interface (with interface ID 1).. 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).. In ATM interface 2, one VPLtp with VPI=0.. In ATM interface 2, two VCLtps with VPI=0 and VCI=40, 41

RNC SGSN

STM-1line #1

10.10.1.1

GTPU-0

GTPU-1

STM-1line #2

10.10.1.2

GPLC-2EL1

EL0

GPLC-1EL1

EL0EthernetSwitch

EthernetSwitch

Router

10.1.4.2

10.1.2.2

AA1 10.1.2.1 10.1.2.2

AA0 10.1.1.1 10.1.1.2

Router

10.1.3.2

10.1.1.2

AA1 10.1.4.1 10.1.4.2

AA0 10.1.3.1 10.1.3.2

= primary route

DN02143138Issue 13-0 en30/01/2009









Note

Do not configure the destination address to the SGSN endpointaddresses.

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

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

ZQRN:GTPU,1:AA0:10.1.3.1,P:32:10.1.3.2

ZQRN:GTPU,1:AA1:10.1.4.1,P:32:10.1.4.2;

4. Create static routes for GTPUs

For primary path, configure a host or sub-net route, while for backuppath, a default route is used. GTPUs always route IP packet via thehost or sub-net route as long as the corresponding AA interface is upand operational. In case the AA interface used by the primary path isdown, the backup path will be used. In this example, the primarypath in GTPU-0 is AA0, while the primary path in GTPU-1 is AA1.

a. Configure a sub-net route to SGSN via AA0 in GTPU-0

ZQKC:GTPU,0:10.10.1.0,24:10.1.1.2:PHY;

b. Configure a default route to SGSN via AA1 in GTPU-0

ZQKC:GTPU,0::10.1.2.2:PHY;

c. Configure a sub-net route to SGSN via AA1 in GTPU-1

ZQKC:GTPU,1:10.10.1.0,24:10.1.4.2:PHY;

d. Configure a default route to SGSN via AA0 in GTPU-1

ZQKC:GTPU,1::10.1.3.2:PHY;

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.


30/01/2009


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 importedto OSPF properly to be learnt by GTPU. Refer to the manual of SGSN formore details.

Figure 32. Iu-PS configuration with OSPF in use






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

= GPLC-2

= 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

DN02143138Issue 13-0 en30/01/2009



















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.

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

ZQKE:GTPU,0:0.0.0.1;





30/01/2009


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

AA0 or AA1 can be selected as the primary route for user traffic bygiving different OSPF costs. The interface with lower cost will bepreferred.

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;

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 has 2 VCCs, one is for RT traffic, the other one is for NRT traffic.

DN02143138Issue 13-0 en30/01/2009



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 33. ATM virtual channel connections and IP addresses with 2 VCCsunder one IPoA interface


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.

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

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

10.1.1.10AA1GTPU-0

10.1.1.11AA1GTPU-1

10.1.1.12AA1GTPU-2

10.1.1.13AA1GTPU-3

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

10.1.2.1

10.1.1.1


30/01/2009


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.


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






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.





DN02143138Issue 13-0 en30/01/2009



4.2 Configuring IP for Iu-PS user plane with NPS1(P)

Purpose

The NPS1(P) unit can be used for IP over ATM (IPoA) connectionsbetween two network elements such as RNC and SGSN.

Before you start

Check that the LAN cables are correctly attached to the NP8S1 unit. Formore information, see Cable Lists in Site documentation.

Steps

1. Interrogate external IP over ATM interfaces (QMI)

ZQMI:[<unit type>],[<unit index>],[<logicalconnection type>]:[<IP interface>]:[<ATMinterface>],[<VPI>],[<VCI>]:[<encapsulationmethod>]:[<state>];

2. Create external IP over ATM interfaces (QMF)

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

3. Assign IP addresses to ATM interfaces (QRN)

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

Note

The IP addresses must be assigned from different sub networks.

4. Assign an IP address to the loopback interface, if necessary(QRN)

Details see instructions in Configuring IP parameters and addressesof interfaces.


30/01/2009


For IPv4:

ZQRN:<unit type>,<unit index>:<interface name>:<IPaddress>,:[<netmask length>]:::;

5. Configure IP based route

Set up the IP based route identifier list and designate the committedbandwidth as well as committed signalling bandwidth, then configurethe IP based route according to the identifier list. For details, refer toWCDMA RAN04 Parameter Dictionary in NOLS.

ZQRU:<action mode>:<IP-based route id>,<IP-basedroute name>:[ip_based_route_bandwidth]:[committed_bandwidth]:[committed_signal_bandwidth]:[committed_dcn_bandwidth]:[ifc_option],[ifc_ratio];

Note

If the 'committed_bandwith', 'comitted_sig_bandwidth' and'committed_dcn_bandwidth' are all zero, it means no CAC is done inthis IP based route. In the ADD mod, the 'ip_based_route_bandwidth','committed_bandwith', 'comitted_sig_bandwidth' and‘committed_dcn_bandwidth’ are all obligatory and have no defaultvalue. When the 'ifc_option' is ON, it means there is flow control for thisIP based route. In the MOD mode, the 'ifc_option' can not be modifiedand the 'ifc_ratio' can be modified when original 'ifc_option' is ON.

ZQRC:<UNIT>,<INDEX>:<IP INTERFACE NAME>:[<IPV4>]=<IP ADDRESS>:<ID/NAME>=<IP BASED ROUTE ID/”IP BASEDROUTE NAME”>;

If an IP based route is attached to more than one IP address, itmeans load sharing needs to be done for this IP based route.

6. Create Static Routes if needed (QKC)


DN02143138Issue 13-0 en30/01/2009



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 Configuring IP parameters and addresses of interfaces.



a. Set the IP address for loopback


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


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


d. Configure an interface for that area


8. Create the user defined DSPM profile (optional)

Besides the default mapping profile, you can create the DSCP toPHB mapping profile. For more information, see Configuring DSCPto PHB mapping profile.

Note

For the two parameters 'PROFILE ID' and 'PROFILE NAME', you needto enter the value for at least one of them.


30/01/2009


ZQ8B:<MODE>:[<PROFILE ID>]:[<PROFILE NAME>]:[<DATATYPE>]:[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>";

9. Assign the DSPM profile for NPS1(P) (optional)

See instructions in Configuring and interrogating IP interface QoSparameters.

ZQ8S:<UNIT>,<INDEX>:<IP INTERFACE NAME>:[<ENABLED/DISABLED>]:[<ID=DSPM PROFILE ID>/<NAME=”DSPMPROFILE NAME”>];

Example IP configuration for Iu-PS with one IP based route with singleNPS1

The following example shows how to configure NPS1P to connect toSGSN with IP over ATM connection. One endpoint address is used inSGSN: 10.3.0.1 in GPLC-1.

The ATM AAL5 connection should be configured properly beforehand.

Figure 34. ATM virtual channel connections and IP addresses with NPS1connected to GPLC unit


Create the following ATM configuration (for instructions, seeCreating ATM resources in RNC in ATM Resource Management):. STM-1 ATM interface (with interface ID 1). In ATM interface 1, one VPLtp with VPI=0. In ATM interface 1, two VCLtps with VPI=0 and VCI=40

2. Create IP over ATM interfaces to all NPS1

10.1.1.1 -> 10.1.1.2IFAE0

VPI=0, VCI=40

STM-1 line #1

NPS1 GPLC110.1.1.2

10.3.0.1

DN02143138Issue 13-0 en30/01/2009



ZQMF:NPS1,0,L:IFAE0:1,0,40:1,IPCONN;


ZQRN:NPS1,0:IFAE0:10.1.1.1,P:32:10.1.1.2;

4. Configure IP based route to NPS1 for different IP Networks

ZQRU:ADD:20,"IPROUTE":11000:10000:100:100:ON,60;

ZQRC:NPS1,0:IFAE0:IPV4=10.1.1.1:ID=20;

5. Create static routes for NPS1

Configure a subnet route to SGSN via IFAE0

ZQKC:NPS1,0:10.3.0.1,24:10.1.1.2:PHY;

Example IP configuration for Iu-PS with multiple IP based routes withsingle NPS1

Figure 35. Configuration of Ethernet interfaces between NPS1 units andexternal routers via OSPF

This example shows how to configure the Iu-PS interface between theRNC and SGSNs using one NPS1 connected to different SGSN. In thisexample, one endpoint address is used in each SGSN.

. 10.3.0.1 in SGSN1

. 10.3.0.2 in SGSN2

IFAE0

NPS1

IFAE1

10.1.1.1 -> 10.2.1.1

10.1.2.1 -> 10.2.1.2

10.2.1.1

10.3.0.1

10.2.1.2

10.3.0.2

VPI=0, VCI=40

VPI=0, VCI=41

STM-1 line #1

STM-1 line #2

SGSN1

SGSN2


30/01/2009


Two IP base routes are configured on two IP addresses to handle thePacket Switched Radio Access Bearers (RAB) originated from differentSGSN in the RNC. When the RNC receives the RAB assignment with IPaddress 10.3.0.1, 10.1.1.1 will be selected as the local IP address.Similarly, when the RAB assignment with IP address 10.3.0.2 is received,10.1.2.1 will be selected as the local IP address.


Create the following ATM configuration (for instructions, seeCreating ATM resources in RNC in ATM Resource Management):. STM-1 ATM interface (with interface ID 1). In ATM interface 1, one VPLtp with VPI=0. In ATM interface 1, two VCLtps with VPI=0 and VCI=40. STM-2 ATM interface (with interface ID 2). In ATM interface 2, one VPLtp with VPI=0. In ATM interface 2, two VCLtps with VPI=0 and VCI=41

2. Create IP over ATM interfaces to all NPS1




ZQRN:NPS1,0:IFAE0:10.1.1.1,P:32:10.2.1.1;

ZQRN:NPS1,0:IFAE1:10.1.2.1,P:32:10.2.1.2;

4. Configure IP based route to NPS1 for different IP Networks





5. Create the static routes for NPS1

Configure the subnet routes to SGSN via IFAE0 and IFAE1

ZQKC:NPS1,0:10.3.0.1,24:10.2.1.1:PHY;

ZQKC:NPS1,0:10.3.0.2,24:10.2.1.2:PHY;

DN02143138Issue 13-0 en30/01/2009



4.3 Configuring IP for user plane with NPGE(P)

Purpose

The NPGE(P) unit is used for Ethernet connections to the IP basedinterfaces, such as Iub, Iur, Iu-CS, Iu-PS. NPGE(P) unit terminates UDP/IPprotocols and forwards packets to SGSN, MGW, RNC, and so on.

Before you start

Check that the LAN cables are correctly attached to the NP2GE unit. Formore information, see Cable Lists in Site documentation.

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). Enter the name of the unitfor the unit type parameter.

ZUSI:<unit type>;

2. Configure the Ethernet interface in NPGE(P) (optional)

Change the Ethernet interface working rate if the connectedEthernet device requires it. The communication will fail if differentworking mode is set on the connected Ethernet devices.

NPGE(P) also provides Ethernet shaping functionality, so a specificvalue for the bandwidth can be associated to the IFGE Ethernetinterface (not allowed for IFFE interface) to restrict the output rate.

For detailed instructions, see chapter Configuring Etherentinterfaces

ZQAS: <unit type>,<unit index>:<IFGE0|IFGE1>:[ <ratevalue>],[<bandwidth value>];

3. Create VLAN interface in NPGE(P) (optional)

First create VLAN interface if VLAN functionality is used in NPGE(P).See instructions in Creating and modifying VLAN interfaces.

ZQRM:<NPGE/NPGEP>,<unit index>:<VLAN name>:<VLANid>:<VLAN physical interface>;


30/01/2009


4. Assign an IP address to the external Ethernet interface or VLANinterface of NPGE(P) unit

See instructions in Configuring IP parameters and addresses ofinterfaces.

For IPv4:


Note

If the jumbo frames is supported, it is recommended to configure theMTU with enough big value, for example 4500 on NPGE(P) (IFGE0/IFGE1) interface to avoid fragmentation because the fragmentation/defragmentation affects the NPGE(P)'s performance.

The QRN MML command can be used to change the MTU value.

ZQRN:<unit type>,<unit index>:<interface name>::::[<MTU>]:;

5. Assign an IP address to the loopback interface of NPGE(P) unit,if necessary

For detailed instructions, see chapter Configuring IP parameters andaddresses of interfaces.

For IPv4:


6. Configure IP based route

Set up the IP based route identifier list and designate the committed

bandwidth as well as committed signalling bandwidth. Thenconfigure the IP based route according to the identifier list. Fordetails, refer toWCDMA Radio Network Configuration Parameters inNOLS.

DN02143138Issue 13-0 en30/01/2009



NED?action=retrieve&library=ru_rel_10_v1_2009_01_27&identifier=dn00211177&edition=311&language=en&coverage=global&encoding=pdf_online_a4&component=data&item=data

ZQRU:<action mode>:<IP-based route id>,<IP-basedroute name>:[ip_based_route_bandwidth]:[committed_bandwidth]:[committed_signal_bandwidth]:[committed_dcn_bandwidth]:[ifc_option],[ifc_ratio];

Note

If the 'committed_bandwith', 'committed_signal_bandwidth' and'committed_dcn_bandwidth' are all zero, it means no CAC is done inthis IP based route. In the ADD mod, the 'ip_based_route_bandwidth','committed_bandwith', 'committed_signal_bandwidth' and‘committed_dcn_bandwidth’ are all obligatory and have no defaultvalue. When the 'ifc_option' is ON, it means there is flow control for thisIP based route. In the MOD mode, the 'ifc_option' can not be modifiedand the 'ifc_ratio' can be modified when original 'ifc_option' is ON.

ZQRC:<UNIT>,<INDEX>:<IP INTERFACE NAME>:[<IPV4>]=<IP ADDRESS>:<ID/NAME>=<IP BASED ROUTE ID/”IP BASEDROUTE NAME”>;

If an IP based route is attached to more than one IP address, itmeans load sharing for this IP based route is enabled.

7. Configure the static routes for NPGE(P)

Create the static routes from NPGE(P) to the external destination(for example, a router). See instructions in Creating and modifyingstatic routes.

2N redundant units (NPGEP) must have logical static routes. Youcan have several NPGE(P) interfaces to the same destinationnetwork. To enable load sharing in the NPGE(P) units, configurestatic routes through more than one NPGE(P) interfaces.

For IPv4:




30/01/2009



a. Set the IP address for loopback


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


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


d. Configure an interface for that area


9. Create the user defined DSPM profile (optional)

Besides the default mapping profile, you can create the DSCP toPHB mapping profile. For more information, see Configuring DSCPto PHB mapping profile.

Note

For the two parameters 'PROFILE ID' and 'PROFILE NAME', you needto enter a value for at least one of them.

ZQ8B:<MODE>:[<PROFILE ID>]:[<PROFILE NAME>]:[<DATATYPE>]:[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>";

10. Assign the DSPM profile for NPGE(P) (optional)

See instructions in Configuring and interrogating IP interface QoSparameters.

DN02143138Issue 13-0 en30/01/2009



ZQ8S:<UNIT>,<INDEX>:<IP INTERFACE NAME>:[<ENABLED/DISABLED>]:[<ID=DSPM PROFILE ID>/<NAME=”DSPMPROFILE NAME”>];

Example Configuring Ethernet interfaces between NPGE units and theexternal routers for Iub interface

The following example shows how to connect NPGE(P) unit to RNC viaexternal physical routers for Iub interface.

1. Interrogate the state of the units

ZUSI:NPGEP;

2. Configure the Ethernet shaping rate to limit the outgoing traffic

The same configuration must be set to the redundant unit separately.

ZQAS:NPGEP,0:IFGE0:BANDWIDTH=800;

ZQAS:NPGEP,1:IFGE0:BANDWIDTH=800;

3. Create IPv4 address in Ethernet or VLAN interface for the NPGE unit

Configure IPv4 address in Ethernet interface.

ZQRN:NPGEP,0:IFGE0:10.33.160.4,P:28;

or

Configure IPv4 address in VLAN interface.

ZQRM:NPGEP,0:VL38:8:IFGE0;

ZQRN:NPGEP,0:VL38:10.33.160.4,P:28;

ZQRN:NPGEP,0:IFGE0:::::UP;

4. Configure the IP based route to NPGE for one BTS


ZQRC:NPGEP,0:IFGE0:IPV4=10.33.160.4:ID=20;

The ‘ip_based_route_bandwidth’, 'committed_bandwith','committed_signal_bandwidth', and 'committed_dcn_bandwidth'should be configured according to the bandwidth of last mileconnection to the BTS.

RNC will do CAC based on 'committed_bandwith'. When the'ifc_option' is ON, it means there is flow control for this IP basedroute and RNC will do traffic shaping for the BTS.

5. Create static routes from NPGE to BTS via the external router


30/01/2009


ZQKC:NPGEP,0:10.33.161.0,24:10.33.160.1:PHY;

Figure 36. Connecting NPGE to multiple IP networks for Iub interface

6. Create a user defined DSPM profile with the given ID and name

ZQ8B:CR:1:"DSPM-PROFILE-1":DEC:EF="12,13",AF2="32",AF4="24,25":;

7. Assign a DSPM profile to an IP interface in NPGE by the givenprofile ID

ZQ8S:NPGEP,0:IFGE0:ENA:ID1=1:;

Example Configuring Ethernet interfaces between NPGE units andexternal routers for Iu-CS interface with one IP based routeacross multiple NPGE units

NPGEP-0(WO) IFGE0

NPGEP-1(SP) IFGE0

IP Network

10.33.161.110.33.160.4/28

10.33.160.4/28

10.33.160.1

DN02143138Issue 13-0 en30/01/2009



Figure 37. Configure NPGEP to multiple IP network via OSPF

One IP based route is attached to two IP addresses, it means to do loadsharing for this IP based route. Two IP addresses added to differentNPGEs will be selected in a round-robin mode.

1. Interrogate the state of the units

ZUSI:NPGE;

2. Create the Ethernet interfaces for the NPGE units

ZQRN:NPGE,0:IFGE0:10.1.1.1,P:28;

ZQRN:NPGE,0:IFGE1:10.1.1.20,P:28;

ZQRN:NPGE,1:IFGE0:10.1.2.1,P:28;

ZQRN:NPGE,1:IFGE1:10.1.2.20,P:28;

3. Set the loopback IP addresses for the NPGE units

ZQRN:NPGE,0:LO0:10.2.1.100,L:32;

ZQRN:NPGE,1:LO0:10.2.2.100,L:32;

4. Configure the IP based route to NPGE for different IP networks


NPGE

MGW

NPGE0

10.2.1.100

10.2.1.100

10.2.1.100

NPGE1

LO0

10.2.2.100

IFGE1 10.1.2.20/28

IFGE0 10.1.1.1/28

IFGE1 10.1.1.20/28

IFGE0 10.1.2.1/28

LO0


30/01/2009


ZQRC:NPGE,0:LO0:IPV4=10.2.1.100:ID=20;

ZQRC:NPGE,0:LO0:IPV4=10.2.2.100:ID=20;

5. Create OSPF from NPGE to MGW via the external router

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

ZQKE:NPGE,0:0.0.0.1;

ZQKE:NPGE,1:0.0.0.1;

b. Configure two interfaces on each NPGE for that area. Thevalues for parameters area identification, hellointerval and router dead interval must be the same as inthe external router.

IFGE0 or IFGE1 can be selected as the primary route for usertraffic by giving different OSPF costs. The interface with lowercost will be preferred.

ZQKF:NPGE,0:IFGE0:0.0.0.1:::10;

ZQKF:NPGE,0:IFGE1:0.0.0.1:::20;

ZQKF:NPGE,1:IFGE0:0.0.0.1:::10;

ZQKF:NPGE,1:IFGE1:0.0.0.1:::20;

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

ZQKJ:NPGE,0:0.0.0.1:ADD:10.2.1.100:;

ZQKJ:NPGE,1:0.0.0.1:ADD:10.2.2.100:;

If the area in this example step 5.a is not configured as stubarea, redistribution can be also used to inform the address ofLO0.

ZQKU:NPGE,0:IF=LO0;

ZQKU:NPGE,1:IF=LO0;

DN02143138Issue 13-0 en30/01/2009




30/01/2009


5 Configuring signalling transport over IPfor control plane

5.1 Configuring signalling transport over IP over ATMfor 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 Planning site configuration for signalling and CreatingM3UA configuration.

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 connectiontype>:<IP interface>:<ATM interface>,<VPI number>,<VCI number>:[<encapsulation method>],[<usage|IPOAMdef>];

Note

Signalling unit should be in an active state before configuration.

DN02143138Issue 13-0 en30/01/2009


Configuring signalling transport over IP for control plane

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

Note

IP addresses must be assigned from different sub-networks.

3. Create static routes if needed (QKC)


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.

4. Make the IP configuration changes

When making changes to an IPoA configuration on ICSU, thereshould be no sockets in ESTABLISHED state using the relevant IPaddress. This can be achieved by removing the SCTP associationfrom the association set. After all necessary changes to IPoAconfiguration are done, a new association can be added to theassociation set.

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;


30/01/2009


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

5.2 Configuring signalling transport over IP overEthernet for control plane

Purpose

The purpose of this procedure is to configure the IP-based signallingtransport over Ethernet for RNC control plane. IP-based Iu-PS, Iu-CS, andIur SS7 signalling stack can be used. For detailed description, refer toPlanning site configuration for signalling and Creating M3UA configuration.

Before you start

Check that the LAN cables are correctly attached to the NPGE(P) unit. Formore information, see Cable Lists in Site documentation.

The signalling unit and the NPGE(P) unit should be in active state beforethe configuration starts.

Steps

1. Assign the IP addresses to the Ethernet interfaces of the NPGE(P) unit (QRN)

ZQRN:<unit type>,[<unit index>]:<interface name>:<IP address>,<L/P>:[<netmask length>]:;

Note

The IP addresses must be assigned from different sub-networks.

2. Create the static routes in the signalling unit and the NPGE(P)unit (QKC)


DN02143138Issue 13-0 en30/01/2009



Note

The IP address for the ATM interface of NPGE(P) unit is used as agateway address for the signalling unit to route traffic.

The parameter local IP address is only valid for local IP addressbased default route. 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.

3. Prepare the internal IP over ATM connection

a. Use the existing full mesh IPoA for Iur/Iu interface

The system maintains a full mesh IPoA connection betweenICSU and NPGE(P) unit. It is mainly used for IP based Iubinterface.

The instructions of configuring IP address for Iub on top of thefull mesh IPoA was included in chapter Configuring IPresources for Iub Control Plane (RNC-BTS/AXC) step 5. It isrecommended to use the same configuration for Iur/Iuinterface to simplify the process.

b. Configure separate internal IP over ATM interface to asignalling unit and the NPGE(P) unit (QMC)

ZQMC:ICSU,[<unit index>],L:<IP interface>:<NPGE/NPGEP>,<unit index>,L:<IP interface>::;

Note

The signalling unit and the NPGE(P) unit should be in an active statebefore the configuration starts.

4. Assign the IP addresses to both ATM interfaces of a signallingunit and the NPGE(P) unit (QRN)

ZQRN:<unit type>,[<unit index>]:<interface name>,U/N:<IP address>,L:32:[<destination IP address>]:<MTUsize>:;


30/01/2009


Note

The parameter IP address and the destination IP address configured tothe signalling unit should be the parameter destination IP address andthe IP address configured to the NPGE(P) unit.

The full mesh IPoA uses unnumbered addressing by default. Becausethe system expects an existing IP address during configuration, the IPaddress can be configured to LO0 interface first.

The MTU size should be no more than PMTU for the all connections.

5. Make the IP configuration changes

When making changes to an IPoA configuration on ICSU, thereshould be no sockets in ESTABLISHED state using the relevant IPaddress. This can be achieved by removing the SCTP associationfrom the association set. After all necessary changes to IPoAconfiguration are done, a new association can be added to theassociation set.

6. Create OSPF configuration in NPGE(P) unit if needed (QKF)

If dynamic route is used, refer to chapter Creating OSPFconfiguration for O&M connection to NetAct.

7. Configure the OSPF to inform other OSPF routers of the ICSUs'IP sub-net if needed (QKJ)

Redistribution can also be used to inform the IP sub-net of ICSU withthe QKU MML command.

If the dynamic route is used, refer to chapter Creating OSPFconfiguration for O&M connection to NetAct.

Example Configuring signalling transport over IP over Ethernet forcontrol plane

The following example shows how to configure ICSU-0 to connect toSGSN with multi-homing IP over Ethernet connection, going throughNPGEP-0 and NPGEP-2.

The existing internal IPoA network is used to simplify the configuration.

DN02143138Issue 13-0 en30/01/2009



The IP addresses for ICSU-0 are 10.20.1.1 and 10.20.2.1. They are usedlater as the SCTP primary source IP address and the secondary source IPaddress.

The IP address for NPGEP-0 is 10.20.1.2 and the IP address for NPGEP-2is 10.20.2.2.

The sub-net addresses for Iu-PS signaling of SGSN are 10.2.3.0/24 and10.2.4.0/24.

The IP addresses for SGSN are 10.2.3.1 and 10.2.4.1.

The IP addresses for site routers are 10.20.1.3 and 10.20.2.3.

1. Assign IP addresses to the Ethernet interfaces

ZQRN:NPGEP,0:IFGE0:10.20.1.2,L:24;


2. Create the static routes for the NPGE(P)

ZQKC:NPGEP,0:10.2.3.0,24:10.20.1.3;

ZQKC:NPGEP,2:10.2.4.0,24:10.20.2.3;

3. Check the existing internal IPoA interfaces

ZQMQ:ICSU,0;

4. Assign IP addresses to the IPoA interfaces

The interfaces are from the output of step 1.. AA495 <-> IFAI79 of NPGEP-0. AA496 <-> IFAI79 of NPGEP-2

The IP addresses for NPGEP is used also in internal IPoA interface.

ZQRN:ICSU,0:LO0:10.20.1.1;

ZQRN:ICSU,0:LO0:10.20.2.1;

ZQRN:ICSU,0:AA495,U:10.20.1.1,L::10.20.1.2:;

ZQRN:ICSU,0:AA496,U:10.20.2.1,L::10.20.2.2:;

ZQRN:NPGEP,0:IFAI79,U:10.20.1.2,L::10.20.1.1;


5. Create static routes for the ICSU

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

ZQKC:ICSU,0:10.2.4.0,24:10.20.2.2,:LOG:;


30/01/2009


6. Verify the IP connectivity from ICSU to SGSN

ZQRX:ICSU,0:IP=10.20.1.3;




Example Configuring signalling transport over IP over Ethernet forcontrol plane with OSPF

The following example shows how to configure the ICSU-0 to connect toSGSN with multi-homing IP over Ethernet connection, going throughNPGEP-0 and NPGEP-2.

The existing internal IPoA network is used to simplify the configuration.

The IP addresses for ICSU-0 are 10.21.1.1 and 10.21.2.1. They are usedlater as the SCTP primary source IP address and the secondary source IPaddress.

The IP address for NPGEP-0 is 10.21.1.2 and the IP address for NPGEP-2is 10.21.2.2.

The sub-net addresses for Iu-PS signaling of SGSN are 10.2.3.0/24 and10.2.4.0/24.

The IP addresses for SGSN are 10.2.3.1 and 10.2.4.1.

The IP addresses for site routers are 10.21.1.3 and 10.21.2.3.

1. Assign IP addresses to the Ethernet interfaces



2. Create the static routes for the NPGE(P)

ZQKC:NPGEP,0:10.2.3.0,24:10.21.1.3;

ZQKC:NPGEP,2:10.2.4.0,24:10.21.2.3;

3. Check the existing internal IPoA interfaces

ZQMQ:ICSU,0;

4. Assign IP addresses to the IPoA interfaces

DN02143138Issue 13-0 en30/01/2009



The interfaces are from the output of step 1.. AA495 <-> IFAI79 of NPGEP-0. AA496 <-> IFAI79 of NPGEP-2

The IP addresses for NPGEP is used also in internal IPoA interface.

ZQRN:ICSU,0:LO0:10.21.1.1;

ZQRN:ICSU,0:LO0:10.21.2.1;

ZQRN:ICSU,0:AA495,U:10.21.1.1,L::10.21.1.2:;

ZQRN:ICSU,0:AA496,U:10.21.2.1,L::10.21.2.2:;



5. Create static routes for the ICSU

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

ZQKC:ICSU,0:10.2.4.0,24:10.21.2.2,:LOG:;

6. Verify the IP connectivity from ICSU to SGSN





7. Create OSPF for NPGE(P)

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

ZQKE:NPGEP,0:0.0.0.1;

ZQKE:NPGEP,2: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 externalrouter.

IFGE0 or IFGE1 can be selected as the primary route forsignalling traffic by giving different OSPF costs. The interfacewith lower cost will be preferred.

ZQKF:NPGEP,0:IFGE0:0.0.0.1:::10;

ZQKF:NPGEP,2:IFGE0:0.0.0.1:::20;


30/01/2009


5.3 Configuring IP resources for Iub control plane(RNC-BTS/AXC)

Purpose

The purpose of this procedure is to prepare and configure IP resources forIub control plane.

Before you start

Check that the LAN cables are correctly attached to the NPGE(P) unit. Formore information, see Cable Lists in Site documentation.

Steps


2. Connect RNC to BTS/AXC via NPGE(P)

The NPGE(P) unit is used for Ethernet connection to the external IPnetwork. In Iub, only IPv4 is supported for the control plane.

Check that the LAN cables are correctly attached to the NPGE(P)unit. For more information, see Cable Lists in Site documentation.

a. 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). Enter the name of theunit for the unit type parameter.

ZUSI:<unit type>;

b. Assign an IP address to the external Ethernet interface ofNPGE(P) (QRN)

See instructions in Configuring IP parameters and addressesof interfaces.

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

Note

The external IP interface addresses must be configured in different sub-nets.

3. Configure the default static routes for NPGE(P)

DN02143138Issue 13-0 en30/01/2009



Create the default static routes from NPGE(P) to the externaldestination (for example, a router). See instructions in Creating andmodifying static routes.

Note

2N redundant units (NPGEP) must have logical static routes for IPv4.

You can have several NPGE(P) interfaces to the same destinationnetwork. To enable load sharing in the NPGE(P) units, configuredefault routes through more than one NPGE(P) interfaces.

4. Configure IP based route in NPGE(P)

IP based route ID is used by ICSU to select a right NPGE(P),through which signalling traffic is routed. For detailed instructions,refer to chapter IP based route configration.

5. Configure local IP sub-net for Iub Control plane

System selects ICSU for NBAP links based on load sharingalgorithm. So all ICSUs' AAx interfaces used for internal IPoAconnections between ICSU and NPGE(P) shall have one IP addressfrom the same IP sub-net configured.

a. Interrogate the states of internal IPoA connections created bythe system (QMQ)

Check that all ICSUs have internal IPoA connections to allNPGE(P). The range of interface names on ICSU side is fromAA450 to AA511. The range of interface name on NPGE(P)side is from IFAI30 to IFAI79. The interface name for the unit isallocated by the unit logical address statically.

ZQMQ:ICSU;

b. Configure local IP sub-net address for Iub Control plane(QMN)

ZQMN:1:<IPV4 address>,<netmask length>:;

c. Check the local IP sub-net and IP address configuration

The IP address for all the reserved internal IPoA is configured.The range of the IP address is from the sub-net IP address tothe sub-net IP address plus 63. The IP address for the ICSUunit is allocated by the unit logical address statically, while theIP address for the NPGE(P) unit is allocated by unit addressdynamically. This means the IP address for the NPGE(P) unitmay be changed if the NPGE(P) is changed from WO-EX toSE-NH and then from SE-NH to WO-EX.


30/01/2009


ZQML;

ZQRI:<unit_type>,<unit_index>;

DN02143138Issue 13-0 en30/01/2009




30/01/2009


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 13-0 en30/01/2009



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 internal IPover ATM interfaces and Creating and modifying external IP overATM interfaces.

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

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

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

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

3. Create a static route for Iu-BC

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

Note

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

For IPv4:


30/01/2009


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.

Example Configuring IP for Iu-BC through ICSU units

The following figure shows an example of IP configuration for Iu-BCinterface with IP addresses. The ICSU-0 is selected to be used towardsthe CBC.

Figure 38. Example of IPv4 configuration for Iu-BC

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

DN02143138Issue 13-0 en30/01/2009



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 sub-network 10.1.1.1/32to selected ICSU.

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

Note

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

3. Assign an IPV4 address to the selected ICSU.

ZQRN:ICSU,0:AA1:10.1.1.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;


30/01/2009


7 Creating and modifying DNSconfiguration

Purpose

You can create the DNS configuration with the QRK command in IPv4,

The interface-specific instructions for configuring the DNS can be found inthe 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.

Steps

1. Interrogate DNS parameter data

You can interrogate current DNS parameters with QRJ in IPv4.

This command has no parameters.

ZQRJ;

Expected outcome

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.

DN02143138Issue 13-0 en30/01/2009



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

Note

The default value for netmask is 0, for resolver cache YES and for roundrobin YES.

Note

To make sure that the primary domain name server (DNS) serverworks, do not use the operation and maintenance server (OMS) IPaddress as a primary DNS IP address.

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

If you want to leave the primary DNS server unchanged, do not enterany values for the first parameters. If the first DNS nameserver is setto

0.0.0.0 (for ZQRK)

then all three DNS server 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.


30/01/2009


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

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

DN02143138Issue 13-0 en30/01/2009




30/01/2009


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

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.

Steps

1. Interrogate IPv4 parameters (QRH)

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

2. Modify IPv4 parameters (QRT)

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

Note that units with the Chorus operating system do not supportlocal subnets (SNL). For more information on Chorus units, see theEngineering description.

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

DN02143138Issue 13-0 en30/01/2009


Modifying IP parameters

3. Delete IPv4 parameters (QRV)

ZQRV:<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 RNC:

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


30/01/2009


9 Configuring IP interfaces

9.1 Creating and modifying internal IP over ATMinterfaces

Purpose

This procedure describes how to interrogate, create and modify internal IPover ATM (IPoA) interfaces by NPS1(P) or NPGE(P). The internal IPoAinterface is configured between ICSU or OMU and NPGE(P) or NPS1(P)units. The interface-specific instructions for configuring IP interfaces canbe found in the Integration instructions.

Steps

1. Interrogate internal IP over ATM interfaces (QMQ)

ZQMQ:[<unit type>],[<unit index>],[<logicalconnection type>]:[<IP interface>]:[<unit 2 type>],[<unit 2 index>],[<logical connection type 2>]:[<IPinterface 2>]:[<inquiry> level>|MANUAL def];

2. Create or modify internal IP over ATM interfaces (QMC)

Internal IP over ATM interfaces can only be modified if they havebeen created manually.

ZQMC:<unit type>,[<unit index>],<logical connectiontype>:<IP interface>:<unit_2 type>,[<unit_2index>],<logical connection type_2>:<IPinterface_2>:[<encapsulation method>];

3. Delete internal IP over ATM interfaces (QMD)

DN02143138Issue 13-0 en30/01/2009


Configuring IP interfaces

ZQMD:INT:<unit type>,[<unit index>]:<IP interface>:<TPI interface>:<unit_2 type>,[<unit_2 index>]:[<IPinterface_2>];

Example Configuring internal IP over ATM interface by NPS1(P)/NPGE(P)

Figure 39. Internal IPoA by NPGE(P) or NPS1(P)

1. Configure IFAI0 interface with IP address 156.151.10.6 ->103.151.12.8 in NPS1-0

ZQRN:NPS1,0:IFAI0,N:156.151.10.6,P:28:103.151.12.8:;

2. Configure AA2 interface with IP address 103.151.12.8 ->156.151.10.6 in ICSU-0

ZQRN:ICSU,0:AA2,N:103.151.12.8,L:28:156.151.10.6:;

3. Configure internal IP over ATM interface from IFAI0 in NPS1-0 toICSU AA2 with encapsulation method VCMUX

ZQMC:NPS1,0,L:IFAI0:ICSU,0,L:AA2:2;

Example Delete internal IP over ATM interface

ZQMD:INT:NPS1,0:IFAI0::ICSU,0:AA2:;

NPS1(P) NPGE(P)

156.151.10.6->103.151.12.8IFAI0

SFU

ICSU-0OMU-0

SFUMXU

103.151.12.8->156.151.10.6AA2


30/01/2009


Example Interrogate internal IP over ATM interfaces

ZQMQ:OMU;

9.2 Creating and modifying external IP over ATMinterfaces

Purpose

This procedure describes how to interrogate, create and modify external IPover ATM (IPoA) interfaces. The external IPoA interface can be configuredon OMU, NPS1(P), RSMU and ICSU units. 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.

The IP stack also has to be configured before you can configure IPoAinterfaces. For more information, see:

1. Creating and modifying DNS configuration

2. Modifying IP parameters

3. Configuring IP parameters and addresses of interfaces

4. Creating and modifying static routes

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 commands LAI and LCI to interrogate ATMinterfaces and external termination points.

Steps

1. Interrogate external IP over ATM interfaces (QMI)

DN02143138Issue 13-0 en30/01/2009



ZQMI:[<unit type>],[<unit index>],[<logicalconnection type>]:[<IP interface>]:[<ATMinterface>],[<VPI>],[<VCI>]:[<encapsulationmethod>]:[<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.

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

3. Delete external IP over ATM interfaces (QMD)

ZQMD:EXT:<unit type>,[<unit index>]:<IP interface>:[<ATM interface>],<VPI number>,<VCI number>;

Example Configuring external IP over ATM interface in OMU


30/01/2009


Figure 40. Example of external IP over ATM configuration

The figure shows the following two subnetworks:

. subnetwork 189.151.0.0 with netmask length 28

IP addresses 189.151.0.0–189.151.0.15.


IP addresses 192.168.0.0–192.168.0.15.

OMU-0ISU-0

SFU

Network element 1

Networkelement 2

Networkelement 3

LAN

NIU-1VPI 20VCI 30

NIU-2VPI 20VCI 30

MUX

VC

OMU-1

192.168.0.1, interface AA3189.151.0.1, interface AA2

DN02143138Issue 13-0 en30/01/2009



1. Configure external IP over ATM interfaces

Configure external IP over ATM interface with network interfacename AA2 to OMU-0 from ATM interface 3 (NIU-1), VPI 20, and VCI30 with encapsulation method VCMUX.

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

Configure external IP over ATM interface with network interfacename AA3 to OMU-0 from ATM interface 4 (NIU-2), VPI 20, and VCI30 with encapsulation method VCMUX.

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

2. Configure external IPoA address

ZQRN:OMU,0:AA2,N:189.151.0.1,P:28;

ZQRN:OMU,0:AA3,N:192.168.0.1,P:28;

Example Configuring two external IPoA connections to one IP over ATMinterfaces in GTPU

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



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 Configuring external IP over ATM interface in NPS1(P)


30/01/2009


Figure 41. External IPoA by NPS1(P)

The figure shows the following two subnetworks:


IP address 152.162.0.0 – 152.162.0.15


IP address 182.151.0.0 – 182.151.0.15

Configure external IP over ATM interface with network interface name AA1to ICSU-0 from ATM interface 3 (NPS1-0), VPI-10, and VCI-20 withencapsulation method VCMUX.

ZQMF:ICSU,0,L:AA1:3,10,20:2;

Configure external IP over ATM interface with network interface IFAE2 inNPS1-0 from ATM interface 3 (NPS1-0), VPI-40, and VCI-50 withencapsulation method VCMUX.

ZQMF:NPS1,0,L:IFAE2:4,40,50:2;

Network elements

NPS1(P)

NPS1(P)

182.151.0.1 interface IFAE2

Interface 3VPI 10VCI 20

SFU

152.162.0.1 interface AA1

ICSU-0OMU-0

SFUMXU

DN02143138Issue 13-0 en30/01/2009



Example Delete external IP over ATM interface

ZQMD:EXT:ICSU,0:AA1:3,10,20:;

Example Interrogate external IP over ATM interfaces

ZQMI:OMU;

9.3 Configuring Ethernet interface

Purpose

You can configure and interrogate Ethernet interface configuration by theQA MML command group. This group of commands is only for the NPGE(P) unit.

Before you start

If you want to configure the Ethernet interface parameter, a NPGE(P) unitis needed to be configured in the system. It is not required that theinterface has been previously created with the QRN MML command.

Steps

1. Configure the rate for the Ethernet interface

You can set a new rate values for the Ethernet interface.

The rate can be specified for both IFFE and IFGE interface of NPGE(P) unit.

ZQAS:<unit type>,<unit index>:<IFFE0|IFFE1>:<ratevalue>;

ZQAS:<unit type>,<unit index>:<IFGE0|IFGE1>:<ratevalue>;

The rate values for the selected interface are 0, 10, 100, 1000. Thevalue 1000 is allowed only for IFGE interfaces. The value 0 indicatesthe auto-negotiated configuration. The default value is 0

2. Configure the bandwidth for the Ethernet interface


30/01/2009


You can set a new bandwidth value for the Ethernet interface. Thebandwidth can be specified only for IFGE interface of NPGE(P) unit(not allowed for IFFE interface).

ZQAS:<unit type>,<unit index>:<IFGE0|IFGE1>:<bandwidth value>;

3. Configure both rate and bandwidth for the Ethernet interface

When the interface is IFGE, you can set both the new bandwidth andrate value for the Ethernet interface.

ZQAS:<unit type>,<unit index>:<IFGE0|IFGE1>:<ratevalue>,<bandwidth value>;

4. Interrogate the Ethernet interface configuration parameters

You can get the rate and bandwidth values for one or more Ethernetinterfaces of one or more NPGE(P) units.

ZQAI:[<unit type>],[<unit index>]:[<interfacetype>];

5. Delete the Ethernet interface configuration

You can delete the associated interface and rate or interface andbandwidth so that the default values are restored.

ZQAD:<unit type>,<unit index>:<interface type>;

Example Configuring Ethernet interface parameters

The following example shows how to configure the Ethernet interfaceparameters.

1. Set the rate of IFFE0 interface on the NPGE-0 to 100

ZQAS:NPGE,0:IFFE0:RATE=100;

2. Set the rate to 1000 and the bandwidth to 900 of IFGE0 interface onthe NPGE-0

ZQAS:NPGE,0:IFFE0:RATE=100,BANDWIDTH=900;

3. Interrogate the rate and bandwidth for all the interfaces of all theNPGE(P) unit in the system

ZQAI;

DN02143138Issue 13-0 en30/01/2009



4. Interrogate the rate for the IFFE0 interface on NPGE-0

ZQAI:NPGE,0:IFFE0;

5. Reset the rate associated to IFGE0 of the NPGE-0 to restore the rateand bandwidth to the default values

ZQAD:NPGE,0:IFGE0;

9.4 Creating and modifying VLAN interfaces

Purpose

You can create and delete a VLAN interface with commands QRM and QRR.After VLAN interface is created, you can configure parameters of VLANinterfaces with the QRN command. NPGE(P) is the only unit to supportVLAN interface. The VLAN interface is configured according to IEEE802.1Q protocol.

Steps

1. Interrogate the VLAN interfaces

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

ZQRE:[<UNIT TYPE>],[<UNIT INDEX>]:[<VLAN NAME>]:[<VLAN ID>]:[<VLAN PHYSICAL INTERFACE>];

2. Create the VLAN interfaces

Create the VLAN interface identified by the VLAN name and theVLAN ID, and attach them to one physical GE interface.

ZQRM:<UNIT TYPE>,<UNIT INDEX>:<VLAN NAME>:<VLAN ID>:<VLAN PHYSICAL INTERFACE>;

The VLAN name should be exclusive within one unit and the VLANID should also be only attached to one physical interface.

3. Delete the VLAN interfaces

Identify the VLAN interface you want to delete by the parametersVLAN name or VLAN ID within one unit. The VLAN interfaceparameters should be removed with command QRG before deletingthe VLAN interface.


30/01/2009


ZQRR:<UNIT TYPE>,<UNIT INDEX>:[<VLAN NAME>:<VLANID>];

4. Configure or modify the parameters of the VLAN interfaces

Configure or modify the IPv4 address, MTU and if state into theexisting VLAN interface. For detailed instructions, see Configuring IPparameters and addresses of interfaces.

Note

The VLAN interface's status is dependent on the Ethernet interface. Itrequires Ethernet interface with up status first.

5. Delete the VLAN interface parameters

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

Example

This example shows how to create and configure the VLAN interface.

1. Create a VLAN interface to NPGE-0 unit.

The VLAN name is 'VL8', the VLAN ID is 5, and they are attached tophysical interface IFGE0.

ZQRM:NPGE,0:VL8:5:IFGE0;

2. Interrogate all VLAN interfaces in NPGE-0

ZQRE:NPGE,0;

3. Delete the VLAN interface and whose name is 'VL8'

ZQRR:NPGE,0::VL8;

4. Configure IP address to the VLAN interface

ZQRN:NPGE,0:VL8:10.1.1.8,P:24:;

5. Modify the MTU value and its state of the VLAN interface

ZQRN:NPGE,0:VL8::::1200:UP;

DN02143138Issue 13-0 en30/01/2009



9.5 Configuring IP parameters and addresses ofinterfaces

Purpose

You can configure a new network interface or IP address with the QRNcommand in IPv4.

The interface-specific instructions for configuring IP interfaces can befound in the Integration instructions.

Steps

1. Interrogate network interfaces (QRI)

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

All IPv4 addresses of the network interface will be displayed.

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

2. Create IPv4 interfaces (QRN)

Identify the IP interface you want to create with parameters unit

type, unit index and interface name. You can also add an IPv4address of the network interface by giving the desired IPv4 address.

The default value for netmask length is 8 (A class), 16 (B class), or24 (C class).

For 2N NP2GE/NP8S1 unit, only logical address can be configuredbecause IP configuration on 2N NP2GE/NP8S1 should always beidentical.

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

ISU and OMU units TCU units NPGE units NPS1 units

EL AA IFETH AI IFGE IFFE IFAI IFAE IFFE IFAI

MinMTU

1500 500 1500 1500 500 1500 500 500 1500 500


30/01/2009


MaxMTU

1500 9180 1500 1500 4500 1500 4500 9180 1500 4500

DefaultMTU

1500 9180 1500 1500 1500 1500 1500 9180 1500 1500

VLAN MTU's range is dependent on MTU of physical interfaceattached, MIN MTU is 496, MAX MTU is IFGE MTU minus 4, defaultVALUE is IFGE MTU minus 4.

Note

If the jumbo frames is supported, it is recommended to configure theMTU with enough big value, for example 4500 on NPGE(P) (IFGE0/IFGE1) interface to avoid fragmentation because the fragmentation/defragmentation affects the NPGE(P)'s performance.

3. Modify IPv4 interfaces (QRN)

Identify the IP interface you want to modify with parameters unit

type, unit index and interface name.

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

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 the command QRG and configure it to anotherpoint-to-point interface type.

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

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

4. Delete IPv4 interface (QRG)

All IPv4 addresses of this interface will be deleted along with thenetwork interface. If IP address is identified, only this IP address willbe deleted.

DN02143138Issue 13-0 en30/01/2009



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

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

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 IP address to OMU

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


30/01/2009


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

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

If you want to create a logical address for a 2N redundant unit, do notinclude the unit index parameter and assign the value L to the IP

address type parameter. In IPv4 logical IP address configuration, forexample, the netmask length is 27 and the status is set to UP.

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

ZQRN:NPGEP,0:IFGE0:192.168.3.3,L:24:::UP:;

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

This example changes the IPv4 configuration for OMU interface AA11.

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;

DN02143138Issue 13-0 en30/01/2009




30/01/2009


10 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 network in the OSPFarea.

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

Note

OSPF configuration can not be supported on the VLAN interface.

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

Note

Router id 0.0.0.0 means router id is chosen automatically.

2. Configure OSPF area parameters (QKE)

DN02143138Issue 13-0 en30/01/2009



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.

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.


30/01/2009


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.

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

Figure 42. Use of virtual link

7. Configure stub network, if required (QKJ)

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

ZQKJ:<unit type>,<unit index>:<areaidentification>:[ADD|DEL]:<stub network>,<stubnetwork mask length>:[<stub network cost>];

Area 0Backbone

Area 2

Area 1

Virtual link

Border router B

Border router A

DN02143138Issue 13-0 en30/01/2009




30/01/2009


11 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 address based default routes are a special kind ofstatic routes. An outgoing IP packet matching a local IP address baseddefault route will be sent according to its local IP address instead of itsdestination address. They usually cooperate with SCTP multihoming toease the configuration of static routes on ISU. Currently, only IPv4 issupported.

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 isALL; 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 13-0 en30/01/2009



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

Note

Currently, local IP address based static routes are supported in IPv4only.

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

Example Configuring the default IPv4 static routes in OMU

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

ZQKC:OMU,0::10.20.41.1,:LOG;

Use the following command to interrogate the static route

ZQKB:OMU;

Expected Outcome


30/01/2009


UNIT DESTINATION GATEWAY ADDRESS TYPE PREFERENCE NBR

OMU-0 DEFAULT ROUTE 10.20.41.1 LOG 0 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 13-0 en30/01/2009




30/01/2009


12 Creating and modifying IP QoSconfiguration on NPS1/NPGE unit

12.1 Configuring DSCP to PHB mapping profile

Purpose

You can configure the DSCP to PHB mapping profile by the commands ofthe Q8 MML command group. This group of commands provides theoperation for configuration, interrogation and deletion of the DSPM profile.A default DSPM profile, which can only be interrogated, is also provided.

Before you start

The default DSCP to PHB mapping is provided by the system. It cannot bemodified or removed. The detailed configuration is shown as below:

PHB DSCP values

EF 46

AF1 10, 12, 14

AF2 18, 20, 22

AF3 26, 28, 30

AF4 34, 36, 38

BE 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 11, 13, 15, 16, 17, 19, 21, 23, 24,25, 27, 29, 31, 32, 33, 35, 37, 39, 40, 41, 42, 43, 44, 45, 47, 48, 49, 50,51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63

Steps

1. Modify the DSPM profile configuration (Q8B)

You can create or modify the DSPM profile by the followingcommand:

DN02143138Issue 13-0 en30/01/2009


Creating and modifying IP QoS configuration on NPS1/NPGE unit

ZQ8B:<MODE|CR/MO>:[<PROFILE ID>]:[<PROFILE NAME>]:[<DATA TYPE>]:[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>";

2. Interrogate the DSPM profile configuration (Q8L)

You can interrogate the configured DSPM profile including thedefault DSPM profile. All the profiles can be shown by not giving anyparameters.

ZQ8L:[<PROFILE ID RANGE>],[<PROFILE NAME>];

3. Delete the DSPM profile configuration (Q8D)

You can delete DSPM profiles. If the profile is in use, for example,the profile has been assigned to one or more IP interfaces, theprofile and the default DSPM profile cannot be deleted.

ZQ8D:[<PROFILE ID RANGE>],[<PROFILE NAME>];

Example Configuring the DSPM profile

Configure a DSPM profile with certain PHB and DSPM mapping values.

1. Interrogate the current DSPM profiles

ZQ8L;

2. Configure a new DSPM profile by the given name and ID

ZQ8B:CR:1:”DSPM-PROFILE-1”:DEC:EF=”30,33,34”,AF1=”22,23,24”;

3. Interrogate the newly created DSPM profile by the name

ZQ8L:NAME=”DSPM=PROFILE-1”;


30/01/2009


12.2 Configuring PHB profile

Purpose

You can configure the PHB profile by the Q8 MML command group. Thisgroup of commands provides the operation for configuration, interrogationand deletion of the PHB profile. A default PHB profile is also provided,which can only be interrogated. PHB parameters are partly configurablewith their own scope.

Before you start

The default PHB profile is provided by the system. It can not be modified orremoved. The detailed configuration is shown as below:

PHBname

Queueschedule

Queuelength

Queueweight

Queuepriority

Min Thd(%)

Max Thd(%)

MaxDrop(%)

Exp.Weight

VLANpriority

BE WRR 500 1 NRT 75 100 10 0 0

AF1 WRR 300 4 NRT 75 100 10 0 1

AF2 WRR 300 10 NRT 75 100 10 0 3

AF3 WRR 300 25 NRT 75 100 10 0 4

AF4 WRR 100 60 RT 100 100 0 0 5

EF SP 100 N/A RT 100 100 0 0 6

PHB parameters configurable scope

Only the following PHB queue parameters are configurable by users. Theothers are defined by the system.

. Queue weight value

(0 – 10000). 0 is given by the system. Users can only configure thevalue in the scope of 1 to 10000.

. Queue priority

This attribute is changeable but it is not supported by the networkprocessor yet in RN4.0.

. WRED minimum thresholds

(0 -100%)

. WRED maximum thresholds

DN02143138Issue 13-0 en30/01/2009



(0 -100%)

This value is configurable but the configuration is not supported bynetwork processor yet in RN4.0.

. WRED maximum drop probability value

(0 -100%)

. Exponential weight factor

(0 -10)

This value is configurable but the configuration is not supported bynetwork processor yet in RN4.0.

. VLAN priority

(0 -7)

Steps

1. Modify the PHB profile configuration (Q8V)

You can create or modify the PHB profile by the following command:

ZQ8V:<MODE|CR/MO>:[<PROFILE ID>]:[<PROFILE NAME>]:<PHB VALUE>:<QUEUE WEIGHT>,<MIN THRESHOLD>,<MAXTHRESHOLD>,<WRED MAX DROP PROBABILITY>,<EXPONENTIALWEIGHT FACTOR>,<VLAN PRIORITY>;

2. Interrogate the PHB profile configuration (Q8W)

You can interrogate the configured PHB profile including the defaultPHB profile. All the profiles can be shown by not giving anyparameters.

ZQ8W:[<PROFILE ID RANGE>],[<PROFILE NAME>];

3. Delete the PHB profile configuration (Q8R)

You can delete PHB profiles. If the profile is in use, for example, theprofile has been assigned to one or more IP interfaces, the profileand the default PHB profile cannot be deleted.

ZQ8R:[<PROFILE ID RANGE>],[<PROFILE NAME>];

Example Configuring the PHB profile

Configure a PHB profile with the certain PHB queue parameters.


30/01/2009


1. Interrogate the current PHB profiles

ZQ8W;

2. Configure a new PHB profile by the given name and ID

ZQ8V:CR:1:”PHB-PROFILE-1”:AF1:15,40,80,30,6,1;

3. Interrogate the newly created PHB profile by the name

ZQ8W:NAME=”PHB-PROFILE-1”;

12.3 Configuring and interrogating IP interface QoSparameters

Purpose

You can configure the QoS parameters for IP interface by using thecommands of the Q8 MML command group. This group of commandsprovides the operation for configuration, interrogation and deletion. Thesecommands are only for NPGE/NPS1 units.

Before you start

If you want to configure the IP interface (type=IFAE) QoS parameter onNPS1 unit, you have to create the IP over ATM interface first. For details,refer to chapter Creating and modifying internal IP over ATM interfacesand Creating and modifying external IP over ATM interfaces.

Steps

1. Configure the IP interface QoS parameters (Q8S)

You can create a DiffServ configuration for IP interface. Theconfigurable parameters are DiffServ Enable/Disable status andDSPM profile ID/name.

DiffServ Disable for IP interface means that all the traffic to orfrom the interface is treated as BE traffic and if the disable status isset, it is not allowed to configure the profile ID.

For Loopback interface, only DSPM profile can be configured, butnot PHB profile.

DN02143138Issue 13-0 en30/01/2009



Note

If the configuration is related to VLAN priority change, NPGE(P)/NPS1unit restart is needed.

ZQ8S:<UNIT>,<INDEX>:<IP INTERFACE NAME>:[<ENABLED/DISABLED>]:[<ID1=DSPM PROFILE ID>/<NAME=”DSPMPROFILE NAME”>]:[<ID2=PHB PROFILE ID>/<NAME2=”PHBPROFILE NAME”>];

2. Interrogate the IP interface QoS parameters (Q8T)

You can interrogate the IP interface DiffServ configurations.

ZQ8T:[<UNIT>],[<INDEX>]:[<IP INTERFACE NAME>]:[<ID1=DSPM PROFILE ID>/<NAME=”DSPM PROFILE NAME”>]:[<ID2=PHB PROFILE ID>/<NAME2=”PHB PROFILE NAME”>];

3. Delete the IP interface QoS parameters (Q8U)

You can delete all the DiffServ configurations of the IP interface.After the QoS parameters was removed, the QoS state of that IPinterface is disabled.

ZQ8U:<UNIT>,[<INDEX>]:<IP INTERFACE NAME>;

Example Configuring IP interface QoS parameters

Configure the IFGE interface in NPGE with the configured DSPM profile.

1. Interrogate the current configured QoS parameters

ZQ8L;

2. Configure a new IP interface QoS by the given ID

ZQ8S:NPGE,0:IFGE0:ENA:ID1=2:ID2=3;

3. Removed the configured interface QoS

ZQ8U:NPGE,0:IFGE0;


30/01/2009


13 IP based route configurationPurpose

This procedure provides instructions on how to configure multiple isolatedIP networks in RNC. This means separating IP interfaces into several sub-networks, which makes it possible to isolate different IP domains fromeach other.

This can be carried out by configuring IP based route on the IP interface ofNPGE(P) or NPS1(P).

Before you start

Multiple isolated IP networks are configured by creating the needednumber of IP-based routes and attaching them to IP addresses. IP-basedroute is created with QRU command, and it is attached to IP addresses withQRC command.

Steps

1. Create IP-based route (QRU)

Use the QRU command to create an IP-based route. Bandwidth canbe specified for the IP-based route. This command is also used tomodify and delete a configured IP-based route.

ZQRU:<action mode>:<IP-based route id>,<IP-basedroute name>:[ip_based_route_bandwidth]:[commmitted_bandwidth]:[commmitted_signal_bandwidth]:[commmitted_dcn_bandwidth]:[ifc_option],[ifc_ratio];

If the 'commmitted_bandwith', 'committed_signal_bandwidth' and'commmitted_dcn_bandwidth' are all zero, it means no CAC is donein this IP based route. In the ADD mod, the'ip_based_route_bandwidth', 'commmitted_bandwith',

DN02143138Issue 13-0 en30/01/2009


IP based route configuration

'committed_signal_bandwidth' and ‘commmitted_dcn_bandwidth’are all obligatory and have no default value. When the 'ifc_option' isON, it means there is flow control for this IP based route. In the MODmode, the 'ifc_option' can not be modified and the 'ifc_ratio' can bemodified when original 'ifc_option' is ON.

2. Interrogate the configured IP-based routes (QRL)

The configured IP-based routes can be interrogated with QRLcommand.

ZQRL;

3. Create IP address associated with the IP-based route (QRC)

Use the QRC command to create an IP address associated with theIP-based route.

ZQRC:<unit type>,<unit index>:<interface name>:<IPaddress>:(ID=<IP-based route id> | NAME=<IP-basedroute name>);

Note

The maximum number of IP based route is 600 which can beconfigured in one NPS1/NPGE unit in RN4.0 release.

4. Interrogate the configured associations between IP addressand IP-based route (QRB)

Use the QRB command to interrogate an IP address associated withthe IP-based route.

ZQRB:[<unit type>,<unit index>]:[<interface name>]:[<IP address>];

5. Delete the association between IP address and IP-based route(QRA)

Use the QRA command to delete an IP address associated with theIP-based route.


30/01/2009


ZQRA:<unit type>,<unit index>:<interface name>:<IPaddress>: (ID=<IP-based route id> | NAME=<IP-basedroute name>);

Example

1. Create an IP-based routes

ZQRU:ADD:1,”CHINA”:6000:5000:100:100:ON,40;

2. Create IP addresses associated with the IP-based routes

ZQRC:NPGEP,0:IFGE0:IPV4=10.33.160.4:ID=1;

3. Modify the bandwidth parameters for the IP-based route

ZQRU:MOD:1,”FINLAND”:5000:4000:200:50;

4. Modify the IP ifc ratio for the IP-based route

ZQRU:MOD:1,"CHINA":::::ON,80;

5. Interrogate the IP-based route

ZQRL;

6. Interrogate the configured association between IP address and IP-based route

ZQRB:NPGEP,0:IFGE0:IPV4=10.33.160.4;

7. Delete the association between the IP address and the IP-basedroute

ZQRA:NPGEP,0:IFGE0:IPV4=10.33.160.4:ID=1;

8. Delete the IP-based route

ZQRU:DEL:1;

DN02143138Issue 13-0 en30/01/2009


IP based route configuration


30/01/2009


14 IP configuration files

The configuration files for the IP protocol environment are:

Table 2. 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 13-0 en30/01/2009



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

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.


30/01/2009


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. FTP port can be changed by MML commandand the default value is 21.

For detailed information about SSH, refer to chapter Configuring SSHServer; for detailed information about SFTP, refer to chapter ConfiguringSFTP Server; for general introduction of SSH and SFTP, refer to Secureoperation and maintenance connections.

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.

DN02143138Issue 13-0 en30/01/2009



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.

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.


30/01/2009


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

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

DN02143138Issue 13-0 en30/01/2009



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

Option tag Parameters Description

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.

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

#

#

#


30/01/2009


15 IP connection configurationtroubleshooting

15.1 Connection to IP application from remote host 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

DN02143138Issue 13-0 en30/01/2009


IP connection configuration troubleshooting

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

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 check the status of upper-layer (TCP/UDP) communcation and IP application. The possibleproblems 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


30/01/2009


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

. Connection closed by IP application

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

DN02143138Issue 13-0 en30/01/2009



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

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.


30/01/2009


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 13-0 en30/01/2009



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 Siemens Networks CustomerService.

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.


30/01/2009


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.

15.2 NP2GE connectivity lost

Description

NP2GE connectivity lost will cause call drop. The reasons for connectivitylost can be:

1. Something is wrong with the cable.

2. Something is wrong with the routing and network configuration.

If an Ethernet link in the NP2GE unit fails, the system sets off an alarm.The alarm description shows the cause for the failure and instructions onhow to proceed.

If no alarm is given for ethernet interface faulty, the failure may be due tothe state of routes or network configurations.

In general, if something goes wrong or is not working well in the networkelement, first check the active alarms. See Alarm system in AlarmAdministration for more information on alarms.

Symptoms

The symptom is NP2GE connectivity lost. It can be that traffic pathbetween NP2GE and external IP network failed.

NPGEP-3

IP NetworkHSRP/VRRP

WO

NPGEP-2

DSP

TPG/DMPG

SP

2nd redundantunit pair

MXU SFU

TPG/DMPG

DSP

DN02143138Issue 13-0 en30/01/2009



The fault may be either with the cable or with the network configuration.

In case of faulty cables, when an Ethernet link fails, the system sets theEthernet interface to "Not running" state and sets off an alarm.

For a non-redundant NP2GE, the system sets off a two-star alarm if thereare Ethernet interfaces still running. The traffic is re-routed evenly throughthe remaining running interfaces. If there are no running interfaces in theunit, the system sets off a three-star alarm. No traffic goes through the unitas long as the alarm is active.

For a redundant NP2GE the system always sets off a two-star alarm. If thelink fails in the active unit, the system makes a unit switchover and routesthe traffic through the new active unit. The system also sets the failed unitto TE state and starts unit diagnostics. If the diagnostics recognise afailure in the Ethernet interface hardware block it sets the unit to SE state.If the diagnostics do not find any faults, the error is in the external LAN. Inthat case, the system sets the unit back to SP state. As a result, the unitcannot become active and start transferring traffic as long as the alarm isactive, even if the current active unit failed.

Recoveryprocedures

Checking if there is an alarm ETHERNET INTERFACE FAULTY

Purpose

Check if there are alarms of NP2GE which indicate a fault in NP2GEconnectivity.

Steps

1. If there is an alarm ETHERNET INTERFACE FAULTY (3239),which indicates a problem in ethernet interface, check thecabling.

2. If there is an alarm COULD NOT CREATE HWFORWARDINGENTRY (3242) , which indicates that a route or an interfaceaddress cannot be created in network processor, check therouting configuration for NP2GE unit and check the network.


30/01/2009


Checking the cabling

Steps

1. Check that the cabling for the NP2GE is correct

For more information, see Cable Lists in Site documentation.

Expected outcome

The cabling is correct. Continue checking the routing configuration.

Unexpected outcome

Cabling is incorrect. Correct the cabling. If problems persists,continue checking the routing configuration.

Checking the address configuration for NP2GE unit

Purpose

Check if the interfaces and addresses of the NP2GE are configuredcorrectly.

Steps

1. Check the state of interfaces and addresses. Check the interfaces and addresses configuration.

For IPv4

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

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

. Check the state interfaces and addresses in the networkprocessor.

ZQRS:<unit type>,<unit index>:NPC,IF;

Expected outcome

The interfaces and addresses in the network processor are consistent withthe configuration.

Unexpected outcome

If the interfaces and addresses are not consistent, reconfigure theinterfaces and addresses.

DN02143138Issue 13-0 en30/01/2009



Checking the routing configuration for NP2GE unit

Purpose

Check if the static routes of the NP2GE are in correct state.

Steps

1. Check the state of static routes. Check the static routes configuration

For IPv4

ZQKB:[<unite type>,[<unite index>]]:[<destination IP address>,<netmask length>]:[<gateway IP address>]:[<route type>]:[<displaylevel ALL|ACTIVE>];

. Check the state of static routes in network processor

ZQRS:<unite type>,<unite index>:NPC,ROU;

Expected outcome

All static routes in network processor are in active (running) stateand consistent with the configuration.

Unexpected outcome

The static routes are in pending (P) state, or not consistent with theconfiguration.

Checking the network configuration

Steps

1. Check the configuration of the site router

For more information, see the Site router documentation.

2. Check IP parameters

With this command you can interrogate the following informationabout the IP parameters of a computer unit:

IPv4 parameters:. if the IP stack forwards the unicast IPv4 packets which do not

belong to it (IP forwarding flag). the time-to-live (hop count) for an IPv4 packet sourced by the

system


30/01/2009


. the subnets considered to be local addresses

. the name of the host computer

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

15.3 IP configuration files are corrupted

Description

The configuration files for the IP protocol environment rarely need to bemodified manually, but if necessary, it can be modified by using an internalor external text editor for modifications.

Note

Be careful when editing the configuration files manually.

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

Symptoms

The IP configuration files are corrupted and the related content displayedby MML command is out of order.

Recoveryprocedures

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

DN02143138Issue 13-0 en30/01/2009



ZQRF:<file name>;

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

Example Propagating hosts file

ZQRF:"/etc/hosts";


30/01/2009


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 13-0 en30/01/2009


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




Configuring IP parameters and addresses of interfaces


30/01/2009


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 13-0 en30/01/2009


Related Topics

Connecting to O&M backbone via ATM interfaceson OMU

Instructions





Connecting to O&M backbone via ATM interfaceson NPS1(P)

Instructions






Instructions

IP connection configuration for RNC


30/01/2009


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

Instructions


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

Instructions


Configuring IP for Iu-PS user plane with GTPU

Instructions


Configuring IP for Iu-PS user plane with NPS1(P)

Instructions


DN02143138Issue 13-0 en30/01/2009


Related Topics

Configuring IP for user plane with NPGE(P)

Instructions



Descriptions

IP configuration for Iu-BC interface


Instructions


Creating and modifying VLAN interfaces

Instructions


Configuring IP parameters and addresses ofinterfaces

Instructions



30/01/2009


IP configuration files are corrupted

Descriptions


DN02143138Issue 13-0 en30/01/2009


Related Topics

Documents

Configuring IP Connection for RNC