Vous êtes sur la page 1sur 74

4Motion and Mini-Centralized ASN-GW

Events and Alarms

Reference Guide
Release 2.5.2
December 2009
P/N: 215487

Document History

Document History
Topic

Description

Date Issued

First publication

General

Events and Alarms

Release 2.0M1,
September 2008
The document was completely revised and updated.

ii

Relaese 2.5.2
November 2009

Reference Guide

Contents

Contents
1. Introduction ......................................................................................... 1
2. Event and Alarm Notification Categories ........................................... 1
3. Event Types ......................................................................................... 2
3.1

Alarm Notification Event Types ................................................................................2

3.2

System Event Notification Event Types...................................................................3

3.3

Configuration Change Notification Event Types ....................................................3

4. Managed Object Types and Instances................................................ 3


5. Alarm Severities .................................................................................. 5
6. Threshold Crossing Alarms ................................................................. 6
7. Alarm Notifications ............................................................................. 7
7.1

Alarm Notification Structure .....................................................................................7

7.2

Description of Alarm Notifications ...........................................................................8

7.3

Base Station (BS) Alarms..........................................................................................9


7.3.1

bsFailureRateThresholdExceed (npuTraps 84)...............................................10

7.3.2

bsExcessMSNumber (npuTraps 83) ...............................................................10

7.3.3

bsExcessiveEapRounds (npuTraps 82) ..........................................................11

7.3.4

bsBestEffortDlDropPktRatioExceed (npuTraps 239).......................................11

7.3.5

bsRealTimeDlDropPktRatioExceed (npuTraps 240) .......................................12

7.3.6

bsNonRealTimeDlDropPktRatioExceed (npuTraps 241) ................................12

7.3.7

bsUgsDlDropPktRatioExceed (npuTraps 242) ................................................13

7.3.8

bsErtDlDropPktRatioExceed (npuTraps 243)..................................................14

7.3.9

bsHighUlmedianNoise (npuTraps 244) ...........................................................14

7.3.10 bsHighUl99PercentNoise (npuTraps 245).......................................................15

Events and Alarms

iii

Reference Guide

Contents

7.3.11 bsCommTimerExpire (npuTraps 70) ...............................................................15


7.3.12 bsAsnGwKeepAliveFailure (npuTraps 85) ......................................................16
7.4

7.5

7.6

PIU Alarms ................................................................................................................16


7.4.1

piuVersionMismatch (npuTraps 198)...............................................................16

7.4.2

piuPowerProblem (npuTraps 196)...................................................................17

7.4.3

piuUnitMissing (npuTraps 197)........................................................................17

PSU Alarms...............................................................................................................17
7.5.1

psuFaultyNoBackup (npuTraps 199)...............................................................17

7.5.2

psuUnitMissingNoBackup (npuTraps 203) ......................................................18

7.5.3

psuUnitOverTempNoBackup (npuTraps 205) .................................................18

7.5.4

psuFaultyWithBackup (npuTraps 200) ............................................................18

7.5.5

psuUnitMissingWithBackup (npuTraps 204) ...................................................19

7.5.6

psuUnitOverTempWithBackup (npuTraps 206)...............................................19

AU Alarms.................................................................................................................19
7.6.1

auIduTableError (npuTraps 13) .......................................................................20

7.6.2

auTxPowerControlProblem (npuTraps 41)......................................................20

7.6.3

auSynthesizerError (npuTraps 35) ..................................................................20

7.6.4

auHighTemperature (npuTraps 12) .................................................................21

7.6.5

auExtOnePpsInputFailure (npuTraps 9)..........................................................21

7.6.6

auInternalOnePpsInputFailure (npuTraps 17) .................................................21

7.6.7

auExternalClockFailure (npuTraps 8)..............................................................21

7.6.8

auInternalClockFailure (npuTraps 16) .............................................................22

7.6.9

auClockHoldoverMode (npuTraps 2)...............................................................22

7.6.10 auInterferenceClkHoldoverTimerExpired (npuTraps 15).................................22


7.6.11 auTxStDownClkHoldoverTimerExpired (npuTraps 42) ...................................23
7.6.12 auConfiguredNotInstall (npuTraps 4) ..............................................................23

Events and Alarms

iv

Reference Guide

Contents

7.6.13 connectivityAUPortDown (npuTraps 120) .......................................................23


7.6.14 auInternalPSfailure (npuTraps 18) ..................................................................24
7.6.15 auCommunicationsFailure (npuTraps 3) .........................................................24
7.6.16 auInitializationFailure (npuTraps 14) ...............................................................24
7.6.17 auUnitTypeMismatch (npuTraps 236) .............................................................25
7.6.18 auUnitTypeMismatch (npuTraps 236) .............................................................25
7.7

ODU Alarms ..............................................................................................................25


7.7.1

oduAuCommLost (npuTraps 182) ...................................................................25

7.7.2

oduTableDownloadfailure (npuTraps 191) ......................................................26

7.7.3

oduHighTemparature (npuTraps 186) .............................................................26

7.7.4

oduUnitTypeMismatch (npuTraps 192) ...........................................................26

7.7.5

oduHighVswrDetection (npuTraps 187) ..........................................................27

7.7.6

oduHwFailure (npuTraps 188).........................................................................27

7.7.7

oduHighOutbandInterference (npuTraps 184).................................................27

7.7.8

oduHighRxSignal (npuTraps 185) ...................................................................28

7.7.9

oduPowerAmplifierFailure (npuTraps 189)......................................................28

7.7.10 oduSynthesizerLockFailure (npuTraps 190)....................................................28


7.8

7.9

AVU Alarms ..............................................................................................................29


7.8.1

avuUnitMissing (npuTraps 46).........................................................................29

7.8.2

avuTotalFailure (npuTraps 45) ........................................................................29

7.8.3

avuAnyFanFailure (npuTraps 43)....................................................................29

Connectivity Alarms ................................................................................................30


7.9.1

connectivityBackhaulPortDown (npuTraps 121)..............................................30

7.9.2

connectivityManagementPortDown (npuTraps 123) .......................................30

7.9.3

connectivityCascadePortDown (npuTraps 122) ..............................................30

7.10 NPU Alarms ..............................................................................................................31

Events and Alarms

Reference Guide

Contents

7.10.1 npuTempLowThresholdExceed (npuTraps 174) .............................................31


7.10.2 npuTempHighThresholdExceed (npuTraps 173) ............................................31
7.10.3 npuRebootFromShadowFailure (npuTraps 156) .............................................32
7.10.4 npuSoftwareSwitchoverFailure (npuTraps 161) ..............................................32
7.10.5 npuExtOnePpsInputFailure (npuTraps 142)....................................................32
7.10.6 npuExternalClockFailure (npuTraps 141)........................................................32
7.10.7 npuInternalClockFailure (npuTraps 148) .........................................................33
7.10.8 npuClockHoldoverMode (npuTraps 130).........................................................33
7.10.9 npuInterferenceClkHoldoverTimerExpired (npuTraps 147).............................33
7.10.10 npuTxStDownClkHoldoverTimerExpired (npuTraps 177) ...............................34
7.10.11 npuCpuHardLimitExceed (npuTraps 138) .......................................................34
7.10.12 npuCpuSoftLimitExceed (npuTraps 228) .......................................................35
7.10.13 npuMemoryHardLimitExceed (npuTraps 152).................................................35
7.10.14 npuMemorySoftLimitExceed Alarm (npuTraps 229)........................................36
7.10.15 npu12VoltFailure (npuTraps 129)....................................................................36
7.10.16 npuFileErrorNpuConfig (npuTraps 144) ..........................................................37
7.11 Site Alarms ...............................................................................................................37
7.11.1 Dry Contact Alarms .........................................................................................37
7.11.2 sitesummarizedAlarm (npuTraps 217) ............................................................41
7.12 GPS Alarms ..............................................................................................................42
7.12.1 gpsCommunicationFailure (npuTraps 124) .....................................................42
7.12.2 gpsRcvLessSatellites (npuTraps 127).............................................................42
7.12.3 gpsLockNotAchieved (npuTraps 125) .............................................................43
7.12.4 gpsUnHealthy (npuTraps 128) ........................................................................43
7.13 ASN-GW Alarms .......................................................................................................43
7.13.1 asngwAaaUnreachable (npuTraps 226)..........................................................43

Events and Alarms

vi

Reference Guide

Contents

7.13.2 asngwAaaSwitchover (npuTraps 227).............................................................44

8. System Event Notification ................................................................ 45


8.1

System Event Notification Structure......................................................................45

8.2

Description of System Event Notifications............................................................45

8.3

NPU System Event Notifications ............................................................................46


8.3.1

npuCSTypeMismatch (npuTraps 221).............................................................46

8.3.2

npuInvalidSVIDCVID (npuTraps 222)..............................................................46

8.3.3

npuResetIntReason (npuTraps 160) ...............................................................47

8.3.4

npuResetExtReason (npuTraps 159) ..............................................................47

8.3.5

npuUnitExtracted (npuTraps 178) ...................................................................47

8.3.6

npuUnitInserted (npuTraps 179)......................................................................47

8.3.7

npuSwDownloadStart (npuTraps 164) ............................................................47

8.3.8

npuSwDownloadFinish (npuTraps 163) ..........................................................48

8.3.9

npuSysBootPerformed (npuTraps 166)...........................................................48

8.3.10 npuLoadingConfigFile (npuTraps 151) ............................................................48


