MPR Configuration File Management

Alcatel-Lucent 9353
Wireless Management System | V7.1

Node B Alarms Reference Guide for 9313/9314 Node B
Alcatel-Lucent - Proprietary
Use pursuant to applicable agreements
NN-20500-018P3
Issue 07.04/EN
June 2010
Alcatel-Lucent 9353
Wireless Management System
Document number: NN-20500-018P3

Document issue: 07.04/EN
Document status: Standard
Product release: V7.1
Date: June 2010
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other
trademarks are the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for
inaccuracies contained herein.
Copyright © 2004-2010 Alcatel-Lucent, All Rights Reserved
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made
available to, or copied or used by anyone outside Alcatel-Lucent without its written authorization.
Not to be used or disclosed except in accordance with applicable agreements.
Publication history 3
PUBLICATION HISTORY
SYSTEM RELEASE: V7.1
June 2010
Issue 07.05/EN Standard
Editorial update
May 2010
Up-Issue for DR5
November 2010
Issue 07.03/EN Preliminary
Update for DR4
November 2009
Update after review
September 2009
Issue 07.01/EN Draft
Update for V7.1 release
SYSTEM RELEASE: OAM07.0
June 2009
Update after internal review
April 2009
Update for UA07.0 / OAM07.0 release
SYSTEM RELEASE: OAM06.0
Copyright © 2004-2010 Alcatel-Lucent Node B Alarms Reference Guide for 9313/9314 Node B
April 2009
Update for DR5
March 2009
January 2009
November 2008
Minor update
October 2008
Update for MNCL1
September 2008
Additional updates per CR DCTPD00066045 completion
August 2008
Update for DR4
Resolution CR DCTPD00066045 Review comments to
NN-20500-018P3_Alcatel-Lucent_9300_WCDMA_
Product_Family_-_Node_B_Alarms_Reference_Guide_for_OneBTS_05.pdf
July 2008
NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

June 2008
Update for DR4
Table of contents 6
1 About this publication................................................................................................................................................. 10

2 Roadmap to Fault Management documentation....................................................................................................... 12
3 New in this release....................................................................................................................................................... 14
4 How to use this publication.........................................................................................................................................15
5 9313 Micro and 9314 Pico alarm descriptions...........................................................................................................20
5.1 ALCAP alarms.......................................................................................................................................................... 21
5.1.1 MicroBTS_1040_00050 - F5 AIS ERROR......................................................................................................... 22
5.1.2 MicroBTS_1041_00050 - F5 RDI ERROR......................................................................................................... 23
5.1.3 MicroBTS_1046_00050 - ALCAP PORT FAULT............................................................................................... 24
5.2 AntennaAccess alarms............................................................................................................................................. 25
5.2.1 MicroBTS_1029_00130 - VSWR FAULT........................................................................................................... 26
5.2.2 MicroBTS_1030_00130 - RX DIVERSITY BRANCH A FAULT......................................................................... 27
5.2.3 MicroBTS_1031_00130 - RX DIVERSITY BRANCH B FAULT......................................................................... 28
5.3 CCP alarms.............................................................................................................................................................. 29
5.3.1 MicroBTS_1033_00060 - COMMUNICATION CONTROL PORT FAULT......................................................... 30
5.3.4 MicroBTS_1042_00060 - UPLINK TRANSMISSION CONGESTION................................................................ 33
5.4 CoolingSystem alarms..............................................................................................................................................34
5.4.1 MicroBTS_1025_00150 - COOLING FAN FAULT............................................................................................. 35
5.5 ExternalAlarmPort alarms.........................................................................................................................................36
5.5.1 MicroBTS_1001_00140 - EXTERNAL EQUIPMENT ALARM............................................................................37
5.6 IMAGroup alarms......................................................................................................................................................38
5.6.1 MicroBTS_1021_00110 - IMA GROUP FAULT................................................................................................. 39
5.7 ItfB alarms.................................................................................................................................................................40
5.7.1 MicroBTS_1034_00020 - MANAGEMENT CHANNEL FAULT.......................................................................... 41
5.8 MicroBTS alarms...................................................................................................................................................... 45
5.8.1 MicroBTS_1005_00000 - NTP SERVER UNAVAILABLE.................................................................................. 46
5.8.2 MicroBTS_1006_00000 - INACCURATE RF REFERENCE.............................................................................. 47
5.8.3 MicroBTS_1007_00000 - LMT CONNECTED................................................................................................... 48
5.8.4 MicroBTS_1015_00000 - OFFICE DATA ERROR.............................................................................................49
5.8.5 MicroBTS_1022_00000 - TIMING REFERENCE LOST IN BTS........................................................................50

Table of contents 7
5.8.6 MicroBTS_1039_00000 - LOCKED BY SITE SWITCH......................................................................................51

