¡ IMS 8.2¡¿UGC3200 Dual-Homing

Dual-Homing
www.huawei.com
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

Foreword
 An inappropriate operation, a device fault, or a natural disaster may
lead to a large-scale service interruption.
 To ensure the security and reliability of a network, Huawei provides the
dual-homing (DH) solution that enables remote disaster recovery and
backup. That is, a backup UGC3200 is configured for the UGC3200
running on the network. Normally, the active UGC3200 processes the
signaling and services. When the active UGC3200 fails, the backup
UGC3200 takes over all the services of the active UGC3200 to ensure
the normal operation of the mobile network.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page2
Learning Instructions
 Upon completion of this course, you will be able to
understand that the UGC3200 functions as:
 A media gateway control function (MGCF) on the IMS network.
 A convergent gateway office.
 An IM-SSF on the IMS network.
Training Objectives
 Upon completion of this course, you will be able to

understand:
 DH networking scheme
 DH implementation principle
 DH data planning
 DH data configuration
Contents
1. Networking
2. Implementation Principle
3. 1+1 Assistant Networking
4. 1+1 Backup Networking
Networking
 The UGC3200 supports the following DH networking

schemes:
 1+1 backup:
In this scheme, two UGC3200s work in active/standby mode.

 1+1 assistance:
In this scheme, two UGC3200s work in assistant mode.
1+1 Assistance
In normal cases, UGC3200 A controls services of area A, and UGC3200 B controls services
of area B.
When UGC3200 A becomes faulty, UGC3200 B will take over the services of area A. When
UGC3200 B is faulty, UGC3200 A will take over the services of area B.
1+1 Backup
In normal cases, UGC3200 A acts as the active server and UGC3200 acts as the backup
server. UGC3200 A controls services of area A and area B, and UGC3200 does not control
any services.
When UGC3200 A becomes faulty, UGC3200 B will take over the services of area A and
area B.
Contents
1. Networking
Logical Structure
1+1 backup 1+1 assistance
DH Switchover Modes
 Automatic switchover
If heartbeat signal loss, power failure, or other factors cause the failure of an active server, the
standby server will be activated. All the MGWs controlled by the active server then register with the
standby server automatically.
 Manual switchover
When an active server needs to be moved or upgraded, you can switch its services to the standby
server by running relevant MML commands on the active server.
 Automatic switchback
If the active server recovers after its services are switched to the standby server, you can switch all
the services back to the active server by running relevant MML commands on the standby server.
 Manual switchback
If the active server and the heartbeat link recover after the services of the active server are
switched to the standby server, the services will be switched back to the active server
automatically.
DH Switchover Process of Media Gateway
6: UGC3200 B accepts the
3: The DH heartbeat is interrupted. registration request from the
2: UGC3200 A
UGC3200 B is activated and accepts a UMG8900, and the service
becomes faulty. registration request from the resumes.
UMG8900.
UGC3200-A UGC3200-B
Heart Beat Alarm

4: Connection between
the UMG8900 and iManager
UGC3200 A is interrupted.
N2000
1: The UMG8900 IP Core

registers with UGC3200
A.
UMG 8900 5: The UMG8900 registers

with UGC3200 B.
Trigger Condition for a DH Switchover
 A DH switchover is performed based on the status of the servers. The trigger conditions of
different DH switchovers are described as follows:
 Trigger condition for an automatic switchover
Heartbeat loss is the unique trigger condition for an automatic switchover. The heartbeat is lost in
any of the following cases:
 The UGC3200 breaks down due to power failure.
 The active and standby IFM modules are faulty.
 All network ports are faulty.
 Trigger condition for a manual switchover
Setting the DH status manually is the unique trigger condition for a manual switchover (by running
SET DHWM).
 Trigger condition for an automatic switchback
The recovery of the heartbeat is the unique trigger condition for an automatic switchback.
 Trigger condition for a manual switchback
Manual setting of the DH status is the unique trigger condition for a manual switchback by
(running SET DHWM).
Impact of a DH Switchover
 Impact on calls
During a DH switchover, all the calls being processed by the original active server will be interrupted.
 Impact on MGWs
When a DH switchover occurs, an MGW re-registers with another server. In this case, all resources are released,
and the calls that have been connected or are being connected by the MGW are disconnected.
 Impact on the trunk side
