Working Principles and O&M of The IGWB (ATCA)

Security Level:
Working Principles and O&M

of the iGWB (ATCA)
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD.
HUAWEI Confidential
Objectives
This tutorial will help you to understand:
What are the differences between the iGWB ATCA

and iGWB CPCI
What are the functions and working principles of

the iGWB
How to install and configure the iGWB
How to use the Web UI of the iGWB
How to locate the faults occurred on the iGWB
HUAWEI Confidential
References
HUAWEI iGWB Product Description
Software Installation in the HUAWEI iGWB User Manual
HUAWEI iGWB Configuration Guide
HUAWEI Confidential
Contents
Chapter 1 iGWB ATCA vs. iGWB CPCI
Chapter 2 Functions of the iGWB
Chapter 3 Working Principles of the iGWB
Chapter 4 Installation and Configuration of
the iGWB
Chapter 5 Maintenance of the iGWB
HUAWEI Confidential
Difference in Deployment
CPCI (server+disk array) ATCA (boards)
Boards of the iGWB ATCA are deployed in pairs in the subracks of the
MSOFTX3000 in a distributed manner. In the case of 10 million subscribers, the
iGWB uses four pairs of boards.
HUAWEI Confidential
Difference in the Software Structure

CPCI (two-node system) ATCA (distributed system)
The iGWB ATCA uses five processes whereas the iGWB CPCI uses seven processes.
Besides, by deploying the processes on the added boards, you can expand the
capacity of the iGWB ATCA.
RCM
Process
HUAWEI Confidential
Difference in System Configuration

CPCI (INI) ATCA (MML)
The iGWB CPCI requires an independent parameter configuration process to set

the parameters in the INI file. The data configuration of iGWB ATCA is managed
by the OMU and is implemented by using MML commands.
HUAWEI Confidential
Difference in the Implementation of Querying and

Browsing CDRs
CPCI (C/S architecture) ATCA (B/S architecture)
In the iGWB CPCI, the iGWB Client software CDR Console needs to be installed
independently. In the iGWB ATCA, it is not required any more because users can
view CDR information by using the browser of Windows.
HUAWEI Confidential
Other Major Differences

Item
CPCI
ATCA
OS
Based on Windows 2000 Server
Based on SUSE Linux
Change of the
interface
between the
iGWB and
MSOFTX3000
Communications protocol:
Communications protocol: based

on the UDP/IP Sliding Window
Protocol
CDR format: ASN.1 format
The ACP protocol is added. It is
based on the UDP/IP protocols and
used for the communication
negotiation between the CCU and AP.
Change of the
interface
between the
iGWB and BC
Supports FTP in PULL and PUSH

modes;
Supports FTAM in PULL mode.
Supports FTP and SFTP in PULL and

PUSH modes;
Does not support FTAM any more.
CDR
synchronization
between the two
nodes
CDR data is synchronized from the

primary node to the secondary node
through scheduled backup. As a
result, the backup data is of low
reliability.

primary node to the secondary node
by using the DRBD technology, which
ensures the reliability of the backup
data.
CDR processing
technology
Customization flexibility is low

because it is achieved by using the
format database, which cannot solve
the problem of hard code.
Customization flexibility is high for the

format engine technology is adopted,
which avoids the problem of hard
code.
based on the TCP/IP Sliding

Window Protocol
CDR format: binary format
HUAWEI Confidential
Review Question
What are the major differences between iGWB
ATCA and iGWB CPCI?
You can answer this question from the following the aspects:
deployment, software structure, system configuration, CDR
Client software, OS, interface between the iGWB and
MSOFTX3000, interface between the iGWB and the BC,
CDR synchronization between the two nodes, and CDR
processing technology.
HUAWEI Confidential
Contents
the iGWB
HUAWEI Confidential
Position of the iGWB on the Network

The iGWB is a gateway between the MSOFTX3000 and the BC. It is responsible
for receiving, preprocessing, and buffering the CDRs from the MSOFTX3000 and
providing CDRs to the BC as a charging interface. The iGWB is installed with the
OMU and MSOFTX3000 in a same cabinet and its operation and maintenance are
managed by the OMU.
HUAWEI Confidential
Functions of the iGWB

The iGWB performs the following functions:
Collecting the CDRs generated by the MSOFTX3000 in real time and ensuring that no
CDR is lost or duplicated during transmission.

The iGWB and MSOFTX3000 are connected over a UDP/IP network with customized Sliding
Window Protocol at the application layer. The Sliding Window Protocol prevents CDR loss or
duplication.
Sorting CDRs and converting their format according to the requirements of the carrier
CDR sorting: To sort CDRs means to classify and then store the CDRs generated by the switch
according to certain conditions. For example, the MSOFTX3000 generates common CDRs (that is,
GSM CDRs) and other types of CDRs, and the iGWB can store different types of CDRs separately.
CDR format converting: CDR files can be stored in multiple formats, including binary, text, and
ASN.1. The CDRs sent from the MSOFTX3000 to the iGWB are in ASN.1 format, which needs to
be changed to meet the format requirements of the BC. To answer this need, CDR format
converting is implemented.
HUAWEI Confidential
Functions of the iGWB (Continued)

