0% found this document useful (0 votes)

131 views76 pages

SG7000 Emergency Maintenance (V200R005C02 - 02)

Uploaded by

Catherine Higino

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

131 views76 pages

SG7000 Emergency Maintenance (V200R005C02 - 02)

Uploaded by

Catherine Higino

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 76

U-SYS SG7000 Signaling Gateway

V200R005C02

Emergency Maintenance

Issue 02
Date 2009-12-14

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://www.huawei.com
Email: [email protected]

Issue 02 (2009-12-14) Huawei Proprietary and Confidential i

About This Document

Purpose
This section describes the organization, related versions, intended audiences, conventions and
update history of U-SYS SG7000 Signaling Gateway Maintenance Manual – Emergency
Maintenance.

Related Versions
The following table lists the product versions related to this document.

Product Name Version

U-SYS SG7000 V200R005C02

Intended Audience
The intended audiences of this document are:

l On-site engineers
l Maintenance engineers
l Commissioning engineers

Organization
This document consists of four chapters and three appendixes, and they are organized as follows.

Chapter Description

1 Classification of Introduces the definitions of the emergent faults and basic

Emergent Faults principles of emergency maintenance.

2 Emergency Introduces the flows for processing emergency faults, such as

Maintenance Flow BAM breakdown, cabinet breakdown, and so on.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential iii

Chapter Description

3 System Restart Describes the application scope, preparations, and specific

procedures of restarting the system.

4 Related Operations of Elaborates the operations relevant to the emergency

Emergency maintenance of the equipment.
Maintenance

5 Record Tables of Gives some samples for recording the emergency maintenance
Emergency operations.
Maintenance

6 Power Supply System Introduces the power supplies used in the SG7000.
of Cabinet

7 Acronyms and Lists the abbreviations and acronyms used in this manual and
Abbreviations the corresponding full expressions.

Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
DANGER

Indicates a hazard with a medium or low level of risk which,

if not avoided, could result in minor or moderate injury.
WARNING

Indicates a potentially hazardous situation that, if not

avoided, could cause equipment damage, data loss, and
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
your time.

NOTE Provides additional information to emphasize or

supplement important points of the main text.

General Conventions
Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

iv Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Convention Description

Boldface Names of files, directories, folders, and users are in boldface. For
example, log in as user root.

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

Command Conventions
Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[] Items (keywords or arguments) in square brackets [ ] are

optional.

{ x | y | ... } Alternative items are grouped in braces and separated by

vertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can
be selected.

GUI Conventions
Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in
boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.

Keyboard Operation
Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressingCtrl+Alt+A means the
three keys should be pressed concurrently.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential v

Format Description

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys
should be pressed in turn.

Mouse Operation
Action Description

Click Select and release the primary mouse button without moving the pointer.

Double-click Press the primary mouse button twice continuously and quickly without
moving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certain
position.

Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.

Updates in Issue 02 (2009-12-14)

The PDB (DPD100-2-20) is added.

Updates in Issue 01 (2009-09-27)

Initial commercial release.

vi Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Contents

About This Document...................................................................................................................iii

1 Classification of Emergent Faults...........................................................................................1-1
1.1 Definitions of Emergent Faults.......................................................................................................................1-2
1.1.1 Equipment Fault.....................................................................................................................................1-2
1.1.2 Extremely Heavy Traffic Fault...............................................................................................................1-3
1.2 Basic Principles of Emergency Maintenance..................................................................................................1-3

2 Emergency Maintenance Flow.................................................................................................2-1

2.1 Overview of Emergency Maintenance Flow ..................................................................................................2-2
2.1.1 Overall Flow...........................................................................................................................................2-2
2.1.2 Collecting Fault Information..................................................................................................................2-5
2.2 Handling Equipment Fault..............................................................................................................................2-6
2.2.1 Handling Breakdown of Cabinet or Frame............................................................................................2-6
2.2.2 Handling BAM Breakdown...................................................................................................................2-7
2.3 Handling Extremely Heavy Traffic Fault........................................................................................................2-9

3 System Restart.............................................................................................................................3-1
3.1 Overview.........................................................................................................................................................3-2
3.1.1 Application Scope..................................................................................................................................3-2
3.1.2 Device Preparations................................................................................................................................3-2
3.1.3 Tool Preparations ..................................................................................................................................3-2
3.2 Restart Procedures...........................................................................................................................................3-3

4 Related Operations of Emergency Maintenance..................................................................4-1

4.1 Power-on Operations.......................................................................................................................................4-2
4.1.1 Powering On and Restarting Cabinet.....................................................................................................4-2
4.1.2 Powering On and Restarting Frames......................................................................................................4-3
4.2 Pulling Out and Inserting Boards....................................................................................................................4-4
4.3 Resetting Operations.......................................................................................................................................4-5
4.3.1 Resetting Boards....................................................................................................................................4-5
4.3.2 Resetting Frames....................................................................................................................................4-6
4.4 Handling BAM Failure....................................................................................................................................4-7
4.4.1 Starting the EWS....................................................................................................................................4-7
4.4.2 Restoring the BAM................................................................................................................................4-9
4.5 Backing Up and Recovering Database..........................................................................................................4-10

Issue 02 (2009-12-14) Huawei Proprietary and Confidential vii

4.5.1 Automatic Backup of Database ...........................................................................................................4-10

4.5.2 Manual Backup of Database ...............................................................................................................4-11
4.5.3 Safe Data Recovery .............................................................................................................................4-16

5 Record Tables of Emergency Maintenance...........................................................................5-1

5.1 Emergency Maintenance Note........................................................................................................................5-2
5.2 Troubleshooting Record Table........................................................................................................................5-3

6 Power Supply System of Cabinet...........................................................................................6-1

6.1 Power Supply Loop of Power Distribution Frame..........................................................................................6-2
6.2 Power Supply Loop in Cabinet.......................................................................................................................6-2

7 Acronyms and Abbreviations..................................................................................................7-1

viii Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figures

Figure 2-1 Overall flow for handling emergent faults..........................................................................................2-3

Figure 2-2 Process status in BAM manager.........................................................................................................2-8
Figure 2-3 Flow of handling extremely heavy traffic faults...............................................................................2-10
Figure 3-1 Flow of restarting system................................................................................................................... 3-4
Figure 3-2 FTP Server user management dialog box...........................................................................................3-7
Figure 3-3 Choose a database to be backed up.....................................................................................................3-9
Figure 3-4 IP addresses of the HSYSs...............................................................................................................3-10
Figure 3-5 Transfer file from super terminal......................................................................................................3-11
Figure 3-6 Choose file name and protocol ........................................................................................................3-12
Figure 4-1 Pull out a board from a frame.............................................................................................................4-4
Figure 4-2 BAM Manager....................................................................................................................................4-8
Figure 4-3 SQL Server enterprise manager........................................................................................................4-12
Figure 4-4 Window of data backup operation....................................................................................................4-13
Figure 4-5 Select database and backup mode.....................................................................................................4-14
Figure 4-6 Choose backup destination...............................................................................................................4-14
Figure 4-7 Set the data overwriting mode..........................................................................................................4-15
Figure 4-8 Data backup progress of the system.................................................................................................4-16
Figure 4-9 SQL Server service manager............................................................................................................4-17
Figure 4-10 Select a database to be recovered...................................................................................................4-18
Figure 4-11 Select the equipment to be recovered.............................................................................................4-19
Figure 4-12 Select the equipment to be recovered.............................................................................................4-19
Figure 6-1 Power supply of the PDB(DPD100-2-6)............................................................................................6-2
Figure 6-2 Power supply of the PDB(DPD100-2-20)..........................................................................................6-2

Issue 02 (2009-12-14) Huawei Proprietary and Confidential ix

Tables

Table 3-1 Suggested value for DIP switch ..........................................................................................................3-7

Table 6-1 Relations between cabinet parts and controlling switches...................................................................6-3

Issue 02 (2009-12-14) Huawei Proprietary and Confidential xi

1 Classification of Emergent Faults

About This Chapter

This chapter describes the definition and classification of emergency faults. Emergency
maintenance refers to series of emergency measures used to minimize loss, remove the fault,
and recover the system or equipment when emergent faults occur.
1.1 Definitions of Emergent Faults
This section describes the definitions of emergency faults. Based on generation reasons, faults
can be classified into the equipment fault and the extremely heavy traffic fault.
1.2 Basic Principles of Emergency Maintenance
This section describes basic principles of emergency maintenance. The emergency faults are
dangerous and may cause call congestion and equipment breakdown, so you must follow the
basic principles during the maintenance.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-1

1.1 Definitions of Emergent Faults

This section describes the definitions of emergency faults. Based on generation reasons, faults
can be classified into the equipment fault and the extremely heavy traffic fault.
1.1.1 Equipment Fault
This section describes the equipment fault. An equipment fault is a severe fault which causes
the loss of most or all of the functions of the equipment.
1.1.2 Extremely Heavy Traffic Fault
This section describes the extremely heavy traffic fault. Extremely heavy traffic may cause
congestion in links, SLPU, SBPU/SBPE, or HSYS, which may result in mass congestion in all
links or boards.

1.1.1 Equipment Fault

This section describes the equipment fault. An equipment fault is a severe fault which causes
the loss of most or all of the functions of the equipment.

Breakdown of Cabinet or Frame

Any of the following situations might result in the breakdown of a frame, cabinet, or even the
entire system.
l The power-off of the main control cabinet (cabinet 0) or master service frame (frame 0 of
the main control cabinet) leads to the breakdown of the entire system.
l The simultaneous breakdown of the active and standby HSYS boards of the master service
frame leads to the breakdown of the entire system.
l 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 configuration, the main control cabinet refers to cabinet 0, the master service frame refers to frame
0 of the main control cabinet, and the slave service frame refers to all the service frames excluding the master
service frame.

