sjzl20083605-ZXC10 BSSB (V8.0.2.002) Emergency Maintenance Manual

ZXC10 BSSB
CDMA2000 Base Station System

Emergency Maintenance Manual
Version 8.0.2.002
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
Copyright © 2006 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-
RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason

R1.0 10/30/2008 First Edition
Serial Number: sjzl20083605

Contents
Preface............................................................... i
Emergency Maintenance Overview ....................1
What is Emergency Maintenance....................................... 1
Emergency Failure Definition ............................................ 1
Emergency Maintenance Principle ..................................... 2
Emergency Maintenance Flow ...........................3
Emergency Maintenance Flow Chart .................................. 3
Service Inspection .......................................................... 5
Fault Location ................................................................ 5
Problem Analysis ............................................................ 5
Ask For Support ............................................................. 5
Restore the Service......................................................... 5
Observe the Service........................................................ 6
Feedback....................................................................... 6
Communicate with Customers .......................................... 6
Failure Analysis Principle ..................................7
Basic Analysis Principles .................................................. 7
Confirming whether BSSB Global Fault .............................. 7
Confirming whether the Problem is a Global BSSB
Problem ................................................................ 8
Voice and 1X Data Service ........................................... 8
EV-DO and 1X Data Service ......................................... 8
Confirming whether Caused by Data Modification ................ 9
Confirming other Reason ................................................. 9
Outer Interference ...................................................... 9
Power Supply Fault ..................................................... 9
BSS Emergency Maintenance........................... 11
BSS Emergency Maintenance Principle..............................11
A Interface Failure Recovery............................................11
Ap Interface Failure Recovery ..........................................13
V5 Interface Failure Recovery..........................................14
OMP Board Malfunction...................................................15
MP Board Malfunction.....................................................16
BPSN Failure .................................................................18
Broken Abis interface .....................................................19
OMC Suspension Emergency Maintenance........ 21
OMC Emergency Maintenance Principle .............................21
Processing Procedures....................................................21
Check the Communication between OMC Server and
OMP ....................................................................22
Check Hard Disk Space on OMC Server.............................22
Check Virus and Operating System Status.........................22
Check Database ............................................................22
Restart Server...............................................................23
Failure Information Feedback ......................... 25
Failure Feedback Factors.................................................25
Fault Feedback Table ......................................................25
Figures ............................................................ 27
Tables ............................................................. 29
Preface
Purpose This manual describes the ZXC10 BSSB Emergency maintenance

check and methods. It provides the maintenance personnel with
detailed information to discover and resolve faults and potential
troubles.
Intended This document is intended for engineers and technicians who per-
Audience form operation activities on the ZXC10 BSSB CDMA2000 Base Sta-
tion System.
Prerequisite Skill To use this document effectively, users should have a general un-
and Knowledge derstanding of wireless telecommunications technology. Familiar-
ity with the following is helpful:
� ZXC10 BSSB CDMA2000 Base Station System and its various
components
� Local operating procedures
What is in This This Manual contains the following chapters:
Manual
Chapter Summary
Chapter 1 Describes Emergency maintenance overview,
Emergency emergency failure definition and maintenance principle
Maintenance
Overview
Chapter 2 Describes Emergency maintenance flow details
Emergency
Maintenance
Flow
Chapter Describes basic analysis principle and BSS problem
3 Failure
Analysis
Principle
Chapter Describes BSS emergency maintenance overview,
4 BSS interface failure recovery, board malfunction trouble
Emergency shooting and rack failure recovery.
Maintenance
Chapter Describes OMC suspension emergency maintenance
5 OMC
Suspension
Emergency
Maintenance
Appendix Describes Failure feedback factors
A Failure
Information
Feedback
Confidential and Proprietary Information of ZTE CORPORATION i

ZXC10 BSSB Emergency Maintenance Manual
This page is intentionally blank.
ii Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
Emergency Maintenance
Overview
Table of Contents:
What is Emergency Maintenance .......................................... 1
Emergency Failure Definition ................................................ 1
Emergency Maintenance Principle ......................................... 2
What is Emergency
Maintenance
Emergency maintenance is a kind of unpredictable maintenance.
It means the immediate troubleshooting for the failed equipments
when there is an emergency.
Emergency Failure Definition