Customizing the filename format, file size, and generation interval of CDR files
Specifying the filename format, setting the file size, and customizing the generation interval of CDR
files are three basic functions of the iGWB as the charging interface. The filename format, file size, and
generation interval of CDR files can all be configured and the configurations can take effect instantly.
Providing the access of the CDR files to the BC to implement online charging
To implement online charging, CDR files need to be transferred from the iGWB to the BC in certain
transmission mode through certain file transfer protocol.
The file transfer protocols used are the FTP and SFTP protocols. FTAM is not supported by the iGWB
ATCA.
PULL and PUSH are the two transmission modes. In PULL mode, the BC logs in to the iGWB to fetch
the CDR files. In PUSH mode, the iGWB uploads the CDR files to the specified directory on the
specified device of the BC. Both the PULL and PUSH modes are supported either when the FTP
protocol or when the SFTP protocol is used. Each pair of boards provides an independent network
interface for the BC.
HUAWEI Confidential
Review Questions
What are the functions of the iGWB?
What protocols are used for transferring CDR files from the iGWB
ACTA to the BC? Is there any difference between the protocols

used by the iGWB CPCI and those used by the iGWB ACTA?
HUAWEI Confidential
Contents
the iGWB
HUAWEI Confidential
Contents
3.1 Hardware Working Principles of the iGWB
3.2 Software Working Principles of the iGWB
HUAWEI Confidential
Hardware Configuration
The iGWB are installed in the integrated
configuration cabinet and the service

processing cabinet of the MSOFTX3000 in
a distributed manner. That is, the four pairs
of boards are installed in the three subracks
of the two cabinets. Besides, the two-node
architecture is used for each pair of boards.
The iGWB uses the following types of
boards:
UPBA1<->USIA1: two CPUs + 8 GB memory

+ 2 x 146 GB hard disks + 2 x 2 GE
interfaces
UPB3<->USIA1: two CPUs + 4 GB memory

+ 2 x 146 GB hard disks + 2 x 2 GE
interfaces
?<->USIA1: two CPUs + 4 GB memory + 2 x

300 GB hard disks + 2 x 2 GE interfaces
(The type of the UPB in this pair is not

determined yet. This information will be
provided after the GA.)
HUAWEI Confidential
Principles for Connecting the Hardware

Subracks are cascaded through the GE
interfaces on the SWI boards. For

details, see the MSOFTX3000 System
Principle.
The operation and maintenance of the
iGWB are implemented through the

OMC interface on the RTM of the OMU.
Each pair of boards provides an
independent charging interface.

Through the internal Base bus, the
OMU delivers the configuration and

command data to the iGWB.
Through the internal Base bus, the
MSOFTX3000 delivers CDRs to the

iGWB and the iGWB sends alarms to
the MSOFTX3000.
primary boards of the iGWB to the

secondary ones through the internal
Fabric bus.
HUAWEI Confidential
Cable Connections from the Interfaces on the RTMs of

the OMUs to Other Devices
OMC interface
NTP interface
Monitoring
interface
Typically, the OMUs are installed in slots 4 and 5 of subrack 0. The corresponding RTMs are the USIA7s. Each
USIA7 has six 100/1000M auto-negotiation Ethernet interfaces.

The USIA7 provides three logical interfaces, which are defined as the OMC interface, NTP interface, and
monitoring interface. The diagram above shows the designations of the interfaces and the connections from the
interfaces to other devices.
Note that the devices should be connected based on the data configured in the iGWB MML command window.
HUAWEI Confidential
Cable Connections from the Interfaces on the RTMs of the

iGWB to Other Devices
CDR distribution
interface
CDR backup
interface
Principles for configuring the boards: Typically, the pairs of boards are installed in slots 8 and 9, slots 4 and 5, and/or slots 10 and 11. The slots
are chosen in the following order (from high priority to low priority):
slots 8 and 9 slots 4 and 5 slots 10 and 11 (The slots in subrack 0 are to be chosen first.)
The corresponding RTMs of each pair of boards are two USIA1s in pair. A USIAI has four 100/1000M auto-negotiation Ethernet interfaces.
Each pair of boards provides two logical interfaces for distributing and backing up CDR files respectively. The two logical interfaces correspond
to the Card3 and Card4 on the USIA1. Typically, each pair of boards uses one of the two network interfaces of Card3 to communicate with the
BC. The two red lines in the figure above demonstrate the primary and secondary links from the iGWB to the BC.
The network adapters for the CDR distribution interface and CDR backup interface can be configured in the iGWB MML command window. Note
that the devices should be connected based on the data configured in the iGWB MML command window.
HUAWEI Confidential
IP Address Planning of the Boards

You need to configure the external network interfaces of each pair of boards need based on the actual
environment; the system automatically generates the IP addresses of the internal network interfaces.
The formulas for generating the IP addresses of the network interfaces on the Base plane and the Fabric plane
on each pair of boards are as follows:

Base1: 172.16. (128 + FrameNo) . (8 x PrimarySlotNo + 5)
Base2: 172.17. (128 + FrameNo) . (8 x PrimarySlotNo + 5)
Fabric1: 172.18. (128 + FrameNo) . (8 x PrimarySlotNo + 5)
Fabric2: 172.19. (128 + FrameNo) . (8 x PrimarySlotNo + 5)
The following table takes the slot 8 and 9 in subrack 0 as an example to describe the IP address planning. (In
typical application scenarios, you need to plan for the IP address for the network interface listed in red only.)
Network Adapter ID
Purpose
IP Address
Card3/Lan0
An external network interface for the BC, serving as the CDR distribution
interface
The IP address of the primary link. You need to configure it based

on the actual condition.
Card3/Lan1
An external network interface for the BC, serving as the CDR distribution
interface
The IP address of the secondary link. You need to configure it

based on the actual condition.
Card4/Lan0
An external network interface for the third-party server, serving as the CDR
backup interface
The IP address of the primary link. You need to configure it based

on the actual condition.
Card4/Lan1
An external network interface for the third-party server, serving as the CDR
backup interface
The IP address of the secondary link. You need to configure it

based on the actual condition.
Base1
An internal network interface for the communication between the

