Sei sulla pagina 1di 37

1.

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

Fault Reason Fault Location

Impact

The air
surrounding
the node is
too warm.

The fan unit is


not able to
decrease the
temperature to
normal values.

The physical
environment
of the node is
too warm.

Too high temperature


can damage the
hardware. Traffic is
affected.

The Fan
unit is not
working
properly.

The Fan unit is


not cooling the
boards in the
subrack.

There can be The fault is


The subrack is not
one or more
located in the Fan being cooled. Boards
Fan alarms.
unit.
can be damaged.
The Fan
problem is the
main reason
for this alarm.

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 high temperature


can damage the
board. Traffic is
affected.

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

Fault Reason Fault


Location

Impact

Device
Disabled

The CcDevice is not


available.

Hardware fault SPB board

The device
remains disabled
until it is enabled
by the operator

Note:
This alarm can appear as a result of the maintenance activity.

3.

Configuration Version Corrupt

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

Configuration The Configuration


Version fault. Version (CV) is
corrupt.

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.

Contact to Default Router 0/1/2 Lost

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

Fault Reason Fault


Location

Impact

IP network
problem.

The traffic on the


network is disturbed.
This can be caused by
high traffic load, a
hardware fault or
wrong configuration of
the network.

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:

There is no impact on traffic at the IP Interface as long as at least one default


router is reachable. If all default routers are unreachable, it is not certain that
any traffic reaches a default router.

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

Fault Reason Fault


Location

Impact

Device
Disabled

The DcDevice is not


available

Hardware fault SPB board

The device
remains disabled
until it is enabled
by the operator

Note:

6.

This alarm can appear as a result of the maintenance activity.

Disk Volume C Full

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.

Too many UpgradePackage MOs, or the MOs are very large.


Large amounts of other files on the C volume (files that are not part of any
UpgradePackage MO).
The minimum free-space limit for the C volume is too large. That is, although
there is a sufficient amount of free space, the value of the attribute
minimumHdVolumeCFreespace in the MO ManagedElementData, is too small for
the C volume on the node.

Disk Volume D Full

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 UpgradePackage MOs, or the MOs are very large.


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.

Equipment Protection Hardware Fault

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 UpgradePackage MOs, or the MOs are very large.

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.

10. ET IP Hardware Fault


Description
The alarm is a primary alarm. The alarm is issued by the MO, ExchangeTerminalIp.
The possible alarm causes and fault locations are stated in additional text and
explained in the table below .
Table 1

Alarm
Cause

Alarm Causes

Description

Fault Reason Fault


Location

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.

11. Ethernet Switch Port Congestion


Description
This is a primary alarm, which is issued by the MO, EthernetSwitchModulePort.
The alarm is issued if the Ethernet switch port is becoming overloaded. The load is
80% or more of the maximum allowed load. The alarm remains as long as the port is
overloaded and ceases automatically when the load decreases. If the Ethernet switch
port becomes more overloaded, this alarm is replaced by the alarm, Ethernet
Switch Port Overload.
The possible alarm causes and fault locations are explained in the table below.
Table 1

Alarm Causes

Alarm
Cause

Description

Fault Reason Fault


Location

Impact

Faulty link(s) The alarm, Ethernet


in the node. Switch Port Fault,
is issued.

See alarm.

See alarm.

Ethernet frames
may be lost and
transmission
quality may
deteriorate.

Maintenance An Ethernet switch is


of Ethernet locked.
switches.

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.

Fault in the network.

UnderThe node or the


dimensioning network is underdimensioned.

12. Ethernet Switch Port Fault


Description
This is a primary alarm, which is issued by the MOs, EthernetSwitchPort and
EthernetSwitchModulePort.
The alarm is issued if the Ethernet Switch detects a "port fault" condition. The
operational state of the port is changed to DISABLED. The alarm remains as long as
the port is faulty. Normally, the fault must be attended to on site.
The possible alarm causes and fault locations are explained in the table below. The
alarm causes are stated in the additionalText.
Table 1

