SJ-20101208143956-019-ZXWN MSCS (V4.10.13) MSC Server Routine Maintenance Guide

ZXWN MSCS
MSC Server
Routine Maintenance Guide
Version: V4.10.13
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revison Reason
R1.0 2011-02-28 First edition
Serial Number: SJ-20101208143956-019
Publishing Date: 2011-02-28(R1.0)

Contents
About This Manual ......................................................................................... I
Declaration of RoHS Compliance ................................................................. I
Chapter 1 Safety Precautions.................................................................... 1-1
1.1 Overview ........................................................................................................... 1-1
1.2 Safety Precautions ............................................................................................. 1-1
1.3 Safety Symbol.................................................................................................... 1-1
Chapter 2 Overview of Routine Maintenance .......................................... 2-1

2.1 Overview ........................................................................................................... 2-1
2.2 Routine Maintenance Classification ..................................................................... 2-1
2.3 Common Maintenance Methods .......................................................................... 2-2
2.4 Precautions on Routine Maintenance .................................................................. 2-4
Chapter 3 Routine Maintenance................................................................ 3-1

3.1 Overview ........................................................................................................... 3-1
3.2 Introduction to Routine Maintenance.................................................................... 3-1
3.3 Daily Routine Maintenance ................................................................................. 3-2
3.3.1 Checking Equipment Room Environment ................................................... 3-3
3.3.2 Checking Power Supply in the Equipment Room ........................................ 3-4
3.3.3 Checking Board CPU Status ..................................................................... 3-4
3.3.4 Checking Equipment Working Status ......................................................... 3-5
3.3.5 Checking Office Status of SS7 Links.......................................................... 3-6
3.3.6 Checking Association Link Status .............................................................. 3-7
3.3.7 Checking Trunk Circuit Status ................................................................... 3-8
3.3.8 Checking Fault Management System ........................................................ 3-9
3.3.9 Checking Mc Interface Status.................................................................. 3-10
3.3.10 Checking Mg/Mj Interface Status (apply for MGCF) .................................3-11
3.3.11 Checking MGW Registration Status ....................................................... 3-12
3.3.12 Analyzing Performance Statistics Data (Daily Maintenance) .................... 3-12
3.3.13 Checking Dual-Homing Working Status.................................................. 3-13
3.3.14 Checking Billing System........................................................................ 3-14
3.3.15 Checking the Running Status of the Foreground..................................... 3-14
3.3.16 Checking the Running Status of the NMS System .................................. 3-15
3.4 Weekly Routine Maintenance............................................................................ 3-15
3.4.1 Checking the Running Status of the Server .............................................. 3-16
I
3.4.2 Backing up Configuration Data in NMS Mode........................................... 3-17
3.4.3 Analyzing Performance Statistics Data (Weekly Maintenance) .................. 3-18
3.5 Monthly Routine Maintenance ........................................................................... 3-18
3.5.1 Analyzing Performance Statistics Data (Monthly Maintenance).................. 3-19
3.5.2 Checking Performance Statistics Tasks.................................................... 3-19
3.5.3 Performing Data Backup......................................................................... 3-20
3.5.4 Checking Billing Files ............................................................................. 3-21
3.6 Quarterly Routine Maintenance ......................................................................... 3-21
3.6.1 Checking System Time ........................................................................... 3-22
3.6.2 Checking the Remote Control Tool .......................................................... 3-23
3.6.3 Checking Operating System Logs ........................................................... 3-25
3.6.4 Checking Database Logs ........................................................................ 3-25
3.7 Yearly Routine Maintenance.............................................................................. 3-26
3.7.1 Performing Changeover on the Important Boards ..................................... 3-26
3.7.2 Testing Dual-Server Changeover on Billing Server.................................... 3-27
3.7.3 Testing Dual-Homing Disaster Recovery Changeover ............................... 3-28
3.7.4 Cleaning Equipment ............................................................................... 3-29
3.7.5 Checking Ground Resistance.................................................................. 3-29
Appendix A Reference Table for Maintenance ....................................... A-1

Appendix B Common Maintenance Table ............................................... B-1
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II
About This Manual
Purpose
The purpose of this manual is to provide procedures and guidelines that support the routine
maintenance operations of ZXWN MSCS.
Intended Audience
This document is intended for engineers and technicians who perform routine maintenance
on ZXWN MSCS.
Prerequisite Skill and Knowledge

To use this document effectively, users should have a general understanding of wireless
telecommunications technology. Familiarity with the following is helpful:
l ZXWN MSCS product and its various components.
l ZXWN MSCS operating procedures.
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
Chapter 1, Safety Precautions This chapter aims to provide the safety precautions to be
known prior to the equipment operation and maintenance.
Chapter 2, Overview of Routine This chapter introduces the classification of routine

Maintenance maintenance, common maintenance methods and precautions
of ZXWN MSCS.
Chapter 3, Routine Maintenance This chapter introduces the routine maintenance activities
about ZXWN MSCS.
Appendix A, Reference Tables for This part lists the maintenance reference table.
Maintenance
Appendix B, Common Maintenance This part lists common maintenance table.

Table
FCC Compliance Statement

This device complies with part 15 of the FCC Rules. Operation is subject to the following
two conditions.
1. This device may not cause harmful interference.

2. This device must accept any interference received, including interference that may
cause undesired operation.
I
Changes or modifications not expressly approved by the party responsible for compliance
could void the user's authority to operate the equipment.
Conventions
ZTE documents employ the following typographical conventions.
Typeface Meaning
Italics References to other Manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input fields, radio button names, check boxes,
drop-down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens and company name.
Note: Provides additional information about a certain topic.
Checkpoint: Indicates that a particular step needs to be checked before proceeding

further.
Tip: Indicates a suggestion or hint to make things easier or more productive for the
reader.
II
Declaration of RoHS
Compliance
To minimize environmental impacts and take more responsibilities to the earth we live
on, this document shall serve as a formal declaration that ZXWN MSCS manufactured
by ZTE CORPORATION is in compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with respect to the following
substances:
l Lead (Pb)
l Mercury (Hg)
l Cadmium (Cd)
l Hexavalent Chromium (Cr (VI))
l PolyBrominated Biphenyls (PBBs)
l PolyBrominated Diphenyl Ethers (PBDEs)
ZXWN MSCS manufactured by ZTE CORPORATION meets the requirements of EU 2002/95/EC;

however, some assemblies are customized to client specifications. Addition of specialized,
customer-specified materials or processes which do not meet the requirements of EU 2002/95/EC
may negate RoHS compliance of the assembly. To guarantee compliance of the assembly, the need
for compliant product must be communicated to ZTE CORPORATION in written form.
This declaration is issued based on our current level of knowledge. Since conditions of use are
outside our control, ZTE CORPORATION makes no warranties, express or implied, and assumes no
liability in connection with the use of this information.
I
II
Chapter 1
Safety Precautions
Table of Contents
Overview ....................................................................................................................1-1
Safety Precautions .....................................................................................................1-1
Safety Symbol ............................................................................................................1-1
1.1 Overview
This chapter explains the safety precautions that operator should learn before equipment
maintenance.
1.2 Safety Precautions

This equipment involves high temperature and high voltages and can only be installed,
operated, and maintained by qualified personnel.
Observe the local safety codes and relevant operating procedures in equipment
installation, operation and maintenance; otherwise, personal injury or equipment damage
may be caused. The safety precautions introduced in this manual are only supplementary
to the local safety codes.
ZTE Corporation shall not be liable for any loss or damage arising from the failure to follow
general safe operation requirements or the safety standards for the design, production and
use of the equipment.
1.3 Safety Symbol

The safety prompt of warning is introduced in this manual. The statement for safety level is
on the right of the safety symbol. The detailed description is under this symbol, as shown
below.
Warning!
Indicates a potentially hazardous situation which, if not avoided, could result in death or
serious injury.
1-1
SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

ZXWN MSCS Routine Maintenance Guide
This page intentionally left blank.
1-2

Chapter 2
Overview of Routine
Maintenance
Table of Contents
Overview ....................................................................................................................2-1
Routine Maintenance Classification............................................................................2-1
Common Maintenance Methods .................................................................................2-2
Precautions on Routine Maintenance .........................................................................2-4
2.1 Overview
This chapter introduces the routine maintenance classification, common maintenance
methods and precautions of ZXWN MSCS.
2.2 Routine Maintenance Classification

