Int CFG Ip MCRNC

Parameter Operating
Documents, Issue 04, WCDMA

RAN and I-HSPA, Rel. RU30,
Operating Documentation,
Issue 04
Integrate and Configure
Configuring IP Connection for

Multicontroller RNC
DN0974301
Issue 01F
Approval Date 2011-07-26
Confidential
Configuring IP Connection for Multicontroller 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 DOCUMENTA-
TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-
RECT, 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 2011. All rights reserved
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the “Legal, Safety
and Environmental Information” part of this document or documentation set.
The same text in German:
f Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-
anforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,
Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-
satzes.
2 Id:0900d805808a1bb0 DN0974301
Confidential Issue 01F
Table of contents
This document has 155 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Overview of IP connection configuration . . . . . . . . . . . . . . . . . . . . . . . . 11

1.1 Multicontroller RNC logical interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Overview of IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.1 Multicontroller RNC site solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.2 Link aggregation groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.3 VLAN interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.4 IP interface hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.5 External connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3 IP termination and redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3.1 Transport solution related Functional Units . . . . . . . . . . . . . . . . . . . . . . 15
1.3.2 User Plane Recovery Group, QNUP . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.3.3 Iub Control Plane Recovery Group, QNIUB. . . . . . . . . . . . . . . . . . . . . . 16
1.3.4 Iu/Iur Control Plane IP termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3.5 O&M Recovery Group, QNOMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3.6 Service Area Broadcast RG, QNCFCP . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.4 IP plan interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2 Configuring IP interfaces . . . . . . . . . . . . . . . ....... .............. 22

2.1 Configuring Ethernet interface . . . . . . . . . . . ....... .............. 22
2.2 Configuring VLAN interfaces . . . . . . . . . . . . ....... .............. 25
2.3 Configuring link aggregation groups . . . . . . ....... .............. 28
2.4 Configuring IP address for interfaces. . . . . . ....... .............. 31
3 Configuring Iu, Iub and Iur interfaces. . . . . . . . . . . . . ...... ....... . 34

3.1 Configuring Iu-PS interface . . . . . . . . . . . . . . . . . . . . ...... ....... . 34
3.2 Configuring Iu-CS interface . . . . . . . . . . . . . . . . . . . . ...... ....... . 44
3.3 Configuring Iur interface . . . . . . . . . . . . . . . . . . . . . . ...... ....... . 54
3.4 Configuring Iub interface . . . . . . . . . . . . . . . . . . . . . . ...... ....... . 63
3.4.1 Configuring IP resources for Iub control plane. . . . . . ...... ....... . 71
3.5 Configuring IP for Iu-BC interface (RNC - CBC) . . . . ...... ....... . 78
3.6 Configuring IP interfaces with OSPF, stub area . . . . ...... ....... . 82
4 Configuring IP for O&M connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

4.1 O&M connectivity, solution 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.2 O&M connectivity, solution 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5 Configuring routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.1 Configuring routing global parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.2 Configuring static routes for IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.3 Configuring OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.3.1 Configuring OSPFv2 overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.3.2 Configuring OSPFv2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.3.3 Redistributing routes to OSPF protocol . . . . . . . . . . . . . . . . . . . . . . . . 116
5.3.3.1 Redistribute static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.3.3.2 Redistribute aggregate routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
DN0974301 Id:0900d805808a1bb0 3
Confidential
5.3.3.3 Redistribute direct routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

5.4 BFD configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.4.1 BFD protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.4.2 Configuring the BFD multihop session . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.4.3 Displaying the runtime information for the multihop BFD session . . . . 122
6 Configuring IP-based route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
7 QoS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

7.1 QoS configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
7.2 Configuring QoS for IP-based route . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.2.1 Configuring DSCP to PHB mapping profile. . . . . . . . . . . . . . . . . . . . . . 133
7.2.2 Configuring PHB profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
7.2.3 Configuring and showing IP-based route QoS parameters . . . . . . . . . 138
7.3 Configuring QoS on interface level . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
7.3.1 Configuring ACL settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
7.3.2 Configuring queue sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.3.3 Configuring VLAN priority mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . 149
8 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8.1 Connection to the application RG from remote host fails . . . . . . . . . . . 151
8.2 mcRNC connectivity fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
4 Id:0900d805808a1bb0 DN0974301
Confidential
List of figures
Figure 1 Logical interfaces of the Multicontroller RNC. . . . . . . . . . . . . . . . . . . . . 11
Figure 2 mcRNC transport site solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 3 IP interface hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 4 Functional Units in mcRNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 5 QNUP Recovery Units allocation in 2 BCN modules setup . . . . . . . . . . 16
Figure 6 QNIUB active Recovery Units allocation in 2 BCN modules setup . . . . 17
Figure 7 Load sharing and IP addressing in 4 EIPU nodes setup . . . . . . . . . . . . 18
Figure 8 IP plan interface object model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 9 Network configuration for Iu-PS interface . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 10 Network configuration for Iu-CS interface . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 11 Network configuration for Iur interface . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 12 mcRNC IP-based Iub connectivity for Flexi Multiradio WCDMA BTS . . 63
Figure 13 IPv4 configuration for Iu-BC 1GE connectivity. . . . . . . . . . . . . . . . . . . . 80
Figure 14 OSPF area scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 15 O&M connectivity, solution 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Figure 16 O&M connectivity, solution 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 17 OSPF area scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 18 Traffic scheduling hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 19 mcRNC redundant configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
DN0974301 Id:0900d805808a1bb0 5
Confidential
List of tables
Table 1 Logical interfaces in the mcRNC System . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 2 mcRNC IP plan and SCLI relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 3 Parameters for Ethernet interface configuration . . . . . . . . . . . . . . . . . . 23
Table 4 Parameters of VLAN interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 5 Parameters for link aggregation groups . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 6 Parameters for add networking address . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 7 Parameters for delete networking address . . . . . . . . . . . . . . . . . . . . . . 32
Table 8 Routing table for ingress traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 9 Routing table for egress traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 10 Routing table for ingress traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Table 11 Routing table for egress traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 12 Trace options and values for routing configuration . . . . . . . . . . . . . . . . 97
Table 13 Parameters for configuring static routes . . . . . . . . . . . . . . . . . . . . . . . 101
Table 14 Commands for configuring OSPF areas . . . . . . . . . . . . . . . . . . . . . . . 106
Table 15 Commands for configuring OSPF interfaces . . . . . . . . . . . . . . . . . . . . 109
Table 16 The commands for configuring global OSPF parameters . . . . . . . . . . 111
Table 17 Parameters for monitoring OSPF protocol . . . . . . . . . . . . . . . . . . . . . . 112
Table 18 The OSPFv2 configuration parameters. . . . . . . . . . . . . . . . . . . . . . . . 115
Table 19 Parameters for redistributing routes between protocols . . . . . . . . . . . 117
Table 20 Mandatory and optional parameters for the BFD commands . . . . . . . 120
Table 21 Parameters for the show networking interface command . . . . . . . . . . 122
Table 22 Mandatory parameters for add ipbr command . . . . . . . . . . . . . . . . . . . 123
Table 23 Optional parameters for add ipbr command . . . . . . . . . . . . . . . . . . . . 124
Table 24 Parameters for show ipbr command . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Table 25 Parameters for add ipro command . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Table 26 Parameters for set ipro command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Table 27 Parameters for show ipro command . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Table 28 Parameters for delete ipro command . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Table 29 Parameters for delete ipbr command . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Table 30 Scheduling methods used for logical interfaces . . . . . . . . . . . . . . . . . . 131
Table 31 DSCP encoding for different UMTS QoS classes or DiffServ PHB types. .
132
Table 32 DSCP to PHB mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Table 33 Parameters used with show qos-profile idsp command . . . . . . . . . . . . 138
Table 34 Parameters used with show qos-profile iphb command . . . . . . . . . . . 138
Table 35 Parameters used with set ipbr command . . . . . . . . . . . . . . . . . . . . . . . 138
Table 36 Parameters for ACL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Table 37 Queue set with default values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Table 38 Parameters for set networking qset command . . . . . . . . . . . . . . . . . . 147
Table 39 Parameters for add networking vlanmapping command . . . . . . . . . . . 149
6 Id:0900d805808a1bb0 DN0974301
Confidential
Configuring IP Connection for Multicontroller RNC 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 01E (2011-06-22, WCDMA RAN and I-HSPA, Rel. RU30,
Operating Documentation, Issue 03) and 01F (2011-07-26, WCDMA RAN and I-
HSPA, Rel. RU30, Operating Documentation, Issue 03, Doc Change Delivery 1)
Configuring Ethernet interface (2.1)

• A note is added to step Add an Ethernet interface to the physical port..
• Parameter shared is added to commands show networking ether and add
networking ether.
Configuring VLAN interfaces (2.2)

• Syntax for command set networking vlan is updated in step Change the
settings of the VLAN interfaces. due to software change.
Configuring link aggregation groups (2.3)

• A note is added to step Add link aggregation.
Configuring Iu-PS interface (3.1)

• Steps Configure the physical interface in the whole Chapter 3 have been updated
with the mcRNC default egress queue set.
Configuring IP-based route (6)

• Parameters owner, ip-address, ipbr-id and iface are changed to mandatory in step
Change settings of IP address and IP-based route association..
• (Date)Parameter dspm-profile-id is updated in Optional parameters for add ipbr
command due to software change.
Configuring DSCP to PHB mapping profile (7.2.1)

• The printout of the example in step 2 is modified.
Changes between issues 01D (2011-03-31, WCDMA RAN, Rel. RU30, Issue 02) and
01E (2011-06-22, WCDMA RAN and I-HSPA, Rel. RU30, Operating Documentation,
Issue 03)
IP termination and redundancy (1.3)

• Figure 5 QNUP Recovery Units allocation in 2 BCN modules setup and Figure 6
QNIUB active Recovery Units allocation in 2 BCN modules setup have beenup-
dated.
Iu/Iur Control Plane IP termination (1.3.4)
• Figure 7 Load sharing and IP addressing in 4 EIPU nodes setup has been updated.
IP plan interface (1.4)
• Figure 8 IP plan interface object model has been updated.
DN0974301 Id:0900d805808abe6d 7
Confidential
Summary of changes Configuring IP Connection for Multicontroller RNC
Configuring Ethernet interface (2.1)

• A note is added to step Change settings of the Ethernet interface due to soft-
warechange.
Configuring VLAN interfaces (2.2)
• Parameter newvrf is added due to the introduction of the feature RAN2257:Sup-
port of Virtual Routing and Forwarding in mcRNC.
• A note is added to step Change the settings of the VLAN interfaces due to soft-
warechange.
Configuring link aggregation groups (2.3)
• Parameter newvrf is added due to the introduction of the feature RAN2257:Sup-
port of Virtual Routing and Forwarding in mcRNC.
• A note is added to step Change the settings of the link aggregation group due tosoft-
ware change.
Configuring IP address for interfaces (2.4)
• Step Modify IP address assigned to a network interface is added due to soft-
warechange.
• The IPRO managed object structure is changed in step Configure user planere-
sources, IP-based route configuration.
• Step Check the node’s internal IP addresses with role “cfeigw” for the redundant-
static routes configuration has been removed.
• Step Configure the static routes has been updated.
Configuring Iu-CS interface (3.2)
Configuring Iur interface (3.3)
Configuring Iub interface (3.4)
• Sub-chapter Configuring IP resources for Iub control plane has been updated. Anew
parameter vrf-id is added.
Changes between issues 01C (2011-01-26, Nokia Siemens Networks WCDMA

RAN, Rel. RU30, Issue 01, Doc Change Delivery 1) and 01D (2011-03-31, WCDMA
RAN, Rel. RU30, Issue 02)
8 Id:0900d805808abe6d DN0974301
Confidential
Configuring IP Connection for Multicontroller RNC Summary of changes
Overview of IP configuration (1.2)

• Chapters Multicontroller RNC site solution, Link aggregation groups, VLAN inter-
faces, IP interface hierarchy, External connectivity have been updated.
• Figure Multicontroller RNC site solution has been updated. The following figures
have been removed: Link aggregation groups, VLAN interfaces.
• The site solution figure changed because ToP server location moved.
IP interface hierarchy (1.2.4)
• Figure IP interface hierarchy has been updated.
IP termination and redundancy (1.3)
• Chapter IP termination and redundancy has been updated.
• Chapter IP termination and redundancy has been added.
IP plan interface (1.4)
• Chapter IP plan interface has been added.
• Figure Figure 8 IP plan interface object model has been updated.
• Chapter Configuring Iu-PS interface has been added.
• Chapter Configuring Iu-PS interface has been updated.
Configuring Iu-CS interface (3.2)
• Chapter Configuring Iu-CS interface has been added.
• Chapter Configuring Iu-CS interface has been updated.
Configuring Iur interface (3.3)
• Chapter Configuring Iur interface has been added.
• Chapter Configuring Iur interface has been updated.
Configuring Iub interface (3.4)
• Chapter Configuring Iub interface has been added.
• Chapter Configuring Iub interface has been updated.
Configuring IP interfaces with OSPF, stub area (3.6)
• Chapter Configuring IP interfaces with OSPF, stub area has been added.
• Chapter Configuring IP interfaces with OSPF, stub area has been updated.
Configuring IP-based route (6)
• Parameter phb-set added.
• Purpose section and Before you start section are changed.
Connection to the application RG from remote host fails (8.1)
• This is a new chapter.
mcRNC connectivity fails (8.2)
• This is a new chapter.
DN0974301 Id:0900d805808abe6d 9
Confidential
Summary of changes Configuring IP Connection for Multicontroller RNC
10 Id:0900d805808abe6d DN0974301
Confidential
Configuring IP Connection for Multicontroller RNC Overview of IP connection configuration
1 Overview of IP connection configuration
1.1 Multicontroller RNC logical interfaces

3GPP defines a set of logical interfaces which the Multicontroller RNC (mcRNC) network
element supports as shown in Figure1 Logical interfaces of the Multicontroller RNC.
NetAct
Iu-CS CS
O&M Core Network
BTS Iub
mcRNC
Iu-PS
PS
Core Network
Iur Iu-BC Iu-PC
CBC
RNC CBC SAS

Figure 1 Logical interfaces of the Multicontroller RNC
Table 1 Logical interfaces in the mcRNC System presents description of the logical
interfaces in the mcRNC network.
Interface Description
Iu-CS Logical interface between the radio network controller (RNC) and
circuit switched core network.
Iu-PS Logical interface between the RNC and the packet core network.
Iur Logical interface for the interconnection of two neighboring RNCs.
Iub Logical interface between the RNC and the WBTS.
Iu-BC Logical interface between the RNC and the cell broadcast center
(CBC).
Iu-PC Logical interface between the RNC and the Stand-alone SMLC (SAS).
O&M Proprietary management interface between the network management
system (NMS) and RNC.
Table 1 Logical interfaces in the mcRNC System
DN0974301 Id:0900d805808abca0 11
Confidential
1.2 Overview of IP configuration
1.2.1 Multicontroller RNC site solution

The Multicontroller RNC (mcRNC) reference setup for the CISCO 76xx based site
solution is shown in Figure 2 mcRNC transport site solution.
Cisco
76xx-1
DCN
NetAct
mcRNC
BTS Packet 1588
Network master
Cisco MGW Optional

BTS 76xx-2 co-location
with Core
SGSN
Figure 2 mcRNC transport site solution

The mcRNC module is connected to a pair of Cisco 76xx routers. BTSs are also con-
nected to the routers by a packet network which is attached to WAN interfaces of the
routers. The CN elements are optionally present at the mcRNC site.
Synchronization of the RAN connected to the mcRNC is provided by an external Time-
over-Packet (ToP) server. The ToP is connected to Cisco site routers.
For more information on the mcRNC site solution, see RAN1711: Cisco 76xx as mcRNC
Site Router in WCDMA RAN, Rel. RU30, Feature Descriptions.
1.2.2 Link aggregation groups

Link aggregation groups (LAG) provide increased bandwidth and high reliability by com-
bining several interfaces into one logical link. The mcRNC Ethernet ports can be aggre-
gated into LAGs to provide more than 1 Gigabit bandwidth per logical interface. The Link
Aggregation Control Protocol is used to manage LAGs. Up to eight 1GE ports of the
same mcRNC module can be aggregated within a one LAG. A maximum of eight LAGs
can be supported for the mcRNC within the same module.
For more information on Ethernet link aggregation in the mcRNC, see RAN2256:
Ethernet link aggregation for mcRNC in WCDMA RAN, Rel. RU30, Feature Descrip-
tions.
1.2.3 VLAN interfaces

The mcRNC supports VLANs as a mechanism to enable traffic separation and quality
of service at layer 2. Traffic separation is achieved by using different VLAN IDs for dif-
12 Id:0900d805808abf84 DN0974301
Confidential
ferent types of traffic. L2 prioritization is provided by indicating the desired class of

service in the priority field in VLAN header.
For more information about VLANs, see the Virtual Local Area Networks (VLAN) chapter
in WCDMA RAN IP Transport.
1.2.4 IP interface hierarchy

Figure 3 IP interface hierarchy shows the IP interface configuration hierarchy.
Ethernet port 1 Ethernet port 2 Ethernet port n
Link Aggregation group (LAG)
0..4094 0..4094
1..8 Ethernet ports per
Link Aggregation Group
VLAN Interface
VLANIDx
0..4000 VLAN
interfaces per LAG
0..10 1..10
Up to 10 IP addresses
IP Address IP Address per interface
a.b.c.d a.b.c.d
Figure 3 IP interface hierarchy

Each network interface might have up to 10 IP addresses configured. The Iu/Iur control
plane should be terminated only on the primary interface address.
1.2.5 External connectivity

The mcRNC module provides the following physical interfaces:
• 6 x 10 Gigabit Ethernet (SFP+ plug-in bays)
g Only two 10 Gigabit Ethernet interfaces are available for external connectivity.
• 16 x 1 Gigabit Ethernet (SFP plug-in bays)

• 1 x 1 Gigabit Ethernet for element management/DCN (available in the first two
modules only; SFP plug-in bays)
1GE and 10GE ports are used for the UTRAN traffic handling (for user, control and man-
agement plane). Any interface can be configured and used as an Iu, Iub, or Iur interface.
The following standards are supported:
• 1000Base-TX, RJ45, electrical transmission using twisted pair cable
• 1000Base-SX, LC connector, optical transmission using multi-mode fiber cable
(MMF)
• 1000Base-Lx, LC connector, optical transmission using single-mode fiber cable
(SMF)
DN0974301 Id:0900d805808abf84 13
Confidential
• 10GBase-LR, LC connector, optical transmission using single-mode fiber cable

(SMF)
• 10GBase-SR, LC connector, optical transmission using multi-mode fiber cable
(MMF)
14 Id:0900d805808abf84 DN0974301
Confidential
1.3 IP termination and redundancy

The mcRNC high availability is implemented by using a Recovery Group (RG) concept.
A Recovery Group instance is associated with certain Functional Units. The service
related to the RG is running in the active Recovery Unit (RU). Figure 4 Functional Units
in mcRNC shows the relationship within the mcRNC containing Functional Units. The
Recovery Units, where the actual software is running and the service is terminated, are
the target for the High Availability actions. In case of the software or hardware failure,
the active RU is switched over to another one and the IP layer service termination is
moved to the new unit which is running the active RU.
mcRNC
Functional Recovery
Unit Group (RG)
Recovery
Unit (RU)
Process(es)
Figure 4 Functional Units in mcRNC

The Recovery Group and the active Recovery Unit allocation is statically configured
within the mcRNC, matching the mcRNC load distribution and protection architecture.
This scheme is described in the transport solution related Recovery Groups section.
1.3.1 Transport solution related Functional Units

The following Functional Units are related to the IP transport solution:
• Centralized Functions Processing Units (CFPU)
– O&M traffic
– Iu-BC (Service Area Broadcast)
• External Interfaces Processing Unit (EIPU)
– user plane
– control plane
– Iu-PC (Location Services)
For more details on the functional unit types, see Multicontroller RNC Hardware
Description.
DN0974301 Id:0900d805808abf86 15
Confidential
1.3.2 User Plane Recovery Group, QNUP

The QNUP Recovery Groups terminate the user plane services of all mcRNC logical
interfaces.
The QNUP Recovery Groups have the following functions and characteristics:
• it is bound to EIPU nodes
• holds the termination of IP addresses at the IP layer
• terminates the User Plane connections from any logical interface from several
neighboring nodes
• has a hot active/standby redundancy scheme for end user connection resilience
The active RUs of the QNUP Recovery Groups are allocated according to the following
scheme in order to provide a good basic load distribution. Figure 5 QNUP Recovery
Units allocation in 2 BCN modules setup shows the 2 BCN module configuration with 4
EIPU nodes, 4 QNUP Recovery Group instances and their active RU allocation. Each
EIPU holds an active RU in normal operation. The same allocation principles are
followed in all mcRNC capacity steps. The IP address tied to a certain RG is active only
in the node where the active RU is running.
BCN-1 BCN-2
EIPU-0 EIPU-2 EIPU-1 EIPU-3

Active Standby /QNUP-0
Standby Active /QNUP-1
Active Standby /QNUP-2
Standby Active /QNUP-3
Figure 5 QNUP Recovery Units allocation in 2 BCN modules setup

For the available capacity steps and EIPU group allocation within BCN modules refer to
Multicontroller RNC Product Description.
1.3.3 Iub Control Plane Recovery Group, QNIUB

The QNIUB Recovery Groups terminate the Iub control plane services at the IP/SCTP
layer.
The QNIUB Recovery Groups have the following functions and characteristics:
• it is bound to EIPU nodes
• it holds the termination of Control Plane IP addresses at the IP layer
• terminates connections from several BTSs
• has a cold active/standby redundancy scheme for end user connection resilience
Cold active/standby redundancy scheme is sufficient for Iub control plane resilience.
The provided redundancy mechanism is transparent to a BTS. In order to provide an
optimal basic load sharing, the active RUs of the QNIUB RGs are allocated with the fol-
lowing scheme. Figure 6 QNIUB active Recovery Units allocation in 2 BCN modules
16 Id:0900d805808abf86 DN0974301
Confidential
setup shows 2 BCN module configuration with 4 EIPU nodes, 4 QNIUB Recovery Group
instances, and their active RU allocation. The same allocation principle is followed in all
mcRNC capacity steps.
BCN-1 BCN-2

Active Standby /QNIUB-0
Standby Active /QNIUB-1
Active Standby /QNIUB-2
Standby Active /QNIUB-3
Figure 6 QNIUB active Recovery Units allocation in 2 BCN modules setup
1.3.4 Iu/Iur Control Plane IP termination

The Iu/Iur control plane traffic termination and the SIGTRAN stack implementation is
located in EIPU nodes. The control plane traffic is terminated directly at the network
interface IP addresses, configured to these EIPU nodes. The transport network redun-
dancy is provided by SCTP multihoming, the service level redundancy and load sharing
is handled at the M3UA/SCCP layer.
The SCCP layer contains a hot active/standby redundancy scheme in order to provide
full RANAP/RNSAP resilience. The SCCP layer redundancy scheme is implemented by
the QNIU Recovery Group, which is automatically maintained by the system. The QNIU
RG does not contain the IP addresses and does not require any configuration by the
user. Figure 7 Load sharing and IP addressing in 4 EIPU nodes setup shows the overall
load sharing and IP addressing scheme in case of 4 EIPU nodes setup.
DN0974301 Id:0900d805808abf86 17
Confidential
BCN-1 BCN-2

SCCP
SCCP SCCP
SCCP SCCP
SCCP SCCP
SCCP SCCP
M3UA M3UA M3UA M3UA

SCTP SCTP SCTP SCTP
IP A1 IP A2 IP B1 IP B2 IP C1 IP C2 IP D1 IP D2
Multi-homed Multi-homed Multi-homed Multi-homed

SCTP SCTP SCTP SCTP
Association Association Association Association
#1 #2 #3 #4
Figure 7 Load sharing and IP addressing in 4 EIPU nodes setup

For optimal mcRNC efficiency and superior SIGTRAN redundancy, each peer MSS or
SGSN should be connected to each EIPU by one SCTP association.
1.3.5 O&M Recovery Group, QNOMU

The O&M connections are terminated at the QNOMU Recovery Group.
The QNOMU Recovery Group:
• is bound to CFPU nodes
• contains the IP address(es) of the O&M connections to BTS, OMS and NetAct
The Recovery Unit is active in one of the CFPU nodes.
1.3.6 Service Area Broadcast RG, QNCFCP

The Service Area Broadcast service is terminated at the QNCFCP Recovery Unit, which
is located in CFPU nodes.
The QNCFCP Recovery Group:
• is bound to CFPU nodes
• contains the IP address for the Service Area Broadcast connections towards the
CBC
18 Id:0900d805808abf86 DN0974301
Confidential
1.4 IP plan interface

The mcRNC IP plan interface to NetAct uses similar object model and structure as the
Stuctured Command Line Interface (SCLI). The IP plan interface object model is pre-
sented in Figure 8 IP plan interface object model. The IP plan object description and the
related SCLI command categories are listed in Table 2 mcRNC IP plan and SCLI rela-
tions. The mcRNC IP plan interface supports plan download, activation and upload
operations.
Figure 8 IP plan interface object model
IP plan Object Description SCLI, Structured

Class Command Line Interface
ACL Access Control List. The ACL func- networking acl rule
tionality includes accepting
packets, dropping packets, and
marking the priority of packets
belonging to a certain packet flow.
Table 2 mcRNC IP plan and SCLI relations
DN0974301 Id:0900d805808abf88 19
Confidential

ADDR IP address. Dedicated addresses networking ... address
are assigned directly to the service
(node, recovery group or recovery
unit) that needs external connectiv-
ity.
ADR4GW Static route, gateway address routing ... static-route
AGPRO4 Aggregate route. routing ... aggregate
AGRT4 Aggregate route. The aggregate routing ... aggregate
routes can be configured in order to
reduce the number of routes adver-
tised between the routers.
BFDS BFD (Multi-Hop). Bidirectional For- networking ... bfd
warding Detection (BFD) is a
network protocol used to detect
faults between two forwarding
engines connected by a link.
ETHER Ethernet Interface. Physical inter- networking ether
face configuration.
EXAG4 Export Aggregate Routes. The routing ... export
existing aggregate route (AGRT4)
to be exported.
EXDI4 Export Interface. The existing inter- routing ... export
face to be exported.
EXSR4 Export Static Route. The existing routing ... export
static route (SRT4) to be exported.
FLTR4 Route Filter. Define routes to be fil- routing
tered.
GLPRM Routing instance global parame- set routing ... max-path-
ters. The global parameters for splits, router-id
static route and OSPF.
IDSP DSCP to PHB mapping. The DSCP qos-profile idsp
to PHB mapping is applied for the IP
Based Route scheduling queue
selection.
IP Generic IP parent object for NetAct
IPBR IP Based Route. IP Based Route ipbr
object class.
IPHB IP Based Route Queue. IP Based qos-profile iphb
Route queue settings.
Table 2 mcRNC IP plan and SCLI relations (Cont.)
20 Id:0900d805808abf88 DN0974301
Confidential

