18

19
20

21

22
23

24
25

26

27

28
29

30

31

32
33

34

35
36

37

38
39

40

41
42

43

44
45

46

47
48

49

50
51

52

53
IMA Group Insufficient Links at Far End

Description

The alarm is issued when one or more Inverse Multiplexing ATM (IMA) links have
failed at the remote (far-end) node, reducing the number of working IMA
links within the IMA group to fewer than the configured "required number of links"
for the IMA group
As a consequence of the fault, the IMA group does not function
The likely cause is hardware failure in one or more IMA links, each of which issues
its own alarm

RNC End
lst <imagroup>
lk <imagroup>
lk <iublnk>
lst <utrancell>

RBS End

alt
st pp
st e1
lst 1-1-ima1
lacc vc eteloopback

Loss of Synch Reference Redundancy

Description
The alarm is issued if only one of a number of defined references is available
This can be caused by the fault indicated in a corresponding primary alarm
reasons
TU Synch Reference Loss of Signal
Network Synch Time from GPS Missing
Loss of Tracking
Synch Reference Path HW Fault
Synch Reference Not Reliable
PDH physical path termination
SDH physical path termination
IP Synchronization reference
get synchronization=1
get . syncRefStatus

Loss of System Clock

Description
The alarm is issued when no system clock is available in the node.
As a consequence of the fault, the traffic over the Synchronous Digital Hierarchy (SDH) or Plesiochronous Digital Hierarch
stopped or disturbed. Some slips or bit errors can occur since the clock is not locked to any timing reference an
required accuracy.
The likely cause is a fault in the main subrack on the following boards:
Timing Unit Board (TUB)
Switch Core Board (SCB)

get synchronization
st plug
get <TUB board proxy>

M3UA Association Down

Description
An alarm is issued when the Message Transfer Part level 3 (MTP3) detects a faulty M3UA Association. The fault can be
temporary.
As a result of the fault, if it is permanent, the signalling capacity is reduced.
The possible causes are as follows:
a transmission fault
a process or processor restart in this node
a faulty General Purpose processor Board (GPB)
a fault in the adjacent signalling node

lst m3uassociation
get <proxy>

Maximum Number of Counters Exceeded

Description

The alarm is a primary alarm. It is issued by the MO, ManagedElement.

The alarm is issued when there are too many active counters.
There is a limit to the total number of simultaneously active counters that are allowed. If the total number of a
becomes greater than the preset maximum number of allowed counters, this alarm is issued.
The alarm is only issued if the maximum limit is exceeded due to creation of new MO instances.
This alarm replaces the alarm, Large Number of Counters.
As a consequence of the fault, performance is degraded. Measurements are automatically suspended to keep t
counters below the limit. The most recently defined measurements are suspended first.
The alarm ceases when the number of active counters becomes lower than a preset percentage of the maximu
counters. The limits can be set in the MO, PmService.

get PmService

MTP3b Link Out of Service

The alarm is a primary alarm. The alarm is issued, by the managed object, Mtp3bSlAnsi, Mtp3bSlChina, Mtp3bS
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 fa
or temporary.
As a result of the fault, the signalling capacity is reduced.
The possible causes are as follows:
a transmission fault
a process or processor restart in this node
a faulty ET board
a fault in the adjacent signalling node

lst Mtp3bSpItu

MTP3b Route Set Unavailable

Description
An alarm is issued when a user of the Message Transfer Part level 3 (MTP3) in the remote node is not accessible from
can be permanent or temporary.
As a result of the fault, signalling traffic to an MTP3 user in the remote node is not possible.
1.The possible causes are as follows:
2.The MTP3 function in the remote node has restarted.
3.A processor for the MTP3 function in the remote node is faulty.

lst mtp3b
PacketDataRouter_CnNotRespondingToICMPEcho

The Internet Protocol (IP) address at the other end of the ATM Adaptation Layer type 5 (AAL5) Permanent Virtu
link does not respond to Internet Control Message Protocol (ICMP) echo request messages.

Pch_InternalResourceUnavailable

Description
Impact:The RNC disables the Pch.

Possible causes:
Faults in the ATM (Asynchronous Transfer Mode) Adaptation Layer type 2 (AAL2):The RNC is unable to set up AT

Faults on the Special Purpose Processor Board (SPB):The RNC is unable to set up SP resources.

Faults in the Pch IP resources:The RNC is unable to set up IP resources.

lst UtranCell=<NSEC24X>,pch=1

Pch_NbapMessageFailure

Description
This alarm is issued when the RBS fails to set up PCH resources requested by the RNC.

lst UtranCell=NSEC24X,pch=1

PDH Loss of Frame

