ZXWR RNC (V3.07.310) Radio Network Controller Notification Handling Reference

ZXWR RNC
Radio Network Controller
Notification Handling Reference

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

V3.17.310d+NetnumenM31V3.10.420a)
Serial Number: sjzl20092956
Contens
Preface............................................................... i
Overview ...........................................................1
Overview of Fault Management......................................... 1
Fault View ..................................................................... 1
Alarm ....................................................................... 1
Notification ................................................................ 2
Alarm ........................................................................... 2
Alarm Property........................................................... 2
Alarm Code ....................................................... 2
Description........................................................ 2
Severity............................................................ 2
Alarm Type........................................................ 3
Probable Cause .......................................................... 3
System Impact........................................................... 3
Handling Suggestion ................................................... 4
Notification .................................................................... 4
Notification Property ................................................... 4
Notification Code................................................ 4
Description........................................................ 4
Importance ....................................................... 4
Notification Type ................................................ 4
Probable Cause .......................................................... 5
System Impact........................................................... 5
Handling Suggestion ................................................... 5
Notifications ......................................................7
198000576 Trunk Slide ................................................... 8
198001600 One of CPUs on One of Boards in This Shelf
Resets (Exceptionally) ............................................. 9
198003394 Entering Daylight Savings Time ....................... 9
198003395 Quitting Daylight Savings Time ........................ 9
198005188 UIM CS Changeover ......................................10
198005192 Boards Work Mode Unsupported.....................10

198005193 Notification of the power-on status of the
basic process ........................................................11
198005441 Port Status on GLI Media Plane Is
Changed. .............................................................11
198005448 485 Set Failure .............................................12
198005700 DSP resets for abnormities .............................12
198005701 Version Load Error ........................................13
198005710 The result of base selection of sets chip ...........14
198005711 The action of select base is working.................14
198005712 The manual select base will be run, please
wait for the result ..................................................14
198005713 APCs RAM error ...........................................15
198005715 PP2S source switched ....................................15
198005956 Board Version Error.......................................15
198005958 IDE Version Files Synchronization
Information ..........................................................16
198005961 OMP Version Check Information ......................17
198005962 Patch version operate fail ...............................17
198010560 No message response in the link for a long
time ....................................................................18
198011840 M3UA user office status change ......................18
198013888 ASP status changed ......................................19
198013889 AS status changed ........................................20
198013890 Sigtran error message received ......................20
198013891 Sigtran notification message received ..............21
198014144 Association establishment failed......................21
198014145 Association restart ........................................22
198019777 APS Switchover Happens ...............................23
198020802 Conflicting IP addresses.................................23
198020803 Conflicting MAC Addresses in Subnet ...............24
198023106 Board Self-Check Failure ................................25
198023107 Board Initialization Failure..............................25
198025664 Abnormal Half-fixed Connection Changes .........26
198026178 Clock work mode changed..............................26
198066065 SCTP Primary Path Set Failed..........................27
198070002 Iu interface global reset notification.................27
198070003 Iu interface resource reset notification .............28
198070004 RNC started Iu interface global reset failure
notification ...........................................................29
198070005 RNC started Iu interface resource reset failure

notification ...........................................................29
198070008 RNC and Node B CCPID configuration are not
identical ...............................................................30
198070009 Broadcast fail ...............................................30
198070010 OMCR failed to fetch FTP file...........................31
198070011 File operation failure between OMCR and RNC
NE ......................................................................32
198083017 the route table of MicroCode subsystem of
this board is overloaded .........................................32
198083019 MicroCode subsystem failed to get the table
of configuration .....................................................33
198083025 Common Channel setup failed notification .........35
198083026 MicroCode subsystem failed to handle DHCP
message from other network...................................36
198083028 Logservice is unavailable................................37
198083029 Performance file store failed ..........................38
Figures ............................................................ 41
Tables ............................................................. 43
List of Glossary................................................ 45
Preface
Purpose
WCDMA 3G mobile telecommunication system, independently developed by ZTE, consists of ZXWN (ZTE WCDMA Core Network)
and ZXWR (ZTE WCDMA Radio Network Subsystem). ZXWR consists of ZXWR RNC (Radio Network Controller) and ZXWR Node B.
This manual introduces the notifications that might occur during
the installation, operation and maintenance of ZTE WCDMA RNC
product. Notification code and description displayed by NetNumen
M31 unified NMS, probable cause for the notification, and the corresponding handling suggestion are covered in this manual.
What is in This
Manual
Intended
Audience
Summary
Chapter
Chapter 1, Overview
of Fault Management
Introduces the concept of fault management,

as well as the definition, type, level
classification of alarm and notification.
Chapter 2, Notification
Introduces RNC notifications with respect to

notification property, probable cause, system
impact, and handling suggestion.
NM engineer
Maintenance engineer
Confidential and Proprietary Information of ZTE CORPORATION
ZXWR RNC Notification Handling Reference
This page is intentionally blank.
ii
Chapter
Overview
Table of Contents
Overview of Fault Management.............................................
Fault View .........................................................................
Alarm ...............................................................................
Notification ........................................................................
1
1
2
4
Overview of Fault
Management
Fault management is responsible for collecting information of failures and events that occur during system operation or service processing.
The information, in the form of alarm or notification, is stored in
database or displayed on realtime basis via a user-oriented fault
monitoring platform. Means such as visual-interface monitor or
history information query can be used to view current or historical system operation and service processing status. Fault management enables maintenance personnel to troubleshoot and take
preventive measures to remove potential fault and restore system
and services as early as possible.
Fault View
Fault is displayed in the form of alarm or notification.
Alarm
The fault that persists during system operation and affects system
reliability and normal services is referred to as an alarm. Alarm
usually lasts until fault removal.
Due to its possible impact on normal system operation, alarm requires timely troubleshooting in which alarm cause is identified,
and the fault is located and handled.
Notification
Notification refers to the non-repeated/instantaneous fault or
event that occurs during system operation. Examples include
board reset, signaling overload, etc.
Notification is mostly caused by sudden environment change
or other accidental factors. No special handling is required for
the notification, which can be automatically removed by the
system. Only the notification that occurs persistently requires
troubleshooting.
Alarm
Alarm Property
Alarm Code
Alarm code is the identifier which differentiates alarms.
Alarm code is defined by a 32-bit field indicating the specific code
value.
Description
Alarm description reflects such content as fault cause and fault
phenomenon in a simple and straightforward way.
Severity
There are four alarm levels, which are indicated in descending order of severity as Critical, Major, Minor, and Warning.
Critical alarm causes system breakdown and service interruption. It requires immediate troubleshooting.
Major alarm significantly affects system operation or weakens