Emergency failure means the equipment damage or network dam-
age. This occurs unpredictably and has serious impact on the net-
work security and service quality.
According to the effect scope, the failures as below are defined as
emergency failures:
1. The whole system is down.
2. Lose any ability of security or emergency call (such as, 110 or
911 call).
3. The failure has a significant threat against other devices or
personal safety
Confidential and Proprietary Information of ZTE CORPORATION 1

Principle
The key target of emergency maintenance is to restore the service
as soon as possible. Network operator should refer to this guide
to prepare the emergency failure handling regulation and provide
trainings for staff.
When there is an emergency failure, make sure that BSS hardware
and transmission are in good condition. Determine whether the
failure is caused by BSS; if so, perform troubleshooting according
to this guide. In addition, contact the ZTE customer support center
for advanced technical support.
Collect the alarm information and hard copies of the failure. Send
the related failure handling report and event logs to ZTE for anal-
ysis.
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2
Flow
Table of Contents:
Emergency Maintenance Flow Chart ...................................... 3
Service Inspection .............................................................. 5
Fault Location .................................................................... 5
Problem Analysis ................................................................ 5
Ask For Support ................................................................. 5
Restore the Service ............................................................ 5
Observe the Service............................................................ 6
Feedback........................................................................... 6
Communicate with Customers .............................................. 6
Flow Chart
Emergency maintenance includes:
1. Service Inspection
2. Fault Location
3. Problem Analysis
4. Ask For Support
5. Restore the Service
6. Observe the Service
7. Feedback
8. Communicate with Customers
Figure 1 shows the emergency maintenance flow.

FIGURE 1 EMERGENCY MAINTENANCE FLOW CHART

Chapter 2 Emergency Maintenance Flow
Service Inspection
Collect user complaints, and observe BSS alarm information and
dynamic data management to make sure there is an emergency.
Fault Location
Collect the performance data and analyze the facade phenomena
of CDMA network fault. Observe device running status and board’s
LED. Ensure whether the problem is from BSS or not.
Problem Analysis
If it is confirmed that the problem is caused by BSS, analyze the
onsite data, signaling and logs (hard copy) for problem locating.
Ask For Support

Ask for support from ZTE customer support center. The center
provides 24×7 hotline service and remote technical support.
1. ZTE customer support center hotline
8008301118 (0755) 26770800
2. Remote Support
According to information provide by service hotline, technical
experts log onto a faulty office in a remote mode and guide
clients to solve the faulty. If the faulty is complicated, di-
rectly arrange technical support engineers for troubleshooting
on site.
3. Onsite technical support
Upon the arrival, the technicians will take emergency measures
to try to restore the service as soon as possible.
Restore the Service

Locate the problem and restore the service with remote support
or onsite support from ZTE. If the problem is still unresolved, try
active/standby changeover, reset or reboot.

Observe the Service

It must be confirmed that the system runs well after restoring.
Watch the system during peak hours. If the problem reoccurs,
resolve it immediately.
Feedback
After restoring the service, send the BSS network statistic reports,
running logs and signaling tracking information to ZTE CDMA De-
partment for analysis.
Communicate with
Customers
According to the onsite information, the customer service team of
ZTE CDMA Department will submit a failure analysis report to the
local ZTE office. The local office shall discuss it with customers
about the failure.

Chapter 3
Failure Analysis
Principle
Table of Contents:
Basic Analysis Principles ...................................................... 7
Confirming whether BSSB Global Fault .................................. 7
Confirming whether the Problem is a Global BSSB Problem ........ 8
Confirming whether Caused by Data Modification .................... 9
Confirming other Reason ..................................................... 9
Basic Analysis Principles

Once the emergency failure occurs, it is necessary to determine
the failure cause immediately. Firstly, locate the problematic net-
work element in order to save time.
Confirming whether BSSB

Global Fault
Before handling the problem, confirm whether the problem is a
global BSSB problem and whether all services are suspended. If
it is not a global problem, then try to analyze what is its impact
scope. These analyses facilitate the emergency handling.
In following cases, it is a global BSSB problem. Otherwise it is a
single BTS site problem.
� Case 1: A interface is broken for more than 1 minute.
If the diagnosis shows that the NO.7 links are all suspended,
the A interface is considered broken.
� Case 2: Call observation shows that all calls fail.
The calls are all failed.
� Case 3:The active and standby boards of important modules
are faulty at the same time.
These modules are: OMP, RMP and the CMP and DSMP with
only one module.

