HUAWEI CBS Routine Maintenance Guide - (R002C02LG0201 - 01, Baseline-Common) - For Customer

HUAWEI CBS
R002C02LG0201
Routine Maintenance Guide

Issue
01
Date
2010-09-29
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2010. 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 the 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 (2010-09-29)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
HUAWEI CBS
About This Document
About This Document

Intended Audience
This document describes the routine maintenance and operation procedures of the HUAWEI
CBS system.
This document is intended for:
l
Maintenance engineers
Technical support engineers
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Changes in Issue 01 (2010-09-29)

Released for the first time.
Issue 01 (2010-09-29)

iii
HUAWEI CBS
Contents
Contents
About This Document...................................................................................................................iii
1 Overview......................................................................................................................................1-1
1.1 Concept of Routine Maintenance....................................................................................................................1-2
1.2 Requirements for Routine Maintenance .........................................................................................................1-2
1.2.1 Qualifications for the Maintenance Personnel.......................................................................................1-2
1.2.2 Requirements for the Running Environment.........................................................................................1-3
1.2.3 Requirements for Security Management................................................................................................1-4
1.2.4 Requirements for Equipment Documents..............................................................................................1-5
1.3 Maintenance Tools..........................................................................................................................................1-5
1.4 Recommendations for Routine Maintenance..................................................................................................1-6
2 Backup Strategies.......................................................................................................................2-1
2.1 Usage Instruction.............................................................................................................................................2-2
2.2 Backup Strategy Table....................................................................................................................................2-3
3 Daily Maintenance.....................................................................................................................3-1
3.1 I2000 Alarm Handling....................................................................................................................................3-2
3.2 I2000 Performance Monitoring.......................................................................................................................3-3
3.3 Monitoring the CBS Through the SMAP........................................................................................................3-6
3.4 Reconciling the CBS Through the SMAP.....................................................................................................3-10
3.5 Maintenance Tasks of the Operating Systems..............................................................................................3-12
3.5.1 Checking the Space Usage of File Systems (ATAE)...........................................................................3-14
3.5.2 Checking the Space Usage of File Systems (HP)................................................................................3-15
3.5.3 Checking the Space Usage of File Systems (IBM)..............................................................................3-16
3.5.4 Checking the Usage of the File System Space on the PC Server.........................................................3-17
3.5.5 Checking Memory Usage (ATAE)......................................................................................................3-18
3.5.6 Checking the Size of Free Memory (HP).............................................................................................3-19
3.5.7 Checking Memory Usage (IBM)..........................................................................................................3-19
3.5.8 Checking the Memory Usage on the PC Server...................................................................................3-20
3.5.9 Checking the CPU Usage (ATAE).......................................................................................................3-21
3.5.10 Checking the CPU Usage (HP)..........................................................................................................3-22
3.5.11 Checking the CPU Usage (IBM)........................................................................................................3-23
3.5.12 Checking the CPU Load on the PC Server........................................................................................3-24
3.5.13 Checking the Status of Network Adapters (ATAE)...........................................................................3-25
Issue 01 (2010-09-29)

HUAWEI CBS
Contents
3.5.14 Checking the Status of Network Adapters (HP)................................................................................3-26

3.5.15 Checking the Status of Network Adapters (IBM)..............................................................................3-28
3.5.16 Checking the Status of the Network Adapter on the PC Server.........................................................3-29
3.5.17 Checking the Status of the Two-Node Cluster (ATAE)....................................................................3-30
3.5.18 Checking the Status of a Two-Node Cluster (HP).............................................................................3-31
3.5.19 Checking the Status of a Two-Node Cluster (IBM)...........................................................................3-32
3.5.20 Checking the Status of the Two-Node Cluster on the PC Server.......................................................3-34
3.5.21 Checking Core Files...........................................................................................................................3-35
3.6 Maintenance Tasks of the Database..............................................................................................................3-35
3.6.1 Checking the Status of the SMDB.......................................................................................................3-37
3.6.2 Checking the Space Usage of the SMDB.............................................................................................3-37
3.6.3 Backing Up the Data of the Memory Database....................................................................................3-39
3.6.4 Checking the Status of the Listener of the Oracle Database................................................................3-41
3.6.5 Checking Usage of the Oracle Tablespaces.........................................................................................3-42
3.6.6 Checking the Status of the Listening Port of the Oracle Database......................................................3-42
3.6.7 Checking the Connection Logs of the Oracle Database.......................................................................3-44
3.6.8 Backing Up the Data of the Oracle Database.......................................................................................3-45
3.6.9 Checking the Status of the Informix Database.....................................................................................3-46
3.6.10 Checking the Space Usage of the Informix Database........................................................................3-47
3.6.11 Checking Logical Log Backup of the Informix Database..................................................................3-48
3.6.12 Backing Up the Data of the Informix Database.................................................................................3-49
3.6.13 Checking the Status of the SQL Server Database..............................................................................3-50
3.6.14 Checking the Tablespace of the SQL Server Database......................................................................3-51
3.6.15 Backing Up the Data of the SQL Server Database............................................................................3-53
3.6.16 Checking the Status of the DB2 Database.........................................................................................3-56
3.6.17 Checking the Tablespace of the DB2 Database.................................................................................3-57
3.7 Maintenance Tasks of the Applications........................................................................................................3-59
3.7.1 Checking the Status of the CBP Processes...........................................................................................3-60
3.7.2 Checking the Status of the BMP Processes..........................................................................................3-61
3.7.3 Checking the Status of the SCP Processes...........................................................................................3-62
3.7.4 Checking the Status of the Process on the DCC Proxy........................................................................3-63
3.7.5 Checking the Status of the Process on the Billing...............................................................................3-64
3.7.6 Checking the Status of the CBP Ports..................................................................................................3-65
3.7.7 Checking the Status of the BMP Ports.................................................................................................3-66
3.7.8 Checking the Status of the SCP Ports..................................................................................................3-68
3.7.9 Checking the Interface Connection Status on the DCC Proxy.............................................................3-69
3.7.10 Checking the Run Logs of the CBP...................................................................................................3-70
3.7.11 Checking the Run Logs of the BMP..................................................................................................3-70
3.7.12 Checking the Run Logs of the SCP....................................................................................................3-71
3.7.13 Checking the Run Log of the DCC Proxy..........................................................................................3-71
3.7.14 Checking the GFEP Run Log.............................................................................................................3-72
3.7.15 Checking the Run Logs of the RBI....................................................................................................3-73
vi

Issue 01 (2010-09-29)
HUAWEI CBS
Contents
3.7.16 Checking the Number of CDRs on the CBP......................................................................................3-74

3.7.17 Checking the Offline CDR on the CBP.............................................................................................3-75
3.7.18 Checking the Scheduled Tasks on the BMP......................................................................................3-75
3.7.19 Checking the AR Task.......................................................................................................................3-76
3.7.20 Checking the Running of the SSMFEP..............................................................................................3-76
3.7.21 Checking the Connection of the GFEP and Other Devices................................................................3-77
3.7.22 Checking That the RBI Transfers CDRs Normally...........................................................................3-79
4 Weekly Maintenance.................................................................................................................4-1
4.1 Backing Up the Log Files (CBP)....................................................................................................................4-3
4.2 Backing Up the Log Files (BMP)...................................................................................................................4-4
4.3 Backing Up the Log Files (SCP).....................................................................................................................4-5
4.4 Backing Up the Log Files (Billing).................................................................................................................4-6
4.5 Backing Up the Log Files (AR&DC)..............................................................................................................4-7
4.6 Backing Up the Log Files (SMP)....................................................................................................................4-8
4.7 Backing Up Log Files on the UVC.................................................................................................................4-9
4.8 Backing Up Log Files on the EVC................................................................................................................4-10
4.9 Backing Up and Clearing History CDRs on the RBI....................................................................................4-11
5 Monthly Maintenance...............................................................................................................5-1
5.1 Maintenance Items Related to Applications....................................................................................................5-2
5.1.1 Changing the Passwords of Running Users ..........................................................................................5-4
5.1.2 Changing the Passwords of SMAP Operators........................................................................................5-5
5.1.3 Backing Up Configuration Files (CBP).................................................................................................5-6
5.1.4 Backing Up Configuration Files (BMP)................................................................................................5-7
5.1.5 Backing Up Configuration Files (Billing)..............................................................................................5-8
5.1.6 Backing Up Configuration Files (AR)...................................................................................................5-9
5.1.7 Backing Up Configuration Files (DC).................................................................................................5-11
5.1.8 Backing Up Configuration Files (SCP)................................................................................................5-12
5.1.9 Backing Up Configuration Files (SMP)...............................................................................................5-13
5.1.10 Backing Up Configuration Files of the GFEP...................................................................................5-14
5.1.11 Backing Up Configuration Files of the RBI.......................................................................................5-16
5.1.12 Backing Up Configuration Files of the iWeb.....................................................................................5-18
5.1.13 Backing Up the Application Program (CBP).....................................................................................5-19
5.1.14 Backing Up the Application Program (BMP)....................................................................................5-21
5.1.15 Backing Up the Application Program (AR&DC)..............................................................................5-22
5.1.16 Backing Up the Application Program (Billing).................................................................................5-24
5.1.17 Backing Up Log Files on the USAU..................................................................................................5-25
5.1.18 Backing Up Log Files on the URP.....................................................................................................5-26
5.1.19 Backing Up Log Files on the iWeb....................................................................................................5-26
5.1.20 Backing Up and Clearing CDR Files on the Billing..........................................................................5-28
5.1.21 Understanding the Service Trend Through iWeb Reports.................................................................5-29
5.1.22 Understanding Key Service Indexes Through the LBI System.........................................................5-31
5.2 Maintenance Items Related to Hardware......................................................................................................5-34
Issue 01 (2010-09-29)

vii
HUAWEI CBS
Contents
5.2.1 Cleaning the Tape Drive......................................................................................................................5-34

5.2.2 Checking the Number of Available Tapes...........................................................................................5-35
5.2.3 Checking the Power Modules and UPS (ATAE).................................................................................5-35
5.2.4 Checking the Power Modules and UPS (Minicomputers)...................................................................5-36
5.2.5 Cleaning the Cabinets...........................................................................................................................5-36
5.3 Checking the Viruses on the Terminal Computer.........................................................................................5-37
5.4 Checking Whether the Device Maintenance Contract Expires.....................................................................5-38
6 Yearly Maintenance...................................................................................................................6-1
6.1 Switching Test.................................................................................................................................................6-2
6.1.1 Testing the Switchover Between Two Nodes (ATAE)..........................................................................6-2
6.1.2 Testing the Switchover Between Two Nodes (HP)...............................................................................6-4
6.1.3 Testing the Switchover Between Two Nodes (IBM)...........................................................................6-14
6.1.4 Testing the Switchover Between the Boards on the USAU.................................................................6-17
6.1.5 Testing the Switchover Between the Boards on the URP....................................................................6-18
6.2 Cleaning the dust (ATAE).............................................................................................................................6-19
6.3 Cleaning the dust (Minicomputers)...............................................................................................................6-20
7 Holiday Maintenance................................................................................................................7-1
7.1 Evaluating the Traffic on the SCP...................................................................................................................7-2
8 Maintenance Related to Upgrade............................................................................................8-1

8.1 Backing Up the Operating Systems................................................................................................................8-2
8.1.1 Backing Up the Operating System (IBM)..............................................................................................8-2
8.1.2 Backing Up the Operating System (HP)................................................................................................8-3
8.1.3 Backing Up the Operating System (SuSE)............................................................................................8-5
8.2 Backing Up the Application Program.............................................................................................................8-7
8.2.1 Backing Up the Application Program (CBP).........................................................................................8-7
8.2.2 Backing Up the Application Program (BMP)........................................................................................8-9
8.2.3 Backing Up the Application Program (AR&DC)................................................................................8-10
8.2.4 Backing Up the Application Program (Billing)...................................................................................8-12
8.2.5 Backing Up Application Programs of the GFEP.................................................................................8-13
8.3 Backing Up Configuration Files...................................................................................................................8-15
8.3.1 Backing Up Configuration Files (CBP)...............................................................................................8-16
8.3.2 Backing Up Configuration Files (BMP)..............................................................................................8-17
8.3.3 Backing Up Configuration Files (Billing)............................................................................................8-19
8.3.4 Backing Up Configuration Files (AR).................................................................................................8-20
8.3.5 Backing Up Configuration Files (DC).................................................................................................8-21
8.3.6 Backing Up Configuration Files (SCP)................................................................................................8-22
8.3.7 Backing Up Configuration Files on the EVC.......................................................................................8-23
8.3.8 Backing Up Configuration Files on the UVC......................................................................................8-24
8.3.9 Backing Up Configuration Files of the GFEP.....................................................................................8-25
8.3.10 Backing Up Configuration Files of the RBI.......................................................................................8-27
8.3.11 Backing Up Configuration Files of the iWeb.....................................................................................8-29
viii

Issue 01 (2010-09-29)
HUAWEI CBS
Contents
9 Routine Maintenance Tables...................................................................................................9-1

9.1 Daily Maintenance Table................................................................................................................................9-2
9.2 Weekly Maintenance Table.............................................................................................................................9-4
9.3 Monthly Maintenance Table........................................................................................................................... 9-5
9.4 Yearly Maintenance Table.............................................................................................................................. 9-6
9.5 Holiday Maintenance Table............................................................................................................................9-7
9.6 List of Maintenance Items for Upgrade.......................................................................................................... 9-8
A Appendix...................................................................................................................................A-1
A.1 Critical Operations in the CBS......................................................................................................................A-2
A.2 Impact Analysis Table of CBS Password Change......................................................................................A-11
A.3 Glossary.......................................................................................................................................................A-15
A.4 Acronyms and Abbreviations......................................................................................................................A-24
Issue 01 (2010-09-29)

ix
HUAWEI CBS
Figures
Figures
Figure 2-1 Usage Instruction of Backup Strategies..............................................................................................2-2
Figure 3-1 Browse Current Fault Alarms by Status.............................................................................................3-2
Figure 3-2 Viewing alarm handling suggestions..................................................................................................3-3
Figure 3-3 List of performance monitoring tasks.................................................................................................3-5
Figure 3-4 Monitoring result................................................................................................................................3-5
Figure 3-5 Monitoring layer 0..............................................................................................................................3-8
Figure 3-6 AR monitoring layer 1........................................................................................................................3-8
Figure 3-7 Configuration page at monitoring layer 0...........................................................................................3-9
Figure 3-8 Reconciliation interface....................................................................................................................3-11
Figure 3-9 Configuration page of the reconciliation interface...........................................................................3-12
Figure 3-10 Window where the service manager of SQL Server 2000 is running............................................3-51
Figure 3-11 Window where the service manager of SQL Server 2000 stops running.......................................3-51
Figure 3-12 Checking the tablespace of the SQL server database.....................................................................3-52
Figure 3-13 Adding data files to the tablespace.................................................................................................3-53
Figure 3-14 Page for backing up the data...........................................................................................................3-54
Figure 3-15 Selecting the database and backup mode in the SQL server backup window................................3-55
Figure 3-16 Window of determining the file path and file name of the backup data ........................................3-56
Figure 3-17 Connection status of the GFEP client.............................................................................................3-78
Figure 3-18 Source path and destination path of the sending module on the RBI client...................................3-79
Figure 5-1 Changing the password of an SMAP operator................................................................................... 5-5
Figure 5-2 Checking the backup of the GFEP configuration files.....................................................................5-15
Figure 5-3 RBI client window............................................................................................................................5-17
Figure 5-4 Entering the backup information......................................................................................................5-17
Figure 5-5 iWeb backup menu...........................................................................................................................5-18
Figure 5-7 Creating a new periodical report.......................................................................................................5-30
Figure 5-8 KPI reports........................................................................................................................................5-32
Figure 5-9 Detailed report information..............................................................................................................5-33
Figure 8-1 Backup window of the GFEP client.................................................................................................8-14
Figure 8-2 Backing up configuration information.............................................................................................8-14
Figure 8-3 Checking the backup of the GFEP configuration files.....................................................................8-26
Figure 8-4 RBI client window............................................................................................................................8-28
Figure 8-5 Entering the backup information......................................................................................................8-28
Issue 01 (2010-09-29)

xi
HUAWEI CBS
Figures
xii

Issue 01 (2010-09-29)
HUAWEI CBS
Tables
Tables
Table 1-1 Parameters of air purity........................................................................................................................1-4
Table 1-2 Subsystem and tools supporting CBS maintenance.............................................................................1-5
Table 2-1 CBS backup strategy table: operating systems (server).......................................................................2-3
Table 2-2 CBS backup strategy table: databases (server)....................................................................................2-5
Table 2-3 CBS backup strategy table: databases (ATAE)....................................................................................2-7
Table 2-4 CBS backup strategy table: applications (server)................................................................................2-9
Table 2-5 CBS backup strategy table: applications (ATAE).............................................................................2-10
Table 2-6 CBS backup strategy table: log files (server).....................................................................................2-12
Table 2-7 CBS backup strategy table: log files (ATAE)....................................................................................2-13
Table 2-8 CBS backup strategy table: configuration files (server)....................................................................2-14
Table 2-9 CBS backup strategy table: configuration files (ATAE)...................................................................2-16
Table 3-1 KPI indexes of the I2000......................................................................................................................3-4
Table 3-2 Description of icons at monitoring layer 0...........................................................................................3-7
Table 3-3 Description of options in the backup window....................................................................................3-55
Table 4-1 Description of configuration items.....................................................................................................4-11
Table 5-1 Method of backing up the GFEP configuration files.........................................................................5-15
Table 5-2 Basic KPIs..........................................................................................................................................5-31
Table 5-3 Relationship between the cleaning cycle and the using frequency of the tape drive.........................5-34
Table 6-1 Two-node cluster status......................................................................................................................6-15
Table 6-2 Two-node cluster status......................................................................................................................6-15
Table 8-1 Method of backing up the GFEP configuration files.........................................................................8-26
Table 9-1 Daily maintenance table.......................................................................................................................9-2
Table 9-2 Weekly maintenance table...................................................................................................................9-4
Table 9-3 Monthly maintenance table..................................................................................................................9-5
Table 9-4 Yearly maintenance table.....................................................................................................................9-7
Table 9-5 Holiday maintenance table...................................................................................................................9-7
Table 9-6 Maintenance table for upgrade.............................................................................................................9-8
Table A-1 Critical operations in the Informix database......................................................................................A-2
Table A-2 Critical operations in the Oracle database .........................................................................................A-3
Table A-3 Critical operations in ATAE...............................................................................................................A-4
Table A-4 Critical Operations in an HP Minicomputer.......................................................................................A-6
Table A-5 Critical Operations in IBM Minicomputer.........................................................................................A-7
Table A-6 Critical operations on the SCP...........................................................................................................A-8
Issue 01 (2010-09-29)

xiii
HUAWEI CBS
Tables
Table A-7 Critical operations on the BMP..........................................................................................................A-9

Table A-8 Critical Operations on the CBP........................................................................................................A-10
Table A-9 Critical operations in the SMDB......................................................................................................A-10
Table A-10 Impact analysis table of CBS password change.............................................................................A-11
xiv

Issue 01 (2010-09-29)
HUAWEI CBS
1 Overview
Overview
About This Chapter

This topic describes the overview to and preparations for routine maintenance.
1.1 Concept of Routine Maintenance
This topic describes the definition, frequency, and objective of routine maintenance.
1.2 Requirements for Routine Maintenance
This topic describes the requirements for routine maintenance.
1.3 Maintenance Tools
This task describes the CBS maintenance tools, functions, corresponding documents, and paths
to the tools and documents.
1.4 Recommendations for Routine Maintenance
This topic describes the recommendations of routine maintenance.
Issue 01 (2010-09-29)

1-1
HUAWEI CBS
1 Overview
1.1 Concept of Routine Maintenance

This topic describes the definition, frequency, and objective of routine maintenance.
Definition
Routine maintenance is also called predictive maintenance or periodical maintenance. Routine
maintenance is performed periodically when devices are in normal state.
Frequency
Frequency of performing each task is provided according to the following factors:
l
Scenario of performing a task
Risk ratio
Effects of a risk in different periods
Objective
The objective of routine maintenance is as follows:
l
Find potential problems in advance and make the device in proper running state.
Learn the running status of the system and provide suggestions of the system development.
1.2 Requirements for Routine Maintenance

This topic describes the requirements for routine maintenance.
1.2.1 Qualifications for the Maintenance Personnel
This topic describes the qualifications that the maintenance personnel must have.
1.2.2 Requirements for the Running Environment
This topic describes the requirements on the running environment.
1.2.3 Requirements for Security Management
This topic describes the requirements of security management.
1.2.4 Requirements for Equipment Documents
This topic describes the requirements of equipment documents.
1.2.1 Qualifications for the Maintenance Personnel

This topic describes the qualifications that the maintenance personnel must have.
The maintenance personnel must have the following qualifications to make the maintenance
effective:
1-2
Understand the principle and networking of each system component.
Be familiar with the operating systems (such as UNIX and Linux) and the databases (such
as Oracle, Informix, SQL Server, and DB2), and master common operation commands and
effects to the system.
Issue 01 (2010-09-29)
HUAWEI CBS
1 Overview
Master the common maintenance tools.
Have the skills of summarizing and analyzing data.
Before performing the routine maintenance, attend maintenance training to learn the
maintenance knowledge, basic operation skills, and emergency handling skills of the
devices. You must also strictly follow the operation rules and industrial safety rules to
ensure personnel safety and device safety.
1.2.2 Requirements for the Running Environment

This topic describes the requirements on the running environment.
The aspects equipment room, power supply system, air conditioning system, lighting system,
fire prevention, and storage conditions need to meet the requirements on the running
environment.
Physical Environment
l
The temperature ranges from 15C to 25C. The recommended temperature is 20C 2
C. The hourly temperature variation is less than 3C.
The relative humidity ranges from 40% to 70%. The hourly relative humidity variation is
less than 3%.
A high-voltage static air cleaner is a recommended device in the minicomputer room.
Do not put the articles such as user manuals, software application manuals, report paper
and ribbons in the minicomputer room.
Power Supply System

l
The power supply of the equipment must be exported directly from the main distribution
panel of a factory or a building (independent special power supply). In addition, the power
supply cannot be shared by devices irrelevant to the system, such as lighting devices or
duplicating machines.
The AC power supply regulator should be installed to filter out surge and interference, thus
providing the equipment in the minicomputer room with pure and stable power supply.
An uninterruptible power supply (UPS) is required to avoid data loss and device damage
in case of power failure.
If the 110 V and 220 V AC sockets are both provided, they must be clearly labeled.
The positions of the power supply cables and sockets must be clearly marked in the switch
board for reference in future troubleshooting or expansion.
Outlets for signal cables/power cables must be left on the raised floor and the edge of the
outlets must be covered with the rubber pad to protect the power and signal cable.
The inlets through which the signal cable power cables are led into the computer room must
be tightly sealed to prevent dirt, rats, and insects from getting in. If the equipment room is
divided into minicomputer room and operation room, the conduit line must be reserved in
the partition wall to avoid leading the signal cable through the wall. The conduit may adopt
PVC tube with a diameter of over 6 cm.
Issue 01 (2010-09-29)

1-3
HUAWEI CBS
1 Overview
Air Conditioning System, Lighting System, and Fire Prevention

l
To meet the requirements of the equipment for running time and room cleanness, an
independent air condition system must be adopted for the computer room, but central air
conditioning system must be avoided whenever possible.
The minicomputer room and the operation room must be installed with emergent lighting
with backup power of maintenance-free batteries.
The minicomputer room should be equipped with automatic fire alarm according to related
fire fighting regulations for buildings, but automatic sprinklers are strictly prohibited.
Fire extinguishing devices in the minicomputer room must be applicable to electrical and
communication devices. Common fire extinguishers such as sprinkler system are not
recommended.
The operation personnel must have training on fire control knowledge, and they must check
the fire control device periodically.
Storage
All the components not yet installed must be stored in a suitable storage space.
l
Equipment: All equipment must be packed properly.
Temperature: 15C to 25C. The hourly temperature variation is less than 10C.
Relative humidity: 30% to 80%.
The air purity must meet the requirements listed in Table 1-1.
Table 1-1 Parameters of air purity
Particle Diameter (m)
Allowed Number of Particles

(ppm)
4 x 107
1.5
4 x 106
4 x 105
The content of sulfur dioxide cannot exceed 0.14 ppm.
1.2.3 Requirements for Security Management

This topic describes the requirements of security management.
Network Security
1-4
The personnel that have no rights are prohibited from touching equipment.
Avoid using terminals on the LAN to access Internet or play games, so as to avoid illegal
access and viruses.
Avoid portable computers to connect to the LAN.

Issue 01 (2010-09-29)
HUAWEI CBS
1 Overview
System Security
l
Strictly control the enabling of the network services.
The connection status of the network is routinely monitored to ensure that an access to the
network is authorized.
Passwords of users must be changed periodically, and rights must be strictly controlled for
proper tasks.
Data Security
The backup plan must be carried out strictly to back up the system data periodically.
1.2.4 Requirements for Equipment Documents

This topic describes the requirements of equipment documents.
Equipment documents have the following types:
l
Product documents
Engineering documents of network
Engineering documents of device
Engineering documents of upgrade
Networking diagram
Equipment room layout
Specifications of special software
Technical documents, user documents, and maintenance documents delivered with

equipment. The completion of equipment documents must be ensured. In addition, files
must be updated in time along with device configuration and networking changes so as to
guide the maintenance more effectively.
The previous routine maintenance tables for comparison must be ensured, so as to check
certain performance data, such as CPU, memory usage.
1.3 Maintenance Tools

This task describes the CBS maintenance tools, functions, corresponding documents, and paths
to the tools and documents.
Table 1-2 Subsystem and tools supporting CBS maintenance
Issue 01 (2010-09-29)
Name
Function
Reference
I2000
Provides alarm information in real

time to help carrier operators to find
problems at earliest so that the
effects of the problems on service
use can be reduced.
I2000 iCnfg Help
HUAWEI CBS Alarm Reference

1-5
HUAWEI CBS
1 Overview
Name
Function
Reference
iWeb
Collects service data automatically

for maintenance personnel to obtain
the trend information about service
data. In this case, preventive
measures can be taken in advance.
HUAWEI CBS Report Help
iCheck
Performs most of the maintenance

items automatically. During daily
maintenance, monthly maintenance,
and holiday maintenance, the iCheck
can be used for automatic check.
CBS iCheck Configuration Help
Breeze iCheck Help
Collects the information about

network devices for monitoring the
statuses of the network devices and
for locating device problems.
Collect Data Help
Collect
Data
Periodically collects the CAPS on

the SCP and provides the function of
drawing the trend of the CAPS.
TabMnt
Backs up and deletes the data of large

tables periodically.
TabMnt VxxxRxxxCxxBxx Installation

and Upgrade Guide
NOTE
You can obtain the paths to the preceding tools and documents at the website http://support.huawei.com.
For the specific paths, see the version matching table released with this version.
1.4 Recommendations for Routine Maintenance

This topic describes the recommendations of routine maintenance.
Before performing the routine maintenance, you must read the following recommendations:
1-6
When replacing device components, or inserting/pulling out a board, you must take the
ESD-preventive measures and wear an ESD-preventive wrist strap.
If you meet any problems during the maintenance, record the original data in details, and
then solve the problem by referring to relevant documents. If you still cannot solve the
problem, contact Huawei engineers at once.
If any emergency occurs, you must handle the emergency problem according to the
emergency maintenance guide, and then contact Huawei customer service center or the
regional office in time.
You must keep the administrator password secret and change it periodically. The
management of passwords must be partitioned strictly by levels according to the operation
rights of the maintenance staff and the maintenance rights of the workstation. The password
partitioning is to ensure the safe running of the terminal system.

Issue 01 (2010-09-29)
HUAWEI CBS
2 Backup Strategies
Backup Strategies
About This Chapter

The important data or files in the CBS system need to be backed up periodically so that they can
be restored if necessary. This chapter describes the backup strategies of the core NEs and
neighboring NEs of the CBS system, including the backup strategies of operating systems,
databases, applications, logs, configuration files, and CDRs. Each backup strategy covers the
information such as the backup frequency, storage medium, and the contents to be backed up.
2.1 Usage Instruction
Service engineers need to read the backup strategies before performing backup operations to
obtain the information such as backup frequency, storage medium, and backup contents.
2.2 Backup Strategy Table
The backup strategy table contains the backup strategies of operating systems, databases,
applications, configuration files, logs, and CDRs.
Issue 01 (2010-09-29)

2-1
HUAWEI CBS
2 Backup Strategies
2.1 Usage Instruction

Service engineers need to read the backup strategies before performing backup operations to
obtain the information such as backup frequency, storage medium, and backup contents.
Usage Instruction of Backup Strategies

It is recommended that service engineers refer to the backup strategies and perform backup tasks
according to the following instruction:
Figure 2-1 Usage Instruction of Backup Strategies
Maintenance engineers need to understand the backup policy, including the information such as
the backup frequency, backup contents, and backup medium. In addition, maintenance engineers
need to understand the specific backup methods. For details about the backup policy, see 2.2
Backup Strategy Table. The backup methods are described in different maintenance cycle
chapters according to the backup frequency. The following is an example:
Example
[Example 1- Find Backup Task According to Backup Frequency] Backing up the database
2-2

Issue 01 (2010-09-29)
HUAWEI CBS
2 Backup Strategies
1.
Find the table named "Backup strategy: databases." Read the backup strategies for the
database of the XX NE to understand the backup contents and the backup frequency "every
day."
2.
In the chapter related to daily maintenance, find the section related to backing up the
database of the XX NE, and then refer to the backup operation guide in this section.
[Example 2- Find Directly] Backing up the BMP operating system

1.
Assume that the on-site BMP uses the ATAE server. full-text search the section related to
backing up the SuSE operating system , and then refer to the backup operation guide in this
section.
2.
Maintenance engineers need to know about the backup medium and frequency according
to the table "Backup strategy: operating systems."
2.2 Backup Strategy Table

The backup strategy table contains the backup strategies of operating systems, databases,
applications, configuration files, logs, and CDRs.
NOTE
The values described in this section are recommended values in normal cases. You can change them as
required. For example, the backup frequency relates to the number of subscribers of an office, so you need
to change the backup frequency according to the number of subscribers of this office. Generally, the greater
the number of subscriber is, the more frequent the data needs to be backed up.
Special description:
l
Backup retention duration: If no special description is provided, the default retention

duration is to retain the backup files until the next backup is successful.
Backup retention quantity: If no special description is provided, the default retention

quantity for database files is at least two copies. For backup of other data, at least one copy
of backup files is required.
Backup level: If no special description is provided, the full backup is required for the
database backup.
Active and standby nodes: If no special description is provided, all backup contents need
to be backed up on both the active and standby nodes.
Backup Strategy: Operating Systems

Table 2-1 CBS backup strategy table: operating systems (server)
Issue 01 (2010-09-29)
NE
Frequency
Contents
Medium
Executio
n Mode
Remarks
CBP
Every year; after

each installation
and upgrade
Full
backup of
root
volume
Tape
Manual
Perform the backup in

special cases on both the
active and standby
nodes.
BMP
Every year; after

each installation
and upgrade
Full
backup of
root
volume
Tape
Manual

active and standby
nodes.

2-3
HUAWEI CBS
2 Backup Strategies
NE
Frequency
Contents
Medium
Executio
n Mode
Remarks
SCP
No manual backup is
required.
If backup is required,
contact Huawei service
engineers.
NOTE
The SCP adopts the
centralized backup
scheme, which is
supported by a
professional service team.
Billin
g
Every year; after

each installation
and upgrade
Full
backup of
root
volume
Tape
Manual

active and standby
nodes.
AR
Every year; after

each installation
and upgrade
Full
backup of
root
volume
Tape
Manual

active and standby
nodes.
DC
Every year; after

each installation
and upgrade
Full
backup of
root
volume
Tape
Manual

active and standby
nodes.
UVC
EVC
GFEP
RBI
USA
U
URP
iWeb
DCC
Procx
y
Note: The character "-" indicates that the backup is not required.
NOTE
The ATAE operating system does not need to be backed up manually.
2-4

Issue 01 (2010-09-29)
HUAWEI CBS
2 Backup Strategies
Backup Strategy: Databases

Table 2-2 CBS backup strategy table: databases (server)
NE
Frequency
CBP
Issue 01 (2010-09-29)
Physical
database:
every day
(00:00:0004:00:00)/
before
upgrade
(10:00:00)
Contents
l
Physical
database:
full
backup
Memory
database:
full
backup
Memory
database:
every day
Medium
l
Physical
database:
temporary
space of tapes
or disk arrays
Memory
database: disk
or tape (Single
CBP node is
directly backed
up to the tape.)
Execution
Mode
l
Physical
database:
manual
backup
Memory
database:
manual
backup
Remarks
For C02, only
the standby
node can be
backed up
and the active
node cannot
be backed up
currently. For
C03, only the
active node
needs to be
backed up,
which is
similar to the
Informix
HDR. The
checkpoint of
the memory
database
needs to be
stopped
during the
backup.
BMP
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
full backup
Physical database:
temporary space
of tapes or disk
arrays
Physical
database:
manual
backup
SCP
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
full backup
Physical database:
temporary space
of tapes or disk
arrays
Physical
database:
manual
backup
Billin
g
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
exclude
prepaid
CDR table,
other need
backup
Physical database:
temporary space
of tapes or disk
arrays
Physical
database:
manual
backup

2-5
HUAWEI CBS
2 Backup Strategies
2-6
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
AR
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
full backup
Physical database:
temporary space
of tapes or disk
arrays
Physical
database:
manual
backup
DC
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
full backup
Physical database:
temporary space
of tapes or disk
arrays
Physical
database:
manual
backup
UVC
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
full backup
Physical database:
temporary space
of tapes or disk
arrays
Physical
database:
manual
backup
EVC
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
full backup
Physical database:
temporary space
of tapes or disk
arrays
Physical
database:
manual
backup
GFEP
RBI
USA
U
Every day
Back up only
the BAM,
ALARM,
and STAT
database
files.
Disk
Automatic
Verify that
the weekly
backups are
successful
and are
transferred to
other media.
The backup
media are
unfixed.

Issue 01 (2010-09-29)
HUAWEI CBS
2 Backup Strategies
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
URP
Every day
Back up only
the BAM
and
ALARM
database
files.
Disk
Automatic
Verify that
the weekly
backups are
successful
and are
transferred to
other media.
The backup
media are
unfixed.
iWeb
DCC
Procx
y
Table 2-3 CBS backup strategy table: databases (ATAE)

NE
Frequency
CBP
Issue 01 (2010-09-29)
Physical
database:
every day
(00:00:0004:00:00)/
before
upgrade
(10:00:00)
Memory
database:
every day
Contents
l
Physical
database:
full
backup
Memory
database:
full
backup
Medium
l
Physical
database:
Back up to
the built-in
disk of the
server, and
then back up
to tapes
Memory
database:
disk or tape
(Single CBP
node is
directly
backed up to
the tape)

Execution
Mode
l
Physical
database:
manual
backup
Memory
database:
manual (or
purchase
backup
software)
Remarks
For C02, only
the standby
node can be
backed up and
the active node
cannot be
backed up
currently. For
C03, only the
active node
needs to be
backed up,
which is
similar to the
Informix HDR.
The checkpoint
of the memory
database needs
to be stopped
during the
backup.
2-7
HUAWEI CBS
2 Backup Strategies
2-8
NE
Frequency
Contents
Medium
BMP
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
full backup
Physical
Physical
database: Back database:
up to the built- manual backup
in disk of the
server, and
then back up to
tapes
SCP
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
full backup
Physical
Physical
in disk of the
server, and
then back up to
tapes
Billin
g
Every month;
every year;
after each
installation
and upgrade
Full backup
of the root
directory
Built-in disks
and tapes of the
backup server
Manual (or
purchase
backup
software)
AR
Every month;
every year;
after each
installation
and upgrade
Full backup
of the root
directory
Built-in disks
and tapes of the
backup server
Manual (or
purchase
backup
software)
DC
Every month;
every year;
after each
installation
and upgrade
Full backup
of the root
directory
Built-in disks
and tapes of the
backup server
Manual (or
purchase
backup
software)
UVC
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
full backup
Physical
Physical
in disk of the
server, and
then back up to
tapes
EVC
Physical
database:
every day
(00:00:00-04:
00:00)/before
upgrade
(10:00:00)
Physical
database:
full backup
Physical
Physical
in disk of the
server, and
then back up to
tapes
GFEP

Execution
Mode
Remarks
Issue 01 (2010-09-29)
HUAWEI CBS
2 Backup Strategies
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
RBI
iWeb
DCC
Procx
y
Backup Strategy: Applications

Table 2-4 CBS backup strategy table: applications (server)
Issue 01 (2010-09-29)
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
CBP
Every month;
every year; after
each installation
and upgrade
Full backup
of the root
directory
Tape
Manual
BMP
Every month;
every year; after
each installation
and upgrade
Full backup
of the root
directory
Tape
Manual
SCP
Every month;
every year; after
each installation
and upgrade
Full backup
of the root
directory
Tape
Manual
Billing
Every week
(00:00:00-04:00:
00)
Full backup
Tape or
disk
Manual (or
purchase
backup
software)
Perform the
backup on both
the active and
standby nodes.
AR
Every week
(00:00:00-04:00:
00)
Full backup
Tape or
disk
Manual (or
purchase
backup
software)
Perform the
backup on both
the active and
standby nodes.
DC
Every week
(00:00:00-04:00:
00)
Full backup
Tape or
disk
Manual (or
purchase
backup
software)
Perform the
backup on both
the active and
standby nodes.