BAM Breakdown
BAM breakdown is a severe fault resulting in the loss of all BAM functions. In actual
applications, any of the following conditions is regarded as a kind of BAM breakdown:
l Power failure of the BAM.
l Unable to start the BAM.
l Automatic and frequent resetting of the BAM.
l The CPU utilization of the BAM is near 100% for a long time.
l The Windows operating system of the BAM breaks down during the operation or it is unable
to boot when the BAM starts.
l Abnormal running of the "BAM Manager". For example, unable to start the BAM Manager,
unable to start all the service processes (their states are "Stopped"), or all the service
processes enter the "Exception" state after being started repeatedly.

1-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Restart of Equipment
Restart the system when:

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

l You need to power on the equipment again after powering it off for other reasons.
l You find that the data in the host and the BAM are not consistent, and cannot recover the
data through the commands.

Unexpected Power Failure in Board

When a board is working normally, it may be powered off if you press the red locker on the
ejector lever inattentively. The board is powered off or faulty when:

l 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.
l The indicator displayed is red when you open the system navigator window on the left of
the maintenance console and select System Setting > Board Position Management.

For details, refer to SG7000 Parts Replacement Guide.

When a board is powered off unexpectedly, pull it out and insert it again to power it on. For
details, refer to section 4.2 Pulling Out and Inserting Boards.

1.1.2 Extremely Heavy Traffic Fault

This section describes the extremely heavy traffic fault. Extremely heavy traffic may cause
congestion in links, SLPU, SBPU/SBPE, or HSYS, which may result in mass congestion in all
links or boards.

The following situations lead to extremely heavy traffic faults:

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

l 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 Basic Principles of Emergency Maintenance

This section describes basic principles of emergency maintenance. The emergency faults are
dangerous and may cause call congestion and equipment breakdown, so you must follow the
basic principles during the maintenance.

To increase the efficiency of handling the emergent faults and minimize the loss, understand the
following basic principles before maintaining the equipment:

l The ultimate purpose of emergency maintenance is to recover the system operations and
service provisioning as soon as possible. To increase the efficiency of handling the
emergent faults, set up handling schemes based on the emergency maintenance manuals
and organize maintenance personnel to study and practice periodically.
l Maintenance personnel must attend the emergency maintenance training which is
mandatory for them before they handle the faults. They must learn the basic methods of
judging and handling emergent faults.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-3

l When there is an emergent fault, check whether the equipment and the bearer network are
working normally. Then determine 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.
l When emergent faults occur to the BAM, do not reinstall the system or format the hard
disk on the BAM. Consult Huawei for technical support to avoid the loss of important data.
l For immediate technical support, you can also contact the customer service center (see page
2 of the cover of this manual) or the regional office of Huawei.
l After handling an emergent fault, collect the alarm information related to this fault and send
the fault handling report, equipment alarm files and log files to Huawei for analysis.

1-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

2 Emergency Maintenance Flow

About This Chapter

This chapter describes the emergency maintenance flow. Emergency maintenance must be
performed based on a general flow. The maintenance handling flow various according to the
equipment fault and the extremely heavy traffic.
2.1 Overview of Emergency Maintenance Flow
This section describes the flow for handling 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.2 Handling Equipment Fault
This section describes the emergency measures taken when the equipment or BAM server breaks
down.
2.3 Handling Extremely Heavy Traffic Fault
This section describes the procedures for handling the extremely heavy traffic fault. Since the
equipment is designed with large capacity, extremely heavy traffic does not have much impact
on the transfer and translation of the traffic. 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. To handle the faults, perform the following steps.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-1

2.1 Overview of Emergency Maintenance Flow

This section describes the flow for handling 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
This section describes the overall flow of emergency maintenance. The ultimate purpose of
emergency maintenance is to recover system operations and service provision as soon as
possible. The process of handling emergency faults is different from those of handling other
faults.
2.1.2 Collecting Fault Information
This section describes the information to be collected during handling the equipment faults.

2.1.1 Overall Flow

This section describes the overall flow of emergency maintenance. The ultimate purpose of
emergency maintenance is to recover system operations and service provision as soon as
possible. The process of handling emergency faults is different from those of handling other
faults.
Figure 2-1 shows the overall flow.

2-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 2-1 Overall flow for handling emergent faults

Collecting Fault Information

When emergent faults occur, collect information from fault complaints, alarms from the network
management system (NMS), and by checking the equipment and making dial tests. This provides
a basis for the subsequent processing.

Checking Hardware Equipment

Hardware faults often cause service congestion. For example, a frame breakdown leads 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 remove the faults.
Common methods of checking the hardware equipment are as follows:

l 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.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-3

l Check if the components, including the LAN Switch and BAM, in the main control cabinet
are running normally.
l Check if the frames are running normally. In the system navigation window of the client,
select System Settings -> Board Position Management. Observe the running status of
the boards (front boards, back boards, and subboards), power frame, and fans.

Checking Bearer Network

If the service congestion occurs when the hardware equipment is running normally, first check
if the bearer network is running normally. Common methods for checking the bearer network
are as follows:
l Check if there is any transmission fault alarm for the alarm management system.
l Use the ping command to check if the connection between related devices is normal.
l Suppose the IP address of the peer 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 peer
equipment is normal.
l If necessary, use the tracert command to locate the IP address of the faulty router in the
bearer network.
l Suppose the IP address of the peer 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 shows the route to the peer equipment and the IP addresses of the
routers on the path.
l Contact the responsible person in the data department. Use specialized instruments or
software to test the parameters of the bearer network, such as the 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.

Handling Equipment Fault

If you have confirmed that the hardware of the equipment is 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.

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.

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.

Judging Whether Fault Is Removed

After handling the fault, check if the fault has been removed, through the NMS and maintenance
console as well as through the telephone dialing test and service verification. By doing these,
you can judge whether the functions or services of the equipment is recovered.

2-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

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 provides a valuable
experience for you and good reference for the manufacturer.

Therefore, collect the fault information in time regardless of whether the fault has been
successfully handled or not. For detailed information about collecting fault information, refer
to section 2.1.2 Collecting Fault Information.

Reporting and Waiting for Technical Support

If you fail to clear the fault according to related emergent fault handling flows, ask the customer
service center (see page 2 of the cover of this manual) or regional office of Huawei for technical
support by telephone or fax.

To shorten fault-handling time, record the 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 5 Record Tables of Emergency
Maintenance.

2.1.2 Collecting Fault Information

This section describes the information to be collected during handling the equipment faults.

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. If the fault is not
solved, use the Emergency Maintenance Note to replace the brief report of the fault.

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".

NOTE

In this version, the default storage path for the system debugging information is "E:\MSSQL\SGData". For the
actual path, refer to the actual installation directory of the system.

These debug log files are crucial to the location of the fault. When the size of these files reaches
a certain threshold, the system auto removes the information saved originally. Therefore, after
the emergent fault occurs, copy and save these files to another place in time.

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. Set the
type and time segment of the alarm to be queried on the pop-up window. Click OK.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-5

2. On the output window of the query result displayed, right click and select Save as?on the
shortcut menu displayed. Then export the alarm log information and save it as a text file.

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 run 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
This section describes the procedures for handling the cabinet or frame breakdown. After
confirming that an emergency fault has occurred to the cabinet or frame, you can check the
equipment and handle the fault according to the following steps.
2.2.2 Handling BAM Breakdown
This section describes the procedures for handling the BAM breakdown. After confirming 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.2.1 Handling Breakdown of Cabinet or Frame

This section describes the procedures for handling the cabinet or frame breakdown. After
confirming that an emergency fault has occurred to the cabinet or frame, you can check the
equipment and handle the fault according to the following steps.

Procedure
Step 1 Checking If Power Supply to Cabinet Is Normal

Power failure in the cabinet leads to the breakdown of the host. To check if the power supply to
the cabinet is normal, follow these methods:

l 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.
l 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.

Step 2 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, to restore the power supply, perform the following steps:

1. To prevent faults, turn off all the power switches 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.

2-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

3. After the power supply system of the equipment room returns to normal, power on and
restart the cabinet based on the methods described in section 4.1 Power-on Operations.
4. When meeting problems during system start or restart, see chapter 3 System Restart for
solutions.

Step 3 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. Important boards, such as the HSYS and SBPI are configured
in the master service frame. Therefore, a power failure in the master service frame directly leads
to the breakdown of the equipment. To check if the power supply to the master service frame is
normal, perform the following steps:
1. 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.
2. 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.
3. IIf 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.

Step 4 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 the breakdown of the HSYSs:

l The "RUN" indicators on the front panels of the active and standby HSYSs are off or
constantly on.
l The "FAIL" indicator on the front panels of the active and standby HSYSs lights up.
l The high-speed bus status indicators "DOMA" and "DOMB" on the front panels of the active
and standby HSYSs are all off.
l The CPU utilizations of the active and standby HSYSs are close to 50% for a long time.

Step 5 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 is running normally. If it is
running abnormally, try to replace the HSYS boards to remove the fault.

Step 6 Collecting Fault Information

Regardless of whether the fault is removed or not, collect the fault information as described in
section 2.1.2 Collecting Fault Information.

----End

2.2.2 Handling BAM Breakdown

This section describes the procedures for handling the BAM breakdown. After confirming 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.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-7

Procedure
Step 1 Checking If Power Supply to BAM Is Normal

A power failure in the BAM leads to a BAM breakdown. To check if the power supply to the
BAM is normal, perform the following steps:

l 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.
l 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.
l 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.

