V100R015ENGC00SPH516 Event List

Issue Date 01 2013/07/31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part o products, services and features described in this document may not be within the purchase scope or the usage scope. Unless other specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warrantie guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the preparation of this documen ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warrant kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com

Web site: Email:

ans without prior written consent of Huawei

their respective holders.

etween Huawei and the customer. All or part of the chase scope or the usage scope. Unless otherwise cument are provided "AS IS" without warranties,

been made in the preparation of this document to ns in this document do not constitute a warranty of any

Purpose
This document provides an event list as a reference for northbound event data.

Version
The corresponding product versions of this document are as follows: NE Type: Match Version: NE Version:

Intended Audience
This document is intended for: Network operators Field engineers System engineers Network planners

Structure
EventID EventName Event ID. Event name. Events are classified into four levels: 1 - Critical 2 - Major 3 - Minor 4 - Warning

EventLevel

EventType

Events are classified into the following types: 1 - Power System 2 - Environment System 3 - Signaling System 4 - Trunk System 5 - Hardware System 6 - Software System 7 - Running System 8 - Communication System 9 - QoS 10 - Processing error 11 - OMC 12 - Integrity Violation 13 - Operational Violation 14 - Physical Violation 15 - Security Service or Mechanism Violation 16 - Time Domain Violation Information used for locating an event, such as the subrack number, slot number, subsystem number, and fault causes. Event meaning. Event handling suggestions.

Location Information Event Explain Revise Advice

Impact on the System Impact of the event on the system. System Actions Possible Causes Disuse Statement Actions taken by the system after the event is generated. Causes that may trigger the event. Statement that an event will be phased out in later versions, including how the event will be phased out and how the system will handle the event.

This document provides an event list as a reference for northbound event data.

The corresponding product versions of this document are as follows: BSC6910GSM iManagerM2000_BSC6910GSM_MATCH_ENG_V200R013C00SPH516 V100R015ENGC00SPH516

This document is intended for: Network operators Field engineers System engineers Network planners

Event ID.

Event name.

Events are classified into four levels: 1 - Critical 2 - Major 3 - Minor 4 - Warning

Events are classified into the following types: 1 - Power System 2 - Environment System 3 - Signaling System 4 - Trunk System 5 - Hardware System 6 - Software System 7 - Running System 8 - Communication System 9 - QoS 10 - Processing error 11 - OMC 12 - Integrity Violation 13 - Operational Violation 14 - Physical Violation 15 - Security Service or Mechanism Violation 16 - Time Domain Violation

Information used for locating an event, such as the subrack number, slot number, subsystem number, and fault causes.

Event meaning.

Event handling suggestions.

Impact of the event on the system.

Actions taken by the system after the event is generated.

Causes that may trigger the event.

Statement that an event will be phased out in later versions, including how the event will be phased out and how the system will handle the event.

211974830.xls.ms_office
EventID 10284 10808 11368 11988 22801 22802 22803 22804 22805 22806 22807 22808 22809 22810 22811 22812 22813 22814 22817 22818 22831 22832 22835 22838 22839 22854 22862 22863 22864 22881 22882 22883 22884 22885 22886 22887 22888 22889 22890 22891 22892 22893 22894 22896 22897 22898 22900 EventName EventLevel EventType

Security Level:
Location Information

