1.1 basic concepts 1-1 - read.pudn.comread.pudn.com/downloads181/ebook/846323/softx3000/softx3000...

Chapter 1 Overview of Emergency Maintenance 1-1..........................................

1.1 Basic Concepts 1-1......................................................................................1.1.1 Emergency Maintenance 1-1...............................................................1.1.2 Emergent Fault 1-1..............................................................................1.1.3 Device Fault 1-1...................................................................................1.1.4 Service Fault 1-3..................................................................................

1.2 Basic Principles of Emergency Maintenance 1-5.........................................

Chapter 2 Handling Emergent Faults 2-1.............................................................

2.1 Introduction to the Chapter 2-1.....................................................................2.2 Overview of Handling Emergent Faults 2-1..................................................

2.2.1 Overall Handling Flow 2-1....................................................................2.2.2 Collecting Fault Information 2-4...........................................................

2.3 Handling Device Fault 2-6............................................................................2.3.1 Handling Host Device Breakdown 2-6.................................................2.3.2 Handling Frame Breakdown 2-11..........................................................2.3.3 Handling Service Module Breakdown 2-13............................................2.3.4 Handling MRS6000 Breakdown 2-15.....................................................2.3.5 Handling BAM Breakdown 2-18.............................................................2.3.6 Handling iGWB Breakdown 2-20...........................................................

2.4 Handling Service Fault 2-23...........................................................................2.4.1 Handling Global Service Congestion 2-23.............................................2.4.2 Handling Partial Service Congestion 2-27.............................................2.4.3 Handling MRS Service Congestion 2-32................................................2.4.4 Handling AMG Service Congestion 2-36...............................................2.4.5 Handling TMG Service Congestion 2-39................................................2.4.6 Handling UMG Service Congestion 2-43...............................................

Chapter 3 Maintenance Operation Guide 3-1......................................................

3.1 Power-On Operations 3-1.............................................................................3.1.1 Overview of Power-On Operations 3-1................................................3.1.2 Power Supply System of Cabinet 3-1..................................................3.1.3 Powering on and Restarting Cabinet 3-3.............................................3.1.4 Powering on and Restarting Frames 3-5.............................................3.1.5 Powering on and Restarting MRS6000 3-6..........................................

3.2 Resetting Operations 3-6..............................................................................3.2.1 Overview of Resetting Operations 3-6.................................................3.2.2 Resetting Frames 3-7...........................................................................3.2.3 Resetting Boards 3-8...........................................................................3.2.4 Resetting Modules by Level 3-9...........................................................3.2.5 Resetting SCC of MRS6000 3-10..........................................................

3.3 Restoring BAM Database 3-11.......................................................................3.3.1 Overview of Restoring BAM Database 3-11..........................................3.3.2 Using BAM Server Software Installer 3-12.............................................3.3.3 Using SQL Server Tools 3-20................................................................

3.4 Switchover and Recovery of BAM 3-32..........................................................3.4.1 Using Emergency Workstation to Replace BAM 3-32............................3.4.2 Stopping Using Emergency Workstations and Restoring BAM 3-35.....

3.5 Scanning and Killing Virus on BAM 3-39........................................................3.5.1 Preparations 3-39...................................................................................3.5.2 Scanning and Killing Virus on BAM 3-41...............................................3.5.3 Restoring Work 3-45..............................................................................

Chapter 4 Maintenance Record Table 4-1............................................................

4.1 Emergency Maintenance Note 4-1...............................................................4.2 Troubleshooting Record Table 4-3...............................................................

Appendix A Acronyms and Abbreviations A-1....................................................

Index .................................................................................................................

Huawei Technologies Proprietary

HUAWEI

U-SYS SoftX3000 SoftSwitch System Emergency Maintenance Manual

V300R003


U-SYS SoftX3000 SoftSwitch System

Emergency Maintenance Manual

Manual Version T2-010310-20050331-C-3.30

Product Version V300R003

BOM 31033710

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

Website: http://www.huawei.com

Email: [email protected]


Copyright © 2005 Huawei Technologies Co., Ltd.

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX, infoX, and TopEng are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this manual are the property of their respective holders.

Notice

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


About This Manual

Release Notes

This manual applies to SoftX3000 SoftSwitch System V300R003 (hereinafter referred to as SoftX3000).

Related Manuals

The related manuals are listed in the following table.

Manual Content

U-SYS SoftX3000 SoftSwitch System Technical Manual-System Description

It provides an overall introduction to the SoftX3000, including product features, applications, and technical specifications.

U-SYS SoftX3000 SoftSwitch System Technical Manual-System Principle

It details on the hardware architecture, component interworking mechanism, and subsystems of alarm, billing, and clock in the SoftX3000.

U-SYS SoftX3000 SoftSwitch System Hardware Description Manual

It details the features and technical specifications of the hardware components of the SoftX3000, including cabinets, frames, boards, cables, and cabinet internal components.

U-SYS SoftX3000 SoftSwitch System Technical Manual–Services and Features

It covers various services and functions supported by the SoftX3000, including voice services, supplementary services, IP Centrex services, multi-media services, value added services, dual homing functions, charging functions, IPTN functions, remote network access functions, and so on.

U-SYS SoftX3000 SoftSwitch System Hardware Installation Manual

It details the installation procedure of the SoftX3000 hardware components, and matters needing attention during the installation process.

U-SYS SoftX3000 SoftSwitch System Software Installation Manual

It covers the detailed procedure of installing the SoftX3000 software, including BAM server, emergency workstation, and client, focusing on the key points that might cause installation failure.

U-SYS SoftX3000 SoftSwitch System Routine Maintenance Guide

It guides the maintenance engineers to perform daily maintenance, monthly maintenance, and yearly maintenance tasks on the SoftX3000.


Manual Content

U-SYS SoftX3000 SoftSwitch System Emergency Maintenance Manual

It guides the maintenance engineers to perform recovery operations in the case of emergencies, such as congestion of global service, AMG, and TMG, and failure of host and BAM.

U-SYS SoftX3000 SoftSwitch System Part Replacement Guide

It guides the maintenance engineers on how to replace hardware components of the SoftX3000, such as boards, fan frame, LAN Switch, and hard disk.

U-SYS SoftX3000 SoftSwitch System Operation Manual-Configuration Guide

It guides the engineers how to configure various data in the SoftX3000, including configuration steps, preparations, database table referencing relationships, and command parameters.

U-SYS SoftX3000 SoftSwitch System Operation Manual-Configuration Examples

It guides the engineers how to configure various data in the SoftX3000, including networking example, configuration script, key parameters and debugging guidance.

U-SYS SoftX3000 SoftSwitch System Operation Manual-Performance Measurement

It guides the engineers how to work on performance measurement tasks and analyze measurement results.

U-SYS SoftX3000 SoftSwitch System Operation Manual-GUI Guide

It guides the engineers how to use the GUI on various clients of the SoftX3000, including operations on menus and navigation tree. In addition, it introduces the operations on TableBrowse.

U-SYS SoftX3000 SoftSwitch System BAM User Manual

It guides the engineers how to install and use the software related to the BAM, including remote maintenance software, anti-virus software, system customized software, and so on.

U-SYS iGateway Bill User Manual

It elaborates on the functioning principle of the iGateway Bill. Also, it teaches you on how to install, maintain, and operate the product.

Organization

The manual describes the maintenance principles, routine maintenance tasks and operations in SoftX3000.

There are five chapters and one appendix in the manual.

Chapter 1 Overview of Emergency Maintenance introduces some basic concepts and basic principles of emergency maintenance.

Chapter 2 Handling Emergent Faults elaborates the handling procedure of device faults and service faults.


Chapter 3 Maintenance Operation Guide details the operations of powering on, resetting, restoring database, switching over and recovering BAM, and scanning and killing virus on BAM.

Chapter 4 Maintenance Record Table lists the maintenance record tables used during emergency maintenance.

Chapter 5 Acronyms and Abbreviations lists the abbreviations used in this manual and the corresponding full expressions.

Intended Readers

The manual is intended for the following readers:

NGN network planning experts NGN network administrators NGN system engineers

Conventions

The manual uses the following conventions:

I. General conventions

Convention Description

Arial Normal paragraphs are in Arial.

Boldface Headings are in Boldface.

Courier New Terminal Display is in Courier New.

II. Command conventions


Boldface The keywords of a command line are in Boldface.

III. GUI conventions



< > Button names are inside angle brackets. For example, click the <OK> button.



[ ] Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window.

/ Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].

IV. Mouse operation

Action Description

Select Press and hold the primary mouse button (left mouse button by default).

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.

V. Symbols

Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. They are defined as follows:

Caution: Means reader be extremely careful during the operation.

Note: Means a complementary description.

Emergency Maintenance Manual U-SYS SoftX3000 SoftSwitch System Table of Contents


i

Table of Contents

Chapter 1 Overview of Emergency Maintenance ....................................................................... 1-1 1.1 Basic Concepts .................................................................................................................. 1-1

1.1.1 Emergency Maintenance ........................................................................................ 1-1 1.1.2 Emergent Fault........................................................................................................ 1-1 1.1.3 Device Fault ............................................................................................................ 1-1 1.1.4 Service Fault ........................................................................................................... 1-3

1.2 Basic Principles of Emergency Maintenance .................................................................... 1-5

Chapter 2 Handling Emergent Faults .......................................................................................... 2-1 2.1 Introduction to the Chapter ................................................................................................ 2-1 2.2 Overview of Handling Emergent Faults ............................................................................. 2-1

2.2.1 Overall Handling Flow ............................................................................................. 2-1 2.2.2 Collecting Fault Information .................................................................................... 2-4

2.3 Handling Device Fault........................................................................................................ 2-6 2.3.1 Handling Host Device Breakdown........................................................................... 2-6 2.3.2 Handling Frame Breakdown.................................................................................. 2-11 2.3.3 Handling Service Module Breakdown ................................................................... 2-13 2.3.4 Handling MRS6000 Breakdown............................................................................ 2-15 2.3.5 Handling BAM Breakdown .................................................................................... 2-18 2.3.6 Handling iGWB Breakdown................................................................................... 2-20

2.4 Handling Service Fault..................................................................................................... 2-23 2.4.1 Handling Global Service Congestion .................................................................... 2-23 2.4.2 Handling Partial Service Congestion .................................................................... 2-27 2.4.3 Handling MRS Service Congestion....................................................................... 2-32 2.4.4 Handling AMG Service Congestion ...................................................................... 2-36 2.4.5 Handling TMG Service Congestion....................................................................... 2-39 2.4.6 Handling UMG Service Congestion ...................................................................... 2-43

Chapter 3 Maintenance Operation Guide.................................................................................... 3-1 3.1 Power-On Operations ........................................................................................................ 3-1

3.1.1 Overview of Power-On Operations ......................................................................... 3-1 3.1.2 Power Supply System of Cabinet............................................................................ 3-1 3.1.3 Powering on and Restarting Cabinet ...................................................................... 3-3 3.1.4 Powering on and Restarting Frames....................................................................... 3-5 3.1.5 Powering on and Restarting MRS6000................................................................... 3-6

3.2 Resetting Operations ......................................................................................................... 3-6 3.2.1 Overview of Resetting Operations .......................................................................... 3-6 3.2.2 Resetting Frames.................................................................................................... 3-7 3.2.3 Resetting Boards..................................................................................................... 3-8

Emergency Maintenance Manual U-SYS SoftX3000 SoftSwitch System Table of Contents


ii

3.2.4 Resetting Modules by Level .................................................................................... 3-9 3.2.5 Resetting SCC of MRS6000 ................................................................................. 3-10

3.3 Restoring BAM Database ................................................................................................ 3-11 3.3.1 Overview of Restoring BAM Database ................................................................. 3-11 3.3.2 Using BAM Server Software Installer.................................................................... 3-12 3.3.3 Using SQL Server Tools ....................................................................................... 3-20

3.4 Switchover and Recovery of BAM ................................................................................... 3-32 3.4.1 Using Emergency Workstation to Replace BAM................................................... 3-32 3.4.2 Stopping Using Emergency Workstations and Restoring BAM ............................ 3-35

3.5 Scanning and Killing Virus on BAM ................................................................................. 3-39 3.5.1 Preparations .......................................................................................................... 3-39 3.5.2 Scanning and Killing Virus on BAM....................................................................... 3-41 3.5.3 Restoring Work...................................................................................................... 3-45

Chapter 4 Maintenance Record Table ......................................................................................... 4-1 4.1 Emergency Maintenance Note .......................................................................................... 4-1 4.2 Troubleshooting Record Table .......................................................................................... 4-3

Appendix A Acronyms and Abbreviations ................................................................................A-1

Index ................................................................................................................................................ i-1

Emergency Maintenance Manual U-SYS SoftX3000 SoftSwitch System Chapter 1 Overview of Emergency Maintenance


1-1

Chapter 1 Overview of Emergency Maintenance

1.1 Basic Concepts

1.1.1 Emergency Maintenance

Emergency maintenance is a series of emergency measures used to minimize the loss, target the fault, and recover the system or devices when emergent faults happen.

1.1.2 Emergent Fault

Emergent faults refer to the faults that happen suddenly and affect a wide range of services or devices. Emergent faults affect network operation and quality of service (QoS). These faults include the host breakdown, BAM breakdown, iGWB breakdown, global service congestion, congestion of the access media gateway (AMG) service and congestion of the trunk media gateway (TMG) service.

To facilitate troubleshooting, the emergent faults related to the SoftX3000 can be defined in the following two aspects. Determine whether a fault is a device fault according to the device functions affected by the fault.

Determine whether a fault is a service fault according to the range of services affected by the fault.

1.1.3 Device Fault

I. Host Breakdown

Host breakdown is a severe fault with loss of full or most of the functions of the SoftX3000 in the network. In the actual applications, any of the following situations is regarded as a kind of host breakdown.

Power failure of all the cabinets Power failure of the integrated configuration cabinets Power failure of the basic frames Breakdown of the SMUIs in the basic frames Breakdown of the IFMIs in the basic frames Breakdown of the CDBIs in the basic frames

II. Service Frame Breakdown

Service frame breakdown is a severe fault with total or most of the functions of a service frame lost. It is shown in forms of the following phenomena.

Power failure of the service frame Breakdown of the SMUIs in the service frame



1-2

Breakdown of all the service modules in the service frame

III. Service Module Breakdown

Service module breakdown is a severe fault with total loss of the functions of a service module. It is shown in form of failure of the active and standby boards (or one board if running in the load sharing mode).

Note:

Board failure is a kind of software fault occurring in the memory of a board with total loss of all functions of the board. Board failure is shown in the following phenomena: The status of the board cannot be reported to the BAM (shown in red on the figure of the device panel); The CPU usage on the board reaches 100%; The “RUN” indicator on the panel of the board is off or on constantly; The “ALM” fault indicator on the panel of the board is on.

IV. MRS6000 Breakdown

MRS6000 breakdown is a severe fault with total loss of the functions of the MRS6000. It is shown in forms of the following phenomena.

Power failure of the MRS6000 frame Failure or down of all the MPC boards in the MRS6000 frame Failure or down of the active and standby SCC boards in the MRS6000 frame

Note:

SCC board failure is a kind of software fault occurring in the memory of a SCC board with total loss of all functions of the SCC board. SCC board down is shown in forms of the following phenomena. You cannot access the Web management interface of the MRS6000 through IE. The "STAT" indicator on the panel of the board is on (red) constantly. The "FAULT" indicator on the panel of the board is on (dark red) constantly.

V. BAM Breakdown

The BAM breakdown is a severe fault with the total loss of functions of the BAM. In the actual applications, any of the following situations is regarded as a kind of BAM breakdown.

Power failure of the BAM Unable to start the BAM Automatic and frequent reset of the BAM



1-3

The CPU usage of the BAM near 100% for a long time. Breakdown of the Windows operating system of the BAM during the operation or

unable to reboot the Windows operating system when the BAM starts. Abnormal running of the “BAM Manager". For example, unable to start the BAM

Manager, or unable to start all the service processes (Their statuses are "Stopped") or all the service processes enter the “Exception” state after being started repeatedly.

VI. iGWB Breakdown

