GSM BSS

GBSS15.0

BSC Node Redundancy Feature

Parameter Description

Issue 01
Date 2013-05-06

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 (2013-05-06) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description Contents

Contents

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

1.1 Scope..................................................................................................................................................................1
1.2 Intended Audience..............................................................................................................................................1
1.3 Change History...................................................................................................................................................1

2 Overview.........................................................................................................................................3
2.1 Introduction........................................................................................................................................................3
2.2 Benefits...............................................................................................................................................................4
2.3 Feature Support by NE.......................................................................................................................................5

3 Technical Description...................................................................................................................6
3.1 Dual- and Single-Homed Service Objects..........................................................................................................6
3.1.1 OPC...........................................................................................................................................................6
3.1.2 BTS............................................................................................................................................................7
3.2 Network Topologies...........................................................................................................................................7
3.2.1 Typical Scenarios......................................................................................................................................7
3.2.2 Networking Modes over the Abis/A/Gb/Inter-BSC Interface...................................................................9
3.3 Fault Detection.................................................................................................................................................15
3.4 Migrating Service Objects in the Event of a Failure........................................................................................16
3.4.1 Migrating Dual-Homed OPCs.................................................................................................................16
3.4.2 Migrating Dual-Homed BTSs.................................................................................................................17
3.5 Neighboring Cells.............................................................................................................................................18
3.5.1 All Dual-Homed BTSs............................................................................................................................18
3.5.2 Combination of Dual- and Single-Homed BTSs.....................................................................................20
3.6 Migrating Back Dual-Homed Service Objects.................................................................................................21
3.7 Maintaining Dual-Homed Service Objects.......................................................................................................22

4 Related Features...........................................................................................................................23
4.1 Abis over IP or Abis IP over E1/T1.................................................................................................................23
4.2 A over IP, A IP over E1/T1, or A over IP Based on Dynamic Load Balancing..............................................23
4.3 Local Multiple Signaling Points.......................................................................................................................23

5 Network Impact...........................................................................................................................24
5.1 System Capacity...............................................................................................................................................24
5.2 Network Performance.......................................................................................................................................24

Issue 01 (2013-05-06) Huawei Proprietary and Confidential ii

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description Contents

6 Engineering Guidelines.............................................................................................................25
6.1 When to Use BSC Node Redundancy..............................................................................................................25
6.2 Required Information.......................................................................................................................................25
6.3 Planning............................................................................................................................................................25
6.4 Deployment......................................................................................................................................................26
6.4.1 Requirements...........................................................................................................................................26
6.4.2 Data Preparation......................................................................................................................................28
6.4.3 Precautions...............................................................................................................................................29
6.4.4 Activation................................................................................................................................................29
6.4.5 Activation Observation............................................................................................................................42
6.4.6 Deactivation.............................................................................................................................................44
6.5 Performance Monitoring...................................................................................................................................45
6.6 Parameter Optimization....................................................................................................................................45
6.7 Troubleshooting................................................................................................................................................45

7 Parameters.....................................................................................................................................46
8 Counters........................................................................................................................................63
9 Glossary.........................................................................................................................................64
10 Reference Documents...............................................................................................................65

Issue 01 (2013-05-06) Huawei Proprietary and Confidential iii

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 1 About This Document

1 About This Document

1.1 Scope
This document describes the implementation principles of the GBFD-113725 BSC Node
Redundancy feature, including network topologies, fault detection, migrating, migrating back,
and maintaining service objects.

1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the BSC Node Redundancy feature
l Work with Huawei GSM products

1.3 Change History

This section provides information about the changes in different document versions.
There are two types of changes, which are defined as follows:
l Feature change: refers to a change in the BSC Node Redundancy feature of a specific
product version.
l Editorial change: refers to a change in wording or the addition of information that was not
described in the earlier version.

Document Issues
The document issue is as follows:
l 01 (2013-05-06)
l Draft A (2013-02-27)

01 (2013-05-06)
This is the first commercial release of GBSS15.0.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 1

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 1 About This Document

Compared with Draft A (2013-02-27), Issue 01 (2013-05-06) incorporates the changes described
in the following table.

Change Type Change Description Parameter Change

Feature change None None

Editorial change Optimized the descriptions None

throughout the document.

Draft A (2013-02-27)
This is a draft.
Compared with issue 01 (2012-04-28) of GBSS14.0, draft A (2013-02-27) of GBSS15.0
incorporates the changes described in the following table.

Change Type Change Description Parameter Change

Feature change Added section "2.3 Feature None

Support by NE."

Editorial change l Added chapter "4 None

Related Features."
l Optimized chapter "6
Engineering
Guidelines."

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 2

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 2 Overview

2 Overview

2.1 Introduction
Huawei introduces the BSC Node Redundancy feature, which is a BSC-level redundancy
solution, to prevent the following problems:
In traditional wireless networks, each BTS connects to only one BSC. If a BSC fails or all the
signaling links on the A interface are disconnected, none of the BTSs served by the BSC can
access the network, and the BSC cannot provide services.

NOTE

This feature applies to the following scenarios:

l BSC failure
A BSC fails or all the A interface boards are faulty. In either case, the BSC cannot process services.
l Failure in signaling links on the A interface
All the signaling links on the A interface are disconnected.

The BSC Node Redundancy feature enables two BSCs to form a redundancy group in all-IP
networking mode (the A, Abis, and inter-BSC interfaces all use IP transmission). Two BSCs in
a redundancy group work in 1+1 backup mode. If one BSC fails or all the signaling links on the
A interface of one BSC are disconnected, the other BSC takes over all services.
Figure 2-1 shows the networking diagram of two BSCs working in a redundancy group.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 3

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 2 Overview

Figure 2-1 Networking diagram of two BSCs working in a redundancy group

In a redundancy group, each BSC considers itself as the local BSC and the other as the peer
BSC. To enable or disable this feature on the local and peer BSCs, set RedundancyMode to an
appropriate value.

LocalBSCID and PeerBSCID specify the local and peer BSCs in a redundancy group,
respectively. GROUPINDEX specifies a redundancy group.

2.2 Benefits
This feature provides the following benefits:

l More reliable BSCs

Two BSCs in a redundancy group work in 1+1 backup mode. If one BSC fails, the other
BSC immediately takes over services from the failed BSC.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 4

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 2 Overview

l More reliable transmission

Both BSCs in a redundancy group connect to a core network (CN) over the A interface. If
all the signaling links on the A interface of one BSC are disconnected, the other BSC
immediately takes over services from the failed BSC.

2.3 Feature Support by NE

Table 2-1 Feature support by NE
Feature BSC6900 BSC6910 GBTS eGBTS

BSC Node √ √ √ ×
Redundancy

NOTE

√ indicates that the NE supports this feature. × indicates that the NE does not support this feature.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 5

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

3 Technical Description

3.1 Dual- and Single-Homed Service Objects

The BSC Node Redundancy feature introduces the concepts of dual- and single-homed service
objects. Dual-homed service object: The service object is configured on two BSCs but is
activated only on one BSC at a time.
Single-homed service object: The service object is configured only on one BSC.
A dual-homed service object is configured as primary-homed on one BSC and as secondary-
homed on the other BSC.
l Primary-homed: The service object provides services on the local BSC and its configuration
data is backed up on the peer BSC. The peer BSC takes over the service objects only when
the local BSC fails or all the signaling links on the A interface of the local BSC are
disconnected.
l Secondary-homed: The service object provides services on the peer BSC and its
configuration data is backed up on the local BSC. The local BSC takes over the service
objects only when the peer BSC fails or all the signaling links on the A interface of the peer
BSC are disconnected.
Each BSC controls its primary- and single-homed service objects and backs up the configuration
data of its secondary-homed service objects. If one BSC fails or all the signaling links on the A
interface of one BSC are disconnected, the other BSC automatically detects the failure and
enables the backup configuration data of the secondary-homed service objects to take effect.
The BSC then takes over services from the failed BSC.
Dual-homed service objects consist of dual-homed originating point codes (OPCs) and BTSs.

3.1.1 OPC
In a redundancy group, HOSTTYPE of an OPC determines whether the OPC works on the local
or peer BSC:
l If HOSTTYPE is set to PRIMHOST(Primary Host), the OPC provides services on the
local BSC.
l If HOSTTYPE is set to SLAVEHOST(Slave Host), the OPC provides services on the peer
BSC.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 6

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

l If HOSTTYPE is set to SINGLEHOST(Single Host), the OPC provides services only on

the local BSC.

3.1.2 BTS
In a redundancy group, HOSTTYPE of a BTS determines whether the BTS works under the
local or peer BSC:
l If HOSTTYPE is set to PRIMHOST(Primary Host), the BTS communicates with the
local BSC.
l If HOSTTYPE is set to SLAVEHOST(Slave Host), the BTS communicates with the peer
BSC.
l If HOSTTYPE is set to SINGLEHOST(Single Host), the BTS communicates only with
the local BSC.
When BSC Node Redundancy is enabled, specify the PEERBTSID, PEERBSCIP,
PEERBSCID, and PEERBSCMASK parameters for dual-homed BTSs under the local BSC.
The local BSC sends the values of these parameters to the BTSs.

NOTE

The BSCIP and PEERBSCIP parameters specify the IP addresses of the two BSCs to which a BTS is
connected.

3.2 Network Topologies

3.2.1 Typical Scenarios

The BSC Node Redundancy feature is used in two typical scenarios: load sharing and active/
standby modes.

Load Sharing Mode

Some dual-homed BTSs are configured as primary-homed BTSs under BSC 1, and other dual-
homed BTSs are configured as primary-homed BTSs under BSC 2. In load sharing mode, if one
BSC fails or all the signaling links on the A interface are disconnected, the peer BSC takes over
services carried by the dual-homed BTSs from the failed BSC.
Figure 3-1 shows an example of using BSC Node Redundancy in load sharing mode.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 7

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

Figure 3-1 BSC Node Redundancy in load sharing mode