Description
The alarm is issued when Plesiochronous Digital Hierarchy (PDH) frame alignment word cannot be found.
As a consequence of the fault, the traffic on the affected PDH physical link or affected Synchronous Digital Hierarchy (

The possible causes are as follows:

1.misconfigured framing between this and the remote node
Note:  The most likely misconfiguration is a wrong setting in the attribute, crc4Mode in the MOs, E1PhysPathTerm or E1T
2.PDH equipment failure in the remote node
3.a problem or a failure along the PDH physical line
3.ET or CBU failure in this node

lst <Subrack=MS,Slot=18,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=MS-18-2,Vc4Ttp=1,Vc12Ttp=
PdrDevice_DeviceDisabled

Description
There is some problem in SPB boards or SPB board goes faulty.

alt
std

Plug-In Unit General Problem

Description
The alarm is issued when:
All defined recovery attempts are performed for the PIU.
Contact with the PIU is lost for at least five minutes.
Possible causes
Repeated software errors.
Configuration fault.
Hardware faults that are not detected by hardware test,
Removed PIU.

st plug
get <proxy>

Plug-In Unit HW Failure

Description

This alarm is issued when a Plug-In Unit is marked faulty after a hardware test of the board.
The cause is that the software that handles the hardware has found an unrecoverable hardware fault

st plug

Power Failure Left Slot

Description

The alarm is issued if the –48V DC power supply to a Switch Core Board
is lost or is outside the allowed voltage range.

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

Power Failure Right Slot

Description

The alarm is issued if the –48V DC power supply to a Switch Core Board
is lost or is outside the allowed voltage range.

Alarm Causes
A cable fault on the right side.
A power supply fault on the right side.
A voltage outside or close to the limit of the allowed voltage range.
A hardware fault on the board.

Ranap_LocalFailure

Description
The RNC loses contact with the CN node.
Either the RNC receives a signal indicating problems in the Core Network (CN) node and timer UserOutOfService
receives an indication that there are problems in the RNC and timer SCCPDisableT expires.

st RANAP
lst m3uassociation

Ranap_RemoteFailure

Description
The RANAP signaling link for communication with the CN stops operating, but lower protocol levels between the
still be operational.
Either the RNC receives a signal indicating problems in the Core Network (CN) node and timer UserOutOfService
Radio Access Network Application Part (RANAP) RESET_ACKNOWLEDGE message is received from the CN after
retransmissions of the RESET message have been sent to the CN.
Possible causes:
Transport network errors between the RNC and the CN node.
Restart in the CN node or intermediate system.
Radio Access Network Application Part (RANAP) application failure in the RNC or the CN node.

alt
st RANAP
lst m3uaassociation

RncFeature_LicenseNot Valid

Description
There is no license key installed for an activated RNC feature.
There is no license key installed or The license key is expired

Impact:The RNC feature is disabled in case the RNC is not in emergency unlock state. In emergency unlock state the feature

license lkf

SCB System Clock Path HW Fault

Description
The alarm is issued when there is a fault in the distribution of the system clock on a Switch Core Board (SCB). Normally, the
attended to on site.
Faulty SCB or SXB
Between the SCB or Switch Extension Board (SXB) on the main subrack and the SCB in the extension subrack(IS
Faulty backplane in the subrack
Impact:If the system clock is not duplicated in the node, the fault can stop or disturb the traffic or the network synchronization

SCCP Remote Subsystem Unavailable

Description
An alarm is issued when a user of the Signalling Connection Control Part (SCCP) in the remote node is not accessible fr
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:
1.An SCCP user in the remote node has restarted.
2.A processor used by an SCCP user in the remote node is faulty
Check:In the alarm list, identify any signalling route set, Mtp3bSrs, that is related to the instance of the remote access
SccpApRemote.

lst mtp3bsrs
Switch Core Fault

Description

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
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.
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

Switch Internal Link Fault

Description
One or more of these alarms are issued when there is a communication fault
in an Inter-Switch module Link (ISL) between the main switch module and an extension
switch module in the node. It is possible that fault-free units can also be indicated.

there is one of the following secondary alarms:

Switch Internal Link Group 0 Fault
Switch Internal Link Group 1 Fault
Switch Internal Link Group 2 Fault
Switch Internal Link Group 3 Fault
Loss of Link Redundancy Group 0
Loss of Link Redundancy Group 1
Loss of Link Redundancy Group 2
Loss of Link Redundancy Group 3

lst InternalLinkGroup

Switch Plane A Fault

Description
The alarm is a secondary alarm. It issued by the managed object, SwitchModule.
The alarm is issued when there is a fault in the active switch plane in a switch module
As a consequence of the fault, the traffic is lost

The likely cause is that it is a consequence of the primary alarms:

Switch Core Fault
Switch Port Fault

Switch Plane B Fault

Description

The alarm is a secondary alarm. It issued by the managed object, SwitchModule.

The alarm is issued when there is a fault in the active switch plane in a switch module
As a consequence of the fault, the traffic is lost

The likely cause is that it is a consequence of the primary alarms:

Switch Core Fault
Switch Port Fault

Switch Port Fault

Description

The alarm is a primary alarm. It 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.

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

Loss of Switch Redundancy Plane A

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

SXB System Clock Path HW Fault

Description
The alarm is issued when there is a fault in the distribution of the system clock of a Switch Extension Board (SX
fault must be attended to on site.
Alarm Cause
Faulty SXB
Between the SXB on the main subrack and the Switch Core Board (SCB) in the extension subrack
Faulty SCB
Faulty backplane in the subrack

System Clock Quality Degradation

Description
The alarm is issued if the system or radio clock enters the free-running mode in a Timing Unit (TU). It gives information ab
in the corresponding primary alarm, which can be:
1.TU Synch Reference Loss of Signal
2.Network Synch Time from GPS Missing
3.Loss of Tracking
4.Synch Reference Path HW Fault
5.Synch Reference Not Reliable
Impact:Traffic is not disturbed

TU Hardware Fault

Description
The alarm is issued if there is a fault in the generation of the system or radio clock on a Timing Unit (TU). Norm
be attended to on site.
Impact:If the Timing Unit is not duplicated in the node, the fault can stop or disturb the traffic or the network synchronization

st plug

UtranCell_NbapReconfigurationFailure

Description
The UtranCell_NbapReconfigurationFailure alarm is a primary alarm. The alarm is issued by the Managed
UtranCell.
RBS does not provide the configured output power due to some internal hardware problems.

Note:  
RNC will internally set a reference value representing the previously configured maximumTransmissionPower in
issued if the RBS reports a degradation of its maxPowerCapDl below 2dB.

lst utrancell=< >

lk iublink= <>
lk <imagroup>

UtranCell_ServiceUnavailable

Description
Termination of the RNC NBAP common signaling to the Radio Base Station (RBS) is failing, due to errors in the
between the RNC and the RBS, or due to hardware faults in the RNC.
The RBS resource handling algorithm can not find any RNC module in operational state "enabled" which has sp
This can be because the maximum number of IubLinks has been reached for all enabled modules, or because t
of UtranCells has been reached for all enabled modules.

lst utrancell=< >

lk iublink= <>
lk <imagroup>

UtranCell_NbapMessageFailure

This alarm is issued when the Radio Base Station (RBS) cannot fulfill the request to set up a UTRAN Cell issued
Network Controller (RNC).

lst utrancell=< >

lk iublink= <>
lk <imagroup>

VC4 Degraded Signal

Description
The alarm is issued when a specified number of the consecutive bad seconds has been detected. A second is de
detected percentage of the block errors is equal to, or greater than, the specified percentage. The values of the
(vcDegM attribute in the MO, Vc4Ttp) and errored blocks (vcDegThreshold attribute in the MO, Vc4Ttp) can be
values are 7 seconds and 30%, respectively. The alarm indicates that the VC4 (Virtual Channel) path through t
Digital Hierarchy (SDH) transport network is affected by bit errors.
As a consequence of the fault, the traffic continues to run, but with quality degraded.
The possible causes are as follows:
a faulty board
a service degradation on the optical receiver
a faulty laser
a transmission media fault

st vc4ttp 

VC4 Loss of MultiFrame

Description
The alarm is issued when there is a mismatch between the H4 bytes in Virtual Container 4 Path Overhead (VC4
two consecutive multiframes.
As a consequence of the fault, the traffic on the affected Synchronous Digital Hierarchy (SDH) link is lost.
The possible causes are as follows:

a transmitter fault in the remote node

a fault in this node
the alarms, VC4 Degraded Signal, or VC4 Remote Defect Indication

st vc4ttp 

VC4 Remote Defect Indication

Description

The alarm is generated when the Remote Defect Indication (RDI) bit is set in the Virtual Container 4 Path Over
As a consequence of the fault, the traffic on the affected VC4 path is lost.
The likely cause is a fault within the Synchronous Digital Hierarchy (SDH) transport network, in the remote nod

st vc4ttp 

VC4 Unequipped Defect

Description
The alarm is generated when the C2 byte received in Virtual Container 4 Path Overhead (VC4 POH) contains th
in five consecutive frames. The alarm indicates that there is no payload on the affected VC4.
As a consequence of the fault, the traffic on the affected VC4 path is lost.
The likely cause is that an Synchronous Digital Hierarchy (SDH) VC4 cross-connection has been removed from,
SDH transport network, resulting in a configuration problem.
lt all  (load all proxies)

st vc4ttp 

lpget vc4ttp 
they should be enabled and unlocked
they should be enabled and unlocked
they should be enabled and unlocked
they should be enabled and unlocked

they should be enabled and unlocked

they should be enabled and unlocked
they should be enabled and unlocked
all should be true
nodeSystemClock in locked mode
All values should be 3

they should be enabled and unlocked

they should be enabled and unlocked

no of counter less than
warningAlarmLimitPercent

op. State should be enable

op. State should be enable

op. State should be enable

op. State should be enable

op. State should be enable

they should be enabled and unlocked

Op. State should be enable

All should be enable
All should be enable
All should be enable
they should be enabled and unlocked
they should be enabled and unlocked
they should be enabled and unlocked
they should be enabled and unlocked
check weather ima link up/down

they should be enabled and unlocked

they should be enabled and unlocked
check weather ima link up/down

they should be enabled and unlocked

they should be enabled and unlocked
check weather ima link up/down
they should be enabled and unlocked

they should be enabled and unlocked

they should be enabled and unlocked

(Show status of VC4 high order proxies
they should be enabled and unlocked )

(Look for incrementing counters on the

following counters pmVcBbe/ES/SES with
a value above zero)