5.8.7 MicroBTS_1043_00000 - FILE STORAGE FULL.............................................................................................. 52
5.8.8 MicroBTS_1044_00000 - USER PLANE FRAME PROTOCOL PROBLEM...................................................... 53
5.9 NodeBCP alarms...................................................................................................................................................... 54
5.9.1 MicroBTS_1032_00030 - NODE B CONTROL PORT FAULT...........................................................................55
5.10 PhysicalLink alarms................................................................................................................................................ 59
5.10.1 MicroBTS_1017_00090 - PHYSICAL LINK FAULT......................................................................................... 60
5.10.2 MicroBTS_1019_00090 - IMA LINK FAULT.....................................................................................................61
5.11 PowerSystem alarms..............................................................................................................................................62
5.11.1 MicroBTS_1026_00160 - INCOMING POWER LOST..................................................................................... 63
5.11.2 MicroBTS_1027_00160 - BATTERY MALFUNCTION..................................................................................... 64
5.11.3 MicroBTS_1028_00160 - BATTERY DISCHARGED....................................................................................... 65
5.11.4 MicroBTS_1045_00160 - INCOMING POWER LEVEL OUT OF RANGE....................................................... 66
5.12 SectorEquipment alarms........................................................................................................................................ 67
5.12.1 MicroBTS_1008_00010 - SECTOR UNIT TEMPERATURE TOO LOW.......................................................... 68
5.12.2 MicroBTS_1009_00010 - SECTOR UNIT TEMPERATURE TOO HIGH......................................................... 69
5.12.3 MicroBTS_1011_00010 - SECTOR HARDWARE FAULT............................................................................... 70
5.12.4 MicroBTS_1036_00010 - LICENSE ERROR................................................................................................... 71
5.12.5 MicroBTS_1037_00010 - LICENSE EXPIRED................................................................................................ 72
5.12.6 MicroBTS_1038_00010 - CONTROL PROCESSOR OVERLOAD.................................................................. 73
5.13 UserDataPort alarms.............................................................................................................................................. 74
5.13.1 MicroBTS_1035_00070 - USER DATA PORT FAULT.................................................................................... 75
5.13.2 MicroBTS_1040_00070 - F5 AIS ERROR....................................................................................................... 76
5.13.3 MicroBTS_1041_00070 - F5 RDI ERROR....................................................................................................... 77
5.13.4 MicroBTS_1042_00070 - UPLINK TRANSMISSION CONGESTION.............................................................. 78
5.14 OAM alarms............................................................................................................................................................79
5.14.1 OAM_0096_00058 - Unexpected software version..........................................................................................80
5.14.2 OAM_0097_00058 - Loss of supervision......................................................................................................... 81
5.14.3 OAM_0098_00058 - BTS enters in SAFE mode..............................................................................................82
5.14.4 OAM_0099_00058 - BTS RESTART............................................................................................................... 83
5.14.5 OAM_0100_00058 - Supervision inhibited by operator....................................................................................84
List of figures 8
Figure 1 - Roadmap to Fault Mangement documentation.................................................................................. ......... 12

Figure 2 - Alarm Manager window........................................................................................................ ............. ......... 16

List of examples 9
Example 1 - 9313 Micro and 9314 Pico Node Bs designation.............................................................. ............. ......... 19
10
1 About this publication

This publication describes the alarm reference information applicable to the UMTS BTS 1120 (Micro)
and BTS 1010 (Pico).
Note:Throughout this document, the same signification can be applied to:
• 9313 Micro Node B for UMTS BTS 1120
• 9314 Pico Node B for UMTS BTS 1010
For more clarification see 9313 Micro and 9314 Pico Node Bs designation.
Applicability
This publication applies Alcatel-Lucent W-CDMA V7.1 system release.
Audience
The publication is intended for operation and maintenance personnel and for those who want to know
the principles of the UMTS BTS 1120 and BTS 1010 alarm references.
Prerequisites
It is recommended that readers also become familiar with the following documents:
• Alcatel-Lucent 9313 Micro Node B Technical Description (NN-20500-053)
• Alcatel-Lucent 9314 Pico Node B Technical Description (NN-20500-094)
• Alcatel-Lucent 9300 W-CDMA Product Family - Fault Management (NN-20500-156)
• Alcatel-Lucent 9353 Management System - User Guide (NN-20500-032)
• UTRAN Supervision Guidelines (UMT/SYS/INF/007308)
Related documents
Alcatel-Lucent 9300 W-CDMA Product Family - Node B Alarms Reference Guide for Macro Node B
and Compact Node B (NN-20500-018)
9313 Micro and 9314 Pico Node Bs maintenance guides:
• Alcatel-Lucent 9313 Micro Node B Hardware Preventive Maintenance (NN-20500-054)
• Alcatel-Lucent 9313 Micro Node B Hardware Corrective Maintenance (NN-20500-055)
• Alcatel-Lucent 9313 Micro Node B and 9314 Pico Node B Operation and Maintenance Manual
(NN-20500-058)
• Alcatel-Lucent 9313 Micro Node B and 9314 Pico Node B Local Maintenance Tool Manual
(NN-20500-057)
How this publication is organized

11
This document describes the 9313 Micro and 9314 Pico alarms raised by the Node B equipment,
then the alarms raised by the OAM.
The corrective procedures applicable to the Node Bs refer to the Node B hardware maintenance
guides.
Vocabulary conventions
The glossary is presented in Alcatel-Lucent 9300 W-CDMA Product Family - Terminology
(NN-20500-002).
Safety regulations
To guarantee the safety of personnel and equipment, the following aspects must be taken into
account:
• general personnel safety instructions
• equipment safety instructions.
12
2 Roadmap to Fault Management documentation

The figure next page shows where the current document stands within the W-CDMA Customer
Documentation.
Note: For a global view of the W-CDMA Customer Documentation, see Roadmap chapter in:
• Alcatel-Lucent 9300 W-CDMA Product Family - Document Collection Overview (NN-20500-050)
• Alcatel-Lucent 9300 W-CDMA Product Family - Access Network Management Overview
(NN-20500-031)
Figure 1 Roadmap to Fault Mangement documentation

13
14
3 New in this release

The following details what is new in Node B Alarms Reference Guide for release OAM07.1.
Features
N/A.
Other changes
For the list of removed, new and modified Node B alarms in this release, see Alcatel-Lucent 9300
W-CDMA Product Family - UA07.1 / OAM07.1 Release Operational Impacts: CM, FM and PM Delta
(NN-20500-052).

15
4 How to use this publication

This part describes how to use this publication.
Introduction
This publication contains the alarm descriptions and refers to corrective maintenance procedures
applicable to the Node B. See the list of Node B hardware maintenance guides in the Related
documents section.
This document does not list alarms generated by LMT, for description of these alarms, see
Alcatel-Lucent Micro Node B and 9314 Pico Node B Local Maintenance Tool Manual
(NN-20500-057).
The general principles and messages required for Node B maintenance are described in 9353
Management System - User Guide (NN-20500-032).
Network maintenance is based on graphical supervision of the network. It is also based on the
identification and replacement of faulty items of equipment, using the alarms.
Description of a Node B alarm sheet