Alarm Causes

Alarm Cause

Description

Fault Reason Fault


Location

Link Down

The traffic on the link Hardware fault,


is disturbed.
network fault,
or configuration
fault.

Board,
Ethernet
network, or
configuration.

Impact
Disruption of
Ethernet traffic
on the affected
link.

Autonegotiation The traffic is switched Autonegotiation Ethernet


Failed to Meet at a lower condition has failed to
network.
Minimum
(speed, duplex or
meet the
Requirements both) than
minimum
configured.
configured
requirements.

Ethernet traffic
is slowed down
on the affected
link.

SFP Module
Mismatch

The SFP Module SFP Module


does not meet on the board.
all the initial
conditions.

Unable to switch
Ethernet traffic
on the affected
link.

Missing or
faulty
hardware.

Unable to switch
Ethernet traffic
on the affected
link.

The SFP Module is


not supported.

No SFP Module The SFP Module is


Installed
missing or is not
detected.

Board.

13. Ethernet Switch Port Overload


Description
This is a primary alarm, which is issued by the MO, EthernetSwitchModulePort.
The alarm is issued if the Ethernet switch port is overloaded. The load is 100% or
more of the maximum allowed load. The alarm remains as long as the port is
overloaded and ceases automatically when the load decreases. If the Ethernet switch
port load decreases, this alarm is replaced by the alarm, Ethernet Switch Port
Congestion.
The possible alarm causes and fault locations are explained in the table below.
Table 1

Alarm Causes

Alarm
Cause

Description

Fault Reason Fault


Location

Impact

Faulty link(s) The alarm, Ethernet


in the node. Switch Port Fault,
is issued.

See alarm.

See alarm.

Ethernet frames
are lost and
transmission
quality
deteriorates.

Maintenance An Ethernet switch is


of Ethernet
locked.
switches.

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.

Fault in the network.

UnderThe node or the


dimensioning. network is underdimensioned.

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

Alarm Cause Description Fault Reason

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

Alarm Cause Description


DL shared
channel type
not supported

Fault Reason

Configuration
The RBS local
fault.
cell does not
support EUL.
There are no HSDSCH Resources
set up in cell.

Unknown C-ID The RBS receives the

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

HW reject or does not


answer at setup of EDCH resources.

Requested
configuration
not supported

Hardware fault. HW

More than four


Configuration
E-AGCH and E- fault.
RGCH/E-HICH
codes are
requested by the
RNC.
Synchronized
setup is
requested.
Both HS-DSCH
and E-DCH
Resources are
set up or
reconfigured or
released in the
same message.
The following IEs
are set: HSDPA

Eul

and E-DCH
Cell Portion
Information
and Target
Non-serving
E-DCH to
Total E-DCH
Power ratio.

Either no EAGCH codes or


no E-HICH/ERGCH codes are
received in initial
message (setup).

Semantic error There are no E-AGCH


codes and no E-HICH/ERGCH codes received in
the initial message
(setup)

Eul

activate them
if the
Enhanced
uplink (Eul) is
unlocked in
that cell in the
RNC.

Note:

This alarm can appear as a result of maintenance activity.

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

Alarm Cause Description

Fault Reason

Unknown C-ID The RNC receives


an unknown Cell
Identification (CID).

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

There are no RBS Dimensioning fault


resources available
for the Secondary
Common Control
Physical Channel
(SCCPCH).

Fach

Transport
resource
unavailable

There are no Iub


Dimensioning fault
data stream (AAL2)
resources available
in the RBS.

Fach

Message not
compatible
with receiver
state

The requested
channel is already
set up.

Dimensioning fault

Fach

Semantic error The NBAP protocol Dimensioning fault


message
information is not
valid.

Fach

NbapTimeout

Fach

The remote node is Dimensioning fault


not responding.

Impact
The RNC
disables
the Fach.

UserPlane
Transport
Option
Mismatch

The NBAP response Configuration fault