iGWB breakdown is a severe fault with the total loss of functions of iGWB. In the actual applications, any of the following situations is regarded to be a kind of iGWB breakdown.

Power failure of iGWB Unable to start the iGWB Automatic and frequent reset of iGWB The CPU usage of the iGWB near 100% for a long time. Breakdown of the Windows operating system of the iGWB during the operation or

unable to reboot the Windows operating system when the iGWB starts. Abnormal running of the iGWB server. For example, unable to start the program at

the client, or unable to browse the bills, or a small bulb could not be found on the status bar after executing the “C:\IGWB\showicon.exe” command.

1.1.4 Service Fault

I. Global Service Congestion

The global service congestion refers to the global service interruption or call congestion with long durations. In the actual applications, any of the following situations is a kind of global service congestion:

No media gateway controlled by the SoftX3000 can register or disconnect immediately after registration.

Call congestion happens to all the subscriber terminals controlled by the SoftX3000, for example, no subscriber is able to call in or call out, and no dialing tone or busy tone is heard after off-hook.

Call congestion happens to all the office directions of the trunk circuits controlled by the SoftX3000, for example, no subscriber is able to call in or call out.

II. Partial Service Congestion

The partial service congestion refers to the service interruption or call congestion of the partial service with long durations. It is shown in forms of the following phenomena.

Some of the media gateways controlled by the SoftX3000 cannot register or disconnect immediately after registration.



1-4

Call congestion happens to some of the subscriber terminals controlled by the SoftX3000, for example, no subscriber is able to call in or call out, and no dialing tone or busy tone is heard after off-hook.

Call congestion happens to some of the office directions of the trunk circuits controlled by the SoftX3000, for example, some subscribers are unable to call in or call out.

III. MRS Service Congestion

The MRS service congestion refers to the fault that the SoftX3000 of the office cannot provide MRS resources for subscribers, that is, the SoftX3000 cannot control the MRS6000 to provide resources for announcement, DTMF number receiving, and conference connection. It is shown in forms of the following phenomena.

Subscribers cannot hear the announcement when using supplementary services. Subscribers cannot use the conference call service. Subscribers cannot use the intelligent network (IN) service of dual stage dialing

type. When there is an incoming call based on session initiation protocol (SIP) or H.323,

the destination office cannot send ring-back tone to the peer office.

IV. AMG Service Congestion

The AMG service congestion refers to call congestion of a whole AMG, that is, no subscriber under this AMG can call in or call out. They hear no dial tone or busy tone after off-hook.

V. TMG Service Congestion

The TMG service congestion refers to call congestion of a whole TMG, that is, all the TDM trunk circuits provided by the TMG cannot be used. For example, all the TDM circuits are faulty, and subscribers are unable to call in or call out.

VI. UMG Service Congestion

The congestion of the universal media gateway (UMG) service refers to the call congestion of the whole UMG. The UMG service congestion can be further defined as follows.

When the UMG is used as an AMG, the UMG service congestion means that all RSP users or V5 users under the UMG cannot call in or call out and hear no dialing tone or busy tone after off-hook.

When the UMG is used as a TMG, the UMG service congestion means that all the TDM trunk circuits provided by the UMG cannot be used such as failure of all the TDM circuits, and unable to call in or call out.



1-5

1.2 Basic Principles of Emergency Maintenance The emergent faults are dangerous and can cause call congestion, device breakdown and bill loss. In order to increase the efficiency of handling the emergent faults and minimize the loss, you need to follow the following basic principles before maintaining the SoftX3000.

The core of emergency maintenance is to recover system operation and service providing as soon as possible. Therefore, the key to increase the efficiency of handling the emergent faults is: You need to set up handling schemes for various emergent faults according to the related emergency maintenance manuals. Meanwhile, you need to practice periodically.

You must attend the emergency maintenance training which is mandatory for maintenance personnel. You must learn the basic method to judge emergent faults and learn how to handle emergent faults.

When there is an emergent fault, check whether the hardware devices and bearer network are working normally. Then you need to judge whether the emergent fault is caused by the SoftX3000. If yes, you can handle the fault according to the pre-prepared schemes or the procedures in this manual.

When emergent faults happen to the BAM or iGWB, you are strictly forbidden to reinstall the system or format the hard disk on the BAM or iGWB before consulting Huawei for technical support.

In order to get quick technical support when handling the emergent fault, you need to contact the Customer Service Center (Page 2 of the cover of this manual) or Regional Office of Huawei Technologies, Co., Ltd. (hereafter referred to as “Huawei”).

After handling the emergent fault, you need to collect the alarm information related to this fault and send the fault handling report, device alarm files and log files to Huawei for analysis. Therefore, Huawei can improve the after-sales service.

Emergency Maintenance Manual U-SYS SoftX3000 SoftSwitch System Chapter 2 Handling Emergent Faults


2-1

Chapter 2 Handling Emergent Faults

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

2.2 Overview of Handling Emergent Faults

2.2.1 Overall Handling Flow

I. Overview of Handling Flow

The ultimate purpose of emergency maintenance is to recover system operation and service providing as soon as possible. The overall handling flow is as shown in Figure 2-1.



2-2

Collecting FaultInformaiton

Start

Reporting forAnalysis

Hardware Ok?

2

Yes

Service Type FaultProcessing

Fault Solved?

Reporting forHelp

Yes

No

7

8

9

9

10

Bearer NetworkFault Processing

Collecting FaultInformation


4

No

3

No

Yes

Device Type FaultProcessing

5 6

BearerNetwork Ok?

Figure 2-1 Overall handling flow of emergent faults

II. Collecting Fault Information

When emergent faults happen, you need to collect as much information as possible from fault complaints, alarms from network management system (NMS), and by checking the device and starting dial tests. This will provide a basis for the following steps.

III. Checking Hardware Devices

The fault of a hardware device can cause service congestion (for example, breakdown of the basic frame will cause global service congestion). Therefore, you must check whether the hardware devices of the SoftX3000 are working normally before handling any emergent fault. The checking methods frequently used are as follows.



2-3

On the navigation tree on the client, open the [Device Management/Device Management] under the Management navigation tree and check whether the BAM, iGWB and all the boards (including the front boards and back boards) are running normally.

Check whether the power supply of the SoftX3000 is normal. Examine the power supplies of the cabinet, components inside the cabinet, the service frames, the MRS6000 frame and the service boards.

Check whether the components in the integrated configuration cabinet are normal, such as the LAN Switch, BAM, and iGWB.

Check whether the service frames (including the MRS6000 frame) are normal, that is, whether the boards in the service frames are normal.

IV. Checking Bearer Network

The next generation network (NGN) is a distributed and open network. Only when the network components of the NGN work coordinately and reliably can the NGN provide all kinds of services for the subscribers continuously and reliably. In the actual application, 40% to 60% of the service congestion are caused by the bearer network failure.

Therefore, when the service congestion happens, if the hardware devices of the SoftX3000 are working normally, you should check whether the bearer network is working normally. The checking methods frequently used are as follows.

Use the “Ping” tool in the port tracing task on the client to check whether the network communication between the SoftX3000 and the congested gateway is normal.

Use the “Tracert” tool in the port tracing task on the client to locate the IP address of the faulty router in the bearer network.

Contact the responsible person. Use professional instrument 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. Confirm whether network congestion, network storm or virus attacking exist in the bearer network.

V. Handling Device Fault

If you have confirmed that the hardware devices of the SoftX3000 are down, that is, it is a device fault, handle the fault immediately according to the pre-prepared scheme or section 2.2 of this manual “Handling of Device Fault”.

VI. Handling Service Fault

If you have confirmed that the hardware devices and bearer network of the SoftX3000 are normal, that is, it is a service fault, handle the fault immediately according to the pre-prepared scheme or section 2.3 of this manual “Handling of Service Fault”.



2-4

VII. Handling Bearer Network Fault

If having confirmed that the service congestion is caused by the bearer network fault, contact the responsible person immediately to handle the bearer network fault.

VIII. Judging Whether Problem Is Solved

After you handled the fault, judge whether the problem has been solved through NMS, maintenance console, dial tests, and service verification. In this way, you can know whether the function or service is normal.

IX. Collecting Fault Information

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

X. Reporting and Waiting for Technical Support

If you fail to clear the fault according to related emergent fault handling flows, ask for technical support from the Customer Service Center (contact details shown on page 2 of the cover of this manual) or Regional Office of Huawei by telephone or fax.

In order to shorten the handling time of the fault, record your emergency handling in detail, notify Huawei of the replaced boards during the handling, and ask for corresponding standby boards. For the fax, you can use emergency maintenance notes. For details, refer to section 4.1 “Emergency Maintenance Note”

2.2.2 Collecting Fault Information

Collect the following types of the SoftX3000 faults:

I. Brief Report of Fault

The service carrier can design the brief report of the fault. The contents of the report include: the occurrence time, nature, representation, and detailed handling of the fault. When the fault is not solved, you can use the emergency maintenance note to replace the brief report of the fault.

II. Collecting Debug Logs

You need to copy all the “*.log” and “*.bak” files under the E:\MSSQL\Data directory in the BAM and save them to a new path in time. These files are debug.log, DeviceLog.log, DeviceAlarm.log, DeviceStat.log, debugLog.bak, DeviceLog.bak, DeviceAlarmLog.bak and DeviceStatLog.bak.



2-5

These debug log files are critical to the location of the fault. When the size of these files reach an extent, the system will automatically remove the information saved originally. Therefore, after the emergent fault occurs, you need to copy and save these files to another place in time.

III. Collecting Alarm Logs

You need to collect the alarm log information from 30 minutes before the occurrence of the fault to 30 minutes after it. You can perform the query and saving operation on the alarm console. The operations are as follows.

1) Select [Alarm Query/Query] on the menu bar of the alarm console, and set the type and time segment of the alarm to be queried on the window popped up. Click <OK>.

2) On the output window of the query result popped up, right click and select “Save as…” on the shortcut menu popped up. Then you can export the alarm log information and save as text files or Excel files.

IV. Collecting Command Logs

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

V. Collecting Debug Log of BAM

When an emergent fault happens to the BAM, try your best to collect the fault location information of the BAM if you can enter its windows operating system. The operations are as follows.

1) Copy all the files (plus folders) under the D:\SoftX3000\RunLog directory in the hard disk of the BAM and save them to another place.

2) Copy the debug.log and debugLog.bak under the E:\MSSQL\Data directory in the hard disk of the BAM and save them to another place.

VI. Collecting Debug Log of iGWB

When an emergent fault happens to the iGWB, you should try your best to collect the fault location information of the iGWB if you can enter the windows operating system of the iGWB. You need to copy the following files and save them to another place:

All files under the C:\iGWB\trace directory in the hard disk of the iGWB (The tracing information files).

All files under the D:\other\log directory in the hard disk of the iGWB (The log files). The igwb.ini file under the C:\iGWB\Config\ini directory in the hard disk of the

iGWB (The parameter configuration file). All the files under the C:\iGWB\Config\format directory in the hard disk of the

iGWB (The bill format configuration files).



2-6

2.3 Handling Device Fault

2.3.1 Handling Host Device Breakdown

I. Overview of Handling Host Device Breakdown:handling

After you confirm the host device breakdown, immediately handle the fault according to the basic flow shown in Figure 2-2. The core steps are as follows.

1) Remove the power supply fault of the cabinet 2) Remove the power supply fault of the basic frame 3) Remove the running fault of the basic frame 4) Remove the configuration data fault



2-7

Fault TypeConfirmed

Reporting forHelp

Cabinet PowerSupply Ok?

Yes

No2 3Repairing and

Restarting

Fault Solved?YesNo

Basic FramePower Supply Ok?

4

SMUI Module Down?5 6

Resetting orReplacing SMUI

Fault Solved?YesNo

13 Collecting FaultInformation

IFMI Module Down?

7 8

Resetting orReplacing IFMI

Fault Solved?YesNo

CDBI Module Down?

9Resetting or

Replacing CDBI

Fault Solved?YesNo


No

YesData Recovery

Fault Solved?YesNo

1211

No

Yes

Yes

No

No

No

ConfigurationData Wrong?

10

Yes

Yes


Figure 2-2 Handling of host device breakdown



2-8

II. Checking Power Supply of Cabinet

Power failure of the integrated configuration cabinet or all cabinets will result in the host breakdown. You can judge whether the power supply of the cabinet is normal by the following methods.

1) If the “RUN” indicator on the panel of the power distribution box (PDB) is on (green), and blinks once per second, the power supply of the cabinet is normal, that is, the input power supply and internal circuits of the PDB are normal.

2) If the “RUN” indicator on the panel of the PDB is off, the power supply of the cabinet is abnormal, that is, the two input power supplies are faulty.

III. Repairing Power Supply System and Re-Powering On

Generally, the faulty power supply of the cabinet is caused by the power supply system in the equipment room. In this case, restore the system according to the following steps.

1) Turn off all the switches (from SW1 to SW6) on the panel of the PDB before restoring the power supply system in the equipment room.

2) Repair the power supply system in the equipment room. 3) Re-Power on the cabinet according to section 3.1.2 of this manual “Powering on

and Restarting Cabinet” after the power supply system is normal.

IV. Checking Power Supply of Basic Frame

Power failure of the basic frame will cause important boards in it unavailable such as the IFMIs and CDBIs, making the host device breakdown. You can judge whether the power supply of the basic frame is normal by the following methods.

If the indicators on the panel of the boards in the basic frame are on, the power supply of the basic frame is normal.

If none of the indicators on the boards is on or only the indicator on the UPWR is on, the power supply of the basic frame is abnormal.

If the power supply of the basic frame is abnormal, do not handle the fault yourself. Immediately contact Huawei technical support.

V. Checking SMUIs in Basic Frame

The SMUIs manage the running of the service frame (namely the OSTA frame). If the SMUIs are down, it means that all the boards in the frame are out of service. The breakdown of the basic frame will cause the IFMIs and CDBIs in it unavailable. Therefore, the breakdown of the SMUIs in the basic frame will cause the host device breakdown.

Any of the following situations can be regarded as the breakdown of the SMUIs in the basic frames.



2-9

The “RUN” indicators on the panels of the active and standby SMUIs are off or on constantly.

The “ALM” fault indicators on the panels of the active and standby SMUIs are on. The “DOMA” and “DOMB” bus domain indicators on the panels of the active and

standby SMUIs are off. The CPU usage of the active and standby SMUIs has been near 100% for a long

time.

VI. Resetting or Replacing SMUIs

You can reset the active and standby SMUIs after confirming that the SMUIs in the basic frames are down. After resetting, the SMUIs should be working normally. If not, replace them.

Caution:

The SMUIs of basic frame 0 record license information of the SoftX3000, which limits the capacity and features of the SoftX3000.When replacing the SMUIs of basic frame 0, apply a new license from Huawei. Otherwise, the frame will stop operation in a limited period.

VII. Checking IFMIs in Basic Frame

The IFMIs provide the physical interface (namely the FE interface) for the IP-based signaling. It is the component in the SoftX3000 to send and receive all kinds of IP signaling messages. If the system only has one IFMI module and it is down, the SoftX3000 is isolated from other components in the network.

Any of the following situations can be regarded as the breakdown of the IFMIs in the basic frame.

The “RUN” indicators on the panels of the active and standby IFMIs are off or on constantly.

The “ALM” fault indicators on the panels of the active and standby IFMIs are on. The CPU usage of the active and standby IFMIs has been near 100% for a long

time.

VIII. Resetting or Replacing IFMIs

You can reset the active and standby IFMIs in the basic frames after confirming that they are down. After resetting, the IFMIs should be working normally. If not, replace them.



2-10

IX. Checking CDBIs in Basic Frame

The CDBIs store all the data related to the host such as the location of subscribers, trunk selection, gateway resource management, black and white lists, IPN number and dispatch capability. If the system is configured with only two CDBIs, the breakdown of the CDBIs will cause the critical central database functions unavailable such as the location of subscribers, line selection of the trunk and gateway resource management.

Any of the following situations can be regarded as the breakdown of the CDBIs in the basic frame.

The “RUN” indicators on the panels of the active and standby CDBIs are off or on constantly.

The “ALM” fault indicators on the panels of the active and standby CDBIs are on. The CPU usage of the active and standby CDBIs has been near 100% for a long