network service capability. It requires troubleshooting as soon
as possible.
Minor alarm affects system operation and network service

capability in a nonsignificant way. It requires timely troubleshooting so as to avoid severity escalation.
Warning poses a potential hazard to system operation and network service capability. It requires troubleshooting at an appropriate time so as to avoid severity escalation.
Chapter 1 Overview
The degree of impact as described in the definition of alarm severity refers to the impact of a single index, such as reliability and
security. Once the impact on any of the index reaches the specified threshold, the severity level of the alarm can be roughly determined. If an alarm has an impact on multiple indices, alarm
severity should be escalated accordingly.
Note:
Alarm severity can be modified in NetNumen M31 NMS (network
management system) if necessary.
Generally speaking, the default alarm severity is reasonably set.
Users should think twice before making any modification.
In addition, the severity of few alarms is undefined. It is up to
users to define the severity of such alarms.
Alarm Type
Alarm is classified into six types according to alarm trigger condition and its system impact.
Equipment alarm: related with device hardware.
Communication alarm: related with information transmission

(ITU-T Recommendation X.733).
Processing alarm: related with software or process fault (ITU-T

Recommendation X.733).
Environment alarm: related with the environment where the

equipment is located (ITU-T Recommendation X.733).
QoS alarm: related with degradation of service quality (ITU-T

Recommendation X.733).
OMS alarm: related with the network management system.
Probable Cause
Probable alarm causes are enumerated to help users troubleshoot,
find preventive measures, and restore the system to normal state
in a timely manner.
System Impact
System impact refers to the impact that the alarm incurs on system or services.
Handling Suggestion
Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling alarms.
After recording the fault phenomenon, O&M personnel may

handle the fault step by step as described in the Handling Suggestion Section of this manual. If the fault is removed (alarm
restored) at any handling step, terminate the handling process.
If the fault is not removed, go ahead to the next handling step.
If the fault cannot be removed, contact the local ZTE office as

soon as possible.
Notification
Notification Property
Notification Code
Notification code is the identifier to differentiate notifications.
Notification code is defined by a 32-bit field indicating the specific
code value.
Description
Notification description reflects such content as fault cause and
fault phenomenon in a simple and straightforward way.
Importance
There are two levels of notification importance: Important and
Ordinary.
Notification Type
No notification type exists.
Chapter 1 Overview
Probable Cause
Probable notification causes are enumerated to help users troubleshoot, find preventive measures, and restore the system to
normal state in a timely manner.
System Impact
System impact refers to the impact that the notification incurs on
system or services.
Handling Suggestion
Troubleshooting measures and suggestions are provided.
Pay attention to the following tips when handling notifications.
After recording the fault phenomenon, O&M personnel may

handle the fault step by step as described in the Handling Suggestion Section of this manual. If the fault is removed (alarm
restored) at any handling step, terminate the handling process.
If the fault is not removed, go ahead to the next handling step.
If the fault cannot be removed, contact the local ZTE office as

soon as possible.
Chapter
Notifications
Table of Contents
198000576 Trunk Slide ....................................................... 8
198001600 One of CPUs on One of Boards in This Shelf Resets
(Exceptionally) ................................................................... 9
198003394 Entering Daylight Savings Time ........................... 9
198003395 Quitting Daylight Savings Time ............................ 9
198005188 UIM CS Changeover ..........................................10
198005192 Boards Work Mode Unsupported.........................10
198005193 Notification of the power-on status of the basic
process ............................................................................11
198005441 Port Status on GLI Media Plane Is Changed. .........11
198005448 485 Set Failure .................................................12
198005700 DSP resets for abnormities .................................12
198005701 Version Load Error ............................................13
198005710 The result of base selection of sets chip ...............14
198005711 The action of select base is working ....................14
198005712 The manual select base will be run, please wait
for the result ....................................................................14
198005713 APCs RAM error ...............................................15
198005715 PP2S source switched ........................................15
198005956 Board Version Error...........................................15
198005958 IDE Version Files Synchronization Information .................................................................................16
198005961 OMP Version Check Information ..........................17
198005962 Patch version operate fail...................................17
198010560 No message response in the link for a long
time ................................................................................18
198011840 M3UA user office status change ..........................18
198013888 ASP status changed ..........................................19
198013889 AS status changed ............................................20
198013890 Sigtran error message received ..........................20
198013891 Sigtran notification message received ..................21
198014144 Association establishment failed..........................21
198014145 Association restart ............................................22
198019777 APS Switchover Happens ...................................23
198020802 Conflicting IP addresses.....................................23
198020803 Conflicting MAC Addresses in Subnet ...................24
198023106 Board Self-Check Failure ....................................25
198023107 Board Initialization Failure..................................25
198025664 Abnormal Half-fixed Connection Changes .............26
198026178 Clock work mode changed .................................26
198066065 SCTP Primary Path Set Failed .............................27
198070002 Iu interface global reset notification ....................27
198070003 Iu interface resource reset notification .................28
198070004 RNC started Iu interface global reset failure notification ............................................................................29
198070005 RNC started Iu interface resource reset failure notification...........................................................................29

198070008 RNC and Node B CCPID configuration are not
identical ...........................................................................30
198070009 Broadcast fail ...................................................30
198070010 OMCR failed to fetch FTP file...............................31
198070011 File operation failure between OMCR and RNC NE
......................................................................................32
198083017 the route table of MicroCode subsystem of this
board is overloaded ...........................................................32
198083019 MicroCode subsystem failed to get the table of
configuration ....................................................................33
198083025 Common Channel setup failed notification ............35
198083026 MicroCode subsystem failed to handle DHCP message from other network ....................................................36
198083028 Logservice is unavailable ...................................37
198083029 Performance file store failed ..............................38
198000576 Trunk Slide

Notification
Property
Notification Code: 198000576
Description: Trunk Slide
Importance: Ordinary
Probable 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.
System Impact
Momentary fault occurs to trunk data service or signaling channel.

