Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Board Overheated :
Description
The alarm is a primary alarm. The alarm is issued by the MO, PlugInUnit.
The possible alarm causes and fault locations are explained in the table below:
Table 1
Alarm Causes
Alarm
Cause
Description
Impact
The air
surrounding
the node is
too warm.
The physical
environment
of the node is
too warm.
The Fan
unit is not
working
properly.
The board
has too
high load.
The board is
too hot.
The process
The fault is
(traffic) load located in the
on the board is configuration
too high.
and/or
dimensioning of
the board.
The
hardware
on the
board is
faulty.
The board is
faulty.
Some
hardware
component is
too hot
because this
or another
component is
faulty.
The overheated
component can be
damaged and traffic
affected..
In the
environment
outside the
subrack.
The board.
The alarm is issued when the temperature of a board becomes higher than the
maximum allowed temperature. That is, the alarm is issued when one or more
temperature sensors on a board detect that the current temperature is too high. This
can be caused by a number of hardware faults, either on the board itself or on the
Fan units in the subrack. The processor load also affects the temperature on the
board. The alarm can therefore be issued for several different reasons, and
sometimes a combination of two reasons can cause the alarm, for example,
decreased capacity in the Fan unit combined with increased load on the board
processor.
The alarm ceases when the temperature on the board decreases and remains at this
lower temperature. All temperature sensors must measure this lower temperature for
the alarm to cease. If the alarm is not acted on, the overheated board can be
damaged and the capacity of the node will be affected.
If several boards are overheated, that is, if this alarm is issued on several instances
of the MO, PlugInUnit, it is likely that the fault is not on the boards, but in the Fan
unit(s) or in the physical environment of the node (including fire). Damaged boards
must be replaced.
It is probably necessary to visit the node.
CcDevice_DeviceDisabled :
2.
Description
The alarm is a primary alarm. The alarm is issued by the Managed Object (MO)
CcDevice.
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm Causes
Alarm
Cause
Description
Impact
Device
Disabled
The device
remains disabled
until it is enabled
by the operator
Note:
This alarm can appear as a result of the maintenance activity.
3.
Description
The alarm is a primary alarm. The alarm is issued by the MO,
ConfigurationVersion.
The possible alarm causes and fault locations are explained in Table 1.
Table 1
Alarm
Cause
Alarm Causes
Description
Fault
Reason
Fault Location
Impact
Software
failure.
The
The CV is not
ConfigurationVersion valid.
MO that issued the
alarm.
Note:
If the alarm is not acted on, that is if the faulty CV is not removed, this faulty
CV can cause a node restart to fail.
4.
Description
The alarm is a primary alarm. The alarm is issued by the MO,IpInterface.
The possible alarm causes and fault locations are explained in the table below.
The alarm can occur only if the Router Path Supervision (RPS) is enabled, which
means that the attribute rps on the MO IpInterface is set to true.
The additional info in the alarm states that the alarm is issued for default router 0,
and specifies the IP address for that default router.
Table 1
Alarm Causes
Alarm
Cause
Description
Impact
IP network
problem.
Wrong
dimensioning
or hardware
fault in the
network.
No impact, if at
least one default
router is
reachable.
IP network.
No traffic, if all
default routers
are unreachable.
The router is The router itself is not The router is The router.
not
answering the ping
not correctly
answering. request.
configured, or
the router is
down, or there
is a hardware
fault on the
router.
As above.
Wrong IP
address
configured
for the
router.
As above.
The IP address is
Configuration
invalid, or it is pointing fault.
to something other
than a router.
Configuration
fault in this
node.
The following are the consequences for the node if the alarm is not solved:
5.
DcDevice_DeviceDisabled
Description
The alarm is a primary alarm. The alarm is issued by the Managed Object (MO)
DcDevice.
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm Causes
Alarm
Cause
Description
Impact
Device
Disabled
The device
remains disabled
until it is enabled
by the operator
Note:
6.
Description
The alarm is a primary alarm. The alarm is issued by the MO ManagedElementData.
The alarm is issued if the amount of stored data on the distributed C volume of the
General purpose Processor Boards (GPB) becomes so large that the volume is full, or
nearly full. The volume is normally checked automatically every 15 minutes, and if
the free space is less than or equal to the value (in megabytes) of the attribute
minimumHdVolumeCFreespace in the MO ManagedElementData, the alarm is issued.
The alarm ceases when the amount of free space increases to at be least one
megabyte more than the value of minimumHdVolumeCFreespace. Normally, it is
necessary to delete files from the C volume in order make sufficient space available,
so that the alarm ceases.
As a result of the fault, there might not be enough space to store important new data
or to create new files on the C volume. Also, there might be not enough space for
new upgrade packages.
The possible causes are as follows:
7.
Description
The alarm is a primary alarm. The alarm is issued by the MO
GeneralProcessorUnit.
The alarm is issued if the amount of stored data on the D volume of a General
purpose Processor Board (GPB) becomes so large that the volume is full, or nearly
full. The volume is normally checked automatically every 15 minutes, and if the free
space is less than or equal to the value (in megabytes) of the attribute,
minimumHdVolumeDFreespace in the MO GeneralProcessorUnit, the alarm is issued.
The alarm ceases when the amount of free space (that is, the value of the attribute,
hdVolumeDFreespace in the MO, GeneralProcessorUnit) increases to at least one
megabyte larger than the value of minimumHdVolumeDFreespace. Normally, it is
necessary to delete files from the D volume to make sufficient space available for the
alarm to cease.
As a result of the fault, there might not be enough space to store important new data
or to create new files on the D volume. Also, there might be not enough space for
new upgrade packages.
The possible causes are as follows:
8.
Description
The alarm is a primary alarm. The alarm is issued by the MO
GeneralProcessorUnit.
The alarm is issued if the amount of stored data on the D volume of a General
purpose Processor Board (GPB) becomes so large that the volume is full, or nearly
full. The volume is normally checked automatically every 15 minutes, and if the free
space is less than or equal to the value (in megabytes) of the attribute,
minimumHdVolumeDFreespace in the MO GeneralProcessorUnit, the alarm is issued.
The alarm ceases when the amount of free space (that is, the value of the attribute,
hdVolumeDFreespace in the MO, GeneralProcessorUnit) increases to at least one
megabyte larger than the value of minimumHdVolumeDFreespace. Normally, it is
necessary to delete files from the D volume to make sufficient space available for the
alarm to cease.
As a result of the fault, there might not be enough space to store important new data
or to create new files on the D volume. Also, there might be not enough space for
new upgrade packages.
The possible causes are as follows:
Too many configuration versions (CV) on the node, or the CVs are very large.
This can be the case if the alarm is issued only for the Core MP board(s), that
is, only for fault-tolerant Core boards indicated by the attribute
faultTolerantCoreStates in the MO ManagedElement.
Large amounts of other files on the D volume (files that are not part of any
UpgradePackage MO or configuration version).
The minimum free-space limit for the D volume is too large. That is, although
there is a reasonably large amount of free space, the value of the attribute
minimumHdVolumeDFreespace is too small for the D volume on the board.
9. ET Hardware Fault
Description
The alarm is a primary alarm. It is issued by the MO, ExchangeTerminal.
The alarm is issued, if the ET board or the ET part of the board is faulty. The fault
must be attended to on site.
As a consequence of the fault, traffic handled by the faulty board is lost.
The likely cause is a hardware fault.
Alarm
Cause
Alarm Causes
Description
Impact
Line card
Initial hardware tests Equipment
ET module on No traffic
problem
have failed.
fault.
CBM
Note:
The alarm can be issued as a result of a maintenance or an upgrade activity.
The following are the consequences for the node if the alarm is not
solved:
No traffic.
Alarm Causes
Alarm
Cause
Description
Impact
See alarm.
See alarm.
Ethernet frames
may be lost and
transmission
quality may
deteriorate.
Maintenance.
MO,
PlugInUnit.
Ethernet frames
may be lost and
transmission
quality may
deteriorate.
Fault in the
network.
Fault in the
network.
Network.
Ethernet frames
may be lost and
transmission
quality may
deteriorate.
Underdimensioning
Node or
network.
Ethernet frames
may be lost and
transmission
quality may
deteriorate.
Alarm Causes
Alarm Cause
Description
Link Down
Board,
Ethernet
network, or
configuration.
Impact
Disruption of
Ethernet traffic
on the affected
link.
Ethernet traffic
is slowed down
on the affected
link.
SFP Module
Mismatch
Unable to switch
Ethernet traffic
on the affected
link.
Missing or
faulty
hardware.
Unable to switch
Ethernet traffic
on the affected
link.
Board.
Alarm Causes
Alarm
Cause
Description
Impact
See alarm.
See alarm.
Ethernet frames
are lost and
transmission
quality
deteriorates.
Maintenance.
MO,
PlugInUnit.
Ethernet frames
are lost and
transmission
quality
deteriorates.
Fault in the
network.
Fault in the
network.
Network.
Ethernet frames
are lost and
transmission
quality
deteriorates.
UnderNode or
dimensioning. network.
Ethernet frames
are lost and
transmission
quality
deteriorates.
14. Eul_CodeAllocationFailure
Description
This alarm is a primary alarm. The alarm is issued by the Managed Object (MO) Eul.
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm Causes
Fault
Location
Invalid
An invalid
Configuration fault
RNC
downlink code downlink code
Configuration.
configuration. configuration
is detected at
Eul code
allocation.
Note:
This alarm can appear as a result of maintenance activity.
Impact
Radio Network
Service Impact.
EUL traffic cannot
be run in the
alarming cell.
15. Eul_NbapMessageFailure
Description
This alarm is a primary alarm. The alarm is issued by the Managed Object (MO) Eul
(Enhanced Uplink).
This alarm is issued when the RBS fails to set up Enhanced Dedicated Channel (EDCH) resources requested by the RNC. The alarm also appears when the RBS
indicates that a given local cell is not capable of supporting EUL.
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm Causes
Fault Reason
Configuration
The RBS local
fault.
cell does not
support EUL.
There are no HSDSCH Resources
set up in cell.
Dimensioning
Fault
Location
Eul
Eul
Impact
As a result of
this alarm, the
RNC disables
the E-DCH
resources in
the cell and
reattempts to
unknown Cell
Identification (C-ID)
error
fault
Cell not
available
Eul
The operational state of Configuration,
the RBS local cell in the Dimensioning,
RBS is Disabled. This and/or Hardware
can be caused by faults fault
in the resources used by
the RBS Local Cell.
HW failure
Requested
configuration
not supported
Hardware fault. HW
Eul
and E-DCH
Cell Portion
Information
and Target
Non-serving
E-DCH to
Total E-DCH
Power ratio.
Eul
activate them
if the
Enhanced
uplink (Eul) is
unlocked in
that cell in the
RNC.
Note:
16. Fach_NbapMessageFailure
Description
This alarm is a primary alarm. It is issued by the Fach Managed Object (MO).
The possible alarm causes and fault locations are explained in Table 1.
Table 1
Alarm Causes
Fault Reason
Configuration fault
Fault
Location
Fach
Cell not
available
The operational
Configuration fault
state of the RBS
Local Cell is
Disabled. This can
be caused by faults
in the resources
used by the RBS
Local Cell.
Fach
Node B
resource
unavailable
Fach
Transport
resource
unavailable
Fach
Message not
compatible
with receiver
state
The requested
channel is already
set up.
Dimensioning fault
Fach
Fach
NbapTimeout
Fach
Impact
The RNC
disables
the Fach.
UserPlane
Transport
Option
Mismatch
IubLink
Binding
Identity
Mismatch
Fach
Fach
Transport
The NBAP response Logical fault
Layer Address from the RBS is
Mismatch
without TLA or with
wrong TLA length.
Note:
This alarm can appear as a result of the maintenance activity.
Alarm Cause
Description
Fault Reason
Fault
Location
Impact
Failure of
Protocol
Mismatch of K1
and K2 bits
If the alarm is issued by the MO MspgExtended, possible alarm causes and fault
locations are explained in Table 2 and Table 3 respectively. The alarm causes are
stated in the additionalText.
Table 2
Alarm Cause
Description
Fault Reason
Fault
Location
Impact
fPAM (MSP
Architecture
mismatch)
fSCM (Signal
number
mismatch)
Alarm
Cause
Alarm Causes
Description
Impact
Configuration
of Fan MO.
Hardware
fault.
The temperature
alarms are not
reliable.
damaged,
because it is
operating under
conditions for
which it was not
designed.
Air flow not Air flow to cool
sufficient
subrack is not
due to too
sufficient.
much dust in
air filter.
Hardware
fault.
The node
equipment can
malfunction
temporarily, or be
damaged,
because it is
operating under
conditions for
which it was not
designed.
A faulty
A faulty temperature Hardware
Fan hardware The temperature
ambient
sensor gives an
fault.
fault.
alarms are not
temperature incorrect temperature
reliable.
sensor.
value.
Note:
The possible source of the fault is the on-site heating or cooling equipment.
The component issuing the alarm is therefore not necessarily at fault. That is,
it is possible that other equipment is at fault and has caused the alarm.
Alarm
Cause
Alarm Causes
Description
Configuration
of Fan MO.
Impact
The temperature
alarms are not
too low.
reliable.
Hardware
fault.
Hardware
fault.
The node
equipment can
malfunction
temporarily, or be
damaged,
because it is
operating under
conditions for
which it was not
designed.
A faulty
A faulty temperature Hardware
Fan hardware The temperature
ambient
sensor gives an
fault.
fault.
alarms are not
temperature incorrect temperature
reliable.
sensor.
value.
Note:
The possible source of the fault is the on-site heating or cooling equipment.
The component issuing the alarm is therefore not necessarily at fault. That is,
it is possible that other equipment is at fault and has caused the alarm.
Description
The alarm is a primary alarm. The alarm is issued by the MO, Fan.
The possible alarm causes and fault locations are explained in the table below.
The alarm is issued for a fan, if a hardware fault occurs. To investigate the cause, a
site visit is necessary.
Table 1
Alarm Causes
Alarm
Cause
Description
Impact
Fan
hardware
fault.
Hardware
fault.
Subrack cooling
may not be
sufficient.
Fan uni.t
Alarm Causes
Alarm
Cause
Description
Impact
Configuration
fault or
hardware
fault.
Node
configuration
or SCB-DF
boards.
No power
The fan is not working Hardware
supply to the because of power
fault.
fan.
failure.
Power supply
or power
cables.
Fan cables
not
connected.
because it is not
connected.
fault.
fan is unknown.
Subrack cooling
may not be
sufficient.
Fan fault.
Hardware
fault.
This alarm can be issued as a result of a maintenance activity. The alarm can also be
issued if the fan is temporarily unavailable to the supervision software. In this case
however, the alarm ceases automatically within a few minutes.
If the fault is not solved, the fan may continue to function autonomously. This can
only be determined by observing the fan itself, because when fan supervision is
disabled, no fan alarms are issued.
1.1.1 Fan Units BKV 301 471/1 and BKV 301 487/1
The alarm is issued when fan supervision has stopped, that is, the operational state
of the fan has been set to disabled.
As a consequence of the fault, the fan may or may not be operating autonomously.
This can only be determined by observation of the actual fan, because when fan
supervision is disabled, no fan alarms are issued.
The possible causes are as follows:
Note:
no power supply to the fan because, for example, a fuse has blown on the
Switch Core Board (SCB) or the fan cable is not correctly connected to the
SCB
a broken or faulty SCB
a broken or faulty fan
A Fan Supervision Failure alarm is issued when the fan is restarted. In this
case, however, the alarm automatically ceases.
23. Hsdsch_CodeAllocationFailure
Description
The alarm is a primary alarm. The alarm is issued by the Managed Object (MO)
Hsdsch.
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm Causes
Fault
Location
An invalid
downlink code
configuration
Invalid
is detected by
Hsdsch
downlink code
Configuration fault
the system at
configuration
High Speed
(HS) code
allocation.
Note:
This alarm can appear as a result of maintenance activity.
Impact
Radio Network
Service Impact.
HSDPA and EUL
traffic cannot be
run in the
alarming cell.
24. Hsdsch_NbapMessageFailure
Description
This alarm is a primary alarm. The alarm is issued by the Hsdsch Managed Object
(MO).
This alarm is issued when the RBS fails to set up High Speed Downlink Shared
Channel (HS-DSCH) resources requested by the RNC. The alarm also appears when
the RBS indicates that a given local cell is not capable of supporting High Speed Data
Packet Access (HSDPA).
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm Causes
Fault Reason
Fault
Impact
DL shared
The RBS local cell
channel type does not support
not supported HSDPA.
Unknown C-ID The RNC receives
an unknown Cell
Identification (CID) error.
Location
Configuration fault Hsdsch
Cell not
available
The operational
Configuration,
state of the RBS
Dimensioning,
Local Cell in the
and/or Hardware
RBS is Disabled
fault
(this can be caused
by faults in the
RBS Local Cell
resources).
RBS
Node B
resource
unavailable
No RBS resources
are available for
the Hsdsch.
Hsdsch
HW Failure
Configuration,
Dimensioning,
and/or Hardware
fault
The RNC
disables the HSDSCH resources
in the cell and
attempts to
activate them
when the HSDSCH is
unlocked.
Hsdsch
Requested
More than five HS- Configuration fault Hsdsch
configuration PDSCH codes are
not supported requested by the
RNC.
Message not Protocol error.
Configuration fault Hsdsch
compatible
with receiver
state
Semantic error The NBAP protocol Dimensioning fault Hsdsch
message
information is not
valid.
NbapTimeout
RBS
NbapError
An NBAP error
Hardware fault
occurred in the
remote node (for
example, the RBS
sent an Error
Indication in reply
to a physical
shared channel
reconfiguration
request message).
RBS
The RNC
disables the HSDSCH resources
in the cell and
attempts to
activate them
when the HSDSCH is
unlocked.
TU Hardware Fault
TU System Clock Path HW Fault
SCB System Clock Path HW Fault
Normally, the fault must be attended to on site, to remove the fault causing the
primary alarm.
As a consequence of the fault, the traffic is not affected because the alarm is issued
only on a node with duplicated clocks, which means that the fault does not have any
impact on Network Synchronization.
The likely cause is a fault in the main subrack on the following boards:
Alarm Causes
Fault Reason
An
The accumulated time Configuration
association is that an association is fault in own or
congested.
congested, is above remote node.
the configured
threshold.
MO.
disturbance.
An
The accumulated time Poor IP network M3uAssociation
association is that an association is quality, or
or
congested.
congested, is above incorrect network M3uaRemoteSp
the configured
planning.
MO.
threshold.
Note:
The alarm can appear as a result of a maintenance activity.
Loss of
messages,
and traffic
disturbance.
a
a
a
a
transmission fault
process or processor restart in this node
faulty General Purpose processor Board (GPB)
fault in the adjacent signalling node
Alarm Causes
Fault Reason
Fault
Location
The Local
No locally
Application
configured
Server (AS) is Signalling
DOWN.
Processes (SP) in
All
M3uaLocalAs
M3uaRemoteSp MO.
MOs serving this
M3uaLocalAs are
Impact
Signalling traffic
toward a specific
local AS is not
possible
Alarm Causes
Fault Reason
The Remote
Application
Server (AS) is
DOWN.
No Signalling
Processes (SP) in
the remote
Application Server
are accessible for
the local
Signalling
Processes.
Fault
Location
Impact
Signalling
traffic toward a
specific remote
AS is not
possible.
Note:
The alarm can be issued as a result of a maintenance activity.
Alarm Causes
Alarm
Cause
Description
Fault Reason
A Remote
SP is
Fault Location
Impact
ET board, or the
network.
No
signalling
disabled.
(SP) is not
accessible for the
related local
Signalling Process.
A Remote
SP is
disabled.
to the
remote SP
in the
adjacent
node.
The MO,
M3uaRemoteSp or
the MO,
M3uaRemoteSctpEp.
No
signalling
to the
remote SP
in the
adjacent
node.
Note:
The alarm can be issued as a result of a maintenance activity.
a
a
a
a
transmission fault
process or processor restart in this node
faulty ET board
fault in the adjacent signalling node
As a result of the fault, signalling traffic to an MTP3 user in the remote node is not
possible.
The possible causes are as follows:
33. NbapDedicated_RncRbsControlLinkDown
Description
This alarm is a primary alarm. The alarm is issued by the Managed Object (MO)
NbapDedicated.
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm Causes
One signaling
bearer (with
no
redundancy)
or both
signaling
Temporary
bearers (with
overload
redundancy)
problems in
for Node B
the Iub link
Application
An Exchange Part (NBAP)
Terminal Board dedicated
(ETB) failure in loses its
the RNC
assured
An ETB failure mode.
in the Radio
Base Station
(RBS)
Configuration or
dimensioning fault.
Multiple
module MP
faults or over
allocation of
UNI-SAAL
CEPs to the
module MPs
are preventing
allocation of
UNI-SAAL
terminations
Configuration or
dimensioning fault.
NbapDedicated
Hardware failure.
RNC ETB.
Hardware failure.
RBS ETB
Configuration or
dimensioning fault.
NbapDedicated
to module
MPs.
Note:
This alarm can appear as a result of maintenance activity.
Note:
This alarm may be preceded by alarms related to the following:
The Physical layer
The Asynchronous Transfer Mode (ATM) layer
An ETB
Alarm Causes
Alarm Cause
Description
Fault
Reason
IP network
problems
No impact on
traffic, if there is
a working
standby
synchronization
reference.
Traffic
disturbances can
occur, if there is
no working
standby
synchronization
reference.
Communication Unable to
problems
communicate with
toward NTP
NTP server due to
server
misconfiguration or
As above.
restarted.
As above.
35. PCH_NbapMessageFailure
Description
This alarm is a primary alarm. It is issued by the Managed Object (MO) Pch (Paging
Channel).
This alarm is issued when the RBS fails to set up PCH resources requested by the
RNC.
The possible alarm causes and fault locations are explained in Table 1.
Table 1
Alarm Causes
Fault Reason
Unknown CID
Configuration fault
Fault
Location
Pch
Cell not
available
The operational
state of the RBS
Local Cell is
Configuration fault
Pch
Impact
The RNC
disables
the Pch.
Requested
CCH attributes are
configuration outside the
not supported supported range.
Transport
resource
unavailable
Pch
Configuration fault
Pch
Pch
Dimensioning fault
Pch
Semantic
error
Dimensioning fault
Pch
Pch
UserPlane
Transport
Option
Mismatch
IubLink
Binding
Identity
Mismatch
Pch
Pch
Transport
The NBAP response Logical fault
Layer
from the RBS is
Address
without TLA or with
Mismatch
wrong TLA length.
Note:
This alarm can appear as a result of the maintenance activity.
36. PdrDevice_DeviceDisabled
Description
The alarm is a primary alarm. The alarm is issued by the Managed Object (MO)
PdrDevice.
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm Causes
Alarm
Cause
Description
Impact
Device
Disabled
The device
remains disabled
until it is enabled
by the operator
Note:
This alarm can appear as a result of the maintenance activity.
A
A
A
A
For SCB-DF and SCB-TF, the fault can be associated with any power inlet.
Description
The alarm is a primary alarm. It is issued by the MO Subrack.
The alarm is issued if the 48V DC power supply to a Switch Core Board (SCB, SCBDF or SCB-TF), to a Control Base Unit (CBU) or to a Digital Unit Board (DUL or DUW)
is lost or is outside the allowed voltage range. The optical indicators on the front of
the SCB-DF and SCB-TF indicate whether there is a voltage applied on a power inlet.
Other boards do not have such an indication.
The possible causes of the alarm are as follows:
A
A
A
A
For SCB-DF and SCB-TF, the fault can be associated with any power inlet.
39. Rach_InternalResourceUnavailable
This alarm is a primary alarm. The alarm is issued by the Managed Object (MO) Rach
(Random Access Channel).
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm Causes
The RNC is
Configuration or
unable to set dimensioning fault.
up Special
Purpose
Processor
(SP)
resources on
the associated
Rach.
Fault
Location
Rach
Rach
Impact
The RNC disables
the Rach.
IP resources
Note:
The RNC is
Configuration or
unable to set dimensioning fault.
up IP
resources on
the associated
Rach.
Rach
40. Rach_NbapMessageFailure
Description
This alarm is a primary alarm. The alarm is issued by the Managed Object (MO)
Rach.
This alarm is issued when the RBS fails to set up Random Access Channel (RACH)
resources requested by the RNC.
The possible alarm causes and fault locations are explained in the Table 1.
Table 1
Alarm Causes
Fault Reason
Fault
Location
Dimensioning fault Rach
Cell not
available
The operational
Configuration,
state of the RBS
Dimensioning,
Local Cell in the
and/or Hardware
RBS is Disabled
fault
(this can be caused
by faults in the
RBS Local Cell
resources).
RBS
Node B
resource
unavailable
No RBS resources
are available for
the Rach.
Configuration,
Dimensioning,
and/or Hardware
fault
Rach
Transport
resource
Configuration,
Dimensioning,
RBS
Impact
The RNC
disables the
Rach
unavailable
(AAL2) resources
available in the
RBS.
and/or Hardware
fault
HW Failure
Message not
compatible
with receiver
state
Protocol error.
Rach
The RNC
disables the
Rach
RBS
NbapError
An NBAP error
Hardware fault
occurred in the
remote node (for
example, the RBS
sent an Error
Indication in reply
to a physical
random access
channel
reconfiguration
request message).
RBS
Binding
Identity
Mismatch
Rach
Transport
The NBAP response Logical fault
Layer Address from the RBS is
Mismatch
without TLA or with
wrong TLA length.
Rach
41. Ranap_LocalFailure
Description
This is a Secondary alarm. The alarm is issued by the Managed Object (MO) Ranap.
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm Causes
Alarm
Cause
Description
Fault Reason
Transport
network
disturbances
between the
RNC and the
CN node.
Fault
Location
Ranap
Impact
The RNC loses
contact with the
CN node.
42. Ranap_RemoteFailure
Description
This is a Primary alarm. The alarm is issued by the Managed Object (MO) Ranap.
The possible alarm causes and fault locations are explained in the table below.
Table 1
Alarm
Cause
Alarm Causes
Description
Fault Reason
Fault
Location
Ranap
Transport
Either the RNC receives Configuration,
network
a signal indicating
hardware, and/or
errors
problems in the Core
dimensioning fault
between the Network (CN) node and
RNC and the timer
CN node.
UserOutOfServiceT
expires, or no Radio
Ranap
Restart in
Configuration,
Access
Network
the CN node
hardware, and/or
Application Part
or
dimensioning fault
intermediate (RANAP)
RESET_ACKNOWLEDGE
system.
message is received
Ranap
Radio
Configuration,
from the CN after
Access
hardware, and/or
configured
Impact
The RANAP
signaling link for
communication
with the CN
stops operating,
but lower
protocol levels
between the
RNC and the CN
may still be
operational.
Network
retransmissions of the dimensioning fault
Application RESET message have
Part
been sent to the CN.
(RANAP)
application
failure in the
RNC or the
CN node.
Note:
This alarm can appear as a result of maintenance activity.
This alarm may be related to the Ranap_LocalFailure alarm.
The influence on traffic from this alarm is indicated in the corresponding secondary
alarm.
If the board is duplicated in the subrack, traffic is not affected by repair activities. If
the board is not duplicated in the subrack, traffic is interrupted by the repair
activities.
The likely cause is a faulty SCB or CBU.
Alarm Causes
Alarm Cause
Description
Fault Reason
Fault Location
Hardware fault
TU
Impact
If the Timing
Unit is not
duplicated in
the node, the
fault can stop
or disturb the
traffic or the
network
synchronization