USPP(HLR)_SM001_E1_1

ZXUN USPP(HLR) Routine Maintenance

Targets

Master Daily Routine Maintenance

Master Weekly Routine Maintenance
Master Monthly Routine Maintenance
Master Warning of Dangerous Operations
Contents

Routine Maintenance Overview

Daily Routine Maintenance
Weekly Routine Maintenance
Monthly Routine Maintenance
Seasonal Routine Maintenance
Daily Maintenance Classification
Daily routine maintenance
Weekly routine maintenance
Monthly routine maintenance
Common Methods for Maintenance
Fault phenomena analysis
LED analysis
Signaling trace analysis
Alarm and log analysis
Instruments measurement analysis
Swap comparison method
Precautions in the Equipment Room

1. Keep the equipment room tidy

2. Do not execute any unrelated software on the system
3. Do not use PC terminal for any other purpose
4. Strictly manage passwords and periodically change it
5. Contact information of ZTE Corporation must be displayed at easily accessible place .

6. Backup data before making any changes to them.

7. Frequently check spare parts and components
8. Do not smoke, eat, play games, or browse the internet;
9. Keep the software and essential maintenance documentation at a convenient places.
Contents

Routine Maintenance Overview

Daily Routine Maintenance
Weekly Routine Maintenance
Monthly Routine Maintenance
Seasonal Routine Maintenance
Checking Temperature

In normal cases, the temperature in the equipment

room is 15C~25 C.

If the temperature is out of range, check

if air conditioner and other ventilation
equipments are working normally
Checking Humidity

In normal cases, the relative humidity in the

equipment room is 30%~70%.

Humidity readings should be done 1.5

meters above the ground and 0.4
meters in front of the device
Viewing Environment Alarms
Check the environment alarm indicator.

Indicator Corresponding Alarm Remark

RUN - It glows when subrack runs.
48VI - It is green when the direct current power is properly
connected.
48VII - It is green when the direct current power is properly
connected.
FAN Fan Alarm It glows when fan shelf is abnormal.
HOT Temperature/Humidity It glows when temperature/humidity is abnormal.
Alarm
Smoke Smoke alarm It glows when smoke is detected.
DOOR Entry control alarm It glows when somebody entering from the door or
window id detected.
ARRESTER Lightning Protection alarm It glows when lightning protection is available.
Checking Board Running Status
Check the status of each indicator light on each board.

Indicator Color Description

ALM Red Board alarm indicator. If it glows, that means board alarms exit.
Otherwise, that means the board has no alarms.
RUN Green Board running indicator. If it glows slowly, that means the boards run
normally.
ENUM Yellow Insertion/extraction (Offline) status indicator. If it glows, that means the
board is extracted.
ACT Green Active board indicator. If it glows, that means corresponding board is
active. Otherwise the board is standby.
Checking Board Running Status

Normal Results:
Each indicator on the front panel of the board works
normally and ALM light does not glow.
Each board has no alarm messages.
The boards without active and standby status are all in
active status.
The boards with active and standby status (for example,
MP) are in active status and standby status respectively.
Checking DSA Node Status
Checking DSA Node Status
Checking System Alarms

Current alarms, current alarm recovery

information, and current notices.

Check System alarms of the day before.

System alarms of the past 3 days.

Notices of the day before.

Notices of the past 3 days.
Checking System Alarms
Performance Statistics Check

The load is evenly shared among the signaling links.

The load of each M3UA signaling link should not exceed 0.2 Erl.

Checking Checking
Checking
MTP3B MTP3
M3UA
Signaling Signaling
Signaling
Links Links
Links

The load is evenly shared among the signaling links.

The load of 2M signaling link should not exceed 0.2 Erl,
The load of 64K signaling link should not exceed 0.4 Erl.
Performance Statistics Check

Checking
Processing
Success
Ratios of
Basic
Services
The processing success ratios in one
office should be stable with no obvious
fluctuation except on holidays.