To display a Node B alarm help sheet, from the Alarm Manager window, right-click the alarm row and
select the Selected Item Help command.
For the other Alarm manager options, see Alcatel-Lucent 9353 Management System - User Guide
(NN-20500-032).
16
Figure 2 Alarm Manager window
An alarm sheet contains a description providing the short explanation of the alarm and a table
detailing the following information:
Alarm name: the specific problem of the alarm

Alarm Code The alarm code, based on the
faultCode
field as displayed in the Alarm Record Viewer.
See Alarm Code format.
Node B Type The impacted Node B types (short form names).
See 9313 Micro and 9314 Pico Node Bs desig-
nation.
Object Class Object Class as it appears in the Alarm Manager
window
Equipment Type Equipment Type of the alarms.
Alarm Type Alarm type which depends on the causes of the
alarm. See Alarm Type - Probable Cause.
Probable Cause Probable cause per alarm type. See Alarm Type
- Probable Cause.
Severity Urgency of the maintenance action. See Sever-
ity.
Impact on Node B operation Description of how the service is affected.
Reason Possible origins of the alarm.
Remedial Action List of recommended responses which corres-

17
Alarm name: the specific problem of the alarm

pond to corrective maintenance procedures
(depend on the release).
Alarm Code format

The alarm code uses the faultCode field as seen in the alarm record details. It specifies the alarm
type according to the following generic pattern:
[Equipment type]_[Alarm code on 4 digits (0-9)]_[MO Object Id on 5 digits (0-9)]
where
• "Equipment type" is MicroBTS or OAM
• "Alarm code" is the alarm code of the equipment type
• "MO Object Id" is the Managed Object Id of the alarmed component.
Alarm Type - Probable Cause

Alarm Type Probable Cause
communications:
• communicationsProtocolError
an alarm of this type is mainly associated with
• communicationsSubsystemFailure
the procedures and/or processes required to
convey information from one point to another. • configurationOrCustomizationError
• degradedSignal
• framingError
• lossOfSignal
• remoteNodeTransmissionError
environment:
• enclosureDoorOpen
an alarm of this type is principally associated
• heatingOrVentilationOrCoolingSystem-
with a condition relating to an enclosure in Problem
which the equipment resides.
• temperatureUnacceptable
equipment:
• adapterError
• equipmentMalfunction
an equipment fault.
• fileError
• inputDeviceError
• powerProblem
• receiveFailure
• timingProblem
• transmitterFailure
18
Alarm Type Probable Cause

processing error:
• communicationsProtocolError
• configurationOrCustomizationError
software or processing fault.
• corruptData
• outOfMemory
• softwareProgramError
quality of service:
• corruptData
• queueSizeExceeded
degradation in the quality of a service.
• Receive Problem
• sfwrEnvironmentProblem
• thresholdCrossed
• underlyingResourceUnavailable
• versionMismatch
Operator
• versionMismatch
Severity
The Node B uses the following perceived severity:
• CRITICAL: indicates that a service affecting condition has occurred and an immediate corrective
action is required.
• MAJOR: indicates that a service affecting condition has developed and an urgent corrective
action is required.
• minor: indicates the existence of a non-service affecting fault condition and that corrective action
will have to be taken in order to prevent a more serious fault.
• warning: indicates the detection of a potential or impending service-affecting fault, before any
significant effects have been felt.

19
9313 Micro and 9314 Pico Node Bs designation

Old Node B designation New Node B designation
Long form Short form
BTS 1120 (Micro) Alcatel-Lucent 9313 Micro Node B 9313 Micro
BTS 1010 (Pico) Alcatel-Lucent 9314 Pico Node B 9314 Pico
20
5 9313 Micro and 9314 Pico alarm descriptions

The Andrew alarms are described in the following order:
• ALCAP alarms
• AntennaAccess alarms
• CCP alarms
• CoolingSystem alarms
• ExternalAlarmPort alarms
• IMAGroup alarms
• ItfB alarms
• MicroBTS alarms
• NodeBCP alarms
• PhysicalLink alarms
• PowerSystem alarms
• SectorEquipment alarms
• UserDataPort alarms
• OAM alarms

21
5.1 ALCAP alarms

The following alarms are generated by the ALCAP.
• MicroBTS_1040_00050 - F5 AIS ERROR
• MicroBTS_1041_00050 - F5 RDI ERROR
• MicroBTS_1046_00050 - ALCAP PORT FAULT
22
5.1.1 MicroBTS_1040_00050 - F5 AIS ERROR

A neighboring node has signaled to the BTS an upstream connectivity failure.
F5 AIS ERROR
Alarm Code MicroBTS_1040_00050
Object Class MicroBTS/ALCAP
Equipment Type ALCAP
Event Type communicationsAlarm
Probable Cause remoteNodeTransmissionError
Severity
• MAJOR
Impact Possible capacity or performance degradation.
Reason A neighboring node has signaled to the BTS an upstream connectivity
failure.
Remedial Action Check the transmission links. Check the configuration of the BTS
1120/BTS 1010, RNC, and transmission network with respect to the af-
fected PVC. When the fault is repaired the alarm will be ceased auto-
matically by BTS 1120/BTS 1010.

23
5.1.2 MicroBTS_1041_00050 - F5 RDI ERROR

F5 RDI ERROR
Severity
• MAJOR
failure.
1120/BTS 1010, RNC and transmission network with respect to the af-
24
5.1.3 MicroBTS_1046_00050 - ALCAP PORT FAULT

ALCAP Port is down.
ALCAP PORT FAULT

Severity
• MAJOR
Impact All traffic services will be shut down.
Reason ALCAP Port is down.
Remedial Action Check that the BTS 1120/BTS 1010 configuration, the RNC configura-
tion and the transmission network configurations are consistent with
respect to the PVC used for ALCAP. Check that the RNC is running
properly. Check that the transmission lines are working. The BTS 1120
/ BTS 1010 will restart periodically if the ALCAP remains faulty.

25
5.2 AntennaAccess alarms