Description
In terms of maintenance contents, the routine maintenance of ZXWN MSCS falls into
routine maintenance, notification/alarm message handling and common failure handling.
Contents
1. Routine maintenance
The routine maintenance is to periodically check the running status of the equipment,
so as to deal with any problem detected as soon as possible. In this way, you can
discover, prevent, and handle any potential trouble at an earlier stage.
Based on the period, maintenance can be classified into the following types.
l Daily routine maintenance
l Weekly routine maintenance
l Monthly routine maintenance
l Quarterly routine maintenance
l Yearly routine maintenance
2. Notification and alarm message handling
Notification and alarm message handling is to analyze different notification and alarm
messages during running of the system, judge the equipment running condition and
take appropriate measures.
2-1

3. Common failure handling

Common failure handling is a process of analyzing, handling and eliminating faults that
cannot be located and eliminated through a single alarm or notification message.
2.3 Common Maintenance Methods

Description
In the routine maintenance, a fault is analyzed and located through some methods. For
a hardware-related problem, we can observe the hardware indicators in conjunction with
substitution method, and comparison method, to judge whether the hardware is working
properly. For a problem related software or service, we use the maintenance tools in the
operation and maintenance system along with the system logs and data analysis, to find
the possible cause.
For problems arising in connection with actual operation, it might be impossible to
determine whether they result from the software or the hardware immediately. In this
case, several methods should be used together for flexible troubleshooting.
Contents
Common maintenance methods are as follows.
1. Analysis of fault symptoms
Generally speaking, network equipment consists of multiple entities, which differ in
symptoms in the case of a problem or fault. When finding a fault or receiving a report on
a fault, maintenance personnel may analyze the phenomena to judge what equipment
entity with a fault may lead to such phenomena, and then try to locate the equipment
entity with the fault.
This is particularly important in case of an emergency fault. Careful analysis of the
fault symptom and exact location of the faulty equipment entity are helpful to avoid
improper operations on the normal equipment entity and troubleshoot in the shortest
time.
2. Analysis of indicators status
To clearly mark the running status of the devices, most devices are equipment with
status indicators. For example, most boards in the foreground have RUN indicator to
indicate the running status of the equipment, ERROR indicator to indicate whether the
board is faulty, POWER indicator to indicate whether the power is powered up, and
flashing indicators that flashes when the board works normally.
The status indicators help analyze the faulty part and even the cause. Check
whether the foreground boards are running normally, whether normal active/standby
changeover is possible. The running status can be confirmed via the fault
management and board indicators. Any board that functions abnormally and is
confirmed as hardware damage must be replaced immediately. If there is no spare
board, please contact the local ZTE office and apply for repair. Keep the warranty
2-2

Chapter 2 Overview of Routine Maintenance
card and the quality guarantee for the equipment in good condition, so in case of
software and hardware failure, you may request technical support.
3. Analysis of alarm logs
ZXWN MSCS can record error messages in the running and important running
parameters. The error messages and important running parameters are recorded in
the log file of the foreground, log files of the background server (including version
application log and system log) and alarm database.
Analysis of the log files and the alarm database information enables maintenance
personnel to locate the exact cause of the fault, and uncover potential problems with
the system.
4. Fail Observer
Fail Observer is an important and practical tool for debugging, maintenance, and
observation. Users can observe the failures with ZXWN MSCS and causes in real
time through ZXWN MSCS Fail Observer window on the maintenance console, so
as to locate the faults with ease.
In case of failure, the cause can be analyzed through signaling trace tools and failure
observer tools. If you cannot locate the exact cause of the failure, please send the
failure record to the local ZTE office for further diagnosis.
In the actual usage, failure observer in case of heavy traffic will take up a large number
of resources. It is recommended to observe services in single-user mode. In addition,
the failure information should not be cleared immediately. Do not clear the traced
failure information before you find the failure cause.
5. Analysis through instrument and meter test
One of the most useful troubleshooting methods is using test instruments and meters
to measure the indices of system running and environment, and then comparing these
indices with those in normal conditions, to find the cause.
6. Comparison and replacement
It is helpful to replace a potentially damaged part with a normal one. If the problem is
settled after replacement, the fault can be located.
In addition, compare the status, parameters, log files, and configuration parameters
of the same part at different times or in different offices to check whether there is any
inconsistency. Perform a modification test at a safe time to eliminate the fault.
The comparison and replacement method is simple and practical. It plays an important
role in the troubleshooting process.
2-3

Note:
Generally, safe time refers to the period from 0:00 am to 6:00. The operations performed
during this period have less impact on the service.
2.4 Precautions on Routine Maintenance

1. Maintain normal temperature/humidity in the equipment room. Keep the environment
tidy and clean, free from dust and moisture. Keep rodents or insects out of the
equipment room.
2. Ensure that the primary power of the system is stable and reliable; and check the
system grounding and lightning ground periodically. In particular, check the lightning
protection system before and after the storm season, to make sure the facilities are in
good condition.
Danger!
Any check and adjustment involving the power part must be made by the professionals.
Otherwise, it may cause casualties and equipment fault.
3. Establish a complete set of maintenance regulations for the equipment room to

standardize the routine maintenance work. A detailed attendant's log should be
maintained to provide detailed records about system operation, version, data change,
upgrading and troubleshooting for analysis and handling after the fault is detected.
Keep a shift record to specify the responsibility clearly.
4. Do not play games or access the Internet via the computer terminal. Do not install,
run or copy other software unrelated to the system in the computer terminal. Do not
use the computer terminal for other purposes.
5. Set different NM passwords for different access rights, put them under strict
management and make changes to them periodically. Also, keep the NM password
only accessible to maintenance personnel.
6. Maintenance personnel should be trained before taking the post to learn some
knowledge about equipment maintenance and network. After training, they should
master the basis operation and maintenance methods and emergency handling skills.
During maintenance operations, they should follow the instructions described in the
relevant manuals of the ZXWN MSCS equipment. Before touching the equipment
hardware, they should wear an antistatic wrist strap to avoid accidents due to human
factors.
7. Do not reset the equipment, load or modify the data at will, and especially, do not
modify data in the NMS database. Back up the data before modification. Do tests and
system inspection after the data modification take effect. The backup data should not
2-4

Chapter 2 Overview of Routine Maintenance
be deleted until it is confirmed that the system is running normally in a certain period
of time (usually a week.) Prior to data modification, data backup should be made.
8. Before performing major operations (such as restoring backup data, transferring
all tables or changed tables with a lot of configuration data, changing over boards,
resetting system and loading version), its feasibility should be assessed carefully.
Only after the corresponding backup and emergency changeback measures are
ready, these major operations can be performed when the service is idle.
9. Do not perform global signaling trace or failure observation or other operations that
greatly impact the load on the foreground and background systems in the daytime.
10. Prepare frequently used tools and meters, such as screwdriver (straight head and
cross head), signaling tester, network cable pliers, multi-meter, AC power supply for
maintenance purpose, telephone line and network cables. Be sure to test and calibrate
the instruments and meters at regular intervals to ensure their accuracy.
11. Frequently check spare parts and components to ensure they are sufficient, intact and
free from being damped or mildewed. Keep them away from those faulty ones during
maintenance, clearly label them and make supplement in time when they are out of
stock.
12. The software and documentation for potential use during maintenance should be kept
at hand as required, so that they are obtainable when necessary.
13. Illumination in the equipment room should meet the requirements for maintenance.
After being damaged, light fittings should be repaired in time. Do not leave dead
lighting corners, which may cause inconvenience in maintenance.
14. Handle faults immediately when they occur. Contact ZTE Corporation at once for any
faults you cannot solve.
15. Put the telephone number and address of ZTE Corporation in a highlighted place to
make it known to all the maintenance personnel, so they can contact ZTE in time when
they need help. Remember to get the latest contact information.
2-5

2-6

Chapter 3
Routine Maintenance
Table of Contents
Overview ....................................................................................................................3-1
Introduction to Routine Maintenance ..........................................................................3-1
Daily Routine Maintenance.........................................................................................3-2
Weekly Routine Maintenance ...................................................................................3-15
Monthly Routine Maintenance ..................................................................................3-18
Quarterly Routine Maintenance ................................................................................3-21
Yearly Routine Maintenance .....................................................................................3-26
3.1 Overview
This chapter introduces the routine maintenance items of ZXWN MSCS.
3.2 Introduction to Routine Maintenance