time.

X. Resetting or Replacing CDBIs

You can reset the active and standby CDBIs in the basic frames after confirming that they are down. After resetting, the CDBIs should be working normally. If not, replace them.

XI. Checking Whether Host Device Breakdown Is Caused by Modification of Configuration Data

The maximum number of tuples, public parameters, and module parameters must not be modified. If you improperly modify these configuration data (for example, the maximum number of tuples is set too big), some boards will not be able to load data, or will be repeatedly trying to load data. The boards become abnormal.

In this case, use the command LST LOG to querying the operation record of the commands MOD MAXT, MOD PUBPRM, and MOD MPRM.

XII. Recovering Configuration Data

If you improperly modify the above configuration data, be sure to correct the data yourself or with the help of Huawei technicians.

Caution:

After data modification, execute the command FMT to convert the data. Then you can reload the related service module to make the data valid after modification.



2-11

XIII. Collecting Fault Information

You must collect the fault information according to the requirements described in section 2.1.2 “Collecting Fault Information” no matter how the fault has been handled. The information collected will be used for further analysis and fault location.

2.3.2 Handling Frame Breakdown

I. Overview of Handling Frame Breakdown:

After you confirm the service frame breakdown, immediately handle the fault according to the basic flow shown in Figure 2-3. The core steps are as follows.

1) Remove the power supply fault of the frame 2) Remove the running fault of the SMUIs


Reporting forHelp

Power SupplyOk?

Yes

No

2

SMUI ModuleDown?

No

3 4

Resetting orChanging SMUI

Fault Solved?

Yes

No



5 5

Yes

Fault TypeConfirmed

Figure 2-3 Handling of service frame breakdown

II. Checking Power Supply of Frame

The power failure of the frame will cause the service frame breakdown. You can judge whether the power supply of the frame is normal by the following methods.



2-12

If the indicators on the panels of the boards in the frame are on, the power supply of the frame is normal.

If none of the indicators on the boards is on or only the indicator on the UPWR is on, the power supply of the frame is abnormal.

If the power supply of the frame is abnormal, do not handle the fault yourself. Immediately contact Huawei for technical support.

III. Checking Whether SMUIs in Frame Are Working Normally

The SMUIs manage the running of the OSTA frame. If the SMUIs are down, it means that all the boards in the frame are out of service.

Any of the following situations can be regarded as the SMUI breakdown in the frame.

The “RUN” indicators on the panels of the active and standby SMUIs are off or on constantly.

The “ALM” fault indicators on the panels of the active and standby SMUIs are on. The “DOMA” and “DOMB” bus domain indicators on the panels of the active and

standby SMUIs are off. The CPU usage of the active and standby SMUIs has been near 100% for a long

time.

IV. Resetting or Replacing SMUIs

You can reset the active and standby SMUIs after confirming that the SMUIs in the frame are down. After resetting, the SMUIs should be working normally. If not, replace them.

Caution:

The SMUIs of basic frame 0 record license information of the SoftX3000, which limits the capacity and features of the SoftX3000.When replacing the SMUIs of basic frame 0, apply a new license from Huawei. Otherwise, the frame will stop operation in a limited period.

The SMUIs of basic frame 0 record license information of the SoftX3000, which limits the capacity and features of the softswitch.

V. Collecting Fault Information




2-13

2.3.3 Handling Service Module Breakdown

I. Overview of Handling Service Module Breakdown:

After you confirm the service module breakdown, immediately handle the fault according to the basic flow shown in Figure 2-4. The core steps are as follows.

1) Remove the configuration data errors 2) Reset the boards corresponding to the service module 3) Replace the boards corresponding to the service module

Reporting forHelp

4



6 6

Configuration Data Wrong?

No

Yes2 3

Data Recovery

Fault Solved?YesNo

Fault Solved?

Resetting Boards

Yes

5

Fault Solved?

Replacing Boards

Yes

No

No

Fault TypeConfirmed


Figure 2-4 Handling of the service module breakdown



2-14

II. Checking Whether Service Module Breakdown Is Caused by Modification of Configuration Data

Generally, you should not modify the configuration data such as the maximum number of tuples, public parameters and module parameters. If you improperly modify these configuration data (for example, the maximum number of tuples is set too big), some boards might be unable to load data or repeatedly trying to load data. The boards become abnormal.

In this case, use the command LST LOG to query the operation record of the commands MOD MAXT, MOD PUBPRM, and MOD MPRM.

III. Recovering Configuration Data

If you improperly modify the above configuration data, be sure to recover the correct data yourself or with the help of Huawei technicians.

Caution:

It is important to note that you should execute the command FMT to convert all the data after modification. Then you can reload the related service module to make the data valid after modification.

IV. Resetting Boards Corresponding to Service Module

If the configuration data is correct, handle the service module breakdown according to the following steps.

1) For the FCCU/FCSU module, you should try to use the command STR BILIF to fetch the bills manually to avoid bill loss.

2) Reset the boards corresponding to the service module. Check whether the service module is working normally afterwards.

V. Replacing Boards Corresponding to Service Module

After resetting, if the service frame is still out of service, replace the boards corresponding to the service module.

VI. Collecting Fault Information




2-15

2.3.4 Handling MRS6000 Breakdown

I. Overview of Handling MRS6000 Breakdown:

After you confirm the MRS6000 breakdown, immediately handle the fault according to the basic flow shown in Figure 2-5. The core steps are as follows.

1) Remove the power supply fault of the MRS6000 2) Remove the fault of the SCCs 3) Remove the fault of the MPCs 4) Remove the configuration error of the internal IP addresses



2-16


Reporting forHelp

Yes

No

2

Yes

8

Data Recovery

Fault Solved?YesNo

9Collecting Fault

Information

9Collecting Fault

Information

Fault TypeConfirmed

SCCs Down?

No

Yes3 4

Resetting orChanging SCCs

Fault Solved?YesNo

No

Yes5

6

Powering-on andRestarting MRS6000

Fault Solved?Yes

No

IP Addresses Wrong?No

7

MPCs Down?

MRS6000 PowerSupply Ok?

Figure 2-5 Handling of the MRS6000 breakdown



2-17

II. Checking Power Supply of MRS6000

The power failure of the MRS6000 frame will cause the MRS6000 breakdown. You can judge whether the power supply of the MRS6000 is normal by the following methods.

If the “PWR” power indicators on the panels of the boards in the MRS6000 frame are on (green), the power supply of the MRS6000 is normal.

If none of the “PWR” power indicators on the panels of the boards in the MRS6000 frame is on (green), the power supply of the MRS6000 is abnormal.

If the power supply of the frame is abnormal, do not handle the fault yourself. Immediately contact Huawei for technical support.

III. Checking SCCs

The SCC boards manage the running of the MRS6000 frame. If the active and standby SCCs are down, it means that all the boards in the MRS6000 frame are out of service. It equals to the MRS6000 breakdown.

Any of the following situations can be regarded as the breakdown of the SCCs in the MRS6000 frame.

The “FAULT” indicators on the panels of the active and standby SCCs are on (red) constantly.

The “STAT” indicators on the panels of the active and standby SCCs are off, or on (red) constantly, or blinking (yellow).

IV. Resetting or Replacing SCCs

You can reset the active and standby SCCs after confirming that they are down. After resetting, the SCCs should be working normally. If not, replace the SCCs.

V. Checking MPCs

All the media resources of the MRS6000 are stored on the MPC boards. Therefore, if the MPCs are down, it means that the MRS6000 is down.

Any of the following situations can be regarded as the breakdown of all the MPCs in the MRS6000 frame.

The “FAULT” indicators on the panels of all the MPCs are on (red) constantly. The “STAT” indicators on the panels of all the MPCs are off, or on (red) constantly,

or blinking (yellow).

VI. Powering on and Restarting MRS6000

You can power on and restart the MRS6000 after confirming that all the MPCs are down. After that, the MPC should be working normally. If not, execute the next step.



2-18

VII. Checking Whether MPC Breakdown Is Caused by Modification of Internal IP Addresses of the Boards

In MRS6000, the SCC boards communicate with the MPC boards through internal Ethernet. This requires that the internal IP addresses of the boards are in the same network segment. If you set the internal IP addresses of the boards improperly, it will cause the MPC board failure.

In this case, check whether the internal IP addresses of the boards are in the same network segment by the following steps.

1) Query the “Control Interface IP Address” of the SCCs through the serial port configuration interface.

2) Query the “Control Interface IP Address” of the MPCs through the Web configuration interface.

VIII. Recovering Configuration Data

Recover the configuration data according to the following steps.

1) If you improperly modified the internal IP addresses of the boards, be sure to recover the correct configuration data yourself or with the help of Huawei technicians.

2) If you modify the internal IP address of the SCC board, power on and restart the MRS6000 to make the data valid after modification. If you modify the internal IP address of the MPC board, reset the MPC to make the data valid after modification.

IX. Collecting Fault Information


2.3.5 Handling BAM Breakdown

I. Overview of Handling BAM Breakdown

After you confirm the BAM breakdown, immediately handle the fault according to the basic flow shown in Figure 2-6. The core steps are as follows.

1) Remove the power supply fault of the BAM 2) Restart the BAM 3) Start the emergency workstation 4) Protect the on-site environment 5) Wait for the technical support



2-19


6

Reporting forHelp

BAM PowerSupply Ok?

Yes

No

2


4

3

Fault TypeConfirmed

Replacing BAM

Fault Solved?Yes

No

Restarting BAM

ProtectingEnvironment

5

6


Figure 2-6 Handling of the BAM breakdown

II. Checking Power Supply of BAM

The power failure of the BAM will cause the BAM breakdown. You can judge whether the power supply of the BAM is normal using the following methods.

If the power indicator of the BAM is green, the power supply of the BAM is normal and the BAM is in the “active” state.

If the power indicator of the BAM is orange, the power supply of the BAM is normal and the BAM is in the “standby” state.

If the power indicator of the BAM is off, the power supply of the BAM is abnormal.



2-20

If the power supply of the BAM is abnormal, do not handle the fault yourself. Immediately contact Huawei for technical support.

III. Restarting BAM

If the power supply of the BAM is normal and the BAM is down, execute the following steps to restore the BAM.

If the BAM is in the “standby” state, press the “power” switch to restart it. If the BAM is running the Windows operating system, use the “Restart” function of

the Windows to restart the BAM. If the Windows operating system is down on the BAM, press the “Reset” button to

restart it.

IV. Using Emergency Workstation to Replace BAM

If the BAM is still not working after being restarted, you should immediately start the emergency workstation to replace the BAM. For details, refer to section 3.4.1 of this manual “Using Emergency Workstation to Replace BAM”.

V. Protecting On-site Environment

If the BAM is still down after being restarted, you must not reinstall the system or format the hard disk of the BAM before consulting the technicians from Huawei. This is to protect the important data in the hard disk of the BAM.

VI. Collecting Fault Information


2.3.6 Handling iGWB Breakdown

I. Overview of Handling iGWB Breakdown

After you confirm the iGWB breakdown, immediately handle the fault according to the basic flow shown in Figure 2-7. The core steps are as follows.

1) Switch over the iGWBs 2) Protect the on-site environment 3) Wait for the technical support"



2-21

Reporting forHelp

AutomaticSwitchover?

No

Yes3

7Collecting Fault

Information

5

Fault TypeConfirmed

iGWBs Down?

2 Yes

No

ProtectingEnvironment

7

4

Yes

No

Configuration Filecorrect?

Data Recovery

Restarting StandbyiGWB

6

Figure 2-7 Handling of the iGWB breakdown

II. Checking Whether Both iGWBs Are Down

Generally, the active and standby iGWBs will not be down at the same time except that the power failure or software fault happens to both of them concurrently.



2-22

If both iGWBs are down, do not handle the fault yourself. Immediately contact Huawei for technical support.

III. Checking Whether Automatic Switchover Happens

Normally, if the active iGWB is down, the system will automatically switch over to the standby iGWB in five minutes. That is, the standby iGWB becomes the active iGWB. You can check whether the switchover has been completed between the active and standby iGWBs by the following methods.

On the desktop of the Windows 2000 Server of the standby iGWB, if the small bulb on the status bar is on, the standby iGWB has become the active iGWB.

You can log on to the iGWB through the client side software on the workstation. You can also query and browse the bills.

IV. Checking Configuration File of Standby iGWB

When the active iGWB is down, the standby iGWB might not be able to automatically become the active iGWB. Generally, this is because the configuration file (its location: C:\iGWB\Config\ini\igwb.ini) of the standby iGWB is wrong.

Check whether the configuration file of the standby iGWB is correct according to the U-SYS iGateway Bill User Manual.

V. Recovering Configuration Data

If you improperly modify the configuration file of the standby iGWB, be sure to recover the correct configuration file yourself or with the help of Huawei technicians.

VI. Restarting Standby iGWB

After modification of the configuration file of the standby iGWB, you should restart the standby iGWB to make it become the active iGWB. You can use the “Restart“ function of the Windows operating system to restart the standby iGWB.

VII. Protecting On-site Environment

When emergent faults happen to the iGWBs, you must not reinstall the system or format the hard disk of the iGWBs before consulting Huawei for technical support. This is to protect the bill data in the hard disk of the iGWBs.

VIII. Collecting Fault Information




2-23

2.4 Handling Service Fault

2.4.1 Handling Global Service Congestion

I. Overview of Handling Global Service Congestion

After you confirm the global service congestion, immediately handle the fault according to the basic flow shown in Figure 2-8. The core steps are as follows.

1) Remove the hardware device fault 2) Remove the bearer network fault 3) Remove the configuration data errors 4) Remove the fault of the IFMIs 5) Remove the fault of the CDBIs



2-24


Reporting forHelp

12


No

Yes6Data Recovery

Fault Solved?YesNo

11

11


Start

Data Backup

Fetching Bills

4

5


2

3

IFMI Module Ok?

Yes

No8 9

Switching orResetting IFMI

Fault Solved?YesNo

CDBI Module Ok?

Yes

10

7

Switching orResetting CDBI

Fault Solved?YesNo

No


Host DeviceDown?

BearerNetwork Ok?


Yes

No

Yes

No

Figure 2-8 Handling of the global service congestion



2-25

II. Checking Host Device

The breakdown of the host device will cause the global service congestion. Therefore, you should check whether the host device is down such as the power failure of the basic frame, the breakdown of the SMUIs in the basic frames, the breakdown of the IFMIs in the basic frames and the breakdown of the CDBIs in the basic frames.

If the host device of the SoftX3000 is down, immediately handle it according to the descriptions in section 2.2.1 of this manual “Handling of Host Device Breakdown”.

III. Checking Bearer Network

The bearer network greatly affects the NGN service. When the bearer network is faulty, it will not only affect the transfer and exchange of signaling messages between the SoftX3000 and the network components of the NGN, but also affect that of the media stream between the terminal subscribers.




Contact the responsible person. Use professional instrument or software to test the parameters of the bearer network such as the transmission delay, bit error rate, packet loss ratio and jitter. Check the bearer network for network congestions, network storms, and virus attacks.

If the bearer network is faulty, contact the responsible person for handling the bearer network fault.

IV. Backing Up Service Data and BAM Database

During the handling of the fault, you might need to reset the boards, modules or frames, which might affect the data safety. Therefore, before these operations, you should back up the service data and the BAM database. The backup operations are as follows.

Execute the command BKP SS to back up the supplementary service data. Execute the command BKP IPN to back up the IPN service data. Execute the command BKP RACF to back up the RACF service data. Execute the command BKP DB to back up the BAM database and the BAM

registry.



2-26

V. Fetching Bills Immediately

During the handling of the fault, you might need to reset the boards, modules or frames, which might affect the bills. Therefore, before these operations, you should execute the command STR BILIF to fetch the bills on the host.

VI. Checking Whether Global Service Congestion Is Caused by Modification of Configuration Data

Generally, you should not modify the configuration data such as the central database in the CDBIs and the IP address of the FE port. If you modify the configuration data incorrectly (for example, disable the gateway resource management function of the CDBIs), the global service congestion of the SoftX3000 might happen after restarting the system.

In this case, you can execute the commands LST CDBFUNC and LST FECFG to check whether the configuration data is correct.