2-9
HUAWEI CBS
2 Backup Strategies
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
UVC
Every month;
every year; after
each installation
and upgrade
Full backup
of the root
directory
Tape
Manual
EVC
Every month;
every year; after
each installation
and upgrade
Full backup
of the root
directory
Tape
Manual
GFEP
After each
installation and
upgrade
System
directories
Tape
Manual
RBI
USAU
URP
iWeb
DCCPr
ocxy
Table 2-5 CBS backup strategy table: applications (ATAE)
2-10
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
CBP
Every month;
every year; after
each
installation and
upgrade
Full
backup of
the root
directory
Built-in disks
and tapes of the
backup server
Manual (or
purchase
backup
software)
BMP
Every month;
every year; after
each
installation and
upgrade
Full
backup of
the root
directory
Built-in disks
and tapes of the
backup server
Manual (or
purchase
backup
software)
SCP
Every month;
every year; after
each
installation and
upgrade
Full
backup of
the root
directory
Built-in disks
and tapes of the
backup server
Manual (or
purchase
backup
software)

Issue 01 (2010-09-29)
HUAWEI CBS
Issue 01 (2010-09-29)
2 Backup Strategies
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
Billin
g
Every month;
before and after
each upgrade
Full
backup
Tape or disk (A
single
application
node is backed
up on the
appointed disk
space
(lvbackup) or
tape.)
Manual
Perform the
backup on both
the active and
standby nodes.
AR
Every month;
before and after
each upgrade
Full
backup
Tape or disk (A
single
application
node is backed
up on the
appointed disk
space
(lvbackup) or
tape.)
Manual
Perform the
backup on both
the active and
standby nodes.
DC
Every month;
before and after
each upgrade
Full
backup
Tape or disk (A
single
application
node is backed
up on the
appointed disk
space
(lvbackup) or
tape.)
Manual
Perform the
backup on both
the active and
standby nodes.
UVC
Every month;
every year; after
each
installation and
upgrade
Full
backup of
the root
directory
Built-in disks
and tapes of the
backup server
Manual (or
purchase
backup
software)
EVC
Every month;
every year; after
each
installation and
upgrade
Full
backup of
the root
directory
Built-in disks
and tapes of the
backup server
Manual (or
purchase
backup
software)
GFEP
After each
installation and
upgrade
System
directories
Built-in disks
and tapes of the
backup server
Manual (or
purchase
backup
software)
RBI
iWeb

2-11
HUAWEI CBS
2 Backup Strategies
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
DCC
Procx
y
Backup Strategy: Log Files

Table 2-6 CBS backup strategy table: log files (server)
2-12
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
CBP
Every week
(00:00:00-0
4:00:00)
Full
backup
Tape or disk (A
single application
node is backed up on
the appointed disk
space (lvbackup) or
tape.)
Manual
Perform the
backup on
both the
active and
standby
nodes.
BMP
Every week
(00:00:00-0
4:00:00)
Full
backup
Tape or disk (A
single application
the appointed disk
space (lvbackup) or
tape.)
Manual
SCP
Every week
(00:00:00-0
4:00:00)
Full
backup
Tape or disk (A
single application
the appointed disk
space (lvbackup) or
tape.)
Manual
UVC
Every week
(00:00:00-0
4:00:00)
Full
backup
Tape or disk (A
single application
the appointed disk
space (lvbackup) or
tape.)
Manual
EVC
Every week
(00:00:00-0
4:00:00)
Full
backup
Tape or disk (A
single application
the appointed disk
space (lvbackup) or
tape.)
Manual
GFEP

Issue 01 (2010-09-29)
HUAWEI CBS
2 Backup Strategies
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
RBI
USAU
Every month
MSSQL
\Data;
all .log
files and
*log.bak
files
Local disk or other

media
Manual
URP
Every month
MSSQL
\Data;
all .log
files and
*log.bak
files
Local disk or other

media
Manual
iWeb
Every month
Local disk or other

media
Manual
DCCProcx
y
Table 2-7 CBS backup strategy table: log files (ATAE)
Issue 01 (2010-09-29)
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
CBP
Every week
(00:00:00-0
4:00:00)
Full backup
Tape or disk
Manual (or
purchase
backup
software)
Perform the
backup on
both the
active and
standby
nodes.
BMP
Every week
(00:00:00-0
4:00:00)
Full backup
Tape or disk
Manual (or
purchase
backup
software)
SCP
Every week
(00:00:00-0
4:00:00)
Full backup
Tape or disk
Manual (or
purchase
backup
software)
UVC
Every week
(00:00:00-0
4:00:00)
Full backup
Tape or disk
Manual (or
purchase
backup
software)

2-13
HUAWEI CBS
2 Backup Strategies
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
EVC
Every week
(00:00:00-0
4:00:00)
Full backup
Tape or disk
Manual (or
purchase
backup
software)
GFEP
RBI
iWeb
Every
month
Local disk or other

media
Manual
DCCProc
xy
Backup Strategy: Configuration Files

Table 2-8 CBS backup strategy table: configuration files (server)
2-14
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
CBP
Every
month;
before and
after each
upgrade
Full backup
Tape or disk (A
single application
node is backed up
on the appointed
disk space
(lvbackup) or
tape.)
Manual
Perform the
backup on both
the active and
standby nodes.
BMP
Every
month;
before and
after each
upgrade
Full backup
Tape or disk (A
single application
node is backed up
on the appointed
disk space
(lvbackup) or
tape.)
Manual
Perform the
backup on both
the active and
standby nodes.
SCP
Before and
after each
upgrade
Full backup
Tape or disk
Manual
Perform the
backup on both
the active and
standby nodes.
UVC
Before and
after each
upgrade
Full backup
Tape or disk
Manual
Perform the
backup on both
the active and
standby nodes.

Issue 01 (2010-09-29)
HUAWEI CBS
2 Backup Strategies
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
EVC
Before and
after each
upgrade
Full backup
Tape or disk
Manual
Perform the
backup on both
the active and
standby nodes.
GFEP
Every day
config
directory in
the GFEP
installation
directory
Tape or disk
Automatic
Verify that the

backups are
successful and
are transferred
to other media
every month
and before and
after each
upgrade. The
backup media
are unfixed.
RBI
Every
month;
before and
after each
upgrade
Tape or disk
Manual
USAU
URP
iWeb
Every
month;
before and
after each
upgrade
Tape or disk
Automatic or manual
DCCPr
ocxy
Before and
after each
upgrade
DCCPro
xy_modu
le_config
.txt
Tape or disk
Manual
DiamBas
eConfig.
xml
icdcomm
.cfg
filesync.
cfg
NMAdpt
Cfg.xml
node.cfg
Issue 01 (2010-09-29)

2-15
HUAWEI CBS
2 Backup Strategies
Table 2-9 CBS backup strategy table: configuration files (ATAE)
2-16
NE
Frequency
Contents
Medium
CBP
Every month;
before and
after each
upgrade
Full backup
Tape or disk (A
Manual
single application
node is backed up
on the appointed
disk space
(lvbackup) or
tape.)
Perform the
backup on
both the
active and
standby
nodes.
BMP
Every month;
before and
after each
upgrade
Full backup
Tape or disk (A
Manual
single application
node is backed up
on the appointed
disk space
(lvbackup) or
tape.)
Perform the
backup on
both the
active and
standby
nodes.
SCP
Before and
after each
upgrade
Full backup
Tape or disk
Manual
Perform the
backup on
both the
active and
standby
nodes.
UVC
Before and
after each
upgrade
Full backup
Tape or disk
Manual
Perform the
backup on
both the
active and
standby
nodes.
EVC
Before and
after each
upgrade
Full backup
Tape or disk
Manual
Perform the
backup on
both the
active and
standby
nodes.

Execution
Mode
Remarks
Issue 01 (2010-09-29)
HUAWEI CBS
2 Backup Strategies
NE
Frequency
Contents
Medium
Execution
Mode
Remarks
GFEP
Every day
config
directory in the
GFEP
installation
directory
Tape or disk
Automatic
Verify that
the backups
are
successful
and are
transferred
to other
media every
month and
before and
after each
upgrade.
The backup
media are
unfixed.
RBI
Every month;
before and
after each
upgrade
Tape or disk
Manual
iWeb
Every month;
before and
after each
upgrade
Tape or disk
Automatic or
manual
DCCP
rocxy
Before and
after each
upgrade
DCCProxy_
module_con
fig.txt
Tape or disk
Manual
DiamBaseC
onfig.xml
icdcomm.cf
g
filesync.cfg
NMAdptCfg
.xml
node.cfg
Backup Strategy: CDRs

The CDRs are backed up in the CDR backup directories on the CBP and BMP automatically.
You can configure scripts to clear CDRs from the bak directory automatically. You can also
back up the CDRs on the RBI directly.
In addition, you can back up the CDRs on the RBI to back up the CDRs of the NEs that are
associated with the RBI. The strategy is as follows:
Issue 01 (2010-09-29)

2-17
HUAWEI CBS
2 Backup Strategies
2-18
Backup frequency: every week
Backup medium: tape or disk
Execution mode: manual
Backup retention duration: three months or half a year
Remarks: Perform the backup only on the active node.

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Daily Maintenance
About This Chapter

This topic describes the maintenance items that need to be performed every day. The
maintenance items are the most important. To improve the efficiency, it is recommended that
the tools should be used to perform the maintenance items.
3.1 I2000 Alarm Handling
Access Browse Current Fault Alarms by Status on the I2000 client to learn the status in real
time.
3.2 I2000 Performance Monitoring
Through I2000 performance monitoring, you can check the performance index value of the NE
in real time, and the performance is displayed in column chart or line chart.
3.3 Monitoring the CBS Through the SMAP
The monitoring system monitors the running status of an NE such as the CBP, Billing, AR, and
DC, monitors the service handling statuses through the Invoicing function, and displays the
service handling statuses in histogram, curve, or pie chart, which helps users to learn about the
service running statuses in time.
3.4 Reconciling the CBS Through the SMAP
The reconciliation function is mainly used to display reconciliation information between NEs
such as the CBP, Billing, Invoicing, AR, and DC. The running statuses of system services can
be displayed dynamically in real time, helping users to learn about the system running status.
3.5 Maintenance Tasks of the Operating Systems
This topic describes the maintenance tasks of the operating systems.
3.6 Maintenance Tasks of the Database
This topic describes the maintenance tasks of the database.
3.7 Maintenance Tasks of the Applications
This topic describes the maintenance tasks of the applications.
Issue 01 (2010-09-29)

3-1
HUAWEI CBS
3 Daily Maintenance
3.1 I2000 Alarm Handling

Access Browse Current Fault Alarms by Status on the I2000 client to learn the status in real
time.
Prerequisite
l
The connection of the I2000 client and the NE is normal.
The I2000 is equipped with the audio or alarm box. In this manner, alarms can be found
through audio and visual prompt.
Context
None.
Procedure
Step 1 Choose Fault > Browse Current Fault Alarms by Status on the I2000 client or click
the toolbar. You can view alarms in four states, as shown in Figure 3-1.
on
Figure 3-1 Browse Current Fault Alarms by Status
Step 2 Check detailed information about alarms in Unacknowledged and uncleare to locate the
problem.
l
3-2
If an alarm needs to be processed, right-click the alarm and choose Acknowledge. The alarm
is moved to Acknowledged and uncleared.
Issue 01 (2010-09-29)
HUAWEI CBS
l
3 Daily Maintenance
If an alarm does not exist or does not need to be processed, right-click the alarm and choose
Clear. The alarm is moved to Acknowledged and cleared.
Step 3 Choose Fault > Current Fault Alarms and click the hyperlink in Process Advice. The
maintenance engineers can open Alarm Reference Help, as shown in Figure 3-2.
Figure 3-2 Viewing alarm handling suggestions
Step 4 After the maintenance engineers drafts and implements the alarm processing scheme, the alarm
is cleared.
Step 5 Double-click the cleared alarm, and the Detail Information window is displayed. Click
Modify in the lower part of the Alarm Memo text box, enter the alarm maintenance experience,
and click Close.
----End
Example
None.
Exception Handling
None.
3.2 I2000 Performance Monitoring

Through I2000 performance monitoring, you can check the performance index value of the NE
in real time, and the performance is displayed in column chart or line chart.
Issue 01 (2010-09-29)

3-3
HUAWEI CBS
3 Daily Maintenance
Prerequisite
l
The connection between the I2000 client and the NE is normal.
The performance monitoring task is created during installation and commissioning.
Context
Certain important KPI indexes of the CBS need to be monitored in real time. The maintenance
engineers can check the statistics through reports. In addition, they can learn the trend of KPI
indexes through performance monitoring. Table 3-1 shows the important KPI indexes of the
CBS.
Table 3-1 KPI indexes of the I2000
N
o
Name
Index Definition
Statistics
Range
Statistics
Period
Default
Alarm
Value
The rate of
successful
calling
The index indicates

the ratio of the
number of
successful calls to
the total number of
calls in a period.
Number of
successful
calls/Number
of call
attempts
Five minutes
Less than
95%
The rate of
successful
recharging
The index indicates

the ratio of the
number of
successful recharges
to the total number
of recharges in a
period.
Number of
successful
recharges/
Number of
recharges
Five minutes
Less than
95%
The rate of
offline CDR
The index indicates

the ratio of the
number of SMS and
voice offline CDRs
to the total number
of CDRs in a period.
Number of
passby SMS
CDRs +
Number of
passby call
CDRs/
Number of
passby CDRs
+ Number of
normal CDRs
Five minutes
Greater than
5%
NOTE
The I2000 can monitor other items, for example, the usage of the file system space, the memory usage,
and the CPU load. It is recommended that you should check the items in the CDR pear hours.
Procedure
Step 1 Choose Performance > Performance Monitoring.
3-4

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Step 2 Choose the Monitoring Task Management tab. The I2000 lists all the created performance
monitoring tasks, as shown in Figure 3-3.
Figure 3-3 List of performance monitoring tasks
Step 3 After selecting a monitoring task, choose the Monitoring Result Display tab. You can obtain
the trend of the performance change through the column chart or line chart, as shown in Figure
3-4.
Figure 3-4 Monitoring result
Step 4 The maintenance engineers need to check whether the trend of the data is abnormal according
to different performance monitoring tasks.
Issue 01 (2010-09-29)

3-5
HUAWEI CBS
3 Daily Maintenance
l
For the task of "the rate of successful calling", if the data curve is in the trend of decreasing
and the ratio of the number of successful calls to the total number of calls is less than 95%,
note the task and locate the problem.
For the task of "the rate of successful recharging", if the data curve is in the trend of decreasing
and the ratio of the number of successful recharges to the total number of recharges is less
than 95%, note the task and locate the problem.
For the task of "the rate of offline CDR", if the data curve is in the trend of increasing and
the ratio of the number of SMS and voice offline CDRs to the total number of CDRs is greater
than 5%, note the task and locate the problem.
----End
Example
None.
Exception Handling
If performance monitoring tasks are created, the maintenance engineers receive alarm messages
when the performance index is abnormal. Then, they can solve the problem in time. To know
how to process alarms on the I2000, see 3.1 I2000 Alarm Handling.
3.3 Monitoring the CBS Through the SMAP

The monitoring system monitors the running status of an NE such as the CBP, Billing, AR, and
DC, monitors the service handling statuses through the Invoicing function, and displays the
service handling statuses in histogram, curve, or pie chart, which helps users to learn about the
service running statuses in time.
Prerequisite
l
Each NE in the system is connected normally.
The NE data collected by the system is written into the OM central database.
Context
The monitoring interface focuses on the application running status and load status. The
monitoring interface consists of two layers of view.
l
The first-layer view is called monitoring layer 0. It collects the status data of each NE in
the system and displays the real-time running status of the entire system.
The second-layer view is called monitoring layer 1. It displays the service running status
of an NE and current data of each node.
Table 3-2 describes the detailed alarm information on an NE on the monitoring layer 0.
3-6

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Table 3-2 Description of icons at monitoring layer 0

Icon
Description
Alarm Status
Current session status on the

CBP.
The green area indicates normal.
The yellow area indicates an

alarm.
The red area indicates a major

alarm.
Green indicates normal.
Yellow indicates an alarm.
Red indicates a major alarm.
Total number of subscribers

who are settled daily on the
CBP.
The green area indicates the

number of subscribers or accounts
that are processed normally.
Total number of subscribers

for whom the Billing
performs bill run.
The red area indicates the number

of subscribers or accounts that fail
to be processed.
The gray area indicates the

number of subscribers or accounts
that are not processed.
This icon is described as

follows:
l
CDR stacking status.
Number of suspended
subscribers.
This icon is described as

follows:
l
Total number of accounts

whose bills are formatted.
Total number of accounts that

are deregistered by the AR.
Procedure
Step 1 Log in to the SMAP.
Step 2 Choose Monitor > Present > Index.
Step 3 The system displays monitoring layer 0, as shown in Figure 3-5. Maintenance engineers can
determine whether a service progress runs normally by checking the color of an icon at this layer.
Issue 01 (2010-09-29)

3-7
HUAWEI CBS
3 Daily Maintenance
Figure 3-5 Monitoring layer 0
Step 4 Double-click an NE monitoring icon at monitoring layer 0 to access monitoring layer 1 of this
NE. For example, double-click AR monitoring icon to access AR monitoring layer 1, as shown
in Figure 3-6. Maintenance engineers can monitor the current data and detailed information
about a node.
Figure 3-6 AR monitoring layer 1
3-8

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Step 5 Click
at the upper right corner at monitoring layer 0 to access the page for
configuring data such as alarm threshold and CDR stacking alarm threshold, as shown in Figure
3-7.
Figure 3-7 Configuration page at monitoring layer 0
----End
Example
None.
Exception Handling
Maintenance engineers can handle an alarm or error according to the following thoughts when
finding the alarm or error prompt on the monitoring interface:
Handle a CAPS alarm according to the exception handling of the Evaluating the Traffic on
the SCP.
Handle an error CDR according to the exception handling of the Checking the Offline CDR
on the CBP.
When the bill run data generated by the Billing is incorrect, exception information is recorded
in the corresponding task log. Maintenance engineers can rectify the exception according to the
exception information. To rectify the exception, do as follows:
1.
Log in to the Billing.
2.
Enable the log function by running setval -l debug.
Issue 01 (2010-09-29)

3-9
HUAWEI CBS
3 Daily Maintenance
3.
Access the log path ${HOME}/log/debug/bmp_debug.log.
When the deregistration data generated by the AR is incorrect, exception information is recorded
in the corresponding task log. Maintenance engineers can rectify the exception according to the
exception information. To rectify the exception, do as follows:
1.
Log in to the server where the AR is located.
2.
Enable the log function by running setval -l debug.
3.
Access the log path ${HOME}/log/debug/bmp_debug.log.
If an error occurs when the Invoicing bills are formatted, maintenance engineers need to try to
format the bills again.
If other exceptions occur, contact Huawei engineers.
3.4 Reconciling the CBS Through the SMAP

The reconciliation function is mainly used to display reconciliation information between NEs
such as the CBP, Billing, Invoicing, AR, and DC. The running statuses of system services can
be displayed dynamically in real time, helping users to learn about the system running status.
Prerequisite
l
Each NE in the system is connected normally.
The NE data collected by the system is written into the OM central database.
Context
Reconciliation can be classified into the following types according to involved NEs:
l
Reconciling the number of CDRs between the CBP and the Billing, that is, checking
whether the number of CDRs generated by the CBP is the same as that of the CDRs received
by the Billing
Reconciling the number of bills between the Billing and the Invoicing, that is, checking
whether the number of bills generated by the Billing is the same as that of bills processed
by the Invoicing
Reconciling the number of accounts between the Billing and the AR, that is, checking
whether the number of accounts on which the Billing performs bill run is the same as that
of accounts deregistered by the AR
Reconciling the number of transactions between the DC and the AR, that is, checking
whether the number of transactions performed by the AR is the same as that of the
transactions processed by the DC
Reconciling the number of transactions between the CBP and the AR, that is, checking
whether the number of transactions performed by the AR is the same as that of the
transactions received by the CBP
NOTE
In addition to the inter-NE reconciliation function, the CBP has the intra-NE reconciliation function to reconcile
the number of online CDRs. The reconciliation formula is as follows: Number of messages + Number of split
messages = Number of charging CDRs + Number of error CDRs + Number of CDRs for subscribers not charged.
The reconciliation page consists of the following parts:

3-10

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
NE reconciliation in the yellow box. Data on these NEs is reconciled by life cycle; that is,
data changes according to the bill cycle selected in the drop-down list box.
NE reconciliation out of the yellow box. Data on these NEs is reconciled by date; that is,
data changes according to the displayed date.
Procedure
Step 2 Choose Monitor > Present > Index.
Step 3 The system displays monitoring layer 0.
Step 4 Click
in Figure 3-8.
at the upper left corner to access the reconciliation interface, as shown
Figure 3-8 Reconciliation interface
Step 5 Select a date or bill cycle to view the reconciled data.

at the upper right corner on the reconciliation page to access the configuration
Step 6 Click
page, as shown in Figure 3-9. You can configure the alarm thresholds for inter-NE
reconciliation.
Issue 01 (2010-09-29)

3-11
HUAWEI CBS
3 Daily Maintenance
Figure 3-9 Configuration page of the reconciliation interface
----End
Example
None.
Exception Handling
If
is displayed on the reconciliation monitoring interface, it indicates that the
data of the reconciled parties is different. Ask maintenance engineers to check the running
statuses of services on each NE.
3.5 Maintenance Tasks of the Operating Systems

This topic describes the maintenance tasks of the operating systems.
3.5.1 Checking the Space Usage of File Systems (ATAE)
This task enables you to check the space usage of file systems. High space usage of the file
systems affects the running of the system and applications.
3.5.2 Checking the Space Usage of File Systems (HP)
3-12

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
3.5.3 Checking the Space Usage of File Systems (IBM)

3.5.4 Checking the Usage of the File System Space on the PC Server
This maintenance item helps you monitor the usage of the disk space to prevent the system or
the application running fault that is caused by great disk space usage.
3.5.5 Checking Memory Usage (ATAE)
This task enables you to check memory usage. Insufficient memory causes poor system
performance, and even process start failure or service interruption.
3.5.6 Checking the Size of Free Memory (HP)
This task enables you to check the size of free memory. Insufficient memory causes poor system
performance and even service interruption.
3.5.7 Checking Memory Usage (IBM)
3.5.8 Checking the Memory Usage on the PC Server
This topic describes how to check the memory usage on the PC server. The insufficient memory
affects the performance, and even the failure to start processes or interruption of services.
3.5.9 Checking the CPU Usage (ATAE)
This task enables you to check the CPU usage. High CPU usage causes call restriction and even
service interruption.
3.5.10 Checking the CPU Usage (HP)
3.5.11 Checking the CPU Usage (IBM)
This task enables you to check the CPU usage. High CPU usage causes service exceptions and
even service interruption.
3.5.12 Checking the CPU Load on the PC Server
This topic describes how to check the CPU load on the PC server. If the CPU load is very great,
the call is limited and even the service is interrupted.
3.5.13 Checking the Status of Network Adapters (ATAE)
This task enables you to check the status of network adapters. Abnormal network adapters causes
service failure (such as communication interruption), and even service interruption.
3.5.14 Checking the Status of Network Adapters (HP)
service failure (such as call restriction), and even service interruption.
3.5.15 Checking the Status of Network Adapters (IBM)
This task enables you to check the status of network adapters. Abnormal network adapters cause
3.5.16 Checking the Status of the Network Adapter on the PC Server
If the status of the network adapter is abnormal, service abnormality, call limit, or service
interruption may occur. This task is performed to check detailed information about the status of
the network adapter.
3.5.17 Checking the Status of the Two-Node Cluster (ATAE)
Issue 01 (2010-09-29)

3-13
HUAWEI CBS
3 Daily Maintenance
This task is performed to check the status of the two-node cluster. If the status of the two-node
cluster is abnormal, serious security problems may occur in the system, and the switchover of
the two-node cluster may fail or the system is abnormal after the switchover.
3.5.18 Checking the Status of a Two-Node Cluster (HP)
This task enables you to check the status of a two-node cluster. If the status of a two-node cluster
is abnormal, serious security problems may occur in the system.
3.5.19 Checking the Status of a Two-Node Cluster (IBM)
3.5.20 Checking the Status of the Two-Node Cluster on the PC Server
This topic describes how to check the status of the two-node cluster. If the two-node cluster runs
abnormally, there is a great potential risk on the security of the system. The two-node cluster
may fail to be switched or the system is abnormal after the switchover.
3.5.21 Checking Core Files
This task enables you to check whether core files are generated. If core files are generated, critical
system faults may occur.
3.5.1 Checking the Space Usage of File Systems (ATAE)

Reference Standard
The space usage rate of each file system (especially /, /tmp, /var, ${TELLIN_DIR}, and /
opt) is less than 80%.
l
The usage rate of / is less than 80%.
The available space of /tmp is more than 500 MB.
The available space of /var is more than 500 MB.
The available space of /home is more than 500 MB.
The available space of /opt is more than 800 MB.
Procedure
Step 1 Log in to a server as the root user.
Step 2 Check disk space.
# df -h
The information similar to the following is displayed:
Filesystem
/dev/sda2
tmpfs
/dev/sda3
Size
46G
4.0G
15G
Used Avail Use% Mounted on

40G 5.3G 89% /
0 4.0G
0% /tmp
9.6G 5.5G 64% /home
The values of Use% indicate the space usage of the file systems.
----End
3-14

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Exception Handling
If the space usage of each file system exceeds 80%, you need to clean the disk space. Before
deleting files, make sure that the files are unnecessary. If any important file is deleted by mistake,
the system cannot run properly.
The following describes file systems according to their types:
l
File systems of an operating system

For example, /, /tmp, /var, /home, and /opt. If the space usage of the file systems of this
type is high, exercise caution when deleting files. It is recommended that you contact
Huawei engineers before deleting files.
You can delete temporary files in /var/tmp and core files.
File systems of applications

The general causes for high space usage of file systems are as follows:
Logs increase rapidly, but cannot be backed up or deleted in time.
The temporary files that are generated during the installation and running of the system
are not deleted in time.
3.5.2 Checking the Space Usage of File Systems (HP)

Reference Standard
The space usage rate of each file system (especially /, /tmp, /var, and /opt) is less than 80%.
l
Procedure
Step 1 Log in to the active node and standby node as the root user.
Step 2 Check the space usage of file systems.
# bdf
Filesystem
on
/dev/vg00/lvol3
/dev/vg00/lvol1
/dev/vg00/lvol8
/dev/vg00/lvol7
/dev/vg00/lvol4
/dev/vg00/lvol6
/dev/vg00/lvol5
kbytes
143360
83733
1048576
1069056
1024000
2187264
2097152
used
59945
30705
852155
761592
10893
1946813
841762
avail
78225
44654
195158
288301
950105
225572
1179942
%used
Mounted
43%
41%
81%
73%
1%
90%
42%
/
/stand
/var
/usr
/tmp
/opt
/home
The values of %Used indicate the space usage of the file systems.
----End
Issue 01 (2010-09-29)

3-15
HUAWEI CBS
3 Daily Maintenance
Exception Handling
If the space usage of the file systems does not meet the standards, delete unnecessary files to
release the space of the file systems.
CAUTION
Before deleting files, make sure that the files are unnecessary.
3.5.3 Checking the Space Usage of File Systems (IBM)

Reference Standard
The space usage rate of each file system (especially /, /tmp, /var, and /opt) is less than 80%.
l
Procedure
Step 2 Check the space usage of file systems.
# df -m
Filesystem
/dev/hd4
/dev/hd2
/dev/hd9var
/dev/hd3
/dev/hd1
/proc
/dev/hd10opt
MB blocks
2048.00
1344.00
1024.00
4096.00
10240.00
2048.00
Free %Used
1902.57
8%
110.56
92%
953.20
7%
3963.58
4%
6424.26
38%
1960.33
5%
Iused %Iused Mounted on

2170
1% /
30933
9% /usr
482
1% /var
77
1% /tmp
1100
1% /home
- /proc
560
1% /opt
The values of %Iused indicate the space usage of the file systems.
----End
Exception Handling
If the space usage of the file systems does not meet the standards, delete unnecessary files to
release the space of the file systems.
3-16

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
CAUTION
Before deleting files, make sure that the files are unnecessary.
3.5.4 Checking the Usage of the File System Space on the PC Server
This maintenance item helps you monitor the usage of the disk space to prevent the system or
the application running fault that is caused by great disk space usage.
Reference Standard
The usage of each file system space must be less than 80%. Note the usage of /, /tmp, /var, $
{TELLIN_DIR}, and /opt file systems.
NOTE
${TELLIN_DIR} is the installation directory of the application system.

l
The usage of the / directory is less than 80%.
The available space of the /tmp directory must be greater than 500 MB.
The available space of the /var directory must be greater than 500 MB.
The available space of the ${TELLIN_DIR} (directory where the application system is)
directory must be greater than 800 MB.
The available space of the /opt directory must be greater than 800 MB.
Precaution
You can use the following two methods to check the space usages of file systems.
l
Through I2000
Through UNIX commands
The following procedure takes the second method as an example.
Procedure
Step 1 Log in as the root user.
Step 2 Check the disk space.
# df -k
The unit of the file system space is KB.
----End
Exception Handling
When the usage of each file system space is greater than 80%, you need to clean the disk space.
Before deleting a file, check whether the file can be deleted. If a file is deleted incorrectly, the
system may not run.
The following describes deletion of files:
Issue 01 (2010-09-29)

3-17
HUAWEI CBS
3 Daily Maintenance
l
File system of the operating system

When the usage of the file system such as /, /tmp, /var, and /opt is great, do not delete files
randomly. You are recommended to contact server engineers.
You need to clean core files and temporary files in /var/tmp.
Application file system

When the usage of the file system such as ${TELLIN_DIR} is great, the disk space is great
due to the following reasons:
The log is increasing rapidly and is not backed up in time.
The temporary files during installation are not deleted in time, for example, $
{TELLIN_DIR}/tmp.
The CDR is not backed up in time.
3.5.5 Checking Memory Usage (ATAE)

Reference Standard
The idle memory is equal to or more than 10% of the total memory.
Procedure
Step 2 Check the status of the memory.
# free -t
total
Mem:
7991
-/+ buffers/cache:
Swap:
2055
used
6798
551
0
free
1193
7440
2055
shared
0
buffers
255
cached
5990
In the preceding information:

l
The values in the Mem line indicate the usage of the physical memory:
The total size of the physical memory is 7991 KB.
The size of the used physical memory is 6798 KB.
The size of the free physical memory is 1193 KB.
The values in the Swap line indicate the usage of the swap space:
The total size of the swap space is 2055 KB.
The size of the used swap space is 0 KB.
The size of the free swap space is 2055 KB.
----End
Exception Handling
If the check result does not meet the check standard, contact Huawei engineers.
3-18

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
3.5.6 Checking the Size of Free Memory (HP)

This task enables you to check the size of free memory. Insufficient memory causes poor system
performance and even service interruption.
Reference Standard
The idle memory is equal to or more than 10% of the total memory.
Procedure
Step 2 Check the size of free memory.
# top
Memory: 420380K (211660K) real, 673084K (373396K) virtual, 14214760K free
The value of free indicates the size of free memory.

Step 3 Check the size of physical memory.
# dmesg | grep Physical
Physical: 16746680 Kbytes, lockable: 13213884 Kbytes, available: 15232700 Kbytes
The value of Physical indicates the size of physical memory.

----End
Exception Handling
3.5.7 Checking Memory Usage (IBM)

Reference Standard
When the memory usage remains unchanged or increases continuously, it indicates that the
memory usage is not proper.
Procedure
Step 2 Check the size of the memory.
# svmon
Issue 01 (2010-09-29)

3-19
HUAWEI CBS
3 Daily Maintenance
size
524277
inuse
428294
free
95983
pin virtual
34138 136745
NOTE
The units of the displayed values are 4 KB.
The displayed result is described as follows:

l
size: size of the physical memory
inuse: size of the used physical memory
free: size of the free physical memory
pin: size of the physical memory that cannot be converted into the swap space
virtual: size of the virtual memory
----End
Exception Handling
3.5.8 Checking the Memory Usage on the PC Server

This topic describes how to check the memory usage on the PC server. The insufficient memory
affects the performance, and even the failure to start processes or interruption of services.
Reference Standard
Ensure that the idle memory is not less than 30% of the total memory.
Precaution
None.
Procedure
Step 2 Check the size of the idle memory.
# free -t
total
used
Mem:
4147836
-/+ buffers/cache:
Swap:
1048552
Total:
5196388
free
4086324
1086620
0
4086324
shared
61512
3061216
1048552
1110064
buffers
0
cached
140660
2859044
The preceding information indicates that the total memory of the system is 5196388 KB and the
available memory is 1110064 KB.
----End
Exception Handling
The memory usage is great in the following situations:
3-20

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
The memory leakage occurs on the memory database used by the database server.
The memory cannot be released because the automatic machine is suspended.
The memory usage varies according to the application; thus, you need to analyze the memory
usage according to the situation.
To obtain the average memory usage, use corresponding functions of the I2000.
3.5.9 Checking the CPU Usage (ATAE)

Reference Standard
l
The average idle rate of the CPU is equal to or more than 25%.
The CPU usage rate for each process is less than or equal to 70%. Otherwise, record the
process name and the time when the CPU usage rate for the process is more than 70%.
Procedure
Step 2 Check the CPU usage.
# top
Cpu(s):
0.1% us,
0.0% sy,
0.0% ni, 99.9% id,
0.0% wa,
0.0% hi,
0.0% si

l
us: CPU usage of user processes
sy: CPU usage of system processes
id: idle CPU rate
wa: wait time of the CPU, which is caused by low I/O speeds
----End
Exception Handling
If the check result does not meet the check standard, perform the following operations:
Step 1 If the CPU usage does not meet the check standard, you need to run the top command to check
whether all the process run properly. If any process runs abnormally, determine whether the
process is necessary. If the process is not necessary, end the process.
Step 2 If the CPU idle rate is less than 25%, it indicates that system hardware performance is poor and
capability expansion is required.
----End
Issue 01 (2010-09-29)

3-21
HUAWEI CBS
3 Daily Maintenance
3.5.10 Checking the CPU Usage (HP)

Reference Standard
l
The CPU usage rate for a single process is less than or equal to 70%.
Procedure
# top
Cpu states:
CPU
LOAD
USER
NICE
SYS
IDLE BLOCK SWAIT
INTR
SSYS
0
0.01
0.0%
0.0%
0.2% 99.8%
0.0%
0.0%
0.0%
0.0%
1
0.07
0.0%
0.0%
0.0% 100.0%
0.0%
0.0%
0.0%
0.0%
2
0.00
0.0%
0.0%
0.0% 100.0%
0.0%
0.0%
0.0%
0.0%
3
0.06
0.0%
0.0%
0.2% 99.8%
0.0%
0.0%
0.0%
0.0%
------ ----- ----- ----- ----- ----- ----- ----- ----avg
0.03
0.0%
0.0%
0.2% 99.8%
0.0%
0.0%
0.0%
0.0%
Memory: 327792K (126964K) real, 515052K (206280K) virtual, 745104K free
TTY
PID USERNAME
?
48 root
?
1420 root
?
4463 root
?
1804 root
?
1413 root
pts/tb 15782 root
?
512 root
?
1640 root
?
38 root
?
966 root
?
2158 root
?
19 root
ksyncer_daemon
?
1 root
?
40 root
?
1296 root
?
0 root
?
2 root
?
3 root
?
4 root
?
10 root
?
11 root
?
12 root
?
13 root
?
14 root
?
15 root
?
16 root
?
17 root
?
20 root
?
23 root
PRI
152
152
-27
152
152
178
152
152
152
152
154
191
NI
20
20
20
20
20
20
20
20
20
20
10
20
152
191
152
127
128
128
128
152
152
147
147
147
147
147
147
133
100
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
SIZE
RES STATE
3024K 2688K run
162M 56920K run
47396K 39576K run
113M 16168K run
25416K 3628K run
10868K 1000K run
7740K 1948K run
23820K 2856K run
216K
192K run
11120K 1356K run
8604K 1180K sleep
144K
128K run
1960K
144K
9304K
72K
72K
72K
72K
72K
288K
72K
72K
72K
72K
72K
72K
72K
72K
564K
128K
1420K
64K
64K
64K
64K
64K
256K
64K
64K
64K
64K
64K
64K
64K
64K
TIME %WCPU
25:43 0.33
4:08 0.22
14:47 0.18
1:55 0.14
0:23 0.12
0:00 0.13
1:37 0.10
0:22 0.08
8:20 0.06
0:04 0.06
20:07 0.05
2:07 0.04
run
run
run
sleep
sleep
sleep
sleep
sleep
run
sleep
sleep
sleep
sleep
sleep
sleep
sleep
sleep
0:27
0:01
0:00
0:48
0:16
2:11
0:11
4:30
0:02
0:01
0:01
0:01
0:02
0:01
0:01
0:04
0:28
0.04
0.04
0.04
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
Page# 1/5
%CPU
0.33
0.21
0.18
0.14
0.12
0.10
0.10
0.08
0.06
0.06
0.05
0.04
COMMAND
vxfsd
cimserver
cmcld
vxsvc
rpcd
top
utmpd
swagentd
schedcpu
automountd
psmctd
0.04
0.04
0.04
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
0.02
init
cmcd
snmpdm
swapper
vhand
statdaemon
unhashdaemon
nfsktcpd
autofskd
lvmkd
lvmkd
lvmkd
lvmkd
lvmkd
lvmkd
lvmdevd
supsched