DATU Board Startup 4 7 DHEU Board Startup 4 7 DPTU Board Startup 4 7 GPS Board Startup 4 7 NE Startup 4 7 NE Shutdown 4 7 OMU Startup 4 7 System Security Alert 2 15 Local User Modifying Other Operator's Password 4 15 Subsystem Measurement Result File Loss 3 9 Alarm Log Database Overflow 3 7 Oversized Log 4 7 License Will Be out of Valid Time 4 7 Base Station TMU Auto Activation 3 7 Automatic Planning Optimization Failure 3 7 Operation of Maximum License Capacity 4 7 Domain User Login Failed 4 15 Local User Login Failed 4 15 Successful OMU Switchover 4 6 NTP Security Authentication Failed 4 15 Board Subsystem Start 3 7 Board Switchover 4 7 Flow Control 4 7 The Status Of Phase-Lock Loop Of System 4 Clock Changed 5 Board Self-Recovery 4 5 Active/Standby Optical Port Switchover 3 Event 4 MSP Switch Event 3 4 Active/Standby Trunk Port Switchover 3 4 Inconsistency Between DHCP Data and4The Configuration 8 BCCH Mutual Aid in a GSM Cell 3 7 Switchback After BCCH Mutual Aid in a 3 GSM Cell 7 Baseband FH Mutual Aid in a GSM Cell3 7 Switchback After Baseband FH Mutual Aid 3 in a GSM Cell 7 GSM Cell BCCH Switched to OL Subcell 3 TRX 7 BTS Power Failure 3 1 Ring Topology Switchover 3 8 Ring Topology Changeback 3 8 Abis Transmission Switchover Started on 4 a Super BTS 8 Abis Transmission Switchover Completed 4 on a Super BTS 8 GSM Cell FH Data Configuration Error 3 7 TRX Path Mutual Aid in a GSM Cell 3 7 Switchback After TRX Path Mutual Aid in 3 a GSM Cell 7 OML Switchover 3 8 GSM MSC Reset 3 7 BSC Reset Notification Message Delivery 3 Failure 8 GSM Cell Transmission Delay Abnormal 3 8 Inconsistency Between Actual BTS Capability 3 and Configuration 7 Data

Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No None. None. Subrack No. = %d, Slot No. = %d IP Address = %d.%d.%d.%d, Description = IP Address = %d.%d.%d.%d, Description = Subrack No. = %d, Logical Slot No. = %d, Number of Cleared Alarm Records = %d Event Cause = %s ESN = %s, Remaining Operation Days = % Site No. = %d, Event Cause = %s, NACK c Site No. = %d, Event Cause = %s, Site Na ESN = %s, Event Cause = %s IP Address = %d.%d.%d.%d, Description = IP Address = %d.%d.%d.%d, Description = Subrack No. = %d, Slot No. = %d, Cause = IP Address = %d.%d.%d.%d, Description = Subrack No. = %d, Slot No. = %s, Subsyst Subrack No. = %d, Slot No. = %d Subrack No. = %d, Slot No. = %d, Subsyst Subrack No. = %d, Slot No. = %d, Last Pha Subrack No. = %d, Slot No. = %s, Board N Subrack No. = %d, Slot No. = %d, Port No. Subrack No. = %d, Int Board Slot No. = %d Subrack No. = %d, Trunk Group Slot No. = BTS ID = %d, Data Mismatch Type = %s, E Cell Index = %d, Cell Name = %s, Cell CG Cell Index = %d, Alarm Cause = %s, Cell N Cell Index = %d, Cell Name = %s, Cell CG Cell Index = %d, Cell Name = %s, Cell CG Cell Index = %d, Cell Name = %s, Cell CG Site Index = %d, Site Name = %s Site Index = %d, Site Name = %s Site Index = %d, Site Name = %s Site Index = %d, Site Name = %s Site Index = %d, Site Name = %s Cell Index = %d, Cell Name = %s, Cell CG Cell Index = %d, Cell Name = %s, Cell CG Cell Index = %d, Cell Name = %s, Cell CG Site Index = %d, Logical Port No. = %d, Sit Index of the DSP = %d, Network ID = %s, Index of the DSP = %d, Network ID = %s, Site Index = %d, Cell Index = %d, Site Nam Site Index = %d, Site Name = %s, Event C

2/18/2014

HUAWEI Confidential

Page9of14

211974830.xls.ms_office
22901 22915 22920 22940 22981 22982 26212 26213 26290 26505 26526 26528 26535 26843 28050 4250 4252 4814 4816 5140 5688 6168 7428 9772 Standard CB Flow Control 4 SCTP Link Destination IP Changeover 4 SCCP Subsystem Congested 3 Board and OMU Patch Status Inconsistency 2 SAU Startup 4 SAU upload failure 3 Board Startup 3 NE Startup 3 Backup Power Saving 4 RF Unit CPRI Interface Switchover 3 RF Unit TX Channel Switched Off 2 RF Unit TX Channel Switched On 3 RF Unit Startup 3 USB Port State Changed 4 Maintenance Link Switchover 3 TRU Board Startup 4 TRX Redundancy Switchover 4 DTMU Board Startup 4 Backup Power Saving 4 CDU Board Startup 4 PMU Board Startup 4 EMU Board Startup 4 IASU Board Startup 4 NFCB Board Startup 4 7 3 3 7 7 7 7 7 1 8 5 5 5 7 4 7 7 7 1 7 7 7 7 7