VII. Recovering Configuration Data


Caution:

If the IP address of the FE interface is modified, you should reset all the IFMI, BSGI, MSGI and MRCA boards of the SoftX3000 to make the data valid after modification.

VIII. Checking IFMIs in Basic Frames

The IFMI module provides the physical interface (namely the FE interface) of the IP signaling. It is the component in the SoftX3000 to send and receive all kinds of IP signaling messages. If the system has only one IFMI module, and the following situations happen to the IFMI module, the SoftX3000 will be isolated from the other components of the NGN network. The global service congestion will happen.

On the Monitor navigation tree window on the client, open the “CPU Usage” window and find that the CPU usage of the active IFMI has been near 100% for a long time.

On the Monitor navigation tree window on the client, open the “Memory Usage” window and find that the memory seizure rate of the active IFMI has been near 100% for a long time.

Execute the command DSP IPSTAT multiple times to query the IP statistics information of the active IFMI. After comparison, find that the flow of the IP packet



2-27

sent or received by the IFMIs is too small. It is much smaller than the flow in normal situation.

IX. Switching or Resetting IFMIs

When the above phenomena happen to the IFMIs in the basic frames, you can execute the command SWP BRD to switch over the IFMIs. After switching, the IFMIs should be working normally. If not, reset the active and standby IFMIs.

X. Checking CDBIs in Basic Frames

The CDBIs store all the data related to the host such as the location of subscribers, line selection of the trunk, gateway resource management, black and white lists, and dispatch capability. If the system only has two CDBIs, and the following situations happen to them, the critical central database functions such as the location of subscribers, line selection of the trunk and gateway resource management will be unavailable.

On the Monitor navigation tree window on the client, open the “CPU Usage” window and find that the CPU usage of the active CDBI has been near 100% for a long time.

On the Monitor navigation tree window on the client, open the “Memory Usage” window and find that the memory seizure rate of the active CDBI has been near 100% for a long time.

XI. Switching or Resetting CDBIs

When the above phenomena happen to the CDBIs in the basic frame, you can execute the command SWP BRD to switch over the CDBIs. After switching, the CDBIs should be working normally. If not, reset them.

XII. Collecting Fault Information


2.4.2 Handling Partial Service Congestion

I. Overview of Handling Partial Service Congestion

After you confirm the partial service congestion, immediately handle the fault according to the basic flow shown in Figure 2-9. The core steps are as follows.

1) Remove the hardware device fault 2) Remove the bearer network fault 3) Remove the service congestion of single gateway 4) Remove the configuration data errors 5) Remove the fault of the FCCU module



2-28


Reporting forHelp

13

No

Yes7Data Recovery

Fault Solved? YesNo

13Collecting Fault

Information

Fetching Bills6


FCCU Module Ok?

Yes

No9

Switching FCCU

Yes

No

8

Leveled ResettingFCCU

One GatewayBlocking

AMG/TMG BlockingProcessing

Yes

No

Start

4

2

3


ServiceModule Down?

BearerNetwork Ok?


Yes

No

Yes

No

5


12

Data Backup

Fault Solved?

YesNoFault Solved?

Checking Bill PoolStatus

11

10

Figure 2-9 Handling of partial service congestion



2-29

II. Checking Related Service Module

The breakdown of the service modules such as the FCCU/FCSU, BSGI and MSGI will probably cause the partial service congestion. Therefore, you should check whether the service modules are down when handling the partial service congestion.

If the service modules of the SoftX3000 are down, you should immediately handle it according to the descriptions in section 2.2.3 of this manual “Handling of Service Module Breakdown”.

III. Checking Bearer Network

The bearer network greatly affects the NGN service. When the bearer network is faulty, it will not only affect the transfer and exchange of signaling messages between the SoftX3000 and the network components of the NGN, but also affect that of the media stream between the terminal subscribers.




Contact the responsible person. Use professional instrument 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. Confirm whether network congestion, network storm or virus attacking exist in the bearer network.

If the bearer network is faulty, contact the responsible person for handling the bearer network fault.

IV. Checking Whether Congestion Is Concentrated on a Gatewayn:

If the subscribers or office directions congested are concentrated on a gateway (AMG or TMG), refer to section 2.3.4 and 2.3.5 of this manual, “Handling of AMG Service Congestion” and “Handling of TMG Service Congestion”, for fault handling. Otherwise, execute the following steps.

V. Backing Up Service Data and BAM Database

During the handling of the fault, you might need to reset the boards or modules. Therefore, before these operations, you should back up the service data and the BAM database. The backup operations are as follows.

Execute the command BKP SS to back up the supplementary service data. Execute the command BKP IPN to back up the IPN service data. Execute the command BKP RACF to back up the RACF service data.



2-30

Execute the command BKP DB to back up the BAM database and the BAM registry.

VI. Fetching Bills Immediately

During the handling of the fault, you might need to reset the boards or modules, which might affect the bills. Therefore, before these operations, you should execute the command STR BILIF to fetch the bills on the host.

VII. Check Whether Partial Service Congestion Is Caused by Modification of Configuration Datan:

Generally, you should not modify the configuration data such as the local port numbers of media gateway control protocol (MGCP) and SIP, digit map of dialed local number set, call attribute of the service prefix, internal timer of the system and software parameters of the system. If you improperly modify the configuration data, partial service congestion of the SoftX3000 might happen.

Caution:

It is important to note that improper use of the network management commands might cause the partial service congestion. Therefore, you should be cautious when using these commands.

In this case, you can use the command LST LOG to query the command log information, and use the commands LST MGCPPARA, LST SIPLP, LST LDNSET and LST CNACLD to query whether related data configuration is correct.



IX. Checking Related FCCUs/FCSUs

The FCCU/FCSU is the core module in the SoftX3000 for service control and call processing. If the subscribers or office directions congested are not concentrated on a gateway (AMG or TMG), it is quite possible that the congestion is caused by the fault in the related FCCU/FCSU.



2-31

Note:

The related FCCU/FCSU refers to the module that processes the media gateway control messages and the call messages of the terminal subscribers or trunk circuits. You can execute the commands LST MGW, LST VSBR, LST MSBR, LST BRA and LST TKC to query the module number.

When the following situations happen to the FCCU/FCSU, it will cause the partial service congestion.

On the Monitor navigation tree window on the client, open the “CPU Usage” window and find that the CPU usage of the active FCCU/FCSU module has been over 80% for a long time.

On the Monitor navigation tree window on the client, open the “Memory Usage” window and find that the memory seizure rate of the FCCU/FCSU module has been over 80% for a long time.

X. Checking Status of Bill Pool of Related FCCU/FCSUs

If the FCCU/FCSU module is working and the module service congestion happens, it is because the bill pool of the module is full, which causes call restriction of the module.

You can execute the command DSP BILPO to query whether the bill pool of the related FCCU/FCSU module is full. You should immediately contact Huawei for technical support no matter what the query result is.

XI. Switching Over FCCU/FCSUs

After confirming that the FCCU/FCSU module is abnormal as described in step eight, you can execute the command SWP BRD to switch over the FCCU/FCSU boards to see whether it becomes normal.

XII. Leveled Resetting of FCCU/FCSUs

If the FCCU/FCSU module is still abnormal after switchover, use the command RST MDU to execute leveled resetting of the active FCCU/FCSU module from level one to level four.

XIII. Collecting Fault Information




2-32

2.4.3 Handling MRS Service Congestion

I. Overview of Handling of MRS Service Congestion

After you confirm the MRS service congestion, immediately handle the fault according to the basic flow shown in Figure 2-10. The core steps are as follows.

1) Remove the hardware device fault of the MRS6000 2) Remove the bearer network fault 3) Remove the misoperation fault 4) Remove the configuration data errors of the SoftX3000 5) Remove the configuration data errors of the MRS6000



2-33


Reporting forHelp

Yes

No3 4

RestoringCommunication

Fault Solved?YesNo

No

YesData Recovery

Fault Solved?YesNo



Start

Communication Ok?

MRS6000 Data Wrong?

No

Yes

7

Data Recovery

Fault Solved?YesNo

9

SoftX3000 Data Wrong?Yes

No

5MRS6000

Deactivated? Activating MRS6000

Fault Solved?YesNo

6

No

8

MRS6000Registration Ok?

2Device Type Fault

ProcessingMRS6000 Down?Yes

No

11

Yes

10

Figure 2-10 Handling of the MRS service congestion



2-34

II. Checking Whether MRS6000 Is Down

The breakdown of the MRS6000 will cause the MRS service congestion. Therefore, you should check whether the MRS6000 is down when handling the MRS service congestion.

If the MRS6000 is down, immediately handle it according to the descriptions in section 2.2.4 of this manual “Handling of MRS6000 Breakdown”.

III. Checking Communication Between MRS6000 and Bearer Network

All the boards of the MRS6000 are connected to the IP bearer network through the Ethernet cables. The Ethernet cables of the SCC are used to transfer the control information between the MRS6000 and the SoftX3000. The Ethernet cables of the MPC are used to transfer the media stream information between the MRS6000 and the terminal subscribers. If the communication between any board and the MRS6000 is abnormal, it will cause the MRS service congestion.

Therefore, when the MRS service congestion happens, if the hardware devices of the MRS6000 are working normally, you should check whether the communication between the MRS6000 and the bearer network is normal. The checking methods frequently used are as follows.

Using the “Ping” tool in the port tracing task on the client of the SoftX3000 to check whether the network communication between the SoftX3000 and the boards (including the SCC and all the MPCs) of the MRS6000 is normal.

Using the “Tracert” tool in the port tracing task on the client to locate the IP address of the faulty router in the bearer network.

IV. Restoring Communication Between MRS6000 and Bearer Network

If you have confirmed that the communication between the MRS6000 and the bearer network is abnormal because of the fault in the bearer network, contact the responsible person to handle the bearer network fault. If you are sure or suspect that it is because of the fault in the MRS6000, execute the following steps to recover the system.

1) Restart the MRS6000 to see whether the communication between the MRS6000 and the bearer network becomes normal.

2) If not, contact Huawei for technical support.

V. Checking Whether MRS6000 Is Deactivated

As one or more media gateway devices, the MRS6000 is managed by the SoftX3000. Each MPC board in MRS6000 is regarded as an independent media gateway. If these media gateways are deactivated, it will cause the MRS service congestion.

You can execute the command DSP MGW on the client of the SoftX3000 to query the maintenance status of the MRS6000. An example of the command is “DSP MGW: EID=’*’, TYPE=MRS”.



2-35

VI. Executing Command ACT MGW to Activate MRS6000

After confirming that the MRS6000 is deactivated, you should immediately execute the command ACT MGW to activate the MRS6000.

VII. Checking Registration of MRS6000

As one or more media gateway devices, the MRS6000 is managed by the SoftX3000. Each MPC board in MRS6000 is regarded as an independent media gateway. If these media gateways cannot register at the SoftX3000, it will cause the MRS service congestion.

You can execute the command DSP MGW on the client of the SoftX3000 to query the registration status of the MRS6000. An example of the command is “DSP MGW: EID=’*’, TYPE=MRS”.

VIII. Checking Whether Congestion Is Caused by Modification of Configuration Data of SoftX3000

If the MRS6000 cannot register to the SoftX3000 and its communication with the SoftX3000 is normal, it is quite possible that the fault is caused by the configuration data error.

You should execute the command LST LOG to query the command log information of the system. Find out whether the commands MOD MGW and RMV MRSRT have been used. You can also execute the following steps to query whether the related interconnection data on the SoftX3000 is correct.

Execute the command LST MGW to query whether the MGCP data is correct such as the interface name (fixed to be ms/cnf), remote IP address (the internal IP address of the MPC in MRS6000), remote port number, encoding type of MGCP, and codec mode.

Execute the command LST MRSRT to query whether the MRS route data is correct.

IX. Recovering Configuration Data

If you improperly modify the configuration data described in the previous step, be sure to recover the correct data on the SoftX3000 yourself or with the help of Huawei technicians.

X. Checking Whether Congestion Is Caused by Modification of Configuration Data of MRS6000

If the MRS6000 cannot register at the SoftX3000 and its communication with the SoftX3000 is normal, it is quite possible that the fault is caused by the configuration data error.



2-36

If the configuration data on the SoftX3000 is correct, you should query whether the following interconnection data at the MRS6000 side is correct through the Web management interface:

The names of the MPCs, “Control interface hostname”. The internal IP addresses of the MPCs, “Control interface IP address”. The MGCP parameters such as the IP address of the media gateway controller

(MGC), the port number of the MGC, the local port number of the MRS6000 and the domain name of the MRS6000.

Caution:

If you execute the maintenance operation of “logging off the service status” on the MPC, the MRS6000 will not be able to register at the SoftX3000.

XI. Recovering Configuration Data

If you improperly modify the configuration data described in the previous step, be sure to recover the correct data at the MRS6000 side yourself or with the help of Huawei technicians.



2.4.4 Handling AMG Service Congestion

I. Overview of Handling of AMG Service Congestion

After you confirm the AMG service congestion, immediately handle the fault according to the basic flow shown in Figure 2-11. The core steps are as follows.

1) Remove the bearer network fault 2) Remove the misoperation fault 3) Remove the configuration data errors of the SoftX3000 4) Remove the configuration data errors of the AMG



2-37


Reporting forHelp

12

No

Yes

6

Data Recovery

Fault Solved?YesNo

12


AMGRegistration Ok?

Yes

No2 3

Bearer Network orAMG FaultProcessing

Fault Solved?YesNo

9

8

Communication Ok?

SoftX3000 Data Wrong? Yes

No

4 AMGDeactivated? Activating AMG

Fault Solved?YesNo

5Yes

No

Data Recovery

Fault Solved?YesNo

AMG Data Wrong?Yes

No

7

AMG FaultProcessing

11


Start

10

Figure 2-11 Handling of AMG service congestion



2-38

II. Checking Communication Between SoftX3000 and AMG

Generally, the SoftX3000 controls multiple AMGs. Therefore, when the congested subscribers are on one AMG, It is very unlikely that the hardware devices of the SoftX3000 are faulty.

When the AMG service congestion happens, you should check whether the communication between the SoftX3000 and the AMG is normal. The checking methods frequently used are as follows.

Using the “Ping” tool in the port tracing task on the client of the SoftX3000 to check whether the network communication between the SoftX3000 and the AMG is normal.

Using the “Tracert” tool in the port tracing task on the client to locate the IP address of the faulty router in the bearer network.

III. Checking Whether Bearer Network or AMG Is Faulty

When the communication between the SoftX3000 and the AMG is abnormal, if the bearer network is faulty, contact the responsible person for handling of the fault; if the AMG is faulty, execute the AMG fault handling.

IV. Checking Whether AMG Is Deactivated

If the AMG is deactivated, the AMG service congestion will happen. You can execute the command DSP MGW on the client of the SoftX3000 to query the maintenance status of the AMG.

V. Executing Command ACT MGW to Activate AMG

After confirming that the AMG is deactivated, you should immediately execute the command ACT MGW to activate the AMG.

VI. Checking Registration of AMG

If the AMG cannot register at the SoftX3000, the AMG service congestion will happen. You can execute the command DSP MGW on the client of the SoftX3000 to query the registration status of the AMG.

VII. Checking Whether Congestion Is Caused by Modification of Configuration Data of SoftX3000

If the AMG cannot register at the SoftX3000 and its communication with the SoftX3000 is normal, it is quite possible that the fault is caused by the configuration data error.

You should execute the command LST LOG to query the command log information of the system. Find out whether the command MOD MGW has been used. You can use the command LST MGW to query the interconnection data related to the AMG such as the interface name, remote IP address, remote port number, encoding type of MGCP, and Codec mode.



2-39


If you improperly modify the configuration data described in the previous step, be sure to recover the correct data on the SoftX3000 yourself or with the help of Huawei technicians.

IX. Checking Whether Congestion Is Caused by Modification of Configuration Data of AMG

If the AMG cannot register at the SoftX3000 and its communication with the SoftX3000 is normal, it is quite possible that the fault is caused by the configuration data error.

If the configuration data on the SoftX3000 is correct, you should query whether the related interconnection data at the AMG side is correct through the network management system (NMS). The data include: the IP address of the MGC, port number of the MGC, local port number of the AMG and domain name of the AMG.

