ZXUN USPP Maintenance & Troubleshooting-System Maintenance-Routine Maintenance-201008-80

ZXUN USPP
Universal Subscriber Profile Platform

Training Manual
HLR Routine Maintenance
ZTE UNIVERSITY
ZTE University, Dameisha
YanTian District, Shenzhen,
P. R. China
518083
Tel: (86) 755 26778800
Fax: (86) 755 26778999
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2010 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 CORPO-
RATION 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 dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. 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.
Publishing Date (MONTH/DATE/YEAR) : 08/09/2010

Contents
HLR Routine Maintenance............................................. 1

1 Routine Maintenance Overview ................................. 2
1.1 Classification......................................................................... 2
1.2 Purposes .............................................................................. 2
1.3 Precautions........................................................................... 3
2 Daily Routine Maintenance ........................................ 5
2.1 Equipment Room Environment Check ....................................... 5
2.1.1 Checking Equipment Room Temperature........................... 5
2.1.2 Checking Equipment Room Humidity ................................ 5
2.2 Hardware System Check......................................................... 6
2.2.1 Checking Board Status ................................................... 6
2.2.2 Checking DSA Node Status ............................................. 6
2.3 Checking System Alarms ........................................................ 8
2.4 Performance Statistics Check .................................................. 9
2.4.1 Checking MTP3 Signaling Links........................................ 9
2.4.2 Checking MTP3B Signaling Links .....................................11
2.4.3 Checking M3UA Signaling Links ......................................11
2.4.4 Checking Processing Success Ratios of Basic
Services .........................................................................................12
2.4.5 Checking Processing Success Ratios of SMS .....................13
2.5 Module Call Loss Check .........................................................14
2.5.1 Checking Call Losses of FE Modules.................................14
2.5.2 Checking UDS Module Call Losses ...................................16
2.6 DST Check...........................................................................18
2.6.1 Checking DST Network Status ........................................18
2.6.2 Checking DST Timed Backup Tasks .................................20
2.7 Log Check ...........................................................................21
2.7.1 Checking FE Logs .........................................................21
2.7.2 Checking DBIO Logs ....................................................23
2.7.3 Checking IMP Logs ......................................................25
2.7.4 Checking UDS Logs ......................................................26
2.7.5 Checking OMC Logs ......................................................30
3 Weekly Routine Maintenance .................................. 33
3.1 FE Check .............................................................................33
3.1.1 Checking FE Time.........................................................33
3.1.2 Checking Resource Occupancy of FE Applications ..............35
3.2 DBIO Check .........................................................................36
3.2.1 Checking DBIO Server Time...........................................36
3.2.2 Checking DBIO Disk Space Usage ...................................37
3.2.3 Checking Virus Database Update on DBIO Server .............37
3.2.4 Checking DBIO OS Logs ................................................38
3.3 IMP Check ...........................................................................38
3.3.1 Checking Hard Disk Occupancy of the IMP .......................38
3.3.2 Checking Virus Database Update of the IMP .....................39
3.3.3 Checking OS Logs of the IMP .........................................39
3.4 UDS Check ..........................................................................40
3.4.1 Checking Resource Occupancy of DSA Applications ...........40
3.4.2 Checking Capacity of U_OISDNCHG ................................41
3.4.3 Checking DST Resource Occupancy.................................41
3.4.4 Checking DST Disk Space Usage.....................................42
3.4.5 Checking DST Memory Usage.........................................43
3.4.6 Checking Data Validity ..................................................43
3.4.7 Checking Disk Array .....................................................44
3.5 OMC Server Check................................................................45
3.5.1 Checking Hard Disk Occupancy of NMS Server..................45
3.5.2 Checking Database Space Usage of NMS Server ...............45
3.5.3 Checking Virus Database Update of NMS Server ...............46
3.5.4 Checking OS Logs in NMS Server....................................46
3.6 Performance Statistics Check .................................................47
3.6.1 Checking the Number of Subscribers ..............................47
Services .........................................................................................49
3.6.4 Checking UDS Consistency ............................................51
3.6.5 Checking Board Load ....................................................52
3.6.6 Checking Server Load ...................................................53
4 Monthly Routine Maintenance ................................. 55
4.1 Performance Statistics Check .................................................55
4.1.1 Checking Success Ratio of Service Provision.....................55
Services .........................................................................................57
4.1.4 Checking Processing Success Ratios of Packet
Services .........................................................................................59
4.2 Checking FE Version..............................................................60
4.3 ATCA Physical Environment Check...........................................61
4.3.1 Checking Shelf Temperature ..........................................61
4.3.2 Checking DC Voltage.....................................................62
4.3.3 Checking Heat Radiation of Racks ...................................62
4.3.4 Checking CMM System Time ..........................................63
4.3.5 Checking Switch Blade Voltage .......................................63
4.3.6 Checking Fan Running Status .........................................64
4.3.7 Checking Server Blade Temperature................................64
4.3.8 Checking Server Blade Voltage .......................................65
4.3.9 Checking Rear Board of Server Blade .............................66
4.4 Juniper Switch Check ............................................................66
4.4.1 Checking Running Status of Juniper Switch ......................66
4.4.2 Checking BFD Session Status of Juniper Switch ................67
4.4.3 Checking Spanning Tree Protocol Status of Juniper
Switch ...........................................................................................67
4.4.4 Checking State of Physical and Aggregated Interfaces of
Juniper Switch ................................................................................67
4.4.5 Checking VRRP Status of Juniper Switch ..........................68
4.4.6 Checking Time of Juniper Switch ....................................68
4.5 Checking Auto-backup of NM Configuration Data.......................68
5 Cautions for Routine Maintenance ........................... 71
Glossary ..................................................................... 73
USPP(HLR)_SM001_E1_0
HLR Routine
Maintenance
After you have completed this course, you
will be able to:

>> Master Daily Routine Maintenance
>> Master Weekly Routine Maintenance
>> Master Monthly Routine Maintenance
>> Master Warning of Dangerous Opera-
tions
Confidential and Proprietary Information of ZTE CORPORATION 1

ZXUN USPP Training Manual
Chapter 1 Routine Maintenance

Overview
After you have completed this chapter, you will know:

>> Classification
>> Purposes
>> Precautions
1.1 Classification
Description To effectively implement the functions of the equipment and pre-
vent potential accidents, it is necessary to perform routine main-
tenance on the running equipment. Routine maintenance is a
preventive measure, which aims to discover and remove the de-
fects and hidden risks of the equipment in time. Regular check
and maintenance improve the safety, stability and reliability of the
equipment.
Category The routine maintenance can be divided into two categories:
Daily Routine Maintenance
Regular Routine Maintenance
Daily Routine Daily routine maintenance refers to the maintenance operations
Maintenance that are implemented by the common maintenance personnel
every day, with relatively simple maintenance process, such as
equipment room environment check, equipment running check,
alarm system check, and log check.
Regular Routine Regular routine maintenance refers to the relatively complicated
Maintenance maintenance operations, such as resource occupancy check and
equipment running environment check that are regularly imple-
mented by the trained maintenance personnel in a certain period
(for example, a week or a month).
1.2 Purposes
Daily Maintenance Find out the alarms of the equipment or hidden risks in time
Purpose and adopt appropriate measures to handle and recover the
faults so as to maintain the healthy level of the equipment and
reduce equipment faults.
Find out the abnormalities of link status or connection dur-
ing service running in time and adopt appropriate measures to
handle and recover system faults so as to ensure normal ser-
vice running.
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Routine Maintenance Overview
Grasp the running status of the equipment and network in real

time, know the running trend of the equipment and network,
and improve the sudden-event handling efficiency of the main-
tenance personnel.
Regular Make the equipment always remain in good condition, and en-
Maintenance sure the safe, stable and reliable running of the system.
Purpose
Find out hidden troubles, including natural aging, function ex-
piry and performance deterioration during the running of the
equipment in time; handle these troubles to prevent the acci-
dents.
1.3 Precautions
Establish a complete set of maintenance regulations for the
equipment room to standardize the routine maintenance work.
Create detailed duty logs and make detailed records of the
daily running state of the system, version, data change, up-
grading and troubleshooting, so that it will be convenient for
fault analysis and troubleshooting once a fault occurs. Keep a
shift record to define the responsibilities clearly.
Maintenance personnel should be well trained on the skills of
basic operations and emergency troubleshooting before taking
the post and should grasp the knowledge related to the equip-
ment maintenance and the networks. During maintenance op-
erations, the maintenance personnel must follow the instruc-
tions described in the related manuals of the HSS system. To
avoid any accident, the personnel must put on antistatic wrist
straps before operating the equipment. The maintenance per-
sonnel should have a precise working attitude and professional
maintenance skills, which should be enhanced through con-
stant learning.
Make records for all the important operations (such as board
switching, system resetting, and software loading). Before the
operations, the qualified maintenance personnel must analyze
the feasibility of the operations and take the related backup,
emergency, and security measures. Back up the data before
you do any change to them. Do not delete the backup data
until the equipment runs properly for a time period (usually a
week) after you change the data.
Set different NMS passwords with different access rights, put
them under strict management, and make changes to them
periodically. The passwords should be provided only to the
maintenance personnel.
Do not play games or surf the Internet on PC terminals. Do
not install, run or copy any other software not related to the
system on the terminal. Do not use the PC terminal for any
other purposes.
Have the regularly used tools and meters ready. The regu-
larly used tools and meters include screwdrivers (flathead and
crosshead), signaling tester, network cable pliers, multi-me-
ter, AC power, telephone line, and network cables. Test and
calibrate the instruments and meters regularly to ensure their
accuracy.

Check spare components regularly to ensure they are sufficient