� Case 4: A/Ap interface interruption over 10 minutes

Check the status of Ap link. If the link is interrupted over 10
minutes, judge the whole office faulty.
� Case 5: V5 interface interruption over 3 minutes
Check the status of V5 link. If all V5 links are interrupted over
3 minutes, judge the whole office faulty.
If there are a lot of call failures, check whether the call failures are
caused by the same problem and whether these failures occur in
a certain base station.
Confirming whether the

Problem is a Global BSSB
Problem
Voice and 1X Data Service
When there are a lot of call failures, check the A interface state in
alarm management and diagnosis.
� A interface link is normal
If A interface link is normal, the call failure observation shows
that the failure cause is T303 expires or SCCP disconnect and
MSC initiate release without reasons. It can be confirmed that
the problem is at switch side. Inform the persons at switch
side and provide them with support to deal with the problem.
The problem may be inside the BSS if the failure is caused by
other reasons.
� A interface link is not normal
If A interface link is suspended, it is unable to locate the faulty
network element. Find it at BSC side, switch side, and trans-
mission side at the same time.
EV-DO and 1X Data Service

When there are a lot of call failures, Check R-P status by alarm
management.
� R-P interface is normal
If signaling tracking shows that the data service does not reach
PDSS, it is considered that the problem occurs at PDSS side.
If signaling tracking shows that the data service does not reach
R-P, it is considered that the problem occurs at PDSS side.

Chapter 3 Failure Analysis Principle
� R-P interface is not normal

If R-P interface is broken, it is unable to locate the faulty net-
work element. Find it at BSC side and PDSS side at the same
time.
Confirming whether Caused

by Data Modification
It must be confirmed that whether the system data was modified
before failure occurs.
If data modification causes failure, immediately restore the previ-
ous system configuration.
Confirming other Reason

Outer Interference
Outer interference may cause a phenomenon of call difficulty in a
great range. Please query whether the RSSI value of faulty BSS
is normal and judge whether the interference resource from a re-
peater.
Power Supply Fault

When there is a power supply failure, focus on the power supplies
recover status. Once the power supply works normally, adjust the
system all at once and recover the service.


Chapter 4
BSS Emergency
Maintenance
Table of Contents:
BSS Emergency Maintenance Principle..................................11
A Interface Failure Recovery ...............................................11
Ap Interface Failure Recovery..............................................13
V5 Interface Failure Recovery..............................................14
OMP Board Malfunction.......................................................15
MP Board Malfunction.........................................................16
BPSN Failure .....................................................................18
Broken Abis interface .........................................................19
BSS Emergency
Maintenance Principle
When there is an emergency at BSS side, Contact the local ZTE
after-sales center to request onsite technical support.
A Interface Failure Recovery

If system generates a global NO.7 link failure alarm, MSC signaling
and BSC signaling are unreachable. The service is suspended. The
NO.7 link diagnosis shows that all NO.7 links are out of service for
more than 5 minutes. Take the following actions:
� If E1/T1 of A interface with signaling link has alarms, and the
corresponding E1/T1 indicators are solid ON, it can be con-
firmed that there is something wrong with A interface connec-
tion. Find out the connections with A interface. The switch side
should make it clear whether the A interface link is broken due
to the cause at switch side. Keep finding if there is no excep-
tion of A interface link.
� View the SPB board from OMC to see if there is an exception
alarm. The alarms caused by broken NO.7 link shows that the
NO.7 link is broken.

Check the SPB indicators at NE. If the SPB board is normal and
NO.7 link is broken, reset SPB board immediately.
Table 1 shows SPB board’s indicators description.
TABLE 1 SPB BOARD INDICATORS DESCRIPTION
N
Color Meaning Description
ame
Flash at 5 Hz: Power ON the board.
Flash at 1 Hz: Board runs normally.
RUN Green Running LED
Off: Indicates board is in OFF
state.
On: Alarm occurs to the board.
ALM Red Alarm LED
Off: No alarm.
On: Power ON the board.
E Unplugging Off: Board starts working.
Yellow
NUM LED
(If ENUM LED is off, do not pull out
the board effectively.)
Active/Sta On: Board is active.
ACT Green ndby state
LED Off: Board is standby.
� If there is no alarm in SPB board, check whether OMP board

