sjzl20091241-ZXMBW AGW (V3 (1) .08.10) Routine Maintenance PDF

ZXMBW AGW
WiMAX Wireless Access Gateway

Routine Maintenance
Version 3.08.10
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2006 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.
Revision History
Revision No. Revision Date Revision Reason

R1.0 03/26/2009 First Edition
Serial Number: sjzl20091241

Contents
Preface............................................................... i
Routine Maintenance Overview .........................1
Daily Maintenance Classifications ...................................... 1
Routine Maintenance Classifications .................................. 2
Essential Tools and Instruments ....................................... 3
Common Methods for Maintenance.................................... 4
Precautions in the Equipment Room .................................. 6
Daily Routine Maintenance ................................7
Checking Equipment Room Temperature ............................ 7
Checking Equipment Room Humidity ................................. 8
Checking Air Conditioner Running State ............................. 8
Check Environment Alarms .............................................. 9
Checking Board Running Status .......................................11
Checking Server Hardware..............................................13
Checking Communication between Foreground and
Background ..........................................................14
Checking Current Alarms ................................................17
Checking Operation Logs ................................................19
Checking LAN Hardware .................................................23
Weekly Routine Maintenance .......................... 25
Checking Input Voltage of Cabinet ...................................25
Checking Dust in Equipment Room...................................26
Checking Server Hard Disk Space ....................................26
Checking History Alarms.................................................28
Backing up Configuration Data ........................................29
Updating Anti-Virus Definitions in OMC Client ....................32
Monthly Routine Maintenance ......................... 35
Testing Active/Standby Boards Changeover .......................35
Analyzing Performance Statistical Data .............................38
Backing up Performance Statistical Data ...........................38
Seasonal Routine Maintenace .......................... 41
Testing Power Supply and Grounding Resistance ................41
Processing History Alarms...............................................42
Testing Basic Functions...................................................44
Figures ............................................................ 45
Tables ............................................................. 47
Maintenance Records ...................................... 49
ZXMBW AGW Daily Maintenance Records ..........................49
ZXMBW AGW Weekly Maintenance Records .......................53
ZXMBW AGW Monthly Maintenance Records ......................56
ZXMBW AGW Seasonal Maintenance Records.....................59
List of Glossary................................................ 63
Preface
Purpose This manual provides procedures and guidelines for Routine Main-
tenance of ZXMBW AGW.
Intended This manual is intended for engineers and technicians who perform
Audience operations on ZXMBW AGW.
Prerequisite Skill To use this guide effectively, users must have a general under-
and Knowledge standing of wireless telecommunications technology. Familiarity
with the following is helpful:
� ZXMBW AGW hardware structure
� Various components of ZXMBW AGW system
� Local operating procedures of ZXMBW AGW
What Is in This This guide contains the following chapters:
Guide
Chapter Summary
Chapter 1 Introduces routine maintenance

Overview for Routine Maintenance classification, tools required, and
recommended precautions for
routine maintenance of ZXMBW
AGW.
Chapter 2 Introduces the maintenance items

Daily Routine Maintenance for daily routine maintenance.

Weekly Routine Maintenance for weekly routine maintenance.

Monthly Maintenance for monthly routine maintenance.

Quarterly Maintenance for quarterly routine maintenance.
Appendix A Introduces maintenance records

Maintenance Records of ZXMBW AGW system.
Confidential and Proprietary Information of ZTE CORPORATION i

ZXMBW AGW Routine Maintenance
This page is intentionally blank.
ii Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
Routine Maintenance
Overview
Table of Contents
Daily Maintenance Classifications .......................................... 1
Routine Maintenance Classifications ...................................... 2
Essential Tools and Instruments ........................................... 3
Common Methods for Maintenance ....................................... 4
Precautions in the Equipment Room ...................................... 6
Daily Maintenance
Classifications
Description In terms of maintenance content, daily maintenance can be clas-
sified into three types, as introduced below:
� Routine maintenance
� Emergency maintenance
� Fault handling
Routine Routine maintenance is periodic maintenance done every day to
Maintenance check the running status of the equipment. Through daily main-
tenance, problems can be found and handled in time to avoid ac-
cidents.
Emergency Emergency maintenance refers to the maintenance done upon oc-
Maintenance curring of various alarm and notification messages during the run-
ning of the equipment.
Fault Handling Fault handling refers to handling various critical faults which can
not be located and removed according to single alarm and notifi-
cation message.
Confidential and Proprietary Information of ZTE CORPORATION 1

Routine Maintenance
Classifications
Description ZXMBW AGW routine maintenance for the system is divided into
two types in terms of the maintenance period.
� Daily routine maintenance
� Periodic maintenance
Daily Routine Daily routine maintenance refers to the maintenance operations
Maintenance done daily with comparatively simple procedure. These operations
can be done by normal maintenance personnel, such as check-
ing equipment room temperature, checking power supply system,
checking charging system, and checking alarm system. The pur-
pose of daily routine maintenance is to:
� Find the alarms given off by the equipment or existing imper-
ceptible faults and take proper measures to restore or trou-
bleshoot. Thus keep the normal running status of equipment
and reduce the fault rate of the equipment.
� Find and handle the abnormalities occurring during the running
of the charging system and the CDR system. Thus to avoid the
economic loss due to loss of CDR information.
� Acquire the running status of the equipment and the network,
in order to improve the efficiency of maintenance personnel in
handling emergencies.
Periodic Routine Periodic routine maintenance refers to the operations generally
Maintenance done by maintenance personnel who have undergone professional
training. The maintenance is done periodically and has compara-
tively complicated procedure, such as network management sys-
tem function check, remote maintenance check, and ground resis-
tance check. The purpose of periodic routine maintenance is to:
� Ensure the security, stability, and reliability of the system
through periodic maintenance on equipment.
� Find the natural aging, function unavailability, performance
degradation of equipment during running through periodic
check, backup, test and clean, and take proper measures to
handle the imperceptible risks and avoid accidents.
Periodic routine maintenance can be further classified into the fol-
lowing three types in terms of maintenance period.
� Weekly routine maintenance
� Monthly routine maintenance
� Seasonal routine maintenance
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Routine Maintenance Overview
Note:
Due to different site conditions and services, the maintenance
items mentioned in this manual may not be completely applica-
ble. Routine maintenance items can be self-set according to the
actual conditions on site.
Essential Tools and