Step 2 Checking If BAM Process Is Normal

The requirements of a normal BAM process are as follows:

l There is no BAM alarm on the alarm console.

l In BAM manager, the status of each process is Started or Stopped instead of Abnormal,
as shown in Figure 2-2.

Figure 2-2 Process status in BAM manager

When the status of a certain process in not Started, you can start the process manually. If it does
not work, proceed the next step.

Step 3 Restarting BAM

If the power supply the BAM is normal but the BAM breaks down, perform the following to
rapidly restore the normal operation of the BAM:

2-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

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.
Step 4 Protecting Site Environment
If you cannot restore the normal operation of the BAM by restarting it, do not perform operations
to the BAM such 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.
Step 5 Collecting Fault Information
Regardless of whether the fault is removed or not, collect the fault information as described in
section 2.1.2 Collecting Fault Information.

----End

2.3 Handling Extremely Heavy Traffic Fault

This section describes the procedures for handling the extremely heavy traffic fault. Since the
equipment is designed with large capacity, extremely heavy traffic does not have much impact
on the transfer and translation of the traffic. 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. To handle the faults, perform the following steps.

Context
NOTE

l Extremely heavy traffic may lead to the congestion of links, SBPU/SBPE, 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.
l 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.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-9

Figure 2-3 Flow of handling extremely heavy traffic faults

Start

Extremely heavy No
traffic fault?

Yes
Clearing activation statistics, Other processing
ccanceling all message tracing flow

Deactivating links of the office

direction, of which the load over the
links constantly exceeds 0.9 Erl.

No Link C has a large

number of messages?

Yes

Deactivating link C

No Opposite plane discards a large

number of messages sent from end
office?

Yes

Modifying data of end office,

directing route to the local system

No Foreground/ background
communication times out?

Yes
Checking correpsonding board

End

2-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Procedure
Step 1 Analyzing Fault Alarm
When a sudden alarm occurs, stay calm, observe the alarm carefully, record it, and analyze its
cause. After confirming that the alarm is caused by extremely heavy traffic, obtain technical
support and at the same time you can perform the following steps.

Step 2 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/SBPE, and HSYS in the foreground and reduce the CPU utilization. After the
statistics console is closed, the statistic data stored by the host in the input/output controller
(IOC) is not sent to the background terminal. Thus, you can reduce the communication load of
the BAM.

Step 3 Canceling All Message Tracing tasks

Run RST TRACE to cancel all message tracing tasks. Run STP ALLMTPTRAC, STP
ALLTRAC, STP M3TRAC, or STP SCTPTRAC to cancel the tracing of the MTP message,
SCCP, maintenance and debugging message, M3UA message, and SCTP message.

NOTE

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.

Step 4 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.
Therefore, you must run DEA N7LKS in the terminal maintenance and test system to deactivate
all the links in the office direction.

Step 5 Handling Faults on Links B and D in Peer Equipment and End Office

When links B and D of the equipment of the peer 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
rises sharply. Therefore, 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 peer equipment is faulty. Therefore,
modify the data of the end office, and direct the corresponding translation point to the local
equipment.

Step 6 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, check engineering information to find the SLPU board
with high load or with links which receive TFP and TFA messages frequently that the links
switch over frequently. After that, pull out the corresponding board to deactivate the links and
reduce the load.

Step 7 Collecting Fault Information

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 2-11

Regardless of whether the fault is removed or not, you must collect the fault information as what
is described in section 2.1.2 Collecting Fault Information.

----End

2-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

3 System Restart

About This Chapter

This chapter describes the system restart. When an emergency fault occurs, you must start/restart
the equipment based on some conditions and general procedures.
3.1 Overview
This section describes the application scope of equipment restart, the tools required, and the
precautions.
3.2 Restart Procedures
This section describes the procedures for restarting the system. After the tools are available and
other conditions are ensured, you can restart the equipment based on equipment restart flow.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-1

3.1 Overview
This section describes the application scope of equipment restart, the tools required, and the
precautions.
3.1.1 Application Scope
This section describes the process of equipment restart and the applicable circumstances.
3.1.2 Device Preparations
This section describes the conditions to be ensured before equipment restart.
3.1.3 Tool Preparations
This section describes the tools to be prepared before equipment restart.

3.1.1 Application Scope

This section describes the process of equipment restart and the applicable circumstances.
l The communications of all input/output devices are interrupted.
l The system cannot normally provide the services, or clear the faults by restarting.
l All boards are faulty.
l The system is in breakdown state.
l The active and standby HSYSs are repeatedly switched over.
l The system is repeatedly loaded.
l Batch programs and data are to be loaded.
NOTE

This document is not applicable to the restart operation in the upgrade.

3.1.2 Device Preparations

This section describes the conditions to be ensured before equipment restart.
l All hardware devices work normally.
l Power supply devices work normally.
l The PDB prompts no alarms.
l The power supply of the PDB works normally.
l The alarm console prompts no power supply alarm.
l Every of the six groups of output voltages of the PDB is -48 V.
l The RUN indicator on the UPWR is ON.

3.1.3 Tool Preparations

This section describes the tools to be prepared before equipment restart.
l Serial port cable
l Network cable
l ESD-preventive wrist strap

3-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

l ESD-preventive glove
l Chip extraction tool
l Straight screwdriver
l Cross screwdriver

3.2 Restart Procedures

This section describes the procedures for restarting the system. After the tools are available and
other conditions are ensured, you can restart the equipment based on equipment restart flow.

Context
Figure 3-1 shows the restart flow. See subsequent sections for details.
As for "BAM faults handling flow" in the figure, see section 2.2.2 Handling BAM
Breakdown for details. For the handling of other faults, see SG7000 Troubleshooting for details.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-3

Figure 3-1 Flow of restarting system

Start

No BAM fault handling flow

BAM works normally?

Yes
No
Device needs restart?

Yes

Software DIP No Prepare to load with

switches of all boards serial port
are queried?
Yes
No
Load program and
data from BAM?

Yes
No Start and set FTP server
FTP server is started?
in BAM manager
Yes

Set software DIP switches

Software DIP switches No

meet requirements?
Yes Back up data

Back up data
Power off and restart
from frame 0
Power off and restart from frame 0

Restart whole frame and

then re-load data through
serial port for boards with
unsatisfactory DIP
switches

No
Link and connection status
is normal?
Yes

Data is consistent in No
host and BAM?
Corresponding fault
Yes handling flow

End

3-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Procedure
Step 1 Device Needs Restart?
If the system encounters hardware or power failure, you must handle it as soon as possible.
See section 3.1.1 Application Scope to decide whether to restart the system when a problem is
met.
Step 2 Software DIP Switches of All Boards Are Queried?
1. Run the following command to query the DIP switches of all boards.
DSP SFTSWT: MODE=ALL;

If the following contents are displayed, it indicates that the DIP switches of all boards are
queried.
RETCODE = 0 Operation succeeded

Soft switch status

------------------
Shelf No. Frame No. Slot No. Location Switch value

0 0 0 Front Not to load data and

program
0 0 1 Front Not to load data and
program
0 0 2 Front Not to load data and
program
0 0 3 Front Not to load data and
program
0 0 4 Front Not to load data and
program
0 0 5 Front Not to load data and
program
0 0 6 Front Not to load data and
program
0 0 10 Front Not to load data and
program
0 0 11 Front Not to load data and
program
0 0 12 Front Not to load data and
program
0 0 0 Up-fasten Not to load data and
program
0 0 1 Up-fasten Not to load data and
program
0 0 2 Up-fasten Not to load data and
program
0 0 3 Up-fasten Not to load data and
program
0 0 5 Up-fasten Not to load data and
program
0 0 10 Up-fasten Not to load data and
program
0 0 12 Up-fasten Not to load data and
program
0 0 0 Down-fasten Not to load data and
program

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-5

0 0 1 Down-fasten Not to load data and

program
0 0 2 Down-fasten Not to load data and
program
0 0 3 Down-fasten Not to load data and
program
0 0 5 Down-fasten Not to load data and
program
0 0 10 Down-fasten Not to load data and
program
0 0 12 Down-fasten Not to load data and
program
2. Query the stratum-2 BOOTROM loading indicators of all boards.
The stratum-2 BOOTROM is re-loaded during the deployment and board replacement.
During system restart, you must determine whether to load the stratum-2 BOOTROM based
on the version number of the stratum-2 BOOTROM.
3. Run DSP EXVERDETAIL to query the version number of the stratum-2 BOOTROM of
the board to be upgraded.
4. Compare the version number of the stratum-2 BOOTROM with the current version number.
If they are not consistent, you must re-load the stratum-2 BOOTROM. To re-load the
stratum-2 BOOTROM, you must start the FTP server in the BAM manager.
5. Run DSP L2BOOT to display the stratum-2 BOOTROM loading indicators of all boards.
If they are not consistent with the actual requirements, run SET L2BOOT to modify.
Step 3 Prepare to Load with Serial Port
For the boards on which the software DIP switches cannot be queried, you must load them
through the serial port. Before loading the boards, prepare as follows:
1. Ensure that the connection between the BAM and the HSYS is normal.
2. Start the FTP server in the BAM manager.
3. Connect the serial port of the BAM to that of the panel of the board to be loaded.
4. Run super terminal on the BAM and click Restore default to set all parameters to the default
values, that is, baud rate to 9600, data bit to 8, parity check to no, stop bit to 1, and stream
control to no.
Step 4 Load Program and Data from BAM?
Determine whether to load the program and the data from the BAM based on the following:
l If the correctness of the program and the data in the board flash memory can be ensured, you
do not need to load from the BAM.
l If the correctness of the program and the data in the board flash memory cannot be ensured,
you are recommended to load from the BAM.
Step 5 FTP Server Is Started?
1. On the Windows desktop, click the BAM manager icon, as shown in