The following alarms are generated by the AntennaAccess.
• MicroBTS_1029_00130 - VSWR FAULT
• MicroBTS_1030_00130 - RX DIVERSITY BRANCH A FAULT
• MicroBTS_1031_00130 - RX DIVERSITY BRANCH B FAULT
26
5.2.1 MicroBTS_1029_00130 - VSWR FAULT

Reflected power too high.
VSWR FAULT
Object Class MicroBTS/SectorEquipment/AntennaAccess
Equipment Type AntennaAccess
Event Type equipmentAlarm
Probable Cause equipmentMalfunction
Severity
• MAJOR
• warning
Impact Possible capacity and/or performance degradation.
Reason Reflected power too high.
Remedial Action The BTS 1120 (Micro) will automatically cease of alarm if the VSWR
fault indication disappears. The operators can restart the BTS 1120
(Micro) to check if the alarm persists. If the alarm persists the antenna
may be defect, or there may be a loose (RF) connection between an-
tenna and the sector equipment unit. The antenna cables should also
be inspected for possible damages or problems.

27
5.2.2 MicroBTS_1030_00130 - RX DIVERSITY BRANCH A FAULT

RX Diversity detected on antenna A.
RX DIVERSITY BRANCH A FAULT

Severity
• minor
Impact Possible capacity and/or performance degradation.
Reason RX Diversity detected on antenna A.
Remedial Action The BTS 1120/BTS 1010 clears the alarm automatically if it detects the
fault has disappeared. The operator can restart the BTS 1120/BTS
1010 to check if the alarm persists. If the alarm persists the antenna
may be defect, or there may be a loose (RF) connection between an-
tenna and the sector equipment unit. The antenna cables should also
be inspected for possible damages or problems.
28
5.2.3 MicroBTS_1031_00130 - RX DIVERSITY BRANCH B FAULT

RX Diversity detected on antenna B.
RX DIVERSITY BRANCH B FAULT

Severity
• minor
Impact N/A
Reason RX Diversity detected on antenna B.
Remedial Action Check the antenna B and its connection.

29
5.3 CCP alarms

The following alarms are generated by the CCP.
• MicroBTS_1033_00060 - COMMUNICATION CONTROL PORT FAULT
• MicroBTS_1042_00060 - UPLINK TRANSMISSION CONGESTION
30
5.3.1 MicroBTS_1033_00060 - COMMUNICATION CONTROL PORT

FAULT
Communication Control Port is down.
COMMUNICATION CONTROL PORT FAULT

Object Class MicroBTS/CCP
Equipment Type CCP
Severity
• MAJOR
Reason Communication Control Port is down.
respect to the PVC used for CCP. Check that the RNC is running prop-
erly. Check that the transmission lines are working. The BTS 1120 /
BTS 1010 will restart periodically if the CCP remains faulty.

31

F5 AIS ERROR
Equipment Type CCP
Severity
• MAJOR
failure.
32

F5 RDI ERROR
Equipment Type CCP
Severity
• MAJOR
failure.

33
5.3.4 MicroBTS_1042_00060 - UPLINK TRANSMISSION CONGESTION

The transmission supervision has detected an uplink congestion.
UPLINK TRANSMISSION CONGESTION

Equipment Type CCP
Probable Cause queueSizeExceeded
Severity
• minor
Impact Degraded capacity or performance
Reason The transmission supervision has detected an uplink congestion.
Remedial Action Check the physical transmission links. Are there any outstanding
alarms. Use the LMT to view the Physical Link Status. Check that the
PVCs are correctly configured with mainly with respect to the PCR
value. The alarm will be ceased automatically when the reason for
congestion is removed.
34
5.4 CoolingSystem alarms

The following alarms are generated by the CoolingSystem.
• MicroBTS_1025_00150 - COOLING FAN FAULT

35
5.4.1 MicroBTS_1025_00150 - COOLING FAN FAULT

Cooling fan fault.
COOLING FAN FAULT

Object Class MicroBTS/SectorEquipment/CoolingSystem
Equipment Type CoolingSystem
Severity
• minor
• MAJOR
Impact No impact - if the temperature becomes the SECTOR UNIT TEMPER-
ATURE TOO HIGH alarm will be raised.
Reason Cooling fan fault.
Remedial Action Check that the fans work properly and make sure that nothing ob-
structs the air flow. If the fans are faulty, replace the fan package.
36
5.5 ExternalAlarmPort alarms

The following alarms are generated by the ExternalAlarmPort.
• MicroBTS_1001_00140 - EXTERNAL EQUIPMENT ALARM

37
5.5.1 MicroBTS_1001_00140 - EXTERNAL EQUIPMENT ALARM

One of the supervised external alarms has been detected.
EXTERNAL EQUIPMENT ALARM

Object Class MicroBTS
Equipment Type ExternalAlarmPort
Event Type environmentalAlarm
Probable Cause unspecifiedReason
Severity
• CRITICAL
• MAJOR
• minor
• warning
Impact None
Reason One of the supervised external alarms has been detected.
Remedial Action The alarm will be ceased when the alarm trigger condition is removed,
for example, the door is closed when a door open state is supervised.
38
5.6 IMAGroup alarms

The following alarms are generated by the IMAGroup.
• MicroBTS_1021_00110 - IMA GROUP FAULT

39
5.6.1 MicroBTS_1021_00110 - IMA GROUP FAULT

A fault has been detected in the IMA Group.
IMA GROUP FAULT

Object Class MicroBTS/IMAGroup
Equipment Type IMAGroup
Severity
• MAJOR
Impact All traffic services are shut down.
Reason A fault has been detected in the IMA Group.
Remedial Action The operator should inspect the individual IMA links for errors when
the IMA group is degraded. The operator should inspect the IMA link
and the IMA group configurations in the case when the IMA group is
disabled. The transmission network or the RNC may be wrongly con-
figured, or they may contain defect transmission hardware in both par-
tial and total IMA group fault cases. The IMA group major classified
alarm ceases automatically if at least one of the IMA links goes back to
enabled state. The degraded status due to the IMA link fault is cleared
if all configured IMA links are in enabled state. The BTS 1120/BTS
1010 automatically restarts when the IMA group goes disabled as an
attempt to recover from the fault.
40
5.7 ItfB alarms