As shown in Figure 3-1, BTSs a and b are dual-homed BTSs. Specifically, BTS a is configured
as a primary-homed BTS under BSC 1 and a secondary-homed BTS under BSC 2, whereas BTS
b is configured as a primary-homed BTS under BSC 2 and a secondary-homed BTS under BSC
1. BTSs 1 and 2 are single-homed BTSs.

Primary- and secondary-homed OPCs are configured for BSCs 1 and 2. The primary-homed
OPC configured for BSC 1 is the same as the secondary-homed OPC configured for BSC 2, and
the primary-homed OPC configured for BSC 2 is the same as the secondary-homed OPC
configured for BSC 1.

A single-homed OPC needs to be configured if BSC 1 or 2 is configured with single-homed

BTSs.

The following table describes the binding between cells and an OPC in a BSC.

Cells Bound OPC

Cells served by primary-homed BTSs under Primary-homed OPC

the BSC

Cells served by secondary-homed BTSs Secondary-homed OPC

under the BSC

Cells served by single-homed BTSs under the Single-homed OPC

BSC

Active/Standby Mode
All dual-homed BTSs are configured as primary-homed BTSs under BSC 1 and as secondary-
homed BTSs under BSC 2. In active/standby mode, if BSC 1 fails or all the signaling links on
the A interface of BSC 1 are disconnected, BSC 2 takes over services carried by the dual-homed
BTSs from BSC 1.

Figure 3-2 shows an example of using BSC Node Redundancy in active/standby mode

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 8

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

Figure 3-2 BSC Node Redundancy in active/standby mode

As shown in Figure 3-2, BTS a is a dual-homed BTS. It is configured as a primary-homed BTS

under BSC 1 and a secondary-homed BTS under BSC 2. BTSs 1 and 2 are single-homed BTSs.
A primary-homed OPC is configured for BSC 1, and a secondary-homed OPC is configured for
BSC 2. The two OPCs are the same.
A single-homed OPC needs to be configured if BSC 1 or 2 is configured with single-homed
BTSs.
The following table describes the binding between cells and an OPC in a BSC.

Cells Bound OPC

Cells served by primary-homed BTSs under Primary-homed OPC

the BSC

Cells served by secondary-homed BTSs Secondary-homed OPC

under the BSC

Cells served by single-homed BTSs under the Single-homed OPC

BSC

3.2.2 Networking Modes over the Abis/A/Gb/Inter-BSC Interface

The BSC Node Redundancy feature applies only to all-IP networking mode (the A, Abis, and
inter-BSC interfaces all use IP transmission). The Gb interface can use any transmission mode.

Abis Interface
A dual-homed BTS can be connected to the primary- and secondary-homed BSCs according to
their IP addresses using routers. A BTS supports two transmission links connecting to the
primary- and secondary-homed BSCs, respectively. In direct connection mode, a BTS does not
support automatic link switchover. A BTS can be connected to two BSCs working in a
redundancy group only through routers.
Three networking scenarios are applicable to the Abis interface:

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 9

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

l Networking scenario 1: An IP bearer network is available on the Abis interface, and the
BTS is deployed at the remote end of the IP bearer network.
The BTS is connected to an optical transceiver in IP over E1/T1 mode. The BSC is
connected to the border router on the BSC side in IP over ETH transmission mode. The
border router on the BTS side is connected to the primary- and secondary-homed BSCs
according to the IP addresses.
Figure 3-3 shows this networking scenario.

Figure 3-3 IP bearer network on the Abis interface and the BTS at the remote end

l Networking scenario 2: An IP bearer network is available on the Abis interface, and the
BTS is deployed at the local end of the IP bearer network.
The BTS is connected to the border router on the BTS side in IP over E1/T1 or IP over
ETH mode. The BSC is connected to the border router on the BSC side in IP over ETH
mode. The border router on the BTS side is connected to the primary- and secondary-homed
BSCs according to the IP addresses.
Figure 3-4 shows this networking scenario.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 10

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

Figure 3-4 IP bearer network on the Abis interface and the BTS at the local end

l Networking scenario 3: No IP bearer network is available on the Abis interface.

An intermediate router is required in Abis over IP mode.
The BTS is connected to an optical transceiver in IP over E1/T1 mode. The BSC is
connected to the border router on the BSC side in IP over ETH mode. The intermediate
router is connected to the primary- and secondary-homed BSCs according to the IP
addresses.
NOTE

To prevent a single-point of failure during network transmission, the intermediate router must support
redundancy backup. Place the intermediate router and the router on the BSC side in different
locations. This ensures that the redundancy function is operational even if the intermediate router is
faulty.
Figure 3-5 shows this networking scenario.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 11

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

Figure 3-5 No IP bearer network on the Abis interface

A Interface
Two BSCs in a redundancy group are connected to the CN using routers.
Two networking scenarios are applicable to the A interface:
l Networking scenario 1: The bearer network on the A interface is an Ethernet network.
The BSC is connected to the border router on the BSC side in IP over ETH mode. The MSC
is connected to the border router on the MSC side in IP over ETH mode.
Figure 3-6 shows this networking scenario.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 12

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

Figure 3-6 Ethernet network as the IP bearer network

l Networking scenario 2: The bearer network on the A interface is a synchronous digital

hierarchy (SDH) or plesiochronous digital hierarchy (PDH) network.
The BSC uses an optical interface to connect to the CN in IP over E1/T1 mode.
Figure 3-7 shows this networking scenario.

Figure 3-7 SDH or PDH network as the IP bearer network

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 13

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

Gb Interface
BSC Node Redundancy has no special requirements for the networking mode used by the Gb
interface. In Gb interface-related protocols, the BSC is virtualized as a network service entity
(NSE). For an SGSN, different NSEs are configured for different BSCs, and the point-to-point
BSSGP virtual connections (PTP BVCs) under different NSEs can be bound to the same cell.
BSC Node Redundancy implements inter-NSE handovers, and the SGSN cannot perceive a BSC
switchover. In addition, the same cell served by different BSCs can be bound to different NSEs.
Figure 3-8 and Figure 3-9 show the networking modes.

Figure 3-8 Gb over IP

Figure 3-9 Gb over FR

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 14

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

Inter-BSC Interface
The inter-BSC interface is used for fault detection on two BSCs in a redundancy group.

Two BSCs in a redundancy group are connected to each other using routers on the inter-BSC
interface.

NOTE

The routes configured over the inter-BSC interface consist of two types: a direct route between BSCs and
an alternative route that passes through a router on the MSC side.
l Direct route: A router is configured between two BSCs to establish communication links over the inter-
BSC interface.
l Alternative route: The signaling network on the A interface is reused. The IP address of the A interface
signaling plane is used to establish communication links. However, the alternative route cannot be
implemented if the BSC connects to the CN without using a router.
The alternative route helps improve the reliability of inter-BSC fault detection. If the direct route is
disconnected but the two BSCs are functional, information can still be transmitted through the alternative
route, thereby preventing a BSC from mistakenly determining that the peer BSC has failed.

Figure 3-10 shows this networking mode.

Figure 3-10 Routes on the inter-BSC interface

3.3 Fault Detection

Fault detection is implemented between two BSCs in a redundancy group by checking the
heartbeat messages periodically transmitted from the peer end over the inter-BSC interface. The
BEATSENDINGDIS parameter specifies the interval for sending heartbeat messages between
two BSCs.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 15

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

Heartbeat messages are transmitted over the Signaling Control Transmission Protocol (SCTP)
link on the inter-BSC interface. To check the status of the SCTP link, run the DSP
SCTPLNK command.
The local BSC is considered unable to provide services and will stop sending heartbeat messages
to the peer BSC when either of the following problems occurs:
l The local BSC fails and thereby cannot provide services.
l The CNSTATEPOLICYFORGROUP parameter is set to AINTFBLOCK(AInterf
Block), and the local BSC detects that the failure of all the signaling links on the A interface
lasts longer than the duration specified by CNFAULTDELAY.
NOTE

l The BSC Node Redundancy feature is allowed only if a BSC in a redundancy group fails or all the
signaling links on the A interface are disconnected. That is, service migration is not triggered if some
boards on a BSC become faulty.
l The transmission status of the Abis interface has no impact on this feature. Consequently, service
migration is not triggered if the transmission over the Abis interface is faulty.
l Service migration is not triggered if a BTS fails.

Upon detecting that the transmission of heartbeat messages has been interrupted for a period
longer than that specified by SLVSERVACTDELAY, the peer BSC considers that the local BSC
cannot provide services. The peer BSC then takes over the primary-homed service objects from
the local BSC.
Under extreme circumstances, if the peer BSC also fails after taking over the service objects, all
services are interrupted. In this case, if the local BSC recovers before the peer BSC does, the
local BSC takes back its primary-homed service objects from the peer BSC after a period
specified by MSTSERVACTDELAY.

3.4 Migrating Service Objects in the Event of a Failure

Two BSCs in a redundancy group manage their respective primary-homed service objects.
If the local BSC cannot provide services, the peer BSC takes over the dual-homed service objects
but not the single-homed service objects from the local BSC. The peer BSC takes over the control
rights of dual-homed OPCs and then dual-homed BTSs.
NOTE

If BSC Node Redundancy is deactivated after control rights are taken over, the peer BSC automatically
releases the control rights of the secondary-homed service objects. The local BSC then takes back the
control rights of the primary-homed service objects.

3.4.1 Migrating Dual-Homed OPCs

If the local BSC in a redundancy group cannot provide services, the single-homed OPCs of the
local BSC stop providing services and become faulty. The peer BSC then takes over the primary-
homed OPCs from the local BSC. These OPCs (secondary-homed OPCs of the peer BSC) are
immediately activated and start to provide services, and therefore these OPCs are changed from
not homed to homed.
MTP3-User Adaptation Layer (M3UA) links are configured to connect the OPC on the MSC
side to each OPC on the BSC side.
The M3UA link carrying the secondary-homed OPC of a BSC is deactivated, and the M3UA
link carrying the primary-homed OPC of a BSC is activated. However, if a BSC in a redundancy

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 16

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

group fails, the M3UA link carrying the primary-homed OPC of the BSC is deactivated, and the
M3UA link carrying the secondary-homed OPC of the other BSC is activated.