in quantity and are in good condition, and make sure that the
components are not affected by dampness or mould. Keep
them away from those faulty ones removed during mainte-
nance. Return the faulty boards for repair in time and prepare
sufficient spare parts for the major boards.
Keep the software and documents that might be used during
the maintenance in a handy place.
Keep the equipment room in normal temperature and humidity.
Keep the environment neat and clean. Take dust prevention
and damp prevention measures. Keep rats and insects out.
Ensure the primary power of the system is stable. Check the
system grounding and lightning protection ground periodically.
Check the lightning protection system before and after the
storm season to make sure that related facilities are in good
condition.
Make sure that the light in the equipment room is bright enough
for the maintenance. Any damaged lamp should be repaired
in time.
The maintenance personnel must perform regular checks and
tests each day and make records by referencing related sug-
gestions in the manual.
Handle any fault as soon as it is detected. Record the detailed
information of the problem that cannot be solved, and then
contact ZTE local office or customer service center for help.
If there is an emergency in the equipment room, the main-
tenance personnel must be calm and perform troubleshooting
according to the Troubleshooting Manual, and contact ZTE lo-
cal office or customer service center immediately.
Keep the contact information of ZTE local office in a noticeable
place and let all maintenance personnel notice it, so they can
contact ZTE in time when they need help. Maintain the contact
information regularly to keep it up to date.

Chapter 2 Daily Routine
Maintenance

>> Equipment Room Environment Check
>> Hardware System Check
>> Checking System Alarms
>> Performance Statistics Check
>> Module Call Loss Check
>> DST Check
>> Log Check
2.1 Equipment Room Environment

Check
2.1.1 Checking Equipment Room
Temperature
Item Check the equipment room temperature.

Purpose Make sure the equipment works under normal temperature.
Procedure Check the temperature shown at the air conditioner.
Criteria In normal cases, the temperature in the equipment room is 15
C~25 C.
2.1.2 Checking Equipment Room

Humidity
Item Check the equipment room humidity.

Purpose Make sure the equipment works under normal humidity.
Procedure Check the relative humidity shown at the air conditioner.
Criteria In normal cases, the relative humidity in the equipment room is
30%~70%.

2.2 Hardware System Check

2.2.1 Checking Board Status
Item Check the running status of boards through panel indicators. The
panel indicators are located on the FE boards, CMM modules,
switching blades, server blades, and fan box.
Purpose Identify board running status by observing the panel indicators.
Procedure For more information about the panel indicators, refer to ZXUN
USPP Universal Subscriber Profile Platform Hardware Description.
Criteria On each panel, the RUN indicator flashes normally and the ALM
indicator is off.
2.2.2 Checking DSA Node Status
Item Check the DSA node status.

Purpose Make sure the DSA node status is normal.
Procedure 1. Log in to the OMM client and enter the NetNumen M30 HLR
main interface. The default view is Daily Maintenance, as
shown in Figure 1.
FIGURE 1 NETNUMEN M30 HLR MAIN INTERFACE

Chapter 2 Daily Routine Maintenance
Note:
For more information about the operations related to OMM daily
maintenance, refer to ZXUN USPP Universal Subscriber Profile
Platform OMM Operation Guide (Daily Operation).
2. On the Watch Report interface as shown in Figure 1, right-

click the UDS entity and select Show All Dsa Node(s) Sta-
tus from the pop-up menu. The Observe DSA node status
interface appears, as shown in Figure 2.
FIGURE 2 UDS TOPOLOGY OBSERVATION INTERFACE
3. In the Node Status field, select all DSA nodes in the DSA tab,
and then click the Start Observe button to observe the status
of the DSA nodes.
Criteria On the DSA tab, the values of Master/Slave, Online Or Not,
Storage Status, and Schema Version of each DSA node must
be correct. For example, the observation result in Figure 3 shows
that the DSA nodes are normal.
FIGURE 3 DSA NODE STATUS

If the observation result shows that any DSA node is abnormal,

check the related alarm information and contact ZTE technical per-
sonnel in time to locate and troubleshoot the fault.
2.3 Checking System Alarms

Item Check the system alarms.
Purpose Make sure there is no abnormal alarm in the system.
main interface.
Note:
You can also log in to the EMS client to check the system
alarms. For more information about the operations, refer to
ZXUN USPP Universal Subscriber Profile Platform EMS Opera-
tion Guide (Alarm Management).
2. On the main interface of NetNumen M30 HLR, enter the

Fault Management view as shown in Figure 4 through the
following methods:
Click the (Fault Management) button.
Choose View > Fault Management from the menu.
FIGURE 4 FAULT MANAGEMENT VIEW

Note:
For more information about the operations related to OMM fault
management, refer to ZXUN USPP Universal Subscriber Profile
Platform OMM Operation Guide (Alarm Management).
3. When checking the system alarms, the following five items

should be checked in every check period:
Current alarms, current alarm recovery information, and
current notices.
System alarms of the day before.
System alarms of the past 3 days.
Notices of the day before.
Notices of the past 3 days.
Criteria There is no abnormal alarm or notification in the system.
Any alarm found should be analyzed and processed in time. The
alarm and troubleshooting information should be sent to ZTE tech-
nical personnel. If the problem cannot be solved, contact ZTE
technical personnel immediately.
2.4 Performance Statistics Check

2.4.1 Checking MTP3 Signaling Links
Item Check the MTP3 signaling links.

Purpose Check if the performance index values of the MTP3 signaling links
have obvious fluctuation.
main interface.
2. On the main interface of NetNumen M30 HLR, enter the Per-
formance Management view as shown in Figure 5 through
the following methods:
Click the (Performance Management) button.
Choose Views > Performance Management from the
menu.

FIGURE 5 PERFORMANCE MANAGEMENT VIEW
Note:
Before performing the query for the first time, you must
create the corresponding measurement task.
For more information about the creation and query opera-
tions in the OMM performance management, refer to ZXUN
USPP Universal Subscriber Profile Platform OMM Operation
Guide (Performance Management).
3. Query the measurement task in measurement type MTP3 Sig-

naling Link. Collect performance index values during the
busiest hours in 5-minute granularity. The performance in-
dices to be queried include: Peak traffic of signaling link
(1/10000) and Link occupancy ratio (1/10000).
Note:
In the Performance Management navigation tree, the path
of measurement type MTP3 Signaling Link is as follows:
Bureau Measurement > Signaling Measurement > No.7
Measurement > MTP3 Signaling Link.
4. Check the performance indices of the MTP3 signaling links dur-

ing the busiest hours. Check if the load is evenly shared among
the signaling links or the load of some signaling links is too
high.
Criteria The load is evenly shared among the signaling links.
The load of 2M signaling link should not exceed 0.2 Erl, and
that of 64K signaling link should not exceed 0.4 Erl.

2.4.2 Checking MTP3B Signaling Links
Item Check the MTP3B signaling links.

Purpose Check if the performance index values of the MTP3B signaling links
main interface.
formance Management view through the following methods:
menu.
Note:
3. Query the measurement task in measurement type MTP3B

Signaling Link. Collect performance index values during the
busiest hours in 5-minute granularity. The performance in-
dices to be queried include: Peak traffic of signaling link
(1/10000) and Link occupancy ratio (1/10000).
Note:
of measurement type MTP3B Signaling Link is as follows:
Bureau Measurement > Signaling Measurement > No.7
Measurement > MTP3B Signaling Link.
4. Check the performance indices of the MTP3B signaling links

during the busiest hours. Check if the load is evenly shared
among the signaling links or the load of some signaling links is
too high.
The load of 2M signaling link should not exceed 0.2 Erl, and
that of 64K signaling link should not exceed 0.4 Erl.
2.4.3 Checking M3UA Signaling Links
Item Check the M3UA signaling links.

Purpose Check if the performance index values of the M3UA signaling links
main interface.
menu.
Note:
create the corresponding calculation index and measure-
ment task.
3. Query the measurement task in measurement type M3UA.

Measure the number of messages sent and received during
the busiest hours in 5-minute granularity.
Note:
of measurement type M3UA is as follows: Bureau Measure-
ment > Signaling Measurement > Sigtran Measurement
> M3UA.
4. Check the performance indices of the M3UA signaling links dur-

ing the busiest hours. Check if the load is evenly shared among
the signaling links or the load of some signaling links is too
high.
The load of each M3UA signaling link should not exceed 0.2 Erl.
2.4.4 Checking Processing Success

Ratios of Basic Services
Item Check the processing success ratio of each basic service.

Purpose Check if the processing success ratio of each basic service has
obvious fluctuation.
main interface.


menu.
Note:
create the corresponding calculation indices and measure-
ment tasks.
3. Query the measurement tasks of the measurement type Basic

Service. Collect the performance statistics data on each day
for analysis.
Note:
In this topic, the calculation indices to be queried are the
processing success ratios of such basic services as authen-
tication, location update, call routing, separate subscriber
data insertion and separate subscriber data deletion.
In the Performance Management navigation tree, the
path of the measurement type Basic Service is as follows:
Bureau Measurement > WCN Service Measurement >
Basic Service.
4. Check the processing success ratio of each basic service. Com-

pare the processing success ratios of basic services with those
in the previous day, and check if the success ratios in the same
time segment have obvious fluctuation.
Criteria The processing success ratios of basic services in one office should
be stable with no obvious fluctuation except on holidays.

Ratios of SMS
Item Check the processing success ratio of SMS.

Purpose Check if the processing success ratio of SMS has obvious fluctua-
tion.
main interface.


menu.
Note:
ment tasks.
3. Query the measurement tasks of the measurement type SM

Service. Collect the performance statistics data on each day
for analysis.
Note:
In this topic, the calculation index to be queried is the pro-
cessing success ratio of SMS and the counters involved
in the calculation include Times of attempted sending
routing information for short messages and Times
of successful sending routing information for short
messages.
path of the measurement type SM Service is as follows:
SM Service.
4. Check the processing success ratio of SMS. Compare the pro-

cessing success ratios of SMS with those in the previous day,
and check if the success ratios in the same time segment have
Criteria The processing success ratios of SMS in one office should be stable
with no obvious fluctuation except on holidays.
2.5 Module Call Loss Check

2.5.1 Checking Call Losses of FE
Modules
Item Check the call losses of the FE modules.

Purpose Make sure the FE modules do not have abnormal call losses.
main interface.

2. On the main interface of NetNumen M30 HLR, enter the Fail-