3-22

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
LOAD: current CPU usage
USER: CPU usage of user processes
SYS: CPU usage of system processes
IDLE: CPU idle rate
%CPU: CPU usage of a single process
----End
Exception Handling
If the check result does not meet the check standard, resolve the problem by using the following
methods:
Step 1 If the CPU usage does not meet the check standard, you need to run the top command to check
whether processes run abnormally.
Step 2 If the CPU idle rate is less than 25% and all the processes run properly, it indicates that system
hardware performance is poor and capability expansion is required.
----End
3.5.11 Checking the CPU Usage (IBM)

This task enables you to check the CPU usage. High CPU usage causes service exceptions and
even service interruption.
Reference Standard
l
The CPU usage rate for a single process is less than or equal to 70%.
Procedure
# vmstat 1 10
kthr
----r b
1 1
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
0 0
memory
page
faults
cpu
----------- ------------------------ ------------ ----------avm
fre re pi po fr
sr cy in
sy cs us sy id wa pc
ec
84231 912032
0
0
0
0
0
0 226
49 35 0 0 99 0 0.01
7.5
84235 912029
0
0
0
0
0
0 238 2236 70 0 1 98 1 0.01
6.5
84235 912029
0
0
0
0
0
0 237 2080 32 0 0 99 0 0.01
10.3
84235 912029
0
0
0
0
0
0 235 2139 48 0 0 99 0 0.01
4.6
84235 912029
0
0
0
0
0
0 229 2080 28 0 0 99 0 0.01
8.1
84235 912029
0
0
0
0
0
0 246 2140 48 0 0 99 0 0.01
5.6
84235 912029
0
0
0
0
0
0 235 2080 30 0 0 99 0 0.01
4.9
84235 912029
0
0
0
0
0
0 238 2141 50 0 0 99 0 0.01
5.4
84235 912029
0
0
0
0
0
0 243 2080 27 0 0 99 0 0.01
4.5
84235 912029
0
0
0
0
0
0 239 2139 46 0 0 99 0 0.01
7.4

Issue 01 (2010-09-29)

3-23
HUAWEI CBS
3 Daily Maintenance
l
us: CPU usage of user processes
sy: CPU usage of system processes
id: CPU idle rate
wa: wait time of the CPU, which is caused by low I/O speeds.
# topas
Name
topas
dtscreen
dtfile
syncd
gil
xmgc
aixmibd
PID
16636
21034
7590
5750
2838
2064
46220
CPU%
0.0
0.0
0.0
0.0
0.0
0.0
0.0
PgSp
1.3
0.5
1.7
0.5
0.1
0.0
0.6
Owner
root
root
root
root
root
root
root
In the preceding information, CPU% indicates the CPU usage of a single process.
----End
Exception Handling
Step 1 If the CPU usage does not meet the check standard, you need to run the topas command to check
whether processes run abnormally.
Step 2 If the CPU idle rate is less than 25% and all the processes run properly, it indicates that system
hardware performance is poor and capability expansion is required.
----End
3.5.12 Checking the CPU Load on the PC Server

This topic describes how to check the CPU load on the PC server. If the CPU load is very great,
the call is limited and even the service is interrupted.
Reference Standard
The average idle CPU usage cannot be less than 25%.
Precaution
None.
Procedure
# top
Cpu(s):
3-24
0.1% us,
0.0% sy,
0.0% ni, 99.9% id,
0.0% wa,

0.0% hi,
0.0% si
Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
You need to pay attention to the following parameters:

l
us indicates the CPU usage of the user process.
sy indicates the CPU usage of the system process.
id indicates the idle CPU usage.
wa indicates the CPU usage of I/O waiting. The I/O waiting time is caused by the low rate
of I/O.
----End
Exception Handling
If the check result does not conform to the check standard, do as follows:
Step 1 If the CPU usage does not conform to the check standard, you need to run the top command to
check whether abnormal progresses are running.
Step 2 If the average CPU idle rate is lower than 25%, and no abnormal process exists in the system,
the hardware resources of the system are insufficient. You are then required to expand the
hardware resources.
----End
3.5.13 Checking the Status of Network Adapters (ATAE)

service failure (such as communication interruption), and even service interruption.
Reference Standard
The following conditions are met:
l
The network adapters on the active node and standby node are in the RUNNING state.
The transmission rate of each network adapter on the active node and standby node is 100
Mbit/s or 1000 Mbit/s in full-duplex mode, and the working mode is auto-negotiation.
Procedure
Step 2 Check the status of all network adapters.
# ifconfig -a
eth0
Link encap:Ethernet HWaddr 00:18:82:35:05:4E

inet addr:192.168.0.185 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::218:82ff:fe35:54e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2861537 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:238299594 (227.2 Mb) TX bytes:748 (748.0 b)
Interrupt:169
eth3
Link encap:Ethernet HWaddr 00:18:82:35:05:4C

inet addr:10.164.124.185 Bcast:10.164.124.255
Issue 01 (2010-09-29)

Mask:255.255.255.0
3-25
HUAWEI CBS
3 Daily Maintenance
inet6 addr: fe80::218:82ff:fe35:54c/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX bytes:34352805348 (32761.3 Mb) TX bytes:8704301796 (8301.0 Mb)
Base address:0xcf00 Memory:fdce0000-fdd00000
lo
Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX bytes:246036 (240.2 Kb) TX bytes:246036 (240.2 Kb)
Step 3 Check the transmission rates and working modes of the network adapters.
For example, you can run the following command to check the transmission rate and working
mode of the eth0 network adapter:
# ethtool eth0
Settings for eth0:
Supported ports: [ MII ]
Supported link modes:
10baseT/Half 10baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes
According to the preceding information, the transmission rate of the network adapter is 1000
Mbit/s in full-duplex mode, and the working mode is auto-negotiation.
----End
Exception Handling
If the status of the network adapters is abnormal, or the transmission rates or working modes of
network adapters are incorrect, contact Huawei datacom engineers to check switch
configurations.
3.5.14 Checking the Status of Network Adapters (HP)

3-26

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Reference Standard
l
The software is in the CLAIMED state.
The hardware is in the UP state.
The transmission rate is 100 Mbit/s or 1000 Mbit/s.
The communication mode is full-duplex.
The working mode is auto-negotiation.
Procedure
Step 2 Check the status of the software of the network adapters.
# ioscan -fnkC lan
Class
I H/W Path
Driver
S/W State
H/W Type
Description
========================================================================
lan
0 0/1/2/0
iether
CLAIMED
INTERFACE
HP PCI-X 1000Base-T
Dual-port Built-in
lan
1 0/1/2/1
iether
CLAIMED
INTERFACE
HP PCI-X 1000Base-T
Dual-port Built-in
lan
2 0/2/1/0/6/0 igelan
CLAIMED
INTERFACE
HP A9784-60002 PCI/PCIX 1000Base-T FC/GigE Combo Adapter
Step 3 Check the status of the hardware of the network adapters.

# lanscan
Hardware
Path
0/1/2/0
0/1/2/1
0/2/1/0/6/0
Station
Address
0x0018FE28A00E
0x0018FE28A00F
0x0016353E84CF
Crd
In#
0
1
2
Hdw
State
UP
UP
UP
Net-Interface
NamePPA
lan0 snap0
lan1 snap1
lan2 snap2
NM
ID
1
2
3
MAC
Type
ETHER
ETHER
ETHER
HP-DLPI
Support
Yes
Yes
Yes
DLPI
Mjr#
119
119
119
Step 4 Check the transmission rate, communication mode, and working mode of a network adapter.
# lanadmin -x Network adapter No.
For example, run the following command:
# lanadmin -x lan0
Speed = 1000 Full-Duplex.
Autonegotiation = On.

l
1000 indicates that the transmission rate of the network adapter is 1000 Mbit/s.
Full-Duplex indicates that the communication mode of the network adapter is full-duplex.
Autonegotiation indicates that the working mode of the network adapter is auto-negotiation.
----End
Issue 01 (2010-09-29)

3-27
HUAWEI CBS
3 Daily Maintenance
Exception Handling
l
If the software or hardware of a network adapter does not work properly, contact HP
engineers.
If the transmission rate, communication mode, or working mode of a network adapter is

incorrect, you can set the incorrect parameter again provided that services are not affected.
# lanadmin -X auto_on Network adapter No.
For example, run the following command:
# lanadmin -X auto_on 0
If the setting is successful, the information similar to the following is displayed:
WARNING: anincorrect setting couldcause serious network problems!!!
Driver is attempting tosetthenewspeed
Reset will take approximately 11 seconds
3.5.15 Checking the Status of Network Adapters (IBM)

This task enables you to check the status of network adapters. Abnormal network adapters cause
Reference Standard
In normal cases, make sure that:
l
The network adapters on the active node and standby node are available.
The transmission rate of each network adapter on the active node and standby node is 100
Mbit/s or 1000 Mbit/s in full-duplex mode, and the working mode is auto-negotiation.
Procedure
Step 2 Check the status of the network adapters.
# lsdev -Cc adapter | grep ent
ent0
ent1
ent2
ent3
Available
Available
Available
Available
05-08
05-09
07-08
07-09
2-Port
2-Port
2-Port
2-Port
10/100/1000
10/100/1000
10/100/1000
10/100/1000
Base-TX
Base-TX
Base-TX
Base-TX
PCI-X
PCI-X
PCI-X
PCI-X
Adapter
Adapter
Adapter
Adapter
(14108902)
(14108902)
(14108902)
(14108902)
Step 3 Check the transmission rate and working mode of a network adapter.
# entstat -dDevice No. | grep Speed
Assume that the value of Device No. is ent0.
Media Speed Selected: Auto negotiation
Media Speed Running: 1000 Mbps Full Duplex
----End
3-28

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Exception Handling
l
If the network adapter is in the abnormal state, contact IBM engineers.
If the transmission rate or working mode is incorrect, use the SMIT tool to change the
transmission rate or working mode provided that services are not affected.
# smit chgenet
Select a network adapter whose attributes need to be modified. On the screen that appears,
change the value of Media Speed as required.
Change / Show Characteristics of an Ethernet Adapter
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
Ethernet Adapter
Description
TX PCI-X Adapter (14108902)
Status
Location
Transmit jumbo frames
no
Enable hardware transmit and receive checksum
Media speed
Enable ALTERNATE ETHERNET address
no
ALTERNATE ETHERNET address
[0x000000000000]
Apply change to DATABASE only
no
Enable failover mode
[Entry Fields]
ent0
2-Port 10/100/1000 BaseAvailable
07-08
yes
Auto_Negotiation
disable
NOTE
The options of Media Speed are as follows:

l
10_Half_Duplex: 10 Mbit/s in half-duplex mode
10_Full_Duplex: 10 Mbit/s in full-duplex mode
100_Half_Duplex: 100 Mbit/s in half-duplex mode
Auto_Negotiation: auto-negotiation of transmission rates and working modes
3.5.16 Checking the Status of the Network Adapter on the PC Server

If the status of the network adapter is abnormal, service abnormality, call limit, or service
interruption may occur. This task is performed to check detailed information about the status of
the network adapter.
Reference Standard
In normal condition, make sure that:
l
The status of each NIC is RUNNING.
The transmission rate is 100 Mbit/s full-duplex or 1000 Mbit/s full-duplex and the working
mode is auto-negotiation.
Precaution
None.
Issue 01 (2010-09-29)

3-29
HUAWEI CBS
3 Daily Maintenance
Procedure
Step 2 Check the status of the network adapter.
# ifconfig -a
Step 3 Check the rate and working mode of the network adapter.
Checking the eth1 network adapter is used as an example.
# ethtool eth1
Settings for eth1:
Supported ports: [ TP ]
Supported link modes:
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
Where, the transmission rate of the NIC is 1000 Mbit/s and full-duplex and the working mode
is auto-negotiation.
----End
Exception Handling
If the network adapter is in abnormal state, or the rate and working mode of the network adapter
are incorrect, contact Huawei engineers.
3.5.17 Checking the Status of the Two-Node Cluster (ATAE)

This task is performed to check the status of the two-node cluster. If the status of the two-node
cluster is abnormal, serious security problems may occur in the system, and the switchover of
the two-node cluster may fail or the system is abnormal after the switchover.
Reference Standard
In normal condition, the status of the two-node cluster is as follows:
l
On the host phost1_1:

The ASMainGrp and FaultSpyGrp service group is in ONLINE state.
On the host phost1_2:
3-30
The ASMainGrp service group is in OFFLINE state.

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
The FaultSpyGrp service group is in ONLINE state.
Precaution
You can check the status of the two-node cluster in the following log files in /var/VRTSvcs/
log:
l
engine_A.log: recording operations performed on the VCS and information about the agent
script.
bmp_spy.log: recording monitoring information about BMP resources.
informix_spy.log: recording monitoring information about Informix resources.
oracle_spy.log: recording monitoring information about Oracle resources.
fault_spy.log: recording monitoring information about FaultSpy resources.
atae_lvm_volume_group.log: recording monitoring information about

ATAELVMVolumeGroup resources.
Procedure
Step 1 Log in to the active node and the standby node as the root user.
Step 2 Check the status of the two-node cluster.
# hastatus -sum
The system displays the information similar to the following:
-- SYSTEM STATE
-- System
A phost1_1
A phost1_2
-- GROUP STATE
-- Group
B ASMainGrp
B ASMainGrp
B FaultSpyGrp
B FaultSpyGrp
State
RUNNING
RUNNING
System
phost1_1
phost1_2
phost1_1
phost1_2
Frozen
0
0
Probed
Y
Y
Y
Y
AutoDisabled
N
N
N
N
State
ONLINE
OFFLINE
ONLINE
ONLINE
----End
Exception Handling
If the result does not meet the standard, locate the fault by analyzing logs.
If you need to restart the two-node cluster manually, see the HUAWEI CBS Installation Guide
or contact Huawei engineers.
3.5.18 Checking the Status of a Two-Node Cluster (HP)

Reference Standard
l
The cluster is in the up state.
The package is in the up or running state.
Issue 01 (2010-09-29)

3-31
HUAWEI CBS
3 Daily Maintenance
l
The node switchover function of the package is enabled.
Procedure
Step 2 Check the running status of the two-node cluster.
# cmviewcl -v
CLUSTER
cluster
STATUS
up
NODE
host1
STATUS
up
STATE
running
PACKAGE
appkg
STATUS
up
STATE
running
Node_Switching_Parameters:
NODE_TYPE
STATUS
SWITCHING
Primary
up
enabled
Alternate
up
enabled
AUTO_RUN
enabled
NODE
host1
NAME
host1a (current)
host1b
----End
Exception Handling
If the status of the two-node cluster is abnormal, rectify the problem according to logs.
If the problem persists, contact Huawei engineers.
3.5.19 Checking the Status of a Two-Node Cluster (IBM)

Reference Standard
The proper status of the two-node cluster is as follows:
l
3-32
Cluster status
In the case of the two-node cluster software HACMP5.2, the clstrmgrES, clinfoES,
and clsmuxpdES processes are in the active state on the active node and standby node.
In the case of the two-node cluster software HACMP5.3 or a later version, the
clstrmgrES and clinfoES processes are in the active state on the active node and
standby node.
The appspy process is in the active state on the active node and is in the inoperative
state on the standby node.
Network status
In the case of the two-node cluster in cold standby mode, the boot IP address on the
active node is in the DOWN state, and other IP addresses are in the UP state.
In the case of the two-node cluster in hot standby mode, all the IP addresses are in the
UP state.
Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Precaution
l
In the cluster software of HACMP5.3 or a later version, the clsmuxpdES process is

integrated into the clstrmgrES process. Therefore, you cannot find the clsmuxpdES
process.
If the appspy processes on the active node and standby node are in the inoperative state,
it indicates that the package of the system or the clinfo process on the active node is not
running. In this case, the two-node cluster cannot be switched over.
Procedure
Step 2 Check the status of the two-node cluster.
1.
Check the status of the processes of the two-node cluster.

# lssrc -g cluster
Subsystem
clstrmgrES
clinfoES
2.
Group
cluster
cluster
PID
450718
503888
Status
active
active
Check the status of the appspy process.

# lssrc -s appspy
The following information is displayed on the active node:
Subsystem
appspy
Group
PID
19514
Status
active
The following information is displayed on the standby node:

Subsystem
appspy
Group
PID
Status
inoperative
Step 3 Check the network status.

# /usr/sbin/cluster/clstat
NOTE
If the preceding command cannot be used, run the /usr/sbin/cluster/clinfo command to restart the clinfo
process.

clstat - HACMP Cluster Status Monitor
------------------------------------Cluster: appcluster
(1143602211)
Thu Mar 30 15:39:16 BEIST 2006
State: UP
Nodes: 2
SubState: STABLE
Node: host1a
State: UP
Interface: host1a_boot (0)
Address: 10.10.11.11
State:
DOWN
Interface: host1a_standby (0)
Address: 10.71.11.11
State:
UP
Interface: host1a_tty (1)
Address: 0.0.0.0
State:
UP
Interface: share_ip (0)
Address: 10.10.11.13
State:
UP
Resource Group: app_reg
State: On line
Issue 01 (2010-09-29)

3-33
HUAWEI CBS
3 Daily Maintenance
Node: host1b
State: UP
Interface: host1b_boot (0)
Interface: host1b_standby (0)
Interface: host1b_tty (1)
Address: 10.10.11.12
State:
UP
Address: 10.71.11.12
State:
UP
Address: 0.0.0.0
State:
UP
----End
Exception Handling
Step 1 Run the smit clstart command to restart the cluster software if the cluster software is not started
on the active node or standby node, that is, not all the clstrmgrES, clsmuxpdES, and
clinfoES processes are displayed after you run the lssrc -g cluster command.
Step 2 Run the startsrc -s appspy command to activate the appspy process if the appspy process on
the active node is in the inactive state.
----End
3.5.20 Checking the Status of the Two-Node Cluster on the PC

Server
This topic describes how to check the status of the two-node cluster. If the two-node cluster runs
abnormally, there is a great potential risk on the security of the system. The two-node cluster
may fail to be switched or the system is abnormal after the switchover.
Reference Standard
The two-node cluster runs normally and no error message is displayed.
Precaution
Perform the following operations on the active and standby nodes.
Procedure
Step 1 Log in to the active node or the standby node as the root user.
Step 2 Run the following command to check the running status of the two-node cluster:
# hastatus -sum
The system displays the following information:
-- SYSTEM STATE
-- System
State
Frozen
A
A
RUNNING
RUNNING
0
0
node-01
node-02
If the State column of each node is displayed as RUNNING, it indicates that the status of the
cluster is normal.
----End
3-34

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Exception Handling
If the result does not meet the standard, analyze the fault according to logs, and then locate the
cause. The log files of the two-node cluster are in /var/VRTSvcs/log. Run the more command
to check the logs of the two-node cluster, and then locate the cause of the exception. If you need
to restart the two-node cluster manually, see the HUAWEI CBS Installation Guide or contact
Huawei engineers.
3.5.21 Checking Core Files

This task enables you to check whether core files are generated. If core files are generated, critical
system faults may occur.
Reference Standard
No core files exist.
Precaution
Perform the following operations on the active node and standby node: (The operations may
affect system performance. Therefore, perform the operations when the traffic is low.)
Procedure
Step 2 Search for core files.
# find / -name "*core*" -print
----End
Exception Handling
If core files are generated, contact Huawei engineers.
3.6 Maintenance Tasks of the Database

This topic describes the maintenance tasks of the database.
3.6.1 Checking the Status of the SMDB
This task is performed to check the status of the SMDB. Abnormal database status can cause
problems, such as failure to release cards and failure to store CDRs in the database, even service
interruption.
3.6.2 Checking the Space Usage of the SMDB
This task is performed to check the space usage of the SMDB. Insufficient space can cause
service failures.
3.6.3 Backing Up the Data of the Memory Database
This topic describes how to perform level-0 backup for the SMDB to prevent the loss of important
data when severe system exceptions occur. To ease the impact of the SMDB backup on the
system running, perform the level-0 backup when the traffic is light, for example, at a time in
02:00:00-03:00:00 in the early morning.
Issue 01 (2010-09-29)

3-35
HUAWEI CBS
3 Daily Maintenance
3.6.4 Checking the Status of the Listener of the Oracle Database

This task enables you to check the status of the listener of the Oracle database. If the status of
the listener is abnormal, the Oracle database cannot be connected properly.
3.6.5 Checking Usage of the Oracle Tablespaces
This task is performed to check the usage of the Oracle tablespaces. Insufficient tablespaces can
cause service failures.
3.6.6 Checking the Status of the Listening Port of the Oracle Database
This task enables you to check the status of the listening port of the Oracle database. If the status
of the listening port is abnormal, the connection to the Oracle database fails.
3.6.7 Checking the Connection Logs of the Oracle Database
This task enables you to check whether error information is recorded in the connection logs of
the Oracle database. If any exception occurs, the Oracle database cannot be connected properly.
3.6.8 Backing Up the Data of the Oracle Database
This topic describes how to perform the level-0 backup operation for the Oracle database to
prevent the loss of important data when severe system exceptions occur.
3.6.9 Checking the Status of the Informix Database
This task enables you to check the status of the Informix database. If the status of the Informix
database is abnormal, the running of services is affected.
3.6.10 Checking the Space Usage of the Informix Database
This task enables you to check the space usage of the Informix database. Insufficient space causes
service failure.
3.6.11 Checking Logical Log Backup of the Informix Database
This topic describes the method of checking the logical log backup of the Informix database.
3.6.12 Backing Up the Data of the Informix Database
This topic describes how to perform the level-0 backup operation for the Informix database to
3.6.13 Checking the Status of the SQL Server Database
This topic describes how to check the status of the SQL server database, ensuring that the SQL
server database runs normally.
3.6.14 Checking the Tablespace of the SQL Server Database
To check the usage of the table space of the database to make a plan for the using of storage
space in time to prevent system exceptions caused by insufficient table space.
3.6.15 Backing Up the Data of the SQL Server Database
You can back up the data of the database through the intelligent query wizard of the Microsoft
SQL Server 2000.
3.6.16 Checking the Status of the DB2 Database
This topic describes how to check the status of the DB2 database, ensuring that the DB2 database
runs normally.
3.6.17 Checking the Tablespace of the DB2 Database
This topic describes how to check the tablespace of the DB2 database. To check the usage of
the table space of the database to make a plan for the using of storage space in time to prevent
system exceptions caused by insufficient table space.
3-36

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
3.6.1 Checking the Status of the SMDB

This task is performed to check the status of the SMDB. Abnormal database status can cause
problems, such as failure to release cards and failure to store CDRs in the database, even service
interruption.
Reference Standard
In normal condition, the status is as follows:
l
Status of the communication between the active node and standby node of the SMDB
The difference between the values of MsgID and AckMsgID must be less than 1.
Otherwise, it indicates that an exception occurs in the communication between the active
node and standby node of the SMDB.
Status of the SMDB
The System Mode of the active node is Primary, and the System Mode of the standby node is
Secondary.
Precaution
None.
Procedure
Step 1 Log in to the system as the smdb user.
Step 2 Run the following command to check the status of the memory database:
% mdstatus -s
Shared memory System Info
System Mode:
Current SCN:
Primary
200
Total Database Size

CLB Memory Size
Root Memory Size
Data Memory Size
Data Used Memory Size
Temp Data Memory Size
Temp Data Used Memory Size
System Memory Size
System Used Memory Size
:
:
:
:
:
:
:
:
:
673.51
20.00
39.51
272.00
128.00
50.00
0
292.00
78.93
MB
MB
MB
MB
KB
MB
B
MB
MB
----End
Exception Handling
If the check result does not meet the standard, contact Huawei engineers.
3.6.2 Checking the Space Usage of the SMDB

This task is performed to check the space usage of the SMDB. Insufficient space can cause
service failures.
Issue 01 (2010-09-29)

3-37
HUAWEI CBS
3 Daily Maintenance
Reference Standard
The sum of Free Size is greater than 20% of the sum of Total Size for each space.
Precaution
None.
Procedure
Step 1 Log in to the active node and standby node as the smdb user.
Step 2 Run the following command:
% mdstatus -sp
Spaces Information:
Name
Size
--------------------------------------dspace0
space1
--------------------------------------ispace0
--------------------------------------hspace0
Type
Create Time
Total Size Free
--------- ------------------- ---------data

2009-10-22 21:52:30 16.00 MB
15.81 MB
data
2009-10-22 21:52:30 20.00 MB
20.00 MB
--------- ------------------- ---------index
2009-10-22 21:52:30 16.00 MB
16.00 MB
--------- ------------------- ---------hash
2009-10-22 21:52:30 20.00 MB
6.39 MB
Check whether the available memory of each space occupies more than 20%.
----End
Exception Handling
If the remaining space is less than 20% of the total space, locate the fault. If the fault cannot be
located, contact Huawei engineers. Check whether the database space needs to be increased. To
increase the space, you can refer to the following steps. (The following commands are for
reference only. Please use the command parameters according to the actual situation.)
Step 1 Log in to the active node and standby node as the smdb user.
Step 2 Run the following command to access the mdsql tool operation interface:
% mdsql
Step 3 Run the following command to create a space:
The command format for creating a space is as follows:
create space space_name type [temp] data|hash|index size value
3-38

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
NOTE
The variable space_name indicates the name of a space.
The field type indicates the type of a space. The types of a space are divided into four categories,
namely, data, hash, index, and temp data. The space of the data type is used for storing data in the
synchronization table of the two-node cluster. The space of the hash type is used for storing the hash
data of the hash index. The space of the index type is used for storing the node data of the hash index.
The space of the temp data type is used for storing temporary table data.
The variable value indicates the size of a space, in MB. The value ranges from 16 to 1024.
Assume that you need to create a space named test0, the type is data, and the size is 17 MB. The
relevant command is as follows:
admin#dbsql> create space test0 type data size 17 ;
If the command is run successfully, the following information is displayed:
create space test0 succeeded.
Step 4 Run the following command to exit the mdsql tool:

admin#dbsql> exit
Step 5 Use the mdalter tool to add a storage unit dynamically.
% mdalter -addspace <space size> <space type>
Run the following command:
% mdalter -addspace 16 1
The following information is displayed after the successful execution:
Create space succeeded! spaceID=3.
Step 6 Run the following command to confirm the successful execution.

% mdstatus -sp
Spaces Information:
Name
Size
--------------------------------------dspace0
space1
test0
--------------------------------------ispace0
--------------------------------------hspace0
Type
Create Time
Total Size Free
--------- ------------------- ---------data

data
data
---------
2009-10-22 21:52:30
2009-10-22 21:52:30
2009-10-23 16:22:32
-------------------
16.00 MB
15.81 MB
20.00 MB
20.00 MB
17.00 MB
17.00 MB
----------
index
2009-10-22 21:52:30 16.00 MB
16.00 MB
--------- ------------------- ---------hash
2009-10-22 21:52:30 20.00 MB
6.39 MB
----End
3.6.3 Backing Up the Data of the Memory Database

This topic describes how to perform level-0 backup for the SMDB to prevent the loss of important
data when severe system exceptions occur. To ease the impact of the SMDB backup on the
system running, perform the level-0 backup when the traffic is light, for example, at a time in
02:00:00-03:00:00 in the early morning.
Issue 01 (2010-09-29)

3-39
HUAWEI CBS
3 Daily Maintenance
Prerequisite
The available space size of the backup directory must be greater than the size of the SMDB.
Context
None.
Procedure
Step 1 Log in to the active node of the CBP system as the smdb user.
Step 2 Check the available space size of the backup directory.
l
IBM/ATAE
% df -k BackupDir
HP
% bdf BackupDir
NOTE
BackupDir: indicates the backup directory of the SMDB, specified by the DBFilePath parameter in the
$HOME/smdb/cfg/smdb_config.cfg file.
Step 3 Check the size of the SMDB.

% mdstatus -s
The value of Total Database Size displayed on the screen indicates the size of the SMDB.
Step 4 Access the bin directory of the SMDB.
% cd $HOME/smdb/bin
Step 5 Spring the level-0 backup.
% mdbackup -l
NOTE
Running this command is to start the backup. To check whether the backup is complete, run the mdbackup
-s command to see the progress.
If the SMDB runs in single-node mode, you need to run the mdmode -s primary -f command to change
to the active-node mode. After the mdb_pmon process starts the mdb_dwrt process, you can perform the
level-0 backup.
----End
Exception Handling
If any exception occurs, do as follows:
1.
Check whether the disk space of the backup directory is sufficient.

(1) Log in to the active node as the root user.
(2) Check the disk space.
l
IBM/ATAE
# df -m
3-40
HP
Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
# bdf
The value of Use% or %Used displayed on the screen indicates the usage of a file
system. The space usage of each file system must be less than 80%.
(3) If the usage is higher than 80%, you need to increase the disk space or delete outdated
files from existing disks through FTP. Then back up log files again.
2.
If the fault persists, contact Huawei engineers.
3.6.4 Checking the Status of the Listener of the Oracle Database

This task enables you to check the status of the listener of the Oracle database. If the status of
the listener is abnormal, the Oracle database cannot be connected properly.
Reference Standard
The listener is in the READY or UNKNOWN state.
Procedure
Step 1 Log in to the active node as the oracle user.
Step 2 Check the status of the listener.
% lsnrctl status
The following information is displayed:
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
-----------------------Alias
LISTENER
Version
TNSLSNR for Linux: Version 11.1.0.6.0 - Production
Start Date
24-MAR-2010 11:04:59
Uptime
1 days 3 hr. 32 min. 43 sec
Trace Level
off
Security
ON: Local OS Authentication
SNMP
OFF
Listener Parameter File
/opt/oracle/product/11.1/network/admin/listener.ora
Listener Log File
/opt/oracle/diag/tnslsnr/bme232/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=bme232)(PORT=1521)))
Services Summary...
Service "ora" has 1 instance(s).
Instance "ora", status READY, has 1 handler(s) for this service...
The command completed successfully
If the status of the listener is normal, the following information is displayed:

----End
Exception Handling
l
If the following information is displayed after you run the lsnrctl status command, it
indicates that the listener is not started:
TNS-12541: TNS:no listener
In this case, run the lsnrctl start command to start the listener.
Issue 01 (2010-09-29)

3-41
HUAWEI CBS
3 Daily Maintenance
l
If other error information is displayed after you run the lsnrctl status command, contact
Huawei engineers.
3.6.5 Checking Usage of the Oracle Tablespaces

This task is performed to check the usage of the Oracle tablespaces. Insufficient tablespaces can
cause service failures.
Reference Standard
The value of the %Used column for every tablespace is less than 75%.
Precaution
None.
Procedure
% sqlplus "/as sysdba"
SQL> select df.tablespace_name "Tablespace",df.bytes/(1024*1024) "Total Size(MB)",
sum(fs.bytes)/(1024*1024) "Free Size(MB)", round(sum(fs.bytes)*100/df.bytes) "%
Free", round((df.bytes-sum(fs.bytes))*100/df.bytes) "% Used" from dba_free_space fs,
( select tablespace_name, sum(bytes) bytes from dba_data_files group by
tablespace_name ) df where fs.tablespace_name = df.tablespace_name group by
df.tablespace_name, df.bytes;
The system displays the information similar to the following:
Tablespace
Total Size(MB) Free Size(MB)
% Free % Used
------------------------------ -------------- ------------- ------ ---------SYSAUX
5000
4403.25
88
12
SYSTEM
2000
1319.6875
66
34
UNDOTBS1
825
783.1875
95
5
UNDOTBS2
500
485.5
97
3
USERS
500
499.9375
100
0
----End
Exception Handling
If the remaining space of a tablespace is insufficient, enlarge the size of the file system or LV
to increase the tablespace or delete unnecessary history data to lower the usage of the tablespace.
3.6.6 Checking the Status of the Listening Port of the Oracle

Database
This task enables you to check the status of the listening port of the Oracle database. If the status
of the listening port is abnormal, the connection to the Oracle database fails.
3-42

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Reference Standard
If the following information is displayed, it indicates that port number 1521 of the Oracle
database is being listened on properly:
tcp
10.10.11.3.1521
*.*
LISTEN
NOTE
The content in bold indicates the floating IP address and port number of the server where the Oracle database
is installed.
Procedure
Step 2 Check the status of the listening port.
% netstat -an | grep LISTEN | grep 1521
If the information similar to the following is displayed, it indicates that the staus of the listening
port is normal:
tcp
10.10.11.3.1521
*.*
LISTEN
----End
Exception Handling
If the status of the listening port is abnormal, perform the following operations:
1.
Check whether the Listener process is started.

lsnrctl status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
-----------------------Alias
LISTENER
Version
TNSLSNR for Linux: Version 11.1.0.6.0 - Production
Start Date
24-MAR-2010 11:04:59
Uptime
1 days 3 hr. 32 min. 43 sec
Trace Level
off
Security
ON: Local OS Authentication
SNMP
OFF
Listener Parameter File
/opt/oracle/product/11.1/network/admin/listener.ora
Listener Log File
/opt/oracle/diag/tnslsnr/bme232/listener/alert/
log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=bme232)(PORT=1521)))
Services Summary...
Service "ora" has 1 instance(s).
The displayed information contains the following content:

In addition, the following content is not contained:

TNS-12541: TNS:no listener
Therefore, the Listener process is running properly.

If the Listener process is not running properly, run the lsnrctl stop command to end it, and
then run the lsnrctl start command to start it.
Issue 01 (2010-09-29)

3-43
HUAWEI CBS
3 Daily Maintenance
NOTE
In normal cases, you do not need to restart the database after the Listener process is started.
2.
If the Listener process is started, check whether the port number for the Listener process
in $ORACLE_HOME/network/admin/listener.ora is 1521.
vi $ORACLE_HOME/network/admin/listener.ora
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = bme232)(PORT = 1521))
If the port number is not 1521, contact Huawei engineers.
3.6.7 Checking the Connection Logs of the Oracle Database

This task enables you to check whether error information is recorded in the connection logs of
the Oracle database. If any exception occurs, the Oracle database cannot be connected properly.
Reference Standard
l
The listener.log file does not contain error information that starts with ORA-, TNS-, or
dead lock.
The size of the listener.log file does not exceed 50 MB.
Procedure
Step 1 Log in to the active node and standby node as the oracle user.
Step 2 Search for the listener.log file.
find . -name "listener.log"
./product/11g/db/log/diag/tnslsnr/bme233/listener/trace/listener.log
./diag/tnslsnr/bme233/listener/trace/listener.log
In the preceding information, bme233 indicates the name of a host.

Step 3 View the listener.log file.
l
./product/11g/db/log/diag/tnslsnr/bme233/listener/trace/listener.log
./diag/tnslsnr/bme233/listener/trace/listener.log
----End
Exception Handling
l
If the listener.log file contains error information that starts with ORA-, TNS-, or dead
lock, report the error information to Huawei engineers.
If the size of the listener.log file exceeds 50 MB, it is recommended that you clear the file.
For example, delete the content "echo > listener.log", but do not delete the listener.log file.
NOTE
You must back up the file before clearing the file.
3-44

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
3.6.8 Backing Up the Data of the Oracle Database

This topic describes how to perform the level-0 backup operation for the Oracle database to
Prerequisite
None.
Context
CAUTION
The level-0 backup operation is performed at idle time, generally finished within four hours after
00:00.
This section provides only backup solution. For the method and procedure of backup (charged),
contact Huawei marketing.
Procedure
Step 1 Visit http://support.huawei.com, and apply for the permission to download documents from this
website.
Step 2 For the backup solution, see the ENIP V100R003C02-Special Topic-CBS Oracle11g Database
Backup and Recovery at http://support.huawei.com.
----End
Exception Handling
1.

(1) Log in to the system as the root user.
l
IBM/ATAE
# df -m
HP
# bdf
2.
Issue 01 (2010-09-29)

3-45
HUAWEI CBS
3 Daily Maintenance
3.6.9 Checking the Status of the Informix Database

This task enables you to check the status of the Informix database. If the status of the Informix
database is abnormal, the running of services is affected.
Reference Standard
l
In shared disk mode:

The database on the active node is in the On-Line state.
In HDR mode:
The database on the active node is in the On-Line (Prim) state and the database on the
standby node is in the Read-Only (Sec) state.
The State parameter for HDR synchronization is set to on.
Precaution
In shared disk mode, you need to check only the active node. In HDR mode, you need to check
both the active node and standby node.
Procedure
Step 1 Log in to the active node and standby node as the informix user.
Step 2 Check the running status of the Informix database.
% onstat Step 3 In HDR mode, run the following command to check the HDR synchronization status.
% onstat -g dri
IBM Informix Dynamic Server Version 9.40.FC7
05:59:12 -- 1025680Kbytes
Data Replication:
Type
State
primary
on
DRINTERVAL
DRTIMEOUT
DRLOSTFOUND
Paired server
host_online1_net
-- On-Line (Prim) -- Up 6 days
Last DR CKPT (id/pg)

976 / 2339
30
30
/opt/informix/etc/dr.lostfound
----End
Exception Handling
If the check result does not meet the check standard, check the status of the Informix database
every 3 seconds. If the status of the Informix database is abnormal, run the following commands
to restart the database and then check the status again:
% onmode -ky
% oninit
% onstat 3-46

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
3.6.10 Checking the Space Usage of the Informix Database