TLA and BID from
the RBS do not
follow the selected
transport option.

IubLink

Binding
Identity
Mismatch

The NBAP response Logical fault


from the RBS is
without BID or with
wrong BID length.

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.

17. Failure of Protocol


Description
The alarm is a primary alarm. The alarm is issued by the MO Mspg or by the MO
MspgExtended.
The alarm is issued if unexpected K1 or K2 bits occur, which are not defined in the
protocol.
Normally, the alarm ceases automatically after matching bits are received.
If the alarm is issued by the MO Mspg, possible alarm causes and fault locations are
explained in Table 1.
Table 1

Alarm Causes for MO Mspg

Alarm Cause

Description

Fault Reason

Fault
Location

Impact

Failure of
Protocol

Mismatch of K1
and K2 bits

Configuration fault Local node or Possible loss


remote node of traffic

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 Causes for MO MspgExtended for ETSI and TTC

Alarm Cause

Description

Fault Reason

Fault
Location

Impact

fPAM (MSP
Architecture
mismatch)

Mismatch of K2 bit 5. Configuration


fault

Remote node Possible loss


of traffic

fINV (Invalid K1 Invalid K1 request or Configuration


request and/or
invalid signal number. fault
signal number)

Local node or Possible loss


remote node of traffic

fSCM (Signal
number
mismatch)

Local node or Possible loss


remote node of traffic

Mismatch of K2 bits Configuration


14 received from the fault
remote node and K1
bits 58 sent from
the local node.

fTMOUT (Request Incorrect response


Configuration
Local node or Possible loss
timeout)
(K1/K2 bits) from the fault
remote node of traffic
remote node. APS
timeout occurs.
Note:
The possible alarm causes fINV and fTMOUT can occur together. The alarm
causes fSCM and fTMOUT can also occur together.

18. Fan Air Temperature High


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 when the ambient temperature, supervised by the fan unit, is
above a specified limit, that is, when the temperature in degrees Celsius exceeds the
value of the attribute criticalAirTempAlarmLimit in the Fan MO. The alarm ceases
when the temperature falls below the value criticalAirTempAlarmLimit minus 3
degrees Celsius.
The alarm requires immediate actions and a site visit is necessary, unless it is caused
by a configuration fault.
Table 1

Alarm
Cause

Alarm Causes

Description

Fault Reason Fault


Location

Impact

The value of An irrelevant alarm is Configuration


the limit is
issued.
fault.
too low.

Configuration
of Fan MO.

A fault in the Climate control fault.


site cooling
or heating
equipment.

Fault in climate The node


control
equipment can
equipment for malfunction
the node.
temporarily, or be

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.

Air filter for


the air flow
through the
subrack.

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.

19. Fan Air Temperature Extremely High


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 when the ambient temperature, supervised by the fan unit, is
above a specified limit, that is, when the temperature in degrees Celsius exceeds the
value of the attribute criticalAirTempAlarmLimit in the Fan MO. The alarm ceases
when the temperature falls below the value criticalAirTempAlarmLimit minus 3
degrees Celsius.
The alarm requires immediate actions and a site visit is necessary, unless it is caused
by a configuration fault.
Table 1

Alarm
Cause

Alarm Causes

Description

Fault Reason Fault


Location

The value of An irrelevant alarm is Configuration


the limit is
issued.
fault.

Configuration
of Fan MO.

Impact
The temperature
alarms are not

too low.

reliable.

A fault in the Climate control fault.


site cooling
or heating
equipment.

Hardware
fault.

Fault in climate The node


control
equipment can
equipment for malfunction
the node.
temporarily, or be
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.

Air filter for


the air flow
through the
subrack.

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.

20. Fan HW Fault

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

Fault Reason Fault


Location

Impact

Fan
hardware
fault.

The fan is faulty.

Hardware
fault.

Subrack cooling
may not be
sufficient.

Fan uni.t

21. Fan Contact Fault


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, when the connection for supervising the fan is lost. The
operational state for the fan has been set to DISABLED. To investigate the cause, a
site visit may be necessary.
Table 1