Overview
Routine maintenance is a kind of preventive maintenance, which covers periodic check
and maintenance on the devices in the running so as to detect and handle the hidden faults
as earliest as possible, thus achieving the long-term reliable, safe, and stable running of
the system.
Categories
1. In terms of maintenance period, ZXWN MSCS routine maintenance can be divided
into daily routine maintenance and regular routine maintenance.
a. Daily routine maintenance refers to the maintenance operations that are
implemented by the common maintenance personnel every day, with relatively
simple maintenance process, such as equipment room environment check,
equipment room power supply check, equipment working status check, and the
billing system check.
b. Regular routine maintenance refers to the relatively complicated maintenance
operations implemented within a certain period. In most cases, it must be
implemented by the trained maintenance personnel, such as the server running
status check and remote maintenance software check.
In terms of the maintenance period, regular routine maintenance further divides
into:
3-1

l Weekly routine maintenance

l Monthly routine maintenance
l Quarterly routine maintenance
l Yearly routine maintenance
2. In terms of the maintenance contents, ZXWN MSCS routine maintenance divides into
environment, service, data, software and hardware maintenance.
As the actual conditions in different offices are not completely the same and the
deployed services are different, it is possible that one or more of the maintenance
items mentioned in the following text are not fully applicable. Routine maintenance
items can be customized by these offices depending on the actual situation with
reference to the following text.
Purposes
1. The purposes of the ZXWN MSCS daily routine maintenance include:
l Discovering the alarms given by the equipment or hidden trouble of faults in time,
adopting appropriate measures to handle and recover the fault so as to maintain
the healthy level of the equipment and reduce the equipment fault ratio.
l Finding and handling the abnormal phenomena appearing during the running of
the billing system and the CDR system in time, thus to avoid or reduce the cost
caused by the CDR loss.
l Grasping the running status of the equipment and network in real time, knowing
the running trend of the equipment or network, and improving the sudden-event
handling efficiency of the maintenance personnel.
2. The purposes of the ZXWN MSCS regular routine maintenance include:
l By maintaining the equipment regularly, making the equipment always remain in
good condition, and ensuring the safe, stable and reliable running of the system.
l Through such methods as regular check, backup, testing and cleaning, finding
hidden troubles, including the natural aging, function expiry and performance
deterioration during the running of the equipment in time. Handling these troubles
by adopting appropriate measures, to eliminate the hidden trouble and prevent the
accidents.
3.3 Daily Routine Maintenance

The daily routine maintenance items of ZXWN MSCS contain the following contents.
l Checking equipment room environment

l Checking power supply in the equipment room
l Checking the status of the CPU on a board
l Checking the working status of the equipment
l Checking office status of SS7 links
l Checking association link status
l Checking trunk circuit status
l Checking fault management system
3-2

Chapter 3 Routine Maintenance
l Checking Mc interface status

l Checking Mg/Mj interface status (apply for MGCF)
l Checking MGW registration status
l Analyzing performance statistics data (Daily Maintenance)
l Checking dual-homing working status
l Checking billing system
l Checking the running status of the foreground
l Checking the running status of the NMS system
3.3.1 Checking Equipment Room Environment

Abstract
Perform this procedure to check the environment of the equipment room to ensure that the
equipment in the equipment room is working at an appropriate temperature and humidity.
The appearance and interior of the cabinet, and the floor of equipment room should be
clean and neat, without obvious dust attached.
The criteria for checking the equipment-room environment are as follows.
l The air-conditioning equipment operates well.
l The temperature and humidity of the equipment room meet the requirements. The
requirements of the equipment on temperature and humidity are listed in the following
table.
Table 3-1 Requirements of ZXWN MSCS Equipment on Operational Environment
Parameter Name Indices
Long-term working condition (note 1) 5℃~40℃

Temperature
Short-term working condition (note 2) -5℃~50℃
Long-term working condition 5 %~85 %

Relative humidity (%)
Short-term working condition 5 %~90 %
• The temperature and humidity in the equipment room are measured at the spot that is 1.5 m
above the floor and 0.4 m in front of the equipment when there is no guard plates in front or rear
of the rack.
• The short-term working condition refers to no more than 96 successive hours and not more than
15 accumulative days every year.
l Dustproof conditions in the equipment room are sound. All things are clean and neat
without obvious dust attached, and the dustproof conditions are sound; otherwise, the
dustproof conditions are bad.
Steps
1. Check the running status of the air conditioners in the equipment room, and make
records. In case of any abnormality, replace or repair the faulty air conditioner as soon
as possible.
2. Check the reading on the thermometer in the equipment room.
3-3

3. Check the reading on the hygrometer in the equipment room.

4. Observe the case and the interior of the equipment, floor, and desk floor in the
equipment room.
– End of Steps –
3.3.2 Checking Power Supply in the Equipment Room

Abstract
This procedure checks the power supply in the equipment room to make sure that the
AC and DC power supply devices in the equipment room provide a voltage environment
required for normal operation.
The criteria for checking the equipment-room power supply are as follows.
l DC power supply
à Standard DC operating voltage: -48 V
à Permitted fluctuation range: -60 V to -40 V
l Operating AC voltage: 220 V ± 22 V, 50 Hz ± 2.5 Hz.
Steps
1. Check the power supply devices in the equipment room and the operating DC voltage
displayed, and make records.
2. Check the power supply devices in the equipment room and the operating AC voltage
displayed, and make records.
3.3.3 Checking Board CPU Status

Abstract
Perform this procedure to check the CPU occupancy of each board.
The criteria for checking the CPU status are as follows.

l The CPU occupancy of each module should not be greater than 60 %.
l The CPU occupancy of each module should be equal basically.
The processing procedure of exceptions is as follows.

l If the CPU occupancy of each module differs greatly, adjust the modules belonged by
trunk groups and links to make the CPU occupancy of each module even.
l If the CPU occupancy of each module exceeds 60 %, capacity expansion should be
considered.
3-4

Steps
1. In the MML Terminal window of the OMM Main Process client, select the office number
to be viewed.
2. Select one of the following methods to check the CPU occupancy.
l In the MML Commands tree, click Maintenance Management > Dynamic Man-
agement > Query Performance Statistic Index Timely > Show CPU Load, and
then click the Execute (F5) button..
l Run the SHOW CPULOAD command.
3.3.4 Checking Equipment Working Status

Abstract
Perform this procedure to check the running and connecting status of the boards and server
to make sure that the whole system works normally.
The criteria for checking the working status of the equipment are as follows.
l The board service status indicator (OOS) and the board health status indicator (OK)
are off. For the boards in active/standby mode, one of them should be in the active
status (the ACT indicator is on), and the other should be in the standby status (the
ACT indicator is off). The board hot swap indicator (H/S) is off. The HOST board
running/alarm indicator (HOST) flashes in green.
l In the Fault Management, there is no communication-link alarm. Each board works
normally without being in unknown status or abnormally active/standby status.
l There is no fan alarm, and the front panel of the board is at a normal temperature.
l The network management interface message processor can report data normally. The
network management center can collect the data normally.
The handling of abnormal cases is as follows.
l When active and standby boards are both in the active mode, or are observed to be
in active status in the OMM client, try to reset the standby board to handle this fault.
l If the active/standby board is in unknown or intermixed status, perform the
active/standby changeover twice at night with the minimum traffic.
l If the fault still cannot be handled, check whether the board hardware is damaged. If
it is, replace it immediately.
l If there is no spare board, please contact the local ZTE office and apply for repair.
l Keep the warranty card and the quality guarantee for the equipment in good condition,
so in case of software and hardware failure, you may request technical support.
Steps
1. Observe the status running indicators on the board.
The common working indicators on each board are listed in the following table.
3-5

Table 3-2 Indicators on Boards
Name Color Description
Service status indicator. It is on in green during power

Dual-color indicator
OOS on reset of the board and in red during power-on. It is
(red/green)
off in other moment.
Health status indicator. It flashes in red at 5 Hz when

Dual-color indicator the hardware address is wrong. It flashes in red at 1
OK
(red/green) Hz when the board generates an alarm. It flashes in
greed at 1 Hz when the board is normal.
Dual-color indicator Active/standby indicator: on for active, and off for

