07 RNC in Pool Delivery Guide (RAN18.1)

WCDMA RAN
RNC in Pool Reconstruction Guide

(RAN18.1)
Issue 01
Date 2016-11-04
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2016. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2016-11-04) Huawei Proprietary and Confidential i

Copyright © Huawei
Technologies Co., Ltd.
RNC in Pool Reconstruction Guide (RAN18.1) Contents
Contents
1 About This Document..................................................................................................................1

1.1 Purpose...........................................................................................................................................................................1
1.2 Scope..............................................................................................................................................................................1
1.3 Intended Audience..........................................................................................................................................................2
1.4 Change History...............................................................................................................................................................2
1.5 Deployment Policy.........................................................................................................................................................2
1.6 Prerequisites...................................................................................................................................................................2
1.7 Precautions.....................................................................................................................................................................3
1.7.1 U2000/CME/NEP........................................................................................................................................................3
1.7.2 Neighboring NEs.........................................................................................................................................................4
1.7.3 NE Licenses.................................................................................................................................................................5
1.7.4 NEs..............................................................................................................................................................................6
1.7.5 Interfaces and Transmission........................................................................................................................................8
1.7.6 NBI Interconnection....................................................................................................................................................9
1.8 Related Documentation................................................................................................................................................10
2 Engineering Guidelines for Load Sharing.............................................................................11

2.1 Typical Scenarios..........................................................................................................................................................11
2.1.1 Scenario 1: N Master RNCs and An Overflow RNC Carrying Multiple Logical RNCs..........................................11
2.1.2 Scenario 2: Two Physical RNCs Carrying Two Logical RNCs................................................................................13
2.1.3 Scenario 3: Four BSC6900s and Two BSC6910s Carrying Multiple Logical RNCs...............................................15
2.2 Deployment Process.....................................................................................................................................................16
2.2.1 Reconstruction Process..............................................................................................................................................16
2.2.2 Rollback Procedure...................................................................................................................................................20
2.2.2.1 Deactivation............................................................................................................................................................20
2.2.2.2 Networking Rollback..............................................................................................................................................20
2.3 Preparation....................................................................................................................................................................21
2.4 Procedures for Load Sharing Reconstruction...............................................................................................................22
2.4.1 Preparing License Files.............................................................................................................................................24
2.4.2 Activating License Files............................................................................................................................................29
2.4.3 Backing Up Data and Preparing Tools......................................................................................................................30
2.4.4 Configuring Iur-p Interfaces......................................................................................................................................33
2.4.4.1 Control-Plane Load Sharing...................................................................................................................................33
Issue 01 (2016-11-04) Huawei Proprietary and Confidential ii

Copyright © Huawei
2.4.4.2 User-Plane Load Sharing........................................................................................................................................37

2.4.5 Configuring Iu/Iur User-Plane Data for the Overflow RNC.....................................................................................42
2.4.6 Configuring Iub User-Plane Data for the Overflow RNC.........................................................................................47
2.4.7 Exporting Configuration Scripts................................................................................................................................55
2.4.8 Pre-Activating Configuration Scripts........................................................................................................................56
2.4.9 Activating Configuration Scripts...............................................................................................................................58
2.4.10 Synchronizing the RNC-level Data Within a Pool..................................................................................................59
2.4.11 Performing CN and Neighboring RNC Interconnection.........................................................................................61
2.4.12 Activating Load Sharing..........................................................................................................................................62
2.4.12.1 Pre-Activation Checks..........................................................................................................................................62
2.4.12.2 Feature Activation................................................................................................................................................64
2.5 Acceptance....................................................................................................................................................................64
2.5.1 Checking the RNC in Pool Topology........................................................................................................................64
2.5.2 Checking the Synchronization Task Status on the CME...........................................................................................67
2.5.3 Checking Licenses.....................................................................................................................................................68
2.5.4 Checking the Iur-p Transmission Delay....................................................................................................................68
2.5.5 Checking Alarms.......................................................................................................................................................68
2.5.6 Checking RNC in Pool Configurations.....................................................................................................................69
2.5.7 Checking Basic Services...........................................................................................................................................69
2.5.8 Accepting Load Sharing............................................................................................................................................70
2.6 Procedures for Rolling Back Load Sharing..................................................................................................................72
2.6.1 Deactivation...............................................................................................................................................................72
2.6.2 RNC in Pool Networking Rollback...........................................................................................................................73
2.6.2.1 Control-Plane Load Sharing Rollback....................................................................................................................73
2.6.2.2 User-Plane Load Sharing Rollback........................................................................................................................73
3 Engineering Guidelines for Node Redundancy....................................................................76

3.1 Typical Scenarios..........................................................................................................................................................76
3.1.1 Scenario 1: N Master RNCs and An Backup RNC Carrying Multiple Logical RNCs.............................................76
3.1.2 Scenario 2: Two Physical RNCs Carrying Two Logical RNCs................................................................................79
3.1.3 Scenario 3: Four BSC6900s and Two BSC6910s Carrying Multiple Logical RNCs...............................................79
3.2 Deployment Process.....................................................................................................................................................82
3.2.1 Reconstruction Process..............................................................................................................................................82
3.2.2 Rollback Procedure...................................................................................................................................................84
3.2.2.1 Deactivating Node Redundancy.............................................................................................................................84
3.2.2.2 Networking Rollback..............................................................................................................................................84
3.3 Preparation....................................................................................................................................................................86
3.4 Procedures for Node Redundancy Reconstruction.......................................................................................................86
3.4.1 Preparing License Files.............................................................................................................................................89
3.4.2 Activating License Files............................................................................................................................................93
3.4.3 Backing Up Data and Preparing Tools......................................................................................................................94
3.4.4 Configuring Iur-p Interfaces......................................................................................................................................97
Issue 01 (2016-11-04) Huawei Proprietary and Confidential iii

Copyright © Huawei
3.4.5 Configuring Iu/Iur Interfaces...................................................................................................................................102

3.4.6 Configuring Iub Data for the Backup RNC.............................................................................................................108
3.4.7 Exporting Configuration Scripts..............................................................................................................................116
3.4.8 Pre-Activating Configuration Scripts......................................................................................................................117
3.4.9 Activating Configuration Scripts.............................................................................................................................119
3.4.10 Synchronizing the RNC-level Data Within a Pool................................................................................................120
3.4.11 Synchronizing the NodeB-level Data Within a Pool.............................................................................................122
3.4.12 Performing CN and Neighboring RNC Interconnection.......................................................................................126
3.4.12.1 Backup Routes....................................................................................................................................................126
3.4.12.2 Active and Standby Links...................................................................................................................................129
3.4.12.3 SCTP Dual-homing............................................................................................................................................131
3.4.13 Activating Node Redundancy................................................................................................................................131
3.4.13.1 Pre-Activation Checks........................................................................................................................................131
3.4.13.2 Feature Activation..............................................................................................................................................133
3.5 Acceptance..................................................................................................................................................................133
3.5.1 Checking the RNC in Pool Topology......................................................................................................................133
3.5.2 Checking the Synchronization Task Status on the CME.........................................................................................136
3.5.3 Checking Licenses...................................................................................................................................................137
3.5.4 Checking the Iur-p Transmission Delay..................................................................................................................138
3.5.5 Checking Alarms.....................................................................................................................................................138
3.5.6 Checking RNC in Pool Configurations...................................................................................................................138
3.5.7 Checking Basic Services.........................................................................................................................................139
3.5.8 Accepting Node Redundancy..................................................................................................................................139
3.6 Procedures for Rolling Back Node Redundancy........................................................................................................142
3.6.1 Deactivation.............................................................................................................................................................142
3.6.2 RNC in Pool Networking Rollback.........................................................................................................................142
3.6.2.1 Networking Rollback for Manual Redundancy....................................................................................................142
3.6.2.2 Networking Rollback for Automatic Redundancy...............................................................................................143
4 Engineering Guidelines for Load Sharing and Node Redundancy................................145

4.1 Typical Scenarios........................................................................................................................................................145
4.1.1 Scenario 1: N Master RNCs and An Overflow/Backup RNC Carrying Multiple Logical RNCs...........................145
4.1.2 Scenario 2: Two Physical RNCs Carrying Two Logical RNCs..............................................................................150
4.1.3 Scenario 3: Four BSC6900s and Two BSC6910s Carrying Multiple Logical RNCs.............................................154
4.2 Deployment Process...................................................................................................................................................159
4.2.1 Reconstruction Process............................................................................................................................................159
4.2.2 Rollback Process.....................................................................................................................................................161
4.2.2.1 Deactivating Load Sharing or Node Redundancy................................................................................................161
4.2.2.2 Networking Rollback............................................................................................................................................162
4.3 Preparation..................................................................................................................................................................164
4.4 Procedures for Load Sharing and Node Redundancy Reconstruction.......................................................................164
4.4.1 Preparing License Files...........................................................................................................................................167
Issue 01 (2016-11-04) Huawei Proprietary and Confidential iv

Copyright © Huawei
4.4.2 Activating License Files..........................................................................................................................................172

4.4.3 Backing Up Data and Preparing Tools....................................................................................................................173
4.4.4 Configuring Iur-p Interfaces....................................................................................................................................176
4.4.5 Configuring Iu/Iur Interfaces...................................................................................................................................182
4.4.6 Configuring Iub Interfaces......................................................................................................................................188
4.4.7 Exporting Configuration Scripts..............................................................................................................................196
4.4.8 Pre-Activating Configuration Scripts......................................................................................................................197
4.4.9 Activating Configuration Scripts.............................................................................................................................199
4.4.10 Synchronizing the RNC-level Data Within a Pool................................................................................................200
4.4.11 Synchronizing the NodeB-level Data Within a Pool.............................................................................................202
4.4.12 Performing CN and Neighboring RNC Interconnection.......................................................................................206
4.4.12.1 Backup Routes....................................................................................................................................................206
4.4.12.2 Active and Standby Links...................................................................................................................................209
4.4.12.3 SCTP Dual-homing............................................................................................................................................211
4.4.13 Activating Load Sharing and Node Redundancy..................................................................................................212
4.4.13.1 Pre-Activation Checks........................................................................................................................................212
4.4.13.2 Feature Activation..............................................................................................................................................212
4.5 Acceptance..................................................................................................................................................................212
4.5.1 Checking the RNC in Pool Topology......................................................................................................................212
4.5.2 Checking the Synchronization Task Status on the CME.........................................................................................215
4.5.3 Checking Licenses...................................................................................................................................................217
4.5.4 Checking the Iur-p Transmission Delay..................................................................................................................217
4.5.5 Checking Alarms.....................................................................................................................................................217
4.5.6 Checking RNC in Pool Configurations...................................................................................................................217
4.5.7 Checking Basic Services.........................................................................................................................................218
4.5.8 Accepting Load Sharing..........................................................................................................................................218
4.5.9 Accepting Node Redundancy..................................................................................................................................221
4.6 Procedures for Rolling Back Load Sharing and Node Redundancy..........................................................................223
4.6.1 Deactivation.............................................................................................................................................................223
4.6.2 RNC in Pool Networking Rollback.........................................................................................................................224
5 Appendix.....................................................................................................................................226
5.1 BSC6910 Initial Configuration...................................................................................................................................226
5.2 Iur-p Transmission Delay Measurement Methods......................................................................................................227
5.3 Creating a Planned Data Area.....................................................................................................................................230
5.4 Iu-BC Solution When RNC in Pool Node Redundancy is Enabled...........................................................................232
5.5 OMCH Configuration Methods When RNC in Pool Node Redundancy is Enabled.................................................234
5.6 Manually Synchronizing RNC in Pool Data..............................................................................................................235
5.7 X Project Deployment Solution..................................................................................................................................236
Issue 01 (2016-11-04) Huawei Proprietary and Confidential v

Copyright © Huawei
RNC in Pool Reconstruction Guide (RAN18.1)
RNC in Pool Reconstruction Guide (RAN18.1) About This DocumentAbout This Document
1 About This Document
1.1 Purpose
1.2 Scope
1.3 Intended Audience
1.4 Change History
1.5 Deployment Policy
1.6 Prerequisites
1.7 Precautions
1.8 Related Documentation
1.1 Purpose
This document describes limitations of RNC in Pool network deployment and provides
procedures for frontline personnel to implement such reconstruction.
1.2 Scope
This document applies only to the implementation phase of RNC in Pool network
deployment. For details on RNC in Pool network design, see UMTS RNC in Pool Network
Design Technical Guide.
This document covers the following features:
 WRFD-150211 RNC in Pool Load Sharing
 WRFD-150212 RNC in Pool Node Redundancy
 WRFD-150240 RNC in Pool Multiple Logical RNCs
This document applies to the NE types as listed in the following table.
Issue 01 (2016-11-04) Huawei Proprietary and Confidential 1

Copyright © Huawei
NE Type NE Model
RNC BSC6910 GU, BSC6900

UO, and BSC6910 UO
NodeB Macro BTS3900, BTS3900A,
BTS3900L, BTS3900AL,
DBS3900, and BTS3900C
Micro BTS3911E
LampSite DBS3900 LampSite
This document provides only operation instructions on BSC6900 V900R018C10/BSC6910

V100R018C10 and U2000/CME involved in RNC in Pool reconstruction.
1.3 Intended Audience

This document is intended for personnel who:
 Need to implement RNC in Pool reconstruction
 Work with Huawei products
1.4 Change History

This is the first draft.
1.5 Deployment Policy

 If a BSC6910 needs to be newly deployed, ensure that the BSC6910 is initially
commissioned before starting RNC in Pool reconstruction. For details on BSC6910
commissioning, see section 5.1BSC6910 Initial Configuration"5.1BSC6910 Initial
Configuration."
 If the transport network needs to be reconstructed during RNC in Pool reconstruction,
you are advised to reconstruct the transport network first and then reconstruct RNC in
Pool. Performing the two reconstructions at the same time may cause long service
interruption and hinder troubleshooting.
1.6 Prerequisites
The following are prerequisites for RNC in Pool reconstruction:
 RNC in Pool network design plan has been completed and finalized high-level design
(HLD)/low-level design (LLD) documents have been published. LLD documents are
mandatory. HLD documents are optional.

Copyright © Huawei
 Implementation Solution for RNC in Pool has been completed and finalized documents
of RNC in Pool reconstruction plan have been published.
 Standalone Configuration Management Express (CME) must be ready because RNC in
Pool reconstruction is CME wizard-based.
 All physical RNCs within one pool must be managed by the same U2000.
 The integrated CME must be provided for networks involved in the RNC in Pool
reconstruction.
 All physical RNCs under one logical RNC must be connected to the same CN node.
 If the Iu and Iur interface uses IP transmission, only Layer 3 networking supports user-
plane load sharing and node redundancy.
 The R and C version number of all physical RNCs within one pool during RNC in Pool
Load Sharing reconstruction must be the same. For example, an RNC of V100R018C10
can form a pool only with an RNC of V900R018C10/V100R018C10, but not with an
RNC of V900R017C01/V100R017C01.
 Names of all NodeBs within one pool during RNC in Pool Node Redundancy
reconstruction must be different.
 Node redundancy is not supported if the Iu-PS interface uses ATM transmission.
1.7 Precautions
1.7.1 U2000/CME/NEP
Both the Load Sharing deployment and Node Redundancy deployment involve the
following:
 The CME must be online to support synchronization of initialed configured global
parameters/NodeB parameters during RNC in Pool reconstruction and synchronization
of modified parameters during routine O&M. Ensure that the U2000 or CME is always
online.
 It is good practice to enable the feature WOFD-231800 RNC in Pool Management on the
iManager U2000 to provide a topology view for users to manage RNC in Pool. With this
feature, logical RNCs in the RNC in Pool networking can be monitored, including the
mapping between the master RNC and the overflow RNC, the mapping between the
master RNC and the backup RNC, the status of the load sharing, the status of the node
redundancy, and changes of NodeB control rights. In addition, control rights of NodeBs
can be switched over between the master RNC and the backup RNC manually.
 For details on applying for the U2000 license and license operation and maintenance, see
javascript:void(0);null.
Load Sharing deployment involves the following:
 If the user-plane load sharing function is enabled, the FTP relay server running on the
U2000 must be reachable to the OMUs of the master RNC and overflow RNC so that
user-plane tracing files can be uploaded to the U2000 server through FTP. To allow user-
plane tracing files to be uploaded to the LMT client through FTP, the LMT client must be
connected to the OMUs of the master RNC and overflow RNC. If the U2000 functions
as an agent for the LMT, the load sharing function becomes unavailable.

Copyright © Huawei
1.7.2 Neighboring NEs

Figure 1.1 Network connection for involved UEs
Impacts of RNC in Pool on the neighboring NEs are as follows:

 For the Nastar
The Nastar delivers machine-machine commands to NEs, and collects logs and
performance data from NEs and processes such data. Therefore, the Nastar must be able
to identify the logical topology of RNC in Pool, deliver commands to the master RNC
and the overflow RNC separately, and collect required data. Currently, the preceding
requirements for the Nastar have been met and the Nastar can be connected to RNC in
Pool networkings.
 For the Event-Based Counter (EBC)
The EBC is responsible for collecting logs from NEs. Therefore, the EBC needs to be
able to identify RNC in Pool logical networkings, and resolve and aggregate data
according to the logical RNC.
Currently, the preceding requirements for the EBC have been met and the EBC can be
connected to RNC in Pool networkings.

Copyright © Huawei
 For the performance surveillance (PRS)

The PRS provides visualization solutions of KPIs, KQIs, capacity, coverage, traffic
volume, and signaling, and collects and processes data sources involved. The PRS
collects data resources from the U2000. For data processing, the PRS needs to be able to
resolve and aggregate data according to the logical RNC.
Currently, the preceding requirements for the PRS have been met and the PRS can be
connected to RNC in Pool networkings.
 For the NE information collector (NIC)
The NIC collects information of physical NEs and therefore the RNC in Pool has no
impact on the NIC.
 For the Trace Server
None.
1.7.3 NE Licenses
BSC6900
 RNC in Pool does not affect BSC6900 license file application.
A BSC6900 supports only one type of license file containing both the software license
control items and hardware license control items, and is under the control of only one
license file.
If the BSC6900 works as the master RNC, the license application method is the same as
that for BSC6900s not using RNC in Pool. Users need to apply for the license file by
using the software electronic serial number (ESN), a string of 40 characters consisting of
the RNC ID, mobile country code (MCC), and mobile network code (MNC).
BSC6910
 RNC in Pool affects the BSC6910 license file application.
A BSC6910 supports two types of license files: the license file containing both the
software license control items and hardware license control items, and the license file
containing only hardware license control items. One BSC6910 is under the control of
either and only one of the two types of license files.
If the BSC6910 requires a license file containing both the software license control items
and hardware license control items, the application method is the same as that for
BSC6910s not using RNC in Pool. Users need to apply for such a license file by using a
software ESN of the master RNC, a string of 40 characters consisting of the RNC ID,
MCC, and MNC.
If the BSC6910 requires a hardware item license file, users need to apply for such a
license file by using a hardware ESN. The ESN is the bar code in the electronic tag of
the BSC6910 main processing subrack (MPS), a string of 20 characters.
RNC in Pool affects the BSC6910 license file application. For detailed impacts, see the red
text listed in Table 1.1.
Table 1.1 License file types corresponding to different RNC in Pool networkings
Feature Name Master RNC Overflow/Backup
RNC
BSC6900 BSC6910 Only as

Overflow/Backup

Copyright © Huawei
Feature Name Master RNC Overflow/Backup

RNC
RNC
Load Sharing License file License file Hardware item
containing both the containing both the license file
software license software license
control items and control items and
hardware license hardware license
control items control items
Node Redundancy License file License file Hardware item
containing both the containing both the license file
software license software license
Load License file License file Hardware item
Sharing+Node containing both the containing both the license file
Redundancy software license software license
 If a BSC6910 functions as both the master and overflow/backup RNCs, multiple orders
on the flexnet operations (FNO) system need to be bound with the software ESN of the
master RNC to generate one license file.
 If a new master RNC is added for an existing overflow/backup RNC, users need to apply
for a license file (containing both the software and hardware license control items) using
the ESN consisting of the RNC ID, MCC, and MNC of the master RNC and then replace
the original license file with the new license file. To produce a final license file, users
need to replace the original hardware license ESN with the software license ESN, and
the license file must contain both the original hardware license control items and
software license control items.
 For each logical RNC in a pool, the corresponding software license control items
required must be applied for by using the ESN of the master RNC. After the application
is complete, such license control items are synchronized to the overflow/backup RNC
over the Iur-p interface.
 For the newly added license application rules, see related feature deployment sections in
this document.
For details on license application and license O&M, see Guide to Application for
BSC6900&BSC6910 License, in which section 3.1.9 "RNC in Pool License (from RAN15.0
Onwards)" is closely related.
1.7.4 NEs
following:
 Each physical RNC can function as the master RNC of only one logical RNC.
 Each logical RNC can be mapped to a maximum of two physical RNCs.

Copyright © Huawei
 The Iur-p interface requires a multi-core IP interface board. For example, the BSC6900
must be configured with an IP interface board GOUc, GOUe, or FG2c to support the Iur-
p interface; The BSC6910 must be configured with an IP interface board GOUc, GOUe,
FG2c, or EXOUa to support the Iur-p interface.
 When the feature WRFD-150240 RNC in Pool Multiple Logical RNCs is used on a
BSC6910 functioning as an overflow RNC:
The total number of NodeBs and cells under the master RNC must not exceed 10,000
and 20,000, respectively.
The total number of neighboring RNCs and cells under the neighboring RNCs must not
exceed 278 and 46,080, respectively.
The total number of both the GSM neighboring cells and LTE neighboring cells must not
exceed 57,600.
The total number of SMLCCELL and SMLCEXT3GCELL MOs must not exceed
20,000.
If any of these items exceed the specifications, services will be affected, and ALM-22243
Excessive Synchronization Data for RNC in Pool Load Sharing is reported.
 When the feature WRFD-150240 RNC in Pool Multiple Logical RNCs is applied on a
BSC6910 functioning as an overflow RNC, the number of adjacent Iub nodes supported
by the overflow RNC depends on its physical specifications.
 If the master RNC is configured with an SAU or GCG board, the overflow RNC must
also be configured with an SAU or GCG board to ensure that the overflow RNC supports
the same function as the master RNC does.
 If user-plane load sharing is enabled and the master RNC is configured with an NIU or
UUEP logic processing unit, the overflow RNC must also be configured with an NIU or
UUEP logic processing unit.
Node Redundancy deployment involves the following:
 When the feature WRFD-150240 RNC in Pool Multiple Logical RNCs is used on a
BSC6910 working as a backup RNC, the sum of the number of NodeBs under the master
RNC and the number of dual-homed NodeBs under the backup RNC must not exceed
10,000. The sum of the number of cells under the master RNC and the number of cells
under the dual-homed NodeBs served by the backup RNC must not exceed 20,000.
Otherwise, configurations for the extra NodeBs or cells on the BSC6910 will fail.
 Node redundancy can be triggered manually or automatically. The automatic mode is
supported only in UO mode.
 In GU mode, one BSC6910 can be the backup RNC for only one BSC6910. To support
node redundancy, the BSC6910 in GU mode must be enabled with RNC in Pool Node
Redundancy and BSC Node Redundancy. For details about how to enable BSC node
redundancy, see BSC Node Redundancy Feature Parameter Description. After a NodeB
control switchover is performed, secondary-homed base stations under the BSC6910 in
GU mode cannot use dynamic spectrum sharing.
 If an SAU, NIU, DEUa, or GCG board is configured and used on the master RNC, the
same type of board must be configured on the backup RNC to ensure that related
functions and features can recover when services are switched over to the backup RNC.
 Upon detecting different R or C version numbers between the master and backup RNCs,
the CME does not synchronize data between the RNCs. If this happens and data
configuration is required, users need to enable the manual data configuration function on
the backup RNC and manually perform data configuration on the master RNC and

Copyright © Huawei
backup RNC separately. Ensure that data configuration is consistent between the master
RNC and backup RNC.
 The GMT time on the two physical nodes under each logical RNC must be consistent. To
achieve this, you are advised to use the same Simple Network Time Protocol (SNTP)
server on the two physical nodes. (You can run the LST SNTPCLTPARA command to
set the SNTP server.) If the GMT time on the two nodes is different, set the time of the
backup RNC to the same as that of the master RNC.
1.7.5 Interfaces and Transmission

following:
 One Iur-p interface can be configured with a maximum of 400 control-plane Iur-p links.
 RNC in Pool requires newly configured Iur-p interfaces. The Iur-p interface supports IP
transmission and Layer 3 networking only.
 The transmission type for the Iu/Iur user plane of the overflow RNC must be the same as
that on the master RNC. If ATM transmission is used, transmission signaling links must
be configured.
 The Iub user plane of the overflow RNC supports only IP transmission.
 When user-plane load sharing is enabled, each neighboring RNC of a pool must have a
unique combination of a network identifier (NI) and originating point code (OPC).
 Interface transmission delay affects control-plane and user-plane performance.
Therefore, Iur-p transmission for the feature WRFD-150211 RNC in Pool Load Sharing
must meet the following requirements: the unidirectional delay over the Iur-p interface
must be less than or equal to 10 ms, the jitter must be less than or equal to 5 ms, and the
packet loss rate must be less than 0.01%.
Node Redundancy deployment involves the following:
 The Iu interface between the master RNC and the CN and that between the backup RNC
and the CN must use the same transmission type. Either IP transmission or ATM
transmission can be used.
 If the BSC6910 uses the feature WRFD-150240 RNC in Pool Multiple Logical RNCs,
multiple master RNCs are backed up by the BSC6910. In this case, all master RNCs
must use the same transmission type on the Iu interface. Either IP or ATM transmission
can be used.
 The Iur interface between the master RNC and neighboring RNCs and that between the
backup RNC and neighboring RNCs must use the same transmission type. Either IP
transmission or ATM transmission can be used.
 When the feature WRFD-150240 RNC in Pool Multiple Logical RNCs is used on the
BSC6910, the ATM-based Iur interface becomes unavailable if the NodeB control rights
of both the two logical RNCs are switched over to the same backup RNC.
 If a BSC6910 functions as the backup RNC for multiple master RNCs, the NIs for the
assisted originating signaling points (OSPs) of the master RNCs must be the same and
the NI for the assisting OSP of the BSC6910 must be the same as that for the assisted
OSPs of the master RNCs.
 The interface transmission performance affects the messages used to negotiate the
control rights between the master RNC and the backup RNC. Therefore, Iur-p
transmission for the feature WRFD-150212 RNC in Pool Node Redundancy must meet
the following requirements: the unidirectional delay over the Iur-p interface must be less

Copyright © Huawei
than or equal to 100 ms, the jitter must be less than or equal to 50 ms, and the packet loss
rate must be less than 1%.
1.7.6 NBI Interconnection

This section describes how to adjust parameter configurations for logical RNCs involved in
the RNC in Pool feature through northbound interfaces (NBIs) on the CME. However, this
feature cannot be activated through NBIs on the CME. The non-logical RNC configurations
can be adjusted in the same way as for RNCs not involved in this feature. Specifically, non-
logical RNCs are configured on physical RNCs separately.
The CME supports configuration data import and export through NBIs. The following figure
illustrates how to adjust configurations for logical RNCs.
 If the master RNC has the NodeB control, set SyncDataCfgMode(UMTS

BSC6900,UMTS BSC6910) to AutoSync for the backup RNC. In this case, northbound
configuration import allows logical RNC configurations to be adjusted on the master
RNC only. During northbound configuration export, the CME may work in either of the
following ways:

Copyright © Huawei
1. The CME does not filter northbound configurations of logical RNCs on the backup
RNC. Instead, the upper-layer NMS filters such data.
2. The CME automatically filters northbound configurations of logical RNCs on the backup
RNC. In this case, FilterRncInPoolData must be set to ON on the CME. For details
about how to set this parameter, see iManager U2000-CME Northbound Interface
Specification. The CME filters only data that needs to be synchronized. For details about
such data, see chapter 11 "Data Synchronization Information for RNC in Pool" of RNC
in Pool Feature Parameter Description.
 If the backup RNC has the NodeB control, run the MML command SET
URNCPOOLCFGCTRL and set SyncDataCfgMode(UMTS BSC6900,UMTS
BSC6910) to ManualCfg for the backup RNC after triggering an RNC switchover. In
this case, northbound configuration import allows logical RNC configurations to be
adjusted on the backup RNC, and logical RNC configuration data will be exported for
both the master and backup RNCs.
When the master RNC recovers, it regains the NodeB control. If the user expects to
synchronize parameter configurations on the backup RNC to the master RNC, the user must
manually synchronize configuration data from the backup RNC to the master RNC using the
CME before the NodeB control switchover. For the detailed procedures, see section
5.6Manually Synchronizing RNC in Pool Data."After manual data synchronization is
complete, run the SET URNCPOOLCFGCTRL MML command with
SyncDataCfgMode(UMTS BSC6900,UMTS BSC6910) set to AutoSync for the backup
RNC.
1.8 Related Documentation

 RNC in Pool Feature Parameter Description
 Technical Guide of UMTS RNC in Pool Network Design
 RNC in Pool Configuration Principle
 Guide to Application for BSC6900&BSC6910 License
 iManager U2000 MBB (Originally Referred to As M2000) V200 License Application
Guide
 javascript:void(0);null
 BSC6900 UMTS Initial Configuration Guide
 BSC6910 UMTS Initial Configuration Guide
To obtain the preceding documents of different versions, visit http://support.huawei.com.

Copyright © Huawei
Engineering Guidelines for Load SharingEngineering
RNC in Pool Reconstruction Guide (RAN18.1) Guidelines for Load Sharing
2 Engineering Guidelines for Load Sharing
2.1 Typical Scenarios

2.2 Deployment Process
2.3 Preparation
2.4 Procedures for Load Sharing Reconstruction
2.5 Acceptance
2.6 Procedures for Rolling Back Load Sharing

This section describes three typical scenarios, any combination of which may also be
considered.
2.1.1 Scenario 1: N Master RNCs and An Overflow RNC Carrying

Multiple Logical RNCs
 In this scenario, N takes the value of 1, 2, 3, 4, 5, or 6. This section uses the N value of 3 as an
example to describe load sharing configurations.
 The BSC6910 functioning as an overflow RNC can be either a newly deployed RNC or a legacy
RNC.
 If multiple RNCBASIC MOs are configured on a BSC6910 working as an overflow RNC, the
feature WRFD-150240 RNC in Pool Multiple Logical RNCs must be used and the corresponding
license is required.
 Load Sharing supports control-plane load sharing (CP_SHARE) and user-plane load
sharing (UP_SHARE). The control-plane load sharing function can be activated
independently. The user-plane load sharing function is by default bound with the control-
plane load sharing function. Therefore, in the following sections, "UP_SHARE"
indicates "CP&UP_SHARE."
Three master RNCs (P_RNC1, P_RNC2, and P_RNC3) and one overflow RNC (P_RNC4)
form a pool of multiple logical RNCs. The overflow RNC for the three master RNCs is
carried on the same physical RNC, as shown in Figure 1.2

Copyright © Huawei
Figure 1.2 Three master RNCs and one overflow RNC carrying multiple logical RNCs
Scenario 1 can be divided into subscenarios, as listed in the following table.
Subsc Before Before Load After After

enari Deployme Sharing Load Deployme
o No. nt Activation Shari nt
ng
Activ
ation
RNC Number of Attribute of

RAT Master Logical RNCs
RNCs
2.1.1.1 Non-RNC- UO N NO_SHARE UO
in-Pool
scenarios
2.1.1.2 Non-RNC- UO N NO_SHARE UO
in-Pool
scenarios
2.1.1.3 Non-RNC- UO N CP_SHARE UO
in-Pool
scenarios
2.1.1.4 Non-RNC- UO N UP_SHARE UO
in-Pool
scenarios
2.1.1.5 Load UO N CP_SHARE UO
Sharing

Copyright © Huawei

ng
Activ
ation
(CP):
N
BSC6900/B
SC6910
(master) + 1
BSC6910
(overflow)
If the logical RNC attribute changes after Load Sharing is activated, the attributes before and after the
activation are highlighted. The number of master RNCs changing from N to M indicates the
specification changes of logical RNCs. For example, a 2+1 pool changes to a 3+1 pool.
2.1.2 Scenario 2: Two Physical RNCs Carrying Two Logical RNCs
 In this scenario, the two physical RNCs must be BSC6910s.

 The two physical RNCs must be enabled with the feature WRFD-150240 RNC in Pool
Multiple Logical RNCs and provided with the license for this feature.
 Load Sharing supports control-plane load sharing (CP_SHARE) and user-plane load
sharing (UP_SHARE). The CP_SHARE function can be activated independently. The
UP_SHARE function is by default bound with the CP_SHARE function and therefore
CP_SHARE will be automatically activated when CP_SHARE is activated. Therefore, in
the following sections, "UP_SHARE" indicates "CP&UP_SHARE."
Two physical RNCs form a pool carrying two logical RNCs (L_RNC1 and L_RNC2). Each
physical RNC (P_RNC1 or P_RNC2) functions as the master RNC for one logical RNC and
as an overflow RNC for another logical RNC, as shown in Figure 1.3

Copyright © Huawei
Figure 1.3 Two physical RNCs carrying two logical RNCs

ng
Activ
ation

RNCs
2.1.2.1 Non-RNC- UO 2 NO_SHARE UO
in-Pool
scenarios
in-Pool
scenarios
2.1.2.3 Load UO 2 CP_SHARE UO
Sharing
(CP):
1 BSC6910
(master+over
flow) + 1
BSC6910
(master+over
flow)
activation are highlighted.

Copyright © Huawei
2.1.3 Scenario 3: Four BSC6900s and Two BSC6910s Carrying

 In this scenario, P_RNC1, P_RNC2, P_RNC3, and P_RNC4 are BSC6900s; P_RNC5 and P_RNC6
must be BSC6910s.
 The BSC6910 functioning as an overflow RNC can be either a newly deployed RNC or a
legacy RNC.
 In this scenario, the two BSC6910s functioning as the overflow RNCs must be enabled
with the feature WRFD-150240 RNC in Pool Multiple Logical RNCs and be provided
with the license for this feature.
Four BSC6900s and two BSC6910s form a pool of multiple logical RNCs, as shown in Figure
1.4.
Figure 1.4 Four BSC6900s and two BSC6910s carrying multiple logical RNCs

ng
Activ
ation

RNCs
in-Pool

Copyright © Huawei

ng
Activ
ation
scenarios
in-Pool
scenarios
2.1.3.3 Load UO 6 CP_SHARE UO
Sharing
(CP):
4 BSC6900s
+2
BSC6910s
activation are highlighted.

2.2.1 Reconstruction Process
This section describes the process of RNC in Pool Load Sharing reconstruction.

Copyright © Huawei
Figure 1.5 Process of RNC in Pool control-plane load sharing reconstruction
Figure 1.6 Estimated time for RNC in Pool control-plane load sharing reconstruction

Copyright © Huawei
Figure 1.7 Process of RNC in Pool user-plane load sharing reconstruction

Copyright © Huawei
Figure 1.8 Estimated time for RNC in Pool user-plane load sharing reconstruction
 During Iur-p interface reconstruction, independent planning of Iur-p user-plane configurations is

required if user-plane load sharing is activated. However, it is unnecessary if only control-plane load
sharing is activated.
 Iu/Iur interface reconstruction involves operations on the peer CN and neighboring
RNCs. Therefore, ensure that O&M personnel of the peer nodes are ready to work.
 During the preceding reconstruction processes, the project duration can be adjusted as
required. It is recommended that reconstruction of different interfaces be performed
separately. It is also recommended that interface reconstruction be performed in low-
traffic hours because reconstruction will affect ongoing services. However, projects may
differ in time plan. If certain interfaces cannot be reconstructed during low-traffic hours,
you are advised to ensure that Iu interfaces are reconstructed during low-traffic hours.
Reconstruction time for other interfaces can be adjusted as required.
 During the preceding reconstruction processes, horizontal operations can be performed
concurrently. Vertical operations must be performed serially. If logical RNC
reconstructions are performed concurrently, you are advised to also reconstruct the Iur-p
interfaces of these RNCs concurrently.
 Standalone CMEs can provide one-stop wizard-based services during RNC in Pool
reconstruction. Therefore, you are advised to use the standalone CME to configure
reconstruction scripts. Traditionally, only Iub interfaces are reconstructed on standalone
CMEs and other interfaces are reconstructed using MML commands. For details about
related operations, see RNC in Pool Feature Parameter Description.

Copyright © Huawei
 Required time listed in the preceding figures is for reference only. Operation personnel
need to estimate required time based on site conditions. Section 5.7X Project
Deployment Solution"5.7X Project Deployment Solution" is an example.
2.2.2 Rollback Procedure

2.2.2.1 Deactivation
After Load Sharing is enabled, you can roll back the feature by deactivating it due to
problems, such as exceptions, less-than-expected benefits, or other O&M issues. Activate the
feature again after problems are resolved.
2.2.2.2 Networking Rollback

If RNC in Pool rollback is required for certain reasons, roll back the RNC in Pool network to
a non-RNC-in-Pool network by referring to the procedure shown in Figure 1.9.

Copyright © Huawei
Figure 1.9 Networking rollback for Load Sharing
2.3 Preparation
 If additional equipment or boards are required before the reconstruction starts, ensure
that the required hardware has been commissioned.

Copyright © Huawei
 Ensure that the cables and optical fibers required for the interface transmission
reconstruction have been installed and commissioned.
 Ensure that the data of legacy RNCs has been collected and backed up before
reconstruction.
2.4 Procedures for Load Sharing Reconstruction

This section describes the detailed procedures for Load Sharing reconstruction. The following
steps apply to all scenarios, unless otherwise specified.
Step 1 Prepare required license files.
For details, see section 2.4.1Preparing License Files"2.4.1Preparing License Files."
Step 2 Activate the licenses.
For details, see section 2.4.2Activating License Files"2.4.2Activating License Files."
Step 3 Back up data and prepare tools.
For details, see section 2.4.3Backing Up Data and Preparing Tools"2.4.3Backing Up Data and
Preparing Tools."
Step 4 Reconstruct Iur-p interfaces.
For control-plane load sharing, Iur-p reconstruction involves only signaling links. For user-
plane load sharing, Iur-p reconstruction involves both signaling links and user-plane
transmission.
1. Prepare Iur-p data.
For details, see section 2.4.4Configuring Iur-p Interfaces"2.4.4Configuring Iur-p
Interfaces."
2. Export the Iur-p configuration scripts.
For details, see section 2.4.7Exporting Configuration Scripts"2.4.7Exporting
Configuration Scripts."
3. Pre-activate the Iur-p configuration scripts.
For details, see section 2.4.8Pre-Activating Configuration Scripts"2.4.8Pre-Activating
4. Complete the installation and commission of cables and optical fibers required for Iur-p
transmission reconstruction and ensure such devices are available.
5. Activate Iur-p configuration data on both the master RNC and overflow RNC.
For details, see section 2.4.9Activating Configuration Scripts"2.4.9Activating
6. Run the DSP IURPLKS command or DSP IURPLNK command to check whether the
Iur-p signaling link is in the normal state.
7. Run the DSP ADJNODEPING command to check whether the Iur-p user plane is in the
normal state.
8. Check whether new alarms are reported on the master RNC and overflow RNC,
including ALM-21606 IURP Link Fault, ALM-21607 External Node Unreachable, and
ALM-21608 IURP Link Congestion. If new alarms are reported, clear them.
9. Check whether the Iur-p delay meets feature requirements.

Copyright © Huawei
For details on detecting the Iur-p delay, see section 5.2Iur-p Transmission Delay
Measurement Methods"5.2Iur-p Transmission Delay Measurement Methods."
10. Check whether the interface configuration needs to be rolled back due to exceptions. If
yes, perform rollback.
Step 5 Synchronize RNC-level data within a pool.
For details, see section 2.4.10Synchronizing the RNC-level Data Within a
Pool"2.4.10Synchronizing the RNC-level Data Within a Pool."After the synchronization is
complete, check whether new alarms are reported on the U2000, including ALM-706
Inconsistent RNC in Pool Configuration, ALM-20759 POOL License Information
Synchronization Failure, and ALM-22307 RNC in Pool Function Unavailable. If new alarms
are reported, clear them.
Step 6 (Mandatory only for user-plane load sharing) Reconstruct Iu/Iur interfaces.
1. Prepare Iu/Iur data.
For details, see section 2.4.5Configuring Iu/Iur User-Plane Data for the Overflow
RNC"2.4.5Configuring Iu/Iur User-Plane Data for the Overflow RNC."
2. Export the Iu/Iur configuration scripts.
3. Pre-activate the Iu/Iur configuration scripts.
4. Complete the installation and commission of cables and optical fibers required for Iu/Iur
5. Activate Iu/Iur configuration data on the overflow RNC.
6. Add the corresponding configuration data on the peer CN node or neighboring RNCs.
For details, see section 2.4.11Performing CN and Neighboring RNC
Interconnection"2.4.11Performing CN and Neighboring RNC Interconnection."
7. Run the SET TNSOFTPARA command with IuIurDIPSynSw set to ON on both the
master and overflow RNCs to turn on the Iu/Iur destination IP (DIP) synchronization
switch.
8. Run the CHK SERINTEG command on the overflow RNC to check whether the Iu and
Iur interface configuration is complete.
9. Check whether the Iu/Iur user plane is reachable on the overflow RNC and the peer CN
and neighboring RNCs.
including ALM-21392 Adjacent Node IP Address Ping Failure. If new alarms are
reported, clear them.
Step 7 (Mandatory only for user-plane load sharing) Reconstruct Iub interfaces.
1. Prepare Iub data.
For details, see section 2.4.6Configuring Iub User-Plane Data for the Overflow
RNC"2.4.6Configuring Iub User-Plane Data for the Overflow RNC."

Copyright © Huawei
2. Export the Iub configuration scripts.

3. Pre-activate the Iub configuration scripts.
4. Complete the installation and commission of cables and optical fibers required for Iub
5. Activate Iub configuration data on the overflow RNC and NodeBs awaiting
configuration.
6. Run the SET TNSOFTPARA command with IubDIPSynSw set to ON on the master
RNC to turn on the DIP synchronization switch.
Step 8 Activate Load Sharing. For details, see section 2.4.12Activating Load
Sharing"2.4.12Activating Load Sharing."
Step 9 Perform reconstruction acceptance. For details, see 2.5Acceptance"2.5Acceptance."
----End
2.4.1 Preparing License Files

 To enable the RNC in Pool Load Sharing feature (including both control-plane load
sharing and user-plane load sharing), the corresponding license control items listed in the
following table must be applied for. The control item is a software license item and
therefore you only need to apply for it in the license file of the master RNC of the
corresponding logical RNC.
Feature Feature Control Control NE License Sales
ID Name Item ID Item Allocation Unit
Name for
Multiple
Operators
WRFD- RNC in Pool LQW1RP RNC in BSC6900 License Per 500

150211 Load LSRES Pool Load BSC6910 control active user
Sharing Sharing items that
(per cannot be
Active configured
User) based on
operators
 If the overflow RNC uses the feature WRFD-150240 RNC in Pool Multiple Logical
RNCs, you also need to apply for the following corresponding license control items. The

Copyright © Huawei
control item is a hardware license item and therefore you need to apply for it in the
license files of the corresponding physical nodes enabled with the feature WRFD-
150240 RNC in Pool Multiple Logical RNCs.
Name for
Multiple
Operators
WRFD- RNC in Pool LQW1RP RNC in BSC6910 License per Logic

150240 Multiple MLRRES Pool control RNC
Logical Multiple items that
RNCs Logical cannot be
RNCs (per configured
RNC) based on
operators
The number of license control items of WRFD-150240 RNC in Pool Multiple Logical RNCs equals the
number of logical RNCs minus one on a BSC6910. Scenario 1 is used as an example. In Figure 1.2
 Consider the content listed in the following table if only the backup license file needs to
be applied for:
BOM Code License ID License Name License
Application
82203572 LQW1HWCL03 RNC Throughput Mandatory if the

Hardware Capacity user-plane load
(per 50Mbps) sharing function is
enabled
82203573 LQW1HWCL04 RNC Active User Mandatory if the
Hardware Capacity control-plane or
(per 1000 Active user-plane load
Users) sharing function is
enabled
82203729 LGW1DPIHC02 Network Optional unless the
Intelligence NIU board is used
Processing
Throughput (per
50Mbps)
82204003 LQW1RPMLRRES RNC in Pool Optional unless the
Multiple Logical feature WRFD-
RNCs (per RNC) 150240 RNC in Pool
Multiple Logical
RNCs is used
81201592 LQW1UPCPDS01 RNC User Plane and Optional unless the
Control Plane feature WRFD-
Dynamic Sharing 141201 RNC User
Plane and Control
Plane Dynamic

Copyright © Huawei
BOM Code License ID License Name License

Application
Sharing is used
 When planning the resource license capacity for the BSC6910, you need to consider the
new service volume that the BSC6910 is going to share as an overflow RNC. For details,
see RNC in Pool Configuration Principle.
 When a network is shared by multiple operators, the features WRFD-150211 RNC in
Pool Load Sharing and WRFD-150240 RNC in Pool Multiple Logical RNCs cannot be
used exclusively for one operator. If both the features are used, they must be used for all
the operators configured on an RNC. Therefore, the preceding license control items are
not operator-specific and the license usage of the primary operator indicates the license
usage of all operators.
The following figures show the logic of processing license files of the master RNC and
overflow RNC in different scenarios.
Figure 9.1 shows the logic of processing the license file of the master RNC.

Copyright © Huawei
Figure 9.1 Logic of processing the license file of the master RNC
Figure 9.2 shows the logic of processing the license file of the overflow RNC.

Copyright © Huawei
Figure 9.2 Logic of processing the license file of the overflow RNC
Logical attributes corresponding to physical nodes in different scenarios are listed in the
following tables.
The following table lists the logical attributes corresponding to the physical nodes of scenario
1 shown in Figure 1.2.
Physical RNC Corresponding Logical Attribute

During License File Processing
P_RNC1 Master RNC

P_RNC2 Master RNC
P_RNC3 Master RNC
P_RNC4 Overflow RNC

Copyright © Huawei

P_RNC1 Master RNC+Overflow RNC


P_RNC1 Master RNC

P_RNC2 Master RNC
P_RNC3 Master RNC
P_RNC4 Master RNC
 When an RNC is newly deployed, you can download the esnextract.exe program from
http://support.huawei.com/ and run it in offline mode on the PC to calculate the ESN. A software
ESN is generated with resource items RNC ID, MCC, and MNC. Hardware ESNs are obtained from
the electronic labels of MPSs. You can also run the LST ESN command to query hardware ESNs in
online mode when the SCU boards of MPSs are running normally. (A hardware ESN is a string of 20
characters with the service ID being NULL.)
 If you need to add the master RNC for an overflow RNC after the deployment of Load
Sharing, see section 1.7.3NE Licenses" for detailed operations.
 Application for licenses other than those of the feature RNC in Pool is not provided here
and the application rules are the same as those for licenses of non-RNC-in-Pool
networkings.
 If license control items Network Intelligence Processing Throughput (per 50Mbps) and
RNC User Plane and Control Plane Dynamic Sharing are required, apply for them by
following the processing principles for other control items of the backup license file.
2.4.2 Activating License Files

This section describes how to activate license files.
 Prepare required license files of the master RNC and overflow RNC and active them
separately by following the instructions provided in section 2.4.1Preparing License
Files." Perform the following steps to activate the license files on the NE side:
Step 1 Before installing the RNC license, check the license file name.

Copyright © Huawei
 The length of the license file name must not exceed 31 bytes.
 The recommended format of license file name is Office No._YYYYMMDD.dat (for
example, AlexBsc1_20070201.dat) and the file name must be unique.
Step 2 On the WebLMT, run the DLD LICENSE command to download the license file to an NE.
The operation GUI and command output are displayed as follows:
Step 3 On the WebLMT, run the LST LICENSE command to query the items specified in the
license file.
Check whether the ESN specified in the license file is the same as that of the NE. Check the
command output to determine whether the license expires and whether the function items
specified in the license file are the same as the function items that have been applied for. If
they are not the same, apply for a new license file. Alternatively, you can use the License Tool
to check the license file offline.
Step 4 On the WebLMT, run the ACT LICENSE command to activate the specified license file.
----End
 Operations for software license files including to activate them, to forcibly revoke them,
and to enable them to enter the emergency state can be performed on only the master
RNC. After an operation is complete, configurations will be synchronized to the
overflow RNC over the Iur-p interface.
 Operations for hardware license files of BSC6910s including to activate them, to forcibly
revoke them, and to enable them to enter the emergency state must be performed on the
corresponding physical RNCs.
2.4.3 Backing Up Data and Preparing Tools

Users can export NE configuration data files using the LMT of the NE. Alternatively, users
can use the integrated CME to export configuration data files of NodeBs and then import the
data into the standalone CME.
Step 1 Obtain configuration data files of NEs including the master RNCs, the overflow RNCs, and
the NodeBs awaiting reconstruction.
Table 1.1 lists the methods for obtaining configuration files of different NEs.
Table 1.1 Methods for obtaining NE configuration data

NE Type File type Configuration Tool Procedure
Controller BCP files WebLMT 1. Log in to the WebLMT client.

2. Run the EXP CFGBCP
command to export the BCP
files.

Copyright © Huawei
You can specify the file save

path and file name. If you do not
specify them, you can check the
BCP file save path and file name
in the command output.
3. Click File Manager on the menu
bar.
The File Manager window is
displayed.
4. Select a file save path in the
directory tree in the left pane,
and select the required BCP files
in the file list in the right pane.
5. Click Download and specify the
local target folder in the
displayed dialog box.
6. When the progress is 100%, the
download is complete.
NodeB XML files CME For detailed operations on the
integrated CME, see "Exporting NE
Configuration Data" in CME
Product Documentation.
Step 2 Start the standalone CME, and then choose Data Management > Import NE Files in the
CME–CME Express window to add an NE file, as shown in Figure 2.1.
Figure 2.1 Starting the standalone CME and adding an NE file
Step 3 Select an NE configuration file from the files exported at step 1, as shown in Figure 3.1

Copyright © Huawei
Figure 3.1 Selecting an NE configuration file to be added
Before starting import, you can add the master RNC, overflow RNC, and NodeBs to Selected
NEs.
Step 4 Click OK to import the selected NE configuration files.
About 3 to 4 minutes are required to import the configuration file of an NE of different
version. After data is imported, the page is displayed, as shown in Figure 4.1

Copyright © Huawei
Figure 4.1 Successful data import
----End
2.4.4 Configuring Iur-p Interfaces

2.4.4.1 Control-Plane Load Sharing
Step 1 Choose UMTS Application > RNC in Pool Configuration > RNC in Pool Commission on
the standalone CME.
Step 2 In the displayed dialog box, select CP load sharing only and click OK.
The dialog box for importing Iur-p data is displayed, as shown in Figure 2.1.

Copyright © Huawei
Figure 2.1 Importing Iur-p data
Step 3 In the displayed dialog box, click the hyperlink Get the Template for Iur-p…
Thedialog box for obtaining the Iur-p template is displayed, as shown in Figure 3.1.
Figure 3.1 Selecting the Iur-p template
Step 4 Specify BSC6910 version and its corresponding Master RNC count (An RNC ID indicates a
logical master RNC.)as well as BSC6900 version and its corresponding Master RNC count,
select CP load sharing, and select the path to which the template is to be exported. Click
Next.

Copyright © Huawei
The required manged object classes (MOCs) are displayed and the quantities of the MOCs are
calculated, and then the quantity of each MOC of a single logical RNC for the Iur-p template
is displayed, as shown in Figure 4.1.
Figure 4.1 Setting the number of MOCs of a single logical RNC for the Iur-p template
The following shows how to calculate the number of logical RNCs:

 If N BSC6900s and one BSC6910 are pooled, the master RNC must be a BSC6900. Therefore, the
number of logical RNCs to be activated equals the number of BSC6900s, that is, N.
 If M BSC6910s and one BSC6910 are pooled, the M BSC6910s function as the master RNCs and
the BSC6910 can function only as the overflow or backup RNC. Therefore, the number of logical
RNCs to be activated equals the number of master RNCs, that is, M.
 If M BSC6910s and one BSC6910 are pooled and the BSC6910 also functions as the master RNC
(for example, scenario 3), the number of logical RNCs to be activated equals the number of
BSC6910s, that is, M + 1.
Step 5 Adjust the number of MOCs and objects.

Generally, the default number of MOCs and objects can be used for most scenarios. However,
the number of MOCs and objects needs to be adjusted to accommodate transport networking
requirements at some specific sites. If Ethernet link aggregation groups exist, the ETHTRK
and ETHTRKIP MOs must be adjusted.
Step 6 After the adjustment is complete, click Next.
The hyperlink for the path of the customized Iur-p interface template is displayed.
Step 7 Click the hyperlink to find the exported Iur-p interface template.
Step 8 Click Finish in the dialog box to close the sub-wizard for customizing the Iur-p interface
template.
Step 9 Fill the common RNC-in-Pool information into CommonData Sheet.

Copyright © Huawei
Such common information must be planned in advance. Figure 9.1 shows an example.
Figure 9.1 Filling in common RNC-in-Pool information
 Only the Pool Name, the names of the master RNC and overflow RNC corresponding to the logical
RNC, and the NODE information must be provided. The CME during the import will automatically
generate URNCBASIC, URNCMAP, NODE, and EXTNODE information for the master RNC
and overflow RNC separately. Ensure that such information on both the RNCs are consistent.
 A minimum of configuration data supported will be generated by running ADD
URNCBASIC. Specifically, a large amount of configuration data will be generated in
the XML script.
Step 10 Fill the Iur-p link set (IURPLKS) in CommonData Sheet. Figure 10.1
Figure 10.1 Filling in the Iur-p link set
Only the information about Iur-p link set from the master RNC to the overflow RNC must be provided.
The CME will automatically generate the IURPLKS information on both the master and overflow RNC
side separately. Ensure that such information on both the RNCs are consistent.
Step 11 Fill the transmission information carried over the master Iur-p link set in the sheets
corresponding to the master and overflow RNCs.
Figure 11.1 shows an example.
Figure 11.1 Filling in transmission information carried over the Iur-p link set

Copyright © Huawei
The Iur-p link set can be carried over DEVIP, ETHIP, or ETHTRK. ETHIP is used as an example in
the preceding figure.
Step 12 After returning back to the the Import Iur-p Interface Data page, select the edited RNC in
Pool configuration data file and then click Next.
The import is complete.
----End
2.4.4.2 User-Plane Load Sharing

the standalone CME.
Step 2 In the displayed dialog box, select CP load sharing only and click OK.
The RNC in Pool activation wizard is displayed, as shown in Figure 2.1

Copyright © Huawei
Figure 2.1 RNC in Pool activation process
Step 3 Double-click the Import Iur-p Interface Data node in the wizard.

Copyright © Huawei
Step 4 Click the hyperlink Get the Template for Iur-p…

The dialog box for obtaining the Iur-p template is displayed, as shown in Figure 4.1.
select CP load sharing, and select the path to which the template is to be exported.
Step 6 Click Next.

Copyright © Huawei
The required manged object classes (MOCs) are displayed and the quantities of the MOCs are
calculated, and then the quantity of each MOC of a single logical RNC for the Iur-p template
is displayed, as shown in Figure 6.1.
Figure 6.1 Setting the number of MOCs of a single logical RNC for the Iur-p template

Step 7 Adjust the MOC and the number of objects.

template.

Copyright © Huawei
 Only the Pool Name, the names of the master RNC and overflow RNC corresponding to the logical
and overflow RNC separately. Ensure that such information on both the RNCs are consistent.
 A minimum of configuration data supported will be generated by running ADD URNCBASIC.
Specifically, a large amount of configuration data will be generated in the XML script.
Step 12 Fill the Iur-p link set (IURPLKS) in CommonData Sheet. Figure 12.1 shows an example.
Only the information about Iur-p link set from the master RNC to the overflow RNC must be provided.
The CME will automatically generate the IURPLKS information on both the master and overflow RNC
side separately. Ensure that such information on both the RNCs are consistent.
corresponding to the master and overflow RNCs.
Figure 13.1 shows an example.

Copyright © Huawei
Step 14 Fill the the Iur-p user-plane transmission information in the sheets corresponding to the
master and overflow RNCs.
Currently, the Iur-p user plane supports only the transmission resource pool. Figure 14.1
shows an example.
Figure 14.1 Filling in Iur-p user-plane transmission information
You can use the default value of the TRMMAP or TRMFACTOR index indicated by the Iur-p user-
plane ADJMAP. However, you are advised to manually specify the value of TRMMAP or
TRMFACTOR as required by the transport networking plan at a site and references such a value in the
table.
Step 15 After returning back to the the Import Iur-p Interface Data page, select the edited RNC in
Pool configuration data file and then click Next.
----End
2.4.5 Configuring Iu/Iur User-Plane Data for the Overflow RNC

The configuration described in this section is required only when user-plane load sharing
needs to be activated. For the overflow RNC, Iu user-plane transmission is mandatory,
whereas Iur user-plane transmission is optional. If the Iur user-plane transmission is not
configured, the Iur user plane of load sharing UEs will be carried over the Iur-p user plane
transmission and will be reachable to the neighboring RNC through the Iur interface of the
master RNC.
The general procedure for configuring the Iu/Iur user-plane data for the overflow RNC is as
follows: Export the Iu/Iur configurations of the master RNC as the basic data of the overflow
RNC, adjust the overflow-RNC-specific planning data, and import such data into the overflow
RNC. Perform the following operations:
Step 1 Double-click the Export IuIur Interface Data node in the RNC in Pool activation wizard.
The dialog box for exporting Iu/Iur data is displayed, as shown in Figure 1.1.

Copyright © Huawei
Figure 1.1 Selecting the mode for exporting Iu/Iur data
If Export by interface is selected, all Iu/Iur interface configurations of the physical RNC will be
exported. You are advised to select Export by interface when all the following conditions are met:
 An overflow RNC is newly deployed.
 All the Iu/Iur data of the master RNC will be used on the overflow RNC to create user-plane data.
Step 2 Specify the NE name and NE version of the master RNC, select UP load sharing, and
Export by filter mode, and then click Next.
The dialog box for selecting the object and interface type is displayed, as shown in Figure 2.1.
Figure 2.1 Selecting the Iu/Iur objects and interface types

Copyright © Huawei
If the master RNC is a BSC6900, you can click Peer IP Address of IP Path or Adjacent Node of IP
Pool Network to export data. Since the overflow RNC is a BSC6910, IPPATH will not be exported if
you export data from the Peer IP Address of IP Path tab page.
Step 3 Select the interface type to be exported in the Interface drop-down list, and add interface
objects to be exported on the Peer IP Address of IP Path tab page. If the Iu-CS or Iu-PS
interface is selected and only IP transmission is supported, switch to the Adjacent Node of IP
POOL Network tab page to select the corresponding interface objects.
Only one interface type can be exported at a time.
Step 4 After the interface objects to be exported are selected, click Next.
The dialog box for setting the path for saving the exported file is displayed, as shown in
Figure 4.1.
Figure 4.1 Setting the path for saving the exported file
Step 5 Set the path for saving the exported file and then click Next.
After the export is complete, the hyperlink for the path of the exported file is displayed, as
shown in Figure 5.1.

Copyright © Huawei
Figure 5.1 Hyperlink for the path of the exported file
Step 6 Click the hyperlink to find the exported file.

Step 7 Click Finish to close the export wizard.
Step 8 Configure the Iu/Iur user-plane data for the overflow RNC based on the exported file and by
following instructions described in Table 1.1
Table 1.1 Policies for configuring Iu/Iur user-plane data based on the exported data of the master
RNC
Transport Processing Based on the Involved MOs
Networking Mode Exported Data of the Master
RNC
IP transmission Based on the network plan of the DEVIP, ETHIP,

overflow RNC, add or update IPPOOL, IPPOOLIP,
physical-layer and data-link-layer and SCRIPRT
data and the planned transmission
resource pool data.
Based on the existing configuration ADJMAP and
data of the overflow RNC, check ADJNODE
whether the primary keys of objects
conflict. If the primary keys of some
objects conflict, adjust the values of
these primary keys.
Check whether common objects are TRMFACTOR and
configured on the overflow RNC. If TRMMAP
they are not configured, configure
them.
ATM transmission Update user-plane data based on the AAL2PATH and
network plan of the overflow RNC. AALRT

Copyright © Huawei
Transport Processing Based on the Involved MOs

Networking Mode Exported Data of the Master
RNC
Update control-plane data for MTP3LNK, MTP3LKS,

Q.AAL2 transmission based on the MTP3RT, N7DPC, and
network plan of the overflow RNC. SAALLNK
Based on the existing configuration ADJMAP and
data of the overflow RNC, check ADJNODE
whether the primary keys of objects
conflict. If the primary keys of some
objects conflict, adjust the values of
these primary keys.
configured on the overflow RNC. If TRMMAP
they are not configured, configure
them.
 In IP transmission mode, you need to fill common objects (such as DEVIP, ETHIP, or ETHTRK,
ETHTRKLNK, or ETHTRKIP) referenced by a transmission resource pool in the shared object
file. In ATM transmission mode, you need to fill the ATM traffic (ATMTRF) referenced by ATM
links in the shared object file.
 When configuring ADJNODE, you are advised to set DIP Automatic Acquisition Switch to
NO(No) and LogicRncShareMode to SHARE.
Step 9 Double-click the Import IuIur Interface Data node in the RNC in Pool activation wizard.
The Import IuIur Interface Data dialog box is displayed, as shown in Figure 9.1. For details
about how to import an Iu/Iur data file into the CME for configuring the corresponding data
for the overflow RNC, see "Importing an Iu/Iur Data Planning File" in CME Product
Documentation.

Copyright © Huawei
Figure 9.1 Importing Iu/Iur interface user-plane data
----End
2.4.6 Configuring Iub User-Plane Data for the Overflow RNC

needs to be activated. To generate a configuration script for batch processing, you need to
customize a summary data file. The general configuration procedure is as follows: Fill data in
the summary data file based on the Iub data of NodeBs to be reconstructed under the master
RNC, export the filled data as the basic data of the overflow RNC, adjust the basic data of the
overflow RNC, import the data to the overflow RNC, and import the summary data file to the
CME.
The CME provides the RNC in Pool Iub wizard. When you set information including feature
application scenarios, number of links, number of IP addresses, and IP addresses used by
links, the CME automatically customizes the related MOs, parameters, and reference
relationships in a summary data file. This simplifies customization and editing of the
summary data file. Perform the following steps:
Step 1 Customize a summary data file template.
1. Choose Advanced > Customize Summary Data File and select a summary template.
The dialog box for selecting a summary data file is displayed, as shown in Figure 1.1.

Copyright © Huawei
Figure 1.1 Selecting a summary template
2. Click Scenario on the toolbar.

3. In the displayed scenario list, select RNC in POOL Iub wizard.
The wizard for customizing a summary template is displayed.
4. On the first wizard page RNC in Pool Features to Be Enabled, select Enable only UP
load sharing, as shown in Figure 1.2.
5. Complete the follow-up object customization as prompted.

Copyright © Huawei
After finishing the steps as prompted, the CME outputs a customization report. This report contains
information such as the data input by the user, MOs, and parameter values automatically added by the
wizard, and data to be filled in by the user.
6. Save the summary template.
− Click Save as on the toolbar.
− Select a save path.
− Specify the name of the exported template file.
− Click Save.
The summary template is saved.
Step 2 Export Iub data of the NodeBs to be reconstructed.
1. Double-click the Export Iub Data Of Overflow/Backup RNC node in the RNC in Pool
activation wizard.
The Export Iub Data Of Overflow/Backup RNC dialog box is displayed, as shown in
Figure 2.1.

Copyright © Huawei
Figure 2.1 Exporting Iub data
2. Specify Master RNC name, select UP load sharing, select the NodeBs to be
reconstructed, and then click Next.
The dialog box for selecting an Iub summary template and a save path is displayed, as
Figure 2.2 Selecting an Iub summary template and a save path
3. Select the previously customized Iub summary template, specify the save path, and click
Next.
After the exporting is complete, the hyperlink for the path of the interface data file is
displayed.
4. Click Finish to close the wizard.
Step 3 Edit and import Iub data.

Copyright © Huawei
1. Based on the network plan of the overflow RNC, add or update physical-layer and data-
link-layer data and the planned transmission resource pool data in the exported Iub data
file, including ETHIP, DEVIP, SCRIPRT, IPPOOL, and IPPOOLIP.
2. Based on the existing RNC configurations, check whether the primary keys of objects
conflict, including ADJNODE, ADJMAP, and NodeB ID.
3. Double-click the Import Iub Data Of Overflow/Backup RNC node in the RNC in Pool
activation wizard.
The dialog box for importing Iub summary data file is displayed, as shown in Figure 3.1.
4. After the edited Iub data file is imported, click Next.
Figure 3.1 Importing NodeB data
5. Select the NodeBs to be reconstructed, deselect the Export scripts and Best Effort
check boxes, and click Next, as shown in Figure 3.2
The import is successful.

Copyright © Huawei
Figure 3.2 Selecting the NodeBs to be reconstructed
 If Best Effort is selected, the CME will import the dual-homed NodeBs with correct data only. To
ensure that all the dual-homed NodeBs of a batch are imported, you are advised to deselect Best
Effort.
 After the import is completed, the CME will automatically create UEXTNodeB on the
overflow RNC.
Step 4 Export the existing configurations of the NodeBs to be reconstructed.
1. Double-click the Export Base Station Bulk Configuration Data node in the RNC in
Pool activation wizard.
The dialog box for exporting Iub bulk configuration data is displayed.
2. Select the NodeB to be reconstructed, as shown in Figure 4.1

Copyright © Huawei
Figure 4.1 Exporting Iub bulk configuration data
3. Specify the management objects to be configured and the save path of the bulk
configuration file, and click Custom MOC, as shown in Figure 4.2
Figure 4.2 Customizing the objects to be exported
4. Import required MOs into the right pane.

To configure Iub user-plane data on the overflow RNC, the IP Path and IP Route MOs
are required (optional if Layer 2 networking is used).
5. Click Next.
The export is successful.
Step 5 Import the adjusted Iub bulk configuration file.

Copyright © Huawei
1. Modify the exported bulk configuration file. Pay attention to the IP Path and IP Route
MOs to be configured on the NodeB to the overflow RNC.
 The original exported data cannot be modified. You can only add new data.
 When configuring Iub user-plane for the overflow RNC, you only need to add the user-plane
configurations.
2. Double-click the Import Base Station Bulk Configuration Data node in the RNC in
The dialog box for importing Iub bulk configuration data is displayed.
3. Specify the save path of the bulk configuration file and upload the modified bulk
configuration file, and then click Next, as shown in Figure 5.1.
Figure 5.1 Selecting the Iub bulk configuration data to be imported
Select the NodeBs to be imported and then click Next, as shown in 2.4.6Configuring Iub
User-Plane Data for the Overflow RNC

Copyright © Huawei
Figure 5.2 Selecting the NodeBs to be imported
4. After the data file is imported, click Finish.

----End
2.4.7 Exporting Configuration Scripts

For details about how to export incremental scripts, choose CME Product Documentation >
CME Management > CME Guidelines > Script File Management > Exporting
Incremental Scripts from a Planned Data Area. The exported scripts include the scripts for
controllers and scripts for base stations. Note that the scripts for base stations are exported
only when user-plane load sharing is enabled.

Copyright © Huawei
Figure 5.3 Successful incremental script export
2.4.8 Pre-Activating Configuration Scripts

Step 1 Start Script Executor on the integrated CME, as shown in the following figure.
Step 2 Choose Project > Load Project to import controller scripts.

Copyright © Huawei
Step 3 Choose Project > Upload Project and in the displayed Confirm box, click Confirm.
Step 4 Right-click and choose Preactive Project to pre-activate the scripts.

To ensure that the controller script is correct, perform pre-activation checks.
If pre-activation errors are detected, perform the following: Modify the script, re-upload the
project, perform pre-activation and pre-activation checks till no error is found.
----End

Copyright © Huawei
2.4.9 Activating Configuration Scripts

Step 1 Right-click and choose Active Project to activate the script.
Step 2 Click Yes in the displayed dialog box shown in the following figure.
Step 3 If an error occurs, click Report in the main menu to check which management object instance
(MOI) runs improperly, as shown in the following figure.

Copyright © Huawei
If the number of NodeBs to be reconstructed is small, you can also use the WebLMT to activate
configuration scripts for NodeBs one by one. For detailed operations, see:
 BSC6900 UMTS LMT User Guide > BSC Maintenance > Batch Configuration
 3900 Series Base Station LMT User Guide > Maintaining the Base Station > Common
Maintenance Tasks > Extra Configuration File Transfer
----End
2.4.10 Synchronizing the RNC-level Data Within a Pool

Involved NEs: Overflow RNC
The following part describes how to perform the configuration.
For information about data to be synchronized, see chapter 11 "Data Synchronization
Information for RNC in Pool" in RNC in Pool Feature Parameter Description. During the
networking configuration, the CME will automatically detect the RNC in Pool networking
information and automatically create an RNC-level synchronization task. With the
synchronization task, initial data synchronization from the master RNC to the overflow RNC
can be manually triggered.
Step 1 Run the LST URNCPOOLCFGCTRL command on the overflow RNC to check whether the
synchronization mode is automatic. If not, run the SET URNCPOOLCFGCTRL command
with Data Synchronization Mode set to AutoSync(Auto Synchronization).
If you need to stop the data synchronization between the master RNC and the overflow RNC, set
SyncDataCfgMode to ManualCfg on the overflow RNC. In this situation, the automatic
synchronization task is automatically stopped, and therefore the modified data on the overflow RNC will
not be overwritten by the automatically synchronized data from the master RNC.
Step 2 On the menu bar of the U2000 client, choose CME > Current Area > Open Current Area
and then choose CME > UMTS Application > RNC in Pool Configuration > RNC in Pool
Configuration Management.
The RNC in Pool Configuration Management tab page is displayed, as shown in Figure
2.1. The synchronization task automatically created by the CME is displayed in the left
navigation tree. The synchronization tasks are named in the following format:
RncLvl_AutoSync_master RNC name (RNC ID)_overflow RNC name.
Figure 2.1 RNC in Pool Configuration Management tab page

Copyright © Huawei
If RNC configuration data fails to be synchronized in Current Area of the CME, the automatic
synchronization task will also fail. In this case, you can manually synchronize configuration data
between the master and backup RNCs by choosing CME > Current Area > Synchronize NE. Then, the
automatic synchronization task will be displayed on the refreshed task list.
Step 3 Select the automatic synchronization task and click to start data synchronization.
After the synchronization is complete, the data difference between the master RNC and
overflow RNC is displayed in the right pane, as shown in Figure 3.1.
Figure 3.1 Data comparison result of the automatic synchronization task
The "Type" column in the comparison result has two values:

 ValDiff: indicates that the parameter has different values on the master RNC and overflow/backup
RNC.
 MOIDiff: indicates that the parameter is set on either the master RNC or on the overflow/backup
RNC, not on both.
Step 4 Click the Sync button to synchronize the configuration data of the master RNC to the
overflow RNC.
After the data is successfully synchronized, the result is displayed in the Result dialog box, as
Figure 4.1 Successful data synchronization

Copyright © Huawei
Step 5 Click to open the Configuration Sync Switch dialog box and check whether Enable Auto
Sync is selected. If not, select it, as shown in Figure 5.1
Figure 5.1 Configuration Sync Switch dialog box
 Configuration Sync Switch is the general switch that controls automatic data synchronization for
RNC in Pool on the CME. This switch is a global switch and its setting takes effect on all the CME
clients.
 Configuration Sync Switch is set to ON when RNC in Pool is enabled for the first time. It is
recommended that this switch not be set to OFF after it is set to ON. You do not need to set this
switch again when RNC in Pool is enabled later.
 Before performing data synchronization, ensure that the parameter
SyncDataCfgMode(BSC6900,BSC6910) is set to AutoSync(Auto Synchronization) on the
overflow RNC.
You can run the SET URNCPOOLCFGCTRL command to set the parameter.
----End
2.4.11 Performing CN and Neighboring RNC Interconnection

needs to be activated.
Involved NEs: CN and neighboring RNC
 If IP transmission is used over the Iu/Iur interfaces, configure user-plane links between
the CN and the overflow RNC and between neighboring RNCs and the overflow RNC
on the CN and neighboring RNCs, respectively.
 If ATM transmission is used over the Iu/Iur interfaces, configure control-plane and user-
plane links between the CN and the overflow RNC and between neighboring RNCs and
the overflow RNC on the CN and neighboring RNCs, respectively. It is recommended
that the control-plane and user-plane transmission bandwidth and link quantities on the
overflow RNC be the same as those on the master RNC.

Copyright © Huawei
If IP paths are used on the Iu-PS user plane of the neighboring RNC, IP paths and IP routes over the Iu-
PS interface of the overflow RNC must be configured on the neighboring RNC. For details, see
"Configuring a Path for Static SRNC Relocation" in BSC6900 UMTS Initial Configuration Guide. (The
section can be found by choosing BSC6900 UMTS Initial Configuration Guide > BSC6900 UMTS
Initial Configuration Guide (MML-based) > Configuring the Interfaces > Configuring the Iur
Interface (over IP) > Configuring a Path for Static SRNC Relocation). If a transmission resource
pool is used on the Iu-PS interface of the neighboring RNC, configuring a path for the UE-not-involved
relocation is not required.
The following figure shows the UE-not-involved relocation in RNC in Pool networking.
As shown in the preceding figure, assume that only IP1 is configured for the Iu-PS interface
of P_RNC1, and only IP2 is configured for the Iu-PS interface of P_RNC2. Assume that
P_RNC3 is a BSC6900, only IP3 is configured for the Iu-PS interface of P_RNC3, and
P_RNC3 is a neighboring RNC of L_RNC1.
Before P_RNC1 and P_RNC2 are pooled, only IP1 can be used on the Iu-PS interface of
L_RNC1. For the neighboring RNC to support the UE-not-involved relocation, an IP path
from IP3 to IP1 and an IP route to IP1 must have been configured on P_RNC3.
After P_RNC1 and P_RNC2 are pooled, IP2 can also be used on the Iu-PS interface of
L_RNC1. Therefore, an IP path from IP3 to IP2 and an IP route to IP2 need to be configured
on P_RNC3. If IP3' and IP2' are also configured on the Iu-PS interfaces of P_RNC3 and
P_RNC2, respectively, you also need to configure IP paths from IP3 to IP2', from IP3' to IP2,
and from IP3' to IP2', and configure an IP route to IP2'.
2.4.12 Activating Load Sharing

2.4.12.1 Pre-Activation Checks
Before activating load sharing, ensure that:
 RNC-level data has been synchronized within the pool. If data has not been
synchronized, perform Step 2 in section 2.4.10Synchronizing the RNC-level Data Within
a Pool"2.4.10Synchronizing the RNC-level Data Within a Pool." It is recommended that

Copyright © Huawei
the DSP URNCPOOLDATASYNC command be executed on the master RNC to query

whether data has been synchronized. If data has not been synchronized, perform the
steps described in section 2.4.10Synchronizing the RNC-level Data Within a
Pool"2.4.10Synchronizing the RNC-level Data Within a Pool."
 The configuration data between the master RNC and the overflow RNC is consistent. If
an ALM-706 Inconsistent RNC in Pool Configuration alarm is reported on the U2000,
manually perform data synchronization on the CME. For the detailed procedures, see
section 5.6Manually Synchronizing RNC in Pool Data."
 The license information for RNC in Pool has been synchronized. To verify whether the
license information synchronization is successful, run the COL LOG command on the
overflow RNC and set Log File Type to BSC_INFO(The Basic Information of the
BSC). If the license information about the logical RNC is contained in the log, the
license information synchronization is successful. If an ALM-20759 POOL License
Information Synchronization Failure alarm is reported, troubleshoot the problem.
 The Iur-p delay is within the required range. See section 5.2Iur-p Transmission Delay
Measurement Methods"5.2Iur-p Transmission Delay Measurement Methods" for
methods to check the Iur-p delay.
 Load sharing is enabled for multicast packets (specified by BIT21 under Fault
Detection Switch 1 in the SET ETHSWITCH command) if the master RNC is a
BSC6900. If not enabled, run the SET ETHSWITCH command with the check box
BIT21 under Fault Detection Switch 1 selected. If this check box is not selected, inter-
subrack traffic may be congested and packets may be discarded, which may lead to
service interruption.
 When the feature RNC in Pool Multiple Logical RNCs has been enabled, flow control of
load sharing has been enabled on the overflow RNC if the control-plane or user-plane
CPU of the overflow RNC is overloaded. To enable the flow control of load sharing on
the overflow RNC, run the SET UPOOLFLOWCTRLPARA command with Control-
Plane Load Sharing and Flow Control SW, User-Plane Load Sharing and Flow
Control Switch, Load Sharing Proportion Control Switch, CPU Threshold in CP
Load Sharing and Flow Control, CPU Threshold in UP Load Sharing and Flow
Control, and CPU Threshold for Load Sharing Proportion Ctrl set to proper values.
 The Iu/Iur DIP synchronization switch is set to on for both the master RNC and overflow
RNC if the Iu/Iur interfaces use IP transmission and user-plane load sharing is required.
To set the Iu/Iur DIP synchronization switch to on, run the SET TNSOFTPARA
command with IuIurDIPSynSw(BSC6900,BSC6910) set to ON. After this switch is
turned on, the overflow RNC obtains the peer IP address and performs transmission
detection before processing services. If IP transmission on the Iu/Iur interface of the
overflow RNC is faulty, an ALM-21392 Adjacent Node IP Address Ping Failure alarm is
reported, informing the customer to rectify the fault. In addition, the faulty Iu/Iur
transmission resources will not take over services, thereby preventing service
interruption due to load sharing. If the user plane of the Iu interface is faulty on the
overflow RNC, the RNC in Pool user-plane load sharing function is impacted and ALM-
22307 RNC in Pool Function Unavailable is reported with the cause value "UP on the Iu
Interface for Overflow RNC Unavailable."
 The Iub DIP synchronization switch is set to on for the master RNC if the Iub interface
uses IP transmission and user-plane load sharing is required. To set the Iub DIP
synchronization switch to on, run the SET TNSOFTPARA command with
IubDIPSynSw(UMTS BSC6900, UMTS BSC6910) set to ON. After this switch is
turned on, the overflow RNC obtains the peer IP address and performs transmission
detection before processing services. If IP transmission on the Iub interface of the
overflow RNC is faulty, an ALM-21392 Adjacent Node IP Address Ping Failure alarm is
reported, informing the customer to rectify the fault. In addition, the faulty Iub
transmission resources will not take over services, thereby preventing service

Copyright © Huawei
interruption due to load sharing. This function is applicable only in scenarios in which
Layer 3 networking is used between a NodeB and the master RNC and between the
NodeB and the overflow RNC and there are reachable routes between all user-plane IP
addresses of the NodeB and the master and overflow RNCs.
 The check results for RNC in Pool configurations have been confirmed on the CME.
2.4.12.2 Feature Activation

Load Sharing is activated on a per logical RNC basis and needs to be active only on the
master RNC.
 To activate control-plane load sharing, run the SET UPOOLLOADSHAREPARA
command on the master RNC with CP Load Sharing Policy set to
CP_SHARE(CP_SHARE), with Control Plane Load Sharing Absolute Threshold
and Control Plane Load Sharing Relative Threshold set to proper values.
 To activate user-plane load sharing, run the SET UPOOLLOADSHAREPARA
command on the master RNC with UP Load Sharing Policy set to
UP_SHARE(UP_SHARE), with User Plane Load Sharing Absolute Threshold and
User Plane Load Sharing Relative Threshold set to proper values.
Control-plane load sharing can be activated alone, but user-plane load sharing cannot.
After activating the RNC in Pool feature, check its configurations again on the CME for correctness.
2.5 Acceptance
This section describes the procedures for performing acceptance to verify whether the
reconstruction is successful.
2.5.1 Checking the RNC in Pool Topology

Before checking the RNC in Pool topology, perform the following operations to synchronize
NEs on the CME: Log in to the U2000, choose CME > Current Area > Synchronize NEs,
and then select physical RNCs shown in the following figure to synchronize NEs in the
current area.

Copyright © Huawei
The operation results are shown in the following figure, indicating that the synchronization is
successful.
If the synchronization fails, follow the instructions provided in the synchronization failure
report to solve the problem.
Then, perform the following steps to check the RNC in Pool topology:
Step 1 Log in to the U2000, and choose Topology > Main Topology on the main menu. On the
displayed Main Topology tab page, choose RNC Pool View from Current View, as shown
in the following figure.
Step 2 Check whether the preceding result is consistent with the current networking. If it is
consistent, choose Topology > Show > Monitor RNC in Pool.

Copyright © Huawei
The status table is displayed in the following figure.
The statuses in the preceding status table must be consistent with the current RNC in Pool
networking configurations.
 If the topology is inconsistent with actual configurations, run the following commands to check
whether all physical RNCs are configured with the same pool name, and whether local nodes of the
logical RNC match with external nodes of the logical RNC:
SET SYS: SUPPORTRNCINPOOL=SUPPORT, POOLNAME="XXX";
SET NODE:NID=XX, NNAME="XX; and ADD EXTNODE:ENID=XX, ENNAME="XX";
 If the statuses shown in the table are inconsistent with actual configurations, run the following
commands to check whether the master RNC and overflow/backup RNC of the same logical RNC
are correctly configured and match with each other:
ADD URNCBASIC: LoadSharingType=XX, RedundancyType=XX; and ADD URNCMAP:
ENID=XX, LoadSharingType=XX, RedundancyType=XX;
----End

Copyright © Huawei
2.5.2 Checking the Synchronization Task Status on the CME

Before checking the status of synchronization tasks, synchronize NEs in the current area.
Automatic Synchronization Task Check

Step 1 On the U2000, choose CME > UMTS Application > RNC in Pool Configuration > RNC in
Pool Configuration Management.
Synchronization tasks are displayed in the RNC in Pool Configuration Management tab
page.
Step 2 Select a task (for example, ) and then click .
Step 3 Click .
Ensure that the synchronization task succeeds.

Copyright © Huawei
Click in the following figure. In the displayed Configuration Sync Switch dialog box, select
Enable Auto Sync.
----End
Manual Synchronization Task Check

If manual synchronization tasks are created, check whether the tasks are displayed in the Task
Management window.
Log in to the U2000, choose Maintenance > Task Management, select Pool Consistency
check on the left, and check the status of different tasks according to task name.
2.5.3 Checking Licenses

Step 1 Run the LST LICENSE command to check whether the licenses for Load Sharing in the
master and backup license files are activated.
Step 2 If possible, run the CMP LICENSE command to compare whether licenses are consistent
between the host and OMU.
----End
2.5.4 Checking the Iur-p Transmission Delay

On the WebLMT, choose Monitor > UMTS Monitoring > Iur-p Monitoring to check
whether the Iur-p transmission delay meets the requirements. For details, see section 5.2Iur-p
Transmission Delay Measurement Methods"5.2Iur-p Transmission Delay Measurement
Methods."
2.5.5 Checking Alarms

Check whether the following alarms are reported after the reconstruction. If any of the
following alarms is reported, perform actions to ensure that the reconstruction is performed
correctly.
 ALM-706 Inconsistent RNC in Pool Configuration
 ALM-20759 POOL License Information Synchronization Failure
 ALM-22307 RNC in Pool Function Unavailable
 ALM-21607 External Node Unreachable
 ALM-21606 IURP Link Fault

Copyright © Huawei
 ALM-21608 IURP Link Congestion

 ALM-21341 IP PM Activation Failure
 ALM-22243 Excessive Synchronization Data for RNC in Pool Load Sharing
 ALM-22391 Function of RNC in Pool Load Sharing Flow Control
2.5.6 Checking RNC in Pool Configurations

This section describes how to check RNC in Pool configurations on the CME for ensuring
data integrity and data consistency between the master RNC and the overflow RNC. To check
the RNC in Pool configurations, perform the following operations:
Step 1 Start the CME, on the menu bar of the planned data area, choose UMTS application > RNC
in Pool Configuration > RNC in Pool Configuration Check (in CME client mode) or CME
> UMTS application > RNC in Pool Configuration > RNC in Pool Configuration Check.
The RNC in Pool Configuration Check page is displayed.
Step 2 Start the check.

Step 3 Check the results.
----End
 Before the check, synchronize RNC and NodeB configuration data to the planned data area on the
CME. Configuration checks are required only for the master RNC.
 In R18C01/CME R16 and later, the function is supported.
2.5.7 Checking Basic Services

Perform the following operations to check basic services:
 Perform dialing tests and drive tests on CS services. The connection success rate is the
same as that before the reconstruction. The voice should be clear.
 Perform dialing tests and drive tests on PS services. The connection success rate is the
same as that before the reconstruction. The PS data is transmitted properly and the
average download speed is close to the average empirical speed.

Copyright © Huawei
If dialing tests and drive tests cannot be performed, you are advised to monitor routine KPIs
of the master RNC for 1 to 2 hours. The KPIs after the construction is expected to be the same
as those before the reconstruction.
2.5.8 Accepting Load Sharing

You can accept Load Sharing by using either one of the following methods:
 Perform IMSI dialing tests and use Load Sharing test reports (To obtain such reports,
visit http://support.huawei.com.).
 Perform IMSI dialing tests and trigger Load Sharing to take effect by adjusting the
activation threshold.
The specific method is selected based on project situations. The final "Acceptance Solution"
is presented in the "Reconstruction and Deployment Solution" upon reaching an agreement
with customers.
IMSI dialing tests: performed at sites where driving tests or dialing tests can be carried out
Step 1 Prepare a test UE and record the IMSI of the UE.
Step 2 Run the ADD UIMSI command on the master RNC with the IMSI parameter set to the UE's
IMSI and the LoadShareSwitch parameter set to ON. If control-plane load sharing is to be
verified, set the LoadShareType parameter to CP_SHARE. If user-plane load sharing is to
be verified, set the LoadShareType parameter to CPUP_BIND_SHARE and the ENID
parameter set to the Node ID of the overflow RNC.
Step 3 Run the LST UIMSI command on the overflow RNC to ensure that the UE's IMSI is
synchronized to the overflow RNC. Use the UE to initiate two calls. The first call enables the
master RNC to learn the UE's IMSI, and in the second call, the master RNC attempts to
offload the call to the overflow RNC.
Step 4 Run the DSP UIMSI command on the master RNC with the IMSI parameter set to the UE's
IMSI and the IMSI_FUNC parameter set to LOADSHARE. If the loading sharing status in
the command output is Control Plane Load Sharing Succeed or Combined Control and
User Plane Load Sharing Succeed, the Load Sharing feature takes effect.
 The UEs are involuntarily offloaded to the overflow RNC by the IMSI, but the load sharing is not
based on the load sharing algorithm. Therefore, the effectiveness of the load sharing algorithm
cannot be verified. The correctness of service processing and the Iur-p interface after UEs are
offloaded to the overflow/backup RNC can be verified.
 This method relies on the unchanged TMSI/P-TMSI in the two RRC Connection Request messages.
If the UE accesses the network using a different TMSI/P-TMSI each time, this method is not
applicable.
----End
Triggering Load Sharing to take effect by adjusting the activation threshold: After the
reconstruction is complete, monitor the load status of the master RNC and overflow/backup
RNC and run the SET UPOOLLOADSHAREPARA command to set the activation
threshold.
Use one of the following methods to verify whether Load Sharing is enabled:
 Run the DSP LICUSAGE command on the master RNC to query the used value of the
license control item RNC in Pool Load Sharing (per Active User). If the return value is
not0, the RNC in Pool Load Sharing feature is enabled.

Copyright © Huawei
 Or check values returned by the following counters. If the values are not 0, the RNC in
Pool Load Sharing feature is enabled.
Feature Name Counter Name Counter Description
Control-Plane Load Sharing VS.RRC.SuccConnEstab.N Number of Successful RRC

odeShare Connection Requests Sent
by UEs Whose Load Is
Shared Between Physical
RNC Nodes
VS.RRC.AttConnEstab.Nod Number of RRC Connection
eShare Requests Sent by UEs
Whose Load Is Shared
Between Physical RNC
Nodes
VS.RAB.AttEstabCS.Conv. Number of CS RAB
NodeShare Assignment Requests for
UEs Whose Load Is Shared
Nodes (Conversational
Service)
VS.RAB.SuccEstabCS.Con Number of Successful CS
v.NodeShare RAB Assignment Requests
for UEs Whose Load Is
RNC Nodes (Conversational
Service)
VS.RAB.AttEstabPS.Bkg.N Number of PS RAB
odeShare Assignment Requests for
Nodes (Background Service)
VS.RAB.SuccEstabPS.Bkg. Number of Successful PS
NodeShare RAB Assignment Requests
RNC Nodes (Background
Service)
VS.RAB.AttEstabPS.Int.No Number of PS RAB
deShare Assignment Requests for
Nodes (Interactive Service)
VS.RAB.SuccEstabPS.Int.N Number of Successful PS
odeShare RAB assignment Requests
RNC Nodes (Interactive
Service)

Copyright © Huawei
VS.LoadSharedActiveUEs. Number of UEs Whose

NodeShare Load Is Shared Between
Physical RNC Nodes
User-Plane Load Sharing VS.CSLoad.Erlang.Equiv.N Average Equivalent Erlangs
odeShare Consumed by CS Load
Sharing Users Between
Physical RNC Nodes for an
RNC
VS.R99PSLoad.DLThruput. DL R99 Average Traffic of
NodeShare Load Sharing Users
Nodes for an RNC in the PS
Domain
VS.R99PSLoad.ULThruput. UL R99 Average Traffic of
Nodes in the PS Domain
VS.HSDPAPSLoad.DLThru HSDPA Average Traffic of
put.NodeShare Load Sharing Users
Domain
VS.HSUPAPSLoad.ULThru HSUPA Average Traffic of
Domain
Before this method is used, identify the absolute and relative load-sharing threshold based on the load
status on the live network. If control-plane load sharing is enabled, identify the absolute and relative
threshold by monitoring the average CPU usage of the master RNC and the overflow/backup RNC
(BSC6900: VS.XPU.CPULOAD.MEAN; BSC6910: VS.CPPOOL.CPULOAD.MEAN). If user-plane
load sharing is enabled, monitor the CPU usage of the master RNC and overflow/backup RNC
(BSC6900: VS.DSP.UsageAvg; BSC6910: VS.UPPOOL.CPULOAD.MEAN). For details, contact
R&D engineers.
2.6 Procedures for Rolling Back Load Sharing

2.6.1 Deactivation
Deactivating Control-Plane Load Sharing
When only control-plane load sharing is enabled, run the SET UPOOLLOADSHAREPARA
NO_SHARE(NO_SHARE) to deactivate Load Sharing.

Copyright © Huawei
Deactivating User-Plane Load Sharing

When control-plane load sharing and user-plane load sharing are both enabled, if you want to
deactivate only user-plane load sharing, run the SET UPOOLLOADSHAREPARA
command on the master RNC with UP Load Sharing Policy set to
NO_SHARE(NO_SHARE). If you want to deactivate both the control-plane load sharing
and user-plane load sharing, run the SET UPOOLLOADSHAREPARA command on the
master RNC with CP Load Sharing Policy set to NO_SHARE(NO_SHARE).
2.6.2 RNC in Pool Networking Rollback

To perform a networking rollback, remove related configurations from the master RNC and
configurations of the logical RNC from the overflow RNC. If N master RNCs are involved,
perform the following steps for these RNCs one by one.
2.6.2.1 Control-Plane Load Sharing Rollback

Step 1 Run the SET UPOOLLOADSHAREPARA command on the master RNC with CP Load
Sharing Policy set to NO_SHARE(NO_SHARE) to disable Load Sharing.
Step 2 Run the EXP URMVRNCDATA command on the overflow RNC to export the script (for
example, Remove_RNC1_Script.zip) for removing the logical RNC. A backup script
Remove_RNC1_Script_bak.zip is also generated. Unzip the Remove_RNC1_Script.zip file
as Remove_RNC1_Script.txt and then upload it to the ftp directory of the active OMU
workspace. Run the RUN BATCHFILE command on the overflow RNC to execute the
exported script.
Step 3 Run the RMV SRCIPRT and RMV DEVIP commands on the overflow RNC. When link
aggregation is not used, run the RMV ETHIP command. When link aggregation is used, run
the RMV ETHTRKIP, RMV ETHTRKLNK, and RMV ETHTRK commands to remove
Iur-p link configurations.
Step 4 Run the RMV IPPOOLIP and RMV IPPOOL commands on the overflow RNC to remove
Iur-p user-plane transmission configurations.
Step 5 Run the RMV IURPLKS, RMV SRCIPRT, and RMV DEVIP commands on the master
RNC. When link aggregation is not used, run the RMV ETHIP command. When link
aggregation is used, run the RMV ETHTRKIP, RMV ETHTRKLNK, and RMV
ETHTRK commands to remove the Iur-p link sets and related IP addresses.
Step 6 Run the RMV URNCMAP command on the master RNC to remove the mapping between a
logical RNC and a physical RNC.
Step 7 Run the RMV EXTNODE command on the master RNC to remove the information about the
external RNC.
Step 8 Run the SET SYS command on the master RNC and overflow RNC with Support RNC in
Pool set to NOT_SUPPORT(Not_Support).
----End
2.6.2.2 User-Plane Load Sharing Rollback


Copyright © Huawei
Step 2 Run the EXP URMVRNCDATA command on the overflow RNC to export the script (for
example, Remove_RNC1_Script.zip) for removing the logical RNC.
A backup script Remove_RNC1_Script_bak.zip is also generated.
Step 3 Unzip the Remove_RNC1_Script.zip as Remove_RNC1_Script.txt and then upload it to
the OMU active workspace/ftp directory.
Step 4 Run the RUN BATCHFILE command on P_RNC2 to execute the exported script for
removing the logical RNC.
Step 5 On the overflow RNC, run RMV SRCIPRT, RMV DEVIP, RMV ETHIP (when link
aggregation is not used), and the following three commands (when link aggregation is used):
RMV ETHTRKIP, RMV ETHTRKLNK, and RMV ETHTRK to remove the Iur-p link
configurations.
Step 6 On the overflow RNC, run RMV IPPOOLIP and RMV IPPOOL to remove the Iur-p user-
plane transmission configurations.
Step 7 On the master RNC, run the following commands to remove the related configurations: RMV
IURPLKS, RMV SRCIPRT, RMV DEVIP, RMV ETHIP (when link aggregation is not
used) and the following three commands (when link aggregation is used): RMV
ETHTRKIP, RMV ETHTRKLNK, and RMV ETHTRK to remove the Iur-p link sets and
related IP addresses
Step 8 On the master RNC, run DEA IPPOOLPM, RMV ADJMAP, RMV ADJNODE, RMV
IPPOOLIP, and RMV IPPOOL to remove the Iur-p user-plane transmission configurations.
Step 9 On the master RNC, run the RMV URNCMAP command to remove the mapping between a
logical RNC and a physical RNC.
Step 10 On the master RNC, run the RMV EXTNODE command to remove the information about
the external RNC.
Step 11 Run the SET SYS command on both the master and overflow RNCs and set Support RNC in
Pool to NOT_SUPPORT(Not Support).
Step 12 Remove the Iu/Iur user-plane data of the overflow RNC on the CN and neighboring RNC,
respectively.
Step 13 Remove the Iub user-plane data of the overflow RNC on the NodeB.
Step 14 Run the SET TNSOFTPARA command on the master RNC with Iu/Iur Destination IP
Synchron Switch and Iub Destination IP Synchron Switch both set to OFF(OFF).
----End
 The EXP URMVRNCDATA command can be used to export MML scripts that are used to remove
the data of an overflow RNC from an OMU. Such data includes the pool data synchronized from the
master RNC, Iub user-plane objects of the overflow RNC (ADJMAP, TRMFACTOR, TRMMAP,
and ADJNODE), Iur-p user-plane transmission and Iur-p links between physical nodes, the mapping
between a logical RNC and a physical node, basic information about the logical RNC, information
about the external physical RNC, and information about the external NodeB.
 If the configurations for the logical RNC need to be restored immediately after being
removed, run the RUN BATCHFILE command to execute the generated rollback script
(Remove_RNC1_Script_bak.txt).
 If a physical RNC within a pool carries the overflow RNCs of multiple logical RNCs at
the same time, delete all related configurations of all the logical RNCs and then you can

Copyright © Huawei
run the SET SYS command with Support RNC in Pool setto
NOT_SUPPORT(Not_Support).

Copyright © Huawei
Engineering Guidelines for Node RedundancyEngineerin
RNC in Pool Reconstruction Guide (RAN18.1) g Guidelines for Node Redundancy
3 Engineering Guidelines for Node

Redundancy

3.3 Preparation
3.4 Procedures for Node Redundancy Reconstruction
3.5 Acceptance
3.6 Procedures for Rolling Back Node Redundancy

considered.
3.1.1 Scenario 1: N Master RNCs and An Backup RNC Carrying

example to describe node redundancy configuration.
 The BSC6910 functioning as a backup RNC can be either a newly deployed RNC or a legacy RNC.
 If multiple RNCBASIC MOs are configured on a BSC6910 working as a backup RNC, the backup
RNC must be enabled with the feature WRFD-150240 RNC in Pool Multiple Logical RNCs and
provided with the license for this feature.
Three master RNCs (P_RNC1, P_RNC2, and P_RNC3) and one backup RNC (P_RNC4)
form a pool of multiple logical RNCs. The backup RNC for the three master RNCs is carried
on the same physical RNC, as shown in Figure 14.1.

Copyright © Huawei
Figure 14.1 Three master RNCs and one backup RNC carrying multiple logical RNCs
Scenario 1 can be divided into the following subscenarios, as listed in the following table.
S Befor Before After Node A

u e Node Redundancy ft
bs Depl Redun Activation er
ce oyme dancy D
n nt Activa e
ar tion pl
io o
N y
o. m
e
nt
R Numb Attribu Interconnection R

N er of te of Scheme N
C Maste Logical C
R r RNCs R
A RNCs A
T T
3. Non- UO N N No UO N
1. RNC- O backu
1. in- _ p
1 Pool R routes
scenar ed
ios un
da
nc
y

Copyright © Huawei

ce oyme dancy D
n nt Activa e
ar tion pl
io o
N y
o. m
e
nt
1. RNC- O backu
1. in- _ p and
2 Pool R standb
scenar ed y
ios un links
da
nc
y
1. RNC- O SCTP
1. in- _ dual-
3 Pool R homin
scenar ed g
ios un
da
nc
y
3. N+1 UO N M Backu UO M
1. backu an p
1. p ua routes
4 routes l/
A
ut
o
m
ati
c
3. N+1 UO N M Activ UO M
1. Activ an e and
1. e and ua standb
5 standb l/ y
y A links
links ut
o
m
ati
c
3. N+1 UO N M SCTP UO M
1. SCTP an dual-

Copyright © Huawei

ce oyme dancy D
n nt Activa e
ar tion pl
io o
N y
o. m
e
nt
1. dual- ua homin
6 homin l/ g
g A
ut
o
m
ati
c
If the logical RNC attribute changes after Node Redundancy is activated, the attributes before and after
the activation are highlighted. The number of master RNCs changing from N to M indicates the
specification changes of logical RNCs. For example, a 2+1 pool changes to a 3+1 pool.

must be BSC6910s.
 The BSC6910 functioning as a backup RNC can be either a newly deployed RNC or a legacy RNC.
 The two BSC6910s functioning as the backup RNCs must be enabled with the feature WRFD-
150240 RNC in Pool Multiple Logical RNCs and provided with the license for this feature.
14.2.

Copyright © Huawei
Su Befor Before After Node A

bsc e Node Redundancy ft
en Depl Redun Activation er
ari oyme dancy D
o nt Activa e
No tion pl
. o
y
m
e
nt
RN Numb Attribu Interconnectio R

C er of te of n Scheme N
RA Maste Logical C
T r RNCs R
RNCs A
T
3.1. Non- UO 6 N No UO 6
3.1 RNC- O backu
in- _ p
Pool R routes
scenar ed
ios un
da
nc
y
3.2 RNC- O active

Copyright © Huawei
Su Befor Before After Node A

bsc e Node Redundancy ft
en Depl Redun Activation er
ari oyme dancy D
o nt Activa e
No tion pl
. o
y
m
e
nt
in- _ and
Pool R stand
scenar ed by
ios un links
da
nc
y
3.3 RNC- O SCTP
in- _ dual-
Pool R homin
scenar ed g
ios un
da
nc
y

Copyright © Huawei

Figure 14.3 Process of RNC in Pool Node Redundancy reconstruction
 Iu/Iur interface reconstruction involves operations on the peer CN and neighboring RNCs.
Therefore, ensure that O&M personnel of the peer nodes are ready to work.
 Despite that no CBC server-related operation is required on the day when Iu-BC interface
reconstruction is performed, users need to ensure that O&M personnel of the peer node are ready to
work. The operations involving the CBC server are performed after the control rights are switched to
the backup RNC. For details, see section 5.4Iu-BC Solution When RNC in Pool Node Redundancy
is Enabled."
 If a large number of NodeBs need to be reconstructed, you are advised to reconstruct Iub
interfaces in batches. It is recommended that the number of NodeBs to be reconstructed

Copyright © Huawei
be no more than 50 for the first batch and no more than 100 for later batches. The
number of batches to be performed can be adjusted as required.
 During the preceding reconstruction processes, the project duration can be adjusted
based on site conditions. It is recommended that reconstruction of different interfaces be
performed separately. It is also recommended that interface reconstruction be performed
in low-traffic hours because reconstruction will affect ongoing services. However,
projects may differ in time plan. If certain interfaces cannot be reconstructed during low-
traffic hours, you are advised to ensure that Iu interfaces are reconstructed during low-
traffic hours. Reconstruction time for other interfaces can be adjusted as required.
concurrently. Vertical operations must be performed serially. If logical RNC
interfaces of these RNCs concurrently.
reconstruction. Therefore, you are advised to use the standalone CME to configure
reconstruction scripts. Traditionally, only Iub interfaces are reconstructed on standalone
CMEs and other interfaces are reconstructed using MML commands. For details about
Figure 14.4 Estimated time for RNC in Pool Node Redundancy reconstruction
 Required time listed in the preceding figure is for reference only. Operation personnel need to
estimate required time based on site conditions.

Copyright © Huawei
 The time required for Iub reconstruction can be used as a reference for later reconstruction with 100
NodeBs per batch.
 Section 5.7X Project Deployment Solution"5.7X Project Deployment Solution" is an example.
3.2.2 Rollback Procedure

3.2.2.1 Deactivating Node Redundancy
After Node Redundancy is enabled, you can roll back the feature by deactivating it due to
problems, such as exceptions, unexpected benefits, or other O&M issues. Activate the feature
again after problems are resolved.


Copyright © Huawei
Figure 14.5 Networking rollback for Node Redundancy

Copyright © Huawei
3.3 Preparation
 The BSC6910 Iu-PS interface supports only IP transmission networking. Therefore, if
the master RNC is a BSC6900 and the Iu-PS interface uses ATM transmission, convert
the ATM transmission to IP transmission before reconstruction.
 If the SCTP dual-homing scheme is used for deploying Node Redundancy, configure
dual-homed SCTP links over Iu and Iur interfaces on the master RNC.
reconstruction.
3.4 Procedures for Node Redundancy Reconstruction

This section describes the detailed procedures for Node Redundancy reconstruction. The
following steps apply to all scenarios, unless otherwise specified.
For details, see section 3.4.1Preparing License Files"3.4.1Preparing License Files."
For details, see section 3.4.2Activating License Files"3.4.2Activating License Files."
For details, see section 3.4.3Backing Up Data and Preparing Tools"3.4.3Backing Up Data and
Preparing Tools."
Step 4 Perform Iur-p reconstruction (only Iur-p signaling links are involved).
Interfaces."
5. Activate Iur-p configuration data on the master RNC and backup RNC separately.

Copyright © Huawei
7. Check whether new alarms are reported on the master RNC and backup RNC, including
ALM-21606 IURP Link Fault, ALM-21607 External Node Unreachable, and ALM-
21608 IURP Link Congestion. If new alarms are reported, clear them.
Pool"3.4.10Synchronizing the RNC-level Data Within a Pool." After the synchronization is
Step 6 Reconstruct Iu/Iur interfaces.
For details, see section 3.4.5Configuring Iu/Iur Interfaces"3.4.5Configuring Iu/Iur
Interfaces."
5. Activate Iu/Iur configuration data on the master RNC and backup RNC separately.
7. Run the SET TNSOFTPARA command with IuIurDIPSynSw set to ON on both the
master and backup RNCs to turn on the Iu/Iur DIP synchronization switch.
8. Run the CHK SERINTEG command on the backup RNC to check whether the Iu/Iur
interface configuration is complete.
9. Check on the backup RNC and peer CN/neighboring RNCs whether the Iu/Iur is in the
normal state. The N7DPC and SCTPLNK must be available and M3LNK must be in
the deactivated state.
ALM-21392 Adjacent Node IP Address Ping Failure. If new alarms are reported, clear
them.

Copyright © Huawei
Step 7 (Optional) Reconstruct the Iu-BC interface (perform this step only when the master RNC is
configured with the Iu-BC interface).
1. Run the ADD DEVIP command on the backup RNC to add an IP address for the
interface board on the CBC server.
2. Run the MOD UCBSADDR command on the backup RNC to change the CBS RNC IP
address and the second CBS RNC IP address (when the CBC server supports Node
Redundancy) to the IP address for the interface board in the preceding step.
3. Add related configurations on the peer CBC server. For details, see section 5.4Iu-BC
Solution When RNC in Pool Node Redundancy is Enabled"5.4Iu-BC Solution When
RNC in Pool Node Redundancy is Enabled."
Step 8 Reconstruct Iub interfaces.
For details, see section 3.4.6Configuring Iub Data for the Backup RNC"3.4.6Configuring
Iub Data for the Backup RNC."
5. Activate Iub configuration data on the master RNC, backup RNC, and NodeBs to be
reconstructed separately.
6. Run the ADD UNODEBLICENSE command on the master RNC with
RNC_IN_POOL_NODE_REDUNDANCY selected under the FuncSwitch1 parameter
to configure Node Redundancy licenses for all dual-homed NodeBs.
7. Run the SET TNSOFTPARA command with IubDIPSynSw set to ON on the master
RNC to turn on the DIP synchronization switch.
8. Run the SET URRCTRLSWITCH command on the master RNC with
SEROBJCFG_NOT_CMP_ALM_REPORT_SWITCH (Service Configuration
Object Inc. Alarm Switch) selected under the FunctionSwitch parameter.
ALM-21392 Adjacent Node IP Address Ping Failure, ALM-22388 Configuration of
Service Objects Incomplete, and ALM-22235 Dual-Homed NodeB Configuration
Incorrect. If new alarms are reported, clear them.
For details, see section 3.4.11Synchronizing the NodeB-level Data Within a
Pool"3.4.11Synchronizing the NodeB-level Data Within a Pool."
Step 10 Run the SET URRCTRLPHYSWITCH command on the master RNC and backup RNC
with NODE_REDUNDANCY_CAPACITY_CHECK_SWTICH selected under the

Copyright © Huawei
OptimizationSwitch parameter to enable the capacity check function for the RNC in Pool
Node Redundancy feature.
Step 11 Activate Node Redundancy.
For details, see section 3.4.13Activating Node Redundancy"3.4.13Activating Node
Redundancy."
Step 12 Perform reconstruction acceptance.
For details, see 3.5Acceptance"3.5Acceptance."
----End
You can configure and commission the common transmission of the interfaces to be reconstructed
independently first and then perform the rest of interface reconstruction operations.

 To enable the RNC in Pool Node Redundancy feature, the corresponding license control
items listed in the following table must be applied for. The control item is a software
license item and therefore you only need to apply for it in the license file of the master
RNC of the corresponding logical RNC.
Name for
Multiple
Operators
WRFD- RNC in Pool LQW1RP RNC in BSC6900 License Per

150212 Node NRRES Pool Node BSC6910 control items NodeB
Redundancy Redundan that cannot
cy (per be configured
NodeB) based on
operators
 If the backup RNC uses the feature WRFD-150240 RNC in Pool Multiple Logical
RNCs, users also need to apply for the corresponding license control items listed in the
following table. The control item is a hardware license item and therefore you need to
apply for it in the license files of the corresponding physical nodes enabled with the
feature WRFD-150240 RNC in Pool Multiple Logical RNCs.
Name for
Multiple
Operators
WRFD- RNC in LQW1R RNC in BSC6910 License per

150240 Pool PMLRR Pool control items Logic
Multiple ES Multiple that cannot RNC
Logical Logical be
RNCs RNCs (per configured

Copyright © Huawei

Name for
Multiple
Operators
RNC) based on
operators
On a BSC6910, the number of license control items of WRFD-150240 RNC in Pool Multiple Logical
RNCs equals the number of logical RNCs minus one. Scenario 1 is used as an example. In Figure 14.1,
the P_RNC4 carries three logical RNCs. Therefore, two Multiple Logical RNCs license control items
need to be purchased in the hardware license file of the P_RNC4.
be applied for:
BOM Code License ID License Name License Application
82203572 LQW1HWCL03 RNC Throughput Required for Node

Hardware Capacity Redundancy activation
(per 50Mbps)
82203573 LQW1HWCL04 RNC Active User Required for Node
Hardware Capacity Redundancy activation
(per 1000 Active
Users)
82203729 LGW1DPIHC02 Network Intelligence Optional unless the NIU
Processing board is used
Throughput (per
50Mbps)
82204003 LQW1RPMLRRES RNC in Pool Multiple Optional unless the
Logical RNCs (per feature WRFD-150240
RNC) RNC in Pool Multiple
Logical RNCs is used
81201592 LQW1UPCPDS01 RNC User Plane and Optional unless the
Control Plane feature WRFD-141201
Dynamic Sharing RNC User Plane and
Control Plane Dynamic
Sharing is used
service volume that the backup RNC is going to share after it becomes the master RNC.
For details, see RNC in Pool Configuration Principle.
 When a network is shared by multiple operators, the features Load Sharing, Node
Redundancy, and Multiple Logical RNCs cannot be used exclusively for one operator. If
these features are used, they must be used for all the operators configured on an RNC.
Therefore, the preceding license control items are not operator-specific and the license
usage is displayed on only the primary operator.

Copyright © Huawei
 The following figures show the logic of processing license files of the master RNC and
backup RNC in different scenarios.

Copyright © Huawei
Figure 12.2 Logic of processing the license file of the backup RNC
following tables.

P_RNC1 Master RNC

P_RNC2 Master RNC
P_RNC3 Master RNC
P_RNC4 Backup RNC

Copyright © Huawei
2 shown in en-us_topic_0034583232.xml#EN-US_TOPIC_0034583232/ref460417244.

P_RNC1 Master RNC + Backup RNC


P_RNC1 Master RNC

P_RNC2 Master RNC
P_RNC3 Master RNC
P_RNC4 Master RNC
online mode when the SCU boards of MPSs are running normally. (A hardware ESN is a string of 20
characters with the service ID being NULL.)
 If you need to add the master RNC on a backup RNC after the deployment of Node Redundancy, see
section 1.7.3NE Licenses"1.7.3NE Licenses" for detailed operations.
 Application for licenses other than those of the feature RNC in Pool is not provided here and the
application rules are the same as those for licenses of non-RNC-in-Pool networkings.
 If license control items Network Intelligence Processing Throughput (per 50Mbps) and RNC User
Plane and Control Plane Dynamic Sharing are required, apply for them by following the processing
principles for other control items of the backup license file.

 Prepare required license files of the master RNC and backup RNC and active them
separately by following the instructions provided in section 3.4.1Preparing License
Files"3.4.1Preparing License Files." Perform the following steps to activate the license
files on the NE side:

Copyright © Huawei

license file.
Check whether the ESN specified in the license file is the same as that of the NE. Check the
command output to determine whether the license expires and whether the function items
specified in the license file are the same as the function items that have been applied for. If
they are not the same, apply for a new license file. Alternatively, you can use the License Tool
to check the license file offline.
----End
RNC. After an operation is complete, configurations will be synchronized to the backup
RNC over the Iur-p interface.
 The Node Redundancy licenses must be configured independently for dual-homed
NodeBs. Run the ADD UNODEBLICENSE command on the master RNC with

Users can export configuration data files of an NE using the NE LMT or WebLMT.
Alternatively, users can use the integrated CME to export configuration data files of NodeBs
and then import the data into the standalone CME.
Step 1 Obtain configuration data files of NEs including the master RNC, the backup RNC, and
NodeBs awaiting reconstruction.
Table 1.1 lists the methods for obtaining configuration files of different NEs.


Copyright © Huawei

2. Run the EXP CFGBCP
command to export the BCP
files.
You can specify the file save
path and file name. If you do not
specify them, you can check the
BCP file save path and file name
in the command output.
3. Click File Manager on the menu
bar. The File Manager window
is displayed.
4. Select a file save path in the
directory tree in the left pane,
and select the required BCP files
in the file list in the right pane.
5. Click Download and specify the
local target folder in the
displayed dialog box.
NodeB XML files CME For detailed operations on the
integrated CME, see "Exporting NE
Configuration Data" in CME
CME–CME Express window to add an NE file, as shown in Figure 2.1

Copyright © Huawei
Before starting import, you can add the master RNC, backup RNC, and NodeBs to Selected
NEs.
Step 4 Click OK to import the selected NE configuration files.
About 3 to 4 minutes are required to import the configuration file of an NE of different
version. After data is imported, the page is displayed, as shown in Figure 4.1.

Copyright © Huawei
----End

the standalone CME.
Step 2 In the displayed dialog box, select CP load sharing or Node Redundancy and click OK.
The RNC in Pool activation wizard is displayed, as shown in Figure 2.1.

Copyright © Huawei
Figure 2.1 RNC in Pool activation wizard

Copyright © Huawei
When the RNC in Pool Node Redundancy feature is to be enabled, the mutual-assistance OSP
relationship on the master RNC and the backup RNC will be added automatically. The assisting OSP is
configured for the backup RNC based on the following principles:
 If the RNC works only as the backup RNC, run the ADD OPC command with The Assist Type of
Signaling Point to ASSISTOR(ASSISTOR).
 If the RNC not only works as the backup RNC of a logical RNC, but also works as the master RNC
of the other logical RNC (for example, scenario 2), run the MOD OPC command with The Assist
Type of Signaling Point to MASTER_ ASSISTOR(MASTER_ASSISTOR).
 If the RNC works only as the master RNC of a logical RNC (for example, scenario 1), run the MOD
OPC command with The Assist Type of Signaling Point to ASSISTOR(ASSISTOR).
Step 4 Click the hyperlink Get the Template for Iur-p…The Get the Template for Iur-p dialog box
is displayed, as shown in Figure 4.1

Copyright © Huawei
select Node redundancy, and select the path to which the template is to be exported.
Step 6 Click Next.
The required MOCs are displayed and the quantities of the MOCs are calculated, and then the
quantity of each MOC of a single logical RNC for the Iur-p template is displayed, as shown in
Figure 6.1.
Figure 6.1 Setting the number of each MOC of a single logical RNC for the Iur-p template

Copyright © Huawei

Step 7 Adjust the number of MOCs and objects.

template.
Such common information must be planned in advance. Figure 3-16 shows an example.
 Only the Pool Name, the names of the master RNC and backup RNC corresponding to the logical
and backup RNC separately. Ensure that such information on both the RNCs are consistent.
Step 12 Fill the Iur-p link set (IURPLKS) in CommonData Sheet. Figure 3-17 shows an example.

Copyright © Huawei
Only the information about Iur-p link set from the master RNC to the backup RNC must be provided.
The CME will automatically generate the IURPLKS information on the master and backup RNC side
separately. Ensure that such information on both the RNCs are consistent.
corresponding to the master and backup RNCs.
Figure 3-18 shows an example.
Step 14 Select the edited RNC in Pool configuration data file and then click Next.
----End
3.4.5 Configuring Iu/Iur Interfaces

The general procedure for configuring the Iu/Iur user-plane data for the backup RNC is as
follows: Export the Iu/Iur configurations of the master RNC as the basic data of the backup
RNC, adjust the backup-RNC-specific planning data, and import such data into the backup
RNC. Perform the following operations:
The Export IuIur Interface Data dialog box is displayed, as shown in Figure 1.1.

Copyright © Huawei
The Iu and Iur interfaces support the following three interconnection schemes. You can choose one or
more of these schemes based on network configurations.
 Backup Routes: If transmission links have been configured from the backup RNC to the
CN, use the existing transmission links.
 Active and Standby Links: If this scheme is used to connect NEs of Ericsson, the SCTP
link port No. planned on the backup RNC must be different from that on the master
RNC. Otherwise, the interconnection fails.
 SCTP Dual-Homing Across Iur-p Interfaces: Before this scheme is used, reconfigure the
SCTP links over the Iu and Iur interfaces as dual-homing configurations. The CME
automatically changes the first local IP address and the second local IP address of SCTP
links on the master RNC to the correct first local IP address and the second local IP
address on the backup RNC, as shown in the following figure.
After the reconstruction, the first local IP address remains unchanged, for example, IP1
in the preceding figure. The second local IP address changes to the address on the backup

Copyright © Huawei
RNC, for example, IP5 in the preceding figure. For the BSC6910, set the Local IP
Distribution Type parameter to IP2_IN_PEER_NODE.
If Export by interface is selected, all Iu and Iur interface configurations of the physical
RNC will be exported. You are advised to select Export by interface when all the
following conditions are met: when a backup RNC is newly deployed, and all the Iu and
Iur data of the master RNC will be used on the backup RNC to create interface data.
 Specify the NE name and NE version of the master RNC, select Node redundancy, and
Export by filter mode, and then click Next. #toc457638125
The dialog box for selecting the object and interface type is displayed, as shown in
Figure 1.2.
If the backup route scheme is used, the objects carrying the same destination point index (DPX) have
been configured with Iu and Iur interfaces on the backup RNC, and therefore repeated object
configurations are not required.
objects to be exported on the DPX tab page. If the Iu-CS or Iu-PS interface is selected, select
the interface objects on both the DPX and Adjacent Node of IP Pool Network tab pages.
Only one interface type can be exported at a time.
Figure 3.1.

Copyright © Huawei
After the export is complete, the save path of the exported file is displayed, as shown in
Figure 4.1.
Figure 4.1 Successful interface data export
Step 5 Click the hyperlink for the path of the data file to find the exported file.
Step 7 Configure the Iu/Iur interface for the backup RNC based on the exported file and by following
instructions described in Table 1.1.

Copyright © Huawei
Table 1.1 Policies for configuring Iu/Iur interface based on the exported file of the master RNC
Transport Processing Based on the Exported Involved MOs
Networking Mode Data of the Master RNC
IP transmission Based on the network plan of the backup DEVIP, ETHIP,

RNC, add or update physical-layer and IPPOOL,
data-link-layer data and the planned IPPOOLIP, and
transmission resource pool data. SCRIPRT
Update control-plane data based on the M3LKS, M3LNK,
network plan of the backup RNC. M3RT, and
SCTPLNK uses the local and peer IP SCTPLNK
addresses and port numbers planned on
the backup RNC. M3LNK references the
newly planned SCTPLNK. M3LKS
references the newly planned M3LNK.
M3RT references the M3DE and
M3LKS newly planned on the backup
RNC.
Based on the existing configuration data ADJMAP,
of the backup RNC, check whether the ADJNODE, M3DE,
primary keys of objects conflict. If the M3LE, and N7DPC
primary keys of some objects conflict,
adjust the values of these primary keys.
ADJNODE needs to reference IPPOOL
planned on the backup RNC. ADJMAP
needs to reference the corresponding
ADJNODE on the backup RNC. For
N7DPC, if the active and standby links
scheme or the SCTP dual-homing
scheme is used, it needs to reference the
newly added assisted OSPs on the
backup RNC; if the backup route scheme
is used, it needs to reference the assisting
or host & assisting OSPs. For M3LE, if
the active and standby links scheme or
the SCTP dual-homing scheme is used, it
needs to reference assisted OSPs on the
backup RNC; if the backup routes
assisting or host & assisting OSPs on the
backup RNC. M3DE needs to reference
M3LE and N7DPC of the backup RNC.
configured on the backup RNC. If they TRMMAP
are not configured, configure them.
network plan of the backup RNC. AALRT

Copyright © Huawei

Networking Mode Data of the Master RNC
Update control-plane data based on the MTP3LNK,

network plan of the backup RNC. MTP3LKS,
MTP3LNK references the newly MTP3RT, and
planned SAALLNK. MTP3LKS SAALLNK
references the newly planned
MTP3LNK. MTP3RT references
N7DPC and MTP3LKS on the backup
RNC.
of the backup RNC, check whether the ADJNODE, and
primary keys of objects conflict. If the N7DPC
If ATM transmission is used, N7DPC
references the assisting or host &
assisting OSPs on the backup RNC.
ADJNODE references N7DPC from the
backup RNC to the CN. ADJMAP
references the corresponding newly
planned ADJNODE on the backup RNC.
In IP transmission mode, you need to fill common objects (such as DEVIP, ETHIP, or ETHTRK,
ETHTRKLNK, or ETHTRKIP) referenced by a transmission resource pool in the shared object file. In
ATM transmission mode, you need to fill the ATM traffic (ATMTRF) referenced by ATM links in the
shared object file.
The Import IuIur Interface Data dialog box is displayed, as shown in Figure 8.1. For details
about how to import an Iu/Iur data file into the CME for configuring the corresponding data
for the backup RNC, see "Importing an Iu/Iur Data Planning File" in CME Product
Documentation.

Copyright © Huawei
----End
3.4.6 Configuring Iub Data for the Backup RNC

To generate a configuration script for batch processing, you need to customize a summary
data file. The general configuration procedure is as follows: Fill data in the summary data file
based on the Iub data of NodeBs to be reconstructed under the master RNC, export the filled
data as the basic data of the backup RNC, adjust the basic data of the backup RNC, import the
data to the backup RNC, and import the summary data file to the CME.

Copyright © Huawei

3. In the displayed scenario list, select RNC in POOL Iub wizard.
4. On the first wizard page RNC in Pool Features to Be Enabled, select Enable node backup
or enabled load sharing and node backup at the same time, as shown in Figure 1.2.

Copyright © Huawei
After finishing the steps as prompted, the CME outputs a customization report. This report contains
− Click Save.
activation wizard.
Figure 2.1.

Copyright © Huawei
2. Specify Master RNC name, select the Node redundancy check box, select the NodeBs
to be reconstructed, and then click Next.
Next.
After the Iub data is exported, the hyperlink for the interface data file path is displayed.

Copyright © Huawei
1. Based on the network plan of the backup RNC, add or update physical-layer and data-
link-layer data and the planned transmission resource pool data in the exported Iub data
file, including ETHIP, DEVIP, SCRIPRT, IPPOOL, and IPPOOLIP. You also need
to update the interface control-plane data, including SCTPLNK, NCP, and CCP.
If the NodeBs to be reconstructed are enabled with the RAN Sharing or MOCN feature, the UNODEB
with the SharingType parameter set to RAN Sharing or MOCN can be configured only when the
switch for the UOPERATORSHARINGMODE parameter is turned on. Therefore, Sharing Type Of
NodeB in the Base Station Transport Data sheet is initially set to Exclusive and Cn Operator Index
is set to the ID of the primary operator.
activation wizard.
4. Import the edited Iub data file, and click Next.

Copyright © Huawei
check boxes, and click Next, as shown in Figure 3.2.
 If Best Effort is selected, the CME will import the dual-homed NodeBs with correct data only. To
ensure that all the dual-homed NodeBs of a batch are imported, you are advised to deselect Best
Effort.
 After the import is complete, the CME automatically modifies the NodeBs of the master RNC as
dual-homed.

Copyright © Huawei
2. Select the NodeB to be reconstructed, as shown in Figure 4.1.
configuration file, and click Custom MOC, as shown in Figure 4.2

Copyright © Huawei
To configure Iub data on the backup RNC, the following MOs are required: SCTP Link,
Control Port Bearer, NodeB Iub Control Port, IP Path, and IP Route (optional if
Layer 2 networking is used).
5. Click Next.
1. Modify data in the exported bulk configuration file, mainly the NodeB data of the SCTP
Link, Control Port Bearer, NodeB Iub Control Port, IP Path, and IP Route to the
backup RNC.
 The original exported data cannot be modified. You can only add new data.
 The attribute of Control Port Bearer is set to MASTER. When Control Port Bearer is referenced by
NodeB Iub Control Port, the attribute of Control Port Bearer is set to SLAVE.
The dialog box for importing Iub bulk configuration data is displayed. Specify the save
path of the bulk configuration file and upload the modified bulk configuration file, and
then click Next, as shown in #EN-US_TOPIC_0034583246/toc457638137
3. Select the NodeBs to be imported and then click Next, as shown in Figure 5.2.

Copyright © Huawei

----End

controllers and scripts for base stations.

Copyright © Huawei


Copyright © Huawei
Step 4 Right-click and choose Preactive Project to pre-activate the scripts.

To ensure that the controller script is correct, perform pre-activation checks.
----End

Copyright © Huawei


Copyright © Huawei
 3900 Series Base Station LMT User Guide > Maintaining the Base Station > Common
----End

Involved NEs: Backup RNC
The RNC-level data is required when a dual-homed NodeB is added on the backup RNC.
Therefore, the RNC-level data must be synchronized within the pool before the NodeB
addition. For information about data to be synchronized, see chapter 11 "Data
Synchronization Information for RNC in Pool" in RNC in Pool Feature Parameter
Description.
During the networking configuration, the CME will automatically detect the RNC in Pool
networking information and automatically create an RNC-level synchronization task. With the
synchronization task, initial data synchronization from the master RNC to the backup RNC
The RNC in Pool Configuration Management tab page is displayed, as shown in Figure
1.1. The synchronization task automatically created by the CME is displayed in the left
navigation tree. The synchronization tasks are named in the following format: Auto_master
RNC name(RNC ID)_overflow/backup RNC name.
Choose CME > UMTS Application > RNC in Pool Configuration instead of RNC Pool
Configuration.

Copyright © Huawei
Step 2 Select the automatic synchronization task and click to start data synchronization.
After the synchronization is complete, the data difference between the master RNC and
backup RNC is displayed in the right pane, as shown in Figure 2.1.

RNC.
 MOIDiff: indicates that the parameter is set on either the master RNC or on the overflow/backup
RNC, not on both.
Step 3 Click the Sync button to synchronize the configuration data of the master RNC to the backup
RNC. After the data is successfully synchronized, the result is displayed in the Result dialog
box, as shown in Figure 3.1

Copyright © Huawei
Step 4 Click to open the Configuration Sync Switch dialog box. Check whether Enable Auto
clients.
SyncDataCfgMode(BSC6900,BSC6910) is set to AutoSync(Auto Synchronization) on the
backup RNC.
----End
3.4.11 Synchronizing the NodeB-level Data Within a Pool

Involved NEs: Backup RNC

Copyright © Huawei
Logical cell data of a NodeB must be synchronized from the master RNC to the backup RNC.
For information about data to be synchronized, see chapter 11 "Data Synchronization
Information for RNC in Pool" in RNC in Pool Feature Parameter Description.
After dual-homed NodeBs are configured on the backup RNC, synchronize the NodeB-level
data from the master RNC to the backup RNC by manually performing a scheduled task.
During the synchronization, if any RNC-level data is updated on the master RNC, the update
will also be synchronized to the backup RNC.
If the scheduled synchronization task of the logical RNC has been created, go to Step 6. If
not, perform the following steps one by one.
The RNC in Pool Configuration Management tab page is displayed.
The synchronization tasks automatically created by the CME are displayed in the left pane.
The synchronization tasks are named in the following format: NodeBLvl_Sync_master RNC
name (master RNC ID)_backup RNC name, as shown in Figure 1.1.
 Synchronization tasks automatically created by the system are on a per RNC basis (that is, NodeBs
are not specified). When dual-homed NodeBs are reconstructed in batches, execute synchronization
tasks of the logical RNC upon completing each batch until all dual-homed NodeBs are
reconstructed.
 In RAN16.0 and later versions, the CME supports automatic creation of synchronization tasks. In
versions earlier than RAN16.0, synchronization tasks are created manually.
Step 2 On the menu bar of the U2000 client, choose Maintenance > Task Management. In the left
navigation tree, click CME and then double-click Pool Consistency Check. In the displayed
New Task dialog box, enter a task name, select Periodic for Execution Type, and click Next,
as shown in Figure 2.1

Copyright © Huawei
Figure 2.1 Creating a scheduled synchronization task
Step 3 Set Start time for the periodic task. It is good practice to perform the task during low-traffic
hours in the early morning. Set 1 for Execution interval. Click Next, as shown in Figure 3.1.
Two or more data synchronization tasks cannot be executed at the same time for the same BSC6910.
Therefore, it is recommended that the interval between the tasks be about 2 hours.
Figure 3.1 Setting the start time and interval for the periodic synchronization task

Copyright © Huawei
Step 4 In the displayed New Task dialog box, select RNC in Pool and click Next. Select the task
created in step 2 and click Finish, as shown in Figure 4.1.
Figure 4.1 Selecting a task
Step 5 View the task by choosing Task Type > CME > Pool Consistency Check in the left
navigation tree. Right-click the task and select Run Now to start the synchronization. After
the synchronization is finished, the Execution Result is displayed as Successful, as shown in
Figure 5.1.
Figure 5.1 Synchronization result
----End

Copyright © Huawei
 Differential data synchronization may be limited by the processing capacity of the operations
support system (OSS). If differential data to be synchronized are beyond the range, the following
message is displayed: "The number of records (xxxxxx) need to be synchronized exceeds the
maximum commands (360000) can be processed in RNC in hours." In this case, you need to
create manual tasks. While creating new tasks, you are advised to select Also show NodeBs and add
less than 100 NodeBs to be synchronized to the right box, as shown in the following figure.

SyncDataCfgMode(BSC6900,BSC6910) is set to AutoSync(Auto Synchronization)
on the backup RNC.

3.4.12.1 Backup Routes
 This scheme is only used when the CN device and neighboring RNC are provided by Huawei. If the
devices are not provided by Huawei, select a final scheme after referring the next two schemes.
 This scheme requires that the signaling transfer point (STP) forwarding function for the assisting
OSP of the backup RNC be activated on the CN and neighboring RNC sides.
The STP forwarding function is enabled by default on Huawei CN. Before executing the scheme, you
are advised to confirm with the CN maintenance staff whether the STP forwarding function has been
activated.
 The STP forwarding function can be activated on the neighboring RNC by running the
MOD N7DPC command with the STP parameter set to ON(ON). The operation affects
ongoing services carried on the backup RNC. Therefore, it is recommended that the STP
forwarding function be activated during off-peak hours.

Copyright © Huawei
Figure 5.2 Backup Iu routes
Figure 5.3 Backup Iur routes
Step 1 (Optional) Configure the control-plane links from the CN or neighboring RNC to the assisting
OSP of the overflow/backup RNC. Skip this step if the links have been configured.
 Configure the control-plane links from the CN or neighboring RNC to the assisting OSP
of the backup RNC.
 Enable the STP forwarding function for the assisting OSP of the backup RNC on the CN
or neighboring RNC.

Copyright © Huawei
Step 2 Configure backup routes from the CN or neighboring RNC to the OSP of the master RNC.
Configure a low-priority backup route to the OSP of the master RNC. The link sets used for
links from the CN or neighboring RNC to the assisting OSP are used on the backup route.
Check whether STP forwarding function for the assisting OSP of the backup RNC has been
enabled on the CN or neighboring RNC. If not, enable STP forwarding. Perform this
operation during off-peak hours because services carried on the backup RNC may be affected.
For example, if IP transmission is used on the Iu/Iur interface, run the ADD M3RT command
on the Huawei mobile switching center (MSC) and the neighboring RNC to add a backup
route to the OSP of the master RNC and set the priority of the backup route to be lower than
the priority of the existing route from the MSC or the neighboring RNC.
Step 3 Configure the user-plane links from the CN or neighboring RNC to the backup RNC.
 If the Iur interface uses ATM transmission, run the ADD ADJNODE command with Is
Root Node set to YES(Root Node) and Is Route Mode set to YES(Route Mode) for
the backup RNC and run the ADD AAL2RT command with Destination ATM Address
set to the ATM address of the backup RNC and Adjacent Node ID set to the adjacent
node ID of the backup RNC to add an AAL2 route. Run the ADD ADJNODE command
on the master RNC with Is Root Node set to YES(Root Node) and Route Mode set to
BYAAL2RT(AAL2 Route) and run the ADD AAL2RT command with Destination
ATM Address set to the ATM address of the master RNC and Adjacent Node ID set to
the adjacent node ID of the master RNC. If the neighboring RNC does not support AAL2
route configuration with the adjacent node functioning as the root node, after a NodeB
control switchover, only the adjacent node (the RNC that has obtained the NodeB
control) and user-plane links need to be configured. The Iur user plane is unavailable
before the configuration is done.
 If the Iur interface is IP-based, an IP path to the backup RNC needs to be added on the
neighboring RNC, when IP paths are used on the user plane. The Adjacent Node ID
parameter must be set to adjacent node ID used for the IP path between the master RNC
and the neighboring RNC. If a transmission resource pool is used on the user plane, do
not modify the configurations on the neighboring RNC.
Step 4 Configure a path for the UE-not-involved relocation on the Iu-PS interface.
Involved NEs: Neighboring RNC
If IP paths are used on the Iu-PS user plane of the neighboring RNC, IP paths and IP routes
over the Iu-PS interface of the backup RNC must be configured on the neighboring RNC. For
details, see "Configuring a Path for Static SRNC Relocation" in BSC6900 UMTS Initial
Configuration Guide. If a transmission resource pool is used on the Iu-PS interface of the
neighboring RNC, configuring a path for the UE-not-involved relocation is not required.
Figure 4.1 shows the UE-not-involved relocation in RNC in Pool networking.

Copyright © Huawei
Figure 4.1 UE-not-involved relocation in RNC in Pool networking
As shown in the preceding figure, assume that only IP1 is configured for the Iu-PS interface
of P_RNC1, and only IP2 is configured for the Iu-PS interface of P_RNC2. Assume that
P_RNC3 is a BSC6900, only IP3 is configured for the Iu-PS interface of P_RNC3, and
P_RNC3 is a neighboring RNC of L_RNC1.
L_RNC1. For the neighboring RNC to support the UE-not-involved relocation, an IP path
from IP3 to IP1 and an IP route to IP1 must have been configured on P_RNC3.
After P_RNC1 and P_RNC2 are pooled, IP2 can also be used on the Iu-PS interface of
L_RNC1. Therefore, an IP path from IP3 to IP2 and an IP route to IP2 need to be configured
on P_RNC3. If IP3' and IP2' are also configured on the Iu-PS interfaces of P_RNC3 and
P_RNC2, respectively, you also need to configure IP paths from IP3 to IP2', from IP3' to IP2,
and from IP3' to IP2', and configure an IP route to IP2'.
----End
3.4.12.2 Active and Standby Links
 This scheme is applicable to the CN device and neighboring RNC provided by non-Huawei vendors.
Therefore, this scheme is the most mature scheme on the live network.
 This scheme imposes requirements on the following NEs and has an impact on services.
The links used by the master RNC and backup RNC halve. If the CN node does not provide sufficient
links, capacity risk may occur during the deployment. Therefore, pre-assessment is required. For
example, the Cisco's CN node provides eight links. When this scheme is adopted to connect Huawei
devices to Cisco's CN, the master RNC and the backup RNC each only uses four links. Therefore,
service processing may fail eventually.
When Huawei devices are connected to the non-Huawei CN, a link unusable alarm may be reported on
the CN. When Huawei devices are connected to Ericsson's CN, no alarm is reported.

Copyright © Huawei
 When Huawei devices are connected to some vendors' CN, the configuration may be
limited. Therefore, a sound communication with customers is required before the
deployment. For example, when Huawei devices are connected to Ericsson's CN, peer
port No. (the CN's SCTP port No.) on the master RNC and backup RNC cannot be the
same.
 Configure the control-plane links from the CN or neighboring RNC to the assisted OSP
of the backup RNC.
Configure the control-plane links from the CN or neighboring RNC to the assisted OSP
of the backup RNC.
 Configure the user-plane links from the CN or neighboring RNC to the overflow/backup
RNC.
This operation is same as that in 3.4.12.1Backup Routes"3.4.12.1Backup Routes."
 Configure a path for the UE-not-involved relocation on the Iu-PS interface.
If IP paths are used on the Iu-PS user plane of the neighboring RNC, IP paths and IP
routes over the Iu-PS interface of the backup RNC must be configured on the
neighboring RNC. For details, see "Configuring a Path for Static SRNC Relocation" in
BSC6900 UMTS Initial Configuration Guide. If a transmission resource pool is used on
the Iu-PS interface of the neighboring RNC, do not configure a path for the UE-not-

Copyright © Huawei
involved relocation. This operation is same as that in 3.4.12.1Backup

Routes"3.4.12.1Backup Routes."
3.4.12.3 SCTP Dual-homing
 This scheme imposes no requirements on neighboring NEs and has no impact on services.
of the backup RNC.
− Modify the setting of the SCTP links from the CN and the neighboring RNC to the
master RNC to dual-homed.
− Set the peer secondary IP address of the RNC to the IP address of the backup RNC.
 Configure the control-plane links from the CN or neighboring RNC to the backup RNC.
Configure the user-plane links from the CN or neighboring RNC to the overflow/backup
RNC. This operation is same as that in 3.4.12.1Backup Routes"3.4.12.1Backup Routes."
3.4.13 Activating Node Redundancy

Before activating Node Redundancy, ensure that:

Copyright © Huawei
 RNC-level data has been synchronized within the pool. If data has not been
synchronized, perform Step 2 to Step 4 in section 2.4.10Synchronizing the RNC-level
Data Within a Pool"2.4.10Synchronizing the RNC-level Data Within a Pool." It is
recommended that the DSP URNCPOOLDATASYNC command be executed on the
master RNC to query whether data has been synchronized. If data has not been
synchronized, perform the steps described in section 2.4.10Synchronizing the RNC-level
Data Within a Pool"2.4.10Synchronizing the RNC-level Data Within a Pool."
 The configuration data between the master RNC and the backup RNC is consistent. If an
ALM-706 Inconsistent RNC in Pool Configuration alarm is reported on the U2000,
manually perform data synchronization on the CME. For the detailed procedures, see
section 5.6Manually Synchronizing RNC in Pool Data"5.6Manually Synchronizing RNC
in Pool Data."
 The license information for RNC in Pool has been synchronized. To verify whether the
license information synchronization is successful, run the COL LOG command on the
backup RNC and set Log File Type to BSC_INFO(The Basic Information of the
BSC). If the license information about the logical RNC is contained in the log, the
license information synchronization is successful. If an ALM-20759 POOL License
Information Synchronization Failure alarm is reported, troubleshoot the problem.
 The configurations of dual-homed NodeBs within the pool are normal. If an ALM-22235
Dual-Homed NodeB Configuration Incorrect alarm is reported on the master RNC or
backup RNC, you are advised to troubleshoot the problem before activation so that
services are normal after NodeB control switchover.
 If the Iu/Iur/Iub interface uses IP transmission, check whether the Iu/Iur/Iub DIP
synchronization switch has been turned on on the master RNC. To turn on the Iu/Iur/Iub
DIP synchronization switch, run the SET TNSOFTPARA command with
IuIurDIPSynSw(UMTS BSC6900, UMTS BSC6910) and IubDIPSynSw(UMTS
BSC6900, UMTS BSC6910) set to ON. After this switch is turned on, the backup RNC
obtains the peer IP address and performs transmission detection before processing
services. If transmission on the Iu/Iur/Iub interface of the backup RNC fails, an ALM-
21392 Adjacent Node IP Address Ping Failure alarm is reported to inform the customer
to rectify the fault, thereby avoiding service interruption due to transmission failure after
switchover to the backup RNC. The Iub DIP synchronization function is applicable only
in scenarios where Layer 3 networking is used between a NodeB and the master RNC
and between the NodeB and the backup RNC and there are reachable routes between all
user-plane IP addresses of the NodeB and the master and backup RNCs. If the CME
detects that the Iu fault of the backup RNC affects the RNC in Pool node redundancy
function, it reports an ALM-22307 RNC in Pool Function Unavailable alarm with the
cause value of "Faulty Iu-CS control plane of the backup RNC", " Faulty Iu-CS user
plane of the backup RNC", " Faulty Iu-PS control plane of the backup RNC", or "Faulty
Iu-PS user plane of the backup RNC."
 The Service Configuration Object Inc. Alarm Switch is turned on. If it is not, run the
SET URRCTRLSWITCH on the master RNC in advance with
SEROBJCFG_NOT_CMP_ALM_REPORT_SWITCH under the FunctionSwitch
parameter selected.
 If the node redundancy is set to the automatic mode, the transmission detection is
enabled on the master and backup RNCs.
 If the Iu control-plane uses the cross-Iur-p standby Iu and Iur paths in an SCTP dual-
homing solution, ensure that the ping detection on the Iu signaling plane on the backup
RNC function is enabled. By default, the function is enabled for automatic node
redundancy. You can run the LST TNSOFTPARA command to verify whether the
function is enabled. If it is not, run the SET TNSOFTPARA command with Auto
Redundancy Enable under the BackupRncIuSigPingPolicy parameter selected to turn
on the function.

Copyright © Huawei
 If the Iu uses IP transmission, check whether the ping detection is enabled.

Generally, the function is enabled by default.
For BSC6900s, you can run the following commands to query IP path configurations on
the Iu-CS and Iu-PS interfaces, respectively: LST IPPATH:ITFT=IUCS and LST
IPPATH:ITFT=IUPS. Ensure that IP path detection is enabled for each IP path on the
Iu interface. If this function is not enabled for an IP path, you can run the MOD
IPPATH command to enable it.
For BSC6910s, you can run the following commands to query adjacent node configurations
on the Iu-CS and Iu-PS interfaces, respectively: LST ADJNODE:NODET=IUCS and LST
ADJNODE:NODET=IUPS. Ensure that ping detection is enabled for each adjacent node on
the Iu interface. If this function is not enabled for an adjacent node, you can run the MOD
ADJNODE command to enable it.
 If ATM transmission is used on the Iu interface, ensure that SAAL transmission detection
is enabled on the backup RNC. The function is enabled by default. You can run the LST
TNSOFTPARA command to verify whether the function is enabled. If it is not, run the
SET TNSOFTPARA command with BackupRncSaalTransDetectSw set to ON to turn
on the function.
 The check results for RNC in Pool configurations have been confirmed on the CME.

In manual NodeB control switchover mode, run the SET UPOOLREDUNDANCY
command on the master RNC with Redundancy Mode set to Manual(Manual).
In automatic NodeB control switchover mode, run the SET UPOOLREDUNDANCY
command on the master RNC with Redundancy Mode set to Automatic(Automatic).
 Ensure that the values of Redundancy Mode on the master and backup RNCs are the
same. To do so, check whether an ALM-706 Inconsistent RNC in Pool Configuration
alarm is reported on the CME. If such an alarm is reported, manually synchronize data
between the master and backup RNCs on the CME.
 In automatic NodeB control switchover mode, check whether ALM-22307 RNC in Pool
Function Unavailable is reported on the master RNC. If such an alarm is reported, clear
the alarm by referring to alarm handling suggestions.
 After activating the RNC in Pool feature, check its configurations again on the CME for
correctness.
3.5 Acceptance
Before checking the RNC in Pool topology, perform the following operations to synchronize NEs on the
CME: Log in to the U2000, choose CME > Current Area > Synchronize NEs, and then select physical
RNCs shown in the following figure to synchronize NEs in the current area.

Copyright © Huawei
successful.
report to solve the problem. Then, perform the following steps to check the RNC in Pool
topology:

Copyright © Huawei
----End
 SET SYS: SUPPORTRNCINPOOL=SUPPORT, POOLNAME="XXX";
 SET NODE:NID=XX, NNAME="XX;
 ADD EXTNODE:ENID=XX, ENNAME="XX";
 If the statuses shown in the table are inconsistent with actual configurations, run the following
commands to check whether the master RNC and overflow/backup RNC of the same logical RNC
are correctly configured and match with each other:
 ADD URNCBASIC: LoadSharingType=XX, RedundancyType=XX;
 ADD URNCMAP: ENID=XX, LoadSharingType=XX, RedundancyType=XX;

Copyright © Huawei


page.
 In versions earlier than R15, the CME automatically creates an autosync task for each logical RNC.
In R15 and later, the CME automatically creates two autosync tasks for logical RNCs supporting
Node Redundancy. One task is RNC-level and the other task is NodeB-level.
 The NodeB-level synchronization task contains information about dual-homed NodeBs. If one of the
following unexpected situations occurs, create manual tasks to rectify the exception.
 Scenario 1: The ID and name of a dual-homed NodeB are inconsistent on the master RNC and
backup RNC, resulting that the CME fails to identify the dual-homed NodeB.
 Scenario 2: The dual-homed NodeB is only configured for the master RNC but not for the backup
RNC. When the NodeB-level synchronization task is executed, an error message is displayed on the
CME. The CME only supports the error check function in R15B240 and later.
 Scenario 3: The specification of the dual-homed NodeB is beyond the processing capability, and
therefore the task fails.

Step 3 Click .

Copyright © Huawei
Enable Auto Sync.
----End

Management window. Log in to the U2000, choose Maintenance > Task Management,
select Pool Consistency check on the left, and check the status of different tasks according to
task name.

Step 1 Run the LST LICENSE command to check whether the licenses for Load Sharing and Node
Redundancy in the master and backup license files are activated.
----End

whether the Iur-p transmission delay meets the requirements. For details, see section 5.2Iur-p
Methods."

Copyright © Huawei

correctly.
 ALM-22388 Configuration of Service Objects Incomplete
 ALM-21392 Adjacent Node IP Address Ping Failure
 ALM-22390 Redundancy Switchover of Logical RNC Control
 EVT-22944 Logical RNC Control Switchover
 ALM-22235 Dual-Homed NodeB Configuration Incorrect
 ALM-22392 Backup RNC Hardware Capacity Reaching the Limit in RNC in Pool Node
Redundancy

data integrity and data consistency between the master RNC and the overflow/backup RNC.
To check the RNC in Pool configurations, perform the following operations:

----End

Copyright © Huawei

3.5.8 Accepting Node Redundancy

The Redundancy Mode can be set to Manual(Manual) or Automatic(Automatic). No
matter the redundancy mode is set to manual or automatic, the acceptance is based on ATP
cases (To obtain such cases, visit http://support.huawei.com.).
 Manual switchover of NodeB control has two cases: a NodeB control switchover from
the master RNC to the backup RNC and from the backup RNC to the master RNC.
 Automatic switchover of NodeB control has four cases:
− A NodeB switchover control from the master RNC to the backup RNC when the
master RNC is faulty caused by power off in the equipment room.
− A NodeB switchover control from the backup RNC to the master RNC when the
backup RNC is faulty caused by power off in the equipment room.
− A NodeB switchover control from the master RNC to the backup RNC when the Iu
interface is faulty between the master RNC and the CN triggered by the Iu interface
failure.
interface is faulty between the backup RNC and the CN triggered by the Iu interface
failure.
 If scenario verification based on ATP cases is not allowed, it is recommended that you
perform the following checks after the deployment:
Step 1 Run the DSP UHOSTRNC command on the master/backup RNC to query the control rights
of a logical RNC.
of a logical RNC. If a large number of NodeBs are involved, the system performance may be
affected. You can skip this step or choose some NodeBs to query the status.
Step 3 Select an available dual-homing NodeB on the master RNC, start Iub tracing and check
whether the NBAP_RNC_POOL_MSG message is transmitted properly on a regular basis.
----End

Copyright © Huawei
 Considering the effect of node redundancy on the network, especially automatic redundancy, you are
advised to perform the acceptance upon an agreement with customers.
 When the switchover of NodeB control cannot be identified, the preceding status-checking steps
only indicate that relevant operations required for the deployment have been configured, but whether
standby links over interfaces after the switchover are functional cannot be guaranteed.
 The following process takes the L_RNC1 as an example.
Step 1 Run the DSP UHOSTRNC command on the P_RNC1 to query the control right of L_RNC1.
Conclusion: P_RNC1 (the master RNC) owns the control right of L_RNC1.
Step 3 Run the DSP UNODEB command on the P_RNC1 to query the homing status of the NodeB.

Copyright © Huawei
Conclusion: P_RNC1 (the master RNC) owns the control right of the NodeB.
Step 5 Start Iub tracing on the P_RNC1 to check whether the NBAP_RNC_POOL_MSG message is
transmitted regularly.
The preceding figures are just for reference.

 Performance measurement results for device and transmission objects are reported on the physical
RNC. Performance measurement results for radio objects are always reported on the physical RNC
that has obtained the NodeB control. After the control right is switched back to the backup RNC,
performance counters can only be found on the backup RNC (for example, NodeB\CELL).
3.6 Procedures for Rolling Back Node Redundancy

3.6.1 Deactivation
Deactivating Node Redundancy:
When NodeB control switchovers are triggered manually, run the FOC UHOSTRNC
command on the master RNC to make sure that the control right has been switched back to
the master RNC, and then run the SET UPOOLREDUNDANCY command with
Redundancy Mode set to NO_Redundancy(NO_Redundancy) to disable Node
Redundancy.

Copyright © Huawei
When NodeB control switchovers are triggered automatically, run the

SETUPOOLREDUNDANCY command on the master RNC and backup RNC with
Redundancy Mode set to Manual(Manual), and then use the manual operation method to
disable Node Redundancy.

configurations of the logical RNC from the backup RNC. If N master RNCs are involved,
perform the following steps for these RNCs one by one.
3.6.2.1 Networking Rollback for Manual Redundancy

Step 1 Run the FOC UHOSTRNC command on the master RNC to forcibly obtain the NodeB
control. Run the REL UHOSTRNC command on the P_RNC2 to forcibly release the NodeB
control.
Step 2 Run the SETUPOOLREDUNDANCY command on the master RNC and backup RNC with
Redundancy Mode set to NO_Redundancy(NO_Redundancy).
Step 3 Run the EXP URMVRNCDATA command on the backup RNC to export the script (for
workspace. Run the RUN BATCHFILE command on the backup RNC to execute the
exported script.
Step 4 Run the RMV SRCIPRT and RMV DEVIP commands on the backup RNC. When link
Step 5 Run the MOD UNODEB command on the master RNC with NodeB Host Type set to
SINGLEHOST(SingHost) for dual-homed NodeBs. Run the MOD OPC command on the
P_RNC1 with The Host Type of Signaling Point to SINGLEHOST(SINGLEHOST).
Step 6 If cross-Iur-p standby Iu and Iur paths in the SCTP dual-homing solution are used, run the
RMV M3LNK, RMV SCTPLNK, ADD SCTPLNK, and ADD M3LNK commands to
reconfigure SCTP and MTP3 user adaption layer (M3UA) links.
Step 8 Run the RMV URNCMAP command on the master RNC to remove the mapping relationship
between a logical RNC and a physical RNC.
external RNC.
Step 10 Run the SET SYS command on the master RNC and backup RNC with Support RNC in
Step 11 Remove backup Iu/Iur interface configurations for the logical RNC from the CN and the
neighboring RNC.
Step 12 Remove the data over the standby Iub interface from the NodeB.

Copyright © Huawei
----End
3.6.2.2 Networking Rollback for Automatic Redundancy

Step 1 When NodeB control switchovers are triggered automatically, run the SET
UPOOLREDUNDANCY command on the master RNC with Redundancy Mode set to
Manual(Manual). Run the SET URNCPOOLCFGCTRL command on the backup RNC
with Data Synchronization Mode set to ManualCfg(Manual Configuration), and then run
the SET UPOOLREDUNDANCY command with Redundancy Mode set to
Manual(Manual).
control. Run the REL UHOSTRNC command on the backup RNC to forcibly release the
NodeB control.
Step 3 Run the SETUPOOLREDUNDANCY command on the master RNC and backup RNC with
Redundancy Mode set to NO_Redundancy(NO_Redundancy).
Step 4 Run the EXP URMVRNCDATA command on the backup RNC to export the script (for
workspace. Run the RUN BATCHFILE command on the backup RNC to execute the
exported script.
Step 5 Run the RMV SRCIPRT and RMV DEVIP commands on the backup RNC. When link
P_RNC1 with The Host Type of Signaling Point to SINGLEHOST(SINGLEHOST).
reconfigure SCTP and M3UA links.
external RNC.
Step 11 Run the SET SYS command on the master RNC and backup RNC with Support RNC in
Step 12 Remove backup Iu/Iur interface configurations for the logical RNC from the CN and the
neighboring RNC.

Copyright © Huawei
 The script exported by running the EXP URMVRNCDATA command can be used to remove the
following configurations for a logical RNC from the backup RNC: NodeB-level data synchronized
from the master RNC within the pool, Iub user-plane objects of the backup RNC (ADJMAP,
TRMFACTOR, TRMMAP, and ADJNODE), Iub control-plane objects of the backup RNC
(UNCP, UCCP, and SAALLNK/SCTPLNK), assisted OSP on the backup RNC, RNC-level data
synchronized from the master RNC within the pool, Iur-p links, mapping between the logical RNC
and the physical RNC, and information about the logical RNC and external physical RNC.
 If the configurations for the logical RNC need to be restored immediately after being removed, run
the RUN BATCHFILE command to execute the generated rollback script
 If a physical RNC within a pool carries the backup RNCs of multiple logical RNCs at the same time,
remove all related configurations of all the logical RNCs and then you can run the SET SYS
command on the master RNC with Support RNC in Pool set to NOT_SUPPORT(Not_Support).
----End

Copyright © Huawei
Engineering Guidelines for Load Sharing and Node
RedundancyEngineering Guidelines for Load Sharing
RNC in Pool Reconstruction Guide (RAN18.1) and Node Redundancy
4 Engineering Guidelines for Load Sharing

and Node Redundancy

4.3 Preparation
4.4 Procedures for Load Sharing and Node Redundancy Reconstruction
4.5 Acceptance
4.6 Procedures for Rolling Back Load Sharing and Node Redundancy

considered.
 When Load Sharing and Node Redundancy are both enabled, the overflow RNC and backup RNC of
a logical RNC must be carried by the same physical RNC.
 The CME only supports the scenarios where Load Sharing and Node Redundancy are both enabled.
The CME does not support the following scenarios.
 Enabling Node Redundancy when Load Sharing has been enabled.
 Enabling Load Sharing when Node Redundancy has been enabled.
4.1.1 Scenario 1: N Master RNCs and An Overflow/Backup RNC

Carrying Multiple Logical RNCs
example to describe the configurations.
 The BSC6910 functioning as an overflow/backup RNC can be either a newly deployed
RNC or a legacy RNC.

Copyright © Huawei
 If multiple RNCBASIC MOs are configured on a BSC6910 working as an overflow

RNC, the BSC6910 must be enabled with the WRFD-150240 RNC in Pool Multiple
Logical RNCs feature and provided with license with this feature.
Three master RNCs (P_RNC1, P_RNC2, and P_RNC3) and an overflow/backup RNC
(P_RNC4) are pooled. Three logical RNCs (L_RNC1, L_RNC2, and L_RNC3) are
respectively mapped to the overflow/backup RNC and each of the master RNCs, as shown in
Figure 14.1.
Figure 14.1 Three master RNCs and an overflow/backup RNC carrying multiple logical RNCs
S Befor Before After Load A

u e Load Sharing and ft
bs Depl Sharin Node er
ce oyme g and Redundancy D
n nt Node Activation e
ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt

C Maste Logical C
R r RNCs R
A RNCs A
T T

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt
1. RNC- O backu
1. in- _S p
1 Pool H routes
scenar A
ios R
E
+
N
O
_
R
ed
un
da
nc
y
1. RNC- O active
1. in- _S and
2 Pool H standb
scenar A y
ios R links
E
+
N
O
_
R
ed
un
da
nc
y
1. RNC- O SCTP
1. in- _S dual-
3 Pool H homin
scenar A g
ios R
E
+

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt
N
O
_
R
ed
un
da
nc
y
1. RNC- O backu
1. in- _S p
4 Pool H routes
scenar A
ios R
E
+
N
O
_
R
ed
un
da
nc
y
1. RNC- O active
1. in- _S and
5 Pool H standb
scenar A y
ios R links
E
+
N
O
_
R
ed
un
da

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt
nc
y
1. RNC- O SCTP
1. in- _S dual-
6 Pool H homin
scenar A g
ios R
E
+
N
O
_
R
ed
un
da
nc
y
4. N+1 UO N U Backu UO M
1. Load P_ p
1. Sharin S routes
7 g H
(UP) A
+ R
Node E
Redun +
dancy M
(back an
up ua
routes l/
) A
ut
o
m
ati
c
4. N+1 UO N U Activ UO M
1. Load P_ e and
1. Sharin S standb
8 g H y

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt
(UP) A links
+ R
Node E
Redun +
dancy M
(activ an
e and ua
standb l/
y A
links) ut
o
m
ati
c
4. N+1 UO N U SCTP UO M
1. Load P_ dual-
1. Sharin S homin
9 g H g
(UP) A
+ R
Node E
Redun +
dancy M
(SCT an
P ua
dual- l/
homin A
g) ut
o
m
ati
c
If the logical RNC attribute changes after Load Sharing and Node Redundancy are activated, the
attributes before and after the activation are highlighted. The number of master RNCs changing from N
to M indicates the specification changes of logical RNCs. For example, a 2+1 pool changes to a 3+1
pool.

Copyright © Huawei
 In this scenario, the two physical RNCs must be BSC6910s.

 The two physical RNCs must be enabled with the WPFD-150240 RNC in Pool Multiple Logical
RNCs feature and provided with license for this feature.
 The two physical RNCs can both be newly deployed RNCs or legacy RNCs.
Alternatively, one is a newly deployed RNC and the other one is a legacy RNC.
A logical RNC (L_RNC1) is mapped to a master RNC (P_RNC1) and an overflow/ backup
RNC (P_RNC2), and the other logical RNC (L_RNC2) is mapped to a master RNC
(P_RNC2) and an overflow/backup RNC (P_RNC1), as shown in Figure 14.2.
Figure 14.2 Two physical RNCs carrying two logical RNCs

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt

C Maste Logical C
R r RNCs R
A RNCs A
T T
4. Non- UO 2 N No UO 2
1. RNC- O backu

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt
2. in- _S p
1 Pool H routes
scenar A
ios R
E
+
N
O
_
R
ed
un
da
nc
y
1. RNC- O active
2. in- _S and
2 Pool H standb
scenar A y
ios R links
E
+
N
O
_
R
ed
un
da
nc
y
1. RNC- O SCTP
2. in- _S dual-
3 Pool H homin
scenar A g
ios R
E
+
N

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt
O
_
R
ed
un
da
nc
y
1. RNC- O backu
2. in- _S p
4 Pool H routes
scenar A
ios R
E
+
N
O
_
R
ed
un
da
nc
y
1. RNC- O active
2. in- _S and
5 Pool H standb
scenar A y
ios R links
E
+
N
O
_
R
ed
un
da
nc

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt
y
1. RNC- O SCTP
2. in- _S dual-
6 Pool H homin
scenar A g
ios R
E
+
N
O
_
R
ed
un
da
nc
y

must be BSC6910s.
 Two BSC6910s functioning as overflow/backup RNCs can be newly deployed RNCs or
legacy RNCs.
 The two BSC6910s working as overflow/backup RNCs must be enabled with the
WRFD-150240 RNC in Pool Multiple Logical RNCs feature and provided with license
for this feature.
14.3.

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt

C Maste Logical C
R r RNCs R
A RNCs A
T T
1. RNC- O backu
3. in- _S p
1 Pool H routes

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt
scenar A
ios R
E
+
N
O
_
R
ed
un
da
nc
y
1. RNC- O active
3. in- _S and
2 Pool H standb
scenar A y
ios R links
E
+
N
O
_
R
ed
un
da
nc
y
1. RNC- O SCTP
3. in- _S dual-
3 Pool H homin
scenar A g
ios R
E
+
N
O
_

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt
R
ed
un
da
nc
y
1. RNC- O backu
3. in- _S p
4 Pool H routes
scenar A
ios R
E
+
N
O
_
R
ed
un
da
nc
y
1. RNC- O active
3. in- _S and
5 Pool H standb
scenar A y
ios R links
E
+
N
O
_
R
ed
un
da
nc
y

Copyright © Huawei

ar Redun pl
io dancy o
N Activa y
o. tion m
e
nt
1. RNC- O SCTP
3. in- _S dual-
6 Pool H homin
scenar A g
ios R
E
+
N
O
_
R
ed
un
da
nc
y

Copyright © Huawei

Figure 14.4 Process of Load Sharing and Node Redundancy reconstruction
 Iu/Iur interface reconstruction involves operations on the peer CN and neighboring RNCs.
Therefore, ensure that O&M personnel of the peer nodes are available.
 Iu-BC interface reconstruction does not involve the CBC server, but ensure O&M
personnel of the peer nodes are available as well. The operations involving the CBC
server are performed after the control rights are switched to the backup RNC. For details,
see section 5.4Iu-BC Solution When RNC in Pool Node Redundancy is Enabled"5.4Iu-
BC Solution When RNC in Pool Node Redundancy is Enabled."
 If a large number of NodeBs need to be reconstructed, you are advised to reconstruct Iub
interfaces in batches. It is recommended that the number of NodeBs to be reconstructed

Copyright © Huawei
be no more than 50 for the first batch and no more than 100 for later batches. The
number of batches to be performed can be adjusted as required.
 During the preceding reconstruction processes, the project duration can be adjusted as
required. It is recommended that reconstruction of different interfaces be performed
separately. It is also recommended that interface reconstruction be performed in low-
traffic hours because reconstruction will affect ongoing services. However, projects may
differ in time plan. If certain interfaces cannot be reconstructed during low-traffic hours,
you are advised to ensure that Iu interfaces are reconstructed during low-traffic hours.
Reconstruction time for other interfaces can be adjusted as required.
concurrently. Vertical operations must be performed serially. When logical RNC
interfaces of these RNCs.
reconstruction. Therefore, you are advised to use the CME to configure reconstruction
scripts. Traditionally, only Iub interfaces are reconstructed based on standalone CMEs
and other reconstructions are reconstructed using MML commands. For details about

Copyright © Huawei
Figure 14.5 Estimated time for Load Sharing and Node Redundancy reconstruction
 Required time listed in the preceding figure is for reference only. Operation personnel need to
estimate required time based on site conditions.
 The time required for Iub reconstruction can be used as a reference for later reconstruction with 100
NodeBs per batch.
 Section 5.7X Project Deployment Solution"5.7X Project Deployment Solution" is an example.
4.2.2 Rollback Process

4.2.2.1 Deactivating Load Sharing or Node Redundancy
After Load Sharing or Node Redundancy is enabled, you can roll back by deactivating it due
to problems, such as exceptions, less-than-expected benefits, or other O&M issues. Activate
the feature again after problems are resolved.

Copyright © Huawei


Copyright © Huawei
Figure 14.6 Networking rollback for Load Sharing and Node Redundancy

Copyright © Huawei
4.3 Preparation
 Because the Iu-PS interface between the BSC6910 and SGSN only supports IP
transmission, if the master RNC is BSC6900 and the ATM transmission mode is used on
the Iu-PS interface, the ATM transmission is reconstructed to IP transmission before
deployment.
 If the SCTP dual-homing scheme is used for deploying Node Redundancy, configure
dual-homed SCTP links over Iu and Iur interfaces on the master RNC.
reconstruction.
4.4 Procedures for Load Sharing and Node Redundancy

Reconstruction
This section describes the detailed procedures for Load Sharing and Node Redundancy
reconstruction. The following steps apply to all scenarios, unless otherwise specified.
For details, see 4.4.1Preparing License Files"4.4.1Preparing License Files."
For details, see 4.4.2Activating License Files"4.4.2Activating License Files."
For details, see 4.4.3Backing Up Data and Preparing Tools"4.4.3Backing Up Data and
Preparing Tools."
Step 4 Reconstruct Iur-p interfaces.
Interfaces."
5. Activate Iur-p configuration data on the master RNC and overflow/backup RNC.

Copyright © Huawei
7. Run the DSP ADJNODEPING command to check whether the Iur-p user plane is in the
normal state.
8. Check whether new alarms are reported on the master RNC and overflow/backup RNC,
including ALM-21606 IURP Link Fault, ALM-21607 External Node Unreachable, and
ALM-21608 IURP Link Congestion. If new alarms are reported, clear them.
Pool"4.4.10Synchronizing the RNC-level Data Within a Pool." After the synchronization is
Step 6 Reconstruct Iu/Iur interfaces.
For details, see section 4.4.5Configuring Iu/Iur Interfaces"4.4.5Configuring Iu/Iur
Interfaces."
5. Activate Iu/Iur configuration data on the master RNC and overflow/backup RNC.
7. Run the SET TNSOFTPARA command on the master RNC and overflow/backup RNC
with the IuIurDIPSynSw parameter set to ON to turn on the Iu/Iur DIP synchronization
switch.
8. Run the CHK SERINTEG command on the overflow/backup RNC to check whether
the Iu/Iur interface configuration is complete.
9. Check on the overflow/backup RNC and peer CN/neighboring RNCs whether the Iu/Iur
status is normal. The N7DPC and SCTPLNK must be available and M3LNK must be in
the deactivated state.

Copyright © Huawei
10. Check whether new alarms are reported on the master RNC and overflow/backup RNC,
Step 7 (Optional) Reconstruct the Iu-BC interface (perform this step only when the master RNC is
configured with the Iu-BC interface).
1. Run the ADD DEVIP command on the overflow/backup RNC to add an IP address for
the interface board on the CBC server.
2. Run the MOD UCBSADDR command on the overflow/backup RNC to change the CBS
RNC IP address and the second CBS RNC IP address (when the CBC server supports
Node Redundancy) to the IP address for the interface board in the preceding step.
3. Add related configurations on the peer CBC server.
For details, see section 5.4Iu-BC Solution When RNC in Pool Node Redundancy is
Enabled"5.4Iu-BC Solution When RNC in Pool Node Redundancy is Enabled."
Step 8 Reconstruct Iub interfaces.
For details, see section 4.4.6Configuring Iub Interfaces"4.4.6Configuring Iub Interfaces."
5. Activate Iub configuration data on the master RNC, the backup/overflow RNC, and
NodeBs awaiting configuration.
6. Run the ADD UNODEBLICENSE command on the master RNC with
7. Run the SET TNSOFTPARA command on the master RNC with the IubDIPSynSw
parameter set to ON to turn on the DIP synchronization switch.
8. Run the following command on the master RNC to turn on the switch for reporting
ALM-22388 Service Configuration Object Incomplete:
SET
URRCTRLSWITCH:FunctionSwitch=SEROBJCFG_NOT_CMP_ALM_REPORT_SWIT
CH-1;
9. Check whether new alarms are reported on the master RNC and the overflow/backup
RNC, including ALM-21392 Adjacent Node IP Address Ping Failure, ALM-22388
Configuration of Service Objects Incomplete, and ALM-22235 Dual-Homed NodeB
Configuration Incorrect. If new alarms are reported, clear them.

Copyright © Huawei
Step 9 Synchronize NodeB-level data within a pool.

For details, see section 4.4.11Synchronizing the NodeB-level Data Within a
Pool"4.4.11Synchronizing the NodeB-level Data Within a Pool."
Step 10 Run the SET URRCTRLPHYSWITCH command on the master RNC and backup RNC
with NODE_REDUNDANCY_CAPACITY_CHECK_SWTICH selected under the
OptimizationSwitch parameter to enable the capacity check function for the RNC in Pool
Node Redundancy feature.
Step 11 Activate Load Sharing and Node Redundancy.
For details, see section 4.4.13Activating Load Sharing and Node
Redundancy"4.4.13Activating Load Sharing and Node Redundancy."
Step 12 Perform reconstruction acceptance.
For details, see 4.5Acceptance"4.5Acceptance."
----End
You can configure and commission the common transmission of the interfaces to be reconstructed
independently first and then perform the rest of interface reconstruction operations.

 To enable the RNC in Pool Load Sharing and Node Redundancy features (including both
control-plane load sharing and user-plane load sharing), the corresponding license
control items listed in the following table must be applied for. The control item is a
software license item and therefore you only need to apply for it in the license file of the
master RNC of the corresponding logical RNC.
ID Name Item ID Item Name Allocation Unit
for
Multiple
Operators
WRFD- RNC in LQW1R RNC in BSC6900 License per 500

150211 Pool Load PLSRES Pool Load BSC6910 control Active
Sharing Sharing (per items that user
Active User) cannot be
configured
based on
operators
150212 Pool Node PNRRES Pool Node BSC6910 control NodeB
Redundancy Redundancy items that
(per NodeB) cannot be
configured
based on
operators

Copyright © Huawei
 If the overflow/backup RNC uses the feature WRFD-150240 RNC in Pool Multiple
Logical RNCs, you also need to apply for the following corresponding license control
items. The control item is a hardware license item and therefore you need to apply for it
in the license files of the corresponding physical nodes enabled with the feature WRFD-
150240 RNC in Pool Multiple Logical RNCs.
Feature Feature License Control NE License Sales
ID Name Control Item Name Allocation Unit
Item ID for
Multiple
Operators

150240 Pool PMLRR Pool control Logic
Multiple ES Multiple items that RNC
Logical Logical cannot be
RNCs RNCs (per configured
RNC) based on
operators
The number of license control items of WRFD-150240 RNC in Pool Multiple Logical RNCs
equals the number of logical RNCs minus one on a BSC6910. Scenario 1 is used as an
example. In Figure 14.1, the P_RNC4 carries three logical RNCs. Therefore, two Multiple
Logical RNCs license control items need to be purchased in the hardware license file of the
P_RNC4.
be applied for:
BOM Code License ID License Name License Application
82203572 LQW1HWCL03 RNC Throughput Mandatory if the user-plane

Hardware Capacity load sharing function or the
(per 50Mbps) Node Redundancy feature
is enabled
82203573 LQW1HWCL04 RNC Active User Mandatory
Hardware Capacity
(per 1000 Active
Users)
82203729 LGW1DPIHC02 Network Optional unless the NIU
Intelligence board is used
Processing
Throughput (per
50Mbps)
82204003 LQW1RPMLRRES RNC in Pool Optional unless the feature
Multiple Logical WRFD-150240 RNC in
RNCs (per RNC) Pool Multiple Logical
RNCs is used
81201592 LQW1UPCPDS01 RNC User Plane Optional unless the feature
and Control Plane WRFD-141201 RNC User
Dynamic Sharing Plane and Control Plane
Dynamic Sharing is used

Copyright © Huawei
new service volume the BSC6910 is going to share as an overflow RNC, the service
volume after the NodeB control is switched from the master RNC to the backup RNC,
and new network intelligence throughput. For details, see RNC in Pool Configuration
Principle.
 When a network is shared by multiple operators, the features WRFD-150211 RNC in
Pool Load Sharing and WRFD-150240 RNC in Pool Multiple Logical RNCs cannot be
used exclusively for one operator. If both the features are used, they must be used for all
the operators configured on an RNC. Therefore, the preceding license control items are
not operator-specific and the license usage of the primary operator indicates the license
usage of all operators.
 The following figures show the logic of processing license files of the master RNC and
overflow/backup RNC in different scenarios.

Copyright © Huawei

Copyright © Huawei
Figure 12.2 Logic of processing the license file of the overflow/backup RNC
following tables.

P_RNC1 Master RNC

P_RNC2 Master RNC
P_RNC3 Master RNC
P_RNC4 Overflow/Backup RNC

Copyright © Huawei

P_RNC1 Master RNC+Overflow/Backup RNC


P_RNC1 Master RNC

P_RNC2 Master RNC
P_RNC3 Master RNC
P_RNC4 Master RNC
online mode when the SCU boards of MPSs are normally running. (A hardware ESN is a string of
20 characters with the service ID being NULL.)
 If you need to add master RNCs on an overflow/backup RNC after the deployment of Load Sharing
and Node Redundancy, see section 1.7.3NE Licenses"1.7.3NE Licenses" for detailed operations.
 Application for licenses other than those of the feature RNC in Pool is not provided here and the
application rules are the same as those for licenses of non-RNC-in-Pool networkings.
 If license control items Network Intelligence Processing Throughput (per 50Mbps) and RNC User
Plane and Control Plane Dynamic Sharing are required, apply for them by following the processing
principles for other control items of the backup license file.

 Prepare required license files of the master RNC and overflow/backup RNC and active
them separately by following the instructions provided in 4.4.1Preparing License
Files"4.4.1Preparing License Files." Perform the following steps to activate the license
files on the NE side:

Copyright © Huawei

license file. Check whether the ESN specified in the license file is the same as that of the NE.
Check the command output to determine whether the license expires and whether the function
items specified in the license file are the same as the function items that have been applied for.
If they are not the same, apply for a new license file. Alternatively, you can use the License
Tool to check the license file offline.
----End
RNC. After an operation is complete, configurations will be synchronized to the
overflow/backup RNC over the Iur-p interface.
 The Node Redundancy licenses are configured for dual-homed NodeBs individually.
Run the ADD UNODEBLICENSE command on the master RNC with

Users can export configuration data files of an NE using the NE LMT or WebLMT.
Alternatively, users can use the integrated CME to export configuration data files of NodeBs
and then import the data into the standalone CME.
Step 1 Obtain configuration data files of NEs including the master RNCs, the overflow/backup
RNCs, and the NodeBs awaiting reconstruction. Table 1.1

NE Type File Type Configuration Procedure
Tool

2. Run the EXP CFGBCP command to
export the BCP files.

Copyright © Huawei
NE Type File Type Configuration Procedure

Tool
You can specify the file save path and file

name. If you do not specify them, you
can check the BCP file save path and file
name in the command output.
3. Click File Manager on the menu bar.
The File Manager window is displayed.
4. Select a file save path in the directory
tree in the left pane, and select the
required BCP files in the file list in the
right pane.
5. Click Download and specify the local
target folder in the displayed dialog box.
NodeB XML files CME For detailed operations on the integrated
CME, see "Exporting NE Configuration
Data" in CME Product Documentation.
CME–CME Express window to add an NE file, as shown in Figure 2.1

Copyright © Huawei
Before starting import, you can add the master RNC, the overflow/backup RNC, and NodeBs
to Selected NEs.
Step 4 Click OK to import the selected NE configuration files. About 3 to 4 minutes are required to
import the configuration file of an NE of different version. After data is imported, the page is
displayed, as shown in Figure 4.1

Copyright © Huawei
----End

the standalone CME.
Step 2 In the displayed dialog box, select UP load sharing or Node Redundancy and click OK. The
RNC in Pool activation wizard is displayed, as shown in Figure 2.1.

Copyright © Huawei
Figure 2.1 RNC in Pool activation wizard

Copyright © Huawei
Step 4 In the displayed dialog box, click the hyperlink Get the Template for Iur-p…The Get the
Template for Iur-p dialog box is displayed, as shown in Figure 4.1
Step 5 Specify BSC6910 version and its corresponding Master RNC Count (An RNC ID indicates
a logical master RNC. For details about how to calculate the number of logical RNCs, see the
following notes), as well as BSC6900 version and its corresponding Master RNC count,
select Node redundancy and UP load sharing, and select the path to which the template to
be exported.
Step 6 Click Next.

Copyright © Huawei
Step 7 The required MOCs are displayed and the quantities of the MOCs are calculated, and then the
quantity of each MOC of a single logical RNC for the Iur-p template is displayed, as shown in
Step 5.
----End
Figure 7.1 Setting the number of each MOC of a single logical RNC for the Iur-p template


template.

Copyright © Huawei
 Enter the Pool Name.

 Enter the Master RNC Name, Overflow RNC Name, Backup RNC Name.
 Enter Node Id, Node Name, and RNC Name.
 The CME during the import will automatically generate URNCBASIC, URNCMAP, NODE, and
EXTNODE information for the master RNC and overflow/backup RNC separately. Such
information on the RNCs is consistent.
Step 5 Fill the Iur-p link set (IURPLKS) in CommonData Sheet. Figure 5.1 shows an example.
Only the information about Iur-p link set from the master RNC to the backup RNC must be provided.
The CME will automatically generate the IURPLKS information on the master and backup RNC side
separately. Ensure that such information on the master RNC and overflow/backup RNC is consistent.
corresponding to the master and backup RNCs. Figure 6.1

Copyright © Huawei
Step 7 If user-plane load sharing is enabled, fill the the Iur-p user-plane transmission information in
the sheets corresponding to the master RNC and the overflow RNC. Currently, the Iur-p user
plane supports only the transmission resource pool. Figure 7.1 shows an example.
Figure 7.1 Filling in Iur-p user-plane transmission information
You can use the default value of the TRMMAP or TRMFACTOR index indicated by the Iur-p user-
plane ADJMAP. However, you are advised to manually specify the value of TRMMAP or
TRMFACTOR as required by the transport networking plan at a site and references such a value in the
table.
Step 8 Select the edited RNC in Pool configuration data file and then click Next.
----End

Copyright © Huawei
 When the RNC in Pool Node Redundancy feature is to be enabled, the mutual-assistance OSP
relationship on the master RNC and the backup RNC will be added automatically. The assisting OSP
is configured for the backup RNC based on the following principles:
 If the RNC works only as the backup RNC, run the ADD OPC command with The
Assist Type of Signaling Point to ASSISTOR(ASSISTOR).
 If the RNC not only works as the backup RNC of a logical RNC, but also works as the
master RNC of the other logical RNC, run the MOD OPC command with The Assist
Type of Signaling Point to ASSISTOR(ASSISTOR).
 Modifying the assist type of signaling point has no impact on the existing services of the
RNC.
4.4.5 Configuring Iu/Iur Interfaces

The general procedure for configuring the Iu/Iur user-plane data for the backup RNC is as
follows: Export the Iu/Iur configurations of the master RNC as the basic data of the backup
RNC, adjust the backup-RNC-specific planning data, and import such data into the backup
RNC. Perform the following operations for each logical master RNC one by one.
The dialog box for exporting Iu/Iur data is displayed, as shown in Figure 1.1.
The Iu/Iur interface supports the following three interconnection schemes. You can choose one or more
of these schemes based on network configurations.
 Backup Routes: If transmission links have been configured from the backup RNC to the CN, use the
existing transmission links.
 Active and Standby Links: If this scheme is used to connect NEs of Ericsson, the SCTP link port No.
planned on the backup RNC must be different from that on the master RNC. Otherwise, the
interconnection fails.

Copyright © Huawei
 SCTP Dual-Homing Across Iur-p Interfaces: Before this scheme is used, reconfigure the SCTP links
over the Iu/Iur interface as dual-homing configurations. The CME automatically changes the first
local IP address and the second local IP address of SCTP links on the master RNC to the correct first
local IP address and the second local IP address on the backup RNC, as shown in the following
figure.
After the reconstruction, the first local IP address remains unchanged, for example, IP1 in the preceding
figure. The second local IP address changes to the address on the backup RNC, for example, IP5 in the
preceding figure. For the BSC6910, set the Local IP Distribution Type parameter to
IP2_IN_PEER_NODE.
If Export by interface is selected, all Iu and Iur interface configurations of the physical RNC will be
exported. You are advised to select Export by interface when all the following conditions are met:
 A new backup RNC is deployed.
 All the Iu and Iur data of the master RNC will be used on the backup RNC to create user-
plane data.
Step 2 Specify the NE name and NE version of the master RNC, select UP load sharing, Node
redundancy, and Export by filter mode. And then click Next.
The dialog box for selecting the object and interface type is displayed, as shown in Figure 2.1.

Copyright © Huawei
If the backup route scheme is used, the objects carrying the DPX have been configured with Iu and Iur
interfaces on the backup RNC, and therefore repeated object configurations are not required.
objects to be exported on the Peer IP Address of IP Path tab page. If the Iu-CS or Iu-PS
interface is selected, select the interface objects on both the DPX and Adjacent Node of IP
Pool Network tab pages. Only one interface type can be exported at a time.
Figure 4.1.
After the export is complete, the save path of the exported file is displayed, as shown in
Figure 5.1.

Copyright © Huawei
Figure 5.1 Successful interface data export
Step 6 Click the hyperlink for the path of the data file to find the exported file.
Step 8 Configure the interface data for the backup RNC based on the exported file and by following
instructions described in the following figures and table.
 COMMON sheet
− M3LE: Five parameters are involved. These five parameters are not related with
the master RNC, and are planned and modified based on data on the backup RNC.
− TRMMAP: TRMMAP ID is planned based on the backup RNC and does not
conflict with others. The specific value of the priority is configured by referring to
interfaces of the master RNC. In general, values of the priority are the same on the
master RNC and the backup RNC. However, the specific per-hop behavior (PHB)
strategy is decided upon an agreement with customers.
− IPPOOL: Modify these parameters based on data on the backup RNC and do not
conflict with these on the backup RNC.
− IPPOOLIP: Matches with IPPOOL. The control-plane IP address by the backup
RNC is used as the IP address planned.
− SRCIPRT: Adds a route for the address of the backup RNC and modify the
address, address type, and next hop.
− IUCS/IUPS/IUR sheet

Copyright © Huawei
 N7DPC: Indicates node redundancy schemes. Different originating point codes (OPCs)
are referenced by N7DPC.
 The assisting or master assisting OPCs are referenced by the backup route scheme. The
assisted OPCs are referenced by the active and standby link scheme and SCTP dual-
homing scheme. Referenced OPCs are adjusted based on different schemes. The indexes
and values of destination point codes (DPCs) are modified base on specific planning.
 ADJNODE: ADJNODE ID and referenced pools are adjusted based on the planning of
the backup RNC. In general, it is recommended that the sharing type and resource
management type of the logical RNC be configured to share.
 M3DE: M3LE is referenced by M3DE. Data is planned and cited indexes are adjusted
based on M3LE on the backup RNC.
 M3LKS: M3DE is referenced by M3LKS, which is adjusted based on the data on the
backup RNC.
 ADJMAP: TRMMAP is referenced by ADJMAP, which is adjusted based on the data
on the backup RNC.
 M3RT: M3RT is associated with M3DE and M3LKS. The parameter values are
adjusted based on the preceding configurations.
 M3LNK: M3LNK is associated with M3LKS and SCTP links. Link index No. is
adjusted based on the planned data on the backup RNC.
 SCTPLNK: The parameter values are adjusted based on the planned IP address and port
No. on the backup RNC.
Table 1.1 Policies for configuring Iu/Iur interface based on the exported file of the master RNC
Networking Data of the Master RNC
IP transmission Based on the network plan of the backup DEVIP, ETHIP,

RNC, add or update physical-layer and IPPOOL,
data-link-layer data and the planned IPPOOLIP, and
transmission resource pool data. SCRIPRT
Update control-plane data based on the M3LKS, M3LNK,
network plan of the backup RNC. M3RT, and
SCTPLNK uses the local and peer IP SCTPLNK
addresses and port numbers planned on
the backup RNC. M3LNK references the
newly planned SCTPLNK. M3LKS
references the newly planned M3LNK.
M3RT references the M3DE and
M3LKS newly planned on the backup
RNC.

Copyright © Huawei


of the backup RNC, check whether the ADJNODE, M3DE,
primary keys of objects conflict. If the M3LE, and N7DPC
ADJNODE needs to reference IPPOOL
planned on the backup RNC. ADJMAP
needs to reference the corresponding
ADJNODE on the backup RNC. For
N7DPC, if the active and standby links
scheme or the SCTP dual-homing
newly added assisted OSPs on the
backup RNC; if the backup route scheme
is used, it needs to reference the assisting
or host & assisting OSPs. For M3LE, if
active and standby links or the SCTP
dual-homing scheme is used, it needs to
reference assisted OSPs on the backup
RNC; if master and backup routes are
used, it needs to reference the assisting or
host & assisting OSPs on the backup
RNC. M3DE needs to reference M3LE
and N7DPC of the backup RNC.
network plan of the backup RNC. AALRT
Update control-plane data based on the MTP3LNK,
network plan of the backup RNC. MTP3LKS,
MTP3LNK references the newly MTP3RT, and
planned SAALLNK. MTP3LKS SAALLNK
references the newly planned
MTP3LNK. MTP3RT references
N7DPC and MTP3LKS on the backup
RNC.
of the backup RNC, check whether the ADJNODE, and
primary keys of objects conflict. If the N7DPC
If ATM transmission is used, N7DPC
references the assisting or host &
assisting OSPs on the backup RNC.
ADJNODE references N7DPC from the
backup RNC to the CN. ADJMAP
references the corresponding newly
planned ADJNODE on the backup RNC.

Copyright © Huawei

Check whether common objects are TRMFACTORT and

configured on the backup RNC. If they RMMAP
In IP transmission mode, you need to fill common objects (such as DEVIP, ETHIP, or ETHTRK,
ETHTRKLNK, or ETHTRKIP) referenced by a transmission resource pool in the shared object file. In
ATM transmission mode, you need to fill the ATM traffic (ATMTRF) referenced by ATM links in the
shared object file.
The Import IuIur Interface Data dialog box is displayed, as shown in the following figure.
For details about how to import an Iu/Iur data file into the CME for configuring the
corresponding data for the backup RNC, see "Importing an Iu/Iur Data Planning File" in CME
----End
4.4.6 Configuring Iub Interfaces

Before configuring Iub interfaces, you are advised to ensure that Iub physical transmission
links from NodeBs to the overflow/backup RNC are ready to work; NodeBs and the
overflow/backup RNC are mounted to the U2000.
To generate a configuration script for batch processing, you need to customize a summary
data file. The general configuration procedure is as follows: Fill data in the summary data file
based on the Iub data of NodeBs to be reconstructed under the master RNC, export the filled

Copyright © Huawei
data as the basic data of the backup RNC, adjust the basic data of the backup RNC, import the
data to the backup RNC, and import the summary data file to the CME. If N master RNCs are
involved, perform the following steps for these RNCs one by one.

3. In the displayed window, select RNC in POOL Iub wizard.
4. On the first wizard page RNC in Pool Features to Be Enabled, select Enable only UP
load sharing, as shown in Figure 1.2.

Copyright © Huawei
After finishing the steps in the wizard, the CME outputs a customization report. This report contains
− Click Save.
activation wizard.
Figure 2.1.

Copyright © Huawei
2. Specify Master RNC name, select UP load sharing and Node redundancy, select the
NodeBs to be reconstructed, and then click Next.
Next.
After the Iub data is exported, the hyperlink for the interface data file path is displayed.

Copyright © Huawei
1. Based on the network plan of backup RNCs, add or update physical-level and data-link-
level data and the planned transmission resource pool data in the exported Iub data file,
including ETHIP, DEVIP, SCRIPRT, IPPOOL, and IPPOOLIP, and update control-
plane interface data, including SCTPLNK, NCP, and CCP.
If the NodeBs to be reconstructed are enabled with the RAN Sharing or MOCN feature, the UNODEB
with the SharingType parameter set to RAN Sharing or MOCN can be configured only when the
switch for the UOPERATORSHARINGMODE parameter is turned on. Therefore, Sharing Type Of
NodeB in the Base Station Transport Data sheet is initially set to Exclusive and Cn Operator Index
is set to the ID of the primary operator.
activation wizard.
4. After the edited Iub data file is imported, click Next.

Copyright © Huawei
check boxes, and then click Next, as shown in Step 3.5
If Best Effort is selected, the CME will import the dual-homed NodeBs with correct data only. To
ensure that all the dual-homed NodeBs of a batch are imported, you are advised to deselect Best Effort.
After the import is completed, the CME will automatically change UNodeB to the dual-homed NodeB
on the master RNC side.

Copyright © Huawei
2. Select the NodeB to be reconstructed, as shown in Figure 4.1.
 This step must be performed in the planned data area. Otherwise, the function will be disabled. For
details about how to create a planned data area, see section 5.3Creating a Planned Data Area."
− The attribute of Control Port Bearer is set to MASTER. When Control Port Bearer
is referenced by NodeB Iub Control Port, the attribute of Control Port Bearer is set
to SLAVE.
configuration file, and click Custom MOC, as shown in Figure 4.2.

Copyright © Huawei

To configure Iub data on the backup RNC, SCTP Link, Control Port Bearer, NodeB
Iub Control Port, IP Path, and IP Route MOs are required(optional if Layer 2
networking is used).
5. Click Next.
1. Modify data in the exported bulk configuration file, mainly the NodeB data of the SCTP
Link, Control Port Bearer, NodeB Iub Control Port, IP Path, and IP Route to the
backup RNC.
The original exported data cannot be modified. You can only add new data.
Pool activation wizard. The dialog box for importing Iub bulk configuration data is
displayed. Specify the save path of the bulk configuration file and upload the modified
bulk configuration file, and then click Next, as shown in Figure 5.1

Copyright © Huawei
3. Select the NodeBs to be imported and then click Next, as shown in Figure 5.2

----End

controllers and scripts for base stations.

Copyright © Huawei


Copyright © Huawei
Step 4 Right-click and choose Preactive Project to pre-activate the scripts. To ensure that the
controller script is correct, perform pre-activation checks.
----End

Copyright © Huawei


Copyright © Huawei
3900 Series Base Station LMT User Guide > Maintaining the Base Station > Common
----End

Involved NEs: Overflow/backup RNC.
The RNC-level data is required for adding a dual-homed NodeB on the overflow/backup
RNC. Therefore, the RNC-level data must be synchronized within the pool before the NodeB
addition. For information about data to be synchronized, see chapter 11 "Data
Description.
During the networking configuration, the CME will automatically detect the RNC in Pool
networking information and automatically create an RNC-level synchronization task. With the
synchronization task, initial data synchronization from the master RNC to the backup RNC
Configuration Management. The RNC in Pool Configuration Management tab page is
displayed, as shown in Figure 1.1. The synchronization task automatically created by the
CME is displayed in the left navigation tree. The synchronization tasks are named in the
following format: Auto_master RNC name(RNC ID)_overflow/backup RNC name.
Choose CME > UMTS Application > RNC in Pool Configuration instead of RNC Pool
Configuration.

Copyright © Huawei
Step 2 Select the automatic synchronization task and click to start data synchronization. After the
synchronization is complete, the data difference between the master RNC and
overflow/backup RNC is displayed in the right pane, as shown in Figure 2.1

RNC.
 MOIDiff: indicates that the parameter is set on either the master RNC or on the
overflow/backup RNC, not on both.
Step 3 Click the Sync button to synchronize the configuration data of the master RNC to the
overflow/backup RNC. After the data is successfully synchronized, the result is displayed in
the Result dialog box, as shown in Figure 3.1.

Copyright © Huawei
Step 4 Click to open the Configuration Sync Switch dialog box. Check whether Enable Auto
clients.
 Before performing data synchronization, ensure that the SyncDataCfgMode parameter on the
overflow/backup RNC is set to AutoSync(Auto Synchronization).
----End
4.4.11 Synchronizing the NodeB-level Data Within a Pool

Involved NEs: Overflow/backup RNC.

Copyright © Huawei
Logical cell data of a NodeB must be synchronized from the master RNC to the
overflow/backup RNC. For information about data to be synchronized, see chapter 11 "Data
Description.
After dual-homed NodeBs are configured on the overflow/backup RNC, synchronize the
RNC-level data and NodeB-level data from the master RNC to the overflow/backup RNC by
manually performing a scheduled task. If N master RNCs are involved, perform the following
steps for these RNCs one by one.
If the scheduled synchronization task of the logical RNC has been created, go to Step 6. If
not, perform the following steps one by one.
Configuration Management. The RNC in Pool Configuration Management tab page is
displayed.
The synchronization task automatically created by the CME is displayed in the left navigation
tree. The synchronization tasks are named in the following format: NodeBLvl_Sync_master
RNC name (RNC ID)_overflow RNC name, as shown in #toc457638192.
 Synchronization tasks automatically created by the system are on a per RNC basis (that is, NodeBs
are not specified). When dual-homed NodeB's reconstruction is performed in batches, execute
synchronization tasks of the logical RNC per batch until all dual-homed NodeBs are reconstructed.
 In RAN16.0 and later versions, the CME supports automatic creation of synchronization
tasks. In versions earlier than RAN16.0, synchronization tasks are created manually.
Step 2 On the menu bar of the U2000 client, choose Maintenance > Task Management. In the left
navigation tree, click CME and then double-click Pool Consistency Check. A New Task
dialog box is displayed. Enter a task name, select Periodic for Execution Type, and click
Next, as shown in Figure 2.1

Copyright © Huawei
Figure 2.1 Dialog box for creating a synchronization task
Step 3 Set Start time for the periodic task. It is good practice to perform the task during low-traffic
hours in the early morning. Set 1 for Execution interval. Click Next, as shown in Figure 3.1.
Two or more data synchronization tasks cannot be executed at the same time for the same BSC6910.
Therefore, it is recommended that the interval between the tasks be about 2 hours.
Figure 3.1 Setting the start time and interval for the periodic synchronization task

Copyright © Huawei
Step 4 In the displayed New Task dialog box, select RNC in Pool and click Next. Select the task
created in step 2 and click Finish, as shown in Figure 4.1
Figure 4.1 Selecting a task
Step 5 In the left navigation tree, choose Task Type > CME > Pool Consistency Check to view the
task. Right-click the task and select Run Now to start the synchronization. After the
synchronization is finished, the Execution Result is displayed as Successful, as shown in
Figure 5.1
Figure 5.1 Synchronization result
----End

Copyright © Huawei
 Differential data synchronization may be limited by the processing capacity of the operations
support system (OSS). If differential data to be synchronized are beyond the range, the following
message is displayed: "The number of records (xxxxxx) need to be synchronized exceeds the
maximum commands (360000) can be processed in RNC in hours." In this case, you need to
create manual tasks. While creating new tasks, you are advised to select Also show NodeBs and add
less than 100 NodeBs to be synchronized to the right box, as shown in the following figure.
 Before performing data synchronization, ensure that the SyncDataCfgMode parameter on the
overflow/backup RNC is set to AutoSync(Auto Synchronization).

4.4.12.1 Backup Routes
 This scheme is only used when the CN device and neighboring RNC are provided by Huawei. If the
devices are not provided by Huawei, select a final scheme after referring the next two schemes.
 This scheme requires that the STP forwarding function for the assisting OSP of the backup RNC be
activated on the CN and neighboring RNC sides.
 The STP forwarding function is enabled by default on Huawei CN. Before executing the scheme,
you are advised to confirm with the CN maintenance staff whether the STP forwarding function has
been activated.
 The STP forwarding function can be activated on the neighboring RNC by running the MOD
N7DPC command with the STP parameter set to ON(ON). The operation affects ongoing services
carried on the backup RNC. Therefore, it is recommended that the STP forwarding function be
activated during off-peak hours.

Copyright © Huawei
Figure 5.2 Backup Iu route configuration
Figure 5.3 Backup Iur route configuration
 (Optional) Configure the control-plane links from the CN or neighboring RNC to the
assisting OSP of the overflow/backup RNC. Skip this step if the links have been
configured.
− Configure the control-plane links from the CN or neighboring RNC to the assisting
OSP of the overflow/backup RNC.
− Enable the STP forwarding function for the assisting OSP of the overflow/backup
RNC on the CN or neighboring RNC.

Copyright © Huawei
 Configure backup routes from the CN or neighboring RNC to the OSP of the master
RNC.
Configure a low-priority backup route to the OSP of the master RNC. The link sets used
for links from the CN or neighboring RNC to the assisting OSP are used on the backup
route. Check whether STP forwarding function for the assisting OSP of the backup RNC
has been enabled on the CN or neighboring RNC. If not, enable STP forwarding.
Perform this operation during off-peak hours because services carried on the backup
RNC may be affected.
For example, if IP transmission is used on the Iu and Iur interfaces, run the ADD M3RT
command on the Huawei mobile switching center (MSC) and the neighboring RNC to
add a backup route to the OSP of the master RNC and set the priority of the backup route
to be lower than the priority of the existing route from the MSC or the neighboring RNC.
RNC.
RNC.
 If the Iur interface uses ATM transmission, run the ADD ADJNODE command with Is
Root Node set to YES(Root Node) and Is Route Mode set to YES(Route Mode) for
the backup RNC and run the ADD AAL2RT command with Destination ATM Address
set to the ATM address of the backup RNC and Adjacent Node ID set to the adjacent
node ID of the backup RNC to add an AAL2 route. Run the ADD ADJNODE command
on the master RNC with Is Root Node set to YES(Root Node) and Route Mode set to
BYAAL2RT(AAL2 Route) and run the ADD AAL2RT command with Destination
ATM Address set to the ATM address of the master RNC and Adjacent Node ID set to
the adjacent node ID of the master RNC. If the neighboring RNC does not support AAL2
route configuration with the adjacent node functioning as the root node, after a NodeB
control switchover, only the adjacent node (the RNC that has obtained the NodeB
control) and user-plane links need to be configured. The Iur user plane is unavailable
before the configuration is done.
 If the Iur interface is IP-based, an IP path to the backup RNC needs to be added on the
neighboring RNC, when IP paths are used on the user plane. The Adjacent Node ID
parameter must be set to adjacent node ID used for the IP path between the master RNC
and the neighboring RNC. If a transmission resource pool is used on the user plane, do
not modify the configurations on the neighboring RNC. You are advised to follow user-
plane data configuration rules for the IP-based Iur interface.
If IP paths are used on the Iu-PS user plane of the neighboring RNC, IP paths and IP routes
over the Iu-PS interface of the backup RNC must be configured on the neighboring RNC. For
details, see "Configuring a Path for Static SRNC Relocation" in BSC6900 UMTS Initial
Configuration Guide. If a transmission resource pool is used on the Iu-PS interface of the
neighboring RNC, configuring a path for the UE-not-involved relocation is not required.
Figure 5.4 shows the UE-not-involved relocation in RNC in Pool networking.

Copyright © Huawei
Figure 5.4 UE-not-involved relocation in RNC in Pool networking
As shown Figure 5.4, assume that only IP1 is configured for the Iu-PS interface of P_RNC1,
and only IP2 is configured for the Iu-PS interface of P_RNC2. Assume that P_RNC3 is a
BSC6900, only IP3 is configured for the Iu-PS interface of P_RNC3, and P_RNC3 is a
neighboring RNC of L_RNC1.
L_RNC1. For the neighboring RNC to support static relocation, an IP path from IP3 to IP1
and an IP route from IP3 to IP1 must be configured on P_RNC3. After P_RNC1 and P_RNC2
are pooled, IP2 can also be used on the Iu-PS interface of L_RNC1. Therefore, an IP path
from IP3 to IP2 and an IP route from IP3 to IP2 are configured on P_RNC3.
If IP3' and IP2' are also configured on the Iu-PS interfaces of P_RNC3 and P_RNC2,
respectively, you also need to configure IP paths from IP3 to IP2', from IP3' to IP2, and from
IP3' to IP2', and configure an IP route to IP2'.
4.4.12.2 Active and Standby Links
Therefore, this scheme is the most mature scheme on the live network.
 This scheme imposes requirements on the following NEs and has an impact on services.
 The links used by the master RNC and overflow/backup RNC halve. If the CN node does not
provide sufficient links, capacity risk may occur during the deployment. Therefore, pre-assessment
is required. For example, the Cisco's CN node provides eight links. When this scheme is adopted to
connect to Cisco's CN, the master RNC and the backup RNC each only uses four links. Therefore,
service processing may fail eventually.
 When Huawei devices are connected to the non-Huawei CN, a link unusable alarm may be reported
on the CN. When Huawei devices are connected to Ericsson's CN, no alarm is reported.
 When Huawei devices are connected to some vendors' CN, the configuration may be limited.
Therefore, a sound communication with customers is required before the deployment. For example,
when Huawei devices are connected to Ericsson's CN, peer port No. (the CN's SCTP port No.) on
the master RNC and overflow/backup RNC cannot be the same.

Copyright © Huawei
of the overflow/backup RNC.
Configure the control-plane links from the CN or neighboring RNC to the assisted OSP
RNC.
RNC. This operation is same as that in 4.4.12.1Backup Routes"4.4.12.1Backup Routes."

Copyright © Huawei
4.4.12.3 SCTP Dual-homing
 This scheme imposes no requirements on neighboring NEs and has no impact on services.
− Modify the setting of the SCTP links from the CN and the neighboring RNC to the
master RNC to dual-homed.
− Set the peer secondary IP address of the RNC to the IP address of the backup RNC.
 Configure the control-plane links from the CN or neighboring RNC to the
overflow/backup RNC.
RNC.
This operation is same as that in 4.4.12.1Backup Routes"4.4.12.1Backup Routes."

Copyright © Huawei
4.4.13 Activating Load Sharing and Node Redundancy

Load Sharing and Node Redundancy are activated after all the conditions specified in
2.4.12.1Pre-Activation Checks"2.4.12.1Pre-Activation Checks" and 3.4.13.1Pre-Activation
Checks"3.4.13.1Pre-Activation Checks" are met.

Perform the following steps on the master RNC to activate Load Sharing and Node
Redundancy:
 To activate control-plane load sharing, run the SET UPOOLLOADSHAREPARA
CP_SHARE(CP_SHARE), with Control Plane Load Sharing Absolute Threshold
and Control Plane Load Sharing Relative Threshold set to proper values.
 To activate user-plane load sharing, run the SET UPOOLLOADSHAREPARA
CP_SHARE(CP_SHARE), with User Plane Load Sharing Absolute Threshold and
User Plane Load Sharing Relative Threshold set to proper values.
 When NodeB control switchovers are triggered manually, run the SET
UPOOLREDUNDANCY command with Redundancy Mode set to Manual(Manual)
to activate Node Redundancy.
 When NodeB control switchovers are triggered automatically, run the SET
UPOOLREDUNDANCY command with Redundancy Mode set to
Automatic(Automatic) to activate Node Redundancy.
 To ensure that the values of Redundancy Mode on the master RNC and backup RNC are the same,
check whether ALM-706 Inconsistent RNC in Pool Configuration is reported on the CME. If ALM-
706 Inconsistent RNC in Pool Configuration is reported, manually synchronize RNC in Pool data on
the CME.
 In automatic NodeB control switchover mode, check whether ALM-22307 RNC in Pool Function
Unavailable is reported on the master RNC. If such an alarm is reported, clear the alarm following
the troubleshooting process.
 After feature activation, check the RNC in Pool configurations again on the CME.
4.5 Acceptance
Before checking the RNC in Pool topology, perform the following operations to synchronize NEs on the
CME: Log in to the U2000, choose CME > Current Area > Synchronize NEs, and then select physical
RNCs shown in the following figure to synchronize NEs in the current area.

Copyright © Huawei
successful.
report to solve the problem.
Then, perform the following steps to check the RNC in Pool topology:

Copyright © Huawei
----End
 SET SYS: SUPPORTRNCINPOOL=SUPPORT, POOLNAME="XXX";
 SET NODE: NID=XX, NNAME="XX;
ADD EXTNODE: ENID=XX, ENNAME="XX";
 If the statuses shown in the table are inconsistent with actual configurations, run the
following commands to check whether the master RNC and overflow/backup RNC of
the same logical RNC are correctly configured and match with each other:
 ADD URNCBASIC: LoadSharingType=XX, RedundancyType=XX;

Copyright © Huawei
 ADD URNCMAP: ENID=XX, LoadSharingType=XX, RedundancyType=XX;

After NEs are synchronized in the current area, perform the following steps to check the task
status:

page.
 In versions earlier than R15, the CME automatically creates an autosync task for each logical RNC.
In R15 and later, the CME automatically creates two autosync tasks for logical RNCs supporting
Node Redundancy. One task is RNC-level and the other task is NodeB-level.
 The NodeB-level synchronization task contains information about dual-homed NodeBs, but if one of
the following unexpected situations occur, create manual tasks to rectify the exception.
 Scenario 1: The ID and name of a dual-homed NodeB are inconsistent on the master RNC and
backup RNC, resulting that the CME fails to identify the dual-homed NodeB.
 Scenario 2: The dual-homed NodeB is only configured for the master RNC but not for the backup
RNC. When the NodeB-level synchronization task is executed, an error message is displayed on the
CME. The CME only supports the error check function in R15B240 and later.
 Scenario 3: The specification of the dual-homed NodeB is beyond the processing capability, and
therefore the task fails.

Step 3 Click .

Copyright © Huawei
Enable Auto Sync.
----End

Management window. Log in to the U2000, choose Maintenance > Task Management,
select Pool Consistency check on the left, and check the status of different tasks according to
task name.

Copyright © Huawei

Step 1 Run the LST LICENSE command to check whether the licenses for Load Sharing and Node
Redundancy in the master and backup license files are activated.
----End

whether the Iur-p transmission delay meets the requirements. For details, see 5.2Iur-p
Methods."

correctly.
 ALM-22388 Configuration of Service Objects Incomplete
 ALM-21392 Adjacent Node IP Address Ping Failure
 ALM-22390 Redundancy Switchover of Logical RNC Control
 EVT-22944 Logical RNC Control Switchover
 ALM-22235 Dual-Homed NodeB Configuration Incorrect
 ALM-22243 Excessive Synchronization Data for RNC in Pool Load Sharing
 ALM-22391 Function of RNC in Pool Load Sharing Flow Control
 ALM-22392 Backup RNC Hardware Capacity Reaching the Limit in RNC in Pool Node
Redundancy

data integrity and data consistency between the master RNC and the overflow/backup RNC.
To check the RNC in Pool configurations, perform the following operations:

Copyright © Huawei

----End

4.5.8 Accepting Load Sharing

You can accept Load Sharing by using either one of the following methods:
 Perform IMSI dialing tests and use Load Sharing test reports (To obtain such reports,
visit http://support.huawei.com.).
 Perform IMSI dialing tests and trigger Load Sharing to take effect by adjusting the
activation threshold on the live network.
The specific method is selected based on project situations. The final "Acceptance Solution"
is presented in the "Reconstruction and Deployment Solution" upon reaching an agreement
with customers.
IMSI dialing tests: performed at sites where driving tests or dialing tests can be carried out
Step 1 Prepare a test UE and record the IMSI of the UE.

Copyright © Huawei
Step 2 Run the ADD UIMSI command on the master RNC with the IMSI parameter set to the UE's
IMSI and the LoadShareSwitch parameter set to ON. If control-plane load sharing is to be
verified, set the LoadShareType parameter to CP_SHARE. If user-plane load sharing is to
be verified, set the LoadShareType parameter to CPUP_BIND_SHARE and the ENID
parameter set to the Node ID of the overflow RNC.
Step 3 Run the LST UIMSI command on the overflow RNC to ensure that the UE's IMSI is
synchronized to the overflow RNC. Use the UE to initiate two calls. The first call enables the
master RNC to learn the UE's IMSI, and in the second call, the master RNC attempts to
offload the call to the overflow RNC.
Step 4 Run the DSP UIMSI command on the master RNC with the IMSI parameter set to the UE's
IMSI and the IMSI_FUNC parameter set to LOADSHARE. If the loading sharing status in
the command output is Control Plane Load Sharing Succeed or Combined Control and
User Plane Load Sharing Succeed, the Load Sharing feature takes effect.
 The UEs are involuntarily offloaded to the overflow RNC by the IMSI, but the load sharing is not
based on the load sharing algorithm. Therefore, the effectiveness of the load sharing algorithm
cannot be verified. The correctness of service processing and the Iur-p interface after UEs are
offloaded to the overflow/backup RNC can be verified.
 This method relies on the unchanged TMSI in the two RRC Connection Request
messages. If the UE accesses the network using a different TMSI each time, this method
is not applicable.
----End
Triggering Load Sharing to take effect by adjusting the activation threshold: After the
reconstruction is complete, monitor the load status of the master RNC and overflow/backup
RNC and run the SET UPOOLLOADSHAREPARA command to set the activation
threshold.
Use one of the following methods to verify whether Load Sharing is enabled:
 Run the DSP LICUSAGE command on the master RNC to query the used value of the
license control item RNC in Pool Load Sharing (per Active User). If the return value is
not 0, the RNC in Pool Load Sharing feature is enabled.
 Or check values returned by the following counters. If the values are not 0, the RNC in
Pool Load Sharing feature is enabled.
Control-Plane Load Sharing VS.RRC.SuccConnEstab.N Number of Successful RRC

odeShare Connection Requests Sent
by UEs Whose Load Is
RNC Nodes
VS.RRC.AttConnEstab.Nod Number of RRC Connection
eShare Requests Sent by UEs
Whose Load Is Shared
Nodes

Copyright © Huawei
VS.RAB.AttEstabCS.Conv. Number of CS RAB

NodeShare Assignment Requests for
Nodes (Conversational
Service)
VS.RAB.SuccEstabCS.Con Number of Successful CS
v.NodeShare RAB Assignment Requests
RNC Nodes (Conversational
Service)
VS.RAB.AttEstabPS.Bkg.N Number of PS RAB
odeShare Assignment Requests for
Nodes (Background Service)
VS.RAB.SuccEstabPS.Bkg. Number of Successful PS
NodeShare RAB Assignment Requests
RNC Nodes (Background
Service)
VS.RAB.AttEstabPS.Int.No Number of PS RAB
deShare Assignment Requests for
Nodes (Interactive Service)
VS.RAB.SuccEstabPS.Int.N Number of Successful PS
odeShare RAB assignment Requests
RNC Nodes (Interactive
Service)
VS.LoadSharedActiveUEs. Number of UEs Whose
NodeShare Load Is Shared Between
Physical RNC Nodes
User-Plane Load Sharing VS.CSLoad.Erlang.Equiv.N Average Equivalent Erlangs
odeShare Consumed by CS Load
Sharing Users Between
Physical RNC Nodes for an
RNC
VS.R99PSLoad.DLThruput. DL R99 Average Traffic of
Domain

Copyright © Huawei
VS.R99PSLoad.ULThruput. UL R99 Average Traffic of

Nodes in the PS Domain
VS.HSDPAPSLoad.DLThru HSDPA Average Traffic of
Domain
VS.HSUPAPSLoad.ULThru HSUPA Average Traffic of
Domain
Before this method is used, identify the absolute and relative load-sharing threshold based on the load
status on the live network. If control-plane load sharing is enabled, identify the absolute and relative
threshold by monitoring the average CPU usage of the master RNC and the overflow/backup RNC
(BSC6900: VS.XPU.CPULOAD.MEAN; BSC6910: VS.CPPOOL.CPULOAD.MEAN). If user-plane
load sharing is enabled, monitor the CPU usage of the master RNC and overflow/backup RNC
(BSC6900: VS.DSP.UsageAvg; BSC6910: VS.UPPOOL.CPULOAD.MEAN). For details, contact
R&D engineers.
4.5.9 Accepting Node Redundancy

The Redundancy Mode can be set to Manual(Manual) or Automatic(Automatic). No
matter the redundancy mode is set to manual or automatic, the acceptance is based on ATP
cases (To obtain such cases, visit http://support.huawei.com.).
 Manual switchover of NodeB control has two cases: a NodeB control switchover from
the master RNC to the backup RNC and from the backup RNC to the master RNC.
 Automatic switchover of NodeB control has four cases:
− A NodeB switchover control from the master RNC to the backup RNC when the
master RNC is faulty caused by power off in the equipment room.
− A NodeB switchover control from the backup RNC to the master RNC when the
backup RNC is faulty caused by power off in the equipment room.
interface is faulty between the master RNC and the CN triggered by the Iu interface
failure.
interface is faulty between the backup RNC and the CN triggered by the Iu interface
failure.
 If scenario verification based on ATP cases is not allowed, it is recommended that you
perform the following checks after the deployment:
of a logical RNC.

Copyright © Huawei
Step 2 Run the DSP UNODEB command on the master/backup RNC to query whether all NodeBs
are homing to the master RNC. If a large number of NodeBs are involved, the system
performance may be affected. You can skip this step or choose some NodeBs to query the
status.
Step 3 Select an available dual-homing NodeB on the master RNC, start Iub tracing and check
whether the NBAP_RNC_POOL_MSG message is transmitted properly on a regular basis.
----End
 Considering the effect of node redundancy on the network, especially automatic redundancy, you are
advised to perform the acceptance upon an agreement with customers.
 When the switchover of NodeB control cannot be identified, the preceding status-checking steps
only indicate that relevant operations required for the deployment have been configured, but whether
standby links over interfaces after the switchover are functional cannot be guaranteed.
 The following process takes the L_RNC1 as an example.
Conclusion: P_RNC1 (the master RNC) owns the control right of L_RNC1.

Copyright © Huawei
Conclusion: P_RNC1 (the master RNC) owns the control right of the NodeB.
Step 5 Start Iub tracing on the P_RNC1 to check whether the NBAP_RNC_POOL_MSG message is
transmitted regularly.
The preceding figures are just for reference.

 Performance measurement results for device and transmission objects are reported on the
physical RNC. Performance measurement results for radio objects are always reported
on the physical RNC that has obtained the NodeB control. After the control right is
switched back to the backup RNC, performance counters can only be found on the
backup RNC (for example, NodeB\CELL).
4.6 Procedures for Rolling Back Load Sharing and Node

Redundancy
4.6.1 Deactivation
Perform the following operations to deactivate Load Sharing or Node Redundancy.

Copyright © Huawei
Deactivating Load Sharing:

 When only control-plane load sharing is enabled, run the SET
UPOOLLOADSHAREPARA command on the master RNC with CP Load Sharing
Policy set to NO_SHARE(NO_SHARE) to deactivate Load Sharing.
 When control-plane load sharing and user-plane load sharing are both enabled, if you
want to only deactivate user-plane load sharing, run the SET
UPOOLLOADSHAREPARA command on the master RNC with UP Load Sharing
Policy set to NO_SHARE(NO_SHARE) to deactivate user-plane load sharing. When
control-plane load sharing and user-plane load sharing are both enabled, run the SET
UPOOLLOADSHAREPARA command on the master RNC with CP Load Sharing
Policy set to NO_SHARE(NO_SHARE) to deactivate both control-plane and user-
plane load sharing.
Deactivating Node Redundancy:

 When NodeB control switchovers are triggered manually, run the FOC UHOSTRNC
command on the master RNC to make sure that the control right has been switched back
to the master RNC, and then run the SET UPOOLREDUNDANCY command with
Redundancy Mode set to NO_Redundancy(NO_Redundancy) to disable Node
Redundancy.
 When NodeB control switchovers are triggered automatically, run the
SETUPOOLREDUNDANCY command on the master RNC and overflow/backup
RNC with Redundancy Mode set to Manual(Manual), and then use the manual
operation method to disable Node Redundancy.

configurations of the logical RNC from the overflow/backup RNC. If N master RNCs are
involved, perform the following steps for these RNCs one by one:
Step 2 When NodeB control switchovers are triggered automatically, run the SET
UPOOLREDUNDANCY command on the master RNC with Redundancy Mode set to
Manual(Manual). Run the SET URNCPOOLCFGCTRL command on the
overflow/backup RNC with Data Synchronization Mode set to ManualCfg(Manual
Configuration), and then run the SET UPOOLREDUNDANCY command with
Redundancy Mode set to Manual(Manual).
control. Run the REL UHOSTRNC command on the overflow/backup RNC to forcibly
release NodeB control.
Step 4 Run the SET UPOOLREDUNDANCY command on the master RNC and overflow/backup
RNC with Redundancy Mode set to NO_Redundancy(NO_Redundancy).
Step 5 Run the EXP URMVRNCDATA command on the overflow/backup RNC to export the script
(for example, Remove_RNC1_Script.zip) for removing the logical RNC. A backup script
workspace. Run the RUN BATCHFILE command on the overflow/backup RNC to execute
the exported script.

Copyright © Huawei
Step 6 Run the RMV SRCIPRT and RMV DEVIP commands on the overflow/backup RNC. When
link aggregation is not used, run the RMV ETHIP command. When link aggregation is used,
run the RMV ETHTRKIP, RMV ETHTRKLNK, and RMV ETHTRK commands to
remove Iur-p link configurations.
master RNC with The Host Type of Signaling Point set to
SINGLEHOST(SINGLEHOST).
reconfigure SCTP and M3UA links.
external RNC.
Step 12 Run the SET SYS command on the master RNC and overflow/backup RNC with Support
RNC in Pool set to NOT_SUPPORT(Not_Support).
Step 13 Remove Iu/Iur interface configurations for L_RNC1 from the CN and the neighboring RNC.
----End
 The script exported by running the EXP URMVRNCDATA command can be used to remove the
following configurations for a logical RNC from the overflow/backup RNC: NodeB-level data
synchronized from the master RNC within the pool, Iub user-plane objects of the backup RNC
(ADJMAP, TRMFACTOR, TRMMAP, and ADJNODE), Iub control-plane objects of the backup
RNC (UNCP, UCCP, and SAALLNK/SCTPLNK), assisted OSP on the backup RNC, RNC-level
data synchronized from the master RNC within the pool, Iur-p links, mapping between the logical
RNC and the physical RNC, and information about the logical RNC and external physical RNC.
 If the configurations for the logical RNC need to be restored immediately after being removed, run
the RUN BATCHFILE command to execute the generated rollback script

Copyright © Huawei
RNC in Pool Reconstruction Guide (RAN18.1) AppendixAppendix
5 Appendix
5.1 BSC6910 Initial Configuration

5.2 Iur-p Transmission Delay Measurement Methods
5.3 Creating a Planned Data Area
5.4 Iu-BC Solution When RNC in Pool Node Redundancy is Enabled
5.5 OMCH Configuration Methods When RNC in Pool Node Redundancy is Enabled
5.6 Manually Synchronizing RNC in Pool Data
5.7 X Project Deployment Solution
5.1 BSC6910 Initial Configuration

The BSC6910 initial configuration is performed on the standalone CME as follows:
Step 1 Configure data.
You are advised to obtain the MBSC data file template, and then import initial configurations.
For details about how to obtain the MBSC data file template, see "Importing MBSC Data" in
CME Product Documentation. Configured data varies with the functional type of RNC.
 If the newly deployed RNC works as the master RNC, the RNC is fully configured.
 If the newly deployed RNC works as the overflow RNC or backup RNC, the RNC is
configured with the following data.
− Global parameters, including the subnet No. and SCTP service listening port No.
− Device data.
 If the BSC6910 does not work as the master RNC of a logical RNC, but works as the overflow
RNC, when control-plane load sharing is enabled, the BSC6910 is only configured with device
parameters on the control plane. Therefore, it is recommended that the CP subsystem proportion of
the general processing unit (GPU) be set to 100% by running the SET UCPUPFLEXCFG
command.

Copyright © Huawei
 Clock and time data on the master RNC cannot be synchronized to the overflow RNC through the
Iur-p interface. The overflow RNC does not provide any external interfaces. Therefore, the overflow
RNC does not require clock data configuration. Ensure that time data on the overflow RNC are the
same as that on the master RNC.
 If the newly deployed RNC works as the backup RNC, clock and time data on the master RNC
cannot be synchronized to the backup RNC through the Iur-p interface, the backup RNC requires
clock and time data configuration. Clock and time data on the backup RNC must be the same as
those on the master RNC.
 If the newly deployed RNC works the master RNC and overflow RNC or as the master
RNC and backup RNC, full configurations are performed on the newly deployed RNC.
Step 2 Start the standalone CME. Choose Advanced > Import MBSC Data, and then select File
path, as shown in Figure 2.1.
Figure 2.1 Selecting the MBSC data file
Step 3 After the data file is imported, click Finish.

----End
 If data configuration is for NEs, see BSC6910 UMTS Initial Configuration Guide. For initial
configuration of the newly deployed RNC, the node ID and node name of the RNC are required.
 After initial configurations are done, you are advised to back up data on the master RNC
and overflow/backup RNC. In case of networking rollback, initial configurations can be
restored. For data backup methods, see RAN Routine Maintenance Guide.
5.2 Iur-p Transmission Delay Measurement Methods
Iur-p transmission delays within the monitoring period cannot accurately indicate the network
transmission quality. Therefore, those delays are only for reference during the reconstruction. It is
unknown that whether the Iur-p transmission delay meets the requirements.

Copyright © Huawei
The transmission requirements for the Iur-p interface are as follows:

 When RNC in Pool Load Sharing is enabled, the one-way transmission delay must not
exceed 10 ms, the transmission jitter must not exceed 5 ms, and the packet loss rate must
be less than 0.01%.
 When RNC in Pool Node Redundancy is enabled, the one-way transmission delay must
not exceed 100 ms, the transmission jitter must not exceed 50 ms, and the packet loss
rate must be less than 1%.
Before activating the feature, use the following methods to determine whether the delay meets
the preceding requirements.
(Recommended) Method 1: Monitor whether the Iur-p transmission day meets the
requirements through the Iur-p interface
Step 1 On the LMT, in the monitor navigation tree on the left, choose Monitor > UMTS
Monitoring > Iur-p Monitoring.
Step 2 The Iur-p Monitoring dialog box is displayed, enter External Node and Monitor Period (s).
Figure 2.1 Iur-p monitoring
Step 3 Click Submit to start the monitoring.

Copyright © Huawei
----End
Method 2: Monitor whether the Iur-p transmission delay meets the requirements by
running the PING IP command.
The maximum delay, the minimum delay, and the average delay are exported by running the
PING IP command on the WebLMT. Based on these delays, the Iur-p transmission delay can
be estimated.
Source IP address: Specify the local IP address.
Destination IP address: Specify the peer IP address.
For example:
PING 34.7.0.1: 56 data bytes
Reply from 34.7.0.1: bytes=56 Sequence=1 ttl=253 time=3 ms
--- 34.7.0.1 ping statistics ---
4 packet(s) transmitted
4 packet(s) received

Copyright © Huawei
Percent 0.00 packet lost

round-trip min/avg/max = 3/3/4 ms
+++ huawei_mbsc
O&M #20780
%%PING IP: SIPADDR="144.7.0.1", DESTIP="34.7.0.1", CONTPING=NO;%%
RETCODE = 0 Execution succeeded.
10 reports in total
(Number of results = 1)
--- END
5.3 Creating a Planned Data Area

Step 1 Synchronize NEs in the current area.
Synchronize NEs in the current area by performing the following operations:
1. Choose CME > Current Area > Synchronize NEs.
2. Select the master RNC, the overflow/backup RNC, and NodeBs to be reconstructed from
the Available NEs area and add them to the Selected NEs area, as shown in Figure 1.1.
Figure 1.1 Selecting NEs
Step 2 Create a planned data area.

Copyright © Huawei
Create a planned data area by performing the following operations. The planned data area is
required for delivering the generated script to the RNCs and NodeBs.
1. Choose CME > Planned Area > Create Planned Area.
2. Specify Planned Area Name. For example, RNC in Pool. Select the master RNC,
overflow/backup RNC, and NodeBs to be reconstructed from the Available NEs area,
add them to the Selected NEs area and then click OK, as shown in Figure 2.1 and Figure
2.2.
Figure 2.1 Selecting RNCs

Copyright © Huawei
Figure 2.2 Selecting NodeBs
----End
5.4 Iu-BC Solution When RNC in Pool Node Redundancy

is Enabled
When Node Redundancy is enabled, if the master RNC is configured with the Iu-BC
interface, the backup RNC also supports Iu-BC redundancy. No matter NodeB control
switchovers are triggered manually or automatically, after the NodeB control switchovers, you
are advised to change the CBC IP address of the involved logical RNC to the IP address of the
master RNC. See Figure 2.3.

Copyright © Huawei
Figure 2.3 Networking for the Iu-BC solution
It is recommended that the reconstruction be performed as follows:

Step 1 Plan a new IP address (for example, IP2 in the preceding figure).
Step 2 Run the ADD DEVIP command on the backup RNC or overflow/backup RNC to add IP2.
Step 3 Run the MOD UCBSADDR command on the backup RNC or overflow/backup RNC with
CBS RNC IP Address set to IP2.
If the CBC server supports node redundancy, the second CBS RNC IP address is planned by following
the same steps.
After the switchover, change the peer RNC IP address on the CBC server to the Iu-BC IP
address of the backup RNC, that is IP1 to IP2 (If the CBC server supports node redundancy,
the second CBS RNC IP address is changed to the Iu-BC IP address of the backup RNC as
well.). CBC configuration relationship before and after the switchover is as follows:
----End

Copyright © Huawei
The reconstruction involves the change of the interface IP address on the CBC server and the method for
changing the IP address may vary with CBC vendors. Therefore, you are advised to clarify the specific
methods to customers before the reconstruction. If the IP address cannot be changed, the Iu-BC interface
cannot support Node Redundancy in this scenario.
5.5 OMCH Configuration Methods When RNC in Pool

Node Redundancy is Enabled
The operation and maintenance channel (OMCH) of the NodeB can pass through the RNC or
does not pass through the RNC.
 The OMCH does not pass through the RNC
In the IP transmission mode, the OMCH of the NodeB does not pass through the RNC.
To ensure that the old OMCH between the NodeB and U2000 is not affected after the
switchover, a standby OMCH or a secondary route is added between the NodeB and
U2000.
Operations on the RNC side:
 ATM transmission applies to the Iub interface: ADD DEVIP, ADD IPOAPVC, and
ADD UNODEBIP
 The Iub IP Pool networking is applied: ADD UNODEBIP and ADD UNODEBESN.
Configure when the NodeB uses the dynamic host configuration protocol (DHCP).
 The ATM and IP transmission both apply to the Iub interface: ADD DEVIP, ADD
IPOAPVC, ADD UNODEBIP, and ADD UNODEBESN (configure when the NodeB
uses the DHCP).
Operations on the NodeB side: ADD OMCH
 The OMCH passes through the RNC
When ATM or IP transmission over E1/T1 is used, the OMCH of the NodeB passes
through the RNC. To ensure that the old OMCH between the NodeB and U2000 is not
affected after the switchover, a standby OMCH or a secondary route through the backup
RNC is added between the NodeB and U2000.
Operations on the RNC side:
 ATM transmission applies to the Iub interface: ADD DEVIP, ADD IPOAPVC, ADD
UNODEBIP, and ADD IPRT
 The Iub IP Pool networking is applied: ADD UNODEBIP and ADD UNODEBESN
(configure when the NodeB uses the DHCP), and ADD IPRT
 The ATM and IP transmission both apply to the Iub interface: ADD DEVIP, ADD
IPOAPVC, ADD UNODEBIP, ADD UNODEBESN (configure when the NodeB uses
the DHCP), and ADD IPRT
Operations on the NodeB side: ADD OMCH
For details, see 3900 Series Base Station Initial Configuration Guide and BSC6910 UMTS
Initial Configuration Guide.
 When the OMCH passes through the RNC, the switchover between the active OMCH and the
standby OMCH takes about 5 to 6 minutes.

Copyright © Huawei
 When a standby OMCH is added, the NODEBIP configured for the backup RNC is separate from
the NODEBIP configured for the master RNC. The two IP addresses cannot be in the same network
segment. When a secondary route is added, the NODEBIP configured for the backup RNC is the
same as that for the master RNC.
 When the OMCH over the Iub interface takes a route from U2000, the backup RNC to the NodeB,
make sure that the route forwarding function of the operation and maintenance unit (OMU) is
enabled. By default, this function is enabled. For details, see the section "Disabling OMU Route
Forwarding" of Appendix: OMU Security FAQs in BSC6910 UMTS OMU Administration Guide.
 When the OMCH does not pass through the RNC, if the backup RNC is not configured with related
data, the OMCH is not affected in most scenarios. However, in some unusual scenarios, the NodeB
cannot be found on U2000, causing the NodeB disconnected. Considering the risk, you are advised
to configure related data for the backup RNC.
5.6 Manually Synchronizing RNC in Pool Data

Step 1 On the U2000, Choose CME > Current Area > Open Current Area to open the current
area, then choose CME > UMTS Application > RNC in Pool Configuration > RNC in
Pool Configuration Management to open the RNC in Pool Configuration Management
tab page.
Scheduled synchronization tasks for this logical RNC are displayed in the task list on the left,
as shown in the following figure.
Step 2 Select the task (for example, ), click on the upper left of the tab page to start the
task.
After the task is completed, data differences among the master RNC and overflow RNC,
backup RNC, and overflow/backup RNC are displayed in the right pane.
Step 3 Click to trigger the synchronization.

Copyright © Huawei
----End
 If you want to synchronize parameter configurations on the backup RNC to the master RNC, click
Reverse Sync, a high-risk prompt pops up, click Yes, reserve sync is in progress. Because the data
on the logical RNC is shared by the master RNC and backup RNC, after data synchronization mode
of the backup RNC is set to the manual mode, check whether logical data on the backup RNC is
complete manually. It is strongly recommended that the RNC-level data on the backup RNC be not
removed, because the data may also be used by the master RNC. If reverse synchronization fails due
to the missing global data of the master RNC, supplement the missing data on the backup RNC.
 Before performing data synchronization, ensure that the SyncDataCfgMode parameter is set to
AutoSync on the overflow/backup RNC.
5.7 X Project Deployment Solution
RNC in Pool
Deployment Project Case.xlsx.xlsx

Copyright © Huawei

07 RNC in Pool Delivery Guide (RAN18.1)

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

07 RNC in Pool Delivery Guide (RAN18.1)

Caricato da

Copyright:

Formati disponibili

WCDMA RAN

RNC in Pool Reconstruction Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2016-11-04) Huawei Proprietary and Confidential i

1 About This Document..................................................................................................................1

2 Engineering Guidelines for Load Sharing.............................................................................11

Issue 01 (2016-11-04) Huawei Proprietary and Confidential ii

2.4.4.2 User-Plane Load Sharing........................................................................................................................................37

3 Engineering Guidelines for Node Redundancy....................................................................76

Issue 01 (2016-11-04) Huawei Proprietary and Confidential iii

3.4.5 Configuring Iu/Iur Interfaces...................................................................................................................................102

4 Engineering Guidelines for Load Sharing and Node Redundancy................................145

Issue 01 (2016-11-04) Huawei Proprietary and Confidential iv

4.4.2 Activating License Files..........................................................................................................................................172

Issue 01 (2016-11-04) Huawei Proprietary and Confidential v

1 About This Document

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 1

RNC BSC6910 GU, BSC6900

This document provides only operation instructions on BSC6900 V900R018C10/BSC6910

1.3 Intended Audience

1.4 Change History

1.5 Deployment Policy

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 2

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 3

1.7.2 Neighboring NEs

Impacts of RNC in Pool on the neighboring NEs are as follows:

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 4

 For the performance surveillance (PRS)

BSC6900 BSC6910 Only as

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 5

Feature Name Master RNC Overflow/Backup

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 6

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 7

1.7.5 Interfaces and Transmission

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 8

1.7.6 NBI Interconnection

 If the master RNC has the NodeB control, set SyncDataCfgMode(UMTS

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 9

1.8 Related Documentation

To obtain the preceding documents of different versions, visit http://support.huawei.com.

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 10

2 Engineering Guidelines for Load Sharing

2.1 Typical Scenarios

2.1 Typical Scenarios

2.1.1 Scenario 1: N Master RNCs and An Overflow RNC Carrying

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 11

Scenario 1 can be divided into subscenarios, as listed in the following table.

Subsc Before Before Load After After

RNC Number of Attribute of

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 12

Subsc Before Before Load After After

2.1.2 Scenario 2: Two Physical RNCs Carrying Two Logical RNCs

 In this scenario, the two physical RNCs must be BSC6910s.

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 13

Figure 1.3 Two physical RNCs carrying two logical RNCs

Scenario 2 can be divided into subscenarios, as listed in the following table.

Subsc Before Before Load After After

RNC Number of Attribute of

Issue 01 (2016-11-04) Huawei Proprietary and Confidential 14

2.1.3 Scenario 3: Four BSC6900s and Two BSC6910s Carrying

Scenario 3 can be divided into subscenarios, as listed in the following table.

Subsc Before Before Load After After