During a DH switchover or switchback, the server that takes over the services will initiate a reset request to the
trunk group. Subscribers (including the calling party and called party) engaged in the ongoing calls will be
disconnected on the base station side.
 Impact on Interception
The Call Content Trigger Function (CCTF) of the active server and that of the standby server are independent of
each other. After a DH switchover, the interception data cannot be backed up to the standby server. Therefore, the
standby server does not have interception data and cannot take over the interception service automatically. To
initiate interception after a DH switchover, you must manually re-establish communication between the CCTF of the
standby server and the LIG, re-register the LIG, and configure the related data. The interception data configured by
the LIG in a server is valid for all the virtual nodes of the server. In addition, voice routes must be set up between
the LIG and the virtual nodes for interception output.
Impact of a DH Switchover – Charging
 Impact on charging
CDRs of the calls that are originated after a switchover are generated on the iGWB of the standby
server. The billing center obtains CDR files from the corresponding directory of this iGWB.
Impact of a DH Switchover – Charging
 Before a DH switchover, all the CDRs sent from the UGC3200 to the iGWBs are saved in the hard
disks of the active and standby iGWBs. These CDRs will not be lost, and the billing center can
obtain the CDR files in the corresponding directory of the iGWBs.
 During the DH switchover, the impacts on the charging of the active calls processed by the
UGC3200 are as follows:
 If the UGC3200 is powered on and is communicating with the iGWBs normally, the UGC3200 generates and
sends the CDRs to the iGWBs.
 If the UGC3200 is powered on but cannot communicate with the iGWBs, the UGC3200 generates and saves
the CDRs in its buffer. After the communication with the iGWBs is restored, the UGC3200 sends the CDRs to
the iGWBs.
 If the UGC3200 is powered off, the CDRs are lost. There is no direct relationship between CDR loss and CDR
type.
 You are advised to configure an independent address on the billing center for each of the active
and standby iGWBs of the active and standby servers. In this way, the billing center obtains CDRs
from the iGWB that has the CDR data without considering whether a DH switchover has occurred.
 After a DH switchover, the iGWB does not sense the DH switchover, and it generates CDRs and
directories according to the same rule.
Contents
1. Networking

3.1 Introduction to Networking
3.2 Data Planning
3.3 Data Configuration
1+1 Assistant Networking
 The following shows the virtual server networking of the 1+1 assistant scheme:
In the two assistant offices, virtual node 0 is the local node and virtual node 1 is
the assistant node. When configuring non-local virtual node 1 in the two offices,
set non-local virtual node 1 as the assistant node of the local node.
node
Mc Interface Networking (1+1 Assistant)
 In normal cases, UGC3200 A controls services of area A; that is, MGW 1 and MGW 2 initiate
registration requests only to UGC3200 A. UGC3200 B controls services of area B, that is,
MGW 3 and MGW 4 initiate registration requests only to UGC3200 B.
 When UGC3200 A becomes faulty or suffers disasters, UGC3200 B will take over the services
of area A, that is, MGW 1 and MGW 2 will initiate registration requests to UGC3200 B.
Before switchover After switchover
SIGTRAN Signaling Networking
(1+1 Assistant)
 In normal cases, the SIGTRAN signaling is transferred from the signaling gateways (namely, the MGWs
shown in the figure) to the active UGC3200 over the SIGTRAN links with a higher priority.
 When UGC3200 A becomes faulty, the links between MGWs 1 and 2 and UGC3200 A are interrupted.
Therefore, the SIGTRAN signaling sent from MGWs 1 and 2 to UGC3200 A is transmitted to UGC3200 B over
the SIGTRAN links connected to UGC3200 B.
Trunk Networking (1+1 Assistant)
 Regardless of whether a DH switchover is performed, trunk voice channels between two assistant UGC3200s still
serve as the bearers between two MGWs, and calls are still inter-office calls. After a DH switchover, the only difference
is that the signaling between the assistant UGC3200s automatically implements an MTP3 layer-based loop internally.
Contents
1. Networking