ACT
(red/green) standby.
H/S Blue Hot swap indicator. It is on when the board is offline.
Running/alarm indicator. The green indicator indicates

Dual-color indicator
HOST that the board is in the running status. The red light
(red/green)
indicates that the board has an alarm.
2. In the Fault Management window, check whether there are communication-link

alarms. In the rack equipment alarm diagram of the fault management, check whether
the active/standby status of each board is normally.
3. Check the alarm indicator of the fan, and observe the running condition of the fan. In
the OMM client, check whether there are alarms about the over-high temperature of
the board.
4. Check whether the operating systems of the terminals are infected with the viruses.
5. Check whether the OMM server/client works normally.
3.3.5 Checking Office Status of SS7 Links

Abstract
Perform this procedure to check whether the signaling links between local office and
other offices are normal, and whether the signaling interworking among adjacent offices
is normal.
The criteria for checking the office status of SS7 links are as follows.
l All the signaling links are in "Available" status.

l All the adjacent-office directions are in "Reachable" status.
Steps
1. Select one of the following method to check the signaling link status of the local office.
3-6

l In the MML Terminal window of the OMM Main Process client, select the required
office number. In the MML Commands tree, click Maintenance Management
> Dynamic Management > NO.7 Relative > Signaling Link > Show SMP
Signaling Link Status, and then click the Execute (F5) button.
l Run the SHOW SMPLNKSTAT command.
2. Select one of the following method to check the status of all the adjacent offices of the
local office.
office number. In the MML Commands tree, click Maintenance Management >
Dynamic Management > Show All Office Status, and then click the Execute
(F5) button.
l Run the SHOW ALLOFFICESTAT command.
3.3.6 Checking Association Link Status

Abstract
Perform this procedure to check whether the associations between the local office and
other offices are normal.
The criteria for checking the association links are as follows.
l All the association links are in normal status.
l All the ASPs are in “ACTIVE” status.
l All the ASs are in “ACTIVE” status.
l All the adjacent offices are in the "Signaling Point Reachable" status.
Steps
1. Select one of the following method to check the association link status of the local
office.
office number. In the MML Commands tree, click Maintenance Management >
Dynamic Management > SIGTRAN Relative > SCTP > Show SCTP Status,
and then click the Execute (F5) button.
l Run the SHOW SCTPSTAT command.
2. Select one of the following methods to check the ASP status.

l Click Maintenance Management > Dynamic Management > SIGTRAN
Relative > ASP > Show ASP Status, and then click the Execute (F5) button.
l Run the SHOW ASPSTAT command.
3. Select one of the following methods to check the AS status.

Relative > AS > Show AS Status, and then click the Execute (F5) button.
l Run the SHOW ASSTAT command.
3-7

4. Select one of the following method to check the status of all the adjacent offices of the
local office.
l Click Maintenance Management > Dynamic Management > Adjacent Office
> Show All Office Status, and then click the Execute (F5) button.
l Run the SHOW ALLOFFICESTAT command.
3.3.7 Checking Trunk Circuit Status

Abstract
Perform this procedure to check trunk circuits to find abnormal trunk circuits and eliminate
exceptions such as long time deadlock and block.
The criteria for checking the trunk circuits are as follows.

l The circuit number of both the circuit block and circuit fault in the circuit statistics of
trunk group is 0.
l No CIC circuit is in either "circuit block" or "circuit fault" status.

If the CIC circuit is blocked or with a hardware fault, execute the unblocking operation on
the circuit. If this problem still remains, check the corresponding board and transmission
line to convert the circuit status to idle.
Steps
1. Select one of the following methods to query the status of all trunk circuits configured
on the local office in turn.
l In the MML Terminal window of the OMM Main Process client, select the
office number as required. In the MML Commands tree, click Maintenance
Management > Dynamic Management > Trunk Circuit > CIC Circuit > Show
CIC Local Status, and then click the Execute (F5) button.
l Run the SHOW LCICSTAT command.
2. Select one of the following methods to check the statistics information about the trunk
group.
l Click Maintenance Management > Dynamic Management > Trunk Circuit >
Circuits Statistics > Show Trunk Group Circuit Statistics, and then click the
Execute (F5) button.
l Run the SHOW TGSTAT command.
3. Select one of the following methods, and then enter trunk group, PCM system and
circuit numbers to check the CIC status of the corresponding BSC circuit group.
l Click Maintenance Management > Dynamic Management > Trunk Circuit >
BSC Circuit > Show BSC Circuit Status, and then click the Execute (F5) button.
l Run the SHOW BSCSTAT command.
3-8

Based on this method, check the status of all the BSC trunk groups.
3.3.8 Checking Fault Management System

Abstract
Perform this procedure to check the current and history alarms in the fault management
system, thus detecting the potential fault. Perform this procedure to check the alarm box,
thus making sure that alarms can be reported normally.
The criteria for checking the fault management system are as follows.
l If there is current alarm without be acknowledged, maintenance personnel should
analyze and handle it at once. For the acknowledged alarm that possibly will affect
the normal running of the system, maintenance personnel also should handle it as
soon as possible.
l If there is a history alarm, maintenance personnel should analyze and acknowledge
its generation and recovery causes to avoid existing fault and possible hidden trouble
of the system.
l It is not recommended to set alarm filtering rules. Even if it is truly necessary, it has
no effect on the running of the system.
l Check whether the RUN indicator on the alarm box flashes normally, whether the
alarms of various levels indicated by the alarm indicator are consistent with those
shown in the fault management, and whether the acknowledged alarms are not shown
on the alarm box.
Steps
1. In the Fault Management window of the OMM Main Process client, check whether
the current alarms are displayed on the Current Alarm tab page. If they are,
analyze, handle and confirm these alarms based on their types, generating locations,
descriptions and severity.
2. In the Fault Management window, query history alarms with the condition of “all
alarms”, and specify the period from the time of the last history alarm query to the
current time.
3. Check the alarm filtering rules set in the Fault Management window.
4. Check the RUN and ALM indicators on the alarm box, and compare the alarm level
displayed on the alarm box with that displayed in the fault management system.
3-9

3.3.9 Checking Mc Interface Status

Abstract
Perform this procedure to check the status of the Mc interface, thus ensuring that the
link between MSCS and MGW is normal, and that the MGW can register on the MSCS
normally.
The criteria for checking the Mc interface status are as follows.
l All the active SCTPs are in "Established" status except the dual-homing heartbeat
association.
l All the ASPs are in “Active” status.
l All the ASs are in “Active” status.
l If the SCTP works abnormally, check whether the network cables are connected
properly, whether the bearer network functions well, and whether the SIPI interface
board functions well.
l If the ASP is abnormal, execute the ASP UP and ASP ACTIVE commands to activate
the ASP again.
Steps
1. In the MML Terminal window of the OMM Main Process client, select the required
office number.
2. Select one of the following methods to check the status of the association to the MGW.
l In the MML Commands tree, click Maintenance Management > Dynamic
Management > SIGTRAN Relative > SCTP > Show SCTP Status, and then
click the Execute (F5) button.
l Run the SHOW SCTPSTAT command.
3. Select one of the following methods to check the status of the AS to the MGW.
Relative > AS > Show AS Status, and then click the Execute (F5) button.
l Run the SHOW ASSTAT command.
4. Select one of the following methods to check the status of the ASP of the H.248 bearer
to the MGW.
Relative > ASP > Show ASP Status, and then click the Execute (F5) button.
l Run the SHOW ASPSTAT command.
3-10

3.3.10 Checking Mg/Mj Interface Status (apply for MGCF)

Abstract
Mg/Mj interface is the interface between MGCF and CSCF/BGCF in the IMS domain, and
it uses the SIP protocol.
The criteria for checking the Mg/Mj interface status are as follows.
l SIP links are “Normal”status.
l The office direction from MGCF to CSCF/BGCF is reachable.
Steps
1. Check the status of the SIP link to see whether it is normal.
In the MML Terminal window of the OMM Main Process client, select the
required office number. Select the menu Maintenance Management > Dynamic
Management > SIP > Show SIP Link Status, and then click the Execute (F5) button
or execute the command SHOW SIPLNKSTAT.
2. Check the hardware connection.
If the status of the SIP signaling link is not normal, check whether the physical
connection and the network cable connection between MGCF and CSCF/BGCF is
correct. If the physical connection is normal, the Link1 indicator on the SIPI board
should be ON.
3. Debug the IP protocol stack.
When the physical connection is correct, Select the required office number under
the MML Terminal window. Select the menu Protocol Configuration > IP Stack
Configuration > IP Stack Tools > PING, input the peer-end IP address and then
click the command Execute (F5). If the ping operation is successful, it means that
the IP protocol stack is normal. Otherwise, check the IP link configuration with the
command SHOW TCPCONN.
4. Check the UDP bearer configuration.
In the MML Terminal window of the OMM Main Process client, Select the required
office number. Check the configuration of the local address, the local port, the peer
address and the peer port with the command SHOW UDPBR.
5. Check the SIP link configuration.
In the MML Terminal window of the OMM Main Process client, Select the required
office number . Check the SIP link configuration with the command SHOW SIPLNK.
3-11