If fault occurs repeatedly, CS/PS service might become unstable.
Otherwise, service is not affected.
Handling
Suggestion
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)
Chapter 2 Notifications
198001600 One of CPUs on

One of Boards in This Shelf
Resets (Exceptionally)
Notification
Property
Probable Cause
Description: One of CPUs on One of Boards in This Shelf Resets

(Exceptionally)
Importance: Important
A certain CPU of a certain board in the shelf abnormally resets.

Probable causes include:
1. Manual operation (for example, unplugging and plugging
board, resetting NMS, or pressing panel reset button).
2. Abnormal board reset.
System Impact
The service or communication link related to the resetting board

is down, but will be restored after board power-on.
Handling
Suggestion
1. Check the NMS operation log to see if manual reset operation

has been performed. If yes, no handling is necessary.
2. Replace board.
198003394 Entering
Daylight Savings Time
Notification
Property
Description: Entering Daylight Savings Time
Probable Cause
The pre-configured Daylight Saving Time starts for the system.
System Impact
None.
Handling
Suggestion
No handling is necessary.
198003395 Quitting Daylight

Savings Time
Notification
Property
Probable Cause
Description: Quitting Daylight Savings Time
The pre-configured Daylight Saving Time ends for the system.
System Impact
Handling
Suggestion
None.
198005188 UIM CS
Changeover
Description: UIM CS Changeover
Probable Cause
1.
2.
3.
4.
5.
Optical module signal loss occurs.

Board input clock loss occurs.
Bit error rate at the optical interface is high.
Lock loss occurs to the phase-locked loop.
Bit error rate on the master/slave interconnecting link of GUIM
board is high.
System Impact
No impact on service.
Notification
Property
Handling
Suggestion
Check if the following alarm occurs in local/opposite board. If yes,

refer to the corresponding alarm handling suggestion.
Related alarms:
198001286 Loss of Clock When Input to Board
198005639 High Error Rate of Optical Interface
198005646 Phase-lock Loop Unlock
198005192 Boards Work

Mode Unsupported
Notification
Property
Description: Boards Work Mode Unsupported
Probable Cause
1. The configured board backup mode is unsupported.

2. FPGA is unloaded, leading to setting failure of board working
mode.
System Impact
Board master/slave backup function is disabled.
Handling
Suggestion
10
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.
198005193 Notification of
the power-on status of the
basic process
Notification
Property
Description: Notification of the power-on status of the basic

process
Probable Cause
1. Board power-on is successful.

2. Board power-on fails or expires.
System Impact
If the notification is power-on success, service will not be affected.

If the notification is power-on failure, the services on the board will
be unavailable.
Handling
Suggestion
On NMS fault management interface, view notification Details

where information of power-on status (Board poweron successful/failed/timeout) is given. Locate the corresponding handling
suggestion based on the given information. The handling suggestions that correspond to different power-on status are described
below.
1. Board poweron successful/failed/timeout: Poweron successful
2. Board poweron successful/failed/timeout: Poweron timeout
Ensure that the board loads the proper version. The boards in
a NE must use the version of the same version No.
3. Board poweron successful/failed/timeout: Poweron failed
Ensure that the board loads the proper version. The boards in
a NE must use the version of the same version No.
198005441 Port Status

on GLI Media Plane Is
Changed.
Notification
Property
Description: Port Status on GLI Media Plane Is Changed.
Probable Cause
1. Connection between UIM/GUIM and GLI is faulty.

2. Board is faulty.
System Impact
The impact varies depending on the "Port status" given in notification Details.
11
1. If the port status is "Master port invalid status" or "Master

port abnormal", the master port fails to forward inner media
stream, and the services on master port will be switched to
slave port. If the slave port is also unavailable, services on the
port will be interrupted.
2. If the port status is "Slave port invalid status" or "Slave port
abnormal", service will not be affected. However, the potential
hazard will emerge once master/slave switching occurs.
3. If the port status is others, service will not be affected.
Handling
Suggestion

where information of "Port status" is given.
1. If the port status is "Master port invalid status" or "Master port
abnormal", refer to the following handling suggestions.
i. Reconnect the cable between UIM/GUIM and GLI.
ii. Replace the optical module or cable used for the connection
between UIM/GUIM and GLI.
iii. Replace UIM/GUIM board.
iv. Replace GLI board.
2. If the port status is others, no handling is necessary.
198005448 485 Set Failure

Notification
Property
Description: 485 Set Failure
Probable Cause
1. 485 communication is interrupted.

2. The board is abnormal.
System Impact
The configured clock reference/environment threshold fails to take

effect. No impact on service.
Handling
Suggestion
1. Unplug and plug 485 cable.

2. Replace 485 cable.
3. Replace board.
198005700 DSP resets for

abnormities
Notification
Property
Probable Cause
12
Description: DSP resets for abnormities
1. DSP chip is faulty.

2. Board is faulty.
System Impact
Handling
Suggestion
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.
DSP resets automatically and abnormally.
If power-on is normal after DSP reset, the board can be restored to normal state.
If DSP resets repeatedly, replace the board or subcard.
198005701 Version Load

Error
Notification
Property
Probable Cause
Description: Version Load Error
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.
System 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.
Handling
Suggestion

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 activated.
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 subcard.
13
iii. Replace board.
198005710 The result of

base selection of sets chip
Notification
Property
Description: The result of base selection of sets chip
Probable Cause
After manual base switchover, man-machine command, or pressing panel button, SETS chip performs base locking operation (at
most for 2 minutes). This notification is to inform the user of the
operation result of manual base selection.
System Impact
None.
Handling
Suggestion
198005711 The action of

select base is working
Notification
Property
Description: The action of select base is working
Probable Cause
When selecting base manually, if the previous base selection is still

in process and operation result is yet to be given, the present manual base selection is shut down and this notification is declared.
System Impact
None.
Handling
Suggestion
198005712 The manual

select base will be run,
please wait for the result
Notification
Property
14
Description: The manual select base will be run, please wait

for the result
Probable 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.
System Impact
None.
Handling
Suggestion
198005713 APCs RAM

error
Notification
Property
Description: APCs RAM error
Probable Cause
Board hardware is faulty.
System Impact
The board where RAM is located is down. ATM cell fails to be forwarded, and all board services are interrupted.
Handling
Suggestion
Replace board.
198005715 PP2S source

switched
Notification
Property
Description: PP2S source switched
Probable Cause
PP2S (Pulse Per 2 Seconds) source is changed at both system clock