The following alarms are generated by the ItfB.
• MicroBTS_1034_00020 - MANAGEMENT CHANNEL FAULT

41
5.7.1 MicroBTS_1034_00020 - MANAGEMENT CHANNEL FAULT

The Operation and Maintenance Port is down.
MANAGEMENT CHANNEL FAULT

Object Class MicroBTS/ItfB
Equipment Type ItfB
Severity
• minor
Impact Possible as the BTS 1120/BTS 1010 restarts after a timeout or at low
traffic hour.
Reason The Operation and Maintenance Port is down.
Remedial Action Check that the OMC is up. Check that the IP configuration of the BTS
1120/BTS 1010 is correct. Check that the BTS 1120/BTS 1010 config-
uration, the RNC configuration and the transmission network configur-
ations are consistent with respect to the PVC used for IP over ATM
(ItfB). If the OaM Link Supervision is active, the BTS 1120/BTS 1010
will restart after 2 hours have elapsed, provided there is no traffic on-
going (dedicated channels). If the node has live traffic (dedicated chan-
nels) the restart will be postponed until low traffic hour of the day,
which is configurable.
42

A neighboring node has signaled to the BTS an upstream connectivity failure. A neighboring node
has signaled to the BTS an upstream connectivity failure.
F5 AIS ERROR
Equipment Type ItfB
Severity
• MAJOR
failure. A neighboring node has signaled to the BTS an upstream con-
nectivity failure.

43

F5 RDI ERROR
Equipment Type ItfB
Severity
• MAJOR
failure.
44


Equipment Type ItfB
Severity
• minor

45
5.8 MicroBTS alarms

The following alarms are generated by the MicroBTS.
• MicroBTS_1005_00000 - NTP SERVER UNAVAILABLE
• MicroBTS_1006_00000 - INACCURATE RF REFERENCE
• MicroBTS_1007_00000 - LMT CONNECTED
• MicroBTS_1015_00000 - OFFICE DATA ERROR
• MicroBTS_1022_00000 - TIMING REFERENCE LOST IN BTS
• MicroBTS_1039_00000 - LOCKED BY SITE SWITCH
• MicroBTS_1043_00000 - FILE STORAGE FULL
• MicroBTS_1044_00000 - USER PLANE FRAME PROTOCOL PROBLEM
46
5.8.1 MicroBTS_1005_00000 - NTP SERVER UNAVAILABLE

The NTP Server is not available.
NTP SERVER UNAVAILABLE

Equipment Type MicroBTS
Severity
• minor
Impact No impact on traffic services. The BTS 1120/BTS 1010 is unable to
produce performance observation files.
Reason The NTP Server is not available.
Remedial Action Check the configuration of the NTP server IP address. Check that the
NTP server is up - try ping. Check that the network infrastructure lets
the NTP traffic through. The fault ceases automatically when the con-
tact with the NTP server recovers (automatically or by an assistance of
the operator). The BTS 1120/BTS 1010 retries to re-establish the con-
tact with the NTP server frequently.

47
5.8.2 MicroBTS_1006_00000 - INACCURATE RF REFERENCE

The RF Reference is outside 3GPP requirements.
INACCURATE RF REFERENCE
Event Type processingErrorAlarm
Probable Cause timingProblem
Severity
• MAJOR
Impact All traffic services are shut down.
Reason The RF Reference is outside 3GPP requirements.
Remedial Action Inspect the status of the physical links. The physical link status view
can be read using the Local Management Tool. The fault ceases auto-
matically when the BTS 1120/BTS 1010 is able to obtain synchroniza-
tion from one of its physical links. The fault ceases automatically when
the required RF stability is reached. For example, after the timing refer-
ence has recovered, that is, when the RF reference is within 3GPP
specification. Note that it can take some time for the PLL to stabilize. If
the alarm persists even though synchronization can be obtained via
the physical links, the reason can be an hardware fault in BTS
1120/BTS 1010 and the unit needs to be replaced. Always attempt a
restart first though.
48
5.8.3 MicroBTS_1007_00000 - LMT CONNECTED

The Local Management Tool has been connected.
LMT CONNECTED
Event Type operatorAlarm
Severity
• warning
Impact None
Reason The Local Management Tool has been connected.
Remedial Action The alarm ceases when the LMT Ethernet contact is disconnected. If
the alarm is activated but no management via the LMT is expected,
somebody can be attempting an unauthorized access to the BTS
1120/BTS 1010.

49
5.8.4 MicroBTS_1015_00000 - OFFICE DATA ERROR

The Office Data in the BTS is not valid.
OFFICE DATA ERROR

Probable Cause configurationOrCustomizationError
Severity
• CRITICAL
Impact Node will not start the traffic services.
Reason The Office Data in the BTS is not valid.
Remedial Action Check the additional text of the alarm for more precise information
about the faulty parameters. Correct the parameters and apply the new
configuration. The alarm will be ceased when the erroneous Office
Data parameter is corrected and upgraded in the BTS 1120/BTS 1010.
50
5.8.5 MicroBTS_1022_00000 - TIMING REFERENCE LOST IN BTS

The timing reference has been lost.
TIMING REFERENCE LOST IN BTS

Probable Cause lossOfSignal
Severity
• minor
Impact None - the INACCURATE RF REFERENCE alarm will be raised if the
state persists for along time.
Reason The timing reference has been lost.
Remedial Action Inspect the status of the physical links. The physical link status view
can be read using the Local Management Tool. The fault ceases auto-
matically when the BTS 1120/BTS 1010 is able to obtain synchroniza-
tion from one of its physical links.

51
5.8.6 MicroBTS_1039_00000 - LOCKED BY SITE SWITCH

The site switch has ordered shutdown of traffic.
LOCKED BY SITE SWITCH