3.3.11 Checking MGW Registration Status

Abstract
Perform this procedure to check whether the registration status of the MGW is normal.
The criterion for checking the MGW registration status is that the gateway should be in
normal operational status. Normally, the in service message should be returned on
the NMS system.
l Check physical boards, physical connections, SCTP associations, ASP, and AS to
see whether they are normal.
l Check the application type of signaling points and H.248 data configuration on the
MGW and MSCS to see whether they are correct.
Steps
1. In the MML Terminal window of the OMM Main Process client, select the office number
to be viewed.
2. Select one of the following methods to check the registration status of the MGW.
l In the MML Commands tree, click Maintenance Management > Dynamic
Management > H248S > Show MGW State.
l Run the SHOW MGWSTAT command.
3. Check whether there are alarms in the OMM Main Process client.
3.3.12 Analyzing Performance Statistics Data (Daily Maintenance)

Abstract
It is necessary to check and analyze the KPI every day. In addition, set the performance
threshold to each KPI. After the index is lower than its threshold, the system will
automatically alarm, thus to monitor the system KPI.
Perform this procedure to analyze the performance statistics data of the system in a day,
and check the service load conditions and equipment operational indices so as to eliminate
the hidden troubles of the equipment.
The inspection criteria for the performance statistics data is listed in the following table.
Table 3-3 Checking Criteria for Performance Statistics
Items Reference Standards
KPI index: call completion rate, Compared with the same period of last week, the index does
paging success rate, and answer not decrease significantly. Meanwhile, this index meets the
bid ratio requirements of carriers.
3-12

Items Reference Standards
Traffic statistics It includes traffic and office traffic index. Compared with the
same period of last week, these indices do not decrease
significantly.
Trunk load statistics The load of each trunk group should be less than 0.7 erl;
otherwise, capacity expansion is necessary.
The ratio of available trunks of each trunk group is 100%;

otherwise, the cause of unavailable trunk should be analyzed.
Signaling load statistics The load of ISUP signaling links should be less than 0.4 erl;
The load of MAP signaling links should be less than 0.2 erl;
CPU occupancy The average CPU occupancy ration should not exceed 60%;
otherwise, its cause should be analyzed, or capacity expansion
is necessary.
VLR occupancy The subscriber capacity of the VLR should not exceed 90% of its
total capacity; otherwise, expanding VLR capacity is necessary.
Steps
1. Open the Performance Management window of the OMM Main Process client to
query the performance statistics data.
2. Analyze the result of performance statistics.
3.3.13 Checking Dual-Homing Working Status

Abstract
Perform this procedure to check the dual-homing working status of the MSCS with the
dual-homing function to know whether the heartbeat line between the active and standby
MSCSs is normal, thus making sure that the standby MSCS can take over the services
immediately when the active MSCS breaks down.
The inspection criteria for the dual-homing working status are as follows.
Both the home terminal and the opposite-end terminal work in active and standby mode,
and the heartbeat status is normal.
Steps
1. In the MML Terminal window of the OMM Main Process client, select one of the
following methods to check the dual-homing working status.
3-13

l In the MML Commands tree, click Advance Configuration >

Disaster-Tolerance Management > Dual Home Maintenance > Show Dual
Home Status, and then click the Execution (F5) button.
l Run the SHOW DHSTATE command.
3.3.14 Checking Billing System

Abstract
Perform this procedure to check whether the billing system runs properly, thus making sure
that the billing data can be generated and transmitted properly.
The criteria for checking the billing system are as follows.
l SPU is in working status.

l CDRs can be generated properly according to the CDR generating condition
configured in the billing configuration.
l The billing center fetches the CDR files periodically, without expired files.
l Billing backup is done properly, and backup tasks are completed according to the
settings.
Steps
1. In the ZXWN Billing System SPU Monitor Manage window of the local maintenance
tool, right-click SPU, and select Query SPU Status from the shortcut menu to check
the SPU running status.
2. In the ZXWN Billing System CDR Manager window of the local maintenance tool,
check the CDR files periodically generated in the Normal CDR directory.
check whether the CDR files in the Remote CDR directory are fetched by the billing
center periodically.
4. According to the used billing backup mode, check whether the CDR backup is done
properly.
3.3.15 Checking the Running Status of the Foreground

Abstract
The criteria for checking the running status of the foreground are as follows.
l The OOS indicator on each board is off.
l The OK indicator on each board flashes in green.
l Active and standby indicators flash properly.
3-14

Steps
1. Check the running and active/standby statuses of each board through NE > Rack
Chart Managemnet tab page of the OMM Daily Maintenance client.
3.3.16 Checking the Running Status of the NMS System

Abstract
The criteria for checking the running status of the NMS system are as follows.
l No alarm about CPU, hard disk, network card or other hardware occurs.
l The NetNumen network management process of the OMM server is started. The
OMM client software on the OMM client is started. The interconnection programs of
upper NMS run properly, such as middle database and CORBA.
l The icon of every network card (except standby network cards) should be in normal
status.
l Both the data backup directory and time are correct, and the backup files are normal.
l There is no major operation record when the equipment operates normally.
Steps
1. Check the hardware running status of the OMM clients.
On the desk of the OMM client, select Start > Programs > Administrative Tools >
Event Viewer to open the Event Viewer dialog box. View the system logs.
2. Check the running status of the OMM server and clients, and the interconnection
programs of upper NM station, such as middle database and CORBA.
On the desk of the OMM server, check whether the NetNumen network management
process is started, whether the network management client software on the OMM
client runs properly, and whether the interconnection programs of upper network
management station run normally, such as middle database and CORBA.
3. Check the communication status of the OMM server and client equipment.
On the desk of the OMM client, right-click the My Network Places icon, select
Properties from the shortcut menu. The Network Connections dialog box pops up.
Check the connection status of every network card.
4. Check whether the network management configuration data and performance data file
backup are normal.
5. Check the operation logs of the network management.
3.4 Weekly Routine Maintenance

The weekly routine maintenance items of ZXWN MSCS contain the following contents.
3-15

l Checking the Running Status of the Server

l Backing up configuration data in NMS mode
l Analyzing Performance Statistics Data (Weekly Maintenance)
3.4.1 Checking the Running Status of the Server

Abstract
Perform this procedure to check the running status of the OMM server and the billing server
system, thus preventing any exception from occurring in the server operating system and
ensuring the proper running of the operation and maintenance system.
The criteria for checking the running status of the OMM server are as follows.
l The authority settings of different users are reasonable without any illegal user.
l The password of administrator is changed periodically without expired account.
l There is no totally shared directory or unrelated shared directory. Prevent virus
attacks.
l Check the status of the OSS/OK/HOST indicator on the server to make sure that no
alarm or power failure or other exceptions occurs.
l Check the system partition of the OMM server, and the partitions where the ORACLE
database and network management software are installed. For those with free space
less than 20 %, clean the disk and delete irrelevant files.
l Check the billing server disk and the billing-related file system, such as /global/b
ill. For those with free space less than 20%, clean the disk or expand the storage
space.
Steps
1. Check whether there is exceptional execution printout displayed in the interface on the
OMM server when the network management system is running.
2. Check the authority setting and the password validity period of the login user of the
OMM server.
3. Check the free space of the hardware disks and disk arrays on all equipment.
Meanwhile, on the NetNumen window of the OMM Main Process client, select Views
> System Management. Configure the server performance monitor to report alarms
in case of disk space exceeding the threshold.
4. Check the status of the OSS/OK/HOST indicator on the OMM server.
3-16

3.4.2 Backing up Configuration Data in NMS Mode