and GPS receiver sides.
System Impact
None.
Handling
Suggestion
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.
198005956 Board Version

Error
Notification
Property
Description: Board Version Error
15
Probable Cause
1. A board is in the slot which is not configured with any board.

2. Board version is unconfigured.
3. Board version has been configured, but version file does not
exist or is damaged.
System Impact
The board fails to obtain version, leading to abnormal board operation and access failure of board services.
Handling
Suggestion
1. On NMS configuration management interface (rack), view rack

layout. Check if the slot is configured with any board. If no
board configuration exists, unplug the board in the slot.
2. On NMS fault management interface, view notification Details
where "Version type of abnormal board" is given. Load and
activate the version on NMS software management interface
according to the given "Version type".
198005958 IDE Version

Files Synchronization
Information
Notification
Property
Description: IDE Version Files Synchronization Information
Probable Cause
Synchronization of master/slave OMP version files occurs.
System 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.
Handling
Suggestion

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.
16
198005961 OMP Version

Check Information
Notification
Property
Description: OMP Version Check Information
Probable Cause
The version file in software version configuration does not exist in

RNC NE.
System Impact
If the non-existent version file is not in use, service will not be

affected.
If the non-existent version file is the activated version, the

corresponding board will fail to fetch version during poweringon, leading to service access failure. This rarely happens.
Handling
Suggestion

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.
198005962 Patch version

operate fail
Notification
Property
Description: Patch version operate fail
Probable Cause
1. Patch version file and CPU version file do not match.

2. Patch version file does not exist in RNC NE.
3. The patch version file related to the patch does not exist in
RNC NE.
System Impact
Patch version activation fails. New functions of the patch version

are unavailable. No impact on service.
Handling
Suggestion
If the patch version is not needed, delete the corresponding

version configuration on NMS software management interface.
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.
17
198010560 No message
response in the link for a
long time
Notification
Property
Description: No message response in the link for a long time
Probable Cause
Bottom layer link quality is poor, there is no message response for

the link for a long time.
System Impact
Related link will be interrupted and cannot bear service.
Handling
Suggestion
1. Check if physical connection works normally.

2. Check NMS alarms/notifications to see whether there exists
physical transmission alarm(s) /notification(s) that occurred
simultaneously with this alarm. If yes, refer to the corresponding alarm/notification handling suggestion.
Alarms/Notifications related to physical transmission are listed
below, with respect to access mode.
i. Fiber Access Mode
198001792 SDH/SONET fault
198066047 Abnormal status in SDH/SONET
198066048 SDH/SONET:Excessive Error Code
ii. E1 Access Mode
198005647 High Error Rate at E1 Bottom Layer
198066045 Trunk error
198066046 Trunk abnormal
198000576 Trunk Slide
198011840 M3UA user

office status change
Notification
Property
Probable Cause
18
Description: M3UA user office status change
1. User configuration of this office is changed.

2. Bottom-layer links are unavailable.
3. The signaling network management message from opposite
end is received.
System Impact
Handling
Suggestion
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.
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.
198013888 ASP status

changed
Notification
Property
Description: ASP status changed
Probable Cause
1. Association status is changed.

2. ASP operation is performed at opposite end.
3. ASP operation is performed in dynamic data management at
local end.
System Impact
If this notification and the alarm of 198066014 M3UA office

inaccessible are declared at the same time, access failure of
new services under this office and abnormal release of ongoing
services will occur.
If merely this notification is declared, service will not be affected.
Handling
Suggestion
1. Check whether association interruption alarm occurs. If yes,

Related alarm:
2. Activate the ASP in dynamic data management.
3. Check whether ASP operation is performed at the opposite end.
19
198013889 AS status
changed
Notification
Property
Description: AS status changed
Probable Cause
1. Association status is changed.

2. ASP operation is performed at opposite end.
3. ASP operation is performed in dynamic data management at
local end.
System Impact
If this notification and the alarm of 198066014 M3UA office

inaccessible are declared at the same time, access failure of
new services under this office and abnormal release of ongoing
services will occur.
If only this notification is declared, service will not be affected.
Handling
Suggestion
1. Check whether association interruption alarm occurs. If yes,

Related alarm:
2. Activate ASP under the AS in dynamic data management.
198013890 Sigtran error

message received
Notification
Property
Description: Sigtran error message received
Probable Cause
1. AS configuration is wrong.
2. Protocol versions used at both sides are different.
System Impact
The corresponding AS fails to be activated, making M3UA office

inaccessible. Reception and sending of message from/to the office
fail. Access of new services under the office fails.
Handling
Suggestion
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.
20
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.
198013891 Sigtran
notification message
received
Notification
Property
Description: Sigtran notification message received
Probable Cause
1. The broken association leads to insufficiency of the number of

ASP in service for AS.
2. Release of ASP in dynamic data management leads to insufficiency of the number of ASP in service for AS.
System Impact
The number of ASP in service for AS is insufficient. If traffic is

heavy, congestion or packet loss might occur, leading to call loss
or increasing PS call access failures. Otherwise, service is not affected.
Handling
Suggestion
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:
2. Reactivate ASP in dynamic data management.
198014144 Association
establishment failed
Notification
Property
Description: Association establishment failed
21
Probable Cause
1. Association configuration at both sides is inconsistent.

2. No less than two associations are configured with same local
address and port, but with different protocol types.
3. Interface board IP address is wrong, or physical link is down.
System Impact
If several association links are available to the destination office, service will not be affected by establishment failure of one
association. 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
services under this office fails.
Handling
Suggestion
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.
198014145 Association
restart
Notification
Property
22
Description: Association restart
Probable Cause
The local end receives a link creation request but detects no link
break, and the association restarts. Probable causes for the alarm
include:
1. Relevant board at peer end resets.
2. The Association link is reestablished at peer end.
System Impact
None.
Handling
Suggestion
No handling is necessary, wait association to restart.
198019777 APS Switchover

Happens
Notification
Property
Probable Cause
Description: APS Switchover Happens
1. Optical interface is faulty. LOS/SF/SD alarms might exist.