Figure 3-11 Migrating dual-homed OPCs

If the direct and alternative routes carrying heartbeat messages simultaneously become faulty
but the BSCs communicate with the CN correctly, the fault detection mechanism determines
that the dual-homed OPCs of the two BSCs are homed and the M3UA links for all the OPCs are
activated. In this scenario, only one OPC can be observed in the CN, and multiple M3UA links
can be observed under the OPC. When BSC 1 sends a message to the CN, the CN may send a
response message to BSC 2 through another M3UA link, thereby probably confusing message
transmission and interrupting all the services provided by the two BSCs.

3.4.2 Migrating Dual-Homed BTSs

After dual-homed OPCs are taken over, the control rights of dual-homed BTSs corresponding
to the dual-homed OPCs are migrated.
If the local BSC in a redundancy group cannot provide services, the single-homed BTSs of the
local BSC stop providing services and become faulty. The peer BSC then takes over the primary-
homed BTSs from the local BSC. These BTSs (secondary-homed BTSs of the peer BSC) are

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 17

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

immediately activated and start to provide services, and the value of Hosted for these BTSs is
therefore changed from No to Yes.
The procedure for migrating the control rights of dual-homed BTSs is as follows:
1. When the local BSC cannot provide services, the signaling links between the local BSC
and its dual-homed BTSs are disconnected.
2. The primary-homed BTS of the local BSC sends a signaling link establishment request to
the peer BSC according to the IP address sent by the local BSC.
3. After a signaling link is established, the peer BSC instructs the BTS to reset.
4. After the BTS resets, it sends a DHCP request to the peer BSC.
5. The peer BSC responds to the BTS with a DHCP response message, which carries the IP
address allocated to the BTS.
6. After receiving the IP address, the BTS resends a signaling link establishment request to
the peer BSC.
7. After a signaling link is established, the peer BSC sends the configuration data to the BTS.
The BTS is then taken over by the peer BSC and starts to provide services.

3.5 Neighboring Cells

The configuration of neighboring cells varies depending on the following scenarios:
l The BTSs controlled by a BSC are all dual-homed BTSs.
l The BTSs controlled by a BSC consist of dual- and single-homed BTSs.

3.5.1 All Dual-Homed BTSs

This scenario has high requirements for the BSC reliability. To meet the requirements, you must
configure all the BTSs and OPCs under two BSCs as dual-homed BTSs and OPCs. Specifically,
configure all the primary-homed BTSs under one BSC, or evenly configure the primary-homed
BTSs under the two BSCs.
If BSC 1 fails or all the signaling links on the A interface of BSC 1 are disconnected, BSC 2
takes over services from BSC 1, and all the BTSs previously controlled by BSC 1 now provide
services under BSC 2. BSCs 1 and 2 work in active/standby mode. Therefore, the maximum
number of services supported by the two BSCs together equals the specification of one BSC.
Figure 3-12 shows the network topology in this scenario.

Figure 3-12 All dual-homed BTSs

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 18

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

If two dual-homed BTSs are configured with a neighbor relationship, configure neighboring
cells using either of the following methods:
l Method 1: Configure cells in two separate BSCs as external neighboring cells of one
another.
l Method 2: Configure cells within a BSC as internal neighboring cells of one another.
If you attempt to configure a cell as both an internal neighboring cell and an external neighboring
cell on a BSC, the configuration fails.
Figure 3-13 shows the two configuration methods in load sharing mode.

Figure 3-13 Configuring neighboring cells in load sharing mode

As shown in Figure 3-13, cell 1 (primary-homed) and cell 1' (secondary-homed) are the same
cell served by dual-homed BTS 1, and cell 2 (primary-homed) and cell 2' (secondary-homed)
are the same cell served by dual-homed BTS 2.
l Method 1: On BSC 1, configure cell 2 as an external neighboring cell of cell 1 and cell 1'
as an external neighboring cell of cell 2'. On BSC 2, configure cell 1 as an external
neighboring cell of cell 2 and cell 2' as an external neighboring cell of cell 1'.
l Method 2: On BSC 1, configure cell 1 and cell 2' as a pair of internal neighboring cells. On
BSC 2, configure cell 1' and cell 2 as a pair of internal neighboring cells.
The two cells are bound to different OPCs. The BSC considers a handover that occurs between
two OPCs as an inter-BSC handover, regardless of whether the two OPCs belong to the same
BSC. Therefore, a handover from cell 1 to cell 2' is considered an inter-BSC handover.
Figure 3-14 shows the two configuration methods in active/standby mode.

Figure 3-14 Configuring neighboring cells in active/standby mode

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 19

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

As shown in Figure 3-14, cell 1 (primary-homed) and cell 1' (secondary-homed) are the same
cell served by dual-homed BTS 1, and cell 2 (primary-homed) and cell 2' (secondary-homed)
are the same cell served by dual-homed BTS 2.
l Method 1: On BSC 1, configure cell 2' as an external neighboring cell of cell 1 and cell 1'
as an external neighboring cell of cell 2. On BSC 2, configure cell 1 as an external
neighboring cell of cell 2' and cell 2 as an external neighboring cell of cell 1'.
l Method 2: On BSC 1, configure cell 1 and cell 2 as a pair of internal neighboring cells. On
BSC 2, configure cell 1' and cell 2' as a pair of internal neighboring cells.

3.5.2 Combination of Dual- and Single-Homed BTSs

This scenario enables a key BTS to quickly provide services when the serving BSC fails. In this
scenario, only one BTS is configured as a dual-homed BTS under two BSCs.
Figure 3-15 shows the network topology in this scenario.

Figure 3-15 Combination of dual- and single-homed BTSs

If BSC 1 fails or all the signaling links on the A interface of BSC 1 are disconnected, BTS 2 (the
only dual-homed BTS under the two BSCs) provides services under BSC 2. Since BTS 1 is
configured as a single-homed BTS under BSC 1, the services provided by the BTS are
interrupted. In this scenario, cells served by the dual-homed BTS must be bound to a dual-homed
OPC, and cells served by single-homed BTSs must be bound to a single-homed OPC. Therefore,
at least two OPCs are required.
If a dual-homed BTS and a single-homed BTS are configured with a neighbor relationship,
configure two cells in a BSC as a pair of internal neighboring cells and two cells in two separate
BSCs as a pair of external neighboring cells.
If you attempt to configure a cell as both an internal neighboring cell and an external neighboring
cell on a BSC, the configuration fails.
Figure 3-16 shows the configuration method in load sharing mode.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 20

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

Figure 3-16 Configuring neighboring cells in load sharing mode

As shown in Figure 3-16, cell 1 (primary-homed) and cell 1' (secondary-homed) are the same
cell served by dual-homed BTS 1, and cell 2 is served by single-homed BTS 2.
On BSC 1, configure cell 1' and cell 2 as a pair of internal neighboring cells. On BSC 2, configure
cell 2 as an external neighboring cell of cell 1.
The two cells are bound to different OPCs. Therefore, a handover between the two cells is
considered an inter-BSC handover.
Figure 3-17 shows the configuration method in active/standby mode.

Figure 3-17 Configuring neighboring cells in active/standby mode

As shown in Figure 3-17, cell 1 (primary-homed) and cell 1' (secondary-homed) are the same
cell served by dual-homed BTS 1, and cell 2 is served by single-homed BTS 2.
On BSC 1, configure cell 1 and cell 2 as a pair of internal neighboring cells. On BSC 2, configure
cell 2 as an external neighboring cell of cell 1'.
The two cells are bound to different OPCs. Therefore, a handover between the two cells is
considered an inter-BSC handover.

3.6 Migrating Back Dual-Homed Service Objects

If the local BSC in a redundancy group fails, the peer BSC takes over the primary-homed service
objects from the local BSC. When the local BSC recovers, the service objects taken over by the
peer BSC can be migrated back, depending on the policy specified by REHOSTTYPE:

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 21

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 3 Technical Description

l If REHOSTTYPE is set to REHOSTRIGHTNOW(ReHostRightNow), service objects

are migrated back immediately after the local BSC recovers.
l If REHOSTTYPE is set to REHOSTDELAY(ReHostDelay), service objects are migrated
back N seconds after the local BSC recovers, where N is specified by
REHOSTDELAYTIME.
l If REHOSTTYPE is set to REHOSTWHEN(ReHostWhen), service objects are migrated
back at the time specified by REHOSTABSTIME after the local BSC recovers.
REHOSTABSTIME must be set to a value in the format of hh:mm:ss.
The procedure for migrating back service objects and that for migrating service objects from a
failed BSC are the same except that they have reverse orders.

3.7 Maintaining Dual-Homed Service Objects

A service object is managed by only one BSC at a time. If the control rights of a dual-homed
service object are migrated from the local BSC to the peer BSC, the local BSC can no longer
maintain the service object. Therefore, a BSC can maintain only service objects that are homed.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 22

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 4 Related Features

4 Related Features

4.1 Abis over IP or Abis IP over E1/T1

The BSC Node Redundancy feature requires the GBFD-118601 Abis over IP or GBFD-118611
Abis IP over E1/T1 feature over the Abis interface.

4.2 A over IP, A IP over E1/T1, or A over IP Based on Dynamic

Load Balancing
l BSC6900:
The BSC Node Redundancy feature requires the GBFD-118602 A over IP or
GBFD-118622 A IP over E1/T1 feature over the A interface.
l BSC6910:
The BSC Node Redundancy feature requires the GBFD-150201 A over IP Based on
Dynamic Load Balancing feature over the A interface.

4.3 Local Multiple Signaling Points

The BSC Node Redundancy feature requires the GBFD-115301 Local Multiple Signaling Points
feature when either of the following conditions is true:
l The BSC has single-homed BTSs.
l The BSC works in load sharing mode.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 23

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 5 Network Impact

5 Network Impact

5.1 System Capacity

None

5.2 Network Performance

The BSC Node Redundancy feature improves the reliability of BSC equipment and transmission
over the A interface and shortens the service downtime. Services are interrupted for 10 to 20
minutes when service objects are being migrated or migrated back.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 24

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