This task enables you to check the space usage of the Informix database. Insufficient space causes
service failure.
Reference Standard
The total usage rate of the workdbs data space is equal to or less than 80%.
NOTE
The formula used to calculate the usage of all workdbs data spaces is as follows: [(Sum of values in the
size column - Sum of values in the free column)/Sum of values in the size column] x 100%
Precaution
In shared disk mode, you need to check only the active node. In HDR mode, however, you need
to check both the active node and standby node.
Procedure
Step 1 Log in to the system as the informix user.
Step 2 Check the space usage of the Informix database.
% onstat -d
If the information similar to the following is displayed, pay attention to the values in the size
and free columns, and use the preceding formula to calculate the usage of all the workdbs data
spaces.
l
IBM
Chunks
address
pathname
700000010340bf8
rlvworkdbs1
700000010184228
rlvworkdbs2
700000010184558
rlvworkdbs3
chunk/dbs
offset
size
free
bpages
flags
10
318216
311324
PI-- /dev/
10
393216
393213
PI-- /dev/
10
393216
393213
PI-- /dev/
HP and ATAE
Chunks
address
c000000007ce2b20
rlvworkdbs1
c000000007ce2e60
rlvworkdbs2
700000010184558
rlvworkdbs3
chunk/dbs
4
4
offset
size
20
1000000
free
959348
20
1000000
999997
10
393216
393213
bpages
flags pathname
PO-- /dev/vgphydb/
PO-- /dev/vgphydb/
PI-- /dev/vgphydb/
----End
Exception Handling
If the total usage of all the workdbs data spaces does not meet the requirement, perform the
following operations to increase data spaces:
Step 1 Add the logical volume (LV) of the raw type according to the disk space usage.
Issue 01 (2010-09-29)

3-47
HUAWEI CBS
3 Daily Maintenance
l
IBM
# mklv -t raw -e x -y lvworkdbs1 phydbvg 32 hdisk3
HP
# lvcreate -n lvworkdbs1 -l 32 /dev/phydbvg
ATAE
# vxassist -g vgphydb -U gen make lvworkdbs1 Size vgphydb_1
NOTE
The value lvworkdbs1 indicates the name of a new LV, phydbvg and vgphydb are the names of the
VGs to which workdbs belongs, and vgphydb_1 is the name of the disk that corresponds to
vgphydb.
The value 32 indicates the number of logical partitions (LPs). The formula used to calculate the number
of LPs is LV size/LP size.
Step 2 Modify the permissions on the LV.

l
IBM
# chown informix:informix /dev/*workdbs1
# chmod 660 /dev/*workdbs1
HP and ATAE
# chown informix:informix /dev/vgphydb/*workdbs1
# chmod 660 /dev/vgphydb/*workdbs1
Step 3 Add the LV to the data spaces.

l
IBM
% onspaces -a workdbs -p /dev/rlvworkdbs1 -o 40 -s 2000000
HP and ATAE
% onspaces -a workdbs -p /dev/vgphydb/rlvworkdbs1 -o 40 -s 2000000
----End
3.6.11 Checking Logical Log Backup of the Informix Database

This topic describes the method of checking the logical log backup of the Informix database.
Reference Standard
The following contents must exist at the beginning of etc/log_full.sh:
ontape -a<
n
!
Precaution
Both the active node and standby node are checked in HDR mode.
Procedure
Step 1 Log in to the active node and the standby node as the informix user.
3-48

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
% view etc/log_full.sh
----End
Exception Handling
If the check result does not meet the standard, do as follows:
Step 1 If you do not back up logs by storing them, you need to add the four lines of statements to the
file and ensure that the logbak.sh timed task does not exist in crontab; otherwise, the HDR may
be abnormal.
Step 2 If you back up logs by storing them, the four lines of statements are not needed. Ensure that the
logbak.sh timed task exists in crontab.
----End
3.6.12 Backing Up the Data of the Informix Database

This topic describes how to perform the level-0 backup operation for the Informix database to
Prerequisite
None.
Context
l
The database is backed up to the tape drive.
When the ontape interactive backup is adopted, view the online.log file. If the following
information is displayed, it indicates that the backup is successful.
Archive on rootdbs, logdbs, phydbs, workdbs Completed
Procedure
Step 1 Log in to the system as the informix user.
Step 2 Perform the level-0 backup.
informix% ontape -s -L 0
----End
Exception Handling
1.

(1) Log in to the system as the root user.
l
IBM/ATAE
# df -m
Issue 01 (2010-09-29)
HP
3-49
HUAWEI CBS
3 Daily Maintenance
# bdf
2.
3.6.13 Checking the Status of the SQL Server Database

This topic describes how to check the status of the SQL server database, ensuring that the SQL
server database runs normally.
Reference Standard
The service manager of SQL Server 2000 runs normally.
Precaution
None.
Procedure
Step 1 Double-click
, which represents the service manager of SQL Server 2000, on the BAM
server. The SQL Server2000 Service Manager dialog box is displayed.
Step 2 Select SQL Server Agent from the Services drop-down list box.
3-50
If
Then
If the icon in the white round of the left

window is a green triangle as shown in
Figure 3-10
It indicates that the service manager of SQL

Server 2000 runs normally.
If the icon in the white round of the left

window is a red block as shown in Figure
3-11
It indicates that the service manager of SQL

Server 2000 stops running. Click Start/
Continue. The manager refreshes the service.

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Figure 3-10 Window where the service manager of SQL Server 2000 is running
Figure 3-11 Window where the service manager of SQL Server 2000 stops running
----End
Exception Handling
If the SQL Server2000 server manager stops running, click Start/Continue to restart the service.
3.6.14 Checking the Tablespace of the SQL Server Database

To check the usage of the table space of the database to make a plan for the using of storage
space in time to prevent system exceptions caused by insufficient table space.
Issue 01 (2010-09-29)

3-51
HUAWEI CBS
3 Daily Maintenance
Reference Standard
The usage of each tablespace cannot exceed 70%.
Precaution
None.
Procedure
Step 1 Log in to the console as the user of the database.
Step 2 Select the database and check the properties. Then, select data files and check the usage of the
database, as shown in Figure 3-12.
Figure 3-12 Checking the tablespace of the SQL server database
----End
Exception Handling
If the usage of a tablespace is greater than 70%, you need to add data files to the tablespace
immediately in the following way:
3-52

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Log in to the console to select the database. Right-click the shortcut menu and choose
Properties. Click the Data Files tab in the dialog box that is displayed and add a data file, as
shown in Figure 3-13.
Figure 3-13 Adding data files to the tablespace
3.6.15 Backing Up the Data of the SQL Server Database

You can back up the data of the database through the intelligent query wizard of the Microsoft
SQL Server 2000.
Prerequisite
l
The BAM runs normally.
The Microsoft SQL Server 2000 runs normally.
Context
Before expansion, upgrade, and loading, you must back up the BAM database and registry table
manually. In this case, you are advertised to use independent backup media. To back up data
through the backup media, ensure that the database is backed up manually. You can back up the
database manually in the following ways:
Issue 01 (2010-09-29)

3-53
HUAWEI CBS
3 Daily Maintenance
l
Command mode (BKP DB)

On the local maintenance terminal, run the BKP DB command. You can back up the BAM
database and registration table to the default backup directory F:\VMSC60.
Menu of Enterprise Manager of the SQL server

Generally, the BKP DB command is used to back up the database. In certain situations,
you cannot use the BKP DB command. In this case, you can use the intelligent query wizard
of the Microsoft SQL Server 2000 to back up the database.
The storage directory of backup files and file name are automatically specified in the
intelligent query wizard of the Microsoft SQL Server 2000.
USAU : The important data files that need to be backed up include BAM, ALARM, and
STAT.
URP : The important data files that need to be backed up include BAM and ALARM.
Procedure
Step 1 Choose Start > Programs > Microsoft SQL Server > Enterprise Manager.
Step 2 Right-click the displayed window and select the database that needs to be backed up, as shown
in Figure 3-14.
Figure 3-14 Page for backing up the data
Step 3 Choose All Tasks > Backup Database.... The window shown in is displayed.
3-54

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Figure 3-15 Selecting the database and backup mode in the SQL server backup window
For the description of backup and overwrite, see Table 3-3.

Table 3-3 Description of options in the backup window
Field
Option and Meaning
Backup
Database-complete: Backs up all the data.

Database-differential: : Backs up the changed data.
Overwrite
Append to media: Not overwrite the current data.

Overwrite existing media: Overwrites the current data.
Select the database that needs to be backed up in Database.
Select the mode for backing up data in Backup.
Select whether to overwrite the current data in Overwrite.
Select the default backup file name in Destination. Click Remove to delete the value, and
then click Add.... Determine the path and file name of the backup file, as shown in Figure
3-16.
Issue 01 (2010-09-29)

3-55
HUAWEI CBS
3 Daily Maintenance
Figure 3-16 Window of determining the file path and file name of the backup data
Step 4 When you back up the data, select the file name and device to be backed up and click OK. Then,
the system starts to back up data. After the system backs up data successfully, the system displays
a message indicating that the backup is complete.
----End
Exception Handling
1.
2.

l
If the disk space is insufficient, clear the disk space or increase the disk space.
If the disk space is sufficient, go to the next step.
Contact Huawei engineers.
3.6.16 Checking the Status of the DB2 Database

This topic describes how to check the status of the DB2 database, ensuring that the DB2 database
runs normally.
Reference Standard
The DB2 database has been started.
Precaution
None.
Procedure
Step 1 Log in to the host where the DB2 database is installed as the administrator of the DB2 server
(for example, dasadm1), and then run the following command:
db2admin start
3-56

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
If the following information is displayed, it indicates that the DB2 management server has been
started normally:
SQL4409W The DB2 Administration Server is already active.
Step 2 Log in to the host where the DB2 database is installed as the instance user of the DB2 database
(for example, db2inst1), and then run the following command:
db2 get instance
Step 3 Check the current instance (Generally, the instance is db2inst1.), and then run the following
command:
db2start
If the following information is displayed, it indicates that the instance has been started normally:
12/20/2005 17:44:44 0 0 SQL1026N The database manager is already active.
SQL1026N The database manager is already active.
Step 4 Assume that the name of the database is db123. Log in to the host where the DB2 database is
installed as the instance user of the DB2 database (for example, db2inst1), and then run the
following command:
db2 connect to db123
If the following information is displayed, it indicates that the DB2 database is connected
successfully:
Database Connection Information
Database server = DB2/LINUX 8.2.0
SQL authorization ID = DB2INST1
Local database alias = db123
----End
Exception Handling
If the service of the DB2 database does not start, log in to the DB2 database as the db2inst1
user. Then, run the db2start command to start the instance of the DB2 database.
3.6.17 Checking the Tablespace of the DB2 Database

This topic describes how to check the tablespace of the DB2 database. To check the usage of
the table space of the database to make a plan for the using of storage space in time to prevent
system exceptions caused by insufficient table space.
Reference Standard
The remaining space must be equal to or greater than 20% of the total tablespace.
Precaution
None.
Procedure
Step 1 Log in to the database as the DB2 instance user to install the device.
Step 2 Run the following command to access the DB2 database:
Issue 01 (2010-09-29)

3-57
HUAWEI CBS
3 Daily Maintenance
db2
Step 3 Run the following command to connect to the DB2 database:
connect to db123
Step 4 Run the following command to check detailed information about all the tablespaces of the
database:
list tablespaces show detail
Tablespace ID = 2
Name = USERSPACE1
Type = Database managed space
Contents = Any data
State = 0x0000
Detailed explanation:
Normal
Total pages = 25600
Useable pages = 25568
Used pages = 6752
Free pages = 18816
High water mark (pages) = 6752
Page size (bytes) = 4096
Extent size (pages) = 32
Prefetch size (pages) = 32
Number of containers = 1
CAUTION
Free pages indicates the remaining pages of a tablespace and the size of each page is 4 KB.
Step 5 You can check information about a specified tablespace container according to the Tablespace
ID that is queried in step 4. Assume that information about tablespace container 2 is queried.
Then run the following command:
list tablespace containers for 2
The detailed information about the tablespace container is as follows:
Container ID = 0
Name = /opt/db2/tsdata/userspace1
Type = File
Total pages = 25600
Useable pages = 25568
Accessible = Yes
CAUTION
The number of remaining pages of the tablespace container is the number of usable pages
subtracted from the number of total pages. The size of each page is 4 KB.
----End
Exception Handling
If the usage of a tablespace exceeds 70%, data files are added to the tablespace.
3-58

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
3.7 Maintenance Tasks of the Applications

This topic describes the maintenance tasks of the applications.
3.7.1 Checking the Status of the CBP Processes
This task is performed to check the status of the CBP processes. Abnormal process status can
affect service operations.
3.7.2 Checking the Status of the BMP Processes
This task is performed to check the status of the BMP processes. Abnormal process status can
3.7.3 Checking the Status of the SCP Processes
This task is performed to check the status of the SCP processes. Abnormal process status can
3.7.4 Checking the Status of the Process on the DCC Proxy
This topic describes how to check whether the process runs normally on the active and standby
nodes of the DCC proxy.
3.7.5 Checking the Status of the Process on the Billing
This topic describes how to check the background process of the Billing.
3.7.6 Checking the Status of the CBP Ports
This task is performed to check whether the status of the CBP ports is normal.
3.7.7 Checking the Status of the BMP Ports
This task is performed to check whether the status of the BMP ports is normal.
3.7.8 Checking the Status of the SCP Ports
This task is performed to check whether the status of the SCP ports is normal.
3.7.9 Checking the Interface Connection Status on the DCC Proxy
This topic describes how to check the connection status of each interface on the DCC proxy.
3.7.10 Checking the Run Logs of the CBP
This task is performed to check whether the exception information exists in the run logs of the
CBP.
3.7.11 Checking the Run Logs of the BMP
BMP.
3.7.12 Checking the Run Logs of the SCP
SCP.
3.7.13 Checking the Run Log of the DCC Proxy
To check the running logs to detect the faults in the system.
3.7.14 Checking the GFEP Run Log
This topic describes how to check whether the GFEP run log contains the WARNING and
ERROR information.
3.7.15 Checking the Run Logs of the RBI
This task is to check that the run logs of the RBI do not contain error or warning information.
The purpose is to ensure that the RBI can transfer CDR files normally.
Issue 01 (2010-09-29)

3-59
HUAWEI CBS
3 Daily Maintenance
3.7.16 Checking the Number of CDRs on the CBP

This task is to check that the number of CDRs on the CBP does not increase or decrease
significantly. The purpose is to ensure that all the required fees are collected from subscribers.
Therefore, the revenue of the carrier can be ensured.
3.7.17 Checking the Offline CDR on the CBP
This task is to check that the offline CDRs on the CBP are processed normally. The purpose is
to ensure that all the required fees are collected from subscribers. Therefore, the revenue of the
carrier can be ensured.
3.7.18 Checking the Scheduled Tasks on the BMP
This topic describes how to check the scheduled tasks in the system. After checking these
scheduled tasks, you can ensure that the services performed by the tasks run normally.
3.7.19 Checking the AR Task
This topic describes how to check the running status and exception of the journal task and journal
collecting task.
3.7.20 Checking the Running of the SSMFEP
This task is to check that the SSMFEP process exists. The purpose is to ensure the normal running
of the SSMFEP and normal delivery of offline short messages.
3.7.21 Checking the Connection of the GFEP and Other Devices
This task is to check the connections between the GFEP and other devices such as the SMSC.
The purpose is to ensure the normal communication between components.
3.7.22 Checking That the RBI Transfers CDRs Normally
This task is to check that the RBI transfers CDRs in time. The purpose is to prevent incorrect
charging caused by non-transfer of CDRs and insufficient disk space caused by CDR pileup on
the RBI.
3.7.1 Checking the Status of the CBP Processes

This task is performed to check the status of the CBP processes. Abnormal process status can
Reference Standard
The number of started containers in the CBP is the same as the setting in the ${HOME}/config/
node.cfg file.
Precaution
For the CBP two-node cluster in hot standby mode, perform the following operations on the
active node and standby node.
For the CBP two-node cluster in cold standby mode, the following steps need to be performed
only on the active node.
Procedure
Step 1 Log in to the CBP system as the cbp user.
Step 2 Run the following command to check the CBP system process status.
cbp% p
3-60

Issue 01 (2010-09-29)
HUAWEI CBS
UID
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
cbp
3 Daily Maintenance
PID
12495
12563
12571
12602
12676
12689
12703
12719
12801
12890
12891
12892
12893
12894
12895
12896
12904
12950
12957
12962
13150
13153
13157
13258
13327
13331
13339
13343
13353
13357
13372
13374
PPID
1
1
1
1
1
1
1
1
1
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
12801
C
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
STIME
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
04:56
TTY
pts/33
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
TIME
00:00:00
00:00:00
00:00:00
00:00:01
00:00:05
00:00:05
00:00:03
00:00:06
00:01:05
00:01:03
00:00:25
00:00:24
00:00:34
00:00:32
00:00:25
00:00:20
00:00:25
00:00:24
00:00:23
00:00:40
00:00:22
00:00:29
00:00:22
00:03:03
00:00:24
00:00:24
00:00:24
00:01:11
00:01:01
00:00:23
00:01:56
00:00:21
ALIASNAME
icdcomm
idcenter
idagent
lom
configDaemon
namingDaemon
toolDaemon
idlproxy
Monitor 0
Center 1
BatchMngAgent 50
CBP_OM 60
CdrBuf2File 70
CommonMngAgent 100
DBAgent 110
DiamAdapter 120
MngMsgProcess 130
RSIProcess 140
SyncDataAgent 150
OutWorkOrderAgent 160
RCOMMAdpt 180
SOAPAdpt 190
RealTimeMngAgt 200
SchedCharging 210
SchedTask 220
CancelResrv 250
TLVMonitor 260
ClearTable 290
SyncCache 300
DiamSessionClean 700
CdrRating 800
DiamMsgRating 900
Step 3 Check whether the processes of the CBP are stable.

After the processes of the CBP are started, all the process IDs remain unchanged.
----End
Exception Handling
If the status of the CBP processes is abnormal, check process start logs or contact Huawei
engineers.
3.7.2 Checking the Status of the BMP Processes

This task is performed to check the status of the BMP processes. Abnormal process status can
Reference Standard
The number of started containers in the BMP is the same as the setting in the ${HOME}/config/
node.cfg file.
Precaution
None.
Issue 01 (2010-09-29)

3-61
HUAWEI CBS
3 Daily Maintenance
Procedure
Step 1 Log in to the BMP system as the bmp user.
Step 2 Run the following command to check the BMP system process status.
bmp% p
If the system displays information similar to the following, it indicates that the status of the BMP
processes is normal.
UID
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
PID
20358
20405
20280
20090
20156
20150
20317
20298
17486
29446
14986
17386
PPID
1
20358
1
1
1
1
1
1
1
1
14960
1
C
0
0
0
0
0
0
0
0
0
0
3
0
STIME
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
TTY
?
?
?
?
?
?
?
?
?
?
?
?
TIME
00:01:43
00:02:44
00:00:34
00:00:04
00:00:00
00:00:00
00:00:47
00:00:51
00:00:00
00:00:00
01:31:21
00:06:53
ALIASNAME
Monitor 0
Center 1
configDaemon
icdcomm
idagent
idcenter
idlproxy
namingDaemon
ExprServer -d
Apache -k
jboss 1
monitor_jboss
Step 3 Check whether the processes of the BMP are stable.

After the processes of the BMP are started, all the process IDs remain unchanged.
----End
Exception Handling
If the status of the BMP processes is abnormal, check process start logs or contact Huawei
engineers.
3.7.3 Checking the Status of the SCP Processes

This task is performed to check the status of the SCP processes. Abnormal process status can
Reference Standard
The counts of the sdf processes, scf processes, and sbf processes are the same as the values of
NrOfSDF, NrOfSCF, NrOfSBF set in the ${TELLIN_DIR}/config/nodesys.cfg file
respectively.
Precaution
For the SCP two-node cluster in hot standby mode, perform the following operations on the
For the SCP two-node cluster in cold standby mode, the following steps need to be performed
Procedure
Step 1 Log in to the SCP system as the scu user.
3-62

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Step 2 Run the following command to check the SCP system process status.
scu% p
The system displays the running status of each process as follows:
UID
scu
scu
scu
scu
scu
scu
scu
PID
13674
14068
32618
33256
42300
59626
59918
PPID
14068
1
14068
14068
14068
14068
14068
C
2
1
0
0
0
1
0
STIME TTY TIME CMD

11:34:17 - 3:05 SipNode
11:34:17 - 0:35 manager 0
11:34:17 - 0:15 smfagent 0
11:34:17 - 0:06 sdf 0
11:34:17 - 0:37 scf 0 1
11:34:17 - 0:18 server 0 1
11:34:17 - 0:06 sbf 0 0
NOTE
The counts of the sdf processes, scf processes, and sbf processes are the same as the values of NrOfSDF,
NrOfSCF, NrOfSBF set in the ${TELLIN_DIR}/config/nodesys.cfg file respectively.
Step 3 Check whether the processes of the SCP are stable.

After the processes of the SCP are started, all the process IDs remain unchanged.
----End
Exception Handling
If the status of the SCP processes is abnormal, check process start logs or contact Huawei
engineers.
3.7.4 Checking the Status of the Process on the DCC Proxy

This topic describes how to check whether the process runs normally on the active and standby
nodes of the DCC proxy.
Reference Standard
On the DCC proxy, the Monitor, DiamAdapte, lom, and icdcomm processes have been started.
Precaution
None.
Procedure
Step 1 Log in to the active and standby nodes as the dcc user.
Step 2 Check the status of the DCC proxy service.
dcc% p
If the following information is displayed on the active node, it indicates that the DCC proxy
service has been started.
UID
dcc
dcc
dcc
dcc
dcc
Issue 01 (2010-09-29)
PID
684220
380968
495830
573608
577788
PPID
1
684220
1
1
1
C
0
0
0
0
0
STIME
00:15:43
00:15:45
00:15:40
10:47:36
22:49:28
TTY
-
TIME
0:35
0:41
0:32
0:00
1:17

COMMAND
Monitor 0
DiamAdapte 120
lom
filemirror
icdcomm
3-63
HUAWEI CBS
3 Daily Maintenance
The system of the standby node displays the following running status of the processes:
UID
dcc
dcc
dcc
dcc
PID
1507500
684102
389236
491612
PPID
1
1507500
1
1
C
0
2
0
0
STIME
11:53:43
11:53:44
11:53:39
11:53:38
TTY
-
TIME COMMAND
0:04 Monitor 0
0:05 DiamAdapte 120
0:03 lom
0:00 icdcomm
----End
Exception Handling
If an exception occurred in the process and the problem cannot be solved after the restart, contact
Huawei engineers.
3.7.5 Checking the Status of the Process on the Billing

This topic describes how to check the background process of the Billing.
Reference Standard
The information about the background process is displayed.
For example, the following information is displayed if the cmdmgr process is normal:
b2ins
20669
0 10:25 ?
00:00:00 cmdmgr -n 101
Procedure
Step 1 Log in to a server through Telnet.
Step 2 Run the following command to perform the routine check:
ps -fu ${LOGNAME} | grep XXX | grep -v grep
NOTE
The variable XXX indicates the name of a process.

The processes that run at the background of Billing include:
l
cmdmgr, dspcdr, impcdr, cmlcdr and syncartrans processes that are always running on the background
of B&B
mskhotbill, billcalc, billgen, and billprep processes that are running on the background of Billing
because they are being invoked
The preceding listed processes are only for reference. Check the processes according to the actual situation.
----End
Exception Handling
If a process ends, restart the process.
The following takes the cmdmgr process as an example to describe how to restart a process:
1.
Log in to the server where the Billing background process runs as the Billing background
user through Telnet.
2.
Run the cmdmgr command to restart the process.

NOTE
Before restarting the process, run the process name h command to view Syntax.
3-64

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
3.7.6 Checking the Status of the CBP Ports

This task is performed to check whether the status of the CBP ports is normal.
Reference Standard
The connection status of each port is ESTABLISHED.
Precaution
None.
Procedure
Step 1 Log in to the active node as the cbp user.
Step 2 Run the following command to check the status of the RCOMMAdapter port of the CBP:
% netstat -an | grep 8060
tcp4
10.10.11.3.8060
*.*
LISTEN
NOTE
Here, the port number 8060 is only for reference. To view the specific port number, use the configadm
tool.

% configadm
===============================================
ENIP config admin: Main
===============================================
[1] Key-value config data operations
[2] Config table operations
[3] Backup-Restore operations
[0] Exit
Please select option :1
===============================================
ENIP config admin: Main > Key-value config data
===============================================
[1] Add config item
[2] Delete config item
[3] Delete config item tree
[4] Update config item
[5] Read Item
[6] Read values
[7] Load values from file
[0] Previous menu
**********************Read values**********************
Enter the key : ENIP
Do you want to write the records to a file?
Press "y" to confirm, any other key to cancel :
Communicating with config center ...
Number of records fetched: 114
key1:
ENIP.Common.SMCenter.ftp.username
value1:
enip
Issue 01 (2010-09-29)

3-65
HUAWEI CBS
3 Daily Maintenance
key2:
ENIP.Common.SMCenter.TransferType
value2:
ENIP.Individual.DOID://0000000A/000000B4/00004650/00004650.RCOMM.Server.PORT.
value70:
8060
Step 3 Run the following command to check the status of the icdcomm port of the CBP:
% netstat -an | grep -w 8888
tcp4
tcp4
tcp4
tcp4
tcp4
tcp4
0
0
0
0
0
0
0
0
0
0
0
3528
172.18.3.20.8888
*.8888
172.18.3.20.8888
172.18.3.20.8888
172.18.3.22.33358
172.18.3.22.33656
172.18.3.10.51353
*.*
172.18.3.32.54855
172.18.3.31.56676
172.18.3.10.8888
172.18.3.30.8888
ESTABLISHED
LISTEN
ESTABLISHED
ESTABLISHED
ESTABLISHED
ESTABLISHED
NOTE
Here, the port number 8888 is only for reference. For the specific port number, see the value of
ICDTCPPORT in the ${HOME}/config/icdcomm.cfg file.
----End
Exception Handling
Check whether the RCOMMAdapter and the icdcomm service are started. If you still cannot
solve the problem, contact Huawei engineers.
3.7.7 Checking the Status of the BMP Ports

This task is performed to check whether the status of the BMP ports is normal.
Reference Standard
Precaution
None.
Procedure
Step 1 Log in to the active node as the bmp user.
Step 2 Run the following command to view the status of the port for the WebService to send product
management requests:
The system displays information similar to the following:
tcp
3-66
*.8686
*.*

LISTEN
Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
NOTE
Here, the port number 8686 is only for reference. For the specific port number, see the value of port in the
WebService manage interface section in the ${HOME}/jboss/server/default/deploy/jbosswebtomcat55.sar/server.xml file.
Step 3 Run the following command to check the status of the RCOMMAdapter port of the BMP:
tcp4
172.18.3.20.8060
*.*
LISTEN
NOTE
Here, the port number 8060 is only for reference. To view the specific port number, use the configadm
tool.

% configadm
===============================================
ENIP config admin: Main
===============================================
[1] Key-value config data operations
[2] Config table operations
[3] Backup-Restore operations
[0] Exit
===============================================
ENIP config admin: Main > Key-value config data
===============================================
[1] Add config item
[2] Delete config item
[3] Delete config item tree
[4] Update config item
[5] Read Item
[6] Read values
[7] Load values from file
[0] Previous menu
**********************Read values**********************
Enter the key : ENIP
Do you want to write the records to a file?
Press "y" to confirm, any other key to cancel :
Communicating with config center ...
Number of records fetched: 114
key1:
ENIP.Common.SMCenter.ftp.username
value1:
enip
key2:
ENIP.Common.SMCenter.TransferType
value2:
...
ENIP.Individual.DOID://0000000A/000000B4/00004650/00004650.RCOMM.Server.PORT.
value70:
8060
...
Step 4 Run the following command to check the status of the icdcomm listen port of the BMP:
Issue 01 (2010-09-29)

3-67
HUAWEI CBS
3 Daily Maintenance
tcp4
tcp4
tcp4
tcp4
tcp4
tcp4
0
0
0
0
0
0
0
0
0
0
0
0
172.18.3.10.51353
*.8888
172.18.3.10.56356
172.18.3.10.56357
172.18.3.10.8888
172.18.3.10.8888
172.18.3.20.8888
*.*
172.18.3.31.8888
172.18.3.32.8888
172.18.3.22.33358
172.18.3.21.65105
ESTABLISHED
LISTEN
ESTABLISHED
ESTABLISHED
ESTABLISHED
ESTABLISHED
The previous information indicates that the port number 8888 of the local host is listened and
the local host is connected to different hosts through this port.
NOTE
Here, the port number 8888 is only for reference. For the specific port number, see the value of
ServerPort in the ${HOME}/config/icdcomm.cfg file.
----End
Exception Handling
Check whether the Jboss, RCOMMAdapter and the icdcomm service are started. If you still
cannot solve the problem, contact Huawei engineers.
3.7.8 Checking the Status of the SCP Ports

This task is performed to check whether the status of the SCP ports is normal.
Reference Standard
Precaution
l
In HDR mode, you need to check the ports only on the active node and check the connection
port between the active node and standby node.
In shared disk mode, you need to check the ports only on the active node.
Procedure
Step 1 Log in to the active node as the scu user.
Step 2 Obtain port numbers for the SCU connecting to the SAU, SMP, and FEP by checking the port
settings in the scusys.cfg file in $TELLIN_DIR/config/.
Step 3 Check the status of the ports.
% netstat -an | grep port number
----End
Exception Handling
If the check result does not meet the check standard, do as follows:
Step 1 Verify that the ports are configured correctly.
Step 2 Ping the peer IP address to verify that the network works normally.
3-68

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Step 3 Verify that the applications of the peer node are running normally.
----End
3.7.9 Checking the Interface Connection Status on the DCC Proxy

This topic describes how to check the connection status of each interface on the DCC proxy.
Reference Standard
Each interface is connected normally and the connection status is ESTABLISHED.
Precaution
None.
Procedure
Step 1 Log in to the active node and standby node of the DCC proxy as the dcc user.
Step 2 Check the icdcomm.cfg file to obtain the port number of the ICDComm link.
1.
dcc% cat ${HOME}/config/icdcomm.cfg

ICDTCPPORT=8816
2.
Run the following command to check the connection of the interface specified by the
preceding port number.
dcc% netstat -an | grep 8816
3.
If the system displays ESTABLISHED, it indicates that the interface connection is normal.
tcp
LISTEN
tcp
0 10.10.14.13:8816
0.0.0.0:*
0 10.10.14.13:8816
10.10.13.13:5674
ESTABLISHED
Step 3 Check the NMAdptCfg.xml file to obtain the listening port number of the UOA connected to
NMAdapter0.
1.
dcc% cat ${HOME}/config/NMAdptCfg.xml

<NMACfg uoaipaddr="10.10.10.1" uoaport="6800"/>
2.
dcc%netstat an | grep 6800
3.
tcp
LISTEN
tcp
0 10.10.14.13:6800
0.0.0.0:*
0 10.10.14.13:6800
10.10.13.13:54295
ESTABLISHED
Step 4 Check the DiamBaseConfig.xml file to obtain the port number of the DCC proxy.
1.
dcc% cat ${HOME}/config/DiamBaseConfig.xml

LocalInfo Port="6553"
2.
dcc% netstat -an | grep 6553
3.
Issue 01 (2010-09-29)
3-69
HUAWEI CBS
3 Daily Maintenance
tcp4
tcp4
0
0
0
0
10.10.14.13.6553
10.10.14.13.6553
*.*
10.10.13.13.52624
LISTEN
ESTABLISHED
----End
Exception Handling
None.
3.7.10 Checking the Run Logs of the CBP

CBP.
Reference Standard
The keyword error, warning, emerg, alert, and critical do not exist in the log files.
Precaution
None.
Procedure
Step 1 Log in to the active node as the cbp user.
Step 2 Check the log files in the $HOME/log/run.
Only the last 1000 rows of run logs in each log file are required:
For example, to read the last 1000 rows of run logs in the rDiamMsgRating_c900.log file, run
the following command:
% tail -1000 rDiamMsgRating_c900.log
----End
Exception Handling
Locate the fault according to error information. For log details, see the HUAWEI ENIP Log
Reference. If the fault persists, contact Huawei engineers.
3.7.11 Checking the Run Logs of the BMP

BMP.
Reference Standard
The keyword error and warning do not exist in the log files.
Precaution
None.
3-70

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Procedure
Step 1 Log in to the active node as the bmp user.
Step 2 Check the log files in the $HOME/log/run.
----End
Exception Handling
3.7.12 Checking the Run Logs of the SCP

SCP.
Reference Standard
The keyword error and warning do not exist in the log files.
Precaution
For the SCP two-node cluster in hot standby mode, perform the following operations on the
For the SCP two-node cluster in cold standby mode, the following steps need to be performed
Procedure
Step 1 Log in to the active node as the scu user.
Step 2 Check the log files in the ${TELLIN_DIR}/temp.
The rule for naming run log files is as follows:
l
If a process relates to a single node, the rule for naming the log file is <Module
Name>_<Process Number>.run. For example, manager_0.run.
If a process relates to multiple nodes, the rule for naming the log file is <Module
Name>_<Node Number>_<Process Number>.run. For example, scf_0_1.run.
----End
Exception Handling
3.7.13 Checking the Run Log of the DCC Proxy

To check the running logs to detect the faults in the system.
Issue 01 (2010-09-29)

3-71
HUAWEI CBS
3 Daily Maintenance
Reference Standard
There are no records of ERROR, EMERGENCY, ALERT, and CRITICAL in the run log.
Precaution
None.
Procedure
Step 1 Log in to the active node of the DCC proxy as the dcc user.
Step 2 Run the following command to access the run log directory:
dcc% cd log/run
Step 3 Check the rDiamAdapter_c120.log log and check whether error logs exist.
dcc% more rDiamAdapter_c120.log | grep ERROR
----End
Exception Handling
Locate the fault according to the error information. If the fault persists, contact Huawei engineers.
3.7.14 Checking the GFEP Run Log

This topic describes how to check whether the GFEP run log contains the WARNING and
ERROR information.
Reference Standard
Check whether the GFEP run log contains the WARNING and ERROR information by viewing
log files.
Precaution
None.
Procedure
Step 1 Log in to the GFEP active node as the GFEP user.
Step 2 Access the GFEP log directory.
% cd $HOME/fep/log
Step 3 Check whether the GFEP run log contains the WARNING and ERROR information by viewing
log files.
% view genfep.log
----End
Exception Handling
Locate the fault according to the error information. If the fault persists, contact Huawei engineers.
3-72

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
3.7.15 Checking the Run Logs of the RBI

This task is to check that the run logs of the RBI do not contain error or warning information.
The purpose is to ensure that the RBI can transfer CDR files normally.
Reference Standard
The logs in the log directory do not contain error or warning information.
Precaution
None.
Procedure
Step 1 Log in to the RBI host as an RBI user.
Step 2 Access the RBI log directory.
%cd $RBI_DIR/log/log
Step 3 Check whether the run logs of the RBI contain the error or warning information.
%view RBIManage0_000000.log
%view Usf0_000000.log
%view RBICollect_*.log
%view RBISend_*.log
----End
Exception Handling
If any error information exists in the logs, locate the error as follows:
1.
2.
Locate the error according to the error information.

l
If an error occurs in the modules such as the collection and sending modules, the logs
of the main control module also record the error information.
If an error occurs in the main control module, find the specific neighboring module
where the error occurs according to the error information, and then obtain the error
information in the logs of the neighboring module.
Locate the error according to the error information in the logs of the specific module. For
example, the RBIManage0_000000.log file contains the following error information:
LogOS 2009-10-10 14:22:16
normal socket[7] was error to be closed! errno:
104, error info:Connection reset by peer
LogOS 2009-10-10 14:22:16
normal Disconnection from :10.164.106.39[7]
The preceding error information indicates that the connection between the client
10.164.106.39 and the RBI is abnormal. The error is generally due to incorrect client
configurations. In this case, check the client configurations.
3.
Issue 01 (2010-09-29)
If the error persists, contact Huawei engineers.

3-73
HUAWEI CBS
3 Daily Maintenance
3.7.16 Checking the Number of CDRs on the CBP

This task is to check that the number of CDRs on the CBP does not increase or decrease
significantly. The purpose is to ensure that all the required fees are collected from subscribers.
Therefore, the revenue of the carrier can be ensured.
Reference Standard
The number of CDRs that are generated on the current day is in the normal range. That is,
compared with the number of CDRs that are generated yesterday, the number of CDRs that are
generated on the current day does not decrease significantly. Generally, if the number of CDRs
decreases by more than 5%, you can consider this situation abnormal. The significant decrease
in special days such as holidays, however, can be considered normal.
Precaution
None.
Procedure
Step 1 Log in to the CBP as a CBP user.
Step 2 Access the CDR directory.
%cd ${CBP_CDRPATH}/output/pps/normal
NOTE
If a backup directory has been planned, you can search the backup directory for CDRs. For the path to each
type of CDR, see the HUAWEI OCS Call Detail Record Reference.
Step 3 Run the following commands to count the CDRs of the current day and yesterday respectively
by taking 2009-08-11 and 2009-08-10 as examples:
%wc -l rec20090811*.unl
%wc -l rec20090810*.unl
Step 4 Compare the number of CDRs that are generated on the two days and determine whether the
number of CDRs of 2009-08-11 decreases significantly according to experiential data. If yes,
see Exception Handling.
----End
Exception Handling
If the number of CDRs of a day is abnormal, perform the following steps:
1.
Access the error or fail directory of the CDRs.

