SG7000 Maintenance Manual-Emergency Maintenance PDF

Chapter 1 Classification of Emergent Faults ................................................
1-1
1.1 Definitions of Emergent Faults ...............................................................

1.1.1 Equipment Fault .............................................................................
1.1.2 Extremely Heavy Traffic Fault ........................................................
1.2 Basic Principles of Emergency Maintenance .........................................
1-1
1-1
1-2
1-3
Chapter 2 Emergency Maintenance Flow ......................................................
2-1
2.1 Overview of Emergency Maintenance Flow ...........................................

2.1.1 Overall Flow ...................................................................................
2.1.2 Collecting Fault Information ...........................................................
2.2 Handling Equipment Fault ......................................................................
2.2.1 Handling Breakdown of Cabinet or Frame .....................................
2.2.2 Handling BAM Breakdown .............................................................
2.2.3 Handling Restart of Equipment ......................................................
2.3 Handling Extremely Heavy Traffic Fault .................................................
2-1
2-1
2-4
2-5
2-5
2-6
2-8
2-9
Chapter 3 Related Operations of Emergency Maintenance .........................
3-1
3.1 Power-on Operations .............................................................................

3.1.1 Powering On and Restarting Cabinet ............................................
3.1.2 Powering On and Restarting Frames.............................................
3.2 Pulling Out and Inserting Boards............................................................
3.3 Resetting Operations..............................................................................
3.3.1 Resetting Frames...........................................................................
3.3.2 Resetting Boards ...........................................................................
3.4 Backing Up and Recovering Database ..................................................
3.4.1 Automatic Backup of Database......................................................
3.4.2 Manual Backup of Database ..........................................................
3.4.3 Safe Data Recovery .......................................................................
3-1
3-1
3-2
3-3
3-5
3-5
3-6
3-6
3-6
3-8
3-12
Appendix A Record Tables of Emergency Maintenance .............................
A-1
A.1 Emergency Maintenance Note...............................................................

A.2 Troubleshooting Record Table...............................................................
A-1
A-3
Appendix B Power Supply System of Cabinet ..............................................
B-1
B.1 Power Supply Loop of Power Distribution Frame ..................................

B.2 Power Supply Loop Inside Cabinet ........................................................
B-1
B-1
Appendix C Acronyms and Abbreviations ....................................................
C-1
Index .................................................................................................................
HUAWEI
U-SYS SG7000 Signaling Gateway

Maintenance Manual Emergency Maintenance
V200R001
Huawei Technologies Proprietary

Maintenance Manual
Volume
Emergency Maintenance
Manual Version
T2-010348-20050530-C-2.00
Product Version
V200R001
BOM
31033848
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
Copyright 2005 Huawei Technologies Co., Ltd.
All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any
means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET,
, ViewPoint, INtess, ETS, DMC,
TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA,
iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE,
OpenEye, Lansway, SmartAX, infoX, TopEng are trademarks of Huawei
Technologies Co., Ltd.
All other trademarks mentioned in this manual are the property of their respective
holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents,
but all statements, information, and recommendations in this manual do not
constitute the warranty of any kind, express or implied.
About This Manual

Release Notes
This manual applies to U-SYS SG7000 Signaling Gateway V200R001.
Organization
The manual describes the maintenance principles, emergency maintenance tasks
and operations of SG7000 V200R001.
There are three chapters and three appendixes in the manual.
z
Chapter 1 Classification of Emergent Faults introduces the definitions of the

emergent faults and basic principles of emergency maintenance.
Chapter 2 Emergency Maintenance Flow introduces the flows for processing

emergency faults, such as BAM breakdown, cabinet breakdown, and so on.
Chapter 3 Related Operations of Emergency Maintenance elaborates the

operations relevant to the emergency maintenance of the equipment.
Appendix A Record Tables of Emergency Maintenance gives some samples

for recording the emergency maintenance operations.
Appendix B Power Supply System of Cabinet introduces the power supplies

used in the SG7000.
Appendix C Acronyms and Abbreviations lists the abbreviations and

acronyms used in this manual and the corresponding full expressions.
Intended Audience
The manual is intended for the following readers:
z
Engineering personnel
Telecom administration personnel
Maintenance personnel
Conventions
The manual uses the following conventions:
I. General conventions
Convention
Description
Arial
Normal paragraphs are in Arial.
Boldface
Headings are in Boldface.
Courier New
Terminal Display is in Courier New.
II. GUI conventions

Convention
Description
<>
Button names are inside angle brackets. For example, click

the <OK> button.
[]
Window names, menu items, data table and field names are
inside square brackets. For example, pop up the [New User]
window.
Multi-level menus are separated by forward slashes. For

example, [File/Create/Folder].
III. Mouse operation

Action
Click
Description
Press the left button or right button quickly (left button by
default).
IV. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Caution, Warning, Danger: Means reader be extremely careful during the

operation.

Note, Comment, Tip, Knowhow, Thought: Means a complementary
description.

Table of Contents
Table of Contents
Chapter 1 Classification of Emergent Faults.............................................................................. 1-1
1.1 Definitions of Emergent Faults........................................................................................... 1-1
1.1.1 Equipment Fault ...................................................................................................... 1-1
1.1.2 Extremely Heavy Traffic Fault ................................................................................. 1-2
1.2 Basic Principles of Emergency Maintenance .................................................................... 1-3
Chapter 2 Emergency Maintenance Flow ................................................................................... 2-1
2.1 Overview of Emergency Maintenance Flow ...................................................................... 2-1
2.1.1 Overall Flow ............................................................................................................ 2-1
2.1.2 Collecting Fault Information .................................................................................... 2-4
2.2 Handling Equipment Fault ................................................................................................. 2-5
2.2.1 Handling Breakdown of Cabinet or Frame.............................................................. 2-5
2.2.2 Handling BAM Breakdown ...................................................................................... 2-7
2.2.3 Handling Restart of Equipment ............................................................................... 2-9
2.3 Handling Extremely Heavy Traffic Fault .......................................................................... 2-10
Chapter 3 Related Operations of Emergency Maintenance ...................................................... 3-1
3.1 Power-on Operations......................................................................................................... 3-1
3.1.1 Powering On and Restarting Cabinet ..................................................................... 3-1
3.1.2 Powering On and Restarting Frames...................................................................... 3-2
3.2 Pulling Out and Inserting Boards ....................................................................................... 3-3
3.3 Resetting Operations ......................................................................................................... 3-5
3.3.1 Resetting Frames .................................................................................................... 3-5
3.3.2 Resetting Boards..................................................................................................... 3-6
3.4 Backing Up and Recovering Database.............................................................................. 3-6
3.4.1 Automatic Backup of Database............................................................................... 3-6
3.4.2 Manual Backup of Database ................................................................................... 3-8
3.4.3 Safe Data Recovery .............................................................................................. 3-12
Appendix A Record Tables of Emergency Maintenance...........................................................A-1
A.1 Emergency Maintenance Note ..........................................................................................A-1
A.2 Troubleshooting Record Table ..........................................................................................A-3
Appendix B Power Supply System of Cabinet ...........................................................................B-1
B.1 Power Supply Loop of Power Distribution Frame .............................................................B-1
B.2 Power Supply Loop Inside Cabinet ...................................................................................B-1
Appendix C Acronyms and Abbreviations .................................................................................C-1
Index ................................................................................................................................................ i-1