3.2 Data Planning
Capacity Planning (1+1 Assistant)
The DH function, often used together with a large-capacity system, enhances
network security, allows flexible networking, and saves costs. The planned capacity,
however, cannot exceed the total capacity of a system.
 Trunk capacity planning
 In the 1+1 assistant DH network, configure the trunk capacity for an office based on the
sum of the trunk capacities of two offices. Configure the trunk circuit data on the CCU
modules evenly. Special data planning is not required.
 Link capacity planning

 For the M3UA link-based signaling networking, the number of BSGs to be configured on a
server is determined by the total number of M3UA links configured on the two active
servers.
 For the M2UA-based SS7 links, the number of BSGs to be configured on a server is
determined by the total number of SS7 links configured on the two active servers.
Planning Methods – Method One
 Plan data based on independent segments. That is, plan data for two assistant servers in a uniform manner and
ensure that the data segments of the two servers are independent. Assign an independent segment range for each
active server, and reserve resources for future capacity expansion.
 Data feature: On the backup server, the combination of a type of data of all active servers does not exceed the maximum number
of tuples defined in the data table.
 Key data: destination code.
The procedure of data planning is as follows:

1. Plan the data segment range (A and B) for two
active servers.
2. Configure data for each active server within its own

data segment range.
3. Copy the data of each active server to its peer

office as the backup data.
Planning Methods – Method Two
 Plan data based on the combination of a public data segment and independent data segments. That is,
reserve a public data segment for all servers to use together, and then allocate a data segment for each
active server to use independently.
 Data feature: The global table is involved. Certain data in the global table may be shared by multiple offices. For
example, all the offices that have the office direction destined for the province-level tandem office can share the same
index.
 Key data: DN set data and called number analysis data.
The procedure of data planning is as follows:

1. Plan a public data segment range A and two
independent data segment ranges B and C for two
active servers.
2. Configure data for each active server within the

public data segment range and its own data
segment range.
Planning Methods – Method Three
 Plan data based on names. Set the same name for the same data configured on the active server and the
backup server, and ensure that the names of the data of the same type are unique on the physical server.
 Data feature: The data configured on the active server is the same as that configured on the backup server except that the
data on the two servers belongs to different virtual nodes. When configuring such data, you do not need to specify indexes
but set names.
 Key data: SRVNODE, DHM3UACFG, DHHCFG, MGW, ESG, M3LE, M3DE, N7DSP, SCCPDSP, SCCPSSN, MASI,
SCCPGT, trunk group, link, link set, signaling route, route, sub-route, route analysis, and call source data.
 When configuring data that is planned based on names, you must comply with the naming specifications.
Contents
1. Networking

3.2 Data Planning
Configuration Principles (1+1
Assistant)
 The key point of DH data configuration is to ensure data consistency between
the active and standby UGC3200s.
 The data on the active UGC3200, such as gateway registration information,
signaling interworking information, trunk interworking information, route selection
scheme, dialing scheme, and service configuration scheme, must be consistent
with that on the standby UGC3200.
Configuring the Specialized DH
Data
 Automatic switchover and manual switchback are recommended for the DH network.
Automatic switchover means that the system automatically switches over the services of the
active server to the standby server when the active server is down. This meets the
requirements of carriers. If a switchback is automatically performed after the faulty server
recovers, call loss occurs. Therefore, you are advised to perform a manual switchback during
the light traffic hour. To configure a manual switchback, perform the following steps:
 On the active server, run SET DHWM to set Work mode of server 0 to Assistant, Switch
mode to Automatic, and Takeover mode to Non-Auto Takeover and Non-Auto
Backward.
SET DHWM: WM=ASSIST, SN="0", SM=AUTO, TM=NON-TK-SW;

 On the standby server, run SET DHWM to set Work mode to Assistant, Switch mode to
Automatic, and Takeover mode to Auto takeover.
SET DHWM: WM=ASSIST, SN="1", SM=AUTO, TM=AUTO-TK;
Configuring the DH Heartbeat Link
 DH heartbeat link
 The DH heartbeat signals are transmitted on UDP. You can run ADD DHHCFG to add a DH heartbeat
link between the local server node and the assistant server node.
 To ensure the transmission reliability of heartbeat signals, you need to configure two heartbeat links
between the two UGC3200s when the system is configured with two or more pairs of WIFMs.
 Standby DH heartbeat link