, or select Start > Program > SG7000 Administration

System > SG7000 Server
2. The BAM Manager window is displayed, in which you can query the status of the FTP
server.
l Start: indicating the FTP server is started.

3-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

l Start: indicating the FTP server is stopped and you can start it directly.
l Abnormal: indicating the FTP server is abnormal. In this case, it is suggested to stop all
services and exit the BAM manager, and then start the BAM manager again.
Step 6 Start and Set FTP Server in BAM

In the BAM Manager, select FTP server and then File > Startor click the icon .
After starting the BAM manager, proceed as follows to set it.

Choose an FTP server task, click to open the FTP Server window. Then choose Configure
> Manage Userto display the window as shown in Figure 3-2.

Figure 3-2 FTP Server user management dialog box

The default user name is ioc_down and password is 123 (only *** is displayed). Enter D:
\SGDATA in the Work Path field.
Step 7 Set Software DIP Switches
l During system restart, if the program and data are not to be loaded from the BAM, proceed
the following settings:
SET SFTSWT: MODE=ALL, VAL=0;
l If the program and the data are to be load from the BAM, set the DIP switches based on the
contents in Table 3-1.

Table 3-1 Suggested value for DIP switch

Board Type Suggested Value for DIP Switch

HSYS (main control frame) 224 (loading and saving program and data)

HSYS (expansion frame) 160 (loading and saving program)

SBPU 224 (loading and saving program and data)

SBPE 224 (loading and saving program and data)

SBPI 224 (loading and saving program and data)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-7

Board Type Suggested Value for DIP Switch

SHPE 224 (loading and saving program and data)

SLPU 224 (loading and saving program and data)

SHPU 224 (loading and saving program and data)

SDUI 224 (loading and saving program and data)

Step 8 Software DIP Switches Meet Requirements?

Thirty seconds after running SET SFTSWT, run DSP SFTSWT to query the DIP switches of
all boards to check whether the settings are correct.
If some values of the DIP switches are not correct, you must load them with serial port cable.
Step 9 Back Up Data
1. Run BKB DB to back up the database and registry of the BAM.
BKP DB: BKDIR="D:\UPDATE\BAMBAK";

If nothing is entered in BKDIR field, the database and the registry will be backed up in the
same folder as that of the database log by default, that is, E:\MSSQL\SGDATA.
The name of the backup BAM database is Bam********.dat. In the file name, the symbols
******** stand for the current date, such as 20051221.
The name of the backup registry is BamReg.bak.
2. Run SQL server enterprise manager to back up the Alarm and Stats databases.
On both the BAM and the terminal, back up the BAM, STATS, and ALARM databases.
Choose Start > Program > Microsoft SQL Server > Enterprise Manage.
Choose a database to be backed up (such as Alarm), right click and then choose All tasks
> Backup Database, as shown in Figure 3-3.

3-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 3-3 Choose a database to be backed up

In the displayed dialog box, click Add and enter the backup path and file name. Then click
OK.
After the backup, the system prompts the success. Click OK to finish the backup.
3. Back up loading folder and log folder.
a. Copy all files and sub-folders under the loading folder (default: D:\SGDATA) to a
PC for backing up files.
b. Copy all files and sub-folders under the log folder (default: E:\MSSQL\SGDATA)
to a PC for backing up files.
4. Back up the License file.
Before restart the system, you must back up the License file.
5. Back up the 128BAM.ini file.
The IP addresses of the HSYSs for communication between the host and the BAM are
recorded in the 128BAM.ini file, as shown in Figure 3-4. IP0 indicates the IP address of
the master HSYS and IP1 indicates that of the slave HSYS.
If the IP addresses of the HSYSs can be pinged on the BAM, it indicates that the
communication between the host and the BAM is normal.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-9

Figure 3-4 IP addresses of the HSYSs

6. Back up other data.

The following information should be queried and saved in a file:

l Authority group
l Statistics tasks (including activated and semi-permanent statistics tasks)
l Scheduled tasks (including sub-tasks)
l WS information
l User information

After restarting the system, check the current running data against that saved in the file. If
the data is missing, add it manually.

a. Querying the information of all authority groups (the following is an example for
querying one authority group):
LST CCG: CG=G_1;
b. Querying the information of all WSs:
LST WS:;
You can query the authorities and IP address of a WS based on its name. For example,
to query the authorities and IP address of a WS whose name is 11111, run the following
command:
LST WS: WS="11111";
c. Querying the information of all activated statistics tasks:
LST TRFACT:;
You can query an activated statistics task based on the task number, for example:
LST TRFACT: TSK=0;
d. Querying the information of all activated and semi-permanent statistics tasks:
LST TRFSEMI:;
You can query an activated and semi-permanent statistics task based on the statistics
type (such as LNK), for example:
LST TRFSEMI: OBJ=LNK;

3-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

e. Querying the information of all scheduled tasks:

LST SCHTSK
Querying the information of all subtasks under a scheduled task:
LST SUBTSK

Step 10 Power Off and Restart

Power off all frames from frame 0.
Proceed as follows to power off every frame: Set the switches of POWERA and POWERB
behind the fan box to OFF.
Power on all frames from frame 0.
Proceed as follows to power on every frame: Set the switches of POWERA and POWERB behind
the fan box to ON.
Step 11 Load Certain Boards with Serial Ports
For the boards whose software DIP switches do not meet the requirements, you must load them
through the serial port cable after system power-off and restart.
1. When the super terminal is in shell (->) state, enter btrmValidOkClr and press Enter.
After the system returns "value = 0 = 0x0", enter reboot 2 and press Enter. The board is
restarted from the stratum-1 BOOTROM. You can also continuously press the reset button
of the board for over seven times until the system prompts "Booting from basic bootrom...".
It indicates that the board is restarted from the stratum-1 BOOTROM.
2. During the restart, enter D when the super terminal prompts to input "d" or "D" to enter
shell (->) state. In shell (->) state, enter loadXmodem to load the module.
3. Choose Transfer > Send Fileon the super terminal, as shown in Figure 3-5.
NOTE

To load the IO board, you must ensure that the system board works normally.

Figure 3-5 Transfer file from super terminal

4. The dialog box as shown in Figure 3-6 is displayed. For the system board, the file name
is sysbios.hdr and for the IO board, the file name is iobios.hdr. Choose Xmodem for the
protocol. Then click Send. It takes about 30 seconds for the super terminal to load the file
to the board over the Xmodem protocol.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-11

Figure 3-6 Choose file name and protocol

After successful loading, the super terminal prints the success prompt.
5. After three seconds, the board is auto reset and loaded with the stratum-2 BOOTROM.
During the reset, the system prompts to input "d" or "D" and you just ignore it. After loading
the stratum-2 BOOTROM, the board is restarted directly from the stratum-2 BOOTROM.
The system prompts "Booting from extended bootrom...." The file name of the stratum-2
BOOTROM of the system board is hsys.bin and that of the IO board is sbpx.bin.
6. After the board works normally, run DSP EXVER on the BAM to query whether the current
version is that to be loaded. If the loading fails, the ALM indicator is always ON. In this
case, you must locate the problem based on the printed information.
Step 12 Link and Connection Status Is Normal?
Proceed as follows to check the system status and handle the problem based on the specific flow
if there is any fault.
1. Query the board status.
The board status should be any of the following:
l Normal
l Master normal
l Backup normal
l Uninstall (for empty slot)

The board is abnormal if its status is any of the following:

l Failure
l Abnormal

For example:
DSP FRM:;

Shelf 0 Frame 0 Card status

----------------------
Shelf No. Frame No. Slot No. Location Board type Board Status

0 0 0 Front SBPU Normal

0 0 1 Front SBPU Normal
0 0 2 Front SBPU Normal
0 0 3 Front SBPU Normal
0 0 4 Front SBPI normal

3-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

0 0 5 Front SBPU Normal

0 0 6 Front HSYS Master
normal
0 0 7 Front <NULL> Uninstall
2. Query the status of the network ports of the SBPI.

The Network port status should be Normal.

For example:
DSP BRD: FN=0, SHN=0, SN=5, LOC=FPB;

%%DSP BRD: SHN=0, FN=0, SN=5, LOC=FPB;%%

RETCODE = 0 Operation succeeded
SBPI board
--------
Shelf No = 0
Frame No = 0
Slot No = 5
Location = Front
Board type = SBPI
Board Status = Normal
Run time = 101

The versions of all boards should be the same.

For example:
DSP EXVERDETAIL: METHOD=ALL;
4. Query the status of the link.

For example:
DSP MULN7LNK: ST=0, EN=500;

The Failure state of the link should be NO.

5. Query the status of the link set.

For example:
DSP MULN7LKS: ST=0, EN=500;

The Failure state of the link set should be NO.

6. Query the status of the route.

For example:
DSP MULN7RT: ST=0, EN=500;
7. Query the status of the DSP.

For example:
DSP MULN7DSP: ST=0, EN=500;

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-13

Step 13 Data Is Consistent in Host and BAM?

1. Check data consistency.
Normally, all data should be in "Consistent" state.
For example:
ACT CNSCHK:;

%%ACT CNSCHK:;%%
RETCODE = 0 Operation succeeded
Result of data consistency check
------------------
Data of HSYS and BAM = All consistent
Data of backup HSYS and HSYS = All consistent
Data of MTP = All consistent
All data in tables = Consistent
--- END

If the data on the HSYS is inconsistent with that on the BAM, you can run RST DBTBL
to restore the equipment data of the BAM by using the data store in the FLASH of the active
HSYS.
If the data on the boards of the host is inconsistent, you can run RST TBL to restore the
equipment data of other boards by using the data store in the FLASH of the active HSYS.