Security Level:

Flow Control Status = %s, Flow Control Ca Subrack No. = %d, Slot No. = %d, SCTP L Network ID = %s, DSP Code = %d, OSP C Subrack No. = %d, Slot No. = %d Subrack No. = %d, Slot No. = %d Subrack No. = %d, Slot No. = %d, host nam Cabinet No. = %d, Subrack No. = %d, Slot Reset Cause = %s, Site No. = %d, Site Typ Cabinet No. = %d, Subrack No. = %d, Slot Cabinet No. = %d, Subrack No. = %d, Slot Cabinet No. = %d, Subrack No. = %d, Slot Cabinet No. = %d, Subrack No. = %d, Slot Cabinet No. = %d, Subrack No. = %d, Slot Cabinet No. = %d, Subrack No. = %d, Slot Switchover Direction = %s, Site No. = %d, Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No Site No. = %d, Board Type = %s, Board No

2/18/2014

HUAWEI Confidential

Page10of14

211974830.xls.ms_office
Event Explain Revise Advice Impact on the System

Security Level:

None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None. This event is generated when theRemote active OMU Handling: startsstep1 up. This event as a notification andstarts does up. not need to be hand The useris isreported notified that the active OMU This event is generated when theRemote active OMU Handling: is shut step1 down. This event as a notification andis does need to be hand The useris isreported notified that the active OMU shutnot down. This event is generated when theRemote OMU software Handling: starts step1 up.This event as a notification and does not need to be hand The useris isreported notified that the OMU software starts up. This event is generated when theRemote local user Handling: fails to log step1 in to This the event system is reported for three successive a notification and within does two not hours. need toin be The administrator is as notified thattimes the local user fails to log tohand the This event is generated when theRemote local user Handling: modifies step1 otherThis operator's event is password. reported a notification and does need to be hand The administrator is as notified that the local user not modifies other oper This event is generated when theRemote measurement Handling: result step1 file Check reported whether by the the host board subsystem isis normal is lost. before the measurement result is The measurement result incomplete. This event is generated when theRemote number Handling: of alarm logs step1 exceeds This event the maximum is reported as a notification (150,000 and by default). does not need to be hand The system deletescapacity some alarms from the database. This event is generated when theRemote size of the Handling: log exceeds step1 80% Check of the maximum information size. and locate the path the oversiz If the log location is not backed up and the size of the log where exceeds the max This event is generated when theRemote license file Handling: is going step1 to be Apply out of for valid a valid time. license The event file, and is generated then download every day thewhen license 30 days file before onto tt The system switches to the trial operation period the license This event is generated when theRemote BTS activates Handling: the step1 configured Check TMU the "Event software. Cause" activation and the "NACK is triggered Cause" when in the the Event BSC inform detect If "Event Cause" is The "TMU activation succeeded", you can infer that This event is generated when theRemote base station Handling: throwstep1 malfunctions The "Event during Cause" the automatic is "Requested planning frequencies optimization are not process. found on theca M The base station that is subject to automatic frequency planning When a system runs at the maximum Remote license Handling: capacity, step1 it indicates Run therunning [MML]LST that all at resource LICENSECTRL[/MML] items are set to their command maximum to check values.The the inf After the maximum license capacity for seven days, the This event is generated when theRemote domain Handling: user fails to step1 log in This to the event OMU. is reported a notification and does notfails need be hand The administrator is as notified that the domain user toto log in to th This event is generated when theRemote local user Handling: fails to log step1 in to This the event system. is reported a notification and does need toin be The administrator is as notified that the local user not fails to log tohand the This event is reported when the original Remote standby Handling: OMU step1 is switched Check the over value to the of the active parameter one. "Cause".step1.1 If active the value Man 1.Users are informed that switchover between the andis stand The OMU sends synchronization Remote requestsHandling: to the NTP step1 server Run periodically the [MML]LST (the interval SNTPCLTPARA[/MML] can be by command running to query [MML]LST the au The synchronization between thequeried OMU and the NTPthe server fails. In This event is generated when a subsystem Remote Handling: of a board None. starts Onsite up. The Handling: subsystem of the board automatically the startup co A subsystem is None. unavailable before it generatesstarts this event. This event is generated when a switchover Remote Handling: is performed step1 between This event the is active reported and as standby a notification boards. and does not need to be hand This event is generated after a switchover between the active and This event is generated when theRemote flow control Handling: statusstep1 of theThis subsystem event isis reported changed. as athe notification and doeswill notbe need to be hand The paging message or access message discarded in s This event is reported when the status Remote of phase-lock Handling: step1 loop is This changed. event is reported as a notification and does not need to be hand None. The event is reported when a board Remote healsHandling: itself through step1 a auto-triggered This event is reported reset. as aifnotification and not need be hand In active/standby mode, the fault on thedoes active board isto automatic This event is generated when an Remote active optical Handling: port is step1 switched This event over to isa reported standbyas optical a notification port. and does not need to be hand None This event is generated when theRemote MSP protocol Handling: changes step1from Check one the switchover "Switchover request Request" to another parameter switchover that the request. event reports.ste There are None This event is generated when a trunk Remote group Handling: work in step1 active/standby This event mode, is reported and anas active a notification sub-port and is switched does not over need to to the be standb hand None This event alarm is generated when Remote the BSC Handling: finds that step1 theCheck data the consistency inESN the DHCP between packet ESN1 received Configured from the orBTS ESN2 is inconsist Configur The carried planned is erroneous. This event is generated when theRemote BCCH TRX Handling: is faulty step1 andOn aThe normal thecell LMT, TRX run inthe the[MML]DSP cell is selected CHNSTAT[/MML] as the are new BCCH command TRX. to chec is re-initialized, and the services temporarily disrupted This event is generated when theRemote switchback Handling: after BCCH step1 mutual This event aid is occurs is re-initialized, reported under asthe a notification following conditions: and not The need BSCto detects be th The cell and the BCCH is does switched back to thehand orig This event is generated when theRemote TRX joining Handling: in baseband step1 On Frequency theservices LMT,Hopping choose (FH) isand faulty. check whether the [ALM]22881[/ALM The in the Event, cell are interrupted for a short period. After TRX This event is generated when theRemote faulty TRXs Handling: joining step1 in baseband Check the FH event.step1.1 are are restored in On a the cell. LMT, choose Event, and the check whet The services temporarily disrupted in the cell. After switchb This event is generated when theRemote BCCH TRX Handling: is faulty step1 andOn the the BCCH LMT, isrun switched the [MML]DSP a TRX CHNSTAT[/MML] inreduced. the OverLaid (OL) command subcell.to chec The coverage area ofto the cell is This event is generated when there Remote is no power Handling: supply None. to the Onsite BTS. Handling: Power on the BTS again. The services of step1 the BTS are disrupted. This event is generated when theRemote BTS ring Handling: topologystep1 is switched Check over. whether the event is caused by a the manual ring and topology s If Huawei I BTS ring topology is used, BTS BTS is reset, all the This event is generated when theRemote BTS ring Handling: topologystep1 is changed Check back. whether the event is caused by a the manual ring and topology c If Huawei I BTS ring topology is used, BTS BTS is reset, all the This event is generated when theRemote BSC to which Handling: a logical step1satellite This event site is belongs reported receives as a notification an OML setup and does request not from needato super be hand BTS None This event is generated when theRemote cell out of Handling: service step1 alarm This for aevent cell ofis the reported logical as satellite a notification cell is recovered. and does not need to be hand None This event is generated when theRemote FH mode Handling: of a cell step1 is set On toThe hybrid theinitialization LMT, FH but run actually the GCELLHOPTP[/MML] does not support hybrid command FH. to m of [MML]SET the the cell cell fails. This event is generated when theRemote physicalHandling: path that step1 is initially On bound theservices LMT, to the choose BCCH TRX > is Browse faulty and Event. theCheck BCCHwhether TRX is switched any even The in the Event cell are temporarily disrupted. This event is generated when theRemote BCCH TRX Handling: is switched step1 back Check to whether the path the that event is initially is caused bound to troubleshooting the BCCH after the path pe The BCCH TRX switches back to by the initial path, TRX andoperations the services This event is generated when a switchover Remote Handling: betweenstep1 the active Check and whether standby the OMLs event isis performed. caused by a manual active/standby OML The BTS re-establishes the OML.After the OML is re-established, i This event is generated when theRemote BSC receives Handling: a RESET step1 Contact message from MSC the maintenance MSC. engineers to identify the cause of the All the the reset type related ongoing calls are disrupted. This event is generated when theRemote number Handling: of reset message step1 Check retransmissions whether any sent E1/T1 by and the BSC IP-related over the alarm A interface is generated. exceeds If yes, n. T g The call-related resources may not be timely released on the MSC This event alarm is generated when Remote a cellHandling: that supports step1 the Check PS service the value detects of the that event the parameter transmission "Event delay Cause" between displayed the BTS in an t When the cause of this event is "Delay in normal cell exceeds Tran This event is generated when theRemote BTS software Handling: version step1 orCheck BTS whether does BTS not needs support tomay the support current configuration. function listedis in"1588v the de Thehardware BTS timethe synchronization fail ifthe the event cause