Severity
• warning
Impact Warning - All traffic services are shut down.
Reason The site switch has ordered shutdown of traffic.
Remedial Action Before unlocking the BTS Site, always make sure no one is near the
physical unit. The alarm will be ceased when the BTS Site object is un-
locked, by either from OMC or with the Remote Shutdown Control
switch.
52
5.8.7 MicroBTS_1043_00000 - FILE STORAGE FULL

File system is full.
FILE STORAGE FULL

Probable Cause outOfMemory
Severity
• minor
Impact The traffic services are not impacted. The performance jobs will be
stopped.
Reason File system is full.
Remedial Action Investigate the reason why the BTS 1120/BTS 1010 is unable to store
the performance observation files on the PM FTP server. Is the PM
FTP server up? Is the PM FTP server correctly configured? Is the Per-
formance Job correctly configured? Is the IP infrastructure up? Once
the reason is known a repair action should be carried out to enable the
file transfer mechanism.

53
5.8.8 MicroBTS_1044_00000 - USER PLANE FRAME PROTOCOL

PROBLEM
User plane frame protocol error.
USER PLANE FRAME PROTOCOL PROBLEM

Severity
• minor
Impact Possible performance and capacity degradation.
Reason User plane frame protocol error.
Remedial Action Check the transmission link. Check the configuration. Check the syn-
chronization. If only one BTS 1120/BTS 1010 alarms then the operator
should try to restart the BTS 1120/BTS 1010. If the restart doesn't re-
cover the problem also the upstream nodes should be checked for er-
rors. If everything is error free in upstream nodes the replacement of
BTS 1120/BTS 1010 may be required.
54
5.9 NodeBCP alarms

The following alarms are generated by the NodeBCP.
• MicroBTS_1032_00030 - NODE B CONTROL PORT FAULT

55
5.9.1 MicroBTS_1032_00030 - NODE B CONTROL PORT FAULT

Node B Control Port is down.
NODE B CONTROL PORT FAULT

Object Class MicroBTS/NodeBCP
Equipment Type NodeBCP
Severity
• MAJOR
Reason Node B Control Port is down.
respect to the PVC used for Node BCP. Check that the RNC is running
properly. Check that the transmission lines are working. The BTS 1120
/ BTS 1010 will restart periodically if the Node BCP remains faulty.
56

F5 AIS ERROR
Severity
• MAJOR
failure.

57

F5 RDI ERROR
Severity
• MAJOR
failure.
58


Severity
• minor
PVC is correctly configured with mainly with respect to the PCR value.
The alarm will be ceased automatically when the reason for congestion
is removed.

59
5.10 PhysicalLink alarms

The following alarms are generated by the PhysicalLink.
• MicroBTS_1017_00090 - PHYSICAL LINK FAULT
• MicroBTS_1019_00090 - IMA LINK FAULT
60
5.10.1 MicroBTS_1017_00090 - PHYSICAL LINK FAULT

Physical tranmission link is down.
PHYSICAL LINK FAULT

Object Class MicroBTS/PhysicalLink
Equipment Type PhysicalLink
Probable Cause communicationsProtocolError
Severity
• MAJOR
Impact Reduced capacity in case IMA is used and there are other working
Physical Links. All traffic services will be shut down if IMA is not used
and BTS 1120/BTS 1010 CP, CCP or ALCAP is impacted. If User Data
PVCs are impacted the traffic services carried on them may be disrup-
ted.
Reason Physical tranmission link is down.
Remedial Action The operator should inspect the physical link status view in order to
gain more information about the fault source. Check the transmission
network and its configuration. Check the transmission cables. The
physical link alarm is ceased automatically by BTS 1120/BTS 1010
when the physical link goes back to enabled state.

61
5.10.2 MicroBTS_1019_00090 - IMA LINK FAULT

A fault has been detected in an IMA Link.
IMA LINK FAULT

Object Class MicroBTS/PhysicalLink
Equipment Type PhysicalLink
Severity
• MAJOR
• minor
Impact Reduced capacity.
Reason A fault has been detected in an IMA Link.
Remedial Action The major IMA link alarm ceases automatically once the IMA link goes
to enabled state. Inspect the operational condition of the physical
transmission link in case of the IMA link alarm. Repair the physical link
fault if it is faulty. Inspect the ATM transmission network and RNC
working condition. The configuration and hardware of these should be
checked for any errors and faults.
62
5.11 PowerSystem alarms

The following alarms are generated by the PowerSystem.
• MicroBTS_1026_00160 - INCOMING POWER LOST
• MicroBTS_1027_00160 - BATTERY MALFUNCTION
• MicroBTS_1028_00160 - BATTERY DISCHARGED
• MicroBTS_1045_00160 - INCOMING POWER LEVEL OUT OF RANGE

63
5.11.1 MicroBTS_1026_00160 - INCOMING POWER LOST

If this alarm is displayed frequently check the power supply for the BTS 1120 (Micro).
INCOMING POWER LOST

Object Class MicroBTS/SectorEquipment/PowerSystem
Equipment Type PowerSystem
Probable Cause powerProblem
Severity
• MAJOR
Impact No traffic impact as long as the backup battery - if attached - lasts.
Reason If this alarm is displayed frequently check the power supply for the BTS
1120 (Micro).
Remedial Action Repair the power fault.
64
5.11.2 MicroBTS_1027_00160 - BATTERY MALFUNCTION

The internal backup battery is faulty.
BATTERY MALFUNCTION
Severity
• MAJOR
• minor
Impact None - as long as there is no problem with the incoming power.
Reason The internal backup battery is faulty.
Remedial Action Minor: Replace the battery within sector equipment unit within reason-
able time. The battery is close to its end of life. Major: The battery has
passed its end of life and need to be replaced immediately.

65
5.11.3 MicroBTS_1028_00160 - BATTERY DISCHARGED