NOTE

Only limited data can be restored when you run RST TBL each time. In this case, you must run the
command many times to restore all the data.
2. Check service data consistency.
Normally, all service data should be in "All consistent" state.
For example:
ACT SERCNSCHK: TBLID=ALL;

%%ACT SERCNSCHK: TBLID=ALL;%%

RETCODE = 0 Operation succeeded

Result of data consistency check

==================
SIMM software configuration information table = All consistent
SIMM MAP-SERVER function table = All consistent
SIMM Virtual roaming Number segment table = All consistent

3-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

SIMM region VLR number segment table = All consistent

SIMM VLR number segment table = All consistent
SIMM IMSI number segment table = All consistent
SIMM user table = All consistent
SIMM MSC number segment table = All consistent
SIMM secretary station number table = All consistent
MNP software configuration information table = All consistent
MNP route number table = All consistent
Service user number segment table = All consistent
RBT virtual roaming number table = All consistent
RBT province VMSC number segment table = All consistent
RBT software configuration information table = All consistent
Service user table = All consistent
Calling B&W list table = All consistent
Called B&W list table = All consistent
Calling trans number table = All consistent
Called trans number table = All consistent
CPC table = All consistent
Number operation table = All consistent
DSP index reference table = All consistent
MNP HLR Address table = All consistent
Foreign number range table = All consistent
IUA linkset table = All consistent
IUA link table = All consistent
Extended destination IP address table = All consistent
Extended destination IP address combination table = All consistent
Extended access control table = All consistent
SMSC address mapping table = All consistent
Virtual SMSC address table = All consistent
Operator number range table = All consistent
Dummy number table = All consistent
SMS configuration table = All consistent
RBT GT number range shield table = All consistent
RBT user number range shield table = All consistent
IMEI Catch configuration table = All consistent
Word crest anaylse table = All consistent
MNP VMSRN range table = All consistent
MNP VMSC range table = All consistent
Sub Msisdn Table = All consistent
MC Local SC Address Table = All consistent
MC Routing Number Table = All consistent
MNP LOCAL NETWORK NUMBER RANGE TABLE = All consistent
MNP SPECIAL PREFIX NUMBER TABLE = All consistent
MNP PREFIX MAPPING MANAGEMENT TABLE = All consistent
--- END

If the service data in the host is inconsistent with that on the BAM, you can run ACT
SERCNSCHK and set RESTORE to YES to restore the data on the BAM. After that, run
ACT SERCNSCHK to check whether the data is consistent.

----End

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 3-15

4 Related Operations of Emergency

Maintenance

About This Chapter

This chapter describes the related operations of the emergency maintenance, including power-
on operations, pulling out and inserting boards, resetting operations, BAM emergency handling,
and database backup and recovery.
4.1 Power-on Operations
This section describes the power-on operations. For the purpose of commissioning, or due to
equipment fault or power supply failure, you must restart the system by the power-on operation.
4.2 Pulling Out and Inserting Boards
This section describes the procedures for pulling out and inserting a board.
4.3 Resetting Operations
This section describes the resetting operations. Based on the reset object, resetting operations
can be classified into frame resetting and board resetting.
4.4 Handling BAM Failure
This section describes the procedures for handling the BAM failure. The EWS can act as a BAM
or a local WS. When the BAM is down, you can use the EWS to replace it.
4.5 Backing Up and Recovering Database
This section describes the procedures for backing up and recovering the BAM database. The
BAM database is also called the background database. It is an SQL database stored in the hard
disk of the BAM in the format of a data table. Its main function is to store all types of data
generated during data configurations.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-1

4.1 Power-on Operations

This section describes the power-on operations. For the purpose of commissioning, or due to
equipment fault or power supply failure, you must restart the system by the power-on operation.
Before the power-on, you must clearly understand the structure of the power supply system (see
6 Power Supply System of Cabinet), carefully read what is specified in this chapter, and deeply
study the power-on procedures.
4.1.1 Powering On and Restarting Cabinet
This section describes the situations and procedures for powering on and restarting a cabinet.
4.1.2 Powering On and Restarting Frames
This section describes the situations and procedures for powering on and restarting a frame.

4.1.1 Powering On and Restarting Cabinet

This section describes the situations and procedures for powering on and restarting a cabinet.

Prerequisite
Cabinets should be powered on and restarted only in the following situations:
l During deployment or expansion, it is necessary to perform power-on test to the equipment
after completing the installation of all hardware.
l During important upgrading of software or hardware, it is necessary to power off the
devices, and then power them on again.
l 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.

Procedure
Step 1 Powering on the DC distribution cabinet
Turn on all switches on the DC power distribution box (PDB) of the equipment. The "RUN"
indicator on the panel of the PDBs should be on (green). It should blink twice every second,
indicating that the input power supply and internal circuits of the PDB are normal.
Step 2 Powering on PDB of main control cabinet
Turn on the switches on the PDB of the main control cabinet one by one, that is, to turn the
switches to "ON" in turn from SW1 to SW6(PDB DPD100-2-6) or from A1/B1 to A10/B10
(PDB DPD100-2-20). 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.
Step 3 Powering on LAN Switch 0 and LAN Switch 1
Turn on the switches of LAN Switch 0 and LAN Switch 1 in the main control cabinet one by
one, that is, to turn the switches of the LAN Switches to "ON". 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.
Step 4 Powering on KVM/LCD converter
Turn on the switch of the KVM (keyboard, video, mouse)/LCD (liquid crystal display) converter
in the main control cabinet, that is, to turn the switch to the side with a "-" symbol. The "KVM/

4-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

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

Step 5 Powering on the server

To start the server, the following procedures must be carried out:

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. The indicator of the switch will turn to green, indicating
a normal power supply of the server.

Step 6 Powering on slave service frames

Turn on the switches on the PDB of the cabinet one by one, that is, to turn the switches on the
PDB to "ON" in the order of SW1 to SW6(PDB DPD100-2-6) or of A1/B1 to A10/B10(PDB
DPD100-2-20). 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.

Step 7 End of operation

After the above operations, check the running status of the components in the cabinet carefully
to ensure there is no abnormality. This completes the power-on operation.

----End

4.1.2 Powering On and Restarting Frames

This section describes the situations and procedures for powering on and restarting a frame.

Prerequisite
Frames should be powered on and restarted only in the following situations:

l The active and standby HSYSs in the frame are faulty or down.
l 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.

Procedure
Step 1 Confirming Electrical Controlling Relationships

Since the power supply of each frame is controlled by the two switches on the PDB, and the
controlling relationships are different, confirm electrical controlling relationships between the
PDB and the components in the cabinet carefully to avoid maloperations.

Step 2 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 PDB one by one. The indicators on all the boards of the frame should
be off, indicating power-off of the frame.

Step 3 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 PDB one by one. That is, turn the switches to "ON". The power module

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-3

indicators "PWR" on all the ALUIs of the frame should be on (green), indicating the frame has
been powered on again.
Step 4 End of Operation
After completing the power on 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
complete the power-on operation.
----End

4.2 Pulling Out and Inserting Boards

This section describes the procedures for pulling out and inserting a board.

Context
NOTE

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 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.

Procedure
Step 1 Wear an ESD-preventive wrist strap. Insert its grounding terminal into the ESD jack of the rack.
Step 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 4-1.
Step 3 Hold the upper and lower ejector levers with 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.
Step 4 Press outward the ejector levers hard with both hands. When the two ejector levers form an angle
of 45 degree, the board connectors break away from the backplane, as shown by step (b) in
Figure 4-1.

Figure 4-1 Pull out a board from a frame

4-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Step 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.

Step 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.

Step 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.

Step 8 To check the status of the board, perform the following steps:
1. If the "RUN" indicator on the front panel of the board is on and blinks regularly, it indicates
that the board is running normally.
2. 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.
3. 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.

----End

Postrequisite
If the board is running abnormally, replace it. For details, refer to SG7000 Parts Replacement
Guide.

4.3 Resetting Operations

This section describes the resetting operations. Based on the reset object, resetting operations
can be classified into frame resetting and board resetting.
4.3.1 Resetting Boards
This section describes the situations and procedures for resetting a board.
4.3.2 Resetting Frames
This section describes the situations and procedures for resetting a frame.

4.3.1 Resetting Boards

This section describes the situations and procedures for resetting a board.

Prerequisite
NOTE

The boards can be reset only in the following situations:

l The board is faulty or down. In this case, you can reset the board directly.
l 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.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-5

If the board to be reset is an HSYS, use the BKP DB command to back up the BAM data before
resetting the board.

Procedure
Step 1 Three ways are available for resetting a board. You can choose a proper way based on actual
conditions.
l Resetting Boards Using RST BRD Command
During upgrade of the software, you can run RST BRD 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;
l 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.
l 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.

----End

4.3.2 Resetting Frames

This section describes the situations and procedures for resetting a frame.

Prerequisite
NOTE

The frames are reset in the following situations:

l All the boards in the frame are faulty or down.
l The major software upgrade is to be implemented.

Before resetting a frame, use the BKP DB command to back up the BAM data.

Procedure
Step 1 Two ways are available for resetting a frame. You can choose a proper way based on actual
conditions.
l 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.
l Resetting a Frame by Pulling Out and Inserting the Active and Standby HSYSs
When all boards in a frame are faulty or breakdown, you can reset the frame through pulling
out and then inserting the active and standby HSYSs if method 1 does not work.

----End

4-6 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

4.4 Handling BAM Failure