2. During inter-board backup, any of the following events occurs.
i. Input clock loss
ii. Inner HW/LVDS alarm
iii. Inner media plane port alarm iv. ENUM open (board not
properly inserted)
iv. Board reset (the board where the working optical interface
is located)
3. Switching is initiated by opposite end.
4. In recovery mode, fault recovery time in optical interface exceeds 5 minutes.
5. APS switching request/clearance is initiated by NMS.
System Impact
During APS switching, the link is interrupted for 10 ~ 50 ms. Few

packet loss might occur, but service is not affected.
Handling
Suggestion
Check operation and maintenance log to see if O&M personnel initiated manual APS switching request/clearance. If yes, no handling
is necessary. If no, check if the following alarms are declared in
the board. If such alarm exists, refer to the corresponding alarm
handling suggestion.
Related alarms:
198005396 Exceptional Internal Media Plane Communication
198005378 Board HW Error
198005635 The board is not plugged firmly
198020802 Conflicting IP
addresses
Notification
Property
Description: Conflicting IP addresses
23
Probable Cause
1. The IP address of this port (including the virtual address in the

same network section) is the same with that of another host
in the local network.
2. Loop exists in the opposite switch connected with this port.
System Impact
Board operation is normal. Communication network is faulty. All

services on this port are down.
Handling
Suggestion
When this notification occurs, the NMS will display the conflicting
IP address, detects the 5-tuple information of the conflicting local port, and detects the MAC address of the external equipment
whose IP conflicts with the NE IP.
1. To view and modify local port IP, open NMS configuration management interface and perform the corresponding operation in
interface configuration (IP address).
To query external equipment port IP, please refer to the maintenance manual of the corresponding equipment.
2. The notification must be caused by the existence of loop in
the switch connected with the local port, if the following two
conditions are satisfied:
Notifications of "198020802 Conflicting IP Address" and

"198020803 Conflicting MAC Address in Subnet"occur concurrently;
Modification of local port IP does not work in restoring the
two notifications mentioned above.
In this case, check whether loop connection between two ports

exists on the opposite switch. Remove the loop connection if
such connection exists.
198020803 Conflicting MAC

Addresses in Subnet
Notification
Property
Description: Conflicting MAC Addresses in Subnet
Probable 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.
System 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.
Handling
Suggestion
When this notification occurs, the NMS will display the conflicting
MAC address, detects the 5-tuple information of the conflicting
local port, and detects the IP address of the external equipment
whose MAC address conflicts with the NE MAC address.
1. Modify local port MAC address, or the conflicting port MAC address of external equipment.
24
Refer to the 5-tuple information displayed in notification Details

to locate the conflicting local port. Local port MAC address
can be viewed and modified in interface configuration (MAC
Address) on NMS configuration management interface.
To query the port MAC address of external equipment, please
refer to the maintenance manual of the corresponding equipment.
2. The notification must be caused by the existence of loop in
the switch connected with the local port, if the following two
conditions are satisfied:
Notifications of "198020802 Conflicting IP Address" and

"198020803 Conflicting MAC Address in Subnet" occur concurrently;
Modification of local port IP does not work in restoring the
two notifications mentioned above.
In this case, check whether loop connection between two ports

exists on the remote switch. Remove the loop connection if
such connection exists.
198023106 Board
Self-Check Failure
Notification
Property
Description: Board Self-Check Failure
Probable Cause
System Impact
The board fails to power on and operate, resulting in UE access

failure and interruption of ongoing services.
Handling
Suggestion
Replace board.
198023107 Board
Initialization Failure
Notification
Property
Description: Board Initialization Failure
Probable Cause
System Impact
The board fails to power on and operate, resulting in UE access

failure and interruption of ongoing services.
25
Handling
Suggestion
Replace board.
198025664 Abnormal
Half-fixed Connection
Changes
Notification
Property
Description: Abnormal Half-fixed Connection Changes
Probable Cause
1. Abnormal jitter occurs to the line clock of the shelf where the
board is located.
2. The switching chip of the board is faulty.
System Impact
TMD channel is interrupted momentarily, which might have a minor impact on service.
Handling
Suggestion
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
198026133 Clock Output Loss
2. Replace the faulty board.
198026178 Clock work

mode changed
Notification
Property
26
Description: Clock work mode changed
Probable Cause
The clock work mode of the CLKG board has changed.
System Impact
System could not get the needed clock.
Handling
Suggestion
198066065 SCTP Primary

Path Set Failed
Notification
Property
Description: SCTP Primary Path Set Failed
Probable 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
System 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.
Handling
Suggestion
On NMS fault management interface, view notification Details,

where information of association ID and the primary path remote
IP address is given. If the primary path remote IP address listed
in notification Details is selected as the primary path, follow the
steps below at opposite end.
1. Add the IP as an interface address at opposite end
2. Add the "primary path remote IP address" given in notification
Details into the local IP address list of the relevant SCTP.
198070002 Iu interface
global reset notification
Notification
Property
Description: Iu interface global reset notification
Probable Cause
1. RESET message is sent by CN.

2. The signaling point of the office related to the CN is inaccessible.
3. Global reset is triggered by NMS.
System Impact
The services that have been established are released. Access of

new service is denied. Service access will be restored in 3 seconds.
Handling
Suggestion

where Alarm Reason is given. Locate the specific alarm handling
suggestion according to the given reason. The handling suggestions that correspond to different reasons are described below.
1. CN reset.
27
i. RESET message is initiated by CN NMS. View CN NMS operation log to see if the reset is initiated. If yes, no handling
is necessary.
ii. Check if transmission-related/board alarm occurs in the
board. If yes, refer to the corresponding alarm handling
suggestion.
Related alarms:
198066005 SCCP SSN is invalid
198066010 MTP3 office inaccessible
198066014 M3UA office inaccessible
2. CN unaccessible. Check if transmission-related/board alarm

occurs. If yes, refer to the corresponding alarm handling suggestion.
Related alarms:
3. OMCR initiate IU reset. The alarm is caused by manual reset

operation. Check RNC NMS operation log to see if the reset
operation exists. If yes, no handling is necessary.
198070003 Iu interface
resource reset notification
Notification
Property
Description: Iu interface resource reset notification
Probable Cause
RESET RESOURCE message is sent by RNC.
System Impact
The service that initiates resource reset is released.
Handling
Suggestion
Check if transmission-related/board alarm occurs. If yes, refer to

the corresponding alarm handling suggestion.
Related alarms:
28
198070004 RNC started Iu