Instruments
Necessary Tools Table 1 shows essential maintenance tools in the equipment room.
TABLE 1 ESSENTIAL MAINTENANCE TOOLS CHECKLIST
S. No Tool S. No Tool
Crimping
Tape 14
1 pliers
Screw drivers (flat-head and Phillips,

Electric
one piece for each type respectively in 15
iron, 40W
2 large, medium and small sizes)
Clamp
Tweezers 16
3 pincers
4 Adjustable wrench 17 Plate puller
Antistatic
Diagonal pliers 18
5 wrist strap
Insulation
Sharp-nose pliers 19
6 tape
7 Cable peeler 20 Cable tie
8 Scissors 21 Pliers
Straight-through cable (the length Telephone

22
9 depends on the actual requirement) line
Serial port line (connecting routers or

23
10 Ethernet switches)
Dustproof
Dehydrated alcohol 24
11 paper
Insulating
Solder wires 25
12 tapes
2M self-
Cable ties 26
13 loop lines

Instruments and Table 2 shows instruments and measurement tools required in the
Meters equipment room.
TABLE 2 INSTRUMENTS AND METERS
Category Device
Environment monitoring 1. Thermometer

meters and instruments 2. Hygrometer
1. Digital multimeter
Maintenance instruments and 2. Earth resistance tester
meters 3. Signaling meter
4. Notebook PC (laptop)
Miscellaneous Burner
Note:
All instruments and meters must be checked and calibrated appro-
priately to ensure that they are in good condition.
Necessary Table 3 shows instruments and measurement tools required in the

Software equipment room.
TABLE 3 ESSENTIAL SOFTWARE
Software Product Used
Operating System Windows 2003 Enterprise Edition
Database System SQL 2005 Server Enterprise
Operating System
SP2 for Windows 2003
Patch
Database System
SP2 for SQL 2005
Patch
McAfee Enterprise (recommended) Norton

Antivirus software
Enterprise
Version software CDROM consistent with the

Version Software
currently running version
Common Methods for

Maintenance
Description There are some common methods for system maintenance. Select
proper methods based on practical situation to locate and solve the
problems efficiently and quickly.

Chapter 1 Routine Maintenance Overview
Faults Phenomena Normally, network equipment contains several entities. Every en-
Analysis Method tity shows different phenomena when faults occur. When mainte-
nance personnel discover faults or receive the faults report, they
can analyze the faults phenomena and judge which entity has cre-
ated this phenomenon. Thus, they can focus on the faulty entity.
This method can avoid performing wrong operations to normal en-
tities and save solving time.
LED Analysis To help users to know the running status of equipment, most
Method equipment has status reporting LEDs. For example, most boards
in foreground have status LED to indicate the running status of
the board. Some boards have fault LED to indicate whether this
board is faulty. Some boards have power supply LED to indicate
whether the power supply is normal. Some boards have flashing
LED to indicate whether the board is working normally. The
background server has power supply LED and fault LED.
The status of LEDs helps to locate the faults and even to analyze
the cause.
Signaling Trace Signaling trace tool is provided by system to analyze and locate
Analysis Method the faults. From the signaling trace tool, it is very easy to know
whether the signal flows, messages, and the parameters in mes-
sage are right or not. Analyzing this information helps to find out
the root causes.
Alarm and Log System records the faulty information and important parameters
Analysis Method during working. The faulty information and important parameters
are recorded in the log file of foreground, log record file of back-
ground server, and alarm database (including version application
program log and system log).
Through analyzing log files and information in alarm database,
maintenance personnel find out the root causes of the faults cor-
rectly and discover the hidden trouble.
Instruments Instruments measurement method is the common method to an-
Measurement alyze the faults. Maintenance personnel can measure the system
Analysis Method working index and environmental index. Then compare the results
with those in normal situation to analyze the causes of the differ-
ences.
Swap Comparison Swap the suspicious faulty component with normal one. If the
Method problem is solved after swapping, the problem can be located eas-
ily.
This method is easy and efficient. Maintenance personnel can also
compare the status, parameters, and log files of the same compo-
nent to find out the differences.
Note:
This method should be performed at the same time (0.00-
6.00am).

Precautions in the
Equipment Room
Work Regulations Work regulations in the equipment room are as follows:
� Keep the equipment room tidy, clean, and in proper order;
� Change shoes at the door and keep the equipment room free
of dust;
� Lay out terminals properly and ensure relevant tools are in
their proper place;
� Do not execute any unrelated software on the system;
� Do not use PC terminal for any other purpose;
� Strictly manage passwords and periodically change it. Disclose
passwords to authorized personnel only;
� Backup data before making any changes to them. Do not
delete the backup data until the equipment runs properly for
some period after changing the data (normally for a week).
Record any change to the data in time;
� Frequently check spare parts and components to ensure the
sufficient in amount, and are free from being damped, or
mildewed. Keep them away from faulty ones removed during
maintenance. Clearly label them and replace them when out
of stock;
� Do not smoke, eat, play games, or browse the internet;
� Keep the software and essential maintenance documentation
at a convenient place;
� Put on antistatic wrist strap before performing any operation
on the equipment;
� Contact information of ZTE Corporation must be displayed at
easily accessible place. Inform all the maintenance personnel
so that they can contact ZTE Corporation when necessary. Up-
date the contact information regularly.
Note:
Before modifying and synchronizing the data, make sure that per-
sonnel in charge approve it. Modifying data at ones discretion may
cause major accidents.
Shift Regulations Shift regulations in the equipment room are as follows:

� Clearly define shift handover formalities to ensure smooth tran-
sition of shift responsibilities;
� Provide clear information to the maintenance personnel arriv-
ing for the next shift by the on duty maintenance personnel;
� During shift handover, the equipment running state, condition
of tools, and instruments must be clear. Documented records
must be complete.

Chapter 2
Daily Routine
Maintenance
Table of Contents
Checking Equipment Room Temperature ................................ 7
Checking Equipment Room Humidity ..................................... 8
Checking Air Conditioner Running State ................................. 8
Check Environment Alarms .................................................. 9
Checking Board Running Status ...........................................11
Checking Server Hardware..................................................13
Checking Communication between Foreground and Back-
ground.............................................................................14
Checking Current Alarms ....................................................17
Checking Operation Logs ....................................................19
Checking LAN Hardware .....................................................23
Checking Equipment Room