IPRO IP Based Route IP address alloca- ipro
tion
IUBSNT Iub SCTP parameters iubsnt
LAGGR Link Aggregation Group networking linkaggr
MD5 OSPF authentication routing ... ospf
O2AREA OSPF v2 Area routing ... ospf
O2GLBL OSPF Global settings routing ... ospf
O2IFC OSPF interface routing ... ospf
O2RNK OSPF priority routing ... ospf
OSTB4 OSPF, Stub area routing ... ospf
OVLNK4 OSPF link routing ... ospf
OWNER Parent Node or Recovery Group networking ... owner
RNG4 Address range. The address routing ... ospf
ranges are used to reduce the
number of routing entries that a
given area emits into the backbone
and thus all areas.
ROUTE4 Aggregate route. routing ... aggregate
RTINST Routing instance within a node networking or routing ...
instance
SRT4 Static route. The static routes can routing ... static-route
be configured by using SRT4 and
ADR4GW object classes.
VLAN VLAN interface networking ... vlan
VLANPM VLAN priority mapping networking vlanmapping
VRF Virtual Routing and Forwarding networking ... vrf
Table 2 mcRNC IP plan and SCLI relations (Cont.)
For more information, see WCDMA RAN Configuration Management and IP Configura-
tion Plan Interface Parameters for Multicontroller RNC.
DN0974301 Id:0900d805808abf88 21
Confidential
Configuring IP interfaces Configuring IP Connection for Multicontroller RNC
2 Configuring IP interfaces
2.1 Configuring Ethernet interface

Purpose
To configure Ethernet interfaces on the Multicontroller RNC module.
Steps
1 Show the current Ethernet interface configuration.

Use the show networking ether command to show the current settings of the
Ethernet interface.
The full syntax of the command is as follows:
show networking [instance <name>] ether [admin <up|down>] [iface
<name>] [ipv4forwarding <yes|no>] [ipv4rpfilter <yes|no>] [mtu
<value>] [outqset <value>] [owner <MO_name>] [port <name>]
[proxy-arp <yes|no>] [shared <yes|no>]
g The instance parameter is used to specify a particular routing instance. The default
value is default. If no instance value is set, the IP configuration of all routing instances
are displayed.
g The parameter enclosed by brackets are optional. For those parameters with a limited
number of values, the values are listed in the angle brackets.
2 Add an Ethernet interface to the physical port.

An Ethernet interface can be created and attached to a physical port (SFP or SFP+
plugin bays). Use the SCLI command as follows:
add networking [instance <name>] ether <owner> iface <name>
port <port_name> [admin <up|down>] [mtu <mtu-size>]
[ipv4forwarding <yes|no>] [ipv4rpfilter <yes|no>] [proxy-arp
<yes|no>] [outqset <name>] [rate-limit <rate-limit>] [shared
<yes|no>]
g The mcRNC specific default physical interface egress queue set is preconfigured in the
system with name rncdefault. Assign this profile to the physical interfaces to enable
proper default egress scheduling weights configuration.
3 Change settings of the Ethernet interface.

Use the set networking ether command to change the current Ethernet interface
settings. The syntax of the command is as follows:
set networking [instance <name>] ether <owner> iface <name>
[admin <up|down>] [ipv4forwarding <yes|no>] [ipv4rpfilter
<yes|no>] [mtu <value>] [outqset <name>]|[deloutqset] [proxy-arp
<yes|no>] [rate-limit <rate-limit>]
22 Id:0900d805808aac99 DN0974301
Confidential
Configuring IP Connection for Multicontroller RNC Configuring IP interfaces
4 Check the Ethernet interface configuration.

Use the show networking ether command to verify if the configuration is success-
ful.
5 Delete the Ethernet interface configuration.

Delete the settings associated with an Ethernet interface so that the default values are
restored. Use the delete networking [instance <name>] ether <owner>
iface <name> command to delete the configuration.
Further information
The following table lists the parameters for configuring Ethernet interface.
Parameter Description Value Range

<owner> This parameter specifies the name of the
managed object that manages the
interface. That is, a node, a recovery
group, a recovery unit or a process. This
is an mandatory parameter.
admin <up|down> The state of the interface. The allowed values are
up and down. Default is
up.
outqset <name> This parameter specifies the name of the
egress queue set which will be used with
this interface. The egress queue set must
be created beforehand. This parameter is
optional.
For more information on queue set, see
Configuring queue sets.
deloutqset This parameter removes the egress
queue set attached to this interface. The
queue set must be created beforehand.
This parameter is optional.
iface <name> The name of the interface where the
changes will be applicable. This is a
mandatory parameter.
instance The networking configuration is applied
to or displayed from the virtual routing
instance specified by this parameter. If
no instance is specified, the configuration
is applied to or displayed from the default
routing instance.
g Note that for mcRNC release 1, only

default routing instance is supported.
ipv4forwarding This parameter specifies if packet The allowed values are
<yes|no> forwarding is allowed for IPv4 traffic. This yes and no. Default value
parameter is optional. is yes.
Table 3 Parameters for Ethernet interface configuration
DN0974301 Id:0900d805808aac99 23
Confidential
Configuring IP interfaces Configuring IP Connection for Multicontroller RNC

ipv4rpfilter This parameter specifies if the reverse The allowed values are
<yes|no> path filter is enabled for IPv4 traffic. This yes and no. Default value
parameter is optional. is no.
mtu <mtu-size> The maximum transmission unit (MTU)
value of the interface.
newvrf <name> The name of the new virtual routing
instance.
g Note that in mcRNC release 1 only

default routing instance is supported.
proxy-arp This parameter specifies if the proxy ARP The values are yes and
<yes|no> is present or not. It is applicable only for no. Default value is no.
IPv4 addresses. This parameter is
optional.
shared <yes|no> Specifies if the SFP port can be shared The values are yes and
by two or more nodes. no. Default value is no.
rate-limit Specifies the rate limit value of the
<rate_limit> physical interface.
Table 3 Parameters for Ethernet interface configuration (Cont.)
24 Id:0900d805808aac99 DN0974301
Confidential
2.2 Configuring VLAN interfaces

Purpose
This section provide instructions on VLAN configuration.
Steps
1 Create VLAN interfaces.

Use add networking vlan command to add new VLAN interface to the configura-
tion. The syntax of the command is as follows:
add networking [instance <name>] vlan <owner> realiface <name>
vid <id> vlaniface <name> [admin <up|down>] [mapping <name>]
[mtu <mtu-size>] [ipv4forwarding <yes|no>] [ipv4rpfilter
<yes|no>] [proxy-arp <yes|no>] [outqset <name>] [rate-limit
<value>]
Example:
Attach the VLAN identifier 120 to the interface_1 interface in the CFPU-0 node by
entering the command below. The corresponding logical interface using this VLAN is
named vlan_1.
add networking vlan /CFPU-0 realiface interface_1 vid 120
vlaniface vlan_1
2 Show the current settings of VLAN interfaces.

The current settings of the VLAN interfaces can be displayed by executing the show
networking vlan command as follows:
show networking [instance <name>] vlan [admin <up|down>] [iface
<name>] [ipv4forwarding <yes|no>] [ipv4rpfilter <yes|no>]
[mapping <name>] [mtu <value>] [owner <MO_name>] [proxy-arp
<yes|no>] [realiface <name>] [vid <vlan_id>] [outqset <name>]
The printout can be, for example:
vlan instance default interfaces:
testVlan
owner : /CFPU-0
realiface : interface_1
vid : 200
MTU : 1500
adminstate : up
IPv4 forwarding : yes
IPv4 rpfilter : no
Proxy ARP : no
3 Change the settings of the VLAN interfaces.

Use the set networking vlan command to change the current settings of the VLAN
interfaces. The syntax of the command is as follows:
DN0974301 Id:0900d805808abaa1 25
Confidential
set networking [instance <name>] vlan <owner> iface <name>

[admin <up|down>] [mapping <name>]|[delmapping] [mtu <mtu-
size>] [ipv4forwarding <yes|no>] [ipv4rpfilter <yes|no>]
[proxy-arp <yes|no>] [outqset <name>]|[deloutqset] [rate-limit
<value>]
4 Delete a VLAN interface.

The command syntax for deleting a VLAN interface is as follows:
delete networking [instance <name>] vlan <owner> iface <name>
Further information
The parameters related to VLAN interfaces are provided in the following table.

<owner> The name of the node or recovery
group that acts as the owner of this
VLAN interface. This parameter is
mandatory.
admin <up|down> The state of the VLAN interface. This The allowed values are up
parameter is optional. and down. Default is up.
delmapping This parameter disables VLAN
priority mapping. It is optional.
deloutqset This parameter restores the default
queue set to this interface. The queue
set must be created beforehand. This
parameter is optional.
instance The networking configuration is
applied to the virtual routing instance
specified by this parameter. If no
instance is specified, the
configuration is applied to the default
routing instance. This parameter is
optional.
g Note that for mcRNC release 1

only default routing instance is
supported.
ipv4forwarding This parameter specifies if the packet The allowed values are yes
<yes|no> forwarding is allowed for IPv4 traffic. and no. Default is yes.
ipv4rpfilter This parameter specifies if the The allowed values are yes
<yes|no> reverse path filter is enabled for IPv4 and no. Default is no.
traffic. This parameter is optional.
mapping <name> The name of the VLAN priority
mapping. This parameter is optional.
Table 4 Parameters of VLAN interfaces
26 Id:0900d805808abaa1 DN0974301
Confidential

mtu <mtu-size> The maximum transmission unit Default value is 1500 bytes.
(MTU) value of the VLAN interface.
Note that the MTU of the VLAN
interface must not exceed the MTU of
the underlying real interface. This
outqset <name> This parameter specifies the logical
name of the queue set, used with this
interface. The queue set must be
created beforehand. This parameter
is optional.
proxy-arp <yes|no> This parameter turns on and off the The allowed values are yes
ProxyARP feature on this interface. and no. Default is no.
rate-limit <rate- Specifies the rate limit value of the
limit> VLAN interface. This parameter is
optional.
realiface <name> The interface where the VLAN is
assigned to. The interface can be
either physical interface (for example
eth0), logical interface (for example
inteface_1), link aggregation
group (for example ethgrp0), or
another VLAN interface. This
parameter is mandatory.
vid <id> The VLAN identifier. This parameter The allowed range is from 1
is mandatory. to 4094.
vlaniface <name> The name of the VLAN interface to be The string length is of
created. This parameter is maximum 15 characters.
mandatory.
Table 4 Parameters of VLAN interfaces (Cont.)
DN0974301 Id:0900d805808abaa1 27
Confidential
2.3 Configuring link aggregation groups

Before you start
If the virtual routing is used, check that the routing instances are created and interfaces
are set to the correct routing instances. For more information, see routing documenta-
tion. In the commands presented in this chapter, the routing instances are defined with
the optional instance <name> parameter that is attached in the commands. In the
command syntax the parameter is placed right after the networking parameter.
Steps
1 Add link aggregation.

Use the add networking linkaggr command to add new link aggregation group to
the configuration. The syntax of the command is as follows:
add networking [instance <name>] linkaggr <owner> iface <name>
algorithm <name> [admin <up|down>] [mtu <mtu-size>] [proxy-arp
<yes|no>] [ipv4forwarding <yes|no>] [ipv4rpfilter <yes|no>]
[outqset <name>] slave <iface> [slave <iface> ...] lacp
<yes|no> [rate-limit <rate-limit>]
g The mcRNC specific default LAG interface egress queue set is preconfigured in the
system with name rncdefault. Assign this profile to the LAG interfaces to enable
proper default egress scheduling weights configuration.
Example:
Create a link aggregation group named ethgrp0 of the physical interfaces eth0 and
eth1 by entering the command below. The link aggregation group is managed by the
CFPU-0 node and it uses five-tuple algorithm for physical interface selection.
add networking linkaggr /CFPU-0 iface ethgrp0 algorithm five-
tuple slave eth0 slave eth1 lacp yes
Example:
To create a link aggregation group named ethgrp0 of the physical interfaces eth0 and
eth1 with the default rate limit, enter the following command:
add networking linkaggr /CFPU-0 iface ethgrp0 slave eth0 slave
eth1
2 Show the current settings of link aggregation groups.

The current settings of the physical interfaces can be shown be executing the show
networking linkaggr command. The printout can be, for example:
lag instance default interfaces:
Lag
owner : /CFPU-0
algorithm : five-tuple
LACP : no
slave : eth1:32768
slave : eth0:32768
MTU : 1500
28 Id:0900d805808aacec DN0974301
Confidential
adminstate : up
IPv4 rpfilter : no
IPv6 rpfilter : no
Egress QueueSet : default
proxy arp : no
rate-limit : 500M
3 Change the settings of the link aggregation group.

Use the set networking linkaggr command to change the current settings of the
link aggregation group. The syntax of the command is as follows:
set networking [instance <name>] linkaggr <owner> iface <name>
[admin <up|down>] [mtu <mtu-size>] [newvrf <name>] [proxy-arp
<yes|no>] [ipv4forwarding <yes|no>] [ipv4rpfilter <yes|no>]
[outqset <name>]|[deloutqset][add-slave <iface_name>] [del-
slave <iface_name>][rate-limit <rate_limit>] [lacp <yes|no>]
Example:
To add the slave interface eth0 to the LAG interface, enter the following command:
set networking linkaggr /CFPU-0 iface ethgrp0 add-slave eth0
To delete the slave interface eth1 from the LAG interface, enter the following
command:
set networking linkaggr /CFPU-0 iface ethgrp0 del-slave eth1
4 Delete link aggregation.

Use the delete networking linkaggr command to delete the new link aggrega-
tion group from the configuration. The syntax of the command:
delete networking [instance <name>] linkaggr <owner> iface
<name>
Example:
Delete a link aggregation group named ethgrp0 of the physical interfaces eth0 and
eth1 by using the following command.
delete networking linkaggr /CFPU-0 iface ethgrp0
Further information
The parameters related to link aggregation groups are provided in the following table.

<owner> The managed object that acts as the owner of
this link aggregation group, for example
/CFPU-0.
admin The state of the link aggregation group. This The values are up and
<up|down> parameter is optional. down. Default is up.
Table 5 Parameters for link aggregation groups
DN0974301 Id:0900d805808aacec 29
Confidential

algorithm The algorithm that is used for selecting the
<name> slave interface for the traffic. In mcRNC, only
five-tuple algorithm is supported.
deloutqset This parameter restores the default qset to the
interface. This parameter is optional?
iface <name> The name of the link aggregation group to be The maximum length of
created, for example ethgrp0. the name is 15
characters.
instance The networking configuration is applied to the
virtual routing instance specified by this
parameter. If no instance is specified, the
configuration is applied to the default routing
instance.
ipv4forwarding This parameter specifies if the packet The allowed values are
<yes|no> forwarding is allowed for IPv4 traffic. This yes and no. Default is
parameter is optional. yes.
ipv4rpfilter This parameter specifies if the reverse path The allowed values are
<yes|no> filter is enabled for IPv4 traffic. This parameter yes and no. Default is
is optional. no.
lacp Link aggregation control protocol. You can The allowed values are
enable or disable the lacp. yes and no. Default is
no.
mtu <mtu-size> The maximum transmission unit (MTU) value Default value is 1500
of the link aggregation group. Note that the bytes.
MTU of the link aggregation group must not
exceed the MTU of any underlying physical
interfaces. This parameter is optional.
newvrf <name> The name of the new virtual routing instance.
g In mcRNC release 1 only default routing

instance is supported.
outqset <name> This parameter specifies the logical name of
the queue set which will be used with this
interface. The queue set must be created
beforehand. This parameter is optional.
proxy-arp This parameter turns on and off the ProxyARP The allowed values are
feature on this interface. yes and no. Default is
no.
rate-limit The physical interface (for example eth0) that Default value is 1G.
<rate_limit> will be added to this link aggregation group.
The number of slave interfaces is not
restricted. Optionally the interface name can
be followed by a colon mark (:) and a priority.
slave <iface> The physical interface (for example eth0) that The allowed range is
will be added to this link aggregation group. from 0 to 65535. The
The number of slave interfaces is not default value is 32768.
restricted. Optionally the interface name can
be followed by a colon mark (:) and a priority.
Table 5 Parameters for link aggregation groups (Cont.)
30 Id:0900d805808aacec DN0974301
Confidential
2.4 Configuring IP address for interfaces

Purpose
To configure the IP parameters and addresses of interfaces.
Steps
1 Check network interfaces

Check the existing configuration of the network interfaces of the computer unit before
configuring new ones. To check IP address setting of the interfaces, use the show
networking address command as follows:
show networking [instance <name>] address [iface <name>] [ip-
address <address/mask>] [owner <name>] [peer <address/mask>]
[role <name>] [type <value>] [user <MO_name>]
2 Create IP address for the network interfaces

Use the add networking address command to add an external IP address to the
interface.
g The network element internal addresses are assigned automatically during the commis-
sioning and they cannot be modified by the user.
Use the following syntax of the command:

add networking [instance <name>] address <dedicated|perimeter>
<owner> iface <name> ip-address <address/mask> [peer
<address/mask>] [role <name>] [user <MO_name>]
Detailed information on usage of the parameters is listed in the following table.

<type> Define the type of the IP address to The allowed values are
be added. dedicated and
Note that currently only dedicated perimeter.
addresses can be added. Perimeter
and virtual addresses are reserved
for future use.
<owner> Define the owner (node, recovery
group or recovery unit) that will be
using the IP address, for example,
/HTTPDplat.
iface <name> Define the interface that will be used
by the IP address, for example
eth1.
Table 6 Parameters for add networking address
DN0974301 Id:0900d8058086018f 31
Confidential

instance The networking configuration is
applied to the virtual routing
instance specified by this parame-
ter. If no instance is specified, the
configuration is applied to the
default routing instance.
g Note that in mcRNC release 1

supported.
ip-address Define the IP address and subnet
<address/mask> mask to be assigned, for example
10.0.0.19/24.
peer <address/mask> For the point to point interfaces,
define the IP address and the
subnet mask of the peer interface,
for example 10.0.0.2/24. This
role <name> Define the role (a user-defined
string) for the service using this IP
address. This parameter is optional.
Note that this parameter is visible in
the command syntax, but cannot
currently be used (reserved for
future use).
user <MO_name> Define a user (recovery group or
recovery unit) for this IP address.
This parameter is optional and used
only if the IP address is used also by
other services than the owner of the
address.
Table 6 Parameters for add networking address (Cont.)
3 Delete IP address for the network interfaces

To remove the external IP from the system use the delete networking address
command.
delete networking [instance <name>] address
<dedicated|perimeter> <owner> iface <name> ip-address
<address/mask>
Detailed information on usage of the parameters is listed in the following table.
Parameter Description Value range

instance Name of the virtual routing instance. If
no instance is specified, the default
routing instance is used.
<type> Define the type of the IP address to be The allowed values are
deleted. dedicated and perimeter.
Table 7 Parameters for delete networking address
32 Id:0900d8058086018f DN0974301
Confidential

<owner> Define the owner (node, recovery group
or recovery unit) that is currently using
the IP address to be deleted, for
example, /CLA-0.
iface <name> Define the interface that is used by the
IP address to be deleted, for example
eth1.
ip-address Define the IP address and subnet mask
<address/mask> to be deleted, for example
10.0.0.10/24.
Table 7 Parameters for delete networking address (Cont.)
DN0974301 Id:0900d8058086018f 33
Confidential
Configuring Iu, Iub and Iur interfaces Configuring IP Connection for Multicontroller RNC
3 Configuring Iu, Iub and Iur interfaces
3.1 Configuring Iu-PS interface

Purpose
To configure the Iu-PS interface.
g IP addresses and subnets given in the document are just examples and must be set
according to the actual network plan.
The configuration examples in the instructions are based on the IP addressing pre-
sented in Figure 9 Network configuration for Iu-PS interface.
BCN 2 RNC SPC Iu-PS User plane

- 310 (Dec) - 10.7.0.0/24
EIPU-1 Router-2
Iu-PS Control plane
cfeigw - SCTP-A 10.8.0.0/24
10.0.1.6/30 (SFP8) 10.0.1.5/30
QNUP-0(Act) - SCTP-B 10.8.1.0/24
10.0.0.6/30 (SFP7) SGSN SPC
10.1.1.1 Ioopback
- 500 (Dec)
QNUP-1 (Standby)
SGSN
10.0.1.1/30
SCTP association-2
Primary: 10.0.0.6
Secondary: 10.0.1.6
Operator
Backbone
(IP)
Router-1
BCN 1
10.0.0.5/30
EIPU-0
cfeigw
10.0.1.2/30 (SFP8)
QNUP-0 (Standby) 10.0.0.2/30 (SFP7) 10.0.0.1/30
QNUP-1(Act)
10.1.1.2 Ioopback
SCTP association-1
Primary: 10.0.0.2
Secondary: 10.0.1.2
Figure 9 Network configuration for Iu-PS interface

The instructions are based on the following network setup.
Multicontroller RNC
Application IP addresses are assigned to a certain recovery group (RG) instance, which
provides the redundancy scheme for hardware and software failures. In this configura-
tion example RG instances QNUP-0 and QNUP-1 are used for the user plane.
• Iu-PS user plane, QNUP-0 and QNUP-1 RG instances:
– QNUP-0: 10.1.1.1
– QNUP-1: 10.1.1.2
• Load sharing applied (multiple RNC side IP addresses used for a user plane)
g In a load sharing configuration, the traffic towards the same IP-based route might
originate from multiple sources in the RNC and might even utilize different network
34 Id:0900d805808a1bb4 DN0974301
Confidential
Configuring IP Connection for Multicontroller RNC Configuring Iu, Iub and Iur interfaces
interfaces. As a consequence, the traffic for this IP-based route might be processed
in multiple (interface) schedulers and egress traffic shaping for the total traffic of this
IP-based route cannot be provided anymore.
• Iu-PS control plane, two SCTP associations; network interface IP addresses are
applied for the SCTP multi-homed connections
– SCTP association-1
1. Primary IP address: 10.0.0.2
2. Secondary IP address: 10.0.1.2
1. Primary IP address: 10.0.0.6
2. Secondary IP address: 10.0.1.6
• Router-1 gateway IP addresses: 10.0.0.1 and 10.0.0.5
Core network
• SGSNs Iu-PS user plane
– 10.7.0.0/24
• SGSNs Iu-PS control plane
– SCTP-A: 10.8.0.0/24
– SCTP-B: 10.8.1.0/24
SIGTRAN
• RNC SPC
– 310 (Dec)
• SGSN SPC
– 500 (Dec)
Before you start

The mcRNC and site routers have been installed and all required connections have
been established. A recommended site solution is described in RAN1711: Cisco 7600
as mcRNC site router feature description.
The IUPS object contains the peer core network element configuration, for example the
signaling point code (SPC) of the SGSN. IUPSIP object class instances contain the IP
address and subnet definitions for a selection of the IP-based route during the user
plane connection setup. For typical cases a single (generic) IUPSIP instance is suffi-
cient, even in case of Flexible Iu or Direct Tunnel features. (In this simple case, it is not
required to specify core network user plane IP addresses in the RNC, instead 0.0.0.0/0
can be used). The differentiated services code point (DSCP) mapping for user plane
connections is configured through IPQM object attributes. The corresponding DSCP to
PHB mapping is configured at the IP layer configuration. The mapping must be aligned
with the DSCP mapping. If other than default DSCP mapping is applied, then the DSCP
to PHB mapping has to be modified accordingly.
The following parameters are related to the Iu-PS interface.
IUPS parameters:
• IPQMIdPS
IUPSIP parameters:
• IPBasedRouteIdPS
DN0974301 Id:0900d805808a1bb4 35
Confidential
• DestIPAddressPS
• IPNetmaskPS
RNTRM RNC level parameters:
• EchoRequestSending (GTP-U ECHO REQUEST activation)
• IPStackErrorTimer
• N3Requests
• T3Response
• Signaling ToDSCP (GTP ECHO REQUEST DSCP value)
g The EchoRequestSending, N3Requests, and T3Response corresponding alarm is

3472 IU-PS IP ROUTING ERROR. It is raised when GTP level Echo Request has
been enabled and sent, but Echo Response has not been received.
IPQM parameters:
• IPQMId
• ConversationalTCToDSCP
• StreamingTCToDSCP
• InteractiveTHP1TCToDSCP
• BackgroundTCToDSCP
Steps
g Before starting a new IP layer configuration, check the existing IP layer configuration.
Use the show networking ether and show networking address SCLI
commands to show the current settings of interfaces. If configuring the mcRNC using
the IP plan, create and activate a plan in the mcRNC in order to have a basic configura-
tion as a starting point for further modifications.
g To avoid IP layer fragmentation an MTU size of 1560 octets is recommended to be used

for the Iu-PS transport.
For more information on MTU, see WCDMA RAN IP Transport.
1 Configure the physical interface

Physical network interfaces are assigned to a certain EIPU node, if not yet configured.
The mcRNC default egress queue set rncdefault has to be assigned to the physical
interface for proper default egress scheduling weights configuration.
• SCLI commands
add networking ether /EIPU-0 iface ethsfp7_r1 port sfp7 outqset
rncdefault
rncdefault
rncdefault
rncdefault
36 Id:0900d805808a1bb4 DN0974301
Confidential
• IP Plan
Related object class: ETHER
RNC-xx/IP-1/OWNER-EIPU-0/ETHER-ethsfp7_r1
• port = SFP7
• admin = 1 (up)(default)
• ipv4forwarding = 1 (yes)(optional)
• mtu = 1560
• outqset = rncdefault
• vrf = default (default)(optional)
g Rate limit is inherited from the interface speed directly if no explicit value is given.
2 Configure VLAN interface (if used)

The VLAN interface is created for a certain physical interface with a reference to its
name. The VLAN ids and the VLAN interface names have to be planned and configured
accordingly.
• SCLI commands examples
#vlan: iupscp1
add networking vlan /EIPU-0 realiface ethsfp7_r1 vid 30 vlaniface
iupscp1_r1
#vlan: iupscp2
iupscp2_r1
#vlan: iupsup
iupsup1_r1
iupsup2_r2
• IP Plan
Related object class: VLAN
RNC-xx/IP-1/OWNER-EIPU-0/VLAN-iupscp1_r1
• mapping = vlanPriDefault
• mtu = 1560 (optional)
• realiface = ethsfp7_r1
• vid = 30
3 Configure the IP addresses of the interfaces

Proceed with the following configuration.
DN0974301 Id:0900d805808a1bb4 37
Confidential
g The interface name refers to created physical interfaces. If VLANs are used, the network
interface IP addresses are tied to VLAN interfaces instead of physical interfaces.
add networking address dedicated /EIPU-0 iface iupscp1_r1 ip-

address 10.0.0.2/30
4 Configure application IP addresses for user plane

Application IP addresses are assigned to a user plane recovery group (RG) and to a
loopback interface. The IP address is visible in the node/unit that is actively running the
service at the present time (active recovery unit, RU). In this case a load sharing for an
Iu-PS interface is applied by configuring two application IP addresses for termination of
Iu-PS user plane connections.
g The role attribute is a free form character string that can be configured optionally. The
role attribute can be defined to keep the IP addressing usage clearly visible in order to
simplify the system maintenance. For the Iu-PS user plane addresses apply, for
example, role “iupsup”.

• SCLI commands
add networking address dedicated /QNUP-0 iface lo ip-address
10.1.1.1/32 role iupsup
10.1.1.2/32 role iupsup
• IP Plan
Related object class: ADDR
RNC-xx/IP-1/OWNER-QNUP-0/ADDR-10.1.1.1-lo
• mask = 32
• type = 0 (dedicated)
• vrf = default (default)
• role = iupsup
5 Configure the static routes