has alarms. The OMP alarms caused by broken NO.7 link of A
interface are “SSN is unavailable" Check OMP indicators at NE.
The indicators description is shown in Table 2.
If OMP board is not normal, perform active/standby
changeover. Afterwards, observe NO. 7.
TABLE 2 OMP BOARD INDICATORS DESCRIPTION
LED Color Name Description
Alarm LED of CPU On: Alarm occurs.

ALM1 Red
subsystem B Off: No alarm.
Flash at 5 Hz: Power ON the
board.
Running LED of Flash at 1 Hz: Board runs
RUN1 Green
CPU subsystem B normally.
Off: Board is not work
normally.
Active/Standby On: Board is active.
ACT1 Green state LED of CPU
subsystem B Off: Board is standby.

Off: Board starts working.
E Y Unplugging LED of
NUM1 ellow CPU subsystem B (If ENUM LED is off, do
not pull out the board
effectively.)

Chapter 4 BSS Emergency Maintenance

ALM2 Red
subsystem A Off: No alarm.
board.
RUN2 Green
CPU subsystem A normally.
Off: Board is not work
normally.
subsystem A Off: Board is standby.

Off: Board starts working.
E Y Unplugging LED of
NUM2 ellow CPU subsystem A (If ENUM LED is off, do
not pull out the board
effectively.)
O Reser - (on the panel of -
MC1 ved OMP board)
OMC network port Flash: Connect OMC network
state LED of CPU port.
O
Green subsystem A (on
MC2 Off: Disconnect OMC
the panel of the
OMP board) network port.
Reser - (on the panel of -

HD1
ved OMP board)
Hard disk state LED Flash: Read/Write the hard
of CPU subsystem disk.
HD2 Red
A (on the panel of
OMP board) Off: Hard disk is idle.
If the problem persists contact ZTE customer support department.
Ap Interface Failure
Recovery
The Ap interface failure mainly occurs while in the initial stage
of network commissioning or cut-over of version upgrading. Ap
interface failure causes are as described below.
1. The voice or short message service is not available.
2. Dynamic Management shows that the Ap interface association
is disabled, faulty or unknown.
3. An association disconnection alarm is reported to OMP.
4. The Ap service state is abnormal. You can telnet to ApCMP
using ShowCallState to view the state.
5. Pinging IP addresses of SIPI and IPI on the MSCe may fails.

Firstly make sure that the versions of ApCMP, SIPI, IPI and UIMC
are correct. Then perform the following steps.
1. Ping the IP addresses of SIPI and IPI on the MSCe to check
whether the physical link is normal.
� If the physical link is broken, check network cable connec-
tion and running status of the router to ensure the network
between the BSC and MSCe is good.
� If the physical link is OK, check IP address, port and routing
configurations of SIPI and IPI.
2. Check the association configuration of Ap interface, and make
sure that is consistent with MSCe side configuration.
3. Check whether the MGW and BSC are consistent in A interface
version.
4. View R_OFFICE in the OMP and ApCMP through the probe.
Make sure that MSStatus is set to 0, and the communication
in office direction is normal.
5. View R_N7SSN in the OMP and ApCMP to check whether all
SSN data are set to 0. If no, check whether the SIGTRAN data
configured in the BSC and the data of SSN-AS Configuration are
complete. Or view R_ASACTASP in the OMP to check whether
the status parameter is set to 3.
6. If the failure remains, reset the SIPI.
7. If the failure still remains, save the interface start signaling
and send it to ZTE Corporation for troubleshooting.
V5 Interface Failure
Recovery
The interruption phenomena of V5 link are described as follows:
1. Dynamic Data Management shows that the V5 interface is
faulty, or sometimes shows disconnected.
2. In the dynamic data management, the status of V5 interface
shows “Faulty”.
3. The status of V5 interface is intermitted and the link of V5
interface is unblocked.
4. In the alarm management interface, an alarm of V5 interface
disconnection occurs in the board V5CMP belongs to.
When the V5 interface is faulty, perform the following operations
for troubleshooting:
1. Ensure that the V5 interface physical link is not broken. Check
whether the IN and OUT ends of each E1 cable are not crossed,
and the primary and secondary links are correctly connected.
2. Check the V5 interface parameters including V5 ID, V5 assign-
ment variable, V5 link ID, type of the protection group of V5
physical C path (ZTE V5 interface supports protection group

1 only) and ID of V5 logical C path. Make sure that they are