This section describes the procedures for handling the BAM failure. The EWS can act as a BAM
or a local WS. When the BAM is down, you can use the EWS to replace it.
The EWS is connected to the BAM. The EWS backs up the data in the BAM at regular intervals
(every four hours by default). Once the BAM is down, you can use the EWS to replace it.
4.4.1 Starting the EWS
This section describes the procedures for starting the EWS. The EWS can act as a common WS
when the BAM is running normally. When the BAM is down, you can use the EWS to replace
it.
4.4.2 Restoring the BAM
This section describes the procedures for restoring the BAM. After you have repaired the BAM,
you can use it again. In this case, you need to replace the EWS with the BAM.

4.4.1 Starting the EWS

This section describes the procedures for starting the EWS. The EWS can act as a common WS
when the BAM is running normally. When the BAM is down, you can use the EWS to replace
it.

Procedure
Step 1 Restoring the Data in the EWS
Restoring the data in the EWS is the same as that in the BAM. For details, see section 4.5 Backing
Up and Recovering Database of this manual.
Step 2 Starting the BAM System of the EWS
After being restarted, the EWS does not start the BAM system automatically. You need to
proceed as follows to start the BAM system.
1. Start the BAM Manager.
Choose Start > Programs > SG7000 Administration System > SG7000 Server. The
BAM Manager window is displayed as shown in Figure 4-2.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-7

Figure 4-2 BAM Manager

2. Copy the License file.

Obtain the License file from a Huawei technical support engineer. Copy the file to D:
\SG7000\SERVICES.
3. Run the MML command (SET OPMODE) to enter the offline status.
4. Run the MML command (FMT) to convert the format of all data.

Step 3 Changing Network Connections

Proceed as follows to disconnect the BAM from the host and connect the EWS to the host:

1. Disconnect the Ethernet cables connecting the BAM.

2. Set the IP address of the EWS to the same as that of the BAM..
3. In the cabinet with the BAM, insert the Ethernet cables of the EWS into the 100 Mbit/s
Ethernet interfaces of the LAN Switch used by the host.
NOTE

l When the BAM is working, the EWS and other common WSs are connected to a LAN Switch. The host is
connected to the other LAN Switch. The BAM is connected to the two LAN Switches through two network
adapters.
l When the EWS replaces the BAM, the EWS and the host use the same LAN Switch.

Step 4 Checking Data

To check the data consistency between the host and the EWS, proceed as follows:
1. Use ACT CNSCHK to check the data consistency. If inconsistency exists, use RST
DBTBL or RST TBL to restore the data. Use the two commands according to the following
rules:
l If inconsistency of equipment data exists, run RST DBTBL to use the host equipment
data to recover the EWS data.

4-8 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

l If inconsistency of board data in the host exists, run RST TBL to use the data saved in
the HSYS to recover the data of the other boards.
2. If service data exist, use ACT SERCNSCHK to check their consistency. If inconsistent
service data exist, set the parameter Whether restore it in the command to yes to recover
the data.
3. If inconsistency still exists, record the names of the inconsistent tables and contact a Huawei
technical support engineer.
4. After you have confirmed that all data tables and service tables are correct, run the command
(SET OPMODE) to start the EWS.

Step 5 Verifying the Running Status of the EWS

To verify whether the EWS has been started successfully, query the hardware configuration
panel and alarm information on the EWS.

----End

4.4.2 Restoring the BAM

This section describes the procedures for restoring the BAM. After you have repaired the BAM,
you can use it again. In this case, you need to replace the EWS with the BAM.

Procedure
Step 1 Backing Up the Data in the EWS

It includes the backup of system data and registry on the EWS.

You can use BKP DB to back up system database and registry. The name of the database backup
file is BamYYYYMMDD.dat. The name of the registry file is BamReg.bak. The two files are
backed up to the E:\MSSQL\SGDATA path. Keep another copy of the two files in another
folder.

NOTE

Before starting the BAM again, you must back up the system data of the EWS and then restore the EWS to the
SGSmirror backup mode. The reason is as follows. After started, the SGSmirror process of the EWS checks the
backup files in the EWS and the source files in the BAM to ensure their consistency (mirror backup). That is,
when files are removed from or added to the BAM, the same files are removed from or added to the EWS.

Step 2 Restoring the EWS to a Common WS

Proceed as follows:

1. Stop BAM Manager. That is, click Exit on the left of the tool bar of BAM Manager. Or
choose File > Exit and then click OK when the system prompts "Are you sure that you
want to exit?"
2. Stop all application programs on the EWS.
3. Disconnect the EWS from the host. Change the IP address of the EWS back to the original
one.
4. Restore the network connections of the EWS with the original network. The EWS starts to
work as a common WS.
NOTE

Do not connect the BAM to the host before you have restored the data in the BAM.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-9

Step 3 Restoring BAM Data

Proceed as follows:

1. Copy the latest backup files of system data and registry files from the EWS to E:\MSSQL
\SGDATA of the BAM.
2. To restore the data in the BAM, see related contents in section 4.5 Backing Up and
Recovering Database of this manual.

Step 4 Reconnecting the BAM to the Host

Proceed as follows:

1. After restarting the BAM, convert the data format and set the online mode.
2. Insert the network cables of the BAM into the 100 Mbit/s Ethernet interfaces of the LAN
Switch(es) used by the host.
NOTE

Step 5 Check the Running Status of the BAM and EWS

To verify whether the BAM and emergency WS are working, query the hardware configuration
status and alarm information on them.

----End

4.5 Backing Up and Recovering Database

This section describes the procedures for backing up and recovering the BAM database. The
BAM database is also called the background database. It is an SQL database stored in the hard
disk of the BAM in the format of a data table. Its main function is to store all types of data
generated during data configurations.
4.5.1 Automatic Backup of Database
This section describes the automatic backup of the database. The system automatically backs
up the database every day in order to recover the data in time in case of sudden equipment failure.
4.5.2 Manual Backup of Database
This section describes the manual backup of the database. Under special situations such as the
expansion, upgrading and loading, you must back up the BAM database and the registry
manually before the upgrading or loading.
4.5.3 Safe Data Recovery
This section describes the 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.

4.5.1 Automatic Backup of Database

This section describes the automatic backup of the database. The system automatically backs
up the database every day in order to recover the data in time in case of sudden equipment failure.

4-10 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

At 4:30 a.m. (default time) every day, the system automatically backs up the BAM database and
the registry to the default directory E:\MSSQL\SGDATA.

NOTE

l 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.
l Ensure that the disk has adequate space.
l Twenty-two backup devices are required 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).
l Automatic backup of the BAM database
l The backup of the BAM database is performed in a cyclic manner. Up to eleven database
files can be backed up. The backup file of the BAM database includes the following
contents.
l 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.
l Saving the database backup of the four Sundays of the past 28 days,
"BamYYYYMMDD.dat" is the file name of these four files.
l On the first day of each month, a BAM database backup has been stored in a file
"BamMonthBak.dat".
l Automatic backup of the BAM registry
l 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.

4.5.2 Manual Backup of Database

This section describes the manual backup of the database. Under special situations such as the
expansion, upgrading and loading, you must back up the BAM database and the registry
manually before the upgrading or loading.

Backup Mode
Two modes are available for manual backup:

l Command Mode (BKP DB)

l Use Tool Menu of Enterprise Manager of SQL Server

To perform the backup through the command is very easy. In the MML client of the service
maintenance system, run BKP DB to back up the current BAM database and the registry to the
default directory E:\MSSQL\SGDATA.

The following section details the mamual backup through the tool menu of the Enterprise
Manager of the SQL Server.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-11

Procedure
Step 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 4-3.

Figure 4-3 SQL Server enterprise manager

Step 2 Assume 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 4-4.

4-12 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 4-4 Window of data backup operation

Step 3 Click All Tasks -> Backup Database to pop up a window as shown in Figure 4-5. 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. 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 4-6.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-13

Figure 4-5 Select database and backup mode

Figure 4-6 Choose backup destination

Step 4 As shown in Figure 4-7, 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.

4-14 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 4-7 Set the data overwriting mode

Step 5 The system backs up the data after confirmation. Moreover, an interface displaying the backup
progress appears as shown in Figure 4-8.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-15

Figure 4-8 Data backup progress of the system

Step 6 When the system has successfully backed up the data, it displays a success prompt.
NOTE

l When BKP DB is carried out 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.
l 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.

----End

4.5.3 Safe Data Recovery

This section describes the 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.

Procedure
Step 1 Quitting All BAM Processes
Step 2 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 Server's access to 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 displays a dialog box as shown in Figure 4-9.

4-16 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 4-9 SQL Server service manager

2. Click to stop the SQL Server program. Then the system displays a dialog box. Click
Yes to interrupt the communication between the foreground and the background.

3. Click in Figure 4-9 to restart the SQL Server.