Temperature
Prerequisites Thermometer is available and is calibrated appropriately.
Context Ensure normal temperature in equipment room to meet the re-
quirements for equipment running and to maintain the equipment.
Steps 1. Read the numeric value from thermometer.
2. Check if the temperature taken from the recommended range
of 0℃ ~ 40℃.
Note:
Temperature reading should be done 2 meters above the
ground and 0.4 meters in front of the device. Temperature
must not be beyond the range of 0℃ ~ 40℃ . Operation time
of the device must not exceed 48 hours with the temperature
ranges of -5℃ ~ 0℃ and 40℃ ~ 45℃ and accumulated oper-
ation time with these temperature ranges should not exceed
15 days in a year.
END OF STEPS

Postrequisite If the temperature is out of range, check if air conditioner and

other ventilation equipments are working normally.
Checking Equipment Room

Humidity
Prerequisites Hygrometer is available and is calibrated appropriately.
Context Ensure normal humidity in equipment room to meet the require-
ments for optimum running of the system and to maintain the
equipment.
Steps 1. Read the numeric value from a hygrometer.
2. Check if the humidity taken from the hygrometer is within rec-
ommended range.
END OF STEPS
Result Checking for humidity in the equipment room is complete.
Note:
The normal relative humidity should be within 20% ~ 90%. Hu-
midity readings should be done 2 meters above the ground and 0.4
meters in front of the device. Relative humidity must not be be-
yond the range of 20% ~90%. Operation time of the device must
not exceed 48 hours with the humidity of less than 5% ~20% and
within the range of 90% ~95% and accumulated operation time
with these humidity ranges should not exceed 15 days in a year.
Postrequisite If the humidity is out of range, check air conditioner and other
ventilation equipment are working normally.
Checking Air Conditioner

Running State
Prerequisites Hygrometer and thermometer are available and are calibrated ap-
propriately.
Context Ensure the proper running of air conditioner in equipment room
to meet the requirements for normal equipment running and to
maintain the equipment.
Steps 1. Check equipment room temperature.
Refer to Checking Equipment Room Temperature.
2. Check equipment room humidity.

Chapter 2 Daily Routine Maintenance
Refer to Checking Equipment Room Humidity.

The air conditioner runs normally and parameters are set cor-
rectly.
END OF STEPS
Postrequisite Repair the air conditioner immediately if it is not working properly.

If the capacity is not up to requirements, add more air conditioners
or increase the power.
Check Environment Alarms

Prerequisites � OMC works normally.
� The communication between the foreground and the back-
ground is normal.
Context Check the environment alarm indicator on the front panel of the
power subrack and the alarm messages in OMC network manage-
ment system, check whether there is infrared, smog, temperature
and humidity alarms.
Steps 1. Check the environment alarm indicator on the front panel of
the power subrack. If the lights marked with FAN, HOT, Smoke,
Door, and Arrester are red, further check corresponding envi-
ronment sensor.
The power subrack in the cabinet has the function of displaying
environment alarms. The front panel of the power subrack has
eight indicator lights, for details, refer to Table 4.
TABLE 4 INDICATORS ON FRONT PANEL OF POWER SUBRACK
Indicator Corresponding Alarm Remark
RUN - It glows when subrack runs.
- It is green when the direct current power is prop-

48V I
erly connected.
- It is green when the direct current power is prop-

48V II
erly connected.
FAN Fan Alarm It glows when fan shelf is abnormal
Temperature/Humidity
HOT It glows when temperature/humidity is abnormal.
Alarm
Smoke Smoke alarm It glows when smoke is detected.
It glows when somebody entering from the door

DOOR Entry control alarm
or window is detected.
ARRESTER Lightning Protection alarm It glows when lightning protection is available.

2. In OMC main window, click Views > Fault Management, and

check whether there is environment alarms in real-time alarm
monitor list, as shown in Figure 1.
FIGURE 1 CURRENT ALARM WINDOW
END OF STEPS
Result � Normally, the environment alarm indicator on the front panel

of the power subrack is not glowing.
� In OMC platform, the alarm messages do not include infrared,
smoke, temperature and humidity alarm messages.
Postrequisite When environment alarms occur, remove the alarms referring to
the following steps:
� When infrared alarm occurs, check whether unauthorized peo-
ple or animals entered the equipment room, or check whether
somebody enters the equipment room from monitored doors
and windows. If necessary, close infrared alarm through fault
management system to remove the alarm messages.

� When smoke alarm occurs, check the equipment room environ-

ment immediately and determine the alarm source and take
proper measures. After that, in fault management system,
click Clean Smoke Alarm to remove the alarm message.
� When temperature/humidity alarm occurs, check current tem-
perature and humidity in the equipment room. If the temper-
ature and the humidity exceeds the permitted range, check
whether the air-conditioner runs normally. For details, refer to
air-conditioner user guide.
� If the temperature and the humidity are in permitted range but
the alarm still exists, check whether the settings for temper-
ature and humidity is reasonable, referring to the method of
measuring temperature and humidity.
Checking Board Running

Status
ground is normal.
Context Check the running status of boards and the alarms and notifica-
tions associated with boards.
Steps 1. Check the status of each indicator light on each board of the
service subrack. When the boards work normally, the green
RUN light on the front panel of the boards glows in a frequency
of once per second; ACT light glows always, and ALM and ENUM
lights keep going out.
For functions of indicators on the front panel of a board, see
Table 5.
TABLE 5 INTRODUCTION TO INDICATORS ON BOARDS
Indicator Color Description
ALM Red Board alarm indicator. If it glows, that

means board alarms exist. 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.

2. Check whether there is alarm on boards through OMC network

management platform. In OMC network management system,
select Views > Daily Maintenance > Rackchart Manage-
ment to open the rackchart window, as shown in Figure 2.
FIGURE 2 RACKCHART
In Figure 2, if a board runs abnormally, corresponding slot in

the rackchart is displayed in a color matching with the alarm.
The colors on a board indicate alarms of different levels, as
shown in Table 6.
TABLE 6 CORRESPONDENCE BETWEEN ALARM COLORS AND ALARM LEVELS
Alarm Color Alarm Level Remark
Cyan No alarm The board runs normally and is active.
Blue No alarm The board runs normally and is standby.
The board has serious fault and should be handled im-

Red Emergency Alarm
mediately.
The board has major fault and should be handled at

Orange Important Alarm
once.

Alarm Color Alarm Level Remark
Yellow Common Alarm The board has common alarms and needs handling.
Grey Unknown Status No board is installed in this slot.
END OF STEPS
Result Generally, a board running normally meets the following condi-

