Test

ZXG10 iBSC Alarm Handling
Objective
• Grasp concepts related to GSM alarms at

BSS.
• Grasp common alarms of iBSC.
Contents
• Alarm Overview
• Common Equipment Alarms of iBSC
• Common Communication Alarms of iBSC
• Common Processing Alarms of iBSC
• Common Environment Alarms of iBSC
• Common QoS Alarms of iBSC
Alarm Management
1. Main Menu 2. Toolbar 3. Resource View, Management View 4. Alarm Information View 5. Message Bar 6. Status Bar
Alarm View
 Alarm
Alarm is the prompt message about the fault that
occurs continuously and influences the system
services and the system reliability. Usually, the alarm
lasts for a period of time and disappears until the
problem or fault is removed.
 Notification
Notification refers to unrepeatable or transient
fault/event occured during the system operation.
Alarm
 Alarm Property
 Alarm Code Severity Alarm Type
 Description Equipment Alarm
 Severity Critical Communications Alarm
 Alarm Type
Major Operation Alarm
Minor Environment Alarm
 Probable Cause
Warning QoS Alarm
 System Impact OMS Alarm
 Handling Suggestion
Notification
 Notification Property
 Notification Code Importance Notification Type
 Description Major
-
 Importance Minor
 Notification Type
 Probable Cause
 System Impact
Contents
• Alarm Overview
198026127 Clock reference source lost (Level 3 alarm)
 Alarm Property
 Alarm Code: 198026127
 Description: Clock reference source lost (Level 3
alarm)
 Severity: Minor
 Alarm Type: Equipment Alarm
 Probable Cause
The input clock reference is in unavailable status for no
more than 10 minutes.
Probable causes include:
1. Clock reference input is abnormal.
2. The configured clock reference does not exist.
198026127 Clock reference source lost (Level 3 alarm)
 System 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. There is no impact on the
service.
1. Re-connect the input clock reference.
2. For the clock reference out of use, delete the
corresponding 'Circuitry Clock Reference'
configuration on the NMS configuration management
interface (board property).
198002560 Board CPU overloaded
 Alarm Property
 Alarm Code: 198002560
 Description: Board CPU overloaded
 Severity: Major
 Probable Cause
1. Excessive data traffic at higher layer.
2. System is performing data synchronization or saving.
3. CPU alarm threshold setting is under configured.
 System 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 impacts 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.
1. Open the rack diagram 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.
198087345 CPU Overload Control Alarm at FUC Mode
 Alarm Property
 Alarm Code: 198087345
 Description: CPU Overload Control Alarm at FUC
Mode
 Severity: Minor
 Probable Cause
The CPU load exceeds the flow control threshold in
module parameter setting.
198087345 CPU Overload Control Alarm at FUC Mode
 System Impact
Some users cannot gain access.
1. On the NMS Fault Management interface, check the
alarm details, which give the flow control level. If the
level of flow control is no more than 3, observe it for
three minutes until the alarm disappears.
2. Block some cells through dynamic data management to
prevent CPU load from increasing. After the alarm is
eliminated, unblock the related cells.
Contents
• Alarm Overview
198087337 Site Abis control link broken
 Alarm Property
 Alarm Code: 198087337
 Description: Site Abis control link broken
 Severity: Critical
 Alarm Type: Communication Alarm
 Probable Cause
1. The site configured on NMS client does not actually
exist.
2. For IP site, the IP configuration on NMS client is not
correct.
3. For E1 site, Abis timeslot of the master rack
configuration on NMS client is not correct.
4. The cable connections are abnormal.
 System Impact
The cells under this site cannot provide any voice or
data services.
1. On the NMS configuration management interface,
check the site configuration through Configuration
Resource Tree. If the configured site does not
actually exist, delete it and then synchronize the data
on BSC and NMS.
2. For IP site, on the NMS configuration interface,
check the Interface configuration under IP related
config on Configuration Resource Tree.
The IPBB item should be configured with the IP
address of the gateway from BTS to BSC. The BPC
item should be configured with the virtual IP address
of the SCTP link from BTS to BSC.
If the configurations are inconsistent with the NMS at
BTS side, correct them and synchronize the data at
BSC and BTS.
3. For E1 site, on the NMS configuration interface,
check the Abis timeslot of master rack configuration
at the site.
4. Check the cables between BTS and BSC to ensure
they are correct.
198087342 Cell Interruption Alarm
 Alarm Property
 Alarm Code: 198087342
 Description: Cell Interruption Alarm
 Severity: Minor
 Alarm Type: Communication Alarm
 Probable Cause