interface global reset failure
notification
Notification
Property
Description: RNC started Iu interface global reset failure notification
Probable Cause
RNC fails to receive reset response message from CN.
System Impact
Access of new service fails. Service access is restored to normal

state in 3 seconds.
Handling
Suggestion
On NMS configuration management interface (MSC SERVER/SGSN

in transmission configuration), check if the MCC and MNC configured by RNC and that configured by CN are consistent. If no,
modify configuration to keep consistency.
198070005 RNC started

Iu interface resource reset
failure notification
Notification
Property
Description: RNC started Iu interface resource reset failure

notification
Probable Cause
RNC fails to receive resource reset response message from CN.
System Impact
No impact on service.
Handling
Suggestion
On NMS configuration management interface (MSC SERVER/SGSN

in transmission configuration), check if the MCC and MNC configured by RNC and that configured by CN are consistent. If no,
modify configuration to keep consistency.
29
198070008 RNC and Node

B CCPID configuration are
not identical
Notification
Property
Description: RNC and Node B CCPID configuration are not

identical
Probable Cause
The CCP ID configured on RNC side and on Node B side is inconsistent.
System Impact
The relevant CCP is unavailable during service establishment.
Handling
Suggestion
1. On NMS configuration management interface (SCTP stream

configuration), modify CCP ID under transmission layer management.
2. On NMS configuration management interface (NE information
configuration), select the relevant Node B. Modify CCP ID in
Node B port configuration.
198070009 Broadcast fail

Notification
Property
Description: Broadcast fail
Probable Cause
1. Configuration related to the system broadcast information of

the cell is incorrect.
2. Transmission is faulty.
System Impact
The cell is unavailable. UE access to the cell fails, and all cell
services are down.
Handling
Suggestion

where Alarm Reason is given. Locate the specific handling suggestion according to the given reason. The handling suggestions
that correspond to the reasons are described below.
1. Alarm reason: Get system information from database failed.
View notification Details where bySIBType information is
given. For example, SIB type=1 indicates fetching failure
of Sib1. Check if the Sib1-related parameter configuration is
correct and if the configuration exists in the cell. The mapping
relationship between SIB type and the configuration required
to be checked is listed below.
i. SIB type=1
On NMS configuration management interface (UE timers
and constants information), check UE timers and counters
in idle and connected status.
30
ii. SIB type=2

On NMS configuration management interface (UTRAN cell),
check URA ID in UTRAN cell global information.
iii. SIB type=3
On NMS configuration management interface (cell selection
and reselection), check cell selection/reselection information parameters and cell access limit parameters.
iv. SIB type=5
On NMS configuration management interface (UTRAN cell),
check common transport channel parameters in SCCPCH
and RACH.
2. Alarm reason: Exceed system broadcast ability.
The notification might be caused by transmission fault. Check
if transmission-related alarm exists in the Node B that the cell
belongs to. If yes, refer to the corresponding alarm handling
suggestion.
i. IP Mode
Check if related alarm exists according to the given association ID.
Related alarms:
198066018 Association congested
ii. ATM Mode
Bottom layer transmission fault. Check if related alarm

exists.
Related alarms:
198066047 Abnormal status in SDH/SONET
198066048 SDH/SONET: Excessive Error Code
PVC unavailable. Check if related alarm exists.

Related alarm:
198018944 PVC Fault
198070010 OMCR failed to

fetch FTP file
Notification
Property
Probable Cause
Description: OMCR failed to fetch FTP file
The FTP channel between NMS and RNC NE is faulty.
31
System Impact
NMS fails to fetch alarm files from RNC NE, and alarm information
is lost. No impact on user service.
Handling
Suggestion
When the link between NMS and RNC NE is normal, open NMS
fault management interface to perform alarm synchronization and
fetch the latest alarm information of RNC NE, so that the alarm
information of NMS and that of RNC NE is consistent.
198070011 File operation

failure between OMCR and
RNC NE
Notification
Property
Description: File operation failure between OMCR and RNC NE
Probable Cause
1. Disk is full.
2. Disk is faulty.
System Impact
RNC NE fails to save alarm files, and alarm information is lost. No

impact on user service.
Handling
Suggestion
1. Clean the hard disk space. Delete the files no longer in use or
move such files to other external devices.
2. Replace board or board hard disk.
3. When the link between NMS and RNC NE is normal, open NMS
fault management interface to perform alarm synchronization
and to fetch the latest alarm information of RNC NE, so that
the alarm information of NMS and that of RNC NE is consistent.
198083017 the route table

of MicroCode subsystem of
this board is overloaded
Notification
Property
Probable Cause
32
Description: the route table of MicroCode subsystem of this

board is overloaded
There are too many configured route entries For RUB board
(VTCD), the table can contain at most 360 route entries. For
RUB board (VTCD_2), the table can contain at most 1024 route
entries. The alarm is declared when the number of route entries
reaches 90% of the table capacity threshold.
System Impact
1. If the number of route entries does not exceed the RUB board
route table capacity, service will not be affected.
2. If the number of route entries exceeds the RUB board route
table capacity, information of some route entries will be lost.
i. If the missing route are the route to Node B or CN, UE
service access to the board will fail.
ii. If the missing route are the route to other RNC NE, access of
Inter-RNC UE services to the board will fail. Meanwhile, tick
clock synchronization of the MBMS service between the relevant RNC NEs will fail, degrading the MBMS service quality.
3. If the number of route entries exceeds the RUB board route
table capacity, the SLA diagnostic test function from RNC to
related NE will be disabled.
Handling
Suggestion
1. On NMS configuration management interface (static route),

delete the routes that are not in use.
2. On NMS configuration management interface (interface configuration), delete the port IP that is no longer in use.
198083019 MicroCode
subsystem failed to get the
table of configuration
Description: MicroCode subsystem failed to get the table of

configuration
Probable Cause
1.
2.
3.
4.
5.
6.
7.
Failed
Failed
Failed
Failed
Failed
Failed
Failed
System Impact
The system impacts that correspond to different alarm causes are

described below.
Notification
Property
to
to
to
to
to
to
to
get
get
get
get
get
get
get
the information of the RUIB.

the configuration of OMCB server.
the configuration of signal dispatch table.
the configuration of IP/UDP.
the configuration of L2 table.
the configuration of path information.
the configuration of pathgroup information.
1. Failed to get the information of the RUIB.