tions:
1. Each indicator on the front panel of the board works normally
and ALM light does not glow.
2. Each board has no alarm messages.
3. The boards without active and standby status are all in active
status.
4. The boards with active and standby status (for example, MP)
are in active status and standby status respectively.
Postrequisite If a board has alarms, the detailed alarm information can be
queried through current alarm and history alarm windows of
Alarm Management, so that the alarm messages can be handled
in time.
When a board has severe fault causing service interruption, the
board can be replaced as emergency handling.
Checking Server Hardware

Prerequisites The server is running.
Context If the server has hardware fault, the services may be interrupted.
Check the server hardware through the alarm indicators on the
front panel of the server.
Steps 1. Open the front door of the server cabinet to check the in-
dicators on the front panel of the server, check whether the
alarm indicators for each server and the magnetic disk array
are glowing or whether the power light gets out.
2. Check the status of each network port (or optical port) on the
rear panel of the server.
3. Check the running status of server fans.
4. Use the hardware checking tool self-contained in the operating
system of the server to check the working condition of the
hardware.
END OF STEPS
Result � Each server and magnetic disk array run normally and no alarm
lights are glowing or the power light is glowing.
� Server fans run normally and give off no abnormal sound.
� When network port is normally connected, the ACT light at the
network port is always glowing; When data is transmitted, the
ACT light flashes frequently.

� The working status of all hardware must be normal.

Postrequisite If the server has abnormality, take the following measures to han-
dle the abnormality.
� If alarms for one power of all servers or magnetic disk arrays
(servers and magnetic disk arrays are configured to have two-
way power module) of a server occur, then it may indicate the
power in one way is faulty. In this case, check the indirect
current power system. There is two-way power indicator at the
front upper end of the server cabinet, if one green indicator for
the power goes out, that surely indicates power problems. If
any alarm light glows, check the power supply.
� If fans provide no wind or give off abnormal sound, contact
ZTE technicians to check the server fans.
Note:
At present, servers on site generally are from a third party. For
details about each indicator on servers, see the technical materials
delivered with servers.
Checking Communication
between Foreground and
Background
� AGW foreground works normally.
Context The communication between the foreground and the background
refers to the communication between foreground AGW and back-
ground OMC. When the communication between the foreground
and the background is interrupted, the background OMC can not
maintain and manage the foreground AGW and AGW can not re-
port alarms and performance statistical information to OMC.
Steps 1. In OMC network management window, click Views > Daily
Maintenance > Dynamic Management > Route Dianosis
> PING to open the window as shown in Figure 3.

FIGURE 3 PING WINDOW
2. Set the source address and destination address of PING tool in

Source Address and Destination Address sections in Figure
3, and set the PING times, packet size, and time-out time.
After that, execute Ping command.
For example, as shown in Figure 4, set Source Address as
the IP address of the local OMC server 128.0.31.129, set the
Destination Address as the IP address of the OMC-2 port of
OMP board of AGW 128.0.31.5. After that, click Add to add
the addresses to Ping list and click Ping command to start ping.

FIGURE 4 EXAMPLES TO USE PING TOOL
END OF STEPS
Result Generally, if Ping command is used at the OMC server and the
IP address of the foreground OMP is reachable, and no packets
are dropped or delayed, then it indicates normal communication
between the foreground and the background.
Postrequisite If the communication between the foreground and the background
is abnormal, the system runs normally within a short time. But the
running status of the foreground can not be acquired at the back-
ground, and the operations by the background on the foreground
can not be accomplished. Handle the problem referring to the fol-
lowing measures.
1. Remove the background server faults.
� Check whether the power supply for the background server
is normal.
� Check whether the power supply for the background server
hardware is normal.

� Check whether the background server has viruses.

� Check whether the operating system of the background
server and the network management database is normal.
� Check whether the operating and maintenance system of
OMC runs normally.
� Check the settings for the network adapter of OMC.
If one or more causes mentioned above lead to the faults, re-
place the faulty parts, remove the viruses, or restart the server
depending on the causes.
2. Remove physical link faults.
If the ping command fails, it means the physical connection is
faulty. In this case, check the working conditions of network
cables, Ethernet switch, and network adapter.
3. Check the running status of each board at the foreground, and
test whether services are abnormal.
Checking Current Alarms

� AGW foreground works normally.
Context Current alarm messages provided by OMC present current fault
information in real time. In daily maintenance, it is necessary to
check current alarms and remove the causes in time.
Steps � Log on to OMC system, and select Views > Fault Manage-
ment > Realtime Alarm Monitor to check whether there is
current alarms in Realtime Current Alarms tabbed section.
Realtime Alarm Monitor provides various ways to conduct
real-time alarm monitoring, as shown in Figure 5.

FIGURE 5 REALTIME ALARM MONITOR
Figure 5 window provides four ways to conduct real-time mon-

itoring.
� Composite Alarm Monitor, which reflects real-time
alarms in broken line graph (or bar graph) combining with
alarm list.
� Chart Monitor, which represents alarms in forms of bro-
ken line graph or bar graph according to alarm types.
� Realtime Alarm Monitor, which reflects alarms in alarm
list.
� Realtime Notification Monitor, which reflects alarms in
alarm list.
END OF STEPS
Result Normally, no Critical and Major alarms occur.

Postrequisite If critical alarms occur, handle the alarms according to the infor-
mation provided in the the alarm messages and also utilizing sig-
naling tracing, log management, and dynamic management tools.

For specific operations, see ZXMBW AGW WiMAX Wireless Access

Gateway Alarm Management Guide.
Checking Operation Logs

ground is normal.
Context OMC operation log contains operation information of users logging
on OMC, including User Name, Rank, Operation Set, Host Address,
Command Function, Detailed Information, Operation Result, Failed
Reason, Connection Mode, Operation Resource, Operation Start
Time, Operation End Time, and Related Log.
Through checking operation log, the managers can check the op-
erations done by users after logging on OMC system.
Steps 1. In OMC system, select Views > Log Management to open
the window as shown in Figure 6.

FIGURE 6 LOG MANAGEMENT
In Figure 6, log management tool provides the management

functions for operation log, security log, and system log.
� Operation Log
contains user operation information, including User Name,
Module, Operation Set, Host Address, Command Function,
Detailed Information, Operation Result, Failed Reason,
Connection Mode, Operation Resource, Operation Start
Time, Operation End Time, and Related Log.
� Security Log
Contains operations meeting security event rules, includ-
ing User Name, Host Address, Log Name, Operation Time,
Connection Mode, and Detailed Information.
� System Log
contains the timing task completion information of the
server, including Rank, Operation Resource, User Name,
Detailed Information, Host Address, Operation Start Time,
Operation End Time, and Related Log.