Alarm Causes

Alarm
Cause

Description

Fault Reason Fault


Location

Impact

Configuration
fault or
hardware
fault.

Node
configuration
or SCB-DF
boards.

The state of the


fan is unknown.
Subrack cooling
may not be
sufficient, if the
fan stops
working.

No power
The fan is not working Hardware
supply to the because of power
fault.
fan.
failure.

Power supply
or power
cables.

The state of the


fan is unknown.
Subrack cooling
may not be
sufficient

Fan cables

Cable between The state of the

Both SCB-DF The operational state


boards are
for both SCB-DF
not
boards is DISABLED.
operational.

The fan is not working Hardware

not
connected.

because it is not
connected.

fault.

fan and SCBDF.

fan is unknown.
Subrack cooling
may not be
sufficient.

Fan fault.

The fan is faulty.

Hardware
fault.

Fan hardware. The state of the


fan is unknown.
Subrack cooling
may not be
sufficient.

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.

22. Fan Supervision Failure


Description
The alarm is a primary alarm. It is issued by the managed object, Fan.

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

Alarm Cause Description Fault Reason

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

Alarm Cause Description

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

Dimensioning 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

HW reject or does Hardware fault


not answer at
setup of HSDPA
resources.

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

The remote node is Hardware fault


not responding.

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.

25. Loss of System Clock


Description
The alarm is a secondary alarm. It is issued by the managed object, Synchronization.
The alarm is issued when one system clock plane is not available, in a node with
duplicated generation and distribution of the system or radio clock. The alarm
provides information about the fault indicated in the corresponding primary alarm.
The primary alarm can be:

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:

Timing Unit Board (TUB)


Switch Core Board (SCB)
Control Base Unit (CBU)

26. M3UA Association Congested


Description
The alarm is a primary alarm. The alarm is issued by the MOs, M3uAssociation or
M3uaRemoteSp.
The possible alarm causes and fault locations are explained in the table below.
Table 1

Alarm Causes

Alarm Cause Description

Fault Reason

An
The accumulated time Configuration
association is that an association is fault in own or
congested.
congested, is above remote node.

Fault Location Impact


M3uAssociation Loss of
or
messages,
M3uaRemoteSp and traffic

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.

27. M3UA Association Down


Description
The alarm is a primary alarm. The alarm is issued by the managed object,
M3uAssociation.
An alarm is issued when the Message Transfer Part level 3 (MTP3) detects a faulty
M3UA Association. The fault can be permanent or temporary.
As a result of the fault, if it is permanent, the signalling capacity is reduced.
The possible causes are as follows:

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

28. M3UA Local AS Down


Description
The alarm is a secondary alarm. The alarm is issued by the MO, M3uaLocalAs.
The possible alarm causes and fault locations are explained in the table below.
Table 1

Alarm Causes

Alarm Cause Description

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

the AS are active disabled.


toward the
remote Signalling
Process.
Note:

The alarm can be issued as a result of a maintenance activity.

29. M3UA Remote AS Down


Description
The alarm is a secondary alarm. The alarm is issued by the MO, M3uaRemoteAs.
The possible alarm causes and fault locations are explained in the table below.
Table 1

Alarm Causes

Alarm Cause Description

Fault Reason

The Remote
Application
Server (AS) is
DOWN.

All M3uaRemoteSp M3uaRemoteAs


MOs serving this
MO.
M3uaRemoteAs MO
are disabled.

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.

30. M3UA Remote SP Down


Description
The alarm is a primary alarm or a secondary alarm. The alarm is issued by the MO,
M3uaRemoteSp.
The possible alarm causes and fault locations are explained in the table below.
Table 1

Alarm Causes

Alarm
Cause

Description

Fault Reason

A Remote
SP is

A specific remote Hardware fault or


Signalling Process network fault.

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.

A specific remote Configuration fault.


Signalling Process
(SP) is not
accessible for the
related local
Signalling Process.

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.