Checking
Processing
Success
Ratios of SMS
Checking Call Losses of FE Modules
Make sure the FE modules do not have abnormal call losses.
Checking UDS Module Call Losses
Make sure the UDS modules do not have abnormal call losses.
Checking DST Network Status
Check the network adapter status.

Make sure the network adapters configured with floating IP addresses are "UP".
Checking DST Network Status

Check the network quality.

Make sure RX-ERR and TX-ERR in the statistics data are 0 or mostly 0.
 Log Check
Check the log files of each subsystem
in the /zxhlr/uds_offce ID_dump
Check the service logs in the node/log directory.
hlrinterlog\hlrmi_Module No.
folder of the IMP
Checking
IMP logs Checking
Check the DBIO 1. Open the installation directory
UDS logs
service logs in the of the Oracle database in the
log folder in the NMS server.
DBIO installation Checking
Checking 2. Check the log files in the
directory. DBIO logs
OMC logs \oracle\product\10.2.0\db_1\N
Checking
ETWORK\log directory.
FE logs
3. Check the alert*.log file in
the
\oracle\product\10.2.0\admin\
SID\bdump directory.
Contents

Daily Routine Maintenance

Weekly Routine Maintenance
Monthly Routine Maintenance
Checking FE Time

The FE time
and OMM time
are
synchronous.
Checking DBIO Disk Space Usage

The disk where the

OS is located (Disk There are no files
C) should have at Free space of other or folders irrelated
least 800M free disks should also be to the system.
space, and the free at least 20% of the Delete
space should be at total disk space. them if there are
least 20% of the any
total disk space.

DBIO Disk Space Usage

UDS Check
Checking Resource Occupancy of DSA Applications

Checking Resource Occupancy of DSA Applications

Make sure the
resource 1.
2. 3.
Query the DB
occupancy ratio Resource
Set querying
of DSA Start
conditions and info of each UDS
ToolsClient.exe, and
applications is choose the
then click OK to module. Check if
within the open the resource the module
DbManager function.
observation tool. status is normal.
normal range.
UDS Check
UDS Check

Checking Checking DST Checking DST

Capacity of Resource Disk Space Usage
U_OISDNCHG Occupancy

Use the probe to

check the
Run command top Run command df k
U_OISDNCHG
to check DST to check the DST
capacity and the
resource occupancy. disk space usage.
number of records
in the table.
UDS Check

Checking DST Run command free -m to check

Memory Usage the DST memory usage.

Checking Data Validity Run command ps ef|grep filecheck.

1. Check the status of RUN indicator.

(Normally, the status indicators of the disk array
should be green.)
Checking Disk Array
2. Check the status of Power indicators.
(Normally, the Power indicators of the disk array
should be green.)
OMC Server Check
The Disk C and the disk where the Oracle database is
located should have at least 800M free space, and the
Checking Hard Disk Occupancy free space should be at least 20%.
of NMS Server Free space of other disks should also be at least 20% of
the total disk space.

Checking Database Space Usage ratio of each table space in the NMS server database
Usage of NMS Server should be lower than 80%. Otherwise, contact ZTE technical
personnel for analysis.

Checking Virus Database Update Usage ratio of each table space in the NMS server database
of NMS Server should be lower than 80%. Otherwise, contact ZTE technical
personnel for analysis.

1. On the NMS server, click Start, then choose Programs >

Checking OS Logs in NMS Server Administrative Tools > Event Viewer.
2. Check the Application logs, Security logs and System
logs of one week. Focus on logs of alarm and error.
Performance Statistics Check
The number of subscribers should not
exceed the threshold set by the
License.

Checking
Processing
Checking Board Checking Server
Success
Load Load
Ratios of SMS &
Basic Services

The performance indices are within the normal range.

During the same busy hours, the indices are stable with no
obvious fluctuation.
Performance Statistics Check

Checking the The number of subscribers should not exceed the

Number of threshold set by the License.
Subscribers If the number reaches or gets close to the threshold,
apply to ZTE Corporation for a new license.

During the normal operation, the statistical objects