The internal backup battery is discharged.
BATTERY DISCHARGED
Severity
• MAJOR
Impact None - as long as there is no problem with the incoming power.
Reason The internal backup battery is discharged.
Remedial Action This is a normal alarm after a longer interrupt in the incoming power,
during which the BTS 1120 (Micro) has been running on the backup
battery. If the alarm persists for more than 24 h the battery needs to be
replaced.
66
5.11.4 MicroBTS_1045_00160 - INCOMING POWER LEVEL OUT OF

RANGE
The incoming power voltage level is out of range.
INCOMING POWER LEVEL OUT OF RANGE

Severity
• warning
• MAJOR
Impact Warning - No service impact. Major - All traffic services will be shut
down.
Reason The incoming power voltage level is out of range.
Remedial Action Investigate the reason for abnormal incoming DC power level on the
site. Check the power supply. If the incoming power level stabilizes the
alarm will be ceased automatically. Cease of major alarm will resume
the live traffic services automatically.

67
5.12 SectorEquipment alarms

The following alarms are generated by the SectorEquipment.
• MicroBTS_1008_00010 - SECTOR UNIT TEMPERATURE TOO LOW
• MicroBTS_1009_00010 - SECTOR UNIT TEMPERATURE TOO HIGH
• MicroBTS_1011_00010 - SECTOR HARDWARE FAULT
• MicroBTS_1036_00010 - LICENSE ERROR
• MicroBTS_1037_00010 - LICENSE EXPIRED
• MicroBTS_1038_00010 - CONTROL PROCESSOR OVERLOAD
68
5.12.1 MicroBTS_1008_00010 - SECTOR UNIT TEMPERATURE TOO

LOW
The operating temperature for the Sector unit is below the limit.
SECTOR UNIT TEMPERATURE TOO LOW

Object Class MicroBTS/SectorEquipment
Equipment Type SectorEquipment
Probable Cause temperatureUnacceptable
Severity
• MAJOR
• warning
Impact Minor - No service impact, Major - All traffic services will be shut down.
Reason The operating temperature for the Sector unit is below the limit.
Remedial Action The most probable reason is a too low ambient temperature. If the
BTS 1120/BTS 1010 has been recently powered up there is a chance
that it will warm up itself. When the temperature raises to above the
threshold level for the Major alarm traffic services will be brought up
automatically by the BTS 1120/BTS 1010.

69
5.12.2 MicroBTS_1009_00010 - SECTOR UNIT TEMPERATURE TOO

HIGH
The operating temperature for the Sector unit is above the limit.
SECTOR UNIT TEMPERATURE TOO HIGH

Probable Cause heatingOrVentilationOrCoolingSystemProblem
Severity
• MAJOR
• warning
Impact Minor - No service impact, Major - All traffic services are shut down.
Reason The operating temperature for the Sector unit is above the limit.
Remedial Action Check that that the fans - if attached - are working correctly. Is the
COOLING FAN FAULT alarm active? Also ensure that no objects ob-
struct the air flow. When the temperature is lowered (for example,
when the cooling is restored or the ambient temperature declines) un-
der the specified threshold level an automatic recovery will happen.
The traffic services will be brought up automatically when the major
alarm ceases.
70
5.12.3 MicroBTS_1011_00010 - SECTOR HARDWARE FAULT

A hardware fault has been detected.
SECTOR HARDWARE FAULT

Severity
• MAJOR
• minor
Reason A hardware fault has been detected.
Remedial Action The operator should try to restart the BTS 1120/BTS 1010. If the alarm
persists after a couple of restarts, the BTS 1120/BTS 1010 unit shall
be replaced.

71
5.12.4 MicroBTS_1036_00010 - LICENSE ERROR

License Upgrade function has failed.
LICENSE ERROR
Severity
• minor
Impact N/A
Reason License Upgrade function has failed.
Remedial Action Check the license server.
72
5.12.5 MicroBTS_1037_00010 - LICENSE EXPIRED

The license has expired.
LICENSE EXPIRED
Severity
• minor
Impact N/A
Reason The license has expired.
Remedial Action Update the license.

73
5.12.6 MicroBTS_1038_00010 - CONTROL PROCESSOR OVERLOAD

The control processor in Node B is overloaded.
CONTROL PROCESSOR OVERLOAD

Probable Cause processorProblem
Severity
• minor
Impact Possible lost calls and capacity and performance degradation.
Reason The control processor in Node B is overloaded.
Remedial Action Reduce the number of measurements initiated by the RNC. Reduce or
remove performance jobs. Restructure the network, possibly by adding
more cells etc.
74
5.13 UserDataPort alarms

The following alarms are generated by the UserDataPort.
• MicroBTS_1035_00070 - USER DATA PORT FAULT

75
5.13.1 MicroBTS_1035_00070 - USER DATA PORT FAULT

User Data Port is down.
USER DATA PORT FAULT

Object Class MicroBTS/UserDataPort
Equipment Type UserDataPort
Severity
• MAJOR
Impact Disturbance of the traffic services carried by the User Data Port in
question. Capacity degradation.
Reason User Data Port is down.
Remedial Action Recover the transmission links carrying the User Data Port. Check the
configuration.
76

A neighboring node has signaled to the BTS an upstream connectivity failure. A neighboring node
has signaled to the BTS an upstream connectivity failure.
F5 AIS ERROR
Severity
• MAJOR
failure. A neighboring node has signaled to the BTS an upstream con-
nectivity failure.

77

F5 RDI ERROR
Severity
• MAJOR
failure.
78
5.13.4 MicroBTS_1042_00070 - UPLINK TRANSMISSION

CONGESTION

Severity
• minor

79
5.14 OAM alarms

The following Andrew alarms are generated by the OAM.
• OAM_0096_00058 - Unexpected software version
• OAM_0097_00058 - Loss of supervision
• OAM_0098_00058 - BTS enters in SAFE mode
• OAM_0099_00058 - BTS RESTART
• OAM_0100_00058 - Supervision inhibited by operator
80
5.14.1 OAM_0096_00058 - Unexpected software version