ure Observation view as shown in Figure 6 through the fol-
lowing methods:
Click the (Failure Observation) button.
Choose View > Failure Observation from the menu.
FIGURE 6 FAILURE OBSERVATION VIEW
Note:
For more information about the operations related to OMM fail-
ure observation, refer to ZXUN USPP Universal Subscriber Pro-
file Platform OMM Operation Guide (Daily Operation).
3. Right-click the WCN MAP or SCCP node on the left side of the
navigation tree. Choose Create Task in the shortcut menu.
The dialog box of failure observation task settings appears.
For example, right-click the WCN MAP node. Choose Create
Task in the shortcut menu. A dialog box appears, as shown in
Figure 7.

FIGURE 7 FAILURE OBSERVATION TASK SETTINGS
4. Choose the FE module to be traced. Set the Filter Setting to

exclude or show the selected failure causes. Click OK to en-
ter the failure observation interface and trace the failure mes-
sages.
Criteria There are few abnormal call losses in the failure observation of FE
modules.
If abnormal call losses occur, locate the problem based on the dis-
played failure reasons and module information, and then take the
corresponding measures. If you cannot locate the problem, con-
tact ZTE technical personnel for help.
2.5.2 Checking UDS Module Call

Losses
Item Check the call losses of UDS modules.

Purpose Make sure the UDS modules do not have abnormal call losses.
main interface.
2. On the main interface of NetNumen M30 HLR, enter the Fail-
ure Observation view as shown in Figure 8 through the fol-
lowing methods:
Click the (Failure Observation) button.
Choose menu View > Failure Observation.

FIGURE 8 FAILURE OBSERVATION VIEW
Note:
For more information about the operations related to OMM fail-
ure observation, refer to ZXUN USPP Universal Subscriber Pro-
file Platform OMM Operation Guide (Daily Operation).
3. Right-click the UDS Protocol or UDS System node in the left

side of the navigation tree. Choose Create Task in the short-
cut menu. The dialog box of failure observation task settings
appears.
For example, right-click the UDS Protocol node. Choose Cre-
ate Task in the shortcut menu. A dialog box appears, as
shown in Figure 9.

FIGURE 9 FAILURE OBSERVATION TASK SETTINGS OF UDS PROTOCOL
4. Choose the UDS module to be traced. Set the Filter Setting

to exclude or show the selected failure causes. Click OK to en-
ter the failure observation interface and trace the failure mes-
sages.
Criteria There are not large amount of abnormal call losses in the failure
observation of UDS modules.
If abnormal call losses occur, locate the problem based on the dis-
played failure reasons and module information, and then take the
corresponding measures. If you cannot locate the problem, con-
tact ZTE technical personnel for help.
2.6 DST Check

2.6.1 Checking DST Network Status
Item Check the DST network status.

Purpose Make sure the DST network status is normal.
Note:
Currently, the ATCA system has 8 network adapters in total,
among which, two are reserved for the dual-server heartbeat,
and the other six are aggregated into three Bonds, with two
network adapters in each Bond. ("Bond" means that two network
adapters are configured with the same external IP address to
realize redundancy or load-sharing.) The 3 Bonds are described
as follows:
Bond0: It acts as the network adapter for the communication
between the front-end and back-end systems. Floating IP ad-
dresses of the dual-server systems of the DST and database
are configured at bond0.
Bond1: It acts as the network adapter for connecting the disk
array. The fixed IP addresses for the communication between
the ATCA and disk array are configured at bond1.
Bond2: It acts as the network adapter for cross-office commu-
nication. It does not exist if the DSA dumped by the DST does
not cross offices.
Procedure 1. Check the network adapter status.

Run command ifconfig a to query the network adapter sta-
tus. The output result is as shown in Figure 10.
FIGURE 10 NETWORK ADAPTER CHECK RESULT
Here, UP suggests that a cable has been plugged in the

network adapter port and signals are being received through
the cable, and the network adapter port is active. If it is
DOWN, the network adapter is inactive or the cable has been
unplugged from the network adapter port.
Note:
During routine maintenance, you only need to examine the
statuses of bond0, bond1 and bond2.
2. Check the switching records of network adapters.

Open all DST logs related to bond0 and bond1 and check if
there are any faults or switches within the aggregation group.

Note:
If network adapter fault appears or the cable is unplugged from
the network adapter, logs will be generated with the file name
/var/log/messages.
3. Check the network quality.

Run command netstat i to query the statistics information of
the network adapter. The output result is as shown in Figure
11.
FIGURE 11 NETWORK QUALITY CHECK RESULT
Here, RX-ERR shows how many packets have failed to be re-

ceived. TX-ERR shows how many packets have failed to be
sent.
Criteria Make sure the network adapters configured with floating IP
addresses are "UP".
Make sure there is no such record as network adapter "DOWN"
or intra-bond switching of network adapters in the system logs
or dual-server logs.
If there is any switching of network adapters, collect the cor-
responding logs and send them to ZTE technical personnel for
analysis.
Make sure RX-ERR and TX-ERR in the statistics data are 0 or
mostly 0. Otherwise, there are failures of data sending/receiv-
ing caused by network problem.
2.6.2 Checking DST Timed Backup

Tasks
Item Check the DST timed backup tasks.

Purpose Make sure the DST timed backup tasks are performed normally.
Procedure 1. Check if data backup has been performed.
Run command cat /var/log/messages |grep BakData to
check the data backup. The following information appears:
May 2 04:00:01 uds202 /usr/sbin/cron[14573]: (root) CMD
(/oracle/BackupRestore/manage/BakDataManage.sh)

Note:
If timed tasks are not carried out on time, examine the log file
to find out the reason.
2. Check if the backup files are normal.

The DST program runs data backup according to the time set
on the NMS, and the backup files are stored at /uds/backup/.
For example, a certain DST dumps six DSAs. At the configured
backup time, the DST backs up the user data of each DSA in
the /uds/backup directory according to the DSA ID. You can
tell if the files are normal by checking the size of the files in
the six folders.
Criteria Normally, there should be records output every day. It is
deemed to be abnormal if no record is output one day.
All the backup files are normal, that is, the file size does not
change abnormally.
2.7 Log Check

2.7.1 Checking FE Logs
Item Check the FE logs.

Purpose Check if there is system problem through logs.
main interface.
2. On the main interface of NetNumen M30 HLR, choose Views
> Professional Maintenance from the menu to enter the
Professional Maintenance view.
3. Click the File Management node on the left side of the nav-
igation tree. The File Management view appears, as shown
in Figure 12.

FIGURE 12 FILE MANAGEMENT VIEW
4. Double-click MP > OMP(Module 1) to view the /DOC0 and

/IDE0 folders. Copy Exc_Omp.txt and Exc_pp.txt in /DOC0
and all files in the routine maintenance period in the EXCINFO
folder of /IDE0 to the local log\left directory. The location of
log files is as shown in Figure 13.
FIGURE 13 FE LOG FILES

Note:
The copy operation is described as follows:
i. Right-click the files to be copied, and then choose Copy in
the shortcut menu.
ii. On the left side of the File Management interface, choose
the Local node in the navigation tree and enter the
log\left folder. Right-click the blank on the right side of
the File Management interface, and then choose Paste
in the shortcut menu.
The left folder must be created in the log directory in ad-
vance. The actual path of the folder in the NMS installation di-
rectory is as follows: ZTE_HLR\zxwomcs\ums-clnt\log\left.
5. By referencing the operation in Step 4, copy the log files in

OMP (Module 1) (Right) to the local directory log\right.
6. Open the folder ZTE_HLR\zxwomcs\ums-clnt\log in the OMM
installation directory. Check the modification time of the log
files.
7. Open the logs modified within the present routine maintenance
period by using the Notepad of Microsoft Windows OS, and then
check if there is any exception information.
Criteria During the routine maintenance period, there is no key infor-
mation, such as Warning, Error, Failure, Exception, Dead
Loop, Loop, restart, INT 13, Broken, Fatal, Critical,
Notice, Shutdown, Close, Power OFF, or Power ON in the
log files. Otherwise, there may be exceptions in the system, and
you need to collect logs and send them to ZTE technical personnel
for analysis.
2.7.2 Checking DBIO Logs
2.7.2.1 Checking DBIO Service Logs
Item Check the DBIO service logs.

Purpose Make sure the DBIO service processing is normal.
Procedure Check the DBIO service logs in the log folder in the DBIO instal-
lation directory. The logs are as follows:
DBIOSRV: It records errors of DBIO command line and data-
reading, for example, failure of command line execution.
DBIOSYS: It records system-level errors of the DBIO, for ex-
ample, DBIO restart.
UDS_DMSS: It is the log of the link management module.
HSLOG: It is the log of the log-processing module.
HCDB: It records the error information of configuration inter-
faces, for example, failure of reading the configuration table.

DBCORE: It records the error information of core code errors of

the database, for example, the table-writing error.
DBESYS: It records the error information of the GLPI module.
The files are named in the format of DBIOSRV_office ID_Module
ID_number. For example, for DBIO module ID 131 in Office 1, the
filename can be DBIOSRV_1_131_0, and DBIOSRV_1_131_1, etc.
In the filenames, the last number is used only to differentiate the
files, and the number cycles (written into the next file if one file is
full). Therefore, the file with the biggest number does not neces-
sarily mean it is the last file. You can queue the files in the order
of the time they are generated, and then check the latest files.
Criteria During the routine maintenance period, the service logs do not
contain any error information (focus on two key words: "ERROR"
and "record not found"). Otherwise, analyze the error information.
If you are not sure about the error, contact ZTE technical personnel
immediately.
2.7.2.2 Checking DBIO Supportive Logs
Item Check the DBIO supportive logs.

Purpose Make sure the DBIO is running normally.
Procedure Check the DBIO supportive logs in the trace folder in the instal-
lation directory of the DBIO. The logs are as follows:
dbio_module no.errlog: records the errors during program
running.
dbio_module no.syslog: records the program running infor-
mation printed by the supportive subsystem.
s10see_app.log: records the application programs informa-
tion observed in the S10See tool.
s10see_oss.log: records the supportive running information
in the S10See tool.
Note:
After opening the S10See tool, you can change the printed details
of s10see_app.log and s10see_oss.log according to the print
level. It is suggested that the output logs be opened only during
troubleshooting.
Criteria During the routine maintenance period, there is no "error" infor-