2. In Figure 6, click the left operation log to check corresponding

log record.
For example, in , click Log Tree Operation LogToday Op-
eration Log, the log list for current day appears, as shown in
Figure 7.
FIGURE 7 TODAY OPERATION LOG
3. Double-click the required record from the log list to check the
detailed information of the log.
For example, double-click the desired record as shown in Figure
7, the detailed content of the log appears, as shown in Figure
8.

FIGURE 8 DETAILED INFORMATION
END OF STEPS
Result 1. The operation log has no content regarding invalid or unautho-

rized operations.
2. The security log has no content regarding invalid login.
Postrequisite If there is abnormality log, make clear who did the operation and
why he did the operation. Pay special attention to invalid opera-
tions, which may cause unexpected result.

Checking LAN Hardware

Context This topic describes the procedure to check LAN equipment for
daily routine maintenance.
Steps 1. Check indicators on switch and router is normal.
2. Check network setting are correct.
3. Check network cable connection with server/maintenance con-
sole.
4. Use ping command to test the connection.
Note:
In the case of multiple switches in cascade connection, make
sure no loop exists.
END OF STEPS
Result The procedure for checking LAN hardware is complete.

Postrequisite If in any abnormality found,take the measures according to prob-
lems and causes listed in Table 7.
TABLE 7 PROBLEMS AND CAUSES
Problem Cause
Accounting system fails to collect

bills in real time. Router is faulty.
Running indicators are giving alarm. Router or SWITCH is faulty.
Running indicators are OFF. Power failure.
Indicator on switch or router shows

normality, but the indicator for a port
shows abnormality. Port is faulty.
Indicator for the port is OFF. Connection node is faulty.
Frequency of indicator for a port on Indicates a large traffic or virus

SWITCH is increased. infection.
In dual-network communication be-

tween network is abnormal. One SWITCH is faulty.


Chapter 3
Weekly Routine
Maintenance
Table of Contents
Checking Input Voltage of Cabinet .......................................25
Checking Dust in Equipment Room.......................................26
Checking Server Hard Disk Space ........................................26
Checking History Alarms.....................................................28
Backing up Configuration Data ............................................29
Updating Anti-Virus Definitions in OMC Client ........................32
Checking Input Voltage of

Cabinet
Prerequisites � Power cables are properly connected.
� The equipment in the cabinet works normally.
Context Various cabinets may utilize different input currents and voltages.
Therefore, check the voltage of the input power every week to
ensure that the input voltage is within the permitted range.
� Direct current power with voltage of –48V is utilized in cabinets.
� Indirect current power with voltage of 220V is utilized in server
cabinets.
Steps 1. Perform the following steps to check the voltage of cabinets
using direct current power.
i. Open the rear door of the cabinet.
ii. Measure the voltage between –48V and –48V GND, and be-
tween –48V and PE connector using the multi-instrument.
iii. Check the measured voltage value.
2. Perform the following steps to check the voltage of server cab-
inets using indirect current power.
i. Open the rear door of the server cabinet.
ii. Measure the voltages between the phase line and zero line,
and between the phase line and the earth line of the power
outlet.
iii. Check the measured voltage value.

For cabinets utilizing two-way powers, additionally measure

the voltages of the input power of the left and right circuits.
END OF STEPS
Result Generally, the measured voltage of cabinet meets the following

conditions:
� The direct current voltage is within the normal scope, that is,
within -57V~-40V.
� The indirect current voltage is within the normal scope, that is,
within 220V±10%.
Postrequisite � If the direct current voltage exceeds the normal range, then
it can be said that the input power of corresponding rack is
abnormal. So it is necessary to check the direct current power
system before led into the cabinet.
� If the indirect current exceeds the permitted range, check the
indirect current power system before led into the cabinet.
Checking Dust in Equipment

Room
Prerequisites Put on an anti-static wrist strap before starting up with the proce-
dure.
Context Check level of dust in equipment room. Because presence of dust
on PC and boards brings damage. Too much dust may result in
short-circuit. So, in weekly maintenance, it is necessary to clean
the dust in equipment room to ensure the normal working status
of devices.
Steps 1. Check dust condition of cabinet and server surface.
2. Clean the cabinet, server, and surrounding environment with a
vacuum cleaner if dust is present.
END OF STEPS
Result There is no dust present in the equipment room.
Checking Server Hard Disk

Space
Prerequisites � OMC server is running normally.
� The communication between OMC server and the client is nor-
mal.

Chapter 3 Weekly Routine Maintenance
Context When the hard disk of OMC server has insufficient space, the run-
ning speed of the equipment slows down, which may cause equip-
ment faults. Therefore, check the hard disk space periodically for
insufficient disk space and to avoid equipment faults.
KLinux operating system is utilized for OMC server, the tools pro-
vided with KLinux can be used to check the hard disk space of OMC
server.
Steps 1. In OMC server, enter MML Terminal mode of KLinux and log in
as root users.
2. Type in df after the command prompt. The hard disk space
information of OMC server is displayed, as shown in Figure 9.
FIGURE 9 THE RESULT OF COMMAND
The Use% column in presents the percentage of hard disk

space used by each file system.
END OF STEPS
Result Generally, the available space for OMC server/boot folder should
be above 15 GBytes.
Postrequisite OMC server provides the method of checking the hard disk space
of OMC server. The operations are as follows:
1. In OMC window, click Views > System Management to open
System Management window.
2. In System Management window, click View corresponding
to Server Performance section to view the usage of CPU,
memory, and hard disk of OMC server, as shown in Figure 10.

FIGURE 10 SERVER INFORMATION
Checking History Alarms

� The login subscribers have history alarm query authority.

Context History alarms are the alarms of the system occurred in the past.
These alarms may have been removed, or still exist. So many
history alarms with identical content can be queried in the alarm
bank if the alarms last a certain period.
Steps � In the main window of the network management client, click
Views > Fault Management. The Fault Management win-
dow appears. In Query History Alarms, select all modules,
all alarm levels, and the time period from previous day to cur-
rent time.
END OF STEPS
Result Normally, history alarms do not include the alarms of Critical and
Major levels.
Postrequisite For detailed operations on history alarms, see ZXMBW AGW WiMAX
Wireless Access Gateway Alarm Management Guide
Backing up Configuration
Data
ground is normal.
Context Back up data before and after configuration data is modified, in
order that configuration data can be recovered in shortest period
when the system is abnormal due to errors caused by misopera-
tions.
Steps 1. In OMC system, select Views > Daily Management to open