The configuration information is used to reassemble the fragments of IP packets inputted into the equipment. Lacking the
configuration information may cause processing failure of fragments of IP packets. Service interruption might occur or service processing rate might slow down.
2. Failed to get the configuration of OMCB server.
Lacking the configuration information may paralyze OMCB
function.
3. Failed to get the configuration of signal dispatch table.
33
Lacking the configuration information causes SCTP data transmission failure on the interface board. The service related to
SCTP Protocol on this board is down.
4. Failed to get the configuration of IP/UDP.
Lacking the configuration information may cause processing
failure of IUPS service, or processing failure of other data based
on IP transmission.
5. Failed to get the configuration of L2 table.
Lacking the configuration information may cause communication failure within the equipment. All services on the board
might be down.
6. Failed to get the configuration of path information.
In the case of ATM interface board, lacking the configuration information may incur processing failure of the AAL2
data based on ATM Adaptation Layer Protocol, leading to
interruption of IUB/IUCS/IUR services under this office.
In the case of IP interface board, lacking the configuration
information may incur processing failure of IP packet traffic
control, leading to interruption of all services under this
office.
7. Failed to get the configuration of pathgroup information.
Handling
Suggestion
In the case of ATM interface board, lacking the configuration information may incur processing failure of the AAL2
data based on ATM Adaptation Layer Protocol, leading to
interruption of IUB/IUCS/IUR services under this office.
In the case of IP interface board, service is not affected.
On NMS alarm management interface, view notification Details

where Alarm Reason is given. Locate the specific handling suggestion according to the given reason. The handling suggestions
that correspond to different reasons are described below.
1. Alarm Reason: Failed to get the information of the RUIB.
On NMS configuration management interface, check whether
Board Reassembling IP Fragments is configured. If no,
perform the corresponding configuration according to network
planning. Make sure to synchronize the configuration data at
NMS and RNC NE after configuration modification. Only after
synchronization can the configuration data take effect at RNC
NE.
2. Alarm Reason: Failed to get the configuration of OMCB server.
On NMS configuration management interface, check whether
master OMP IP is configured. If no, perform the corresponding configuration according to network planning. Make sure to
synchronize the configuration data at NMS and RNC NE after
configuration modification. Only after synchronization can the
configuration data take effect at RNC NE.
3. Alarm Reason: Failed to get the configuration of signal dispatch
table.
On NMS configuration management interface (SCTP association configuration), check whether the relevant office is configured. If no, perform the corresponding configuration according
to network planning. Make sure to synchronize the configura-
34
tion data at NMS and RNC NE after configuration modification.

Only after synchronization can the configuration data take effect at RNC NE.
4. Alarm Reason: Failed to get the configuration of IP/UDP.
On NMS configuration management interface (service IP for
DSP), check whether the relevant office is configured in DSP
service IP address. If no, perform the corresponding configuration according to network planning. Make sure to synchronize
the configuration data at NMS and RNC NE after configuration
modification. Only after synchronization can the configuration
data take effect at RNC NE.
5. Alarm Reason: Failed to get the configuration of L2 table.
Make sure to synchronize the configuration data at NMS and
RNC NE after configuration modification. Only after synchronization can the configuration data take effect at RNC NE.
6. Alarm Reason: Failed to get the configuration of path information.
On NMS configuration management interface (path configuration), check whether the relevant office is configured. If no,
perform the corresponding configuration according to network
planning. Make sure to synchronize the configuration data at
NMS and RNC NE after configuration modification. Only after
synchronization can the configuration data take effect at RNC
NE.
7. Alarm Reason: Failed to get the configuration of pathgroup
information.
On NMS configuration management interface (path group configuration), check whether the relevant office is configured. If
no, perform the corresponding configuration according to network planning. Make sure to synchronize the configuration
data at NMS and RNC NE after configuration modification. Only
after synchronization can the configuration data take effect at
RNC NE.
198083025 Common
Channel setup failed
notification
Notification
Property
Description: Common Channel setup failed notification
Probable Cause
1. Use plane resource initialization fails.

2. Common channel establishment fails on Node B side.
3. Common channel configuration is deleted in NMS.
System Impact
Common Channel is unavailable, which falls into the following

three cases.
35
1. If the SCCPCH carrying FACH is unavailable, UE-initiated CS/PS

services will be down.
2. If the SCCPCH carrying PCH is unavailable, paging function will
be unavailable in the system, leading to failure of UE-initiated
CS/PS services.
3. If the PRACH carrying RACH is unavailable, UE access to the
cell will fail.
Handling
Suggestion
On NMS alarm management interface, view notification Details

where Alarm Reason is given. Locate the specific handling suggestion according to the given reason.
The handling suggestions that correspond to different reasons are
described below.
1. Alarm reason: User plane resource unit initialization fail.
i. On NMS configuration management interface (NE information configuration), select the relevant Node B. Check the
correctness of parameter configuration on path configuration interface. Check if forwarding bandwidth is configured.
ii. On NMS configuration management interface (path group
configuration), view path group configuration. Check the
correctness of parameter configuration.
2. Alarm reason: CCH setup fail at NodeB side.
On NMS configuration management interface (BS ground resource management), view IP parameter configuration in IP
and route management. Ensure that at least one COS is selected.
3. Alarm reason: CCH delete by OMCR.
Automatic processing is performed by the system. Common
channel deletion is initiated by RNC. No handling is necessary.
4. Others.
Common channel will be automatically reestablished by the
system. No handling is necessary.
198083026 MicroCode
subsystem failed to handle
DHCP message from other
network
Notification
Property
Probable Cause
36
Description: MicroCode subsystem failed to handle DHCP message from other network
1. OMCB IP is unconfigured by RNC.

2. The remote IP address of PPP/MLPPP link is unconfigured.
System Impact
The system impacts that correspond to different notification

causes are described below.
1. RNC OMCB IP to Node B has not been configured.
Case 1
If Node B has never fetched the OMCB channel configuration information (including OMCB SERVER IP address,
OMCB gateway IP, and Node B IP address) before notification occurs, OMCB channel of the Node B would be blocked.
Node Bs failure to fetch IP address would lead to its failure
to get other configuration information. Thus the service as
a whole is affected.
Case 2
Node B has fetched the OMCB channel configuration information (including OMCB SERVER IP address, OMCB gateway IP, and Node B IP address) before notification occurs.
If there is no configuration modification, OMCB channel