i

Chapter 1 Classification of Emergent Faults

Emergency maintenance is a series of emergency measures used to minimize the
loss, remove the fault, and recover the system or equipment when emergent faults
happen.
1.1 Definitions of Emergent Faults

1.1.1 Equipment Fault
An equipment fault is a severe fault which causes the loss of most of or all the
functions of the equipment.
I. Breakdown of Cabinet or Frame

Any of the following situations might result in the breakdown of a frame, cabinet, or
even the whole system.
z
The power-off of the basic cabinet (cabinet 0) or master service frame (frame 0 of
the basic cabinet) leads to the breakdown of the whole system.
The simultaneous breakdown of the active and standby HSYS boards of the
master service frame leads to the breakdown of the whole system.
The simultaneous breakdown of the active and standby HSYS boards of the
slave service frame leads to the breakdown of the service frame.
Note:
In the default delivery configuration, the basic cabinet refers to cabinet 0, the master
service frame refers to frame 0 of the basic cabinet, and the slave service frame refers
to all the service frames excluding the master service frame.
II. BAM Breakdown

BAM breakdown is a severe fault with the loss of all BAM functions. In the actual
applications, any of the following situations is regarded as a kind of BAM breakdown:
z
Power failure of the BAM.
Unable to start the BAM.
Automatic and frequent resetting of the BAM.
The CPU utilization of the BAM keeps near 100% for a long time.
The Windows operating system of the BAM breaks down during the operation or
it is unable to boot when the BAM starts.
1-1

z
Abnormal running of the BAM Manager". For example, unable to start the BAM
Manager, unable to start all the service processes (their statuses are "Stopped"),
or all the service processes enter the Exception state after being started
repeatedly.
III. Restart of Equipment

When one of the following situations occurs, you need to restart the equipment:
z
You need to load a batch of data to the equipment.
You need to power on the equipment again after powering it off for other
reasons.
You find that the data in the host and the BAM are not consistent, and cannot
recover the data through the commands.
IV. Accidental Power Failure to Board

When a board is working normally, it may be powered off if you press the red locker on
the ejector lever accidentally. When one of the following situations occurs, the board
is powered off:
If the blue hot-swap indicator on the front panel of the board is on or all the indicators
on the front panel of the board are off, the board is powered off.
Open the system navigator window on the left of the maintenance console. Select
[System Setting/Board Position Management]. If the indicator of the board is red, the
board is powered off or faulty. For details about whether a board is faulty, refer to
U-SYS SG7000 Signaling Gateway Maintenance Manual Parts Replacement
Guide.
After a board is accidentally powered off, power it on again by pulling out and inserting
it again. For details, refer to section 3.2 Pulling Out and Inserting Board in this
manual.
1.1.2 Extremely Heavy Traffic Fault

Extremely heavy traffic may cause congestion to links, SLPU, SBPU, or HSYS, which
results in mass congestion to all links or boards. The following situations lead to
extremely heavy traffic faults:
z
The CPU utilization rises sharply, often to above 50%.
Corresponding loading alarms of links are generated. Sometimes, a large

number of TransFer-Forbidden signal (TFP) and TransFer-Allowed signal (TFA)
messages frequently appear on links, causing the frequent switchover of the
links.

1-2

1.2 Basic Principles of Emergency Maintenance

The emergent faults are dangerous and can cause call congestion and equipment
breakdown. In order to increase the efficiency of handling the emergent faults and
minimize the loss, be sure to know the following basic principles before maintaining
the equipment:
z
The core of emergency maintenance is to recover the system operations and

service provisioning as soon as possible. To promote the efficiency of handling
the emergent faults, you need to set up handling schemes for various emergent
faults according to the emergency maintenance manuals and practice
periodically.
You must attend the emergency maintenance training which is mandatory for
maintenance personnel. You must learn the basic methods of judging emergent
faults and learn how to handle emergent faults.
When there is an emergent fault, check whether the equipment and the bearer
network are working normally. Then you need to judge whether the emergent
fault is caused by the equipment. If yes, you can handle the fault according to the
pre-prepared schemes or the procedures in this manual.
When emergent faults happen to the BAM, you are forbidden to reinstall the
system or format the hard disk on the BAM before consulting Huawei for
technical support to avoid the loss of some important data.
In order to get quick technical support when handling an emergent fault, you
need to contact the customer service center (see page 2 of the cover of this
manual) or the regional office of Huawei.
After handling an emergent fault, you need to collect the alarm information
related to this fault and send the fault handling report, equipment alarm files and
log files to Huawei for analysis. By doing this, you can help Huawei improve the
after-sales services.

1-3

Chapter 2 Emergency Maintenance Flow

2.1 Overview of Emergency Maintenance Flow
This chapter describes the handling flow for emergency maintenance to help you
cope with emergent faults. In case of an unexpected alarm or fault, you need to stay
calm, observe the alarm or fault, and record it properly.
2.1.1 Overall Flow

The ultimate purpose of emergency maintenance is to recover system operations and
service provisioning as soon as possible. The overall flow is as shown in Figure 2-1.
Start
1
Collecting fault
information
No
Hardware Ok?
Yes
Bearer
network Ok?
No
Yes
4
Handling
equipment fault
Handlng bearer
network fault
Handling extremely
heavy traffic fault
Fault solved?
No
Collecting fault
information
Yes
8
Collecting fault
information
9
Reporting for
analysis
Figure 2-1 Overall flow for handling emergent faults

2-1
Reporting for
Help

I. Collecting Fault Information

When emergent faults happen, you need to collect as much information as possible
from fault complaints, alarms from the network management system (NMS), and by
checking the equipment and making dial tests. This will provide a basis for the
subsequent processing.
II. Checking Hardware Equipment