31. MTP3b Link Out of Service


Description
The alarm is a primary alarm. The alarm is issued, by the managed object,
Mtp3bSlAnsi, Mtp3bSlChina, Mtp3bSlItu, or Mtp3bSlTtc, depending on the standard
that is used in the network.
An alarm is issued when the Message Transfer Part level 3 (MTP3) detects a faulty
MTP3b signalling link. The fault can be permanent or temporary.
As a result of the fault, the signalling capacity is reduced.
The possible causes are as follows:

a
a
a
a

transmission fault
process or processor restart in this node
faulty ET board
fault in the adjacent signalling node

32. MTP3b Route Set Unavailable


Description
The alarm is a primary alarm. The alarm is issued by the managed object, Mtp3bSrs.
An alarm is issued when a user of the Message Transfer Part level 3 (MTP3) in the
remote node is not accessible from this node. The fault can be permanent or
temporary.

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:

The MTP3 function in the remote node has restarted.


A processor for the MTP3 function in the remote node is faulty.

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

Alarm Cause Description Fault Reason


Temporary
disturbances
or
interruptions
in the Iub link

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

Fault Location Impact


NbapDedicated If the fault is
persistent, the
RNC drops all
calls.

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

34. NTP Server Reachability Fault


Description
The alarm is a primary alarm. The alarm is issued by the MO, IpSyncRef.
The alarm is issued when a Network Time Protocol (NTP) client detects a "not
reachability" condition toward an NTP Server, which has been configured as an IP
synchronization reference. The state of the faulty synchronization reference is
changed to NOT_REACHABLE. The alarm remains as long as the reference server is not
reachable.
The possible alarm causes and fault locations are explained in the table below.
Table 1

Alarm Causes

Alarm Cause

Description

Fault
Reason

Fault Location Impact

IP network
problems

The traffic on the


Dimensioning IP network
network is disturbed. or hardware
This can be caused
fault.
by high traffic load or
a hardware fault.

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

Configuration NTP server


or hardware
fault, or
server has

As above.

because the NTP


server is disabled.
Wrong IP
address

restarted.

IP address is invalid Configuration Synchronization As above.


or it points to a host fault.
configuration
that is not an NTP
fault
server.

DNS problems The DNS is not


Configuration DNS
performing its task in or hardware
translating domain
fault.
names into valid, upto-date IP addresses.
Wrong domain
name

As above.

Configuration Synchronization As above.


DN (domain
configuration
name) cannot fault.
fault
be resolved
DN resolved
to a host that
is not an NTP
server
DN resolved
to a nonexistent host

If there is a hardware fault, a site visit may be necessary.

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

Alarm Cause Description

Fault Reason

Unknown CID

The RNC receives