1. The site to which the cell belongs is lost.
2. The cell BCCH frequency is faulty.
 System Impact
The cell cannot provide any voice or data services.
1. On the NMS Fault Management interface, check if
related alarms exist. If yes, follow the suggestions for
handling the related alarms.
The related alarm is as follows:
2. On the NMS Dynamic Data Management interface,

check if the cell state is abnormal.
On the Radio Resource Management tab, check
BTS management, TRX management, and TS
management.
1. BTS management
 If manually blocked BTSs exist, unblock them.
 If global reset cell blockage exists, rectify A interface
faults.
2. TRX management
 If the BCCH of the cell concerned is manually blocked,
unblock the TRX.
 If “LAPD break cause TRX to block” exists, restore the
LAPD link.
 If CU or FU operation state of the TRX is blocked,
rectify the TRX fault.
3. TS management
If the BCCH TS of the cell concerned is manually
blocked, unblock the TS.
Contents
• Alarm Overview
198005123 DB Config Doesn't Fit for Device
 Alarm Property
 Alarm Code: 198005123
 Description: DB Config Doesn't Fit for Device
 Severity: Minor
 Alarm Type: Processing Alarm
 Probable Cause
1. The type of physical board is incorrectly configured.
2. A wrong board is inserted.
198005123 DB Config Doesn't Fit for Device
 System Impact
The board fails to be normally powered on. The services
carried by the board are interrupted.
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.
198005387 Alarm Due to Inconsistent MP Type
 Alarm Property
 Alarm Code: 198005387
 Description: Alarm Due to Inconsistent MP Type
 Severity: Major
 Alarm Type: Processing Alarm
 Probable Cause
1. The MP type is changed on NMS and the board is
not restarted.
2. The active MP type on the local board is inconsistent
with that configured on NMS.
198005387 Alarm Due to Inconsistent MP Type
 System Impact
This alarm has no impact on the service.
Reset the board.
Contents
• Alarm Overview
198025856 Rack temperature is higher than high threshold
 Alarm Property
 Alarm Code: 198025856
 Description: Rack temperature is higher than high
threshold
 Severity: Minor
 Alarm Type: Environment Alarm
 Probable Cause
1. Threshold configuration is unreasonable.
2. Actual rack temperature is too high.
 System Impact
1. If the alarm is caused by unreasonable threshold
configuration, the service will not be affected.
2. If the alarm is caused by high rack temperature,
board operation might be abnormal and board
services might be interrupted.
1. On the NMS configuration management interface
(power board alarm parameters), check the upper
limit of rack temperature. Modify the threshold value
if the previous configuration is unreasonable.
The recommended upper threshold value is 70.
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 at the air inlet and outlet of the rack.
Remove the nearby objects that obstruct rack
ventilation.
4. Ensure that the rack fan works normally.
198025864 Fault in fan plug-in box
 Alarm Property
 Alarm Code: 198025864
 Description: Fault in fan plug-in box
 Severity: Minor
 Alarm Type: Environment Alarm
 Probable Cause
1. FAN module is not tightly inserted into the rack.
2. FAN module hardware is faulty.
198025864 Fault in fan plug-in box
 System Impact
This alarm might lead to excessively high rack
temperature, resulting in abnormal board operation and
interruption of board services.
1. Check if the FAN module is tightly inserted into the
rack. If not, unplug and plug the FAN module.
2. Replace the FAN module.
Contents
• Alarm Overview
198023296 Inter-board Message Communication
Flow Rate Over Alarm Threshold
 Alarm Property
 Alarm Code: 198023296
 Description: Inter-board Message Communication
 Severity: Minor
 Alarm Type: QoS Alarm
 Probable Cause
The configured alarm threshold is less than the usual
inter-board communication traffic in input and output
directions of the board control plane.
198023296 Inter-board Message Communication
 System Impact
No impact on user service.
On the NMS configuration management interface, check
if the configured alarm threshold of communication
traffic in input and output directions of the board control
plane is too low.
Recommended value: 0xffffffff(4096M).

Test

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Test

Uploaded by

Copyright:

Available Formats

ZXG10 iBSC Alarm Handling

• Grasp concepts related to GSM alarms at

2. Check for the record of data synchronization, data

2. On the NMS Dynamic Data Management interface,

2. Check the thermometer in equipment room to see if

You might also like