6 Engineering Guidelines

6.1 When to Use BSC Node Redundancy

It is recommended that the BSC Node Redundancy feature be enabled in areas that have high
requirements for network reliability.

6.2 Required Information

Before deploying BSC Node Redundancy, collect the following information:
l Networking over different interfaces
l Networking in the CN
l Type of transmission interface boards on the BSC and BTS

6.3 Planning
RF Planning
None

Network Planning
The A, Abis, and inter-BSC interfaces use IP transmission. The Gb interface can use any
transmission mode. For details, see section 3.2.2 Networking Modes over the Abis/A/Gb/
Inter-BSC Interface.
A redundancy group consists of only two BSCs.
The two BSCs in a redundancy group connect to only one MSC/SGSN or MSC/SGSN pool.
A BTS cannot directly connect to a BSC over the Abis interface. Therefore, BTSs use routers
to connect to the two BSCs in a redundancy group.

Hardware Planning
IP interface boards are required for the BSC and BTS.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 25

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

BTSs other than the BTS3006C, BTS3002E, BTS3900B, and BTS3900E are supported.

6.4 Deployment

6.4.1 Requirements
Table 6-1 Deployment requirements
Aspect Requirement

Related features See chapter 4 Related Features.

BSC The BSC is configured with IP interface

boards.

BTS A BTS other than the BTS3006C,

BTS3002E, BTS3900B, and BTS3900E is
used, because they are not supported.
The BTS is configured with IP interface
boards.

GSM networking A redundancy group consists of only two

BSCs.
The two BSCs in a redundancy group connect
to only one MSC/SGSN or MSC/SGSN pool.
The A, Abis, and inter-BSC interfaces use IP
transmission. The Gb interface can use any
transmission mode.
A BTS cannot directly connect to a BSC over
the Abis interface. Therefore, BTSs use
routers to connect to the two BSCs in a
redundancy group.

MS None

MSC The MSC is configured with M3UA links and

M3UA link sets that connect to BSCs.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 26

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

Aspect Requirement

License The license controlling this feature has been

activated. For details about the license control
item, see License Control Item Description.
For details about how to activate the license,
see License Management Feature
Parameter Description.
NOTE
Assuming that the electronic serial numbers
(ESNs) for BSC 1 and BSC 2 are ESN 1 and ESN
2, respectively:
When only dual-homed BTSs are configured,
license 1 is generated when the order of BSC 1 is
bound to ESN 1 and ESN 2, and license 2 is
generated when the order of BSC 2 is bound to
ESN 1 and ESN 2. Licenses 1 and 2 are then
combined into one license file, which is loaded on
both BSCs.
When both single- and dual-homed BTSs are
configured, license 1 is generated when the order
of BSC 1 is bound to ESN 1, and license 2 is
generated when the order of BSC 2 is bound to
ESN 2. License 1 and license 2 are then loaded on
BSC 1 and BSC 2, respectively.
The licenses for enabling this feature on BSCs 1
and 2 have been obtained.

Others Two BSCs in a redundancy group are

configured with dual-homed service objects,
and the size of data for the single- and dual-
homed service objects configured under one
BSC must not exceed the specifications of the
BSC.
The WOFD-231100 BSC Redundancy
Management-GBSS feature is enabled on the
M2000.
Cell broadcast center (CBC) services do not
support this feature.
Only built-in packet control units (PCUs)
support this feature.
For a BTS under two BSCs in a redundancy
group, if the BTS is single-homed, it must be
configured only under one BSC; if the BTS is
dual-homed, it must be configured as a
primary-homed BTS under one BSC and a
secondary-homed BTS under the other BSC.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 27

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

6.4.2 Data Preparation

Table 6-2 Data preparation

Parameter Parameter ID NE Setting Notes Data Source

Name

The host type of HOSTTYPE BSC6900/ See section 3.1 Engineering

signalling point BSC6910 Dual- and design
Single-Homed
Service
Objects.

HostType HOSTTYPE BSC6900/ See section 3.1 Equipment plan

BSC6910 Dual- and
Single-Homed
Service
Objects.

Peer BSC IP PEERBSCIP BSC6900/ N/A Radio network

BSC6910 plan (negotiated
with the peer
end)

Peer BTS ID PEERBTSID BSC6900/ N/A Equipment plan

BSC6910

Peer BSC Mask PEERBSCMA BSC6900/ N/A Transmission

SK BSC6910 network plan
(negotiated with
the peer end)

Peer BSC ID PEERBSCID BSC6900/ N/A Transmission

BSC6910 network plan
(internal plan)

BSC Node GROUPINDE BSC6900/ N/A Engineering

Redundancy X BSC6910 design
Group Index

BSC Node GROUPNAME BSC6900/ N/A Engineering

Redundancy BSC6910 design
Group Name

Interval for BEATSENDIN BSC6900/ See section 3.3 Engineering

Sending GDIS BSC6910 Fault design
Heartbeat Detection.

Local BSC ID LocalBSCID BSC6900/ N/A Engineering

BSC6910 design

Peer BSC ID PeerBSCID BSC6900/ N/A Engineering

BSC6910 design

Master Service MSTSERVAC BSC6900/ N/A Engineering

Active Delay TDELAY BSC6910 design

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 28

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

Parameter Parameter ID NE Setting Notes Data Source

Name

Slave Service SLVSERVACT BSC6900/ N/A Engineering

Active Delay DELAY BSC6910 design

CN Fault Delay CNFAULTDE BSC6900/ N/A Engineering

LAY BSC6910 design

CN State Policy CNSTATEPOL BSC6900/ Set this Engineering

For Group ICYFORGRO BSC6910 parameter to design
UP AINTFBLOC
K(AInterf
Block).

ReHost Type REHOSTTYPE BSC6900/ See section 3.6 Engineering

BSC6910 Migrating design
Back Dual-
Homed Service
Objects.

ReHostDelayTi REHOSTDEL BSC6900/ See section 3.6 Engineering

me AYTIME BSC6910 Migrating design
Back Dual-
Homed Service
Objects.

ReHost REHOSTABST BSC6900/ See section 3.6 Engineering

Absolute Time IME BSC6910 Migrating design
Back Dual-
Homed Service
Objects.

Redundancy RedundancyM BSC6900/ Set this Engineering

Mode ode BSC6910 parameter to design
Automatic
(Automatic).

6.4.3 Precautions
Services are interrupted for 10 to 20 minutes when service objects are being migrated or migrated
back.

Disable the BSC Node Redundancy feature before upgrading a BSC and enable this feature after
the upgrade is complete.

6.4.4 Activation
Configure data for the BSC Node Redundancy feature by performing the following steps:

Step 1 Configure signaling points and signaling links over the A interface.

Step 2 Configure BTS data.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 29

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

Step 3 Configure signaling links connecting two BSCs.

Step 4 Configure the BSC Node Redundancy feature.

Configure other BSC data using the same method as that in common scenarios. For details, see
BSC6900 GSM Initial Configuration Guide or BSC6910 GSM Initial Configuration Guide.

NOTE

When BSC Node Redundancy is enabled, the data about BTSs and OPCs is configured in redundancy mode
on two BSCs. Therefore, after configuring data on one BSC, copy the configuration scripts to the other
BSC, thereby improving operation and maintenance (O&M) efficiency. However, manually modify the
following parameters because they must be set to different values on the two BSCs:
l The host type of signalling point
l HostType
l Local BSC ID
l Peer BSC ID
l BSC IP
l Peer BSC IP.

----End

Using the LMT

l Configuring data on BSC 1 LMT

Step 1 Configure signaling points and signaling links over the A interface.
NOTE

In load sharing mode, configure both primary- and secondary-homed OPCs and signaling links. In active/
standby mode, configure primary- or secondary-homed OPCs and signaling links.
If the BSC has single-homed BTSs, configure single-homed OPCs and signaling links in the same method
as that in common scenarios. For details, see BSC6900 GSM Initial Configuration Guide or BSC6910 GSM
Initial Configuration Guide.

To configure the primary-homed OPC and signaling links for BSC 1, perform the following
steps:

1. On BSC 1 LMT, run the ADD OPC command with its parameters set as follows:
l Set OSP name, OSP index, Network ID, OSP code bits, Signal point data format,
and OSP code to appropriate values.
l Set The host type of signalling point to PRIMHOST(PRIMHOST).
2. Run the ADD N7DPC command to add a destination signaling point (DSP) for the primary-
homed OPC. In this step, set DSP name, DSP index, OSP index, Signal point data
format, DSP code, DSP type, and DSP bear type to appropriate values.
3. Run the ADD M3LE command to add an M3UA local entity for the primary-homed OPC.
In this step, set OSP index to the same value as that for the primary-homed OPC.
4. Run the ADD M3DE command to add an M3UA destination entity for the primary-homed
OPC. In this step, set DSP index to the same value as that for the primary-homed OPC.
5. Run the ADD M3LKS command to add an M3UA link set for the primary-homed OPC.
In this step, set Destination entity No. to the same value as that for the primary-homed
OPC.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 30

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

6. Run the ADD M3RT command to add an M3UA route for the primary-homed OPC. In
this step, set Destination entity No. and Signalling link set index to the same values as
those for the primary-homed OPC.
7. Run the ADD SCTPLNK command to add an SCTP link for the primary-homed OPC. In
this step, set First local IP address, First destination IP address, and Destination SCTP
port No. to appropriate values.
8. Run the ADD M3LNK command to add an M3UA link for the primary-homed OPC. In
this step, set SCTP link No. to the same value as that for the primary-homed OPC.
Configure secondary-homed OPCs and signaling links using the same method. For details, see
"Configuring data on BSC 2 LMT."
Step 2 Configure BTS data.
NOTE

l The configuration data for a dual-homing BTS must be consistent on BSC 1 and BSC 2. For a BTS
configured on two BSCs, it is possible that the value of BTS NAME is the same while the value of
BTS ID is different on the two BSCs. During routine maintenance, if you change the value of a BTS-
related parameter on BSC 1, simultaneously change the value of this parameter on BSC 2. To improve
O&M efficiency, set BTS ID to the same value on both BSCs.
l Configure a single-homed BTS using the same methods as those in common scenarios. For details, see
BSC6900 GSM Initial Configuration Guide or BSC6910 GSM Initial Configuration Guide.
l Set BSC IP, HostType, and Peer BSC IP to the values negotiated between the two BSCs.

To configure a dual-homed BTS for BSC 1 and BSC 2, perform the following steps:
1. Add a BTS onto BSC 1. For details, see BSC6900 GSM Initial Configuration Guide or
BSC6910 GSM Initial Configuration Guide.
NOTE

Set HostType to an appropriate value when you run the ADD BTS command on BSC 1 LMT.
2. On BSC 1 LMT, run the SET BTSIP command with BTS IP, BSC IP, Peer BTS ID,
Peer BSC IP, Peer BSC ID, and Peer BSC Mask set to appropriate values. Among them,
BSC IP and Peer BSC IP indicate the two BSCs' IP addresses simultaneously obtained by
the BTS when being configured.
3. Run the ADD BTSIPRT command to add routes from the BTS to the two BSCs.
4. Configure neighboring cells by following the principles described in section 3.5
Neighboring Cells. For details, see BSC6900 GSM Initial Configuration Guide or
BSC6910 GSM Initial Configuration Guide.
5. Configure PTP BVCs for the cells served by the dual-homed BTS on the two BSCs. For
details, see BSC6900 GSM Initial Configuration Guide or BSC6910 GSM Initial
Configuration Guide.
To configure multiple dual-homed BTSs for BSC 1 and BSC 2, repeat step 2.
Step 3 Configure signaling links connecting two BSCs.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 31

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

NOTE

The following rules apply when you configure signaling links connecting two BSCs:
l Set First local IP address and Second local IP address for BSC 1 to the same values as those of First
destination IP address and Second destination IP address for BSC 2, respectively.
l Set First destination IP address and Second destination IP address for BSC 1 to the same values
as those of First local IP address and Second local IP address for BSC 2, respectively.
l Set Local SCTP port No. and Destination SCTP port No. for BSC 1 to the same values as those of
Destination SCTP port No. and Local SCTP port No. for BSC 2, respectively.
l Configure multiple signaling links connecting two BSCs, and ensure that the configuration data is
consistent on both BSCs.

1. On BSC 1 LMT, run the ADD SCTPLNK command with Signalling link mode set to
CLIENT(CLIENT MOD) and Application type set to BBAP(BBAP).
2. (Optional): If BSC 1 connects to BSC 2 through intermediate equipment, run the ADD
IPRT command to add an IP route from BSC 1 to the intermediate equipment.
Step 4 Configure the BSC Node Redundancy feature.
1. Run the SET GBSCREDGRP command to configure data for a redundancy group. In this
step, set Local BSC ID and Peer BSC ID for BSC 1 to the same values as those of Peer
BSC ID and Local BSC ID for BSC 2, respectively.
2. Run the SET GREDGRPHOSTPOLICY command with CN State Policy For Group
set to AINTFBLOCK(AInterf Block) and ReHost Type set to an appropriate value.
3. Run the SET GNODEREDUNDANCY command with Redundancy Mode set to
Automatic(Automatic).

----End

l Configuring data on BSC 2 LMT

Step 1 Configure signaling points and signaling links over the A interface.
NOTE

In load sharing mode, configure both primary- and secondary-homed OPCs and signaling links. In active/
standby mode, configure primary- or secondary-homed OPCs and signaling links.
If the BSC has single-homed BTSs, configure single-homed OPCs and signaling links in the same method
as that in common scenarios. For details, see BSC6900 GSM Initial Configuration Guide or BSC6910 GSM
Initial Configuration Guide.

To configure secondary-homed OPCs and signaling links, perform the following steps:
1. On BSC 2 LMT, run the ADD OPC command with its parameters set as follows:
l Set OSP name, OSP index, Network ID, OSP code bits, Signal point data format,
and OSP code to appropriate values.
l Set The host type of signalling point to SLAVEHOST(SLAVEHOST).
2. Run the ADD N7DPC command to add a DSP for the secondary-homed OPC. In this step,
set DSP name, DSP index, OSP index, Signal point data format, DSP code, DSP
type, and DSP bear type to appropriate values.
3. Run the ADD M3LE command to add an M3UA local entity for the secondary-homed
OPC. In this step, set OSP index to the same value as that for the secondary-homed OPC.
4. Run the ADD M3DE command to add an M3UA destination entity for the secondary-
homed OPC. In this step, set DSP index to the same value as that for the secondary-homed
OPC.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 32

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

5. Run the ADD M3LKS command to add an M3UA link set for the secondary-homed OPC.
In this step, set Destination entity No. to the same value as that for the secondary-homed
OPC.
6. Run the ADD M3RT command to add an M3UA route for the secondary-homed OPC. In
this step, set Destination entity No. and Signalling link set index to the same values as
those for the secondary-homed OPC.
7. Run the ADD SCTPLNK command to add an SCTP link for the secondary-homed OPC.
In this step, set First local IP address, First destination IP address, and Destination
SCTP port No. to appropriate values.
8. Run the ADD M3LNK command to add an M3UA link for the secondary-homed OPC. In
this step, set SCTP link No. to the same value as that for the secondary-homed OPC.
You can configure primary-homed OPCs and signaling links using the same method. For details,
see "Configuring data on BSC 1 LMT."
Step 2 Configure BTS data.
NOTE

l The configuration data for a dual-homing BTS must be consistent on BSC 1 and BSC 2. For a BTS
configured on two BSCs, it is possible that the value of BTS NAME is the same while the value of
BTS ID is different on the two BSCs. During routine maintenance, if you change the value of a BTS-
related parameter on BSC 1, change the value of this parameter on BSC 2. To improve O&M efficiency,
set BTS ID to the same value on both BSCs.
l Configure a single-homed BTS using the same methods as those in common scenarios. For details, see
BSC6900 GSM Initial Configuration Guide or BSC6910 GSM Initial Configuration Guide.
l Set BSC IP, HostType, and Peer BSC IP to the values negotiated between the two BSCs.

To configure a dual-homed BTS for BSC 1 and BSC 2, perform the following steps:
1. Add a BTS to BSC 2. For details, see BSC6900 GSM Initial Configuration Guide or
BSC6910 GSM Initial Configuration Guide.
NOTE

Set HostType to an appropriate value when you run the ADD BTS command on BSC 2 LMT.
2. On BSC 2 LMT, run the SET BTSIP command with BTS IP, BSC IP, Peer BTS ID,
Peer BSC IP, Peer BSC ID, and Peer BSC Mask set to appropriate values. Among them,
BSC IP and Peer BSC IP indicate the two BSCs' IP addresses simultaneously obtained by
the BTS when being configured.
3. Run the ADD BTSIPRT command to add routes from the BTS to the two BSCs.
4. Configure neighboring cells by following the principles described in section 3.5
Neighboring Cells. For details, see BSC6900 GSM Initial Configuration Guide or
BSC6910 GSM Initial Configuration Guide.
5. Configure PTP BVCs for the cells served by the dual-homed BTS on the two BSCs. For
details, see BSC6900 GSM Initial Configuration Guide or BSC6910 GSM Initial
Configuration Guide.
To configure multiple dual-homed BTSs for BSC 1 and BSC 2, repeat step 2.
Step 3 Configure signaling links connecting two BSCs.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 33

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

NOTE

The following rules apply when you configure signaling links connecting two BSCs:
l Set First local IP address and Second local IP address for BSC 1 to the same values as those of First
destination IP address and Second destination IP address for BSC 2, respectively.
l Set First destination IP address and Second destination IP address for BSC 1 to the same values
as those of First local IP address and Second local IP address for BSC 2, respectively.
l Set Local SCTP port No. for BSC 1 to the same value as that of Destination SCTP port No. for BSC
2.
l Configure multiple signaling links connecting two BSCs, and ensure that the configuration data is
consistent on both BSCs.

1. On BSC 2 LMT, run the ADD SCTPLNK command with Signalling link mode set to
SERVER(SERVER MOD) and Application type set to BBAP(BBAP).
2. (Optional): If BSC 1 connects to BSC 2 through intermediate equipment, run the ADD
IPRT command to add an IP route from BSC 2 to the intermediate equipment.
Step 4 Configure the BSC Node Redundancy feature.
1. On BSC 2 LMT, run the SET GBSCREDGRP command to configure data for a
redundancy group. In this step, set Local BSC ID and Peer BSC ID for BSC 2 to the same
values as those of Peer BSC ID and Local BSC ID for BSC 1, respectively.
2. Run the SET GREDGRPHOSTPOLICY command with CN State Policy For Group
set to AINTFBLOCK(AInterf Block) and ReHost Type set to an appropriate value.
3. Run the SET GNODEREDUNDANCY command with Redundancy Mode set to
Automatic(Automatic).

----End

MML Command Examples

//Configuring data on BSC 1 LMT
//Configuring signaling points and signaling links over the A interface
ADD OPC: NAME="A", SPX=0, NI=NATB, SPCBITS=BIT14, SPDF=WNF, SPC=2730,
HOSTTYPE=PRIMHOST;
ADD N7DPC: NAME="A to MSC", DPX=0, SPX=0, SPDF=WNF, DPC=4369, DPCT=A,
BEARTYPE=M3UA;
ADD M3LE: LENO=0, SPX=0, ENTITYT=M3UA_IPSP, NAME="0";
ADD M3DE: DENO=0, LENO=0, DPX=0, ENTITYT=M3UA_IPSP, NAME="0";
ADD M3LKS: SIGLKSX=0, DENO=0, WKMODE=M3UA_IPSP, NAME="0";
ADD M3RT: DENO=0, SIGLKSX=0, NAME="0";
//BSC6900:
ADD SCTPLNK: SRN=0, SN=2, SCTPLNKN=1, MODE=CLIENT, APP=M3UA,
LOCIP1="192.3.0.111", PEERIP1="192.3.0.2", PEERPN=6000,
LOGPORTFLAG=NO, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE,
SWITCHBACKFLAG=YES;
//BSC6910:

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 34

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

ADD SCTPLNK: SCTPLNKID=1, MODE=CLIENT, APP=M3UA, LOCIP1="192.3.0.111",

PEERIP1="192.3.0.2", PEERPN=6000,
LOGPORTFLAG=NO, SWITCHBACKFLAG=YES;
//BSC6900:
ADD M3LNK: SIGLKSX=0, SIGLNKID=0, SRN=0, SN=2, SCTPLNKN=1, NAME="0";
//BSC6910:
ADD M3LNK: SIGLKSX=0, SIGLNKID=0, SCTPLNKID=1, NAME="0";

//Configuring BTS attributes

ADD BTS: BTSID=72, BTSNAME="bts3900", BTSTYPE=BTS3900_GSM,
SERVICEMODE=IP, SRANMODE=SUPPORT, INNBBULICSHAEN=NO,
HOSTTYPE=PRIMHOST;
SET BTSIP:BTSID=72, IDTYPE=BYID, BSCIP="172.18.125.124",
BTSIP="166.253.121.10", BTSCOMTYPE=PORTIP, PEERBTSID=172,
PEERBSCIP="172.18.125.69", PEERBSCMASK="255.255.255.255", PEERBSCID=1,
CFGFLAG=NULL, BTSGWIPSWITCH=OFF;

//Configuring BTS routes

ADD BTSIPRT: IDTYPE=BYID, BTSID=72, DSTIP="172.18.125.124",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="166.253.121.4";
ADD BTSIPRT: IDTYPE=BYID, BTSID=72, DSTIP="172.18.125.69",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="166.253.121.4";

//Configuring neighboring cells (Cells 1 and 2046 are both dual-homed cells.)
ADD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=1, NBR2GNCELLID=2046,
NCELLTYPE=HANDOVERNCELL, SRCHOCTRLSWITCH=HOALGORITHM1;
ADD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=2046, NBR2GNCELLID=1,
NCELLTYPE=HANDOVERNCELL, SRCHOCTRLSWITCH=HOALGORITHM1;

//Configuring PTP BVCs

ADD PTPBVC: NSEI=0, BVCI=6, IDTYPE=BYNAME, CELLNAME="cell-11";

//Configuring signaling links connecting two BSCs

//BSC6900:
ADD SCTPLNK: SRN=0, SN=2, SCTPLNKN=0, MODE=CLIENT, APP=BBAP,
LOCPN=5000, LOCIP1="192.3.0.111", LOCIP2="10.161.39.111", PEERIP1="192.3.0.110",
PEERIP2="10.161.39.110", PEERPN=58000, LOGPORTFLAG=NO,
VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;
//BSC6910:
ADD SCTPLNK: SCTPLNKID=0, MODE=CLIENT, APP=BBAP, LOCPN=5000,
LOCIP1="192.3.0.111", LOCIP2="10.161.39.111", PEERIP1="192.3.0.110",

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 35

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

PEERIP2="10.161.39.110", PEERPN=58000, LOGPORTFLAG=NO,

SWITCHBACKFLAG=YES;

//Configuring BSC Node Redundancy

SET GBSCREDGRP: GROUPINDEX=0, LocalBSCID=0, PeerBSCID=1;
SET GREDGRPHOSTPOLICY: CNSTATEPOLICYFORGROUP=AINTFBLOCK,
REHOSTTYPE=REHOSTDELAY, REHOSTDELAYTIME=60;
SET GNODEREDUNDANCY: RedundancyMode=Automatic;

//Configuring data on BSC 2 LMT

//Configuring signaling points and signaling links over the A interface
ADD OPC: NAME="A", SPX=0, NI=NATB, SPCBITS=BIT14, SPDF=WNF, SPC=2730,
HOSTTYPE=SLAVEHOST;
ADD N7DPC: NAME="A to MSC", DPX=0, SPX=0, SPDF=WNF, DPC=4369, DPCT=A,
BEARTYPE=M3UA;
ADD M3LE: LENO=0, SPX=0, ENTITYT=M3UA_IPSP, NAME="0";
ADD M3DE: DENO=0, LENO=0, DPX=0, ENTITYT=M3UA_IPSP, NAME="0";
ADD M3LKS: SIGLKSX=0, DENO=0, WKMODE=M3UA_IPSP, NAME="0";
ADD M3RT: DENO=0, SIGLKSX=0, NAME="0";
//BSC6900:
ADD SCTPLNK: SRN=0, SN=2, SCTPLNKN=1, MODE=CLIENT, APP=M3UA,
LOCIP1="192.3.0.110", PEERIP1="192.3.0.2", PEERPN=6000,
LOGPORTFLAG=NO, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE,
SWITCHBACKFLAG=YES;
//BSC6910:
ADD SCTPLNK: SCTPLNKID=1, MODE=CLIENT, APP=M3UA, LOCIP1="192.3.0.110",
PEERIP1="192.3.0.2", PEERPN=6000,
LOGPORTFLAG=NO, SWITCHBACKFLAG=YES;
//BSC6900:
ADD M3LNK: SIGLKSX=0, SIGLNKID=0, SRN=0, SN=2, SCTPLNKN=1, NAME="0";
//BSC6910:
ADD M3LNK: SIGLKSX=0, SIGLNKID=0, SCTPLNKID=1, NAME="0";

//Configuring BTS attributes

ADD BTS: BTSID=172, BTSNAME="bts3900s", BTSTYPE=BTS3900_GSM,
SERVICEMODE=IP, SRANMODE=SUPPORT, INNBBULICSHAEN=NO,
HOSTTYPE=SLAVEHOST;
SET BTSIP:BTSID=172, IDTYPE=BYID, BSCIP="172.18.125.69",
BTSIP="166.253.121.10", BTSCOMTYPE=PORTIP, PEERBTSID=72,

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 36

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

PEERBSCIP="172.18.125.124", PEERBSCMASK="255.255.255.255", PEERBSCID=0,

CFGFLAG=NULL, BTSGWIPSWITCH=OFF;

//Configuring BTS routes

ADD BTSIPRT: IDTYPE=BYID, BTSID=172, DSTIP="172.18.125.124",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="166.253.121.4";
ADD BTSIPRT: IDTYPE=BYID, BTSID=172, DSTIP="172.18.125.69",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="166.253.121.4";

//Configuring neighboring cells (Cells 1 and 2046 are both dual-homed cells.)
ADD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=1, NBR2GNCELLID=2046,
NCELLTYPE=HANDOVERNCELL, SRCHOCTRLSWITCH=HOALGORITHM1;
ADD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=2046, NBR2GNCELLID=1,
NCELLTYPE=HANDOVERNCELL, SRCHOCTRLSWITCH=HOALGORITHM1;

//Configuring PTP BVCs

ADD PTPBVC: NSEI=1, BVCI=6, IDTYPE=BYNAME, CELLNAME="cell-11";
//Configuring signaling links connecting two BSCs
//BSC6900:
ADD SCTPLNK: SRN=0, SN=2, SCTPLNKN=0, MODE=CLIENT, APP=BBAP,
LOCPN=58000, LOCIP1="192.3.0.110", LOCIP2="10.161.39.110",
PEERIP1="192.3.0.111",
PEERIP2="10.161.39.111", PEERPN=5000, LOGPORTFLAG=NO,
VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;
//BSC6910:
ADD SCTPLNK: SCTPLNKID=0, MODE=CLIENT, APP=BBAP, LOCPN=58000,
LOCIP1="192.3.0.110", LOCIP2="10.161.39.110", PEERIP1="192.3.0.111",
PEERIP2="10.161.39.111", PEERPN=5000, LOGPORTFLAG=NO,
SWITCHBACKFLAG=YES;
//Configuring BSC Node Redundancy
SET GBSCREDGRP: GROUPINDEX=0, LocalBSCID=1, PeerBSCID=0;
SET GREDGRPHOSTPOLICY: CNSTATEPOLICYFORGROUP=AINTFBLOCK,
REHOSTTYPE=REHOSTDELAY, REHOSTDELAYTIME=60;
SET GNODEREDUNDANCY: RedundancyMode=Automatic;

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 37

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

Using the CME

NOTE

l When configuring the BSC Node Redundancy feature on the CME, perform a single configuration
first, and then perform a batch modification if required.
l Configure the parameters of a single object before a batch modification. Perform a batch modification
before logging out of the parameter setting interface.

Step 1 Configure a single object (such as a cell) on the CME.

Set parameters on the CME according to the operation sequence in Table 6-3. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.

Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)

To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.

----End

Table 6-3 Configuring parameters on the CME

SN Managed NE Parameter Parameter Configura

Object Name ID ble in CME
(MO) Batch
Modificati
on Center

1 OPC BSC6900/ OSP name NAME No

BSC6910
OSP index SPX

Network ID NI

OSP code SPCBITS

bits

Signal point SPDF

data format

OSP code SPC

[Whole
Number]

The host type HOSTTYPE

of signalling
point

2 N7DPC BSC6900/ DSP name NAME No

BSC6910
DSP index DPX

OSP index SPX

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 38

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

SN Managed NE Parameter Parameter Configura

Object Name ID ble in CME
(MO) Batch
Modificati
on Center

Signal point SPDF

data format

DSP code DPC

[Whole
Number]

DSP type DPCT

DSP bear BEARTYPE

type

3 M3LE BSC6900/ Local entity LENO No

BSC6910 No.

OSP index SPX

Local entity ENTITYT

type

Local entity NAME

name

4 M3DE BSC6900/ Destination DENO No

BSC6910 entity No.

Local entity LENO

No.

DSP index DPX

Destination ENTITYT
entity type

Destination NAME
entity name

5 M3LKS BSC6900/ Signalling SIGLKSX No

BSC6910 link set index

Destination DENO
entity No.

Work mode WKMODE

M3UA NAME
Signalling
link set name

6 M3RT BSC6900/ Destination DENO No

BSC6910 entity No.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 39

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

SN Managed NE Parameter Parameter Configura

Object Name ID ble in CME
(MO) Batch
Modificati
on Center

Signalling SIGLKSX
link set index

M3UA route NAME

name

7 SCTPLNK BSC6900/ Signalling MODE No

BSC6910 link mode

Application APP
type

First local IP LOCIP1

address

First PEERIP1
destination
IP address

Destination PEERPN
SCTP port
No.

8 M3LNK BSC6900/ Signalling SIGLKSX No

BSC6910 link set index

Signaling SIGLNKID
link ID

M3UA NAME
Signaling
link name

9 BTS BSC6900/ BTS Index BTSID No

BSC6910
BTS Name BTSNAME

BTS Type BTSTYPE

Service SERVICEM
mode ODE

HostType HOSTTYPE

10 BTSIP BSC6900/ BSC IP BSCIP No

BSC6910
BTS IP BTSIP

BTS BTSCOMT
Communicat YPE
ion Type

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 40

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

SN Managed NE Parameter Parameter Configura

Object Name ID ble in CME
(MO) Batch
Modificati
on Center

Peer BTS ID PEERBTSI

D

Peer BSC IP PEERBSCI

P

Peer BSC PEERBSC

Mask MASK

Peer BSC ID PEERBSCI

D

11 BTSIPRT BSC6900/ Destination DSTIP No

BSC6910 IP Address

Destination DSTMASK
Address
Mask

Route Type RTTYPE

Forward NEXTHOP
Route
Address

12 G2GNCELL BSC6900/ Source Cell SRC2GNCE No

BSC6910 Index LLID

Neighbor 2G NBR2GNC
Cell Index ELLID

Neighboring NCELLTYP
Cell Type E

13 PTPBVC BSC6900/ NSE NSEI No

BSC6910 Identifier

PTP BVC BVCI

Identifier

Cell Name CELLNAM

E

14 SCTPLNK BSC6900/ Signalling MODE No

BSC6910 link mode

Application APP
type

Local SCTP LOCPN

port No.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 41

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

SN Managed NE Parameter Parameter Configura

Object Name ID ble in CME
(MO) Batch
Modificati
on Center

First local IP LOCIP1

address

First PEERIP1
destination
IP address

Destination PEERPN
SCTP port
No.

15 IPRT BSC6900/ Destination DSTIP No

NOTE BSC6910 IP address
A route is
required if Destination DSTMASK
two BSCs address mask
are
connected Forward NEXTHOP
through route address
intermediate
equipment. Priority PRIORITY

16 GBSCRED BSC6900/ BSC Node GROUPIN No

GRP BSC6910 Redundancy DEX
Group Index

Local BSC LocalBSCI

ID D

Peer BSC ID PeerBSCID

17 GREDGRP BSC6900/ ReHost Type REHOSTTY Yes

HOSTPOLI BSC6910 PE
CY
ReHostDela REHOSTD
yTime ELAYTIME

CN State CNSTATEP
Policy For OLICYFOR
Group GROUP

18 GNODERE BSC6900/ Redundancy Redundancy No

DUNDANC BSC6910 Mode Mode
Y

6.4.5 Activation Observation

In the examples provided in this section, the queried BTS and OPC are configured as primary-
homed service objects under BSC 1 and as secondary-homed service objects under BSC 2.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 42

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

l Querying information about BSC Node Redundancy when both BSCs work correctly
1. On BSC 1 LMT, run the DSP BTSSTAT command to check the homing status of the dual-
homed BTS.
Expected result: The value of Hosted is Yes.
2. Run the DSP M3LNK command to check the status of an M3UA link.
Expected result: The value of Administrative state is Uninhibited.
3. Run the DSP OPC command to check the homing status of the dual-homed OPC.
Expected result: The value of OPC host state is Yes.
4. On BSC 2 LMT, run the DSP BTSSTAT command to check the homing status of the dual-
homed BTS.
Expected result: The value of Hosted is No.
5. Run the DSP M3LNK command to check the status of an M3UA link.
Expected result: The value of Administrative state is Inhibited.
6. Run the DSP OPC command to check the homing status of the dual-homed OPC.
Expected result: The value of OPC host state is No.

l Verifying BSC Node Redundancy when a BSC fails

1. Power off BSC 1 and wait 20 minutes.
2. On BSC 2 LMT, run the DSP BTSSTAT command to check the homing status of the dual-
homed BTS.
Expected result: The value of Hosted is Yes.
3. Run the DSP M3LNK command to check the status of an M3UA link.
Expected result: The value of Administrative state is Uninhibited.
4. Run the DSP OPC command to check the homing status of the dual-homed OPC.
Expected result: The value of OPC host state is Yes.
5. Power on BSC 1 and wait 20 minutes.
6. On BSC 1 LMT and BSC 2 LMT, run the DSP BTSSTAT command to check the homing
status of the dual-homed BTS controlled by each BSC.
Expected result: The value of Hosted is Yes for BSC 1 and No for BSC 2.
7. Run the DSP M3LNK command to check the status of an M3UA link connecting to each
BSC.
Expected result: The value of Administrative state is Uninhibited for BSC 1 and
Inhibited for BSC 2.
8. Run the DSP OPC command to check the homing status of the dual-homed OPC of each
BSC.
Expected result: The value of OPC host state is Yes for BSC 1 and No for BSC 2.

l Verifying BSC Node Redundancy when all the signaling links on the A interface are
disconnected
1. On BSC 1 LMT, run the DEA M3LNK command to deactivate all the M3UA links on the
A interface. Then, wait 20 minutes.
2. On BSC 2 LMT, run the DSP BTSSTAT command to check the homing status of the dual-
homed BTS.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 43

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

Expected result: The value of Hosted is Yes.

3. Run the DSP M3LNK command to check the status of an M3UA link.
Expected result: The value of Administrative state is Uninhibited.
4. Run the DSP OPC command to check the homing status of the dual-homed OPC.
Expected result: The value of OPC host state is Yes.
5. On BSC 1 LMT, run the ACT M3LNK command to activate all the M3UA links on the
A interface. Then, wait 20 minutes.
6. On BSC 1 LMT and BSC 2 LMT, run the DSP BTSSTAT command to check the homing
status of the dual-homed BTS controlled by each BSC.
Expected result: The value of Hosted is Yes for BSC 1 and No for BSC 2.
7. Run the DSP M3LNK command to check the status of an M3UA link connecting to each
BSC.
Expected result: The value of Administrative state is Uninhibited for BSC 1 and
Inhibited for BSC 2.
8. Run the DSP OPC command to check the homing status of the dual-homed OPC of each
BSC.
Expected result: The value of OPC host state is Yes for BSC 1 and No for BSC 2.

6.4.6 Deactivation

Using the LMT

On BSC 1 LMT and BSC 2 LMT, run the SET GNODEREDUNDANCY command with
Redundancy Mode set to NO_Redundancy(No Redundancy) on each BSC.

MML Command Examples

SET GNODEREDUNDANCY: RedundancyMode=NO_Redundancy;

Using the CME

NOTE

l When configuring the BSC Node Redundancy feature on the CME, perform a single configuration
first, and then perform a batch modification if required.
l Configure the parameters of a single object before a batch modification. Perform a batch modification
before logging out of the parameter setting interface.

Step 1 Configure a single object (such as a cell) on the CME.

Set the parameter described in Table 6-4 on the CME. For instructions on how to perform the
CME single configuration, see CME Single Configuration Operation Guide.

Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)

To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.

----End

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 44

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 6 Engineering Guidelines

Table 6-4 Configuring the parameter on the CME

MO NE Parameter Parameter ID Configurable
Name in CME Batch
Modification
Center

GNODEREDU BSC6900/ Redundancy RedundancyM No

NDANCY BSC6910 Mode ode

6.5 Performance Monitoring

None

6.6 Parameter Optimization

None

6.7 Troubleshooting
When two BSCs in a redundancy group work correctly, they regularly check the homing
attributes of BTSs and the homing status of service objects of each other.
l When a BSC detects that the homing attributes of a BTS conflict on the two BSCs, the BSC
reports ALM-21815 Dual-Hosted BTS Configuration Error.
l When a BSC detects that the homing status of a service object conflicts on the two BSCs,
the BSCs perform different operations depending on the actual conditions:
– If a service object is not homed onto the two BSCs, the primary- and secondary-homed
BSCs wait a period specified by MSTSERVACTDELAY and
SLVSERVACTDELAY respectively and then initiate negotiations with the peer BSC
to determine which BSC can obtain the control rights of the service object.
– If a service object is homed on both BSCs, the primary-homed BSC takes over the
service object from the secondary-homed BSC immediately after the link carrying
heartbeat messages recovers.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 45

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

7 Parameters

Table 7-1 Parameter description

Parameter ID NE MML Feature ID Feature Name Description
Command

RedundancyM BSC6900/ SET GBFD-118602 A over IP Meaning:Behav

ode BSC6910 GNODEREDU ior of the other
NDANCY BSC when one
BSC in a
redundancy
group is faulty.
When this
parameter is set
to
No_Redundanc
y and one BSC is
faulty, the other
BSC does not
perform any
operation, and
the services
provided by the
faulty BSC are
interrupted.
When this
parameter is set
to Automatic
and one BSC is
faulty, the other
BSC
automatically
takes over
services from
the faulty BSC.
When this
parameter is set
to Manual, a

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 46

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

switchover
command is
executed to
migrate services
provided by one
BSC to the other
BSC.
GUI Value
Range:NO_Red
undancy(No
Redundancy),
Automatic
(Automatic),
Manual
(Manual)
Unit:None
Actual Value
Range:NO_Red
undancy,
Automatic,
Manual
Default
Value:NO_Red
undancy(No
Redundancy)

LocalBSCID BSC6900/ SET GBFD-113725 BSC Node Meaning:ID of

BSC6910 GBSCREDGR Redundancy the local BSC in
P the BSC node
redundancy
group.
GUI Value
Range:0~65534
Unit:None
Actual Value
Range:0~65534
Default
Value:None

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 47

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

PeerBSCID BSC6900/ SET GBFD-113725 BSC Node Meaning:ID of