MSOFTX3000 and the primary plane of the OMU
Automatically generated IP address: 172.16.128.69
Base2
An internal network interface for the communication between the

MSOFTX3000 and the secondary plane of the OMU
Fabirc1
An internal network interface for the CDR data synchronization between the
primary and secondary nodes and the primary heartbeat link
Fabric2
An internal network interface for the CDR data synchronization between the
primary and secondary nodes and the secondary heartbeat link
HUAWEI Confidential
Review Questions
Which cabinet of the MSOFTX3000 is the iGWB installed in?
What types of boards does the iGWB support?

Describe the communication network interfaces between the
iGWB, MSOFTX3000, OMU, BC, and third-party server. Tell

others through which network interface the operation and
maintenance of the iGWB is implemented.
Describe how to configure the IP addresses for a pair of boards.
HUAWEI Confidential
Contents
3.1 Hardware Working Principles of the iGWB
3.2 Software Working Principles of the iGWB
HUAWEI Confidential
Software Structure of the iGWB

The processes deployed on the iGWB server include the ACM, AP, RCM, CDM, CBK,
CQB, and QBM process, among which the ACM process and QBM process are global
processes that need to be deployed on one pair of boards only. Therefore, you need to
deploy the rest five processes on each pair of boards, and the ACM process and QBM
process on the first pair of boards.
The processes on both the primary boards and the secondary boards are running. The
difference is that the processes on the primary boards are in the Active state whereas
those on the secondary boards are in the Standby state.
HUAWEI Confidential
Functions of the iGWB Processes

ID
Name
Function
ACM
Access Control Module
It is globally unique. It negotiates with MSOFTX3000 by using the ACP protocol and
then allocates the CDRs generated by the MSOFTX3000 to the boards of the iGWB
to balance the data load among the boards and to increase the reliability.
AP
Access Point
It is deployed on each pair of boards. It performs the core service of the iGWB, that
is, processing the CDRs, which includes receiving, sorting, converting, and storing
the CDRs.
RCM
Resource Control Management
It is deployed on each pair of boards. It controls and manages various software and
hardware resources, including the virtual IP resources, available disk space, and
access point process. It performs failover if a resource fault cannot be rectified.
CDM
CDR Distribution Management
It is deployed on each pair of boards. It sends the final CDR files to the BC through
FTP or SFTP in PUSH or PULL mode. Typically, it sends the final CDR files through
FTP in PULL mode.
CBK
CDR Backup
It is deployed on each pair of boards. It backs up the original CDR files through FTP
or SFTP to the third-party server to strengthen the security of the CDR data.
CQB
CDR Query & Browse
It is deployed on each pair of boards. It performs the CDR querying and browsing
function after receiving the CDR querying and browsing commands delivered by the
QBM process, and reports the results to the QBM process.
QBM
CDR Query & Browse

Management
It is globally unique. It delivers CDR querying and browsing commands after

receiving the CDR querying and browsing requirements from the Client, receives
and merges the querying and browsing results, and then sends the results to the
Client.
HUAWEI Confidential
Basic Principles of the iGWB Access Control Process

Before sending the CDRs to the iGWB, a CCU sends an application to the ACM first.
After the ACM specifies the AP, the CCU starts to send CDRs to the specified AP. If an
exception occurs on this AP, the CCU applies for another AP from the ACM.
The data collecting and connection control are implemented through two separate
links. The ACM assigns APs to receive and process the CDRs from the CCUs
according to the number of CCUs each AP takes and its CDR processing
performance. In this way, the load is balanced among the APs and system usability is
improved.
The ACM provides the MSX a unique interface.
HUAWEI Confidential
Basic Process of CDR Processing

The AP process performs the major functions of the iGWB and it is divided
into the following three modules:

CDR collecting module: It receives and saves the original CDRs, and it uses the
Sliding Window Protocol to ensure that no CDR is lost or duplicated during
transmission.
CDR processing module: It sorts CDRs, converts the format of CDRs, generates
final CDRs, and sends them to the final CDR storing module.
Final CDR storing module: It saves CDRs in different channels as files and
provide them to the BC.
HUAWEI Confidential
iGWB Format Engine Technology

By using the format engine technology, the iGWB can automatically generate a CDR
encoding/decoding library according to the description of the CDR format.

Scripts are used to describe the principles for sorting, converting, and merging
CDRs. The iGWB provides the environment for running the scripts.
HUAWEI Confidential
Principle for Synchronizing the CDRs from the

Primary Node to the Secondary Node
The iGWB uses the Distributed
Replicated Block Device (DRBD)

technology to implement real-time CDR
synchronization between the primary
and secondary nodes.
By using the DRBD technology, the
entire hard disk device is mirrored over

the TCP/IP network, thus achieving
network-level RAID 1 fault tolerance.
The figure on the right shows the data
synchronization process by using the

DRBD technology. After data is written
to hard disks, the upper layer receives
the information that the writing
operation is successful.
HUAWEI Confidential
Resource Management of the Two-Node iGWB

The RCM process manages the
resources of the iGWB, such as the

network interfaces, IP resources, and
applications.
All the processes deployed on a board
are in the same state: Active or Standby.

At the beginning, processes on both the
primary boards and the secondary boards
are started. Then, the RMU process
determines the states of the boards. The
RCM process on a board that is specified
as the active board activates the
resources bottom up, that is, activates the
network adapters first, then the IP
resources, and the applications at last.
The RCM process on a standby board
activates the network adapters and some
IP resources only. The figure on the right
shows the state of each resource.
If a resource on an active board is faulty
and cannot be recovered, a failover is

triggered.
If both a resource on an active board and
its corresponding resource on the