Step 3 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 4-10, select Bam in the Restore as database field and
From device in the Restore field. Recover the data setting according to actual situations
(complete database recovery, recovery of different 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.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-17

Figure 4-10 Select a database to be recovered

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

4-18 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 4-11 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 4-12.

Figure 4-12 Select the equipment to be recovered

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.

----End

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 4-19

Postrequisite
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.

4-20 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

5 Record Tables of Emergency Maintenance

About This Chapter

This appendix describes the usage of the records tables for the emergency maintenance.
5.1 Emergency Maintenance Note
This section describes the 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.
5.2 Troubleshooting Record Table
This section describes the usage of the troubleshooting record table for the emergency
maintenance.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-1

5.1 Emergency Maintenance Note

This section describes the 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.

The following contents are to be filled by customer in detail

Office name Equip Capacity

ment
type

Complainer Contac Version

t
telepho
ne

Date and time Respon Whether it has □ Yes

ding passed the □ No
date warranty
and period
time
require
d

Description of the fault(s) and handling processes (in detail):

Auditor:
Stamp (your department):

The following contents are to be filled by Huawei

Handling method □by telephone

□ by remote maintenance
□ by on-site support

Results (additional pages can be attached)

Operator:
Date:

Unsolved problems:

Note: This table is to be stamped by the operation and maintenance department.

5-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

5.2 Troubleshooting Record Table

This section describes the usage of the troubleshooting record table for the emergency
maintenance.
Name of equipment: IP address: Maintenance date:

Occurrence time: Solving time:

Person on duty: Handling person:

Category of fault:
□ Hardware fault
□ Power supply fault
□ Clock fault
□ Hardware fault
□ Power supply fault
□ FE/E1 interface fault
□ Transmission network fault
Trunk link fault:
□ Fault in communication between foreground and background
□ User terminal fault
□ MTP link fault
Other faults:

Source of fault:
□ Customer complaint
□ Alarm system
□ Found in routine maintenance
Other sources:

Description of fault:

Handling method and result:

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 5-3

6 Power Supply System of Cabinet

About This Chapter

This appendix describes the power supply loops in a PDB or cabinet.

6.1 Power Supply Loop of Power Distribution Frame
This section describes the power supply loops in a PDB. Each SG7000 cabinet is powered by
two -48 VDC power supplies. The power supply for the parts in the cabinet is controlled by the
PDB at the top of the cabinet.
6.2 Power Supply Loop in Cabinet
This section describes the power supply loops in a cabinet. The SG7000 has two types of
cabinets: main control cabinet and expansion cabinet. Because different types of cabinets have
different parts, their primary power supply system loops (namely -48 V power supply systems)
are different.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-1

6.1 Power Supply Loop of Power Distribution Frame

This section describes the power supply loops in a PDB. Each SG7000 cabinet is powered by
two -48 VDC power supplies. The power supply for the parts in the cabinet is controlled by the
PDB at the top of the cabinet.
The power supply of the PDB is as shown in Figure 6-1(DPD100-2-6) or Figure 6-2
(DPD100-2-20).

Figure 6-1 Power supply of the PDB(DPD100-2-6)

Figure 6-2 Power supply of the PDB(DPD100-2-20)

-48V1

-48V2

PDB

…… ……

A1 A2 A10 B1 B2 B10

To increase the reliability of the power supplies in the cabinet, the PDB uses a large power diode
to combine the two input power supplies into one. Then the power supply is exported to the six
switches on the panel of the PDB through one power bus cable. These switches help to supply
the power for the parts in the cabinet through a power distribution system. In this way, when
one input power supply fails, the other can power the parts in the cabinet through the PDB.

6.2 Power Supply Loop in Cabinet

This section describes the power supply loops in a cabinet. The SG7000 has two types of
cabinets: main control cabinet and expansion cabinet. Because different types of cabinets have

6-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

different parts, their primary power supply system loops (namely -48 V power supply systems)
are different.
The LAN Switch 0, LAN Switch 1, and the KVMS in the basic cabinet are controlled by a power
switch, while the other parts are powered by the two switches on the PDB.
The relations between the PDB and the parts in the cabinet are as shown in Table 6-1.

Table 6-1 Relations between cabinet parts and controlling switches

Cabinet type Part Controlling switch Controlling
(DPD100-2-6) switch
(DPD100-2-20)

Basic cabinet BAM SW3, SW5 A1, B1

FIREWALL 1 SW1 B4

FIREWALL 0 SW2 A4

LANSWITCH 3 SW1 B5

LANSWITCH 2 SW3 A5

LANSwitch0 SW2 A6

LANSwitch1 SW3 B6

KVM/LCD SW6 A7

Master service frame 0 SW4, SW5 A2, B2

Slave service frame 1 SW4, SW6 A3, B3

Extension Slave service frame 3 SW1, SW2 A4, B4

cabinet
Slave service frame 2 SW2, SW3 A3, B3

Slave service frame 1 SW3, SW4 A2, B2

Slave service frame 0 SW5, SW6 A1, B1

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 6-3

7 Acronyms and Abbreviations

A
AS Application Server
ALUI Alarm Unit Interface board

B
BAM Back Administration Module

D
DPC Destination Point Code

L
LAN Local Area Network
LCD Liquid Crystal Display

K
KVM Keyboard, Video, Mouse

M
MML Man-Machine Language
MTP Message Transfer Part

N
NGN Next Generation Network

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 7-1

P
PDB Power Distribution Box

S
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

T
TFA TransFer-Allowed signal
TFP TransFer-Forbidden signal

W
WS Work Station

7-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

SG7000 Basic Operations (V200R005C02 - 02)
No ratings yet
SG7000 Basic Operations (V200R005C02 - 02)
71 pages
SG7000 Configuration Examples (V200R005C02 - 02)
No ratings yet
SG7000 Configuration Examples (V200R005C02 - 02)
73 pages
SG7000 Data Configuration (V200R005C02 - 02)
No ratings yet
SG7000 Data Configuration (V200R005C02 - 02)
385 pages
SG7000 Compliance and Safety (V200R005C02 - 02)
No ratings yet
SG7000 Compliance and Safety (V200R005C02 - 02)
36 pages
SG7000 Hardware Description (V200R005C02 - 02)
No ratings yet
SG7000 Hardware Description (V200R005C02 - 02)
185 pages
SG7000 Feature Description (V200R005C02 - 02)
No ratings yet
SG7000 Feature Description (V200R005C02 - 02)
493 pages
Annex1 U-SYS SG7000 Signaling Gateway Product - Description
100% (1)
Annex1 U-SYS SG7000 Signaling Gateway Product - Description
114 pages
GSM Troubleshooting Guide
No ratings yet
GSM Troubleshooting Guide
468 pages
RRU5904&RRU5904w&RRU5304&RRU5304w Hardware Description (04) (PDF) - en
No ratings yet
RRU5904&RRU5904w&RRU5304&RRU5304w Hardware Description (04) (PDF) - en
43 pages
Huawei Series Ethernet Switches Alarm Handling S2750&5700&6700 PDF
No ratings yet
Huawei Series Ethernet Switches Alarm Handling S2750&5700&6700 PDF
946 pages
GBSS13.0 Troubleshooting Guide (02) (PDF) - en
No ratings yet
GBSS13.0 Troubleshooting Guide (02) (PDF) - en
381 pages
Rru5901&Rru5901w&Rru5301 (2.6g) &rru3971a Hardware Description (05) (PDF) - en
No ratings yet
Rru5901&Rru5901w&Rru5301 (2.6g) &rru3971a Hardware Description (05) (PDF) - en
43 pages
RRU5905&RRU5905w&RRU5305 (1.4G) Hardware Description (06) (PDF) - en
No ratings yet
RRU5905&RRU5905w&RRU5305 (1.4G) Hardware Description (06) (PDF) - en
46 pages
RRU5901&RRU5901w&RRU5301&RRU3971a Hardware Description (04) (PDF) - EN
No ratings yet
RRU5901&RRU5901w&RRU5301&RRU3971a Hardware Description (04) (PDF) - EN
39 pages
CBSS Configuration and Adjustment Guide (CBSS9.0 - 01) (PDF) - en
No ratings yet
CBSS Configuration and Adjustment Guide (CBSS9.0 - 01) (PDF) - en
475 pages
HUAWEI USG6000 Series & NGFW Module V100R001 Administrator Guide 04
No ratings yet
HUAWEI USG6000 Series & NGFW Module V100R001 Administrator Guide 04
4,895 pages
Product Description (V800R009C10 - 01) PDF
No ratings yet
Product Description (V800R009C10 - 01) PDF
60 pages
RRU3838 Amp Amp RRU3839 Amp Amp RRU3958 Hardware Description 10 PDF - en
No ratings yet
RRU3838 Amp Amp RRU3839 Amp Amp RRU3958 Hardware Description 10 PDF - en
39 pages
Huawei Usg6000v v500r001c10spc100 Administrator Guide
No ratings yet
Huawei Usg6000v v500r001c10spc100 Administrator Guide
3,169 pages
SG7000 Maintenance Manual-Emergency Maintenance PDF
No ratings yet
SG7000 Maintenance Manual-Emergency Maintenance PDF
45 pages
BSC6900 GSM Site Maintenance Guide
No ratings yet
BSC6900 GSM Site Maintenance Guide
193 pages
Emergency Hardware Maintenance (V600R001C00 03)
No ratings yet
Emergency Hardware Maintenance (V600R001C00 03)
87 pages
BSC6910 SAU User Guide (EBC&EMS Service Components) (V100R021C10 - 02) (PDF) - EN
No ratings yet
BSC6910 SAU User Guide (EBC&EMS Service Components) (V100R021C10 - 02) (PDF) - EN
151 pages
Hardware Description: Issue 02 Date 2018-02-06
No ratings yet
Hardware Description: Issue 02 Date 2018-02-06
133 pages
HUAWEI SIG9800 V300R001C00 Configuration Guide 01 PDF
No ratings yet
HUAWEI SIG9800 V300R001C00 Configuration Guide 01 PDF
1,010 pages
RRU3832&RRU3632 Hardware Description (02) (PDF) - EN
No ratings yet
RRU3832&RRU3632 Hardware Description (02) (PDF) - EN
38 pages
BSC6900 GSM Technical Description (V900R012C01 - 02)
No ratings yet
BSC6900 GSM Technical Description (V900R012C01 - 02)
113 pages
Bsc6900 Installation
100% (2)
Bsc6900 Installation
163 pages
IPCLK1000 User Guide
No ratings yet
IPCLK1000 User Guide
119 pages
IPCLK1000 User Guide PDF
No ratings yet
IPCLK1000 User Guide PDF
119 pages
HUAWEI GSM Base Station Subsystem BSS Fe
No ratings yet
HUAWEI GSM Base Station Subsystem BSS Fe
101 pages
3900 Series Base Station RFU Hardware Description (V100R013C10 - 01) (PDF) - en
No ratings yet
3900 Series Base Station RFU Hardware Description (V100R013C10 - 01) (PDF) - en
64 pages
RRU3953&RRU3953w Hardware Description (02) (PDF) - en
No ratings yet
RRU3953&RRU3953w Hardware Description (02) (PDF) - en
37 pages
E RAN
100% (2)
E RAN
137 pages
RRU3936 Hardware Description (12) (PDF) - EN
No ratings yet
RRU3936 Hardware Description (12) (PDF) - EN
48 pages
14 WLAN Typical Configuration Examples PDF
No ratings yet
14 WLAN Typical Configuration Examples PDF
2,135 pages
RRU3952 (850M) Hardware Description (Draft C) (PDF) - EN PDF
No ratings yet
RRU3952 (850M) Hardware Description (Draft C) (PDF) - EN PDF
41 pages
IPCLK1000 User Guide PDF
No ratings yet
IPCLK1000 User Guide PDF
126 pages
NCE V100R018C10 Command Reference (Restricted) 01-C
No ratings yet
NCE V100R018C10 Command Reference (Restricted) 01-C
266 pages
RRU3908 V2 Hardware Description (V100R002C00 - 03)
No ratings yet
RRU3908 V2 Hardware Description (V100R002C00 - 03)
47 pages
User Manual 2536672
No ratings yet
User Manual 2536672
37 pages
APM30H&TMC11H&IBBS200D&IBBS200T (Ver.B) User Guide (V200R303 - 07) - 20101109-B-1.0 PDF
No ratings yet
APM30H&TMC11H&IBBS200D&IBBS200T (Ver.B) User Guide (V200R303 - 07) - 20101109-B-1.0 PDF
218 pages
RRU3832&RRU3632 Installation Guide (07) (PDF) - EN
No ratings yet
RRU3832&RRU3632 Installation Guide (07) (PDF) - EN
131 pages
BSC6910 Spare Parts Catalog (V100R017C10 - Draft A) (PDF) - EN
No ratings yet
BSC6910 Spare Parts Catalog (V100R017C10 - Draft A) (PDF) - EN
24 pages
EG860 User Guide (V200R003C00 - 02) (PDF) - EN
0% (1)
EG860 User Guide (V200R003C00 - 02) (PDF) - EN
124 pages
BSC6910 GSM Commissioning Guide (V100R015C00 - 02) (PDF) - en
No ratings yet
BSC6910 GSM Commissioning Guide (V100R015C00 - 02) (PDF) - en
81 pages
eNodeB Technical Description (V100R004C00 - 03) (PDF) - EN PDF
100% (2)
eNodeB Technical Description (V100R004C00 - 03) (PDF) - EN PDF
107 pages
UMTS Radio Access Network Documentation Guide
No ratings yet
UMTS Radio Access Network Documentation Guide
42 pages
User Manual RRU
No ratings yet
User Manual RRU
40 pages
Apm30h&Tmc11h&Ibbs200d&Ibbs200t (Ver.b) User Guide (v200r303 - 11)
No ratings yet
Apm30h&Tmc11h&Ibbs200d&Ibbs200t (Ver.b) User Guide (v200r303 - 11)
219 pages
IPCLK1000 User Guide
No ratings yet
IPCLK1000 User Guide
117 pages
Bsc6910 GSM Installation Guide (v100r015c00 - 03) (PDF) - en
No ratings yet
Bsc6910 GSM Installation Guide (v100r015c00 - 03) (PDF) - en
101 pages
EG860 User Guide (V200R002C00 - 06) (PDF) - EN
No ratings yet
EG860 User Guide (V200R002C00 - 06) (PDF) - EN
110 pages
Bts3606ce Bts3606ac Cdma PDF
No ratings yet
Bts3606ce Bts3606ac Cdma PDF
70 pages
Fat AP and Cloud AP V200R019C00 Command Reference PDF
No ratings yet
Fat AP and Cloud AP V200R019C00 Command Reference PDF
4,890 pages
Huawei Igwb User Manual
No ratings yet
Huawei Igwb User Manual
68 pages
01-2 Installation Guide
No ratings yet
01-2 Installation Guide
335 pages
Commissioning Guide - (V200R008C02 01, NGN)
No ratings yet
Commissioning Guide - (V200R008C02 01, NGN)
148 pages
Feature Description - (V200R008C02 01, NGN)
No ratings yet
Feature Description - (V200R008C02 01, NGN)
432 pages
00-2 About This Document
No ratings yet
00-2 About This Document
10 pages
User Manual: Huawei Igwb
No ratings yet
User Manual: Huawei Igwb
3 pages
02 Part
No ratings yet
02 Part
4 pages
User Manual: Part 1 Product Description Part 2 Installation Guide Part 3 Configuration Guide Part 4 Routine Maintenance
No ratings yet
User Manual: Part 1 Product Description Part 2 Installation Guide Part 3 Configuration Guide Part 4 Routine Maintenance
2 pages
SIP Tel URI Support in Cisco UBE
No ratings yet
SIP Tel URI Support in Cisco UBE
4 pages
290L ECONAVI INVERTER Bottom Freezer Black 2-Door Refrigerator NR-BV320GKPH
No ratings yet
290L ECONAVI INVERTER Bottom Freezer Black 2-Door Refrigerator NR-BV320GKPH
1 page
0D50
No ratings yet
0D50
1 page
MandaVax Opt-Out
100% (3)
MandaVax Opt-Out
1 page
RCC Create Circuit Group: Function
No ratings yet
RCC Create Circuit Group: Function
11 pages
Data Privacy Contact Form Mandaluyong
100% (1)
Data Privacy Contact Form Mandaluyong
1 page
Fps Monitor
No ratings yet
Fps Monitor
3 pages
RVNL3
No ratings yet
RVNL3
7 pages
Intel Classmate Specs
No ratings yet
Intel Classmate Specs
4 pages
Kazza's Corner - Astone AP-300
No ratings yet
Kazza's Corner - Astone AP-300
4 pages
Price of Age Computers
No ratings yet
Price of Age Computers
94 pages
Hadoop - How To Install in 5 Steps in Windows 10 - by Shashank Singhal - Analytics Vidhya - Medium
No ratings yet
Hadoop - How To Install in 5 Steps in Windows 10 - by Shashank Singhal - Analytics Vidhya - Medium
33 pages
MCP-161 - Micro III Direct Communications
100% (2)
MCP-161 - Micro III Direct Communications
1 page
Error
No ratings yet
Error
6 pages
Electrical Connector Symbols
No ratings yet
Electrical Connector Symbols
4 pages
Talal Jawaid: Software Engineer Resume
No ratings yet
Talal Jawaid: Software Engineer Resume
1 page
ION7400 Modbus Map
No ratings yet
ION7400 Modbus Map
101 pages
Linear Algebra:: Electronics and Communication Engineering
No ratings yet
Linear Algebra:: Electronics and Communication Engineering
3 pages
Daftar Harga Komputer 04 Desember 2010 (16.45 WIB)
No ratings yet
Daftar Harga Komputer 04 Desember 2010 (16.45 WIB)
63 pages
Class 8 Electricity 2
No ratings yet
Class 8 Electricity 2
4 pages
Fujitsu W510 PC, Used With System SW VC10 and VD10 CSTD AXD3-500.805.01 AX41-060.841.07
100% (2)
Fujitsu W510 PC, Used With System SW VC10 and VD10 CSTD AXD3-500.805.01 AX41-060.841.07
103 pages
Handout Sae j1939 Fundamentals
67% (3)
Handout Sae j1939 Fundamentals
54 pages
Nutanix Cluster Architecture SEO Guide
No ratings yet
Nutanix Cluster Architecture SEO Guide
15 pages
Computing Essentials 2013 Making IT Work For You 23rd Edition OLeary Solutions Manual 1
100% (98)
Computing Essentials 2013 Making IT Work For You 23rd Edition OLeary Solutions Manual 1
18 pages
Chapter - 18 Intro To Network Layer 12052021 024156pm 1 10012022 105155am 1 22062022 095946am 26122022 101336am
No ratings yet
Chapter - 18 Intro To Network Layer 12052021 024156pm 1 10012022 105155am 1 22062022 095946am 26122022 101336am
79 pages
Hybrid Solar Inverter: Project Guide MR - Vishwaprakash Babu
No ratings yet
Hybrid Solar Inverter: Project Guide MR - Vishwaprakash Babu
12 pages
NSR Neb-2000c Eb212175
No ratings yet
NSR Neb-2000c Eb212175
1 page
L230 LineCoder
No ratings yet
L230 LineCoder
12 pages
UI Design for Developers
No ratings yet
UI Design for Developers
3 pages
Fire Fighting Robot
No ratings yet
Fire Fighting Robot
5 pages
04 - VASS6 Nombres Profinet
No ratings yet
04 - VASS6 Nombres Profinet
16 pages
Project 10.1
No ratings yet
Project 10.1
19 pages
Modman Log
No ratings yet
Modman Log
6 pages
Ugee V4.1 Driver Manual
No ratings yet
Ugee V4.1 Driver Manual
30 pages
HP Laserjet Pro M402N: Datasheet
No ratings yet
HP Laserjet Pro M402N: Datasheet
2 pages
Student Database Management System Finale
No ratings yet
Student Database Management System Finale
28 pages