an unknown Cell
Identification (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.

Disabled. This can


be caused by faults
in the resources
used by the RBS
Local Cell.
Node B
resource
unavailable

There are no RBS


Dimensioning fault
resources available
for the Secondary
Common Control
Physical Channel
(SCCPCH).

Requested
CCH attributes are
configuration outside the
not supported supported range.
Transport
resource
unavailable

Pch

Configuration fault

Pch

There are no Iub


Dimensioning fault
data stream (AAL2)
resources available
in the RBS.

Pch

Message not The requested


compatible
channel is already
with receiver set up.
state

Dimensioning fault

Pch

Semantic
error

Dimensioning fault

Pch

NbapTimeout The remote node is Dimensioning fault


not responding.

Pch

UserPlane
Transport
Option
Mismatch

The NBAP response Configuration fault


TLA and BID from
the RBS do not
follow the selected
transport option.

IubLink

Binding
Identity
Mismatch

The NBAP response Logical fault


from the RBS is
without BID or with
wrong BID length.

Pch

The NBAP protocol


message
information is not
valid.

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

Fault Reason Fault


Location

Impact

Device
Disabled

The PdrDevice is not


available

Hardware fault SPB board

The device
remains disabled
until it is enabled
by the operator

Note:
This alarm can appear as a result of the maintenance activity.

37. Power Failure Left Slot


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

cable fault on the left side.


power supply fault on the left side.
voltage outside or close to the limit of the allowed voltage range.
hardware fault on the board.

For SCB-DF and SCB-TF, the fault can be associated with any power inlet.

38. Power Failure Right Slot

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

cable fault on the left side.


power supply fault on the left side.
voltage outside or close to the limit of the allowed voltage range.
hardware fault on the board.

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

Alarm Cause Description Fault Reason


ATM resources The RNC is
Configuration or
unable to set dimensioning fault.
up ATM
Adaptation
Layer type 2
(AAL2)
resources on
the associated
Rach.
SP resources

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

This alarm can appear as a result of maintenance activity.

More information about the alarm can be found in the additionalInfo


for the alarm. The probable alarm additional information and alarm
causes are shown in the table below.

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

Alarm Cause Description


Unknown C-ID The RNC receives
an unknown Cell
Identification (CID) error.

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

There are no Iub


data stream

Configuration,
Dimensioning,

RBS

Impact
The RNC
disables the
Rach

unavailable

(AAL2) resources
available in the
RBS.

and/or Hardware
fault

HW Failure

HW reject or does Hardware fault


not answer at
setup of Rach
resources.

Message not
compatible
with receiver
state

Protocol error.

Rach

Configuration fault Rach

The RNC
disables the
Rach

Semantic error The NBAP protocol Dimensioning fault Rach


message
information is not
valid.
NbapTimeout

The remote node is Hardware fault


not responding.

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

The NBAP response Logical fault


from the RBS is
without BID or with
wrong BID length.

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

Either the RNC


Configuration,
receives a signal
hardware, and/or
indicating
dimensioning fault
problems in the
Core Network (CN)
node and timer
Ranap
Restart in the UserOutOfServiceT Configuration,
expires,
or
the
CN node or
hardware, and/or
intermediate RNC receives an
dimensioning fault
indication that
system.
there are problems
Ranap
The RNC, or in the RNC and
Configuration,
one of its
hardware, and/or
timer
components SCCPDisableT
dimensioning fault
is faulty.
expires.

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.

43. SCCP Remote Subsystem Unavailable


Description
The alarm is a primary alarm. The alarm is issued by the managed object,
SccpApRemote.
An alarm is issued when a user of the Signalling Connection Control Part (SCCP) in
the remote node is not accessible from this node. The fault can be permanent or
temporary. Normally, the alarm is temporary and ceases automatically.
As a result of the fault, signalling traffic to an SCCP user in the remote node is not
possible.
The possible causes are as follows:

An SCCP user in the remote node has restarted.


A processor used by an SCCP user in the remote node is faulty

44. Switch Core Fault


Description
The alarm is a primary alarm. It is issued by the managed object, PlugInUnit.
One or more of these alarms is issued when there is a fault in the switch plane. A
switch plane is distributed on all boards in a switch module. In some cases, fault-free
units may be indicated as well. The alarm is also issued for a limited period of time
for a Switch Core Board (SCB) or a Control Board Unit (CBU) in connection with
upgrade, and node and board restart. In these cases, it is not necessary to act on an
alarm if it ceases spontaneously.
The fault must be attended to on site.

As a consequence of the alarm, there is one of the following secondary alarms:

Switch Plane A Fault


Switch Plane B Fault
Loss of Switch Redundancy Plane A
Loss of Switch Redundancy Plane B

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.

45. TU Hardware Fault


Description
The alarm is a primary alarm. It is issued by the MO, TimingUnit.
The alarm is issued if there is a fault in the generation of the system or radio clock
on a Timing Unit (TU). Normally, the fault must be attended to on site.
The alarm indicates the most likely faulty board to start from with repairing actions.
Table 1

Alarm Causes

Alarm Cause

Description

Fault in Timing Faulty TU


Unit hardware

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

Potrebbero piacerti anche