8.3.11 npuLoadConfigFileSuccess (npuTraps 150) ...................................................48
8.3.12 npuSysShutdownPerformed (npuTraps 168) ..................................................49
8.3.13 npuConsoleSessionOpen (npuTraps 134) ......................................................49
8.3.14 npuTelnetSessionOpen (npuTraps 170) .........................................................49
8.3.15 npuConsoleSessionTimeout (npuTraps 137) ..................................................49
8.3.16 npuTelnetSessionTimeout (npuTraps 172) .....................................................50
8.3.17 npuConsoleSessionQuit (npuTraps 135) ........................................................50
8.3.18 npuTelnetSessionQuit (npuTraps 171.............................................................50
8.3.19 npuUserLoginSuccess (npuTraps 181) ...........................................................50
8.3.20 npuUserLoginFailure (npuTraps 180)..............................................................51
8.3.21 npuSysConfigFileChg (npuTraps 167) ............................................................51

Events and Alarms

vii

Reference Guide

Contents

8.3.22 npuNmsConnBsEstablish (npuTraps 154) ......................................................51


8.3.23 npuNmsConnBsLost (npuTraps 155) ..............................................................51
8.3.24 npuSwDownloadFailureInProgress (npuTraps................................................52
8.3.25 npuSwDownloadFailureServerNotConfigured
(npuTraps 230)52
8.3.26 npuSwDownloadFailureServerFailed (npuTraps 231).....................................52
8.3.27 npuSwDownloadFailureDecompressionFailed
(npuTraps 232)52
8.3.28 npuSwDownloadFailureHwSwNotCompatible
(npuTraps 233)53
8.3.29 npuSwDownloadFailureNameMismatch (npuTraps 234) ................................53
8.3.30 npuSwDownloadFailureFlashAccessFailed (npuTraps 235)...........................53
8.3.31 npuSwSwitchOverFailure (npuTraps 165).......................................................53
8.3.32 npuSwSetAsMainFailure (npuTraps 248)........................................................54
8.3.33 npuFileSignatureFailure (npuTraps 146).........................................................54
8.3.34 npuFileSaveFailure (npuTraps 145) ................................................................54
8.3.35 npuTrapRateExceeded (npuTrap 169)............................................................54
8.3.36 npuAUImageRepositoryModified (npuTraps 218) ...........................................54
8.3.37 npuSWSetAsMain (npuTraps 219)..................................................................55
8.3.38 npuAuSwDownloadStart (npuTraps 237) ........................................................55
8.3.39 npuAuSwDownloadFinish (npuTraps 238) ......................................................55
8.4

8.5

BS System Event Notifications...............................................................................55


8.4.1

bsKeepAliveFailure (npuTraps 246) ................................................................55

8.4.2

bsKeepAliveASNGWReboot (npuTraps 247)..................................................56

8.4.3

bsConnectivityOpportunisticASNGW (npuTraps 86)......................................56

PIU Event Notifications............................................................................................56


8.5.1

Events and Alarms

piuNonConfigInsertion (npuTraps 195) ...........................................................56

viii

Reference Guide

Contents

8.5.2
8.6

8.7

piuNonConfigExtraction (npuTraps 194) .........................................................56

PSU Event Notifications ..........................................................................................57


8.6.1

psuNonConfigInsertion (npuTraps 202) ..........................................................57

8.6.2

psuNonConfigExtraction (npuTraps 201) ........................................................57

AU Event Notifications ............................................................................................57


8.7.1

auResetIntReason (npuTraps 29) ...................................................................57

8.7.2

auResetExtReason (npuTraps 28) ..................................................................58

8.7.3

auNonConfigExtraction (npuTraps 23) ............................................................58

8.7.4

auNonConfigInsertion (npuTraps 24) ..............................................................58

8.7.5

auNonAvailablityOfAuSoftware (npuTraps 22)................................................58

8.7.6

auSwDownloadStart (npuTraps 32) ................................................................58

8.7.7

auSwDownloadFinish (npuTraps 31) ..............................................................59

8.7.8

auSysBootPerformed (npuTraps 36)...............................................................59

8.7.9

auLoadingConfigFile (npuTraps 20) ................................................................59

8.7.10 auLoadConfigFileSuccess (npuTraps 19) .......................................................59


8.7.11 auSysShutdownPerformed (npuTraps 37) ......................................................60
8.7.12 auPrimarySysConfigFileChanged (npuTraps 25)............................................60
8.7.13 auTxFrameLostDueToOverload (npuTraps 40................................................60
8.7.14 auSwitchoverFailureRebootFromShadow (npuTraps 33) ...............................60
8.7.15 auSwitchoverFailureSetAsMain (npuTraps 34) ...............................................60
8.8

ASN-GW Event Notifications...................................................................................61


8.8.1

npuMandQoSParamMissing (npuTraps 223) ..................................................61

8.8.2

asnGWSFInfoMismatch (npuTraps 220) .........................................................61

8.8.3

asnGwKeepAliveFailure (npuTraps 224).........................................................61

8.8.4

asnGwKeepAliveBSReboot (npuTraps 225) ...................................................61

Events and Alarms

ix

Reference Guide

Contents

9. Configuration Change Notifications.................................................. 62


9.1

Configuration Change Notification Structure........................................................62

9.2

Description of Configuration Change Notifications .............................................62

9.3

npuConfigChangeAddition (npuTraps 131)...........................................................63

9.4

npuConfigChangeDeletion (npuTraps 132) ...........................................................63

9.5

npuConfigChangeModification (npuTraps 133) ....................................................63

9.6

npuNeRepConfigurationChg (npuTraps 153)........................................................63

Events and Alarms

Reference Guide

Introduction

1.

Introduction
This document describes the alarm and event notifications (traps) in the 4Motion
Macro Indoor and Outdoor BTSs and in the Mini-Centralized ASN-GW.
The document covers the following topics:
Event and Alarm Notification Categories on page 1
Event Types on page 2
Managed Object Types and Instances on page 3
Alarm Severities on page 5
Threshold Crossing Alarms on page 6
Alarm Notifications on page 7
System Event Notification on page 45
Configuration Change Notifications on page 62

2.

Event and Alarm Notification Categories


The system supports the gollowing event and alarm notification categories
(eventCategory object):
alarmNotification (1): Alarm Notification is a persistent indication of a fault.
An alarm is said to be 'set' (or raised) when a fault is first detected and
administratively enabled. An alarm is said to be 'cleared' when a fault is first
noticed to have ceased or administratively disabled.
systemEventNotification (3): System Event Notification indicates an event
that is of interest to the operator of the management system, but is not
indicating any failure of the system or part of it. As such, system events carry
information only. They are not assigned with severity, and are not cleared by
any mechanism.
configurationChangeNotification (4): Configuration Change Notification
indicates an event related to a configuration change. In general, configuration
change notifications are issued by the device due to any configuration change
done on any managed object. This can be done by either the element

Events and Alarms

Reference Guide

Event Types

Alarm Notification Event Types

management system or by any other management entity (e.g. CLI). The


configuration change notification data include also the nature of change
(Create / Delete / Modify).
In some cases, more than one notification type may be issued due to a single
event. For example, creation of a new managed object that is not yet installed will
generate a configuration change notification and an alarm notification.

3.

Event Types
Each notification message includes also an indication on the event type
(eventType object). The available event types for the supported categories are:

3.1

Alarm Notification Event Types


The event types for Alarm Notifications are in accordance with ITU-T
recommendation X.733:
other (1): Used to report an alarm event not cobered by any of the following
alarm event types.
communicationsAlarm (2): Used to report when the object detects a
communications error.
qualityOfServiceAlarm (3): Used to report a failure in the quality of service of
the managed object.
processingErrorAlarm (4): Used to report processing failure in a managed
object.
equipmentAlarm (5): Used to report a failure in the equipment.
environmentalAlarm (6): used to report a problem in the environment.
integrityViolation (7): Used to report that a potential interruption in
information flow has occurred such that information may have been illegally
modified, inserted or deleted.
operationalViolation (8): Used to report that the provision of the requested
service was not possible due to the unavailability, malfunction or incorrect
invocation of the service.

Events and Alarms

Reference Guide

Managed Object Types and Instances

System Event Notification Event Types

physicalViolation (9): Used to report that a physical resource has been violated
in a way that indicates a potential security attack.
securityServiceOrMechanismViolation (10): Used to report that a security
attack has been detected by a security service or mechanism.
timeDomainViolation (11): used to report that an event has occurred at an
unexpected or prohibited time.

3.2

System Event Notification Event Types


Event types for System Event Notifications include:
neReportedSystemEvent (41)
npuSWDowloadSystemEvents (42)
auSWDowloadSystemEvents (43)
npuConfigurationFileSystemEvents (44)
auConfigurationFileSystemEvents (45)

3.3

Configuration Change Notification Event Types


Event types for Configuration Change Notifications include:
neReportedConfigurationChange (31)
entityAdded (32)
entityChanged (33)
entityRemoved (34)

4.

Managed Object Types and Instances


Each trap includes indication on the managed object (moType object) associated
with the event that triggered the trap (trap source). It also includes indication of
the MO instance (moInstance object)
The possible MO Types supported by the current release are:

Events and Alarms

Reference Guide

Managed Object Types and Instances

Configuration Change Notification Event Types

Table 1: MO Types and Instance Range


moType

moInstance Range

site(10)

asngw(20)

connectivity(31)

bs(45)

1-16777215 (the BS ID in
decimal format)

npu(51)

avu(52)

piu(53)

1-2

psu(54)

1-4

au(55)

Macro Indoor BTS: 1-4, 7-9


Macro Indoor BTS: 1-3, 7-9

gps(63)

odu(71)

Macro Indoor BTS:1-28


Macro Indoor BTS: 1-24

These Managed Objects represent physical entities (e.g. NPU, ODU) as well as
logical ones (e.g. ASN-GW, BS).
The following figure represents the slot IDs assigned to the Macro Indoor BTS
shelf modules:

Figure 1-1: 4Motion Shelf Slots Assignment


The following table details the mapping of Macro Outdoor BTS AUs to Slot
numbers:

Events and Alarms

Reference Guide

Alarm Severities

Configuration Change Notification Event Types

Table 1-1: Mapping of Outdoor Macro BTS AUs to Slot #

5.

AU

Slot #

AU of NAU

SAU

Master AU of DAU 1

Slave AU of DAU 1

Master AU of DAU 2

Slave AU of DAU 2

Alarm Severities
The Event Severity Value (eventSeverityValue) indicates how the capabilities of the
managed object has been affected by the alarming event. It represents the severity
of the alarm, as perceived by the managed object.
The Object Severity Value (objectSeverityValue) indicates the overall perceived
severity level of the managed object at the moment the alarm message was issued.
The severity levels defined in the system in accordance with ITU-T Rec X.733 are:
cleared (1): The Cleared severity level indicates the clearing of one or more
previously reported alarms. This alarm clears all alarms for this managed
object that have the same Alarm type, Probable cause and Specific problems (if
given).
indeterminate (2): The Indeterminate severity level indicates that the severity
level cannot be determined.
critical (3): The Critical severity level indicates that a service affecting
condition has occurred and an immediate corrective action is required. Such
a severity can be reported, for example, when a managed object becomes
totally out of service and its capability must be restored.
major (4): The Major severity level indicates that a service affecting condition
has developed and an urgent corrective action is required. Such a severity can
be reported, for example, when there is a severe degradation in the capability
of the managed object and its full capability must be restored.
minor (5): The Minor severity level indicates the existence of a non-service
affecting fault condition and that corrective action should be taken in order to
prevent a more serious (for example, service affecting) fault. Such a severity

Events and Alarms

Reference Guide

Threshold Crossing Alarms

Configuration Change Notification Event Types

can be reported, for example, when the detected alarm condition is not
currently degrading the capacity of the managed object.
warning (6): The Warning severity level indicates the detection of a potential or
impending service affecting fault, before any significant effects have been felt.
Action should be taken to further diagnose (if necessary) and correct the
problem in order to prevent it from becoming a more serious service affecting
fault.

6.

Threshold Crossing Alarms


Some alarm types relate to threshold crossing of a parameter. Such a parameter
may be a candidate for performance monitoring.
For threshold crossing alarm notifications only, the following fields provide
additional information:
thresholdId: The identification (a numerical code indicating the mib name) of
the threshold attribute that caused the notification.
thresholdLevel: The current level of the crossed threshold that caused the
notification.

NOTE
As some of the threshold level values may be modified by the EMS operator the actual threshold
value at the time of alarm notification generation is recorded

Events and Alarms

Reference Guide

Alarm Notifications

Alarm Notification Structure

7.

Alarm Notifications

7.1

Alarm Notification Structure


The following objects comprise the alarm notification:

Table 2: Alarm Notification Structure


No.

Object

Description

Site ID (siteId)

Integer. The Site number (0-999999)

Notification ID (notificationId)

Integer. Event sequence number.

Time Stamp (timeStamp)

DisplayString. The time (NE clock) at alarm


declaration. DisplayString in the format:
DD/MM/YYYY HH:MM:SS

MO Type (moType)

Integer. The code of the MO to which the alarm


is related. See Managed Object Types
and Instances on page 3.

MO Instance (moInstance)

Integer. The instance of the MO to which the


alarm is related. See Managed Object
Types and Instances on page 3.

Event Category (eventCategory)

Integer. The category code of the event:


alarmNotification (1)

Event Type (eventType)

Integer. The type code of the event. See

Alarm Notification Event Types on


page 2
This is the first level of definition of the alarm
event. Additional details may be provides by the
"ProbableCause" and "specificProblem" objects
described below
8

Probable Cause (probableCause)

Integer. The code representing the probable


cause of the event. This is the second level of
definition of the alarming event.
The supported Probable Causes are according
to the definition in ITU-T recommendation
M.3100M. See also the descriptions of specific
alarm notifications in the following sections.

Events and Alarms

Reference Guide

Alarm Notifications

Description of Alarm Notifications

Table 2: Alarm Notification Structure (Continued)


No.

Object

Description

Specific Problem Data (specificProblemData)

Integer, or an empty string. The code


representing the specific problem that caused
the event. This is the third level of definition of
the alarming event. See also the descriptions of
specific alarm notifications in the following
sections.
An empty string indicates Not Applicable.

10

Specific Problem Value (specificProblemValue)

Integer. Includes numerical values if needed (in


addition to the specific problem description).
String syntax

11

Event Severity Value (eventSeverityValue)

Alarm Perceived Severity: The perceived


severity of the alarm. For details see Alarm
Severities on page 5:

12

Object Severity Value (objectSeverityValue)

Object Perveived Severity: The overall perceived


severity level of the MO at the moment the alarm
message was issued. For details see Alarm
Severities on page 5.

13

Threshold ID (thresholdId)

Integer. Relevant for threshold-crossing alarms


only. Indicates the ID of the crossed threshold.
Set to trshldNotApplicable (22) for all other alarm
notifications. For details see Threshold
Crossing Alarms on page 6.

14

Threshold Level (thresholdLevel)

DisplayString. Relevant for threshold-crossing


alarms only. The current value of the threshold
that has been crossed. Set to a value of 0 for all
other alarm notifications.

7.2

Description of Alarm Notifications


In the following descriptions of specific Alarm Notifications the following objects
are not described (description/functionally do not depend on specific notification):
siteId
notificationId
timeStamp
moInstance

Events and Alarms

Reference Guide

Alarm Notifications

Base Station (BS) Alarms

eventCategory
objectSeverityValue
The following objects are described only when meaningful (other than Not
Applicable):
specificProblemData
specificProblemValue
thresholdId
thresholdLevel
The supported Alarm Notifications include the following groups:
Base Station (BS) Alarms on page 9
PIU Alarms on page 16
PSU Alarms on page 17
AU Alarms on page 19
ODU Alarms on page 25
AVU Alarms on page 29
Connectivity Alarms on page 30
NPU Alarms on page 31
Site Alarms on page 37
GPS Alarms on page 42
ASN-GW Alarms on page 43

7.3

Base Station (BS) Alarms


BS alarm notifications are not applicable for Mini-Centralized ASN-GW.

Events and Alarms

Reference Guide

Alarm Notifications

Base Station (BS) Alarms

moType for all BS alarm notifications is bs (10).

7.3.1

bsFailureRateThresholdExceed (npuTraps 84)


Description: The number of failed Authentication [EAP-Failure result (Auth
Complete TLV) R6 message from ASNGW] in a 15-minutes period has crossed the
pre-defined threshold.
In the management system, see Suspended EAP Process parameter in the BS
Connectivity Basic page, Authentication tab.
In CLI, use the following command to view the current value of this threshold:
npu# show auth-general bs <bs-id-lsb>
Use the following command to set a different value for this threshold:
npu(config-bs-<bs-id-lsb>)# auth-general suspendedeapprocthrshld.

Table 3: bsFailureRateThresholdExceed Objects

7.3.2

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Security service or mechanism violation (10)

Probable Cause

Authentication failure (600)

Specific Problem Data

Failure rate threshold exceeded (19)

Threshold ID

bsAlrmEapSuspendthrshld (6)

Threshold Level

0-10000. 0 means the alarm is disabled. Default value is 10000.

bsExcessMSNumber (npuTraps 83)


Description: The number of MSs in active operation state served by the BS
exceeded the threshold.
In the management system, see Active MSs parameter in the BS Connectivity
Basic page, Authentication tab.
In CLI, use the following command to view the current value of this threshold:
npu# show auth-general bs <bs-id-lsb>
Use the following command to set a different value for this threshold:
npu(config-bs-<bs-id-lsb>)# auth-general activemsthrshld.

Events and Alarms

10

Reference Guide

Alarm Notifications

Base Station (BS) Alarms

Table 4: bsExcessMSNumber Alarm Objects

7.3.3

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Quality of service alarm (3)

Probable Cause

System resources overload (207)

Specific Problem Data

Excessive MS number (16)

Threshold ID

bsAlrmActvMsthrshld (2)

Threshold Level

0-1024. 0 means the alarm is disabled. Default value is 1024.

bsExcessiveEapRounds (npuTraps 82)


Description: Excessive number of EAP messages in reauthentication session.
In the management system, see Maximum EAP Rounds parameter in the BS
Connectivity Basic page, Authentication tab.
In CLI, use the following command to view the current value of this threshold:
npu# show auth-general bs <bs-id-lsb>
Use the following command to set a different value for this threshold:
npu(config-bs-<bs-id-lsb>)# auth-general maxeaproundsthrshld.

Table 5: bsExcessiveEapRounds Alarm Objects

7.3.4

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Processing error alarm (4)

Probable Cause

Application subsystem failure (158)

Specific Problem Data

Excessive EAP rounds (15)

Threshold ID

bsAlrmMaxEapRndthrshld (9)

Threshold Level

0-100. 0 means the alarm is disabled. Default value is 100.

bsBestEffortDlDropPktRatioExceed (npuTraps 239)


Description: The DL dropped packets ratio (in promils), of DL packets in all Best
Effort services, has exceeded the threshold.
In the management system, see Best Effort parameter in the BS Radio Advanced
page, Management tab.

Events and Alarms

11

Reference Guide

Alarm Notifications

Base Station (BS) Alarms

In CLI, use the following command to view the current value of this threshold:
npu# show alrm-thrshld bs <bs-id-lsb>
Use the following command to set a different value for this threshold:
npu(config-bs-<bs-id-lsb>)# alrm-thrshld Be-exc-dl-drop-thr.

Table 6: bsBestEffortDlDropPktRatioExceed Objects

7.3.5

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Quality of Service alarm (3)

Probable Cause

Excessive DL dropped packets rate - best effort service (208)

Threshold ID

bsExcessiveDlDroppedPacketsRatioBestEffortThreshold (24)

Threshold Level

0-1000. 0 means the alarm is disabled. Default value is 1000.

bsRealTimeDlDropPktRatioExceed (npuTraps 240)


Description: The DL dropped packets ratio (in promils), of DL packets in all Real
Time services, has exceeded the threshold.
In the management system, see RT-VR parameter in the BS Radio Advanced page,
Management tab.
In CLI, use the following command to view the current value of this threshold:
npu# show alrm-thrshld bs <bs-id-lsb>
Use the following command to set a different value for this threshold:
npu(config-bs-<bs-id-lsb>)# alrm-thrshld rt-exc-dl-drop-thr.

Table 7: bsRealTimeDlDropPktRatioExceed Alarm Objects

7.3.6

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Quality of Service alarm (3)

Probable Cause

Excessive DL dropped packets rate - realtime service (208)

Threshold ID

bsExcessiveDlDroppedPacketsRatioRealTimeThreshold (25)

Threshold Level

0-1000. 0 means the alarm is disabled. Default value is 1000.

bsNonRealTimeDlDropPktRatioExceed (npuTraps 241)


Description: The DL dropped packets ratio (in promils), of DL packets in all Non
Real Time services, has exceeded the threshold.

Events and Alarms

12

Reference Guide

Alarm Notifications

Base Station (BS) Alarms

In the management system, see NRT-VR parameter in the BS Radio Advanced


page, Management tab.
In CLI, use the following command to view the current value of this threshold:
npu# show alrm-thrshld bs <bs-id-lsb>
Use the following command to set a different value for this threshold:
npu(config-bs-<bs-id-lsb>)# alrm-thrshld nrt-exc-dl-drop-thr.

Table 8: bsNonRealTimeDlDropPktRatioExceed Objects

7.3.7

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Quality of Service alarm (3)

Probable Cause

Excessive DL dropped packets rate - non real time service (210)

Threshold ID

bsExcessiveDlDroppedPacketsRatioNonRealTimeThreshold (26)

Threshold Level

0-1000. 0 means the alarm is disabled. Default value is 1000.

bsUgsDlDropPktRatioExceed (npuTraps 242)


Description: The DL dropped packets ratio (in promils), of DL packets in all UGS
services, has exceeded the threshold.
In the management system, see UGS parameter in the BS Radio Advanced page,
Management tab.
In CLI, use the following command to view the current value of this threshold:
npu# show alrm-thrshld bs <bs-id-lsb>
Use the following command to set a different value for this threshold:
npu(config-bs-<bs-id-lsb>)# alrm-thrshld ugs-exc-dl-drop-thr.

Table 9: bsUgsDlDropPktRatioExceed Objects


Object

Description

Alarm Severity

Minor (5)

Alarm Type

Quality of Service alarm (3)

Probable Cause

Excessive DL dropped packets rate - UGS service (211)

Threshold ID

bsExcessiveDlDroppedPacketsRatioUgsThreshold (27)

Threshold Level

0-1000. 0 means the alarm is disabled. Default value is 1000.

Events and Alarms

13

Reference Guide

Alarm Notifications

7.3.8

Base Station (BS) Alarms

bsErtDlDropPktRatioExceed (npuTraps 243)


Description: The DL dropped packets ratio (in promils), of DL packets in all
ERT-VR services, has exceeded the threshold.
In the management system, see UGS parameter in the BS Radio Advanced page,
Management tab.
In CLI, use the following command to view the current value of this threshold:
npu# show alrm-thrshld bs <bs-id-lsb>
Use the following command to set a different value for this threshold:
npu(config-bs-<bs-id-lsb>)# alrm-thrshld ert-exc-dl-drop-thr.

Table 10: bsErtDlDropPktRatioExceed Objects

7.3.9

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Quality of Service alarm (3)

Probable Cause

Excessive DL dropped packets rate - ERT service (212)

Threshold ID

bsExcessiveDlDroppedPacketsRatioErtThreshold (28)

Threshold Level

0-1000. 0 means the alarm is disabled. Default value is 1000.

bsHighUlmedianNoise (npuTraps 244)


Description: The uplink median noise level represents the median value of the
noise floor histogram.If the measured uplink median noise level exceeds the value
calculated as the target noise and interference level for the PUSC Zone plus the
value of the Uplink Median Noise parameter, an excessive uplink median noise
alarm will be generated.
In the management system, see Uplink Median Noise parameter in the BS Radio
Advanced page, Management tab.
In CLI, use the following command to view the current value of this threshold:
npu# show alrm-thrshld bs <bs-id-lsb>
Use the following command to set a different value for this threshold:
npu(config-bs-<bs-id-lsb>)# alrm-thrshld ul-mednoise.

Events and Alarms

14

Reference Guide

Alarm Notifications

Base Station (BS) Alarms

Table 11: bsHighUlmedianNoise Objects

7.3.10

Object

Description

Alarm Severity

Minor 5)

Alarm Type

Quality of Service alarm (3)

Probable Cause

High UL median noise(213)

Threshold ID

bsUlNoiseFloorMediandBmThreshold (29)

Threshold Level

-135 to -100 (dBm). Default value is -122.

bsHighUl99PercentNoise (npuTraps 245)


Description: The uplink 99% noise level represents the 99% value of the noise
floor histogram.If the uplink 99% noise level exceeds the value calculated as the
target noise and interference level for the PUSC Zone ( see Radio Advanced
Page-Power Control Tab on page 238) plus the value of the Uplink 99% Percentile
Noise parameter, an excessive uplink 99% percentile noise alarm will be
generated.
In the management system, see Uplink 99% Percentile Noise parameter in the BS
Radio Advanced page, Management tab.
In CLI, use the following command to view the current value of this threshold:
npu# show alrm-thrshld bs <bs-id-lsb>
Use the following command to set a different value for this threshold:
npu(config-bs-<bs-id-lsb>)# alrm-thrshld ul-99prcntnoise.

Table 12: bsHighUl99PercentNoise Objects

7.3.11

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Quality of Service alarm (3)

Probable Cause

High UL 99% noise(214)

Threshold ID

bsUlNoiseFloor99percentiledBmThreshold (30)

Threshold Level

-135 to -100 (dBm). Default value is -125.

bsCommTimerExpire (npuTraps 70)


Description: Communication timer expired for Autheticator <ASNGWID>.

Events and Alarms

15

Reference Guide

Alarm Notifications

PIU Alarms

Table 13: bsCommTimerExpire Objects

7.3.12

Object

Description

Alarm Severity

Major (4)

Alarm Type

Communications alarm (2)

Probable Cause

Communications Subsystem Failure (505)

Specific Problem Value

ASN-GW ID

bsAsnGwKeepAliveFailure (npuTraps 85)


Table 14: bsAsnGwKeepAliveFailure Objects

7.4

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Communication alarm (2)

Probable Cause

Communications Subsystem Failure (505)

Specific Problem Data

ASN-GW Keep-Alive Failure (66)

Specific Problem Value

ASN-GW IP Address

PIU Alarms
PIU alarm notifications are not applicable for Macro Outdoor BTS and
Mini-Centralized ASN-GW.
moType for all PIU alarm notifications is piu (53).

7.4.1

piuVersionMismatch (npuTraps 198)


Description: The installed PIU version is different from the PIU version that is
configured as required.

Table 15: piuVersionMismatch Objects


Object

Description

Alarm Severity

Indeterminate (2)

Alarm Type

Equipment alarm (5)

Probable Cause

Version Mismatch (166)

Events and Alarms

16

Reference Guide

Alarm Notifications

7.4.2

PSU Alarms

piuPowerProblem (npuTraps 196)


Description: The PIU is faulty, or the -48VDC input power of the PIU is outside the permissible
range.

Table 16: piuPowerProblem Objects

7.4.3

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Equipment alarm (5)

Probable Cause

Power problem (58)

piuUnitMissing (npuTraps 197)


Description: The configured PIU is not installed in the appropriate slot.

Table 17: piuUnitMissing Objects

7.5

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Equipment alarm (5)

Probable Cause

Replaceable unit is missing (62)

PSU Alarms
PSU alarm notifications are not applicable for Macro Outdoor BTS and
Mini-Centralized ASN-GW.
The minimum number of PSUs required for a configuration with up to 4 AUs is 2.
For a configuration with 5 or more AUs the minimum number of PSUs is 3. If PSU
redundancy is supported (more PSUs than the minimum required), it means there
is a backup PSU. Otherwise it means no backup.
moType for all PSU alarm notifications is psu (54).

7.5.1

psuFaultyNoBackup (npuTraps 199)


Description: The PSU is malfunctioning and does not have a backup module (no
redundancy), which may cause the system to be shut down.

Events and Alarms

17

Reference Guide

Alarm Notifications

PSU Alarms

Table 18: psuFaultyNoBackup Objects

7.5.2

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Unit failure - no redundant unit (52)

psuUnitMissingNoBackup (npuTraps 203)


Description: The PSU is configured but not installed in the appropriate slot. In
addition, there is no backup PSU module available for the missing PSU module
(no redundancy), and this condition may impact the functioning of the cell site.

Table 19: psuUnitMissingNoBackup Objects

7.5.3

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Unit missing - no redundant unit (54)

psuUnitOverTempNoBackup (npuTraps 205)


Description: The PSU is providing degraded output power because it is
overheated. In addition, no backup exists for this PSU, and this condition may
impact the functioning of the cell site.

Table 20: psuUnitOverTempNoBackup Objects

7.5.4

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Unit overtemperature - no redundant unit (56)

psuFaultyWithBackup (npuTraps 200)


Description: The PSU is malfunctioning; however a backup PSU exists for the
malfunctioning PSU module and the cell site can continue to operate normally.

Events and Alarms

18

Reference Guide

Alarm Notifications

AU Alarms

Table 21: psuFaultyWithBackup Objects

7.5.5

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Unit failure - redundant unit exists (53)

psuUnitMissingWithBackup (npuTraps 204)


Description: The PSU is configured but not installed; however a backup PSU
exists for the missing PSU module, and the cell site can continue to operate
normally.

Table 22: psuUnitMissingWithBackup Objects

7.5.6

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Equipment alarm (5)

Probable Cause

Replaceable unit missing (62)

Specific Problem Data

Unit missing - redundant unit exists (55)

psuUnitOverTempWithBackup (npuTraps 206)


Description: The PSU is providing degraded output power because it is
overheated; ; however a backup PSU exists for the malfunctioning PSU module,
and the cell site can continue to operate normally.

Table 23: psuUnitOverTempWithBackup Objects

7.6

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment Malfunction (514)

Specific Problem Data

Unit overtemperature - redundant unit exists (57)

AU Alarms
AU alarm notifications are not applicable for Mini-Centralized ASN-GW.
moType for all AU alarm notifications is au (55).

Events and Alarms

19

Reference Guide

Alarm Notifications

7.6.1

AU Alarms

auIduTableError (npuTraps 13)


Description: The AU has detected an internal hardware problem related to IDU
table.

Table 24: auIduTableError Objects

7.6.2

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

IDU table-burn failure (23)

auTxPowerControlProblem (npuTraps 41)


Description: The AU has detected an internal hardware problem related to Tx
power control.

Table 25: auTxPowerControlProblem Objects

7.6.3

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Tx power too high (51)

auSynthesizerError (npuTraps 35)


Description: The AU has detected an internal hardware problem related to the
synthesizer.

Table 26: auSynthesizerError Objects


Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Synthesizer lock failure (48)

Events and Alarms

20

Reference Guide

Alarm Notifications

7.6.4

AU Alarms

auHighTemperature (npuTraps 12)


Description: The temperature of the AU is higher than maximum permissible
limit.

Table 27: auHighTemperature Objects

7.6.5

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Environmental alarm (6)

Probable Cause

High temperature (123)

Specific Problem Data

High temperature (22)

auExtOnePpsInputFailure (npuTraps 9)
Description: The AU has lost its 1 PPS signal input from the NPU.

Table 28: auExtOnePpsInputFailure Objects

7.6.6

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Loss Of Synchronisation (76)

Specific Problem Data

External 1PPS source (18)

auInternalOnePpsInputFailure (npuTraps 17)


Description: A failure has occurred in the AU because of loss synchronization with
the internal 1PPS signal from the NPU.

Table 29: auInternalOnePpsInputFailure Objects

7.6.7

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Loss of synchronisation (76)

Specific Problem Data

Internal 1PPS source (25)

auExternalClockFailure (npuTraps 8)
Description: A failure has occurred in the AU because of loss synchronization with
the external 16 MHz signal.

Events and Alarms

21

Reference Guide

Alarm Notifications

AU Alarms

Table 30: auExternalClockFailure Objects

7.6.8

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Loss of synchronisation (76)

Specific Problem Data

External 16 MHz source (17)

auInternalClockFailure (npuTraps 16)


Description: Failure of the internal 16 MHz source.

Table 31: auInternalClockFailure Objects

7.6.9

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Loss of synchronisation (76)

Specific Problem Data

Internal 16 MHz source (24)

auClockHoldoverMode (npuTraps 2)
Description: The AU has entered the clock holdover mode because it is not
receiving the 1PPS signal from the NPU.

Table 32: auClockHoldoverMode Objects

7.6.10

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Timing problem (66)

Specific Problem Data

Clock holdover entered (10)

auInterferenceClkHoldoverTimerExpired (npuTraps 15)


Description: The timer that determines the maximum period for which the AU
should provide clock holdover for interference has expired.

Events and Alarms

22

Reference Guide

Alarm Notifications

AU Alarms

Table 33: auInterferenceClkHoldoverTimerExpired Objects

7.6.11

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Timing problem (66)

Specific Problem Data

Clock holdover interference timed out (11)

auTxStDownClkHoldoverTimerExpired (npuTraps 42)


Description: The AU has stopped data transmission after the timer that
determines the maximum period for which the AU should provide clock holdover
for Tx shut-down expires.

Table 34: auTxStDownClkHoldoverTimerExpired Objects

7.6.12

Object

Description

Alarm Severity

Critical (3)

Alarm Type

Equipment alarm (5)

Probable Cause

Timing problem (66)

Specific Problem Data

Clock holdover shut-down timed out (12)

auConfiguredNotInstall (npuTraps 4)
Description: The configured AU module is not installed in the specified slot.

Table 35: auConfiguredNotInstall Objects

7.6.13

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Not installed (38)

connectivityAUPortDown (npuTraps 120)


Description: AU malfunction.

Events and Alarms

23

Reference Guide

Alarm Notifications

AU Alarms

Table 36: connectivityAUPortDown Objects

7.6.14

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Replaceable unit problem (69)

Specific Problem Data

Port down (43)

auInternalPSfailure (npuTraps 18)


Description: The AU is malfunctioning because of a problem with the internal
power supply.

Table 37: auInternalPSfailure Objects

7.6.15

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Replaceable unit problem (69)

Specific Problem Data

Internal PS failure (26)

auCommunicationsFailure (npuTraps 3)
Description: Module ready indication was not received within the configured
timeout after AU became healthy.

Table 38: auCommunicationsFailure Objects

7.6.16

Object

Description

Alarm Severity

Major (4)

Alarm Type

Communications alarm (2)

Probable Cause

Communications subsystem failure (505)

Specific Problem Data

Module not ready (29)

auInitializationFailure (npuTraps 14)


Description: An initialization failure has occurred because the state change
indication was not received within the configured timeout after the AU has sent
the module ready indication.

Events and Alarms

24

Reference Guide

Alarm Notifications

ODU Alarms

Table 39: auInitializationFailure Objects

7.6.17

Object

Description

Alarm Severity

Major (4)

Alarm Type

Processing Error alarm (4)

Probable Cause

Initialization failure (174)

auUnitTypeMismatch (npuTraps 236)


Description: The installed AU type is different from the configured one.

Table 40: auUnitTypeMismatch Objects

7.6.18

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment Alarm (5)

Probable Cause

Replaceable Unit Type Mismatch (63)

auUnitTypeMismatch (npuTraps 236)


Description: The installed AU type is different from the configured one.

Table 41: auUnitTypeMismatch Objects

7.7

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment Alarm (5)

Probable Cause

Replaceable Unit Type Mismatch (63)

ODU Alarms
ODU alarm notifications are not applicable for Mini-Centralized ASN-GW.
moType for all ODU alarm notifications is odu (71).

7.7.1

oduAuCommLost (npuTraps 182)


Description: Communication lost between AU and ODU.

Events and Alarms

25

Reference Guide

Alarm Notifications

ODU Alarms

Table 42: oduAuCommLost Objects

7.7.2

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

No communication (33)

oduTableDownloadfailure (npuTraps 191)


Description: An error was detected while downloading a table to the ODU.

Table 43: oduTableDownloadfailure Objects

7.7.3

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Table download failure (49)

oduHighTemparature (npuTraps 186)


Description: The ODU temperature is too high.

Table 44: oduHighTemparature Objects

7.7.4

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Environmental alarm (6)

Probable Cause

High Temperature (123)

oduUnitTypeMismatch (npuTraps 192)


Description: The installed ODU type is different from the configured one.

Events and Alarms

26

Reference Guide

Alarm Notifications

ODU Alarms

Table 45: oduUnitTypeMismatch Objects

7.7.5

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Replaceable unit type mismatch (63)

Specific Problem Data

ODU type (39)

oduHighVswrDetection (npuTraps 187)


Description: The system detected VSWR (Voltage Standing Wave Ratio) value
higher than allowed.

Table 46: oduHighVswrDetection Objects

7.7.6

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Antenna failure (71)

Specific Problem Data

High VSWR (21)

oduHwFailure (npuTraps 188)


Description: The ODU has detected an internal hardware problem.

Table 47: oduHwFailure Objects

7.7.7

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment Malfunction (514)

oduHighOutbandInterference (npuTraps 184)


Description: High out-of-band interference is received.

Events and Alarms

27

Reference Guide

Alarm Notifications

ODU Alarms

Table 48: oduHighOutbandInterference Objects

7.7.8

Object

Description

Alarm Severity

Intermediate (2)

Alarm Type

Communication alarm (2)

Probable Cause

High interference (169)

Specific Problem Data

Out-of-band (41)

oduHighRxSignal (npuTraps 185)


Description: Rx signal level is too high.

Table 49: oduHighRxSignal Objects

7.7.9

Object

Description

Alarm Severity

Intermediate (2)

Alarm Type

Communication alarm (2)

Probable Cause

Receive failure (17)

Specific Problem Data

Rx signal too high (46)

oduPowerAmplifierFailure (npuTraps 189)


Description: Power amplifier failure has been detected.

Table 50: oduPowerAmplifierFailure Objects

7.7.10

Object

Description

Alarm Severity

Major (4) (2)

Alarm Type

Equipment alarm (5)

Probable Cause

Transmitter failure (67)

Specific Problem Data

Power amplifier (44)

oduSynthesizerLockFailure (npuTraps 190)


Description: The ODU has detected an internal hardware problem regarding the
synthesizer.

Events and Alarms

28

Reference Guide

Alarm Notifications

AVU Alarms

Table 51: oduSynthesizerLockFailure Objects

7.8

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Synthesizer lock failure (48)

AVU Alarms
AVU alarm notifications are not applicable for Macro Outdoor BTS.
moType for all AVU alarm notifications is avu (52).

7.8.1

avuUnitMissing (npuTraps 46)


Description: The AVU module is not installed in the chassis. (The PIU may be shut
down after this alarm is raised).

Table 52: avuUnitMissing Objects

7.8.2

Object

Description

Alarm Severity

Critical (3)

Alarm Type

Equipment alarm (5)

Probable Cause

Replaceable unit missing (62)

avuTotalFailure (npuTraps 45)


Description: A fault has occurred in the internal AVU circuitry (the system is
automatically shut down after this alarm is raised).

Table 53: avuTotalFailure Objects

7.8.3

Object

Description

Alarm Severity

Critical (3)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Total AVU failure (50)

avuAnyFanFailure (npuTraps 43)


Description: An AVU fan has failed.

Events and Alarms

29

Reference Guide

Alarm Notifications

Connectivity Alarms

Table 54: avuAnyFanFailure Objects

7.9

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

Non-Service-affecting AVU failure (34)

Connectivity Alarms
moType for all Connectivity alarm notifications is connectivity (31).

7.9.1

connectivityBackhaulPortDown (npuTraps 121)


Description: Connectivity with the DATA port has been lost.

Table 55: connectivityBackhaulPortDown Objects

7.9.2

Object

Description

Alarm Severity

Critical (3)

Alarm Type

Communications alarm (2)

Probable Cause

Communications subsystem failure (505)

Specific Problem Data

Backhaul (8)

connectivityManagementPortDown (npuTraps 123)


Description: Management port is down.

Table 56: connectivityManagementPortDown Alarm Objects

7.9.3

Object

Description

Alarm Severity

Minor (5)

Alarm Ype

Communications alarm (2)

Probable Cause

Communications subsystem failure (505)

Specific Problem Data

Management (40)

connectivityCascadePortDown (npuTraps 122)


This alarm is not applicable for the Macro Outdoor BTS.
Description: Connectivity with the CSCD port has been lost.

Events and Alarms

30

Reference Guide

Alarm Notifications

NPU Alarms

Table 57: connectivityCascadePortDown Alarm Objects

7.10

Object

Description

Alarm Severity

Major (4)

Alarm Type

Communications alarm (2)

Probable Cause

Communications subsystem failure (505)

Specific Problem Data

Cascade (9)

NPU Alarms
moType for all NPU alarm notifications is npu (51).

7.10.1

npuTempLowThresholdExceed (npuTraps 174)


Description: The NPU temperature is higher than the permitted temperature
threshold.

Table 58: npuTempLowThresholdExceed Objects

7.10.2

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Environmental alarm (6)

Probable Cause

High temperature (123)

Specific Problem Data

High temperature (22)

npuTempHighThresholdExceed (npuTraps 173)


Description: The NPU temperature is very high. The system is automatically shut
down when this alarm is raised.

Table 59: npuTempHighThresholdExceed Objects


Object

Description

Alarm Severity

Critical (3)

Alarm Type

Environmental alarm (6)

Probable Cause

High temperature (123)

Specific Problem Data

Very high temperature (58)

Events and Alarms

31

Reference Guide

Alarm Notifications

7.10.3

NPU Alarms

npuRebootFromShadowFailure (npuTraps 156)


Description: A failure has occurred while booting up the NPU with the shadow
image residing in the NPU flash.

Table 60: npuRebootFromShadowFailure Objects

7.10.4

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Processing Error alarm (4)

Probable Cause

Software switchover failure (168)

Specific Problem Data

Run from shadow failure (45)

npuSoftwareSwitchoverFailure (npuTraps 161)


Description: A failure has occurred while trying to set the shadow image as the
operational image.

Table 61: npuSoftwareSwitchoverFailure Objects

7.10.5

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Processing Error alarm (4)

Probable Cause

Software switchover failure (168)

Specific Problem Data

Set as main failure (47)

npuExtOnePpsInputFailure (npuTraps 142)


Description: The NPU has lost synchronization with the external 1PPS signal.

Table 62: npuExtOnePpsInputFailure Objects

7.10.6

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Loss of synchronisation (76)

Specific Problem Data

External 1PPS source (18)

npuExternalClockFailure (npuTraps 141)


Description: The NPU has lost synchronization with the GPS, and is unable to
receive the external 16 MHz signal.

Events and Alarms

32

Reference Guide

Alarm Notifications

NPU Alarms

Table 63: npuExternalClockFailure Objects

7.10.7

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Loss of synchronisation (76)

Specific Problem Data

External 16 MHz source (17)

npuInternalClockFailure (npuTraps 148)


Description: The NPU clock that provides the internal 16 MHz signal has failed.

Table 64: npuInternalClockFailure Objects

7.10.8

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Loss of synchronisation (76)

Specific Problem Data

Internal 16 MHz source (24)

npuClockHoldoverMode (npuTraps 130)


Description: The NPU is no longer receiving the 1PPS signal, and has entered the
clock holdover mode.

Table 65: npuClockHoldoverMode Objects

7.10.9

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Timing problem (66)

Specific Problem Data

Clock holdover entered (10)

npuInterferenceClkHoldoverTimerExpired (npuTraps 147)


Description: The timer that determines the maximum period for which the NPU
should provide holdover has expired.

Events and Alarms

33

Reference Guide

Alarm Notifications

NPU Alarms

Table 66: npuInterferenceClkHoldoverTimerExpired Objects

7.10.10

Object

Description

Alarm Severity

Critical (3)

Alarm Type

Equipment alarm (5)

Probable Cause

Timing problem (66)

Specific Problem Data

Clock holdover interference timed out (11)

npuTxStDownClkHoldoverTimerExpired (npuTraps 177)


Description: The NPU has stopped data transmission after the timer that
determines the maximum period for which the NPU should provide holdover
expires. This alarm is raised after the npuInterferenceClkHoldoverTimerExpired
alarm is raised.

Table 67: npuTxStDownClkHoldoverTimerExpired Objects

7.10.11

Object

Description

Alarm Severity

Critical (3)

Alarm Type

Equipment alarm (5)

Probable Cause

Timing Problem (66)

Specific Problem Data

Clock holdover shut-down timed out (12)

npuCpuHardLimitExceed (npuTraps 138)


Description:The hard limit for CPU resource utilization has been exceeded.
In CLI, use the following command to view the current value of the CPU hard
limit: npu# show resource limits
Use the following command to set a different value for the CPU hard limit:
npu(config)# limit cpu hardlimit <limit>.

Table 68: npuCpuHardLimitExceed Objects


Object

Description

Alarm Severity

Major (4)

Events and Alarms

34

Reference Guide

Alarm Notifications

NPU Alarms

Table 68: npuCpuHardLimitExceed Objects

7.10.12

Object

Description

Alarm Type

Processing Error alarm (4)

Probable Cause

CPU cycles limit exceeded (509)

Specific Problem Data

NPU CPU usage hard limit threshold (31)

Threshold ID

npuCpUsageHardLimitThreshold (15)

Threshold Level

1-99 (%). The default is 90 (%).

npuCpuSoftLimitExceed (npuTraps 228)


Description:The soft limit for CPU resource utilization has been exceeded.
In CLI, use the following command to view the current value of the CPU soft limit:
npu# show resource limits
Use the following command to set a different value for the CPU soft limit:
npu(config)# limit cpu softlimit <limit>.

Table 69: npuCpuSoftLimitExceed Objects

7.10.13

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Processing Error alarm (4)

Probable Cause

CPU cycles limit exceeded (509)

Specific Problem Data

NPU CPU usage soft limit threshold (64)

Threshold ID

npuCpUsageSoftLimitThreshold (16)

Threshold Level

1-99 (%). The default is 70 (%).

npuMemoryHardLimitExceed (npuTraps 152)


Description:The hard limit for memory utilization has been exceeded.
In CLI, use the following command to view the current value of the memory hard
limit: npu# show resource limits
Use the following command to set a different value for the memory hard limit:
npu(config)# limit memory hardlimit <limit>.

Events and Alarms

35

Reference Guide

Alarm Notifications

NPU Alarms

Table 70: npuMemoryHardLimitExceed Objects

7.10.14

Object

Description

Alarm Severity

Major (4)

Alarm Type

Processing Error alarm (4)

Probable Cause

Out of memory (162)

Specific Problem Data

NPU memory usage hard limit threshold (32)

Threshold ID

npuCpMemoryUsageHardLimitThreshold (17)

Threshold Level

1-99 (%). The default is 90 (%).

npuMemorySoftLimitExceed Alarm (npuTraps 229)


Description:The soft limit for memory utilization has been exceeded.
In CLI, use the following command to view the current value of the memory soft
limit: npu# show resource limits
Use the following command to set a different value for the memory soft limit:
npu(config)# limit memory softlimit <limit>.

Table 71: npuMemorySoftLimitExceed Alarm Objects

7.10.15

Object

Description

Alarm Severity

Minor (5)

Alarm Type

Processing Error alarm (4)

Probable Cause

Out of memory (162)

Specific Problem Data

NPU memory usage soft limit threshold (65)

Threshold ID

npuCpMemoryUsageSoftLimitThreshold (18)

Threshold Level

1-99 (%). The default is 70 (%).

npu12VoltFailure (npuTraps 129)


Description: The NPU module is unable to provide 12 Volts to the appropriate
devices.

Events and Alarms

36

Reference Guide

Alarm Notifications

Site Alarms

Table 72: npu12VoltFailure Objects

7.10.16

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

12 Volt Failure (61)

npuFileErrorNpuConfig (npuTraps 144)


Description: Configuration file is faulty.

Table 73: npuFileErrorNpuConfig Objects


Object

Description

Alarm Severity

Critical (3)

Alarm Type

Processing Error alarm (4)

Probable Cause

File error (161)

Specific Problem Data

NPU Configuration file (30)

Specific Problem Value

Operation (1)
Vendor (2)

7.11

Site Alarms
moType for all Site alarm notifications is site (10).
Site alarms include the following types of alarms:
Dry Contact Alarms
sitesummarizedAlarm (npuTraps 217)

7.11.1

Dry Contact Alarms


Dry Contact alarms are applicable only for the Macro Indoor BTS.
Dry Contact input alarms are external devices that are connected to the unit, and
notify the system when there is a change in external conditions. When the system
receives this notification, an alarm notification is raised, notifying the
administrator of the change indicated by the external device.

Events and Alarms

37

Reference Guide

Alarm Notifications

Site Alarms

Up to eight dry contact input alarms, each connected to a different pin on the
ALRM-IN connector, can be defined. The possible alarm conditions are:
Commercial power failure
Fire
Enclosure door open
High temperature
Flood
Low fuel
Low battery threshold
Generator failure
Intrusion detection
External equipment failure

For details on managing dry contact alarms using CLI, see the Managing
Dry-contact Input Alarms section in the System Manual. For details on managing
dry contact alarms using the management system see the Dry Contacts tab in the
Site Page.
According to actual mapping of dry contacts to alarm conditions, the following
alarm notifications may be supported (up to 8 different notifications):

7.11.1.1

sitePowerFailure (npuTraps 216)


Description: A failure has occurred in the external power supply.

Table 74: sitePowerFailure Objects


Object

Description

Alarm Severity

Minor (5)

Alarm Type

Environmental alarm (6)

Probable Cause

Commercial power failure (106)

Specific Problem Value

#1 to #8 (according to actual mapping of the alarm condition)

Events and Alarms

38

Reference Guide

Alarm Notifications

7.11.1.2

Site Alarms

siteFireDetection (npuTraps 209)


Description: A fire has been detected at the site where the chassis is located.

Table 75: siteFireDetection Objects

7.11.1.3

Object

Description

Alarm Severity

Critical (3)

Alarm Type

Environmental alarm (6)

Probable Cause

Fire (120)

Specific Problem Value

#1 to #8 (according to actual mapping of the alarm condition)

siteDoorOpen (npuTraps 207)


Description: The site door has been opened.

Table 76: siteDoorOpen Objects

7.11.1.4

Object

Description

Alarm Severity

Warning (6)

Alarm Type

Environmental alarm (6)

Probable Cause

Enclosure door open (118)

Specific Problem Value

#1 to #8 (according to actual mapping of the alarm condition)

siteHighTemperature (npuTraps 212)


Table 77: siteHighTemperature Objects

7.11.1.5

Object

Description

Alarm Severity

Warning (6)

Alarm Type

Environmental alarm (6)

Probable Cause

High temperature (123)

Specific Problem Value

#1 to #8 (according to actual mapping of the alarm condition)

siteFloodDetection (npuTraps 210)


Description: A flood has been detected at the site where the chassis is located.

Events and Alarms

39

Reference Guide

Alarm Notifications

Site Alarms

Table 78: siteFloodDetection Objects

7.11.1.6

Object

Description

Alarm Severity

Critical (3)

Alarm Type

Environmental alarm (6)

Probable Cause

Flood (121)

Specific Problem Value

#1 to #8 (according to actual mapping of the alarm condition)

siteLowFuelDetection (npuTraps 215)


Description: The fuel level of the backup generator is low.

Table 79: siteLowFuelDetection Objects

7.11.1.7

Object

Description

Alarm Severity

Warning (6)

Alarm Type

Environmental alarm (6)

Probable Cause

Low fuel (127)

Specific Problem Value

#1 to #8 (according to actual mapping of the alarm condition)

siteLowBatteryThreshold (npuTraps 214)


Description: The battery power level is low.

Table 80: siteLowBatteryThreshold Objects

7.11.1.8

Object

Description

Alarm Severity

Warning (6)

Alarm Type

Environmental alarm (6)

Probable Cause

Low battery threshold (112)

Specific Problem Value

#1 to #8 (according to actual mapping of the alarm condition)

siteGeneratorFailure (npuTraps 211)


Description: The backup mains generator is faulty.

Events and Alarms

40

Reference Guide

Alarm Notifications

Site Alarms

Table 81: siteGeneratorFailure Objects


Object

Description

Alarm Severity

Warning (6)

Alarm Type

Environmental alarm (6)

Probable Cause

Generator failure (111)

Specific Problem Value

#1 to #8 (according to actual mapping of the alarm condition)

7.11.1.9

siteIntrusionDetection (npuTraps 213)


Description: Intrusion into site where the chassis is located has been detected.

Table 82: siteIntrusionDetection Objects


Object

Description

Alarm Severity

Warning (6)

Alarm Type

Environmental alarm (6)

Probable Cause

Intrusion detection (126)

Specific Problem Value

#1 to #8 (according to actual mapping of the alarm condition)

7.11.1.10

siteExternalEquipmentFailure (npuTraps 208)


Description A failure has occurred in the relevant external equipment.

Table 83: siteExternalEquipmentFailure Objects

7.11.2

Object

Description

Alarm Severity

Warning (6)

Alarm Type

Environmental alarm (6)

Probable Cause

External equipment failure (135)

Specific Problem Value

#1 to #8 (according to actual mapping of the alarm condition)

sitesummarizedAlarm (npuTraps 217)


Summarized alarm is an indication on the status of the site as a whole, and is
related to the site as a managed object (MO). The summarized alarm behavior,
structure and applicable values obey the same definitions for alarm notification in
general.
The severity value of the summarized alarm reflects the highest severity value of
any open alarm of the site and all its descendant managed objects.

Events and Alarms

41

Reference Guide

Alarm Notifications

GPS Alarms

Table 84: sitesummarizeAlarm Objects


Object

Description

Alarm Severity

According to current status of the site:

Critical (3)
Major (4)
Minor (5)
Warning (6)
Indeterminate (2)

7.12

Alarm Type

Other (1)

Probable Cause

Summarized alarm (167)

GPS Alarms
GPS alarm notifications are not applicable for Mini-Centralized ASN-GW
moType for all GPS alarm notifications is gps (63).

7.12.1

gpsCommunicationFailure (npuTraps 124)


Description: A failure has occurred in the communication between the GPS
receiver and NPU.

Table 85: gpsCommunicationFailure Objects

7.12.2

Object

Description

Alarm Severity

Major (4)

Alarm Type

Communications alarm (2)

Probable Cause

Equipment malfunction (514)

Specific Problem Data

No communication (33)

gpsRcvLessSatellites (npuTraps 127)


Description: The GPS is synchronized to less than the minimum number of
satellites (4) at the time of initialization.

Events and Alarms

42

Reference Guide

Alarm Notifications

ASN-GW Alarms

Table 86: gpsRcvLessSatellites Objects

7.12.3

Object

Description

Alarm Severity

Major (4)

Alarm Type

Communications alarm (2)

Probable Cause

Degraded signal (3)

Specific Problem Data

Less than the minimum no. of satellites is received (27)

gpsLockNotAchieved (npuTraps 125)


Description: The GPS is synchronized to less than the minimum number of
satellites required to maintain synchronization.

Table 87: gpsLockNotAchieved Objects

7.12.4

Object

Description

Alarm Severity

Major (4)

Alarm Type

Communications alarm (2)

Probable Cause

Degraded signal (3)

Specific Problem Data

Lock not achieved

gpsUnHealthy (npuTraps 128)


Description: GPS problem.

Table 88: gpsUnHealthy Alarm Objects

7.13

Object

Description

Alarm Severity

Major (4)

Alarm Type

Equipment alarm (5)

Probable Cause

Replaceable unit problem (69)

Specific Problem Data

Not healthy (37)

ASN-GW Alarms
moType for all ASN-GW alarm notifications is asngw (20).

7.13.1

asngwAaaUnreachable (npuTraps 226)


This alarm notification is not applicable for the current release that does not
support AAA redundancy.

Events and Alarms

43

Reference Guide

Alarm Notifications

ASN-GW Alarms

Description: Both primary and secondary AAA servers are not reachable for the
AlrmAaaSwitchoverRetryFailThrshld within a measured period (PM interval).
Accounting and IP-CAN session transaction are also considered.

Table 89: asngwAaaUnreachable Alarm Objects

7.13.2

Object

Description

Alarm Severity

Major (4)

Alarm Type

Processing error alarm (4)

Probable Cause

Application subsystem failure (158)

Specific Problem Data

AAA Server Unreachable (62). Value: AAA alias

Specific Problem Value

AAA alias

Threshold ID

AlrmAaaSwitchoverRetryFailThrshld (23)

asngwAaaSwitchover (npuTraps 227)


This alarm notification is not applicable for the current release that does not
support AAA redundancy.
Description: Automatic switchover between AAA servers has occurred.

Table 90: asngwAaaSwitchover Objects


Object

Description

Alarm Severity

Minor (5)

Alarm Type

Processing error alarm (4)

Probable Cause

Application subsystem failure (158)

Specific Problem Data

AAA Server Switchover (63)

Specific Problem Value

AAA alias

Events and Alarms

44

Reference Guide

System Event Notification

System Event Notification Structure

8.

System Event Notification

8.1

System Event Notification Structure


The following objects comprise the system event notifications:

Table 91: System Event Notification Structure


No.

Object)

Description

siteId

Integer. The Site number (0-999999)

notificationId

Integer. Event sequence number.

timeStamp

DisplayString. The time (NE clock) at alarm declaration.


DisplayString in the format:
DD/MM/YYYY HH:MM:SS

moType

Integer. The code of the MO to which the alarm is related. See


Managed Object Types and Instances on page 3.

moInstance

Integer. The instance of the MO to which the alarm is related.


See Managed Object Types and Instances on
page 3.

eventCategory

Integer. The category code of the event:


systemEventNotification (3)

eventType

Integer. The type code of the event. See System Event

Notification Event Types on page 3


8

eventDescription (description of the


reported event)

Integer. A code indicating the proprietary description of the


event. For details see the descriptions of specific system
event notifications in the following sections.

eventSpecificData

DisplayString. One or more data fields (or an empty string), to


be concatenated with the text defined in the
"eventDescription" in predefined placeholders (specific to
each event description).

8.2

Description of System Event Notifications


In the following descriptions of specific System Event Notifications the following
objects are not described (description/functionally do not depend on specific
notification):
siteId
notificationId

Events and Alarms

45

Reference Guide

System Event Notification

NPU System Event Notifications

timeStamp
moInstance
eventCategory
The eventSpecificData object is described only when meaningful (other than Not
Applicable).
The supported System Event Notifications include the following groups:
NPU System Event Notifications on page 46
BS System Event Notifications on page 55
PIU Event Notifications on page 56
PSU Event Notifications on page 57
AU Event Notifications on page 57
ASN-GW Event Notifications on page 61

8.3

NPU System Event Notifications


moType for all system event notifications is npu (51)

8.3.1

npuCSTypeMismatch (npuTraps 221)


Table 92: npuCSTypeMismatch Event Notification Objects
Object

Description

Description

CS Type Mismatch (47)

Event Type

NE reported system event (41)

8.3.2

npuInvalidSVIDCVID (npuTraps 222)


Table 93: npuInvalidSVIDCVID Event Notification Objects
Object

Description

Description

Excessive assignment of SVID-CVID vector (48).

Event Type

NE reported system event (41)

Events and Alarms

46

Reference Guide

System Event Notification

8.3.3

NPU System Event Notifications

npuResetIntReason (npuTraps 160)


Table 94: npuResetIntReason Event Notification Objects
Object

Description

Description

Unit is going to perform reset due to internal reason (40)

Event Type

NE reported system event (41)

8.3.4

npuResetExtReason (npuTraps 159)


Table 95: npuResetExtReason Event Notification Objects
Object

Description

Description

Unit is going to perform reset due to external command (39)

Event Type

NE reported system event (41)

8.3.5

npuUnitExtracted (npuTraps 178)


Table 96: npuUnitExtracted Event Notification Objects
Object

Description

Description

Unit is being extracted from chassis (37)

Event Type

NE reported system event (41)

8.3.6

npuUnitInserted (npuTraps 179)


Table 97: npuUnitInserted Event Notification Objects
Object

Description

Description

Unit is being inserted into chassis (38)

Event Type

NE reported system event (41)

8.3.7

npuSwDownloadStart (npuTraps 164)


Table 98: npuSwDownloadStart Event Notification Objects
Object

Description

Description

SW download process has started (24)

Event Type

NPU S/W download system event (42)

Events and Alarms

47

Reference Guide

System Event Notification

8.3.8

NPU System Event Notifications

npuSwDownloadFinish (npuTraps 163)


Table 99: npuSwDownloadFinish Event Notification Objects
Object

Description

Description

SW download process has finished (23)

Event Type

NPU S/W download system event (42)

8.3.9

npuSysBootPerformed (npuTraps 166)


Table 100: npuSysBootPerformed Event Notification Objects
Object

Description

Description

System boot performed (27).

Event Type

NE reported system event (41)

8.3.10

npuLoadingConfigFile (npuTraps 151)


Table 101: npuLoadingConfigFile Trap Objects

Object

Description

Description

System loading configuration from (29)

Event Type

NPU configuration file system event (44)

Specific Data

The configuration file that is being loaded, i.e. <filename.cfg>.

8.3.11

npuLoadConfigFileSuccess (npuTraps 150)


Table 102: npuLoadConfigFileSuccess Event Notification Objects

Object

Description

Description

System successfully loaded configuration from (31)

Event Type

NPU configuration file system event (44)

Specific Data

The configuration file that was successfully loaded, i.e. <filename.cfg>.

Events and Alarms

48

Reference Guide

System Event Notification

8.3.12

NPU System Event Notifications

npuSysShutdownPerformed (npuTraps 168)


Table 103: npuSysShutdownPerformed Event Notification Objects

Object

Description

Description

System shutdown performed (30)

Event Type

NE reported system event (41)

8.3.13

npuConsoleSessionOpen (npuTraps 134)


Table 104: npuConsoleSessionOpen Event Notification Objects

Object

Description

Description

Console session Open (6).

Event Type

NE reported system event (41)

Specific Data

The session number of the opened session, i.e. <session#>.

8.3.14

npuTelnetSessionOpen (npuTraps 170)


Table 105: npuTelnetSessionOpen Event Notification Objects

Object

Description

Description

Telnet session open from (32)

Event Type

NE reported system event (41)

Specific Data

The session number and the IP address of the machine accessing the
NPU over Telnet, i.e. <session#><IP address>.

8.3.15

npuConsoleSessionTimeout (npuTraps 137)


Table 106: npuConsoleSessionTimeout Event Notification Objects

Object

Description

Description

Console session timed out (7)

Event Type

NE reported system event (41)

Specific Data

The session number of the session that has expired, i.e. <session#>.

Events and Alarms

49

Reference Guide

System Event Notification

8.3.16

NPU System Event Notifications

npuTelnetSessionTimeout (npuTraps 172)


Table 107: npuTelnetSessionTimeout Event Notification Objects

Object

Description

Description

Telnet session with timed out (33)

Event Type

NE reported system event (41)

Specific Data

The session number and the IP address of the machine for which the
session has expired, i.e. <session#><IP address>.

8.3.17

npuConsoleSessionQuit (npuTraps 135)


Table 108: npuConsoleSessionQuit Event Notification Objects

Object

Description

Description

Console session quit (8)

Event Type

NE reported system event (41)

Specific Data

The number of the session that is terminated, i.e. <session#>.

8.3.18

npuTelnetSessionQuit (npuTraps 171


Table 109: npuTelnetSessionQuit Objects

Object

Description

Description

Telnet session with quit (34)

Event Type

NE reported system event (41)

Specific Data

The session number and the IP address of the machine for which the
Telnet session is terminated, i.e. <session#><IP address>.

8.3.19

npuUserLoginSuccess (npuTraps 181)


Table 110: npuUserLoginSuccess Event Notification Objects

Object

Description

Description

Successful logon in session (2)

Event Type

NE reported system event (41)

Specific Data

The user name for logging in to the CLI and the session number,
i.e.<Username>, <session#>.

Events and Alarms

50

Reference Guide

System Event Notification

8.3.20

NPU System Event Notifications

npuUserLoginFailure (npuTraps 180)


Table 111: npuUserLoginFailure Event Notification Objects

Object

Description

Description

unsuccessful logon attempt within session (3)

Event Type

NE reported system event (41)

Specific Data

The user name for logging in to the CLI, and the session number for
which login was unsuccessful, i.e.<Username>, <session#>.

8.3.21

npuSysConfigFileChg (npuTraps 167)


Table 112: npuSysConfigFileChg Event Notification Objects

Object

Description

Description

Primary system configuration file changed (18)

Event Type

NPU configuration file system event (44)

8.3.22

npuNmsConnBsEstablish (npuTraps 154)


Table 113: npuNmsConnBsEstablish Event Notification Objects

Object

Description

Description

NMS connection established with NMS Module Agent of BS (14)

Event Type

NE reported system event (41)

Specific Data

The slot ID of the AU for which this event is applicable, i.e. <AU#>.

8.3.23

npuNmsConnBsLost (npuTraps 155)


Table 114: npuNmsConnBsLost Event Notification Objects

Object

Description

Description

NMS connection lost with NMS Module Agent of BS (15)

Event Type

NE reported system event (41)

Specific Data

The slot ID of the AU for which this event is applicable, i.e. <AU#>.

Events and Alarms

51

Reference Guide

System Event Notification

8.3.24

NPU System Event Notifications

npuSwDownloadFailureInProgress (npuTraps
Table 115: npuSwDownloadFailureInProgress Event Notification Objects

Object

Description

Description

Download failure to NPU (11)

Event Type

NPU S/W download system event (42)

Specific Data

One NPU image download is already in progress.

npuSwDownloadFailureServerNotConfigured
(npuTraps 230)

8.3.25

Table 116: npuSwDownloadFailureServerNotConfigured Event Notification Objects


Object

Description

Description

Download failure to NPU (11)

Event Type

NPU S/W download system event (42)

Specific Data

Tftp Server not configured

8.3.26

npuSwDownloadFailureServerFailed (npuTraps 231)


Table 117: npuSwDownloadFailureServerFailed Event Notification Objects

Object

Description

Description

Download failure to NPU (11)

Event Type

NPU S/W download system event (42)

Specific Data

Download of software from TFTP server failed.

8.3.27

npuSwDownloadFailureDecompressionFailed
(npuTraps 232)

Table 118: npuSwDownloadFailureDecompressionFailed Event Notification Objects


Object

Description

Description

Download failure to NPU (11)

Event Type

NPU S/W download system event (42)

Specific Data

Decompression of the downloaded zipped file failed.

Events and Alarms

52

Reference Guide

System Event Notification

NPU System Event Notifications

npuSwDownloadFailureHwSwNotCompatible
(npuTraps 233)

8.3.28

Table 119: npuSwDownloadFailureHwSwNotCompatible Event Notification Objects


Object

Description

Description

Download failure to NPU (11)

Event Type

NPU S/W download system event (42)

Specific Data

HW-SW compatibility check failed.

8.3.29

npuSwDownloadFailureNameMismatch (npuTraps 234)


Table 120: npuSwDownloadFailureNameMismatch Event Notification Objects

Object

Description

Description

Download failure to NPU (11)

Event Type

NPU S/W download system event (42)

Specific Data

Image name does not match with the image name in the descriptor file.

8.3.30

npuSwDownloadFailureFlashAccessFailed (npuTraps 235)


Table 121: npuSwDownloadFailureFlashAccessFailed Event Notification Objects

Object

Description

Description

Download failure to NPU (11)

Event Type

NPU S/W download system event (42)

Specific Data

Cannot access flash using file system.

8.3.31

npuSwSwitchOverFailure (npuTraps 165)


Table 122: npuSwSwitchOverFailure Event Notification Objects

Object

Description

Description

Switch-over failure : Reboot from Shadow (25)

Event Type

NPU S/W download system event (42)

Events and Alarms

53

Reference Guide

System Event Notification

8.3.32

NPU System Event Notifications

npuSwSetAsMainFailure (npuTraps 248)


Table 123: npuSwSetAsMainFailure Event Notification Objects

Object

Description

Description

Switch-over failure : Set as main (26)

Event Type

NPU S/W download system event (42)

8.3.33

npuFileSignatureFailure (npuTraps 146)


Table 124: npuFileSignatureFailure Event Notification Objects

Object

Description

Description

File signature failure (13)

Event Type

NPU configuration file system event (44)

8.3.34

npuFileSaveFailure (npuTraps 145)


Table 125: npuFileSaveFailure Event Notification Objects

Object

Description

Description

File save failure (12)

Event Type

NPU configuration file system event (44)

8.3.35

npuTrapRateExceeded (npuTrap 169)


Table 126: npuTrapRateExceeded Event Notification Objects

Object

Description

Description

TNPU Trap Rate Exceeded (42)

Event Type

NE reported system event (41)

8.3.36

npuAUImageRepositoryModified (npuTraps 218)


Table 127: npuAUImageRepositoryModified Event Notification Objects

Object

Description

Description

AU Image Repository at NPU modified (43)

Event Type

AU S/W download system event (43)

Events and Alarms

54

Reference Guide

System Event Notification

8.3.37

BS System Event Notifications

npuSWSetAsMain (npuTraps 219)


Table 128: npuSWSetAsMain Event Notification Objects

Object

Description

Description

NPU SW set as main (44)

Event Type

NPU S/W download system event (42)

8.3.38

npuAuSwDownloadStart (npuTraps 237)


Table 129: npuAuSwDownloadStart Event Notification Objects

Object

Description

Description

SW download process has started (24)

Event Type

AU S/W download system event (43)

8.3.39

npuAuSwDownloadFinish (npuTraps 238)


Table 130: npuAuSwDownloadFinish Event Notification Objects

Object

Description

Description

SW download process has finished (23)

Event Type

AU S/W download system event (43)

8.4

BS System Event Notifications


BS system event notifications are not applicable for Mini-Centralized ASN-GW.
MO Type for all BS system event notifications is bs (45).

8.4.1

bsKeepAliveFailure (npuTraps 246)


Table 131: bsKeepAliveFailure Event Notification Objects
Object

Description

Description

Keep Alive failure due to no Response from ASNGW (51)

Event Type

NE reported system event (41)

Specific Data

ASNGW IP address

Events and Alarms

55

Reference Guide

System Event Notification

8.4.2

PIU Event Notifications

bsKeepAliveASNGWReboot (npuTraps 247)


Table 132: bsKeepAliveASNGWReboot Event Notification Objects
Object

Description

Description

Keep Alive failure due to ASNGW reboot (52)

Event Type

NE reported system event (41)

Specific Data

ASNGW IP address

8.4.3

bsConnectivityOpportunisticASNGW (npuTraps 86)


Table 133: bsConnectivityOpportunisticASNGW Event Notification Objects
Object

Description

Description

Connectivity status of opportunistic ASNGW (53)

Event Type

NE reported system event (41)

Specific Data

<ASNGW IP address>, <Connection Status> (on/off)

8.5

PIU Event Notifications


PIU system event notifications are not applicable for Macro Outdoor BTS and
Mini-Centralized ASN-GW.
MO Type for all PIU system event notifications is piu (53)

8.5.1

piuNonConfigInsertion (npuTraps 195)


Table 134: piuNonConfigInsertion Event Notification Objects
Object

Description

Description

Non-configured unit is being inserted into chassis (17)

Event Type

NE reported system event (41)

8.5.2

piuNonConfigExtraction (npuTraps 194)


Table 135: piuNonConfigExtraction Event Notification Objects
Object

Description

Description

Non-configured unit is being extracted from chassis (16)

Event Type

NE reported system event (41)

Events and Alarms

56

Reference Guide

System Event Notification

8.6

PSU Event Notifications

PSU Event Notifications


PSU system event notifications are not applicable for Macro Outdoor BTS and
Mini-Centralized ASN-GW.
MO Type for all PSU system event notifications is psu (54)

8.6.1

psuNonConfigInsertion (npuTraps 202)


Table 136: psuNonConfigInsertion Event Notification Objects
Object

Description

Description

Non-configured unit is being inserted into chassis (17)

Event Type

NE reported system event (41)

8.6.2

psuNonConfigExtraction (npuTraps 201)


Table 137: psuNonConfigExtraction Event Notification Objects
Object

Description

Description

Non-configured unit is being extracted from chassis (16)

Event Type

NE reported system event (41)

8.7

AU Event Notifications
AU system event notifications are not applicable for Mini-Centralized ASN-GW.
MO Type for all AU system event notifications is au (55).

8.7.1

auResetIntReason (npuTraps 29)


Table 138: auResetIntReason Event Notification Objects
Object

Description

Description

Unit is going to perform reset due to internal reason (40)

Event Type

NE reported system event (41)

Events and Alarms

57

Reference Guide

System Event Notification

8.7.2

AU Event Notifications

auResetExtReason (npuTraps 28)


Table 139: auResetExtReason Event Notification Objects
Object

Description

Description

Unit is going to perform reset due to external command (39)

Event Type

NE reported system event (41)

8.7.3

auNonConfigExtraction (npuTraps 23)


Table 140: auNonConfigExtraction Event Notification Objects
Object

Description

Description

Non-configured unit is being extracted from chassis (16)

Event Type

NE reported system event (41)

8.7.4

auNonConfigInsertion (npuTraps 24)


Table 141: auNonConfigInsertion Event Notification Objects
Object

Description

Description

Non-configured unit is being inserted into chassis (17)

Event Type

NE reported system event (41)

8.7.5

auNonAvailablityOfAuSoftware (npuTraps 22)


Table 142: auNonAvailablityOfAuSoftware Event Notification Objects
Object

Description

Description

System event indication non-availablity of AU software in the CSGW (1)

Event Type

8.7.6

auSwDownloadStart (npuTraps 32)


Table 143: auSwDownloadStart Event Notification Objects
Object

Description

Description

SW download process has started (24)

Event Type

AU S/W download system event (43)

Events and Alarms

58

Reference Guide

System Event Notification

8.7.7

AU Event Notifications

auSwDownloadFinish (npuTraps 31)


Table 144: auSwDownloadFinish Event Notification Objects
Object

Description

Description

SW download process has finished (23)

Event Type

AU S/W download system event (43)

8.7.8

auSysBootPerformed (npuTraps 36)


Table 145: auSysBootPerformed Event Notification Objects
Object

Description

Description

System boot performed (27)

Event Type

NE reported system event (41)

8.7.9

auLoadingConfigFile (npuTraps 20)


Table 146: auLoadingConfigFile Event Notification Objects
Object

Description

Description

System loading configuration from (29)

Event Type

AU configuration file system event (45)

Specific Data

The configuration file that is being loaded, i.e. <filename.cfg>.

8.7.10

auLoadConfigFileSuccess (npuTraps 19)


Table 147: auLoadConfigFileSuccess Event Notification Objects

Object

Description

Description

System successfully loaded configuration from (31)

Event Type

AU configuration file system event (45)

Specific Data

The configuration file that was successfully loaded, i.e. <filename.cfg>.

Events and Alarms

59

Reference Guide

System Event Notification

8.7.11

AU Event Notifications

auSysShutdownPerformed (npuTraps 37)


Table 148: auSysShutdownPerformed Event Notification Objects

Object

Description

Description

System shutdown performed (30)

Event Type

NE reported system event (41)

8.7.12

auPrimarySysConfigFileChanged (npuTraps 25)


Table 149: auPrimarySysConfigFileChanged Event Notification Objects

Object

Description

Description

Primary system configuration file changed (18)

Event Type

AU configuration file system event (45)

8.7.13

auTxFrameLostDueToOverload (npuTraps 40
Table 150: auTxFrameLostDueToOverload Event Notification Objects

Object

Description

Description

A Tx frame was lost due to overload (4)

Event Type

NE reported system event (41)

8.7.14

auSwitchoverFailureRebootFromShadow (npuTraps 33)


Table 151: auSwitchoverFailureRebootFromShadow Event Notification Objects

Object

Description

Description

Switch-over failure : Reboot from Shadow (25)

Event Type

AU S/W download system event (43)

8.7.15

auSwitchoverFailureSetAsMain (npuTraps 34)


Table 152: auSwitchoverFailureSetAsMain Event Notification Objects

Object

Description

Description

Switch-over failure : Set as main (26)

Event Type

AU S/W download system event (43)

Events and Alarms

60

Reference Guide

System Event Notification

8.8

ASN-GW Event Notifications

ASN-GW Event Notifications


MO Type for all ASN-GW system event notifications is asngw (20)

8.8.1

npuMandQoSParamMissing (npuTraps 223)


Table 153: npuMandQoSParamMissing Event Notification Objects
Object

Description

Description

Mandatory Qos Parameter missing. (50)

Event Type

NE reported system event (41)

8.8.2

asnGWSFInfoMismatch (npuTraps 220)


Table 154: asnGWSFInfoMismatch Event Notification Objects
Object

Description

Description

The requested number of SFs exceeds CPE capability (49)

Event Type

NE reported system event (41)

Specific Data

MS ID

8.8.3

asnGwKeepAliveFailure (npuTraps 224)


Table 155: asnGwKeepAliveFailure Event Notification Objects
Object

Description

Description

Keep Alive failure due to no Response from BS (45)

Event Type

NE reported system event (41)

Specific Data

BS ID

8.8.4

asnGwKeepAliveBSReboot (npuTraps 225)


Table 156: asnGwKeepAliveBSReboot Event Notification Objects
Object

Description

Description

Keep Alive failure due to BS Reboot. (46)

Event Type

NE reported system event (41)

Specific Data

BS ID

Events and Alarms

61

Reference Guide

Configuration Change Notifications

Configuration Change Notification Structure

9.

Configuration Change Notifications

9.1

Configuration Change Notification Structure


The following objects comprise the configuration change notifications:

Table 157: Configuration-Change Notification Structure


No.

Object

Description

siteId

Integer. The Site number (0-999999)

notificationId

Integer. Event sequence number.

timeStamp

DisplayString. The time (NE clock) at alarm


declaration. DisplayString in the format:
DD/MM/YYYY HH:MM:SS

moType

Integer. The code of the MO to which the alarm is


related. See Managed Object Types and
Instances on page 3.

moInstance

Integer. The instance of the MO to which the alarm


is related. See Managed Object Types and
Instances on page 3.

eventCategory

Integer. The category code of the event:


systemEventNotification (3)

eventType

Integer. The type code of the event. See

Configuration Change Notification Event


Types on page 3
8

9.2

groupOid

DisplayString. The OID of the group of parameters


in which the change was detected. Set to 0 if the
changed parameter does not belong to a group. In
case of a change in a specific row of a table, this
field will be of the format "Table OID.Index" where
the Index value denotes the specific row index.

Description of Configuration Change Notifications


In the following descriptions of specific Configuration Change Notifications the
following objects are not described (description/functionally do not depend on
specific notification):
siteId
notificationId

Events and Alarms

62

Reference Guide

Configuration Change Notifications

npuConfigChangeAddition (npuTraps 131)

timeStamp
moInstance
eventCategory
groupOid

9.3

npuConfigChangeAddition (npuTraps 131)


Description: A new entity has been added to the configuration by an external
management operation.

Table 158: npuConfigChangeAddition Notification Objects


Object

Description

Event Type

entityAdded(32)

9.4

npuConfigChangeDeletion (npuTraps 132)


Description: An entity has been removed from the configuration by an external
management operation.

Table 159: npuConfigChangeDeletion Notification Objects


Object

Description

Event Type

entityRemoved(34)

9.5

npuConfigChangeModification (npuTraps 133)


Description: A parameter of the entity has been modified by by an external
management operation.

Table 160: npuConfigChangeModification Notification Objects

9.6

Object

Description

Event Type

entityChanged(33)

npuNeRepConfigurationChg (npuTraps 153)


Description: The entity has been changed by the system.

Events and Alarms

63

Reference Guide

Configuration Change Notifications

npuNeRepConfigurationChg (npuTraps 153)

Table 161: npuNeRepConfigurationChg Notification Objects


Object

Description

Event Type

neReportedConfigurationChange(31)

Events and Alarms

64

Reference Guide

Vous aimerez peut-être aussi