Beruflich Dokumente
Kultur Dokumente
UMTS
UTRAN Operation, Administration,
Maintenance and Provisioning
UMTS-04.03
UTRAN OAM&P
401-382-290R04.03
Issue 1
August 2007
Alcatel-Lucent - Proprietary
This document contains proprietary information of Alcatel-Lucent and
is not to be disclosed or used except in accordance with applicable agreements.
Copyright © 2007 Alcatel-Lucent
Unpublished and Not for Publication
All Rights Reserved
See notice on first age
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 © 2007 Alcatel-Lucent. All Rights Reserved.
Notice
Every effort has been made to ensure that the information contained in this information product was accurate at the time of printing. However,
information is subject to change.
Conformance statements
There are no in-country requirements that are applicable for this Information Product.
Alcatel-Lucent - Proprietary
See notice on first page
Contents
Tasks ................................................................................................................................................................................................. lx
1 Hazard statements
2 UTRAN overview
Mechanical structure of the Lucent UMTS Macrocell Compact Indoor ........................................................ 3-12
Component numbering in the Lucent UMTS Macrocell Compact Indoor .................................................... 3-16
Mechanical structure of the Lucent UMTS Macrocell Compact Outdoor ..................................................... 3-19
Component numbering in the Lucent UMTS Macrocell Compact Outdoor ................................................. 3-23
Structure of the UMTS Lucent UMTS Modular Cell Outdoor for +24V
Component numbering in the UMTS Modular Cell Outdoor for +24 V ....................................................... 3-32
...................................................................................................................................................................................................................................
iv Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
5 UTRAN tools
6 Radio frequencies
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary v
Issue 1, August 2007 See notice on first page
Contents
7 E1T1 growth
Introduction
...................................................................................................................................................................................................................................
vi Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
Information Models
11 Principles of maintenance
12 Preventive maintenance
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary vii
Issue 1, August 2007 See notice on first page
Contents
...................................................................................................................................................................................................................................
viii Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
General information
ALDController alarms
AlarmHub alarms
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary ix
Issue 1, August 2007 See notice on first page
Contents
AmpShelfFan alarms
CPC alarms
CPRIPort alarms
CTU alarms
...................................................................................................................................................................................................................................
x Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
Cell alarms
DigitalShelfFan alarms
E1T1Port alarms
E3T3Port alarms
...................................................................................................................................................................................................................................
xii Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
EthernetPort alarms
ExtRxAmp alarms
Filter alarms
Frame alarms
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary xiii
Issue 1, August 2007 See notice on first page
Contents
GRS alarms
IMAGroup alarms
IOU alarms
...................................................................................................................................................................................................................................
xiv Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
NodeB alarms
OCM alarms
...................................................................................................................................................................................................................................
xvi Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
OM alarms
RETActuator alarms
RFHead alarms
Radio alarms
RxAmp alarms
STM1OC3Port alarms
TDU alarms
TxAmp alarms
UCU alarms
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary xxiii
Issue 1, August 2007 See notice on first page
Contents
URC alarms
General information
AC alarms
CICC alarms
...................................................................................................................................................................................................................................
xxiv Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
CICCBPEtherPort alarms
CICCProc alarms
Cabinet alarms
EDCH alarms
ESC alarms
...................................................................................................................................................................................................................................
xxvi Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
ESCBPEtherPort alarms
ESCFAEtherPort alarms
ESCProc alarms
ExtAlmBox alarms
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary xxvii
Issue 1, August 2007 See notice on first page
Contents
FBPShelf alarms
FanTray alarms
GICC alarms
GICCBPEtherPort alarms
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary xxix
Issue 1, August 2007 See notice on first page
Contents
GICCFAEtherPort alarms
GICCProc alarms
GICCSTM1OC3Port alarms
...................................................................................................................................................................................................................................
xxx Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
HSDPA alarms
IuB alarms
IuCS alarms
IuPS alarms
IuPSSubNet alarms
IuR alarms
...................................................................................................................................................................................................................................
xxxii Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
LCell alarms
LNodeB alarms
LRNC alarms
OCNS alarms
OCNSHSDPA alarms
PG alarms
PRACH alarms
...................................................................................................................................................................................................................................
xxxvi Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
PSU alarms
RF trace alarms
SB alarms
SBBPEtherPort alarms
SBClan alarms
SBProc alarms
...................................................................................................................................................................................................................................
xxxviii Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
SCCPCHFach alarms
SCCPCHPch alarms
SMLC alarms
SS7Link alarms
SS7LinkSet alarms
SS7Stack alarms
...................................................................................................................................................................................................................................
xl Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
Diagnose hardware
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary xli
Issue 1, August 2007 See notice on first page
Contents
Reset objects
22 PM data collection
Add objects
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary xliii
Issue 1, August 2007 See notice on first page
Contents
Modify objects
Remove objects
Add objects
...................................................................................................................................................................................................................................
xlvi Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
Modify objects
Remove objects
...................................................................................................................................................................................................................................
xlviii Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
Rehome Node B
26 Manage software
Backup data
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary xlix
Issue 1, August 2007 See notice on first page
Contents
...................................................................................................................................................................................................................................
l Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
27 Manage services
OCNS service
RF trace service
HSDPA-OCNS service
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary li
Issue 1, August 2007 See notice on first page
Contents
A Wizard descriptions
Create wizards
...................................................................................................................................................................................................................................
lii Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Contents
Modify wizards
Remove wizards
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary lv
Issue 1, August 2007 See notice on first page
Contents
Glossary
Index
...................................................................................................................................................................................................................................
lvi Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
About this information product
About this information product
Purpose
The purpose of this information product is to:
• Present an overview of how Operation, Administration, Maintenance and
Provisioning is performed on the UTRAN
• Present an overview of the hardware in the UTRAN
• Describe the Object Information Model that is used to represent the UTRAN
• Provide the Operation, Administration, Maintenance and Provisioning procedures
that an OMC operator is able to perform on the UTRAN
Intended audience
The audience for this information product includes:
• OMC administrator
• OMC operator
Conventions used
The following conventions are used in the document:
Technical support
For technical support, contact your local customer support team. Reach them via the
web at https://support.lucent.com/ or the telephone number listed under the Technical
Assistance Center menu at http://www.lucent.com/contact/.
How to order
Website ordering
To order Lucent Technologies information products, contact your local sales
representative, use the following websites, or use the email, phone, and fax contacts
linked from “Contact Us” on these sites:
• Documentation: http://www.lucentdocs.com
• Training: https://training.lucent.com/
Telephone, fax or email ordering
To order Lucent Technologies information products from an order entry representative
use one of the following:
• Within the United States, call 1-888-582-3688 or send email to
cicorders@lucent.com (to fax an order, call 1-800-566-9568).
• Within Canada, call 1-317-322-6616 or send email to cicorders@lucent.com (to fax
an order, call 1-317-322-6699).
• International, call 1-317-322-6416 or send email to intlorders@lucent.com (to fax
an order, call 1-317-322-6699).
Related documentation
Documents that are related to this information product are:
• UMTS Lucent OMC-UPS Operations, Administration, Maintenance, and
Provisioning, 401-380-022
• UMTS Lucent Managed Object Descriptions, 401-380-071
• UMTS Radio Network Controller Technical Description, 401-382-320
• UMTS Radio Network Controller Operations, Administration and Maintenance
RNC OA&M, 401-382-360
• Lucent UMTS Macrocell Indoor, Operation, Administration and Maintenance for
+24V, 401-382-462
• Lucent UMTS Modular Cell Outdoor, Operation, Administration and Maintenance
for +24V, 401-382-760
• Lucent UMTS Macrocell Compact, Operation, Administration and Maintenance for
+24V, 401-382-961
• Lucent UMTS Microcell (Type M), Operation, Administration and Maintenance for
+24V, 401-382-966
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary lix
Issue 1, August 2007 See notice on first page
,
About this information product
Related training
Training products that are related to this information product:
• UMTS system introduction, UM1001 (for the instructor led version), UM1001C (for
the computer based version), or the UM1001W (for the web based version)
• UMTS Hardware Overview, UM1911 (for the instructor led version), UM1911C
(for the computer based version)
• UMTS Lucent OMC-UPS Network System Administration, UM4712
• UMTS Lucent OMC-UPS Network Configuration & Fault Management, UM4711
• UMTS UTRAN Signaling and Parameters, UM4302
Tasks
This information product describes how to:
• Perform Fault Management on the UTRAN using the OMC
• Perform Configuration Management on the UTRAN using the OMC
• Perform Performance Management on the UTRAN using the OMC
How to comment
To comment on this information product, go to the Online Comment Form
(http://www.lucent-info.com/comments/enus/) or e-mail your comments to the
Comments Hotline (comments@alcatel-lucent.com).
...................................................................................................................................................................................................................................
lx Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
,
Part I: Hazard statements
Overview
...................................................................................................................................................................................................................................
Purpose
This documentation part provides the hazard statements that relate to UTRAN.
There are no physical hazards that are related to the tasks that an OMC operator can
perform on the UTRAN.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary I-1
Issue 1, August 2007 See notice on first page
1 H azard statements
1
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter provides the hazard statements that relate to UTRAN.
References
For more information about the hazard statements of the Lucent Technologies UTRAN
hardware, refer to:
• Lucent RNC Operations, Administration and Maintenance, 401-382-360
• Lucent UMTS Macrocell Indoor, Operation , Administration and Maintenance for
+24 V, 401-382-462
• Lucent UMTS Modular Cell Outdoor Operation, Administration and Maintenance
for +24V , 401-382-760
• Lucent UMTS Macrocell Compact, Operation, Administration and Maintenance for
+24V, 401-382-961
• Lucent UMTS Microcell (Type M), Operation , Administration and Maintenance,
401-382-966
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 1-1
Issue 1, August 2007 See notice on first page
Hazard statements
No hazard statements
There are no hazard statements related to the tasks that an OMC operator can perform
on the UTRAN.
...................................................................................................................................................................................................................................
1-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Part II: System description
Overview
...................................................................................................................................................................................................................................
Purpose
This documentation part includes descriptive information about the UTRAN
components.
Reference
For more information about the technical specifications of the Lucent Technologies
RNC and the Node B, refer to:
• Lucent RNC Technical Description, 401-382-320
• Lucent UMTS Macrocell, Technical Description for -48 V, 401-382-420
• Lucent UMTS Macrocell, Technical Description for -24 V, 401-382-421
• Lucent UMTS Modular Cell Outdoor, Technical Description for +24 V,
401-382-720.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary II-1
Issue 1, August 2007 See notice on first page
2 U TRAN overview
2
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter describes the architecture, functions and maintenance aspects of the
UMTS Terrestrial Radio Access Network (UTRAN).
Overview
The aspects of the UTRAN can be subdivided into the following subjects:
• Architecture and functions
• Elements
• Interfaces
• Transmission equipment
• Operating and Maintenance Center (OMC).
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 2-1
Issue 1, August 2007 See notice on first page
UTRAN overview
UMTS network
...................................................................................................................................................................................................................................
Overview
The UMTS network architecture consists of three main parts:
• User equipment.
• UTRAN
• Core network
Network architecture
UMTS network architecture:
PSTN/ISDN IP networks
Core network
3G-MSC 3G-SGSN
Access
network
RNC RNC
Node B Node B
...................................................................................................................................................................................................................................
2-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
UTRAN overview UMTS network
User equipment
The term User Equipment (UE) refers to the mobile devices that are used to access
UMTS services.
Examples of UEs are:
• Mobile phone
• Personal Digital Assistant (PDA)
• Laptop personal computer.
Access network
The access network is known as the UMTS Terrestrial Radio Access Network
(UTRAN) and provides user access to the core network. The UTRAN also manages
the radio resources, call setup, and handovers.
A UMTS network may consist of one or more access networks that use different radio
access systems and that are linked to the same core network. Together these networks
form a single UMTS network.
The entities of the UTRAN are:
• Radio Network Controller (RNC)
• Node B.
Core network
The core network provides central switching, transmission and service-provisioning
functions that are required to provide UMTS services.
The entities of the core network are grouped into functional areas:
• Entities to support circuit-switched services
• Entities to support packet-switched services
• Entities that are shared by packet-switched and circuit-switched services.
Circuit-switched entities
The entities of the circuit-switched core network are:
• Mobile Switching Center (3G-MSC)
• Gateway MSC (GMSC)
• Visitor Location Register (VLR).
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 2-3
Issue 1, August 2007 See notice on first page
UTRAN overview UMTS network
Packet-switched entities
The entities of the packet-switched core network are:
• Serving GPRS Support Node (3G-SGSN)
• Gateway GPRS Support Node (3G-GGSN).
Shared entities
The entities that are shared by the circuit-switched and packet-switched core networks
are:
• Home Location Register (HLR)
• Authentication Center (AuC)
• Equipment Identity Register (EIR).
...................................................................................................................................................................................................................................
2-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
UTRAN overview
Overview
The UTRAN consists of a series of Radio Network Subsystems (RNS). ’RNS’ is an
abstract term that defines the entities that manage the resources and
transmission/reception for a particular set of cells.
Functions
The functions of the UTRAN are:
• Radio resource management
• Bearer support for packet data
• Call setup and release
• Handover control
• User access to the core network.
Core network
Iu-cs Iu-ps
Itf-R
OMC
Cell UTRAN
Uu
th
y 20
Ma
y,
sda
Tue
s
sage
Mes
s
tact
Con
e
Offic
r
nda
Cale
User equipment
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 2-5
Issue 1, August 2007 See notice on first page
UTRAN overview UTRAN functions and interfaces
RNS
Each RNS contains:
• One RNC
• One or more Node Bs.
RNC interfaces
The RNC has the following interfaces:
• Iub interface to the Node Bs
• Iu-cs interface to the circuit-switched core network
• Iu-ps interface to the packet-switched core network
• Iur interface to other RNCs. An RNC can be interconnected to multiple other RNCs
• Itf-R interface to the OMC.
Node B interfaces
The Node B has the following interfaces:
• Uu interface to UEs
• Iub interface to the RNC
• Itf-B interface to the OMC.
...................................................................................................................................................................................................................................
2-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
UTRAN overview
Node B
...................................................................................................................................................................................................................................
Functions
The Node B is responsible for:
• Radio transmission and reception to and from the UE
• Termination of ATM Adaptation Layer (AAL) 5 and AAL-2 layers on the Iub
interface
• Call-processing functions, including channel-element resource allocation and
application processing
• OA&M processing, including circuit-pack status monitoring and reporting to the
OMC
• External-alarm inputs and output control
• Antenna connections.
Physical
The Lucent UMTS Node Bs are dedicated to UMTS macro cellular applications and
are available in both indoor and outdoor versions.A single cabinet offers a capacity of
3 sectors on 1 carrier frequency.
Receive diversity
The Lucent UMTS Node Bs supports two-channel antenna diversity for the uplink.
Each antenna uses a separate receiver. The data from the receivers is combined. This
improves the signal-to-noise ratio.
Antenna-tilt interface
The Lucent UMTS Node Bs supports an optional electrical antenna-tilt control
interface.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 2-7
Issue 1, August 2007 See notice on first page
UTRAN overview
Functions
The RNC is primarily responsible for:
• Supporting of call setup, maintenance and tear down
• Management of radio resources
• Management of UE mobility in the UTRAN.
Call setup
Support of call setup, maintenance and tear down includes:
• Handling of call-admission requests (including integrity checks on signaling
messages)
• Establishing, maintaining and deleting signaling bearers towards a UE
• Establishing, maintaining and deleting radio bearers (at agreed QoS levels) towards
a UE
• Handling the routing of end-user voice and/or data traffic between the core network
and supporting Node Bs
• Implementing the ciphering of user traffic and control-plane signaling.
Radio resources
Management of radio resources includes:
• Setting power-level targets
• Allocating radio-channel codes.
UE mobility
Management of UE mobility in the UTRAN includes:
• Performing hard/soft/softer handovers.
RNC types
Types of RNC:
• Serving RNC (SRNC)
• Drift RNC (DRNC).
Serving RNC
The SRNC controls the connection of an established call between the UE and the
UTRAN. The SRNC is the RNC where the UE originates a call.
...................................................................................................................................................................................................................................
2-8 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
UTRAN overview Radio Network Controller
Drift RNC
When the UE roams, the DRNC can support the SRNC by providing radio resources.
This is the case when the UE roams to cells that are not under the control of the
SRNC.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 2-9
Issue 1, August 2007 See notice on first page
UTRAN overview
Overview
The OMC is used for maintenance of the UTRAN. The OMC provides the Element
Management (EM) functions of the UTRAN. The OMC offers management of the
UTRAN from a centralized location.
Functions of the OMC are:
• Fault management
• Configuration management
• Performance management
• Security management
• Inventory management
• Software management
• Support for Network Management Systems (NMS).
...................................................................................................................................................................................................................................
2-10 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
UTRAN overview Operation and Maintenance Center (OMC)
Itf-N
OMC
Integrated SNM
EML
Node B RNC
EM EM
Itf-B Itf-R
Iub
NodeB RNC NEL
RMT/LMT LMT
Layers
The layers of the OA&M reference model are:
• Network Management Layer (NML)
• Element Management Layer (EML)
• Network Element Layer (NEL).
The OMC is part of the EML.
NML systems
Systems within the Network Management Layer are:
• Integrated Fault Management (IFM)
• Integrated Configuration Management (ICM)
• Integrated Performance Management (IPM)
• Integrated Inventory Management (IIM).
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 2-11
Issue 1, August 2007 See notice on first page
UTRAN overview Operation and Maintenance Center (OMC)
OMC interfaces
The OMC has the following interfaces:
• Itf-N between the OMC and the NMS (also named Northbound interface)
• Itf-R between the OMC and an RNC.
• Itf-B between the OMC and a Node B.
OMC connectivity
The OMC needs to connect to the UTRAN elements via both IP and ATM protocols.
The OMC can use an existing IP and/or an ATM infrastructure to connect with the
UTRAN elements.
Methods of transporting OA&M traffic via the Itf-R and Itf-B interfaces from the
OMC to the RNC and the Node B:
• In-band across the ATM network
• Separate data-connection network.
If the RNC is co-located with an ATM edge switch, the OA&M traffic from the OMC
to the Node B via the Itf-B can be sent on the physical links that are used for the Iub
traffic.
Overview
Network provisioning for the transmission equipment of the 3G wireless networks uses
the methods that are used for wireline networks. A transport network may have either
SDH or SONET equipment. Typically, the transmission equipment in the transport
networks consists of multiplexers that are arranged in ring configurations. The transport
network has to provide Internet Protocol (IP) over Asynchronous Transfer Mode
(ATM).
ATM
edge
device transport
network
OMC-T ethernet
ethernet
edge edge
device RNC
device
STM-1
4xE1 4xE1
Node B Node B
Transmission equipment
Types of transmission equipment:
• Edge devices, for example: switches and access concentrators
• ATM end users, for example: Node B, RNC, 3G-MSC, and 3G-SGSN
• ATM backbone switches in the ATM transport network.
ATM provisioning
ATM provisioning consists of the provisioning of ATM network elements within the
different domains of the UMTS network.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 2-13
Issue 1, August 2007 See notice on first page
UTRAN overview UTRAN Transmission equipment
IP network provisioning
The UMTS network has IP components in the access, circuit, transport, and packet
domains. Each of these domains contains elements that need configuration files and IP
addresses for equipment initialization.
IP network management
For network provisioning, the IP addresses are static. There is no direct need to
centralize the provisioning of IP addresses. However, it is essential that an inventory of
IP addresses is maintained. VitalQIP ™ can be used to maintain this inventory.
...................................................................................................................................................................................................................................
2-14 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
3 N ode B mechanical structure
3
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter contains the mechanical structure diagrams and component numbering of
the different Lucent UMTS Node B models.
These diagrams can be used by the OMC operator to determine:
• The Node B hardware that is available
• The location of the hardware within the Node B cabinet.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-1
Issue 1, August 2007 See notice on first page
Node B mechanical structure Overview
....................................................................................................................................................................................................................................
3-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides the mechanical structure diagrams and component numbering of
the different models of the UMTS Lucent Macrocell.
Related information
For more information about the Lucent UMTS Macrocell Indoor, refer to:
• Lucent UMTS Macrocell +24V Technical Description, 401-382-421.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-3
Issue 1, August 2007 See notice on first page
Node B mechanical structure
Overview
The Lucent UMTS Macrocell Indoor offers the opportunity for expansion to
configurations with more carriers and/or sectors, power, Tx diversity etc. by simply
adding the necessary circuit packs, amplifiers, etc.
J41
J41
LUCENT-SN XXXXXXXXXXXX
LUCENT-SN XXXXXXXXXXXX
LUCENT-SN XXXXXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
J2-C
J22-C
J2-C
J22-C
J2-C
J22-C
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
Filter shelf
Filter units
J24
J24
J24
J4
J4
J4
DIV0
DIV0
DIV0
J25
J25
J25
DIV1
DIV1
DIV1
J5
J5
J5
J26
J26
J26
J6
J6
J6
J11
J11
J11
J31
J31
J31
J7
J7
J7
J28
J28
J28
J8
J8
J8
J20 J21 J22 J23 J24 J25 J26 J27 J28 J29
DS1
CB1
CBs CB2
FAC
J7
-48VDC
Blank
Blank
Fan
(rear venting)
Amplifier shelf
AMPs
CB5-J16
J16
ESD
J1 J2 J3 J4
D C
J13
IN 1
J H
B
3
F
J5
PDP
A
5
E
J6 J7 J8
C
7
F
J14
B
9
E
A
11
D
J9 J10 J11 J12
Blank
Fan
(rear venting)
Digital shelf
Circuit packs
IOU OM CPCs
...................................................................................................................................................................................................................................
3-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Mechanical structure of the Lucent UMTS Macrocell
Indoor
J41
J41
J41
LUCENT-SN XXXXXXXXXXXX
LUCENT-SN XXXXXXXXXXXX
LUCENT-SN XXXXXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
J2-C
J22-C
J2-C
J22-C
J2-C
J22-C
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
J24
Filter units
J24
J24
J4
J4
J4
DIV0
DIV0
DIV0
J25
J25
J25
DIV1
DIV1
DIV1
J5
J5
J5
J26
J26
J26
J6
J6
J6
J11
J11
J11
J31
J31
J31
J7
J7
J7
J28
J28
J28
J8
J8
J8
Filter shelf
J41
J41
J41
LUCENT-SN XXXXXXXXXXXX
LUCENT-SN XXXXXXXXXXXX
LUCENT-SN XXXXXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
J2-C
J22-C
J2-C
J22-C
J2-C
J22-C
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
Filter units
J24
J24
J24
J4
J4
J4
DIV0
DIV0
DIV0
J25
J25
J25
DIV1
DIV1
DIV1
J5
J5
J5
J26
J26
J26
J6
J6
J6
J11
J11
J11
J31
J31
J31
J7
J7
J7
J28
J28
J28
J8
J8
J8
FAC4 J1
J20
J2 J3
J21
J4 J5
J22
J6 J7
J23
J8 J9
J24
J10 J11
J25
J12
SEC-B
J13
J26
DS1
J14
J27
J16 J17
J28 J29
J18 J19
Blank
CBs
Blank
CB5-J16
ESD
J1
CB1-J1-J2-J3
J2 J3
CB2-J4-J5-J6
J4
D
IN
J
J13
C
1
H
OUT 2
B
3
F
4
J5
PDP
A
5
E
6
J6 J7 J8
C
7
F
8
J14
B
E
9
10
A
11
D
12
J9 J10 J11
CB4-J10-J11-J12
J12
GREEN = NORMAL
RED = FAULT
1 2 3 4 5 6 7 8 9 10 11 12
CB5-J16
RF IN RF IN RF IN J13 RF IN J14
RF IN RF IN
D C B A C B A
IN 1 3 5 7 9 11
ESD J H F E F E D
AMPs
Lucent Lucent Lucent Lucent Lucent Lucent Lucent Lucent Lucent Lucent
L-ETH GIG-E
TX ON TX ON TX ON TX ON TX ON TX ON
U-ETH
TX2 TX2 TX2 TX2 TX2 TX2
GIG-E
TONE TONE TONE TONE TONE TONE
STAT
FAIL FAIL
MVM Load MVM Load STAT STAT STAT STAT STAT STAT
TIM 1
ACT ACT
Circuit packs
TX1-ON TX1-ON TX1-ON TX1-ON TX1-ON TX1-ON
L4 L3
RC1 RC1 RC1 RC1 RC1 RC1
L6 L5
L8 L7
RX1 RX1 RX1 RX1 RX1 RX1
J9
J17
15.00 MHz 15.00 MHz
J13 J12 OUT ø OUT ø
J7 J8 J1
J3 J14 J6
J16
IOU JTAG
J18
Cab.AI. UDRV
J4
422 Bus
J5
15.00 MHz
OUT 1
OMA
OM FAIL
RDY
15.00 MHz
OUT 1
OMQ
FAIL
RDY 5V
3.3V
FAIL
RDY
CPC-A
48V
FAIL
RDY
5V
3.3V
CPC-A
48V
CPCs FAIL
RDY
15V
8V
1.5V
CPC-B
48V
15V
8V
1.5V
FAIL
RDY
CPC-B
48V
Shelves
The Macrocell Indoor contains the following shelves:
• Filter shelf
• Amplifier shelf
“Note”: The amplifier shelf might be replaced by blanking plates for Multiple
Carrier Power Amplifier (MCPA) configurations.
• Digital shelf
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-5
Issue 1, August 2007 See notice on first page
Node B mechanical structure Mechanical structure of the Lucent UMTS Macrocell
Indoor
Shelf Components
Filter shelf The filter shelf contains the following components:
• Filter panels
• Filter Access Card (FAC)
• Circuit Breakers (CBs)
• E1/T1 Secondary Protection (SEC-B)
Amplifier shelf The amplifier shelf contains the following components:
• Amplifier modules (AMPs)
• Splitters and combiners, if required
• Power Distribution Panel (PDP)
• Fan tray (configured for amplifier shelf position)
• Blanking modules.
Additional information:
The amplifier shelf might be replaced by blanking plates
for MCPA configurations. In that case the output signals
from the radio units are routed via the hatchplate to the
external amplifiers.
Digital shelf The digital shelf contains the following components:
• Circuit packs,
comprising the following units:
– Universal Radio Controller (URC)
– UMTS Channel Units (UCUs)
– Common Timing Unit (CTU)
– Multi-Carrier Radios (MCRs).
• Blanking modules
• Input Output Unit (IOU)
• Oscillator Modules (OMs)
• Common Power Converters (CPCs)
• Fan tray (configured for digital shelf position). This
fan tray is omitted in case of “Single Fan Tray”
configuration.
....................................................................................................................................................................................................................................
3-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Mechanical structure of the Lucent UMTS Macrocell
Indoor
Receiver preamplifiers
Low Noise Amplifiers (LNAs) can be used as receiver preamplifiers in the various
frequency ranges. Depending on frequency ranges and mounting options these LNAs
are variously denoted.
The DxTMAs are optional Tower Mounted Amplifiers (could also be mounted on a
wall) and provide two independent pre-amplification branches.
Top view
At the top of the Macrocell Indoor external connections are made. Besides the earth
connectors three connector areas can be distinguished:
RF
connectors
Hatch
Power
plate
connectors
Earth
connectors
Legend:
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-7
Issue 1, August 2007 See notice on first page
Node B mechanical structure
1 2 3
Filter Panels
Filter shelf
4 5 6
CB FAC
Fan tray
Amplifier Modules
Amplifier shelf
1 2 3 4 5 6 7 8 9 10 11 12
PDP
Fan tray
MCR
MCR
MCR
MCR
MCR
MCR
URC
URC
URC
URC
UCU
UCU
UCU
UCU
UCU
UCU
UCU
UCU
UCU
UCU
UCU
UCU
CTU
CTU
Digital shelf
1 2 3 4 1 2 3 4 5 6 1 2 1 2 3 4 5 6 7 8 9 10 11 12
OM CPCA CPCB
IOU
1 2 1 2 3 4 5 6 7 8
...................................................................................................................................................................................................................................
3-8 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Component numbering in the Lucent UMTS Macrocell
Indoor
This figure is an example for a dual-band configured UMTS Node B. For single-band
configurations, only the corresponding MCR, UCU, filters and amplifier modules are
equipped. For Single Fan Tray configurations, the digital shelf fan tray is omitted, the
amplifier modules are located directly above the digital shelf and the PDP is located
above the amplifier shelf fan tray.
Important! The following sections only list components of which there can be
more than one in the Macrocell Indoor.
Component Numbering
Filter panels The filter panels are numbered from left to right, starting
with the upper row, from 1 to 3 and continuing in the
lower row from 4 to 6. The upper row is used for 1900
MHz or 2100 MHz, the lower row for 850 MHz filters.
Component Numbering
Amplifier Modules The Amplifier Modules are numbered from left to right,
from 1 to 12. Slots are alternatively assigned in pairs to
2100/1900 MHz and 850 MHz amplifiers: slots 1/2, 5/6
and 9/10 for 2100/1900 MHz, slots 3/4, 7/8 and 11/12 for
850 MHz.
Component Numbering
URC The Universal Radio Controllers (URC) are numbered
from left to right, from 1 to 4.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-9
Issue 1, August 2007 See notice on first page
Node B mechanical structure Component numbering in the Lucent UMTS Macrocell
Indoor
Component Numbering
UCU The UMTS Channel Units (UCU) are numbered from left
to right, from 1 to 6 (in the left part) and from 7 to 12
(in the right part). The UCUs are pooled resources for 2
groups of 6 UCUs. It is recommended to populate the
UCUs in consecutive order, starting with “1”.
CTU The Common Timing Unit(s) (CTU) are numbered from
left to right, 1 and 2.
MCR The Multi-Carrier Radios (MCR) are numbered from left
to right, from 1 to 6. Slots 1 to 3 are assigned for
2100/1900 MHz radios, slots 4 to 6 are assigned to 850
MHz radios.
OM The Oscillator Module(s) (OM) are numbered from the
left to the right, 1 and 2.
CPC The Common Power Converters (CPC) are numbered
from left to right, from 1 to 4 (CPC-A) and from 5 to 8
(CPC-B).
....................................................................................................................................................................................................................................
3-10 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides the mechanical structure diagrams and component numbering of
the Lucent UMTS Macrocell Compact Indoor.
Related information
For more information about the Lucent UMTS Macrocell Compact, refer to:
• Lucent UMTS Macrocell Compact Technical Description for +24V, 401-382-921.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-11
Issue 1, August 2007 See notice on first page
Node B mechanical structure
Inside view
View of the Lucent UMTS Macrocell Compact Indoor with open door (3s1c
configuration without Tx diversity, minimum UCU population):
Lucent Technologies
J41
J41
J41
TEST PULSE
LUCENT-SN XXXXXXXXXXX
LUCENT-SN XXXXXXXXXXX
LUCENT-SN XXXXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
J20
J22-C
J22-C
J22-C
J1
J2-C
J2-C
J2-C
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
J2
Filter units
J3
TEST CLOCK
J4
J26 J25 J24
J4
J4
J21
J5
DIV0
DIV0
DIV0
DIV1
DIV1
DIV1
J5
J5
J5
J22
J6
Blank
J6
J6
J6
J7
J23
J8
J11
J11
J11
J31
J31
J31
J7
J7
J7
J9
J24
J10
J25
J28
J28
J28
J8
J8
J8
J11
Filter shelf
J12
J13
J26
DS1
J14
J16
J27
15MHz IN 15MHz OUT
J28
Blank
J17
J29
I2C IN
J18
I2C OUT
J19
CBs
UTDU
FAC
Blank
CB2
CB1
J1
J3
J7
J2
AMPs
(rear venting)
Hybrid shelf
RDY
FAIL
Fan
OMR
CPCs OMR
15.00 MHz
15.00 MHz
OUT ø
OUT 1
C P C -B
4 8V
RDY
FAIL
8V
15V
1.5V
C P C -A
4 8V
RDY
FAIL
5V
3.3V
U
U
D
D
T
T
1
2
Lucent
BIAS-T
CTU
15.00
OUT
MHz
RDY
NVM
OM
FAIL
FLY
EX
FAIL
Tx O N /O FF
Lucent
U C R 2100
BN J 26
Tx2
Tx1
R x1
R x2
P1.5
BarCodeArea
PDPs
Fail
R eady
Tx O N
Fault
Tx O N /O FF
Lucent
U C R 2100
BN J 26
Tx1
Tx2
R x1
R x2
P1.5
BarCodeArea
Tx O N
Fail
R eady
Fault
Tx O N /O FF
Lucent
U C R 2100
BN J 26
Tx1
Tx2
R x1
R x2
P1.5
BarCodeArea
Tx O N
Fail
R eady
Fault
15 MHz
IN (2)
M VM Load
Lucent
U C U 48v
BNJ 24
P1.5
BarCodeArea
FAIL
AC T
15 MHz
M VM Load
Lucent
IN (1)
U C U 48v
BN J 24
P1.5
BarCodeArea
FAIL
AC T
Circuit packs
OUT (2)
M VM Load
15 MHz
Lucent
U C U 48v
BNJ 24
P1.5
BarCodeArea
FAIL
AC T
3
4
GREEN = NORMAL
0 12
7 65
RED = FAULT
M VM Load
Lucent
OUT (1)
U C U 48v
15 MHz
9
8
BN J 24
P1.5
BarCodeArea
FAIL
AC T
C
A
B
L1
NVM
RDY
L2
FAIL
L3
L4
HIOU
FAN TRAY POWER
FAN TRAY
Shelves
The Lucent Macrocell Compact Indoor contains the following shelves:
• Filter shelf
• Hybrid shelf.
Shelf Components
Filter shelf • Filter panels
• Filter Access Card (FAC)
• Circuit Breakers (CBs)
A one unit (1 U) tall space below the filters is available
to mount customer supplied facilities equipment.
...................................................................................................................................................................................................................................
3-12 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Mechanical structure of the Lucent UMTS Macrocell
Compact Indoor
Shelf Components
Hybrid shelf • Amplifier Modules (AMPs)
• Splitters and combiners, if required
• Power Distribution Panel (PDP-1)
• Circuit packs,
comprising:
– Universal Radio Controller (URC)
– UMTS Channel Units (UCUs)
– Common Timing Unit (CTU)
– Multi-Carrier Radio (MCR)
• Hybrid Input Output Unit (HIOU)
• Oscillator Module (OM)
• Common Power Converter (CPC)
• Fan tray
• Blanking modules.
Optional components
The following optional component can be installed in the Lucent UMTS Macrocell
Compact Indoor:
• Power Distribution Panel (PDP-3) can be mounted directly to the right of the
digital section of the hybrid shelf, when more than three Amplifier Modules are
installed.
Installation options
Installation options for the Lucent UMTS Macrocell Compact Indoor:
• Basic plinth, can be used as a mounting pedestal for the cabinet.
• battery plinth containing a single string of four backup batteries.
View of the installation options for the Lucent UMTS Macrocell Compact Indoor:
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-13
Issue 1, August 2007 See notice on first page
3-14
Top view
DIV0
LUCENT-CC XXXXXXXXX
J8
J11
LUCENT-SN XXXXXXXXXXX
J20
J1
RED = FAULT
TEST PULSE
J2-C
J6 J5 J4
J2
GREEN = NORMAL
J3
J7 RF ON TTLNA LNA
J4
J21
TEST CLOCK
J5
J41
J22
0 12
RF ON TTLNA LNA
J6
9 3
8 4 J28
7 65
J7
J31
Lucent Technologies
J23
J8
J9
J24
J10
J25
DIV1
J11
J12
DIV0
LUCENT-CC XXXXXXXXX
J13
U C U 48v U C U 48v U C U 48v U C U 48v U C R 2100 U C R 2100 U C R 2100
URC P1.5 P1.5 P1.5 P1.5 P1.5 P1.5 P1.5 CTU J8
BN J 24 BNJ 24 BN J 24 BN J 24 BNJ 26 BN J 26 BNJ 26 J11
LUCENT-SN XXXXXXXXXXX
J26
Lucent Lucent Lucent
DS1
Lucent Lucent Lucent Lucent Lucent Lucent
J14
J2-C
J6 J5 J4
J16
J27
J7 RF ON TTLNA LNA
J28
J17
T
D
U
1 FAIL
FAIL
J29
RDY
J41
Tx1 Tx1 Tx1 RDY
J18
NVM Tx O N /O FF Tx O N /O FF Tx O N /O FF J28
U
I2C IN
2
RDY C P C -A C P C -B J31
4 8V 4 8V J26 J25 J24 J22-C
L1 Tx2 Tx2 Tx2
J19
L2 15.00
I2C OUT
MHz
L3 R eady R eady R eady
OUT
FAIL FAIL FAIL FAIL
Tx O N Tx O N Tx O N
L4 M VM Load M VM Load M VM Load M VM Load
Fault Fault Fault
AC T ACT AC T ACT
FAIL
Fail Fail Fail DIV1
UTDU
NVM
RDY
A DIV0
OM LUCENT-CC XXXXXXXXX
FAIL
15.00 MHz
FLY OUT ø
R x1 R x1 R x1 EX J2 J1 J8
J11
LUCENT-SN XXXXXXXXXXX
B
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
J2-C
BIAS-T J6 J5 J4
15.00 MHz FAIL
OUT 1
C RDY
R x2 R x2 R x2
J7 RF ON TTLNA LNA
OMR
J41
J3 RF ON TTLNA LNA
FAN TRAY FILTER SHELF J7 J28
15 MHz 15 MHz 15 MHz 15 MHz
OUT (1) OUT (2) IN (1) IN (2) J31
J26 J25 J24 J22-C
basic plinth
FAN TRAY POWER FAN TRAY POWER
with optional
DIV1
Indoor cabinet
J27 J26 J25 TEST CLOCK TEST PULSE
15MHz IN 15MHz OUT J24 J23 J22
DS1
I2C OUT I2C IN
CB1 J29 J28 J21 J20
UTDU
J19 J18 J17 J16 J14 J13 J12 J11 J10 J9 J8 J7 J6 J5 J4 J3 J2 J1
CB2
DIV0
LUCENT-CC XXXXXXXXX
J8
J11
LUCENT-SN XXXXXXXXXXX
J20
J1
RED = FAULT
TEST PULSE
J2-C
J6 J5 J4
J2
GREEN = NORMAL
J3
J7 RF ON TTLNA LNA
J4
J21
TEST CLOCK
J5
J41
J22
0 12
RF ON TTLNA LNA
J6
9 3
8 4 J28
7 65
J7
J31
Lucent Technologies
J24
J10
J25
DIV1
J11
J12
DIV0
LUCENT-CC XXXXXXXXX
J13
J2-C
J6 J5 J4
J16
J27
J7 RF ON TTLNA LNA
J28
J17
T
D
U
1 FAIL
FAIL
J29
RDY
J41
Tx1 Tx1 Tx1 RDY
15MHz IN 15MHz OUT
5V
15V
3.3V
FAIL 8V RF ON TTLNA LNA
T 1.5V
D
J18
NVM Tx O N /O FF Tx O N /O FF Tx O N /O FF J28
U
I2C IN
2
RDY C P C -A C P C -B J31
4 8V 4 8V J26 J25 J24 J22-C
L1 Tx2 Tx2 Tx2
J19
L2 15.00
I2C OUT
MHz
L3 R eady R eady R eady
OUT
FAIL FAIL FAIL FAIL
Tx O N Tx O N Tx O N
L4 M VM Load M VM Load M VM Load M VM Load
Fault Fault Fault
AC T ACT AC T AC T
FAIL
Fail Fail Fail DIV1
UTDU
NVM
RDY
A DIV0
OM LUCENT-CC XXXXXXXXX
FAIL
15.00 MHz
FLY OUT ø
R x1 R x1 R x1 EX J2 J1 J8
J11
LUCENT-SN XXXXXXXXXXX
B
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
J2-C
BIAS-T J6 J5 J4
15.00 MHz FAIL
OUT 1
C RDY
R x2 R x2 R x2
J7 RF ON TTLNA LNA
OMR
J41
J3 RF ON TTLNA LNA
FAN TRAY FILTER SHELF J7 J28
15 MHz 15 MHz 15 MHz 15 MHz
OUT (1) OUT (2) IN (1) IN (2) J31
J26 J25 J24 J22-C
FAN TRAY POWER FAN TRAY POWER
with optional
battery plinth
Indoor cabinet
J27 J26 J25 TEST CLOCK TEST PULSE
15MHz IN 15MHz OUT J24 J23 J22
DS1
I2C OUT I2C IN
CB1 J29 J28 J21 J20
UTDU
J19 J18 J17 J16 J14 J13 J12 J11 J10 J9 J8 J7 J6 J5 J4 J3 J2 J1
CB2
Alcatel-Lucent - Proprietary
Besides the earth connectors three connector areas can be distinguished:
At the top of the Lucent Macrocell Compact Indoor external connections are made.
....................................................................................................................................................................................................................................
Node B mechanical structure Mechanical structure of the Lucent UMTS Macrocell
Compact Indoor
RF connectors
Battery cable
port
1 2 3 4 5 6
GPS
connector
E1/T1
ALARMS (0-7)
(1-4)
E1/T1
(5-8)
ETR
SECB 1
Earthing points
RET
ALARMS (16-29)
SECB 1 RELAY (2-3)
Hatch plate
(e.g. T1/E1 and alarms)
Legend:
Receiver preamplifiers
Low Noise Amplifiers (LNAs) can be used as receiver preamplifiers in the various
frequency ranges. Depending on frequency ranges and mounting options these LNAs
are variously denoted.
The DxTMAs are optional Tower Mounted Amplifiers (could also be mounted on a
wall) and provide two independent pre-amplification branches.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-15
Issue 1, August 2007 See notice on first page
Node B mechanical structure
Filter Panels
1 2 3
Blank FAC
6
5
Amplifier 4
Modules 3
2
1
Hybrid Fan Tray
(B) 2
CPC
OM
(B) 1
(A) 2 (A) 1
Hybrid shelf
CTU 2
1
PDP
3
MCR 2
1
4
3
UCU 2
1
2
URC 1
HIOU 1 2
Power shelf
Important! The following sections only list components of which there can be
more than one in the Lucent Macrocell Compact.
Component Numbering
Filter panels Left to right, from 1 to 3.
...................................................................................................................................................................................................................................
3-16 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Component numbering in the Lucent UMTS Macrocell
Compact Indoor
Component Numbering
Amplifier Modules (AMP) From bottom to top, 1 to 6.
Universal Radio From bottom to top, 1 to 2.
Controllers (URCs)
UMTS Channel Units From bottom to top, 1 to 4.
(UCUs)
Multi-Carrier Radios From bottom to the top, 1 to 3.
(MCRs)
Common Timing Units From bottom to top, 1 and 2.
(CTUs)
Common Power Converters From right to left, 1 to 2.
Type A (CPC-A)
Common Power Converters From bottom to top, 1 to 2.
Type B (CPC-B)
Power Distribution Panel The first, PDP-1, is integrated into the Hybrid Shelves’
(PDP) Power Distribution Assembly (PDA).
The optional , PDP-3, can be mounted directly to the
right side of the hybrid shelf when more than three
AMPs are installed.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-17
Issue 1, August 2007 See notice on first page
Node B mechanical structure
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides the mechanical structure diagrams and component numbering of
the UMTS Lucent Macrocell Compact Outdoor.
Related information
For more information about the Lucent UMTS Macrocell Compact, refer to:
• Lucent UMTS Macrocell Compact Technical Description, 401-382-921.
Contents
...................................................................................................................................................................................................................................
3-18 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure
Inside view
View of the Lucent UMTS Macrocell Compact Outdoor with door removed (3s1c
configuration without Tx diversity, minimum UCU population):
J41
J41
J41
LUCENT-SN XXXXXXXXXXX
LUCENT-SN XXXXXXXXXXX
LUCENT-SN XXXXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
J22-C
J22-C
J22-C
J2-C
J2-C
J2-C
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
Blank
Filter units
J26 J25 J24
J4
J4
DIV0
DIV0
DIV0
DIV1
DIV1
DIV1
J5
J5
J5
J6
J6
J6
J11
J11
J11
J31
J31
J31
J7
J7
J7
J28
J28
J28
J8
J8
J8
Filter shelf
Blank
CBs
FAC
CB2
CB1
Blank
J1
J3
J7
J2
Common I/O panel
Heat exchanger
AMPs
(optional)
Fan Tray
Heater (optional)
RDY
FAIL
Hybrid shelf
OMR
15.00 MHz
15.00 MHz
OUT ø
OUT 1
CPCs OMR
C P C -B
4 8V
RDY
FAIL
8V
15V
1.5V
C P C -A
4 8V
RDY
FAIL
5V
3.3V
U
U
D
D
T
T
1
2
Lucent
BIAS-T
CTU
15.00
OUT
MHz
RDY
FAIL
FLY
EX
OM
NVM
FAIL
Tx O N /O FF
Lucent
U C R 2100
BN J 26
Tx2
Tx1
R x1
R x2
P1.5
BarCodeArea
Fail
R eady
Tx O N
Fault
Tx O N /O FF
Lucent
U C R 2100
BN J 26
Tx1
Tx2
R x1
R x2
P1.5
BarCodeArea
Fail
Tx O N
R eady
Fault
PDP
Tx O N /O FF
Lucent
U C R 2100
BN J 26
Tx1
Tx2
R x1
R x2
P1.5
BarCodeArea
Fail
Tx O N
R eady
Fault
15 MHz
IN (2)
M VM Load
Lucent
U C U 48v
BN J 24
P1.5
BarCodeArea
FAIL
AC T
15 MHz
M VM Load
Lucent
IN (1)
U C U 48v
BN J 24
P1.5
BarCodeArea
Circuit packs
FAIL
AC T
OUT (2)
M VM Load
15 MHz
Lucent
U C U 48v
BN J 24
P1.5
BarCodeArea
FAIL
AC T
3
4
GREEN = NORMAL
0 12
7 65
RED = FAULT
M VM Load
Lucent
OUT (1)
U C U 48v
15 MHz
9
8
BN J 24
P1.5
BarCodeArea
FAIL
AC T
Lucent
URC
C
A
B
L1
NVM
RDY
L2
FAIL
L3
L4
HIOU
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-19
Issue 1, August 2007 See notice on first page
Node B mechanical structure Mechanical structure of the Lucent UMTS Macrocell
Compact Outdoor
Shelves
The Lucent Macrocell Compact Outdoor contains the following shelves:
• Filter shelf
• Hybrid shelf
• Power shelf (optional)
• Connection area.
Shelf Components
Filter shelf • Filter panels
• Filter Access Card (FAC)
• Circuit Breakers (CBs)
a one unit (1 U) high space, below the filters, is
available to mount customer supplied facilities
equipment.
Hybrid shelf • Amplifier Modules (AMPs)
• splitters and combiners, if required
• Power Distribution Panel (PDP-1)
• circuit packs,
comprising:
– Universal Radio Controller (URC)
– UMTS Channel Units (UCUs)
– Common Timing Unit (CTU)
– Multi-Carrier Radio (MCR)
• Hybrid Input Output Unit (HIOU)
• Oscillator Module (OM)
• Common Power Converter (CPC)
• fan tray
• blanking modules.
• heater (optional)
• PDP-3 (optional)
Power shelf (optional) • Four rectifiers
• power controller
• heater switch.
....................................................................................................................................................................................................................................
3-20 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
401-382-290R04.03
Issue 1, August 2007
•
•
•
•
•
Connection area
Installation options
DIV0
LUCENT-CC XXXXXXXXX
J8
J11
LUCENT-SN XXXXXXXXXXX
J20
J1
RED = FAULT
TEST PULSE
J2-C
J6 J5 J4
J2
GREEN = NORMAL
J3
J7 RF ON TTLNA LNA
J4
J21
TEST CLOCK
J41
J5
J22
0 12
RF ON TTLNA LNA
J6
9 3
8 4 J28
7 65
J7
J31
J26 J25 J24 J22-C
J23
Node B mechanical structure
J8
Receiver preamplifiers
J9
J24
J10
J25
DIV1
J11
J12
DIV0
LUCENT-CC XXXXXXXXX
J13
U C U 48v U C U 48v U C U 48v U C U 48v U C R 2100 U C R 2100 U C R 2100
URC P1.5 P1.5 P1.5 P1.5 P1.5 P1.5 P1.5 CTU J8
BN J 24 BN J 24 BNJ 24 BN J 24 BN J 26 BN J 26 BN J 26 J11
LUCENT-SN XXXXXXXXXXX
J26
Lucent Lucent Lucent
DS1
Lucent Lucent Lucent Lucent Lucent
J14
Lucent
J2-C
J6 J5 J4
J16
J27
J7 RF ON TTLNA LNA
J28
J17
T
D
U
1 FAIL
FAIL J41
J29
RDY
RDY
Tx1 Tx1 Tx1
J18
NVM Tx O N /O FF Tx O N /O FF Tx O N /O FF J28
U
I2C IN
2
RDY C P C -A C P C -B J31
4 8V 4 8V J26 J25 J24 J22-C
L1 Tx2 Tx2 Tx2
J19
L2 15.00
I2C OUT
MHz
L3 R eady R eady R eady OUT
FAIL FAIL FAIL FAIL
Tx O N Tx O N Tx O N
L4 M VM Load M VM Load M VM Load M VM Load
Fault Fault Fault
AC T AC T ACT AC T
FAIL
Fail Fail Fail DIV1
UTDU
NVM
RDY
A
OM
DIV0
LUCENT-CC XXXXXXXXX
FAIL
15.00 MHz
FLY OUT ø J8
R x1 R x1 R x1 EX J2 J1
J11
LUCENT-SN XXXXXXXXXXX
B
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
J2-C
BIAS-T J6 J5 J4
15.00 MHz FAIL
OUT 1
C RDY
basic plinth
R x2 R x2 R x2
J7 RF ON TTLNA LNA
with optional
OMR
J41
J3 RF ON TTLNA LNA
FAN TRAY FILTER SHELF J7 J28
15 MHz 15 MHz 15 MHz 15 MHz
OUT (1) OUT (2) IN (1) IN (2) J31
J26 J25 J24 J22-C
FAN TRAY POWER FAN TRAY POWER
Outdoor cabinet
DIV1
CB1
CB2
J8
J11
LUCENT-SN XXXXXXXXXXX
J20
J1
RED = FAULT
TEST PULSE
J2-C
J6 J5 J4
J2
GREEN = NORMAL
J3
J7 RF ON TTLNA LNA
J4
J21
TEST CLOCK
J41
J5
J22
0 12
RF ON TTLNA LNA
J6
9 3
8 4 J28
7 65
J7
J31
J26 J25 J24 J22-C
J23
J8
J9
J24
J10
J25
DIV1
J11
J12
DIV0
LUCENT-CC XXXXXXXXX
J13
Lucent
J2-C
J6 J5 J4
J16
J27
J7 RF ON TTLNA LNA
J28
J17
T
D
U
1 FAIL
FAIL J41
J29
RDY
RDY
Tx1 Tx1 Tx1
15MHz IN 15MHz OUT
5V
15V
3.3V
Alcatel-Lucent - Proprietary
FAIL 8V RF ON TTLNA LNA
T 1.5V
D
J18
NVM Tx O N /O FF Tx O N /O FF Tx O N /O FF J28
U
I2C IN
2
RDY C P C -A C P C -B J31
4 8V 4 8V J26 J25 J24 J22-C
L1 Tx2 Tx2 Tx2
J19
L2 15.00
I2C OUT
MHz
L3 R eady R eady R eady OUT
FAIL FAIL FAIL FAIL
Tx O N Tx O N Tx O N
L4 M VM Load M VM Load M VM Load M VM Load
Fault Fault Fault
AC T AC T AC T AC T
FAIL
Fail Fail Fail DIV1
UTDU
NVM
RDY
A
OM
DIV0
LUCENT-CC XXXXXXXXX
FAIL
15.00 MHz
FLY OUT ø J8
R x1 R x1 R x1 EX J2 J1
J11
LUCENT-SN XXXXXXXXXXX
B
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
BarCodeArea
J2-C
BIAS-T J6 J5 J4
15.00 MHz FAIL
OUT 1
C RDY
R x2 R x2 R x2
J7 RF ON TTLNA LNA
with optional
OMR
J41
battery plinth
J3 RF ON TTLNA LNA
FAN TRAY FILTER SHELF J7 J28
15 MHz 15 MHz 15 MHz 15 MHz
OUT (1) OUT (2) IN (1) IN (2) J31
J26 J25 J24 J22-C
FAN TRAY POWER FAN TRAY POWER
Outdoor cabinet
DIV1
CB1
CB2
Installation options for the Lucent Macrocell Compact Outdoor:
Space for power and signalling cables entering the cabinet from below.
View of the installation options for the Lucent Macrocell Compact Outdoor:
Low Noise Amplifiers (LNAs) can be used as receiver preamplifiers in the various
frequency ranges. Depending on frequency ranges and mounting options these LNAs
3-21
Compact Outdoor
Mechanical structure of the Lucent UMTS Macrocell
....................................................................................................................................................................................................................................
Node B mechanical structure Mechanical structure of the Lucent UMTS Macrocell
Compact Outdoor
The DxTMAs are optional Tower Mounted Amplifiers (could also be mounted on a
wall) and provide two independent pre-amplification branches.
....................................................................................................................................................................................................................................
3-22 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure
Filter Panels
1 2 3
Filter shelf
Facilities
Common I/O panel
FAC
6
5
Amplifier 4
Modules 3
2
1
Hybrid Fan Tray
(B) 2
OM
CPC
(B) 1
(A) 2 (A) 1
Hybrid shelf
2 PDP
CTU 1
3
MCR 2
Cable I/O area
1
4
3
UCU 2
1
2
URC 1
HIOU 1 2
1 2
Rectifiers Power shelf
3 4
Important! The following sections only list those components that are available in
the Lucent Macrocell Compact more than once.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-23
Issue 1, August 2007 See notice on first page
Node B mechanical structure Component numbering in the Lucent UMTS Macrocell
Compact Outdoor
Component Numbering
Filter panels The dual duplexer panels are numbered from left to right,
from 1 to 3.
Component Numbering
Amplifier Modules (AMP) From bottom to top, 1 to 6.
Universal Radio From bottom to top, 1 to 2.
Controllers (URCs)
UMTS Channel Units From bottom to top, 1 to 4.
(UCUs)
Multi-Carrier Radios From bottom to the top, 1 to 3.
(MCRs)
Common Timing Units From bottom to top, 1 and 2.
(CTUs)
Common Power Converters From right to left, 1 to 2.
Type A (CPC-A)
Common Power Converters From bottom to top, 1 to 2.
Type B (CPC-B)
Power Distribution Panel The first, PDP-1, is integrated into the Hybrid Shelves’
(PDP) Power Distribution Assembly (PDA).
The optional , PDP-3, can be mounted directly to the
right side of the hybrid shelf when more than three
AMPs are installed.
Power shelf, for AC power top left to bottom right, 1 to 4
applications
....................................................................................................................................................................................................................................
3-24 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides the mechanical structure diagrams and component numbering of
the Lucent UMTS Modular Cell.
Related information
For more information about the Lucent UMTS Modular Cell, refer to
• Lucent UMTS Modular Cell Outdoor +24 V Technical Description, 401-382-720.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-25
Issue 1, August 2007 See notice on first page
Node B mechanical structure
Solar shields
...................................................................................................................................................................................................................................
3-26 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Mechanical structure of the UMTS Modular Cell Outdoor
Fresh Air
Filter Intake
Front view Rear view
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-27
Issue 1, August 2007 See notice on first page
Node B mechanical structure Mechanical structure of the UMTS Modular Cell Outdoor
Filter units
HPDA
EFIM
Filter shelf
Blank
J1 J2 J3 J4 J5 J6
CBs FAC
CB1 CB2
J7
-48VDC
Fan
(rear venting)
Amplifier shelf
PAMs Battery
compartment
CB5-J16
J16
ESD
J1 J2 J3 J4
D C
J13
IN 1
J H
PDP
B
3
F
J5
A
5
E
J6 J7 J8
C
7
F
J14
B
E
9
A
J9
11
D
J10 J11 J12
ACF
PMN
PMJ
TEMP
FUSE
GREEN = NORMAL
Fan
RED = FAULT
(Front venting)
DC OK
DC OK
DC OK
DC OK
AC OK
AC OK
AC OK
AC OK
Rectifiers
P1.5 P1.5
BNJ 24 BNJ 24
Digital shelf
TECTROL
TECTROL
TECTROL
T Total Power Solutions
MADE IN CANADA
MADE IN CANADA
MADE IN CANADA
I/P: 100-240 VAC 18A
1413T031600216-2
1413T031600216-2
1413T031600216-2
O/P: 1350W MAX.
P/N: TC91S-1413
P/N: TC91S-1413
P/N: TC91S-1413
50/60Hz
50/60Hz
50/60Hz
50/60Hz
T
D
U
T
1
Tx1 Tx1 Tx1
FAIL
T
NVM D
U Tx ON/OFF Tx ON/OFF Tx ON/OFF
Circuit packs
2
RDY
L1 Tx2 Tx2 Tx2
L2 15.00
MHz
L3 OUT Ready Ready Ready
FAIL FAIL
Tx ON Tx ON Tx ON
L4 MVM Load MVM Load
DC OK
DC OK
DC OK
DC OK
AC OK
AC OK
AC OK
AC OK
RDY
A
OM
FAIL
FLY
EX Rx1 Rx1 Rx1
Rectifiers
BIAS-T
C
Rx2 Rx2 Rx2
T TECTROL
T TECTROL
TECTROL
TECTROL
Total Power Solutions
MADE IN CANADA
MADE IN CANADA
MADE IN CANADA
I/P: 100-240 VAC 18A
1413T031600216-2
1413T031600216-2
1413T031600216-2
O/P: 1350W MAX.
P/N: TC91S-1413
P/N: TC91S-1413
P/N: TC91S-1413
50/60Hz
50/60Hz
50/60Hz
50/60Hz
T
J9
IOU OM CPCs
J17
15.00 MHz 15.00 MHz
J13 J12 OUT ø OUT ø
J7 J8 J1
AC PDA
J3 J14 J6
J16
J18
15.00 MHz FAIL 15.00 MHz FAIL FAIL
OUT 1 FAIL RDY RDY FAIL FAIL
J4 OUT 1
J5 RDY RDY 5V 5V
RDY RDY
15V 15V
3.3V 3.3V
8V 8V
1.5V 1.5V
JTAG Cab.AI. UDRV 422 Bus
....................................................................................................................................................................................................................................
3-28 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Mechanical structure of the UMTS Modular Cell Outdoor
J41
J41
J41
LUCENT-SN XXXXXXXXXXXX
LUCENT-SN XXXXXXXXXXXX
LUCENT-SN XXXXXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
J2-C
J22-C
J2-C
J22-C
J2-C
J22-C
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
Filter units
J24
J24
J24
J4
J4
J4
DIV0
DIV0
DIV0
J25
J25
J25
DIV1
DIV1
DIV1
J5
J5
J5
J26
J26
J26
J6
J6
J6
J11
J11
J11
J31
J31
J31
J7
J7
J7
J28
J28
J28
J8
J8
J8
Filter shelf
HPDA
EFIM
J41
J41
J41
LUCENT-SN XXXXXXXXXXXX
LUCENT-SN XXXXXXXXXXXX
LUCENT-SN XXXXXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
LUCENT-CC XXXXXXXXX
J2-C
J22-C
J2-C
J22-C
J2-C
J22-C
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
RF ON TTLNA LNA
J24
J24
J24
J4
J4
J4
Filter units
DIV0
DIV0
DIV0
J25
J25
J25
DIV1
DIV1
DIV1
J5
J5
J5
J26
J26
J26
J6
J6
J6
J11
J11
J11
J31
J31
J31
J7
J7
J7
J28
J28
J28
J8
J8
J8
FAC
SEC-B
J1 J2 J3 J4 J5 J6 J7 J8 J9 J10 J11 J12 J13 J14 J16 J17 J18 J19
J20 J21 J22 J23 J24 J25 J26 J27 J28 J29
DS1
CBs Blank
GREEN = NORMAL
9
0 12
RED = FAULT
(rear venting)
8 4
7 65 AMPLIFIER, OUTDOOR CABINET
(Application per top-plate label)
Amplifier shelf
1 2 3 4 5 6 7 8 9 10 11 12
RF IN RF IN RF IN RF IN RF IN RF IN
Battery
PAMs compartment
RF OUT RF OUT RF OUT RF OUT RF OUT RF OUT
CB5-J16
ESD
J1
CB1-J1-J2-J3
J2 J3
CB2-J4-J5-J6
J4
D
IN
J
PDP
J13
C
1
H
OUT 2
B
3
F
4
J5
A
5
E
6
J6 J7 J8
C
7
F
8
J14
B
E
9
10
A
11
D
12
J9 J10 J11
CB4-J10-J11-J12
J12
Blank
GROWTH GROWTH ALARMS BATTERY GROWTH ALARMS
BD
PWR
ACF
PMJ
TEMP
FUSE
PMN
GREEN = NORMAL
RED = FAULT
DC OK
DC OK
DC OK
AC OK
AC OK
AC OK
AC OK
URC-II
UCU48v UCU48v CTU-II MCR1900 MCR1900 MCR1900 MCR1900 MCR1900 MCR1900
Rectifiers
Digital shelf
Lucent Lucent Lucent Lucent Lucent Lucent Lucent Lucent Lucent Lucent
TECTROL
T TECTROL
TECTROL
T TECTROL
T Total Power Solutions
MADE IN CANADA
MADE IN CANADA
MADE IN CANADA
I/P: 100-240 VAC 18A
1413T031600216-2
1413T031600216-2
1413T031600216-2
O/P: 1350W MAX.
P/N: TC91S-1413
P/N: TC91S-1413
P/N: TC91S-1413
50/60Hz
50/60Hz
50/60Hz
50/60Hz
L-ETH GIG-E
T
TX ON TX ON TX ON TX ON TX ON TX ON
Circuit packs
TX OFF TX OFF TX OFF TX OFF TX OFF TX OFF
U-ETH
TX2 TX2 TX2 TX2 TX2 TX2
GIG-E
TONE TONE TONE TONE TONE TONE
STAT
FAIL FAIL
MVM Load MVM Load
DC OK
DC OK
DC OK
DC OK
AC OK
AC OK
AC OK
AC OK
L4 L3
RC1 RC1 RC1 RC1 RC1 RC1
L6 L5
L8 L7
RX1 RX1 RX1 RX1 RX1 RX1
T TECTROL
TECTROL
T TECTROL
T Total Power Solutions
MADE IN CANADA
MADE IN CANADA
MADE IN CANADA
I/P: 100-240 VAC 18A
1413T031600216-2
1413T031600216-2
1413T031600216-2
O/P: 1350W MAX.
P/N: TC91S-1413
P/N: TC91S-1413
P/N: TC91S-1413
50/60Hz
50/60Hz
50/60Hz
50/60Hz
T
J9
J17
15.00 MHz 15.00 MHz
J13 J12 OUT ø OUT ø
J7 J8 J1
IOU J18
JTAG
J16
Cab.AI.
J3
UDRV
J14
J4
422 Bus
J6
J5
15.00 MHz
OUT 1
OM FAIL
RDY
15.00 MHz
OUT 1
FAIL
RDY
FAIL
RDY
5V
3.3V
5V
3.3V
FAIL
RDY
CPCs FAIL
RDY
15V
8V
1.5V
15V
8V
1.5V
FAIL
RDY
AC PDA
OMA OMQ CPC-A
48V
CPC-A
48V
CPC-B
48V
CPC-B
48V
Outdoor-specific components
The UMTS Modular Cell Outdoor provides the following outdoor-specific components:
• The Enhanced Facilities Interface Module (EFIM) carries the Punch-down
connectors for T1/E1 lines, User Alarms, RS485/422 and User Relays.
• AC-Rectifiers for DC conversion of the AC mains power supply
• The AC Power Distribution Assembly (ACPDA)
distributes the AC power to the
– AC-Rectifiers
– Cabinet Heaters
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-29
Issue 1, August 2007 See notice on first page
Node B mechanical structure Mechanical structure of the UMTS Modular Cell Outdoor
– Battery Heaters
– Convenience outlet.
• The battery compartment contains backup batteries for short-term AC mains failure
coverage and controlled shutdown.
• The High Power Distribution Assembly (HPDA) distributes the DC power from the
AC rectifiers or the internal backup batteries or the optional external batteries to
the shelves inside the cabinet.
Non integrated power option
If DC power supply is available on site, the power module, containing the controller,
the rectifiers and the ACPDA may be omitted. In this case the HPDA is replaced by a
Low Power Distribution Assembly (LPDA), providing fuses for the heat exchanger
fans and the cabinet light.
As no battery backup is necessary when DC power is supplied on site, the battery
compartment is accordingly replaced by a blanking plate.
If additionally AC power supply is available on site, an optional AC service kit
providing an AC mains outlet may be installed.
Shelves
The Modular Cell Outdoor contains the following shelves:
• Filter shelf
• Amplifier shelf
“Note”: The amplifier shelf might be replaced by blanking plates for Multiple
Carrier Power Amplifier (MCPA) configurations.
• Digital shelf.
Shelf Components
Filter shelf The filter shelf contains the following components:
• Filter panels
• Filter Access Card (FAC)
• Circuit Breakers (CB).
• E1/T1 or E3/T3 Secondary Protection (SEC-B)
....................................................................................................................................................................................................................................
3-30 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Mechanical structure of the UMTS Modular Cell Outdoor
Shelf Components
Amplifier shelf The amplifier shelf contains the following components:
• Power Amplifier Modules (PAM)
• Splitters and combiners, if required
• Power Distribution Panel (PDP)
• Fan tray (configured for amplifier shelf position)
• Blanking modules.
Additional information:
The amplifier shelf might be replaced by blanking plates
for MCPA configurations. In that case the output signals
from the radio units are routed via the hatchplate to the
external amplifiers.
Digital shelf The digital shelf contains the following components:
• Input Output Unit (IOU)
• Oscillator Modules (OM)
• Common Power Converter (CPC)
• Fan tray (configured for digital shelf position)
• Blanking modules
• Circuit packs.
The circuit packs consist of the following units:
• Universal Radio Controller (URC)
• UMTS Channel Units (UCU)
• Common Timing Unit (CTU)
• Multi-Carrier Radio (MCR).
Receiver preamplifiers
Low Noise Amplifiers (LNAs) can be used as receiver preamplifiers in the various
frequency ranges. Depending on frequency ranges and mounting options these LNAs
are variously denoted.
The DxTMAs are optional Tower Mounted Amplifiers (could also be mounted on a
wall) and provide two independent pre-amplification branches.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-31
Issue 1, August 2007 See notice on first page
Node B mechanical structure
1 2 3
HPDA
EFIM
Filter shelf
Filter Panels
4 5 6
CB FAC
Fan tray
Amplifier shelf
PDP
Controller and
interface card
1 2 1 2
Fan tray
Rectifiers
Digital shelf
3 4 3 4
1 2 3 4 1 2 3 4 5 6 1 2 1 2 3 4 5 6 7 8 9 10 11 12
Auxiliary Primary
shelf shelf
OM CPCA CPCB
IOU
1 2 1 2 3 4 5 6 7 8 AC PDA
Important! The following sections only list components of which there can be
more than one in the Modular Cell Outdoor for +24 V.
...................................................................................................................................................................................................................................
3-32 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Component numbering in the UMTS Modular Cell
Outdoor for +24 V
Component Numbering
Filter panels The filter panels are numbered from left to right, starting
with the upper row, from 1 to 3 and continuing in the
lower row from 4 to 6.
Component Numbering
Amplifier Modules The Amplifier Modules are numbered from left to right,
from 1 to 12.
Component Numbering
URC The Universal Radio Controllers (URC) are numbered
from left to right, from 1 to 4.
UCU The UMTS Channel Units (UCU) are numbered from left
to right, from 1 to 6 (in the left part) and from 7 to 12
(in the right part). The UCUs are pooled resources for 2
groups of 6 UCUs. It is recommended to populate the
UCUs in consecutive order, starting with “1”.
CTU The Common Timing Unit(s) (CTU) are numbered from
left to right, 1 and 2.
MCR The Multi-Carrier Radios (MCR) are numbered from left
to right, from 1 to 6.
OM The Oscillator Module(s) (OM) are numbered from the
left to the right, 1 and 2. Depending on the configuration,
they can be a Rubidium-based (OMR) and/or
quartz-based asynchronous Oscillator Modules (OMA).
CPC The Common Power Converters (CPC) are numbered
from left to right, from 1 to 4 (CPC-A), and from 5 to 8
(CPC-B).
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-33
Issue 1, August 2007 See notice on first page
Node B mechanical structure Component numbering in the UMTS Modular Cell
Outdoor for +24 V
Rectifier numbering
The AC rectifiers are divided into two groups of four. The first group is placed at the
cabinet’s wall, the second group to the left of the first group. Inside the groups the
rectifiers are numbered clockwise from 1 to 4 in the first group and from 5 to 8 in the
second. Numbering starts in the left column, upper row of each group.
....................................................................................................................................................................................................................................
3-34 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides the mechanical structure diagrams and component numbering of
theLucent UMTS Microcell.
Related information
For more information about the Lucent UMTS Microcell, refer to:
• Lucent UMTS Microcell Technical Description, 401-382-926.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-35
Issue 1, August 2007 See notice on first page
Node B mechanical structure
Outside view
Outside view of the Lucent Microcell Outdoor:
Inside view
View of the Lucent Microcell Outdoor for +24 V with door removed (1s1c
configuration):
...................................................................................................................................................................................................................................
3-36 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Mechanical structure of the Lucent UMTS Microcell
Outdoor
Fresh air
CPCs filter
IOU-1 OMR
Rectifier
Shelves
The Lucent Microcell Outdoor contains the following shelves:
• Fan shelf
• Digital shelf
• Amplifier shelf
• Filter and power shelf.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-37
Issue 1, August 2007 See notice on first page
Node B mechanical structure Mechanical structure of the Lucent UMTS Microcell
Outdoor
Shelf Components
Fan shelf The fan shelf contains the following components:
• Two fan sections used to cool the digital shelf and
the amplifier.
Digital shelf The digital shelf contains the following components:
• Lucent Microcell Input Output Unit (IOU1C)
• Circuit packs,
comprising the following units:
– Universal Radio Controller (URC)
– UMTS Channel Units (UCU)
– UMTS Multi-Carrier Radio (MCR)
– Common Timing Unit (CTU).
• Common Power Converter (CPC)
• Oscillator Modules (OMs)
• Power Distribution Module (PDM).
Amplifier shelf The amplifier shelf contains the following components:
• Single amplifier module.
Filter and power shelf The filter shelf contains the following components:
• I/O panel
• Dual Duplex Filter with TTLNA support
• Single rectifier module with controller
Installation options
Installation options for the Lucent Microcell Outdoor:
• Pole-mounted (with or without battery plinth)
• Wall-mounted (with or without battery plinth)
• Floor stand-mounted (with or without battery plinth)
• Concrete pad (with battery plinth).
View of the installation options for the Lucent Microcell Outdoor:
....................................................................................................................................................................................................................................
3-38 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure Mechanical structure of the Lucent UMTS Microcell
Outdoor
Battery plinth
When supplied with AC power, the Lucent Microcell Outdoor can be equipped with a
battery plinth.
The battery plinth contains a water-tight battery compartment for short term AC mains
failure coverage. It can hold up to four 12 V batteries connected in a serial-parellel
configuration to supply +24 volt back-up power to the cabinet in the event of a power
interruption.
View of the optional battery plinth:
Busbar with
battery fuse
Battery clamp
Batteries
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-39
Issue 1, August 2007 See notice on first page
Node B mechanical structure Mechanical structure of the Lucent UMTS Microcell
Outdoor
I/O panel
All interface connections to the Lucent Microcell Outdoor enter at the bottom of the
cabinet.
Bottom view of the Lucent Microcell Outdoor:
Bottom view
Earthing points
GPS
RF Antenna
AC feed
E1/T1 feed
User alarms
Spare
Receiver preamplifiers
Low Noise Amplifiers (LNAs) can be used as receiver preamplifiers in the various
frequency ranges. Depending on frequency ranges and mounting options these LNAs
are variously denoted.
The DxTMAs are optional Tower Mounted Amplifiers (could also be mounted on a
wall) and provide two independent pre-amplification branches.
....................................................................................................................................................................................................................................
3-40 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Node B mechanical structure
CPC B
CPC A
1 1
MCR
PDM
URC
UCU
UCU
CTU
Digital shelf
Exhaust Duct
Inlet Duct
OM
1 1 1 2 1 1 1 1
1 1
Important! The following sections only list components of which there can be
more than one in the Lucent Microcell Outdoor.
Component Numbering
URC There is only one Universal Radio Controller (URC).
UCU The UMTS Channel Units (UCUs) are numbered from
left to right, from 1 to 2.
MCR There is only one Multi-Carrier Radio (MCR).
CTU There is only one Common Timing Unit (CTU).
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 3-41
Issue 1, August 2007 See notice on first page
Node B mechanical structure Component numbering in the Lucent UMTS Microcell
Outdoor
Component Numbering
CPC There is only one Common Power Converter Type A
(CPC-A), and one Common Power Converter Type B
(CPC-B).
OM There is only one Oscillator Module (OM) . Depending
on the configuration, this can be a Rubidium-based
(OMR) or a quartz-based asynchronous Oscillator Module
(OMA).
PDM There is only one Power Distribution Module (PDM).
Component Numbering
Amplifier modules There is only one amplifier module.
Component Numbering
Filter panels There is only one dual duplex filter.
....................................................................................................................................................................................................................................
3-42 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
4 R NC mechanical structure
4
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter contains the mechanical structure diagrams of the RNC.
These diagrams provide the OMC operator with an overview of:
• The RNC hardware that is available
• The location of the hardware within the RNC cabinet
• The basic functions of the RNC hardware.
Related information
For more information about the RNC mechanical structure, refer to:
• Lucent RNC Technical Description, 401-382-320
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 4-1
Issue 1, August 2007 See notice on first page
RNC mechanical structure
Overview
This topic provides a brief description of the Radio Network Controller (RNC)
components.
...................................................................................................................................................................................................................................
4-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
RNC mechanical structure UMTS RNC mechanical description
FIP X X
X X X X X X
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Power X X X
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
X X X
distribution Lucent
O
O
Lucent
shelf O
O
INPUT POWER OK
O
O
50 A MAX 50 A MAX 40 A MAX 40 A MAX 40 A MAX 40 A MAX 40 A MAX 40 A MAX 30 A MAX
O
O
O
O
O
O
INPUT POWER OK
O
O
50 A MAX 50 A MAX 40 A MAX 40 A MAX 40 A MAX 40 A MAX 40 A MAX 40 A MAX 30 A MAX
REVERSE POLARITY REVERSE POLARITY
O
O
CB 1 CB 2 CB 3 CB 4 CB 5 CB 6 CB 7 CB 8 CB 9 CB 1 CB 2 CB 3 CB 4 CB 5 CB 6 CB 7 CB 8 CB 9
ECBU-A ECBU-B
Blank
panel
Alarm
board
Fiber Management O
O
X
! !! !!! O
X O
X O
X O
X O
X O
X O
X O
X O
X O
X
Fan
Unit (FMU) Trays
CONSOLE CONSOLE
O
O
o
O
O
o
o o o o
Console
Console
o o o o
O
o o o o
o
oo o o o o
oo
O O
oo
oo
oo CPC6601 O O CPC6601
oo
oo 10/100/1000M 10/100/1000M
O
P P P P P P P P P P
P P P M M M M M M M M P P P
M M M
GbE 1
GbE 1
M M M C C C C C C C C M M
20X
20X
C C C
C C C 2 2 2 2 2 2 2 2 C C
2 2 B
B B B B B
21X
21X
GbE 2
GbE 2
22X
22X
23X
23X
O O O O
Mezzanine 2
Mezzanine 2
P P P P P P P P P P
OOOO M M M M M M M M OOOO
A B
M M
A B
P P P P P P
O M M M C C C C C C C C C C M M M
OOOO
X
OOOO C C C 1 1 1 1 1 1 1 1 1 1 C C C
O OOOO A A A A A A OOOO
OOOO OOOO
Upper
X
cPSB
E E
Mezzanine 1
Mezzanine 1
oo
O T T T T T T T T T T
CP2300S-650 CP2300S-650 CP2300S-650 CP2300S-650 CP2300S-650 CP2300S-650
A B
A B
Link
1 1 1 1 1 1 1 1
Link
Speed
E OO E OO
Speed
chassis
R
HOT HOT HOT HOT HOT HOT
+ O HOT SWAP
SWAP SWAP SWAP HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS SWAP SWAP SWAP
HOT SWAP
O
O
X O
X O
X O
X O
X O
X O
X O
X O
X O
X
Cable Management
Unit (CMU)
This is a much longer Label This is a much longer Label This is a much longer Label This is a much longer Label This is a much longer Label
taking up 2 lines taking up 2 lines taking up 2 lines taking up 2 lines taking up 2 lines
Label Label Label Label Label Label Label Label Label Label
Terminal server
(shown without MRV
Communications Inc.
IR Series In-Reach
front cover)
FMU
O
O
X
! !! !!! O O O O O O O O O O
Fan
Trays
X X X X X X X X X X
CONSOLE CONSOLE
O
O
o
O
O
o
o o o o
Console
Console
o o o o
O
o o o o
o
oo o o o o
oo
O O
oo
oo
oo CPC6601 O O CPC6601
oo
oo 10/100/1000M 10/100/1000M
O
P P P P P P P P P P
P P P M M M M M M M M P P P
M M M
GbE 1
GbE 1
M M M C C C C C C C C M M
20X
20X
C C C
C C C 2 2 2 2 2 2 2 2 C C
2 2 B
B B B B B
21X
21X
GbE 2
GbE 2
22X
22X
+
23X
23X
O O O O
Mezzanine 2
Mezzanine 2
P P P P P P P P P P
OOOO M M M M M M M M OOOO
A B
M M
A B
P P P P P P
O M M M C C C C C C C C C C M M M
OOOO
X
OOOO C C C 1 1 1 1 1 1 1 1 1 1 C C C
Lower
O OOOO A A A A A A OOOO
X OOOO OOOO
! !! !!! OOOO OOOO
OOOO OOOO
OOOO OOOO
OOOO OOOO
CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM
OOOO RS O
R R R R R R R R R R
OOOO
COM COM COM O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT COM COM COM
O
OOOO OOOO
R/
OOE/ R/
OOE/ R/
OOE/ R/
OOE/ R/
OOE/ R/
OOE/ R/
OOE/ R/
OOE/ R/
OOE/ R/
OOE/
cPSB
o
oo
oo
oo
oo
OOOO U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 OOOO
OOOO OOOO
oo
oo
E E E E E E E E E E
Mezzanine 1
Mezzanine 1
oo
O T T T T T T T T T T
CP2300S-650 CP2300S-650 CP2300S-650 CP2300S-650 CP2300S-650 CP2300S-650
A B
A B
1 1 1 1 1 1 1 1
Link
E OO E OO
Speed
chassis
USER USER USER O O O O O O O O O O USER USER
O Reset L 1 2 L 1 2 L 1 2 L 1 2 L 1 2 L 1 2 L 1 2 L 1 2 L 1 2 L 1 2 O Reset
READY READY READY READY READY READY
CompactPCI TM
R
HOT HOT HOT
O O O O O O O O O O HOT HOT HOT
CompactPCI TM
R
+ O HOT SWAP
SWAP SWAP SWAP HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS SWAP SWAP SWAP
HOT SWAP
O
O
X O
X O
X O
X O
X O
X O
X O
X O
X O
X
CMU
This is a much longer Label This is a much longer Label This is a much longer Label This is a much longer Label This is a much longer Label
taking up 2 lines taking up 2 lines taking up 2 lines taking up 2 lines taking up 2 lines
Label Label Label Label Label Label Label Label Label Label
Blank
panel
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 4-3
Issue 1, August 2007 See notice on first page
RNC mechanical structure UMTS RNC mechanical description
Cabinet
The cabinet provides support for:
• Installation in both NAR and ETSI central offices
• Underfloor cable entry
• Raised floor installation
• Minimal requirement for floor space
• Cable entry from overhead cable racks
• Simplicity of maintenance through its straightforward layout. Maintenance is
typically performed from the front of the cabinet.
cPSB chassis
The cPSB chassis and its installed components are the primary call processing element
of the cabinet. The cPSB chassis has 21 slots for a combination of node cards, alarm
cards, and Ethernet ® switch cards. Each cabinet has two cPSB chassis.
The following types of cards are used:
• Alarm Cards (AC), also known as Chassis Management Modules (CMM)
• Gateway Intelligent Carrier Cards (GICC)
• Common Intelligent Carrier Cards (CICC)
• Ethernet Switch Cards (ESC)
• Solaris Blades (SB), also known as (FMS) blades
...................................................................................................................................................................................................................................
4-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
RNC mechanical structure UMTS RNC mechanical description
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 4-5
Issue 1, August 2007 See notice on first page
RNC mechanical structure
Overview
This topic describes the Compact PCI Packet Switched Backplane (cPSB) chassis,
which may also be referred to as the cPSB shelf, its component parts and their
functions.
cPSB chassis
The cPSB chassis and its installed components are the primary element of the FBP
cabinet. Up to twocPSB chassis can be contained in an FBP cabinet.
The cPSB chassis is PICMg2.16-compliant and is the foundation of the cPSB shelf and
components. The cPSB chassis includes the backplane, power, and cooling. It is a
full-height (12U high) chassis that provides slots for the remaining subcomponents.
The components in each PICMg2.16-compliant cPSB chassis include:
• Alarm Cards (AC): 2 per chassis
• Ethernet Switch Cards (ESC): 2 per chassis
• Depending on the configuration, up to 18 processing cards per chassis including
Common Intelligent Carrier Cards (CICCs), Gateway Common Carrier Cards
(GICCs) and Solaris Blades (SBs)
• Power supply units
• Fan trays
• Blank panels for unused slots.
Alarm Cards
The chassis Alarm Cards (ACs) provide reliability management for the blades. Two
alarm cards are used in each cPSB shelf. The alarm card follows the standard PICMG
2.16 and IPMI specifications. Software in the alarm cards implements low-level chassis
hardware management and provides alarm information to the application.
The alarm cards obtain feed voltage status directly from the power supplies. This
enables the alarm cards to send alarm information via Simple Network Management
Protocol (SNMP) to a system manager.
...................................................................................................................................................................................................................................
4-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
RNC mechanical structure cPSB chassis and components
Gigabit Ethernet ports. Four of the switched ports are available for interfacing with
other switched ports in the cabinet or with an external network. 20 ports are available
within the backplane to connect to other cards in the chassis.
Solaris ® Blades
A Solaris Blade (SB) consists of a Sun ™ Sparc ® processor and provides call processing
and OA&M functions.
The SPARC processor core communicates with the packet switched backplane directly
through two 10/100 Base -TX Ethernet interfaces. The Solaris ® Blade is a PICMG ®
2.16 cPSB card implementing a complete Solaris system including processor, memory
and disk subsystem. Two PCI Mezzanine Card (PMC) slots are available for individual
application needs.
The contents of the PCI mezzanine cards in the Solaris Blade varies:
• Slot A is available for additional I/O needs (for example, Ethernet interface)
• Slot B is reserved for the on-board disk drive.
Fan trays
The top of each cPSB chassis contains three fan trays, each containing three fans, a
control board and a status LED. This combination of fan trays provides cooling for the
entire shelf. Each fan is a Field Replaceable Unit (FRU).
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 4-7
Issue 1, August 2007 See notice on first page
RNC mechanical structure
cPSB chassis
The cPSB chassis contains:
• Fan units
• Circuit packs
• Power supply units
• Blanking panels
Fan units
The fan units are proprietary field replacement units.
Circuit packs
The following types of circuit packs are used:
• Alarm Card (AC). Also known as a Chassis Management Module (CMM)
• Gateway Intelligent Carrier Card (GICC)
• Common Intelligent Carrier Card (CICC)
• Ethernet Switch Card (ESC)
• Solaris Blade (SB). Also known asFMS Blade
Blanking panels
Blanking panels cover all unused circuit pack slots. This ensures correct airflow
through the cPSB chassis.
Configurations supported
The cPSB chassis supports the following circuit pack configurations for the UMTS
RNC:
• A-12-10 configuration
• A-12-20 configuration
cPSB chassis
The following diagram shows a front view of a UMTS cPSB chassis with circuit
packs. It is the same for both upper and lower chassis.
...................................................................................................................................................................................................................................
4-8 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
RNC mechanical structure cPSB chassis configuration
Fan units
GICC
ESC
O
X
O
X
! !! !!! O
X O
X O
X O
X O
X O
X O
X O
X O
X O
X
CONSOLE CONSOLE
O
O
o
O
O
o
o o o o
Console
Console
o o o o
O
o o o o
o
o o o o
Alarm
oo
oo
oo
oo
oo
oo
CPC6601 O
O O
O CPC6601
oo 10/100/1000M 10/100/1000M
P P P P P P P P P P
card 1
O
P P P M M M M M M M M M M P P P
GbE 1
GbE 1
M M M M M M
20X
20X
C C C C C C C C C C
C C C 2 2 2 2 2 2 2 2 C C C
2 2
B B B B B B
21X
21X
GbE 2
GbE 2
22X
22X
23X
+
23X
O O O O
Mezzanine 2
Mezzanine 2
P P P P P P P P P P
A B
OOOO
A B
OOOO P P P M M M M M M M M M M P P P
O
X M M M C C C C C C C C C C M M M
OOOO C C C 1 1 1 1 1 1 1 1 1 1 C C C
OOOO
O OOOO A A A A A A OOOO
X OOOO OOOO
! !! !!! OOOO OOOO
OOOO OOOO
OOOO OOOO
OOOO OOOO
CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM CompactPCI TM
OOOO RS O
R R R R R R R R R R
OOOO
COM COM COM O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT RS O O ABT COM COM COM
O
OOOO R/ R/ R/ R/ R/ R/ R/ R/ OOOO
o
oo
oo
OOOO OOE/ OOE/ OOE/ OOE/ OOE/ OOE/ OOE/ OOE/ R/
OOE/ R/
OOE/ OOOO
Alarm
oo
oo
U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 U1 U2 U1 U2
oo
oo
OOOO OOOO
Mezzanine 1
E E E E E E E E
Mezzanine 1
oo
E E
O T T T T T T T T T T
A B
A B
card 2
MGMT (MDI) H H H H H H H H H H
Link
Link
O 1 1 1 1 1 1 1 1 1 1 O
ABORT ABORT ABORT ABORT ABORT ABORT
S S S S S S S S S S
O O O O O O O O O O O O O O O O O O O O
Speed
E OO E OO E OO E OO E OO E OO E OO E OO
Speed
+ O SWAP SWAP SWAP HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS HS OOSYS SWAP SWAP SWAP O
O
X O
X O
X O
X O
X O
X O
X O
X O
X O
X
Solaris
Blades
CICC
ground
jack
grille/filter
Label Label Label Label Label Label
Power
Label Label Label Label
supply
units
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 4-9
Issue 1, August 2007 See notice on first page
RNC mechanical structure cPSB chassis configuration
SB1-06 (fms09)
SB1-04 (fms05)
SB1-05 (fms01)
CMM1-1
CICC1-09
CICC1-10
CICC1-11
CICC1-12
CICC1-13
GICC1-20
GICC1-3
BLANK
BLANK
BLANK
BLANK
BLANK
SB1-18
SB1-19
ESC1-21
SB1-17
ESC1-2
Card
Chassis
CMM1-2
1
Slot 2 3 4 6 7 8 9 10 11 12 14 15 16 18 20
1 5 13 17 19 21
position
SB2-04 (fms06)
SB2-05 (fms02)
BLANK(fms10)
CMM2-1
CICC2-11
CICC2-12
CICC2-13
CICC2-09
CICC2-10
GICC2-20
BLANK
BLANK
BLANK
GICC2-3
BLANK
BLANK
SB2-17
SB2-18
SB2-19
ESC2-21
ESC2-2
SB2-06
Card
CMM2-2
Chassis
2
Slot
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
position
Legend:
...................................................................................................................................................................................................................................
4-10 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
RNC mechanical structure cPSB chassis configuration
CMM1-1
SB1-04 (fms05)
SB1-05 (fms01)
SB1-06 (fms09)
SB1-19 (fms03)
SB1-17 (fms11)
SB1-18 (fms07)
CICC1-7
CICC1-8
CICC1-9
CICC1-10
CICC1-11
CICC1-12
CICC1-13
CICC1-14
CICC1-15
CICC1-16
GICC1-20
GICC1-03
ESC1-21
ESC1-02
Card
Chassis
CMM1-2
1
Slot 2 3 4 6 7 8 9 10 11 12 14 15 16 18 20
1 5 13 17 19 21
position
CMM2-1
SB2-19 (fms04)
SB2-04 (fms06)
SB2-05 (fms02)
SB2-06 (fms10)
SB2-17 (fms12)
SB2-18 (fms08)
CICC2-11
CICC2-12
CICC2-13
CICC2-14
CICC2-15
CICC2-16
CICC2-7
CICC2-8
CICC2-9
CICC2-10
GICC2-20
GICC2-03
ESC2-21
ESC2-02
Card
CMM2-2
Chassis
2
Slot
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
position
Legend:
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 4-11
Issue 1, August 2007 See notice on first page
Part III: Performing OAM&P on the
UTRAN
Overview
...................................................................................................................................................................................................................................
Purpose
This documentation part includes the descriptive and procedural information that an
OMC operator basically needs to know to perform OAM&P tasks on the UTRAN.
Reference
For more information about performing OAM&P tasks on the UTRAN, refer to:
• UMTS Lucent OMC-UPS Operations, Administration, Maintenance, and
Provisioning, 401-380-022
• UMTS Lucent Managed Object Descriptions, 401-380-071
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary III-1
Issue 1, August 2007 See notice on first page
5 U TRAN tools
5
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter describes the tools and equipment that can be used to :
• Perform maintenance on the UTRAN
• Check the UTRAN performance.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 5-1
Issue 1, August 2007 See notice on first page
UTRAN tools
Maintenance terminals
...................................................................................................................................................................................................................................
Introduction
Maintenance terminals provide the maintenance management interface for the UTRAN.
Types of maintenance terminals are:
• RNC Local Maintenance Terminal (LMT)
• Node B Remote Maintenance Terminal (RMT).
• Node B Local Maintenance Terminal (LMT)
RNC LMT
The RNC LMT provides telnet access to a command-line interface that is used to
perform administration, diagnosis, and maintenance of the RNC equipment. Connection
to the RNC is via the RNC LAN or directly over the RS-232 serial port.
Node B RMT
The Node B RMT application allows maintenance tasks to be performed on a Node B
without a physical connection to a wireless network. The Node B RMT can be used
for installation and maintenance of Node B cells.
Node B LMT
The Node B LMT provides access to the element management functions used to
perform administration, diagnosis, and maintenance of the Node B equipment.
Connection to the Node B is via the Ethernet port on the Node B.
Event message
The Node B sends an event message to the OMC to indicate that a Node B LMT has
gained control over the Node B. In this case, the Node B maintains the registration
with both the OMC and the Node B LMT. Any autonomous events and alarms from
the Node B, which are generated by the Node B, are sent to both the OMC and the
Node B LMT.
Events resulting from operations such as create or delete from the OMC will be sent to
the Node B LMT. Events resulting from operations such as create or delete from the
Node B LMT will be sent to the OMC.
When both the OMC and Node B LMT manage the same Node B in parallel, the LMT
takes precedence. In this case, the Node B LMT has read/write privileges and the
OMC has read-only privileges. The Node B automatically synchronizes its data with
the OMC through events.
...................................................................................................................................................................................................................................
5-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
UTRAN tools Maintenance terminals
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 5-3
Issue 1, August 2007 See notice on first page
UTRAN tools
Overview
The Orthogonal Channel Noise Simulator (OCNS) is a tool that simulates voice or data
traffic on the forward link or downlink from the Node B to the UE within a cell or
cluster of cells. The OCNS runs on the Node B, hence only OCNS setup data is sent
over the Iub interface and not the noise itself.
Test call
On request of a technician, OCNS noise is generated to cause interference for a special
test call. This is particularly necessary when the network is first installed and when
cluster testing and complete system testing are required.
Noise model
Noise models that are supported by the OCNS are:
• Voice
• Data.
The generated noise pattern can be defined by parameters to simulate the interference
noise that is generated by real live traffic.
Where:
• burst on time represents voice activity by the simulated user
• burst off time represents no voice activity by the simulated user.
...................................................................................................................................................................................................................................
5-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
UTRAN tools Orthogonal Channel Noise Simulator
Where:
• burst on time represents data activity by the simulated user
• burst off time represents no data activity by the simulated user
• burst cluster represents the total on and off burst time
• think time represents the processing time for the tool.
Power variation
Power variation can be used to vary the power of each frame to simulate power
control. When power variation is switched off, each frame will be sent with a constant
power level.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 5-5
Issue 1, August 2007 See notice on first page
UTRAN tools
RF trace
...................................................................................................................................................................................................................................
Introduction
The RF trace capability is a service which allows the operator to gather radio related
information associated with a predefined UE.
The information that is collected is can be used by the network operator to:
• Check the network performance
• Localize faults
• Optimize the network.
Performed in RNC
The RF trace functionality within the RNC is performed by the collection of signaling
messages on the Uu, Iub and Iu interfaces.
Collected data
For each RF trace, data is collected from the following sources:
• UE
• Node B
• RNC.
Number of RF traces
The maximum number of traces that can be performed are:
• One RF trace per UE
• 10 RF traces per RNC.
...................................................................................................................................................................................................................................
5-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
UTRAN tools
Overview
The High Speed Downlink Packet Access (HSDPA) Orthogonal Channel Noise
Simulator (OCNS) is a tool that simulates HSDPA traffic on the forward link or
downlink from the Node B to the UE within a cell or cluster of cells.
Test call
On request of a technician, HSDPA-OCNS traffic is generated to cause interference for
a special test call. This is particularly necessary when the network is first installed and
when cluster testing and complete system testing are required.
Where:
• burst on time represents data activity by the simulated user
• burst off time represents no data activity by the simulated user
• burst cluster represents the total on and off burst time
• think time represents the processing time for the tool.
Power variation
Power variation can be used to vary the power of each frame to simulate power
control. When power variation is switched off, each frame will be sent with a constant
power level.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 5-7
Issue 1, August 2007 See notice on first page
6 R adio frequencies
6
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter provides procedures for:
• modifying the frequency for Node B cells, and
• adding new frequencies on the RNC.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 6-1
Issue 1, August 2007 See notice on first page
Radio frequencies
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides the procedures that should be performed to modify the Node B
frequency.
Contents
...................................................................................................................................................................................................................................
6-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Radio frequencies
Purpose
This procedure should be followed to verify that the required frequency for the Node B
is configured on the RNC.
Radio Frequency
The UTRAN frequency is the licensed frequency in which the RNS is allowed to
operate in for a specific market.
Procedure
Perform the following steps to verify that the required frequency is available:
...................................................................................................................................................................................................
1 At the Network Manager HM view, select the RNC object for which you want to
verify the radio frequency.
...................................................................................................................................................................................................
5 Verify in the frequency table, if the specified frequency for the UTRAN is listed. The
frequencies are listed as the frequencyBand and frequency channel number.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 6-3
Issue 1, August 2007 See notice on first page
Radio frequencies Verify RNC configured frequency
...................................................................................................................................................................................................
...................................................................................................................................................................................................
7 Click Finish.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Radio frequencies
Purpose
This topic provides the procedure to modify the frequency used in the downlink
direction for a Node B cell.
The OMC CLI is used in this procedure.
Important! This procedure is useful when you update a few Node Bs manually. If
the frequency of all Node Bs in a market need to be changed, then a script which
makes repetitive use of the modifycell-lcell command is recommended.
Commands
There are two commands:
• Shutdown - In this scenario, the LCell object is shutdown gracefully. Existing calls
within the cell are allowed to complete before the object is shutdown. See “Modify
Node B frequency - without locking cell” (p. 6-6).
• Lock - In this scenario, the LCell object is immediately shutdown. Existing calls
within the cell are not allowed to complete before the object is shutdown. See
“Modify Node B frequency - locking cell” (p. 6-6).
Scripts
A script can be created to change the frequency for multiple cells on multiple Node Bs.
The script will need to repeat the modifycell-lcell command multiple times to
change the frequency for the required cells.
Reference
For more information on the modifycell-lcell command, refer to:
• Command Line Interface, 401-380-072.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 6-5
Issue 1, August 2007 See notice on first page
Radio frequencies Modify Node B frequency - CLI
Example:
modifycell-lcell:name=″LRNC=41,LNodeB=10,LCell=3″,LCELLATTRS_UARFCNND=
4357;
E...................................................................................................................................................................................................
ND OF STEPS
Example:
lock-lcell:name=″LRNC=41,LNodeB=10,LCell=3″;
modifycell-lcell:name=″LRNC=41,LNodeB=10,LCell=3″,LCELLATTRS_UARFCNND=
4357;
unlock-lcell:name=″LRNC=41,LNodeB=10,LCell=3″;
E...................................................................................................................................................................................................
ND OF STEPS
....................................................................................................................................................................................................................................
6-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Radio frequencies Modify Node B frequency - CLI
Modified objects
This command modifies the LCell object.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 6-7
Issue 1, August 2007 See notice on first page
Radio frequencies
Purpose
This topic provides the procedure to modify the frequency used in the downlink
direction for a Node B cell.
This OMC GUI is used in this procedure.
Important! Using the OMC CLI to modify the frequency will reduce the amount
of time required to perform this task. See “Modify Node B frequency - CLI”
(p. 6-5).
Related information
None.
Procedure
Perform the following steps to modify the frequency of the cell:
...................................................................................................................................................................................................
1 At the Network Manager HM view, select the RNC object that manages the Node Bs
that require frequency modification.
...................................................................................................................................................................................................
3 In the RNC object tree, select the LNodeBTable and expend the tree.
Result: A list of LNodeB objects appear.
...................................................................................................................................................................................................
5 Right click the LCell object to be modified and select Modify UseCases -> Cell.
...................................................................................................................................................................................................................................
6-8 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Radio frequencies Modify Node B frequency - GUI
8 In the LCell tab, use the selection arrows to set the Band in the umtsFrequencyBand
field.
...................................................................................................................................................................................................
9 In the LCell tab, set the new frequency in the uARFCNNd (downlink frequency) field.
The field is listed in the Transmitter frequency box.
Note: The uARFCNNu (uplink Frequency) is automatically set, hence it is not
necessary to define this frequency.
...................................................................................................................................................................................................
12 Verify that the new frequency is set in the LCell configuration window.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 6-9
Issue 1, August 2007 See notice on first page
Radio frequencies Modify Node B frequency - GUI
...................................................................................................................................................................................................
13 Repeat Step 1 to Step 12 for other LCell objects that require a frequency modification.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-10 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Radio frequencies
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides the procedures that should be performed to configure a new
frequency on the RNC.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 6-11
Issue 1, August 2007 See notice on first page
Radio frequencies
Preliminary information
...................................................................................................................................................................................................................................
Overview
This topic lists the order in which procedures must be performed to add a new
frequency to the RNC. It also describes the consequences of RNC reset and the
frequency ranges.
RNC Reset
Adding a new frequency to the RNC will trigger the resetRequired flag to be set to
“true”. This requires the RNC to be reset after the new frequency is added.
Note: All Node Bs associated with the RNC will be unavailable during the RNC reset.
WARNING: An RNC reset is a service effecting action. If the RNC is in service,
contact the Market Program Manager to obtain permission to execute the reset.
Frequency
The frequency band and downlink frequency are needed prior to performing the
procedures. This table provides a frequency band and downlink frequency cross
reference.
...................................................................................................................................................................................................................................
6-12 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Radio frequencies Preliminary information
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 6-13
Issue 1, August 2007 See notice on first page
Radio frequencies
Purpose
This procedure describes how to add a new frequency to an existing RNC.
Related information
None.
Procedure
Perform the following steps to add a new frequency to an existing RNC:
...................................................................................................................................................................................................
1 At the Network Manager HM view, select the RNC object for which you want to add
a new frequency.
...................................................................................................................................................................................................
2 Click the arrow to the left of the RNC managed object to open the RNC tree.
...................................................................................................................................................................................................
3 Right click the LRNC object, and select Modify Usecases -> RNC.
Result: The Modify RNC: LRNC details view appears.
...................................................................................................................................................................................................
4 From the Modify RNC: LRNC details view, click on the LRNC tab, then click the
Add... button in the Freq box.
Result: The Parameters of freq window appears.
...................................................................................................................................................................................................
5 In the Parameters of freq window, click on the arrows in the frequencyBand field to
select the band, and enter the downlink frequency/channel in the frequency field.
...................................................................................................................................................................................................
7 After the frequency is added, click the Cancel button in the Parameters of freq
window.
...................................................................................................................................................................................................................................
6-14 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Radio frequencies Add a new frequency
In the Modify RNC: LRNC details view, verify that the new frequency and band class
have been added to the freq box.
Note: You may have to scroll through the window to see the added frequency.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 6-15
Issue 1, August 2007 See notice on first page
Radio frequencies
Purpose
This procedure describes how to verify a newly added frequency to the RNC.
Related information
None.
Procedure
Perform the following steps to verify the newly added frequency to the RNC:
...................................................................................................................................................................................................
1 At the Network Manager HM view, select the RNC object for which you want to
verify the new frequency was added.
...................................................................................................................................................................................................
2 Click the arrow to the left of the RNC managed object to open the RNC tree.
...................................................................................................................................................................................................
4 In the RNC detailed view, click on the LRNC tab, and use the arrows to check the
frequency in the freq box.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
6-16 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Radio frequencies Check RNC configured frequency
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 6-17
Issue 1, August 2007 See notice on first page
Radio frequencies
RNC Reset
...................................................................................................................................................................................................................................
Purpose
This procedure describes how to reset the RNC.
WARNING! An RNC reset is a service affecting action. Approval must be obtained
before a reset is performed on an in-service RNC.
Related information
After adding a new frequency to the RNC, the resetRequired flag will set to “true” by
the system. This is because a reset of the RNC is required before the new frequency
can take effect.
Procedure
Perform the following steps to reset the RNC:
...................................................................................................................................................................................................
1 At the Network Manager HM view, select the RNC object that you want to reset.
...................................................................................................................................................................................................
2 Click the arrow to the left of the RNC managed object to open the RNC tree.
...................................................................................................................................................................................................
3 Double click the RNC object to open the detail view of the RNC.
Result: The RNC detailed view appears.
...................................................................................................................................................................................................
4 In the RNC detailed view, click the State tab to verify the resetRequired flag displays
“true”. If the flag is not “true”, then no reset is required and the remaining steps can
be skipped.
...................................................................................................................................................................................................
6 In the Reset window, select the force option, then click on the Finish button to reset
the RNC.
...................................................................................................................................................................................................................................
6-18 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Radio frequencies RNC Reset
Important! Depending on the size of the network, the RNC reset can take over 20
minutes to complete. The reset will finish once the RNC Full Tree Audit completes
at the OMC.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 6-19
Issue 1, August 2007 See notice on first page
Radio frequencies
RNCTRACE Reset
...................................................................................................................................................................................................................................
Purpose
This procedure describes how to reset the rnctrace level on all the CP blades.
Related information
None.
Procedure
Perform the following steps to reset the rnctrace level on all the CP blades:
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
6-20 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
7 E 1T1 growth
7
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter describes how to add E1T1 connections.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 7-1
Issue 1, August 2007 See notice on first page
E1T1 growth
E1T1 growth
...................................................................................................................................................................................................................................
Overview
This topic describes how to add new E1T1 links to an existing IMAGroup through the
OMC GUI and CLI.
Where:
• a represents the Node B ID
• b represents the IMAGroup ID
• c represents the E1T1 Ports attributes
• d represents the name of the Node B
...................................................................................................................................................................................................................................
7-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
E1T1 growth E1T1 growth
For more information about each CLI command and the required command syntax,
refer to the Lucent Operations and Maintenance Center - UTRAN Command Line
Interface, 401-380-072 manual.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 7-3
Issue 1, August 2007 See notice on first page
8 S SH and Telnet connections
8
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter provides the procedures to open a Secure Shell (SSH) session for the
OMC client to:
• An RNC
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 8-1
Issue 1, August 2007 See notice on first page
SSH and Telnet connections
Purpose
This topic provides the procedure to open a Secure Shell (SSH) session from the OMC
client PC to an RNC.
Related information
There is no related information for this procedure.
Procedure
Perform the following steps to open an SSH session:
...................................................................................................................................................................................................
1 In the Network Manager window select the FMS OA&M blade in the RNC that you
want to establish an SSH session with.
...................................................................................................................................................................................................
2 Go to the Tools menu and select Cut Through → SSH Cut Through.
Result: The SSH console is displayed.
...................................................................................................................................................................................................
3 At the SSH console, log on to the FMS blade as an RNC user, for example, primUser.
Important! If password authentication is disabled at the RNC, the connection
between the OMC-UPS and the RNC can only be done using key authentication.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
8-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
SSH and Telnet connections
Telnet to a Node B
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure to open a Telnet session from the OMC client PC to
a Node B.
Related information
There is no related information for this procedure.
Procedure
Perform the following steps to log on the Node B through a Telnet session:
...................................................................................................................................................................................................
2 Go to the tools menu and select Cut Through → Telnet Cut Through.
Result: A telnet session to the Node B is opened. The IP address that is used for
this connection is retrieved from the Telnet Host IP attribute of the NodeB
object.
...................................................................................................................................................................................................
3 Fill in the Login Name and Password to establish the Telnet session to the Node B.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 8-3
Issue 1, August 2007 See notice on first page
9 R ecommended OMC filters
9
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter provides the procedures to be used by the OMC administrator in order to
generate a number of recommended alarm filters that can be used during the alarm
surveillance process.
After the filters are created, they can be used by the OMC operator during the
day-to-day alarm surveillance process. These filters allow the operator to quickly
oversee the alarm status of the network elements or interfaces while performing Fault
Management (FM).
Note: The filters that are discussed in this topic are defined on the OMC. If a filter
needs to be defined to suppress alarm on a Node B or an RNC itself, refer to the
“Suppress alarms on a Node B or an RNC” (p. 13-13) topic.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 9-1
Issue 1, August 2007 See notice on first page
Recommended OMC filters
Recommended filters
...................................................................................................................................................................................................................................
Filters
Filters filter data and display only the data that is matching the filter criteria. The
OMC operator can create filters to filter for example by alarm severity or type of
alarm. Filters can be stored on the OMC server. In specific situations, like an overload
situation, the OMC operator can select the appropriate filter to see only the alarms that
are matching the filter criteria.
Recommended filters
Alarms are cleared by severity. During serious UTRAN network problems, many
alarms of a different severity are displayed in the Alarm Tables.
Therefore Lucent recommends to create the following filters:
...................................................................................................................................................................................................................................
9-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Recommended OMC filters
Purpose
This topic provides the procedure to create a critical alarm filter.
Related information
There is no related information for this procedure.
1 At the Alarm Manager window, go to the Tools menu and select Filter.
Result: The Alarm Filter window opens.
...................................................................................................................................................................................................
5 Enter a representative file name for this filter, for example, OverloadCriticalAlarms, in
the Save Alarm Filter dialog window and select Save.
Result: The filter is saved and is available for future use.
If you cannot save the filter because the maximum number of filters has been
reached, contact your fault management administrator to delete an unnecessary
filter.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 9-3
Issue 1, August 2007 See notice on first page
Recommended OMC filters
Purpose
This topic provides the procedure to create critical and major alarm filters.
Related information
There is no related information for this procedure.
1 At the Alarm Manager window, go to the Tools menu and select Filter.
Result: The Alarm Filter window opens.
...................................................................................................................................................................................................
5 Enter a representative file name for this filter, for example, OverloadCriticalMajo-
rAlarms, in the Save Alarm Filter dialog window and select Save.
Result: The filter is saved and is available for future use.
If you cannot save the filter because the maximum number of filters has been
reached, contact your fault management administrator to delete an unnecessary
filter.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
9-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Recommended OMC filters
Purpose
This topic provides the procedure to create all alarms during shift filters.
Related information
There is no related information for this procedure.
1 At the Alarm Manager window, go to the Tools menu and select Filter.
Result: The Alarm Filter window opens.
...................................................................................................................................................................................................
5 Enter a representative file name for this filter, for example, AlarmDuringShift, in the
Save Alarm Filter dialog window and select Save.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 9-5
Issue 1, August 2007 See notice on first page
Recommended OMC filters Create filter - all alarms during shift
...................................................................................................................................................................................................................................
9-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Recommended OMC filters
Purpose
This topic provides the procedure to create acknowledged alarm by user filters.
Related information
There is no related information for this procedure.
1 At the Alarm Manager window, go to the Tools menu and select Filter.
Result: The Alarm Filter window opens.
...................................................................................................................................................................................................
5 Enter a representative file name for this filter, for example, UnackAlarms, in the Save
Alarm Filter dialog window and select Save.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 9-7
Issue 1, August 2007 See notice on first page
Recommended OMC filters Create filter - acknowledged alarm by user
...................................................................................................................................................................................................................................
9-8 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Recommended OMC filters
Purpose
This topic provides the procedure to create unacknowledged alarm filters.
Related information
There is no related information for this procedure.
1 At the Alarm Manager window, go to the Tools menu and select Filter.
Result: The Alarm Filter window opens.
...................................................................................................................................................................................................
6 Enter a representative file name for this filter, for example, AckAlarmsByOmcadm, in
the Save Alarm Filter dialog window and select Save.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 9-9
Issue 1, August 2007 See notice on first page
Recommended OMC filters Create filter - unacknowledged alarms
...................................................................................................................................................................................................................................
9-10 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
10 10 UTRAN Managed
The
Information Model (MIM)
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter includes the descriptions of the Managed Information Models (MIMs) that
are used in the different UTRAN elements.
These models function as the basis of how the UTRAN is represented on the OMC
and how the different objects are related to each other.
Contents
Introduction 10-2
The UTRAN information model 10-3
MIBs in the Lucent UTRAN 10-4
MIB contents 10-6
Working with the UTRAN MIB 10-8
Information Models 10-9
Introduction 10-10
SNM information model 10-11
RNC Information model 10-13
Node B information model 10-16
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 10-1
Issue 1, August 2007 See notice on first page
The UTRAN Managed Information Model (MIM)
Introduction
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes how in the Node B, RNC and OMC, information is:
• Stored in a Managed Information Base (MIB)
• Managed by the Managed Information Model (MIM)
• Related to each other.
Contents
...................................................................................................................................................................................................................................
10-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
The UTRAN Managed Information Model (MIM)
MIM Example
A common example of a MIB and a MIM:
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 10-3
Issue 1, August 2007 See notice on first page
The UTRAN Managed Information Model (MIM)
Graphical representation
The following figure shows the location of the MIBs within the Lucent UTRAN:
Network Management
System NML
Itf-N
OMC-UPS
Integrated SNM
EML
Node B RNC
EM EM
Itf-B Itf-R
Iub NEL
Node B RNC
...................................................................................................................................................................................................................................
10-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
The UTRAN Managed Information Model (MIM) MIBs in the Lucent UTRAN
Node B MIB
The Node B MIB contains all information that is needed to configure and control the
Node B hardware and the logical Node B objects (the cells) that are controlled by the
Node B.
RNC MIB
The RNC MIB contains all information that is needed to configure and control the
RNC hardware and the logical RNC objects (the location areas, handover parameters,
etc.) that are controlled by the RNC.
OMC-UPS MIBs
In the OMC-UPS three MIBs are available:
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 10-5
Issue 1, August 2007 See notice on first page
The UTRAN Managed Information Model (MIM)
MIB contents
...................................................................................................................................................................................................................................
Overview
This topic provides the definitions that are needed to better understand the
object-oriented structure of the MIBs.
Definition
Objects Represent the basic building blocks of the MIB.
In the MIB, each object:
• Has a contained relationship with a parent object (except for the top object)
• Can be associated with other objects
• Consists of a number of attributes (parameters).
Definition
Object types Can represent either physical or logical resources. A physical object is
real and can be touched whereas a logical object is abstract in nature.
Examples of Physical and Logical Objects
Definition
Attribute An attribute is a property carried by an object. This property is a condition,
value or predefined set of values. All objects have one or more attributes.
Definition
Parent-Attribute When an attribute exists of more than one property it is referred to
as a Parent-Attribute.
Definition
Sub-Attribute When an attribute exists of more than one property, the parent-attribute
can be divided into a number of sub-attributes. Each sub-attribute can be a
condition, value or predefined set of values.
...................................................................................................................................................................................................................................
10-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
The UTRAN Managed Information Model (MIM) MIB contents
Definition
Contained relationship When an object has a contained relationship with another
object, there is a parent-child relation between these two objects. To be able to
create a child object, the parent object always needs to be present.
Definition
Associated relationship When an object has an associated relationship with another
object, the objects rely upon the services of each other. Neither object is
subordinate to the other but they are directly related, and neither can function
without the other. In some cases, an object that relies upon the service of another
object, cannot be created until the other object is created first.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 10-7
Issue 1, August 2007 See notice on first page
The UTRAN Managed Information Model (MIM)
Reference
For more information about the actions that can be performed on each UTRAN
attribute, refer to the UTRAN Attribute Descriptions manual, 401-382-801.
...................................................................................................................................................................................................................................
10-8 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
The UTRAN Managed Information Model (MIM)
Information Models
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes how objects are structured for the:
• SNM Information Model
• RNC Information Model
• Node B Information Model.
Contents
Introduction 10-10
SNM information model 10-11
RNC Information model 10-13
Node B information model 10-16
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 10-9
Issue 1, August 2007 See notice on first page
The UTRAN Managed Information Model (MIM)
Introduction
...................................................................................................................................................................................................................................
Information models
When an OMC operator is performing UTRAN related tasks at the OMC GUI or CLI,
the operator must understand how all these managed objects:
• Are represented at the OMC (their names)
• Are related to each other (the contained and associated relationships that they
have).
All this information is provided in the information models.
...................................................................................................................................................................................................................................
10-10 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
The UTRAN Managed Information Model (MIM)
CLI visibility
To assure that the SNM MIM is still fully accessible and manageable, the complete
model has been made accessible for OMC-UPS CLI users.
Network
SNM
ItfBLink
= Containment
The SNM MIM is located under the OMC-UPS folder in the Network manager
window.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 10-11
Issue 1, August 2007 See notice on first page
The UTRAN Managed Information Model (MIM) SNM information model
SNM
LinkProfile
RncManagedElement NodeBManagedElement
VccDetail
ItfBGroup
b Uni
NodeBFunction ItfBLink
a b a
IubLink
a
b b
RncFunction IucsLink Msc
a
b
IupsLink Sgsn
a
b
UtranCell
IurLink ExternalRnc
ExternalUtranCell
ItfRLink
ExternalGSMCell
= Containment
= Association
= Not visible on the OMC GUI
....................................................................................................................................................................................................................................
10-12 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
The UTRAN Managed Information Model (MIM)
Overview
The RNC information model is too large to represent in one diagram, hence this model
has been divided into the following categories:
• Hardware related RNC objects
• Logical RNC objects.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 10-13
Issue 1, August 2007 See notice on first page
The UTRAN Managed Information Model (MIM) RNC Information model
Network
Rns
LRNC
FBPShelf GICCPair
CICCProc ESCProc
CICCBPEtherPort ESCBPEtherPort
GICCProc
ESCFAEtherPort
GICCBPEtherPort SBProc
GICCFAEtherPort SBClan
GICCSTM1OC3Port SBBPEtherPort
PG = Containment
= Association
= Pre-configured
= Refer to logical object tree
....................................................................................................................................................................................................................................
10-14 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
The UTRAN Managed Information Model (MIM) RNC Information model
Network
Rns
LRNC
PeriodCriteria
FddExtCell
SS7Link
URA
GsmExtCell
LA
PRACH
PRNC IuR Iub IuPS IuCS
SCCPCHFach
PG
RA
SCCPCHPch
SAPS OCNS
ATMQOS
EDCH
= Pre-configured
= Containment
= Association
= Value valid for all
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 10-15
Issue 1, August 2007 See notice on first page
The UTRAN Managed Information Model (MIM)
Network
Rns
NodeB
= Containment
= Association
TDU Filter AmpShelfFan TxAmp
CTU UCU
AlarmHub OM
or IOU
DigitalShelfFan OCM
URC CPRIPort
...................................................................................................................................................................................................................................
10-16 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Part IV: Fault Management
Overview
...................................................................................................................................................................................................................................
Purpose
This documentation part includes all tasks that an OMC operator can perform to do
Fault Management on the UTRAN.
References
For more information about performing Fault Management on the UTRAN, refer to:
UMTS Lucent OMC-UPS Operations, Administration, Maintenance, and Provisioning,
401-380-022
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary IV-1
Issue 1, August 2007 See notice on first page
11 Principles of maintenance
11
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter describes:
• How fault management can be performed in the UTRAN
• Which equipment can be used to perform fault management in the UTRAN
• The characteristics of the alarms that can be generated by the UTRAN.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 11-1
Issue 1, August 2007 See notice on first page
Principles of maintenance
Overview
UTRAN fault management:
• Provides the required functionality for the operator to detect faults
• Determines the cause of faults in the system
• Helps the operator to minimize the effect of the faults on the service provided by
the network
• Provides assistance to correct the fault.
Fault management monitors the operational and administrative states of each of the
network elements within the system that is controlled by the Element Managers (EM),
as well as the operational and administrative states of all the individual components of
the network elements.
Reference
UMTS fault management is based on the TMN management principles for fault
management that are defined in:
• ITU-T Recommendation M.3400: TMN Management Functions.
The requirements for UMTS fault management are outlined in:
• 3G Technical Specification 32.111: UMTS - 3G Configuration Management.
The requirements for alarm reporting are outlined in:
• ITU-T Recommendation X.733: Information Technology - Open Systems
Interconnection - System Management: Alarm reporting function
Fault-management architecture
The fault-management architecture for the UTRAN domain with the Integrated Fault
Manager (IFM) interfacing to the OMC and the OMC interfacing to the network
elements Node B and RNC:
...................................................................................................................................................................................................................................
11-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Principles of maintenance UTRAN fault-management architecture
Itf-N
OMC
Integrated SNM
EML
Node B RNC
EM EM
Itf-B Itf-R
Iub
NodeB RNC NEL
RMT/LMT LMT
Element managers
The Element Managers (EM) collect and classify event and alarm messages and then
display the appropriate status to EM operators. The NEs are able to take defined
recovery action depending on the nature of the fault and the EM is also able to take
defined recovery action to return the network to an operational state.
OMC
The OMC combines the element-management functions for the UTRAN NEs in one
system. The OMC monitors and controls the RNC, the Node B and the external
equipment that is controlled from these NEs.
Functional blocks within the OMC:
• RNC Element Management (RNC EM) function
• Node B Element Management (Node B EM) function
• Integrated RNC/Node B Sub-Network Management (SNM) function.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 11-3
Issue 1, August 2007 See notice on first page
Principles of maintenance UTRAN fault-management architecture
LMT
The Local Maintenance Terminal (LMT) is attached to a single RNC. The
fault-management operator will have access to a RNC from the LMT terminal.
RMT
The Remote Maintenance Terminal (RMT) is attached to a single Node B. The
fault-management operator will have access to a Node B from the RMT terminal.
IFM
The Integrated Fault Manager (IFM) is the fault-management functionality that is
resident at the Network Management System (NMS) in the management hierarchy. The
IFM provides an overall view of the different types of equipment within the complete
UMTS system, including the outstanding alarms and the operational states of the NEs.
...................................................................................................................................................................................................................................
11-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Principles of maintenance
Affected component
The affected component indicates the hardware unit in which the defect has been
detected.
Identification of the affected unit:
• On the OMC the affected unit is indicated by its FDN.
An example of the FDN is: LRNC=1,Cabinet=1,FBPShelf=1,CICC=1.
• In the fault clearance procedures the affected unit is indicated in the first part of the
alarm name.
An example of the alarm name is: CICC_lostCommunication.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 11-5
Issue 1, August 2007 See notice on first page
Principles of maintenance UTRAN alarm parameters
Alarm severity
Alarms in the network can have the following degree of severity:
Severity Description
Critical A service-affecting condition has occurred and requires
immediate corrective action.
This degree of severity is used when a fault has affected the
service provided to the mobile user(s) such that no service can
be provided in some areas.
Major A service-affecting condition has occurred and urgent
corrective action is required.
This degree of severity is used when a fault has reduced rather
than removed the capability of the network to provide a
service.
Minor A non-service-affecting fault has occurred and corrective action
should be taken to prevent more serious faults.
Typically, minor faults are faults that do not degrade the
network capacity, maybe because redundant capacity was
available or the fault did not affect network traffic.
Warning A potential or impending service-affecting condition has been
detected.
The problem should be corrected to prevent it becoming
service-affecting.
Indeterminate The severity level cannot be determined.
Probable cause
The probable cause of the alarm indicates the most probable reason for triggering the
alarm.
...................................................................................................................................................................................................................................
11-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Principles of maintenance UTRAN alarm parameters
Nature Description
ADAC Alarms of this type are Automatically Detected and Automatically
Cleared (ADAC).
Alarms that belong to this category will automatically be removed
from the active list at the moment that the fault has been corrected.
Examples:
• The alarm is cleared when the unit has been replaced
successfully
• The alarm is automatically cleared when the software process
has successfully restarted.
ADMC Alarms of this type are Automatically Detected but must be
Manually Cleared (ADMC).
Alarms that belong to this category must be removed manually from
the OMC active alarm list at the moment that the fault has been
corrected.
Examples:
• After the unit has been replaced the alarm must be manually
reset
• After the software process has restarted the alarm must be
manually reset.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 11-7
Issue 1, August 2007 See notice on first page
Principles of maintenance
Alarm thresholds
For certain Node B and RNC events, thresholds have been defined to indicate when an
alarm should be triggered. In almost all cases these threshold levels have been defined
internally in the NE and can not be changed.
Fault types
Thresholds are used to detect faults of the following types:
Environmental faults
Upper and lower thresholds are used to detect an environmental condition and its
clearance. This method is used to prevent repeated reporting and clearance if a
condition fluctuates around a single threshold.
A second threshold may be defined at which the equipment is endangered by adverse
environmental conditions and more drastic action must therefore be taken, for example:
shut down autonomously.
Note
Most environmental conditions will be detected using external equipment, and will
therefore be detected as external alarms.
Overload conditions
Overload conditions are reported when a threshold is exceeded and cleared with
hysteresis.
...................................................................................................................................................................................................................................
11-8 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Principles of maintenance UTRAN alarm thresholds
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 11-9
Issue 1, August 2007 See notice on first page
12 Preventive maintenance
12
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter contains all the tasks that should be performed by the OMC operator to
perform preventive maintenance on the UTRAN.
Related information
For more related information about preventive maintenance that should be performed
directly on the RNC or the Node B, refer to:
• Lucent RNC Operations, Administration and Maintenance, 401-382-360
• Lucent UMTS Macrocell Indoor, Operation, Administration and Maintenance for
+24V, 401-382-462
• Lucent UMTS Modular Cell Outdoor, Operation, Administration and Maintenance
for +24V, 401-382-760
• Lucent UMTS Macrocell Compact, Operation, Administration and Maintenance for
+24V, 401-382-961
• Lucent UMTS Microcell (Type M), Operation, Administration and Maintenance for
+24V, 401-382-966.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 12-1
Issue 1, August 2007 See notice on first page
Preventive maintenance
Overview
This topic includes the time line for the different preventive maintenance tasks.
...................................................................................................................................................................................................................................
12-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Preventive maintenance
Purpose
This topic provides the procedures that can be performed to check the operational
status and alarm status of the complete UTRAN.
Note: The procedures that are provided in this topic are written as complementary
procedures to the normal alarm surveillance process that is described in the “Alarm
surveillance process” (p. 13-3).
1 Create and activate an alarm filter containing all (LRNC and NodeB) objects.
...................................................................................................................................................................................................
2 At the Fault Manager, go to the View menu and select Refresh to resynchronize the
current alarm view with the active alarms.
...................................................................................................................................................................................................
3 For each of the alarms that occurred as new alarms after the synchronization, decide
whether they need immediate attention or whether they can be solved at a later stage
during the “normal” day to day alarm surveillance process.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 12-3
Issue 1, August 2007 See notice on first page
Preventive maintenance Check UTRAN status
...................................................................................................................................................................................................
3 Check the + subtree box if you want to include the child objects and click OK.
...................................................................................................................................................................................................
4 After the synchronization completed, determine whether any abnormalities are reported
by the OMC indicating differences between the UTRAN and the OMC. If any
abnormalities are reported, decide whether they need your immediate attention or
whether they can be solved at a later stage.
The generated report can be found in the http://<OMC-UPS server IP
address>:12000/reports/current/NEAuditLogReport directory.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
12-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Preventive maintenance Check UTRAN status
2 Browse through the cleared alarms and determine whether there were any
abnormalities that should be checked in further detail.
E...................................................................................................................................................................................................
ND OF STEPS
1 Open the FM event log view containing all the error messages that were forwarded
from the UTRAN network elements to the OMC.
...................................................................................................................................................................................................
2 Activate a log view filter to view the errors that have been reported since the last time
that this procedure has been performed.
...................................................................................................................................................................................................
3 Browse through the error logs and determine whether there were any abnormalities that
should be checked in further detail.
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 12-5
Issue 1, August 2007 See notice on first page
Preventive maintenance Check UTRAN status
3 Select an object class in the Class-names List, left click and select View.
Result: A table opens showing the objects of the selected NE and their operational,
administrative and alarm state.
...................................................................................................................................................................................................
4 For each locked and disabled object, determine whether there were any operational
status abnormalities that should be checked in further detail.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
12-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Preventive maintenance
Check RF coverage
...................................................................................................................................................................................................................................
Overview
The measurements that can be used in preventive maintenance to test the RF network
coverage are:
• Drive test
• RF trace.
Reference
For more information about how often the RF coverage should be checked from a
preventive maintenance point of view, see the “Preventive maintenance schedule”
(p. 12-2) topic.
Drive test
Drive test equipment is used to measure downlink RF coverage.
Equipment typically consists of two components:
• UMTS receiver
• UMTS test phone.
The UMTS receiver is used to measure basic UMTS Node B transmitter characteristics
(for example Tx Power, Pilot level).
The test mobile is used to measure a downlink channel and record Physical and Layer
3 message to monitor the progress of a test call and identify potential causes of quality
affecting issues.
RF trace
The RF Trace capability is a service that allows the operator to gather radio related
information associated to a predefined UE.
Reference
For more information about the RF trace service:
• General information, refer to “RF trace” (p. 5-6)
• Procedures for managing RF traces, refer to “Manage the RF trace service”
(p. 27-8).
Measurement analysis
When measurements are performed regularly and the information is analyzed, an
operator can detect trends. For example deteriorating performances can be detected,
even before errors are generated.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 12-7
Issue 1, August 2007 See notice on first page
13 13
Corrective maintenance - alarm
surveillance
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter provides all the procedures that are needed to perform alarm surveillance
on the OMC for:
• RNC related alarms
• Node B related alarms.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-1
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance
Overview
...................................................................................................................................................................................................................................
Purpose
This section includes the description of the day to day alarm surveillance process, as
well as the procedures that are needed to fulfill this process.
Contents
...................................................................................................................................................................................................................................
13-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance
Purpose
This topic describes the overall process that should be followed by the OMC operator
to perform alarm surveillance on the UTRAN.
Begin
Open the
1 fault manager
Open standard
2 alarm tables
Window
overloaded with Open alarm
3 overload filter
new alarms? Y
Abnor-
All alarms malities in the
5 acknowledged? UTRAN alarms?
Y N
N Y
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-3
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance Alarm surveillance process
1 Open the fault manager using the “Open the fault manager” (p. 13-6) procedure.
...................................................................................................................................................................................................
2 Open the standard alarm tables using the “Open standard alarm tables” (p. 13-7)
procedure.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
13-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance Alarm surveillance process
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
7 For each of the acknowledged alarms, solve the alarm by following the “Fault
correction process” (p. 18-3) process.
When finished return to step 1 once more to determine whether there are new alarms.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-5
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance
Purpose
This topic provides the procedure to open the fault manager.
Related information
There is no related information for this procedure.
2 Click the Maximize button in the upper right corner of the window to display the
window full screen.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
13-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance
Purpose
This topic provides the procedure to open predefined alarm tables. With these
predefined alarm tables the OMC operator is able to monitor new alarms,
acknowledged alarms, and abnormal events in one view.
Related information
Refer to:
• “Create filter - all alarms during shift” (p. 9-5), to create an alarm filter that filters
all alarms that occur during your shift.
• “Create filter - acknowledged alarm by user” (p. 9-7), to create an alarm filter that
filters all alarms that are acknowledged by you.
• “Create filter - unacknowledged alarms” (p. 9-9), to create an alarm filter that
filters all alarms that are unacknowledged.
1 At the Fault Manager window, go to the Tools menu and select Filter.
Result: The Alarm Filter window opens.
...................................................................................................................................................................................................
2 Select from the Custom filter drop-down list, the “all alarms during shift filter” and
check the following:
• The Date field shows the date of today
• The Time field shows the time your shift starts.
Click View table.
...................................................................................................................................................................................................
3 At the Fault Manager window, go to the Tools menu and select Filter.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-7
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance Open standard alarm tables
4 Select from the Custom filter drop-down list, the “acknowledged alarms by user filter”
and click View table.
...................................................................................................................................................................................................
5 At the Fault Manager window, go to the Tools menu and select Filter.
Result: The Alarm Filter window opens.
...................................................................................................................................................................................................
6 Select from the Custom filter drop-down list, the “unacknowledged alarm filter” and
click View table.
...................................................................................................................................................................................................
7 At the Fault Manager window, go to the Windows menu and select Tile.
E...................................................................................................................................................................................................
ND OF STEPS
Result:
As a result of this procedure the alarm tables are displayed.
....................................................................................................................................................................................................................................
13-8 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance
Purpose
This topic provides the procedure to open a predefined critical or a critical and major
alarm filter. This supresses all other alarms.
This filter should be activated at the moment that the alarm view window becomes
overloaded and therefore does not directly respond to the requests that are performed.
Related information
Refer to
• “Create filter - critical alarms” (p. 9-3), to create an alarm filter that filters all
critical alarms
• “Create filter - critical and major alarms” (p. 9-4), to create an alarm filter that
filters both the critical and major alarms.
1 Disconnect the alarm tables by selecting the Disconnect/Connect the alarm browser
button in each alarm table.
...................................................................................................................................................................................................
2 At the Fault Manager window, go to the Tools menu and select Filter.
Result: The Alarm Filter window opens.
...................................................................................................................................................................................................
3 If... then...
the alarm window is severely select from the Custom filter drop-down list, the
overloaded, “overload critical alarms only filter”and click View
table.
the response time of the window select from the Custom filter drop-down list, the
is becoming to slow, “overload critical + major alarms only filter”and
click View table.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-9
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance Open alarm overload filter
Result: A new Alarm Table window opens, displaying only those alarms that are
matching the selected criteria and suppressing all other alarms.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
13-10 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance
Purpose
This topic provides the procedure to close the predefined critical or critical and major
alarm overload filter.
Related information
There is no related information for this procedure.
2 Reconnect the standard alarm tables by selecting the Disconnect/Connect the alarm
browser button in each alarm table.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-11
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance
Purpose
This topic provides the procedure to acknowledge alarms.
Related information
There is no related information for this procedure.
Procedure
Perform the following steps to acknowledge an alarm:
...................................................................................................................................................................................................
1 In the Alarm Table, click on the alarm that you want to acknowledge.
...................................................................................................................................................................................................
Task result
A record is added to the alarm history, indicating that the alarm has been
acknowledged.
Important! Acknowledging the alarm only marks the alarm as acknowledged in the
element manager database; it does not affect the fault condition in the object itself.
...................................................................................................................................................................................................................................
13-12 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance
Overview
...................................................................................................................................................................................................................................
Purpose
This section includes the GUI procedures that can be used to suppress alarms on a
Node B or an RNC.
Alarm suppression can be useful when:
• Unimportant alarms keep on appearing on the OMC
• Certain Node Bs and/or RNCs are flooding the OMC with alarms. When this
happens, it might be useful to temporarily suppress all or part of the alarms of the
failing network element.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-13
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance
Purpose
This topic provides the GUI procedure that can be used to create an alarm suppression
filter for a Node B or an RNC.
After creating a suppression filter, this filter can be activated for a particular Node B or
RNC using the “Activate alarm suppression” (p. 13-16) procedure.
Related information
There is no related information for this procedure.
Procedure
Perform the following steps to create an alarm suppression filter for a Node B or an
RNC:
...................................................................................................................................................................................................
1 If... then...
alarm suppression should be use the Network Manager Window to navigate to a
created for a Node B, randomly selected NodeB object.
alarm suppression should be use the Network Manager Window to navigate to a
created for an RNC, randomly selected LRNC object.
...................................................................................................................................................................................................
2 Go to the Tools menu and select Alarm Filter Administration => Create
<LRNC/NodeB> Alarm Filter.
Result: The Create <LRNC/NodeB> Alarm Filter window appears.
...................................................................................................................................................................................................
3 In the Create <LRNC/NodeB> Alarm Filter window specify the file name that should
be used for this filter.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
13-14 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance Create an alarm suppression filter
...................................................................................................................................................................................................
5 In the window use the pull down list to insert an alarm supression definition criteria.
Reference: Use the “Alarm suppression attributes” (p. 13-26) topic for more
information about the possible filter settings.
...................................................................................................................................................................................................
6 If... then...
more alarm suppression definitions should return to step 4.
be added to the alarm suppression filter,
...................................................................................................................................................................................................
7 Press Finish to complete adding the new alarm filter to the existing list of filters.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-15
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance
Purpose
This topic provides the GUI procedure that can be used to activate an alarm
suppression filter on a Node B or an RNC.
After activating an alarm filter, a predefined set of alarms will be suppressed at the
Node B/RNC and therefore they will not be forwarded to the OMC anymore.
References
For more information on how you can create an alarm suppression filter, refer to the
“Create an alarm suppression filter” (p. 13-14) procedure.
Procedure
Perform the following steps to activate alarm suppression for a Node B or an RNC:
...................................................................................................................................................................................................
1 If... then...
alarm suppression should be use the Network Manager Window to navigate to a
activated for a Node B, randomly selected NodeB object.
alarm suppression should be use the Network Manager Window to navigate to a
activated for an RNC, randomly selected LRNC object.
...................................................................................................................................................................................................
2 Double click on the “arrow” icon to open the randomly selected NodeB or LRNC in
the Network Element table view window.
...................................................................................................................................................................................................
3 Go to the Tools menu and select Alarm Filter Administration => Apply
<LRNC/NodeB> Alarm Filter.
Result: The Apply <LRNC/NodeB> Alarm Filter window appears containing the
currently defined alarm suppression filters.
...................................................................................................................................................................................................
4 Select the alarm suppression filter that should be activated and press the Next button.
...................................................................................................................................................................................................................................
13-16 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance Activate alarm suppression
Result: A screen showing all the alarm suppression definitions of the selected
alarm filter appears.
...................................................................................................................................................................................................
5 If... then...
the alarm suppression filter definitions refer to the “Modify an alarm suppression
should still be updated before the filter filter” (p. 13-22)procedure.
should be activated,
...................................................................................................................................................................................................
7 From the list of FDNs, select the NodeB/LRNC for which the filter should be
activated.
Note: If needed more than one Node B or RNC can be selected.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-17
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance
Purpose
This topic provides the GUI procedure that can be used to deactivate alarm suppression
on a Node B or an RNC.
Related information
There is no related information for this procedure.
Procedure
Perform the following steps to deactivate alarm suppression on a Node B or an RNC:
...................................................................................................................................................................................................
1 If... then...
alarm suppression should be use the Network Manager Window to navigate to a
deactivated for a Node B, randomly selected NodeB object.
alarm suppression should be use the Network Manager Window to navigate to a
deactivated for an RNC, randomly selected LRNC object.
...................................................................................................................................................................................................
2 Go to the Tools menu and select Alarm Filter Administration => Apply
<LRNC/NodeB> Alarm Filter.
Result: The Apply Alarm Filter window appears containing the current list of
alarm filters.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
13-18 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance Deactivate alarm suppression
...................................................................................................................................................................................................
5 From the list of FDNs, select the NodeB/LRNC for which the filter should be
activated.
Note: If needed more than one Node B or RNC can be selected.
...................................................................................................................................................................................................
6 Press Finish to deactivate (unset) the filter settings on the selected NodeBs or RNCs.
Note: When the deactivation failed, the previously specified filter settings remain
active.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-19
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance
Purpose
This topic provides the GUI procedure that can be used to retrieve (get) the current
alarm suppression settings of a Node B or an RNC.
Related information
There is no related information for this procedure.
Procedure
Perform the following steps to retrieve the current alarm suppression settings of a
Node B or an RNC:
...................................................................................................................................................................................................
1 If... then...
alarm suppression should be use the Network Manager Window to navigate to
retrieved for a Node B, the NodeB object for which the settings should be
checked.
alarm suppression should be use the Network Manager Window to navigate to
retrieved for an RNC, the LRNC object for which the settings should be
checked.
...................................................................................................................................................................................................
2 Go to the Tools menu and select Alarm Filter Administration => Open
<LRNC/NodeB> Alarm Filter.
Result: The Open <LRNC/NodeB> Alarm Filter window appears containing the
currently defined alarm filters.
...................................................................................................................................................................................................
3 Select the alarm filter which contains the Node B or RNC identity for which you want
to view the current alarm settings.
An example of an activated filter name for RNC number 10 is RNC2.1_rnc10.
Note: If no filter is available no alarm suppression is active.
...................................................................................................................................................................................................................................
13-20 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance Retrieve current alarm suppression settings
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-21
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance
Purpose
This topic provides the GUI procedure that can be used to modify the alarm definitions
of an existing alarm Node B or RNC suppression filter.
Note: This procedure only modifies the suppression filter definitions on the OMC. The
modifications that are made to a filter are not automatically activated in the Node Bs
or RNCs where this filter is currently activated.
Related information
To apply the modified filter to a Node B or RNC, use the “Activate alarm suppression”
(p. 13-16) procedure to overrule the current Node B or RNC settings.
Procedure
Perform the following steps to create an alarm suppression filter for a Node B or an
RNC:
...................................................................................................................................................................................................
1 If... then...
alarm suppression should be use the Network Manager Window to navigate to a
modified for a Node B, randomly selected NodeB object.
alarm suppression should be use the Network Manager Window to navigate to a
modified for an RNC, randomly selected LRNC object.
...................................................................................................................................................................................................
2 Go to the Tools menu and select Alarm Filter Administration => Open
<LRNC/NodeB> Alarm Filter.
Result: The Open <LRNC/NodeB> Alarm Filter window appears containing the
currently defined alarm filters.
...................................................................................................................................................................................................
3 Using the pull-down list navigate to the filter that should be modified.
...................................................................................................................................................................................................................................
13-22 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance Modify an alarm suppression filter
...................................................................................................................................................................................................
5 If... then...
a filter definition should be added press Add to add the new alarm filter
definition to the existing list of filters.
a filter definition should be deleted press Delete to remove the alarm filter
definition from the existing list of filters.
Reference: Use the “Alarm suppression attributes” (p. 13-26) topic for more
information about the possible filter settings.
...................................................................................................................................................................................................
6 If... then...
more types of alarm suppression return to step 4.
definitions should be added or removed
from the alarm suppression filter,
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-23
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance
Purpose
This topic provides the procedure that can be used to delete an existing alarm
suppression filter.
Related information
There is no related information for this procedure.
Procedure
Perform the following steps to delete an alarm suppression filter:
...................................................................................................................................................................................................
1 If... then...
an alarm suppression should be use the Network Manager Window to navigate to a
deleted that has been defined to randomly selected NodeB object.
suppress alarms on a Node B,
an alarm suppression should be use the Network Manager Window to navigate to a
deleted that has been defined to randomly selected LRNC object.
suppress alarms on a RNC,
...................................................................................................................................................................................................
2 Go to the Tools menu and select Alarm Filter Administration => Delete
<LRNC/NodeB> Alarm Filter.
Result: The Delete <LRNC/NodeB> Alarm Filter window appears containing the
currently defined alarm filters.
...................................................................................................................................................................................................
3 Using the pull-down list navigate to the filter that should be deleted.
...................................................................................................................................................................................................................................
13-24 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance Delete an alarm suppression filter
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-25
Issue 1, August 2007 See notice on first page
Corrective maintenance - alarm surveillance
Overview
This topic provides the description of the attribute values that are used for controlling
alarm suppression on a Node B or an RNC.
Criteria settings
The criteria settings are used to determine the alarms that should be suppressed for a
Node B or an RNC.
For the criteria the following settings are applicable:
Settings Description
severity Suppress all alarms of a specified severity
specificProblem Suppress all alarms with a specified
specificProblem.
FilterCriteria settings
The filterCriteria settings are used to determine the alarms that should be suppressed.
For the filterCriteria the following settings are applicable:
Scope settings
The scope settings are used for determining whether an alarm should be suppressed for
an element, a unit or for a certain group of alarms.
...................................................................................................................................................................................................................................
13-26 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - alarm surveillance Alarm suppression attributes
Settings Description
class Suppress all alarms of a specified alarm class
(group of alarms)
instance Suppress all alarms belonging to a specific
instance (object) of a Node B or RNC
element Suppress all alarms belonging to a specific Node
B or RNC.
FilterApplication settings
The filterApplication settings are used to define the name of the unit for the alarm(s)
that should be suppressed.
For the filterApplication the following settings are applicable:
Notes:
1. The instance and the class filterapplication scopes can only be combined with the filtercriteria equal to
specificProblem
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 13-27
Issue 1, August 2007 See notice on first page
14 14
Corrective maintenance - OMC
alarm clearance procedures
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter contains the fault clearance procedures that are related OMC alarms
which have been generated due to problems in the UTRAN.
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-1
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when there
is a NE communication establishment failure for receiving events or to synchronize
alarms.
Description
There is no connectivity between the OMC and the NE to receive events or to perform
alarm synchronizations. This alarm is created either on system startup or on NE
creation.
Severity
CRITICAL
Probable cause
• The network element is down
• Problems in the LAN network
• Problems in the transmission network between the OMC-UPS and the network
element.
System impact
• Autonomous NE updates (state changes, alarms, etc.) will not appear on the system
for that NE
• Alarm synchronization operation will fail for that NE
• The system will reflect the last known state for that NE before the communication
was lost.
• Lost calls due to a failing network element
• Technician maintenance requests from the OMC-UPS will be denied
Related information
There is no related information for this procedure.
...................................................................................................................................................................................................................................
14-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance NE communication establishment failure
procedures
To clear alarm
...................................................................................................................................................................................................
1 If the alarm occurs for more than one network element, check the network
(LAN/WAN) connections.
...................................................................................................................................................................................................
2 If the heartbeat failure is indicated for a given NE, check the appropriate fault
clearance procedures for the different heartbeat failures.
E...................................................................................................................................................................................................
ND OF STEPS
1 At the RNC, check whether RNC processes are initialized by RCC and AMW (system
software)
Result: After initialization the BSC OAM process is running on either FMS1 or
FMS2.
...................................................................................................................................................................................................
2 Check the TCP/IP communication between the RNC and the OMC-UPS.
FMS 1 and FMS 2 should be able to ping the OMC-UPS External IP address.
Similarly, the OMC-UPS should be able to ping the external FMS IP address
provisioned.
Additionally the RNC’s FWRVCVM IP address needs to be pingable.
If it is not possible to ping the OMC-UPS and/or the FMS check:
• Infrastructure cable connections and cable connectors
• Ethernet-Switch Port set up in the RNC
• IP address of OMC-UPS of /etc/hosts as configured during RNC installation
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-3
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance NE communication establishment failure
procedures
3 Check the throughput of the actual Itf-r link. Check the Transport Network or
connection and throughput to ensure no dropped packets are occurring.
...................................................................................................................................................................................................
4 Contact Alcatel-Lucent customer support to check the database as installed in the RNC
and in the OMC-UPS (data scripts). Errors when populating data lead to inabilities for
the registration use case to complete.
E...................................................................................................................................................................................................
ND OF STEPS
1 Check the TCP/IP communication between the Node B and the OMC-UPS.
The OMC-UPS should be able to ping the external Node B OAM&P IP address.
If it is not possible to ping the Node B, check:
• Infrastructure cable connections and cable connectors
• Correct Configuration of DHCP-Server, from which the NodeB retrieves its IP
address as well as netmasks, etc.
• Correct setup of IP interfaces on LIU and UMC of the NodeB
• Correct setup of ERM-Module in PSAX connected to NodeB.
...................................................................................................................................................................................................
2 Check the throughput of the actual Itf-b link. Check the Transport Network or
connection and throughput to ensure no dropped packets are occurring.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
14-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance NE communication establishment failure
procedures
1 Check the TCP/IP communication between the CGF or SGSN and the OMC-UPS.
The OMC-UPS should be able to ping the external IP address of the NE.
• Ping the CGF or SGSN from the OMC-UPS server
...................................................................................................................................................................................................
2 If it is not possible to ping the CGF or SGSN, clear the IPsec settings on both the
OMC-UPS and the NE then ping again to determine if there are possible network
problems.
To clear the IPSec settings:
• SSH to the NE and run “showIPsec ca” or
• From the OMC-UPS server /omc/OMC-U/scripts/ directory run “./disable_ipsec.sh
ipaddress”
...................................................................................................................................................................................................
3 If the problem persists, verify that the OMC-UPS IP address is configured for SNMP
Management, that the system IP address is valid and that the Community String is
enabled.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-5
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when a
predefined overload threshold was exceeded for a specified NE.
Description
This overload condition occurs when the system is receiving more events from the NE
than the number specified by the threshold.
Severity
MINOR, MAJOR or CRITICAL based on overload severity.
Probable cause
• The system is receiving events over a predefined threshold
• The network element performs a reboot
• The network element is in an unstable state
System impact
• The system performance may be affected when receiving more events that it can
handle at a given time. This impact depends on the threshold levels being exceeded
and the load of the system when the overload condition is raised.
• Autonomous system updates (state changes, alarms, etc.) will not appear on the
OMC-UPS.
• The OMC-UPS will reflect the last known state of the system before the event
buffer became overloaded (shadowed mode).
Related information
Thresholds can be established per NE type and per event type (alarms and non-alarms
event types). Thresholds are defined by the detection and abatement levels, which are
both the same.
By default the system takes the following corrective actions to abate the overload
condition. These corrective actions depend on the threshold being exceeded
• Minor: no corrective actions are taken by the system.
• Major: discard all the events coming from this NE if it is a normal priority one.
• Critical: discard all the events coming from this NE whether the NE is high or
normal priority.
...................................................................................................................................................................................................................................
14-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance Event-driven overload on single NE
procedures
If an overload condition starts at a given severity, all the actions defined for each lower
severity will be executed before starting the corrective actions for the current severity.
For example, if the overload condition starts at critical severity, all the corrective
actions defined for minor and major severity will be executed before proceeding with
those actions defined for the critical level. Events will be processed again once the
overload condition of the given severity is abated. Events discarded by the corrective
actions will be processed again when the NE is re-synchronized.
To clear alarm
Contact the system administrator and alert them about the problem. The system
administrator may need to perform the following actions:
...................................................................................................................................................................................................
1 Analyze the message to determine the NE causing the overload. Then check if this NE
has any kind of problem that makes it to send an excess of events. Set the NE to
unmanage state to stop receiving burst of events from it.
...................................................................................................................................................................................................
2 Check the overload threshold levels are correctly established. They can have too low
values so the overload conditions are raised too soon. Change the thresholds if they do
not fit your environment.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-7
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance
procedures
Heartbeat failed
...................................................................................................................................................................................................................................
Purpose
This procedure provides instructions for clearing the fault that was caused when an NE
heartbeat fails.
Description
This alarm is generated when the heartbeat synchronization signal between the
indicated Network element and the OMC is lost. This happens when you cannot access
the NE or when there is a NE type or NE version mismatch. The default parameter for
heartbeat frequency is one minute.
Severity
Critical when there is a NE type mismatch and Major when there is an NE version
mismatch.
Probable cause
• The network element is down
• Problems in the LAN network
• Problems in the transmission network between the OMC-UPS and the network
element.
System impact
• Lost calls due to a failing network element.
• Alarms and events from the NE are lost
• Technician maintenance request from the management system will be denied.
• Autonomous system updates such as state changes will not appear on the OMC.
• The OMC will reflect the last known state of the system before the communication
was lost (shadowed mode).
Related information
There is no related information for this procedure.
• ProbableCause
• SpecificProblems
If the values in these fields are not retained, the alarm is not cleared and a new alarm
is generated with a new value in the SpecificProblems field.
To clear alarm
...................................................................................................................................................................................................
2 After the connection is restored, perform a full audit and synchronize the alarm on the
affected NE.
E...................................................................................................................................................................................................
ND OF STEPS
1 At the RNC, check whether the RNC processes are initialized by RCC and AMW
(system software).
Result: After initialization the BSC OAM process is running on either FMS1 or
FMS2.
...................................................................................................................................................................................................
2 Check the TCP/IP communication between the RNC and the OMC-UPS.
FMS 1 and FMS 2 should be able to ping the OMC-UPS External IP address.
Similarly, the OMC-UPS should be able to ping the external FMS IP address
provisioned.
Additionally the RNC’s FWRVCVM IP address needs to be pingable.
If it is not possible to ping the OMC-UPS and/or the FMS check:
• Infrastructure cable connections and cable connectors
• Ethernet-Switch Port set up in the RNC
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-9
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance Heartbeat failed
procedures
3 Check the throughput of the actual Itf-r link. Check the Transport Network or
connection and throughput to ensure no dropped packets are occurring.
...................................................................................................................................................................................................
4 Contact Alcatel-Lucent customer support to check the database as installed in the RNC
and in the OMC-UPS (data scripts). Errors when populating data lead to inabilities for
the registration use case to complete.
E...................................................................................................................................................................................................
ND OF STEPS
1 Check the TCP/IP communication between the Node B and the OMC-UPS.
The Node B should be able to ping the OMC-UPS external IP address.
If it is not possible to ping the Node B, check:
• Infrastructure cable connections and cable connectors
• Correct Configuration of DHCP-Server, from which the NodeB retrieves its IP
address as well as netmasks, etc.
• Correct setup of IP interfaces on LIU and UMC of the NodeB
• Correct setup of ERM-Module in PSAX connected to NodeB.
...................................................................................................................................................................................................
2 Check the throughput of the actual Itf-b link. Check the Transport Network or
connection and throughput to ensure no dropped packets are occurring.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
14-10 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance Heartbeat failed
procedures
1 Check the TCP/IP communication between the CGF or SGSN and the OMC-UPS.
The OMC-UPS should be able to ping the external IP address of the NE.
• Ping the CGF or SGSN from the OMC-UPS server
...................................................................................................................................................................................................
2 If it is not possible to ping the CGF or SGSN, clear the IPsec settings on both the
OMC-UPS and the NE then ping again to determine if there are possible network
problems.
To clear the IPSec settings:
• SSH to the NE and run “showIPsec ca” or
• From the OMC-UPS server /omc/OMC-U/scripts/ directory run “./disable_ipsec.sh
ipaddress”
...................................................................................................................................................................................................
3 If the problem persists, verify that the OMC-UPS IP address is configured for SNMP
Management, that the system IP address is valid and that the Community String is
enabled.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-11
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when a NE
Heartbeat fails (NE type mismatch)
Description
The management system is not able to contact the network element, because the
contacted network element does not match the expected network element type.
Important! This alarm must be cleared manually.
Severity
CRITICAL
Probable cause
• The IP address entered on the OMC-UPS has been set incorrectly
• Problems in the DHCP pool.
System impact
• Technician maintenance requests from the management system will be denied
• Autonomous system updates (state changes, alarms, PM, etc.) will not appear on
the management system.
• The OMC will reflect the last known state of the system before the communication
was lost (shadowed mode).
Related information
There is no related information for this procedure.
To clear alarm
...................................................................................................................................................................................................
1 At the OMC, verify if the specified type matches the expected type of the network
element.
...................................................................................................................................................................................................................................
14-12 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance Heartbeat failed: NE type mismatch
procedures
...................................................................................................................................................................................................
2 At the OMC, verify if the specified IP address matches the actual IP address of the
network element.
...................................................................................................................................................................................................
3 At the OMC, set the network element to UNMANAGE state and delete the network
element.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-13
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when a NE
heartbeat fails due to NE version mismatch.
Description
The OMC is not able to contact the network element, because the software version
running on the contacted network element does not match the expected software
version.
Important! This alarm must be cleared manually.
Severity
MAJOR
Probable cause
Network element runs on a different software version then the OMC-UPS currently
supports.
System impact
• Technician maintenance requests from the management system will be denied.
• Autonomous system updates such as state changes will not appear on the OMC.
• The OMC will reflect the last known state of the system before the communication
was lost (shadowed mode).
Related information
There is no related information for this procedure.
To clear alarm
...................................................................................................................................................................................................
1 At the OMC, check whether the specified software version matches the expected
software version of the network element. If the software version has been set
incorrectly, set the network element to UNMANAGE state and modify the software
version.
...................................................................................................................................................................................................................................
14-14 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance Heartbeat failed: NE version mismatch
procedures
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-15
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when the
NE communication parameters are invalid.
Description
The communication parameters provided for this network element are not correct.
Severity
CRITICAL
Probable cause
Communications protocol error.
System impact
• Autonomous NE updates (state changes, alarms, etc.) will not appear on the system
for that NE
• Alarm synchronization operation will fail for that NE
• The system will reflect the last known state for that NE before the communication
was lost.
Related information
There is no related information for this procedure.
To clear alarm
...................................................................................................................................................................................................
2 If all communication parameters are correct, contact the system administrator and alert
them to this alarm
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
14-16 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when the
maximum number of incoming and not yet processed events per a specific NE has
been exceeded.
Description
The OMC has reached the threshold value for the maximum number of incoming and
not yet processed events for the reported network element.
Important! This alarm must be cleared manually. Alarm Correlation can also use
Auto Detect Manual Clear (ADMC) alarms.
Severity
MAJOR
Probable cause
• The NE performs a reboot
• The NE is in unstable phase
System impact
• Technician maintenance request from the OMC will be denied.
• Autonomous system updates such as state changes will not appear on the OMC.
• The OMC will reflect the last known state of the system before the event buffer
became overloaded (shadowed mode).
Related information
There is no related information for this procedure.
To clear alarm
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-17
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance Event capacity exceeded
procedures
...................................................................................................................................................................................................
2 At the OMC, verify if there are alarms that indicate the reason for the NE overload.
...................................................................................................................................................................................................
4 From the Network Manager, select the NE and perform an alarm synchronization.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
14-18 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault caused when the alarm
related information is out of sync.
Description
This alarm is raised when the alarm synchronization or an event has failed to update
alarms.
Severity
Major
Probable cause
• Failure on the creation or update of an alarm from either the user or from a fault
event
• Failure updating alarms on an alarm synchronization process
• Failure on the update of counters of the Alarm Summary
System impact
The alarm information displayed for this NE may not represent the current status.
Related information
There is no related information for this procedure.
To clear alarm
...................................................................................................................................................................................................
1 Analyze the message to determine the problem. Check the probable cause of the alarm.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-19
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance Alarm information out of sync
procedures
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
14-20 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when the
OMC is performing an alarm synchronization for an NE. The alarms reflected for this
network element are not synchronized with the network element until the operation is
complete.
Description
When an alarm synchronization is initiated on a network element, the OMC raises a
suspect alarm on this NE to indicate that the alarm synchronization is in progress.
Severity
WARNING when the alarm synchronization is in progress and MAJOR if
synchronization fails.
Probable cause
The network connection with the network element has failed.
System impact
• Autonomous NE updates such as state changes will not take place until the alarm
synchronization finishes.
• Further alarm synchronization requests on the same NE will not take place.
Related information
There is no related information for this procedure.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-21
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance NE alarm synchronization in progress
procedures
To clear alarm
...................................................................................................................................................................................................
1 Acknowledge the alarm and wait until the synchronization is complete. A suspect alarm
cannot be cleared manually; however, the alarm will be cleared automatically when the
alarm synchronization is completed successfully. If the synchronization is not
completed successfully, the alarm will be cleared on the next successful
synchronization on the specified NE.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
14-22 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when there
is a NE communication establishment failure for receiving events or to synchronize
alarms.
Description
There is no connectivity between the OMC and the NE to receive events or to perform
alarm synchronizations. This alarm is created either on system startup or on NE
creation.
Severity
CRITICAL
Probable cause
• The network element is down
• Problems in the LAN network
• Problems in the transmission network between the OMC-UPS and the network
element.
System impact
• Autonomous NE updates (state changes, alarms, etc.) will not appear on the system
for that NE
• Alarm synchronization operation will fail for that NE
• The system will reflect the last known state for that NE before the communication
was lost.
• Lost calls due to a failing network element
• Technician maintenance requests from the OMC-UPS will be denied
Related information
There is no related information for this procedure.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-23
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance NE communication establishment failure
procedures
To clear alarm
...................................................................................................................................................................................................
1 If the alarm occurs for more than one network element, check the network
(LAN/WAN) connections.
...................................................................................................................................................................................................
2 If the heartbeat failure is indicated for a given NE, check the appropriate fault
clearance procedures for the different heartbeat failures.
E...................................................................................................................................................................................................
ND OF STEPS
1 At the RNC, check whether RNC processes are initialized by RCC and AMW (system
software)
Result: After initialization the BSC OAM process is running on either FMS1 or
FMS2.
...................................................................................................................................................................................................
2 Check the TCP/IP communication between the RNC and the OMC-UPS.
FMS 1 and FMS 2 should be able to ping the OMC-UPS External IP address.
Similarly, the OMC-UPS should be able to ping the external FMS IP address
provisioned.
Additionally the RNC’s FWRVCVM IP address needs to be pingable.
If it is not possible to ping the OMC-UPS and/or the FMS check:
• Infrastructure cable connections and cable connectors
• Ethernet-Switch Port set up in the RNC
• IP address of OMC-UPS of /etc/hosts as configured during RNC installation
...................................................................................................................................................................................................................................
14-24 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance NE communication establishment failure
procedures
3 Check the throughput of the actual Itf-r link. Check the Transport Network or
connection and throughput to ensure no dropped packets are occurring.
...................................................................................................................................................................................................
4 Contact Alcatel-Lucent customer support to check the database as installed in the RNC
and in the OMC-UPS (data scripts). Errors when populating data lead to inabilities for
the registration use case to complete.
E...................................................................................................................................................................................................
ND OF STEPS
1 Check the TCP/IP communication between the Node B and the OMC-UPS.
The OMC-UPS should be able to ping the external Node B OAM&P IP address.
If it is not possible to ping the Node B, check:
• Infrastructure cable connections and cable connectors
• Correct Configuration of DHCP-Server, from which the NodeB retrieves its IP
address as well as netmasks, etc.
• Correct setup of IP interfaces on LIU and UMC of the NodeB
• Correct setup of ERM-Module in PSAX connected to NodeB.
...................................................................................................................................................................................................
2 Check the throughput of the actual Itf-b link. Check the Transport Network or
connection and throughput to ensure no dropped packets are occurring.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
ND OF STEPS
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-25
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance NE communication establishment failure
procedures
1 Check the TCP/IP communication between the CGF or SGSN and the OMC-UPS.
The OMC-UPS should be able to ping the external IP address of the NE.
• Ping the CGF or SGSN from the OMC-UPS server
...................................................................................................................................................................................................
2 If it is not possible to ping the CGF or SGSN, clear the IPsec settings on both the
OMC-UPS and the NE then ping again to determine if there are possible network
problems.
To clear the IPSec settings:
• SSH to the NE and run “showIPsec ca” or
• From the OMC-UPS server /omc/OMC-U/scripts/ directory run “./disable_ipsec.sh
ipaddress”
...................................................................................................................................................................................................
3 If the problem persists, verify that the OMC-UPS IP address is configured for SNMP
Management, that the system IP address is valid and that the Community String is
enabled.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
14-26 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when a NE
event could not be processed
Description
An network element could not be processed because the event type that was passed on
was incorrect.
Severity
WARNING
Probable cause
Lock could not be acquired, or the management system detected that one MO for
which one or more events have been received, is not found in the management system
database.
System impact
The OMC and the network element are not 100% synchronized. Any attribute value
change related to MO not found in OMC database could not be handled.
Related information
Important! This alarm must be cleared manually. Alarm Correlation can also use
alarms with nature ADMC.
To clear alarm
...................................................................................................................................................................................................
2 Using the System Alarm window, select the NE for which the alarm has been reported
and perform an alarm synchronization.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-27
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance NE event could not be processed
procedures
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
14-28 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the Synchronization source mismatch
alarm.
Description
OMC-UPS has detected that a configuration value was changed on the network
element.
Important! This alarm must be cleared manually. Alarm Correlation can also use
Auto Detect Manual Clear (ADMC) alarms.
Severity
Warning
Probable cause
The configuration data on the network has been altered directly without using
OMC-UPS.
System impact
• Technician maintenance request from the management system will be denied.
• Autonomous system updates (state changes, alarms, etc.) will not appear on the
management system.
• The management system will reflect the last known state of the system before the
event buffer became overloaded (shadowed mode).
• The OMC-UPS and the network element are not fully synchronized.
Related information
There is no related information for this procedure.
To clear alarm
...................................................................................................................................................................................................
1 At the OMC, verify if there are alarms that indicate why the NE is creating the
overload.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-29
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance Synchronization source mismatch
procedures
...................................................................................................................................................................................................
3 From the System Alarm window in the network manager, select Node B or RNC for
which the alarm has been reported and perform an alarm synchronization (Sync NE
Alarms).
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
14-30 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when the
PM result files cannot be deleted from the NE.
Description
This alarm is only applicable when the OMC is designed to delete the PM result files
on the NE after the successfully retrievals.
Severity
WARNING
Probable cause
Remote node transmission error
System impact
The OMC may collect the same PM result file twice. There is no direct impact on the
OMC, but other management systems that process the performance management may
be lacking input.
Related information
There is no related information for this procedure.
To clear alarm
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-31
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when the
PM result files cannot be retrieved from certain NEs.
Description
Unable to automatically retrieve the PM data from the indicated network element.
Severity
WARNING
Probable cause
Remote node transmission error.
System impact
There is no direct impact on the OMC, but other management systems that process the
performance management may be lacking input.
Related information
There is no related information for this procedure.
To clear alarm
...................................................................................................................................................................................................
1 At the OMC-UPS, verify if there are alarms that indicate that there are communication
problems with the NE.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
14-32 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance Unable to automatically retrieve PM data from NE
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, startup and FTP or SFTP session to the NE for which the problem
has been reported and manually download the missing measurements to the OMC-UPS.
...................................................................................................................................................................................................
4 If the PM files are automatically forwarded to the NMS, a manual FTP session should
be started to upload the missing PM files to the NMS.
...................................................................................................................................................................................................
5 At the OMC, verify if the FTP address, FTP port number, directory, user name and
password match the data programmed on the failing NE.
...................................................................................................................................................................................................
6 At the OMC server, ping the FTP address to determine if there are possible network
problems.
...................................................................................................................................................................................................
7 At the OMC server, manually FTP to the NE using the same IP address, same login
and password an to the same directory.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-33
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance
procedures
Purpose
This procedure provides instructions for clearing the fault that was caused when a NE
state was set to unmanaged.
Description
The state of the NE is set to unmanaged. In the unmanaged state, the NE continues to
provide service but the communication between management system and the NE is
stopped. The communication can be restored whenever needed.
Severity
WARNING
Probable cause
The network element has been changed into unmanaged state.
System impact
• The OMC closes the connection with the NE. This implies that the operator will be
unable to perform any operation on the NE or to receive any notification from it.
• Loss of communication to the NE and corrupt data. Any operation that implies
communication with the NE will be rejected. The alarms shown for this NE may
not represent the current alarm status.
• Technician maintenance requests from the OMC-UPS will not be send to the NE.
• The system will reflect the last known state of the system before the
communication was lost.
Related information
There is no related information for this procedure.
...................................................................................................................................................................................................................................
14-34 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - OMC alarm clearance Unmanaged state set to NE
procedures
To clear alarm
...................................................................................................................................................................................................
1 Change the unmanaged state to managed, so the NE can be registered again. A suspect
alarm cannot be cleared manually; however, the alarm will clear automatically once the
problem is fixed.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 14-35
Issue 1, August 2007 See notice on first page
Corrective maintenance - OMC alarm clearance
procedures
Reference
Since the OMC alarm clearance procedures that are not listed in this chapter are
mainly related to OMC system alarms and not to the UTRAN, these fault clearance
procedures have been included in the:
Lucent OMC-UPS Operations, Administration, Maintenance, and Provisioning,
401-380-022 manual.
...................................................................................................................................................................................................................................
14-36 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
15 15
Corrective maintenance - Node
B alarm clearance procedures
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter provides the procedures to clear Node B alarms that are raised on the
OMC.
Related information
For more related information about this topic, refer to:
• Lucent UMTS Macrocell Indoor, Operation, Administration and Maintenance for
+24V, 401-382-462
• Lucent UMTS Modular Cell Outdoor, Operation, Administration and Maintenance
for +24V, 401-382-760
• Lucent UMTS Macrocell Compact, Operation, Administration and Maintenance for
+24V, 401-382-961
• Lucent UMTS Microcell (Type M), Operation, Administration and Maintenance for
+24V, 401-382-966
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-1
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Overview
procedures
ALDController_softwareDownloadFailure 15-27
ALDController_softwareFailure 15-29
ALDController_softwareVersionMismatch 15-31
ALDController_temperatureOutOfRange 15-33
ALDController_unknownDeviceDetected 15-35
AlarmHub alarms 15-37
AlarmHub_communicationFailure 15-38
AlarmHub_externalAlarmPort0 15-40
AlarmHub_externalAlarmPort1 15-42
AlarmHub_externalAlarmPort2 15-44
AlarmHub_externalAlarmPort3 15-46
AlarmHub_externalAlarmPort4 15-48
AlarmHub_externalAlarmPort5 15-50
AlarmHub_externalAlarmPort6 15-52
AlarmHub_externalAlarmPort7 15-54
AmpShelfFan alarms 15-56
AmpShelfFan_equipmentFault 15-57
CPC alarms 15-59
CPC_communicationFailure 15-60
CPC_configurationMismatch 15-62
CPC_dCOutputFailure 15-64
CPC_lowDCInput 15-66
CPC_overTemperature 15-68
CPRIPort alarms 15-70
CPRIPort_fibreLOF 15-71
CPRIPort_fibreLOS 15-72
CPRIPort_fibreRAI 15-73
CPRIPort_fibreSAPDefect 15-74
CPRIPort_fibreSigLow 15-75
CPRIPort_transmitterSwitchOff 15-76
CTU alarms 15-78
CTU_boardGenericMismatch 15-80
...................................................................................................................................................................................................................................
15-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Overview
procedures
CTU_clockFailure15Mhz 15-82
CTU_clockFailure30_72Mhz 15-84
CTU_communicationFailure 15-86
CTU_configurationMismatch 15-88
CTU_flywheelStart 15-90
CTU_flywheelTimeLimitReached 15-92
CTU_frequencyOutOfRange 15-94
CTU_gPSAntennaFailure 15-96
CTU_gPSReceiverFailure 15-98
CTU_hardwareModelMismatch 15-100
CTU_inactive 15-102
CTU_initialisationFailure 15-104
CTU_lossOfClockSourceSynchronisation 15-106
CTU_maintenanceRequested 15-108
CTU_messageThrottleOn 15-110
CTU_noOMConfiguredInDatabase 15-112
CTU_phaseLockLoopFailure 15-114
CTU_selfTestFailure 15-116
CTU_syncSourceMismatch 15-118
CTU_temperatureOutOfRange 15-120
CTU_timeOfDayDataInvalid 15-122
CTU_underTemperature 15-124
CTU_waitingForClockSignal 15-126
Cell alarms 15-128
Cell_blockRequestTimerExpiry 15-129
Cell_configurationMismatch 15-131
Cell_powerTestThresholdExceeded 15-133
Cell_rETNotSupported 15-136
Cell_receiveAntennaTestThresholdExceededOnAllAntennas 15-138
Cell_receiveAntennaTestThresholdExceededOnAntenna1 15-140
Cell_receiveAntennaTestThresholdExceededOnAntenna2 15-142
Cell_temporarySoftwareFailure 15-144
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-3
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Overview
procedures
...................................................................................................................................................................................................................................
15-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Overview
procedures
Filter_communicationFailure 15-202
Filter_configurationMismatch 15-204
Filter_dCConverterFailure 15-206
Filter_hardwareModelMismatch 15-208
Filter_localConfigurationFailure 15-210
Filter_unknownHardwareModel 15-212
Frame alarms 15-214
Frame_cabinetDoorOpen 15-215
Frame_cabinetHeaterFailure 15-217
Frame_fanFault 15-219
Frame_heatManagementSystemCompressorFailure 15-221
Frame_heatManagementSystemControllerFailure 15-223
Frame_overTemperature 15-225
Frame_underTemperature 15-227
GRS alarms 15-229
GRS_configurationMismatch 15-230
GRS_firstPortNumberAlreadyInUse 15-232
GRS_gPSAntennaFailure 15-234
GRS_gPSAntennaPositionUnknown 15-236
GRS_gPSReceiverFailure 15-238
GRS_gPSReceiverUnavailable 15-240
GRS_satelliteHealthyThresholdExceededForAllVisibleSatellites 15-241
GRS_secondPortNumberAlreadyInUse 15-243
GRS_selfSurveyFailed 15-245
IMAGroup alarms 15-247
IMAGroup_criticalGroupAlarm 15-248
IMAGroup_criticalGroupConfigurationAlarm 15-250
IMAGroup_majorGroupAlarm 15-252
IMAGroup_noncriticalGroupConfigurationAlarm 15-254
IOU alarms 15-256
IOU_communicationFailure 15-258
IOU_externalAlarmPort0 15-260
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-5
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Overview
procedures
IOU_externalAlarmPort1 15-262
IOU_externalAlarmPort10 15-264
IOU_externalAlarmPort11 15-266
IOU_externalAlarmPort12 15-268
IOU_externalAlarmPort13 15-270
IOU_externalAlarmPort14 15-272
IOU_externalAlarmPort15 15-274
IOU_externalAlarmPort16 15-276
IOU_externalAlarmPort17 15-278
IOU_externalAlarmPort18 15-280
IOU_externalAlarmPort19 15-282
IOU_externalAlarmPort2 15-284
IOU_externalAlarmPort20 15-286
IOU_externalAlarmPort21 15-288
IOU_externalAlarmPort22 15-290
IOU_externalAlarmPort23 15-292
IOU_externalAlarmPort24 15-294
IOU_externalAlarmPort25 15-296
IOU_externalAlarmPort26 15-298
IOU_externalAlarmPort27 15-300
IOU_externalAlarmPort28 15-302
IOU_externalAlarmPort29 15-304
IOU_externalAlarmPort3 15-306
IOU_externalAlarmPort30 15-308
IOU_externalAlarmPort31 15-310
IOU_externalAlarmPort4 15-312
IOU_externalAlarmPort5 15-314
IOU_externalAlarmPort6 15-316
IOU_externalAlarmPort7 15-318
IOU_externalAlarmPort8 15-320
IOU_externalAlarmPort9 15-322
Iub interface alarms 15-324
...................................................................................................................................................................................................................................
15-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Overview
procedures
IubInterface_rNCCommunicationLost 15-325
NodeB alarms 15-327
NodeB_alarmDefFileCorrupt 15-328
NodeB_alarmDefFileMissing 15-330
NodeB_databaseCleared 15-332
NodeB_databaseRestoredFromSnapshot 15-335
NodeB_filesystemNearingCapacity 15-337
NodeB_filesystemObjectCorrupt 15-339
NodeB_invalidSecurityDataDetected 15-341
NodeB_ipfwNatRulesAltered 15-343
NodeB_nodeBTypeMismatch 15-345
NodeB_snapshotFailed 15-347
NodeB_unauthorizedLoginAttempt 15-349
NodeB_userPasswordLoginAttempt 15-351
OCM alarms 15-353
OCM_boardGenericMismatch 15-354
OCM_clockFailure30_72MHz 15-356
OCM_communicationFailure 15-357
OCM_initialisationFailure 15-359
OCM_lossOfForwardBusLink 15-360
OCM_lossOfPulse 15-361
OCM_missingconfigurationData 15-362
OCM_selfTestFailure 15-364
OM alarms 15-365
OM_clockFailure15Mhz 15-366
OM_configurationMismatch 15-368
OM_frequencyOutOfRange 15-370
OM_hardwareModelMismatch 15-372
OM_inactive 15-375
OM_maintenanceRequested 15-377
OM_phaseLockLoopFailure 15-380
OM_temperatureOutOfRange 15-382
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-7
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Overview
procedures
OM_underTemperature 15-384
RETActuator alarms 15-386
RETActuator_actuatorJam 15-387
RETActuator_calibrationLost 15-389
RETActuator_communicationFailure 15-391
RETActuator_deviceTypeMismatch 15-393
RETActuator_hardwareFailure 15-394
RETActuator_positionLost 15-396
RETActuator_softwareFailure 15-398
RETActuator_tiltAngleOutOfRange 15-400
RFHead alarms 15-402
RFHead_boardGenericMismatch 15-404
RFHead_clockFailure 15-406
RFHead_communicationFailure 15-407
RFHead_criticalTransmitterAlarm 15-409
RFHead_dCInputFailure 15-411
RFHead_diversityImbalance 15-412
RFHead_externalAlarmPort0 15-414
RFHead_externalAlarmPort1 15-415
RFHead_externalAlarmPort2 15-416
RFHead_externalAlarmPort3 15-417
RFHead_externalAlarmPort4 15-418
RFHead_externalAlarmPort5 15-419
RFHead_fibreLOF 15-420
RFHead_fibreLOS 15-422
RFHead_fibreRAI 15-424
RFHead_fibreSAPDefect 15-426
RFHead_fibreSigLow 15-428
RFHead_initialisationFailure 15-430
RFHead_noncriticalTransmitterAlarm 15-431
RFHead_overTemperature 15-433
RFHead_rFOverdrive 15-435
...................................................................................................................................................................................................................................
15-8 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Overview
procedures
RFHead_receiver1Failure 15-436
RFHead_receiver2Failure 15-437
RFHead_receiverFailure 15-438
RFHead_selfTestFailure 15-439
RFHead_softwareFailure 15-440
RFHead_temperatureOutOfRange 15-441
RFHead_txActivationFailure 15-443
RFHead_underTemperature 15-444
RFHead_vSWRAlarm 15-445
RFHead_warmup 15-446
Radio alarms 15-447
Radio_applicationInsane 15-449
Radio_boardGenericMismatch 15-450
Radio_clockFailure30_72Mhz 15-452
Radio_communicationFailure 15-455
Radio_configurationMismatch 15-457
Radio_criticalGainFailure 15-459
Radio_digitalClippingDetected 15-461
Radio_diversityImbalance 15-463
Radio_fPGAFailure 15-465
Radio_filterPanelRecordInvalid 15-467
Radio_hardwareModelMismatch 15-469
Radio_hwErrorDetectedByPlatformSw 15-471
Radio_initialisationFailure 15-473
Radio_internalGainFailure 15-475
Radio_localConfigurationFailure 15-477
Radio_lossOfDemodulatorSynthesizerSynchronisation 15-479
Radio_lossOfForwardBusLink 15-482
Radio_lossOfModulatorSynthesizerSynchronisation 15-484
Radio_lossOfPulse 15-487
Radio_lossOfReceiveSynthesizerSynchronisation 15-490
Radio_lossOfTransmitSynthesizerSynchronisation 15-493
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-9
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Overview
procedures
Radio_majorGainFailure 15-496
Radio_majorPlatformSwError 15-499
Radio_majorTxSpectrumFailure 15-500
Radio_messageThrottleOn 15-503
Radio_minorGainFailure 15-505
Radio_missingConfigurationData 15-508
Radio_missingDelayCalibrationData 15-510
Radio_overTemperature 15-512
Radio_portMapInvalid 15-514
Radio_rFOverdrive 15-516
Radio_rFPathMismatch 15-518
Radio_resyncOfPulse 15-520
Radio_rx1PathFaultDetected 15-523
Radio_rx2PathFaultDetected 15-525
Radio_samplingReceiverFailure 15-527
Radio_selfTestFailure 15-529
Radio_synthesizerFailure122Mhz 15-531
Radio_synthesizerFailure15Mhz 15-533
Radio_tDUCommunicationFailure 15-535
Radio_toneGeneratorFailure 15-537
Radio_transmitGainLimitExceeded 15-539
Radio_transmitterSwitchFailure 15-542
Radio_transmitterSwitchOff 15-544
Radio_txActivationMalfunction 15-546
Radio_underTemperature 15-548
RxAmp alarms 15-550
RxAmp_equipmentFault 15-551
RxAmp_initialisationFailure 15-553
STM1OC3Port alarms 15-555
STM1OC3Port_linkFailureAIS_L 15-556
STM1OC3Port_linkFailureAIS_P 15-558
STM1OC3Port_linkFailureLOF 15-560
...................................................................................................................................................................................................................................
15-10 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Overview
procedures
STM1OC3Port_linkFailureLOP_P 15-562
STM1OC3Port_linkFailureLOS 15-564
STM1OC3Port_linkFailurePLM_P 15-566
STM1OC3Port_linkFailureRDI_L 15-568
STM1OC3Port_linkFailureRDI_P 15-570
STM1OC3Port_linkFailureSLU_P 15-572
STM1OC3port_localConfigurationFailure 15-574
STM1OC3Port_pathTraceMismatch 15-576
STM1OC3Port_signalDegraded_L 15-578
STM1OC3Port_signalDegraded_P 15-580
STM1OC3Port_signalFailed_L 15-582
STM1OC3Port_signalFailed_P 15-584
TDU alarms 15-586
TDU_applicationInsane 15-587
TDU_boardGenericMismatch 15-589
TDU_communicationFailure 15-591
TDU_configurationMismatch 15-593
TDU_criticalVoltageFailure 15-595
TDU_filterPanelRecordInvalid 15-597
TDU_frequencySynthesizerFailure 15-599
TDU_heaterFailure 15-601
TDU_hwErrorDetectedByPlatformSw 15-603
TDU_initialisationFailure 15-605
TDU_localConfigurationFailure 15-607
TDU_lossOfPulse 15-609
TDU_majorPlatformSwError 15-612
TDU_messageThrottleOn 15-614
TDU_portMapInvalid 15-616
TDU_selfTestFailure 15-618
TDU_temperatureOutOfRange 15-620
TDU_tssiDetectorFailure 15-622
TxAmp alarms 15-624
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-11
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Overview
procedures
TxAmp_amplifierSwitchFailure 15-625
TxAmp_communicationFailure 15-627
TxAmp_configurationMismatch 15-629
TxAmp_equipmentFault 15-631
TxAmp_externalAmplifierFailure 15-633
TxAmp_hardwareModelMismatch 15-635
TxAmp_incompletePredistortionCoefficients 15-637
TxAmp_initialisationFailure 15-639
TxAmp_localConfigurationFailure 15-641
TxAmp_messageThrottleOn 15-643
TxAmp_missingPredistortionCoefficients 15-645
TxAmp_overTemperature 15-647
TxAmp_rFOverdrive 15-649
TxAmp_selfTestFailure 15-651
TxAmp_severeExternalAmplifierFailure 15-653
TxAmp_underTemperature 15-655
TxAmp_warmupFailure 15-657
UCU alarms 15-659
UCU_applicationInsane 15-660
UCU_clockFailure30_72Mhz 15-662
UCU_combinerToASICBusFailure 15-664
UCU_communicationFailure 15-666
UCU_configurationMismatch 15-668
UCU_criticalChannelElementFailure 15-670
UCU_criticalChannelElementSystemResourceFailure 15-672
UCU_excessiveDownlinkParityErrors 15-674
UCU_excessiveUplinkParityErrors 15-676
UCU_fPGAFailure 15-678
UCU_hwErrorDetectedByPlatformSw 15-681
UCU_initialisationFailure 15-683
UCU_lossOfForwardBusLink 15-685
UCU_majorChannelElementSystemResourceFailure 15-687
...................................................................................................................................................................................................................................
15-12 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Overview
procedures
UCU_majorPlatformSwError 15-689
UCU_selfTestFailure 15-691
UCU_voltageOutOfRange 15-693
UCU_watchdogInitiatedReset 15-695
URC alarms 15-697
URC_aTMOutOfCellDelineation 15-698
URC_applicationInsane 15-700
URC_clockFailure30_72Mhz 15-701
URC_configurationMismatch 15-703
URC_hardwareModelMismatch 15-705
URC_hwErrorDetectedByPlatformSw 15-707
URC_localConfigurationFailure 15-709
URC_lossOfPulse 15-711
URC_majorPlatformSwError 15-713
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-13
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
General information
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides general information on how the Node B handles hardware and
software faults.
Contents
...................................................................................................................................................................................................................................
15-14 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Object relationships
...................................................................................................................................................................................................................................
Managed objects
The Node B is a collection of Managed Objects (MO). When an MO detects an error
condition and sends an alarm to the OMC-UPS which is not only informational, the
system will perform an autonomous recovery action.
Dependencies
Some MOs such as radios, UCUs, TDUs depend on other MOs, e.g. a Radio MO
depends on the CTU MO. So when the CTU MO is disabled because it detects an
error condition, the Radio MO will also be disabled.
If a number of alarms for different MOs are sent to the OMC, the operator should
proceed as follows:
1. Find and analyse the oldest alarm (timestamp)
2. Perform the fault clearance procedure defined for it.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-15
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Purpose
This topic describes alarm recovery actions that are taken when a fault occurs in the
Node B hardware or software.
...................................................................................................................................................................................................................................
15-16 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Node B fault recovery actions
procedures
Alarm occurs
Report alarm
Autonomous Y
recovery action
performed?
Re-
N
Isolate N initialization N
unit? threshold
reached?
Re-initialize unit
Y Y
Isolate unit
Operator performs
fault clearance procedure
N Fault
cleared?
Is
alarm of N Operator
ADAC clears alarm
Nature?
Automatically
clear alarm
End
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-17
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Node B fault recovery actions
procedures
The FM logs alarms locally in the historical alarm logfile which is stored in the RAM.
These alarms can be viewed via ftp (one file per day and one summary file
“NODEB.ALARM”). The Node B RMT provides access to the historical alarm logfiles
via the “FTP Agent” screen. When the Node B is reset, the historical alarm logfile is
empty.
Automatically reinitialize
The unit is reset and reinitialized automatically by the NodeB as local fault defense.
Note: If the fault occurs again, this local fault defense is repeated, if the reinitialization
threshold hasn’t been reached (6 reinitializations within 1 hour). If the threshold has
been reached, the unit is isolated
Isolate unit
If the unit has a severe fault or the reinitialization threshold has reached, the unit is
isolated, which means that it is reset, but not reinitialized. The operator must trigger a
reset action of the unit, so that the unit leaves the isolate state.
Clearing alarms
If... then...
the fault has been cleared but the MO an additional alarm is raised, the MO is
fails to successfully reset and initialize, isolated (MO dependent) and the initial
alarm will still be pending.
....................................................................................................................................................................................................................................
15-18 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Node B fault recovery actions
procedures
If... then...
the fault has been cleared and the MO an alarm clear message is forwarded to
ssuccessfully resets and initializes, the OMC to remove the alarm from the
active alarm list.1
Notes:
1. If after a short time frame (depends on the MO), the fault is triggered again in the Node
B, the MO will be reset (an alarm will be triggered for during the reset period). If the
fault occurs more than six times within the next hour, the MO will become isolated and
the triggered alarm will remain active.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-19
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Overview
This topic describes the autonomous actions that are taken by the Node B whenever
the Node B is internally reset.
Autonomous recovery
When a severe fault occurs, the Node B is autonomously reset.
When a URC is reset, the loss of communication with the Node B will be indicated by
an RNC alarm at the OMC.
Failing URC
The following actions are taken after a severe fault has been detected in the URC:
Notes:
1. If the URC software restarted successfully.
...................................................................................................................................................................................................................................
15-20 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-21
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
ALDController alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the ALD Controller alarms.
Contents
ALDController_communicationFailure 15-23
ALDController_hardwareFailure 15-25
ALDController_softwareDownloadFailure 15-27
ALDController_softwareFailure 15-29
ALDController_softwareVersionMismatch 15-31
ALDController_temperatureOutOfRange 15-33
ALDController_unknownDeviceDetected 15-35
...................................................................................................................................................................................................................................
15-22 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
ALDController_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ALDController_communication-
Failure alarm.
Description
The communication to the ALD Controller cannot be established or has been lost.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Possible root causes:
• Cabling problem
• Equipment failure
• Equipment not installed
System impact
ALD system not operational. NodeB cyclicly tries to reconnect.No impact on call
processing.
1 At the OMC-UPS, wait several minutes for automatic clearance of the alarm.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-23
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance ALDController_communicationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-24 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
ALDController_hardwareFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ALDController_hardwareFailure
alarm.
Description
A hardware failure has occured on the ALD Controller.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The ALD Controller is reset and reinitialized autonomously. During that time the ALD
system is not operational. No impact on call processing.
2 At the OMC-UPS, reset the ALDController object, which leads to a hard reset of the
ALD Controller.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-25
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance ALDController_hardwareFailure
procedures
If the alarm is cleared and not reported again, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-26 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
ALDController_softwareDownloadFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ALDController_softwareDown-
loadFailure alarm.
Description
Software download to the ALD Controller has failed.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Possible root causes:
• Communication problem
• Equipment failure
• Corrupted file
System impact
ALD system not operational. No impact on call processing.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-27
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance ALDController_softwareDownloadFailure
procedures
2 At the OMC-UPS, reset the ALDController object to start the download again.
If the download has been completed successfully, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-28 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
ALDController_softwareFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ALDController_softwareFailure
alarm.
Description
A software failure has occured on the ALD Controller.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Software error.
System impact
The ALD Controller is reset and re-initialized autonomously. During that time the ALD
system is not operational. No impact on call processing.
2 At the OMC-UPS, reset the ALDController object, which leads to a hard reset of the
ALD Controller.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-29
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance ALDController_softwareFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-30 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
ALDController_softwareVersionMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ALDController_softwareVersion-
Mismatch alarm.
Description
The software version on the ALD Controller does not match the current NodeB
software version.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
Software version mismatch during initial NodeB startup or NodeB upgrade or
downgrade.
System impact
ALD system not operational.No impact on call processing.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-31
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance ALDController_softwareVersionMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-32 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
ALDController_temperatureOutOfRange
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ALDController_temperature-
OutOfRange alarm.
Description
The temperature of the ALD Controller has exceeded the specified upper or lower
limit.
Default severity
Major
Alarm type
environmentalAlarm
Root cause
low or high temperature.
System impact
The ALD Controller remains operational, but may fail at any time as it is operating
outside the guaranteed environmental conditions. If the ALD Controller is reset, it will
not come up until the temperature is again within acceptable limits.
1 At the OMC-UPS, check for Frame alarms related to heat management system or fan
problems, and perform the fault clearance procedure for the alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-33
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance ALDController_temperatureOutOfRange
procedures
...................................................................................................................................................................................................
2 At the NodeB, check environment of the ALD Controller for unacceptable temperature
and repair fan / heat management system as appropriate.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-34 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
ALDController_unknownDeviceDetected
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ALDController_unknownDeviceDe-
tected alarm.
Description
Unknown antenna line device detected.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
One or more antenna line devices are not configured in the backplane of the NodeB.
System impact
Unknown antenna line device is not used.
1 At the OMC-UPS or NodeB, check configuration of the ALD system in the backplane
of the NodeB via (remote) RMT
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-35
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance ALDController_unknownDeviceDetected
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-36 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
AlarmHub alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Alarm Hub alarms.
Contents
AlarmHub_communicationFailure 15-38
AlarmHub_externalAlarmPort0 15-40
AlarmHub_externalAlarmPort1 15-42
AlarmHub_externalAlarmPort2 15-44
AlarmHub_externalAlarmPort3 15-46
AlarmHub_externalAlarmPort4 15-48
AlarmHub_externalAlarmPort5 15-50
AlarmHub_externalAlarmPort6 15-52
AlarmHub_externalAlarmPort7 15-54
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-37
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
AlarmHub_communicationFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not supported in this release.
This topic provides the procedure for clearing the AlarmHub_communicationFailure
alarm.
Description
Heartbeat synchronisation between the Alarm Hub and the URC has been lost.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA
System impact
TBA
1 TBA
...................................................................................................................................................................................................................................
15-38 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance AlarmHub_communicationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-39
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
AlarmHub_externalAlarmPort0
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not supported in this release.
This topic provides the procedure for clearing the AlarmHub_externalAlarmPort0
alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA
System impact
TBA
1 TBA
...................................................................................................................................................................................................................................
15-40 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance AlarmHub_externalAlarmPort0
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-41
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
AlarmHub_externalAlarmPort1
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not supported in this release.
This topic provides the procedure for clearing the AlarmHub_externalAlarmPort1
alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA
System impact
TBA
1 TBA
...................................................................................................................................................................................................................................
15-42 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance AlarmHub_externalAlarmPort1
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-43
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
AlarmHub_externalAlarmPort2
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not supported in this release.
This topic provides the procedure for clearing the AlarmHub_externalAlarmPort2
alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA
System impact
TBA
1 TBA
...................................................................................................................................................................................................................................
15-44 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance AlarmHub_externalAlarmPort2
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-45
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
AlarmHub_externalAlarmPort3
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not supported in this release.
This topic provides the procedure for clearing the AlarmHub_externalAlarmPort3
alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA
System impact
TBA
1 TBA
...................................................................................................................................................................................................................................
15-46 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance AlarmHub_externalAlarmPort3
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-47
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
AlarmHub_externalAlarmPort4
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not supported in this release.
This topic provides the procedure for clearing the AlarmHub_externalAlarmPort4
alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA
System impact
TBA
1 TBA
...................................................................................................................................................................................................................................
15-48 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance AlarmHub_externalAlarmPort4
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-49
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
AlarmHub_externalAlarmPort5
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not supported in this release.
This topic provides the procedure for clearing the AlarmHub_externalAlarmPort5
alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA
System impact
TBA
1 TBA
...................................................................................................................................................................................................................................
15-50 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance AlarmHub_externalAlarmPort5
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-51
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
AlarmHub_externalAlarmPort6
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not supported in this release.
This topic provides the procedure for clearing the AlarmHub_externalAlarmPort6
alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA
System impact
TBA
1 TBA
...................................................................................................................................................................................................................................
15-52 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance AlarmHub_externalAlarmPort6
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-53
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
AlarmHub_externalAlarmPort7
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not supported in this release.
This topic provides the procedure for clearing the AlarmHub_externalAlarmPort7
alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA
System impact
TBA
1 TBA
...................................................................................................................................................................................................................................
15-54 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance AlarmHub_externalAlarmPort7
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-55
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
AmpShelfFan alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the amplifier shelf fan.
Contents
AmpShelfFan_equipmentFault 15-57
...................................................................................................................................................................................................................................
15-56 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
AmpShelfFan_equipmentFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the AmpShelfFan_equipmentFault alarm.
Description
The fan in the Amplifier Shelf failed.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment malfunction.
System impact
The system will be impacted as indicated below:
• The shelf temperature will rise causing over-temperature alarms on the boards if the
alarm is pending and the operational state of the DigitalShelfFan MO is disabled.
• In case of a intermittent fault condition, the alarm is only cleared if the fault did
not occur again within 3 hours.
• Over temperature alarms result in shutdown of boards and dropped calls on the
Node B.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-57
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance AmpShelfFan_equipmentFault
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-58 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
CPC alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Common Power Converter
(CPC).
Contents
CPC_communicationFailure 15-60
CPC_configurationMismatch 15-62
CPC_dCOutputFailure 15-64
CPC_lowDCInput 15-66
CPC_overTemperature 15-68
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-59
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CPC_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CPC_communicationFailure alarm.
Description
Heartbeat synchronization between the CPC (Common Power Converter) and the URC
(Universal Radio Controller) has been lost.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Possible root causes are:
• Equipment failure
• Timing problem.
System impact
The system will be impacted as indicated below:
• The call capacity of the whole Node B is reduced, if the alarm is pending and the
operational state of the CPC MO is disabled.
• If too many boards fail, the Node B can no longer operate.
• In case of a intermittent fault condition, the alarm is only cleared if the fault did
not occur again within 3 hours.
Note: There are two types of CPCs, an A type and a B type, which deliver different
voltages. At least one instance of each type is needed.
...................................................................................................................................................................................................................................
15-60 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CPC_communicationFailure
procedures
1 At the Node B, check whether the CPC is mounted correctly into the shelf.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-61
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CPC_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CPC_configurationMismatch alarm.
Description
The configuration conflicts with attribute value(s) of other object(s).
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No service available
1 At the Node B, check for nodeBTypeMismatch alarm of the NodeB object and perform
the fault clearance procedure for that alarm.
If this alarm is cleared together with the nodeBTypeMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................................................
15-62 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CPC_configurationMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-63
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CPC_dCOutputFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CPC_dCOutputFailure alarm.
Description
A DC output failure at the CPC (Common Power Converter) has been detected.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment malfunction.
System impact
The system will be impacted as indicated below:
• The call capacity of the whole Node B is reduced, if the alarm is pending and the
operational state of the CPC MO is disabled.
• If too many boards fail, the Node B can no longer operate.
• In case of a intermittent fault condition, the alarm is only cleared if the fault did
not occur again within 3 hours.
Note: There are two types of CPCs, an A type and a B type, which deliver different
voltages. At least one instance of each type is needed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-65
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CPC_lowDCInput
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CPC_lowDCInput alarm.
Description
A low DC input power on the CPC (Common Power Converter) is detected.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Power problem.
System impact
The system will be impacted as indicated below:
• The call capacity of the whole Node B is reduced, if the alarm is pending and the
operational state of the CPC MO is disabled.
• If too many boards fail, the Node B can no longer operate.
• In case of a intermittent fault condition, the alarm is only cleared if the fault did
not occur again within 3 hours.
Note: There are two types of CPCs, an A type and a B type, which deliver different
voltages. At least one instance of each type is needed.
2 At the Node B, ensure that the DC input voltage is not too low.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the Node B, check the outdoor site DC input voltage. Replace any battery that runs
low.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-67
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CPC_overTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CPC_overTemperature alarm.
Description
The CPC (Common Power Converter) reports that the temperature is above the
specified limit.
Default severity
Major
Alarm type
environmentalAlarm
Root cause
The temperature of the CPC is unacceptable.
System impact
The system will be impacted as indicated below:
• The call capacity of the whole Node B is reduced, if the alarm is pending and the
operational state of the CPC MO is disabled.
• If too many boards fail, the Node B can no longer operate.
• In case of a intermittent fault condition, the alarm is only cleared if the fault did
not occur again within 3 hours.
Note: There are two types of CPCs, an A type and a B type, which deliver different
voltages. At least one instance of each type is needed.
...................................................................................................................................................................................................................................
15-68 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CPC_overTemperature
procedures
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-69
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CPRIPort alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the CPRIPort alarms.
Contents
CPRIPort_fibreLOF 15-71
CPRIPort_fibreLOS 15-72
CPRIPort_fibreRAI 15-73
CPRIPort_fibreSAPDefect 15-74
CPRIPort_fibreSigLow 15-75
CPRIPort_transmitterSwitchOff 15-76
...................................................................................................................................................................................................................................
15-70 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
CPRIPort_fibreLOF
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the CPRIPort_fibreLOF alarm.
Description
The fibre interface has encountered a loss of frame.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
TBA
System impact
TBA
1 TBA.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-71
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CPRIPort_fibreLOS
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the CPRIPort_fibreLOS alarm.
Description
The fibre interface has encountered a loss of signal.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
TBA
System impact
TBA
...................................................................................................................................................................................................................................
15-72 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
CPRIPort_fibreRAI
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the CPRIPort_fibreRAI alarm.
Description
The fibre interface has encountered a remote alarm indication.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
TBA
System impact
TBA
1 TBA.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-73
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CPRIPort_fibreSAPDefect
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the CPRIPort_fibreSAPDefect alarm.
Description
The fibre interface has encountered a service access point (SAP) defect.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
TBA
System impact
TBA
1 TBA.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
15-74 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
CPRIPort_fibreSigLow
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the CPRIPort_fibreSigLow alarm.
Description
The fibre interface has encountered a low optical signal.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
TBA
System impact
TBA
1 TBA.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-75
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CPRIPort_transmitterSwitchOff
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the CPRIPort_transmitterSwitchOff
alarm.
Description
The HW switch on the OCM faceplate is set to off. This turns off the transmit data
stream (ie downstream) of the user plane of the connected RF Heads.
Default severity
Warning
Alarm type
equipmentAlarm
Root cause
Equipment failure
System impact
TBA
1 TBA.
...................................................................................................................................................................................................................................
15-76 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CPRIPort_transmitterSwitchOff
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-77
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Common Timing Unit
(CTU).
Contents
CTU_boardGenericMismatch 15-80
CTU_clockFailure15Mhz 15-82
CTU_clockFailure30_72Mhz 15-84
CTU_communicationFailure 15-86
CTU_configurationMismatch 15-88
CTU_flywheelStart 15-90
CTU_flywheelTimeLimitReached 15-92
CTU_frequencyOutOfRange 15-94
CTU_gPSAntennaFailure 15-96
CTU_gPSReceiverFailure 15-98
CTU_hardwareModelMismatch 15-100
CTU_inactive 15-102
CTU_initialisationFailure 15-104
CTU_lossOfClockSourceSynchronisation 15-106
CTU_maintenanceRequested 15-108
CTU_messageThrottleOn 15-110
CTU_noOMConfiguredInDatabase 15-112
CTU_phaseLockLoopFailure 15-114
CTU_selfTestFailure 15-116
CTU_syncSourceMismatch 15-118
CTU_temperatureOutOfRange 15-120
CTU_timeOfDayDataInvalid 15-122
CTU_underTemperature 15-124
...................................................................................................................................................................................................................................
15-78 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Overview
procedures
CTU_waitingForClockSignal 15-126
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-79
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_boardGenericMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_boardGenericMismatch alarm.
Description
The software version on the Common Timing Unit (CTU) does not match with the
current version stored on the URC because a software download failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
The software on the CTU could not be updated because the download from the URC
to the CTU failed.
System impact
The CTU can not be initiated to service. No calls on this Node B are possible.
2 At the OMC-UPS, reset the CTU object to update the software on the CTU.
If the alarm is cleared, the procedure is completed
...................................................................................................................................................................................................................................
15-80 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_boardGenericMismatch
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, check the state of the current NodeB software version via RMT. If
the state is not GOOD, reset the NodeB object.
If the alarm is cleared, the procedure is completed.
Result: The NodeB automatically downloads missing/corrupted software files from
the FTP server (OMC) and updates the software on the CTU.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-81
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_clockFailure15Mhz
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_clockFailure15Mhz alarm.
Description
The Common Timing Unit (CTU) detected loss of the 15.0 Mhz clock. This may be
due to failure of OM onboard the CTU.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
Call processing on the Node B is interrupted
2 At the Node B, make sure that the CTU is mounted correctly in the frame.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and initialize the CTU.
...................................................................................................................................................................................................................................
15-82 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_clockFailure15Mhz
procedures
4 At the Node B, check the cabling between the CTU and I/O panel.
...................................................................................................................................................................................................
5 At the OMC-UPS, reset the CTU object to reset and initialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-83
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_clockFailure30_72Mhz
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_clockFailure30_72Mhz alarm.
Description
The Common Timing Unit (CTU) failed to detect the 30.72 MHz clock signal.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
Call processing on the Node B is interrupted. If a spare CTU is available, a
switch-over will occur.
2 At the Node B, check the cabling between the Oscillator Module and the faceplate and
between the CTU and the faceplate.
...................................................................................................................................................................................................................................
15-84 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_clockFailure30_72Mhz
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and initialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-85
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_communicationFailure alarm.
Description
Heartbeat synchronization between the Common Timing Unit (CTU) and the Universal
Radio Controller (URC) has been lost or timeout occured during initialisation of the
CTU.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Possible root causes are:
• Equipment failure
• Timing problem.
• Missing or pulled board.
System impact
Call processing on the Node B is interrupted. If a spare CTU is available, a
switch-over will occur.
1 At the OMC-UPS, wait until the CTU reinitialization is completed. If the alarm is not
cleared within 5 minutes, the initialisation has failed.
...................................................................................................................................................................................................................................
15-86 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_communicationFailure
procedures
3 At the Node B, make sure that the CTU is mounted properly in the shelf.
...................................................................................................................................................................................................
4 At the OMC-UPS, reset the CTU object to reset and reinitialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-87
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_configurationMismatch alarm.
Description
The configuration conflicts with attribute value(s) of other object(s).
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No service available
1 At the Node B, check for nodeBTypeMismatch alarm of the NodeB object and perform
the fault clearance procedure for that alarm.
If this alarm is cleared together with the nodeBTypeMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................................................
15-88 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_configurationMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-89
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_flywheelStart
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_flywheelStart alarm.
Description
Flywheeling start.
Default severity
Warning
Alarm type
equipmentAlarm
Root cause
The discipline source (network or GPS) has been lost in case of an crystal oscillator
(OM-Q).
System impact
The clock of the Node B will become unstable.
The CTU is allowed to flywheel for 72 hours. During this time period, there is no
impact on call processing. After 72 hours call processing will be disabled.
...................................................................................................................................................................................................................................
15-90 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_flywheelStart
procedures
1 Important! Avoid any maintenance activity which is not related to the flywheeling
and which would cause a reset and initialization of the CTU or the complete Node
B.
If... Then...
The discipline source = gps Go to step 2.
The discipline source = network Go to step 4.
...................................................................................................................................................................................................
2 At the Node B, make sure that the GPS antenna, the GPS antenna cable, receiver and
the clock splitter are working properly.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the OMC-UPS, check for E1T1Port alarms and perform the fault clearance
procedure related to these alarms.
...................................................................................................................................................................................................
5 At the OMC-UPS, reset the CTU object to reset and reinitialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-91
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_flywheelTimeLimitReached
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_flywheelTimeLimitReached
alarm.
Description
Flywheeling time limit reached.
Default severity
Critical
Alarm type
qualityofServiceAlarm
Root cause
The discipline source (network or GPS) is not available during initialisation of the
CTU with a crystal oscillator (OM-Q), or the CTU flywheeled for more than 72 hours.
System impact
RF part is shut down. No call processing is possible and all calls are dropped.
1 If... Then...
The discipline source = gps Go to step 2.
The discipline source = network Go to step 5.
...................................................................................................................................................................................................................................
15-92 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_flywheelTimeLimitReached
procedures
...................................................................................................................................................................................................
2 At the Node B, make sure that the GPS antenna, the GPS antenna cable, receiver and
the clock splitter are working properly.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and reinitialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
5 At the OMC-UPS, check for E1T1Port alarms and perform fault clearance procedure
related to these alarms.
...................................................................................................................................................................................................
6 At the OMC-UPS, reset the CTU object to reset and reinitialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
8 At the OMC-UPS, reset the CTU object to reset and reinitialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-93
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_frequencyOutOfRange
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_frequencyOutOfRange alarm.
Description
The frequency generated by the Oscillator Module (OM) onboard the CTU is out of
range
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment failure or network clock failure
System impact
Call processing may be impacted:
• Cells not available to the UE (sleeping cell)
• Handover not possible to cells of the affected NodeB
• Radio frequency being out of the assigned band
1 At the OMC-UPS, determine if the alarm occurs for single or multiple Node Bs.
...................................................................................................................................................................................................
2 In the case of multiple Node Bs being affected, check and repair the network clock
...................................................................................................................................................................................................................................
15-94 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_frequencyOutOfRange
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-95
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_gPSAntennaFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_gPSAntennaFailure alarm.
Description
The Global Positioning System (GPS) receiver detected that the GPS antenna or the
antenna cable is broken.
Important! This alarm only applies if the syncSource attribute of the NodeB object
is set to ″internalGPS″
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Antenna problem.
System impact
Call processing on the Node B is interrupted.
If a spare CTU is available, a switch-over will occur.
1 At the Node B, make sure that the GPS antenna and the GPS antenna cable are
working properly.
...................................................................................................................................................................................................................................
15-96 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_gPSAntennaFailure
procedures
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-97
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_gPSReceiverFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_gPSReceiverFailure alarm.
Description
The Common Timing Unit (CTU) detected a Global Positioning System (GPS) receiver
failure.
Important! This alarm only applies if the syncSource attribute of the NodeB object
is set to ″internalGPS″
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
Call processing on the Node B is interrupted.
If a spare CTU is available, a switch-over will occur.
1 At the Node B, make sure that the GPS antenna, the GPS antenna cable, receiver, and
the clock splitter are working properly.
...................................................................................................................................................................................................................................
15-98 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_gPSReceiverFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-99
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_hardwareModelMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_hardwareModelMismatch
alarm.
Description
The detected hardware model does not match the value specified
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No impact on service.
...................................................................................................................................................................................................................................
15-100 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_hardwareModelMismatch
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, update the expected hardware model attribute to match the detected
hardware model attribute
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-101
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_inactive
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_inactive alarm.
Description
The OM onboard the CTU is not operational.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
Call processing on the Node B is interrupted
2 At the Node B, make sure that the CTU is mounted correctly in the frame.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and initialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-102 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_inactive
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-103
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_initialisationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_initialisationFailure alarm.
Description
The Common Timing Unit (CTU) failed to initialize, due to a failure during Board
Level Self Test (BLST), reset or enable.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The CTU cannot be initialized to service. If no spare CTU is available, then the Node
B cannot be brought to service. If a spare is available, then the spare CTU is activated.
1 At the Node B, make sure that the CTU is mounted correctly in the frame.
...................................................................................................................................................................................................
2 At the OMC-UPS, reset the CTU object to reset and reinitialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-104 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_initialisationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-105
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_lossOfClockSourceSynchronisation
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_lossOfClockSourceSynchro-
nisation alarm.
Description
The Common Timing Unit (CTU) cannot detect the 8 kHz E1 synchronization signal
from the E1 link.
Note: This alarm only applies when the syncSource attribute of the NodeB object is
set to network.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
Calls might drop if the clock signal remains unstable.
1 At the OMC-UPS, check for E1T1Port alarms and perform fault clearance procedure
related to these alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-106 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_lossOfClockSourceSynchronisation
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-107
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_maintenanceRequested
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_maintenanceRequested alarm.
Description
The OM onboard the CTU is indicating that it can no longer compensate for frequency
shifts.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
OM frequency can no longer be adjusted.
1 At the OMC-UPS, reset the CTU object to reset the CTU board.
Use the reset type type0 to trigger a software reset.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the OMC-UPS, reset the CTU object to reset the CTU board.
Use the reset type type1 to trigger a power cycle.
...................................................................................................................................................................................................................................
15-108 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_maintenanceRequested
procedures
3 At the Node B, make sure that the CTU is mounted correctly in the frame.
...................................................................................................................................................................................................
4 At the OMC-UPS, reset the CTU object to reset and initialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-109
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_messageThrottleOn
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_messageThrottleOn alarm.
Description
Message throttling has been activated because too many errors are being sent by the
Common Timing Unit (CTU).
Default severity
Critical
Alarm type
qualityofServiceAlarm
Root cause
System resources are at or are near maximum capacity. Too many errors have occurred
in a given time frame.
System impact
Call processing on the Node B is interrupted. If there is a spare CTU, a switch-over
will occur.
2 At the OMC-UPS, check for other CTU and OM alarms and perform fault clearance
procedures for the alarms.
...................................................................................................................................................................................................................................
15-110 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_messageThrottleOn
procedures
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-111
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_noOMConfiguredInDatabase
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_noOMConfiguredInDatabase
alarm.
Description
OM hardware is present, but it is not configured in the database. The CTU can not
initialize.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Probable causes are:
• Configuration error.
System impact
The CTU can not initialize, call processing is blocked on the entire Node B.
...................................................................................................................................................................................................................................
15-112 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_noOMConfiguredInDatabase
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-113
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_phaseLockLoopFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_phaseLockLoopFailure alarm.
Description
The phase lock on the OM onboard the CTU has failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
Call processing on the Node B is interrupted
2 At the Node B, make sure that the CTU is mounted correctly in the frame.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and initialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-114 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_phaseLockLoopFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-115
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_selfTestFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_selfTestFailure alarm.
Description
The Common Timing Unit (CTU) failed the Board Level Self Test (BLST).
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
CTU cannot be initialized to service. If no spare CTU is available, the Node B cannot
be brought to service. If a spare CTU is available the spare CTU is activated.
1 At the Node B, make sure that the CTU is mounted correctly in the frame.
...................................................................................................................................................................................................
2 At the OMC-UPS, reset the CTU object to reset and reinitialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-117
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_syncSourceMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_syncSourceMismatch alarm.
Description
The available OM (separate board or integrated in CTU) does not fit to the configured
syncSource of the Node B.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
The OM hardware does not fit to the configured syncSource. The CTU can not be
configured.
System impact
Call processing is blocked on the whole Node B.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-119
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_temperatureOutOfRange
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_temperatureOutOfRange alarm.
Description
The temperature of the OM onboard the CTU has exceeded the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Probable causes are:
• Defective heater on OM.
• Environmental temperature too high
System impact
Call processing on the Node B is interrupted
1 At the OMC-UPS check for Frame and DigitalShelfFan alarms and perform the fault
clearance procedure for these alarms.
If the temperatureOutOfRange alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-120 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_temperatureOutOfRange
procedures
...................................................................................................................................................................................................
2 At the Node B, make sure that the system is operating within its operational
temperature.
If the temperatureOutOfRange alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and re-initialize the CTU, if the
temperatureOutOfRange alarm has been reported several times and so the CTU has
been isolated.
If the alarm is cleared and not reported again, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-121
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_timeOfDayDataInvalid
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_timeOfDayDataInvalid alarm.
Description
The time of day data cannot be determined.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Timing problem.
System impact
Call processing on the Node B is interrupted. If there is a spare CTU, a switch-over
will occur.
1 At the Node B, make sure that the GPS antenna, the GPS antenna cable, receiver and
the clock splitter are working properly.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
15-122 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_timeOfDayDataInvalid
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-123
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_underTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_underTemperature alarm.
Description
The temperature of the OM onboard the CTU is below the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Probable causes are:
• Defective heater on OM.
• Environmental temperature too low.
System impact
Call processing on the Node B is interrupted
1 At the OMC-UPS check for Frame alarms and perform the fault clearance procedure
for these alarms.
If the underTemperature alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-124 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_underTemperature
procedures
...................................................................................................................................................................................................
2 At the Node B, make sure that the system is operating within itsoperational
temperature.
If the underTemperature alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and re-initialize the CTU, if the
underTemperature alarm has been reported several times and so the CTU has been
isolated.
If the alarm is cleared and not reported again, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-125
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
CTU_waitingForClockSignal
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CTU_waitingForClockSignal alarm.
Description
The Common Timing Unit (CTU) is waiting for the clock signal to become stable.
Default severity
Warning
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
If the clock signal remains unstable calls might drop. The CTU and OM are reset and
reinitialize autonomously.
Note: In the startup phase this alarm is informational only, it should disappear after 15
minutes.
...................................................................................................................................................................................................................................
15-126 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance CTU_waitingForClockSignal
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, check the synchronization sources. At the OMC-U, reset the CTU
object to reset and reinitialize the CTU.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-127
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Cell alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the Cell fault clearance procedures.
Contents
Cell_blockRequestTimerExpiry 15-129
Cell_configurationMismatch 15-131
Cell_powerTestThresholdExceeded 15-133
Cell_rETNotSupported 15-136
Cell_receiveAntennaTestThresholdExceededOnAllAntennas 15-138
Cell_receiveAntennaTestThresholdExceededOnAntenna1 15-140
Cell_receiveAntennaTestThresholdExceededOnAntenna2 15-142
Cell_temporarySoftwareFailure 15-144
...................................................................................................................................................................................................................................
15-128 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Cell_blockRequestTimerExpiry
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Cell_blockRequestTimerExpiry
alarm.
Description
A block resource request message has been sent to the RNC. The RNC has failed to
respond even after the request was repeated.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Software failure.
System impact
There may be a mismatch between the state of the Cell at the NodeB and RNC.
1 At the OMC-UPS, check for any alarm of the related LCell and IuB objects of the
RNC and perform the fault clearance procedures for these alarms.
...................................................................................................................................................................................................
2 At the OMC-UPS, repeat the lock command, either for NodeB, URC or Radio object.
If the lock is successful, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-129
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Cell_blockRequestTimerExpiry
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the Radio object related to the Cell object.
...................................................................................................................................................................................................
4 At the OMC-UPS, repeat the lock command, either for NodeB, URC or Radio object.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-130 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Cell_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Cell_configurationMismatch alarm.
Description
A consistency error between the MO data and its related port maps, Unit Type
Descriptor and/or hardware.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning, frequency band not supported by any Radio or RF-Head or
equipment failure.
System impact
No Service available in this cell.
2 At the OMC-UPS, check the administrative state of the MO CTU. Unlock the MO
CTU, if required.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-131
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Cell_configurationMismatch
procedures
3 At the OMC-UPS, check for CTU & OM alarms and perform the fault clearance
procedure of these alarms.
If the configurationMismatch alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the OMC-UPS, check for Radio and/or RFHead alarms and perform the fault
clearance procedure of these alarms.
If the configurationMismatch alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
5 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-132 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Cell_powerTestThresholdExceeded
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Cell_powerTestThresholdExceeded
alarm.
Description
A powerTest was executed and the carrier power test threshold has been exceeded.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Transmit failure.
System impact
Call capacity is degraded.
1 At the OMC-UPS, check for TX path alarms (Radio and TxAmp objects) alarms and
perform fault clearance procedures for the alarms. Probably Radio_transmitGainLimit-
Exceeded is pending.
Then request another Power Test.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-133
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Cell_powerTestThresholdExceeded
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, check for TDU alarms and perform fault clearance procedures for
the alarms. Especially when powerTest alarms are reported form multiple cells, the
TDU could have a failure.
Then request another Power Test.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the Node B, make sure that the TX path (Filter, RF cabling and TX antenna) is
working properly.
Then request another Power Test.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the Node B:
• Lock the TxAmp object
• Replace the amplifier module
• Reset the TxAmp object
• Unlock the TxAmp object
Then request another Power Test.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
5 At the Node B:
• Lock the Radio object
• Replace the Radio
• Reset the Radio object
• Unlock the Radio object
Then request another Power Test.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
6 At the Node B:
• Lock the TDU object
• Replace the TDU
• Reset the TDU object
• Unlock the TDU object
....................................................................................................................................................................................................................................
15-134 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Cell_powerTestThresholdExceeded
procedures
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-135
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Cell_rETNotSupported
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Cell_rETNotSupported alarm.
Description
RET not supported, since at least one antenna, but not all antennas supporting this cell
have a RET actuator assigned.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
misconfiguration in backplane of NodeB.
System impact
ALD system not operational for the cell. No impact on call processing.
...................................................................................................................................................................................................................................
15-136 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Cell_rETNotSupported
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-137
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Cell_receiveAntennaTestThresholdExceededOnAllAntennas
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Cell_receiveAntennaTestThresh-
oldExceededOnAllAntennas alarm.
Description
This alarm is generated when an Rx Antenna Test is executed and the threshold is
exceeded on all antennas. A failure indicates that the antenna is not functioning.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Receive failure.
System impact
Disfunction of all antennas to be expected.
Degradation of call capacity to be expected.
1 At the OMC-UPS, check for TDU alarms and perform fault clearance procedures for
the alarms. Then request another RX Antenna Test.
...................................................................................................................................................................................................
2 At the OMC-UPS, check for Radio, TxAmp and Filter alarms and perform fault
clearance procedures for the alarms. Then request another RX Antenna Test.
...................................................................................................................................................................................................................................
15-138 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures Cell_receiveAntennaTestThresholdExceededOnAllAntennas
3 At the NodeB, make sure, that the RX path (Filter, RF cabling and RX antenna) is
working properly
If required replace the RX Antenna. Then request another RX Antenna Test
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the NodeB, replace the Filter panel. Then request another RX Antenna Test.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-139
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Cell_receiveAntennaTestThresholdExceededOnAntenna1
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Cell_receiveAntennaTestThresh-
oldExceededOnAntenna1 alarm.
Description
This alarm is generated when a RX Antenna Test is executed and the threshold is
exceeded on antenna 1.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
Receive failure.
System impact
Disfunction of antenna 1 to be expected.
Minor degradation of call capacity to be expected.l
1 At the OMC-UPS, check for RxAmp and Filter alarms and perform fault clearance
procedures for the alarms.
Then request another RX Antenna Test.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-140 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Cell_receiveAntennaTestThresholdExceededOnAntenna1
procedures
...................................................................................................................................................................................................
2 At the Node B, make sure that the RX path (Filter, RF cabling and RX antenna) is
working properly.
Replace RX antenna 1 if required.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-141
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Cell_receiveAntennaTestThresholdExceededOnAntenna2
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Cell_receiveAntennaTestThresh-
oldExceededOnAntenna2 alarm.
Description
This alarm is generated when a RX Antenna Test is executed and the threshold is
exceeded on antenna 2.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
Receive failure.
System impact
Disfunction of antenna 2 to be expected.
Minor degradation of call capacity to be expected.
1 At the OMC-UPS, check for RxAmp and Filter alarms and perform fault clearance
procedures for the alarms.
Then request another RX Antenna Test.
If the alarm is cleared, the procedure is completed
...................................................................................................................................................................................................................................
15-142 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Cell_receiveAntennaTestThresholdExceededOnAntenna2
procedures
...................................................................................................................................................................................................
2 At the Node B, make sure that the RX path (Filter, RF cabling and RX antenna) is
working properly.
Replace RX antenna 2 if required.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-143
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Cell_temporarySoftwareFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Cell_temporarySoftwareFailure
alarm.
Description
A temporary software failure occured leading to disabled/failed common or shared
channels.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
Software failure.
System impact
The service of the cell is impacted dependant on the failed channel. The availability of
the channels is reported via NBAP.
...................................................................................................................................................................................................................................
15-144 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Cell_temporarySoftwareFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-145
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
DigitalShelfFan alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the digital shelf fan.
Contents
DigitalShelfFan_equipmentFault 15-147
...................................................................................................................................................................................................................................
15-146 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
DigitalShelfFan_equipmentFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the DigitalShelfFan_equipmentFault
alarm.
Description
The fan in the Digital Shelf failed.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Fan failure.
System impact
The system will be impacted as indicated below:
• The shelf temperature will rise causing over-temperature alarms on the boards if the
alarm is pending and the operational state of the DigitalShelfFan MO is disabled.
• In case of a intermittent fault condition, the alarm is only cleared if the fault did
not occur again within 3 hours.
• Over temperature alarms result in shutdown of boards and dropped calls on the
Node B.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-147
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance DigitalShelfFan_equipmentFault
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-148 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the E1T1 port.
Contents
E1T1Port_aISDetected 15-150
E1T1Port_atmSyncLost 15-152
E1T1Port_bitErrorRateGreaterThan1PerMillion 15-154
E1T1Port_bitErrorRateGreaterThan1PerThousand 15-156
E1T1Port_configurationMismatch 15-158
E1T1Port_frameLost 15-160
E1T1Port_frameMissed 15-162
E1T1Port_frameSlip 15-164
E1T1Port_iMALinkAlarm 15-166
E1T1port_localConfigurationFailure 15-168
E1T1Port_remoteAlarmIndication 15-170
E1T1Port_signalLost 15-172
E1T1Port_unexpectedIMAGroup 15-174
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-149
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_aISDetected
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1Port_aISDetected alarm.
Description
At the reported DS1 port, the Node B detected an AIS signal. This alarm indicates a
problem in the equipment at the remote end of the E1/T1 connection.
For a T1 configured port, this alarm is also known as BLUE ALARM.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Loss of frame due to internal equipment fault at the remote end of the E1/T1 line. This
is most probably the ATM router interface card or an internal ATM router problem.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-150 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1Port_aISDetected
procedures
1 Check the equipment for the reason to send an AIS signal towards the Node B and
take the appropriate action.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-151
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_atmSyncLost
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1Port_atmSyncLost alarm.
Description
At the reported DS1, loss of the ATM stream synchonisation has been detected.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Loss of signal due to link interuption or equipment malfunction
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
1 Make sure that the E1/T1 line and both sides of the interface cards are working
properly.
...................................................................................................................................................................................................................................
15-152 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1Port_atmSyncLost
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-153
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_bitErrorRateGreaterThan1PerMillion
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
E1T1Port_bitErrorRateGreaterThan1PerMillion alarm.
Description
At the reported DS1 port, the Node B detected a Bit Error Rate which is greater than
10E–6.
For a T1 configured port, the calculation is based on CRC-6 (Extended superframe) or
framing (superframe) errors. For an E1 configured port, the calculation is based on
framing errors.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Communication protocol error.
System impact
The E1/T1 link quality is degraded. Communication to the RNC is affected.
...................................................................................................................................................................................................................................
15-154 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1Port_bitErrorRateGreaterThan1PerMillion
procedures
If... Then...
The fault is cleared after a short Go to step 2.
time and when it does not occur
frequently,
The fault is steadily active or Go to step 3
occurs frequently,
...................................................................................................................................................................................................
2 Check the DS1 port carefully in case of more frequent occurrences of this alarm and
act accordingly.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 Make sure that the E1/T1 line to the router, interface card of the router and the router
are working properly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-155
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_bitErrorRateGreaterThan1PerThousand
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
E1T1Port_bitErrorRateGreaterThan1PerThousand alarm.
Description
At the reported DS1 port, the Node B detected a Bit Error Rate which is greater than
1E-3. For a E1 configured port, the calculation is based on framing errors. For a T1
configured port, the calculation is based on CRC-6 (Extended superframe) or framing
(superframe) errors. The limit of resolution for the T1 BER detection is therefore
2.16E-4.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Communication protocol error.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-156 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1Port_bitErrorRateGreaterThan1PerThousand
procedures
If... Then...
The fault is cleared after a short Go to step 2.
time and when it does not occurs
frequently,
The fault is steadily active or Go to step 3
occurs frequently,
...................................................................................................................................................................................................
2 Check the DS1 port carefully in case of more frequent occurrences of this alarm and
act accordingly.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 Make sure that the E1/T1 line to the router, interface card of the router, and the router
are working properly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-157
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1Port_configurationMismatch
alarm.
Description
The configuration conflicts with attribute value(s) of other object(s).
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No service available
1 At the Node B, check for nodeBTypeMismatch alarm of the NodeB object and perform
the fault clearance procedure for that alarm.
If this alarm is cleared together with the nodeBTypeMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................................................
15-158 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1Port_configurationMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-159
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_frameLost
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1Port_frameLost alarm.
Description
At the reported DS1 port, the Node B detected a loss of frame synchronization of the
E1/T1 signal. For example, the Node B can not detect the framing pattern.
For a T1 configured port, this alarm is known as RED ALARM. For an E1 configured
port, the alarm is raised after three consecutive incorrect frame alignment signals.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Timing problem.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-160 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1Port_frameLost
procedures
1 Make sure that the E1/T1 line and both sides of the interface cards are working
properly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-161
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_frameMissed
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1Port_frameMissed alarm.
Description
At the reported DS1, the NodeB detected missed/repeated frames. This alarm is
reported, when the number of missed/repeated frame incidents reached a certain
threshold.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
framing error.
System impact
The E1/T1 link quality is degraded. Communication to the RNC is affected.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-163
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_frameSlip
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1Port_frameSlip alarm.
Description
At the reported DS1 port, the Node B detected a frame slip. This alarms indicates a
problem with the clock synchronization between the Node B and the transport network.
This alarm is raised if the number of slip incidents reaches a threshold.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Framing error.
System impact
The E1/T1 link quality is degraded. Communication to the RNC is affected.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-165
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_iMALinkAlarm
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1Port_iMALinkAlarm alarm.
Description
This alarm indicates a failure for the IMA E1/T1 Link.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Possible route causes are:
1. Loss of IMA Frame.
2. Link out of delay syncronization
3. Remote failure indication
4. Tx link unusable
5. Rx link unusable
6. Link misconfiguration (link addition failure)
7. Tx link misconnected
8. Rx link misconnected
9. ATM Edge device removed failed link from IMA Group.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-166 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1Port_iMALinkAlarm
procedures
1 At the OMC-UPS, check for other (non-IMA) E1T1Port alarms and perform fault
clearance procedure for these alarms.
If the alarm is cleared, together with the other E1T1Port alarms, the procedure is
completed.
...................................................................................................................................................................................................
2 Initiate enhanced link tests to identify and correct the root cause.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-167
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1port_localConfigurationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1port_localConfigurationFailure
alarm.
Description
The configuration conflicts with local configuration data.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Missing or faulty local configuration data.
System impact
The E1/T1 link is not available.
1 At the OMC-UPS, check for configurationMismatch alarm and perform fault clearance
procedure for that alarm..
If the alarm is cleared together with the configurationMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................................................
15-168 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1port_localConfigurationFailure
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, use the remote RMT tool to check the following configuration data:
• Trunk Group Member parameters.
• ATMPHY parameters
Configure the parameters if required.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-169
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_remoteAlarmIndication
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1Port_remoteAlarmIndication
alarm.
Description
At the reported DS1 port, the Node B detected a remote alarm indication signal. This
alarm indicates a problem at the remote end of the E1/T1 connection.
The alarm indicates a synchronization or bit error rate problem at the ATM router
interface card or an internal ATM router problem.
For a T1 configured port, this alarm is known as YELLOW ALARM.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Synchronization/Bit error rate problem or internal problem at the remote end.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-170 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1Port_remoteAlarmIndication
procedures
1 Check ATM equipment at the remote end of the E1/T1 line and take appropriate action.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 Make sure that the E1/T1 line to the router, interface card of the router, and the router
are working properly.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-171
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_signalLost
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1Port_signalLost alarm.
Description
At the reported DS1 port, the Node B detected no E1/T1 signal. The pulse density is
below the level where the clock signal can be derived.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Loss of signal due to link interuption or equipment malfunction
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
1 Make sure that the E1/T1 line and both sides of the interface cards are working
properly.
...................................................................................................................................................................................................................................
15-172 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1Port_signalLost
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-173
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E1T1Port_unexpectedIMAGroup
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E1T1Port_unexpectedIMAGroup
alarm.
Description
An unexpected IMA group has been auto-detected.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
E1/T1 link auto-detected in IMA group, but referenced by IubInterface object.
System impact
Virtual Channel Links (VCLs) associated with this E1/T1 link are not available for
service.
1 At the OMC-UPS, verify and update the IMA configuration, so that the IMA
configuration of the Node B matches the IMA configuration on the ATM Edge Device.
...................................................................................................................................................................................................................................
15-174 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E1T1Port_unexpectedIMAGroup
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-175
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E3T3Port alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the E3T3Port alarms.
Contents
E3T3Port_linkFailureAIS 15-177
E3T3Port_linkFailureHBER 15-179
E3T3Port_linkFailureLBER 15-181
E3T3Port_linkFailureLOF 15-183
E3T3Port_linkFailureLOS 15-185
E3T3Port_linkFailureOOF 15-187
E3T3Port_linkFailureRDI 15-188
E3T3port_localConfigurationFailure 15-190
...................................................................................................................................................................................................................................
15-176 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
E3T3Port_linkFailureAIS
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E3T3Port_linkFailureAIS alarm.
Description
An Alarm Indication Signal (AIS) failure has been detected..
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Transmission problem upstream of the E3/T3 line.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
1 At the OMC-UPS, Check the remote end of the E3/T3 line for sending the AIS signal
and take the appropriate action.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-177
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance E3T3Port_linkFailureAIS
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-178 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
E3T3Port_linkFailureHBER
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E3T3Port_linkFailureHBER alarm.
Description
The bit error rate (BER) on the E3T3 link has exceeded 10^-3.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Poor link quality on the E3/T3 line.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-179
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance E3T3Port_linkFailureHBER
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-180 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
E3T3Port_linkFailureLBER
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E3T3Port_linkFailureLBER alarm.
Description
The bit error rate (BER) on the E3T3 link has exceeded 10-6.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Poor link quality on the E3/T3 line.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-181
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance E3T3Port_linkFailureLBER
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-182 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
E3T3Port_linkFailureLOF
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E3T3Port_linkFailureLOF alarm.
Description
A Loss of Frame (LOF) failure has been detected.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
The E3/T3 port is not synchronized with the transmission link.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-183
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance E3T3Port_linkFailureLOF
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-184 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
E3T3Port_linkFailureLOS
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E3T3Port_linkFailureLOS alarm.
Description
A loss of signal (LOS) failure has been detected.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Loss of signal due to link interuption or equipment malfunction.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-185
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance E3T3Port_linkFailureLOS
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-186 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
E3T3Port_linkFailureOOF
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E3T3Port_linkFailureOOF alarm.
Description
An Out of Frame (OOF) failure has been detected.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Extensive OOF conditions.
System impact
The E3/T3 link quality may be degraded.
1 Ensure that the E3/T3 line and both sides of the interface cards are working correctly.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-187
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E3T3Port_linkFailureRDI
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E3T3Port_linkFailureRDI alarm.
Description
A Remote Defect Indication (RDI) failure has been detected.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Link problem at the remote end of the line.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-188 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E3T3Port_linkFailureRDI
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-189
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
E3T3port_localConfigurationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the E3T3port_localConfigurationFailure
alarm.
Description
The configuration conflicts with local configuration data.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Missing or faulty local configuration data.
System impact
The STM/OC3 link is not available.
1 At the Node B, use the RMT tool to check the Trunk Group Member parameters
Configure the parameters if required.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-190 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance E3T3port_localConfigurationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-191
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
EthernetPort alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the ethernetPort alarms.
Contents
EthernetPort_portFailure 15-193
...................................................................................................................................................................................................................................
15-192 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
EthernetPort_portFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the EthernetPort_portFailure alarm.
Description
The Ethernet Port has failed and is unavailable for service.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Equipment failure.
System impact
Ethernet cut through failed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-193
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
ExtRxAmp alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Tower Top Low Noise
Amplifier (TTLNA).
Contents
ExtRxAmp_configurationMismatch 15-195
ExtRxAmp_equipmentFault 15-197
ExtRxAmp_localConfigurationFailure 15-199
...................................................................................................................................................................................................................................
15-194 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
ExtRxAmp_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtRxAmp_configurationMismatch
alarm.
Description
The configuration conflicts with attribute value(s) of other object(s).
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No service available
1 At the Node B, check for nodeBTypeMismatch alarm of the NodeB object and perform
the fault clearance procedure for that alarm.
If this alarm is cleared together with the nodeBTypeMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-195
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance ExtRxAmp_configurationMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-196 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
ExtRxAmp_equipmentFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtRxAmp_equipmentFault alarm.
Description
One TTLNA associated with a filter panel failed. It will automatically be bypassed. As
a result the radio functionality will be impaired, but still be present.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Possible root causes are:
• Filter panel failure
• Current limits are not defined in EEPROM of filter panel
• Power consumption of the TTLNA is out of the defined current limits.
System impact
Call capacity on this cell will decrease and calls on the border of the cell may be
dropped.
1 At the OMC-UPS, check for filter alarms and perform the fault clearance procedures
for those alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-197
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance ExtRxAmp_equipmentFault
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, lock and unlock the ExtRxAmp to reactivate the TTLNA.
...................................................................................................................................................................................................
3 At the NodeB, check whether the TTLNA descriptor of the associated filter panel is
OK and configure the TTLNA descriptor if required.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the NodeB, check the TTLNA LED of the associated filter panel:
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-198 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
ExtRxAmp_localConfigurationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtRxAmp_localConfiguration-
Failure alarm.
Description
The configuration conflicts with local configuration data.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Missing or faulty local configuration data.
System impact
No service available
1 At the Node B, check for configurationMismatch alarm and perform fault clearance
procedure for that alarm..
If the alarm is cleared together with the configurationMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 At the OMC-UPS, check and update local configuration data via remote RMT.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-199
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance ExtRxAmp_localConfigurationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-200 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Filter alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the filter shelf.
Contents
Filter_communicationFailure 15-202
Filter_configurationMismatch 15-204
Filter_dCConverterFailure 15-206
Filter_hardwareModelMismatch 15-208
Filter_localConfigurationFailure 15-210
Filter_unknownHardwareModel 15-212
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-201
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Filter_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Filter_communicationFailure alarm.
Description
The heartbeat synchronization between the Filter unit and the Universal Radio
Controller (URC) has been lost or timeout occured during initialisation of the TxAmp.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Possible root causes are:
• Equipment failure
• Timing problem.
• Missing or pulled board.
System impact
The system will be impacted as indicated below:
• ExtRxAmp supported by the power supply within the filter might report errors
• Affected cells are degraded if the alarm is pending and the operational state of the
Filter MO is disabled.
• If this was the only Filter unit or the last Filter unit which served the cell, the cell
is disabled.
• In case of a intermittent fault condition, the alarm is only cleared if the fault did
not occur again within 3 hours.
...................................................................................................................................................................................................................................
15-202 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Filter_communicationFailure
procedures
1 At the Node B, make sure that the Filter unit is mounted correctly in the shelf.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-203
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Filter_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Filter_configurationMismatch alarm.
Description
The configuration conflicts with attribute value(s) of other object(s).
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No service available
1 At the Node B, check for nodeBTypeMismatch alarm of the NodeB object and perform
the fault clearance procedure for that alarm.
If this alarm is cleared together with the nodeBTypeMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................................................
15-204 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Filter_configurationMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-205
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Filter_dCConverterFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Filter_dCConverterFailure alarm.
Description
The DC converter within the Filter unit has detected a failure.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment malfunction. This can be caused by a hardware problem or disruption of the
power supply to the Filter unit.
System impact
The system will be impacted as indicated below:
• ExtRxAmp supported by the power supply within the Filter unit might report errors
• Affected cells are degraded if the alarm is pending and the operational state of the
Filter MO is disabled.
• If this was the only Filter unit or the last Filter unit which served the cell, the cell
is disabled.
• In case of a intermittent fault condition, the alarm is only cleared if the fault did
not occur again within 3 hours.
...................................................................................................................................................................................................................................
15-206 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Filter_dCConverterFailure
procedures
1 At the Node B, make sure that the Filter unit is powered on.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the Node B, make sure that the circuit breaker switch and cabling to the Filter unit
are OK
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-207
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Filter_hardwareModelMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Filter_hardwareModelMismatch
alarm.
Description
The detected Filter hardware model does not match the value specified.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No impact on service.
...................................................................................................................................................................................................................................
15-208 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Filter_hardwareModelMismatch
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, lock the Radio object associated with the Filter.
...................................................................................................................................................................................................
3 At the OMC-UPS, update the expected hardware model attribute to match the detected
hardware model attribute.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-209
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Filter_localConfigurationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Filter_localConfigurationFailure
alarm.
Description
The configuration conflicts with local configuration data.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Missing or faulty local configuration data.
System impact
No service available
1 At the OMC-UPS, check for configurationMismatch alarm and perform fault clearance
procedure for that alarm..
If the alarm is cleared together with the configurationMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................................................
15-210 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Filter_localConfigurationFailure
procedures
...................................................................................................................................................................................................
2 If the problem persists, contact Alcatel-Lucent customer support to check the local
configuration data of the Filter and provide the additionalText of the alarm.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-211
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Filter_unknownHardwareModel
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Filter_unknownHardwareModel
alarm.
Description
The detected Filter hardware model is not known by the software.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
Invalid or new filter unit not supported by the NodeB
System impact
Correct operation of the corresponding cell cannot be guaranteed.
2 At the OMC-UPS, lock the Radio object associated with the Filter.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
15-212 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Filter_unknownHardwareModel
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-213
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Frame alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Node B frame.
Contents
Frame_cabinetDoorOpen 15-215
Frame_cabinetHeaterFailure 15-217
Frame_fanFault 15-219
Frame_heatManagementSystemCompressorFailure 15-221
Frame_heatManagementSystemControllerFailure 15-223
Frame_overTemperature 15-225
Frame_underTemperature 15-227
...................................................................................................................................................................................................................................
15-214 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Frame_cabinetDoorOpen
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Frame_cabinetDoorOpen alarm.
Description
This alarm is raised, when the cabinet door is opened.
Default severity
Major
Alarm type
physicalViolation
Root cause
If the alarm has not been triggered by service personnel working at the enclosure door,
there are two possible reasons for the alarm:
• The cabinet door has been opened by an unknown person
• The door contacts may be faulty.
System impact
None.
2 At the Node B, make sure that the cabinet shows no marks of vandalism or a faulty
door contact.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-215
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Frame_cabinetDoorOpen
procedures
Repair damaged door contacts and any other damages that are visible.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-216 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Frame_cabinetHeaterFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Frame_cabinetHeaterFailure alarm.
Description
The BTS cabinet heater has failed. This alarm occurs only on Macrocell Compact
Outdoor versions (V1) which have an intelligent heater controller and on Modular Cell
Outdoor.
Default severity
Major
Alarm type
environmentalAlarm
Root cause
The cabinet heater has failed.
System impact
No immediate impact.
The temperature in the frame can drop and cause temperature alarms on the boards in
the frame. Temperature alarms result in shutdown of boards and can cause dropped
calls on the Node B.
In case of a intermittent fault condition, the alarm is only cleared if the fault did not
occur again within 30 minutes.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-218 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Frame_fanFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Frame_fanFault alarm.
Description
A fan in the BTS frame is not functioning properly.This alarm occurs only on Modular
Cell Outdoor.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Heating, ventilation or cooling system problem.
System impact
No immediate impact.
The temperature in the frame can rise and cause over-temperature alarms on the boards
in the frame. Over- temperature alarms result in shutdown of boards and can cause
dropped calls on the Node B.
In case of a intermittent fault condition, the alarm is only cleared if the fault did not
occur again within 30 minutes.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-219
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Frame_fanFault
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-220 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Frame_heatManagementSystemCompressorFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Frame_heatManagementSystemCom-
pressorFailure alarm.
Description
The BTS frame Heat Management System compressor has failed. This alarm occurs
only on Modular Cell Outdoor.
Severity
Critical
Root cause
Heating or ventilation or cooling system problem.
System impact
No immediate impact.
The temperature in the system can exceed thresholds and cause temperature alarms on
the boards in the system. Temperature alarms result in shutdown of boards and can
cause dropped calls on the Node B.
In case of a intermittent fault condition, the alarm is only cleared if the fault did not
occur again within 30 minutes.
1 At the Node B, repair of replace the Frame Heat Management System Compressor.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-221
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Frame_heatManagementSystemCompressorFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-222 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Frame_heatManagementSystemControllerFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Frame_heatManagementSystemCon-
trollerFailure alarm.
Description
The BTS frame Heat Management System controller has failed. This alarm occurs only
on Macrocell Compact Outdoor versions (V1) which have an intelligent heater
controller and on Modular Cell Outdoor.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Heating or ventilation or cooling system problem.
System impact
No immediate impact.
The temperature in the system can exceed thresholds and cause temperature alarms on
the boards in the system. Temperature alarms result in shutdown of boards and can
cause dropped calls on the Node B.
In case of a intermittent fault condition, the alarm is only cleared if the fault did not
occur again within 30 minutes.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-223
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Frame_heatManagementSystemControllerFailure
procedures
1 At the Node B, repair or replace the Frame Heat Management System Controller.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-224 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Frame_overTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Frame_overTemperature alarm.
Description
The BTS frame Heat Management System is indicating that the temperature is above a
preset threshold. This alarm occurs only on Macrocell Compact Outdoor versions (V1)
which have an intelligent heater controller and on Modular Cell Outdoor.
Default severity
Major
Alarm type
environmentalAlarm
Root cause
Unacceptable high temperature.
System impact
No immediate impact.
The over-temperature in the frame can cause over-temperature alarms on the boards in
the frame. Over temperature alarms result in shutdown of boards and can cause
dropped calls on the Node B.
In case of a intermittent fault condition, the alarm is only cleared if the fault did not
occur again within 30 minutes.
1 At the OMC-UPS, make sure that there are no other temperature related alarms.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-225
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Frame_overTemperature
procedures
....................................................................................................................................................................................................................................
15-226 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Frame_underTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Frame_underTemperature alarm.
Description
The BTS frame Heat Management System is indicating that the temperature is below a
preset threshold. This alarm occurs only on Macrocell Compact Outdoor versions (V1)
which have an intelligent heater controller and on Modular Cell Outdoor.
Default severity
Major
Alarm type
environmentalAlarm
Root cause
Unacceptable low temperature.
System impact
No immediate impact.
The under-temperature in the frame can cause temperature alarms on the boards in the
frame. Temperature alarms result in shutdown of boards and can cause dropped calls
on the Node B.
In case of a intermittent fault condition, the alarm is only cleared if the fault did not
occur again within 3 hours.
1 At the OMC-UPS, make sure that there are no other temperature related alarms.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-227
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Frame_underTemperature
procedures
....................................................................................................................................................................................................................................
15-228 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
GRS alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the GRS alarms.
Contents
GRS_configurationMismatch 15-230
GRS_firstPortNumberAlreadyInUse 15-232
GRS_gPSAntennaFailure 15-234
GRS_gPSAntennaPositionUnknown 15-236
GRS_gPSReceiverFailure 15-238
GRS_gPSReceiverUnavailable 15-240
GRS_satelliteHealthyThresholdExceededForAllVisibleSatellites 15-241
GRS_secondPortNumberAlreadyInUse 15-243
GRS_selfSurveyFailed 15-245
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-229
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
GRS_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GRS_configurationMismatch.
Description
No appropriate CTU found or configured.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
This Node B will not provide GRS service.
2 At the OMC-UPS, make sure that the syncSource attribute of the NodeB object is not
equal to ″network″, ″internalGPS″ or ″externalGPS″
...................................................................................................................................................................................................................................
15-230 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance GRS_configurationMismatch
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, check for syncSourceMismatch alarm of the CTU and perform the
fault clearance procedure of that alarm.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the OMC-UPS, check for hardwareModelMismatch alarm of the CTU and perform
the fault clearance procedure of that alarm.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-231
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
GRS_firstPortNumberAlreadyInUse
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GRS_firstPortNumberAlreadyInUse
alarm.
Description
The GRS could not open a TCP/IP port with the specified port number because there is
already another port opened with the same port number.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
The operator selected a port number which was already assigned previously to another
service.
System impact
This NodeB will not provide GRS service.
1 At the OMC-UPS, lock the GRS object, update firstPortNumber attribute to assign
another port number and unlock the GRS object.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-232 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance GRS_firstPortNumberAlreadyInUse
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-233
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
GRS_gPSAntennaFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GRS_gPSAntennaFailure alarm.
Description
The Global Positioning System (GPS) receiver detected that the GPS antenna or the
antenna cable is broken.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
This Node B will not provide GRS service.
1 At the Node B, make sure that the GPS antenna and the GPS antenna cable are intact
and working properly.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
15-234 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance GRS_gPSAntennaFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-235
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
GRS_gPSAntennaPositionUnknown
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GRS_gPSAntennaPositionUnknown
alarm.
Description
The position of the GPS Antenna is not available to the NodeB.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Possible root causes are:
• Position not written into backplane
• Self survey not yet performed
System impact
This NodeB will not provide GRS service.
...................................................................................................................................................................................................................................
15-236 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance GRS_gPSAntennaPositionUnknown
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-237
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
GRS_gPSReceiverFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GRS_gPSReceiverFailure alarm.
Description
The Common Timing Unit (CTU) detected a Global Positioning System (GPS) receiver
failure.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
This Node B will not provide GRS service.
1 At the Node B, make sure that the GPS antenna, the GPS antenna cable, receiver, and
the clock splitter are working properly.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
15-238 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance GRS_gPSReceiverFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-239
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
GRS_gPSReceiverUnavailable
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GRS_gPSReceiverUnavailable.
Description
The GPS receiver is not available.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Underlying resource unavailable.
System impact
This Node B will not provide GRS service.
1 At the OMC-UPS, check for CTU alarms and perform the fault clearance procedure for
these alarms.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
15-240 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
GRS_satelliteHealthyThresholdExceededForAllVisibleSatellites
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GRS_satelliteHealthyThreshold-
ExceededForAllVisibleSatellites alarm.
Description
The NodeB detects that for all visible satellites the averaged pseudorange correction
value exceeds the Satellite Healthy Threshold.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
The coordinates of the GPS antenna are not correct.
System impact
This NodeB will not provide GRS service.
1 At the OMC-UPS, check the coordinates of the GPS antenna. Consider initiating a self
survey so that the GPS antenna location can be determined autonomously by the
system.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-241
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures GRS_satelliteHealthyThresholdExceededForAllVisibleSatellites
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-242 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
GRS_secondPortNumberAlreadyInUse
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GRS_secondPortNumberAlreadyI-
nUse alarm.
Description
The GRS could not open a TCP/IP port with the specified port number because there is
already another port opened with the same port number.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
The operator selected a port number which was already assigned previously to another
service.
System impact
This NodeB will not provide GRS service.
1 At the OMC-UPS, lock the GRS object, update secondPortNumber attribute to assign
another port number and unlock the GRS object.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-243
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance GRS_secondPortNumberAlreadyInUse
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-244 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
GRS_selfSurveyFailed
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GRS_selfSurveyFailed.
Description
The Self Survey could not be completed successfully.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Underlying resource unavailable.
System impact
This Node B will not provide GRS service.
2 At the OMC-UPS, check for CTU alarms and perform fault clearance procedure of
these alarms.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-245
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance GRS_selfSurveyFailed
procedures
....................................................................................................................................................................................................................................
15-246 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
IMAGroup alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the IMA Group alarms.
Contents
IMAGroup_criticalGroupAlarm 15-248
IMAGroup_criticalGroupConfigurationAlarm 15-250
IMAGroup_majorGroupAlarm 15-252
IMAGroup_noncriticalGroupConfigurationAlarm 15-254
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-247
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IMAGroup_criticalGroupAlarm
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IMAGroup_criticalGroupAlarm
alarm.
Description
This alarm indicates a critical problem for the IMA Group. The IMA Group is no
longer operational.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Possible root causes are:
1. All transmit and/or all receive links are down.
2. ATM Edge Device indicates that less than minimum number of transmit or receive
links are active.
3. ATM Edge Device indicates the group is starting up.
4. ATM Edge Device indicates it is blocked.
5. This IMAGroup is not configured on ATM Edge Device.
System impact
IMA Group not available for traffic if the alarm is pending and the operational state of
the IMAGroup MO is disabled.
In case of a intermittent fault condition, the alarm is only cleared if the fault didn’t
occur again within 20 minutes.
...................................................................................................................................................................................................................................
15-248 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance IMAGroup_criticalGroupAlarm
procedures
1 At the OMC-UPS, check for E1T1Port alarms and perform fault clearance procedures
for these alarms.
If the alarm is cleared, together with the E1T1Port alarms, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-249
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IMAGroup_criticalGroupConfigurationAlarm
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IMAGroup_criticalGroupConfigu-
rationAlarm alarm.
Description
This Alarm indicates a critical configuration problem for the IMA Group detected on
Node B.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Configuration failure:
1. The ATM Edge Device tries to use unacceptable configuration parameters.
2. The ATM Edge Device reports unacceptable configuration parameters.
System impact
IMA Group not available for traffic.
1 At the OMC-UPS, verify the IMA Group parameters and correct the configuration.
...................................................................................................................................................................................................................................
15-250 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance IMAGroup_criticalGroupConfigurationAlarm
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-251
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IMAGroup_majorGroupAlarm
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IMAGroup_majorGroupAlarm alarm.
Description
This alarm indicates a major problem for the IMA Group. The IMA group is still
operational
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Possible root causes:
• One or more IMA links have failed.
• Number of auto-detected enabled IMA links less than number of configured IMA
links.
System impact
Bandwidth of IMA Group is degraded if the alarm is pending and the operational state
/ AVS of the IMAGroup MO is enabled / degraded.
In case of a intermittent fault condition, the alarm is only cleared if the fault did not
occur again within 20 minutes.
...................................................................................................................................................................................................................................
15-252 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance IMAGroup_majorGroupAlarm
procedures
1 At the OMC-UPS, check for criticalGroupAlarm and perform the fault clearance
procedure for that alarm.
If the alarm is cleared, together with the criticalGroupAlarm, the procedure is
completed
...................................................................................................................................................................................................
2 At the OMC-UPS, check for E1T1Port alarms and perform fault clearance procedure
for these alarms.
If the alarm is cleared, together with the E1T1Port alarms, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-253
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IMAGroup_noncriticalGroupConfigurationAlarm
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IMAGroup_noncriticalGroupCon-
figurationAlarm alarm.
Description
This Alarm indicates a noncritical configuration problem for the IMA Group detected
on NodeB.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Possible root causes:
1. Configuration mismatch between the ATM Edge Device and the NodeB: configured
IMA links do not match auto-detected ones.
2. Different timeslot allocation detected for E1T1Ports of the same IMAGroup.
3. At least one traffic PVC configured via IubInterface object has been blocked or its
bandwidth has been reduced, since the configured bandwidth of the IMAGroup
cannot carry all PVCs of the IubInterface object.
System impact
Traffic on IMA Group may be degraded.
...................................................................................................................................................................................................................................
15-254 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance IMAGroup_noncriticalGroupConfigurationAlarm
procedures
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-255
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Input Output Unit (IOU).
Contents
IOU_communicationFailure 15-258
IOU_externalAlarmPort0 15-260
IOU_externalAlarmPort1 15-262
IOU_externalAlarmPort10 15-264
IOU_externalAlarmPort11 15-266
IOU_externalAlarmPort12 15-268
IOU_externalAlarmPort13 15-270
IOU_externalAlarmPort14 15-272
IOU_externalAlarmPort15 15-274
IOU_externalAlarmPort16 15-276
IOU_externalAlarmPort17 15-278
IOU_externalAlarmPort18 15-280
IOU_externalAlarmPort19 15-282
IOU_externalAlarmPort2 15-284
IOU_externalAlarmPort20 15-286
IOU_externalAlarmPort21 15-288
IOU_externalAlarmPort22 15-290
IOU_externalAlarmPort23 15-292
IOU_externalAlarmPort24 15-294
IOU_externalAlarmPort25 15-296
IOU_externalAlarmPort26 15-298
IOU_externalAlarmPort27 15-300
IOU_externalAlarmPort28 15-302
IOU_externalAlarmPort29 15-304
...................................................................................................................................................................................................................................
15-256 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Overview
procedures
IOU_externalAlarmPort3 15-306
IOU_externalAlarmPort30 15-308
IOU_externalAlarmPort31 15-310
IOU_externalAlarmPort4 15-312
IOU_externalAlarmPort5 15-314
IOU_externalAlarmPort6 15-316
IOU_externalAlarmPort7 15-318
IOU_externalAlarmPort8 15-320
IOU_externalAlarmPort9 15-322
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-257
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_communicationFailure alarm.
Description
Heartbeat synchronization between the Input Output Unit (IOU) and the Universal
Radio Controller (URC) has been lost.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
The system will be impacted as indicated below:
• Communication to the RNC and OMC-U might be affected in case of E1/T1.
• User alarms are no longer signaled if the alarm is pending and the operational state
of the IOU MO is disabled.
• In case of a intermittent fault condition, the alarm is only cleared if the fault didn’t
occur again within 3 hours.
1 At the Node B, make sure that the IOU is mounted properly in the shelf.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-258 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance IOU_communicationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-259
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort0
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort0 alarm.
Description
An alarm on external alarm port 0 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 0.
2 Request a service technician to take action depending upon the user-defined specific
Problem.
...................................................................................................................................................................................................................................
15-260 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance IOU_externalAlarmPort0
procedures
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-261
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort1
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort1 alarm.
Description
An alarm on external alarm port 1 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 1.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-263
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort10
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort10 alarm.
Description
An alarm on external alarm port 10 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 10.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-265
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort11
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort11 alarm.
Description
An alarm on external alarm port 11 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 11.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-267
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort12
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort12 alarm.
Description
An alarm on external alarm port 12 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 12.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-269
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort13
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort13 alarm.
Description
An alarm on external alarm port 13 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 13.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-271
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort14
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort14 alarm.
Description
An alarm on external alarm port 14 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 14.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-273
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort15
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort15 alarm.
Description
An alarm on external alarm port 15 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 15.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-275
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort16
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort16 alarm.
Description
An alarm on external alarm port 16 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 16.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-277
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort17
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort17 alarm.
Description
An alarm on external alarm port 17 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 17.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-279
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort18
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort18 alarm.
Description
An alarm on external alarm port 18 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 18.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-281
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort19
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort19 alarm.
Description
An alarm on external alarm port 19 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 19.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-283
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort2
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort2 alarm.
Description
An alarm on external alarm port 2 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 2.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-285
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort20
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort20 alarm.
Description
An alarm on external alarm port 20 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 20.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-287
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort21
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort21 alarm.
Description
An alarm on external alarm port 21 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 21.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-289
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort22
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort22 alarm.
Description
An alarm on external alarm port 22 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 22.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-291
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort23
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort23 alarm.
Description
An alarm on external alarm port 23 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 23.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-293
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort24
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort24 alarm.
Description
An alarm on external alarm port 24 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 24.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-295
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort25
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort25 alarm.
Description
An alarm on external alarm port 25 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 25.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-297
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort26
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort26 alarm.
Description
An alarm on external alarm port 26 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 26.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-299
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort27
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort27 alarm.
Description
An alarm on external alarm port 27 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 27.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-301
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort28
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort28 alarm.
Description
An alarm on external alarm port 28 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 28.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-303
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort29
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort29 alarm.
Description
An alarm on external alarm port 29 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 29.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-305
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort3
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort3 alarm.
Description
An alarm on external alarm port 3 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 3.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-307
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort30
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort30 alarm.
Description
An alarm on external alarm port 30 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 30.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-309
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort31
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort31 alarm.
Description
An alarm on external alarm port 31 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 31.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-311
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort4
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort4 alarm.
Description
An alarm on external alarm port 4 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 4.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-313
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort5
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort5 alarm.
Description
An alarm on external alarm port 5 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 5.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-315
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort6
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort6 alarm.
Description
An alarm on external alarm port 6 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 6.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-317
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort7
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort7 alarm.
Description
An alarm on external alarm port 7 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 7.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-319
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort8
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort8 alarm.
Description
An alarm on external alarm port 8 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 8.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-321
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
IOU_externalAlarmPort9
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IOU_externalAlarmPort9 alarm.
Description
An alarm on external alarm port 9 has been detected. The description depends on the
site-specific configuration and is contained in the alarm text.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
The probable cause depends on the site-specific configuration.
System impact
This depends on the nature of the external equipment connected to the external alarm
port 9.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-323
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Iub interface.
Contents
IubInterface_rNCCommunicationLost 15-325
...................................................................................................................................................................................................................................
15-324 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
IubInterface_rNCCommunicationLost
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IubInterface_rNCCommunicationLost
alarm.
Description
The ALCAP and/or NBAP connection to the RNC has failed.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• Hardware problems
• Link failure
• Communication software failure on the Node B or the RNC
System impact
Loss of service for the whole Node B if the alarm is pending and the operational state
of the IubInterface MO is disabled. The operational state is set to disabled if ALCAP
and/or NBAP connection is down.
In case of a intermittent fault condition, the alarm is only cleared if the fault didn’t
occur again within 20 minutes.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-325
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance IubInterface_rNCCommunicationLost
procedures
1 At the OMC-UPS, check for RNC alarms indicating IubInterface problems and perform
fault clearance procedure for these alarms
If the alarm is cleared, together with the RNC alarms, the procedure is completed.
...................................................................................................................................................................................................
3 At the OMC-UPS, verify and if necessary correct the ATM settings for the ALCAP and
NBAP connection.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-326 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
NodeB alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the NodeB object alarms.
Contents
NodeB_alarmDefFileCorrupt 15-328
NodeB_alarmDefFileMissing 15-330
NodeB_databaseCleared 15-332
NodeB_databaseRestoredFromSnapshot 15-335
NodeB_filesystemNearingCapacity 15-337
NodeB_filesystemObjectCorrupt 15-339
NodeB_invalidSecurityDataDetected 15-341
NodeB_ipfwNatRulesAltered 15-343
NodeB_nodeBTypeMismatch 15-345
NodeB_snapshotFailed 15-347
NodeB_unauthorizedLoginAttempt 15-349
NodeB_userPasswordLoginAttempt 15-351
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-327
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
NodeB_alarmDefFileCorrupt
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_alarmDefFileCorrupt alarm.
Description
The Alarm Definition File (ADF) is corrupted and could not be parsed.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
ADF corrupted due to hardware problem or manual intervention
System impact
No impact on service
1 At the OMC-UPS, perform the update alarm definition use case to download and
install a default or modified ADF on the NodeB.
...................................................................................................................................................................................................................................
15-328 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance NodeB_alarmDefFileCorrupt
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-329
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
NodeB_alarmDefFileMissing
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_alarmDefFileMissing alarm.
Description
The Alarm Definition File (ADF) could not be found.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Probable root causes are:
• ADF lost due to software problem
• Hardware problem
• Manual intervention
System impact
No impact on service
1 At the OMC-UPS, perform the update alarm definition use case to download and
install a default or modified ADF on the NodeB.
...................................................................................................................................................................................................................................
15-330 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance NodeB_alarmDefFileMissing
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-331
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
NodeB_databaseCleared
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_databaseCleared alarm.
Description
The Node B started up with an empty (initial) database, because:
• The Node B detected an inconsistent database and could not recover from the
snapshot file
• The Node B performed cyclic reboots.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Probable causes of the inconsistent database are:
• Hardware failure of the flash filesystem, which causes a corrupt filesystem
• Software failure
In case of cyclic reboots, the Node B clears the database as a local foult defense to
prevent the Node B performing cyclic reboots.
System impact
The Node B performs a reset and starts with an empty database. Therefore no call
processing is possible.
...................................................................................................................................................................................................................................
15-332 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance NodeB_databaseCleared
procedures
2 At the OMC-UPS, run the restore NodeB database command to restore the selected
backup database file on the Node B.
If the Node B data have been restored successfully, the procedure is completed.
Otherwise continue with step 10.
...................................................................................................................................................................................................
3 At the OMC-UPS, copy the suspect database file to the backup directory of the Node
B on the OMC-UPS.
Source directory is /data/snapshot/<nodeb_local_identifier>
Target directory is /backup/backups/NodeB/<nodeb_local_identifier>
The <nodeb_local_identifier> is the ″Local identifier″, which is stored under the NE
Management Parameters of the Node B.
...................................................................................................................................................................................................
5 At the OMC-UPS, run the restore NodeB database command to restore the suspect
database file on the Node B.
If the Node B data have been restored successfully, the procedure is completed.
...................................................................................................................................................................................................
6 Contact Alcatel-Lucent customer support to get the suspect database file repaired.
...................................................................................................................................................................................................
7 At the OMC-UPS, store the repaired database file on the OMC-UPS under the backup
directory of the Node B.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-333
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance NodeB_databaseCleared
procedures
...................................................................................................................................................................................................
9 At the OMC-UPS, run the restore Node B database command to restore the repaired
database file on the Node B.
If the Node B data has been restored successfully, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-334 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
NodeB_databaseRestoredFromSnapshot
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_databaseRestoredFrom-
Snapshot alarm.
Description
The Node B has restored the database from the snapshot that was stored at the FTP
server (OMC-U). The database is restored as a recovery action after the Node B has
detected an inconsistent database during startup.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
This alarm indicates the database restore recovery action is performed after an
inconsistent database was detected by the Node.
Probable causes of the inconsistent database are:
• Hardware failure of the flash filesystem, which causes a corrupt filesystem
• Software failure during activation of new Node B software
• Software failure or corrupt database during restore of Node B database backup
• Software failure because of Node B reset during a Node B database update.
System impact
During the reset no call processing is possible. When the reset completes, call
processing is possible again.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-335
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance NodeB_databaseRestoredFromSnapshot
procedures
1 If ... then ..
the alarm is raised as part of a the new software could not recover from the
node B software activation, database.
Contact Alcatel-Lucent customer support.
the alarm is raised as part of a the software could not restart with that database
restore of a database backup, and restored the database from the snapshot.
Contact Alcatel-Lucent customer support.
the alarm is raised as part of the latest Itf-B commands are not included in the
updating the database via Itf-B, restored snapshot.
Repeat the Itf-B commands.
the alarm is raised for other there may be a hardware failure of the flash
reasons, filesystem.
Contact Alcatel-Lucent customer support to check
the URC.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-336 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
NodeB_filesystemNearingCapacity
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_filesystemNearingCapacity
alarm.
Description
The filesystem on the persistent file storage is near capacity.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Unnecessary files are stored on the filesystem. Probably more than two NodeB
software versions are stored on the filesystem
System impact
No immediate service impact, but if the space continues to fill up, there will be
adverse effects, possibly leading to loss of data and NodeB reset. Snapshots of the
local database onto the FTP server are not performed.
1 At the OMC-UPS, avoid any configuration update for the NodeB, since the space
would continue to fill up.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-337
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance NodeB_filesystemNearingCapacity
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, use the remote RMT tool to check the filesystem of the NodeB.
Remove NodeB SW versions, which are not required.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-338 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
NodeB_filesystemObjectCorrupt
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_filesystemObjectCorrupt
alarm.
Description
A corrupt filesystem object has been detected.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
Partially corrupted filesystem
System impact
None.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-339
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance NodeB_filesystemObjectCorrupt
procedures
....................................................................................................................................................................................................................................
15-340 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
NodeB_invalidSecurityDataDetected
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_invalidSecurityDataDetected
alarm.
Description
Invalid security data for the nodeB has been detected.
This indicates that an unknown security data exists which controls access to the
NodeB.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
securityServiceOrMechanismViolation
Root cause
Unspecified
System impact
An unknown security data compromises NodeB security.
1 At the OMC-UPS, investigate the invalid security data, determining how and why it
was caused.
Inform the security organisation and take appropriate action to correct the security data.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-341
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance NodeB_invalidSecurityDataDetected
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-342 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
NodeB_ipfwNatRulesAltered
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_ipfwNatRulesAltered alarm.
Description
Internet Protocol Firewall (IPFW) or Network Address Table rules have been altered.
This determines the fundamental port security and authorization on the NodeB.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
integrityViolation
Root cause
The IPFW or NAT rules have been altered.
System impact
These rules determine port security and authorization on the NodeB, an unauthorized
change to these may indicate compromised security.
1 At the OMC-UPS, investigate how and why the alteration took place.
If the alterations were not authorized then the operator should inform their security
organisation, then take appropriate action to correct the rules.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-343
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance NodeB_ipfwNatRulesAltered
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-344 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
NodeB_nodeBTypeMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_nodeBTypeMismatch alarm.
Description
The attribute detectedNodeBType retrieved from the backplane eeprom does not match
the value of the attribute expectedNodeBType.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
There may be an inconsistency between created managed objects and installed
hardware that may lead to unavailability of affected resources.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-345
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance NodeB_nodeBTypeMismatch
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, use the Remote Maintenance Terminal (RMT) to set the correct
Node B type in the backplane eeprom.
...................................................................................................................................................................................................
3 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-346 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
NodeB_snapshotFailed
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_snapshotFailed alarm.
Description
The snapshot of Node B data to the FTP server has failed.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
This may alarm be reported as part of a Node B backup or as part of an autonomous
snapshot completed in case of data changes.
Probable causes are:
• FTP server down
• Link to FTP server interrupted
• FTP server misconfigured
• FTP server directory full.
• Collection and/or bundling of database has failed
System impact
No immediate effect on service, but system integrity endangered in case of loss of data
or corrupted data at the Node B.
The Node B will periodically retry to generate the snapshot. Once the snapshot is
generated the alarm will be cleared.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-347
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance NodeB_snapshotFailed
procedures
1 At the OMC-UPS, retrieve the detailed information from the additionalText field of the
alarm.
If the bundling and/or collection of the database has failed, contact Alcatel-Lucent
customer support.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-348 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
NodeB_unauthorizedLoginAttempt
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_unauthorizedLoginAttempt
alarm.
Description
The NodeB has detected an authentication failure.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
securityServiceOrMechanismViolation
Root cause
Failed SSH login attempt using user and key authentication.
System impact
None.
1 At the OMC-UPS, check whether the OMC-UPS application performed the failed login
attempt.
If so, ensure that the OMC-U is using the correct keys.
...................................................................................................................................................................................................
2 At the OMC-UPS, collect the security event logfile from the NodeB if required.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-349
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance NodeB_unauthorizedLoginAttempt
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, perform the security actions defined by the security organization.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-350 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
NodeB_userPasswordLoginAttempt
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the NodeB_userPasswordLoginAttempt
alarm.
Description
A username/password manual authentication attempt has been made.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
securityServiceOrMechanismViolation
Root cause
Successful or failed SSH login attempt using user and password authentication.
System impact
None.
2 At the OMC-UPS, check additionalText field of the alarm to establish if the login
attempt was successful or not.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-351
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance NodeB_userPasswordLoginAttempt
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, collect the security event logfile from the NodeB if required.
...................................................................................................................................................................................................
4 At the OMC-UPS, perform the security actions defined by the security organization.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-352 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
OCM alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the OCM alarms.
Contents
OCM_boardGenericMismatch 15-354
OCM_clockFailure30_72MHz 15-356
OCM_communicationFailure 15-357
OCM_initialisationFailure 15-359
OCM_lossOfForwardBusLink 15-360
OCM_lossOfPulse 15-361
OCM_missingconfigurationData 15-362
OCM_selfTestFailure 15-364
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-353
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OCM_boardGenericMismatch
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the OCM_boardGenericMismatch alarm.
Description
The software on the OCM could not be updated to the current version stored on the
URC, because the download failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-354 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance OCM_boardGenericMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-355
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OCM_clockFailure30_72MHz
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the OCM_clockFailure30_72MHz alarm.
Description
The 30.72 MHz clock signal from the CTU has failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-356 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
OCM_communicationFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the OCM_communicationFailure alarm.
Description
Heartbeat synchronisation between the OCM and the URC has been lost or timeout
occured during initialisation of the OCM.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-357
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance OCM_communicationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-358 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
OCM_initialisationFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the OCM_initialisationFailure alarm.
Description
The OneBTS CPRI module has failed to initialize correctly.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
1 At the OMC-UPS, determine the reason for failure and resolve the problem.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-359
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OCM_lossOfForwardBusLink
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the OCM_lossOfForwardBusLink alarm.
Description
Loss of forward bus link from all UCUs.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-360 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
OCM_lossOfPulse
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the OCM_lossOfPulse alarm.
Description
The OCM failed to detect the 10ms pulses.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-361
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OCM_missingconfigurationData
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the OCM_missingconfigurationData
alarm.
Description
Missing essential configuration parameters on OCM
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Software failure: missing configuration data
System impact
The OCM cannot be initiated to service. No calls are possible in the related cells.
2 At the OMC-UPS, reset the OCM object to initialize the OCM board.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-363
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OCM_selfTestFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the OCM_selfTestFailure alarm.
Description
Diagnostics on the OCM have failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
1 At the OMC-UPS, determine the reason for failure and resolve the problem..
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
15-364 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
OM alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Oscillator Module (OM).
Contents
OM_clockFailure15Mhz 15-366
OM_configurationMismatch 15-368
OM_frequencyOutOfRange 15-370
OM_hardwareModelMismatch 15-372
OM_inactive 15-375
OM_maintenanceRequested 15-377
OM_phaseLockLoopFailure 15-380
OM_temperatureOutOfRange 15-382
OM_underTemperature 15-384
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-365
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OM_clockFailure15Mhz
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the OM_clockFailure15Mhz alarm.
Description
The 15 MHz clock signal from the Oscillator Module (OM) has been lost.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
Calls on the whole Node B will drop.
2 At the Node B, make sure that the Oscillator Module is mounted properly in the shelf.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and re-initialize the Oscillator Module.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-366 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance OM_clockFailure15Mhz
procedures
...................................................................................................................................................................................................
4 At the Node B, make sure that the cabling between the Oscillator Module and the I/O
panel is OK.
...................................................................................................................................................................................................
5 At the OMC-UPS, reset the CTU object to reset and re-initialize the Oscillator Module.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-367
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OM_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the OM_configurationMismatch alarm.
Description
The configuration conflicts with attribute value(s) of other object(s).
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No service available
1 At the Node B, check for nodeBTypeMismatch alarm of the NodeB object and perform
the fault clearance procedure for that alarm.
If this alarm is cleared together with the nodeBTypeMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................................................
15-368 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance OM_configurationMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-369
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OM_frequencyOutOfRange
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the OM_frequencyOutOfRange alarm.
Description
The frequency generated by the Oscillator Module (OM) onboard the CTU is out of
range
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment failure or network clock failure
System impact
Call processing may be impacted:
• Cells not available to the UE (sleeping cell)
• Handover not possible to cells of the affected NodeB
• Radio frequency being out of the assigned band
1 At the OMC-UPS, determine if the alarm occurs for single or multiple Node Bs.
...................................................................................................................................................................................................
2 In the case of multiple Node Bs being affected, check and repair the network clock
...................................................................................................................................................................................................................................
15-370 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance OM_frequencyOutOfRange
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-371
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OM_hardwareModelMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the OM_hardwareModelMismatch alarm.
Description
The detected Oscillator Module (OM) does not match the value specified.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No impact on service.
...................................................................................................................................................................................................................................
15-372 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance OM_hardwareModelMismatch
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, update the expected hardware model attribute to match the detected
hardware model attribute.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-373
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance OM_hardwareModelMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-374 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
OM_inactive
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the OM_inactive alarm.
Description
The Oscillator Module (OM) is not operational.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
Calls on the whole Node B will drop.
2 At the Node B, make sure that the Oscillator Module is mounted properly in the shelf.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and re-initialize the Oscillator Module.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-375
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance OM_inactive
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-376 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
OM_maintenanceRequested
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the OM_maintenanceRequested alarm.
Description
The Oscillator Module (OM) sends a message to indicate that it can no longer
compensate for frequency shift.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
OM frequency can no longer be adjusted. Call processing may be impacted.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-377
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance OM_maintenanceRequested
procedures
1 At the OMC-UPS, check if this alarm occurs only for a single NodeB or whether it
occurs for several NodeBs belonging to the same part of the network .
If... Then...
in case of a single NodeB the carry out the fault clearance procedure as defined
OM is likely to be defective. Go to step 2.
Otherwise the network timing
might be out of sync.
In case of several NodeBs check and repair the network clock.
belonging to the same part of the
network,
...................................................................................................................................................................................................
2 At the OMC-UPS, reset the CTU object to initialize the Ocillator Module.
Use the reset type type0 to trigger a software reset.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to initialize the Ocillator Module.
Use the reset type type1 to trigger a power cycle.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the Node B, make sure that the Oscillator Module is mounted properly in the shelf.
...................................................................................................................................................................................................
5 At the OMC-UPS, reset the CTU object to initialize the Oscillator Module.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-378 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance OM_maintenanceRequested
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-379
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OM_phaseLockLoopFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the OM_phaseLockLoopFailure alarm.
Description
The Oscillator Module Phase Lock Loop failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Clock synchronization problem.
System impact
Calls on the whole Node B will drop.
2 At the Node B, make sure that the Oscillator Module is mounted properly in the shelf.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and re-initialize the Oscillator Module.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-380 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance OM_phaseLockLoopFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-381
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OM_temperatureOutOfRange
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the OM_temperatureOutOfRange alarm.
Description
The Oscillator Module temperature sensor detected that the temperature has exceeded
the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Probable causes are:
• Defective heater on OM.
• Environmental temperature too high.
System impact
Calls on the whole Node B will drop.
1 At the OMC-UPS check for Frame and DigitalShelfFan alarms and perform the fault
clearance procedure for these alarms.
...................................................................................................................................................................................................................................
15-382 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance OM_temperatureOutOfRange
procedures
2 At the Node B, make sure that the system is operating within its operational
temperature.
If the temperatureOutOfRange alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and re-initialize the Oscillator Module,
if the temperatureOutOfRange alarm has been reported several times and so the CTU
and OM have been isolated
If the alarm is cleared and not reported again, the procedure is completed
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-383
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
OM_underTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the OM_underTemperature alarm.
Description
The Oscillator Module temperature sensor detected that the temperature is below the
specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Probable causes are:
• Defective heater on OM.
• Environmental temperature too low.
System impact
Calls on the whole Node B will drop.
1 At the OMC-UPS check for Frame alarms and perform the fault clearance procedure
for these alarms.
...................................................................................................................................................................................................................................
15-384 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance OM_underTemperature
procedures
2 At the Node B, make sure that the system is operating within its operational
temperature.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the CTU object to reset and re-initialize the Oscillator Module,
if the underTemperature alarm has been reported several times and so the CTU and
OM have been isolated.
If the alarm is cleared and not reported again, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-385
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RETActuator alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the RET Actuator alarms.
Contents
RETActuator_actuatorJam 15-387
RETActuator_calibrationLost 15-389
RETActuator_communicationFailure 15-391
RETActuator_deviceTypeMismatch 15-393
RETActuator_hardwareFailure 15-394
RETActuator_positionLost 15-396
RETActuator_softwareFailure 15-398
RETActuator_tiltAngleOutOfRange 15-400
...................................................................................................................................................................................................................................
15-386 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RETActuator_actuatorJam
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RETActuator_actuatorJam alarm.
Description
Actuator jam has been detected.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
RET Actuator is stuck. The alarm does not imply that the position or calibration has
been lost.
System impact
RET Actuator can not be moved. No impact on call processing.
1 At the OMC-UPS, wait some time (at least one hour) for automatic clearance of the
alarm.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-387
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance RETActuator_actuatorJam
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-388 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RETActuator_calibrationLost
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RETActuator_calibrationLost alarm.
Description
The RET Actuator has lost its calibration
Default severity
Major
Alarm type
equipmentAlarm
Root cause
The RET Actuator has not completed a calibration action or calibration has been lost
due to power interruption.
System impact
Current position of actuator is not changed. The detectedElectricalTilt attribute of
RETActuator object may be incorrect. No impact on call processing.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-389
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance RETActuator_calibrationLost
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-390 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RETActuator_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RETActuator_communicationFailure
alarm.
Description
The communication to the RET Actuator cannot be established or has been lost.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment failure or cabling problem
System impact
RET Actuator not operational. NodeB cyclicly tries to reconnect. No impact on call
processing
1 At the OMC-UPS, wait several minutes for automatic clearance of the alarm..
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the NodeB, check cabling between the ALD Controller and the RET Actuator.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-391
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance RETActuator_communicationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-392 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RETActuator_deviceTypeMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RETActuator_deviceTypeMismatch
alarm.
Description
The detected device type is not a RET device.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Wrong device connected.
System impact
RETActuator not operational.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-393
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RETActuator_hardwareFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RETActuator_hardwareFailure alarm.
Description
A hardware failure has occured on the RET Actuator.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The RET Actuator is reset and reinitialized autonomously. During that time the actuator
is not operational.
...................................................................................................................................................................................................................................
15-394 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RETActuator_hardwareFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-395
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RETActuator_positionLost
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RETActuator_positionLost alarm.
Description
The RET Actuator has lost its position.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
ALD system is unable to return a correct position value for example due to a power
failure
System impact
Current position of actuator is not changed. The detectedElectricalTilt attribute of
RETActuator object may be incorrect. No impact on call processing
...................................................................................................................................................................................................................................
15-396 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RETActuator_positionLost
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-397
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RETActuator_softwareFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RETActuator_softwareFailure alarm.
Description
A software failure has occured on the RET actuator.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Software error.
System impact
The RET actuator is reset and reinitialized autonomously. During that time the RET
actuator is not operational. No impact on call processing.
...................................................................................................................................................................................................................................
15-398 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RETActuator_softwareFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-399
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RETActuator_tiltAngleOutOfRange
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RETActuator_tiltAngleOutOfRange
alarm.
Description
The requested tilt angle is beyond minimum or maximum electrical tilt.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
Configuration problem
System impact
The RET Actuator is still operational. The RET Actuator stopped at minimum or
maximum electrical tilt. No impact on call processing.
...................................................................................................................................................................................................................................
15-400 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RETActuator_tiltAngleOutOfRange
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-401
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the RFHead alarms.
Contents
RFHead_boardGenericMismatch 15-404
RFHead_clockFailure 15-406
RFHead_communicationFailure 15-407
RFHead_criticalTransmitterAlarm 15-409
RFHead_dCInputFailure 15-411
RFHead_diversityImbalance 15-412
RFHead_externalAlarmPort0 15-414
RFHead_externalAlarmPort1 15-415
RFHead_externalAlarmPort2 15-416
RFHead_externalAlarmPort3 15-417
RFHead_externalAlarmPort4 15-418
RFHead_externalAlarmPort5 15-419
RFHead_fibreLOF 15-420
RFHead_fibreLOS 15-422
RFHead_fibreRAI 15-424
RFHead_fibreSAPDefect 15-426
RFHead_fibreSigLow 15-428
RFHead_initialisationFailure 15-430
RFHead_noncriticalTransmitterAlarm 15-431
RFHead_overTemperature 15-433
RFHead_rFOverdrive 15-435
RFHead_receiver1Failure 15-436
RFHead_receiver2Failure 15-437
RFHead_receiverFailure 15-438
...................................................................................................................................................................................................................................
15-402 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Overview
procedures
RFHead_selfTestFailure 15-439
RFHead_softwareFailure 15-440
RFHead_temperatureOutOfRange 15-441
RFHead_txActivationFailure 15-443
RFHead_underTemperature 15-444
RFHead_vSWRAlarm 15-445
RFHead_warmup 15-446
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-403
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_boardGenericMismatch
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_boardGenericMismatch
alarm.
Description
The software on the RFHead could not be updated to the current version stored on the
URC, because the download failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-404 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RFHead_boardGenericMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-405
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_clockFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_clockFailure alarm.
Description
One or more digital clocks and/or the frequency reference have failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-406 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_communicationFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_communicationFailure
alarm.
Description
synchronisation between the RFHead and the URC has been lost or timeout occured
during initialisation of the RFHead.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-407
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance RFHead_communicationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-408 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_criticalTransmitterAlarm
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_criticalTransmitterAlarm
alarm.
Description
The RF-Head experienced a critical transmitter failure.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-409
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance RFHead_criticalTransmitterAlarm
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-410 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_dCInputFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_dCInputFailure alarm.
Description
Low or high DC Input is being detected.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-411
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_diversityImbalance
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_diversityImbalance alarm.
Description
The delta between receive antenna 1 and receive antenna 2 has exceeded a specified
threshold.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-412 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RFHead_diversityImbalance
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-413
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_externalAlarmPort0
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_externalAlarmPort0 alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-414 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_externalAlarmPort1
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_externalAlarmPort1 alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-415
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_externalAlarmPort2
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_externalAlarmPort2 alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-416 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_externalAlarmPort3
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_externalAlarmPort3 alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-417
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_externalAlarmPort4
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_externalAlarmPort4 alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-418 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_externalAlarmPort5
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_externalAlarmPort5 alarm.
Description
This string is derived from the externalAlarm attribute.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-419
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_fibreLOF
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_fibreLOF alarm.
Description
The master port of the previous RF Head or the slave port of this RF Head has
encountered a loss of frame.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-420 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RFHead_fibreLOF
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-421
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_fibreLOS
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_fibreLOS alarm.
Description
The master port of the previous RF Head or the slave port of this RF Head has
encountered a loss of signal.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-422 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RFHead_fibreLOS
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-423
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_fibreRAI
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_fibreRAI alarm.
Description
The master port of the previous RF Head or the slave port of this RF head has
encountered a remote alarm signal.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-424 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RFHead_fibreRAI
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-425
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_fibreSAPDefect
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_fibreSAPDefect alarm.
Description
The master port of the previous RF Head or the slave port of this RF Head has
encountered a service access point defect.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-426 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RFHead_fibreSAPDefect
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-427
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_fibreSigLow
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_fibreSigLow alarm.
Description
The master port of the previous RF head or the slave port of this RF Head has
encountered a low optical signal.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-428 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance RFHead_fibreSigLow
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-429
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_initialisationFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_initialisationFailure alarm.
Description
The RFHead module failed to initialise properly.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-430 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_noncriticalTransmitterAlarm
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_noncriticalTransmitterAlarm
alarm.
Description
The RF Head experienced a minor transmitter failure.
Default severity
Warning
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-431
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance RFHead_noncriticalTransmitterAlarm
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-432 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_overTemperature
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_overTemperature alarm.
Description
The RF head is over the operational temperature limit but the RF head is still
operational.
Default severity
Warning
Alarm type
environmentalAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-433
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance RFHead_overTemperature
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-434 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_rFOverdrive
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_rFOverdrive alarm.
Description
The RF head is being overdriven by the OCM.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-435
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_receiver1Failure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RFHead_receiver1Failure alarm.
Description
The RF Head is experiencing difficulty in the first receive path. A failure of the
External Rx Amplifier (TTLNA) in Rx Path 1 will also trigger this alarm.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-436 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_receiver2Failure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RFHead_receiver2Failure alarm.
Description
The RF Head is experiencing difficulty in the second receive path. A failure of
theExternal Rx Amplifier (TTLNA) in Rx Path 2 will also trigger this alarm.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-437
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_receiverFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_receiverFailure alarm.
Description
The RF Head is experiencing a failure on both receive paths.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-438 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_selfTestFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_selfTestFailure alarm.
Description
Diagnostics on the RFHead have failed and operation is not possible.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-439
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_softwareFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_softwareFailure alarm.
Description
The RF Head has encountered a software failure.
Default severity
Warning
Alarm type
processingErrorAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-440 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_temperatureOutOfRange
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
Ye
This topic provides the procedure for clearing the RFHead_temperatureOutOfRange
alarm.
Description
The RF head transmitter has shut down due to critical temperature.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-441
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance RFHead_temperatureOutOfRange
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-442 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_txActivationFailure
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_txActivationFailure alarm.
Description
The RF head has failed to activate the transmitter.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-443
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_underTemperature
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_underTemperature alarm.
Description
The RF Head is transmitting below its normal operating temperature.
Default severity
Warning
Alarm type
environmentalAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-444 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RFHead_vSWRAlarm
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_vSWRAlarm alarm.
Description
VSWR level has fallen below alarm threshold.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-445
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RFHead_warmup
...................................................................................................................................................................................................................................
Purpose
Important! This managed object is not currently supported.
This topic provides the procedure for clearing the RFHead_warmup alarm.
Description
The RF Head warms up, since its components are not warm enough for operation.
Default severity
Major
Alarm type
environmentalAlarm
Root cause
TBA.
System impact
TBA.
...................................................................................................................................................................................................................................
15-446 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Radio.
Contents
Radio_applicationInsane 15-449
Radio_boardGenericMismatch 15-450
Radio_clockFailure30_72Mhz 15-452
Radio_communicationFailure 15-455
Radio_configurationMismatch 15-457
Radio_criticalGainFailure 15-459
Radio_digitalClippingDetected 15-461
Radio_diversityImbalance 15-463
Radio_fPGAFailure 15-465
Radio_filterPanelRecordInvalid 15-467
Radio_hardwareModelMismatch 15-469
Radio_hwErrorDetectedByPlatformSw 15-471
Radio_initialisationFailure 15-473
Radio_internalGainFailure 15-475
Radio_localConfigurationFailure 15-477
Radio_lossOfDemodulatorSynthesizerSynchronisation 15-479
Radio_lossOfForwardBusLink 15-482
Radio_lossOfModulatorSynthesizerSynchronisation 15-484
Radio_lossOfPulse 15-487
Radio_lossOfReceiveSynthesizerSynchronisation 15-490
Radio_lossOfTransmitSynthesizerSynchronisation 15-493
Radio_majorGainFailure 15-496
Radio_majorPlatformSwError 15-499
Radio_majorTxSpectrumFailure 15-500
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-447
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Overview
procedures
Radio_messageThrottleOn 15-503
Radio_minorGainFailure 15-505
Radio_missingConfigurationData 15-508
Radio_missingDelayCalibrationData 15-510
Radio_overTemperature 15-512
Radio_portMapInvalid 15-514
Radio_rFOverdrive 15-516
Radio_rFPathMismatch 15-518
Radio_resyncOfPulse 15-520
Radio_rx1PathFaultDetected 15-523
Radio_rx2PathFaultDetected 15-525
Radio_samplingReceiverFailure 15-527
Radio_selfTestFailure 15-529
Radio_synthesizerFailure122Mhz 15-531
Radio_synthesizerFailure15Mhz 15-533
Radio_tDUCommunicationFailure 15-535
Radio_toneGeneratorFailure 15-537
Radio_transmitGainLimitExceeded 15-539
Radio_transmitterSwitchFailure 15-542
Radio_transmitterSwitchOff 15-544
Radio_txActivationMalfunction 15-546
Radio_underTemperature 15-548
....................................................................................................................................................................................................................................
15-448 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_applicationInsane
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_applicationInsane alarm.
Description
The Radio application software is not functioning properly.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Software program error.
System impact
All calls in this cell are lost.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-449
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_boardGenericMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_boardGenericMismatch alarm.
Description
The software version on the Radio does not match with the current version stored,
because software download failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
The software on the Radio could not be updated, because the download to the Radio
failed.
System impact
The Radio can not be initiated to service. No calls in this cell are possible.
...................................................................................................................................................................................................................................
15-450 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_boardGenericMismatch
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the Radio object to update the software on the Radio.
If the alarm is cleared, the procedure is completed
...................................................................................................................................................................................................
4 At the OMC-UPS, check the state of the current NodeB software version via RMT. If
the state is not GOOD, reset the NodeB object
If the alarm is cleared, the procedure is completed
Result: The NodeB automatically downloads missing/corrupted software files from
the FTP server (OMC) and updates the software on the Radio.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-451
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_clockFailure30_72Mhz
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_clockFailure30_72Mhz alarm.
Description
The Radio detected loss of the 30.72Mhz clock.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem due to a CTU failure or to the clock circuitry in the Radio.
System impact
All calls in the cell that the Radio serves are lost.
...................................................................................................................................................................................................................................
15-452 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_clockFailure30_72Mhz
procedures
...................................................................................................................................................................................................
If... Then...
This is the only Radio that is Go to step 3.
reporting an error,
There are also CTU or Oscillator Go to step 7.
Module errors,
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-453
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_clockFailure30_72Mhz
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-454 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_communicationFailure alarm.
Description
Heartbeat synchronization between the Radio and the URC has been lost or timeout
occured during initialization or cyclic audit of the Radio.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Possible root causes are:
• Equipment failure
• Timing problem.
• Missing or pulled board.
• Backplane EEPROM not accessible
System impact
All calls in this cell are lost.
1 At the OMC-UPS, wait until the Radio reinitialization is completed. If the alarm is not
cleared within 5 minutes, the initialisation has failed.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-455
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_communicationFailure
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, solve any other error which would cause this alarm as a side effect.
...................................................................................................................................................................................................
4 At the Node B, make sure that the Radio is mounted properly in the frame.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-456 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_configurationMismatch alarm.
Description
The configuration conflicts with attribute value(s) of other object(s).
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No service available
1 At the Node B, check for nodeBTypeMismatch alarm of the NodeB object and perform
the fault clearance procedure for that alarm.
If this alarm is cleared together with the nodeBTypeMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-457
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_configurationMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-458 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_criticalGainFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_criticalGainFailure alarm.
Description
Radio gain control algorithm is not able to initialize correctly.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Hardware failure.
System impact
All calls in this cell are lost.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-459
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_criticalGainFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-460 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_digitalClippingDetected
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_digitalClippingDetected alarm.
Description
The Radio reports digital clipping.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Defective UCU.
System impact
Call capacity in the cell served by the Radio is reduced.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-461
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_digitalClippingDetected
procedures
...................................................................................................................................................................................................
...................................................................................................................................................................................................
9 Carry out several test calls in order to verify that the alarm is cleared
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-462 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_diversityImbalance
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_diversityImbalance alarm.
Description
The delta between receive antenna 1 and receive antenna 2 has exceeded a specified
threshold.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Probable causes are:
• Cable or connector problems
• Antenna problems
• Receiver failure.
System impact
The cell is degraded.
1 At the OMC-UPS, check for ExtRxAmp, Filter, RxAmp and Radio alarms and perform
fault clearance procedure related to these alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-463
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_diversityImbalance
procedures
...................................................................................................................................................................................................
2 At the Node B, make sure that the receive path (antenna, RF cable, filter unit, Radio
and cabling) is working properly.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-464 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_fPGAFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_fPGAFailure alarm.
Description
One of the Field Programmable Gate Arrays on the Radio has failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
No new calls are accepted, existing calls are dropped.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-465
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_fPGAFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-466 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_filterPanelRecordInvalid
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_filterPanelRecordInvalid
alarm.
Description
One or all filter panel records used for the configuration of the Radios are invalid.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Probable causes are:
• Port map might not match filter panel configuration
• Filter panel might be not connected
• Local filter panel EEPROM data corrupt.
System impact
The radio cannot be configured properly. The Cell that is supported by this radio
cannot be used.
1 At the OMC-UPS, use the remote RMT to make sure that the backplane EEPROM
data is OK.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-467
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_filterPanelRecordInvalid
procedures
...................................................................................................................................................................................................
5 At the Node B, make sure that all filter panels are mounted correctly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-468 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_hardwareModelMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_hardwareModelMismatch
alarm.
Description
The detected radio hardware model does not match the value specified.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No impact on service.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-469
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_hardwareModelMismatch
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, update the expected hardware model attribute to match the detected
hardware model attribute.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-470 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_hwErrorDetectedByPlatformSw
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_hwErrorDetectedByPlat-
formSw alarm.
Description
The platform that supports the application software has detected a potentially
unrecoverable hardware fault.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Hardware failure
System impact
All calls in the cell supported by this Radio will be dropped.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-471
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_hwErrorDetectedByPlatformSw
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-472 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_initialisationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_initialisationFailure alarm.
Description
The Radio failed to initialize.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The Radio cannot be initiated to service. No calls in this cell are possible.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-473
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_initialisationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-474 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_internalGainFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_internalGainFailure alarm.
Description
Radio internal gain is different from the expected gain.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
Hardware failure.
System impact
Output power variance is to be expected.The transmit spectrum may break mask.
If... Then...
If one of these alarms is pending replacement of the Radio is required, since the
Radio will not transmit at the correct power level.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-475
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_internalGainFailure
procedures
If... Then...
If one of these alarms is not replacement of the Radio is recommended, but not
pending urgently required, since the Radio will still
transmits at the correct power level.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-476 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_localConfigurationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_Radio_localConfiguration-
Failure alarm.
Description
The configuration conflicts with local configuration data..
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Missing or faulty local configuration data.
System impact
No service available
1 At the Node B, check for configurationMismatch alarm and perform fault clearance
procedure for that alarm..
If the alarm is cleared together with the configurationMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 At the OMC-UPS, check and update local configuration data via remote RMT.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-477
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_localConfigurationFailure
procedures
....................................................................................................................................................................................................................................
15-478 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_lossOfDemodulatorSynthesizerSynchronisation
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_lossOfDemodulatorSynthe-
sizerSynchronisation alarm.
Description
The demodulator is out of synchronization which causes the Rx signal to be out of
lock.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
All calls in this cell are lost.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-479
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_lossOfDemodulatorSynthesizerSynchronisation
procedures
...................................................................................................................................................................................................
2 If... Then...
There are also synthesizer errors Go to step 3.
on other Radios
There are no other synthesizer Go to step 11.
errors.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-481
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_lossOfForwardBusLink
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_lossOfForwardBusLink alarm.
Description
The Radio reported loss of the forward bus link.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
All calls in this cell are lost.
...................................................................................................................................................................................................
3 At the Node B, make sure that the timing (clock source, cables, Oscillator Module) to
the Radio are OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-483
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_lossOfModulatorSynthesizerSynchronisation
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_lossOfModulatorSynthe-
sizerSynchronisation alarm.
Description
The modulator is out of synchronization which causes the Tx signal to be out of lock.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
All calls in this cell are lost.
2 If... Then...
There are also synthesizer errors Go to step 3.
on other Radios.
...................................................................................................................................................................................................................................
15-484 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_lossOfModulatorSynthesizerSynchronisation
procedures
If... Then...
There are no other synthesizer Go to step 11.
errors.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-485
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_lossOfModulatorSynthesizerSynchronisation
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-486 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_lossOfPulse
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_lossOfPulse alarm.
Description
The 10 mSec pulses are not detected by the Radio.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
All calls in this cell are lost.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-487
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_lossOfPulse
procedures
...................................................................................................................................................................................................
If... Then...
This is theonlyRadio reporting Go to step 3.
this alarm,
This is not the only Radio Go to step 8.
reporting this alarm,
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-488 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_lossOfPulse
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-489
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_lossOfReceiveSynthesizerSynchronisation
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_lossOfReceiveSynthesiz-
erSynchronisation alarm.
Description
The Rx signal is no longer synchronized.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
All calls in this cell are lost.
2 If... Then...
There are also synthesizer errors Go to step 3.
on other Radios.
...................................................................................................................................................................................................................................
15-490 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_lossOfReceiveSynthesizerSynchronisation
procedures
If... Then...
There are no other synthesizer Go to step 11.
errors.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-491
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_lossOfReceiveSynthesizerSynchronisation
procedures
....................................................................................................................................................................................................................................
15-492 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_lossOfTransmitSynthesizerSynchronisation
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_lossOfTransmitSynthesiz-
erSynchronisation alarm.
Description
The Tx signal is no longer tuned. This indicates a clocking error.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
All calls in this cell are lost.
2 If... Then...
There are also synthesizer errors Go to step 3.
on other Radios.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-493
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_lossOfTransmitSynthesizerSynchronisation
procedures
If... Then...
There are no other synthesizer Go to step 11.
errors.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-494 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_lossOfTransmitSynthesizerSynchronisation
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-495
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_majorGainFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_majorGainFailure alarm.
Description
The Radio’s internal attenuators are at their limit or the Radio gain control algorithm is
not able to initialize correctly.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Cabling problem or hardware failure.
System impact
Radio output power variance is to be expected. The transmit spectrum may break
mask.
1 At the OMC-UPS, check for internalGainFailure alarm of the Radio and perform the
fault clearance procedure related to this alarm.
If the majorGainFailure alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-496 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_majorGainFailure
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, extract the additional information (CAI) from the additional text of
the alarm:
If... Then...
CAI=0XE: “transmit gain indicates at startup of Radio, that the gain control
out of range” algorithm has failed to lock resulting in a fallback
to local loop. Go to step 3.
CAI=0X8: “attenuation not indicates that attenuators have run out of
available – internal fault” adjustment by a large amount due to a fault
internal to the Radio. Go to step 9.
CAI=0X9: “attenuation not indicates that attenuators have run out of
available – external adjustment by a large amount due to a fault
fault” external to the Radio. Go to step 14.
CAI=0XA: “attenuation not indicates that the attenuators have run out of
available – unknown fault” adjustment by a large amount due to an unknown
fault. First run the fault clearance procedure for the
“attenuation not available – external fault” and if
the problem still persists, the fault clearance
procedure for the “attenuation not available –
internal fault”.
...................................................................................................................................................................................................
3 At the OMC-UPS, check for criticalGainFailure alarm of the Radio and perform fault
clearance procedure related to this alarm.
If the majorGainFailure alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the OMC-UPS, check for TxAmp alarms and perform the fault clearance procedures
related to these alarms.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
9 At the OMC-UPS, check for overTemperature alarms of the Radio and perform the
fault clearance procedure of these alarms.
If the majorGainFailure alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
14 At the OMC-UPS, check for TxAmp alarms and perform the fault clearance procedures
related to these alarms.
If the majorGainFailure alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-498 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_majorPlatformSwError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_majorPlatformSwError alarm.
Description
The platform code (USL) which supports the application software has reported a major
error
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
The Radio platform SW detected an error condition that can only be cleared by a
restart of the application software.
System impact
All Calls in the cell supported by this Radio will be dropped.
1 No immediate action is required. Contact Lucent customer support for more in-depth
investigation of this fault.
END OF STEPS
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-499
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_majorTxSpectrumFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_majorTxSpectrumFailure
alarm.
Description
Spectrum management algorithm detected a major failure.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Spectrum management training was required, for one of the following reasons:
• An amplifier module has been detected (initial startup or replacement), for which
training has not been completed.
• The maximum transmission power has been increased.
• The spectrum management coefficients are out of date.
• The transmission frequency has been changed.
Spectrum management failed for one of the following reasons:
• Failure of the sampling receiver circuit of the Radio.
• Failure of the feedback path between the filter panel and the Radio.
System impact
Radio may not satisfy 3GPP spectrum mask.
...................................................................................................................................................................................................................................
15-500 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_majorTxSpectrumFailure
procedures
5 At the Node B, check the feedback cable from the filter unit to the Radio.
...................................................................................................................................................................................................
7 At the OMC-UPS, lock the TxAmp object related to the Radio object.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-501
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_majorTxSpectrumFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-502 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_messageThrottleOn
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_messageThrottleOn alarm.
Description
Message throttling has been activated because too many minor errors are being sent by
the Radio.
Default severity
Critical
Alarm type
qualityofServiceAlarm
Root cause
Resource is at or is nearing its capacity.
System impact
The Radio performs a reset. All calls in this cell are lost.
2 At the OMC-UPS, check for other Radio alarms and perform fault clearance
procedures for the alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-503
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_messageThrottleOn
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-504 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_minorGainFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_minorGainFailure alarm.
Description
Minor gain failure indicating an RF path fault outside of the Radio or a large
instantaneous gain error. Transmit port attenuator has been adjusted beyond allowable
limit to compensate for gain change external to the Radio, or the Radio has detected a
change in loop gain beyond acceptable limits.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
Probable causes are:
• RF path fault outside of the Radio.
• Large instantaneous gain change within the Radio.
System impact
Output power variance is to be expected. The transmit spectrum may break mask.
1 At the OMC-UPS, check for internalGainFailure alarm of the Radio and perform the
fault clearance procedure related to this alarm.
If the minorGainFailure alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-505
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_minorGainFailure
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, check for alarms of the backhaul interface (E1/T1, IubInterface,
IMAGroup) and perform the fault clearance procedure related to these alarms.
If the minorGainFailure alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the OMC-UPS, extract the additional information (CAI) from the additional text of
the alarm:
If... Then...
CAI=0X7: “external gain indicates, that the Radio has identified a gradual
error” gain error external to the Radio greater than a
threshold and has stopped adjusting the attenuators.
Go to step 4.
CAI=0XB: “large indicates, that the Radio has identified a sudden
instantaneous gain error – change of gain internal to the Radio and has
internal stopped adjusting the attenuators. Go to step 7.
fault”
CAI=0XC: “large indicates, that the Radio has identified a sudden
instantaneous gain error – change of gain external to the Radio and has
external stopped adjusting the attenuators. Go to step 12
fault”
CAI=0XD: “large indicates, that the Radio has identified a sudden
instantaneous gain error – change of gain due to an unknown fault. First run
unknown the fault clearance procedures for the “large
fault” instantaneous gain error – external fault” and if the
problem still persists, the fault clearance procedure
for the “large instantaneous gain error – internal
fault”.
...................................................................................................................................................................................................
4 At the OMC-UPS, check for TxAmp alarms and perform the fault clearance procedures
related to these alarms.
If the minorGainFailure alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
5 In case of NodeB installation and first startup: At the NodeB, perform a recalibration
of the RF-path related to the Radio
If the minorGainFailure alarm is cleared, the procedure is completed.
....................................................................................................................................................................................................................................
15-506 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_minorGainFailure
procedures
...................................................................................................................................................................................................
12 At the OMC-UPS, check for TxAmp alarms and perform the fault clearance procedures
related to these alarms.
If the minorGainFailure alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-507
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_missingConfigurationData
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_missingConfigurationData
alarm.
Description
The configuration conflicts with local configuration data..
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Missing or faulty local configuration data.
System impact
No service available
1 At the Node B, check for configurationMismatch alarm and perform fault clearance
procedure for that alarm..
If the alarm is cleared together with the configurationMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 At the OMC-UPS, check and update local configuration data via remote RMT.
...................................................................................................................................................................................................................................
15-508 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_missingConfigurationData
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-509
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_missingDelayCalibrationData
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_missingDelayCalibrationData
alarm.
Description
Delay calibration data needed for round trip time measurement is missing.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
Delay calibration data is missing in the backplane, filter panel, or Radio.
System impact
Round trip time measurement not available towards the RNC. Location services
accuracy degraded. Normal call processing is not affected.
1 At the Node B, check backplane and filter panel EEPROM data via RMT and correct
as appropriate.
...................................................................................................................................................................................................................................
15-510 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_missingDelayCalibrationData
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-511
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_overTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_overTemperature alarm.
Description
The Radio temperature sensor detected a temperature above the specifications limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
High temperature.
System impact
All calls are dropped immediately. Call processing on the cell is blocked, so no new
calls are accepted.
1 At the OMC-UPS, check for Frame, AmpShelfFan and DigitalShelfFan alarms related
to heat management system or fan problems, and perform the fault clearance procedure
for these alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-512 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_overTemperature
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, reset the Radio object, if the overTemperature alarm has been
reported several times and so the Radio has been isolated. If the alarm has been
cleared and is not reported again, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-513
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_portMapInvalid
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_portMapInvalid alarm.
Description
The Radio port map contained in the backplane’s EEPROM is invalid.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
The port map contained in the backplane EEPROM is invalid.
System impact
The Radio cannot be configured properly. The Cell that is supported by this Radio
cannot be used.
1 At the OMC-UPS, use the remote RMT to make sure that the backplane EEPROM
data is OK.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
15-514 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_portMapInvalid
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-515
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_rFOverdrive
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_rFOverdrive alarm.
Description
The UMTS Channel Unit (UCU) is driving the Radio with a too strong digital signal.
As a result there will be RF clipping and Bit Error Rates.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Excessive input power.
Probable causes are:
• Configuration error
• Failure on Radio
System impact
Cell is degraded and calls may drop.
1 Check the (RF power) configuration of the Radio and correct if necessary.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-516 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_rFOverdrive
procedures
...................................................................................................................................................................................................
7 If the problem persists, request Alcatel-Lucent customer support to check why the
Radio is operating at a higher than normal power level.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-517
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_rFPathMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_rFPathMismatch alarm.
Description
The hardware of the RF-path does not fit together.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Provisioning of inconsistent hardware:
• The combination of TTLNA and DAS equipment is not supported.
• The combination of Radio and Amplifier board is not supported.
• Filter, Radio and Amplifier boards do not support the same band class.
• The supported frequency range does not fit into a known frequency band.
System impact
No traffic possible on associated cell.
1 At the OMC-UPS, extract detailed information about the mismatch from the
additionalText of the alarm.
...................................................................................................................................................................................................................................
15-518 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_rFPathMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-519
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_resyncOfPulse
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_resyncOfPulse alarm.
Description
Resyncronization of 10 millisecond pulse occurred. Radio lost UL and DL data for a
short time.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
No impact on service.
...................................................................................................................................................................................................................................
15-520 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_resyncOfPulse
procedures
If... Then...
This alarm is reported repeatedly Go to step 2.
for more than one Radio,
Otherwise, Go to step 5.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-521
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_resyncOfPulse
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-522 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_rx1PathFaultDetected
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_rx1PathFaultDetected.
Description
This alarm indicates a hardware failure in the first Rx Path chain.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
Dysfunction of the first Rx path is to be expected.
1 At the Node B, ensure that the first receive path (antenna, RF cable, filter unit, radio
and cabling) is working properly.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-523
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_rx1PathFaultDetected
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-524 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_rx2PathFaultDetected
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_rx2PathFaultDetected.
Description
This alarm indicates a hardware failure of the second Rx Path chain.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
Dysfunction of the second Rx path is to be expected.
1 At the Node B, ensure that the second receive path (antenna, RF cable, filter unit,
radio and cabling) is working properly.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-525
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_rx2PathFaultDetected
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-526 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_samplingReceiverFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_samplingReceiverFailure
alarm.
Description
Radio software failed to read data from the sampling receiver circuit.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Hardware failure.
System impact
No impact on service. Spectrum management will be impacted when a measurement is
required.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-527
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_samplingReceiverFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-528 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_selfTestFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_selfTestFailure alarm.
Description
The Radio failed the Board Level Self Test (BLST).
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The Radio cannot be initiated to service. No calls in this cell are possible.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-529
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_selfTestFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-530 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_synthesizerFailure122Mhz
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_synthesizerFailure122Mhz
alarm.
Description
The 122 Mhz synthesizer failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
The Radio is reset and reinitialized autonomously.
2 At the Node B, make sure that the cabling on the Oscillator Module and CTU is OK.
...................................................................................................................................................................................................
4 At the OMC-UPS, check for and clear any Oscillator Module or CTU alarms.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-532 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_synthesizerFailure15Mhz
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_synthesizerFailure15Mhz
alarm.
Description
The 15 MHz synthesizer failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
All calls in this cell are dropped.
2 At the Node B, make sure that the cabling on the Oscillator Module and CTU is OK.
...................................................................................................................................................................................................
4 At the OMC-UPS, check for and clear any Oscillator Module and CTU alarms.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-534 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_tDUCommunicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_tDUCommunicationFailure
alarm.
Description
The Radio is unable to reach the Test and Diagnostic Unit (TDU).
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The Radio will reduce its transmit power. Call capacity in the cell is reduced.
1 At the OMC-UPS, check for other Radio objects also reporting this error.
If... Then...
More Radio objects reporting this Go to step 2.
error,
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-535
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_tDUCommunicationFailure
procedures
If... Then...
Only this Radio object reporting Go to step 6.
this error,
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-536 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_toneGeneratorFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_toneGeneratorFailure alarm.
Description
The onboard tone generator circuit has failed during execution of an Rx antenna test.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
Hardware failure.
System impact
No impact on service. Result of Rx antenna test is invalid, further Rx antenna tests are
rejected
2 At the OMC-UPS, reset the Radio object to initialize the Radio and clear the alarm.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-537
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_toneGeneratorFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-538 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
Radio_transmitGainLimitExceeded
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_transmitGainLimitExceeded
alarm.
Description
The transmit close loop gain control is out of range.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Probable causes are:
• Transmitter failure
• TDU power detector failure
• Cabling problem.
System impact
Call capacity in the cell served by this Radio is reduced.
1 If... Then...
This alarm is reported by one Go to step 2.
Radio,
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-539
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance Radio_transmitGainLimitExceeded
procedures
If... Then...
This alarm is reported by more Go to step 9.
Radios,
...................................................................................................................................................................................................
2 At the Node B, make sure that the cabling between the Radio, transmit power
amplifier, filter and the TDU is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-540 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_transmitGainLimitExceeded
procedures
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-541
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_transmitterSwitchFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_transmitterSwitchFailure
alarm.
Description
The activation/deactivation of the radio transmitter has failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
All calls in this cell are lost.
1 At the OMC-UPS, wait until the Radio reinitialization has been completed.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-543
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_transmitterSwitchOff
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_transmitterSwitchOff alarm.
Description
This alarm indicates that the Radio associated with this cell is currently turned off. The
switch on the front panel of the radio circuit pack is set off.
Default severity
Warning
Alarm type
equipmentAlarm
Root cause
Transmitter failure.
System impact
This is not really an indication of a problem but a status report. All calls in this cell
are lost.
1 At the Node B, turn the Tx front panel switch on the Radio to the On position.
...................................................................................................................................................................................................................................
15-544 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_transmitterSwitchOff
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-545
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_txActivationMalfunction
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_txActivationMalfunction
alarm.
Description
The Radio does not have its transmitter turned on, or can not activate its transmitter.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Radio transmitter switched off due to hardware or software problems.
System impact
The cell served by this Radio is not operational. No traffic in this cell is possible.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-547
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
Radio_underTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Radio_underTemperature alarm.
Description
The Radio temperature sensor detected a temperature below the specifications limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Low temperature.
System impact
All calls are dropped immediately. Call processing on the cell is blocked, so no new
calls are accepted.
1 At the OMC-UPS, check for Frame, AmpShelfFan and DigitalShelfFan alarms related
to heat management system or fan problems, and perform the fault clearance procedure
for these alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-548 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance Radio_underTemperature
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, reset the Radio object, if the underTemperature alarm has been
reported several times and so the Radio has been isolated. If the alarm has been
cleared and is not reported again, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-549
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
RxAmp alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the LNA.
Contents
RxAmp_equipmentFault 15-551
RxAmp_initialisationFailure 15-553
...................................................................................................................................................................................................................................
15-550 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RxAmp_equipmentFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RxAmp_equipmentFault alarm.
Description
One LNA in a filter panel failed. As a result the radio functionality will be impaired,
but still be present.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The system will be impacted as indicated below:
• Affected cells are degraded if the alarm is pending and the operational state of the
RxAmp MO is disabled.
• If this was the only RxAmplifier or the last RxAmplifier which served the cell, the
cell is disabled.
• In case of a intermittent fault condition, the alarm is only cleared if the fault did
not occur again within 3 hours.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-551
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance RxAmp_equipmentFault
procedures
...................................................................................................................................................................................................
2 At the Node B, replace the filter unit of the RxAmplifier (the LNA is part of the filter
unit).
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-552 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
RxAmp_initialisationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the RxAmp_initialisationFailure alarm.
Description
The RxAmp has failed to initialize.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The filter can not be initiated to service. The call capacity on this cell is decreased. If
no filter unit associated with this cell can be initiated to service, call processing on this
cell is blocked.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-553
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance RxAmp_initialisationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-554 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the STM1OC3Port alarms.
Contents
STM1OC3Port_linkFailureAIS_L 15-556
STM1OC3Port_linkFailureAIS_P 15-558
STM1OC3Port_linkFailureLOF 15-560
STM1OC3Port_linkFailureLOP_P 15-562
STM1OC3Port_linkFailureLOS 15-564
STM1OC3Port_linkFailurePLM_P 15-566
STM1OC3Port_linkFailureRDI_L 15-568
STM1OC3Port_linkFailureRDI_P 15-570
STM1OC3Port_linkFailureSLU_P 15-572
STM1OC3port_localConfigurationFailure 15-574
STM1OC3Port_pathTraceMismatch 15-576
STM1OC3Port_signalDegraded_L 15-578
STM1OC3Port_signalDegraded_P 15-580
STM1OC3Port_signalFailed_L 15-582
STM1OC3Port_signalFailed_P 15-584
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-555
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_linkFailureAIS_L
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_linkFailureAIS_L
alarm.
Description
An Alarm Indication Signal Line (AIS-L) failure has occured on the ATM
(STM1/OC3) link connection
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Transmission problem in the upstream link (for example, loss of frame, loss of signal,
etc).
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-557
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_linkFailureAIS_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_linkFailureAIS_P
alarm.
Description
An Alarm Indication Signal Path (AIS-P) failure has occured on the ATM (STM1/OC3)
link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Transmission problem upstream of the STM-1/OC-3 path.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-558 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_linkFailureAIS_P
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-559
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_linkFailureLOF
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_linkFailureLOF
alarm.
Description
A Loss of Frame (LOF) failure has occured on the ATM (STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
STM1/OC3 line is not synchronised to the transmission link. Framing of the
STM1/OC3 signal is corrupt
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-560 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_linkFailureLOF
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-561
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_linkFailureLOP_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_linkFailureLOP_P
alarm.
Description
A Loss of Pointer Path (LOP-P) failure has occured on the ATM (STM1/OC3) link
connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Pointer information missing or wrong.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-562 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_linkFailureLOP_P
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-563
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_linkFailureLOS
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_linkFailureLOS
alarm.
Description
A Loss of Signal (LOS) failure has occured on the ATM (STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Loss of signal due to link interruption or equipment malfunction.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-564 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_linkFailureLOS
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-565
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_linkFailurePLM_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_linkFailurePLM_P
alarm.
Description
A Payload Label Mismatch Path (PLM-P) failure has occured on the ATM
(STM1/OC3) link connection
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Payload label of a path is corrupted.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-566 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_linkFailurePLM_P
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-567
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_linkFailureRDI_L
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_linkFailureRDI_L
alarm.
Description
A Remote Defect Indication Line (RDI-L) failure has occured on the ATM
(STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Link problem at the remote end of the STM1/OC3 line..
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-568 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_linkFailureRDI_L
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-569
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_linkFailureRDI_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_linkFailureRDI_P
alarm.
Description
A Remote Defect Indication Path (RDI-P) failure has occured on the ATM
(STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Link problem at the remote end of the STM1/OC3 path..
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-570 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_linkFailureRDI_P
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-571
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_linkFailureSLU_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_linkFailureSLU_P
alarm.
Description
The received STM1/OC3 signal label is set to unequipped. Most likely the signal label
has been corrupted or not properly set at the source or in the upstream transmission
equipment.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Signal label corrupted or not properly set at the source or in the upstream transmission
equipment.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-572 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_linkFailureSLU_P
procedures
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-573
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3port_localConfigurationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
STM1OC3port_localConfigurationFailure alarm.
Description
The configuration conflicts with local configuration data.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Missing or faulty local configuration data.
System impact
The STM/OC3 link is not available.
1 At the Node B, use the RMT tool to check the Trunk Group Member parameters
Configure the parameters if required.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-574 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3port_localConfigurationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-575
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_pathTraceMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_pathTraceMismatch
alarm.
Description
There is a mismatch between the received J1 path trace and the expected J1 sequence.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
J1 path trace mismatch in case of wrong end-to-end network configuration or cabling.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-576 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_pathTraceMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-577
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_signalDegraded_L
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_signalDegraded_L
alarm.
Description
The STM1/OC3 signal on the line is degraded due to bit error rate greater than 1 per
million.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Poor link quality on the STM1/OC3 line..
System impact
Communication to the RNC may be affected..
...................................................................................................................................................................................................................................
15-578 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_signalDegraded_L
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-579
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_signalDegraded_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_signalDegraded_P
alarm.
Description
The STM1/OC3 signal on the line is degraded due to bit error rate greater than 1 per
million.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Poor link quality on the STM1/OC3 path..
System impact
Communication to the RNC may be affected..
...................................................................................................................................................................................................................................
15-580 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_signalDegraded_P
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-581
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_signalFailed_L
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_signalFailed_L
alarm.
Description
The STM1/OC3 signal on the line has failed due to bit error rate greater than 1 per
thousand.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Poor link quality on the STM1/OC3 line.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-582 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_signalFailed_L
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-583
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
STM1OC3Port_signalFailed_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the STM1OC3Port_signalFailed_P
alarm.
Description
The STM1/OC3 signal on the path has failed due to bit error rate greater than 1 per
thousand.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Poor link quality on the STM1/OC3 path.
System impact
Communication to the RNC is affected.
In case of a severe fault condition the operational state is set to disabled and the line is
taken out of service.
It may take several minutes to clear the alarm, after the fault condition has been
cleared.
...................................................................................................................................................................................................................................
15-584 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance STM1OC3Port_signalFailed_P
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-585
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
TDU alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Test and Diagnostic Unit
(TDU).
Contents
TDU_applicationInsane 15-587
TDU_boardGenericMismatch 15-589
TDU_communicationFailure 15-591
TDU_configurationMismatch 15-593
TDU_criticalVoltageFailure 15-595
TDU_filterPanelRecordInvalid 15-597
TDU_frequencySynthesizerFailure 15-599
TDU_heaterFailure 15-601
TDU_hwErrorDetectedByPlatformSw 15-603
TDU_initialisationFailure 15-605
TDU_localConfigurationFailure 15-607
TDU_lossOfPulse 15-609
TDU_majorPlatformSwError 15-612
TDU_messageThrottleOn 15-614
TDU_portMapInvalid 15-616
TDU_selfTestFailure 15-618
TDU_temperatureOutOfRange 15-620
TDU_tssiDetectorFailure 15-622
...................................................................................................................................................................................................................................
15-586 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_applicationInsane
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_applicationInsane alarm.
Description
The application software executing on the Test and Diagnostic Unit (TDU) is not
functioning properly.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Software program error.
System impact
The system impact will be:
• Reduction of radio power and traffic capacity.
• Unavailability of RF Antenna tests.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-587
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TDU_applicationInsane
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-588 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_boardGenericMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_boardGenericMismatch alarm.
Description
The software version on the Test and Diagnostic Unit (TDU) does not match with the
current version stored on the URC, because a software download failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
The software on the TDU could not be updated, because the download from the URC
to the TDU failed.
System impact
The TDU can not be initiated to service. No RF antenna tests and diagnostic functions
are available.
2 At the OMC-UPS, reset the TDU object to update the software on the TDU.
If the alarm is cleared, the procedure is completed
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-589
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TDU_boardGenericMismatch
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, check the state of the current NodeB software version via RMT. If
the state is not GOOD, reset the NodeB object.
If the alarm is cleared, the procedure is completed.
Result: The NodeB automatically downloads missing/corrupted software files from
the FTP server (OMC) and updates the software on the TDU.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-590 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_communicationFailure alarm.
Description
Heartbeat synchronization between the Test and Diagnostic Unit (TDU) and the
Universal Radio Controller (URC) has been lost or timeout occured during
initialization of the TDU.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Possible root causes are:
• Equipment failure
• Timing problem.
• Missing or pulled board.
• Backplane EEPROM not accessible
System impact
The system impact will be:
• Reduction of radio power and traffic capacity.
• Unavailability of RF Antenna tests.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-591
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TDU_communicationFailure
procedures
1 At the OMC-UPS, wait until the TDU reinitialization is completed. If the alarm is not
cleared within 5 minutes, the initialization has failed.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the Node B, make sure that the TDU is mounted properly in the frame.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-592 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_configurationMismatch alarm.
Description
The configuration conflicts with attribute value(s) of other object(s).
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No service available
1 At the Node B, check for nodeBTypeMismatch alarm of the NodeB object and perform
the fault clearance procedure for that alarm.
If this alarm is cleared together with the nodeBTypeMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-593
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TDU_configurationMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-594 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_criticalVoltageFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_criticalVoltageFailure alarm.
Description
This error condition effects an internally generated DC voltage. The Test and
Diagnostic Unit (TDU) can detect the voltage of the 9.1V converter and raises an
alarm if it is too low or high. There is also a 3.3V converter in series with the 9.1V
converter so if the voltage drops too much, then the system will lose the 3.3V
converter.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
The voltage regulator on the TDU is broken.
System impact
The call capacity of the Node B is reduced.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-596 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_filterPanelRecordInvalid
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_filterPanelRecordInvalid alarm.
Description
One or all filter panel records used for TDU’s configuration are invalid.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Probable causes are:
• Port map might not match filter panel configuration.
• Filter panel might be not connected.
• Local filter panel EEPROM data corrupt.
System impact
TDU cannot be configured properly. The Node B’s Radios will reduce their power, i.e.
the overall traffic capacity is reduced.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-597
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TDU_filterPanelRecordInvalid
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, use the remote RMT to make sure that the backplane EEPROM
data is OK.
...................................................................................................................................................................................................
5 At the Node B, make sure that all filter panels are mounted correctly.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-598 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_frequencySynthesizerFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_frequencySynthesizerFailure
alarm.
Description
The Test and Diagnostic Unit (TDU) cannot perform an RF measurement.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
The system impact will be:
• Reduction of radio power and traffic capacity.
• Unavailability of RF Antenna tests.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-599
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TDU_frequencySynthesizerFailure
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, check for clock alarms of the CTU and OM and perform fault
clearance procedures for the alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-600 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_heaterFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_heaterFailure alarm.
Description
The TDU’s own heater failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Hardware failure on TDU.
System impact
The TDU is unable to deliver correct measurements. The Node B’s Radios will reduce
their power. As a result of this power reduction the overall traffic capacity is reduced.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-602 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_hwErrorDetectedByPlatformSw
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_hwErrorDetectedByPlatformSw
alarm.
Description
The platform code (USL) that supports the application software has detected a
potentially unrecoverable hardware fault.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Hardware failure.
System impact
The Node B’s Radios will reduce their power. As a result of the power reduction the
overall traffic capacity is reduced.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-603
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TDU_hwErrorDetectedByPlatformSw
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-604 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_initialisationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_initialisationFailure alarm.
Description
The Test and Diagnostic Unit (TDU) failed to initialize.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The system impact will be:
• Reduction of radio power and traffic capacity.
• Unavailability of RF Antenna tests.
1 At the Node B, make sure that the TDU is mounted correctly in the frame.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-605
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TDU_initialisationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-606 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_localConfigurationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_localConfigurationFailure
alarm.
Description
The configuration conflicts with local configuration data.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Missing or faulty local configuration data.
System impact
No service available
1 At the Node B, check for configurationMismatch alarm and perform fault clearance
procedure for that alarm..
If the alarm is cleared together with the configurationMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 At the OMC-UPS, check and update local configuration data via remote RMT.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-607
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TDU_localConfigurationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-608 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TDU_lossOfPulse
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_lossOfPulse alarm.
Description
The Test and Diagnostic Unit (TDU) failed to detect the 10 millisecond pulse.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Probable root causes are:
• Hardware failure
• Timing problem.
System impact
The system impact will be:
• Reduction of radio power and traffic capacity.
• Unavailability of RF Antenna tests.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-609
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TDU_lossOfPulse
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, check for clock alarms of the CTU and OM and perform fault
clearance procedures for the alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the Node B, make sure that the clock cable between the CTU and the TDU is
properly connected.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-610 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance TDU_lossOfPulse
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-611
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
TDU_majorPlatformSwError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_majorPlatformSwError alarm.
Description
The platform code (USL) which supports the application software has reported a major
error.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
The boards platform SW detected an error condition which can only be cleared by an
restart of the application software.
System impact
The Radios will reduce their power, i.e. the overall traffic capacity is reduced.
...................................................................................................................................................................................................................................
15-612 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance TDU_majorPlatformSwError
procedures
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support for more in-depth investigation of this fault.
END OF STEPS
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-613
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
TDU_messageThrottleOn
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_messageThrottleOn alarm.
Description
The Test and Diagnostic Unit (TDU) reports too many errors to the RCS.
Default severity
Critical
Alarm type
qualityofServiceAlarm
Root cause
System resources overload.
System impact
If too many errors occur in a given time frame, then the TDU will be reset and
reinitialized.
The system impact will be:
• Reduction of radio power and traffic capacity.
• Unavailability of RF Antenna tests.
...................................................................................................................................................................................................................................
15-614 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance TDU_messageThrottleOn
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, check for other TDU alarms and perform fault clearance procedures
for the alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-615
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
TDU_portMapInvalid
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_portMapInvalid alarm.
Description
The Test and Diagnostic Unit (TDU) port map contained in the backplane’s EEPROM
is invalid.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
The port map contained in the backplane EEPROM is invalid.
System impact
TDU cannot be configured properly. The Radios will reduce their power, i.e. the
overall traffic capacity is reduced.
1 At the OMC-UPS, use the remote RMT to make sure that the backplane EEPROM
data is OK.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
15-616 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance TDU_portMapInvalid
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-617
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
TDU_selfTestFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_selfTestFailure alarm.
Description
The Test and Diagnostic Unit (TDU) has failed the Board Level Self Test (BLST).
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The system impact will be:
• Reduction of radio power and traffic capacity.
• Unavailability of RF Antenna tests.
1 At the Node B, make sure that the TDU is mounted correctly in the frame.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
15-618 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance TDU_selfTestFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-619
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
TDU_temperatureOutOfRange
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_temperatureOutOfRange alarm.
Description
The TDU temperature sensor has detected a temperature above its design threshold.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible root causes are:
• Heat management failure
• Fan failure.
System impact
Measurement results might be incorrect.
1 At the OMC-UPS, check for Frame, AmpShelfFan and DigitalShelfFan alarms related
to heat management system or fan problems, and perform the fault clearance procedure
for these alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-620 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance TDU_temperatureOutOfRange
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, reset the TDU object, if the overTemperature alarm has been
reported several times and so the TDU has been isolated.
the alarm has been cleared and is not reported again, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-621
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
TDU_tssiDetectorFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TDU_tssiDetectorFailure alarm.
Description
The Transmit Signal Strength Indicator (TSSI) detector reading is below the maximum
quiet level.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
The TSSI detector circuitry on the TDU is broken.
System impact
The Call capacity of the Node B is reduced.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-623
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
TxAmp alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the amplifier module.
Contents
TxAmp_amplifierSwitchFailure 15-625
TxAmp_communicationFailure 15-627
TxAmp_configurationMismatch 15-629
TxAmp_equipmentFault 15-631
TxAmp_externalAmplifierFailure 15-633
TxAmp_hardwareModelMismatch 15-635
TxAmp_incompletePredistortionCoefficients 15-637
TxAmp_initialisationFailure 15-639
TxAmp_localConfigurationFailure 15-641
TxAmp_messageThrottleOn 15-643
TxAmp_missingPredistortionCoefficients 15-645
TxAmp_overTemperature 15-647
TxAmp_rFOverdrive 15-649
TxAmp_selfTestFailure 15-651
TxAmp_severeExternalAmplifierFailure 15-653
TxAmp_underTemperature 15-655
TxAmp_warmupFailure 15-657
...................................................................................................................................................................................................................................
15-624 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_amplifierSwitchFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_amplifierSwitchFailure
alarm.
Description
The activation/deactivation of the amplifier has failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
All calls in this cell are lost.
1 At the OMC-UPS, wait until the Amplifier module reinitialization has been completed.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-626 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_communicationFailure
alarm.
Description
Heartbeat synchronisation between the TxAmp and the URC has been lost or timeout
occured during initialisation of the TxAmp.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Possible root causes are:
• Equipment failure
• Timing problem.
• Missing or pulled board.
System impact
All calls in the cell are lost, when a TxAmp fails and performs a reset or when a
TxAmp cannot be initialized to service.
1 At the OMC-UPS, wait until the amplifier module reinitialization is completed. If the
alarm is not cleared within 5 minutes, the initialisation has failed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-627
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_communicationFailure
procedures
2 At the OMC-UPS, check for other TxAmp alarms and perform fault clearance
procedure for the alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the Node B, make sure that the amplifier module is mounted firmly in the shelf and
that the cabling is OK.
...................................................................................................................................................................................................
4 At the OMC-UPS, reset the TxAmp object to initialize the amplifier module.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-628 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_configurationMismatch
alarm.
Description
The configuration conflicts with attribute value(s) of other object(s).
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No service available
1 At the Node B, check for nodeBTypeMismatch alarm of the NodeB object and perform
the fault clearance procedure for that alarm.
If this alarm is cleared together with the nodeBTypeMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-629
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_configurationMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-630 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_equipmentFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_equipmentFault alarm.
Description
The amplifier module has detected an equipment failure.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
All calls in the cell are lost, when a TxAmp fails and performs a reset or when a
TxAmp cannot be initialized to service.
....................................................................................................................................................................................................................................
15-632 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_externalAmplifierFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_externalAmplifierFailure
alarm.
Description
A minor failure of the external amplifier (MCPA or RFoF) has been reported via an
external alarm.
This alarm is raised, if an external amplifier raises an alarm via the external alarm box
of the IOU, where the externalAlarms attribute has been configured as follows for the
specific port: ″specificProblem″ equal to ″failureOnMCPA<i> or
“failureOnExtAmplifier<i>”
Note: i is the instance of the TxAmp object modelling the MCPA or RFoF); ″severity″
equal to major or critical.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
Call-processing is blocked and so all calls in this cell are dropped.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-633
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_externalAmplifierFailure
procedures
1 At the Node B, make sure that the external amplifier is working properly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-634 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_hardwareModelMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_hardwareModelMismatch
alarm.
Description
The detected hardware model does not match the value specified.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No impact on service.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-635
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_hardwareModelMismatch
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, update the expected hardware model attribute to match the detected
hardware model attribute.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-636 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_incompletePredistortionCoefficients
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_incompletePredistortion-
Coefficients alarm.
Description
The predistortion coefficients stored in the amplifier module are incomplete and do not
support the requested maximum cell power.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Probable causes are:
• Missing predistortion data in the EEPROM of amplifier module for the requested
maximum cell power.
• The configured power for the cell is higher than the transmit power amplifier is
calibrated for.
System impact
The system impacts are:
• The Radio cannot be configured properly.
• The cell supported by this Radio cannot be brought to service.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-637
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_incompletePredistortionCoefficients
procedures
If... then...
the attribute values are not go to step 2.
correct,
the attribute values are correct, go to step 4.
...................................................................................................................................................................................................
3 At the OMC-UPS, re-create (add) the UtranCell with the correct attributes.
If the alarm is cleared the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-638 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_initialisationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_initialisationFailure alarm.
Description
The amplifier module failed to initialize.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
The amplifier module cannot be initialized to service. All calls in the cell are lost,
when a TxAmp fails and performs a reset or when a TxAmp cannot be initialized to
service.
1 At the Node B, make sure that the amplifier module is mounted correctly in the frame.
...................................................................................................................................................................................................
2 At the OMC-UPS, reset the TxAmp object to initialize the amplifier module.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-639
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_initialisationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-640 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_localConfigurationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_localConfigurationFailure
alarm.
Description
The configuration conflicts with local configuration data.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Missing or faulty local configuration data.
System impact
No service available
1 At the Node B, check for configurationMismatch alarm and perform fault clearance
procedure for that alarm..
If the alarm is cleared together with the configurationMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 At the OMC-UPS, check and update local configuration data via remote RMT.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-641
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_localConfigurationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-642 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_messageThrottleOn
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_messageThrottleOn alarm.
Description
Message throttling has been activated because too many errors are being sent by the
amplifier module.
Default severity
Warning
Alarm type
qualityofServiceAlarm
Root cause
System resources at or nearing capacity overload.
System impact
All calls in the cell are lost, when a TxAmp fails and performs a reset or when a
TxAmp cannot be initialized to service.
1 At the OMC-UPS, check for other TxAmp alarms and perform fault clearance
procedures for the alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-643
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_messageThrottleOn
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-644 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_missingPredistortionCoefficients
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_missingPredistortionCo-
efficients alarm.
Description
The predistortion coefficient record can not be read from the transmit power amplifier.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Probable causes are:
• No predistortion training is performed after replacing amplifier module or Radio
hardware failure
• Amplifier module predistortion coefficients are missing or corrupted.
System impact
The system impacts are:
• Reduced transmit power on the cell
• Reduced traffic capacity on the cell.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-645
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_missingPredistortionCoefficients
procedures
At the Node B, perform the “Amplifier predistortion training” procedure to make sure
that the amplifier module predistortion coefficients are correct.
Result: Refer to the Lucent UMTS Node B Operations, Administration and
Maintenance manual for more information about the “Amplifier predistortion
training” procedure.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-646 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_overTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_overTemperature alarm.
Description
The amplifier module temperature sensor detected a temperature above the specified
limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Temperature is unacceptable.
System impact
Call processing is blocked on the cell. The amplifier module is shut down (no RF
output) and all calls are lost.
3 At the Node B, make sure that the system is operating within its operational
temperature.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the OMC-UPS, reset the TxAmp object, if the overTemperature alarm has been
reported several times and so the amplifier module has been isolated.
If the alarm has been cleared and is not reported again, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-648 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_rFOverdrive
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_rFOverdrive alarm.
Description
The amplifier module has detected an RF overdrive condition.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Excessive transmitter output power
• Incorrect Radio calibration
• Radio hardware failure.
System impact
The input signal will be limited to prevent damage.
In case of a intermittent fault condition, the alarm is only cleared if the fault did not
occur again within 30 minutes.
1 At the OMC-UPS, check for Radio alarms and perform fault clearance procedure for
the alarms.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-649
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_rFOverdrive
procedures
....................................................................................................................................................................................................................................
15-650 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_selfTestFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_selfTestFailure alarm.
Description
The amplifier module has failed the Board Level Self Test (BLST).
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
All calls in the cell are lost, when a TxAmp fails and performs a reset or when a
TxAmp cannot be initialized to service.
1 At the Node B, make sure that the amplifier module is mounted correctly in the frame.
...................................................................................................................................................................................................
2 At the OMC-UPS, reset the TxAmp object to initialize the amplifier module.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-652 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_severeExternalAmplifierFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_severeExternalAmplifier-
Failure alarm.
Description
A critical failure of the external amplifier (MCPA or RFoF) has been reported via an
external alarm.
This alarm is raised, if an external amplifier raises an alarm via the external alarm box
of the IOU, where the externalAlarms attribute has been configured as follows for the
specific port: ″specificProblem″ equal to ″failureOnMCPA<i> or
“failureOnExtAmplifier<i>”
Note: i is the instance of the TxAmp object modelling the MCPA or RFoF); ″severity″
equal to major or critical.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
Call-processing is blocked and so all calls in this cell are dropped.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-653
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_severeExternalAmplifierFailure
procedures
1 At the Node B, make sure that the external amplifier is working properly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-654 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_underTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_underTemperature alarm.
Description
The amplifier module is operating below its normal operating temperature (warm-up).
Default severity
Warning
Alarm type
environmentalAlarm
Root cause
Amplifier module has not reach proper operating temperature. The amplifier module
has not warmed up sufficiently after DC power is first supplied. The amplifier module
can take up to 15 minutes to warm up.
System impact
Call processing is blocked on the cell.
2 At the OMC-UPS, check for heat management alarms and perform fault clearance
procedures for the alarms.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-655
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_underTemperature
procedures
....................................................................................................................................................................................................................................
15-656 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
TxAmp_warmupFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the TxAmp_warmupFailure alarm.
Description
The amplifier module failed to warm up within 15 minutes.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment malfunction.
System impact
All calls in the cell are lost, when a TxAmp fails and performs a reset or when a
TxAmp cannot be initialized to service.
If... Then...
This is the only TxAmp object Go to step 2.
that is affected,
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-657
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance TxAmp_warmupFailure
procedures
If... Then...
There are more TxAmp objects Go to step 7.
affected,
...................................................................................................................................................................................................
8 At the Node B, make sure that the environment conditions are OK.
...................................................................................................................................................................................................
9 At the OMC-UPS, reset the TxAmp object to initialize the amplifier module.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-658 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
UCU alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the UTRA Channel Unit
(UCU).
Contents
UCU_applicationInsane 15-660
UCU_clockFailure30_72Mhz 15-662
UCU_combinerToASICBusFailure 15-664
UCU_communicationFailure 15-666
UCU_configurationMismatch 15-668
UCU_criticalChannelElementFailure 15-670
UCU_criticalChannelElementSystemResourceFailure 15-672
UCU_excessiveDownlinkParityErrors 15-674
UCU_excessiveUplinkParityErrors 15-676
UCU_fPGAFailure 15-678
UCU_hwErrorDetectedByPlatformSw 15-681
UCU_initialisationFailure 15-683
UCU_lossOfForwardBusLink 15-685
UCU_majorChannelElementSystemResourceFailure 15-687
UCU_majorPlatformSwError 15-689
UCU_selfTestFailure 15-691
UCU_voltageOutOfRange 15-693
UCU_watchdogInitiatedReset 15-695
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-659
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
UCU_applicationInsane
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_applicationInsane alarm.
Description
The UCU application software is not functioning properly.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Software program error.
System impact
No call processing on this UCU is possible. The system capacity is temporarily
degraded.
...................................................................................................................................................................................................................................
15-660 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance UCU_applicationInsane
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-661
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
UCU_clockFailure30_72Mhz
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_clockFailure30_72Mhz alarm.
Description
The 30.72 MHz clock signal from the CTU has failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
No call processing on this UCU is possible. The system capacity is degraded.
...................................................................................................................................................................................................................................
15-662 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance UCU_clockFailure30_72Mhz
procedures
...................................................................................................................................................................................................
6 At the OMC-UPS, make sure that the clock distribution within the Node B is OK.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-663
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
UCU_combinerToASICBusFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_combinerToASICBusFailure
alarm.
Description
UCU has detected a high parity error rate on the internal ASIC to the combiner bus.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
All channels of the UCU are not available. No call processing on this UCU is possible.
The system capacity is degraded.
2 At the OMC-UPS, make sure that the clock and power supply of the UCU are OK.
...................................................................................................................................................................................................................................
15-664 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance UCU_combinerToASICBusFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-665
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
UCU_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_communicationFailure alarm.
Description
Heartbeat synchronization between the UTRA Channel Unit (UCU) and the Universal
Radio Controller (URC) has been lost or timeout occured during initialisation of the
UCU.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Possible root causes are:
• Equipment failure
• Timing problem.
• Missing or pulled board.
System impact
Call processing on this UCU is interrupted. The system capacity is degraded.
1 At the OMC-UPS, wait until the UCU reinitialization is completed. If the alarm is not
cleared within 5 minutes, the initialisation has failed.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-666 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance UCU_communicationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-667
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
UCU_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_configurationMismatch alarm.
Description
UCU mixed configuration (UCU-II and UCU-III) is not supported.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
UCU mixed configuration
System impact
No service available
2 At the OMC-UPS, lock the UCU object(s) which should not provide service.
...................................................................................................................................................................................................
3 At the OMC-UPS, reset the alarmed UCU object to bring this UCU back to service.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
15-668 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance UCU_configurationMismatch
procedures
...................................................................................................................................................................................................
4 Check, if the UCU needs to be replaced by a UCU of the other type or if the UCU
needs to be removed. In case of replacement
In case of replacement goto Step 5, otherwise goto Step 9.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-669
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
UCU_criticalChannelElementFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_criticalChannelElementFailure
alarm.
Description
A critical channel element failure has occured.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Critical equipment failure of one or more channel elements.
System impact
No call processing on this UCU is possible. The system capacity is degraded.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-671
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
UCU_criticalChannelElementSystemResourceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_criticalChannelElementSys-
temResourceFailure alarm.
Description
All channel elements on the UCU have failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure of all channel elements
System impact
No call processing on this UCU is possible. The system capacity is degraded.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-673
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
UCU_excessiveDownlinkParityErrors
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_excessiveDownlinkParityErrors
alarm.
Description
The UTRA Channel Unit (UCU) causes a parity error on the transmit bus to the Radio.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Hardware failure on UCU
• Hardware failure on Radio
• Connection problem to backplane.
System impact
The overall traffic capacity of the Node B is reduced.
...................................................................................................................................................................................................................................
15-674 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance UCU_excessiveDownlinkParityErrors
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, check for clock alarms and take appropriate action.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
7 At the Node B, make sure that the backplane and UCU backplane connector are OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-675
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
UCU_excessiveUplinkParityErrors
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_excessiveUplinkParityErrors
alarm.
Description
The UCU has detected that the uplink data stream on the reverse traffic bus exhibits
excessive parity error rates. This bus is part of the backplane.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Transmit failure
• Failure on transmitting Radio
System impact
All uplink channels of the UCU are unavailable. No call processing on this UCU is
possible. The system capacity is degraded.
...................................................................................................................................................................................................................................
15-676 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance UCU_excessiveUplinkParityErrors
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, check for Radio alarms and perform fault clearance procedures for
the alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the OMC-UPS, check for power supply and clock reports and take the appropriate
action.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
8 At the Node B, make sure that the backplane bus is working properly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-677
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
UCU_fPGAFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_fPGAFailure alarm.
Description
The UCU has detected a faulty Field Programmable Gate Array (FPGA) behavior
during reset, load or start of the FPGA.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
This could be a FPGA hardware problem or a problem with the loadable FPGA image.
System impact
No call processing on this UCU is possible. The system capacity is degraded.
...................................................................................................................................................................................................................................
15-678 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance UCU_fPGAFailure
procedures
...................................................................................................................................................................................................
If... Then...
This is the only UCU that is Go to step 2.
reporting an alarm,
There are more UCUs reporting Go to step 8.
an alarm,
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-679
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance UCU_fPGAFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-680 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
UCU_hwErrorDetectedByPlatformSw
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_hwErrorDetectedByPlat-
formSw alarm.
Description
The platform code (USL) that supports the application software has detected a
potentially unrecoverable hardware fault.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Hardware failure
System impact
Calls served by this UCU are dropped. The traffic capacity of the Node Bs is
temporarily degraded.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-681
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance UCU_hwErrorDetectedByPlatformSw
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-682 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
UCU_initialisationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_initialisationFailure alarm.
Description
The UTRA Channel Unit (UCU) failed to initialize due to a Board Level Self Test
(BLST), Reset, or Enable Failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
No call processing on this UCU is possible. The system capacity is degraded.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-684 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
UCU_lossOfForwardBusLink
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_lossOfForwardBusLink alarm.
Description
The UTRA Channel Unit (UCU) causes a link loss on the transmit bus to the Radio.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Hardware failure on UCU
• Hardware failure on Radio
• Connection problem to backplane.
System impact
Overall Node B’s traffic capacity is reduced.
...................................................................................................................................................................................................
6 At the Node B, make sure that the backplane and UCU backplane connector are OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-686 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
UCU_majorChannelElementSystemResourceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_majorChannelElementSys-
temResourceFailure alarm.
Description
At least one, but not all channel elements have failed on the UCU board.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
channel element failure.
System impact
The capacity of the UCU is degraded.
Service Interruption on failed channel elements.
1 At the OMC-UPS, check for CTU and OM (if present) alarms and perform the fault
clearance procedure for these alarms.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-688 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
UCU_majorPlatformSwError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_majorPlatformSwError alarm.
Description
The platform code (USL) that supports the application software has reported a major
error.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
The UCU platform SW detected an error condition that can only be cleared by a restart
of the application software.
System impact
Calls served by this UCU are dropped. The Node B’s traffic capacity is temporarily
degraded.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-689
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance UCU_majorPlatformSwError
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-690 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
UCU_selfTestFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_selfTestFailure alarm.
Description
The UTRA Channel Unit (UCU) Board Level Self Test (BLST) failed. The BLST is
stored in the Info RAM and can be read.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
No call processing on this UCU is possible. The system capacity is degraded.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-692 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
UCU_voltageOutOfRange
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_voltageOutOfRange alarm.
Description
The internal voltage provided by the on board power supply is out of range.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment failure.
System impact
No call processing on this UCU is possible. System capacity is degraded.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-693
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance UCU_voltageOutOfRange
procedures
...................................................................................................................................................................................................
3 At the Node B, check and repair the power supply for the UCU boards
...................................................................................................................................................................................................
4 At the OMC-UPS, reset the UCU object to initialize the UCU board.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
5 At the Node B, check the power supply at the board slot for further indications and
take the appropriate action.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-694 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
UCU_watchdogInitiatedReset
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the UCU_watchdogInitiatedReset alarm.
Description
The UTRA Channel Unit (UCU) watchdog process has reset the UCU.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Timing problem.
System impact
Call capacity is temporarily degraded.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-695
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance UCU_watchdogInitiatedReset
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-696 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
URC alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Universal Radio Controller
(URC).
Contents
URC_aTMOutOfCellDelineation 15-698
URC_applicationInsane 15-700
URC_clockFailure30_72Mhz 15-701
URC_configurationMismatch 15-703
URC_hardwareModelMismatch 15-705
URC_hwErrorDetectedByPlatformSw 15-707
URC_localConfigurationFailure 15-709
URC_lossOfPulse 15-711
URC_majorPlatformSwError 15-713
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-697
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
URC_aTMOutOfCellDelineation
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the URC_aTMOutOfCellDelineation
alarm.
Description
A configuration error has occurred in ATM communication.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
Configuration or customizing error.
System impact
Traffic on the whole Node B is impossible.
1 Check the ATM network configuration between the RNC and the Node B for clock
errors and take the appropriate action.
...................................................................................................................................................................................................................................
15-698 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance URC_aTMOutOfCellDelineation
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-699
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance
procedures
URC_applicationInsane
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the URC_applicationInsane alarm.
Description
Application software executing on the URC is not functioning properly.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Software program error.
System impact
Traffic on the whole Node B is impossible.
...................................................................................................................................................................................................................................
15-700 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
URC_clockFailure30_72Mhz
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the URC_clockFailure30_72Mhz alarm.
Description
The 30.72 MHz clock signal from the CTU has failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
Calls on the whole Node B are lost.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-701
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance URC_clockFailure30_72Mhz
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-702 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
URC_configurationMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the URC_configurationMismatch alarm.
Description
The configuration conflicts with attribute value(s) of other object(s).
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No service available
1 At the Node B, check for nodeBTypeMismatch alarm of the NodeB object and perform
the fault clearance procedure for that alarm.
If this alarm is cleared together with the nodeBTypeMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent customer support to verify the planning data for this Node B
and recreate the Node B with the new data.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-703
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance URC_configurationMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-704 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
URC_hardwareModelMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the URC_hardwareModelMismatch
alarm.
Description
The detected hardware does not match the value specified.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Inconsistent planning.
System impact
No impact on service.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-705
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance URC_hardwareModelMismatch
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, update the expected hardware model attribute to match the detected
hardware model attribute.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-706 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
URC_hwErrorDetectedByPlatformSw
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the URC_hwErrorDetectedByPlat-
formSw alarm.
Description
The platform which supports the application software has detected a potentially
unrecoverable hardware fault.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Hardware failure
System impact
The whole Node B is reset and temporarily unavailable.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-707
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance URC_hwErrorDetectedByPlatformSw
procedures
....................................................................................................................................................................................................................................
15-708 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
URC_localConfigurationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the URC_localConfigurationFailure
alarm.
Description
The configuration conflicts with local configuration data.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Missing or faulty local configuration data.
System impact
No service available
1 At the Node B, check for configurationMismatch alarm and perform fault clearance
procedure for that alarm..
If the alarm is cleared together with the configurationMismatch alarm, the procedure is
completed.
...................................................................................................................................................................................................
2 At the OMC-UPS, check and update local configuration data via remote RMT.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-709
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance URC_localConfigurationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-710 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
URC_lossOfPulse
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the URC_lossOfPulse alarm.
Description
The URC failed to detect the 10 millisecond pulse.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Timing problem.
System impact
Calls on the whole Node B are lost.
1 At the OMC-UPS, check for clock alarms of the CTU and OM and perform fault
clearance procedures for the alarms..
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
15-712 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - Node B alarm clearance
procedures
URC_majorPlatformSwError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the URC_majorPlatformSwError alarm.
Description
The platform code (USL) that supports the application software has reported a major
error.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
The URC platform software detected an error condition that can only be cleared by a
restart of the application software.
System impact
The whole Node B is reset and temporarily unavailable.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 15-713
Issue 1, August 2007 See notice on first page
Corrective maintenance - Node B alarm clearance URC_majorPlatformSwError
procedures
....................................................................................................................................................................................................................................
15-714 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
16 16
Corrective maintenance - RNC
alarm clearance procedures
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter provides procedures to clear RNC alarms that are raised on the OMC.
Related information
For more related information about this topic, refer to:
• Radio Network Controller Operations, Administration and Maintenance RNC
OA&M, 401-382-360
Contents
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-1
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance Overview
procedures
CICC_maintenanceMode 16-37
CICC_notInstalled 16-38
CICC_overTemperature 16-40
CICC_overTemperatureInFlow 16-42
CICC_overTemperatureOutFlow 16-44
CICCBPEtherPort alarms 16-46
CICCBPEtherPort_communicationFailureESC1_2 16-47
CICCBPEtherPort_communicationFailureESC1_21 16-49
CICCBPEtherPort_communicationFailureESC2_2 16-51
CICCBPEtherPort_communicationFailureESC2_21 16-53
CICCBPEtherPort_linkFailure 16-55
CICCBPEtherPort_restoreServiceFailure 16-57
CICCProc alarms 16-59
CICCProc_communicationFailure 16-60
CICCProc_communicationFailureLRM 16-62
CICCProc_configurationError 16-64
CICCProc_cpuUsageOverload 16-65
CICCProc_criticalSoftwareFailure 16-66
CICCProc_heartbeatFailure 16-68
CICCProc_memoryBlockError 16-70
CICCProc_memoryUsageOverload 16-72
CICCProc_resourceFailure 16-73
CICCProc_restoreServiceFailure 16-75
CICCProc_softwareAssertError 16-77
CICCProc_softwareVersionMismatch 16-79
CICCProc_standbyMateDown 16-81
CICCProc_switchover 16-83
CICCProc_vitalResourceFailure 16-85
Cabinet alarms 16-87
Cabinet_fanOrCktBreakerFailure 16-88
EDCH alarms 16-89
EDCH_configurationRequestFailed 16-90
...................................................................................................................................................................................................................................
16-2 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance Overview
procedures
EDCH_resourceDegradation 16-92
EDCH_resourceFailure 16-94
ESC alarms 16-96
ESC_degradeGroupMemberFault 16-97
ESC_failureGroupMemberFault 16-99
ESC_lossOfPower 16-101
ESC_lossOfSanity 16-103
ESC_lostCommunication 16-105
ESC_maintenanceMode 16-107
ESC_notInstalled 16-108
ESC_overTemperature 16-110
ESCProc_softwareVersionMismatch 16-112
ESCBPEtherPort alarms 16-114
ESCBPEtherPort_linkFailure 16-115
ESCFAEtherPort alarms 16-117
ESCFAEtherPort_linkFailure 16-118
ESCProc alarms 16-120
ESCProc_communicationFailure 16-121
ExtAlmBox alarms 16-123
ExtAlmBox_communicationFailure 16-125
ExtAlmBox_externalAlarmPort1 16-127
ExtAlmBox_externalAlarmPort10 16-129
ExtAlmBox_externalAlarmPort11 16-131
ExtAlmBox_externalAlarmPort12 16-133
ExtAlmBox_externalAlarmPort13 16-135
ExtAlmBox_externalAlarmPort14 16-137
ExtAlmBox_externalAlarmPort15 16-139
ExtAlmBox_externalAlarmPort16 16-141
ExtAlmBox_externalAlarmPort17 16-143
ExtAlmBox_externalAlarmPort18 16-145
ExtAlmBox_externalAlarmPort19 16-147
ExtAlmBox_externalAlarmPort2 16-149
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-3
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance Overview
procedures
ExtAlmBox_externalAlarmPort20 16-151
ExtAlmBox_externalAlarmPort21 16-153
ExtAlmBox_externalAlarmPort22 16-155
ExtAlmBox_externalAlarmPort23 16-157
ExtAlmBox_externalAlarmPort24 16-159
ExtAlmBox_externalAlarmPort25 16-161
ExtAlmBox_externalAlarmPort26 16-163
ExtAlmBox_externalAlarmPort27 16-165
ExtAlmBox_externalAlarmPort28 16-167
ExtAlmBox_externalAlarmPort29 16-169
ExtAlmBox_externalAlarmPort3 16-171
ExtAlmBox_externalAlarmPort30 16-173
ExtAlmBox_externalAlarmPort31 16-175
ExtAlmBox_externalAlarmPort32 16-177
ExtAlmBox_externalAlarmPort4 16-179
ExtAlmBox_externalAlarmPort5 16-181
ExtAlmBox_externalAlarmPort6 16-183
ExtAlmBox_externalAlarmPort7 16-185
ExtAlmBox_externalAlarmPort8 16-187
ExtAlmBox_externalAlarmPort9 16-189
FBPShelf alarms 16-191
FBPShelf_overTemperature 16-192
FBPShelf_overTemperatureSensor1 16-194
FBPShelf_overTemperatureSensor2 16-196
FBPShelf_overTemperatureSensor3 16-198
FBPShelf_overTemperatureSensor4 16-200
FBPShelf_overTemperatureSensor5 16-202
FBPShelf_overTemperatureSensor6 16-204
FBPShelf_overTemperatureSensor7 16-206
FBPShelf_overTemperatureSensor8 16-208
FanTray alarms 16-210
FanTray_fan1Failure 16-211
...................................................................................................................................................................................................................................
16-4 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance Overview
procedures
FanTray_fan2Failure 16-213
FanTray_fan3Failure 16-215
FanTray_notInstalled 16-217
GICC alarms 16-218
GICC_degradeGroupMemberFault 16-219
GICC_escalatingRecovery 16-221
GICC_failureGroupMemberFault 16-223
GICC_lossOfPower 16-225
GICC_lossOfSanity 16-227
GICC_lostCommunication 16-229
GICC_maintenanceMode 16-231
GICC_notInstalled 16-232
GICC_overTemperature 16-234
GICC_overTemperatureInFlow 16-236
GICC_overTemperatureOutFlow 16-238
GICCBPEtherPort alarms 16-240
GICCBPEtherPort_communicationFailureESC1_2 16-241
GICCBPEtherPort_communicationFailureESC1_21 16-243
GICCBPEtherPort_communicationFailureESC2_2 16-245
GICCBPEtherPort_communicationFailureESC2_21 16-247
GICCBPEtherPort_linkFailure 16-249
GICCBPEtherPort_restoreServiceFailure 16-251
GICCFAEtherPort alarms 16-253
GICCFAEtherPort_linkFailure 16-254
GICCFAEtherPort_restoreServiceFailure 16-256
GICCProc alarms 16-258
GICCProc_allOpticalLinksFailed 16-259
GICCProc_communicationFailure 16-261
GICCProc_communicationFailureLRM 16-263
GICCProc_configurationError 16-265
GICCProc_cpuUsageOverload 16-266
GICCProc_criticalSoftwareFailure 16-267
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-5
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance Overview
procedures
GICCProc_heartbeatFailure 16-269
GICCProc_memoryBlockError 16-271
GICCProc_memoryUsageOverload 16-273
GICCProc_resourceFailure 16-274
GICCProc_restoreServiceFailure 16-276
GICCProc_softwareAssertError 16-278
GICCProc_softwareVersionMismatch 16-280
GICCProc_standbyMateDown 16-282
GICCProc_vitalResourceFailure 16-284
GICCSTM1OC3Port alarms 16-286
GICCSTM1OC3Port_linkFailure 16-287
GICCSTM1OC3Port_linkFailureAIS_L 16-289
GICCSTM1OC3Port_linkFailureAIS_P 16-291
GICCSTM1OC3Port_linkFailureLCD_P 16-293
GICCSTM1OC3Port_linkFailureLOF 16-295
GICCSTM1OC3Port_linkFailureLOP_P 16-297
GICCSTM1OC3Port_linkFailureLOS 16-299
GICCSTM1OC3Port_linkFailurePLM_P 16-301
GICCSTM1OC3Port_linkFailureRDI_L 16-303
GICCSTM1OC3Port_linkFailureRDI_P 16-305
GICCSTM1OC3Port_restoreServiceFailure 16-307
HSDPA alarms 16-309
HSDPA_degraded 16-310
HSDPA_failed 16-312
HSDPA_hSDPAOCNSchannelSetupFailure 16-314
HSDPA_notInstalled 16-316
IuB alarms 16-318
IuB_cellReconfigTimeout 16-319
IuB_cellSetupTimeout 16-321
IuB_channelReconfigFailure 16-323
IuB_channelReconfigTimeout 16-325
IuB_channelSetupFailure 16-327
...................................................................................................................................................................................................................................
16-6 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance Overview
procedures
IuB_channelSetupTimeout 16-329
IuB_highBER 16-331
IuB_nBAP_Reset_Requ_CCP_Fail 16-333
IuB_nBAP_Reset_Requ_Fail 16-335
IuB_nodeBCommunicationLost 16-337
IuB_parameterFailure 16-340
IuB_resourceFailure 16-342
IuB_sAALUNI_RES_PROT_STA_DN 16-344
IuB_sAALUNI_VCC_ST_DN 16-346
IuB_uNIStack_FAIL 16-348
IuCS alarms 16-350
IuCS_coreNetwork_OOS_For_NonUE_Sig 16-351
IuCS_rANAPResetFail 16-353
IuCS_remoteSubsystemOutOfService 16-355
IuCS_sNE_Context_Cre_Fail_For_NonUE_Sig 16-357
IuPS alarms 16-359
IuPS_coreNetwork_OOS_For_NonUE_Sig 16-360
IuPS_gTP_U_Echo_Responses_Not_Received 16-362
IuPS_rANAPResetFail 16-364
IuPS_remoteSubsystemOutOfService 16-366
IuPS_sNE_Context_Cre_Fail_For_NonUE_Sig 16-368
IuPSSubNet alarms 16-370
IuPSSubNet_communicationFailure 16-371
IuR alarms 16-373
IuR_pRNC_OOS_For_NonUE_Sig 16-374
IuR_remoteSubsystemOutOfService 16-376
IuR_sNE_Context_Cre_Fail_For_NonUE_Sig 16-378
LCell alarms 16-380
LCell_avail_Status_Degraded 16-381
LCell_bCCHScheduleErr 16-382
LCell_callPreemptionError 16-384
LCell_callPreemptionFailure 16-386
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-7
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance Overview
procedures
LCell_channelSetupFailure 16-388
LCell_code_Allocation_Failure 16-390
LCell_code_Starvation 16-392
LCell_common_Transport_Channel_Reconfiguration_Failure 16-394
LCell_common_Transport_Channel_Reconfiguration_Timeout 16-396
LCell_common_Transport_Channel_Setup_Failure 16-398
LCell_common_Transport_Channel_Setup_Timeout 16-400
LCell_configurationError 16-402
LCell_configurationErrorSCCPCH 16-404
LCell_nodeBUnavailable 16-406
LCell_rRC_Connection_Establish_Failure 16-408
LCell_reconfigFailure 16-410
LCell_reconfigTimeout 16-412
LCell_setupFailure 16-414
LCell_setupTimeout 16-416
LCell_system_Information_Update_Failure 16-418
LCell_tPUCellContextFailure 16-420
LNodeB alarms 16-421
LNodeB_cell_Deletion_No_Response 16-422
LNodeB_cre_Control_End_Pt_Fail 16-424
LNodeB_download_Logical_Cell_Information_To_RNC_Failed 16-425
LRNC alarms 16-427
LRNC_alarmDefFileCorrupt 16-429
LRNC_alarmDefFileMissing 16-431
LRNC_cLIScriptFailed 16-433
LRNC_ciccGiccConfigFileMissing 16-435
LRNC_clockSourceFailure 16-437
LRNC_configurationError 16-438
LRNC_coreFileGenerated 16-440
LRNC_dBReplicationAuditFailure 16-442
LRNC_dGPSCorrFailure 16-445
LRNC_dataAuditFailure 16-447
...................................................................................................................................................................................................................................
16-8 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance Overview
procedures
LRNC_degradeGroupMemberFault 16-449
LRNC_eventFloodConditionDetected 16-451
LRNC_failureGroupMemberFault 16-453
LRNC_ftProcessError 16-454
LRNC_general_Handling_Error_Indication 16-457
LRNC_hostProcessCommunicationFailure 16-459
LRNC_hostProcessEnlistTimeout 16-461
LRNC_hostProcessFailure 16-463
LRNC_hostProcessRestartFailure 16-464
LRNC_hostProcessRestartSuspended 16-466
LRNC_hostProcessTerminationFailure 16-468
LRNC_iCNOAPVCMeshErr 16-470
LRNC_iNITrunLevelTimeout 16-472
LRNC_iNITterminatingTimeout 16-474
LRNC_internal_Clock_Source_Disconnected 16-476
LRNC_log100PercentFull 16-477
LRNC_log80PercentFull 16-479
LRNC_miscellaneous-Cause 16-481
LRNC_oamStateControlFailure 16-483
LRNC_perfMgr_DNMAP_INIT 16-485
LRNC_pmArchiveInitFailure 16-487
LRNC_pmCTDBImageFailure 16-489
LRNC_pmCTDBInitFailure 16-491
LRNC_primary_Clock_Source_Disconnected 16-493
LRNC_sMLC_UDP_Port_Fail 16-495
LRNC_sRS_NAV_Data_Ind 16-496
LRNC_secondSRSTCPEstLinkFailure 16-498
LRNC_suActivationFailure 16-500
LRNC_suApplyFailure 16-503
LRNC_suBackoutFailure 16-506
LRNC_suCommitFailure 16-510
LRNC_suDeApplyFailure 16-512
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-9
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance Overview
procedures
LRNC_suDeleteFailure 16-515
LRNC_suDownloadFailure 16-517
LRNC_suFallbackFailure 16-520
LRNC_suICCPartialUpdateFailure 16-523
LRNC_suInfoSyncFailure 16-526
LRNC_suInstallFailure 16-529
LRNC_suStatePanicFailure 16-531
LRNC_ueCompressedModeGapOverlap 16-533
LRNC_utranCompressedModeGapOverlap 16-535
OCNS alarms 16-537
OCNS_chDelRxLock 16-538
OCNS_channelFailure 16-540
OCNS_channelReconfigFailure 16-542
OCNS_channelReestablished 16-544
OCNS_channelSetupFailure 16-546
OCNS_resourcesUnavailable 16-548
OCNSHSDPA alarms 16-550
OCNSHSDPA_failureIndicationFromNodeB 16-551
OCNSHSDPA_setupFailed 16-553
PG alarms 16-555
PG_apsCriticalLineFailure 16-556
PG_apsCriticalProcessorFailure 16-558
PG_apsMajorLineFailure 16-560
PG_apsMajorProcessorFailure 16-562
PG_apsMinorLineFailure 16-564
PG_apsMinorProcessorFailure 16-566
PRACH alarms 16-568
PRACH_op_State_Disabled 16-569
PSU alarms 16-571
PSU_equipmentFailure 16-572
PSU_overTemperature 16-574
RF trace alarms 16-576
...................................................................................................................................................................................................................................
16-10 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance Overview
procedures
RFTrace_ueMeasurementsUnavailable 16-577
SB alarms 16-579
SB_bscSwFailOutage_CNIWMCapsule1 16-580
SB_bscSwFailOutage_CellServerCapsule1 16-582
SB_bscSwFailOutage_CellServerCapsule10 16-584
SB_bscSwFailOutage_CellServerCapsule2 16-586
SB_bscSwFailOutage_CellServerCapsule3 16-588
SB_bscSwFailOutage_CellServerCapsule4 16-590
SB_bscSwFailOutage_CellServerCapsule5 16-592
SB_bscSwFailOutage_CellServerCapsule6 16-594
SB_bscSwFailOutage_CellServerCapsule7 16-596
SB_bscSwFailOutage_CellServerCapsule8 16-598
SB_bscSwFailOutage_CellServerCapsule9 16-600
SB_bscSwFailOutage_PeerRNCIWMCapsule1 16-602
SB_bscSwFailOutage_RNSServerCapsule1 16-604
SB_degradeGroupMemberFault 16-606
SB_failureGroupMemberFault 16-608
SB_lossOfPower 16-610
SB_lossOfSanity 16-612
SB_lostCommunication 16-614
SB_maintenanceMode 16-616
SB_notInstalled 16-617
SB_overTemperature 16-619
SBBPEtherPort alarms 16-621
SBBPEtherPort_linkFailure 16-622
SBClan alarms 16-623
SBClan_linkFail 16-624
SBProc alarms 16-625
SBProc_acCommunicationFailure 16-627
SBProc_componentMissing 16-628
SBProc_cpuUsageOverload 16-629
SBProc_diskReadTimeExceeded 16-630
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-11
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance Overview
procedures
SBProc_fLXEV_CLAN_PARENT_FAIL 16-632
SBProc_fLXEV_NODE_FAILING 16-633
SBProc_fLXEV_NODE_NOTACTIVE 16-635
SBProc_fLXEV_SMON_NOHBEAT 16-637
SBProc_filesystem01Full 16-639
SBProc_filesystem02Full 16-640
SBProc_filesystem03Full 16-641
SBProc_filesystem04Full 16-642
SBProc_filesystem05Full 16-643
SBProc_filesystem06Full 16-644
SBProc_filesystem07Full 16-645
SBProc_filesystem08Full 16-646
SBProc_filesystem09Full 16-647
SBProc_filesystem10Full 16-648
SBProc_filesystem11Full 16-649
SBProc_filesystem12Full 16-650
SBProc_filesystem13Full 16-651
SBProc_filesystem14Full 16-652
SBProc_filesystem15Full 16-653
SBProc_filesystem16Full 16-654
SBProc_lossOfClockSourceSync 16-655
SBProc_memoryUsageOverload 16-657
SBProc_nodeFailure 16-659
SBProc_overTemperature 16-661
SBProc_processFailure 16-663
SBProc_processFailureApplication 16-665
SBProc_rootLoginFailure 16-668
SBProc_sULoginFailure 16-669
SBProc_shutdownTempReached 16-670
SBProc_temperatureOffLimits 16-672
SBProc_userLoginFailure 16-674
SBProc_virtualClusterFailure 16-675
...................................................................................................................................................................................................................................
16-12 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance Overview
procedures
SBProc_virtualClusterVirtualMachineFailure 16-676
SCCPCHFach alarms 16-678
SCCPCHFach_op_State_Disabled 16-679
SCCPCHPch alarms 16-681
SCCPCHPch_op_State_Disabled 16-682
SMLC alarms 16-684
SMLC_dGPSCorrectionFailure 16-685
SMLC_primarySRSIpConnectionFailure 16-687
SMLC_primarySRSLinkFailure 16-689
SMLC_sRS-Both-IP-Fail 16-691
SMLC_sRS_SV_Ind 16-693
SMLC_secondarySRSIpConnectionFailure 16-695
SMLC_secondarySRSLinkFailure 16-697
SS7Link alarms 16-699
SS7Link_mtp3LinkDown 16-700
SS7Link_mtp3LinkRemotelyBlocked 16-702
SS7Link_qsaalLinkCongested 16-704
SS7LinkSet alarms 16-706
SS7LinkSet_congestionTowardsRemoteMTP3 16-707
SS7LinkSet_remoteMTP3Unreachable 16-709
SS7LinkSet_remoteMTP3UserUnavailable 16-711
SS7Stack alarms 16-712
SS7Stack_nniStackFailure 16-713
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-13
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
General information
Overview
...................................................................................................................................................................................................................................
Purpose
This section provides general information on how the RNC handles hardware and
software faults.
Contents
...................................................................................................................................................................................................................................
16-14 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
Purpose
This topic describes alarm recovery actions that are taken when a fault occurs in the
RNC hardware or software.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-15
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance RNC fault recovery actions
procedures
Alarm occurs
Report alarm
Autonomous Y
recovery action
performed?
Re-
N
Isolate N initialization N
unit? threshold
reached?
Re-initialize unit
Y Y
Isolate unit
Operator performs
fault clearance procedure
N Fault
cleared?
Is
alarm of N Operator
ADAC clears alarm
Nature?
Automatically
clear alarm
End
....................................................................................................................................................................................................................................
16-16 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance RNC fault recovery actions
procedures
Automatically reinitialize
If the unit supports an automatic reinitialization, one or more of the following
reinitialization actions can be performed:
• Restart one or more software processes
• Reboot the software
• Reset the complete unit.
Note: If the automatic reinitialization fails, this action is repeated until the
reinitialization threshold has been exceeded. When the threshold is exceeded and the
fault is not corrected, the unit will be isolated.
Isolate unit
If the unit does not support an automatic recovery action, the unit can be put into an
isolated state. When the unit is in this state it cannot be used by any of the other units.
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-17
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
Overview
This topic describes the autonomous actions that are taken by the RNC whenever the
RNC is internally reset.
Autonomous recovery
When a severe fault occurs, the RNC will autonomously reset itself.
Notes:
1. If the RNC software restarted successfully.
...................................................................................................................................................................................................................................
16-18 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-19
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
AC alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Alarm Card alarms.
Contents
AC_communicationFailure 16-21
AC_softwareVersionMismatch 16-23
...................................................................................................................................................................................................................................
16-20 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
AC_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the AC_communicationFailure alarm.
Description
Communication to the Alarm Card (AC) has failed.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
No SNMP communication between the SB and alarm card.
System impact
No blade management functions available.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-21
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance AC_communicationFailure
procedures
...................................................................................................................................................................................................
4 At the OMC-UPS, check if there are ESC alarms and correct ESC failures.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-22 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
AC_softwareVersionMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the AC_softwareVersionMismatch alarm.
Description
The software version running on this processor does not match the provisioned
software version.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
A software installation failed or has not initiated.
System impact
Processor may not initialize properly.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-23
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICC alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Common Intelligent
Carrier Card (CICC).
Contents
CICC_degradeGroupMemberFault 16-25
CICC_escalatingRecovery 16-27
CICC_failureGroupMemberFault 16-29
CICC_lossOfPower 16-31
CICC_lossOfSanity 16-33
CICC_lostCommunication 16-35
CICC_maintenanceMode 16-37
CICC_notInstalled 16-38
CICC_overTemperature 16-40
CICC_overTemperatureInFlow 16-42
CICC_overTemperatureOutFlow 16-44
...................................................................................................................................................................................................................................
16-24 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICC_degradeGroupMemberFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_degradeGroupMemberFault
alarm.
Description
A member of the Common Intelligent Carrier Card (CICC) degrade group failed.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
A member of a degrade group faulted (operationalState Disabled and
availabilityStatus Failed). This causes the CICC to go degraded (operationalState
Enabled and availabilityStatus Degraded).
The members of the CICC degrade group are:
• The 2 non-main processors (CICCProc 1 and CICCProc 2)
• All backplane Ethernet ports (CICCBPEtherPort)
System impact
The CICC is considered degraded.
The system impact depends on the rootcause of the alarm.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-25
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICC_degradeGroupMemberFault
procedures
....................................................................................................................................................................................................................................
16-26 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICC_escalatingRecovery
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_escalatingRecovery alarm.
Description
The system is escalating recovery of the Common Intelligent Carrier Card (CICC) and
may have exhausted attempts to recover the unit.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
The CICC is not responding to recovery due to software or hardware failure.
System impact
Voice and data handling traffic handling capacity decreased.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-27
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICC_escalatingRecovery
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-28 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICC_failureGroupMemberFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_failureGroupMemberFault
alarm.
Description
A member of the Common Intelligent Carrier Card (CICC) failure group failed.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
A member of a failure group faulted (operationalState Disabled and
availabilityStatus Failed). This causes the CICC to fail (operationalState Disabled
and availabilityStatus Failed).
The member of the CICC failure group is:
• The main processor (CICCProc 0)
System impact
The CICC is not operational.
The system impact depends on the rootcause of the alarm.
....................................................................................................................................................................................................................................
16-30 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICC_lossOfPower
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_lossOfPower alarm.
Description
The Common Intelligent Carrier Card (CICC) has lost power.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment problem.
System impact
No direct system impact.
2 At the RNC, check whether the CICC is inserted into correct slot and powered on.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-31
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICC_lossOfPower
procedures
...................................................................................................................................................................................................
3 At the RNC, if the CICC is inserted in the correct slot, remove and re-insert the CICC.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-32 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICC_lossOfSanity
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_lossOfSanity alarm.
Description
The Common Intelligent Carrier Card (CICC) lost sanity or integrity.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
The Alarm Card did not detect a board healthy signal from the CICC.
System impact
The CICC is inoperative and the capacity to handle voice and data traffic decreases.
2 At the RNC, check whether the CICC is inserted into correct slot and powered on.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-34 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICC_lostCommunication
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_lostCommunication alarm.
Description
Alarm Card (AC) lost heartbeat communication to the Common Intelligent Carrier
Card (CICC).
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Equipment problem.
System impact
The CICC may operate but will likely not respond to some OA&M commands,
especially those entered through the CLI.
1 At the RNC, check whether the CICC is inserted into correct slot and powered on.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the RNC, if the CICC is inserted in the correct slot, remove and re-insert the CICC.
If the alarm is cleared,the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-35
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICC_lostCommunication
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-36 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICC_maintenanceMode
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_maintenanceMode alarm.
Description
The Common Intelligent Carrier Card (CICC) is in maintenance mode.
Default severity
Warning
Alarm type
processingErrorAlarm
Root cause
Configuration problem.
System impact
Alarm Card recovery for this CICC is inhibited.
1 At the RNC, use the maintenance terminal to put the CICC back into active mode.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-37
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICC_notInstalled
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_notInstalled alarm.
Description
Common Intelligent Carrier Card (CICC) is not properly installed in the shelf slot.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
The specified CICC is physically removed from the shelf or is not correctly inserted
and the Alarm Card does not detect the CICC.
System impact
The CICC is inoperative and the capacity to handle voice and data traffic decreases.
1 At the RNC, if the CICC is not inserted, insert the CICC into the correct slot .
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the RNC, if the CICC is inserted in the correct slot, remove and re-insert the CICC.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-38 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance CICC_notInstalled
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-39
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICC_overTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_overTemperature alarm.
Description
The temperature is above the specified limit.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-40 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance CICC_overTemperature
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly by replacing
the card.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-41
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICC_overTemperatureInFlow
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_overTemperatureInFlow
alarm.
Description
The inflow temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-42 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance CICC_overTemperatureInFlow
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly by replacing
the card.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-43
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICC_overTemperatureOutFlow
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICC_overTemperatureOutFlow
alarm.
Description
The outflow temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-44 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance CICC_overTemperatureOutFlow
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly by replacing
the card.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-45
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICCBPEtherPort alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the CICC Ethernet port
alarms.
Contents
CICCBPEtherPort_communicationFailureESC1_2 16-47
CICCBPEtherPort_communicationFailureESC1_21 16-49
CICCBPEtherPort_communicationFailureESC2_2 16-51
CICCBPEtherPort_communicationFailureESC2_21 16-53
CICCBPEtherPort_linkFailure 16-55
CICCBPEtherPort_restoreServiceFailure 16-57
...................................................................................................................................................................................................................................
16-46 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCBPEtherPort_communicationFailureESC1_2
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCBPEtherPort_communication-
FailureESC1_2 alarm.
Description
Ethernet communication to shelf 1, ESC 2 has failed.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• ESC hardware failure
• CICC hardware failure
• Cable failures
System impact
No direct impact, the alternate fabric is used to provide Ethernet communication.
However the card is now vulnerable.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-47
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCBPEtherPort_communicationFailureESC1_2
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-48 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCBPEtherPort_communicationFailureESC1_21
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCBPEtherPort_communication-
FailureESC1_21 alarm.
Description
Ethernet communication to shelf 1, ESC 21 has failed.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• ESC hardware failure
• CICC hardware failure
• Cable failures
System impact
No direct impact, the alternate fabric is used to provide Ethernet communication.
However the card is now vulnerable.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-49
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCBPEtherPort_communicationFailureESC1_21
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-50 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCBPEtherPort_communicationFailureESC2_2
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCBPEtherPort_communication-
FailureESC2_2 alarm.
Description
Ethernet communication to shelf 2, ESC 2 has failed.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• ESC hardware failure
• CICC hardware failure
• Cable failures
System impact
No direct impact, the alternate fabric is used to provide Ethernet communication.
However the card is now vulnerable.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-51
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCBPEtherPort_communicationFailureESC2_2
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-52 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCBPEtherPort_communicationFailureESC2_21
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCBPEtherPort_communication-
FailureESC2_21 alarm.
Description
Ethernet communication to shelf 2, ESC 21 has failed.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• ESC hardware failure
• CICC hardware failure
• Cable failures.
System impact
No direct impact, the alternate fabric is used to provide Ethernet communication.
However the card is now vulnerable.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-53
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCBPEtherPort_communicationFailureESC2_21
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-54 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCBPEtherPort_linkFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCBPEtherPort_linkFailure alarm.
Description
A failure occurred on the backplane ethernet link connection.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Backplane ethernet connection failure.
System impact
No communication with CICC possible.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-55
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCBPEtherPort_linkFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-56 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCBPEtherPort_restoreServiceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCBPEtherPort_restoreSer-
viceFailure alarm.
Description
Request to restore service of the Common Intelligent Carrier Card (CICC) backplane
ethernet port has failed
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Maintenance action could not be performed due to underlying software failure.
System impact
CICC not available.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-58 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCProc alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the CICC Processor
(CICCProc).
Contents
CICCProc_communicationFailure 16-60
CICCProc_communicationFailureLRM 16-62
CICCProc_configurationError 16-64
CICCProc_cpuUsageOverload 16-65
CICCProc_criticalSoftwareFailure 16-66
CICCProc_heartbeatFailure 16-68
CICCProc_memoryBlockError 16-70
CICCProc_memoryUsageOverload 16-72
CICCProc_resourceFailure 16-73
CICCProc_restoreServiceFailure 16-75
CICCProc_softwareAssertError 16-77
CICCProc_softwareVersionMismatch 16-79
CICCProc_standbyMateDown 16-81
CICCProc_switchover 16-83
CICCProc_vitalResourceFailure 16-85
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-59
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_communicationFailure
alarm.
Description
Communication to the processor of the Common Intelligent Carrier Card (CICC) has
failed.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
No SNMP communication between the SB and CICC.
System impact
CICC not available.
1 At the OMC-UPS, if the CICC is initializing, ensure that the CICC restores
successfully.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
16-60 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance CICCProc_communicationFailure
procedures
...................................................................................................................................................................................................
4 At the OMC-UPS, check if there are ESC alarms and correct ESC failures.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-61
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_communicationFailureLRM
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_communicationFail-
ureLRM alarm.
Description
Communication from FMS host processor to LRM on the CICC processor has failed.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• Faulty hardware
• Bad software image
• Incorrect board installed
• An initialization is in progress
System impact
CICC processor is unavailable for use by call processing.
1 If alarm has not cleared within 15 minutes, check if other boards of the same type
have successfully booted, if not, verify correct software is installed successfully.
...................................................................................................................................................................................................................................
16-62 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance CICCProc_communicationFailureLRM
procedures
...................................................................................................................................................................................................
3 At the RNC, replace the board if it has previously been inservice or verify the correct
board was installed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-63
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_configurationError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_configurationError alarm.
Description
An error was found in the configuration data used by this processor.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
The data was either populated incorrectly initially, or a data change was made that
introduced the error.
System impact
Call processing may be affected.
...................................................................................................................................................................................................................................
16-64 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_cpuUsageOverload
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_cpuUsageOverload alarm.
Description
The processor on the CICC is in CPU usage overload.
Default severity
Minor
Alarm type
qualityofServiceAlarm
Root cause
The threshold for CPU usage overload of the processor on the CICC is exceeded.
System impact
Reduced throughput on the CICC. System audits will be inhibited.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-65
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_criticalSoftwareFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_criticalSoftwareFailure
alarm.
Description
A critical software failure has occurred.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Possible causes may be:
• A critical problem, possibly caused by a software or hardware failure, is detected
by the TPU application.
• Process failure on a remote CICC. Probably the remote CICC performs a reset.
Underlying service Data Management Framework (DMF) unavailable caused by
software or hardware failure.
System impact
Evaluate the system impact from the depending “context failure” alarms raised by
BSC:
• Active CICC failure: all calls are dropped
• Standby CICC failure: no impact
...................................................................................................................................................................................................................................
16-66 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance CICCProc_criticalSoftwareFailure
procedures
1 At the OMC-UPS, clear any other alarm that has been reported for the same CICC
object.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 If the fault is reported periodically by the same CICC, at the OMC-UPS, lock the
CICC object.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-67
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_heartbeatFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_heartbeatFailure alarm.
Description
This fault is raised when a TPU platform heartbeat module has trouble communicating
with either peer instances or the local application.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Process failure on a remote CICC. Possible causes are:
• The remote CICC performs a reset
• A GICC reports that it cannot communicate with a CICC
• A CCC reports that it cannot communicate with a GICC
System impact
A remote CICC probably performs a reset.
The system impact depends on the type of the remote CICC card:
• Active CICC: all calls are dropped
• Standby CICC: no impact
...................................................................................................................................................................................................................................
16-68 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance CICCProc_heartbeatFailure
procedures
1 No action required. The error will be cleared automatically after the remote CICC has
been recovered.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-69
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_memoryBlockError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_memoryBlockError alarm.
Description
This fault is raised during early indications of memory block exhaustion (Message
Block Chain of CBUFFER).
Default severity
Major
Alarm type
qualityofServiceAlarm
Root cause
High load distributed to the CICC causing memory block exhaustion.
The high load can be an indication that the RNC is at its capacity or is nearing its
capacity and requires replanning or re-engineering.
System impact
Establishment of new calls may be refused. As long as the memory block error is not
cleared, the TPU application (C-plane) does not accept new contexts/calls on that
CICC.
1 At the OMC-UPS, make sure that all CICC objects are unlocked and enabled.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-70 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance CICCProc_memoryBlockError
procedures
...................................................................................................................................................................................................
2 A network replanning may be necessary in case the capacity of the RNC is reached.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-71
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_memoryUsageOverload
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_memoryUsageOverload
alarm.
Description
The processor on the CICC is in memory usage overload.
Default severity
Major
Alarm type
qualityofServiceAlarm
Root cause
The threshold for memory usage overload of the processor on the CICC is exceeded.
System impact
Memory overload may degrade the system performance.
...................................................................................................................................................................................................................................
16-72 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_resourceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_resourceFailure alarm.
Description
A non-vital resource is unavailable or is out of service.
Default severity
Minor
Alarm type
qualityofServiceAlarm
Root cause
Underlying resource unavailable caused by software or hardware failure of the
CICCBPEtherPort.
System impact
CICC not available for call processing.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-73
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCProc_resourceFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-74 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_restoreServiceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_restoreServiceFailure
alarm.
Description
Request to restore service of the Common Intelligent Carrier Card (CICC) Processor
has failed.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Maintenance action could not be performed due to underlying software failure.
System impact
CICC processor not available.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-75
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCProc_restoreServiceFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-76 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_softwareAssertError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_softwareAssertError
alarm.
Description
A software assertion error has occurred.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
An invalid condition is detected by the TPU application.
System impact
Evaluate the system impact from the depending “context failure” alarms raised by
BSC:
• Active CICC failure: all calls are dropped
• Standby CICC failure: no impact
• Calls related to the Node B contexts (NBAP/ALCAP stacks) or cell contexts
(common control channels) hosted on that card are dropped.
1 At the OMC-UPS, perform a reset of the CICC object to reboot the CICC.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-77
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCProc_softwareAssertError
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-78 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_softwareVersionMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_softwareVersionMismatch
alarm.
Description
The software version running on this processor does not match the provisioned
software version.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
A software installation failed or has not initiated.
System impact
Processor may not initialize properly.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-79
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCProc_softwareVersionMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-80 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_standbyMateDown
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_standbyMateDown alarm.
Description
The associated Common Intelligent Carrier Card (CICC) standby mate processor is
unavailable.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Optical ATM link failure or ether fabric failure.
System impact
No redundant CICC processor available.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-81
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCProc_standbyMateDown
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-82 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_switchover
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_switchover alarm.
Description
A switchover of the SS7 stack has occurred from the active Signaling Processor on the
CICC in the FBP shelf to the standby Signaling Processor on the CICC in the other
FBP shelf..
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
The standby Signaling Processor detected that the active Signaling Processor has failed
and a switchover was triggered.
System impact
When the switchover to the standby Signaling Processor occurs, all calls are dropped.
When the switchover is completed, calls can be established again.
If the failing Signaling Processor remains disabled after the failure, standby Signaling
Processor is no longer available.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-83
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCProc_switchover
procedures
1 At the OMC-UPS, check whether the switchover was successful and SS7 stack is
started on the new Signaling Processor. Check whether calls can be established again.
...................................................................................................................................................................................................
2 At the OMC-UPS, check the state of the Signaling Processor that failed:
If ... then ..
The state is unlocked and 1. the Signaling Processor that failed has
enabled, recovered successfully
2. the procedure is completed.
The state is NOT unlocked and replace the CICC that hosts the Signaling
enabled, Processor:
1. At the OMC-UPS, lock the CICC object
2. At the RNC, replace the CICC.
3. At the OMC-UPS, reset the CICC object
4. At the OMC-UPS, unlock the CICC object
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-84 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
CICCProc_vitalResourceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the CICCProc_vitalResourceFailure
alarm.
Description
A vital resource is unavailable or is out of service.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
An underlying vital resource is unavailable caused by software or hardware failure of
the CICCBPEtherPort.
System impact
The CICC is not available for call processing.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-85
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance CICCProc_vitalResourceFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-86 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
Cabinet alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the RNC Cabinet
Contents
Cabinet_fanOrCktBreakerFailure 16-88
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-87
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
Cabinet_fanOrCktBreakerFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the Cabinet_fanOrCktBreakerFailure
alarm.
Description
A fan or circuit breaker failure has occurred.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Configuration problem.
System impact
Heating and/or power problems.
1 At the RNC, verify cabinet power breakers and fans are operating.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
16-88 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
EDCH alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the EDCH alarms.
Contents
EDCH_configurationRequestFailed 16-90
EDCH_resourceDegradation 16-92
EDCH_resourceFailure 16-94
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-89
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
EDCH_configurationRequestFailed
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the EDCH-configurationRequestFailed
alarm.
Description
CRNC detects that it was not possible to set up E-DCH services in the cell.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
A request to configure E-DCH resources in the cell has failed. This failure can be due
to any of the following reasons:
• E-DCH functionality is switched off at the RNC level.
• NodeB does not support E-DCH services.
• RNC is unable to reserve the channelisation codes required for E-DCH downlink
channels.
• A Physical Shared Channel Reconfiguration Failure message or no response was
received from the NodeB in response to a request to configure E-DCH services.
It is recommended to delete the EDCH managed object as channelization codes could
have been allocated and they should be freed and made available for R99 calls.
System impact
E-DCH calls cannot be made on the affected cell, non E-DCH calls are still possible.
...................................................................................................................................................................................................................................
16-90 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance EDCH_configurationRequestFailed
procedures
3 The EDCH MO must be deleted and recreated for E-DCH resources to be configured
again.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-91
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
EDCH_resourceDegradation
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the EDCH-resourceDegradation alarm.
Description
A Service Impacting NBAP RSI message was received from the NodeB which
indicates that the E-DCH resources were degraded.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
A Service Impacting NBAP RSI message was received from the NodeB, which
indicates that the E-DCH resources were degraded. E-DCH calls are still possible, but
the full quota of E-DCH calls is not possible until the problem is fixed.
System impact
E-DCH calls can be made on the affected cell but the faulty equipment will restrict the
number of such calls, non E-DCH calls are still possible.
1 At the OMC-UPS, check for alarms from the NodeB, take corrective actions to resolve
hardware failures that affect the functioning of a cell.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-92 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance EDCH_resourceDegradation
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-93
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
EDCH_resourceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the EDCH-resourceFailure alarm.
Description
A hardware failure at the NodeB resulted in E-DCH failure.
Default severity
Minor
Alarm type
qualityofServiceAlarm
Root cause
A hardware failure at the NodeB, which resulted in a change in the E-DCH capability
of the cell, has been communicated to the CRNC via the Cell Information->E-DCH
Resources Information element in the Service Impacting NBAP RSI message.
System impact
E-DCH calls cannot be made on the affected cell, non E-DCH calls are still possible.
1 At the OMC-UPS, check for alarms from the NodeB, take corrective actions to resolve
hardware failures that affect the functioning of a cell.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-95
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
ESC alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Ethernet Switching Card
(ESC) alarms.
Contents
ESC_degradeGroupMemberFault 16-97
ESC_failureGroupMemberFault 16-99
ESC_lossOfPower 16-101
ESC_lossOfSanity 16-103
ESC_lostCommunication 16-105
ESC_maintenanceMode 16-107
ESC_notInstalled 16-108
ESC_overTemperature 16-110
ESCProc_softwareVersionMismatch 16-112
...................................................................................................................................................................................................................................
16-96 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ESC_degradeGroupMemberFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESC_degradeGroupMemberFault
alarm.
Description
A member of the Ethernet Switching Card (ESC) degrade group failed.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
A member of a degrade group faulted (operationalState Disabled and
availabilityStatus Failed). This causes the ESC to go degraded (operationalState
Enabled and availabilityStatus Degraded).
The members of the ESC degrade group are:
• All backplane Ethernet ports (ESCBPEtherPort)
• All front access Ethernet ports (ESCFAEtherPort)
System impact
The ESC is considered degraded.
The system impact depends on the rootcause of the alarm.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-97
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ESC_degradeGroupMemberFault
procedures
....................................................................................................................................................................................................................................
16-98 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ESC_failureGroupMemberFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESC_failureGroupMemberFault
alarm.
Description
A member of the Ethernet Switching Card (ESC) failure group failed.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
A member of a failure group faulted (operationalState Disabled and
availabilityStatus Failed). This causes the ESC to fail (operationalState Disabled
and availabilityStatus Failed).
The member of the ESC failure group is:
• The ESC processor (ESCProc)
System impact
The ESC is not operational.
The system impact depends on the rootcause of the alarm.
....................................................................................................................................................................................................................................
16-100 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ESC_lossOfPower
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESC_lossOfPower alarm.
Description
The Ethernet Switching Card (ESC) has lost power.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
No power available at ESC.
System impact
This ESC can provide internal and external ethernet connectivity. The redundant ESC
will take over the switching tasks.
1 At the RNC, check whether the ESC is inserted into correct slot and powered on.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the RNC, if the ESC is inserted in the correct slot, remove and re-insert the ESC.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-101
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ESC_lossOfPower
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-102 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ESC_lossOfSanity
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESC_lossOfSanity alarm.
Description
The Ethernet Switch Card (ESC) lost sanity or integrity.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
The Alarm Card did not detect a board healthy signal from the ESC.
System impact
None, the redundant ESC will take over the switching tasks.
2 At the RNC, check whether the ESC is inserted into correct slot and powered on.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-104 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ESC_lostCommunication
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESC_lostCommunication alarm.
Description
The Alarm Card (AC) lost heartbeat communication to the Ethernet Switching Card
(ESC).
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Equipment problem.
System impact
None
1 At the RNC, check whether the ESC is inserted into correct slot and powered on.
If the alarm is cleared, the procedure is completed..
...................................................................................................................................................................................................
2 At the RNC, if the ESC is inserted in the correct slot, remove and re-insert the ESC.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-105
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ESC_lostCommunication
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-106 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ESC_maintenanceMode
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESC_maintenanceMode alarm.
Description
The Ethernet Switching Card (ESC) is in maintenance mode.
Default severity
Warning
Alarm type
processingErrorAlarm
Root cause
Configuration problem.
System impact
Alarm Card recovery for the ESC is inhibited.
1 At the RNC, use the local maintenance terminal to put the ESC back into active mode.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-107
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
ESC_notInstalled
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESC_notInstalled alarm.
Description
The Ethernet Switching Card (ESC) is not properly installed in the shelf slot.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
The specified ESC is physically removed from the shelf or is not correctly inserted and
the Alarm Card does not detect the ESC.
System impact
None, the other ESC takes over.
1 At the RNC, if the ESC is not inserted, insert the ESC into the correct slot.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the RNC, if the ESC is inserted in the correct slot, remove and re-insert the ESC.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-108 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance ESC_notInstalled
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-109
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
ESC_overTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESC_overTemperature alarm.
Description
The temperature is above the specified limit.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-110 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance ESC_overTemperature
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly by replacing
the card.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-111
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
ESCProc_softwareVersionMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESCProc_softwareVersionMismatch
alarm.
Description
The software version running on this processor does not match the provisioned
software version.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
A software installation failed or has not initiated.
System impact
Processor may not initialize properly.
...................................................................................................................................................................................................................................
16-112 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance ESCProc_softwareVersionMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-113
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
ESCBPEtherPort alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Ethernet Switching Card
BackPlane Ethernet port alarms.
Contents
ESCBPEtherPort_linkFailure 16-115
...................................................................................................................................................................................................................................
16-114 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ESCBPEtherPort_linkFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESCBPEtherPort_linkFailure alarm.
Description
A failure occurred on the backplane ethernet link connection.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Backplane ethernet connection failure
System impact
None, the other ESC takes over.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-115
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ESCBPEtherPort_linkFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-116 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ESCFAEtherPort alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Ethernet Switching Card
Front Access Ethernet port alarms.
Contents
ESCFAEtherPort_linkFailure 16-118
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-117
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
ESCFAEtherPort_linkFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESCFAEtherPort_linkFailure alarm.
Description
A failure occurred on the frontplate Ethernet link connection.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Frontplane Ethernet connection failure
System impact
Communication over the Ethernet link connections fails.
1 At the RNC, check the physical Ethernet link connection on the frontplate.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
16-118 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance ESCFAEtherPort_linkFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-119
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
ESCProc alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Ethernet Switching Card
processor alarms.
Contents
ESCProc_communicationFailure 16-121
...................................................................................................................................................................................................................................
16-120 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ESCProc_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ESCProc_communicationFailure
alarm.
Description
Communication to the Ethernet Switch Card (ESC) processor has failed.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
No SNMP communication between the SB and ESC.
System impact
No internal and external ethernet connectivity is provided by the ESC.
1 At the OMC-UPS, if the ESC is initializing, ensure that the ESC restores successfully.
If the alarm is cleared, procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-122 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the External Alarm Box.
Contents
ExtAlmBox_communicationFailure 16-125
ExtAlmBox_externalAlarmPort1 16-127
ExtAlmBox_externalAlarmPort10 16-129
ExtAlmBox_externalAlarmPort11 16-131
ExtAlmBox_externalAlarmPort12 16-133
ExtAlmBox_externalAlarmPort13 16-135
ExtAlmBox_externalAlarmPort14 16-137
ExtAlmBox_externalAlarmPort15 16-139
ExtAlmBox_externalAlarmPort16 16-141
ExtAlmBox_externalAlarmPort17 16-143
ExtAlmBox_externalAlarmPort18 16-145
ExtAlmBox_externalAlarmPort19 16-147
ExtAlmBox_externalAlarmPort2 16-149
ExtAlmBox_externalAlarmPort20 16-151
ExtAlmBox_externalAlarmPort21 16-153
ExtAlmBox_externalAlarmPort22 16-155
ExtAlmBox_externalAlarmPort23 16-157
ExtAlmBox_externalAlarmPort24 16-159
ExtAlmBox_externalAlarmPort25 16-161
ExtAlmBox_externalAlarmPort26 16-163
ExtAlmBox_externalAlarmPort27 16-165
ExtAlmBox_externalAlarmPort28 16-167
ExtAlmBox_externalAlarmPort29 16-169
ExtAlmBox_externalAlarmPort3 16-171
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-123
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance Overview
procedures
ExtAlmBox_externalAlarmPort30 16-173
ExtAlmBox_externalAlarmPort31 16-175
ExtAlmBox_externalAlarmPort32 16-177
ExtAlmBox_externalAlarmPort4 16-179
ExtAlmBox_externalAlarmPort5 16-181
ExtAlmBox_externalAlarmPort6 16-183
ExtAlmBox_externalAlarmPort7 16-185
ExtAlmBox_externalAlarmPort8 16-187
ExtAlmBox_externalAlarmPort9 16-189
....................................................................................................................................................................................................................................
16-124 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_communicationFailure
alarm.
Description
A communication failure to the External Alarm Box has occurred.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Connectivity is lost between the RNC and the External Alarm Box.
System impact
No alarms from the External Alarm Box will be reported to the OMC-UPS.
1 At the RNC, make sure that the connection between the RNC and the External Alarm
Box is OK.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-125
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_communicationFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-126 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort1
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort1
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 1.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-127
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort1
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-128 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort10
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort10
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 10.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-129
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort10
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-130 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort11
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort11
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 11.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-131
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort11
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-132 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort12
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort12
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 12.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-133
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort12
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-134 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort13
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort13
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 13.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-135
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort13
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-136 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort14
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort14
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 14.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-137
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort14
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-138 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort15
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort15
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 15.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-139
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort15
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-140 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort16
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort16
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 16.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-141
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort16
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-142 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort17
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort17
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 17.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-143
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort17
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-144 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort18
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort18
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 18.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-145
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort18
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-146 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort19
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort19
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 19.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-147
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort19
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-148 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort2
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort2
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 2.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-149
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort2
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-150 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort20
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort20
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 20.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-151
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort20
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-152 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort21
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort21
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 21.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-153
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort21
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-154 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort22
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort22
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 22.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-155
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort22
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-156 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort23
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort23
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 23.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-157
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort23
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-158 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort24
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort24
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 24.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-159
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort24
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-160 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort25
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort25
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 25.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-161
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort25
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-162 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort26
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort26
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 26.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-163
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort26
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-164 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort27
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort27
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 27.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-165
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort27
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-166 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort28
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort28
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 28.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-167
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort28
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-168 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort29
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort29
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 29.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-169
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort29
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-170 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort3
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort3
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 3.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-171
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort3
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-172 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort30
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort30
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 30.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-173
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort30
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-174 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort31
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort31
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 31.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-175
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort31
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-176 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort32
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort32
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 32.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-177
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort32
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-178 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort4
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort4
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 4.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-179
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort4
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-180 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort5
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort5
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 5.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-181
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort5
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-182 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort6
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort6
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 6.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-183
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort6
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-184 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort7
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort7
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 7.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-185
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort7
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-186 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort8
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort8
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 8.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-187
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort8
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-188 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
ExtAlmBox_externalAlarmPort9
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the ExtAlmBox_externalAlarmPort9
alarm.
Description
The condition that is monitored using this external alarm port is active.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
This alarm was triggered by the external equipment connected to External Alarm Box
(EAB) port 9.
System impact
Dependent on the external equipment connected to the port.
1 Request a service technician to take action. The action depends upon the site-specific
configuration and the external equipment that is connected to the external alarm port.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-189
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance ExtAlmBox_externalAlarmPort9
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-190 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
FBPShelf alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the FBP shelf alarms.
Contents
FBPShelf_overTemperature 16-192
FBPShelf_overTemperatureSensor1 16-194
FBPShelf_overTemperatureSensor2 16-196
FBPShelf_overTemperatureSensor3 16-198
FBPShelf_overTemperatureSensor4 16-200
FBPShelf_overTemperatureSensor5 16-202
FBPShelf_overTemperatureSensor6 16-204
FBPShelf_overTemperatureSensor7 16-206
FBPShelf_overTemperatureSensor8 16-208
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-191
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
FBPShelf_overTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FBPShelf_overTemperature alarm.
Description
The temperature is above the specified limit.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated overTemperature alarms on any
individual cards using the appropriate clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-192 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance FBPShelf_overTemperature
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
5 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
6 At the RNC, verify that the temperature sensors are functioning correctly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-193
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
FBPShelf_overTemperatureSensor1
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FBPShelf_overTemperatureSensor1
alarm.
Description
The temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-194 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance FBPShelf_overTemperatureSensor1
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-195
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
FBPShelf_overTemperatureSensor2
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FBPShelf_overTemperatureSensor2
alarm.
Description
The temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-196 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance FBPShelf_overTemperatureSensor2
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-197
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
FBPShelf_overTemperatureSensor3
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FBPShelf_overTemperatureSensor3
alarm.
Description
The temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-198 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance FBPShelf_overTemperatureSensor3
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-199
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
FBPShelf_overTemperatureSensor4
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FBPShelf_overTemperatureSensor4
alarm.
Description
The temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-200 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance FBPShelf_overTemperatureSensor4
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-201
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
FBPShelf_overTemperatureSensor5
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FBPShelf_overTemperatureSensor5
alarm.
Description
The temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-202 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance FBPShelf_overTemperatureSensor5
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-203
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
FBPShelf_overTemperatureSensor6
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FBPShelf_overTemperatureSensor6
alarm.
Description
The temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-204 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance FBPShelf_overTemperatureSensor6
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-205
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
FBPShelf_overTemperatureSensor7
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FBPShelf_overTemperatureSensor7
alarm.
Description
The temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-206 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance FBPShelf_overTemperatureSensor7
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-207
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
FBPShelf_overTemperatureSensor8
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FBPShelf_overTemperatureSensor8
alarm.
Description
The temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-208 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance FBPShelf_overTemperatureSensor8
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-209
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
FanTray alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the FanTray unit.
Contents
FanTray_fan1Failure 16-211
FanTray_fan2Failure 16-213
FanTray_fan3Failure 16-215
FanTray_notInstalled 16-217
...................................................................................................................................................................................................................................
16-210 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
FanTray_fan1Failure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FanTray_fan1Failure alarm.
Description
The fan 1 is not functioning properly. The fan is not rotating or is not rotating at the
proper speed.
Default severity
1 is not rotating at the proper speed.
Alarm type
Alarm type is unknown.
Root cause
Possible root causes are:
• Objects blocking the rotation of the fan
• Fan defect.
System impact
No or insufficient cooling facilities available. This can lead to hardware failures
because of high temperatures.
2 At the RNC, inspect the fan tray and remove any object that obstruct the rotation of
the fan.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-211
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance FanTray_fan1Failure
procedures
....................................................................................................................................................................................................................................
16-212 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
FanTray_fan2Failure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FanTray_fan2Failure alarm.
Description
The fan 2 is not functioning properly. The fan is not rotating or is not rotating at the
proper speed.
Default severity
2 is not rotating at the proper speed.
Alarm type
Alarm type is unknown.
Root cause
Possible root causes are:
• Objects blocking the rotation of the fan
• Fan defect.
System impact
No or insufficient cooling facilities available. This can lead to hardware failures
because of high temperatures.
2 At the RNC, inspect the fan tray and remove any object that obstruct the rotation of
the fan.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-213
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance FanTray_fan2Failure
procedures
....................................................................................................................................................................................................................................
16-214 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
FanTray_fan3Failure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FanTray_fan3Failure alarm.
Description
The fan 3 is not functioning properly. The fan is not rotating or is not rotating at the
proper speed.
Default severity
3 is not rotating at the proper speed.
Alarm type
Alarm type is unknown.
Root cause
Possible root causes are:
• Objects blocking the rotation of the fan
• Fan defect.
System impact
No or insufficient cooling facilities available. This can lead to hardware failures
because of high temperatures.
2 At the RNC, inspect the fan tray and remove any object that obstruct the rotation of
the fan.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-215
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance FanTray_fan3Failure
procedures
....................................................................................................................................................................................................................................
16-216 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
FanTray_notInstalled
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the FanTray_notInstalled alarm.
Description
The fan tray is not installed.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Fan tray not installed
System impact
No cooling facilities available
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-217
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICC alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Gateway Intelligent
Carrier Card (GICC).
Contents
GICC_degradeGroupMemberFault 16-219
GICC_escalatingRecovery 16-221
GICC_failureGroupMemberFault 16-223
GICC_lossOfPower 16-225
GICC_lossOfSanity 16-227
GICC_lostCommunication 16-229
GICC_maintenanceMode 16-231
GICC_notInstalled 16-232
GICC_overTemperature 16-234
GICC_overTemperatureInFlow 16-236
GICC_overTemperatureOutFlow 16-238
...................................................................................................................................................................................................................................
16-218 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICC_degradeGroupMemberFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICC_degradeGroupMemberFault
alarm.
Description
A member of the Gateway Intelligent Carrier Card (GICC) degrade group failed.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
A member of a degrade group faulted (operationalState Disabled and
availabilityStatus Failed). This causes the GICC to go degraded (operationalState
Enabled and availabilityStatus Degraded).
The members of the GICC degrade group are:
• All STM1/OC3 ports (GICCSTM1OC3Port)
• All backplane Ethernet ports (GICCBPEtherPort)
• All front access Ethernet ports (GICCFAEtherPort)
System impact
The GICC is considered degraded.
The system impact depends on the rootcause of the alarm.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-219
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICC_degradeGroupMemberFault
procedures
....................................................................................................................................................................................................................................
16-220 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICC_escalatingRecovery
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICC_escalatingRecovery alarm.
Description
The system is escalating recovery of the Gateway Intelligent Carrier Card (GICC) and
may have exhausted attempts to recover the unit,
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
The GICC is not responding to recovery due to software or hardware failure
System impact
None. The other GICC will take over
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-221
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICC_escalatingRecovery
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-222 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICC_failureGroupMemberFault
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICC_failureGroupMemberFault
alarm.
Description
A member of the Gateway Intelligent Carrier Card (GICC) failure group failed.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
A member of a failure group faulted (operationalState Disabled and
availabilityStatus Failed). This causes the GICC to fail (operationalState Disabled
and availabilityStatus Failed).
The member of the GICC failure group is:
• The GICC processor (GICCProc)
System impact
The GICC is not operational.
The system impact depends on the rootcause of the alarm.
....................................................................................................................................................................................................................................
16-224 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICC_lossOfPower
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICC_lossOfPower alarm.
Description
The Gateway Intelligent Carrier Card (GICC) has lost power.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Equipment problem
System impact
None.
2 At the RNC, check whether the GICC is inserted into correct slot and powered on.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-225
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICC_lossOfPower
procedures
...................................................................................................................................................................................................
3 At the RNC, if the GICC is inserted in the correct slot, remove and re-insert the GICC.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-226 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICC_lossOfSanity
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedures for clearing the GICC_lossOfSanity alarm.
Description
The Gateway Inteligent Carrier Card (GICC) lost sanity or integrity.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
The Alarm Card did not detect a board healthy signal from the GICC.
System impact
None.
2 At the RNC, check whether the GICC is inserted into correct slot and powered on.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-228 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICC_lostCommunication
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICC_lostCommunication alarm.
Description
Alarm Card (AC) lost heartbeat communication to the Gateway Intelligent Carrier Card
(GICC).
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Equipment problem.
System impact
The GICC may operate but will likely not respond to some OA&M commands,
especially those entered through the CLI.
1 At the RNC, check whether the GICC is inserted into correct slot and powered on.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the RNC, if the GICC is inserted in the correct slot, remove and re-insert the GICC.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-229
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICC_lostCommunication
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-230 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICC_maintenanceMode
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICC_maintenanceMode alarm.
Description
The Gateway Intelligent Carrier Card (GICC) is in maintenance mode.
Default severity
Warning
Alarm type
processingErrorAlarm
Root cause
Configuration problem.
System impact
Alarm Card recovery for this GICC is inhibited.
1 At the RNC, use the maintenance terminal to put the GICC back into active mode.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-231
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICC_notInstalled
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICC_notInstalled alarm.
Description
Gateway Intelligent Carrier Card is not properly installed in shelf slot.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
The specified GICC is physically removed from the shelf or is not correctly inserted
and the Alarm Card does not detect the GICC.
System impact
None.
1 At the RNC, if the GICC is not inserted, insert the GICC into the correct slot.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the RNC, if the GICC is inserted in the correct slot, remove and re-insert the GICC.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-232 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICC_notInstalled
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-233
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICC_overTemperature
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICC_overTemperature alarm.
Description
The temperature is above the specified limit.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-234 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICC_overTemperature
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly by replacing
the card.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-235
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICC_overTemperatureInFlow
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICC_overTemperatureInFlow
alarm.
Description
The inflow temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-236 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICC_overTemperatureInFlow
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly by replacing
the card.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-237
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICC_overTemperatureOutFlow
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICC_overTemperatureOutFlow
alarm.
Description
The outflow temperature is above the specified limit.
Default severity
Critical
Alarm type
environmentalAlarm
Root cause
Possible causes are:
• Defective circuit boards
• Airflow obstruction or diversion
• Fan or temperature sensor failure.
System impact
Increase in cabinet temperature could lead to possible component failure.
1 At the OMC-UPS, check for and clear any associated fan alarms using the appropriate
clearance procedures
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-238 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICC_overTemperatureOutFlow
procedures
...................................................................................................................................................................................................
3 At the RNC, check if the Rear Transition Module (RTM) is correctly installed.
...................................................................................................................................................................................................
4 At the RNC, check if any empty card slots have missing or incorrectly installed filler
plates.
...................................................................................................................................................................................................
5 At the RNC, verify that the temperature sensors are functioning correctly by replacing
the card.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-239
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCBPEtherPort alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the GICC backplane Ethernet
port alarms.
Contents
GICCBPEtherPort_communicationFailureESC1_2 16-241
GICCBPEtherPort_communicationFailureESC1_21 16-243
GICCBPEtherPort_communicationFailureESC2_2 16-245
GICCBPEtherPort_communicationFailureESC2_21 16-247
GICCBPEtherPort_linkFailure 16-249
GICCBPEtherPort_restoreServiceFailure 16-251
...................................................................................................................................................................................................................................
16-240 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCBPEtherPort_communicationFailureESC1_2
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCBPEtherPort_communication-
FailureESC1_2 alarm.
Description
Ethernet communication to shelf 1, ESC 2 has failed.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• ESC hardware failure
• GICC hardware failure
• Cable failures.
System impact
No direct impact, the alternate fabric is used to provide Ethernet communication.
However the card is now vulnerable.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-241
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCBPEtherPort_communicationFailureESC1_2
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-242 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCBPEtherPort_communicationFailureESC1_21
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCBPEtherPort_communication-
FailureESC1_21 alarm.
Description
Ethernet communication to shelf 1, ESC 21 has failed.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• ESC hardware failure
• GICC hardware failure
• Cable failures.
System impact
No direct impact, the alternate fabric is used to provide Ethernet communication.
However the card is now vulnerable.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-243
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCBPEtherPort_communicationFailureESC1_21
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-244 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCBPEtherPort_communicationFailureESC2_2
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCBPEtherPort_communication-
FailureESC2_2 alarm.
Description
Ethernet communication to shelf 2, ESC 2 has failed.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• ESC hardware failure
• GICC hardware failure
• Cable failures.
System impact
No direct impact, the alternate fabric is used to provide Ethernet communication.
However the card is now vulnerable.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-245
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCBPEtherPort_communicationFailureESC2_2
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-246 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCBPEtherPort_communicationFailureESC2_21
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCBPEtherPort_communication-
FailureESC2_21 alarm.
Description
Ethernet communication to shelf 2, ESC 21 has failed.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• ESC hardware failure
• GICC hardware failure
• Cable failures.
System impact
No direct impact, the alternate fabric is used to provide Ethernet communication.
However the card is now vulnerable.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-247
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCBPEtherPort_communicationFailureESC2_21
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-248 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCBPEtherPort_linkFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCBPEtherPort_linkFailure alarm.
Description
A failure occurred on the backplane ethernet link connection.
Important! This alarm must be cleared manually.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Ethernet link connection failure
System impact
No communication with GICC possible.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-249
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCBPEtherPort_linkFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-250 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCBPEtherPort_restoreServiceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCBPEtherPort_restoreSer-
viceFailure alarm.
Description
Request to restore service of the GICC Ether port has failed
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Maintenance action could not be performed due to underlying software failure.
System impact
GICC processor not available.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-252 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCFAEtherPort alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the GICC front access
Ethernet port alarms.
Contents
GICCFAEtherPort_linkFailure 16-254
GICCFAEtherPort_restoreServiceFailure 16-256
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-253
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCFAEtherPort_linkFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCFAEtherPort_linkFailure alarm.
Description
A failure occurred on the front access ethernet link connection.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
Ethernet link connection failure
System impact
No communication with GICC possible.
...................................................................................................................................................................................................................................
16-254 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICCFAEtherPort_linkFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-255
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCFAEtherPort_restoreServiceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCFAEtherPort_restoreSer-
viceFailure alarm.
Description
Request to restore service of the GICC front access Ethernet port has failed.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Maintenance action could not be performed due to underlying software failure.
System impact
GICC processor not available.
...................................................................................................................................................................................................................................
16-256 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICCFAEtherPort_restoreServiceFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-257
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCProc alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the GICCProc.
Contents
GICCProc_allOpticalLinksFailed 16-259
GICCProc_communicationFailure 16-261
GICCProc_communicationFailureLRM 16-263
GICCProc_configurationError 16-265
GICCProc_cpuUsageOverload 16-266
GICCProc_criticalSoftwareFailure 16-267
GICCProc_heartbeatFailure 16-269
GICCProc_memoryBlockError 16-271
GICCProc_memoryUsageOverload 16-273
GICCProc_resourceFailure 16-274
GICCProc_restoreServiceFailure 16-276
GICCProc_softwareAssertError 16-278
GICCProc_softwareVersionMismatch 16-280
GICCProc_standbyMateDown 16-282
GICCProc_vitalResourceFailure 16-284
...................................................................................................................................................................................................................................
16-258 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_allOpticalLinksFailed
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_allOpticalLinksFailed
alarm.
Description
All STM1/OC3 optical links on a GICC have failed.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Possible network configuration problem, physical link failure, or the GICC has been
locked
System impact
No reduncancy is available for the optical links assigned to the GICC. Any optical link
failure on the mated GICC will result in complete loss of communication for that link
1 At the OMC-UPS, check for alarms on individual optical links and perform the
appropriate procedures to clear them.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-259
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCProc_allOpticalLinksFailed
procedures
...................................................................................................................................................................................................
2 If there are no optical link failure alarms, but the GICC has been manually locked,
unlock the GICC object.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-260 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_communicationFailure
alarm.
Description
Communication to the Gateway Intelligent Carrier Card (GICC) processor has failed.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
No SNMP communication between the SB and GICC.
System impact
GICC is not available.
1 At the OMC-UPS, if the GICC is initializing, ensure that the GICC restores
successfully.
If the alarm is cleared, procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-261
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCProc_communicationFailure
procedures
...................................................................................................................................................................................................
4 At the OMC-UPS, check if there are ESC alarms and correct ESC failures.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-262 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_communicationFailureLRM
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_communicationFail-
ureLRM alarm.
Description
Communication from FMS host processor to LRM on the GICC processor has failed.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• Faulty hardware.
• Bad software image.
• Incorrect board installed.
• An initialization is in progress.
System impact
GICC processor is unavailable for use by call processing.
1 If the alarm has not cleared within 15 minutes, check if other boards of the same type
have successfully booted, if not, verify correct software is installed successfully.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-263
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCProc_communicationFailureLRM
procedures
...................................................................................................................................................................................................
3 At the RNC, replace the board if it has previously been inservice or verify the correct
board was installed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-264 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_configurationError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_configurationError alarm.
Description
An error was found in the configuration data used by this processor.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
The data was either populated incorrectly initially, or a data change was made that
introduced the error.
System impact
Call processing may be affected.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-265
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_cpuUsageOverload
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_cpuUsageOverload alarm.
Description
The processor on the GICC is in CPU usage overload.
Default severity
Minor
Alarm type
qualityofServiceAlarm
Root cause
The threshold for CPU usage overload of the processor on the GICC is exceeded.
System impact
Reduced throughput on the GICC. System audits will be inhibited.
...................................................................................................................................................................................................................................
16-266 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_criticalSoftwareFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_criticalSoftwareFailure
alarm.
Description
A critical software failure has occurred.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Possible causes may be:
• A critical problem, possibly caused by a software or hardware failure, is detected
by the TPU application
System impact
The GICC is not available. Some calls may be dropped. Network elements may be
dropped and then recovered after a switch to the standby GICC or the recovery of the
active GICC.
1 At the OMC-UPS, clear any other alarm that has been reported for the same GICC
object
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-267
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCProc_criticalSoftwareFailure
procedures
2 If the fault is reported periodically by the same GICC, at the OMC-UPS, lock the
GICC object.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-268 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_heartbeatFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_heartbeatFailure alarm.
Description
This fault is raised when a TPU platform heartbeat module has trouble communicating
with either peer instances or the local application.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Process failure on a remote GICC card. Possible causes are:
• The remote GICC card performs a reset
• A GICC reports that it cannot communicate with a CICC
• A CICC reports that it cannot communicate with a GICC.
System impact
A remote GICC card probably performs a reset.
1 No action required. The error will be cleared automatically after the remote GICC has
been recovered.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-269
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCProc_heartbeatFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-270 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_memoryBlockError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_memoryBlockError
alarm.
Description
Possible indications of high Message Block Chain (MBC) memory loading are
occurring.
Default severity
Major
Alarm type
qualityofServiceAlarm
Root cause
High load distributed to the GICC causing high Message Block Chain memory load.
The high load can be an indication that the RNC is at its capacity or is nearing its
capacity and requires replanning or re-engineering.
System impact
Establishment of new calls may be refused. As long as the memory block error is not
cleared, the TPU application (C-plane) does not accept new contexts/calls on that
GICC.
1 At the OMC-UPS, make sure that all GICC cards are unlocked and enabled.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-271
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCProc_memoryBlockError
procedures
...................................................................................................................................................................................................
2 A network replanning may be necessary in case the capacity of the RNC is reached.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-272 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_memoryUsageOverload
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_memoryUsageOverload
alarm.
Description
The processor on the GICC is in memory usage overload.
Default severity
Major
Alarm type
qualityofServiceAlarm
Root cause
The threshold for memory usage overload of the processor on the GICC is exceeded.
System impact
Memory overload may degrade the system performance.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-273
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_resourceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_resourceFailure alarm.
Description
A non-vital resource is unavailable or has been lost.
Default severity
Minor
Alarm type
qualityofServiceAlarm
Root cause
Probable causes are
• Underlying resource (GICCBPEthePort) unavailable caused by software or
hardware failure.
• Underlying service Data Management Framework (DMF) unavailable caused by
software or hardware failure.
System impact
GICC not available for call processing.
...................................................................................................................................................................................................................................
16-274 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICCProc_resourceFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-275
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_restoreServiceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_restoreServiceFailure
alarm.
Description
Request to restore service of the Gateway Intelligent Carrier Card (GICC) Processor
has failed
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Maintenance action could not be performed due to underlying software failure.
System impact
GICC processor not available.
...................................................................................................................................................................................................................................
16-276 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICCProc_restoreServiceFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-277
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_softwareAssertError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_softwareAssertError
alarm.
Description
A software assertion error has occurred.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
An invalid condition is detected by the TPU application.
System impact
The GICC is not available. Some calls may be dropped. Network elements may be
dropped and then recovered after a switch to the standby GICC or the recovery of the
active GICC.
1 At the OMC-UPS, perform a reset of the GICC object to reboot the GICC.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
16-278 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICCProc_softwareAssertError
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-279
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_softwareVersionMismatch
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_softwareVersionMismatch
alarm.
Description
The software version running on this processor does not match the provisioned
software version.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
A software installation failed or has not initiated.
System impact
Processor may not initialize properly.
...................................................................................................................................................................................................................................
16-280 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICCProc_softwareVersionMismatch
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-281
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_standbyMateDown
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_standbyMateDown alarm.
Description
Standby services on the associated mate Gateway Intelligent Carrier Card (GICC) may
be unavailable or degraded.
This alarm indicates that one of three conditions likely occurred:
1. All optical links on the mated GICC are failed or unavailable.
An indication that this may have occurred would be individual alarms on each of
the 4 OC3 ports on the other GICC, as well as an ’allOpticalLinksFailed’ alarm on
the other GICCProc.
2. The processor or card itself on the associated mated GICC may have failed.
An indication that this may have occurred would be one or more alarms on the
other GICC or GICCProc.
3. The GICCProc upon which this alarm was raised has lost communication with it’s
associated mated GICCProc. The other GICCProc may be fully operational or
failed in this case, however since the local GICCProc cannot heartbeat with it’s
standby mate GICCProc this alarm will be raised.
If no individual alarms are seen on the associated mate GICC or GICCProc then
this may be a communication problem and the standby services may very well be
still available, though it is highly advisable to troubleshoot this issue to the point
where this alarm becomes cleared.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Optical ATM link failure or ethernet fabric failure.
System impact
No redundant GICC processor available.
1 At the OMC-UPS, check the status of the OC3 ports on the associated mate GICC. If
all 4 OC3 ports are alarmed and / or failed then this ’standbyMateDown’ will be raised
on the local GICCProc. Check also for an ’allOpticalLinksFailed’ alarm on the mated
GICCProc. This can also cause the current alarm This implies that no standby OC3
ports are available if one of the local ports fail.
Check the PSAX and network to see if the port failure is external. If no external cause
can be found proceed to step 2.
...................................................................................................................................................................................................
2 At the OMC-UPS, check the status of the associated mate GICC processor and the
mate GICC board itself. Also check if the mated GICC is locked. Check for alarms or
states that indicate problems with the board or processor and replace if necessary. If no
problem can be found on the mate board or processor proceed to step 3.
...................................................................................................................................................................................................
3 At the OMC-UPS, check the status of local RNC communications, - e.g. look for ESC
and EthernetPort alarms that might effect GICC communications. If no local
communications problem can be found proceed to step 4.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-283
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCProc_vitalResourceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCProc_vitalResourceFailure
alarm.
Description
A vital resource is unavailable or is out of service.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Probable causes are:
• Underlying resource (GICCBPEthePort) unavailable caused by software or
hardware failure.
• Underlying service Data Management Framework (DMF) unavailable caused by
software or hardware failure.
System impact
GICC not available for call processing. Calls hosted on the card or context that are
hosted on that card are dropped.
...................................................................................................................................................................................................................................
16-284 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance GICCProc_vitalResourceFailure
procedures
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-285
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the GICC STM1/OC3 port.
Contents
GICCSTM1OC3Port_linkFailure 16-287
GICCSTM1OC3Port_linkFailureAIS_L 16-289
GICCSTM1OC3Port_linkFailureAIS_P 16-291
GICCSTM1OC3Port_linkFailureLCD_P 16-293
GICCSTM1OC3Port_linkFailureLOF 16-295
GICCSTM1OC3Port_linkFailureLOP_P 16-297
GICCSTM1OC3Port_linkFailureLOS 16-299
GICCSTM1OC3Port_linkFailurePLM_P 16-301
GICCSTM1OC3Port_linkFailureRDI_L 16-303
GICCSTM1OC3Port_linkFailureRDI_P 16-305
GICCSTM1OC3Port_restoreServiceFailure 16-307
...................................................................................................................................................................................................................................
16-286 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_linkFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCSTM1OC3Port_linkFailure
alarm.
Description
A failure has occurred on the ATM (STM1/OC3) link connection.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
ATM link connection failure
System impact
During the switch over to the standby GICC some packets may be lost. If the standby
GICC is not available the connection to the network will be lost and calls will fail.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-287
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCSTM1OC3Port_linkFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-288 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_linkFailureAIS_L
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
GICCSTM1OC3Port_linkFailureAIS_L alarm.
Description
An Alarm Indication Signal - Line (AIS-L) failure has occurred on the ATM
(STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
An AIS-L is an indication that the far end is out of service.
An AIS-L is sent by an Section Terminating Equipment (STE) to a downstream Line
Terminating Equipment (LTE) when LOS or LOF is detected on an incoming SONET
section.
System impact
During the switch over some packets may be lost. If the protection line is not
available, the connection to the network will be lost and calls will fail.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-289
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCSTM1OC3Port_linkFailureAIS_L
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-290 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_linkFailureAIS_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
GICCSTM1OC3Port_linkFailureAIS_P alarm.
Description
An Alarm Indication Signal - Path (AIS-P) failure has occurred on the ATM
(STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
An AIS-P is an indication that the far end is out of service.
An AIS-P is sent by an Line Terminating Equipment (LTE) to a downstream Path
Terminating Equipment (PTE) when an LOS or LOF is detected on a upstream
SONET section.
System impact
During the switch over some packets may be lost. If the protection line is not
available, the connection to the network will be lost and calls will fail.
Loss of communication at the remote end of the optical link.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-291
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCSTM1OC3Port_linkFailureAIS_P
procedures
2 At the far end, check the physical ATM link connection. Correct problem found at the
far end.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-292 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_linkFailureLCD_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
GICCSTM1OC3Port_linkFailureLCD_P alarm.
Description
An Loss of Cell Delineation - Path (LCD-P) failure has occurred on the ATM
(STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
The ATM cell alignment boundary in an octet stream can not be maintained.
Possible causes are:
• Physical problem with the ATM link connection.
System impact
Loss of communication.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-293
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCSTM1OC3Port_linkFailureLCD_P
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-294 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_linkFailureLOF
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCSTM1OC3Port_linkFailureLOF
alarm.
Description
An Loss Of Frame (LOF) has occurred on the ATM (STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
A signal could not be detected at the interface. The cause of the problem can be at the
RNC or at the far end of the connection. Both sides must be checked.
Probable causes are:
• The link is not plugged in
• The connector is damaged
• The fiber is damaged
• The fiber is cut.
System impact
During the switch over some packets may be lost. If the protection line is not
available, the connection to the network will be lost and calls will fail.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-295
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCSTM1OC3Port_linkFailureLOF
procedures
....................................................................................................................................................................................................................................
16-296 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_linkFailureLOP_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
GICCSTM1OC3Port_linkFailureLOP_P alarm.
Description
An Loss of Pointer Path (LOP-P) failure has occurred on the ATM (STM1/OC3) link
connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
A valid pointer on an incoming signal can not be located.
A possible provisioning problem.
System impact
Payload can not be extracted from messages.
During the switch over some packets may be lost. If the protection line is not
available, the connection to the network will be lost and calls will fail.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-298 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_linkFailureLOS
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the GICCSTM1OC3Port_linkFailureLOS
alarm.
Description
An Loss of Signal (LOS) failure has occurred on the ATM (STM1/OC3) link
connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Physical problem with the ATM link connection.
System impact
During the switch over some packets may be lost. If the protection line is not
available, the connection to the network will be lost and calls will fail.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-299
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCSTM1OC3Port_linkFailureLOS
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-300 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_linkFailurePLM_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
GICCSTM1OC3Port_linkFailurePLM_P alarm.
Description
A Payload-Label-Mismatch-Path (PLM-P) failure has occurred on the ATM
(STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
The incoming payload label does not match the expected payload label. The label is
corrupted.
System impact
During the switch over some packets may be lost. If the protection line is not
available, the connection to the network will be lost and calls will fail.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-301
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCSTM1OC3Port_linkFailurePLM_P
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-302 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_linkFailureRDI_L
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
GICCSTM1OC3Port_linkFailureRDI_L alarm.
Description
A Remote Defect Indication Line (RDI-L) failure has occurred on the ATM
(STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
A problem at the remote end of the line segment.
An RDI-L is sent upstream to a peer Line Terminating Equipment (LTE) when an
AIS-L alarm or low-level defects are detected.
System impact
The link has a problem at the remote end of the line segment.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-303
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCSTM1OC3Port_linkFailureRDI_L
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-304 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_linkFailureRDI_P
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
GICCSTM1OC3Port_linkFailureRDI_P alarm.
Description
A Remote Defect Indication Path (RDI-P) failure has occurred on the ATM
(STM1/OC3) link connection.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
An RDI-P is an indication of a problem at the remote end of the line segment.
An RDI-P is sent upstream to a peer Path Terminating Equipement (PTE) when a
defect in the signal, typically an AIS-P, is detected.
System impact
The link has a problem at the remote end of the line segment.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-305
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCSTM1OC3Port_linkFailureRDI_P
procedures
...................................................................................................................................................................................................
2 At the far end, check the physical ATM link connection. Correct problem found at the
far end.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-306 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
GICCSTM1OC3Port_restoreServiceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the
GICCSTM1OC3Port_restoreServiceFailure alarm.
Description
Request to restore service of the Gateway Intelligent Carrier Card (GICC) Processor
has failed
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Maintenance action could not be performed due to underlying software failure.
System impact
GICC processor not available.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-307
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance GICCSTM1OC3Port_restoreServiceFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-308 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
HSDPA alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for HSDPA alarms
Contents
HSDPA_degraded 16-310
HSDPA_failed 16-312
HSDPA_hSDPAOCNSchannelSetupFailure 16-314
HSDPA_notInstalled 16-316
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-309
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
HSDPA_degraded
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the HSDPA_degraded alarm.
Description
CRNC detects that the HSDPA object has transitioned to the enabled/degraded state.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
A Service Impacting NBAP RSI message was received from the NodeB which
indicates that the HSDPA resources were degraded. HSDPA calls are still possible, but
the full quota of HSDPA calls is not possible until the problem is fixed.
System impact
HSDPA calls can be made on the affected cell but the number of such calls will be
restricted by the faulty equipment, non-HSDPA calls are still possible.
1 At the OMC-UPS, check for alarms from the NodeB, take corrective actions to resolve
hardware failures, which affect the functioning of a cell.
...................................................................................................................................................................................................................................
16-310 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance HSDPA_degraded
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-311
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
HSDPA_failed
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the HSDPA_failed alarm.
Description
CRNC detects that the HSDPA object has transitioned to the disabled/failed state.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
A hardware failure at the NodeB which resulted in a change in the HSDPA capability
of the cell has been communicated to the CRNC via the Cell Information HS-DSCH
Resources Information element in the Service Impacting NBAP RSI message.
System impact
HSDPA calls cannot be made on the affected cell, non-HSDPA calls are still possible.
1 At the OMC-UPS, check for alarms from the NodeB, take corrective actions to resolve
hardware failures, which affect the functioning of a cell.
If the HSDPA fault cannot be rectified immediately, it is recommended to delete the
HSDPA managed object so that channelisation codes will be available for R99 calls.
...................................................................................................................................................................................................................................
16-312 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance HSDPA_failed
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-313
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
HSDPA_hSDPAOCNSchannelSetupFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the HSDPA_hSDPAOCNSchannelSetup-
Failure alarm.
Description
OCNS-HSDPA setup has been failed.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
HSDPA resources unavailable in the LCell.
System impact
OCNS-HSDPA service unavailable.
...................................................................................................................................................................................................................................
16-314 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance HSDPA_hSDPAOCNSchannelSetupFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-315
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
HSDPA_notInstalled
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the HSDPA_notInstalled alarm.
Description
CRNC detects that it was not possible to set up HSDPA services in the cell.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
A request to configure HSDPA resources in the cell has failed. This failure can be due
to any of the following reasons:
• HSDPA functionality is switched off at the RNC level.
The NodeB does not support HSDPA services.
• The RNC is unable to reserve the channelization codes required for HSDPA.
• A Physical Shared Channel Reconfiguration Failure message or no response was
received from the NodeB in response to a request to configure HSDPA services.
Important! It is recommended to delete the HSDPA managed object as
channelisation codes could have been allocated and they should be freed and made
available for R99 calls.
System impact
HSDPA calls cannot be made on the affected cell, non-HSDPA calls are still possible.
...................................................................................................................................................................................................................................
16-316 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance HSDPA_notInstalled
procedures
3 The HSDPA MO must be deleted and recreated for HSDPA resources to be configured
again.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-317
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuB alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Iub interface.
Contents
IuB_cellReconfigTimeout 16-319
IuB_cellSetupTimeout 16-321
IuB_channelReconfigFailure 16-323
IuB_channelReconfigTimeout 16-325
IuB_channelSetupFailure 16-327
IuB_channelSetupTimeout 16-329
IuB_highBER 16-331
IuB_nBAP_Reset_Requ_CCP_Fail 16-333
IuB_nBAP_Reset_Requ_Fail 16-335
IuB_nodeBCommunicationLost 16-337
IuB_parameterFailure 16-340
IuB_resourceFailure 16-342
IuB_sAALUNI_RES_PROT_STA_DN 16-344
IuB_sAALUNI_VCC_ST_DN 16-346
IuB_uNIStack_FAIL 16-348
...................................................................................................................................................................................................................................
16-318 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuB_cellReconfigTimeout
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_cellReconfigTimeout alarm.
Description
There is a timeout of the NBAP Common transport channel reconfiguration request
procedure initiated by the RNC.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
The cell reconfiguration has failed.
System impact
The new configuration for the cell cannot proceed.
1 At the OMC-UPS, make sure that the Node B operational state is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the OMC-UPS, make sure that the IuB operational state is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-319
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuB_cellReconfigTimeout
procedures
...................................................................................................................................................................................................
3 At the OMC-UPS, if the Cell Reconfiguration Timer value is too short, retry the
reconfiguration by increasing the value of the Cell Reconfiguration Timer.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-320 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuB_cellSetupTimeout
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_cellSetupTimeout alarm.
Description
There is a timeout of the NBAP Cell Setup Request procedure initiated by the RNC.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Cell Setup timeout. The cell setup procedure may fail and result in the LCell
uncommissioned for call processing. Failures for this have occurred when the ATM
network drops packets resulting in the far end Node B not receiving all packets
associated with this message.
System impact
The Cell initialization has failed.
1 At the OMC-UPS, make sure that the Cell Setup Request Timer value is not too short.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the OMC-UPS, make sure that the Node B operational state is OK.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-321
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuB_cellSetupTimeout
procedures
3 At the OMC-UPS, make sure that the IuB operational state is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-322 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuB_channelReconfigFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_channelReconfigFailure alarm.
Description
The NBAP procedure “Common Transport Channel Reconfiguration” request initiated
by the RNC has failed for other reasons than a timeout.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
The common channel reconfiguration has failed.
System impact
The new configuration for the common channel cannot proceed.
1 If... Then...
The cause is ‘Node B resources The logical cell configuration does not match the
not Available’, capability of the local cell. Go to step 2.
The cause is ‘Power level not The logical cell configuration does not match the
supported’, capability of the local cell or power range. Go to
step 3.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-323
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuB_channelReconfigFailure
procedures
If... Then...
The cause is ‘Hardware Failure’, Go to step 4.
...................................................................................................................................................................................................
2 At the OMC-UPS, check the common channel resources allocation on the LCell object
for the channels stated in the CELL RECONFIGURATION REQUEST message.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-324 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuB_channelReconfigTimeout
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_channelReconfigTimeout alarm.
Description
There is a timeout of the NBAP Common Transport Channel Reconfiguration request
procedure initiated by the RNC.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
The common channel reconfiguration has failed.
System impact
The new configuration for the common channel cannot proceed.
1 At the OMC-UPS, make sure that the Node B operational state is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
2 At the OMC-UPS, make sure that the IuB operational state is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-325
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuB_channelReconfigTimeout
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-326 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuB_channelSetupFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_channelSetupFailure alarm.
Description
There is a failure of the NBAP procedure Common Transport Channel Reconfiguration.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
A Common Channel Setup failure is detected by the Node B. Possible root causes,
indicated in the common channel setup failure cause, are:
• Node B resources not available
• Power level not supported
• Hardware failure.
System impact
The Cell initialization has failed.
1 If... Then...
The cause is ‘Node B resources The logical cell configuration does not match the
not Available’, capability of the local cell. Go to step 2.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-327
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuB_channelSetupFailure
procedures
If... Then...
The cause is ‘Power level not The logical cell configuration does not match the
supported’, capability of the local cell or power range. Go to
step 4.
The cause is ‘Hardware Failure’, Go to step 6.
...................................................................................................................................................................................................
2 At the OMC-UPS, check the Common channel resources allocated in the Common
channel Setup Request message. Make sure that the correct logical cell configuration is
being used.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-328 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuB_channelSetupTimeout
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_channelSetupTimeout alarm.
Description
There is a timeout of the NBAP Common transport channel setup request procedure
initiated by the RNC.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Setup timeout. The common channel transport procedure may fail and result in the
LCell object being uncommissioned. Failures for this have occurred when ALCAP has
failed to successfully establish common channels on the first traffic channel.
System impact
The Cell initialization has failed.
1 At the OMC-UPS, make sure that the Node B operational state and the IuB operational
state are OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-329
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuB_channelSetupTimeout
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, make sure that the Common transport channel setup request timer.
value is not too short.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the OMC-UPS, correct the ALCAP transport layer address to align the Node B and
RNC database values.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
4 At the OMC-UPS, correct the ATM transport network to successfully pass the ALCAP
messages required to set up RACH, FACH, PCH.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
5 At the OMC-UPS, correct framing protocol failures which would cause the TPU to fail
in setting up common channels.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-330 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuB_highBER
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_highBER alarm.
Description
High BER detected on IuB by u & s-plane.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
This alarm is reported as a result of high BER on the IuB link between NodeB &
RNC. Possible causes are:
• Bad connection on E1/T1.
• Faults in the transport network.
• Poor quality of the transmission link
System impact
Excessive link layer retransmission resulting in a significant decrease in user
throughput.
Degrading the capacity of the IuB link.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-331
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuB_highBER
procedures
....................................................................................................................................................................................................................................
16-332 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuB_nBAP_Reset_Requ_CCP_Fail
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_nBAP_Reset_Requ_CCP_Fail
alarm.
Description
NBAP Reset Request for one or more CCPs failed.
Important! This alarm must be cleared manually.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
NBAP Reset Request for one or more CCPs failed.
System impact
Cannot guarantee that Node B has released all resources within a Node B subsystem
associated with previous calls. Risk for some hanging resources to remain in Node B
reducing efficiency.
1 At the OMC-UPS, make sure that the operational state of the Node B is OK.
...................................................................................................................................................................................................
2 At the OMC-UPS, make sure that the Iub transmission link is OK.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-333
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuB_nBAP_Reset_Requ_CCP_Fail
procedures
....................................................................................................................................................................................................................................
16-334 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuB_nBAP_Reset_Requ_Fail
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_nBAP_Reset_Requ_Fail alarm.
Description
NBAP Reset Request for entire Node B failed.
Important! This alarm must be cleared manually.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
NBAP Reset Request for entire Node B failed.
System impact
Cannot guarantee that Node B has released all resources associated with previous calls.
Risk for some hanging resources to remain in NodeB reducing efficiency.
1 At the OMC-UPS, make sure that the operational state of the Node B is OK.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-335
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuB_nBAP_Reset_Requ_Fail
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-336 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuB_nodeBCommunicationLost
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_nodeBCommunicationLost
alarm.
Description
Communication to the Node B is lost.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• Hardware problems
• Link failure
• Communication software failure on the Node B or the RNC.
System impact
Loss of service to the Node B.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-337
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuB_nodeBCommunicationLost
procedures
If... Then...
Only one IubCommunicationLost Go to step 2.
alarm is active,
More IubCommunicationLost Go to step 5.
alarms are active,
...................................................................................................................................................................................................
2 At the OMC-UPS, clear any URC or E1T1Port alarms that can cause this problem.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the OMC-UPS, clear any other alarms that can cause this problem.
Hardware failures for the Node B would result in other errors for the Node B
Controller logs indicating where the action takes place.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
5 At the OMC-UPS, clear any ICC alarms that can cause this problem.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-338 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuB_nodeBCommunicationLost
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-339
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuB_parameterFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_parameterFailure alarm.
Description
Orthogonal Channel Noise Simulator (OCNS) Channel failure due to incorrect input
parameters.
Important! This alarm must be cleared manually.
Default severity
Minor
Alarm type
communicationsAlarm
Root cause
This fault is due to incorrect input parameters for setting up the OCNS.
Note: The Distinguished Name (DN) of the OCNS channel for which incorrect
parameters have been entered, is listed in the alarm text.
System impact
OCNS testing is not available.
1 At the OMC-UPS, check the OCNS input parameters. The cell id or channel id could
be wrong. Make sure that the values are in the recommended range.
...................................................................................................................................................................................................................................
16-340 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuB_parameterFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-341
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuB_resourceFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_resourceFailure alarm.
Description
Orthogonal Channel Noise Simulator (OCNS) Channel failure due to unavailable
resources.
Important! This alarm must be cleared manually.
Default severity
Minor
Alarm type
qualityofServiceAlarm
Root cause
OCNS Resource failure could be due to insufficient power available to set up OCNS
channels on a particular cell, or Node B resources are not available.
Note: The Distinguished Name (DN) of the OCNS channel for which the resource
setup failed, is listed in the alarm text.
System impact
OCNS testing is not available.
1 At the OMC-UPS, check the input power setting for each of the OCNS channels.
Make sure that the total power for OCNS channels does not exceed the recommended
value.
...................................................................................................................................................................................................................................
16-342 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuB_resourceFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-343
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuB_sAALUNI_RES_PROT_STA_DN
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_sAALUNI_RES_PROT_S-
TA_DN alarm.
Description
The Signaling ATM Adaptation Layer -User Network Interface (SAAL-UNI) assured
link is down.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Communication failure.
System impact
Loss of service on the link
...................................................................................................................................................................................................................................
16-344 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuB_sAALUNI_RES_PROT_STA_DN
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-345
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuB_sAALUNI_VCC_ST_DN
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_sAALUNI_VCC_ST_DN alarm.
Description
The Signaling ATM Adaptation Layer - User Network Interface (SAAL-UNI) virtual
channel connection is down.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Virtual channel failure.
System impact
No virtual channel available.
...................................................................................................................................................................................................................................
16-346 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuB_sAALUNI_VCC_ST_DN
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-347
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuB_uNIStack_FAIL
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuB_uNIStack_FAIL alarm.
Description
General User-Network Interface (UNI) stack error.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Possible causes are:
• Task suspended
• Task dead
• General configuration error
• Layer manager failure.
System impact
Signaling link is temporarily not available.
1 No action required.
The signaling link restores automatically and the alarm clears automatically.
...................................................................................................................................................................................................................................
16-348 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuB_uNIStack_FAIL
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-349
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuCS alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Iu-cs interface.
Contents
IuCS_coreNetwork_OOS_For_NonUE_Sig 16-351
IuCS_rANAPResetFail 16-353
IuCS_remoteSubsystemOutOfService 16-355
IuCS_sNE_Context_Cre_Fail_For_NonUE_Sig 16-357
...................................................................................................................................................................................................................................
16-350 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuCS_coreNetwork_OOS_For_NonUE_Sig
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuCS_coreNetwork_OOS_For_Non-
UE_Sig alarm.
Description
Remote core network out of service.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
The circuit switched core network has an ‘out of service’ service state. The RNC is
unable to communicate with the circuit switched core network.
System impact
Communication is suspended over connection-oriented or connectionless Iu-CS
channels. Circuit switched services including voice are not available.
1 Contact circuit switch MSC maintenance personnel to determine the cause of the
‘out-of-service’ core network and take the appropriate action.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-351
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuCS_coreNetwork_OOS_For_NonUE_Sig
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-352 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuCS_rANAPResetFail
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuCS_rANAPResetFail alarm.
Description
RANAP reset procedure towards the 3G-MSC failed.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
RANAP reset procedure towards the 3G-MSC failed.
System impact
Cannot guarantee that 3G-MSC has released all resources associated with the RNC that
had previously been allocated to support calls. Potential risk for some hanging
resources to remain in 3G-MSC reducing efficiency.
1 At the OMC-UPS, make sure that the 3G-MSC operational state and the Iu-cs
transmission link are OK.
...................................................................................................................................................................................................
2 At the OMC-UPS, perform a reset type 2 on the IuCS object. This will trigger a
RANAP reset procedure.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-353
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuCS_rANAPResetFail
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-354 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuCS_remoteSubsystemOutOfService
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuCS_remoteSubsystemOutOfService
alarm.
Description
The remote subsystem has gone out of service.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Possible causes are:
• Remote SCCP subsystem being out of service
• Remote SCCP stack being not available
• MTP3 connection failure (indicated by the SS7_MTP3_PAUSE alarm).
System impact
Existing circuit switched calls are dropped. New circuit switched calls are refused.
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-355
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuCS_remoteSubsystemOutOfService
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-356 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuCS_sNE_Context_Cre_Fail_For_NonUE_Sig
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuCS_sNE_Context_Cre_Fail_For-
_NonUE_Sig alarm.
Description
IuCS Sub Network Element Connectionless Context Create Failure.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Possible causes are:
• No GICC available for call processing
• Failure to create ATM resources (AAL2 PVCs)
• Unavailability of the Broadband SS7 stack (possibly caused by a GICC failure or a
signaling stack failure).
System impact
The shelf is not available for call processing. No calls are possible.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-358 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuPS alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Iu-ps interface.
Contents
IuPS_coreNetwork_OOS_For_NonUE_Sig 16-360
IuPS_gTP_U_Echo_Responses_Not_Received 16-362
IuPS_rANAPResetFail 16-364
IuPS_remoteSubsystemOutOfService 16-366
IuPS_sNE_Context_Cre_Fail_For_NonUE_Sig 16-368
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-359
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuPS_coreNetwork_OOS_For_NonUE_Sig
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuPS_coreNetwork_OOS_For_Non-
UE_Sig alarm.
Description
The remote core network is out of service.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Possible causes are:
• Gateway Intelligent Carrier Cards (GICC) on the RNC are not in an operational
state
• The packet switched core network has an ‘out of service’ service state and the RNC
is unable to communicate with the packet switched core network.
System impact
Communication is suspended over connection-oriented or connectionless Iu-PS
channels. Packet switched services are not available.
1 At the OMC-UPS, make sure that the GICC object is in an operational state
(Unlocked/Enabled).
...................................................................................................................................................................................................................................
16-360 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuPS_coreNetwork_OOS_For_NonUE_Sig
procedures
...................................................................................................................................................................................................
2 Contact packet switch SGSN maintenance personnel to determine the cause of the
‘out-of-service’ core network.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-361
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuPS_gTP_U_Echo_Responses_Not_Received
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuPS_gTP_U_Echo_Responses-
_Not_Received alarm.
Description
The RNC did not receive an Echo Response message on the several consecutive Echo
Request messages transmitted by the RNC.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• An SGSN error in the IP protocol stack
• A transport network error
• A change in the configuration of either the transport network, RNC, or SGSN,
while the nodes were in operation.
System impact
The particular GPRS Tunneling Protocol - User plane (GTP-U) instance blocked its
communication with the particular SGSN IP address.
...................................................................................................................................................................................................................................
16-362 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuPS_gTP_U_Echo_Responses_Not_Received
procedures
1 Check all the possible causes that created this error and take the appropriate action.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-363
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuPS_rANAPResetFail
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuPS_rANAPResetFail alarm.
Description
RANAP reset procedure towards the SGSN failed.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
RANAP reset procedure towards SGSN failed.
System impact
Cannot guarantee that SGSN has released all resources associated with RNC that had
previously been allocated to support calls. Potential risk for some hanging resources to
remain in SGSN reducing efficiency.
1 At the OMC-UPS, make sure that the SGSN operational state and the Iu-ps
transmission link are OK.
...................................................................................................................................................................................................
2 At the OMC-UPS, perform a reset type 2 on the IuPS object. This will trigger a
RANAP reset procedure.
...................................................................................................................................................................................................................................
16-364 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuPS_rANAPResetFail
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-365
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuPS_remoteSubsystemOutOfService
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuPS_remoteSubsystemOutOfService
alarm.
Description
The remote subsystem has gone out of service.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Possible causes are:
• Remote SCCP subsystem being out of service
• Remote SCCP stack being not available
• MTP3 connection failure (indicated by the SS7_MTP3_PAUSE alarm).
System impact
Existing packet switched calls are dropped. New packet switched calls are refused.
...................................................................................................................................................................................................................................
16-366 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuPS_remoteSubsystemOutOfService
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-367
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuPS_sNE_Context_Cre_Fail_For_NonUE_Sig
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuPS_sNE_Context_Cre_Fail_For-
_NonUE_Sig alarm.
Description
IuPS Sub Network Element Connectionless Context Create Failure.
Default severity
Major
Alarm type
processingErrorAlarm
Probable cause
Possible causes are:
• No GICC available for call processing
• Failure to create ATM resources (AAL2 PVCs)
• Unavailability of the Broadband SS7 stack (possibly caused by a GICC failure or a
signaling stack failure).
System impact
The shelf is not available for call processing. No calls are possible.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-369
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuPSSubNet alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the IuPSSubNet alarms.
Contents
IuPSSubNet_communicationFailure 16-371
...................................................................................................................................................................................................................................
16-370 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuPSSubNet_communicationFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuPSSubNet_communicationFailure
alarm.
Description
The IuPSSubnet is disabled, all associated Permanent Virtual Circuits (PVCs) have
failed.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• Configuration problem
• The SGSN on the packet core network is down
• A router between the RNC and the SGSN has failed.
System impact
New packet call are not possible
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-371
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance IuPSSubNet_communicationFailure
procedures
...................................................................................................................................................................................................
2 At the RNC, check that the SGSN IP addresses are correctly configured.
If the alarm is cleared, procedure is completed.
...................................................................................................................................................................................................
If... Then...
If the SGSN is not functional, Go to step 4.
If the SGSN is functional, Go to step 5.
...................................................................................................................................................................................................
5 Check the status of PVCs on any routers between the RNC and the SGSN.
If the alarm is cleared, procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
16-372 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
IuR alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the Iur interface.
Contents
IuR_pRNC_OOS_For_NonUE_Sig 16-374
IuR_remoteSubsystemOutOfService 16-376
IuR_sNE_Context_Cre_Fail_For_NonUE_Sig 16-378
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-373
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuR_pRNC_OOS_For_NonUE_Sig
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuR_pRNC_OOS_For_NonUE_Sig
alarm.
Description
The peer RNC is out of service.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Possible causes are:
• Communication link to the peer RNC is down
• Local RNC Iur link or other component problem
• Peer RNC Iur link or other component problem.
System impact
Communication is suspended over connection-oriented or connectionless Iur channels.
The serving RNC is not able to establish resources for radio link setup on the peer
RNC.
1 At the OMC-UPS, make sure that the communications link to the peer RNC is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-374 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuR_pRNC_OOS_For_NonUE_Sig
procedures
...................................................................................................................................................................................................
2 At the OMC-UPS, make sure that the Iur and parent components on the local and the
peer RNCs are unlocked and enabled.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-375
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuR_remoteSubsystemOutOfService
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuR_remoteSubsystemOutOfService
alarm.
Description
The remote subsystem has gone out of service.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
Possible causes are:
• Remote SCCP subsystem being out of service
• Remote SCCP stack being not available
• MTP3 connection failure (indicated by the SS7_MTP3_PAUSE alarm).
System impact
Existing packet switched calls are dropped. New packet switched calls are refused.
...................................................................................................................................................................................................................................
16-376 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance IuR_remoteSubsystemOutOfService
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-377
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
IuR_sNE_Context_Cre_Fail_For_NonUE_Sig
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the IuR_sNE_Context_Cre_Fail_For-
_NonUE_Sig alarm.
Description
IuR Sub Network Element Connectionless Context Create Failure.
Default severity
Major
Alarm type
processingErrorAlarm
Probable cause
Possible causes are:
• No GICC available for call processing
• Failure to create ATM resources (AAL2 PVCs)
• Unavailability of the Broadband SS7 stack (possibly caused by a GICC failure or a
signaling stack failure).
System impact
The shelf is unavailable for call processing. No calls are possible.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-379
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell alarms
Overview
...................................................................................................................................................................................................................................
Purpose
This section describes the fault clearance procedures for the LCell.
Contents
LCell_avail_Status_Degraded 16-381
LCell_bCCHScheduleErr 16-382
LCell_callPreemptionError 16-384
LCell_callPreemptionFailure 16-386
LCell_channelSetupFailure 16-388
LCell_code_Allocation_Failure 16-390
LCell_code_Starvation 16-392
LCell_common_Transport_Channel_Reconfiguration_Failure 16-394
LCell_common_Transport_Channel_Reconfiguration_Timeout 16-396
LCell_common_Transport_Channel_Setup_Failure 16-398
LCell_common_Transport_Channel_Setup_Timeout 16-400
LCell_configurationError 16-402
LCell_configurationErrorSCCPCH 16-404
LCell_nodeBUnavailable 16-406
LCell_rRC_Connection_Establish_Failure 16-408
LCell_reconfigFailure 16-410
LCell_reconfigTimeout 16-412
LCell_setupFailure 16-414
LCell_setupTimeout 16-416
LCell_system_Information_Update_Failure 16-418
LCell_tPUCellContextFailure 16-420
...................................................................................................................................................................................................................................
16-380 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures
LCell_avail_Status_Degraded
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_avail_Status_Degraded alarm.
Description
The availability status of the cell is degraded.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
The NodeB have indicated that the power capability of the cell has been degraded or
there has been some other RNC initiated degradation of the cell.
System impact
Depending on the root cause of the cell degradation, call processing may be impacted.
1 Locate the root cause of the cell degradation and take appropriate action.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-381
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_bCCHScheduleErr
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_bCCHScheduleErr alarm.
Description
CRNC detects that the BCCH schedule is invalid.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
System Information Blocks (SIB) scheduling parameters are incorrect.
System impact
The scheduling error is due to an attempt by the operator to apply an invalid SIB REP
of any SIB Type. The CRNC calculates the new BCCH schedule with the new SIB
REP and found that it resulted in overlapping SIBs.
1 At the OMC-UPS, use the default value of the SIB REP of the SIB Type (if available).
...................................................................................................................................................................................................
2 Apply the previous value of the SIB REP of the SIB Type (if any).
...................................................................................................................................................................................................................................
16-382 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_bCCHScheduleErr
procedures
...................................................................................................................................................................................................
3 Change the SIB REP of the SIB Type in consultation with Alcatel-Lucent customer
support.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-383
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_callPreemptionError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_callPreemptionError alarm.
Description
The RNC has preempted the wrong class of call types. Code starvation has occurred
and there are no free channelisation codes for a new emergency call request.
Important! This alarm must be cleared manually.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
Software error. The RNC pre-empted a wrong type of call (e.g. control channels or
existing emergency calls). This means that the wrong class of calls were pre-empted in
the event of code starvation and a request for an emergency call.
System impact
Existing call(s) may be dropped, the new emergency call may not be allowed.
...................................................................................................................................................................................................................................
16-384 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_callPreemptionError
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-385
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_callPreemptionFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_callPreemptionFailure alarm.
Description
The RNC has failed to to preempt existing calls to accommodate a request for a new
emergency call. Code starvation has occurred and there are no free channelisation
codes for a new emergency call request.
Important! This alarm must be cleared manually.
Default severity
Minor
Alarm type
processingErrorAlarm
Root cause
Software error. The RNC pre-empted a wrong type of call (e.g. control channels or
existing emergency calls). This means that the wrong class of calls were pre-empted in
the event of code starvation and a request for an emergency call.
System impact
Emergency calls will not be accepted.
...................................................................................................................................................................................................................................
16-386 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_callPreemptionFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-387
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_channelSetupFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_channelSetupFailure alarm.
Description
Orthogonal Channel Noise Simulator (OCNS) Channel Setup Failure.
Important! This alarm must be cleared manually.
Default severity
Minor
Alarm type
equipmentAlarm
Root cause
The OCNS should be run during the provisioning of the system. Possible causes are:
• No DL Channelisation codes in this cell are available
• Too many engineers are working on the provisioning system
• Problem with the resource allocation in the system
• Hardware failure or break of Iub link.
Note: The Distinguished Name (DN) of the OCNS channel for which the setup failed,
is listed in the alarm text.
System impact
OCNS testing is not available.
...................................................................................................................................................................................................................................
16-388 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_channelSetupFailure
procedures
2 Check how many CEs have been occupied. If all CEs have been occupied, this means
that too many people are using the system now. Else go to step 3.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-389
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_code_Allocation_Failure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_code_Allocation_Failure
alarm.
Description
Channelisation code allocation failure per sector-carrier. Codes are not allocated.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Probable causes are:
• Software error
• Database inconsistency
• Corrupt data.
System impact
Cannot accommodate new users requiring new channelisation code.
...................................................................................................................................................................................................................................
16-390 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_code_Allocation_Failure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-391
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_code_Starvation
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_code_Starvation alarm.
Description
Channelisation code starvation detected (no codes are available) per sector-carrier.
Default severity
Major
Alarm type
qualityofServiceAlarm
Root cause
Probable causes are:
• Congestion
• Resource is at or nearing capacity
• System resources overload.
System impact
Cannot accommodate new users requiring new channelisation code.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-393
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_common_Transport_Channel_Reconfiguration_Failure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_common_Transport_Channel-
_Reconfiguration_Failure alarm.
Description
The Common Transport Channel reconfiguration has failed.
Default severity
Warning
Alarm type
equipmentAlarm
Root cause
Probable causes are:
• Unknown cell identified
• Insufficient physical channel resources
• Node B resources unavailable
• DL radio resources not available
• UL radio resources not available
• Insufficient physical channel resources
• Requested configuration not supported.
System impact
Possible system impact may be:
• The transport channel has not been resized
• The call capacity of the cell has not been adjusted.
...................................................................................................................................................................................................................................
16-394 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures LCell_common_Transport_Channel_Reconfiguration_Failure
1 At the OMC-UPS, make sure that the operational state of the Node B is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-395
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_common_Transport_Channel_Reconfiguration_Timeout
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_common_Transport_Channel-
_Reconfiguration_Timeout alarm.
Description
The Common Transport Channel reconfiguration timer has expired.
Default severity
Critical
Alarm type
communicationsAlarm
Root cause
Probable causes are:
• The timer is set too short
• The Node B is malfunctioning.
System impact
Possible system impact may be:
• The transport channel has not been resized
• The call capacity of the cell has not been adjusted.
1 At the OMC-UPS, make sure that the operational state of the Node B is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-396 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance
procedures LCell_common_Transport_Channel_Reconfiguration_Timeout
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-397
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_common_Transport_Channel_Setup_Failure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_common_Transport_Chan-
nel_Setup_Failure alarm.
Description
The setup of the Common Transport Channel has failed.
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Probable causes are:
• Unknown cell identified
• Insufficient physical channel resources
• Node B resources unavailable
• DL radio resources not available
• UL radio resources not available
• Insufficient physical channel resources
• Requested configuration not supported.
System impact
Possible system impact may be:
• The transport channel has not been setup
• The call capacity of the cell has not been created.
...................................................................................................................................................................................................................................
16-398 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_common_Transport_Channel_Setup_Failure
procedures
1 At the OMC-UPS, make sure that the operational state of the Node B is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-399
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_common_Transport_Channel_Setup_Timeout
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_common_Transport_Chan-
nel_Setup_Timeout alarm.
Description
The Common Transport Channel setup timer has expired.
Default severity
Warning
Alarm type
communicationsAlarm
Root cause
Probable causes are:
• The timer is set too short
• The Node B is malfunctioning.
System impact
Possible system impact may be:
• The transport channel has not been setup
• The call capacity of the cell has not been created.
1 At the OMC-UPS, make sure that the operational state of the Node B is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-400 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_common_Transport_Channel_Setup_Timeout
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-401
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_configurationError
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_configurationError alarm.
Description
Configuration error.
Important! This alarm must be cleared manually.
Default severity
Critical
Alarm type
processingErrorAlarm
Root cause
The Node B fails to update System Information Blocks (SIBs).
System impact
SIBs cannot be updated in a cell. UEs cannot access the radio network correctly.
...................................................................................................................................................................................................................................
16-402 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_configurationError
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-403
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_configurationErrorSCCPCH
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_configurationErrorSCCPCH
alarm.
Description
The FACH service profile for one or more cells has been configured with data
incompatible with the software release.
Important! This alarm must be cleared manually.
Default severity
Major
Alarm type
processingErrorAlarm
Root cause
Incorrect FACH service profile configuration. The profile requires one data and one
signalling FACH.
System impact
Cells with incorrect configuration will not transmit.
1 At the OMC-UPS, check OAM configuration for the FACH service profile.
...................................................................................................................................................................................................................................
16-404 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_configurationErrorSCCPCH
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-405
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_nodeBUnavailable
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_nodeBUnavailable alarm.
Description
The cell is not operational due to a Node B block.
Default severity
Major
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Node B is blocked
• Node B is currently being reset.
System impact
No calls are possible on the cell.
1 At the OMC-UPS, make sure that the Node B operational state is OK.
...................................................................................................................................................................................................................................
16-406 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_nodeBUnavailable
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-407
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_rRC_Connection_Establish_Failure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_rRC_Connection_Establish-
_Failure alarm.
Description
Failure to establish a RRC connection.
Default severity
Major
Alarm type
communicationsAlarm
Root cause
Probable causes are:
• NBAP/RNSAP radio link setup failure including time-out
• ALCAP NBAP/RNSAP data transport bearer setup failure including time-out
• Data transport bearer synchronization failure
• SRNC fails to receive RRC CONNECTION SETUP COMPLETE message
• RESET message in RRC connection establish.
System impact
Possible system impact may be:
• Call setup delay
• Failure to establish a call.
...................................................................................................................................................................................................................................
16-408 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_rRC_Connection_Establish_Failure
procedures
1 At the Node B, make sure that the radio interfaces are operational.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
3 At the OMC-UPS, make sure that the RRC configuration parameters are OK.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-409
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_reconfigFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_reconfigFailure alarm.
Description
Logical cell reconfiguration failed.
Default severity
Warning
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Unknown cell identified
• Insufficient physical channel resources
• Node B resources unavailable
• Power level not supported.
System impact
Possible system impact may be:
• The cell has not been reconfigured
• The call capacity of the cell has not been adjusted.
1 At the OMC-UPS, make sure that the operational state of the Node B is OK.
...................................................................................................................................................................................................................................
16-410 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_reconfigFailure
procedures
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-411
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_reconfigTimeout
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_reconfigTimeout alarm.
Description
The logical cell reconfiguration timer has expired.
Default severity
Warning
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• The timer is set too short
• The Node B is malfunctioning.
System impact
Possible system impact may be:
• The cell has not been reconfigured
• The call capacity of the cell has not been adjusted.
1 At the OMC-UPS, make sure that the operational state of the Node B is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-412 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_reconfigTimeout
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-413
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_setupFailure
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_setupFailure alarm.
Description
The cell setup has failed. !!!!!!!!!!!
Default severity
Critical
Alarm type
equipmentAlarm
Root cause
Possible causes are:
• Unknown cell identified
• Insufficient physical channel resources
• Node B resources unavailable
• Power level not supported.
System impact
The new cell has not been added.
1 At the OMC-UPS, make sure that the operational state of the Node B is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................................................
16-414 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_setupFailure
procedures
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
401-382-290R04.03 Alcatel-Lucent - Proprietary 16-415
Issue 1, August 2007 See notice on first page
Corrective maintenance - RNC alarm clearance
procedures
LCell_setupTimeout
...................................................................................................................................................................................................................................
Purpose
This topic provides the procedure for clearing the LCell_setupTimeout alarm.
Description
The cell setup time expired.
Default severity
Warning
Alarm type
communicationsAlarm
Root cause
Possible causes are:
• The timer is set too short
• The Node B is malfunctioning.
System impact
The new cell has not been added.
1 At the OMC-UPS, make sure that the operational state of the Node B is OK.
If the alarm is cleared, the procedure is completed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
16-416 Alcatel-Lucent - Proprietary 401-382-290R04.03
See notice on first page Issue 1, August 2007
Corrective maintenance - RNC alarm clearance LCell_setupTimeout
procedures
...................................................................................................................................................................................................
...............................................................................