X. Recovering Configuration Data

If you improperly modify the configuration data described in the previous step, be sure to immediately recover the correct data at the AMG side through NMS.

XI. Handling AMG Fault

If the AMG is still abnormal after the above steps, handle the AMG fault according to the maintenance manual for the AMG.



2.4.5 Handling TMG Service Congestion

I. Overview of Handling TMG Service Congestion

After you confirm the TMG service congestion, immediately handle the fault according to the basic flow shown in Figure 2-12. The core steps are as follows.

1) Remove the bearer network fault 2) Remove the misoperation fault 3) Remove the signaling interconnection fault 4) Remove the trunk interconnection fault 5) Remove the configuration data errors of the SoftX3000 6) Remove the configuration data errors of the TMG



2-40

12

Same as AMG

Yes

2

5DSP Accessible?

Data Recovery

Fault Solved?No

Yes

7Yes

No

TMG RegistrationOk?

No3

SignalingData Wrong?

Yes

No

End

4

86

9

Yes

No

Reporting

Outgoing CallRouting Ok?

10

13

Yes

Data Recovery

Fault Solved?No

Yes

Trunk DataWrong?

Yes

No

End Reporting


No

15

Data Recovery

Fault Solved?No

Yes

Routing DataWrong?

Yes

No



14


Reporting forHelp

16

17

17

17

Peer Office FaultProcessing

TMG FaultProcessing

TransmissionNetwork or TMGFault Processing

SignalingNetwork or TMGFault Processing

TrunkCircuits Ok?

11

Figure 2-12 Handling of the TMG service congestion



2-41

II. Executing Same Steps as Those for AMG Service Congestion

Generally, the SoftX3000 controls multiple TMGs. Therefore, when the congested subscribers are on one TMG, It is very unlikely that the hardware devices of the SoftX3000 are faulty.

Step one to step four for handling the TMG service congestion are the same as those for handling the AMG service congestion. For details, refer to section 2.3.5 of this manual “Handling of AMG Service Congestion”.

III. Checking Registration of TMG

If the TMG cannot register at the SoftX3000, it will cause the TMG service congestion.

You can execute the command DSP MGW on the client of the SoftX3000 to query the registration status of the TMG.

IV. Handling TMG Fault

If the bearer network is normal and the data configuration of the media gateway on the SoftX3000 interconnecting the TMG is correct, but the TMG cannot register at the SoftX3000, you should execute the TMG fault handling according to the TMG maintenance manual.

V. Checking Whether DSP Is Accessible

Suppose the No. 7 trunk is used for the networking between the SoftX3000 of the local office and a peer office. No matter which signaling networking mode is used, to make the office direction from the local office to the peer office available, the signaling point (SP) of the peer office must be accessible for the SP of the local office. Otherwise, the service congestion of the office direction will happen.

You can execute the command DSP N7DSP on the client of the SoftX3000 to query whether the SP of the peer office is accessible for the SP of the local office.

VI. Checking Whether Congestion Is Caused by Modification of Signaling Data

If the bearer network is working normally, and the SP of the peer office is inaccessible for the SP of the local office, you should execute the command LST LOG to query the command log information of the system. Find out whether the commands MOD M3RT, MOD N7RT, MOD N7LNK have been used to modify the signaling data of the local office.

VII. Recovering Signaling Data

If you improperly modify the signaling data, be sure to immediately recover the correct signaling data on the SoftX3000 according to the “Debugging Instruction” of the related networking instance in the U-SYS SoftX3000 SoftSwitch System Operation Manual—Configuration Example.



2-42

VIII. Checking Whether Bearer Network or TMG Is Faulty

If the bearer network is working normally, and the signaling data on the SoftX3000 is correct, but the SP of the peer office is inaccessible for the SP of the local office, the SG, STP, TMG or peer end SP in the signaling network might be faulty. In this case, you should start the fault handling for the SG, STP or TMG.

IX. Checking Trunk Circuits

If the SP of the peer office is inaccessible for the SP of the local office, you should execute the command DSP OFTK to check whether the trunk circuits between the local office and the peer office are normal.

If all these trunk circuits are abnormal (faulty, unknown or congested), the office direction from the local office to the peer office will be unavailable. The service congestion of the office direction will happen.

X. Whether Fault Is Caused by Modification of Trunk Data

If the SP of the peer office is accessible for the SP of the local office, and all the trunk circuits between the local office and the peer office are abnormal, you should execute the command LST LOG to query the command log information of the system. Find out whether the commands MOD N7TG and MOD N7TKC have been used to modify the trunk data of the local office.

XI. Recovering Trunk Data

If you improperly modify the trunk data, be sure to immediately recover the correct trunk data on the SoftX3000 according to the “Debugging Instruction” of the related networking instance in the U-SYS SoftX3000 SoftSwitch System Operation Manual—Configuration Instance.

XII. Checking Transmission Network and TMG

If the SP of the peer office is accessible for the SP of the local office, and the trunk data on the SoftX3000 is correct, but all the trunk circuits between the local office and the peer office are still abnormal, the transmission devices, TMG or peer office might be faulty. You should start fault handling of the transmission network or TMG.

XIII. Checking Routing of Outgoing Call

Generally, if the trunk circuits between the local office and the peer office are normal, the office direction congestion is caused by incorrect routing data.

In this case, you can use the “Interface Trace Task” or “User Trace Task” tool on the client of the SoftX3000 to trace whether the outgoing calls of the office direction made by the subscribers of the local office can route to the corresponding trunk circuits.



2-43

XIV. Checking Whether Fault Is Caused by Modification of Routing Data

If the subscribers (with the outgoing call authority of the office direction) of the local office cannot route to the corresponding trunk circuits when making outgoing calls, the routing data of the SoftX3000 is incorrect.

In this case, you should execute the command LST LOG to query the command log information of the system. Find out whether the commands MOD CNACLD, MOD RTANA, MOD RT, MOD SRT, and MOD OFC have been used to modify the routing data of the local office.

XV. Recovering Routing Data

If you improperly modify the routing data, be sure to immediately recover the correct data on the SoftX3000.

XVI. Handling Peer Office Fault

If the trunk circuits between the local office and the peer office are normal, and the subscribers of the local office can route to the corresponding trunk circuits when making outgoing calls, the routing data of the peer office is incorrect. You should contact the peer office for fault handling.

XVII. Collecting Fault Information


2.4.6 Handling UMG Service Congestion

The UMG can serve as an independent AMG or TMG, or a mixture of AMG and TMG. When the UMG service congestion happens, you can handle it according to section 2.3.4 and 2.3.5 of this manual, “Handling of AMG Service Congestion” and “Handling of TMG Service Congestion”.

Emergency Maintenance Manual U-SYS SoftX3000 SoftSwitch System Chapter 3 Maintenance Operation Guide


3-1

Chapter 3 Maintenance Operation Guide

3.1 Power-On Operations

3.1.1 Overview of Power-On Operations

The power-on operations can be classified into the following categories:

Powering on and Restarting Cabinet Powering on and Restarting Frames Powering on and Restarting MRS6000

3.1.2 Power Supply System of Cabinet

I. Power Supply of Power Distribution Box

All cabinets of the SoftX3000 are N68-22 cabinets. Under normal circumstances, the power of each N68-22 cabinet is supplied by two independent –48 V direct current (DC) power supplies. The power supply of the components inside the cabinet is controlled by the PDB at the top of the cabinet. The power supply of the PDB is as shown in Figure 3-1.

-48V1

-48V2

PDB

SW1 SW2 SW3 SW4 SW5 SW6 Figure 3-1 Power supply of the PDB

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



3-2

II. Power Supply Loop Inside Cabinet

The SoftX3000 has three types of cabinets: integrated configuration cabinets, service processing cabinets and media resource server cabinets. Because different types of cabinets have different components, their primary power supply systems (namely –48 V power supply) are different. The electrical connections of the primary power supply systems of different cabinets are shown in Figure 3-2.

In tegrated Configuration Cabinet

Bas ic Frame 0

1 2 3 4 5 6

KVM/LCDLANSwitc h1LANSwitc h0

BAMStandby iGWBAc tive iGWB

PDF

Serv ic e Proc es sing Cabinet

4

3

5

4

3

5

6

( 2, 4)( 1, 3)

( 3, 4)

24

2

3

1

2

SW1 SW2

6

5

SW3 SW4 SW5 SW6

1 2 3 4 5 6

PDFSW1 SW2 SW3 SW4 SW5 SW6

Ex pans ion Frame 2

Dummy PanelDummy Panel

Media Res ourc e Serv er Cabinet

MRS6000 Frame1

1 2 5 6

PDFSW1 SW2 SW3 SW4 SW5 SW6

3 4

Dummy Panel

Dummy Panel

Ex pans ion Frame 1

Ex pans ion Frame 3

Ex pans ion Frame 4

Ex pans ion Frame 5

2

Figure 3-2 Electrical connections of the primary power supply systems of different cabinets

As shown in Figure 3-2, except for the LAN Switch 0, the LAN Switch 1, and the KVM/LCD converter inside the integrated configuration cabinet, the power of all the other components is supplied by the two switches on the PDB. The relationship between the PDB and the components inside the cabinet is as shown in Table 3-1.

Table 3-1 The relationship between the PDB and the components inside the cabinet.

Cabinet type Component Controlling switches

Active iGWB SW2, SW4

Standby iGWB SW1, SW3

BAM SW3, SW4

Disk array (only when iGWB adopts IBM server)

SW1, SW6

Integrated configuration cabinets

0#LAN Switch SW3



3-3

Cabinet type Component Controlling switches

1#LAN Switch SW2

KVM/LCD converter SW4

Basic frame 0 SW4, SW5

Integrated configuration cabinets Expansion frame 1 SW5, SW6

Expansion frame 2 SW5, SW6


Expansion frame 4 SW2, SW3 Service processing cabinet


Media resource server cabinet MRS6000 frame SW1, SW2

Since the SoftX3000 uses universal N68-22 cabinets, during the actual deployment, to increase the utilization of cabinets, the installation or configuration order of the components inside the cabinets might be different from that shown in Figure 3-2. You need to confirm the relationship between the PDB and the components in the cabinet before starting the operation to avoid mistakes.

3.1.3 Powering on and Restarting Cabinet

I. Application Scenarios

Only in the following situations can cabinets be powered on and restarted:

During deployment or expansion, the engineer needs to perform power-on test to the SoftX3000 after finishing the installation of all hardware devices.

During important upgrading of software or hardware, it is necessary to power off the SoftX3000 before powering it on.

Major fault of the power supply system causes power failure of the SoftX3000. When the power supply system become normal, it is necessary to power on the SoftX3000.

Take the cabinets in Figure 3-2 as an example. Suppose all the switches are “off” at the moment. The complete procedures for powering on the cabinets of the SoftX3000 are as follows:

II. Turning On the Power of the DC Power Distribution Cabinet

Turn on all switches in the DC power distribution cabinet of the SoftX3000. Now the “RUN” indicator on the panel of the PDBs should be on (green). It should blink once every second indicating the input power supply and internal circuits of the PDBs are normal.



3-4

III. Turning On the Power of PDB of Integrated Configuration Cabinet

Turn on the switches on the PDB of the integrated configuration cabinet one by one, that is, to turn the switches on the PDB to “ON” in the order of SW1 to SW6. Now the “RUN” indicators on the panel of all the UPWR boards in frame 0 and frame 1 should be on (green), indicating the power supplies of the frames are normal.

IV. Turning On the Power of LAN Switch 0 and LAN Switch 1

Turn on the switches of LAN Switch 0 and LAN Switch 1 in the integrated configuration cabinet one by one, that is, to turn the switches of the LAN Switches to “ON”. Now the “POWER” indicators on the panel of the two LAN Switches should be on (green), indicating the power supplies of the LAN Switches are normal.

V. Turning On the Power of KVM/LCD Converter

Turn on the switch of the KVM/LCD converter in the integrated configuration cabinet, that is, to turn the switch to the side with a “—“ symbol. Now the “KVM PWR” indicator on the panel of the KVM should be on (green), indicating that the power supply of the KVM/LCD converter is normal.

VI. Turning On the Power of the Server

Check the indicators on the power switches of the BAM, standby iGWB, and active iGWB in the integrated configuration cabinet.

If the power indicator is green, it means that the power supply of the corresponding server is normal. You cannot press the switch of the server because it will cause power failure of the server.

If the power indicator is orange, it means that the corresponding server is in standby status. You can press the switch of the server. Now the indicator of the switch will turn to green, indicating normal power supply of the server.

VII. Turning On the Power of PDB of Service Processing Cabinet

Turn on the switches of the PDB of the service processing cabinet one by one, that is, to turn the switches of the PDB to “ON” in the order of SW1 to SW6. Now the “RUN” indicators on the panel of all the UPWR boards in frame 2, frame 3, frame 4 and frame 5 should be on (green), indicating the power supplies of the frames are normal.

VIII. Turning On the Power of PDB of Media Resource Server Cabinet

Turn on switches SW1 and SW2 of the PDB in the media resource server cabinet one by one. Now the input power cables of the MRS6000 frame has been powered on.

IX. Turning On the Power of MRS6000 Frame

Turn on the switches on the MRS6000 frame of the media resource server cabinet one by one, that is, to turn the switches on the MRS6000 frame, Feed A and Feed B, to



3-5

“ON”. Now the “PWR” indicators on all the SCC and MPC boards should be on (green), indicating the power supply of the frame is normal.

X. End of Operation

After the above operations, you should check the running status of the components in the cabinet carefully to confirm there is no abnormality. Then you can finish the power-on operation.

3.1.4 Powering on and Restarting Frames

Caution:

Only in the following situations can frames be powered on and restarted: The active and standby SMUI boards in the frame are faulty or down. Major fault of the power supply system causes power failure of the frame. After

repairing the power supply system of the frame, it is necessary to power on the frame.

I. Confirm the Electrical Controlling Relationship

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

II. Turning Off Two Switches Controlling Power Supply of PDB

After confirming the electrical controlling relationship, turn off the two switches controlling power supply of the PDB one by one, that is, to turn the switches to “OFF”. Now the indicators on all the boards of the frame should be off, indicating power-off of the frame.

III. Turning On Two Switches Controlling Power Supply of PDB

Ten seconds after the frame is powered off, you can turn on the two switches controlling power supply of the PDB one by one, that is, to turn the switches to “ON”. Now the “RUN” indicators on all the UPWR boards of the frame should be on (green), indicating power-on of the frame is completed.



3-6

IV. End of Operation

After the above operations, you can open the device panel on the client to see whether the frame has been powered on and working. If there is no abnormality, you can finish the power-on operation.

3.1.5 Powering on and Restarting MRS6000

Caution:

Only in the following situations can MRS6000 be powered on and restarted. The active and standby SCC boards in the MRS6000 frame are faulty or down. Major fault of the power supply system causes power failure of the MRS6000 frame.

After repairing the power supply system of the frame, it is necessary to power on the frame.

I. Turning Off Two Switches of MRS6000 Frame

Turn off the switches on the MRS6000 frame of the media resource server cabinet one by one, that is, to turn the switches on the MRS6000 frame, Feed A and Feed B, to “OFF”. Now the “PWR” indicators on all the SCC and MPC boards should be on (green), indicating the power failure of the MRS6000 frame.

II. Turning On Two Switches of MRS6000 Frame

Turn on the switches on the MRS6000 frame of the media resource server cabinet one by one, that is, to turn the switches on the MRS6000 frame, Feed A and Feed B, to “OFF”. Now the “PWR” indicators on all the SCC and MPC boards should be on (green), indicating the power-on of the MRS6000 frame is completed.

III. End of Operation

After the above operations, you should check the running status of MRS6000 by accessing the Web management interface through IE. If no abnormality is found, you can finish the power-on operation.

3.2 Resetting Operations

3.2.1 Overview of Resetting Operations

The resetting operations include the following categories:

Resetting Frames Resetting Boards



3-7

Resetting Modules by Level Resetting SCC of MRS6000

3.2.2 Resetting Frames

Caution:

Only in the following situations can frames be reset. All the boards in the frame are faulty or down. During major upgrading of software, it is necessary to reset frames.