mation in the errlog and syslog. Otherwise, analyze the cause to
the "error" information. If you are not sure about the error, con-
tact ZTE technical personnel immediately.

2.7.3 Checking IMP Logs
2.7.3.1 Checking Service Logs of the IMP
Item Check the service logs of the interface message processor (IMP).
Purpose Make sure the service processing of the IMP is normal.
Procedure Check the service logs in the hlrinterlog\hlrmi_Module No.
folder of the IMP. The logs are as follows:
APP_yyyymmdd.LOG: records the MML commands received by
the IMP and the execution results.
SOAP_yyyymmdd.LOG: records the XML commands received by
the IMP and the execution results.
RUN.LOG: records the running information of programs such as
user login.
Here, "yyyymmdd" stands for the record date.
Note:
The path of the hlrinterlog folder is configured according to
hlrinter.ini in the IMP installation directory, and the default
path is c:\hlrinterlog.

mation in the logs. Otherwise, analyze the "error" information. If
you are not sure about the error, contact ZTE technical personnel
immediately.
2.7.3.2 Checking Supportive Logs of the IMP
Item Check the supportive logs of the IMP.

Purpose Make sure the IMP is running normally.
Procedure Check the supportive logs in the trace folder in the IMP installation
directory. The logs are as follows:
zxhlr_mi_module no.errlog: records the errors during pro-
gram running.
zxhlr_mi_module no.syslog: records the program running
information printed by the supportive subsystem.
s10see_app.log: records the application programs informa-
tion observed in the S10See tool.
s10see_oss.log: records the supportive running information
in the S10See tool.

Note:
After opening the S10See tool, you can change the printed details
of s10see_app.log and s10see_oss.log according to the print
level. It is suggested that the output logs be opened only during
troubleshooting.

mation in the errlog and syslog. Otherwise, analyze the cause to
the "error" information. If you are not sure about the error, con-
tact ZTE technical personnel immediately.
2.7.4 Checking UDS Logs
2.7.4.1 Checking DST Service Logs
Item Check the DST service logs.

Purpose Make sure the DST service processing is normal.
Procedure Check the log files of each subsystem in the /zxhlr/uds_offce
ID_dump node/log directory. Focus on the following key words:
"failed", "unsuccessful broken", "error", "fault", and "int13" to see
if there are any errors.
The log folder of the DST contains the following log files:
dbcore_office ID_node ID_0.log: Log of user memory DB
of 3G platform
hcdb__office ID_node ID_0.log: Log of memory DB mod-
ule configuration
uds_dbss_office ID_node ID_0.log: Log of service pro-
cessing of UDS memory DB
uds_dmss_office ID_node ID_0.log: UDS distributed mon-
itor processing log, recording if there are state shift or node
communication problems
uds_dsss_office ID_node ID_0.log: UDS directory service
processing log, recording if UDS has any problem in processing
the LDAP operation from the DBIO and FE
uds_mtss_office ID_node ID_0.log: UDS maintenance
message processing log, recording the processing of the
probes, NM messages, etc
uds_rss_office ID_node ID_0.log: Internal DSA data du-
plication log in the UDS
uds_sss_office ID_node ID_0.log: Data storage process-
ing log in the UDS
uds_sys_office ID_node ID_0.log: Log recording the brief
information of the UDS node running status
Criteria During the routine maintenance period, there are no "failed", "un-
successful broken", "error", "fault", or "int13" in the logs. If you

are not sure of the cause to the error logs, contact ZTE technical
personnel for help.
2.7.4.2 Checking DST Supportive Logs
Item Check the DST supportive logs.

Purpose Make sure the DST is running normally.
Procedure Check uds.out*.errlog and uds.out*.sysog in the
/zxhlr/uds_office ID_dump node/trace directory to find out
the DST running status. Check if there is any interruption caused
by the restart or problems of the node. Check if the physical links
between the current node and other nodes are interrupted.
Criteria During the maintenance period, there is no interruption caused
by the restart or other problems of the node. There is no link
interruption between the current node and other nodes. If you
are not sure of the cause to the error logs, contact ZTE technical
personnel for help.
2.7.4.3 Checking Dual-Server Logs
Item Check the dual-server logs.

Purpose Make sure the dual-server system is running normally.
Procedure The SUSE operating system of the ATCA board uses VCS cluster
management software. You can examine the status of the dual-
server system through the following two methods:
Use the GUI terminal.
i. Use Xmanager to log in to either server and run command
hagui. The login window appears as shown in Figure 14.

FIGURE 14 DUAL-SERVER LOGIN
ii. Choose the cluster to be checked. Enter the username and

password to log in to the VCS interface.
iii. Choose View > Logs from the menu. The cluster logs
interface appears, as shown in Figure 15.
FIGURE 15 DUAL-SERVER LOGS
iv. Click the Edit Filters button to select and filter the logs.
Focus on the "Critical", "Error", and "Warning" information
in the logs.
Use a command line.

Run command vi /var/VRTSvcs/log/engine_A.log to open

the /var/VRTSvcs/log/engine_A.log file. Check if the log
contains the "error", "failure", or "warning" information.
Criteria There is no "Critical", "Error", or "Warning" information in the VCS
logs. There is no log containing the "error", "failure", or "warning"
information. If you are not sure of the cause to the error logs,
contact ZTE technical personnel for help.
2.7.4.4 Checking DST Database Logs
Item Check the DST database logs.

Purpose Make sure the DST database is running normally.
Procedure 1. Check the status of the Oracle database instance.
Run command vi /oracle/admin/hlr/bdump/alert_hlr.
log to check if there are logs or log switching.
Normally, there is only log switching information during the
database operation, and any other information should be
deemed as abnormal. Log switching is like the following:
Tue May 19 20:30:37 2009 Thread 1 advanced to log sequence 43
(LGWR switch) Current log# 1 seq# 43 mem# 0: /oradata1/hlr/log1a
Current log# 1 seq# 43 mem# 1: /oradata2/hlr/log1b
2. Check the status of the Oracle listener.

i. Run command vi /oracle/products/10g/network/log
/sqlnet.log to check if the log file is empty.
There will be sqlnet.log only after the connection to
the database is interrupted. Therefore, the file should be
empty if the system operation is normal. If it is not empty,
the connection to the database has been interrupted.
ii. Run command vi /oracle/products/10g/network/log
/listener.log to check if the log file contains the informa-
tion other than the timed heartbeat detect information.
The listener.log is the log file of the Oracle listener. The
file should be empty if the system operation is normal.
However, because the dual-server system of Oracle 10g
checks the heartbeat regularly (the function cannot be dis-
abled at present), there should be information like the fol-
lowing:
11-MAR-2009 17:03:36 * (CONNECT_DATA=(CID=(PROGRAM=)
(HOST=uds209)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)
(SERVICE=LISTENER)(VERSION=169870336)) * status * 0
WARNING: Subscription for node down event still pending
Any information other than the above information in the

listener.log should be deemed as abnormal.
Criteria There is no log information other than the log switching infor-
mation in the alert_hlr.log.
There is no new log information in the sqlnet.log.
There is no log information other than the timed heartbeat de-
tect information in the listener.log.

2.7.5 Checking OMC Logs
2.7.5.1 Checking Database Logs of NMS Server
Item Check the database logs of the NMS server.

Purpose Make sure the database of the NMS server is running normally.
Procedure
Tip:
Perform the check on the EMS server and OMM server respectively.
1. Open the installation directory of the Oracle database in the

NMS server.
2. Check the log files in the \oracle\product\10.2.0\db_1\NE-
TWORK\log directory.
3. Check the alert*.log file in the \oracle\prod-
uct\10.2.0\admin\SID\bdump directory.
Here, SID is the actual database instance name.
Criteria During the routine maintenance period, there is no key error in-
formation such as Warning, Error, Failure, Exception, Dead
Loop, restart or INT 13 in the log files. If you are not sure of
the cause to the error logs, contact ZTE technical personnel for
help.
2.7.5.2 Checking NMS Logs
Item Check the NMS logs, including the operation logs, security logs,
and system logs.
Purpose Make sure the NMS system is running normally without any ab-
normal operation.
Procedure
Tip:
Perform the check on the EMS client and OMM client respectively.
This topic describes only the operations on the OMM client, which
are similar to those on the EMS client.
1. Log in to the OMM client and enter the NetNumen M30 HLR
main interface.
> Log Management from the menu. The Log Management
view appears, as shown in Figure 16.

FIGURE 16 LOG MANAGEMENT VIEW
Note:
For more information about the operations related to OMM log
Platform OMM Operation Guide (Daily Operation).
For more information about the operations related to EMS log
Platform EMS Operation Guide (Daily Operation).
3. Check the NMS logs, including the operation logs, security logs,
and system logs.
Criteria There is no abnormal operation information in the operation
Logs.
There is no illegal user login information in the security logs.
There is no error information in the system logs.

This page is intentionally blank.

Chapter 3 Weekly Routine
Maintenance

>> FE Check
>> DBIO Check
>> IMP Check
>> UDS Check
>> OMC Server Check
3.1 FE Check
3.1.1 Checking FE Time
Item Check the FE time.

Purpose Make sure the FE time is synchronous with the time of the SNTP
server (generally, the OMM server).
main interface.
2. On the main interface of NetNumen M30 HLR, enter the MML
Terminal view as shown in Figure 17 through the following
methods:
Click the (MML Terminal) button.
Choose Views > MML Terminal from the menu.

FIGURE 17 MML TERMINAL VIEW
3. In the navigation tree, click the node corresponding to the local

office, for example, node 8 as shown in Figure 17. In the lower
part of the Command Process interface, enter command S
HOW SNTPSVR in the text box. Click the Execute button
to query the configuration of the SNTP server. The command
execution result is as shown in Figure 18.
FIGURE 18 QUERYING THE SNTP SEVER SETTINGS
4. In the lower part of the Command Process interface of the