Hardware defaults often cause service congestion. For example, a frame breakdown
will lead to service congestion. Therefore, to improve the efficiency of fault handling,
you must check if the hardware equipment is running normally before taking any
measures to solve an emergent fault. Common methods of checking the hardware
equipment are as follows:
z
Check if the power supply to the equipment is normal. That is, check if the power
supply to the cabinet, components within the cabinet, and frames is normal.
Check if the components, including the LAN Switch and BAM, in the basic
cabinet run normally.
Check if the frames run normally. In the system navigation window of the client,
select System Settings -> Board Position Management. Observe the running
statuses of the boards (front boards, back boards, and subboards), power frame,
and fans.
III. Checking Bearer Network

If the service congestion occurs when the hardware equipment runs normally, first
check if the bearer network runs normally. Common methods of checking the bearer
network are as follows:
z
Check if there is any transmission fault alarm for the alarm management system.
Use the ping command to check if the connection between related devices is
normal.
Suppose the IP address of the opposite equipment is 10.10.10.2. Enter command in

the Run dialog box. After the Command window is displayed, enter ping 10.10.10.2.
If the returned message shows that the packet loss ratio is 0%, the communication
with the opposite equipment is normal.
z
If necessary, use the tracert command to locate the IP address of the faulty
router in the bearer network.
Suppose the IP address of the opposite equipment is 10.10.10.2. Enter command in

the Run dialog box. After the Command window is displayed, enter tracert
10.10.10.2. The returned information will show the route to the opposite equipment
and the IP addresses of the routers on the path.
z
Contact the responsible person in the data department. Use specialized

instruments or software to test the parameters of the bearer network such as the

2-2

transmission delay, the bit error rate, the packet loss ratio and the jitter. Check
whether network congestion, network storm or virus attacking exists in the
bearer network.
IV. Handling Equipment Fault

If you have confirmed that the hardware of the equipment are down; that is, it is an
equipment fault, handle the fault immediately according to the pre-prepared scheme
or section 2.2 Handling Equipment Fault.
V. Handling Extremely Heavy Traffic Fault

If service congestion occurs and you have confirmed that it is not a hardware fault,
check if it is an extremely heavy traffic fault. If yes, handle the fault according to the
pre-prepared scheme or the flow described in section 2.3 Handling Extremely Heavy
Traffic Fault.
VI. Handling Bearer Network Fault

If you have confirmed that the service congestion is caused by the bearer network
fault, contact the responsible person in the data department immediately to handle the
bearer network fault.
VII. Judging Whether Fault Is Removed

After handling the fault, you must check if the fault has been removed through the
NMS and maintenance console as well as by such means as telephone dialing test
and service verification. By doing these, you can judge whether the functions or
services of the equipment recover to normal.
VIII. Collecting Fault Information

Collecting fault information is important for requesting technical support, analyzing
and locating the source of the fault, and preventing re-occurrence of similar faults. It
can provide valuable experience for you and good reference for the manufacturer.
Therefore, you need to collect the fault information in time no matter the fault has
been successfully handled or not. For detailed information about collecting fault
information, refer to section 2.1.2 Collecting Fault Information.
IX. Reporting and Waiting for Technical Support

If you fail to clear the fault according to related emergent fault handling flows, ask for
technical support from the customer service center (see page 2 of the cover of this
manual) or regional office of Huawei by telephone or fax.
In order to shorten the handling time of the fault, record your emergency handling in
detail, notify Huawei of the replaced boards during the handling, and ask for
corresponding standby boards. For the fax, you can use the Emergency Maintenance
Note. For details, refer to Appendix A Record Tables of Emergency Maintenance.
2-3

2.1.2 Collecting Fault Information

Collect the following types of the equipment faults:
I. Brief Report of Fault

The service carrier can design the brief report of the fault. The contents of the report
include the occurrence time, nature, representation, and detailed handling of the fault.
When the fault is not solved, you can use the Emergency Maintenance Note to
replace the brief report of the fault.
II. Collecting Debug Logs

You need to copy all the *.dbg and *.log files under the directory
E:\MSSQL\SGData in the BAM and save them to a new path in time. These files are
*.dbg, debug.log, and DatamanError.log.
Caution:
In this version, if the server is in single-system mode, the default storage path for the
system debugging information is E:\MSSQL\SGData. For actual path, refer to the
actual installation directory of the system.
In this version, if the server is in dual-system mode, the default storage path for the
system debugging information is F:\MSSQL\DATALOG.
These debug log files are crucial to the location of the fault. When the size of these
files reaches a certain threshold, the system will automatically remove the information
saved originally. Therefore, after the emergent fault occurs, you need to copy and
save these files to another place in time.
III. Collecting Alarm Logs

You need to collect the alarm log information from 30 minutes before the occurrence
of the fault to 30 minutes after it. You can perform the query and saving operations on
the alarm management system. The operations are as follows:
1)
Select Alarm Query -> Query on the menu bar of the alarm management
system, and set the type and time segment of the alarm to be queried on the
pop-up window. Click OK.
2)
On the output window of the query result popped up, right click and select Save
as on the shortcut menu popped up. Then you can export the alarm log
information and save it as a text file.

2-4

IV. Collecting Command Logs

You need to collect the command log information from 30 minutes before the
occurrence of the fault to 30 minutes after it. You can execute the command LST LOG
on the client to export the related command log information and save it as a text file.
2.2 Handling Equipment Fault

This section describes the emergency measures taken when the equipment or BAM
server breaks down.
2.2.1 Handling Breakdown of Cabinet or Frame

If you confirm that an emergent fault has occurred to the cabinet or frame, follow these
steps to check the equipment and handle the fault.
I. Checking If Power Supply to Cabinet Is Normal

A power failure to the cabinet leads to the breakdown of the host. Follow these
methods to check if the power supply to the cabinet is normal:
z
If the green RUN indicator on the front panel of the power distribution frame is
on and blinks once every two seconds, it indicates that the power supply to the
cabinet is normal. That is, the power supply to the power distribution frame and
the circuit in it is normal.
If the green RUN indicator on the front panel of the power distribution frame is
off, it indicates that the power supply to the cabinet is abnormal. That is, neither
of the two channels of the power supply to the power distribution frame has any
voltage.
II. Powering On and Restarting Cabinet After Repairing Power Supply System
Abnormal power supply to the cabinet is generally caused by faults of the power
supply system of the equipment room. In this case, proceed as follows to restore the
power supply:
1)
To prevent accidents, turn off all the power switches (SW1 to SW6) on the front
panel of the power distribution frame before the power supply system of the
equipment room returns to normal.
2)
Repair the power supply system of the equipment room immediately.
3)
After the power supply system of the equipment room returns to normal, power
on and restart the cabinet according to the methods described in section 3.1
Power-On Operations.
III. Checking If Power Supply to Master Service Frame Is Normal

After confirming that the power supply to the cabinet is normal, check if the power
supply to the master service frame is normal. Since such important boards as the
2-5