To ensure the reliability of DH switchover and switchback and prevent dual activation of the active and
standby servers, you can run ADD DHM3UACFG to add a standby heartbeat signal link running over M3UA.
The rules for configuring the standby heartbeat link are as follows:
 Before configuring the M3UA heartbeat link, configure the M3UA local entity, destination entity, link set,
link, and route.
 Before configuring the M3UA heartbeat link, ensure that the corresponding UDP heartbeat link has been
configured correctly; otherwise, you cannot configure the M3UA heartbeat link.
 The M3UA heartbeat link is only a standby heartbeat link for the UDP heartbeat link.
 Configure only one M3UA heartbeat link between the local UGC3200 and its assistant server.
Configuring Mc Interface Data
 The data for the UGC3200 to interwork with MGWs includes the MGW
data (configured by running ADD MGW and ADD H248LNK).
 Each MGW is associated with a virtual server node.
Configuring Signaling Data – MTP
 MTP signaling data
The server node to which the MTP DPC and associated MTP data (such as MTP link set,
MTP route, and MTP link) belong is determined by the server node to which the local SP
belongs.
To configure the M2UA-based MTP3 data, perform the following steps:

 Configure the active N7DSP, N7LKS, N7RT, and N7LNK for the local server node on the
UGC3200.
 Configure the standby N7DSP, N7LKS, N7RT, and N7LNK for other nodes on the
UGC3200.
 Ensure that the service load from one MGW is evenly distributed among all the BMGW
modules of the UGC3200.
Configuring Signaling Data – M2UA/IUA
 M2UA/IUA signaling data
The virtual server node to which the M2UA or IUA links and link sets belong is determined by the
virtual server node to which the EMGW belongs. The virtual server node to which the EMGW
belongs is determined by the virtual server node to which the MGW belongs. If the EMGW belongs
to virtual server node 0, then the M2UA or IUA links and link sets are managed by virtual server
node 0.
To configure the M2UA/IUA signaling data, perform the following steps:

 Configure the active EMGW (by running ADD EMGW), M2UA link sets (by running ADD
M2LKS), and M2UA links (by running ADD M2LNK) for virtual server node 0 on the UGC3200.
 Configure the standby EMGW, M2UA link set, and M2UA links for other virtual server nodes on
the UGC3200.
 Configure one M2UA link set on the embedded MGW. The link set contains two links, one
connected to an active server node and the other connected to the standby server node.
Configuring Signaling Data – M3UA
 M3UA signaling data
The server node to which the M3UA local entity and associated M3UA data (such as M3UA destination entity, M3UA
link set, M3UA route, and M3UA link) belong is determined by the server node to which the local SP belongs. If the
M3UA local entity belongs to server 0, then the M3UA local entity and other associated data are managed by server 0.
To configure the M3UA signaling data, perform the following steps:

 Configure the active M3UA local entity, destination entity, link set, routes, and links for virtual server node 0 on the
UGC3200.
 Configure the standby M3UA local entities, destination entities, link sets, routes, and links for other virtual server
nodes on the UGC3200.
 Configure a link set on the embedded MGW to its corresponding SP. Then, configure a number of links within the
link set (the number of links must be the same as the number of SPF boards). The links connected to the two
UGC3200s must be configured with different priorities. The links connected to the active UGC3200 are configured
with a higher priority, and the links connected to the standby UGC3200 are configured with a lower priority.
 Ensure that the service load from one MGW is evenly distributed among all the BMGW modules of the UGC3200.
Configuring Trunk Office Direction
Data
 When adding a route or subroute for the DH system, you must specify the
virtual server node of the route or subroute. The configuration of the
ISUP, TUP, R2, PRA, and BICC office direction data, route analysis data,
trunk group data, and trunk circuit data is the same as that of common
data.
Contents
1. Networking

4.2 Data Planning
Introduction to Networking (1+1
Backup)
 The following shows the virtual server networking of the 1+1 backup scheme:
A virtual server node is configured on the active server to set up a heartbeat link
with the backup server. The standby server node is not configured with any
service data.
Mc Interface Networking (1+1 Backup)
 In normal cases, UGC3200 A controls services of area A, that is, MGW 1 and MGW 2 initiate