MML Terminal view, enter command SHOW TIME:MODUL
E=1 in the text box. Click the Execute button to query the FE
time. The command execution result is as shown in Figure 19.

Chapter 3 Weekly Routine Maintenance
FIGURE 19 QUERYING THE FE TIME
5. Click the (Query System Time) button in the toolbar to query

the OMM server time. Check if the FE time is synchronous with
the OMM server time.
Criteria The FE time is extracted from the SNTP server (OMM server).
The FE time and OMM time are synchronous.
3.1.2 Checking Resource Occupancy

of FE Applications
Item Check the resource occupancy of FE applications.

Purpose Make sure the resource occupancy ratios of FE applications are
within the normal range.
Procedure 1. Start ToolsClient.exe, and choose the DbManager function.
2. Enter the Bureau No. (current office ID) and Module No.
(module ID, here, it is module 1). Set the DataArea Type
(Data area type), and then click OK to open the resource ob-
servation tool.
3. Click the Query Modules button to query the FE modules.
Note:
Check the resource occupancy of all the FE service modules.
4. Right-click the resource item to be observed, and then choose

StatisticObserve in the shortcut menu.

5. Set the observation period and click OK to observe the resource

occupancy ratio.
Criteria Normally, during the observation period of 1 minute, the resource
occupancy ratio is low and the average ratio is below 1%. If the
ratio stays higher than that level for a long time, contact ZTE tech-
nical personnel for analysis immediately.
3.2 DBIO Check

3.2.1 Checking DBIO Server Time
Item Check the DBIO server time.

Purpose Make sure the time setting on the DBIO server is correct.
Procedure 1. Check the setting of time zone.
i. On the DBIO server, double-click the time in the notification
area. The Date and Time Properties dialog box appears.
ii. Choose the Time Zone tab, as shown in Figure 20.
FIGURE 20 TIME ZONE TAB
iii. Check the time zone setting, and then click OK.
2. Check the setting of time synchronization.
i. On the DBIO server, click Start, then choose Programs
> ZXWN HLR Tools > ZXWN HLR Configure Tool from
the taskbar. The configuration tool window appears.

ii. Expand the dbio node in the navigation tree on the dialog
box. Choose the node corresponding to the DBIO server to
enter the corresponding configuration tool interface.
iii. Choose the s10platsntp.ini tab on the interface and check
the time synchronization setting of the DBIO server, and
then click Quit.
Criteria The time zone of the DBIO server is consistent with the local
time zone.
The time of the DBIO server is synchronized with that of the
SNTP server (generally, the OMM server).
3.2.2 Checking DBIO Disk Space

Usage
Item Check the application resource occupancy (hard disk occupancy)

of the DBIO server.
Purpose Make sure the hard disk of the DBIO server has sufficient free
space.
Procedure 1. Check the total space and free space of the disk.
2. Check if there is any file or folder irrelated to the system.
Criteria The disk where the OS is located (Disk C) should have at least
800M free space, and the free space should be at least 20% of
the total disk space. Otherwise, delete some useless files.
Free space of other disks should also be at least 20% of the
total disk space. Otherwise, you need to delete some useless
files.
There are no files or folders irrelated to the system. Delete
them if there are any.
3.2.3 Checking Virus Database Update

on DBIO Server
Item Check the virus database update of the anti-virus software on the
DBIO server.
Purpose Prevent virus infection in the OS of the DBIO server.
Procedure Check the date of virus database update and update the virus data-
base.
Criteria Update the virus database manually at least once a week.
Disable the regular virus scanning function, and manually scan
the system for viruses when the call traffic is low.

3.2.4 Checking DBIO OS Logs
Item Check the OS logs in the DBIO server.

Purpose Detect potential risks on the DBIO server by checking the system
logs.
Procedure 1. On the DBIO server, click Start, then choose Programs >
Administrative Tools > Event Viewer. The Event Viewer
dialog box appears, as shown in Figure 21.
FIGURE 21 EVENT VIEWER DIALOG BOX
2. Check the Application logs, Security logs and System logs

of one week. Focus on logs of alarm and error.
Criteria There is no failure event in the application logs.
There is no such event as illegal access in the security logs.
There is no error event of the programs (such as system driver)
that affects system operation in the system logs, for example,
network adapter failure or hard disk problem.
3.3 IMP Check

3.3.1 Checking Hard Disk Occupancy
of the IMP

of the IMP.
Purpose Make sure the hard disk of the IMP has sufficient free space.
Procedure 1. Check the total space and free space of the disk.


Criteria The disk where the OS is located (Disk C) should have at least
800M free space, and the free space should be at least 20% of
the total disk space. Otherwise, delete some useless files.
total disk space. Otherwise, delete some useless files.

of the IMP
Item Check the virus database update of the anti-virus software in the
IMP.
Purpose Prevent virus infection in the OS of the IMP.
Procedure Check the date of virus database update and update the virus data-
base.
3.3.3 Checking OS Logs of the IMP
Item Check the OS logs of the IMP.

Purpose Detect potential risks in the OS of the IMP by checking the logs.
Procedure 1. On the IMP, click Start, then choose Programs > Adminis-
trative Tools > Event Viewer. The Event Viewer dialog
box appears, as shown in Figure 22.


3.4 UDS Check

3.4.1 Checking Resource Occupancy
of DSA Applications
Item Check the resource occupancy of DSA applications.

Purpose Make sure the resource occupancy ratio of DSA applications is
Procedure 1. Start ToolsClient.exe, and choose the DbManager function.
2. Enter the Bureau No. (current office ID) and Module No.
(module ID). Set the DataArea Type (Data area type) to UDS,
and then click OK to open the resource observation tool.
3. Click the Query Modules button to query the DB Resource
and Storage Info of each UDS module. Check if the module
status is normal.
Criteria The query is successful and the module status is normal. For ex-
ample, the check result is as shown in Figure 23.

FIGURE 23 RESOURCE OCCUPANCY OF DSA APPLICATIONS
3.4.2 Checking Capacity of

U_OISDNCHG
Item Check the capacity of the U_OISDNCHG.

Purpose Make sure the U_OISDNCHG has sufficient capacity.
Procedure Use the probe to check the U_OISDNCHG capacity and the number
of records in the table.
Criteria The number of current records does not exceed 80% of the table
capacity. Otherwise, contact ZTE technical personnel for analysis.
3.4.3 Checking DST Resource

Occupancy
Item Check the DST resource occupancy.

Purpose Make sure the DST resource occupancy ratio is normal.
Procedure Run command top, and the output result is as shown in Figure 24.

FIGURE 24 DST RESOURCE OCCUPANCY
The output result includes the CPU usage of users and kernel and
the usage of the memory and SWAP space. The CPU usage is listed
in a sequence. You can know the processes consuming much CPU
resource by refreshing the list.
Note:
According to the default configuration file, the DST performs the
CKPT operation every 5 minutes, which causes the CPU usage to
surge for a while. The duration of the surge depends on the ser-
vice volume. The surge is caused by two processes: uds.out and
oracle.
Criteria There is no abnormal surge of the CPU usage. The CPU usage
surge not caused by the uds.out and oracle processes should be
considered as abnormal.
3.4.4 Checking DST Disk Space Usage
Item Check the DST disk space usage.

Purpose Make sure the DST disk has sufficient free space.
Procedure Run command df k to check the DST disk space usage.
uds201:/zxhlr/uds_1_191/log # df -k Filesystem 1K-blocks
Used Available Use% Mounted on /dev/sda1 20972152
6850624 14121528 33% / udev 8220900 184
8220716 1% /dev /dev/sda5 20972152 1852536
19119616 9% /oracle /dev/sda7 41944376 32840
41911536 1% /uds /dev/sda6 31462264 383748
31078516 2% /zxhlr fas270c-a:/vol/oradata1_191 115343360
87848544 27494816 77% /oradata1 fas270c-b:/vol/oradata2_191
115343360 93213216 22130144 81% /oradata2
Information in bold belongs to the mapping logic disks of NetApp

disk array, and the other information belongs to the local ATCA
disks.

Criteria Except the mapping disks of NetApp disk array, the usage of each
file system shall be below 80%. Otherwise, pay close attention to
it and expand the capacity when necessary.
3.4.5 Checking DST Memory Usage
Item Check the DST memory usage.

Purpose Make sure there is sufficient idle memory in the DST.
Procedure Run command free -m to check the DST memory usage.
uds202:~ # free -m total used free shared buffers
cached Mem: 16056 11441 4615 0 177
8648 -/+ buffers/cache: 2615 13441 Swap:
16378 0 16378
Here, total is the total system memory, used is the memory that
is being used, and cached is the cache requested when the OS is
executing the IO operation (for example, a large amount of mem-
ory is used as cached when the DB server is performing frequent
IO operations). Generally speaking, cached memory equals to idle
memory.
Criteria In most cases, valid idle memory = free memory + cached mem-
ory. When there is less than 1G idle memory, pay attention to the
usage of SWAP space and the top five memory-consuming pro-
cesses.
3.4.6 Checking Data Validity
Item Check the data validity.

Purpose Make sure the data is valid.
Procedure 1. Check the running status of the filecheck server.
Run command ps ef|grep filecheck. Check if the output
information is similar to the following:
usppdata:/filecheck/log # ps -ef|grep filecheck root 19793
1 2 May28 ? 08:23:15 ./filecheck.out root
21005 20913 0 15:23 pts/2 00:00:00 grep filecheck
2. Check the output result of the filecheck server.

i. Enter the /filecheck folder of the filecheck server, and
then open the filecheck.result file.
ii. Check if the file contains the information related to the data
validity check.
3. Check the logs on the filecheck server.
i. Enter the /filecheck/log folder of the filecheck server,
and then open the filecheck_1_151_0.log file.
ii. Check if the log file contains the log information similar to
the following:

[2009-06-13 09:11:34:443] Pno:042, LEVEL:5, <***