HSYS and SBPI are configured in the master service frame, a power failure to the
master service frame directly leads to the breakdown of the equipment. Proceed as
follows to check if the power supply to the master service frame is normal:
z
If the indicators on the front panels of all the boards in the master service frame
are on, it indicates that the power supply to the master service frame is normal.
If no indicator on the front panels of the boards in the master service frame is on,
it indicates that the power supply to the master service frame is abnormal.
If the power supply to the master service frame is abnormal, do not perform any
operations before locating the fault. Contact Huawei immediately for technical
support.
IV. Checking If HSYSs in Master Service Frame and Slave Service Frame
Have Broken Down
The HSYS module supports the normal operation of service frames (OSTA frames). If
all the HSYSs break down, no boards in the frames can work normally.
If the following situations occur, it indicates that the HSYSs have broken down:
z
The RUN indicators on the front panels of the active and standby HSYSs are off
or constantly on.
The FAIL indicator on the front panels of the active and standby HSYSs lights
up.
The high-speed bus status indicators DOMA and DOMB on the front panels of
the active and standby HSYSs are all off.
The CPU utilizations of the active and standby HSYSs are close to 50% for a
long time.
V. Resetting or Replacing HSYS

After confirming that the HSYS module in the service frame has broken down, first
reset the active and standby HSYSs, and then check if the HSYS module runs
normally. If it runs abnormally, try to replace the HSYS boards to remove the fault.
VI. Collecting Fault Information

No matter the fault is removed or not, you need to collect the fault information as
described in section 2.1.2 Collecting Fault Information.
2.2.2 Handling BAM Breakdown

If you confirm that the BAM has broken down, handle the fault immediately according
to the following process: remove the power supply fault of the BAM restart the BAM
protect the site environment wait for technical support.

2-6

I. Checking If Power Supply to BAM Is Normal

A power failure to the BAM leads to a BAM breakdown. Proceed as follows to check if
the power supply to the BAM is normal:
z
If the power indicator of the BAM is green, it indicates that the power supply to
the BAM is normal and the BAM is on.
If the power indicator of the BAM is yellow, it indicates that the power supply to
the BAM is normal and the BAM is in the standby state.
If the power indicator of the BAM is off, it indicates that the power supply to the
BAM is abnormal.
If the power supply to the BAM is abnormal, do not perform any operations before
locating the fault cause. Contact Huawei immediately for technical support.
II. Checking If Hard Disk Array Cabinet Is Normally Powered

z
If the BAM is in single-system mode and the system is not equipped with a hard
disk array cabinet, you can skip this step.
If the BAM is in dual-system mode and the system is equipped with a hard disk
array cabinet, check the power indicator on the front panel of the hard disk array
cabinet. When the power supply is normal, the indicator is constantly green.
III. Restarting BAM

If the power supply the BAM is normal but the BAM breaks down, proceed as follows
to rapidly restore the normal operation of the BAM:
1)
If the BAM is in the standby state, press the power switch of the BAM to restart
the BAM.
2)
If the Windows operating system of the BAM is still running, use the restart
function of the operating system to restart the BAM.
3)
If the Windows operating system of the BAM breaks down, press the Reset
button of the BAM to restart the BAM.
IV. Protecting Site Environment

If you cannot restore the normal operation of the BAM by restarting it, do not perform
such operations to the BAM as reinstalling the system or formatting the hard disk
before technical support personnel of Huawei arrive. Otherwise, you may lose
important data on the hard disk of the BAM.
V. Collecting Fault Information


2-7

2.2.3 Handling Restart of Equipment

Start
No
Restart
mandatorily?
Yes
Querying software parameter switches of
all boards
No
Load data from

background?
Yes
FTP program
is running?
No
Opening FTP service

program
Yes
Setting software parameter
switches
Software parameter switches

meet standards?
No
Yes
Powering off frames one by one starting from frame 0 and then
powering them on one by one
No
Boards are
normally loaded?
Yes
Other processing flow
No
Data is
consistent?
Yes
End
Figure 2-2 Flow of handling restart of equipment

You need to restart the equipment when it requires to load programs or data in
batches or because of other reasons (it is to be powered on again after a power
failure). To ensure that the equipment can be normally restarted and it can run
normally after the restart, proceed as follows:
2-8

1)
Confirm whether restart is mandatory.
2)
Use the DSP SFTSWT command to query the software parameter switches of all
the boards.
3)
Confirm whether loading programs and data from the background is required. If it
is required, check if the FTP program in the BAM is running. If not, start the FTP
program manually.
4)
Use the SET SFTSWT command to set the software parameter switches. After
completing the setting, use the DSP SFTSWT command to query if the setting is
successful. If it is not, reset the software parameter switches.
5)
After powering off the service frames one by one starting with master service
frame 0, power on them one by one starting with master service frame 0.
6)
Check if the boards can be normally loaded and normally run, and if the links and
connections are normal.
7)
Check if the data is consistent.
8)
If insolvable problems occur during the restart, contact Huawei for technical
support.
2.3 Handling Extremely Heavy Traffic Fault

Since the equipment is designed with much redundancy, extremely heavy traffic does
not have much impact on the transfer and translation of the equipment. Long-time
extremely heavy traffic, however, will cause faults such as rise of CPU utilization,
generation of a large number of alarms, and no response to delivered commands.
Proceed as follows to handles the faults:
Extremely heavy traffic may lead to the congestion of links, SBPU, or HSYS, which
further causes mass congestion of links or boards. As a result, mass interruption of
communication occurs. If the extremely high traffic fault is not handled in time, the
consequences can be severe.
Caution:
Extremely heavy traffic may cause no response for commands delivered. In the
process of emergency maintenance, if the system does not respond after a command
has been delivered many times, contact Huawei immediately for technical support.

2-9

Start
Extremely heavy
traffic fault?
No
Yes
Clearing activation
statistics, canceling all
message tracing
Other processing
flow
Deactivating links of the office

direction, of which the load over the
links constantly exceeds 0.9 Erl.
Link C has a
large number
of messages
No
Yes
Deactivating
link C
Opposite plane
discards a large
number of messages
sent from end
office?
Yes
Modifying data of end
office, directing route to
the local SG
No
Foreground/
background
communication
times out?
Yes
Checking
correpsonding board
End
Figure 2-3 Flow of handling extremely heavy traffic faults

2-10

I. Analyzing Fault Alarm

When a sudden alarm occurs, stay calm, observe the alarm carefully, record it, and
analyze its cause. If you confirm that the alarm is caused by extremely heavy traffic,
ask for technical support in accordance with the related flow and perform the following
operations.
II. Clearing Activation Statistics and Closing Statistics Console

