76XX

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

Configuring RNC IP site solution based on Cisco 76xx routers

DN70664131

Issue 01CApproval Date 2009-11-05

Confidential

2 DN70664131Issue 01C

Configuring RNC IP site solution based on Cisco 76xxrouters

Id:0900d80580646965Confidential

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

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

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

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

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

Copyright © Nokia Siemens Networks 2009. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN70664131Issue 01C

3



Table of contentsThis document has 23 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Solution based on Cisco 76xx series routers. . . . . . . . . . . . . . . . . . . . . . 9

2 RNC IP site solution based on Cisco 76xx routers . . . . . . . . . . . . . . . . 102.1 Co-located equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1.1 Symmetricom TP5000 equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1.2 Site support equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1.3 Co-located network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Physical configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2.1 Physical Ethernet interface configuration. . . . . . . . . . . . . . . . . . . . . . . . 102.2.2 Ethernet cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2.3 Ethernet cable types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2.4 Ethernet link connectivity for protected NP2GE units . . . . . . . . . . . . . . 112.3 Ethernet configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.1 Ethernet interface configuration in RNC and site routers. . . . . . . . . . . . 112.3.2 VLAN configuration in the RNC switches. . . . . . . . . . . . . . . . . . . . . . . . 122.3.3 Spanning tree configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4 IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4.1 MTU settings in RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4.2 MTU settings in the RNC site routers . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4.3 Default gateway configuration in RNC OMU and OMS . . . . . . . . . . . . . 132.4.4 IP route configuration in site routers for uplink Iub traffic. . . . . . . . . . . . 132.4.5 IP route configuration in the site routers for downlink Iub traffic . . . . . . 132.4.6 HSRP protection for user plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.5 Quality of service (QoS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.5.1 Packet marking in RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.5.2 Packet classification in site routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.6 Control plane configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.6.1 Multiple active NP2GEs for control plane redundancy. . . . . . . . . . . . . . 142.6.2 RNC internal IPoA configuration for control plane . . . . . . . . . . . . . . . . . 152.6.3 Control plane IP address configuration in the RNC . . . . . . . . . . . . . . . . 152.7 User plane configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.7.1 RNC IP-based route configuration for Iu/Iur connections without load shar-

ing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.7.2 RNC IP-based route configuration for Iu connections with load sharing 162.7.3 RNC configuration of IP-based route for Iub . . . . . . . . . . . . . . . . . . . . . 162.8 O&M configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3 Reference configuration for RNC IP site solution based on Cisco 76xx rout-ers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.1 Site configuration and equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2 Ethernet configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.1 VLAN and HSRP site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.2 Ethernet LAN port configuration in the site routers . . . . . . . . . . . . . . . . 20

4 DN70664131Issue 01C



3.3 IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.3.1 RNC external IP interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . 213.3.2 RNC internal IP interface reference configuration for RNC2600 capacity

step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.4 Quality of service (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

DN70664131Issue 01C

5



List of figuresFigure 1 Cisco 76xx as RNC site router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Figure 2 Connectivity between protected NP2GE (NPGEP) units and Cisco 76xx

routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 3 Multiple active NP2GEs for control plane redundancy. . . . . . . . . . . . . . 15Figure 4 DCN connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 5 Cisco 76xx as RNC site solution with ToP master server . . . . . . . . . . . 17

6 DN70664131Issue 01C



List of tablesTable 1 VLAN interface and HSRP group configuration in Cisco 7609 routers . 19Table 2 Ethernet LAN port configuration in the site routers . . . . . . . . . . . . . . . . 20Table 3 RNC external IP interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . 21Table 4 RNC internal IP interface configuration for RNC2600 . . . . . . . . . . . . . . 22Table 5 DiffServ configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

DN70664131Issue 01C

7


Summary of changes


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

Please note that our issue numbering system is changing. For more information, see Guide to WCDMA RAN Documentation.

Changes between issues 01B and 01CA note has been added in the section Spanning tree configuration.

In the table RNC internal IP interface configuration for RNC2600, the interface type name format of the NPGE units has been changed from IFAI0* to IFAI*.

Figure Cisco 76xx as RNC site solution with ToP master server in the section Site con-figuration and equipment has been rectified.

Changes between issues 1-1 and 01BThe name of the document has been changed into Configuring RNC IP site solution based on Cisco 76xx routers.

Section Solution based on Tellabs router, Chapter RNC IP site solution for Iub based on Tellabs router, and Chapter Reference configuration for RNC IP site solution for Iub based on Tellabs router have been moved to Configuring RNC IP site solution for Iub based on Tellebs router.

The following sections have been added:

• HSRP protection for user plane • RNC IP-based route configuration for Iu connections with load sharing

The following sections have been updated:

• Ethernet cabling • Ethernet interface configuration in RNC and site routers • Spanning tree configuration • MTU settings in the RNC site routers • Default gateway configuration in RNC OMU and OMS • IP route configuration in site routers for uplink Iub traffic • Packet marking in RNC • Multiple active NP2GEs for control plane redundancy • RNC internal IPoA configuration for control plane • Control plane IP address configuration in the RNC • O&M configuration • Site configuration and equipment • RNC internal IP interface reference configuration for RNC2600 capacity step 1

The following table have been updated:

• VLAN interface and HSRP group configuration in Cisco 7609 routers • Ethernet LAN port configuration in the site routers • RNC external IP interface configuration • RNC internal IP interface configuration for RNC2600

Figure Cisco 76xx as RNC site router has been rectified.

8 DN70664131Issue 01C



Summary of changes

Changes between issues 1-0 and 1-1The following chapters have been added:

• RNC IP site solution for Iub based on Tellabs router • Reference configuration for RNC IP site solution for Iub based on Tellabs router.

Section Spanning tree configuration has been added.

The names of the following chapters have changed:

• Introduction into Introduction to RNC IP site solution • Reference configuration for RNC IP site solution into Reference configuration for

RNC IP site solution based on Cisco 76xx routers.

The name of Section Non-paired NP2GEs for control plane redundancy has changed into Multiple active NP2GEs for control plane redundancy.

The following sections have been updated:

• Introduction to RNC IP site solution • Ethernet interface configuration in RNC and site equipment • VLAN configuration in the RNC switches • Packet marking in RNC • Multiple active NP2GEs for control plane redundancy • Configuration of RNC IP based route for Iu/Iur connections without load-sharing • RNC configuration of IP based route for Iub.

DN70664131Issue 01C

9


Introduction

Id:0900d805806152dbConfidential

1 Introduction

1.1 Solution based on Cisco 76xx series routersCisco 76xx series supports Layer 2 switching (Ethernet) and Layer 3 routing (IP) at the same time.

A redundant pair of Cisco 76xx series routers integrates an RNC into the operator's IP-based RAN and handles all interfaces at the same time (Iub, Iur, Iu-PS, Iu-CS, O&M).

The deployment of a Cisco 76xx series router provides many standard WAN interfaces including 1 Gigabit Ethernet, 10 Gigabit Ethernet, SDH, and ATM.

This site solution enables a unified site connectivity at the core site featuring RNC(s), MGW(s), and/or SGSN(s), as frequently the same solution is already established as a CN (Core Network) site solution.

Based on the selected interface implementation, the site solution interoperates with various backbone architectures, such as IP/MPLS or Carrier Ethernet.

Cisco 76xx series can be upgraded with the security gateway functionality.

The Cisco 76xx series interoperability with the RNC redundancy solution has been ver-ified.

Figure Cisco 76xx as RNC site router shows the reference setup for the Cisco 76xx based RNC site solution.

Figure 1 Cisco 76xx as RNC site router

The solution consists of a pair of Cisco 76xx routers connected to the RNC (and poten-tially further co-located mobile network elements). WBTSes are connected through a packet network that is attached to the routers WAN interfaces. The core network (CN) elements shown in Figure Cisco 76xx as RNC site router are optionally present at the RNC site.

10 DN70664131Issue 01C



RNC IP site solution based on Cisco 76xx routers

2 RNC IP site solution based on Cisco 76xx routers

2.1 Co-located equipment

2.1.1 Symmetricom TP5000 equipmentIf the functionality of Timing-over-Packet master server has to be implemented at the RNC site, the installation is based on the following equipment:

• Symmetricom TP5000 ToP master clock • one IOC interface module • two 100/1000Base-T SFPs (small form-factor pluggable)

Additionally a timing source (such as GPS) can be located in the RNC site to provide timing input to the ToP master clock. Suitable sources are defined by the TP5000 requirements.

2.1.2 Site support equipmentAdditional site support equipment, such as a local management PC or other mainte-nance equipment, should be considered in the site connectivity planning.

2.1.3 Co-located network elementsThe site solution can be shared with additional network elements, such as an MGW. For more information, see Configuring IP Connection for RNC.

2.2 Physical configuration

2.2.1 Physical Ethernet interface configuration

RNC NP2GE unitsThe connectivity between the RNC NP2GE units and the site routers ports is based on one of the following standards:

• 1000Base-TX, RJ-45 connectors - electrical transmission • 1000Base-LX, LC connectors - optical transmission (SFP required)

RNC ESA24 unitsThe connectivity between the RNC ESA24 units and the site routers ports is based on Fast Ethernet (100Base-T/TX, RJ-45 connectors).

2.2.2 Ethernet cabling

100 Mbit Ethernet and 1 Gbit Ethernet electrical linksElectrical (twisted pair) Fast Ethernet and Gigabit Ethernet cabling between the site routers and the RNC complies with Category 5 at least.

DN70664131Issue 01C

11




1 Gbit Ethernet optical links1 Gigabit Ethernet cabling between the site routers and the RNC is based on a single-mode-fiber (SMF) complying with standard ITU-T G.652.

10 Gbit Ethernet optical links10 Gigabit Ethernet cabling between the site routers is based on a single-mode-fiber (SMF) complying with standard ITU-T G.652.

2.2.3 Ethernet cable typesBetween the RNC ESA24 units and the site routers, crossover cables are required.

Between RNC NP2GE units and the site routers, straight-through cables are required.

2.2.4 Ethernet link connectivity for protected NP2GE unitsIf a pair of NP2GE units in the RNC is configured to the protected mode (NPGEP) oper-ation and both Ethernet ports are to be used, these two ports of the working (WO) unit have to be connected to the same router. Accordingly, the two ports of the spare (SP), protecting NP2GE unit are connected to the other router. Supported and not supported connections are depicted in Figure Connectivity between protected NP2GE (NPGEP) units and Cisco 76xx routers.

Figure 2 Connectivity between protected NP2GE (NPGEP) units and Cisco 76xx routers

2.3 Ethernet configuration

2.3.1 Ethernet interface configuration in RNC and site routers

Configuration in RNC NP2GEs and the site routersNP2GE units in the RNC and the connected site router ports operate in full-duplex 1 Gb/s mode only. This is assured by using Ethernet auto-negotiation mode in both devices

g For the 1 Gb/s Ethernet standard, auto-negotiation is the default operating mode. In addition, it provides advanced error-detection capabilities (for example, the remote fault indicator). The default NP2GE operating mode, auto-negotiation, allows only full-duplex 1 Gb/s.

NPGEP 0

(WO)

NPGEP 1

(SP)

0

1

RNC

Supported configuration NOT supported configuration

0

1

NPGEP 0

(WO)

NPGEP 1

(SP)

0

1

RNC

0

1

12 DN70664131Issue 01C




It is recommended to configure the Ethernet ports of the site routers to mdix auto mode. The RNC NP2GE ports operate in automatic MDI/MDIX detection mode (not configu-rable).

Configuration in the RNC ESA24 switches and the site routersThe RNC ESA24 switches and the connected ports in the site routers operate in full-duplex 100 Mb/s mode. This configuration is enabled with either Ethernet auto-negotia-tion mode or forced mode in both devices.

It is recommended to configure the Ethernet ports of the site routers to no mdix auto mode and the RNC ESA24 ports to crossover mdix mode.

2.3.2 VLAN configuration in the RNC switchesIn the RNC ESA24 switches, only the ports connected to the site routers are VLAN tagged. These ports are configured to the O&M VLAN.

RNC OMU and OMS units do not require VLAN configuration, thus it is limited to the ESA switches only.

2.3.3 Spanning tree configurationBetween ESA24 units in the RNC and the corresponding site router ports, a Multiple Spanning Tree Protocol (MSTP) configuration should be applied. RootGuard should be activated on the site router ports connected to the RNC ESA24 unit(s). PortFast feature should be activated on all other site router ports that are connected to the RNC NP2GE units.

A consistent MSTP configuration (region name, revision number, VLAN to instance mapping) must be applied to the site routers and ESA24 switches. The site routers must be configured as primary and secondary root switches. Thus, the following bridge prior-ities have to be applied:

• primary root: 24576 • secondary root: 28672 • ESA24: 32768 (default)

Because of the redundant links between ESA24 switches and the site routers, MSTP protocol is required to break the layer 2 loops.

NP2GE units are not Ethernet switches, thus no spanning tree is required between NP2GEs and the site routers. PortFast feature is used to enable a fast recovery of NP2GE unit interfaces.

g Cisco IOS requires different commands for activating PortFast on ports that are in trunking mode (command spanning-tree portfast trunk) compared to ports that are in access mode (command spanning-tree portfast).

2.4 IP configuration

2.4.1 MTU settings in RNCIn the NP2GE units, MaximumTtransmission Unit (MTU) size is configured to 1500 bytes. In the ICSU units, MTU is configured to 1472 bytes.

DN70664131Issue 01C

13




For the control plane also the Iub part has to be considered, as the same ICSU is used for both Iub and Iu/Iur. Flexi WCDMA BTS introduces a payload limit of 1472 byte. This limit does not have to be considered for the user plane, as the Frame Protocol in the RNC already considers the MTU size of the user plane.

2.4.2 MTU settings in the RNC site routersMTU size of 1500 bytes is configured on all site routers interfaces connected to the RNC or the mobile backhaul network, assuming that the network supports the MTU of at least 1500 bytes end-to-end.

2.4.3 Default gateway configuration in RNC OMU and OMSOMU and OMS units in the RNC are configured to use a default gateway for the whole traffic. The gateway address is the virtual (HSRP - Hot Standby Router Protocol) IP address of the RNC site routers. The address is located in the O&M subnet (for example, the address 10.1.4.1 in accordance with VLAN and HSRP site configuration).

As the site routers terminate the IP routes between the network management system and the RNC site, it is sufficient for OMU and OMS units to forward traffic directly to the routers.

2.4.4 IP route configuration in site routers for uplink Iub trafficIf multiple interfaces are configured for the Iub transport in the RNC, the site routers are configured with Equal Cost Multiple Routes (ECMP) towards the RNC Iub control plane subnets. To provide a sufficient level of redundancy and capacity, it is recommended to configure at least two parallel routes.

In the downlink, the RNC detects which NPGE handles the user plane traffic of a partic-ular base station, so that the control plane traffic can be sent through the same NPGE. However, in the uplink direction this information is not available in the site routers. An unbalanced allocation of the uplink control plane traffic to a single NPGE or a few NPGEs can be avoided using ECMP.

For the user plane no routes are required, as the user plane subnets in the RNC are con-nected directly to the site routers. For more information, see RNC configuration of IP-based route for Iub.

2.4.5 IP route configuration in the site routers for downlink Iub trafficFor each base station the routes towards their control/user plane and O&M subnets are configured to the site routers.

2.4.6 HSRP protection for user planeIf static routing is used for the user plane between the RNC and another NE, it is recom-mended to deploy the Hot Standby Router Protocol (HSRP) in the site routers. The fol-lowing timer settings are recommended:

• HSRP hello timer: 300 ms • HSRP hold timer: 1000 ms

14 DN70664131Issue 01C




With the static routing, a separate default gateway needs to be configured for each IP route. Without the HSRP, in case the default gateway fails, there is no protection IP route for this gateway. When deployed, the HSRP monitors the state of the primary gateway (the site router with a higher priority) and provides a protection gateway (the router with a lower priority). In case of a primary gateway failure, the protection gateway takes the (virtual) gateway IP address and becomes the active gateway.

g The control plane traffic is not protected by the HSRP because it can interfere with the operation of the multi-homing protection of the Stream Control Transmission Protocol (SCTP).

For more information, see VLAN and HSRP site configuration.

2.5 Quality of service (QoS)

2.5.1 Packet marking in RNCThe RNC provides packet priority marking based on the Differentiated Services Code Point (DSCP). Even though the RNC supports packet marking based on the 3 bit VLAN priority code point (PCP) field of the Ethernet frame, too, it is recommended to use the DSCP marking. Marking of the O&M traffic, as well as any other marking scheme, can be provided by using QoS access list in the site routers.

The reference configuration described in Quality of service (QoS) uses the DSCP marking in the RNC.

2.5.2 Packet classification in site routersThe classification of the ingress packets in the site routers is based on the received DSCP in all site routers Ethernet ports connected to the RNC NP2GE units. For the Ethernet ports connected to the ESA24 switches and data communication network (DCN), the site routers apply a fixed classification in accordance with the operator’s DSCP setting for O&M traffic (this is typically 10 - AF1).

As the OMU and OMS units do not apply the DCSP marking of the egress traffic, it is executed in the site routers based on their QoS access lists.

2.6 Control plane configuration

2.6.1 Multiple active NP2GEs for control plane redundancyTwo different active (WO) NP2GE units are used to transmit the Iu/Iur control plane traffic. For a given control plane connection (for example, towards an MSC Server), each primary SCTP link uses one active NPGEP unit, while each secondary SCTP link (multi-homing in use) uses the other active NPGEP unit. Thus, a specific NP2GE is never used for both the primary and secondary link of the same control plane connection. Primary and secondary associations of different control plane instances can be mixed on the same NPGEPs to implement load sharing. For example, NPGEP-0 hosts both IuCS primary and IuPS secondary associations, as it is indicated in Figure Multiple active NP2GEs for control plane redundancy.

DN70664131Issue 01C

15




Figure 3 Multiple active NP2GEs for control plane redundancy

g NP2GE switchover is non-revertive; thus the original configuration is not returned automatically. Consequently both SCTP paths can go through the same site router. When the problem that led to the NP2GE switchover is fixed, the operator can manually switchover the NP2GE during a maintenance period.

2.6.2 RNC internal IPoA configuration for control planeThe RNC Iub control plane subnet is based on the IP over ATM (IPoA) mesh automati-cally created between ICSUs and NP2GEs. In addition, for Iu/Iur control plane connec-tions, it is recommended to manually create the RNC internal IPoA connections.

2.6.3 Control plane IP address configuration in the RNCIt is recommended to assign IP addresses to the IPoA interfaces in the ICSU and NPGE units in the following way:

• in the numbered mode for the ICSU units • in the unnumbered mode for the NPGE units

In the NPGE units, the Ethernet interfaces (IFGE) reuse IP addresses in unnumbered mode, avoiding the need for additional IP addresses. In the ICSU units, the default mode (numbered) is used.

2.7 User plane configuration

2.7.1 RNC IP-based route configuration for Iu/Iur connections without load sharingFor each CN element and each neighboring RNC, it is recommended to configure a ded-icated IP-based route using different IP addresses from separate subnets at the RNC site.

g RNC also supports the use of one address for multiple connections. This is not rec-ommended since it introduces some restrictions on the network planning (for

16 DN70664131Issue 01C




example, the same VLAN tag needs to be applied externally) and also complicates the network troubleshooting.

2.7.2 RNC IP-based route configuration for Iu connections with load sharingIn addition to the configuration described in Section RNC IP-based route configuration for Iu/Iur connections without load sharing, the RNC supports configuring load sharing connections towards CN elements (for example, high capacity Iu-PS connection). It is implemented by a single IP-based route, which is based on two IP addresses configured to different NP2GE units. For protection, the solution provides up to 2x 1 Gb/s capacity and load balancing (the RNC applies the round robin scheme per connection).

2.7.3 RNC configuration of IP-based route for IubFor each base station, a dedicated IP-based route is configured. At the RNC side, only one IP address is configured to each Ethernet port/VLAN that is used for Iub interface.

No benefits are derived from using dedicated IP address for each Iub IP-based route in the RNC. Thus, the minimum amount of addresses (one address per port without VLANs, or one address per VLAN respectively) is chosen in order to minimize the con-figuration effort and IP address demand.

2.8 O&M configurationDCN connectivityThe DCN network (O&M network providing the connection to NetAct) provides layer 3 (routed) connections to the site routers. The O&M related units in the RNC are con-nected to the site routers through ESA24 switches, as indicated in Figure DCN connec-tivity, using layer 2 switching.

Figure 4 DCN connectivity

Routing in the OMS and OMU units is based on a single default IP route, as described in Section Default gateway configuration in RNC OMU and OMS.

RNC

OMU-0

(WO)

OMS

OMU-1

(SP)

Transport

Network

DCN

NetAct

ESA24 - 0

ESA24 - 1

7600 - 1

7600 - 0

DN70664131Issue 01C

17


Reference configuration for RNC IP site solution basedon Cisco 76xx routers


3 Reference configuration for RNC IP site solution based on Cisco 76xx routers

3.1 Site configuration and equipmentCisco 76xx as RNC site solutionThe reference configuration presented in this chapter is based on a pair of Cisco 76xx series routers. It consists of the following equipment items:

• RNC2600 (capacity step 1) • dual Cisco 7600 series routers • two Ethernet based interfaces to the transport network (L2 and/or L3 configuration) • two Layer 3 interfaces to the DCN (O&M) network (providing the connectivity

towards NetAct)

If the functionality of Timing-over-Packet master server is required at the RNC site, addi-tionally Symmetricom TP5000 ToP master clock is installed.

Figure Cisco 76xx as RNC site solution with ToP master server depicts the connectivity solution for the RNC site including the ToP master server. Depending on the RNC con-figuration, different numbers of NP2GE units are required.

Figure 5 Cisco 76xx as RNC site solution with ToP master server

RNC2600 equipmentThe RNC installation is based on the following equipment configuration:

• RNC2600 (capacity step 1) • six NP2GE Ethernet interface units (in protected configuration: three WO + three

SP) • two ESA24 Ethernet switches

18 DN70664131Issue 01C



Reference configuration for RNC IP site solution based on Cisco 76xx routers

• two OMU units • one OMS unit

Further units are required to operate the RNC; however, here only those affecting the IP transport are considered.

Cisco 7609 router equipmentThe Cisco router installation is based on the following equipment configuration:

• Chassis - 7609-S • Supervisor - 7600 Route Switch Processor 720 (7609S-RSP720C-P) • IOS 12.2(33)SRC2 Software - Advanced IP Services license • Catalyst 6500 48-port 10/100/1000 Gigabit Ethernet line card (WS-X6748-GE-TX) • Catalyst 6500 Central Forwarding Card for WS-X67xx modules (WS-F6700-CFC) • Catalyst 6500 256MB DDR, xCEF720 (MEM-XCEF720-256M)

Optional Cisco 7609 router equipment

g This equipment is optional and depends on the customer network planning.

WAN interface modules may be required to connect the site routers to the transport network. The type of the modules used is defined by the transport network and its requirements. The following modules are recommended:

• Catalyst 6500 24/48-port Gigabit Ethernet line card for SFPs (WS-X6724/6748-SFP)

• Cisco 7600 Ethernet Services 20-port 1 Gigabit Ethernet line card (7600-ES20-GE3C)

• Cisco 7600 Ethernet Services 2-port 10 Gigabit Ethernet line card (7600-ES20-10G3C)

If 10 Gigabit Ethernet interconnection between the two routers is considered, it is rec-ommended to use Catalyst 6500 8-port 10 Gigabit Ethernet line card (WS-X6708-10G-3C) for a cost-efficient implementation (less applicable as a WAN interface unit because of limitations on queueing and shaping):

The recommended SFPs/XFPs are:

• for Catalyst 6500 SFP (WS-X6724/6748-SFP) line cards • 1000Base-LX/LH SFP (GLC-LH-SM) for the optical transmission • 1000Base-T SFP (GLC-T) for the electrical transmission

• for Ethernet Services (ES20) line cards • Multirate XFP module for 10GBase-LR and OC192 SR-1 (XFP-10GLR-

OC192SR) • for 10 Gigabit Ethernet LAN (WS-X6708) line card

• 10GBase-LR X2 module (X2-10GB-LR)

3.2 Ethernet configuration

3.2.1 VLAN and HSRP site configurationTable VLAN interface and HSRP group configuration in Cisco 7609 routers lists VLANs to be configured in the site routers.

DN70664131Issue 01C

19




VLAN usage device IP address / subnet

HSRP

group prio

group ID

virtual router IP

8 O&M7609-1 10.1.4.02 / 29 110

8 10.1.4.01 / 297609-2 10.1.4.03 / 29 90

9 ToP7609-1 10.1.5.02 / 29 110

9 10.1.5.01 / 297609-2 10.1.5.03 / 29 90

10 Iu-PS UP7609-1 10.1.1.02 / 29 110

10 10.1.1.01 / 297609-2 10.1.1.03 / 29 90

12 Iu-CS UP7609-1 10.1.1.18 / 29 90

12 10.1.1.17 / 297609-2 10.1.1.19 / 29 110

15 Iur-1 UP7609-1 10.1.1.26 / 29 90

15 10.1.1.25 / 297609-2 10.1.1.27 / 29 110

16 Iur-2 UP7609-1 10.1.1.34 / 29 90

16 10.1.1.33 / 297609-2 10.1.1.35 / 29 110

20 Iu-PS CP prim.

7609-1 n/an/a

7609-2 10.1.2.03 / 29

21 Iu-PS CP sec.

7609-1 10.1.2.10 / 29n/a

7609-2 n/a

22 Iu-CS CP prim.

7609-1 10.1.2.18 / 29n/a

7609-2 n/a

23 Iu-CS CP sec.

7609-1 n/an/a

7609-2 10.1.2.27 / 29

24 Iur-1 CP prim.

7609-1 10.1.2.34 / 29n/a

7609-2 n/a

25 Iur-1 CP sec.

7609-1 n/an/a

7609-2 10.1.2.43 / 29

26 Iur-2 CP prim.

7609-1 n/an/a

7609-2 10.1.2.51 / 29

27 Iur-2 CP sec.

7609-1 10.1.2.58 / 29n/a

7609-2 n/a

30 Iub-17609-1 10.1.3.66 / 29 90

30 10.1.3.65 / 297609-2 10.1.3.67 / 29 110

31 Iub-27609-1 10.1.3.74 / 29 90

31 10.1.3.73 / 297609-2 10.1.3.75 / 29 110

Table 1 VLAN interface and HSRP group configuration in Cisco 7609 routers

20 DN70664131Issue 01C




3.2.2 Ethernet LAN port configuration in the site routersEthernet LAN ports in the site routers are configured in accordance with Table Ethernet LAN port configuration in the site routers.

Interface mode, LAN port mode, and Trunk encapsulation have constant values for all configurations, respectively: switchport, nonegotiate, and dot1g.

device port allowed VLANs

EtherChannelspan. tree usage

con-nected

portmode group

7609-1 Gi5/1 all active 1 MSTP Site switch interconnect

7609-2 / Gi5/1


7609-2 / Gi5/2

7609-1 Gi1/1 10 - - PortFast Iu-PS UP NPGE0-IFGE0

7609-1 Gi1/2 21,22,24,27

- - PortFast Iu control plane

NPGE0-IFGE1

7609-1 Gi1/3 12 - - PortFast Iu-CS UP NPGE3-IFGE0

7609-1 Gi1/4 15,16,20,23,25,26

- - PortFast Iur UP, Iu control plane

NPGE3-IFGE1

7609-1 Gi1/5 30 - - PortFast Iub NPGE5-IFGE0


7609-1 Gi1/13 8 - - RootGuard O&M ESA24-0


7609-1 Gi1/19 9 - - PortFast Timing-over-Packet

ToP Master, IOC 0-0


7609-1 / Gi5/1


7609-1 / Gi5/2

7609-2 Gi1/1 10 - - PortFast Iu-PS UP NPGE1-IFGE0

7609-2 Gi1/2 21,22,24,27

- - PortFast Iu control plane

NPGE1-IFGE1

7609-2 Gi1/3 12 - - PortFast Iu-CS UP NPGE2-IFGE0

7609-2 Gi1/4 15,16,20,23,25,26

- - PortFast Iur UP, Iu control plane

NPGE2-IFGE1


Table 2 Ethernet LAN port configuration in the site routers

DN70664131Issue 01C

21




The site routers ports that face the RNC ESA switches have to be configured as a trunk for all VLANs (VLAN parameter allowed) because the same site router might be involved in further multiple spanning tree (MST) instances. The Multiple Spanning Tree Protocol (MSTP) needs at least one VLAN from each instance to be allowed on each trunk to operate correctly.

3.3 IP configuration

3.3.1 RNC external IP interface configurationThe RNC IP interfaces are configured as indicated in Table RNC external IP interface configuration.




7609-2 Gi1/19 9 - - PortFast Timing-over-Packet

ToP Master, IOC 0-1

device port allowed VLANs

EtherChannelspan. tree usage

con-nected

portmode group

Table 2 Ethernet LAN port configuration in the site routers (Cont.)

unit interface usage IP address / subnet remark

NPGE-0

IFGE-0 Iu-PS UP 10.1.1.04 / 29

HSRP not applied to control planeIFGE-1

Iu-CS CP (primary) 10.1.2.20 / 29

Iu-PS CP (secondary) 10.1.2.12 / 29

Iur-1 CP (primary) 10.1.2.36 / 29

Iur-2 CP (secondary) 10.1.2.60 / 29

Iu-PC #1 10.1.2.68 / 29

NPGE-2

IFGE-0 Iu-CS UP 10.1.1.20 / 29

HSRP not applied to control planeIFGE-1

Iur-1 UP 10.1.1.28 / 29

Iur-2 UP 10.1.1.36 / 29

Iu-CS CP (secondary) 10.1.2.28 / 29

Iu-PS CP (primary) 10.1.2.04 / 29

Iur-1 CP (secondary) 10.1.2.44 / 29

Iur-2 CP (primary) 10.1.2.52 / 29

Iu-PC #2 10.1.2.76 / 29

Table 3 RNC external IP interface configuration

22 DN70664131Issue 01C




3.3.2 RNC internal IP interface reference configuration for RNC2600 capacity step 1The RNC internal IP interfaces (IPoA interfaces on ICSU and NPGE units) are config-ured as indicated in Table RNC internal IP interface configuration for RNC2600.

NPGE-4IFGE-0 Iub-1 UP/CP 10.1.3.68 / 29

-IFGE-1 Iub-2 UP/CP 10.1.3.76 / 29

NPGE-1 (Redundant unit for NPGE-0: the same configuration applies)



OMU-0EL-0 O&M 10.1.4.05 / 28

-EL-1 O&M 10.1.4.05 / 28

OMU-1 (Redundant unit for OMU-0: the same configuration applies)

OMSEL-0 O&M 10.1.4.04 / 28

-EL-1 O&M 10.1.4.04 / 28

unit interface usage IP address / subnet remark

Table 3 RNC external IP interface configuration (Cont.)

ICSUusage

NPGE

unit inter-face

IP address IP address inter-face

unit

ICSU-0

AA010.1.3.145 / 29 Iu-CS CP (primary) 10.1.2.20 / 29

IFAI0 NPGE-010.1.3.161 / 29 Iur-1 CP (primary) 10.1.2.36 / 29

AA110.1.3.153 / 29 Iu-CS CP (secondary) 10.1.2.28 / 29

IFAI0 NPGE-210.1.3.169 / 29 Iur-1 CP (secondary) 10.1.2.44 / 29

ICSU-1

AA010.1.3.146/ 29 Iu-CS CP (primary) 10.1.2.20 / 29


AA110.1.3.154 / 29 Iu-CS CP (secondary) 10.1.2.28 / 29


ICSU-2

AA010.1.3.129 / 29 Iu-PS CP (primary) 10.1.2.04 / 29


AA110.1.3.137/ 29 Iu-PS CP (secondary) 10.1.2.12 / 29

IFAI2 NPGE-010.1.3.185/ 29 Iur-2 CP (secondary) 10.1.2.60 / 29

ICSU-3

AA010.1.3.130 / 29 Iu-PS CP (primary) 10.1.2.04 / 29


AA110.1.3.138 / 29 Iu-PS CP (secondary) 10.1.2.12 / 29


Table 4 RNC internal IP interface configuration for RNC2600

DN70664131Issue 01C

23




Iub control plane is configured on subnet 10.1.3.0/29 using the full mesh of IPoA links between all the ICSU and NPGE units. This is created automatically by the system. The IPoA mesh is based on interfaces AA450-AA511 (in ICSUs) and on interfaces IFAI30-IFAI79 (in NPGEs).

3.4 Quality of service (QoS)DiffServ configurationDSCP to per-hop behavior (PHB) mapping is applied in accordance with Table DiffServ configuration.

g The Ethernet line card of the reference configuration in the site router supports only four queues instead of the six supported by the RNC. Four queues are common for most of the transmission devices.

DSCP PHB usage example (Iu) usage example (Iub)

Tx Queue in site router

46 EF AMR, CS-Data RT DCH strict priority queue

36 AF42streaming data, GTP signaling

NRT DCH, HSPA control high priority queue

34 AF41 control plane NBAP

26 AF3interactive data (THP1) RT HSPA

medium priority queue18 AF2

interactive data (THP2)

10 AF1interactive data (THP3) O&M

0 BE background data NRT HSPA best effort queue

Table 5 DiffServ configuration

Documents

76XX