finish check bno is 1, DSAID is 340, module is 60,
result is SUCCESS ***>
This log information indicates that the processing of DB
backup files of DSA cluster 340 is successful.
iii. Check if the data of each DSA cluster in the backup direc-
tory is the latest.
4. Check if there is abnormal alarm related to data validity on the
Alarm Management view of the NMS.
Note:
If a DSA cluster does not have DB logs backed up that day or
fails to rebuild indices, the filecheck server reports the log file
check failed alarm through a DSA in the DSA cluster.
Criteria The filecheck server is running normally.

The /filecheck/filecheck.result file in the filecheck server
contains the information indicating that the check is passed or
the specific reason for failed check.
The data of each DSA cluster in the backup directory is the
latest.
There is no abnormal alarm related to data validity in the NMS.
3.4.7 Checking Disk Array
Item Check the disk array.

Purpose Make sure the disk array works normally and has sufficient free
space.
Procedure 1. Check the status of RUN indicator of each disk on the front
panel of the disk array.
2. Check the status of Power indicators of the disk array.
3. Run telnet to the two headers of each disk array respectively,
and then check the operation prompt.
4. Based on the check result in 3.4.4, observe the disk usage of
each file system in the disk array, and compare the result with
the previous check result.
Criteria Normally, the status indicators of the disk array should be
green. The frequency of flash indicates the rate of read-
ing/writing. If any indicator is in any other color, there must
be an alarm. Record the alarm information and contact ZTE
technical personnel for help.
Normally, the Power indicators of the disk array should be
green. If any indicator is in any other color, there must be
an alarm. Record the alarm information and contact ZTE tech-
nical personnel for help.
Normally, after entering the disk array header, the operation
prompt is shown as the IP address of the header for the login,

and there should be no takeover in the prompt. If the prompt

contains takeover, it means that header takeover happens.
Contact ZTE technical personnel for help.
If the space usage of each file system in the disk array in-
creases continuously, all space can be used up in 30 days.
Contact ZTE technical personnel for help.
3.5 OMC Server Check

3.5.1 Checking Hard Disk Occupancy
of NMS Server

of the NMS server.
Purpose Make sure the hard disk of the NMS server has sufficient free
space.
Procedure
Tip:
1. Check the total space and free space of the disk.

Criteria The disk where the OS is located (Disk C) and the disk where
the Oracle database is located should have at least 800M free
space, and the free space should be at least 20% of the total
disk space. Otherwise, delete some useless files.
total disk space. Otherwise, delete some useless files.
3.5.2 Checking Database Space Usage

of NMS Server
Item Check the database space usage of the NMS server.

Purpose Make sure the space usage ratio of the tables in the NMS server
database is within the normal range.

Procedure
Tip:
1. On the NMS server, click Start, then choose Programs > Ora-
cle-OraDb10g_home1 > Database Control-SID. Here, SID
is the actual database instance name. The Enterprise Man-
ager interface appears.
2. Connect to the database as the user "sys".
3. In Space Summary of the Home tab, click the value of Data-
base Size to open the Tablespaces interface. Check the
space usage ratio of each table.
Criteria Usage ratio of each table space in the NMS server database should
be lower than 80%. Otherwise, contact ZTE technical personnel
for analysis.

of NMS Server
Item Check the virus database update of the anti-virus software on the
NMS server.
Purpose Prevent virus infection in the OS of the NMS server.
Procedure
Tip:
Check the date of virus database update and update the virus data-
base.
3.5.4 Checking OS Logs in NMS Server
Item Check the operating system (OS) logs in the NMS server.
Purpose Detect potential risks in the OS of the NMS server by checking the
logs.

Procedure
Tip:
1. On the NMS server, click Start, then choose Programs > Ad-
ministrative Tools > Event Viewer. The Event Viewer di-
alog box appears, as shown in Figure 25.


3.6.1 Checking the Number of
Subscribers
Item Check the number of subscribers.

Purpose Make sure the number of subscribers does not reach or get close
to the threshold controlled by the License.
main interface.


menu.
Note:
create the corresponding measurement tasks.
3. Query the measurement tasks of the measurement type WCN

Subscribers. The performance indices to be queried include
the number of current HLR subscribers, the number of sub-
scribers who subscribe each service, the number of national
roaming subscribers, the number of international roaming sub-
scribers etc.

Note:
of measurement type WCN Subscribers is as follows: Bu-
reau Measurement > Subscriber Number Measurement
> WCN Subscribers.
4. Check if the number of subscribers reaches or gets close to the

threshold controlled by the License.
Note:
If you are not sure about the threshold of subscriber number
in the local office, choose Views > License Management on
the NetNumen M30 main interface. The License Manage-
ment interface appears, showing the threshold controlled by
the License.
Criteria The number of subscribers should not exceed the threshold set by
the License. If the number reaches or gets close to the threshold,
apply to ZTE Corporation for a new license.


main interface.
menu.

Note:
ment tasks.

Service. Collect the performance statistics data in a week for
analysis.
Note:
Basic Service.

pare the processing success ratios of basic services in the same
time segment during the week, and check if the success ratios

Ratios of SMS

tion.
main interface.
menu.

Note:
ment tasks.

Service. Collect the performance statistics data in a week for
analysis.
Note:
messages.
SM Service.

cessing success ratios of SMS in the same time segment during
the week, and check if the success ratios have obvious fluctu-
ation.
3.6.4 Checking UDS Consistency
Item Check the UDS consistency.

Purpose Make sure the UDS consistency is normal.
main interface.
menu.

Note:
3. Query the measurement tasks of measurement type Statis-

tics of UDS DS Check. The indices to be queried include:
Count of received DSP CheckSa action, Count of suc-
cess DSP CheckSa action, Count of sent DSP CheckSa
action, Count of the Record not conform to other DSA
when checking, and Count of the Record successfully re-
vised when checking.
Note:
of measurement type Statistics of UDS DS Check is as fol-
lows: Bureau Measurement > UDS Measurement > Sta-
tistics of UDS DS Check.
4. Check if the values of the performance indices in the UDS con-

sistency check are all 0.
Note:
The consistency check is triggered when the IDSA has refer-
ence to the PDSA while there is no such record on the PDSA.
Therefore, when some system data is missing, the statistical
objects of the UDS consistency check are not 0.
Criteria During the normal operation, the statistical objects of the UDS
consistency check should be 0. If the statistical objects of the
UDS consistency check are not 0, it means that some system data
is missing. Contact ZTE technical personnel for help.
3.6.5 Checking Board Load
Item Checking the board load.

Purpose Make sure the board load is normal with no obvious fluctuation.
main interface.


menu.
Note:
3. Query the measurement task in measurement type Board

Load Statistic. Collect performance index values during the
busiest hours in 5-minute granularity. The performance indices
to be queried include: Mean ratio of the CPU usage(%),
Peak ratio of the CPU usage(%), Mean ratio of the mem-
ory usage(%), Peak ratio of the memory usage(%), and
Mean ratio of the hard disk usage(1/10000).
Note:
of measurement type Board Load Statistic is as follows: Bu-
reau Measurement > Global Measurement > Board Load
Statistic
4. Check the performance indices of the board in the busiest

hours. Check if the time segment is within the busy hours.
Compare the index values with historical data and check if the
data has obvious fluctuation.
Criteria The performance indices of the board load are within the normal
range. During the same busy hours, the indices are stable with no
3.6.6 Checking Server Load
Item Check the server load.

Purpose Make sure the server load is normal with no obvious fluctuation.
main interface.
menu.

Note:
3. Query the measurement task in measurement type HLR Sever

Load Statistic. Collect performance index values during the
busiest hours in 5-minute granularity. The performance indices
to be queried include: Mean ratio of the CPU usage(%),
Peak ratio of the CPU usage(%), Mean ratio of the mem-
ory usage(%), Peak ratio of the memory usage(%), and
Mean ratio of the hard disk usage(1/10000).
Note:
path of measurement type HLR Sever Load Statistic is as
follows: Bureau Measurement > Global Measurement >
HLR Sever Load Statistic.
4. Check the performance indices of the server in the busiest

hours. Check if the time segment is within the busy hours.
Compare the index values with historical data and check if the
data has obvious fluctuation.
Criteria The performance indices of the server load are within the normal
range. During the same busy hours, the indices are stable with no

Chapter 4 Monthly Routine
Maintenance

>> Checking FE Version
>> ATCA Physical Environment Check
>> Juniper Switch Check
>> Checking Auto-backup of NM Configuration Data

4.1.1 Checking Success Ratio of
Service Provision
Item Check the success ratio of the service provision.

Purpose Check if the success ratio of the service provision has obvious fluc-
tuation.
main interface.
menu.

Note:
ment tasks.
3. Query the measurement tasks of the measurement type WCN

Provision. Collect the performance statistics data in a month
for analysis. In the measurement type, all the service provi-
sioning operations on the agent and BOSS can be queried, in-
cluding: authentication provisioning, number allocation, user
deletion from the agent, suspension/power-off operations, in-
telligent service modification, supplementary service modifica-
tion, basic service modification and other operations.
Note:
provisioning success ratios of all WCN services.
path of the measurement type WCN Provision is as fol-
lows: Bureau Measurement > Provision Measurement
> WCN Provision.
4. Check the provisioning success ratio of each service. Compare

the success ratios of service provision in the same time seg-
ment during the month, and check if the success ratios have

Chapter 4 Monthly Routine Maintenance
Criteria The success ratios of services provision in one office should be

stable with no obvious fluctuation.


main interface.
menu.
Note:
ment tasks.

Service. Collect the performance statistics data in a month for
analysis.
Note:
Basic Service.

pare the processing success ratios of basic services in the same
time segment during the month, and check if the success ra-
tios have obvious fluctuation.


Ratios of SMS

tion.
main interface.
menu.
Note:
ment tasks.

Service. Collect the performance statistics data in a month
for analysis.
Note:
messages.
SM Service.

cessing success ratios of SMS in the same time segment during
the month, and check if the success ratios have obvious fluc-
tuation.