Checking
of the UDS consistency check should be 0.
UDS
If they are not 0, it means that some system data is
Consistency
missing. Contact ZTE technical personnel for help.
Contents

Daily Routine Maintenance

Weekly Routine Maintenance
Monthly Routine Maintenance
Performance Statistics Check

Normal results

The success ratios in one office should be

stable with no obvious fluctuation.

Processing Processing Processing

Success Ratio Success Ratios Success Success Ratios
of Service of Basic Ratios of of Packet
Provision Services SMS Services
Checking FE Version
Make sure the version of each FE module and board is consistent with
the OMM version.
Checking FE Version
Checking FE Version
ATCA Physical Environment Check

Checking
The difference of the temperature at the air
Shelf
intake and the room temperature should not
Temperature
be greater than 5 C.

For the systems with -48 V power supply, the rated

Checking DC
DC voltage of the rack is -48 V and the allowed range
Voltage
of fluctuation is -57 V~-40 V.
ATCA Physical Environment Check

Checking Checking
Heat CMM
Radiation System
of Racks Time

The dust filters are clean. Step:

The air intakes and
outtakes are not blocked.
The fans are working
normally.
The blank panels are fixed
well.
Run command telnet to log in
to the active CMM, and run
command date to check CMM
system time.
Criteria:
The CMM system time is
consistent with the local
standard time.
ATCA Physical Environment Check

Checking Checking
Switch Blade Server Blade
Voltage Voltage

Compare the current

voltage value with the Compare the current
voltage threshold of voltage value with the
each voltage sensor voltage threshold of
on the switch blade. each voltage sensor on
Check if the voltage the server blade. Check
values are all normal. if the voltage values are
all normal.
 ATCA Physical Environment Check
The rotation speed level is 7 and the
rotation speed is 4500-4600 rpm
when the system is working under
the normal temperature.

Checking Fan
Running Status
Compare the current
temperature value with the
temperature threshold.
Check if the temperature
values are all normal.
Checking Checking Rear
Server Blade Board of Server
Temperature Blade

The VGA monitor, PS/2 keyboard

and mouse of the server blade
work normally.
 Juniper Switch Check
1. Log in to the switch through ssh or telnet as
"user".
Checking 2. Run command show chassis environment.
Running Normal Result:
Status The "status" of Power, Temp and Fans of the
Juniper switch should all be "ok".

Juniper 1. Log in to the switch

Switch through ssh or telnet as
1. Log in to the switch Check "user".
through ssh or telnet 2. Run command show
as "user". chassis environment.
2. Run command show Checking Checking Normal Result:
bfd session. BFD Spanning The "state" of SW1,
Normal Result: Session Tree Protocol SW2, ae0.0 and ae1.0
The "status" of each Status Status should be "FWD".
interface address For SW3 and SW4, the
should be "up". current "state" of ae0.0,
ae1.0, ae2.0, ae3.0 and
ae4.0 should be "FWD".
Juniper Switch Check
1. Log in to the switch through ssh or telnet as "user".
Checking State 2. Run command show interfaces | grep "ge-|ae" | grep
of Physical and "Physical link is".
Aggregated Criteria
Interfaces The physical links of the connected ports should be "up".

1. Log in to the switch through ssh or telnet as "user".

Juniper 2. Run command show vrrp.
Checking Criteria
Switch VRRP Status Normally, the "VR state" of SW1 and SW3 should be
Check "master", and the "VR state" of SW2 and SW4 should
be "backup".

1. Log in to the switch through ssh or telnet as "user".

2. Run command show system uptime.
3. Check if the current time is consistent with the actual time.
Checking Time 4. Check if the system has been restarted or re-configured recently.
Criteria
The current time of the Juniper switch is consistent with the actual
time with an error of no more than 5 minutes.
Checking Auto-backup of NM Configuration Data

1. On the main interface of NetNumen M30, choose Views >

Professional Maintenance.
2. In the navigation tree, choose the Data Maintenance > Backup
Task node.
3. Check the data generated in the auto-backup path.
4. Dump and clear the backup files older than 3 months.

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.