The static routes configuration is required if the optional feature OSPF is not used. The
system adds automatically the ingress direction static routes for the EIPU units running
the QNUP Recovery Group instance. The application IP addresses can be reached
through both EIPU units.
Node Network Id Priority Gateway Notes

EIPU-0 10.7.0.0/24 0 10.0.0.1 (to Router-1) Iu-PS user plane, ECMP
Table Routing table for egress traffic
38 Id:0900d805808a1bb4 DN0974301
Confidential

EIPU-0 10.8.0.0/24 0 10.0.0.1 (to Router-1) Iu-PS control plane, primary association
EIPU-0 10.8.1.0/24 0 10.0.1.1 (to Router-2) Iu-PS control plane, secondary associa-
tion
EIPU-1 10.8.0.0/24 0 10.0.0.5 (to Router-1) Iu-PS control plane, primary association
EIPU-1 10.8.1.0/24 0 10.0.1.5 (to Router-2) Iu-PS control plane, secondary associa-
tion
Table Routing table for egress traffic (Cont.)
• SCLI commands
The ECMP routing is used for the user plane egress traffic. These routes might serve
several destination nodes depending on the core network IP subnet planning.
set routing node EIPU-0 static-route 10.7.0.0/24 nexthop gateway
address 10.0.0.1 on
address 10.0.1.1 on
address 10.0.0.5 on
address 10.0.1.5 on
Egress routes for the control plane destination subnets. These routes might serve
several destination nodes depending on the core network IP subnet planning.
address 10.0.0.1 on
address 10.0.1.1 on
address 10.0.0.5 on
address 10.0.1.5 on
• IP Plan
Related object class: SRT4, ADR4GW
RNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/SRT4-10.7.0.0-24
• nexthop = 2 (gateway)
RNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/SRT4-10.7.0.0-24/ADR4GW-10.0.0.1
• No attributes needed, default values applied
DN0974301 Id:0900d805808a1bb4 39
Confidential
6 Configure user plane resources, IP-based route configuration
g For more information on IP-based route, see the Configuring IP-based route chapter.
Configure the IP-based route instance 1 for the Iu-PS interface. The IP-based route
instance is referred from the RNW configuration IUPSIP definitions as described in step
10.
The IP-based route configuration for the Iu-PS is supported in a non-load sharing and a
load sharing mode.
g In a load sharing configuration, traffic towards the same IP-based route originates from
multiple sources in the RNC and might even use different network interfaces. As a con-
sequence, traffic for this IP-based route might be processed in multiple (interface)
schedulers and egress traffic shaping for the total traffic of this IP-based route cannot
be provided anymore.
• SCLI commands
add ipbr ipbr-id 1 committed-bandwidth 0 committed-dcn-bandwidth
0 committed-sig-bandwidth 0 ipbr-name IuPSipbr-1 route-bandwidth
0 scheduler-type none
If a user plane non-load sharing configuration is applied, proceed as follows.
Assign a single IP address to the IP-based route 1 for the Iu-PS user plane source IP
address selection.
add ipro ipbr-id 1 ip-address 10.1.1.1 iface lo owner /QNUP-0
If a user plane load sharing configuration is applied, proceed as follows.
Assign several IP addresses to the IP-based route 1 for the Iu-PS user plane source IP
address selection.
• IP Plan
Related object class: IPBR, IPRO
RNC-xx/IP-1/IPBR-1
• ipBasedRouteName = IuPSipbr-1
• routeBW = 0
• committedBW = 0
• committedDcnBW = 0
• committedSigBW = 0
• dspmProfileID = 0 (default)
• phbProfileID = 0 (default)
• schedulerType = 0 (none)
RNC-xx/IP-1/OWNER-QNUP-0/IPRO-1-10.1.1.1-lo
• No attributes needed, default values applied.
RNC-xx/IP-1/OWNER-QNUP-1/IPRO-1-10.1.1.2-lo (required if load sharing is applied)
• No attributes needed, default values applied.
40 Id:0900d805808a1bb4 DN0974301
Confidential
7 Configure control plane resources for Iu-PS

It is recommended to use all EIPUs for Iu control plane. Additionally SCTP multihoming
is recommended for the SCTP network level redundancy.
In the configuration examples two EIPUs are used for terminating SIGTRAN connec-
tions, the SCTP multihoming is enabled.
1 Create Services Access Point
Services Access Point (SAP) is used to configure a particular signaling network at
the stack. The SAP identifies the network indicator and variant of a node in the
SIGTRAN network. A node can have multiple SAPs configured. Multiple SAPs can
be added with the same network indicator.
Proceed with the following configuration:
add signaling service-access-point id 1 name SAPRNC1 network-
appearance 1 network-indicator NAO network-type itu
2 Create local Application Server (AS)
A local AS is a logical entity serving a specific Routing Key. A Routing Key identifies
a specific traffic type handled by the Local AS. The AS is identified with a routing
context between two peers. A Local AS is required for the IPSP configuration.
add signaling ss7 local-as id 1 name LASRNC1 routing-context
1 routing-key-dpc 310 service-access-point-name SAPRNC1
traffic-mode loadshare
3 Create remote AS
A remote AS is a logical entity serving a specific Routing Key. The AS is identified
with a routing context between two peers (SGSAP or IPSP-IPSP).
add signaling ss7 remote-as id 1 name SGSN1 communication-type
ipsp pending-timer 3 routing-context 2000 routing-key-dpc 500
service-access-point-name SAPRNC1 traffic-mode loadshare
4 Create M3UA association
An M3UA association object includes a local Application Server Process (ASP) and
a remote ASP.
add signaling ss7 association id 21 local-as-name LASRNC1
communication-type ipsp local-ip-addr 10.0.0.2 local-ip-addr
10.0.1.2 local-port 49225 remote-as-name SGSN1 remote-ip-addr
10.8.0.1 remote-ip-addr 10.8.1.1 remote-port 2905 node /EIPU-
0 role server exchange-mode double
10.0.0.6 local-port 49225 remote-as-name SGSN1 remote-ip-addr
DN0974301 Id:0900d805808a1bb4 41
Confidential
5 Create SCCP own point code

add signaling sccp own-point-code id 1 type primary local-as-
name LASRNC1
6 Create SCCP destination point code
add signaling sccp destination-point-code id 4 remote-as-name
SGSN1
7 Create SCCP subsystem
add signaling sccp subsystem id 1 name SSN310500 point-code-
name LASRNC1 ssn 142
name SGSN1 ssn 142
8 Create SCCP concerned subsystem
g SCCP Concerned Subsystem is informed about a state change in the affected sub-
system.

add signaling sccp concerned-subsystem name CSS1 subsystem-
name SSN310500 affected-subsystem-name SSN500310
9 Create SCCP concerned point code
g SCCP concerned point code is informed about a affected subsystem state change.
add signaling sccp concerned-point-code name CPC1 point-code-

name SGSN1 affected-subsystem-name SSN310500
10 Enable associations
set signaling ss7 association admin-state enabled id 21
g For more information, see Configuring SS7 Signaling Transport over IP for Multicon-
troller RNC.
8 Check and configure QoS related resources

In most cases using the default QoS values is sufficient, but depending on network
architecture and further QoS constraints, the values need to be reviewed and possibly
adjusted.
For more information, see the QoS configuration chapter.
9 Configure the Radio Network layer information

a) Start the mcRNC OMS Element Manager and launch the Parameter Editor tool, or
alternatively use the RNW Plan from NetAct
b) Select Configuration Management → Network Topology → Tree View
c) Select the RNC in the Topology Tree
d) Click the drop down menu next to the RNC
42 Id:0900d805808a1bb4 DN0974301
Confidential
e) Create the IPQM object if not created, select Create → new IPQM. Already existing
IPQM can also be used.
• Use the default DSCP values within the IPQM. The existing IPQM can be used
if the same DSCP mapping applies
• Only one IPQM object is needed for all the IP based Iu interfaces.
f) IP configuration for the IUPS and IUPSIP object
• The IPQMId has to refer to the IPQM object created in step e.
• IP-based route reference for the Iu-PS user plane transport bearer setup is
retrieved based on the peer IP address signaled in RANAP RAB assignment
request.
IP-based route identification has to refer to the already created IP-based route
instance in the mcRNC. IP-based route instance is used for the mcRNC user
plane source IP address selection, where the selected IP address also defines
the HW unit terminating the IP transport bearer in the mcRNC.
• In case a single IP-based route entity is used for all the Iu-PS user plane traffic,
the following mapping is recommended: 0.0.0.0/0 -> IP-based route id 1. At least
one destination IP subnet definition is required (at least one IUPSIP instance)
and the default value 0.0.0.0/0 is sufficient in most of the cases.
• In case detailed destination IP-address-based references are required (normally
only the case if dedicated traffic shaping or CAC towards certain core nodes is
needed), related entries such as 10.7.0.0/24 -> IP-based route id 1(netmask /24,
255.255.255.0) can be configured. IUPS object instance might contain several
IUPSIP instances. Such a configuration is necessary only if separate mcRNC IP
addresses are required for the connection towards a certain destination core
network peer element.
The following is a simple IUPS configuration where all the GTP tunnels are
created through the IP-based route 1.
g The possible configuration of user plane traffic load sharing is performed during
the IP-based route configuration phase.
• IUPS-1
• SignPointCode = 500 (SPC of the peer element, SGSN)
• IPQMId = 1
• IUPS-1 - IUPSIP-1
• DestIPAddressPS: 0.0.0.0
• IPNetmaskPS = 0
• IPBasedRouteIdPS = 1
DN0974301 Id:0900d805808a1bb4 43
Confidential
3.2 Configuring Iu-CS interface

Purpose
To configure the Iu-CS interface.
The configuration examples in the instructions use the IP addressing presented in

Figure 10 Network configuration for Iu-CS interface.
Iu-CS User plane
RNC SPC - 10.7.4.0/24
BCN 2
- 310 (Dec)
Iu-CS Control plane
EIPU-1 Router-2 - SCTP-A 10.8.5.0/24
cfeigw - SCTP-B 10.8.6.0/24
10.0.1.6/30 (SFP8) 10.0.1.5/30
QNUP-0(Act) MSC Server SPC
10.0.0.6/30 (SFP7)
10.1.4.1 Io - 510 (Dec)
QNUP-1 (Standby)
MSC Server
10.0.1.1/30
SCTP association-2
Primary: 10.0.0.6
Secondary: 10.0.1.6 Operator
Backbone
(IP)
Router-1
BCN 1
10.0.0.5/30
EIPU-0
cfeigw
10.0.1.2/30 (SFP8)
QNUP-0 (Standby) 10.0.0.2/30 (SFP7) 10.0.0.1/30 MGW(s)
QNUP-1(Act)
10.1.4.2 Io
SCTP association-1
Primary: 10.0.0.2
Secondary: 10.0.1.2
Figure 10 Network configuration for Iu-CS interface

Multicontroller RNC
tion example for the user plane RG instances QNUP-0 and QNUP-1 are used.
• Iu-CS user plane, QNUP-0 and QNUP-1 RG instances
– QNUP-0: 10.1.4.1
– QNUP-1: 10.1.4.2
– Load sharing applied
g In a load sharing configuration, the traffic towards the same IP-based route
might originate from multiple sources in the RNC and might even utilize different
network interfaces. As a consequence, the traffic for this IP-based route might
be processed in multiple (interface) schedulers and egress traffic shaping for the
total traffic of this IP-based route cannot be provided anymore.
44 Id:0900d805808a1c4f DN0974301
Confidential
• Iu-CS control plane, two SCTP associations; network interface IP addresses are
1. Primary IP address: 10.0.0.2 (SFP7)
2. Secondary IP address: 10.0.1.2 (SFP8)
Core network
• MGWs Iu-CS user plane
– 10.7.4.0/24
• MSC servers Iu-CS control plane
– SCTP-A: 10.8.5.0/24
– SCTP-B: 10.8.6.0/24
SIGTRAN
• RNC SPC
– 310 (Dec)
• MSC Server SPC
– 510 (Dec)
Before you start

CS Core (MGW and MSS) must be configured. For the MSS and MGW configuration
refer to the Core Network documentation.
Specific parameters have to be defined for each IP-based Iu interface. The differentiated
services code point (DSCP) mapping for the user plane connections is configured with
the IPQM object attributes. The corresponding DSCP to PHB mapping is configured at
the IP layer configuration. Each used DSCP must have a corresponding DSCP to PHB
mapping for the egress traffic scheduling.
The following parameters are related to the Iu-CS interface.
IUCS parameters:
• IPQMIdCS
• IPBasedRouteIdCS
• MinUDPPortCS
• RtcpActivation
• Iu Interface Identifier
• Core Network Identifier
• Mobile Country Code
• Mobile Network Code
• Network Indicator
• Signaling Point Code
DN0974301 Id:0900d805808a1c4f 45
Confidential
• Release version of Core Network

IUCSIP parameters:
• IPBasedRouteIdCS
• DestIPAddressCS
• IPNetmaskCS
IPQM parameters:
• IPQMId
• ConversationalTCToDSCP
• StreamingTCToDSCP
• BackgroundTCToDSCP
Steps
the IP plan, upload a plan to NetAct in order to have a basic configuration as a starting
point for further modifications.

The physical network interfaces are assigned to a certain EIPU node, if not yet config-
ured. The mcRNC default egress queue set rncdefault has to be assigned to the
physical interface for proper default egress scheduling weights configuration.
• SCLI commands
rncdefault
rncdefault
rncdefault
rncdefault
• IP Plan
• port = sfp7
• mtu = 1500
46 Id:0900d805808a1c4f DN0974301
Confidential
g Rate limit is inherited from the interface speed directly if the value is not explicitly given.

accordingly.
• SCLI commands
#vlan: iucscp1
iucscp1_r1
iucscp1_r1
#vlan: iucscp2
iucscp2_r2
iucscp2_r2
#vlan: iucsup
iucscp_r1
iucscp_r2
iucscp_r1
iucscp_r2
• IP Plan
RNC-xx/IP-1/OWNER-EIPU-0/VLAN-iucscp1_r1
• realiface = ethsfp7_r1
• vid = 50

g The interface name refers to the created physical interfaces. If VLANs are used, the
network interface IP addresses are tied to VLAN interfaces instead of physical inter-
faces.
DN0974301 Id:0900d805808a1c4f 47
Confidential
add networking address dedicated /EIPU-0 iface iucscp1_r1 ip-

address 10.0.0.2/30

service at the present time (active recovery unit, RU). In this case the user plane load
sharing for the Iu-CS interface is applied. The IP connection admission control function-
ality is applied as well.
g The role attribute is a freeform character string that can be configured optionally. The
simplify the system maintenance. For the Iu-CS user plane addresses apply, for
example, role “iucsup”.

• SCLI commands
10.1.4.1/32 role iucsup
10.1.4.2/32 role iucsup
• IP Plan
• mask = 32
• role = iucsup

The static routes configuration is required if the optional feature OSPF is not used. The
system adds automatically the ingress direction static routes for the EIPU units running
the QNUP Recovery Group instance. The application IP addresses can be reached
through both EIPU units.

EIPU-0 10.7.4.0/24 0 10.0.0.1 (to Router-1) Iu-CS user plane, ECMP
EIPU-0 10.8.5.0/24 0 10.0.0.1 (to Router-1) Iu-CS control plane, primary association
48 Id:0900d805808a1c4f DN0974301
Confidential

EIPU-0 10.8.6.0/24 0 10.0.1.1 (to Router-2) Iu-CS control plane, secondary associa-
tion
EIPU-1 10.8.5.0/24 0 10.0.0.5 (to Router-1) Iu-CS control plane, primary association
EIPU-1 10.8.6.0/24 0 10.0.1.5 (to Router-2) Iu-CS control plane, secondary associa-
tion
• SCLI commands
The ECMP routing is used for the user plane egress traffic. These routes might serve
several destination nodes depending on the IP subnet planning.
address 10.0.0.1 on
address 10.0.1.1 on
address 10.0.0.5 on
address 10.0.1.5 on
Egress routes for control plane destination subnets. These routes might serve several
destination nodes depending on the IP subnet planning.
address 10.0.0.1 on
address 10.0.1.1 on
address 10.0.0.5 on
address 10.0.1.5 on
• IP Plan
6 Check and configure the QoS related resources

adjusted.
DN0974301 Id:0900d805808a1c4f 49
Confidential
Configure the IP-based route instance 1 for the Iu-CS interface. The IP-based route
instance is referred from the RNW configuration IUCSIP definitions as described in step
9.
The IP-based route configuration for the Iu-CS is represented with a non-load sharing
mode. The IP connection admission control is configured for Iu-CS connections.
g The IP-based route level scheduling cannot be applied in the load sharing configuration
mode.
• SCLI commands
add ipbr ipbr-id 1 committed-bandwidth 800000 committed-dcn-
bandwidth 0 committed-sig-bandwidth 0 ipbr-name IuCSipbr-1 route-
bandwidth 1000000 scheduler-type none
If a user plane non-load sharing configuration is applied, assign a single IP address to
the IP-based route 1 for the Iu-CS user plane source IP address selection.
If a user plane load sharing configuration is applied, assign several IP addresses to the
IP-based route 1 for the Iu-CS user plane source IP address selection.
• IP Plan
RNC-xx/IP-1/IPBR-1
• ipBasedRouteName = IuCSipbr-1
• routeBW = 1000000
• committedBW = 800000
RNC-xx/IP-1/OWNER-QNUP-1/IPRO-1-10.1.4.2-lo (required if load sharing is applied)
8 Configure control plane resources for Iu-CS

It is recommended to use all EIPUs for Iu control plane. Additionally SCTP multihoming
is recommended for the SCTP network level redundancy.
50 Id:0900d805808a1c4f DN0974301
Confidential
In the configuration examples two EIPUs are used for terminating SIGTRAN connec-
tions, the SCTP multihoming is enabled.
add signaling service-access-point id 1 name SAPRNC1 network-
3 Create remote AS
add signaling ss7 remote-as id 2 name MSS1 communication-type
ipsp pending-timer 3 routing-context 2001 routing-key-dpc 510
service-access-point-name SAPRNC1 traffic-mode loadshare
An M3UA association object includes one local Application Server Process (ASP)
and one remote ASP. When a command is executed, remote ASP is set by default
to management blocking. Management blocking of the remote ASP is removed
when the association is enabled.
10.0.1.2 local-port 49225 remote-as-name MSS1 remote-ip-addr
10.0.0.6 local-port 49225 remote-as-name MSS1 remote-ip-addr
DN0974301 Id:0900d805808a1c4f 51
Confidential

add signaling sccp own-point-code id 1 type primary local-as-
name LASRNC1
add signaling sccp destination-point-code id 5 remote-as-name
MSS1
name MSS1 ssn 145
system.

add signaling sccp concerned-subsystem name CSS2 subsystem-
add signaling sccp concerned-point-code name CPC2 point-code-

name MSS1 affected-subsystem-name SSN310510
g For more information, see Configuring SS7 Signaling Transport over IP for Multicon-
troller RNC.

a) Start the mcRNC OMS Element Manager and launch Parameter Editor tool, or alter-
natively use the RNW Plan from NetAct
e) Create the IPQM object if not created, select Create → new IPQM. Already existing
IPQM can also be used.
• Use default DSCP values within the IPQM. Only one IPQM is required for all the
IP Iu interfaces by default. The existing IPQM can be used if the same DSCP
mapping applies.
• Only one IPQM object is needed for all the IP based Iu interfaces by default. The
default values apply for the minimum default port.
f) IP configuration for the IUCS and IUCSIP objects
52 Id:0900d805808a1c4f DN0974301
Confidential
• The IPQMId has to refer to the IPQM object created in step e.

• Activate the RTCP, the default values apply
g Check whether the RTCP activation status is consistent with the MGW configu-
ration.
• IP-based route reference for the Iu-CS user plane transport bearer setup is
retrieved based on the peer IP address signaled at RANAP RAB assignment.
IP-based route identification has to refer to the already created IP-based route
• In case a single IP-based route entity is used for all the Iu-CS user plane traffic,
the following mapping is recommended: 0.0.0.0/0 -> IP-based route id 1. At least
one destination IP subnet definition is required (at least one IUCSIP instance)
and a value 0.0.0.0/0 is sufficient in most of the cases.
• In case detailed destination IP address based references are required (normally
only the case if dedicated traffic shaping towards certain core nodes is needed),
related entries such as 10.7.0.0/24 -> IP-based route id 1(netmask /24,
255.255.255.0) can be configured. IUCS object instance might contain several
IUCSIP instances. Such a configuration is necessary only if separate mcRNC IP
addresses are required for the connection towards a certain destination core
network peer element.
The following is a simple IUCS configuration where all the connections are created
through the IP-based route instance 1.
g The possible configuration of user plane traffic load sharing is performed during the IP-
based route configuration phase.
• IUCS-1
• SingPointCode = 510 (SPC of the peer element, MSC server)
• IPQMId = 1
• IUCS-1 - IUCSIP-1
• DestIPAddressCS: 0.0.0.0
• IPNetmaskCS = 0
• IPBasedRouteIdCS = 1
DN0974301 Id:0900d805808a1c4f 53
Confidential
3.3 Configuring Iur interface

Purpose
To configure the Iur interface.
The configuration examples in the instructions use the IP addressing presented in

Figure 11 Network configuration for Iur interface.
Iur User plane
BCN 2 RNC SPC - 10.7.7.0/24
- 310 (Dec)
EIPU-1 Router-2 Iur Control plane
- SCTP-A 10.8.8.0/24
cfeigw
10.0.1.6/30 (SFP8) 10.0.1.5/30 - SCTP-B 10.8.9.0/24
QNUP-0(Act) 10.0.0.6/30 (SFP7) Neighboring RNC SPC

10.1.7.1 Io - 520 (Dec)
10.0.1.1/30 RNC
SCTP association-2
Primary: 10.0.0.6
Secondary: 10.0.1.6
Operator
Backbone
(IP)
Router-1
BCN 1
10.0.0.5/30
EIPU-0
cfeigw
10.0.1.2/30 (SFP8)
10.0.0.2/30 (SFP7) 10.0.0.1/30 RNC(s)
QNUP-0 (Standby)
SCTP association-1
Primary: 10.0.0.2
Secondary: 10.0.1.2
Figure 11 Network configuration for Iur interface

Multicontroller RNC
tion example for the user plane RG instance QNUP-0 is used.
• Iur user plane, QNUP-0 RG instance
– QNUP-0: 10.1.7.1
• Iur control plane, two SCTP associations; network interface IP addresses are
54 Id:0900d805808a1c51 DN0974301
Confidential

Neighboring RNCs
• Iur user plane of neighboring RNCs
– 10.7.7.0/24
• Iur control plane of neighboring RNCs
– SCTP-A: 10.8.8.0/24
– SCTP-B: 10.8.9.0/24
SIGTRAN
• RNC SPC
– 310 (Dec)
• Neighboring RNC SPC
– 520 (Dec)
Before you start

Specific parameters have to be defined for each IP-based Iur interface. The differenti-
ated services code point (DSCP) mapping for the user plane connections is configured
with the IUR object attributes. The corresponding DSCP to PHB mapping is configured
at the IP layer configuration. Each used DSCP must have a corresponding DSCP to
PHB mapping for the egress scheduling.
The following parameters are related to the Iur interface.
IUR parameters:
• IPBasedRouteIdIur
• MinUDPPortIur
• MaxFPDLFrameSizeIur
• DSCPHighIur
• DSCPLowIur
• DSCPMedDCHIur
• ToAWEOffsetNRTDCHIP
• ToAWEOffsetRTDCHIP
• ToAWSOffsetNRTDCHIP
• ToAWSOffsetRTDCHIP
Steps
DN0974301 Id:0900d805808a1c51 55
Confidential

• SCLI commands
rncdefault
rncdefault
rncdefault
rncdefault
• IP Plan
• port = sfp7
• mtu = 1500

accordingly.
• SCLI commands
#vlan: iurcp1
iurcp1_r1
iurcp1_r1
#vlan: iurcp2
iupscp1_r1
iupscp1_r1
#vlan: iurup
56 Id:0900d805808a1c51 DN0974301
Confidential

iurup1_r1
iurup1_r2
iurup2_r1
iurup2_r2
• IP Plan
RNC-xx/IP-1/OWNER-EIPU-0/VLAN-iurcp1_r1
• realface = ethsfp7_r1
• vid = 60

add networking address dedicated /EIPU-0 iface iurcp1_r1 ip-

address 10.0.0.2/30

service at the present time (active recovery unit, RU). In this case the non-load sharing
for the Iur interface is applied. The IP connection admission control functionality is
applied as well.
simplify the system maintenance. For the Iur user plane addresses apply, for example,
role “iurup”.

• SCLI commands
10.1.7.1/32 role iurup
• IP Plan
DN0974301 Id:0900d805808a1c51 57
Confidential
• mask = 32
• role = iurup

The static routes configuration is required if OSPF is not used. The system adds auto-
matically the ingress direction static routes for the EIPU units running the QNUP
Recovery Group instance. The application IP addresses can be reached through both
EIPU units.

EIPU-0 10.7.7.0/24 0 10.0.0.1 (to Router-1) Iur user plane, ECMP
EIPU-0 10.8.8.0/24 0 10.0.0.1 (to Router-1) Iur control plane, primary association
EIPU-0 10.8.9.0/24 0 10.0.1.1 (to Router-2) Iur control plane, secondary association
EIPU-1 10.8.9.0/24 0 10.0.0.5 (to Router-1) Iur control plane, primary association
EIPU-1 10.8.9.0/24 0 10.0.1.5 (to Router-2) Iur control plane, secondary association
• SCLI commands
The ECMP routing is used for the user plane egress traffic. These entries might serve
address 10.0.0.1 on
address 10.0.1.1 on
address 10.0.0.5 on
address 10.0.1.5 on
Egress routes for the control plane destination subnets. These entries might serve
address 10.0.0.1 on
address 10.0.1.1 on
address 10.0.0.5 on
58 Id:0900d805808a1c51 DN0974301
Confidential

address 10.0.1.5 on
• IP Plan
6 Check and configure the QoS related resources

adjusted.
Configure the IP-based route instance 1 for the Iur interface. The IP-based route
instance is referred from the RNW configuration IURIP definitions as described in step 9.
The IP-based route configuration for the Iur is represented with a non-load sharing
mode. The IP connection admission control is configured for Iur connections.
g The IP-based route level scheduling can be applied in the non-load sharing configura-
tion mode.
• SCLI commands
bandwidth 0 committed-sig-bandwidth 0 ipbr-name Iuripbr-1 route-
bandwidth 600000 scheduler-type none
If basic non-load sharing configuration is applied, assign the IP address to the IP-based
route 1 for the Iur user plane source IP address selection.
• IP Plan
RNC-xx/IP-1/IPBR-1
• ipBasedRouteName = Iuripbr-1
• routeBW = 600000
DN0974301 Id:0900d805808a1c51 59
Confidential
8 Configure control plane resources for Iur