standby board are faulty, the failover
cannot be performed.
HUAWEI Confidential
Basic Process of Querying and Browsing CDRs

The QBM process coordinates and manages the CQB process running on each
board and provides an external interface for querying and browsing CDRs.
The OMU server transparently transmits CDR querying and browsing commands.
HUAWEI Confidential
Principle for Managing the Configuration

The data configuration of the iGWB is managed by the OMU through MML
commands.
The LMT Client manages the configuration parameters in the object-based
approach. That is, the parameters are first stored in the Oracle database on the
OMU server. Then, the OMU informs the iGWB the processes that need to be
activated on different pairs of boards.
HUAWEI Confidential
Directory Structure of the Software on the iGWB Server

Directory
Description
/opt/ne/0032/proc/workspace0/prog
Stores the files of the seven processes and the trace files.
/opt/ne/0032/proc/workspace0/prog/trace
Stores important tracing information about the running of the iGWB in the trace
files.
/opt/ne/0032/proc/workspace0/prog/error_report
Stores important error information about the running of the iGWB.
/opt/ne/0032/proc/workspace0/other
Stores the dynamic library file and configuration files of the iGWB.
/opt/ne/0032/proc/workspace0/other/download
Stores the format engine package downloaded from the OMU server
/opt/ne/0032/proc/workspace0/other/fem
Stores the currently-used format engine-related files, including the CDR format
description files, encoding/decoding libraries, and scripts about CDR processing
principles.
/opt/ne/0032/proc/workspace0/other/fem/desc
Stores the format description files of original CDRs and final CDRs.
/opt/ne/0032/proc/workspace0/other/fem/coder
Stores the encoding/decoding libraries of the currently-used original CDRs and

final CDRs.
/opt/ne/0032/proc/workspace0/other/fem/script
Stores the scripts defining the currently-used principles for sorting, merging, and
converting CDRs.
/var/igwb/StatusFile
Stores the status information about the running of the iGWB.
Note: workspace0 in the directories indicates that the system is running in workspace 1. When the
system is upgraded, the workspace is switched. Therefore, you need to change the directories based
on the actual workspace. You can view the information about the actual workspace by running the LST
WIKSP command in the CGP MML command window.
HUAWEI Confidential
Directory Structure of CDR Files

Directory
/var/igwb/frontsave
Description
The original CDR files are stored in /var/igwb/frontsave, classified into
its subdirectories based on the access points, and further classified
based on date in each directory.
The error CDR files are stored in /var/igwb/frontsave/error, classified
into its subdirectories based on the access points, and further classified
based on the causes of the errors in each subdirectory.
/var/igwb/backsave
The final CDR files are stored in /var/igwb/backsave in two copies.

The first copies of the final CDR files are stored in
/var/igwb/backsave/access point name/first/channel name/date. That is,
they are classified based on the access points, the channels, and then
date.
The second copies of the final CDR files are stored in
/var/igwb/backsave/access point name/first/channel name. This
directory structure is slightly different from the structure of the directory
for storing the first copies of the final CDR files. This directory is
accessible to the BC for it to fetch CDR files and the CDR files are
deleted from the iGWB in real time after being obtained by the BC.
Thus, this directory does not contain date folders in the channel folders.
HUAWEI Confidential
Directory Structure of the Original CDR Files
HUAWEI Confidential
Directory Structure of the Final CDR Files
The first copies of final CDR files are stored locally

for querying and browsing. They are deleted by the
iGWB.
The second copies of final CDR files are provided

for the BC. The BC deletes them from the iGWB
after fetching them. If the BC does not delete
them, the iGWB deletes them.
HUAWEI Confidential
Principle for Naming Original CDR Files

The BC cannot access original CDR files. The principle for naming each
original CDR file is as follows:

AP name + Original CDR serial number + Original CDR filename extension
AP name: It is the name of the access point of the CDR file. It cannot be changed.
Original CDR serial number: It is a 10-digit decimal number. This number ranges from
0000000001 to 4294967295 and is given to each CDR file in the chronological order that
the CDR file is generated by each access point.
Original CDR filename extension: The extension of the names of original CDR files is
.bil and it cannot be configured.
Take AP10000005378.bil as an example. This filename indicates that the file is

the No. 5378 original CDR file that is generated by AP1.
HUAWEI Confidential
Principle for Naming the First Copies of Final CDR Files

The BC cannot access the first copies of final CDR files, either. The principle for
naming the first copy of each CDR file is as follows:

gz + AP name + Length of the prefix of the second copies of final CDR files +
Length of the serial number of the second copies of final CDRs + Serial
number of the first copy of the final CDR file + Underscore + Filename of the
second copy of the final CDR file
gz: It is a compression identifier. If the first copy of a final CDR file is not compressed, its
name does not contain this identifier.
AP name: It is the name of the access point of the CDR file. It cannot be changed.
Length of the prefix of the second copies of final CDR files: It is a two-digit decimal
number. It indicates the length of the prefix of the second copies of final CDR files.
Length of the serial number of the second copies of final CDR files: It is a two-digit
decimal number. It indicates the length of the serial numbers of the second copies of
final CDR files.
Serial number of the first copy of the final CDR file: It is a 10-digit decimal number.
This number ranges from 0000000001 to 4294967295 and is given to each CDR file in
the chronological order that the CDR file is saved in each access point.
Take gzAP101080000002634_b00002627.dat as an example. This filename

indicates that the file is the first copy of the No. 2634 final CDR file that is
generated by AP1 and this file is compressed.
HUAWEI Confidential
Principle for Naming the Second Copies of Final CDR Files

The BC can access the second copies of final CDR files. The principle for
naming the second copy of each final CDR file is as follows:

Prefix of the second copies of final CDR files + Serial number of the second
copy of the final CDR file + Filename extension of the second copies of final
CDRs + .gz
Prefix of the second copies of final CDR files: It can be configured by running the
ADD CDRSTOR command. Generally, it is b.
Serial number of the second copy of the final CDR file: It can be configured by
running the ADD CDRSTOR command. This number is given in the chronological
order that the CDR is saved in each channel.
Filename extension of the second copy of final CDR files: It can be configured by
running the ADD CDRSTOR command. Generally, it is .dat.
.gz: It a compression identifier. Generally, the names of the second copies of final
CDR files do not contain this identifier for usually the second copies of final CDR files
are not compressed.
Take b00002627.dat as an example. This filename indicates that it is the

second copy of the No. 2627 final CDR file saved in a channel and this file
is not compressed.
HUAWEI Confidential
Review Questions
What are the processes deployed on the iGWB server? What is the function of
each process?
Where are the process files stored? Where are the currently-used format
engine-related files stored?

What resources are managed by each pair of boards? When will a failover be
triggered?
Where are original CDR files stored and what is their naming principle?
Where are the CDR files used by the maintenance personnel for querying and
browsing stored and what is their naming principle?

Where are the CDR files provided for the BC stored and what is their naming
principle?
HUAWEI Confidential
Contents
the iGWB
HUAWEI Confidential
Contents
Chapter 4 Installation and Configuration
of the iGWB
4.1 Installation of the iGWB
4.2 Configuration of the iGWB
4.3 Capacity Expansion of the iGWB
HUAWEI Confidential
Introduction to the Installation of the iGWB

Installation of iGWB Client:
LMT Client: It is connected to the OMU Server and is used for
managing the configuration and maintenance of the iGWB. You
need to install the CGP Client and then the iGWB Client before
installing the LMT Client.
Web-UI: Use the Windows Internet Explorer or install Firefox, and
then connect the browser to the OMU Server for querying and
browsing CDRs.
Installation of the iGWB Server

After you upload the software package of the iGWB Server to the
OMU Server, the iGWB downloads the software package from the
OMU board and runs it automatically. Therefore, you do not need to
install the software package manually.
HUAWEI Confidential
Process of Installing the iGWB

Step 1: Upload the following iGWB installation packages:
iGWB Server software package: IGWB_SRV_V500R005Cxx.tar
iGWB third-party software package: drbd0.7.24-1.tar and

vs.ftpd1.0.tar
iGWB ME file: iGWB format engine package, for example,

fem_asn1.tar.gz
Step 2: Install the iGWB Client.
It is recommended that you install the LMT Client through the JWS.
Step 3: Configure the iGWB installation data.
Add boards and iGWB MEs, deploy the module group, and install the
OS.
Step 4: Check the installation.
Clear the alarms about the iGWB and check the running status of
modules of the iGWB.
For details, see Software Installation in the HUAWEI iGWB User
Manual.
Note:
Currently, the pre-installation plan is being made. If the iGWB is pre-installed, you
do not need to install it on site. When you want to expand the capacity of the iGWB, you
can start the operation from adding boards.
HUAWEI Confidential
Description of the Installation of the iGWB

User Operation
Background Operations on the OMU Server
Background
Operations on the
Boards of the iGWB
Upload the
software package
of the iGWB
Server:
IGWB_SRV_V500
R005Cxx.tar.
1. Store the software package in /opt/pub/software/tmp.
None.
Upload the thirdparty software

package:
drbd0.7.24-1.tar,
vs.ftpd1.0.tar.
1. Store the software package in /opt/pub/software/tmp.
Upload the iGWB

ME file.
Store the uploaded format engine package in

/opt/HUAWEI/cgp/workshop/omu/share/nefile/iGWB-fmt.
None.
Run the ADD

RACK, ADD
SUBRACK, and
ADD BRD
commands to add
the racks,
subracks, and
boards.
Add the related racks, subracks, and boards to the OMU

management database. When adding boards, the application type of
the boards needs to be specified as IGWB because the OMU Server
installs different software on the boards of different application types.
None.
2. Decompress the software package to

/opt/HUAWEI/cgp/version/igwb.
3. Delete the software package from /opt/pub/software/tmp.
None.
2. Decompress the two software packages to /opt/pub/software/drbd

and /opt/pub/software/vs.ftpd respectively.
3. Delete the software packages from /opt/pub/software/tmp.
HUAWEI Confidential
Description of the Installation of the iGWB (Continued)

User
Operation
Run ADD ME
to add an
iGWB.
Background Operations on the OMU Server
1. Register the information about the added iGWB in

the OMU management database.
Background Operations
on the Boards of the
iGWB
None.
2. Create an iGWB database table and import the

iGWB stored procedures in the table.
3. Copy the program files of the iGWB to
\/opt/HUAWEI/cgp/workshop/nes/ne50/workspace1.
Run ADD MG
to add a
module group
Add the information about the added module group to

the TBL_MODULEDESC table of the iGWB.
None.
Run STR
INSTBRD.
Obtain the application type of each board according to

the corresponding rack and slot information entered. If
the application type of a board is IGWB, the iGWB is
notified to install the OS, the DRBD software, and the
FTP software on the board. After the installation is
complete, the iGWB restarts the board.
After the restart is

complete, the iGWB
automatically downloads
the iGWB program files
from the OMU server and
starts the modules of the
iGWB.
HUAWEI Confidential
Review Questions
What does the iGWB Client contain? How to install the iGWB
Client and iGWB Server?
HUAWEI Confidential
Contents
of the iGWB
HUAWEI Confidential
Introduction to the Configuration of the iGWB

