IP Connection Configuration for
RNC
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
1 (145)
IP Connection Configuration for RNC
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted in
any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given “as is” and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT
NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners,
and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2008. All rights reserved.
2 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Contents
Contents
Contents 3
Summary of changes 5
1
1.1
1.2
1.3
1.4
Overview of IP connection configuration 11
IP connection configuration for RNC O&M 11
OMS TCP/IP network 13
IP configuration for Iu-PS interface 16
IP configuration for Iu-BC interface 19
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.8.1
2.8.2
2.8.3
2.8.4
2.8.5
2.8.6
2.8.7
2.8.8
2.9
2.10
Configuring IP for O&M backbone (RNC-NetAct) 21
Configuring IP for O&M backbone (RNC — NetAct) 21
Creating MMI user profiles and user IDs for remote connections to
NetAct 24
Configuring IP stack in OMU 25
Creating OSPF configuration for O&M connection to NetAct 29
Configuring static routes for the O&M connection to NetAct 35
Configuring ESA12 37
Configuring ESA24 39
Configuring OMS for DCN 43
Configuring OMS for DCN 43
Checking the calendar time in OMS 47
Configuring the DHCP server in OMS 48
Configuring the DNS client in OMS 49
Configuring OMS to RNC 50
Configuring NTP services in OMS 53
Configuring OMS system identifier 55
Configuring IP addresses for OMS 56
Connecting to O&M backbone via Ethernet 58
Connecting to O&M backbone via ATM interfaces 59
3
Configuring IP for BTS O&M (RNC-BTS/AXC)
4
Configuring IP for Iu-PS User Plane (RNC-SGSN)
5
Configuring Signalling Transport over IP for Control Plane 87
6
Configuring IP for Iu-BC (RNC-CBC) 89
7
Creating and modifying DNS configuration 95
8
Creating and modifying IP interfaces 99
9
Modifying IP parameters 105
10
Creating and modifying IP over ATM interfaces 109
11
Modifying OSPF configuration 113
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
61
67
3 (145)
IP Connection Configuration for RNC
12
Creating and modifying static routes 117
13
Creating and modifying IP QoS configuration 121
14
14.1
14.2
IP configuration files 125
IP configuration files 125
Modifying IP configuration files
15
Connection to IP application from remote host fails 133
130
Related Topics 141
4 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest
document issue contains all changes made to previous issues.
Changes between issues 11-2 and 11-3
Configuring IP for Iu-PS User Plane (RNC-SGSN)
Added the introduction of GTPU selection principle and the related
examples.
Added one example "IP configuration for Iu-PS with GTPUs connected to
different SGSNs".
Changes between issues 11-1 and 11-2
Configuring IP for Iu-PS User Plane (RNC-SGSN)
"QMF" MML command was updated.
Changes between issues 11-0 and 11-1
IP connection configuration for RNC O&M
.
In the figure information on NEMU has been replaced with
corresponding 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
DN02143138
Issue 11-3 en
.
Title changed
.
In 'Purpose' section information on NEMU has been replaced with
OMS.
# Nokia Siemens Networks
5 (145)
IP Connection Configuration for RNC
.
In Figures information on NEMU has been replaced with
corresponding 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 been
added.
.
In step 3, the first chapter has been modified and information about
IPSec added.
Configuring IP for O&M backbone (RNC — NetAct)
.
In 'Purpose' section information on NEMU has been replaced with
OMS.
.
In 'Before you start' section NEMU has been replaced with OMS.
.
In Figure information on NEMU has been replaced with
corresponding information on OMS.
.
In NOTE under Figure NEMU has been replaced with OMS.
.
In Step 5. NEMU has been replaced with OMS. Also replaced in link.
Creating MMI user profiles and user IDs for remote connections to NetAct
.
In 'Purpose' section information on NEMU has been replaced with
corresponding information on OMS.
.
In Step 2-3. NEMU has been replaced with OMS.
.
In Example 1. NEMU has been replaced with OMS. NEMU
commands have been replaced with OMS commands.
Configuring IP stack in OMU
.
Original step 4 about "Modify interface priority" was deleted.
.
A note about redundant ESA24 configuration has been added.
Creating OSPF configuration for O&M connection to NetAct
6 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Summary of changes
.
In Figure information on NEMU has been replaced with
corresponding 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
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 with
corresponding 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.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
7 (145)
IP Connection Configuration for RNC
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.
Configuring IP stack in OMU
Syntax of "Q6" and "QRN" commands are modified.
Creating OSPF configuration for O&M connection to NetAct
Example of "OSPF configuration for RNC", step 1 and step 5 are modified.
Configuring static routes for O&M connection to NetAct
.
Content of purpose is modified.
.
Syntax of "QKC" command is modified.
Connecting to O&M backbone via ATM interfaces
.
Title is changed from "Configuring IP over ATM interfaces".
.
Note "The destination of IP address ..." is added and steps are
arranged.
.
Sytax of "Q6N" command is modified.
Configuring IP for BTS O&M (RNC-BTS/AXC)
Syntax "QKC" command is modified.
Configuring IP for Iu-PS User Plane (RNC-SGSN)
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)
8 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Summary of changes
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 ATM
interfaces" 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 modifying
IPQoS configuration.
IP configuration files
Content about "DiffServ codepoint configuration data" is deleted from table
of "configuration files in the IP protocol environment" and the relevant
contents in this chapter are also deleted.
Modifying IP configuration files
Steps are rearranged and modified.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
9 (145)
IP Connection Configuration for RNC
10 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Overview of IP connection configuration
1
Overview of IP connection configuration
1.1
IP connection configuration for RNC O&M
Purpose
It is important to plan the network carefully before starting the
configuration. The network administrator has to plan and maintain a
coherent view of the network and its components in order to make it
continuously work smoothly and reliably. Issues to be considered are the
network structure, hardware needed, and security issues.
In RNC, IP connections are used for O&M traffic towards backbone or
base station (BTS) and for user plane and control plane traffic towards the
Serving GPRS Support Node (SGSN), the Cell Broadcast Center (CBC),
and the Standalone SMLC (SAS).
IPv6 is not in use for O&M connections.
The following figure shows an example of IP configuration for O&M
network of RNC.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
11 (145)
IP Connection Configuration for RNC
NetAct
O&M
backbone
10.3.1.1/24
IP over ATM
virtual
connection
RAN O&M backbone address range
10.0.0.0/14
OSPF Area 0
Computer
with
Element Manager
10.3.2.1/24
10.1.1.1/28
MGW
10.1.1.10/28
10.1.1.5/28
ESA12/ESA24
10.1.1.9/28
OMS
(10.1.1.4/28)
(10.1.1.3/28)
AA255 10.3.2.2/32
10.1.1.2/28 (logical)
OMU
AA0 10.3.1.2/32
RNC LAN
10.1.1.0/28
10.1.1.2/32
10.1.1.2/32
RNC
unnumbered lines
RAN BTS sites
address range
10.1.3.0
Figure 1.
RAN BTS sites
address range
10.1.2.0
Example of IP configuration for RNC O&M network
For more information on data communication networks (DCN), see Data
communication network for operation and maintenance in the Nokia
WCDMA RAN System Information Set.
12 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Overview of IP connection configuration
Steps
1.
Plan DHCP addresses
Assign a range of IP addresses to DHCP. The client computers on
the local area network (LAN) request the IP address from the DHCP
server.
2.
Draw a map of your network
The easiest way to plan your network and determine the naming is to
draw a map of the network. The map should contain at least the
following:
.
Existing networks, network elements, routers, and remote
hosts which are going to be connected.
.
Those units of the network element which have the IP stack.
.
The IP addresses, subnetwork structure, host names, and the
domain name.
.
The names for the servers.
3.
Plan IP routing and OSPF areas
There are no specified guidelines for the number of routers in an
area or the number of the neighbours per segment or what is the
best way to plan a network. The following list gives you some
subjects which you should consider when planning the network:
.
the number of routers per area
.
the number of neighbours
.
the number of areas per Area Border Routers
.
the number of sub areas
1.2
OMS TCP/IP network
Purpose
OMS has to be physically connected to the managed network element and
external networks. The connections are done through ESA12 or ESA24
Ethernet switch. The compact OMS has redundant Ethernet interfaces,
which have to be connected to the ESA12/ESA24 switch. The Ethernet
interfaces of the RNC are also connected to the same ESA12/ESA24
switch.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
13 (145)
IP Connection Configuration for RNC
The local network also has to be connected to the DCN network that
enables the connections towards Nokia NetAct and other external
systems.
In RNC there are two main DCN connectivity alternatives for the
connection between OMS and NetAct, IP over ATM connectivity and
Ethernet connectivity.
If IP over ATM connectivity is used, OMS uses OMU unit as its default IP
router. OMU unit routes the IP traffic between OMS and NetAct using ATM
virtual circuits and IP over ATM. The connection between OMS and OMU
is always Ethernet.
The following figure describes the IP over ATM based connectivity
alternative on general level.
RNC
OMS
ESA12/ESA24
NetAct
Figure 2.
ATM SW
OMU
IP over ATM based connectivity between OMS and NetAct
If Ethernet connectivity is used, OMS uses an external IP router as its
default router. The IP router routes the IP traffic between OMS and NetAct
over the LAN/WAN IP network. The connection between OMS and the
external IP router is always Ethernet and the LAN/WAN network can be
any type of IP network, for instance Ethernet, ATM or SDH network.
The following figure describes the Ethernet based connectivity alternative
on general level.
It is possible to add high level of redundancy to the RNC’s Ethernet
network by installing an optional redundant ESA24 switch. It should be
noted that it is allowed to add the redundant ESA24, if the existing switch is
ESA24. If ESA12 switch exists, it must be replaced by ESA24. When
redundant ESA24 exists, OMS and OMU will be physically connected to
both ESA24 switches, as shown in figure 7.
14 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Overview of IP connection configuration
RNC
OMS
ESA12/ESA24
IP Router LAN/WAN
NetAct
OMU
Figure 3.
Ethernet based connectivity between OMS and NetAct
RNC
OMS
ESA24
IP Router LAN/WAN
OMU
Figure 4.
NetAct
ESA24
Ethernet based connectivity between OMS and NetAct, with
redundant 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 the
same subnetwork as the other addresses in the same physical
network.
a.
Make a drawing of the RNC subnetwork. Include all the units,
routers and switches that need data communications
connections.
b.
Define the address space for the subnetwork.
c.
Select addresses for the IP interfaces of the devices in the
network.
3.
DN02143138
Issue 11-3 en
Plan the network security for OMS
# Nokia Siemens Networks
15 (145)
IP Connection Configuration for RNC
Security aspects should be taken into consideration when planning
the TCP/IP network for OMS. In other words, the transport network
between the RNC and the NetAct should be a part of a trusted
private intranet. If some external insecure networks are used as
transport networks, you should be aware of the TCP/IP security
issues.
It is possible to add strong network-level security to communication
between RNC and NetAct by using optional IP Security (IPSec)
feature. IPSec can be used in both OMS and OMU unit to encrypt
and integrity-protect all or only selected traffic between RNC and
NetAct. For more information about IPSec, refer to document
RAN33: IP Security for O&M Traffic Between RNC and NetAct,
Feature Activation Manual.
There are username/password mechanisms for application level
connections to OMS.
1.3
IP configuration for Iu-PS interface
Purpose
The Iu-PS interface connects the RNC and the Serving GPRS Support
Node (SGSN). The IP connection is used for user plane and control plane
traffic.
Before you start
For more information on the Iu-PS interface, see Iu interface specification
in the Nokia WCDMA RAN System Information Set in NOLS.
Summary
In Iu-PS interface, the traffic goes through NIS1 and GTPU units. In GTPU
units, all users and packets are treated equally regardless of the service,
Quality of Service (QoS) requirement, and packet size. However, you can
dedicate two or more GTPUs to serve only real-time IP traffic between the
RNC and the SGSN. Dedication is done by configuring IP over 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 a separate real-time
optimised Iu-PS PVC (CBR or rt-VBR) for Packet Switched Radio Access
Bearers (RABs) between the GTPU and the SGSN and a separate internal
real-time optimised VCC between the GTPU and the DMCU. Another
solution is to use layer-two segregation functionality of GTPU. By this
solution, you can use two VCCs under one IPoA interface of GTPU. One of
these two VCCs is dedicated to real-time IP traffic.
16 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Overview of IP connection configuration
It is also possible to configure QoS DiffServ traffic classification to GTPU
units. You can prioritise the throughput real time (rt) traffic rather than nonreal time (nrt) traffic in the GTPU TCP/IP stack. Such configuration is done
with MML command Q8. For more detailed instructions, refer to Creating
and modifying IP QoS configuration.
Note
If you want to dedicate a GTPU for real-time IP traffic, configure the
usage of all IP over ATM interfaces of the unit as IPOART.
If you want to use layer-two segregation functionality, configure two
VCCs to one IPoA interface, configure the usage of one VCC as
IPOART and the other VCC's usage as IPOAUD.
The following figures show the difference between non-dedicated and
dedicated GTPUs.
Non-dedicated VCCs
GTPU
GTPU
SFU
MXU
GTPU
SGSN
GTPU
GTPU
Figure 5.
DN02143138
Issue 11-3 en
All GTPUs used for real-time and non-real time traffic
# Nokia Siemens Networks
17 (145)
IP Connection Configuration for RNC
GTPU
NRT-VCCs
GTPU
SFU
MXU
GTPU
GTPU
SGSN
RT-VCCs
GTPU
Figure 6.
Certain GTPUs dedicated for real-time IP traffic
GTPU
GTPU
SFU
MXU
GTPU
SGSN
GTPU
GTPU
NRT_VCC
RT_VCC
Figure 7.
18 (145)
Dedicate VCC for real-time IP traffic (Layer-two segregation solution)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Overview of IP connection configuration
Note
If you decide to dedicate some GTPUs for real-time traffic, configure at
least 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-time
traffic, see the Feature Activation Manual for Dedicated GTPU for RT PS
Support.
Steps
1.
Draw a map of your network
The easiest way to plan your network and determine the naming is to
draw a map of the network. The map should contain at least the
following:
.
Existing networks, network elements, routers, and remote
hosts which are going to be connected.
.
Those units of the network element which have the IP stack.
.
The IP addresses, subnetwork structure, host names, and the
domain name.
.
The names for the servers.
2.
Plan routing
You can use either static routes or OSPF for routing. If you use only
static routes, see the examples in Configuring IP for Iu-PS User
Plane (RNC — SGSN) for instructions on how to create redundancy
for the Iu-PS interface.
1.4
IP configuration for Iu-BC interface
The Iu-BC interface is the logical interface between a radio network
controller (RNC) in the radio access network (RAN) and a cell broadcast
centre (CBC) in the core network.
The Iu-BC is one instance of an Iu interface and is used for cell broadcast
services.For more information on the Iu-BC interface, see Iu interface
specification in the Nokia WCDMA RAN System Information Set.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
19 (145)
IP Connection Configuration for RNC
All user data and signalling (SABP) traffic goes through the same ICSU
units. You need to select only one working ICSU unit (WO-EX) as active
one and configure IP address, IPoA VCC and static route on it. For more
information, see Configuring IP for Iu-BC (RNC-CBC).
20 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
2
2.1
Configuring IP for O&M backbone (RNCNetAct)
Configuring IP for O&M backbone (RNC — NetAct)
Purpose
This chapter shows the procedure to configure the Operation and
Maintenance Server (OMS), ESA12/ESA24 Ethernet switch and the
Operation and Maintenance Unit (OMU) for the data communication
network (DCN). After this, you can use the Element Manager to manage
the RNC remotely.
The O&M backbone can be configured either via Ethernet or via ATM
virtual connections, or via both.
Note
You can improve the redundancy of the RNC Ethernet network by
installing a redundant ESA24 Ethernet switch and redundant Ethernet
cabling.
Before you start
Check that:
DN02143138
Issue 11-3 en
.
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
# Nokia Siemens Networks
21 (145)
IP Connection Configuration for RNC
.
.
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 is
also required. Usually, this interface is Iu-CS.
Computer
with
Element Manager
192.168.1.10/28
192.168.1.5/28
ESA12/ESA24
192.168.1.9/28
OMU
OMS
192.168.1.1/28 (logical)
RNC LAN
192.168.1.0/28
RNC
Figure 8.
Preconfigured settings for O&M network
Note
The default gateway in OMS and ESA12/ESA24 is 192.168.1.1.
Steps
1.
Create MMI user profiles and user IDs for remote connection to
NetAct
See Creating MMI user profiles and user IDs for remote connections
to NetAct for detailed instructions.
2.
22 (145)
Configure IP stack in OMU
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
See instructions in Configuring IP stack in OMU.
3.
Configure IP routing
There are two ways to configure routing information:
.
by creating OSPF configuration
See instructions in Creating OSPF configuration for O&M
connection to NetAct.
.
by configuring static routes
See instructions in Configuring static routes for O&M
connection to NetAct.
4.
Configure the Ethernet/LAN switch
Configure the Ethernet (LAN) switch according to instructions in
Configuring ESA12 or Configuring ESA24, depending on which one
you have in your configuration.
5.
Configure OMS
Configure OMS according to instructions in Configuring OMS for
DCN.
6.
Configure external IP connections
Configure the connection to NetAct for O&M traffic. There are two
ways to connect the RNC to NetAct:
.
by configuring the O&M backbone via Ethernet
Refer to instructions in Connecting to O&M backbone via
Ethernet.
.
by configuring the O&M backbone via ATM virtual connections
Refer to instructions in Connecting to the O&M backbone via
ATM interfaces.
The recommended way of connecting RNC to NetAct is via Ethernet.
The connection via ATM should only be used as a backup. O&M
connections can be configured to use both ways.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
23 (145)
IP Connection Configuration for RNC
2.2
Creating MMI user profiles and user IDs for remote
connections to NetAct
Purpose
To enable remote connections from the NetAct to the RNC, you need to
create users NUPADM and NEMUAD and their profiles in the RNC. NetAct
application (service user management) accesses RNC with NUPADM
profile. NUPADM profile is mandatory to create other service users in
NetAct application. NEMUAD profile is created to enable communication
between OMS and OMU. For example, without NEMUAD profile, PM data
cannot be transferred to OMS and therefore affects the transfer
measurement to NetAct.
See the example below for detailed instructions.
Before you start
If you do not know the password, contact your NetAct administrator.
Steps
1.
Establish a telnet connection to RNC OMU
Enter the preconfigured IP address to OMU (the default IP address
is 192.168.1.1):
telnet <IP address of OMU>
2.
Create new MMI user profiles
Create the user profiles for NUPADM and NEMUAD. Refer to
Creating MMI user profiles in Information Security for details.
3.
Create new MMI user IDs
Create the NUPADM and NEMUAD user IDs. Refer to Creating MMI
user IDs in Information Security for details.
Example
Creating MMI user profiles and user IDs in the RNC
This example shows how to create the NUPADM and NEMUAD MMI
profiles and user IDs in the RNC.
24 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
1.
Create the user profiles.
ZIAA:NUPADM:ALL=250:VTIME=FOREVER,UNIQUE=YES;
ZIAA:NEMUAD:ALL=250:VTIME=FOREVER,UNIQUE=YES::
FTP=W;
2.
Create the user IDs.
ZIAH:NUPADM:NUPADM;
ZIAH:NEMUAD:NEMUAD;
When creating a new user ID, the system prompts you for a
password. The password created here is used for communication
between the OMS or the NetAct and the RNC. The system displays
the following output:
/* IDENTIFY PASSWORD:
MINIMUM PASSWORD LENGTH IS 6
MAXIMUM PASSWORD LENGTH IS 16 */
NEW PASSWORD:********
VERIFICATION:********
COMMAND EXECUTED
Enter the same password as used in the OMS and the NetAct.
2.3
Configuring IP stack in OMU
Purpose
The purpose of this procedure is to configure OMU for data communication
network (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 the
configuration.
For IPv6:
You can use the Q6J, Q6H, Q6I, and Q6S commands to interrogate the
configuration.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
25 (145)
IP Connection Configuration for RNC
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 DNS
server>],[<third DNS server>],[<local domain name>],
[<sortlist>],[<netmask>]:[<resolver cache>],
[<round robin>];
For IPv6:
ZQ6K:[<primary DNS server>],[<secondary DNS
server>],[<third DNS server>],[<local domain name>],
[<network sortlist>],[<prefix length>]:[<resolver
cache>],[<round robin>];
2.
Modify TCP/IP parameters
Set host names, define if the OMU forwards IP packets, set the
maximum time-to-live value and define if the subnets are considered
to be local addresses in both OMU units.
For IPv4:
ZQRT:<unit type>, <unit index>:([HOST=<host name>],
[IPF=<IP forwarding>],[TTL=<IP TTL>],[SNL=<subnets
are local>]);
For IPv6:
ZQ6T:<unit type>,<unit index>:([IPF=<IP
forwarding>],[HLIM=<hoplimit>],[RADV=<router
advertisement>]);
3.
Add a new logical IP address
Assign the IP address to both OMU units by QRN for IPv4 and Q6N
for IPv6.
26 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
ZQRN:OMU:<interface name>,[<point to point interface
type>]:[<IP address>],[<IP address type> ]:[<netmask
length>]:[<destination IP address>]:[<MTU>]:
[<state>];
ZQ6N:OMU:<interface name>,[<point to point interface
type>]:[<IP address>],[<address type>]:[<prefix
length>]:[<destination IP address>];
4.
Configure IP routing
There are two ways to configure routing information:
.
by creating OSPF configuration
Refer to instructions in Creating OSPF configuration for O&M
connection to NetAct.
.
by configuring static routes
Refer to instructions in Configuring static routes for O&M
connection to NetAct.
5.
Remove the preconfigured IP address
Remove the preconfigured IP address from both OMU units by QRG
command for IPv4, by Q6G command for IPv6.
ZQRG:OMU,<unit index>:<interface name...>,:<IP
address>;
ZQ6G:OMU,<unit index>:<interface name>:<IP
address>:;
Note
Interface name can be a specific one or a range, for example: AA0 to
AA10.
If the unit index for 2N type logical IP address is specified, the logical
addresses will be deleted both from WO and SP unit.
Example
Configuring IPv4 stack in OMU
This example shows how to configure the IPv4 stack in OMU for DCN.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
27 (145)
IP Connection Configuration for RNC
1.
Configure DNS parameter data. The IPV4 address of the primary
DNS server is 10.1.1.5 and the local domain name RNC1.NETACT.
OPERATOR.COM.
ZQRK:10.1.1.5,,,"RNC1.NETACT.OPERATOR.COM";
2.
Modify IPv4 parameters for both OMU units separately. Set the host
name to OMU, set IP forwarding on, and specify that subnets are not
local.
ZQRT:OMU,0:HOST="OMU",IPF=YES,SNL=NO;
ZQRT:OMU,1:HOST="OMU",IPF=YES,SNL=NO;
3.
Add a new logical IPv4 address (10.1.1.2) to the OMU units. The
interface name is EL0 and the netmask is length 28.
ZQRN:OMU:EL0:10.1.1.2,L:28:::UP;
If the optional redundant ESA24 switch has been installed, the
following example command is used instead. In that case, the logical
IP address (10.1.1.2) is added to both EL0 and EL1 interfaces at the
same time.
ZQRN:OMU:EL0&&EL1:10.1.1.2,L:28:::UP;
4.
Configure IPv4 routing. For examples, see Creating OSPF
configuration for O&M connection to NetAct and Configuring static
routes for O&M connection to NetAct.
5.
Remove the preconfigured IPv4 address (198.168.1.1) from both
OMU units.
ZQRG:OMU,0:EL0:192.168.1.1;
Example
Configuring IPv6 stack in OMU
This example shows how to configure the IPv6 stack in OMU for DCN.
1.
Configure DNS parameter data. The IPv6 address of the primary
DNS server is 3FEE::1 and the local domain name RNC1.NETACT.
OPERATOR.COM.
ZQ6K:"3FEE::1",,,"RNC1.NETACT.OPERATOR.COM";
2.
Modify IPv6 parameters for both OMU units separately. Set the host
name to OMU, set IP forwarding on, set hoplimit value as 70, and set
router advertisement OFF.
ZQ6T:OMU,0:IPF=ON,HLIM=70,RADV=OFF;
ZQ6T:OMU,1:IPF=ON,HLIM=70,RADV=OFF;
28 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
3.
Add a new logical IPv6 address (3FFE:1200:3012:C020:380:6FFF:
FE5A:5BB7) to the OMU units. The interface name is EL0 and the
netmask is length 20.
ZQ6N:OMU,0:EL0:"3FFE:1200:3012:C020:380:6FFF:
FE5A:5BB7",L:20;
4.
Remove the preconfigured IPv6 address (3FEE::1) from both OMU
units.
ZQ6G:OMU,0:EL0:"3FEE::1":;
2.4
Creating OSPF configuration for O&M connection
to 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 ATM
virtual connection, the IP over ATM interface for OMU must be created
before OSPF is configured. Refer to instructions in Connecting to O&M
backbone via ATM interfaces.
You must remove the existing default routes before creating the OSPF
configuration. If the default routes are not removed, the RNC might
advertise itself, incorrectly, as an alternative default route to other routers.
For instructions on how to remove default routes, see Configuring static
routes for O&M connection to NetAct.
Steps
1.
Configure OSPF router parameters (QKS)
If the OMU units have physical IP addresses in addition to a logical
IP address, the OMU units must have a different router ID. Give the
physical address of the OMU unit as the value for the router ID
parameter, to avoid having two routers with the same router ID, in
the network.
ZQKS:<unit type>,<unit index>:[MOD|DEL],<router
id>:<rfc1583compatibility>:<spf delay>:<spf hold
time>;
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
29 (145)
IP Connection Configuration for RNC
2.
Configure OSPF area parameters (QKE)
Define the OSPF area (both backbone and other area) parameters
of an OSPF router.
ZQKE:<unit type>,<unit index>:<area
identification>:<stub area>,[<stub area route
cost>],<totally stubby area>;
The area identification specifies the area ID for a new OSPF. The
area ID is entered as a dotted-quad. The area ID of 0.0.0.0 is
reserved for the backbone. The IP network number of a subnetted
network may be used as the area ID.
Note
The area parameters do not become effective (written into the
configuration file) until the area has been attached to an interface.
3.
Interrogate IP interfaces (QRI)
You must know the “interface identification” of the network interfaces
when you are configuring OSPF interfaces.
ZQRI:<unit type>,<unit index>:<interface name>:
<display mode>;
If you do not give any parameter values, network interface
information of all computer units of the network element is listed.
4.
Configure OSPF interfaces (QKF)
ZQKF:<unit type>,<unit index> :<interface
specification>:<area identification>:[<hello
interval>]:[<router dead interval>]:[<ospf cost>]:<
[election priority>]:[<passive>]:[<authentication>
| <password>];
5.
Configure redistribute parameters (QKU)
Usually static routes to BTSs are redistributed to OSPF by
redistribution configuration.
30 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
ZQKU:<unit type>,<unit index>:<redistribute type and
identification>:<metric>;
6.
Configure network prefix, if required (QKH)
This command defines a network prefix in the OSPF area.
Configuring the network prefix is optional to reduce the routing
information exchange between different areas.
ZQKH:<unit type>,<unit index>:<area
identification>:<operation>:<network prefix>,
<network prefix mask length>:<network prefix
restriction>;
7.
Configure virtual link parameters, if required (QKV)
If there is an OSPF area which does not have a physical connection
to the backbone area, use a virtual link to provide a logical path from
the disconnected area to the backbone area. Virtual links have to be
configured to both ends of the link. The QKV command has to be
entered separately for both border routers using the virtual link.
ZQKV:<unit type>,<unit index>:<router
identification>:<transit area>:<hello interval>:
<router dead interval>:<authentication>;
Example
Creating OSPF configuration for O&M DCN
The following example illustrates OSPF configuration for O&M DCN. The
corresponding IP network interfaces have been configured before this
procedure.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
31 (145)
IP Connection Configuration for RNC
NetAct
O&M
backbone
10.3.1.1/24
IP over ATM
virtual
connection
RAN O&M backbone address range
10.0.0.0/14
OSPF Area 0
Computer
with
Element Manager
10.3.2.1/24
10.1.1.1/28
MGW
10.1.1.10/28
10.1.1.5/28
ESA12/ESA24
10.1.1.9/28
OMS
(10.1.1.4/28)
(10.1.1.3/28)
AA255 10.3.2.2/32
10.1.1.2/28 (logical)
OMU
AA0 10.3.1.2/32
RNC LAN
10.1.1.0/28
10.1.1.2/32
10.1.1.2/32
RNC
unnumbered lines
RAN BTS sites
address range
10.1.3.0
Figure 9.
RAN BTS sites
address range
10.1.2.0
Example of OSPF configuration for RNC
This example presents the configuration of OSPF parameters in the OMU
unit. The OMU unit in RNC is a border router. The unit has three interfaces:
EL0, AA0, and AA255. The EL0 interface is attached to the backbone area
through an Ethernet connection. The AA0 and AA255 interfaces are
attached to the backbone area through an IP over ATM connection.
32 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
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 ID
10.1.1.2 and accept the default values for the remaining parameters.
ZQKS:OMU,0:,10.1.1.2;
ZQKS:OMU,1:,10.1.1.2;
4.
Configure OSPF area parameters.
Configure the backbone area information for the OMU.
ZQKE:OMU,0:0.0.0.0;
ZQKE:OMU,1:0.0.0.0;
5.
Inquire the attached interfaces.
ZQRI:OMU;
The following output is displayed:
IF
UNIT
NAME
------- -----OMU-0
AA0
AA255
EL0
DN02143138
Issue 11-3 en
ADM
IF
ADDR
STATE MTU PRIORITY TYPE TYPE IP ADDRESS
----- ----- ---- ---- ------------UP
1500
L
10.3.1.2/32
->10.3.1.1
UP
1500
L
10.3.2.2/32
->10.3.2.1
UP
1500
L
10.1.1.2/28
# Nokia Siemens Networks
33 (145)
IP Connection Configuration for RNC
OMU-1
AA0
UP
1500
L
AA255
UP
1500
L
EL0
UP
1500
L
6.
(10.3.1.2)/32
->10.3.1.1
(10.3.2.2)/32
->10.3.2.1
(10.1.1.2)/28
Configure OSPF interfaces.
Configure an OSPF interface for the EL0, AA0, and AA255
interfaces.
The EL0 interface is attached to the backbone area through an
Ethernet connection. Accept default values for the hello interval
and router dead interval parameters and set the ospf cost to
10.
ZQKF:OMU,0:EL0:0.0.0.0:::10;
ZQKF:OMU,1:EL0:0.0.0.0:::10;
The AA0 and AA255 interfaces are attached to the backbone area
through an IPoA connection. Set the hello interval to 30, router
dead interval to 120, and ospf cost to 100.
ZQKF:OMU,0:AA0:0.0.0.0:30:120:100;
ZQKF:OMU,1:AA0:0.0.0.0:30:120:100;
ZQKF:OMU,0:AA255:0.0.0.0:30:120:100;
ZQKF:OMU,1:AA255:0.0.0.0:30:120:100;
If an optional redundant ESA24 switch has been installed and the
QRI command printout in step 5 shows that OMU’s EL1 interfaces
are configured with the same IP addresses as the EL0 interfaces,
then the EL1 interfaces are also configured as OSPF interfaces with
the following commands:
ZQKF:OMU,0:EL1:0.0.0.0:::10;
ZQKF:OMU,1:EL1:0.0.0.0:::10;
7.
Configure redistribute parameters.
Configure the OSPF to redistribute all valid static routes.
ZQKU:OMU,0:ST=;
ZQKU:OMU,1:ST=;
34 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
2.5
Configuring static routes for the O&M connection
to NetAct
Purpose
Static routes are used when dynamic routing (OSPF in this case, see
Creating OSPF configuration for O&M connection to NetAct) does not
provide any useful functionality over the static routes. In other words, they
are used when a simple static route works as efficient as a more
complicated dynamic routing. Static routes can be used with dynamic
routing when creating a host route to a host that does not run dynamic
routing.
Static routing is extremely suitable when there is only one connection
(Ethernet or IP over ATM) towards NetAct. When there are two or more
connections towards NetAct, OSPF is the recommended solution.
Redundant static routing is also the alternative. With redundant static
routing, multiple static routes via different gateways in different
preferences can be configured for a same destination. If the primary route
goes down, the backup route will take the duty. For more details about
OSPF solution, see Creating OSPF configuration for O&M connection to
NetAct and refer Creating and modifying static routes for more details
about 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 it
follows 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 default
route.
Note
If you cannot use the default route, see the next step.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
35 (145)
IP Connection Configuration for RNC
ZQKC:<unit type>,<unit index>::<gateway IP address>,
[<local IP address>]:[<route type>]:[<route
preference>];
Note
The parameter local IP address is only valid for local IP address based
default route. For normal static routes, you do not need to give the local
IP address. For more information about local IP address based default
routes, refer to Creating and modifying static routes.
2.
If the default route cannot be used
Then
Delete the default static route for IP configuration
a.
Obtain the number of the static route to be deleted.
ZQKB:<unit type>,<unit index>;
b.
Delete the route by identifying it by its route number or by its
identification.
ZQKA:<route number>;
ZQKA::<unit type>,<unit index>;
3.
If the default route cannot be used and you deleted it, or if you need
to create more routes
Then
Create new static routes (QKC)
You create new static routes by using the QKC command.
ZQKC:<unit type>,<unit index>:<destination IP
address>,[<netmask length>]:<gateway IP address>:
[<route type>]:[<route preference>];
Example
Creating a default static route in RNC OMU
The same default route is used for both OMU-0 and OMU-1.
ZQKC:OMU,0::10.1.1.1,:LOG;
36 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
2.6
Configuring ESA12
Purpose
The purpose of this procedure is to configure the ESA12 Ethernet switch
for O&M DCN.
Steps
1.
Establish a telnet connection to ESA12
a.
Enter the preconfigured IP address to ESA12 (the default IP
address is 192.168.1.9).
telnet <ip address of ESA12>
b.
Enter your login ID and password.
The default password is empty. Therefore, press Enter to
continue. If you have already changed your password during
commissioning, enter your new password.
NOKIA ESA-12.
Username:nokia
Password:********
Expected outcome
The following options are displayed:
ESA12
Main Menu
1. General Configuration
2. SNMP Configuration
3. Ports Configuration
4. Ports Status
5. Load Factory Defaults
6. Software Upgrade
7. Reset
8. Logout
2.
Press 1 to select General Configuration from the menu
The General Configuration menu shows the current settings.
Expected outcome
The General Configuration menu is printed on the command line.
General Configuration
MAC address
1. Agent IP Address
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
00 A0 12 0B 02 74
: 192.168.001.009
37 (145)
IP Connection Configuration for RNC
2.
3.
4.
5.
6.
9.
3.
Agent Netmask
: 255.255.255.240
Default Gateway
: 192.168.001.001
Supervisor/Terminal Password :
System Name
:
Advanced Features
Main Menu
Press the number of the parameter you want to change
Expected outcome
The selected parameter row with the current settings is printed
below the menu.
4.
Use the backspace key to remove the current parameter value
5.
Enter the new value for the parameter and press Enter
Expected outcome
The General Configuration menu is printed on the command line.
The menu shows the new settings.
Expected outcome
The session is interrupted immediately after you change the IP address.
Change the IP address only after having changed all other parameters.
Example
Changing the default gateway in ESA12
This example shows how to change the default gateway in ESA12.
1.
Establish a telnet connection to ESA12. In this example, the
password has not been changed yet.
telnet 192.168.1.9
Username:nokia
Password:
2.
Press 1 to select General Configuration in the main menu.
3.
Press 3 to select Default Gateway. The current address is displayed
on the command line:
Default Gateway : 192.168.1.1
38 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
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
1.
2.
3.
4.
5.
6.
9.
2.7
MAC address
Agent IP Address
:
Agent Netmask
:
Default Gateway
:
Supervisor/Terminal Password :
System Name
:
Advanced Features
Main Menu
00 A0 12 0B 02 74
192.168.001.009
255.255.255.240
10.001.001.002
Configuring ESA24
Purpose
This procedure describes how to configure the ESA24 Ethernet/LAN
switch.
Before you start
Before you start the configuration, check the following:
.
The PC or laptop that you are using is connected to one of the
Ethernet ports of the ESA24 switch with an Ethernet cable.
.
The ESA24 Ethernet switch is powered up (the LED on the front
panel of the switch is green).
Steps
1.
DN02143138
Issue 11-3 en
Connect to the IP address of ESA24 via Telnet
# Nokia Siemens Networks
39 (145)
IP Connection Configuration for RNC
Note
If connection to the IP address of ESA24 is via Telnet, the IP address
will change to the given address by the command IP address X.X.X.
X/x.x and the Telnet connection will stop responding. The initial
configuration has to be done by the serial connection. See ESA24 10/
100 Mbit Ethernet Switch User Guide for the detailed information.
a.
b.
Start a Telnet session by selecting Start -> Run on the
Windows Taskbar.
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 the
password has been changed, and press Enter.
Expected outcome
After successful login, the ESA24 prompt is displayed:
ESA24>
3.
Enable RSTP or MSTP for ESA24, if necessary
If you want to prevent cabling loops, enable the Rapid Spanning
Tree Protocol (RSTP) or the Multiple Spanning Tree Protocol
(MSTP) for ESA24.
a.
Plan the STP role of each LAN switch in the L2 broadcast
domain area.
b.
Check that all LAN switches in the L2 broadcast domain area
are running compatible STP versions.
c.
Configure the bridge priority of the STP root switch and
configure all the links directly connected to computer units as
edge ports.
40 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
For more information, see ESA24 10/100 Mbit Ethernet Switch User
Guide in PDF format in NOLS and Cable Lists and Use of ATM Links
and LAN Connections in Site documents.
4.
Change to a privileged mode in BiNOS
Enable the privileged mode in ESA24 operating system with the
command
ESA24> enable
The privileged mode allows advanced viewing and configuration for
the unit.
Note
The command prompt in privileged mode is the hash(#).
By default, the enable command does not ask for a password. It is
possible to protect the administrator's rights with a password. See
the ESA24 10/100 Mbit Ethernet Switch User Guide for more
information.
5.
Change to configuration mode in BiNOS
Enable the configuration mode in ESA24 operating system with the
command
ESA24#configure terminal
6.
Set the IP address and netmask for ESA24
ESA24(config)#ip address <ip address>/<netmask>
7.
Set the default gateway for ESA24
Delete the existing default route before add new route.
ESA24(config)#no ip route 0.0.0.0/0
ESA24(config)#ip route <destination address>/
<destination network mask> <ip gateway address>
8.
DN02143138
Issue 11-3 en
Enable DHCP, if necessary
# Nokia Siemens Networks
41 (145)
IP Connection Configuration for RNC
ESA24(config)#ip address dhcp
9.
Save the configuration
ESA24#write
Further information
To view information on the commands, enter ? in the ESA24 command
prompt. To view more information on the syntax of a specific command,
enter <command> ?.
Example
Configuring ESA24
This example shows how to configure ESA24.
1.
Connect to the IP address of ESA24 via Telnet.
a.
Select Start -> Run on the Windows Taskbar.
b.
Connect to the IP address of ESA24:
telnet 192.168.1.9
c.
Press Enter.
The following prompt is displayed:
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.
42 (145)
Save the configuration.
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
ESA24#write
2.8
Configuring OMS for DCN
2.8.1
Configuring OMS for DCN
Purpose
To get OMS fully integrated to the DCN, the default settings of OMS 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 EM Homepage. Go to the
EM Homepage with your Internet browser by entering the following
address: https://192.168.1.5. Use Nemuadmin / nemuuser usename
and password for logging into the EM homepage.
Download PuTTY from the link and save it to your computer (for
example to C:/temp). Then open putty.exe from your computer and
give an OMS IP address for the hostname (the default is
192.168.1.5), and click Open.
Log in with the username Nemuadmin / nemuuser
Change permissions to root user by giving the following command:
su -
Then provide the root user password (the default one is
anonymous). The root user is the only username who has the
necessary rights to execute the following configuring steps.
2.
DN02143138
Issue 11-3 en
Change the time zone settings
# Nokia Siemens Networks
43 (145)
IP Connection Configuration for RNC
For changing the time zone settings, refer to the instructions in
Changing time zone settings in OMS.
3.
Check the calendar time
For checking the correct calendar time, refer to the instructions in
Checking the calendar time in OMS.
4.
Password for the root user
If you want to change the password for the root user, give the
following command:
passwd
For enabling the new password to LDAP, the following command has
to executed:
fsdistribute /etc/shadow
5.
Configure the FTP user
If you want to change the default FTP user password, execute the
following command:
/opt/Nokia/SS_OMSINST/script/modifyOMSSettings.sh
You will see the following printout:
OMS FTP server IP address is 192.168.1.5
which is the user's own IP address
Type omsFtpUser password [press ENTER to use default]:
Here you have to add the new password for the FTP user.
You have to set the following settings: FTP Password = ******
OMS FTP IP = 192.168.1.5
FTP Username = omsFtpUser
FTP Password = ******
Are these parameters correct (yes/no)?
44 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
Check whether these parameters are correct, and then answer 'yes'.
6.
Configure the NWI3 user
a.
If you only want to change the default NWI3 user password,
execute the following command:
passwd Nemuadmin
b.
If you want to create a new NWI3 user, execute the following
command:
fsuseradd -g 557 <your_nwi3_username> -G pmgRoot for
example:
fsuseradd -g 557 nwi3user -G pmgRoot
c.
where 557 is the group number where the user will be added.
Set a password for the new user:
passwd <your_nwi3_username>
d.
If you want to take the new account into use immediately,
update the new user to the registry with the following
command:
fshascli –r /NWI3Adapter
7.
Add/remove MMI mapping to/from users
If you want to give MMI mapping, use the zmmimapping command.
MMI mapping is used by the MMI Window application to log OMS
users into the OMU. All users who have MMI mapping are printed.
a.
Print existing mapping.
Example
zmmimapping -p
b.
If OMS user already has mapping, delete mapping.
Example
zmmimapping -d Nemuadmin
c.
Add new mapping.
Example
zmmimapping -a Nemuadmin NEMUAD
For more information about MMI, see Using Element Manager in
RNC OMS.
8.
DN02143138
Issue 11-3 en
Configure OMS to RNC
# Nokia Siemens Networks
45 (145)
IP Connection Configuration for RNC
For configuring OMS to RNC, refer to the instructions in Configuring
OMS to RNC.
9.
Configure the OMS system identifier
For configuring the OMS system ID, refer to the instructions in
Configuring the OMS system identifier.
10.
Define the IP address for OMS
For defining the network settings for OMS, refer to the instructions in
Configuring IP address for OMS.
11.
Configure the DHCP server
For configuring the DHCP server, refer to the instructions in
Configuring the DHCP server in OMS.
Further information
The following table lists the OMS LDAP variables used when configuring
OMS for RNC connection.
Table 1.
46 (145)
RNC data in OMS registry
Variable
Data
Base identifier of RNC
NE-RNC-<id>, where the <id> must be
within the range 1 - 4095
OMU's IP address
As configured in Configuring IP stack in
OMU.
OMS's IP address
As configured in Configuring IP addresses
for OMS.
EMT UserName
The NEMUAD user ID created in Creating
MMI user profiles and user IDs for remote
connections to NetAct.
EMT Password
The NEMUAD user password created in
Creating MMI user profiles and user IDs
for remote connections to NetAct.
OMU FTP Username
The NEMUAD user ID created in Creating
MMI user profiles and user IDs for remote
connections to NetAct.
OMU FTP Password
The NEMUAD user password created in
Creating MMI user profiles and user IDs
for remote connections to NetAct.
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
Table 1.
RNC data in OMS registry (cont.)
Variable
Data
OMU Telnet UserName
The NEMUAD user ID created in Creating
MMI user profiles and user IDs for remote
connections to NetAct.
OMU Telnet Password
The NEMUAD user password created in
Creating MMI user profiles and user IDs
for remote connections to NetAct.
Note
All usernames and passwords are only examples.
Table 2.
2.8.2
RNC data in OMS registry
Variable
Data
OMS FTP UserName
The name of the service user with OMS
FTP Access, this is omsFtpUser.
OMS FTP Password
The password for the OMS FTP user as
defined in Configuring OMS for DCN.
OMS Registration Account Username
The NetAct NWI3 Access account
username.
OMS Registration Account Password
The NetAct NWI3 Access account
password.
Network Management’s Registration IOR
(RSIOR)
The Network Management's Registration
IOR (RSIOR) in NetAct
Checking the calendar time in OMS
Purpose
You have to make sure that the calendar time in OMS is set correctly.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
47 (145)
IP Connection Configuration for RNC
Note
Pre-installed OMS has its hardware clock set to UTC time and after
changing time zone, time should be correct. If time is offset only by few
minutes, or OMS time is in the past, time difference is acceptable.
After performing Configuring IP addresses for OMS part, OMS
connects to the NTP and resynchronises time. Since system has
timestamps both in files and database entries, it refuses to overwrite
newer settings with older ones. Therefore if after changing time zone
OMS time is in the future, system has newer timestamps than
commissioning 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, continue installation.
If time is in the past, continue the installation. When system restarts
in section Configuring IP addresses for OMS after modifying network
settings, check time with date command and continue on
commissioning when NTP has synchronised time.
If time is in the future, reinstall OMS according to the installation
instructions.
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 DHCP
can give an IP address when requested. Also, the DHCP address must be
in the same network as OMS. For example, if the OMS network interfaces
are in the 10.8.122.0 network, trying to give an IP address of 10.8.118.0
network will fail, since the network interface giving the IP address and
given address are in different networks.
48 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
You must have a root access to modify the DHCP settings and/or change
its status.
Steps
1.
Modifying DHCP address pool
a.
Open /opt/Nokia/SS_OMSINST/dhcpd/dhcpd.conf in a text
editor. The file contains an example configuration, which you
have to modify to match the current network and wanted
address pool.
b.
Change the subnet and netmask to the correct settings.
Consult OMS networks settings for the correct subnet and
netmask.
In the range line, type the first and last IP address of the IP
range that is defined to the DHCP IP pool.
For example:
range 10.1.1.10 10.1.1.12
c.
2.
gives a pool of three IP addresses starting with 10.1.1.10.
Exit the editor with saving the settings.
Using DHCP
Start DHCP by executing the following command:
chmod 544 /opt/Nokia/SS_OMSINST/dhcpd/zstart_dhcpd.sh
/opt/Nokia/SS_OMSINST/dhcpd/zstart_dhcpd.sh
The DHCPD is now started. Booting OMS will deactivate the
DHCPD.
To deactivate DHCP, execute the following command:
/opt/Nokia/SS_OMSINST/dhcpd/zstop_dhcpd.sh
To gain more information, use man DHCP.
2.8.4
Configuring the DNS client in OMS
Before you start
The DNS client configuration is distributed into the FlexiPlatform, and it is
present after system restart. Restarting the ClusterDNS service activates
the new configuration.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
49 (145)
IP Connection Configuration for RNC
Steps
1.
Open the /etc/clusterdns.conf file with an editor.
Open the configuration file with an editor you are familiar with, for
example nano as shown in the example below:
nano /etc/clusterdns.conf
2.
Find forwarders { 192.168.1.1; }; line and replace the default
address with the correct DNS IP
3.
Save and close the clusterdns.conf file.
4.
Distribute the configured file into the FlexiPlatform.
Run the following command for distributing the configured file into
the FlexiPlatform:
fsdistribute /etc/clusterdns.conf
5.
Restart the ClusterDNS service.
Run the following command for restarting the ClusterDNS service.
After this command, the new configuration is in use. Enter:
fshascli -r /ClusterDNS
Note
NEMU used to act as a secondary DNS service to the network. In OMS,
NEMU DNS is no longer available, as it was removed to improve
security and cleanup architecture.
2.8.5
Configuring OMS to RNC
Purpose
The External Message Transfer (EMT) connection between OMS and
OMU requires the following:
50 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
.
the LDAP registry includes the IP address of OMU and the user ID
and password of the network element
.
the user ID and password have been defined in the network element
for the EMT connection
.
the IP address of the OMS and the FTP username and password
also have to be defined for measurement bulk data transfer
.
the network element must have a user ID that the EMT, Telnet and
FTP connections can use.
Before you start
The following user accounts have to be created to OMS:
.
OMS FTP user (the default is omsFtpUser)
.
NWI3 user (the default is Nemuadmin)
Note
The NWI3 user must be the same as defined in the NetAct maintenance
region to which the OMS belongs.
Steps
1.
Start the zmodifyOMUSettings script
Start the zmodifyOMUSettings script by entering the following
command:
zmodifyOMUSettings
2.
See further instructions in zmodifyOMUSettings
You can change the OMU IP by using the zmodifyOMUSettings tool.
The zmodifyOMUSettings tool writes the entered information to the
LDAP register.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
51 (145)
IP Connection Configuration for RNC
Note
If the OMU FTP, OMU Telnet, or EMT passwords or usernames are
changed on the managed element side, the same changes must also
be done on the OMS side.
Start zmodifyOMUsettings
Current OMU IP can be checked by entering
the command zomuip and press enter.
Start zmodifyOMUSettings by entering the
command zmodifyOMUSettings in a SSH
client window.
When zmodifyOMUSettings is started, it asks
for new values. For the new values, see the
entries below:
OMU IP address
Insert the logical IP address of the OMU unit of
the managed network element: 10.1.1.2
OMU EMT UserName
Enter OMU EMT UserName. Press ENTER if
the current value is OK.
.
EMT UserName [STRING] current value:
SYSTEM
.
EMT UserName [STRING] new value:
NEMUAD
EMT Password
Enter EMT Password and press ENTER.
* EMT Password [STRING] new value: ******
Give the current password for NEMUAD.
OMU FTP UserName
Enter OMU FTP UserName. Press ENTER if
the current value is OK.
.
OMU FTP UserName [STRING] current
value: SYSTEM
.
OMU FTP UserName [STRING] new
value: NEMUAD
OMU FTP Password
Enter OMU FTP Password and press ENTER.
* OMU FTP Password [STRING] new value:
******
Give the current password for NEMUAD.
OMU Telnet UserName
52 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
Enter OMU Telnet UserName. Press ENTER if
the current value is OK.
OMU Telnet UserName [STRING] current
value: SYSTEM
OMU Telnet UserName [STRING] new value:
NEMUAD
OMU Telnet Password
Enter OMU Telnet Password and press
ENTER.
OMU Telnet Password [STRING] new value:
******
Give the current password for NEMUAD.
Changes to be updated
Check the information which will be updated.
You have to set the following:
OMU IP = 10.1.1.2
EMT Username = NEMUAD
EMT Password = ******
FTP Username = NEMUAD
FTP Password = ******
Telnet Username = NEMUAD
Telnet Password = ******
Are these parameters correct (yes/no)?
Answer: yes
Do you want to restart NWI3Adapter and OMS SW's (postConfig CHOOSE NO)? (yes/no)
Answer: no
2.8.6
Configuring NTP services in OMS
Purpose
OMS NTP can be configured to external NTP. Restarting ClusterNTP
service activates the new configuration.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
53 (145)
IP Connection Configuration for RNC
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 editor
for 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 correct
NTP server settings. For example: 10.0.0.5
restrict 10.0.0.5 mask 255.255.255.255 nomodify notrap
noquery
Replace the IP address in the server line with correct IP address:
server 10.0.0.5 iburst minpoll 4
3.
Save, then close the editor
4.
Distribute the configured file
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
54 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
2.8.7
Configuring OMS system identifier
Purpose
This procedure configures the system identifier of OMS. The systemId has
to have the same value as the identifier of the network element, for
example, (systemId = NE-RNC-'rnc_id'). In this scenario, the system
consists of a managed network element and OMS, which is logically seen
as part of the network element itself. In this case, the system identifier and
network 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 can
be problems in sending notifications to the NetAct. Note also that the
systemId must be unique in the whole network.
Steps
1.
Start the zchangecluster-id script
Entering the following command:
zchangecluster-id
2.
See further instructions in zchangecluster-id below:
RNC ID
The value could be for example NE-RNC'rnc_id' or MD-SITE-'number'.
The value must be chosen between 1 - 4095,
for example, NE-RNC-'1'.
Give new RNC id number <1-4095>:
NWI3Adapter restart
The new clusterid will be valid after the
NWI3Adapter restart.
Do you want restart NWI3Adapter and OMS SW's? (yes/no)
Answer: no
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
55 (145)
IP Connection Configuration for RNC
Note
The cluster id will not change during default/current session. It is valid
from new sessions onward.
2.8.8
Configuring IP addresses for OMS
Purpose
OMS network settings can be modified afterwards by the
zmodifyNetworkSettings command. The DNS client and NTP
configuration files are distributed into the FlexiPlatform. New
configurations are present after system restart.
Before you start
Gather the following information:
.
OMS IP address
.
Netmask, in bits. For more information, see the conversion table
below
.
Gateway (usually it is OMU address)
.
NTP IP address
.
DNS IP address
Table 3.
Bits/Subnet conversion table
24
255.255.255.0
25
255.255.255.128
26
255.255.255.192
27
255.255.255.224
28
255.255.255.240
29
255.255.255.248
Script will query information listed above and confirm that entered
information is correct. After script has run OMS will restart itself to activate
new settings.
56 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
Note
NEMU used to act as a secondary DNS service to the network. In OMS,
NEMU DNS is no longer available, as it was removed to improve
security and cleanup architecture.
Steps
1.
Enter zmodifyNetworkSettings
Executing the zmodifyNetworkSettings starts query for new
network settings, confirm changes and then change values to the
OMS and restart to take new settings to the use.
Command print capture:
# zmodifyNetworkSettings
Modifying network settings...
Enter parameters
OMS IP:
10.1.1.5
NETMASK: (in bits e.g. 24)
28
DNS IP:
10.0.0.5
NTP IP:
10.0.0.5
DEFAULT GATEWAY:
10.1.1.2
Parameters
OMS IP: 10.1.1.5
NETMASK: /28
DNS IP: 10.0.0.5
NTP IP: 10.0.0.5
DEFAULT GATEWAY: 10.1.1.2
These are used variables, continue? (yes/no)?
After answering yes, zmodifyNetworkSettings will modify values
and ask to restart OMS.
Answer: y
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
57 (145)
IP Connection Configuration for RNC
/ 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 network
settings
Configuring computer network settings depends on the operating
system.
3.
If OMS time was in the past in calendar time
Check on chapter Checking the calendar time in OMS, login to the
OMS after restart and verify time on date command. When NTP has
synchronised time to current time, continue commissioning. If time
difference was larger than 15 minutes, restart OMS once more
before continuing commissioning to ensure that services have
stabilized.
2.9
Connecting to O&M backbone via Ethernet
Purpose
This procedure describes how to connect RNC to the external network for
O&M connections using an external router connected to the ESA12 or
ESA24 Ethernet switch.
Computer with
Element Manager
OMS
O&M
Ethernet
connection
ESA24
NetAct
RNC
Figure 10.
58 (145)
OMU
Ethernet connection for O&M traffic
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for O&M backbone (RNC-NetAct)
O&M connections from the RNC to the O&M backbone can also be
created via ATM virtual connections, but Ethernet is the preferred way.
Note
Even if the IP over ATM connection has been configured, the O&M
traffic does not automatically switch to using it when the Ethernet
connection is down.
Before you start
Because the IP addresses for OMU, ESA12/ESA24 and OMS have been
preconfigured in the RNC, you must first change the IP addresses. Several
elements in the network can have the same preconfigured IP addresses,
so if you do not change the preconfigured addresses, there will be
problems in the network.
Steps
1.
Connect the network element physically to the external router
via ESA12/ESA24 Ethernet switch
Connect the router to the ESA12/ESA24 switch.
2.
2.10
Configure the external router according to instructions
provided by the router vendor
Connecting to O&M backbone via ATM interfaces
Purpose
For O&M connections towards NetAct, IP over ATM interfaces for OMU
are only required if the RNC is connected to the external network via ATM
virtual connections. The preferred way to connect RNC to NetAct is via
Ethernet (see Connecting to O&M backbone via Ethernet). The IP over
ATM connection should only be used as a backup.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
59 (145)
IP Connection Configuration for RNC
Note
Even if the IP over ATM connection has been configured, the O&M
traffic does not automatically switch to using it when the Ethernet
connection is down.
Before you start
ATM resources must be created before this procedure is commenced. For
instructions, see Creating ATM resources in RNC in ATM Resource
Management.
Steps
1.
Configure IP over ATM interface to the functional unit
Refer the instructions in Creating and modifying IP over ATM
interfaces.
2.
Assign IP addresses to the interfaces
Defining the destination IP address creates a static route in the
routing table for the IP interface.
Note
The destination IP address parameter is always mandatory.
For IPv4:
ZQRN:<unit type>,<unit index>:<interface name>,
[<point to point interface type>]:[<IP address>],[<IP
address type>]:[<netmask length>]:[<destination IP
address>]:[<MTU>]:[<state>];
For IPv6:
ZQ6N:<unit type>,<unit index>:<interface name>,
[<point to point interface type>]:[<IP address>],[<IP
address type>]:[<prefix length>]:[<destination IP
address>];
60 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for BTS O&M (RNC-BTS/AXC)
3
Configuring IP for BTS O&M (RNC-BTS/
AXC)
Purpose
The purpose of this procedure is to configure IP for BTS O&M (RNC-BTS/
AXC and RNC-FlexiBTS). The alternative ways to configure IP for BTS
O&M are detailed below:
.
tree topology ATM layer for O&M network to BTS, or
.
star topology ATM layer for O&M network to BTS.
By using star topology, O&M connections can use the same VPI as control
plane traffic. The VPI connection must then be configured as CBR class.
This also means that if the O&M VCI is configured to UBR class, it can use
the same maximum capacity that is the bit rate for VPI.
You should use the dedicated VPI for O&M traffic in the tree model so that
the O&M connection can use the free capacity of the link more easily.
Note
Currently, FlexiBTS does not support ATM cross-connecting. Therefore,
a FlexiBTS can be configured only in a star topology or as the last BTS
in a tree topology.
For more information on the topologies, see the Nokia WCDMA RAN
System Information Set.
You can use either static routing or dynamic routing (OSPF) for BTS O&M.
If you use OSPF, you do not need to configure static routes towards the
BTSs. When you create the OSPF configuration, the routes are
automatically created after the configuration.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
61 (145)
IP Connection Configuration for RNC
With OSPF, you must use unnumbered interfaces towards the BTS,
because the AXC only supports unnumbered interfaces. If you have
numbered point-to-point interfaces with static routing in use and you want
to activate OSPF also to these interfaces, you must modify the interface
type. For instructions on how to modify point-to-point interfaces, see
Creating and modifying IP interfaces in IP Connection Configuration for
RNC.
Note
Currently, FlexiBTS does not support dynamic (OSPF) routing and
numbered IP interfaces. Therefore, only static routing must be used
towards a FlexiBTS and the IP interface type must be unnumbered.
Before you start
You need to create ATM resources for the Iub interface before starting this
procedure. When using tree topology, the VPI/VCI termination point with
default 0/32 must be created for the O&M connection in OMU.
When using star topology, you need to create VPI/VCI termination point for
O&M connection for dedicated BTS in OMU. Check if the VPI/VCI
termination point is already created for the control plane. By default, the
same VPI termination point is used as the control plane traffic for BTS. The
VPI is configured as CBR class.
You also should have ATM plans available for the tree or star model DCN
for O&M. For more information, see Creating ATM resources in RNC in
ATM Resource Management.
Steps
1.
Start the MMI Window in the Element Manager
2.
Create an IP over ATM interface towards BTS in OMU
It is recommended to use unnumbered interfaces towards BTS
because point-to-point links do not need IP subnets specified for the
link. This also helps in planning and configuring the IP network when
IP subnets are not used with point-to-point links.
For instructions, see Creating and modifying IP over ATM interfaces.
3.
If you are using static routing
Then
62 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for BTS O&M (RNC-BTS/AXC)
Create static route for BTS O&M
For O&M connections towards BTS, configure the route from OMU
to the IP address of the gateway that is on the other side of the pointto-point ATM connections (AXC address of BTS site).
ZQKC:<unit type>,<unit index>:[<destination IP
address>],[<netmask length>]:<gateway IP address>,
[<local IP address>]:[<route type>]:[<route
preference>];
Note
The parameter local IP address is only valid for local IP address based
default routes. For normal static routes, you do not need to give the
local IP address. For more information about local IP address based
default routes, refer to Creating and modifying static routes.
4.
If you are using OSPF
Then
Configure OSPF area parameters and interfaces
a.
Define the OSPF parameters of an OSPF router.
The area identification specifies the area ID for a new OSPF.
The area ID is entered as a dotted-quad. The IP network
number of a subnetted network may be used as the area ID. It
is recommended that all OSPF areas except the backbone be
configured as totally stubby areas.
ZQKE:<unit type>,<unit index>:<area
identification>:<stub area>,[<stub area route
cost>],<totally stubby area>;
b.
Define the OSPF interface parameters of an OSPF router.
The default value for router dead interval parameter in
AXC is 120. Because the value must be the same in both AXC
and RNC, change the value of the router dead interval
parameter to 120 in RNC.
ZQKF:<unit type>,<unit index>:<interface
specification>:<area identification>:[<hello
interval>]:[<router dead interval>]:[<ospf
cost>]:[<election priority>]:[<passive>]:
[<authentication> | <authentication>,
<password>];
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
63 (145)
IP Connection Configuration for RNC
Further information
Example
Configuring IP for BTS O&M using star topology ATM layer
This example presents IP for BTS O&M configuration in RNC when star
topology ATM layer and dynamic routing (OSPF) is used.
RNC Element
Manager
O&M
backbone
ESA12/ESA24
OMS
EL0 10.1.1.2/28 (logical)
OMU
RNC LAN
10.1.1.0/28
AA2 10.1.1.2/32
AA1 10.1.1.2/32
RNC
unnumbered lines
RAN BTS sites
address range
10.1.3.0/29
Figure 11.
1.
RAN BTS sites
address range
10.1.2.0/29
Example of IP configuration for BTS O&M when star topology and
OSPF are used
Create IP interfaces towards every BTS in OMU.
Assign logical IP addresses to the unnumbered point-to-point
network interfaces of the OMU unit, with MTU value 1500.
64 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for BTS O&M (RNC-BTS/AXC)
Note
Unnumbered IP address should be the same as IP address of EL
interface. If you don't know what IP address is in use on EL interface,
check the configuration first by QRI command, for example:
ZQRI:OMU:EL0;
ZQRN:OMU:AA1,U:10.1.1.2,L::10.1.2.1:1500:UP;
ZQRN:OMU:AA2,U:10.1.1.2,L::10.1.3.1:1500:UP;
...
ZQRN:OMU:AA31,U:10.1.1.2,L::10.1.32.1:1500:UP;
ZQRN:OMU:AA32,U:10.1.1.2,L::10.1.33.1:1500:UP;
2.
Create an IP over ATM interface between the IP interface and the
ATM termination point.
Configure an IP over ATM interface with network interface names
AA1...AA32 using the same VPI as control plane traffic, and with VCI
32.
ZQMF:OMU,,L:AA1:1,1,32;
ZQMF:OMU,,L:AA2:2,2,32;
...
ZQMF:OMU,,L:AA31:1,31,32;
ZQMF:OMU,,L:AA32:2,32,32;
3.
Configure OSPF area parameters of an OSPF router for the BTS
branch.
ZQKE:OMU,0:10.1.2.0:Y,,Y;
ZQKE:OMU,1:10.1.2.0:Y,,Y;
4.
Configure the OSPF interface parameters of an OSPF router.
ZQKF:OMU,0:AA1:10.1.2.0::120;
ZQKF:OMU,1:AA1:10.1.2.0::120;
ZQKF:OMU,0:AA2:10.1.2.0::120;
ZQKF:OMU,1:AA2:10.1.2.0::120;
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
65 (145)
IP Connection Configuration for RNC
...
ZQKF:OMU,0:AA31:10.1.2.0::120;
ZQKF:OMU,1:AA31:10.1.2.0::120;
ZQKF:OMU,0:AA32:10.1.2.0::120;
ZQKF:OMU,1:AA32:10.1.2.0::120;
Example
Configuring IP for BTS O&M using tree topology ATM layer
This example presents IP for BTS O&M configuration in RNC when tree
topology ATM layer and static routing are used.
1.
Create IP interfaces towards the BTS in OMU.
Assign logical IP addresses and destination IP addresses to the
unnumbered point-to-point network interfaces of the OMU unit, with
MTU value 1500, and accept default values for the rest of the
parameters.
ZQRN:OMU:AA1,U:10.1.1.2,L::10.1.2.1:1500:UP;
ZQRN:OMU:AA2,U:10.1.1.2,L::10.1.3.1:1500:UP;
2.
Create an IP over ATM interface between the IP interface and the
ATM termination point.
Configure a TCP/IP ATM interface with network interface names AA1
(to OMU from ATM interface 1) and AA2 (to OMU from ATM interface
2) using VPI 0 and VCI 32 and accept default values for the rest of
the parameters.
ZQMF:OMU,,L:AA1:1,0,32;
ZQMF:OMU,,L:AA2:2,0,32;
3.
Create static routes for the BTS branch.
Create static routes for OMU to the IP subnetworks 10.1.2.0/24 and
10.1.3.0/24 via the router with IP addresses 10.1.2.1 and 10.1.3.1.
ZQKC:OMU,0:10.1.2.0,24:10.1.2.1,:LOG;
ZQKC:OMU,0:10.1.3.0,24:10.1.3.1,:LOG;
66 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-PS User Plane (RNC-SGSN)
4
Configuring IP for Iu-PS User Plane
(RNC-SGSN)
Purpose
The purpose of this procedure is to configure IP for the Iu-PS interface
between the RNC and the Serving GPRS Support Node (SGSN).
Before you start
You should know the GTP-U endpoint address in SGSN. The address will
be in RAB assignment. The GTPU selection is based on the following
mechanism:
DN02143138
Issue 11-3 en
1.
Try to find the GTPU which can fulfill the following two requirements
at the same time:
a.
One of this GTPU's IPoA interfaces has the destination IP
address as same as the IP address received in RAB
assignment.
b.
At least one of this GTPU’s IPoA interfaces is in good working
state.
If more than one GTPU can fulfill these requirements, the GTPU will
be selected round-robin among these GTPUs
2.
If no GTPU can fulfill the requirements in step 1, try to find the GTPU
which can fulfill the following requirement:
a.
At least one of this GTPU’s IPoA interfaces is in good working
state.
If more than one GTPU can fulfill this requirement, the GTPU will be
selected round-robin among these GTPUs.
3.
If no GTPU can be selected in step 2, the GTPU selection is failed.
# Nokia Siemens Networks
67 (145)
IP Connection Configuration for RNC
Note
In addition to the MML based configuration the Iu-PS interface ATM and
IP basic resources can be configured via the IP and ATM plan interface
from the NetAct. The ATM plan interface contains the basic support for
ATM interface, VPLtp and VCLtp creation while the IP plan support
covers the basic support for the MML commands QMF, QRN and QKC.
The IP plan support does not cover the OSPF configuration or IP QoS
configuration.
For more information on the IP plan interface, see IP plan interface in
document RNC Operation and Maintenance.
The ATM resources must be created before the interface can be
configured. For instructions, see Creating ATM resources in RNC in ATM
Resource Management.
Steps
1.
Interrogate the states of the units in the system (USI)
Check that the units for which you are going to create network
interfaces are in working state (WO-EX).
ZUSI:<unit type>;
2.
Create IP over ATM interfaces to all GTPUs
Create IPoA interfaces to all GTPUs (at least one ATM VCCs per
GTPU) according to instructions in Creating and modifying IP over
ATM interfaces. Set the value of the encapsulation method
parameter to LLC/SNAP.
If you want to dedicate a GTPU for real-time IP traffic, set the value
of usage parameter to IPOART (this is an optional feature) for all IPoA
interfaces of the unit.
IPoA interfaces can support 2 VCCs under one interface. These
VCCs have different usage parameters. So you can dedicate one
VCC to real-time IP traffic under a given IPoA interface. For more
information about configuring 2 VCCs for one IPoA interface, refer to
Creating and modifying IP over ATM interfaces.
3.
68 (145)
Configure the default static routes
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-PS User Plane (RNC-SGSN)
You do not need to specify the destination IP address for the default
route.
For IPv4:
ZQKC:<unit type>,<unit index>::<gateway IP address>,
[<local IP address>]:[<route type>]:[<route
preference>];
Note
The parameter local IP address is only valid for the local IP address
based default routes. For normal static routes, you do not need to give
the local IP address. For more information about local IP address based
default routes, refer to Creating and modifying static routes.
For IPv6:
ZQ7C:<unit type>,<unit index>:<destination IP
address>,[<prefix length>]:<gateway IP address>:
[<route type>]:[<route preference>];
4.
Create other static routes, if needed
For IPv4:
ZQKC:<unit type>,<unit index>:<destination IP
address>,[<netmask length>]:<gateway IP address>:
[<route type>]:[<route preference>];
For IPv6:
ZQ7C:<unit type>,<unit index>:<destination IP
address>,[<prefix length>]:<gateway IP address>:
[<route type>]:[<route preference>];
5.
Create OSPF configuration, if necessary
Currently, OSPF only supports IPv4. If you want to use OSPF routing
on the Iu-PS interface, create the configuration as follows:
a.
Set the IP address for loopback.
ZQRN:<unit type>,<unit index>:<interface name>:
<IP address>;
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
69 (145)
IP Connection Configuration for RNC
b.
c.
d.
6.
Configure the OSPF to inform other OSPF routers of the
loopback address.
ZQKU:<unit type>,<unit index>:<redistribute
type and identification>:<metric>;
Configure the area(s) that include also the neighbouring
routers.
ZQKE:<unit type>,<unit index>:<area
identification>:<stub area>,[<stub area route
cost>],<totally stubby area>;
Configure an interface for that area.
ZQKF:<unit type>,<unit index>:<interface
specification>:<area identification>:[<hello
interval>]:[<router dead interval>]:[<ospf
cost>]:[<election priority>]:[<passive>]:
[<authentication> | <authentication>,
<password>];
Create QoS DiffServ configuration (GTPU), if needed
It is also possible to configure QoS DiffServ traffic classification to
GTPU units. The main function for IP QoS DiffServ is to assure that
real time (RT) traffic has a higher throughput priority than non-real
time (NRT) traffic in the GTPU TCP/IP stack. It checks that the traffic
is real time or non-real time and processes the traffic base on the
desired ratio. For detailed instructions, refer to Creating and
modifying IP QoS configuration.
Example
IP configuration for Iu-PS with each GTPU connected to one
SGSN unit
This example shows how to configure the Iu-PS interface between the
RNC and SGSN using two STM-1 interfaces in both RNC and SGSN. In
the example, four GTPU units are deployed to handle the Packet Switched
Radio Access Bearers in the RNC in load sharing mode. Each GTPU is
logically connected to one of the SGSN units, GPLCs. Two GTP-U
endpoint addresses are used in SGSN:
70 (145)
.
10.2.0.1 in GPLC-1
.
10.3.0.1 in GPLC-2
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-PS User Plane (RNC-SGSN)
RNC
GTPU-0
AA1
SGSN
10.1.1.10
VPI=0, VCI=40
10.2.0.1
10.1.1.1
GPLC1
VPI=0, VCI=41
GTPU-1
AA1
10.1.1.11
STM-1 line #1
GTPU-2
AA2
10.1.2.12
VPI=0, VCI=42
10.1.2.1
VPI=0, VCI=43
GTPU-3
AA2
10.1.2.13
10.3.0.1
GPLC2
STM-1 line #2
= GPLC-1
= GPLC-2
Figure 12.
1.
ATM virtual channel connections and IP addresses with each GTPU
connected to one GPLC unit
Create ATM resources.
Create the following ATM configuration (for instructions, see
Creating ATM resources in RNC in ATM Resource Management):
.
STM-1 ATM interface (with interface ID 1). This interface is
connected to SGSN (GPLC-1) via a direct physical connection
or via the SDH transmission network.
.
In ATM interface 1, one VPLtp with VPI=0.
.
In ATM interface 1, two VCLtps with VPI=0 and VCI=40, 41.
.
STM-1 ATM interface (with interface ID 2). This interface is
connected to SGSN (GPLC-2) via a direct physical connection
or via the SDH transmission network.
.
In ATM interface 2, one VPLtp with VPI=0.
.
In ATM interface 2, two VCLtps with VPI=0 and VCI=42, 43.
2.
DN02143138
Issue 11-3 en
Create IP over ATM interfaces to all GTPUs.
# Nokia Siemens Networks
71 (145)
IP Connection Configuration for RNC
a.
b.
Create IP over ATM interfaces connected to GPLC-1.
ZQMF:GTPU,0,P:AA1:1,0,40:1,IPOAUD;
ZQMF:GTPU,1,P:AA1:1,0,41:1,IPOAUD;
Create IP over ATM interfaces connected to GPLC-2.
ZQMF:GTPU,2,P:AA2:2,0,42:1,IPOAUD;
ZQMF:GTPU,3,P:AA2:2,0,43:1,IPOAUD;
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 GPLC
unit in the SGSN.
ZQKC:GTPU,0::10.1.1.1,:PHY;
ZQKC:GTPU,1::10.1.1.1,:PHY;
ZQKC:GTPU,2::10.1.2.1,:PHY;
ZQKC:GTPU,3::10.1.2.1,:PHY;
Example
IP Configuration for Iu-PS when a GTPU can serve only one
SGSN 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 and
GTPU-3 are connected to GPLC-2. There is no route or IP forwarding
between GPLC-1 and GPLC-2, that means GTPU-0 and GTPU-1 can
serve only 10.2.0.1; meanwhile, GTPU-2 and GTPU-3 can serve only
10.3.0.1.
To archive that kind of dedication, configure IP address of AA interface in
GTPU-0 and GTPU-1 to 10.2.0.1; meanwhile, configure that of GTPU-2
and GTPU-3 to 10.3.0.1.
72 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-PS User Plane (RNC-SGSN)
When RNC receives RAB assignment with IP address 10.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.
RNC
GTPU-0
AA1
SGSN
10.1.1.10
VPI=0, VCI=40
10.2.0.1
10.1.1.1
GPLC1
VPI=0, VCI=41
GTPU-1
AA1
10.1.1.11
STM-1 line #1
GTPU-2
AA2
No forwarding
between GPLCs
10.1.2.12
VPI=0, VCI=42
10.3.0.1
10.1.2.1
VPI=0, VCI=43
GTPU-3
AA2
10.1.2.13
GPLC2
STM-1 line #2
= GPLC1
= GPLC2
Figure 13.
1.
GTPUs connected to only one GPLC
Create ATM resources
Create the following ATM configuration. For instructions, see
Creating ATM resources in RNC in ATM Resource Management.
.
STM-1 ATM interface (with interface ID 1). This interface is
connected to SGSN (GPLC-1) via a direct physical connection
or via the SDH transmission network.
.
In ATM interface 1, one VPLtp with VPI=0.
.
In ATM interface 1, two VCLtps with VPI=0 and VCI=40, 41
.
STM-1 ATM interface (with interface ID 2). This interface is
connected to SGSN (GPLC-2) via a direct physical connection
or via the SDH transmission network.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
73 (145)
IP Connection Configuration for RNC
.
.
2.
In ATM interface 2, one VPLtp with VPI=0.
In ATM interface 2, two VCLtps with VPI=0 and VCI=42, 43.
Create IP over ATM interfaces to all GTPUs
ZQMF:GTPU,0,P:AA1:1,0,40:1,IPOAUD;
ZQMF:GTPU,1,P:AA1:1,0,41:1,IPOAUD;
ZQMF:GTPU,2,P:AA2:2,0,42:1,IPOAUD;
ZQMF:GTPU,3,P:AA2:2,0,43:1,IPOAUD;
3.
Assign IP addresses to the network interfaces
a.
Configure GTPU-0 and GTPU-1 to serve SGSN address
10.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 address
10.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 both
SGSN units
This example shows how to configure the Iu-PS interface between the
RNC and SGSN using two STM-1 interfaces in RNC and SGSN. In this
example, 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 deployed
to handle the Packet Switched Radio Access Bearers in RNC in load
sharing mode. When RNC receives RAB assignment with IP address
10.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 that
even if one link fails, the interface capacity between the RNC and SGSN
remains the same. Note that the same redundancy can be achieved by
using OSPF instead of static routing (see the next example: configuring IuPS when OSPF is in use).
74 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-PS User Plane (RNC-SGSN)
In this configuration, RNC always has a connection to the IP addresses of
the GPLC units (10.2.0.1 and 10.3.0.1) even if one of the interfaces of a
GTPU fails.
RNC
GTPU-0
SGSN
AA0 10.1.1.10
10.2.0.1
AA1 10.1.2.10
10.1.2.1
VPI=0, VCI=40
VPI=0, VCI=41
10.2.0.1
10.1.1.1
GTPU-1
GTPU-2
AA0 10.1.1.11
10.1.2.1
AA1 10.1.2.11
10.2.0.1
AA0 10.1.1.12
10.1.1.1
AA1 10.1.2.12
10.3.0.1
GPLC-1
VPI=0, VCI=42
VPI=0, VCI=43
STM-1 line #1
VPI=0, VCI=40
VPI=0, VCI=41
10.3.0.1
10.1.2.1
GTPU-3
AA0 10.1.1.13
10.3.0.1
AA1 10.1.2.13
10.1.1.1
VPI=0, VCI=42
VPI=0, VCI=43
GPLC-2
STM-1 line #2
= GPLC-1
= GPLC-2
= primary route
Figure 14.
1.
ATM virtual channel connections and IP addresses with GTPUs
connected to both GPLC units
Create ATM resources.
Create the following ATM configuration (for instructions, see
Creating ATM resources in RNC in ATM Resource Management):
.
STM-1 ATM interface (with interface ID 1). This interface is
connected to SGSN (GPLC-1) via a direct physical connection
or via the SDH transmission network.
.
In ATM interface 1, one VPLtp with VPI=0.
.
In ATM interface 1, four VCLtps with VPI=0 and VCI=40...43.
.
STM-1 ATM interface (with interface ID 2). This interface is
connected to SGSN (GPLC-2) via a direct physical connection
or via the SDH transmission network.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
75 (145)
IP Connection Configuration for RNC
.
.
In ATM interface 2, one VPLtp with VPI=0.
In ATM interface 2, four VCLtps with VPI=0 and VCI=40...43.
2.
Create IP over ATM interfaces to all GTPUs.
a.
Create IP over ATM interfaces connected to GPLC-1.
ZQMF:GTPU,0,P:AA0:1,0,40:1,IPOAUD;
ZQMF:GTPU,1,P:AA1:1,0,41:1,IPOAUD;
ZQMF:GTPU,2,P:AA0:1,0,42:1,IPOAUD;
ZQMF:GTPU,3,P:AA1:1,0,43:1,IPOAUD;
b.
Create IP over ATM interfaces connected to GPLC-2.
ZQMF:GTPU,0,P:AA1:2,0,40:1,IPOAUD;
ZQMF:GTPU,1,P:AA0:2,0,41:1,IPOAUD;
ZQMF:GTPU,2,P:AA1:2,0,42:1,IPOAUD;
ZQMF:GTPU,3,P:AA0:2,0,43:1,IPOAUD;
3.
Assign IP addresses to the network interfaces.
Note that the destination address of the IP over ATM interface does
not have to be the IP address of the next hop. The IP address and
destination IP address of the IP over ATM interface can be in
different subnets.
a.
Configure interfaces connected to GPLC-1.
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.
ZQKC:GTPU,0::10.1.2.1,:PHY;
ZQKC:GTPU,1::10.1.2.1,:PHY;
ZQKC:GTPU,2::10.1.1.1,:PHY;
ZQKC:GTPU,3::10.1.1.1,:PHY;
There should be one connection and route between GPLC-1 and
GPLC-2.
76 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-PS User Plane (RNC-SGSN)
Example
IP configuration for Iu-PS with GTPUs connected to different
SGSNs
This example shows how to configure the Iu-PS interface between the
RNC and SGSNs using two GTPUs connected to different SGSN. In this
example, 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 Switched
Radio Access Bearers originated from different SGSN in RNC. When the
RNC receives RAB assignment with IP address 10.2.1.1 or 10.2.1.2, only
GTPU-0 will be possibly selected. Similarly, when RAB assignment with IP
address 10.2.2.1 or 10.2.2.2 is received, only GTPU-1 will be possibly
selected.
RNC
SGSN1
GTPU-0
AA0 10.1.1.1
10.1.1.2
VPI=0, VCI=40
10.2.1.1
10.2.1.2
GTP-0 10.2.1.1
STM-1 line #1
GTP-1 10.2.1.2
SGSN2
GTPU-1
AA0 10.1.2.1
10.1.2.2
VPI=0, VCI=41
10.2.2.1
10.2.2.2
GTP-0 10.2.2.1
STM-1 line #2
GTP-1 10.2.2.2
SGSN1
SGSN2
Figure 15.
1.
ATM virtual channel connections and IP addresses with GTPUs
connected to different SGSNs
Create ATM resources.
Create the following ATM configuration (for instructions, see
Creating ATM resources in RNC in ATM Resource Management):
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
77 (145)
IP Connection Configuration for RNC
.
.
.
.
.
.
STM-1 ATM interface (with interface ID 1). This interface is
connected to SGSN1 via a direct physical connection or via
the SDH transmission network.
In ATM interface 1, one VPLtp with VPI=0.
In ATM interface 1, four VCLtps with VPI=0 and VCI=40.
STM-1 ATM interface (with interface ID 2). This interface is
connected to SGSN2 via a direct physical connection or via
the SDH transmission network.
In ATM interface 2, one VPLtp with VPI=0.
In ATM interface 2, four VCLtps with VPI=0 and VCI=41.
2.
Create IP over ATM interfaces to all GTPUs.
a.
Create IP over ATM interfaces connected to SGSN1
ZQMF:GTPU,0,P:AA0:1,0,40:1,IPOAUD;
b.
Create IP over ATM interfaces connected to SGSN2
ZQMF:GTPU,1,P:AA0:2,0,41:1,IPOAUD;
3.
Assign IP addresses to the network interfaces
Note that the destination address of the IP over ATM interface does
not have to be the IP address of the next hop. The IP address and
destination IP address of the IP over ATM interface can be in
different subnets.
a.
Configure interfaces connected to 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
ZQKC:GTPU,0::10.2.1.1,:PHY;
ZQKC:GTPU,1::10.2.2.1,:PHY;
Example
Configuring Iu-PS by using static routes for redundancy
This example shows another way to configure Iu-PS by using static routes
to archieve the redundancy purpose.
In this example, there are two GTP-U endpoint addresses belonging to a
same subnet in SGSN: 10.10.1.1/24 and 10.10.1.2/24:
78 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-PS User Plane (RNC-SGSN)
.
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 two
addresses in SGSN. In this example, each GTPU is configured to serve
both two addresses in a load sharing mode.
SGSN
RNC
Router
GTPU-0
AA0 10.1.1.1
AA1 10.1.2.1
10.1.1.2
10.1.1.2
10.1.2.2
10.1.3.2
Ethernet
Switch
10.10.1.1
EL0
GPLC-1
EL1
STM-1
line #1
Router
GTPU-1
AA0 10.1.3.1
10.1.3.2
10.1.2.2
AA1 10.1.4.1
10.1.4.2
10.1.4.2
EL0
Ethernet
Switch
GPLC-2
EL1
10.10.1.2
STM-1
line #2
= primary route
Figure 16.
1.
GTPUs connected to SGSN by ATM and Ethernet
Create ATM resources
Create the following ATM configuration. For instructions, see
Creating ATM resources in RNC in ATM Resource Management.
.
STM-1 ATM interface (with interface ID 1).
.
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
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
79 (145)
IP Connection Configuration for RNC
2.
Create IP over ATM interfaces to all GTPUs
ZQMF:GTPU,0,P:AA0:1,0,40:1,IPOAUD;
ZQMF:GTPU,0,P:AA1:2,0,40:1,IPOAUD;
ZQMF:GTPU,1,P:AA0:1,0,41:1,IPOAUD;
ZQMF:GTPU,1,P:AA1:2,0,41:1,IPOAUD;
3.
Assign IP addresses to the network interfaces
Note
Do not configure the destination address to the SGSN endpoint
addresses.
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 subnet route, while for backup
path, a default route is used. GTPUs always route IP packet via the
host or subnet route as long as the corresponding AA interface is up
and operational. In case the AA interface used by the primary path is
down, the backup path will be used. In this example, the primary
path in GTPU-0 is AA0, while the primary path in GTPU-1 is AA1.
a.
Configure a subnet 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 subnet 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 the
RNC and SGSN using OSPF for routing. When OSPF is in use and a link
fails, the user plane traffic is switched to the working link.
80 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-PS User Plane (RNC-SGSN)
In this example, the address of Lo0 interface, which will be used as GTP
endpoint on GTPUs, will be distributed to SGSN by either configuring it as
a stub host, or redistribute Lo0 interface into ospf routing domain. Similarly,
the address used as GTP endpoint on SGSN should be imported to ospf
properly to be learnt by GTPU. Refer to the manual of SGSN for more
details.
RNC
LO0
GTPU-0
10.1.1.1
AA1 10.1.2.10
10.1.2.1
GTPU-3
10.1.1.3
10.1.1.1
AA1 10.1.2.11
10.1.2.1
10.2.0.1
GPLC-1
VPI=0, VCI=42
VPI=0, VCI=43
STM-1 line #1
10.1.1.4
AA0 10.1.1.12
10.1.1.1
AA1 10.1.2.12
10.1.2.1
LO0
VPI=0, VCI=40
VPI=0, VCI=41
10.1.1.1
AA0 10.1.1.11
LO0
GTPU-2
10.1.1.2
AA0 10.1.1.10
LO0
GTPU-1
SGSN
VPI=0, VCI=40
VPI=0, VCI=41
10.3.0.1
10.1.2.1
10.1.1.5
AA0 10.1.1.13
10.1.1.1
AA1 10.1.2.13
10.1.2.1
VPI=0, VCI=42
VPI=0, VCI=43
GPLC-2
STM-1 line #2
= GPLC-1
= GPLC-2
= primary route
Figure 17.
1.
Iu-PS configuration with OSPF in use
Create ATM resources.
Create the following ATM configuration (for instructions, see
Creating ATM resources in RNC in ATM Resource Management):
.
STM-1 ATM interface (with interface ID 0). This interface is
connected to SGSN (GPLC-1) via a direct physical connection
or via the SDH transmission network.
.
In ATM interface 1, one VPLtp with VPI=0.
.
In ATM interface 1, four VCLtps with VPI=0 and VCI=40...43.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
81 (145)
IP Connection Configuration for RNC
.
.
.
82 (145)
STM-1 ATM interface (with interface ID 1). This interface is
connected to SGSN (GPLC-2) via a direct physical connection
or via the SDH transmission network.
In ATM interface 2, one VPLtp with VPI=0.
In ATM interface 2, four VCLtps with VPI=0 and VCI=40...43.
2.
Create IP over ATM interfaces to all GTPUs.
a.
Create IP over ATM interfaces connected to GPLC-1.
ZQMF:GTPU,0,L:AA0:1,0,40:1,IPOAUD;
ZQMF:GTPU,1,L:AA0:1,0,41:1,IPOAUD;
ZQMF:GTPU,2,L:AA0:1,0,42:1,IPOAUD;
ZQMF:GTPU,3,L:AA0:1,0,43:1,IPOAUD;
b.
Create IP over ATM interfaces connected to GPLC-2.
ZQMF:GTPU,0,L:AA1:2,0,40:1,IPOAUD;
ZQMF:GTPU,1,L:AA1:2,0,41:1,IPOAUD;
ZQMF:GTPU,2,L:AA1:2,0,42:1,IPOAUD;
ZQMF:GTPU,3,L:AA1:2,0,43:1,IPOAUD;
3.
Assign IP addresses to the network interfaces.
a.
Configure interfaces connected to GPLC-1.
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;
ZQRN:GTPU,1:LO0:10.1.1.3;
ZQRN:GTPU,2:LO0:10.1.1.4;
ZQRN:GTPU,3:LO0:10.1.1.5;
4.
Create the OSPF configuration.
a.
Configure the area(s) that include also the neighbouring
routers.
ZQKE:GTPU,0:0.0.0.1;
ZQKE:GTPU,1:0.0.0.1;
ZQKE:GTPU,2:0.0.0.1;
ZQKE:GTPU,3:0.0.0.1;
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-PS User Plane (RNC-SGSN)
b.
Configure two interfaces for that area. The values for
parameters area identification, hello interval and
router dead interval must be the same as in the SGSN.
Note
we can select AA0 or AA1 as the primary route for user traffic by giving
different ospf costs. The interface with lower cost will be preferred.
c.
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;
Configure the OSPF to inform other OSPF routers of the
loopback address.
ZQKJ:GTPU,0:0.0.0.1:ADD:10.1.1.2:;
ZQKJ:GTPU,1:0.0.0.1:ADD:10.1.1.3:;
ZQKJ:GTPU,2:0.0.0.1:ADD:10.1.1.4:;
ZQKJ:GTPU,3:0.0.0.1:ADD:10.1.1.5:;
Note
If the area in step 4.a is not configured as stub area, redistribution can
be also used to inform the address of LO0.
ZQKU:GTPU,0:IF=LO0;
ZQKU:GTPU,1:IF=LO0;
ZQKU:GTPU,2:IF=LO0;
ZQKU:GTPU,3:IF=LO0;
Example
IP configuration for Iu-PS with dedicated VCC for RT traffic
This example shows how to configure the Iu-PS interface between RNC
and SGSN using dedicated VCC for RT traffic. In the example, every IPoA
interface have 2 VCCs, one is for RT traffic, the other is for NRT traffic.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
83 (145)
IP Connection Configuration for RNC
From RNC’s point of view, the egress traffic is treated according to its QoS
attribute. But for ingress traffic, which VCC will be chosen is determined by
SGSN.
RNC
GTPU-0
AA1
SGSN
10.1.1.10
VPI=0, VCI=38
VPI=0, VCI=39
10.1.1.1
GTPU-1
AA1
10.1.1.11
VPI=0, VCI=40
VPI=0, VCI=41
STM-1 line #1
GTPU-2
AA1
10.1.1.12
VPI=0, VCI=42
GPLC1
VPI=0, VCI=43
10.1.2.1
GTPU-3
VPI=0, VCI=44
AA1
10.1.1.13
GPLC2
VPI=0, VCI=45
STM-1 line #2
= NRT
= RT
Figure 18.
1.
ATM virtual channel connections and IP addresses with 2 VCCs
under one IPoA interface
Create ATM resources
Create the following ATM configuration (for instructions, see
Creating ATM resources in RNC in ATM Resource Management):
STM-1 ATM interface (with interface ID 1). This interface is
connected to SGSN (GPLC-1) via a direct physical connection or via
the SDH transmission network.
In ATM interface 1, one VPLtp with VPI=0.
In ATM interface 1, four VCLtps with VPI=0 and VCI=38, 39, 40, 41.
84 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-PS User Plane (RNC-SGSN)
STM-1 ATM interface (with interface ID 2). This interface is
connected to SGSN (GPLC-2) via a direct physical connection or via
the SDH transmission network.
In ATM interface 2, one VPLtp with VPI=0.
In ATM interface 2, four VCLtps with VPI=0 and VCI=42, 43, 44, 45.
2.
Create IP over ATM interfaces to all GTPUs
a.
Create IP over ATM interfaces connected to GPLC-1
ZQMF:GTPU,0,L:AA1:1,0,38:1,IPOAUD;
ZQMF:GTPU,0,L:AA1:1,0,39:1,IPOART;
ZQMF:GTPU,1,L:AA1:1,0,40:1,IPOAUD;
ZQMF:GTPU,1,L:AA1:1,0,41:1,IPOART;
b.
Create IP over ATM interfaces connected to GPLC-2
ZQMF:GTPU,2,L:AA1:2,0,42:1,IPOAUD;
ZQMF:GTPU,2,L:AA1:2,0,43:1,IPOART;
ZQMF:GTPU,3,L:AA1:2,0,44:1,IPOAUD;
ZQMF:GTPU,3,L:AA1:2,0,45:1,IPOART;
3.
Assign IP addresses to the network interfaces
a.
Configure interfaces connected to GPLC-1
ZQRN:GTPU,0:AA1:10.1.1.10,P:32:10.1.1.1;
ZQRN:GTPU,1:AA1:10.1.1.11,P:32:10.1.1.1;
b.
Configure the interfaces connected to GPLC-2
ZQRN:GTPU,2:AA1:10.1.2.12,P:32:10.1.2.1;
ZQRN:GTPU,3:AA1:10.1.2.13,P:32:10.1.2.1;
4.
Create static routes for GTPUs
With the following default routes, all traffic is forwarded to the GPLC
unit in the SGSN.
ZQKC:GTPU,0::10.1.1.1,:PHY;
ZQKC:GTPU,1::10.1.1.1,:PHY;
ZQKC:GTPU,2::10.1.2.1,:PHY;
ZQKC:GTPU,3::10.1.2.1,:PHY;
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
85 (145)
IP Connection Configuration for RNC
86 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring Signalling Transport over IP for Control Plane
5
Configuring Signalling Transport over IP
for Control Plane
Purpose
The purpose of this procedure is to configure the IP-based signalling
transport over ATM connection for RNC control plane. IP-based Iu-PS, IuCS and Iur SS7 signalling stack can be used. For more detailed
description, refer to Configuring IP-based signalling channels.
Before you start
ATM resources must be created before starting this procedure. Signalling
unit 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/physical
connection type>:<IP interface>:<ATM interface>,
<VPI number>,<VCI number>:[<encapsulation method>],
[<usage|IPOAM def>];
Note
Signalling unit should be an active state before configuration.
2.
Assign IP addresses to both ATM interfaces of a signalling unit
(QRN).
ZQRN:<unit type>,[<unit index>]:<interface name>,
[<point to point interface type>]:<IP address>,[<IP
address type> ]:[<netmask_length>]:[<destination IP
address>]:[<MTU>]:[<state>];
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
87 (145)
IP Connection Configuration for RNC
Note
IP addresses must be assigned from different sub-networks.
3.
Create Static Routes if needed (QKC).
ZQKC: <unit type>, <unit index>:[<destination IP
address>],[<netmask length>]:<gateway IP address>,
[<local IP address>]:[<route type>]:[<route
preference>];
Note
The parameter local IP address is only valid for local IP address based
default route. For normal static routes, you do not need to give the local
IP address. For more information about local IP address based default
routes, refer to Creating and modifying static routes.
Example
The following example shows how to configure ICSU-0 to connect to
SGSN with IP over ATM connection. Suppose the subnet address for IuPS signaling of SGSN is 10.2.3.0/24. The ATM AAL5 connection should
be configured properly beforehand.
ZQMF:ICSU,0,L:AA0:1,0,40:1,IPOAM;
ZQRN:ICSU,0:AA0,N:10.20.1.1,L::10.20.1.2:;
ZQKC:ICSU,0:10.2.3.0,24:10.20.1.2,:LOG:;
88 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-BC (RNC-CBC)
6
Configuring IP for Iu-BC (RNC-CBC)
Purpose
The purpose of this procedure is to configure IP for the Iu-BC interface
between the RNC and the Cell Broadcast Centre (CBC).
All user data and signalling (SABP) traffic goes through the same Interface
Control and Signalling Unit (ICSU). You must configure one VCC and one
static route towards the CBC for the selected ICSU. Static routes are
needed only in the case when the CBC is not directly connected to the
RNC (for example, router is connected between the RNC and the CBC). In
case of ICSU switchover, IP over ATM interface, IP address and static
routes will move to the new unit.
Before you start
The ATM resources for Iu-BC need to be created before this procedure is
commenced. For instructions, see Creating ATM resources in RNC in ATM
Resource Management.
Steps
1.
Check the selected ICSU unit towards the CBC
The RNC allocates the ICSU unit for the CBC when the CBC
reference data is created to the RNC configuration. You can check
the selected ICSU (logical address for the selected ICSU) from the
RNC RNW Object Browser's RNC dialog and core network tab.
For further information of the parameter please refer to the WCDMA
RAN04 Parameter Dictionary documentation: RNC - CBList CBCItem - ICSUforCBC.
Check the ICSU-id based on the logical address selected towards
the CBC.
ZUSI:ICSU;
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
89 (145)
IP Connection Configuration for RNC
2.
Create the IP over ATM interface to selected ICSU
Create the IP over ATM interface to selected ICSU towards the CBC
according to the instructions in Creating and modifying IP over ATM
interfaces.
If you want to distribute incoming traffic between several ICSU units,
then create as many IP over ATM interfaces as needed (one
separate IP over ATM interface for each used ICSU) towards the
CBC. In this case, only selected ICSU unit is sending RNC
originated Restart and Failure messages towards the CBC. The
CBC must be configured to send data to different IP addresses, that
is, to different ICSU units.
When assigning an IP address to the ICSU unit, assign a logical IP
address to the unit by giving value L to the IP address type
parameter.
If you want to configure several IP over ATM interfaces towards the
CBC (distributing incoming traffic between several ICSU units), give
the network interface parameter a different value in all units,
value L to the IP address type parameter, and assign a different IP
address to each unit.
The destination IP address is the address of the router interface
or the CBC interface which terminates the VCC.
3.
Create a static route for Iu-BC
For Iu-BC connections towards the CBC, configure one static route
with route type "LOG" for selected ICSU to the IP address of the
router terminating IP over ATM PVCs. Static routes are needed only
in the case when the CBC is not directly connected to the RNC.
Note
Only static routes can be configured for ICSU units. Static routes are
only required for ICSUs if any of the IP packets have a different
destination address than the IP address of the CBC (for example, if a
router is used between the RNC and CBC), and they are to be
transferred via the VCC.
For IPv4:
90 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-BC (RNC-CBC)
ZQKC:<unit type>,<unit index>:[<destination IP
address>],[<netmask length>]:<gateway IP address>,
[<local IP address>]:<route type>:[<route
preference>];
Note
The parameter local IP address is only valid for the local IP address
based default routes. For normal static routes, you do not need to give
the local IP address. For more information about local IP address based
default routes, refer to Creating and modifying static routes.
For IPv6:
ZQ7C:<unit type>,<unit index>:<destination IP
address>,[<prefix length>]:<gateway IP address>:
[<route type>]:[<route preference>];
Example
Configuring IP for Iu-BC through ICSU units
The following figure shows an example of IP configuration for Iu-BC
interface with IPv4 and IPv6 addresses. The ICSU-0 is selected to be used
towards the CBC.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
91 (145)
IP Connection Configuration for RNC
RNC site
ICSU-0
Core site
Router terminating
IP over ATM PVCs
(can also be an
extra ATM Interface)
MGW
RNC
10.1.1.1
ICSU-1
NIS
NIS
NIS
10.1.1.200
CBC
any
media
ICSU-2
...
STM-1
VPI=x
VPI=y
VP
cross
connects
ICSU-18
subnet 10.1.1.0/32
Figure 19.
Example of IPv4 configuration for Iu-BC
The following examples show how to configure the IP for the Iu-BC
interface between the RNC and the CBC. The ICSU-0 is selected to be
used towards the CBC. The Iu-BC PVCs are configured to the STM-1
interface between the RNC and the MGW. The IPoA PVCs are terminated
in a router. The PVCs can also be terminated in the CBC, if it is located in
the same site.
For IPv4 case:
1.
Create ATM resources as instructed in Creating ATM resources in
RNC in ATM Resource Management.
2.
Create IP over ATM interfaces connected to subnetwork 10.1.1.1/32
to selected ICSU.
ZQMF:ICSU,0,L:AA1:1,0,40:1,IPOAUD;
92 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Configuring IP for Iu-BC (RNC-CBC)
Note
Note: The ICSU-0 is selected to be used towards the CBC.
3.
Assign an IPV4 address to the selected ICSU.
ZQRN:ICSU,0:AA1:10.1.1.1,L:32:10.1.1.200;
4.
Create a static route for selected ICSU.
With the following default routes, all traffic is forwarded to the router
terminating IP over ATM PVCs.
ZQKC:ICSU,0::10.1.1.200,:LOG;
For IPv6 case: with the same figure, replace the IPv4 address "10.1.1.1"
with IPv6 address "3FFE:1200:3012:C020:580:8FFF:FE7A:7BB7" and the
IPv4 address "10.1.1.200" with IPv6 address "3FFE:1200:3012:
C020:580:8FFF:FE7A:4BB4".
1.
Create ATM resources as instructed in Creating ATM resources in
RNCin ATM Resource Management.
2.
Create IPv6 over ATM interfaces connected to subnetwork to
selected ICSU.
ZQMF:ICSU,0,L:AA1:1,0,40:1,IPOAUD;
Note: The ICSU-0 is selected to be used towards the CBC.
3.
Assign an IPv6 address to the selected ICSU.
ZQ6N:ICSU,0:AA1:"3FFE:1200:3012:C020:580:8FFF:
FE7A:7BB7",L:128:"3FFE:1200:3012:C020:580:8FFF:
FE7A:4BB4";
4.
Create a static route for each ICSU.
With the following default routes, all traffic is forwarded to the router
terminating IP over ATM PVCs. A static route is needed for each
ICSU because during the ICSU switchover static route is not
switching to the new unit.
ZQ7C:ICSU,0::"3FFE:1200:3012:C020:580:8FFF:
FE7A:4BB4":LOG;
ZQ7C:ICSU,1::"3FFE:1200:3012:C020:580:8FFF:
FE7A:4BB4":LOG;
...
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
93 (145)
IP Connection Configuration for RNC
ZQ7C:ICSU,18::"3FFE:1200:3012:C020:580:8FFF:
FE7A:4BB4":LOG;
94 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying DNS configuration
7
Creating and modifying DNS
configuration
Purpose
You can create the DNS configuration with the QRK command in IPv4, and
Q6K command in IPv6. The interface-specific instructions for configuring
the DNS can be found in the integration instructions.
Before you start
Note
In addition to the MML based configuration the IP layer can be
configured via the IP plan interface from the NetAct. The IP plan
support does not contain the OSPF configuration.
For more information on the IP plan interface, see IP plan interface in
document RNC Operation and Maintenance.
Steps
1.
Interrogate DNS parameter data
You can interrogate current DNS parameters with QRJ in IPv4, and
Q6J in IPv6. These commands have no parameters.
ZQRJ;
ZQ6J;
Expected outcome
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
95 (145)
IP Connection Configuration for RNC
If the DNS service is utilised in IP data transfer, a common domain
name of the local environment and the DNS server addresses are
displayed. All the computer units of the network element that have IP
services belong to the same domain.
2.
Modify DNS configuration
This command defines whether or not the DNS service is utilised in
IP data transfer. You can also use this command to add a DNS name
server address.
For IPv4:
ZQRK:[<primary DNS server>],[<secondary DNS
server>],[<third DNS server>],[<local domain name>],
[<sortlist>],[<netmask>]:[<resolver cache>],
[<round robin>];
For IPv6:
ZQ6K:[<primary DNS server>],[<secondary DNS
server>],[<third DNS server>],[<local domain name>],
[<sortlist>],[<prefix length>]:[<resolver cache>],
[<round robin>];
3.
Remove DNS name server address from use
For IPv4:
ZQRK:0.0.0.0,0.0.0.0,0.0.0.0,<local domain name>;
For IPv6:
ZQ6K:"::",,,<local domain name>;
If you want to leave the primary DNS server unchanged, do not give
any values for the first parameters. If the first DNS nameserver set to
0.0.0.0, then all those three DNS servers will be disabled.
Example
Enabling and disabling DNS service for IPv4 data transfer
This example shows how to set DNS service for IPv4 data transfer.
ZQRK:172.23.69.12,172.23.69.13,172.23.69.14,"HOST.
NET",10.0.1.0,24:YES,YES:;
96 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying DNS configuration
If you want to disable DNS only in the third DNS server, and keep others,
give the command
ZQRK:,,0.0.0.0,"HOST.NET",10.0.1.0,24:YES,YES:;
Example
Enabling and disabling DNS service for IPv6 data transfer
This example shows how to set DNS service for IPv6 data transfer.
1.
Enable DNS and use IPv6 address
3FFE:1200:333A:444B:555C:666D:777E:888F as primary server,
IP address 3FFE:1200:888A:777B:666C:555D:444E:333F as
secondary server, and
3FFE:1200:333F:444E:555D:666C:777B:888A as the third server.
The domain name is HOST.NET. Network sortlist is
3FFE:1200:3012:C020:0280:5FFF:222A:4BB5 and prefix is 32.
Resolver cache and round robin are in USE status.
ZQ6K: "3FFE:1200:333A:444B:555C:666D:777E:888F",
"3FFE:1200:888A:777B:666C:555D:444E:333F",
"3FFE:1200:333F:444E:555D:666C:777B:88A", "HOST.
NET", "3FFE:1200:3012:C020:0280:5FFF:222A:4BB5",
32:YES,YES;
2.
Disable DNS, change the domain name to STARDUST.COM, and
leave the network sortlist unchanged.
ZQ6K:"::",,,"STARDUST.COM";
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
97 (145)
IP Connection Configuration for RNC
98 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying IP interfaces
8
Creating and modifying IP interfaces
Purpose
You can configure a new network interface or IP address with the QRN
command in IPv4, and Q6N in IPv6. You can find the interface-specific
instructions for configuring IP interfaces in the integration instructions.
Summary
Choose from the steps below the one or the ones that you need.
The last step, Change existing IP configuration for a point-to-point
interface, gives detailed instructions for situations when the destination
address for the IP over ATM interface changes in interfaces where
InATMARP is in use. If you do not block the IPoA interface before
changing the configuration in the IPA2800 network element, the
InATMARP creates a new entry in the routing table and the QRN command
returns error messages.
Steps
1.
Interrogate network interfaces
Check the configured network interfaces of the computer unit before
configuring new ones.
For IPv4:
ZQRI:<unit type>,<unit index>::YES;
For IPv6:
ZQ6I:<unit type>,<unit index>::YES:;
2.
Create IP interfaces
For IPv4:
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
99 (145)
IP Connection Configuration for RNC
ZQRN:<unit type>,<unit index>:<interface name>,
[<point to point interface type>]:[<IP address>],[<IP
address type>]:[<netmask length>]:[<destination IP
address>]:[<MTU>]:[<state>];
For IPv6:
ZQ6N:<unit type>,<unit index>:<interface name>,
[<point to point interface type>]:[<IP address>],[<IP
address type>]:[<prefix length>]:[<destination IP
address>];
Table 4.
MTU values for different units
ISU, ICSU, GTPU
and OMU units
TCU units
IPFGE units
EL
AA
IFETH
AI
IFETH
IFFGE
AI
AA
Min MTU
1500
1
1500
1500
1500
1500
1500
1500
Max MTU
1500
9180
1500
1500
1500
1500
1500
1500
Default
MTU
1500
9180
1500
1500
1500
1500
1500
1500
Note
The MTU value should be set according to the table when you create or
modify the interfaces for the ISU, ICSU, GTPU, OMU, TCU and IPFE
(P), IPGE(P), IPFGE units.
3.
Modify IP interfaces
Identify the IP interface you want to modify with the parameters unit
type, unit index and interface name.
For IPv4:
ZQRN:<unit type>,<unit index>:<interface name>,
[<point to point interface type>]:[<IP address>],[<IP
address type>]:[<netmask length>]:[<destination IP
address>]:[<MTU>]:[<state>];
For IPv6:
100 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying IP interfaces
ZQ6N:<unit type>,<unit index>:<interface name>,
[<point to point interface type>]:[<IP address>],[IP
address type]:[<prefix length>]:[<destination IP
address>];
The numbered or unnumbered point to point interface type
parameter is valid only for ATM point-to-point interfaces. If you want
to change the point-to-point interface type you must remove the
interface by using QRG command for IPv4, Q6G command for IPv6
and configure it to another point-to-point interface type.
N
U
4.
A numbered interface has a unique IP address.
This value is the default.
An unnumbered interface does not have a
unique IP address. It shares its IP address with
the Ethernet interface IP address.
Delete IP interface
Before deleting all IP addresses from the network interface, delete
all the static routes that have been configured for the interface. For
detailed instructions, see Creating and modifying static routes.
For IPv4:
ZQRG:<unit type>,<unit index>:<interface name...>;
For IPv6:
ZQ6G:<unit type>,<unit index>:<interface name...>;
5.
Change existing IP configuration for a point-to-point interface
If you want to change the IP configuration in a point-to-point interface
where 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> | all
def,<VCI> | all def]:<change>;
b.
Delete the existing routing.
If OSPF is in use, delete the OSPF interface:
ZQKL:<unit type>,<unit index>: [<interface
identification>];
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
101 (145)
IP Connection Configuration for RNC
c.
d.
e.
f.
Example
If static routing is in use, delete all the static routes that have
been configured for the interface. For detailed instructions, see
Creating and modifying static routes.
Delete the IP address (QRG)
ZQRG:<unit type>,<unit index>:<interface
name...>;
Create the new IP address (QRN)
ZQRN:<unit type>,<unit index>:<interface name>,
(<point to point interface type>):(<IP
address>),(<IP address type> ):(<netmask
length>):(<destination IP address>):(<MTU>):
(<state>);
Unblock the IPoA VCC (QMG)
ZQMG:UNIT=<unit type> | <ATM=<ATM interface> |
USAGE=<usage> | INDEX=<unit index>:[<VPI> | all
def,<VCI> | all def]:<change>;
Reconfigure routing.
If OSPF is in use, reconfigure the OSPF parameters:
ZQKF:<unit type>,<unit index>:<interface
identification>:<area identification>;
If static routing is in use, create new static routes. For detailed
instructions, see Creating and modifying static routes.
Adding a new IPv4 address to OMU
This example shows how to add a new IP address to the EL0 interface of
the OMU unit with index 0. The IP address of the interface is 10.20.41.130
and netmask length is 24.
ZQRN:OMU,0:EL0:10.20.41.130:24;
Example
Creating a logical IPv4 address for a 2N redundant unit
If you want to create a logical IPv4 address for a 2N redundant unit, do not
give the unit index parameter and set the IP address type parameter
with value L. In this example, the netmask length is 27 and the status is set
to UP.
ZQRN:OMU:EL0:131.228.45.179,L:27:::UP;
Example
Changing the existing IPv4 configuration for a point-to-point
interface
This example changes the IPv4 configuration for OMU interface AA11.
102 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying IP interfaces
1.
Block the IPoA VCC (QMG)
ZQMG:ATM=11:0,32:2;
2.
Delete the OSPF interface in OMU-1 (QKL)
ZQKL:OMU,1:AA11;
3.
Delete the IP address in OMU-1 (QRG)
ZQRG:OMU,1:AA11;
4.
Create the new IP address (QRN)
ZQRN:OMU:AA11,U:10.1.1.2,L::10.1.12.1:1500:UP;
5.
Unblock the IPoA VCC (QMG)
ZQMG:ATM=11:0,32:1;
6.
Reconfigure the OSPF parameters (QKF)
ZQKF:OMU,1:AA11:10.1.12.0;
ZQKF:OMU,0:AA11:10.1.12.0;
Example
Creating a logical IPv6 address for a 2N redundant unit
This example shows how to add a logical IPv6 address to the EL0
interface of OMU unit.
ZQ6N:OMU:EL0:"3FFE:1200:3:12:C020:280:5FFF:FE4A:4BB7",
L;
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
103 (145)
IP Connection Configuration for RNC
104 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Modifying IP parameters
9
Modifying IP parameters
Purpose
You can specify the parameters specific to the IP protocol stack with the
QRT command in IPv4. You can set host names, define if the unit forwards
IP packets, set the maximum time-to-live value and define if the subnets
are considered to be local addresses. The IP parameters can be deleted
using QRV command.
You can specify the parameters specific to the IP protocol stack with the
Q6T command in IPv6. You can define if the unit forwards IPv6 packets, set
the hop limit value and define if the unit receives router advertisements.
The IP parameters can be deleted with the Q6V command.
Before you start
Note
In addition to the MML based configuration the IP layer can be
configured via the IP plan interface from the NetAct. For further details
on the IP plan interface see IP plan interface in document RNC
Operation and Maintenance.
Steps
1.
Interrogate TCP/IP parameters
For IPv4:
ZQRH:<unit type>,<unit index>;
For IPv6:
ZQ6H:<unit type>,<unit index>:;
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
105 (145)
IP Connection Configuration for RNC
2.
Modify TCP/IP parameters
For IPv4:
The default value for TTL is 64, and for SNL is YES.
Note
Chorus units do not support local subnets (SNL).
ZQRT:<unit type>,<unit index>:(HOST=<host name>,
[IPF=<IP forwarding>],[TTL=<IP TTL>],[SNL=<subnets
are local>]);
For IPv6:
ZQ6T:<unit type>,<unit index>:(IPF=<IP forwarding>,
[HLIM=<hoplimit>],[RADV=<router advertisment>]);
3.
Delete TCP/IP parameters
For IPv4:
ZQRV:<unit type>,[<unit index>];
For IPv6:
ZQ6V:<unit type>,[<unit index>];
Example
Modifying IPv4 parameters in OMU
This example shows how to modify the IP parameters in the OMU unit. Set
the unit type parameter to OMU, and the HOST parameter to what is
detailed in the IP address plan (for example, OMU). In the MGW, set the
IPF parameter to NO and in the RNC to YES. Set the TTL parameter to
default and the SNL parameter to NO.
In the MGW:
ZQRT:OMU,0:HOST="OMU",IPF=NO,TTL=64,SNL=NO;
In the RNC:
ZQRT:OMU,0:HOST="OMU",IPF=YES,TTL=64,SNL=NO;
106 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Modifying IP parameters
Example
Modifying IPv6 parameters in OMU
This example shows how to modify the IP parameters in the OMU unit. Set
the unit type parameter to OMU. In the MGW, set the IPF parameter to
OFF and in the RNC to ON. Set the HLIM parameter to default and the
RADV parameter to OFF.
In the MGW:
ZQ6T:OMU,0:IPF=OFF,HLIM=64,RADV=OFF;
In the RNC:
ZQ6T:OMU,0:IPF=ON,HLIM=64,RADV=OFF;
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
107 (145)
IP Connection Configuration for RNC
108 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying IP over ATM interfaces
10
Creating and modifying IP over ATM
interfaces
Purpose
This procedure describes how to interrogate, create, and modify both
internal and external IP over ATM (IPoA) interfaces. The interface-specific
instructions for configuring IP interfaces can be found in the integration
instructions.
Before you start
The ATM interfaces and external termination points have to be configured
before you can configure external IPoA interfaces. For more information,
refer to ATM resources in ATM Resource Management.
You need the ATM virtual channel configuration information when you
create external IPoA interfaces. You have to know the “interface
identification” values of the network interface units, virtual path identifiers
(VPI), and virtual channel identifiers (VCI). If you do not have this
information, you can use LAI and LCI commands to interrogate ATM
interfaces and external termination points.
Steps
1.
Interrogate external IP over ATM interfaces (QMI)
ZQMI:[<unit type>],[<unit index>],[<logical/
physical connection type>]:[<IP interface>]:[<ATM
interface>],[<VPI>],[<VCI>]:[<encapsulation>]:
[<state>];
2.
Create external IP over ATM interfaces (QMF)
The QMF command creates a VC from an external termination point
at the unit to the internal termination point in the computer unit and
attaches the new VC to an IP interface.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
109 (145)
IP Connection Configuration for RNC
ZQMF:<unit type>,[<unit index>],<logical/physical
connection type>:<IP interface>:<ATM interface>,
<VPI number>,<VCI number>:[<encapsulation method>],
[<usage | IPOAM def>];
3.
Delete IP over ATM interfaces (QMD)
The ATM interface, VPI number, VCI number parameters define
which external termination point is disconnected from the IP
interface of the unit. These parameters are only needed when
deleting an external connection.
The unit_2 type, unit_2 index and IP interface_2 parameters
are in use only when deleting an internal connection.
ZQMD:<remove type>:<unit type>,[<unit index>]:<IP
interface>:[<ATM interface>],[<VPI number>],[<VCI
number>]:[<unit_2 type>],[<unit_2 index>]:[<IP
interface_2>];
Example
Configuring IP over ATM interface
Configure IP over ATM interface with network interface AA2 to OMU-0
from ATM interface 3 (NIU-1), VPI 20, and VCI 30 with encapsulation
method VCMUX.
ZQMF:OMU,,L:AA2:3,20,30:2;
Configure IP over ATM interface with network interface AA3 to OMU-0
from ATM interface 4 (NIU-2), VPI 20, and VCI 30 with encapsulation
method VCMUX.
ZQMF:OMU,0,P:AA3:4,20,30:2;
Example
Configuring two IPoA connections to one IP over ATM
interfaces
Configure two IPoA connections to IPoA interface AA0 of GTPU-0. The
first IPoA connection is from ATM interface 4(NIU-2), VPI 20 and VCI 30
with encapsulation method LLC/SNAP. The second IPoA connection is
from ATM interface 4(NIU-2), VPI 20 and VCI 31 with encapsulation
method LLC/SNAP.
ZQMF:GTPU,0,L:AA0:4,20,30:1,IPOAUD;
ZQMF:GTPU,0,L:AA0:4,20,31:1,IPOART;
110 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying IP over ATM interfaces
Only GTPU can support two IPoA connections under one IPoA interface.
These two IPoA connections’ usages must be different. Usually one is for
IPOAUD, the other is for IPOART.
Example
Interrogate external IP over ATM interfaces
ZQMI:OMU;
Expected outcome
INTERFACE CONFIGURED FOR EXTERNAL USE:
UNIT&INDEX
---------OMU
OMU-0
DN02143138
Issue 11-3 en
TYPE IP INT
---- -----LOG
AA2
PHY
AA3
ATM IF
-----3
3
VPI
--20
20
VCI
--30
30
# Nokia Siemens Networks
ENC METHOD
---------VCMUX
VCMUX
USAGE
----IPOAM
IPOAM
OPER
STATE
----RUN
RUN
ADMIN
STATE
----UP
UP
111 (145)
IP Connection Configuration for RNC
112 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Modifying OSPF configuration
11
Modifying OSPF configuration
Purpose
You can modify the OSPF router parameters, area parameters, and
interface parameters of an OSPF router after the OSPF configuration has
been created. You can also define a network prefix in the OSPF area,
configure virtual link parameters and define a stub host in the OSPF area.
The interface-specific instructions for configuring OSPF can be found in
the integration instructions.
Steps
1.
Configure OSPF router parameters (QKS)
This command defines the OSPF parameters of an OSPF router.
ZQKS:<unit type>,<unit index>:[MOD|DEL],<router
id>:<rfc1583compatibility>:<spf delay>:<spf hold
time>;
Note
Remove the router parameters with route id 0.0.0.0.
2.
Configure OSPF area parameters (QKE)
This command defines the OSPF area (both backbone and other
area) parameters of an OSPF router.
ZQKE:<unit type>,<unit index>:<area
identification>:<stub area>,[<stub area route
cost>],<totally stubby area>;
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
113 (145)
IP Connection Configuration for RNC
The area identification specifies the area ID for a new OSPF. The
area ID is entered as a dotted-quad. The area ID of 0.0.0.0 is
reserved for the backbone. The IP network number of a subnetted
network may be used as the area ID.
Note
The area parameters do not become effective (written into the
configuration file) until there exists an interface which has the area
attached to itself.
3.
Configure OSPF interface parameters (QKF)
This command defines the OSPF interface parameters of an OSPF
router.
ZQKF:<unit type>,<unit index>:<interface
specification>:<area identification>:[<hello
interval>]:[<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 type
and identification>:<metric>;
5.
Configure network prefix, if required (QKH)
This command defines a network prefix in the OSPF area.
Configuring the network prefix is optional.
ZQKH:<unit type>,<unit index>:<area
identification>:<operation>:<network prefix>:
<network prefix mask length>:<network prefix
restriction>;
6.
114 (145)
Configure virtual link parameters, if required (QKV)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Modifying OSPF configuration
If there is an OSPF area which does not have a physical connection
to the backbone area, use a virtual link to provide a logical path from
the disconnected area to the backbone area. Virtual links have to be
configured to both ends of the link. The command QKV has to be
entered separately for both border routers using the virtual link.
ZQKV:<unit type>,<unit index> :<router
identification>:<transit area>:[<hello interval>]:
[<router dead interval>]:[<authentication> |
<password>];
Area 2
Virtual link
Area 0
Backbone
Border router B
Area 1
Border router A
Figure 20.
7.
Use of virtual link
Configure stub host, if required (QKJ)
This command defines a stub host in the OSPF area. Configuring
the stub host is optional.
ZQKJ:<unit type>,<unit index>:<area
identification>:ADD:<stub host>:[<stub host cost>];
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
115 (145)
IP Connection Configuration for RNC
116 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying static routes
12
Creating and modifying static routes
Purpose
Static routes are used when dynamic routing (for example, OSPF) does
not provide any useful function over the static routes. In other words they
are used when configuring a simple static route achieves the same
objective as using the more complicated dynamic routing. Static routes
can be used with dynamic routing when creating a host route to a host that
does not run dynamic routing.
Particularly, local IP based default routes are a special kind of static routes.
An outgoing IP packet matching a local IP address based default route will
be sent according to its local IP address instead of its destination address.
They usually cooperate with SCTP multihoming to ease the configuration
of static routes on signalling units. Currently, only IPv4 is supported.
Steps
1.
Interrogate IPv4 static routes (QKB)
The display level specifies how to display the search results. This
command displays all possible static routes if the display level is
"ALL"; it only displays current active static routes if it is "ACTIVE". The
default value is "ACTIVE".
ZQKB:[<unit type>,[<unit index>]]:[<destination IP
address>,<netmask length>]]:[<gateway IP address>]:
[<route type>]:[<display level>];
If you do not enter any parameter values, the route information of all
units is listed.
2.
DN02143138
Issue 11-3 en
Add IPv4 static routes (QKC)
# Nokia Siemens Networks
117 (145)
IP Connection Configuration for RNC
a.
b.
3.
Add destination IP address based static routes.
The static route is identified with unit identification, destination
IP address, and next hop address. Unit identification identifies
the unit where the information of unit type and unit index is
used. Destination IP address and netmask length define the
target.
ZQKC:<unit type>,<unit index>:<destination IP
address>,[<netmask length>]:<gateway IP
address>:[<route type>]:[<route preference>];
Add local IP address based static routes.
The local IP address based default route is identified with unit
identification, local IP address, and next hop address. Unit
identification identifies the unit where the information of unit
type and unit index is used.
ZQKC:<unit type>,<unit index>::<gateway IP
address>,<local IP address>;
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 by
source unit identification.
ZQKA:<route number>; or
ZQKA::<unit type>,<unit index>;
You can delete the route by identifying it by its route number. You
can obtain the route number with the QKB command.
ZQKA:<route number>:<unit type>,[<unit index>];
4.
Interrogate IPv6 static routes (Q7B)
ZQ7B:[unit type,[<unit index>]];
If you do not enter any parameter values, the route information of all
units is listed.
5.
Add IPv6 static routes (Q7C)
The static route is identified with unit identification, destination IP
address and next hop address. Unit identification identifies the unit
where this information is used. Destination IP address and prefix
length define the target.
118 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying static routes
ZQ7C:<unit type>,<unit index>:<destination IP
address>,[<prefix length>]:<gateway IP address>:
[<route type>]:[<route preference>];
Note
Logical route is not supported for IPv6. If logical IPv6 address is used,
the same IPv6 static route should be configured on all redundant units.
6.
Delete IPv6 static routes (Q7A)
ZQ7A:<route number>:<unit type>,<unit index>;
Example
Configuring the default static route in OMU
This example shows how to configure the default static route in OMU.
ZQKC:OMU,0::10.20.41.1,:;
Example
Creating the default IPv6 static route for OMU
The same default route is used for both OMU-0 and OMU-1.
ZQ7C:OMU,0&&1::"3FFE:701:33:1A::1";
Example
Configuring redundant static routes in OMU
This example shows how to configure multiple static routes to a same
destination in OMU. Each static route has a different preference. Lower
preference 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 first
static route is used to forward packets. Whenever 10.2.10.1 becomes
down, the second one will take the duty.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
119 (145)
IP Connection Configuration for RNC
120 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying IP QoS configuration
13
Creating and modifying IP QoS
configuration
Purpose
Differentiated Services (DiffServ) is the recommended IP QoS technology
in the UMTS networks and it is supported on GTPUs for Iu-PS user traffic.
There are two traffic classes (TC) supported: RT is for real time and NRT is
for non real time traffic. The IP QoS handling mechanism is different for
downlink and uplink traffic:
.
For downlink traffic, GTPU can classify IP traffic into RT and NRT
and give different scheduling treatment during congestion based on
their weights.
.
For uplink traffic, GTPU can classify IP traffic into RT and NRT, and
transmit them through different VCCs based on the corresponding
IPoA interface parameter (ATM usage tag, refer to IPoA
configuration). It is so-called layer-two segregation.
Before you start
IP QoS configuration is only in GTPU for Iu-PS user plane. The same
configuration is for all GTPUs and Iu-PS user plane traffic.
Steps
1.
Interrogate IP QoS configuration (Q8I)
ZQ8I;
2.
Enable or disable DiffServ handling (Q8F)
Set the status of DiffServ handling separately by given DiffServ
switches. There are three diffserv switches:
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
121 (145)
IP Connection Configuration for RNC
ING : Switch to enable/disable DiffServ for Iu-PS downlink user
traffic. If it is disabled, all downlink IP traffic will get same treatment
on GTPUs.
SEG: Switch to enable/disable the layer-two segregation feature for
Iu-PS uplink user traffic.
DVCC: Switch to enable/disable using default VCC. This switch is
meaningful only if SEG switch is enabled. If it is disabled, when there
is no corresponding VCC configured for a sending IP packet, the
packet will be dropped. Otherwise, the traffic will be sent through the
default VCC (VCC for NRT traffic if it exists, or VCC for RT traffic).
ZQ8F:[ING=<INGRESS DIFFSERV>|ENA/DIS],[SEG=<Layer 2
SEGREGATION>|ENA/DIS],[DVCC=<USE DEFAULT VCC>|ENA/
DIS];
3.
Create or modify DSCP to traffic Class mapping (Q8C)
Operator can define the mapping from DiffServ code points (DSCP)
to TC. The same mapping is used both for downlink and uplink
traffic.
ZQ8C:<traffic class>:[<data type>]:<DSCP number...
>;
4.
Modify RT and NRT ratio (Q8N)
Basically, this ratio is used for RT and NRT traffic throughput of
downlink traffic. It will probably be adjusted according to the real
traffic situation. It can range from 1 to 50 (decimal). The default value
is 1.
ZQ8N:<BW>;
5.
Configure UMTS traffic class to DSCP (Q8M)
Use this command to configure UMTS traffic class to DSCP
mapping. Operator should give both UNTS TC and DSCP values in
one parameter block. Operator should also give at least one pair of
the mapping data.
UMTS TC value: This parameter identifies the UMTS traffic class.
The value range is from 0 to 6 and it is obligatory.
122 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Creating and modifying IP QoS configuration
DSCP value: This parameter identifies the DSCP value. The value
range is from 0 to 63 and it is obligatory.
ZQ8M:<UMTS TC>,<DSCP>:[<UMTS TC>,<DSCP>:<...>];
6.
Interrogate the UMTS traffic class to DCSP (Q8Q)
ZQ8Q;
Example
IP QoS configuration on GTPU for downlink traffic
Configure the IP QoS configuration for downlink traffic including DSCP to
traffic class mapping. Enable or disable DiffServ handling and RT & NRT
ratio.
1.
Interrogate IP QoS configuration and get the current IP QoS
configuration.
ZQ8I;
2.
Configure the DSCP to traffic class mapping.
ZQ8C:NRT:HEX:"2A";
ZQ8C:RT:DEC:"50,51";
3.
Enable DiffServ for Iu-PS downlink user traffic and use the default
VCC.
ZQ8F:ING=ENA;
4.
Modify RT and NRT ratio.
ZQ8N:7;
Example
IP QoS configuration on GTPU for uplink traffic
Configure the IP QoS configuration for uplink traffic including DSCP to
traffic class mapping. Enable or disable DiffServ handling.
1.
Interrogate IP QoS configuration and get the current IP QoS
configuration.
ZQ8I;
2.
Configure the DSCP to traffic class mapping.
ZQ8C:NRT:HEX:"2A";
ZQ8C:RT:DEC:"50,51";
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
123 (145)
IP Connection Configuration for RNC
3.
Enable layer-two segregation feature for Iu-PS uplink user traffic and
use the default VCC.
ZQ8F:SEG=ENA,DVCC=ENA;
Example
1.
IP QoS configuration on GTPU for UMTS traffic class to DCSP
mapping
Configure the UMTS TC to DCSP mapping
ZQ8M:0,12:1,15:2,20;
2.
Interrogate the UMTS TC to DCSP mapping
ZQ8Q;
124 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
IP configuration files
14
IP configuration files
14.1
IP configuration files
The configuration files for the IP protocol environment are:
Table 5.
Configuration files in the IP protocol environment
Disk file
Data file
Description
POCPROZZ.IMG
/etc/protocols
Known (IP) protocols data.
POCSERZZ.IMG
/etc/services
Known network services data.
POCHOSZZ.IMG
/etc/hosts
Known hosts data.
POCRESZZ.IMG
/etc/resolv.conf
DNS resolver configuration data.
POCFTPZZ.IMG
/etc/ftp.conf
FTP server configuration data.
Note
IP configuration files should be initialized first and can not be modified
by MML commands directly.
Protocols file (/etc/protocols)
The protocols file contains information regarding the known protocols used
on the Internet. The following information is presented for each protocol:
DN02143138
Issue 11-3 en
.
official protocol name
.
protocol number
.
aliases
# Nokia Siemens Networks
125 (145)
IP Connection Configuration for RNC
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 line
are not interpreted by routines which search the file. Protocol names may
contain any printable character other than a field delimiter, new line or
comment character.
The protocol file contains no tags or criticality information. The field is
common for the file and can be determined in advance from Assigned
Numbers and there should be no need to modify the file.
Example
Protocol file
#
# Internet (IP) protocols
#
ip
0
IP
icmp
1
ICMP
igmp
2
IGMP
ggp
3
GGP
tcp
6
TCP
pup
12
PUP
udp
17
UDP
ipv6
41
IPv6
esp
50
ESP
ah
51
AH
icmpv6 58
ICMPV6
ospf
89
OSPFIGP
...
#
#
#
#
#
#
#
#
#
#
#
#
internet protocol, pseudo
internet control message protocol
internet group management protocol
gateway-gateway protocol
transmission control protocol
PARC universal packet protocol
user datagram protocol
Internet Protocol, version 6
Encapsulating Security Payload
Authentication Header
Internet Control Message Protocol v6
Open Shortest Path First IGP
Services file (/etc/services)
The services file contains information regarding the known services
available in the Internet. The following information is presented for each
service:
.
official service name
.
port number
.
protocol name
.
aliases
Items are separated by any number of blanks and/or tab characters. The
port number and protocol name are considered a single item; '/' is used to
separate the port and protocol (for example, 512/tcp). '#' indicates the
beginning of a comment; subsequent characters up to the end of the line
are not interpreted by the routines which search the file.
Service names may contain any printable character other than a field
delimiter, new line, or comment character.
126 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
IP configuration files
The services file contains no tags or criticality information. The file is
common to the whole network element. The contents of the file can be
determined in advance from Assigned Numbers and there should be very
little need to modify the file.
Example
Services file
#
# Network services, Internet style
#
tcpmux
1/tcp
# TCP port multiplexer (RFC1078)
echo
7/tcp
echo
7/udp
discard
9/tcp
sink null
discard
9/udp
sink null
systat
11/tcp
users
daytime
13/tcp
daytime
13/udp
netstat
15/tcp
qotd
17/tcp
quote
msp
18/tcp
# message send protocol
msp
18/udp
chargen
19/tcp
ttytst source
chargen
19/udp
ttytst source
ftp-data
20/tcp
# default ftp data port
ftp
21/tcp
# File Transfer Protocol
ssh
22/tcp
# Secure Shell
ssh
22/udp
telnet
23/tcp
...
Hosts file (/etc/hosts)
The hosts file contains information regarding some hosts on the network.
The following information is presented for each host:
.
internet address
.
official host name
.
aliases
Items are separated by any number of blanks and/or tab characters. '#'
indicates the beginning of a comment; characters up to the end of the line
are not interpreted by routines which search the file.
When using the name server this file provides a backup when the name
server is not running. It is suggested that only a few addresses be included
in this file. These include address for the local interfaces that ifconfig
may need at boot time and a few machines on the local network.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
127 (145)
IP Connection Configuration for RNC
Addresses are specified in the conventional dot notation. Host names may
contain any printable character other than a field delimiter, newline, or
comment character.
The hosts file contains no tags or criticality information. The file is common
to the whole network element. The contents of the file cannot be
determined in advance but a stub file with a localhost entry and
commented examples can be packaged.
Example
Host file
#
# Host Database
#
127.0.0.1
131.228.45.176
131.228.118.232
3ffe:1200:3012:c020::52
localhost
ws20027.ntc.nokia.com
axl01it.ntc.nokia.com
L052.ntc.nokia.com
loopback
ws20027
axl01it
L052
DNS resolver configuration file (/etc/resolv.conf)
The file contains information on DNS resolver configuration. The following
information is presented:
.
name server
.
search list for hostname lookup
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 line
are not interpreted by routines which search the file.
Addresses are specified in the conventional dot notation. Names may
contain any printable character other than a field delimiter, newline, or
comment character.
The DNS resolver configuration file contains no tags or criticality
information. The file is common to the whole network element. The
contents of the file cannot be determined in advance but a stub file with a
localhost entry and commented examples can be packaged.
Example
DNS resolver file
#
# resolv.conf - DNS resolver configuration
#
# The different configuration options are:
#
# nameserver Internet address (in dot notation) of a name server that the
128 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
IP configuration files
#
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 initialisation
parameters for the FTP servers.
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 line
are not interpreted by routines which search the file.
For each unit, the options are in between unit and endunit tags.
Note
FTP server is on OMU only.
The following options can be specified:
Table 6.
FTP server configuration file parameters
Option tag
Parameters
Description
log
Log file name (optional,
default is /RUNNING/
ASWDIR/FTPSERVR.XML,
backup is /RUNNING/
If log file name is specified, the FTP events are
recorded into this file.
ASWDIR/FTPSERVER.OLD)
logwrap
Bytes count (decimal
integer)
When this amount of bytes has been written to
logfile, the log file is closed and renamed with a
new 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 after
500000 bytes.
Note that this option is not effective unless the
log option tag has also been specified.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
129 (145)
IP Connection Configuration for RNC
Table 6.
FTP server configuration file parameters (cont.)
Option tag
Parameters
Description
inact
Inactivity timer (decimal
integer)
The value of control connection inactivity timeout, in seconds.
If the option is not specified, inactivity timer of
600 seconds is used.
checkport
If specified, the parameters of received PORT
command are checked.
Example
FTP server configuration file
#ftp.conf
#
# start in OMU with logging and inactivity timer of 600 seconds
#
unit OMU
log /RUNNING/ASWDIR/FTPSERVER.XML
inact 600
logwrap 500000
endunit
#
#
#
14.2
Modifying IP configuration files
Purpose
The configuration files for the IP protocol environment rarely need to be
modified, but if necessary, use an internal or external text editor for
modifications. These files cannot be modified by using MML commands.
Note
Be careful when editing the configuration files manually.
The files POCPROZZ.IMG, POCSERZZ.IMG and POCHOSZZ.IMG can be
configured manually.
130 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
IP configuration files
Steps
1.
Modify the file in an internal or external text editor
Note
Modify files in OMU RAM (for example, under directory /etc/) instead of
files in hard disk (for example, POCPROZZ.IMG). A file can be
downloaded from OMU by FTP, modifed by an external text editor and
uploaded to OMU by FTP finally.
2.
Propagate a configuration file within a network element
ZQRF:<file name>;
Or
ZQ6F:<file name>;
The command will also save the changed file to hard disk.
3.
Modify the file in an internal or external text editor
Example
Propagating hosts file
ZQRF:"/etc/hosts";
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
131 (145)
IP Connection Configuration for RNC
132 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Connection to IP application from remote host fails
15
Connection to IP application from remote
host fails
Description
The following problems are divided according to the output you get when
you try to contact an IP application in the network element. If you receive
no 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.
Recovery
procedures
The following steps will help to locate/solve the problem.
In addition, there are several error messages, which may appear when the
connection to IP application from a remote host fails. If you get an error
message, you can check the corresponding procedure directly.
.
Connection refused
For more information, see Check the state of the EMT (832), Telnet
or FTP service.
.
No route to host
For more information, see Check the routing information.
.
Connection closed by foreign host
For more information, see Investigating the reason for Connection
Closed by Foreign Host error Message.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
133 (145)
IP Connection Configuration for RNC
Check IP-Layer Communication
Steps
1.
Check connection
Use the ping (or traceroute) command from the remote
workstation or node to check the connection. In the QRX command
the unit type and unit index parameters specify the unit which
sends the PING. The host or IP address parameter specifies the
unit 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 your
DNS server.
.
IP Routing failed
For more information, see Check the routing information and
Check the IP routing settings.
.
Network interface status
For more information, see Check the connected network
interface.
If IP-Layer communication is ok, then we need check the status of
upper-layer (TCP/UDP) communcation and IP application. The
possible problems are as follows:
.
IP application is not running
For more information, see Check the state of the EMT (832),
Telnet or FTP service.
.
Connection refused by IP application
For more information, see Check the state of the EMT (832),
Telnet or FTP service.
.
Connection closed by IP application
134 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Connection to IP application from remote host fails
For more information, see Investigating the reason for
Connection Closed by Foreign Host error Message.
Check the DNS configuration
Purpose
If an error message such as “hostname resolution failure” shows on your
workstation, check the DNS configuration on the workstation and DNS
server.
Steps
1.
Check the DNS Configuration on your workstation
Refer to the guideline provided by workstation vender for more
details.
Expected outcome
The IP address of the RNC's hostname should be resolved correctly
on the workstation.
Check the routing information
Purpose
This is applied when getting an error message, for example, “No route to
host”.
Steps
1.
Check the routing table in your workstation when error
message comes from your workstation.
Refer to the guideline provided by workstation vender for more
details.
Expected outcome
There should exist a route to the RNC in question.
2.
If the error message is from RNC,
Then
QRS command can be used to check the routing table in RNC
unit.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
135 (145)
IP Connection Configuration for RNC
ZQRS:<unit type>,<unit index>:ROU;
Check whether the concerned IP address appears in the output. If
not, check whether routing is configured correctly on RNC. For more
information, 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 network
element are configured properly
Then
a.
b.
c.
d.
e.
f.
Interrogate OSPF parameters.
ZQKI:<unit type>,<unit index>;
Interrogate OSPF area parameters.
ZQKN:[<unit type>,<unit index>]:[<area
idenitification>];
Interrogate OSPF interface parameters.
ZQKR:[<unit type>,<unit index>]:[<interface
identification>];
Interrogate virtual link parameters.
ZQKW:[<unit type>,<unit index>];
Interrogate redistribute parameters.
ZQKY:[<unit type>,<unit index>]:[<redistribute
type>];
Check the OSPF settings defined in the other nodes according
to 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.
136 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Connection to IP application from remote host fails
Check the connected network interface
Purpose
Check the administrative and operational state of connected network
interface. Also, check that the connected network interface has the same
IP 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 shown
by the QRI command. Also check that the IP address tried from the client
is 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 in
the 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 number
of active connections for that application type should not exceed the
maximum number of connections:
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
137 (145)
IP Connection Configuration for RNC
UNIT: <unit type>-<unit index>
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address
tcp
0
35
x.x.x.x.telnet y.y.y.y.y.zzzz
.
.
tcp
0
0
*.832
*.*
tcp
0
0
*.ftp
*.*
tcp
0
0
*.telnet
*.*
(state)
ESTABLISHED
LISTEN
LISTEN
LISTEN
If you checked the state of BS-O&M in RNC, the output also contains the
line
tcp
0
0
*.BS-O&M
*.*
LISTEN
Unexpected outcome
If the contacted IP application does not exist in the network element or if its
state is other than LISTEN, contact Nokia Customer Service.
Investigating the reason for Connection Closed by Foreign Host error
message
Purpose
The IP application in the network element has for some reason closed the
connection, for example, the computer unit with the IP application has
restarted.
Steps
1.
Try to re-establish the connection to be sure that there was not
just a temporary breakdown
2.
Check the states of the applications (QRS)
Check the states of the applications by QRS command according to
Check 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.
138 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Connection to IP application from remote host fails
Note
If step 1 and step 2 still failed to resolve the problem, it might be due to
IP layer communication failure. Refer to Check IP layer communication.
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
139 (145)
IP Connection Configuration for RNC
140 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Related Topics
Related Topics
IP connection configuration for RNC O&M
Instructions
OMS TCP/IP network
Configuring IP for O&M backbone (RNC - NetAct)
Configuring IP for BTS O&M (RNC - BTS/AXC)
Descriptions
IP configuration files
OMS TCP/IP network
Instructions
IP connection configuration for RNC O&M
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
141 (145)
IP Connection Configuration for RNC
IP configuration for Iu-BC interface
Instructions
Configuring IP for Iu-BC (RNC — CBC)
IP configuration files
Configuring IP for O&M backbone (RNC — NetAct)
Instructions
IP connection configuration for RNC O&M
Creating MMI user profiles and user IDs for remote
connections to NetAct
Instructions
Configuring IP for O&M backbone (RNC — NetAct)
Configuring IP stack in OMU
Instructions
Configuring IP for O&M backbone (RNC - NetAct)
Creating and modifying DNS configuration
Modifying IP parameters
Creating and modifying IP interfaces
142 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Related Topics
Creating OSPF configuration for O&M connection
to NetAct
Instructions
Configuring IP for O&M backbone (RNC - NetAct)
Modifying OSPF configuration
Configuring static routes for the O&M connection
to NetAct
Instructions
Configuring IP for O&M backbone (RNC - NetAct)
Creating and modifying static routes
Configuring ESA12
Instructions
Configuring IP for O&M backbone (RNC – NetAct)
Configuring ESA24
Instructions
Configuring IP for O&M backbone (RNC — NetAct)
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
143 (145)
IP Connection Configuration for RNC
Connecting to O&M backbone via ATM interfaces
Instructions
Configuring IP for O&M backbone (RNC - NetAct)
Creating and modifying IP over ATM interfaces
Creating and modifying IP interfaces
Configuring IP for BTS O&M (RNC-BTS/AXC)
Instructions
IP connection configuration for RNC
Configuring IP for Iu-PS User Plane (RNC-SGSN)
Instructions
IP configuration for Iu-PS interface
Configuring IP for Iu-BC (RNC-CBC)
Descriptions
IP configuration for Iu-BC interface
144 (145)
# Nokia Siemens Networks
DN02143138
Issue 11-3 en
Related Topics
Creating and modifying IP interfaces
Instructions
Modifying IP parameters
Modifying IP parameters
Instructions
Creating and modifying IP interfaces
Modifying IP configuration files
Descriptions
IP configuration files
DN02143138
Issue 11-3 en
# Nokia Siemens Networks
145 (145)