configuring_ip_connection_for_mcrnc.pdf

WCDMA RAN, Rel. RU40,Operating Documentation,Issue 08

Configuring IP Connection forMulticontroller RNC DN0974301Issue 02GApproval Date 2014-09-17

Nokia Networks

The information in this document applies solely to the hardware/software product (“Product”) specifiedherein, and only as specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may notbe used except for the purposes defined in the agreement between You and Nokia Solutions and Networks(“Agreement”) under which this document is distributed. No part of this document may be used, copied,reproduced, modified or transmitted in any form or means without the prior written permission of NokiaSolutions and Networks. If you have not entered into an Agreement applicable to the Product, or if thatAgreement has expired or has been terminated, You may not use this document in any manner and Youare obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and Youassume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part ofthe process of continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statementsconcerning the suitability, capacity, fitness for purpose or performance of the Product are given solely onan “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the rightto change any such information and statements without notice. Nokia Solutions and Networks has made allreasonable efforts to ensure that the content of this document is adequate and free of material errors andomissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correctionof such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Productwill be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TOANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THECONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BELIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OFERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not bedistributed or disclosed to any third parties without the prior written consent of Nokia Solutions andNetworks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this documentmay be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © 2014 Nokia Solutions and Networks. 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 thisproduct 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 andEnvironmental Information” part of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and follow the recommendationsfor power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services weoffer, please contact us at Nokia Solutions and Networks for any additional information.

Configuring IP Connection for Multicontroller RNC

2 DN0974301 Issue: 02G

Table of ContentsThis document has 301 pages

Summary of changes................................................................... 10

1 Overview of IP connection configuration...................................... 111.1 Multicontroller RNC logical interfaces...........................................111.2 Overview of IP configuration........................................................ 121.2.1 Differences between mcRNC and RNC2600 (IP transport)......... 221.3 IP termination and redundancy.................................................... 231.3.1 Transport solution related Functional Units..................................241.3.2 User Plane Recovery Group, QNUP............................................241.3.3 Iub Control Plane Recovery Group, QNIUB.................................251.3.4 Iu/Iur Control Plane IP termination............................................... 261.3.5 O&M Recovery Group, QNOMU.................................................. 271.3.6 Service Area Broadcast RG, QNCFCP........................................271.4 IP plan interface........................................................................... 271.5 Permissions for SCLI commands.................................................31 2 Configuring IP interfaces..............................................................332.1 Configuring Ethernet interface..................................................... 332.2 Configuring VLAN interfaces........................................................362.3 Configuring link aggregation groups............................................ 392.4 Configuring Ethernet switch port group........................................432.5 Configuring IP address for interfaces...........................................442.6 Configuring IP resources for Iub control plane.............................47 3 Configuring Iu, Iub and Iur interfaces........................................... 533.1 Introduction.................................................................................. 533.2 Configuring mcRNC OSPF SiSo, VRF, 10GE and shared EIPU. 543.2.1 Configuring mcRNC OSPF SiSo, VRF, 10GE and shared EIPU

instructions................................................................................... 653.3 Configuring mcRNC OSPF SiSo, VRF, 10GE, 1GE with LAG and

dedicated EIPU ........................................................................... 913.4 Configuring mcRNC OSPF SiSo, VRF, 1GE with LAG and shared

EIPU...........................................................................................1093.5 Configuring mcRNC VRRP/HSRP SiSo, VRF, 10GE and shared

EIPU...........................................................................................1313.5.1 Instructions.................................................................................1383.6 Configuring mcRNC VRRP/HSRP SiSo, VRF, 1GE with LAG and

shared EIPU...............................................................................1483.7 Configuring mcRNC VRRP/HSRP SiSo, VRF, 10GE, 1GE with

LAG and dedicated EIPU........................................................... 1663.8 Configuring Iu, Iur, and Iub interfaces with mcRNC Evolved Site

Solution...................................................................................... 1833.9 Configuring IP for Iu-BC interface (RNC - CBC)........................ 192


Issue: 02G DN0974301 3

4 Configuring IP for O&M connections..........................................194 5 Configuring routing.....................................................................2075.1 Configuring routing global parameters....................................... 2075.2 Configuring static routes for IPv4............................................... 2095.3 Configuring OSPF...................................................................... 2145.3.1 Configuring OSPFv2 overview................................................... 2145.3.2 Configuring OSPFv2.................................................................. 2155.3.3 Redistributing routes to OSPF protocol......................................2395.4 Configuring virtual routing.......................................................... 242 6 Configuring IP-based route........................................................ 245 7 Configuring QoS.........................................................................2547.1 QoS configuration overview....................................................... 2547.2 Configuring QoS for IP-based route...........................................2577.2.1 Configuring DSCP to PHB mapping profile................................2577.2.2 Configuring PHB profile..............................................................2607.2.3 Configuring and showing IP-based route QoS parameters .......2617.3 Configuring QoS on interface level............................................ 2637.3.1 Configuring ACL settings........................................................... 2637.3.2 Configuring queue sets.............................................................. 2697.3.3 Configuring VLAN priority mappings.......................................... 272 8 Configuring network monitoring................................................. 2748.1 BFD configuration...................................................................... 2748.1.1 BFD protocol.............................................................................. 2748.1.2 Configuring the BFD multihop session.......................................2748.1.3 Displaying the runtime information for the multihop BFD session....

2788.2 ICMP Configuration....................................................................2798.2.1 Internet control message protocol functionality..........................2798.2.2 Configuring internet control message protocol monitoring session..

2798.3 Link state detector configuration................................................ 2828.3.1 Link state detector functionality..................................................2828.3.2 Configuring a monitoring group/interface/nexthop for monitoring....

2848.4 Configuring TWAMP measurement............................................2888.4.1 Configuring TWAMP initiator...................................................... 2888.4.2 Configuring TWAMP reflector.....................................................291 9 Configuring NTP.........................................................................293 10 Configuring DNS........................................................................ 296 11 Troubleshooting..........................................................................29911.1 Connection to the application RG from remote host fails...........29911.2 mcRNC connectivity fails........................................................... 300


4 DN0974301 Issue: 02G

List of FiguresFigure 1 Logical interfaces of the Multicontroller RNC......................................11Figure 2 Cabling for OSPF 10GE connectivity................................................. 15Figure 3 Cabling for OSPF with 1GE ...............................................................15Figure 4 EIPU cabling principles.......................................................................17Figure 5 Cabling principles for 10GE connectivity............................................ 17Figure 6 User plane connections...................................................................... 18Figure 7 Iu and Iur control plane connections...................................................19Figure 8 Cabling principles for one EIPU pair ..................................................20Figure 9 IP addressing and routing configuration principles.............................20Figure 10 IP interface hierarchy..........................................................................21Figure 11 Functional Units in mcRNC................................................................ 24Figure 12 QNUP Recovery Units allocation in 2 BCN modules setup................25Figure 13 QNIUB active Recovery Units allocation in 2 BCN modules setup.... 26Figure 14 Load sharing and IP addressing in 4 EIPU nodes setup.................... 26Figure 15 mcRNC IP plan and SCLI relations.................................................... 28Figure 16 Network configuration for mcRNC OSPF SiSo with 10GE and VRF..56Figure 17 Iub configuration for mcRNC OSPF SiSo with 10GE and VRF.......... 57Figure 18 Iu/Iur User Plane configuration for mcRNC OSPF SiSo with 10GE and

VRF.................................................................................................... 58Figure 19 Iu/Iur Control Plane configuration for mcRNC OSPF SiSo with 10GE

and VRF............................................................................................. 59Figure 20 Network configuration for mcRNC OSPF SiSo with 10GE, LAG and

VRF.................................................................................................... 92Figure 21 Iub configuration for mcRNC OSPF SiSo with 10GE, LAG and VRF.93Figure 22 Iu/Iur User Plane configuration for mcRNC OSPF SiSo with 10GE,

LAG and VRF..................................................................................... 94Figure 23 Iu/Iur Control Plane configuration for mcRNC OSPF SiSo with 10GE,

LAG and VRF..................................................................................... 95Figure 24 Network configuration for mcRNC OSPF SiSo with LAG and VRF.. 111Figure 25 Iub configuration for mcRNC OSPF SiSo with LAG and VRF.......... 112Figure 26 Iu/Iur User Plane configuration for mcRNC OSPF SiSo with LAG and

VRF...................................................................................................113Figure 27 Iu/Iur Control Plane configuration for mcRNC OSPF SiSo with LAG

and VRF............................................................................................114Figure 28 Network configuration for mcRNC VRRP/HSRP SiSo with 10GE and

VRF.................................................................................................. 132Figure 29 Iub configuration for mcRNC VRRP/HSRP SiSo with 10GE and VRF...

133Figure 30 Iu/Iur User Plane configuration for mcRNC VRRP/HSRP SiSo with

10GE and VRF................................................................................. 134Figure 31 Iu/Iur Control Plane configuration for mcRNC VRRP/HSRP SiSo with

10GE and VRF................................................................................. 135


Issue: 02G DN0974301 5

Figure 32 Network configuration for mcRNC VRRP/HSRP SiSo with LAG andVRF.................................................................................................. 150

Figure 33 Iub configuration for mcRNC VRRP/HSRP SiSo with LAG and VRF.....151

Figure 34 Iu/Iur User Plane configuration for mcRNC VRRP/HSRP SiSo withLAG and VRF................................................................................... 152

Figure 35 Iu/Iur Control Plane configuration for mcRNC VRRP/HSRP SiSo withLAG and VRF................................................................................... 153

Figure 36 Network configuration for mcRNC VRRP/HSRP SiSo with 10GE, LAGand VRF........................................................................................... 168

Figure 37 Iub configuration for mcRNC VRRP/HSRP SiSo with 10GE,LAG andVRF.................................................................................................. 169

Figure 38 Iu/Iur User Plane configuration for mcRNC VRRP/HSRP SiSo with10GE, LAG and VRF........................................................................ 170

Figure 39 Iu/Iur Control Plane configuration for mcRNC VRRP/HSRP SiSo with10GE, LAG and VRF ....................................................................... 171

Figure 40 Network configuration for Iu, Iur, and Iub with evolved site solution.185Figure 41 IPv4 configuration for Iu-BC 1GE connectivity................................. 193Figure 42 O&M connectivity, solution 1............................................................ 195Figure 43 O&M connectivity, solution 1 with OSPF.......................................... 199Figure 44 O&M connectivity, solution 2............................................................ 204Figure 45 OSPF area scheme.......................................................................... 215Figure 46 Traffic scheduling hierarchy..............................................................254


6 DN0974301 Issue: 02G

List of TablesTable 1 Logical interfaces in the mcRNC System........................................... 11Table 2 BCN-B network interfaces.................................................................. 13Table 3 BCN-A network interfaces.................................................................. 13Table 4 Dedicated EIPU allocation..................................................................14Table 5 Differences between mcRNC and RNC2600 (IP transport)............... 22Table 6 mcRNC IP plan and SCLI relations.................................................... 29Table 7 SCLI commands and user permissions..............................................32Table 8 Parameters for Ethernet interface configuration.................................34Table 9 Parameters of VLAN interfaces.......................................................... 38Table 10 Parameters for link aggregation groups............................................. 41Table 11 Parameters for networking switch port-group.....................................44Table 12 Parameters for add networking address command...................44Table 13 Parameters for set networking address command...................45Table 14 Parameters for delete networking address command............ 46Table 15 Parameters of add networking iubsnt command......................47Table 16 Parameter of show networking iubsnt command......................50Table 17 Parameters of set networking iubsnt command......................50Table 18 Parameter of delete networking iubsnt command................. 52Table 19 Iub control and user plane IP addresses............................................ 60Table 20 Iu and Iur user plane IP addresses.....................................................61Table 21 Routing table for Iu-PS traffic............................................................. 73Table 22 Iub control and user plane IP addresses............................................ 96Table 23 Iu and Iur user plane IP addresses.....................................................96Table 24 Routing table for Iu-PS traffic........................................................... 103Table 25 Iub control and user plane IP addresses.......................................... 115Table 26 Iu and Iur user plane IP addresses...................................................116Table 27 Routing table for Iu-PS traffic........................................................... 124Table 28 Iu and Iur user plane IP addresses...................................................136Table 29 Routing table for Iu-PS traffic........................................................... 144Table 30 Iu and Iur user plane IP addresses...................................................154Table 31 Routing table for Iu-PS traffic........................................................... 162Table 32 Iu and Iur user plane IP addresses...................................................172Table 33 Routing table for Iu-PS traffic........................................................... 179Table 34 Iu-PS user plane...............................................................................190Table 35 Iu-PS control plane........................................................................... 190Table 36 Routing table for egress traffic..........................................................197Table 37 Routing table for ingress traffic.........................................................205Table 38 Routing table for egress traffic..........................................................205


Issue: 02G DN0974301 7

Table 39 Parameters for configuring static routes...........................................212Table 40 Commands for configuring OSPF areas...........................................216Table 41 Commands for configuring OSPF interfaces.................................... 220Table 42 The commands for configuring global OSPF parameters................ 223Table 43 Parameters for monitoring OSPF protocol....................................... 225Table 44 The OSPFv2 configuration parameters............................................ 227Table 45 Commands for configuring OSPF areas...........................................228Table 46 Commands for configuring OSPF interfaces.................................... 231Table 47 The commands for configuring global OSPF parameters................ 235Table 48 Parameters for monitoring OSPF protocol....................................... 236Table 49 Parameters for redistributing routes between protocols................... 239Table 50 Parameters for virtual routing........................................................... 243Table 51 Parameters for networking ipbr commands......................................250Table 52 Parameters for networking ipro commands......................................252Table 53 Scheduling methods used for logical interfaces............................... 255Table 54 DSCP encoding for different UMTS QoS classes or DiffServ PHB

types................................................................................................. 256Table 55 DSCP to PHB mapping.................................................................... 257Table 56 Parameters for show networking qos-profile idsp command............262Table 57 Parameters for show networking qos-profile iphb command............262Table 58 Parameters for set networking ipbr command..................................262Table 59 Parameters for ACL commands....................................................... 265Table 60 Queue set with default values.......................................................... 270Table 61 Parameters for set networking qset command......................270Table 62 Parameters for add networking vlanmapping command........272Table 63 Parameters for add networking monitoring bfd session command...276Table 64 Parameters for the show networking monitoring bfd

runtime command..........................................................................278Table 65 Parameters for the networking monitoring icmp commands......

281Table 66 Parameters for the networking link-state-detector

commands........................................................................................ 287Table 67 Parameters for networking monitoring twamp sender commands... 290Table 68 Parameters for networking monitoring twamp reflector commands. 292Table 69 Parameters for NTP configuration.................................................... 294Table 70 Parameters for DNS configuration....................................................297


8 DN0974301 Issue: 02G

Summary of changesChanges between document issues are cumulative. Therefore, the latest documentissue contains all changes made to previous issues.

See Guide to WCDMA RAN Operating Documentation.

Changes between issues 02F (2014-07-01) and 02G (2014-09-19,RU40)A step has been added to the OSPF site solution for link break handling.

Changes between issues 02E (2014-05-23) and 02F (2014-07-01,RU40)Configuring IP for Iu-BC interface (RNC - CBC) has been updated for clarity.

Changes between issues 02D (2014-03-21, RU40) and 02E (2014-05-23, RU40)O&M connectivity, solution 1 with OSPF and BFD in Configuring IP for O&M connectionshas been updated to clarify subnet mask for CFPU as illustrated in the figure.


Issue: 02G DN0974301 9

guide_to_wcdma_ran_operating_documentation.pdf

1 Overview of IP connection configuration

1.1 Multicontroller RNC logical interfaces3GPP defines a set of logical interfaces which the Multicontroller RNC (mcRNC) networkelement supports as shown in Figure1 Logical interfaces of the Multicontroller RNC.

Figure 1 Logical interfaces of the Multicontroller RNC

Table 1: Logical interfaces in the mcRNC System presents description of the logicalinterfaces in the mcRNC network.

Table 1 Logical interfaces in the mcRNC System

Interface

Description

Iu-CS Logical interface between the radio network controller (RNC) and circuitswitched 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.

Summary of changes Configuring IP Connection for Multicontroller RNC

10 DN0974301 Issue: 02G

Table 1 Logical interfaces in the mcRNC System (Cont.)

Interface

Description

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.

1.2 Overview of IP configurationIntroduction

Within the mcRNC product the network connectivity and transport layer processingcapacity is aligned with the control plane and user plane processing capacity. Thenetwork interfaces and network processing units (EIPU) are located throughout the BCNmodules of the mcRNC. Capacity upgrades add the needed extra connectivity andnetwork processing capability along with the control and user plane processing power.

Both 1GE and 10GE Ethernet interfaces are supported with the mcRNC BCN-Bhardware. Full transport redundancy is provided for the failure cases with locating theservices to EIPU pairs where the EIPUs are located to two different BCN modules. AllEIPU nodes process traffic at normal conditions while still reserving the capacity to takeover the responsibilities of the pair EIPU node in case of a failure.

For the mcRNC the networking processing capacity, connectivity and redundancy isprovided as per EIPU pair basis. Groups of two EIPUs (EIPU n and EIPU n+1) indifferent BCNs form a pair. With VRRP/HSRP site solution and OSPF site solution with10GE connectivity each EIPU is connected to one site router/switch. EIPUs with evennumber n connect to the first site router and EIPUs with odd number n+1 connect to thesecond site router. This type of a cabling setup is applicable for both 1GE and 10GEconnectivity. With mcRNC Evolved site solution and with OSPF 1GE site solution allEIPU nodes are connected to both site routers/switches supporting the 1GE connectivity.

O&M functions are provided with the Central Functions Processing Unit (CFPU) locatedto two first BCN modules. The CFPUs have directly connected external LAN interfacesfor the BTS O&M, OMS, NetAct and O&M network connectivity in general.

Multicontroller RNC physical connectivity

Multicontroller RNC physical network interfaces are dependent on the BCN hardwarevariant. The BCN-B hardware provides the option to apply both 1GE and 10GE networkconnectivity as listed in Table 2: BCN-B network interfaces. The table lists the connectorswithin one BCN module.

Configuring IP Connection for Multicontroller RNC Overview of IP connection configuration

Issue: 02G DN0974301 11

Table 2 BCN-B network interfaces

Interfaces

Printed label

SCLI/IP plan

10 * 1GE (EIPU) SFP 13 - SFP 22 sfp13 - sfp22

2 * 10GE (EIPU) SFP+ 11, SFP+ 12 sfp11, sfp12

1 * 1GE (CFPU*) LAN 1 eth0

* CFPU nodes are located in two first BCN modules. LAN interface is directly connectedto CFPU node.

g The following port combinations are supported for the external connectivity: SFP+11and SFP13 - SFP22 or SFP+11 and SFP+12. Both 10GE interfaces and 1GE interfacesare not supported simultaneously.

The trace port is reserved for the mirroring of the external connectivity ports (SFP11 -SFP22). SFP20 is reserved for L3 Data Collector(Megamon)/Emil connectivity.Additionally SFP21 can be used for the Megamon monitoring connectivity as well.Furthermore, SFP21 and SFP22 can be configured in shared mode for Magemon/Emil.

With 10GE full connectivity two EIPU nodes of a single BCN module can be connectedto the same external 10GE port of the BCN module. This is to provide an optimizedconnectivity where 1*10GE interface per BCN module is configured permanently andallows to take full advantage of the processing power of all EIPU nodes.

With BCN-A hardware (mcRNC2.0) the external connectivity provided within one BCNmodule is listed in Table 3: BCN-A network interfaces. BCN-A HW supports 1GE networkconnectivity.

Table 3 BCN-A network interfaces

Interfaces

printed label

SCLI/IP plan

16 * 1GE (EIPU) SFP 7 - SFP 22 sfp7 - sfp22

1 * 1GE (CFPU*) LAN 1 eth0

Shared and dedicated EIPU setup

mcRNC supports shared and dedicated EIPU setups that can be applied depending onthe site router and network configuration. The main principles:

Shared EIPU scheme:

• One pair of site routers aggregating all Iub, Iur and Iu traffic towards the mcRNC• BTSs, neighbor RNCs, CN elements are connected to all EIPU nodes• Still allows also to configure a certain BTS to certain EIPU node where BTS

generated load is manually distributed over the EIPU nodes

Overview of IP connection configuration Configuring IP Connection for Multicontroller RNC

12 DN0974301 Issue: 02G

Dedicated EIPU scheme:

• Certain EIPU pairs reserved for BTS connections and certain EIPU pairs forCN/neighbor RNC

• EIPU division has to be planned based on the capacity step relatedrecommendations

Table 4: Dedicated EIPU allocation presents the dedicated EIPU configuration options.

Table 4 Dedicated EIPU allocation

BCN

EIPU

Iu-CSUserPlane

Iu-PSUserPlane

IuControlPlane

Iur UserPlane

IurControlPlane

Iub

Capacity Step

BCN 1&2 EIPU 0&1 X X X X X CS1

(2*BCN)

CS3

(4*BCN)EIPU 2&3 - - X - X X

BCN 3&4 EIPU 4&5 X X X X X -

EIPU 6&7 - - X - X X

Within the shared EIPU setup the Iu, Iur and Iub traffic is allocated to all EIPU nodeswithin the mcRNC. With dedicated EIPU setup selected EIPU nodes terminate the Iubtraffic while other nodes terminate the Iu and Iur traffic. With both dedicated and sharedEIPU setup the Iu/Iur control plane is distributed over all EIPU nodes in order to achievebest possible SIGTRAN load sharing with all setups.

Multicontroller RNC site solutions

The site solutions for mcRNC provide support options with different main characteristics:L3 static routes, VRRP/HSRP and dynamic routing based configurations. The mcRNCsupports 1GE and 10GE physical connectivity where both can be also used at the sametime. Different site solution options are covered within chapters mcRNC Evolved SiteSolution-mcRNC OSPF Site Solution and detailed configuration examples are includedin chapters 3 and 4 representing the related SCLI and IP plan commands and attributes.

mcRNC OSPF Site Solution

The mcRNC L3 OSPF Site Solution is L3 type of a setup where dynamic routing isapplied to distribute the IP addresses to site routers and further to network. The solutionis available at mcRNC3.0 release for both 1GE and 10GE interfaces externalconnectivity.

With the OSPF site solution the VRF (Virtual Routing and Forwarding) feature is requiredin order to keep the dynamic routing and the Iu/Iur control plane (SCTP Multi-Homing)static routing separated. The Iu/Iur control plane should be always located to VRF1 - 4.

Main characteristics of the solution:

• L3 type of site solution with dynamic routing


Issue: 02G DN0974301 13

• OSPF with BFD (Single Hop) or OSPF Fast Hello applied for fast reaction to linkfailures

• Supports 1GE and 10GE interfaces• Required optional features

– RAN1510 license for RAN2550 OSPF Enhancements in mcRNC (BFD SingleHop with OSPF)

• Required standard features

– RAN2257 Virtual Routing and Forwarding feature for logical routing functionsseparation within EIPU nodes

Figure 2 Cabling for OSPF 10GE connectivity

Figure 3 Cabling for OSPF with 1GE

The Iu/Iur user plane and the Iub control and user plane are terminated on loopbackaddresses of the EIPUs. The IP addresses are configured with Recovery Group as theowner and the IP address is located within the same node that is running the activeRecovery Unit of the RG.

With OSPF Site Solution the connectivity is organized in a way that each EIPU nodes isconnected to both site routers. These principles are followed with both 1GE and 10GEconnectivity. Recovery Group (QNUP, QNIUB) protection switchover is triggered by thefollowing events:

• SW failure (mcRNC redundancy mechanisms)

The Iu and Iur control plane (SIGTRAN) connections apply the network interface IPaddresses within the mcRNC backplane side. This makes it possible to distribute SCTPassociations freely within the EIPU nodes even if the given EIPU does not providephysical connectivity towards the corresponding peer NE.


14 DN0974301 Issue: 02G

• User plane, Iub Control plane

– IP address: Loopback interface, IP address follows the service– Routing: OSPF– Redundancy: Recovery Group, OSPF

• Iu/Iur Control plane

– IP address for EIPU having external connectivity to destination network (gatewayEIPU)

• External Network interface address, fixed IP address

– IP address for EIPU not having external connectivity to destination network

• Internal Network interface address within the sctp1 and sctp2 interface in thebackplane (VRF1-4), fixed IP address

– Routing: Static routes– Redundancy: SCTP Multi-Homing– The configuration is the same with OSPF and VRRP/HSRP site solutions

The reference configuration for the site solution option is provided within mcRNC sitesolution based on Juniper with OSPF using 1GE and 10GE connectivity and mcRNC sitesolution based on Juniper with OSPF using 10 Gigabit Ethernet connectivity.

mcRNC VRRP/HSRP Site Solution

mcRNC VRRP/HSRP site solution is L2 type of site solution with L2 domain spanningover the EIPUs and site routers/switches but not over the RNC site. The VRRP/HSRP isapplied for site router redundancy making the planning principles compatible with thecurrent main IPA-RNC site solution.

With the VRRP/HSRP site solution the VRF (Virtual Routing and Forwarding) feature isrequired in order to keep the static route configuration as simple as possible and to allowdefault route based routing for Iu/Iur user plane and Iub traffic. The Iu/Iur control planeshould be always located to VRF1 - 4.

The solution is available from mcRNC3.0 release onwards and supports both 1GE and10GE interfaces.


• Site solution based on Ethernet switchport configuration in the site routers• Site router redundancy is managed with VRRP or HSRP protocols• One VLAN spans over the EIPUs and site routers/switches (not further to network)• Provides planning principles compatibility with the current IPA-RNC VRRP/HSRP site

solution• Supports 1GE and 10GE interfaces• Required standard features

– RAN2257 Virtual Routing and Forwarding feature for logical routing functionsseparation within EIPU

The cabling principles with 1GE and Ethernet Link Aggregation for one EIPU pair aredepicted in the Figure 4: EIPU cabling principles.


Issue: 02G DN0974301 15

Figure 4 EIPU cabling principles

The cabling principles for 10GE optimized connectivity is presented in Figure 5: Cablingprinciples for 10GE connectivity.

Figure 5 Cabling principles for 10GE connectivity

The Iu/Iur user plane and the Iub control and user plane traffic is terminated at IP layeron the network interface addresses of the EIPUs. The IP addresses are configured withinthe network interface with Recovery Group as the owner of the address. The IP addressis located within the same node that is running the active Recovery Unit of the RG. For aVLAN interface with terminating only user plane traffic the fixed IP address is not neededto be configured. Still for each EIPU at least one fixed IP address should exist within oneof the VLAN interfaces. This is needed in order to always provide IP access to a specificnode for connectivity testing and trouble shooting for example.

The interface or link failure is detected with the Link State Detector functionality. LinkState Detector is bound to RG and configured to monitor network interface(s) state. Incase of link or interface failure the RG switchover will be triggered and the service alongwith the related IP address moves to new EIPU. Recovery Group (QNUP, QNIUB)protection switchover is triggered by the following events:


16 DN0974301 Issue: 02G

• SW failure (mcRNC redundancy mechanisms)• Link/Interface failure (Link State Detector)

The Iu and Iur control plane (SIGTRAN) connections apply the network interface IPaddresses within the mcRNC backplane side. This makes it possible to distribute SCTPassociations freely within the EIPU nodes even if the given EIPU does not providephysical connectivity towards the corresponding peer NE. The IP addressing and routingconfiguration principles are listed below and depicted in Figure 6: User planeconnections.


– IP address: Network interface, IP address follows the service– Routing: Static routes– Redundancy: Recovery Group, Link State Detector, VRRP/HSRP


– IP address for EIPU having external connectivity to destination network (gatewayEIPU)

• External Network interface address, fixed IP address

– IP address for EIPU not having external connectivity to destination network

• Internal Network interface address within the sctp1 and sctp2 interface in thebackplane (VRF1-4), fixed IP address

– Routing: Static routes– Redundancy: SCTP Multi-Homing– The configuration is the same with VRRP/HSRP and OSPF site solutions

Figure 6 User plane connections


Issue: 02G DN0974301 17

Figure 7 Iu and Iur control plane connections

mcRNC Evolved Site Solution

mcRNC Evolved site solution is L3 type of solution where L2 switching takes place withinthe site router but not in between the site routers. The site solution is available atmcRNC3.0 release and it supports only 1GE interfaces. It is not recommended to usethis site solution when the operator plans to use 10GE interfaces in the future. Then thesite soultion must be changed. The transport redundancy is based on configuringprimary and redundant static routes in both mcRNC and site routers. The BFD SingleHop is applied for L3 level next hop supervision.

Since the site solution contains L2 switching within the site router/switch the VLANs mayspan in between the site router and several EIPU nodes allowing logical trafficseparation with minimum amount of VLANs.


• Site solution based on Ethernet switchport configuration in the site routers• One VLAN spans over the EIPUs and a single site router/switch (user plane)• Redundancy is based on the static routes configuration (L3 type of a site solution)• BFD Single-Hop with static routes applied for next-hop supervision• Supports only 1GE interfaces.• Required optional features

– RAN1510 OSPF license for RAN2440 Fast IP re-routing (BFD Single Hop withstatic routes)

• Recommended standard features

– RAN2257 Virtual Routing and Forwarding feature for logical routing functionsseparation within EIPU nodes


18 DN0974301 Issue: 02G

The cabling principles for one EIPU pair are depicted in the Figure 8: Cabling principlesfor one EIPU pair.

Figure 8 Cabling principles for one EIPU pair

The user plane and Iub control plane addresses are configured to EIPU loopbackinterface. The Iu and Iur control plane (SIGTRAN) connections apply the networkinterface IP addresses directly. The IP addressing and routing configuration principlesare listed below and depicted in Figure 9: IP addressing and routing configurationprinciples.


– IP address: Loopback interface, IP address follows the service– Routing: Static routes– Redundancy: Redundant static routes– Related RG: QNUP, QNIUB


– IP address: Network interface, fixed IP address– Routing: Static routes– Redundancy: SCTP Multi-Homing

Figure 9 IP addressing and routing configuration principles


Issue: 02G DN0974301 19

Link aggregation groups

Link aggregation groups (LAG) provide increased bandwidth and high reliability bycombining several 1GE interfaces into one logical link. The mcRNC Ethernet ports canbe aggregated 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 portsof the same mcRNC module can be aggregated within a one LAG. A maximum of eightLAGs can be supported for the mcRNC within the same module. LAG is impossible if10GE interface is in use in the same EIPU.

For more information on Ethernet link aggregation in the mcRNC, see RAN2256:Ethernet link aggregation for mcRNC in WCDMA RAN, Rel. RU30, Feature Descriptions.

VLAN interfaces

The mcRNC supports VLANs as a mechanism to enable traffic separation and quality ofservice at layer 2. Traffic separation is achieved by using different VLAN IDs for differenttypes of traffic. L2 prioritization is provided by indicating the desired class of service inthe priority field in VLAN header.

For more information about VLANs, see the Virtual Local Area Networks (VLAN) chapterin WCDMA RAN IP Transport.

IP interface hierarchy

Figure 10: IP interface hierarchy shows the IP interface configuration hierarchy.

Figure 10 IP interface hierarchy

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

External connectivity

The mcRNC module provides the following physical interfaces for network connectivity:


20 DN0974301 Issue: 02G

BCN-A:

• 16 x 1 Gigabit Ethernet (SFP plug-in bays) per BCN module• 1 x 1 Gigabit Ethernet for element management/DCN (available in the first two BCN

modules only; SFP plug-in bays)

BCN-B:

• 2 x 10 Gigabit Ethernet (SFP+ plug-in bays) per BCN module• 10 x 1 Gigabit Ethernet (SFP plug-in bays) per BCN module• 1 x 1 Gigabit Ethernet for element management/DCN (available in the first two BCN

modules only; SFP plug-in bays)

1GE and 10GE ports are used for the UTRAN traffic handling (for user, control andmanagement plane). Any interface can be configured and used as an Iu, Iub, or Iurinterface.

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)• 10GBase-LR, LC connector, optical transmission using single-mode fiber cable

(SMF)• 10GBase-SR, LC connector, optical transmission using multi-mode fiber cable (MMF)

1.2.1 Differences between mcRNC and RNC2600 (IP transport)

Table 5 Differences between mcRNC and RNC2600 (IP transport)

RNC2600 (NPGEP) Multicontroller RNC

Active / standby interface protection All interfaces active, enabling comprehensiveconnectivity monitoring and load sharing

Network, application, and unit protection arecombined in single protection mechanism(NPGEP, 2N redundancy)

Application and unit protection by FlexiPlatformHA services, network protection based on sitesolution (L3 routing, VRRP)

End-to-end layer 2 network support mcRNC requires L3 site routers, L2 end-to-end(L2 Iub) solution support can be considered inlater releases based on the customer demand.L3 site routers are preferred from the NSNview.

Logical interfaces (Iu/Iur/Iub) can be placed onseparate physical interfaces (so called"Dedicated NPGE" configuration)

Logical interfaces (Iu/Iur/Iub) can be placed onseparate physical interfaces (So called"Dedicated EIPU" configuration)

RNC2600 Site Solutions

• HSRP/VRRP Site Solution• OSPF supported

mcRNC Site Solutions

• Static route + BFD Single-Hop (EvolvedSiSo, RU30)

• OSPF Site Solution (RU30)• HSRP/VRRP Site Solution (RU40)

Routing instances separation only availablewith using separate dedicated NPGE(P) units

VRF feature supported for separating therouting instances


Issue: 02G DN0974301 21

Table 5 Differences between mcRNC and RNC2600 (IP transport) (Cont.)

RNC2600 (NPGEP) Multicontroller RNC

• Can be used for simplified Static routesetup

• Needed with OSPF based routing (Iu/Iurcontrol plane and SCTP Multi-Homing withstatic routes)

IP Based Route scheduling available for Iub(IFC, Internal Flow Control)

IP Based Route scheduling available for allinterfaces (Virtual or Real Queues, InternalFlow Control or E-RED)

Spanning tree required for ESA protection No spanning tree needed

Physical interfaces support: 1 Gigabit Ethernet Physical interfaces support: 1 and 10 GigabitEthernet

DHCP server / DHCP relay services supported DHCP server / DHCP relay services notsupported

Source address based routing supported VRF feature supported for similar use cases

Signalling configuration via plan interfacesupported

Signalling plan interface not supported in RU40

Ethernet link OAM supported (RAN2254) Ethernet Link OAM not supported

1.3 IP termination and redundancyThe mcRNC high availability is implemented by using a Recovery Group (RG) concept.A Recovery Group instance is associated with certain Functional Units. The servicerelated to the RG is running in the active Recovery Unit (RU). Figure 11: Functional Unitsin mcRNC shows the relationship within the mcRNC containing Functional Units. TheRecovery Units, where the actual software is running and the service is terminated, arethe target for the High Availability actions. In case of the software or hardware failure, theactive RU is switched over to another one and the IP layer service termination is movedto the new unit which is running the active RU.


22 DN0974301 Issue: 02G

Figure 11 Functional Units in mcRNC

mcRNC

RecoveryGroup�(RG)

FunctionalUnit

RecoveryUnit�(RU)

Process(es)

The Recovery Group and the active Recovery Unit allocation is statically configuredwithin 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 HardwareDescription.

1.3.2 User Plane Recovery Group, QNUP

The QNUP Recovery Groups terminate the user plane services of all mcRNC logicalinterfaces.

The QNUP Recovery Groups have the following functions and characteristics:

• it is bound to EIPU nodes• it is the owner of the IP addresses for User Plane services• terminates the User Plane connections from any logical interface from several

neighboring nodes


Issue: 02G DN0974301 23

• 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 followingscheme in order to provide a good basic load distribution. Figure 12: QNUP RecoveryUnits allocation in 2 BCN modules setup shows the 2 BCN module configuration with 4EIPU nodes, 4 QNUP Recovery Group instances and their active RU allocation. EachEIPU holds an active RU in normal operation. The same allocation principles arefollowed in all mcRNC capacity steps. The IP address tied to a certain RG is active onlyin the node where the active RU is running.

Figure 12 QNUP Recovery Units allocation in 2 BCN modules setup

BCN-1

EIPU-0 EIPU-2

BCN-2

EIPU-1 EIPU-3

/QNUP-0Active Standby

Active Standby

ActiveStandby

ActiveStandby

/QNUP-1

/QNUP-2

/QNUP-3

For the available capacity steps and EIPU group allocation within BCN modules refer toMulticontroller RNC Product Description. The mcRNC configuration may contain 0 - 2EIPU units per BCN module. The external connectivity and EIPU related RecoveryGroup redundancy concept is designed to work at EIPU pair basis.

1.3.3 Iub Control Plane Recovery Group, QNIUB

The QNIUB Recovery Groups terminate the Iub control plane services at the IP/SCTPlayer.

The QNIUB Recovery Groups have the following functions and characteristics:

• it is bound to EIPU nodes• it is the owner of the IP addresses for Iub Control Plane services• 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. Theprovided redundancy mechanism is transparent to a BTS. In order to provide an optimalbasic load sharing, the active RUs of the QNIUB RGs are allocated with the followingscheme. Figure 13: QNIUB active Recovery Units allocation in 2 BCN modules setupshows 2 BCN module configuration with 4 EIPU nodes, 4 QNIUB Recovery Groupinstances, and their active RU allocation. The same allocation principle is followed in allmcRNC capacity steps.


24 DN0974301 Issue: 02G

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

BCN-1

EIPU-0 EIPU-2

BCN-2

EIPU-1 EIPU-3

/QNIUB-0Active Standby

Active Standby

ActiveStandby

ActiveStandby

/ -1QNIUB

/ -2QNIUB

/ -3QNIUB

1.3.4 Iu/Iur Control Plane IP termination

The Iu/Iur control plane traffic termination and the SIGTRAN stack implementation islocated in EIPU nodes. Depending on the external connectivity scheme, the controlplane traffic is terminated in external interface or backplane interface IP addresses,configured to these EIPU nodes. The transport network redundancy is provided by SCTPmultihoming, the service level redundancy and load sharing is handled at theM3UA/SCCP layer.

The SCCP layer contains a hot active/standby redundancy scheme in order to providefull RANAP/RNSAP resilience. The SCCP layer redundancy scheme is implemented bythe QNIU Recovery Group, which is automatically maintained by the system. The QNIURG does not contain the IP addresses and does not require any configuration by theuser. Figure 14: Load sharing and IP addressing in 4 EIPU nodes setup shows theoverall load sharing and IP addressing scheme in case of 4 EIPU nodes setup.

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

BCN-1

EIPU-0 EIPU-2

BCN-2

EIPU-1 EIPU-3

SCCP SCCP

SCCP SCCP

SCCP

SCCP SCCP

SCCP SCCP

M3UA

SCTP

IP A1 IP A2

M3UA

SCTP

IP B1 IP B2

M3UA

SCTP

IP C1 IP C2

M3UA

SCTP

IP D1 IP D2

Multi-homed

SCTP

Association

#1

Multi-homed

SCTP

Association

#2

Multi-homed

SCTP

Association

#3

Multi-homed

SCTP

Association

#4


Issue: 02G DN0974301 25

The SCTP associations towards single peer MSS or SGSN should be divided over 2, 4or 8 EIPU nodes for optimal redundancy and load balancing. The SCTP associationstowards different peer elements should be divided over all EIPU nodes in order toprovide full overall SIGTRAN traffic load sharing within the mcRNC.

1.3.5 O&M Recovery Group, QNOMU

The VRF (Virtual Routing and Forwarding) feature is required in order to keep the Iu/Iurcontrol plane static route configuration separated from the user plane and Iub trafficrouting. The Iu/Iur control plane should be always located to VRF1 - 4. The IP addressesof one SCTP Multi-Homed association end point have to be located to the same VRFinstance.

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• contains the IP address(es) between RNC and NetAct site• has a hot active/standby redundancy scheme for end user connection resilience

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, whichis 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• has a hot active/standby redundancy scheme for end user connection resilience

1.4 IP plan interfaceThe mcRNC IP plan interface to NetAct uses similar object model and structure as theStuctured Command Line Interface (SCLI). The IP plan interface object model ispresented in Figure 15: mcRNC IP plan and SCLI relations. The IP plan objectdescription and the related SCLI command categories are listed in Table 6: mcRNC IPplan and SCLI relations. The mcRNC IP plan interface supports plan download,activation and upload operations.


26 DN0974301 Issue: 02G

g The IP plan interface operations saves the current active configuration to disk. Thisensures that the defined configuration implemented via the IP plan interface will bepermanent and kept in use even after the next system restart. Note that all otherconfiguration changes performed via the SCLI commands will be done to the currentactive configuration. Taking a snapshot takes some time during which the configurationdirectory (LDAP) is locked. As a result, it is not possible to make configuration changeswith SCLI commands or provide a new IP plan.

For more information on the snapshot operation, please refer to SCLI manual in theReference section.

Figure 15 mcRNC IP plan and SCLI relations


Issue: 02G DN0974301 27

Table 6 mcRNC IP plan and SCLI relations

IP plan Object Class

Description

SCLI

ACL Access Control List. The ACLfunctionality includes acceptingpackets, dropping packets, andmarking the priority of packetsbelonging to a certain packet flow.

networking acl rule

ADDR IP address. Dedicated addresses areassigned directly to the service (nodeor recovery group) that needs externalconnectivity.

networking ... address

ADR4GW Static route, gateway address routing ... static-route

AGPRO4 Aggregate route. routing ... aggregate

AGRT4 Aggregate route. The aggregate routescan be configured in order to reducethe number of routes advertisedbetween the routers.

routing ... aggregate

BFDS BFD (Multi-Hop). BidirectionalForwarding Detection (BFD) is anetwork protocol used to detect faultsbetween two forwarding enginesconnected by a link.

networking ... monitoring bfd

DNS Domain Name System networking-service dns

ETHER Ethernet Interface. Physical interfaceconfiguration.

networking ether

EXAG4 Export Aggregate Routes. The existingaggregate route (AGRT4) to beexported.

routing ... export

EXDI4 Export Interface. The existing interfaceto be exported.

routing ... export

EXSR4 Export Static Route. The existing staticroute (SRT4) to be exported.

routing ... export

FLTR4 Route Filter. Define routes to befiltered.

routing

GLPRM Routing instance global parameters.The global parameters for static routeand OSPF.

set routing ... max-path-splits,router-id

ICMPS Internet control message protocolobject class

networking ... monitoring icmp


28 DN0974301 Issue: 02G

Table 6 mcRNC IP plan and SCLI relations (Cont.)


Description

SCLI

IDSP DSCP to PHB mapping. The DSCP toPHB mapping is applied for the IPBased Route scheduling queueselection.

networking qos-profile idsp

IP Generic IP parent object for NetAct

IPBR IP Based Route. IP Based Route objectclass.

networking ipbr

IPHB IP Based Route Queue. IP BasedRoute queue settings.

networking qos-profile iphb

IPRO IP Based Route IP address allocation networking ipro

IUBSNT Iub SCTP parameters networking iubsnt

LAGGR Ethernet link aggregation. Multiplephysical links between two endpointscan be aggregated into a linkaggregation group to increase linkbandwidth and improve the availabilityin case of a single physical link failure.

networking ... linkaggr

LNSIF Link state detection interfaces objectclass

networking ... link-state-detector interface

LNSMG Link state detection monitoring group networking ... link-state-detector monitoring group

LNSNH Links state detection nexthop objectclass

networking ... link-state-detector next-hop

MD5 OSPF authentication routing ... ospf

NTP Network Time Protocol networking-service ntp

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


Issue: 02G DN0974301 29

Table 6 mcRNC IP plan and SCLI relations (Cont.)


Description

SCLI

OWNER Parent Node or Recovery Group networking ... owner

QSET Scheduling and queue managementparameter set.

networking ... qset

QSPEC Scheduling and queue managementparameters for the interface egressQoS.

networking ... qset

RNG4 Address range. The address rangesare used to reduce the number ofrouting entries that a given area emitsinto the backbone and thus all areas.

routing ... ospf

ROUTE4 Aggregate route. routing ... aggregate

RTINST Routing instance within a node networking or routing ...instance

SRT4 Static route. The static routes can beconfigured by using SRT4 andADR4GW object classes.

routing ... static-route

TWAMPR Two-Way Active Measurement Protocolreflector object class

networking monitoring twampreflector

TWAMPS Two-Way Active Measurement Protocolsender object class

networking monitoring twampsender

VLAN VLAN interface networking ... vlan

VLANPM VLAN priority mapping networking vlanmapping

VRF Virtual Routing and Forwarding networking ... vrf

For more information, see WCDMA RAN Configuration Management and IPConfiguration Plan Interface Parameters for Multicontroller RNC Excel.

1.5 Permissions for SCLI commandsThe permissions represent the ability to invoke a particular command through the SCLI.

You need to have correct permissions for executing SCLI commands.

SCLI commands and their related user permissions are provided in Table 7: SCLIcommands and user permissions.


30 DN0974301 Issue: 02G

Table 7 SCLI commands and user permissions

Command

Permission

add fsNetworkingManage

set fsNetworkingManage

show fsNetworkingManage, fsNetworkingView

delete fsNetworkingManage


Issue: 02G DN0974301 31

2 Configuring IP interfaces

2.1 Configuring Ethernet interfacePurpose

To configure Ethernet interfaces on the mcRNC.

Basic configuration options for external connectivity are:

• directly connected SFP ports• 10GE shared port where two EIPU nodes within the same BCN share the port

Before you start

Create the VRF instance with the instruction in Chapter Configuring virtual routing if youwant to apply the VRF instance to the network interface.

When you want to create an Ethernet interface and attach it to a port group, create theport group with instruction in Chapter Configuring Ethernet switch port group first.

1 Show the current Ethernet interface configuration.Use the show networking ether command to show the current settings of theEthernet 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>]

g The instance parameter is used to specify a particular routing instance. The defaultvalue is default. If no instance value is set, the IP configuration of all routing instancesare displayed.

g The parameter enclosed by brackets are optional. For those parameters with a limitednumber of values, the values are listed in the angle brackets.

2 Add an Ethernet interface.Create an Ethernet interface. The interface can be attached to a physical port (SFPor SFP+ plug-in bays) or a port group. 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>]

g The mcRNC specific default physical interface egress queue set is pre-configured in thesystem with name rncdefault. Assign this profile to the physical interfaces to enableproper default egress scheduling weights configuration.


32 DN0974301 Issue: 02G

Example

Add Ethernet interface ethsfp7 to port sfp7.

add networking instance iucs ether /EIPU-0 iface ethsfp7 portsfp7

Create a port group protgroup1 for port sfp21 on BCN box 1. Then create theEthernet interface for the port group.

add networking switch port-group name portgroup1 port LMP-1-1-1:sfp21

add networking ether /EIPU-0 iface ethge1 port portgroup1

3 Change settings of the Ethernet interface.Use the set networking ether command to change the current Ethernetinterface 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>] [newvrf <name>] [outqset<name>]|[deloutqset] [proxy-arp <yes|no>] [rate-limit <rate-limit>]

g The VRF instance (parameter: newvrf) cannot be changed if an IP address isassigned to the Ethernet interface.

4 Check the Ethernet interface configuration.Use the show networking ether command to verify if the configuration issuccessful.

5 Delete the Ethernet interface configuration.Delete the settings associated with an Ethernet interface so that the default valuesare 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.

Table 8 Parameters for Ethernet interface configuration

Parameter

Description

Value Range

<owner> This parameter specifies the name of theobject that manages the interface. Thisobject can be a node, a recovery group,a recovery unit or a process. This is amandatory parameter.

Configuring IP Connection for Multicontroller RNC Configuring IP interfaces

Issue: 02G DN0974301 33

Table 8 Parameters for Ethernet interface configuration (Cont.)

Parameter

Description

Value Range

admin <up|down> This parameter specifies the state of theinterface.

The allowed values areup and down. The defaultvalue is up.

outqset <name> This parameter specifies the name of theegress queue set to be used with thisinterface. This parameter is optional.

g The egress queue set should becreated beforehand.

For more information on queue set, seeConfiguring queue sets.

deloutqset This parameter removes the egressqueue set attached to the interface. Thisparameter is optional.

g The egress queue set should becreated beforehand.

iface <name> This parameter specifies the name of theinterface where the changes areapplicable. This is a mandatoryparameter.

instance The networking configuration is appliedto or displayed from the virtual routinginstance specified by this parameter. Ifno instance is specified, theconfiguration is applied to or displayedfrom the default routing instance.

ipv4forwarding<yes|no>

This parameter specifies if the packetforwarding is allowed for IPv4 traffic.This parameter is optional.

The allowed values areyes and no. The defaultvalue is yes.

ipv4rpfilter<yes|no>

This parameter specifies if the reversepath filter is enabled for IPv4 traffic. Thisparameter is optional.

The allowed values areyes and no. The defaultvalue is no.

mtu <mtu-size> This parameter specifies the maximumtransmission unit (MTU) value of theinterface.

The default value is 1500bytes.

newvrf <name> This parameter specifies the name of thenew virtual routing instance.

Configuring IP interfaces Configuring IP Connection for Multicontroller RNC

34 DN0974301 Issue: 02G

Table 8 Parameters for Ethernet interface configuration (Cont.)

Parameter

Description

Value Range

port <port-name> This parameter specifies the name of theport or port group, where the Ethernetinterface is added.

The allowed port namesdepend on the hardwaretype. For BCN-A, theallowed values are sfp7 tosfp22. For BCN-B, theallowed values are sfp11to sfp22.

The names of the portgroups created by theuser can also be givenhere.

g The port name isthe same as theport numberavailable on thefront panel of theBCN hardware.

proxy-arp<yes|no>

This parameter specifies if the proxyARP is present or not. It is applicableonly for IPv4 addresses. This parameteris optional.

The allowed values areyes and no. The defaultvalue is no.

rate-limit<rate_limit>

This parameter specifies the rate limitvalue of the physical interface.

-

2.2 Configuring VLAN interfacesPurpose

To configure the VLAN interfaces on the Multicontroller RNC module.

1 Create VLAN interfaces.Use add networking vlan command to add a new VLAN interface. The syntaxof 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>]

g The mcRNC specific default DSCP to VLAN PCP (802.1Q, VLAN priority bit) is pre-configured in the system with the name "vlandscptopcp". Assign this profile to the VLANinterfaces to enable proper DSCP to VLAN priority bit marking. Operator specific DSCPto VLAN priority bit mapping profiles can be also assigned in case the system defaultmapping profile is not convenient.


Issue: 02G DN0974301 35

Example:

Attach the VLAN identifier 120 to the interface_1 interface in the EIPU-0 node byentering the command below. The corresponding logical interface using this VLAN isnamed as vlan_1.

add networking vlan /EIPU-0 realiface interface_1 vid 120 vlaniface vlan_1

2 Show the current settings of VLAN interfaces.Display the current settings of the VLAN interfaces by using the show networkingvlan 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>]Expected outcomeThe printout is, for example: vlan_1 (VLAN interface) VRF name(ID) : default (0) owner : /EIPU-0 MTU : 1500 admin state : up IPv4 forwarding : yes IPv4 rp-filter : no IPv6 forwarding : no IPv6 rp-filter : yes proxy ARP : no VLAN ID : 120 real interface : interface_1

3 Change the settings of the VLAN interfaces.Use the set networking vlan command to change the current settings of theVLAN interfaces. The syntax of the command is as follows:set networking [instance <name>] vlan <owner> iface <name> [admin <up|down>] [mapping <name>]|[delmapping] [mtu <mtu-size>] [newvrf <vrf-name>] [ipv4forwarding <yes|no>] [ipv4rpfilter <yes|no>] [proxy- arp <yes|no>]

g The VRF instance (parameter: newvrf) cannot be changed if an IP address isassigned to the VLAN interface.

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.


36 DN0974301 Issue: 02G

Table 9 Parameters of VLAN interfaces

Parameter

Description

Value Range

<owner> This parameter specifies the name ofthe node or recovery group that actsas the owner of this VLAN interface.This parameter is mandatory.

admin <up|down> This parameter specifies the state ofthe VLAN interface. This parameteris optional.

The allowed values are upand down. The default valueis up.

delmapping This parameter disables VLANpriority mapping. It is optional.

instance The networking configuration isapplied to the virtual routing instancespecified by this parameter. If noinstance is specified, theconfiguration is applied to the defaultrouting instance. This parameter isoptional.


This parameter specifies if the packetforwarding is allowed for IPv4 traffic.This parameter is optional.

The allowed values are yesand no. The default value isyes.


This parameter specifies if thereverse path filter is enabled for IPv4traffic. This parameter is optional.

The allowed values are yesand no. Default is no.

mapping <name> This parameter specifies the name ofthe VLAN priority mapping. Thisparameter is optional.

mtu <mtu-size> This parameter specifies the MTUvalue of the VLAN interface. Thisparameter is optional.

g The MTU value of the VLANinterface cannot exceed theMTU of the underlying realinterface.


newvrf This parameter specifies the virtualrouting instance name. Thisparameter is optional.

proxy-arp <yes|no> This parameter turns on and off theProxyARP feature on the interface.This parameter is optional.

The allowed values are yesand no. Default is no.


Issue: 02G DN0974301 37

Table 9 Parameters of VLAN interfaces (Cont.)

Parameter

Description

Value Range

realiface <name> This parameter specifies theinterface where the VLAN isassigned to. The interface can beeither a physical interface (forexample eth0), a logical interface(for example inteface_1), a linkaggregation group (for exampleethgrp0), or another VLANinterface. This parameter ismandatory.

vid <id> This parameter specifies the VLANidentifier. This parameter ismandatory.

The allowed range is from 1to 4094.

vlaniface <name> This parameter specifies the name ofthe VLAN interface to be created.This parameter is mandatory.

The string length is ofmaximum 15 characters.

2.3 Configuring link aggregation groupsPurpose

To configure the link aggregation groups on the Multicontroller RNC module.

Before you start

If the virtual routing is used, check that the routing instances are created and interfacesare set to the correct routing instances. For more information, see routingdocumentation. In the commands presented in this chapter, the routing instances aredefined with the optional instance <name> parameter that is attached in thecommands. In the command syntax the parameter is placed right after the networkingparameter.

g Note

LAG configuration is controlled by License. For more information see theRAN2256: Ethernet Link Aggregation for mcRNC feature license.

1 Add a link aggregation.Use the add networking linkaggr command to add a new link aggregationgroup. The syntax of the command is as follows:add networking [instance <name>] linkaggr <owner> iface <name> slave <iface> [slave <iface>...] [admin <up|down>] [algorithm <name>] [ipv4forwarding <yes|no>] [ipv4rpfilter <yes|no>] [lacp <yes|no>] [mtu <mtu-size>] [outqset <name>] [proxy-arp <yes|no>] [rate-limit <rate-limit>]


38 DN0974301 Issue: 02G

g Only Ethernet interfaces configured on SFP ports from the same BCN can be added toan link aggregation group.

g The mcRNC specific default LAG interface egress queue set is preconfigured in thesystem with name rncdefault. Assign this profile to the LAG interfaces to enableproper default egress scheduling weights configuration.

Example:

Create a link aggregation group with the name ethgrp0 of the physical interfacesethsfp10 and ethsfp11 by entering the command below. The link aggregationgroup is managed by the EIPU-0 node and it uses five-tuple algorithm for physicalinterface selection.

add networking linkaggr /EIPU-0 iface ethgrp0 algorithm five-tuple slave ethsfp10 slave ethsfp11 lacp yes

To create a link aggregation group named ethgrp0 of the physical interfacesethsfp10 and ethsfp11 with the default rate limit, enter the following command:

add networking linkaggr /EIPU-0 iface ethgrp0 slave ethsfp10 slave ethsfp11

2 Show the current settings of link aggregation groups.The current settings of the physical interfaces can be shown by using the shownetworking linkaggr command. The syntax of the command is as follows:show networking linkaggr [admin <up|down>] [algorithm <name>] [iface <name>] [ipv4forwarding <yes|no>] [ipv4rpfilter <yes|no>] [lacp <yes|no>] [mtu <mtu-size>] [owner <name>] [proxy-arp <yes|no>] [slave <iface>]

3 Change the settings of the link aggregation group.Use the set networking linkaggr command to change the current settings ofthe link aggregation group. The syntax of the command is as follows:set networking [instance <name>] linkaggr <owner> iface <name> [add- slave <iface_name>] [delslave <iface_name>] [admin <up|down>] [algorithm <name>] [ipv4forwarding <yes|no>] [ipv4rpfilter <yes|no>] [lacp <yes|no>] [mtu <mtu-size>] [newvrf <name>] [proxy-arp <yes|no>] [outqset <name>]|[deloutqset] [rate-limit <rate_limit>]

g The VRF instance (parameter: newvrf) cannot be changed if an IP address isassigned to the Ethernet interface.

Example

To add the slave interface ethsfp10 to the LAG interface, enter the followingcommand:

set networking linkaggr /EIPU-0 iface ethgrp0 add-slaveethsfp10

To delete the slave interface ethsfp10 from the LAG interface, enter the followingcommand:


Issue: 02G DN0974301 39

set networking linkaggr /EIPU-0 iface ethgrp0 del-slaveethsfp10

4 Delete link aggregation.Use the delete networking linkaggr command to delete a new linkaggregation group. The syntax of the command is as follows:delete networking [instance <name>] linkaggr <owner> iface <name>

Example:

Delete a link aggregation group named ethgrp0 of the physical interfacesethsfp10 and ethsfp11 by using the following command.

delete networking linkaggr /EIPU-0 iface ethgrp0

Further information

The parameters related to link aggregation groups are provided in the following table.

Table 10 Parameters for link aggregation groups

Parameter

Description

Value Range

<owner> The managed object that acts as the owner ofthis link aggregation group, for example,/CFPU-0.

admin<up|down>

The state of the link aggregation group. Thisparameter is optional.

The allowed values areup and down. Default isup.

algorithm<name>

The algorithm that is used for selecting theslave interface for the traffic. In mcRNC, onlyfive-tuple algorithm is supported.

deloutqset This parameter restores the default qset to theinterface. This parameter is optional.

iface <name> The name of the link aggregation group to becreated, for example, ethgrp0.

The maximum length ofthe name is 15characters.

instance<name>

The networking configuration is applied to thevirtual routing instance specified by thisparameter. If no instance is specified, theconfiguration is applied to the default routinginstance.


This parameter enables or disables the packetforwarding for IPv4 traffic. This parameter isoptional.

The allowed values areyes and no. Default isyes.


40 DN0974301 Issue: 02G

Table 10 Parameters for link aggregation groups (Cont.)

Parameter

Description

Value Range


This parameter enables or disables thereverse path filter for IPv4 traffic. Thisparameter is optional.

The allowed values areyes and no. Default isno.

lacp This parameter specifies the link aggregationcontrol protocol. You can enable or disable thelacp.

The allowed values areyes and no. Default isno.

mtu <mtu-size> This parameter specifies the MTU value of thelink aggregation group. This parameter isoptional.

g The MTU of the link aggregation groupcannot exceed the MTU of anyunderlying physical interfaces.


newvrf This parameter specifies the virtual routinginstance name. It’s used when changing thevrf property of the link aggregation group. Thisparameter is optional.

outqset <name> This parameter specifies the logical name ofthe queue set which will be used with thisinterface. The queue set must be createdbeforehand. This parameter is optional.

proxy-arp This parameter turns on and off the ProxyARPfeature on this interface.

The allowed values areyes and no.

rate-limit<rate_limit>

This parameter specifies the rate limit value ofthe Ethernet interface.

Default value is 1G.

slave <iface> The physical interface to be added to the linkaggregation group. The number of slaveinterfaces is not restricted. Optionally theinterface name can be followed by a colonmark (:) and a priority.


add-slave Optional parameter. This parameter definesthe physical interface name to be added byusing command set networkinglinkaggr.


del-slave Optional parameter. This parameter definesthe physical interface name to be removed byusing command set networkinglinkaggr.



Issue: 02G DN0974301 41

2.4 Configuring Ethernet switch port groupPurpose

An Ethernet switch port group contains one or more ports. It can contain any externalports in a cluster. It has a unique VLAN ID, which is used to connect ports in differentboxes in a multi-box system to one VLAN. When port group is mapped as an interface toa node, the node is able to receive traffic from any of the port group ports. A port groupcan be mapped as an interface to multiple nodes, each receiving traffic from the sameport group.

1 Add a new Ethernet switch port group.To add a new Ethernet switch port group, enter the following command:add networking switch port-group name <name> port <port>

Example:To add a new Ethernet switch port group and assign a couple of switch ports to it,enter the following command:add networking switch port-group name pGroup1 port LMP-1-1-1:sfp13 port LMP-1-1-1:sfp15

2 View an Ethernet switch port groupTo view an Ethernet switch port group, enter the following command:show networking switch port-group [name <name>] [port <port>]

Example:

To view the Ethernet switch port group pGroup1, enter the following command:

show networking switch port-group name pGroup1

3 Delete an Ethernet switch port-group.To delete an Ethernet switch port group, enter the following command:delete networking switch port-group name <name>

Example:

To delete the Ethernet switch port group pGroup1, enter the following command:

delete networking switch port-group name pGroup1

Further information

Table 11: Parameters for networking switch port-group lists the parameters for thenetworking switch port-group commands:


42 DN0974301 Issue: 02G

Table 11 Parameters for networking switch port-group

Parameter

Description

<name> Specifies the port group name.

<port> Specifies the switch port name pair. For example, LMP-1-1-1:sfp13, here LMP-1-1-1 is the name of the switch andsfp13 is the name of the port.

2.5 Configuring IP address for interfacesPurpose

To configure the IP parameters and addresses of interfaces.

1 Create IP address for the network interfaces.Use the add networking address command to add an external IP address tothe interface.

g When configuring IP addresses for user plane traffic, one IP address can be used foronly one logical interface type (for example, Iub).

g The network element internal addresses are assigned automatically during thecommissioning and they cannot be modified.

Use the following syntax of the command:add networking [instance <name>] address <owner> iface <name> ip- address <address/mask> [role <name>] [user <MO_name>]Detailed information on usage of the parameters is listed in the following table:

Table 12 Parameters for add networking address command

Parameter

Description

<owner> Mandatory parameter. This parameter defines the owner(node or recovery group) that uses the IP address, forexample, /CFPU-0.

iface <name> Mandatory parameter. This parameter defines the interfaceto be used by the IP address, for example eth1.

instance Optional parameter. The networking configuration is appliedto the virtual routing instance specified by this parameter. Ifno instance is specified, the configuration is applied to thedefault routing instance.


Issue: 02G DN0974301 43

Table 12 Parameters for add networking address command (Cont.)

Parameter

Description

ip-address<address/mask>

Mandatory parameter. This parameter defines the IPaddress and subnet mask to be assigned, for example10.0.0.19/24.

role <name> Optional parameter. This parameter defines the role (auser-defined string) for the service using this IP address.For example, for Iu-PS user plane IP address, value“iupsup” can be used.

user <MO_name> Optional parameter. This parameter defines a user(recovery group or recovery unit) for this IP address.

g This parameter is used only if the IP address is usedalso by services other than the owner of the address.

Example

Assign IP address 10.0.1.8.1/28 to the VLAN interface vl110 on QNUP-0. The IPaddress is used for Iu-PS user plane traffic.

add networking address /QNUP-0 iface vl110 ip-address10.0.8.1/28 role iupsup

2 Modify the IP address that is assigned to a network interface.External IP addresses of the system are modified by using the set networkingaddress command. The full syntax of the command is:set networking [instance<name>] address <owner> iface <name> ip- address <address/mask> [add-role <role_name>] [add-user <user_name>] [del-role <role_name>] [del-user <user_name>]

Table 13 Parameters for set networking address command

Parameter

Description

instance Optional parameter. The networking configuration is appliedto the virtual routing instance specified by this parameter. Ifno instance is specified, the configuration is applied to thedefault routing instance.

<owner> Mandatory parameter. This parameter defines the owner(node or recovery group) to be using the IP address, forexample, /CFPU-0.

iface <name> Mandatory parameter. This parameter defines the interfaceto be used by the IP address, for example eth1.


44 DN0974301 Issue: 02G

Table 13 Parameters for set networking address command (Cont.)

Parameter

Description


Mandatory parameter. This parameter defines the IPaddress and subnet mask to be assigned, for example10.0.0.19/24.

add-role<role_name>

Optional parameter. This parameter defines the role nameto be added for the service using this IP.

add-user<user_name>

Optional parameter. This parameter defines the user nameto be added for the service using this IP.

del-role<role_name>

Optional parameter. This parameter defines the role nameto be deleted for the service using this IP.

del-user<user_name>

Optional parameter. This parameter defines the user nameto be deleted for the service using this IP.

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

4 Delete the IP address from the network interfaces.To remove the external IP from the system use the delete networking addresscommand as follows:delete networking [instance <name>] address <owner> iface <name> ip- address <address/mask>Detailed information on usage of the parameters is listed in the following table:

Table 14 Parameters for delete networking address command

Parameter

Description

instance This parameter defines the name of the virtual routinginstance. If no instance is specified, the default routinginstance is used.

<owner> This parameter defines the owner (node, recovery group orrecovery unit) that is currently using the IP address to bedeleted, for example, /CFPU-0.

iface <name> This parameter defines the interface that is used by the IPaddress to be deleted, for example eth1.


Issue: 02G DN0974301 45

Table 14 Parameters for delete networking address command (Cont.)

Parameter

Description


This parameter defines the IP address and subnet mask tobe deleted, for example 10.0.0.10/24.

2.6 Configuring IP resources for Iub control planePurpose

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 Configure the Iub subnet for control plane.When the user creates an NBAP link, the Iub subnet matching the specified VRF andIP address/mask is chosen for the NBAP link. The Iub subnet parameters also applyto the local SCTP association of the NBAP link.Use the add networking iubsnt command in order to create the Iub subnet, thesyntax of the command is the following:add networking iubsnt iubsnt-id <iubsnt-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 <vrf>]

The following table describes the usage of the parameters.

Table 15 Parameters of add networking iubsnt command

Parameter

Description

Value range

iubsnt-id Mandatory parameter. This is the IDof the Iub subnet. A default subnetwith ID 0 is available with subnetaddress 0.0.0.0 and mask 0. Thisdefault subnet cannot be deleted.

Range: 1-8

net-address Mandatory Parameter. Thisparameter is used to identify thenetwork address of iubsnt.

Format: NET-ADDRESS/MASK-LEN


46 DN0974301 Issue: 02G

Table 15 Parameters of add networking iubsnt command (Cont.)

Parameter

Description

Value range

rto-initial Optional parameter. This is theinitial value of RTO(retransmissiontimeout) that is used in RTOcalculations. This parameter is aproperty of SCTP protocol.

Range: 10 to 60000 msDefault: 1000 ms

rto-max Optional parameter. This is themaximum value of RTO that is usedin RTO calculations. This parameteris a property of SCTP protocol.

Range: 10-120000 msDefault: 2000 ms

rto-min Optional parameter. This is theminimum value of RTO that is usedin RTO calculations. This parameteris a property of SCTP protocol.


association-max-retrans

Optional parameter. This parameteris a property of SCTP protocol. Itdefines the maximum number ofconsecutive retransmissions to apeer over the association before anendpoint considers that the peer isunreachable and closes theassociation.

Range: 1-15Default: 5

heartbeat-interval

Optional parameter. This is the timeinterval between the trasmissions oftwo HEARTBEAT chunks. Thisparameter is a property of SCTPprotocol.


path-max-retrans Optional parameter. This parameteris a property of SCTP protocol. Itdefines the maximum number ofconsecutive retransmissions ofmessages over the path to the peerendpoint before it is marked asinactive. A path connects a sourceIP address and a destination IPaddress.


sack-period Optional parameter. This parameteris a property of SCTP protocol. Itdefines the delayed SACK timeout.


max-frame-size Optional parameter. This parameterdefines the maximum segment sizeat SCTP layer.

Range: 540 to 1452bytes, values ofmultiples of fourDefault: 1452 bytes


Issue: 02G DN0974301 47

Table 15 Parameters of add networking iubsnt command (Cont.)

Parameter

Description

Value range

g If the valueentered is not amultiple of four,the value isrounded down tothe nearest validvalue.

vrf Optional parameter. This is thename of the virtual routing andforwarding instance.

The allowed values area to z, A to Z, 0 to 9,and _ characters (lowercase, upper case,numeric andunderscore). Themaximum length of aname is 15 charactersand the minimum lengthis 1 character.

Example 1: Adding an Iub subnet with default parameter valuesadd networking iubsnt iubsnt-id 1 net-address 192.251.1.1/16Example 2: Adding an Iub subnet and setting all parameter valuesadd networking iubsnt iubsnt-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-framesize 1000 vrf vrf1

2 Configure the 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 unitis the address for NBAP links based on SCTP association.When you create an NBAP link, the system selects QNIUB RG based on VRF and IPaddress/mask. If multiple RGs are found, the system selects QNIUB RG based on loadsharing principle to balance load among different RGs. Furthermore, if the chosenQNIUB RG has more than one IP addresses on the specified VRF and IPaddress/mask, the load sharing cannot be done among the IP addresses in the sameRG.To achieve load sharing on IP address level, assign one IP address instead of anetwork segment when you create the NBAP link.

Use the following syntax of add networking address command to add anexternal IP address:add networking [instance <name>] address <owner> iface <name>ip-address <address/mask>] [peer <address/mask>] [role <name>][user <MO_name>]

For more information on IP configuration, see instructions in Configuring IPparameters and addresses of interfaces.


48 DN0974301 Issue: 02G

3 Check the Iub subnet configuration parameters.Use the show networking iubsnt command in order to check the parameters ofthe Iubsnt, the syntax of the command is the following:show networking iubsnt [iubsnt-id <iubsnt-id>]

When no parameter is specified, all Iub subnets will be listed.

Table 16 Parameter of show networking iubsnt command

Parameter

Description

Value range

iubsnt-id Optional parameter. This is the IDof the Iub subnet. The Iub subnetwith ID 0 is the default subnet thatcannot be deleted.

Range: 0-8

4 Modify the Iub subnet configuration parameters.Use the set networking iubsnt command to modify the parameters of theIubsnt, the syntax of the command is as follows:set networking iubsnt iubsnt-id <iubsnt-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.

Table 17 Parameters of set networking iubsnt command

Parameter

Description

Value range

iubsnt-id Mandatory parameter. This is theID of the Iub subnet. A defaultsubnet with ID 0 is available withsubnet address 0.0.0.0 and mask0. This default subnet cannot bedeleted.

Range: 0-8

rto-initial Optional parameter. This is theinitial value of RTO(retransmissiontimeout) that is used in RTOcalculations. This parameter is aproperty of SCTP protocol.

Range: 10 to 60000 msDefault: 1000 ms

rto-max Optional parameter. This is themaximum value of RTO that is usedin RTO calculations. Thisparameter is a property of SCTPprotocol.



Issue: 02G DN0974301 49

Table 17 Parameters of set networking iubsnt command (Cont.)

Parameter

Description

Value range

rto-min Optional parameter. This is theminimum value of RTO that is usedin RTO calculations. Thisparameter is a property of SCTPprotocol.


association-max-retrans

Optional parameter. This parameteris a property of SCTP protocol. Itdefines the maximum number ofconsecutive retransmissions to apeer over the association before anendpoint considers that the peer isunreachable and closes theassociation.


heartbeat-interval

Optional parameter. This is the timeinterval between the trasmissionsof two HEARTBEAT chunks. Thisparameter is a property of SCTPprotocol.


path-max-retrans Optional parameter. This parameteris a property of SCTP protocol. Itdefines the maximum number ofconsecutive retransmissions ofmessages over the path to the peerendpoint before it is marked asinactive. A path connects a sourceIP address and a destination IPaddress.


sack-period Optional parameter. This parameteris a property of SCTP protocol. Itdefines the delayed SACK timeout.


max-frame-size Optional parameter. This parameterdefines the maximum segment sizeat SCTP layer.

Range: 540 to 1452bytes, values ofmultiples of fourDefault: 1452 bytes

g If the valueentered is not amultiple of four,the value isrounded down tothe nearest validvalue.


50 DN0974301 Issue: 02G

Example: Changing Iub subnet configurationset networking iubsnt iubsnt-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 1452

5 Delete the Iub subnet, if necessary.

g Make sure that there are no NBAP links in the subnet, before deleting the Iubsnt.

Use the delete networking iubsnt command to delete the Iubsnt, the syntaxof the command is as follows:delete networking iubsnt iubsnt-id <iubsnt-id>

Table 18 Parameter of delete networking iubsnt command

Parameter

Description

Value range

iubsnt-id Mandatory parameter. This is the IDof the Iub subnet. The Iub subnetwith ID 0 is the default subnet thatcannot be deleted.

Range: 1-8

Further information

For more information on Iubsnt SCLI commands, see Multicontroller RNC SCLICommands.


Issue: 02G DN0974301 51

3 Configuring Iu, Iub and Iur interfaces

3.1 IntroductionThis chapter describes configuration examples for the IP layer and site solutions for themcRNC. The O&M connectivity is handled separately in Configuring IP for O&Mconnections chapter.

The basic principles for the site solutions are presented in chapter Multicontroller RNCsite solutions. The mcRNC Site Solution alternatives and related references can befound below:

1. mcRNC Site Solution with OSPF and VRFSite Solution option applies dynamic routing for distributing the user plane applicationIP addresses to site routers. The Iu/Iur control plane configuration with SCTP multi-homing is managed with static routes. Both 1GE and 10GE interfaces are supportedfor network connectivity.The OSPF Site Solution configuration examples are listed within chapters:

• Configuring mcRNC OSPF SiSo, VRF, 10GE and shared EIPU• Configuring mcRNC OSPF SiSo, VRF, 1GE with LAG and shared EIPU• Configuring mcRNC OSPF SiSo, VRF, 10GE, 1GE with LAG and dedicated EIPU

The Iu and Iur control plane configuration and the Radio Network configuration is thesame for VRRP/HSRP and OSPF Site Solution. The Iu/Iur control plane is managedwith static routes within all site solution options.For more information on the OSPF site solution, see “mcRNC Site Solution based onJuniper with OSPF using 10 Gigabit Ethernet connectivity” and “mcRNC SiteSolution based on Juniper with OSPF using 1GE and 10GE connectivity”.

2. mcRNC Site Solution with VRRP/HSRPSite Solution option applies VRRP/HSRP for site routers/switches redundancy. TheL2 domain spans over the EIPUs and site routers/switches but not further to network.The configuration option provides planning principles compatibility with the currentIPA-RNC VRRP/HSRP site solution. 1GE and 10GE interfaces are supported fornetwork connectivity.The VLAN configuration provides logical traffic separation in between the Iu-PS, Iu-CS, Iur and Iub traffic. The Iu/Iur control plane and Radio Network layer configurationfor each logical interface is fully opened within the chapters 3.2 – 3.5.The VRRP/HSRP site solution with Ethernet Link Aggregation, VRF and 10GEinterface are presented within the chapters:

• Configuring mcRNC VRRP/HSRP SiSo, VRF, 10GE and shared EIPU• Configuring mcRNC VRRP/HSRP SiSo, VRF, 1GE with LAG and shared EIPU•

For more information on the mcRNC VRRP/HSRP site solution, see mcRNC SiteSolution based on Juniper with VRRP using 10 Gigabit Ethernet connectivity andmcRNC Site Solution based on Juniper with VRRP using 1GE and 10GEconnectivity.

3. mcRNC Evolved Site Solution


52 DN0974301 Issue: 02G

configuring_ip_connection_for_mcrnc.pdf

The Evolved Site Solution option has been supported already in mcRNC2.0. TheEthernet switching takes place within the site router simplifying the overall VLANsetup. BFD (Single Hop) with static routes is applied for L3 level next hopsupervision. Only 1GE interfaces are supported for external connectivity.

•

4. Configuring IP for Iu-BC interface (RNC - CBC)The Iu-BC (Service Area Broadcast) connections are terminated to CFPU unit. TheIP address for the communication is located to QNCFCP recovery group within theCPFU.

5. Configuring IP for Iu-PC interface (RNC - SMLC/SAS)Iu-PC is the 3GPP interface between mcRNC and Standalone SMLC (SAS), which isused to transport UE location calculation related information. Iu-PC interface IPconfiguration guidelines follow Iu/Iur control plane IP configurations, which arepresented in this document.In case GEO-redundant Iu-PC configuration is implemented, contact NSN customersupport for additional configuration instructions.

3.2 Configuring mcRNC OSPF SiSo, VRF, 10GE andshared EIPUPurpose

The purpose of this section is to explain how to configure the Iu, Iur and Iub interfaceswith the OSPF site solution, Virtual Routing and Forwarding (VRF), 10GE interfaces.Themulticontroller RNC provides optimized connectivity alternative for 10GE interface-basedsite solution. With 10GE optimized solution, two EIPU nodes of a single BCN module areconnected to the same external 10GE port of the BCN module.

The following optional features are required:

• RAN1510 OSPF for Redundancy• RAN2696 mcRNC 10 Gigabit Ethernet Based Network Connectivity

The following standard feature is applied:

• RAN2257 Support of Virtual Routing and Forwarding in mcRNC

The configuration example is presented with mcRNC capacity step s1 and with a sharedEIPU setup. The shared EIPU setup means that all EIPU nodes terminate the traffic fromall logical interfaces (Iu/Iur/Iub). The example configuration can be applied for planningand configuring bigger capacity steps using the presented design pattern for furtherneeded EIPU nodes. The configuration and connectivity principles apply according toEIPU pair and BCN pair basis. In case of full 10GE connectivity optimized configurationone 10GE interface per BCN module is required.

The VRF instances are logically separate routing processes within the EIPU withseparate routing tables and interfaces.The VRF instances are used to keep routinginformation, IP addressing, and IP interfaces logically separated between different logicalinterfaces. With OSPF SiSo, the Iu/Iur control plane - managed with static routes - isseparated from the user plane resources routing that is managed dynamically withOSPF.

Configuring IP Connection for Multicontroller RNC Configuring Iu, Iub and Iur interfaces

Issue: 02G DN0974301 53


The VRF implementation is applied for the Iu/Iur/Iub user plane and control plane. Forthe Iu/Iur control plane, both IP addresses of the SCTP multi-homed association mustbelong to the same VRF. The O&M functions within the CFPU are supported only withinthe default VRF (VRF-0).

The main building blocks for the VRF are the following:

• VRFs are configured in EIPU nodes to logically separate the routing functions and IPaddressing.

• Simplified static route configuration can be applied for the user plane connections.• One VLAN interface can belong to only one VRF.

The main building blocks for the OSPF site solution in general are the following:

• L3 type of site solution with dynamic routing• OSPF manages the user plane routing• Iu/Iur control plane with SCTP Multi-Homing is managed with static routes• Supports 1GE and 10GE interfaces

Restrictions

• O&M-related functions in the CFPU unit belong to the default VRF only. Iu/Iur controlplane IP addresses of a single SCTP multi-homed association can only belong toone VRF. Incoming traffic towards the IP address within the VRF has to come in viathe VLAN interface tied to the same VRF.

g Note

The given IP addresses and subnets are just examples and must be set according tothe actual network plan.

The configuration examples in the instructions are based on the IP addressing presentedin Figure 16: Network configuration for mcRNC OSPF SiSo with 10GE and VRF. VRFsare applied for different domains:the Iu and Iur user plane, the Iu and Iur control planeand the Iub control and user planes.

Configuring Iu, Iub and Iur interfaces Configuring IP Connection for Multicontroller RNC

54 DN0974301 Issue: 02G

Figure 16 Network configuration for mcRNC OSPF SiSo with 10GE and VRF

The detailed configuration for the Iub interface is presented in Figure 17: Iubconfiguration for mcRNC OSPF SiSo with 10GE and VRF. The application IP addressesfrom the Iub user plane and control plane are bound to each QNUP and QNIUBinstances and assigned to the loopback interface of the corresponding VRF. Separate IPaddresses are applied for the Iub user plane and the Iub control plane to allowindependent failure actions for the services. The related IP addresses and VLANinterfaces belong to the “iub” VRF with numeric id11.


Issue: 02G DN0974301 55

Figure 17 Iub configuration for mcRNC OSPF SiSo with 10GE and VRF

The detailed figure for Iu-PS, Iu-CS and Iur user plane IP addressing is presented inFigure 18: Iu/Iur User Plane configuration for mcRNC OSPF SiSo with 10GE and VRF.Separate IP addresses are applied for the Iu-CS, Iu-PS and Iur user plane traffic IP layertermination. The related IP addresses and VLAN interfaces belong to “iuiurup” VRF withnumeric id5.


56 DN0974301 Issue: 02G

Figure 18 Iu/Iur User Plane configuration for mcRNC OSPF SiSo with 10GE and VRF

The Iu-PS, Iu-CS and Iur control plane SCTP associations and related IP addressing ispresented in Figure 19: Iu/Iur Control Plane configuration for mcRNC OSPF SiSo with10GE and VRF. The SCTP IP addresses are configured to the EIPU backplane cfeigwinterfaces. Certain EIPU nodes are selected to work as gateways for the Iu/Iur controlplane traffic. The related IP addresses and VLAN interfaces belong to the “iuiurcp” VRFwith numeric id1. The Iu and Iur control plane configuration principles are similar in bothVRRP/HSRRP and OSPF site solutions.


Issue: 02G DN0974301 57

Figure 19 Iu/Iur Control Plane configuration for mcRNC OSPF SiSo with 10GE andVRF

g The SCTP multi-homed associations source IP address configuration model haschanged in mcRNC4.1 (RU50 EP1). All SCTP source IP addresses can be configuredfrom the backplane side sctp subnets (sctp-interfaces). With mcRNC3.0 or earlier SWreleases the configuration model listed in RU40 documentation has to be still followed.Even though a simpler configuration model is supported with mcRNC4.1 still the earlierconfiguration model can be continued to be used after the SW upgrade to mcRNC4.1level. There is no need to adjust the configuration of already installed base immediatelybut the changes can be made gradually at appropriate time.

The mcRNC site configuration applied VLANs for logical traffic separation and VRFs forlogical routing functions separation. With VRFs and static routes, it is possible to apply,for example, a default route configuration for the user plane connections in case all theuser planes goes out via the same gateway without affecting the Iu/Iur control planewhich requires specific route entries. Configuration with 10GE interfaces providessimplified connectivity, IP addressing and easy sharing of the EIPU capacity. Within thisconfiguration example all EIPU nodes terminate traffic from all logical interfaces (sharedEIPU setup).

Multicontroller RNC

VRF and VLAN configuration:

• Iu/Iur User Plane, VRF iuiurup (VRF id 5)


58 DN0974301 Issue: 02G

– VLAN11 10.0.1.0/28

– VLAN12 10.0.1.16/28

• Iu/Iur Control Plane, VRF iuiurcp (VRF id 1)

– VLAN15 10.1.8.0/28– VLAN17 10.1.8.32/28– VLAN19 10.1.8.64/28– VLAN16 10.1.8.128/28– VLAN18 10.1.8.160/28– VLAN20 10.1.8.192/28

• Iub Control and User Plane, VRF iub (VRF id 11)

– VLAN21 10.0.4.0/28

– VLAN22 10.0.4.16/28

Application IP addresses are assigned to a certain recovery group (RG) instance, whichprovides the redundancy scheme for hardware and software failures. With the OSPF sitesolution, the user plane IP addresses are configured to the loopback interface of thecorresponding VRF instance. The IP address follows the active Recovery Unit (RU) ofthe QNUP RG. The Iub-related application IP addresses are presented in Table 19: Iubcontrol and user plane IP addresses.The Iu and Iur user plane addresses are presentedin Table 20: Iu and Iur user plane IP addresses.

Table 19 Iub control and user plane IP addresses

Recovery Group

Iub

QNUP-0, Iub user plane 10.1.0.1

QNUP-1 10.1.0.2

QNUP-2 10.1.0.3

QNUP-3 10.1.0.4

QNIUB-0, Iub control plane 10.1.0.65

QNIUB-1 10.1.0.66

QNIUB-2 10.1.0.67

QNIUB-3 10.1.0.68


Issue: 02G DN0974301 59

Table 20 Iu and Iur user plane IP addresses

Recovery Group

Iu-PS

Iu-CS

Iur

QNUP-0 10.1.1.1 10.1.1.17 10.1.1.33

QNUP-1 10.1.1.2 10.1.1.18 10.1.1.34

QNUP-2 10.1.1.3 10.1.1.19 10.1.1.35

QNUP-3 10.1.1.4 10.1.1.20 10.1.1.36

• Iu-PS control plane, SCTP associations

– SCTP association-1, 10.1.8.2/28, 10.1.8.145/28– SCTP association-2, 10.1.8.18/28, 10.1.8.130/28– SCTP association-3, 10.1.8.3/28, 10.1.8.147/28– SCTP association-4, 10.1.8.20/28, 10.1.8.131/28

• Iu-CS control plane, two SCTP associations


• Iur control plane, SCTP associations

– SCTP association-1, 10.1.8.66/28, 10.1.8.209/28– SCTP association-2, 10.1.8.82/28, 10.1.8.194/28

Routers/site switches:

• Router-1 gateway IP addresses: VL17 10.0.2.1• Router-2 gateway IP addresses: VL18 10.0.2.17

OSPF for site routers/switches (user plane traffic VRFs):Two OSPF areas associated toseparate VRFs are applied for Iu/Iur user plane and Iub.

• Iu/Iur user plane: OSPF stub area 10.0.1.0, routing instance iuiurup• Iub control and user plane: OSPF stub area 10.0.4.0, routing instance iub

Before you start

Ensure that the mcRNC and site routers have been installed and all requiredconnections have been established. The site solution with OSPF is described in mcRNCSite Solution based on Juniper EX4500 with OSPF using 10 Gigabit Ethernetconnectivity documents.

Configure the parameters for the Iu-PS, Iu-CS, Iur and Iub interfaces according to the listbelow.

Iu-PS, Iu-CS, Iur, Iub generic paramaters


60 DN0974301 Issue: 02G

• Iu-PS interfaceThe IUPS object contains the peer core network element configuration, for examplethe signaling point code (SPC) of the SGSN. The IUPSIP object class instancescontain the IP address and subnet definitions for a selection of the IP-based routeduring the user plane connection setup. For typical cases, a single (generic) IUPSIPinstance is sufficient, even in case of Flexible Iu or Direct Tunnel features. In thissimple case, it is not required to specify core network user plane IP addresses in theRNC, instead 0.0.0.0/0 can be used. The differentiated services code point (DSCP)mapping for user plane connections is configured through the 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 DSCPmapping 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

– DestIPAddressPS

– IPNetmaskPS

RNTRM RNC-level parameters:

– EchoRequestSending (GTP-U ECHO REQUEST activation)

– IPStackErrorTimer

– N3Requests

– T3Response

– DSCPForGTPSignalling (GTP ECHO REQUEST DSCP value)

g The EchoRequestSending, N3Requests, and T3Response corresponding alarm is3472 IU-PS IP ROUTING ERROR. It is raised when GTP level Echo Request hasbeen enabled and sent, but Echo Response has not been received.

IPQM parameters:

– IPQMId

– ConversationalTCToDSCP

– StreamingTCToDSCP

– InteractiveTHP1TCToDSCP



– BackgroundTCToDSCP

• Iu-CS interfaceThe CS core (MGW and MSS) must be configured. For the MSS and MGWconfiguration refer to the core network documentation. Specific parameters must bedefined for each IP-based Iu interface. The differentiated services code pointmapping 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 egresstraffic scheduling.The following parameters are related to the Iu-CS interface.


Issue: 02G DN0974301 61

IUCS parameters:

– IPQMIdCS

– IPBasedRouteIdCS

– MinUDPPortCS

– RtcpActivation

– Iu Interface Identifier

– Core Network Identifier

– Mobile Country Code

– Mobile Network Code

– Network Indicator

– Signaling Point Code

– Release version of Core Network

IUCSIP parameters:

– IPBasedRouteIdCS

– DestIPAddressCS

– IPNetmaskCS

IPQM parameters:

– IPQMId

– ConversationalTCToDSCP

– StreamingTCToDSCP




– BackgroundTCToDSCP

• Iur interfaceNeighbor RNCs must be configured. Specific parameters must be defined for eachIP-based Iu interface. The differentiated services code point (DSCP) mapping for theuser plane connections is configured with the IPQM object attributes. Thecorresponding DSCP to PHB mapping is configured at the IP layer configuration.Each used DSCP must have a corresponding DSCP to PHB mapping for the egresstraffic scheduling.The following parameters are related to the Iur interface.IUR parameters:

– IPBasedRouteIdIur

– MinUDPPortIur

– MaxFPDLFrameSizeIur

– DSCPHighIur

– DSCPLowIur

– DSCPMedDCHIur

– ToAWEOffsetNRTDCHIP

– ToAWEOffsetRTDCHIP

– ToAWSOffsetNRTDCHIP

– ToAWSOffsetRTDCHIP

• Iub interface


62 DN0974301 Issue: 02G

Application IP addresses are assigned to a certain recovery group (RG) instance,which provides the redundancy scheme for hardware and software failures. In thisconfiguration example RG instances QNIUB-0, QNIUB-1, QNUP-0 and QNUP-1running within the EIPU-0 and 1 nodes are used for the user plane traffic termination.With VRRP/HSRP site solution the Iub control plane and user plane IP addressesare configured to VLAN interface subnet. The IP addresses follow the activeRecovery Unit (RU) of the QNIUB and QNUP RGs. For the Iub configuration all theVLAN interface addresses are logical addresses following the active RU.

– Iub user plane, QNUP-0 and QNUP-1 RG instances

• QNUP-0: VRF iub, 10.1.0.1• QNUP-1: VRF iub, 10.1.0.2• QNUP-2: VRF iub, 10.1.0.3• QNUP-3: VRF iub, 10.1.0.4

– Iub control plane, two QNIUB RG instances are used to provide the NBAP linkIP/SCTP termination

– Iub control plane, QNIUB-0 and QNIUB-1 RG instances:

• QNIUB-0: VRF iub, 10.1.0.65• QNIUB-1: VRF iub, 10.1.0.66• QNIUB-2: VRF iub, 10.1.0.67• QNIUB-3: VRF iub, 10.1.0.68• Iub control plane subnet configured to BTS: 10.1.0.64/27

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

The parameters can be configured with the mcRNC Parameter Editor GUI. BTSparameters can be configured with the BTS Site Manager or NetAct. For moreinformation about BTS parameters, see Plan Editor Flexi Transport Module Parameters.

g Note

Before starting a new IP layer configuration, check the existing IP layer configuration.Use the show networking ether and show networking address SCLIcommands to show the current settings of interfaces. If configuring the mcRNC usingthe IP plan, create and activate a plan in the mcRNC to have a basic configuration as astarting point for further modifications.

g Note

To avoid IP layer fragmentation, an MTU with the size of 1560 octets is recommendedto be used for the Iu-PS transport. For more information on MTU, seeWCDMA RAN IP Transport.

Steps


Issue: 02G DN0974301 63

3.2.1 Configuring mcRNC OSPF SiSo, VRF, 10GE and sharedEIPU instructions

1 Configure the VRF instances.

• SCLI commandsadd networking vrf name iuiurup id 5

add networking vrf name iuiurcp id 1

add networking vrf name iub id 11

• IP PlanRelated object class: VRFRNC-xx/IP-1/VRF-iuiurup1

• id = 5

2 Configure the physical interfaces.Physical network interfaces are assigned to a certain EIPU node, if not yetconfigured. The mcRNC default egress queue set rncdefault has to be assignedto the physical interface for proper default egress scheduling weights configuration.

• SCLI commands#Add shared port group to first BCN moduleadd networking switch port-group name sfp11-bcn1 port LMP-1-1-1:sfp11#Add shared port group to second BCN moduleadd networking switch port-group name sfp11-bcn2 port LMP-1-2-1:sfp11#Assign shared 10GE port from first BCN module to EIPUadd networking ether /EIPU-0 iface eth_b1 port sfp11-bcn1outqset rncdefault mtu 1560add networking ether /EIPU-1 iface eth_b1 port sfp11-bcn1outqset rncdefault mtu 1560add networking ether /EIPU-2 iface eth_b1 port sfp11-bcn1outqset rncdefault mtu 1560add networking ether /EIPU-3 iface eth_b1 port sfp11-bcn1outqset rncdefault mtu 1560#Assign shared 10GE port from second BCN module to EIPUadd networking ether /EIPU-0 iface eth_b2 port sfp11-bcn2outqset rncdefault mtu 1560add networking ether /EIPU-1 iface eth_b2 port sfp11-bcn2outqset rncdefault mtu 1560add networking ether /EIPU-2 iface eth_b2 port sfp11-bcn2outqset rncdefault mtu 1560add networking ether /EIPU-3 iface eth_b2 port sfp11-bcn2outqset rncdefault mtu 1560

•

g NoteThe 10GE port mode where several EIPU nodes share the same external 10GE port isnot configurable via IP plan interface within mcRNC3.0.


64 DN0974301 Issue: 02G

g NoteThe rate limit is inherited from the interface speed directly if no explicit value is given.

3 Configure VLAN interfaces within 10GE interfaces.The VLAN interface is created for a certain physical interface with a reference to itsname. The VLAN ids and the VLAN interface names must be planned andconfigured accordingly.

• SCLI commandsvlan 11-14, iu iur user planeadd networking instance iuiurup vlan /EIPU-0 realifaceeth_b1 vid 11 vlaniface iuiurup_vl11 mapping vlandscptopcpmtu 1560add networking instance iuiurup vlan /EIPU-0 realifaceeth_b2 vid 12 vlaniface iuiurup_vl12 mapping vlandscptopcpmtu 1560add networking instance iuiurup vlan /EIPU-1 realifaceeth_b1 vid 13 vlaniface iuiurup_vl13 mapping vlandscptopcpmtu 1560add networking instance iuiurup vlan /EIPU-1 realifaceeth_b2 vid 14 vlaniface iuiurup_vl14 mapping vlandscptopcpmtu 1560add networking instance iuiurup vlan /EIPU-2 realifaceeth_b1 vid 11 vlaniface iuiurup_vl11 mapping vlandscptopcpmtu 1560add networking instance iuiurup vlan /EIPU-2 realifaceeth_b2 vid 12 vlaniface iuiurup_vl12 mapping vlandscptopcpmtu 1560add networking instance iuiurup vlan /EIPU-3 realifaceeth_b1 vid 13 vlaniface iuiurup_vl13 mapping vlandscptopcpmtu 1560add networking instance iuiurup vlan /EIPU-3 realifaceeth_b2 vid 14 vlaniface iuiurup_vl14 mapping vlandscptopcpmtu 1560#vlan 15-20, iu iur control planeadd networking instance iuiurcp vlan /EIPU-0 realifaceeth_b1 vid 15 vlaniface iuiurcp_vl15 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-1 realifaceeth_b2 vid 16 vlaniface iuiurcp_vl16 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-2 realifaceeth_b1 vid 15 vlaniface iuiurcp_vl15 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-3 realifaceeth_b2 vid 16 vlaniface iuiurcp_vl16 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-0 realifaceeth_b1 vid 17 vlaniface iuiurcp_vl17 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-1 realifaceeth_b2 vid 18 vlaniface iuiurcp_vl18 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-2 realifaceeth_b1 vid 17 vlaniface iuiurcp_vl17 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-3 realifaceeth_b2 vid 18 vlaniface iuiurcp_vl18 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-0 realifaceeth_b1 vid 19 vlaniface iuiurcp_vl19 mapping vlandscptopcp


Issue: 02G DN0974301 65

add networking instance iuiurcp vlan /EIPU-1 realifaceeth_b2 vid 20 vlaniface iuiurcp_vl20 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-2 realifaceeth_b1 vid 19 vlaniface iuiurcp_vl19 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-3 realifaceeth_b2 vid 20 vlaniface iuiurcp_vl20 mapping vlandscptopcp#vlan 21-24, iub control and user planeadd networking instance iub vlan /EIPU-0 realiface eth_b1vid 21 vlaniface iub_vl21 mapping vlandscptopcpadd networking instance iub vlan /EIPU-0 realiface eth_b2vid 22 vlaniface iub_vl22 mapping vlandscptopcpadd networking instance iub vlan /EIPU-1 realiface eth_b1vid 23 vlaniface iub_vl23 mapping vlandscptopcpadd networking instance iub vlan /EIPU-1 realiface eth_b2vid 24 vlaniface iub_vl24 mapping vlandscptopcpadd networking instance iub vlan /EIPU-2 realiface eth_b1vid 21 vlaniface iub_vl21 mapping vlandscptopcpadd networking instance iub vlan /EIPU-2 realiface eth_b2vid 22 vlaniface iub_vl22 mapping vlandscptopcpadd networking instance iub vlan /EIPU-3 realiface eth_b1vid 23 vlaniface iub_vl23 mapping vlandscptopcpadd networking instance iub vlan /EIPU-3 realiface eth_b2vid 24 vlaniface iub_vl24 mapping vlandscptopcp

• IP PlanRelated object class: VLANRNC-xx/IP-1/OWNER-EIPU-0/VLAN-iuiurup_vl11

• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mapping = vlandscptopcp• mtu = 1560• realiface = eth_b1• vid = 11• vrf = iuiurup

4 Configure the IP addresses of the VLAN interfaces.Proceed with the following configuration for fixed VLAN interface IP addressconfiguration.

g The interface name refers to created physical interface. If VLANs are used, the networkinterface IP addresses are tied to VLAN interfaces.

#vlan 11-14, iu iur user planeadd networking instance iuiurup address dedicated /EIPU-0iface iuiurup_vl11 ip-address 10.0.1.2/28

add networking instance iuiurup address dedicated /EIPU-2iface iuiurup_vl11 ip-address 10.0.1.3/28




66 DN0974301 Issue: 02G





#vlan 15-20, iu iur control planeadd networking instance iuiurcp address dedicated /EIPU-0iface iuiurcp_vl15 ip-address 10.1.8.2/28

add networking instance iuiurcp address dedicated /EIPU-2iface iuiurcp_vl15 ip-address 10.1.8.3/28









#vlan 21-24, iub control and user planeadd networking instance iub address dedicated /EIPU-0 ifaceiub_vl21 ip-address 10.0.4.2/28

add networking instance iub address dedicated /EIPU-2 ifaceiub_vl21 ip-address 10.0.4.3/28








Issue: 02G DN0974301 67

• IP PlanRelated object class: ADDRRNC-xx/IP-1/OWNER-EIPU-0/ADDR-10.0.1.2-iuiurcp_vl11

• mask = 28• vrf = iuiurcp

5 Configure application IP addresses for user plane.With the OSPF site solution, the Iu/Iur/Iub user plane and Iub control planeapplication IP addresses are assigned to the loopback interfaces of thecorresponding VRF instance. The application IP address is present in the node/unitthat is running the service at the time (active recovery unit, RU).

g NoteThe role attribute is a free-form character string that can be configured optionally. Therole attribute can be defined to keep the IP addressing usage clearly visible to simplifythe system maintenance. For the Iu-PS, user plane addresses apply, for example, roleiupsup.Proceed with the following configuration,

• SCLI commands#Iu-PS user plane IP addresses, VRF iuiurupadd networking instance iuiurup address dedicated /QNUP-0 iface lo ip-address 10.1.1.1/32 role iupsup

add networking instance iuiurup address dedicated /QNUP-1 iface lo ip-address 10.1.1.2/32 role iupsup



#Iu-CS user plane IP addresses, VRF iuiurupadd networking instance iuiurup address dedicated /QNUP-0 iface lo ip-address 10.1.1.17/32 role iucsup

add networking instance iuiurup address dedicated /QNUP-1 iface lo ip-address 10.1.1.18/32 role iucsup



#Iur user plane IP addresses, VRF iuiurupadd networking instance iuiurup address dedicated /QNUP-0 iface lo ip-address 10.1.1.33/32 role iurup

add networking instance iuiurup address dedicated /QNUP-1 iface lo ip-address 10.1.1.34/32 role iurup


68 DN0974301 Issue: 02G



#Iub control and user plane IP addresses, VRF iubadd networking instance iub address dedicated /QNUP-0 iface lo ip- address 10.1.0.1/32 role iubup

add networking instance iub address dedicated /QNUP-1 iface lo ip- address 10.1.0.2/32 role iubup



add networking instance iub address dedicated /QNIUB-0 iface lo ip-address 10.1.0.65/32 role iubcp




• IP PlanRelated object class: ADDRRNC-xx/IP-1/OWNER-QNUP-0/ADDR-10.1.1.1/32-lo5

• mask = 32• vrf = iuiurup• role = iupsup

6 Configure IP addresses for Iu and Iur control plane.The Iu/Iur control plane IP addresses are configured to sctp1 and sctp2 interfaces atbackplane side. The control plane subnets span over all EIPU nodes (or over theplanned nodes), providing the possibility to reach the service via any EIPU nodewithout additional static routes configuration.The SIGTRAN-related SCTP associations for different neighbor elements must belocated as evenly as possible within the EIPU nodes. At least four EIPU nodes mustbe applied towards one CN peer element and the SCTP associations towardsdifferent CN/neighbor RNC elements might be distributed evenly in between all EIPUnodes.


Issue: 02G DN0974301 69

g NoteThe SCTP association is terminated to a certain EIPU node. The IP addresses of SCTPmulti-homed association are configured to the interface from where the outgoingSCTP/SIGTRAN traffic is forwarded out. The sctp1_[VRF-id] and sctp2_[VRF-id]interfaces are pre configured to the mcRNC. The first four RFs including the defaultVRFs (VRF id 1- 4) contain the SCTP interfaces and they are applied for the Iu/Iurcontrol plane configuration.

g NoteThe role attribute is a free-form character string that can be configured optionally. Therole attribute can be defined to keep the IP addressing usage clearly visible to simplifythe system maintenance. For the Iu-PS control plane addresses apply, for example, role“iupscp”.

g NoteThe user /SS7SGU has to be added for the interface IP addresses that are applied asIu/Iur control plane source IP addresses (SS7/SIGTRAN/SCTP IP termination).

Proceed with the following configuration,

• SCLI commands#Iu-PS Control plane IP addressesadd networking instance iuiurcp address dedicated /EIPU-0 iface sctp1_1 ip-address 10.1.8.17/28 role iupscp user /SS7SGU

add networking instance iuiurcp address dedicated /EIPU-1 iface sctp1_1 ip-address 10.1.8.18/28 role iupscp user /SS7SGU







t NoteProceed with similar logic for all CN and neighbor RNC elements according to the plan.

• IP PlanRelated object class: ADDRRNC-xx/IP-1/OWNER-EIPU-0/ADDR-10.1.8.17-sctp1_1


70 DN0974301 Issue: 02G

• mask = 28• vrf = iuiurcp• role = iupscp

7 Check and configure the Iub SCTP parameters, IUBSNTThe Iub interface SCTP layer parameters are managed through the IUBSNT objectclass. The system contains one default SCTP profile. For the new NBAP/SCTPconnection, the default profile values are applied, unless an explicitly-configuredIUBSNT matching the IP address of the selected RNC is found from the system. TheIUBSNT object IP address and mask attributes define the group of Iub control planeterminations where the profile is applied. In most cases, the default profile values canbe applied.

g The IUBSNT profile contains the maximum SCTP frame size definition which controlshe fragmentation at the SCTP layer. To avoid fragmentation at the IP layer, themaximum IP datagram size must not exceed the MTU configured in the network. Inaddition 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 guaranteesthat SCTP packets are not fragmented at the IP layer as long as the transport networkMTU has a value of 1472 or above.

• SCLI commandsCheck the current profiles and value:show networking iubsnt {[local-subnet-id <subnetid-value>]?}Add new profile, if needed:add networking iubsnt local-subnet-id 1 net-address10.1.0.0/24 rto-initial 2000 rto-min 1759 rto-max 3000association-max-retrans 7 pathmax-retrans 7 heartbeat-interval 2000 sack-period 400 max-framesize 1452

• IP Plan

Related object class: IUBSNTRNC-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 = 1759 ms• sackPeriod = 400 ms

8 Configure the static routes.The following static routes mustbe configured to the system. The site routersinterface addresses are applied as gateways for the Iu control plane multi-homedconnections.


Issue: 02G DN0974301 71

• User plane traffic: destination subnets are reached with routes learned via theOSPF.

• Control plane traffic: destination subnets are reached via site the outer or theEIPU backplane interface address as the gateway. The Table 21: Routing tablefor Iu-PS trafficpresents the static routes needed towards the Iu-PS control plane.Configure the other control plane static routes with similar logic.

• Static routes for ingress traffic via the backplane are not needed.• Iu/Iur control plane, the SCTP IP addresses are located at the local subnets of

the EIPU nodes, thus no static routes are needed at the ingress direction.

Table 21 Routing table for Iu-PS traffic

Node

VRF

Network Id

Priority

Gateway

Notes

EIPU-0 iuiurcp 10.8.0.0/24 0 10.1.8.1 Iu-PS control plane, router-1 as GWto first destination CP subnet

EIPU-0 iuiurcp 10.8.1.0/24 0 10.1.8.146 Iu-PS control plane, via EIPU-1 androuter-2 as GW to second destinationCP subnet

EIPU-1 iuiurcp 10.8.0.0/24 0 10.1.8.17 Iu-PS control plane, via EIPU-0 androuter-1 as GW to first destination CPsubnet

EIPU-1 iuiurcp 10.8.1.0/24 0 10.1.8.129 Iu-PS control plane, router-2 as GWto second destination CP subnet


EIPU-2 iuiurcp 10.8.1.0/24 0 10.1.8.148 Iu-PS control plane, EIPU-1 androuter-2 as GW to second destinationCP subnet



• SCLI commands

g NoteConfigure all Iu and Iur user plane and Iub control and user plane routes with the sameprinciples to all related EIPU nodes.


72 DN0974301 Issue: 02G

#Control plane, routes may serve several destination CN elements depending onthe network planningset routing instance iuiurcp node EIPU-0 static-route 10.8.0.0/24 nexthop gateway address 10.1.8.1 on

set routing instance iuiurcp node EIPU-0 static-route 10.8.1.0/24 nexthop gateway address 10.1.8.146 on







g NoteConfigure all Iu and Iur control plane routes with the same principles to all needed EIPUnodes,

• IP Plan

RNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurcp/SRT4-10.8.0.0-24

• nexthop = 2 (gateway)

RNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurcp/SRT4-10.8.0.0-24/ADR4GW-10.1.8.1

• No attributes needed, default values are applied





9 Configure OSPF

a) Configure the OSPF router id for each node


Issue: 02G DN0974301 73

g NoteThe interface IP address applied for the given VRF is set as the router id. It isrecommended to select an existing IP address to the OSPF router id to make itinherently unique. Although it is not mandatory to use an IP address as the router id, adotted-quad value might be used.

The following are the router id settings for iuiurup and iub VRF instances.

• SCLI commands#Router id values for iuiurup VRFset routing instance iuiurup node EIPU-0 router-id10.0.1.2set routing instance iuiurup node EIPU-1 router-id10.0.1.34set routing instance iuiurup node EIPU-2 router-id10.0.1.3set routing instance iuiurup node EIPU-3 router-id10.0.1.35#Router id values for iub VRFset routing instance iub node EIPU-0 router-id 10.0.4.2set routing instance iub node EIPU-1 router-id 10.0.4.34set routing instance iub node EIPU-2 router-id 10.0.4.3set routing instance iub node EIPU-3 router-id 10.0.4.35

• IP PlanRelated object class: GLPRMRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup/GLPRM

• routerId = 10.0.1.2

b) Configure the OSPF areas

g NoteCreate the OSPF stub area within each needed routing instance.

• SCLI commands#iuiurup areasset routing instance iuiurup node EIPU-0 ospf area 10.0.1.0 on

set routing instance iuiurup node EIPU-0 ospf area 10.0.1.0 stub on

set routing instance iuiurup node EIPU-1 ospf area 10.0.1.0 on





set routing instance iuiurup node EIPU-3 ospf area 10.0.1.0


74 DN0974301 Issue: 02G

stub on

#iub areasset routing instance iub node EIPU-0 ospf area 10.0.4.0 on

set routing instance iub node EIPU-0 ospf area 10.0.4.0 stub on

set routing instance iub node EIPU-1 ospf area 10.0.4.0 on






– IP PlanRelated object class: O2AREARNC-xx/IP-0/OWNER-EIPU-0/RTINST-iuiurup/O2AREA-10.0.1.0

– stub = 1 (yes, Stub area)

c) Adjust OSPF throttle SPF delay for link break handlingThe OSPF throttle SPF delay is needed to be adjusted in order to initiate the SPFrecalculation in the EIPU routing instance quickly enough after the neighbour orlink failure. The configuration needs to be repeated for all EIPU nodes and allrouting instances having the OSPF configuration. The configuration is neededalways when the OSPF interfaces in the EIPU leading to routers have differentcost values. In such case the SPF recalculation is performed immediately afterthe interface failure is detected.set routing instance iuiurup node EIPU-0 ospf throttle spf-delay 200set routing instance iub node EIPU-0 ospf throttle spf-delay 200set routing instance iuiurup node EIPU-1 ospf throttle spf-delay 200set routing instance iub node EIPU-1 ospf throttle spf-delay 200

d) Activate the OSPF on the loopback and network interfaces.Proceed with the following configuration to activate the OSPF on the loopbackinterfaces.

• SCLI commands#iuiurup VRF loopback interfaceset routing instance iuiurup node EIPU-0 ospf interface lo area 10.0.1.0 on

set routing instance iuiurup node EIPU-1 ospf interface lo area 10.0.1.0 on



Issue: 02G DN0974301 75


#iub VRF loopback interfaceset routing instance iub node EIPU-0 ospf interface lo area 10.0.4.0 on

set routing instance iub node EIPU-1 ospf interface lo area 10.0.4.0 on



• IP PlanRelated object class: O2AREA - O2IFCRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup/O2AREA-10.0.1.0/O2IFC-lo11

Proceed with the following configuration to activate the OSPF on the networkinterfaces (VLAN interfaces).

• SCLI commands#iuiurup VRF VLAN interfacesset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 area 10.0.1.0 onset routing instance iuiurup node EIPU-2 ospf interfaceiuiurup_vl11 area 10.0.1.0 onset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 area 10.0.1.0 onset routing instance iuiurup node EIPU-2 ospf interfaceiuiurup_vl12 area 10.0.1.0 onset routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl13 area 10.0.1.0 onset routing instance iuiurup node EIPU-3 ospf interfaceiuiurup_vl13 area 10.0.1.0 onset routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl14 area 10.0.1.0 onset routing instance iuiurup node EIPU-3 ospf interfaceiuiurup_vl14 area 10.0.1.0 on#iub VRF VLAN interfacesset routing instance iub node EIPU-0 ospf interfaceiub_vl21 area 10.0.4.0 onset routing instance iub node EIPU-2 ospf interfaceiub_vl21 area 10.0.4.0 onset routing instance iub node EIPU-0 ospf interfaceiub_vl22 area 10.0.4.0 onset routing instance iub node EIPU-2 ospf interfaceiub_vl22 area 10.0.4.0 onset routing instance iub node EIPU-1 ospf interfaceiub_vl23 area 10.0.4.0 onset routing instance iub node EIPU-3 ospf interfaceiub_vl23 area 10.0.4.0 onset routing instance iub node EIPU-1 ospf interfaceiub_vl24 area 10.0.4.0 on


76 DN0974301 Issue: 02G

set routing instance iub node EIPU-3 ospf interfaceiub_vl24 area 10.0.4.0 on

e) Configure BFD Single-Hop for OSPF-enabled VLAN interfacesBFD Single-Hop is activated for OSPF-enabled VLAN interfaces to achieve fastrecovery of the neighbor/OSPF interface failures.#VRF iuiurupset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 bfd-detect-mult 3 bfd-monitoring enable bfd-rxinterval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-2 ospf interfaceiuiurup_vl11 bfd-detect-mult 3 bfd-monitoring enable bfd-rxinterval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 bfd-detect-mult 3 bfd-monitoring enable bfd-rxinterval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-2 ospf interfaceiuiurup_vl12 bfd-detect-mult 3 bfd-monitoring enable bfd-rxinterval 150 bfd-tx-interval 150#VRF iubset routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl13 bfd-detect-mult 3 bfd-monitoring enable bfd-rxinterval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-3 ospf interfaceiuiurup_vl13 bfd-detect-mult 3 bfd-monitoring enable bfd-rxinterval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl14 bfd-detect-mult 3 bfd-monitoring enable bfd-rxinterval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-2 ospf interfaceiuiurup_vl14 bfd-detect-mult 3 bfd-monitoring enable bfd-rxinterval 150 bfd-tx-interval 150

f) Configure OSPF parameters

g For each network instance, set the OSPF designated router election priority parametersproperly. It is not recommended to allow the EIPU nodes to become a designatedrouter.

Proceed with the following configuration.Set the external interfaces priority to 0.

• SCLI commands#VRF iuiurupset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 priority 0set routing instance iuiurup node EIPU-2 ospf interfaceiuiurup_vl11 priority 0set routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 priority 0set routing instance iuiurup node EIPU-2 ospf interfaceiuiurup_vl12 priority 0set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl13 priority 0set routing instance iuiurup node EIPU-3 ospf interfaceiuiurup_vl13 priority 0


Issue: 02G DN0974301 77

set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl14 priority 0set routing instance iuiurup node EIPU-3 ospf interfaceiuiurup_vl14 priority 0#VRF iubset routing instance iub node EIPU-0 ospf interfaceiub_vl21 priority 0set routing instance iub node EIPU-2 ospf interfaceiub_vl21 priority 0set routing instance iub node EIPU-0 ospf interfaceiub_vl22 priority 0set routing instance iub node EIPU-2 ospf interfaceiub_vl22 priority 0set routing instance iub node EIPU-1 ospf interfaceiub_vl23 priority 0set routing instance iub node EIPU-3 ospf interfaceiub_vl23 priority 0set routing instance iub node EIPU-1 ospf interfaceiub_vl24 priority 0set routing instance iub node EIPU-3 ospf interfaceiub_vl24 priority 0Set the directly connected VLAN interface cost to value 20 and VLANconnected to router connected to neighbor BCN module to value 40. This isenable the system to prefer the BCN module directly connected physical linkin normal conditions.

– SCLI commands#VRF iuiurupset routing instance iuiurup node EIPU-0 ospfinterface iuiurup_vl11 cost 20set routing instance iuiurup node EIPU-2 ospfinterface iuiurup_vl11 cost 40set routing instance iuiurup node EIPU-0 ospfinterface iuiurup_vl12 cost 40set routing instance iuiurup node EIPU-2 ospfinterface iuiurup_vl12 cost 20set routing instance iuiurup node EIPU-1 ospfinterface iuiurup_vl13 cost 20set routing instance iuiurup node EIPU-3 ospfinterface iuiurup_vl13 cost 40set routing instance iuiurup node EIPU-1 ospfinterface iuiurup_vl14 cost 40set routing instance iuiurup node EIPU-3 ospfinterface iuiurup_vl14 cost 20#VRF iubset routing instance iub node EIPU-0 ospf interfaceiub_vl21 cost 20set routing instance iub node EIPU-2 ospf interfaceiub_vl21 cost 40set routing instance iub node EIPU-0 ospf interfaceiub_vl22 cost 40set routing instance iub node EIPU-2 ospf interfaceiub_vl22 cost 20set routing instance iub node EIPU-1 ospf interfaceiub_vl23 cost 20


78 DN0974301 Issue: 02G

set routing instance iub node EIPU-3 ospf interfaceiub_vl23 cost 40set routing instance iub node EIPU-1 ospf interfaceiub_vl24 cost 40set routing instance iub node EIPU-3 ospf interfaceiub_vl24 cost 20

– IP PlanRelated object class:O2AREA - O2IFCRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup/O2AREA-10.0.1.0/O2IFC-iuiurup_vl11

– electionPriority = 0– ospfCost = 2– bfdDetectMonitoring = 1 (enabled)– bfdDetectMult = 3– bfdRxInterval = 150– bfdTxInterval = 150

10 OSPF authentication (OPTIONAL)In case the OSPF authentication (here MD5 authentication) is applied then insert thefollowing commands with proper secrets. The example commands are shown below.set routing instance iuiurup node EIPU-0 ospf interface loauthtype md5 key 1 secret passwd123

set routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 authtype md5 key 1 secret passwd123

set routing instance iub node EIPU-0 ospf interface loauthtype md5 key 1 secret passwd123

set routing instance iub node EIPU-0 ospf interface iub_vl21authtype md5 key 1 secret passwd123

11 Configure user plane resources, IP-based route configurationThe following steps describe the Iu-PS interface configuration as an example.

• SCLI commandsadd networking ipbr ipbr-id 1 route-bandwidth 0 committed-bandwidth 0 committed-dcn-bandwidth 0 committed-sig-bandwidth 0 ipbr-name iupsipbr-1 scheduler-type none

If a user plane non-load sharing configuration is applied, proceed as follows, assigna single IP address to the IP-based route 1 for the Iu-PS user plane source IPaddress selection.add networking ipro ipbr-id 1 ip-address 10.1.1.1 iface lo5owner /QNUP-0 vrf iuiurup

If a user plane IP Based Route load sharing configuration is applied, proceed asfollows, assign several IP addresses to the IP-based route 1 for the Iu-PS user planesource IP address selection.add networking ipro ipbr-id 1 ip-address 10.1.1.1 iface lo5 owner /QNUP-0 vrf iuiurup

add networking ipro ipbr-id 1 ip-address 10.1.1.2 iface lo5 owner


Issue: 02G DN0974301 79

/QNUP-1 vrf iuiurup

add networking ipro ipbr-id 1 ip-address 10.1.1.3 iface lo5 owner /QNUP-2 vrf iuiurup


• IP PlanRelated object class: IPBR, IPRORNC-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-lo5

• vrf = iuiurup

RNC-xx/IP-1/OWNER-QNUP-1/IPRO-1-10.1.1.1-lo5 (… more instances configuredwith IPBR load sharing)

• vrf = iuiurup

The following steps describe the Iu-CS interface configuration as an example.

• SCLI commandsadd networking ipbr ipbr-id 1 route-bandwidth 0 committed- bandwidth 0 committed-dcn-bandwidth 0 committed-sig-bandwidth 0 ipbr-name iucsipbr-2 scheduler-type noneWith user plane IP Based Route load sharing configuration proceed as follows.add networking ipro ipbr-id 1 ip-address 10.1.1.17 iface lo5 owner /QNUP-0 vrf iuiurup




The following steps describe the Iur interface configuration as an example.

• SCLI commandsipbr ipbr-id 1 route-bandwidth 0 committed-bandwidth 0 committed- dcn-bandwidth 0 committed-sig-bandwidth 0 ipbr-name iuripbr-3 scheduler-type none


80 DN0974301 Issue: 02G

With user plane IP Based Route load sharing configuration proceed as follows.add networking ipro ipbr-id 1 ip-address 10.1.1.33 iface lo5 owner /QNUP-0 vrf iuiurup




The following steps describe the Iub interface configuration towards a single BTS asan example. The IP Based Route scheduling is provided and therefore the IP BasedRoute load sharing is not applied in this case.

• SCLI commandsadd networking ipbr ipbr-id 1 route-bandwidth 1000 committed- bandwidth 500 committed-dcn-bandwidth 1 committed-sig-bandwidth 1 ipbr-name iub-wbts-123 scheduler-type virtualQueue ifc-nrthsdpa IFCWith user plane IP Based Route load sharing configuration proceed as follows.add networking ipro ipbr-id 1 ip-address 10.1.0.1 iface lo9 owner /QNUP-0 vrf iub

12 Configure multi-hop path monitoring (OPTIONAL)The following commands provide a reference for the multi-hop path monitoringconfiguration towards the BTS. The multi-hop path monitoring can be appliedtowards BTS, neighbor RNC or core network element. In this example the BFD Multi-Hop is configured towards the BTS. The IP Based Route reference related to theBTS is added to BFD configuration. With this setup the new connection setups willbe blocked towards the BTS in case the BFD session state is down.add networking monitoring bfd session /QNUP-0 name bts-1srcaddr 10.1.0.1 dstaddr 10.2.0.1 reference-id 1 detect-mult 3rx-interval 1000 tx-interval 1000

13 Configure control plane resourcesThe Iu/Iur control plane resources configuration consist of a generic mcRNCresources and the interface and neighbor element specific part setup. Typically onemcRNC contains one SAP (Service Access Point) instance and one AS (ApplicationServer) instance. This is in case the mcRNC operators within one signaling network.Further the example configuration contains one SCCP profile and logical interfacespecific SCTP profiles. Having interface specific SCTP profiles makes it possible toadjust the SCTP specific profile settings in case needed without affecting otherlogical interfaces.For Iu control plane configuration, it is recommended to use at least four EIPUs forthe load-sharing and redundancy of the connection towards the single CN element.Additionally, SCTP multi-homing is recommended for the SCTP association networklevel redundancy provisioning. The detailed number of EIPU units, that is required fortotal control plane traffic load sharing purposes, must be planned according todimensioning guidelines, see Dimensioning WCDMA RAN Access Network (RNC


Issue: 02G DN0974301 81

and Transport). In the configuration examples, two EIPUs are used for terminatingthe SIGTRAN connections and the SCTP multi-homing is enabled.Proceed with the following configuration:

a) Configuring SCCP timer profilesAn SCCP timer profile is used to configure SCCP timer-specific parameters.The user can administer the SCCP timer configuration for different networksusing the same SCLI command. The network type parameter in the commandallows users to create network-specific timer configurations. To apply the createdtimer profile at the stack, users must associate the profile with a particular serviceaccess point using the add/set command of the service access point.

g Consider the following before adding or administering SCCP timer profiles in SAP:

• For different SAPs with the same network types, ensure that same SCCP timerprofile is used. However if different SAPs have the same network type but differentSCCP timer profiles, then the expected behavior is that the latest updated timerprofile is enforced.

• The t-iar timer value in the local network element must always be in multiples (atleast thrice) of the highest t-ias timer value configured among all the remotenetwork elements.

• The t-ias timer value in the local network element must always be lower thanone-third of the lowest t-iar timer value configured among all the remote networkelements.

Configure the SCCP timer profiles with the following command:add signaling sccp sccp-timer-profile name sccpprofile1network-type itu t-a 100 t-congestion 5 t-connect 80 t-d 5t-guard 1380 t-iar 700 t-ias 300 t-interval 50 t-reassembly10 t-release 10 trepeat-release 10 t-reset 10For more information on SCCP timer profiles, their configurations, commandsyntax, and parameters, see Configuring SS7 Signaling Transport over IP forMulticontroller RNC (chapter Configuring SCCP timer profiles). In theconfiguration examples within this document, the default timer profile is appliedfor all created SAP instances.

b) Create Services Access PointThe Services Access Point (SAP) is used to configure a particular signalingnetwork at the stack. The SAP identifies the network indicator and variant of anode in the SIGTRAN network. A node can have multiple SAPs configured.Multiple SAPs can be added with the same network indicator.add signaling service-access-point id 1 name SAPRNC1network-appearance 1 network-indicator NA0 network-type itusccp-timer-profile-name sccpprofile1

c) Create local Application ServerA local Application Server (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 isidentified with a routing context between two peers. A Local AS is required for theIPSP configuration.add signaling ss7 local-as id 1 name LASRNC1 routingcontext1 routing-key-dpc 310 service-access-point-name SAPRNC1traffic-mode loadshare

Iu-PS interface

a) Add SCTP profile for the Iu-PS interfaceadd signaling sctp-profile from-template SS7 name iups

b) Create remote Application Server


82 DN0974301 Issue: 02G

Ensure that the Routing Context (RC) value configured for the remote AS in thelocal network element is same as that configured in the remote network element.A remote AS is a logical entity serving a specific Routing Key. The AS isidentified with a routing context between two peers (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-modeloadshare

c) Create M3UA associationSingle-mode exchange is recommended for M3UA associations. An M3UAassociation object includes a local Application Server Process (ASP) and aremote ASP.add signaling ss7 association id 21 local-as-name LASRNC1communication-type ipsp local-ip-addr 10.1.8.17 local-ipaddr 10.1.8.145 local-client-port 49225 remote-as-nameSGSN1 remoteip-addr 10.8.0.1 remote-ip-addr 10.8.1.1remote-port 2905 node /EIPU-0 vrf-name iuiurcp role clientexchange-mode single sctpprofile iupsadd signaling ss7 association id 22 local-as-name LASRNC1communication-type ipsp local-ip-addr 10.1.8.18 local-ip-addr 10.1.8.146 local-client-port 49225 remote-as-nameSGSN1 remoteip-addr 10.8.0.2 remote-ip-addr 10.8.1.2remote-port 2905 node /EIPU-1 vrf-name iuiurcp role clientexchange-mode single sctp-profile iupsadd signaling ss7 association id 23 local-as-name LASRNC1communication-type ipsp local-ip-addr 10.1.8.19 local-ip-addr 10.1.8.147 local-client-port 49225 remote-as-nameSGSN1 remoteip-addr 10.8.0.1 remote-ip-addr 10.8.1.1remote-port 2905 node /EIPU-2 vrf-name iuiurcp role clientexchange-mode single sctpprofile iupsadd signaling ss7 association id 24 local-as-name LASRNC1communication-type ipsp local-ip-addr 10.1.8.20 local-ip-addr 10.1.8.148 local-client-port 49225 remote-as-nameSGSN1 remoteip-addr 10.8.0.2 remote-ip-addr 10.8.1.2remote-port 2905 node /EIPU-3 vrf-name iuiurcp role clientexchange-mode single sctp-profile iups

d) Create SCCP own point codeadd signaling sccp own-point-code id 1 local-as-nameLASRNC1

e) Create SCCP destination point codeadd signaling sccp destination-point-code id 4 remote-asname SGSN1

f) Create SCCP subsystemadd signaling sccp subsystem id 1 name SSN310510 pointcode-name LASRNC1 ssn 142add signaling sccp subsystem id 2 name SSN500310 pointcode-name SGSN1 ssn 142

g) Create SCCP concerned subsystemSCCP Concerned Subsystem is informed about a state change in the affectedsubsystem.add signaling sccp concerned-subsystem name CSS1 subsystem-name SSN310510 affected-subsystem-name SSN500310

h) Create SCCP concerned point codeThe SCCP concerned point code is informed about an affected subsystem statechange.


Issue: 02G DN0974301 83

add signaling sccp concerned-point-code name CPC1pointcode-name SGSN1 affected-subsystem-name SSN310510

i) Enable associationsset signaling ss7 association admin-state enabled id 21set signaling ss7 association admin-state enabled id 22

For more information, see Configuring SS7 Signaling Transport over IP forMulticontroller RNC.Iu-CS interface

a) Add SCTP profile for the Iu-CS interfaceadd signaling sctp-profile from-template SS7 name iucs

b) Create remote ASEnsure that the Routing Context (RC) value configured for the remote. AS in thelocal network element is same as that configured in the remote network element.add signaling ss7 remote-as id 2 name MSS1communicationtype ipsp pending-timer 3 routing-context 2001routingkey-dpc 510 service-access-point-name SAPRNC1trafficmode loadshare

c) Create M3UA associationSingle-mode exchange is recommended for M3UA associations.An M3UA association object includes one local Application Server Process (ASP)and one remote ASP. When a command is executed, the remote ASP is set bydefault to management blocking. Management blocking of the remote ASP isremoved when the association is enabled.add signaling ss7 association id 51 local-as-name LASRNC1communication-type ipsp local-ip-addr 10.1.8.49 local-ip-addr 10.1.8.177 local-client-port 49225 remote-as-name MSS1remote-ip-addr 10.8.5.1 remote-ip-addr 10.8.6.1 remote-port2905 node /EIPU-0 vrf-name iuiurcp role client exchange-mode single sctp-profile iucsadd signaling ss7 association id 52 local-as-name LASRNC1communication-type ipsp local-ip-addr 10.1.8.50 local-ip-addr 10.1.8.178 local-client-port 49225 remote-as-name MSS1remote-ip-addr 10.8.5.2 remote-ip-addr 10.8.6.2 remote-port2905 node /EIPU-1 vrf-name iuiurcp role client exchange-mode single sctp-profile iucsadd signaling ss7 association id 53 local-as-name LASRNC1communication-type ipsp local-ip-addr 10.1.8.51 local-ip-addr 10.1.8.179 local-client-port 49225 remote-as-name MSS1remote-ip-addr 10.8.5.1 remote-ip-addr 10.8.6.1 remote-port2905 node /EIPU-0 vrf-name iuiurcp role client exchange-mode single sctp-profile iucsadd signaling ss7 association id 54 local-as-name LASRNC1communication-type ipsp local-ip-addr 10.1.8.52 local-ip-addr 10.1.8.180 local-client-port 49225 remote-as-name MSS1remote-ip-addr 10.8.5.2 remote-ip-addr 10.8.6.2 remote-port2905 node /EIPU-1 vrf-name iuiurcp role client exchange-mode single sctp-profile iucs


e) Create SCCP destination point codeadd signaling sccp destination-point-code id 5 remote-asname MSS1


84 DN0974301 Issue: 02G

f) Create SCCP subsystemadd signaling sccp subsystem id 1 name SSN310510 pointcode-name LASRNC1 ssn 142add signaling sccp subsystem id 2 name SSN510310 pointcode-name MSS1 ssn 142

g) Create SCCP concerned subsystemSCCP Concerned Subsystem is informed about a state change in the affectedsubsystem.add signaling sccp concerned-subsystem name CSS2 subsystem-name SSN310510 affected-subsystem-name SSN510310

h) Create SCCP concerned point codeThe SCCP concerned point code is informed about an affected subsystem statechange.add signaling sccp concerned-point-code name CPC2pointcode-name MSS1 affected-subsystem-name SSN310510


For more information, see Configuring SS7 Signaling Transport over IP forMulticontroller RNC.Iur interface

a) Add SCTP profile for the Iur interfaceadd signaling sctp-profile from-template SS7 name iur

b) Create remote ASEnsure that the Routing Context (RC) value configured for the remote AS in thelocal network element is same as that configured in the remote network element.A remote AS is a logical entity serving a specific Routing Key. The AS isidentified with a routing context between two peers (IPSP-IPSP).add signaling 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-modeloadshare

c) Create M3UA associationSingle-mode exchange is recommended for M3UA associations, M3UAassociation object includes one local Application Server Process (ASP) and oneremote ASP. When a command is executed, the remote ASP is set by default tomanagement blocking. Management blocking of the remote ASP is removedwhen the association is enabled.add signaling ss7 association id 81 local-as-name LASRNC1communication-type ipsp local-ip-addr 10.1.8.81 localipaddr10.1.8.209 local-client-port 49225 remote-as-name DRNC1remoteip-addr 10.8.8.1 remote-ip-addr 10.8.9.1 remote-port2905 node /EIPU-0 vrf-name iuiurcp role client exchange-mode single sctp-profile iuradd signaling ss7 association id 82 local-as-name LASRNC1communication-type ipsp local-ip-addr 10.1.8.82 localipaddr10.1.8.210 local-client-port 49225 remote-as-name DRNC2remoteip-addr 10.8.8.2 remote-ip-addr 10.8.9.2 remote-port2905 node /EIPU-1 vrf-name iuiurcp role client exchange-mode single sctp-profile iur



Issue: 02G DN0974301 85

e) Create SCCP destination point codeadd signaling sccp destination-point-code id 6 remote-asname DRNC2

f) Create SCCP subsystemadd signaling sccp subsystem id 1 name SSN310520pointcodename LASRNC1 ssn 143add signaling sccp subsystem id 2 name SSN520310pointcodename SGSN1 ssn 143

g) Create SCCP concerned subsystemSCCP Concerned Subsystem is informed about a state change in the affectedsubsystem.add signaling sccp concerned-subsystem name CSS3subsystemname SSN310520 affected-subsystem-name SSN520310

h) Create SCCP concerned point codeadd signaling sccp concerned-point-code name CPC3pointcodename DRNC2 affected-subsystem-name SSN310520


14 Check and configure QoS related resources.In most cases, using the default QoS values is sufficient, but depending on networkarchitecture and further QoS constraints, the values need to be reviewed andpossibly adjusted.For more information, see Configuring QoS.

15 Configure the Radio Network layer information.

• Iu-PS interface

a) Start the mcRNC OMS Element Manager and launch the Parameter Editortool, or alternatively, use the RNW Plan from NetAct

b) Select Configuration Management → Network Topology → Tree Viewc) Select the RNC in the Topology Treed) Click the drop-down menu next to the RNCe) If the IPQM object is not yet created, create it by selecting Create -> new

IPQM. Existing IPQM objects can also be used.

– Use the default DSCP values within the IPQM. The existing IPQM can beused 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 must refer to the IPQM object created in step e.– The IP-based route reference for the Iu-PS user plane transport bearer

setup is retrieved based on the peer IP address signaled in The RANAPRAB assignment request.


86 DN0974301 Issue: 02G

The IP-based route identification must refer to the already-created IP-based route instance in the mcRNC. The IP-based route instance is usedfor the mcRNC user plane source IP address selection, where theselected IP address also defines the HW unit terminating the IP transportbearer in the mcRNC.

– In case a single IP-based route entity is used for all the Iu-PS user planetraffic, the following mapping is recommended: 0.0.0.0/0 -> IP-basedroute id 1. At least one destination IP subnet definition is required (atleast one IUPSIP instance) and the default value 0.0.0.0/0 is sufficient inmost of the cases.

– In case the detailed destination IP-address-based references arerequired (normally only the case if dedicated traffic shaping or CACtowards certain core nodes is needed), related entries such as10.7.0.0/24 -> IP-based route id 1(netmask /24, 255.255.255.0) can beconfigured.The IUPS object instance might contain several IUPSIPinstances. Such a configuration is necessary only if separate mcRNC IPaddresses are required for the connection towards a certain destinationcore network peer element.The following is a simple IUPS configuration where all the GTP tunnelsare 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

• Iu-CS interface

a) Start the mcRNC OMS Element Manager and launch the Parameter Editortool, or alternatively, use the RNW Plan from NetAct

b) Select Configuration Management → Network Topology → Tree Viewc) Select the RNC in the Topology Treed) Click the drop-down menu next to the RNCe) If the IPQM object is not yet created, create it by selecting Create -> new

IPQM. Existing IPQM objects can also be used.

– Use default DSCP values within the IPQM. Only one IPQM is required forall the IP Iu interfaces by default. The existing IPQM can be used if thesame DSCP mapping applies.

– Only one IPQM object is needed for all the IP-based Iu interfaces bydefault. The default values apply for the minimum default port.

f) IP configuration for the IUCS and IUCSIP objects


Issue: 02G DN0974301 87

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

– The IP-based route reference for the Iu-CS user plane transport bearersetup is retrieved based on the peer IP address signaled at RANAP RABassignment.The IP-based route identification has to refer to the already-created IP-based route instance in the mcRNC. IP-based route instance is used forthe mcRNC user plane source IP address selection, where the selectedIP address also defines the HW unit terminating the IP transport bearer inthe mcRNC.

– In case a single IP-based route entity is used for all the Iu-CS user planetraffic, the following mapping is recommended: 0.0.0.0/0 -> IP-basedroute id 2. At least one destination IP subnet definition is required (atleast one IUCSIP instance) and a value 0.0.0.0/0 is sufficient in most ofthe cases.

– In case detailed destination IP address based references are required(normally only the case if dedicated traffic shaping towards certain corenodes is needed), related entries such as 10.7.0.0/24 -> IP-based routeid 2 (netmask /24, 255.255.255.0) can be configured. The IUCS objectinstance might contain several IUCSIP instances. Such a configuration isnecessary only if separate mcRNC IP addresses are required for theconnection towards a certain destination core network peer element.

The following is a simple IUCS configuration where all the connections arecreated through the IP-based route instance 2.


– 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 = 2

• Iur interfacea) Start the mcRNC OMS Element Manager and launch the Parameter Editortool, or alternatively, use the RNW Plan from NetActb) Select Configuration Management → Network Topology → Tree Viewc) Select the RNC in the Topology Treed) Click the drop-down menu next to the RNCe) If the IUR object is not yet created, create it by selecting Create -> new IPQM.Existing IUR objects can also be used.

– The IP-based route identification has to refer to the already-created IP-basedroute instance in the mcRNC. IP-based route instance is used for the mcRNCuser plane source IP address selection, where the selected IP address also


88 DN0974301 Issue: 02G

defines the HW unit terminating the IP transport bearer in the mcRNC.Thefollowing is a simple IUR configuration where all the connections are createdthrough the IP-based route instance 3.


– IUR-1

• SignPointCode = 520 (SPC of the peer element, neighboring RNC)• IPBasedRouteIdIur = 3

• Iub interface

a) Start the mcRNC OMS Element Manager and launch 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.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. Theattributes are used to control the NBAP link RNC own IP addressselection and IPNB creation phase.If any of the IP addresses (tied to QNUIB recovery groups) haveconnectivity to the BTS, the default 0.0.0.0/0 reference can be applied. Inthis case the system freely selects the NBAP link SCTP/IP termination. Ifonly a certain EIPU unit has connectivity to the BTS, then the Iub controlIP address selection can be limited with the subnet definition. Even aspecific address can be referred with /32 value if needed.

4. In the D-NBAP List enter 1 for the Communication Control Port ID; theSCTP Port Number for D-NBAP is automatically calculated.

f) Create or modify the WBTS object so that it contains the IPNB reference andIP 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 routeconfigured in corresponding step.

– Default values can be used in most cases for MinUDPPortIub,ToAWEOffsetNRTDCHIP, ToAWEOffsetRTDCHIP,ToAWSOffsetNRTDCHIP, and ToAWSOffsetRTDCHIP.

– With QoS settings the values have to be filled in according to theplanning for DSCPMedDCH, DSCPLow, DSCPHigh, DSCPMedHSPA,HSDPAULCToDSCP, HSUPADLCToDSCP.


Issue: 02G DN0974301 89

3.3 Configuring mcRNC OSPF SiSo, VRF, 10GE, 1GEwith LAG and dedicated EIPUPurpose

To configure the Iu, Iur and Iub interface with the OSPF site solution, Virtual Routing andForwarding (VRF), 10GE and 1GE interfaces and Ethernet Link Aggregation (LAG)functionalities.


• RAN1510 OSPF for Redundancy• RAN2256 Ethernet Link Aggregation for mcRNC



The configuration example is presented with mcRNC capacity step s3 and withdedicated EIPU setup. The dedicated EIPU setup means that certain EIPU nodesterminate the traffic from Iu and Iur logical interfaces while certain EIPU nodes handlethe Iub. Here the Iu/Iur connectivity is configured with 10GE interfaces while the Iubdirection is configured with 1GE and Ethernet Link Aggregation. The dedicated EIPUconfiguration can be applied to gradually take the 10GE interfaces in use or in caseoperator has separate physical routers to different domains.

The example configuration can be applied for planning and configuring bigger capacitysteps with using the presented design pattern for further needed EIPU nodes. Theconfiguration and connectivity principles apply as per EIPU pair basis.

The Virtual Routing and Forwarding instances are logically separate routing processeswithin the EIPU with separate routing tables and interfaces. VRF instances are used tokeep routing information, IP addressing, and IP interfaces logically separated betweendifferent logical interfaces. With OSPF SiSo the Iu/Iur control plane, managed with staticroutes, is separated from the user plane resources routing that is managed dynamicallywith OSPF.

The VRF implementation can be applied for Iu/Iur/Iub user plane and control plane. Thetotal amount of the VRFs should be planned to be as low as possible in order to keep theoverall configuration complexity low. For the Iu/Iur control plane, both IP addresses of theSCTP multi-homed association have to belong to the same VRF. The O&M functionswithin the CFPU are supported only within the default VRF (VRF-0).


• VRFs are configured in EIPU nodes to logically separate the routing functions and IPaddressing

• Simplified static route configuration can be applied for the user-plane connections• One VLAN interface can belong to only one VRF


• L3 type of site solution with dynamic routing• OSPF manages the user plane routing• Iu/Iur control plane with SCTP Multi-Homing is managed with static routes


90 DN0974301 Issue: 02G

• Supports 1GE and 10GE interfaces

Restrictions:

O&M-related functions in the CFPU unit belong to default VRF only. Iu/Iur control planeIP addresses of a single SCTP multi-homed association can only belong to one VRF.Incoming traffic towards the IP address within the VRF has to come in via the VLANinterface tied to the same VRF.

g IP addresses and subnets given in the document are just examples and must be setaccording to the actual network plan.

The configuration examples in the instructions are based on the IP addressing presentedin Figure Network configuration for mcRNC OSPF SiSo with 10GE LAG and VRF. VRFsare applied for different domains: Iu and Iur user plane, Iu and Iur control plane and Iubcontrol and user plane.

Figure 20 Network configuration for mcRNC OSPF SiSo with 10GE, LAG and VRF

The detailed configuration for the Iub interface is presented in Figure 20: Networkconfiguration for mcRNC OSPF SiSo with 10GE, LAG and VRF. The application IPaddresses for the Iub user plane and control plane are bound to QNUP and QNIUBinstances and assigned to loopback interface of the corresponding VRF. Separate IP


Issue: 02G DN0974301 91

addresses are applied for Iub user plane and Iub control plane in order to allowindependent failure actions for the services. The related IP addresses and VLANinterfaces belong to “iub” VRF with numeric id 21.

Figure 21 Iub configuration for mcRNC OSPF SiSo with 10GE, LAG and VRF

Detailed figure for Iu-PS, Iu-CS and Iur user plane IP addressing is presented in Figure21: Iub configuration for mcRNC OSPF SiSo with 10GE, LAG and VRF. Separate IPaddresses are applied for the Iu-CS, Iu-PS and Iur user plane traffic IP layer termination.The related IP addresses and VLAN interfaces belong to “iuiurup” VRF with numeric id 5.


92 DN0974301 Issue: 02G

Figure 22 Iu/Iur User Plane configuration for mcRNC OSPF SiSo with 10GE, LAGand VRF

The Iu-PS, Iu-CS and Iur control plane SCTP associations and related IP addressing ispresented in Figure Iu/Iur User Plane configuration for mcRNC OSPF SiSo with LAG andVRF. The SCTP IP addresses are configured to EIPU backplane cfeigw interfaces.Certain EIPU nodes are selected to work as gateways for the Iu/Iur control plane traffic.The related IP addresses and VLAN interfaces belong to “iuiurcp” VRF with numeric id 5.The Iu and Iur control plane configuration principles are similar in both VRRP/HSRP andOSPF site solutions.


Issue: 02G DN0974301 93

Figure 23 Iu/Iur Control Plane configuration for mcRNC OSPF SiSo with 10GE, LAGand VRF


The mcRNC site configuration applied VLANs for logical traffic separation and VRFs forlogical routing functions separation. With VRFs and static routes it is possible to apply forexample a default route configuration for the user plane connections in case all the userplane goes out via the same gateway without affecting for example to Iu/Iur control planerequiring a specific route entries.

Ethernet Link Aggregation is applied to group 1GE interfaces into a higher bandwidthlogical interface allowing simplified IP addressing and easier load sharing over severalphysical links from EIPU node to router. All EIPU nodes terminate traffic from all logicalinterfaces (shared EIPU scheme).

Multicontroller RNC



94 DN0974301 Issue: 02G


– VLAN11 10.0.1.0/28– VLAN12 10.0.1.16/28




– VLAN21 10.0.4.0/28– VLAN22 10.0.4.16/28

Application IP addresses are assigned to a certain recovery group (RG) instance, whichprovides the redundancy scheme for hardware and software failures. With OSPF sitesolution the user plane IP addresses are configured to loopback interface of thecorresponding VRF instance. The IP address follows the active Recovery Unit (RU) ofthe QNUP RG. The Iub related application IP addresses are presented in Table Iubcontrol and user plane IP addresses. The Iu and Iur user plane addresses are presentedin Table Iu and Iur user plane IP addresses.


Recovery Group

Iub


QNUP-3 10.1.0.2


QNUP-3 10.1.0.66


Recovery Group

Iu-PS

Iu-CS

Iur

QNUP-0 10.1.1.1 10.1.1.17 10.1.1.33

QNUP-1 10.1.1.2 10.1.1.18 10.1.1.34


– SCTP association-1, 10.1.8.2/28, 10.1.8.145/28


Issue: 02G DN0974301 95

– SCTP association-2, 10.1.8.18/28, 10.1.8.130/28– SCTP association-3, 10.1.8.19/28, 10.1.8.147/28– SCTP association-4, 10.1.8.20/28, 10.1.8.148/28





OSPF for site routers/switches (user plane traffic VRFs):

Two OSPF areas associated to separate VRFs are applied for Iu/Iur user plane and Iub.


Before you start

The mcRNC and site routers have been installed and all required connections have beenestablished. The site solution with OSPF is described in mcRNC Site Solution based onJuniper with OSPF using 10 Gigabit Ethernet connectivity and mcRNC Site Solutionbased on Juniper with OSPF using 1GE and 10GE connectivity documents.

StepsBefore you start

g Before starting a new IP layer configuration, check the existing IP layer configuration.Use the show networking ether and show networking address SCLIcommands to show the current settings of interfaces. If configuring the mcRNC usingthe IP plan, create and activate a plan in the mcRNC in order to have a basicconfiguration as a starting point for further modifications.

g To avoid IP layer fragmentation an MTU size of 1560 octets is recommended to be usedfor the Iu-PS transport. For more information on MTU, see WCDMA RAN IP Transport.

1 Configure the VRF interface

• SCLI commands

add networking vrf name iuiurup id 5



• IP Plan


96 DN0974301 Issue: 02G

Related object class: VRFRNC-xx/IP-1/VRF-iuiurup

• id = 5

2 Configure the physical interfacesPhysical network interfaces are assigned to a certain EIPU node, if not yetconfigured. The mcRNC default egress queue set rncdefault has to be assigned tothe physical interface for proper default egress scheduling weights configuration.

• SCLI commands

# Configure 10GE ports## Create shared 10GE portsadd networking switch port-group name sfp11-bcn1 port LMP-1-1-1:sfp11

add networking switch port-group name sfp11-bcn2 port LMP-1-2-1:sfp11

Assign BCN-1 shared 10GE port to EIPU nodesadd networking ether /EIPU-0 iface eth_b1 port sfp11-bcn1outqset rncdefault mtu 1560

add networking ether /EIPU-1 iface eth_b1 port sfp11-bcn1outqset rncdefault mtu 1560

# Assign BCN-2 shared 10GE port to EIPU nodesadd networking ether /EIPU-0 iface eth_b2 port sfp11-bcn2outqset rncdefault mtu 1560

add networking ether /EIPU-1 iface eth_b2 port sfp11-bcn2outqset rncdefault mtu 1560

# Configure 1GE portsadd networking ether /EIPU-2 iface ethsfp17_r1 port sfp17outqset rncdefault

add networking ether /EIPU-2 iface ethsfp18_r1 port sfp18outqset rncdefault







g Rate limit is inherited from the interface speed directly if no explicit value is given.


Issue: 02G DN0974301 97

3 Configure the Ethernet Link Aggregation, LAG interfaces

• SCLI commands

# Configure LAG interfacesadd networking linkaggr /EIPU-2 iface lag1 slave ethsfp17_r1slave ethsfp18_r1 outqset rncdefault

add networking linkaggr /EIPU-2 iface lag2 slave ethsfp19_r1slave ethsfp20_r1 outqset rncdefault



4 Configure VLAN interfaces within LAG interfacesThe VLAN interface is created for a certain physical interface/LAG interface with areference to its name. The VLAN ids and the VLAN interface names have to beplanned and configured accordingly.

• SCLI commands#vlan 11-14, iu iur user planeadd networking instance iuiurup vlan /EIPU-0 realifaceeth_b1 vid 11 vlaniface iuiurup_vl11 mapping vlandscptopcpmtu 1560add networking instance iuiurup vlan /EIPU-0 realifaceeth_b2 vid 12 vlaniface iuiurup_vl12 mapping vlandscptopcpmtu 1560add networking instance iuiurup vlan /EIPU-1 realifaceeth_b1 vid 13 vlaniface iuiurup_vl13 mapping vlandscptopcpmtu 1560add networking instance iuiurup vlan /EIPU-1 realifaceeth_b2 vid 14 vlaniface iuiurup_vl14 mapping vlandscptopcpmtu 1560#vlan 15-20, iu iur control planeadd networking instance iuiurcp vlan /EIPU-0 realifaceeth_b1 vid 15 vlaniface iuiurcp_vl15 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-1 realifaceeth_b2 vid 16 vlaniface iuiurcp_vl16 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-0 realifaceeth_b1 vid 17 vlaniface iuiurcp_vl17 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-1 realifaceeth_b2 vid 18 vlaniface iuiurcp_vl18 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-0 realifaceeth_b1 vid 19 vlaniface iuiurcp_vl19 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-1 realifaceeth_b2 vid 20 vlaniface iuiurcp_vl20 mapping vlandscptopcp#vlan 21-24, iub control and user planeadd networking instance iub vlan /EIPU-2 realiface lag1 vid21 vlaniface iub_vl21 mapping vlandscptopcpadd networking instance iub vlan /EIPU-2 realiface lag2 vid22 vlaniface iub_vl22 mapping vlandscptopcpadd networking instance iub vlan /EIPU-3 realiface lag1 vid23 vlaniface iub_vl23 mapping vlandscptopcp


98 DN0974301 Issue: 02G

add networking instance iub vlan /EIPU-3 realiface lag2 vid24 vlaniface iub_vl24 mapping vlandscptopcp


• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mapping = vlandscptopcp• mtu = 1560• realiface = lag1• vid = 11• vrf = iuiurup

5 Configure the IP addresses of the VLAN interfacesProceed with the following configuration for fixed VLAN interface IP addressconfiguration.

g The interface name refers to created physical interface or LAG interface. If VLANs areused, the network interface IP addresses are tied to VLAN interfaces.

• SCLI commands#VLANs 11-14, iu iur user planeadd networking instance iuiurup address dedicated /EIPU-0iface iuiurup_vl11 ip-address 10.0.1.2/28add networking instance iuiurup address dedicated /EIPU-0iface iuiurup_vl12 ip-address 10.0.1.18/28add networking instance iuiurup address dedicated /EIPU-1iface iuiurup_vl13 ip-address 10.0.1.34/28add networking instance iuiurup address dedicated /EIPU-1iface iuiurup_vl14 ip-address 10.0.1.50/28#VLANs 15-20, iu iur control planeadd networking instance iuiurcp address dedicated /EIPU-0iface iuiurcp_vl15 ip-address 10.1.8.2/28add networking instance iuiurcp address dedicated /EIPU-1iface iuiurcp_vl16 ip-address 10.1.8.130/28add networking instance iuiurcp address dedicated /EIPU-0iface iuiurcp_vl17 ip-address 10.1.8.34/28add networking instance iuiurcp address dedicated /EIPU-1iface iuiurcp_vl18 ip-address 10.1.8.162/28add networking instance iuiurcp address dedicated /EIPU-0iface iuiurcp_vl19 ip-address 10.1.8.66/28add networking instance iuiurcp address dedicated /EIPU-1iface iuiurcp_vl20 ip-address 10.1.8.194/28#VLANs 21-24, iub user and control planeadd networking instance iub address dedicated /EIPU-2 ifaceiub_vl21 ip-address 10.0.4.3/28add networking instance iub address dedicated /EIPU-2 ifaceiub_vl22 ip-address 10.0.4.19/28add networking instance iub address dedicated /EIPU-3 ifaceiub_vl23 ip-address 10.0.4.35/28add networking instance iub address dedicated /EIPU-3 ifaceiub_vl24 ip-address 10.0.4.51/28


Issue: 02G DN0974301 99

• IP Plan

Related object class:ADDRRNC-xx/IP-1/OWNER-EIPU-0/ADDR-10.0.2.2-iuiurcp_vl17

• mask=28• vrf=iuiurcp

6 Configure application IP addresses for user planeWith OSPF site solution Iu/Iur/Iub user plane and Iub control plane application IPaddresses are assigned to loopback interfaces of the corresponding VRF instance.The application IP address is present in the node/unit that is running the service atthe time (active recovery unit, RU).

g The role attribute is a free form character string that can be configured optionally. Therole attribute can be defined to keep the IP addressing usage clearly visible in order tosimplify the system maintenance. For the Iu-PS user plane addresses apply, forexample, role “iupsup”.

Proceed with the following configuration.

• SCLI commands#Iu-PS user plane IP addresses, VRF iuiurupadd networking instance iuiurup address dedicated /QNUP-0iface lo ip-address 10.1.1.1/32 role iupsupadd networking instance iuiurup address dedicated /QNUP-1iface lo ip-address 10.1.1.2/32 role iupsup#Iu-CS user plane IP addresses, VRF iuiurupadd networking instance iuiurup address dedicated /QNUP-0iface lo ip-address 10.1.1.17/32 role iucsupadd networking instance iuiurup address dedicated /QNUP-1iface lo ip-address 10.1.1.18/32 role iucsup#Iur user plane IP addresses, VRF iuiurupadd networking instance iuiurup address dedicated /QNUP-0iface lo ip-address 10.1.1.33/32 role iurupadd networking instance iuiurup address dedicated /QNUP-1iface lo ip-address 10.1.1.34/32 role iurup#Iub control and user plane IP addresses, VRF iubadd networking instance iub address dedicated /QNUP-2 ifacelo ip-address 10.1.0.3/32 role iubupadd networking instance iub address dedicated /QNUP-3 ifacelo ip-address 10.1.0.4/32 role iubupadd networking instance iub address dedicated /QNIUB-2iface lo ip-address 10.1.0.67/32 role iubcpadd networking instance iub address dedicated /QNIUB-3iface lo ip-address 10.1.0.68/32 role iubcp

• IP PlanRelated object class: ADDRRNC-xx/IP-1/OWNER-QNUP-0/ADDR-10.1.1.1-lo



100 DN0974301 Issue: 02G

7 Configure IP addresses for Iu and Iur control planeThe Iu/Iur Control plane IP addresses are configured to sctp1 and sctp2 interfaces atbackplane side (sctp1_1 and sctp2_1 for the VRF id 1). The control plane subnetsspan over all EIPU nodes (or over the planned nodes) providing the possibility toreach the service via any EIPU node without additional static routes configuration.The SIGTRAN related SCTP associations should be located as evenly as possiblewithin the EIPU nodes. At least four EIPU nodes should be applied towards one CNpeer element and the SCTP associations towards different CN / neighbor RNCelements should be distributed evenly in between all EIPU nodes.

g The SCTP association is terminated to a certain EIPU node. The IP addresses of SCTPMulti-Homed association are configured to the interface from where the outgoingSCTP/SIGTRAN traffic is forwarded out. The sctp1_[VRF-id] and sctp2_[VRF-id]interfaces are pre configured to the mcRNC. Four first VRFs including the default VRF(VRF id 0 - 3) contain the sctp interfaces and they can be applied for the Iu/Iur controlplane configuration.

g The role attribute is a free form character string that can be configured optionally. Therole attribute can be defined to keep the IP addressing usage clearly visible in order tosimplify the system maintenance. For the Iu-PS control plane addresses apply, forexample, role “iupscp”.

g The user /SS7SGU has to be added for the interface IP addresses that are applied asIu/Iur control plane source IP addresses (SS7/SIGTRAN/SCTP IP termination).


• SCLI commands#Iu-PS Control plane IP addressesadd networking instance iuiurcp address dedicated /EIPU-0iface sctp1_1 ip-address 10.1.8.17/28 role iupscpadd networking instance iuiurcp address dedicated /EIPU-1iface sctp1_1 ip-address 10.1.8.18/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-2iface sctp1_1 ip-address 10.1.8.19/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-3iface sctp1_1 ip-address 10.1.8.20/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-0iface sctp2_1 ip-address 10.1.8.145/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-1iface sctp2_1 ip-address 10.1.8.146/28 role iupscpadd networking instance iuiurcp address dedicated /EIPU-2iface sctp2_1 ip-address 10.1.8.147/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-3iface sctp2_1 ip-address 10.1.8.148/28 role iupscp user/SS7SGU

g Proceed with similar logics for all CN and neighbor RNC elements according to theplan.


Issue: 02G DN0974301 101



8 Configure the static routesThe following static routes have to be configured to the system. The VRRP/HSRPvirtual IP address will be used as user plane traffic gateway towards the peerelement. The site routers interface addresses are applied as gateways for the Iucontrol plane multi-homed connections.

• User plane traffic: Destination subnets are reached with routes learned via theOSPF.

• Control plane traffic: Destination subnets are reached via site router or EIPUbackplane interface address as gateway. The table presents the static routesneeded towards the Iu-PS control plane.

g Configure the other control plane static routes with similar logics.

• Static routes for ingress traffic via the backplane are not needed

– User plane the traffic is terminated at address located to VLAN interface thusthere is no need for redundant ingress routes via backplane

– Iu/Iur control plane the SCTP IP addresses are located to local subnets of theEIPU nodes thus no static routes needed at ingress direction


Node

VRF

Network Id

Priority

Gateway

Notes

EIPU-0 iuiurcp 10.8.0.0/24 0 10.1.8.1 Iu-PS control plane, router-1 asGW to first destination CP subnet

EIPU-0 iuiurcp 10.8.1.0/24 0 10.1.8.146 Iu-PS control plane, via EIPU-1and router-2 as GW to seconddestination CP subnet

EIPU-1 iuiurcp 10.8.0.0/24 0 10.1.8.17 Iu-PS control plane, via EIPU-0and router-1 as GW to firstdestination CP subnet

EIPU-1 iuiurcp 10.8.1.0/24 0 10.1.8.129 Iu-PS control plane, router-2 asGW to second destination CPsubnet



102 DN0974301 Issue: 02G

Table 24 Routing table for Iu-PS traffic (Cont.)

Node

VRF

Network Id

Priority

Gateway

Notes

EIPU-2 iuiurcp 10.81.0/24 0 10.1.8.146 Iu-PS control plane, EIPU-1 androuter-2 as GW to seconddestination CP subnet


EIPU-3 iuiurcp 10.8.1.0/24 0 10.1.8.146 Iu-PS control plane, EIPU-1 androuter-2 as GW to seconddestination CP subnet

• SCLI commands#Control plane, routes may serve several destination CN elements depending onthe network planningset routing instance iuiurcp node EIPU-0 static-route10.8.0.0/24 nexthop gateway address 10.1.8.1 onset routing instance iuiurcp node EIPU-0 static-route10.8.1.0/24 nexthop gateway address 10.1.8.146 onset routing instance iuiurcp node EIPU-1 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 onset routing instance iuiurcp node EIPU-1 static-route10.8.1.0/24 nexthop gateway address 10.0.1.129 onset routing instance iuiurcp node EIPU-2 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 onset routing instance iuiurcp node EIPU-2 static-route10.8.1.0/24 nexthop gateway address 10.1.8.145 onset routing instance iuiurcp node EIPU-3 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 onset routing instance iuiurcp node EIPU-3 static-route10.8.1.0/24 nexthop gateway address 10.1.8.145 on

g Configure all Iu and Iur control plane routes with same logic for all the needed EIPUnodes

• IP PlanRelated object class: SRT4, ADR4GWRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurcp/SRT4-10.8.0.0-24

• nexthop = 2 (gateway)RNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurcp/SRT4-10.8.0.0-24/ADR4GW-10.1.8.1

• No attributes needed, default values are appliedRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurcp/SRT4-10.8.1.0-24




Issue: 02G DN0974301 103

9 Configure OSPF

a) Configure the OSPF router id for each nodeThe interface IP address applied for the given VRF is set as router id. It isrecommended to select an existing IP address to OSPF router id in order tomake it inherently unique. Even that it is not mandatory to use an IP address asrouter id, a dotted-quad value should be used.Router id setting for iuiurup and iub VRF instances.

• SCLI commands#Router id values for iuiurup VRFset routing instance iuiurup node EIPU-0 router-id10.0.1.2set routing instance iuiurup node EIPU-1 router-id10.0.1.18#Router id values for iub VRFset routing instance iub node EIPU-2 router-id 10.0.4.2set routing instance iub node EIPU-3 router-id 10.0.4.18

• IP PlanRelated object class: GLPRMRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup/GLPRM

• routerId = 10.0.1.2

b) Configure the OSPF areas#iuiurup areasset routing instance iuiurup node EIPU-0 ospf area 10.0.1.0onset routing instance iuiurup node EIPU-0 ospf area 10.0.1.0stub onset routing instance iuiurup node EIPU-1 ospf area 10.0.1.0onset routing instance iuiurup node EIPU-1 ospf area 10.0.1.0stub on#iub areasset routing instance iub node EIPU-2 ospf area 10.0.4.0 onset routing instance iub node EIPU-2 ospf area 10.0.4.0stub onset routing instance iub node EIPU-3 ospf area 10.0.4.0 onset routing instance iub node EIPU-3 ospf area 10.0.4.0stub on

• IP PlanRelated object class: O2AREARNC-xx/IP-0/OWNER-EIPU-0/RTINST-iuiurup/O2AREA-10.0.1.0

• stub = 1 (yes, Stub area)

c) Activate the OSPF on the interfacesActivate the OSPF on the loopback and network interfaces.Proceed with the following configuration in order to activate the OSPF on theloopback interfaces

• SCLI commands#iuiurup VRF loopback interfaceset routing instance iuiurup node EIPU-0 ospf interfacelo area 10.0.1.0 on


104 DN0974301 Issue: 02G

set routing instance iuiurup node EIPU-1 ospf interfacelo area 10.0.1.0 on#iub VRF loopback interfaceset routing instance iub node EIPU-2 ospf interface loarea 10.0.4.0 onset routing instance iub node EIPU-3 ospf interface loarea 10.0.4.0 on


Proceed with the following configuration in order to activate the OSPF on thenetwork interfaces (VLAN interfaces)

• SCLI commands#iuiurup VRF VLAN interfacesset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 area 10.0.1.0 onset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 area 10.0.1.0 onset routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl13 area 10.0.1.0 onset routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl14 area 10.0.1.0 on#iub VRF VLAN interfacesset routing instance iub node EIPU-2 ospf interfaceiuiurup_vl21 area 10.0.4.0 onset routing instance iub node EIPU-2 ospf interfaceiuiurup_vl22 area 10.0.4.0 onset routing instance iub node EIPU-3 ospf interfaceiuiurup_vl23 area 10.0.4.0 onset routing instance iub node EIPU-3 ospf interfaceiuiurup_vl24 area 10.0.4.0 on

d) Adjust OSPF throttle SPF delay for link break handlingThe OSPF throttle SPF delay is needed to be adjusted in order to initiate the SPFrecalculation in the EIPU routing instance quickly enough after the neighbour orlink failure. The configuration needs to be repeated for all EIPU nodes and allrouting instances having the OSPF configuration. The configuration is neededalways when the OSPF interfaces in the EIPU leading to routers have differentcost values. In such case the SPF recalculation is performed immediately afterthe interface failure is detected.set routing instance iuiurup node EIPU-0 ospf throttle spf-delay 200set routing instance iub node EIPU-0 ospf throttle spf-delay 200set routing instance iuiurup node EIPU-1 ospf throttle spf-delay 200set routing instance iub node EIPU-1 ospf throttle spf-delay 200

e) Configure BFD Single-Hop for OSPF enabled VLAN interfacesBFD Single-Hop is activated for OSPF enabled VLAN interfaces in order toachieve fast recovery of the neighbor/OSPF interface failures.#VRF iuiurupset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 bfd-detect-mult 3 bfd-monitoring enable bfdrx-interval 150 bfd-tx-interval 150


Issue: 02G DN0974301 105

set routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 bfd-detect-mult 3 bfd-monitoring enable bfdrx-interval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl13 bfd-detect-mult 3 bfd-monitoring enable bfdrx-interval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl14 bfd-detect-mult 3 bfd-monitoring enable bfdrx-interval 150 bfd-tx-interval 150#VRF iubset routing instance iub node EIPU-2 ospf interfaceiuiurup_vl21 bfd-detect-mult 3 bfd-monitoring enable bfdrx-interval 150 bfd-tx-interval 150set routing instance iub node EIPU-2 ospf interfaceiuiurup_vl22 bfd-detect-mult 3 bfd-monitoring enable bfdrx-interval 150 bfd-tx-interval 150set routing instance iub node EIPU-3 ospf interfaceiuiurup_vl23 bfd-detect-mult 3 bfd-monitoring enable bfdrx-interval 150 bfd-tx-interval 150set routing instance iub node EIPU-3 ospf interfaceiuiurup_vl24 bfd-detect-mult 3 bfd-monitoring enable bfdrx-interval 150 bfd-tx-interval 150

f) Configure OSPF parametersFor each network instance set the OSPF designated router election priorityparameters properly. It is not recommended to allow the EIPU nodes to becomea designated router. Proceed with the following configuration.Set the external interfaces priority to 0.

• SCLI commands#VRF iuiurupset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 priority 0set routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 priority 0set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl11 priority 0set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl12 priority 0#VRF iubset routing instance iub node EIPU-2 ospf interfaceiub_vl21 priority 0set routing instance iub node EIPU-2 ospf interfaceiub_vl22 priority 0set routing instance iub node EIPU-3 ospf interfaceiub_vl23 priority 0set routing instance iub node EIPU-3 ospf interfaceiub_vl24 priority 0Set the directly connected VLAN interface cost to value 20 and VLANconnected to router connected to neighbor BCN module to value 40. This isenable the system to prefer the BCN module directly connected physical linkin normal conditions.

– SCLI commands

#VRF iuiurup


106 DN0974301 Issue: 02G

set routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 cost 20set routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 cost 40set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl11 cost 40set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl12 cost 20#VRF iubset routing instance iub node EIPU-2 ospf interfaceiub_vl21 cost 20set routing instance iub node EIPU-2 ospf interfaceiub_vl22 cost 40set routing instance iub node EIPU-3 ospf interfaceiub_vl23 cost 40set routing instance iub node EIPU-3 ospf interfaceiub_vl24 cost 20

• IP PlanRelated object class:O2AREA - O2IFCRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup/O2AREA-10.0.1.0/O2IFC-iuiurup_vl11

• electionPriority = 0• ospfCost = 2• bfdDetectMonitoring = 1 (enabled)• bfdDetectMult = 3• bfdRxInterval = 150• bfdTxInterval = 150

10 Configure user plane resources, IP-based route configurationFor IP Based Route configuration at Iu, Iur and Iub interfaces please refer tochapters 3.2 - 3.5. The following steps describe the Iu-PS interface configuration asan example.

• SCLI commandsadd networking ipbr ipbr-id 1 route-bandwidth 0 committed-bandwidth 0 committed-dcn-bandwidth 0 committed-sig-bandwidth 0 ipbr-name iupsipbr-1 scheduler-type noneIf a user plane non-load sharing configuration is applied, proceed asfollows.Assign a single IP address to the IP-based route 1 for the Iu-PS user planesource IP address selection.add networking ipro ipbr-id 1 ip-address 10.1.1.1 iface lo4owner /QNUP-0 vrf iuiurupIf a user plane IP Based Route load sharing configuration is applied,proceed as follows.Assign several IP addresses to the IP-based route 1 for the Iu-PS user planesource IP address selection.add networking ipro ipbr-id 1 ip-address 10.1.1.1 iface lo4owner /QNUP-2 vrf iuiurupadd networking ipro ipbr-id 1 ip-address 10.1.1.2 iface lo4owner /QNUP-3 vrf iuiurup

• IP PlanRelated object class: IPBR, IPRO


Issue: 02G DN0974301 107

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-lo5• vrf = iuiurup

RNC-xx/IP-1/OWNER-QNUP-1/IPRO-1-10.1.1.2-lo5 (more instances configuredwith IPBR load sharing)

• vrf = iuiurup

11 Configure control plane resourcesFor Iu and Iur control plane connections configuration details please refer to chapter3.2.

12 Check and configure QoS related resourcesIn most cases using the default QoS values is sufficient, but depending on networkarchitecture and further QoS constraints, the values need to be reviewed andpossibly adjusted.For more information, see the QoS configuration chapter.

13 Configure the Radio Network layer informationWith RNW configuration for Iu-PS, Iu-CS, Iur and Iub please refer to correspondingsteps within chapter 3.2.

3.4 Configuring mcRNC OSPF SiSo, VRF, 1GE withLAG and shared EIPUPurpose

To configure the Iu, Iur and Iub interface with the OSPF site solution, Virtual Routing andForwarding (VRF), 1GE interfaces and Ethernet Link Aggregation (LAG) functionalities.


• RAN1510 OSPF for Redundancy• RAN2256 Ethernet Link Aggregation for mcRNC



The configuration example is presented with mcRNC capacity step s3 and with sharedEIPU setup. The shared EIPU setup means that all EIPU nodes terminate the traffic fromall logical interfaces (Iu / Iur / Iub). The example configuration can be applied for planning


108 DN0974301 Issue: 02G

and configuring bigger capacity steps with using the presented design pattern for furtherneeded EIPU nodes. The configuration and connectivity principles apply as per EIPUpair basis.

The Virtual Routing and Forwarding instances are logically separate routing processeswithin the EIPU with separate routing tables and interfaces. VRF instances are used tokeep routing information, IP addressing, and IP interfaces logically separated betweendifferent logical interfaces. With OSPF SiSo the Iu/Iur control plane, managed with staticroutes, is separated from the user plane resources routing that is managed dynamicallywith OSPF.

The VRF implementation can be applied for Iu/Iur/Iub user plane and control plane. Thetotal amount of the VRFs should be planned to be as low as possible in order to keep theoverall configuration complexity low. For the Iu/Iur control plane, both IP addresses of theSCTP multi-homed association have to belong to the same VRF. The O&M functionswithin the CFPU are supported only within the default VRF (VRF-0).





• L3 type of site solution with dynamic routing• OSPF manages the user plane routing• Iu/Iur control plane with SCTP Multi-Homing is managed with static routes• Supports 1GE and 10GE interfaces

Restrictions:

O&M-related functions in the CFPU unit belong to default VRF only. Iu/Iur control planeIP addresses of a single SCTP multi-homed association can only belong to one VRF.Incoming traffic towards the IP address within the VRF has to come in via the VLANinterface tied to the same VRF.


The configuration examples in the instructions are based on the IP addressing presentedin Figure 24: Network configuration for mcRNC OSPF SiSo with LAG and VRF. VRFsare applied for different domains: Iu and Iur user plane, Iu and Iur control plane and Iubcontrol and user plane.


Issue: 02G DN0974301 109

Figure 24 Network configuration for mcRNC OSPF SiSo with LAG and VRF

The detailed configuration for the Iub interface is presented in Figure 24: Networkconfiguration for mcRNC OSPF SiSo with LAG and VRF. The application IP addressesfor the Iub user plane and control plane are bound to QNUP and QNIUB instances andassigned to loopback interface of the corresponding VRF. Separate IP addresses areapplied for Iub user plane and Iub control plane in order to allow independent failureactions for the services. The related IP addresses and VLAN interfaces belong to “iub”VRF with numeric id 11.


110 DN0974301 Issue: 02G

Figure 25 Iub configuration for mcRNC OSPF SiSo with LAG and VRF

Detailed figure for Iu-PS, Iu-CS and Iur user plane IP addressing is presented in Figure25: Iub configuration for mcRNC OSPF SiSo with LAG and VRF. Separate IP addressesare applied for the Iu-CS, Iu-PS and Iur user plane traffic IP layer termination. Therelated IP addresses and VLAN interfaces belong to “iuiurup” VRF with numeric id 5.


Issue: 02G DN0974301 111

Figure 26 Iu/Iur User Plane configuration for mcRNC OSPF SiSo with LAG and VRF

The Iu-PS, Iu-CS and Iur control plane SCTP associations and related IP addressing ispresented in Figure 26: Iu/Iur User Plane configuration for mcRNC OSPF SiSo with LAGand VRF. The SCTP IP addresses are configured to EIPU backplane cfeigw interfaces.Certain EIPU nodes are selected to work as gateways for the Iu/Iur control plane traffic.The related IP addresses and VLAN interfaces belong to “iuiurcp” VRF with numeric id 1.The Iu and Iur control plane configuration principles are similar in both VRRP/HSRP andOSPF site solutions.


112 DN0974301 Issue: 02G

Figure 27 Iu/Iur Control Plane configuration for mcRNC OSPF SiSo with LAG andVRF


The mcRNC site configuration applied VLANs for logical traffic separation and VRFs forlogical routing functions separation. With VRFs and static routes it is possible to apply forexample a default route configuration for the user plane connections in case all the userplane goes out via the same gateway without affecting for example to Iu/Iur control planerequiring a specific route entries.

Ethernet Link Aggregation is applied to group 1GE interfaces into a higher bandwidthlogical interface allowing simplified IP addressing and easier load sharing over severalphysical links from EIPU node to router. All EIPU nodes terminate traffic from all logicalinterfaces (shared EIPU scheme).

Multicontroller RNC



Issue: 02G DN0974301 113


– VLAN11 10.0.2.0/28– VLAN12 10.0.2.16/28– VLAN13 10.0.2.32/28– VLAN14 10.0.2.48/28




– VLAN21 10.0.4.0/28– VLAN22 10.0.4.16/28– VLAN23 10.0.4.32/28– VLAN24 10.0.4.48/28

Application IP addresses are assigned to a certain recovery group (RG) instance, whichprovides the redundancy scheme for hardware and software failures. With OSPF sitesolution the user plane IP addresses are configured to loopback interface of thecorresponding VRF instance. The IP address follows the active Recovery Unit (RU) ofthe QNUP RG. The Iub related application IP addresses are presented in Table 25: Iubcontrol and user plane IP addresses. The Iu and Iur user plane addresses are presentedin Table 26: Iu and Iur user plane IP addresses.


Recovery Group

Iub


QNUP-1 10.1.0.2

QNUP-2 10.1.0.3

QNUP-3 10.1.0.4

QNUP-0, Iub control plane 10.1.0.65

QNUP-1 10.1.0.66

QNUP-2 10.1.0.67

QNUP-3 10.1.0.68


114 DN0974301 Issue: 02G


Recovery Group

Iu-PS

Iu-CS

Iur

QNUP-0 10.1.1.1 10.1.1.17 10.1.1.33

QNUP-1 10.1.1.2 10.1.1.18 10.1.1.34

QNUP-2 10.1.1.3 10.1.1.19 10.1.1.35

QNUP-3 10.1.1.4 10.1.1.20 10.1.1.36







Routers/site switches


OSPF for site routers/switches (user plane traffic VRFs):

Two OSPF areas associated to separate VRFs are applied for Iu/Iur user plane and Iub.


Before you start

The mcRNC and site routers have been installed and all required connections have beenestablished. The site solution with OSPF is described in mcRNC Site Solution based onJuniper with OSPF using 10 Gigabit Ethernet connectivity and mcRNC Site Solutionbased on Juniper with OSPF using 1GE and 10GE connectivity documents.


Issue: 02G DN0974301 115


g Before starting a new IP layer configuration, check the existing IP layer configuration.Use the show networking ether and show networking address SCLIcommands to show the current settings of interfaces. If configuring the mcRNC usingthe IP plan, create and activate a plan in the mcRNC in order to have a basicconfiguration as a starting point for further modifications.

g To avoid IP layer fragmentation an MTU size of 1560 octets is recommended to be usedfor the Iu-PS transport. For more information on MTU, see WCDMA RAN IP Transport.

1 Configure the VRF interface

• SCLI commands

add networking vrf name iuiurup id 5



• IP Plan

Related object class: VRFRNC-xx/IP-1/VRF-iuiurup

• id=5

2 Configure the physical interfacesPhysical network interfaces are assigned to a certain EIPU node, if not yetconfigured. The mcRNC default egress queue set rncdefault has to be assigned tothe physical interface for proper default egress scheduling weights configuration.

• SCLI commands

add networking ether /EIPU-0 iface ethsfp13_r1 port sfp13outqset rncdefault mtu 1560








116 DN0974301 Issue: 02G










• IP Plan

Related object class: ETHERRNC-xx/IP-1/OWNER-EIPU-0/ETHER-ethsfp13_r1

• port = sfp13• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mtu=1560• outqset = rncdefault• vrf = default (default)(optional)

3 Configure the Ethernet Link Aggregation, LAG interfaces

• SCLI commands

add networking linkaggr /EIPU-0 iface lag1 slave ethsfp13_r1slave ethsfp14_r1 outqset rncdefault mtu 1560








Issue: 02G DN0974301 117



• SCLI commands#vlan 11-14, iu iur user planeadd networking instance iuiurup vlan /EIPU-0 realiface lag1vid 11 vlaniface iuiurup_vl11 mapping vlandscptopcp mtu1560add networking instance iuiurup vlan /EIPU-0 realiface lag2vid 12 vlaniface iuiurup_vl12 mapping vlandscptopcp mtu1560add networking instance iuiurup vlan /EIPU-1 realiface lag1vid 13 vlaniface iuiurup_vl13 mapping vlandscptopcp mtu1560add networking instance iuiurup vlan /EIPU-1 realiface lag2vid 14 vlaniface iuiurup_vl14 mapping vlandscptopcp mtu1560add networking instance iuiurup vlan /EIPU-2 realiface lag1vid 11 vlaniface iuiurup_vl11 mapping vlandscptopcp mtu1560add networking instance iuiurup vlan /EIPU-2 realiface lag2vid 12 vlaniface iuiurup_vl12 mapping vlandscptopcp mtu1560add networking instance iuiurup vlan /EIPU-3 realiface lag1vid 13 vlaniface iuiurup_vl13 mapping vlandscptopcp mtu1560add networking instance iuiurup vlan /EIPU-3 realiface lag2vid 14 vlaniface iuiurup_vl14 mapping vlandscptopcp mtu1560#vlan 17&18, iu iur control planeadd networking instance iuiurcp vlan /EIPU-0 realiface lag1vid 17 vlaniface iuiurcp_vl17 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-1 realiface lag1vid 18 vlaniface iuiurcp_vl18 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-2 realiface lag1vid 17 vlaniface iuiurcp_vl17 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-3 realiface lag1vid 18 vlaniface iuiurcp_vl18 mapping vlandscptopcp#vlan 21-24, iub control and user planeadd networking instance iub vlan /EIPU-0 realiface lag1 vid21 vlaniface iub_vl21 mapping vlandscptopcpadd networking instance iub vlan /EIPU-0 realiface lag2 vid22 vlaniface iub_vl22 mapping vlandscptopcpadd networking instance iub vlan /EIPU-1 realiface lag1 vid23 vlaniface iub_vl23 mapping vlandscptopcpadd networking instance iub vlan /EIPU-1 realiface lag2 vid24 vlaniface iub_vl24 mapping vlandscptopcpadd networking instance iub vlan /EIPU-2 realiface lag1 vid21 vlaniface iub_vl21 mapping vlandscptopcp


118 DN0974301 Issue: 02G

add networking instance iub vlan /EIPU-2 realiface lag2 vid22 vlaniface iub_vl22 mapping vlandscptopcpadd networking instance iub vlan /EIPU-3 realiface lag1 vid23 vlaniface iub_vl23 mapping vlandscptopcpadd networking instance iub vlan /EIPU-3 realiface lag2 vid24 vlaniface iub_vl24 mapping vlandscptopcp


• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mapping = vlandscptopcp• mtu = 1560• realiface = lag1• vid = 11• vrf = iuiurup


• SCLI commands#vlan 11-14add networking instance iuiurup address dedicated /EIPU-0iface iuiurup_vl11 ip-address 10.0.1.2/28add networking instance iuiurup address dedicated /EIPU-2iface iuiurup_vl11 ip-address 10.0.1.3/28add networking instance iuiurup address dedicated /EIPU-0iface iuiurup_vl12 ip-address 10.0.1.18/28add networking instance iuiurup address dedicated /EIPU-2iface iuiurup_vl12 ip-address 10.0.1.19/28add networking instance iuiurup address dedicated /EIPU-1iface iuiurup_vl13 ip-address 10.0.1.34/28add networking instance iuiurup address dedicated /EIPU-3iface iuiurup_vl13 ip-address 10.0.1.35/28add networking instance iuiurup address dedicated /EIPU-1iface iuiurup_vl14 ip-address 10.0.1.50/28add networking instance iuiurup address dedicated /EIPU-3iface iuiurup_vl14 ip-address 10.0.1.51/28#VLANs 15-20: iuiurcpadd networking instance iuiurcp address dedicated /EIPU-0iface iuiurcp_vl15 ipaddress 10.1.8.2/28add networking instance iuiurcp address dedicated /EIPU-0iface iuiurcp_vl17 ipaddress 10.1.8.34/28add networking instance iuiurcp address dedicated /EIPU-0iface iuiurcp_vl19 ipaddress 10.1.8.66/28add networking instance iuiurcp address dedicated /EIPU-2iface iuiurcp_vl15 ipaddress 10.1.8.3/28add networking instance iuiurcp address dedicated /EIPU-2iface iuiurcp_vl17 ipaddress 10.1.8.35/28add networking instance iuiurcp address dedicated /EIPU-1iface iuiurcp_vl16 ipaddress 10.1.8.130/28


Issue: 02G DN0974301 119

add networking instance iuiurcp address dedicated /EIPU-1iface iuiurcp_vl18 ipaddress 10.1.8.162/28add networking instance iuiurcp address dedicated /EIPU-1iface iuiurcp_vl20 ipaddress 10.1.8.194/28add networking instance iuiurcp address dedicated /EIPU-3iface iuiurcp_vl16 ipaddress 10.1.8.131/28add networking instance iuiurcp address dedicated /EIPU-3iface iuiurcp_vl18 ipaddress 10.1.8.163/28#vlan 21-24, iub control and user planeadd networking instance iub address dedicated /EIPU-0 ifaceiub_vl21 ip-address 10.0.4.2/28add networking instance iub address dedicated /EIPU-2 ifaceiub_vl21 ip-address 10.0.4.3/28add networking instance iub address dedicated /EIPU-0 ifaceiub_vl22 ip-address 10.0.4.18/28add networking instance iub address dedicated /EIPU-2 ifaceiub_vl22 ip-address 10.0.4.19/28add networking instance iub address dedicated /EIPU-1 ifaceiub_vl23 ip-address 10.0.4.34/28add networking instance iub address dedicated /EIPU-3 ifaceiub_vl23 ip-address 10.0.4.35/28add networking instance iub address dedicated /EIPU-1 ifaceiub_vl24 ip-address 10.0.4.50/28add networking instance iub address dedicated /EIPU-3 ifaceiub_vl24 ip-address 10.0.4.51/28

• IP Plan

Related object class:ADDRRNC-xx/IP-1/OWNER-EIPU-0/ADDR-10.1.8.2-iuiurcp_vl17

• mask=28• vrf=iuiurcp

6 Configure application IP addresses for user planeWith OSPF site solution Iu/Iur/Iub user plane and Iub control plane application IPaddresses are assigned to loopback interfaces of the corresponding VRF instance.The application IP address is present in the node/unit that is running the service atthe time (active recovery unit, RU).



• SCLI commands#Iu-PS user plane IP addresses, VRF iuiurupadd networking instance iuiurup address dedicated /QNUP-0iface lo ip-address 10.1.1.1/32 role iupsupadd networking instance iuiurup address dedicated /QNUP-1iface lo ip-address 10.1.1.2/32 role iupsupadd networking instance iuiurup address dedicated /QNUP-2iface lo ip-address 10.1.1.3/32 role iupsup


120 DN0974301 Issue: 02G

add networking instance iuiurup address dedicated /QNUP-3iface lo ip-address 10.1.1.4/32 role iupsup#Iu-CS user plane IP addresses, VRF iuiurupadd networking instance iuiurup address dedicated /QNUP-0iface lo ip-address 10.1.1.17/32 role iucsupadd networking instance iuiurup address dedicated /QNUP-1iface lo ip-address 10.1.1.18/32 role iucsupadd networking instance iuiurup address dedicated /QNUP-2iface lo ip-address 10.1.1.19/32 role iucsupadd networking instance iuiurup address dedicated /QNUP-3iface lo ip-address 10.1.1.20/32 role iucsup#Iur user plane IP addresses, VRF iuiurupadd networking instance iuiurup address dedicated /QNUP-0iface lo ip-address 10.1.1.33/32 role iurupadd networking instance iuiurup address dedicated /QNUP-1iface lo ip-address 10.1.1.34/32 role iurupadd networking instance iuiurup address dedicated /QNUP-2iface lo ip-address 10.1.1.35/32 role iurupadd networking instance iuiurup address dedicated /QNUP-3iface lo ip-address 10.1.1.36/32 role iurup#Iub control and user plane IP addresses, VRF iubadd networking instance iub address dedicated /QNUP-0 ifacelo ip-address 10.1.0.1/32 role iubupadd networking instance iub address dedicated /QNUP-1 ifacelo ip-address 10.1.0.2/32 role iubupadd networking instance iub address dedicated /QNUP-2 ifacelo ip-address 10.1.0.3/32 role iubupadd networking instance iub address dedicated /QNUP-3 ifacelo ip-address 10.1.0.4/32 role iubupadd networking instance iub address dedicated /QNIUB-0iface lo ip-address 10.1.0.65/32 role iubcpadd networking instance iub address dedicated /QNIUB-1iface lo ip-address 10.1.0.66/32 role iubcpadd networking instance iub address dedicated /QNIUB-2iface lo ip-address 10.1.0.67/32 role iubcpadd networking instance iub address dedicated /QNIUB-3iface lo ip-address 10.1.0.68/32 role iubcp

• IP PlanRelated object class: ADDRRNC-xx/IP-1/OWNER-QNUP-0/ADDR-10.1.1.1/32-lo5


7 Configure IP addresses for Iu and Iur control planeThe Iu/Iur Control plane IP addresses are configured to sctp1 and sctp2 interfaces atbackplane side (cfeigw17 for the VRF 17). The control plane subnets span over allEIPU nodes (or over the planned nodes) providing the possibility to reach the servicevia any EIPU node without additional static routes configuration.The SIGTRAN related SCTP associations should be located as evenly as possiblewithin the EIPU nodes. At least four EIPU nodes should be applied towards one CNpeer element and the SCTP associations towards different CN / neighbor RNCelements should be distributed evenly in between all EIPU nodes.


Issue: 02G DN0974301 121

g The SCTP association is terminated to a certain EIPU node. The IP addresses of SCTPMulti-Homed association are configured to the interface from where the outgoingSCTP/SIGTRAN traffic is forwarded out. The sctp1_[VRF-id] and sctp2_[VRF-id]interfaces are pre configured to the mcRNC. Four first VRFs including the default VRF(VRF id 1- 4) contain the sctp interfaces and they can be applied for the Iu/Iur controlplane configuration.




• SCLI commands#Iu-PS Control plane IP addressesadd networking instance iuiurcp address dedicated /EIPU-0iface sctp1_1 ip-address 10.1.8.17/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-1iface sctp1_1 ip-address 10.1.8.18/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-2iface sctp1_1 ip-address 10.1.8.19/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-3iface sctp1_1 ip-address 10.1.8.20/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-0iface sctp2_1 ip-address 10.1.8.145/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-1iface sctp2_1 ip-address 10.1.8.146/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-2iface sctp2_1 ip-address 10.1.8.147/28 role iupscp user/SS7SGUadd networking instance iuiurcp address dedicated /EIPU-3iface sctp2_1 ip-address 10.1.8.148/28 role iupscp user/SS7SGU





122 DN0974301 Issue: 02G


• User plane traffic: Destination subnets are reached with routes learned via theOSPF.


g Configure the other control plane static routes with similar logics.


– User plane the traffic is terminated at address located to VLAN interface thusthere is no need for redundant ingress routes via backplane

– Iu/Iur control plane the SCTP IP addresses are located to local subnets of theEIPU nodes thus no static routes needed at ingress direction


Node

VRF

Network Id

Priority

Gateway

Notes

EIPU-0 iuiurcp 10.8.0.0/24 0 10.1.8.1 Iu-PS control plane, router-1 asGW to first destination CP subnet

EIPU-0 iuiurcp 10.8.1.0/24 0 10.1.8.146 Iu-PS control plane, via EIPU-1and router-2 as GW to seconddestination CP subnet


EIPU-1 iuiurcp 10.8.1.0/24 0 10.1.8.129 Iu-PS control plane, router-2 asGW to second destination CPsubnet


EIPU-2 iuiurcp 10.81.0/24 0 10.1.8.145 Iu-PS control plane, EIPU-1 androuter-2 as GW to seconddestination CP subnet



Issue: 02G DN0974301 123


Node

VRF

Network Id

Priority

Gateway

Notes

EIPU-3 iuiurcp 10.8.1.0/24 0 10.1.8.145 Iu-PS control plane, EIPU-1 androuter-2 as GW to seconddestination CP subnet

• SCLI commands#Control plane, routes may serve several destination CN elements depending onthe network planningset routing instance iuiurcp node EIPU-0 static-route10.8.0.0/24 nexthop gateway address 10.1.8.1 onset routing instance iuiurcp node EIPU-0 static-route10.8.1.0/24 nexthop gateway address 10.1.8.146 onset routing instance iuiurcp node EIPU-1 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 onset routing instance iuiurcp node EIPU-1 static-route10.8.1.0/24 nexthop gateway address 10.0.1.129 onset routing instance iuiurcp node EIPU-2 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 onset routing instance iuiurcp node EIPU-2 static-route10.8.1.0/24 nexthop gateway address 10.1.8.145 onset routing instance iuiurcp node EIPU-3 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 onset routing instance iuiurcp node EIPU-3 static-route10.8.1.0/24 nexthop gateway address 10.1.8.145 on

g Configure all Iu and Iur control plane routes with same logic for all the needed EIPUnodes

• IP PlanRelated object class: SRT4, ADR4GWRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurcp/SRT4-10.8.0.0-24


• No attributes needed, default values are appliedRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurcp/SRT4-10.8.1.0-24



9 Configure OSPF



124 DN0974301 Issue: 02G

• SCLI commands#Router id values for iuiurup VRFset routing instance iuiurup node EIPU-0 router-id10.0.1.2set routing instance iuiurup node EIPU-1 router-id10.0.1.18set routing instance iuiurup node EIPU-2 router-id10.0.1.3set routing instance iuiurup node EIPU-3 router-id10.0.1.19#Router id values for iub VRFset routing instance iub node EIPU-0 router-id 10.0.4.2set routing instance iub node EIPU-1 router-id 10.0.4.18set routing instance iub node EIPU-2 router-id 10.0.4.3set routing instance iub node EIPU-3 router-id 10.0.4.19

• IP PlanRelated object class: GLPRMRNC-xx/IP-1/OWNER-EIPU-0/GLPRM-1

• routerId = 10.0.1.2

b) Configure the OSPF areas#iuiurup areasset routing instance iuiurup node EIPU-0 ospf area 10.0.1.0onset routing instance iuiurup node EIPU-0 ospf area 10.0.1.0stub onset routing instance iuiurup node EIPU-1 ospf area 10.0.1.0onset routing instance iuiurup node EIPU-1 ospf area 10.0.1.0stub onset routing instance iuiurup node EIPU-2 ospf area 10.0.1.0onset routing instance iuiurup node EIPU-2 ospf area 10.0.1.0stub onset routing instance iuiurup node EIPU-3 ospf area 10.0.1.0onset routing instance iuiurup node EIPU-3 ospf area 10.0.1.0stub on#iub areasset routing instance iub node EIPU-0 ospf area 10.0.4.0 onset routing instance iub node EIPU-0 ospf area 10.0.4.0stub onset routing instance iub node EIPU-1 ospf area 10.0.4.0 onset routing instance iub node EIPU-1 ospf area 10.0.4.0stub onset routing instance iub node EIPU-2 ospf area 10.0.4.0 onset routing instance iub node EIPU-2 ospf area 10.0.4.0stub onset routing instance iub node EIPU-3 ospf area 10.0.4.0 onset routing instance iub node EIPU-3 ospf area 10.0.4.0stub on

• IP PlanRelated object class: O2AREARNC-xx/IP-0/OWNER-EIPU-0/RTINST-iuiurup/O2AREA-10.0.1.0


Issue: 02G DN0974301 125


c) Adjust OSPF throttle SPF delay for link break handlingThe OSPF throttle SPF delay is needed to be adjusted in order to initiate the SPFrecalculation in the EIPU routing instance quickly enough after the neighbour orlink failure. The configuration needs to be repeated for all EIPU nodes and allrouting instances having the OSPF configuration. The configuration is neededalways when the OSPF interfaces in the EIPU leading to routers have differentcost values. In such case the SPF recalculation is performed immediately afterthe interface failure is detected.set routing instance iuiurup node EIPU-0 ospf throttle spf-delay 200set routing instance iub node EIPU-0 ospf throttle spf-delay 200set routing instance iuiurup node EIPU-1 ospf throttle spf-delay 200set routing instance iub node EIPU-1 ospf throttle spf-delay 200

d) Activate the OSPF on the interfacesActivate the OSPF on the loopback and network interfaces.

• Proceed with the following configuration in order to activate the OSPF on theloopback interfaces

• SCLI commands#iuiurup VRF loopback interfaceset routing instance iuiurup node EIPU-0 ospf interfacelo area 10.0.1.0 onset routing instance iuiurup node EIPU-1 ospf interfacelo area 10.0.1.0 onset routing instance iuiurup node EIPU-2 ospf interfacelo area 10.0.1.0 onset routing instance iuiurup node EIPU-3 ospf interfacelo area 10.0.1.0 on#iub VRF loopback interfaceset routing instance iub node EIPU-0 ospf interface loarea 10.0.4.0 onset routing instance iub node EIPU-1 ospf interface loarea 10.0.4.0 onset routing instance iub node EIPU-2 ospf interface loarea 10.0.4.0 onset routing instance iub node EIPU-3 ospf interface loarea 10.0.4.0 on


Proceed with the following configuration in order to activate the OSPF on thenetwork interfaces (VLAN interfaces)

• SCLI commands#iuiurup VRF VLAN interfacesset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 area 10.0.1.0 onset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 area 10.0.1.0 onset routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl13 area 10.0.1.0 on


126 DN0974301 Issue: 02G

set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl14 area 10.0.1.0 on#iub VRF VLAN interfacesset routing instance iub node EIPU-2 ospf interfaceiuiurup_vl21 area 10.0.4.0 onset routing instance iub node EIPU-2 ospf interfaceiuiurup_vl22 area 10.0.4.0 onset routing instance iub node EIPU-3 ospf interfaceiuiurup_vl23 area 10.0.4.0 onset routing instance iub node EIPU-3 ospf interfaceiuiurup_vl24 area 10.0.4.0 on

e) Configure BFD Single-Hop for OSPF enabled VLAN interfacesBFD Single-Hop is activated for OSPF enabled VLAN interfaces in order toachieve fast recovery of the neighbor/OSPF interface failures.#VRF iuiurupset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 bfd-detect-mult 3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 bfd-detect-mult 3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl13 bfd-detect-mult 3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl14 bfd-detect-mult 3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150#VRF iubset routing instance iub node EIPU-2 ospf interfaceiub_vl21 bfd-detect-mult 3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150set routing instance iub node EIPU-2 ospf interfaceiub_vl22 bfd-detect-mult 3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150set routing instance iub node EIPU-3 ospf interfaceiub_vl23 bfd-detect-mult 3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150set routing instance iub node EIPU-3 ospf interfaceiub_vl24 bfd-detect-mult 3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150

f) Configure OSPF parametersFor each network instance set the OSPF designated router election priorityparameters properly. It is not recommended to allow the EIPU nodes to becomea designated router. Proceed with the following configuration.Set the external interfaces priority to 0.

• SCLI commands#VRF iuiurupset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 priority 0set routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 priority 0set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl11 priority 0


Issue: 02G DN0974301 127

set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl12 priority 0#VRF iubset routing instance iub node EIPU-2 ospf interfaceiub_vl21 priority 0set routing instance iub node EIPU-2 ospf interfaceiub_vl22 priority 0set routing instance iub node EIPU-3 ospf interfaceiub_vl23 priority 0set routing instance iub node EIPU-3 ospf interfaceiub_vl24 priority 0Set the interfaces cost to 20.

– SCLI commands

#VRF iuiurupset routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl11 cost 20set routing instance iuiurup node EIPU-0 ospf interfaceiuiurup_vl12 cost 40set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl11 cost 40set routing instance iuiurup node EIPU-1 ospf interfaceiuiurup_vl12 cost 20#VRF iubset routing instance iub node EIPU-2 ospf interfaceiub_vl21 cost 20set routing instance iub node EIPU-2 ospf interfaceiub_vl22 cost 40set routing instance iub node EIPU-3 ospf interfaceiub_vl23 cost 40set routing instance iub node EIPU-3 ospf interfaceiub_vl24 cost 20

• IP PlanRelated object class:O2AREA - O2IFCRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup/O2AREA-10.0.1.0/O2IFC-iuiurup_vl11


10 Configure user plane resources, IP-based route configurationFor IP Based Route configuration at Iu, Iur and Iub interfaces please refer tochapters 3.2 - 3.5. The following steps describe the Iu-PS interface configuration asan example.

• SCLI commandsadd networking ipbr ipbr-id 1 route-bandwidth 0 committed-bandwidth 0 committed-dcn-bandwidth 0 committed-sig-bandwidth 0 ipbr-name iupsipbr-1 scheduler-type none


128 DN0974301 Issue: 02G

If a user plane non-load sharing configuration is applied, proceed asfollows.Assign a single IP address to the IP-based route 1 for the Iu-PS user planesource IP address selection.add networking ipro ipbr-id 1 ip-address 10.1.1.1 iface lo5owner /QNUP-0 vrf iuiurupIf a user plane IP Based Route load sharing configuration is applied,proceed as follows.Assign several IP addresses to the IP-based route 1 for the Iu-PS user planesource IP address selection.add networking ipro ipbr-id 1 ip-address 10.1.1.1 iface lo5owner /QNUP-0 vrf iuiurupadd networking ipro ipbr-id 1 ip-address 10.1.1.2 iface lo5owner /QNUP-1 vrf iuiurupadd networking ipro ipbr-id 1 ip-address 10.1.1.3 iface lo5owner /QNUP-2 vrf iuiurupadd networking ipro ipbr-id 1 ip-address 10.1.1.4 iface lo5owner /QNUP-3 vrf iuiurup



RNC-xx/IP-1/OWNER-QNUP-0/IPRO-1-10.1.1.1-lo5• vrf = iuiurup

RNC-xx/IP-1/OWNER-QNUP-1/IPRO-1-10.1.1.2-lo5 (more instances configuredwith IPBR load sharing)

• vrf = iuiurup

11 Configure control plane resourcesFor Iu and Iur control plane connections configuration details please refer to chapter3.2.


13 Configure the Radio Network layer informationWith RNW configuration for Iu-PS, Iu-CS, Iur and Iub please refer to correspondingchapter 3.2.


Issue: 02G DN0974301 129

3.5 Configuring mcRNC VRRP/HSRP SiSo, VRF, 10GEand shared EIPUPurpose

To configure the Iu, Iur and Iub interfaces with the VRRP/HSRP site solution, VirtualRouting and Forwarding (VRF) and 10GE interfaces.The multicontroller RNC providesoptimized connectivity alternative for 10GE interfaces based site solution. With theoptimized solution, two EIPU nodes of a single BCN module are connected to the sameexternal 10GE port of the BCN module.

The following optional feature is required:

• RAN2696 mcRNC 10 Gigabit Ethernet Based Network Connectivity



The configuration example is presented with mcRNC capacity step s1 and with sharedEIPU setup. The shared EIPU setup means that all EIPU nodes terminate the traffic fromall logical interfaces (Iu/Iur/Iub). The example configuration is applied for planning andconfiguring bigger capacity steps using the presented design pattern for further neededEIPU nodes. The configuration and connectivity principles apply as per EIPU pair andBCN pair basis. In case of full 10GE connectivity optimized configuration, one 10GEinterface per BCN module is required.

g Note

IP addresses and subnets given in the document are just examples and must be setaccording to the actual network plan.

The configuration examples in the instructions are based on the IP addressing presentedin Figure 28: Network configuration for mcRNC VRRP/HSRP SiSo with 10GE and VRF.VRFs are applied for different domains: Iu and Iur user plane, Iu and Iur control planeand Iub control and user plane.


130 DN0974301 Issue: 02G

Figure 28 Network configuration for mcRNC VRRP/HSRP SiSo with 10GE and VRF

The detailed configuration for the Iub interface is presented in Figure 29: Iubconfiguration for mcRNC VRRP/HSRP SiSo with 10GE and VRF. One IP address fromthe VLAN interface subnet is bound to each QNUP and QNIUB instance. Separate IPaddresses are applied for Iub user plane and Iub control plane to allow independentfailure actions for the services. The related IP addresses and VLAN interfaces belong to“iub” VRF.


Issue: 02G DN0974301 131

Figure 29 Iub configuration for mcRNC VRRP/HSRP SiSo with 10GE and VRF

Detailed figure for Iu-PS, Iu-CS and Iur user plane IP addressing are presented in Figure30: Iu/Iur User Plane configuration for mcRNC VRRP/HSRP SiSo with 10GE and VRF.Separate IP addresses are applied for the Iu-CS, Iu-PS and Iur user plane traffic IP layertermination. The related IP addresses and VLAN interfaces belong to “iuiurup” VRF.


132 DN0974301 Issue: 02G

Figure 30 Iu/Iur User Plane configuration for mcRNC VRRP/HSRP SiSo with 10GEand VRF

The Iu-PS, Iu-CS and Iur control plane SCTP associations and related IP addressing arepresented in Figure 31: Iu/Iur Control Plane configuration for mcRNC VRRP/HSRP SiSowith 10GE and VRF. The SCTP IP addresses are configured to EIPU backplane cfeigwinterfaces. Certain EIPU nodes are selected to work as gateways for the Iu/Iur controlplane traffic. The related IP addresses and VLAN interfaces belong to “iuiurcp” VRF.


Issue: 02G DN0974301 133

Figure 31 Iu/Iur Control Plane configuration for mcRNC VRRP/HSRP SiSo with 10GEand VRF


The mcRNC site configuration applies VLANs for logical traffic separation and VRFs forlogical routing functions separation. With VRFs and static routes, the user is able toapply a default route configuration for the user plane connections without affectingIu/Iurcontrol planes (which require specific route entries) when all the user planes go outthrough the same gateway.The configuration with 10GE interfaces provides a simplifiedconnectivity, IP addressing and easy sharing of the EIPU capacity. Within thisconfiguration example, all EIPU nodes terminate traffic from all logical interfaces (sharedEIPU setup).

Multicontroller RNC

VRF and VLAN configurations:

• Iu/Iur User Plane, VRF iuiurup1 (VRF id 4)


134 DN0974301 Issue: 02G

– VLAN11 10.0.1.0/27


– VLAN12 10.0.1.32/27


– VLAN17 10.1.8.0/28– VLAN18 10.1.8.128/28

• Iub Control and User Plane, VRF iub1 (VRF id 11)

– VLAN21 10.0.4.0/27


– VLAN22 10.0.4.32/27

The application IP addresses are assigned to a certain recovery group (RG) instance,which provides the redundancy scheme for hardware and software failures. WithVRRP/HSRP site solution, the user plane IP addresses are configured to VLAN interfacesubnet. The IP address follows the active Recovery Unit (RU) of the QNUP RG. The Iuand Iur user plane addresses are presented in Table 28: Iu and Iur user plane IPaddresses.


Recovery Group

Iu-PS

Iu-CS

Iur

Iub

QNUP-0 10.0.1.4 10.0.1.14 10.0.1.24 10.0.4.4

QNUP-1 10.0.1.36 10.0.1.46 10.0.1.56 10.0.4.36

QNUP-2 10.0.1.5 10.0.1.15 10.0.1.25 10.0.4.5

QNUP-3 10.0.1.37 10.0.1.47 10.0.1.57 10.0.4.37






Issue: 02G DN0974301 135



Routers/site switches:


VRRP/HSRP for site routers/switches (applied for user plane traffic):Two VRRP/HSRPgroups are applied for Iu/Iur user plane and Iub. The VRRP/HSRP priorities must beplanned and configured properly in the routers to provide adequate router level trafficload sharing.

• VRRP/HSRP group 11 virtual IP address: 10.0.1.1• VRRP/HSRP group 12 virtual IP address: 10.0.1.33• VRRP/HSRP group 21 virtual IP address: 10.0.4.1• VRRP/HSRP group 22 virtual IP address: 10.0.4.33

The core network and SIGTRAN for Iu-PS, Iu-CS and Iur control planes’ configurationrefer to Configuring mcRNC OSPF SiSo, VRF, 10GE and shared EIPU

Before you start

Before starting the configuration, make sure that the mcRNC and site routers areinstalled and all the required connections are established. The site solution withVRRP/HSRP is described in mcRNC Site Solution based on Juniper EX4500 with VRRPusing 10 Gigabit Ethernet connectivity document.

For a detailed configuration steps of the radio network (RNW) layer and Iu/Iur controlplanes (SIGTRAN, SS&) for the Iu-PS and Iu-CS, Iur and Iub, see Configuring mcRNCOSPF SiSo, VRF, 10GE and shared EIPU

Steps

g Note

Before starting a new IP layer configuration, check the existing IP layer configuration.Use the show networking ether and show networking address SCLIcommands to show the current settings of the interfaces. When configuring the mcRNCusing the IP plan, create and activate a plan in the mcRNC to have a basicconfiguration as a starting point for further modifications.

g Note

To avoid IP layer fragmentation, an MTU with size of 1560 octets is recommended to beused for the Iu-PS transport. For more information on MTU, seeWCDMA RAN IP Transport.


136 DN0974301 Issue: 02G

3.5.1 Instructions

1 Configure the VRF instances

• SCLI commandsadd networking vrf name iuiurup1 id 4

add networking vrf name iuiurup2 id 5


add networking vrf name iub1 id 11

add networking vrf name iub2 id 12

• IP PlanRelated object class: VRFRNC-xx/IP-1/VRF-iub1

• id = 11

2 Configure the physical interfacesIf the physical network interfaces are not yet configured, they are assigned to acertain EIPU node. The mcRNC default egress queue set rncdefault has to beassigned to the physical interface for proper default egress scheduling weightsconfiguration.

• SCLI commands#Add shared port group to first BCN moduleadd networking switch port-group name sfp11-bcn1 port LMP-1-1-1:sfp11#Add shared port group to second BCN moduleadd networking switch port-group name sfp11-bcn2 port LMP-1-2-1:sfp11#Assign shared 10GE port to EIPU nodes of first BCN moduleadd networking ether /EIPU-0 iface ethsfp11 port sfp11-bcn1outqset rncdefault mtu 1560add networking ether /EIPU-2 iface ethsfp11 port sfp11-bcn1outqset rncdefault mtu 1560#Assign shared 10GE port to EIPU nodes of second BCN moduleadd networking ether /EIPU-1 iface ethsfp11 port sfp11-bcn2outqset rncdefault mtu 1560add networking ether /EIPU-3 iface ethsfp11 port sfp11-bcn2outqset rncdefault mtu 1560

• IP Plan

g The 10GE port mode, where several EIPU nodes share the same external 10GE port, isnot configurable via IP plan interface within mcRNC3.0.

g The rate limit is directly inherited from the interface speed directly if no explicit value isgiven.


Issue: 02G DN0974301 137

3 Configure the link state detector to the interfaces with QNUP and QNIUB ownerThe link state detector is configured to notify the QNUP and QNIUB Recovery Group(RG) about the interface state changes. Once the interface state goes down, theactive Recovery Unit of the RG instance is moved to the EIPU-pair node.

g The link state detector configuration is mandatory for mcRNC VRRP/HSRP sitesolution. At EIPU nodes, the link state detector is applied for 1GE, LAG or 10GEinterface with having the QNUP and QNIUB as the owner.

• SCLI command examples#Link state detector configurationadd networking link-state-detector /QNUP-0 iface ethsfp11

add networking link-state-detector /QNUP-1 iface ethsfp11



add networking link-state-detector /QNIUB-0 iface ethsfp11




• IP PlanRelated object class: LNSIFRNC-xx/IP-1/OWNER-QNUP-0/LNSIF-ethsfp11

4 Configure the VLAN interfaces within 10GE interfacesThe VLAN interface is created for a certain physical interface with reference to itsname. The VLAN ids and the VLAN interface names have to be planned andconfigured accordingly.

• SCLI commands#vlan 11&12, iu iur user planeadd networking instance iuiurup1 vlan /EIPU-0 realifaceethsfp11 vid 11 vlaniface iuiurup_vl11 mappingvlandscptopcp mtu 1560add networking instance iuiurup2 vlan /EIPU-0 realifaceethsfp11 vid 12 vlaniface iuiurup_vl12 mappingvlandscptopcp mtu 1560add networking instance iuiurup1 vlan /EIPU-1 realifaceethsfp11 vid 11 vlaniface iuiurup_vl11 mappingvlandscptopcp mtu 1560add networking instance iuiurup2 vlan /EIPU-1 realifaceethsfp11 vid 12 vlaniface iuiurup_vl12 mappingvlandscptopcp mtu 1560

t Configure the VLAN interfaces for all EIPU nodes.


138 DN0974301 Issue: 02G

#vlan 17&18, iu iur control planeadd networking instance iuiurcp vlan /EIPU-0 realiface ethsfp11 vid 17 vlaniface iuiurcp_vl17 mapping vlandscptopcp

add networking instance iuiurcp vlan /EIPU-1 realiface ethsfp11 vid 18 vlaniface iuiurcp_vl18 mapping vlandscptopcp



#vlan 21&22, iub control and user planeadd networking instance iub1 vlan /EIPU-0 realiface ethsfp11 vid 21 vlaniface iub_vl21 mapping vlandscptopcp

add networking instance iub2 vlan /EIPU-0 realiface ethsfp11 vid 22 vlaniface iub_vl22 mapping vlandscptopcp



t Configure VLAN interfaces for all EIPU nodes.


• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mapping = vlandscptopcp• mtu = 1560• realiface = ethsfp11• vid = 11• vrf = iuiurup1


g The interface name refers to the created physical interface. If VLANs are used, thenetwork interface IP addresses are tied to VLAN interfaces.

#VLANs 17 and 18add networking instance iuiurcp address dedicated /EIPU-0 iface iuiurcp_vl17 ip-address 10.1.8.2/28 user /SS7SGU

add networking instance iuiurcp address dedicated /EIPU-1 iface iuiurcp_vl18 ip-address 10.1.8.130/28 user /SS7SGU


Issue: 02G DN0974301 139



g Repeat configuration for Iu-CS and Iur interfaces related addresses.



6 Configure the application IP addresses for user planeWith VRRP/HSRP site solution, the user plane and Iub control plane application IPaddresses are assigned to VLAN interface subnet. The user plane application IPaddresses belong to router local subnets and the IP address is present in thenode/unit that is running the service at this time (active recovery unit, RU).

g With VRRP/HSRP site solution, the VLAN names should be configured symmetrically inboth EIPU nodes of the EIPU pair. This is to allow configuration of the logical IPaddress that will follow active RU of the QNUP RG. Along with the RG switchover, therelated IP address will move to the new node. Within the service switchover the newMAC address will be reported with gratuitous ARP to site routers.

g The role attribute is a free form character string that can be configured optionally. Therole attribute can be defined to keep the IP addressing usage visible to simplify thesystem maintenance. For the Iu-PS user plane addresses apply, for example, role“iupsup”.Proceed with the following configuration.

• SCLI commands#Iu-PS user plane IP addresses, VRF iuiurupadd networking instance iuiurup1 address dedicated /QNUP-0 iface iuiurup_vl11 ip-address 10.0.1.4/27 role iupsup

add networking instance iuiurup2 address dedicated /QNUP-1 iface iuiurup_vl12 ip-address 10.0.1.36/27 role iupsup



#Iu-CS user plane IP addresses, VRF iuiurupadd networking instance iuiurup1 address dedicated /QNUP-0 iface iuiurup_vl11 ip-address 10.0.1.14/27 role iucsup

add networking instance iuiurup2 address dedicated /QNUP-1 iface


140 DN0974301 Issue: 02G

iuiurup_vl12 ip-address 10.0.1.46/27 role iucsup

add networking instance iuiurup1 address dedicated /QNUP-2 iface iuiurup_vl11 ip-address 10.0.1.15/27 role iucsup

add networking instance iuiurup2 address dedicated /QNUP-3 iface iuiurup_vl12 ip-address 10.0.1.47/27 role iucsup

#Iur user plane IP addresses, VRF iuiurupadd networking instance iuiurup1 address dedicated /QNUP-0 iface iuiurup_vl11 ip-address 10.0.1.24/27 role iurup

add networking instance iuiurup2 address dedicated /QNUP-1 iface iuiurup_vl12 ip-address 10.0.1.56/27 role iurup



#Iub control and user plane IP addresses, VRF iubadd networking instance iub1 address dedicated /QNUP-0 iface iub_vl21 ip-address 10.0.4.4/27 role iubup

add networking instance iub2 address dedicated /QNUP-1 iface iub_vl22 ip-address 10.0.4.36/27 role iubup



add networking instance iub1 address dedicated /QNIUB-0 iface iub_vl21 ip-address 10.0.4.20/27 role iubcp




• IP PlanRelated object class: ADDRRNC-xx/IP-1/OWNER-QNUP-0/ADDR-10.0.1.4-iuiurup_vl11

• mask = 27• vrf = iuiurup1• role = iupsup


Issue: 02G DN0974301 141

7 Configure IP addresses for Iu and Iur control plane sctp interfacesThe Iu/Iur Control plane IP addresses are configured to sctp1 and sctp2 interfaces atbackplane side (sctp1_1 and sctp2_1 for the VRF id 1). The control plane subnetsspan over all EIPU nodes (or over the planned nodes), which enables the possibilityto reach the service via any EIPU node without additional static routes configuration.The SIGTRAN related SCTP associations should be located as evenly as possiblewithin the EIPU nodes. At least four EIPU nodes should be applied towards one CNpeer element and the SCTP associations towards different CN/neighbor RNCelements should be distributed evenly in between all EIPU nodes.

g The SCTP association is terminated to a certain EIPU node. The IP addresses of SCTPMulti-Homed association are configured to the interface from where the outgoingSCTP/SIGTRAN traffic is forwarded out. The sctp1_[VRF-id] and sctp2_[VRF-id]interfaces are preconfigured to the mcRNC. The first four VRFs including the defaultVRF (VRF id 0 - 3), contain the sctp interfaces and they can be applied for the Iu/Iurcontrol plane configuration.




• SCLI commands#Iu-PS Control plane IP addressesadd networking instance iuiurcp address dedicated /EIPU-0 iface sctp1_1 ip-address 10.1.8.17/28 role iupscp user /SS7SGU









142 DN0974301 Issue: 02G

t Proceed with similar logics for all CN and neighbour RNC elements according to theplan.




• User plane traffic: Destination subnets are reached via VRRP/HSRP virtual IP asgateway. The default route can be applied within a user plane’s VRF.

• Control plane traffic: Destination subnets are reached via site router or EIPUbackplane interface address as gateway. The table presents the static routesneeded towards the Iu-PS control plane. Configure the other control plane staticroutes with similar logics.

• Static routes for ingress traffic via the backplane are not needed• In the user plane the traffic is terminated at address located to VLAN interface,

thus there is no need for redundant ingress routes via backplane• In the Iu/Iur control planes, the SCTP IP addresses are located to the local

subnets of the EIPU nodes, thus there are no static routes that are needed atingress direction.


Node

VRF

Network Id

Priority

Gateway

Notes

EIPU-0 iuiurup1 default 0 10.0.1.1 Iu Iur user plane

EIPU-0 iuiurup2 default 0 10.0.1.33 -







EIPU-0 iub1 default 0 10.0.4.1 Iub control and user plane

EIPU-0 iub2 default 0 10.0.4.33 -


Issue: 02G DN0974301 143


Node

VRF

Network Id

Priority

Gateway

Notes



EIPU-2 iub1 default 0 10.0.4.1 Iub control and user plane





EIPU-0 iuiurcp 10.8.1.0/24 0 10.1.8.146 Iu-PS control plane, via EIPU-1 androuter-2 as GW to second destinationCP subnet







• SCLI commands#User plane, routes might serve several destination CN elements depending onthe network planningset routing instance iuiurup1 node EIPU-0 static-route default nexthop gateway address 10.0.1.1 on

set routing instance iuiurup2 node EIPU-0 static-route default nexthop gateway address 10.0.1.33 on


144 DN0974301 Issue: 02G







g Configure all Iu and Iur user planes and Iub control and user plane routes with the sameprinciples to all related EIPU nodes.

#Control plane, routes may serve several destination CN elements depending onthe network planningset routing instance iuiurcp node EIPU-0 static-route 10.8.0.0/24 nexthop gateway address 10.1.8.1 on








g Configure all Iu and Iur control plane routes using the same principles to all neededEIPU nodes.

• IP Plan

Related object class: SRT4, ADR4GW


Issue: 02G DN0974301 145

RNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup1/SRT4-default


RNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup1/SRT4-default/ADR4GW-10.0.1.1


RNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup2/SRT4-default


RNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup2/SRT4-default/ADR4GW-10.0.1.33










9 Configure the user plane resources, IP-based route configurationFor IP Based Route configuration at Iu, Iur and Iub interfaces, please refer toConfiguring mcRNC OSPF SiSo, VRF, 10GE and shared EIPU:The following steps describe the Iu-PS interface configuration as an example.

• SCLI commandsadd ipbr ipbr-id 1 route-bandwidth 0 committed-bandwidth 0committed-dcn-bandwidth 0 committed-sig-bandwidth 0 ipbr-name iupsipbr-1 scheduler-type none

After a user plane non-load sharing configuration is applied, assign a single IPaddress to the IP-based route 1 for the Iu-PS user plane source IP addressselection.add ipro ipbr-id 1 ip-address 10.0.1.17 iface iups_vl11 owner/QNUP-0 vrf iuiurup1

After a user plane IP Based Route load sharing configuration is applied, assignseveral IP addresses to the IP-based route 1 for the Iu-PS user plane source IPaddress selection.add ipro ipbr-id 1 ip-address 10.0.1.4 iface iuiurup_vl11 owner /QNUP-0 vrf iuiurup1

add ipro ipbr-id 1 ip-address 10.0.1.36 iface iuiurup_vl12 owner /QNUP-1 vrf iuiurup2



146 DN0974301 Issue: 02G




RNC-xx/IP-1/OWNER-QNUP-0/IPRO-1-10.0.1.4-iuiurup_vl11

• • vrf = iuiurup1

RNC-xx/IP-1/OWNER-QNUP-1/IPRO-1-10.0.1.36-iuiurup_vl12 (… more instancesconfigured with IPBR load sharing)

• • vrf = iuiurup2

10 Configure the control plane resourcesFor more details on Iu and Iur control plane connections' configuration, seeConfiguring mcRNC OSPF SiSo, VRF, 10GE and shared EIPU.

11 Check and configure QoS related resourcesIn most cases, using the default QoS values are sufficient, but depending onnetwork’s architecture and further QoS constraints, the values need to be reviewedand possibly adjusted.For more information, see Configuring QoS.

12 Configure the Radio Network layer informationFor RNW configuration for Iu-PS, Iu-CS, Iur, and Iub, see Configuring mcRNC OSPFSiSo, VRF, 10GE and shared EIPU.

3.6 Configuring mcRNC VRRP/HSRP SiSo, VRF, 1GEwith LAG and shared EIPUPurpose

To configure the Iu, Iur and Iub interface with the VRRP/HSRP site solution, VirtualRouting and Forwarding (VRF), 1GE interfaces and Ethernet Link Aggregation (LAG)functionalities.


Issue: 02G DN0974301 147

The following optional feature is required:

• RAN2256 Ethernet Link Aggregation for mcRNC



The configuration example is presented with mcRNC capacity step s1 and with sharedEIPU setup. The shared EIPU setup means that all EIPU nodes terminate the traffic fromall logical interfaces (Iu / Iur / Iub). The example configuration can be applied for planningand configuring bigger capacity steps with using the presented design pattern for furtherneeded EIPU nodes. The configuration and connectivity principles apply as per EIPUpair basis.

The Virtual Routing and Forwarding instances are logically separate routing processeswithin the EIPU with separate routing tables and interfaces. VRF instances are used tokeep routing information, IP addressing, and IP interfaces logically separated betweendifferent logical interfaces. For the user plane connections within one VRF, a simplifieddefault route-based configuration can be applied to avoid mcRNC static routeconfiguration changes if the neighbor network element allocations and destination IPaddresses change. With default route configuration the amount of needed static routesfor the user plane is decreased to minimum.

The VRF implementation can be applied for Iu/Iur/Iub user plane and control plane. Thetotal amount of the VRFs should be planned to be as low as possible in order to keep theoverall configuration complexity low. For the Iu/Iur control plane, both IP addresses of theSCTP multi-homed association have to belong to the same VRF. The O&M functionswithin the CFPU are supported within the default VRF (VRF-0).




The main building blocks for the VRRP/HSRP site solution in general are the following:

• L2 type of site solution where L2 switching takes place in between the site routers• VRRP/HSRP applied for router redundancy (user plane)• Provides planning principles compatibility with the current IPA-RNC VRRP/HSRP site

solution• Supports 1GE and 10GE interfaces

Restrictions:

• O&M-related functions in the CFPU unit belong to default VRF only. Iu/Iur controlplane IP addresses of a single SCTP multi-homed association can only belong toone VRF. Incoming traffic towards the IP address within the VRF has to come inthrough the VLAN interface tied to the same VRF.



148 DN0974301 Issue: 02G

The configuration examples in the instructions are based on the IP addressing presentedin Figure Network configuration for mcRNC VRRP/HSRP SiSo with LAG and VRF. VRFsare applied for different domains: Iu and Iur user plane, Iu and Iur control plane and Iubcontrol and user plane.

Figure 32 Network configuration for mcRNC VRRP/HSRP SiSo with LAG and VRF

EIPU-3 VRF�iuiurup11

VRF�iuiurup12

VRF�iub1

VRF�iub2

VLAN11�10.0.1.5/27

VLAN12�10.0.1.37/27

VLAN18�10.1.8.131/28

VLAN21�10.0.4.5/27

VLAN22�10.0.4.37/27

VRF�iuiurcp

LA

G1


VRF�iuiurup2

VRF�iub1

VRF�iub2

VLAN11�10.0.1.4/27

VLAN12�10.0.1.36/27

VLAN18�10.1.8.13 /280

VLAN21�10.0.4.4/27

VLAN22�10.0.4.36/27

VRF�iuiurcp

LA

G1

Router-2

VL11�10.0.1.3/27

VL12�10.0.1.35/27

VL18�10.1.8.129/28

VL21�10.0.4.3/27

VL22�10.0.4.35/27SFP16

SFP15

SFP14

SFP13

SFP20

SFP19

SFP18

SFP17


VRF�iuiurup2

VRF�iub1

VRF�iub2

VLAN11�10.0.1.5/27

VLAN12�10.0.1.37/27

VLAN17�10.0.1.8.3/28

VLAN21�10.0.4.5/27

VLAN22�10.0.4.37/27

VRF�iuiurcp

LA

G1


VRF�iuiurup2

VRF�iub1

VRF�iub2

VLAN11�10.0.1.4/27

VLAN12�10.0.1.36/27

VLAN17�10.1.8.2/28

VLAN21�10.0.4.4/27

VLAN22�10.0.4.36/27

VRF�iuiurcp

LA

G1

Router-1

VL11�10.0.1.2/27

VL12�10.0.1.34/27

VL17�10.1.8.1/28

VL21�10.0.4.2/27

VL22�10.0.4.34/27SFP16

SFP15

SFP14

SFP13

SFP20

SFP19

SFP18

SFP17

cfeigw1

sctp1_1

sctp2_1

cfeigw1

sctp1_1

sctp2_1

cfeigw1

sctp1_1

sctp2_1

cfeigw1

sctp1_1

sctp2_1

VRRP11

VRRP12

VRRP21

VRRP22

The detailed configuration for the Iub interface is presented in Figure Networkconfiguration for mcRNC VRRP/HSRP SiSo with LAG and VRF. One IP address fromthe VLAN interface subnet is bound to each QNUP and QNIUB instance. Separate IPaddresses are applied for Iub user plane and Iub control plane in order to allowindependent failure actions for the services. The related IP addresses and VLANinterfaces belong to “iub” VRF.


Issue: 02G DN0974301 149

Figure 33 Iub configuration for mcRNC VRRP/HSRP SiSo with LAG and VRF

EIPU-1

BCN�2

Router-2

VL21�10.0.4.0/27

VL22�10.0.4.35/27

VL22�10.0.4.36/27

VL22�10.0.4.52/27

VL21�10.0.4.4/27

VL21�10.0.4.20/27

VRRP22�10.0.4.33/27

VRRP21�10.0.4.1/27

Router-1

QNUP-0�(Standby)

VL21�10.0.4.2/27

VL22�10.0.4.34/27

EIPU-0

BCN�1

mcRNC�Iub�controlplane�subnet-10.0.4.0/26

Iub�User�plane�andControl�plane�address-BTS#1:�10.2.0.1-BTSs�subnet�10.2.0.0/24

Iubbackhaul

(IP)

BTS#1

QN�UB-1�(Standby)I

QN�UB-0�(Act)10.0.4.20�(VL21)

I

QNUP-1�(Act)10.0.4.36�(VL22)

QN�UB-0�(Standby)I

QN�UB-1�(Act)10.0.4.52�(VL22)

I

QNUP-1�(Standby)

QNUP-0�(Act)10.0.4.4�(VL21)

BTS(s)

BTS�O&M�subnet-10.10.0.0/24

LAG1

VRF�iub1

VL22�10.0.4.36/27

VL22�10.0.4.52/27

VL21�10.0.4.4/27

VL21�10.0.4.20/27

LAG1

VRF�iub1

VRF�iub2

VRF�iub2

Detailed figure for Iu-PS, Iu-CS and Iur user plane IP addressing is presented in Figurex. Separate IP addresses are applied for the Iu-CS, Iu-PS and Iur user plane traffic IPlayer termination. The related IP addresses and VLAN interfaces belong to “iuiurup” VRF.


150 DN0974301 Issue: 02G

Figure 34 Iu/Iur User Plane configuration for mcRNC VRRP/HSRP SiSo with LAGand VRF

The Iu-PS, Iu-CS and Iur control plane SCTP associations and related IP addressing ispresented in Figure x. The SCTP IP addresses are configured to EIPU backplane cfeigwinterfaces. Certain EIPU nodes are selected to work as gateways for the Iu/Iur controlplane traffic. The related IP addresses and VLAN interfaces belong to “iuiurcp” VRF.


Issue: 02G DN0974301 151

Figure 35 Iu/Iur Control Plane configuration for mcRNC VRRP/HSRP SiSo with LAGand VRF


The mcRNC site configuration applied VLANs for logical traffic separation and VRFs forlogical routing functions separation. With VRFs and static routes it is possible to apply forexample a default route configuration for the user plane connections in case all the userplane goes out through the same gateway without affecting for example to Iu/Iur controlplane requiring a specific route entries. Ethernet Link Aggregation is applied to group1GE interfaces into a higher bandwidth logical interface allowing simplified IP addressingand easier load sharing over several physical links from EIPU node to router. All EIPUnodes terminate traffic from all logical interfaces (shared EIPU scheme).

Multicontroller RNC




152 DN0974301 Issue: 02G

– VLAN11 10.0.1.0/27


– VLAN12 10.0.1.32/27


– VLAN17 10.0.2.0/28– VLAN18 10.0.2.16/28


– VLAN21 10.0.4.0/27


– VLAN22 10.0.4.32/27

Application IP addresses are assigned to a certain recovery group (RG) instance, whichprovides the redundancy scheme for hardware and software failures. With VRRP/HSRPsite solution the user plane IP addresses are configured to VLAN interface subnet. TheIP address follows the active Recovery Unit (RU) of the QNUP RG. The Iu and Iur userplane addresses are presented in Table Iu and Iur user plane IP addresses.


RecoveryGroup

Iu-PS

Iu-CS

Iur

Iub

QNUP-0 10.0.1.4 10.0.1.14 10.0.1.24 10.0.4.4

QNUP-1 10.0.1.36 10.0.1.46 10.0.1.56 10.0.4.36

QNUP-2 10.0.1.5 10.0.1.15 10.0.1.25 10.0.4.5

QNUP-3 10.0.1.37 10.0.1.47 10.0.1.57 10.0.4.37







Issue: 02G DN0974301 153




VRRP/HSRP for site routers/switches (applied for user plane traffic):

Two VRRP/HSRP groups are applied for Iu/Iur user plane and Iub. The VRRP/HSRPpriorities have to be planned and configured properly in the routers to provide adequaterouter level traffic load sharing.


Core network and SIGTRAN

For Iu-PS, Iu-CS and Iur control plane configuration refer to Chapters 3.2 - 3.4.

Before you start

The mcRNC and site routers have been installed and all required connections have beenestablished. The site solution with VRRP/HSRP is described in mcRNC Site Solutionbased on Juniper with VRRP using 10 Gigabit Ethernet connectivity and mcRNC SiteSolution based on Juniper with VRRP using 1GE and 10GE connectivity documents.

The generic related parameters for the Iu-PS, Iu-CS, Iur and Iub can be seen from theChapters 3.2 – 3.5


g Before starting a new IP-layer configuration, check the existing IP-layer configuration.Use the show networking ether and show networking address SCLIcommands to show the current interface settings. If configuring the mcRNC using the IPplan, create and activate a plan in the mcRNC to have a basic configuration as astarting point for further modifications.

g To avoid IP-layer fragmentation, an MTU size of 1560 octets is recommended for the Iu-PS transport.

For more information on MTU, see WCDMA RAN IP Transport.


• SCLI commandsadd networking vrf name iuiurup1 id 5add networking vrf name iuiurup1 id 6


154 DN0974301 Issue: 02G

add networking vrf name iuiurcp id 1add networking vrf name iub1 id 11add networking vrf name iub2 id 12


• id = 11

2 Configure the physical interface.Physical network interfaces are assigned to a certain EIPU node, if not yetconfigured. The mcRNC default egress queue set rncdefault has to beassigned to the physical interface for proper default egress scheduling weightsconfiguration.

• SCLI commandsadd networking ether /EIPU-0 iface ethsfp13 port sfp13outqset rncdefault mtu 1560add networking ether /EIPU-0 iface ethsfp14 port sfp14outqset rncdefault mtu 1560add networking ether /EIPU-0 iface ethsfp15 port sfp15outqset rncdefault mtu 1560add networking ether /EIPU-0 iface ethsfp16 port sfp16outqset rncdefault mtu 1560add networking ether /EIPU-1 iface ethsfp13 port sfp13outqset rncdefault mtu 1560add networking ether /EIPU-1 iface ethsfp14 port sfp14outqset rncdefault mtu 1560add networking ether /EIPU-1 iface ethsfp15 port sfp15outqset rncdefault mtu 1560add networking ether /EIPU-1 iface ethsfp16 port sfp16outqset rncdefault mtu 1560add networking ether /EIPU-2 iface ethsfp17 port sfp17outqset rncdefault mtu 1560add networking ether /EIPU-2 iface ethsfp18 port sfp18outqset rncdefault mtu 1560add networking ether /EIPU-2 iface ethsfp19 port sfp19outqset rncdefault mtu 1560add networking ether /EIPU-2 iface ethsfp20 port sfp20outqset rncdefault mtu 1560add networking ether /EIPU-3 iface ethsfp17 port sfp17outqset rncdefault mtu 1560add networking ether /EIPU-3 iface ethsfp18 port sfp18outqset rncdefault mtu 1560add networking ether /EIPU-3 iface ethsfp19 port sfp19outqset rncdefault mtu 1560add networking ether /EIPU-3 iface ethsfp20 port sfp20outqset rncdefault mtu 1560

• IP PlanRelated object class: ETHERRNC-xx/IP-1/OWNER-EIPU-0/ETHER-ethsfp13

• port = sfp13• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mtu = 1560


Issue: 02G DN0974301 155

• outqset = rncdefault• vrf = default (default)(optional)


3 Configure the Ethernet Link Aggregation, LAG interfacesadd networking linkaggr /EIPU-0 iface lag1 slave ethsfp13slave ethsfp14 slave ethsfp15 slave ethsfp16 outqsetrncdefault mtu 1560

add networking linkaggr /EIPU-1 iface lag1 slave ethsfp13slave ethsfp14 slave ethsfp15 slave ethsfp16 outqsetrncdefault mtu 1560



4 Configure link state detector to the interfaces with QNUP and QNIUB ownerThe link state detector is configured to notify the QNUP Recovery Group about theinterface state changes. Once the interface state goes down the active RecoveryUnit of the RG instance is moved to the EIPU-pair node.

g NoteLink state detector configuration is mandatory for mcRNC VRRP/HSRP site solution. AtEIPU nodes the Link state detector is applied for 1GE, LAG or 10GE interface withhaving the QNUP as the owner.

• SCLI commands examples#Link state detector configurationadd networking link-state-detector /QNUP-0 iface ethsfp13iface ethsfp14 iface ethsfp15 iface ethsfp16add networking link-state-detector /QNUP-1 iface ethsfp13iface ethsfp14 iface ethsfp15 iface ethsfp16add networking link-state-detector /QNUP-2 iface ethsfp17iface ethsfp18 iface ethsfp19 iface ethsfp20add networking link-state-detector /QNUP-3 iface ethsfp17iface ethsfp18 iface ethsfp19 iface ethsfp20add networking link-state-detector /QNIUB-0 iface ethsfp13iface ethsfp14 iface ethsfp15 iface ethsfp16add networking link-state-detector /QNIUB-1 iface ethsfp13iface ethsfp14 iface ethsfp15 iface ethsfp16add networking link-state-detector /QNIUB-2 iface ethsfp17iface ethsfp18 iface ethsfp19 iface ethsfp20add networking link-state-detector /QNIUB-3 iface ethsfp17iface ethsfp18 iface ethsfp19 iface ethsfp20



156 DN0974301 Issue: 02G


• SCLI commands#vlan 11&12, iu iur user planeadd networking instance iuiurup1 vlan /EIPU-0 realifacelag1 vid 11 vlaniface iuiurup_vl11 mapping vlandscptopcpmtu 1560add networking instance iuiurup2 vlan /EIPU-0 realifacelag1 vid 12 vlaniface iuiurup_vl12 mapping vlandscptopcpmtu 1560add networking instance iuiurup1 vlan /EIPU-1 realifacelag1 vid 11 vlaniface iuiurup_vl11 mapping vlandscptopcpmtu 1560add networking instance iuiurup2 vlan /EIPU-1 realifacelag1 vid 12 vlaniface iuiurup_vl12 mapping vlandscptopcpmtu 1560

g The same can be repeated for the rest of the EIPU nodes.

#vlan 15 - 18, iu iur control planeadd networking instance iuiurcp vlan /EIPU-0 realiface lag1vid 15 vlaniface iuiurcp_vl15 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-1 realiface lag1vid 16 vlaniface iuiurcp_vl16 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-0 realiface lag1vid 17 vlaniface iuiurcp_vl17 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-1 realiface lag1vid 18 vlaniface iuiurcp_vl18 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-2 realiface lag1vid 17 vlaniface iuiurcp_vl17 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-3 realiface lag1vid 18 vlaniface iuiurcp_vl18 mapping vlandscptopcp#vlan 21&22, iub control and user planeadd networking instance iub1 vlan /EIPU-0 realiface lag1vid 21 vlaniface iub_vl21 mapping vlandscptopcpadd networking instance iub2 vlan /EIPU-0 realiface lag1vid 22 vlaniface iub_vl22 mapping vlandscptopcpadd networking instance iub1 vlan /EIPU-1 realiface lag1vid 21 vlaniface iub_vl21 mapping vlandscptopcpadd networking instance iub2 vlan /EIPU-1 realiface lag1vid 22 vlaniface iub_vl22 mapping vlandscptopcp



• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mapping = vlandscptopcp• mtu = 1560• realiface = lag1


Issue: 02G DN0974301 157

• vid = 11• vrf = iuiurup1



• Scli commands#VLANs 17 and 18add networking instance iuiurcp address dedicated /EIPU-0iface iuiurcp_vl17 ip-address 10.1.8.2/28add networking instance iuiurcp address dedicated /EIPU-1iface iuiurcp_vl18 ip-address 10.1.8.130/28add networking instance iuiurcp address dedicated /EIPU-2iface iuiurcp_vl17 ip-address 10.1.8.3/28add networking instance iuiurcp address dedicated /EIPU-3iface iuiurcp_vl18 ip-address 10.1.8.131/28Repeat the same for Iu-CS and Iur interfaces related addresses.



7 Configure application IP addresses for user planeWith VRRP/HSRP site solution the user plane and Iub control plane application IPaddresses are assigned to VLAN interface subnet. The user plane application IPaddresses belong to router local subnets and the IP address is present in thenode/unit that is running the service at the time (active recovery unit, RU).

g The VLAN interface names belonging to the same subnet have to be the same in bothEIPU nodes of the EIPU pair. This is to allow configuration of the logical IP address thatfollows active RU of the QNUP RG. Along with the RG switchover the related IPaddress moves to the new node. Within the service switchover the new MAC address isto be reported with gratuitous ARP to site routers.



• SCLI commands#Iu-PS user plane IP addresses, VRF iuiurupadd networking instance iuiurup1 address dedicated /QNUP-0iface iuiurup_vl11 ip-address 10.0.1.4/27 role iupsupadd networking instance iuiurup2 address dedicated /QNUP-1iface iuiurup_vl12 ip-address 10.0.1.36/27 role iupsup


158 DN0974301 Issue: 02G

add networking instance iuiurup1 address dedicated /QNUP-2iface iuiurup_vl11 ip-address 10.0.1.5/27 role iupsupadd networking instance iuiurup2 address dedicated /QNUP-3iface iuiurup_vl12 ip-address 10.0.1.37/27 role iupsup#Iu-CS user plane IP addresses, VRF iuiurupadd networking instance iuiurup1 address dedicated /QNUP-0iface iuiurup_vl11 ip-address 10.0.1.14/27 role iucsupadd networking instance iuiurup2 address dedicated /QNUP-1iface iuiurup_vl12 ip-address 10.0.1.46/27 role iucsupadd networking instance iuiurup1 address dedicated /QNUP-2iface iuiurup_vl11 ip-address 10.0.1.15/27 role iucsupadd networking instance iuiurup2 address dedicated /QNUP-3iface iuiurup_vl12 ip-address 10.0.1.47/27 role iucsup#Iur user plane IP addresses, VRF iuiurupadd networking instance iuiurup1 address dedicated /QNUP-0iface iuiurup_vl11 ip-address 10.0.1.24/27 role iurupadd networking instance iuiurup2 address dedicated /QNUP-1iface iuiurup_vl12 ip-address 10.0.1.56/27 role iurupadd networking instance iuiurup1 address dedicated /QNUP-2iface iuiurup_vl11 ip-address 10.0.1.25/27 role iurupadd networking instance iuiurup2 address dedicated /QNUP-3iface iuiurup_vl12 ip-address 10.0.1.57/27 role iurup#Iub control and user plane IP addresses, VRF iubadd networking instance iub1 address dedicated /QNUP-0iface iub_vl21 ip-address 10.0.4.4/27 role iubupadd networking instance iub2 address dedicated /QNUP-1iface iub_vl22 ip-address 10.0.4.36/27 role iubupadd networking instance iub1 address dedicated /QNUP-2iface iub_vl21 ip-address 10.0.4.5/27 role iubupadd networking instance iub2 address dedicated /QNUP-3iface iub_vl22 ip-address 10.0.4.37/27 role iubupadd networking instance iub1 address dedicated /QNIUB-0iface iub_vl21 ip-address 10.0.4.20/27 role iubcpadd networking instance iub2 address dedicated /QNIUB -1iface iub_vl22 ip-address 10.0.4.52/27 role iubcpadd networking instance iub1 address dedicated /QNIUB -2iface iub_vl21 ip-address 10.0.4.21/27 role iubcpadd networking instance iub2 address dedicated /QNIUB -3iface iub_vl22 ip-address 10.0.4.53/27 role iubcp



8 Configure IP addresses for Iu and Iur control plane sctp interfacesThe Iu/Iur Control plane IP addresses are configured to sctp1 and sctp2 interfaces atbackplane side (sctp1_1 and sctp2_1 for the VRF id 1). The control plane subnetsspan over all EIPU nodes (or over the planned nodes) providing the possibility toreach the service through any EIPU node without additional static routesconfiguration.


Issue: 02G DN0974301 159

The SIGTRAN related SCTP associations should be located as evenly as possiblewithin the EIPU nodes. At least four EIPU nodes should be applied towards one CNpeer element and the SCTP associations towards different CN / neighbor RNCelements should be distributed evenly in between all EIPU nodes.

g The SCTP association is terminated to a certain EIPU node. The IP addresses of SCTPMulti-Homed association are configured to the interface from where the outgoingSCTP/SIGTRAN traffic is forwarded out. The sctp1_[VRF-id] and sctp2_[VRF-id]interfaces are preconfigured to the mcRNC. Four first VRFs including the default VRF(VRF id 0 - 3) contain the sctp interfaces and they can be applied for the Iu/Iur controlplane configuration.







• mask = 28


160 DN0974301 Issue: 02G

• vrf = iuiurcp• role = iupscp

9 Configure the static routesThe following static routes have to be configured to the system. The VRRP/HSRPvirtual IP address is to be used as user plane traffic gateway towards the peerelement. The site routers interface addresses are applied as gateways for the Iucontrol plane multi-homed connections.

• User plane traffic: Destination subnets are reached through VRRP/HSRP virtualIP as gateway. The default route can be applied within a user plane VRF.

• Control plane traffic: Destination subnets are reached through site router or EIPUbackplane interface address as gateway. The table presents the static routesneeded towards the Iu-PS control plane.

Configure the other control plane static routes with similar logics

• Static routes for ingress traffic through the backplane are not needed

– Static routes for ingress traffic through the backplane are not needed– Iu/Iur control plane the SCTP IP addresses are located to local subnets of the

EIPU nodes thus no static routes needed at ingress direction


Node

VRF

Network Id

Priority

Gateway

Notes









EIPU-0 iub1 default 0 10.0.1.1 Iub control and userplane




Issue: 02G DN0974301 161


Node

VRF

Network Id

Priority

Gateway

Notes






EIPU-0 iuiurcp 10.8.0.0/24 0 10.1.8.1 Iu-PS control plane,EIPU-0 and router-1 asGW to first destinationCP subnet

EIPU-0 iuiurcp 10.8.1.0/24 0 10.1.8.146 Iu-PS control plane,router-1 as GW tosecond destination CPsubnet




EIPU-2 iuiurcp 10.8.1.0/24 0 10.1.8.146 Iu-PS control plane,through EIPU-1 androuter-2 as GW tosecond destination CPsubnet



162 DN0974301 Issue: 02G


Node

VRF

Network Id

Priority

Gateway

Notes

EIPU-3 iuiurcp 10.8.1.0/24 0 10.1.8.129 Iu-PS control plane,through EIPU-1 androuter-2 as GW tosecond destination CPsubnet

• SCLI commands#User plane, routes might serve several destination CN elements depending onthe network planningset routing instance iuiurup1 node EIPU-0 static-routedefault nexthop gateway address 10.0.1.1 onset routing instance iuiurup2 node EIPU-0 static-routedefault nexthop gateway address 10.0.1.33 onset routing instance iuiurup1 node EIPU-1 static-routedefault nexthop gateway address 10.0.1.1 onset routing instance iuiurup2 node EIPU-1 static-routedefault nexthop gateway address 10.0.1.33 onset routing instance iuiurup1 node EIPU-2 static-routedefault nexthop gateway address 10.0.1.1 onset routing instance iuiurup2 node EIPU-2 static-routedefault nexthop gateway address 10.0.1.33 onset routing instance iuiurup1 node EIPU-3 static-routedefault nexthop gateway address 10.0.1.1 onset routing instance iuiurup2 node EIPU-3 static-routedefault nexthop gateway address 10.0.1.33 on

g Configure all Iu and Iur user plane and Iub control and user plane routes with sameprinciples to all related EIPU nodes

#Control plane, routes might serve several destination CN elements dependingon the network planningset routing instance iuiurcp node EIPU-0 static-route10.8.0.0/24 nexthop gateway address 10.1.8.1 onset routing instance iuiurcp node EIPU-0 static-route10.8.1.0/24 nexthop gateway address 10.1.8.146 onset routing instance iuiurcp node EIPU-1 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 onset routing instance iuiurcp node EIPU-1 static-route10.8.1.0/24 nexthop gateway address 10.1.8.129 onset routing instance iuiurcp node EIPU-2 static-route10.8.0.0/24 nexthop gateway address 10.1.8.1 onset routing instance iuiurcp node EIPU-2 static-route10.8.1.0/24 nexthop gateway address 10.1.8.146 onset routing instance iuiurcp node EIPU-3 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 onset routing instance iuiurcp node EIPU-3 static-route10.8.1.0/24 nexthop gateway address 0.1.8.129 on


Issue: 02G DN0974301 163

g Configure all Iu and Iur control plane routes with same principles to all needed EIPUnodes

– IP PlanRelated object class: SRT4, ADR4GWRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup1/SRT4-default

– nexthop = 2 (gateway)RNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup1/SRT4-default/ADR4GW-10.0.1.1

– No attributes needed, default values are appliedRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup2/SRT4-default


– No attributes needed, default values are applied


– nexthop = 2 (gateway)







10 Configure user plane resources, IP-based route configurationFor IP Based Route configuration at Iu, Iur and Iub interfaces please refer tochapters 3.2 – 3.5. The following steps describe the Iu-PS interface configuration asan example.


If a user plane non-load sharing configuration is applied, proceed as followsAssign a single IP address to the IP-based route 1 for the Iu-PS user plane source IPaddress selection.add ipro ipbr-id 1 ip-address 10.0.1.17 iface iups_vl11 owner/QNUP-0 vrf iuiurup1

If a user plane IP Based Route load sharing configuration is applied, proceedas follows.Assign several IP addresses to the IP-based route 1 for the Iu-PS user plane sourceIP address selection.add ipro ipbr-id 1 ip-address 10.0.1.4 iface iuiurup_vl11owner /QNUP-0 vrf iuiurup1


164 DN0974301 Issue: 02G

add ipro ipbr-id 1 ip-address 10.0.1.36 iface iuiurup_vl12owner /QNUP-1 vrf iuiurup2





RNC-xx/IP-1/OWNER-QNUP-0/IPRO-1-10.0.1.4-iuiurup_vl11• vrfId = iuiurup1

RNC-xx/IP-1/OWNER-QNUP-1/IPRO-1-10.0.1.36-iuiurup_vl12 (… moreinstances configured with IPBR load sharing)

• vrfId = iuiurup2

11 Configure control plane resourcesFor the Iu/Iur control plane resources creation refer to chapter 3.2.

12 Check and configure QoS related resourcesIn most cases using the default QoS values is sufficient, but depending on networkarchitecture and further QoS constraints, the values need to be reviewed andpossibly adjusted. For more information, see the QoS configuration chapter.

13 Configure the Radio Network layer informationWith RNW configuration for Iu-PS, Iu-CS, Iur and Iub please refer to correspondingchapters 3.2.

3.7 Configuring mcRNC VRRP/HSRP SiSo, VRF, 10GE,1GE with LAG and dedicated EIPUPurpose

To configure the Iu, Iur and Iub interface with the VRRP/HSRP site solution, VirtualRouting and Forwarding (VRF), 10GE interfaces and 1GE with LAG functionalities.

The following optional features is required:

• RAN2256 Ethernet Link Aggregation for mcRNC


Issue: 02G DN0974301 165



The configuration example is presented with mcRNC capacity step s1 and withdedicated EIPU setup. Dedicated EIPU setup means the certain EIPU nodes arephysically connected to a certain neighbor elements like CS/PS core. The given EIPUnodes provide the user plane connectivity. The Iu/Iur control plane is distributed over allEIPU nodes in order to share the SIGTRAN load. Here the Iu/Iur connectivity isconfigured with 10GE interfaces while the Iub direction is configured with 1GE andEthernet Link Aggregation. The dedicated EIPU configuration can be applied to graduallytake the 10GE interfaces in use or in case operator has separate physical routers todifferent domains.

The example configuration can be applied for planning and configuring bigger capacitysteps with using the presented design pattern for further needed EIPU nodes. Theconfiguration and connectivity principles apply as per EIPU pair basis.

The Virtual Routing and Forwarding instances are logically separate routing processeswithin the EIPU with separate routing tables and interfaces. VRF instances are used tokeep routing information, IP addressing, and IP interfaces logically separated betweendifferent logical interfaces. For the user plane connections within one VRF, a simplifieddefault route-based configuration can be applied to avoid mcRNC static routeconfiguration changes if the neighbor network element allocations and destination IPaddresses change. With default route configuration the amount of needed static routesfor the user plane is decreased to minimum.


The configuration examples in the instructions are based on the IP addressing presentedin . VRFs are applied for different domains: Iu and Iur user plane, Iu and Iur control planeand Iub control and user plane.


166 DN0974301 Issue: 02G


Figure 36 Network configuration for mcRNC VRRP/HSRP SiSo with 10GE, LAG andVRF

The detailed configuration for the Iub interface is presented in . One IP address from theVLAN interface subnet is bound to each QNUP and QNIUB instance. Separate IPaddresses are applied for Iub user plane and Iub control plane in order to allowindependent failure actions for the services. The related IP addresses and VLANinterfaces belong to “iub” VRF.


Issue: 02G DN0974301 167


Figure 37 Iub configuration for mcRNC VRRP/HSRP SiSo with 10GE,LAG and VRF

Detailed figure for Iu-PS, Iu-CS and Iur user plane IP addressing is presented in .Separate IP addresses are applied for the Iu-CS, Iu-PS and Iur user plane traffic IP layertermination. The related IP addresses and VLAN interfaces belong to “iuiurup” VRF.


168 DN0974301 Issue: 02G


Figure 38 Iu/Iur User Plane configuration for mcRNC VRRP/HSRP SiSo with 10GE,LAG and VRF

The Iu-PS, Iu-CS and Iur control plane SCTP associations and related IP addressing ispresented in . The SCTP IP addresses are configured to EIPU backplane cfeigwinterfaces. Certain EIPU nodes are selected to work as gateways for the Iu/Iur controlplane traffic. The related IP addresses and VLAN interfaces belong to “iuiurcp” VRF.


Issue: 02G DN0974301 169


Figure 39 Iu/Iur Control Plane configuration for mcRNC VRRP/HSRP SiSo with10GE, LAG and VRF


The mcRNC site configuration applied VLANs for logical traffic separation and VRFs forlogical routing functions separation. With VRFs and static routes it is possible to apply forexample a default route configuration for the user plane connections in case all the userplane goes out via the same gateway without affecting for example to Iu/Iur control planerequiring a specific route entries. Ethernet Link Aggregation is applied to group 1GEinterfaces into a higher bandwidth logical interface allowing simplified IP addressing andeasier load sharing over several physical links from EIPU node to router. All EIPU nodesterminate traffic from all logical interfaces (shared EIPU scheme).

Multicontroller RNC




170 DN0974301 Issue: 02G

– VLAN11 10.0.1.0/27


–


– VLAN17 10.0.2.0/28– VLAN18 10.0.2.16/28


– VLAN21 10.0.4.0/27


– VLAN22 10.0.4.32/27

Application IP addresses are assigned to a certain recovery group (RG) instance, whichprovides the redundancy scheme for hardware and software failures. With VRRP/HSRPsite solution the user plane IP addresses are configured to VLAN interface subnet. TheIP address follows the active Recovery Unit (RU) of the QNUP RG. The Iu and Iur userplane addresses are presented in .


RecoveryGroup

Iu-PS

Iu-CS

Iur

Iub

QNUP-0 10.0.1.4 10.0.1.14 10.0.1.24

QNUP-1 10.0.1.36 10.0.1.46 10.0.1.56

QNUP-2 10.0.4.4

QNUP-3 10.0.4.36



• Iu-CS control plane, SCTP associations




Issue: 02G DN0974301 171





VRRP/HSRP for site routers/switches (applied for user plane traffic):Two VRRP/HSRPgroups are applied for Iu/Iur user plane and Iub. The VRRP/HSRP priorities have to beplanned and configured properly in the routers to provide adequate router level trafficload sharing.


Core network and SIGTRAN

For Iu-PS, Iu-CS and Iur control plane configuration refer to Chapters 3.2 - 3.4.

Before you start

The mcRNC and site routers have been installed and all required connections have beenestablished. The site solution with VRRP/HSRP is described in mcRNC Site Solutionbased on Juniper EX4500 with VRRP using 10 Gigabit Ethernet connectivity andmcRNC Site Solution based on Juniper EX4500 with VRRP using 1GE and 10GEconnectivity documents.

The generic related parameters for the Iu-PS, Iu-CS, Iur and Iub can be seen from theChapters 3.2 – 3.5


g Before starting a new IP-layer configuration, check the existing IP-layer configuration.Use the show networking ether and show networking address SCLIcommands to show the current interface settings. If configuring the mcRNC using the IPplan, create and activate a plan in the mcRNC to have a basic configuration as astarting point for further modifications.

g To avoid IP-layer fragmentation, an MTU size of 1560 octets is recommended for the Iu-PS transport.



• SCLI commandsadd networking vrf name iuiurup1 id 5add networking vrf name iuiurup2 id 6


172 DN0974301 Issue: 02G

add networking vrf name iuiurcp id 1add networking vrf name iub1 id 11add networking vrf name iub2 id 12


• id = 10

2 Configure the physical interface.Physical network interfaces are assigned to a certain EIPU node, if not yetconfigured. The mcRNC default egress queue set rncdefault has to be assigned tothe physical interface for proper default egress scheduling weights configuration. The10GE physical ports within the BCN module are sfp11 and sfp12.

• SCLI commands#Configure 10GE portsadd networking ether /EIPU-0 iface ethsfp10ge port sfp11outqset rncdefault mtu 1560add networking ether /EIPU-1 iface ethsfp10ge port sfp11outqset rncdefault mtu 1560#Configure 1GE portsadd networking ether /EIPU-2 iface ethsfp17_r1 port sfp17outqset rncdefaultadd networking ether /EIPU-2 iface ethsfp18_r1 port sfp18outqset rncdefaultadd networking ether /EIPU-2 iface ethsfp19_r1 port sfp19outqset rncdefaultadd networking ether /EIPU-2 iface ethsfp20_r1 port sfp20outqset rncdefaultadd networking ether /EIPU-3 iface ethsfp17_r1 port sfp17outqset rncdefaultadd networking ether /EIPU-3 iface ethsfp18_r1 port sfp18outqset rncdefaultadd networking ether /EIPU-3 iface ethsfp19_r1 port sfp19outqset rncdefaultadd networking ether /EIPU-3 iface ethsfp20_r1 port sfp20outqset rncdefault

• IP PlanRelated object class: ETHERRNC-xx/IP-1/OWNER-EIPU-0/ETHER-ethsfp11_r1

• port = sfp11• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mtu = 1560• outqset = rncdefault• vrf = default



Issue: 02G DN0974301 173

3 Configure the Ethernet Link Aggregation, LAG interfacesadd networking linkaggr /EIPU-2 iface lag23 slave ethsfp17_r1slave ethsfp18_r1 slave ethsfp19_r1 slave ethsfp20_r1 outqsetrncdefaultadd networking linkaggr /EIPU-3 iface lag23 slave ethsfp17_r2slave ethsfp18_r2 slave ethsfp19_r2 slave ethsfp20_r2 outqsetrncdefault

4 Configure link state detector to the interfaces with QNUP and QNIUB ownerThe link state detector is configured to notify the QNUP Recovery Group about theinterface state changes. Once the interface state goes down the active RecoveryUnit of the RG instance is moved to the EIPU-pair node.

g NoteLink state detector configuration is mandatory for mcRNC VRRP/HSRP site solution. AtEIPU nodes the Link state detector is applied for 1GE, LAG or 10GE interface withhaving the QNUP as the owner.

• SCLI commands examples#Link state detector configurationadd networking link-state-detector /QNUP-0 iface ethsfp11





dd networking link-state-detector /QNIUB-1 iface ethsfp11




5 Configure VLAN interfacesThe VLAN interface is created for a certain physical interface/LAG interface with areference to its name. The VLAN ids and the VLAN interface names have to beplanned and configured accordingly.

• SCLI commands#vlan 11&12, iu iur user planeadd networking instance iuiurup1 vlan /EIPU-0 realifaceethsfp10ge vid 11 vlaniface iuiurup_vl11 mappingvlandscptopcp


174 DN0974301 Issue: 02G

add networking instance iuiurup2 vlan /EIPU-0 realifaceethsfp10ge vid 12 vlaniface iuiurup_vl12 mappingvlandscptopcpadd networking instance iuiurup1 vlan /EIPU-1 realifaceethsfp10ge vid 11 vlaniface iuiurup_vl11 mappingvlandscptopcpadd networking instance iuiurup2 vlan /EIPU-1 realifaceethsfp10ge vid 12 vlaniface iuiurup_vl12 mappingvlandscptopcp


#vlan 17&18, iu iur control planeadd networking instance iuiurcp vlan /EIPU-0 realifacelag01 vid 17 vlaniface iuiurcp_vl17 mapping vlandscptopcpadd networking instance iuiurcp vlan /EIPU-1 realifacelag01 vid 18 vlaniface iuiurcp_vl18 mapping vlandscptopcp#vlan 21&22, iub control and user planeadd networking instance iub1 vlan /EIPU-0 realiface lag23vid 21 vlaniface iub_vl21 mapping vlandscptopcpadd networking instance iub2 vlan /EIPU-0 realiface lag23vid 22 vlaniface iub_vl22 mapping vlandscptopcpadd networking instance iub1 vlan /EIPU-1 realiface lag23vid 21 vlaniface iub_vl21 mapping vlandscptopcpadd networking instance iub2 vlan /EIPU-1 realiface lag23vid 22 vlaniface iub_vl22 mapping vlandscptopcp


• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mapping = vlandscptopcp• mtu = 1560• realiface = lag01• vid = 11• vrf = iuiurup1



• SCLI commands#VLANs 17 and 18add networking instance iuiurcp address dedicated /EIPU-0iface iuiurcp_vl17 ip-address 10.0.2.2/28add networking instance iuiurcp address dedicated /EIPU-1iface iuiurcp_vl18 ip-address 10.0.2.18/28



Issue: 02G DN0974301 175


7 Configure application IP addresses for user planeWith VRRP/HSRP site solution the user plane and Iub control plane application IPaddresses are assigned to VLAN interface subnet. The user plane application IPaddresses belong to router local subnets and the IP address is present in thenode/unit that is running the service at the time (active recovery unit, RU).

g The VLAN interface names belonging to the same subnet have to be the same in bothEIPU nodes of the EIPU pair. This is to allow configuration of the logical IP address thatwill follow active RU of the QNUP RG. Along with the RG switchover the related IPaddress will move to the new node. Within the service switchover the new MACaddress will be reported with gratuitous ARP to site routers.



• SCLI commands#Iu-PS user plane IP addresses, VRF iuiurupadd networking instance iuiurup1 address dedicated /QNUP-0iface iuiurup_vl11 ip-address 10.0.1.4/27 role iupsupadd networking instance iuiurup2 address dedicated /QNUP-1iface iuiurup_vl12 ip-address 10.0.1.36/27 role iupsup#Iu-CS user plane IP addresses, VRF iuiurupadd networking instance iuiurup1 address dedicated /QNUP-0iface iuiurup_vl11 ip-address 10.0.1.14/27 role iucsupadd networking instance iuiurup2 address dedicated /QNUP-1iface iuiurup_vl12 ip-address 10.0.1.46/27 role iucsup#Iur user plane IP addresses, VRF iuiurupadd networking instance iuiurup1 address dedicated /QNUP-0iface iuiurup_vl11 ip-address 10.0.1.24/27 role iurupadd networking instance iuiurup2 address dedicated /QNUP-1iface iuiurup_vl12 ip-address 10.0.1.56/27 role iurup#Iub control and user plane IP addresses, VRF iubadd networking instance iub1 address dedicated /QNUP-2iface iub_vl21 ip-address 10.0.4.4/27 role iubupadd networking instance iub2 address dedicated /QNUP-3iface iub_vl22 ip-address 10.0.4.36/27 role iubupadd networking instance iub1 address dedicated /QNIUB-2iface iub_vl21 ip-address 10.0.4.20/27 role iubcpadd networking instance iub2 address dedicated /QNIUB -3iface iub_vl22 ip-address 10.0.4.52/27 role iubcp




176 DN0974301 Issue: 02G

8 Configure IP addresses for Iu and Iur control planeThe Iu/Iur Control plane IP addresses are configured to sctp1 and sctp2 interfaces atbackplane side (sctp1_1 and sctp2_1 for the VRF id 1). The control plane subnetsspan over all EIPU nodes (or over the planned nodes) providing the possibility toreach the service via any EIPU node without additional static routes configuration.The SIGTRAN related SCTP associations should be located as evenly as possiblewithin the EIPU nodes. At least four EIPU nodes should be applied towards one CNpeer element and the SCTP associations towards different CN / neighbor RNCelements should be distributed evenly in between all EIPU nodes.

g The SCTP association is terminated to a certain EIPU node. The IP addresses of SCTPMulti-Homed association are configured to the interface from where the outgoingSCTP/SIGTRAN traffic is forwarded out. The sctp1_[VRF-id] and sctp2_[VRF-id]interfaces are pre configured to the mcRNC. Four first VRFs including the default VRF(VRF id 0 - 3) contain the sctp interfaces and they can be applied for the Iu/Iur controlplane configuration.






Issue: 02G DN0974301 177





• User plane traffic: Destination subnets are reached via VRRP/HSRP virtual IP asgateway. The default route can be applied within a user plane VRF.


g Configure the other control plane static routes with similar logics


– With user plane the traffic is terminated at address located to VLAN interfacethus there is no need for redundant ingress routes via backplane.

– With control plane the SCTP IP addresses are located to local subnets of theEIPU nodes.


Node

VRF

Network Id

Priority

Gateway

Notes










178 DN0974301 Issue: 02G


Node

VRF

Network Id

Priority

Gateway

Notes









EIPU-0 iuiurcp 10.8.0.0/24 0 10.1.8.1 Iu-PS control plane,router-1 as GW to firstdestination CP subnet

EIPU-0 iuiurcp 10.8.1.0/24 0 10.1.8.146 Iu-PS control plane, viaEIPU-1 and router-2 asGW to seconddestination CP subnet





Issue: 02G DN0974301 179


Node

VRF

Network Id

Priority

Gateway

Notes




• SCLI commands#User plane, routes may serve several destination CN elements depending onthe network planningset routing instance iuiurup1 node EIPU-0 static-routedefault nexthop gateway address 10.0.1.1 onset routing instance iuiurup2 node EIPU-0 static-routedefault nexthop gateway address 10.0.1.33 onset routing instance iuiurup1 node EIPU-1 static-routedefault nexthop gateway address 10.0.1.1 onset routing instance iuiurup2 node EIPU-1 static-routedefault nexthop gateway address 10.0.1.33 onset routing instance iuiurup1 node EIPU-2 static-routedefault nexthop gateway address 10.0.1.1 onset routing instance iuiurup2 node EIPU-2 static-routedefault nexthop gateway address 10.0.1.33 onset routing instance iuiurup1 node EIPU-3 static-routedefault nexthop gateway address 10.0.1.1 onset routing instance iuiurup2 node EIPU-3 static-routedefault nexthop gateway address 10.0.1.33 on

g Configure all Iu and Iur user plane and Iub control and user plane routes with sameprinciples to all related EIPU nodes

#Control plane, routes may serve several destination CN elements depending onthe network planningset routing instance iuiurcp node EIPU-0 static-route10.8.0.0/24 nexthop gateway address 10.1.8.1 onset routing instance iuiurcp node EIPU-0 static-route10.8.1.0/24 nexthop gateway address 10.1.8.146 onset routing instance iuiurcp node EIPU-1 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 onset routing instance iuiurcp node EIPU-1 static-route10.8.1.0/24 nexthop gateway address 10.0.1.129 onset routing instance iuiurcp node EIPU-2 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 on


180 DN0974301 Issue: 02G

set routing instance iuiurcp node EIPU-2 static-route10.8.1.0/24 nexthop gateway address 10.1.8.145 onset routing instance iuiurcp node EIPU-3 static-route10.8.0.0/24 nexthop gateway address 10.1.8.17 onset routing instance iuiurcp node EIPU-3 static-route10.8.1.0/24 nexthop gateway address 10.1.8.145 on

g Configure all Iu and Iur control plane routes with same principles to all needed EIPUnodes

– IP PlanRelated object class: SRT4, ADR4GWRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup11/SRT4-default


– No attributes needed, default values are appliedRNC-xx/IP-1/OWNER-EIPU-0/RTINST-iuiurup12/SRT4-default











10 Configure user plane resources, IP-based route configurationFor IP Based Route configuration at Iu, Iur and Iub interfaces please refer tochapters 3.2 – 3.5. The following steps describe the Iu-PS interface configuration asan example.


If a user plane non-load sharing configuration is applied, proceed as follows.Assign several IP addresses to the IP-based route 1 for the Iu-PS user plane sourceIP address selection.add ipro ipbr-id 1 ip-address 10.0.1.17 iface iups_vl11 owner/QNUP-0 vrf iuiurup1


Issue: 02G DN0974301 181

If a user plane IP Based Route load sharing configuration is applied, proceedas follows.Assign several IP addresses to the IP-based route 1 for the Iu-PS user plane sourceIP address selection.add ipro ipbr-id 1 ip-address 10.0.1.4 iface iuiurup_vl11owner /QNUP-0 vrf iuiurup1




RNC-xx/IP-1/OWNER-QNUP-0/IPRO-1-10.0.1.4-iuiurup_vl11• vrf = iuiurup1

RNC-xx/IP-1/OWNER-QNUP-1/IPRO-1-10.0.1.36-iuiurup_vl12 (more instancesconfigured with IPBR load sharing)

• vrf = iuiurup1

11 Configure control plane resourcesFor the Iu/Iur control plane resources creation refer to chapter 3.2.


13 Configure the Radio Network layer informationWith RNW configuration for Iu-PS, Iu-CS, Iur and Iub please refer to correspondingchapters 3.2.

3.8 Configuring Iu, Iur, and Iub interfaces with mcRNCEvolved Site SolutionPurpose

This section describes how to configure the Iu, Iur, and Iub interface with the mcRNCevolved Site Solution. The evolved site solution provides support for L2 VLANs spanningseveral network interface units (EIPU) and site routers supporting only 1GE interfaces.


182 DN0974301 Issue: 02G

Therefore this option is not suitable if the operator is planning to use 10 GE in the future.BFD single-hop (RAN2440 Fast IP rerouting) sessions bound to static routes are used tosupervise connectivity at the L3 level from the both mcRNC and site routers’ side. Theoverall number of VLANs needed for the logical traffic separation is smaller compared tothe mcRNC basic site solution.

The configuration instructions within this section list only the main differences comparedto steps already listed in Configuring Iu-PS interface, mcRNC basic SiSo, Configuring Iu-CS interface, mcRNC basic SiSo, Configuring Iur interface, mcRNC basic SiSo andConfiguring Iub interface, mcRNC basic SiSo for the basic Site Solution. The IP layerconfiguration, Iu/Iur signaling, and RNW attribute configuration is the same as themcRNC basic Site Solution.

The main building blocks are the following:

• L2 VLAN interfaces are used in the site routers (mcRNC basic site solution is basedon L3 VLAN subinterfaces).

• L2 domain is spans the area between one site router and mcRNC network interfaceunits (EIPU) that can be located in several BCN modules.

• The same VLANs are shared by different mcRNC network interface units (EIPU).• BFD (single hop) is deployed to supervise network connectivity between the mcRNC

and the site routers.

References:

mcRNC basic site solution: Configuring mcRNC IP Site Solution Based on Cisco 76xxSite Routers and mcRNC evolved site solution: Evolved mcRNC Site Solution.


The configuration examples in the instructions are based on the IP addressing presentedin Figure 40: Network configuration for Iu, Iur, and Iub with evolved site solution. Theapplication IP addresses present the Iu-PS interface-related addressing, while the VLANinterface addressing presents all logical interface (Iu/Iur/Iub) configurations.


Issue: 02G DN0974301 183

Figure 40 Network configuration for Iu, Iur, and Iub with evolved site solution

The instructions are based on the following network setup:

Multicontroller RNC

Traffic is logically separated in between the mcRNC and site routers with VLANs. TheVLAN configuration is the following:

• Iu-PS

– VLAN11 10.0.1.0/27– VLAN12 10.0.1.32/27

• Iu-CS

– VLAN13 10.0.2.0/27– VLAN14 10.0.2.32/27

• Iur


184 DN0974301 Issue: 02G

– VLAN15 10.0.3.0/27– VLAN16 10.0.3.32/27

• Iub

– VLAN21 10.0.4.0/27– VLAN22 10.0.4.32/27

For the application IP addresses, only the Iu-PS source addresses are presented here.For other logical interfaces, the addressing follows the same principles as in sectionsConfiguring Iu-PS interface, mcRNC basic SiSo, Configuring Iu-CS interface, mcRNCbasic SiSo, Configuring Iur interface, mcRNC basic SiSo and Configuring Iub interface,mcRNC basic SiSo with the exception that the Iu/Iur control plane addresses are nowallocated from the VLAN interface reserved for the particular logical interface.

Application IP addresses are assigned to a certain recovery group (RG) instance, whichprovides the redundancy scheme for hardware and software failures. In the followingconfiguration example, RG instances QNUP-0 and QNUP-1 are used for the Iu-PS userplane.

• Iu-PS user plane, QNUP-0, and QNUP-1 RG instances• QNUP-0: 10.1.1.1• 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 mightoriginate from multiple sources in the RNC and might even use different networkinterfaces. As a consequence, the traffic for this IP-based route might be processed inmultiple (interface) schedulers and egress traffic shaping for the total traffic of this IP-based route can no longer be provided.

• Iu-PS control plane, two SCTP associations; network interface IP addresses areapplied for the SCTP multi-homed connections

– SCTP association-1

• IP address 1: 10.0.1.2• IP address 2: 10.0.1.34

– SCTP association-2

• IP address 1: 10.0.1.3• IP address 2: 10.0.1.35• router-1 gateway IP addresses in VLAN11: 10.0.1.1• router-2 gateway IP addresses in VLAN12: 10.0.1.33

Core network Iu-PS

• 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 Iu-PS


Issue: 02G DN0974301 185

• RNC SPC

– 310 (Dec)

• SGSN SPC

– 500 (Dec)

Before you start

The mcRNC and site routers have been installed and all required connections have beenestablished. A recommended site solution is described in mcRNC evolved site solution:Evolved mcRNC Site Solution.

Configuration of the object classes related to the Radio Network database remains thesame as presented in sections Configuring Iu-PS interface, mcRNC basic SiSo,Configuring Iu-CS interface, mcRNC basic SiSo, Configuring Iur interface, mcRNC basicSiSo and Configuring Iub interface, mcRNC basic SiSo.


g Before starting a new IP layer configuration, check the existing IP layer configuration.Use the show networking ether and show networking address SCLIcommands to show the current interface settings. If configuring the mcRNC using the IPplan, create and activate a plan in the mcRNC to have a basic configuration as astarting point for further modifications.

g To avoid IP layer fragmentation, an MTU size of 1560 octets is recommended for the Iu-PS transport.


1 Configure the physical interface.Physical network interfaces are assigned to a certain EIPU node, if not yetconfigured.

• SCLI commands





• IP Plan

Related object class: ETHERRNC-xx/IP-1/OWNER-EIPU-0/ETHER-ethsfp7_r1


186 DN0974301 Issue: 02G

• port = sfp7• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mtu = 1560• vrf = default (default)(optional)


2 Configure VLAN interfaces.The VLAN interface is created for a certain physical interface with a reference to itsname. The VLAN IDs and the VLAN interface names have to be planned andconfigured accordingly.

• SCLI command examples for EIPU-0

#vlan: iups R1

add networking vlan /EIPU-0 realiface ethsfp7_r1 vid 11vlaniface vl11_iups_r1

#vlan: iucs R1

add networking vlan /EIPU-0 realiface ethsfp7_r1 vid 13vlaniface vl13_iucs_r1

#vlan: iur R1

add networking vlan /EIPU-0 realiface ethsfp7_r1 vid 15vlaniface vl15_iur_r1

#vlan: iub R1

add networking vlan /EIPU-0 realiface ethsfp7_r1 vid 17vlaniface vl17_iub_r1

#vlan: iups R2

add networking vlan /EIPU-0 realiface ethsfp8_r2 vid 12vlaniface vl12_iups_r2

#vlan: iucs R2

add networking vlan /EIPU-0 realiface ethsfp8_r2 vid 14vlaniface vl14_iucs_r2

#vlan: iur R2

add networking vlan /EIPU-0 realiface ethsfp8_r2 vid 16vlaniface vl16_iur_r2

#vlan: iub R2

add networking vlan /EIPU-0 realiface ethsfp8_r2 vid 18vlaniface vl18_iub_r2

• IP Plan

Related object class: VLANRNC-xx/IP-1/OWNER-EIPU-0/VLAN-vl11_iups_r1

• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)


Issue: 02G DN0974301 187

• mapping = vlandscptopcp• mtu = 1560 (optional)• realiface = ethsfp7_r1• vid = 11• vrf = default (default)(optional)

3 Configure the IP addresses of the interfaces.Proceed with the following configuration:

g The interface name refers to the created physical interfaces. Once VLANs are used, thenetwork interface IP addresses are tied to VLAN interfaces instead of physicalinterfaces.

Use the following command to add IP address to EIPU-0 VLAN 11 towards router-1:add networking address dedicated /EIPU-0 iface vl11_iups_r1ip-address 10.0.1.2/27

• IP Plan

Related object class: ADDRRNC-xx/IP-1/OWNER-EIPU-0/ADDR-10.0.1.2-vl11_iups_r1

• mask = 27• type = 0 (dedicated)• vrf = default (default)• role = iupsup

4 Configure application IP addresses for the user plane.Application IP addresses are assigned to a user plane recovery group (RG) and to aloopback interface. The IP address is visible in the node/unit that is actively runningthe service at the present time (active recovery unit, RU). In this case, load sharingfor an Iu-PS interface is applied by configuring two application IP addresses fortermination of Iu-PS user plane connections. All the user-plane application IPaddresses for different logical interfaces are configured as presented in sectionsConfiguring Iu-PS interface, mcRNC basic SiSo, Configuring Iu-CS interface,mcRNC basic SiSo, Configuring Iur interface, mcRNC basic SiSo and ConfiguringIub interface, mcRNC basic SiSo.

g The role attribute is a free-form character string that can be optionally configured. Therole attribute can be defined to keep the IP addressing usage clearly visible in order tosimplify the system maintenance. For the Iu-PS user-plane addresses apply, forexample, role “iupsup”.

Proceed with the following configuration:

• SCLI commands

add networking address dedicated /QNUP-0 iface lo ip-address10.1.1.1/32 role iupsup

add networking address dedicated /QNUP-1 iface lo ip-address10.1.1.2/32 role iupsup


188 DN0974301 Issue: 02G

• IP Plan

Related object class: ADDRRNC-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.With the evolved site solution, the static routes have to be configured with the BFDsingle-hop option from both mcRNC and site routers (RAN2440 Fast IP routingfeature). The BFD single-hop makes it possible to notice interface/link failures withinthe L2 domain and perform L3 level supervision for the connectivity.

g NoteThe system adds automatically the ingress direction static routes towards theapplication addresses configured to the loopback interface and tied to theQNUP/QNIUB Recovery Group instance. The application IP addresses can be reachedthrough both EIPU units of the redundant EIPU pair (EIPU-0/1, EIPU-2/3 etc). Thetransport redundancy static routes are added by the system once a new IP address isconfigured to the loopback interface. The automatically maintained static route entriesmight not be adjusted or deleted by user.

Node Network Id Priority Gateway Notes

Table 34 Iu-PS user plane

Node

Network Id

Priority

Gateway

Notes

EIPU-0 10.7.0.0/24 0 10.0.1.1 (to Router-1) Iu-PS user plane, ECMP




Table 35 Iu-PS control plane

Node

Network Id

Priority

Gateway

Notes

EIPU-0 10.8.0.0/24 0 10.0.1.1 (to Router-1) Iu-PS control plane, primaryassociation

EIPU-0 10.8.1.0/24 0 10.0.1.33 (to Router-2) Iu-PS control plane, secondaryassociation

EIPU-1 10.8.0.0/24 0 10.0.1.33 (to Router-2) Iu-PS control plane, primaryassociation


Issue: 02G DN0974301 189

Table 35 Iu-PS control plane (Cont.)

Node

Network Id

Priority

Gateway

Notes

EIPU-1 10.8.1.0/24 0 10.0.1.1 (to Router-1) Iu-PS control plane, secondaryassociation

• SCLI commands

The ECMP routing is used for the user-plane egress traffic. These routes might serveseveral destination nodes depending on the core network IP subnet planning.Commands are repeated with the same principles for all the required static routes.Static route priority is set to 0 (highest) by default if no other value is given.set routing node EIPU-0 static-route 10.7.0.0/24 nexthopgateway address 10.0.1.1 bfd-detect-mult 3 bfd-rx-interval 150bfd-monitoring enabled bfd-tx-interval 150 on

set routing node EIPU-0 static-route 10.7.0.0/24 nexthopgateway address 10.0.1.33 bfd-detect-mult 3 bfd-rx-interval150 bfd-monitoring enabled bfd-tx-interval 150 on

• IP Plan

Related object class: SRT4, ADR4GWRNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/SRT4-10.7.0.0-24


RNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/SRT4-10.7.0.0-24/ADR4GW-10.0.1.1

• bfdDetectMult = 3• bfdMonitoring = 1 (enabled)• bfdRxInterval = 150• bfdTxInterval = 150

RNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/SRT4-10.7.0.0-24/ADR4GW-10.0.1.33

• bfdDetectMult = 3• bfdMonitoring = 1 (enabled)• bfdRxInterval = 150• bfdTxInterval = 150

6 Configure user plane resources for Iu-PS, Iu-CS, Iur and Iub, IP-based routeconfiguration.User-plane connections related to the IP-based route configuration for differentlogical interfaces proceeds as described in the corresponding steps in sectionsConfiguring Iu-PS interface, mcRNC basic SiSo, Configuring Iu-CS interface,mcRNC basic SiSo, Configuring Iur interface, mcRNC basic SiSo and ConfiguringIub interface, mcRNC basic SiSo. The IP based route configuration controls thesource IP address selection for the user-plane connections, IP connection admissioncontrol, and IP layer scheduling.


190 DN0974301 Issue: 02G

7 Configure control plane resources for Iu-PS, Iu-CS, Iur, and Iub.Control plane connection-related configuration for different logical interfacesproceeds as described in the corresponding steps in sections Configuring Iu-PSinterface, mcRNC basic SiSo, Configuring Iu-CS interface, mcRNC basic SiSo,Configuring Iur interface, mcRNC basic SiSo and Configuring Iub interface, mcRNCbasic SiSo

8 Check and configure QoS related resources.In most cases using the default QoS values is sufficient, but depending on networkarchitecture and further QoS constraints, the values need to be reviewed andpossibly adjusted. For more information, see section QoS Configuration.

9 Configure the Radio Network layer information.Radio Network layer configuration for different logical interfaces proceeds asdescribed in the corresponding steps in sections Configuring Iu-PS interface,mcRNC basic SiSo, Configuring Iu-CS interface, mcRNC basic SiSo, Configuring Iurinterface, mcRNC basic SiSo and Configuring Iub interface, mcRNC basic SiSo.

3.9 Configuring IP for Iu-BC interface (RNC - CBC)Summary

The Iu-BC traffic is terminated to CFPU units of the mcRNC. Within this exampleconfiguration, the connectivity to Cell Broadcast Centre comes via the CFPU unit LANinterfaces. It is assumed that operator may organize the connectivity to CBC via therouters that are connected to LAN ports.

In this chapter, general steps of IP configuration for Iu-BC interface are presented. Whatit comes to routing configuration it is assumed that operator has configured the OSPFO&M connectivity following the chapter 4 O&M connectivity, solution 1 with OSPF andBFD steps. The OSPF will distribute the mcRNC CBC source IP address further tonetwork and also learn the related destination subnets dynamically.

Purpose

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

Before you start

The basic mcRNC O&M connectivity via LAN ports is present and the IP connectivityexists.

g The O&M OSPF connectivity via the LAN interfaces is already configured.

1 Configure an IP address for Iu-BC service in the CFPU unitadd networking instance default address /QNCFCP iface lo ip-address 10.0.10.111/32 role iubc


Issue: 02G DN0974301 191

Example

Figure 41 IPv4 configuration for Iu-BC 1GE connectivity


192 DN0974301 Issue: 02G

4 Configuring IP for O&M connectionsThe mcRNC O&M physical connectivity can be built using different schemes. Dependingon 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 (CFPUnode):

• CFPU network interface IP addresses, used also as the NTP and DNS client sourceaddresses; owner CFPU

• SSH IP addresses for the shell and SCLI access, basic mcRNC management IPaddress; owner SSH Recovery Group

• O&M IP addresses for OMS/NetAct and BTS connections, one or two IP addressesscheme; owner QNOMU Recovery Group

The RNC O&M IP addressing can be configured using one or two RNC O&M IPaddresses 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/NetActO&M traffic logically separated at the IP layer.

The two O&M addresses configuration scheme requires the following role attributesconfiguration 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 systemoperates with one O&M address scheme in respect to BTS O&M connections towardsBTS and OMS/NetAct connectivity.

The SSH connections require their own IP address in the SSH Recovery Group locatedin CFPUs. The given IP address provides the local management tool connectivity forshell access and the SCLI commands. NTP and DNS clients are bound to the networkinterface addresses.

O&M connectivity, solution 1In case of direct connectivity to BTS through the DCN routers, LAN1 ports associatedwith CFPU nodes can be used for connection to both OMS/NetAct and BTS. Thesolution 1 cabling and IP addressing is presented in Figure 42: O&M connectivity,solution 1.


Issue: 02G DN0974301 193

Figure 42 O&M connectivity, solution 1


1 Configure the physical interface, LAN portsThe LAN ports are fixed to CFPU nodes, the configuration actions are not required.

2 Configure VLAN interface (if used)The VLAN interface is created for a certain physical interface with a reference to itsname. Therefore the VLAN id and the VLAN interface name have to be planned andconfigured accordingly.

• SCLI commands examples

#vlan: oam

add networking vlan /CFPU-0 realiface eth0 vid 50 vlanifaceoam_r1

add networking vlan /CFPU-1 realiface eth0 vid 55 vlanifaceoam_r2

• IP Plan

Related object class: VLANRNC-xx/IP-1/OWNER-CFPU-0/VLAN-oam_r1

• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mapping = vlanPriDefault• realface = eth0• vid = 50• vrf = default (default)(optional)

Configuring IP for O&M connections Configuring IP Connection for Multicontroller RNC

194 DN0974301 Issue: 02G

3 Configure the IP addresses of the interfacesThe 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 to get theaddresses visible with the corresponding recovery-group-name-based inquiries.

g The interface name refers to created VLAN interfaces.

Proceed with the following configuration.add networking address dedicated /CFPU-0 iface oam_r1ipaddress 10.0.9.2/28 user /SSH user /ClusterNTP user/ClusterDNS role oam

add networking address dedicated /CFPU-1 iface oam_r2ipaddress 10.0.9.10/28 user /SSH user /ClusterNTP user/ClusterDNS role oam

• IP Plan

Related object class: ADDRRNC-xx/IP-1/OWNER-CFPU-0/ADDR-10.0.9.2-oam_r1

• mask = 29• type = 0 (dedicated)• vrf = default (default)• user = /SSH /ClusterNTP /ClusterDNS• role = oam

4 Configure application IP addressesThe 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 thenode/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, toget the shell and SCLI access. For the SSH IP address the role attribute valueshould be set to “ssh”. This enables mcRNC to automatically report correct SSH IPaddress towards NetAct for the SCLI access.

g The role attribute is a free form character string that can be configured optionally. Therole attribute might be defined to keep the IP addressing usage clearly visible to simplifythe 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 IPaddress.

g Only one IP address for SSH should be configured.


• SCLI commands

add networking address dedicated /QNOMU iface lo ip-address10.10.0.1/32 role btsom

Configuring IP Connection for Multicontroller RNC Configuring IP for O&M connections

Issue: 02G DN0974301 195

add networking address dedicated /QNOMU iface lo ip-address10.10.9.1/32 user /QNHTTPD role oms

• IP Plan

Related object class: ADDRRNC-xx/IP-1/OWNER-QNOMU-0/ADDR-10.10.0.1-lo

• mask = 32• type = 0 (dedicated)• vrf = default (default)• role = btsom

5 Configure the static routesThe static routes configuration is required if OSPF is not used.

g NoteThe system adds automatically the ingress direction static routes towards theapplication addresses configured to the loopback interface and tied to theSSH/QNOMU/QNCFCP Recovery Group instance. The application IP addresses canbe reached through both CFPU units of the redundant CFPU pair. The transportredundancy static routes are added by the system once a new IP address is configuredto the loopback interface. The automatically maintained static route entries might not beadjusted or deleted by user.

Table 36 Routing table for egress traffic

Node

Network Id

Priority

Gateway

Notes

CFPU-0 a.a.a.a/xx (BTSO&M destinationsubnet)

0 10.0.9.1 (to Router-1) Egress forwarding


8 cfeigw CFPU-1 Egress forwarding,redundant route

CFPU-0 b.b.b.b/xx (OMSO&M destinationsubnet)









196 DN0974301 Issue: 02G

Table 36 Routing table for egress traffic (Cont.)

Node

Network Id

Priority

Gateway

Notes





g The SCLI commands contain a generic reference to the CFPU internal cfeigw interfaceIP address. Replace the “cfeigw CFPU-x” with the corresponding IP address such as169.254.0.4. The SCLI command “show networking address iface cfeigw” can be usedto review the addresses of the system-configured internal cfeigw interface.

• SCLI commands

Ingress direction redundancy static routes in between the CFPU nodes towards theloopback IP addresses are created automatically by the system.Egress static routes for the O&M destination subnets, containing primary andsecondary route entry.set routing node CFPU-0 static-route a.a.a.a/xx nexthopgateway address 10.0.9.1 on

set routing node CFPU-0 static-route a.a.a.a/xx nexthopgateway address “cfeigw CFPU-1” priority 8 on

set routing node CFPU-0 static-route b.b.b.b/xx nexthopgateway address 10.0.9.1 on

set routing node CFPU-0 static-route b.b.b.b/xx nexthopgateway address “cfeigw CFPU-1” priority 8 on

set routing node CFPU-0 static-route a.a.a.a/xx nexthopgateway address 10.0.9.9 on

set routing node CFPU-1 static-route a.a.a.a/xx nexthopgateway address “cfeigw CFPU-0” priority 8 on



O&M connectivity, solution 1 with OSPF and BFDIn case of direct connectivity to BTS through the DCN routers, LAN1 ports associatedwith CFPU nodes can be used for connection to both OMS/NetAct and BTS.Configuration applies OSPF for the routing aided with the BFD Single-Hop pollingmechanism. Cabling and IP addressing is presented in Figure 43: O&M connectivity,solution 1 with OSPF


Issue: 02G DN0974301 197

Figure 43 O&M connectivity, solution 1 with OSPF


1. Configure the physical interface, LAN portsThe LAN ports are fixed to CFPU nodes, the configuration actions are not required.

2. Configure VLAN interface (if used)The VLAN interface is created for a certain physical interface with a reference to itsname. Therefore the VLAN id and the VLAN interface name have to be planned andconfigured accordingly.

• SCLI commands examples#vlan: oamadd networking vlan /CFPU-0 realiface eth0 vid 50 vlanifaceoam_r1 mapping vlandscptopcpadd networking vlan /CFPU-1 realiface eth0 vid 55 vlanifaceoam_r2 mapping vlandscptopcp


198 DN0974301 Issue: 02G

g In case the internal oam_int interfaces are not yet created to the system, then run thefollowing commands. Please, note that the interface for internal VLAN has to be xaui0and the VLAN id has to be 879.

add networking vlan /CFPU-0 vlaniface oam_int realiface xaui0vid 879 mapping intvlanpiptopcp

add networking vlan /CFPU-1 vlaniface oam_int realiface xaui0vid 879 mapping intvlanpiptopcp

• IP PlanRelated object class: VLANRNC-xx/IP-1/OWNER-CFPU-0/VLAN-oam_r1

• admin = 1 (up)(default)• ipv4forwarding = 1 (yes)(optional)• mapping = vlandscptopcp• realface = eth0• vid = 50

3. Configure the IP addresses of the interfacesThe 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 to get theaddresses visible with the corresponding recovery-group-name-based inquiries.

g The interface name refers to created VLAN interfaces.

The following user definitions have to be considered in addition for the O&Mfunctionalities: user PAP user RuimReplicator.

Proceed with the following configuration.add networking address dedicated /CFPU-0 iface oam_r1ipaddress 10.0.9.6/28 user /ClusterNTP user /ClusterDNS user/SSH role oamadd networking address dedicated /CFPU-1 iface oam_r2ipaddress 10.0.9.10/28 user /ClusterNTP user /ClusterDNS user/SSH role oamadd networking address dedicated /CFPU-0 iface oam_intipaddress 10.0.9.13/30 role oamadd networking address dedicated /CFPU-1 iface oam_intipaddress 10.0.9.14/30 role oam

• IP PlanRelated object class: ADDRRNC-xx/IP-1/OWNER-CFPU-0/ADDR-10.0.9.2-oam_r1

• mask = 32• type = 0 (dedicated)• vrf = default (default)• user = /ClusterNTP, /ClusterDNS, /SSH

4. Configure application IP addressesThe 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 thenode/unit that is actively running the service at the present time (active recovery unit,RU).


Issue: 02G DN0974301 199

The SSH IP address is required for the management connection to the mcRNC, toget the shell and SCLI access. For the SSH IP address the role attribute valueshould be set to “ssh”. This enables mcRNC to automatically report correct SSH IPaddress towards NetAct for the SCLI access.

g The role attribute is a free form character string that can be configured optionally. Therole attribute might be defined to keep the IP addressing usage clearly visible to simplifythe system maintenance.

f If the BTS O&M two-address 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.

g Only one IP address for SSH should be configured.


• SCLI commandsadd networking address dedicated /SSH iface lo ip-address10.10.0.2/32 role sshadd networking address dedicated /QNOMU iface lo ip-address10.10.9.1/32 user /QNHTTPD role omsadd networking address dedicated /QNOMU iface lo ip-address10.10.0.1/32 role btsom

• IP PlanRelated object class: ADDRRNC-xx/IP-1/OWNER-QNOMU-0/ADDR-10.10.0.1-lo

• mask = 32• type = 0 (dedicated)• vrf = default (default)• user = /QNHTTPD• role = btsom

5. Configure the static routesThe static routes configuration in case the OSPF O&M setup is not needed whenthere is a public subnet configured to CFPU node backplane side.

6. Configure the OSPF


• SCLI commandsset routing instance default node CFPU-0 router-id10.0.9.2set routing instance default node CFPU-1 router-id10.0.9.10

• IP PlanRelated object class: GLPRMRNC-xx/IP-1/OWNER-CFPU-0/RTINST-default/GLPRM

• routerId = 10.0.9.2


200 DN0974301 Issue: 02G

b) Configure the OSPF areasCreate the OSPF area within each needed routing instance. The following is anexample of a stub area usage between the mcRNC and the site router.

g The OSPF area design has to be planned according to the end-to-end network designprinciples. Within the examples the stub area is assigned to keep the mcRNC routingtable size minimized with assuming that mcRNC is connected to bigger OSPFautonomous system/network.

• SCLI commandsset routing instance default node CFPU-0 ospf area10.0.0.10 onset routing instance default node CFPU-0 ospf area10.0.0.10 stub onset routing instance default node CFPU-1 ospf area10.0.0.10 onset routing instance default node CFPU-1 ospf area10.0.0.10 stub on

• IP PlanRelated object class: O2AREARNC-xx/IP-0/OWNER-CFPU-0/RTINST-default/O2AREA-10.0.0.10


c) Activate the OSPF on the interfacesActivate the OSPF on the loopback and network interfaces.Proceed with the following configuration in order to activate the OSPF on theloopback interfaces

• SCLI commandsset routing instance default node CFPU-0 ospf interfacelo area 10.0.0.10 onset routing instance default node CFPU-1 ospf interfacelo area 10.0.0.10 on

• IP PlanRelated object class: O2AREA - O2IFCRNC-xx/IP-1/OWNER-CFPU-0/RTINST-default/O2AREA-10.0.0.10/O2IFC-lo

Proceed with the following configuration in order to activate the OSPF on thenetwork interfaces (VLAN interfaces

• SCLI commandsset routing instance default node CFPU-0 ospf interfaceoam_r1 area 10.0.0.10 onset routing instance default node CFPU-1 ospf interfaceoam_r2 area 10.0.0.10 onset routing instance default node CFPU-0 ospf interfaceoam_int area 10.0.0.10 onset routing instance default node CFPU-1 ospf interfaceoam_int area 10.0.0.10 on

d) Configure BFD Single-Hop for OSPF enabled VLAN interfacesBFD Single-Hop is activated for OSPF enabled VLAN interfaces in order toachieve fast recovery of the neighbor/OSPF interface failures.#VRF iuiurup


Issue: 02G DN0974301 201

set routing instance default node CFPU-0 ospf interfaceoam_r1 bfd-detect-mult 3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150set routing instance default node CFPU-1 ospf interfaceoam_r2 bfd-detect-mult 3 bfd-monitoring enable bfd-rx-interval 150 bfd-tx-interval 150

e) Configure OSPF parametersFor each network instance set the OSPF designated router election priorityparameters properly. It is not recommended to allow the EIPU nodes to becomea designated router.Proceed with the following configuration.Set the external interfaces priority to 0.

• SCLI commandsset routing instance default node CFPU-0 ospf interfaceoam_r1 priority 0set routing instance default node CFPU-1 ospf interfaceoam_r2 priority 0set routing instance default node CFPU-0 ospf interfaceoam_int priority 0set routing instance default node CFPU-1 ospf interfaceoam_int priority 0

Set the interfaces cost to 2.

• SCLI commands#VRF iuiurupset routing instance default node CFPU-0 ospf interfaceoam_r1 cost 2set routing instance default node CFPU-1 ospf interfaceoam_r2 cost 2set routing instance default node CFPU-0 ospf interfaceoam_int cost 2set routing instance default node CFPU-1 ospf interfaceoam_int cost 2

• IP PlanRelated object class:O2AREA - O2IFCRNC-xx/IP-1/OWNER-CFPU-0/RTINST-default/O2AREA-10.0.0.10/O2IFC-oam_r1



202 DN0974301 Issue: 02G

O&M connectivity, solution 2In the second solution the LAN1 ports, associated with CFPUs, are used for the O&Mconnectivity to OMS and NetAct. The BTS O&M connectivity is provided through theEIPU units. This solution is used when the BTS can be reached only through the routersconnected to EIPU nodes. Figure 44: O&M connectivity, solution 2 shows the cablingand basic IP addressing of the solution 2.

Figure 44 O&M connectivity, solution 2

Router-2

Router-1

TransportNetwork

10.0.1.9/30

10.0.0.1/30

BTS!O&M!a.a.a.a/xx

DCN,!O&M

OMS!b.b.b.b/xx

CFPU-1cfeigw

O&M!(Standby)::!QNOMU-0-!10.10.0.1!lo!(role “btsom”)-!10.10.9.1!lo!(role “oms”)

10.0.9.10/29!(LAN1)

10.0.1.1/30

10.0.0.9/30

DCN!router-1

DCN!router-2

10.0.9.9/29

10.0.9.1/29

EIPU-1

cfeigw

QNUP-0!GW10.0.1.10/30!(SFP8)

10.0.0.10/30!(SFP7)

CFPU-0cfeigw

QNOMU-0!GW

O&M!(Active)::!QNOMU-0-!10.10.0.1!lo!(role “btsom”)-!10.10.9.1!lo!(role “oms”)

10.0.9.2/29!(LAN1)

EIPU-0

cfeigw

QNUP-0!GW10.0.1.2/30!(SFP8)

10.0.0.2/30!(SFP7)

SSH!(Active)10.10.0.2!lo

QNOMU-0!GW

SSH!(Standby)10.10.0.2!lo

The mcRNC CFPU nodes host the O&M Recovery Group (QNOMU). The O&M recoverygroup, in two first modules, is using the 2N hot-standby configuration. The LAN1interface is associated with CFPU node providing the connectivity to the site router orDCN 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&Mconnectivity, solution 1), with the exception of step Configure the static routes, which isas follows:

1 Configure the static routesThe static routes configuration is required if OSPF is not used.


Issue: 02G DN0974301 203

g NoteThe system adds automatically the ingress direction static routes towards theapplication addresses configured to the loopback interface and tied to theSSH/QNOMU/QNCFCP Recovery Group instance. The application IP addresses canbe reached through both CFPU units of the redundant CFPU pair. The transportredundancy static routes are added by the system once a new IP address is configuredto the loopback interface. The automatically maintained static route entries might not beadjusted or deleted by user.

Table 37 Routing table for ingress traffic

Node

Network Id

Priority

Gateway

Notes

EIPU-0 10.10.0.1/32 (O&Msource “iub”)

0 QNOMU-0 GW Ingress, EIPU toCFPU/QNOMU

EIPU-1 10.10.9.1/32 (O&Msource “iub”)

0 QNOMU-0 GW Ingress, EIPU toCFPU/QNOMU

Table 38 Routing table for egress traffic

Node

Network Id

Priority

Gateway

Notes


0 QNUP-0 (GW) Egress forwarding to BTSsubnet through EIPU


0 10.0.9.1 (DCN Router-1)

Egress forwarding, toOMS/NetAct




0 QNUP-0 (GW) Egress forwarding, toBTS subnet through EIPU


0 10.0.9.9 (DCN Router-1)

Egress forwarding, toOMS/NetAct



EIPU-0 a.a.a.a/xx (BTSO&M destinationsubnet)

0 10.0.0.1 (to Router-1) Egress forwarding, ECMP


204 DN0974301 Issue: 02G

Table 38 Routing table for egress traffic (Cont.)

Node

Network Id

Priority

Gateway

Notes







g The SCLI commands contain a generic reference to the CFPU internal cfeigw interfaceIP address. Replace the <cfeigw CFPU-x> with the corresponding IP address suchas 169.254.0.4. The SCLI command show networking address iface cfeigwcan be used to review the addresses of the system-configured internal cfeigw interface.

• SCLI commands

Ingress direction redundancy static routes in between the CFPU nodes towards theloopback IP addresses are created automatically by the system.Egress static routes for the O&M destination subnets, containing primary andsecondary route entry.set routing node CFPU-0 static-route a.a.a.a/xx nexthopgateway address “QNUP-0 GW” on



set routing node CFPU-1 static-route a.a.a.a/xx nexthopgateway address “QNUP-0 GW” on



Egress routes for the EIPU nodes towards the BTS O&M subnetset routing node EIPU-0 static-route a.a.a.a/xx nexthopgateway address 10.0.0.1 on

set routing node EIPU-0 static-route a.a.a.a/xx nexthopgateway address 10.0.1.1 on




Issue: 02G DN0974301 205

5 Configuring routing

5.1 Configuring routing global parametersPurpose

Several tools are provided for the user to control the routing procedures in the networkelement. Note that some of these tools replace the basic IP management tools, whichare typically used in different than router types of products.

Setting router IDPurpose

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 numberexcept 0.0.0.0. Make sure that the router ID is unique. Virtual routing can be also used.Virtual routers need individual router ID.

1 Assign the ID to a router.The command for setting the router ID is as follows: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 tothe default instance.

2 Check the current ID of the router.Use the following command to display the router ID:show routing instance <name> node <name> router-id [all]

Setting maximum number of equal-cost pathsPurpose

You can specify a maximum number of the equal-cost paths to be used when there ismore than one equal-cost path to the destination. Setting the maximum number of theequal-cost paths affects the whole system instead of one specific routing instance.

Before you start

g Only OSPF routes and static routes are able to use more than one next hop address,thus this functionality can only be used with them.

g The allowed range for the maximum number of equal-cost paths is from 1 to 8 and thedefault value is 8. Changing the value will cause all existing routes to be re-installed.


206 DN0974301 Issue: 02G

1 Set the maximum number of the equal-cost paths.The command for setting the maximum number of the equal-cost paths is as follows:set routing [instance <name>] node <name> max-path-splits <value>

2 Check the maximum number of equal-cost paths.Use the following command to display the maximum number of equal-cost paths:show routing [instance <name>] node <name> max-path-splits config [all]

g With parameter all you can display the maximum numbers of equal-cost paths for allthe instances on the node.

Setting tracing for routingPurpose

You can monitor routing system events by enabling the routing trace functionality. Thelogging is not turned on by default, because tracing consumes system resources andcan reduce the system performance. Tracing can be enabled either globally for allprotocols or for each protocol separately.

1 Change the routing trace setting.

a) If you want to enable the the tracing for routing protocols, use the command asfollows:set routing [instance <name>] node <name> trace <protocol> <trace option> on

b) If you want to disable the the tracing for routing protocols, use the command asfollows:set routing [instance <name>] node <name> trace <protocol> <trace option> off

2 Check the tracing for routing protocols.Use the following command to display the tracing for routing protocols:show routing [instance <name>] node <name> trace <trace option> configThe 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. Whenthe trace file reaches the maximum size, it is renamed as a numbered backup file; forinstance, the first backup trace file is named /var/log/ipsrd.log.0.

Example

To display the tracing for routing protocols, enter the following command:

show routing [instance <name>] node <name> trace <trace option> config

Configuring IP Connection for Multicontroller RNC Configuring routing

Issue: 02G DN0974301 207

To enable the tracing in the CFPU-0 node for all options related to the OSPF protocolby entering the following command:

set routing node CFPU-0 trace ospf all on

To display the tracing in the CFPU-0 node for global option, enter the followingcommand:

show routing node CFPU-0 trace global config

To display the tracing in the CFPU-0 node for kernel option, enter the followingcommand:

show routing node CFPU-0 trace kernel config

To display the tracing in the CFPU-0 node for ospf (IPv4 protocol) option, enter thefollowing command:

show routing node CFPU-0 trace ospf config

To display the trace files in the CFPU-0 node, enter the following command:

show routing [instance <name>] node CFPU-0 tracefile\config

3 Set the maximum size of the trace file (optional).The command for setting the maximum size of the trace file (in megabytes) is asfollows:set routing node <name> tracefile size <1-4095>

g The default size is one megabyte. The user must make sure that there is enough diskspace for the trace log files.

4 Set the maximum number of trace files (optional).The command for setting the maximum number of trace files is as follows:set routing node <name> tracefile maxnum <1-1000>

g The default number of trace files is 10. When the maximum number of the trace log filesis exceeded, the oldest file will be removed. The user must make sure there is enoughdisk space for the trace log files.

5.2 Configuring static routes for IPv4Purpose

To configure the static routes for IPv4.

Configuring routing Configuring IP Connection for Multicontroller RNC

208 DN0974301 Issue: 02G

Before you start

If the virtual routing is used, check that the routing instances are created and interfacesare set to the correct routing instances. In the commands presented in this chapter, therouting instances are defined with the optional instance <name> parameter that isattached in the commands. In the command syntax the parameter is placed right afterthe routing parameter.

g Use transactions to bundle multiple changes into one bigger change. Use configurationlocking feature to prevent other users from interfering with your configuration changes.

1 Define a static route to the next hop gateway.You can define multiple static routes to next hop gateways. The static route defines anext hop gateway for packets that are destined to a specified IP address range.Define the route with the following command:set routing [instance <name>] node <name> static-route <IP_PREFIX|default> nexthop gateway address <address> [priority <1- 8>] onFurther informationAn individual static route per gateway can be removed with the following command:set routing [instance <name>] node <name> static-route <IP_PREFIX|default> nexthop gateway address <address> offAll routes for a given subnet can be removed with the following command:set routing [instance <name>] node <name> static-route <IP_PREFIX|default> offFor nodes where the routing daemon is not deployed, the MTU size and source IPaddress can be set for the default static route using the following commands:set routing [instance <name>] node <name> static-route <IP_PREFIX|default> mtu <mtu-size>set routing [instance <name>] node <name> static-route <IP_PREFIX|default> source <IP-address>

2 Enable packet rejecting.Instead of forwarding packets to the next hop, you can optionally create reject orblackhole type routes. Reject causes packets to be dropped and unreachablemessages to be sent to packet originators.Blackhole causes packets to be dropped but does not cause unreachable messagesto be sent. These can be used, for example, to drop temporarily all packetsgenerated 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 rejectset routing [instance <name>] node <node> static-route <IP_PREFIX|default> nexthop blackhole

3 Enable or disable the BFD protocol for an existing static route.The single-hop BFD 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-


Issue: 02G DN0974301 209

8>] [bfd-tx-interval <tx-interval |default>] [bfd-rx-interval <rx- interval|default>] [bfd-monitoring <enabled|disabled>] [bfd-detect- mult <multvalue|default>] onTo enable the single-hop BFD session, set the bfd-monitoring parameter toenabled. To disable the single-hop BFD session, set the bfd-monitoringparameter to disabled.

g For multi-hop BFD configuration, see BFD configuration.

4 Configure the BFD hold time for existing routes.The parameter bfd-static-holdtime is used to configure the hold time for allBFD sessions for static routes. The command is as follows:set routing [instance <name>] node <node> bfd-static-holdtime <bfd- static-holdtime>The range of the bfd-static-holdtime parameter is 0 to 900 seconds. Thedefault value is 0. By setting the value to 0, you can disable the BFD holdtimefeature.

Example

To display the BFD hold time parameter configured for the static route, enter thefollowing commands:

show routing [instance <name>] node <node> bfd-static-holdtime configshow routing [instance <name>] node <node> bfd-static-holdtime config allshow routing [instance <instance_name>] node <node_name> static-route configshow routing [instance <instance_name>] node <node_name> static-route config all

5 Configure protocol rank for existing routes.Define the protocol rank for the existing static routes. Rank is used to determinewhich route is used when there are several routes from different protocols to thesame destination.The new rank for the given static route is defined with the following command:set routing [instance <name>] node <node> static-route <IP_PREFIX|default> rank <0-255>

6 Monitor static routes.Monitor the status of the static routes with the command:show routing [instance <name>] node <name> static-route config [all]

Example

To monitor the status of the static routes configured for the CFPU-0 node, enter thefollowing command:

show routing node CFPU-0 static-route config all


210 DN0974301 Issue: 02G

The following output is displayed:

Instance: default

BFD hold time: 0

Static route: default Next hop type: normal Rank: not defined Gateway: 192.190.140.1 Preference: 1 BFD monitoring: disabled BFD tx interval: 1000 BFD rx interval: 1000 BFD detect multiplier: 4

Further information

Details of the parameters of the routing command are shown in the table below.

Table 39 Parameters for configuring static routes

Parameter

Description

Value range

instance <name> The routing configuration isapplied to the virtual routinginstance specified by thisparameter. If no instance isspecified, the routingconfiguration is applied to thedefault routing instance. This isan optional parameter.

-

node <node-name> This parameter specifies thenode name where the staticroute configuration takes place.

-

address <address> This parameter specifies the IPaddress of the gateway.

-

mtu <mtu-size> This parameter specifies theMTU value of the default staticroute. This parameter isoptional.

g This parameter issupported only for nodesin which the RoutingDaemon is not deployed.

The allowed value range is1280 to 9000.

source <IP-address> This parameter specifies thesource IP address or range ofIP addresses selector written informat <IP-address/mask>.Optional parameter.

-


Issue: 02G DN0974301 211

Table 39 Parameters for configuring static routes (Cont.)

Parameter

Description

Value range

g This parameter issupported only for nodesin which the RoutingDaemon is not deployed.

<IP_PREFIX|default> This parameter specifies thedestination network address inthe form of prefix/mask, wherethe prefix is unicast IPv4address and the mask is anetwork mask.

The allowed values are:

• prefix: unicast IPv4address

• mask: network mask in therange 1 to 32.

priority <1-8> This parameter specifies thepriority of the static route.

The higher priority (lower value)next hops are preferred.Switching over to the next routein the list happens only if theinterface fails. It does nothappen for non-reachable nexthops if the interface is still up. Ifthe priority is the same and theinterface is up, it will be anequal cost, multipath route.

The allowed range is from 1 to8.

bfd-tx-interval <tx-interval |default>

This parameter specifies theminimum interval between thetransmitted BFD controlpackets in milliseconds. Thisparameter is optional.

The allowed values are in therange 50ms to 60000ms with agranularity of 50 ms. Thedefault value is 1000 ms.

g This parameter acceptseither the numeric valueor the value default. Ifthe value default isused, then the value ofbfd-tx-interval isset to a default value of1000 ms.

bfd-rx-interval <rx-interval|default>

This parameter specifies theminimum interval between thereceived BFD control packetsin milliseconds. This parameteris optional.

The allowed values are in therange 50 ms to 60000 ms witha granularity of 50 ms. Thedefault value is 1000 ms.


212 DN0974301 Issue: 02G

Table 39 Parameters for configuring static routes (Cont.)

Parameter

Description

Value range

g This parameter acceptseither the numeric valueor the value default. Ifthe value default isused, then the value ofbfd-rx-interval isset to a default value of1000 ms.

bfd-detect-mult<mult-value|default>

This parameter specifies thedesired detection time multiplierfor the BFD control packets onthe local system. Thenegotiated control packettransmission interval, multipliedby this parameter, is thedetection time for a particularBFD session. This parameter isoptional.

The allowed value range isfrom 1 to 50. The default valueis 4.

g This parameter acceptseither the numeric valueor the value default. Ifthe value default isused, then the value ofbfd-detect-mult isset to a default value of4.

bfd-monitoring<enabled|disabled>

This parameter enables ordisables the BFD protocol forthe static route. This parameteris optional.

The allowed values areenabled and disabled. Thedefault value is disable.

5.3 Configuring OSPF5.3.1 Configuring OSPFv2 overview

This chapter provides an overview and operating instructions on mcRNC related toRAN1879: Dynamic routing by OSPF.

The Open Shortest Path First (OSPF) is configured on the external Ethernet interface ofthe mcRNC. Some of the key benefits this feature brings to the mcRNC are reducingconfiguration effort and fast convergence. In addition, it provides robustness in case oflink failure because traffic can be dynamically re-routed.

The OSPF area scheme for mcRNC is shown in the figure below. The external interfacesof the two BCN modules and the router interfaces connected to the modules are in area100. And the router interfaces towards the backbone are in backbone area 0.


Issue: 02G DN0974301 213

Figure 45 OSPF area scheme

To avoid flooding AS external advertisements into an area, you can set this area to stubarea. For stub areas, the border router automatically advertises a default route in placeof the external routes that are not being advertised within the stub area so that routers inthe stub area can reach destinations outside the area. This reduces the link-statedatabase size, and therefore the memory requirements, for a stub area’s internal routers.

The following subchapters introduce the procedure of OSPF configuration and routeredistribution if you want to export routes to OSPF protocol on a node.

5.3.2 Configuring OSPFv2Purpose

To configure and monitor the OSPFv2 routing protocol.

Configuration of OSPFv2 requires only a few mandatory steps. Other optional steps maybe 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 canconfigure a large number of global, interface, and area-related OSPF parameters. Thisprocedure also introduces how to verify the configuration and how to monitor routingtables and statistics.

Before you start

Check that the routing instances are created, if virtual routing is being used and set tothe correct interfaces. In addition, some OSPF commands require that the IP addressesare assigned to the interfaces before the command can be executed. In the commands


214 DN0974301 Issue: 02G

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, theparameter is placed right after the routing parameter.

g To bundle multiple changes into one bigger change, use the transaction feature. Toprevent other users from interfering with your configuration changes, use theconfiguration locking feature.

We recommend you to configure the OSPF router ID manually. Select the following valueas the router ID if the OSPF router ID is not configured:

• one of the Ioopback interface IP addresses• one of the other IP addresses configured on the router in case no loopback interface

IP address is configured

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 areaparameters, such as: backbone, stub, and totally-stubby.Create a backbone area with the backbone keyword. This automatically creates anidentifier 0.0.0.0 which is reserved exclusively for the backbone area. Create otherareas with your selected identifiers. The identifier should be given as a dotted/quadvalue or as a 32-bit number. You can use your subnetted IPv4 network address asarea IDs.The OSPF area configuration can be defined using the following command:set routing [instance <name>] node <name> ospf areaThe parameters of the commands (the part after the ospf parameter) are presentedin the following table.

Table 40 Commands for configuring OSPF areas

Parameter

Description

Value range

area backbone<on|off>

This parameterenables/disables the backbonearea. Enabling the backbonearea sets the area ID 0.0.0.0for the backbone area.

The allowed values areon and off. Thedefault value is off.

area <OSPF_AREA><on|off>

This parameterenables/disables an OSPFarea. Enabling the OSPF areasets the specified area ID.


area <OSPF_AREA>stub <on|off>

This parameterenables/disables an OSPFstub area. A stub area is anarea which does not haveexternal routes. Enabling theOSPF stub area sets thespecified area ID for the stubarea.



Issue: 02G DN0974301 215

Table 40 Commands for configuring OSPF areas (Cont.)

Parameter

Description

Value range

area <OSPF_AREA>stub default-cost<1- 16777215>

This parameter sets the costfor the default summary routefor the stub area.

The allowed values arefrom 1 to 16777215.

area <OSPF_AREA>stub summary<on|off>

This parameter sets the stubarea to forward or blocksummary information. If a stubarea (area without externalroutes), does not havesummary routes it is called atotally-stubby-area.

The allowed values areon and off.The defaultvalue is off.

area {backbone |<OSPF_AREA>} range<IP_PREFIX><on|off>

This parameter defines therange of networks belonging toan area.

The allowed values areon and off.

area {backbone |<OSPF_AREA>} range<IP_PREFIX>restrict <on|off>

This parameter defines therange of networks belonging toan area in which the summarynetwork LSAs are not sent.


area {backbone |<OSPF_AREA>} stub-network <IP_PREFIX><on|off>

This parameter defines therange of networks belonging toa stub network.


area {backbone |<OSPF_AREA>} stub-network <IP_PREFIX>cost <1-65535>

This parameter defines thecost for the default route in astub network.


area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA><on|off>

This parameterenables/disables a virtual linkfrom the router that does nothave connection to a backbonenetwork. Virtual link is definedthrough an adjacent non-backbone area (transit area) bydefining the termination pointof the virtual link and the ID ofthe transit area. Thetermination point is the routerID of the adjacent area'sborder router having thebackbone connection. Thetransit area is an area that isshared by the router you areconfiguring and the routerhaving the backbone

The allowed values areon and off . Thedefault value is off.


216 DN0974301 Issue: 02G


Parameter

Description

Value range

connection. The area ID mustbe pre-configured using thebasic area commands.

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA> hello-interval <time>

This parameter sets the hello-interval in seconds for thevirtual link.

The allowed values arefrom 1 to 65535.The default value is 30.

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA> dead-interval <time>

This parameter sets the dead-interval in seconds for thevirtual link.

The allowed values arefrom 1 to 4294967295.The default value is120.

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA>retransmit-interval<time>

This parameter sets theretransmit-interval in secondsfor the virtual link.


area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA>authtype none

This parameter disables theauthentication for the virtuallink.

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA>authtype simple

This parameter selects thesimple authentication type forthe virtual link and define the 1to 8 alpha numericalcharacters authentication key.Generally, routers on a givenlink must agree on theauthentication configuration toform a neighbor adjacency.The authentication scheme Isused to verify that the routinginformation is received fromtrusted peers.

area backbonevirtual-link<ROUTER_ID>

This parameter selects theMD5 authentication. Enter atleast one key ID and its

The allowedparameters are:


Issue: 02G DN0974301 217


Parameter

Description

Value range

transit-area<OSPF_AREA>authtype md5 key<AUTH_KEYID> secret<MD5_SECRET>

corresponding MD5 secret. Inoutgoing packets, the MD5secret is included in encryptedform to authenticate the packetand if you configure multiplekey IDs, the largest key ID isused for authenticating thepackets. All keys can be usedto authenticate incomingpackets. Routers on a givenlink must agree on theauthentication configuration toform a neighbor adjacency.Use an authentication schemeto guarantee that routinginformation is accepted onlyfrom trusted peers.

• <AUTH_KEYID>: 1to 255

• <MD5_SECRET>:1 to 16�alphanumericcharacters..

g The MD5 secretshould besurrounded bydouble quotationmarks when non-alphanumericcharacters areused.

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA>authtype md5 key<AUTH_KEYID> off

This parameter deletes theMD5 key in question.

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 whichthe equipment is integrated. Both hello-interval and dead-interval valuesshould 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 MD5authentication is used.To define the interface configuration, use the following command:set routing [instance <name>] node <name> ospf interfaceThe parameters of the command (the part after the ospf parameter) are presentedin the following table:


218 DN0974301 Issue: 02G

Table 41 Commands for configuring OSPF interfaces

Parameter

Description

Value range

interface<IFNAME> area{backbone |<OSPF_AREA>}<on|off>

This parameter assigns anOSPF area to an interface. Thearea should be defined earlier.


interface<IFNAME> hello-interval <time>

This parameter sets the hello-interval in seconds.


interface<IFNAME> fast-hello-interval

This parameter specifies thetime in milliseconds between thehello packets that the routersends to the interface.

The allowed values arefrom 50 to 950 ms witha granularity of 50 ms.The default value is 200ms.

interface<IFNAME> dead-interval <time>

This parameter sets the dead-interval in seconds.


interface<IFNAME>retransmit-interval <time>

This parameter sets theretransmit-interval in seconds.


interface<IFNAME> cost<value>

This parameter sets the cost forsending packets over aninterface.


interface<IFNAME> priority<value>

This parameter defines theelection priority for OSPFrouter/interface. The router withthe highest priority is selected tobe the designated router. Therouter with priority equal to 0 willnot be selected as thedesignated router.


interface<IFNAME> passive<on|off>

This parameter sets the OSPFinterface to passive state. Inpassive state, the OSPFinterface does not send hellopackets and therefore the linkdoes not form any adjacencies.


interface<IFNAME> authtypenone

This parameter disablesauthentication.


Issue: 02G DN0974301 219

Table 41 Commands for configuring OSPF interfaces (Cont.)

Parameter

Description

Value range

interface<IFNAME> authtypesimple <PASSWORD>

This parameter enables simpleauthentication and sets thepassword. Generally, routers ona given link must agree on theauthentication configuration toform neighbor adjacency. Theauthentication scheme is used toverify that the routing informationis received from trusted peers.

The allowed values are1 to 8 alpha numericalcharacters.

interface<IFNAME> authtypemd5 key<AUTH_KEYID>secret<MD5_SECRET>

This parameter enables MD5authentication. Enter at least onekey ID and its correspondingMD5 secret. If you configuremultiple key ids, the largest keyID is used for authenticatingoutgoing packets. All keys canbe used to authenticateincoming packets. Routers on agiven link must agree on theauthentication configuration toform neighbor adjacency. Use anauthentication scheme toguarantee that routinginformation is accepted onlyfrom trusted peers.



• <MD5_SECRET>: 1to 16 alphanumericcharacters.

interface<IFNAME> authtypemd5 key<AUTH_KEYID> off

This parameter deletes the MD5key in question.


This parameter enables ordisables the BFD protocol for theOSPF interface. This is anoptional parameter.

g The BFD monitoring isdisabled by default.

The allowed values areenabled anddisabled.

bfd-tx-interval<tx-interval|default>

The minimum interval, inmilliseconds, between thetransmitted BFD control packetsthat the system uses at thecurrent time. This is an optionalparameter.

The allowed value is inthe range 50ms to60000ms with agranularity of 50ms. Thedefault value is 1000ms.


220 DN0974301 Issue: 02G


Parameter

Description

Value range

g This parameteraccepts either thenumeric value orthe valuedefault. If thevalue default isused, then thevalue ofbfd-tx-interval is setto a default valueof 1000ms.

bfd-rx-interval<rx-interval|default>

The minimum interval, inmilliseconds, between thereceived BFD control packetsthat the system requires. This isan optional parameter.

The allowed value is inthe range 50ms to60000 ms with agranularity of 50ms. Thedefault value is 1000ms.

g This parameteraccepts either thenumeric value orthe valuedefault. If thevalue default isused, then thevalue ofbfd-rx-interval is setto a default valueof 1000ms.


The desired detection timemultiplier for the BFD controlpackets on the local system. Thenegotiated control packettransmission interval, multipliedby this parameter, will be thedetection time for a particularBFD session. This is an optionalparameter.

The allowed value is inthe range 1 to 50. Thedefault value is 4.

g This parameteraccepts either thenumeric value orthe valuedefault. If thevalue default isused, then thevalue ofbfd-detect-mult is set to adefault value of 4.


Issue: 02G DN0974301 221

3 Configure global OSPF parameters.A set of generic OSPF parameters allows you to tune the system wide routingparameters. The system-wide parameters include the RFC 1583 compatibilitysetting, the shortest path first (SPF) algorithm tuning parameters, and the defaultsused when importing OSPF routes from the external autonomous system andadvertising these routes to other OSPF nodes. The RFC 1583 compatibility isenabled by default. It must be enabled if your environment includes other elementsthat are based on RFC 1583.The syntax of the command for configuring the global OSPF settings is:set routing [instance <name>] node <name> ospf The parameters (the part after the ospf parameter) for global OSPF settings arepresented in the table below:

Table 42 The commands for configuring global OSPF parameters

Parameter

Description

Value range

rfc1583-compatibility<on|off>

This parameter enables/disablesthe RFC 1583 compatibility. Thecurrent version supports OSPFv2as defined in RFC 2178. RFC 2178replaced earlier RFC 1583 byproviding improved security andloop avoidance.

The allowed values areon and off.The default value ison.

spf-delay <time> This parameter sets the delay inseconds between the first new LSAand the resulting SPF calculation(this is the calculation of a routingtable).


spf-holdtime<time>

This parameter sets the delay inseconds between successive SPFcalculations. The spf-holdtimeis not configurable and isdynamically determined by thespf-holdtime-start and spf-holdtime-max parameters. Thecurrent value of spf-holdtimecan be determined using the showrouting [instance<name>]node <name> ospf config[all] command.


default-ase-cost<value>

This parameter sets the defaultcost used for advertising non-OSPF routes as autonomoussystem external (ASE).


default-ase-type<1-2>

This parameter defines the type ofASE route used or use the default(1). For type 1 ASE, the total costof the route is the sum of the AS

The allowed values are1 and 2.The default value is 1.


222 DN0974301 Issue: 02G

Table 42 The commands for configuring global OSPF parameters (Cont.)

Parameter

Description

Value range

external and internal costs. Fortype 2 ASE, the cost of the route isalways the AS external cost.

throttle {spf-delay <time>}

This parameter specifies the timeto wait in milliseconds beforerecalculating the OSPF routingtable after a change in thetopology.

The allowed values arefrom 100 to 60000 mswith a granularity of100 ms.The default value is1000ms.

throttle{spf-holdtime-start<time>}

This parameter specifies the initialvalue to be used as delay betweenthe successive SPF calculations.This delay is also known as spf-holdtime. If a topology changeoccurs during the delay, it causesthe next spf-holdtime to beincreased by 100 ms until itreaches spf-holdtime-max. Ifthere are no topology changesduring the spf-holdtime waitinterval, the value of spf-holdtime will be reset to the initialvalue (spf-holdtime-start).

The allowed values arefrom 100 to 60000 mswith a granularity of100 ms.The default value is10000 ms.

throttle{spf-holdtime-max<time>}

This parameter specifies themaximum delay in millisecondsbetween the successive SPFcalculations. If a topology changeoccurs during the delay, it causesthe next spf-holdtime to beincreased by 100ms until it reachesspf-holdtime-max. If there areno topology changes during thespf-holdtime wait interval, thevalue of spf-holdtime will bereset to the initial value (spf-holdtime-start).


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 thefollowing table:


Issue: 02G DN0974301 223

Table 43 Parameters for monitoring OSPF protocol

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

config all This parameter displays an OSPF configuration for all routinginstances.

neighbors This parameter displays the IP addresses of neighboringinterfaces, their election priority and status and the number oferrors logged for each interface.

neighbor<IPADDRESS>

This parameter displays the neighbor router IDs, their electionpriority, DR states, hello dead counter, link local addresses,interfaces and errors.

interfaces This parameter displays the names of all configured OSPFinterfaces, their corresponding IP addresses, the area to whicheach interface is assigned, the status of each interface and theIP addresses of the designated router and backup designatedrouter of each logical interface.

interfacesdetailed

This parameter displays detailed information about each OSPFinterface, including the authentication type configured (if any),the router IDs and IP addresses of the designated router andbackup designated router, the timer intervals configured forhello, wait, dead and retransmit messages and the number ofneighbors for each interface.

interfacesstats

This parameter displays the number of each type of errormessage logged by each interface.

interface<IFNAME>

This parameter displays the information on the specified OSPFinterface.

interface<IFNAME> stats

This parameter displays the number of each type of errormessage logged by the specified interface.

interface<IFNAME>detailed

This parameter displays detailed information about thespecified interface, including the authentication type configuredif any, the router IDs and IP addresses of the designated routerand backup designated router, the timer intervals configured forhello wait, dead and retransmit messages and the number ofneighbors for each interface.

packets This parameter displays the number of each type of packetsent, including hello packets, link state update packets,database description packets and link state acknowledgmentand link state request packets.


224 DN0974301 Issue: 02G

Table 43 Parameters for monitoring OSPF protocol (Cont.)

Parameter

Description

errors This parameter displays the total number of each type of errormessage sent, including hello protocol errors, databasedescription errors, protocol errors, link state acknowledgmenterrors, link state request errors, link state update errors and IPerrors.

errors dd This parameter displays the database description errors.

errors hello This parameter displays the Hello protocol errors.

errors ip This parameter displays the IP errors.

errors lsack This parameter displays the link state acknowledgment errors.

errors lsu This parameter displays the link state update errors.

errors lsr This parameter displays the link state request errors.

errorsprotocol

This parameter displays the protocol errors.

border-routers This parameter displays the border router ID, type of the borderrouter and the cost to the border router.

database This parameter displays the OSPF link-state databaseinformation.

database areas This parameter displays router link state, network link state, ASborder router link state, AS external link state and summarylink state statistics for each OSPF area. Also displays thechecksum, sequence number and link count of each OSPFinterface.

database area<OSPF_AREA>

This parameter displays router link state, network link state, ASborder router link state, AS external link state and summarylink state statistics for the specified OSPF area. Also displaysthe checksum, sequence number and link count of each IPaddress configured within the specified OSPF area.

database asbr-summary-lsa

This parameter displays a summary of AS border router linkstate information for each OSPF area.

databasechecksum

This parameter displays a checksum calculated from the totalLSA database. It is useful for comparing databases on differentrouters.

databasedatabase-summary

This parameter displays a summary of router link state,network link state, summary link state and AS border router linkstate statistics.


Issue: 02G DN0974301 225


Parameter

Description

databasenetwork-lsa

This parameter displays network link state information,including the advertised router, sequence number andchecksum of each OSPF interface.

databaseexternal-lsa

This parameter displays AS external link state information.

databaserouter-lsa

This parameter displays a summary of router link stateinformation for each OSPF area.

databasesummary-lsa

This parameter displays a summary of link state information foreach OSPF area.

database type<1-5>

This parameter displays link state information associated withthe specified 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 examplenumber of interface up/down events, virtual interface up/downevents, designated router election events, router ID changes,area border router changes, AS border router changes andnumber of self LSA promos.

Further information

The parameters used in all the commands in this procedure are presented in thefollowing table:

Table 44 The OSPFv2 configuration parameters.

Parameter

Description

instance <name> The routing configuration is applied to or displayed from the virtualrouting instance specified by this parameter. This is an optionalparameter.If no instance is specified, the routing configuration isapplied to the default routing instance.

node <node-name> This parameter specifies the node name where the routeconfiguration takes place.


226 DN0974301 Issue: 02G

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 areaparameters, such as: backbone, stub, and totally-stubby.Create a backbone area with the backbone keyword. This automatically creates anidentifier 0.0.0.0 which is reserved exclusively for the backbone area. Create otherareas with your selected identifiers. The identifier should be given as a dotted/quadvalue or as a 32-bit number. You can use your subnetted IPv4 network address asarea IDs.The OSPF area configuration can be defined using the following command:set routing [instance <name>] node <name> ospf areaThe parameters of the commands (the part after the ospf parameter) are presentedin the following table.

Table 45 Commands for configuring OSPF areas

Parameter

Description

Value range

area backbone<on|off>

This parameterenables/disables the backbonearea. Enabling the backbonearea sets the area ID 0.0.0.0for the backbone area.


area <OSPF_AREA><on|off>

This parameterenables/disables an OSPFarea. Enabling the OSPF areasets the specified area ID.


area <OSPF_AREA>stub <on|off>

This parameterenables/disables an OSPFstub area. A stub area is anarea which does not haveexternal routes. Enabling theOSPF stub area sets thespecified area ID for the stubarea.


area <OSPF_AREA>stub default-cost<1- 16777215>

This parameter sets the costfor the default summary routefor the stub area.


area <OSPF_AREA>stub summary<on|off>

This parameter sets the stubarea to forward or blocksummary information. If a stubarea (area without externalroutes), does not havesummary routes it is called atotally-stubby-area.

The allowed values areon and off.The defaultvalue is off.


Issue: 02G DN0974301 227


Parameter

Description

Value range

area {backbone |<OSPF_AREA>} range<IP_PREFIX><on|off>

This parameter defines therange of networks belonging toan area.


area {backbone |<OSPF_AREA>} range<IP_PREFIX>restrict <on|off>

This parameter defines therange of networks belonging toan area in which the summarynetwork LSAs are not sent.


area {backbone |<OSPF_AREA>} stub-network <IP_PREFIX><on|off>

This parameter defines therange of networks belonging toa stub network.


area {backbone |<OSPF_AREA>} stub-network <IP_PREFIX>cost <1-65535>

This parameter defines thecost for the default route in astub network.


area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA><on|off>

This parameterenables/disables a virtual linkfrom the router that does nothave connection to a backbonenetwork. Virtual link is definedthrough an adjacent non-backbone area (transit area) bydefining the termination pointof the virtual link and the ID ofthe transit area. Thetermination point is the routerID of the adjacent area'sborder router having thebackbone connection. Thetransit area is an area that isshared by the router you areconfiguring and the routerhaving the backboneconnection. The area ID mustbe pre-configured using thebasic area commands.

The allowed values areon and off . Thedefault value is off.

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA> hello-interval <time>

This parameter sets the hello-interval in seconds for thevirtual link.



228 DN0974301 Issue: 02G


Parameter

Description

Value range

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA> dead-interval <time>

This parameter sets the dead-interval in seconds for thevirtual link.

The allowed values arefrom 1 to 4294967295.The default value is120.

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA>retransmit-interval<time>

This parameter sets theretransmit-interval in secondsfor the virtual link.


area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA>authtype none

This parameter disables theauthentication for the virtuallink.

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA>authtype simple

This parameter selects thesimple authentication type forthe virtual link and define the 1to 8 alpha numericalcharacters authentication key.Generally, routers on a givenlink must agree on theauthentication configuration toform a neighbor adjacency.The authentication scheme Isused to verify that the routinginformation is received fromtrusted peers.

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA>authtype md5 key<AUTH_KEYID> secret<MD5_SECRET>

This parameter selects theMD5 authentication. Enter atleast one key ID and itscorresponding MD5 secret. Inoutgoing packets, the MD5secret is included in encryptedform to authenticate the packetand if you configure multiplekey IDs, the largest key ID isused for authenticating thepackets. All keys can be usedto authenticate incomingpackets. Routers on a givenlink must agree on the

The allowedparameters are:


• <MD5_SECRET>:1 to 16�alphanumericcharacters..


Issue: 02G DN0974301 229


Parameter

Description

Value range

authentication configuration toform a neighbor adjacency.Use an authentication schemeto guarantee that routinginformation is accepted onlyfrom trusted peers.

g The MD5 secretshould besurrounded bydouble quotationmarks when non-alphanumericcharacters areused.

area backbonevirtual-link<ROUTER_ID>transit-area<OSPF_AREA>authtype md5 key<AUTH_KEYID> off

This parameter deletes theMD5 key in question.

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 whichthe equipment is integrated. Both hello-interval and dead-interval valuesshould 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 MD5authentication is used.To define the interface configuration, use the following command:set routing [instance <name>] node <name> ospf interfaceThe parameters of the command (the part after the ospf parameter) are presentedin the following table:

Table 46 Commands for configuring OSPF interfaces

Parameter

Description

Value range

interface<IFNAME> area{backbone |<OSPF_AREA>}<on|off>

This parameter assigns anOSPF area to an interface. Thearea should be defined earlier.


interface<IFNAME> hello-interval <time>

This parameter sets the hello-interval in seconds.



230 DN0974301 Issue: 02G


Parameter

Description

Value range

interface<IFNAME> fast-hello-interval

This parameter specifies thetime in milliseconds between thehello packets that the routersends to the interface.

The allowed values arefrom 50 to 950 ms witha granularity of 50 ms.The default value is 200ms.

interface<IFNAME> dead-interval <time>

This parameter sets the dead-interval in seconds.


interface<IFNAME>retransmit-interval <time>

This parameter sets theretransmit-interval in seconds.


interface<IFNAME> cost<value>

This parameter sets the cost forsending packets over aninterface.


interface<IFNAME> priority<value>

This parameter defines theelection priority for OSPFrouter/interface. The router withthe highest priority is selected tobe the designated router. Therouter with priority equal to 0 willnot be selected as thedesignated router.


interface<IFNAME> passive<on|off>

This parameter sets the OSPFinterface to passive state. Inpassive state, the OSPFinterface does not send hellopackets and therefore the linkdoes not form any adjacencies.


interface<IFNAME> authtypenone

This parameter disablesauthentication.

interface<IFNAME> authtypesimple <PASSWORD>

This parameter enables simpleauthentication and sets thepassword. Generally, routers ona given link must agree on theauthentication configuration toform neighbor adjacency. Theauthentication scheme is used toverify that the routing informationis received from trusted peers.

The allowed values are1 to 8 alpha numericalcharacters.


Issue: 02G DN0974301 231


Parameter

Description

Value range

interface<IFNAME> authtypemd5 key<AUTH_KEYID>secret<MD5_SECRET>

This parameter enables MD5authentication. Enter at least onekey ID and its correspondingMD5 secret. If you configuremultiple key ids, the largest keyID is used for authenticatingoutgoing packets. All keys canbe used to authenticateincoming packets. Routers on agiven link must agree on theauthentication configuration toform neighbor adjacency. Use anauthentication scheme toguarantee that routinginformation is accepted onlyfrom trusted peers.



• <MD5_SECRET>: 1to 16 alphanumericcharacters.

interface<IFNAME> authtypemd5 key<AUTH_KEYID> off

This parameter deletes the MD5key in question.


This parameter enables ordisables the BFD protocol for theOSPF interface. This is anoptional parameter.

g The BFD monitoring isdisabled by default.

The allowed values areenabled anddisabled.

bfd-tx-interval<tx-interval|default>

The minimum interval, inmilliseconds, between thetransmitted BFD control packetsthat the system uses at thecurrent time. This is an optionalparameter.

The allowed value is inthe range 50ms to60000ms with agranularity of 50ms. Thedefault value is 1000ms.

g This parameteraccepts either thenumeric value orthe valuedefault. If thevalue default isused, then thevalue ofbfd-tx-interval is setto a default valueof 1000ms.


232 DN0974301 Issue: 02G


Parameter

Description

Value range

bfd-rx-interval<rx-interval|default>

The minimum interval, inmilliseconds, between thereceived BFD control packetsthat the system requires. This isan optional parameter.

The allowed value is inthe range 50ms to60000 ms with agranularity of 50ms. Thedefault value is 1000ms.

g This parameteraccepts either thenumeric value orthe valuedefault. If thevalue default isused, then thevalue ofbfd-rx-interval is setto a default valueof 1000ms.


The desired detection timemultiplier for the BFD controlpackets on the local system. Thenegotiated control packettransmission interval, multipliedby this parameter, will be thedetection time for a particularBFD session. This is an optionalparameter.

The allowed value is inthe range 1 to 50. Thedefault value is 4.

g This parameteraccepts either thenumeric value orthe valuedefault. If thevalue default isused, then thevalue ofbfd-detect-mult is set to adefault value of 4.

3 Configure global OSPF parameters.A set of generic OSPF parameters allows you to tune the system wide routingparameters. The system-wide parameters include the RFC 1583 compatibilitysetting, the shortest path first (SPF) algorithm tuning parameters, and the defaultsused when importing OSPF routes from the external autonomous system andadvertising these routes to other OSPF nodes. The RFC 1583 compatibility isenabled by default. It must be enabled if your environment includes other elementsthat are based on RFC 1583.The syntax of the command for configuring the global OSPF settings is:set routing [instance <name>] node <name> ospf The parameters (the part after the ospf parameter) for global OSPF settings arepresented in the table below:


Issue: 02G DN0974301 233

Table 47 The commands for configuring global OSPF parameters

Parameter

Description

Value range

rfc1583-compatibility<on|off>

This parameter enables/disablesthe RFC 1583 compatibility. Thecurrent version supports OSPFv2as defined in RFC 2178. RFC 2178replaced earlier RFC 1583 byproviding improved security andloop avoidance.

The allowed values areon and off.The default value ison.

spf-delay <time> This parameter sets the delay inseconds between the first new LSAand the resulting SPF calculation(this is the calculation of a routingtable).


spf-holdtime<time>

This parameter sets the delay inseconds between successive SPFcalculations. The spf-holdtimeis not configurable and isdynamically determined by thespf-holdtime-start and spf-holdtime-max parameters. Thecurrent value of spf-holdtimecan be determined using the showrouting [instance<name>]node <name> ospf config[all] command.


default-ase-cost<value>

This parameter sets the defaultcost used for advertising non-OSPF routes as autonomoussystem external (ASE).


default-ase-type<1-2>

This parameter defines the type ofASE route used or use the default(1). For type 1 ASE, the total costof the route is the sum of the ASexternal and internal costs. Fortype 2 ASE, the cost of the route isalways the AS external cost.

The allowed values are1 and 2.The default value is 1.

throttle {spf-delay <time>}

This parameter specifies the timeto wait in milliseconds beforerecalculating the OSPF routingtable after a change in thetopology.

The allowed values arefrom 100 to 60000 mswith a granularity of100 ms.The default value is1000ms.


234 DN0974301 Issue: 02G

Table 47 The commands for configuring global OSPF parameters (Cont.)

Parameter

Description

Value range

throttle{spf-holdtime-start<time>}

This parameter specifies the initialvalue to be used as delay betweenthe successive SPF calculations.This delay is also known as spf-holdtime. If a topology changeoccurs during the delay, it causesthe next spf-holdtime to beincreased by 100 ms until itreaches spf-holdtime-max. Ifthere are no topology changesduring the spf-holdtime waitinterval, the value of spf-holdtime will be reset to the initialvalue (spf-holdtime-start).


throttle{spf-holdtime-max<time>}

This parameter specifies themaximum delay in millisecondsbetween the successive SPFcalculations. If a topology changeoccurs during the delay, it causesthe next spf-holdtime to beincreased by 100ms until it reachesspf-holdtime-max. If there areno topology changes during thespf-holdtime wait interval, thevalue of spf-holdtime will bereset to the initial value (spf-holdtime-start).


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 thefollowing table:

Table 48 Parameters for monitoring OSPF protocol

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

config all This parameter displays an OSPF configuration for all routinginstances.


Issue: 02G DN0974301 235


Parameter

Description

neighbors This parameter displays the IP addresses of neighboringinterfaces, their election priority and status and the number oferrors logged for each interface.

neighbor<IPADDRESS>

This parameter displays the neighbor router IDs, their electionpriority, DR states, hello dead counter, link local addresses,interfaces and errors.

interfaces This parameter displays the names of all configured OSPFinterfaces, their corresponding IP addresses, the area to whicheach interface is assigned, the status of each interface and theIP addresses of the designated router and backup designatedrouter of each logical interface.

interfacesdetailed

This parameter displays detailed information about each OSPFinterface, including the authentication type configured (if any),the router IDs and IP addresses of the designated router andbackup designated router, the timer intervals configured forhello, wait, dead and retransmit messages and the number ofneighbors for each interface.

interfacesstats

This parameter displays the number of each type of errormessage logged by each interface.

interface<IFNAME>

This parameter displays the information on the specified OSPFinterface.

interface<IFNAME> stats

This parameter displays the number of each type of errormessage logged by the specified interface.

interface<IFNAME>detailed

This parameter displays detailed information about thespecified interface, including the authentication type configuredif any, the router IDs and IP addresses of the designated routerand backup designated router, the timer intervals configured forhello wait, dead and retransmit messages and the number ofneighbors for each interface.

packets This parameter displays the number of each type of packetsent, including hello packets, link state update packets,database description packets and link state acknowledgmentand link state request packets.

errors This parameter displays the total number of each type of errormessage sent, including hello protocol errors, databasedescription errors, protocol errors, link state acknowledgmenterrors, link state request errors, link state update errors and IPerrors.

errors dd This parameter displays the database description errors.


236 DN0974301 Issue: 02G


Parameter

Description

errors hello This parameter displays the Hello protocol errors.

errors ip This parameter displays the IP errors.

errors lsack This parameter displays the link state acknowledgment errors.

errors lsu This parameter displays the link state update errors.

errors lsr This parameter displays the link state request errors.

errorsprotocol

This parameter displays the protocol errors.

border-routers This parameter displays the border router ID, type of the borderrouter and the cost to the border router.

database This parameter displays the OSPF link-state databaseinformation.

database areas This parameter displays router link state, network link state, ASborder router link state, AS external link state and summarylink state statistics for each OSPF area. Also displays thechecksum, sequence number and link count of each OSPFinterface.

database area<OSPF_AREA>

This parameter displays router link state, network link state, ASborder router link state, AS external link state and summarylink state statistics for the specified OSPF area. Also displaysthe checksum, sequence number and link count of each IPaddress configured within the specified OSPF area.

database asbr-summary-lsa

This parameter displays a summary of AS border router linkstate information for each OSPF area.

databasechecksum

This parameter displays a checksum calculated from the totalLSA database. It is useful for comparing databases on differentrouters.

databasedatabase-summary

This parameter displays a summary of router link state,network link state, summary link state and AS border router linkstate statistics.

databasenetwork-lsa

This parameter displays network link state information,including the advertised router, sequence number andchecksum of each OSPF interface.

databaseexternal-lsa

This parameter displays AS external link state information.


Issue: 02G DN0974301 237


Parameter

Description

databaserouter-lsa

This parameter displays a summary of router link stateinformation for each OSPF area.

databasesummary-lsa

This parameter displays a summary of link state information foreach OSPF area.

database type<1-5>

This parameter displays link state information associated withthe specified 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 examplenumber of interface up/down events, virtual interface up/downevents, designated router election events, router ID changes,area border router changes, AS border router changes andnumber of self LSA promos.

5.3.3 Redistributing routes to OSPF protocolPurpose

This section shows how to redistribute routes to OSPF protocol.

Further information

The parameters for the route redistribution commands are listed in the following table:

Table 49 Parameters for redistributing routes between protocols

Parameter

Description

Value range

instance The routing configuration isapplied to the virtual routinginstance specified by thisparameter. This is an optionalparameter. If no instance isspecified, the routingconfiguration is applied to thedefault routing instance.

-


238 DN0974301 Issue: 02G

Table 49 Parameters for redistributing routes between protocols (Cont.)

Parameter

Description

Value range

node <node-name> This parameter specifies thename of the node where the routeredistributing takes place.

-

export <export-protocol>

This parameter specifies thename of the protocol where toredistribute the routes to.

The allowed value isospf2ase.

aggregate<IP_prefix>

This parameter specifies thenetwork address of the aggregateroute.

The value can be either aspecific route in the formatprefix/mask, or all for allroutes.

cost <cost-value> Specifies the cost for the createdexternal route.

The cost value can be in therange from 1 to 16777215.

static-route <route> Specifies the static route to beredistributed to the OSPF externalroute.

Use value all to redistributeall static routes, or give theindividual route in the form ofprefix/mask.

direct {all |interface-name<name>}

This parameter specifies that allcurrently active routes must beredistributed into the OSPFexternal route. If this setting is'on', routes can be individuallyrestricted into OSPF externalroute and vice-versa.

Use value all to redistributeall interface routes, or givethe interface-nameparameter followed by thename of the individualinterface.

Redistribute static routes

Purpose

To redistribute static routes to OSPF protocol.

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:set routing [instance <name>] node <node-name> export <export- protocol> static-route <route> cost <cost-value>


Issue: 02G DN0974301 239

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:set routing [instance <name>] node <node-name> export <export- protocol> static-route <route> cost <cost-value>

Redistribute aggregate routes

Purpose

To redistribute aggregate routes to OSPF protocol.

1 Enable the redistribution.The aggregate routes are exported by using the following command:set routing [instance <name>] node <node-name> export <export- protocol> aggregate <IP_prefix> on

2 Set the cost for the exported route.The cost for the exported route is set by using the following command:set routing [instance <name>] node <node-name> export <export- protocol> aggregate <IP_prefix> cost <cost-value>

Steps

1 Enable the redistribution.The aggregate routes are exported by using the following command:set routing [instance <name>] node <node-name> export <export- protocol> aggregate <IP_prefix> on

2 Set the cost for the exported route.The cost for the exported route is set by using the following command:set routing [instance <name>] node <node-name> export <export- protocol> aggregate <IP_prefix> cost <cost-value>

Redistribute direct routes

Purpose

To redistribute direct routes to OSPF protocol.


240 DN0974301 Issue: 02G

1 Enable the redistribution.The direct interface routes are exported by using the following command:set routing [instance <name>] node <node-name> export <export- protocol> direct {all | interface-name <name>} on

2 Set the cost for the exported route.The cost for the exported route is set by using the following command:set routing [instance <name>] node <node-name> export <export- protocol> direct {all | interface-name <name>} cost <cost-value>

Steps

1 Enable the redistribution.The direct interface routes are exported by using the following command:set routing [instance <name>] node <node-name> export <export- protocol> direct {all | interface-name <name>} on

2 Set the cost for the exported route.The cost for the exported route is set by using the following command:set routing [instance <name>] node <node-name> export <export- protocol> direct {all | interface-name <name>} cost <cost-value>

5.4 Configuring virtual routingPurpose

Virtual Routing and Forwarding (VRF) means the virtualization of transmission controlprotocol/Internet protocol (TCP/IP) stack and routing. Each routing instance acts as aseparate router within the same physical hardware. Packet forwarding and terminationwill be done in the context of the routing instance.

Each routing instance has a separate forwarding table. Different routing instances canhave overlapping IP addresses.

When using virtual routing, each logical IP interface (VLAN, tunnel interface) is assignedto a specific routing instance, not directly to the interface. This is done by using the sameIP management commands as without virtual routing, but including the instance<name> parameter in the command.

There is no other general configuration for virtual routing than creating the routinginstances. They are created by using the add networking vrf structured commandline interface command.

There are two basic use cases for virtual routing:

• isolating IP interfaces• making connections to separate corporate networks


Issue: 02G DN0974301 241

Before you start

Before deleting the VRF instance, ensure that:

• all interfaces in the VRF instance are deleted or moved to another instance.• other configurations referring to the VRF instance have been removed.

1 Create the routing instance.To create a routing instance, enter the following command:add networking vrf name <name> [id <id>] [node <node>]

g Do not specify the node name when you create a VRF on the mcRNC.

2 Verify the routing instances.To check the existing routing instances, enter the following command:show networking vrfExpected outcomeThe printout is, for example: default VRFid : 0 vrf_1 VRFid : 1

3 Delete a routing instance.Remove the instance by using the following command:delete networking vrf name <name>

g The default routing instance cannot be removed.

Further information

Table 50: Parameters for virtual routing lists the parameters used with the networkingvrf commands.

Table 50 Parameters for virtual routing

Parameter

Description

Value Range

name <name> Specifies the name for a specific virtualrouting instance.

The name of the default routing instanceis default and ID is 0. The defaultrouting instance cannot be removed.

g When creating several VRFinstances, use transactions tospeed up the process.

The allowed values arecharacters a to z, A to Z, 0 to9, and _ (lower case, uppercase, numeric and underscore).The maximum length is 15characters and the minimumlength is 1 character.


242 DN0974301 Issue: 02G

Table 50 Parameters for virtual routing (Cont.)

Parameter

Description

Value Range

id <id> Specifies the numeric identifier of therouting instance.

The allowed value range isfrom 1 to 63.

node <node> Specifies the node name. The node maybe a management/service blade. Uponexecution, specifies the available node.

g Leave this parameter empty whenyou create a VRF on the mcRNC.


Issue: 02G DN0974301 243

6 Configuring IP-based routePurpose

User plane traffic scheduling, transport layer admission is managed with object classcalled IP-based route (IPBR). The user plane source IP address selection related to theIP-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 (package 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 IPaddress is selected from.

The logical IP connection admission control (CAC) function operates at IP layer. Thecommitted bit rate attribute defines the limit that system can admit connections to thesystem.

The IP-based route level shaping and scheduling provides real queue based and virtualqueue based scheduling options. For more information, see QoS configuration overview.

If you want to enable load sharing on the IP-based route(s), you can attach one or twoIP-based routes to one or two IP addresses with FULL PHB set towards the samenetwoking element. For example, the following configurations are supported for Iubinterface:

• Option A:

– IP-based route 1 -> IP address 1 -> PHB set ALL -> BTS 1– IP-based route 1 -> IP address 2 -> PHB set ALL -> BTS 1

• Option B:

– IP-based route 1 -> IP address 1 -> PHB set ALL -> BTS 1– IP-based route 2 -> IP address 2 -> PHB set ALL -> BTS 1

If you want to enable VLAN traffic differentiation on the IP-based route(s) for Iub userplane traffic, you can attach one or two IP-based routes to two IP addresses with trafficdifferentiation PHB sets towards the same BTS. For example, the followingconfigurations are supported:

• Option A:

– IP-based route 1 -> IP address 1 -> PHB sets EF, AF4, AF3 -> BTS 1– IP-based route 1 -> IP address 2 -> PHB sets AF2, AF1, BE -> BTS 1

• Option B:


244 DN0974301 Issue: 02G

– IP-based route 1 -> IP address 1 -> PHB sets EF, AF4, AF3 -> BTS 1– IP-based route 2 -> IP address 2 -> PHB sets AF2, AF1, BE -> BTS 1

g VLAN traffic differentiation mode is only supported on Iub interface. The values of thedifferentiation PHB sets towards a certain BTS together cover all the six PHBs, andoverlapping is not allowed.

Before you start

The transport network planning has to be available to fill in a proper schedulingbandwidth and committed bit rate values. This applies for the case that connectionadmission control and IP layer scheduling is applied for the given connections.

To minimize the impact on the ongoing traffic, lock the related cells before modifying theUDP multiplexing configurations. For more information, see Activating RAN1886:Efficient Transport for Small IP Packets.

1 Create IP-based route.Use the add networking ipbr command to create an IPBR.add networking ipbr ipbr-id <ipbr-id> ipbr-name <ipbr-name>committed-bandwidth <committed-bandwidth> committed-dcn-bandwidth <committed-dcn-bandwidth> committed-sig-bandwidth<committed-sig-bandwidth> route-bandwidth <route-bandwidth>[dspm-profile-id <dspm-profile-id>] [ifc-nrtdch <ifc-nrtdch>][ifc-nrthsdpa <ifc-nrthsdpa>] [local-mux-port <local-mux-port>] [max-mux-packets <max-mux-packets>] [mux-dscp <mux-dscp>] [mux-enable <mux-enable>] [phb-profile-id <phb-profile-id>] [remote-mux-port <remote-mux-port>] [scheduler-type<scheduler-type>]

Use the command add networking ipbr to create an IPBR. The followingconditions should be fulfilled to create the IPBR successfully:

• Parameters route-bandwidth, committed-bandwidth, committed-dcn-bandwidth, and committed-sig-bandwidth must fulfill all the conditionsbelow to perform the CAC on the IP-based route:

– committed-bandwidth >= (Bit rate of IP connection) +committed-sig-bandwidth + committed-dcn-bandwidth

– committed-bandwidth <= route-bandwidth

• If the CAC is not needed on the IP-based route, set committed-bandwidth,committed-dcn-bandwidth, and committed-sig-bandwidth all to zero.For further information on CAC, refer to RNC/Flexi Direct BTS CAC.

• When the route-bandwidth is zero (CAC is off), set scheduler-type tonone.

• When parameter scheduler-type is set to none or realQueue, parametersifc-nrtdch and ifc-nrthsdpa only can be set to E-RED.

g UDP multiplexing can be only used for Iub/Iur. License is required to enable this feature.

Route bandwidth and committed bandwidth depend on the site solution, routing path,and network element. Configure route bandwidth and committed bandwidth to valuesnot large than 1G in the following cases:

Configuring IP Connection for Multicontroller RNC Configuring IP-based route

Issue: 02G DN0974301 245

wcdma_ran_ip_transport.pdf

• The IP-based route is bound to an IP address configured on an 1G Ethernetinterface.

• The IP-based route is bound to an IP address routed on 1G Ethernet interface.• The IP-based route is configured for the Iub interface.

You can find the parameters for add networking ipbr command in Table 51:Parameters for networking ipbr commands.

Example

1. Add an IP-based route with name TEST-ID-1000.

add networking 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 0phb-profile-id 0 ifc-nrtdch IFC ifc-nrthsdpa E-RED scheduler-type virtualQueue

2. Add an IP-based route with UDP multiplexing enabled.

add networking ipbr ipbr-id 1 ipbr-name 1 mux-enable enablecommitted-bandwidth 1000000 committed-sig-bandwidth 1committed-dcn-bandwidth 1 route-bandwidth 1000000

2 Check the configured IP-based routes.The configured IP-based routes can be listed with the show networking ipbrcommand.show networking ipbr [ipbr-id <ipbr-id>] [ipbr-name <ipbr-name>]

You can find the parameters for show networking ipbr command in Table 51:Parameters for networking ipbr commands.

Example

1. Show the IP-based route with ID1000.

show networking ipbr ipbr-id 1000

2. Show all the IP-based routes configured.

show networking ipbr

3 Modify the IP-based routes if update is required.The configured IP-based routes can be modified with the set networking ipbrcommand.set networking ipbr ipbr-id <ipbr-id> [ipbr-name <ipbr-name>][committed-bandwidth <committed-bandwidth>] [committed-dcn-bandwidth <committed-dcn-bandwidth>] [committed-sig-bandwidth<committed-sig-bandwidth>] [route-bandwidth <route-bandwidth>][dspm-profile-id <dspm-profile-id>] [ifc-nrtdch <ifc-nrtdch>][ifc-nrthsdpa <ifc-nrthsdpa>] [local-mux-port <local-mux-port>] [max-mux-packets <max-mux-packets>] [mux-dscp <mux-

Configuring IP-based route Configuring IP Connection for Multicontroller RNC

246 DN0974301 Issue: 02G

dscp>] [mux-enable <mux-enable>] [mode <mode>] [phb-profile-id<phb-profile-id>] [remote-mux-port <remote-mux-port>][scheduler-type <scheduler-type>]

You can find the parameters for set networking ipbr command in Table 51:Parameters for networking ipbr commands.

g Forced update is provided when you want to modify the local-mux-port when thereare transport bearers on the local UDP port with the IP-based route.If you modify the IP multiplexing parameters by using IP Plan, the parameters areforced to be updated.

Example

1. Set the bandwidth for the IP-based route with ID 1000:

set networking ipbr ipbr-id 1000 route-bandwidth 10000000committed-bandwidth 10000000 committed-sig-bandwidth 50000committed-dcn-bandwidth 10000

4 Bind an IP address with the IP-based route.Use the add networking ipro command to associate an IP address with the IP-based route.add networking ipro owner <owner> ip-address <ip-address>ipbr-id <ipbr-id> iface <interface> [mode <mode>] [phb-set<phb-set>] [vrf <vrf>]

You can find the parameters for add networking ipro command in Table 52:Parameters for networking ipro commands.

g The IP-based route can only be bound to QNUP recovery group.

Example

1. Associate the IP address 192.140.73.1 to the IP-based route whose ID is 1000.

add networking ipro iface lo ip-address 192.140.73.1 ipbr-id 1000 owner /QNUP-0

2. Add an association and specify the VRF instance.

add networking ipro iface lo ip-address 192.140.73.1 ipbr-id 1000 owner /QNUP-0 vrf vrf1

5 Change the PHB settings for an IP-based route.Use the set networking ipro command, you can change the PHB settings ofthe IP-based route.set networking ipro owner <owner> ip-address <ip-address>ipbr-id <ipbr-id> iface <interface> [phb-set <phb-set>]

You can find the parameters for set networking ipro command in Table 52:Parameters for networking ipro commands.

Example


Issue: 02G DN0974301 247

Change the PHB set value of the IP-based route associated with IP 192.140.73.1 toBE.

set networking ipro owner /QNUP-0 iface lo ipbr-id 1000 ip-address 192.140.73.1 phb-set BE

6 Show the configured associations between IP address and IP-based route.Use the show networking ipro command to show an IP address associated withthe IP-based route.show networking ipro [owner <owner>] [ip-address <ip-address>][ipbr-id <ipbr-id>] [iface <interface>] [vrf <vrf>]

You can find the parameters for show networking ipro command in Table 52:Parameters for networking ipro commands.

Example

Show all IP address and IP-based route associations on recovery group QNUP-0:

show networking ipro owner /QNUP-0

7 Delete the association between IP address and IP-based route.Use the delete networking ipro command to delete an IP address associatedwith the IPBR.delete networking ipro owner <owner> ip-address <ip-address>ipbr-id <ipbr-id> iface <interface> [mode <mode>]

You can find the parameters for delete networking ipro command in Table 52:Parameters for networking ipro commands.

Example

Delete an association:

delete networking ipro ipbr-id 1000 iface lo ip-address 192.140.73.1 owner /QNUP-0

8 Delete the IP-based route.Use the delete networking ipbr command to delete an IPBR.You can find the parameters for delete networking ipbr command in Table 51:Parameters for networking ipbr commands.ExampleDelete the IP-based route with ID 1000 and name TEST-ID-1000:delete networking ipbr ipbr-id 1000 ipbr-name TEST-ID-1000

Further information

Table 51: Parameters for networking ipbr commands lists the parameters for commandsadd networking ipbr, show networking ipbr, set networking ipbr anddelete networking ipbr.


248 DN0974301 Issue: 02G

Table 51 Parameters for networking ipbr commands

Parameter

Description

Value range

ipbr-id This parameter specifies the IP-based route (IPBR) ID.

1 - 4095

ipbr-name This parameter specifies the IP-based route name (caseinsensitive).

The string length is of maximum15 characters. The allowedcharacters are a-z, A-Z, 0-9, ".", "-" (lower case, upper case,numeric, dot and hyphen).

committed-bandwidth

This parameter specifies the IP-based route committed bandwidthlimit in kbps.

0 - 10000000

route-bandwidth This parameter specifies the IP-based route route bandwidth limitin kbps.

0 - 10000000

committed-dcn-bandwidth

This parameter specifies the IP-based route committed DCNbandwidth in kbps.

0 - 1000

committed-sig-bandwidth

This parameter specifies the IP-based route committed signalingbandwidth in kbps.

0 - 50000

dspm-profile-id This parameter specifies theDSCP to PHB mapping profile ID.

g To view existing DSCP toPHB mapping profiles,enter commandshow networking qos-profile idsp.

The allowed values are from 0 to10.

The default value is 0.

ifc-nrtdch This parameter specifiec the IP-based route internal flow control(IFC) behavior for non-real timeDCH traffic.


• E-RED (When congestionoccurs the packets aredropped.)

• IFC (When congestionoccurs notifications are sentto the sender.)

The default value is E-RED

ifc-nrthsdpa This parameter specifies the IP-based route IFC behavior for non-real time HSDPA traffic.


• E-RED (When congestionoccurs the packets aredropped.)


Issue: 02G DN0974301 249

Table 51 Parameters for networking ipbr commands (Cont.)

Parameter

Description

Value range

• IFC (When congestionoccurs notifications are sentto the sender.)

The default value is E-RED

phb-profile-id This parameter specifies the PHBprofile ID for QoS.

g To view existing PHBprofiles, enter commandshow networking qos-profile iphb.

The allowed values are from 0 to10.


scheduler-type This parameter specifies thescheduler type.

For more information on the realqueue and virtual queue, seeQoS configuration overview.


• none

• virtualQueue

• realQueue

The default value is none.

local-mux-port This parameter specifies the localUDP port for IP multiplexing.

The allowed value range is 49152- 65535.


max-mux-packets This parameter specifies themaximum number of packets inone multiplexed IP packet.

The allowed value range is 1 - 30.


mux-dscp This parameter specifies theDSCP value for IP multiplexing.

The allowed value range is 0 - 63.


mux-enable This parameter enables ordisables the IP multiplexing.

The allowed values are disableand enable.

The default value is disable.

remote-mux-port This parameter specifies theremote UDP port for the IPmultiplexing.

The allowed value range is 49152- 65535.


mode This parameter specifies theoperation mode of settingparameter local-mux-port ofthe IP-based route.

When there are transport bearersset up on IP address which isbound with the IP-based route,and on the local-mux-port of the


• normal

• force

The default value is normal.


250 DN0974301 Issue: 02G

Table 51 Parameters for networking ipbr commands (Cont.)

Parameter

Description

Value range

IP-based route, you can useforce mode to set the local-mux-port, and remove transportbearers at the same time. Whileby using normal mode theoperation is rejected.

Table 52: Parameters for networking ipro commands lists the parameters for commandsadd networking ipro, show networking ipro, set networking ipro anddelete networking ipro.

Table 52 Parameters for networking ipro commands

Parameter

Details

Value range

owner This parameter specifies theowner of the user plane IPaddress.

ip-address This parameter specifies the userplane IP address which isattached to the IP-based route.

ipbr-id This parameter specifies the IP-based route ID.

1 - 4095

iface This parameter specifies thenetwork interface on which theuser plane IP address isconfigured.

phb-set This is the PHB classes to beenabled for an IPRO.

The allowed values can be ALLor a group of consecutive classesin the PHB class set (EF, AF4,AF3, AF2, AF1, BE). At leasteither EF or BE should beincluded.

When set to ALL, all the sixclasses are enabled.

The default value is ALL.

vrf This is the name of the virtualrouting and forwarding instance.

The string length is of maximum15 characters. The allowedcharacters are a-z, A-Z, 0-9, and"_" (lower case, upper case,numeric and underscore).


Issue: 02G DN0974301 251

Table 52 Parameters for networking ipro commands (Cont.)

Parameter

Details

Value range

mode This parameter specifies themode in use.

If you want to add an IPRO whenthere are transport bearers basedon the IP address which is boundto the IP-based route and thelocal-mux-port of the IP-basedroute, you can succeed with theforce mode.

If you want to delete an IPROwhen there are transport bearersbased on it, you can succeed withthe force mode.

By using normal mode, bothoperations fail.


• normal

• force

The default value is normal.


252 DN0974301 Issue: 02G

7 Configuring QoS

7.1 QoS configuration overviewEgress traffic scheduling in the Multicontroller RNC (mcRNC) is configured at two levelsin a hierarchical structure as shown in the figure below.

Figure 46 Traffic scheduling hierarchy

The highest level is IP-based route level. It performs traffic scheduling and shaping onthe IP layer. The second level is interface level which does traffic scheduling based onthe network interface, including Ethernet interface or Link Aggregation Group interface.Each network interface aggregates the egress traffic forwarded to the given physicalinterface.

For VLAN interface, the 3-bit Priority Code Point (PCP) field in the VLAN tag is used todifferentiate traffic in the external network. Usage of the PCP field for this purpose isdefined in IEEE 802.1p. The vlanmapping SCLI command can be used to define themapping between PCP values and the Differentiated Services Code Point (DSCP) foroutgoing 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 RNCsource IP address is selected from. The IP-based route is used for the user planeconnections 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 IPaddress selection operates in load sharing or non-load sharing mode.


Issue: 02G DN0974301 253

The logical IP connection admission control function operates at IP layer. The committedbit 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 sharingconfiguration and it can be also disabled with setting the committed bit rate to 0.

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 wherethe packets are queued while the virtual scheduling is based on triggering the InternalFlow Control (IFC) or packet drop events (E-RED based) for the data according to thestatus seen by the virtual scheduling. The real-queue-based scheduling is able toprovide more accurate traffic shaping compared to rate limiting of the virtual scheduler.The virtual scheduling can minimize the delays generated at the transport layer withkeeping the egress queues as short as possible.

The queue selection at the IP-based route level takes place via DSCP to PHB mappingprofile configured via IDSP object class. The DSCP profile is used to map certain DSCPvalues 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

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

type of handling for the user plane traffic.

Table 53 Scheduling methods used for logical interfaces

Combinations

Iub

Iur

Iu-CS

Iu-PS

None x x x x

VQ+IFC x - - -

VQ+E-RED x x x x

RQ+E-RED x x x x

The following sub-chapters show how to configure a DSCP profile, PHB profile andspecify 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

Configuring QoS Configuring IP Connection for Multicontroller RNC

254 DN0974301 Issue: 02G

• Packet scheduler

In addition, a number of non-user configurable measures are addressed inside thecluster to prioritize all internal as well as high priority external traffic.

The classifier, filter, and marker are implemented in Access Control List (ACL). The ACLrules classify packets into packet flows based on the following selectors:

• Virtual Routing and Forwarding instance• Any type of interface• 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 supported: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 tohandle (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 additionalfragments are following the first fragment. Because of this fact use of port basedrules in PREROUTING and POSTROUTING chains is not recommended.)

An ACL rule can accept or drop the classified packet flow. The ACL can also performmarking 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 ofService (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 and7, 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 UMTSQoS class or DiffServ per-hop behavior (PHB) type translates into the correspondingDSCP value (equivalent to the corresponding TOS byte value where the two last bits areexcluded).

Table 54 DSCP encoding for different UMTS QoS classes or DiffServ PHB types.

UMTS QoS class

DiffServ PHB

DSCP hex value

DSCP binary value

Conversational Expedited Forwarding (EF) 0x2e 101110

Streaming Assured Forwarding (AF11) 0x0a 001010

Interactive, traffichandling priority 1

Assured Forwarding (AF21) 0x12 010010


Assured Forwarding (AF31) 0x1a 011010


Assured Forwarding (AF41) 0x22 100010

Configuring IP Connection for Multicontroller RNC Configuring QoS

Issue: 02G DN0974301 255

Table 54 DSCP encoding for different UMTS QoS classes or DiffServ PHB types.(Cont.)

UMTS QoS class

DiffServ PHB

DSCP hex value

DSCP binary value

Background Best Effort (BE) 0x00 000000

Dropper/policer, buffer manager, and packet scheduler are implemented as a set ofqueues per egress port. Each queue buffers packets of a particular PIP. The schedulerschedules (dequeue) packets from the queues based on the queue priority. In case ofegress link congestion, packets from high priority queues will have higher chance to bescheduled with lowest delay. Length of the queue is managed by a queue managementalgorithm. Tail Drop, as an absolute dropping algorithm, discards all packets exceedingthe configured threshold.

g The longer the queue is, the more system resources are used, and the moreunnecessary packet flow latency is created.

7.2 Configuring QoS for IP-based route7.2.1 Configuring DSCP to PHB mapping profile

Purpose

The DSCP to PHB mapping profiles is configured by using the structured command lineinterface (SCLI) commands. This group of commands has a wide set of commands forconfiguration, interrogation and deletion of the DSCP mapping profiles. A default DSCPprofile, 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 noDSCP values are specified for a queue are specified during the configuration, the defaultvalues are used. But if you specify a DSCP value that by default in another queue, thevalue is removed from the original queue and reassigned to the new queue.

g A default mapping profile with ID 0 exists in the system and it cannot be modified ordeleted.

Table 55 DSCP to PHB mapping

PHB

DSCP values

EF 46

AF1 10, 12, 14

AF2 18, 20, 22


256 DN0974301 Issue: 02G

Table 55 DSCP to PHB mapping (Cont.)

PHB

DSCP values

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

1 Create the DSCP profile.Use the add networking qos-profile idsp command to add a DSCPmapping profile to the system. The syntax of this command is as follows:add networking 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>]

g To specify more than one DSCP values for a PHB class, separate them by commawithout any space.

Example

Create a DSCP profile with default mappings.

add networking qos-profile idsp idsp-id 1 idsp-name idsp-1

2 Modify the DSCP profile configuration.Use the set networking qos-profile idsp command to update an existingDSCP mapping profile. The syntax is as follows:set networking 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 networking qos-profile idsp idsp-id 1 idsp-name idsp-1af1-queue 10,12,43

The DSCP value 43 that is initially assigned to BE queue is reassigned to AF1queue. And the other default value for AF1 queue remain unchanged. The DSCPmapping profile after executing this command is as follows:

profileID profileName phb dscpValue1 idsp-1 BE 0 1 2 3 4 5 6 7 8 9 11 13 15 16 17 19 21 23 24 25


Issue: 02G DN0974301 257

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 631 idsp-1 EF 461 idsp-1 AF1 10 12 14 431 idsp-1 AF2 18 20 221 idsp-1 AF3 26 28 301 idsp-1 AF4 34 36 38

3 Show the DSCP profile configuration.Use the show networking qos-profile idsp to check the configured DSCPprofile including the default DSCP profile. When no parameter is given, all theprofiles will be listed. The syntax is as follows:show networking qos-profile idsp [idsp-id <idsp-id>] [idsp-name <idsp-name>]

Example

show networking qos-profile idsp idsp-id 1 idsp-name idsp-1

4 Delete the DSCP profile configuration.Use the delete networking qos-profile idsp command to delete the DSCPprofile. If the profile is in use, for example, the profile has been assigned to one ormore IP-based route, you need to delete the associated target before deleting theDSCP profile. The syntax of this command is as follows:delete networking qos-profile idsp idsp-id <idsp-id>

Example

delete networking qos-profile idsp idsp-id 1

User case: Configuring the DSCP profile

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

1. Add a DSCP profile.add networking qos-profile idsp idsp-id 1 idsp-name idsp-1

2. Configure the new DSCP profile by the given name and ID.set networking qos-profile idsp idsp-id 1 idsp-name idsp-1af1-queue 10,12,43

3. List the newly created DSCP profile by the name.show networking qos-profile idsp idsp-id 1 idsp-name idsp-1

Further information

For more information on the usage of the qos-profile SCLI command, see MulticontrollerRNC SCLI Commands.


258 DN0974301 Issue: 02G

7.2.2 Configuring PHB profilePurpose

To configure PHB profile using SCLI command. The PHB profile specifies algorithmparameters 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 bemodified or removed.

1 Create the PHB profile.Use the add networking qos-profile iphb command to create the PHBprofile. The syntax is as follows:add networking qos-profile iphb iphb-id <iphb-id> iphb-name <iphb- name> [af1-queue <weight,minThresh,maxThresh,maxProb,expWeight>] [af2-queue <weight,minThresh,maxThresh,maxProb,expWeight>] [af3-queue <weight,minThresh,maxThresh,maxProb,expWeight>] [af4-queue <weight,minThresh,maxThresh,maxProb,expWeight>] [be-queue <weight,minThresh,maxThresh,maxProb,expWeight>]

Example

Create a PHB profile and use default values for AF1, AF2, AF3, AF4, EF and BE.

add networking qos-profile iphb iphb-id 1 iphb-name iphb-1

2 Modify the PHB profile configuration.Use the set networking qos-profile iphb command to update the PHBprofile. The syntax is as follows:set networking qos-profile iphb iphb-id <iphb-id> [iphb-name <iphb- name>] [af1-queue <weight,minThresh,maxThresh,maxProb,expWeight>] [af2-queue <weight,minThresh,maxThresh,maxProb,expWeight>] [af3-queue <weight,minThresh,maxThresh,maxProb,expWeight>] [af4-queue <weight,minThresh,maxThresh,maxProb,expWeight>] [be-queue <weight,minThresh,maxThresh,maxProb,expWeight>]

Example

set networking qos-profile iphb iphb-id 1 iphb-name iphb-1af1-queue 4,75,100,10,4


Issue: 02G DN0974301 259

3 Check the PHB profile configuration.Use the show networking qos-profile iphb command to check theconfigured PHB profile. When no parameter is given, all the profiles will be listed.The syntax is as follows:show networking qos-profile iphb [iphb-id <iphb-id>] [iphb-name <iphb-name>]

Example

show networking qos-profile iphb iphb-id 1 iphb-name iphb-1

4 Delete the PHB profile configuration.Use the delete networking qos-profile iphb command to delete PHBprofiles. If the profile is used by other element such as an IP-based route, delete thetarget element before deleting the PHB profile. The default PHB profile with ID 0cannot be deleted. The syntax of this command is as follows:delete networking qos-profile iphb iphb-id <iphb-id>

Example

delete networking qos-profile iphb iphb-id 1

User case: Configuring the PHB profile

Configure a PHB profile with the specific PHB queue parameters.

1. Create a new PHB profile by the given name and ID.add networking qos-profile iphb iphb-id 2 iphb-name iphb-2

2. Update the PHB profile.set networking qos-profile iphb iphb-id 2 iphb-name iphb-2af3-queue 4,75,100,10,4

3. Check the newly created PHB profile by the name.show networking qos-profile iphb-name iphb-2

Further information

For more information on usage of the commands and parameters, see MulticontrollerRNC SCLI Commands.

7.2.3 Configuring and showing IP-based route QoS parametersPurpose

To configure IP-based route QoS parameters.

1 Show the IP-based route QoS parameters.Use the show networking qos-profile idsp and show networking qos-profile iphb command to check the configured QoS profiles. Table 56:Parameters for show networking qos-profile idsp command and Table 57:Parameters for show networking qos-profile iphb command show the parametersused with these commands.


260 DN0974301 Issue: 02G

Table 56 Parameters for show networking qos-profile idsp command

Parameter

Description

idsp-name Optional parameter. This parameter specifies the DSCP profilename.

idsp-id Optional parameter. This parameter specifies the DSCP profileID.

Table 57 Parameters for show networking qos-profile iphb command

Parameter

Description

iphb-name Optional parameter. This parameter specifies the PHB profilename.

iphb-id Optional parameter. This parameter specifies the PHB profileID.

Example

show networking qos-profile idsp idsp-id 1 idsp-name idsp-1

show networking qos-profile iphb iphb-id 1 iphb-name iphb-1

2 Configure the IP-based route QoS parameters.Use the set networking ipbr ipbr-id <id> [phb-profile-id <id>][dspm-profile-id <id>] command to bind the DSCP and PHB profiles with theIPBR. Table 58: Parameters for set networking ipbr command lists the parametersused to set the QoS for the IP-based route with this command.

Table 58 Parameters for set networking ipbr command

Parameter

Details

ipbr-id This parameter specifies the IPBR ID.The allowed value rangeis 1 to 4095.

phb-profile-id This parameter specifies the PHB profile ID for QoS.The allowed value range is 0 to 10. The default value is 0.

dspm-profile-id This parameter specifies the DSCP to PHB mapping profileID.The allowed value range is 0 to 10. The default value is 0.

Example


Issue: 02G DN0974301 261

set networking ipbr ipbr-id 1 phb-profile-id 1 dspm-profile-id1

Set the IPBR QoS profiles to default values.

set networking 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, seeMulticontroller RNC SCLI Commands.

7.3 Configuring QoS on interface level7.3.1 Configuring ACL settings

Purpose

QoS-aware IP forwarding is implemented using the Access Control Lists (ACLs). TheACL functionality includes accepting packets, dropping packets, and marking the priorityof packets belonging to a certain packet flow. In the ACL rule table lookup, the drop andaccept rules are terminating, whereas marking rules are non-terminating. Hence, byusing multiple rules, multiple marking actions can be performed with a flow.

The platform automatically sets an ACL bypass flag for loopback and untaggedinterfaces of all internal networks. This flag is hard coded and cannot be overridden. Asof now it is not visible in the user interfaces. It protects the network element fromaccidental misconfiguration, like operators adding a drop all rule for all interfaces. Anyother rules added to internal interfaces will be ignored.

g ACL rule indexes 101 - 102, 120 - 134 are configured during mcRNC installation. Donot modify or delete these ACL rules.

1 Add a new ACL rule with associated QoS settings.A new ACL rule with associated QoS settings is created with the add networkingaclrule command. The syntax of the command, including the mandatoryparameters, 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/mask>] [srcport <port-number>] [srcportend <end-port- number>] [protocol <L4-protocol>][dstaddr <IP-address/mask>] [addr- family <IP-address-family>] [dstport <port-number>] [dstportend <endport-number>] <ACL-rule-action>

g To prevent looping of packets between the nodes, the ACL rule must be configured fordropping the packets in forward chain with VLAN (used for forwarding the externalpackets between EIPUs) as input (input-iface) and output (output-iface)interface.

Example: Adding a new ACL rule for VRF instance


262 DN0974301 Issue: 02G

Create a new ACL rule (accept packet flow) for the incoming local traffic for thedefault VRF instance of the EIPU-0 node. The index of this ACL rule is 12000. Enterthe following command:add networking aclrule /EIPU-0 chain input index 12000 vrf default accept Create a new ACL rule for the incoming local traffic for vrf1 instance of the EIPU-0node. The index of this ACL rule is 12000. Enter the following command:add networking aclrule /EIPU-0 chain input index 12000 vrf vrf1 acceptCreate a new ACL rule for the incoming local traffic for all VRF instances of theEIPU-0 node. The index of this ACL rule is 12000. Enter the following command:add networking aclrule /EIPU-0 chain input index 12000 acceptExample: Adding a new ACL ruleCreate a new ACL rule for the outgoing local traffic from the ethrtm1_1 interface ofthe EIPU-0 node, where the source IP address is 10.0.0.5. The index of this ACL ruleis 100. Enter the following command:add networking aclrule /EIPU-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 routinginstance, enter the following command:add networking aclrule /EIPU-0 index 100 chain output vrf default srcaddr 10.0.0.5 acceptExample: Adding a new ACL ruleCreate a new ACL rule for the forwarded traffic, from the ethrtm1_1 interface of theEIPU-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 /EIPU-0 index 100 input-iface ethrtm1_1 output-iface ethrtm1_2 chain forward srcaddr 10.0.0.5/32 accept Example: Adding a new ACL rule with DSCP QoS settingCreate a new ACL rule to mark the DSCP field of all the forwarded traffic, from theethrtm1_1 interface of the EIPU-0 node IP packets. The source IP address must bein the range of 10.0.0.0 to 10.0.0.255, with the desired QoS setting (EF for ExpeditedForwarding). The index of this ACL rule is 210. The DSCP value for EF packet flow is0x2e. Enter the following command:add networking aclrule /EIPU-0 index 210 input-iface ethrtm1_1 chain prerouting srcaddr 10.0.0.0/24 dscp 0x2e

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>] [input-iface <interface-name>] [output-iface <interface-name>] [chain <chain-value>] The show command displays all the rules affecting the flow, defined by the selectionof filters specified. That is, for owner, ruleid and chain parameters, the exactmatching rules are displayed. However, for input-iface and output-ifaceparameters, the exact match and rules created without interface are displayed.

Example: Displaying existing ACL rules


Issue: 02G DN0974301 263

Display a list of existing ACL rules affecting packets coming to the local Linux stackof the EIPU-0 node. Enter the following command:

show networking aclrule owner /EIPU-0 chain input

3 View runtime information for ACL rule table.To view the runtime information for existing ACL rules, enter the following command:show networking aclrule runtime [node <node>]

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

Table 59 Parameters for ACL commands

Parameter

Description

Value range

<owner> This parameter specifies theowner of the object. The value ofthe node or the RG. Thisparameter is mandatory.

-

index <ACL-rule-index>

This parameter specifies theindex (priority) value of the ACLrule to be created, deleted ordisplayed. This parameter ismandatory.

100 to 31999

chain <chain-value>

This parameter specifies wherethe filtering rules are processed.This parameter is mandatory.


• input - altering packets thatare coming to the local Linuxstack.

• output - altering packetsthat are originated from thelocal Linux stack.

• postrouting - alteringoutgoing packets afterrouting. To improve theforwarding performance thelocally originated packets inthis chain must not befiltered. The output chainmust be used instead.

• prerouting - alteringincoming packets beforerouting. To improve theforwarding performance the


264 DN0974301 Issue: 02G

Table 59 Parameters for ACL commands (Cont.)

Parameter

Description

Value range

locally terminated packets inthis chain must not befiltered. The input chainmust be used instead.

• forward- altering packetsthat are forwarded from thelocal Linux stack.

dscp <dscp_value> 6-bit DSCP sub-field of IP header.This parameter is optional.

0 to 63, 0x0 to 0x3F or 0x0 to0x3f

<ACL-rule-action> This parameter specifies the ACLrule action. This parameter ismandatory.


• accept - terminating actionto accept all packets of theflow.

• drop - terminating action todrop all packets of the flow.

• dscp-mark <DSCP> - non-terminating action to modifythe DSCP value in the Typeof Service (TOS) field of theIP packet using the <DSCP>value.

• pip-mark - nonterminatingaction to mark the packetinternal priority (PIP) usingthe <PIP> value.

input-iface <iface_name>

This parameter specifies the inputinterface selector. Any type ofinterface can be used. Thisparameter is optional.

g Use this parameter onlywith input, preroutingand forward chains.

The input-ifaceparameter cannot be usedwith the vrf parameter.

-

output-iface <iface_name>

This parameter specifies theoutput interface selector. Anytype of interface can be used.This parameter is optional.

-


Issue: 02G DN0974301 265


Parameter

Description

Value range

g Use this parameter onlywith output,postrouting andforward chains.

The output-ifaceparameter cannot be usedwith the vrf parameter.

srcaddr <IP-address>

This parameter specifies thesource IP address or range of IPaddresses selector written informat <IP-address/mask>.This parameter is optional.

srcport <port-number>

This parameter specifies thesource port number selector. Thisparameter is optional.

g Use this parameter onlywith TCP, UDP or SCTPprotocols.

The allowed value range is 0 to65535. If no value is specified,then the rule is applied to entirerange of ports.

srcportend <end-port-number>

This parameter specifies the lastsource port number. It is used todefine a range of port numberswhere the first port number in therange is srcport. Thisparameter is optional.

g Use the parameter onlywith TCP, UDP or SCTPprotocols and thesrcport parameter.

The allowed value range is 0 to65535. If no value is specified,the rule is applied to the portspecified in the srcportparameter.

vrf This parameter specifies thename of the virtual routinginstance. This parameter isoptional.

g The vrf parametercannot be used with theiface parameter.

The allowed value range is 0 to63. The name of the defaultrouting instance is default and IDis 0. The default routing instancecannot be removed.

protocol <L4-protocol>

This parameter selects the layer4 protocol to which the ACL ruleis applied. This parameter isoptional.


• tcp - the ACL rule applies toTCP traffic only.

• udp - the ACL rule applies toUDP traffic only.


266 DN0974301 Issue: 02G


Parameter

Description

Value range

• sctp - the ACL rule appliesto SCTP traffic only.

• protocol numbers - theACL rule applies to protocolnumbers (0 to 255) only.

If 0 or no value is specified, therule applies to all the protocols.

dstaddr <IP-address>

This parameter specifies thedestination IP address or range ofIP addresses selector written informat <IP-address/mask>.This parameter is optional.

-

addr-family <IP-address-family>

This parameter specifies the IPaddress family. It defines an IPaddress family to which the ACLrule without an address isapplied. This parameter isoptional.


• ipv4 - the ACL rule appliesto all IPv4 flows.

• ipv6 - the ACL rule appliesto all IPv6 flows.

The default value is ipv4.

For mcRNC only ipv4 is allowed.

dstport <port-number>

This parameter specifies thedestination port number selector.This parameter is optional.

g Use the parameter onlywith TCP, UDP or SCTPprotocols.

The allowed value range is 0 to65535. If no value is specified,the rule is applied to entire rangeof ports.

dstportend <port-number>

This parameter specifies the lastdestination port number. It is usedto define a range of port numberswhere the first port number in therange is dstport. Thisparameter is optional.

g Use the parameter onlywith TCP, UDP or SCTPprotocols and thedstport parameter.

0 to 65535. If no value isspecified, then the rule is appliedto the port specified in thedstport parameter.

<DSCP> This parameter specifies theDSCP value in the Type ofService (TOS) field of the IPpacket header.

0 to 63, 0x0 to 0x3F or 0x0 to0x3f


Issue: 02G DN0974301 267


Parameter

Description

Value range

<PIP> This parameter specifies theunique packet internal priority(PIP) value that can beassociated with a queue in aqueue set or with a layer 2 VLANpriority value.

0 to 7

node <node> This parameter specifies thenode whose runtime ACL table isdisplayed.

7.3.2 Configuring queue setsPurpose

Queues are essential if QoS-aware scheduling is to be implemented at the egressnetwork interface. When a queue set is created in the system, it is automatically filledwith six queues with default settings. The number of six queues is hard-coded andcannot be changed. The user can only modify settings of these queues or delete thewhole queue set. A default queue set, default, is created and assigned to every newinterfaces automatically. The default queue set cannot be modified or deleted.

There are two types of queues in a qset: strict priority (static) queues and weightedround robin (WRR). Scheduling behavior is different for both types. The user cannotchange 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 ispossible to modify settings of queues when the queue set is already assigned to aninterface. The changes are propagated in real time. When doing so, it is recommendedto 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 ASnode's egress queues with estimated aggregated size less then 6000 packets. Otherwiseit is not guaranteed that the packets drop according to their priority. For example, Ifaverage Ethernet frame size in your setup is 1 kB, then total aggregated queue size pernode should be less then 6 MB.

g In Multicontroller RNC there are two pre-configured queue sets: default andrncdefault. We recommend you to map queue set rncdefault to interfaces.

Do not modify or delete queue set rncdefault.

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:


268 DN0974301 Issue: 02G

Table 60 Queue set with default values

Name

Qspec

Weight

Queue length

Network Control (NC) 5 static 20k

Assured forwarding class 1 (AF1) 4 8 50k




Best Effort (BE) 0 8 100k

g New queue set created and filled with six queues with default settings. These settingscan be modified.

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-ofqueue>] [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 berepeated for each of six total queues.The parameters for this command are presented in the following table:

Table 61 Parameters for set networking qset command

Parameter

Description

Value range

queue <queue-ID> This parameter specifies the uniquequeue ID within a queue set. It isequivalent to the packet internal priority(determined by the pip-markparameter) in the ACL. A queue withhigher <queue-ID> value has higherpreference for service. The ACL mustmark packets with the internal priority forthe scheduler to be able to differentiatethe packet flows.

0 to 5

name <name-of-queue>

This parameter specifies the name ofqueue to be added.

weight <queue-weight>

This parameter specifies the queueweight. For weighted queue, the higherthe weight value, the higher the

1 to 8


Issue: 02G DN0974301 269

Table 61 Parameters for set networking qset command (Cont.)

Parameter

Description

Value range

scheduling priority. Weight of the static(strict priority) queues (number 6 and 7)may not be changed.

dropper <logical-dropper>

This parameter specifies the name ofexisting dropper object. This parameteris optional.

length <tail-drop-queue-length>

This parameter specifies the size of aqueue in bytes. A tail dropper withspecified value as a threshold is createdif it is not existing and applied to thequeue. This parameter is optional.

1024 to 1048576

Example:Creating a queue set and modifying three queues in the queue set

a) Create a queue set by entering the following command:add networking qset thisqset

b) Assign the created queue set to an interface:set networking ether /EIPU-0 iface ether1_1 outqset thisqset

c) Modify the queue 0 for Expedited Forwarding (EF) PHB packet traffic, the queue1 for Assured Forwarding (AF1) PHB packet traffic and the queue 2 for AssuredForwarding (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

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 thefollowing 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 executedand a warning message will be displayed.

Example

To de-assign the queue set from an interface enter following command:

set networking ether /EIPU-0 iface ether1_1 deloutqset


270 DN0974301 Issue: 02G

7.3.3 Configuring VLAN priority mappingsPurpose

It is also possible to differentiate packet flows in layer 2 in a VLAN, using the 3-bit PriorityCode Point (PCP) field in the VLAN tag field defined in IEEE 802.1Q. This requiresconfiguring a VLAN priority map.

After VLAN mapping is created, it must be assigned to one or more interfaces. It can beassigned to Ethernet, link aggregation or bonding interface.

Before you start

g Use transactions to bundle multiple changes into one bigger change. Use configurationlocking feature to prevent other users from interfering with your configuration changes.

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 parameters for this command are presented in the table below:

Table 62 Parameters for add networking vlanmapping command

Parameter

Description

name <name-of-map>

This parameter specifies the name of the VLAN priority mapto be created.

type <dscp|pip> This parameter indicates whether the layer 3 priority valuesare defined in terms of DSCP values or packet internalpriority (PIP) values.

mapping<mapping-values>

This parameter defines VLAN priority mapping. Selection ofthe parameter to be used in mapping is based on the valueyou give for type.In addition, the multiplicity depends on type value. ForDSCP map, maximum 64 pairs are allowed; for PIP map,maximum 8 pairs are allowed.At least one pair must be specified. You do not have tospecify all the 64 or 8 pairs.

Example: Creating a VLAN priority mapping

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


Issue: 02G DN0974301 271

Example: Modifying a VLAN priority mapping

set networking vlanmapping name testMapping mapping 29:4 mapping 60:1

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: Deleting a VLAN priority mapping

delete networking vlanmapping name testMapping


272 DN0974301 Issue: 02G

8 Configuring network monitoring

8.1 BFD configuration8.1.1 BFD protocol

Bidirectional Forwarding Detection (BFD) is a network protocol used to detect faultsbetween two hosts connected by a link. It provides low-overhead detection of faults evenon physical media that do not support failure detection of any kind, such as virtualcircuits, tunnels and MPLS Label switched paths.

The important features of BFD are:

• The protocol is independent of the data protocol being forwarded between twosystems.

• BFD packets are carried as the payload of the encapsulating protocol appropriate forthe medium and network.

• It provides failure detection on any kind of path between systems, including directphysical links, virtual circuits, tunnels, MPLS, LSPs, multihop routed paths, andunidirectional links.

• Ability to be bootstrapped by any other protocol that automatically forms peer,neighbor or adjacency relationships to provide BFD endpoint discovery.

BFD supervision can be used to monitor user plane status for Iub, Iur and Iu interfaces,when the protocol is also supported on the NE on the other end.

g Non-responding IP addresses and non-responding pathes are marked as faulty andcan’t be used for new calls.

BFD single-hop sessions can be used to track IP connectivity between directlyconnected systems. It can also be used to supplement the detection mechanisms inrouting protocols, or to monitor router-host connectivity, among other applications.

g The BFD single-hop session is not supported as a standalone feature and is integratedwith the routing daemon. For details, see Configuring static routes for IPv4.

The BFD multihop session can be used to detect faults on arbitrary paths betweensystems, which may span multiple network hops and follow unpredictable paths.

8.1.2 Configuring the BFD multihop sessionPurpose

To configure the BFD multihop session.

1 Add a BFD multihop session.The BFD multihop session can be added using the add networking monitoringbfd session command. The full syntax of the command is:add networking [instance <vrf_name>] monitoring bfd session <owner> name <name_value> srcaddr <srcaddr_value> dstaddr <dstaddr_value>


Issue: 02G DN0974301 273

[tx-interval <tx-interval>] [rx-interval <rx-interval>] [detect-mult <detect-mult>] [reference-id <reference-id>]

Example

To add the BFD multihop session for the default instance of the EIPU-0 node, enterthe following command:

add networking instance default monitoring bfd session /EIPU-0name bfd1 srcaddr 192.168.0.1 dstaddr 192.168.0.2 tx-interval100 rx-interval 100 detect-mult 6

To add the BFD multihop session with reference ID as 200, enter the followingcommand:

add networking instance default monitoring bfd session /EIPU-0name bfd2 srcaddr 192.168.0.1 dstaddr 192.168.0.2 reference-id200

2 Modify the existing BFD multihop session.The BFD multihop session can be modified using the set networkingmonitoring bfd session command. The full syntax of the command is:set networking [instance <vrf_name>] monitoring bfd session <owner> name <name_value> [tx-interval <tx-interval>] [rx-interval <rx- interval>] [detect-mult <detect-mult>] [reference-id <id>]

Example

To modify the existing multihop BFD session of the EIPU-0 node, enter the followingcommand:

set networking instance default monitoring bfd session /EIPU-0name bfd1 srcaddr 192.168.0.1 dstaddr 192.168.0.2 tx-interval200 rx-interval 200 detect-mult 4

In this example, the rx-interval and tx-interval is changed to 200 ms andthe value of detect-mult parameter is changed to 4.

To modify the reference ID of existing multihop BFD session to 210, enter thefollowing command:

set networking instance default monitoring bfd session /EIPU-0name bdf2 reference-id 210

3 Display the existing BFD multihop sessions.The BFD multihop session can be displayed using the show networkingmonitoring bfd command.To display all the BFD multihop sessions, enter the following command:show networking monitoring bfd configTo display a particular multihop BFD session, enter the following command:show networking instance <vrf_name> monitoring bfd session config [owner <node>] [name <name_value>] [dst-addr <dstaddr_value>] [srcaddr <srcaddr_value>]

Configuring network monitoring Configuring IP Connection for Multicontroller RNC

274 DN0974301 Issue: 02G

Example

To display the multihop BFD session with name bfd1, enter the following command:

show networking instance default monitoring bfd session config name bfd1


BFD sessions in default instance:

session name : bfd1 dst address : 192.168.0.2 src address : 192.168.0.1 owner : /EIPU-0 vrf name (ID) : default (0) detect mult : 4 tx interval (msec) : 200 rx interval (msec) : 200 hop type : multi reference id : 0

4 Delete the BFD multihop sessions.The BFD multihop session can be deleted using the delete networkingmonitoring bfd session command. The full syntax of the command is:delete networking [instance <vrf_name>] monitoring bfd session <owner> name <name_value>

Example

To delete a BFD multihop sessions of the EIPU-0 node, enter the followingcommand:

delete networking instance default monitoring bfd session/EIPU-0 name bfd1

Further Information

describes the parameters for the add networking monitoring bfd sessioncommand:

Table 63 Parameters for add networking monitoring bfd session command

Parameter

Description

Value range

<owner> This parameter specifies the nodeor the RG where the multihop BFDsession is added. This is amandatory parameter.

instance <vrf_name> The multihop BFD session is addedto the virtual routing instancespecified by this parameter. If theinstance parameter is not specified,

Configuring IP Connection for Multicontroller RNC Configuring network monitoring

Issue: 02G DN0974301 275

Table 63 Parameters for add networking monitoring bfd session command (Cont.)

Parameter

Description

Value range

then the BFD session is added tothe default routing instance. This isan optional parameter.

name <name_value> Specifies the unique name for thebidirectional forwarding detection(BFD) session. This is a mandatoryparameter.

The allowed value is astring of maximum 80characters that includes ato z, A to Z, 0 to 9, hyphen(-), full stop (.), orunderscore (_).

srcaddr<srcaddr_value>

This parameter specifies the sourceaddress. This is a mandatoryparameter.

dstaddr <dstaddr_value>

This parameter specifies thedestination address. This is amandatory parameter.

tx-interval <tx-interval>

This parameter specifies theminimum interval, in milliseconds,between the transmitted BFDcontrol packets that the systemuses at the current time. This is anoptional parameter.

The allowed values are inthe range from 50 ms to60000 ms with a granularityof 50 ms. The default valueis 1000 ms.

rx-interval <rx-interval>

This parameter specifies theminimum interval, in milliseconds,between the received BFD controlpackets that the system requires.This is an optional parameter.

The allowed values are inthe range from 50ms to60000 ms with a granularityof 50ms. The default valueis 1000ms.

detect-mult<detect-mult>

This parameter specifies the desireddetection time multiplier for the BFDcontrol packets on the local system.The negotiated control packettransmission interval, multiplied bythis parameter, will be the detectiontime for a particular BFD session.This is an optional parameter.

The allowed values are inthe range 1 to 50. Thedefault value is 4.

reference-id<reference-id>

Specifies the reference ID for theBFD session. Reference ID is anapplication specific identifierassociated with the BFD session.This ID has no significance for BFD,but is included in BFD's systeminternal notifications and BFDalarms when BFD state changes.This is an optional parameter.

0 to 65535. The defaultvalue is 0.


276 DN0974301 Issue: 02G

Table 63 Parameters for add networking monitoring bfd session command (Cont.)

Parameter

Description

Value range

g When the BFD session isused to moniter IPROconnection status, give thesame value forreference-id here andipbr-id for the IP-basedroute. Then the value rangeis 1 to 4095.

8.1.3 Displaying the runtime information for the multihop BFDsessionPurpose

To show the runtime information for the multihop BFD sessions.

1 Display the runtime information for the multihop BFD session.To display the runtime information for the multihop BFD session, enter the followingcommand:show networking [instance <vrf_name>] monitoring bfd runtime [node <node-name>] [name <name_value>] [src-addr <srcaddr_value>] [dst-addr <dstaddr_value>] [state <Down|Up>]The following table describes the parameters for the show networkingmonitoring bfd runtime command:

Table 64 Parameters for the show networking monitoring bfd runtimecommand

Parameter

Description

instance <vrf_name> Displays the runtime information for the multihopBFD session with the specified instance, forexample, vrf1.

node <node-name> Specifies the node of the session. This can bespecified to filter the runtime statistics of thesession based on the specified node or RG.

name <name_value> Specifies the name of the session. This can beused to filter the runtime statistics of the sessionsbased on the specified name.

src-addr<srcaddr_value>

Specifies the source address of the session. Thiscan be used to filter the sessions based on thespecified source address.


Issue: 02G DN0974301 277

Table 64 Parameters for the show networking monitoring bfd runtimecommand (Cont.)

Parameter

Description

dst-addr<dstaddr_value>

Specifies the destination address of the session.This can be used to filter the runtime statistics ofthe sessions based on the specified destinationaddress.

state <Down|Up> Specifies the state of the session. This can bespecified to filter the runtime statistics of thesessions based on the specified session state.

Example: Displaying the runtime information for BFD sessions added to EIPU-0node

To display the runtime information the multihop BFD session bfd1 on the EIPU-0 node,enter the following command:

show networking instance default monitoring bfd runtime node EIPU-0 name bfd1


Vrf: default (0) Session name: bfd1 Diagnostic: No DiagnosticState:Up Reference Id: 100Source address : 10.29.58.10Destination address : 10.29.58.9

8.2 ICMP Configuration8.2.1 Internet control message protocol functionality

ICMP monitoring mechanism provides the bidirectional forwarding detection (BFD) typeforwarding path supervision and provides fast detection of forwarding path failuresbetween session endpoints.

ICMP monitoring sessions are asymmetric; therefore, no special configuration is requiredin the remote endpoint. ICMP request reply is used to check the ICMP monitoringsession states. ICMP based supervision can be used to monitor user plane status for Iurand Iu interfaces, when the protocol is also supported on the peer NE.

g Non-responding IP addresses and non-responding pathes are marked as faulty andcan’t be used for new calls.

8.2.2 Configuring internet control message protocol monitoringsessionPurpose

To configure an ICMP monitoring session.


278 DN0974301 Issue: 02G

1 Add an ICMP monitoring session.To add a ICMP monitoring session, enter the following command:add networking [instance <vrf_name>] monitoring icmp session <owner> name <name_value> dstaddr <dstaddr_address> srcaddr <srcaddr_address> [payload <payload>] [rx-timeout <rx-timeout>] [tx-interval <tx- interval>] [max-lost-packets <max-lost-packets>] [reference-id <reference-id>]Example:To add a monitoring ICMP session to /EIPU-0 node, enter the following command:add networking monitoring icmp session /EIPU-0 name abc srcaddr 10.0.0.1 dstaddr 10.0.0.2 tx-interval 200 max-lost-packets 10

2 Modify the ICMP monitoring session.To modify the ICMP monitoring session, enter the following command:set networking instance <vrf_name> monitoring icmp session <owner> name <name_value> [rx-timeout <rx-timeout>] [tx-interval <tx- interval>] [payload <payload>] [max-lost-packets <max-lost-packets>] [reference-id <reference-id>]ExampleTo modify ICMP monitoring session on /EIPU-0 node, enter the followingcommand:set networking monitoring icmp session /EIPU-0 name abcreference-id 10

3 View ICMP monitoring sessions.To view the ICMP monitoring sessions for a specific routing instance, enter thefollowing command:show networking [instance <vrf_name>] monitoring icmp session config [owner <owner_value>] [name <name_value>] [src-addr <srcaddr_value>] [dst-addr <dstaddr_value>]To view all the ICMP monitoring sessions, enter the following command:show networking monitoring icmp configTo view the ICMP monitoring runtime information, enter the following command:show networking [instance <vrf_name>] monitoring icmp runtime [node <node_name>] [name <name_value>] [src-addr <srcaddr_value>] [dst-addr <dstaddr_value>] [state <down|up>]Example:To view all the ICMP monitoring information, enter the following command:show networking monitoring icmp configThe following output is displayed:ICMP connectivity monitoring sessions in default instance

session name : abc dst address : 10.0.0.2 src address : 10.0.0.1 owner : /EIPU-0 vrf name (ID) : default (0) tx interval (msec) : 200


Issue: 02G DN0974301 279

rx timeout (msec) : 500 max lost packets : 10 packet payload : 64 reference id : 10To view the ICMP monitoring runtime information on the default VRF, enter thefollowing command:show networking instance default monitoring icmp session config owner /EIPU-0 To view the ICMP monitoring runtime information, enter the following commandshow networking instance default monitoring icmp runtime node EIPU-0 name abcThe following output is displayed:ICMP monitoring sessions on node: EIPU-0

Vrf name (ID): default (0) Session name: abc State: Down Reference Id: 0Source Address : 10.0.0.1Destination Address : 10.0.0.2

4 Delete the ICMP monitoring session.To delete an ICMP monitoring session on a specified node, enter the followingcommand:delete networking [instance <vrf_name>] monitoring icmp session <owner> name <name_value>Example:To delete the ICMP monitoring session named abc, enter the following command:delete networking monitoring icmp session /EIPU-0 name abc

Further information

Table 65: Parameters for the networking monitoring icmp commands describes theparameters for the ICMP configuration commands:

Table 65 Parameters for the networking monitoring icmp commands

Parameter

Description

instance <vrf_name> This parameter specifies the name of the VRF.

<owner> This parameter specifies the name of the node or recoverygroup.

name <name_value> This parameter specifies the unique name for the ICMPsession. It can be a string of maximum 80 characters thatincludes a to z, A to Z, 0 to 9, hyphen (-), full stop (.), orunderscore (_).

dstaddr<dstaddr_address>

This parameter specifies the destination address.


280 DN0974301 Issue: 02G

Table 65 Parameters for the networking monitoring icmp commands (Cont.)

Parameter

Description

srcaddr<srcaddr_address>

This parameter specifies the source address.

rx-timeout <rx-timeout>

This parameter specifies the echo reply timeout inmilliseconds. It is the timeout on waiting for an ICMP echoreply.

The value ranges from 100 to 600000 milliseconds. Bydefault, the value is 500 ms. Granularity is 50 ms.

tx-interval <tx-interval>

This parameter specifies the desired minimum transmitinterval in milliseconds. It is the interval between transmittedICMP echo request messages.

The value ranges from 150 to 600000 milliseconds. Bydefault, the value is 1000 ms. Granularity is 50 ms.

max-lost-packets <max-lost-packets>

This parameter specifies the maximum number of missingICMP echo reply packets. Session runtime state goes downwhen the maximum number of lost packets are exceeded.

The value ranges from 1 to 255. By default, the value is 5.

payload <payload> This parameter specifies the packet payload size. It is thesize of the payload in the transmitted ICMP echo requestpackets.

The value ranges from 0 to 128. By default, the value is 64.

reference-id<reference-id>

This parameter specifies the reference ID for the ICMPmonitoring session. It is an application specific identifierassociated with the ICMP monitoring session. This ID has nosignificance for ICMP monitoring session, but is included inthe system internal notifications and ICMP monitoringsession alarms when ICMP monitoring session statechanges.

The value ranges from 0 to 65535. By default the value is 0.

8.3 Link state detector configuration8.3.1 Link state detector functionality

Link state detector is a resource controller process that can be included under therecovery units of Application/Platform recovery group. Link state detector monitors themonitoring resources (that is; interfaces (physical and logical), nexthops, interfacegroups, and nexthop groups) and informs HAS to perform corrective action wheneverthey go down.


Issue: 02G DN0974301 281

g The monitoring group added to link state detector acts as a logical resource. HASperforms switchover only when the last available resource (interface or nexthop) in thegroup goes down.

Example:

If link state detector has to monitor resouces associated with the /ClusterDNSrecovery group, it must be added as a process under the recovery unit of the/ClusterDNS recovery group.

g Link state detector must be added as a process under the recovery unit as part ofdeployment before the commissioning.

To verify that link state detector is added as a process under the recovery unit, enter thefollowing commands:

show has view managed-object /CLA-0/FSClusterDNSServer

For the recovery groups having link state detector as a resource controller process, twoadditional attributes called RESOURCE_STATE and RESOURCE_LEVEL are displayed.

If any of the monitoring resources are up in both; the active and the standby nodes, thenthe RESOURCE_STATE field is set to FUNCTIONAL.

If all the monitoring resources go down in the active node, the RESOURCE_STATE is setto NON-FUNCTIONAL and the node is changed to SE-OU state.

If all the monitoring resources comes up in the current standby node and go down in thecurrent active node, the RESOURCE-STATE field is set to NON-FUNCTIONAL in the activenode and switchover happens. Then, the current standby node becomes active again.

g For /SSH, /ClusterNTP, and /ClusterDNS recovery groups, RESOURCE_STATE isnot set to NON-FUNCTIONAL when the monitoring resources go down.

The RESOURCE_LEVEL attribute is used to determine which of the recovery units of anactive-standby recovery group will be active. Whenever the recovery unit’s resource levelis higher than that of its peer, the recovery group becomes active on the node.

To determine the additional attributes, enter the following command:

show has state managed-object /CLA-*/FSClusterDNSServer

The following is displayed:

OBJECT ADMINISTRATIVE OPERATIONAL USAGE ROLE /CLA-0/FSClusterDNSServer UNLOCKED ENABLED IDLE COLDSTANDBY /CLA-1/FSClusterDNSServer UNLOCKED ENABLED ACTIVE ACTIVE

PROCEDURAL DYNAMICNOTINITIALIZED RESOURCE_STATE=FUNCTIONAL RESOURCE_LEVEL=100 - RESOURCE_STATE=FUNCTIONAL RESOURCE_LEVEL=100


282 DN0974301 Issue: 02G

g When link state detector is configured to monitor OSPF routes (with BFD monitoringenabled), the following throttling parameters need to be enabled for faster switchovers.

• calc-max-delay

• calc-start-threshold

• calc-restart-threshold

To enable the throttling parameters, enter the following command:

set routing ospf2 calc-max-delay 0 set routing ospf2 calc-start-threshold 0 set routing ospf2 calc-restart-threshold 10

For more information on OSPF routes, see Network Configuration guide.

8.3.2 Configuring a monitoring group/interface/nexthop formonitoringPurpose

To configure a monitoring group, interface or nexthop for monitoring.

1 Add a monitoring group/interface/nexthop for monitoring.To create a monitoring group with interface(s), enter the following command:add networking [instance <vrf_name>] link-state-detector monitoring- group <owner> iface-mon-group <iface-group-name> iface <interface>...To create a monitoring group with nexthop(s), enter the following command:add networking [instance <vrf_name>] link-state-detector monitoring- group <owner> nexthop-mon-group <nexthop-group-name> nexthop <nexthop>...To add a monitoring group/interface/nexthop for monitoring, enter the followingcommand:add networking [instance <vrf_name>] link-state-detector <owner> [unit <node_name>] [iface <interface>...] [iface-mon-group <iface- group-name>] [nexthop <nexthop>...] [nexthop-mon-group <nexthop- group-name>]

g • When creating a group using the add command, make sure at least one resource isadded to the group.

• When adding an recovery group (RG) for monitoring using the add command, makesure at least one resource (interface, nexthop, or monitoring group) exists underthat RG for monitoring.

Example:To create monitoring groups with interfaces, enter the following commands:add networking instance default link-state-detector monitoring-group /ClusterDNS iface-mon-group ifgrp iface ethsfp10add networking instance default link-state-detector monitoring-group /ClusterDNS iface-mon-group ifgrp1 iface ethsfp11


Issue: 02G DN0974301 283

To create monitoring group with nexthops, enter the following commands:add networking instance default link-state-detector monitoring-group /ClusterDNS nexthop-mon-group nhgrp nexthop 10.102.233.1add networking instance default link-state-detector monitoring-group /ClusterDNS nexthop-mon-group nhgrp1 nexthop 10.102.233.2To add an interface/nexthop/group for monitoring to a recovery group, enter thefollowing command:add networking instance default link-state-detector /ClusterDNS iface-mon-group ifgrp nexthop-mon-group nhgrp iface eth0 nexthop 1.1.1.1To monitor interface eth0 on CFPU-0 node, enter the following command:add networking link-state-detector /ClusterNTP unit CFPU-0 iface eth0

2 Modify a monitoring group/interface/nexthop which is being monitored.To modify a monitoring group with interface(s), enter the following command:set networking [instance <vrf_name>] link-state-detector monitoring- group <owner> iface-mon-group <iface-group-name> add-iface <interface> del-iface <interface> To modify a monitoring group with nexthop(s), enter the following command:set networking [instance <vrf_name>] link-state-detector monitoring- group <owner> nexthop-mon-group <nexthop-group-name> add-nexthop <nexthop> del-nexthop <nexthop>To modify link state detection on a recovery group (RG), enter the followingcommand:set networking [instance <vrf_name>] link-state-detector <owner> [unit <node_name>] [add-iface-mon-group <iface-group-name>] [del- iface-mon-group <iface-group-name>] [add-iface <interface>] [del- iface <interface>] [add-nexthop-mon-group <nexthop-group-name>] [del- nexthop-mon-group <nexthop-group-name>] [add-nexthop <nexthop>] [del- nexthop <nexthop>]

g • When modifying monitoring group using the set command, make sure at least oneresource (interface or nexthop) exists under that group.

• When modifying monitoring information of an recovery group (RG) using the setcommand, make sure at least one resource (interface, nexthop, or monitoringgroup) exists under that RG for monitoring.

ExampleTo modify an interface(s) of a monitoring group, enter the following command:set networking instance default link-state-detector monitoring-group /ClusterDNS iface-mon-group ifgrp add-iface ethsfp12 del-iface ethsfp10To modify a nexthop(s) of a monitoring group, enter the following command:set networking instance default link-state-detector monitoring-group /ClusterDNS nexthop-mon-group nhgrp add-nexthop 10.102.233.3 del- nexthop 10.102.233.1To modify monitoring of a recovery group (RG), enter the following command:set networking instance default link-state-detector /ClusterDNS unit CFPU-0 add-iface-mon-group ifgrp1 del-iface-mon-group ifgrp add- nexthop-mon-group nhgrp1 del-nexthop-mon-group nhgrp


284 DN0974301 Issue: 02G

3 View monitoring information of an interface/nexthop group.To view an interface/nexthop group information, enter the following command:show networking link-state-detector [monitoring-group] <owner> [iface-mon-group <iface-group-name>] [nexthop-mon-group <nexthop- group-name>]Example:To view a nexthop(s) group information, enter the following command:show networking link-state-detector monitoring-group /ClusterDNS nexthop-mon-group nhgrpThe following output is displayed:Nexthop Group: nhgrp Owner : /ClusterDNS Vrf : 0 nexthop : 10.102.233.3

g VRF is relevant only for nexthop monitoring and not for interface monitoring. Henceshow command displays VRF information only for nexthops.

To view interface(s) group information, enter the following command:show networking link-state-detector monitoring-group /ClusterDNS iface-mon-group ifgrpThe following output is displayed:Iface Group: ifgrp Owner : /ClusterDNS iface : ethsfp12To view monitoring information of a recovery group (RG), enter the followingcommand:show networking link-state-detector /ClusterDNSThe following output is displayed:/ClusterDNS iface : eth3@CFPU-0 xthop : 1.1.1.1@0@CFPU-0 ifacegroup : ifgrp1@CFPU-0 iface : ethsfp11 nexthopgroup : nhgrp1@0@CFPU-0 nexthop : 10.102.233.2

4 Disable monitoring of an interface/nexthop monitoring group.To disable link state detection on a recovery group (RG), enter the followingcommand:delete networking link-state-detector <owner>To delete an interface/nexthop monitoring group, enter the following command:set networking [instance <vrf_name>] link-state-detector <owner> [del-iface-mon-group <iface-group-name>] [del-nexthop-mon-group <nexthop-group-name>]Example:


Issue: 02G DN0974301 285

To disable monitoring of an interface monitoring group, enter the followingcommands:set networking instance default link-state-detector /ClusterDNS del- iface-mon-group ifgrpTo disable monitoring of a nexthop monitoring group, enter the following commands:set networking instance default link-state-detector /ClusterDNS del- nexthop-mon-group nhgrpTo disable link state detection on a recovery group (RG), enter the followingcommanddelete networking link-state-detector /ClusterDNS

Further information

The following table describes the parameters for the link state detector commands.

Table 66 Parameters for the networking link-state-detector commands

Parameter

Description

instance <vrf_name> This parameter specifies the name of the VRF. This is anoptional parameter.

g VRF is relevant only for nexthop monitoring and not forinterface monitoring.

monitoring-group This parameter modifies a monitoring group.

<owner> This parameter specifies the recovery group (RG) having linkstate detector deployed as a resource controller process.

iface-mon-group<iface-group-name>

This parameter specifies the interface group name. It is createdto monitor a group of interfaces together. The switchover of linkstate detection happens only when all the interfaces in thegroup are not reachable.

iface <interface> This parameter specifies the interface that is added to theinterface monitoring group when added along with theparameter iface-mon-group, else it specifies the interfaceon which link state detection has to be enabled.

nexthop-mon-group<nexthop-group-name>

This parameter specifies the nexthop group name. It is createdto monitor a group of nexthops together. The group acts as alogical resource. The switchover of link state detection happensonly when all the nexthops in the group are not reachable.

nexthop <nexthop> This parameter specifies the nexthop to be added to thenexthop monitoring group when added along with theparameter nexthop-mon-group, else it specifies the nexthopon which link state detection has to be enabled.

unit <node_name> This parameter specifies the node name having link statedetector deployed as a resource controller process.


286 DN0974301 Issue: 02G

Table 66 Parameters for the networking link-state-detector commands(Cont.)

Parameter

Description

g It is used to monitor a monitoring resource present onlyon a node; for example, to monitor the interface eth0present only on the CFPU-0 node.

add-iface-mon-group<iface-group-name>

This parameter specifies the interface group on which link statedetection has to be enabled.

add-iface <interface> This parameter specifies the interface that is added to theinterface monitoring group when added along with theparameter add-iface-mon-group, else it specifies theinterface on which link state detection has to be enabled.

del-iface-mon-group<iface-group-name>

This parameter specifies the interface group on which link statedetection has to be disabled.

del-iface <interface> This parameter specifies the interface to be removed from theinterface monitoring group when added along with theparameter del-iface-mon-group, else it specifies theinterface on which link state detection has to be disabled.

add-nexthop-mon-group<nexthop-group-name>

This parameter specifies the nexthop group on which link statedetection has to be enabled.

add-nexthop <nexthop> This parameter specifies the nexthop to be added to thenexthop monitoring group when added along with theparameter add-nexthop-mon-group, else it specifies thenexthop on which link state detection has to be enabled.

del-nexthop-mon-group<nexthop-group-name>

This parameter specifies the nexthop group on which link statedetection has to be disabled.

del-nexthop <nexthop> This parameter specifies the nexthop to be removed from thenexthop monitoring group when added along with theparameter del-nexthop-mon-group, else it specifies thenexthop on which link state detection has to be disabled.

8.4 Configuring TWAMP measurement8.4.1 Configuring TWAMP initiator

Purpose

Two-way Active Measurement Protocol (TWAMP) can be used to measure andsupervise the IP network conditions through the mobile backhaul between two networkelements. This chapter introduces how to configure TWAMP initiator (sender) session onthe mcRNC.


Issue: 02G DN0974301 287

1 Create TWAMP measurement initiator session.Use the add networking monitoring twamp sender command to addTWAMP measurement initiator information on the mcRNC. The syntax of thecommand is as follows:add networking monitoring twamp sender <owner> session-id <id>dest-ip-addr <IP address> [port <value>] src-ip-addr <IPaddress> [dscp <value>] [packet-length <value>] [packet-frequency <value>] [rtt-threshold <value>] [plr-threshold<value>] [session-state <on|off>] [vrf <name>]

2 Check the IP TWAMP measurement sender information.Use the show networking monitoring twamp sender command to view theIP TWAMP measurement sender information.The full syntax of the command is as follows:show networking monitoring twamp sender [owner <name>][session-id <id>] [session-state <on|off>] [vrf <name>]

3 Change the IP TWAMP measurement sender session information.Use the set networking monitoring twamp sender command to change theIP TWAMP measurement sender session information.The full syntax of the command is as follows:set networking monitoring twamp sender [<owner>] session-id<id> [dest-ip-addr <IP address>] [port <value>] [src-ip-addr<IP address>] [dscp <value>] [packet-length <value>] [packet-frequency <value>] [rtt-threshold <value>] [plr-threshold<value>] [session-state <on|off>] [vrf <name>]

g You can set value for parameters dest-ip-addr, src-ip-addr and port only whenthe TWAMP session state is off. Use commandshow networking monitoring twamp sender session-id <id> to check thesession state.

4 Delete the IP TWAMP measurement sender session.Use the delete networking monitoring twamp sender command to deletethe IP TWAMP measurement sender session.The full syntax of the command is as follows:delete networking monitoring twamp sender session-id <id>

Further information

Detailed explanations of the parameters are listed in the following table:


288 DN0974301 Issue: 02G

Table 67 Parameters for networking monitoring twamp sender commands

Parameter

Description

Value Range

<owner> This parameter specifies the name of themanaged object of the TWAMP sender.This pamater can be a node, a recoverygroup, a recovery unit or a process.

session-id <id> This parameter specifies the identifiernumber of the TWAMP sender session.Up to 100 sessions with session statecan be created on one owner.

Range: 1 to 4095

dest-ip-addr <IPaddress>

This parameter specifies the destinationIP address for the TWAMP session.

port <value> This parameter specifies the destinationport number of the TWAMP session. TheUDP echo server or TWAMP reflector isexpected to respond from the definedport.

Range: 1 to 65535

Default: 7

src-ip-addr <IPaddress>

This parameter specifies the source IPaddress for the TWAMP session.

dscp <value> This parameter specifies the differentialservice code point (DSCP) value for thetest traffic.

Range: 0 to 63

Default: 34

packet-length<value>

This parameter specifies the length oftest packet on the IP layer.

g The measurement packets shallnot be fragmented on their waythrough the network. Thereforethe length of the test packetcannot exceed the minimum MTUwithin the network.

Range: 69 to 1500 bytes

Default: 100 bytes

packet-frequency<value>

This parameter specifies the number ofTWAMP messages sent out per second.

Range: 1 or 10

Default: 1

plr-threshold<value>

This parameter specifies the packet lossratio (PLR) alarm threshold.

If this threshold is exceeded, a PLRalarm will be set.

Range: 0.00% to100.00%

Step: 0.01%

Default: 100.00%

rtt-threshold<value>

This parameter specifies the Round TripTime (RTT) alarm threshold.

If this threshold is exceeded, an RTTalarm will be set.

Range: 0 to 1000 ms

Default: 1000 ms


Issue: 02G DN0974301 289

Table 67 Parameters for networking monitoring twamp sender commands (Cont.)

Parameter

Description

Value Range

session-state<on|off>

This parameter specifies the initialsession state of the TWAMP session.

The allowed values areon and off. The defaultvalue is off.

When the value is on, theIP network test packet issent out immediately.

vrf <name> This parameter specifies the name for aspecific virtual routing instance.

The allowed values are ato z, A to Z, 0 to 9, and _characters (lower case,upper case, numeric andunderscore). Themaximum length of aname is 15 charactersand the minimum lengthis 1 character.

8.4.2 Configuring TWAMP reflectorPurpose

This chapter introduces how to configure TWAMP reflector session on the mcRNC.

1 Create TWAMP measurement reflector session.Use the add networking monitoring twamp reflector command to addTWAMP measurement reflector session on the mcRNC. The syntax of the commandis as follows:add networking monitoring twamp reflector <owner> session-id<id>

2 Check the IP TWAMP measurement reflector information.Use the show networking monitoring twamp reflector command to viewthe IP TWAMP measurement reflector information.The full syntax of the command is as follows:show networking monitoring twamp reflector [session-id <id>]

3 Delete the IP TWAMP measurement reflector session.Use the delete networking monitoring twamp reflector command todelete the IP TWAMP measurement reflector session.The full syntax of the command is as follows:delete networking monitoring twamp reflector session-id <id>

Further information


290 DN0974301 Issue: 02G

Detailed explanations of the parameters are listed in the following table:

Table 68 Parameters for networking monitoring twamp reflector commands

Parameter

Description

Value Range

<owner> This parameter specifies the name of themanaged object of the TWAMP reflector.This pamater can be a node, a recoverygroup, a recovery unit or a process.

session-id <id> This parameter specifies the identifiernumber of the TWAMP reflector session.Up to 100 sessions with session statecan be created on one owner.

Range: 1 to 4095


Issue: 02G DN0974301 291

9 Configuring NTPPurpose

The Network Time Protocol (NTP) is used for synchronizing the internal time of thecluster to an external reference time source, and its use is strongly recommended. Forredundancy, up to three external NTP servers can be used by the system. NTP providesaccuracy within a millisecond in a local area network (LAN) and up to a few tens ofmilliseconds in a wide area network (WAN).

The NTP daemon running in a client or server makes statistical calculations from theincoming time stamps. The accuracy of the time improves the longer the daemon isrunning. Clocks in the network make an abrupt jump to the correct time only during timeinitialization (if the time difference is greater than 1000 seconds). Otherwise, clients orservers maintain their correct time on a continuous basis by requesting time stamps froma common NTP server at regular intervals.

The accuracy of the NTP server is indicated by a stratum number. The primary servers

(stratum 1) are synchronized directly to coordinated universal time (UTC) by radio,satellite, or modem. The secondary servers (stratum 2) are synchronized to the primaryservers. The secondary servers are usually located in an operator's or Internet serviceprovider's network.

The system automatically selects the best time source from the network of NTP serversand automatically adjusts the polling rate, that is, how often the time stamp is requested.The minimum polling interval is 16 seconds and the maximum polling interval is 1024seconds.

In a single node deployment NTP is only used to guarantee the accuracy of the timestamps in the logs, alarms and reports generated by the platform. If there are no externalservers defined, the system uses the time information stored in the internal hardwareclock.

1 Check the current NTP configuration.To see the current NTP configuration, enter the following command:show networking-service ntpIf the NTP addresses are not added, there will be no printout.

2 Option Description

If an NTP configuration exists in the system

Then Delete the current NTP configuration.

To be able to add a new NTP configuration, the current configurationmust be deleted first. Delete the current NTP configuration by enteringthe following command:

delete networking-service ntp


292 DN0974301 Issue: 02G

3 Assign the addresses of external NTP servers to the system.Use the add networking-service ntp command to assign the IP addresses ofthe external NTP servers (forwarders) to the system. Up to three external NTPservers can be assigned.The syntax of the command is as follows:add networking-service ntp forwarder <IP address or host name of an external NTP server>

4 Modify the NTP configuration.To modify the current NTP configuration, enter the following command:set networking-service ntp [add-forwarder <IP address or host name of an external NTP server>] [delete-forwarder <IP address or host name of an external NTP server>]

5 Verify the NTP configuration.To see the current NTP configuration, enter the following command:show networking-service ntp

Example:

1. Assign IPv4 addresses 10.20.30.40 and 10.20.30.50 of external NTP serversby entering the following command:add networking-service ntp forwarder 10.20.30.40 forwarder 10.20.30.50

2. Verify that the configuration was assigned correctly. Enter the following command:show networking-service ntpThe printout in this example is as follows:forwarder: 10.20.30.40forwarder: 10.20.30.50

Further information

Parameters for NTP configuration shows the parameters for networking-servicedns commands:

Table 69 Parameters for NTP configuration

Parameter

Description

Value Range

forwarder <address> The IP address or the hostname of the external NTPserver.

Up to three external NTPservers can be assigned tothe system.

add-forwarder <IPaddress or host nameof an external NTPserver>

This parameter adds the IPaddress or the host name of anexternal DNS server.

Configuring IP Connection for Multicontroller RNC Configuring NTP

Issue: 02G DN0974301 293

configuring_ip_connection_for_flexi_direct_rnc.pdf

Table 69 Parameters for NTP configuration (Cont.)

Parameter

Description

Value Range

delete-forwarder <IPaddress or host nameof an external NTPserver>

This parameter removes the IPaddress or the host name of anexternal DNS server.

Configuring NTP Configuring IP Connection for Multicontroller RNC

294 DN0974301 Issue: 02G

10 Configuring DNSPurpose

The domain name system (DNS) is a distributed database that offers, among others,mapping between IP addresses and domain names (host names). The DNSinfrastructure consists of DNS servers (also called name servers) and DNS clients (alsocalled resolvers) with the main task of querying information from DNS servers.

DNS servers are organized in a hierarchical structure consisting of master DNS serversand forwarding DNS servers. Master DNS servers contain the zone information innonvolatile memory. A zone is a subset of the DNS namespace that is managed by aspecific DNS server. A master DNS server that contains the complete information foraparticular zone is called the authoritative DNS server for that zone.

Forwarding DNS servers load the zone information from a DNS server higher up in thehierarchy (either a master server or another forwarding server). This replicationprocessis called zone transfer.

Every host in any IP network is equipped with a resolver, a DNS client that is able toretrieve information from a DNS server. An application that needs to find a mappingbetween a domain name and an IP address uses the resolver to query an appropriateDNS server. Besides sending queries to DNS servers, resolvers also interpret theresponses received from the DNS servers before returning the results to theapplications.

In the simplest form the domain name system (DNS) is configured by assigning the IPaddress(es) of the external DNS server(s) to the system. For redundancy, one to threeexternal DNS servers can be used by the system.

1 Check the current DNS configuration.To check the current DNS configuration, enter the following command:show networking-service dnsIf the DNS addresses are not added, there is no printout.

2 Option Description

If a DNS configuration exists in the system

Then Delete the current DNS configuration.

To add a new DNS configuration, the current configuration must bedeleted first. Delete the current DNS configuration by entering thefollowing command:

delete networking-service dns

3 Assign the addresses of external DNS servers to the system.Use the add networking-service dns command to assign the IP addresses ofthe external DNS servers (forwarders) to the system. The syntax of the command isas follows:add networking-service dns forwarder <forwarder_address>

Configuring IP Connection for Multicontroller RNC Configuring NTP

Issue: 02G DN0974301 295

4 Modify the DNS configuration.To modify the current DNS configuration, enter the following command:set networking-service dns [add-forwarder <forwarder_address>] [delete-forwarder <forwarder_address>]

5 Verify the DNS configuration.To see the current DNS configuration, enter the following command:show networking-service dns

Example:

Assign the addresses 10.20.30.41 and 10.20.30.51 for external DNS servers byentering the following command:

add networking-service dns forwarder 10.20.30.41 forwarder 10.20.30.51

Verify that the configuration is assigned correctly. Enter the following command:

show networking-service dns

Example:

Assign the address 10.20.30.61 and remove the address 10.20.30.51 of externalDNS servers by entering the following command:

set networking-service dns add-forwarder 10.20.30.61 delete-forwarder 10.20.30.51

Verify that the configuration is assigned correctly. Enter the following command:

show networking-service dns

Further information

Table 70 Parameters for DNS configuration

Parameter

Description

Value Range

forwarder <address> The IP address of the externalDNS server.

Forwarder is one of the DNSservers that loads the zoneinformation from a DNS serverhigher up in the hierarchy(either a master server oranother forwarding server).

Up to three external DNSservers can be assigned tothe system.

add-forwarder<forwarder_address>

This parameter adds an IPaddress of an external DNSserver.

Configuring DNS Configuring IP Connection for Multicontroller RNC

296 DN0974301 Issue: 02G

Table 70 Parameters for DNS configuration (Cont.)

Parameter

Description

Value Range

delete-forwarder<forwarder_address>

This parameter removes an IPaddress of an external DNSserver.

Configuring IP Connection for Multicontroller RNC Configuring DNS

Issue: 02G DN0974301 297

11 Troubleshooting

11.1 Connection to the application RG from remote hostfailsDescription

If you cannot reach an application RG from the remote host, the possible reasonsinclude:

• 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 proceduresCheck the IP-layer Communication

Steps

1 Check the connection.Use the ping command from the remote workstation or node to check theconnection.

a) Use the shell bash full command.b) 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.

Exampleshow 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

Configuring DNS Configuring IP Connection for Multicontroller RNC

298 DN0974301 Issue: 02G

3 If dynamic routes defined in the network element are configured, check theOSPF routing settings.a) Check OSPF configuration.

show routing node <node_name> ospf configb) Check OSPF interface configuration.

show routing node <node_name> ospf interface <interfacename>

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.

4 If static routes are configured, check the static route settings.show routing node <node name> static-route configFor instructions on configuring static route, see Configuring static routes for IPv4.

5 Check the connected network interface.Check the administrative and operational state of the connected network interface.

a) Check the network interface.show networking ether owner <owner_name> iface <iface_name>In the printout, the administrative state should be up and the IPv4 forwardingshould be yes.

b) Check the network interface running status.show networking interface runtime node <node_name> iface<iface_name>

11.2 mcRNC connectivity failsDescription

The redundant configuration requires that the two BCN boxes must be connected via theSFP+ ports. The connectivity lost will cause call drop. The reasons for connectivity lostcan 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 betweenBCNs.

The fault may be either with the cabling or with the network configuration.

Configuring IP Connection for Multicontroller RNC Troubleshooting

Issue: 02G DN0974301 299

In case of faulty cabling, when an Ethernet link fails, the system sets the Ethernetinterface to "Not running" state and raises an alarm.

If no alarm is raised, the failure may be due to the network configuration.

Recovery proceduresSteps

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 alarmdescription 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 aproblem in Ethernet interface, check the cabling.

2 Check the cabling.Check whether the cables are well connected.

3 If the cabling is correct, check the routing configuration of the EIPUs.Before you startThe internal IP configuration is pre-defined for mcRNC. However, you can still checkthe configuration. If you find something wrong with the internal IP addresses orroutes, please contact NSN Technical Support group.Steps

a) Check the application IP addresses used by mcRNC, such as the address for Iu-PS, Iu-CS and Iur. Use the following command.show networking iproFor more instructions on associating the IP addresses to the certain IP-basedroute, see Configuring IP based-route.

b) Check the routing configuration on the node.show routing node <node name> route

Troubleshooting Configuring IP Connection for Multicontroller RNC

300 DN0974301 Issue: 02G

configuring_ip_connection_for_mcrnc.pdf

Documents

Transcript of configuring_ip_connection_for_mcrnc.pdf