FIGURE 11 DAILY MAINTENANCE WINDOW
2. In Daily Maintenance window, click Data Maintenance >

Backup/Restore > Backup Configuration Data in the left
navigation tree. Backup Configuration Data window ap-
pears as shown in Figure 12.

FIGURE 12 BACKUP CONFIGURATION DATA
The parameters in Figure 12 are described in Table 8.
TABLE 8 PARAMETERS IN DATA BACKUP WINDOW
Parameter Description Example
Back up the configuration data to corresponding

Server
directory of server.
Back up the configuration data to corresponding In this example, select

Client
directory of the client. Client
The backup configuration data are divided into

Backup Con- three types, Common Configuration Data, IP
tent Stack Configuration Data, and Common and
IP Stack Configuration Data.
Type in the file name and directory of the backup

File Path D:\BACKUP.ZIP
files.
After the backup starts, the backup progress is

Guage
displayed.

3. Input the parameters according to the example in Table 8, and

click Apply to start backup.
4. After the backup is complete, a message appears to prompt
the success.
END OF STEPS
Result 1. Data is backed up.

2. The backup files are alternatively saved in an offline storage
media (such as optical disk) except being saved in the main-
tenance console.
3. The name of the backup file should contain data or time infor-
mation for future check.
Postrequisite � Check whether the configuration data is backed up every time
it is modified. Back up configuration data at least once every
week.
� If no backup file is found, perform the backup procedure again.
Caution:
It is necessary to back up configuration data before and after the
data is modified.
Updating Anti-Virus
Definitions in OMC Client
Prerequisites � OMC client works normally.
ground is normal.
Context At present, OMC client utilizes Windows operating system. The
anti-virus definitions needs constant real-time updating to detect
newer malware.
Steps � If OMC client is installed with McAfee Enterprise anti-virus soft-
ware, perform the following operations:
i. Right-click in the status bar of the OMC clientand select
VirusScan Enterprise > On-Demand Scan to scan all
files.
ii. Right-click in the status bar of the OMC client and se-
lect VirusScan Enterprise > Update Now to update anti-
virus in time.
� If OMC client is installed with Norton anti-virus software, per-
form the following operations:
i. Run Norton AntiVirus to scan all local hard disks and skill
virus.

ii. Run Norton AntiVirus and click Liveupdate to update anti-

virus, or manually download latest anti-virus from Internet.
END OF STEPS
Result Normally, OMC client has no virus, and the anti-virus software has
the latest virus definitions.


Chapter 4
Monthly Routine
Maintenance
Table of Contents
Testing Active/Standby Boards Changeover ...........................35
Analyzing Performance Statistical Data .................................38
Backing up Performance Statistical Data ...............................38
Testing Active/Standby
Boards Changeover
Prerequisites � OMC server is in working status.
ground is normal.
Context In standard configuration for AGW, two SMP boards are configured,
one is active board, and the other is standby board. When the
active SMP board fails to work (or is pulled out), the standby board
automatically takes over all jobs of the original active board to act
as the active board.
SMP changeover includes normal changeover and forced
changeover. Normally, normal changeover is used. But forced
changeover is used when the active SMP is faulty and causes
changeover failure.
Steps 1. In OMC system, select Views > Daily Management to open

FIGURE 13 DAILY MAINTENANCE
2. In Daily Maintenance window, click Rackchart Manage-

ment. Figure 14 is the schematic diagram for partial rackchart
and shows the distribution of boards in BPSN shelf of a rack.
FIGURE 14 BOARD RACKCHART
3. Right-click the board to be changed over, and select Show

CPU Status and Changeover, and Reset from the pop-up

Chapter 4 Monthly Routine Maintenance
shortcut menu, and right-lick the CPU to be switched over, the

window occurring is as shown in Figure 15.
FIGURE 15 SELECTING CHANGEOVER TYPE
4. Normally, Normal Changeoveris selected. During

changeover, changeover process is displayed.
END OF STEPS
Result � Normally, the active and standby SMP boards changeover is

successful.
� After changeover, the service functions of AGW are tested to
be normal.
Postrequisite If the changeover fails, the communication between the active and
standby SMP boards may be interrupted, or the standby SMP is
abnormal. In this case, corresponding alarms occur. Handle the
alarms according to the alarm content.
If the changeover is successful but some functions seem to be
abnormal, it may be caused due to asynchronous data between
the active and standby boards. In this case, synchronize total
table to the foreground to correct this error.

Warning:
Board changeover is somewhat dangerous, so changeover test
is necessarily done when the traffic is low enough, for example,
within 0:00 6:00.
Analyzing Performance
Statistical Data
ground is normal.
Context Performance statistical function provided by
OMC can be used to enquire any variation of service abilities of the
system. Generally, system performance statistical data regularly
varies with time. To acquire information about the running status
of entire system, perform performance statistical operation once
every month to observe the variation of each item.
Steps 1. In OMC network management window, select menu Views >
Performance Management.
2. Open the performance statistical module to collect and analyze
each important running index during last week.
END OF STEPS
Result Normally, each index is within the required scope and varies little
compared with latest index.
Postrequisite If an index varies greatly some day, further collect the detailed
data during that day (querying by smaller granularity), and deter-
mine the cause for the abnormality according to the specific event
occurring on that day. For example, determine whether network
fault exists, or whether network structure varies. To create or
query performance statistical tasks in Performance Management
window, see ZXMBW AGW WiMAX Wireless Access Gateway Per-
formance Management Guide; To understand and analyze perfor-
mance data, see ZXMBW AGW WiMAX Wireless Access Gateway
Performance Measurement Item Reference.
Backing up Performance
Statistical Data
Prerequisites � OMC server works normally.

Chapter 4 Monthly Routine Maintenance

ground is normal.
Context Back up performance statistical data to save the history perfor-
mance statistical data in local disk in file form.
Steps 1. In OMC network management window, click Views > MML
Terminal.
2. In MML Terminal window, click MML Command > System
Maintenance > Performance And Alarm Data Mainte-
nance > Backup Data > Backup Performance Data, the
window varies as shown in Figure 16.
FIGURE 16 BACKING UP PERFORMANCE DATA
3. In Command Execute Result tabbed section, type in file

name, file path, Network Element ID, backup mode, and start-
ing/ending time. And then click Execute (F5).
END OF STEPS

Result Performance statistical data is normally backed up. The backup