Abstract
This section describes the procedure of the configuration data backup of the system, thus
ensuring that the office data can be recovered in time in case of anything abnormal with
the system.
The criteria for configuration data backup are as follows.
l In case of any modification in data on the very day, relevant backup should be
available. In addition, the backup data are saved before and after modification.
l In case of no modification in configuration data recently, they should be backed up
weekly.
l The backup data are saved in at least two different places.
Configuration data backup in NMS mode means backing up configuration data through the
MML Terminal subsystem of the NMS software.
Steps
1. Open the MML Terminal window of the OMM Main Process client .In the configuration
resource tree , select the NE requiring backup.
2. In the MML Commands tree, click Data Maintenance > Backup and Restore Data
> Backup and Restore Configuration Data > Backup Data. The parameter input
area of the BAK command is displayed in the right pane, as shown in the following
figure.
Figure 3-1 BAK Command
3. Configure File Name, File Path, and Content of Backup, and then click the
Execution (F5) button. Wait for the appearance of the export success prompt. The
elapsed time of an export process is related with the data volume.
4. It is recommended to write descriptions based on the content of the saved data.
For example:
Name Office Number Office Type
2011_02_06_11.zip 11 MSCS
3-17

3.4.3 Analyzing Performance Statistics Data (Weekly Maintenance)

Abstract
Perform this procedure to analyze the performance statistics data of the system in a week,
thus knowing the load conditions and service indices in a week. Analyze abnormal indices
in depth so as to eliminate the hidden troubles of the system.
The criterion for checking the performance statistics data is that compared with the
performance statistical data last week, there are no abnormal performance data.
l In case of great difference between the statistical data this week and last week,
consider the traffic features, changes to the configuration data, alarm information
and other causes this week. And analyze the cause of the statistical data difference.
If the cause is rational, no handling is required. If it is an equipment alarm, handle
it as soon as possible.
l If the CPU and the memory occupation rates of the MP of the GPBA0 board exceed
60%, analyze the cause and give the corresponding solutions. If the board itself is
faulty, contact the local ZTE office to replace it. If the services cause heavy load,
perform flow restriction after objective analysis on the services.
Steps
1. Analyze indices such as the call completion ratio, paging success ratio, traffic, BHCA,
and handover success ratio, which should fluctuate in the normal range, and the load
of each module should be balanced.
2. Check whether the each line traffic, each link load, and the CPU load on each module
of each office fluctuate in the normal range.
3. Analyze the change trend of the number of subscribers registered on the VLR, and
explain it rationally.
3.5 Monthly Routine Maintenance

The monthly routine maintenance items of ZXWN MSCS contain the following contents.
l Analyzing performance statistics data (Monthly Maintenance)

l Checking performance statistics tasks
l Performing data backup
l Checking Billing Files
3-18

3.5.1 Analyzing Performance Statistics Data (Monthly Maintenance)

Abstract
Perform this procedure to analyze the system running status this month and the exceptions
in the statistics results to eliminate the equipment faults, and to analyze the subscriber
actions so as to give solutions as far as possible.
The criterion for checking the performance statistics data is that there is no exceptional
change to all the statistics data.
When the statistics data are abnormal, analyze the cause and handle the problem. If the
measurement task is or will be expired, configure it again.
Steps
1. Analyze indices such as the call completion ratio, paging success ratio, traffic, BHCA,
and handover success ratio, which should fluctuate in the normal range and the load
on all the modules should be balanced.
2. Check the traffic of every line, the load of every link, and the CPU load on all the
modules of each office fluctuate in the normal range.
3. Analyze the change trend of the number of subscribers registered on the VLR, and
explain it rationally.
3.5.2 Checking Performance Statistics Tasks

Abstract
Perform this procedure to check the creation of the statistics tasks to make sure the
statistics tasks are complete and the analysis data are available whenever there is need
for data analysis.
The criteria for checking the performance statistics task are as follows.
l The key tasks should have been created, including the resource occupancy of
ZXWN MSCS, basic traffic, office direction, circuit group and NO.7 signaling system.
Office directions, No.7 office directions, circuit groups and No.7 links are configured
completely.
l No task has expired. Generally, the lifetime of a task is set for 2~4 years.
l Tasks should be set rationally, especially the statistic granularity and statistic time
period. They can be determined according to the requirements of the carrier.
When the test results show abnormal, analyze the cause and handle the problem.
3-19

Steps
1. Check whether the performance statistics tasks are created for ZXWN MSCS and the
logical function configuration.
2. Check whether the tasks have expired or are about to expire.
3. Check whether the tasks are reasonable.
3.5.3 Performing Data Backup

Abstract
Perform this procedure to back up the network management data, including the backups
of history alarm records, performance statistical data and operation and maintenance logs.
The criterion for data backup is that all the data backups are complete successfully.
In case of abnormal data backup, analyze the cause and handle the problem.
Steps
1. Back up history alarm records.
i. The system will automatically clear the history alarm records when the time for
clearing these logs is expired (generally three months). Maintenance personnel
should back up the alarm records periodically, which may help troubleshooting and
learn about the network running conditions.
ii. It is suggested to back up the alarm record database monthly.
iii. Analyze the history alarms to detect and eliminate faults and hidden troubles in
time.
2. Back up the performance statistics data.
i. The system will automatically clear the history performance statistics data when
the system-specified time for clearing these data is expired (generally three
months). Maintenance personnel should back up these data periodically, which
may help troubleshooting and learn about the network running conditions.
ii. It is suggested to back up the performance statistics database monthly.
3. Back up the operation and maintenance logs.

The network management log files are stored in the server, and you may view these
logs from a terminal connected to this server. Authorized operators are allowed to
query, and back up the logs. However, the log database is not unlimited. When the
system-specified time for clearing a log database is expired (generally three months),
the system will automatically clear log files.
3-20

It is suggested to back up the operation and maintenance logs monthly. The backup
files are named by date.
3.5.4 Checking Billing Files

Abstract
Perform this procedure to randomly check the billing files generated this month to
ensure that the single billing file is correct and that the entire billing files do not fluctuate
exceptionally.
The criteria for checking the billing files are as follows.
l The Normal CDR directory contains no CDRs in abnormal size and the CDRs have
continuous serial numbers without broken number.
l The Abnormal CDR directory contains no exceptional CDRs.
Contact the local ZTE office.
Steps
1. In the ZXWN Billing System SPU Monitor Manage window of the local maintenance
tool, right-click SPU, and select Query SPU Status from the shortcut menu to check
the SPU running status.
check the CDR files generated in the Normal CDR directory. Check whether the CDR
serial number is continuous, and whether the bytes of all the CDRs are normal.
check whether there are CDR files in the Abnormal CDR directory.
4. Decode the CDR files. Check several CDR records at random.

3.6 Quarterly Routine Maintenance

The quarterly routine maintenance items of ZXWN MSCS contain the following contents.
l Checking system time

l Checking the remote control tool
l Checking operating system logs
l Checking database logs
3-21

3.6.1 Checking System Time

Abstract
Perform this procedure to check the time of each module and SNTP server time in the
system to ensure the time accuracy.
The criteria for checking the system time are as follows.
l The foreground OMP module time, OMM server time, and OMM client time keep high
accuracy with an error less than five seconds. If they are not, adjust their time when
the service is idle after obtaining approval of the person in charge. The adjustment
range is not more than 30 seconds every time.
l The settings of the SNTP server are correct.
Steps
1. Check the time of foreground OMP module through the Clock Management module
of the local maintenance tool.
2. On the OMM client, check the time and time zone settings of the Windows operating
system.
3. On the OMM Main Process client, select System > Query System Time, or click the
button on the toolbar to view the system time.
The interface shown in the following figure pops up.
Figure 3-2 Viewing System Time
following methods to check the time zone setting of the local office.
3-22

l In the MML Commands tree, click Device Configuration > Device Parameter
Configuration > NE Global Parameter Configuration > Show Global
Configuration Time Zone Information, and then click Execute (F5) button.
l Run the SHOW TZ command.
following methods to check the SNTP server setting of the local office.
l In the MML Commands tree, click Device Configuration > Device Parameter
Configuration > NE Global Parameter Configuration > Show SNTP Server
Address, and then click Execute (F5) button.
l Run the SHOW SNTP command.
3.6.2 Checking the Remote Control Tool