The configuration of the iGWB is managed by the OMU through MML commands. The
parameters are stored in the Oracle database on the OMU board, and then the service
modules of the iGWB are notified that the parameters are stored in the Oracle database.
The iGWB manages the configuration parameters in the object-based approach. The objects
are designed according to service logic, so they are easy to remember.

Each object supports the addition, modification, deletion, and query of the configuration data.
Object
Oracle Database Table
Corresponding
iGWB Modules
Module group
TBL_MODULEDESC (ID: 4)
All the modules
Access control (optional)
TBL_ACTRL (ID: 6)
ACM
CDR receiving (optional)
TBL_CDRRECV (ID: 7)
AP
CDR processing
TBL_CDRPROC (ID: 8)
AP
CDR storing
TBL_CDRCDRSTOR (ID: 9)
AP
IP resource
TBL_IPRESOURCE (ID: 5)
CDM or CBK
CDR distribution
TBL_CDRDISTR (ID: 10)
CDM
CDR backing up
TBL_CDRBACKUP (ID: 11)
CBK
CDR patch
TBL_CDRPATCH (ID: 12)
AP
HUAWEI Confidential
Process of Configuring the Services of the iGWB

Step 1: Configure the processing of CDRs.
Configure the format engine package required by the iGWB to

process CDRs.
Step 2: Configure the storing of CDRs.
Configure the principles for storing original CDR files, the first
copies of final CDR files, and the second copies of final CDR
files.
Step 3: Configure the distribution of CDRs.
Configure the CDR distribution mode (PUSH or PULL).
Step 4: Configure the backing up of CDRs. (optional)
Configure the CDR backup policy (backing up original CDR files

or the first copies of final CDR files to the third-party server).
Note: The communication between the iGWB and MSOFTX3000 and

the two-node-related configurations are implemented by programs
automatically.
HUAWEI Confidential
iGWB Configuration Configuring the Processing of CDRs

The format engine package contains the core files for processing CDRs, including the
configuration file of the CDR processing flow, the scripts that define the principles for sorting,
merging, and converting CDRs, the encoding/decoding library of final CDRs. The user needs
to customize the format engine on site, for example, to modify the CDR filtering and sorting
conditions. The tool for customizing the format engine is being developed.
The configuration of CDR processing is global; therefore, you need to perform the
configuration once only. The configuration takes effect on the added boards automatically.
Modifications to this object do not take effect instantly. You need to run RST SERVICE for
the modifications to take effect.

For details, see the Configuration Guide or the MML Command Help.
HUAWEI Confidential
iGWB Configuration Configuring the Storing of CDRs

The iGWB stores original CDR files, the first copies of final CDR files, and the second
copies of final CDR files. You need to configure the principle for storing each type of
CDR files.
You need to configure the principle for storing original CDR files and the first copy of final
CDR files once only. You can configure different principles for storing the second copies
of CDR files in different channels as required.
The configuration of CDR storage principles is global; thus, the configuration takes effect
on the added boards automatically.

Any modification to this object takes effect instantly.
HUAWEI Confidential
iGWB Configuration Configuring the Distribution of CDRs

CDR files can be transferred from the iGWB to the BC through the FTP or SFTP protocol in PULL
or PUSH mode. In common scenarios, CDR files are transferred through the FTP protocol in
PUSH mode. Besides, the FTAM protocol is not supported any more. The iGWB can give the
access of the second copies of final CDR files to the BC directly. Therefore, the iGWB no longer
needs to back up final CDR files to another directory.
Each pair of boards provides an independent IP address for communicating with the BC.
Therefore, you need to configure the IP address, file transfer protocol, and the distribution mode for
each pair of boards.
The objects related to CDR distribution are IP resource and CDR distribution. The IP resource
object is used for configuring the IP address for communicating with the BC and modification to
this object do not take effect instantly. The CDR distribution object is used for configuring
parameters such as the file transfer protocol and distribution mode used for distributing CDR files
and modifications to this object take effect instantly.
HUAWEI Confidential
iGWB Configuration Configuring the Backing Up of

CDRs (Optional)
The iGWB supports to back up original CDR files and the first copies of final CDR files to
the third-party server through the FTP or SFTP protocol in PUSH mode.
If CDR files need to be backed up, each pair of boards provides an independent IP
address for communicating with the third-party server.

The objects related to CDR backing up are IP resource and CDR backing up. The IP
resource object is used to configure the IP address for communicating with the third-party
server and modifications to this object do not take effect instantly. The CDR backing up
object is used for configuring parameters such as the file transfer protocol and distribution mode
used for backing up CDR files and modifications to this object take effect instantly.
HUAWEI Confidential
Contents
of the iGWB
HUAWEI Confidential
Process of Expanding the Capacity of the iGWB

Step 1: Add a pair of boards.
Run ADD BRD in the CGP MML command window.

Step 2: Deploy the module group on the added boards.
Run ADD MG in the iGWB MML command window.

Step 3: Configure the distribution of CDRs for the added
boards.
Run ADD IPRESOURCE and ADD CDRDISTR in the
iGWB MML command window.
Step 4: Configure the backing up of CDRs for the added
boards. (optional)
Run ADD IPRESOURCE and CDRBACKUP in the
iGWB MML command window.
Step 5: Install the OS and other software for the boards.
Run STR INSTBRD in the CGP MML command window.
HUAWEI Confidential
Review Questions
What are the configuration objects of the iGWB? Which process(es)
of the iGWB Server does(do) each object correspond to?

How to configure a virtual IP address for the iGWB and make the
configuration take effect?