BSC6910 GBSCREDGR Redundancy the peer BSC in
P the BSC node
redundancy
group.
GUI Value
Range:0~65534
Unit:None
Actual Value
Range:0~65534
Default
Value:None

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 48

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

GROUPINDE BSC6900/ SET GBFD-113725 BSC Node Meaning:Index

X BSC6910 GBSCREDGR Redundancy of the BSC Node
P Redundancy
Group. It
identifies a BSC
redundancy
group. The BSC
node
redundancy is a
function through
which two BSCs
form a
redundancy
group when the
all-IP
transmission
mode is applied.
The two BSCs in
a redundancy
group work in 1
+1 load sharing
mode. When one
BSC in a
redundancy
group is faulty or
all the signaling
links on the A
interface are
faulty, the other
BSC in this
group takes over
the voice and
data services. In
this manner, the
reliability and
robustness of the
network are
improved, the
service
disruption time
due to BSC
failure is
reduced, and the
quality of
service (QoS) is
improved.
GUI Value
Range:0~65534
Unit:None

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 49

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

Actual Value
Range:0~65534
Default
Value:None

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 50

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

HOSTTYPE BSC6900/ ADD OPC GBFD-113725 BSC Node Meaning:Indi-

BSC6910 MOD OPC Redundancy cates the host
type of the
signalling point.
When the BSC
node
redundancy
feature is
enabled, the
primary BSC
and the
secondary BSC
each must be
configured with
a signaling point
coded in the
same mode. The
host type of the
signaling point
of the primary
BSC is set to
"PRIMHOST",
and the host type
of the signaling
point of the
secondary BSC
is set to
"SLAVEHOST
". When the BSC
node
redundancy
feature is
disabled, the
host type of the
signaling point
of the BSC is set
to
"SINGLEHOST
".
GUI Value
Range:SINGLE
HOST
(SINGLEHOST
), PRIMHOST
(PRIMHOST),
SLAVEHOST
(SLAVEHOST)
Unit:None

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 51

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

Actual Value
Range:SINGLE
HOST,
PRIMHOST,
SLAVEHOST
Default
Value:SINGLE
HOST
(SINGLEHOST
)

HOSTTYPE BSC6900/ ADD BTS GBFD-113725 BSC Node Meaning:Host

BSC6910 MOD BTS Redundancy type of an IP
BTS.
GUI Value
Range:SINGLE
HOST(Single
Host),
PRIMHOST
(Primary Host),
SLAVEHOST
(Slave Host)
Unit:None
Actual Value
Range:SINGLE
HOST,
PRIMHOST,
SLAVEHOST
Default
Value:SINGLE
HOST(Single
Host)

PEERBTSID BSC6900/ SET BTSIP GBFD-118601 Abis over IP Meaning:Identi-

BSC6910 GBFD-113725 BSC Node fier of the peer
Redundancy BTS on the
homing BSC
side
GUI Value
Range:0~2047
Unit:None
Actual Value
Range:0~2047
Default
Value:None

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 52

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

PEERBSCIP BSC6900/ SET BTSIP GBFD-118601 Abis over IP Meaning:IP

BSC6910 GBFD-113725 BSC Node address of the
Redundancy peer BSC on the
homing BSC
side
GUI Value
Range:Valid IP
Address
Unit:None
Actual Value
Range:Valid IP
Address
Default Value:
255.255.255.25
5

PEERBSCID BSC6900/ SET BTSIP GBFD-118601 Abis over IP Meaning:ID of

BSC6910 the peer BSC on
the homing BSC
side
GUI Value
Range:0~65534
Unit:None
Actual Value
Range:0~65534
Default
Value:None

PEERBSCMA BSC6900/ SET BTSIP GBFD-118601 Abis over IP Meaning:Subnet

SK BSC6910 GBFD-113725 BSC Node mask of the port
Redundancy IP address at the
peer BSC.
GUI Value
Range:Valid IP
Address
Unit:None
Actual Value
Range:Valid IP
Address
Default Value:
255.255.255.25
5

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 53

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

BSCIP BSC6900/ SET BTSIP GBFD-118601 Abis over IP Meaning:When

BSC6910 "BTS MultiIP
Switch" is set to
NO, this
parameter
indicates the IP
address of the
interface board
on the BSC side.
When "BTS
MultiIP Switch"
is set to YES,
this parameter
indicates the IP
address of the
maintenance
plane on the
BSC side.
GUI Value
Range:Valid IP
Address
Unit:None
Actual Value
Range:Valid IP
Address
Default Value:
255.255.255.25
5

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 54

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

BEATSENDIN BSC6900/ SET GBFD-113725 BSC Node Meaning:Time

GDIS BSC6910 GBSCREDGR Redundancy interval for
P sending a
handshake
message
between BSCs.
The parameter
checks whether
the
communication
among BSCs in
a redundancy
group is normal.
GUI Value
Range:1~60
Unit:s
Actual Value
Range:1~60
Default Value:1

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 55

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

CNSTATEPO BSC6900/ SET GBFD-113725 BSC Node Meaning:Policy

LICYFORGR BSC6910 GREDGRPHO Redundancy of the BSC for
OUP STPOLICY judging whether
the interface
status of the core
network is
normal. If the
value is NONE,
the BSC does
not change the
service
management
right. If the
value is
AINTFBLOCK,
the BSC releases
the service
management
right when
detecting
disconnection at
the A interface.
GUI Value
Range:NONE
(None),
AINTFBLOCK
(AInterf Block)
Unit:None
Actual Value
Range:NONE,
AINTFBLOCK
Default
Value:NONE
(None)

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 56

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

CNFAULTDE BSC6900/ SET GBFD-113725 BSC Node Meaning:Time

LAY BSC6910 GREDGRPHO Redundancy delay in the
STPOLICY detection of core
network
interface failure.
Within the
preset value of
this parameter,
the BSC
continuously
detects core
network
interface
failures and then
releases the
management
right of service
objects.
GUI Value
Range:1~60
Unit:s
Actual Value
Range:1~60
Default Value:
30

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 57

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

SLVSERVAC BSC6900/ SET GBFD-113725 BSC Node Meaning:If no

TDELAY BSC6910 GREDGRPHO Redundancy handshake
STPOLICY message is
received from
the peer within
the delay, the
slave service at
the local BSC is
activated. A
slave service
object provides
services at the
peer BSC and its
configuration
data is backed up
at the local BSC.
A slave service
object provides
services at the
local BSC only
when the peer
BSC is faulty or
when all the
signaling links
on the A
interface of the
peer BSC are
faulty.
GUI Value
Range:1~600
Unit:s
Actual Value
Range:1~600
Default Value:
300

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 58

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

MSTSERVAC BSC6900/ SET GBFD-113725 BSC Node Meaning:If no

TDELAY BSC6910 GREDGRPHO Redundancy handshake
STPOLICY message is
received from
the peer within
the delay, the
master service at
the local BSC is
activated. A
master service
object provides
services at the
local BSC and
its configuration
data is backed up
at the peer BSC.
A master service
object provides
services at the
peer BSC only
when the local
BSC is faulty or
when all the
signaling links
on the A
interface of the
local BSC are
faulty.
GUI Value
Range:1~600
Unit:s
Actual Value
Range:1~600
Default Value:
45

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 59

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

REHOSTTYP BSC6900/ SET GBFD-113725 BSC Node Meaning:Servic

E BSC6910 GREDGRPHO Redundancy e re-host policy.
STPOLICY If the local BSC
in a BSC node
redundancy
group is faulty,
the peer BSC
takes over the
primary-hosted
service objects
on the local
BSC. If the local
BSC recovers, it
reclaims these
service objects
from the peer
BSC according
to a certain
policy if related
requirements are
met.
GUI Value
Range:REHOS-
TRIGHTNOW
(ReHostRightN
ow),
REHOSTDELA
Y
(ReHostDelay),
REHOSTWHE
N
(ReHostWhen)
Unit:None
Actual Value
Range:REHOS-
TRIGHTNOW,
REHOSTDELA
Y,
REHOSTWHE
N
Default
Value:REHOST
DELAY
(ReHostDelay)

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 60

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

REHOSTDEL BSC6900/ SET GBFD-113725 BSC Node Meaning:Delay

AYTIME BSC6910 GREDGRPHO Redundancy of service re-
STPOLICY host. If
"REHOSTTYP
E" is set to
"ReHostDelay"
and the local
BSC recovers, it
reclaims service
objects after a
delay specified
by this
parameter.
GUI Value
Range:1~3600
Unit:s
Actual Value
Range:1~3600
Default Value:
600

REHOSTABS BSC6900/ SET GBFD-113725 BSC Node Meaning:Absol

TIME BSC6910 GREDGRPHO Redundancy ute service re-
STPOLICY host time. If
"REHOSTTYP
E" is set to
"ReHostWhen"
and the local
BSC recovers, it
reclaims service
objects at the
time specified
by this
parameter.
GUI Value
Range:hour,
min, sec
Unit:None
Actual Value
Range:
00:00:00~23:59
:59
Default
Value:None

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 61

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 7 Parameters

Parameter ID NE MML Feature ID Feature Name Description

Command

GROUPNAM BSC6900/ SET GBFD-113725 BSC Node Meaning:Name

E BSC6910 GBSCREDGR Redundancy of a BSC node
P redundancy
group. Group
names cannot
contain the
following
invalid
characters: , ; = "
' In addition,
group names
cannot contain
two or more
consecutive %,
two or more
consecutive
spaces, or more
than two
consecutive +.
GUI Value
Range:1~20
characters
Unit:None
Actual Value
Range:1~20
characters
Default
Value:None

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 62

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 8 Counters

8 Counters

There are no specific counters associated with this feature.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 63

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 9 Glossary

9 Glossary

For the acronyms, abbreviations, terms, and definitions, see the Glossary.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 64

Copyright © Huawei Technologies Co., Ltd.
GSM BSS
BSC Node Redundancy Feature Parameter Description 10 Reference Documents

10 Reference Documents

There are no specific reference documents associated with this feature.

Issue 01 (2013-05-06) Huawei Proprietary and Confidential 65

Copyright © Huawei Technologies Co., Ltd.