By using the DEL TRFACT command to clear activation statistics, you can reduce the
load on the SLPU, SBPU, and HSYS in the foreground and cut the CPU utilization.
After the statistics console is closed, the statistic data stored by the host in the input /
output controller (IOC) will not be sent to the background terminal. In this way, you can
reduce the communication load of the BAM.
III. Canceling All Message Tracing tasks

Carry out the RST TRACE command to cancel all message tracing tasks. You can
also carry out the STP ALLMTPTRAC, STP ALLTRAC, STP ALLTRAC, STP
M3TRAC, or STP SCTPTRAC command to cancel the tracing of the MTP message,
SCCP, maintenance and debugging message, M3UA message, and SCTP message.
Caution:
If there is no response to the command, re-send the command several times. If there
is still no response, contact Huawei for technical support.
IV. Deactivating Links of Office Direction, Load of Which Constantly Exceeds

0.9 Erl
Sometimes, the load of all the links of an office direction constantly exceeds 0.9 erl, or
the links frequently receive TFP and TFA messages, which leads to frequent
switchover of the links. In this case, you should use the command DEA N7LKS in the
terminal maintenance and test system to deactivate all the links in the office direction.
V. Handling Faults on Links B and D in Opposite Equipment and End Office

When links B and D of the equipment of the opposite plane are faulty while links A and
C are normal, messages cannot be forwarded from the plane. At this time, the
forwarded and translated messages will be transferred to the equipment from link C.
As a result, the load of the equipment will rise sharply. In this case, deactivate link C.
If the end office statically shares the load of the equipment, the messages forwarded
and translated by the end office will be discarded when the opposite equipment is

2-11

faulty. In this case, modify the data of the end office, and direct the corresponding
translation point to the local equipment.
VI. Handling Communication Timeout in Foreground and Background

When the HSYS has a high CPU utilization, commands sent from the terminal
workstation (WS) such as one to deactivate a link often do not get a response, and the
terminal prompts Communication Timeout. In this case, you can consult engineering
information to look for the SLPU board with high load or with links which receive TFP
and TFA messages so frequently that the links switch over frequently. After that, pull
out the corresponding board to deactivate the links and reduce the load.
VII. Collecting Fault Information


2-12

Chapter 3 Related Operations of Emergency Maintenance
Chapter 3 Related Operations of Emergency

Maintenance
3.1 Power-on Operations
3.1.1 Powering On and Restarting Cabinet
Cabinets should be powered on and restarted only in the following situations:
z
During deployment or expansion, it is necessary to perform power-on test to the

equipment after finishing the installation of all hardware.
During important upgrading of software or hardware, it is necessary to power off

the devices, and then power them on again.
Major faults of the power supply system cause power failures of the equipment.
When the power supply system becomes normal, it is necessary to power on the
equipment.
Follow these steps to power on and restart a cabinet:
I. Powering On the DC Power Distribution Cabinet

Turn on all switches on the DC power distribution frame (PDF) of the equipment. Now
the RUN indicator on the panel of the PDFs should be on (green). It should blink
twice every second, indicating that the input power supply and internal circuits of the
PDFs are normal.
II. Powering On PDF of Basic Cabinet

Turn on the switches on the PDF of the basic cabinet one by one, that is, to turn the
switches to ON in turn from SW1 to SW6. Now the power module indicators PWR
on the panel of the frame monitoring board ALUI should be on (green), indicating the
power supplies for the frames are normal.
III. Powering On LAN Switch 0 and LAN Switch 1

Turn on the switches of LAN Switch 0 and LAN Switch 1 in the basic cabinet one by
one, that is, to turn the switches of the LAN Switches to ON. Now the POWER
indicators on the panel of the two LAN Switches should be on (green), indicating the
power supplies for the LAN Switches are normal.
IV. Powering On KVM/LCD Converter

Turn on the switch of the KVM (keyboard, video, mouse)/LCD (liquid crystal display)
converter in the basic cabinet, that is, to turn the switch to the side with a symbol.

3-1

Now the KVM/PWR indicator on the panel of the KVM should be on (green),
indicating that the power supply to the KVM/LCD converter is normal.
V. Powering On the Server

As the BAM server may be configure either in single-system mode or dual-system
mode, strictly carry out the following procedures to start the server.
If the single-system mode is adopted, proceed as follows:
z
If the power indicator of the server is orange, it means that the server is in the
standby state. You can press the power switch of the server. Now the indicator of
the switch will turn to green, indicating a normal power supply of the server.
If the dual-system mode is adopted, proceed as follows:

z
In the dual-system mode, the system is equipped with a hard disk array cabinet.
Turn on the two power switches on the back of the hard disk array cabinet. If the
power supply is normal, the power indicator on the front panel of the hard disk
array cabinet will be constantly green.
After confirming the hard disk array cabinet is normally started, start the server.
Turn on the power switch of the active server. After the active server starts its
operating system, start the standby server.
Note:
Check the label on the server. By default, the server named ServerA is the active
server, and the one named ServerB is the standby server.
VI. Powering On Slave Service Frames

Turn on the switches on the PDF of the cabinet one by one, that is, to turn the
switches on the PDF to ON in the order of SW1 to SW6. Now the power module
indicators PWR on the panels of the monitoring boards (ALUIs) of the slave service
frames should be on (green), indicating the power supply for the frames is normal.
VII. End of Operation

After the above operations, check the running status of the components in the cabinet
carefully to ensure there is no abnormality. Till now, the power-on operation is
completed.
3.1.2 Powering On and Restarting Frames

Frames should be powered on and restarted only in the following situations:
z
The active and standby HSYSs in the frame are faulty or down.

3-2

z
Major faults of the power supply system cause power failures of the frame. After
repairing the power supply system of the frame, power on the frame.
I. Confirming Electrical Controlling Relationships

Since the power supply of each frame is controlled by the two switches on the PDF,
and the controlling relationships are different, confirm electrical controlling
relationships between the PDF and the components in the cabinet carefully to avoid
maloperations.
II. Turning Off Two Switches Controlling Power Supply of Frame

After confirming the electrical controlling relationships, turn off the two switches
controlling the power supply of the PDF one by one. Now the indicators on all the
boards of the frame should be off, indicating power-off of the frame.
III. Turning On Two Switches Controlling Power Supply of Frame

Ten seconds after the frame is powered off, turn on the two switches controlling the
power supply of the frames on the PDF one by one. That is, turn the switches to ON.
Now the power module indicators PWR on all the ALUIs of the frame should be on
(green), indicating the frame has been powered on again.
IV. End of Operation