file name appears in the destination folder.

Chapter 5
Seasonal Routine
Maintenace
Table of Contents
Testing Power Supply and Grounding Resistance ....................41
Processing History Alarms...................................................42
Testing Basic Functions ......................................................44
Testing Power Supply and

Grounding Resistance
Prerequisites � Wear antistatic wrist strap.
� Make sure that the plug of the strap connects securely to static
discharging hole on top of front cabinet panel.
� Switch on power supply.
� Perform test between 00:00 AM and 06:00 AM.
� Keep properly working multi-meter and other testing tools
ready.
Context Power supply level is very important for proper functioning of
equipment. Low or high power supply levels may damage the
equipment.
Steps 1. Open the rear door of switching cabinet.
2. Find the input power terminals.
3. Use a multimeter to check AC and DC voltage between each
-48V input and ground, and between each -48V input and pro-
tection ground.
4. Check multimeter reading.

Note:
DC voltage should be -48 V in ideal case. It should be close to
-48 V. Voltage must be with in range of -40 V to -57 V.
Allowed range for AC voltage: -57 V ~ -40V. AC work voltage:
220 ± 10%, 50 Hz ± 5%.
5. Check whether the grounding resistance is up to the require-

ment, which should be lower than 1 Ohm.
6. Check the power line connection.
END OF STEPS
Result Checking power supply is complete.
Processing History Alarms

Prerequisites OMC server runs normally.
Context History alarm data is stored in corresponding data table of OMC
database. Users can delete history alarm data of the last season
to reduce the load of the database.
Steps 1. In OMC network management window, click Views > MML
Terminal.
2. In the MML command tree on the left of MML Terminal win-
dow, click MML Command > System Maintenance > Per-
formance And Alarm Data Maintenance > Clean Data >
Delete Alarm Data, the window varies as shown in Figure 17.

Chapter 5 Seasonal Routine Maintenace
FIGURE 17 DELETE ALARM DATA WINDOW
3. In Delete Alarm Data window, select the deletion mode, set

the start and end times and the alarm level. After that, click
Execute (F5).
END OF STEPS
Postrequisite Remove the history notification data and performance statistical

data during a period using similar method.

Note:
Before performing deletion, back up the history alarm data (or
notification data, performance statistical data) utilizing Backup
Data function to store the history alarm data in other computers.
Testing Basic Functions

Prerequisites � OMC server works normally.
ground is normal.
Context Check basic services of AGW to ensure normal running of basic
services.
Steps � User a mobile terminal to access to Internet or other service
operations associated with WIMAX, check the service functions
of ZXMBW AGW, including route forwarding function, session
management function, application layer service, NTP function,
IP address management function, charging function and other
auxiliary service functions.
END OF STEPS
Postrequisite If basic services are found to be running abnormally, check

whether the mobile terminal is normal and then try to locate the
faults. If this fails, contact ZTE technicians for further handling.
Note:
Contact ZTE technology support center or customer service line as
shown below:
� ZTE Global Custom Support Center Hotline:
(0755) 26770800
800-8301118
400-8301118
� ZTE technology support website: http://support.zte.com.cn
� Customer service mailbox: 800@zte.com.cn

Figures
Figure 1 Current Alarm Window ...........................................10

Figure 2 Rackchart.............................................................12
Figure 3 PING Window .......................................................15
Figure 4 Examples to Use PING Tool .....................................16
Figure 5 Realtime Alarm Monitor..........................................18
Figure 6 Log Management...................................................20
Figure 7 Today Operation Log ..............................................21
Figure 8 Detailed Information..............................................22
Figure 9 The result of command ..........................................27
Figure 10 Server Information ..............................................28
Figure 11 Daily Maintenance Window ...................................30
Figure 12 Backup Configuration Data ...................................31
Figure 13 Daily Maintenance ...............................................36
Figure 14 Board Rackchart ..................................................36
Figure 15 Selecting changeover Type....................................37
Figure 16 Backing up Performance Data ...............................39
Figure 17 Delete Alarm Data Window ...................................43


Tables
Table 1 Essential Maintenance Tools Checklist ......................... 3

Table 2 Instruments and Meters ........................................... 4
Table 3 Essential Software ................................................... 4
Table 4 Indicators on Front Panel of Power Subrack ................. 9
Table 5 Introduction to Indicators on Boards .........................11
Table 6 Correspondence between Alarm Colors and Alarm
Levels ..............................................................12
Table 7 Problems and Causes ..............................................23
Table 8 Parameters in Data Backup Window ..........................31
Table 9 ZXMBW AGW Daily Maintenance Records ...................49
Table 10 ZXMBW AGW Weekly Maintenance Records...............53
Table 11 ZXMBW AGW Monthly Maintenance Records .............57
Table 12 ZXMBW AGW Seasonal Maintenance Records ............59


Appendix A
Maintenance Records
Table of Contents
ZXMBW AGW Daily Maintenance Records ..............................49
ZXMBW AGW Weekly Maintenance Records ...........................53
ZXMBW AGW Monthly Maintenance Records ..........................56
ZXMBW AGW Seasonal Maintenance Records.........................59
ZXMBW AGW Daily

Maintenance Records
ZXMBW AGW daily maintenance records are as shown in Table 9.
TABLE 9 ZXMBW AGW DAILY MAINTENANCE RECORDS
ZXMBW AGW Daily Maintenance Records
Office name Date MM-DD-YY
On-duty time Till o’clock Off-duty person On-duty person:
Basic check items
1. Check whether the board indicator is normal.

Open the front door of the front-end cabinet, and check whether each board
has red-indicator alarm (check the module).
□ Normal □ Abnormal
Abnormality Description

2. Check whether the board indicator is normal.

Open the front door of the server cabinet, and check whether server alarms
exist; Switch over the servers to check whether the program running abnormality
alarm prompt section occurs in the window.
3. Check the alarm messages of each module

In the maintenance terminal, open Daily Maintenance window, a schematic diagram
of the rack panel appears on the right rack diagram. Check whether there is any
alarm (Level-1 alarm is denoted by red, Level-2 alarm is denoted by orange, Level-3
alarm is denoted by yellow, and Level-4 alarm is denoted by blue). The active state
is denoted by green. The standby state is denoted by light blue. The mixed state is
denoted by light cyan. The unknown state is denoted by light purple.
4. Query the operation log in OMC

Check the system log, operation log, and security log.
5. Check the hardware of the LAN.

Check HUB, router, firewall and the connected network cables or optical fibers.

