Documente Academic
Documente Profesional
Documente Cultură
Routine Maintenance
Version 2.0.1.07
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 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 CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
201007-15
First edition
Contents
Figures ............................................................ 43
Tables ............................................................. 45
Glossary .......................................................... 47
II
Intended
Audience
Prerequisite Skill
and Knowledge
What Is in This
Manual
Maintenance engineer
To use this document effectively, users should have a general understanding of wireless telecommunications technology. Familiarity with the following is helpful:
ZXSS10SoftSwitch interfaces
Summary
Chapter
Routine
nance
2, Daily
Mainte-
This chapter describes the mandatory daily maintenance items required for the long-term, stable,
and effective running of SoftSwitch
Chapter 3, Weekly
Routine
Maintenance
Chapter 4, Monthly
Routine
Maintenance
Chapter 5, Yearly
Routine
Maintenance
Conventions
Chapter
Summary
Appendix A
Appendix B
Meaning
Italics
Quotes
Links on screens.
Bold
CAPS
II
Typeface
Meaning
Click
Doubleclick
Right-click
Declaration of RoHS
Compliance
To minimize the environmental impact and take more responsibility to the earth we live, this document shall serve as formal declaration that ZXSS10 SS1b manufactured by ZTE CORPORATION
are in compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with respect to the following substances:
Lead (Pb)
Mercury (Hg)
Cadmium (Cd)
II
Chapter
Maintenance Overview
Table of Contents
Device Maintenance Introduction ..........................................
Routine Maintenance Classification........................................
Working Flow of Routine Maintenance....................................
Precautions in Routine Maintenance ......................................
1
2
2
3
Device Maintenance
Introduction
Maintenance of the ZXSS10 SS1b is divided into the following three
parts.
1. Routine maintenance
According to maintenance cycle, ZXSS10 SS1b is divided into
daily routine maintenance and periodical routine maintenance.
The proper routine maintenance of the ZXSS10 SS1b system
is significant. It serves to check the running state of the device periodically and solve the detected problem in time, for the
purpose of detecting hidden troubles, preventing accidents, locating faults in time and conducting troubleshooting as early
as possible. For the details of routine maintenance of ZXSS10
SS1b, refer description of following chapters.
2. Notification and alarm
ZXSS10 SS1b is a powerful SoftSwitch product. Besides the
applications and service processing capacity, ZXSS10 SS1b is
also featured with the self-contained fault notification system
and functions, namely, alarms and notifications of ZXSS10
SS1b. To note that the system is configured with the automatic
error correction mechanism to handle some reported faults,
therefore no human involvement is needed. For details of
alarms and notifications of ZXSS10 SS1b, refer to the ZXSS10
SS1b Alarm and Notification Message Reference.
3. Troubleshooting
Troubleshooting refers to the process of analyzing, processing
and finally solving a fault after it is detected or relevant complaint is received. For more details, refer to the ZXSS10 SS1b
Troubleshooting Guide.
Routine Maintenance
Classification
Based on maintenance period, there are daily maintenance and
regular maintenance. Regular maintenance is divided into weekly
maintenance, monthly maintenance and annual maintenance.
Routine
maintenance
Regular Routine
Maintenance
4. Fill in Routine Maintenance Record and enclose a sheet to illustrate fault phenomenon, check methods and troubleshooting
in detail.
Precautions in Routine
Maintenance
1. Maintain normal temperature/humidity in equipment room.
i.
Keep environment tidy and clean, free from dust and moisture.
ii.
ii.
ii.
ii.
During maintenance operations, they must follow instructions described in related manual.
ii.
iii.
ii.
iii.
ii.
Spare parts must be separately preserved from those defective ones replaced during maintenance, labeled for distinction.
Chapter
Daily Routine
Maintenance
Table of Contents
Checking Equipment Room .................................................. 5
Viewing EMS Operation State ............................................... 6
Checking Database Server State........................................... 7
Checking Bearer Network State ............................................ 8
Checking System Alarms ..................................................... 9
Checking Board Operation State ..........................................11
Checking Trunk Circuit State ...............................................13
Checking MG State ............................................................14
Checking Traffic Statistics ...................................................15
Checking CDR Files ...........................................................16
Checking Data Auto-Backup ...............................................16
Checking EMS Security Status .............................................17
Checking System Security Status.........................................18
Reference
Standards
Relative humidity
(%)
1.
2.
Long-term working
condition
+5~+40
Short-term working
condition
(-5)~+50
Long-term working
condition
5%~85%
Short-term working
condition
5%~90%
If the relative humidity in the equipment room is too high, dehumidifiers should be used; otherwise, humidifying equipment
should be used.
Remove dust from equipment periodically. For more information, see Removing Dust.
Reference
Standards
Troubleshooting
Check EMS port status by netstat -an or telnet ip:port commands, including 21, 1433, 1521, 5000, 5432, 3306 and port
21099 21114.
Use the PING command to check if each servers network connection is normal.
ii. Perform optional query operations in the Configure Management window to see if the function is enabled. If so, it
indicates the database server functions normally.
The other way is as follows: Telnet to the database server and
log in it as root (default password: root). Use the ps ef|grep
out command to check the database servers all progresses.
Among the *.out progresses, the occurrence of all.out and
monitor.out (must be in operation state) indicates the database
servers all progresses function normally.
Reference
Standards
Troubleshooting
The occurrence of all.out and monitor.out progresses in operation state indicates the database servers all progresses function normally.
ii.
Reference
Standards
Troubleshooting
1. The NIC in SS side provides the external ports. Use the following troubleshooting way when an external device's IP address
is unreachable.
i.
ii.
ii.
3. If the bearer network fails, in general, related alarms indicating the link interruption appear in the alarm console. Check
the bearer network according to alarm prompts, and contact
maintenance personnel for troubleshooting. If necessary, contact ZTE technical experts for assistance.
Tip:
Click the
button from the toolbar to export alarms and store
them in Microsoft Excel, Adobe PDF, HTMF or text files.
Reference
Standard
Troubleshooting
10
Refer to ZXSS10 SS1b Alarm and Notification Message Reference for other faults handling.
Caution:
Troubleshoot the alarms once they occur, meanwhile, the service
personnel should report and records detailed alarm information for
fatal faults.
Board status
One way is to check each board's panel indicator. The other
way is to check the current alarms and see if there are alarms
indicating abnormal operating boards.
ii. Select the View CPU & Memory tab, and select a board's
module number from the list box. Enter the sampling interval in the Time Interval text box, which should be less
than 0.1 second. Click the Start button, the utilization of
and memory is displayed, as shown in Figure 3.
11
AND
MEMORY
Reference
Standards
12
ON
SC
Troubleshooting
The available space of SC's hard disk should not be less than
the partition or less than 30% of total hard disk space.
ii. Reset the board, then check if the board as well as services
returns to normal.
iii. Replace the board. Check if services are normal after the
board returns to normal.
iv. For problems that defy solution, contact ZTE technical experts for assistance.
For abnormal communication among boards, contact ZTE technical experts for assistance.
Perform the following steps if the usage rate of is too high for
a long time.
i.
1. In the Configure Management window, select Service Manage > Dynamic Data Management from the main menu,
entering Dynamic Data Management window.
2. In the Dynamic Data Management window, select Trunk
Circuit from Dynamic Data Type drop-down list, check the
state of trunk circuit, as shown in Figure 5.
13
Reference
Standards
Troubleshooting
Checking MG State
Maintenance
Guidance
1. Check TG state
2. Check SG state
3. Check AG state
Reference
Standards
Troubleshooting
14
OF
Troubleshooting
15
Reference
Standards
Troubleshooting
backup files: Check if the size of the daily backup CDR files
is greatly reduced than ever before, as well as if CDR files are
normally generated everyday.
Charging center's files: According to the on-site data configuration, check if the number of files in the charging server's
local memory disk is normal, if the file numbers are in series,
and if the size of files is normal.
16
Troubleshooting
If the data auto-backup functions abnormally, perform the following procedure for check:
1. Check if the auto-backup function is enabled.
2. Check if the backup path is correctly set.
3. Check if the disk space is sufficient.
4. If FTP backup fails, check the network and FTP setting.
1. In the NetNumenN31 Unified Network Management System window, right-select the NE, and select View > Security
Management from the menu bar to enter the Security Management interface. Then, select Role Management from the
Security Management Tree. Next, check the online user name
17
This check mainly involves the firewall log analysis, system path
upgrade and virus database updates for anti-virus software.
1. Check the firewall log and see if there are some policy bugs. If
so, modify policies in time.
2. Check if system has a latest patch. If not, upgrade it in time.
3. Check if the anti-virus software has a latest virus database. If
not, upgrade it in time.
Reference
Standards
Troubleshooting
Tip:
To boost the maintenance efficiency, it is suggested for the maintenance personnel to edit all MMLs applied to routine maintenance
into a script file. In such case, the script file can be executed in
batch mode.
18
Chapter
Weekly Routine
Maintenance
Table of Contents
Testing Non-Voice Services .................................................19
Checking System Charging ................................................19
Backing up Data Manually...................................................20
Backing up Charging Files ..................................................22
1. Mutually make calls on two phone sets, and media must pass
NGN gateway. Connect one fax machine respectively to two
phone sets to perform fax test.
2. Performing Modem test, connect two phone sets respectively
to PC with Modem to perform dialing test, and transmit a file
after call is connected.
Reference
Standards
Troubleshooting
Fax can be sent normally with words legible. In Modem test, file
must be transmitted normally.
1. Check if the terminal is normal.
2. Check if the configuration is normal.
3. Contact ZTE technical experts for assistance.
Reference
Standards
19
Troubleshooting
20
FIGURE 8 BACKING
UP
DATA MANUALLY
OF THE
Parameter
Description
Operation type
Backup Object
FTP
Database
21
ii.
Reference
Standards
Troubleshooting
Parameter
Description
according to the type of the backup
data.
Database backup
Database Recover
Select Charging > Settling and Totaling from the menu bar,
and click the Data backuping&restoring tab.
1. System data backup
In the System data backup&restore field, click the Backup
button to enter the System data backup&restore dialog box.
Then select a target disk, select the Maximum radio button
and click the Run button to backup data to MO or other external
memory facilities.
2. Charging data backup
22
23
24
Chapter
Monthly Routine
Maintenance
Table of Contents
Checking Time Synchronization ...........................................25
Backing up System Software ...............................................26
Checking Spare Materials and Parts......................................26
Checking Time
Synchronization
Maintenance
Guidance
Reference
Standards
Troubleshooting
25
Back up system software periodically. When path change and version update are involved, it is necessary to back up system software. A suggestion is to record system software program into
a disc, and still keep this program in the maintenance PCs designated directory. Note that the backup software version number must be consistent with the current-network software version
number.
Reference
Standards
System software backup is normal, and the backup version number is consistent with the current version number.
Reference
Standards
26
All spare products and parts must be kept well, without damages,
cracks and corrosion. The numbers are correct, and damaged or
replaced parts should be returned for repair in time.
Chapter
Yearly Routine
Maintenance
Table of Contents
Testing Diagnosis Function ..................................................27
Testing System Switchover .................................................28
Checking Cabinet Status.....................................................29
Removing Dust..................................................................29
1. In the NetNumenN31 Unified Network Management System window, right-click the NE, and select Diagnose Management from the pop-up menu. After the Diagnose Management window appears, click the Instant Test tab, then
the System Detect tab to check following contents.
i.
ii.
27
Reference
Standards
Caution:
For example, 1286:14,20080610: The module number represents the active SSN, and the password represents current
date.
module numb
For example, 1295:14,20080610: The module number represents the active NIC, and the password represents current
date.
28
password
SPC test: Power off the designated board and see if the
services can be smoothly switched over to the standby board.
Note that SPC boards must be configured in active/standby
mode.
The command format: 1213: module number,
password
For example: 1213:2,20080610.
Caution:
After the SPC switchover finishes, use the 1212 command to
boot SPCs.
Reference
Standards
The switchover for SCs, SSNs, and NICs is normal, without any service interruption. After the active SPC is powered off, the standby
SPC can smoothly take over services.
All cables should not have any damage, aging, erosion or electrical burn.
The cabinet top (inside) should not touch or hold any foreign
part. All rodent-resistant nets should be tightly binded and
have no damages.
Removing Dust
Maintenance
Guide
Use a dry, clean pledget to wipe the cabinet cover, and use
a vacuum cleaner to clean the area around the cabinet's air
intake.
ii. Remove the cabinet's air net, and wash it with water. Then,
install the dried air net into the cabinet bottom. For the
detailed operations, refer to the Installing, Removing and
29
Cleaning boards
Caution:
i.
Vacuum cleaner
Use a dry, clean anti-static soft brush to gently remove
the dust from the board surface; meanwhile, align the
vacuum cleaner's slot with the brush.
Advantages: simple operation and low cost; disadvantages: Dust cannot be thoroughly removed (the poisonous gas adhering to the boards still cannot be removed)
Detergent way
Use dedicated detergents (non-corrosive, non-conducting, high-volatility and anhydrous) to clean boards, like
IPA.
Advantages: thorough dust removal, most poisonous
gas can be removed from the board. Disadvantages:
relative complicated operations and higher cost
30
Warning:
Because SSNI boards in different shelves correspond to different S2 DIP switch settings, the maintenance personnel
must cautiously check the S2 DIP switch to ensure the accuracy.
Reference
Standards
All operation procedure must strictly follow the ESD prevention measures. For operations concerning the ESD
prevention desktop, the maintenance personnel must
wear ESD prevention coats and antistatic wrist straps.
The use of detergents must strictly follow related standards. Otherwise, invisible damages will be caused for
boards.
31
32
Appendix
Routine Maintenance
Record Tables
Table of Contents
Daily Routine Maintenance Record Table ...............................33
Weekly Routine Maintenance Record Table ............................35
Monthly Routine Maintenance Record Table ...........................36
Yearly Routine Maintenance Record Table ..............................37
Maintenance Condition
Temperature
normal
abnormal
Humidity
normal
abnormal
Dust proof
normal
abnormal
Fire fighting
normal
abnormal
Theft
protection
normal
abnormal
EMS
operation
state
EMS
operation
state
normal
abnormal
Database
server state
Database
server state
normal
abnormal
Equipment
room
environment
Maintenance
Signature and
Date
Remark
33
Maintenance Item
Maintenance Condition
Bearer
network state
Bearer
network state
normal
abnormal
System
alarm
System alarm
normal
abnormal
CPU and
memory
normal
abnormal
Remaining
hard disk
space in SC
normal
abnormal
Trunk circuit
state
normal
abnormal
MG State
normal
abnormal
Traffic
statistical
task state
normal
abnormal
Traffic
statistical
task result
normal
abnormal
CDR files
normal
abnormal
Data AutoBackup
Data AutoBackup
normal
abnormal
EMS security
condition
EMS security
condition
normal
abnormal
System
security
condition
System
security
condition
normal
abnormal
Board
operation
state
Trunk circuit
state
MG State
Traffic
statistics
CDR files
Alarm and
abnormal
phenomenon
handling
Residual
problems
34
Maintenance
Signature and
Date
Remark
Weekly Routine
Maintenance Record Table
TABLE 4 WEEKLY ROUTINE MAINTENANCE RECORD TABLE
Maintenance Item
Maintenance
Condition
Testing
voice
services
normal abnormal
Testing
nonvoice
services
normal abnormal
Checking
system
charging
Checking system
charging
normal abnormal
Backing
up data
manually
Backing
up data
manually
finished no
Backing
up
charging
files
Backing
up
charging
files
finished no
Testing
the
system
services
Maintenance
Personnel Signature
and Date
Remark
Alarm
and abnormal
phenomenon
handling
Residual
problems
35
Monthly Routine
Maintenance Record Table
TABLE 5 MONTHLY ROUTINE MAINTENANCE RECORD TABLE
Maintenance Item
Maintenance Condition
Time Synchronization
Time
Synchronization
normal
abnormal
System
software
backup
System software
backup
finished no
The storage
environment of
spare parts and
components
normal
abnormal
Number of
spare parts and
components
finished no
Spare
parts and
components
check
Alarm and
abnormal
phenomenon
handling
Residual
problems
36
Maintenance
Personnel
Signature and
Date
Remark
Maintenance
Condition
Diagnosis
test
Board
diagnosis
test
normal
abnormal
System
switchover test
System
switchover test
finished no
Cable
status
normal
abnormal
Cabinet
protection
normal
abnormal
Air conditioner(s)
finished no
Air filter
finished no
Fan shelf
finished no
Boards
finished no
Cabinet
status
check
Equipment dust
removal
Remark
Alarm and
abnormal
phenomenon handling
Residual
problems
37
38
Appendix
Unsafe Hardware
Operations
Main
Class
Sub Class
Board
operation
39
Main
Class
Sub Class
Cable operation
Power
operation
Random operations
on P power in the
cabinet and secondary power supply
are forbidden.
SSN Panel
Indicator
40
Name
Indicator
Description
MST
Green
On when SC is in
active state
RES
Green
On when SC is in
standby state
RUN
Green
FAU
Red
On when SC fails
Name
Indicator
Description
RUN
Green
Flashes at 1HZ; on
or off if SSN is in
abnormal state
FAU
Red
On if SSN fails
MST
Green
On if SSN is in active
state
RES
Green
On if SSN is in standby
state
SSNI Panel
Indicator
SPC Panel
Indicator
NIC Panel
Indicator
CSN Panel
Indicator
Name
Indicator
Description
PWR
Green
Name
Indicator
Description
RUN
Green
Flashes at 1HZ; on
or off if SPC is in
abnormal state
FAU
Red
On if SPC fails
Name
Indicator
Description
MST/RES
Green
On if NIC is in active
state; off if NIC is in
standby state.
FAU
Red
On if NIC fails
RUN
Green
Flashes at 1HZ
when NIC functions
normally.
Name
Indicator
Description
HL1
Yellow
On if CSN is working;
HL2
Red
On or flashes if CSN
fails
HL3
Green
Flashes if CSN is
working properly; on
or off if CSN is in
abnormal state
HL4
Green
On if CSN is in active
state; off if CSN is in
standby state
HL5
Green
On if CSN is in standby
state; off is CSN is in
active state
41
42
Figures
43
44
Tables
45
46
Glossary
AG
- Access Gateway
CDR
- Call Detail Record
CPU
- Central Processing Unit
EMS
- Element Management System
FTP
- File Transfer Protocol
NGN
- Next Generation Network
NIC
- Network Interface Card
PC
- Personal Computer
SC
- System Control (Card)
SG
- Signaling Gateway
SNTP
- Simple Network Time Protocol
SPC
- System Protocol Control (card)
SS
- Soft Switch
SSN
- System Switching Network (card)
TG
- Trunk Gateway
47