After the above operations, you can open the equipment panel on the client to see
whether the frame is powered on and working normally. If there is no abnormality, you
can finish the power-on operation.
3.2 Pulling Out and Inserting Boards
Caution:
If the lower ejector lever of a board is pressed down or the hot-swap indicator (blue) is
on, it indicates that the board is powered off. At this time, if you just press the lower
ejector lever, you cannot power on the board. Instead, you must pull out the board and
then insert it into the backplane again. After that, press the lower ejector lever to
power the board on.
Proceed as follows to pull out and insert a board:

1)
Put on an ESD-preventive wrist strap. Insert its grounding terminal into the ESD
jack of the rack.

3-3

2)
Use a cross screwdriver to loosen the fixing screws in the upper and lower
ejector levers of the board, as shown by step (a) in Figure 3-1.
3)
Grasp the upper and lower ejector levers with both hands. Press down the red
lockers on the ejector levers with thumbs to release the ejector levers. After that,
you can pull out the board from the frame.
4)
Press outward the ejector levers hard with both hands. When the two ejector
levers form an angle of 45, the board connectors break away from the
backplane, as shown by step (b) in Figure 3-1.
Figure 3-1 Pull out a board from a frame

5)
Grasp the ejector levers with both hands, and pull out the board for one to two
centimeters smoothly along the slide rails of the frame until the board breaks
away from the backplane.
6)
After confirming that the board has broken away from the backplane, insert it into
the backplane again. Stop pushing when the positioning pin on the front panel of
the board touches the pin positioning hole on the frame.
7)
Turn inward the ejector levers of the board hard with both hands. When the
ejector levers are vertical to the front panel, the locking keys lock the ejector
levers. This indicates that the board has been inserted into the frame.
Proceed as follows to check the status of the board:

z
If the RUN indicator on the front panel of the board is on and blinks regularly, it
indicates that the board is running normally.
Open the system navigator pane on the left of the maintenance console window,
and select System Setting -> Board Position Management. If the board
indicator is green or light blue (when in the standby state), it indicates that the
board is running normally. If the indicator is red, it indicates that the board is
running abnormally.
If the fault indicator ALM (yellow) on the front panel of the board is on for one
second and then off for one second, it indicates that the board is running
abnormally.
If the board is running abnormally, you need to replace it. For details, refer to U-SYS
SG7000 Signaling Gateway Maintenance Manual Parts Replacement Guide.
3-4

3.3 Resetting Operations

3.3.1 Resetting Frames
Caution:
The frames are reset in the following situations:
z
All the boards in the frame are faulty or down.
The major software upgrade is to be implemented.
I. Preparations
Before resetting a frame, use the BKP DB command to back up the BAM data.
II. Method 1: Resetting a Frame by Resetting All Boards in Frame

During failure or down of all the boards in the frame, you can reset the frame by
resetting all the boards in the frame according to the following steps:
1)
Press the Reset button on the panel of the HSYS boards to reset the active and
standby HSYSs.
2)
Press the Reset button on the panel of the service boards (front boards) to
reset the service boards.
III. Method 2: Resetting a Frame by Pulling Out and Inserting the Active and
Standby HSYSs
During failure or down of all the boards in the frame, you can reset the frame through
pulling out and inserting the active and standby HSYSs if method 1 does not work.

3-5

3.3.2 Resetting Boards
Caution:
Only in the following situations can boards be reset:
z
The board is faulty or down. In this case, you can reset the board directly.
During major upgrading of software, it is necessary to reset boards. In this case,

reset the standby boards first. After the standby boards work normally, reset the
active boards.
I. Preparations
If the board to be reset is an HSYS, use the BKP DB command to back up the BAM
data before resetting the board.
II. Method 1: Resetting Boards Using RST BRD Command

During major upgrading of software, you can carry out the RST BRD command to
reset boards. For example:
//Resetting the front board in slot 0 of frame 0 of rack 0.
RST BRD: FN=0, SHN=0, SN=0, LOC=FPB;
III. Method 2: Resetting Boards by Pressing Reset Buttons on Boards

During failure or down of the board, you can reset the board by pressing the Reset
button on the panel of the board.
IV. Method 3: Resetting Front Boards by Powering It On and Off

Reset a board by using the PWR BRD command to power on and off the board.
3.4 Backing Up and Recovering Database

The BAM database is also called the background database. It is a SQL database
stored in the hard disk of the BAM in the format of a data table. Its main function is to
store all kinds of data generated in the users data configurations.
3.4.1 Automatic Backup of Database

At 4:30 a.m. (default time) every day, the system automatically backs up the BAM
database and the registry to a default directory.
z
In single-system mode, the default directory is E:\MSSQL\SGDATA.
In dual-system mode, the default directory is F:\MSSQL\DATALOG.

3-6

Caution:
z
In this version, the default storage path for the BAM database and registry is
E:\MSSQL\SGDATA. For the specific path, refer to the actual installation
directory.
Ensure that the disk has adequate space.
Twenty-two backup devices are needed for routine backup (twenty-two

erasable/writable compact disks or twenty-two tape cassettes). Of the twenty-two
devices, six are used to back up the data from Monday to Saturday of the current
week (ordinary backup), four to back up the data of the recent four Sundays
(weekly backup), and twelve to back up the data of the first day of each month of
the current year (monthly backup).
1)
Automatic backup of the BAM database
The backup of the BAM database is performed in a cyclic manner. At most eleven
database files can be backed up. The backup file of the BAM database includes the
following contents.
z
Saving the database backup of the past consecutive seven days from the current
day (except Sunday), BamYYYYMMDD.dat is the file name of these six files.
Saving the database backup of the four Sundays of the past 28 days,
BamYYYYMMDD.dat is the file name of these four files.
On the first day of each month, a BAM database backup has been stored in a file
BamMonthBak.dat.
2)
Automatic backup of the BAM registry
The system automatically stores the BAM registration information in the Windows NT
system registry every day. Only the latest backup is retained, with the file name of
BamReg.bak.
Note:
In the BAM.ini configuration file, you can set the start time of the automatic BAM
database backup and registry backup for the system by modifying the value of
BkpDbStartHour (start hour of the database backup) and BkpDbStartMin (start minute
of the database backup) in DataMan. Restart the DataMan process for the new
setting to take effect after the modification of the content in the sub-item.

3-7

3.4.2 Manual Backup of Database

Under such special situations as the expansion, upgrading and loading, you have to
back up the BAM database and the registry manually before the upgrading or loading.
There are two modes for manual backup.
I. Command Mode (BKP DB)

In the MML client of the service maintenance system, execute the BKP DB command
to back up the current BAM database and the registry to a default directory.
z
In single-system mode, the default directory is E:\MSSQL\SGDATA.
In dual-system mode, the default directory is F:\MSSQL\DATALOG.
II. Use Tool Menu of Enterprise Manager of SQL Server