Ratios of Packet Services
Item Check the processing success ratio of each packet service.

Purpose Check if the processing success ratio of each packet service has
main interface.
menu.
Note:
ment tasks.
3. Query the measurement tasks of the measurement type

Packet Service. Collect the performance statistics data in a
month for analysis.
Note:
processing success ratios of sending routing information for
GPRS and GPRS location update.
path of the measurement type Packet Service is as fol-
lows: Bureau Measurement > WCN Service Measure-
ment > Packet Service.
4. Check the processing success ratio of each packet service.

Compare the processing success ratios of packet services in
the same time segment during the month, and check if the
success ratios have obvious fluctuation.
Criteria The processing success ratios of packet services in one office
should be stable with no obvious fluctuation except on holidays.

4.2 Checking FE Version

Item Check the running versions of FE modules.
Purpose Make sure the version of each FE module and board is consistent
with the OMM version.
main interface.
> Professional Maintenance from the menu to enter the
Professional Maintenance view.
3. Click the Version Management > Version Query node in
the navigation tree. The Version Query interface appears, as
shown in Figure 28.
FIGURE 28 VERSION QUERY INTERFACE
4. Click the (Query Running Version) button on the Version

Query interface. The Bureau Config Information dialog box
appears, as shown in Figure 29.

FIGURE 29 CONFIGURATION INFORMATION DIALOG BOX
5. Choose all the FE modules and boards. Click OK to query the

running versions. The versions of the queried modules and
boards are displayed on the Version Query interface.
Criteria The CPU version of each FE module and board is consistent with
the OMM version.
4.3 ATCA Physical Environment

Check
4.3.1 Checking Shelf Temperature
Item Check the shelf temperature.

Purpose Make sure the devices work under favorable temperature and the
heat radiation of the shelf is normal.
Procedure 1. Run command telnet to log in to the active CMM.
2. Run the following command to query the temperature at the
air outtake of the shelf:
cmmget l fantray1 -t 0:Chassis T001' -d current
3. Run the following command to query the temperature at the
air intake of the shelf:
cmmget -l shelf -t 0:ChassisTemp 1' -d current
cmmget -l shelf -t 0:ChassisTemp 2' -d current
Criteria The difference of the temperature at the air intake and the
room temperature should not be greater than 5 C.

The temperature at the air outtake should not be more than

10 C higher than the temperature at the air intake.
4.3.2 Checking DC Voltage
Item Check the DC voltage in the equipment room.

Purpose Make sure the DC power supply is reliable, and the monitoring data
on the power board in the server rack is normal.
Procedure 1. Use a multimeter to measure the voltage of the four power
supply lines in the rack and then record the data.
2. Run command telnet to log in to the active CMM.
3. Run the following commands to read the measured value of
the power board:
cmmget l pem1 t 0:DC48V-A d current
cmmget l pem1 t 0:DC48V-B d current
Criteria For the systems with -48 V power supply, the rated DC voltage
of the rack is -48 V and the allowed range of fluctuation is -57
V~-40 V. The DC voltage of each power supply line shown on the
multimeter should be within the range.
4.3.3 Checking Heat Radiation of

Racks
Item Check the heat radiation of racks.

Purpose Make sure the air intakes and outtakes of the racks are not blocked
and the fans are working normally.
Procedure 1. Check when the last cleaning was made and if the dust filter
needs to be cleaned. Remind the maintenance personnel to
clean dust filters regularly.
2. Check if air intakes and outtakes of the racks are blocked.
3. Check if the fans are working normally, if their rotation speeds
are consistent, and if there is any abnormal sound.
4. Check if the blank panels at the front and back slots are fixed
well.
Criteria The dust filters are clean.
The air intakes and outtakes are not blocked.
The fans are working normally.
The blank panels are fixed well.

4.3.4 Checking CMM System Time
Item Check the CMM system time.

Purpose Make sure the CMM system time is consistent with the local stan-
dard time.
2. Run command date to check if the CMM system time is con-
sistent with the local standard time.
Criteria The CMM system time is consistent with the local standard time.
4.3.5 Checking Switch Blade Voltage
Item Check the switch blade voltage.

Purpose Make sure the board-level voltage of the switch blade is within the
normal range.
2. Run the following command to query the voltage sensor on
each switch blade:
cmmget -l bladeN -d listtargets
Here, "N" stands for the slot of the switch blade. The value
range is 7-8.
3. Run the following command to query the current voltage value
displayed on the voltage sensor of each switch blade:
cmmget -l bladeN -t "0:+12vcc" -d current
range is 7-8. "+12vcc" stands for the +12 V voltage sen-
sor. Replace +12Vcc with +3.3Vcc, +2.5Vcc, +1.25Vcc, and
+1.2Vcc respectively to query the voltage threshold of each
voltage sensor.
4. Run the following command to query the voltage threshold of
the voltage sensor on each switch blade:
cmmget -l bladeN -t "0:+12vcc" -d thresholdsall
range is 7-8. "+12vcc" stands for the 12 V voltage sensor. Re-
place +12Vcc with +3.3Vcc, +2.5Vcc, +1.25Vcc, and +1.2Vcc
respectively to query the current voltage value of all voltage
sensors.
5. Compare the current voltage value with the voltage threshold
of each voltage sensor on the switch blade. Check if the voltage
values are all normal.
Criteria The current voltage values of all voltage sensors are within the
normal range.

4.3.6 Checking Fan Running Status
Item Check the fan running status in the fan box.

Purpose Make sure the fan running status is under monitor of the CMM.
Procedure 1. Check if the fan indicators are normal and if the sound of fan
running is normal.
2. Plug and unplug the fans and check if the fans can resume
working at the normal speed (level 7 by default).
3. Run command telnet to log in to the active CMM.
4. Run the following command to query the rotation speeds of the
fans:
cmmget l fantray1 t "0:SysFan-N" d current
Here, N can be any of 1-12.
5. Run the following command to query the fan speed level:
cmmget l fantray1 d currentfanlevel
6. Run the following command to query the recommended setting
of rotation speed level:
cmmgetl fantray1d recommendedsetting
Criteria The rotation speed level is 7 and the rotation speed is 4500-4600
rpm when the system is working under the normal temperature.
4.3.7 Checking Server Blade

Temperature
Item Check the temperatures of the CPU, MCH, and SAS controller of
the server blade.
Purpose Eliminate potential faults of the CPU, MCH and SAS controller.
2. Run the following command to query the current temperatures
of the MCH, SAS, CPU0 and CPU1.
cmmget l bladeN t "0:mch temp" d current
cmmget l bladeN t "0:sas temp" d current
cmmget l bladeN t "0:cpu0 temp" d current
cmmget l bladeN t "0:cpu1 temp" d current
Here, "N" stands for the slot of the server blade. The value can
be any of 1-6, 9-14.

Caution:
The difference of temperatures between CPU0 and CPU1 should
not be greater than 15 C. Otherwise, Check the installation of
heat radiators of the two CPUs.
3. Run the following command to query the temperature thresh-

olds of the MCH, SAS, and CPU0.
cmmget l bladeN t "0:mch temp" d thresholdsall
cmmget l bladeN t "0:sas temp" d thresholdsall
cmmget l bladeN t "0:cpu0 temp" d thresholdsall
be any of 1-6, 9-14.
4. Compare the current temperature value with the temperature
threshold of each temperature sensor on the server blade.
Check if the temperature values are all normal.
Criteria The current temperature values of all temperature sensors are
If the current value of the temperature sensor exceeds the
threshold, check if alarms are timely and correct. Check if
alarms recover quickly after the temperature falls below the
threshold.
If the current value of the temperature sensor exceeds the up-
per limit of the threshold, check if fans are working at full-
speed and if the temperature is dropping gradually. Avoid fre-
quent temperature fluctuations above and below the threshold
resulted from variation of fan rotation speed.
4.3.8 Checking Server Blade Voltage
Item Check the server blade voltage.

Purpose Make sure the board-level voltage of the server blade is within the
normal range.
2. Run the following command to query the voltage sensor on
each server blade:
cmmget -l bladeN -d listtargets
be any of 1-6, 9-14.
3. Run the following command to query the current voltage value
displayed on the voltage sensor of each server blade:
cmmget -l bladeN -t "0:+12vcc" -d current
Here, "N" stands for the slot of the server blade. The value
can be any of 1-6, 9-14. "+12vcc" stands for the +12 V volt-
age sensor. Replace +12Vcc with +5Vcc, +3.3Vcc, CPU0 Vcc,
CPU1 Vcc, DDR2 Vcc, +1.5Vcc, +1.05Vcc, SW Vcc and GE Vcc

respectively to query the voltage threshold of all voltage sen-

sors.
4. Run the following command to query the voltage threshold of
the voltage sensor on each server blade:
cmmget -l bladeN -t "0:+12vcc" -d thresholdsall
Here, "N" stands for the slot of the server blade. The value
can be any of 1-6, 9-14. "+12vcc" stands for the 12 V volt-
age sensor. Replace +12Vcc with +5Vcc, +3.3Vcc, CPU0 Vcc,
CPU1 Vcc, DDR2 Vcc, +1.5Vcc, +1.05Vcc, SW Vcc and GE Vcc
respectively to query the current voltage value of all voltage
sensors.
5. Compare the current voltage value with the voltage threshold
of each voltage sensor on the server blade. Check if the voltage
values are all normal.
Criteria The current voltage values of all voltage sensors are within the
normal range.
4.3.9 Checking Rear Board of Server

Blade
Item Check the external device connection on the rear board of the
server blade.
Purpose Make sure the VGA monitor, PS/2 keyboard and mouse are firmly
connected to the rear board of the server blade.
Procedure 1. Check if the VGA monitor, PS/2 keyboard and mouse are con-
nected correctly and users can operate the server blade with
the KVM.
2. Check if the fastening screws at cable connectors on the rear
board of the server blade are tight.
Criteria The VGA monitor, PS/2 keyboard and mouse of the server blade
work normally.
4.4 Juniper Switch Check

4.4.1 Checking Running Status of
Juniper Switch
Item Check the running status of the Juniper switch components.