Abstract
This procedure describes how to check the installation and the usage of the remote control
tool (such as the vncviewer software) so that the ZTE engineer can check the running of
the device remotely and support the remote technical support.
The standard is as follows:
The connection of the remote control tool is normal.
Steps
1. Check whether the remote desktop is enabled by the OMM server.
The details are as follows:
i. Select System > Preferences > Remote Desktop to open the Remote Desktop
Preferences dialog box, as shown in Figure 3-3.
3-23

Figure 3-3 Preference of the Remote Desktop
ii. In the window as shown in Figure 3-3, select the checkbox Allow other users
to view your desktop and the checkbox Allow other users to control your
desktop. It is also allowed to select the checkbox Require the user to enter this
password and then type the password. This password is the login password for
vncviewer.
iii. After that, click the Close button to close the window.
2. On the client where the vncviewer software is installed, check whether the vncviewer
can log in to the OMM server normally.
The details are as follows:
i. Double-click the software vncviewer to open the page as shown in Figure 3-4.
Figure 3-4 Login Window
ii. Type the IP address of the OMM server in the text box VNC server and then click
the OK button. If the password is set in the Remote Desktop Preferences dialog
box of the OMM server, the dialog box as shown in Figure 3-5 pops up. Input the
3-24

password and then click the OK button. Otherwise, log in to the main window of
the OMM server directly.
Figure 3-5 Password
3. Check whether the maintainer of the equipment room and the related director are
skilled in the remote control tool.
3.6.3 Checking Operating System Logs

Abstract
The criteria for checking the operating system logs are as follows.
l In the case of application logs, there are no failure events.
l In the case of security logs, there is no such events as illegal access.
l In the case of system logs, there is no such errors as the system driver error affecting
the system. For example, there is no record that the network card or hard disk is
abnormal.
Steps
1. In the OMM clientselect Start > Programs > Administrative Tools > Event Viewer.
Check the Application, Security, and System logs that are generated recently.
Specially check the warning and error logs.
3.6.4 Checking Database Logs

Abstract
The criterion for checking the database logs is as follows.
There is no error starting from "ORA-" in the Oracle log file (\oracle\admin\orcl\bd
ump\alert_sid.log, where sid is the name of actual database instance). Otherwise,
contact ZTE Corporation for handling.
Steps
1. In the installation directory of Oracle, check all the log files in the \oracle\product
\10gR2\network\log folder.
3-25

2. In the installation directory of Oracle, check the alert_sid.log log file in the \o
racle\admin\orcl\bdump folder, where sid is the name of the actual database
instance.
For example, if the SID name is set to orcl during the installation of Oracle database,
the directory in this case is \oracle\admin\orcl\bdump.
3.7 Yearly Routine Maintenance

The yearly routine maintenance items of ZXWN MSCS contain the following contents.
l Changing over the important boards
l Testing dual-server changeover on billing server
l Testing dual-homing disaster recovery changeover
l Cleaning equipment
l Checking ground resistance
3.7.1 Performing Changeover on the Important Boards

Abstract
Perform this procedure to do the changeover test on the important boards such as
GPBA0,GPBB0,SWBB0so as to find the hidden operation troubles of the hardware board
in time and handle them.
The criteria for checking the active/standby changeover function of boards are as follows.
After changeover, services, alarms, the performance statistics data, and CDRs are all
normal.
If the faulty board is found during the changeover test, handle it as soon as possible to
eliminate the hidden hardware troubles.
Caution!
The active/standby changeover should be performed in the time period with low traffic,
such as after 00:00 at night. Before changeover, maintenance personnel should submit
the application to the person in charge for approval. In addition, data backup are required
before changeover. During the changeover, maintenance personnel should make sure that
the NM end system and its hardware are in normal operation, as well as the connection
of loading cables and data backup. Do not frequently change over boards. The interval
between twice changeover should not be less than 30 minutes.
3-26

Steps
1. On the OMM Daily Maintenance client, select NE and open the Rack Chart
Management tab page. Right-click the active board, and select Show CPU from the
shortcut menu.
2. In the CPU list, right-click the CPU to be changed over, and select Normal
Changeover from the shortcut menu.
Caution!
Board changeover is performed with the CPU as unit. For a board with multiple CPUs,
input the total number of its CPUs on the configuration interface to complete the whole
board changeover.
3. After changeover, check whether CS services, billing CDRs, and signaling system
function well.
4. After the test, change back the board in the same way.
5. After change back, check whether CS services and CDRs are normal.
3.7.2 Testing Dual-Server Changeover on Billing Server

Abstract
Perform this procedure to check whether the active/standby billing dual-server system are
proper, and whether they properly communicate with the foreground MP.
The criteria for testing the dual-server changeover on the billing server are as follows.
l Changeover can be performed. The dual-server resource management program
shows that the active/standby status of the dual-server system is normal and the
services can be taken over between the dual servers properly.
l The active server communicates with the foreground MP properly. No CDR is lost.
Caution!
such as after 00:00 at night. Before changeover, maintenance personnel must submit the
application to the person in charge for approval. In addition, the data must be backed
up before changeover. Before changeover, make sure that the NM end system and its
hardware are in proper operation, as well as the data backup. Do not frequently change
over boards. The interval between twice changeover should not be less than 30 minutes.
3-27

Steps
1. Check whether the configuration files and operation files of the standby and active
server are consistent.
2. Perform the dual-server changeover through the dual-server resource management
program.
3. Observe 30 minutes of CDRs, and then test and analyze them.
4. In case of normal test result, restart the standby server, and observe whether the
server gets started normally.
5. Change back to the previous active server.
3.7.3 Testing Dual-Homing Disaster Recovery Changeover

Abstract
The criteria for checking the dual-homing disaster recovery changeover are as follows.
After changeover, services, alarms, the performance statistics data, and CDRs are all
normal. After the test, change back to the previous active MSCS.
Caution!
such as after 00:00 at night. Before changeover, maintenance personnel should submit
the application to the person in charge for approval. In addition, data backup and dump are
required before changeover. Before changeover, make sure that the NM end system and
its hardware are in proper operation, as well as the connection of loading cables and data
backup. Do not frequently change over boards. The interval between twice changeover
should not be less than 30 minutes.
Steps
1. On the OMM Main Process client, select Views > Professional Maintenance > MSCS
> Dual Home Management > Dual Home Changeover to open the Dual Home
Changeover tab page.
2. On the Dual Home Changeover tab page, click Changeover to open the
Changeover tab page.
3. Select a changeover mode as required. Click Execute. The process information and
results of the changeover are displayed on the Output Information Board tab page.
3-28

3.7.4 Cleaning Equipment

Abstract
Perform this procedure to clear the dust attached to the equipment to avoid the circuit
malfunction resulting from thick dust and to reduce the faults caused by the environment
factors.
The criterion is that the equipment is clean and free of dust.
Caution!
Exercise extreme caution when removing dust from the equipment. Remove dust from
racks, boards and servers when they are offline. Do not affect the proper running of the
system.
Steps
1. Remove dust from racks
Wipe the rack surface with a clean duster or cotton cloth, including the top and bottom
of the rack.
2. Remove dust from shelves
Wipe the surface of the shelf that has been replaced with a clean cotton cloth.
3. Remove dust from boards.
Remove dust from the boards that have been replaced with tools such as a clean
cotton cloth, antistatic banister brush, or vacuum cleaner.
4. Remove dust from servers
After powering off the server, remove dust from the circuit boards in the server with
tools such as a clean cotton cloth, antistatic banister brush, or vacuum cleaner.
3.7.5 Checking Ground Resistance

Abstract
Perform this procedure to make sure that the ground resistance is in the normal range.
The criteria for checking the ground resistance are as follows.
The ground resistance of the equipment room is less than 1 Ω. If condition permits, the
protective grounding wire can be connected to the earth through an independent grounding
pole.
3-29

If the ground resistance is too high, it is necessary to arrange the grounding bar again. If
condition permits, the protective grounding wire can be connected to the earth through an
independent grounding pole.
Steps
1. Measure the ground resistance of the equipment room.
3-30

Appendix A
Reference Table for
Maintenance
It is recommended to extract the System Networking Diagram from the engineering
documents. In addition to basic networking information of the equipment is the current
office, this system networking diagram should indicate the maintenance information,
including name, telephone number, attendants, and actual installation of the equipment
room.
Table A-1 Reference Table for Maintenance
Equipment Room Name: Tel: Attendant:
System Networking Diagram:
A-1