1)
In the Windows NT interface of BAM, click Start -> Programs -> Microsoft SQL
Server 7.0 -> Enterprise Manager to log in to the database server. The
database server window is as shown in Figure 3-2.
Figure 3-2 SQL Server enterprise manager

2)
Suppose the BAM name is 2203 (Windows NT). Expand the navigation tree to
open the node Console Root -> Microsoft SQL Servers -> 2203 (Windows
NT) -> Databases. Right-click the node to display a floating menu as shown in
Figure 3-3.

3-8

Figure 3-3 Window of data backup operation

3)
Click All Tasks -> Backup Database to pop up a window as shown in Figure 3-4.
Select Bam from the Database field to select the database to be backed up. In
the Backup field, determine the method of data backup by selecting backup of
all the data or of data that has been modified. Select the default data backup file
name of the system in the Destination field and click Remove to remove the
value. Then click the Add to determine the file name and the path where the
backup file is located, as shown in Figure 3-5.

3-9

Figure 3-4 Select database and backup mode
Figure 3-5 Choose backup destination

4)
As shown in Figure 3-6, select Overwrite existing media in the Overwrite area,
which indicates to overwrite the previously backed up data. If you do not want to
overwrite the data, select Append to media and click OK.

3-10

Figure 3-6 Set the data overwriting mode

5)
The system will back up the data after confirmation. Moreover, an interface
displaying the backup progress will pop up as shown in Figure 3-7.

3-11

Figure 3-7 Data backup progress of the system

6)
When the system has successfully backed up the data, it gives a success
prompt.
Note:
z
When the BKP DB command is executed for the BAM database backup, the
system does not back up the operation log. When the Enterprise Manager Tool
menu of the SQL Server is used for the data backup, the system will back up the
operation log.
The file generated from manual backup is named based on the date. If several
times of backup are necessary within one day, the file name of the last backup has
to be modified manually.
3.4.3 Safe Data Recovery

The operation of the safe data recovery is also carried out on BAM. You can either run
the installation program of the terminal system or use the SQL Service Manager to
recover the BAM data. The SQL Service Manager is recommended. The data
recovery process through the SQL Service Manager is specified in the following text.

3-12

I. Quitting All BAM Processes

Quit all BAM processes to avoid the recovery failure caused by the process accessing
the data.
II. Restarting SQL Server Program

Stop the SQL Server program and then restart it. In this way, the recovery will not fail
due to the SQL Servers access to some data in the BAM server. Its operation
procedures are as follows:
1)
In the terminal system of BAM server, click Start -> Programs -> Microsoft
SQL Server 7.0 -> Service Manager. The system will display a dialog box as
shown in
Figure 3-8.
Figure 3-8 SQL Server service manager
2)
Click
to stop the SQL Server program. Then the system will pop up a
dialogue box. Click Yes to interrupt the communication between the foreground
and the background.
3)
Click
in Figure 3-8 to restart the SQL Server.
III. Restoring BAM Database

1)
In the Windows NT interface, click Start -> Programs -> Microsoft SQL Server
-> Enterprise Manager to log on to the database server.
2)
Enter Console Root -> Microsoft SQL Servers -> SQLserver Group ->
L17918B (Windows NT) -> Databases. Right-click and select All Tasks ->
Restore Database.
3)
In the window as shown in Figure 3-9, select Bam in the Restore as database
field and From equipment in the Restore field. Recover the data setting
according to actual situations (complete database recovery, recovery of different
3-13

databases, and so on). In general, the information displayed in the data

equipment of Equipment is the latest backed up equipment data file. If the
equipment data file to be recovered is correct, steps 4 to 7 can be skipped.
Otherwise, start from step 4.
Figure 3-9 Select a database to be recovered

4)
If the equipment file displayed in Figure 3-9 is not the equipment data file to be
restored, proceed as follows:
5)
Click elect Devices to display a window as shown in Figure 3-10.

3-14

Figure 3-10 Select the equipment to be recovered

6)
Select the equipment file in the list. Click Remove All and Add. The system
displays a window as shown in Figure 3-11.
Figure 3-11 Choose the database file to be restored

7)
Click OK after selecting the equipment to be recovered based on the equipment

name.
8)
Select the data backup file to be recovered and click OK. The system will display
a window showing the progress of the data recovery.
9)
After the data recovery is finished, set the BAM Service to the automatic startup
mode and restart the BAM.

3-15

Caution:
After using the SQL Service Manager tool to recover BAM data, you must carry out
the FMT command, which converts the format of all data.

3-16

Appendix A Record Tables of Emergency Maintenance
Appendix A Record Tables of Emergency

Maintenance
A.1 Emergency Maintenance Note
If you failed to remove the fault, ask for help from Huawei by phone or fax. In order to
shorten the troubleshooting time, record your operations in detail, notify Huawei of the
replaced boards during the handling, and ask for corresponding standby boards from
Huawei according to the warranty in the contract.
You can use the following Emergency Maintenance Note for fax.

A-1

Emergency Maintenance Note

The following contents are to be filled by customer in detail
Office name
Equipment type
Capacity
Complainer
Contact
telephone
Version
Date and time
Responding
date and time
required
Whether
it
has passed
the warranty
period
Yes No
Description of the fault(s) and handling processes (in detail):
Auditor:
Stamp (your department):
The following contents are to be filled by Huawei
by telephone
on-site support
Handling method
by remote maintenance
Results (additional pages can be attached)
Operator:
Date:
Unsolved problems:
Note: This table is to be stamped by the operation and maintenance department.

A-2
by

A.2 Troubleshooting Record Table

Equipment name:
IP address:
Date of maintenance: _______

Time of occurrence:
Time of solution:
Person on duty:
Operator:
Fault type:
Hardware fault
Power fault
FE/E1 interface fault
Transmission network fault
Relaylink fault
Clock fault
Communication fault between host and BAM

MTP link fault
Subscriber terminal fault
Other faults
Fault source:
User complaint
Alarm system
Found during routine maintenance
Other sources
Description of Fault:
Handling method and result:

A-3

Appendix B Power Supply System of Cabinet

B.1 Power Supply Loop of Power Distribution Frame
All cabinets of the SG7000 are N68-22 cabinets. Under normal circumstances, the
power of each N68-22 cabinet is supplied by two independent 48 V direct current (DC)
power supplies. The power supply of the components inside the cabinet is controlled by
the PDF at the top of the cabinet. The power supply of the PDF is as shown in Figure
B-1.
-48V1
-48V2
PDF
SW1 SW2 SW3 SW4 SW5 SW6
Figure B-1 Power supply of the PDF