For an Iur control plane configuration it is recommended to use at least two EIPUs for
the load sharing and redundancy of the connection. Additionally SCTP multihoming is
recommended for the SCTP association network level redundancy provisioning. The
detailed number of EIPU units, that is required for total control plane traffic load sharing
purposes, must be planned according to dimensioning guidelines, see Dimensioning
WCDMA RAN Access Network (RNC and Transport). In the configuration examples two
EIPUs are used for terminating SIGTRAN connections, the SCTP multihoming is
enabled.
add signalling service-access-point id 1 name SAPRNC1 network-
3 Create remote AS
add signalling ss7 remote-as id 1 name DRNC1 communication-
type ipsp pending-timer 3 routing-context 2002 routing-key-dpc
520 service-access-point-name SAPRNC1 traffic-mode loadshare
An M3UA association object includes one local Application Server Process (ASP)
and one remote ASP. When a command is executed, remote ASP is set by default
to management blocking. Management blocking of the remote ASP is removed
when the association is enabled.
60 Id:0900d805808a1c51 DN0974301
Confidential

add signalling ss7 association id 81 local-as-name LASRNC1
10.0.1.2 local-port 49225 remote-as-name DRNC1 remote-ip-addr
add signalling ss7 association id 82 local-as-name LASRNC1
10.0.0.6 local-port 49225 remote-as-name DRNC2 remote-ip-addr
add signalling sccp own-point-code id 1 type primary local-as-
name LASRNC1
add signalling sccp destination-point-code id 6 remote-as-name
DRNC2
add signalling sccp subsystem id 1 name SSN310520 point-code-
add signalling sccp subsystem id 2 name SSN520310 point-code-
name SGSN1 ssn 148
system.

add signalling sccp concerned-subsystem name CSS3 subsystem-
add signalling sccp concerned-point-code name CPC3 point-code-

name DRNC2 affected-subsystem-name SSN310520
set signalling ss7 association admin-state enabled id 81
set signalling ss7 association admin-state enabled id 82

DN0974301 Id:0900d805808a1c51 61
Confidential

e) Create the IUR object if not created, select Create → new IUR. Already existing IUR
can also be used.
• IP-based route identification has to refer to the already created IP-based route
The following is a simple IUR configuration where all the connections are created
through the IP-based route instance 1.
g The possible configuration of user plane traffic load sharing is performed during the IP-
based route configuration phase.
• IUR-1
– SignPointCode = 520 (SPC of the peer element, neighboring RNC)
– IPBasedRouteIdIur = 1
62 Id:0900d805808a1c51 DN0974301
Confidential
3.4 Configuring Iub interface

Purpose
To configure the Iub interface.
The configuration examples in the instructions use the IP addressing and network con-
figuration presented in Figure 12 mcRNC IP-based Iub connectivity for Flexi Multiradio
WCDMA BTS.
BCN 2
Iub user and control
EIPU-1 Router-2 plane addresses
cfeigw - BTS#1 10.2.0.1/24
10.0.1.6/30 (SFP8) 10.0.1.5/30
QNUP-0(Active)
10.0.0.6/30 (SFP7)
10.1.0.1 Io
QNIUB-0 (Standby)
BTS#1
10.0.1.1/30
QNIUB-1 (Active)
10.1.0.66 Io
Operator
Backbone
(IP)
Router-1
BCN 1
10.0.0.5/30
EIPU-0
cfeigw
10.0.1.2/30 (SFP8) BTSs
QNUP-0 (Standby) 10.0.0.2/30 (SFP7) 10.0.0.1/30
QNIUB-0(Active)
10.1.0.65 Io
QNIUB-1 (Standby) mcRNC Iub control BTSs O&M subnet

plane subnet 10.10.0.0/24
10.1.0.64/26
Figure 12 mcRNC IP-based Iub connectivity for Flexi Multiradio WCDMA BTS
Multicontroller RNC
tion example QNUP-0 is used for the user plane RG instances.
• Iub user plane, QNUP-0 RG instance
– QNUP-0: 10.1.0.1
• Iub control plane, two QNIUB RG instances are used to provide the NBAP link
IP/SCTP termination
– QNIUB-0 IP address: 10.1.0.65
– QNIUB-1 IP address: 10.1.0.66
– Iub control plane subnet: 10.1.0.64/26
DN0974301 Id:0900d805808a1c53 63
Confidential
BTS IP addresses
• user and control plane
– BTS#1: 10.2.0.1/24
• BTS O&M subnet for several BTSs
– 10.10.0.0/24
Before you start

RNW configuration has to be done according to the network plan. Configuration can be
created by using either the RNW Parameter Editor (RNC EM application) or the RNW
plan interface. The IP-layer configuration can be managed using the SCLI commands
or the IP plan interface from NetAct.
The following parameters are related to the Iub interface.
IPNB parameters for IP Iub control plane connections:
• IPNBId
• WBTSId
• MinSCTPPortIub
• NodeBIPAddress
• SourceNBAPIPAddress
• SourceNBAPIPNetmask
• NBAPDSCP
• CNBAP
• SCTPPortNumberCNBAP
• DNBAPList
• DNBAP
• CControlPortID
• SCTPPortNumberDNBAP
WBTS parameters for IP Iub user plane connections:
• IPNBId
• IPBasedRouteId
• IPBasedRouteId2 (optional)
• MinUDPPortIub
• MaxFPDLFrameSizeIub
– control the maximum Frame Protocol frame used by the mcRNC
• MaxBTSOMFrameSize
– control the maximum BTS O&M message size
• DSCPHigh
– DSCP value for user plane transport bearers for common channels, SRBs
through Rel-99 DCH and HSPA, CS domain calls through Rel-99 DCH and
HSPA
• DSCPMedDCH
– DSCP value for R99 NRT DCH
• DSCPMedHSPA
– DSCP value for streaming HSPA user data
64 Id:0900d805808a1c53 DN0974301
Confidential
• DSCPLow
– DSCP value for the NRT HSPA user data
• HSDPAULCToDSCP
– DSCP value for the HS-DSCH uplink Frame Protocol control frames
• HSUPADLCToDSCP
– DSCP value for the E-DCH downlink Frame Protocol control frames
• ToAWEOffsetNRTDCHIP
• ToAWEOffsetRTDCHIP
• ToAWSOffsetNRTDCHIP
• ToAWSOffsetRTDCHIP
The parameters can be configured with the mcRNC Parameter Editor GUI.
BTS parameters can be configured with the BTS Site Manager or NetAct. For more
information about BTS parameters, see Plan Editor Flexi Transport Module Parameters.
Steps

• SCLI commands
rncdefault
rncdefault
rncdefault
rncdefault
• IP Plan
• port = sfp7
• mtu = 1500
DN0974301 Id:0900d805808a1c53 65
Confidential
g Rate limit is inherited from the interface speed directly if the value is not explicitly given.

accordingly.
• SCLI commands
#vlan: iub1
iub1_r1
iub1_r1
#vlan: iub2
iub2_r2
iub2_r2
• IP Plan
RNC-xx/IP-1/OWNER-EIPU-0/VLAN-iub1_r1
• realIface = ethsfp7_r1
• vid = 10
3 Configure IP addresses of the interfaces

add networking address dedicated /EIPU-0 iface iub1_r1 ip-address

10.0.0.2/30

Application IP addresses are assigned to the user plane recovery group (RG) and to a
service at the present time (active recovery unit, RU). In this case a load sharing for an
Iub interface is applied by configuring two application IP addresses for termination of Iub
user plane connections.
66 Id:0900d805808a1c53 DN0974301
Confidential
role attribute can be defined to keep the IP addresses usage clearly visible in order to
simplify the system maintenance. For the Iub user and control plane addresses apply,
for example, role “iubup” and “iubcp”.

• SCLI commands
10.1.0.1/32 role iubup
• IP Plan
• mask = 32
• role = iubup
5 Configure application IP addresses for control plane NBAP/SCTP links

The IUB control plane IP addresses are assigned to the QNIUB Recovery Group and
are tied to the loopback interface.
• SCLI commands
add networking address dedicated /QNIUB-0 iface lo ip-address
10.1.0.65/32 role iubcp
add networking address dedicated /QNIUB-1 iface lo ip-address
10.1.0.66/32 role iubcp
• IP Plan
RNC-xx/IP-1/OWNER-EIPU-0/ADDR-10.1.0.65-lo
• mask = 32
• role = iubcp
6 Check and configure the Iub SCTP parameters, IUBSNT

The Iub interface SCTP layer parameters are managed through the IUBSNT object
class. The system contains one default SCTP profile. For the new NBAP/SCTP connec-
tion, the default profile values are applied, unless an explicitly configured IUBSNT
matching the IP address of the selected RNC can be found from the system. The
IUBSNT object IP address and mask attributes define the group of Iub control plane ter-
minations where the profile is applied.
In most cases the default profile values can be applied.
g The IUBSNT profile contains the maximum SCTP frame size definition controlling the
fragmentation at the SCTP layer. To avoid fragmentation at the IP layer, it has to be
DN0974301 Id:0900d805808a1c53 67
Confidential
verified that the maximum IP datagram size does not exceed the MTU configured in the
network. In addition to the network MTU, the BTS requirements for the maximum IP
datagram size (1472) for the Iub control plane has to be followed as well. The default
value guarantees that SCTP packets are not fragmented at the IP layer as long as the
transport network MTU is 1472 or above.
• SCLI commands
Check the current profiles and value:
show iubsnt {[local-subnet-id <subnetid-value>]?}
Add new profile, if needed:
add iubsnt local-subnet-id 1 net-address 10.1.0.0/24 rto-initial
2000 rto-min 1759 rto-max 3000 association-max-retrans 7 path-
max-retrans 7 heartbeat-interval 2000 sack-period 400 max-frame-
size 1452
• IP Plan
RNC-xx/IP-1/IUBSNT-1
• IPV4MaskLength = 24
• IPV4SubnetAddress = 10.1.0.0
• assocMaxRetrans = 7
• hbInterval = 2000
• maxSCTPFrameSize =1452
• pathMaxRetrans = 7
• rtoInitial = 2000 ms
• rtoMax = 3000 ms
• rtoMin = 1750 ms
• sackPeriod = 400 ms

Configuration of static routes is required if OSPF is not used. The system adds automat-
ically the ingress direction static routes for the EIPU units running the QNIUB Recovery
Group instances. The application IP addresses can be reached through both EIPU units.

EIPU-0 10.2.0.0/24 0 10.0.0.1 (to Router-1) BTS subnet, user and control plane,
ECMP
EIPU-0 10.2.0.0/24 0 10.0.1.1 (to Router-2) IBTS subnet, user and control plane,
ECMP
ECMP
ECMP
68 Id:0900d805808a1c53 DN0974301
Confidential
• SCLI commands
The ECMP routing is used for the mcRNC user plane egress traffic. These routes might
serve several destination nodes depending on the IP subnet planning.
address 10.0.0.1 on
address 10.0.1.1 on
address 10.0.0.5 on
address 10.0.1.5 on
• IP Plan
8 Check and configure QoS related resources

adjusted.
g For more information, see the Configuring IP-based route chapter.
Configure the IP-based route instance 1 for the Iub interface. The IP-based route
instance is referred from the RNW configuration WBTS definitions as described in step
9.
The IP-based route for the Iub is configured with a non-load sharing mode. IP connec-
tion admission control and IP-based route level scheduling is applied, enabling usage of
rate limiting per base station.
• SCLI commands
bandwidth 150 committed-sig-bandwidth 150 ipbr-name Iubipbr-1
route-bandwidth 10000 scheduler-type virtual
If basic non-load sharing configuration is applied, assign the mcRNC IP address to the
IP-based route 1 for the Iub user plane source IP address selection.
DN0974301 Id:0900d805808a1c53 69
Confidential
• IP Plan
RNC-xx/IP-1/IPBR-1
• ipBasedRouteName = Iubipbr-1
• routeBW = 10000
• schedulerType = virtual (none)
10 Configure the IP-based Iub in the mcRNC Parameter Editor GUI.

e) Create the IPNB object if not created, select Create → new IPNB.
1. Provide the IPNB with an object identifier.
2. Assign the BTS CP/UP 10.2.0.1 IP address as a control plane destination
address Iub.
3. Assign a proper RNC own Iub control plane subnet definition with the
SourceNBAPIPAddress and SourceNBAPIPNetmask attributes. The attri-
butes are used to control the NBAP link RNC own IP address selection and IPNB
creation phase.
If any of the IP addresses (tied to QNUIB recovery groups) have connectivity to
the BTS, the default 0.0.0.0/0 reference can be applied. In this case the system
freely selects the NBAP link SCTP/IP termination. If only a certain EIPU unit has
connectivity to the BTS, then the Iub control IP address selection can be limited
with the subnet definition. Even a specific address can be referred with /32 value
if needed.
4. In the D-NBAP List enter 1 for the Communication Control Port ID; the SCTP
Port Number for D-NBAP is automatically calculated.
f) Create or modify the WBTS object so that it contains the IPNB reference and IP Iub
user plane configuration.
1. Configure IPNBId (IPNB object identifier) into the WBTS data.
2. Set attributes related to IP-based Iub user plane correctly.
• Set IPBasedRouteIdIub so that it refers to the IP based route configured
in step 9.
• Default values can be used for MinUDPPortIub, DSCPMedDCH, DSCPLow,
DSCPHigh, DSCPMedHSPA, HSDPAULCToDSCP, HSUPADLCToDSCP,
70 Id:0900d805808a1c53 DN0974301
Confidential
ToAWEOffsetNRTDCHIP, ToAWEOffsetRTDCHIP,
ToAWSOffsetNRTDCHIP, and ToAWSOffsetRTDCHIP.
3.4.1 Configuring IP resources for Iub control plane

Purpose
The purpose of this procedure is to configure Iub control plane subnet.
Before you start

Check that the LAN cables are correctly attached to the mcRNC.
1 Connect to the mcRNC
g SCLI commands are executed under fsclish prompt

Enter:
fsclish
2 Configure the local sub-net for Iub control plane

Use the add iubsnt command in order to create the Iub local subnet, the syntax of the
command is the following:
add iubsnt local-subnet-id <local-subnet-id> net-address <net-
address> [rto-initial <rto-initial>] [rto-max <rto-max>] [rto-min
<rto-min>] [association-max-retrans <association-max-retrans>]
[heartbeat-interval <heartbeat-interval>] [path-max-retrans
<path-max-retrans>] [sack-period <sack-period>] [max-frame-size
<max-frame-size>] [vrf-id <vrf-id>]
The following table describes the usage of the parameters.
Parameter Description Syntax

local-subnet-id Mandatory parameter. Range: 1-8
This is the ID of the Iub
local subnet. A default
subnet with ID 0 is avail-
able with subnet
address 0.0.0.0 and
mask 0. This default
subnet cannot be
deleted nor modified.
net-address Mandatory Parameter. Format: NET-
This parameter is used ADDRESS/MASK-LEN
to identify the network
address of iubsnt.
Table Parameters of add iubsnt command
DN0974301 Id:0900d805808a1c53 71
Confidential

rto-initial Optional parameter. Range: 10 to 60000 ms
This is the initial value of Default: 1000 ms
RTO(retransmission
timeout) that is used in
RTO calculations. This
parameter is a property
of SCTP protocol.
rto-max Optional parameter. Range: 10-120000 ms
This is the maximum Default: 2000 ms
value of RTO that is
used in RTO calcula-
tions. This parameter is
a property of SCTP pro-
tocol.
rto-min Optional parameter. Range: 10-20000 ms
This is the minimum Default: 750 ms
tocol.
association-max- Optional parameter. Range: 1-15
retrans This parameter is a Default: 5
property of SCTP proto-
col. It defines the
maximum number of
consecutive retransmis-
sions to a peer over the
association before an
endpoint considers that
the peer is unreachable
and closes the associa-
tion.
heartbeat- Optional parameter. Range: 100-300000 ms
interval This is the time interval Default: 1000 ms
between the trasmis-
sions of two HEART-
BEAT chunks. This
of SCTP protocol.
Table Parameters of add iubsnt command (Cont.)
72 Id:0900d805808a1c53 DN0974301
Confidential

path-max-retrans Optional parameter. Range: 1-15
This parameter is a Default: 5
col. It defines the
maximum number of
sions of messages over
the path to the peer
endpoint before it is
marked as inactive. A
path connects a source
IP address and a desti-
nation IP address.
sack-period Optional parameter. Range: 0-500 ms
This parameter is a Default: 200 ms
col. It defines the
delayed SACK timeout.
max-frame-size Optional parameter. Range: 540 to 9000
This parameter defines bytes
the maximum segment Default: 1452 bytes
size at SCTP layer.
vrf-id Optional parameter. Range: 0-63
This is the ID of the Default: 0
virtual routing and for-
warding instance.
Table Parameters of add iubsnt command (Cont.)
Example 1: Adding an Iub local subnet with default parameter values

add iubsnt local-subnet-id 1 net-address 192.251.1.1/16
Example 2: Adding an Iub local subnet and setting all parameter values
add iubsnt local-subnet-id 1 net-address 192.251.1.1/16
association-max-retrans 10 heartbeat-interval 500 path-max-
retrans 10 rto-initial 1000 rto-min 1000 rto-max 4000 sack-
period 300 max-frame-size 1500 vrf-id 1
3 Configure an IP address on QNIUB recovery group (RG) on EIPU unit
g The QNIUB is the recovery group for Iub control plane. The IP address on QNIUB is the
local IP for NBAP links based on SCTP association.
Use the following syntax of add networking address command to add an external
IP address:
add networking [instance <name>] address <owner> iface <name> ip-
address <address/mask>] [peer <address/mask>] [role <name>]
[table <id>] [user <MO_name>] [via <gateway>]
DN0974301 Id:0900d805808a1c53 73
Confidential
For more information on IP configuration, see instructions in Configuring IP parameters

and addresses of interfaces.
4 Check the local subnet for Iub control plane configuration parameters
Use the show iubsnt command in order to check the parameters of the Iubsnt, the
syntax of the command is the following:
show iubsnt [local-subnet-id <local-subnet-id>]
When no parameter is specified, all Iub local subnets will be listed.

local- Optional Range: 0-8
subnet-id parameter.
This is the
ID of the Iub
local subnet.
The local
subnet with
ID 0 is the
default
subnet that
is not config-
urable.
Table Parameter of show iubsnt command
5 Modify the local IP sub-net for Iub control plane configuration parameters
Use the set iubsnt command to modify the parameters of the Iubsnt, the syntax of
the command is as follows:
set iubsnt local-subnet-id <local-subnet-id> [rto-initial <rto-
initial>] [rto-max <rto-max>] [rto-min <rto-min>] [association-
max-retrans <association-max-retrans>] [heartbeat-interval
<heartbeat-interval>] [path-max-retrans <path-max-retrans>]
[sack-period <sack-period>] [max-frame-size <max-frame-size>]
The following table describes the usage of the parameters.
74 Id:0900d805808a1c53 DN0974301
Confidential

local-subnet-id Mandatory parameter. Range: 1-8
This is the ID of the Iub
local subnet. A default
subnet with ID 0 is avail-
able with subnet
address 0.0.0.0 and
mask 0. This default
subnet cannot be
deleted nor modified.
rto-initial Optional parameter. Range: 10 to 60000 ms
This is the initial value of Default: 1000 ms
RTO(retransmission
timeout) that is used in
RTO calculations. This
of SCTP protocol.
rto-max Optional parameter. Range: 10-120000 ms
This is the maximum Default: 2000 ms
tocol.
rto-min Optional parameter. Range: 10-20000 ms
This is the minimum Default: 750 ms
tocol.
association-max- Optional parameter. Range: 1-15
retrans This parameter is a Default: 5
col. It defines the
maximum number of
sions to a peer over the
association before an
endpoint considers that
the peer is unreachable
and closes the associa-
tion.
Table Parameters of set iubsnt command
DN0974301 Id:0900d805808a1c53 75
Confidential

heartbeat- Optional parameter. Range: 100-300000 ms
interval This is the time interval Default: 1000 ms
between the trasmis-
sions of two HEART-
BEAT chunks. This
of SCTP protocol.
path-max-retrans Optional parameter. Range: 1-15
This parameter is a Default: 5
col. It defines the
maximum number of
sions of messages over
the path to the peer
endpoint before it is
marked as inactive. A
path connects a source
IP address and a desti-
nation IP address.
sack-period Optional parameter. Range: 0-500 ms
This parameter is a Default: 200 ms
col. It defines the
delayed SACK timeout.
max-frame-size Optional parameter. Range: 540 to 9000
This parameter defines bytes
the maximum segment Default: 1452 bytes
size at SCTP layer.
Table Parameters of set iubsnt command (Cont.)
Example: Changing Iub local subnet configuration

set iubsnt local-subnet-id 1 association-max-retrans 6
heartbeat-interval 300 path-max-retrans 6 rto-initial 1000 rto-
max 3000 rto-min 1000 sack-period 200 max-frame-size 1472
6 Delete the local IP subnet, if necessary
g Make sure that there are no NBAP links in the subnet, before deleting the Iubsnt.
Use the delete iubsnt command to delete the Iubsnt, the syntax of the command is
as follows:
delete iubsnt local-subnet-id <local-subnet-id>
76 Id:0900d805808a1c53 DN0974301
Confidential

local- Mandatory Range: 1-8
subnet-id parameter.
This is the
ID of the Iub
local subnet.
The local
subnet with
ID 0 is the
default
subnet that
is not config-
urable.
Table Parameter of delete iubsnt command
Further information
For more information on Iubsnt SCLI commands, see Multicontroller RNC SCLI Com-
mands.
DN0974301 Id:0900d805808a1c53 77
Confidential
3.5 Configuring IP for Iu-BC interface (RNC - CBC)

Purpose
To configure IP for the Iu-BC interface between the RNC and the Cell Broadcast Centre
(CBC).
Before you start

The IP resources for Iu-BC need to be created.
Summary
The Iu-BC traffic to and from the mcRNC is routed via EIPU unit, which terminates
UDP/IP protocol on the incoming packets and forwards to the CFPU unit for further pro-
cessing.
In this chapter, general steps of IP configuration for Iu-BC interface are presented.
Steps
1 Check the states of the units in the system

Use the show functional-unit all command in order to check whether the
recovery units are in working state.
2 Configure the Ethernet interface in EIPU (optional)

Change the Ethernet interface working rate if the connected Ethernet device requires it.
The communication will fail if different working mode is set on the connected Ethernet
devices.
For detailed instructions, see the chapter Configuring Ethernet interfaces
3 Create VLAN interface (optional)

Use the add networking command to create a VLAN interface. The syntax of the
command is as follows:
add networking [instance <name>] vlan <owner> realiface <name>
vid <id> vlaniface <name> [admin <up|down>] [mapping <name>] [mtu
<mtu-size>] [ipv4forwarding <yes|no>] [ipv4rpfilter
<yes|no>][proxy-arp <yes|no>]
For detailed intructions, see instructions in Configuring VLAN interfaces
4 Assign an IP address to the external Ethernet interface or VLAN interface of the

EIPUunit
Use the following syntax of add networking address command to add an external
IP address:
add networking [instance <name>] address <owner> iface <name> ip-
address <address/mask>] [peer <address/mask>] [role <name>]
[table <id>] [user <MO_name>] [via <gateway>]
See instructions in Configuring IP parameters and addresses of interfaces.
78 Id:0900d805808abf94 DN0974301
Confidential
5 Configure an IP address for Iu-BC service in the CFPU unit

6 Configure an IP address in both EIPU and CFPU units

7 Configure the static routes for the EIPU unit

Create the static routes from EIPU to the external destination (for example, a router).
See instructions in Configuring static routes for IPv4.
8 Create OSPF configuration, if necessary

Create the static routes from EIPU to the external destination (for example, a router).
See the chapter Configuring OSPFv2.
Example 1: Configuring IP for Iu-BC interface with 1GE connectivity

The following figure shows the IP connectivity scheme based on 1GE SFP modules. The
Iu-BC traffic is routed through EIPU units of the mcRNC and terminated in the CFPU
units.
g The internal IP addresses are configured during the commissioning phase and do not
need to be configured. You only need to add routing entries for these addresses.
DN0974301 Id:0900d805808abf94 79
Confidential
EIPU-3
cfeigw 10.0.1.14/30 (SFP16)
QNUP-2 GW
10.0.0.14/30 (SFP15)
EIPU-1 Router-2
cfeigw 10.0.1.13/30
10.0.1.10/30 (SFP8)
QNUP-0 GW 10.0.1.9/30
10.0.0.10/30 (SFP7)
CFPU-1 CBC c.c.c.c/xx

cfeigw
QNCFCP-0 GW 10.0.1.5/30
SAB (Active):: QNCFCP-0 10.0.1.1/30
- 10.22.0.1 lo
Transport
Network
EIPU-2
cfeigw 10.0.1.6/30 (SFP16) 10.0.0.13/30
QNUP-2 GW 10.0.0.9/30
10.0.0.6/30 (SFP15)
EIPU-0
cfeigw 10.0.1.2/30 (SFP8)
QNUP-0 GW 10.0.0.2/30 (SFP7) 10.0.0.5/30
10.0.0.1/30
CFPU-0 Router-1
cfeigw
QNCFCP-0 GW
SAB (Standby):: QNCFCP-0
- 10.22.0.1 lo
Figure 13 IPv4 configuration for Iu-BC 1GE connectivity
Node Network Id Priority Gateway

EIPU-0 10.22.0.1/32 0 QNCFCP-0 GW
(Iu-BC, SAB source)
EIPU-1 10.22.0.1/32 0 QNCFCP-0 GW
(Iu-BC, SAB source)
Table Routing table for ingress traffic

CFPU-0 c.c.c.c/xx 1 QNUP-0 GW Egress
(CBC dest subnet)
CFPU-1 c.c.c.c/xx 1 QNUP-0 GW Egress
(CBC dest subnet)
EIPU-0 c.c.c.c/xx 1 10.0.0.1 (to Router-1) Egress, ECMP
(CBC dest subnet)
80 Id:0900d805808abf94 DN0974301
Confidential

(CBC dest subnet)
(CBC dest subnet)
(CBC dest subnet)
DN0974301 Id:0900d805808abf94 81
Confidential
3.6 Configuring IP interfaces with OSPF, stub area

Purpose
To configure IP interfaces with OSPF.
The OSPF protocol is used to provide dynamic routing within the OSPF Autonomous
System (AS). If activated, routes to the mcRNC application IP addresses are distributed
to the site routers and to the network, depending on the network design.
In the presented OSPF area scheme the mcRNC external interfaces and the site routers
interfaces are connected to the external interfaces in Area 100.0.0.0. The following
benefits are provided:
• The internal network of the network element is not exposed to the external network.
• The convergence time of the OSPF area for the external interfaces is reduced.
• The stub area configuration keeps the amount of the routing table entries small
within the mcRNC.
The following example presents the configuration for a single OSPF area network,
created between the mcRNC and site routers. The OSPF usage and the OSPF area
planning affect the required configuration and require special attention while planning
the network-level OSPF; consider this carefully before use.
The instructions are based on the IP addressing and network setup presented in Figure
14 OSPF area scheme.
Module 2 OSPF Area 100.0.0.0

EIPU-3
cfeigw 10.0.1.14/30 (SFP16)
QNUP-2 GW
10.0.0.14/30 (SFP15)
10.0.0.13/30
10.0.1.9/30
EIPU-1
cfeigw
QNUP-0 GW 10.0.1.10/30 (SFP8)
10.0.0.10/30 (SFP7)
10.0.1.5/30
QNUP-0 (Active) 10.0.1.1/30
10.1.0.1 lo
Area 0.0.0.0
Module 1
10.0.0.13/30
EIPU-2 10.0.0.9/30
cfeigw 10.0.1.6/30 (SFP16)