%cd ${CBP_CDRPATH}/output/pps/error
%cd ${CBP_CDRPATH}/output/pps/fail
2.
Check whether either of the two directories contains the CDR files that are generated on
the current day.
l
3-74
If yes, pack the CDR files and submit them to Huawei engineers.
Issue 01 (2010-09-29)
HUAWEI CBS
l
3 Daily Maintenance
If no, contact Huawei engineers and inform them of the value by which the number of
CDRs decreases, or keep observing the change of the number of CDRs.
3.7.17 Checking the Offline CDR on the CBP

This task is to check that the offline CDRs on the CBP are processed normally. The purpose is
to ensure that all the required fees are collected from subscribers. Therefore, the revenue of the
carrier can be ensured.
Reference Standard
The error CDR directory of the offline CDRs on the CBP does not contain offline CDR files.
NOTE
Generally, when a fault occurs in the CBP or an exception occurs in the message link, the system passes
by services. After the CBP is recovered or the message link becomes normal, the SCP sends DCC messages
to request the CBP to perform authentication and charging and sends the CDRs that are generated during
the passby to the CBP for rating. Therefore, all the required fees are collected from subscribers.
Precaution
None.
Procedure
Step 1 Log in to the CBP as a CBP user.
Step 2 Access the error CDR directory of a specific service in the offline CDR subdirectory. Here, the
offline CDR directory of the voice service is used as an example.
%cd ${CBP_CDRPATH}/input/scpabr/voice/err
Step 3 Run the ls command to check whether certain files exist in the error directory. If yes, it indicates
that offline CDRs exist.
----End
Exception Handling
If certain offline CDRs exist, perform the following steps:
1.
Open an offline CDR file, and then determine whether an exception occurs according to
the meanings and value ranges of the fields in the CDR by referring to the HUAWEI CBS
Call Detail Record Reference. For example, if the value of the field indicating the deducted
fee is 0, or the value of the field indicating the policy ID for rating is incorrect, you can
infer that an exception occurs.
2.
Pack the offline CDR file and submit it to Huawei engineers.
3.7.18 Checking the Scheduled Tasks on the BMP

This topic describes how to check the scheduled tasks in the system. After checking these
scheduled tasks, you can ensure that the services performed by the tasks run normally.
Issue 01 (2010-09-29)

3-75
HUAWEI CBS
3 Daily Maintenance
Reference Standard
No records with running result being failed are displayed on the Query Result tab page.
Procedure
Step 2 Choose System > Task > BMP task Execution Result.
Step 3 Select failed from the Execution result drop-down list box.
Step 4 Click Query to check whether any failure records are displayed on the Query Result tab page.
----End
Exception Handling
If certain failure records are displayed on the Query Result tab page, contact Huawei
maintenance engineers and provide the query result.
3.7.19 Checking the AR Task

This topic describes how to check the running status and exception of the journal task and journal
collecting task.
Reference Standard
Task logs do not record any exceptions.
Procedure
Step 2 Choose Account Receivable > Query > Task Log
Step 3 Select the task type and running time, and then click Query. The system displays the
corresponding logs.
Step 4 In the logs record any exceptions, click
to view the details.
----End
Exception Handling
If exceptions occur in the running of a task, all the exceptions are recorded in the corresponding
task logs. You can handle the exceptions based on exception information.
If the system displays a message similar to "The G/L code is not found," the cause is that the G/
L code is not configured. To solve this problem, access the AR menu, choose Setting > G/L
Account, and then configure the G/L code.
3.7.20 Checking the Running of the SSMFEP

This task is to check that the SSMFEP process exists. The purpose is to ensure the normal running
of the SSMFEP and normal delivery of offline short messages.
3-76

Issue 01 (2010-09-29)
HUAWEI CBS
3 Daily Maintenance
Reference Standard
The SSMFEP process exists, and the process ID remains unchanged.
Precaution
None.
Procedure
Step 1 Log in to the SCP as the scu user.
%ps -ef | grep ssmfep
The system displays the following information:
scu 5667
1 0 Aug 19 ?
43:18 /bin/ksh /tellin/scu/iinas/serplus/
seragent/bin/ssmfepstatcpu.sh 5
scu 3554
1 0 Aug 19 ?
158:10 ./ssmfep
scu 12492 11592 0 10:17:01 pts/tc
0:00 grep ssmfep
Step 3 Run the preceding command again, and then check whether the process exists and whether the
process ID changes. If the process does not exist or the process ID changes, see Exception
Handling.
----End
Exception Handling
The crontab starts the monitoring process every half an hour to monitor the running of the
SSMFEP process. If the SSMFEP process does not exist, the monitoring process starts the
SSMFEP process. If the SSMFEP process exists, the monitoring process exits, and no manual
processing is required.
3.7.21 Checking the Connection of the GFEP and Other Devices

This task is to check the connections between the GFEP and other devices such as the SMSC.
The purpose is to ensure the normal communication between components.
Reference Standard
The value of Connection State of the devices whose Connection ID is greater than 20 is OPEN.
NOTE
The connection IDs that are smaller than or equal to 20 are internal system IDs. When you check the connections
between the GFEP and other devices, you need to pay attention to only the connection IDs that are greater than
20.
The value of Connection ID varies according to the device that the GFEP is connected to. When the GFEP is
connected to the SMSC, two connection IDs exist. You can view the IP address and port number of the peer
device corresponding to each connection ID by choosing Browse > Connection Information.
Precaution
None.
Issue 01 (2010-09-29)

3-77
HUAWEI CBS
3 Daily Maintenance
Procedure
Step 1 Start and log in to the GFEP client.
Step 2 Right-click Connection in the navigation tree, and then choose State.
The Connection State window shown in Figure 3-17 is displayed.
Figure 3-17 Connection status of the GFEP client
Step 3 Check the connections between the GFEP and other devices. For example, check that the status
of the connection between the GFEP and the SMSC is OPEN.
----End
Exception Handling
If the GFEP is disconnected from a device, perform the following steps:
1.
Log in to the GFEP host as a GFEP user.
2.
Run the following command to obtain the running status of the GFEP server, and then check
whether the four important processes of the GFEP server exist:
%fep stat
gfep
gfep
gfep
gfep
29909
29911
29908
24964
1
1
1
1
0
1
0
0
05:17:11
05:17:11
05:17:11
05:17:12
- 0:00 ./keeper
- 54:42 ./genfep
- 0:25 ./dbServer
- 0:43 ksh ./collect.sh
Run the preceding command repeatedly to check whether the four processes are normal. If
a process is abnormal or does not exist, perform the following step.
3.
Run the following commands in sequence to restart the GFEP.

%fep stop
%fep start
3-78

Issue 01 (2010-09-29)
HUAWEI CBS
4.
3 Daily Maintenance
If the exception persists, contact Huawei engineers.
3.7.22 Checking That the RBI Transfers CDRs Normally

This task is to check that the RBI transfers CDRs in time. The purpose is to prevent incorrect
charging caused by non-transfer of CDRs and insufficient disk space caused by CDR pileup on
the RBI.
Reference Standard
The CDRs in the source path are transferred to the destination path.
Figure 3-18 shows the source path and destination path of the sending module on the RBI client.
Figure 3-18 Source path and destination path of the sending module on the RBI client
Precaution
None.
Procedure
Step 1 Log in to the RBI host as an RBI user.
Step 2 Run the following command to view the source path of the CDRs to be transferred by the RBI.
The command uses the background configuration file as an example.
%view $RBI_DIR/config/RBISend.cfg
Issue 01 (2010-09-29)

3-79
HUAWEI CBS
3 Daily Maintenance
The WorkDir configuration item in the background configuration file indicates the source path
of the CDRs to be transferred by the RBI.
Step 3 Access the source directory of the CDRs to check whether the directory contains CDRs that are
not transferred in time.
The RBI transfers the CDRs in real time. If there are CDRs generated 30 minutes before, the
CDRs may be not transferred in time. You can perform the following steps to further check
whether the CDRs are transferred in time. If the RBI transfers the CDRs in time, you do not
need to perform the following steps.
Step 4 Access the log directory of the RBI.
%cd $RBI_DIR/log/log
Step 5 View the log file and check that there is no error information similar to error move remote file
xxx unmoveremote to xxx fail.
%view RBISend_*.log
----End
Exception Handling
If the log contains error information, it indicates that the CDRs are not transferred in time. In
this case, locate the exception as follows:
3-80
1.
Check that the information such as the IP address, access user, and path in the file
$RBI_DIR/config/RBISend.cfg are the same as those of the actual environment.
2.
Check that the source directory of each sending module or filtering module on the local
RBI node is different. If the source directories of certain sending modules or filtering
modules are the same, the CDR files of a certain sending module or a certain filtering
module may be sent to another path.

Issue 01 (2010-09-29)
HUAWEI CBS
4 Weekly Maintenance
Weekly Maintenance
About This Chapter

This topic describes the maintenance items that need to be performed every week. All the
maintenance items are performed manually.
4.1 Backing Up the Log Files (CBP)
This task is performed to back up CBP log files. Thus, the backup files can be used to restore
the system in case of exceptions. In addition, backup log files need to be stored on other media
to prevent insufficient disk space.
4.2 Backing Up the Log Files (BMP)
This task is performed to back up BMP log files. Thus, the backup files can be used to restore
4.3 Backing Up the Log Files (SCP)
This task is performed to back up SCP log files. Thus, the backup files can be used to restore
4.4 Backing Up the Log Files (Billing)
This task is performed to back up Billing log files. Thus, the backup files can be used to restore
4.5 Backing Up the Log Files (AR&DC)
This task is performed to back up AR&DC log files. Thus, the backup files can be used to restore
4.6 Backing Up the Log Files (SMP)
This task is performed to back up SMP log files regularly. Thus, the backup files can be used to
restore the system in case of exceptions. In addition, backup log files need to be stored on other
media to prevent insufficient disk space.
4.7 Backing Up Log Files on the UVC
This topic describes how to back up the log files in specified directories of the SCP on the UVC
and to delete the log files after backing up them.
Issue 01 (2010-09-29)

4-1
HUAWEI CBS
4.8 Backing Up Log Files on the EVC

This topic describes how to back up the log files in specified directories of the SCP on the EVC
4.9 Backing Up and Clearing History CDRs on the RBI
This task is to back up the history CDRs on the RBI and clear the history CDRs after backing
up them. The purpose is to ensure the sufficient space of the CDR directory, thus preventing the
CDR transfers to other systems from being blocked.
4-2

Issue 01 (2010-09-29)
HUAWEI CBS
4.1 Backing Up the Log Files (CBP)