I. Preparations

If the FCCU/FCSU is in the frame to be reset, before resetting, execute the following operations.

Execute the command BKP SS to back up supplementary service data. Execute the command STR BILIF to fetch the bills from the host manually.

II. Method 1:Resetting Frames Using Command RST FRM

During major upgrading of software, you can execute the command RST FRM to reset frames. For example:

Resetting all boards in frame 0.

RST FRM: FN=0, BT=SMUI-1&FCCU-1&FCSU-1&CDBI-1&BSGI-1&IFMI-1&MRCA-1 &MSGI-1,

ACTIVE/STANDBY=ALL;

Resetting all active boards in frame 0.

RST FRM: FN=0, BT=SMUI-1&FCCU-1&FCSU-1&CDBI-1&BSGI-1&IFMI-1&MRCA-1& MSGI-1,

ACTIVE/STANDBY=MAIN;

Resetting all standby boards in frame 0.

RST FRM: FN=0, BT=SMUI-1&FCCU-1&FCSU-1&CDBI-1&BSGI-1&IFMI-1&MRCA-1& MSGI-1,

ACTIVE/STANDBY=STANDBY;

III. Method 2:Resetting Frame Through Resetting All Boards in Frame

During failure or down of all the boards in the frame, you can reset the frame through resetting all the boards in the frame according to the following steps.

1) Press the “Reset” button on the panel of the SMUI boards to reset the active and standby SMUIs.



3-8

2) Press the “Reset” button on the panel of the service boards (front boards) to reset the service boards.

IV. Method 3:Resetting Frame Through Inserting and Pulling out Active and Standby SMUIs

During failure or down of all the boards in the frame, you can reset the frame through inserting and pulling out the active and standby SMUIs if method 2 is not working.

3.2.3 Resetting Boards

Caution:

Only in the following situations can boards be reset. The board is faulty or down. In this case, you can reset the board directly. During major upgrading of software, it is necessary to reset boards. In this case, you should reset the standby boards first. After the standby boards are working normally, reset the active boards.

I. Preparations

If the board to be reset is the FCCU/FCSU, execute the following operations.


II. Method 1: Resetting Boards Using Command RST BRD

During major upgrading of software, you can execute the command RST BRD to reset boards. For example:

Resetting the front board in slot 0 of frame 0.

RST BRD: FN=0, SN=0, PSN=FB;

Resetting the back board in slot 13 of frame 0.

RST BRD: FN=0, SN=13, PSN=BB;

III. Method 2:Resetting Boards Through Pressing the “Reset” Buttons on boards

During failure or down of the board, you can reset the board through pressing the “Reset” button on the panel of the board.



3-9

3.2.4 Resetting Modules by Level

I. Overview of Resetting Modules by Level

Only in the following situations can you reset the modules by level:

Call congestion of long duration and wide area happens in a FCCU module. The running of a module is not stable.

Directly resetting the board where this module is located is risky. Therefore, you can use leveled resetting to reset the module.

Generally, you can reset modules by level using software methods. The SoftX3000 provides four levels of resetting operation in the command RST MDU. Different levels of resetting have different influence on the running of the system.

II. Preparations

If the module to be reset is the FCCU/FCSU, execute the following operations.


III. Resetting Modules at Level 1

Resetting modules at level 1 has the following features:

Carrying out checking inside the module. Clearing temporarily allocated resources. Keeping bills and subscribers that have completed the conversation. Affecting the subscribers that are connecting. Not loading data and programs.

IV. Resetting Modules at Level 2


Carrying out checking between modules. Clearing temporarily allocated resources. Keeping bills and subscribers that have completed the conversation. Affecting the subscribers that are connecting. Not loading data or programs.

V. Resetting Modules at Level 3


Carrying out software resetting of the specified module Keeping bills Affecting the subscribers that have completed the conversation or are connecting Not loading programs or loading data.



3-10

VI. Resetting Modules at Level 4


Carrying out software resetting of the specified module. Keeping bills. Affecting the subscribers that have completed the conversation or are connecting. Loading programs and data.

VII. Examples:

Carrying out level 1 resetting for No. 22 active module.

RST MDU: MN=22, EX=MAIN, LEVEL=LVL1;

Carrying out level 1 resetting for No. 22 standby module.

RST MDU: MN=22, EX=STDBY, LEVEL=LVL1;







3.2.5 Resetting SCC of MRS6000

Caution:

Only when the SCC of the MRS6000 is faulty or down can you reset the SCC.

I. Resetting SCC Through Web Management Interface

Reset the SCC through the Web management interface according to the following steps.

1) Log on to the Web management interface of the MRS6000. Click the “Configuration” option in the navigation tree at the left of the interface.

2) Click the “Slot Configuration” in the option list of the “Configuration”. 3) Click the "Reset Card" in the option list of the "Slot Configuration", as shown in

Figure 3-3.



3-11

Figure 3-3 Web management interface of the MRS6000

4) Select the slot of the SCC board to be reset, for example, slot 1. 5) Select the type of reset operation: Normal (the board will not be reset during

running) or Forced (the board will be reset anyway). 6) Click the <Execute> button to reset the specified SCC. If the MRS6000 frame only

has one SCC, the system will reset all the MPCs when resetting the SCC.

II. Resetting Boards Through Pressing “Reset” Button

You can press the “Reset” button on the panel of the SCC to reset the SCC when it is necessary to perform hardware resetting operation.

3.3 Restoring BAM Database

3.3.1 Overview of Restoring BAM Database

The Back Administration Module (BAM) database is an SQL database stored in the BAM hard disk in datasheet format, and it is used to store all the data generated during the data configuration operations by the user. In the following cases, it is necessary to restore the BAM database.

If the BAM Server software is reinstalled, the BAM database will be cleared. In this case, you can replace the current empty database with the backup BAM database.

When the emergency workstation takes over the BAM due to the BAM failure, or the BAM resumes normal operation after troubleshooting, it is required to replace



3-12

the BAM database being used in the BAM or emergency workstation with the latest database.

There are two methods to restore the BAM database. One is to execute the BAM Server software installer, and the other is to use the SQL Server 2000 tools. Generally, it is recommended to use the first method.

3.3.2 Using BAM Server Software Installer

Using the BAM Server software installer can restore the BAM database as well as the BAM registry and bill meter. By default, you can use the following backup files under the directory F:\SoftX3000 in the BAM hard disk:

The BAM database backup file: The file name format is “BamYYYYMMDD.dat”, where “YYYY” indicates year, “MM” stands for month and “DD” denotes date.

The BAM registry backup file: The file name is “BamReg.bak”. The BAM bill meter backup file: The file name is “MeterBak.dat”.

The following steps guide you through restoring the BAM database by using the BAM Server software installer.

I. Stopping BAMService

Stop the BAMService according to the following steps.

1) On the desktop of Windows 2000 Server, select [Start/Programs/Administrative Tools/Services] to pop up the [Services] window as shown in Figure 3-4.

Figure 3-4 [Services] window (1)

2) Right click on [BAMService], and then select [Stop] on the pop-up menu.



3-13

3) The system will stop the “BAMService”. If the operation is successful, the [Status] column corresponding to [BAMService] will become blank as shown in Figure 3-5, indicating that the “BAMService” has been stopped.


II. Stopping Smirror Service

Refer to the steps in the above section to stop the “Smirror” service. If the operation is successful, the [Status] column corresponding to [Smirror] will become blank as shown in Figure 3-5, indicating that the “Smirror” service has been stopped.

III. Checking SQL Server Service Manager

Check whether the “SQL Server Service Manager” is started according to the following steps.

1) On the desktop of Windows 2000 Server, double click on the “Service Manager”

icon in the status bar at the lower right corner of the screen, and the system will

pop up the [SQL Server Service Manager] window, as shown in Figure 3-6.



3-14

Figure 3-6 [SQL Server Service Manager] window

2) If the status bar on the [SQL Server Service Manager] window (Figure 3-6) shows “Running - \\W27500 MSSQLServer”, the “SQL Server Service Manager” is running normally. In this case, you can go on to Step IV Stopping BAM Manager.

Note:

The “W27500” on the status bar on the [SQL Server Service Manager] window (Figure 3-6) is the computer name of the BAM. It is only an example here. The name might be different in the actual application.

3) If the status bar on the [SQL Server Service Manager] window (Figure 3-6) shows “Stopping - \\W27500 MSSQLServer”, the “SQL Server Service Manager” is not running normally. In this case, you need to select “SQL Server” in the [Services]

box, and click the <Start/Continue> button on the window to start the “SQL

Server Service Manager”.

IV. Stopping BAM Manager

Stop the BAM Manager according to the following steps.

1) On the desktop of Windows 2000 Server, double click on the “BAM Manager” icon

on the status bar at the lower right of the screen, and the system will pop up the

[BAM Manager] window, as shown in Figure 3-7.



3-15

Figure 3-7 [BAM Manager] window

2) Click the <Exit> button at the upper left of the window shown in Figure 3-7, and the system will prompt "Are you sure that you want to exit?”. Click <Yes> to confirm it.

3) The system pops up the [Service Control] interface as shown in Figure 3-8. After a few seconds, the BAM Manager will be stopped.

Figure 3-8 [Service Control] interface

V. Executing BAM Server Software Installer

Insert the “U-SYS SoftX3000 operation and maintenance software package CD” into CD-ROM drive, or directly execute the file SETUP.EXE in the installation directory of the BAM Server software to start the installer.

After initialization, the [Setup Instruction] interface will pop up. Select [Restore SoftX3000 Environment and Data] and click <Next> to proceed, as shown in Figure 3-9.



3-16

Figure 3-9 S[Setup Instruction] interface

VI. Selecting or Specifying Complete Path of Backup File

The system pops up the [Restore Data] interface as shown in Figure 3-9, on which you need to fill in or select the complete paths of the backup files. The operations are as follows.

1) In the [SoftX3000 Registry Backup File] box, fill in the complete path of the BAM registry backup file. By default, the complete path is “F:\SoftX3000\ BamReg.bak”. It should be noted that you must fill in the name of the backup registry file when restoring data on the emergency workstation if the structure of the software directory of the emergency workstation is the same as that of the BAM (That is, both of them used the default installation path). If their structures are different, you cannot enter the name of the backup registry file when restoring data on the emergency workstation.

2) In the [SoftX3000 System Database Backup File] box, fill in the complete path of the BAM database backup file. By default, the complete path is “F:\SoftX3000 \BamYYYYMMDD.dat”. It is recommended to select the latest backup file.

3) In the [SoftX3000 Bill Database Backup File] box, fill in the complete path of the BAM meter backup file. By default, the complete path is “F:\SoftX3000\ MeterBak.dat”.

After specifying the backup files, click <Restore> to proceed.



3-17

Figure 3-10 [Restore Data] interface

VII. Continuing Operation

Continue the operations according to the following steps.

1) The system prompts the [Question] dialog box as shown in Figure 3-11, prompting you whether to proceed with the irreversible operation. To confirm it, click <Yes>

Figure 3-11 [Question] dialog box

2) The system pops up the [Information] dialog box as shown in Figure 3-12, prompting the time required to restore the data. Click <OK> to confirm it.



3-18

Figure 3-12 [Information] dialog box (1)

3) The system pops up the [Information] dialog box as shown in Figure 3-13, prompting you to close all running programs, processes and real-monitor function. Click <OK> after completing all the operations.

Figure 3-13 [Information] dialog box (2)

4) The system displays the restoring progress as shown in Figure 3-14.

Figure 3-14 Progress bar

VIII. Restarting BAM

After the restoration is completed, the system pops up the [Setup Complete] interface as shown in Figure 3-15, prompting you to restart the computer. Select [Yes, I want to restart my computer now] and click <Finish> to restart the BAM Server.



3-19

Figure 3-15 S[Setup Complete] interface

IX. Converting Database Files

Because the restored BAM database file is not the final file to be loaded, it is required to convert the format before loading it to the host.

After the BAM Server restarts, execute the following MML commands on the maintenance console.

1) Run LOF to set offline. 2) Run SET FMT:STS=ON to set the format conversion switch to “ON”. 3) Run FMT to convert the format of all data. 4) Run LON to set online.

X. Checking Data Consistency

After completing the above steps, be sure to use the command STR CRC to check the consistency between the host data and BAM data of all modules. If the host data and BAM data of all modules are consistent, the BAM data restoration is completed successfully. If there is a table listing the inconsistencies between the host data and BAM data of a module, it is required to take one of the following measures to solve the problem according to the actual conditions.

1) Use the command SND SPD to resend to the host the corresponding data table to replace the one that has inconsistent data in the module.

2) If the problem still exists, it is required to reset the host so as to reload all data from the BAM Server. Before resetting the host, be sure to fetch bills to avoid bill loss.



3-20

3.3.3 Using SQL Server Tools

I. Stopping BAMService

Stop the BAMService according to the following steps.



2) Right click on [BAMService], and then select [Stop] on the pop-up menu. 3) The system will stop the “BAMService”. If the operation is successful, the [Status]

column corresponding to [BAMService] will become blank as shown in Figure 3-17, indicating that the “BAMService” has been stopped.



3-21


II. Stopping Smirror Service

Refer to the steps in the above section to stop the “Smirror” service. If the operation is successful, the [Status] column corresponding to [Smirror] will become blank as shown in Figure 3-17, indicating that the “Smirror” service has been stopped.

III. Checking SQL Server Service Manager

Check whether the SQL Server Service Manager is started according to the following steps.

1) On the desktop of Windows 2000 Server, double click on the “Service Manager”

icon in the status bar at the lower right corner of the screen, and the system will

pop up the [SQL Server Service Manager] window, as shown in Figure 3-18.



3-22

Figure 3-18 [SQL Server Service Manager] window

2) If the status bar on the [SQL Server Service Manager] window (Figure 3-18) shows “Running - \\W27500 MSSQLServer”, the “SQL Server Service Manager” is running normally. In this case, you can go on to Step 4.

Note:

The “W27500” on the status bar on the [SQL Server Service Manager] window (Figure 3-18) is the computer name of the BAM. It is only an example here. The name might be different in the actual application.

3) If the status bar on the [SQL Server Service Manager] window (Figure 3-18) shows “Stopping - \\W27500 MSSQLServer”, the “SQL Server Service Manager” is not running normally. In this case, you need to select “SQL Server” in the

[Services] box, and click the <Start/Continue> button on the window to start

the “SQL Server Service Manager”.

IV. Stopping BAM Manager

Stop the BAM Manager according to the following steps.

1) On the desktop of Windows 2000 Server, double click on the “BAM Manager” icon

on the status bar at the lower right of the screen, and the system will pop up the

[BAM Manager] window, as shown in Figure 3-19.



3-23



3) The system pops up the [Service Control] interface as shown in Figure 3-20. After a few seconds, the BAM Manager will be stopped.

Figure 3-20 [Service Control] interface

V. Logging On to SQL Database Server

On the desktop of Windows 2000 Server, select [Start / Programs / Microsoft SQL Server / Enterprise Manager], and the system pops up the [SQL Server Enterprise Manager] window as shown in Figure 3-21.



3-24

Figure 3-21 [SQL Server Enterprise Manager] window

In normal cases, the system will log on to the SQL database server automatically. If logging on is successful, the system will display the computer name (W27500 in this example) of the BAM Server under the [SQL Server Group] node in the left pane as shown in Figure 3-21, and there is a green circle with a white triangle in the icon at the

left of the computer name. See .

If the system cannot log on to the SQL database server, select [Action/New SQL Server Registration…] in Figure 3-21 and follow the system prompts to accept all default options until logging on to the SQL database server.

VI. Restoring SQL Database

Restore the SQL database according to the following steps.

1) In the left pane as shown in Figure 3-21, expand [Microsoft SQL Servers/SQL Server Group/W27500 (Windows NT)/Databases] and select the [Bam].

2) Right click and select [All Tasks/Restore database…] from the pop-up menu. The system will prompt the [Restore database] interface as shown in Figure 3-22.



3-25

Figure 3-22 [Restore database] interface (1)

3) As shown in Figure 3-22, select [From device] in the [Restore] field and select [Database-complete] in the [Restore backup set] field. After above settings, click <Select Devices…> to proceed.