would not be affected.
If there is configuration modification before notification

occurs, OMCB channel would be affected in such a way
that modified service configuration data fail to take effect on Node B.
2. Peer IP Address of PPP/MLPPP Link has not been configured.

Association link is interrupted. All services on the board are
down.
Handling
Suggestion

where Fail Cause is given. Locate the specific handling suggestion
which corresponds to the listed cause. The handling suggestions
that correspond to different causes are described below.
1. Fail Cause: RNC OMCB IP to Node B has not been configured.
On NMS configuration management interface, check if Manager Node B IP is configured. If no, add the configuration.
2. Fail Cause: Peer IP Address of PPP/MLPPP Link has not been
configured.
On NMS configuration management interface (PPP parameter),
check if remote IP address is configured. If not, add the configuration.
198083028 Logservice is
unavailable
Notification
Property
Probable Cause
Description: Logservice is unavailable
1. Log service is unavailable.

2. Communication between log server and ROMP is faulty.
37
System Impact
Logservice can not receive performance file, and performance file

save on ROMP.
Handling
Suggestion
1. Check whether the log service operation in log server is normal.

If no, restart log service. The checking method is as follows.
Run /StartLogServ under the /home/zte/LogService/bin directory.
2. Check whether the control plane communication between log
server and ROMP is normal The checking method is as follows.
i. Open a terminal dialog box in the LINUX system.
ii. Issue SHELL command of ping 128.0.31.1 at terminal to
see if ping operation is successful. If no, troubleshoot communication fault in control plane.
198083029 Performance file

store failed
Notification
Property
Description: Performance file store failed
Probable Cause
1. Logservice disk space less than 100M.

2. Logservice version is consistent with ROMP version.
3. Logservice is unavailable, and ROMP disk space less than
100M.
4. Board time be adjusted.
5. The unavailable duration of Logservice has exceeded two
hours.
System Impact
Logservice or ROMP can not save performance file, performance

data may be lost.
Handling
Suggestion
Take different action according to Alarm Reason in alarm Details:

1. If Alarm Reason is Logservice disk space less than 100M,
clean up disk of Logservice.
2. If Alarm Reason is Directory on Logservice conflict with which
on ROMP, it mean Logservice version is consistent with ROMP
version, use the correct Logservice version.
3. If Alarm Reason is Logservice is unavailable, and ROMP disk
space less than 100M,
i. Clean up disk of ROMP.
ii. Refer to the corresponding alarm handling suggestion.
Related alarms:
198083028 Logservice is unavailable.
4. if Alarm Reason is Session can not end normally, performance
file can not be saved, it mean Board time be adjusted, no
handling is necessary.
5. If Alarm Reason is Logservice is unavailable, and file number
more than limit on ROMP, it mean The unavailable duration of
Logservice has exceeded two hours, refer to the corresponding
alarm handling suggestion.
38
Related alarms:
198083028 Logservice is unavailable
39
40
Figures
41
42
Tables
43
44
List of Glossary
ASP - Application Server Process
ATM - Asynchronous Transfer Mode
CPU - Central Processing Unit
CS - Circuit Switch
DHCP - Dynamic Host Configuration Protocol
DSP - Digital Signal Processor
FPGA - FieldProgrammable Gate Array
GUIM - GE Universal Interface Module
M3UA - MTP3 User Adaptation Layer
MLPPP - Multilink Point-to-Point Protocol
OMP - Operating & Maintenance Processor
PPP - Point-to-Point Protocol
PS - Packet Scheduling
45

ZXWR RNC (V3.07.310) Radio Network Controller Notification Handling Reference

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZXWR RNC (V3.07.310) Radio Network Controller Notification Handling Reference

Загружено:

Авторское право:

Доступные форматы

ZXWR RNC

Radio Network Controller

Notification Handling Reference

First Edition (ZXWR RNC V3.07.310d+OMMR

Serial Number: sjzl20092956

198005192 Boards Work Mode Unsupported.....................10

198070005 RNC started Iu interface resource reset failure

Introduces the concept of fault management,

Introduces RNC notifications with respect to

Confidential and Proprietary Information of ZTE CORPORATION

ZXWR RNC Notification Handling Reference

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION

ZXWR RNC Notification Handling Reference

Major alarm significantly affects system operation or weakens

Minor alarm affects system operation and network service

Confidential and Proprietary Information of ZTE CORPORATION

Equipment alarm: related with device hardware.

Communication alarm: related with information transmission

Processing alarm: related with software or process fault (ITU-T

Environment alarm: related with the environment where the

QoS alarm: related with degradation of service quality (ITU-T

OMS alarm: related with the network management system.

Confidential and Proprietary Information of ZTE CORPORATION

ZXWR RNC Notification Handling Reference

After recording the fault phenomenon, O&M personnel may

If the fault cannot be removed, contact the local ZTE office as

Confidential and Proprietary Information of ZTE CORPORATION

After recording the fault phenomenon, O&M personnel may

If the fault cannot be removed, contact the local ZTE office as

Confidential and Proprietary Information of ZTE CORPORATION

ZXWR RNC Notification Handling Reference

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION

ZXWR RNC Notification Handling Reference

198070005 RNC started Iu interface resource reset failure notification...........................................................................29

198000576 Trunk Slide

Notification Code: 198000576

Description: Trunk Slide

Since frequency difference might exist between trunk line clock

Momentary fault occurs to trunk data service or signaling channel.

Check the clock synchronization status at both sides. If the status

198026127 Clock reference source lost (Level 3 alarm)

198026128 Clock reference source lost (Level 2 alarm)

198026129 Clock reference source lost (Level 1 alarm)

Confidential and Proprietary Information of ZTE CORPORATION

198001600 One of CPUs on

Notification Code: 198001600

Description: One of CPUs on One of Boards in This Shelf Resets

A certain CPU of a certain board in the shelf abnormally resets.

The service or communication link related to the resetting board

1. Check the NMS operation log to see if manual reset operation

Notification Code: 198003394

Description: Entering Daylight Savings Time

The pre-configured Daylight Saving Time starts for the system.

198003395 Quitting Daylight

Notification Code: 198003395

Description: Quitting Daylight Savings Time

The pre-configured Daylight Saving Time ends for the system.

Confidential and Proprietary Information of ZTE CORPORATION

ZXWR RNC Notification Handling Reference

Notification Code: 198005188