Professional Documents
Culture Documents
Version 6.20
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
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
Revision History
Document
ZXG10 BSS (V6.20) Base Station Subsystem Alarm Handling Manual
Name
Document Revision
Product Version V6.20 R1.0
Number
Equipment
Serial No. sjzl20083213
Installation Date
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good Fair Average Poor Bad N/A
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction Make it more concise/brief
Improve the Contents Add more step-by-step procedures/tutorials
Improve the organization Add more troubleshooting information
Include more figures Make it less technical
Your Add more examples Add more/better quick reference aids
suggestions for Add more detail Improve the index
improvement of
this Other suggestions
documentation __________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail
This page is intentionally blank.
Contents
Chapter 1 .........................................................................1
Chapter 2 .........................................................................5
Appendix A ..................................................................251
Abbreviations ..............................................................251
Tables ..........................................................................259
Index ...........................................................................261
This page is intentionally blank.
About This Manual
Purpose
This manual describes BSS (V6.20) related alarm messages in
terms of alarm cause, influence, and handling suggestions. You
can analyze, locate, and handle faults by referring to this
document.
Intended Audience
This manual is intended for engineers and technicians who
perform operation activities on the ZXG BSS.
Chapter Summary
Chapter 1, Alarm Introduces the basic concepts of BSS
Messages (V6.20) alarms, including alarm definition,
severity, handling suggestions, and
classification
Chapter 2, Alarm Describes the BSS (V6.20) alarms in terms
Message Description of alarm cause, influence on the system,
Chapter Summary
and handing flow.
Related Documentation
The following documentation is related to this manual:
ZXG10 iBSC (V6.20) Base Station Controller Documentation
Guide
ZXG10 iBSC (V6.20) Base Station Controller Technical
Manual
ZXG10 iBSC (V6.20) Base Station Controller Hardware
Manual
ZXG10 iBSC (V6.20) Base Station Controller Installation
Manual
ZXG10 iBSC (V6.20) Base Station Controller Performance
Counters Manual – Volume I
ZXG10 iBSC (V6.20) Base Station Controller KPI Reference
Manual
ZXG10 iBSC (V6.20) Base Station Controller Maintenance
Manual (Routine Maintenance)
ZXG10 iBSC (V6.20) Base Station Controller Maintenance
Manual (Troubleshooting)
ZXG10 iBSC (V6.20) Base Station Controller Maintenance
Manual (Emergency Maintenance)
ZXG10 BSS (V6.20) Base Station Subsystem Notification
Handling Manual
ZXG10 BSS (V6.20) Base Station Subsystem OMM Sofrware
Installation Manual
ZXG10 BSS (V6.20) Base Station Subsystem Configuration
Manual (Initial Configuration Guide)
ZXG10 BSS (V6.20) Base Station Subsystem Configuration
Manual (Feature Configuration Guide)
ZXG10 BSS (V6.20) Base Station Subsystem MML Command
Manual
ZXG10 BSS (V6.20) Base Station Subsystem Radio
Parameters Manual
ZXG10 BSS (V6.20) Base Station Subsystem Operation
Manual (Diagnosis and Test)
ZXG10 BSS (V6.20) Base Station Subsystem Operation
Manual (Signaling Tracing)
Conventions
Typographical ZTE documents employ the following typographical conventions.
Conventions
T ABLE 2 TYPOGR APHICAL CONVENTIONS
Typeface Meaning
Italics References to other Manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input
fields, radio button names, check boxes, drop-
down lists, dialog box names, window names.
CAPS Keys on the keyshelf and buttons on screens and
company name.
Constant width Text that you type, program code, files and
directory names, and function names.
[] Optional parameters.
{} Mandatory parameters.
| Select one of the parameters that are delimited
by it.
Note: Provides additional information about a
certain topic.
Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.
Typeface Meaning
moving the mouse.
Hazardous substances
Names of Parts
Pb Hg Cd Cr(VI) PBB’s PBDE’s
System × 0 0 0 0 0
Cables and Assembly 0 0 0 0 0 0
Auxiliary Equipment × × × × × ×
Table Explanation:
0: The usage of the substance in all of the components is less
than the allowed values given by 2002/95/EC standard.
×: The usage of the substance in at least one of the components
is beyond the allowed values given by 2002/95/EC standard.
Note:
Alarm levels can be modified in the Netnumen M31 EMS
system based on the actual situations.
Generally, the default settings are comparatively reasonable.
Be cautious when re-defining levels. It is not allowed to
modify the settings at will.
In addition, some alarm levels are not defined. For these alarms,
users can define their levels in actual situations.
Alarm Handling
Pay attention to the following points when handling alarms:
After noting down the problem and symptom, system
maintenance personnel should handle the alarms step by
step by referring to the solutions described in this manual.
Unless otherwise specified, end the alarm handling once the
fault is rectified (that is, the alarm is recovered), or go to the
next step if the problem persists.
If the alarm fails to be handled or recovered, contact the
local ZTE office.
Alarm Classification
The BSS related alarm messages on Netnumen M31 can be
classified into the following six types:
Equipment alarms
Communication alarms
Handling alarms
Environment alarms
QoS alarms
Alarm Messages
Equipment Alarms
Loss of Optical Transceiver Module
Signal
Alarm Property Alarm code: 198000002
Alarm level: 2
Alarm Cause The local-end RX fiber or peer-end TX fiber is not properly
connected.
The local or peer-end optical transceiver module is faulty.
The peer end does not export optical signals forcibly.
The UIM has no TFS subcard or the board does not provide
TDM optical interface function.
Influence The link connected to the fiber circuit is broken and the service
is interrupted.
Handling Flow 1. Correctly insert the local and the peer-end fibers and check if
the alarm is eliminated.
2. Replace the fiber and check if the alarm is eliminated.
starts. If this trunk link is not used for CSU loopback test, this
alarm won't be triggered.
Influence The configured trunk link is congested.
Handling Flow After diagnosis and test, do some settings, where end A sends
the command of canceling CSU loopback to end B.
SDH/SONET fault
Alarm Property Alarm code: 198001792
Alarm level: 2
Alarm Cause The upstream optical transmission device is faulty.
The optical fiber transmission line is faulty.
SDH/SONET:Loss of Frame
Alarm Property Alarm code: 198001793
Alarm level: 2
Alarm Cause The upstream SDH devices are faulty.
Influence All the trunk receiving signals that are transmitted through the
SDH/SONET line are interrupted.
Handling Flow Ask SDH transmission equipment maintenance personnel to
rectify the faults.
Alarm level: 2
Alarm Cause The optical fiber on the optical distribution frame is incorrectly
connected during optical fiber cutover and scheduling, or the
expected value is incorrectly set on the network management
system.
Influence The matching relations of the trunks and trunk signals are wrong.
Handling Flow 1. Check if the fibers are correctly connected to the ODFs at
local end and peer end.
If yes, go to step 2.
If no, correctly connect the fibers, and then check if the
alarm is eliminated.
2. Check if the predefined values of “section access point
identifier” at both ends are consistent. If not, set the same
value. Check whether the alarm is eliminated.
SDH/SONET:MS-AIS,Line Alarm
Indication Signal
Alarm Property Alarm code: 198001795
Alarm level: 2
Alarm Cause The upriver equipment has faults, such as LOS, LOF, and RS
TIM.
Influence All the trunk receiving signals that are transmitted through the
SDH/SONET line are interrupted.
Handling Flow Clear the “primary alarm” according to the alarm generated from
the network node equipment in the corresponding multiplexing
section.
SDH/SONET:Multiplexing Section
Far-end Reception Failure/Line Far-
end Reception Failure
Alarm Property Alarm code: 198001796
Alarm level: 3
Alarm Cause Errors occur on the uplink direction of the downstream
equipment.
Influence All the trunk sending signals that are transmitted through the
SDH/SONET line are interrupted.
Handling Flow
SDH/SONET:Signal Failure
Alarm Property Alarm code: 198001797
Alarm level: 2
Alarm Cause For all the NEs in the multiplexing section where the board
resides, the fiber pigtail connectors in the down direction are
contaminated. The increase of transmission line attenuation
or change in optical transmission mode leads to error code.
The ADM transmit device is faulty.
Influence All the trunk receiving signals that are transmitted through the
SDH/SONET line generate large numbers of alarms.
Handling Flow 1. Check if the fiber pigtail heads are contaminated.
If yes, clean the connectors, and then check if the alarm
is eliminated.
If no, go to step 2.
2. Use an optical power meter to detect the optical power
attenuation of each connection point in the down direction in
the multiplexing section and find if the value is excessive.
If yes, adjust the attenuation, and then check if the
alarm is eliminated.
If no, go to step 3.
3. Ask maintenance personnel for transmission network to
check if the ADM transmit device is faulty, end the alarm
handing.
SDH/SONET:Signal Deterioration
Alarm Property Alarm code: 198001798
Alarm level: 3
Alarm Cause When signal degrade (SD) and signal fail (SF) occur at the same
time, eliminate SF first. When SD occurs individually, it can be
inferred that the ADM transmit device is faulty.
Influence Some trunk receiving signals generate various alarms.
Handling Flow 1. Eliminate SF, if it occurs. Check if the alarm is eliminated.
2. Check the optical fibers and fiber transceiver modules at the
local and peer ends. Ensure that the optical fibers are well
connected and that the optical transceiver module is not
loose. Check if the alarm is eliminated.
SDH/SONET:Loss of AU-4
Pointer/Loss of Channel Pointer
Alarm Property Alarm code: 198001799
Alarm level: 2
Alarm Cause The upstream AU-4 pointer processing unit is faulty.
Influence All the trunk receiving signals that are transmitted through the
SDH/SONET line are interrupted.
Handling Flow Ask maintenance personnel for transmission network to check if
the AU-4 pointer processing unit of the upstream device is faulty.
SDH/SONET:AU-AIS/Channel-AIS
Alarm Property Alarm code: 198001800
Alarm level: 2
Alarm Cause The upstream VC-4 channel control unit is faulty.
Influence All the trunk receiving signals that are transmitted through the
SDH line are interrupted.
Handling Flow Ask maintenance personnel for transmission network to check if
the VC-4 channel control unit of the upstream device is faulty.
SDH/SONET:HP-Trace Mismatch/
Patch Trace Mismatch
Alarm Property Alarm code: 198001801
Alarm level: 2
Alarm Cause The optical fiber on the ODF is incorrectly connected during
optical fiber cutover and scheduling, or the expected value is
incorrectly set on the network management system.
Influence The matching relations of all the trunk signals are wrong.
Handling Flow
SDH/SONET:HP Unassembled/Path
Unassembled
Alarm Property Alarm code: 198001802
Alarm level: 2
Alarm Cause During project installation, the internal cross connection of SDH
network is not complete, or the SDTB/SDTB2 remote device is
not equipped with the channel where SDTB/SDTB2 locates.
Influence All the trunk receiving signals that are transmitted through the
SDH/SONET line are interrupted.
Handling Flow Ask maintenance personnel for transmission network to check if
the VC-4 channel control unit (C2) of the upstream device is
faulty.
SDH/SONET:LOM
Alarm Property Alarm code: 198001805
Alarm level: 2
Alarm Cause The upstream VC-4 channel control unit is faulty.
Influence All the trunk receiving signals that are transmitted through the
SDH/SONET line are interrupted.
Handling Flow Ask maintenance personnel for transmission network to check if
the VC-4 channel control unit (H4) of the upstream device is
faulty.
SDH/SONET: Loss of TU
Pointer/Loss of Virtual Tributary
Pointer
Alarm Property Alarm code: 198001806
Alarm level: 4
Alarm Cause The upstream TU pointer processing unit is faulty.
Influence The trunks that the tributary bears stop receiving trunk signals.
Handling Flow Ask maintenance personnel for transmission network to check if
the upstream TU-12 tributary pointer processing unit is faulty.
SDH/SONET:LP-RFI/Virtual
Tributary-RFI
Alarm Property Alarm code: 198001809
Alarm level: 4
Alarm Cause The upstream TU-12 tributary control unit is faulty.
Influence The trunks that the tributary bears stop receiving trunk signals.
Handling Flow 1. Check if the optical fibers are correctly connected to the
ODFs at the local end and peer end and if the processing of
the TU-12 tributary pointer of the upstream equipment is
faulty.
If the connection is correct and there is no fault, go to
step 3.
If the connection is wrong or there is a fault, go to step 2.
2. Correctly connect the optical fibers. Check if the alarm is
eliminated. This is upstream troubleshooting.
3. Check the alarms at both ends. Check the alarms at the peer
end before checking those at the local end. A loopback
operation can also be performed to locate the problem step
by step from the local end equipment, transmission
equipment, and peer end equipment. Two methods can be
used, software loop and hardware loop. Check if the alarm is
eliminated.
4. Replace the board. Check if the alarm is eliminated.
SDH/SONET:LP-Trace Mismatch/
Virtual Tributary Trace Mismatch
Alarm Property Alarm code: 198001810
Alarm level: 4
Alarm Cause The optical fiber on the digital distribution frame (DDF) is
incorrectly connected during optical fiber cutover and scheduling,
or the expected value is incorrectly set on the network
management system.
Influence The matching relations of the trunks and trunk signals that the
tributary bears are wrong.
Handling Flow 1. Check if the fibers are correctly connected to the ODFs at
local end and peer end.
If yes, go to step 2.
SDH/SONET:LP-Unloaded/Virtual
Tributary Unloaded
Alarm Property Alarm code: 198001811
Alarm level: 4
Alarm Cause During project installation, the internal cross connection of SDH
network is not complete, or the remote device isn't equipped
with the tributary.
Influence The trunks that the tributary bears stop receiving trunk signals.
Handling Flow 1. Check the optical fibers and fiber transceiver modules at the
local and peer ends. Ensure that the optical fibers are well
connected and that the optical transceiver modules are not
loose. Check if the alarm is eliminated.
2. Ask maintenance personnel to check the connections at both
ends. Ensure that the signal label received by the tributary is
consistent with that at the local end. Check if the alarm is
eliminated.
3. Ask the maintenance personnel for transmission equipment
to use an SDH tester to check if the upstream and
downstream circuit configurations of each DXC node device
on the transmission line during the corresponding timeslot
are correct, and check if V5 byte configuration is consistent
with that at peer-end. (The default configuration at local end
is asynchronous mapping.)
4. Replace the board. Check if the alarm is eliminated.
SDH/SONET:LP Label
Mismatch/Virtual Tributary Label
Mismatch
Alarm Property Alarm code: 198001812
Alarm level: 4
Alarm Cause The upstream and downstream circuits of DXCs of each station
are not complete. The V5 signal label is inconsistent with that at
the peer end.
Influence The trunks that the tributary bears stop receiving trunk signals.
Handling Flow 1. Check the optical fibers and fiber transceiver modules at the
local and peer ends. Ensure that the optical fibers are well
connected and that the optical transceiver modules are not
loose. Check if the alarm is eliminated.
2. Ask maintenance personnel to check the configuration
connections at both ends. Ensure that the information on V5
signal label is consistent with that at the peer end. Check if
the alarm is eliminated.
3. Replace the board. Check if the alarm is eliminated.
Alarm level: 2
Alarm Cause The receiving signal attenuation is excessive.
The optical fiber head is contaminated or the connector is
wrong.
The peer-end transmitting part in multiplexing section is
faulty.
The local-end receiving part in multiplexing section is faulty.
B2 error code
Influence All the voice services that the optical path bears have noises or
call losses. The data service channel has error codes.
Handling Flow 1. Check the optical fibers and fiber transceiver modules at the
local and peer ends. Ensure that the optical fibers are well
connected and that the optical transceiver modules are not
loose. Check if the alarm is eliminated.
2. Replace the optical module or board. Check if the alarm is
eliminated.
3. Ask maintenance personnel to check the peer-end office.
After the fault is rectified, check if the alarm is eliminated.
4. Something may be wrong with the transmission equipment.
Ask maintenance personnel special for transmission
equipment to do troubleshooting.
SDH/SONET:MS-Remote Error
Indication
Alarm Property Alarm code: 198001820
Alarm level: 2
Alarm Cause The receiving signal attenuation is excessive.
The transmitting part of the directly connected transmission
equipment is faulty.
The optical fiber head is contaminated or the connector is
wrong.
The receiving part at the local end is faulty.
Influence The voice services that the optical path bears have noises or call
losses. The data service channel has error codes.
Handling Flow 1. Check the optical fibers and fiber transceiver modules at the
local and peer ends. Ensure that the optical fibers are well
connected and that the optical transceiver modules are not
loose. Check if the alarm is eliminated.
2. Replace the optical module or board. Check if the alarm is
eliminated.
3. Ask maintenance personnel to check the peer-end office.
After the fault is rectified, check if the alarm is eliminated.
4. Something may be wrong with the transmission equipment.
Ask maintenance personnel special for transmission
equipment to do troubleshooting.
SDH/SONET:HP-Remote Error
Indication
Alarm Property Alarm code: 198001821
Alarm level: 2
Alarm Cause The receiving signal attenuation is excessive.
The transmitting part of the directly connected transmission
equipment is faulty.
The optical fiber head is contaminated or the connector is
wrong.
The receiving part at the local end is faulty.
Influence The voice services that the optical path bears have noises or call
losses. The data service channel has error codes.
Handling Flow 1. Check the optical fibers and fiber transceiver modules at the
local and peer ends. Ensure that the optical fibers are well
connected and that the optical transceiver modules are not
loose. Check if the alarm is eliminated.
2. Replace the optical module or board. Check if the alarm is
eliminated.
3. Ask maintenance personnel to check the peer-end office.
After the fault is rectified, check if the alarm is eliminated.
4. Something may be wrong with the transmission equipment.
Ask maintenance personnel special for transmission
equipment to do troubleshooting.
Alarm level: 2
Alarm Cause For all the NEs in the multiplexing section where the board
resides, the fiber pigtail connectors in the down direction are
contaminated. The increase of transmission line attenuation
or change in optical transmission mode leads to error code.
The ADM transmit device is faulty.
Influence All the trunk receiving signals that are transmitted through the
SDH/SONET line generate large numbers of alarms.
Handling Flow 1. Check the optical fibers and fiber transceiver modules at the
local and peer ends. Ensure that the optical fibers are well
connected and that the optical transceiver modules are not
loose. Check if the alarm is eliminated.
2. Replace the optical module or board. Check if the alarm is
eliminated.
3. Ask maintenance personnel to check the peer-end office.
After the fault is rectified, check if the alarm is eliminated.
4. Something may be wrong with the transmission equipment.
Ask maintenance personnel special for transmission
equipment to do troubleshooting.
SDH/SONET:HP Signal
Deterioration
Alarm Property Alarm code: 198001823
Alarm level: 2
Alarm Cause When signal degrade (SD) and signal fail (SF) occur at the same
time, eliminate SF first. When SD occurs individually, it can be
inferred that the ADM transmit device is faulty.
Influence Some trunk receiving signals generate various alarms.
Handling Flow 1. Eliminate SF, if it occurs. Check if the alarm is eliminated.
2. Check the optical fibers and fiber transceiver modules at the
local and peer ends. Ensure that the optical fibers are well
connected and that the optical transceiver module is not
loose. Check if the alarm is eliminated.
3. Replace the fiber module or board. Check if the alarm is
eliminated.
4. Ask maintenance personnel to check the peer-end office and
rectify the faults. Check if the alarm is eliminated.
5. Something may be wrong with the transmission equipment.
Ask maintenance personnel special for transmission
equipment to do troubleshooting.
OFF Alarm
Alarm Property Alarm code: 198002050
Alarm level: 3
Alarm Cause The protocols used by the two matching parties mismatch.
They must use the E3 (E1) or T3 (T1) protocols at the same
time. E3 (E1) cannot match T3 (T1)
Cable transmission incurs error.
Influence E3 transmission is exceptional.
Handling Flow 1. Check if the protocols used by the matching parties match
each other, that is, both use E3 (E1) or T3 (T1).
If they mismatch, configure the same protocol.
If they match, go to step 2.
Handling Flow 1. Check if the fans work normally and if the fans are
insufficient.
If the fans are insufficient, add fans and power on all the
fans. Wait for ten minutes. Check if the alarm is
eliminated.
If the fans are not powered on, power them on and wait
for ten minutes. Check if the alarm is eliminated.
If the fans are sufficient and work normally, go to step 2.
2. Check if the temperature in the equipment room is too high.
If the temperature is high, improve the ventilation
situation or take measures to reduce the temperature.
After the temperature returns to normal range, check if
the alarm is eliminated.
If the temperature is normal, go to step 3.
3. Note down the alarm information.
2. Pull out and then plug in the board again in position. Check if
the alarm is eliminated.
3. Replace the slot. Check if the alarm is eliminated.
SMBUS Error
Alarm Property Alarm code: 198005636
Alarm level: 2
Alarm Cause If the board is reset when the read-write time sequences of the
SMBUS equipment are not finished, the SMBUS cannot be
enabled after the south bridge is reset. All the SMBUS
equipments need be reset again (the board need be pulled out
and plugged).
Influence When the SMBUS incurs error, the board can be restarted
through BIOS settings. However, after the version is run, the
temperature cannot be detected for the board with SMBUS
FPGA Exception
Alarm Property Alarm code: 198005640
Alarm level: 2
Alarm Cause FPGA runs exceptionally. For example, FPGA is lost and the
mother board clock is lost.
Influence The board cannot work normally.
Handling Flow Restart the board and then the board downloads EPGA again.
Remarks This alarm seldom occurs.
Subcard Abnormal
Alarm Property Alarm code: 198005645
Alarm level: 3
Alarm Cause The UIM/CHUB GCS sub-card is exceptional. The probable
reasons are:
The sub-card is not inserted in position.
Alarm Cause The peer end has faults. That is, the configuration has faults or
the devices do not support. The symptom is the bridging channel
that the remote end indicates through K2 is not the one required
by the local.
Influence The switchover fails when the configuration is 1:1.
Handling Flow 1. Check if configurations on the two ends are both 1+1 or
1:1(1:N).
If no, modify them as consistent ones. Check if the alarm
is eliminated.
If yes, go to step 2.
2. Check if PSN boards are in running status. Check if the
optical fiber connections are correct. If no, correctly connect
the optical fibers and check if the alarm is eliminated.
No Response to Requesting
Database for Secondary Forwarding
Table Information
Alarm Property Alarm code: 198019968
Alarm level: 2
Alarm Cause The OMP is not normally powered on.
Control plane messages are delayed.
Influence The media flow in the shelf of the UIM is broken.
Handling Flow 1. Restart the OMP board to see if it works normally.
2. Restart the UIM board to see if it works normally.
3. Record the details.
Alarm level: 3
Alarm Cause Bugs exist in configuration or chip.
Influence The link may be broken.
Handling Flow Check the configuration. Replace the board. Check if the alarm is
eliminated.
If yes, go to step 3.
If no, go to step 4.
3. Check whether there are sufficient link resources.
If sufficient, query performance statistic data to check
whether load are evenly shared among links. If yes, go to
step 1. If no, go to step 4.
If insufficient, add new links and check whether this
alarm is eliminated. If no, use the above method for
sufficient link resources.
4. Record the details.
Back up related local office configuration data and peer-
end office configuration data.
Back up related local office and peer-end office history
alarms and notifications, as well as current alarms.
Handling Flow Change the EPU version to the one matching the RPU version.
Check if the alarm is eliminated.
MCC Abnormal
Alarm Property Alarm code: 198066050
Alarm level: 2
Alarm Cause The MCC hardware is faulty.
Influence All MCC channels cannot transceive data.
Handling Flow Pull out the board for 5 seconds and insert it again after a full
discharge. Check if the alarm is eliminated.
Power overvoltage/undervoltage
alarm
Alarm Property Alarm code: 198087102
Alarm level: 3
Alarm Cause CMM/CMB power voltage is out of adjustment range.
Influence CMB works exceptionally.
Handling Flow Replace CMM/CMB board as soon as possible.
Alarm level: 3
Alarm Cause The alarm is due to chip fault, abnormal clock, difference from
BSC clock, bad E1 connections, or others.
Influence If the problem seldom occurs, the conversation is slightly
affected. If the problem frequently occurs, for example, once
every several minutes, the conversation is abnormal or the link
between TRM/DTRU and BSC is abnormal.
Handling Flow 1. Check the electric-connection performance of E1 line through
loopback test.
If fault exists, make cables again to rectify the faults.
If no fault exists, go to step 2.
2. Tightly insert CMM/CMB and power it on again. Check if the
alarm is eliminated.
3. Start the self-loop detection and check if the E1 interface
self-loop detection is normal.
If yes, it is inferred that the transmission is faulty.
Troubleshoot the transmission faults.
If no, go to step 4.
4. Replace CMM/CMB board. Check if the alarm is eliminated.
5. Replace the backplane.
If no, go to step 4.
4. Replace CMM/CMB board. Check if the alarm is eliminated.
5. Replace the backplane.
Alarm level: 3
Alarm Cause The alarm is due to chip fault, abnormal clock, difference from
BSC clock, bad E1 connections, or others.
Influence If the problem seldom occurs, the conversation is slightly
affected. If the problem frequently occurs, for example, once
every several minutes, the conversation is abnormal or the link
between TRM/DTRU and BSC is abnormal.
Handling Flow 1. Check the electric-connection performance of E1 line through
loopback test.
If fault exists, make cables again to rectify the faults.
If no fault exists, go to step 2.
2. Tightly insert CMM/CMB and power it on again. Check if the
alarm is eliminated.
3. Start the self-loop detection and check if the E1 interface
self-loop detection is normal.
If yes, it is inferred that the transmission is faulty.
Troubleshoot the transmission faults.
If no, go to step 4.
4. Replace CMM/CMB board. Check if the alarm is eliminated.
5. Replace the backplane.
Alarm level: 3
Alarm Cause The alarm is due to chip fault, abnormal clock, difference from
BSC clock, bad E1 connections, or others.
Influence If the problem seldom occurs, the conversation is slightly
affected. If the problem frequently occurs, for example, once
every several minutes, the conversation is abnormal or the link
between TRM/DTRU and BSC is abnormal.
Handling Flow 1. Check the electric-connection performance of E1 line through
loopback test.
If fault exists, make cables again to rectify the faults.
If no fault exists, go to step 2.
2. Tightly insert CMM/CMB and power it on again. Check if the
alarm is eliminated.
3. Start the self-loop detection and check if the E1 interface
self-loop detection is normal.
If yes, it is inferred that the transmission is faulty.
Troubleshoot the transmission faults.
If no, go to step 4.
4. Replace CMM/CMB board. Check if the alarm is eliminated.
5. Replace the backplane.
If no, go to step 4.
4. Replace CMM/CMB board. Check if the alarm is eliminated.
5. Replace the backplane.
Alarm level: 3
Alarm Cause The alarm is due to chip fault, abnormal clock, difference from
BSC clock, bad E1 connections, or others.
Influence If the problem seldom occurs, the conversation is slightly
affected. If the problem frequently occurs, for example, once
every several minutes, the conversation is abnormal or the link
between TRM/DTRU and BSC is abnormal.
Handling Flow 1. Check the electric-connection performance of E1 line through
loopback test.
If fault exists, make cables again to rectify the faults.
If no fault exists, go to step 2.
2. Tightly insert CMM/CMB and power it on again. Check if the
alarm is eliminated.
3. Start the self-loop detection and check if the E1 interface
self-loop detection is normal.
If yes, it is inferred that the transmission is faulty.
Troubleshoot the transmission faults.
If no, go to step 4.
4. Replace CMM/CMB board. Check if the alarm is eliminated.
5. Replace the backplane.
Temperature alarm
Alarm Property Alarm code: 198087170
Alarm level: 4
Alarm Cause The alarm is due to fan fault or too high module temperature.
Influence If the problem seldom occurs, the conversation is slightly
affected. If the problem frequently occurs, for example, once
every several minutes, the conversation is abnormal or the link
between TRM/DTRU and BSC is abnormal.
Handling Flow Check the environment temperature. If it conforms to the
demand, keep on observing and keep normal status on
prerequisite that other modules have no fault. If not improve the
work environment. If fault exists, change the FCM module.
Fan absent
Alarm Property Alarm code: 198087171
Alarm level: 4
Alarm Cause The fan is not inserted or not in position.
Influence TRM/DTRU temperature is too high and the performance indices
are affected.
Handling Flow Insert the fan, or pull out and plug in the fan again.
Fan 1 alarm
Alarm Property Alarm code: 198087175
Alarm level: 4
Alarm Cause The fan stops rotating due to fault.
Influence The frequency shelf on the same layer has high temperature.
Handling Flow 1. Check if the fan stops rotating.
If it stops, change the fan subrack.
If no, go to step 2.
2. Check if the link between the fan and the fan control board is
faulty.
If faults exist, go to step 3.
If no fault exists, go to step 4.
3. Check if the fan cables have faults and if the board-to-board
connectors have faults.
If the fan cables have faults, change the fan subrack.
If the board-to-board connectors have faults, change the
fan control board DFCM/FNCB.
4. Check if the alarm line is faulty.
If yes, troubleshoot the alarm line.
If no, go to step 5.
5. Check if alarm collection on the fan control board is
exceptional.
Fan 2 alarm
Alarm Property Alarm code: 198087176
Alarm level: 4
Alarm Cause The fan stops rotating due to fault.
Influence The frequency shelf on the same layer has high temperature.
Handling Flow 1. Check if the fan stops rotating.
If it stops, change the fan subrack.
If no, go to step 2.
2. Check if the link between the fan and the fan control board is
faulty.
If faults exist, go to step 3.
If no fault exists, go to step 4.
3. Check if the fan cables have faults and if the board-to-board
connectors have faults.
If the fan cables have faults, change the fan subrack.
If the board-to-board connectors have faults, change the
fan control board DFCM/FNCB.
4. Check if the alarm line is faulty.
If yes, troubleshoot the alarm line.
If no, go to step 5.
5. Check if alarm collection on the fan control board is
exceptional.
If exceptions occur, change the fan control board
DFCM/FNCB.
If no exceptions occur, go to step 6.
6. Check if alarm collecting circuit of TRM/DTRU is exceptional.
If yes, change the TRM/DTRU.
Alarm Cause The alarm is due to fan fault or too high module temperature.
Influence TRM/DTRU temperature is too high and the performance indices
are affected.
Handling Flow Check the environment temperature. If it conforms to the
demand, keep on observing and keep normal status on
prerequisite that other modules have no fault. If not improve the
work environment. If fault exists, change the FCM module.
LNA alarm
Alarm Property Alarm code: 198087178
Alarm level: 3
Alarm Cause LNA current exceeds by 30%.
Influence The connected TRM/DTRU cannot work completely (if both active
and density LNAs are faulty) or cannot work normally (only one
LNA is faulty).
Handling Flow Replace AEM module as soon as possible.
LNA0 alarm
Alarm Property Alarm code: 198087186
Alarm level: 3
Alarm Cause LNA0 current exceeds by 30%.
Influence The connected DTRU cannot work completely (if both active and
density LNAs are faulty) or cannot work normally (only one LNA
is faulty).
Handling Flow Replace AEM module as soon as possible.
LNA1 alarm
Alarm Property Alarm code: 198087187
Alarm level: 3
Alarm Cause LNA1 current exceeds by 30%.
Influence The connected DTRU cannot work completely (if both active and
density LNAs are faulty) or cannot work normally (only one LNA
is faulty).
Handling Flow Replace AEM module as soon as possible.
Uplink failure
Alarm Property Alarm code: 198087201
Alarm level: 3
Alarm Cause Errors occur during the receipt of uplink data.
Influence The TRM/DTRU is unavailable. If it is BCCH carrier, the normal
operation of the whole cell is affected.
Handling Flow 1. Reset the module.
2. Replace the module if the reset does not solve the problem.
Alarm level: 3
Alarm Cause DSP0 of channel processing unit has no response temporarily.
Influence If DSP0 of channel processing unit has no response temporarily,
the control unit loads and initializes the DSP again. If the alarm
cannot be eliminated, it indicates that the DSP loading cannot
succeed. This fault disables two channels of a carrier unit to
work. If the carrier is BCCH, the whole cell cannot work.
Handling Flow Reset this CU. Check if the alarm is eliminated.
If the alarm is eliminated, it is inferred that the alarm is
arisen by interior DSP exceptions. After resetting resumes,
the CU could work normally.
If the alarm is not eliminated, start the BCCH switchover
policy on the BSC and replace TRM/DTRU.
Alarm level: 3
Alarm Cause This alarm is caused by DSP software or hardware error.
Influence The modulation module cannot work. The carrier or cell (when
the carrier is assigned BCCH) cannot work normally.
Handling Flow 1. Download the DSP software again.
2. Reset TRM/DTRU and restart DSP. Check if the alarm is
eliminated.
If the alarm is eliminated, the DSP initialization failure is
due to strong exterior interference. The TRM/DTRU can
work normally.
If the alarm is not eliminated, change the TRM/DTRU.
Alarm Cause The DTRU fails to work. If the DTRU has BCCH carrier, the cell
service is affected.
Influence The DTRU fails to work. If the DTRU has BCCH carrier, the cell
service is affected.
Handling Flow Measure the clock of BURST interruption to check whether it is
normal or not, if it breaks down, then replace the DTRM module
in time.
CU intialization failure
Alarm Property Alarm code: 198087249
Alarm level: 3
Alarm Cause This problem is caused by DSP software or hardware error.
Influence The modulation module cannot work. If the carrier is assigned
SCCH, the carrier or cell cannot work normally.
Handling Flow 1. Download the DSP software again.
2. Reset the module and restart DSP. Check if the alarm is
eliminated.
If the alarm is eliminated, the DSP initialization failure is
due to strong exterior interference. The module can work
normally.
If the alarm is not eliminated, change the module.
TPU's FN alarm
Alarm Property Alarm code: 198087253
Alarm level: 3
Alarm Cause Frame clock FCLK has problem and upper-level frame number
synchronization source FUC has problem.
Influence The DTRU fails to work. If the DTRU has BCCH carrier, the cell
service is affected.
Handling Flow 1. Check if FCLK of frame number producing point is normal. If
it is directly transported, check the clock frequency, wave
shape; if it is produced by phase locked, check whether the
alarm of lost lock exists. If there are some problems, replace
TRM module.
2. Check the transmission link, that is, transmission clock,
interface chip, the size of error code rate.
Rx PLL1 unlock
Alarm Property Alarm code: 198087254
Alarm level: 3
Alarm Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) fault.
Influence Conversation may fail on the TRM/DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module. Check if the alarm is eliminated.
3. Replace the module.
Rx PLL2 unlock
Alarm Property Alarm code: 198087255
Alarm level: 3
Alarm Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) fault.
Influence Conversation may fail on the TRM/DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module. Check if the alarm is eliminated.
3. Replace the module.
Tx PLL1 unlock
Alarm Property Alarm code: 198087256
Alarm level: 3
Alarm Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) fault.
Influence Conversation may fail on the TRM/DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module. Check if the alarm is eliminated.
3. Replace the module.
Tx PLL2 unlock
Alarm Property Alarm code: 198087257
Alarm level: 3
Alarm Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) fault.
Influence Conversation may fail on the TRM/DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module. Check if the alarm is eliminated.
3. Replace the module.
Tx IF PLL unlock
Alarm Property Alarm code: 198087259
Alarm level: 3
Alarm Cause Clock signal is unstable or TRM Phase-Locked Loop (PLL) fault.
Influence Conversation may fail on the TRM/DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module. Check if the alarm is eliminated.
3. Replace the module.
PA overtemperature minor
alarm(BTS V2)
Alarm Property Alarm code: 198087263
Alarm level: 4
Alarm Cause PA temperature is too high, which is possibly due to PA working
with rated power for a long time, fan not working for a long time,
too high environment temperature, detecting circuit fault, and
other reasons.
Influence The TRM/DTRU can work, but the PA degradation speeds up.
Handling Flow 1. Check if the fan can work normally.
If yes, go to step 2.
If no, rectify the faults. Check if the alarm is eliminated.
2. Check if the environment temperature is too high.
If yes, go to step 3.
If no, improve the equipment room environment. Check if
the alarm is eliminated.
PA overtemperature major
alarm(BTS V2)
Alarm Property Alarm code: 198087264
Alarm level: 3
Alarm Cause PA temperature is too high, which is possibly due to PA working
with rated power for a long time, fan not working for a long time,
too high environment temperature, detecting circuit fault, and
other reasons.
Influence The power output of the TRM/DTRU is protectively shutdown. PA
degradation speeds up.
Handling Flow 1. Check if the fan can work normally.
If yes, go to step 2.
If no, rectify the faults. Check if the alarm is eliminated.
2. Check if the environment temperature is too high.
If yes, go to step 3.
If no, improve the equipment room environment. Check if
the alarm is eliminated.
3. Reset the module. Check if the alarm is eliminated.
4. The testing circuit may be faulty. Replace the module.
PA power overvoltage
Alarm Property Alarm code: 198087266
Alarm level: 3
Alarm Cause The problem is caused by overvoltage of PA power.
Influence The PA may be damaged. The modulation module protectively
closes the power output.
Handling Flow Check if the PA testing circuit is faulty. If yes, replace the
TRM/DTRU as soon as possible.
80w PA overtemperature
Alarm Property Alarm code: 198087271
Alarm level: 4
Alarm Cause PA temperature is too high, which is possibly due to PA working
with rated power for a long time, fan not working for a long time,
too high environment temperature, detecting circuit fault, and
other reasons.
Influence The TRM/DTRU can work but the PA degradation speeds up.
Handling Flow 1. Check if the fan can work normally.
If yes, go to step 2.
If no, rectify the faults. Check if the alarm is eliminated.
2. Check if the environment temperature is too high.
If yes, go to step 3.
If no, improve the equipment room environment. Check if
the alarm is eliminated.
3. Reset the module. Check if the alarm is eliminated.
4. The testing circuit may be faulty. Replace the module.
Alarm level: 3
Alarm Cause PA temperature is too high, which is possibly due to PA working
with rated power for a long time, fan not working for a long time,
too high environment temperature, detecting circuit fault, and
other reasons.
Influence The TRM/DTRU can work but the PA degradation speeds up.
Handling Flow 1. Check if the fan can work normally.
If yes, go to step 2.
If no, rectify the faults. Check if the alarm is eliminated.
2. Check if the environment temperature is too high.
If yes, go to step 3.
If no, improve the equipment room environment. Check if
the alarm is eliminated.
3. Reset the module. Check if the alarm is eliminated.
4. The testing circuit may be faulty. Replace the module.
80w PA absent
Alarm Property Alarm code: 198087276
Alarm level: 3
Alarm Cause The PA is not in position.
Influence No output power.
Handling Flow Check if the PA testing circuit is faulty. If yes, replace the
TRM/DTRU as soon as possible.
TXIF unlock
Alarm Property Alarm code: 198087277
Alarm level: 3
Alarm Cause Clock signal is unstable or DTRM Phase-Locked Loop (PLL) is
faulty.
Influence Conversations may fail on the DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module again. Check if the alarm is eliminated.
3. Replace the module.
TPF unlock
Alarm Property Alarm code: 198087278
Alarm level: 3
Alarm Cause Clock signal is unstable or DTRM Phase-Locked Loop (PLL) is
faulty.
Influence Conversations may fail on the DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
TXRF unlock
Alarm Property Alarm code: 198087279
Alarm level: 3
Alarm Cause Clock signal is unstable or DTRM Phase-Locked Loop (PLL) is
faulty.
Influence Conversations may fail on the DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module again. Check if the alarm is eliminated.
3. Replace the module.
RXRF unlock
Alarm Property Alarm code: 198087280
Alarm level: 3
Alarm Cause Clock signal is unstable or DTRM Phase-Locked Loop (PLL) is
faulty.
Influence Conversations may fail on the DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module again. Check if the alarm is eliminated.
3. Replace the module.
60 ms clock lost
Alarm Property Alarm code: 198087282
Alarm level: 3
Alarm Cause 60 ms synchronization clock receiving is abnormal and 60 ms
synchronization clock unit works abnormally.
Influence Conversations may fail on the DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module again. Check if the alarm is eliminated.
3. Check if the socket on the backplane of the corresponding
module is normal. If it is normal, replace the module and
then check if the alarm is eliminated. If it is not exceptional,
replace the backplane and then check if the alarm is
eliminated.
4. Replace the CMB.
8M clock of HW lost
Alarm Property Alarm code: 198087283
Alarm level: 3
Alarm Cause HW 8 MHz clock receiving is abnormal and HW 8 MHz clock unit
works abnormally.
Influence Conversations may fail on the DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module again. Check if the alarm is eliminated.
3. Check if the socket on the backplane of the corresponding
module is normal. If it is normal, replace the module and
then check if the alarm is eliminated. If it is not exceptional,
replace the backplane and then check if the alarm is
eliminated.
4. Replace the CMB.
8K clock of HW lost
Alarm Property Alarm code: 198087284
Alarm level: 3
Alarm Cause HW 8 kHz clock receiving is abnormal and HW 8 kHz clock unit
works abnormally.
Influence Conversations may fail on the DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module again. Check if the alarm is eliminated.
3. Check if the socket on the backplane of the corresponding
module is normal. If it is normal, replace the module and
then check if the alarm is eliminated. If it is not exceptional,
replace the backplane and then check if the alarm is
eliminated.
4. Replace the CMB.
Alarm Cause AD6650 clock receiving is abnormal and AD6650 clock unit
works abnormally.
Influence Conversations may fail on the DTRU.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module again. Check if the alarm is eliminated.
3. Replace the DTRU.
PA VSWR alarm
Alarm Property Alarm code: 198087290
Alarm level: 3
Alarm Cause The reverse power is too high. It may be caused by the
existence of open circuit or high resistance in output end of PA.
Influence Conversation fails on the DTRU. The PA is damaged.
Handling Flow 1. Reset DTRU. Check if the alarm is eliminated.
2. Replace the RF cables from DTRU to AEM. Check if the alarm
is eliminated.
3. Replace DTRU.
Handling Flow 1. Check if the lines between the heat exchanger control board
and the fan are normal.
2. Replace the fan.
FR device failure
Alarm Property Alarm code: 198087340
Alarm level: 2
Alarm Cause The BRCH works abnormally. N392 errors are detected in the
last N393 STATUS ENQUIRY events.
Influence The BRCH on Gb interface is broken.
Handling Flow 1. Check if the E1 interface of the BRCH has alarms incessantly.
If yes, check the transmission equipment and rectify
transmission alarms.
2. Check if E1 device is normal through a selfloop test at the
local. If it is abnormal, change the E1 line and check if the
alarm is eliminated. If it is normal, then contact SGSN
maintenance personnel to perform peer-end selfloop. Check
if the peer end is normal. If no, then contact peer-end
FR congestion
Alarm Property Alarm code: 198087341
Alarm level: 3
Alarm Cause In case of an intermediate Frame Relay network, the number of
a frame with a BECN bit set to "1" is more than or equal to the
number of a frame with a BECN bit set to "0" in T interval.
Influence Quality of some users’ PS service is reduced.
Handling Flow Add BRCG links or BRCH timeslots.
Handling Flow 1. Check alarm details. If the flow control level is 8 or lower
than 8, observe for three minutes and check if the alarm is
eliminated. If the flow control level is higher than 8, go to
step 2.
2. Check if the cell parameter RACH overload level threshold is
correct.
3. Check the traffic statistics. Consider expanding overloaded
sites or using traffic sharing.
Tx PLL unlock
Alarm Property Alarm code: 198087368
Alarm level: 3
Alarm Cause The clock signal is unstable, or the TRM/DTRU phase-locked loop
is faulty.
Influence S8001 cannot converse.
Handling Flow 1. Reset the module. Check if the alarm is eliminated.
2. Power on the module again. Check if the alarm is eliminated.
3. Change the module.
Handling Flow Reset the HBTS and check if the alarm is eliminated. If the alarm
is eliminated, it is inferred that the alarm is arisen by interior
interference, which makes CPU read data from FLASH MEMORY.
After resetting resumes, the CU could work normally. If the
alarm cannot be eliminated after being reset, replace the HBTS
module.
Alarm Cause The opposite board is not in position or the clock is faulty.
Influence The opposite board cannot work normally. The active and
standby switchover fails.
Handling Flow Replace the CCI board.
FN error alarm
Alarm Property Alarm code: 198087417
Alarm level: 4
Alarm Cause Downlink framing is affected.
Influence The frame number from CCI has error.
Handling Flow 1. Reset CCI. Check if the alarm is eliminated.
2. Reset GBP. Check if the alarm is eliminated.
3. Rectify CCI hardware faults. Check if the alarm is eliminated.
4. Rectify the LVDS link fault of GBP. Check if the alarm is
eliminated.
Alarm level: 3
Alarm Cause The RRU clock unit works abnormally.
Influence Normal communication fails.
Handling Flow Check if the optical fiber between RRU and BBU is normal. If no,
change the optical fibers.
Handling Flow Check the power module. If the power module is faulty, replace
it with a new one.
FR device failure
Alarm Property Alarm code: 198087430
Alarm level: 3
Alarm Cause Too many times of FLASH programming leads to read/write error.
Influence The system fails to load and read any version.
Handling Flow This problem cannot be manually solved. It belongs to FLASH
chip fault. To clear the alarm, replace the RRU.
Assignment Failure
Alarm Property Alarm code: 198087437
Alarm level: 2
Alarm Cause The TCH resource blockage rate on CMP exceeds the threshold.
Influence Calls are difficult to be given or connected. Traffic volume is
affected.
Handling Flow 1. Check if the channel is manually blocked. If yes, manually
unblock it.
2. Check if the board is normal. If no, reset, pull out and plug in,
or replace the board.
3. Check if the cell is normal and if the interference is severe. If
yes, optimize the network.
Communication Alarms
Exceptional Connection Setup
Alarm Property Alarm code: 100000
Alarm level: 1
Alarm Cause The communication between the EMS and NE is broken. The NE
is disconnected from the OMC server.
Influence Messages related to the device cannot be reported normally.
Handling Flow Check if the link is normal.
Remarks Link alarm
that may result in LOS, AIS, or LOF on the peer end would
probably cause this alarm.
Influence The trunk signals received by the trunk are interrupted.
Handling Flow At the peer end, at least one alarm among LOS, AIS, or LOF
may be generated. Check and record the peer-end alarm. Check
if intermediate transmission equipment for this trunk link has
faults. If fault occurs, clear the related fault.
Handling Flow 1. Check if FE-C3/4 is used as the routing port when UIM in the
BUSN/BGSN shelf adopts the RUIM1 rear board for FE
routing.
If FE-C3/4 is used as routing port, the system generates
an alarm. Reuse FE-C1/2 as the routing port and then
wait for 1 second to see if the alarm is eliminated.
If FE-C3/4 is not used as the routing port, the alarm will
need no handling. End alarm handling.
2. Check if the ports on the peer end connected with a couple of
ports on the local board are coupling ports.
If they are coupling ports, the alarm will need no
handling. End alarm handling.
If they aren't coupling ports, that couple of ports on the
local end will generate the alarm. Reconnect this pair of
FE lines, pay attention that both ends of their ports
should be in couples. After reconnect the FE lines, check
if the alarm is eliminated.
Remarks The ports at both ends of FE lines must be in couples, for
example:
When connecting CHUB to UIM, the connection line led from
the CHUB rear board RCHUB1/RCHUB2 must be connected
from consecutive couple of ports (port1/port2, port3/port4,
port5/port6, port7/port8) to coupling ports on the UIM rear
board.
When connecting UIM to UIM/CHUB, the ports on UIM rear
board used for connection must be in couples. For example,
if adopting the RUIM1 rear board, two FE-C1/2 ports must be
used as FE routing ports. If adopting the RUIM2/RUIM3 rear
board, the consecutive couple of ports like FE1/FE2, FE3/FE4,
FE5/FE6 must be used as FE routing ports.
Board HW Error
Alarm Property Alarm code: 198005378
Alarm level: 2
Alarm Cause NE clock is exceptional.
The TDM connection chip is exceptional.
The board hardware is faulty.
The backplane hardware is faulty.
Influence The CS domain service may be interrupted.
Handling Flow 1. Check the HW number configured for this board and
neighboring slots to see if the number exceeds the number
of physical slots.
Communication between
environment monitoring board and
OMP board abnormal
Alarm Property Alarm code: 198005382
Alarm level: 2
Alarm Cause The RS485 communication link between PWRD and OMP is
broken.
There is no connection between PWRD and OMP, or the
connection has a failure.
The rack number configured for the rack in which this PWRD
locates is not consistent with the rack number set by PWRD
DIP switches.
Influence The environment status cannot be monitored.
Handling Flow 1. Check if the connection between PWRD and OMP is correct.
If it is not correct, correctly connect OMP and PWRD.
If it is correct, go to step 2.
2. Check if the connection cables between PWRD and OMP have
faults.
If yes, replace the cables. Check if the alarm is
eliminated.
If no, go to step 3.
3. Check if the configured rack number is consistent with the
value of PWRD DIP switches. If no, adjust the value of PWRD
DIP switches. Check if the alarm is eliminated.
RAWMACIP Channel
Communication Exception
Alarm Property Alarm code: 198005397
Alarm level: 2
Alarm Cause
HDLC unavailable
Alarm Property Alarm code: 198018688
Alarm level: 2
Alarm Cause This alarm is generated when an HDLC is created. It
disappears when the link gets through.
The link is broken.
Influence If the HDLC is the last available HDLC that is bound to the UID,
then all the services of the corresponding UID are interrupted. If
the HDLC is not the last available HDLC that is bound to the UID,
the service traffic on the corresponding UID is reduced.
Handling Flow 1. Check the settings of HDLC channel to see whether the E1/TI
of this HDLC and its time slots match the peer end.
If yes, go to step 2.
If no, modify HDLC setting and make it accordant with
the peer end HDLC.
2. Check if the physical connection is correct.
If yes, go to step 3.
If no, adjust the physical connection to make it consistent
with the peer end. Check if the alarm is eliminated.
3. Check if the E1/T1 lines have quality problems.
If yes, change the E1/T1 lines. Check if the alarm is
eliminated.
If no, go to step 4.
4. Record the statistic data of messages received by and sent
from the HDLC.
UID unavailable
Alarm Property Alarm code: 198018689
Alarm level: 2
Alarm Cause This alarm is generated when a UID is created. It disappears
when the link gets through.
The link is broken.
Influence All the services on the UID are interrupted.
Handling Flow When at least one HDCL on UID becomes available, the UID can
be used. In this case, the alarm disappears automatically. To
make the HDLC available, follow the suggestions in “HDLC
unavailable.”
UID unavailable
Alarm Property Alarm code: 198018689
Alarm level: 2
Alarm Cause This alarm is generated when a UID is created. It disappears
when the link gets through.
The link is broken.
Influence All the services on the UID are interrupted.
Handling Flow
When at least one HDCL on UID becomes available, the UID can
be used. In this case, the alarm disappears automatically. To
make the HDLC available, follow the suggestions in “HDLC
unavailable.”
FE is in blocked state
Alarm Property Alarm code: 198019205
Alarm level: 2
Alarm Cause The alarm is generated at the local end when the local end IMA
group receives the “status device is in blocked state” message in
the ICP cell from the far-end IMA group.
Influence The IMA link is broken.
Handling Flow Check the status of the far-end IMA group. If the far-end group
is set to inhibited, enter the module No., subsystem No., unit
No., subunit No., and the group name on the DDM and then set
the group on the far end to “uninhibited”.
Alarm level: 2
Alarm Cause A receiving link in the group does not connect to the remote end
IMA group link other links.
Influence The Iu physical link is broken.
Handling Flow Check receiving link connections on the two ends to see if each
receiving link is connected to the near-end IMA group normally
and if the proper local E1 link is connected to the corresponding
E1 link on remote end. If a receiving link is not connected to the
near-end IMA group or the local link does not connect to the
remote link, rectify the fault and check if the alarm is eliminated.
If no, go step 2.
2. Check whether the UIM board in the same shelf as this board,
the UIM board in the shelf where the home module is located
and the CHUB (if there is any) are working normally.
If yes, go to step 3.
If no, restore the above mentioned boards to the normal
state. Check if the alarm is eliminated.
3. Check if the board is successfully powered on (that is, RUN
indicator flashes at 1 Hz). If the board is not successfully
powered on, power it on. Check if the alarm is eliminated.
Alarm level: 2
Alarm Cause This alarm is often generated during initial port creation
because ports are generally created dynamically.
The former IPCP state is OPENED. When the link changes to
broken, the link quality is reduced, or lower layer module is
faulty (for example, BSP or microcode fault), the PPP
discards packets for consecutive five times. Moreover, the
PPP state transition leads to another negation.
Influence The service is interrupted.
Handling Flow If the link is smooth and IPCP becomes opened after
negotiation, the alarm is restored.
Delete the ports that are not OPENED. The methods for
generating and deleting PPP ports vary depending on the
logical board. BIPI/GIPI are dynamically added or deleted.
PISI is statically added or deleted, that is, it has only one
external port.
HDLC unavailable
Alarm Property Alarm code: 198066024
Alarm level: 2
Alarm Cause This alarm is generated after a HDLC is created. It
disappears after the link gets through.
The link is broken.
Influence If the HDLC is the last available HDLC that is bound to the UID,
then all the services of the corresponding UID are interrupted. If
the HDLC is not the last available HDLC that is bound to the UID,
the service traffic on the corresponding UID is reduced.
Handling Flow 1. Check the settings of HDLC channel to see whether the E1/TI
of this HDLC and its time slots match the peer end.
If yes, go to step 2.
If no, modify HDLC setting and make it accordant with
the peer end HDLC.
2. Check if the physical connection is correct.
If yes, go to step 3.
If no, adjust the physical connection to make it consistent
with the peer end. Check if the alarm is eliminated.
3. Check if the E1/T1 lines have quality problems.
If yes, change the E1/T1 lines. Check if the alarm is
eliminated.
If no, go to step 4.
4. Record the statistic data of messages received by and sent
from the HDLC.
UID unavailable
Alarm Property Alarm code: 198066025
Alarm level: 2
Alarm Cause This alarm is generated when a UID is created. It disappears
when the link gets through.
The link is broken.
Influence All the services on the UID are interrupted.
Handling Flow When at least one HDCL on UID becomes available, the UID can
be used. In this case, the alarm disappears automatically. To
make the HDLC available, follow the suggestions in “HDLC
unavailable.”
Trunk error
Alarm Property Alarm code: 198066045
Alarm level: 2
Alarm Cause The trunk cables are not correctly connected.
Influence The trunk fails to be accessed. All connections based on the
trunk are interrupted.
Handling Flow 1. Check if the E1 lines on the DDF are correctly connected.
Check if the alarm is eliminated.
2. Set the E1 line to loopback at the local side. Check if the
alarm is eliminated.
If the alarm is eliminated, detect the upstream devices
and take the corresponding measure.
If the alarm is not eliminated, go to step 3.
3. Replace the board. End the alarm handling.
Trunk abnormal
Alarm Property Alarm code: 198066046
Alarm level: 2
Alarm Cause Trunk LOF,AIS,or RAI is detected.
Influence The trunk fails to be accessed. All connections based on the
trunk are interrupted.
Handling Flow 1. Check if the grounding of devices is well at both ends.
2. Check if the frame formats at both ends are consistent.
3. Check if impedances match.
HW link broken
Alarm Property Alarm code: 198087101
Alarm level: 3
Alarm Cause BTS internal link breaks.
Influence The BTS cannot work normally.
Handling Flow 1. Reset the board. Check if the alarm is eliminated.
2. Power on the board again. Check if the alarm is eliminated.
3. Check if the backplane jacket matching the board is normal.
If it is abnormal, replace the backplane and then check if
the alarm is eliminated.
If it is normal, replace the module and then check if the
alarm is eliminated.
4. Replace the CMB.
Handling Flow 1. Check if the cables between racks are correctly inserted or
have faults. If faults exist, replace them as soon as possible.
2. Start the self-check of master/slave rack communication.
Determine whether the problem is caused by CMM/CMB
hardware or software fault. Rectify the faults.
If no, go to step 2.
2. Inset the CMM/CMB board tightly and power it on again.
Check if the alarm is eliminated.
3. Start the selfloop test of E1 interface. Check if the result is
normal.
If yes, infer that the fault is rooted in transmission.
Rectify transmission faults.
If no, go to step 4.
4. Change the CMM/CMB board. Check if the alarm is eliminated.
5. Replace the backplane.
Alarm level: 3
Alarm Cause The HDLC link between the CMM and TPU is broken. The CMM
hardware is faulty.
Influence The FUC polling is faulty. No data can be transmitted between
the TPU and CMM. If the data configuration of FUC, CHP, and
CIP cannot complete, their states cannot be reported.
Handling Flow The system can run but data configuration cannot be performed.
If the problem is only that the TPU link is broken for a long time,
use the following method to solve the problem:
1. Check if the TPU board is inserted tightly.
2. Reset the TPU board. Check if the alarm is eliminated.
3. Check if the CMM board works normally.
4. Check if the address switch on the backplane is correct.
5. Check if the transmission lines on the backplane are correctly
connected.
6. Use a HW selfloop test to check whether the fault is rooted in
software or hardware. If the hardware is faulty, replace the
related board. If the software is faulty, modify and upgrade
the software version.
Handling Alarms
Process Instance Configuration Error
Alarm Property Alarm code: 198002562
Alarm level: 2
Alarm Cause The number of instances is modified in the processes whose
instances cannot be configured. For example, the maximum
or minimum instance number of the processes registered as
(1, 1) is modified.
The preset number of process instances is excessive, which
results in insufficient memory.
The configuration of process instances does not observe the
configuration rules, for example, the maximum number of
processes should be greater than or equal to the minimum,
the process instances to be configured should be firstly
registered in the version.
Influence The board startup fails.
Handling Flow Check the configuration table of process instances. Record the
alarm details.
Alarm level: 2
Alarm Cause The subnet mask of OMC gateway read from the OMP database
is inconsistent with that previously saved on the OMP.
Influence The system cannot start normally. This may disable the
communication between foreground and background.
Handling Flow Restart the active and standby OMP boards at the same time.
Check if the alarm is eliminated.
Alarm Cause The preset work mode of external port does not take effect due
to faulty performance of the chip on the local end or
unsuccessful settings on the peer end.
Influence The network interface does not work as the setting.
Handling Flow 1. Check if the work mode on the peer end matches the one set
on the local end.
If yes, go to step 2.
If no, modify the work mode on the peer end to make it
consistent with the one on the local end. Check if the
alarm is eliminated.
2. Check if the work mode at the local end is correctly set. If no,
change it to a correct one and then check if the alarm is
eliminated.
Microcode Is Abnormal
Alarm Property Alarm code: 198015360
Alarm level: 2
Alarm Cause The micro code program is trapped in an endless loop.
Hardware faults of micro engineer leads to exceptional
operation.
Hardware faults of CP or XP leads to exceptional operation.
Influence The board communication link is broken.
The service that the board bears is interrupted.
Handling Flow 1. Restart the board that generates the alarm (board of Release
version starts automatically). After the board is restarted,
check if the alarm is eliminated.
2. Pull out and plug in the board. After the board is restarted,
check if the alarm is eliminated.
3. The board hardware may have fault. Replace the board.
Check if the alarm is eliminated.
PVC Fault
Alarm Property Alarm code: 198018944
Alarm level: 3
Alarm Cause When PVC CC function is enabled, the working status of PVC
becomes non-operating status.
The local end enables CC function, but the peer end does not
enable this function.
Influence The PVC status changes to faulty. The services that the PVC
bears, irrespective of signaling or data, are interrupted.
Handling Flow 1. Check if the optical fibers corresponding to the PVC work
normally.
If no, correctly connect the fibers and then check if the
alarm is eliminated.
If the fibers work normally, go to step 2.
2. Check if the CC function is enabled on the local end but not
on the peer end
If yes, activate the CC function on the peer end so that
the local end can receive CC cells. Send user data from
the peer end, and the peer end can receive the user cell.
You can also deactivate CC detection on the local end.
Check if the alarm is eliminated.
If no, go to step 3.
FE reports unacceptable
configuration parameters(M size)
Alarm Property Alarm code: 198019201
Alarm level: 2
Alarm Cause The near-end IMA group receives unacceptable configuration
message through ICP cells from the far-end IMA group. (M size)
Influence The IMA link is broken.
Handling Flow Check if the parameter configuration of frame length (M size) on
the near end and far end match each other.
Check if the configuration of IMA version on the near end and far
end match each other.
SNTP failure
Alarm Property Alarm code: 198066027
Alarm level: 3
Alarm Cause The NTP server does not exist or it works abnormally.
The IP address of the NTP server in the database is different
from the actual one.
The NTP ser IP address of the NTP server is set to 0 or
0xFFFFFFFF in the database.
The period of synchronization is zero.
Influence The system time may be different.
Handling Flow 1. Check if NTP server exists or if the NTP server works
normally.
If it does not exist or work normally, configure the NTP
server and make it work normally. Issue a command of
NTP time synchronization on the background, and then
check if the alarm is eliminated after 30 seconds.
If it works normally, go to step 2.
2. Check if the IP address of the NTP server configured in the
database is consistent with that of the actual NTP server.
If no, modify the IP address of the NTP server on the
foreground to make it consistent with the actual one and
upload the modified data to the foreground. Alternatively,
modify the IP address of the NTP server to make it
consistent that in the database. Issue a command of NTP
time synchronization on the background, and then check
if the alarm is eliminated after 30 seconds.
If yes, go to step 3.
3. Check if the IP address of the NTP server is set to 0 or
0xFFFFFFFF in the database.
If yes, change it to the actual IP address of the NTP
server and upload the modified data to the foreground.
Check if the alarm is eliminated after 10 seconds.
If no, go to step 5.
4. Record the alarm details.
Remarks Generally, the BSC background checks the data legality before
synchronizing data. Only legal data can be synchronized.
Therefore, this alarm seldom occurs.
L3 Software of FUC No
Response(BTS V2)
Alarm Property Alarm code: 198087219
Alarm level: 4
Alarm Cause The MO software has/has no response temporally (which is
determined by CMM).
Influence The background cannot detect the running status of FUC. Calls,
however, are not affected.
Handling Flow 1. Wait for ten minutes. Check if the alarm is eliminated.
2. If the alarm cannot be eliminated for a long time, pull out
and plug in the FUC when the traffic is low. Reset the FUC
and then check if the alarm is eliminated.
3. Reset the CMM when the traffic is low. Check if the alarm is
eliminated.
4. Replace the TRM/DTRU. Check if the alarm is eliminated.
5. If the alarm is due to software faults, modify and upgrade
the version.
Environment Alarms
Cell delineation do not
synchronization about cell on E1 link
Alarm Property Alarm code: 198001026
Alarm level: 3
Alarm Cause The HEC field of cell header is corrupted, which results in loss of
delineation. This alarm is generally caused by physical layer
faults. It may also be caused by different methods for processing
HECs on local end and peer end devices.
Influence The data receipt fails and the signaling link is broken.
Handling Flow 1. Check if other physical layer alarms exist. If yes, clear the
alarms and then check if this alarm is eliminated.
2. Check if both ends are configured as SDH mode or SONET
mode. If the modes are inconsistent, set them to correct
signaling mode and then check if the alarm is eliminated.
Smoke alarm
Alarm Property Alarm code: 198025866
Alarm level: 3
Alarm Cause The smoke detector detects smoke.
Influence The boards work abnormally.
Handling Flow Check if smoke exists in the equipment room. If yes, dispel the
smoke and then check if the alarm is eliminated.
Infrared alarm
Alarm Property Alarm code: 198025867
Alarm level: 3
Alarm Cause The infrared of the equipment room is higher than the preset
threshold.
Influence The boards work abnormally.
Handling Flow 1. Check if there is any animal around the infrared sensor.
If yes, keep them away from the sensor. Check if the
alarm is eliminated.
If no, go to step 2.
2. Check if the infrared sensor is correctly configured. If no,
modify the configuration and then check if the alarm is
eliminated.
Lightning alarm
Alarm Property Alarm code: 198025868
Alarm level: 3
Alarm Cause The equipment room is influenced by thunderstroke in bad
weather.
Influence The boards work abnormally.
Handling Flow Check if there is lightning hazard. If yes, take protection
measures. Check if the alarm is eliminated.
QoS Alarms
Inter-board Message Communication
Flow Rate Over Alarm Threshold
Alarm Property Alarm code: 198023296
Alarm level: 3
Alarm Cause The system calculates the communication flow rate in a period
and determines if the communication flow rate in input/output
direction of the control panel is more than the alarm threshold.
If it exceeds the threshold, the alarm is generated.
Influence Packets may be lost.
Handling Flow Check if the threshold is reasonable.
Association congested
Alarm Property Alarm code: 198066018
Alarm level: 3
Alarm Cause The service is busy.
The loads among associations are unbalanced.
The association resource is insufficient.
Influence Messages are lost.
Handling Flow 1. Make no manual intervention and just wait the system to
recover. 30 seconds later, check if the alarm is eliminated.
2. Check if the service in process is busy.
If yes, go to step 3.
If no, go to step 4.
3. Check if association resources are sufficient.
If sufficient, check if loads are evenly shared among
associations. If yes, go to step 1. If no, go to step 4.
If insufficient, add new associations and check if this
alarm is eliminated. If no, use the above method for
sufficient link resources.
4. Record the details.
Back up related local office configuration data and peer-
end office configuration data.
Back up related local office and peer-end office history
alarms and notifications, as well as current alarms.
Abbreviations
A
AAL2 ATM Adaptation Layer 2
AAL5 ATM Adaptation Layer type 5
AEM Antenna Equipment Module
AIS Alarm Indication Signal
AIU A Interface Unit
AMR Adaptive Multi Rate
APBE ATM Process Board Enhanced version
APS Automatic Protection Switching
AS Application Server
ASP Application Server Process
ATM Asynchronous Transfer Mode
B
BCSN Backplane of Circuit Switch Network
BCTC Backplane of ConTrol Center
BGSN Backplane of Giga Universal Service Network
BHCA Busy-Hour Call Attempts
BIPB Abis Interface Processing board
GIPI BSC IP Interface board
BIU aBis Interface Unit
BPSN Backplane of Packet Switch Network
BSC Base Station Controller
BSS Base Station System
BSSAP Base Station System Application Part
BSSGP Base Station System EDGE/GPRS Protocol
BTS Base Transceiver Station
BUSN Backplane of Universal Switch Network
C
CAS Channel Associated Signaling
CC Calling Control
CCS Common Channel Signaling
CCS7 Common Channel Signaling System NO.7
CDU Combiner Distribution Unit
CEU Combiner Extension Unit
CHP Channel Processor
CHUB Control plane HUB
CIP Carrier Interface Part
CLKG Clock Generator
CM Communication Management
CMB Control & Maintenance Board
CMM Controller & Maintenance Module
CMP Control Main Processor
CN Core Network
CPU Central Processing Unit
CS Circuit Switch
CSU Channel Service Unit
CU Carrier Unit
D
DBS Data Base Subsystem
DC Direct Current
DCE Data Circuit terminating Equipment
DDF Digital Distribution Frame
DDN Digital Data Network
DFCM Dual -carrier Fan Cortrol Module
DRTB Dual Rate Transcoder Board
DSP Digital Signal Processor
DTB Digital Trunk Board
DTE Data Terminal Equipment
DTRU Dual -carrier Transceiver Unit
DTU Digital Trunk Unit
DTX Discontinuous Transmission
DXC Digital CrosS Connection
E
EAM External Alarm Module
EIPI E1 IP Interface
EIR Equipment Identification Register
EMC ElectroMagnetic Compatibility
EMI Electro Magnetic Interference
ETSI European Telecommunications Standards Institute
ETSN Enhanced TDM Switch Network Board
F
FAM Fan Alarm Module
FCLK Frame Clock
FCM Fan Control Module
FCU Fused Combiner Unit
FDM Fan Driver Module
FE Fast Ethernet
FIB Fast-ethernet Interface Board
FN Frame Number
FNCB Fan Control Board
FNIB Fan Interface Board
FR Frame Relay
FRS Full Rate Service
FSMU Far SubMultiplexing Unit
FUC Frame Unit Controller
G
GERAN GSM/EDGE Radio Access Network
GIPB Gb Interface Processing board
GIPI GE IP Interface
GIU Gb Interface Unit
GLI Gigabit Line Interface
GND GrouND
GNDP GrouND Protection
GPRS General Packet Radio Service
GPS Global Position System
GSM Global System for Mobile Communication
GUIM Gigabit universal Interface Module
GUP GSM Universal Processing board
GUP2 GSM Universal Processing board
H
HBTS Home-BTS
HDLC High-level Data Link Control protocol
HLR Home Location Register
HPI Host Port Interface
HSCSD High Speed Circuit Switched Data
HTRU Home-BTS Transceiver Unit
HW High Way line
I
ICM Integrated Clock Module
IMA Inverse Multiplexing for ATM
IMAB IMA Board
PE Protective Earthing
PLL Phase Locked Loop
PLMN Public Land Mobile Network
PPCH Packet Paging Channel
PS Packet Switch
PSN Packet Switch Network
PSPDN Packet Switched Public Data Network
PSTN Public Switching Telephone Network
PTP Point To Point
PWRD PoWeR Distributor
PWRDB PoWeR Distributor Backplane
Q
QoS Quality of Service
R
RACH Random Access Channel
RBID Rearboard of ID Interface
RCBU Resources board Configuration Basal Unit
RCHB1 Rear board 1 of CHUB
RCHB2 Rear board 2 of CHUB
RCKG1 Rear board 1 of CLKG
RCKG2 Rear board 2 of CLKG
RDI Remote Defect Indication
RDTB Rear Board of DTB
RGER Rear Card of GE for BUSN and BGSN
RGIM1 Rear General Interface Moudle 1
RGUM1 Rear board 1 of GUIM
RGUM2 Rear board 2 of GUIM
RLC Radio Link Control
RMPB Rear board of OMP
RMNIC Rear board of MNIC
RR Radio Resource
RSPB Rear Board of SPB
RSVB Rear board of Server
RTU Radio Transceiver Unit
RUIM1 Rear board 1 of UIM
RUIM2 Rear board 2 of UIM
RUIM3 Rear board 3 of UIM
S
SACCH Slow Associated Control Channel
SAPI Service Access Point Indicator
SAR Segment And Reassemble