2/18/2014

HUAWEI Confidential

Page11of14

211974830.xls.ms_office

Security Level:

This event is generated when theRemote BSC starts Handling: or stops step1 standard After flow cellstandard broadcast control stops, (CB) query flow control. deleted The messages BSC on the the CBC CPU server. usa When CB flow control is started, the detects BSC cannot receive This alarm is generated when theRemote destination Handling: IP address step1of This the event SCTP is link reported is changed as a function notification over. may and not need be hand The SCTP multi-homing be does unavailable forto use. This event is generated when theRemote BSC receives Handling: the step1 SCCPThis subsystem event iscongestion reported as message a notification from and the peer does NE. not need to be hand A proportion of new services are rejected based on the congestion This event is generated when theRemote actual patch Handling: status step1 of a board Run the is inconsistent [MML]CMP with that stored in command the OMU to after check the whether board isthe re The board patch isBRDVER[/MML] not restored to the status specified by the OMU This event is generated when theRemote SAU software Handling: starts step1 up. This event as a notification and does not need to be hand The useris isreported notified that the SAU software starts up. This event alarm is generated when Remote the SAU Handling: fails tostep1 upload Log the inresult to the data server, to be the and server. then run localhost" command, check The data cannot uploaded tothe the"ftp server and the upper layer can Null Remote Handling: stepNULL NULL Onsite Handling: None. NULL Null Remote Handling: stepNULL NULL Onsite Handling: None. NULL Null Remote Handling: stepNULL NULL Onsite Handling: None. NULL Null Remote Handling: stepNULL NULL Onsite Handling: None. NULL Null Remote Handling: stepNULL NULL Onsite Handling: None. NULL Null Remote Handling: stepNULL NULL Onsite Handling: None. NULL Null Remote Handling: stepNULL NULL Onsite Handling: None. NULL Null Remote Handling: stepNULL NULL Onsite Handling: None. NULL Null Remote Handling: stepNULL NULL Onsite Handling: None. NULL None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None. None Remote Handling: None. Onsite Handling: None.