4) The system pops up the [Choose Restore Devices] interface as shown in Figure 3-23, prompting you to select the device (that is, the file path) where the BAM database backup file is located.



3-26

Figure 3-23 [Choose Restore Devices] interface (1)

The interface shows the latest BAM database backup file. Click <Remove All> to clear the record and click <Add…> to add a specific file.

5) The system pops up the [Choose Restore Destination] interface as shown in Figure 3-24, prompting you to select the path of the BAM database file.

Figure 3-24 [Choose Restore Destination] interface

If it is necessary to specify the file path, select or fill in the file path in the [File name] box, for example, F:\SoftX3000\Bam20031020.bat.



3-27

If you want to select the BAM database file from the default folder F:\SoftX3000, select a file from the [Backup device] drop-down list.

After selecting or filling in the correct database file, click <OK> to continue.

6) The system will return to the [Choose Restore Devices] interface, on which the specified the BAM database file is displayed in the [Device name] box as shown in Figure 3-25. Confirm it and click <OK> to proceed.

Figure 3-25 [Choose Restore Devices] interface (2)

7) The system will return to the [Restore database] interface, on which the specified the BAM database file is displayed in the [Devices] box as shown in Figure 3-26. Click the [Option] tab on the top of the interface.



3-28


8) In the “Option” tag of the [Restore Database] interface, select the [Force restore over existing database] as shown in Figure 3-27, indicating to restore over the existing database forcedly. Confirm that the paths and names of the two logical files (Bam_Data and Bam_Log) are correct in the “Restore database files as” box (Figure 3-27 shows the default values). If they are correct, click <OK> to proceed.



3-29


Caution:

If [Force restore over exiting database] is not selected, it may cause repeated records to exist in the BAM database, and the data configuration into collision. During the installation of the BAM server software or emergency workstation application software, if you did not use the default installation path, you must correctly specify the path and name of the logical files “Bam_Data” and “Bam_Log”. Otherwise, you will fail to restore the BAM database

9) The system displays the restoring progress as shown in Figure 3-28.



3-30

Figure 3-28 [Restore Progress] interface

10) After the restoration is completed, the system will prompt “Restore of database ‘Bam’ completed successfully”. Click <OK> to confirm it.

11) By now, the BAM database has been restored.

VII. Restarting BAMService

Restart the BAMService according to the following steps.



2) Right click on [BAMService], and then select [Start] on the pop-up menu to restart the "BAMService”.



3-31

VIII. Restarting Smirror Service

Refer to the steps in the above section to start the “Smirror” service.

IX. Restarting BAM Service Processes

On the desktop of Windows 2000 Server, select [Start/Programs/U-SYS SoftX3000 Operation and Maintenance Center/U-SYS SoftX3000 Server], and the system pops up the [BAM Manager] window. When the status of all the BAM service processes becomes “Started” as shown in Figure 3-30, all the BAM service processes is started.


X. Converting Database Files

Because the restored BAM database file is not the final file to be loaded, it is required to convert its format according to the following steps before loading it to the host.

1) Run LOF to set offline. 2) Run SET FMT:STS=ON to set the format conversion switch to “ON”. 3) Run FMT to convert the format of all data. 4) Run LON to set online.

XI. Checking Data Consistency

After completing the above steps, be sure to use the command STR CRC to check the consistency between the host data and BAM data of all modules. If the host data and BAM data of all modules are consistent, the BAM data restoration is completed successfully. If there is a table listing the inconsistencies between the host data and BAM data of a module, it is required to take one of the following measures to solve the problem according to the actual conditions.



3-32

1) Use the command SND SPD to resend to the host the corresponding data table to replace the one that has inconsistent data in the module.

2) If the problem still exists, it is required to reset the host so as to reload all data from the BAM Server. Before resetting the host, be sure to fetch bills to avoid bill loss.

3.4 Switchover and Recovery of BAM The BAM is the core device for the terminal system of the SoftX3000 to implement operation and maintenance (OAM). It bridges the communication between workstations and the host. For the reliability of the terminal system, the SoftX3000 has emergency workstations to work as the hardware backup devices for the BAM.

Emergency workstations are important components of the terminal system of the SoftX3000. The major function is to replace the BAM when emergent fault happens (for example, the BAM breakdown) so that you can restore the terminal system quickly. Meanwhile, you can have the opportunity to repair the BAM when the emergency workstation is working.

3.4.1 Using Emergency Workstation to Replace BAM

I. Preparations

You need to make the following preparations before using emergency workstations to replace the BAM:

1) Make sure that the emergency workstation is working normally. If the BAM is infected by viruses, you should make sure that the emergency workstation is virus free. Otherwise, scan and kill the viruses or reinstall the system.

2) Make sure that the Ethernet cables from the emergency workstation to LAN Switch 0 and LAN Switch 1 of the integrated configuration cabinet are established but disconnected.

II. Backing Up BAM Database

When accidents happen to the BAM, you need to try your best to back up the BAM database manually so that the data will be consistent after you start to use the emergency workstation. The operations are as follows.

1) Stop all data configuration operations immediately. Be sure to disconnect the BAM with the external computer network.

2) Start the client side program on the BAM and execute the command BKP DB to back up the BAM database manually.

3) Connect the BAM with the external computer network through cables. On the emergency workstation, copy all the recently modified “.dat” and “.bak” files under the F:\SoftX3000 directory in the BAM hard disk. It is recommended to save these latest files to a directory (other than the F:\SoftX3000 directory) in the hard disk of the emergency workstation.



3-33

On the emergency workstation, you can copy the files in the BAM hard disk by the following method:

On the desktop of Windows operating system, select [Start/Run…] and enter “\\SX3KBAM\F$\SoftX3000” in which “SX3KBAM” is the computer name of the BAM. You can replace it with the actual name if applicable.

The system will pop up an “Enter Network Password” window. Enter the account name and password of the system administrator for the Windows 2000 Server of the BAM. You can use “Administrator” as the account name. After confirmation, on the workstation, you can access the F:\SoftX3000 directory in the hard disk of the BAM.

III. Disconnecting BAM

Disconnect the BAM with all the other devices according to the following steps.

1) Disconnect the BAM with the host: Unplug the two Ethernet cables at the BAM side connecting the BAM with LAN Switch 0 and LAN Switch 1.

2) Disconnect the BAM with external computer network: Unplug the Ethernet cables at the BAM side connecting the BAM with the external computer network.

IV. Restoring BAM Database on Emergency Workstation

Before starting to use the emergency workstation, you must use the latest data to restore the BAM database on the emergency workstation to maintain consistency. For detailed operations to restore the BAM database on the emergency workstation, refer to the descriptions in section 3.3.1 “BAM Server Software Installer”.

V. Starting BAM Manager

Under normal situations, the emergency workstation will not start the BAM Manager automatically. Therefore, you must start the BAM Manager for the emergency workstation to replace the BAM.

On the desktop of the Windows operating system, select [Start/Programs/U-SYS SoftX3000 Operation and Maintenance Center/U-SYS SoftX3000 Server] or press the <Enter> key after entering “D:\ SoftX3000\SecurityManager.EXE”, and you can start the BAM Manager, as shown in Figure 3-31.



3-34


VI. Converting Format of All Data.

On the desktop of the Windows operating system, select [Start/Programs/U-SYS SoftX3000 Operation and Maintenance Center/U-SYS SoftX3000 Client] and log on as a super administrator. Then execute the following MML commands on the client.

1) Run LOF to set offline. 2) Run SET FMT:STS=ON to set the format conversion switch to “ON”. 3) Run FMT to convert the format of all data.

VII. Reconfiguring Network Parameters and Network Connections

Reconfigure the network parameters and network connections of the emergency workstation according to the following steps.

1) Modify the IP address of the external network adaptors of the emergency workstation to the same as those of the BAM so that the emergency workstation can replace the BAM.

2) Configure the IP addresses of the network adaptors on the emergency workstation that are responsible for communication with the host: Set the IP address of network adaptor 0 to 172.20.200.0 / 255.255.0.0 and the IP address of network adaptor 1 to 172.30.200.0 / 255.255.0.0.

3) Connect the emergency workstation to the host: Connect network adaptor 0 on the emergency workstation with LAN Switch 0 and network adaptor 1 with LAN Switch 1.



3-35

Caution:

It is important to note that the network connection between the emergency workstation and the host is set up according to the standard stipulation. In the actual applications, if the emergency workstation cannot communicate with the host, make the following modifications: Connect network adaptor 0 on the emergency workstation with LAN Switch 1 and network adaptor 1 with LAN Switch 0.

VIII. Setting Online.

Start the client on the emergency workstation and execute the command LON to set online.

IX. Checking Data

Execute the command STR CRC to check the data on the host and BAM. If all the data tables checked are consistent, ignore the following steps. If inconsistent data table exists, execute the following steps.

1) Execute the command LST USD to query whether there are data records that have not been sent to the host. If yes, execute the command SND USD to resend these data records.

2) Collect the operation records after the date of the BAM database backup file. Re-execute these operations.

3) Re-execute the command STR CRC to check the data on the host and BAM. If inconsistent data exist, contact the Technical Service Department of Huawei.

X. Checking Settings of Emergency Workstation

Log on to the terminal system of the SoftX3000 through an ordinary workstation and execute all kinds of query or maintenance operations such as display of the panel of devices, query of office data, display of status of gateways and display of status of signaling gateways. If the above functions are normal, the emergency workstation has replaced the BAM successfully.

Up to now, using the emergency workstations to replace the BAM has been completed.

3.4.2 Stopping Using Emergency Workstations and Restoring BAM

I. Backing Up BAM Database

You need to stop using the emergency workstation and restore the BAM after the BAM has been repaired. You need to back up the BAM database manually according to the following steps to maintain data consistency.



3-36

1) Stop all data configuration operations immediately. Be sure to disconnect the emergency workstation with the external computer network.

2) Start the client side program on the emergency workstation and execute the command BKP DB to back up the BAM database manually.

3) Connect the emergency workstation with external computer network through Ethernet cables. On the BAM, copy all latest modified “.dat” and “.bak” files under the F:\SoftX3000 directory in the hard disk of the emergency workstation.

Note:

On the BAM, you can copy the files in the hard disk of the emergency workstation by the following method:

On the desktop of Windows operating system, select [Start/Run…] and enter “\\SX3KBAM-EM\F$\SoftX3000” in which “SX3KBAM-EM” is the computer name of the emergency workstation. You can replace it with the actual name if applicable.

The system will pop up an “Enter Network Password” window. Enter the account name and password of the system administrator for the Windows 2000 Server of the emergency workstation. You can use “Administrator” as the account name. After confirmation, on the BAM, you can access the F:\SoftX3000 directory in the hard disk of the emergency workstation.

II. Stopping BAM Manager on Emergency Workstation

Stop the BAM Manager on the emergency workstation according to the following steps.

1) On the desktop of Windows 2000 Server, double click the “BAM Manager” icon

on the status bar at the lower right of the screen, and the system will pop up the [BAM Manager] window, as shown in Figure 3-32.



3-37



3) The system pops up the [Service Control] interface. After a few seconds, the BAM Manager will be stopped.

III. Stopping Emergency Workstation

Stop running the emergency workstation according to the following steps.

1) Disconnect the emergency workstation with the host: Unplug the two Ethernet cables at the emergency workstation side connecting the emergency workstation with LAN Switch 0 and LAN Switch 1.

2) Modify the IP addresses of the network adaptors connecting the emergency workstation with the external computer network to the original ones to avoid collision with the IP addresses of the BAM to be configured.

IV. Restoring BAM Database on BAM

Before restoring the running of the BAM, you must use the newest data to restore the BAM database on the BAM to maintain consistency. For detailed operations to restore the BAM database on the BAM, refer to the descriptions in section 3.3.1 “BAM Server Software Installer”.

V. Reconfiguring Network Parameters and Network Connections

Reconfigure the network parameters and network connections of the BAM according to the following steps.



3-38

1) Modify the IP addresses of the network adaptors connecting the BAM with the external computer network to the original IP addresses so that the workstations can log on to the BAM.

2) Configure the IP addresses of the network adaptors on the BAM that are responsible for communication with the host: Set the IP address of network adaptor 0 to 172.20.200.0 / 255.255.0.0 and the IP address of network adaptor 1 to 172.30.200.0 / 255.255.0.0.

3) Disconnect the BAM with the host: Connect network adaptor 0 on the BAM with LAN Switch 0 and network adaptor 1 with LAN Switch 1.

Caution:

It is important to note that the network connection between the BAM and the host is set up according to the standard stipulation. In the actual applications, if the BAM cannot communicate with the host, make the following modifications: Connect network adaptor 0 on the BAM with LAN Switch 1 and network adaptor 1 with LAN Switch 0.

VI. Setting Online.

Start the client side program on the BAM and execute the command LON to set online.

VII. Checking Data

Execute the command STR CRC to check the data on the host and BAM. If all the data tables checked are consistent, ignore the following steps. If inconsistent data table exists, execute the following steps.

1) Execute the command LST USD to query whether there are data records that have not been sent to the host. If yes, execute the command to resend these data records.

2) Collect the operation records after the date of the BAM database backup files backed up. Re-execute these operations.

3) Re-execute the command STR CRC to check the data on the host and BAM. If inconsistent data exist, contact the Technical Service Department of Huawei.

VIII. Checking Functions of BAM

Log on to the terminal system of the SoftX3000 through an ordinary workstation and execute all kinds of query or maintenance operations such as display of the panel of devices, query of office data, display of statuses of gateways and display of statuses of signaling gateways. If the above functions are normal, the BAM is normal.

Up to now, stopping the emergency workstations and restoring the BAM have been completed.



3-39

3.5 Scanning and Killing Virus on BAM As a computer, the running of the BAM can be affected by external viruses. If you are certain or suspect that the BAM is infected by viruses, you must scan and kill the viruses on the BAM according to the procedures in this section.

3.5.1 Preparations

Scanning and killing viruses on the BAM are risky. The consequence is unpredictable. The worst result is that It will cause system breakdown. Therefore, you must make the following preparations before scanning and killing the viruses:

I. Preparing Software (CD)

Prepare the software (compact disks) as shown in Table 3-2.

Table 3-2 List of software (CDs)

Name of CD Use of CD

ServeRAID Support (CD) It is used to configure the RAID 1 of the hard disk of the server.

ServeRAID 5.10 Driver for Windows 2000 Server (floppy disk)

It is used to install the driver of the SCSI controller of the server.

Windows 2000 Server (CD) It is used to install the operating system on the BAM or the emergency workstation.

Microsoft Windows 2000 Service Pack4 (CD)

It is used to install the Pach4 patch of the operating system.

IBM 10/100 Ethernet Server Adapters Family Device Drivers and Installation (CD)

It is used to install the driver of the extension network adaptor of the BAM.

SQL Server 2000 Standard Edition (CD)

It is used to install the database software on the BAM or the emergency workstation.

SQL Server 2000 Service Pack 3 (CD)

It is used to install the patch of the SQL Server 2000 on the BAM or the emergency workstation.

U-SYS SoftX3000 operation and maintenance application software packet (CD)

It is used to install the operation and maintenance software on the BAM or the emergency workstation.

II. Preparing Antivirus Software

Prepare the antivirus software according to the following steps.

1) Huawei recommends you to use the Norton AntiVirus 7.6 or later.



3-40

2) Read the latest notice on the website of Norton Corporation and download the latest virus definition file to the CD. The website of Norton Corporation is:http://www.norton.com

III. Preparing Patch Files for Windows 2000 Server or SQL Server 2000 (Optional)

Sometimes the BAM is infected by the viruses because of the security holes existing in the Windows 2000 Server or SQL Server 2000. Microsoft Corporation has the corresponding patches on its website.

You need to prepare the patch files to the Windows 2000 Server or SQL Server 2000.Read the latest notice on the website of Microsoft Corporation and download the latest patch files to the CD. The website of Microsoft Corporation is:http://www.micorosoft.com

IV. Preparing Emergency Workstation

The emergency workstation has the same software structure as the BAM. Therefore, if the BAM is infected by a virus, it is quite possible that the emergency workstation is infected by the same virus. In this case, you need to scan and kill the virus (or reinstall the system) on the emergency workstation first to make sure that the emergency workstation meets the following requirement.