consistent with those in the switch.
3. Check whether multi-frame CRC is used for V5 interface E1
frame check. If no, change it into multi-frame CRC.
4. Check whether the V5CMP, V5SPB and E1 interface board run
normally. If no, check whether the version of the faulty board
is correct. If yes, restart the V5 interface and reset the faulty
board.
5. If the failure remains, contact the switch maintenance person-
nel to check whether the switch is faulty.
6. If the failure still cannot be located, save the layer 3 and layer
2 signaling of V5 interface start and send it back to ZTE Cor-
poration for troubleshooting.
7. When the failure is removed, Dynamic Data Management will
show that the V5 interface is in a normal state and V5 link check
will succeed. If two physical C paths are equipped, perform
a protective handoff test on the V5 logical C path to check
whether the V5 interface recovers.
OMP Board Malfunction

OMP has active/standby configuration. Only when the two boards
fail at the same time, it is likely that global call failure occurs.
Observe OMP board LED indicators. If RMP or the MP type with
only one module is failed, check the OMC alarms and NE indicators.
The indicators description is shown in Table 3.
TABLE 3 OMP BOARD INDICATORS DESCRIPTION

ALM1 Red
board.
RUN1 Green
Off: Board is not working
normally.

Unplugging LED
E Off: Board starts working.
Yellow of CPU subsystem
NUM1
B (If ENUM LED is off, do not pull
out the board effectively.)

ALM2 Red


board.
RUN2 Green
normally.

Unplugging LED
E Off: Board starts working.
Yellow of CPU subsystem
NUM2
A (If ENUM LED is off, do not pull
Reser
OMC1
ved
Reser
OMC2
ved
Reser -
HD1
ved
Reser
HD2
ved
If LEDs of both MP boards indicate that the boards do not work

normally at the same time, plug out one of them and synchronize
the data to NE device. Observe running OMP’s work status.
If the problem remains, plug out the current OMP boards, then
plug in again, and synchronize the data to NE device. Observe
running OMP’s work status.
If the problem remains, ask for support from ZTE custom engi-
neers.
MP Board Malfunction
According to service types, MP board is divided into RMP, CMP,
DSMP, and HMP. RMP, CMP, DSMP are used for 1x Release A service
while HMP is used for EV-DO service.
In general, RMP is active/standby configured. Each BSC is
equipped with a module.
If the module equipped with many MP types fails, it won’t affect
the global service of BSS.
If RMP or the MP type with only one module is failed, check the
OMC alarms and NE indicators. The indicators description is shown
in Table 4.

TABLE 4 MP BOARD INDICATORS DESCRIPTION

ALM1 Red
board.
RUN1 Green
normally.

E Unplugging LED of Off: Board starts working.
Yellow
NUM1 CPU subsystem B
(If ENUM LED is off, do not pull

ALM2 Red
board.
RUN2 Green
normally.

E Unplugging LED of Off: Board starts working.
Yellow
NUM2 CPU subsystem A
(If ENUM LED is off, do not pull
Reser
OMC1
ved
Reser
OMC2
ved
Reser -
HD1
ved
Reser
HD2
ved
If the active/standby changeover is not performed on the failed

MP module, the global service will be affected. Perform ac-
tive/standby changeover manually in NE device. After completing
active/standby changeover, observe the active module and make
sure the service works normally.

If the problem still exits, pull out the standby board, and reset the
active board manually. If the module runs normally, observe the
service status.
If the problem remains, ask for support from ZTE customer sup-
port engineers.
BPSN Failure
If BPSN or one of its board fails, and changeover are not per-
formed, the global voice and data service will be affected.
If there are multi BUSNs, make sure that media stream works
normally in BUSN by diagnosis testing media stream. If media
stream between BUSN do not work normally, then maybe the prob-
lem is from BPSN. At first, record the connection relations between
BUSNs and CLI board in BPSN, then look for the cause of the prob-
lem by following steps.
� Check whether panel indicators on every GLI board flash nor-
mally.Table 5 shows the GLI board indicators Description
TABLE 5 GLI BOARD INDICATORS DESCRIPTION
LED Color Meaning Description

Name
RUN Green Running Flash at 5 Hz: Power ON the board
LED Flash at 1 Hz: Board runs normally.
Solid on: Version is downloaded
successfully and is starting up.
Off: Board is abnormal.
ALM Red Alarm On: Alarm occurs.
LED Off: No alarm.
ENUM Yellow Unplugg Solid on:Board is not inserted in
ing LED proper and do not download a
version.
Flash at 5 Hz: While the board is
running, the wrench is open and the
board has alarm.
Flash at 1 Hz: While the board is
running, the wrench is open. The
board can be extracted.
Off: Board is abnormal.
ACT Green Active/ On: Board is active.
Standby Off: Board is standby.
state LED
ACT1 Green Optical Solid on: Logic not works normally.
~ interface Flash: Transfer/receive the data.
ACT8 activation
LED
SD1 ~ Green Optical On: Optical port receives optical
SD8 signal signals.
LED Off: Optical port not receives any
optical signal.

Normally, the ACT indicators of transponder, selected by rout-

ing, blink quickly (3-5Hz). All SD indicators of transponder with
optical fibers are solid ON. If there is any indicator exception,
reinsert the optical fibers.
� If the problem remains, perform changeover on the GLI board.
� If the problem remains, perform changeover on the PSN board.
� If the problem remains, perform changeover on the UIMC
board in BPSN.
If the problem still exits, contact ZTE after-sales engineers imme-
diately for support.
Broken Abis interface

Some base stations do not provide services anymore because of
Abis interface. This problem can not be detected by both active
and standby CCM of BTS.
Once the Abis interface is broken, find out the problem. Firstly,
make sure that the problem is not caused by transmission. Record
the number of broken base stations as well as the connection re-
lationships with ABPM board.
If there is no problem with transmission, and the broken base
stations belong to one ABPM board, perform active/standby
changeover at once.
After changeover, if the problem still exits, contact ZTE after-sales
engineers immediately for support.


Chapter 5
OMC Suspension
Table of Contents:
OMC Emergency Maintenance Principle .................................21
Processing Procedures........................................................21
Check the Communication between OMC Server and OMP .........22
Check Hard Disk Space on OMC Server.................................22
Check Virus and Operating System Status.............................22
Check Database ................................................................22
Restart Server...................................................................23
OMC Emergency
Maintenance Principle
System does not get affected even OMC service fails. So that han-
dle it calmly.
OMC failure may occurs due to the of the following reasons:
� Broken link between OMC server and NE OMP.
� OMC server can not run normally.
� OMC server can not provide operation service (i.e. viewing
alarm information).
If the problem still exits, contact ZTE after-sales engineers or sup-
port.
Processing Procedures
The processing procedures of emergency maintenance for OMC
service suspension are as below:
1. 1. Check the communication between server and OMP.
2. 2. Make sure hard disk has free space.
3. 3. Make sure the server is not infected by virus and the oper-
ating system runs normally.

4. 4. Make sure the database OMC runs normally.

5. 5. Reboot the server.
Check the Communication

between OMC Server and
OMP
1. PING NE OMP to see whether the communication is normal
2. If PING fails, check the connection between OMC server and
OMP
3. Check OMP network cable connectors and the connections.
Check Hard Disk Space on

OMC Server
1. Make sure that the system disk and other disks where server
software and data software locate have enough storage room.
2. If there is no enough storage room, delete some documents
and vacate risk room.
Check Virus and Operating

System Status
1. Use the latest virus library to scan and kill virus
2. Reinstall operating system and OMC server applications, if the
operating system has problem.
Check Database
1. Make sure the database is started.
2. Make sure the database can be connected successfully.
3. If the database is in normal state, restart OMC server.
4. If the database is faulty, stop it.

Chapter 5 OMC Suspension Emergency Maintenance
5. Restart database.
6. Restart OMC.
Restart Server
If the operations above can not resolve the problem, restart the
server.
1. Close the OMC client and server process and restart the server.
2. Start the database.
3. Start OMC server and client process.


Appendix A
Failure Information
Feedback
Table of Contents:
Failure Feedback Factors........................................................... 25
Fault Feedback Table ................................................................ 25
Failure Feedback Factors

1. Occurrence
Record when the failure occurs.
2. Symptom
� Describe the board state, dynamic state, OMC alarms, sig-
naling and call state. These states are the basis of on-site
troubleshooting incidence.
� Describe the effect scope, for example, the whole BSC or
a single site.
� If the symptom is not clear, capture the screen. For exam-
ple, the information can not be saved such as the channel
state shown in dynamic.
3. Troubleshooting steps
� Onsite troubleshooting steps and checkpoints.
� Wrong operations.
� It is suggested to form a habit of creating server operation
logs for convenient viewing.
4. System logs
System logs contain the information about system running
state and system problems. They are mainly used in finding
the system problem.
Fault Feedback Table

The onsite fault feedback table is as shown in Table 6.

TABLE 6 ONSITE FAULT FEEDBACK TABLE
Feedback Feedb Recei

Personnel ack Date ver
Contact Tel E-mail
Corporation Model
Network Capa
city Version
Fault occur
rence time,
phenomenon
and descript
ion
Operation
and handl
ing procedure
description on
site
Onsite data
feedback
Analysis and Handling

handling opin Supervi D
ion sor ate
Final handling
opinion and
conclusion

Figures
Figure 1 Emergency Maintenance Flow Chart.......................... 4


Tables
Table 1 SPB Board Indicators Description ..............................12

Table 2 OMP Board Indicators Description .............................12
Table 3 OMP Board Indicators Description .............................15
Table 4 MP Board Indicators Description ...............................17
Table 5 GLI board indicators Description ...............................18
Table 6 Onsite Fault Feedback Table .....................................26

sjzl20083605-ZXC10 BSSB (V8.0.2.002) Emergency Maintenance Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

sjzl20083605-ZXC10 BSSB (V8.0.2.002) Emergency Maintenance Manual

Uploaded by

Copyright:

Available Formats

ZXC10 BSSB

CDMA2000 Base Station System

Copyright © 2006 ZTE CORPORATION.

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

Revision No. Revision Date Revision Reason

Serial Number: sjzl20083605

Purpose This manual describes the ZXC10 BSSB Emergency maintenance

Confidential and Proprietary Information of ZTE CORPORATION i

This page is intentionally blank.

ii Confidential and Proprietary Information of ZTE CORPORATION

Emergency Failure Definition

Confidential and Proprietary Information of ZTE CORPORATION 1

2 Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 3

FIGURE 1 EMERGENCY MAINTENANCE FLOW CHART

4 Confidential and Proprietary Information of ZTE CORPORATION

Ask For Support

Restore the Service

Confidential and Proprietary Information of ZTE CORPORATION 5

Observe the Service

6 Confidential and Proprietary Information of ZTE CORPORATION

Basic Analysis Principles

Confirming whether BSSB

Confidential and Proprietary Information of ZTE CORPORATION 7

� Case 4: A/Ap interface interruption over 10 minutes

Confirming whether the

EV-DO and 1X Data Service

8 Confidential and Proprietary Information of ZTE CORPORATION

� R-P interface is not normal

Confirming whether Caused

Confirming other Reason

Power Supply Fault

Confidential and Proprietary Information of ZTE CORPORATION 9

This page is intentionally blank.

10 Confidential and Proprietary Information of ZTE CORPORATION

A Interface Failure Recovery

Confidential and Proprietary Information of ZTE CORPORATION 11

TABLE 1 SPB BOARD INDICATORS DESCRIPTION

� If there is no alarm in SPB board, check whether OMP board

TABLE 2 OMP BOARD INDICATORS DESCRIPTION

LED Color Name Description

Alarm LED of CPU On: Alarm occurs.

On: Power ON the board.

12 Confidential and Proprietary Information of ZTE CORPORATION

LED Color Name Description

Alarm LED of CPU On: Alarm occurs.

On: Power ON the board.

Reser - (on the panel of -

If the problem persists contact ZTE customer support department.

Confidential and Proprietary Information of ZTE CORPORATION 13

14 Confidential and Proprietary Information of ZTE CORPORATION

1 only) and ID of V5 logical C path. Make sure that they are

OMP Board Malfunction

TABLE 3 OMP BOARD INDICATORS DESCRIPTION

LED Color Name Description

Alarm LED of CPU On: Alarm occurs.

On: Power ON the board.

Alarm LED of CPU On: Alarm occurs.

Confidential and Proprietary Information of ZTE CORPORATION 15

LED Color Name Description

On: Power ON the board.

If LEDs of both MP boards indicate that the boards do not work

16 Confidential and Proprietary Information of ZTE CORPORATION