registration requests only to UGC3200 A. UGC3200 B does not control any services in normal
cases.
 When UGC3200 A becomes faulty or suffers disasters, UGC3200 B will take over the services
of area A, that is, MGW 1 and MGW 2 will initiate registration requests to UGC3200 B.
SIGTRAN Signaling Networking
(1+1 Backup)
 Before a switchover, the SIGTRAN signaling from the MGW to the UGC3200 is transmitted over the SIGTRAN
links with a higher priority destined for the active UGC3200, that is UGC3200 A.
 When UGC3200 A is faulty, the links between the MGWs 1 and 2 and UGC3200 A are interrupted. Therefore,
the SIGTRAN signaling sent from MGWs 1 and 2 to UGC3200 A is transmitted to UGC3200 B over the
SIGTRAN links connected to UGC3200 B.
Trunk Networking (1+1 Backup)
 Before a switchover in the trunk networking, the MGWs manage their own trunk circuits.
 When UGC3200 A becomes faulty, the trunk networking remains the same, that is, the trunk
circuits still belong to their original MGWs; however, the signaling routes are changed.
Contents
1. Networking

4.2 Data Planning
Capacity Planning (1+1 Backup)
In 1+1 backup mode, the host of the backup server stores the office data of the active
server. If a switchover occurs, the backup server activates the corresponding virtual
node and uses the data of that virtual node.
 Trunk capacity planning
 In the 1+1 backup DH network, configure the trunk capacity for the backup office based on
the trunk capacity of the active office.
 Configure the trunk circuit data on the CCU modules evenly. Special data planning is not
required.
 Link capacity planning

 For the M3UA link-based signaling networking, the number of BSGs to be configured on the
backup server is determined by the number of M3UA links configured on the active server.
 For the M2UA-based MTP links, the number of BSGs to be configured on the backup server
is determined by the number of MTP links configured on the active server.
Planning Method
 In a 1+1 backup network, the backup server is a complete backup of the active
server. No special data planning is required.
Contents
1. Networking

4.2 Data Planning
Configuration Principle (1+1 Backup)
 In a 1+1 backup network, the backup server is a complete backup of the
active server. Therefore, the data on the backup server, such as signaling
data, trunk data, and service data, is consistent with that on the active
server.
Configuring the DH Work Mode
 Automatic switchover and manual switchback are recommended for the DH
network.
Automatic switchover means that the system automatically switches over the services of
the active server to the standby server when the active server is down. This meets the
requirements of carriers. If a switchback is automatically performed after the faulty server
recovers, call loss occurs. Therefore, you are advised to perform a manual switchback
when the traffic is lightest. To configure a manual switchback, perform the following steps:
 On the active server, run SET DHWM to set Work mode of server 0 to Assistant,
Switch mode to Automatic, and Takeover mode to Non-Auto Takeover and Non-
Auto Backward.
SET DHWM: WM=ASSIST, SN="0", SM=AUTO, TM=NON-TK-SW;

 On the standby server, run SET DHWM to set Work mode to Assistant, Switch
mode to Automatic, and Takeover mode to Auto takeover.
SET DHWM: WM=ASSIST, SN="1", SM=AUTO, TM=AUTO-TK;
Configuring the DH Heartbeat Link
 DH heartbeat link
 The DH heartbeat signals are transmitted on UDP. You can run ADD DHHCFG to add a DH heartbeat
link between the local server node and the assistant server node.
 To ensure the transmission reliability of heartbeat signals, you need to configure two heartbeat links
between the two UGC3200s when the system is configured with two or more pairs of WIFMs.
 Standby DH heartbeat link
To ensure the reliability of DH switchover and switchback and prevent dual activation of the active and
standby servers, you can run ADD DHM3UACFG to add a standby heartbeat signal link running over M3UA.
The rules for configuring the standby heartbeat link are as follows:
 Before configuring the M3UA heartbeat link, configure the M3UA local entity, destination entity, link set,
link, and route.
 Before configuring the M3UA heartbeat link, ensure that the corresponding UDP heartbeat link has been
configured correctly; otherwise, you cannot configure the M3UA heartbeat link.
 The M3UA heartbeat link is only a standby heartbeat link for the UDP heartbeat link.
 Configure only one M3UA heartbeat link between the local UGC3200 and its assistant server.