The emergency workstation will not be infected by the virus. Appropriate antivirus software (for example, Norton AntiVirus) has been installed

and the virus description database has been renewed.

Caution:

It is important to note that when the patches are used to the Windows 2000 Server or SQL Server 2000 to restore the emergency workstation, you need to contact the Technical Service Department of Huawei to get technical support because these patches might have not passed the compatibility test of Huawei.

V. Backing Up BAM Database

For security, you must back up the BAM database manually on the BAM according to the following steps before scanning the BAM for viruses.

1) Stop all data configuration operations immediately. Be sure to disconnect the BAM with the external computer network.

2) Start the client side program on the BAM and execute the command BKP DB to back up the BAM database manually.



3-41

VI. Backing Up Data in Hard Disk of BAM

Connect the BAM with external computer network through Ethernet cables. On the emergency workstation, copy all files under the following directories in the hard disk of the BAM:

Directory Description

D:\Data It is used to store the files to be loaded to the host. It is composed of two sub-directories and source files of the host software and data.

D:\Mssql\Data It is used to store system database files.

E:\Mssql\Data It is used to store database log files.

F:\SoftX3000 It is used to store files such as the BAM registry and the BAM database.

Note:

On the emergency workstation, you can copy the files in the BAM hard disk by the following methods (taking the F:\SoftX3000 directory as an example):

On the desktop of Windows operating system, select [Start/Run…] and enter “\\SX3KBAM\F$\SoftX3000” in which “SX3KBAM” is the computer name of the BAM. You can replace it with the actual name if applicable.

The system will pop up an “Enter Network Password” window. Enter the account name and password of the system administrator for the Windows 2000 Server of the BAM. You can use “Administrator” as the account name. After confirmation, on the workstation, you can access the F:\SoftX3000 directory in the hard disk of the BAM.

VII. Using Emergency Workstations to Replace BAM

It takes quite a long time to scan and kill the viruses on the BAM. The BAM breakdown is possible during the process. Therefore, in order to reduce the effect on the SoftX3000 terminal system, you need to use the emergency workstation to replace the BAM before scanning the BAM for viruses.

For detailed operations, refer to section 3.4.1 “Using Emergency Workstations to Replace BAM”.

3.5.2 Scanning and Killing Virus on BAM

I. Disconnecting BAM

Disconnect the BAM with all the other devices according to the following steps.



3-42

1) Disconnect the BAM with the host: Unplug the two Ethernet cables at the BAM side connecting the BAM with LAN Switch 0 and LAN Switch 1.

2) Disconnect the BAM with external computer network: Unplug the Ethernet cables at the BAM side connecting the BAM with the external computer network.

II. Rebooting Windows Operating System of BAM in Safe Mode

Start the BAM. Press the <F8> key after hardware self-test. Choose to start Windows 2000 Server in “Safe mode”.

III. Installing Antivirus Software

In the “Safe mode” of Windows 2000 Server, you can install the Norton AntiVirus on the BAM. For installation method, refer to the user manual attached to the software or online help.

IV. Updating Virus Definition File

After installing the Norton AntiVirus, you need to download the latest virus definition file. For the operation method, refer to the user manual attached to the software or online help.

V. Configuring Antivirus Software

Configure the antivirus software according to the following steps.

1) On the desktop of Windows 2000 Server, select [Start/Programs/Norton AntiVirus Corporate Edition/Norton AntiVirus Corporate Edition] to pop up the [Norton AntiVirus Corporate Edition] window as shown in Figure 3-33.

Figure 3-33 Norton AntiVirus Corporate Edition window (1)



3-43

2) In Figure 3-33, click the [Scan/Scan Computer] on the navigation tree on the left and the system will pop up the [Scan Computer] sub-window. Select [My Computer] to scan the whole computer, as shown in Figure 3-34.


Note:

The squares at the left of the sub-window have different meanings: : means the file, folder or drive is not selected. : means one file or folder is selected. : means one folder or drive is selected. Meanwhile, it means all items in the folder or

drive are selected. : means the folder or drive is not selected, but at least one item in the folder or drive

is selected.

3) In Figure 3-34, click the cross square at the left of “Local Disk (D)” to expand the folders in drive D. Click the at the left of the folders “D:\Data” and “D:\MSSQL” to make it become , indicating the two folders are not selected or scanned, as shown in Figure 3-35.



3-44


4) Use the same method to make the at the left of “E:\MSSQL” and “F:\SoftX3000” become , indicating the files under “E:\MSSQL” and “F:\SoftX3000” are not to be scanned.

VI. Scanning and Killing Virus on BAM

In Figure 3-34, click the <Scan> button at the lower right to scan the specified files and folders in the hard disk of the BAM. The progress and status will be shown as that in Figure 3-36.

Figure 3-36 ”Scan Computer” window



3-45

During the scanning, Norton Antivirus will record the information in detail such as the name of the infected file, virus name and type, whether to quarantine the virus and whether to clear the virus. Save these information and send them to Huawei for analysis.

VII. Confirming Whether Operation Is Successful

After the scanning is finished, you need to execute the following steps according to the information displayed in Figure 3-36.

If viruses that are unable to be quarantined or cleared exist on the BAM, the scanning is not totally successful. Contact Huawei for technical support in time.

If all viruses are cleared, the scanning is successful and you can continue to do the restoring work as follows.

3.5.3 Restoring Work

I. Uninstalling Antivirus Software

After all viruses are cleared on the BAM, uninstall the antivirus software on the BAM in time. On the desktop of Windows 2000 Server, you can select [Start / Setting / Control Panel] to open the control panel. Double click “Add/Remove Programs” and uninstall the antivirus software in the pop-up interface.

II. Confirming Whether It Is Necessary to Load Patches

The latest patch files released on the website of Microsoft Corporation for Windows 2000 Server or SQL Server 2000 might have not passed the compatibility test of Huawei. Loading these patch files will cause unexpected consequence.

Therefore, you need to contact the Technical Service Department of Huawei to see whether it is possible to load the patches for Windows 2000 Server or SQL Server 2000. Only after the permission of professional technicians of Huawei can you load these patches.

Caution:

It is important to note that if it is necessary to load patches for the Windows 2000 Server or SQL Server 2000 on the BAM, ask for the related operation guide from the Technical Service Department of Huawei.

III. Restarting BAM

Shut down the Windows operating system and restart the BAM.



3-46

IV. Checking Whether BAM Is Working

After restarting the BAM, you can check whether the BAM is working by the following methods.

Windows 2000 Server can be started. SQL Server Service Manager can be started. The BAM Manager can be started and the statuses of all service processes are

“Started”, as shown in Figure 3-37.


V. Stop Using Emergency Workstations and Restore BAM

When the BAM is working normally, you can stop using the emergency workstation and restore the BAM. For detailed description, refer to section 3.4.2 “Stopping Using Emergency Workstations and Restoring BAM”.

VI. Restoring Emergency Workstation

After restoring the running of the BAM, restore the emergency workstation according to the following steps.

1) Uninstall the antivirus software on the emergency workstation. 2) Load the patches for the Windows 2000 Server or SQL Server 2000 on the

emergency workstation if applicable. 3) Restart the emergency workstation. Check whether the network communication is

normal between the emergency workstation and the BAM. Check whether the Smirror service is started normally.

Emergency Maintenance Manual U-SYS SoftX3000 SoftSwitch System Chapter 4 Maintenance Record Table


4-1

Chapter 4 Maintenance Record Table

4.1 Emergency Maintenance Note If you failed to remove the fault after handling, ask for help from Huawei by phone or fax. In order to shorten the troubleshooting time, record your fault handling 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 “Emergency Maintenance Note” for fax as follows:



4-2

Emergency Maintenance Note Please fill in the following contents in detail

Office name Device type Capacity

Complainer Contact telephone

Version

Date and time Responding date and time required

Whether it has passed the warranty period

□Yes □No

Description of the fault(s) and handling processes (in detail) Auditor; Stamp (your department):

The following contents are to be filled by Huawei

Handling method O by telephone O by remote maintenance O by on-site support

Results (additional pages can be attached) Operator: Date:

Outstanding issues



4-3

4.2 Troubleshooting Record Table Name of the softswitch office: Date of Maintenance:

Time of occurrence: Time of solution:

Person on duty: Operator:

Fault type: Hardware fault Power fault Clock fault FE/E1 interface fault Bearer network fault Transmission network fault Communication fault between host and BAM Media gateway fault MRS fault Subscriber terminal fault Console fault Subscriber cable fault MTP link fault SIGTRAN link fault PRA link fault V5 interface fault Trunk circuit fault Charging fault Other faults

Fault source: User complaint Alarm system Found during routine maintenance Other sources

Description of Fault:

Handling method and result

Emergency Maintenance Manual U-SYS SoftX3000 SoftSwitch System Appendix A Acronyms and Abbreviations


A-1

Appendix A Acronyms and Abbreviations

Abbreviations Description

A

AMG Access Media Gateway

AN Access Network

B

BAM Back Administration Module

BFII Back insert FE Interface Unit

BITS Building Integrated Timing Supply

BSGI Broadband Signaling Gateway

C

CDBI Central Database Board

CDR Call Detail Record

Centrex Central Office Exchange Service

CIC Circuit Identification Code

CKII Clock Interface Unit

CPC Central Processing Board

D

DDI Direct-Dialing-In

DPC Destination Point Code

DSS1 Digital Subscriber Signaling No.1

DTMF Dual-Tone Multifrequency

E

EC Echo Canceller

EPII E1_Pool Interface Unit

F

FCCU Fixed Calling Control Unit

FCSU Fixed Calling Control Unit and Signaling process Unit

FE Fast Ethernet

FSK Frequency Shift Keying

G



A-2


GK Gatekeeper

GW GateWay

I

IAD Integrated Access Device

IFMI IP Forward Module

iGWB iGateWay Bill

IN Intelligent Network

INAP Intelligent Network Application Protocol

iOSS integrated Operation Support System

IP Internet Protocol

IPN Internet Personal Number

ISDN Integrated Services Digital Network

ISUP ISDN User Part

ITU-T International Telecommunication Union - Telecommunication Standardization Sector

IUA ISDN Q.921-User Adaptation Layer

M

M2UA Message Transfer Part 2 (MTP2) -User Adaptation Layer

M3UA Message Transfer Part 3 (MTP3) -User Adaptation Layer

MCU Multipoint Control Unit

MG Media Gateway

MGC Media Gateway Controller

MGCP Media Gateway Control Protocol

MML Man Machine Language

MRCA Media Resource Control Unit

MRIA Media Resource Interface Unit

MRS Media Resource Server

MSGI Multimedia Signaling Gateway Unit

MTA Media Terminal Adapter

MTP Message Transfer Part

N

NAT Network Address Translation

NCS Network-Based Call Signaling



A-3


NGN Next Generation Network

NMS Network Management System

NP Number Portability

O

OAM Operation Administration and Maintenance

P

PBX Private Branch Exchange

PDB Power Distribution Box

POTS Plain Old Telephone Service

PSTN Public Switched Telephone Network

R

RAS Registration, Admission and Status

S

SAU Signaling Access Unit

SCN Switched Circuit Network

SCP Service Control Point

SCTP Stream Control Transmission Protocol

SG Signaling Gateway

SIGTRAN Signaling Transport

SIP Session Initiation Protocol

SIUI System Interface Unit

SoftSwitch Software switch

SP Signaling Point

SSP Service Switching Point

STP Signaling Transfer Point

T

TDM Time Division Multiplex(ing)

TMG Trunk Media Gateway

U

UMG Universal Media Gateway

U-NICA Universal Network Intelligent Core Architecture

U-Path —

U-SYS You Design Your System



A-4


V

V5UA V5.2-User Adaptation Layer

VoIP Voice Over IP

A

Emergency Maintenance Manual U-SYS SoftX3000 SoftSwitch System Index


i-1

Index

C check cause of breakdown

handle host device breakdown, 2-10

handle iGWB breakdown, 2-24

handle service module breakdown, 2-14

check cause of congestion

handle global service congestion, 2-28

handle partial service congestion, 2-32, 2-33

check power supply

handle BAM breakdown, 2-21

collect fault information

brief report of fault, 2-4

collect alarm logs, 2-5

collect command logs, 2-5

collect debug log of BAM, 2-5

collect debug log of iGWB, 2-6

collect debug logs, 2-5

D device fault

BAM breakdown, 1-2

host breakdown, 1-1

iGWB breakdown, 1-3

MRS6000 breakdown, 1-2

service frame breakdown, 1-1

service module breakdown, 1-2

E emergency fault, 1-1

emergency maintenance, 1-1

F flow chart

handle BAM breakdown, 2-20

handle frame breakdown, 2-11

handle global service congestion, 2-25

handle host device breakdown, 2-6

handle iGWB breakdown, 2-22

handle MRS service congestion, 2-35

handle MRS6000 breakdown, 2-15

handle partial service congestion, 2-30

handle service module breakdown, 2-13

handling emergent fault, 2-1

H handle BAM breakdown

check power supply of BAM, 2-21

collect fault information, 2-22

flow chart, 2-20

reserve fault, 2-22

restart BAM, 2-22

start emergency workstation, 2-22

handle emergent fault

check bearer network, 2-3

check hardware device, 2-2

collect fault information, 2-2, 2-4

handle bearer network fault, 2-4

handle service fault, 2-4

judge whether problem is solved, 2-4

report for technical support, 2-4

handle frame breakdown

check power supply of frame, 2-12

check SMUIs, 2-12


flow chart, 2-11

replace SMUIs, 2-13

reset SMUIs, 2-13

handle global service congestion

back up BAM database data, 2-27

back up service data, 2-27


check cause of congestion, 2-28

check CDBIs in basic frames, 2-29

check host device, 2-27



i-2

check IFMIs in basic frames, 2-28


fetch bills immediately, 2-28

flow chart, 2-25

recover configuration data, 2-28

reset CDBIs, 2-29

reset IFMIs, 2-29

switch over CDBIs, 2-29

switch over IFMIs, 2-29

handle host device breakdown

check cause of breakdown, 2-10

check IFMIs in basic frame, 2-10

check power supply of basic frame, 2-8

check power supply of cabinet, 2-8

check SMUIs in basic frame, 2-8, 2-9


flow chart, 2-6


repair power supply system, 2-8

replace CDBIs in basic frame, 2-10

replace IFMIs in basic frame, 2-10

replace SMUIs in basic frame, 2-9

re-power on, 2-8

reset CDBIs in basic frame, 2-10

reset IFMIs in basic frame, 2-10

reset SMUIs in basic frame, 2-9

handle iGWB breakdown

check both iGWBs, 2-23


check configuration file of standby iGWB, 2-24


flow chart, 2-22


restart standby iGWB, 2-24

handle MRS service congestion

check communication between MRS6000 and

bearer network, 2-37

check MRS6000, 2-37

flow chart, 2-35

handle MRS6000 breakdown


check MPCs, 2-18

check power supply of MRS6000, 2-18

check SCCs, 2-18


flow chart, 2-15

power on MRS6000, 2-19


replace SCCs, 2-18

reset SCCs, 2-18

restart MRS6000, 2-19

handle partial service congestion

back up BAM database, 2-33

back up service data, 2-33


check bill pool of related FCCUs/FCSUs, 2-34

check cause of congestion, 2-32, 2-33

check related FCCUs/FCSUs, 2-34

check related service module, 2-32


fetch bills immediately, 2-33

flow chart, 2-30


switch over FCCUs/FCSUs, 2-34

handle service module breakdown



flow chart, 2-13


replace boards, 2-15

reset boards, 2-15

handling emergent fault

flow chart, 2-1

M maintenance operation

power-on operation, 3-1

recover BAM, 3-32

reset operation, 3-6

restore BAM database, 3-11

scan virus, BAM, 3-38

switch over BAM, 3-32



i-3

S service fault

AMG service congestion, 1-4

global service congestion, 1-3

MRS service congestion, 1-4

partial service congestion, 1-3

TMG service congestion, 1-4

UMG service congestion, 1-4

i.

1.1 basic concepts 1-1 - read.pudn.comread.pudn.com/downloads181/ebook/846323/softx3000/softx3000...

Documents