QNUP-2 GW
10.0.0.6/30 (SFP15)
10.0.0.5/30
10.0.0.1/30
EIPU-0
cfeigw
QNUP-0 GW 10.0.1.2/30 (SFP8)
10.0.0.2/30 (SFP7)
QNUP-0 (Standby)
10.1.0.1 lo
Figure 14 OSPF area scheme
82 Id:0900d805808a1c55 DN0974301
Confidential
Steps

• SCLI commands
rncdefault
rncdefault
rncdefault
rncdefault
• IP Plan
• port = SFP7

Proceed with the following configuration in order to assign the IP addresses to the
network interfaces.
• SCLI commands
add networking address dedicated /EIPU-0 iface ethsfp7_r1 ip-
address 10.0.0.2/30
address 10.0.1.2/30
address 10.0.0.10/30
DN0974301 Id:0900d805808a1c55 83
Confidential

address 10.0.1.10/30
• IP Plan
RNC-xx/IP-1/OWNER-EIPU-0/ADDR-10.0.0.2-ethsfp7_r1
• mask = 30
• vrf = default (default VRF)
3 Configure the OSPF router id for each node

• SCLI commands
set routing instance default node EIPU-0 router-id 192.0.0.1
set routing instance default node EIPU-1 router-id 192.0.0.2
• IP Plan
Related object class: RTRID
RNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/RTRID-192.0.0.1
• No attributes required, because the router id is the instance id.
4 Configure the OSPF area

Create the OSPF area in each routing instance. The following is an example of a stub
area usage between the mcRNC and the site router.
• SCLI commands
set routing instance default node EIPU-0 ospf area 100.0.0.0 stub
on
set routing instance default node EIPU-1 ospf area 100.0.0.0 stub
on
• IP Plan
Related object class: O2AREA
RNC-xx/IP-0/OWNER-EIPU-0/RTINST-default/O2AREA-100.0.0.0
• stub = 1 (Stub area)
5 Activate the OSPF on the interfaces

Activate the OSPF on the loopback and network interfaces, in order to distribute the
routes to applications IP addresses to the site routers.
• Proceed with the following configuration in order to activate the OSPF on the
loopback interface
• SCLI commands
set routing instance default node EIPU-0 ospf interface lo area
100.0.0.0 on
set routing instance default node EIPU-1 ospf interface lo area
100.0.0.0 on
84 Id:0900d805808a1c55 DN0974301
Confidential
• IP Plan
Related object class: O2AREA - O2IFC
RNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/O2AREA-0.0.0.0/O2IFC-lo
• Proceed with the following configuration in order to activate the OSPF on the
network interfaces
• SCLI commands
set routing instance default node EIPU-0 ospf interface
ethsfp7_r1 area 100.0.0.0 on
6 Configure basic OSPF parameters

For each network instance set the OSPF designated router election priority parameters.
It is not recommended to allow the EIPU nodes to become a designated router.
• SCLI commands
ethsfp7_r1 priority 0
Set the OSPF parameters to allow fast failover behavior.
• SCLI commands
ethsfp7_r1 hello-interval 1
ethsfp7_r1 dead-interval 2
DN0974301 Id:0900d805808a1c55 85
Confidential

• IP Plan
Related object class:O2AREA - O2IFC
RNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/O2AREA-0.0.0.0/O2IFC-ethsfp7_r1
• authType = 0 (default, none)
• deadInterval = 2
• electionPriority = 0
• helloInterval = 1
• ospfCost = 1(default)
• passive = 1 (on)
• retransmitInterval = 15
7 Configure the stub networks for the user plane redundancy

The mcRNC user plane redundancy scheme is based on the Recovery Group tied to
EIPU nodes. The service, that is actively running in one of the EIPU nodes (active
Recovery Unit), can also be reached through a redundant EIPU node in case of, for
example, a link failure. In order to advertise the redundant path to a service IP address
from a redundant EIPU node, a stub-network is used.
g The stub network is Nokia Siemens Networks’ proprietary concept and is not related to
the OSPF stub area.
Additionally, the configuration has to include the ingress direction redundant static
routes for the traffic forwarding purposes. The configuration of the ingress direction
redundant static routes is the same as with the static route based use cases.
set routing instance default node EIPU-0 ospf area 100.0.0.0 stub-
network 10.1.0.1/32 on
set routing instance default node EIPU-1 ospf area 100.0.0.0 stub-
network 10.1.0.1/32 on
8 Configure the static routes for the user plane redundancy

The static routes are required in order to reach the service through the redundant EIPU
node, if the EIPU node running the service loses the connection to the network. These
routes cannot be created by OSPF.
g Before configuring the static routes, check the node’s internal IP addresses with role
“cfeigw” for the redundant static routes configuration, enter the following command:
show networking address role cfeigw
The printout is of type:
instant default interfaces:
cfeigw
type : dedicated
address : 169.254.0.6/24
86 Id:0900d805808a1c55 DN0974301
Confidential
owner : /EIPU-0
role : cfeigw
cfeigw
type : dedicated
address : 169.254.0.7/24
owner : /EIPU-1
role : cfeigw
The internal IP addresses are configured automatically during the commissioning phase
and might differ in practice. Listed IP addresses are just examples.
The following is the configuration of the ingress related static routes for the mcRNC user
application IP addresses.
address “cfeigw EIPU-1” on
address “cfeigw EIPU-0” on
DN0974301 Id:0900d805808a1c55 87
Confidential
Configuring IP for O&M connections Configuring IP Connection for Multicontroller RNC
4 Configuring IP for O&M connections

The mcRNC O&M physical connectivity can be built using different schemes. Depend-
ing on the overall transport network configuration, two basic solutions can be applied.
The following are the IP addresses required for all the O&M related services (CFPU
node):
• CFPU network interface IP addresses, used also as the NTP and DNS client source
addresses; owner CFPU
• SSH IP addresses for the shell and SCLI access, basic mcRNC management IP
address; owner SSH Recovery Group
• O&M IP addresses for OMS/NetAct and BTS connections, one or two IP addresses
scheme; owner QNOMU Recovery Group
The RNC O&M IP addressing can be configured using one or two RNC O&M IP
addresses in the QNOMU Recovery Group. The one-address option is similar to the
IPA-RNC, where both OMS/NetAct and BTS connections terminate at the same IP
address. The two-addresses alternative provides the option to keep the BTS and
OMS/NetAct O&M traffic logically separated at the IP layer.
The two O&M addresses configuration scheme requires the following role attributes
configuration for the O&M application IP address:
• BTS O&M, Iub direction: role = “btsom”
• BTS O&M, OMS/NetAct: role = “oms”
g The role attribute is not case sensitive.
If a role attribute is not defined for the O&M application IP address, then the system
operates with one O&M address scheme in respect to BTS O&M connections towards
BTS and OMS/NetAct connectivity.
The SSH connections require their own IP address in the SSH Recovery Group located
in CFPUs. The given IP address provides the local management tool connectivity for
shell access and the SCLI commands. NTP and DNS clients are bound to the network
interface addresses.
4.1 O&M connectivity, solution 1

In case of direct connectivity to BTS through the DCN routers, LAN1 ports associated
with CFPU nodes can be used for connection to both OMS/NetAct and BTS. The
solution 1 cabling and IP addressing is presented in Figure 15 O&M connectivity,
solution 1.
88 Id:0900d805808abf96 DN0974301
Confidential
Configuring IP Connection for Multicontroller RNC Configuring IP for O&M connections
Module 2
BTS O&M a.a.a.a/xx
CFPU-1
cfeigw Router-2
SSH (Active) LAN1 10.0.9.10/29 10.0.9.9/29 Transport
- 10.10.0.2 lo Network
O&M (Active):: QNOMU-0

- 10.10.0.1 lo (role “btsom”)
- 10.10.9.1 lo (role “oms”)
Module 1
DCN, O&M
CFPU-0
cfeigw
SSH (Standby) LAN1 10.0.9.2/29 10.0.9.1/29
OMS b.b.b.b/xx
- 10.10.0.2 lo Router-1
O&M (Standby):: QNOMU-0

- 10.10.0.1 lo (role “btsom”)
- 10.10.9.1 lo (role “oms”)
Figure 15 O&M connectivity, solution 1

1 Configure the physical interface, LAN ports

The LAN ports are fixed to CFPU nodes, the configuration actions are not required.

name. Therefore the VLAN id and the VLAN interface name have to be planned and
configured accordingly.
• SCLI commands examples
#vlan: oam
add networking vlan /CFPU-0 realiface eth0 vid 50 vlaniface
oam_r1
add networking vlan /CFPU-1 realiface eth0 vid 55 vlaniface
oam_r2
• IP Plan
RNC-xx/IP-1/OWNER-CFPU-0/VLAN-oam_r1
• realface = eth0
• vid = 50

The interface addresses are used as source addresses for the NTP and DNS
clients. The “user” attribute is added to the interface address configuration in order
DN0974301 Id:0900d805808abf96 89
Confidential
to get the addresses visible with the corresponding recovery-group-name-based

inquiries.
g The interface name refers to created VLAN interfaces.

add networking address dedicated /CFPU-0 iface oam_r1 ip-
address 10.0.9.2/29 user /ClusterNTP user /ClusterDNS
add networking address dedicated /CFPU-1 iface oam_r2 ip-
address 10.0.9.10/29 user /ClusterNTP user /ClusterDNS
• IP Plan
RNC-xx/IP-1/OWNER-CFPU-0/ADDR-10.0.9.2-oam_r1
• mask = 32
• user = /ClusterNTP, user = /ClusterDNS
4 Configure application IP addresses

The O&M application IP addresses are assigned to the QNOMU recovery group
(RG) and to a loopback interface of the CFPU. The IP address is visible in the
node/unit that is actively running the service at the present time (active recovery unit,
RU).
The SSH IP address is required for the management connection to the mcRNC, to
get the shell and SCLI access.
g The role attribute is a free form character string that can be configured optionally.
The role attribute might be defined to keep the IP addressing usage clearly visible
to simplify the system maintenance.
w If the BTS O&M two-addresses scheme is used, the role attribute must be set to
“btsom” and “oms” to allow the O&M application SW to bind to a proper source IP
address.

• SCLI commands
add networking address dedicated /SSH iface lo ip-address
10.10.0.2/32 role ssh
add networking address dedicated /QNOMU iface lo ip-address
10.10.0.1/32 role btsom
add networking address dedicated /QNOMU iface lo ip-address
10.10.9.1/32 role oms
• IP Plan
RNC-xx/IP-1/OWNER-QNOMU-0/ADDR-10.10.0.1-lo
• mask = 32
90 Id:0900d805808abf96 DN0974301
Confidential

• role = btsom

The static routes configuration is required if OSPF is not used.

CFPU-0 10.10.0.0/30 (O&M 0 cfeigw CFPU-1 Ingress
source “btsom”)
source “oms”)
source “btsom”)
source “oms”)
Table 8 Routing table for ingress traffic

CFPU-0 a.a.a.a/xx (BTS 0 10.0.9.1 (to Router-1) Egress forwarding
O&M destination
subnet)
CFPU-0 a.a.a.a/xx (BTS 8 cfeigw CFPU-1 Egress forwarding, redun-
O&M destination dant route
subnet)
CFPU-0 b.b.b.b/xx (OMS 0 10.0.9.1 (to Router-1) Egress forwarding
O&M destination
subnet)
CFPU-0 b.b.b.b/xx (OMS 8 cfeigw CFPU-1 Egress forwarding, redun-
subnet)
CFPU-1 a.a.a.a/xx (BTS 0 10.0.9.9 (to Router-2) Egress forwarding
O&M destination
subnet)
CFPU-1 a.a.a.a/xx (BTS 8 cfeigw CFPU-0 Egress forwarding, redun-
subnet)
CFPU-1 b.b.b.b/xx (OMS 0 10.0.9.9 (to Router-2) Egress forwarding
O&M destination
subnet)
subnet)
Table 9 Routing table for egress traffic
DN0974301 Id:0900d805808abf96 91
Confidential
• SCLI commands
Ingress redundancy related static routes for the user application IP addresses.
set routing node CFPU-0 static-route 10.10.0.0/30 nexthop
gateway address “cfeigw CFPU-1” on
Egress static routes for the O&M destination subnets, containing primary and sec-
ondary route entry.
set routing node CFPU-0 static-route a.a.a.a/xx nexthop
gateway address 10.0.9.1 on
gateway address “cfeigw CFPU-1” priority 8 on
set routing node CFPU-0 static-route b.b.b.b/xx nexthop
4.2 O&M connectivity, solution 2

In the second solution the LAN1 ports, associated with CFPUs, are used for the O&M
connectivity to OMS and NetAct. The BTS O&M connectivity is provided through the
EIPU units. This solution is used when the BTS can be reached only through the routers
connected to EIPU nodes. Figure 16 O&M connectivity, solution 2 shows the cabling
and basic IP addressing of the solution 2.
92 Id:0900d805808abf96 DN0974301
Confidential
EIPU-1 Router-2
cfeigw 10.0.1.9/30
10.0.1.10/30 (SFP8)
QNUP-0 GW
10.0.0.10/30 (SFP7) BTS O&M a.a.a.a/xx
CFPU-1
10.0.1.1/30
cfeigw
QNOMU-0 GW 10.0.9.10/29 (LAN1) Transport
Network
SSH (Active)
10.10.0.2 lo 10.0.0.9/30
O&M (Standby):: QNOMU-0
- 10.10.0.1 lo (role “btsom”)
- 10.10.9.1 lo (role “oms”)
10.0.0.1/30
Router-1
EIPU-0
DCN router-2
cfeigw 10.0.9.9/29
10.0.1.2/30 (SFP8)
QNUP-0 GW
10.0.0.2/30 (SFP7)
CFPU-0 DCN, O&M

cfeigw
QNOMU-0 GW 10.0.9.2/29 (LAN1)
SSH (Standby) 10.0.9.1/29
10.10.0.2 lo
DCN router-1
O&M (Active):: QNOMU-0 OMS b.b.b.b/xx
- 10.10.0.1 lo (role “btsom”)
- 10.10.9.1 lo (role “oms”)
Figure 16 O&M connectivity, solution 2

The mcRNC CFPU nodes host the O&M Recovery Group (QNOMU). The O&M
recovery group, in two first modules, is using the 2N hot-standby configuration. The
LAN1 interface is associated with CFPU node providing the connectivity to the site
router or DCN router depending on the O&M network setup.
For solution 2, the O&M addressing configuration is the same as for solution 1 (see O&M
connectivity, solution 1), with the exception of step Configure the static routes, which is
as follows:

The static routes configuration is required if OSPF is not used.

source “oms”)
source “oms”)
EIPU-0 10.10.0.1/32 (O&M 0 QNOMU-0 GW Ingress, EIPU to
source “iub”) CFPU/QNOMU
Table 10 Routing table for ingress traffic
DN0974301 Id:0900d805808abf96 93
Confidential

EIPU-1 10.10.9.1/32 (O&M 0 QNOMU-0 GW Ingress, EIPU to
source “iub”) CFPU/QNOMU
Table 10 Routing table for ingress traffic (Cont.)

CFPU-0 a.a.a.a/xx (BTS 0 QNUP-0 (GW) Egress forwarding to BTS
O&M destination subnet through EIPU
subnet)
CFPU-0 b.b.b.b/xx (OMS 0 10.0.9.1 (DCN Router- Egress forwarding, to
O&M destination 1) OMS/NetAct
subnet)
subnet)
CFPU-1 a.a.a.a/xx (BTS 0 QNUP-0 (GW) Egress forwarding, to
O&M destination BTS subnet through EIPU
subnet)
CFPU-1 b.b.b.b/xx (OMS 0 10.0.9.9 (DCN Router- Egress forwarding, to
O&M destination 1) OMS/NetAct
subnet)
subnet)
EIPU-0 a.a.a.a/xx (BTS 0 10.0.0.1 (to Router-1) Egress forwarding, ECMP
O&M destination
subnet)
O&M destination
subnet)
O&M destination
subnet)
O&M destination
subnet)
Table 11 Routing table for egress traffic
• SCLI commands
Ingress redundancy related static routes for the user application IP addresses.
94 Id:0900d805808abf96 DN0974301
Confidential

set routing node EIPU-0 static-route 10.10.0.1/30 nexthop
gateway address “QNOMU GW” on
set routing node EIPU-1 static-route 10.10.0.1/32 nexthop
gateway address “QNOMU GW” on
Egress static routes for the O&M destination subnets, containing primary and sec-
ondary route entry.
gateway address “QNUP-0 GW” on
gateway address “QNUP-0 GW” on
Egress routes for the EIPU nodes towards the BTS O&M subnet
set routing node EIPU-0 static-route a.a.a.a/xx nexthop
DN0974301 Id:0900d805808abf96 95
Confidential
Configuring routing Configuring IP Connection for Multicontroller RNC
5 Configuring routing
5.1 Configuring routing global parameters

Several tools are provided for the user to control the routing procedures in the network
element. Note that some of these tools replace the basic IP management tools, which
are typically used in different than router types of products.
Setting router ID
Set the unique dotted-quad router ID for each router in the routing domain. For instance,
the router ID can be the IPv4 address of the router or any other dotted-quad number
except 0.0.0.0. The user must ensure that the router ID is unique. Virtual routing can be
also used. Virtual routers need individual router ID.
The command for setting the router ID is the following:
set routing instance <name> node <name> router-id <ROUTER_ID>
g If the instance parameter is not specified, then the router ID configuration is applied to
the default instance.
The command for showing the current router ID is the following:

show routing instance <name> node <name> router-id
Setting maximum number of equal-cost paths

The user can specify a maximum number of the equal-cost paths that will be used when
there is more than one equal-cost path to a destination. Setting the maximum number
of the equal-cost paths is not routing instance specific, but general for whole system.
Note that only OSPF and static routes are able to use more than one next hop address,
thus this functionality can only be used with them. The allowed range for the maximum
number of equal-cost paths is from 1 to 8 and the default value is 8. Changing the value
will cause all existing routes to be re-installed. The maximum number of the equal-cost
paths can be set by using the following command:
set routing [instance <name>] node <name> max-path-splits
<value>
The command for displaying the maximum number of equal-cost paths is:
show routing [instance <name>] node <name> max-path-splits
config
Setting tracing for routing

The user can monitor routing system events by enabling the routing trace functionality.
The logging is not turned on by default, because tracing consumes system resources
and can reduce the system performance. Tracing can be enabled either globally for all
protocols or for each protocol separately.
The command for enabling the tracing for routing protocols is the following:
set routing [instance <name>] node <name> trace <protocol> <trace option> on
The command for disabling the tracing for routing protocols is the following:
set routing [instance <name>] node <name> trace <protocol> <trace option> off
The allowed values and trace options are presented in the following table.
96 Id:0900d805808a92ba DN0974301
Confidential
Configuring IP Connection for Multicontroller RNC Configuring routing
Protocol <protocol> Option <trace option>

global adv | parse | cluster |all| general
|normal|policy|route|state|task|
timer
kernel iflist | interface | packets | remnants
| request | routes|all|general|
normal|policy
ospf ack | dd | dr | hello | lsa | packets |
request | spf | trap | update |all|
general| normal| policy | route | state |
task | timer| spf-timer
Table 12 Trace options and values for routing configuration
To display the tracing for routing protocols, enter the following command:
show routing [instance <name>] node <name> trace <trace option> config
For example, enable the tracing in the CLA-0 node for all options related to the OSPF
protocol by entering the following command:
set routing node CLA-0 trace ospf all on
The latest trace logs are saved in the ipsrd.log file in the /var/log directory. The
user can adjust the maximum size and number of the backup trace files. When the trace
file reaches the maximum size, it is renamed as a numbered backup file; for instance,
the first backup trace file is named /var/log/ipsrd.log.0.
To display the tracing in the CLA-0 node for global option, enter the following
command:
show routing node CLA-0 trace global config
To display the tracing in the CLA-0 node for kernel option, enter the following
command:
show routing node CLA-0 trace kernel config
To display the tracing in the CLA-0 node for ospf (IPv4 protocol) option, enter the fol-
lowing command:
show routing node CLA-0 trace ospf config
To display the tracing in the CLA-0 node for ospf3 (IPv6 protocol) option, enter the fol-
lowing command:
show routing node CLA-0 ipv6 trace ospf3 config
The command for setting the maximum size of the trace file (in megabytes) is the follow-
ing:
set routing node <name> tracefile size <1-4095>
The default size is one megabyte. The user must ensure that enough disk space exists
for the trace log files.
The command for setting the maximum number of trace files is the following:
set routing node <name> tracefile maxnum <1-1000>
The default number of trace files is 10. When the maximum number of the trace log files
is exceeded, the oldest file will be removed. The user must ensure that enough disk
space exists for the trace log files.
DN0974301 Id:0900d805808a92ba 97
Confidential
Configuring routing Configuring IP Connection for Multicontroller RNC
To display the trace files in the CLA-0 node, enter the following command:
show routing [instance <name>] node CLA-0 tracefile\
config
98 Id:0900d805808a92ba DN0974301
Confidential
5.2 Configuring static routes for IPv4

Before you start
If the virtual routing is used, check that the routing instances are created and interfaces
are set to the correct routing instances. In the commands presented in this chapter, the
routing instances are defined with the optional instance <name> parameter that is
attached in the commands. In the command syntax the parameter is placed right after
the routing parameter.
g You can use transactions to bundle multiple changes into one bigger change. Note also
that you can prevent other users from interfering with your configuration changes by
using the configuration locking feature.
Summary
The static routes can be configured by using the set routing node <node>
static-route SCLI command.
To configure the static routes for IPv4, you have to first define them. Then, if needed,
set the protocol rank for them and verify your configuration.
The parameters of all the commands are described at the end of this section, under
Further information.
Steps
1 Define a route to the default gateway.

You can define a default route by creating a static route over the full address space. This
route is selected if any of the more specific routes does not match. The default route can
be created using a default key word. It equals to network address 0.0.0.0/0. The
default route is created with the following command:
set routing node <name> static-route default nexthop gateway
address <address> on
You can remove the default route with the following command:
set routing node <name> static-route default off
2 Define a static route to the next hop gateway.

You can define multiple static routes to next hop gateways. The static route defines a
next hop gateway for packets that are destined to a specified IP address range. The
route is defined with the following command:
set routing [instance <name>] node <name> static-route
<IP_PREFIX|default> nexthop gateway address <address> [priority
<1-8>] on
An individual static route per gateway can be removed with the following command:
<IP_PREFIX|default> nexthop gateway address <address> off
All routes for a given subnet can be removed with the following command:
<IP_PREFIX|default> off
DN0974301 Id:0900d8058088d42d 99
Confidential
For nodes where the routing daemon is not deployed, the MTU size and source IP
address can be set for the default static route using the following commands:
<IP_PREFIX|default> mtu <mtu-size>
<IP_PREFIX|default> source <IP-address>
3 Enable packet rejecting.

Instead of forwarding packets to the next hop, you can optionally create reject or black-
hole type routes. Reject causes packets to be dropped and unreachable messages to
be sent to packet originators.
Blackhole causes packets to be dropped but does not cause unreachable messages to
be sent. These can be used, for example, to drop temporarily all packets generated by
a denial of service attack.
The reject and blackhole type routes are created with the following commands:
set routing [instance <name>] node <node> static-route
<IP_PREFIX|default> nexthop reject
<IP_PREFIX|default> nexthop blackhole
4 Enable or disable the BFD protocol for the existing static route.
The BFD protocol can be enabled or disabled using the following command:
set routing [instance <name>] node <node_name> static-route
<IP_PREFIX|default> nexthop gateway address <address> [priority
<1-8>] [bfd-tx-interval <tx-interval |default>] [bfd-rx-
interval <rx-interval|default>] [bfd-monitoring
<enabled|disabled>] on
To enable the BFD protocol set the bfd-monitoring parameter to enabled.To disable
the BFD protocol set the bfd-monitoring parameter to disabled.
5 Configure the BFD hold time for existing routes.

The parameter bfd-static-holdtime is used to configure the hold time for all BFD
sessions for static routes. The command syntax is as follows:
set routing [instance <name>] node <node> bfd-static-holdtime
<bfd-static-holdtime>
The range of bfd-static-holdtime is 0 to 900 ms. If you don’t specify the value, the
default value is 0.
To display the BFD hold time parameter configured for the static route, enter the follow-
ing commands:
show routing [instance <name>] node <node> bfd-static-holdtime
config
show routing [instance <instance_name>] node <node_name>
static-route config
100 Id:0900d8058088d42d DN0974301

Confidential
show routing [instance <instance_name>] node <node_name>

static-route config all
6 Configure protocol rank for existing routes.

You can define protocol rank for existing static routes. Rank is used by the routing
system to determine which route is used when there are routes from different protocols
to same destination.
The new rank for the given static route is defined with the following command:
<IP_PREFIX|default> rank <0-255>
7 Monitor static routes.

You can monitor the status of the static routes with the command:
show routing [instance <name>] node <name> static-route config
Example:
To monitor the status of the static routes configured for the CFPU-0 node, enter the fol-
lowing command:
show routing node CFPU-0 static-route config all
The following output is displayed:
Instance: default
Static route: default Next hop type: normal Rank: not defined
Gateway: 10.102.236.1 Preference: not defined
BFD monitoring: disabled BFD tx interval: 1000 BFD rx interval:
1000 BFD detect multiplier:
Further information
Details of the parameters of the routing command are shown in the table below.

instance <name> The routing configuration is
instance specified by this
parameter. If no instance is
specified, the routing
default routing instance. This is
an optional parameter..
g Note that in mcRNC

release 1 only default
routing instance is
supported.
node <node-name> The node name where the static
route configuration takes place.
address <address> IP address of the gateway.
Table 13 Parameters for configuring static routes
DN0974301 Id:0900d8058088d42d 101

Confidential

mtu <mtu-size> The maximum transmission unit The allowed value range is
(MTU) value of the default static 1280 to 9000.
route. Optional parameter.
g This parameter is
supported only for nodes in
which the Routing Daemon
is not deployed.
source <IP-address> The source IP address or range
of IP addresses selector written
in format <IP-address/mask>.
Optional parameter.
g This parameter is
supported only for nodes in
which the Routing Daemon
is not deployed.
<IP_PREFIX|default> The destination network prefix: unicast IPv4 address
address in the form of mask: network mask in the
prefix/mask, where the prefix is range 1 to 32.
unicast IPv4 address and the
mask is a network mask.
priority <1-8> Priority of the static route. The The allowed range is from 1 to
higher priority (lower value) 8.
next hops are preferred.
Switching over to the next route
in the list happens only if the
interface fails. It does not
happen for non-reachable next
hops if the interface is still up. If
the priority is the same and the
interface is up, it will be an
equal cost, multipath route.
bfd-tx-interval <tx- The minimum interval, in The allowed value is in the
interval milliseconds, between the range 50ms to 60000ms with a
|default> transmitted BFD control granularity of 50 ms. The
packets. Optional parameter. default value is 1000 ms.
This parameter accepts either
the numeric value or the value
default. If the value
default is used, then the
value of bfd-tx-interval is
set to a default value of 1000
ms.
Table 13 Parameters for configuring static routes (Cont.)
102 Id:0900d8058088d42d DN0974301

Confidential

bfd-rx-interval <rx- The minimum interval, in The allowed value is in the
interval|default> milliseconds, between the range 50 ms to 60000 ms with
received BFD control packets. a granularity of 50 ms. The
Optional parameter. default value is 1000 ms.
This parameter accepts either
the numeric value or the value
default. If the value
default is used, then the
value of bfd-rx-interval is
set to a default value of 1000
ms.
bfd-detect-mult The desired detection time The allowed value is in the
<mult-value|default> multiplier for the BFD control range 1 to 50. The default
packets on the local system. value is 4.
The negotiated control packet This parameter accepts either
transmission interval, multiplied the numeric value or the value
by this parameter, is the default. If the value
detection time for a particular default is used, then the
BFD session. Optional value of bfd-detect-mult is
parameter. set to a default value of 4.
bfd-monitoring Enables or disables the BFD The allowed values are
<enabled|disabled> protocol for the static route. enabled and disabled.
Optional parameter.
The BFD monitoring is disabled
by default.
rank <0-255> The route from protocol with the You can define a different rank
lowest rank is used. from the range between 0 and
255. By default, the static
routes have a rank value of 60,
OSPF routes have 10, and
OSPF ASE routes have 150.
Table 13 Parameters for configuring static routes (Cont.)
DN0974301 Id:0900d8058088d42d 103

Confidential
5.3 Configuring OSPF
5.3.1 Configuring OSPFv2 overview

This chapter provides an overview and operating instructions on mcRNC related to
RAN1879: Dynamic routing by OSPF.
The Open Shortest Path First (OSPF) is configured on the external Ethernet interface of
the mcRNC. Some of the key benefits this feature brings to the mcRNC are reducing
configuration effort and fast convergence. In addition, it provides robustness in case of
link failure because traffic can be dynamically re-routed.
The OSPF area scheme for mcRNC is shown in the figure below. The external inter-
faces of the two BCN modules and the router interfaces connected to the modules are
in area 100. And the router interfaces towards the backbone are in backbone area 0.
Figure 17 OSPF area scheme

To avoid flooding AS external advertisements into an area, you can set this area to stub
area. For stub areas, the border router automatically advertises a default route in place
of the external routes that are not being advertised within the stub area so that routers
in the stub area can reach destinations outside the area. This reduces the link-state
104 Id:0900d805808abb81 DN0974301

Confidential
database size, and therefore the memory requirements, for a stub area’s internal
routers.
The following subchapters introduce the procedure of OSPF configuration and route
redistribution if you want to export routes to OSPF protocol on a node.
DN0974301 Id:0900d805808abb81 105

Confidential
5.3.2 Configuring OSPFv2

Purpose
To configure and monitor the OSPFv2 routing protocol.
Configuration of OSPFv2 requires only a few mandatory steps. Other optional steps
may be required depending on your environment. After the network interfaces are
created, enable the OSPF areas and define an area for each interface. In addition, you
can configure a large number of global, interface, and area-related OSPF parameters.
This procedure also introduces how to verify the configuration and how to monitor
routing tables and statistics.
Before you start

Check that the routing instances are created, if virtual routing is being used and set to
the correct interfaces. In addition, some OSPF commands require that the IP addresses
are assigned to the interfaces before the command can be executed. In the commands
presented in this chapter, the routing instances are defined with the optional instance
<name> parameter that is attached in the commands. In the command syntax, the
parameter is placed right after the routing parameter.
g To bundle multiple changes into one bigger change, use the transaction feature. To
prevent other users from interfering with your configuration changes, use the configura-
tion locking feature.
Steps
1 Configure OSPF areas.

Every OSPF router must belong to at least one area. If there is more than one area, at
least one area must be a backbone area. To add areas, modify the area parameters,
such as: backbone, stub, and totally-stubby.
Create a backbone area with the backbone keyword. This automatically creates an
identifier 0.0.0.0 which is reserved exclusively for the backbone area. Create other
areas with your selected identifiers. The identifier should be given as a dotted/quad
value or as a 32-bit number. You can use your subnetted IPv4 network address as area
IDs.
The OSPF area configuration can be defined using the following command:
set routing [instance <name>] node <name> ospf area
g Disabling the areas does not delete the configuration information. Thus, they can be
enabled later without a need for re-configuring.
The parameters of the commands (the part after the ospf parameter) are presented in
the following table.

area backbone This parameter enables/disables The allowed values are on
<on|off> the backbone area. Enabling the and off. The default value
backbone area sets the area ID is off.
0.0.0.0 for the backbone area.
Table 14 Commands for configuring OSPF areas
106 Id:0900d805808abb78 DN0974301

Confidential

area <OSPF_AREA> This parameter enables/disables The allowed values are on
<on|off> an OSPF area. Enabling the OSPF and off. The default value
area sets the specified area ID. is off.
area <OSPF_AREA> stub This parameter enables/disables The allowed values are on
<on|off> an OSPF stub area. A stub area is and off. The default value
an area which does not have is off.
external routes. Enabling the
OSPF stub area sets the specified
area ID for the stub area.
area <OSPF_AREA> stub This parameter sets the cost for The allowed values are
default-cost <1- the default summary route for the from 1 to 65535. The
65535> stub area. default value is 1.
area <OSPF_AREA> stub This parameter sets the stub area The allowed values are on
summary <on|off> to forward or block summary infor- and off.The default value
mation. If a stub area (area without is off.
external routes), does not have
summary routes it is called a
totally-stubby-area.
area {backbone | This parameter defines the range The allowed values are on
<OSPF_AREA>} range of networks belonging to an area. and off.
<IP_PREFIX> <on|off>
<OSPF_AREA>} range of networks belonging to an area in and off.
<IP_PREFIX> restrict which the summary network LSAs
<on|off> are not sent.
<OSPF_AREA>} stub- of networks belonging to a stub and off.
network <IP_PREFIX> network.
<on|off>
area {backbone | This parameter defines the cost for The allowed values are
<OSPF_AREA>} stub- the default route in a stub network. from 1 to 16777215. The
network <IP_PREFIX> default value is 1.
cost <1-16777215>
area backbone This parameter enables/disables a The allowed values are on
virtual-link virtual link from the router that does and off . The default
<ROUTER_ID> transit- not have connection to a backbone value is off.
area <OSPF_AREA> network. Virtual link is defined
<on|off> through an adjacent non-backbone
area (transit area) by defining the
termination point of the virtual link
and the ID of the transit area. The
termination point is the router ID of
the adjacent area's border router
having the backbone connection.
The transit area is an area that is
shared by the router you are con-
figuring and the router having the
backbone connection. The area ID
must be pre-configured using the
basic area commands.
Table 14 Commands for configuring OSPF areas (Cont.)
DN0974301 Id:0900d805808abb78 107

Confidential

area backbone This parameter sets the hello- The allowed values are
virtual-link interval in seconds for the virtual from 1 to 65535.
<ROUTER_ID> transit- link. The default value is 30.
area <OSPF_AREA>
hello-interval <time>
area backbone This parameter sets the dead- The allowed values are
area <OSPF_AREA>
dead-interval <time>
area backbone This parameter sets the retransmit- The allowed values are
area <OSPF_AREA>
retransmit-interval
<time>
area backbone This parameter disables the
virtual-link authentication for the virtual link.
<ROUTER_ID> transit-
area <OSPF_AREA>
authtype none
area backbone This parameter selects the simple
virtual-link authentication type for the virtual
<ROUTER_ID> transit- link and define the 1 to 8 alpha
area <OSPF_AREA> numerical characters authentica-
authtype simple tion key. Generally, routers on a
given link must agree on the
authentication configuration to
form a neighbor adjacency. The
authentication scheme Is used to
verify that the routing information is
received from trusted peers.
area backbone This parameter selects the MD5 The allowed parameters
virtual-link authentication. Enter at least one are:
<ROUTER_ID> transit- key ID and its corresponding MD5
• <AUTH_KEYID> : 1 to
area <OSPF_AREA> secret . In outgoing packets, the
255
authtype md5 key MD5 secret is included in
<AUTH_KEYID> secret encrypted form to authenticate the • <MD5_SECRET> : All
<MD5_SECRET> packet and if you configure printable 7-bit ASCII
multiple key IDs, the largest key ID characters except the
is used for authenticating the double quotation
packets. All keys can be used to mark.
authenticate incoming packets.
Routers on a given link must agree
g The MD5 secret
on the authentication configuration should be surrounded
to form a neighbor adjacency. Use by double quotation
an authentication scheme to guar- marks when non-
antee that routing information is alphanumeric charac-
accepted only from trusted peers.
ters are used.
108 Id:0900d805808abb78 DN0974301

Confidential

area backbone This parameter deletes the MD5
virtual-link key in question.
<ROUTER_ID> transit-
area <OSPF_AREA>
authtype md5 key
<AUTH_KEYID> off
2 Configure the OSPF interfaces.

Attach an interface to each area that uses OSPF area.
Verify that the interface configuration is compatible with the environment into which the
equipment is integrated. Both hello-interval and dead-interval values should
be the same as the corresponding values in every node within the same area. The
authentication information is provided to all nodes if simple or MD5 authentication is
used.
To define the interface configuration, use the following command:
set routing [instance <name>] node <name> ospf interface
The parameterss of the command (the part after the ospf parameter) are presented in
the following table:

interface <IFNAME> This parameter assigns an OSPF The allowed values are on
area {backbone | area to an interface. The area should and off.
<OSPF_AREA>} be defined earlier.
<on|off>
interface <IFNAME> This parameter sets the hello- The allowed values are
hello-interval interval in seconds. from 1 to 65535.
<time> The default value is 10.
interface <IFNAME> This parameter specifies the time in The allowed values are
fast-hello-interval milliseconds between the hello from 50 to 950 ms with a
packets that the router sends to the granularity of 50 ms.
interface. The default value is 200
ms.
interface <IFNAME> This paramerer sets the dead- The allowed values are
dead-interval <time> interval in seconds. from 1 to 4294967295.
The default value is 40.
interface <IFNAME> This paramerer sets the retransmit- The allowed values are
retransmit-interval interval in seconds. from 1 to 4294967295.
<time> The default value is 5.
interface <IFNAME> This paramerer sets the cost for The allowed values are
cost <value> sending packets over an interface. from 1 to 65535.
Table 15 Commands for configuring OSPF interfaces
DN0974301 Id:0900d805808abb78 109

Confidential

interface <IFNAME> This paramerer defines the election The allowed values are
priority <value> priority for OSPF router/interface. from 0 to 255.
The router with the highest priority is The default value is 1.
selected to be the designated router.
The router with priority equal to 0 will
not be selected as the designated
router.
interface <IFNAME> This paramerer sets the OSPF inter- The allowed values are on
passive <on|off> face to passive state. In passive and off.
state, the OSPF interface does not
send hello packets and therefore the
link does not form any adjacencies.
interface <IFNAME> This paramerer disables authentica-
authtype none tion.
interface <IFNAME> This paramerer enables simple The allowed values are 1 to
authtype simple authentication and sets the pass- 8 alpha numerical charac-
<PASSWORD> word. Generally, routers on a given ters.
link must agree on the authentication
configuration to form neighbor adja-
cency. The authentication scheme is
used to verify that the routing infor-
mation is received from trusted
peers.
interface <IFNAME> This paramerer enables MD5 The allowed values are:
authtype md5 key authentication. Enter at least one key
• <AUTH_KEYID>: 1 to
<AUTH_KEYID> secret ID and its corresponding MD5
255
<MD5_SECRET> secret. If you configure multiple key
ids, the largest key ID is used for • <MD5_SECRET>: 1 to
authenticating outgoing packets. All 16 alphanumeric char-
keys can be used to authenticate acters.
incoming packets. Routers on a
given link must agree on the authen-
tication configuration to form
neighbor adjacency. Use an authen-
tication scheme to guarantee that
routing information is accepted only
from trusted peers.
interface <IFNAME> This paramerer deletes the MD5 key
authtype md5 key in question.
<AUTH_KEYID> off
Table 15 Commands for configuring OSPF interfaces (Cont.)
3 Configure global OSPF parameters.

A set of generic OSPF parameters allows you to tune the system wide routing parame-
ters. The system-wide parameters include the RFC 1583 compatibility setting, the
shortest path first (SPF) algorithm tuning parameters, and the defaults used when
importing OSPF routes from the external autonomous system and advertising these
routes to other OSPF nodes. The RFC 1583 compatibility is enabled by default. It must
be enabled if your environment includes other elements that are based on RFC 1583.
The syntax of the command for configuring the global OSPF settings is:
110 Id:0900d805808abb78 DN0974301

Confidential
set routing [instance <name>] node <name> ospf [rfc1583-

combatibility <on|off>] [spf-delay <time>] [spf-holdtime
<time>] [default-ase-cost <value>] [default-ase-type <1-2>]
[throttle {spf-delay <time>|spf-holdtime-start <time> | spf-
holdtime-max <time>}]
The parameters (the part after the ospf parameter) for global OSPF settings are pre-
sented in the table below:

rfc1583- This parameter enables/disables the The allowed values are
compatibility RFC 1583 compatibility. The current on and off.
<on|off> version supports OSPFv2 as defined in The default value is on.
RFC 2178. RFC 2178 replaced earlier
RFC 1583 by providing improved
security and loop avoidance.
spf-delay <time> This parameter sets the delay in The allowed values are
seconds between the first new LSA and from 1 to 60.
the resulting SPF calculation (this is the The default value is 2.
calculation of a routing table).
spf-holdtime <time> This parameter sets the delay in The allowed values are
seconds between successive SPF cal- from 1 to 60.
culations. The spf-holdtime is not The default value is 5.
configurable and is dynamically deter-
mined by the spf-holdtime-start
and spf-holdtime-max parameters.
The current value of spf-holdtime
can be determined using the show
routing [instance<name>] node
<name> ipv6 command.
default-ase-cost This parameter sets the default cost The allowed values are
<value> used for advertising non-OSPF routes from 1 to 16777215.
as autonomous system external (ASE). The default value is 1.
default-ase-type This parameter defines the type of ASE The allowed values are 1
<1-2> route used or use the default (1). For and 2.
type 1 ASE, the total cost of the route is The default value is 1.
the sum of the AS external and internal
costs. For type 2 ASE, the cost of the
route is always the AS external cost.
throttle {spf-delay This parameter specifies the time to The allowed values are
<time>} wait in milliseconds before recalculating from 100 to 60000 ms
the OSPF routing table after a change with a granularity of 100
in the topology. ms.
The default value is 200
ms.
Table 16 The commands for configuring global OSPF parameters
DN0974301 Id:0900d805808abb78 111

Confidential

throttle{spf- This parameter specifies the initial The allowed values are
holdtime-start value to be used as delay between the from 100 to 60000 ms
<time>} successive SPF calculations. This with a granularity of 100
delay is also known as spf- ms.
holdtime. If a topology change occurs The default value is
during the delay, it causes the next 10000 ms.
spf-holdtime to be increased by 100
ms until it reaches spf-holdtime-
max. If there are no topology changes
during the spf-holdtime wait inter-
val, the value of spf-holdtime will be
reset to the initial value (spf-
holdtime-start).
throttle{spf- This parameter specifies the maximum The allowed values are
holdtime-max delay in milliseconds between the suc- from 100 to 60000 ms
<time>} cessive SPF calculations. If a topology with a granularity of 100
change occurs during the delay, it ms.
causes the next spf-holdtime to be The default value is
increased by 100ms until it reaches 10000 ms.
spf-holdtime-max. If there are no
topology changes during the spf-
holdtime wait interval, the value of
spf-holdtime will be reset to the
initial value (spf-holdtime-start).
Table 16 The commands for configuring global OSPF parameters (Cont.)
4 Monitor OSPF protocol.

Monitor the OSPF protocol by using the show routing [instance <name>] node
<name> ospf command.
The parameters to be entered after the ospf command are presented in the following
table:
Parameter Description
summary This parameter displays a summary of the OSPF status, including the
number of areas configured.
config This parameter displays an OSPF configuration for a specific routing
instance.
config all This parameter displays an OSPF configuration for all routing
instances.
neighbors This parameter displays the IP addresses of neighboring interfaces,
their election priority and status and the number of errors logged for
each interface.
neighbor This parameter displays the election priority, status and number of
<IPADDRESS> errors logged for the specified IP address or neighbor ID.
Table 17 Parameters for monitoring OSPF protocol
112 Id:0900d805808abb78 DN0974301

Confidential
interfaces This parameter displays the names of all configured OSPF interfaces,
their corresponding IP addresses, the area to which each interface is
assigned, the status of each interface and the IP addresses of the des-
ignated router and backup designated router of each logical interface.
interfaces This parameter displays detailed information about each OSPF inter-
detailed face, including the authentication type configured (if any), the router IDs
and IP addresses of the designated router and backup designated
router, the timer intervals configured for hello, wait, dead and restrans-
mit messages and the number of neighbors for each interface.
interfaces stats This parameter displays the number of each type of error message
logged by each interface.
interface This parameter displays the information on the specified OSPF inter-
<IFNAME> face.
interface This parameter displays the number of each type of error message
<IFNAME> stats logged by the specified interface.
interface This parameter displays detailed information about the specified inter-
<IFNAME> face, including the authentication type configured if any, the router IDs
detailed and IP addresses of the designated router and backup designated
router, the timer intervals configured for hello wait, dead and restrans-
mit messages and the number of neighbors for each interface.
packets This parameter displays the number of each type of packet sent, includ-
ing hello packets, link state update packets, database description
packets and link state acknowledgment and link state request packets.
errors This parameter displays the total number of each type of error message
sent, including hello protocol errors, database description errors,
protocol errors, link state acknowledgment errors, link state request
errors, link state update errors and IP errors.
errors dd This parameter displays the number of each type of database descrip-
tion error messages only.
errors hello This parameter displays the number of each type of hello error
messages only.
errors ip This parameter displays the number of each type of IP error messages
only.
errors lsack This parameter displays the number of each type of link state acknowl-
edgment error messages only.
errors lsu This parameter displays the number of each type of link state update
error messages only.
errors lsr This parameter displays the number of each type of link state request
error messages only.
errors protocol This parameter displays the number of each type of protocol error
messages only.
border-routers This parameter displays the border router ID, type of the border router
and the cost to the border router.
database This parameter displays the OSPF link-state database information.
Table 17 Parameters for monitoring OSPF protocol (Cont.)
DN0974301 Id:0900d805808abb78 113

Confidential
database areas This parameter displays router link state, network link state, AS border
router link state, AS external link state and summary link state statistics
for each OSPF area. Also displays the checksum, sequence number
and link count of each OSPF interface.
database area This parameter displays router link state, network link state, AS border
<OSPF_AREA> router link state, AS external link state and summary link state statistics
for the specified OSPF area. Also displays the checksum, sequence
number and link count of each IP address configured within the speci-
fied OSPF area.
database asbr- This parameter displays a summary of AS border router link state infor-
summary-lsa mation for each OSPF area.
database This parameter displays a checksum calculated from the total LSA
checksum database. It is useful for comparing databases on different routers.
database This parameter displays a summary of router link state, network link
database-summary state, summary link state and AS border router link state statistics.
database This parameter displays network link state information, including the
network-lsa advertised router, sequence number and checksum of each OSPF
interface.
database This parameter displays AS external link state information.
external-lsa
database router- This parameter displays a summary of router link state information for
lsa each OSPF area.
database This parameter displays a summary of link state information for each
summary-lsa OSPF area.
database type This parameter displays link state information associated with the spec-
<1-5> ified value.
The allowed values are 1 to 5:
• The value 1 displays router link state statistics.
• The value 2 displays network link state statistics.
• The value 3 displays summary link state statistics.
• The value 4 displays AS border router link state statistics.
• The value 5 displays AS external link state statistics.
events This parameter displays the OSPF routing events, for example number
of interface up/down events, virtual interface up/down events, desig-
nated router election events, router ID changes, area border router
changes, AS border router changes and number of self LSA promos.
Table 17 Parameters for monitoring OSPF protocol (Cont.)
Further information
The parameters used in all the commands in this paocedure are presented in the follow-
ing table:
114 Id:0900d805808abb78 DN0974301

Confidential
instance <name> The routing configuration is applied to or displayed from the virtual
routing instance specified by this parameter. This is an optional
parameter.If no instance is specified, the routing configuration is
applied to the default routing instance.
node <node-name> This parameter specifies the node name where the route
configuration takes place.
Table 18 The OSPFv2 configuration parameters.
DN0974301 Id:0900d805808abb78 115

Confidential
5.3.3 Redistributing routes to OSPF protocol

Purpose
This section shows how to redistribute routes to OSPF protocol.
5.3.3.1 Redistribute static routes

Purpose
To redistribute static routes to OSPF protocol.
Steps
1 Enable the redistribution.

The static routes are exported by using the following command:
set routing [instance <name>] node <node-name> export <export-
protocol> static-route <route> on
2 Set the cost for the exported route.

The cost for the exported route is set by using the following command:
protocol> static-route <route> cost <cost-value>
5.3.3.2 Redistribute aggregate routes

Purpose
To redistribute aggregate routes to OSPF protocol.
Steps

The aggregate routes are exported by using the following command:
protocol> aggregate <IP_prefix> on

protocol> aggregate <IP_prefix> cost <cost-value>
5.3.3.3 Redistribute direct routes

Purpose
To redistribute direct routes to OSPF protocol.
116 Id:0900d805808bdf12 DN0974301

Confidential
Steps

The direct interface routes are exported by using the following command:
protocol> direct {all | interface-name <name>} on

protocol> direct {all | interface-name <name>} cost <cost-
value>
Further information
The parameters for the route redistribution commands are listed in the following table:

instance The routing configuration is
instance specified by this
parameter. This is an optional
parameter. If no instance is
specified, the routing
node <node-name> This parameter specifies the
name of the node where the route
redistributing takes place.
export <export- This parameter specifies the The allowed value is
protocol> name of the protocol where to ospf2ase.
redistribute the routes to.
aggregate This parameter specifies the The value can be either a
<IP_prefix> network address of the aggregate specific route in the format
route. prefix/mask, or all for all
routes.
cost <cost-value> Specifies the cost for the created The cost value can be in the
external route. range from 1 to 16777215.
static-route <route> Specifies the static route to be Use value all to redistribute
redistributed to the OSPF external all static routes, or give the
route. individual route in the form of
prefix/mask.
direct {all | This parameter specifies that all Use value all to redistribute
interface-name currently active routes must be all interface routes, or give
<name>} redistributed into the the interface-name
OSPFexternal route. If this setting parameter followed by the
is 'on', routes can be individually name of the individual
restricted into OSPF external interface.
route and vice-versa.
Table 19 Parameters for redistributing routes between protocols
DN0974301 Id:0900d805808bdf12 117

Confidential
5.4 BFD configuration
5.4.1 BFD protocol

Bidirectional Forwarding Detection (BFD) is a network protocol used to detect faults
between two hosts connected by a link. It provides low-overhead detection of faults even
on physical media that do not support failure detection of any kind, such as Ethernet,
virtual circuits, tunnels and MPLS Label switched paths.
The important features of BFD are:
• The protocol is independent of the data protocol being forwarded between two
systems.
• BFD packets are carried as the payload of the encapsulating protocol appropriate
for the medium and network.
• It provides failure detection on any kind of path between systems, including direct
physical links, virtual circuits, tunnels, MPLS, LSPs, multihop routed paths, and uni-
directional links.
• Ability to be bootstrapped by any other protocol that automatically forms peer,
neighbor or adjacency relationships to provide BFD endpoint discovery.
BFD single-hop sessions can be used to track IPv4 and IPv6 connectivity between
directly connected systems. It can also be used to supplement the detection mecha-
nisms in routing protocols, or to monitor router-host connectivity, among other applica-
tions.
g The BFD singlehop session is not supported as a standalone feature and is integrated
with the routing daemon.
The BFD multihop session can be used to detect faults on arbitrary paths between
systems, which may span multiple network hops and follow unpredictable paths.
g In mcRNC release one, only mulihop BFD is supported.
118 Id:0900d8058085e748 DN0974301

Confidential
5.4.2 Configuring the BFD multihop session

Purpose
To configure the BFD multihop session.
Steps
1 Add the BFD multihop session

The BFD multihop session can be added using the add networking bfd session
command. The full syntax of the command is:
add networking instance <instance_name> bfd session <owner>
srcaddr <srcaddr_value> dstaddr <dstaddr_value> [tx-interval
<tx-interval>][rx-interval <rx-interval>] [detect-mult <detect-
mult>]
Example:
To add the BFD multihop session for the default instance of the CFPU-0 node, enter the
following command:
add networking instance default bfd session /CFPU-0 srcaddr
192.168.0.1 dstaddr 192.168.0.2 tx-interval 100 rx-interval 100
detect-mult 6
2 Modify the existing BFD multihop session

The BFD multihop session can be modified using the set networking bfd
command. The full syntax of the command is:
set networking instance <instance_name> bfd session <owner>
srcaddr <srcaddr_value> dstaddr <dstaddr_value> [tx-interval
<tx-interval>][rx-interval <rx-interval>] detect-mult <detect-
mult>
Example:
To modify the existing multihop BFD session of the CFPU-0 node, enter the following
command:
set networking instance default bfd session /CFPU-0 srcaddr
192.168.0.1 dstaddr 192.168.0.2 tx-interval 200 rx-interval 200
detect-mult 4
In this example, the rx-interval and tx-interval is changed to 200 ms and the
value of detect-mult parameter is changed to 4.
3 Display the existing BFD multihop sessions

The BFD multihop session can be displayed using the show networking bfd
command.
To display all the BFD multihop sessions, enter the following command:
show networking bfd config all
To display the multihop BFD sessions configured for a particular instance and node,
enter the following command:
DN0974301 Id:0900d8058085e746 119

Confidential
show networking instance <instance_name> bfd session owner

<node> config
To display the multihop BFD sessions configured with a particular source and destina-
tion address, enter the following command:
show networking instance <instance_name> bfd session owner
<node> srcaddr <unicast_address> dstaddr <unicast_address>
config
Example:
To display the BFD multihop sessions configured with a source address of
192.168.0.1 and destination address of 192.168.0.2, enter the following
command:
show networking instance default bfd session owner /CFPU-0
srcaddr 192.168.0.1 dstaddr 192.168.0.2 config
4 Delete the BFD multihop sessions

The BFD multihop session can be deleted using the delete networking bfd
session command. The full syntax of the command is:
delete networking instance <instance_name> bfd session <owner>
srcaddr <srcaddr_value> dstaddr <dstaddr_value>
Example:
To delete the BFD multihop sessions of the CFPU-0 node, enter the following command:
delete networking instance default bfd session owner /CFPU-0
srcaddr 192.168.0.1 dstaddr 192.168.0.2
Further information
The following table describes the parameters for the BFD commands.

<owner> Specifies the node name, where the
multihop BFD session is added. This
is a mandatory parameter.
<instance> The multihop BFD session is added
to the virtual routing instance
specified by this parameter. If the
instance parameter is not specified,
then the BFD session is added to the
default routing instance. This is an
optional parameter.
g Note that for mcRNC release 1

supported.
Table 20 Mandatory and optional parameters for the BFD commands
120 Id:0900d8058085e746 DN0974301

Confidential

srcaddr Specifies the source address. The
source address can be an IPv4 or
IPv6 address. This is a mandatory
parameter.
dstaddr Specifies the destination address.
The destination address can be an
IPv4 or IPv6 address. This is a
mandatory parameter.
tx-interval The minimum interval, in The allowed value is in the
milliseconds, between the range 50ms to 60000ms
transmitted BFD control packets that with a granularity of 50ms.
the system uses at the current time. The default value is
This is an optional parameter. 1000ms.
rx-interval The minimum interval, in The allowed value is in the
milliseconds, between the received range 50ms to 60000 ms
BFD control packets that the system with a granularity of 50ms.
requires. This is an optional The default value is
parameter. 1000ms.
detect-mult The desired detection time multiplier The allowed value is in the
for the BFD control packets on the range 1 to 50. The default
local system. The negotiated control value is 4.
packet transmission interval,
multiplied by this parameter, will be
the detection time for a particular
BFD session. This is an optional
parameter.
Table 20 Mandatory and optional parameters for the BFD commands (Cont.)
DN0974301 Id:0900d8058085e746 121

Confidential
5.4.3 Displaying the runtime information for the multihop BFD session
Summary
The runtime information for the multihop BFD session is listed using the show
networking bfd runtime node <node-name> command.
Steps
1 Display the runtime information for the multihop BFD session.

To display the runtime information for the multihop BFD session, enter the following
command:
show networking bfd runtime node <node-name>
The full syntax of the command is:
show networking [instance <instance_name>] bfd runtime node <node-name> [srcaddr
<srcaddr_value>][dstaddr <dstaddr_value>][state <state_info>]
Instead of listing the runtime information for all multihop BFD sessions, you can filter the
printout using the following options:
[instance <NAME>] Displays the runtime information for the multihop BFD
session with the specified instance.
g Note that for mcRNC release 1 only supports

node <node-name> Displays the runtime information for the multihop BFD
sessions added to this node.
[srcaddr <srcaddr_value>] Displays the runtime information for the multihop BFD
sessions added with the specified source address.
[dstaddr <dstaddr_value>] Displays the runtime information for the multihop BFD
sessions added with the specified destination
address.
[state <state_info>] Displays the runtime information for the multihop BFD
sessions with the specified session state information.
The value can be up or down.
Table 21 Parameters for the show networking interface command
Example: Displaying the runtime information for BFD sessions added to CFPU-0
node
To display the runtime information the multihop BFD sessions added to the CFPU-0
node, enter the following command:
show networking bfd runtime node CFPU-0
The following output is displayed:
Vrf Source Address Destination Address State Diagnostic
0 10.0.1.1 10.0.1.2 Up No Diagnostic
122 Id:0900d80580862892 DN0974301

Confidential
Configuring IP Connection for Multicontroller RNC Configuring IP-based route
6 Configuring IP-based route

Purpose
User plane traffic scheduling, transport layer admission is managed with object class
called IP-based route (IPBR). The user plane source IP address selection related to
the IP-based route instance is managed via the IPRO object class.
The IP-based route concept comprises the following functions:
• User Plane IP address selection (RNC own address, source IP address)
• IP connection admission control
• Traffic shaping settings, including:
• QoS settings (DSCP mappings)
• Packet scheduler type (virtual or real scheduler)
• Queue management (tail drop or Internal Flow Control)
• UDP multiplexing enabling.
The IP-based route related IP address(es) are configured via the IPRO object class
(SCLI: ipro). The related IP address(es) form a set from where the RNC source IP
address is selected from.
The logical IP connection admission control function operates at IP layer. The commit-
ted bit rate attribute defines the higher limit that system can admit connections to the
system.
The IP-based route level shaping and scheduling provides real queue based and virtual
queue based scheduling options. For more information, see QoS configuration over-
view.
Before you start

The transport network planning has to be available to fill in a proper scheduling band-
width and committed bit rate values. This applies for the case that connection admission
control and IP layer scheduling is applied for the given connections.
Steps
1 Create IP-based route.

Use the add ipbr command to create an IPBR. Table 22 Mandatory parameters for
add ipbr command lists themandatory parameters of the add ipbr command.

ipbr-id This parameter specifies the IP-based route 1 - 4095
(IPBR) ID.
ipbr-name This parameter specifies the IPBR name The string
length is of?
maximum 15
characters.
committed-bandwidth This parameter specifies the IPBR committed 0 - 1000000
bandwidth limit in kbps.
Table 22 Mandatory parameters for add ipbr command
DN0974301 Id:0900d805808a73db 123

Confidential
Configuring IP-based route Configuring IP Connection for Multicontroller RNC

route-bandwidth This parameter specifies the IPBR route band- 0 - 1000000
width limit in kbps.
committed-dcn- This parameter specifies the IPBR committed 0 - 1000
bandwidth DCN bandwidth in kbps.
committed-sig- This parameter specifies the IPBR signaling 0 - 50000
bandwidth bandwidth in kbps.
Table 22 Mandatory parameters for add ipbr command (Cont.)
Table 23 Optional parameters for add ipbr command lists the optional parameters fpr
add ipbr command.

dspm-profile-id This parameter specifies the The allowed values are from 0 to
DSCP to PHB mapping profile ID. 10.
ifc-nrtdch This parameter specifiec the The allowed values are:
IPBR internal flow control (IFC)
• E-RED (When congestion
behavior for non-real time DCH
occurs the packets are
traffic.
dropped.)
• IFC (When congestion
occurs notifications are sent
to the sender.)
The default value is E-RED
ifc-nrthsdpa This parameter specifies the The allowed values are:
IPBR IFC behavior for non-real
• E-RED (When congestion
time HSDPA traffic.
occurs the packets are
dropped.)
• IFC (When congestion
occurs notifications are sent
to the sender.)
The default value is E-RED
phb-profile-id This parameter specifies the PHB The allowed values are from 0 to
profile ID for QoS. 10.
scheduler-type This parameter specifies the The allowed values are:
scheduler type.
• none
For more information on the real • virtualQueue
queue and virtual queue, see QoS
configuration overview.
• realQueue
The default value is none.
local-mux-port This parameter specifies the local The allowed value range is 49152
UDP port for IP multiplexing. - 65535.
Table 23 Optional parameters for add ipbr command
124 Id:0900d805808a73db DN0974301

Confidential

max-mux-packets This parameter specifies the The allowed value range is 5 - 30.
maximum number of packets in The default value is 30.
one multiplexed IP packet.
mux-dscp This parameter specifies the The allowed value range is 0 - 63.
DSCP value for IP multiplexing. The default value is 46.
mux-enable This parameter enables the IP
multiplexing. By default, the multi-
plexing function is disabled.
remote-mux-port This parameter specifies the The allowed value range is 49152
remote UDP port for the IP multi- - 65535.
plexing. The default value is 65535.
Table 23 Optional parameters for add ipbr command (Cont.)
Example:
1. Adding a IP-based route with name TEST-ID-1000
add ipbr ipbr-id 1000 ipbr-name TEST-ID-1000 route-bandwidth
1000000 committed-bandwidth 1000000 committed-sig-bandwidth 5000
committed-dcn-bandwidth 1000 dspm-profile-id 0 phb-profile-id 0
ifc-nrtdch IFC ifc-nrthsdpa E-RED scheduler-type virtualQueue
2. Enabling the UDP multiplexing of the IP packets
add ipbr ipbr-id 1 ipbr-name 1 mux-enable enable committed-
bandwidth 1000000 committed-sig-bandwidth 1 committed-dcn-
bandwidth 1 route-bandwidth 1000000
g Get a license before enabling the UDP multiplexing function.
2 Check the configured IP-based routes.

The configured IP-based routes can be listed with the show ipbr command.
Table 24 Parameters for show ipbr commandlists the parameters used with this
command.

ipbr-id Optional parameter. This parame- 1 - 4095
ter shows the IPBR information by
IPBR ID.
ipbr-name Optional parameter. This parame- The string length is of? maximum
ter shows the IPBR information by 15 characters.
name.
Table 24 Parameters for show ipbr command
Example:
1. Showing the IP-based route with ID1000:
show ipbr ipbr-id 1000
DN0974301 Id:0900d805808a73db 125

Confidential
2. Showing all IP-based routes:

show ipbr
3 Bind an IP address with the IP-based route.

Use the add ipro command to associate an IP address with the IP-based route.
Table 25 Parameters for add ipro command lists the parameters used with this
command.
Parameter Details Value range

owner Mandatory parameter. This
parameter specifies IPRO owner.
ip-address Mandatory parameter. This
parameter specifies IP address
for IPRO.
ipbr-id Mandatory parameter. This 1 - 4095
parameter specifies IPBR ID for
which IPRO is created.
iface Mandatory parameter. This
parameter specifies IP network
interface.
phb-set Optional parameter. This is the The allowed values can be ALL or a
PHB classes to be enabled for an group of consecutive classes in the
IPRO. PHB class set (EF, AF4, AF3, AF2,
AF1, BE). When set to ALL, all the six
classes are enabled. The default
value is ALL.
vrf-id Optional parameter. This parame- The allowed value range is 0 - 63.
ter specifies the ID of the virtual The default value is 0.
routing and forwarding (VRF)
instance.
Table 25 Parameters for add ipro command
g Follow the constraints when you configure the IP address and the IPBR binding:
• The IP-based route can only be bound to QNUP recovery group.
• Check that the IP address is a valid address attached to a loopback interface and to
the QNUP recovery group.
Example:
1. Associating the IP address 192.140.73.1 to the IP-based route whose ID is 1000:
add ipro iface lo ip-address 192.140.73.1 ipbr-id 1000 owner
/QNUP-0
2. Adding an association and specifying the VRF instance:
add ipro iface lo ip-address 192.140.73.1 ipbr-id 1000 owner
/QNUP-0 vrf-id 5
126 Id:0900d805808a73db DN0974301

Confidential
4 Change settings of IP address and IP-based route association.

Use the set ipro command to change settings of the IP address and IP-based route
association.
Table 26 Parameters for set ipro command lists the parameters used with this
command.
owner Mandatory parameter. This parameter specifies the IPRO owner.
ip-address Mandatory parameter. This parameter specifies the IP address for
IPRO.
ipbr-id Mandatory parameter. This parameter specifies the IPBR ID for which
IPRO is created.
The allowed value range is 1 - 4095.
iface Mandatory parameter. This parameter specifies the IP network inter-
face.
phb-set Optional Parameter. This is the PHB classes to be enabled for an
IPRO.
The allowed values can be ALL or a group of consecutive classes in
the PHB class set (EF, AF4, AF3, AF2, AF1, BE). When set to ALL, all
the six classes are enabled. The default value is ALL.
Table 26 Parameters for set ipro command
The following constraints need to be followed while changing IP address and IPBR
bingding:
• An IP-based route can only be bound to QNUP recovery group.
• Check that the IP address is a valid address attached to a loopback interface and to
the QNUP recovery group.
Example:
Changing the ID of the IP-based route associcated with IP 192.140.73.1 to 9
set ipro iface lo ipbr-id 9 ip-address 192.140.73.1 owner /QNUP
5 Show the configured associations between IP address and IP-based route.

Use the show ipro command to show an IP address associated with the IP-based
route.
Table 27 Parameters for show ipro command lists the parameters used with this
command.
owner Optional parameter. This parameter specifies the IPRO owner.
ip-address Optional parameter. This parameter specifies IP address for IPRO.
Table 27 Parameters for show ipro command
DN0974301 Id:0900d805808a73db 127

Confidential
ipbr-id Optional parameter. This parameter specifies IPBR ID for which IPRO
is created.
iface Optional parameter. This parameter specifies IP network interface.
vrf-id Optional parameter. This parameter specifies the ID of the virtual
routing and forwarding (VRF) instance.
Table 27 Parameters for show ipro command (Cont.)
Example:
Showing all IP address and IP-based route associations on recovery unit QNUP-0:
show ipro owner /QNUP-0
6 Delete the association between IP address and IP-based route.

Use the delete ipro command to delete an IP address associated with the IPBR.
Table 28 Parameters for delete ipro command lists the parameters used with this
command.
owner Mandatory parameter. This parameter specifies the IPRO owner, for
example, /EITPUPTRMRG.
ip-address Mandatory parameter. This parameter specifies the IP address for
IPRO.
ipbr-id Mandatory parameter. This parameter specifies the IPBR ID for which
IPRO is created. Range: 1-4095
iface Mandatory parameter. This parameter specifies the IP network inter-
face.
delete-mode Optional parameter. The allowed values are:
• normal: the operation would fail when there are transport bearers
based on it.
• force: the operation proceeds no matter whether there are trans-
port bearers based on it. Because the system will remove all the
transport bearers.
The default value is normal.
Table 28 Parameters for delete ipro command
Example:
Deleting an association:
delete ipro ipbr-id 1000 iface lo ip-address 192.140.73.1 owner
/QNUP-0
7 Delete the IP-based route.

Use the delete ipbr command to delete an IPBR.
128 Id:0900d805808a73db DN0974301

Confidential
Table 29 Parameters for delete ipbr command lists the parameters used with this
command.
Parameter Details
ipbr-id Mandatory parameter. This parameter deletes an IPBR by the IPBR
ID.
ipbr-name Optional parameter. This parameter deletes an IPBR by the IPBR
name.
Table 29 Parameters for delete ipbr command
Example:
Deleting the IP-based route with ID 1000 and name TEST-ID-1000:
delete ipbr ipbr-id 1000 ipbr-name TEST-ID-1000
Further information
For more instructions on usage of the ipbr and ipro SCLI commands, see Multicontroller
RNC SCLI Commands.
DN0974301 Id:0900d805808a73db 129

Confidential
QoS configuration Configuring IP Connection for Multicontroller RNC
7 QoS configuration
7.1 QoS configuration overview

Egress traffic scheduling in the Multicontroller RNC (mcRNC) is configured at two levels
in a hierarchical structure as shown in the figure below.
Figure 18 Traffic scheduling hierarchy

The highest level is IP-based route level. It performs traffic scheduling and shaping on
the IP layer. The second level is interface level which does traffic scheduling based on
the network interface, including Ethernet interface or Link Aggregation Group interface.
Each network interface aggregates the egress traffic forwarded to the given physical
interface.
For VLAN interface, the 3-bit Priority Code Point (PCP) field in the VLAN tag is used to
differentiate traffic in the external network. Usage of the PCP field for this purpose is
defined in IEEE 802.1p. The vlanmapping SCLI command can be used to define the
mapping between PCP values and the Differentiated Services Code Point (DSCP) for
outgoing traffic.
The following sub-chapters show how to configure QoS for the two levels respectively.
IP-based route level QoS
The IP-based route related IP address(es) are configured via the IPRO object class
(SCLI command: ipro). The related IP address(es) form a set from where the RNC
source IP address is selected from. The IP-based route is used for the user plane con-
nections IP address selection in each logical interface ( Iub, Iur, Iu-CS or Iu-PS) handling
the user plane bearers. The IP address configuration defines whether the IP address
selection operates in load sharing or non-load sharing mode.
The logical IP connection admission control function operates at IP layer. The commit-
ted bit rate attribute defines the higher limit that system can admit connections to the
system. The connection admission control operates in both load sharing and non-load
sharing configuration and it can be also disabled with setting the committed bit rate to 0.
130 Id:0900d805808abaec DN0974301

Confidential
Configuring IP Connection for Multicontroller RNC QoS configuration
The IP-based route level shaping and scheduling provides real-queue-based and
virtual-queue-based scheduling options. The real scheduling option contains real
queues where the packets are queued while the virtual scheduling is based on triggering
the Internal Flow Control (IFC) or packet drop events (E-RED based) for the data
according to the status seen by the virtual scheduling. The real-queue-based scheduling
is able to provide more accurate traffic shaping compared to rate limiting of the virtual
scheduler. The virtual scheduling can minimize the delays generated at the transport
layer with keeping the egress queues as short as possible.
The queue selection at the IP-based route level takes place via DSCP to PHB mapping
profile configured via IDSP object class. The DSCP profile is used to map certain DSCP
values to a PHB class.
The following table lists the scheduling methods that can be used per logical interface.
• VQ = Virtual queue based scheduling
• RQ = Real queue based scheduling
• IFC = Internal Flow Control, mechanism to limit traffic directly at user plane process-
ing. This method can be applied for the Iub only.
• E-RED = Enhanced random early detection based mechanism to trigger packet drop
events
• VQ+E-RED and RQ+E-RED schemes provide the AQM (Active Queue Manage-
ment) type of handling for the user plane traffic.
Combinations Iub Iur Iu-CS Iu-PS

None x x x x
VQ+IFC x
VQ+E-RED x x NA x
RQ+E-RED x x x x
Table 30 Scheduling methods used for logical interfaces
The following sub-chapters show how to configure a DSCP profile, PHB profile and
specify QoS parameters for an IP-based route.
Interface level QoS
In this level, traffic QoS can be done by the following configurable components:
• Classifier
• Filter
• Marker
• Dropper/policer
• Buffer manager
• Packet scheduler
In addition, a number of non-user configurable measures are addressed inside the
cluster to prioritize all internal as well as high priority external traffic.
The classifier, filter, and marker are implemented in Access Control List (ACL). The ACL
rules classify packets into packet flows based on the following selectors:
• Virtual Routing and Forwarding instance
• Any type of interface
DN0974301 Id:0900d805808abaec 131

Confidential
QoS configuration Configuring IP Connection for Multicontroller RNC
• IP stack netfilter hooks (Hooks are places in the IP stack to insert a filtering code. As
far as netfilter hooks are concerned, the following hooks are available and sup-
ported: packet reception (PREROUTING), forwarded (FORWARD), locally delivered
(INPUT), locally output (OUTPUT), and packet send (POSTROUTING) .)
• IP source or destination address (address/mask) or address family
• Layer 4 protocol
• UDP / TCP / SCTP source or destination port (or range of ports) (UDP / TCP / SCTP
source or destination port (or range of ports) (Port based ACL rules are able to
handle (for example drop) only the first fragment of the fragmented packet. Then re-
assembly buffers could potentially fill up the memory, in the case many additional
fragments are following the first fragment. Because of this fact use of port based
rules in PREROUTING and POSTROUTING chains is not recommended.)
An ACL rule can accept or drop the classified packet flow. The ACL can also perform
marking external as well as internal priority of packets belonging to a certain packet flow.
• External priority: 6-bit Differentiated Services Code Point (DSCP) value in the Type
of Service (TOS) field in the IP header, to be used in a QoS-aware external network.
• Internal priority: Marking the packet internal priority (PIP), a number between 0 and
7, to be associated with a certain queue at egress with the same priority.
As far as the DSCP encoding is concerned, the table below describes how the UMTS
QoS class or DiffServ per-hop behavior (PHB) type translates into the corresponding
DSCP value (equivalent to the corresponding TOS byte value where the two last bits are
excluded).
UMTS QoS class DiffServ PHB DSCP hex value DSCP binary value
Conversational Expedited Forwarding (EF) 0x2e 101110
Streaming Assured Forwarding (AF11) 0x0a 001010
Interactive, traffic Assured Forwarding (AF21) 0x12 010010
handling priority 1
Interactive, traffic Assured Forwarding (AF31) 0x1a 011010
handling priority 2
Interactive, traffic Assured Forwarding (AF41) 0x22 100010
handling priority 3
Background Best Effort (BE) 0x00 000000
Table 31 DSCP encoding for different UMTS QoS classes or DiffServ PHB types.
Dropper/policer, buffer manager, and packet scheduler are implemented as a set of

queues per egress port. Each queue buffers packets of a particular PIP. The scheduler
schedules (dequeue) packets from the queues based on the queue priority. In case of
egress link congestion, packets from high priority queues will have higher chance to be
scheduled with lowest delay. Length of the queue is managed by a queue management
algorithm. Tail Drop, as an absolute dropping algorithm, discards all packets exceeding
the configured threshold.
g The longer the queue is, the more system resources are used, and the more unneces-
sary packet flow latency is created.
132 Id:0900d805808abaec DN0974301

Confidential
7.2 Configuring QoS for IP-based route
7.2.1 Configuring DSCP to PHB mapping profile

Purpose
The DSCP to PHB mapping profiles is configured by using the structured command line
interface (SCLI) commands. This group of commands has a wide set of commands for
configuration, interrogation and deletion of the DSCP mapping profiles. A default DSCP
profile, which can only be interrogated, is also provided.
The 64 DSCP values (range from 0 to 63) are distributed to the six PHB classes (EF,
AF1, AF2, AF3, AF4 and BE). By default the distribution is as in the following table. If no
DSCP values are specified for a queue are specified during the configuration, the default
values are used. But if you specify a DSCP value that by default in another queue, the
value is removed from the original queue and reassigned to the new queue.
In addition, a default mapping profile with ID 0 exists in the system and it cannot be
modified or deleted.
PHB DSCP values

EF 46
AF1 10, 12, 14
AF2 18, 20, 22
AF3 26, 28, 30
AF4 34, 36, 38
BE 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 11, 13, 15, 16, 17, 19, 21,
23, 24, 25, 27, 29, 31, 32, 33, 35, 37, 39, 40, 41, 42, 43, 44,
45, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62,
63
Table 32 DSCP to PHB mapping
Steps
1 Create the DSCP profile.

Use the add qos-profile idsp command to add a DSCP mapping profile to the
system. The syntax of this command is as follows:
add qos-profile idsp <idsp-id> idsp-name <idsp-name> [af1-queue
<af1-queue>] [af2-queue <af2-queue>] [af3-queue <af3-queue>]
[af4-queue <af4-queue>] [be-queue <be-queue>] [ef-queue <ef-
queue>]
g To specify more than one DSCP values for a PHB class, separate them by comma
without any space.
Example
Create a DSCP profile with default mappings.
add qos-profile idsp idsp-id 1 idsp-name idsp-1
DN0974301 Id:0900d805808abaf3 133

Confidential
2 Modify the DSCP profile configuration.

Use the set qos-profile idsp command to update the existing DSCP mapping
profile. The syntax is as follows:
set qos-profile idsp idsp-id <idsp-id> [idsp-name <idsp-name>]
[af1-queue <af1-queue>] [af2-queue <af2-queue>] [af3-queue
<af3-queue>] [af4-queue <af4-queue>] [be-queue <be-queue>] [ef-
queue <ef-queue>]
Example
Assign the DSCP values 10, 12 and 43 to the AF1 queue.
set qos-profile idsp idsp-id 1 idsp-name idsp-1 af1-queue
10,12,43
The DSCP value 43 that is initially assigned to BE queue is reassigned to AF1 queue.
And the other default value for AF1 queue remain unchanged. The DSCP mapping
profile after executing this command is as follows:
profileID profileName phb dscpValue
1 idsp-1 BE 0 1 2 3 4 5 6 7 8 9
11 13 15 16 17 19 21 23 24 25
27 29 31 32 33 35 37 39 40 41
42 44 45 47 48 49 50 51 52 53
54 55 56 57 58 59 60 61 62 63
1 idsp-1 EF 46
1 idsp-1 AF1 10 12 14 43
1 idsp-1 AF2 18 20 22
1 idsp-1 AF3 26 28 30
1 idsp-1 AF4 34 36 38
3 Show the DSCP profile configuration.

Use the show qos-profile idsp to check the configured DSCP profile including
the default DSCP profile. If no parameter is given, all the profiles will be listed. The
syntax is as follows:
show qos-profile idsp [idsp-id <idsp-id>] [idsp-name <idsp-
name>]
Example
show qos-profile idsp idsp-id 1 idsp-name idsp-1
If you want to show all the DSCP profiles in the system, use * mark, as shown below:
show qos-profile idsp idsp-id * idsp-name *
4 Delete the DSCP profile configuration.

Use the delete qos-profile idsp command to delete the DSCP profile. If the
profile is in use, for example, the profile has been assigned to one or more IP-based
route, you need to delete the associated target before deleting the DSCP profile. The
syntax of this command is as follows:
delete qos-profile idsp idsp-id <idsp-id>
134 Id:0900d805808abaf3 DN0974301

Confidential
g The default DSCP profile with ID 0 cannot be deleted.
Example
delete qos-profile idsp idsp-id 1
Further information
For more information on the usage of the qos-profile SCLI command, see Multicontroller
RNC SCLI Commands.
User case: Configuring the DSCP profile

Configure a DSCP profile with certain PHB and DSCP mapping values.
1. List the current DSCP profiles.
show qos-profile idsp idsp-id * idsp-name *
2. Add a DSCP profile.
add qos-profile idsp idsp-id 1 idsp-name idsp-1
3. Configure a new DSCP profile by the given name and ID.
set qos-profile idsp idsp-id 1 idsp-name idsp-1 af1-queue
10,12,43
4. List the newly created DSCP profile by the name.
DN0974301 Id:0900d805808abaf3 135

Confidential
7.2.2 Configuring PHB profile

Purpose
To configure PHB profile using SCLI command. The PHB profile specifies algorithm
parameters related to each PHB class. Each profile contains six PHB classes: EF, AF1,
AF2, AF3, AF4 and BE. The five algorithm factors are:
• Queue weight (for WFQ algorithm)
• Minimum threshold (for WRED algorithm)
• Maximum threshold (for WRED algorithm)
• Maximum drop probability (for WRED algorithm)
• Exponential weight (for WRED algorithm)
g A default PHB profile with ID 0 is provided by the system. The default profile cannot be
modified or removed.
Steps
1 Create the PHB profile.

Use the add qos-profile iphb command to create the PHB profile. The syntax is
as follows:
add qos-profile iphb iphb-id <iphb-id> iphb-name <iphb-name>
[af1-queue <queWeight,minThresh,maxThresh,maxDrop,expWeight>]
[be-queue <queWeight,minThresh,maxThresh,maxDrop,expWeight>]
[ef-queue <queWeight,minThresh,maxThresh,maxDrop,expWeight>]
Example
Create a PHB profile and use default values for AF1, AF2, AF3, AF4, EF and BE.
add qos-profile iphb iphb-id 1 iphb-name iphb-1
2 Modify the PHB profile configuration.

Use the set qos-profile iphb command to update the PHB profile. The syntax is
as follows:
set qos-profile iphb iphb-id <iphb-id> [iphb-name <iphb-name>]
[be-queue <queWeight,minThresh,maxThresh,maxDrop,expWeight>]
[ef-queue <queWeight,minThresh,maxThresh,maxDrop,expWeight>]
Example
set qos-profile iphb iphb-id 1 iphb-name iphb-1 af1-queue
4,75,90,10,4
136 Id:0900d805808ac923 DN0974301

Confidential
3 Check the PHB profile configuration.

Use the show qos-profile iphb command to check the configured PHB profile. The
syntax is as follows:
show qos-profile iphb [iphb-id <iphb-id>] [iphb-name <iphb-
name>]
Example
show qos-profile iphb iphb-id 1 iphb-name iphb-1
If you want to see all the phb profiles in the system, use * mark.
show qos-profile iphb iphb-id * iphb-name *
4 Delete the PHB profile configuration.

Use the delete qos-profile iphb command to delete PHB profiles. If the profile
is used by other element such as an IP-based route, delete the target element before
deleting the PHB profile. The default PHB profile with ID 0 cannot be deleted. The syntax
of this command is as follows:
delete qos-profile iphb iphb-id <iphb-id>
Example
delete qos-profile iphb iphb-id 1
Further information
For more information on usage of the commands and parameters, see Multicontroller
RNC SCLI Commands.
User case: Configuring the PHB profile

Configure a PHB profile with the specific PHB queue parameters.
1. Show the current PHB profiles.
show qos-profile iphb iphb-id * iphb-name *
2. Create a new PHB profile by the given name and ID.
add qos-profile iphb iphb-id 2 iphb-name iphb-2
3. Update the PHB profile.
set qos-profile iphb iphb-id 2 iphb-name iphb-2 af3-queue
4,75,90,10,4
4. Check the newly created PHB profile by the name.
show qos-profile iphb-name iphb-2
DN0974301 Id:0900d805808ac923 137

Confidential
7.2.3 Configuring and showing IP-based route QoS parameters

Purpose
To configure IP-based route QoS parameters.
Steps
1 Show the IP-based route QoS parameters

Use the show qos-profile idsp and show qos-profile iphb command to
check the configured QoS profiles. Tables Parameters used with show qos-profile idsp
command and Parameters used with show qos-profile iphb command show the param-
eters used with these commands.
Parameter Details
idsp-name Optional parameter. Specifies DSCP
profile name.
idsp-id Optional parameter. Specifies DSCP
profile ID.
range: 0-10 or * (* indicates all profiles)
Table 33 Parameters used with show qos-profile idsp command
Parameter Details
iphb-name Optional parameter. Specifies PHB profile
name.
iphb-id Optional parameter. Specifies PHB profile
ID.
range: 0-10 or * (* indicates all profiles)
Table 34 Parameters used with show qos-profile iphb command
Example:
show qos-profile iphb iphb-id 1 iphb-name iphb-1
2 Configure the IP-based route QoS parameters

Use the set ipbr command to bind the DSCP and PHB profiles with the IPBR. Table
Parameters used with set ipbr command lists the parameters used to set the QoS for
the IP-based route with this command.
Parameter Details
ipbr-id specifies IPBR ID;
range: 1-4095
Table 35 Parameters used with set ipbr command
138 Id:0900d80580839a7f DN0974301

Confidential
Parameter Details
phb-profile-id specifies PHB profile ID for QoS;
range: 0-10; default: 0
dspm-profile-id specifies DSCP profile ID for QoS;
range: 0-10; default: 0
Table 35 Parameters used with set ipbr command (Cont.)
Example:
set ipbr ipbr-id 1 phb-profile-id 1 dspm-profile-id 1
Example: Setting the IPBR QoS profiles to default values
set ipbr ipbr-id 1 phb-profile-id 0 dspm-profile-id 0
Further information
For more information on the usage of the SCLI commands for QoS and IPBR, see Mul-
ticontroller RNC SCLI Commands.
DN0974301 Id:0900d80580839a7f 139

Confidential
7.3 Configuring QoS on interface level
7.3.1 Configuring ACL settings

Purpose
QoS-aware IP forwarding is implemented using the Access Control Lists (ACLs). The
ACL functionality includes accepting packets, dropping packets, and marking the priority
of packets belonging to a certain packet flow. In the ACL rule table lookup, the drop and
accept rules are terminating, whereas marking rules are non-terminating. Hence, by
using multiple rules, multiple marking actions can be performed with a flow.
The platform automatically sets an ACL bypass flag for loopback and untagged inter-
faces of all internal networks. This flag is hardcoded and cannot be overridden. As of
now it is not visible in the user interfaces. It protects the network element from accidental
misconfiguration, like operators adding a drop all rule for all interfaces. Any other rules
added to internal interfaces will be ignored.
Steps
1 Add a new ACL rule with associated QoS settings.

A new ACL rule with associated QoS settings is created with the add networking
aclrule command. The syntax of the command, including the mandatory parameters,
is:
add networking aclrule <owner> index <ACL-rule-index> chain
<chain-value> [dscp <dscp_value>] [input-iface <interface-
name>] [output-iface <interface-name>][vrf <vrf_instance_name>]
[srcaddr <source-IP-address>] [srcport <port-number>]
[srcportend <end-port-number>] [protocol <L4-protocol>][dstaddr
<IP-address>] [addr-family <IP-address-family>][dstport <port-
number>] [dstportend <port-number>] <ACL-rule-action>
g To prevent looping of packets between the nodes, the ACL rule must be configured for
dropping the packets in forward chain with VLAN (used for forwarding the external
packets between EIPUs) as input (input-iface) and output (output-iface) inter-
face.
Example: Adding a new ACL rule for VRF instance

Create a new ACL rule (accept packet flow) for the incoming local traffic for the default
VRF instance of the AS-0 node. The index of this ACL rule is 12000. Enter the following
command:
add networking aclrule /AS-0 chain input index 12000 vrf
default accept
Create a new ACL rule for the incoming local traffic for vrf1 instance of the AS-0 node.
The index of this ACL rule is 12000. Enter the following command:
add networking aclrule /AS-0 chain input index 12000 vrf vrf1
accept
Create a new ACL rule for the incoming local traffic for all VRF instances of the AS-0
node. The index of this ACL rule is 12000. Enter the following command:
add networking aclrule /AS-0 chain input index 12000 accept
140 Id:0900d805808aca81 DN0974301

Confidential
Example: Adding a new ACL rule

Create a new ACL rule for the outgoing local traffic from the ethrtm1_1 interface of the
AS-0 node, where the source IP address is 10.0.0.5. The index of this ACL rule is 100.
Enter the following command:
add networking aclrule /AS-0 index 100 output-iface ethrtm1_1
chain output srcaddr 10.0.0.5 accept
To accept traffic originated from local IP stack to all interfaces of default routing instance,
enter the following command:
add networking aclrule /AS-0 index 100 chain output vrf default
srcaddr 10.0.0.5 accept
Example: Adding a new ACL rule

Create a new ACL rule for the forwarded traffic, from the ethrtm1_1 interface of the AS-
0 node, where source IP address is 10.0.0.5. The index of this ACL rule is 100. Enter
the following command:
add networking aclrule /AS-0 index 100 input-iface ethrtm1_1
output-iface ethrtm1_2 chain forward srcaddr 10.0.0.5/24 accept
Example: Adding a new ACL rule with DSCP QoS setting

Create a new ACL rule to mark the DSCP field of all the forwarded traffic, from the
ethrtm1_1 interface of the AS-0 node IP packets. The source IP address must be in the
range of 10.0.0.0 to 10.0.0.255, with the desired QoS setting (EF for Expedited Forward-
ing). The index of this ACL rule is 101. The DSCP value for EF packet flow is 0x2e. Enter
add networking aclrule /AS-0 index 101 input-iface ethrtm1_1
chain prerouting srcaddr 10.0.0.0/24 dscp-mark 0x2e
Example: Adding a new ACL rule with internal priority QoS setting
Create a new ACL rule to mark the PIP of all locally originated packets outgoing from
the ethrtm1-1 interface of the AS-0 node, where the source IP address is 10.0.0.5. The
index of this ACL rule is 102. The internal priority value for this packet flow is 3. Enter
add networking aclrule /AS-0 index 102 output-iface ethrtm1_1
chain output srcaddr 10.0.0.5 pip-mark 3
2 Show existing ACL rules

To display a list of existing ACL rules, enter the following command:
show networking aclrule [owner <owner>] [index <ACL-rule-
index>] [iface <interface-name>][chain <chain-value>]
The show command displays all the rules affecting the flow, defined by the selection of
filters specified. That is, for owner, ruleid and chain parameters, the exact matching
rules are displayed. But for the iface parameter, the exact match and the rules created
without the interface is displayed.
Example: Displaying existing ACL rules

Display a list of existing ACL rules affecting packets coming to the local Linux stack of
the AS-0 node. Enter the following command:
DN0974301 Id:0900d805808aca81 141

Confidential
show networking aclrule owner /AS-0 chain input
3 Delete an ACL rule

To delete an existing ACL rule, enter the following command:
delete networking aclrule <owner> index <ACL-rule-index>
Further information
The parameters for ACL commands are listed in the following table.

<owner> This parameter specifies the
owner of the object. The value of
the node or the RG. This
parameter is mandatory.
index <ACL-rule- This parameter specifies the 100 to 31999
index> index (priority) value of the ACL
rule to be created, deleted or
displayed. This parameter is
mandatory.
chain <chain- This parameter specifies where The allowed values are:
value> the filtering rules are processed.
• input - altering packets that
This parameter is mandatory.
are coming to the local Linux
stack.
• output - altering packets
that are originated from the
local Linux stack.
• postrouting - altering
outgoing packets after
routing. To improve the
forwarding performance the
locally originated packets in
this chain must not be filtered.
The output chain must be
used instead.
• prerouting - altering
incoming packets before
routing. To improve the
forwarding performance the
locally terminated packets in
this chain must not be filtered.
The input chain must be
used instead.
• forward- altering packets
that are forwarded from the
local Linux stack.
dscp <dscp_value> 6-bit DSCP sub-field of IP header. 0x0 to 0x3F
Table 36 Parameters for ACL commands
142 Id:0900d805808aca81 DN0974301

Confidential

<ACL-rule- This parameter specifies the ACL The allowed values are:
action> rule action. This parameterr is
• accept - terminating action
mandatory.
to accept all packets of the
flow.
• drop - terminating action to
drop all packets of the flow.
• dscp-mark <DSCP> - non-
terminating action to modify
the DSCP value in the Type
of Service (TOS) field of the
IP packet using the <DSCP>
value.
• pip-mark - nonterminating
action to mark the packet
internal priority (PIP) using
the <PIP> value.
input- This parameter specifies the input
iface <iface_nam interface selector. Any type of
e> interface can be used. This
g Use this parameter only with

input, prerouting and
forward chains.
The input-iface
parameter cannot be used
with the vrf parameter.
output- This parameter specifies the
iface <iface_nam output interface selector. Any type
e> of interface can be used. This

output, postrouting and
forward chains.
The output-iface
parameter cannot be used
with the vrf parameter.
srcaddr <IP- This parameter specifies the
address> source IP address or range of IP
addresses selector written in
format <IP-address/mask>.
srcport <port- This parameter specifies the The allowed value range is 0 to
number> source port number selector. This 65535. If no value is specified,
parameter is optional. then the rule is applied to entire
range of ports.
TCP, UDP or SCTP
protocols.
Table 36 Parameters for ACL commands (Cont.)
DN0974301 Id:0900d805808aca81 143

Confidential

srcportend <end- This parameter specifies the last The allowed value range is 0 to
port-number> source port number. It is used to 65535. If no value is specified, the
define a range of port numbers rule is applied to the port specified
where the first port number in the in the srcport parameter.
range is srcport. This
g Use the parameter only with

TCP, UDP or SCTP protocols
and the srcport parameter.
vrf This parameter specifies the The allowed value range is 0 to
name of the virtual routing 599. The name of the default
instance. This parameter is routing instance is default and ID
optional. is 0. The default routing instance
cannot be removed.
g The vrf parameter cannot
be used with the iface
parameter.
protocol <L4- This parameter selects the layer 4 The allowed values are:
protocol> protocol to which the ACL rule is
applied. This parameter is
• tcp - the ACL rule applies to
TCP traffic only.
optional.
• udp - the ACL rule applies to
UDP traffic only.
• sctp - the ACL rule applies
to SCTP traffic only.
• protocol numbers - the
ACL rule applies to protocol
numbers (0 to 255) only.
If 0 or no value is specified, the
rule applies to all the protocols.
dstaddr <IP- This parameter specifies the
address> destination IP address or range of
IP addresses selector written in
format <IP-address/mask>.
addr-family This parameter specifies the IP The allowed values are:
<IP-address- address family. It defines an IP
• ipv4 - the ACL rule applies
family> address family to which the ACL
to all IPv4 flows.
rule without an address is applied.
This parameter is optional. • ipv6 - the ACL rule applies
to all IPv6 flows.
If no specific address family or
address is specified, the rule
applies to all IP flows.
dstport <port- This parameter specifies the The allowed value range is 0 to
number> destination port number selector. 65535. If no value is specified, the
This parameter is optional. rule is applied to entire range of
ports.
TCP, UDP or SCTP
protocols.
144 Id:0900d805808aca81 DN0974301

Confidential

dstportend <port- This parameter specifies the last 0 to 65535. If no value is
number> destination port numbe. It is used specified, then the rule is applied
to define a range of port numbers to the port specified in the
where the first port number in the dstport parameter.
range is dstport. This

TCP, UDP or SCTP protocols
and the dstport parameter.
<DSCP> This parameter specifies the 0x0 to 0x3F
DSCP value in the Type of
Service (TOS) field of the IP
packet header.
<PIP> This parameter specifies the 0 to 7
unique packet internal priority
(PIP) value that can be
associated with a queue in a
queue set or with a layer 2 VLAN
priority value.
DN0974301 Id:0900d805808aca81 145

Confidential
7.3.2 Configuring queue sets

Purpose
Queues are essential if QoS-aware scheduling is to be implemented at the egress
network interface. When a queue set is created in the system, it is automatically filled
with six queues with default settings. The number of six queues is hard-coded and
cannot be changed. The user can only modify settings of these queues or delete the
whole queue set. A default queue set, default, is created and assigned to every new
interfaces automatically. Default queue set cannot be modified.
There are two types of queues in a qset: strict priority (static) queues and weighted
round robin (WRR). Scheduling behavior is differrent for both types. The user cannot
change number of strict priority (static) queues.
After queue set is created, assign it to one or more interfaces to activate the egress QoS.
A queue set can be assigned to ethernet, link aggregation or bonding interface. It is
possible to modify settings of queues when the queue set is already assigned to an inter-
face. The changes are propagated in real time. When doing so, it is recommended to
specify all necessary changes to queues within one single command.
To get the full advantage of the egress QoS, it is recommended to configure an AS
node's egress queues with estimated aggregated size less then 6000 packets. Other-
wise it is not guaranteed that the packets drop according to their priority. For example,
If average ethernet frame size in your setup is 1 kB, then total aggregated queue size
per node should be less then 6 MB.
A queue set cannot be deleted, when it is assigned to an interface. A warning message
will be displayed.
Steps
1 Create a queue set.

To create a new queue set, enter the following command:
add networking qset <name-of-qset>
The queue set is created with default settings given in the following table:
Name Qspec Weight Queue length

Expedited Forwarding (EF) 5 SP 100k
Assured forwarding class 1 (AF1) 4 8 200k
Best Effort (BE) 0 8 500k
Table 37 Queue set with default values
g New queue set created and filled with eight queues with default settings. These settings
can be modified.
146 Id:0900d805808aca61 DN0974301

Confidential
2 Modify a queue in the existing queue set.

To modify a queue in existing queue set, enter the following command:
set networking qset <name-of-qset> {queue <queue-ID> [name
<name-of-queue>] [weight <queue-weight>] [length <tail-drop-
queue-length>] [dropper <logical-dropper>] }
Note that parameters in curly brackets can be repeated. In this case, they can be
repeated for each of 8 total queues. The only excpetions are queue6 and queue7,
which has fixed parameter weights, and it cannot be set up.
The parameters for this command are presented in the following table:

queue <queue-ID> This parameter specifies the unique queue ID 0 to 7
within a queue set. It is equivalent to the
packet internal priority (determined by the
pip-mark parameter) in the ACL. A queue
with higher <queue-ID> value has higher
preference for service. The ACL must mark
packets with the internal priority for the sched-
uler to be able to differentiate the packet
flows.
name <name-of- This parameter specifies the name of queue
queue> to be added.
weight <queue- This parameter specifies the queue weight. 1 to 8
weight> For weighted queue, the higher the weight
value, the higher the scheduling priority.
Weight of the static (strict priority) queues
(number 6 and 7) may not be changed.
dropper <logical- This parameter specifies the name of existing
dropper> dropper object. This parameter is optional.
length <tail-drop- This parameter specifies the size of a queue 1024 to 1048576
queue-length> in bytes. A tail dropper with specified value as
a threshold is created if it is not existing and
applied to the queue. This parameter is
optional.
Table 38 Parameters for set networking qset command
Example: Creating a queue set and modifying three queues in the queue set
1. Create a queue set by entering the following command:
add networking qset thisqset
2. Assign the created queue set to an interface:
set networking ether /CLA-0 iface ether1_1 outqset thisqset
3. Modify the queue 0 for Expedited Forwarding (EF) PHB packet traffic, the queue 1
for Assured Forwarding (AF1) PHB packet traffic and the queue 2 for Assured For-
warding (AF2) PHB packet traffic. Enter the following command:
set networking qset thisqset queue 0 name EF weight 1 length
10240 queue 1 name AF1 weight 4 length 10240 queue 2 name
AF2 weight 3 length 10240
DN0974301 Id:0900d805808aca61 147

Confidential
g Mark the packets with the corresponding internal ACL priority value, then a certain
<queue-ID> value has effect on the packet scheduling, .
3 Show existing queue sets.

To show existing queue sets (including the queues in each queue set), enter the follow-
ing command:
show networking qset [name <name-of-qset>]
4 Delete a queue set.

To delete an existing queue set, enter the following command:
delete networking qset name <name-of-qset>
In case the queue set is assigned to an interface, the command cannot be executed and
a warning message will be displayed.
Example
To deassign the queue set from an interface enter following command:
set networking ether /CLA-0 iface ether1_1 deloutqset
148 Id:0900d805808aca61 DN0974301

Confidential
7.3.3 Configuring VLAN priority mappings

Purpose
It is also possible to differentiate packet flows in layer 2 in a VLAN, using the 3-bit Priority
Code Point (PCP) field in the VLAN tag field defined in IEEE 802.1Q. This requires con-
figuring a VLAN priority map.
After VLAN mapping is created, it must be assigned to one or more interfaces. It can be
assigned to ethernet, link aggregation or bonding interface.
Before you start
g Use transactions to bundle multiple changes into one bigger change. Use configuration
locking feature to prevent other users from interfering with your configuration changes.
Steps
1 Create a VLAN priority map.

To create a new VLAN priority map, enter the following command:
add networking vlanmapping mapping <mapping-values> name <name-
of-map> type <dscp|pip>
The mandatory parameters for this command are presented in the table below:
name <name-of-map> This parameter specifies the name of the VLAN priority map to be
created.
type <dscp|pip> This parameter indicates whether the layer 3 priority values are
defined in terms of DSCP values or packet internal priority (PIP)
values.
mapping <mapping- This parameter specifies the mapping as [A:B], where A is either
values> the DSCP value or PIP priority value and B is the corresponding
VLAN priority value.
Up to eight mapping entries can be defined. At least one mapping
entry must be given.
Table 39 Parameters for add networking vlanmapping command
Example:
add networking vlanmapping name testMapping mapping 46:6
mapping 60:1 type dscp
2 Modify a VLAN priority map.

To modify an existing VLAN priority map, enter the following command:
set networking vlanmapping name <name-of-map> [type <dscp|pip>]
[mapping <mapping-values>]
Example:
set networking vlanmapping name testMapping mapping 29:4
mapping 60:1
DN0974301 Id:0900d805808aca73 149

Confidential
3 Show existing VLAN priority maps.

To show existing VLAN priority maps, enter the following command:
show networking vlanmapping [type <dscp|pip>] [name <name>]
4 Delete a VLAN priority map.

To delete an existing VLAN priority map, enter the following command:
delete networking vlanmapping name <name-of-map>
Example:
delete networking vlanmapping name testMapping
150 Id:0900d805808aca73 DN0974301

Confidential
Configuring IP Connection for Multicontroller RNC Troubleshooting
8 Troubleshooting
8.1 Connection to the application RG from remote host fails
Description
If you cannot reach an application RG from the remote host, the possible reasons
include:
• No valid route is configured from the host to the mcRNC.
• The network interface is in wrong state.
Symptoms
The remote host is unable to establish a connection to the application RG.
Recovery procedures
Check the IP-layer Communication
Steps
1 Check connection
Use the ping command from the remote workstation or node to check the connec-
tion.
1 Use the shell bash full command
2 Use the ping command to check the IP layer connection.
ping x.x.x.x
Expected outcome
----x.x.x.x PING Statistics----1 packets transmitted, 1 packets received, 0%
packet loss
2 Check IP routing table

Check IP routing table to find out whether the route you sent the packets is there.
Use the show routing node command. The following routes must exist:
• The route to the remote host.
• The route to the application RG.
Example
show routing node CFPU-0 route
S 0.0.0.0/0 via 10.68.157.129 eth0 cost 0 age 9688
C 10.68.157.128/26 is directly connected eth0
C 192.8/16 is directly connected ether1_1
3 Check the IP routing settings

1 If dynamic routes defined in the network element are configured
Then
DN0974301 Id:0900d805808aca8e 151

Confidential
Troubleshooting Configuring IP Connection for Multicontroller RNC
a) Check OSPF configuration.

show routing node <node_name> ospf config
b) Check OSPF interface configuration.
show routing node <node_name> ospf interface <interface
name>
c) Check OSPF routing errors.
show routing node <node_name> ospf errors
d) Check OSPF routing neighbors.
show routing node <node_name> ospf neighbors
For instructions on the configuring OSPF settings, see Configuring OSPF.
2 Check the static routes configurations
show routing node <node name> static-route config
For instructions on configuring static route, see Configuring static routes for
IPv4.
4 Check the connected network interface

Check the administrative and operational state of the connected network interface.
1 Check the network interface
show networking ether owner <owner_name> iface <iface_name>
Expected outcome
In the printout, the administrative state should be up and the IPv4 forwarding
should be yes.
Example
MTU : 1500
adminstate : up
IPv4 rpfilter : yes
IPv6 forwarding : no
IPv6 rpfilter : yes
proxy arp : no
2 Check the network interface running status
show networking interface runtime node <node_name> iface
<iface_name>
152 Id:0900d805808aca8e DN0974301

Confidential
8.2 mcRNC connectivity fails
Description
The redundant configuration requires that the two BCN boxes must be connected via
the SFP+ ports. The connectivity lost will cause call drop. The reasons for connectivity
lost can be:
1. Problem with the cables between BCNs.
2. Problem with the internal routing configuration of EIPUs.
Symptoms
The symptom is mcRNC connectivity lost. It can be that traffic path disconnects between
BCNs.
The fault may be either with the cabling or with the network configuration.
In case of faulty cabling, when an Ethernet link fails, the system sets the Ethernet inter-
face to "Not running" state and raises an alarm.
If no alarm is raised, the failure may be due to the network configuration.
Recovery procedures
Steps
1 Check if there is an alarm ETHERNET INTERFACE FAULTY

If an Ethernet link in the mcRNC unit fails, the system sets off an alarm. The alarm
description shows the reason for the failure and instructions on how to proceed.
Use the show alarm active command to show the active alarms.
If there is an alarm ETHERNET INTERFACE FAULTY (70146), which indicates a
problem in Ethernet interface, check the cabling.
2 Check the cabling

Check whether the cables are well connected.
Expected outcome
The cabling is correct. Check the routing configuration
Unexpected outcome
Cabling is incorrect. Correct the cabling.
3 Check the routing configuration of the EIPUs.
Before you start

The internal IP configuration is pre-defined for mcRNC. However, you can still check
the configuration. You can see the figure below about the redundant configuration
of mcRNC. If you find something wrong with the internal IP addresses or routes,
please contact NSN Technical Support group.
DN0974301 Id:0900d805808acace 153

Confidential
mcRNC module 2
EIPU-3
cfeigw
QNUP-2 GW 10.0.0.2/30 SFP16

10.0.0.6/30 SFP15
10.0.0.1/30
10.0.0.9/30
EIPU-1 10.0.0.17/30
cfeigw 10.0.0.25/30
QNUP-0 GW 10.0.0.10/30 SFP8
10.0.0.14/30 SFP7
mcRNC module 1 Transport Network
EIPU- 2
cfeigw
QNUP-0 GW 10.0.0.18/30 SFP16

10.0.0.22/30 SFP15
10.0.0.5/30
10.0.0.13/30
EIPU-0
10.0.0.21/30
cfeigw 10.0.0.29/30
QNUP-0 GW 10.0.0.26/30 SFP8
10.0.0.30/30 SFP7
mcRNC module 1
Figure 19 mcRNC redundant configuration
Steps
1 Check the application IP addresses used by mcRNC, such as the address for
Iu-PS, Iu-CS and Iur. Use the show ipro command.
show ipro
Expected outcome
==== IPRO LIST ================================================================
IPBR ID IP Address Owner Interface PHB set
EF AF4 AF3 AF2 AF1 BE
===============================================================================
1 10.69.59.200 /QNUP-0 lo on on on on on on
===============================================================================
For more instructions on associating the IP addresses to the certain IP-based
route, see Configuring IP based-route
2 Check the routing configuration on the node.
show routing node <node name> route
Expected outcome
Codes: C - Connected, S - Static, I - IGRP, R - RIP, B - BGP, O - OSPF
E - OSPF external, A - Aggregate, K - Kernel Remnant, H - Hidden
P - Suppressed
S 0.0.0.0/0 via 10.106.129.225 eth0 cost 0 age 13236
154 Id:0900d805808acace DN0974301

Confidential
C 10.106.129.192/26 is directly connected eth0

C 192.233/16 is directly connected ether1_1
DN0974301 Id:0900d805808acace 155

Confidential

Int CFG Ip MCRNC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Int CFG Ip MCRNC

Uploaded by

Copyright:

Available Formats

Parameter Operating

Documents, Issue 04, WCDMA

Integrate and Configure

Configuring IP Connection for

f Important Notice on Product Safety

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit

1 Overview of IP connection configuration . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Configuring IP interfaces . . . . . . . . . . . . . . . ....... .............. 22

3 Configuring Iu, Iub and Iur interfaces. . . . . . . . . . . . . ...... ....... . 34

4 Configuring IP for O&M connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

5.3.3.3 Redistribute direct routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

6 Configuring IP-based route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

7 QoS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Configuring Ethernet interface (2.1)

Configuring VLAN interfaces (2.2)

Configuring link aggregation groups (2.3)

Configuring Iu-PS interface (3.1)

Configuring IP-based route (6)

Configuring DSCP to PHB mapping profile (7.2.1)

IP termination and redundancy (1.3)

Configuring Ethernet interface (2.1)

Changes between issues 01C (2011-01-26, Nokia Siemens Networks WCDMA

Overview of IP configuration (1.2)

1 Overview of IP connection configuration

1.1 Multicontroller RNC logical interfaces

Iur Iu-BC Iu-PC

RNC CBC SAS

Table 1 Logical interfaces in the mcRNC System

1.2 Overview of IP configuration

1.2.1 Multicontroller RNC site solution

Cisco MGW Optional

Figure 2 mcRNC transport site solution

1.2.2 Link aggregation groups

1.2.3 VLAN interfaces

ferent types of traffic. L2 prioritization is provided by indicating the desired class of

1.2.4 IP interface hierarchy

Ethernet port 1 Ethernet port 2 Ethernet port n

Link Aggregation group (LAG)

Figure 3 IP interface hierarchy

1.2.5 External connectivity

• 16 x 1 Gigabit Ethernet (SFP plug-in bays)

• 10GBase-LR, LC connector, optical transmission using single-mode fiber cable

1.3 IP termination and redundancy

Figure 4 Functional Units in mcRNC

1.3.1 Transport solution related Functional Units

1.3.2 User Plane Recovery Group, QNUP

EIPU-0 EIPU-2 EIPU-1 EIPU-3

Standby Active /QNUP-1

Active Standby /QNUP-2

Standby Active /QNUP-3

Figure 5 QNUP Recovery Units allocation in 2 BCN modules setup

1.3.3 Iub Control Plane Recovery Group, QNIUB

EIPU-0 EIPU-2 EIPU-1 EIPU-3

Standby Active /QNIUB-1

Active Standby /QNIUB-2

Standby Active /QNIUB-3

Figure 6 QNIUB active Recovery Units allocation in 2 BCN modules setup

1.3.4 Iu/Iur Control Plane IP termination

EIPU-0 EIPU-2 EIPU-1 EIPU-3

M3UA M3UA M3UA M3UA

Multi-homed Multi-homed Multi-homed Multi-homed

Figure 7 Load sharing and IP addressing in 4 EIPU nodes setup