Configuring Mc interface data
 The data for the UGC3200 to interwork with MGWs includes the MGW
data (configured by running ADD MGW), H.248 link data (configured by
running ADD H248LNK), media connections between MGWs (configured
by running ADD MGWCONN), and paths between MGWs (configured by
running ADD MGWPATH).
 Each MGW is associated with a virtual server node.
Configuring Signaling Data – MTP
 MTP signaling data
The server node to which the MTP DPC and associated MTP data (such as MTP link set, MTP
route, and MTP link) belong is determined by the server node to which the local SP belongs.
To configure the M2UA-based MTP3 data, perform the following steps:

 Configure the active N7DSP, N7LKS, N7RT, and N7LNK for the local server node on the
UGC3200.
 Configure the standby N7DSP, N7LKS, N7RT, and N7LNK for other nodes on the
UGC3200.
 Ensure that the service load from one MGW is evenly distributed among all the BMGW
modules of the UGC3200.
Configuring Signaling Data – M2UA/IUA
 M2UA/IUA signaling data
The virtual server node to which the M2UA or IUA links and link sets belong is determined by the
virtual server node to which the EMGW belongs, and the virtual server node to which the EMGW
belongs is determined by the virtual server node to which the MGW belongs. If the EMGW belongs
to virtual server node 0, then the M2UA or IUA links and link sets are managed by virtual server node
0.
To configure the M2UA/IUA signaling data, perform the following steps:

 Configure the active EMGW (by running ADD EMGW), M2UA link sets (by running ADD
M2LKS), and M2UA links (by running ADD M2LNK) for virtual server node 0 on the UGC3200.
 Configure the standby EMGW, M2UA link set, and M2UA links for other virtual server nodes on
the UGC3200.
 Configure one M2UA link set on the MGW (embedded with the EMGW). The link set contains
two links, one connected to an active server node and the other connected to the standby server
node.
Configuring Signaling Data – M3UA
 M3UA signaling data
The server node to which the M3UA local entity and associated M3UA data (such as M3UA destination entity,
M3UA link set, M3UA route, and M3UA link) belong is determined by the server node to which the local SP
belongs. If the M3UA local entity belongs to server 0, then the M3UA local entity and other associated data are
managed by server 0.
To configure the M3UA signaling data, perform the following steps:

 Configure the active M3UA local entity, destination entity, link set, routes, and links for virtual server node
0 on the UGC3200.
 Configure the standby M3UA local entities, destination entities, link sets, routes, and links for other virtual
server nodes on the UGC3200.
 Configure a link set on the MGW (embedded with the MGW) to its corresponding SP. Then, configure a
number of links within the link set (the number of links must be the same as the number of SPF boards).
The links connected to the two UGC3200s must be configured with different priorities. The links connected
to the active UGC3200 are configured with a higher priority, and the links connected to the standby
UGC3200 are configured with a lower priority.
 Ensure that the service load from one MGW is evenly distributed among all the BMGW modules of the
UGC3200.
Configuring Trunk Office Direction
Data
 When adding a route or subroute for the DH system, you must specify the
virtual server node of the route or subroute. The configuration of the
ISUP, TUP, R2, PRA, and BICC office direction data, route analysis data,
trunk group data, and trunk circuit data is the same as that of common
data.
FAQ: How Is the LSTP Connected
to the Server?
 Typically, carriers require that the LSTP be connected to the server directly through the
TDM signaling. The networking scheme with the route priority function is recommended.
 The routes from SPC C to SPC A are as follows:

 Route 1 goes through link set 1. The priority of this route is high.
high
 Route 2 goes through link set 2. The priority of this route is low.
 All links from SPC C to SPC A are in the path between the LSTP and server 1. A
maximum of 16 links can be configured. The advantages of this mode are as follows:
 The links of the LSTP are fully used. This is a big advantage for the 1+1 assistant mode or 1+1
backup mode when the TDM signaling is used.
 It avoids the situation that half of the links of the LSTP are faulty.
FAQ: How Are the HLR and SCP
Connected to the Server?
 If the HLR and SCP are not deployed together with the local MGW, it is recommended that