Purpose Make sure all components of the Juniper switch are working nor-
mally.
Procedure 1. Log in to the switch through ssh or telnet as "user".
2. Run command show chassis environment.

Criteria The "status" of Power, Temp and Fans of the Juniper switch should
all be "ok".
4.4.2 Checking BFD Session Status of

Juniper Switch
Item Check the status of the BFD session for the communication be-
tween the Juniper switch and the FE modules.
Purpose Make sure the BFD session of the Juniper switch has been estab-
lished.
2. Run command show bfd session.
Criteria The "status" of each interface address for the communication be-
tween the Juniper switch and the FE modules should be "up".
4.4.3 Checking Spanning Tree Protocol

Status of Juniper Switch
Item Check the spanning tree protocol status of the Juniper switch's
ports.
Purpose Make sure the spanning tree protocol of the Juniper switch's ports
is enabled normally.
2. Run command show spanning-tree interface.
Criteria The "state" of SW1, SW2, ae0.0 and ae1.0 should be "FWD".
For SW3 and SW4, the current "state" of ae0.0, ae1.0, ae2.0,
ae3.0 and ae4.0 should be "FWD".
4.4.4 Checking State of Physical and

Aggregated Interfaces of Juniper
Switch
Item Check the state of physical and aggregated interfaces of the Ju-
niper switch.
Purpose Make sure the port connections of the Juniper switch are all nor-
mal.
2. Run command show interfaces | grep "ge-|ae" | grep
"Physical link is".
Criteria The physical links of the connected ports should be "up".

4.4.5 Checking VRRP Status of Juniper

Switch
Item Check the VRRP status of the Juniper switch.

Purpose Check if the VRRP status is normal and if any switchover happens.
2. Run command show vrrp.
Criteria Normally, the "VR state" of SW1 and SW3 should be "master",
and the "VR state" of SW2 and SW4 should be "backup".
If SW1 (or SW3) is powered off, the "VR state" of SW2 (or
SW4) should be "master".
4.4.6 Checking Time of Juniper Switch
Item Check the time of the Juniper switch.

Purpose Check if the time of the Juniper switch is correct, and check the
time of the last startup and configuration.
2. Run command show system uptime.
3. Check if the current time is consistent with the actual time.
4. Check if the system has been restarted or re-configured re-
cently.
Criteria The current time of the Juniper switch is consistent with the actual
time with an error of no more than 5 minutes. If the time of the
Juniper switch is inaccurate, check if the NTP server is normal.
4.5 Checking Auto-backup of NM

Configuration Data
Item Check the auto-backup of NM configuration data.
Purpose Make sure the NM configuration data is backed up regularly.

Procedure
Tip:
Perform the check on the EMS client and OMM client respectively.
In this topic, the operations on the OMM client are described. For
more information about the operations on the EMS client, refer to
ZXUN USPP Universal Subscriber Profile Platform EMS Operation
Guide (Daily Operation).
1. Log in to the OMM client and enter the NetNumen M30 main
interface.
2. On the main interface of NetNumen M30, choose Views >
Professional Maintenance from the menu to enter the Pro-
fessional Maintenance view.
3. In the navigation tree, choose the Data Maintenance >
Backup Task node. The Backup Task interface appears.
Check the auto-backup task of the NM configuration data and
the path of the backup files.
4. Check the data generated in the auto-backup path.
5. Dump and clear the backup files older than 3 months.
Criteria The backup files of NM configuration data are generated correctly.
For important operations such as network upgrade and cutover, the
configuration data should be backed up, and the backup filenames
should be clear and correct.


Chapter 5 Cautions for Routine
Maintenance
TABLE 1 CAUTIONS FOR ROUTINE MAINTENANCE
Operation Caution Possible Results Caused by Misoperation
Board-related Do not unplug online The data synchronization between active and
operations active board. standby boards requires a certain period when the
standby board works normally. When the active
board is unplugged online, the latest data on it
cannot be completely and automatically backed up
to the standby board, although the system will
switch over the boards automatically. It will easily
cause statistical errors and data loss.
When the standby board works abnormally, this
operation will interrupt all the service processing
of corresponding module, resulting in partial or
global service block in the system.
Do not press the A board will be implemented the hardware reset

RST button on the by force in case of the RST button on the board
board panel at will. panel being pressed. Only qualified maintenance
personnel can press it when serious fault occurs
in the system.
Pressing the RST button on the active board panel
will reset the active board. The consequence is the
same as that of "Unplugging online active board".
Do not plug and The electrostatic on human bodies may cause great
unplug boards damage to the components. If the maintenance
without wearing personnel plug or unplug boards without wearing
antistatic wrist antistatic wrist straps, the boards may suffer
straps. electrostatic damage easily. As a result, boards are
damaged or run unstably.
Cable-related Do not plug or This operation probably will interrupt services and the
operations unplug network communication between the front-end and back-end
cables inside the systems.
cabinet at will.
Power-supply- Do not operate the The maintenance personnel can operate various
related power switches on power switches by following operation procedure only
operations the cabinet at will. when serious fault occurs in the system, or during
network upgrade, network expansion, and component
replacement. This operation will stop system running
and interrupt services.


Glossary
3G
The 3rd Generation Mobile Communications
ATCA
Advanced Telecommunications Computing Architecture
BFD
Bidirectional Forwarding Detection
BOSS
Business and Operation Support System
CMM
Chassis Management Module
CPU
Central Processing Unit
DBIO
DataBase Input & Output
DSA
Directory System Agent
DST
Data Storage Transfer
EMS
Element Management System
FE
Front End
GPRS
General Packet Radio Service
ID
Identification/Identity/Identifier
IDSA
Identity DSA
IO
Input & Output
IP
Internet Protocol
KVM
Keyboard, Video and Mouse
LDAP
Lightweight Directory Access Protocol
M3UA
MTP3-User Adaptation layer protocol
MCH
MicroTCA Carrier Hub
MML
Man Machine Language

MTP3
Message Transfer Part layer 3
MTP3B
B-ISDN Message Transfer Part level 3
NTP
Network Time Protocol
OMM
Operation & Maintenance Module
OMP
Operation & maintenance Main Processer
PDSA
Profile DSA
SAS
Serial Attached SCSI
SMS
Short Message Service
SNTP
Simple Network Time Protocol
UDS
Universal Directory Server
VGA
Video Graphic Adapter
VRRP
Virtual Router Redundancy Protocol
XML
eXtensible Markup Language

ZXUN USPP Maintenance &amp; Troubleshooting-System Maintenance-Routine Maintenance-201008-80

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

ZXUN USPP Maintenance &amp; Troubleshooting-System Maintenance-Routine Maintenance-201008-80

Hochgeladen von

Copyright:

Verfügbare Formate

ZXUN USPP

Universal Subscriber Profile Platform

HLR Routine Maintenance

Copyright 2010 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Publishing Date (MONTH/DATE/YEAR) : 08/09/2010

HLR Routine Maintenance............................................. 1

will be able to:

Confidential and Proprietary Information of ZTE CORPORATION 1

Chapter 1 Routine Maintenance

After you have completed this chapter, you will know:

2 Confidential and Proprietary Information of ZTE CORPORATION

Grasp the running status of the equipment and network in real

Confidential and Proprietary Information of ZTE CORPORATION 3

Check spare components regularly to ensure they are sufficient

4 Confidential and Proprietary Information of ZTE CORPORATION

After you have completed this chapter, you will know:

2.1 Equipment Room Environment

Item Check the equipment room temperature.

2.1.2 Checking Equipment Room

Item Check the equipment room humidity.

Confidential and Proprietary Information of ZTE CORPORATION 5

2.2 Hardware System Check

2.2.2 Checking DSA Node Status

Item Check the DSA node status.

FIGURE 1 NETNUMEN M30 HLR MAIN INTERFACE

6 Confidential and Proprietary Information of ZTE CORPORATION

2. On the Watch Report interface as shown in Figure 1, right-

FIGURE 2 UDS TOPOLOGY OBSERVATION INTERFACE

FIGURE 3 DSA NODE STATUS

Confidential and Proprietary Information of ZTE CORPORATION 7

If the observation result shows that any DSA node is abnormal,

2.3 Checking System Alarms

2. On the main interface of NetNumen M30 HLR, enter the

FIGURE 4 FAULT MANAGEMENT VIEW

8 Confidential and Proprietary Information of ZTE CORPORATION

3. When checking the system alarms, the following five items

2.4 Performance Statistics Check

Item Check the MTP3 signaling links.

Confidential and Proprietary Information of ZTE CORPORATION 9

FIGURE 5 PERFORMANCE MANAGEMENT VIEW

3. Query the measurement task in measurement type MTP3 Sig-

4. Check the performance indices of the MTP3 signaling links dur-

10 Confidential and Proprietary Information of ZTE CORPORATION

2.4.2 Checking MTP3B Signaling Links

Item Check the MTP3B signaling links.

3. Query the measurement task in measurement type MTP3B

4. Check the performance indices of the MTP3B signaling links

2.4.3 Checking M3UA Signaling Links

Item Check the M3UA signaling links.

Confidential and Proprietary Information of ZTE CORPORATION 11

3. Query the measurement task in measurement type M3UA.

4. Check the performance indices of the M3UA signaling links dur-

2.4.4 Checking Processing Success

Item Check the processing success ratio of each basic service.

12 Confidential and Proprietary Information of ZTE CORPORATION

2. On the main interface of NetNumen M30 HLR, enter the Per-

3. Query the measurement tasks of the measurement type Basic

4. Check the processing success ratio of each basic service. Com-

2.4.5 Checking Processing Success

Item Check the processing success ratio of SMS.

Confidential and Proprietary Information of ZTE CORPORATION 13

Click the (Performance Management) button.

3. Query the measurement tasks of the measurement type SM

ZXUN USPP Maintenance & Troubleshooting-System Maintenance-Routine Maintenance-201008-80

ZXUN USPP Maintenance & Troubleshooting-System Maintenance-Routine Maintenance-201008-80