This task is performed to back up CBP log files. Thus, the backup files can be used to restore
Prerequisite
l
The disk or tape for backup has sufficient available space.
The user who back up files has the write and execute permissions to the backup directory.
Context
None.
Procedure
Step 1 Log in to the active node of the CBP system as the cbp user.
Step 2 Run the following command to compress the log files.
In the following command, the log file package is named cbp.log090710.tar.
% tar -cvf cbp.log090710.tar ${HOME}/log/*
Step 3 Store the log file package to the planned backup directory, such as the mount directory /
backup of lvbackup.
% mv cbp.log090710.tar /backup
Step 4 Run the following command to delete the log files that are backed up.
% rm -rf ${HOME}/log/*
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
Issue 01 (2010-09-29)

4-3
HUAWEI CBS
2.
4.2 Backing Up the Log Files (BMP)

This task is performed to back up BMP log files. Thus, the backup files can be used to restore
Prerequisite
l
The user who backs up files has the write and execute permissions to the backup directory.
Context
None.
Procedure
Step 1 Log in to the active node of the BMP system as the bmp user.
In the following command, the log file package is named bmp.log090710.tar.
% tar -cvf bmp.log090710.tar ${HOME}/log/*
backup of lvbackup.
% mv bmp.log090710.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
4-4

Issue 01 (2010-09-29)
HUAWEI CBS
2.
4.3 Backing Up the Log Files (SCP)

This task is performed to back up SCP log files. Thus, the backup files can be used to restore
Prerequisite
l
Context
None.
Procedure
Step 1 Log in to the active node of the SCP system as the scu user.
% tar -cvf scu.log.tar ${TELLIN_DIR}/log/*
backup of lvbackup.
% mv scu.log.tar /backup
% rm -rf ${TELLIN_DIR}/log/*
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
Issue 01 (2010-09-29)

4-5
HUAWEI CBS
2.
4.4 Backing Up the Log Files (Billing)

This task is performed to back up Billing log files. Thus, the backup files can be used to restore
Prerequisite
l
The user who back up files has the write and execute permissions to the backup directory.
Context
None.
Procedure
Step 1 Log in to the active node of the Billing system as the billing user.
In the following command, the log file package is named billing.log090710.tar.
% tar -cvf billing.log090710.tar ${HOME}/BILLING/log/*
backup of lvbackup.
% mv billing.log090710.tar /backup
% rm -rf ${HOME}/BILLING/log/*
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
4-6

Issue 01 (2010-09-29)
HUAWEI CBS
2.
4.5 Backing Up the Log Files (AR&DC)

This task is performed to back up AR&DC log files. Thus, the backup files can be used to restore
Prerequisite
l
Context
None.
Procedure
Step 1 Log in to the active node of the AR&DC system as the ar user.
In the following command, the log file package is named ar.log090710.tar.
% tar -cvf ar.log090710.tar ${HOME}/log/*
backup of lvbackup.
% mv ar.log090710.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
Issue 01 (2010-09-29)
HP
4-7
HUAWEI CBS
# bdf
2.
4.6 Backing Up the Log Files (SMP)

This task is performed to back up SMP log files regularly. Thus, the backup files can be used to
restore the system in case of exceptions. In addition, backup log files need to be stored on other
media to prevent insufficient disk space.
Prerequisite
l
Context
None.
Procedure
Step 1 Log in to the active node of the SMP system as the smp user.
In the following command, the log file package is named smp.log090710.tar.
% tar -cvf smp.log090710.tar ${HOME}/smp_run/log/*
backup of lvbackup.
% mv smp.log090710.tar /backup
% rm -rf ${HOME}/smp_run/log/*
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
4-8
HP
Issue 01 (2010-09-29)
HUAWEI CBS
# bdf
2.
4.7 Backing Up Log Files on the UVC

This topic describes how to back up the log files in specified directories of the SCP on the UVC
Prerequisite
None.
Context
You need to manually back up important log files to the tape drive periodically. You can back
up common log files as required. During backup, you need to move the log files to the backup
directory, and then compress, pack, and back up the log files to the tape drive.
Generally, you cannot delete log files manually. You can delete the log files only after they are
backed up.
Procedure
Step 1 Log in to the UVC as the scu user.
Step 2 Run the following command to access the log directory:
cd ${TELLIN_DIR}/log
Step 3 Pack the log files.
% tar -cvf uvc.log090710.tar ${TELLIN_DIR}/log/*.log
Step 4 Save the packed log files to the planned directory.
% mv uvc.log090710.tar /backup
Step 5 Delete the log files that are backed up.
% rm -f ${TELLIN_DIR}/log/*.log
----End
Exception Handling
1.

Issue 01 (2010-09-29)

4-9
HUAWEI CBS
l
IBM/ATAE
# df -m
HP
# bdf
2.
4.8 Backing Up Log Files on the EVC

This topic describes how to back up the log files in specified directories of the SCP on the EVC
Prerequisite
None.
Context
You need to manually back up important log files to the tape drive periodically. You can back
up common log files as required. During backup, you need to move the log files to the backup
directory, and then compress, pack, and back up the log files to the tape drive.
Generally, you cannot delete log files manually. You can delete the log files only after they are
backed up.
Procedure
Step 1 Log in to the EVC as the scu user.
Step 2 Run the following command to access the log directory:
cd ${TELLIN_DIR}/log
Step 3 Pack the log files.
% tar -cvf evc.log090710.tar ${TELLIN_DIR}/log/*.log
Step 4 Save the packed log files to the planned directory.
% mv evc.log090710.tar /backup
Step 5 Delete the log files that are backed up.
% rm -f ${TELLIN_DIR}/log/*.log
----End
Exception Handling
4-10

Issue 01 (2010-09-29)
HUAWEI CBS
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.
4.9 Backing Up and Clearing History CDRs on the RBI

This task is to back up the history CDRs on the RBI and clear the history CDRs after backing
up them. The purpose is to ensure the sufficient space of the CDR directory, thus preventing the
CDR transfers to other systems from being blocked.
Prerequisite
l
The disk or tape for storing the backup data has sufficient space.
The user who backs up CDRs has the write and execute permissions on the backup directory.
Context
NEs have the mechanism of automatically backing up and clearing history CDRs.
l
The SCP periodically invokes the billadm program to delete the CDRs that are generated
N days before, in which N is specified by BAKRECORD_KPDAYS.
The CBP periodically runs the script for deleting CDRs periodically through the
crontab. When the RBI is available, the RBI takes away the CDRs so that the CDRs can
be deleted and backed up on the RBI.
NOTE
The frequency of backing up and clearing the history CDRs of an office depends on the size of the directory for
storing CDRs and the number of subscribers of the office. If there are a large number of subscribers, you need
to back up and clear history CDRs every day.
Table 4-1 describes the key configuration files and configuration items of the RBI. You can
obtain the CDR backup paths on the RBI through the configuration items, and then clear the
CDR files from the backup paths periodically.
Table 4-1 Description of configuration items
Issue 01 (2010-09-29)
Configuratio
n File
Configuratio
n Item
Description
RBICollect.cfg
RemoteDir
Path of external NEs, from which the RBI obtains the

CDRs.

4-11
HUAWEI CBS
Configuratio
n File
RBISend.cfg
Configuratio
n Item
Description
CollectDir
Path for storing the CDRs obtained by the RBI.
CollectBackup
Dir
Path where the RBI backs up the collected files. This path
needs to be cleared periodically.
WorkDir
Source path of CDRs to be transferred by the RBI.

l
If the formats of the CDRs obtained by the RBI need

to be converted, the CDRs are obtained from the
directory specified by CollectDir in the
RBICollect.cfg file. The conversion result is saved in
the directory specified by WorkDir in the
RBISend.cfg file.
If the format of CDRs obtained by the RBI does not

need to be converted, the directory specified by
CollectDir in the RBICollect.cfg file is the same as
the directory specified by WorkDir in the
RBISend.cfg file.
RemoteSendDi
r
Destination path of the CDRs to be transferred by the

RBI.
SendBackupDi
r
Directory of the CDRs that are backed up on the RBI host.

Because the files transferred by the RBI are collected
from other NEs, and the backup path is already set on the
collection module, no backup is required during transfer.
Therefore, you do not need to set this directory. If you set
this directory, this directory needs to be cleared
periodically.
NOTE
The RBICollect.cfg and RBISend.cfg files are stored in the path $RBI_DIR/config.
Procedure
Step 1 Log in to the active node of the RBI as the RBI user.
Step 2 Run the following command to check the directory of the CDRs that are backed up on the local
RBI host:
%view $RBI_DIR/config/RBICollect.cfg
The CollectBackupDir configuration item in the RBICollect.cfg file indicates the directory of
the CDRs that are backed up on the local RBI host.
Step 3 Move the CDRs that are backed up locally to the specified directory for backing up CDRs or
back up them to the tape drive.
----End
4-12

Issue 01 (2010-09-29)
HUAWEI CBS
Exception Handling
If an exception occurs during the backup, perform the following steps:
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.
Issue 01 (2010-09-29)

4-13
HUAWEI CBS
5 Monthly Maintenance
Monthly Maintenance
About This Chapter

This topic describes the maintenance items that need to be performed every month. Most of
maintenance items are performed manually.
5.1 Maintenance Items Related to Applications
This topic describes the maintenance items related to the applications of the CBS and
neighboring NEs.
5.2 Maintenance Items Related to Hardware
This section describes the maintenance items related to the hardware devices of the system.
5.3 Checking the Viruses on the Terminal Computer
This task is performed to periodically kill the viruses in the operating system where the SMAP
terminal is located to ensure the system security.
5.4 Checking Whether the Device Maintenance Contract Expires
This task is performed to check the device maintenance contract periodically to prevent service
quality decrease due to contract expiration.
Issue 01 (2010-09-29)

5-1
HUAWEI CBS
5.1 Maintenance Items Related to Applications

This topic describes the maintenance items related to the applications of the CBS and
neighboring NEs.
5.1.1 Changing the Passwords of Running Users
This topic describes how to change the passwords of the running users periodically to ensure
the system security.
5.1.2 Changing the Passwords of SMAP Operators
This task is to change the passwords of SMAP operators periodically to ensure the system
security.
5.1.3 Backing Up Configuration Files (CBP)
The configuration files of CBP are backed up once every month or before and after the system
upgrade. Thus, the files can be restored in case of exceptions. In addition, the backup files need
to be stored on other media to prevent insufficient disk space.
5.1.4 Backing Up Configuration Files (BMP)
The configuration files of BMP are backed up once every month or before and after the system
5.1.5 Backing Up Configuration Files (Billing)
The configuration files of Billing are backed up once every month or before and after the system
5.1.6 Backing Up Configuration Files (AR)
The configuration files of AR are backed up once every month or before and after the system
5.1.7 Backing Up Configuration Files (DC)
The configuration files of DC are backed up once every month or before and after the system
5.1.8 Backing Up Configuration Files (SCP)
The configuration files of SCP are backed up once every month or before and after the system
5.1.9 Backing Up Configuration Files (SMP)
The configuration files of SMP are backed up once every month or before and after the system
5.1.10 Backing Up Configuration Files of the GFEP
The GFEP automatically backs up the config directory every day. This task is to check that the
configuration files are backed up successfully every month and before or after an upgrade. The
purpose is to ensure that the configuration items can be restored when an error occurs. In addition,
you need to move the backup files to other media to prevent insufficient disk space.
5.1.11 Backing Up Configuration Files of the RBI
5-2

Issue 01 (2010-09-29)
HUAWEI CBS
This task is to back up the configuration files of the RBI before or after you modify the
configuration files or perform an upgrade through the RBI client. The purpose is to ensure that
the configuration files can be restored when an error occurs. In addition, you need to move the
backup files to other media to prevent insufficient disk space.
5.1.12 Backing Up Configuration Files of the iWeb
This topic describes how to back up configuration files, log files, and project files manually
before and after the upgrade. After the files are backed up successfully, you can move them to
other media through Export.
5.1.13 Backing Up the Application Program (CBP)
This task is performed to back up the CBP application program regularly. Thus, the application
program can be restored in case of exceptions. In addition, the backup files need to be stored on
other media to prevent insufficient disk space.
5.1.14 Backing Up the Application Program (BMP)
This task is performed to back up the BMP application program regularly. Thus, the application
5.1.15 Backing Up the Application Program (AR&DC)
This task is performed to back up the AR&DC application program regularly. Thus, the
application program can be restored in case of exceptions. In addition, the backup files need to
be stored on other media to prevent insufficient disk space.
5.1.16 Backing Up the Application Program (Billing)
This task is performed to back up the Billing application program regularly. Thus, the application
5.1.17 Backing Up Log Files on the USAU
This topic describes how to back up the log files in specified directories and to delete the log
files after backing up them.
5.1.18 Backing Up Log Files on the URP
5.1.19 Backing Up Log Files on the iWeb
5.1.20 Backing Up and Clearing CDR Files on the Billing
This topic describes how to back up the CDR files in history bill cycles to the storage space and
how to clear the CDR files that are already backed up.
5.1.21 Understanding the Service Trend Through iWeb Reports
This topic describes how to understand the changes and trend of service data such as the number
of new users, the total recharge amount, and CAPS.
5.1.22 Understanding Key Service Indexes Through the LBI System
The LBI system provides a basic KPI function to display carrier-concerned indexes in figures
and tables. In this way, carriers can understand the key indexes and their changes.
Issue 01 (2010-09-29)

5-3
HUAWEI CBS
5.1.1 Changing the Passwords of Running Users

This topic describes how to change the passwords of the running users periodically to ensure
the system security.
Prerequisite
The running users are as follows:
l
BMP system: The running users bmp and smp of the BMP system
CBP system: The running user cbp of the CBP system; The running user smdb of the SMDB
SCP system: The running user scu of the SCP system
Context
CAUTION
Certain passwords are saved in the configuration files. When you change a password, remember
to modify the configuration file that contains the password. If only the password is changed and
the configuration file is not modified, severe abnormality such as database access failure may
occur. When a customer service engineer changes a password, remember to confirm that the
configuration files should be modified. For details on analysis of user passwords, see A.2 Impact
Analysis Table of CBS Password Change.
You need to perform this maintenance item on both the active and standby nodes. Perform this
maintenance item on the active node first, and then perform this maintenance item on the standby
node when the services on the active node run normally.
The following procedure takes the operation of changing the password for the user bmp as an
example.
Procedure
Step 1 Log in to the BMP system as the root user.
Step 2 Run the following command to change the running user password.
# passwd bmp
Step 3 Set the new password according to the system prompts.
----End
Exception Handling
If an exception occurs during password change, for example, the database cannot be connected,
check the following:
5-4
1.
Whether the configuration files and database tables that involve the user password are
modified
2.
Whether the encrypted text is generated through the correct encryption method and entered
in the configuration file
Issue 01 (2010-09-29)
HUAWEI CBS
If the preceding configurations are correct, but the fault persists, perform the following steps:
1.
Restore all the files and database tables that are modified and use the old password to ensure
the normal running of the system.
2.
Record the password change process, and send the changed password and modified files
and database tables to Huawei engineers.
5.1.2 Changing the Passwords of SMAP Operators

This task is to change the passwords of SMAP operators periodically to ensure the system
security.
Context
The sysadmin user is the super user of the SMAP and has all the menu rights and function rights
of the SMAP. The sysadmin user can create other users including business operators and can
change the passwords of other users.
Procedure
Step 1 Enter the URL of the SMAP in the address box of the browser, for example, http://
10.10.10.1:8080
Step 2 Log in as an SMAP operator.
Step 3 Click
in the upper right corner of the page.
The system displays the User Information tab page.

Step 4 Change the password as shown in Figure 5-1.
Figure 5-1 Changing the password of an SMAP operator
TIP
You can click Verify to verify whether the new password can be used.
Step 5 Click Save.

Step 6 Log in to the server as the SMAP operator again to verify that the password is changed
successfully.
----End
Issue 01 (2010-09-29)

5-5
HUAWEI CBS
Exception Handling
If the SMAP operator forgets the login password, or the system displays a message indicating
that the password is incorrect during login of the SMAP operator, perform the following steps:
1.
Log in as the sysadmin user.
2.
Choose System Console > System Management > User in the navigation tree of the
SMAP.
3.
Set the conditions for querying the SMAP operator. In the query results, click the password
resetting button
in the desired record. The Reset Password page is displayed.
4.
Modify the password.
5.
Click Save.
6.
Log in to the server as the SMAP operator again to verify that the password is changed
successfully.

Prerequisite
l
Context
CAUTION
The backup operation is performed in idle time.
Both the active node and standby node need to be backed up.Take the operation in the active
node for example.The standby node don't need to be backed up for the cold two-node cluster.
Procedure
Step 2 Run the following command to compress the configuration files in the relevant CBP directories:
cbp% tar -cvf cbp.config.conf20090710.tar ${HOME}/config
cbp% tar -cvf cbp.addons.conf20090710.tar ${HOME}/add-ons/config
Step 3 Store the configuration file package to the planned backup directory, such as the mount
directory /backup of lvbackup.
cbp% mv cbp.config.conf20090710.tar /backup
5-6

Issue 01 (2010-09-29)
HUAWEI CBS
cbp% mv cbp.addons.conf20090710.tar /backup

----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
l
Context
CAUTION
For details of configuration files, see the HUAWEI ENIP Configuration File Reference. This
document describes the paths, functions, configuration methods of the configuration files.
Procedure
Issue 01 (2010-09-29)

5-7
HUAWEI CBS
Step 2 Run the following command to compress the configuration files in the relevant BMP directories:
% tar -cvf bmp.config.conf20090710.tar ${HOME}/config
% tar -cvf bmp.addons.conf20090710.tar ${HOME}/add-ons/config
% tar -cvf bmp.jboss.conf20090710.tar ${HOME}/jboss/server/default/conf
% mv bmp.config.conf20090710.tar /backup
% mv bmp.addons.conf20090710.tar /backup
% mv bmp.jboss.conf20090710.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
5-8

Issue 01 (2010-09-29)
HUAWEI CBS
Context
CAUTION
Both the active node and standby node need to be backed up. Take the operation in the active
node for example. The standby node don't need to be backed up for the cold two-node cluster.
For details of configuration files, see the HUAWEI CBS Configuration File Reference. This
Procedure
Step 2 Run the following command to compress the configuration files in the relevant Billing
directories:
% tar -cvf billing.config.conf20090710.tar ${BILLING_HOME}/config/
% mv billing.config.conf20090710.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Issue 01 (2010-09-29)

5-9
HUAWEI CBS
Prerequisite
l
Context
CAUTION
Procedure
Step 1 Log in to the active node of the AR system as the ar user.
Step 2 Run the following command to compress the configuration files in the relevant AR directories:
% tar -cvf ar.jboss.conf20090710.tar ${JBOSS_HOME}/server/default/deploy/smap.ear/
default.war/WEB-INF/classes/conf/
% mv ar.jboss.conf20090710.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.
5-10

Issue 01 (2010-09-29)
HUAWEI CBS

Prerequisite
l
Context
CAUTION
Procedure
Step 1 Log in to the active node of the DC system as the dc user.
Step 2 Run the following command to compress the configuration files in the relevant DC directories:
% tar -cvf dc.jboss.conf20090710.tar ${JBOSS_HOME}/server/default/deploy/smap.ear/
% mv dc.jboss.conf20090710.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
Issue 01 (2010-09-29)

5-11
HUAWEI CBS
2.

Prerequisite
l
Context
CAUTION
Procedure
Step 2 Run the following command to compress the configuration files in the relevant SCP directories:
scu% tar -cvf scu.config.conf20090710.tar ${TELLIN_DIR}/config
scu% mv scu.config.conf20090710.tar /backup
----End
Exception Handling
1.

5-12

Issue 01 (2010-09-29)
HUAWEI CBS
l
IBM/ATAE
# df -m
HP
# bdf
2.
5.1.9 Backing Up Configuration Files (SMP)

The configuration files of SMP are backed up once every month or before and after the system
Prerequisite
l
Context
CAUTION
Procedure
Step 1 Log in to the active node of the SMP system as the smp user.
Step 2 Run the following command to compress the configuration files in the relevant SMP directories:
% tar -cvf smp.config.conf20090710.tar ${HOME}/sms_run/config
% tar -cvf smp.cfg.conf20090710.tar ${HOME}/sms_run/cfg
% tar -cvf smp.inetcfg.conf20090710.tar ${HOME}/sms_run/bin/inetcfg.cfg
% tar -cvf smp.license.conf20090710.tar ${HOME}/sms_run/bin/license.dat
% mv smp.config.conf20090710.tar /backup
Issue 01 (2010-09-29)

5-13
HUAWEI CBS
% mv smp.cfg.conf20090710.tar /backup
% mv smp.inetcfg.conf20090710.tar /backup
% mv smp.license.conf20090710.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
Context
During the startup of the GFEP, the backup script starts automatically, and the system
performance is not affected. Table 5-1 describes the method of backing up the GFEP
configuration files.
5-14

Issue 01 (2010-09-29)
HUAWEI CBS
Table 5-1 Method of backing up the GFEP configuration files

Backup Script
Mode
Backup
Content
Frequen
cy
Remarks
collect.sh
Pack files in backup of

the GFEP installation
directory.
config directory
in the GFEP
installation
directory
Every day
The backup
data of only
the latest
seven days is
reserved,
and the
backup data
that is
generated
seven days
before is
deleted.
The script starts

automatically
during the
startup of the
GFEP.
[Name format]:
GFEP.backup.config.YY
_MM_DD_HH_MM_SS
_Weekday.tar.gz
Procedure
Step 1 Log in to the GFEP host as the GFEP user.
Step 2 Access the backup directory of the GFEP.
%cd $HOME/fep/backup
Step 3 Check whether the backup is successful. Figure 5-2 shows the backup data of the seven days.
Figure 5-2 Checking the backup of the GFEP configuration files
Step 4 Maintenance engineers are advised to move the backup files to other media according to the
situation of the office.
----End
Exception Handling
1.

l
Issue 01 (2010-09-29)
IBM/ATAE
5-15
HUAWEI CBS
# df -m
l
HP
# bdf
2.

Prerequisite
Context
Before modifying a configuration file or performing an upgrade, you can back up the
configuration file through the RBI client. You can back up the configuration files of the following
modules as required:
l
RBIManage
RBICollect
RBISend
RBIFilter
RBICompress
RBICombine
Procedure
Step 1 Log in to the RBI client, namely, URBIConfig.
Step 2 Choose Main Control module in the navigation tree, as shown in Figure 5-3.
5-16

Issue 01 (2010-09-29)
HUAWEI CBS
Figure 5-3 RBI client window
Step 3 Choose Configurations > Backup.

The system displays the backup confirm dialog box. Click Yes in the dialog box.
Step 4 In the dialog box, enter Note name of the file that needs to be backed up, as shown in Figure
5-4.
Figure 5-4 Entering the backup information
Step 5 Click OK. The system displays a message indicating that the backup is successful. The
configuration files of the module are backed up in the path config/backup of the RBI user.
NOTE
If there are too many files in config/backup, you need to delete the discarded backup files.
Step 6 It is recommended that maintenance engineers move backup files to other media according to
the situation of the office.
----End
Issue 01 (2010-09-29)

5-17
HUAWEI CBS
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
Maintenance engineers must have the right of Maintenance.
Context
The iWeb page provides the backup menu, as shown in Figure 5-5. Maintenance engineers can
set Schedule so that the system backs up configuration files periodically.
Figure 5-5 iWeb backup menu
5-18

Issue 01 (2010-09-29)
HUAWEI CBS
Procedure
Step 1 Log in to the iWeb system.
Step 2 Choose Maintenance > Backup & Restore.
Step 3 Click Backup.
Step 4 In the displayed window, enter the backup name and click Ok.
Step 5 Maintenance engineers can back up files in *.bat to a specified place as follows:
1.
In the list, select the check box of one item before backup. You can select only one item.
2.
Click Export.
3.
In the displayed dialog box, click Save after confirming that the preceding configuration
is correct.
4.
In the displayed dialog box, select the storage place. You can change the backup name.
Then click Save.
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
l
Issue 01 (2010-09-29)

5-19
HUAWEI CBS
Context
CAUTION
The backup operation affects the I/O of the disk and the existing network greatly. In this case,
you need to perform backup in idle time, for example, 00:00 to 04:00.
Before backing up the application programs, ensure that the operation is approved and to be
performed by a dedicated person.
This section provides only directories to be backed up and the backup solution. For the method
and procedure of backup (charged), contact Huawei marketing.
The application programs are backed up in full backup mode. Both the active node and standby
node need to be backed up.
Procedure
Step 1 Log in to the active node and standby node of the CBP as the root user.
Step 2 Compress the files in the relevant CBP directories.
The directories on the CBP active node to be backed up are as follows:
l
/enip
/corefiles
/hwshare
/opt/informix
/oracle
The directories on the CBP standby node to be backed up are as follows:

l
/enip
/corefiles
/hwshare
/opt/informix
/oracle
The following describes how to back up the /enip directory.

% tar -cvf enip.tar /enip
Step 3 Store the application program package to the planned backup directory, such as the mount
The following describes how to save the /enip directory.
% mv enip.tar /backup
----End
5-20

Issue 01 (2010-09-29)
HUAWEI CBS
Exception Handling
1.

(1) Log in to the active node and the standby node as the root user.
l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
l
Context
CAUTION
Procedure
Step 1 Log in to the active node and standby node of the BMP as the root user.
Step 2 Compress the files in the relevant BMP directories.
Issue 01 (2010-09-29)

5-21
HUAWEI CBS
The directories on the BMP active node to be backed up are as follows:

l
/enip
/corefiles
/hwshare
/opt/informix
/opt/informix/temp
/oracle
The directories on the BMP standby node to be backed up are as follows:

l
/corefiles
/hwshare

bmp% tar -cvf enip.tar /enip
bmp% mv enip.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

5-22

Issue 01 (2010-09-29)
HUAWEI CBS
Prerequisite
l
Context
CAUTION
Procedure
Step 1 Log in to the active node and standby node of the AR&DC as the root user.
Step 2 Compress the files in the relevant AR&DC directories.
The directories on the AR&DC to be backed up are as follows: /${JBOSS_HOME}
The following describes how to back up the ${JBOSS_HOME} directory.
% tar -cvf jboss.tar /${JBOSS_HOME}
The following describes how to save the /jboss directory.
% mv jboss.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
Issue 01 (2010-09-29)
HP
5-23
HUAWEI CBS
# bdf
2.

Prerequisite
l
Context
CAUTION
Procedure
Step 1 Log in to the active node and standby node of the Billing as the root user.
Step 2 Compress the files in the relevant Billing directories.
The directories on the Billing to be backed up are as follows:
5-24
${BILLING_HOME}/bin
${BILLING_HOME}/config
${BILLING_HOME}/ebill
${BILLING_HOME}/install
${BILLING_HOME}/lib
${BILLING_HOME}/ShareLib
${BILLING_HOME}/tool
Issue 01 (2010-09-29)
HUAWEI CBS
The following describes how to back up the ${BILLING_HOME}/bin directory.

% tar -cvf bin.tar ${BILLING_HOME}/bin
The following describes how to save the ${BILLING_HOME}/bin directory.
% mv bin.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.
5.1.17 Backing Up Log Files on the USAU

Prerequisite
None.
Context
None.
Procedure
Step 1 Log in to the PC of the USAU.
Step 2 Open E:\MSSQL\Data. The folder contains *.log and *log.bak.
Step 3 Copy the folder to other disks or media.
----End
Issue 01 (2010-09-29)

5-25
HUAWEI CBS
Exception Handling
1.
2.

l
5.1.18 Backing Up Log Files on the URP

Prerequisite
None.
Context
None.
Procedure
Step 1 Log in to the PC where the URP is installed.
Step 2 Access E:\MSSQL\Data to view the generated logs.
Step 3 Copy important log files AlarmMaskLog and DeviceAlarmLog to other disks or storage media.
----End
Exception Handling
1.
2.

l
5.1.19 Backing Up Log Files on the iWeb

Prerequisite
5-26

Issue 01 (2010-09-29)
HUAWEI CBS
Context
Procedure
1.
2.
Click Export.
3.
is correct.
4.
Then click Save.
----End
Exception Handling
1.

l
Issue 01 (2010-09-29)
IBM/ATAE
5-27
HUAWEI CBS
# df -m
l
HP
# bdf
2.
5.1.20 Backing Up and Clearing CDR Files on the Billing

This topic describes how to back up the CDR files in history bill cycles to the storage space and
how to clear the CDR files that are already backed up.
Impact on the System

A large amount of bill data is saved in CDR files. Assume that every subscriber has about 50
pieces of bill data in a bill cycle. If there are one million subscribers, 50 million pieces of bill
data are generated. The bill data occupies a large amount of storage space. If the bill data is not
backed up and cleared during a long period, the space of the hard disks on the server will be
insufficient.
Prerequisite
None.
Tools and Materials

None.
Precaution
None.
Procedure
Step 1 Log in to the server through Telnet.
Step 2 Run the following command to switch to the CDR directory:
%cd $BILLING_HOME/DATA
Step 3 Access the sub directory, for example: CDR_POS/01/bak
Save the compressed bill data in history bill cycles to the memory.
Step 4 Delete the data that is already backed up.
----End
Related Information
None.
5-28

Issue 01 (2010-09-29)
HUAWEI CBS
5.1.21 Understanding the Service Trend Through iWeb Reports

This topic describes how to understand the changes and trend of service data such as the number
of new users, the total recharge amount, and CAPS.
Prerequisite
The WEBRPT module is already installed and you can access the iWeb reports through the URL.
Context
You must focus on the changes of the following service data:
l
Number of new subscribers
Total recharge amount
Call times
The names of the reports related to the preceding three types of data are as follows:
l
Report of subscribers
Report of cardrecharge
Report of cashrecharge
Call times status daily report
Through iWeb, you can check different data reports in the Report menu. You can also use the
Schedule menu and report templates to customize reports for different periods.
The following takes customizing the Number of Monthly New Users report as an example to
describe how to understand the service trend through iWeb reports.
Procedure
Step 1 Log in to the iWeb page through a browser.
Step 2 Click Schedule.
Step 3 Click
Step 4 In the new interface, configure the basic data for the report.
1.
Issue 01 (2010-09-29)
On the General tab page, input the information as shown in Figure 5-7.

5-29
HUAWEI CBS
Figure 5-7 Creating a new periodical report
2.
On the Template tab page, choose Report of Subscribers as the data and style template.
3.
On the Distribution tab page, three report generation methods are available:
l
Sending the generated report through Email: In this case, you need to input the Email
address.
Releasing as a public report: Choose the Publish Report check box, input the
description, select the importance of the report, and select the directory to store the
report.
Transmitting through FTP: Choose the FTP check box and then input information such
as the IP address.
Step 5 Click Save to store the periodical report.

NOTE
Through the preceding procedure, you can also customize monthly templates for the total recharge amount and
the call times reports. Through the monthly data, you can know the trend of data.
----End
Exception Handling
If the iWeb server runs normally but cannot be accessed through the IE browser, rectify the fault
as follows:
l
5-30
If the agent server is enabled on the client, set the server URL in the IE browser to the
exceptional Web address when the agent server is used.
Issue 01 (2010-09-29)
HUAWEI CBS
l
If the firewall is enabled on the computer where the report server is installed, set the port
number of the report system to the exceptional port number when the firewall is enabled
or disable the firewall.
5.1.22 Understanding Key Service Indexes Through the LBI System

The LBI system provides a basic KPI function to display carrier-concerned indexes in figures
and tables. In this way, carriers can understand the key indexes and their changes.
Prerequisite
The LBI system have been installed and you can access the LBI reports through the URL.
Context
The basic KPIs of the LBI system include the following:
l
KPI of Product Ordered Subscribers
KPI of Newly-added&Lost Subscribers
KPI of Bill Statistic
Table 5-2 describes the basic KPIs.

Table 5-2 Basic KPIs
KPI
Statistics
Frequency
Storage
Period
Query
Condition
Statistics Content
KPI of
Product
Ordered
Subscribers
Every day
90 days
Statistics
date
The statistics include the

number of subscribers and
the number of new
subscribers by date and
product to help carriers to
understand the situation of
developing subscribers.
KPI of
Newlyadded&Lost
Subscribers
Every day
90 days
Statistics
date
The statistics include the

number of new subscribers
and the number of
deregistered subscribers by
date and package to help
carriers to take actions at
earliest based on the
deregistration situation.
KPI of Bill
Statistics
Every day
90 days
Statistics
date
The statistics include

subscribers' incomes by date
and product to help carriers
to understand the general
income of the system.
The following procedure describes how to query the KPI of Newly-added&Lost Subs report
for service data in the LBI system to understand the key service indexes.
Issue 01 (2010-09-29)

5-31
HUAWEI CBS
Procedure
Step 1 Log in to the LBI system through the Microsoft Internet explorer.
Step 2 Click
Step 3 Click
to display the list of functions.
to display the report data on the left side of the resource management page.
Step 4 Choose Data > System Resource > KPI to display the KPI reports, as shown in Figure 5-8.
Figure 5-8 KPI reports
Step 5 Choose KPI of Newly-added&LostSubs to display the report page.

Step 6 Select a time segment, as shown in
. Then click
OK to display the detailed report information in figures and tables, as shown in Figure 5-9.
5-32

Issue 01 (2010-09-29)
HUAWEI CBS
Figure 5-9 Detailed report information
----End
Exception Handling
If the LBI system runs normally but cannot be accessed through the Microsoft Internet explorer,
rectify the fault as follows:
l
Issue 01 (2010-09-29)
If the agent server is enabled on the client, set the server URL in the Microsoft Internet
explorer to the exceptional Web address when the agent server is used.

5-33
HUAWEI CBS
l
If the firewall is enabled on the computer where the report server is installed, set the port
number of the report system to the exceptional port number when the firewall is enabled
or disable the firewall.
5.2 Maintenance Items Related to Hardware

This section describes the maintenance items related to the hardware devices of the system.
5.2.1 Cleaning the Tape Drive
This task is performed to clean the tape drive to ensure its availability and prevent data loss due
to tape drive unavailability.
5.2.2 Checking the Number of Available Tapes
You need to check the number of available tapes periodically. Verify that data can be backed
up with enough tapes.
5.2.3 Checking the Power Modules and UPS (ATAE)
This task is performed to check the power modules and UPS to ensure the reliability of the system
power supply.
5.2.4 Checking the Power Modules and UPS (Minicomputers)
power supply.
5.2.5 Cleaning the Cabinets
This task is to check whether the cabinets and cabinet fans are clean to ensure safety.
5.2.1 Cleaning the Tape Drive

This task is performed to clean the tape drive to ensure its availability and prevent data loss due
to tape drive unavailability.
Reference Standard
The reference standards are as follows:
l
The cleaning time cannot exceed 30 seconds.
The cleaning indicator of the tape drive does not turn yellow.
NOTE
The use of the cleaning tape must be recorded after it is used. Do not use expired tape.
Context
Table 5-3 lists the relationship between the cleaning cycle and the using frequency of the tape
drive.
Table 5-3 Relationship between the cleaning cycle and the using frequency of the tape drive
5-34
Using Frequency (Times/Day)
Cleaning Cycle (Week)
4
Issue 01 (2010-09-29)
HUAWEI CBS
Using Frequency (Times/Day)
Cleaning Cycle (Week)
Procedure
Step 1 Insert the cleaning tape to the tape drive. Then the system cleans the tape drive automatically.
Step 2 During cleaning, the green light is on. After cleaning the tape drive is complete, the green light
is off.
----End
Exception Handling
If the cleaning indicator turns yellow and blinks, it indicates that the magnetic head is dirty. You
must clean it immediately.
If the tape is ejected in a short time, it indicates that the cleaning fails. You must insert the tape
again.
5.2.2 Checking the Number of Available Tapes

You need to check the number of available tapes periodically. Verify that data can be backed
up with enough tapes.
Reference Standard
The number of available tapes can be used for at least one month.
Context
None.
Procedure
Step 1 The number of available tapes needs to be audited by the owner.
----End
Exception Handling
If the available tapes are not enough, buy new tapes.
5.2.3 Checking the Power Modules and UPS (ATAE)

power supply.
Issue 01 (2010-09-29)

5-35
HUAWEI CBS
Reference Standard
None.
Context
The UPS works normally, and the power modules are normal.
Procedure
Step 1 Check the status of the UPS.
Step 2 Check whether there are sundries around the power modules.
----End
Exception Handling
l
If the power supply module is abnormal, contact the power supply department to solve the
problem.
If the UPS is faulty, use the standby UPS.
5.2.4 Checking the Power Modules and UPS (Minicomputers)

power supply.
Reference Standard
None.
Context
The UPS works normally, and the power modules are normal.
Procedure
Step 1 Check the status of the UPS.
Step 2 Check whether there are sundries around the power modules.
----End
Exception Handling
l
If the power supply module is abnormal, contact the power supply department to solve the
problem.
If the UPS is faulty, use the standby UPS.
5.2.5 Cleaning the Cabinets

This task is to check whether the cabinets and cabinet fans are clean to ensure safety.
5-36

Issue 01 (2010-09-29)
HUAWEI CBS
Reference Standard
The reference standards are as follows:
l
The surfaces of cabinets and racks must be clean, neat, and dustless.
The cabinet fans run normally without any noise.
Context
None.
Procedure
Step 1 Check the surfaces and insides of the cabinets and ensure that they are clean.
Step 2 Check the cabinet fans and ensure that they are clean.
----End
Exception Handling
None.
5.3 Checking the Viruses on the Terminal Computer

This task is performed to periodically kill the viruses in the operating system where the SMAP
terminal is located to ensure the system security.
Reference Standard
l
No virus is found after the virus scanning.
No infected files are found at the maintenance terminal.
Context
None.
Procedure
Step 1 Log in to the SMAP client as the user that has the administrator authority.
Step 2 Shut down all the application processes.
Step 3 Disconnect the computer from the external network.
Step 4 Use anti-virus software to scan the computer.
----End
Exception Handling
None.
Issue 01 (2010-09-29)

5-37
HUAWEI CBS
5.4 Checking Whether the Device Maintenance Contract

Expires
This task is performed to check the device maintenance contract periodically to prevent service
quality decrease due to contract expiration.
Reference Standard
None.
Context
None.
Procedure
Step 1 Ask relevant professional engineers to verify the device maintenance contract.
----End
Exception Handling
If the contract has expired, please contact Huawei marketing to renew the contract.
5-38

Issue 01 (2010-09-29)
HUAWEI CBS
6 Yearly Maintenance
Yearly Maintenance
About This Chapter

The maintenance items that need to be performed more than once a year are listed.
6.1 Switching Test
This topic describes the switching test.
6.2 Cleaning the dust (ATAE)
You need to clean the dust periodically to keep the systems running stably.
6.3 Cleaning the dust (Minicomputers)
Issue 01 (2010-09-29)

6-1
HUAWEI CBS
6.1 Switching Test

This topic describes the switching test.
6.1.1 Testing the Switchover Between Two Nodes (ATAE)
The switchover of the two-node cluster is performed once every year. This is to guarantee that
the switchover of the two-node cluster can be normally performed and the system can normally
provide services for external systems when exceptions occur.
6.1.2 Testing the Switchover Between Two Nodes (HP)
6.1.3 Testing the Switchover Between Two Nodes (IBM)
6.1.4 Testing the Switchover Between the Boards on the USAU
During yearly maintenance, you need to perform switchover between the master and slave
boards, and rectify minor faults through restarting.
6.1.5 Testing the Switchover Between the Boards on the URP
6.1.1 Testing the Switchover Between Two Nodes (ATAE)

Prerequisite
The active node and standby node are in the normal state.
Before the switchover of the two-node cluster, make sure that calls can be made successfully,
CDRs can be generated successfully, the SMDBs on the active node and standby node, and the
physical database are in the normal state, and the data can be synchronized successfully between
the two nodes.
The system space usage is smaller than 80%. The CBP and BMP services are normal and the
CPU and memory usage are normal.
6-2

Issue 01 (2010-09-29)
HUAWEI CBS
Context
CAUTION
l
The switchover of the two-node cluster affects the existing network greatly. In this case,
you need to perform switchover in idle time.
Before two-node cluster switchover, ensure that the operation is approved and to be
You can perform the two-node cluster switchover by using the following methods:
l
Stop the application to trigger a switchover.
Stop the database server to trigger a switchover.

NOTE
On the CBP, you can stop the SMDB to trigger the switchover of the two-node cluster.
The ATAE manages the two-node cluster through the Cluster Manager. This topic takes the
BMP&SMP two-node cluster in cold standby mode and the Oracle nonRAC local database for
example to describe the switchover procedure. For the switchover of other NEs, see the
installation guide of the matching version.
Procedure
Step 1 Start the Cluster Manager.
Step 2 On the left of the Cluster Explorer page, right-click the service group OracleGroup and choose
Switch To > Standby node. Then the service group is switched to the other node.
Step 3 Check the status of service groups.
On the left of the Cluster Explorer page, select service groups and click the Status tab page to
view the status.
l
The OracleGroup is in ONLINE state on the new active node and in OFFLINE state on the
new standby node.
The FaultSpyGroup is in ONLINE state both on the two nodes.
Step 4 Test service operations.

l
The services to be tested at the BMP side are subscriber creation, activation, and recharge.
The services to be tested at the SMP side are making voice calls, sending short messages,
and generating CDRs.
----End
Exception Handling
If the switchover of the two-node cluster fails, do as follows to collect the fault information and
send the information to Huawei R&D engineers for fault location:
1.
Issue 01 (2010-09-29)
Log in to the active node as the root user.

6-3
HUAWEI CBS
2.
Run the following command to collect information:

# hagetcf
Saving 6.45 MB.
Enter path where configuration can be saved (default is /tmp ):
3.
Type the path of the to-be-collected information, such as /tmp/back.

Collecting package infos
Checking VCS package integrity
Collecting VCS information
Collecting system configuration
Collecting selected /etc files
Collecting VCS configuration files
Collecting system boot related files
Collecting selected /proc files
Collecting files from /var/VRTSvcs/log
Collecting files from /var/VRTSvcs/lock
Collecting /var/log/messages*
Collecting core files in /opt/VRTSvcs
Compressing /tmp/back/vcsconf.linux191.tar to /tmp/back/
vcsconf.linux191.tar.gz
Done. Please e-mail /tmp/back/vcsconf.linux191.tar.gz to your support
provider.
NOTE
Package the collected information to vcsconf.linux191.tar.gz. The field linux191 indicates the host
name.
4.
Run the following command to check whether the information is successfully collected:
# cd /tmp/back
# ls
ENIP_V100R003C03B614_HA_Install.tar.gz
ENIP_V100R003C03B614_HA_OCS_RUN_ATAE.tar.gz
5.
install
vcsconf.linux191.tar.gz
Send the collected information to Huawei R&D engineers for fault locating.
6.1.2 Testing the Switchover Between Two Nodes (HP)

Prerequisite
the two nodes.
6-4

Issue 01 (2010-09-29)
HUAWEI CBS
Context
CAUTION
l
The switchover of the two-node cluster affects the existing network greatly. In this case, you
need to perform switchover in idle time.
l

NOTE
This topic takes the BMP&SMP two-node cluster in cold standby mode and the Oracle nonRAC
local database for example to describe the switchover procedure. For the switchover of other
NEs, see the installation guide of the matching version.
Procedure
Step 1 Stop an application to trigger a switchover of the two-node cluster.
1.
Log in to host1a as the bmp user.
2.
Stop the BMP.

% stop_bmp.sh
3.
Log in to host1b as the root user. Check whether bmppkg is switched to host1b.
# cmviewcl -v
If bmppkg is switched to host1b, you see the following information:
PACKAGE STATUS STATE AUTO_RUN NODE
bmppkg up running enabled host1b
The preceding information in bold indicates that bmppkg is switched to host1b.

4.
Check whether the floating IP address for external services is bound to host1b (active node
after the switchover).
# netstat -i | grep share_ip
lan900:1 1500 10.10.11.0 share_ip 6776 0 6776 0 0
The lan900 is the logical network interface name of the APA network adapter on host1b.
The displayed information indicates that the floating IP address is already bound to the
lan900.
5.
Log in to host1b (active node after the switchover) and host1a (standby node after the
switchover) as the oracle user, and then check the status of the database.
% /oracle/crs/bin/crs_stat -t
Name Type Target State Host
-----------------------------------------------------------ora....T1.lsnr application ONLINE ONLINE host1a
ora.host1a.gsd application ONLINE ONLINE host1a
ora.host1a.ons application ONLINE ONLINE host1a
Issue 01 (2010-09-29)

6-5
HUAWEI CBS
ora.host1a.vip
ora....T2.lsnr
ora.host1b.gsd
ora.host1b.ons
ora.host1b.vip
ora.orc.db
ora....c1.inst
ora....c2.inst
ora...._orc.cs
ora....rc1.srv
application
application
application
application
application
application
application
application
application
application
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
ONLINE
host1a
host1b
host1b
host1b
host1b
host1b
host1a
host1b
host1b
host1b
oracle% sqlplus "/as sysdba"

SQL> select status from v$instance;
If the database is started, you see information similar to the following:
STATUS
-----------------------------------OPEN
SQL> select open_mode from v$database;

If the database is normal, you see information similar to the following:
OPEN_MODE
---------READ WRITE
6.
Check the status of the related applications on host1b (active node after the switchover).
a.
Log in to host1b as the bmp user, and then check whether the processes of the BMP
are started.
%p
If the BMP is normal, you see the information similar to the following:
UID
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
PID
20358
20405
20280
20090
20156
20150
20317
20298
17486
29446
14986
17386
PPID
1
20358
1
1
1
1
1
1
1
1
14960
1
C
0
0
0
0
0
0
0
0
0
0
3
0
STIME
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
TTY
?
?
?
?
?
?
?
?
?
?
?
?
TIME
00:01:43
00:02:44
00:00:34
00:00:04
00:00:00
00:00:00
00:00:47
00:00:51
00:00:00
00:00:00
01:31:21
00:06:53
ALIASNAME
Monitor 0
Center 1
configDaemon
icdcomm
idagent
idcenter
idlproxy
namingDaemon
ExprServer -d
Apache -k
jboss 1
monitor_jboss
View $HOME/log/run/bmp_run.log to check the processes of the BMP.

b.
Switch to the uoa user, and then check whether the processes of the UOA are started.
%p
If the UOA is normal, you see information similar to the following:
uoa 27305 1 0 21:30:31 ? 0:00 uoa_lma
uoa 29186 27305 0 21:30:54 ? 0:02 uoa_log_agent
uoa 28307 27305 0 21:30:42 ? 0:02 uoa_perf_agent
uoa 27326 27305 0 21:30:31 ? 0:00 Naming_Service -ORBEndPoint iiop://
10.10.11.13:6445
uoa 28611 27305 0 21:30:45 ? 0:00 uoa_cli
uoa 28869 27305 0 21:30:51 ? 0:01 uoa_sxpadapter 0
uoa 27900 27305 0 21:30:39 ? 0:01 uoa_trace_agent
uoa 28767 27305 0 21:30:48 ? 0:01 uoa_soapadapter
uoa 27455 27305 0 21:30:35 ? 0:04 uoa_server
c.
Switch to the smp user, and then check whether the processes of the SMP are started.
%p
6-6

Issue 01 (2010-09-29)
HUAWEI CBS
The status of each process is displayed as follows:

UID
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
PID PPID C STIME TTY TIME CMD

192868 524942 0 23:08:36 - 0:33
196654 524942 0 23:08:11 - 1:38
229912 524942 0 23:08:17 - 0:04
233506 524942 0 23:07:56 - 2:57
254480
1 0 23:07:51 - 0:07
258788 524942 0 23:07:59 - 0:03
266598 524942 0 23:08:02 - 0:04
274774 524942 0 23:08:14 - 1:38
295400 524942 0 23:08:24 - 0:03
307506 524942 0 23:08:08 - 1:38
332108 524942 0 23:08:05 - 0:04
340022 524942 0 23:08:30 - 0:03
372932 524942 0 23:08:27 - 0:02
385348 524942 0 23:08:33 - 0:13
430164 524942 0 23:08:20 - 0:05
524942
1 0 23:07:54 - 0:01
136_sms_scp_agent -noinput
111_smpker -noinput 1
115_sms_kernel_agent -noinput
100_oamagent -noinput
sms_cfg_center -noinput
101_sms_access_agent -noinput
103_sms_db_agent -noinput
127_sms_log_serv -noinput
105_sms_secu_serv -noinput
129_sms_pois_serv -noinput
128_sms_fs_serv -noinput
133_sms_mml_agent -noinput
125_sms_serv_center -noinput
sms_lca -noinput
The SMP has been started. The preceding information is only an example. The
displayed process information varies with the actual situation. View the log files in
$SMS_DIR/log and make sure that the SMP is started properly.
d.
Switch to the root user, and then check whether the spy.sh monitor process is running.
% su - root
# ps -ef | grep spy.sh | grep monitor
If the spy.sh monitor process is running, you see the information similar to the
following.
root 18591 17990 1 11:23:25 ? 3:50 /usr/bin/ksh /etc/cmcluster/bmppkg/
spy.sh monitor
7.
Check the status of the related applications on host1a (standby node after the switchover).
a.
Log in to the standby node as the bmp user, and then check whether the processes of
the BMP are started.
% su - bmp
%p
If the BMP on the standby node is not started, you see the following information:
p: Command not found
b.
Switch to the smp user, and then check the processes of the SMP.
% su - smp
%p
If the SMP on the standby node is not started, you see the following information:
c.
Switch to the uoa user, and then check the processes of the UOA.
% su - uoa
%p
If the UOA on the standby node is not started, you see the following information:
uoa_lma has not exist, maybe something is wrong with it
d.
Switch to the root user, and then check whether the spy.sh standby process is running.
% su - root
# ps -ef | grep spy.sh | grep standby
If the spy.sh standby process is running, you see the information similar to the
following:
Issue 01 (2010-09-29)

6-7
HUAWEI CBS

spy.sh standby
8.
Log in to host1b as the smp user.
9.
Stop the SMP.

% stop.sh sms
10. Log in to host1a as the root user. Check whether bmppkg is switched to host1a.
# cmviewcl -v
If bmppkg is switched to host1a, you see the following information:
bmppkg up running enabled host1a
The preceding information in bold indicates that bmppkg is switched to host1a.

11. Check whether the floating IP address for external services is bound to host1a (active node
after the switchover).
lan900:1 1500 10.10.11.0 share_ip 6776 0 6776 0 0
The lan900 is the logical network interface name of the APA network adapter on host1b.
The displayed information indicates that the floating IP address is already bound to the
lan900.
12. Log in to host1a (active node after the switchover) and host1b (standby node after the
ora.host1a.vip application ONLINE ONLINE host1a
ora....T2.lsnr application ONLINE ONLINE host1b
ora.host1b.gsd application ONLINE ONLINE host1b
ora.host1b.ons application ONLINE ONLINE host1b
ora.host1b.vip application ONLINE ONLINE host1b
ora.orc.db
application ONLINE ONLINE host1b
ora....c1.inst application ONLINE ONLINE host1a
ora....c2.inst application ONLINE ONLINE host1b
ora...._orc.cs application ONLINE ONLINE host1b
ora....rc1.srv application ONLINE ONLINE host1b

STATUS
-----------------------------------OPEN

OPEN_MODE
---------READ WRITE
6-8

Issue 01 (2010-09-29)
HUAWEI CBS
13. Check the status of the related applications and monitoring process on host1a (the active
node after the switchover).
a.
Log in to host1a as the bmp user, and then check whether the processes of the BMP
are started.
%p
UID
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
PID
20358
20405
20280
20090
20156
20150
20317
20298
17486
29446
14986
17386
PPID
1
20358
1
1
1
1
1
1
1
1
14960
1
C
0
0
0
0
0
0
0
0
0
0
3
0
STIME
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
TTY
?
?
?
?
?
?
?
?
?
?
?
?
TIME
00:01:43
00:02:44
00:00:34
00:00:04
00:00:00
00:00:00
00:00:47
00:00:51
00:00:00
00:00:00
01:31:21
00:06:53
ALIASNAME
Monitor 0
Center 1
configDaemon
icdcomm
idagent
idcenter
idlproxy
namingDaemon
ExprServer -d
Apache -k
jboss 1
monitor_jboss

b.
%p
uoa 27305 1 0 21:30:31 ? 0:00 uoa_lma
uoa 29186 27305 0 21:30:54 ? 0:02 uoa_log_agent
10.10.11.13:6445
uoa 28611 27305 0 21:30:45 ? 0:00 uoa_cli
uoa 27455 27305 0 21:30:35 ? 0:04 uoa_server
c.
%p
UID
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp

192868 524942 0 23:08:36 - 0:33
196654 524942 0 23:08:11 - 1:38
229912 524942 0 23:08:17 - 0:04
233506 524942 0 23:07:56 - 2:57
254480
1 0 23:07:51 - 0:07
258788 524942 0 23:07:59 - 0:03
266598 524942 0 23:08:02 - 0:04
274774 524942 0 23:08:14 - 1:38
295400 524942 0 23:08:24 - 0:03
307506 524942 0 23:08:08 - 1:38
332108 524942 0 23:08:05 - 0:04
340022 524942 0 23:08:30 - 0:03
372932 524942 0 23:08:27 - 0:02
385348 524942 0 23:08:33 - 0:13
430164 524942 0 23:08:20 - 0:05
524942
1 0 23:07:54 - 0:01
sms_lca -noinput
d.
% su - root
Issue 01 (2010-09-29)

6-9
HUAWEI CBS

following.
spy.sh monitor
14. Check the status of the related applications and monitoring process on host1b (the standby
a.
% su - bmp
%p
b.
% su - smp
%p
c.
% su - uoa
%p
d.
% su - root
following:
spy.sh standby
Step 2 Stop the database to trigger a switchover of the two-node cluster.

1.
Log in to host1a as the root user. Make sure that SWITCHING is set to enabled on the
# cmviewcl -v
The displayed information must include the following:
bmppkg up running enabled host1a
Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual
Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Service up 0 0 share_ip
Subnet up 10.10.11.0
Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
6-10

Issue 01 (2010-09-29)
HUAWEI CBS
Primary up enabled host1a(current)

Alternate up enabled host1b
If SWITCHING is set to disabled, reset it to enabled.

# cmmodpkg -e -n node name -v bmppkg
2.
Switch to the oracle user, and then stop the database.

% onmode.sh
3.
Log in to host1b as the root user. Check whether bmppkg is switched to host1b.
# cmviewcl - v
If bmppkg is switched to host1b, you see the following information:
bmppkg up running enabled host1b
4.
Check whether the floating IP address for external services is bound to host1b.
lan900:1 1500 10.10.11.0 share_ip 6776 0 6776 0 0
In the preceding information, lan900 is the logical network interface name of the APA
network adapter on host1b, and the command response indicates that the floating IP address
is bound to lan900.
5.
Log in to host1b (active node after the switchover) and host1a (standby node after the
ora.host1a.vip application ONLINE ONLINE host1a
ora....T2.lsnr application ONLINE ONLINE host1b
ora.host1b.gsd application ONLINE ONLINE host1b
ora.host1b.ons application ONLINE ONLINE host1b
ora.host1b.vip application ONLINE ONLINE host1b
ora.orc.db
application ONLINE ONLINE host1b
ora....c1.inst application ONLINE ONLINE host1a
ora....c2.inst application ONLINE ONLINE host1b
ora...._orc.cs application ONLINE ONLINE host1b
ora....rc1.srv application ONLINE ONLINE host1b

STATUS
-----------------------------------OPEN

OPEN_MODE
---------READ WRITE
Issue 01 (2010-09-29)

6-11
HUAWEI CBS
6.
Check the status of the related applications and monitoring process on host1b (the active
a.
Switch to the bmp user, and then check whether the processes of the BMP are started
normally.
%p
UID
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
bmp
PID
20358
20405
20280
20090
20156
20150
20317
20298
17486
29446
14986
17386
PPID
1
20358
1
1
1
1
1
1
1
1
14960
1
C
0
0
0
0
0
0
0
0
0
0
3
0
STIME
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
Sep27
TTY
?
?
?
?
?
?
?
?
?
?
?
?
TIME
00:01:43
00:02:44
00:00:34
00:00:04
00:00:00
00:00:00
00:00:47
00:00:51
00:00:00
00:00:00
01:31:21
00:06:53
ALIASNAME
Monitor 0
Center 1
configDaemon
icdcomm
idagent
idcenter
idlproxy
namingDaemon
ExprServer -d
Apache -k
jboss 1
monitor_jboss

b.
%p
uoa 27305 1 0 21:30:31 ? 0:00 uoa_lma
uoa 29186 27305 0 21:30:54 ? 0:02 uoa_log_agent
10.10.11.13:6445
uoa 28611 27305 0 21:30:45 ? 0:00 uoa_cli
uoa 27455 27305 0 21:30:35 ? 0:04 uoa_server
c.
%p
UID
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp
smp

192868 524942 0 23:08:36 - 0:33
196654 524942 0 23:08:11 - 1:38
229912 524942 0 23:08:17 - 0:04
233506 524942 0 23:07:56 - 2:57
254480
1 0 23:07:51 - 0:07
258788 524942 0 23:07:59 - 0:03
266598 524942 0 23:08:02 - 0:04
274774 524942 0 23:08:14 - 1:38
295400 524942 0 23:08:24 - 0:03
307506 524942 0 23:08:08 - 1:38
332108 524942 0 23:08:05 - 0:04
340022 524942 0 23:08:30 - 0:03
372932 524942 0 23:08:27 - 0:02
385348 524942 0 23:08:33 - 0:13
430164 524942 0 23:08:20 - 0:05
524942
1 0 23:07:54 - 0:01
sms_lca -noinput
d.
% su - root
6-12

Issue 01 (2010-09-29)
HUAWEI CBS

following.
spy.sh monitor
7.
Check the status of the related applications and monitoring process on host1a (the standby
a.
% su - bmp
%p
b.
% su - smp
%p
c.
% su - uoa
%p
d.
% su - root
following:
spy.sh standby
----End
Exception Handling
If the switchover fails, check the following logs to locate the fault:
l
Check the following BMP logs:
/etc/cmcluster/bmppkg/spy.log
/etc/cmcluster/bmppkg/control.sh.log
Check the following CBP logs:
/etc/cmcluster/cbppkg/spy.log
/etc/cmcluster/cbppkg/control.sh.log

Issue 01 (2010-09-29)

6-13
HUAWEI CBS
6.1.3 Testing the Switchover Between Two Nodes (IBM)

Prerequisite
the two nodes.
Context
CAUTION
l
The switchover of the two-node cluster affects the existing network greatly. In this case, you
need to perform switchover in idle time.
l

NOTE
However, you cannot stop the network database to trigger the switchover of the two-node cluster.
This topic takes the BMP&SMP two-node cluster in cold standby mode and the Oracle nonRAC
local database for example to describe the switchover procedure. For the switchover of other
NEs, see the installation guide of the matching version.
Procedure
Step 1 Stop an application to trigger a switchover of the two-node cluster.
1.
6-14
Log in to the active node and standby node as bmp user and see Table 6-1 to check whether
the status of the two-node cluster is normal.

Issue 01 (2010-09-29)
HUAWEI CBS
Table 6-1 Two-node cluster status
2.
Check Item
host1a
host1b
Cluster processes
The status of the cluster

processes is active.

Network status
The status of the active IP

address of the active node is
DOWN, and the status of
other IP addresses is UP.

appspy
The status of the process is

active.

inoperative.
spy.sh
The spy.sh monitor and

appspy.sh processes are
started.

started.
Database
The database status is OnLine -- Up.
The database is not started.
Application
The BMP, SMP, and UOA

are started.

are not started.
VG
The VGs bmpvg, smpvg,

oravg, and datavg are
activated on this node.

oravg, and datavg are not
Floating IP address
The floating IP address is

bound to the active network
adapter of this node.
The floating IP address is not

Run the following command to stop the BMP as the bmp user:
% stop_bmp.sh
The switchover duration varies according to the host performance and data volume. After
the switchover of the two-node cluster, the original active node host1a works as the standby
node, and the original standby node host1b works as the active node.
3.
See Table 6-2 to check whether the status of the two-node cluster is normal after the
switchover.
Table 6-2 Two-node cluster status
Issue 01 (2010-09-29)
Check Item
host1b
host1a
Cluster processes


Network status



6-15
HUAWEI CBS
Check Item
host1b
host1a
appspy

active.

inoperative.
spy.sh

started.

started.
Database
The database status is OnLine -- Up.
The database is not started.
Application

are started.

are not started.
VG

oravg, and datavg are

oravg, and datavg are not
Floating IP address
The floating IP address is

The floating IP address is not

Step 2 Stop the database to trigger a switchover of the two-node cluster.

1.
See Table 6-2 to check whether the status of the two-node cluster is normal.
2.
Log in to the active node host1b as the oracle user. Run the following command to stop
the database.
% sqlplus "/as sysdba"
SQL> shutdown oracle% lsnrctl stop
3.
See Table 6-1 to check whether the status of the two-node cluster is normal after the
switchover.
----End
Exception Handling
If the switchover fails, check the following logs to locate the fault:
l
Check the following BMP logs:
/usr/sbin/cluster/utilities/bmp/bmppkg/spy.log
/usr/sbin/cluster/utilities/bmp/bmppkg/bmppkg.log
/usr/sbin/cluster/utilities/bmp/event/event.log
Check the following CBP logs:
/usr/sbin/cluster/utilities/cbp/cbppkg/spy.log
/usr/sbin/cluster/utilities/cbp/cbppkg/cbppkg.log
/usr/sbin/cluster/utilities/cbp/event/event.log

6-16

Issue 01 (2010-09-29)
HUAWEI CBS
6.1.4 Testing the Switchover Between the Boards on the USAU

Prerequisite
There is the risk on this operation. The operation personnel must be familiar with the device and
understand the running status of the device. In addition, the master and slave system run
normally. Before switchover, contact Huawei Engineers. Then, perform the operation if
approved.
CAUTION
l
The maintenance before switchover needs to be performed in the time range when the traffic
is small, such as 2:00 am to 4:00 am. You can select the time as required. Ensure that the
communication is not interrupted and services are not affected during switchover.
Before switchover, ensure that the system runs normally, the slave board is normal, and the
data is backed up.
The switchover cannot be performed frequently. It is recommended that the switchover be

performed once half a year.
Operation Procedure
Maintenance Item
Operation Instructions
Standards
Switchover of the host

system
Run the SWP BRD command to

test the switchover of main
boards.
The master board is reset.
The slave board becomes the

master board and the master
board becomes the slave
board.
The system runs normally

after the switchover is
complete.
The system displays alarm

messages during the
switchover between boards.
Exception Handling
l
When the switchover between the active and standby boards fails, and the system cannot
process services normally, you need to reload each board from the BAM to restore the
service.
If the function of the new active board cannot be restored, you need to immediately run the
SWP BRD command to switch this board back to the standby board.
Issue 01 (2010-09-29)

6-17
HUAWEI CBS
6.1.5 Testing the Switchover Between the Boards on the URP

Prerequisite
There is the risk on this operation. The operation personnel must be familiar with the device and
understand the running status of the device. In addition, the switchover should be performed
when the master and slave system run normally. Before switchover, contact Huawei Engineers.
Then, perform the operation if approved.
CAUTION
l
The maintenance before switchover needs to be performed in the time range when the traffic
is small, such as 2:00 am to 4:00 am. You can select the time as required. Ensure that the
communication is not interrupted and services are not affected during switchover.
Before switchover, ensure that the system runs normally, the slave board is normal, and the
data is backed up.
The switchover cannot be performed frequently. It is recommended that the switchover be

performed once half a year.
Operation Procedure
Maintenance Item
Operation Instructions
Standards
Switchover of the host

system
Run the SWP BRD command to

test the switchover of main
boards.
The master board is reset.
The slave board becomes the

master board and the master
board becomes the slave
board.
The system runs normally

after the switchover is
complete.
The system displays alarm

messages during the
switchover between boards.
Exception Handling
6-18
When the switchover between the active and standby boards fails, and the system cannot
process services normally, you need to reload each board from the BAM to restore the
service.
If the function of the new active board cannot be restored, you need to immediately run the
SWP BRD command to switch this board back to the standby board.
Issue 01 (2010-09-29)
HUAWEI CBS
6.2 Cleaning the dust (ATAE)

Reference Standard
The air filter shelf, air filter gauze, fan tray, air deflector, and blades should be clean.
Context
If the appearance of devices is covered with dust, or if the air inlets and outlets of the system
are blocked with dust, the heat dissipation performance of the system will be degraded, which
affects the stability of the system. Therefore, cleaning dust from devices is important in routine
maintenance.
To ensure stability of a device, clean all the boards in a cabinet regularly (at least once a year).
Ensure that every device is clean.
CAUTION
Cleaning blades is a risky operation. Make sure that:
l
Antistatic measures are taken during all operations.
The detergent complies with the related national standards. This prevents damage to the
blades.
Do not insert or pull out cables during cleaning.
Procedure
Step 1 Determine which components need to be cleaned.
Components to be cleaned
l
Cleaning air filter shelf
Cleaning the air filter gauze
Cleaning the air deflectors
Cleaning the fan tray
Cleaning blades
Step 2 Clean the dusty components.

l
Common method:
Use a clean cotton yarn cloth, ESD-preventive soft brush, and a vacuum cleaner to wipe the
dust off the fan blades and the circuit boards in the backup fan tray.
Cleaning blades
You can clean the blade by using many methods. The purpose of these methods is to prevent
damage to the physical and electrical features of the blade.
----End
Issue 01 (2010-09-29)

6-19
HUAWEI CBS
Exception Handling
None.
6.3 Cleaning the dust (Minicomputers)

Reference Standard
The air filter shelf, air filter gauze, fan tray, air deflector should be clean.
Context
If the appearance of devices is covered with dust, or if the air inlets and outlets of the system
are blocked with dust, the heat dissipation performance of the system will be degraded, which
affects the stability of the system. Therefore, cleaning dust from devices is important in routine
maintenance.
To ensure stability of a device, clean all the boards in a cabinet regularly (at least once a year).
Ensure that every device is clean.
CAUTION
Stopping and cleaning minicomputers are important operations. Ensure that this operation is
performed by a professional person.
Do not insert or pull out cables during cleaning.
Procedure
Step 1 Determine which components need to be cleaned.
Components to be cleaned
l
Cleaning air filter shelf
Cleaning the air filter gauze
Cleaning the air deflectors
Cleaning the fan tray
Step 2 Clean the dusty components.

Common method:
Use a clean cotton yarn cloth, ESD-preventive soft brush, and a vacuum cleaner to wipe the dust
off the fan blades and the circuit boards in the backup fan tray.
----End
6-20

Issue 01 (2010-09-29)
HUAWEI CBS
Exception Handling
None.
Issue 01 (2010-09-29)

6-21
HUAWEI CBS
7 Holiday Maintenance
Holiday Maintenance
About This Chapter

This topic describes the maintenance items that need to be performed comprehensively before
holiday to ensure normal running of the system on holiday.
7.1 Evaluating the Traffic on the SCP
This topic describes how to evaluate whether the traffic volume on holiday may exceed the
maximum traffic volume supported by the system by understanding the trend of the traffic half
a month earlier than the holiday. If the traffic volume on holiday may exceed the maximum
traffic volume supported by the system, prepare emergency maintenance.
Issue 01 (2010-09-29)

7-1
HUAWEI CBS
7 Holiday Maintenance
7.1 Evaluating the Traffic on the SCP

This topic describes how to evaluate whether the traffic volume on holiday may exceed the
maximum traffic volume supported by the system by understanding the trend of the traffic half
a month earlier than the holiday. If the traffic volume on holiday may exceed the maximum
traffic volume supported by the system, prepare emergency maintenance.
Prerequisite
l
The average traffic on each office is different. The maintenance engineers need to learn the
volume of daily traffic in normal situations.
Understand the maximum volume of traffic supported by the system according to the
technical scheme provided by Huawei marketing personnel for deployment.
Context
If there are multiple SCPs, the traffic on the SCPs needs to be evaluated respectively.
Procedure
Step 1 Log in to the SCP active node as the scu user.
Step 2 Access the ${TELLIN_DIR}/temp directory of the SCP.
% cd ${TELLIN_DIR}/temp
Step 3 Obtain the CAPS value by checking logs.
% view manager_0.run
The SCP displays the CAPS value every minute. For example, Platform CAPS: 11.12.
Step 4 Obtain detailed data and draw the trend of the CAPS value change, including detailed time and
value corresponding to the CAPS.
NOTE
The maintenance engineers are recommended to check the CAPS data every day. They can collect CAPS values
on the SCP through Huawei tool Collect Data. The frequency is optional.
----End
Exception Handling
If the CAPS value is lower than the normal value, perform the following checking. For the
unsolved problems, contract Huawei engineers.
7-2
1.
Checking the Space Usage of File Systems, if the usage of the file system space is high,
you need to clear the disk space.
2.
Checking the Memory Usage, check whether the automatic machine is suspended.
3.
Checking the CPU Usage. Check whether an exceptional process exists. You can delete
this process after the analysis.
Issue 01 (2010-09-29)
HUAWEI CBS
8 Maintenance Related to Upgrade
Maintenance Related to Upgrade
About This Chapter

The maintenance engineers need to back up applications, configuration files, and databases
before upgrade and expansion. In this manner, the configuration and data can be recovered
rapidly after the upgrade.
8.1 Backing Up the Operating Systems
This topic describes the backup of the operating systems.
8.2 Backing Up the Application Program
This topic describes the backup of the application program.
8.3 Backing Up Configuration Files
You need to back up configuration files before expansion and upgrade. In this manner, you can
rapidly recover the configuration or recover the system in the case of abnormality after upgrade.
Issue 01 (2010-09-29)

8-1
HUAWEI CBS
8.1 Backing Up the Operating Systems

This topic describes the backup of the operating systems.
8.1.1 Backing Up the Operating System (IBM)
The IBM operating system is backed up once every year or before and after the system upgrade.
8.1.2 Backing Up the Operating System (HP)
The HP operating system is backed up once every year or before and after the system upgrade.
8.1.3 Backing Up the Operating System (SuSE)
The SuSE operating system is backed up once every year or before and after the system upgrade.
Thus, the backup file can be restored in case of exceptions.
8.1.1 Backing Up the Operating System (IBM)

The IBM operating system is backed up once every year or before and after the system upgrade.
Prerequisite
l
This solution adopts backup by tape. Before backup, verify that the tape has sufficient
available space.
Verify that the available space of the /tmp directory is at least 8.8 MB. You can run the df
-k command to check whether the file system has sufficient available space. If the available
space is insufficient, run the following command (for reference) to increase the space. For
details of the planning, see the HUAWEI ENIP Installation Guide.
# chfs -a size=+200000 /tmp
Context
CAUTION
The backup operation is performed at idle time, generally finished within four hours after 00:00.
The operating system is backed up in full backup mode. Both the active node and standby node
need to be backed up.
There are two backup modes. You can select one.
Procedure
Step 1 In command line mode
1.
Log in to the active node and standby node as the root user.
2.
Run the following command to back up the operating system:

# mksysb -i /dev/rmt0
8-2

Issue 01 (2010-09-29)
HUAWEI CBS

Creating information file (/image.data) for rootvg.
Creating tape boot image...
Creating list of files to back up.
Backing up 32179 files...................
3.
After the backup is complete as required, take out the tape and save it.
Step 2 In smit mode

1.
Log in to the active node and standby node as the root user.
2.
Run the following command to back up the operating system:

# smitty mksysb
Back Up the System
* Backup DEVICE or FILE

+/
Create MAP files?
EXCLUDE files?
List files as they are backed up?
Verify readability if tape device?
Generate new /image.data file?
EXPAND /tmp if needed?
Disable software packing of backup?
Backup extended attributes?
Number of BLOCKS to write in a single output
#
(Leave blank to use a system default)
[/dev/rmt0]
no
no
no
no
yes
no
no
yes
[]
+
+
+
+
+
+
+
+
The part in bold indicates the backup medium. Select tape.

3.
After the backup is complete as required, take out the tape and save it.
----End
Exception Handling
If the backup fails, locate the fault according to the error message displayed after the backup
command is run. If the fault persists, contact Huawei engineers.
8.1.2 Backing Up the Operating System (HP)

The HP operating system is backed up once every year or before and after the system upgrade.
Prerequisite
l
This solution adopts backup by tape. Before backup, verify that the tape drive is connected
normally. That is, the host is connected to the tape drive through the SCSI cable and the
tape drive is also connected to the Terminator.
Run the following command to check whether the tape drive is connected normally:
# ioscan -fnC tape
Class
I H/W Path
Driver S/W State
H/W Type
Description
=====================================================================
tape
1 0/1/1/1.1.0 stape CLAIMED
DEVICE
HP
C5683A
/dev/rmt/1m
/dev/rmt/c3t1d0BESTn
/dev/rmt/1mb
/dev/rmt/c3t1d0BESTnb
/dev/rmt/1mn
/dev/rmt/c3t1d0DDS
Issue 01 (2010-09-29)

8-3
HUAWEI CBS

/dev/rmt/1mnb
/dev/rmt/c3t1d0BEST
/dev/rmt/c3t1d0BESTb
/dev/rmt/c3t1d0DDSb
/dev/rmt/c3t1d0DDSn
/dev/rmt/c3t1d0DDSnb
CAUTION
If the tape drive cannot be identified, you need to install the tape driver. Do as follows: Run
the sam command, and then choose Peripheral Devices > Tape Drives > Actions >
Add. Perform operations as prompted.
l
Verify that the tape drive has sufficient available space.
Run the following command to verify that the ignite-ux software is installed. The software
is installed in the system by default.
# swlist | grep -i ignite
B5725AA
UX)
Ignite-UX-11-11
11.11 Systems
C.6.10.97
C.6.10.97
HP-UX Installation Utilities (IgniteHP-UX Installation Utilities for Installing
Context
CAUTION
Procedure
Step 2 Run the following command to back up the operating system:
# make_tape_recovery -Av
NOTE
For the operating system whose version is earlier than HPUX11.00, run the make_recovery command
to back up the operating system.
If the system configurations vary, you need to back up the operating system again.
Step 3 After the backup is complete as required, take out the tape and save it.
----End
Exception Handling
If any exception occurs, contact Huawei engineers.
8-4

Issue 01 (2010-09-29)
HUAWEI CBS
8.1.3 Backing Up the Operating System (SuSE)

The SuSE operating system is backed up once every year or before and after the system upgrade.
Thus, the backup file can be restored in case of exceptions.
Prerequisite
The software source name for making mirror files is Make mirror file 1.0. The system can
automatically make this software source, so manual making is not required.
The space of /mirror-file on the USM server is sufficient for storing mirror files.
Context
The SuSE operating system is backed up through the mirroring function of the USM. The
mirroring function of the USM is to make a mirror file for all the data on the hard disk of a server
blade. The data includes the partitioning information, operating system, and application system
on the hard disk.
The mirror files are stored in the /mirror-file directory on the USM server. Through the mirror
management function of the USM, you can check the information about the mirror file, such as
the size, creation time, and storage path, and delete the unnecessary mirror files.
CAUTION
The mirror function of the USM is to copy all the data on a server blade to another server blade.
After restoration, you can check the running status of the server blade according to the actual
requirements of applications.
Ensure that services running on the network are not affected.
This section provides only manual backup solution. For the method and procedure of backup
(charged), contact Huawei marketing.
Procedure
Step 1 Making Mirror Templates.
1.
Choose Deployment > Template Management. The Template Management page

appears.
2.
Click Add. The Customize Template page appears.
3.
Enter the template name, such as Make Mirror Template.
4.
Click Add Software. The Add Software page appears.
5.
Select Make mirror file 1.0 from Software list, and click OK. The Customize
Template page appears.
6.
Click Edit to set the parameters for making mirror files.

The parameter description is as follows:
Issue 01 (2010-09-29)

8-5
HUAWEI CBS

l
Mirror name: name of a mirror file that is successfully made, which cannot be duplicated
with existing mirror file names. The name is composed of numbers, letters, underscore
(_), and hyphen (-), and starts with a letter. For example, set this parameter to
linux9sp2.
Description: additional information about a mirror file.
7.
Click OK. The Customize Template page appears.
8.
Click Submit. The system notifies whether to add software sources in the correct sequence.
Click OK.
Step 2 Creating and Performing a Mirror Making Task.

1.
Choose Deployment > Task Management. The Task Management page appears.
2.
Click Add. The Add Task page appears.
3.
Configure the information about a deployment task.

l
Task name: unique identifier of a deployment task. For example, set the parameter to
Make Mirror Task.
The methods of performing a task are as follows:
Scheduled: Performs the task at the scheduled time.
Immediate: Performs the task immediately after the task is submitted.
Manual: Performs the task manually.
For example, set the method to Manual.

4.
Click Select Template. Select the template for the deployment task, such as Make Mirror
Template. Then click OK.
5.
Select the shelf, and then click Next.
6.
Select the blade for making mirrors from the blade list, and click Next.
7.
Configure the deployment parameters, and click Next.

l
Execution Password: password for the root user to log in to the server blade. The
password should be the same as that set when you deploy the operating system.
IP address: IP address of the network adapter of the Base plan of the server blade. The
IP address and the IP address of the network adapter of the DHCP service provided by
the USM server are in the same network segment.
8.
Click Submit. The dialog box for confirming the operation appears.
9.
Click OK. The Task Management page appears.
10. Select the required deployment task such as Make Mirror Task, and click Execute.
If the task progress bar displays 100%, it indicates that mirror backup task is performed
successfully. Choose Deployment > Mirror Management. The Mirror Management page
appears. You can check the mirror files in the mirror file list.
----End
Exception Handling
If the backup fails, check wrapper.log file in /var/log/ATAE of the USM server according to
the error information displayed on the USM GUI to locate the problem. If the fault persists,
contact Huawei engineers.
8-6

Issue 01 (2010-09-29)
HUAWEI CBS
8.2 Backing Up the Application Program

This topic describes the backup of the application program.
8.2.5 Backing Up Application Programs of the GFEP
Before an upgrade, you need to back up the system directory so that you can restore it if the
upgrade fails. You also need to back up the configurations such as the protocol configuration
and connection configuration so that the new version can quickly use these configurations after
upgrade. In addition, you need to move the backup files to other media to prevent insufficient
disk space.

Prerequisite
l
Context
CAUTION
Issue 01 (2010-09-29)

8-7
HUAWEI CBS
Procedure
Step 1 Log in to the active node and standby node of the CBP as the root user.
Step 2 Compress the files in the relevant CBP directories.
The directories on the CBP active node to be backed up are as follows:
l
/enip
/corefiles
/hwshare
/opt/informix
/oracle
The directories on the CBP standby node to be backed up are as follows:

l
/enip
/corefiles
/hwshare
/opt/informix
/oracle

% tar -cvf enip.tar /enip
% mv enip.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
8-8

Issue 01 (2010-09-29)
HUAWEI CBS
2.

Prerequisite
l
Context
CAUTION
Procedure
Step 1 Log in to the active node and standby node of the BMP as the root user.
Step 2 Compress the files in the relevant BMP directories.
The directories on the BMP active node to be backed up are as follows:
l
/enip
/corefiles
/hwshare
/opt/informix
/opt/informix/temp
/oracle
The directories on the BMP standby node to be backed up are as follows:

Issue 01 (2010-09-29)

8-9
HUAWEI CBS

l
/corefiles
/hwshare

bmp% tar -cvf enip.tar /enip
bmp% mv enip.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
8-10

Issue 01 (2010-09-29)
HUAWEI CBS
Context
CAUTION
Procedure
Step 1 Log in to the active node and standby node of the AR&DC as the root user.
Step 2 Compress the files in the relevant AR&DC directories.
The directories on the AR&DC to be backed up are as follows: /${JBOSS_HOME}
The following describes how to back up the ${JBOSS_HOME} directory.
% tar -cvf jboss.tar /${JBOSS_HOME}
The following describes how to save the /jboss directory.
% mv jboss.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
Issue 01 (2010-09-29)

8-11
HUAWEI CBS
2.

Prerequisite
l
Context
CAUTION
Procedure
Step 1 Log in to the active node and standby node of the Billing as the root user.
Step 2 Compress the files in the relevant Billing directories.
The directories on the Billing to be backed up are as follows:
l
${BILLING_HOME}/bin
${BILLING_HOME}/config
${BILLING_HOME}/ebill
${BILLING_HOME}/install
${BILLING_HOME}/lib
${BILLING_HOME}/ShareLib
${BILLING_HOME}/tool
The following describes how to back up the ${BILLING_HOME}/bin directory.

% tar -cvf bin.tar ${BILLING_HOME}/bin
8-12

Issue 01 (2010-09-29)
HUAWEI CBS
The following describes how to save the ${BILLING_HOME}/bin directory.

% mv bin.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.
8.2.5 Backing Up Application Programs of the GFEP

Before an upgrade, you need to back up the system directory so that you can restore it if the
upgrade fails. You also need to back up the configurations such as the protocol configuration
and connection configuration so that the new version can quickly use these configurations after
upgrade. In addition, you need to move the backup files to other media to prevent insufficient
disk space.
Prerequisite
l
The user who backs up application programs has the write and execute permissions on the
backup directory.
Context
On the GFEP client, back up the configuration through the interface, including the protocol,
connection, heartbeat script configuration, database setting, setting of the routing table, log
setting, and setting of the timing operation, as shown in Figure 8-1.
Issue 01 (2010-09-29)

8-13
HUAWEI CBS
Figure 8-1 Backup window of the GFEP client
Procedure
Step 1 Log in to the GFEP client.
Step 2 Choose Maintenance > Backup.
The Backup System dialog box is displayed.
Step 3 Select the path to the file from which the configuration information (including protocols and
scripts) needs to be exported, as shown in Figure 8-2.
Figure 8-2 Backing up configuration information
NOTE
You are advised to name the file in the format version number + creation time.
Step 4 Log in to the GFEP host as a GFEP user.

Step 5 Stop the GFEP.
8-14

Issue 01 (2010-09-29)
HUAWEI CBS
%fep stop
Step 6 Access the fep directory.
%cd fep
Step 7 Back up the FEP application.
%cp -r /home/gfep/fep /home/gfep/fep_bakyyyymmdd
Step 8 When the backup is complete, maintenance engineers can move the backup directory to other
storage media.
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.
8.3 Backing Up Configuration Files

You need to back up configuration files before expansion and upgrade. In this manner, you can
rapidly recover the configuration or recover the system in the case of abnormality after upgrade.
Issue 01 (2010-09-29)

8-15
HUAWEI CBS
8.3.7 Backing Up Configuration Files on the EVC
The EVC needs to back up configuration files on the SCP before and after the upgrade.
8.3.8 Backing Up Configuration Files on the UVC
This topic describes how to back up the configuration files of the SCP on the UVC before and
after the upgrade.

Prerequisite
l
Context
CAUTION
8-16

Issue 01 (2010-09-29)
HUAWEI CBS
Procedure
Step 2 Run the following command to compress the configuration files in the relevant CBP directories:
cbp% tar -cvf cbp.config.conf20090710.tar ${HOME}/config
cbp% tar -cvf cbp.addons.conf20090710.tar ${HOME}/add-ons/config
cbp% mv cbp.config.conf20090710.tar /backup
cbp% mv cbp.addons.conf20090710.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
l
Issue 01 (2010-09-29)

8-17
HUAWEI CBS
Context
CAUTION
Procedure
Step 2 Run the following command to compress the configuration files in the relevant BMP directories:
% tar -cvf bmp.config.conf20090710.tar ${HOME}/config
% tar -cvf bmp.addons.conf20090710.tar ${HOME}/add-ons/config
% tar -cvf bmp.jboss.conf20090710.tar ${HOME}/jboss/server/default/conf
% mv bmp.config.conf20090710.tar /backup
% mv bmp.addons.conf20090710.tar /backup
% mv bmp.jboss.conf20090710.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.
8-18

Issue 01 (2010-09-29)
HUAWEI CBS

Prerequisite
l
Context
CAUTION
Procedure
Step 2 Run the following command to compress the configuration files in the relevant Billing
directories:
% tar -cvf billing.config.conf20090710.tar ${BILLING_HOME}/config/
% mv billing.config.conf20090710.tar /backup
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
Issue 01 (2010-09-29)

8-19
HUAWEI CBS
2.

Prerequisite
l
Context
CAUTION
Procedure
Step 1 Log in to the active node of the AR system as the ar user.
Step 2 Run the following command to compress the configuration files in the relevant AR directories:
% tar -cvf ar.jboss.conf20090710.tar ${JBOSS_HOME}/server/default/deploy/smap.ear/
% mv ar.jboss.conf20090710.tar /backup
----End
Exception Handling
1.

8-20

Issue 01 (2010-09-29)
HUAWEI CBS

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
l
Context
CAUTION
Procedure
Step 1 Log in to the active node of the DC system as the dc user.
Step 2 Run the following command to compress the configuration files in the relevant DC directories:
% tar -cvf dc.jboss.conf20090710.tar ${JBOSS_HOME}/server/default/deploy/smap.ear/
% mv dc.jboss.conf20090710.tar /backup
----End
Issue 01 (2010-09-29)

8-21
HUAWEI CBS
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
l
Context
CAUTION
Procedure
Step 2 Run the following command to compress the configuration files in the relevant SCP directories:
scu% tar -cvf scu.config.conf20090710.tar ${TELLIN_DIR}/config
8-22

Issue 01 (2010-09-29)
HUAWEI CBS
scu% mv scu.config.conf20090710.tar /backup

----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.
8.3.7 Backing Up Configuration Files on the EVC

The EVC needs to back up configuration files on the SCP before and after the upgrade.
Prerequisite
None.
Context
None.
Procedure
Step 2 Run the following command to back up the config directory of the SCP:
%cd $HOME
%mkdir evcBAK_(early version number)
%cp $HOME/config/ evcBAK_(early version number)/
----End
Exception Handling
1.
Issue 01 (2010-09-29)

8-23
HUAWEI CBS

l
IBM/ATAE
# df -m
HP
# bdf
2.
8.3.8 Backing Up Configuration Files on the UVC

This topic describes how to back up the configuration files of the SCP on the UVC before and
after the upgrade.
Prerequisite
Ensure that no recharge cards are configured or no customized task is run before backup.
Context
None.
Procedure
Step 2 Run the following command to back up the config directory of the SCP:
%cd $HOME
%mkdir uvcBAK_(early version number)
%cp $HOME/config/ uvcBAK_(early version number)/
Step 3 Log in to the SMP.
Step 4 Run the following command to back up the following important configuration files in $
{HOME}/smp_run/bin:
%cd ${HOME}/smp_run/bin
%cp prepare_file.cfg prepare_file.cfg.bak
%cp single_manager.cfg single_manager.cfg.bak
Step 5 Run the following command to back up the cfg directory in ${HOME}/sms_run:
%cd ${HOME}/sms_run
%mkdir uvcBAK_(early version number)
8-24

Issue 01 (2010-09-29)
HUAWEI CBS
%cp cp sms_run/cfg uvcBAK_(early version number)/

----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
Context
During the startup of the GFEP, the backup script starts automatically, and the system
performance is not affected. Table 8-1 describes the method of backing up the GFEP
configuration files.
Issue 01 (2010-09-29)

8-25
HUAWEI CBS
Table 8-1 Method of backing up the GFEP configuration files

Backup Script
Mode
Backup
Content
Frequen
cy
Remarks
collect.sh
Pack files in backup of

the GFEP installation
directory.
config directory
in the GFEP
installation
directory
Every day
The backup
data of only
the latest
seven days is
reserved,
and the
backup data
that is
generated
seven days
before is
deleted.
The script starts

automatically
during the
startup of the
GFEP.
[Name format]:
GFEP.backup.config.YY
_MM_DD_HH_MM_SS
_Weekday.tar.gz
Procedure
Step 1 Log in to the GFEP host as the GFEP user.
Step 2 Access the backup directory of the GFEP.
%cd $HOME/fep/backup
Step 3 Check whether the backup is successful. Figure 8-3 shows the backup data of the seven days.
Figure 8-3 Checking the backup of the GFEP configuration files
Step 4 Maintenance engineers are advised to move the backup files to other media according to the
situation of the office.
----End
Exception Handling
1.

l
8-26
IBM/ATAE
Issue 01 (2010-09-29)
HUAWEI CBS
# df -m
l
HP
# bdf
2.

Prerequisite
Context
Before modifying a configuration file or performing an upgrade, you can back up the
configuration file through the RBI client. You can back up the configuration files of the following
modules as required:
l
RBIManage
RBICollect
RBISend
RBIFilter
RBICompress
RBICombine
Procedure
Step 1 Log in to the RBI client, namely, URBIConfig.
Step 2 Choose Main Control module in the navigation tree, as shown in Figure 8-4.
Issue 01 (2010-09-29)

8-27
HUAWEI CBS
Figure 8-4 RBI client window
Step 3 Choose Configurations > Backup.

The system displays the backup confirm dialog box. Click Yes in the dialog box.
Step 4 In the dialog box, enter Note name of the file that needs to be backed up, as shown in Figure
8-5.
Figure 8-5 Entering the backup information
Step 5 Click OK. The system displays a message indicating that the backup is successful. The
configuration files of the module are backed up in the path config/backup of the RBI user.
NOTE
If there are too many files in config/backup, you need to delete the discarded backup files.
Step 6 It is recommended that maintenance engineers move backup files to other media according to
the situation of the office.
----End
8-28

Issue 01 (2010-09-29)
HUAWEI CBS
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.

Prerequisite
Context
Issue 01 (2010-09-29)

8-29
HUAWEI CBS
Procedure
1.
2.
Click Export.
3.
is correct.
4.
Then click Save.
----End
Exception Handling
1.

l
IBM/ATAE
# df -m
HP
# bdf
2.
8-30

Issue 01 (2010-09-29)
HUAWEI CBS
9 Routine Maintenance Tables
Routine Maintenance Tables
About This Chapter

The maintenance table is the summary table of the maintenance items that need to be performed
by maintenance engineers.
9.1 Daily Maintenance Table
The daily maintenance table is the summary table of the maintenance items that need to be
performed at least once a day. In this case, the maintenance engineers can perform the
maintenance items after tailoring certain maintenance items as required.
9.2 Weekly Maintenance Table
The weekly maintenance table is the summary table of the maintenance items that need to be
performed at least once a week. The maintenance engineers can perform the maintenance items
after tailoring them as required.
9.3 Monthly Maintenance Table
The monthly maintenance table is the summary table of the maintenance items that need to be
performed at least once a month. The maintenance engineers can perform the maintenance items
9.4 Yearly Maintenance Table
The yearly maintenance table is the summary table of the maintenance items that need to be
performed at least once a year. The maintenance engineers can perform the maintenance items
9.5 Holiday Maintenance Table
The holiday maintenance table is the summary table of the maintenance items that need to be
performed at least once before the holiday. The maintenance engineers can perform the
maintenance items after tailoring them as required.
9.6 List of Maintenance Items for Upgrade
The maintenance table for upgrade is the summary table of maintenance items that need to be
performed before upgrade. The maintenance engineers can perform the maintenance items after
tailoring them as required.
Issue 01 (2010-09-29)

9-1
HUAWEI CBS
9.1 Daily Maintenance Table

The daily maintenance table is the summary table of the maintenance items that need to be
performed at least once a day. In this case, the maintenance engineers can perform the
maintenance items after tailoring certain maintenance items as required.
Table 9-1 shows the daily maintenance items.
Table 9-1 Daily maintenance table
Daily Maintenance Working Log
Office name:
Date:
Checked by:
Maintenance Item
Check Result
Processing I2000 alarms
Yes
No
Monitoring the I2000 performance
Yes
No
Checking the usage of the file system space
Yes
No
Checking the memory usage
Yes
No
Checking the CPU load
Yes
No
Checking the status of the network adapter
Yes
No
Checking the status of the two-node cluster
Yes
No
Checking the core file
Yes
No
Checking the status of the memory database
Yes
No
Checking the space of the memory database
Yes
No
Backing up the data of the memory database
Yes
No
9-2

Issue 01 (2010-09-29)
HUAWEI CBS

Checking the status of the Oracle database
Yes
No
Checking the tablespace of the Oracle

database
Yes
Checking the listening port of the Oracle

database
Yes
Checking the alert logs of the Oracle

database
Yes
Backing up the data of the Oracle database
Yes
No
No
No
No
Checking the status of the Informix database
Yes
No
Checking the tablespace of the Informix

database
Yes
Checking the backup of logical logs of the

Informix database
Yes
Backing up the data of the Informix database
Yes
No
No
No
Checking the status of the SQL server
database
Yes
Checking the tablespace of the SQL server

database
Yes
Backing up the SQL server database
Yes
No
No
No
Checking the status of the DB2 database
Yes
No
Checking the tablespace of the DB2

database
Yes
Checking the status of the process
Yes
No
No
Checking the port status
Yes
No
Checking the run logs
Yes
No
Issue 01 (2010-09-29)

9-3
HUAWEI CBS

Checking the number of CDR on the CBP
Yes
No
Checking the offline CDRs on the CBP
Yes
No
Checking whether the SSMFEP runs

normally
Yes
Checking the connection status of the GFEP

and other devices
Yes
Checking whether the RBI transfers the

CDRs normally
Yes
No
No
No
Duty contents
Remaining problems:
Supervisor check:
9.2 Weekly Maintenance Table

The weekly maintenance table is the summary table of the maintenance items that need to be
performed at least once a week. The maintenance engineers can perform the maintenance items
Table 9-2 describes the weekly maintenance table.
Table 9-2 Weekly maintenance table
Weekly Maintenance Working Log
Office name:
Date:
Checked by:
Maintenance Item
Check Result
Yes
Backing up log files on the CBP
No
Backing up log files on the BMP
Yes
No
Backing up log files on the SCP
Yes
No
9-4

Issue 01 (2010-09-29)
HUAWEI CBS
Weekly Maintenance Working Log

Backing up log files on the SMP
Yes
No
Backing up log files on the UVC
Yes
No
Backing up log files on the EVC
Yes
No
Backing Up and Clearing History CDRs on

the RBI
Yes
No
Duty contents
Remaining problems:
Supervisor check:
9.3 Monthly Maintenance Table

The monthly maintenance table is the summary table of the maintenance items that need to be
performed at least once a month. The maintenance engineers can perform the maintenance items
Table 9-3 describes the monthly maintenance table.
Table 9-3 Monthly maintenance table
Monthly Maintenance Working Log
Office name
Date:
Checked by:
Maintenance Item
Check Result
Performing a comprehensive check by

using the iCheck
Yes
Changing the passwords of running

users
Yes
Changing the passwords of business

operators
Yes
Backing up configuration files
Yes
No
No
No
No
Issue 01 (2010-09-29)

9-5
HUAWEI CBS
Monthly Maintenance Working Log

Backing up application programs
Yes
No
Backing up log files
Yes
No
Understanding the service trend through

iWeb reports
Yes
Cleaning the tape drive
Yes
No
No
Checking the number of available tapes
Yes
No
Checking the power modules and the

UPS (ATAE)
Yes
Checking the power modules and the

UPS (server)
Yes
Cleaning the cabinets
Yes
No
No
No
Checking the viruses on the SMAP
terminal
Yes
Checking whether the device

maintenance contract expires
Yes
No
No
Duty contents
Remaining problems:
Supervisor check:
9.4 Yearly Maintenance Table

The yearly maintenance table is the summary table of the maintenance items that need to be
performed at least once a year. The maintenance engineers can perform the maintenance items
Table 9-4 describes the yearly maintenance table.
9-6

Issue 01 (2010-09-29)
HUAWEI CBS
Table 9-4 Yearly maintenance table

Yearly Maintenance Working Log
Office name:
Date:
Checked by:
Maintenance Item
Check Result
Testing the switchover between the two

nodes of the two-node cluster
Yes
Testing the switchover between the boards
Yes
No
No
Cleaning the dust
Yes
No
Duty contents
Remaining problems:
Supervisor check:
9.5 Holiday Maintenance Table

The holiday maintenance table is the summary table of the maintenance items that need to be
performed at least once before the holiday. The maintenance engineers can perform the
maintenance items after tailoring them as required.
Table 9-5 describes the holiday maintenance table.
Table 9-5 Holiday maintenance table
Holiday Maintenance Working Log
Office name:
Date:
Checked by:
Maintenance Item
Check Result
Performing a comprehensive check by using

the iCheck
Yes
No
Duty contents
Remaining problems:
Supervisor check:
Issue 01 (2010-09-29)

9-7
HUAWEI CBS
9.6 List of Maintenance Items for Upgrade

The maintenance table for upgrade is the summary table of maintenance items that need to be
performed before upgrade. The maintenance engineers can perform the maintenance items after
tailoring them as required.
Table 9-6 describes the maintenance table for upgrade.
Table 9-6 Maintenance table for upgrade
Upgrade Maintenance Working Log
Office name:
Date:
Checked by:
Maintenance Item
Check Result
Performing a comprehensive check by using

the iCheck
Yes
Backing up the data of the operating system
Yes
No
No
Backing up application programs
Yes
No
Backing up configuration files
Yes
No
Duty contents
Remaining problems:
Supervisor check:
9-8

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Appendix
A.1 Critical Operations in the CBS

This topic describes maintenance operations that cause system exceptions in the online charging
system (OCS).
A.2 Impact Analysis Table of CBS Password Change
Certain passwords are saved in the configuration files. When you change a password, you also
need to modify the configuration file that contains the password. If only the password is changed
and the configuration file is not modified, severe abnormality such as database access failure
may occur.
A.3 Glossary
A.4 Acronyms and Abbreviations
Issue 01 (2010-09-29)

A-1
HUAWEI CBS
A Appendix
A.1 Critical Operations in the CBS

This topic describes maintenance operations that cause system exceptions in the online charging
system (OCS).
Precautions
In routine maintenance, precautions include but not limit to the following points:
l
Maintain the system by using foreground maintenance systems, for example, the service
management access point (SMAP). You can modify system-level parameters only after
being approved. If you need to modify system-level parameters, back up the parameters
beforehand and make sure the modifications are correct.
Run more or cat to check data in the configuration file. You cannot run vi to modify a file
without permission. If you need to modify a file, back up the parameters beforehand and
make sure that the modifications are correct.
You can perform the following operations only after being approved by carriers:?
Informix Database
Table A-1 Critical operations in the Informix database
A-2
Operation
Description
oninit -i
Initialize the database and all data in the database is

damaged.
oninit -s
Change the database status from Online into

Quiescent. In this case, other users cannot access the
database.
oncheck -cI
Check whether indexes of the database tables are

normal. The checked tables are added with shared
locks.
oncheck -pt
Print the data structure of the system. The checked

tables are added with shared locks.
onmode -ky
Stop a database.
onmode -s
Change the database status from Online into

Quiescent. Then, you can carry on performing the
ongoing transactions, but you are not allowed to start
new transactions. In the Quiescent mode, other users
cannot access the database.
onmode -u
Change the database status from Online into Quiescent

before the ongoing transactions are complete. Then,
other users cannot access the database.

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Operation
Description
onmode -z
End a thread, and applications become abnormal. You

can perform this operation only if you understand
specifics of the thread.
onmode -Z
End a transaction, and applications become abnormal.

You can perform this operation only if you understand
specifics of the transaction.
onmode -d { standard|primary
Name of the data service |secondary
Name of the data service }
The data replication mode is cut down. Other users

may not be able to access the database. Therefore, run
this command only during emergencies.
onspaces -d
Delete the database space or the temporary database

space. Data can be missing.
Update/delete/select/load/unload/
Drop index/Create index and other
SQL operations
Perform SQL operations on large tables. In this case,

use indexes and pay attention to the number and
performance of locks. If the number of locks is
incorrect or performance of locks is poor, tables may
be locked and the database may break down. For
example, if you create indexes for a large table of more
than a million data records, you need to assess the
duration of creating the indexes. Specifically, if the
operation of creating an index is canceled, the rollback
time duration is the same as the duration of creating
the index. If you end the rollback forcibly by ending a
thread, the database breaks down.
Changing the password of the

database
Change the password of the database, you need to

change the configurations of the network elements that
connect the database.
Backing up the database
If you back up the database when the call traffic is

heavy, the system performance is affected.
Oracle Database
Table A-2 Critical operations in the Oracle database
Issue 01 (2010-09-29)
Operation
Description
lsnrctl stop
Stop the listener.

A-3
HUAWEI CBS
A Appendix
Operation
Description
Update/delete/select/load/unload/Drop
index/Create index and other SQL
operations
Perform SQL operations on large tables. In

this case, use indexes and pay attention to the
number and performance of locks. If the
number of locks is incorrect or performance
of locks is poor, tables may be locked and the
database may break down. For example, if
you create indexes for a table of more than a
million data records, you need to assess the
possible result. Specifically, if the operation
of creating an index is canceled, the rollback
time duration is the same as that of creating
the index. If you end the rollback by ending a
thread, the database breaks down.
/sbin/init.d/init.crs stop
Stop the Oracle database and CRS in Oracle

RAC mode.
SQL> shutdown immediate;
Stop the database.
SQL> alter system set parameter name =

parameter value scope = spfile;
Modify spile. For example, modify archive

paths.
SQL> DROP TABLESPACE name of the

data space INCLUDING CONTENTS
AND DATAFILES;
Data space is deleted and data is missing.
Directly edit files in $ORACLE_HOME/

network/admin/.
Changing the password of the database
Change the password of the database. In this

case, you need to change the configurations
of the NEs that connect the database.
Backing up the database.
If you back up the database when the call

traffic is heavy, the system performance is
affected.
ATAE
Table A-3 Critical operations in ATAE
A-4
Operation
Description
vxvol -g volume name stopall
Deactivate LVs.
vxassit -g VG name remove volume LV

name
Delete LVs.
vxdg destroy VG name
Delete VGs.
umount file system
Demount file systems.

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Operation
Description
haconf -dump -makero
Stop the VCS.
hastop -all -force

haconf -dump -makero
Issue 01 (2010-09-29)
hastop -all
Stop the VCS, processes and applications for

monitoring the two-node cluster; Unbind
floating IP addresses; Deactivate LVs and
VGs.
reboot
Restart the system.
shutdown
Stop the System.
kill -9 process ID
Forcibly kill the corresponding process.
rm *
Delete files.
Changing the values of kernel parameters
chmod
Change the properties of files.
chown
Change the owner and owner group of a file.
mv
Move or rename a file or directory.
ifconfig bondX:X floating IP netmask

subnet mask delete
Unbind floating IP addresses.
Changing IP addresses of devices, such as

USM servers, SMM blades, and storage
controllers
If IP addresses are changed, devices may be

disconnected and networks become
abnormal.
Changing the system time
You can change the system time only after

being approved. Otherwise, time of service
blades can be different from the system time.
Then, serious problems occur.
Changing the time zone and DST of the

system
Charging errors and call interruptions may

occur if you perform these operations when
data exists in the SMDB.
Changing the transmission rate and working

mode of network adapters
These operations may cause that the network

communications are interrupted.
Changing node names
This may cause the system to be abnormal.
Changing routes, access lists, and strategies

of the firewall
Modifying network services, such as the

Telnet and FTP services

A-5
HUAWEI CBS
A Appendix
HP Minicomputer
Table A-4 Critical Operations in an HP Minicomputer
A-6
Operation
Description
vgchange -a n VG name
Deactivate VGs.
lvremove
Delete LVs.
vgexport -s -m
Delete VGs.
umount file system
cmhaltcl
Stop the two-node cluster.
cmhaltnode
Stop a node of the two-node cluster.
cmhaltpkg
Stop application packages of the two-node

cluster.
cmhaltserv
Stop services on the two-node cluster.
reboot
Restart the system.
shutdown
Stop the System.
init
Stop and then restart a server to a specified

mode.
kill -9 process ID
ipcrm
Delete the message queue, semaphore, and ID

of the shared memory.
rm *
Delete files.
chmod
Change the permissions of the files.
chown
mv
ifconfig lanX:1 0.0.0.0
Changing IP addresses of minicomputers

abnormal.
Time of service blades can be different from

the system time if the system time is modified
against rules. In this case, serious problems
occur.
Modifying the time zone and DST of the

system


Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Operation
Description

mode of network adapters

Changing node names
This may cause the system to be abnormal.

of the firewall

Telnet and FTP services.
IBM Minicomputer
Table A-5 Critical Operations in IBM Minicomputer
Issue 01 (2010-09-29)
Operation
Description
varyoffvg VG name
Deactivate VGs.
reducevg -df physical volume name
Delete physical volumes.
rmlv -f LV name
Delete LVs.
rmdev
Remove devices.
umount file system
smit clstop
reboot
Restart the minicomputer.
shutdown
Stop the minicomputer.
init
Stop and then restart the minicomputer to a

specified mode.
kill -9 process ID
ipcrm
Delete the message queue, semaphore, and ID

of the shared memory.
rm *
Delete files.
stopsrc -s appspy
Stop the monitoring subsystem of the twonode cluster.
stopsrc -s cluster
chmod
Change the permissions of the files.
chown

A-7
HUAWEI CBS
A Appendix
Operation
Description
mv
ifconfig enX floating IP addresses netmask

subnet mask delete
Changing IP addresses of minicomputers

abnormal.
Time of service blades can be different from

the system time if the system time is changed
against rules. In this case, serious problems
occur.
Changing the time zone and DST of the

system.


mode of network adapters.

Changing node names
This may cause system to be abnormal.

of the firewall.

Telnet and FTP services
SCP
Table A-6 Critical operations on the SCP
A-8
Operation
Description
$HOME/bin/kill_scp.sh
Stop the SCP.
$HOME/bin/stop_scp.sh
Stop the SCP.
setval all
The function of printing messages on the SCP

platform is enabled, which affects the
performance of the related devices.
serviceadm
This service management command is used

to deactivate, uninstall, and delete Huawei
intelligent network services.
${UOA_RUN_ROOT}/shell/uoa_start.sh
Start the UOA.
${UOA_RUN_ROOT}/shell/uoa_stop.sh
Stop the UOA and applications cannot

generate alarms.

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Operation
Description
Updating network configuration files and

load charging matrix when the call traffic is
heavy
BMP
Table A-7 Critical operations on the BMP
Issue 01 (2010-09-29)
Operation
Description
$HOME/tools/stop_bmp.sh
End all the BMP processes and services are

interrupted.
$HOME/tools/stop_app.sh

interrupted.
$HOME/bin/stop.sh

interrupted.
$HOME/tools/stop_jboss.sh
End the JBOSS, which causes services to be

interrupted.
$HOME/tools/stop_enipapp.sh
End all ENIP Core processes.
$HOME/bin/stop_enip.sh
$HOME/bin/kill_enip.sh
Stop the UOA and applications cannot

generate alarms.
$HOME/jboss/bin/shutdown.sh
End the JBOSS process and services break

down.
logadm_bmp -on
Enable the debug log function.
Back up and store files and directories whose

suffixes are not .bak in $HOME/jboss/
server/default/deploy.
Startup of the JBOSS becomes abnormal.
serviceadm
Deactivate or uninstall services, and then

sessions and some services become
interrupted.
configadm
Running the configadm command

improperly causes the system to be abnormal.
logadm
Run this command to manage ENIP CORE

logs.
ipmaptool
Running the ipmaptool command


A-9
HUAWEI CBS
A Appendix
CBP
Table A-8 Critical Operations on the CBP
Operation
Description
$HOME/tools/stop_cbp.sh
End all CBP processes, and then sessions and

some services become interrupted.
$HOME/tools/stop_app.sh

$HOME/bin/stop_enip.sh

$HOME/bin/stop.sh

$HOME/bin/kill_enip.sh

Stop the UOA, which causes that applications

cannot generate alarms.
logadm
Run this command to manage ENIP CORE

logs.
serviceadm
Deactivate or uninstall services, and then

sessions and some services become
interrupted.
configadm
Running the configadm command

ipmaptool
Running the ipmaptool command

Running kill -9 to end CBP processes that

access the SMDB
This operation causes the SMDB to be

abnormal.
SMDB
Table A-9 Critical operations in the SMDB
A-10
Operation
Description
${SMDB_ROOT}/bin/stop_mdb.sh
Stop the SMDB, which triggers the

switchover.
${SMDB_ROOT}/bin/mdmode
Set the run mode of the SMDB.
${SMDB_ROOT}/bin/mddel.sh
Delete the shared memory of the SMDB.

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Operation
Description
Performing mdalter and mdrestore

operations in ${SMDB_ROOT}/bin
Running mdauto.sh and SynMemDB in $

{SMDB_ROOT}/bin
Run mdauto.sh and SynMemDB in $

{SMDB_ROOT}/bin, which causes the
memory size to be rebuilt and the physical
database to be synchronized.
Using the mdsql tool of the SMDB to perform

the operations including update, delete,
drop and alter.
Use the mdsql tool of the SMDB to perform

the operations including update, delete,
drop and alter. For example, perform these
operations on table spaces.
Running kill to end a parent process and

container0 during the restart of a service
Run kill to end a parent process and

container0 during the restart of a service, and
the switchover is triggered.
A.2 Impact Analysis Table of CBS Password Change

Certain passwords are saved in the configuration files. When you change a password, you also
need to modify the configuration file that contains the password. If only the password is changed
and the configuration file is not modified, severe abnormality such as database access failure
may occur.
Table A-10 Impact analysis table of CBS password change
User
Home
Group
Usage
Impact After Password Change
root
root
None.
No impact.
Informix
Informix
Installation and
running user of
the Informix
database.
No impact.
bmp
enip
Installation and
running user of
the BMP.
If you obtain CDRs as this user, the RBI is

involved. In this case, the corresponding
password is required on the RBI configuration
page.
uoa
enip
Installation and
running user of
the Uniform
Operation and
Management
Agent (OAM).
No impact.
BMP
Issue 01 (2010-09-29)

A-11
HUAWEI CBS
A Appendix
User
Home
Group
Usage
dbserver
enip
User for
installation.
No impact.
sysdb
enip
User for
accessing the
BMP system
database.
The following modules are involved:

l
BME:
Related configuration of the DSB: Change the
user name and password of the system
database in $HOME/jboss/server/default/
conf/login-config.xml according to
<security-domain>bmp_JBossRelam_0</
security-domain> in <jndiname>InformixXADS</jndi-name> of
bmp-xa-ds.xml. Encrypt the changed
password and fill it in password. You need to
use bmp_encrypt.sh to convert the password
in cipher text. Then restart the JBOSS.
You need to modify the $HOME/config/
bmp.server.xml .
In later versions of C03, you need to change
the .odbc.ini file in home directory and use
Dissect encryption.
A-12
userdb
enip
User name for

accessing the
BMP user
database.
mml
None
Password of the
MML interface.
yournam
e
None
User name and

password for
logging in to the
mail server.
Dssync: Use the configadm tool to change the

value of the ENIPcore configuration item.
When changing the value of the
ENIP.Common.DBUSER.password
configuration item, you need to use Dissect
encryption in the bin directory of the CBP
user.
CBP: The SMDB is affected. You need to

modify the .ODBC.ini file manually. You
need to use the Dissect to encrypt the password
filled in .ODBC.ini
TaskControl: ${ENIP_HOME}/config/
TaskControl/FileConvert.cfg and
USERID /PASSWORD files need to be
modified.
See the password change impact analysis of the

sysdb user of the BMP.

Issue 01 (2010-09-29)
HUAWEI CBS
User
A Appendix
Home
Group
Usage
root
root
None.
No impact.
Informix
Informix
Installation and
running user of
the Informix
database.
No impact.
cbp
enip
Installation and
running user of
the CBP.
CBP
BUS: The FTP configuration file

ftphelper.xml needs to be modified.
RBI: If you obtain CDRs as this user, the

corresponding password is required on the
RBI configuration page.
smdb
enip
Installation and
running user of
the Smart
Memory
Database
(SMDB).
No impact.
uoa
enip
Installation and
running user of
the UOA.
No impact.
dbXXX:
XXX is
the CBP
node.
enip
User name for

accessing the
CBP physical
database on the
CBPDB blade
when the
network
database is
used.
See the password change impact analysis of the

sysdb user of the BMP.
dbserver
None.
User name for

creating the
database cbpdb.
No impact.
root
root
None.
No impact.
Informix
Informix
Installation and
running user of
the Informix
database.
No impact.
SMP
Issue 01 (2010-09-29)

A-13
HUAWEI CBS
A Appendix
User
Home
Group
Usage
smp
tellin
Installation and
running user of
the SMP.
The SMP uses the sms user to access the database

to change the password. The application is not
affected.
oams
tellin
Installation and
running user of
the
OAMServer.
No impact.
soam
tellin
Installation and
running user of
the independent
OAMServer.
No impact.
uoa
tellin
Installation and
running user of
the UOA.
No impact.
root
root
None.
No impact.
Informix
Informix
Installation and
running user of
the Informix
database.
No impact.
scu
tellin
Installation and
running user of
the SCP.
The following module is involved:
FTP user name

of the SCP.
SCP
sms
A-14
tellin
BUS: The FTP configuration file ftphelper.xml

for configuring short messages needs to be
modified. It is recommended that the IP address
of the SMS module should be used as the IP
address of the FTP.
BUS: The FTP configuration file

ftphelper.xml needs to be modified.
In LDS mode, the login-config.xml file needs
to be modified.
SMP: The commserv db process of the SMP

is affected. You need to restart this process
after using the dbcfgtool tool to synchronize
the password.
SMPSER: The license update is affected. The

FTP password in the platform configuration
file inetcfg.cfg needs to be changed.
RBI: If connections are configured, the

password needs to be changed on the
configuration page.

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
User
Home
Group
Usage
oams
tellin
Installation and
running user of
the
OAMServer.
No impact.
soam
tellin
Installation and
running user of
the independent
OAMServer.
No impact.
uoa
tellin
Installation and
running user of
the UOA.
No impact.
root
root
None.
No impact.
Informix
Informix
Installation and
running user of
the Informix
database.
Offices that do not use the SMS discrete number

scheme: Password change does not affect the
application.
GFEP
Offices that use the discrete number scheme: The

login-config.xml file needs to be modified, and
the JBOSS needs to be restarted.
gfep
gfep
Installation and
running user of
the SCP.
No impact.
uoa
gfep
Installation and
running user of
the UOA.
No impact.
A.3 Glossary
A
Issue 01 (2010-09-29)
Account
An entity through which a customer can pay for the

telecommunications services provided by a carrier. An
account is the minimum unit for billing settlement.
Account accumulation
A process of accumulating the fees of a CDR to relevant

account items according to different fee types.
Account book
A book that records the information about the income and

expense of each fee item in the account by class. An
account matches one or more account books. An account
book often records the information such as account
number, bill cycle, and account book subject.

A-15
HUAWEI CBS
A Appendix
Accumulation item
The accumulation of the service usage, consumption, and

recharge fees of a subscriber.
Activation
An operation that enables a subscriber to use different

telecommunications services provided by a carrier. After
being activated, a subscriber account enters the active
period, and the state of the subscriber is Active.
Active period
A specific period in the life cycle of a subscriber account.

The subscriber account is in Active state within the active
period. A subscriber account enters the Active state after
being activated. Subscribers whose accounts are in
Active state can use the telecommunications services
provided by carriers.
Admission limit
The minimum consumption amount that a carrier sets for

a subscriber in a bill cycle. If the consumption amount of
a subscriber does not reach the minimum consumption
amount that the carrier sets, the CBS system deducts the
minimum consumption amount that the carrier sets.
Advance payment
A fee that is paid by a customer in advance when the

customer is not in arrears.
Appendant product
The products that a subscriber can subscribe to when the

subscriber selects a certain brand.
Authorization
An action for determining whether an entity can access the

resources after a request.
A-16
Basic fee
A fee that a subscriber pays for the telecommunication

through a network or channel of a carrier regardless of a
specific service. It is also called channel fee. The charge
rate of the basic fee is often fixed.
Basic fee for voice service
The local call fees or roaming fees that a subscriber needs

to pay a carrier when the subscriber uses the network of
the carrier to make or answer calls. When a subscriber
makes or answers a call on the registered mobile local
network, that is, in the home area, the local call fees are
deducted. When the subscriber roams to other mobile local
networks, the roaming fee is deducted.
Bill
A list through which a carrier provides the service fee

information periodically for a subscriber. A bill records the
information such as the final balance and the fees for using
the services and products. Bills are classified into detail
bills and summary bills. A carrier charges a subscriber
according to the information on the bill.

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Bill cycle
The interval for charging service fees from subscribers.

The interval can be set according to the operation strategy
of a carrier and is often one month. When a bill cycle ends,
the CBS system calculates the fees that a subscriber needs
to pay in the bill cycle and generates a bill.
Bill run
A process of calculating the billing result such as the

monthly fee, discount, incentive, usage summary, free unit,
rebate, and other charge and credit (OCC).
Blacklist
A list that records the information about the customers with

restricted transactions. The customers in the blacklist are
forbidden to use certain services. The carrier can add the
customers who are in arrears for a long period, break
contracts, or have little credit to the blacklist.
BMP
A network element of the CBS system that manages the

operation of services, such as product management,
charging management, resource management.
Brand
A name that a carrier defines after segmenting the market

and combining the products according to the ages,
consumption habits, and consumption levels of customers.
A carrier combines products and sells the combination to
specified customer groups by brand to make profits.
Issue 01 (2010-09-29)
Call control
A function of processing a call, consisting of creating,

monitoring, maintaining, connecting, and releasing a call
and providing service features.
Call forwarding
An operation performed by a service agent to forward a

call to the IVR process or other service agents in the
customer service center when the service agent processes
a call. A call can be forwarded to the IVR process in either
of the following modes: hang-up forwarding and blind
forwarding. A call can be forwarded to an agent in any of
the following modes: talk forwarding, connect forwarding,
blind forwarding, and three-party forwarding. A call can
be forwarded to a specified service agent in the mode of
specified forwarding.
Call screening
A service of call control. If the service is enabled for a

subscriber, the subscriber can maintain a screening table
that records the information such as discrete numbers,
number segments, areas, time segments, and passwords.
Before a call is connected, the CBS system determines
whether to continue the call according to the current
attribute of the calling subscriber and the information such
as the screening table, screening type, screening strategy,
and screening mode.

A-17
HUAWEI CBS
A Appendix
CAMEL subscription
information
The information that identifies whether a subscriber

subscribes to an intelligent service. The CSI contains the
operation support information related to a subscriber, such
as the service key. Generally, the CSI contains OriginatedCAMEL Subscription Information (O-CSI) and
Terminated-CAMEL Subscription Information (T-CSI).
CBP
A network element of the CBS system for receiving

external charging requests and performing online and
offline charging.
CBS
A solution that implements the convergence of online

charging and offline charging, voice service charging and
data service charging, prepaid subscriber management and
postpaid subscriber management. The CBS is an integrated
end-to-end business operation and support system,
providing the functions such as product management,
resource management, integrated operation, customer
service agent, accounting calculation, credit control,
settlement, recharging center, and call control.
CDR
A call detail record that records the information about a

certain charging event collected in a certain format. The
information includes the time when the call is made, the
call duration, and the data transmission quantity. A call
detail record is used for charging and settlement, and serves
as the service usage record provided for subscribers.
Content fee
The extra fee that is charged if a service provides certain

information. The charge rate of the content fee is variable
and relates to specific services.
Collect call
A service in which a called party pays the call fee for the
calling party in a call. When a subscriber makes a collect
call, the subscriber needs to dial the collect call access code
before dialing the called number.
Cooperate customer
An organization or enterprise that signs a contract with a

carrier. A corporate customer subscribes to and uses the
telecommunications services and products provided by a
carrier.
Credit control
A process of controlling the consumption amount of the

telecommunications services for a subscriber according to
the remaining call fee and credit limit of the subscriber.
Credit limit
An amount that a subscriber can overdraw.
Customer
An individual, an enterprise, or a corporation that uses the

products or services provided by a carrier or a third-party
partner. Customers are classified into individual customers
and corporate customers.
A-18

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Deactivation
An operation that disables a postpaid subscriber to use

different telecommunications services provided by a
carrier. After being deactivated, a subscriber account
enters the Disable state.
Deposit
An amount of money that a customer pays in advance for

using a particular service.
Disable
A state that an account enters if the subscriber of an account

does not recharge the account that is in Suspend state after
the suspend period. The Disable state can be MO barred
or MO&MT barred. A subscriber in MO barred state can
only answer calls and a subscriber in MO&MT barred
state can neither make calls nor answer calls.
F
Familiarity number
A mobile number that a subscriber sets, which can enjoy a

preferential tariff when a call is made between this mobile
number and the mobile number of the subscriber. The
number of familiarity numbers that a subscriber can set is
determined by the carrier. Special numbers such as a
customer service number cannot be set as familiarity
numbers.
Fee item
A detailed item of the consumption fees of a subscriber.

For example, the local call fee item and national toll call
fee item.
Free resources
A resource that a carrier provides for subscribers for free

use. Free resources include a certain number of short
messages, the call duration, and the data traffic.
G
Group condition
The rule for distinguishing scenarios or subscriber objects.

For a certain service that a carrier provides, the charge fees
vary according to the scenario or subscriber object.
H
Hot billing
A process of performing the real-time bill run and

generating a bill before the end of a bill cycle as requested
by a subscriber. The bill records the consumption of the
subscriber in the bill cycle.
I
Instantiation
Issue 01 (2010-09-29)
A process of defining the tariff of a product when the

product is created, including the operations of selecting the
matching service and defining the tariff for the service.

A-19
HUAWEI CBS
A Appendix
IVR
A telecommunications system, prevalent with PBX and

voice mail systems, that uses a prerecorded database of
voice messages to present options to a user, typically over
telephone lines. User input is retrieved via DTMF tone key
presses.
M
Main product
A product that a subscriber must subscribe to during the

registration according to the system settings and that is
bound with the basic fee of a brand.
MO barred
A specific state in the life cycle of a subscriber. It is also

called suspension. A subscriber in this state can only
answer calls.
N
Network element
A network device that actually exists and has the basic

information such as an IP address, port number, user name,
and password.
Northbound interface
A software interface that the I2000 provides for superior

NMSs or the third-party integrated analysis software
(namely, the external system).
O
Offline charging
A charging mechanism where the charging information

does not affect the service provisioning in real time. The
offline charging is based on bills, that is, the system
performs rating and fee deduction according to the
collected original call records of subscribers.
Online charging
A charging mechanism for monitoring the account balance

online in real time. When the account balance of a
subscriber is used up, the system prevents the subscriber
from using the service. In this case, the risk of owing fees
is reduced.
CBS
A system that implements the convergence of online

charging and offline charging, voice service charging and
data service charging, prepaid subscriber management and
postpaid subscriber management. The CBS system
provides the functions such as rating, subscriber balance
management, and real-time monitor.
Organization
An abstract concept. It refers to the structure of enterprise

organizations. Organizations are hierarchically connected.
A-20

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Point
The credit amount that a subscriber can obtain based on the

contribution of the subscriber to a carrier. The points are
converted according to the consumption amount of a
subscriber. The subscriber can use the points to exchange
for certain product or products.
Pool period
A period in which a subscriber of an account that is in

Disable state does not recharge the account after the
deletion period An account in this period is in Pool state.
A subscriber in Pool state cannot perform any operations.
The CBS system deletes the subscriber account and
reclaims the number resources after the pool period.
Postpaid service
A service that requires customers to pay for calls or other

services in advance. When a customer uses a certain
service that is provided by a carrier, the network performs
real-time charging on the service usage. The usage fee is
deducted from the prepayment.
Prepaid service
A service that requires customers to pay for calls or other

services in advance. When a customer uses a certain
service that is provided by a carrier, the network performs
real-time charging on the service usage. The usage fee is
deducted from the prepayment.
Price event
The action of using the telecommunications network

resources and the services. For example, a voice call and a
message transfer between users, the information
interaction between subscribers and application systems,
the roaming service, the interconnection service between
carriers, and other events that carriers want to charge fees.
Price Plan
A set of pricing policies provided by a carrier for a group

of telecommunications services. The charging system can
calculate the fees for using the service based on the service
usage and pricing plan of a subscriber.
Product
A combination of one or more services with predefined

tariff. Carriers can directly sell the combination of services
to customers.
Promotion
A flexible marketing strategy that a carrier uses to attract

subscribers. When a subscriber meets certain conditions,
for example, the service consumption of the subscriber
reaches a preset value or the subscriber subscribes to a
product, the subscriber can enjoy preferential policies.
R
Recharge
Issue 01 (2010-09-29)
To add an amount or a service volume to an account of the

service system through a valued card or by cash.

A-21
HUAWEI CBS
A Appendix
Recharge blacklist
A subscriber account state that a carrier sets to prevent

subscribers from attempting to recharge accounts by
guessing recharge card number or password. If the number
of events that a subscriber enters incorrect recharge card
numbers or passwords consecutively reaches the threshold
in the system when the subscriber recharges an account,
the subscriber enters the recharge blacklist state. In this
case, the recharge function of the subscriber is restricted.
Reservation
An operation of the CBS system reserving and freezing a

certain amount of the account balance before subscribers
use the services that a carrier provides to ensure that the
accounts have enough balance to pay the service using fee.
In the CBS system, reservation can avoid overdraft when
subscribers use multiple services concurrently.
Reservation return
An operation that the system returns the reserved balance

or resources to the subscriber accounts. The reasons for
reservation return may be one of the following: service
rollback, service timeout, and reserved amount or
resources not used up
Roaming
The action of a subscriber using services on a non-home

telecommunications network.
Roaming in
A process for a subscriber to access the home

telecommunications network from a non-home
Roaming out
A process for a subscriber to access a non-home

telecommunications network from the home
A-22
SCP
A physical entity in the intelligent network that implements

a service control function.
Service
A group of functions, material objects, or procedures that

a service provider develops for sale in products. A service
does not have any price and cannot be sold to subscribers.
Settlement
A process of allocating the collected service fees that are

generated during the cooperation between partners when a
telecommunications service involves the communication
resources or value-added service resources of multiple
partners. The fee allocation is based on the resource usage
and agreement that is signed by the partners in advance.
Subscriber
An object that a carrier defines based on a customer after

the customer subscribes to a product or a service.

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Suspend period
The period in which a subscriber account is not recharged

after the active period. An account in the suspend period
is in Suspend state. Generally, the balance and bonus
resources of an account in Suspend state are available. The
subscriber is restricted in using certain services. For
example, a subscriber of an account that is in Suspend state
cannot use the free resource account for making calls. If a
subscriber recharges an account during the suspend period,
the account returns to Active state. At the same time, the
validity period of the account is extended.
T
Tariff
A term related to the pricing and discount policies of a

product. Generally, the tariffs are classified into usage
tariff, rental tariff, discount tariff, and reward tariff.
Tariff policy
The policy used to define the rule condition, charging rate,

and charging action for different tariffs. One or multiple
policies exist for a product. For example, after a subscriber
subscribes to a GPRS package, a monthly rental of 20
dollars is charged each month. If the monthly rental is
charged successfully, the subscriber can use the GPRS
service. When the subscriber answers calls, no fee is
charged. For the GPRS package, three policies exist:
monthly rental policy, policy of using the GPRS service
for free, and policy of charging the called party free.
Tariff policy template
A set of tariff rules, which abstract the tariff service logic

with common attributes and encapsulate complicated
logic. Template is short for tariff policy template. The
templates are used to customize the calculation rules of
rating, fee deduction, and accumulation about a charging
event. The CBS system determines whether to perform an
action according to template conditions to implement the
corresponding tariff policy.
Time schema
The time condition that needs to be met when a tariff is

defined so that different charging rates are adopted in
different time segments.
Transfer account balance
A process of transferring the account balance of an account

to another account.
U
Upper limit
Issue 01 (2010-09-29)
The maximum consumption amount that a carrier sets for

a subscriber in a bill cycle. If the consumption amount if a
subscriber exceeds the maximum consumption amount
that the carrier sets, the CBS system still deducts the
maximum consumption amount that the carrier sets.

A-23
HUAWEI CBS
A Appendix
W
White list
A set of lists for controlling whether a subscriber can log

in to the CBS system or use telecommunications services.
Only subscribers in this list can log in to the CBS system
or use telecommunications services.
A.4 Acronyms and Abbreviations

3
3GPP
The Third Generation Partner Plan
A
AAA
Authentication, Authorization, and

Accounting
ABNF
Augmented Backus Naur Form
AC
Apply Charging
ACK
Acknowledgement
ACR
Apply Charging Report
AIP
Advanced Intelligent Peripheral
AoC
Announce of Charge
API
Application Programming Interface
APN
Access Point Name
AS
Application Server
ATI
Automatic Transmitter Identification
ATM
Automatic Teller Machine
AVP
Attribute Value Pairs
A-24
BME
Business Management Environment
BMP
Business Management Point
BSS
Business Support System

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
Issue 01 (2010-09-29)
CAA
Client Access Agent
CAC
Charging Area Cell
CAP
CAMEL Application Part
CAZ
Charging Area Zone
CBE
Convergent Billing Engine
CBP
Convergence Billing Point
CBCP
Convergent Billing Configuration Point
CBS
Convergent Billing System
CC
Customer Care
CCF
Call Control Function
CCBS
Custom Care & Billing Solution
CCA
Credit Control Answer
CC&BM
Customer Care and Business Management
CCR
Credit Control Request
CDMA
Code Division Multiple Access
CDR
Call Detail Record
CDRSC
Call Detail Record Store and Convert
CF
Call Forwarding
CFC
Call Froward Conditional
CFU
Call Froward Unconditional
CNL
National Location Code
COS
Class of Service
CP
Content Provider
CRM
Customer Relationship Management
CTD
Cell and Time Distribution
CTI
Computer Telephony Integration
CS
Circuit Switched
CSI
CAMEL Subscription Information
CSP
Communication Service Provider
CUG
Closed User Group

A-25
HUAWEI CBS
A Appendix
D
DCC
Diameter Credit Control
DCCA
Diameter Credit Control Application
DNS
Domain Name Server
DP
Detection Point
DR
Delivery Report
DSC
Digital Speaking Clock
DSL
Digital Subscriber Line
DTMF
Dual Tone Multi-Frequency
E
EDGE
Enhanced Data rates for GSM Evolution
ENIP
Enhanced Network Intelligent Platform
ETL
Extraction, Transformation, Loading
eTOM
enhanced Telecom Operations Map
F
FA
Foreign Agent
FCI
Full Configuration Interaction
FEID
Front End ID
FEP
Front End Processor
FEPID
Front End Processor ID
FN
Familiarity Number
FPH
Free Phone
FQDN
Fully Qualified Domain Name
FTP
File Transfer Protocol
A-26
GFEP
General Front End Processor
GGSN
Gateway GPRS Support Node
GLR
Gateway Location Register
GMSC
Gateway Mobile Switching Center

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
GPRS
General Packet Radio Service
GSM
Global System for Mobile communications
GUI
Graphical User Interface
GW
GateWay
H
HLR
Home Location Register
HTTP
Hypertext Transfer Protocol
Issue 01 (2010-09-29)
ICCID
Integrated Circuit Card Identity
ICS
Incoming Call Screen
ID
Identity
IDD
International Direct Dialing
IDP
Initial Detection Point
IMEI
International Mobile Station Equipment

Identity
IMS
IP Multimedia Subsystem
IMSI
International Mobile Subscriber Identity
IN
Intelligent Network
INAP
Intelligent Network Application Protocol
IP
Internet Protocol
IP
Intelligent Peripherals
IPCG
IP Charging Gateway
IPv4
Internet Protocol version 4
IPv6
Internet Protocol version 6
IR
International Roam
ISDN
Integrated Services Digital Network
ISO
International Standard Organization
ISUP
ISDN User Part
ITU-T
International Telecommunication Union Telecommunication Standardization Sector
IVR
Interactive Voice Response

A-27
HUAWEI CBS
A Appendix
L
LAC
Location Area Code
LN
Love Number
M
MAP
Mobile Application Part
MCC
Mobile Country Code
MCN
Multiple Subscriber Number
MCN
Missed Call Notification
MDCC
Mobile Data Service Control Center
MDMC
Mobile Data Service Management Center
MDN
Mobile Directory Number
MDSP
Mobile Data Service Platform
MF
Master File
MML
Man-Machine Language
MMS
Multimedia Message Service
MMSC
Multimedia Message Service Center
MMSO
MMS Originator
MMSR
MMS Recipient
MNC
Mobile Network Code
MO
Mobile Originated
MSC
Mobile Switching Center
MSISDN
Mobile Station International ISDN Number
MT
Mobile Terminated
A-28
NAI
Network Access Identifier
NAS
Network Access Server
NE
Network Element
NGN
Next Generation Network
NM
Network Management

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
NP
Number Portability
NTP
Network Time Protocol
O
OCP
Online Charging Point
CBS
Online Charging System
OSS
Operation Support System
P
P2P
Point to Point
PA
Play Announcement
PBX
Private Branch Exchange
PC
Pricing Catalogue
PDP
Packet Data Protocol
PDU
Protocol Data Unit
P-FPH
Personal Free Phone
PHS
Personal Handyphone System
PID
Process ID
PIN
Personal Identification Number
PLMN
Public Land Mobile Network
PMN
Public Mobile Network
POP
Post Office Protocol
PPS
Prepaid Service
PRM
Partner Relationship Management
PS
Packet Switched
PSI
Payment Server Interface
PSTN
Public Switched Telephone Network
Q
QoS
Quality of Service
R
RADIUS
Issue 01 (2010-09-29)
Remote Authentication Dial-In User Service

A-29
HUAWEI CBS
A Appendix
RBI
Record Bill Interface
RBT
Ring Back Tone
RFC
Remote Feature Control
RN
Route Number
RRR
Read Reply Report
RTCP
Real-time Transport Control Protocol
RTP
Real-time Transport Protocol
RTSP
Real-Time Streaming Protocol
RUIM
Removable User Identity Module
A-30
SCF
Service Control Function
SCP
Service Control Point
SCTP
Stream Control Transmission Protocol
SCU
Service Control Unit
SDR
Special Drawing Rights
SDU
Service Data Unit
SGSN
Serving GPRS Support Node
SIGTRAN
Signaling Transport
SIP
Session initiation Protocol
SIM
Subscriber Identity Module
SMAP
Short Message Access Protocol
SMOI
Service Management Open Interface
SMP
Service Management Point
SMPP
Short Message Peer to Peer
SMS
Service Management System
SMS
Short Message Service
SMSC
Short Message Service Center
SMTP
Simple Mail Transfer Protocol
SNMP
Simple Network Management Protocol
SP
Service Provider
SRF
Specialized Resource Function

Issue 01 (2010-09-29)
HUAWEI CBS
A Appendix
SSN
Security Server Network
SSP
Service Switching Point
STP
Signaling Transfer Point
T
TCAP
Transaction Capabilities Application Part
TCP
Transfer Control Protocol
TDM
Time Division Multiplex
TDMA
Time Division Multiple Access
TD-SCDMA
Time Division-Synchronous Code Division

Multiple Access
TLS
Transport Layer Security
TUP
Telephone User Part
U
UAP
U-SYS universal access platform
UCB
USSD Call Back
UOA
Uniform OM Agent
URI
Uniform Resource Identifier
URL
Universal Resource Locator
URP
Universal Resource Platform
USAU
Universal Signaling Access Unit
USSD
Unstructured Supplementary Service Data
UTC
Universal Time Coordinated
UVC
Uniform Voucher Center
UVS
Uniform Voice Solutions
Issue 01 (2010-09-29)
VAT
Value-added tax
VC
Voucher Center
VLR
Visitor Location Register
VMS
Voice Mail System
VoIP
Voice over IP
A-31
HUAWEI CBS
A Appendix
VPN
Virtual Private Network
VSCP
Value-added Service Control Point
A-32
WAP
Wireless Application Protocol
WCDMA
Wideband Code Division Multiple Access
WIFI
Wireless fidelity
WIMAX
Worldwide Interoperability for Microwave

Access
WIN
Wireless Intelligent Network
WISG
Wireless Integrated Service Gateway

Issue 01 (2010-09-29)

HUAWEI CBS Routine Maintenance Guide - (R002C02LG0201 - 01, Baseline-Common) - For Customer

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

HUAWEI CBS Routine Maintenance Guide - (R002C02LG0201 - 01, Baseline-Common) - For Customer

Diunggah oleh

Hak Cipta:

Format Tersedia

HUAWEI CBS

Routine Maintenance Guide

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Technical support engineers

Changes in Issue 01 (2010-09-29)

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

3.5.14 Checking the Status of Network Adapters (HP)................................................................................3-26

Huawei Proprietary and Confidential

3.7.16 Checking the Number of CDRs on the CBP......................................................................................3-74

Huawei Proprietary and Confidential

5.2.1 Cleaning the Tape Drive......................................................................................................................5-34

8 Maintenance Related to Upgrade............................................................................................8-1

Huawei Proprietary and Confidential

9 Routine Maintenance Tables...................................................................................................9-1

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Figure 8-6 iWeb backup menu...........................................................................................................................8-29

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Table A-7 Critical operations on the BMP..........................................................................................................A-9

Huawei Proprietary and Confidential

About This Chapter

Huawei Proprietary and Confidential

1.1 Concept of Routine Maintenance

Scenario of performing a task

Effects of a risk in different periods

1.2 Requirements for Routine Maintenance

1.2.1 Qualifications for the Maintenance Personnel

Understand the principle and networking of each system component.

Master the common maintenance tools.

Have the skills of summarizing and analyzing data.

1.2.2 Requirements for the Running Environment

A high-voltage static air cleaner is a recommended device in the minicomputer room.

Power Supply System

Huawei Proprietary and Confidential

Air Conditioning System, Lighting System, and Fire Prevention

Equipment: All equipment must be packed properly.

Relative humidity: 30% to 80%.

Allowed Number of Particles

The content of sulfur dioxide cannot exceed 0.14 ppm.

1.2.3 Requirements for Security Management

Avoid portable computers to connect to the LAN.

Huawei Proprietary and Confidential

Strictly control the enabling of the network services.

1.2.4 Requirements for Equipment Documents

Engineering documents of network

Engineering documents of device

Engineering documents of upgrade

Equipment room layout

Specifications of special software

Technical documents, user documents, and maintenance documents delivered with

1.3 Maintenance Tools

Provides alarm information in real

I2000 iCnfg Help

HUAWEI CBS Alarm Reference