they be connected to the server directly through the TDM signaling, as in the LSTP
networking model.
 If the HLR and SCP are deployed together with the local MGW, they are connected to the
server through the link priority function of the M3UA proxy mode.
This networking model has the following

advantages:
 The HLR and the SCP can connect to remote
servers 1 and 2 through the neighboring MGW,
without the need to connect to remote servers 1
and 2 directly through TDM links.
 The TDM link resources of the HLR and SCP are
not wasted.
 There is no special requirement for the HLR and
SCP.
FAQ: What Is Dual Activation? Why Does It
Happen? What Impact Does It Have?
 Dual activation means that node 0 of the active server and the corresponding node of the standby
server are in active state. That is, the same logical virtual node is active on two servers.
 Dual activation may occur when either of the following conditions occurs: One is that dual activation
is configured manually; the other is that the status of both servers is normal but the heartbeat
signals are lost.
 In the case of dual activation, the signaling links of the active server are preferred and the services
are not affected if the MGWs controlled by the active server still register with the active server.
However, backup data is loaded and certain alarms are generated because the corresponding
node of the standby server becomes active. This does not affect the normal running of the system.
If the MGWs controlled by the active server register with the standby server, manual intervention is
required, for example, you must perform a manual switchover.
 If dual activation occurs, repair the heartbeat links immediately so that the active and standby
servers use heartbeat links to automatically check the status of virtual nodes. In normal cases,
virtual node 0 of the active server should be active, and the corresponding virtual node of the
standby server should be deactivated. Alternatively, set one virtual node to deactivated manually.

¡ IMS 8.2¡¿UGC3200 Dual-Homing

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

¡ IMS 8.2¡¿UGC3200 Dual-Homing

Uploaded by

Copyright:

Available Formats

Dual-Homing

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Upon completion of this course, you will be able to

3. 1+1 Assistant Networking

4. 1+1 Backup Networking

 The UGC3200 supports the following DH networking

In this scheme, two UGC3200s work in active/standby mode.

In this scheme, two UGC3200s work in assistant mode.

3. 1+1 Assistant Networking

4. 1+1 Backup Networking

1+1 backup 1+1 assistance

Heart Beat Alarm

1: The UMG8900 IP Core

UMG 8900 5: The UMG8900 registers

3. 1+1 Assistant Networking

3.2 Data Planning

3.3 Data Configuration

4. 1+1 Backup Networking

Before switchover After switchover

Before switchover After switchover

Before switchover After switchover

3. 1+1 Assistant Networking

3.2 Data Planning

3.3 Data Configuration

4. 1+1 Backup Networking

 Link capacity planning

The procedure of data planning is as follows:

2. Configure data for each active server within its own

3. Copy the data of each active server to its peer

The procedure of data planning is as follows:

2. Configure data for each active server within the

3. 1+1 Assistant Networking

3.2 Data Planning

3.3 Data Configuration

4. 1+1 Backup Networking

SET DHWM: WM=ASSIST, SN="0", SM=AUTO, TM=NON-TK-SW;

SET DHWM: WM=ASSIST, SN="1", SM=AUTO, TM=AUTO-TK;

 Standby DH heartbeat link

To configure the M2UA-based MTP3 data, perform the following steps:

To configure the M2UA/IUA signaling data, perform the following steps:

To configure the M3UA signaling data, perform the following steps:

3. 1+1 Assistant Networking

4. 1+1 Backup Networking

4.2 Data Planning

4.3 Data Configuration

Before switchover After switchover

Before switchover After switchover

Before switchover After switchover

3. 1+1 Assistant Networking

4. 1+1 Backup Networking

4.2 Data Planning

4.3 Data Configuration

 Link capacity planning

3. 1+1 Assistant Networking

4. 1+1 Backup Networking

4.2 Data Planning

4.3 Data Configuration

SET DHWM: WM=ASSIST, SN="0", SM=AUTO, TM=NON-TK-SW;

SET DHWM: WM=ASSIST, SN="1", SM=AUTO, TM=AUTO-TK;

 Standby DH heartbeat link

To configure the M2UA-based MTP3 data, perform the following steps:

To configure the M2UA/IUA signaling data, perform the following steps:

To configure the M3UA signaling data, perform the following steps: