Professional Documents
Culture Documents
Version: V6.30.103
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2014 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 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 the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
II
III
IV
VI
VII
VIII
IX
XI
XII
XIII
XIV
XV
XVI
Glossary .......................................................................................................... I
XVII
XVIII
Intended Audience
This manual is intended for:
l Maintenance engineers
l On-duty staff in equipment room
Chapter Description
Appendix A Link Information Describes the complex operations for alarm handling.
II
Fault Indication
The fault management system indicates a fault or event occurring in the network in the
form of alarm or notification.
l A fault is indicated in the form of alarm when it persists and affects the reliability
and services of the system. An alarm will be cleared only after the fault is resolved.
Immediate troubleshooting is required when alarms occur.
l A notification indicates a non-repeatable or instantaneous fault or event in the
system, for example, board reset and signaling overload. Such a fault or event is
normally caused by a sudden environment change or other accidental factors. No
special handling is required because the fault or event causing a notification can be
automatically handled by the system. However, a frequently-reported notification
requires troubleshooting.
Alarm Format
The alarms defined for the ZXG10 iBSCare provided with the information such as property
and possible causes. For details, refer to Table 1-1.
Item Description
Name Summarizes the fault information, such as the fault cause and phenomenon.
1-1
Item Description
Severity There are four alarm severity levels, which are indicated in descending order
of severity as Critical, Major, Minor, and Warning.
l Critical: indicates a fault that causes failures of system operations or
service capabilities. Immediate troubleshooting is required when a critical
alarm is reported.
l Major: indicates a fault that seriously impacts proper system operations or
reduces service capabilities. Clearing the fault to restore the system as
soon as possible is required when a major alarm occurs.
l Minor: indicates a fault that slightly influences proper system operations or
reduces service capabilities. Proper measures should be taken to clear
the fault in a timely manner and prevent the occurrence of more severe
alarms when a major alarm occurs.
l Warning: indicates a fault that has a potential or gradual impact on proper
system operations or service capabilities. Warning messages need to
be analyzed and proper measures should be taken to clear the fault in a
timely manner and avoid more severe alarms.
l Unknown: indicates a fault that severity is defined by users.
The impact degree described in the definition of alarm severity refers to the
impact on a single index, for example, reliability or security. Once the impact
on any index reaches the specified threshold, the severity level of the alarm
can be roughly determined. If an alarm has an impact on multiple indices, its
severity level should be escalated accordingly.
Type Based on the triggering condition and system impact, alarms can be classified
into the following five types:
l Equipment alarm: related with equipment hardware faults.
l Communication alarm: related with information transmission faults (ITU-T
Recommendation X.733).
l Processing error alarm: related with software or processing faults (defined
in ITU-T Recommendation X.733).
l Environment alarm: related with the environment where the equipment is
located (defined in ITU-T Recommendation X.733).
l QoS alarm: related with equipment operation performance or indexes.
Alarm Cause Provides probable alarm causes to help users troubleshoot, find preventive
measures, and restore the system to normal state in a timely manner.
Impact Provides the consequence of each alarm and the impact on the system and
services.
1-2
Item Description
Notification Format
The notifications defined for the ZXG10 iBSC are provided with the information such as
property and possible causes. For details, refer to Table 1-2.
Item Description
Name Summarizes the event information, such as the cause and phenomenon.
Severity There are two alarm severity levels, which are indicated in descending order of
severity as Major, and Minor.
l Major: indicates a fault that seriously impacts proper system operations or
reduces service capabilities. Clearing the fault to restore the system as
soon as possible is required when a major alarm occurs.
l Minor: indicates a fault that slightly influences proper system operations or
reduces service capabilities. Proper measures should be taken to clear
the fault in a timely manner and prevent the occurrence of more severe
alarms when a major alarm occurs.
The impact degree described in the definition of notification severity refers
to the impact on a single index, for example, reliability or security. Once the
impact on any index reaches the specified threshold, the severity level of the
notification can be roughly determined. If a notification has an impact on
multiple indices, its severity level should be escalated accordingly.
Type The notification types are the same as the alarm types.
Notification Cause Provides probable notification causes to help users troubleshoot, find
preventive measures, and restore the system to normal state in a timely
manner.
Impact Provides the consequence of each notification and the impact on the system
and services.
1-3
Item Description
1-4
The complete DN information that can be used for checking or modifying the configuration
data is as follows:
2-1
SubNetwork=1333,MEID=1333,ConfigSet=n,TransportNetwork=1,Ss7=1,LocalSp=1,Re
moteSp=1
Where:
l ConfigSet=0 indicates that the data is in the modification area (used for modifying NE
configuration data).
l ConfigSet=1 indicates that the data is in the snapshot area (used for checking NE
configuration).
Steps
l Querying configuration objects through the GUI
1. From the navigation tree in the Configuration Management window, select
Snapshot Area under the NE node, see Figure 2-1.
2. In the search box, enter the object type name Adjacent Office Information, and
click . See Figure 2-2.
2-2
4. Double-click a configuration object and view its attributes in the displayed tab, see
Figure 2-4.
2-3
Note:
The configuration object MOC is case sensitive.
End of Steps
Steps
l Querying the parent object through the GUI
1. From the navigation tree in the Configuration Management window, select
Snapshot Area under the NE node, see Figure 2-6.
2-4
2. In the search box, enter the object type name 7 Signalling Configuration, and
click . See Figure 2-7.
You can set conditions to quickly find the object, for example, select DN as the
matching condition, like as the matching algorithm, and TransportNetwork=1 as
the matching value, see Figure 2-8.
2-5
4. Double-click the configuration object. Its attributes are shown the displayed tab,
see Figure 2-9.
End of Steps
2-6
Steps
l Querying the referring object through the GUI
1. From the navigation tree in the Configuration Management window, select
Snapshot Area under the NE node, see Figure 2-11.
2. In the search box, enter the object type name Mtp3 Route, and click , See
Figure 2-12.
2-7
You can set conditions to quickly find the object, for example, select DN as the
matching condition, like as the matching algorithm, and Mtp3Route=1 as the
matching value, see Figure 2-13.
4. Double-click the configuration object. Its attributes are shown the displayed tab,
see Figure 2-14.
2-8
3. Drag the horizontal scroll bar to the right and view the Used signalling linkset 1
information.
End of Steps
2-9
Steps
1. Right-click the faulty NE, and select Open Diagram from the shortcut menu.
The board where the alarm is generated blinks in the color corresponding to the alarm
severity. For details, refer to the following table.
Critical
Major
Minor
Warning
2. In the Rank Chart, right-click the faulty board, and select Show Active Alarm from
the shortcut menu, see Figure 2-17.
2-10
Steps
l Querying alarms through the GUI
1. On the Location tab, select the NE Type of the controller, see Figure 2-18.
2-11
2. Select the board where the alarm is generated, see Figure 2-19.
3. Switch to the Alarm Code tab, and select Port trunk failed(199007168), see
Figure 2-20.
2-12
1. In the navigation tree of the MML Terminal, select Fault Management > Show
Active Alarm, see Figure 2-22.
End of Steps
Context
If the office information is available in the alarm details, you can view the office information
by either of the following two methods:
l Alarm list
The office information is available in the corresponding columns in the alarm list, see
the following figure:
2-13
l Additional information
The office information is available in the Additional Information area on the Detail
tab, see the following figure:
Steps
l Fuzzy query
1. On the Others tab, select Remark(Fuzzy Match), and enter 3005 in the text box,
see Figure 2-23.
2-14
2. Click OK. The queried alarm is displayed on the query result tab, see Figure 2-24.
l Advanced query
1. On the Others tab, click Advanced. The Advanced dialog box is displayed.
2. On the Additional Information tab, enter 3005 in the Site ID(Office) text box,
see Figure 2-25.
3. Click OK. The queried alarm is displayed on the query result tab, see Figure 2-24.
End of Steps
2-15
2-16
Code: 198019456
Name: All high-speed links between line card and switching boards are out of
synchronization
Severity: Critical
Alarm Description
All HSSLS between line card and switching boards are out of synchronization
Alarm Cause
1. The configuration of the PSN type is inconsistent with the actual used of PSN type
2. PSN hardware is abnormal.
3. GLI/TLIV hardware is faulty.
3-1
Impact
1. All services on the equipment are down if the alarm is caused by Cause 1 or Cause 2.
2. All services on the line card are affected if the alarm is caused by Cause 3. If the service is not
configured in master/slave or load sharing mode, all services on the line card will be down. If the
service is configured in master/slave or load sharing mode, all services on the line card will soon be
restored after being down temporarily.
Action
1. Check whether PSN board reboots repeatedly. If yes, Check whether the PSN board type
configured is consistent with the PSN board type actually in use.
If inconsistent (for example, the configured board type is PSN4V and the board type actually in use is
PSN8V), modify board type configuration or replace the board actually in use to keep consistency
between board configuration and the board in use.
If consistent, PSN board hardware might be faulty. In this case, replace PSN board.
2. If the alarm occurs in line card, check if the same alarm occurs in other line card(s) located in the
same shelf with the faulty line card.
If the same alarm occurs in all other line cards, PSN board might be faulty. Reboot PSN board and
check if the line card alarms are restored. If alarms are not restored, replace PSN board.
If merely the line card where this alarm occurs reboots repeatedly, replace the board where the
alarm is generated.
Code: 198019465
Severity: Warning
Alarm Description
CSIX RX and TX packets is abnormal, the number of error packets exceeds the threshold
Alarm Cause
Impact
3-2
Action
Code: 198029952
Severity: Major
Alarm Description
Link Fault: The physical layer has determined a fault that occurred in the receive direction of the
local DTE
Dying Gasp: An unrecoverable local failure condition has occurred
Critical Event: An unspecified critical event has occurred
Alarm Cause
Link Fault: The physical layer has determined a fault that occurred in the receive direction of the
local DTE
Dying Gasp: An unrecoverable local failure condition has occurred
Critical Event: An unspecified critical event has occurred
Impact
Link Fault:
The port can't receive data, the operations will interrupt.
Dying Gasp:
The port can't receive data, the operations will interrupt.
Critical Event:
The 802.3ah is failed, can't detect the fault of link.
3-3
Action
Link Fault:
1. Check the peer is or not right.
2. If right, change the optical fiber and check the alarm.
3. If the alarm is alive, change the and check the alarm.
4. If the alarm is alive, change the board.
Dying Gasp:
Check the peer is or not down.
Critical Event:
1. Check the 802.3ah is or not enable, if it is disable, it can't receive PDU.
2. If the 802.3ah is enable, if the port is optical, check the alarm of Link Fault is or not alive, if the
alarm is alive, the port can't receive the PDU
3. Or not, change the good network cable.
4. If the alarm is alive, change the peer board.
Code: 198030208
Severity: Minor
Alarm Description
Alarm Cause
DefXconCCM:
The MAID of the received CCM dose not exactly match the MAID configured in the receiving MEP.
DefErrorCCM:
1. The MEPID in the received CCM is not configured in the receiving MEP.
2. The MEPID in the received CCM matches the MEPID of the receiving MEP.
3. The CCM interval filed in the received CCM dose not match the configured for the receiving MEP.
4. The source mac of CCM is not match the mac of rmep's configured .
DefRemoteCCM:
The MEP is not receiving CCM in timeout.
DefRDICCM:
The MEP is receiving CCM that have the RDI.
AIS:
The MEP is receiving AIS.
3-4
LCK:
The MEP is receiving LCK.
Impact
DefXconCCM:
The configure of MD is error.
DefErrorCCM:
The configure of MEP in MA is error.
DefRemoteCCM:
1. the other mep is not enable.
2. the link is fault, mep can't receive PUD.
DefRDICCM:
The receive of the last MEP is error.
AIS:
The receive of the former MEP is error.
LCK:
The receive of the former MEP is error.
Action
DefXconCCM:
Check the configure of the peer MD.
DefErrorCCM:
Check the configure of all MEP in MA.
DefRemoteCCM:
1. Check the fault of the link
2. Check the other MEP in MA is enabled or not.
DefRDICCM:
Check the alarm of the last MEP.
AIS:
Check the alarm of the former MEP.
LCK:
Check the alarm of the former MEP.
Code: 198005633
Severity: Major
3-5
Alarm Description
Alarm Cause
The ribbon cable is loose or the hard disk fails, usually a hardware failure.
Impact
This is an OMP alarm caused by hard disk breakage, which will affect the system in three ways:
1. The OMP can not boot and services can not access the board.
2. If the log server is abnormal, performance data temporarily stored in the hard disk of the OMP
will be lost.
3. No peripheral board can be powered on because when a peripheral board boots, it will request
for a version from the OMP.
Action
Replace the fault hard disk or replace the board, where the hard disk is installed.
Code: 198005635
Severity: Major
Alarm Description
ENUM is open
Alarm Cause
Impact
The active/standby board changeover or the APS changeover will fail. This board can not be
switched to the active board.
3-6
Action
Code: 198005639
Severity: Major
Alarm Description
Alarm Cause
The fiber is not completed connected to the port, or is damaged, or is not compatible with the optical
transceiver module in T-network switch. There is no light signal input into the optics module.
This alarm is dedicated to the TDM optical port only. The possible causes of this alarm include:
1. TDM receiver fiber optics failure, fiber optics module failure.
This type of failures include: damaged fiber on the receiver, unconnected fiber, contaminated fiber or
damaged optics module on the receiver.
2. Fiber optics failure at the transmitting module on the corresponding TDM.
This type of failures include: damaged fiber on the transmitter, unconnected fiber, and contaminated
fiber.
3. Compatibility between fiber optics and optics module.
The fiber transmission rate of TDM signal is incompatible with the wave length of the optics module.
4. Loss of signal (LOS) alarm operation is performed on the corresponding SDH device.
This includes the manual diagnosis test alarm operation.
Impact
There might be error in the data transmitted by the optical port which affects the quality of all the
services performed on this optical port.
3-7
Action
1. Perform loopback test to determine source of this alarm is on the local devices or the corresponding
devices. Perform self-loop test on local device. If the failure persists, the failure source is on local
device; if the failure disappears after self-loop test, then the source of failure is on the corresponding
device. Contact the corresponding device for solution.
2. Replace optics module.
3. Replace the fibber optics.
4. Replace the board.
Code: 198005640
Severity: Major
Alarm Description
Alarm Cause
FPGA runs abnormally, for example, FPGA is lost, or the board clock is lost.
Impact
Action
1. Restart the board. In this case, the board downloads FPGA again.
2. Replace the board.
3-8
Code: 198005644
Severity: Major
Alarm Description
Alarm Cause
Impact
The sub-card channel is not initialized or the initialization fails. As a result, the channel corresponding
to the alarm chip cannot be used normally. This affects the service carried by the board of the
sub-card. After the channel is available and the alarm is eliminated, the service is recovered.
Action
1. Unplug and plug the sub-card again. Wait for the board to be powered on.
2. Replace the sub-card.
Code: 198005645
Severity: Minor
Alarm Description
Subcard abnormal
3-9
Alarm Cause
Impact
UIMC/GUIM/CHUB GCS sub-card functions abnormally. Packets may be lost, and even worse, link
disconnection may occur on the control planes of some boards. For active/standby configuration,
there are two cases:
1. If the active board is abnormal while the standby board is normal, the system performs
active/standby switchover. Thus, the standby board takes over the services of the faulty active
board. In this case, the service is not affected.
2. If both the active and standby boards are abnormal, active/standby switchover is forbidden. In this
case, the service is interrupted because the faulty board cannot restore to the normal status.
Action
1. Check the sub-card connection on the board. If the sub-card is loosely inserted, tightly insert it and
wait for the board to be powered on.
2. Replace the sub-card.
Code: 198005646
Severity: Critical
Alarm Description
Alarm Cause
3-10
Impact
The service clock and system clock are inconsistent on the board with unlocked phase-lock loop. As
a result, the service carried by the board is interrupted.
Action
1. On NMS fault management interface, check if the related clock alarm occur. If yes, handle the
alarm by referring to the corresponding suggestions.
The related alarm is as follows:
198005381 Input Clock Abnormal
2. On NMS fault management interface, check if related alarms occur on the optical port for clock
extraction. If yes, handle the alarm by referring to the corresponding suggestions.
The related alarms are as follows:
198001792 SDH/SONET fault
198005639 High Error Rate of Optical Interface
198000002 Loss of Optical Transceiver Module Signal
3. Check the operation and maintenance logs. If the operation of changing the clock extraction
reference for the loop is recorded, report the alarm as a normal phenomenon. In this case, no
handling operation is required.
4. Switch to the standby clock board.
5. Switch to the standby UIM/GUIM board.
6. Replace the board.
Code: 198005647
Severity: Major
Alarm Description
Alarm Cause
3-11
Impact
The trunk fails to receive trunk signals. If the belonged port has only this link, all services on the port
are interrupted. Otherwise, only the port bandwidth is affected. The quantity of upper layer access
services associated with the port is decreased. The accessed bandwidth is reduced. The service,
however, is not interrupted.
Action
1. Conduct a meter measurement or loopback test to find out whether the alarm is rooted in the
local end or peer end.
Meter measurement: Connect a trunk test meter to check if the signal received by the local end trunk
is normal. If yes, the fault is rooted in the local end. If the test shows the problem persists, the fault is
rooted in the peer end. In this case, inform the peer end to troubleshoot.
Loopback test: Perform self-loop at the trunk where alarm occurs at local end. If the problem persists,
it indicates that the fault is rooted in the local end. If the alarm is eliminated, it indicates that the alarm
is rooted in the peer end. In this case, inform the peer end to troubleshoot.
2. Replace the trunk cable.
3. Replace the board.
Code: 198005656
Severity: Major
Alarm Description
Alarm Cause
3-12
Impact
The unavailable sub-card clock affects the normal operation of the board. This may cause clock
jittering, and the service that implements media stream exchange through this board becomes
unstable. In the most serious case, the system clock is lost and the service carried by the board is
interrupted.
Action
1. Check the subcard connection status. If the subcard is loose, tightly connect it and power it
on again.
2. Replace the subcard
3. Replace the board.
Code: 198005663
Severity: Major
Alarm Description
Alarm Cause
Impact
This alarm only occurs to the IMAB. When it occurs, the IMAB can not operate normally and the trunk
borne on the board will be broken. As a result, users can not access the board and the existing
services will be interrupted.
Action
1. Check whether the 'Board input clock lose' or 'PLL unlock' alarm exists. If so, handle the alarm first.
2. Replace the board.
3-13
Code: 198005665
Severity: Critical
Alarm Description
Alarm Cause
Impact
Be usually determined as hardware fault, which affects system clock. It might lead to the system
clock loss and system synchronization failure.
When system clock loss/offset occurs, its subsequent impact on service is described below.
1.For TDM transmission, all links based on the TDM transmission medium (including the transmission
link currently in service for UE and cell transmission link) are affected. Packet loss might occur on
these links, leading to degradation of service quality. In the case of serious packet loss, service
interruption and handover failure will occur. Even worse, the cell might be out of service.
2.For non-TDM transmission (for example, IP transmission), Iub interface service is affected, while
Iur interface and Iu interface services are not affected. The clock that Node B derives from RNC
via IEEE1588 is inaccurate.
When RNC clock frequency offset is no more than 0.05 ppm, Node B synchronization will not fail, but
success rate of inter-RNC inter-Node B soft handover might fall.
When RNC clock frequency offset exceeds 0.5 ppm, Node B will fail to lock the clock. In this case,
Node B will oscillate freely and success rate of inter-Node B soft handover might fall.
3-14
Action
On NMS fault management interface, view alarm Details where Error type information is given.
Locate the corresponding alarm handling suggestion according to the error type.
The alarm handling suggestions that correspond to the error types are described below.
1.Type A Fault on Board (GPS) Phase-lock Equipment
1) On NMS test management interface, perform diagnostic test on ICM board. Check the working
status of the GPS module. If Class A fault persists in the GPS module, replace the board.
2) Check if output clock loss occurs. If yes, replace the board.
2.Phase-lock Equipment of This Board (GPS) Is in Power-on Status
If the alarm persists, hardware fault might exist. Replace the board.
Code: 198000256
Severity: Minor
Alarm Description
Alarm Cause
1. No network cable is connected with Network Port OMC or OMC2 on rear board of OMP.
2. Network cable is disconnected or cable connector is loose.
3. Network port on the board is faulty.
Impact
Action
1. Ensure that the network cable connected to Network Port OMC or OMC2 is connected firmly
and correctly on the both end.
2. Unplug and plug the network cable on Network Port OMC or OMC2 of OMP board
3. Check if OMC or OMC2 network cable works normally. If no, replace the cable.
3-15
Code: 198001284
Name: The phase of 8K, 16K clock, input to backplane board, is not matched
Severity: Minor
Alarm Description
The phase of 8K, 16M clock, input to backplane board, is not matched
Alarm Cause
Impact
The system fails to achieve synchronization so that the board can not work normally. As a result, UE
can not be accessed and services borne on the board are interrupted.
Action
1. Check the clock input cable and ensure that the cable is good and well connected.
2. Clock board changeover.
3. UIM/GUIM board changeover.
4. Replace the board which reported alarm.
Code: 198001286
Severity: Minor
Alarm Description
3-16
Alarm Cause
Impact
The board fails to synchronize with system clock so that it can not work normally. As a result, UE can
not be accessed and services borne on the board are interrupted.
Action
1. Check if the clock (input) cable at the shelf is intact and properly connected.
2. Check if the following alarm occurs in the board. If yes, refer to the corresponding alarm handling
suggestion.
Related alarm: 198005635 The board is not plugged firmly
3. Replace board.
Code: 198000002
Severity: Minor
Alarm Description
Alarm Cause
3-17
Impact
The optical interface fails to work normally. If the optical interface is configured with APS protection,
service will be switched to protection optical interface. Otherwise, all services on the optical interface
will be down.
Action
1. Carry out loop test to determine whether the alarm is caused by local end or opposite end. Perform
fiber self-loop at local equipment. If the alarm persists, fault might lie in local equipment. If the alarm
disappears, inform the opposite end to troubleshoot.
2. Replace the optical module.
3. Replace fiber.
4. Replace board.
Code: 198001792
Severity: Major
Alarm Description
When the power of the receiving-optical signaling is lower than the sensitivity of the optical receiver,
the LOS alarm occurs. When the LOS alarm occurs, the board inserts "110" between bit 6 and bit 8
of the multiplexing section overhead (MSOH) K2 on the sending side, via, send the MS RDI to
each other.
3-18
Alarm Cause
The alarm occurs when the receiving optical power is below optical receiver sensitivity. Generally
speaking, normal receiving optical power range for optical modules is between -28 dBm and -8 dBm.
Optical signals within this range can be detected.
Probable causes for the alarm include:
1. The receiving optical fiber/module of local SDH equipment is faulty.
Receiving optical fiber is faulty or disconnected.
Optical connector is polluted.
Receiving optical module is faulty.
2. The transmitting optical fiber of opposite SDH equipment is faulty.
Transmitting optical fiber is faulty or disconnected.
Optical connector is polluted.
3. The optical transmission line of SDH equipment is faulty.
Tail fiber and flange between fiber distribution frame and the equipment at local end are faulty
or disconnected.
The related connector is in poor contact.
4. The receiving optical power at local end is excessively low.
Optical power attenuation on the fiber transmission line at receiving end is too much.
Opposite-end transmitting optical power is too low.
5. Operation of LOS insertion is performed at opposite end.
Manual operation of LOS insertion is performed in diagnostic test, and optical module is shutdown by
force.
6. Optical fiber and optical module is incompatible.
The fiber transmission rate of STM signals and the optical module wavelength are incompatible.
Impact
SDH/SONET fails to work normally, leading to UE access failure on SDH/SONET and interruption
of ongoing services.
Action
1. Use meter measurement or loop test to judge whether the alarm is caused by local end or
opposite end.
Meter Measurement
Use a SDH test meter or optical power meter to test whether the receiving optical signals at local end
are normal. If normal, fault might lie in local equipment. If abnormal, fault lies in opposite end or on
transmission side. Inform the opposite end or transmission side to troubleshoot.
Loop Test
Perform fiber self-loop at local SDH equipment. If the alarm persists, fault might lie in local equipment.
If the alarm disappears, inform the opposite end to troubleshoot.
If it is a local fault, go on with the following steps.
2. Replace optical module.
3. Replace optical fiber.
4. Replace board.
3-19
Code: 198001825
Severity: Warning
Alarm Description
Alarm Cause
Impact
SDH/SONET equipment can work. However, call loss or noise occurs to all voice services on this
optical path, and bit error occurs on the data service channel.
Action
1. Use meter measurement or loop test to judge whether the alarm is caused by local end or
opposite end.
Meter Measurement
Use a SDH test meter or optical power meter to test whether the receiving optical signals at local end
are normal. If normal, fault might lie in local equipment. If abnormal, fault lies in opposite end or on
transmission side. Inform the opposite end or transmission side to troubleshoot.
Loop Test
Perform fiber self-loop at local SDH equipment. If the alarm persists, fault might lie in local equipment.
If the alarm disappears, inform the opposite end to troubleshoot.
If it is a local fault, go on with the following steps.
2. Replace optical module.
3. Replace optical fiber.
4. Replace board.
3-20
Code: 198015874
Severity: Major
Alarm Description
A link level flow control occurred in 2400 during specified time and could not be recovered.
Alarm Cause
Impact
The services carried by the board are unstable. In most serious case, all services carried by the
board are interrupted.
Action
1. On NMS fault management interface, check if the PSN in the same shelf has generated related
alarms. If yes, follow the suggestions on handling the related alarms.
The related alarm is as follows:
198019456 All high-speed links between line card and package switching board are out of
synchronism
2. Unplug and plug the board.
3. Replace the board.
Code: 198015875
Severity: Minor
3-21
Alarm Description
The number of dropped packets is over the threshold due to lookup critical table failure
Alarm Cause
Impact
Packets would be dropped which would cause poor voice quality and other problems.
Action
Switch the master port of the GLI board (where table lookup failed) to the partner board
Code: 198015876
Severity: Minor
Alarm Description
Alarm Cause
Impact
Packets would be dropped which would cause poor voice quality and other problems.
Action
3-22
Code: 198015877
Severity: Minor
Alarm Description
Alarm Cause
Impact
Packets would be dropped which would cause poor voice quality and other problems.
Action
Code: 198002560
Severity: Major
Alarm Description
3-23
Alarm Cause
Impact
CPU occupancy indicates the current status of system operation. CPU overloaded, or over high
occupancy, is usually caused by service or operation that consume much time.
It has the following impact on the system:
Services with low priority level have little or no access to the processing of CPU, which reduces
processing speed of the services or even halts the processing.
System board could reset under excessively overloading conditions, causing interruption to the
service it performs.
Action
1. Open the rack map on the Configuration Management window, select Board, right click and select
Board Property. Check the CPU overload threshold setting on the CPU Information tab. Please reset
CPU overload threshold if the CPU overload threshold value is too low. It will take 30 seconds for
the new setting to take effect.
Recommended threshold value: 80% for low level load threshold, 90% for high level load threshold.
2. Check for the record of data synchronization, data saving or other file operations in the network
manager log files. Those operations might increase the CPU utilization rate radically, and it might
take 2 minutes.
3. Check for the record of new board added or version upgrade operation in the network manager
log files. Version upgrading operation might increase CPU utilization rate radically, and it might
take 2 minutes.
Code: 198002561
Severity: Major
Alarm Description
3-24
Alarm Cause
1. Fan faulty.
2. High temperature in rack.
3. CPU overload.
Impact
Action
1. In NMS Configuration Management interface, click Rack. Right click the concerned board >
Show Board Properties Page > CPU1 or CPU2. Check 2 parameters: Low/High threshold of alarm
temperature, Reset temperature. If the settings are low, please adjust the High threshold of alarm
temperature and the Reset temperature. The new settings will be valid after 30 seconds.
Recommended Thresholds: High threshold of alarm temperature: 90 degrees Celsius, Reset
temperature: 95 degrees Celsius.
2. Observe the thermometer in machine room to know room temperature. If it is high, please take
effective measures to cool down.
3. Check the surface of the boards. Does it have much dust? If yes, please clean it for better cooling.
4. Check the air intake and air outlet of the rack. Does it have much dust? If yes, please clean it
for better ventilation.
5. Make sure the fan(s) on the rack works normally.
6. Replace the fault board.
Code: 198025602
Severity: Minor
Alarm Description
Alarm Cause
3-25
Impact
The link with abnormal connection is interrupted. Accordingly, services are affected.
Action
1. In NMS Configuration Management interface, view the configuration of IMA links. Do the values of
HW and TS fields configured for IMA links conflict (for example, two A ends are configured with the
same B end). If yes, modify the configuration.
2. Replace the faulty board.
Code: 198005376
Severity: Major
Alarm Description
Alarm Cause
Impact
Because internal media stream can not be transmitted via this port, it will select another port for
transmission. If all the internal ports are abnormal, the internal media stream will be interrupted and
all the services provided on this board will be interrupted.
3-26
Action
1. Check the Alarm Management window for the CUP overloaded on the first level switching board,
UIM board at the shelf, or local board. Perform recommended solution to process the alarm(s) if any.
Related Alarm: 198002560 Board CPU Overloaded
2. Check the Alarm Management window for the alarms of Inter-shelf media plane links abnormal.
Perform the recommended solution to process the alarm(s) if any.
Related Alarm: 198005121 Inter-shelf Media Plane Link Error
3. Replace the board.
4. Change the slot of the board.
5. Replace the UIM in the same shelf.
Code: 198066070
Severity: Major
Alarm Description
Alarm Cause
Impact
If the board is normal, but its in-position indicator has a fault, then this alarm does not affect services.
The board is in blocked status, no services can be accessed. If the board acts as a resource board,
its resources can not be used.
Action
3-27
Code: 198005381
Severity: Critical
Alarm Description
Alarm Cause
Impact
The services are interrupted because the system can not get a proper clock.
Action
1. Reconnect the cable between the board and the clock reference (the previous level).
2. Replace the cable between the board and the clock reference.
3. Check the signal output from the reference clock source.
4. Replace the board.
Code: 198005389
Severity: Warning
Alarm Description
3-28
Alarm Cause
1. Configuration is incorrect.
2. Board is misplaced.
Impact
Since the board where the unconfigured sub card is located resets repeatedly, power resource of
the equipment is wasted. However, services won't be affected.
Action
Code: 198005390
Name: CPU sub card is missing from slot but is configured in database
Severity: Major
Alarm Description
Alarm Cause
Impact
The sub-card functions are unavailable, accordingly this board does not support relevant services.
The influence on the system is various according to different type of sub-card.
If the sub-card is an interface board, the transmission link via this board is not connectable, then
services will be accessed through other sub-card. If the sub-card is a signalling process board,
the cell/Node B configured for this board is not available for services. If the sub-card is a user's
plane board, user plane process capability will decline, then services will be accessed through
other sub-card.
3-29
Action
Is the sub-card required? If no, modify the type of board so that the new type doesn't support such
sub-card; if yes, insert the sub-card firmly.
Code: 198005395
Severity: Major
Alarm Description
Alarm Cause
Impact
This port is not available for services. If there is a standby port, data can be received or transmitted
via the standby port. But in this case, totally data throughput will decline. Meanwhile, the reliability
and stability of the system declines. If there is no standby port, all communication links via this port
will be broken, and the services carried via this port will be interrupted.
Action
3-30
Code: 198005396
Severity: Major
Alarm Description
Alarm Cause
Impact
If the internal media plane stream can not be processed, packets may be lost. In this case, services
provided by this board become unstable.
If it is port fault or connector fault, the internal media plane is completely broken. In this case, services
borne on this board are interrupted.
If either CPU or traffic is overloaded, services carried on the board will be delayed. In serious
situation, services may be interrupted.
Action
1. Check the Alarm Management window for the alarms of Inter-shelf media plane links abnormal.
Perform the recommended solution to process the alarm(s) if any.
Related Alarm: 198005376 internal media plane port failure.
2. Check the Alarm Management window for the CUP overloaded on the first level switching board,
UIM board at the shelf, or local board. Perform recommended solution to process the alarm(s) if any.
Related Alarm: 198002560 Board CPU Overloaded
3. Check the Alarm Management window for the alarms of Inter-shelf media plane links abnormal.
Perform the recommended solution to process the alarm(s) if any.
Related Alarm: 198005121 Inter-shelf Media Plane Link Error
4. Replace the board.
5. Change the slot of the board.
3-31
Code: 198005399
Severity: Major
Alarm Description
The state should be reported to the DBS and blocked in the DBS when Dsp resources is not
available.(such as broken)
Alarm Cause
This alarm indicates DSP resource is not available. It is monitored by higher-level layer. Once DSP is
blocked, an alarm is given. This includes the following situations:
1. DSP version fails to be loaded so that the system is unable to operate normally.
2. The HPI port on DSP is abnormal.
3. The DSP media plane communication is disconnected.
4. DSP resets.
Impact
All services processed by this DSP are interrupted, and those services will be re-created on other
normal DSPs. If the DSP is unavailable for a long time, system performance will be degraded.
Action
1. In network management system, check the operation & maintenance log file. Is there a record,
indicating DSP version replacing? If yes, this operation must cause DSP to reset. And having this
alarm is a normal phenomenon. No handling is required. Please wait until DSP reset is complete.
2. In Alarm Management interface, check whether there is one of the following alarms. If yes, please
solve the problem according to corresponding handling suggestions.
Related Alarms:
198005701 Version Load Error
198005655 DSP auto-detection abnormal
198005700 DSP abnormally resets
3. Reset the board.
4. Replace the board.
3-32
Code: 198005403
Severity: Major
Alarm Description
Board's hardware faults occur in SRAM self-check during the process of system power on
Alarm Cause
Impact
Action
Code: 198005404
Severity: Major
Alarm Description
Alarm Cause
3-33
Impact
Action
Code: 198005405
Severity: Major
Alarm Description
Alarm Cause
Impact
Action
Code: 198026116
3-34
Severity: Major
Alarm Description
Alarm Cause
Hardware is faulty.
Impact
1. If it is caused by the master clock board, the system will fail to get clock. Because of this, all
clock-related boards can not work normally and services will be interrupted. The relevant boards
include IMA protocol processing board and interface board with HW process capability.
2. If it is caused by the slave clock board, services will not be affected.
Action
1. If the alarm is reported by master board rather than slave board, perform master/slave switching.
2. Replace the board where the alarm is reported.
Code: 198026117
Severity: Major
Alarm Description
Alarm Cause
Hardware is faulty.
Impact
The system can not get wanted clock, therefore all clock-related processes are abnormal.
3-35
Action
1. If the board where the alarm is declared is ICM, please replace the board.
2. If the board where the alarm is declared is CLKG:
Check the connection between CLKG and GCM.
Replace the CLKG.
Replace the GCM.
Code: 198026118
Severity: Major
Alarm Description
Alarm Cause
Hardware is faulty.
Impact
The system can not get wanted clock, therefore all clock-related processes are abnormal.
Action
Code: 198026127
Severity: Minor
3-36
Alarm Description
Alarm Cause
Impact
When all configured clock reference sources are lost, the clock board comes to free running or
hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board.
No impact on service.
Action
Code: 198026128
Severity: Major
Alarm Description
Alarm Cause
Input clock reference is in unavailable status for more than 10 minutes and less than 24 hours.
Probable causes include:
1. Clock reference input is abnormal.
2. The configured clock reference does not exist.
3-37
Impact
When all configured clock reference sources are lost, the clock board comes to free running or
hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board.
The clock loss leads to synchronization failure between system clock and clock reference source.
Service interruption might occur.
The system will not be affected if the following two events happen together.
Input clock reference source is lost.
The phase-locked loop locks other clock reference source.
Action
Code: 198026129
Severity: Critical
Alarm Description
Alarm Cause
3-38
Impact
When all configured clock reference sources are lost, the clock board comes to free running or
hold-over state. Accuracy of output clock is determined by the crystal oscillator of clock board.
The clock loss leads to synchronization failure between system clock and clock reference source.
Service interruption will occur.
The system will not be affected if the following two events happen together.
Input clock reference source is lost.
The phase-locked loop locks other clock reference source.
Action
Code: 198026131
Severity: Minor
Alarm Description
Alarm Cause
Impact
System could not get the needed clock, which will cause processing abnormity related to the clock.
Action
1. If the alarm is reported by the master board, and the slave board is good, perform master/slave
changeover operation.
2. Replace the fault board.
3-39
Code: 198026133
Severity: Major
Alarm Description
Alarm Cause
Hardware is faulty.
Impact
1. If this alarm occurs on the master board, system clock synchronization will fail and services will
be interrupted.
2. If this alarm occurs on the slave board, services will not be affected.
Action
1. If the alarm is declared by master board rather than slave board, perform master/slave switching.
2. Replace board.
Code: 198005632
Severity: Major
Alarm Description
Hard disk usage rate exceeds one of the thresholds. There are three kinds of threshold about this
alarm.
3-40
Alarm Cause
Impact
When hard disk usage rate exceeds its threshold, new data can not be written. The data may be
lost. There is no impact on services.
Action
1. In NMS configuration management interface, click MPX86 or MPX86/2 alarm parameters > hard
disk full alarm to check the threshold used to report a hard disk usage alarm. If the threshold value is
low, please increase it.
2. Clean the space of hard disk. Delete the files that are no longer used, or move them to external
storage devices.
3.1.49 198005637 Back card does not match with front board
Alarm Information
Code: 198005637
Severity: Minor
Alarm Description
Back card error. Back card and frontal board do not match
Alarm Cause
Impact
1. When the rear board interface is used to connect other network element, it will cause link
interruption at bottom layer, and services over the corresponding link will be interrupted.
2. When the rear board interface is used to connect internal control plane, it will cause communication
error at internal control plane. As a result, the board can not exchange control plane messages and
services borne on the board will be interrupted.
3. When the rear board interface of clock board is used to extract clock, it will cause loss of clock
signal. Because without input clock, the system services will be interrupted.
3-41
Action
1. Check the front board type for the correct rear board type, and use the correct rear board.
2. Replace the defective rear board with a new rear board.
Code: 198005661
Severity: Warning
Alarm Description
Alarm Cause
Impact
The APS optical port data on the standby board cannot reach the active board. When the active
optical port is normal, the service is not affected. When the active optical port is faulty, APS fails to
protect optical port and thus all services carried by the optical port are interrupted.
Action
Code: 198005662
3-42
Severity: Warning
Alarm Description
Alarm Cause
Impact
When hard disk work for long time without sleep, engine will be in high speed spin state for long, this
will influence the life of disk, and data will lose when disk be abnormal.
Disk of some model will lock the engine when it keep work for long time to protect the disk. But this is
out of the software controled, and may result in data lose when disk cannot be accessed transitorily.
Action
No handling is necessary.
Code: 198005667
Severity: Minor
Alarm Description
Loop E1 alarm
Alarm Cause
3-43
Impact
Data can not be sent out because of the loopback E1.
Action
1. Disconnect the loopback E1.
2. Restart the board.
3. Replace the board.
4. Replace the opposite board.
Severity: Minor
Alarm Description
Cross-linked E1 alarm
Alarm Cause
Self board has cross-linked E1.
Impact
Data can not be sent out because of cross-linked E1.
Action
1. Disconnect the cross-linked E1, Wait for 1 minute and check whether the alarm disappears.
2. Restart the board and check whether the alarm disappears.
3. Replace the board by another one and check whether the alarm disappears.
4. Replace the board connected with this board, check whether the alarm disappears.
3-44
Severity: Critical
Alarm Description
Alarm Cause
Synchronization status check of FPGA and SPI4/VSC872/VSC874 failed. It's usually caused by
hardware exceptions. For example, the clock chip works abnormally.
Impact
If synchronization status check of FPGA fail, Media can not receive or send data normally. And the
board will reset for the exception of the media check frame.
Action
Code: 198005671
Name: Sending or receiving packets using the cascade ports inner board failed
Severity: Critical
Alarm Description
Sending or receiving packets using the cascade ports inner board failed
Alarm Cause
3-45
Impact
Cascade ports inner UIMC/GUIM/GUIM2/CHUB functions abnormally. Packets may be lost, and even
worse, link disconnection may occur on the control planes of some boards. For active/standby
configuration, there are two cases:
1. If the active board is abnormal while the standby board is normal, the system performs
active/standby switchover. Thus, the standby board takes over the services of the faulty active
board. In this case, the service is not affected.
2. If both the active and standby boards are abnormal, active/standby switchover is forbidden. In this
case, the service is interrupted because the faulty board cannot restore to the normal status.
Action
1. Check the GCS subcard connection on the board. If the subcard is loosely inserted, tightly insert it
and wait for the board to be powered on.
2. Replace the GCS subcard.
3. Replace the UIM2/GUIM/GUIM2/CHUB board.
Code: 198005655
Severity: Major
Alarm Description
Alarm Cause
Impact
This DSP will be blocked and no longer available. The cell of this DSP is out of service; the subscriber
using this DSP is out of service; call loss rate might increase when call traffic is high.
3-46
Action
Code: 198019712
Severity: Major
Alarm Description
Alarm Cause
Impact
APS automatic protection switching function is paralyzed. When the working optical port is abnormal,
the protection optical port will not work, leading to service interruption on this optical port.
Action
3-47
Check APS protection direction (unidirectional or bidirectional) configured at local end. Ensure
configuration consistency at both ends.
On NMS configuration management interface, locate the relevant board in the rack. Right-Click the
board and open board properties page. Click Optical port APS protection to view the "Protection
Direct" (unidirectional or bidirectional).
4. Check whether APS is supported by the opposite equipment. Check whether APS configuration is
correct and has taken effect.
Code: 198019713
Severity: Major
Alarm Description
Alarm Cause
Impact
1. When fibber connection is correct and the working optical port can work normally, services won't
be affected.
2. When the working optical port is faulty, APS automatic protection switching function doesn't work,
and services carried via this optical port will be interrupted due to lack of protection.
Action
3-48
On NMS configuration management interface, locate the relevant board in the rack. Right-Click the
board and open board properties page. Click Optical port APS protection to view the "Protection
Type" (1+1 or 1:1).
3. Check APS protection direction at both ends.
Check APS protection direction (unidirectional or bidirectional) configured at local end. Ensure
configuration consistency at both ends.
On NMS configuration management interface, locate the relevant board in the rack. Right-Click the
board and open board properties page. Click Optical port APS protection to view the "Protection
Direct" (unidirectional or bidirectional).
Code: 198019714
Severity: Major
Alarm Description
Alarm Cause
Impact
The board can not enter into normal working status. All board services fail to be established.
Action
1. If board backup mode is configured as 1:1 or 1+1 and SDH optical interface is needed, at least one
set of APS protection needs to be configured.
To configure APS protection:
On NMS configuration management interface, locate the relevant board in the rack. Right-Click the
board and open board properties page. Click Optical port APS protection.
2. If board master/slave mode is not needed, modify board backup mode into.
To configure board backup mode:
Delete the relevant board on NMS configuration management interface. Then recreate the board.
Select board backup mode as "None" during board creation.
3. If board backup mode is configured as 1:1 and no SDH optical interface is required, modify the
board backup mode into 1+1.
3-49
Code: 198005121
Severity: Minor
Alarm Description
Ge routing is abnormal
Alarm Cause
1. The fiber connection is error between shelves, or the fiber is not physically plugged.
2. The background configuration of the board is inconsistent with its foreground physical connection.
3. The transceiver of the board link detection packet is exceptional.
Impact
The inter-shelf service bandwidth is reduced. The inter-shelf services may be interrupted if no
backup is configured.
Action
1. In the NMS Configuration Management interface, select Unit Connection Relation, then compare
the configuration with actual physical connection. If it is different, adjust connection cables according
to the configuration.
2. Check the connection of optical fiber and make sure it is in cross connection. Is there any relevant
alarm? If yes, please solve the problem according to recommended handling suggestions.
Relevant Alarm: 198005125 GE optical transceiver module is wrongly connected to left/right board
slots at opposite end
3. Replace the optical fiber or the optical transceiver module so that the SD indicator for the
corresponding port is on.
4. Replace the local board.
5. Replace the opposite board.
3-50
Code: 198005124
Severity: Minor
Alarm Description
Alarm Cause
1. Connection failure.
2. Line failure.
3. Board failure.
4. Rear board failure.
Impact
There is no impact on services when TRUNK connection is not adopted for inter-shelf control plane
communication. However if TRUNK connection is adopted, this alarm indicates insufficient network
communication capability. This may cause congestion at control plane. During heavy traffic period,
this may cause much delay or services interruption in extreme condition.
Action
1. Check whether TRUNK connection is used for inter-shelf control plane. If not, no handling
is required.
2. Check the number of connections, i.e. 4 FEs and 2 GEs are required. Complete the connections if
there is any missing.
3. Check whether the connection is correct.
The correct connection is described as below:
For FE port trunk, if UIM board is installed on BUSN shelf, then TRUNK connection is not supported.
In this case, this alarm won't occur. If UIM is installed on other shelf, FE7, FE8, FE9 and FE10
work together to form a TRUNK port. However if it is GUIM/GUIM2 board, FE3, FE4, FE5 and FE6
form a TRUNK port.
For CHUB board, every 4 adjacent FE ports form a TRUNK port, such as FE1~FE4, FE5~FE8 etc.
For each trunk port, All the 4 RE ports must be connected, and direct connection is recommended.
For GE port trunk, 2 GE interfaces (CHUB board inter-connection) are connected in cross-connection
mode. The #1 GE port on the left board on the local shelf corresponds to the #1 GE port on the left
board on the opposite shelf; the #2 GE port on the left board on the local shelf corresponds to the #2
GE port on the right board of opposite shelf.
3-51
The #1 GE port on the right board on the local shelf corresponds to the #2 GE port on the left board
on the opposite shelf, and the #2 GE port on the left board on the local shelf corresponds to the #2
GE port on the right board on the opposite shelf.
4. Replace the cable.
5. Replace the rear board.
6. Replace the connected board.
Code: 198005125
Severity: Minor
Alarm Description
Alarm Cause
Impact
Action
Code: 198005893
Severity: Critical
3-52
Alarm Description
Alarm Cause
Impact
Action
Code: 198005650
Severity: Critical
Alarm Description
Alarm Cause
Impact
The board fails to start up, or control plane communication is abnormal. As a result, users cannot
gain access and existing services are interrupted.
3-53
Action
1. Check whether the DIP switch setting is changed or the board is not restarted after the change.
2. Plug and unplug the board and then check if the alarm is eliminated.
Code: 198005672
Severity: Major
Alarm Description
Synchronization Ethernet clock source is unusable, the slave clock port can not synchronize with the
connected port.
Alarm Cause
1. The slave clock port does not receive ESMC PDU for 5 seconds.
2. The SSM value that the slave clock port received is DNU.
3. The port speed is 10M.
4. Physical link of the port is broken.
Impact
The slave clock port can not synchronize with the connected port, which will cause processing
abnormity related to the clock.
Action
1. Check the synchronization Ethernet's master/slave clock configuration of the connected port,
the configuration should be master;
2. Check local and connected port speed, port speed should not be 10M;
3. Check if the physical connection is correct.
3-54
Code: 198015878
Severity: Major
Alarm Description
The number of dropped frames is over threshold due to internal fabric port receive error
Alarm Cause
Impact
Packets would be dropped which would cause poor voice quality and other problems.
Action
1. If only ONE GLI triggered this alarm, switch all master port of this board to its partner board,
and reboot the board.
2. If the alarm being triggered again after the board rebooted, replace the board.
3. If the alarm being triggered again after the board replaced, contact the next level of maintenance
support.
4. If the more than one GLI triggered this alarm, contact the next level of maintenance support.
Code: 198015879
Severity: Minor
Alarm Description
3-55
Alarm Cause
Impact
Packets would be dropped which would cause poor voice quality and other problems.
Action
Code: 198015880
Severity: Minor
Alarm Description
The number of dropped packets is over threshold due to control and media plane communication error
Alarm Cause
Impact
Packets would be dropped which would cause poor voice quality and other problems.
Action
3-56
Code: 198015881
Severity: Minor
Alarm Description
Alarm Cause
1. Packets error.
2. Board hardware error.
Impact
Packets would be dropped which would cause poor voice quality and other problems.
Action
1. Check all the GLI board in the same shelf to confirm whether there were any other alarms, if this
is the ONLY alarmed board, switch all master port of this board to its partner board, and replace
this board.
2. If this alarm being triggered again after the board replaced, contact the next level of maintenance
support.
3. If more than one GLI triggered this alarm, contact the next level of maintenance support.
Code: 198015882
Severity: Minor
Alarm Description
3-57
Alarm Cause
Impact
Packets would be dropped which would cause poor voice quality and other problems.
Action
1. Check the state of all ports of the alarmed board, if more than 2 ports of this board is in master
state, switch 1 or 2 ports to its partner port.
2. If the alarm is still active, reboot the board.
3. If the alarm being triggered again after the board rebooted, replace the board.
Code: 198005670
Severity: Critical
Alarm Description
Alarm Cause
Impact
Action
3-58
Code: 198005673
Severity: Major
Alarm Description
Alarm Cause
The setting of the DIP switch on the backboard has been changed.
Impact
Action
1. Plug the uim/UIM_2/GUIM/GUIM2/GUIM/GUIM2_2 board tightly to the slot again and then observe
if the alarm is given.
Y->Go to "2"
N->End.
2. Replace the backplane of the shelf, and check if this alarm is given.
Y->Please contact the next level of maintenance support.
N->End.
Code: 198005653
Severity: Major
3-59
Alarm Description
Alarm Cause
Class B faults of GPS module of ICM board are generated by singlechip processor checking,
including antenna feed short circuit or open circuit, poor quality of received satellite signals or difficulty
in receiving satellite signals, and large phase difference of 10M OCXO assistant phase control.
Impact
There is no impact on system clock or services if the type B fault lasts for less than 48 hours. After 48
hours, the system clock is deviated and system synchronization fails. When GPS signal is poor, the
alarm will be repeatedly reported/restored. As long as the alarm lasts for no more than 48 hours, both
system clock and services will not be affected.
When the system clock is lost or clock frequency deviation happens, services may be affected
differently according to transmission mode.
1. For TDM transmission, all links based on TDM transmission medium (including UE transmission
link and cell transmission link) will be affected. Packets may be lost, which leads to degradation
of service quality. In serious situation, services may be interrupted, handover may fail and cell
out-of-service may happen.
2. For non-TDM transmission (e.g. IP transmission), services via Iub interface will be affected. This
fault will not affect services via Iur interface or Iu interface. In this case, Node B will fetch clock signal
from RNC by using IEEE1588 function, but the clock is inaccurate.
When RNC's clock frequency offset is no more than 0.05 ppm, Node B synchronization can be
achieved. But inter-RNC soft handover success rate will fall.
When RNC's clock frequency offset exceeds 0.5 ppm, Node B cannot lock the clock. Then Node B
will work in free oscillation mode. In this case, inter-Node B soft handover success rate will drop.
Action
Check the input circuit of antenna feeder of ICM board so that it can receive good GPS signals.
The checking items include:
1) The position of the receiving antenna.
The antenna should be installed in an open area, far away from high buildings and clear from shades.
The effective visibility angle of the antenna should be greater than 150 degrees.
2) The connection between power splitter and front panel.
The connector used to connect the power splitter and the front panel should be in good contact and
properly connected.
3-60
Code: 198005674
Name: Sending or receiving packets between management port and CPU control port
failed
Severity: Critical
Alarm Description
Sending or receiving packets between management port and CPU control port failed
Alarm Cause
Impact
Isolate island, checking packets being abnormal or messages between shelves being abnormal may
occur. For active/standby configuration, there are two cases:
1. If the active board is abnormal while the standby board is normal, the system performs
active/standby switchover. Thus, the standby board takes over the services of the faulty active
board. In this case, the service is not affected.
2. If both the active and standby boards are abnormal, active/standby switchover is forbidden. In this
case, the service is interrupted because the faulty board cannot restore to the normal status.
Action
Replace the board. CPU control port, management port or switch chip is error when this alarm
happens. By resetting the board, this fault will be self-cured with very few possibility, and the fault
may remain.
Code: 198005130
Severity: Major
3-61
Alarm Description
Alarm Cause
Impact
Action
Try to change over the special fiber port by network manage system. If failed to change over for three
continuous times, the fiber port has fault, please replace the fiber port or board.
Code: 198005131
Severity: Warning
Alarm Description
Alarm Cause
The fiber is not completed connected to the port, or is damaged, or is not compatible with the optical
transceiver module in T-net switch.
Impact
There might be error in the data transmitted by the optical port which affects the quality of all the
services performed on this optical port.
3-62
Action
Code: 198005675
Severity: Warning
Alarm Description
Alarm Cause
Impact
The input power of the shelf has may have fault. There will be no power if all two electrical sources
input are abnormal.
Action
1. Please check the cable connection between the PDU and the back board.
Y->If the cable connection is OK, go to 2;
N->If the cable connection is error, please connect the cable again. Check whether the alarm
disappears. Y->The troubleshooting completes. N->Go to 2.
2. Please check the switch.
Y->If the switch is OK, go to 3;
N->If the switch is abnormal, please switch on the switch. Check whether the alarm disappears.
Y->The troubleshooting completes. N->Go to 3.
3. Please replace the cable.
Y->If the alarm disappears, the troubleshooting completes.
3-63
Code: 198016641
Severity: Major
Alarm Description
Device's LRU algorithm is invalid, which may cause failure of queue scheduling
Alarm Cause
Impact
It may cause failure of queue scheduling, and then services won't work normally.
Action
Make records of the alarm information and contact the next level of maintenance support.
Code: 198002563
Severity: Major
Alarm Description
3-64
Alarm Cause
Impact
Action
Code: 198002564
Severity: Major
Alarm Description
Alarm Cause
Impact
Action
1. Wait for about 20 minutes. If the alarm is not restored, please restart the board.
2. If the alarm still exists after restarting the board, please replace the board.
3-65
Code: 198005132
Severity: Minor
Alarm Description
The mate board exist POWERON signal but RUN signal is inexistent
Alarm Cause
The mate board exist POWERON signal but RUN signal is inexistent.
Impact
Action
Code: 198005676
Severity: Major
Alarm Description
The connect port flow is too high, that is over the value of flow threshold configuration.
Alarm Cause
The connect port flow is too high, that is over the value of flow threshold configuration.
3-66
Impact
Action
Code: 198005791
Severity: Minor
Alarm Description
Alarm Cause
Impact
It affects the data transfer of the remote SFP. If it is serious, which will make bad the SFF on the
other side.
Action
3-67
Code: 198005792
Severity: Minor
Alarm Description
Alarm Cause
Impact
Action
Code: 198005793
Severity: Minor
Alarm Description
3-68
Alarm Cause
Impact
It affects the data transfer of the local SFP. If it is serious, which will make bad the SFF on the
other side.
Action
1. Check the configuration of the TX module on the remote side is too long transmission.
2. Replace the SFP on the remote side.
3. Check the configuration of the fiber type (You should use single mode fiber, but OM1 or OM2 or
OM3 fiber).
4. Replace the SFP on the local side.
Code: 198005794
Severity: Minor
Alarm Description
Alarm Cause
Impact
Action
1. Check the configuration of the TX module on the remote side is too long transmission.
2. Replace the SFP on the remote side.
3. Check the configuration of the fiber type (You should use single mode fiber, but OM1 or OM2 or
OM3 fiber).
4. Replace the SFP on the local side.
3-69
Code: 198005795
Severity: Minor
Alarm Description
Alarm Cause
Impact
Action
Code: 198018436
Severity: Major
Alarm Description
3-70
Alarm Cause
Board hardware fault.
Impact
When the slave board change to master, the service through this board will be interrupt.
Action
Replace the board.
Severity: Minor
Alarm Description
APP driver memory operation abnormal, such as static memory is not enough or pointer is rewrited.
Alarm Cause
1. Static memory is not enough.
2. Pointer was rewrited.
Impact
The board may reboot when the static memory is not enough.
Action
When the memory exception influences the services, reboot the board.
3-71
Severity: Minor
Alarm Description
The RNC detects that the user-plane resource pool cannot assign new resources.
Alarm Cause
Impact
Action
1. [A2051] Run the START DTM command to perform a board diagnostic test to diagnose the
operational statuses of all RUB resource boards, and check whether the resource board is
operating properly.
Yes -> Step 2.
No -> Step 3.
2. Contact the next level of maintenance support (it is recommended to expand the capacity
of the RUB board).
3. 3. Contact the next level of maintenance support.
Code: 198105026
Severity: Critical
Alarm Description
Alarm Cause
3-72
Impact
Action
1. Run the SET NORMALRESET command to reset the board in accordance with "Rack number",
"Shelf number", "Slot number", and "CPU number" in the alarm information. Wait for five minutes,
and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Contact the next level of maintenance support.
Code: 198105029
Severity: Major
Alarm Description
Alarm Cause
Impact
When the OMP is reset, the operation and maintenance tasks are affected, but services are not
affected.
Action
1. After the alarm arises, wait for five minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Contact the next level of maintenance support.
3-73
Code: 198105034
Severity: Minor
Alarm Description
The log server board detects that the corresponding rear card is offline.
Alarm Cause
l The rear card corresponding to the log server board is not present.
l The rear card has a poor contact with the log server board.
l The hardware of the rear card corresponding to the log server board is faulty.
Impact
The link between the log server and OMM server is interrupted, and the OMM fails to obtain the
signaling tracing data or performance statistics data.
Action
1. Check whether the rear card is installed in the physical location where the alarm arises.
Yes -> Step 3.
No -> Step 2.
2. Install the rear card into the corresponding slot, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Remove and reinstall the rear card, and check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
4. Replace the rear card with an operational one, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Contact the next level of maintenance support.
3-74
Severity: Minor
Alarm Description
The log server board detects a disk failure.
Alarm Cause
l The SMART parameter of the hard disk on the log server is not correctly set.
l The RAID1 level of the hard disk on the log server is degraded.
Impact
A faulty hard disk has no effect on the system. If the backup hard disk also fails, the log server
cannot operate properly.
Action
1. Determine the location of the abnormal hard disk in accordance with "Error hardware disk
location" in the alarm information.[[Replace the hard disk with an operational one]], and check
whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Contact the next level of maintenance support.
Severity: Minor
Alarm Description
The log server board detects that the disk partition usage is too high.
3-75
Alarm Cause
The usage of the hard disk partition on the log server exceeds the threshold (95 percent).
Impact
The disk partition space is insufficient, causing the log server not to operate properly.
Action
3.1.96 198105039 Bursty flow rate of the control plane for shelf
connection overload
Alarm Information
Code: 198105039
Name: Bursty flow rate of the control plane for shelf connection overload
Severity: Major
Alarm Description
The base station controller detects that a burst of the control-plane inter-shelf flow
exceeds the overload threshold (Bglobal(Bglobal).Stream Overload threshold of Trunk
Port(trunkPortOverLoadThr)) .
Alarm Cause
Impact
A burst of control-plane inter-shelf flow triggers the overload control in the system, causing new users
not to be connected to the system.
3-76
Action
Alarm Description
Alarm Cause
80g detects that the GLIQP board restarts, or the 80g chip is abnormal.
3-77
Impact
Action
Restart the board for which the alarm is reported. Replace the board with a good one if the alarm still
exists. Contact the next level of maintenance support. if replacing the board does not work.
Alarm Description
There are no frame heads on the LVDS channel, or the 257th and the 258th time slot are not 0xf1 or
0xba with frame heads on the LVDS channel
Alarm Cause
Impact
Action
1. Check if the TFI optical fiber corresponding to this path is connected in position or is damaged.
2. Connect the fiber in place or replace it with anther one, and check if the alarm is eliminated.
3. Check if the fiber matches the optical transceiver module.
4. Replace the fiber, and check if the alarm is eliminated.
5. Switch T network board.
3-78
Alarm Description
It is wrong about the 129th time slot loop of LVDS between logic TSNB and TFI
Alarm Cause
Impact
Action
1. Check if the TFI optical fiber corresponding to this path is connected in position or is damaged.
2. Connect the fiber in place or replace it with anther one, and check if the alarm is eliminated.
3. Check if the fiber matches the optical transceiver module.
4. Replace the fiber, and check if the alarm is eliminated.
5. Switch T network board.
Alarm Description
Alarm Cause
Connection chip (73273/73260) faults on TDM Switch Network Board cause some 129 time slots of
HW having connection faults.
Impact
If the fault occurs on master board, board state will be changed to slave; slave board will be reset
immediately.
3-79
Action
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
3-80
Alarm Cause
The running physical link between the master and the slave port is broken.
Impact
Action
Alarm Description
Alarm Cause
Impact
Action
1. Reset the corresponding DSP chip or the board by using MML command on the background and
then check the alarm is eliminated.
2. Replace the board.
3-81
Alarm Description
Alarm Cause
1. APS Channel between Master and Slave Board gets hardware fault.
2. The connection on the backplane between the slot and the neighboring slot gets errors.
Impact
Action
Alarm Description
3-82
Alarm Cause
Impact
The Gb bear channel corresponding to this alarm is blocked and the Gb bandwidth is decreased.
In this case, PS traffic congestion may occur.
Action
1. According to the board's physical position and PCM number ("Port") in the alarm details,
check whether the configuration of "E1 Port(E1Port)"."E1 Frame Type(Crc4Mode)" of the PCM
link ("Brch(GFrGbBrch)"."Used Gb Interface Pcm(refGGbPcm)") on the Gb interface board is
consistent with that of the SGSN.
Yes -> Step 3.
No -> Step 2.
2. Modify the configuration of "E1 Frame Type" for the PCM link on the Gb interface board to ensure
the consistency with that of the SGSN, and then check whether this alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the configurations of "PCM TS(StartTs)" and "Access rate"(GFrGbBrch.AR)" in the
"Brch(GFrGbBrch)" configuration parameter of the BSC are consistent with those of the SGSN.
Yes -> Step 5.
No -> Step 4.
4. Modify the two parameters for consistency between the BSC and the SGSN, and check whether
the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Check whether the E1 port corresponding to the bear channel reports an alarm.
Yes -> Step 6.
No -> Step 7.
6. Handle the transmission device alarm, and check whether this alarm is cleared.
Yes -> End.
No -> Step 7.
7. Perform a physical self-loop check on the local E1 terminal device, and check whether the E1 line
operates properly (the green light flashes slowly).
Yes -> Step 9.
No -> Step 8.
8. Replace the E1 line, and check whether the alarm is cleared.
Yes -> End.
No -> Step 9.
9. Contact SGSN maintenance personnel to check whether the peer E1 line operates properly.
Yes -> Step 11.
No -> Step 10.
3-83
10. Contact SGSN maintenance personnel to troubleshoot the SGSN equipment, and check whether
the alarm is cleared.
Yes -> End.
No -> Step 11.
11. Replace the faulty board, and check whether the alarm is cleared.
Yes -> End.
No -> Step 12.
12. Contact the next level of maintenance support.
Alarm Description
Alarm Cause
In case of intermediate Frame Relay networking, for a specific NSVC, the number of frames with the
BECN bit of "1" is more than or equal to the number of frames with the BECN bit of "0" in a 10-second
interval. (The peer end may be overloaded or be configured improperly.)
Impact
Quality of PS services for some of users may be degraded, or new users fail to access the services.
Action
3-84
Alarm Description
This alarm is reported if a board detects that the NSVC link in E1 is faulty.
Alarm Cause
NS Alive Ack cannot be received several consecutive times (GBssFunction.NSAliveMax) during the
NS Alive procedure.
Impact
Action
1. Check whether the configuration of "NSEI" and "NSVCI" in the alarm details is consistent with
that of the SGSN.
Yes -> Step 3.
No -> Step 2.
2. Search the parent object "Frame relay Nse(GFrGbNse)" and modify "Nse ID(GFrGbNseSeq)".
Modify the configuration of "NSVCI(GFrGbNsvcSeq)" according to the alarm object "Frame relay
Nsvc(GFrGbNsvc)" for consistency with that of the SGSN, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the following alarm arises:
198087340 FR device failure
Yes -> Step 4.
No -> Step 5.
4. Handle the above alarm, and check whether this alarm is cleared.
Yes -> End.
No -> Step 5.
5. Contact the next level of maintenance support.
3-85
Alarm Description
This alarm is reported if a board detects that the NSVC link in IP is faulty.
Alarm Cause
NS Alive Ack cannot be received several consecutive times (GBssFunction.NSAliveMax) during the
NS Alive procedure.
Impact
For single NSVC link configuration, the PS service is interrupted. For multi-NSVC link configuration,
the bandwidth is decreased. In this case, PS traffic congestion may occur.
Action
1. Check whether the configuration of "NSEI" in the alarm details is consistent with that of the SGSN.
Yes -> Step 3.
No -> Step 2.
2. Modify the configuration of the parameter "Nse ID(GIpGbNseSeq)" of the object "IP
Nse(GIpGbNse)" for consistency with that of the SGSN, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether alarms arise on the Gb interface board.
Yes -> Step 4.
No -> Step 5.
4. Handle the related alarms, and check whether this alarm is cleared.
Yes -> End.
No -> Step 5.
5. Contact the maintenance personnel of the transmission or peer device to check whether the
transmission or peer device is faulty.
Yes -> Step 6.
No -> Step 7.
6. Remove the faults, and check whether the alarm is cleared.
Yes -> End.
No -> Step 7.
7. Contact the next level of maintenance support.
3-86
Alarm Description
This alarm is reported if the BSC detects the PS process unit failure.
Alarm Cause
Impact
Action
1. Wait for five minutes, and check whether the alarm is cleared automatically.
Yes -> End.
No -> Step 2.
2. Execute the QRY PSCELLDSPcommand based on "Site ID" and "Bts ID" in the alarm details to
query the corresponding SLAVE of the cell. Execute the QRY SUNITSTATUScommand based
on "Sub System number", "RUP board number", and "SLAVE number" in the returned results
to query the status of the sub-unit.
"Manual block" status -> Step 3.
Other status -> Step 4.
3. Unblock the PS processing sub-unit. Check whether the alarm is cleared.
Yes -> End.
No -> Step 4.
4. Reset the PS processing sub-unit, wait for two minutes, and then check whether the alarm
is cleared.
Yes -> End.
No -> Step 5.
5. Contact the next level of maintenance support.
3-87
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
3-88
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
3-89
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
3-90
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
3-91
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
3-92
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
3-93
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
3-94
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
3-95
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
3-96
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
3-97
Alarm Cause
None
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
None
Impact
User-defined.
Action
None
3-98
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
Impact
A transmission link inside the BTS is disconnected, frame numbers are confused, and the frequency
synthesizer does not operate properly.
Action
1)Test transmission index. If the transmission continuously has over-2Hz frequency offset in
4 seconds or the single frequency adjustment is more than 4 Hz for 15 times in 6 minutes, it is
necessary to notify the engineer to adjust transmission.
2)Reset CMB board and check whether the alarm disappears.
3)If the alarm does not disappear, replace CMB board.
3-99
Alarm Description
Alarm Cause
Impact
A transmission link inside the BTS is disconnected, frame numbers are confused, and the frequency
synthesizer does not operate properly.
Action
1)Test transmission index. If the transmission continuously has over-2Hz frequency offset in
4 seconds or the single frequency adjustment is more than 4 Hz for 15 times in 6 minutes, it is
necessary to notify the engineer to adjust transmission.
2)Reset CMB board and check whether the alarm disappears.
3)If the alarm does not disappear, replace CMB board.
Alarm Description
3-100
Alarm Cause
Standby CMM/CMB board is not powered on, or active-standby CMM/CMB board communication
error
Impact
Action
Alarm Description
Alarm Cause
Impact
The system is less reliable because the faulty master board fails to be switched over to the slave
board.
Action
check if standby board is present in the rack. If it is , reset or insert standby board again( normal
state of standby board is that power lamp always lights and running lamp always lights);if it isn't,
insert a new CMM/CMB board
3-101
Alarm Description
Standby CMM/CMB board abnormal
Alarm Cause
Standby CMM/CMB board starts abnormally or not inserted properly
Impact
The master and slave boards fail to be switched over.
Action
Check whether the spare board is on the rack. If yes, reset or re-plug the board ( it is in the normal
condition if the power LED indicator and RUN LED indicator are both on). If no, plug in the new
CMB board if necessary.
Alarm Description
CMM/CMB power failure alarm
Alarm Cause
CMM/CMB board is power off
Impact
The CMM/CMB boards fail to operate.
3-102
Action
E1 interface will bridge-connect automatically. Replace the CMB circuit board as quickly as possible.
Alarm Description
Alarm Cause
Impact
Action
1. Check if line between racks is connected. if it has problems, connect or replace it. 2. start
self-check of master-slave rack communication to confirm the problem of CMM/CMB hardware
or software. then replace it
3-103
Alarm Description
Alarm Cause
Impact
Action
1. Check if line between racks is connected. if it has problems, connect or replace it. 2. start
self-check of master-slave rack communication to confirm the problem of CMM/CMB hardware
or software. then replace it
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
3-104
Action
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, bad E1 connections, or CMM board not
support C/F configuration, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
3-105
Alarm Description
Alarm Cause
Sending line is shorted, the remote end might not receive data sent from local end
Impact
Action
1.Check the electrical connection property of the E1 cable.2. If the cable of E1 did not have problems,
insert the board tightly and resetting.3.If the warning continue to exist, the E1 interface chip maybe is
in abnormal.4. If can pass the chip selftest, can start the selfloop test procedure for E1 interface.5.If
the selfloop test result is correct, can think that the transmission equipment have problems.
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
3-106
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, bad E1 connections, or CMM board not
support C/F configuration, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
3-107
Action
Alarm Description
Alarm Cause
Sending line is shorted, the remote end might not receive data sent from local end
Impact
Action
1.Check the electrical connection property of the E1 cable.2. If the cable of E1 did not have problems,
insert the board tightly and resetting.3.If the warning continue to exist, the E1 interface chip maybe is
in abnormal.4. If can pass the chip selftest, can start the selfloop test procedure for E1 interface.5.If
the selfloop test result is correct, can think that the transmission equipment have problems.
3-108
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, bad E1 connections, or CMM board not
support C/F configuration, etc
3-109
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
Alarm Description
Alarm Cause
Sending line is shorted, the remote end might not receive data sent from local end
Impact
Action
1.Check the electrical connection property of the E1 cable.2. If the cable of E1 did not have problems,
insert the board tightly and resetting.3.If the warning continue to exist, the E1 interface chip maybe is
in abnormal.4. If can pass the chip selftest, can start the selfloop test procedure for E1 interface.5.If
the selfloop test result is correct, can think that the transmission equipment have problems.
3-110
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
Alarm Description
3-111
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, bad E1 connections, or CMM board not
support C/F configuration, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
Alarm Description
Alarm Cause
Sending line is shorted, the remote end might not receive data sent from local end
Impact
3-112
Action
1.Check the electrical connection property of the E1 cable.2. If the cable of E1 did not have problems,
insert the board tightly and resetting.3.If the warning continue to exist, the E1 interface chip maybe is
in abnormal.4. If can pass the chip selftest, can start the selfloop test procedure for E1 interface.5.If
the selfloop test result is correct, can think that the transmission equipment have problems.
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
3-113
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, bad E1 connections, or CMM board not
support C/F configuration, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
Alarm Description
Alarm Cause
Sending line is shorted, the remote end might not receive data sent from local end
3-114
Impact
Action
1.Check the electrical connection property of the E1 cable.2. If the cable of E1 did not have problems,
insert the board tightly and resetting.3.If the warning continue to exist, the E1 interface chip maybe is
in abnormal.4. If can pass the chip selftest, can start the selfloop test procedure for E1 interface.5.If
the selfloop test result is correct, can think that the transmission equipment have problems.
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
3-115
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, bad E1 connections, or CMM board not
support C/F configuration, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
1. Check the electric-connection performance of E1 line. 2. if E1 line has no problem, insert the board
tightly and reset. 3.if C/F Trunk alarm happens, please check Whether CMM board hardware version
is 030903 or 030900, and if so, it need be changed to 030508 version.( this situation only suitable for
Site V2 serials). 4. if alarm still exists, maybe E1 interface chip is abnormal. 5. if chip's self-check is
passed, start loop test of E1 interface. 6. if loop test of E1 is correct, the transport has problems.
Alarm Description
3-116
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
1. Check the electric-connection performance of E1 line. 2. if E1 line has no problem, insert the board
tightly and reset. 3. if alarm still exists, maybe E1 interface chip is abnormal. 4. if chip's self-check is
passed, start loop test of E1 interface. 5. if loop test of E1 is correct, the transport has problems
Alarm Description
Alarm Cause
Sending line is shorted, the remote end might not receive data sent from local end
Impact
Action
1.Check the electrical connection property of the E1 cable.2. If the cable of E1 did not have problems,
insert the board tightly and resetting.3.If the warning continue to exist, the E1 interface chip maybe is
in abnormal.4. If can pass the chip selftest, can start the selfloop test procedure for E1 interface.5.If
the selfloop test result is correct, can think that the transmission equipment have problems.
3-117
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
1. Check the electric-connection performance of E1 line. 2. if E1 line has no problem, insert the board
tightly and reset. 3. if alarm still exists, maybe E1 interface chip is abnormal. 4. if chip's self-check is
passed, start loop test of E1 interface. 5. if loop test of E1 is correct, the transport has problems
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
3-118
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
1. Check the electric-connection performance of E1 line. 2. if E1 line has no problem, insert the board
tightly and reset. 3. if alarm still exists, maybe E1 interface chip is abnormal. 4. if chip's self-check is
passed, start loop test of E1 interface. 5. if loop test of E1 is correct, the transport has problems
Alarm Description
Alarm Cause
Sending line is shorted, the remote end might not receive data sent from local end
Impact
Action
1.Check the electrical connection property of the E1 cable.2. If the cable of E1 did not have problems,
insert the board tightly and resetting.3.If the warning continue to exist, the E1 interface chip maybe is
in abnormal.4. If can pass the chip selftest, can start the selfloop test procedure for E1 interface.5.If
the selfloop test result is correct, can think that the transmission equipment have problems.
3-119
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
Action
1. Check the electric-connection performance of E1 line. 2. if E1 line has no problem, insert the board
tightly and reset. 3. if alarm still exists, maybe E1 interface chip is abnormal. 4. if chip's self-check is
passed, start loop test of E1 interface. 5. if loop test of E1 is correct, the transport has problems
Alarm Description
Alarm Cause
Chip fault, clock abnormal, difference from BSC clock, or bad E1 connections, etc
Impact
This fault has a little impact on calls if it does not occur frequently. However, errors may occur during
a call or the link establishment between the TRM/DTRU and the BSC if this alarm occurs frequently
(for example, at intervals of several minutes).
3-120
Action
1. Check the electric-connection performance of E1 line. 2. if E1 line has no problem, insert the board
tightly and reset. 3. if alarm still exists, maybe E1 interface chip is abnormal. 4. if chip's self-check is
passed, start loop test of E1 interface. 5. if loop test of E1 is correct, the transport has problems
Alarm Description
Alarm Cause
Sending line is shorted, the remote end might not receive data sent from local end
Impact
Action
1.Check the electrical connection property of the E1 cable.2. If the cable of E1 did not have problems,
insert the board tightly and resetting.3.If the warning continue to exist, the E1 interface chip maybe is
in abnormal.4. If can pass the chip selftest, can start the selfloop test procedure for E1 interface.5.If
the selfloop test result is correct, can think that the transmission equipment have problems.
3-121
Alarm Description
Temperature alarm
Alarm Cause
Impact
User-defined.
Action
check the envirnment temperature.if it conforms to the demand, keep on observing and keep normal
status in the case of other modules no fault. If not , please change it.if there are some other problems,
please replace FCM module
Alarm Description
Fan absent
Alarm Cause
Impact
User-defined.
Action
3-122
Alarm Description
Alarm Cause
CPU fault
Impact
User-defined.
Action
1. check the line and correct it. 2. check the fan and replace FCM.
Alarm Description
Fan alarm
Alarm Cause
Impact
User-defined.
3-123
Action
Alarm Description
Alarm Cause
Impact
Action
Check the environment temperature meets the requirement or not.If meet the requirement, under the
premise that other modules have not fault, can continue to observe, and keep the normal work. If not
meet the requirement, then improving the equipments working environment is needed. If break down,
then should replace the FCM module immediately.
3-124
Alarm Description
Fan 1 alarm
Alarm Cause
Impact
Too high temperature is generated on the TRX shelf in the same layer.
Action
Check the alarm circuit have fault or not, if have problem, then resolve it.
2. Check the fan has fault or not. If have problem, then replace the FCM.
3. Check the alarm sampling electric circuit of TPU is good or not, otherwise replacing the
corresponding DTRM module
Alarm Description
Fan 2 alarm
Alarm Cause
Impact
Too high temperature is generated on the TRX shelf in the same layer.
Action
Check the alarm circuit have fault or not, if have problem, then resolve it.2. Check the fan has fault or
not. If have problem, then replace the FCM.3. Check the alarm sampling electric circuit of TPU is
good or not, otherwise replacing the corresponding DTRM module
3-125
Alarm Description
Alarm Cause
Impact
Action
Check the environment temperature meets the request or not.If meet the request, under the premise
that other modules have not fault, can continue to observe, and keep the normal work. If not meet
the request, then improving the equipments working environment is needed. If break down, then
should replace the FCM module immediately.
Alarm Description
LNA alarm
Alarm Cause
3-126
Impact
User-defined.
Action
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Alarm Description
3-127
Alarm Cause
Impact
User-defined.
Action
keep on observing.if normal work isn't influenced, don't replace AEM module.
Alarm Description
Alarm Cause
Impact
User-defined.
Action
please replace AEM and reset TRM which connects with this AEM.
3-128
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Alarm Description
Alarm Cause
Impact
User-defined.
Action
check whether config type of AEM doesn't conform to actual type, whether insert tightly and poweron.
If not, please replace it.if type is correct, problem maybe is the fault of back panel transport or the
fault of TPU collecting circuit, please replace the cable or the module.
3-129
Alarm Description
Alarm Cause
Impact
User-defined.
Action
please replace AEM and reset TRM which connects with this AEM.
Alarm Description
Alarm Cause
Impact
3-130
Action
( 1)Check whether there is PA temperature alarm or fan environment temperature alarm on the
background. If yes, deal with the fan alarm first. It is necessary to plug in the blank module if there is
no TRX on the right side of TRM board.
( 2)Check whether the fuse of CDU is damaged. If yes, replace it. ( Note: FU1 2A, FU2 1A)
( 3)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear board
are bent. If yes, change the slot or replace the rear board. After that, re-power on and check whether
the alarm is recovered. ( If changing the slot, it is necessary to re-configure on the background.)
( 4)Replace CDU.
Alarm Description
LNA0 alarm
Alarm Cause
Impact
The connected DTRU board fails to operate (both master and diversity LNAs are faulty) or does not
operate fully (only one LNA is faulty).
Action
( 1)Check whether there is PA temperature alarm or fan environment temperature alarm on the
background. If yes, deal with the fan alarm first. It is necessary to plug in the blank module if there is
no TRX on the right side of TRM board.
( 2)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear board
are bent. If yes, change the slot or replace the rear board. After that, re-power on and check whether
the alarm is recovered. ( If changing the slot, it is necessary to re-configure on the background.)
( 3)Replace CDU.
3-131
Alarm Description
LNA1 alarm
Alarm Cause
Impact
The connected DTRU board fails to operate (both master and diversity LNAs are faulty) or does not
operate fully (only one LNA is faulty).
Action
( 1)Check whether there is PA temperature alarm or fan environment temperature alarm on the
background. If yes, deal with the fan alarm first. It is necessary to plug in the blank module if there is
no TRX on the right side of TRM board.
( 2)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear board
are bent. If yes, change the slot or replace the rear board. After that, re-power on and check whether
the alarm is recovered. ( If changing the slot, it is necessary to re-configure on the background.)
( 3)Replace CDU.
Alarm Description
3-132
Alarm Cause
Impact
This fault has an impact on the uplink receive sensitivity of the related DTRU board.
Action
( 1)Check whether there is PA temperature alarm or fan environment temperature alarm on the
background. If yes, deal with the fan alarm first. It is necessary to plug in the blank module if there is
no TRX on the right side of TRM board.
( 2)Pull off PA power cable. The position of PA power cable: open the BTS rear cover and pull off the
socket with the label of TA_PWR X31 ( X31 PA_PWR for the old rack). The PA power cable connects
to PWRTA_Ln on the top of cabinet. Check whether the alarm disappears. The power cable is useless
in the place where no PA exists. In the place where PA exists, the alarm disappears. It is necessary
to check whether the short circuit exists between the power cable and PA or whether PA goes wrong.
( 3)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear board
are bent. If yes, change the slot or replace the rear board. After that, re-power on and check whether
the alarm is recovered. ( If changing the slot, it is necessary to re-configure on the background.)
( 4)Replace CDU and reset TRX connecting with it.
Alarm Description
Alarm Cause
Impact
This fault has an impact on the uplink receive sensitivity of the related DTRU board.
3-133
Action
( 1)Check whether there is PA temperature alarm or fan environment temperature alarm on the
background. If yes, deal with the fan alarm first. It is necessary to plug in the blank module if there is
no TRX on the right side of TRM board.
( 2)Pull off PA power cable. The position of PA power cable: open the BTS rear cover and pull off the
socket with the label of TA_PWR X31 ( X31 PA_PWR for the old rack). The PA power cable connects
to PWRTA_Ln on the top of cabinet. Check whether the alarm disappears. The power cable is useless
in the place where no PA exists. In the place where PA exists, the alarm disappears. It is necessary
to check whether the short circuit exists between the power cable and PA or whether PA goes wrong.
( 3)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear board
are bent. If yes, change the slot or replace the rear board. After that, re-power on and check whether
the alarm is recovered. ( If changing the slot, it is necessary to re-configure on the background.)
( 4)Replace CDU and reset TRX connecting with it.
Alarm Description
Alarm Cause
Impact
3-134
Action
( 1) Check whether the connection between RF jumper which connects DTRU with CDU and CDU
antenna mouth is tight. If the connection is loose, fasten it with tool. After that, reset the TRX and
check whether the alarm disappears.
( 2)Measure SWR of the jumper between CDU and antenna with SITEMASTER. Check whether the
SWR value exceeds standard. If yes, the antenna has fault. Check the antenna system part by part
upon the test result. Once the fault is found, fasten the antenna, make waterproof treatment on the
antenna and replace the antenna. Reset the TRX and check whether the alarm disappears.
( 3)Replace the RF cable which connects DTRU with CDU. Reset the TRX connecting with it and
check whether the alarm disappears.
( 4)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear
board are bent. If yes, replace the rear board. Check whether the alarm cable connector of CDU
is loose or off. If yes, fasten it and re-power it on. Three minutes after the TRX is running, check
whether the alarm disappears.
( 5)Replace CDU and reset TRX connecting with it.
Alarm Description
Alarm Cause
Impact
3-135
Action
( 1) Check whether the connection between RF jumper which connects DTRU with CDU and CDU
antenna mouth is tight. If the connection is loose, fasten it with tool. After that, reset the TRX. Three
minutes after the TRX is running, check whether the alarm disappears.
( 2)Measure SWR of the jumper between CDU and antenna with SITEMASTER. Check whether the
SWR value exceeds standard. If yes, the antenna has fault. Check the antenna system part by
part upon the test result. Once the fault is found, fasten the antenna, make waterproof treatment
on the antenna and replace the antenna. Reset the TRX. Three minutes after the TRX is running,
check whether the alarm disappears.
( 3)Replace the RF cable which connects DTRU with CDU. Reset the TRX connecting with it. Three
minutes after the TRX is running, check whether the alarm disappears.
( 4)Pull out of CDU and DTRU modules in the same layer. Check whether the pins on the rear
board are bent. If yes, replace the rear board. Check whether the alarm cable connector is loose
or off. If yes, fasten it and re-power it on. Three minutes after the TRX is running, check whether
the alarm disappears.
( 5)Replace CDU and reset TRX connecting with it.
Alarm Description
Alarm Cause
Impact
3-136
Action
( 1)Check whether there is PA temperature alarm or fan environment temperature alarm on the
background. If yes, deal with the fan alarm first. It is necessary to plug in the blank module if there is
no TRX on the right side of TRM board.
( 2)Check whether AEM configuration type is consistent with the actual type, and whether DTRU is
associated with the background, otherwise change or modify the background configuration.
( 3)Check whether AEM powers on, and plugged properly. Shut down AEM module power, plug off
and then plug in the module, turn on the power to check whether the alarm has been recovered.
( 4)Check whether the board DIP switch of AEM is correct. Otherwise, adjust the DIP switch till it is
correct. Check whether the fuse on CDU is broken, if so, change the fuse of the same model. Note:
FU1 2A, FU2 1A; power on the equipment to check whether the alarm is recovered.
( 5)Plug off the AEM and DTRU module of the same layer, check whether there backplane pin is
curved, if so, change the backplane and re-power on to check whether the alarm is recovered.
( 6)Plug in site id, and reset CMB. About five minutes later, check whether the alarm is recovered.
( 7)Replace AEM module.
Alarm Description
Alarm Cause
Impact
3-137
Action
( 1) Check whether there is PA temperature alarm or fan environmental temperature alarm, if so,
process with the fan alarm first. If there is no another TRX or blank module on the right side of the
TRX, plug in a blank module;
( 2) Check whether AEM configuration type is consistent with the actual type, and whether DTRU is
associated with the background, otherwise change or modify the background configuration.
( 3) Check whether AEM powers on, and plugged properly. Shut down AEM module power, plug off
and then plug in the module, turn on the power to check whether the alarm has been recovered.
( 4) Check whether the board DIP switch of AEM is correct. Otherwise, adjust the DIP switch till it is
correct. Check whether the fuse on CDU is broken, if so, change the fuse of the same model. Note:
FU1 2A, FU2 1A; power on the equipment to check whether the alarm is recovered.
( 5) Plug off the AEM and DTRU module of the same layer, check whether there backplane pin is
curved, if so, change the backplane and re-power on to check whether the alarm is recovered.
( 6) Plug in site id, and reset CMB. About five minutes later, check whether the alarm is recovered.
( 7) Change AEM module.
Alarm Description
Alarm Cause
Impact
User-defined.
Action
3-138
Alarm Description
CIP resource can't be used
Alarm Cause
Uplink/downlink loop data demodulation failure
Impact
User-defined.
Action
if alarm exists, at the same time some traffics exist on this TRM, it indicates this TRM is normal; if
there aren't some traffics on this TRM, or RF_LOOP test failure which arose by OMCR, this TRM is
damaged and please replace it at once.
Alarm Description
Uplink failure
Alarm Cause
Error in uplink data receiving
Impact
User-defined.
3-139
Action
Alarm Description
Alarm Cause
Impact
User-defined.
Action
user can reset TPU to solve this problem. If it isn't solved, please replace TRM module.
Alarm Description
3-140
Alarm Cause
Cell parameter configuration is incorrect or conflicts with channel parameters and CU parameter
configuration, carrier frequency configuration in omcr is unconform with the physical board
Impact
User-defined.
Action
1.Wait ten minutes. If the alarm still exists, configure parameters again from background, and
synchronize them to base station. Otherwise check the hardware and replace TRM/DTRM module in
time.
2.Please check whether the carrier frequency configuration in omcr is conform with the physical
board or not.
Alarm Description
Alarm Cause
HDLC link between CMM and TPU breaks, CMM hardware error, etc
Impact
User-defined.
3-141
Action
system can run, but any data doesn't be configured.if only TPU link longtime break, User can use
the methods as follows to remove the problem:
1.Check whether TPU plugin tightly.
2.Reset TPU board.
3.Check whether CMM work normally.
4.Check address switch's right.
5.Transport line''s connection on back panel.
6.Use HW loop test to confirm software problem or hardware problem.if hardware has problems,
please replace it, if software has problems please upgrade software version.
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Reset this CU firstly.If the alarm resume, it could be confirmed that the alarm is arisen by interior
status of DSP abnormal.After resetting resumes, the CU could work normally.if not, BSC should start
BCCH changeover strategy and replace TRM module.
3-142
Alarm Description
Software version of CIP mismatch
Alarm Cause
CIP software version load error. If one of the carriers is configured as BCCH, then the whole cell
can not work normally.
Impact
User-defined.
Action
reset TRM, if it is of no effect, please replace TRM module.
Alarm Description
Clock alarm for TPU and CMM
Alarm Cause
Clock between TPU and CMM is disconnected
Impact
User-defined.
Action
1. If this TPU alarm is the only one alarm in the base station, check the line connection on back
panel.if the connection is correct , please replace TRM.
2. if other TPUs have the same alarm as this TPU, check whether clock alarm exists on CMM
board. If it is , please replace CMM.
3-143
Alarm Description
Alarm Cause
Frame clock FCLK has problem, upper-level frame number synchronization source CMM has problem
Impact
User-defined.
Action
1.check if FCLK of frame no 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 loose lock
exists.if there are some problems, please replace TRM module.
2. Transport link( transport clock, interface chip, the size of error code rate)3. check superior
synchro source of frame no
Alarm Description
Alarm Cause
3-144
Impact
All the sixteen physical channels of the dual-carrier fail to operate properly. Cell services may also be
affected if the DTRU board is configured as BCCH.
Action
Alarm Description
Alarm Cause
Cell parameter configuration is incorrect or conflicts with channel parameters and CIP parameter
configuration
Impact
Action
1. If the alarm is not recovered within 10 minutes, re-configure the parameter in the background,
and synchronize to the base station.
2. Reset the TRX, after 10 minutes, check whether the alarm is recovered.
3. Re-plug the TRX module, after 10 minutes, check whether the alarm is recovered.
4. Change the corresponding TRX module.
3-145
Alarm Description
Alarm Cause
HDLC link between CMB and TPU breaks, CMB hardware error, etc
Impact
TPU polling is faulty and data fails to be transmitted between the TPU and CMB. Data fails to be
configured for the FUC, CHP, and CIP and their states fail to be reported.
Action
1. Check whether DTRU is plugged tightly and properly. Re-plug DTRU module, and add DTRU in
corresponding position according to the configuration, so as to check whether the alarm is recovered.
2. Reset DTRU board to check whether the alarm is recovered.
3. If alarms occur in all the cells, check whether CMB board works normally. Re-plug CMB to check
whether the alarm is recovered.
4. Check whether the DIP switch on the backplane is correct. Otherwise, adjust the switch to correct
position, to check whether the alarm is recovered.
5. Check whether the transmission line of the backplane is connected correctly. Otherwise connect
the line to correct position to check whether the alarm is recovered.
3-146
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
Frame clock FCLK has problem, upper-level frame number synchronization source CMB has problem
Impact
The DTRU board fails to operate. Cell services may also be affected if the DTRU board is configured
with BCCH.
3-147
Action
1. Measure every Frame clock FCLK that produce frame number to ensure it is normal( if deliver
directly, then see the frequency of the clock, whether waveform have or not distortion. if it is
phaselock to produce, then check whether have the warning of lose lock or not). if have fault then
replace the DTRM module in time.
2. Check transmission link( whether clock of transmission is normal or not, whether the interface chip
have or not warning, whether the size of the error code rate is small or not)
3.Whether the upper source of synchronization exists the warning or not.
Alarm Description
Rx PLL1 unlock
Alarm Cause
Impact
User-defined.
Action
1. Check whether clock alarm exists with LMT.if it exists, please replace relevant module.if it doesn't
exist, check the 13M output of TP on front panel. If it doesn't exist, there is clock problem from TPU to
RCU.please replace TRM.
2. if the problem still exists, maybe the LO fail, please replace TRM.
3-148
Alarm Description
Rx PLL2 unlock
Alarm Cause
Impact
User-defined.
Action
1. Check whether clock alarm exists with LMT.if it exists, please replace relevant module.if it doesn't
exist, check the 13M output of TP on front panel. If it doesn't exist, there is clock problem from TPU to
RCU.please replace TRM.
2. if the problem still exists, maybe the LO fail, please replace TRM.
Alarm Description
Tx PLL1 unlock
Alarm Cause
Impact
User-defined.
3-149
Action
1. Check whether clock alarm exists with LMT.if it exists, please replace relevant module.if it doesn't
exist, check the 13M output of TP on front panel. If it doesn't exist, there is clock problem from TPU to
RCU.please replace TRM.
2. if the problem still exists, maybe the LO fail, please replace TRM.
Alarm Description
Tx PLL2 unlock
Alarm Cause
Impact
User-defined.
Action
1. Check whether clock alarm exists with LMT.if it exists, please replace relevant module.if it doesn't
exist, check the 13M output of TP on front panel. If it doesn't exist, there is clock problem from TPU to
RCU.please replace TRM.
2. if the problem still exists, maybe the LO fail, please replace TRM.
3-150
Alarm Description
Alarm Cause
Impact
User-defined.
Action
1. Check whether clock alarm exists with LMT.if it exists, please replace relevant module.if it doesn't
exist, check the 13M output of TP on front panel. If it doesn't exist, there is clock problem from TPU to
RCU.please replace TRM.
2. if the problem still exists, maybe the LO fail, please replace TRM.
Alarm Description
Tx IF PLL unlock
Alarm Cause
Impact
User-defined.
Action
1. Check whether clock alarm exists with LMT.if it exists, please replace relevant module.if it doesn't
exist, check the 13M output of TP on front panel. If it doesn't exist, there is clock problem from TPU to
RCU.please replace TRM.
2. if the problem still exists, maybe the LO fail, please replace TRM.
3-151
Alarm Description
Alarm Cause
EEPROM fault
Impact
User-defined.
Action
Alarm Description
Alarm Cause
Impact
User-defined.
3-152
Action
Alarm Description
Alarm Cause
Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in
output end of PA
Impact
User-defined.
Action
Alarm Description
3-153
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, environment temperature too high, and detecting circuit fault, etc
Impact
User-defined.
Action
1.Check whether fan works normally or not and whether the environment temperature is high or not.
2.If the fan works normally and the environment temperature is normal, the PA temperature warning
still exist then may be the detection electric circuit breakdown, continue to observe.
Alarm Description
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, environment temperature too high, and detecting circuit fault, etc
Impact
User-defined.
Action
1.Check whether fan works normally or not and whether the environment temperature is high or not.
2.If the fan works normally and the environment temperature is normal, the PA temperature warning
still exist then may be the detection electric circuit breakdown, should replace the TRM/DTRM
module in time.
3-154
Alarm Description
PA output power alarm
Alarm Cause
Direct reason: Difference between PA output power and CIP control power is more than 3 db;
Possible reason: PA aging, power detecting circuit fault, or detecting threshold too narrow
Impact
User-defined.
Action
1.Reset TRM and observe.
2. if alarm exists, replace TRM module as soon as possible.
Alarm Description
PA power overvoltage
Alarm Cause
PA power overvoltage
Impact
User-defined.
3-155
Action
check the check circuit of PA.if it has problem, please replace TRM.
Alarm Description
Alarm Cause
PA power undervoltage
Impact
User-defined.
Action
check the check circuit of PA.if it has problem, please replace TRM.
Alarm Description
Alarm Cause
3-156
Impact
User-defined.
Action
1. Check the signal and time-sequence between CHP and modulation module.
2. if the problem still exists, please replace TRM in time.
Alarm Description
Alarm Cause
Impact
User-defined.
Action
3-157
Alarm Description
Alarm Cause
Direct reason: Reverse power is too high; Possible reason: Open circuit or high resistance exists at
the output end of PA
Impact
User-defined.
Action
Alarm Description
80w PA overtemperature
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, environment temperature too high, and detecting circuit fault, etc
Impact
User-defined.
Action
1.Check whether fan works normally or not and whether the environment temperature is high or not.
2.If the fan works normally and the environment temperature is normal, the PA temperature warning
still exist then may be the detection electric circuit breakdown, continue to observe.
3-158
Alarm Description
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, environment temperature too high, and detecting circuit fault, etc
Impact
User-defined.
Action
1.Check whether fan works normally or not and whether the environment temperature is high or not.
2.If the fan works normally and the environment temperature is normal, the PA temperature warning
still exist then may be the detection electric circuit breakdown, should replace the TRM/DTRM
module in time.
Alarm Description
Alarm Cause
Direct reason: Difference between PA output power and CIP control power is more than 3 db;
Possible reason: PA aging, power detecting circuit fault, or detecting threshold too narrow
3-159
Impact
User-defined.
Action
Alarm Description
Alarm Cause
PA power overvoltage
Impact
User-defined.
Action
check the check circuit of PA.if it has problem, please replace TRM.
3-160
Alarm Description
Alarm Cause
PA power undervoltage
Impact
User-defined.
Action
check the check circuit of PA.if it has problem, please replace TRM
Alarm Description
80w PA absent
Alarm Cause
PA not in position
Impact
User-defined.
Action
check the check circuit of PA.if it has problem, please replace TRM.
3-161
Alarm Description
TXIF unlock
Alarm Cause
Impact
Action
1. Restart the TRX, if the fault disappears, it indicates there is no fault in DTRU.
2. Check whether there is signal between Pinout 2 and 15 of HW line; if there is no signal, change
the HW line and continue with the test; if there is still no signal, it may be caused by CMB fault.
Test the 13M clock port on the equipment top, if there is signal, re-plug CMB board, if there is no
signal, it may be caused by CMB fault.
3. If the signal test is normal, re-plug this TRX. If there is still faults, change the fault TRX slot. If the
problem continues, change DTRU.
Alarm Description
TPF unlock
Alarm Cause
Impact
3-162
Action
1. Restart the TRX, if the fault disappears, it indicates there is no fault in DTRU.
2. Check whether there is signal between Pinout 2 and 15 of HW line; if there is no signal, change
the HW line and continue with the test; if there is still no signal, it may be caused by CMB fault.
Test the 13M clock port on the equipment top, if there is signal, re-plug CMB board, if there is no
signal, it may be caused by CMB fault.
3. If the signal test is normal, re-plug this TRX. If there is still faults, change the fault TRX slot. If the
problem continues, change DTRU.
Alarm Description
TXRF unlock
Alarm Cause
Impact
Action
1. Restart the TRX, if the fault disappears, it indicates there is no fault in DTRU.
2. Check whether there is signal between Pinout 2 and 15 of HW line; if there is no signal, change
the HW line and continue with the test; if there is still no signal, it may be caused by CMB fault.
Test the 13M clock port on the equipment top, if there is signal, re-plug CMB board, if there is no
signal, it may be caused by CMB fault.
3. If the signal test is normal, re-plug this TRX. If there is still faults, change the fault TRX slot. If the
problem continues, change DTRU.
3-163
Alarm Description
RXRF unlock
Alarm Cause
Impact
Action
1. See through LMT whether have the clock warning, if have, then replace the corresponding
module.If have not clock warning, then check whether have output or not from 13M clock of TP
front panel. If have not output, then can be thought that the clock fault between TPU and RCU and
should replace the DTRM module.
2.If still have fault and can't recover, then it is possible that local oscillator have fault, and should
replace the DTRM in time.
Alarm Description
Alarm Cause
3-164
Impact
Action
1. Restart the TRX, if the fault disappears, it indicates there is no fault in DTRU.
2. Check whether there is signal between Pinout 2 and 15 of HW line; if there is no signal, change
the HW line and continue with the test; if there is still no signal, it may be caused by CMB fault.
Test the 13M clock port on the equipment top, if there is signal, re-plug CMB board, if there is no
signal, it may be caused by CMB fault.
3. If the signal test is normal, re-plug this TRX. If there is still faults, change the fault TRX slot. If the
problem continues, change DTRU.
Alarm Description
60 ms clock lost
Alarm Cause
Impact
Action
1. Check the configuration, if there are excessive standby racks configured, ignore this alarm.
2. Check whether the 60ms cables are connected properly, or whether the cables are broken.
Reconnect or change the 60ms cables to check whether the alarm is recovered.
3. Check whether the CMB of standby racks work normally. If it is not normal, recover CMB working
status to check whether the alarm is recovered.
3-165
Alarm Description
Alarm Cause
RF board 52 MHz clock receiving is abnormal, RF board 52 MHz clock unit works abnormally
Impact
Action
1. Restart the TRX, if the fault disappears, it indicates there is no fault in DTRU.
2. Check whether there is signal between Pinout 2 and 15 of HW line; if there is no signal, change
the HW line and continue with the test; if there is still no signal, it may be caused by CMB fault.
Test the 13M clock port on the equipment top, if there is signal, re-plug CMB board, if there is no
signal, it may be caused by CMB fault.
3. If the signal test is normal, re-plug this TRX. If there is still faults, change the fault TRX slot. If the
problem continues, change DTRU.
Alarm Description
3-166
Alarm Cause
PA power overvoltage
Impact
The PA may be broken and the modulation module may switch off the power output for protection.
Action
Check whether the PA examination electric circuit break down or not, if have the fault, should replace
the DTRM in time
Alarm Description
PA power undervoltage alarm
Alarm Cause
PA power undervoltage
Impact
The output power is faulty.
Action
Check whether the PA examination electric circuit break down or not, if have the fault, should replace
the DTRM in time
3-167
Alarm Description
PA VSWR alarm
Alarm Cause
Direct reason: reverse power is too high. Possible reason: open circuit or high resistance exists in
output end of PA
Impact
Action
1. Check whether the PA output connects the electric cable tightly, if not, connects the PA output
and the electric cable tightly.
2. If still break down then should replace the DTRM module in time.
Alarm Description
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, environment temperature too high, and detecting circuit fault, etc
Impact
The DTRU still operates properly but the performance of the PA is deteriorated drastically.
3-168
Action
1.Check whether fan works normally or not and whether the environment temperature is high or not.
2.If the fan works normally and the environment temperature is normal, the PA temperature warning
still exist then may be the detection electric circuit breakdown, continue to observe.
Alarm Description
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, environment temperature too high, and detecting circuit fault, etc
Impact
The power output of the DTRU is switched off for protection and the performance of the PA is
deteriorated drastically.
Action
1.Check whether fan works normally or not and whether the environment temperature is high or not.
2.If the fan works normally and the environment temperature is normal, the PA temperature warning
still exist then may be the detection electric circuit breakdown, should replace the DTRM module in
time.
3-169
Alarm Description
Alarm Cause
Direct reason: Difference between PA output power and CHP control power is more than 3 db;
Possible reason: PA aging, power detecting circuit fault, detecting threshold too narrow
Impact
The DTRU board may fail to operate and the power is out of control.
Action
Alarm Description
Alarm Cause
Impact
The TRM/DTRU boards fail to operate. Cell services may also be affected if the TRM/DTRU is
configured as BCCH.
Action
3-170
Alarm Description
Alarm Cause
Impact
The power output of the TRM/DTRU is switched off for protection and the performance of the RTU is
deteriorated drastically.
Action
1.To detect the whether the fans are running and the electric power source is overheat.
2.If the fans are running and the electric power source isn't overheat, maybe there is something wrong
in the error-detector circuit.
Alarm Description
Alarm Cause
3-171
Impact
Action
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
3-172
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and replace the heat exchanger.
3-173
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
Impact
Action
3-174
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and handle the fault.
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and handle the fault.
3-175
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and replace the lightning protector.
Alarm Description
Alarm Cause
Impact
3-176
Action
Perform on-site check immediately to find fault cause and close the back door.
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and close the front door.
Alarm Description
Alarm Cause
3-177
Impact
Action
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
3-178
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and replace the heat exchanger.
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and replace the heat exchanger.
3-179
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and replace the heat exchanger.
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and replace the heat exchanger.
3-180
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and replace the heat exchanger.
Alarm Description
Alarm Cause
Impact
3-181
Action
Perform on-site check immediately to find fault cause and handle the fault.
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and handle the fault.
Alarm Description
Alarm Cause
3-182
Impact
Action
Perform on-site check immediately to find fault cause and replace the fan.
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and replace the fan.
Alarm Description
3-183
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and replace the fan.
Alarm Description
Alarm Cause
Impact
Action
Perform on-site check immediately to find fault cause and handle the fault.
3-184
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Alarm Description
Alarm Cause
Impact
Action
3-185
Alarm Description
Inner fan 1 alarm (for M8202)
Alarm Cause
Fan stops rotating due to fault
Impact
The temperature in the cabinet is too high.
Action
1. Check the alarm connection and eliminate the malfunction;
2. Check the fan and maintain the fault; 3. Check the collection system of the dTPB board and
replace the wrong one.
Alarm Description
Outer fan 2 and fan 4 alarm (for M8202)
Alarm Cause
Fan stops rotating due to fault
Impact
The temperature in the cabinet is too high.
3-186
Action
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
3-187
Alarm Cause
Fan fault or module temperature too high
Impact
Performance is reduced due to too high temperature of the TRM/DTRU boards.
Action
Check the environment temperature, if the temperature is normal, keep on observing while other
modules works normally, otherwise, improve the equipment working conditions.
Alarm Description
Rack temperature major alarm
Alarm Cause
Fan fault or module temperature too high
Impact
Performance is reduced because the equipment is damaged.
Action
Check the environment temperature, if the temperature is normal, keep on observing while other
modules works normally, otherwise, improve the equipment working conditions.
3-188
Alarm Description
Alarm Cause
Impact
Too high temperature in the cabinet may result in deteriorated performance and shorter service life
of the devices.
Action
Alarm Description
Alarm Cause
Impact
Too high temperature in the cabinet may result in deteriorated performance and shorter service life
of the devices.
3-189
Action
Alarm Description
Alarm Cause
Impact
Too high temperature in the cabinet may result in deteriorated performance and shorter service life
of the devices.
Action
3-190
Alarm Description
Alarm Cause
Impact
Too high temperature in the cabinet may result in deteriorated performance and shorter service life
of the devices.
Action
Alarm Description
Alarm Cause
Impact
Too high temperature in the cabinet may result in deteriorated performance and shorter service life
of the devices.
Action
3-191
Alarm Description
Alarm Cause
Impact
Too high temperature in the cabinet may result in deteriorated performance and shorter service life
of the devices.
Action
Alarm Description
Alarm Cause
3-192
Impact
Too high temperature in the cabinet may result in deteriorated performance and shorter service life
of the devices.
Action
Alarm Description
Alarm Cause
Impact
Too high temperature in the cabinet may result in deteriorated performance and shorter service life
of the devices.
Action
3-193
Alarm Description
Alarm Cause
Impact
Too high temperature in the cabinet may result in deteriorated performance and shorter service life
of the devices.
Action
Alarm Description
Alarm Cause
Impact
Action
3-194
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Alarm Description
Alarm Cause
Impact
User-defined.
3-195
Action
Switch to the slave circuit board as quickly as possible. If Necessarily, to replace the CCI circuit board.
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Alarm Description
3-196
Alarm Cause
Impact
User-defined.
Action
Alarm Description
Alarm Cause
Impact
User-defined.
Action
3-197
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Exam the backboard and SERDES chip in the relevant GBP board.
3-198
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Alarm Description
Alarm Cause
Impact
Action
3-199
Alarm Description
Alarm Cause
Impact
Action
1. Check if much dust result in the slow rotate speed of the fan or not.
2. If not, exchange new fan frame.
Alarm Description
Alarm Cause
Impact
This fault has no impact on heat dissipation, but the fan fails to be controlled.
3-200
Action
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
3-201
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
Impact
User-defined.
Action
3-202
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Alarm Description
Alarm Cause
clock lost
Impact
User-defined.
Action
If there is 13M or 61.44M clock lost alarm in CCI board, and there is alarm all the same after reset the
board, please exam the clock source; If no 13M or 61.44M clock lost alarm, and there is alarm after
reset GBP all the same, please exam the LVDS access.
3-203
Alarm Description
60ms clock lost alarm
Alarm Cause
FR or FN error
Impact
User-defined.
Action
If there is FR or FN error in the CCI, and there is error all the same after reset the CCI, please
exam the hardware; If there is not FR or FN error in the CCI, and there is 60ms clock lost alarm
all the same, please exam the LVDS access.
Alarm Description
26MHz and 52MHz lost of clock alarm
Alarm Cause
the loop of clock is unlock
Impact
User-defined.
3-204
Action
If there is 13M clock lost alarm in the CCI, and there is alarm all the same after reset CCI, please
exam the clock source; if there is not 13M clock lost alarm in the CCI, and there is clock lost alarm all
the same after reset GBP, please exam 13M clock LVDS access. If there is no problem with the LVDS
access, please replace the FPGA PLL that is invalid.
Alarm Description
Alarm Cause
Impact
User-defined.
Action
If there is up 60ms super frame synchronization head exam failing alarm in the CCI, and there
is alarm all the same after reset CCI, please exam its hardware. If no up 60ms super frame
synchronization head exam failing alarm, and there is alarm all the same after reset GBP, please
exam the LVDS access.
3-205
Alarm Description
Alarm Cause
Impact
User-defined.
Action
None
Alarm Description
Alarm Cause
Impact
User-defined.
Action
If it is of no effect to reset GBP and CCI, please exam the LVDS data format from CCI, else to
replace the LVDS.
3-206
Alarm Description
FN error alarm
Alarm Cause
Impact
User-defined.
Action
If there is FN error the CCI, and there is error all the same after reset CCI, please exam the hardware.
If no FN error, but there is FN error after reset GBP, exam the LVDS access.
Alarm Description
Alarm Cause
Impact
The sensitivity and coverage of the receiver antenna decreases because one of the diversities is faulty.
3-207
Action
Reset the TRX; if there is a fault, change the slot; if problem remains, change DTRU.
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
3-208
Impact
The IP ABIS function is partially supported and some carrier frequencies are not available.
Action
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
3-209
Alarm Cause
HDLC break off between CMB and FIB;CMB or FIB hardware error
Impact
Data fails to be transmitted between the CMB and FIB.
Action
1.watch cmb or fib work or not
2.if cmb or fib doesn't work, reset it
3.if alarm does not restore for a long time, please change a new cmb or fib
Alarm Description
FIB configure wrong
Alarm Cause
parameter Configuration over time or wrong
Impact
This alarm seldom occurs because the back end of the BSC generally checks data validity before
data synchronization.
Action
wait for ten minutes, if alarm still does not restore, ismg configure parameter again, and synchronize
to the site. If problem remain, just change a new fib
3-210
Alarm Description
Alarm Cause
Impact
Action
1.wait for ten minute, and watch whether alarm restore or not
2.ifalarm does not restore for a long time, please pull out the fib board and put it in to slot again
when service not too busy
3.if alarm remain after reset fib, please reset cmb when service not too busy
4.if alarm remain please change a new fib
5.if software has bug, please update to the latest
Alarm Description
Alarm Cause
Impact
Services are affected because the LNA of the cell fails to operate properly.
3-211
Action
Alarm Description
Alarm Cause
Impact
Services are affected because the LNA of the cell fails to operate properly.
Action
Alarm Description
Alarm Cause
3-212
Impact
The DTRU board fails to operate. Cell services may also be affected if the DTRU is configured
as BCCH.
Action
Alarm Description
Alarm Cause
Impact
The DTRU board fails to operate. Cell services may also be affected if the DTRU is configured
as BCCH.
Action
3-213
Alarm Description
5v voltage alarm
Alarm Cause
Impact
The DTRU board fails to operate. Cell services may also be affected if the DTRU is configured
as BCCH.
Action
Alarm Description
Alarm Cause
Impact
Action
3-214
Alarm Description
Alarm Cause
Not support GPS synchronization, GPS clock synchronization failed or GPS fault
Impact
Action
1. Check whether the current CMB board supports GPS synchronization. If not, replace it with the
new one supporting GPS. 2.To check EIB/FIB if support GPS or not 3.Change EIB/FIB
Alarm Description
Alarm Cause
Impact
3-215
Action
Alarm Description
Alarm Cause
Impact
Action
3-216
Alarm Description
Alarm Cause
Impact
Action
1. Check cable connection from antennas to EIB or FIB, include GPSSP if short or not.
2. Check the cable between EIB/FIB and the top of equipment.
3. Check EIB/FIB, if something is wrong in it, replace the relevant unit.
Alarm Description
Alarm Cause
Impact
Action
3-217
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
Impact
3-218
Action
Alarm Description
Alarm Cause
Impact
Action
3-219
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
Impact
Action
3-220
Alarm Description
Access iBSC failure
Alarm Cause
Authentication failed or unconnected response
Impact
User-defined.
Action
1.Authentication again
2.Check physical link
Alarm Description
Control link broken
Alarm Cause
Communication broken between
BTS and BSC
Impact
User-defined.
3-221
Action
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Alarm Description
3-222
Alarm Cause
the transmission line is broken
Impact
User-defined.
Action
check the transmission line
Alarm Description
Parameter configuration mismatch
Alarm Cause
iBSC parameters configuration
failed, time-out or broken links
Impact
User-defined.
Action
configuration
parameter again.
3-223
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Alarm Description
Alarm Cause
Impact
User-defined.
Action
3-224
Alarm Description
Tx PLL unlock
Alarm Cause
Clock signal instability or PLL failed
Impact
User-defined.
Action
Forbid TRM, send
warning information
Alarm Description
Wrong parameter configuration for EEPROM
Alarm Cause
EEPROM hardware failed or previously written into the EEPROM invalid parameters, resulting in
EEPROM RF parameters can not read.
Impact
User-defined.
3-225
Action
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Reset HBTS, Download DSP software version again.if the alarm is not restored alarm, replace HBTS
Alarm Description
3-226
Alarm Cause
DSP programming error
Impact
User-defined.
Action
Reset DSP, load DSP software version, configuration CHP parameters.
Alarm Description
FPGA interface fault
Alarm Cause
DSP and FPGA interface interruption
Impact
User-defined.
Action
load FPGA version again, reset HBTS,
replace HBTS
3-227
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Reset HBTS
Alarm Description
Alarm Cause
Impact
User-defined.
Action
3-228
Alarm Description
Alarm Cause
HBTS can not get to the IP address from the DNS server
Impact
User-defined.
Action
Alarm Description
Alarm Cause
HBTS can not get to the IP address from the DHCP server
Impact
User-defined.
3-229
Action
Alarm Description
IPSec failure
Alarm Cause
Impact
User-defined.
Action
Alarm Description
Alarm Cause
3-230
Impact
User-defined.
Action
Alarm Description
Alarm Cause
Impact
User-defined.
Action
Configuration the IP address, subnet mask, gateway, port of iBSC and HBTS by LMT.
3-231
Alarm Description
Over temperature
Alarm Cause
Over temperature
Impact
User-defined.
Action
Alarm Description
Voltage abnormity
Alarm Cause
Voltage abnormity
Impact
User-defined.
Action
Check power
3-232
Alarm Description
Alarm Cause
Abis link on the earth surface is broken, then the service of satellite-backup site changes to the
satellite abis link
Impact
This fault has no impact on a service if the service is successfully switched over.
Action
check the abis link on the earth surface, and restore it as soon as possible
Alarm Description
Alarm Cause
Impact
Action
3-233
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
Impact
3-234
Action
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
3-235
Impact
Action
Alarm Description
Alarm Cause
Impact
The backup satellite link of the E1 BTS may fail to operate properly.
Action
Alarm Description
3-236
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
Impact
Action
3-237
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
Impact
Action
3-238
Alarm Description
Alarm Cause
Impact
Action
Alarm Description
Alarm Cause
AC mains failure
Impact
User-defined.
Action
check AC
3-239
Alarm Description
Alarm Cause
Impact
Action
Code: 198022784
Severity: Minor
Alarm Description
3-240
Alarm Cause
Impact
All services on the path relating to the BFD session will be switched to the standby path. Service
interruption will occur if no standby path exists.
Action
Check alarm details on the NMS Alarm Management interface to find the source address and the
destination address of the BFD session. The source address refers to the address of local equipment.
The destination address refers to the address of the opposite BFD session equipment.
1. Check the status of the line card at the local end. If the line card restarts repeatedly, replace it
and power on.
2. Check the physical connection between the BFD session-related port and the local line card. If the
connection is loose or broken, tighten or replace the cable. If the port indicator is on, it means the
physical connection is normal.
3. Ping intermediate and termination equipment in turn with correct IP address.
i. Telnet to the interface board to check the link by making a ping test. For example, if the destination
address is 2.2.2.10, enter the following command in the telnet interface.
brs_ping_b "2.2.2.10"
ii. Wait for 5 seconds, and then enter the next command.
BrsShowLog "ICMP"
a. If "PING===>destine 2.2.2.10 timeout" displays on the screen, it means the response times out.
b. If "ping_receive:Reply from 2.2.2.10: bytes=60 time<1ms" displays on the screen, it means the link
is normal.
iii. In case of timeout, check if the related route and address are configured correctly. If not, correct
the reconfiguration and do a ping test again.
iv. If the route/address is configured correctly but the repsonse still times out, it means a link is broken
or the intermediate equipment is faulty. In this case, check to see if there is any broken network
cable, loose connection or abnormal equipment along the BFD session path. If yes, take necessary
actions, such as replacing the broken cable, tightening the connection, or repairing or replacing the
fault equipment, to solve the problem.
4. If the ping test indicates that packets can be received and sent normally at both ends, check to see
if the BFD session at both ends is configured correctly by performing the following steps:
i. Check the configuration of BFD session on the NMS Configuration Management interface to
ensure the BFD switch is in "enabled" status.
ii. Make sure that the BFD session is configured with the same working mode at both sides.
iii. Make sure that at least one device plays an "active" role for the BFD session.
3-241
iv. Make sure that the BFD session exists at both ends, and that the source and the destination
IP addresses are matched.
v. Make sure that the hop mode (single hop/multi-hop) is consistent at both ends.
vi. Make sure that the authentication information is consistent at both ends.
5. Reboot the board where the interface is located.
Code: 198066029
Severity: Major
Alarm Description
Alarm Cause
1. The alarm occurs in PPP port creating, modifying, deleting when PPP port is created by command.
2. The alarm occurs once in PPP port during board power-on, and recovers after successful PPP
negotiation.
3. Physical link is down, or link transmission quality is poor.
4. Adjustment of PPP link parameter leads to link re-negotiation, causing the alarm.
Impact
Action
Check alarm details on the NMS Alarm Management interface to find the faulty PPP port ID.
1. Check the cable connections at both ends to see if they are loose or broken. If yes, tighten the
connection or replace the broken cable.
2. Refer to the networking plan to check if the E1 cable is correctly connected.
3. Click IPOverE1 Configuration on the NMS Configuration Management interface to check E1 ID and
time slot. Make sure that the time slot configuration is consistent at both ends.
4. Check PPP parameters on the NMS Configuration Management interface to ensure that the
configuration is consistent at both ends.
5. Check the connection relation of DT and EIPI on the NMS Configuration Management interface to
ensure that the PPP port configuration is consistent at both ends.
3-242
Code: 198066026
Severity: Major
Alarm Description
Alarm Cause
Impact
If multiple paths are available for the association and there exists normal path, relevant services will
not be affected.
If merely one path is available for the association, all services on the association is down.
Action
On NMS fault management interface, view alarm Details, where information of association ID, local
address, and remote address is given.
1. On NMS configuration management interface (static route), query the route information of the
remote address. Locate the out port according to the route information. Check if network cable of the
out port is disconnected or loose. If yes, unplug and plug the cable or replace the cable.
2. On NMS configuration management interface (SCTP association configuration), query the ID of
the module where the association is located. Check if the following alarm occurs in the relevant
board. If yes, refer to the corresponding alarm handling suggestion.
Related alarm: 198066003 Control plane communication abnormal between board and its home
module
3. On NMS configuration management interface (static route), query if the route to the remote
address of the association is configured. If not, add the configuration.
4. Check the intermediate equipment on association path. If the routes to local address and remote
address of the association are not configured, add the configuration according to equipment
operation manual.
5. Check at opposite end if the route to the local address of the association is configured. If not,
add the configuration.
3-243
Code: 198029953
Severity: Minor
Alarm Description
Alarm Cause
The local port state is loop back because the peer port starts Ethernet OAM loop back request
of 802.3ah.
Impact
The Ethernet link which is in loop back test can't bear service data.
Action
Check if the peer port has started Ethernet OAM loop back test. If yes, stop it, if no, disable local port
Ethernet OAM.
3.2.5 198005666 The number of the error packets from MAC port
exceeds the threshold
Alarm Information
Code: 198005666
Name: The number of the error packets from MAC port exceeds the threshold
Severity: Minor
Alarm Description
The number of the error packets from MAC port exceeds the threshold
3-244
Alarm Cause
The number of the error packets from MAC port exceeds the threshold.
Impact
Action
1.Check whether the connection between this port and the peer port is correct.
Y->Go to "2"
N->Check whether the cable connecting two ports is damaged. It is recommended to replace a new
cable. If the alarm disappears: Y-> End, N-> Go to "2".
2.Try to replace the network interface on the peer end and then check if the alarm disappears.
Y->End.
N->Go to "3"
3.Try to replace the board or the network interface on the local end and then check if the alarm
disappears.
Y->End.
N->Please contact the next level of maintenance support.
Code: 198000519
Severity: Major
Alarm Description
Trunk error
3-245
Alarm Cause
Impact
The trunk equipment fails to work normally. All services based on the trunk are interrupted.
Action
1. Check whether the alarm is caused by local end or opposite end via meter measurement or
loop test.
Meter Measurement
Use a trunk test meter to test whether the trunk receiving signals at local end are normal. If yes, fault
might lie in local equipment. If no, troubleshoot at opposite end.
Loop test
Perform trunk self-loop at local end. If the alarm persists, fault might lie in local equipment. If the
alarm disappears, troubleshoot at opposite end.
2. Replace trunk cable.
3. Replace the board.
Code: 198000520
Severity: Major
Alarm Description
Trunk abnormal
3-246
Alarm Cause
1. Trunk frame formats at local end and at opposite end are inconsistent.
2. The transmitting end of opposite trunk equipment is faulty.
3. Local trunk equipment is faulty.
4. Equipment grounding at both ends is bad.
5. Impedance mismatch occurs.
Impact
Action
Alarm details are displayed in NMS Alarm Management interface, where fault type is given. You can
easily find handling suggestions according to the fault type.
The handling suggestions for each fault type are described as below:
1.Loss of E1 trunk frame, loss of E1 trunk multi-frame, E1 trunk alarm indication
i. In NMS Configuration Management interface, right click the board and select Subunit Configuration
to check whether frame format at both ends is the same.
ii. In NMS Configuration Management interface, right click the board and select Subunit Configuration
to check whether impedance is correct.
iii. Check whether the grounding at both ends is proper.
iv. If possible, locate alarm position, either at local end or at opposite end, by means of measurement
instrument, loopback test, or board/cable replacement.
2. E1 trunk receives an alarm indication from opposite end.
Check the alarm status of opposite end. Because the alarm indication is sent from opposite end,
please solve the opposite-end problem first.
Code: 198015617
Severity: Minor
Alarm Description
The number of hardware error frames that the port received during specified time exceeds the
threshold
3-247
Alarm Cause
Impact
Datagram reception of the board is affected. The service on this port might be unstable. Worst of all,
all services on the board might be interrupted.
Action
Code: 198015618
Severity: Minor
Alarm Description
The number of hardware error frames that the port received during specified time exceeds the
threshold
Alarm Cause
Impact
Datagram reception of the board is affected. The service on the board might be unstable.
3-248
Action
1. Pull out and insert the fiber/network cables to check if the fault is eliminated.
Y-> Finish the alarm handling.
N-> go to "2".
2. Replace fiber/network cables to check if the fault is eliminated.
Y-> Finish the alarm handling.
N-> go to "3".
3. Restart the board to check if the fault is eliminated.
Y-> Finish the alarm handling.
N-> go to "4".
4. Pull out/insert the board to check if the fault is eliminated.
Y-> Finish the alarm handling.
N-> go to "5".
5. Replace the board to check if the fault is eliminated.
Y-> Finish the alarm handling.
N-> For other reasons, please contact the next level of maintenance support.
Code: 198015873
Severity: Major
Alarm Description
The number of frames of CSIX horizontal parity check error received during specified time exceeds
the threshold.
Alarm Cause
Impact
If the fault lies in PSN board, service of the entire RNC NE will become unstable. If the alarm persists,
all services will be interrupted.
If the fault lies in the board where the alarm is declared, only the services on this board are affected.
3-249
Action
1. Check if the following alarm exists in PSN board at the same shelf. If yes, refer to the
corresponding alarm handling suggestion.
Related alarm: 198019456 All high-speed links between line card and package switching board
are out of synchronism
2. Unplug and plug board.
3. Replace board.
Code: 198003841
Severity: Major
Alarm Description
The RUDP of the control plane retransmission ratio over the threshold
Alarm Cause
There are some badly-touched boards in the system environment and the retransfer-ratio of RUDP
packets increases.
Impact
Action
Make records of the alarm information and contact the next level of maintenance support.
Code: 198005651
3-250
Severity: Major
Alarm Description
Alarm Cause
Impact
Action
Code: 198066003
Name: Control plane communication is abnormal between board and its home module
Severity: Minor
Alarm Description
3-251
Alarm Cause
Impact
Action
Code: 198005378
Severity: Major
Alarm Description
Alarm Cause
Impact
3-252
Action
1. Check the local board for the Related Alarms. Perform the recommended solution to process
the possible alarms.
Related Alarms:
198001286 Loss of clock when input to board
198005646 Phase-lock loop unlock
2. Check the clock board for the Related Alarms. Perform the recommended solution to process
the possible alarms.
Related Alarms:
198026133 Output clock lost
198026129 Clock reference source lost (Level 1 alarm)
198026128 Clock reference source lost (Level 2 alarm)
198026127 Clock reference source lost (Level 3 alarm)
3. Open the Configuration Management window and check whether the SDTB/SDTB2 has configured
APS while the active/standby board is configure.
How to check APS protection configuration: open the rack map on the Configuration Management
window, find the SDTB/SDTB2 board, right click to pop up shortcut menu, and select Optical port
APS Protection.
4. Replace the board.
5. Replace the slot.
6. Replace the UIM/GUIM in the same shelf.
Code: 198066004
Severity: Major
Alarm Description
Alarm Cause
3-253
Impact
The board is blocked so that it can not provide functions. Furthermore, all services under the relevant
module become unavailable.
Action
Code: 198005382
Severity: Major
Alarm Description
Alarm Cause
1. The power board is not connected to the OMP or the connection is wrong.
2. The power board locates in a rack. The configured rack number is different from that where DIP
switch of the power board locates.
Impact
The system can not monitor the status of power supply and environmental situation. However,
there is no impact on services.
Action
1. Reconnect the serial cable between the power board and OMP.
2. Make sure the rack number configured for the rack in which this power board locates is consistent
with the rack number switch set for the power board.
3-254
Code: 198005397
Severity: Major
Alarm Description
Alarm Cause
Impact
The channel between user plane processing board and signaling processing board is abnormal. This
causes degradation of QoS. In serious situation, services will be interrupted.
Action
1. In NMS Alarm Management interface, check whether the UIM/GUIM board of the same shelf has a
relevant alarm. If yes, please solve the problem according to corresponding handling suggestions.
Related alarm: 198002560 Board CPU overloaded
2. Replace the board.
3. Replace the UIM/GUIM of the same shelf.
4. Replace the slot.
Code: 198005401
Severity: Major
3-255
Alarm Description
Alarm Cause
Impact
Action
Alarm details are displayed in NMS Alarm Management interface, where fault type is given. You can
easily find handling suggestions according to the fault type.
The handling suggestions for each type are described as below.
1. Fault type: ATM abnormal
The internal related chip link of ATM processing board is abnormal. In this case, replace the board.
2. Fault type: L1 switch abnormal
The L1 media plane switching from UIM/GUIM/GUIM2 to GLI is abnormal. This is usually caused
by abnormal link between UIM/GUIM/GUIM2 and GLI. In this case, reconnect the cable between
UIM/GUIM/GUIM2 and GLI, or replace the cable. If optical fiber is used, replace the optical module.
Code: 198005122
Severity: Minor
Alarm Description
The control plane communication link between Master and Slave Boards is broken
3-256
Alarm Cause
1. The board is configured to be in active/standby mode, but the mate board is not in position.
2. Hardware Problem.
Impact
The active board can not communicate with the standby board. As a result, active/standby
changeover operation fails. There is no impact on services.
Action
1. Make sure the board is configured backup mode, and the master and slave boards are firmly in
place.
2. Check the opposite board for the related alarms. If there are related alarms,Perform the
recommended solution to process the possible alarms.
Description: 198066070, The board is offline or the CPU is in reset status for a long time
3. Replace the opposite board.
4. Change the slots of both the master and slave boards.
Code: 198005126
Severity: Critical
Alarm Description
The ports on the opposite board connected with a couple of ports on the local board are not paired
ports, or FE-C3/4 on RUIM1 backcard receives link detecting packets.
Alarm Cause
1. FE-C3/4 is used for FE routing port when RUIM1 rear board is used.
2. When CHUB is connected to UIM/GUIM/GUIM2, CHUB rear card (RCHUB1/RCHUB2) uses
discrete ports (e.g. port1/port3) to connect UIM rear card.
3. When UIM/GUIM/GUIM2 is connected to UIM/GUIM/GUIM2 CHUB, connections used for FE
routing connection are not in pairs (e.g.FE-C2/4).
4. When UIM is connected to UIM/CHUB, only one cable is used for FE inter-connection.
3-257
Impact
Control plane routing is disconnected; ports are switched over in cycle; all services on this shelf
are interrupted.
Action
Code: 198005127
Severity: Minor
Alarm Description
In a pair of FE port,one is link ok but another is link error, then the link error port need to be reported
alarm .
3-258
Alarm Cause
1. In a pair of FE ports, one has normal link but the other has link error.
2. The hardware is faulty.
Impact
Because one FE port has normal control plane link, services are not affected. However if this port is
faulty, services can not be switched to the other port, leading to service interruption.
Action
1. Check if only one cable is used to connect the port pair of the rear board to the peer-end FE port.
Ensure that both cables are connected to the peer end.
2. Reconnect the cables or replace the cables.
3. Replace the rear board.
4. Replace the board.
Code: 198005128
Severity: Minor
Alarm Description
Alarm Cause
Impact
Action
1. Check whether two shelf with same physical ID exists. Modify the switch of one of the two shelfs
and reset the shelf and board if such connection exists.
2. Check if the board link to the same board by different link type. Remove one of link type and reset
the board if such connection exists.
3-259
Code: 198066005
Severity: Minor
Alarm Description
Alarm Cause
Impact
Signaling data can not be sent to/received from the relevant subsystem. New service can not access
to the corresponding office. And existing services are interrupted abnormally.
Action
1. Check whether there is an office (the office that corresponds to the subsystem) inaccessible alarm.
If yes, solve the problem according to corresponding handling suggestion.
Related alarms:
i. 198066010 MTP3 office inaccessible
ii. 198066014 M3UA office inaccessible
2. Unblock the subsystem in dynamic data management.
3. In NMS Configuration Management interface, check the configuration of signaling point code
(for A) at A end. Is SCCP user included in user type configuration. If no, add the configuration.
Meanwhile, check the corresponding configuration at B end.
4. Check whether the status of signaling point subsystem (for B) is available at B end. If no, the
signaling point subsystem at B end must be out of service. Try to find the reason for this abnormal
status.
5. Check whether the signaling point subsystem (for B) is configured at B end. If no, add the
configuration at B end.
3-260
Code: 198066010
Severity: Major
Alarm Description
Alarm Cause
Impact
UE fails to receive/transmit messages from/to the relevant office. New services can not be accessed
to this office, and existing services are interrupted abnormally.
Action
1. Check whether there is an unavailable link alarm. If yes, please solve the problem according to
corresponding handling suggestions.
Related alarm: 198066011 MTP3 link unavailable
2. Check whether the configuration of office and link at opposite end is correct.
Code: 198066011
Severity: Minor
Alarm Description
3-261
Alarm Cause
Impact
If several MTP3 links are available for the office, services will not be affected. In the case of heavy
traffic, link congestion may occur, leading to loss of packets/calls and decreased PS call access rate.
If merely one link is available to the destination signalling point, the office may become inaccessible.
UE fails to receive/transmit messages from/to the relevant office. New services can not be accessed
to this office, and existing services are interrupted abnormally.
Action
1. IN NMS Configuration Management interface, click Signalling Link Configuration to check PVC
configuration. Make sure that the configuration of CVPI and CVCI should be the same at both ends.
2. In Dynamic Data Management, check link status. If it is interrupted and connected now and then, it
means the link unavailability is caused by MTP3 link test failure.
1) In NMS Configuration Management interface, check the configuration of signalling point code at
both ends. Ensure that the configuration is consistent at both ends.
2) In NMS Configuration Management interface, check the configuration of signalling link at both
ends. Ensure that the configuration of SLC (Signalling Link Code) is consistent at both ends.
3. Re-activate the link in Dynamic Data Management.
4. Check board status. If it is abnormal, reset or replace the board.
5. The opposite end has released the relevant link. Ask the opposite end to deal with the alarm as
link unavailable.
Code: 198066014
Severity: Major
Alarm Description
3-262
Alarm Cause
Impact
UE fails to receive/transmit messages from/to the relevant office. New services can not be accessed
to this office, and existing services are interrupted abnormally.
Action
1. Check whether there is an association link broken alarm. If yes, please solve the problem
according to corresponding handling suggestions.
Related alarm: 198066019 Association link broken
2. In NMS Configuration Management interface, view AS Static Information to check whether a
routing context exists. If yes, view the relevant configuration such as routing context ID, AS ID
and AS service mode.
The correct configuration is described below.
i. The routing context ID and AS service mode must be the same at both ends.
ii. AS ID must meet the following requirements: if ASP is configured for local end, SGP should
be configured for opposite end; if IPSP client is configured for local end, IPSP server should be
configured for opposite end.
3. Re-activate the ASP in Dynamic Data Management.
4. Check whether the configuration of relevant office is correct at opposite end.
Code: 198066019
Severity: Major
Alarm Description
3-263
Alarm Cause
Impact
If several association links are available to the destination office, service will not be affected. In the
case of heavy traffic, congestion of available association(s) might occur, leading to upper layer
call loss or increasing PS call access failures.
If merely one association link is available to the destination office, the office might become
inaccessible. Reception and sending of messages from/to the relevant office fail. Access of new
services under this office fails, and abnormal release of ongoing services occurs.
Action
Code: 198005129
Severity: Minor
Alarm Description
Alarm Cause
3-264
Impact
Action
Code: 198031744
Severity: Minor
Alarm Description
Alarm Cause
Impact
All services on the path relating to the BFD session will be switched to the standby path. Service
interruption will occur if no standby path exists.
3-265
Action
Check alarm details on the NMS Alarm Management interface to find the source address and the
destination address of the BFD session. The source address refers to the address of local equipment.
The destination address refers to the address of the opposite IPD session equipment.
1. Check the status of the line card at the local end. If the line card restarts repeatedly, replace it
and power on.
2. Check the physical connection between the IPD session-related port and the local line card. If the
connection is loose or broken, tighten or replace the cable. If the port indicator is on, it means the
physical connection is normal.
3. Ping intermediate and termination equipment in turn with correct IP address.
i. Telnet to the interface board to check the link by making a ping test. For example, if the destination
address is 2.2.2.10, enter the following command in the telnet interface.
brs_ping_b "2.2.2.10"
ii. Wait for 5 seconds, and then enter the next command.
BrsShowLog "ICMP"
a. If "PING===>destine 2.2.2.10 timeout" displays on the screen, it means the response times out.
b. If "ping_receive:Reply from 2.2.2.10: bytes=60 time<1ms" displays on the screen, it means the link
is normal.
iii. In case of timeout, check if the related route and address are configured correctly. If not, correct
the reconfiguration and do a ping test again.
iv. If the route/address is configured correctly but the response still times out, it means a link is broken
or the intermediate equipment is faulty. In this case, check to see if there is any broken network
cable, loose connection or abnormal equipment along the IPD session path. If yes, take necessary
actions, such as replacing the broken cable, tightening the connection, or repairing or replacing the
fault equipment, to solve the problem.
4. If the ping test indicates that packets can be received and sent normally at both ends, make sure
that the IPD session exists at the local end, and that the source and the destination IP addresses are
matched.
5. Reboot the board where the interface is located.
Code: 198105021
Severity: Minor
3-266
Alarm Description
The base station controller that has the "MultiPath Protection on Iub Interface" function enabled
detects that the IP service channel on the Iub interface is unavailable or the operation and
maintenance channel on the Iub interface is unavailable.
Alarm Cause
l The bottom-layer transmission is faulty, for example, the physical connection is broken.
l The configuration is not correct.
l The transport quality is degraded (for IP over Ethernet-based channels, the base station
controller detects that the packet loss rate is larger than 25 percent or receives less than three
keepalive packets consecutively. For IP over PPP-based channels, the base station controller
detects that the packet loss rate is larger than 70 percent or receives less than seven keepalive
packets consecutively).
l The hardware of the interface board on the local or peer end is faulty.
Impact
Related services and the operation and maintenance system may select another available IP channel
to transport data. If no available channel exists, services may be interrupted, or the connection
between the base station and network management system is broken.
Action
1. Check whether the following parameters are set in accordance with actual requirements:
l "Operation Maintenance Configuration(OmCon)". "OMCB Inner IP Address(InnerOm-
cbIpv4Addr)"
l "Operation Maintenance Configuration(OmCon)". "OMCB Inner IP Mask
Length(InnerIpv4MaskLen)"
l "Operation Maintenance Configuration(OmCon)". "OMCB Agent IPv4 Address to
NODEB(OmcbAgIpv4Addr)" (note:to IPv4 NODEB)
l "Operation Maintenance Configuration(OmCon)". "OMCB Agent IPv6 Address to
NODEB(OmcbAgIpv6Addr)" (note:to IPv6 NODEB)
Yes -> Step 3.
No -> Step 2.
2. Modify the above parameters as required or contact the maintenance personnel of the base
station to modify parameters. Wait for two minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether "Ip channel attribute" in the alarm information is "Service Channel".
Yes -> Step 4.
No -> Step 6.
4. Check whether the following parameters of the "Iub Transmission Path(UIubTrPath)" object are
set as required in accordance with "ANE id" and "Ip domain id or OMCB path id" in the alarm
information:
3-267
Code: 198105035
Name: The communication link between LogService board and OMP is broken
3-268
Severity: Minor
Alarm Description
The OMP detects an interruption of the link with the log server board.
Alarm Cause
Impact
The OMM fails to obtain the signaling tracing data, and the NDS server fails to obtain the network
optimization data.
Action
Alarm Description
3-269
Alarm Cause
Impact
BTS break-down
Action
If the new Abis link. Please synchronize and wait with no other operation, the alarm will resume
after 1 minute.
If master/slave change happened before, the alarm will resume after 1 minute, no need any operation.
Check the board has alarm "2560 Board cpu overload", please deal with first.
Alarm Description
Alarm Cause
Impact
Action
3-270
Alarm Description
Alarm Cause
The traffic flow carried by the MTP2 is excessive under the condition of current link bandwidth. It
exceeds the alarm threshold of link transmission load. The alarm threshold is related to MITP2 link
type. For 64K link, the alarm threshold is: bandwidth occupation ratio reaches 0.8. For N*64k or 2M
link, the alarm threshold is: bandwidth occupation ratio reaches 0.6.
Impact
If MTP2 link is overloaded for quite a long time, the signalling link will be congested. As a result,
service messages will be lost by MTP2 and the service will be interrupted.
Action
1. Add links to the office that is in service for the congested link.
2. Take the following measures to improve transmission quality of physical links.
Replace bottom layer lines.
Ensure that connector contact and cable connection are normal.
Alarm Description
3-271
Alarm Cause
The traffic flow carried by the MTP2 is excessive under the condition of current link bandwidth. It
exceeds the alarm threshold of link transmission load. The alarm threshold is related to MITP2 link
type. For 64K link, the alarm threshold is: bandwidth occupation ratio reaches 0.8. For N*64k or 2M
link, the alarm threshold is: bandwidth occupation ratio reaches 0.6.
Impact
This alarm has little impact on the local. If MTP2 link reception is overloaded for quite a long time,
the signalling reception will be congested. This may trigger the signalling flow control of MTP2
layer. In most serious case, package loss may occur, which leads to call loss or decrease of PS
access success rate.
Action
1. Add links to the office that is in service for the congested link.
2. Take the following measures to improve transmission quality of physical links.
Replace bottom layer lines.
Ensure that connector contact and cable connection are normal.
Alarm Description
Alarm Cause
Impact
Reception and sending of messages from/to the relevant cluster fail. Access of new service under
this cluster fails, and abnormal release of the ongoing service occurs.
3-272
Action
1. Check if there exists unavailable link alarm. If yes, refer to the corresponding alarm handling
suggestion.
Related alarms: 8400129 MTP3 link unavailable
2. Check if cluster and link configuration at opposite end is correct.
Alarm Description
This alarm is reported if the BSC detects that the Abis link of the super station is exchanged to
the satellite link or the standby link.
Alarm Cause
Impact
This alarm has no impact on the current operation of the system. However, the system reliability
will be decreased.
Action
1. Locate the alarm object, and check whether the object reports the following alarms:
198066026 Association path broken
198066019 Association link broken
198066029 PPP link broken
Yes -> Step 2.
No -> Step 3.
2. Handle the alarm, and check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Contact the next level of maintenance support.
3-273
Alarm Description
This alarm is reported if the BSC detects that the state of a cell is abnormal.
Alarm Cause
l The link between the BSC and the site that the cell belongs to is broken.
l The BCCH TRX of the cell is faulty.
l The cell is manually blocked.
l The configuration of related cell parameters is incorrect.
Impact
Action
1. Locate the site in accordance with "Site ID" in the alarm details, and check whether the following
alarms exist in the site:
198087336 Rack Abis control link broken
198087337 Site Abis control link broken
Yes -> Step 2.
No -> Step 3.
2. Handle the related alarms, and check whether this alarm is cleared.
Yes -> End.
No -> Step 3.
3. Query the "GSM Cell Configuration(GGsmCell)" object of the cell, check the following parameters
of the object, perform necessary operations as required, and check whether the alarm is cleared.
l "Cell management"
Execute the QRY CELL command to query the cell state in accordance with "Site ID" and
"Bts ID". If the cell is manually blocked, execute the UNB CELL command to unblock the cell.
l "TRX management"
If the BCCH TRX corresponding to the cell is manually blocked, execute the UNB FUTRX or
UNB CUTRX command to unblock the TRX.
If the CU or FU operation state of the TRX is blocked, which indicates a TRX fault, query and
clear related alarms in the base station. If the alarm persists, proceed to Step 4.
l "Channel Management"
3-274
If the BCCH timeslot corresponding to the cell is manually blocked, execute the UNB TS
command to unblock the timeslot.
Yes -> End.
No -> Step 4.
4. Contact the next level of maintenance support.
Alarm Description
This alarm is reported if the BSC detects that a TRX is manually blocked.
Alarm Cause
Impact
Action
1. Locate the blocked TRX in accordance with "Site ID", "Bts ID", and "Trx ID" in the alarm details,
and execute the UNB FUTRX or UNB CUTRX command to unblock the TRX. Check whether
the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Contact the next level of maintenance support.
3-275
Alarm Description
This alarm is reported if the BSC detects that the control link between the controller and a rack
is broken.
Alarm Cause
Impact
Action
1. 1. Locate "Site ID" in the alarm details, and check whether the corresponding site is required in
the network planning.
Yes -> Step 2.
No -> Delete the site configuration, or suppress the alarm. End alarm handling.
2. 2. Check whether the following association and PPP related alarms exist in accordance with "Site
ID" or "office information" in the alarm details.
198066019 Association link broken
198000519 Trunk error
198000520 Trunk abnormal
Yes -> Step 3.
No -> Step 4.
3. 3. Handle the related alarms, and check whether this alarm is cleared.
Yes -> End.
No -> Step 4.
4. 4. Contact the next level of maintenance support.
3-276
Alarm Description
This alarm is reported if the BSC detects LAPD link congestion between the rack and the BSC.
Alarm Cause
Impact
A severe loss of frames occurs on LAPD channels, which results in abnormal or even interrupted
communication. The quality of service degrades.
Action
1. Check whether enough LAPD channels are configured in accordance with the number of TRXs
configured on the site.
The recommended configuration is as follows:
- When 6 TRXs are configured, at least one LAPD channel must be configured.
- When 7 to 16 TRXs are configured, at least two LAPD channels must be configured.
- When 17 to 26 TRXs are configured, at least three LAPD channels must be configured.
- When 27 to 36 TRXs are configured, at least four LAPD channels must be configured.
Yes -> Step 3.
No -> Step 2.
2. Add one or more LADP channels as follows: In Configuration Management, view the attributes
of the CMB board on the rack diagram of the base station, and then add an "OMU slot number".
Check whether the alarm is cleared.
Yes -> End.
No -> Step 3.
3. Check whether the following alarm and notification exist in accordance with "Site ID" in the
alarm details or the object reporting the alarm:
198087102 Power overvoltage/undervoltage alarm
198000576 Loss of Frame on Trunk
Yes -> Step 4.
No -> Step 5.
4. Handle the related alarms, and check whether this alarm is cleared.
Yes -> End.
No -> Step 5.
5. Contact the next level of maintenance support.
3-277
Alarm Description
This alarm is reported if the BSC detects that the LAPD communication link of a base station is broken.
Alarm Cause
Impact
All cells of the site fail to provide any voice or data service.
Action
1. Locate "Site ID" in the alarm details, and check whether the corresponding site is required in
the network planning.
Yes -> Step 2.
No -> Delete the site configuration, or suppress the alarm. End alarm handling.
2. Check whether the following association and PPP related alarms exist in accordance with "Site
ID" or "office information" in the alarm details.
198066026 Association path broken
198066019 Association link broken
198066029 PPP link broken
Yes -> Step 3.
No -> Step 4.
3. Handle the related alarms, and check whether this alarm is cleared.
Yes -> End.
No -> Step 4.
4. Contact the next level of maintenance support.
3-278
Alarm Description
HW link broken
Alarm Cause
Impact
Action
1. Start HW self-loop test to check whether the cable connection goes wrong.
2. If all of DTRU fail to build link, re-plug CMB board.
3. If the software has problem, upgrade it.
Code: 198015360
Severity: Major
Alarm Description
Microcode is abnormal
3-279
Alarm Cause
The Network Processor hardware in the board (whose microcode is abnormal) is faulty.
Impact
Action
1. Wait for the board to reboot. If the alarm cannot be restored after board rebooting, unplug and
then plug the board.
2. If the alarm still cannot be restored, replace the board.
Code: 198023040
Severity: Major
Alarm Description
Alarm Cause
The current alarm board has too many alarms so that the relevant alarm pool is full.
Impact
Action
3-280
3.3.3 198066031 OMP alarm pool is full, unable to store any more
alarms.
Alarm Information
Code: 198066031
Name: OMP alarm pool is full, unable to store any more alarms.
Severity: Major
Alarm Description
Number of OMP alarms exceeds threshold
Alarm Cause
There are too many system alarms. The alarm pool is full of system alarms.
Impact
Alarms may be lost, but there is no impact on user services.
Action
1. Delete any temporarily useless virtual configuration resources.
2. On NMS fault management interface, delete some alarms which have small system impact.
Severity: Minor
Alarm Description
NTP time exceeds the threshold
Alarm Cause
1. Control-panel link between OMP and RPU board is down.
2. NTP time and local time differs greatly.
3-281
Impact
NTP time synchronization terminates, bringing in time deviation between the foreground and the
backgroundeffecting some servicessuch as charges, and leading to interruption of ongoing
services.
Action
On NMS fault management interface, check if the alarm related to RPU board exists. If yes, refer to
the corresponding alarm handling suggestion.
Related alarm: 198066004 Control plane communication abnormal between MP and OMP
Code: 198066027
Severity: Minor
Alarm Description
Alarm Cause
Impact
SNTP synchronization failure may cause time difference between system time and real time. For
example, the real time is 1:00 am, but the system time is 2:00 am. Since the system clock frequency
is correct, services will not be affected.
3-282
Action
Alarm details are displayed in NMS Alarm Management interface, where fault type is given. You can
easily find handling suggestions according to the fault type.
The handling suggestions for each type are described as below.
1. Invalid database configuration.
In NMS Configuration Management interface, click Network Element Ground Resource Management
to check whether the IP address of SNTP server is invalid, or SNTP synchronization period is wrong.
If the IP address of SNTP server is 255.255.255.255 or SNTP synchronization period is 0, please
correct the configuration.
2. Failure in getting time from SNTP server
1) Ensure that SNTP server exists and it works normally.
2) Ensure that the configured IP address of SNTP server in database is the same as its real IP
address.
Code: 198005387
Severity: Major
Alarm Description
Alarm Cause
Impact
Action
1. For CMP and SMP, reset the board through NMS man-machine command interface.
2. For OMP, set the start mode as "foreground start" on NMS and then reset the board.
Do as follows:
On NMS software version management interface, select the menu for querying foreground (that is,
RNC NE) board start mode. In the pop-up dialog box, set the start mode to "foreground start".
3-283
Code: 198005388
Severity: Major
Alarm Description
Alarm Cause
Impact
This alarm may cause OMP work abnormally, and the entire network element services are affected.
Action
1. Reset the active and standby OMPs through NMS man-machine command interface.
2. Replace the board.
Code: 198005398
Severity: Major
Alarm Description
Alarm Cause
The office ID of a shelf where DIP switch locates is different from that of a shelf where OMP locates.
3-284
Impact
The MAC address conflicts. The MAC and IP address verification fails. All boards on the shelf can
not be powered on. All services carried by the shelf are interrupted.
Action
By operating the hardware dial code key on the shelf, Set the office ID of the shelf where DIP switch
locates to be the same as that of OMP belonged shelf.
Code: 198005402
Severity: Major
Alarm Description
The Data from the OMP database is inconsistent with that previously saved on the OMP
Alarm Cause
After the start information of OMP is modified, the active and standby OMP boards are not restarted.
Impact
Action
Restart the active and the standby OMP boards at the same time through NMS man-machine
interface command .
Code: 198005649
3-285
Severity: Major
Alarm Description
Alarm Cause
1. The speed mode configuration of the port does not take effect.
2. The duplex mode configuration of the port does not take effect.
3. The master or slave mode configuration of the port does not take effect.
4. The auto negotiation mode configuration of the port does not take effect.
Above four points, the set work mode of the external port does not take effect due to faulty
performance of the chip on the local end or unsuccessful settings on the peer end.
Impact
1. The port fails to work in the preset mode. This causes the port to be unavailable and all services
of the port are interrupted.
2. For Auto mode, the bandwidth of the external port becomes insufficient. As a result, some services
of the port are interrupted.
Action
On NMS fault management interface, check the alarm details, which give the reasons of mode error.
You can quickly locate the handling method according to it.
The handling suggestions for each reason of mode error are as follows:
Speed mode error
1.Check the speed settings on the both end ports if they are correct and consistent.
Y->Go to "2".
N->Modify the speed settings, which the hardware supports on the both end, to make them be
consistent with each other, and then check the alarm if it is eliminated.
Y->End.
N->Go to "2".
2.Please contact the next level of maintenance support.
Duplex mode error
1.Check the duplex mode settings on the both ports end if they are correct and consistent.
Y->Go to "2".
N->Modify the duplex mode settings, which the hardware supports on the both end, to make them be
consistent with each other, and then check the alarm if it is eliminated.
Y->End.
N->Go to "2".
2.Please contact the next level of maintenance support.
GE port master or slave mode error
1.Check the master and slave mode settings on the both end ports if they are correct and consistent.
3-286
Y->Go to "2".
N->Modify the master or slave mode settings, which the hardware supports on the both end, to make
them match with each other, and then check the alarm if it is eliminated.
Y->End.
N->Go to "2".
2.Please contact the next level of maintenance support.
Auto negotiation failed
1.Check the work mode settings on the both end ports if they are correct and consistent, if one of
them is auto negotiation, the other one can not be force mode.
Y->Go to "2".
N->Modify the work mode settings, which the hardware supports on the both end, to make them be
consistent with each other, and then check the alarm if it is eliminated.
Y->End.
N->Go to "2".
2.Please contact the next level of maintenance support.
Code: 198005123
Severity: Minor
Alarm Description
The equipment type configured in the DB is inconsistent with the hardware device
Alarm Cause
Impact
The board fails to be normally powered on. The services carried by the board are interrupted.
3-287
Action
1. The NMS configuration management interface gives the rack diagram. Select the board and check
if the Basic Information and CPU Information of the rack are correct. If the settings are incorrect,
delete the board and create a new one.
2. Check if a correct board is inserted in the slot on the rack. If not, insert the correct one.
Code: 198066013
Severity: Major
Alarm Description
MTP3 link congest. The messages that MTP3 sent to MTP2 have reached a particular percentage in
MTP2 buffers and queues.
Alarm Cause
Impact
Link congestion will cause transmission delay. If congestion is not serious, services will not be
affected. However, if it is serious, packet loss or call loss may occur, and access success rate of
PS services may fall.
Action
1. Check the peak traffic of MTP3(B) signaling link performance statistics. If the payload reach to
6000, it's necessary to add links or increase the PVC bandwidth.
2. Check the physical connection, and check the following alarm. If there are some alarms as follows,
solve related alarms firstly.
(1) Fiber access:
1792 SDH/SONET faulty
1824 SDH/SONET exception
(2) E1 access:
519 trunk faulty
1026 E1 ATM cell synchronization failed
3-288
Code: 198066018
Severity: Minor
Alarm Description
Association congestion
Alarm Cause
1. Transmission quality of bottom layer link(include the physical links between interface board and
signal processing board inside network element and the physical links between interface board and
opposite network element) is poor.
2. Upper layer traffic in sending service data is heavy, confirming it by the traffic networking model.
Impact
Link congestion will cause transmission delay. If congestion is not serious, services will not be
affected. However, if it is serious, packet loss or call loss may occur, and access success rate of
PS services may fall.
Action
1. Check network cable connection. Ensure that the network cable is tightly inserted.
2. Add association links to the office that is in service for the congested association.
3. If intermediate equipment exists between local end and opposite end, check the transmission
quality of intermediate equipment.
Code: 198105027
Severity: Minor
3-289
Alarm Description
The user-plane processing board detects that the CPU is overloaded ("BGlobal(Bglobal)"."RUP
Congestion Threshold(RupCongestThr)").
Alarm Cause
Impact
Some users who are connected through the RUB may be rejected.
Action
Alarm Description
3-290
Alarm Cause
The transferred data records exceed the maximum capacity of the table, and the capacity of the
receiver memory file buffer is insufficient.
Impact
If the board is powering on, the excessive data records (beyond table capacity) are discarded.
Action
1. Lookup if the capacity of the table is correct, please make records of the alarm information and
contact the next level of maintenance support.
2. Synchronize the capacity tables, then synchronize all tables to the foreground and reboot the
board. If the alarm still has not restored, please make records of the alarm information and contact
the next level of maintenance support.
Alarm Description
Alarm Cause
T network fiber connection does not conform to optical interface connection relation configured on
the background.
Impact
Action
Modify the fiber connection or the connection configuration to keep the configuration consistent
with the physical connection.
3-291
Alarm Description
Alarm Cause
1. Appoint the version for OMP and select the option of restart after switch,but the version file have
existed on OMP's DOC0.2.Swtich the BOOT version.
Impact
The board version will not take effect if the board does not reset.
Action
Alarm Description
Alarm Cause
Impact
3-292
Action
Alarm Description
This alarm is reported if the BSC detects data errors in the following two processes:
- Power-on loading
- Data synchronization
Alarm Cause
Impact
Action
3-293
Alarm Description
This alarm is reported if the BSC detects that the service connection failure count of one board
exceeds the threshold.
Alarm Cause
Impact
Action
l If the alarm is reported that the cause of AIPB board alarm is 1 or the cause of DRTB/TIPB
board alarm is 2, the port number is allocated unsuccessfully. You need to query the network
management system and check whether the IPUDP resources assigned to the board is sufficient.
If the IPUDP resources are insufficient, you need increase the resources. Otherwise, contact the
next level of maintenance support.
l If the alarm is reported that the cause of AIPB board alarm is 3 or the cause of DRTB/TIPB board
alarm is 7, the next hop is obtained unsuccessfully. You need to check whether the version of the
base station is not compatible with the version of the BSC. If the version of the base station is not
compatible with the version of the BSC, you need to load the proper version for the base station.
If the version of the base station is compatible with the version of the BSC, you need to check the
route configuration of CN user plane. If the route configuration of CN user plane is incorrect, you
need to modify the configuration. Otherwise, contact the next level of maintenance support.
l If the alarm is reported that the cause of AIPB/BIPB board alarm is 4 or the cause of DRTB/TIPB
board alarm is 8, you need to check whether all VTCD boards and GLI boards are configured
properly and check whether the version is powered on properly. If there is anything wrong, you
need to make a modification. Otherwise, contact the next level of maintenance support.
3-294
Code: 198023296
Name: Inter-board message communication flow rate exceeds the alarm threshold
Severity: Minor
Alarm Description
The communication flow rate in input and output directions of the control plane exceeds the alarm
threshold
Alarm Cause
The configured alarm threshold is less than the usual inter-board communication traffic in input
and output directions of the board control plane.
Impact
Packet of the control plane loss might occur. No impact on user service.
Action
Code: 198066069
Name: The number of times of signaling data transfer exceeds the allowed threshold
of the license
Severity: Major
3-295
Alarm Description
Alarm Cause
The number of transfer that passes MTP3/M3UA/SCCP/SUA exceed the permission of license.
Impact
Action
Alarm Description
This alarm is reported if the BSC initiates flow control in "FUC control mode" upon receiving
"OVERLOAD" from the MSC through the A-interface.
The "FUC control mode" allows the base station to discard the access messages of some MSs as
required by the BSC.
Alarm Cause
Impact
Action
No action is required.
3-296
Alarm Description
This alarm is reported if the BSC initiates flow control in "FUC control mode" upon detecting that the
CPU load is above "GSM Logical Configuration(GBssFunction)"."Start limit of FUC flow control
for CPU overload(CpuFucCtlCpu)".
The "FUC control mode" allows the base station to discard the access messages of some MSs as
required by the BSC.
Alarm Cause
Impact
Some users fail to gain access to the system due to the flow control automatically initiated by the
BSC. If the traffic is still excessive after flow control, the CPU load may grow further. In this case,
the system may break down.
Action
1. 1. Query "Flow Control Level" in the alarm details. If the flow control level is five or lower, wait for
three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. 2. Execute the BLK FUTR or BLK CUTR command based on "Site ID", "Bts ID", and "Trx
ID" to block some cells. In this way, the access of some users can be limited to avoid system
breakdown caused by further increase of the CPU load. Check whether the alarm is cleared.
Yes -> Step 3.
No -> Step 2.
3. 3. Execute the UNB FUTRX or UNB CUTRX command to unblock some cells one batch at a
time based on "Site ID", "Bts ID", and "Trx ID". The alarm handling is completed.
3-297
Alarm Description
This alarm is reported if the BSC initiates flow control in "FUC control mode" upon detecting No.7
signaling point congestion on the A-interface.
The "FUC control mode" allows the base station to discard the access messages of some MSs as
required by the BSC.
Alarm Cause
Impact
Some users fail to gain access to the system due to the flow control automatically initiated by the
BSC. If the traffic is still excessive after flow control, the signaling on the A-interface may be blocked
and services may be interrupted.
Action
1. Query "Flow Control Level" in the alarm details. If the flow control level is five or lower, wait for
three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Execute the BLK FUTR or BLK CUTR command based on "Site ID", "Bts ID", and "Trx ID" to
block some cells. In this way, the access of some users can be limited to avoid A-interface
disconnection caused by further increase of the No.7 signaling load. Check whether the alarm
is cleared.
Yes -> Step 3.
No -> Step 2.
3. Execute the UNB FUTRX or UNB CUTRX command to unblock some cells one batch at a time
based on "Site ID", "Bts ID", and "Trx ID". The alarm handling is completed.
3-298
Alarm Description
This alarm is reported if the BSC initiates flow control in "system message control mode" upon
receiving "OVERLOAD" from the MSC through the A-interface.
The "system message control mode" allows the base station to deny the access of some MSs through
the system information broadcasted over the air interface.
Alarm Cause
Impact
Action
No action is required.
Alarm Description
This alarm is reported if the BSC initiates flow control in "system message control mode" upon
detecting that the CPU load is above "GSM Logical Configuration(GBssFunction)"."Start limit of
system message method for CPU overload(CpuSysInfoCtlCpu)".
The "system message control mode" allows the base station to deny the access of some MSs through
the system information broadcasted over the air interface.
3-299
Alarm Cause
Impact
Some users fail to gain access to the system due to the flow control automatically initiated by the
BSC. If the traffic is still excessive after flow control, the CPU load may grow further. In this case,
the system may break down.
Action
1. 1. Query "Flow Control Level" in the alarm details. If the flow control level is eight or lower, wait
for three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. 2. Execute the BLK CELL command to block some cells based on "Site ID" and "Bts ID" in the
alarm details. In this case, the access of some users can be limited to avoid system breakdown
caused by excessive CPU load. Check whether the alarm is cleared.
Yes -> Step 3.
No -> Step 2.
3. 3. Execute the UNB CELL command to unblock some cells based on "Site ID" and "Bts ID" in the
alarm details. The alarm handling is completed.
Alarm Description
This alarm is reported if the BSC initiates flow control in "system message control mode" upon
detecting No.7 signaling point congestion on the A-interface.
The "system message control mode" allows the base station to deny the access of some MSs through
the system information broadcasted over the air interface.
Alarm Cause
3-300
Impact
Some users fail to gain access to the system due to the flow control automatically initiated by the
BSC. If the traffic is still excessive after flow control, the signaling on the A-interface may be blocked
and services may be interrupted.
Action
1. Query "Flow Control Level" in the alarm details. If the flow control level is eight or lower, wait for
three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Execute the BLK CELL command to block some cells in accordance with "Site ID" and "Bts ID"
in the alarm details. In this case, the access of some users can be limited to avoid system
breakdown caused by excessive CPU load. Check whether the alarm is cleared.
Yes -> Step 3.
No -> Step 2.
3. Execute the UNB CELL command to unblock some cells in accordance with "Site ID" and "Bts
ID" in the alarm details. The alarm handling is completed.
Alarm Description
This alarm is reported if the BSC detects the RACH load of a cell exceeds the threshold ("GSM
Cell Configuration(GGsmCell)"."CCCH load indication (RACH)(CcchLoadINDThs_0)"), or the PCH
load of a cell exceeds the threshold ("GSM Cell Configuration(GGsmCell)"."CCCH load indication
(PCH)(CcchLoadINDThs_1)").
Alarm Cause
Impact
Some MS CS services under this cell fail to gain access to the system due to the flow control
automatically initiated by the BSC.
3-301
Action
1. Query "Flow Control Level" in the alarm details. If the flow control level is eight or lower, wait for
ten minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. If the alarm occurs frequently, contact network optimization engineers to:
- add CCCHs to the cell, or
- expand the capacity of the overloaded cell, or
- share the traffic.
Alarm Description
This alarm is reported if the BSC detects that all NSVCs of an NSE are in the "block" state.
Alarm Cause
Impact
Action
1. 1. Locate the alarm object in State Management, and query the state of NSCV link. Verify that
the state is "manual block".
Yes -> Step 2.
No -> Step 3.
2. 2. Execute the UNB NSVC command to unblock all NSVC links which are in the "manual
block" state and check whether the alarm is cleared in accordance with "SGSN ID", "NSE ID",
and "NSVC ID" in the alarm details.
Yes -> End.
No -> Step 3.
3. 3. Check whether the following alarms exist:
198087352 NSVC's E1 failure alarm
3-302
Alarm Description
This alarm is reported if the BSC detects that all NSVCs of an SGSN are in the "block" state.
Alarm Cause
Impact
Action
1. Execute the QRY NSV command to query the state of this NSVC link and check whether the state
is "manual block" in accordance with "SGSN ID", "NSE ID", and "NSVC ID" in the alarm details.
Yes -> Step 2.
No -> Step 3.
2. Execute the UNB NSVC command to unblock all NSVC links which are in the "manual block"
state and check whether the alarm is cleared in accordance with "SGSN ID", "NSE ID", and
"NSVC ID" in the alarm details.
Yes -> End.
No -> Step 3.
3. Check whether the following alarms exist:
198087352 NSVC's E1 failure alarm
198087465 NSVC's IP failure alarm
Yes -> Step 4.
3-303
No -> Step 5.
4. Handle the alarm, and check whether the alarm is cleared.
Yes -> End.
No -> Step 5.
5. Contact the next level of maintenance support.
Alarm Description
This alarm is reported if the BSC detects that the connection count of an Ethernet port on the BIPB
board exceeds the threshold (2500 routes).
Alarm Cause
Impact
Packet loss may occur on the Ethernet port and the service quality is degraded.
Action
3-304
Alarm Description
This alarm is reported if the BSC initiates flow control in "manual user access control mode".
"manual user access control mode" indicates that the network management system delivers flow
control parameters to the BSC and the BSC executes flow control unconditionally.
Alarm Cause
Impact
Action
No action is required.
Alarm Description
This alarm is reported if the BSC initiates flow control in "paging control mode" upon detecting that
the CPU load exceeds the threshold ("GSM Logical Configuration(GBssFunction).CPU threshold of
paging flow control(CpuPagingCtlCpu)").
"paging control mode" indicates that the BSC discards some paging messages.
Alarm Cause
Impact
Some users fail to gain access to the system due to the flow control automatically initiated by the
BSC. If the traffic is still excessive after flow control, the CPU load may grow further. In this case,
the system may break down.
3-305
Action
1. Execute the BLK CELL command to block some cells in accordance with "Site ID" and "Bts ID"
in the alarm details. Limit the access of some users to avoid system breakdown caused by
excessive CPU load. Check whether the alarm is cleared.
Yes -> Step 2.
No -> Step 1.
2. Execute the UNB CELL command to unblock some cells in accordance with "Site ID" and "Bts
ID" in the alarm details. The alarm handling is completed.
Alarm Description
This alarm is reported if the BSC detects that the state of A-interface trunk circuit is manually blocked.
Alarm Cause
Impact
Action
3-306
No -> Step 3.
3. Contact the next level of maintenance support.
Alarm Description
This alarm is reported if the BSC detects that the state of BVC is manually blocked.
Alarm Cause
Impact
Action
3-307
Alarm Description
This alarm is reported if the BSC initiates flow control in "FUC control mode" upon detecting inter-shelf
traffic overload in the system.
The "FUC control mode" allows the base station to discard the access messages of some mobile
phones as required by the BSC.
Alarm Cause
Impact
Action
1. 1. Query "Flow Control Level" in the alarm details. If the flow control level is five or lower, wait for
three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. 2. Execute the BLK CELL command to block some cells in accordance with "Site ID" and "Bts
ID" in the alarm details. Limit the access of some users to avoid system breakdown caused by
further increase of the inter-shelf traffic. Check whether the alarm is cleared.
Yes -> Step 3.
No -> Step 2.
3. 3. Execute the UNB CELL command to unblock some cells one batch at a time in accordance
with "Site ID" and "Bts ID" in the alarm details. The alarm handling is completed.
Alarm Description
This alarm is reported if the BSC initiates flow control in "system message control mode" upon
detecting inter-shelf traffic overload in the system.
The "system message control mode" allows the base station to deny the access of some MSs through
the system information broadcasted over the air interface.
3-308
Alarm Cause
Impact
Action
1. Query "Flow Control Level" in the alarm details. If the flow control level is eight or lower, wait for
three minutes, and check whether the alarm is cleared.
Yes -> End.
No -> Step 2.
2. Execute the BLK CELL command to block some cells in accordance with "Site ID" and "Bts ID"
in the alarm details. In this case, the access of some users can be limited to avoid system
breakdown caused by further increase of the inter-shelf traffic. Check whether the alarm is
cleared.
Yes -> Step 3.
No -> Step 2.
3. Execute the UNB CELL command to unblock some cells in accordance with "Site ID" and "Bts
ID" in the alarm details. The alarm handling is completed.
Alarm Description
This alarm is reported if the BSC detects that a timeslot of the air interface is manually blocked.
Alarm Cause
Impact
3-309
Action
Code: 198025856
Severity: Minor
Alarm Description
Alarm Cause
Impact
3-310
Action
1. In NMS Configuration Management interface, click Power Board Alarm Parameters to view the
upper threshold of rack temperature. If the configuration is unreasonable, please modify it. The
recommended value of upper threshold is 70 degrees in Celsius.
2. Check the thermometer in equipment room to see if the actual temperature is too high. If yes, take
necessary cooling measures.
3. Remove dust from air intake and outlet of the rack. Remove any obstacle nearby which may
affect ventilation.
4. Ensure that the rack fan works normally.
Code: 198025857
Severity: Minor
Alarm Description
Alarm Cause
1. Threshold is incorrect.
2. Temperature sensor is not working
3. External room heating control not working.
Impact
Action
1. In NMS Configuration Management interface, click Power Board Alarm Parameters to view the
lower threshold of rack temperature. If the configuration is unreasonable, please modify it. The
recommended value of lower threshold is 0 degrees Celsius.
2. Check the thermometer in equipment room to see if the actual temperature is too low. If yes,
take necessary warming measures.
3. Setting the sensor correctly.
3-311
Severity: Minor
Alarm Description
Room temperature is higher than high threshold
Alarm Cause
1. Threshold configuration is unreasonable.
2. Actual temperature in equipment room is too high.
Impact
1. If an unreasonable threshold is configured, services will not be affected.
2. If the alarm is caused by high room temperature, board may work abnormally and board services
may be interrupted.
Action
1. On NMS configuration management interface (power board alarm parameters), check the upper
limit of equipment room temperature. Modify the threshold value if the previous configuration is
unreasonable. The recommended high threshold value is 40.
2. Check the thermometer in equipment room to see if the actual temperature is too high. If yes, take
necessary cooling and ventilation measures.
Severity: Minor
Alarm Description
Room temperature is lower than low threshold
3-312
Alarm Cause
Impact
Action
1. In NMS Configuration Management interface, click Power Board Alarm Parameters to view the
lower threshold of room temperature. If the configuration is unreasonable, please modify it. The
recommended value of lower threshold is 0 degrees Celsius.
2. Check the thermometer in equipment room to see if the actual temperature is too low. If yes,
take necessary warming measures.
3. Setting the sensor correctly.
Code: 198025860
Severity: Minor
Alarm Description
Alarm Cause
Impact
3-313
Action
1. In NMS Configuration Management interface, click Power Board Alarm Parameters to view the
upper threshold of rack voltage. If the configuration is unreasonable, please modify it. For 48V power
supply, the recommended value of upper threshold is 57V; for 60V power supply, the recommended
value is 72.
2. Find out which line voltage exceeds upper threshold by using the voltage index given in alarm
details. Regulator through the power supply equipment to lower down the input voltage of this line.
Code: 198025861
Severity: Minor
Alarm Description
Alarm Cause
Impact
Action
1. In NMS Configuration Management interface, click Power Board Alarm Parameters to view the
lower threshold of rack voltage. If the configuration is unreasonable, please modify it. For 48V power
supply, the recommended value of lower threshold is 40V; for 60V power supply, the recommended
value is 50.
2. Find out which line voltage is below lower threshold by using the voltage index given in alarm
details. Regulator through the power supply equipment to increase the input voltage of this line.
3-314
Severity: Minor
Alarm Description
Humidity is high
Alarm Cause
1. The configured threshold is unreasonable.
2. Actual humidity in equipment room is too high.
Impact
1. If an unreasonable threshold is configured, services will not be affected.
2. If the alarm is caused by high room humidity, board may work abnormally and board services may
be interrupted.
Action
1. In NMS Configuration Management interface, click Power Board Alarm Parameters to view
the upper threshold of room humidity. If the configuration is unreasonable, please modify it. The
recommended value of upper threshold is 90.
2. Check the hygrometer in equipment room to see if the actual humidity is too high. If yes, take
necessary dehumidifying measures.
Severity: Minor
Alarm Description
Humidity is low
3-315
Alarm Cause
Impact
Action
1. In NMS Configuration Management interface, click Power Board Alarm Parameters to view
the lower threshold of room humidity. If the configuration is unreasonable, please modify it. The
recommended value of upper threshold is 90.
2. Check the hygrometer in equipment room to see if the actual humidity is too low. If yes, take
necessary humidifying measures.
3. Setting the sensor correctly.
Code: 198025864
Severity: Minor
Alarm Description
Alarm Cause
Impact
This alarm may cause very high rack temperature. As a result, the relevant board may work
abnormally and board services may be interrupted.
3-316
Action
1. Check whether the FAN subrack is tightly inserted into the rack. If no, unplug and plug it.
2. Replace the fan subrack.
3. Setting the sensor correctly.
Code: 198025865
Severity: Minor
Alarm Description
Alarm Cause
Impact
Action
Code: 198025866
3-317
Severity: Minor
Alarm Description
Smoke detected
Alarm Cause
Impact
Services won't be affected, but there is a potential safety problem. Need to be handled immediately.
Action
Code: 198025867
Severity: Minor
Alarm Description
Infrared alarm
Alarm Cause
3-318
Impact
Action
1. Does an animal or a person approach near the infrared sensor? If yes, remove the heat source. If
no, please check the configuration of infra-red sensor. If the configuration is correct, sensor sensitivity
may be reduced to some extent.
2. The infra-red sensor is faulty. Replace the sensor.
3. Setting the sensor correctly.
Code: 198025868
Severity: Minor
Alarm Description
Lightning alarm
Alarm Cause
Impact
The board may work abnormally due to lightning stroke. Accordingly, board services will be
interrupted.
Action
3-319
Code: 198025869
Severity: Minor
Alarm Description
Alarm Cause
Impact
This shelf can not be supplied with power. All boards on the shelf can not work and board services
are interrupted.
Action
Alarm Description
3-320
Alarm Cause
Impact
NO impact to traffic only loss of Time synchronisation data for time stamp of events and reporting.
Action
3-321
3-322
4-1
4-2
4-3
Code: 198020291
Severity: Major
Notification Description
Notification Cause
Impact
Action
Ensure that the actual capacity of the physical memory is more than 1GB.
Code: 198020802
Severity: Minor
Notification Description
The Source IP in ARP packet is same with local IP address (include virtual address by ARP Proxy
4-4
Notification Cause
1. This network port is configured with the same IP address (including the virtual address in the same
network segment) as another host in the local network.
2. The peer-end switch that connects with this network port has a loop.
Impact
Board operation is normal. Communication network is faulty. All services on this port are down.
Action
When an IP address conflict occur, the NMS will display the conflicted IP address. Meanwhile, the
5-tuple information of the conflicted local port, as well as the conflicted MAC address of the external
device, can be detected.
1. Click Interface Configuration on the NMS Configuration interface to check the local interface
address. Modify the local interface address or the IP address of the conflicted external device.
Refer to the corresponding equipment maintenance manual to learn how to query the IP address of
external device.
2. The switch connected with the local port must have a loop if the following two conditions are
satisfied:
1) "20802 Conflicting IP Address" and "20803 Conflicting MAC Address in Subnet" concur;
2) Even though the local port IP address is changed, the two alarms still exist.
In this case, check whether there is a cable that connects both ports of the peer-end switch. If
yes, remove the cable.
Code: 198020803
Severity: Minor
Notification Description
The Source MAC in ARP packet is same with local MAC address.
Notification Cause
1. The MAC address of this port is the same with another MAC address in the direct connect network.
2. Loop exists in the remote switch connected with this port.
4-5
Impact
Board operation is normal. The notification leads to packet lookup failure in Layer 2 forwarding table.
Then packet loss occurs and all services related to this port will be down.
Action
When an MAC address conflict occurs, the NMS will display the conflicted MAC address. Meanwhile,
the 5-tuple information of the conflicted local port, as well as the conflicted MAC address of the
external device, can be detected.
1. Modify the MAC address of the local port or the conflicted MAC address of the external device.
Find the conflicted local port according to the displayed 5-tuple information. Click Interface
Configuration on the NMS Configuration interface and select "MAC Address" to check and modify
the MAC address of the local port.
Refer to the corresponding equipment maintenance manual to learn how to query the MAC address
of the external device.
2. The switch connected with the local port must have a loop if the following two conditions are
satisfied:
1) "20802 Conflicting IP Address" and "20803 Conflicting MAC Address in Subnet" concur;
2) Even though the local port IP is changed, the two alarms still exist.
In this case, check whether there is a cable that connects both ports of the peer-end switch. If
yes, remove the cable.
Code: 198020804
Severity: Minor
Notification Description
Failed to generate static ARP from the newly added IP address,because the number of static ARPs
which generated by IP has reached the maximum.
Notification Cause
Failed to generate static ARP from the newly added IP address, because the number of static ARPs
which generated by IP has reached the maximum (each port up to 100).
4-6
Impact
The external device failed to communicate with the IP address from which no static ARP is generated.
Action
Delete some proxy addresses configured for virtual ports and re-configure IP address within the limit
of static ARPs.
Code: 198020805
Severity: Minor
Notification Description
Notification Cause
When the switch of the ARP detecting enabled, NE can send ARP request packet with the ARP's
IP periodically, if NE can not receive the ARP respond packet during the set time, NE will report
this alarm information.
Impact
Action
1. Please check the device's IP address configuration of the peer end, Please check the destination
IP address of the ARP request packet whether exist.
2. Please check physical link.
3. Please check the exchanger's VLAN configuration. The local port and the destination port must be
configured with the same VLAN ID.
4-7
Code: 198020806
Severity: Minor
Notification Description
Notification Cause
When the switch of the ARP detecting enabled, NE can send static ARP request packet with the static
ARP's IP periodically, if NE receives the ARP respond packet whose MAC or dot1q encapsulation is
not the same as static ARP's during the set time, NE will report this alarm information.
Impact
Action
Code: 198018241
Severity: Major
Notification Description
4-8
Notification Cause
Impact
Action
Check if there is severe packet loss in physical link (It can be checked by ping command), and
handle physical link faults.
Code: 198018242
Severity: Minor
Notification Description
Notification Cause
Impact
Action
Check MD5 encrypted option of the two ends of application layer. If an end does not set with MD5
encrypted option, then set MD5 encrypted option for this end. The application layer protocol includes
BGP and LDP.
4-9
Severity: Minor
Notification Description
TCP packet have MD5 option, but wrong MD5 message abstract
Notification Cause
When application layer is receiving messages, MD5 cryptographic keys set on both ends are
inconsistent.
Impact
Application layer communication failure
Action
Set the same MD5 cryptographic keys for both ends of application layer. The application layer
protocol includes BGP and LDP.
Severity: Minor
Notification Description
Set Sctp primary path failed
Notification Cause
The remote IP of the SCTP primary path configured at application layer is not included in the local
address list of SCTP at opposite end
4-10
Impact
This notification informs user of the update failure of SCTP primary path. The primary path currently
in use is not affected. No impact on service.
Action
Check notification details on the NMS Alarm Management interface to find the SCTP ID and the
primary remote IP address.
To use the primary remote IP address as the primary SCTP path, perform the following steps:
1. Add the IP address as an interface address at the peer-end equipment.
2. Add the "primary remote IP address" to the "local SCTP IP address" list.
Code: 198030016
Severity: Major
Notification Description
Notification Cause
Impact
Action
Code: 198000576
4-11
Severity: Minor
Notification Description
Loss of frame on trunk
Notification Cause
Since frequency difference might exist between trunk line clock and local receive clock, the trunk
receive clock is not synchronous with the transmit clock.
Impact
Momentary fault occurs to trunk data service or signalling channel. If fault occurs repeatedly, CS/PS
service might become unstable. Otherwise, service is not affected.
Action
Check the clock synchronization status at both sides. If the status is unsynchronized, check if
LOL-related (loss of lock) alarm occurs in clock board. If yes, refer to the corresponding alarm
handling suggestion.
Related alarms:
198026127 Clock reference source lost (Level 3 alarm)
198026128 Clock reference source lost (Level 2 alarm)
198026129 Clock reference source lost (Level 1 alarm)
Severity: Major
Notification Description
MCC is faulty
Notification Cause
MCC Hardware is faulty.
4-12
Impact
Action
1. Unplug the board for 5 seconds, and plug it again after a full discharge.
2. Replace the board.
Code: 198001600
Severity: Major
Notification Description
Notification Cause
A CPU on a board at the shelf abnormally resets. The possible causes are:
1. User request CPU reset.
2. Board has reset itself due to fault.
Impact
The relevant services or communication links will be interrupted or disconnected. This alarm will be
recovered after the board is powered on normally.
Action
1. Check the NMS operation log to see whether there is a manual reset record. If yes, no handling is
necessary.
2. Replace the board.
4-13
Code: 198008005
Severity: Minor
Notification Description
Notification Cause
The transferred data records exceed the maximum capacity of the table, and the capacity of the
receiver memory file buffer is insufficient.
Impact
If the board is powering on, the excessive data records (beyond table capacity) are discarded.
Action
Code: 198017216
Name: Error in MCS Multi-Core processor receiving configuration data from DBS
Severity: Major
Notification Description
1. The configuration data from OAM to RNC is abnormal (the configuration data from DBS are
abnormal).
2. Failure in adding a vital data table.
4-14
Notification Cause
Impact
It may cause packet forwarding problem since some vital data table is absent.
Action
Check the data configuration, if there is a configuring error, correct it and reboot the board.
Code: 198023106
Severity: Minor
Notification Description
Notification Cause
Impact
The board fails to power on possibly, and the service or communication link related to this board is
down.
Action
4-15
Code: 198023107
Severity: Minor
Notification Description
Notification Cause
Impact
The board fails to be powered on. As a result, UE can not be accessed and existing services are
interrupted.
Action
Code: 198023617
Severity: Major
Notification Description
The file which is used for restoring protocol configuration data is unusable.
Notification Cause
During the process of system power on, the DAT file obtained from VMM is unusable or the TXT
file which saves configuration data is unusable.
4-16
Impact
Action
On NMS fault management interface, view the alarm details, which give the Additional Reason.
1. If it's the DAT file error, then we need to reload the file from VMM and switch to the new file.
2. If it's the TXT file error, then take the following step:
1)Get the TXT file from ""/DOC0/DATA1"" directory at RPU with File Manager method.
2)Open the TXT file and delete line ""[CRC_DATFILE]="" and ""[CRC_TXTFILE]="".
3)Transmit the modified TXT file.
4)Reboot RPU.
Code: 198003138
Severity: Major
Notification Description
Notification Cause
Impact
1. If the fault flash is on OMP board, the OMP board will fail to be powered on. If both master/slave
OMP boards have the flash fault, the entire system can not start up.
2. If the fault flash is on other board, the board can be powered on normally and there is no impact
on services.
4-17
Action
Code: 198003394
Severity: Minor
Notification Description
Notification Cause
Impact
No impact
Action
No handling is necessary.
Code: 198003395
Severity: Minor
Notification Description
4-18
Notification Cause
Daylight saving time is de-activated and the system is back to normal country clock.
Impact
No impact
Action
No handling is necessary.
Code: 198025664
Severity: Major
Notification Description
Notification Cause
1. Abnormal jitter occurs to the line clock of the shelf where the board is located.
2. The board is faulty.
Impact
TMD channel is interrupted momentarily, which may have a slight impact on services.
4-19
Action
1.Check alarms and notifications to see if the alarm(s)/notification(s) related to input clock
exist(s).Related alarm(s) and notification(s) are listed below.
198026116 CLKG PP2S Output Clock Lost
198026127 Clock reference source lost (Level 3 alarm)
198026128 Clock reference source lost (Level 2 alarm)
198026129 Clock reference source lost (Level 1 alarm)
198026133 Clock Output Loss
2.Replace the faulty board.
Code: 198005441
Severity: Minor
Notification Description
Notification Cause
Impact
4-20
Action
Alarm details are displayed in NMS Alarm Management interface, where port status is given.
1. If the port status is "Master port invalid status" or "Master port abnormal", please solve the problem
according to the following handling suggestions.
i. Reconnect the cable between UIM/GUIM/GUIM2 and GLI.
ii. Replace the optical module or cable used for the connection between UIM/GUIM/GUIM2 and GLI.
iii. Replace the UIM/GUIM/GUIM2 board.
iv. Replace the GLI board.
2. If the port status is others, no handling is necessary.
Code: 198005448
Name: 485 seriel bus link between CLKG/PWRD and OMP is broken
Severity: Minor
Notification Description
Notification Cause
Impact
The configured clock reference/environment threshold fails to take into effect. There is no impact
on services.
Action
4-21
Code: 198026176
Severity: Minor
Notification Description
Notification Cause
Impact
System could not get the needed clock, which will cause processing abnormity related to the clock.
Action
No need to handle.
Code: 198026177
Severity: Minor
Notification Description
Notification Cause
4-22
Impact
Action
Code: 198026178
Severity: Minor
Notification Description
Notification Cause
Impact
Action
No need to handle.
Code: 198026179
Severity: Minor
4-23
Notification Description
Notification Cause
Impact
System could not get the needed clock, which will cause processing abnormity related to the clock.
Action
No need to handle.
Code: 198005705
Severity: Major
Notification Description
Notification Cause
Impact
Action
4-24
Code: 198005710
Severity: Minor
Notification Description
Notification Cause
After manual base switchover, man-machine command, or pressing panel button, clock board
performs base locking operation (at most for 2 minutes). This notification is to inform the user of
the operation result of manual base selection.
Impact
No impact on service.
Action
No handling is necessary.
Code: 198005711
Severity: Minor
Notification Description
If the last benchmark selection operation is being done and the corresponding result is not given, this
current benchmark selection operation will be cancelled and the corresponding notice will be reported
4-25
Notification Cause
If previous operation about clock reference selection doesn't finish and relevant result is not given
yet, the system will screen any new attempt to manually select clock reference. And in this case,
this notification is declared.
Impact
No impact on service.
Action
No handling is necessary.
Code: 198005712
Name: The manual select base will be run, please wait for the result
Severity: Minor
Notification Description
When the reference is selected with panel keys, the background sends this message to notify the
user that the command is being executed and ask the user to wait for the execution result
Notification Cause
The notification is declared after selecting base via panel button, to remind user that the base
selection is in process and to request user to wait for the operation result.
Impact
No impact on service.
Action
No handling is necessary.
4-26
Code: 198005713
Severity: Major
Notification Description
Notification Cause
Impact
The alarm board can not be used. ATM cell fails to be forwarded, and all board services are
interrupted.
Action
Code: 198005715
Severity: Minor
Notification Description
Notification Cause
PP2S (Pulse Per 2 Seconds) source is switched at both system clock and GPS receiver sides.
4-27
Impact
No impact on service.
Action
GPS side PP2S has a higher priority. If PP2S is switched over from GPS-side to system-side, check
the GPS receiver and antenna feed status.
Code: 198005718
Severity: Minor
Notification Description
The network port connected with a master clock port in this board is a master clock port too
Notification Cause
Two ports which are configured as synchronous Ethernet master clock port are directly connected.
Impact
If network connecting is normal, then there is no impact; if it is network connecting mistake, then the
port can not synchronize to the connected master clock port.
Action
If network connecting is normal, there is no need to handle; if it is network connecting mistake, there
is need to reconfigure the clock port or reconnect the port.
Code: 198005700
4-28
Severity: Major
Notification Description
DSP error
Notification Cause
1. DSP chip on the board that has alarm is faulty.
2. Board is faulty.
Impact
DSP is unavailable during reset, but will be restored to normal state after reset. During reset, cells on
the DSP are out of service, services on the DSP are interrupted, and call loss increases.
Action
DSP resets automatically and abnormally.
1. If power-on is normal(the board has no alarm code 5399) after DSP reset, the board can be
restored to normal state.
2. If DSP resets repeatedly, replace the board or sub-card.
Severity: Major
Notification Description
Version Load Error
Notification Cause
The equipment is abnormal in the process of version loading, which falls into three cases.
1. The equipment fails to fetch the needed version.
2. Version loading to chip fails.
3. Chip hardware is faulty.
4-29
Impact
1. Microcode version loading fails, leading to repeated board reset and interruption of board services.
2. Firmware/single-chip computer version loading fails, leading to abnormal board operation and
interruption of board services.
3. DSP version loading fails. Cells on the DSP will be out of service. Services on the DSP are
interrupted, and the number of call loss increases.
Action
On NMS fault management interface, view notification Details where "Loading corresponding alarm
information" is given. Locate the corresponding handling suggestion based on the given information.
1. Any of the following items displayed by "Loading corresponding alarm information" indicates that
the chip fails to obtain the needed version. On NMS software management interface, check the
configured version for the chip and version status. Ensure that the needed version is configured for
the chip and the version is actived. If the version is not actived, please active the version by the OMC
i. DSP6416 No.d : No Version Information
ii.DSP5402 No.d : No Version Information
iii. MC fail to get version information
iv. OCT6100 fail to get version information
v. M82620 : Index = d fail to get version information
2. If information other than the items listed above appears, refer to the following handling suggestion.
i. Reset board.
ii. Replace DSP sub-card.
iii. Replace board.
Code: 198019777
Severity: Minor
Notification Description
4-30
Notification Cause
Impact
During APS changeover process, the link is interrupted for 10 ~ 50 ms. Few packets may be lost, but
services won't be affected.
Action
View operation & maintenance log to see whether there is a record, indicating an operator manually
initiates APS changeover request/clearance. If yes, no handling is necessary. If no, check whether
there is one of the following alarms. If yes, please solve the problem according to corresponding
handling suggestions.
Related alarms:
198001792 SDH/SONET fault
198005396 Exceptional Internal Media Plane Communication
198005378 Board HW Error
198005635 The board is not plugged firmly.
Code: 198005188
Severity: Minor
Notification Description
4-31
Notification Cause
Impact
Action
Check if the following alarm occurs in local/opposite board. If yes, refer to the corresponding alarm
handling suggestion.
Related alarms:
198001286 Loss of input clock
198005639 High Error Rate of Optical Interface
198005646 Phase-locked Loop Unlocked
Code: 198005189
Severity: Minor
Notification Description
Notification Cause
It is hardware system fault. The CS domain of the UIM switches over due to artificial operation.
Impact
4-32
Action
1. Analyze the switchover reason according to the additional information about the alarm .If it is not
because of the system fault but due to control of MML command at the background or caused
by non-active/standby changeover, or the standby board does not exist physically, nothing would
be done for this alarm.
2. If it is because of the system fault, eliminate those alarms firstly.
Code: 198005192
Severity: Minor
Notification Description
Notification Cause
1. The work mode that the board does not support is configured on the background.
2. Such reasons as FPGA not loading cause that there are errors in setting the working mode for
the board.
Impact
Action
1. Check the configuration of board backup mode. If the configured backup mode is not supported by
the board, modify configuration or replace the board with one that supports such configuration.
2. Unplug and plug board. Reload FPGA version.
4-33
Code: 198005193
Severity: Minor
Notification Description
Notification Cause
Impact
Action
Alarm details are displayed in NMS Alarm Management interface, where powered-on status (Board
poweron successful/failed/timeout) is given. You can easily find handling suggestions according to
the powered-on status.
The handling suggestions for each status are described as below.
1. Powered on successful
No handling is necessary.
2. Powered-on timeout
Ensure that the board loads a proper version. The boards on a network element must use the
same version.
3. Powered-on failed
Ensure that the board loads a proper version. The boards on a network element must use the
same version.
4-34
Code: 198005956
Severity: Minor
Notification Description
Periphery board request version info error or download / load version file error
Notification Cause
Impact
The board fails to obtain version, leading to abnormal board operation and access failure of board
services.
Action
1. On NMS configuration management interface (rack), view rack layout. Make sure that the board
configured is the same with the board plugged in the slot.
2. According to board type information in detailed notification, add and reload the right version.
Code: 198005958
Severity: Minor
4-35
Notification Description
Notification Cause
Impact
1. IDE version file synchronization occurs between master and slave OMP (ROMB board). Service
will not be affected by synchronization result.
2. In the case of synchronization failure, partial loss of version file will occur to slave OMP
Action
On NMS fault management interface, view notification Details where "Synchronization information" is
given.
1. If synchronization information is "Failed to obtain file record during synchronization" or
"Synchronization failed", find the name of the version file in notification Details. According to the given
file name, locate on NMS software management interface the corresponding version configuration in
the version file database. Reload the version file to RNC NE. Delete the version file if it is not in use.
2. If synchronization information is others, no handling is necessary.
Code: 198005961
Severity: Minor
Notification Description
Notification Cause
The version file in software version configuration does not exist in RNC NE.
4-36
Impact
1. If the non-existent version file is not in use, service will not be affected.
2. If the non-existent version file is the activated version, the corresponding board will fail to fetch
version during powering-on, leading to service access failure.
Action
On NMS fault management interface, view notification Details where "Version file name" is given.
According to the given file name, locate on NMS software management interface the corresponding
version configuration in the version file database. Reload the version file to RNC NE.
Code: 198005962
Severity: Minor
Notification Description
Notification Cause
Impact
Patch version activation fails. New functions of the patch version are unavailable. No impact on
service.
Action
1. If the patch version is not needed, delete the corresponding version configuration on NMS software
management interface.
2. If the patch version is needed, locate on NMS software management interface the version
configuration of patch version file and related patch version file in the version file database. Reload
the version files to RNC NE.
4-37
Code: 198011840
Severity: Major
Notification Description
Notification Cause
Impact
If M3UA user office status changes from accessible to inaccessible, reception and sending of
messages from/to the office fail. Access of new services under the office fails, and abnormal release
of the ongoing service occurs.
If M3UA user office status changes from inaccessible to accessible, the system will return to normal
state.
Action
1. Check whether link interruption alarm occurs to the link/association. If yes, refer to the
corresponding alarm handling suggestion.
Related alarms:
198066011 MTP3 link unavailable
198066019 Association link broken
2. On NMS configuration management interface, check if the M3UA user is configured in the relevant
office. If no, add the configuration.
3. Locate the cause for office status change at opposite end.
Code: 198013888
4-38
Severity: Minor
Notification Description
Notification Cause
Impact
If both "ASP status changed" notification and "8400384 M3UA office inaccessible" alarm occur at the
same time, new services can not be accessed to the office and existing services will be interrupted
abnormally.
If merely this notification is reported, services will not be affected.
Action
1. Check whether association interruption alarm occurs. If yes, refer to the corresponding alarm
handling suggestion.
Related alarm: 198066019 Association link broken
2. Activate the ASP in dynamic data management.
3. Check whether ASP operation is performed at the opposite end.
Code: 198013889
Severity: Minor
Notification Description
4-39
Notification Cause
Impact
If both "AS status changed" notification and "8400384 M3UA office inaccessible" alarm occur at the
same time, new services can not be accessed to the office and existing services will be interrupted
abnormally.
If merely this notification is reported, services will not be affected.
Action
1. Check whether association interruption alarm occurs. If yes, refer to the corresponding alarm
handling suggestion.
Related alarm: 198066019 Association link broken
2. Activate ASP under the AS in dynamic data management.
3. Check whether ASP operation is performed at the opposite end.
Code: 198013890
Severity: Minor
Notification Description
Notification Cause
1. AS configuration is wrong.
2. Protocol versions used at both sides are different.
Impact
4-40
Action
1. Check AS configuration to see whether the configured traffic mode at both sides are consistent. If
no, modify configuration to keep consistency.
2. APP server AS ID configuration must meet the following requirements. If ASP is configured for
local end, SGP should be configured for Opposite end. Vice versa. If IPSP client is configured for
local end, IPSP server should be configured for opposite end. Vice Versa.
3. Activate the ASP in dynamic data management.
4. On NMS configuration management interface (AS configuration), check if routing context and
routing context ID are configured. Ensure that the routing contexts configured at both ends are
the same.
5. On NMS configuration management interface, check whether the local ASP in service for AS is
configured. If no, add the configuration.
6. Check the protocol versions used at both sides. Ensure that the protocol versions are the same.
Code: 198013891
Severity: Minor
Notification Description
Notification Cause
1. Because association links are interrupted, the number of activated ASPs, associated to the serving
AS, is insufficient.
2. ASP is released in Dynamic Data Management so that the number of ASPs, associated to the
serving AS, is insufficient.
Impact
The number of ASPs associated to the serving AS is insufficient. If traffic is heavy, congestion or
packet loss may occur, leading to loss of calls and decreased PS call access rate. However, if
traffic is not heavy, services will not be affected.
4-41
Action
1. On NMS configuration management interface (AS configuration), query ASP-related associations.
Check whether interruption alarm occurs in the association(s). If yes, refer to the corresponding
alarm handling suggestion.
Related alarm: 198066019 Association link broken
2. Reactivate ASP in dynamic data management.
3. Check whether ASP operation is performed at the opposite end.
Severity: Minor
Notification Description
Allocate memory fail
Notification Cause
Memory is insufficient, that result in dynamic memory allocation failure when the processor is
powered on.
Impact
If Application Server/Application Server Process is not configured on this board, system will not
be affected. Or else process will be unstable.
Action
1. Need to enlarge memory capacity of the alarming board and then restart the board.
2. If Application Server/Application Server Process is not configured on this board, then the alarm
should be ignored.
4-42
Severity: Major
Notification Description
Notification Cause
Impact
If several association links are available to the destination office, services will not be affected. In
the case of heavy traffic, link congestion may occur, leading to loss of calls and decreased PS
call access rate.
If merely one association link is available to the destination office, the office may become inaccessible.
UE fails to receive/transmit messages from/to the relevant office. New services can not be accessed
to this office.
Action
1. On NMS configuration management interface, check association configuration at local end and
opposite end. Checking items include local IP address, local port No., remote IP address, remote port
No., and application property of SCTP association. If the association at local end is configured as
client, the association at opposite end should be configured as server. Vice Versa.
2. At local end, check whether the associations configured with different protocol types have the
same local IP address and local port No.. If yes, perform configuration modification to differentiate the
local IP address and local port No. of these associations.
3. Check protocol stack configuration at both ends to see if interface board addresses are in the same
network segment. If no, modify configuration to put two addresses in the same network segment.
4. Ping the opposite-end interface board address to see if the network cable or other intermediate link
is faulty. Replace the cable if ping fails.
Code: 198014145
4-43
Severity: Minor
Notification Description
The peer end originated link reestablishment, and the association restarted.
Notification Cause
The local end receives a link setup request but actually it doesn't detect a broken link. This causes
association restarts. Probable reasons are:
1. Relevant board at opposite end resets.
2. An association link is re-established at opposite end.
Impact
No impact.
Action
Code: 198005195
Severity: Minor
Notification Description
The PCB ID, BOM ID or physical board type is inconsistent between master board and slave board.
Notification Cause
4-44
Impact
Not support to mix plug into shelf, the board can't work normally.
Action
Depend on PCB ID, BOM ID and physical board type of the self board and the mate board according
to the additional information about the inform, inquire "Board mix plug test conclusion.xls" and check
the two boards can mix plug into shelf? If yes ignore it, if not use the same PCB ID, BOM ID and
physical boar type please.
Code: 198031040
Severity: Minor
Notification Description
Notification Cause
BRS protocol processes ACL configuration data which synchronized by DBS from ACL offline
configuration failed.
Impact
Action
1. Check the ACL configuration type and error information from alarm inform.
2. Correct the ACL offline configuration data base on alarm inform.
3. Synchronize the ACL offline configuration data.
4-45
Code: 198105001
Severity: Minor
Notification Description
The board fails to obtain the database configuration from itself or the OMP.
Notification Cause
Impact
The effect on the system varies with the alarm cause. Detailed information is as follows:
l Failing to obtain the IP segment reassemble board information.
This information is used to process the external fragmented IP packets arriving at the device.
If the information is missing, the processing of fragmented IP packets may fail, causing the
interruption of services or a decline of the service processing rate.
l Failing to obtain the OMCB server configuration.
If the configuration is missing, the OMCB function may fail to be used.
l Failing to obtain the signaling distribution table.
If the information is missing, the SCTP data may fail to be transmitted on the interface board,
and related services operating on the board are interrupted.
l Failing to obtain the IP/UDP distribution table.
If the information is missing, the processing of the IUPS service or the IP transport-based data
may fail.
l Failing to obtain the layer-2 forwarding table.
If the information is missing, the internal communication of the device is not operating properly,
causing the interruption of all services operating on the board.
l Failing to obtain the path configuration table.
For the ATM interface board, if the information is missing, the processing of the AAL2-based data
may fail, causing the interruption of the IUB, IUCS, and IUR services belonging to the office.
For the IP interface board, the traffic control on IP packets may fail, causing the interruption of
all services belonging to the office.
l Failing to obtain the path group configuration table.
For the ATM interface board, if the information is missing, the processing of the AAL2-based data
may fail, causing the interruption of IUB, IUCS, and IUR services belonging to the office. For the
IP interface board, there is no impact on services.
4-46
Action
1. Re-execute synchronize all data, and check whether the notification persists.
Yes -> Step 2.
No -> End.
2. Check whether the following parameters are set as required in accordance with "Table name" in
the notification information.
IpUdpTbl: "Slave Sunit(UpSlaveSunit)"
PathGrpTbl: "Transmission Path Group(TrPathGroup)"
PathTbl:
l UMTS: "Iub Transmission Path(UIubTrPath)", "MGW Transmission Path(UMgwTrPath)",
"Iups Transmission Path(UIupsTrPath)", "Iur Transmission Path(UIurTrPath)", and "Iurg
Transmission Path(UIurgTrPath)"
l TD: "Iub Transmission Path(TIubTrPath)", "MGW Transmission Path(TMgwTrPath)",
"Iups Transmission Path(TIupsTrPath)", "Iur Transmission Path(TIurTrPath)", and "Iurg
Transmission Path(TIurgTrPath)"
l GSM: "Abis Transmission Path(GAbisTrPath)", "A Transmission Path(GATrPath)", "Gb
Transmission Path(GGbTrPath)", "Ater Transmission Path(GAterTrPath)", and "Iurg
Transmission Path(GIurgTrPath)"
PathCirTbl:
l UMTS: "CIR of Iub Transmission Path(UIubTrPathCir)", "CIR of MGW Transmission
Path(UMgwTrPathCir)", "CIR of Iups Transmission Path(UIupsTrPathCir)", "CIR of Iur
Transmission Path(UIurTrPathCir)", and "CIR of Iurg Transmission Path(UIurgTrPathCir)"
l GSM: "CIR of Abis Transmission Path(GAbisTrPathCir)", "CIR of A Transmission
Path(GATrPathCir)", "CIR of Gb Transmission Path(GGbTrPathCir)", "CIR of Ater
Transmission Path(GAterTrPathCir)", and "CIR of Iurg Transmission Path(GIurgTrPathCir)"
l TD: "CIR of Iub Transmission Path(TIubTrPathCir)", "CIR of MGW Transmission
Path(TMgwTrPathCir)", "CIR of Iups Transmission Path(TIupsTrPathCir)", "CIR of Iur
Transmission Path(TIurTrPathCir)", and "CIR of Iurg Transmission Path(TIurgTrPathCir)"
IntfIpAddrTbl: check "Ethernet IP Interface(EthIpIntf)", "Ethernet IP Sub Interface(EthIpSubIntf)",
"Ethernet Channel IP Sub Interface(EthChIpSubIntf)", "Ethernet Channel IP
Interface(EthChIpIntf)", "IP Interface of ML-PPP Group(MlpppTpIpIntf)", "IP Interface of PPP
Link(PppIpIntf)", "Super Vlan IP Interface(EthSuperIpIntf)", "IPOA IP Configuration(IpoaTp)",
"Loopback IP Interface(LbIpIntf)", and "Virtual IP Interface(VIpIntf)".
ReassBrdTbl: Check "IP Configuration(Ip)". "IP Segment ReAssemble Default Unit(ref1Unit)" and
"IP Configuration(Ip)". "IP Segment ReAssemble Units(ref2Unit[])".
DhcpRoleTbl: check "DHCP Server(DhcpServer)" and "DHCP Relay(DhcpRelay)".
DataMuxTbl: check "IP Configuration(Ip)". "DeMux Port of RTP MUX (IuDeMuxUdpPort)" and "IP
Configuration(Ip)". "DeMux Port of UDP/RTP MUX (IubDeMuxUdpPort)".
SctpCfgTbl: check "Association(SctpAssociation)".
OmcbCfgTbl: check "Operation Maintenance Configuration(OmCon)".
InnerOmcbCliIp:
l UMTS: "Iub Link(UIubLink)". "OMCB Inner Service IPv4 Address(InnerOmcbCliIPv4)".
l TD: "Iub Link(TIubLink)". "OMCB Inner Service IPv4 Address(InnerOmcbCliIPv4)".
l GSM: "Abis Office(GAbisLink)". "OMCB Inner Service IPv4 Address(InnerOmcbCliIPv4)"
4-47
OmcbMultiPath:
l UMTS: "Omcb Path(UOmcbPath)"
l TD: "Omcb Path(TOmcbPath)"
l GSM: "Omcb Path(GOmcbPath)"
UdpUnitTbl: "UDP Port Configuration(UDPPORTNUM)"
PtpTbl: "PTP Interface Configuration(PtpPort)"
DhcpRelayTbl: "DHCP Relay(DhcpRelay)".
Yes -> Step 4.
No -> Step 3.
3. Modify the configuration as required, and check whether the notification persists.
Yes -> Step 4.
No -> End.
4. Contact the next level of maintenance support.
Code: 198105002
Severity: Minor
Notification Description
The total number of routing entries that the user-plane board detects exceeds 90 percent of the
maximum number of routing entries that the board supports.
Notification Cause
Too many route entries are configured, reaching 90 percent of the upperlimit of the routing table (the
maximum number of routing entries that the VTCD board supports is 360, and the maximum number
of routing entries that the VTCD-2 board supports is 4096).
4-48
Impact
l If the total number of routing entries does not exceed the maximum capacity of the routing table
on the user-plane processing board, services are not affected.
l If the total number of routing entries exceeds the maximum capacity of the routing table on the
user-plane processing board, some routing entries are lost.
If the lost route is the route from the RNC/BSC to Node B/BTS or to the CN, user services
may fail to be connected to the board.
If the lost route is destined to the peer RNC NE, the cross-RNC user services cannot be
connected to the board.
The SLA diagnostic test between the RNC and other NEs fails to be executed.
Action
Code: 198105003
4-49
Severity: Minor
Notification Description
Notification Cause
Impact
Action
1. Open the rack diagram, and identify the board type (interface board or non-interface board) in
accordance with the physical address in the notification information. Check whether the following
configuration is in accordance with actual requirements.
l non-interface board parameters
"DHCP Client(DhcpClient)"
l interface board parameters
Code: 198105004
4-50
Severity: Minor
Notification Description
The interface board fails to be added to the User Trace Multicast Group.
Notification Cause
The interface board fails to be added to the User Trace Multicast Group, which may be caused
by the abnormal communication with the control-plane channel of other control-plane boards or
the abnormal operation of the board.
Impact
The user tracing function of the interface board may fail to operate properly. There is no impact
on services.
Action
Code: 198105005
Severity: Minor
Notification Description
The user-plane board detects that the clock difference between the slave subunit and host exceeds
the threshold.
Notification Cause
l The clock deviation between the slave subunit and host exceeds the threshold (default: 36
seconds).
l The crystal oscillator of the slave subunit or host is not accurate.
l The board is writing the black box.
4-51
Impact
Action
Code: 198105006
Severity: Minor
Notification Description
The user-plane board detects the loss of the external clock of the slave subunit.
Notification Cause
l The clock channel between the clock board and user-plane board is not operating properly.
l The clock board is not operating properly.
l The hardware of the user-plane board is faulty.
4-52
Impact
Action
Code: 198105008
4-53
Severity: Minor
Notification Description
The base station controller that has the "Transmission CAC based on SLA-PM" function enabled
detects that bandwidth automatic adjustment is invalid.
Notification Cause
The base station controller cannot completely solve the loss of packets over the path after setting the
transmission path bandwidth to the smallest value.
Impact
The packet loss ratio of the path is larger than the reference value, which causes a decline of the
PS/CS service quality, the access failure, and service interruption.
Action
1. Find the interface location in accordance with the network planning data and "ANE ID" in the
notification information, and check whether the physical cable connected to the interface is loose.
Yes -> Step 2.
No -> Step 3.
2. Secure the physical cable.
3. Wait for half an hour, and check whether the notification persists.
Yes -> Step 4.
No -> End.
4. Record the packet loss ratio in additional information of the newly reported notification, and
contact the next level of maintenance support.
Code: 198105018
Severity: Minor
Notification Description
4-54
Notification Cause
l The log server is not operating properly, for example, the link between the log server board and
OMP is broken, the rear card corresponding to the log server board is offline, or the disk of the
log server has insufficient space.
l The OMP is not operating properly, for example, the link with the OMM is broken. If the link
between the OMM and OMP is broken for more than eight performance statistics periods, the
OMP does not write performance files.
Impact
There is no impact on services. The performance statistics data may be lost, causing the performance
statistics results to be incorrect.
Action
Code: 198105019
Severity: Minor
4-55
Notification Description
The user-plane board detects a memory soft check failure in the slave subunit.
Notification Cause
Impact
Action
Code: 198105030
Severity: Minor
Notification Description
The non-OMP board detects that not all of the performance data on the board is reported to the OMP.
4-56
Notification Cause
l Too many measurement statistics task are executed at the same time, resulting in a large
amount of performance data on the non-OMP board. The data cannot be sent to the OMP
during the specified time.
l The communication between the OMP and non-OMP board is faulty.
Impact
There is no impact on services. The performance statistics data may be lost, causing the performance
statistics results to be incorrect.
Action
Code: 198105032
Severity: Minor
Notification Description
The base station controller detects that the bandwidth that is already allocated in the transmission
path exceeds the bandwidth upperlimit.
4-57
Notification Cause
Impact
The available bandwidth to the destination address is smaller than the allocated bandwidth, the base
station controller selectively releases services over the transmission path to avoid congestions on
the transmission path.
Action
1. Query the transmission path object in the corresponding office in accordance with "ANE ID" and
"Transmission path ID" in the alarm information. Check whether the "Transport BandWidth
Adjustment Switch based on IP SLA(IpBandAdjSwitch)" parameter of the object is set to
"1:(Open)".
Yes-> It means that the "Transmission CAC based on SLA-PM" function is enabled, and the
transport quality of the transmission channel to the office is deteriorated or the intermediate
device is faulty. In this case, contact the maintenance personnel of the intermediate device to
resolve the fault. End alarm handling.
No -> Step 2.
2. It means a higher-priority service is forcedly accessed, causing the exceeding of the bandwidth
limit. In this case, no action is required, and end alarm handling.
Code: 198105033
Severity: Minor
Notification Description
The base station controller detects that the bandwidth that is already allocated in the transmission
path group exceeds the bandwidth upperlimit.
4-58
Notification Cause
Impact
The available bandwidth to the destination address is smaller than the allocated bandwidth, and
therefore the rate at which services operate over the path group decreases.
Action
1. Query the "Transmission Path Group(TrPathGroup)" object in accordance with "Path group ID" in
the alarm information. If "E1/T1 Transport BandWidth Adjustment Switch(E1T1BandAdjSwit)" is
set to "1:(Open)", check whether the following alarms arise:
198000518 Trunk link is used for CSU loopback test
198000519 Trunk error
198000520 Trunk abnormal
198001792 Loss of SDH transmission link
198001825 High BER on SDH / Sonet link
198066029 PPP link broken
Yes -> Step 2.
No -> Step 3.
2. Resolve the related alarms, and end alarm handling.
3. It means a higher-priority service is forcedly accessed, causing the exceeding of the bandwidth
limit. In this case, no action is required, and end alarm handling.
Notification Description
4-59
Notification Cause
Impact
If the HDLC is the last available one in the UID,the service on the UID will be interrupted. If the HDLC
is not the last available one in the UID, the traffic on the UID will be reduced.
Action
1.Check the settings of HDLC channel to see whether the E1/TI of this HDLC and its time slots are
accordant with the peer end.
2.Check whether the physical connection is correct.
3.Check whether the E1/T1 line is damaged.
4.Note down the statistic data of messages received and sent from the HDLC, and contact the
next level of maintenance support.
Notification Description
LSDB Overflow
Notification Cause
Impact
Action
1.Configure route aggregation to reduce the number of LSAs. Check if the alarm is eliminated.
Y->If so, finish the alarm handling.
N->Contact the next level of maintenance support.
4-60
Notification Description
Notification Cause
Impact
Action
1.To modify the relevant configuration of OSPF and make them are coordinated. Check if the alarm is
eliminated.
Y->If so, finish the alarm handling.
N->Contact the next level of maintenance support.
Notification Description
Failed to add the ospf routes to the dynamic protocol routing table for overflowing
Notification Cause
Failed to add the ospf routes to the dynamic protocol routing table for overflowing
4-61
Impact
Action
1.Check routes on RPU through the background to see whether there are any needless interface
addresses and static routes.
Y->If the unwanted IP addresses or static routes exist, delete the unwanted IP interface addresses
or static routes. If so, go to step "2".
N->If IP address is not configured on the interface, go to step "3".
2.Check whether the alarm is eliminated.
Y->If so, finish the alarm handling.
N->If not, go to step "3".
3.Reduce the quantity of its distributed route information through route aggregation on the peer router
and then check whether the local alarm is eliminated.
Y->If so, finish the alarm handling.
N->If not, go to step "4".
4.Record the detailed information.
1) Record IP address and static route configuration on the interface.
2) Record the dynamic route information. Contact the next level of maintenance support.
Notification Description
Notification Cause
Impact
4-62
Action
1.Configure an IPv4 address for an interface (It is recommended to configured an IPv4 address for a
Loopback interface) , make it a Router ID, and then re-create an OSPF process. Check whether
the alarm disappears.
Y->End.
N->Contact the next level of maintenance support.
Notification Description
Notification Cause
Impact
Action
1.To modify the relevant configuration of OSPF and make them are coordinated. Check if the alarm is
eliminated.
Y->If so, finish the alarm handling.
N->Contact the next level of maintenance support.
4-63
Notification Description
Notification Cause
Impact
Action
1.Check routes on RPU to see if there are any needless interface addresses and static routes.
Y->If there are, delete the unwanted IP interface addresses or static routes, go to "2".
N->If IP address is not configured on the interface, go to "3".
2.Check if the alarm is eliminated.
Y->If so, finish the alarm handling.
N->If not, go to "3".
3.Reduce the quantity of its distributed route information through route aggregation on the peer router.
And check if the alarm is eliminated on the local.
Y->If so, finish the alarm handling.
N->If not, go to "4".
4.Record the detailed information.
1)Record IP address and static route information on the interface.
2)Record the dynamic route information. Contact the next level of maintenance support.
Notification Description
Notification Cause
When adding a neighbor, the address of the neighbor mismatches with that of the interface.
4-64
Impact
The dynamic route expected to be obtained from this neighbor fails to be established.
Action
1.Check the address of interface to see whether it is in the same network segment with that of rip
neighbor.
Y->If so, go to "3".
N->If not, go to "2".
2.Check if the configured neighbor address is the network number or broadcast address.
Y->If so, go to "3".
N->go to "4".
3.Reconfigure the neighbor address to finish the alarm handling.
4.Contact the next level of maintenance support.
Notification Description
Notification Cause
Impact
Action
1.Check if the authentication types on the two ends are consistent. If not, go to "2". Y-> If so, go to "3".
2.Modify verification types on two ends as consistent ones. And Finish the alarm handling.
3.If the verification types are consistent, check if the verification keys are consistent, if so, go to "4". If
not, modify them as consistent ones. Finish the alarm handling.
4.Contact the next level of maintenance support.
4-65
Notification Description
Refused to receive because of version incompatibility between interface and route update message
Notification Cause
The version number of the interface on remote device is inconsistent with that on local device.
Impact
Action
1.Check if the version number of the interface on remote device is inconsistent with that on local
device. Y-> Go to "3". N-> Go to "2".
2.Reconfigure it and finish the alarm handling.
3.Contact the next level of maintenance support.
Notification Description
4-66
Notification Cause
In ISIS instance configuration under protocol stack configuration mode, System-id has wrong
configuration.
Impact
ISIS neighbor status fails to be established between the neighboring routers whose system IDs
conflict.
Action
1.Check system id configuration in ISIS instance on the router by show running config command
for conflict.
Y->Modify system id configuration in the instance, go to "2".
N->Contact the next level of maintenance support.
2.Check if the alarm is eliminated.
Y->Finish the alarm handling.
N->Please contact the next level of maintenance support.
Notification Description
Notification Cause
Message authentication modes or keys configured on the routers of the two ends are inconsistent.
Impact
The message that fails to be authenticated is omitted. The local router can not synchronize the
LSDB with the corresponding router.
4-67
Action
1.Find out the peer-end router according to system id in the alarm message.
2.Execute the show running config command locally and remotely. Check the routers on the two ends
in the displayed device running configuration to see if the protocol authentication modes in ISIS
protocol stack instance configuration are consistent (MD5/TEXT).
Y->Go to "3".
N->Modify the protocol authentication modes on the routers of the two ends as the consistent ones
and perform the interconnection operations again. Finish the alarm handling.
3.Execute the show running config command locally and remotely. Check the routers on the two ends
in the displayed device running configuration to see if the protocol message authentication keys in
ISIS protocol instance configuration are consistent (MD5/TEXT).
Y->Please contact the next level of maintenance support.
N->Modify the protocol authentication modes on the routers of the two ends as the consistent ones
and perform the interconnection operations again. Finish the alarm handling.
Notification Description
Notification Cause
Impact
4-68
Action
Notification Description
Notification Cause
Impact
Action
4-69
Notification Description
Notification Cause
DNS server makes no response, so the link may be broken or the DNS server is down.
Impact
Action
1.Use command Ping to check whether the link between the network element which the DNS client
belongs to and the DNS server is available.
Y->go to "2".
N->Solve the physical link problem.
2.Check the status of DNS server to see whether it is listening at port 53.
Y->Contact the next level of maintenance support.
N->Solve equipment problem.
Notification Description
4-70
Notification Cause
Impact
The SIPI board will restart, which may affect the normal data packet processing of the board, and
causes the services on the board unstable.
Action
1. On the background, close the message exception detection of SIG_IPI forwarding service. In
this way, the board will not restart.
2. If an alarm appears when this function is enabled, check whether the signaling is configured
to pass through this board.
3. Check whether the transmission configuration and network are faulty.
4. If the problem still exists, replace the board.
Notification Description
Notification Cause
The board does not support the trunk configuration in the database.
Impact
4-71
Action
1.Check if this board configuration is correct.
Y->Go to "2"
N->Modify the board configuration and then restart the board to see if the alarm is still given: Y->
end,N->go to "2".
2.Replace the board with one that matches the configuration, and check if this alarm is still given.
Y->Please contact the next level of maintenance support.
Y->End.
Notification Description
The active/standby modules of PSN clock have changed over successfully
Notification Cause
It is triggered from the background.
Impact
None
Action
No need to handle.
4-72
Notification Description
Notification Cause
The board does not provide external 16M or 8K clock for MCBSP interface of DSP, so DSP can only
use its clock which is not very steady, resulting in unsteadiness of DSP ping operation.
Impact
None
Action
Notification Description
Notification Cause
1. The CS optical interface changeover is initiated on the background through MML command
operation.
2. The CS optical interface has faults and automatically switches over.
(GE interfaces are located on the upper half of the GUIM/GUIM2 board while the CS domain optical
interfaces are located on the lower half of it.
Impact
4-73
Action
1. If it is because of artificial operations, this alarm occurrence belongs to normal situation and
there is no need to handle it.
2. Confirm if the indication light of the CS optical interface on the board which gives the alarm is off.If
the light is off, check if the fiber or light module has problems.
3. Check if the following alarm occurs in local/opposite board. If yes, refer to the corresponding
alarm handling suggestion.
1286 Loss of clock when input to board
5639 High error rate of optical interface
5646 Phase-lock loop unlock
Notification Description
Notification Cause
The slave board have some master processes when update the EPLD.
Impact
Action
Switch some active functions (such as optical interfaces) to standby ones on the standby board
through MML command operation.Switch again after the operation.
4-74
Notification Description
Notification Cause
Impact
Action
1. According to the object reporting this notification, query the object "GSM Cell
Configuration(GGsmCell)", and check whether the parameter "BCCH switch
allowed(CanBcchExch)" is "Yes".
Query the global object "GSM Logical Configuration(GBssFunction)", and check whether the
parameter "BCCH switch allowed(CanBcchExch)" is "Yes".
Yes -> Step 3.
No -> Step 2.
2. Modify these two parameters to "Yes". Wait for eight minutes, and check whether the notification
is still reported.
Yes -> Step 3.
No -> End.
3. Execute the QRY TRX command based on "Site ID" and "Bts ID" in the alarm details to query
the state of all the carrier frequencies in the cell. Execute the UNB FUTRX or UNB CUTRX
command to unblock the carrier frequencies in "manual block" state based on "Trx ID". Wait for
eight minutes, and check whether the notification is still reported.
Yes -> Step 4.
No -> End.
4. Contact BS maintenance personnel to check whether carrier frequency-related faults occurred.
Yes -> Step 5.
No -> Step 6.
5. Ask BS maintenance personnel to remove the faults. Check whether the notification persists.
Yes -> Step 6.
No -> End.
6. Contact the next level of maintenance support.
4-75
Notification Description
This notification is reported if the BSC detects the ring network status has changed. There are
three ring network statuses:
l Switchover status
l Normal connection status
l Disconnection status
Notification Cause
Impact
Action
No action is required.
Notification Description
This notification is reported if the BSC detects the intelligent power-on/power-off state of the carrier
has been changed.
4-76
Notification Cause
Impact
None.
Action
No action is required.
Notification Description
This notification is reported if the BSC detects there is no GPRS traffic in a cell for one hour.
Notification Cause
Impact
None.
Action
No action is required.
4-77
Notification Description
This notification is reported if the BSC detects that the Abis interface link changes from the satellite
link to the ground link or from the ground link to the satellite link.
Notification Cause
Impact
None.
Action
No action is required.
Notification Description
This notification is reported if a board detects that an NSVC link is deleted manually.
Notification Cause
Impact
None.
Action
1. Check whether the NSVC link is the one that should be deleted.
Yes -> End.
No -> Step 2.
2. Contact the next level of maintenance support.
4-78
Notification Description
Notification Cause
Impact
Action
1. Check whether the configuration of the following parameters of the object "IP Nse(GIpGbNse)" is
consistent with that of the SGSN.
- "Nse ID(GIpGbNseSeq)"
- "SGSN IP Address(SGSNIPAddress)"
- "SGSN UDP Port(SGSNUDPPort)"
Yes -> Step 3.
No -> Step 2.
2. Modify the parameter configuration for consistency with that of the SGSN, and check whether
the notification is cleared.
Yes -> End.
No -> Step 3.
3. Contact the next level of maintenance support.
4-79
Notification Description
Notification Cause
Impact
Action
Notification Description
Notification Cause
Impact
None.
4-80
Action
1. Based on "NSVCI" together with "SGSN ID" and "NSEI" in the alarm details, check whether the
NSVC link is the one that should be deleted.
Yes -> End.
No -> Step 2.
2. Contact the next level of maintenance support.
Notification Description
This notification is reported if the BSC fails to obtain the MSC SPC.
Notification Cause
The BSC is not configured with the MSC office type.
Impact
All the services are interrupted.
Action
1. Configure the object "Adjacent Office Information(RemoteSp)" with "Type of adjacent
office(OfficeType)" of 512(MSCSERVER) or 576(MGW+MSCSERVER). whether the notification
persists.
Yes -> Step 2.
No -> End.
2. Contact the next level of maintenance support.
4-81
Notification Description
This notification is reported if the BSC detects a carrier failure in a baseband frequency-hopping
group and automatically performs active/standby switchover.
Notification Cause
Impact
None.
Action
1. Execute the QRY TRX command based on "Site ID", "Bts ID", and "Trx ID" in the alarm details,
and check whether the status of this carrier is "manual block".
Yes -> Step 2.
No -> Step 3.
2. Execute the UNB FUTRX or UNB CUTRX command based on "Site ID", "Bts ID", and "Trx ID" in
the alarm details to unblock the blocked carrier Check whether the following notifications arise:
198087504 Baseband frequency hopping exchange for trx restore
Yes -> End.
No -> Step 5.
3. Contact BS maintenance personnel to check whether carrier related faults occurred.
Yes -> Step 4.
No -> Step 5.
4. Ask BS maintenance personnel to remove the faults. The alarm handling is completed.
5. Contact the next level of maintenance support.
4-82
Notification Description
This notification is reported if the BSC detects a carrier recovery in a baseband frequency-hopping
group and automatically performs active/standby switchover.
Notification Cause
Impact
None.
Action
No action is required.
Notification Description
This notification is generated if the network management system initiates cell/carrier/timeslot "Block
after service released" and the BSC performs one of the following operations.
- The object is blocked after the current services are released.
- The system initiates BCCH switchover when the BSC is waiting for resources to be released. The
object is blocked mandatorily.
- The object is blocked mandatorily when the longest timer expires and the resources are not
released yet.
Notification Cause
Impact
4-83
Action
No action is required.
Notification Description
This notification is generated if the BSC detects that PCU resources are insufficient when the cell
is selecting PCU resource.
Notification Cause
l PCU resources are insufficient.
l PCU resources are faulty.
Impact
Some cells cannot provide data service.
Action
1. On the rack diagram of [Alarm management], check whether an alarm exists on the UPPB board.
Yes -> Step 2.
No -> Step 3.
2. Handle the alarm. The alarm handling is completed.
3. Contact the next level of maintenance support.
4-84
Notification Description
This notification is generated if the BSC detects that switchover occurs on the BIPB board or the
LAPD board.
Notification Cause
l The system performs switchover automatically due to a sub-unit fault.
l The system performs switchover back automatically after the faulty sub-unit resumes normal.
l Switchover is initiated manually.
Impact
None.
Action
1. Execute the QRY SUNITSTATU command to query the state of the corresponding sub-unit
and check whether the state is "fault" in accordance with "Sub system No", "Source Unit No",
and "Source sub unit No" in the alarm details.
Yes -> Step 2.
No -> Step 3.
2. Execute the SET DSPRESE command to reset this sub-unit upon the relevant RACK, SHELF,
SLOT configuration information in accordance with "Sub system No", "Source Unit No", and
"Source sub unit No" in the alarm details. Then, execute the QRY SUNITSTATU command to
query the state of the corresponding sub-unit and check whether the state is "fault".
Yes -> Step 3.
No -> End.
3. Contact the next level of maintenance support.
Notification Description
This notification is generated if the BSC detects that the master power of the base station is recovered.
Notification Cause
The master power of the base station is recovered.
4-85
Impact
None.
Action
No action is required.
Notification Description
If the BSC receives the "BTS master power interruption" message reported by the base station and
it waits for a moment (by configuring "Site(GBtsSiteManager)"."the delay time of master power
Off(MasterPwrOffTime)", and confirms that some carriers are powered off after the master power is
off, the BSC generates this notification.
Notification Cause
Impact
None.
Action
No action is required.
4-86
Notification Description
If the BSC detects that the master power of the base station is off and it waits for a moment (by
configuring "Site(GBtsSiteManager)"."the delay time of master power Off(MasterPwrOffTime)", and
confirms that some carriers are powered off after the master power is off and then waits for another
moment (by configuring ""Site(GBtsSiteManager)"."the delay time of Transceivers Off(TrxOffTime)"
before terminating all carriers except BCCH carrier, the BSC generates this notification.
Notification Cause
Impact
None.
Action
No action is required.
Notification Description
This notification is generated if the BSC detects that the Abis link of the super station is exchanged
(among the subaerial link, the satellite link or the standby link).
Notification Cause
Impact
None.
4-87
Action
No action is required.
Notification Description
This notification is generated if the BSC detects the power-on/power-off state of the cell's BCCH
carrier has been changed.
Notification Cause
The BSC has changed the power-on/power-off state of the cell's BCCH carrier.
Impact
None.
Action
No action is required.
Notification Description
This notification is generated if the BSC detects that TRAU frame alignment loss occurs on a voice
channel for a long time.
4-88
Notification Cause
Impact
None.
Action
No action is required.
Notification Description
Notification Cause
Impact
None.
Action
No action is required.
4-89
Notification Description
This notification is generated if the BSC detects that packet loss occurs on a voice channel for a
long time.
Notification Cause
Impact
None.
Action
No action is required.
Notification Description
This notification is reported if the BSC automatically releases a detected illegal dynamic association.
Notification Cause
l More than two dynamic associations are established between the BSC and a base station.
l A conflict of local port number occurs between the new dynamic association and an existing
association (master or slave) due to incorrect association configuration at the base station side.
Impact
The association establishment on the Abis interface of the base station may be influenced.
4-90
Action
1. Locate the base station and its site ID in accordance with "peer IP address" and "peer port
ID" in the alarm details, and check whether more than two associations are configured at the
base station side.
Yes -> Step 2.
No -> Step 3.
2. Delete the extra associations. Check whether the notification persists.
Yes -> Step 3.
No -> End.
3. View the association configuration at the base station side, and check whether the local port
number of the association is configured to the site ID of the base station.
Yes -> Step 5.
No -> Step 4.
4. Modify the configuration at the base station side, and configure the local port number to that of
the base station. Check whether the notification persists.
Yes -> Step 5.
No -> End.
5. Contact the next level of maintenance support.
Notification Description
This alarm is reported if a board detects that the throughput of a Gb interface exceeds the permissible
value.
Notification Cause
The throughput of the Gb interface exceeds the configured permissible value continuously for several
times due to high PS traffic.
Impact
Some users fail to gain access to the system due to the automatically initiated flow control.
4-91
Action
The BSC will implement flow control automatically. Observing notifications is required without the
need of further operation. The capacity can be expanded if an increase of the upper limit of Gb
interface throughput is required.
Notification Description
None
Notification Cause
Cell No Traffic
Impact
None.
Action
None
Notification Description
None
4-92
Notification Cause
Impact
None.
Action
None
Notification Description
None
Notification Cause
Impact
None.
Action
None
4-93
Notification Description
None
Notification Cause
Impact
None.
Action
None
Notification Description
None
Notification Cause
Impact
None.
Action
1) Modify to static channel, reserve not more than 4 channels for PS.
2) If 16 channels of 2 TRX all for PS, modify to static coding mode, and coding mode should Less
than MCS6. If EDGE not work, this restrict is not exist.
4-94
Notification Description
None
Notification Cause
Impact
None.
Action
1) Modify to static channel, reserve not more than 4 channels for PS.
2)If 16 channels of 2 TRX all for PS, modify to static coding mode, and coding mode should Less than
MCS6. If EDGE not work, this restrict is not exist.
Notification Description
None
Notification Cause
4-95
Impact
Action
Notification Description
None
Notification Cause
Impact
None.
Action
4-96
Notification Description
None
Notification Cause
Impact
Action
Notification Description
None
Notification Cause
Site IP Conflict
Impact
Action
4-97
Notification Description
None
Notification Cause
Impact
User-defined.
Action
None
4-98
A.1 A2051
Run the START DTM command to perform a diagnosis test to the board and check
the status of all the RUB resource boards.
Command example
START DTM:TESTTYPE=DIAG_BOARD_TEST, OBJTYPE="Board", MOC="PhysCpu",
MOI="SubNetwork=35, MEID=35, Equipment=1,Rack=1, Shelf=2, Board=7, PhysCpu
=1", ATTRIBUTES="RackNo=1, ShelfNo=2, SlotNo=7, CpuNo=1", TESTSEQ="1";
Parameter description
Run the above board diagnosis command on each configured RUB board.
A-1
A-2
CPU
- Central Processing Unit
CS
- Circuit Switched
DHCP
- Dynamic Host Configuration Protocol
GSM
- Global System for Mobile Communications
LAPD
- Link Access Procedure for D-channel
MO
- Managed Object
MOC
- Managed Object Class
NE
- Network Element
NSE
- Network Service Entity
NSVC
- Network Service Virtual Connection
OMCB
- Operation & Maintenance Center for Node B
OMM
- Operation & Maintenance Module
OMP
- Operation & Maintenance Processor
PCU
- Packet Control Unit
PPP
- Point-to-Point Protocol
PS
- Packet Switched
RNC
- Radio Network Controller
RUB
- RNC User Plane Board
SCTP
- Stream Control Transmission Protocol
SGSN
- Serving GPRS Support Node
SLA
- Service Level Agreement
SPC
- Signaling Point Code
TD
- Time Division
THUB
- Trunk HUB
TRAU
- Transcoder Rate Adaptor Unit
UDP
- User Datagram Protocol
UMTS
- Universal Mobile Telecommunication System
VTCD
- Voice Transcoder Card based on DSP
II