A-2

Appendix B
Common Maintenance Table
Table B-1 On-Duty Report of ZXWN MSCS
Duty Time: From to Previous shift Next shift
What to Do for the 1: Check the equipment room environment, including the running state of the air-conditioner,
Shift temperature, humidity and dustproof status in the equipment room.
□ Normal □ Abnormal
Abnormal symptoms:
2. Check the DC voltage, including power equipment and the DC working voltage displayed.
The standard value of DC working voltage is -48 V, and the allowed range is –57 V ~ -40 V.
Abnormal symptoms:
3. Check the AC voltage, including power supply equipment and the AC working voltage
displayed, which is 220 V ± 22 V and 50 Hz ± 2.5 Hz.
Abnormal symptoms:
4. Check the working status of board CPU: Check whether the CPU occupancy is normal, and
whether the CPU occupancy of all boards is basically balanced.
Abnormal symptoms:
5. Check the working status of the equipment: Observe the RUN indicator on the board to
make sure that the board hardware functions properly.
Abnormal symptoms:
6. Check the SS7 link load: Go to the performance statistics system, to query the statistical
data of SS7 link. Make sure that the link load is normal.
Abnormal symptoms:
B-1

7. Check the status of association links: Enter the Dynamic Management tab of the MML
Terminal window. Make sure that all the association links function properly, and all the office
directions are accessible.
Abnormal symptoms:
8. Check the status of the trunk circuits to see whether the trunk circuits of all the offices
are idle.
Abnormal symptoms:
9. Check current alarms: On the OMM client, start the Fault Management system, and query
whether there are current alarms displayed on the Realtime Current Alarms tab.
Abnormal symptoms:
10. Check history alarms: On the OMM client, start the fault management system, and query
whether there are history alarms displayed on the Realtime History Alarms tab tab. Select
all the modules and all the alarm levels. Specify the time period from 0:00 of the previous day
to the current time.
Abnormal symptoms:
11. Check the status of the Mc interface. Enter the Maintenance Management > Dynamic
Management tab of the MML Terminal window. Check whether the associations and ASP
are normal.
Abnormal symptoms:
12. Check the registration status of the MGW. Normally, the MGW is in service.
Abnormal symptoms:
13. Check performance statistical indices: On the OMM client, enter the performance
management system and check the performance statistical data.
Abnormal symptoms:
14. Check the real-time antivirus monitoring system of each terminal to make sure that there
is no virus infection alarm given by this system.
Abnormal symptoms:
B-2

Appendix B Common Maintenance Table
15. Check the basic data configuration backup: Check whether the current configuration data
are backed up in the backup directory. If they are not, back up them.
Abnormal symptoms:
16. Check the generation of the CDR files: Check the generation of the CDR files under the
directory where the CDR files of the ZXWN CG billing server are saved.
Abnormal symptoms:
17. Check CDR backup: Check whether the CDR files of the previous day have been backed
up. Check whether the CDRs backed up in the normal CDR directory have been automatically
deleted and whether only the CDR files generated within the specified number of days are
reserved. Check whether the tapes and MO disks are full and whether there are related
alarms. Replace them if necessary. Check whether the CDR files under the remote access
directory are extracted by the billing center. Check the space available in the disk array
file system.
Abnormal symptoms:
18. Check the communication between the billing server and the foreground: Ping the IP
address of the foreground modules from the billing server to see whether the communication
between the billing server and foreground modules are normal.
Abnormal symptoms:
19. Check log information: Open the O&M log system to query the required operation log.
Abnormal symptoms:
20. Check basic services: Use the mobile terminal to perform the call-related operations to
make sure whether the services are normal.
Abnormal symptoms:
21. Check the alarm box: Check the RUN and ALM indicators on the alarm box, and compare
the alarm level displayed on the alarm box with that displayed in the fault management system.
Abnormal symptoms:
B-3

Equipment room 1. Temperature

environment
2. Humidity
3: Dustproof:
Duty Description Troubleshooting:
Unsolved problems:
Double-checked by shift leader:
B-4

Figures
Figure 3-1 BAK Command ...................................................................................... 3-17
Figure 3-2 Viewing System Time............................................................................. 3-22
Figure 3-3 Preference of the Remote Desktop ........................................................ 3-24
Figure 3-4 Login Window ........................................................................................ 3-24
Figure 3-5 Password............................................................................................... 3-25
I
Figures

Tables
Table 3-1 Requirements of ZXWN MSCS Equipment on Operational
Environment............................................................................................. 3-3
Table 3-2 Indicators on Boards.................................................................................. 3-6
Table 3-3 Checking Criteria for Performance Statistics............................................ 3-12
Table A-1 Reference Table for Maintenance..............................................................A-1
Table B-1 On-Duty Report of ZXWN MSCS ..............................................................B-1
III
Tables

Glossary
AS
- Application Server
ASP
- Application Server Process
BGCF
- Breakout Gateway Control Function
BSC
- Base Station Controller
CIC
- Circuit Identification Code
CORBA
- Common Object Request Broker Architecture
CPU
- Central Processing Unit
CSCF
- Call Session Control Function
IMS
- IP Multimedia Subsystem
ISUP
- ISDN User Part
KPI
- Key Performance Indicator
MAP
- Mobile Application Part
MGCF
- MediaGateway Control Function
MGW
- Media GateWay
MSCS
- Mobile Switching Center Server
NMS
- Network Management System
PCM
- Pulse Code Modulation
V
SCTP
- Stream Control Transmission Protocol
SIP
- Session Initiation Protocol
SIPI
- Signaling IP bearer Interface
SNTP
- Simple Network Time Protocol
SS7
- Signaling System No. 7
VLR
- Visitor Location Register
VI

SJ-20101208143956-019-ZXWN MSCS (V4.10.13) MSC Server Routine Maintenance Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SJ-20101208143956-019-ZXWN MSCS (V4.10.13) MSC Server Routine Maintenance Guide

Hochgeladen von

Copyright:

Verfügbare Formate

ZXWN MSCS

Revision No. Revision Date Revison Reason

R1.0 2011-02-28 First edition

Serial Number: SJ-20101208143956-019

Publishing Date: 2011-02-28(R1.0)

Chapter 2 Overview of Routine Maintenance .......................................... 2-1

Chapter 3 Routine Maintenance................................................................ 3-1

Appendix A Reference Table for Maintenance ....................................... A-1

Prerequisite Skill and Knowledge

What Is in This Manual

Chapter 2, Overview of Routine This chapter introduces the classification of routine

Appendix B, Common Maintenance This part lists common maintenance table.

FCC Compliance Statement

1. This device may not cause harmful interference.

Italics References to other Manuals and documents.

“Quotes” Links on screens.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before proceeding

ZXWN MSCS manufactured by ZTE CORPORATION meets the requirements of EU 2002/95/EC;

1.2 Safety Precautions

1.3 Safety Symbol

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

2.2 Routine Maintenance Classification

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

3. Common failure handling

2.3 Common Maintenance Methods

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

2.4 Precautions on Routine Maintenance

3. Establish a complete set of maintenance regulations for the equipment room to

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

3.2 Introduction to Routine Maintenance

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

l Weekly routine maintenance

3.3 Daily Routine Maintenance

l Checking equipment room environment

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

l Checking Mc interface status

3.3.1 Checking Equipment Room Environment

Table 3-1 Requirements of ZXWN MSCS Equipment on Operational Environment

Parameter Name Indices

Long-term working condition (note 1) 5℃~40℃

Long-term working condition 5 %~85 %

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

3. Check the reading on the hygrometer in the equipment room.

3.3.2 Checking Power Supply in the Equipment Room

3.3.3 Checking Board CPU Status

The criteria for checking the CPU status are as follows.

The processing procedure of exceptions is as follows.

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

3.3.4 Checking Equipment Working Status

SJ-20101208143956-019|2011-02-28(R1.0) ZTE Proprietary and Confidential

Table 3-2 Indicators on Boards

Name Color Description

Service status indicator. It is on in green during power

Health status indicator. It flashes in red at 5 Hz when

Dual-color indicator Active/standby indicator: on for active, and off for

H/S Blue Hot swap indicator. It is on when the board is offline.

Running/alarm indicator. The green indicator indicates