This alarm indicates that the software release running on the BTS is inconsistent with the software
release defined at OMC-B level. The runningSoftwareVersion parameter received during the
connection phase is not aligned with the defintion in OMC-B's database.
Unexpected software version

Alarm Code OAM_0096_00058
RAN Managed Ob- MicroBTS
ject
Equipment Type N/A
Event Type quality of service
Probable Cause sfwrEnvironmentProblem
Severity MAJOR
Impact The BTS software may be inconsistent with respect to its configuration.
Reason Software release running on BTS is different from the software release
defined in OMC-B's database.
Remedial Action Download and Activate the appropriate software release from the SRS.

81
5.14.2 OAM_0097_00058 - Loss of supervision

This alarm indicates that there was a loss of supervision with the MicroBTS. OAMLinkAdmState
equal to unlocked and MicroBTS unknownStatus equal to TRUE.
Loss of supervision
ject
Equipment Type N/A
Event Type communications
Probable Cause communicationsSubsystemFailure
Severity CRITICAL
Impact The state of MicroBTS is unknown due to loss of OAM link.
Reason Loss of OAM link between OMC and MicroBTS.
Remedial Action cf iBTS Hardware maintenance Guide - No particular action is re-
quired. This notification may be required by Global Product Support for
debugging purposes
82
5.14.3 OAM_0098_00058 - BTS enters in SAFE mode

This event is generated when the BTS enters in a SAFE mode. Alarm is cleared when BTS restarts
and enters in a NORMAL mode.
BTS enters in SAFE mode

ject
Equipment Type N/A
Event Type quality of service
Severity CRITICAL
Impact Degraded service.
Reason This event is generated when the BTS enters in a SAFE mode. Alarm
is cleared when BTS restarts and enters in a NORMAL mode.
Remedial Action N/A

83
5.14.4 OAM_0099_00058 - BTS RESTART

This event indicates a restart of the micro/pico BTS.
BTS RESTART
ject
Equipment Type N/A
Event Type processing error
Probable Cause softwareProgramError
Severity warning
Impact N/A
Reason This event indicates a restart of the micro/pico BTS.
Remedial Action N/A
84
5.14.5 OAM_0100_00058 - Supervision inhibited by operator

This alarm indicates that OAMLinkAdministrativeState parameter (MicroBTS NE) is set to locked.
This alarm indicates that the MicroBTS is no more supervised. OAM link with the MicroBTS is closed.
Supervision inhibited by operator

ject
Equipment Type N/A
Event Type communications
Severity warning
Impact The MicroBTS supervision is inhibited because the OAMLinkAdminis-
trativeState is locked.
Reason Supervision inhibited by operator. OAM link with the MicroBTS is
closed.
Remedial Action If the MicroBTS supervision is required, set the OAMLinkAdministrat-
iveState to unlocked.

85
Alcatel-Lucent 9353
Wireless Management System
Alcatel-Lucent
Document number: NN-20500-018P3

Document issue: 07.04/EN
Document status: Standard
Product Release: V7.1
Date: June 2010
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of
their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained
herein.
Copyright © 2004-2010 Alcatel-Lucent, All Rights Reserved
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or
used by anyone outside Alcatel-Lucent without its written authorization.
Not to be used or disclosed except in accordance with applicable agreements.

MPR Configuration File Management

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

MPR Configuration File Management

Diunggah oleh

Hak Cipta:

Format Tersedia

Alcatel-Lucent 9353

Wireless Management System | V7.1

Document number: NN-20500-018P3

SYSTEM RELEASE: OAM07.0

SYSTEM RELEASE: OAM06.0

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

1 About this publication................................................................................................................................................. 10

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

5.8.6 MicroBTS_1039_00000 - LOCKED BY SITE SWITCH......................................................................................51

Figure 1 - Roadmap to Fault Mangement documentation.................................................................................. ......... 12

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

1 About this publication

How this publication is organized

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

2 Roadmap to Fault Management documentation

Figure 1 Roadmap to Fault Mangement documentation

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

3 New in this release

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

4 How to use this publication

Description of a Node B alarm sheet

Figure 2 Alarm Manager window

Alarm name: the specific problem of the alarm

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

Alarm name: the specific problem of the alarm

Alarm Code format

Alarm Type - Probable Cause

Alarm Type Probable Cause

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

9313 Micro and 9314 Pico Node Bs designation

5 9313 Micro and 9314 Pico alarm descriptions

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

5.1 ALCAP alarms

5.1.1 MicroBTS_1040_00050 - F5 AIS ERROR

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

5.1.2 MicroBTS_1041_00050 - F5 RDI ERROR

5.1.3 MicroBTS_1046_00050 - ALCAP PORT FAULT

ALCAP PORT FAULT

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

5.2 AntennaAccess alarms

5.2.1 MicroBTS_1029_00130 - VSWR FAULT

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

5.2.2 MicroBTS_1030_00130 - RX DIVERSITY BRANCH A FAULT

RX DIVERSITY BRANCH A FAULT

5.2.3 MicroBTS_1031_00130 - RX DIVERSITY BRANCH B FAULT

RX DIVERSITY BRANCH B FAULT

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

5.3 CCP alarms

5.3.1 MicroBTS_1033_00060 - COMMUNICATION CONTROL PORT

COMMUNICATION CONTROL PORT FAULT

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

5.3.2 MicroBTS_1040_00060 - F5 AIS ERROR

5.3.3 MicroBTS_1041_00060 - F5 RDI ERROR

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

5.3.4 MicroBTS_1042_00060 - UPLINK TRANSMISSION CONGESTION

UPLINK TRANSMISSION CONGESTION

5.4 CoolingSystem alarms

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

5.4.1 MicroBTS_1025_00150 - COOLING FAN FAULT

COOLING FAN FAULT

5.5 ExternalAlarmPort alarms

NN-20500-018P3 07.04/EN Standard June 2010 Copyright © 2004-2010 Alcatel-Lucent

5.5.1 MicroBTS_1001_00140 - EXTERNAL EQUIPMENT ALARM