Appendix A Maintenance Records
6. Check the temperature and humidity of the equipment room.

7. Check the running status of the air-conditioner in the equipment room.

8 Check operation log

In Log Tree of Log Management window, select Operation Log, set searching items and
start/end dates as needed. After that, click OK and check whether abnormal users did
abnormal operations
9 Check other items ( )


10 Check other items ( )

Duty memo
Fault and handling

Unresolved problems
Checked by supervisor on-duty:
ZXMBW AGW Weekly

Maintenance Records
ZXMBW AGW weekly maintenance records are as shown in Table
10.
TABLE 10 ZXMBW AGW WEEKLY MAINTENANCE RECORDS
ZXMBW AGW Weekly Maintenance Records
Office name Date MM-DD-YY
Maintenance Item

1. Updating the latest virus definitions and scan virus.

When updating latest virus definitions or scanning virus for OMC client, select
scanning before deleting files. This is to avoid deletion of useful files, which may
cause system faults and services may get interrupted.
Maintenance result:
Maintenance personnel: Time:
2. Server file system space, the free space for /boot folder must not be less then 5G.
Delete useless files. But for useful files while useless for normal running of the
system, back up them before deleting them. Ensure the free space for /boot
folder of KLinux system is not less than 5G.
Maintenance result:
3. Checking History Alarms

Maintenance result:
4. Backing up Configuration Data

For configuration data without modified, back up the data every week.
Maintenance result:

5. Checking Input Voltage of Cabinet

Maintenance result:
6. Check the dust in the equipment room.

Maintenance result:
7 Other checking items ( )

Maintenance result:


Maintenance result:

Maintenance result:
Maintenance memo
Problems and solutions:
Unresolved problems
ZXMBW AGW Monthly

Maintenance Records
ZXMBW AGW monthly maintenance records are as shown in Table
11.

TABLE 11 ZXMBW AGW MONTHLY MAINTENANCE RECORDS
ZXMBW AGW Monthly Maintenance Records
Office name: Date MM-DD-YY
Maintenance Item
1. SMP switchover test

Maintenance Result:
Maintenance Personnel: Time:
2. OMP switchover test

Maintenance Result:
3. Produce monthly statistics table as needed. Back up performance

statistics database once every month
Maintenance Result:

4. Other checking items

Maintenance result:
5. Other checking items

Maintenance result:
Maintenance memo

Unresolved problems
ZXMBW AGW Seasonal

Maintenance Records
ZXMBW AGW seasonal maintenance records are as shown in Table
12.
TABLE 12 ZXMBW AGW SEASONAL MAINTENANCE RECORDS
ZXMBW AGW Seasonal Maintenance Records
Office name: Date MM-DD-YY
Maintenance Item
1. Clean the history alarm data of last season

Maintenance Result:

2. Clean the history notification data of last season

Maintenance Result:
3. Clear the history performance data of last season

Maintenance Result:
4. Test each basic function of the system

Maintenance Result:

5. Test power supply and ground resistance

Maintenance Result:
Maintenance memo
Unresolved problems:


List of Glossary
AGW - ASN Gateway ASN

ASN - Access Service Network
ASP - Application Service Process
CSN - Connectivity Services Network
ENUM - Enumeration
ISP - Internet Server ProviderInternet
NSP - Network Service Provider
NTP - Network Time Protocol
OMC - Operations & Maintenance Center
WiMAX - Worldwide Interoperability for Microware Access

sjzl20091241-ZXMBW AGW (V3 (1) .08.10) Routine Maintenance PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

sjzl20091241-ZXMBW AGW (V3 (1) .08.10) Routine Maintenance PDF

Transféré par

Droits d'auteur :

Formats disponibles

ZXMBW AGW

WiMAX Wireless Access Gateway

Copyright © 2006 ZTE CORPORATION.

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

Revision No. Revision Date Revision Reason

Serial Number: sjzl20091241

Chapter 1 Introduces routine maintenance

Chapter 2 Introduces the maintenance items

Chapter 3 Introduces the maintenance items

Chapter 4 Introduces the maintenance items

Chapter 5 Introduces the maintenance items

Appendix A Introduces maintenance records

Confidential and Proprietary Information of ZTE CORPORATION i

This page is intentionally blank.

ii Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 1

2 Confidential and Proprietary Information of ZTE CORPORATION

Essential Tools and

TABLE 1 ESSENTIAL MAINTENANCE TOOLS CHECKLIST

Screw drivers (flat-head and Phillips,

4 Adjustable wrench 17 Plate puller

7 Cable peeler 20 Cable tie

Straight-through cable (the length Telephone

Serial port line (connecting routers or

Confidential and Proprietary Information of ZTE CORPORATION 3

TABLE 2 INSTRUMENTS AND METERS

Environment monitoring 1. Thermometer

Necessary Table 3 shows instruments and measurement tools required in the

TABLE 3 ESSENTIAL SOFTWARE

Software Product Used

Operating System Windows 2003 Enterprise Edition

Database System SQL 2005 Server Enterprise

McAfee Enterprise (recommended) Norton

Version software CDROM consistent with the

Common Methods for

4 Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 5

Shift Regulations Shift regulations in the equipment room are as follows:

6 Confidential and Proprietary Information of ZTE CORPORATION

Checking Equipment Room

Confidential and Proprietary Information of ZTE CORPORATION 7

Postrequisite If the temperature is out of range, check if air conditioner and

Checking Equipment Room

Result Checking for humidity in the equipment room is complete.

Checking Air Conditioner

8 Confidential and Proprietary Information of ZTE CORPORATION

Refer to Checking Equipment Room Humidity.

Postrequisite Repair the air conditioner immediately if it is not working properly.

Check Environment Alarms

TABLE 4 INDICATORS ON FRONT PANEL OF POWER SUBRACK

Indicator Corresponding Alarm Remark

RUN - It glows when subrack runs.

- It is green when the direct current power is prop-

- It is green when the direct current power is prop-

FAN Fan Alarm It glows when fan shelf is abnormal

Smoke Smoke alarm It glows when smoke is detected.

It glows when somebody entering from the door

ARRESTER Lightning Protection alarm It glows when lightning protection is available.

Confidential and Proprietary Information of ZTE CORPORATION 9

2. In OMC main window, click Views > Fault Management, and

FIGURE 1 CURRENT ALARM WINDOW

Result � Normally, the environment alarm indicator on the front panel

10 Confidential and Proprietary Information of ZTE CORPORATION