2/18/2014

HUAWEI Confidential

Page12of14

211974830.xls.ms_office
System Actions Possible Causes Disuse Statement

Security Level:

N/A N/A N/A N/A N/A None The active OMU starts up. N/A None The active OMU is shut down. N/A up. None The OMU software starts N/A None The user name or password is entered incorrectly. N/A None The local user modifies other operator's password. N/A None The version of the OMU does not match that of the host board.The module on the OMU works ab N/A The OMU automatically deletes The cleared number alarms of alarm and logs event exceeds alarmsthe to reduce maximum the capacity. number of alarm logs below the maximum capa N/A When the size of the host logThe exceeds size of the the maximum log exceeds size, 80% the system of the maximum automatically size.removes the earlier information of the log a N/A None Less than 30 days are left before the license file expires. N/A None Failed to query the BTS running version.TMU activation failed. TMU activation succeeded.Failed t N/A None The M2000 has no information about the frequencies that the base station has requested. The M2 N/A at the maximum license capacity. None The system currently runs N/A None The user name or password is entered incorrectly. N/A None The user name or password is entered incorrectly.The local user has been locked when he or she N/A Automatic OMU switchover. The switchover is caused by the missing of None Manual OMU switchover. N/A None The NTP server authentication information configured on the OMU is inconsistent with the actual N None The board is poweredN/A on. The BSC6910 system resets. The subrack resets. The board resets. Th N/A The subsystem of the active board is faulty. A manual switchover is per None The active board is faulty. N/A Some minor tasks or functions CPU areoccupancy temporarily of stopped the board due subsystem to high system is tooload. high.These Packet tasks occupancy will be gradually of the board resumed subsystem after is th None. The clock phase-lock N/A loop is in current source tracing process. During this process, the status of c N/A RSTREASON[/MML] command to query the reason for a reset cause None You can run the [MML]DSP N/A None The POUc is configured to work in backup mode.After the MSP protocol module sends the optical N/A If the "Switchover Request" is The "forced original switchover", active port "SF", is faulty. or "manual The user switchover", initiates the theswitchover services are through switched the over OMC. to The [FILE]link190 peer en None If a trunk group worksN/A in active/standby mode and "Aggregation Mode" is set to MANUAL_AGGRE N/A None The ESN configured on the BSC for the BTS is inconsistent with the ESN carried in the DHCP pac N/A detects When this event is generated, The thehardware system automatically of the BCCH TRX is the faulty.The TRXs available BCCH TRX for use is manually in the cell blocked.The and selects BCCH one as isthe manu ne N/A due When the original BCCH TRX Aresumes forced switchback normal operation, occurs the to BCCH data is configuration.The in the unblocked original administrative BCCH TRX state, resumes and the normal switchbac op N/A When this event is generated, The theBCCH system TRX initializes is faulty, theand cell. the BCCH mutual aid occurs.The TRX joining in baseband FH is fau N/A When this event is generated, The thefaults system oninitializes the faulty the TRX cell. joining in frequency hopping are rectified.The faults on the BCCH TR N/A TRX The system automatically searches The hardware for the TRXs of the available BCCH for is use faulty.The in the cell, BCCH switches is manually the BCCH blocked.The to a TRX BCCH in the OL TRX subcell, is manu an N/A None There is no power supply to the BTS. The BTS is switched over to the An upper-level reverse direction. BTS inN/A the current ring direction is deactivated or reset.The link on the forward ring N/A When the event is generated, An the upper-level BTS is changed BTS inback the current to the forward ring direction direction. is deactivated or reset.The link on the reverse ring N/A None The Abis transmission mode of the super BTS switches from terrestrial transmission to satellite tra N/A None The Abis transmission mode of the super BTS successfully switches to satellite transmission. N/A The initialization of the cell ceases The FH when mode the of event a cell isis generated. set to hybrid FH but actually the BTS does not support hybrid FH. N/A The BTS binds a normal path The to the path BCCH that is TRX. initially bound to the BCCH TRX is faulty.The hardware of the BCCH TRX is faulty N/A TRX The BTS binds the path initially A forced configured switchback for the occurs BCCH due to back data to configuration.The the BCCH TRX. path that is initially bound to the BCCH N/A The event is generated whenThe a switchover OML in the between BTS that the supports active and thestandby active/standby OMLs is OML performed. switchover Theis active faulty.A OML manual is switched active/sta to N/A The BSC releases all the reset The type event related is caused transmission by MSC resources fault.The occupied event is caused by ongoing by the calls. manual reset of the MSC. N/A None The SS7 signaling link is intermittent. N/A None Delay in normal cell exceeds Transmission Delay Threshold for GSM Cells.Delay in satellite cell is N/A The system does not send the The event-related BTS is configured configuration to support data1588v2 to the BTS. time synchronization, which is actually not supported by

2/18/2014

HUAWEI Confidential

Page13of14

211974830.xls.ms_office

Security Level:

N/A is started.Standard After standard CB flow control Standard is started, CB the flow BSC control discards all newly received CB messages flow control over is stopped. the interface between the BSC an N/A The system switches the SCTP The totransport other available network destination is intermittently IP addresses. disrupted. N/A The BSC will automatically enable The BSC the flow receives control the to SCCP reduce subsystem traffic flow congestion to this congested message SCCP fromsubsystem. the peer NE. N/A board reset is activated and that after board reset is deactivated, you can None If the patch status before N/Aup. None The SAU software starts N/A The current task continuously The attempts IP address to connect and port to the number server. of If the the server connection are configured cannot be incorrectly.The recovered before network 24:00 connection on that day o N/A NULL Null N/A NULL Null N/A NULL Null N/A NULL Null N/A NULL Null N/A NULL Null N/A NULL Null N/A NULL Null N/A NULL Null N/A N/A N/A N/A N/A N/A N/A N/A N/A

2/18/2014

HUAWEI Confidential

Page14of14