In order to increase the reliability of the power supplies of the components inside the
cabinet, the PDF uses a large power diode to combine the two input power supplies
into one. Then the power supply is exported to the six switches (from SW1 to SW6) on
the panel of the PDF through one power bus cable. These switches help to supply the
power for the components inside the cabinet through corresponding power distribution
system. In this way, when one input power supply fails, the other can still supply power
for the components inside the cabinet through the PDF.
B.2 Power Supply Loop Inside Cabinet

The SG7000 has two types of cabinets: basic cabinet and extension cabinet. Because
different types of cabinets have different components, their primary power supply
system loops (namely 48 V power supply systems) are different.
The LAN Switch 0, LAN Switch 1, and the KVM/LCD converter inside the basic cabinet
are controlled by a power switch, while the other components are powered by the two
switches on the PDF.
Because the BAM can be either in single-system mode or dual-system mode, different
modes have different hardware configurations. In this case, the power supplies also
differ accordingly. For specific differences, refer to the following tables.

B-1

z
In single-system mode, the relationships between the PDF and the components
inside the cabinet are as shown in Table B-1.
Table B-1 Relationship between cabinet components and controlling switches (1)
Cabinet type
Basic cabinet
Extension cabinet
Component
Controlling switch
BAM
SW5, SW6
LAN Switch 0
SW3
LAN Switch 1
SW2
KVM/LCD
SW1
Master service frame 0
SW1, SW4
Slave service frame 1
SW2, SW5
SW1, SW4
SW2, SW5
In dual-system mode, the relationships between the PDF and the components
inside the cabinet are as shown in Table B-2.
Table B-2 Relationship between cabinet components and controlling switches (2)
Cabinet type
Component
BAM0
SW5, SW6
BAM1
SW5, SW6
Hard disk array cabinet

(ARRAY)
Basic cabinet
Extension cabinet
Controlling switch
SW3, SW4
LAN Switch 0
SW3
LAN Switch 1
SW2
KVM/LCD
SW1
Master service frame 0
SW1, SW4
SW2, SW5
SW1, SW4
SW2, SW5

B-2

Appendix C Acronyms and Abbreviations
Appendix C Acronyms and Abbreviations

Acronym/abbreviation
Full spelling
AS
Application Server
ALUI
Alarm Unit Interface board
BAM
Back Administration Module
DPC
Destination Point Code
LAN
Local Area Network
LCD
Liquid Crystal Display
KVM
Keyboard, Video, Mouse
MML
Man-Machine Language
MTP
Message Transfer Part
NGN
Next Generation Network
SBPI
Signaling Broadband Processing Interface
SBPU
Signaling Broadband Processing Unit
SCCP
Signaling Connection and Control Part
SCTP
Signaling Control Transmission Protocol
SG
Signaling Gateway
SLPU
Signaling Low Processing Unit
SN
Sequence Number
SQL
Structured Query Language
STP
Signaling Transfer Point
TFA
TransFer-Allowed signal
TFP
TransFer-Forbidden signal
WS
Work Station

C-1

Index
Index
A
analyzing fault alarm, 2-11
HSYS checking, 2-6
BAM breakdown, 1-1
power supply of BAM checking, 2-7
board
power supply of hard disk array checking, 2-7
inserting, 3-3
powering on
pulling, 3-3
KVM/LCD converter, 3-1

power distribution cabinet, 3-1
powering distribution cabinet, 3-1
cabinet breakdown, 1-1
sever, 3-2
canceling message tracing, 2-11
slave service frames, 3-2
clearing activation statistic, 2-11
pressing reset button, 3-5
collecting
alarm log, 2-4
command log, 2-5
resetting board, 3-6
debug log, 2-4
restarting
BAM, 2-7
equipment, 2-9
data recovering, 3-12
power supply system, 2-5
database
automatic backup, 3-6
manual backup, 3-8
status of board checking, 3-4
deactivating link, 2-11
T
the power supply system checking, 2-5
i.

i-1

SG7000 Maintenance Manual-Emergency Maintenance PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SG7000 Maintenance Manual-Emergency Maintenance PDF

Uploaded by

Copyright:

Available Formats

Chapter 1 Classification of Emergent Faults ................................................

1.1 Definitions of Emergent Faults ...............................................................

Chapter 2 Emergency Maintenance Flow ......................................................

2.1 Overview of Emergency Maintenance Flow ...........................................

Chapter 3 Related Operations of Emergency Maintenance .........................

3.1 Power-on Operations .............................................................................

Appendix A Record Tables of Emergency Maintenance .............................

A.1 Emergency Maintenance Note...............................................................

Appendix B Power Supply System of Cabinet ..............................................

B.1 Power Supply Loop of Power Distribution Frame ..................................

Appendix C Acronyms and Abbreviations ....................................................

U-SYS SG7000 Signaling Gateway

Huawei Technologies Proprietary

U-SYS SG7000 Signaling Gateway

Huawei Technologies Co., Ltd.

Huawei Technologies Proprietary

Copyright 2005 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

Huawei Technologies Proprietary

About This Manual

Chapter 1 Classification of Emergent Faults introduces the definitions of the

Chapter 2 Emergency Maintenance Flow introduces the flows for processing

Chapter 3 Related Operations of Emergency Maintenance elaborates the

Appendix A Record Tables of Emergency Maintenance gives some samples

Appendix B Power Supply System of Cabinet introduces the power supplies

Appendix C Acronyms and Abbreviations lists the abbreviations and

Telecom administration personnel

Huawei Technologies Proprietary

Normal paragraphs are in Arial.

Headings are in Boldface.

Terminal Display is in Courier New.

II. GUI conventions

Button names are inside angle brackets. For example, click

Multi-level menus are separated by forward slashes. For

III. Mouse operation

Caution, Warning, Danger: Means reader be extremely careful during the

Note, Comment, Tip, Knowhow, Thought: Means a complementary

Huawei Technologies Proprietary

Maintenance Manual Emergency Maintenance

Huawei Technologies Proprietary

Maintenance Manual Emergency Maintenance

Chapter 1 Classification of Emergent Faults

Chapter 1 Classification of Emergent Faults

1.1 Definitions of Emergent Faults

I. Breakdown of Cabinet or Frame

II. BAM Breakdown

Power failure of the BAM.

Unable to start the BAM.

Automatic and frequent resetting of the BAM.

Maintenance Manual Emergency Maintenance

Chapter 1 Classification of Emergent Faults

III. Restart of Equipment

You need to load a batch of data to the equipment.

IV. Accidental Power Failure to Board

1.1.2 Extremely Heavy Traffic Fault

The CPU utilization rises sharply, often to above 50%.

Corresponding loading alarms of links are generated. Sometimes, a large

Huawei Technologies Proprietary

Maintenance Manual Emergency Maintenance