How to modify the format engine of the iGWB?
What are the steps for expanding the capacity of the iGWB?
HUAWEI Confidential
Contents
the iGWB
HUAWEI Confidential
Contents
Chapter 5 The Maintenance of the iGWB
5.1 Web UI of the iGWB
5.2 Routine Maintenance of the iGWB
5.3 Method of Locating the Faults
Occurred on the iGWB
HUAWEI Confidential
Web UI of the iGWB Browsing CDR Files

When you browse the CDRs files in a date directory, the CDRs files on all
the pairs of boards in the date directory are displayed.

After you select one CDR file or multiple CDR files and enter the browsing
conditions, you can view the CDRs that meet the conditions.
HUAWEI Confidential
Web UI of the iGWB Browsing CDRs

You can set which CDR fields to be displayed. After you place the mouse pointer on
a CDR record for a while, the information about the file that contains the CDR is
displayed.
After you select one CDR or multiple CDRs and click Detail, you can view the
details about the selected CDR(s) displayed in a tree structure and you can also
save or print the CDR(s).
HUAWEI Confidential
Web UI of the iGWB Querying CDRs

Through the Web UI of the
iGWB, you can query CDRs

in the following ways:
By channel: querying the CDRs

in the specified channel
By type: querying a type of CDRs
By field: querying the CDRs that

meet the value a field or the
values of some fields, supporting
fuzzy search
By time: querying the CDRs that

are generated within the
specified period
HUAWEI Confidential
Contents
HUAWEI Confidential
Maintenance of the Running Status of the iGWB

Item
Operation
Results
Checking the running

status of the boards
On the Device Panel tab page of the CGP, choose

Device Management > Software Management >
CGP and double-click Rack to check the running
status of the boards of the iGWB.
If the icon of a board is displayed in green, it indicates that the board

runs properly; if the icon of a board is displayed in red, it indicates
that the board is faulty.
Checking the service

running status
Method one: Right-click an iGWB ME in Object

Navigation Tree, and then select Module
Management in the displayed window to view the
service status and the state (active or standby) of
each module.
Method two: Run DSP SERVICE in the iGWB MML
command window to check the status of each module.
Method one: If the icon of a module is not displayed in red, it indicates

that the module works properly; otherwise, it indicates that a fault
occurs.
Method two: If the state of a module is shown as being activated or is
activated, it indicates that the module works properly; otherwise, it
indicates that a fault occurs.
Checking the receiving

of CDRs from the
switch to the iGWB
Initiate a call and ask the switch to send the CDR of

the call to the iGWB.
View the CDR through the Web UI of the iGWB.
The iGWB can receive the CDR of this call and you can view this
CDR through the Web UI of the iGWB after a while.
No data of the CDR is incorrect, lost, or duplicated.
Checking the collecting

of CDRs by the BC
The PULL mode: Check whether the second copies of

CDR files are deleted within a day. (The command to
implement this function is to be developed.)
The PUSH mode: Run DSP CDRDISTR in the iGWB
MML command window and view the link status in the
displayed result.
The PULL mode: none.

The PUSH mode: If the link status is Normal, it indicates that CDR
files are being transmitted properly; if the link status is Wait, it
indicates that no CDRs are being transmitted; and if the link status is
Fault, it indicates that a fault occurs.
Checking CDR
synchronization
between the two nodes
Run DSP CDRSYNC in the iGWB MML command

window and view the connection state in the displayed
result.
If the the connection state is Connective, it indicates that the the

connection state is normal; if the the connection state is
Disconnective, it indicates that the synchronization link is faulty; and
if the the connection state is Unknown, it indicates that an exception
occurs in the synchronization program.
Checking the backing

up of CDRs
Run DSP CDRBACKUP in the iGWB MML command

window and view the link status in the displayed
result.
If the link status is Normal, it indicates that CDR files are being
backed up properly; if the link status is Wait, it indicates that no CDRs
are being backed up; and if the link status is Fault, it indicates that a
fault occurs.
HUAWEI Confidential
Routine Maintenance of the iGWB

Item
Operation
Checking the status

and free space of the
hard disk
Run DSP HARDDISK in the CGP MML command

window and view the displayed result.
If the disk status of the slot where an iGWB

board is inserted is shown as normal, it
indicates that the hard disk of the iGWB board
is normal; otherwise, it indicates that the hard
disk of the iGWB board is faulty. The displayed
result also shows the free space of the hard
disk.
Checking whether
error CDRs exist
Error CDRs are stored in /var/igwb/frontsave/error

and can be queried through the iGWB MML
command window. (The command to implement
this function is to be developed.)
None.
Failover test (You

need to perform this
test in the case of
the two-node
system.)
Run SWP SERVICE in the iGWB MML command

window to trigger a failover, and then:
Method one: run DSP SERVICE in the iGWB
MML command window one minute later to check
the service status.
Method two: right-click iGWB in the Object
navigation tree and select Module Management
in the displayed window to view the service status
and state (active or standby) of each module.
Method one: After a failover, if the service status

is shown as active, it indicates that the failover
is successful.
Method two: If no module icon is displayed in
red, it indicates that the failover is successful.
Checking whether
alarms exist
On the MSOFTX3000 Client, click the Alarm

menu. In the displayed window, check view
whether alarms oft the iGWB exist.
None.
Checking the
communication with
the MSOFTX3000
in the iGWB MML command window, run DSP

ACTRL to view the communication between the
MSOFTX3000 and ACM, and run DSP
CDRRECV to view the communication between
the MSOFTX3000 and AP.
If the link status is Normal, it indicates that the

iGWB can communicate with the MSOFTX3000
properly; if the link status is Fault, it indicates
that a fault occurs.
HUAWEI Confidential
Results
Contents
HUAWEI Confidential
Locating Faults by Using the Commands of the iGWB

Command
Function
PING (to be developed)
Checks the connectivity between the iGWB and the BC and that between
the iGWB and the third-party server.
TRACERT (to be developed)
A route tracing command. Identifies the path through which the IP packet is
sent to the destination address.
CHK ACTRL
Checks the information about the AP allocated to each CCU by the ACM.
DSP FEMPACKET
Queries the channels and the format engine package used by each
channel. Because modifications to format engine packages do not take
effect instantly, inconsistency between a format engine package on the
Client and its corresponding one on the server may be generated. This
command can be used with the LST CDRPROC command to check this
type of inconsistency.
DSP CDRDISTR
Queries the IP address and port number used for the iGWB to distribute
CDR files to the BC in PUSH mode. Because changes to IP addresses do
not take effect instantly, inconsistency between an IP address on the Client
and its corresponding one on the server may be generated. This command
can be used with the LST IPRESOURCE command to check this type of
inconsistency.
DSP CDRBACKUP
Queries the IP address used for the iGWB to back up CDR files to the thirdparty server. Because changes to IP addresses do not take effect instantly,
inconsistency between an IP address on the Client and its corresponding
one on the server may be generated. This command can be used with the
LST IPRESOURCE command to check this type of inconsistency.
CHK RESSTATE (hidden)
Viewing the status of and dependencies among the resources

managed by the RCM process.
HUAWEI Confidential
Locating Faults by Using the Trace Files of the iGWB

Directory (on an iGWB
board)
Description
/
opt/ne/0032/proc/workspace0/pro
g/trace/acm_proc_trace_0N.txt
Stores the trace files of the ACM module. N is the serial number of the file. Its
value ranges from 1 to 5. That is, the system stores up to five trace files for a
module and the serial numbers of the trace files start from 01.
/
g/trace/ap_procK_trace_0N.txt
Stores the trace files of the AP module. K is the serial number of the AP module.
You can query the serial number of each module by running LST MODULE in the
CGP MML command window. N is the serial number of the file. Its value ranges
from 1 to 5. That is, the system stores up to five trace files for a module and the
serial numbers of the trace files start from 01.
/
g/trace/cdm_proc_trace_0N.txt
Stores the trace files of the CDM module. N is the serial number of the file. Its
/
g/trace/cbk_proc_trace_0N.txt
Stores the trace files of the CBK module. N is the serial number of the file. Its
/
g/trace/qbm_proc_trace_0N.txt
Stores the trace files of the QBM module. N is the serial number of the file. Its
/
g/trace/cqb_proc_trace_0N.txt
Stores the trace files of the CQB module. N is the serial number of the file. Its
/
g/trace/rcm_proc_trace_0N.txt
Stores the trace files of the RCM module. N is the serial number of the file. Its
HUAWEI Confidential
Review Questions
How to browse and query CDRs on the iGWB?
How to check the status of each process?
How to check whether the iGWB can receive CDRs properly?
How to perform a failover test of the iGWB. What are the
precautions?
The trace files of which processes are stored in the trace
directory?
HUAWEI Confidential
Security Level:
Thank You
www.huawei.com
www.huawei.com
HUAWEI Confidential

Working Principles and O&M of The IGWB (ATCA)

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

Working Principles and O&M of The IGWB (ATCA)

Uploaded by

Copyright:

Available Formats

Security Level:

Working Principles and O&M

HUAWEI TECHNOLOGIES CO., LTD.

What are the differences between the iGWB ATCA

What are the functions and working principles of

How to install and configure the iGWB

How to use the Web UI of the iGWB

How to locate the faults occurred on the iGWB

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Difference in the Software Structure

HUAWEI TECHNOLOGIES CO., LTD.

Difference in System Configuration

The iGWB CPCI requires an independent parameter configuration process to set

HUAWEI TECHNOLOGIES CO., LTD.

Difference in the Implementation of Querying and

HUAWEI TECHNOLOGIES CO., LTD.

Other Major Differences

Based on Windows 2000 Server

Based on SUSE Linux

Communications protocol: based

Supports FTP in PULL and PUSH

Supports FTP and SFTP in PULL and

CDR data is synchronized from the

CDR data is synchronized from the

Customization flexibility is low

Customization flexibility is high for the

based on the TCP/IP Sliding

HUAWEI TECHNOLOGIES CO., LTD.

ATCA and iGWB CPCI?

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Position of the iGWB on the Network

HUAWEI TECHNOLOGIES CO., LTD.

Functions of the iGWB

CDR is lost or duplicated during transmission.

HUAWEI TECHNOLOGIES CO., LTD.

Functions of the iGWB (Continued)

HUAWEI TECHNOLOGIES CO., LTD.

ACTA to the BC? Is there any difference between the protocols

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

configuration cabinet and the service

UPBA1<->USIA1: two CPUs + 8 GB memory

UPB3<->USIA1: two CPUs + 4 GB memory

?<->USIA1: two CPUs + 4 GB memory + 2 x

(The type of the UPB in this pair is not

HUAWEI TECHNOLOGIES CO., LTD.

Principles for Connecting the Hardware

interfaces on the SWI boards. For

iGWB are implemented through the

independent charging interface.

OMU delivers the configuration and

MSOFTX3000 delivers CDRs to the

primary boards of the iGWB to the

HUAWEI TECHNOLOGIES CO., LTD.

Cable Connections from the Interfaces on the RTMs of

USIA7 has six 100/1000M auto-negotiation Ethernet interfaces.

HUAWEI TECHNOLOGIES CO., LTD.

Cable Connections from the Interfaces on the RTMs of the