9YZ054810005RKZZA Vol1 9471 Wireless Mobility Manager WMM Alarm Dictionary, WM7.0.0

Use pursuant to applicable agreements
Title page
Alcatel-Lucent LTE Evolved Packet Core

(EPC)
9471 Wireless Mobility Manager (WMM) | Release WM7.0.0
Alarm Dictionary
9YZ-05481-0005-RKZZA
Issue 1 | August 2013
Alcatel-Lucent Proprietary
Legal notice
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2013 Alcatel-Lucent. All rights reserved.
Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside
Alcatel-Lucent without its written authorization.
Not to be used or disclosed except in accordance with applicable agreements.
Notice
Every effort has been made to ensure that the information contained in this document was accurate at the time of printing. However, information is subject to
change.
PICMG, AdvancedTCA, and ATCA are registered trademarks of the PCI Industrial Computer Manufacturers Group.
Conformance statements
Refer to Appendix A, Compliance Summary.
Limited warranty
This system is a single homogenous system consisting of component parts designed to operate in the manner that the switch is configured when provided to
the customer. Changes to system level configurations set "at the factory" can affect the availability, throughput, standards compliance, and stability of the
product and result in expanded unplanned downtimes as unforeseen issues arise with untested configuration settings. Changes from factory settings can result
in violation of warranty and maintenance agreements with Alcatel-Lucent and should not be performed without the expressed written consent of
Alcatel-Lucent.
Licenses
Refer to the 9471 WMM Technical Description for a complete licensing statement.
Technical support
For technical support, contact your local customer support team. Reach them using the web at http://alcatel-lucent.com/support (http://alcatel-lucent.com/
support) at or the telephone number listed under the Technical Assistance Center menu at http://www.alcatel-lucent.com/contact (http://www.alcatel-lucent.
com/contact).
Alcatel-Lucent Proprietary
Contents
About this document

Purpose .......................................................................................................................................................................................... xiii
xiii
Reason for reissue ...................................................................................................................................................................... xiii

xiii
Intended audience ...................................................................................................................................................................... xiv

xiv
How to use this document ....................................................................................................................................................... xiv

xiv
Conventions used ....................................................................................................................................................................... xiv

xiv
Related information .................................................................................................................................................................... xv

xv
To obtain technical support, documentation, and training or submit feedback ................................................... xvi
How to comment ........................................................................................................................................................................ xvi

xvi
1 About alarm management
Overview ...................................................................................................................................................................................... 1-1

1-1
Alarm groups description ....................................................................................................................................................... 1-2

1-2
Network event categories description ............................................................................................................................... 1-6

1-6
2 MME Alarms
Overview ...................................................................................................................................................................................... 2-1

2-1
LSS_cmasFailure ..................................................................................................................................................................... 2-4

2-4
LSS_cmasReceiveFailure ..................................................................................................................................................... 2-5

2-5
LSS_cmasSendFailure ........................................................................................................................................................... 2-6

2-6
LSS_cpiGTPcResponseTOGn ............................................................................................................................................. 2-7

2-7
LSS_cpiGTPcResponseTOS3 .............................................................................................................................................. 2-9

2-9
LSS_cpiGTPcResponseTOSv ............................................................................................................................................ 2-11

2-11
LSS_cpiHOFailuresTo3G2GOverGn ............................................................................................................................. 2-13

2-13
LSS_cpiHOfailuresFromGERANoverS3 ...................................................................................................................... 2-15

2-15
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary iii
9YZ-05481-0005-RKZZA Release Use pursuant to applicable agreements
WM7.0.0
Issue 1 August 2013
Contents
....................................................................................................................................................................................................................................
LSS_cpiHOfailuresFromUTRANoverS3 ...................................................................................................................... 2-17
2-17
LSS_cpiHOfailuresRAUto2G3GOverS3 ...................................................................................................................... 2-19

2-19
LSS_cpiHOfailuresRAUto2G3GnewSgwOverS3 ..................................................................................................... 2-21

2-21
LSS_cpiHOfailuresRAUto2G3GsameSgwOverS3 ................................................................................................... 2-23

2-23
LSS_cpiHOfailuresToGERANoverS3 ........................................................................................................................... 2-25

2-25
LSS_cpiHOfailuresToUTRANoverS3 ........................................................................................................................... 2-27

2-27
LSS_cpiMAFCommunicationFailureRate .................................................................................................................... 2-29

2-29
LSS_cpiMBMSSessionStartM3FailureRate ................................................................................................................ 2-31

2-31
LSS_cpiMBMSSessionStartSmFailureRate ................................................................................................................. 2-33

2-33
LSS_cpiMBMSSessionStopM3FailureRate ................................................................................................................. 2-35

2-35
LSS_cpiMBMSSessionStopSmFailureRate ................................................................................................................. 2-37

2-37
LSS_cpiMBMSSessionUpdateM3FailureRate ........................................................................................................... 2-39

2-39
LSS_cpiMBMSSessionUpdateSmFailureRate ............................................................................................................ 2-41

2-41
LSS_cpiMafAttachFailuresSysRelated .......................................................................................................................... 2-43

2-43
LSS_cpiMafAttachWithPGWreselection ...................................................................................................................... 2-44

2-44
LSS_cpiMafAttachWithSGWreselection ...................................................................................................................... 2-45

2-45
LSS_cpiMafEIRfailuresS13 ............................................................................................................................................... 2-46

2-46
LSS_cpiMafExtServiceReqFailuresSysRelated ......................................................................................................... 2-47

2-47
LSS_cpiMafExtServiceRequestFailures ........................................................................................................................ 2-49

2-49
LSS_cpiMafFailuresOverSGs ........................................................................................................................................... 2-51

2-51
LSS_cpiMafHLRAuthFail .................................................................................................................................................. 2-52

2-52
LSS_cpiMafHSSreselection ............................................................................................................................................... 2-53

2-53
LSS_cpiMafPDNconnWithPGWreselection ................................................................................................................ 2-54

2-54
LSS_cpiMafServiceReqFailuresSysRelated ................................................................................................................ 2-55

2-55
LSS_cpiMafTauFailuresInterMme .................................................................................................................................. 2-56

2-56
LSS_cpiMafTauFailuresInterMmeInterSgw ................................................................................................................ 2-57

2-57
LSS_cpiMafTauFailuresInterSgw .................................................................................................................................... 2-59

2-59
....................................................................................................................................................................................................................................
iv Alcatel-Lucent Proprietary 9471 WMM Alarms
Use pursuant to applicable agreements 9YZ-05481-0005-RKZZA Release
WM7.0.0
Issue 1 August 2013
Contents
....................................................................................................................................................................................................................................
LSS_cpiNoPSHOFailuresOverSv .................................................................................................................................... 2-61
2-61
LSS_cpiPSHOFailuresOverSv .......................................................................................................................................... 2-63

2-63
LSS_cpiS3TauFailures ......................................................................................................................................................... 2-65

2-65
LSS_cpiS3TauFailuresInterSgw ....................................................................................................................................... 2-67

2-67
LSS_cpiS3TauFailuresIntraSGW ..................................................................................................................................... 2-69

2-69
LSS_cpiStopWarnMsgDeliveryS1MMEFailureRate ................................................................................................ 2-71

2-71
LSS_cpiStopWarnMsgDeliverySBcFailureRate ........................................................................................................ 2-73

2-73
LSS_cpiUECapacityUsage ................................................................................................................................................. 2-75

2-75
LSS_cpiWarnMsgDeliveryS1MMEFailureRate ......................................................................................................... 2-76

2-76
LSS_cpiWarnMsgDeliverySBcFailureRate .................................................................................................................. 2-78

2-78
LSS_dataMismatch ................................................................................................................................................................ 2-80

2-80
LSS_excessiveExternalLinksDown ............................................................................................................................... 2-83

2-83
LSS_externalLinkConfigurationLimit ............................................................................................................................ 2-84

2-84
LSS_externalLinkDown ..................................................................................................................................................... 2-85

2-85
LSS_failedAttachReqsRateExceeded ............................................................................................................................. 2-86

2-86
LSS_failedAuthRequestsHSSRateExceeded ............................................................................................................... 2-88

2-88
LSS_failedAuthRequestsUERateExceeded .................................................................................................................. 2-90

2-90
LSS_failedCrDedBearerReqsRateExceeded ................................................................................................................ 2-91

2-91
LSS_failedDeactDedBearerReqsRateExceeded ......................................................................................................... 2-93

2-93
LSS_failedHRPDhandoverRateExceeded .................................................................................................................... 2-94

2-94
LSS_failedMobileTermLocRequestRateExceeded .................................................................................................... 2-95

2-95
LSS_failedNetwrkInducedLocRequestRateExceeded .............................................................................................. 2-97

2-97
LSS_failedNumHOFwdRelocRateExceeded ............................................................................................................... 2-99

2-99
LSS_failedNumHOPathSwNewSgwRateExceeded ............................................................................................... 2-100

2-100
LSS_failedNumHOPathSwSameSgwRateExceeded .............................................................................................. 2-101

2-101
LSS_failedNumHORequiredRateExceeded .............................................................................................................. 2-102

2-102
LSS_failedS1MMEconnEstRateExceeded ................................................................................................................. 2-103

2-103
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary v
WM7.0.0
Issue 1 August 2013
Contents
....................................................................................................................................................................................................................................
LSS_failedServiceReqsRateExceeded ......................................................................................................................... 2-104
2-104
LSS_failedTAURateExceeded ........................................................................................................................................ 2-106

2-106
LSS_failedUpdBearerReqsRateExceeded .................................................................................................................. 2-108

2-108
LSS_failedUpdDedBearerReqsRateExceeded .......................................................................................................... 2-109

2-109
LSS_ggsnDnsError ............................................................................................................................................................ 2-110

2-110
LSS_internalCommunicationFailure ........................................................................................................................... 2-111

2-111
LSS_ippuBusError ............................................................................................................................................................. 2-112

2-112
LSS_ippuResourceReset .................................................................................................................................................. 2-114

2-114
LSS_liNearingCapacityLimit ......................................................................................................................................... 2-115

2-115
LSS_maxDurationExpiredOnHRPDhandover .......................................................................................................... 2-116

2-116
LSS_mmeDnsError ............................................................................................................................................................ 2-117

2-117
LSS_noResetAckReceived ............................................................................................................................................... 2-118

2-118
LSS_numTOS10gtpcRateExceeded .............................................................................................................................. 2-119

2-119
LSS_numTOS11gtpcRateExceeded .............................................................................................................................. 2-120

2-120
LSS_numTOS3gtpcRateExceeded ................................................................................................................................ 2-121

2-121
LSS_pathAvailability ........................................................................................................................................................ 2-122

2-122
LSS_pgwDnsError ............................................................................................................................................................. 2-123

2-123
LSS_provisioningError ..................................................................................................................................................... 2-124

2-124
LSS_sgsnDnsError ............................................................................................................................................................. 2-125

2-125
LSS_taiFqdnError .............................................................................................................................................................. 2-126

2-126
3 SGSN Alarms
Overview ...................................................................................................................................................................................... 3-1

3-1
LSS_cdrStorageSpaceThreshold ......................................................................................................................................... 3-3

3-3
LSS_cgfNotResponding ......................................................................................................................................................... 3-4

3-4
LSS_cgfServiceNotSupported ............................................................................................................................................. 3-5

3-5
LSS_cgfSystemFailure ........................................................................................................................................................... 3-6

3-6
LSS_cgfVersionNotSupported ............................................................................................................................................. 3-7

3-7
....................................................................................................................................................................................................................................
vi Alcatel-Lucent Proprietary 9471 WMM Alarms
WM7.0.0
Issue 1 August 2013
Contents
....................................................................................................................................................................................................................................
LSS_cpiGTPcResponseTOGn ............................................................................................................................................. 3-8
3-8
LSS_cpiGTPcResponseTOS3 ........................................................................................................................................... 3-10

3-10
LSS_cpiUECapacityUsage ................................................................................................................................................. 3-12

3-12
LSS_excessiveExternalLinksDown ............................................................................................................................... 3-13

3-13
LSS_externalLinkDown ..................................................................................................................................................... 3-14

3-14
LSS_ggsnDnsError ............................................................................................................................................................... 3-15

3-15
LSS_internalCommunicationFailure ............................................................................................................................. 3-16

3-16
LSS_ippuBusError ................................................................................................................................................................ 3-17

3-17
LSS_ippuResourceReset .................................................................................................................................................... 3-19

3-19
LSS_liNearingCapacityLimit ........................................................................................................................................... 3-20

3-20
LSS_msThreshold .................................................................................................................................................................. 3-21

3-21
LSS_noResetAckReceived ................................................................................................................................................. 3-22

3-22
LSS_nseBandwidthThreshold ........................................................................................................................................... 3-23

3-23
LSS_pathAvailability ........................................................................................................................................................... 3-24

3-24
LSS_pdpThreshold ................................................................................................................................................................ 3-25

3-25
LSS_sgsnDnsError ............................................................................................................................................................... 3-26

3-26
4 BASE_ATCA Alarms
Overview ...................................................................................................................................................................................... 4-1

4-1
ATCA_AggregatePowerSensor ........................................................................................................................................... 4-6

4-6
ATCA_AggregateTemperatureSensor ............................................................................................................................... 4-7

4-7
ATCA_BoardPower ................................................................................................................................................................. 4-8

4-8
ATCA_CPLDState ................................................................................................................................................................... 4-9

4-9
ATCA_DS75Temperature ................................................................................................................................................... 4-11

4-11
ATCA_ExhaustTemp ............................................................................................................................................................ 4-13

4-13
ATCA_FPGATemp ................................................................................................................................................................ 4-15

4-15
ATCA_FanSpeed .................................................................................................................................................................... 4-17

4-17
ATCA_FanTrayPresence ..................................................................................................................................................... 4-18

4-18
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary vii
WM7.0.0
Issue 1 August 2013
Contents
....................................................................................................................................................................................................................................
ATCA_FanTraysFRU ........................................................................................................................................................... 4-19
4-19
ATCA_FilterPresence ........................................................................................................................................................... 4-21

4-21
ATCA_I2CLocalBus ............................................................................................................................................................. 4-22

4-22
ATCA_IPMBLink .................................................................................................................................................................. 4-23

4-23
ATCA_InletTemp ................................................................................................................................................................... 4-24

4-24
ATCA_LM75Temperature .................................................................................................................................................. 4-26

4-26
ATCA_LM83Temperature .................................................................................................................................................. 4-28

4-28
ATCA_LMeUC75Temperature ......................................................................................................................................... 4-30

4-30
ATCA_LMeUC75Top-Rig ................................................................................................................................................. 4-32

4-32
ATCA_LocalTemperature ................................................................................................................................................... 4-34

4-34
ATCA_MMCTemp ................................................................................................................................................................ 4-35

4-35
ATCA_OcteonTemperature ................................................................................................................................................ 4-37

4-37
ATCA_OutletTemp ................................................................................................................................................................ 4-38

4-38
ATCA_PayloadCurrent ........................................................................................................................................................ 4-40

4-40
ATCA_PayloadVoltage ........................................................................................................................................................ 4-42

4-42
ATCA_PowerOk ..................................................................................................................................................................... 4-44

4-44
ATCA_ShelfFRUs ................................................................................................................................................................. 4-45

4-45
ATCA_UnexpectedDeact .................................................................................................................................................... 4-47

4-47
ATCA_m48vSensor ............................................................................................................................................................... 4-48

4-48
LSS_cardConnectionLost .................................................................................................................................................. 4-49

4-49
LSS_cardError ........................................................................................................................................................................ 4-51

4-51
LSS_cpiAlrmCritical ............................................................................................................................................................ 4-52

4-52
LSS_cpiAlrmMajor ............................................................................................................................................................... 4-53

4-53
LSS_cpiAlrmMinor ............................................................................................................................................................... 4-54

4-54
LSS_cpiAlrmWarning .......................................................................................................................................................... 4-55

4-55
LSS_cpiAsrtEsc ...................................................................................................................................................................... 4-56

4-56
LSS_cpiAsrtNonEsc ............................................................................................................................................................. 4-58

4-58
....................................................................................................................................................................................................................................
viii Alcatel-Lucent Proprietary 9471 WMM Alarms
WM7.0.0
Issue 1 August 2013
Contents
....................................................................................................................................................................................................................................
LSS_cpiAsrtNonEscCritical ............................................................................................................................................... 4-60
4-60
LSS_cpiAsrtNonEscMajor ................................................................................................................................................. 4-62

4-62
LSS_cpiAsrtNonEscMinor ................................................................................................................................................. 4-64

4-64
LSS_cpiAudErrCount ........................................................................................................................................................... 4-66

4-66
LSS_cpiAudManAct ............................................................................................................................................................. 4-68

4-68
LSS_cpiAudNewEvent ........................................................................................................................................................ 4-70

4-70
LSS_cpiExceptionService ................................................................................................................................................... 4-72

4-72
LSS_cpiFileSysUsage .......................................................................................................................................................... 4-74

4-74
LSS_cpiMemAllocFail ......................................................................................................................................................... 4-75

4-75
LSS_cpiReinitServiceSelf ................................................................................................................................................... 4-76

4-76
LSS_cpuOverload ................................................................................................................................................................. 4-78

4-78
LSS_databaseConnectionLost .......................................................................................................................................... 4-79

4-79
LSS_databaseReplicationLinkDown ............................................................................................................................. 4-80

4-80
LSS_databaseSizeExhausted ............................................................................................................................................ 4-81

4-81
LSS_dbHighCpuUtilization .............................................................................................................................................. 4-82

4-82
LSS_dbOffline ....................................................................................................................................................................... 4-83

4-83
LSS_dbStatusUnexpected .................................................................................................................................................. 4-84

4-84
LSS_degradedResource ....................................................................................................................................................... 4-85

4-85
LSS_degrow ......................................................................................................................................................................... 4-126

4-126
LSS_diskGoingDown ....................................................................................................................................................... 4-127

4-127
LSS_diskSector ................................................................................................................................................................... 4-128

4-128
LSS_dnsThreshold ............................................................................................................................................................. 4-129

4-129
LSS_ethernetError .............................................................................................................................................................. 4-130

4-130
LSS_ethernetLinkDown ................................................................................................................................................... 4-131

4-131
LSS_externalConnectivity .............................................................................................................................................. 4-133

4-133
LSS_fru .................................................................................................................................................................................. 4-134

4-134
LSS_grow .............................................................................................................................................................................. 4-135

4-135
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary ix
WM7.0.0
Issue 1 August 2013
Contents
....................................................................................................................................................................................................................................
LSS_hostDown .................................................................................................................................................................... 4-136
4-136
LSS_memoryOverload ..................................................................................................................................................... 4-137

4-137
LSS_nodeGroupOOS ........................................................................................................................................................ 4-138

4-138
LSS_nodeOOS ..................................................................................................................................................................... 4-139

4-139
LSS_numberOfTuplesInUse ............................................................................................................................................ 4-140

4-140
LSS_osSecInfoModificationDetected ......................................................................................................................... 4-141

4-141
LSS_osSecInformationMissing ..................................................................................................................................... 4-142

4-142
LSS_osSecUnexpectedInformation ............................................................................................................................. 4-143

4-143
LSS_patch ............................................................................................................................................................................. 4-144

4-144
LSS_pktCorruptionDetectedViaRCCLANCheck ................................................................................................... 4-145

4-145
LSS_platformCommandFailure .................................................................................................................................... 4-146

4-146
LSS_pmDataNotCollected ............................................................................................................................................... 4-147

4-147
LSS_processDown ............................................................................................................................................................. 4-148

4-148
LSS_processNotStarted ..................................................................................................................................................... 4-149

4-149
LSS_remoteQueryServerFailure ................................................................................................................................... 4-152

4-152
LSS_remotedbLinkDown ................................................................................................................................................ 4-153

4-153
LSS_restore ........................................................................................................................................................................... 4-154

4-154
LSS_serviceOnewayCommunication .......................................................................................................................... 4-155

4-155
LSS_sheddingOverload .................................................................................................................................................... 4-156

4-156
LSS_shmcEthernetError .................................................................................................................................................... 4-157

4-157
LSS_simxml ......................................................................................................................................................................... 4-158

4-158
LSS_softwareAllocatedResourceOverload ............................................................................................................... 4-159

4-159
LSS_softwareComponentStandbyNotReady ........................................................................................................... 4-160

4-160
LSS_svcdegrow ................................................................................................................................................................... 4-161

4-161
LSS_svcgrow ....................................................................................................................................................................... 4-162

4-162
LSS_swVersionMismatch ................................................................................................................................................. 4-163

4-163
LSS_tftpDownloadCorrupt ............................................................................................................................................. 4-164

4-164
....................................................................................................................................................................................................................................
x Alcatel-Lucent Proprietary 9471 WMM Alarms
WM7.0.0
Issue 1 August 2013
Contents
....................................................................................................................................................................................................................................
LSS_threadsExhausted ...................................................................................................................................................... 4-166
4-166
LSS_upgrade ........................................................................................................................................................................ 4-167

4-167
LSS_virtualClusterDown ................................................................................................................................................. 4-168

4-168
RALARM_Loop .................................................................................................................................................................. 4-169

4-169
RALARM_Power ................................................................................................................................................................ 4-170

4-170
SYS_BackupFailure ............................................................................................................................................................ 4-171

4-171
SYS_CPM_USERDATA_INCONSITENCY ........................................................................................................... 4-172

4-172
SYS_CPM_USERDATA_RESTORED ...................................................................................................................... 4-173

4-173
SYS_Configuration ............................................................................................................................................................ 4-174

4-174
SYS_EventQueueCapacity ............................................................................................................................................. 4-176

4-176
SYS_ICMPFailure ............................................................................................................................................................... 4-177

4-177
SYS_IPsecConfig ............................................................................................................................................................... 4-178

4-178
SYS_LinkDown ................................................................................................................................................................... 4-179

4-179
SYS_NotifyDisabled ......................................................................................................................................................... 4-180

4-180
SYS_NotifyLocked ............................................................................................................................................................ 4-181

4-181
SYS_RADIUS_TO_LDAP_FAILURE ....................................................................................................................... 4-182

4-182
SYS_ROOT_ACCESS_DENIED ................................................................................................................................. 4-183

4-183
SYS_ROOT_FTP_VIOLATION ................................................................................................................................... 4-184

4-184
SYS_ROOT_LOGIN_VIOLATION ............................................................................................................................ 4-185

4-185
SYS_ROOT_SSH_LOGIN_VIOLATION ................................................................................................................. 4-186

4-186
SYS_SNETrapOverload .................................................................................................................................................... 4-187

4-187
SYS_SNMPAuthenticationFailure ................................................................................................................................ 4-188

4-188
SYS_SNMPFailure ............................................................................................................................................................. 4-189

4-189
SYS_SU_TO_ROOT_FAILURE .................................................................................................................................. 4-190

4-190
SYS_SYSTEMTrapOverload .......................................................................................................................................... 4-191

4-191
SYS_SetupAAAFailure ..................................................................................................................................................... 4-192

4-192
SYS_TestAlarm ................................................................................................................................................................... 4-193

4-193
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary xi
WM7.0.0
Issue 1 August 2013
Contents
....................................................................................................................................................................................................................................
SYS_ThresholdCrossed ................................................................................................................................................... 4-194
4-194
SYS_UndiscoveredObject ............................................................................................................................................... 4-195

4-195
SYS_WriteAAAFailure ..................................................................................................................................................... 4-196

4-196
A Compliance Summary
9471 WMM compliance summary .................................................................................................................................... A-1

A-1
B References
Revision history ........................................................................................................................................................................ B-1

B-1
Index
....................................................................................................................................................................................................................................
xii Alcatel-Lucent Proprietary 9471 WMM Alarms
WM7.0.0
Issue 1 August 2013
About this document
About this document
Purpose
This document is used to interpret alarms on the Alcatel-Lucent 9471 WMM.
Reason for reissue

The following was updated in this release:
Reason for Change Location

New MME Alarms: LSS_cmasFailure (p. 2-4)
LSS_cmasReceiveFailure (p. 2-5)
LSS_cmasSendFailure (p. 2-6)
LSS_cpiMafAttachWithPGWreselection (p. 2-44)
LSS_cpiMafAttachWithSGWreselection (p. 2-45)
LSS_cpiMafHSSreselection (p. 2-53)
LSS_cpiMafPDNconnWithPGWreselection (p. 2-54)
LSS_excessiveExternalLinksDown (p. 2-83)
LSS_externalLinkConfigurationLimit (p. 2-84)
New ATCA platform alarm ATCA_LMeUC75Top-Rig (p. 4-32)

LSS_nodeGroupOOS (p. 4-138)
LSS_nodeOOS (p. 4-139)
LSS_threadsExhausted (p. 4-166)
Modified ATCA_BASE LSS_diskSector (p. 4-128) (Updated fault clearance

alarms procedure)
SYS_Configuration (p. 4-174) (change 'ntp' to
'ntp_server' in fault clearance commands)
...................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary xiii
WM7.0.0
Issue 1 August 2013
About this document
....................................................................................................................................................................................................................................
Intended audience
This document is for service provider personnel who support the 9471 WMM.
How to use this document

The WMM application is built on a common platform used by many different
applications. The WMM does not use all of the capabilities of the platform and therefore,
some base ATCA alarms may not be applicable. In addition, certain functionality defined
within some alarms may also not be applicable to the WMM such as the following: CDR,
SS7, FS5K, FS GUI, NGSS, TL1, and CPSB.
Conventions used
The following conventions are used throughout this information product:
Typographic conventions
This information product presents different types of information in different typefaces to
emphasize the nature of the information:
Literal input: Keystrokes that you are to enter character by character exactly as shown
in the text appear in monospace bold type. For example:
Enter the following command:
apappsconfig
Variable user input: Input values that vary from one execution or instance to another
appear in monospace bold italic type. For example:
cd directory
where
directory = the directory to change to.
Literal output: The names of files, directories, forms, messages, and other information
that a system outputs exactly as shown in the text appear in monospace regular
type. For example:
RST SPA=cnam REQUEST ACKNOWLEDGED
Variable system output: Values that vary from one instance to another in system
output appear in monospace italic type. For example:
RST SPA=SPA_NAME REQUEST COMPLETED
where
SPA_NAME = the name of the Service Package Application (SPA) that is successfully
restored.
The names of keys on a terminal keyboard are indicated by bold letters. For example:
....................................................................................................................................................................................................................................
xiv Alcatel-Lucent Proprietary 9471 WMM Alarms
WM7.0.0
Issue 1 August 2013
About this document
....................................................................................................................................................................................................................................
Press the F4 (Enter Query) function key.
The Ctrl (Control) key is signified by the carat ( ^ ) symbol. When the ^ symbol
precedes the name of another key (as in ^e), press the Ctrl key and the other key
simultaneously.
Actions for user input
In this information product, the following words specify what actions to perform to input
data or execute commands:
The word enter means to key in the specified keystrokes (such as a command) and
then press the Enter or Return key. For example:
Enter the following command:
apappconfig
The word type means to key in the specified keystrokes (such as a value in the field of
a form) without pressing the Enter or Return key. For example:
In the IP address field, type the IP address of the host server.
Related information
The following documents contain information related to this product:
Document Document Title

Number
9YZ-05481-0001- 9471 WMM Technical Description
DEZZA
9YZ-05481-0002- 9471 WMM Operations, Administration & Maintenance
REZZA
9YZ-05481-0003- 9471 WMM Security Management
USZZA Note: Restricted Document only available through the OLCS website.
9YZ-05481-0004- 9471 WMM Software Update
RJZZA
9YZ-05481-0006- 9471 WMM Observation Counters
RKZZA
9YZ-05481-0008- 9471 WMM Site Preparation
RJZZA
9YZ-05481-0012- 9471 WMM CALEA/LI Management
REZZA Note: Restricted Document only available through the OLCS website.
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary xv
WM7.0.0
Issue 1 August 2013
About this document
....................................................................................................................................................................................................................................
To obtain technical support, documentation, and training or submit feedback
The Online Customer Support (OLCS) web site (http://support.alcatel-lucent.com),
provides access to technical support, related documentation, related training, and
feedback tools. The site also provides account registration for new users.
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
xvi Alcatel-Lucent Proprietary 9471 WMM Alarms
WM7.0.0
Issue 1 August 2013
1 About alarm management
1
Overview
Purpose
This chapter provides a description of alarm groups and network event categories.
Contents
Alarm groups description 1-2

Network event categories description 1-6
...................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary 1-1
WM7.0.0
Issue 1 August 2013
About alarm management Alarm groups description
....................................................................................................................................................................................................................................
Alarm groups description

Overview
Different alarm categories can be observed in the MI GUI under Fault Management --->
Alarms menu. The alarm types, alarm severities, and probable causes are defined in the
CCITT standard X.733.
Although alarm details are available in the X.733 standards, the 3GPP standards are used
which are based off X.733 standards.
Introduction
Alarms appearing in the alarm log are all propagated events with the severities: Warning,
Minor, Major, Indeterminate and Critical. All other events appear in the event log.
Alarm types
The Alarm Type field is shown as a column in the alarms window on the MI GUI, and as
eventType on the properties of an alarm.
Alarm Type Explanation

Communication Associated with the procedures and/or processes required to convey
alarm information from one point to another.
Quality of Service Associated with degradation in the quality of a service.
Alarm
Processing Error Associated with a software or processing fault.
alarm
Equipment alarm Associated with an equipment fault.
Environmental Associated with a condition relating to an enclosure in which the
alarm equipment resides.
Integrity violation For security alarms: associated with duplicate information, information
missing, information modification detected, information out of sequence,
or unexpected information.
Operational For security alarms: associated with denial of service, out of service,
violation procedural error, or unspecified reason.
Physical violation For security alarms: associated with cable tamper, intrusion detection or
alarm unspecified reason.
Security service or For security alarms: associated with authentication failure, breach of
mechanism confidentiality, non-repudiation failure, unauthorized access attempt, or
violation alarm unspecified reason.
....................................................................................................................................................................................................................................
1-2 Alcatel-Lucent Proprietary 9471 WMM Alarms
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Alarm Type Explanation

Time domain For security alarms: associated with delayed information, key expired or
violation alarm out of hours activity.
Alarm severity
The Severity field appears as a column in the alarms window on the MI GUI, and as field
on the alarm details.
Severity Explanation
Critical The Critical severity level indicates that a service affecting condition has
occurred and immediate corrective action is required. For example, this severity
is reported when a managed object is out of service and its capability must be
restored.
Major The Major severity level indicates that a service affecting condition has
developed and urgent corrective action is required. For example, this severity is
reported when a severe degradation in the capability of the managed object
exists and its full capability must be restored.
Minor The Minor severity level indicates the existence of a non-service affecting fault
condition and that corrective action should be taken to prevent a more serious
(for example, service affecting) fault. For example, this severity is reported
when the detected alarm condition is not currently degrading the capacity of the
managed object.
Warning The Warning severity level indicates the detection of a potential or impending
service affecting fault, before any significant affects have been felt. To prevent a
more serious service-affecting fault, further action should be taken to diagnose
and correct the problem.
Indetermi- The Indeterminate severity level indicates that the severity level cannot be
nate determined by the sending element.
Cleared The Cleared severity level indicates the clearing of one or more previously
reported alarms. This alarm clears all alarms for the managed object that have
the same alarm type, probable cause, and specific problems. Multiple associated
notifications can be cleared by using the correlated notifications parameter.
When using filters a !clear severity also exists. This severity can be used to show all
active (not cleared) alarms in the system.
Alarms with informational severity appear under the events log and are described at the
events part.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Cause of alarms
The Probable Cause field is shown as a column in the alarms window on the MI GUI,
and as stringProbableCause field on the properties of an alarm. It provides an indication
of the most likely cause of the alarm and the related problem.
Two examples of probable causes available on the MI-Agent are explained in the table
that follows. Descriptions are retrieved from the ITU-T X.733 specification. For a
complete description of the probable causes, refer to the X.733 and other standards listed
under the reference part.
Probable Cause Explanation

Communication Protocol Error A communication protocol has been violated
Configuration or Customizing A system or device generation or customizing parameter has
Error been specified incorrectly, or is inconsistent with the actual
configuration
Alarm categories
The alarm category is shown in the Alarm Summary View, as a field on the alarm
details, and can optionally be added as a column to the alarms view window. This
category is used to group all alarms on a system in addition to the provided severity. The
different category types can also be used as criteria within custom views.
Category Category related to:

CP Hosts The hosts of the WMM
CP HW The hardware of the WMM
CP Services The services on top of the WMM
Topology The physical architecture of the network
Reference
The following specifications apply to alarms and events:
Telecommunication management; Fault Management; Part 2: Alarm Integration
Reference Point (IRP): Information Service (IS) , 3GPP TS 32.111-2
Telecommunication management; Fault Management; Part 3: Alarm Integration
Reference Point (IRP): Common Object Request Broker Architecture (CORBA)
Solution Set (SS), 3GPP TS 32.111-3
Generic network information model , ITU-T M.3100
Information technology - Open Systems Interconnection - Structure of management
information: Definition of management information, ITU-T X.721
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Information technology - Open Systems Interconnection - Systems Management:
Alarm reporting function, ITU-T X.733
Information technology - Open Systems Interconnection - Systems Management:
Security alarm reporting function , ITU-T X.736
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
About alarm management Network event categories description
....................................................................................................................................................................................................................................
Network event categories description

Introduction
Network events provide detail and history about activities that generate alarms. Events
can be used to correlate multiple alarms to a particular event. The same tasks that can be
performed on alarms can be performed on events (for example, search, creating custom
views, and filtering).
Events can be viewed in the MI GUI under Fault Management ----> Events. Events
received by the MI-Agent are logged in the events log. All events with the severities:
Warning, Minor, Major, Indeterminate and Critical are propagated to an alarm in the
alarm log. Other event types (with the severities, Info or State) are not propagated to the
alarm log and only stay in the event log.
Severity description
Events use all the standard severities used for alarms. Event-specific severities are
described in the table that follows
Severity Explanation
Info Used for alarms which do not require action to be taken.
Because this severity does not meet the X.733 standard, these alarms are not
propagated to the alarm log and show only in the event log.
State Indicates that a state change happened to a managed object on the MI-Agent.
This state follows the X.731 standard and should be referred to for more
information.
Event details
Details about specific events can be retrieved by viewing the details for the event. The
details and the Message field provides information to understand the cause of the event.
Custom Views
Certain types of events can be filtered out of the extensive event log by using Custom
Views on the MI GUI menu bar. One example is the custom view for informational
alarms which can be viewed separately in a sub folder under Events.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
2 MME Alarms
2
Overview
Purpose
This chapter contains alarms that are specific to the MME.
Contents
LSS_cmasFailure 2-4
LSS_cmasReceiveFailure 2-5
LSS_cmasSendFailure 2-6
LSS_cpiGTPcResponseTOGn 2-7
LSS_cpiGTPcResponseTOS3 2-9
LSS_cpiGTPcResponseTOSv 2-11
LSS_cpiHOFailuresTo3G2GOverGn 2-13
LSS_cpiHOfailuresFromGERANoverS3 2-15
LSS_cpiHOfailuresFromUTRANoverS3 2-17
LSS_cpiHOfailuresRAUto2G3GOverS3 2-19
LSS_cpiHOfailuresRAUto2G3GnewSgwOverS3 2-21
LSS_cpiHOfailuresRAUto2G3GsameSgwOverS3 2-23
LSS_cpiHOfailuresToGERANoverS3 2-25
LSS_cpiHOfailuresToUTRANoverS3 2-27
LSS_cpiMAFCommunicationFailureRate 2-29
LSS_cpiMBMSSessionStartM3FailureRate 2-31
LSS_cpiMBMSSessionStartSmFailureRate 2-33
LSS_cpiMBMSSessionStopM3FailureRate 2-35
LSS_cpiMBMSSessionStopSmFailureRate 2-37
...................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms Overview
....................................................................................................................................................................................................................................
LSS_cpiMBMSSessionUpdateM3FailureRate 2-39
LSS_cpiMBMSSessionUpdateSmFailureRate 2-41
LSS_cpiMafAttachFailuresSysRelated 2-43
LSS_cpiMafAttachWithPGWreselection 2-44
LSS_cpiMafAttachWithSGWreselection 2-45
LSS_cpiMafEIRfailuresS13 2-46
LSS_cpiMafExtServiceReqFailuresSysRelated 2-47
LSS_cpiMafExtServiceRequestFailures 2-49
LSS_cpiMafFailuresOverSGs 2-51
LSS_cpiMafHLRAuthFail 2-52
LSS_cpiMafHSSreselection 2-53
LSS_cpiMafPDNconnWithPGWreselection 2-54
LSS_cpiMafServiceReqFailuresSysRelated 2-55
LSS_cpiMafTauFailuresInterMme 2-56
LSS_cpiMafTauFailuresInterMmeInterSgw 2-57
LSS_cpiMafTauFailuresInterSgw 2-59
LSS_cpiNoPSHOFailuresOverSv 2-61
LSS_cpiPSHOFailuresOverSv 2-63
LSS_cpiS3TauFailures 2-65
LSS_cpiS3TauFailuresInterSgw 2-67
LSS_cpiS3TauFailuresIntraSGW 2-69
LSS_cpiStopWarnMsgDeliveryS1MMEFailureRate 2-71
LSS_cpiStopWarnMsgDeliverySBcFailureRate 2-73
LSS_cpiUECapacityUsage 2-75
LSS_cpiWarnMsgDeliveryS1MMEFailureRate 2-76
LSS_cpiWarnMsgDeliverySBcFailureRate 2-78
LSS_dataMismatch 2-80
LSS_excessiveExternalLinksDown 2-83
LSS_externalLinkConfigurationLimit 2-84
LSS_externalLinkDown 2-85
LSS_failedAttachReqsRateExceeded 2-86
LSS_failedAuthRequestsHSSRateExceeded 2-88
LSS_failedAuthRequestsUERateExceeded 2-90
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms Overview
....................................................................................................................................................................................................................................
LSS_failedCrDedBearerReqsRateExceeded 2-91
LSS_failedDeactDedBearerReqsRateExceeded 2-93
LSS_failedHRPDhandoverRateExceeded 2-94
LSS_failedMobileTermLocRequestRateExceeded 2-95
LSS_failedNetwrkInducedLocRequestRateExceeded 2-97
LSS_failedNumHOFwdRelocRateExceeded 2-99
LSS_failedNumHOPathSwNewSgwRateExceeded 2-100
LSS_failedNumHOPathSwSameSgwRateExceeded 2-101
LSS_failedNumHORequiredRateExceeded 2-102
LSS_failedS1MMEconnEstRateExceeded 2-103
LSS_failedServiceReqsRateExceeded 2-104
LSS_failedTAURateExceeded 2-106
LSS_failedUpdBearerReqsRateExceeded 2-108
LSS_failedUpdDedBearerReqsRateExceeded 2-109
LSS_ggsnDnsError 2-110
LSS_internalCommunicationFailure 2-111
LSS_ippuBusError 2-112
LSS_ippuResourceReset 2-114
LSS_liNearingCapacityLimit 2-115
LSS_maxDurationExpiredOnHRPDhandover 2-116
LSS_mmeDnsError 2-117
LSS_noResetAckReceived 2-118
LSS_numTOS10gtpcRateExceeded 2-119
LSS_pathAvailability 2-122
LSS_pgwDnsError 2-123
LSS_provisioningError 2-124
LSS_sgsnDnsError 2-125
LSS_taiFqdnError 2-126
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cmasFailure
....................................................................................................................................................................................................................................
LSS_cmasFailure
Description
This alarm indicates that there is software failure in s1mme or sbc modules, related to
CMAS.
Default severity
CRITICAL, MAJOR, MINOR
Root Cause
Software failure in either the S1mme or sbc modules. Severity of the alarm is
controlled by provisoning global parameters
Fault clearance procedure

...................................................................................................................................................................................................
1 Contact Alcatel-Lucent Customer Support.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cmasReceiveFailure
....................................................................................................................................................................................................................................
LSS_cmasReceiveFailure
Description
This alarm indicates that the MME failed to receive an acknowledgement to a CMAS
message.
Default severity
Root Cause
Possible link failure on the S1mme interface. Severity of the alarm is controlled by
provisioning global parameters.

...................................................................................................................................................................................................
1 Verify that the S1mme links are up.

...................................................................................................................................................................................................
2 Alarm can only be cleared manually by running "alarm_cli --clear

alarmName=LSS_cmasReceiveFailure" from the active MI.
...................................................................................................................................................................................................
3 If condition persists, contact Alcatel-Lucent Customer Support.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cmasSendFailure
....................................................................................................................................................................................................................................
LSS_cmasSendFailure
Description
This alarm indicates that there is a failure in sending a CMAS message over s1mme or
sbc interfaces.
Default severity
Root Cause
Possible link failure on the S1mme or sbc interfaces. Severity of the alarm is
controlled by provisioning global parameters.

...................................................................................................................................................................................................
1 Verify that the S1mme and sbc links are up.

...................................................................................................................................................................................................
2 Alarm can only be cleared manually by running "alarm_cli --clear

alarmName=LSS_cmasSendFailure" from the active MI.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiGTPcResponseTOGn
....................................................................................................................................................................................................................................
LSS_cpiGTPcResponseTOGn
Description
The raised alarm, LSS_cpiGTPcResponseTOGn, indicates that the value of
VS.cpiGTPcResponseTOGn has exceeded a threshold in the last 15 minute interval. This
counter monitors the percentage of GTP Requests sent over a Gn interface for which no
Response is received by the WMM. The Gn interface connects the WMM with one or
more SGSNs. The calculated percentage is compared against provisioned thresholds for
Minor, Major, and Critical alarm conditions.
Notes:
The alarm clears if no threshold is met in one of the following intervals.
Default severity
Severity Details
THE ALARM SEVERITY IS DETERMINED BY THE THRESHOLD SETTINGS. THE
DEFAULT ALARM SEVERITY FOLLOWS THE CRITERIA BELOW:
Critical Alarm: Rate value > 15
Major Alarm: 10 < Rate value <= 15
Minor Alarm: 5 < Rate value <= 10
Root Cause
Failure to receive GTP responses from an SGSN could be due to any of the following
reasons:
Errors or problems at the far end SGSN
Network problems between the WMM and the SGSN
Internal errors at the WMM

...................................................................................................................................................................................................
1 Check neighboring SGSNs for error conditions or ongoing problems. Verify network
connectivity and proper configuration between WMM and SGSNs. If SGSNs and
network connectivity are verified, examine all the GTP failure counters to determine if
one failure cause predominates, and check fs.log to determine if errors related to the Gn
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiGTPcResponseTOGn
....................................................................................................................................................................................................................................
interface have been reported. Contact next level of support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiGTPcResponseTOS3
....................................................................................................................................................................................................................................
LSS_cpiGTPcResponseTOS3
Description
The raised alarm, LSS_cpiGTPcResponseTOS3, indicates meeting a threshold of GTP
response failure rate in the last 5 minute interval. This failure rate monitors the percentage
of GTP Requests sent over an S3 interface for which no Response is received by the
MME. The S3 interface connects the MME with one or more SGSNs. The calculated
percentage is compared against provisioned thresholds for Minor, Major, and Critical
alarm conditions.
Notes:
An alarm with the same severity is raised only once for the same CPI and component.
Default severity
Severity Details
Root Cause
reasons:
Network problems between the MME and the SGSN
Internal errors at the MME

...................................................................................................................................................................................................
connectivity and proper configuration between MME and SGSNs. If SGSNs and network
connectivity are verified, examine all the GTP failure counters to determine if one failure
cause predominates, and check fs.log to determine if errors related to the S3 interface
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiGTPcResponseTOS3
....................................................................................................................................................................................................................................
have been reported. Contact next level of support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiGTPcResponseTOSv
....................................................................................................................................................................................................................................
LSS_cpiGTPcResponseTOSv
Description
The raised alarm LSS_cpiGTPcResponseTOSv indicates meeting a threshold of the GTPc
Response Time out over Sv CPI (requests sent over an Sv interface for which no response
is received), which is calculated every 5 minutes using this formula:
VS.NbrTO_SvGtpc / VS.TotalReqSent_SvGtpc
Notes:
The thresholds are configurable on MI CPI GUI.
Default severity
Severity Details
Root Cause
Failure to receive GTP responses from an MSC could be due to any of the following
reasons:
Errors or problems at the far end MSC
Network problems between the MME and the MSC

...................................................................................................................................................................................................
1 Check neighboring MSC(s) for error conditions or ongoing problems. Verify network
connectivity and proper configuration between MME and MSC(s). If MSC(s) and
one failure cause predominates, and check fs.log to determine if errors related to the Sv
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiGTPcResponseTOSv
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOFailuresTo3G2GOverGn
....................................................................................................................................................................................................................................
LSS_cpiHOFailuresTo3G2GOverGn
Description
The raised alarm, LSS_cpiHOFailuresTo3G2GOverGn, indicates that the value of
VS.cpiHOFailuresto3G2GOverGn has exceeded a threshold in the last 15 minute interval.
This counter monitors the failure rate of attempted handovers from E-UTRAN to a
UTRAN/GERAN SGSN using the Gn interface. This includes Routing Area Update
procedures. The failure rate is compared against provisioned thresholds for Minor, Major,
and Critical alarm conditions.
Notes:
Default severity
Severity Details
Root Cause
Attempted handovers from E-UTRAN to a UTRAN/GERAN SGSN via the Gn interface
may fail for any of the following reasons:
Protocol Errors on the Gn interface with the SGSN
Gn link inhibited due to link lock or link disabled due to dependency on the parent
managed object
The UE Context requested by and SGSN is not available in the MME
UE failed security validation at the MME
Failure to complete Routing Area Update procedure at the SGSN
Network connectivity problems between MME and SGSN
MME failure to release resources at completion of Routing Area Update procedure
Internal MME error
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOFailuresTo3G2GOverGn
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
For failures attributed to the SGSN, check the target UTRAN/GERAN network for
errors related to inter-system mobility procedures.
For failures attributed to the MME, check the Gn link status and MME service status.
Check fs.log for error indications related to Gn interface procedures, contact next
level of support if internal MME errors are indicated.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresFromGERANoverS3
....................................................................................................................................................................................................................................
LSS_cpiHOfailuresFromGERANoverS3
Description
The raised alarm, LSS_cpiHOfailuresFromGERANoverS3, indicates that the value of
VS.cpiHOfailuresFromGERANoverS3 has exceeded a threshold in the last 5 minute
interval. This counter monitors the failure rate of attempted handovers from GERAN to a
E-UTRAN SGSN using the S3 interface. The failure rate is compared against provisioned
thresholds for Minor, Major, and Critical alarm conditions.
Notes:
Default severity
Severity Details
Root Cause
Attempted handovers from GERAN to E-UTRAN SGSN via the S3 interface may fail for
any of the following reasons:
Protocol Errors on the S3 interface with the SGSN
S3 link inhibited due to link lock or link disabled due to dependency on the parent
managed object
Internal MME error
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresFromGERANoverS3
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
For failures attributed to the MME, check the S3 link status and MME service status.
Check fs.log for error indications related to S3 interface procedures, contact next level
of support if internal MME errors are indicated.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresFromUTRANoverS3
....................................................................................................................................................................................................................................
LSS_cpiHOfailuresFromUTRANoverS3
Description
The raised alarm, LSS_cpiHOfailuresFromUTRANoverS3, indicates that the value of
VS.cpiHOfailuresFromUTRANoverS3 has exceeded a threshold in the last 5 minute
interval. This counter monitors the failure rate of attempted handovers from UTRAN to a
E-UTRAN SGSN using the S3 interface. The failure rate is compared against provisioned
Notes:
Default severity
Severity Details
Root Cause
Attempted handovers from UTRAN to E-UTRAN SGSN via the S3 interface may fail for
any of the following reasons:
managed object
Internal MME error
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresFromUTRANoverS3
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresRAUto2G3GOverS3
....................................................................................................................................................................................................................................
LSS_cpiHOfailuresRAUto2G3GOverS3
Description
The raised alarm, LSS_cpiHOfailuresRAUto2G3GOverS3, indicates the failure rate of
attempted Routing Area Update (RAU) procedures from E-UTRAN to a
UTRAN/GERAN SGSN using the S3 interface has exceeded a threshold in the last 5
minute interval. Failures encountered during the entire duration of the RAU procedure are
included. Therefore, failures encountered both prior to and after SGW change
determination are included. The failure rate is compared against provisioned thresholds
for Minor, Major, and Critical alarm conditions.
Notes:
Default severity
Severity Details
Root Cause
Attempted Routing Area Update procedures from E-UTRAN to a UTRAN/GERAN
SGSN using the S3 interface may fail for any of the following reasons:
managed object
Internal MME resource overload
Internal MME error
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresRAUto2G3GOverS3
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 For failures attributed to the SGSN, check the target UTRAN/GERAN network for errors
related to inter-system mobility procedures.
...................................................................................................................................................................................................
2 For failures attributed to the MME, check the S3 link status and MME service status.
...................................................................................................................................................................................................
3 Check fs.log for error indications related to S3 interface procedures, contact

Alcatel-Lucent Customer Support if internal MME errors are indicated.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresRAUto2G3GnewSgwOverS3
....................................................................................................................................................................................................................................
LSS_cpiHOfailuresRAUto2G3GnewSgwOverS3
Description
The raised alarm, LSS_cpiHOfailuresRAUto2G3GnewSgwOverS3, indicates that the
value of VS.cpiHOfailuresRAUto2G3GnewSgwOverS3 has exceeded a threshold in the
last 5 minute interval. This counter monitors the failure rate of attempted RAU-based
handovers from E-UTRAN to a UTRAN/GERAN SGSN using the S3 interface with
SGW Relocation. This is Routing Area Update procedures. The failure rate is compared
against provisioned thresholds for Minor, Major, and Critical alarm conditions.
Notes:
Default severity
Severity Details
Root Cause
Attempted RAU-based handovers from E-UTRAN to a UTRAN/GERAN SGSN via the
S3 interface may fail for any of the following reasons:
managed object
Internal MME error
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresRAUto2G3GnewSgwOverS3
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresRAUto2G3GsameSgwOverS3
....................................................................................................................................................................................................................................
LSS_cpiHOfailuresRAUto2G3GsameSgwOverS3
Description
The raised alarm, LSS_cpiHOfailuresRAUto2G3GsameSgwOverS3, indicates that the
value of VS.cpiHOfailuresRAUto2G3GsameSgwOverS3 has exceeded a threshold in the
last 5 minute interval. This counter monitors the failure rate of attempted handovers from
E-UTRAN to a UTRAN/GERAN SGSN using the S3 interface without SGW Relocation.
This is Routing Area Update procedures. The failure rate is compared against provisioned
Notes:
Default severity
Severity Details
Root Cause
Attempted RAU-based handovers from E-UTRAN to a UTRAN/GERAN SGSN via the
S3 interface may fail for any of the following reasons:
managed object
Internal MME error
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresRAUto2G3GsameSgwOverS3
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresToGERANoverS3
....................................................................................................................................................................................................................................
LSS_cpiHOfailuresToGERANoverS3
Description
The raised alarm, LSS_cpiHOfailuresToGERANoverS3, indicates that the value of
VS.cpiHOfailuresToGERANoverS3 has exceeded a threshold in the last 5 minute
interval. This counter monitors the failure rate of attempted handovers from E-UTRAN to
a GERAN SGSN using the S3 interface. The failure rate is compared against provisioned
Notes:
Default severity
Severity Details
Root Cause
Attempted handovers from E-UTRAN to a GERAN SGSN via the S3 interface may fail
for any of the following reasons:
managed object
Internal MME error
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresToGERANoverS3
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresToUTRANoverS3
....................................................................................................................................................................................................................................
LSS_cpiHOfailuresToUTRANoverS3
Description
The raised alarm, LSS_cpiHOfailuresToUTRANoverS3, indicates that the value of
VS.cpiHOfailuresToUTRANoverS3 has exceeded a threshold in the last 5 minute
interval. This counter monitors the failure rate of attempted handovers from E-UTRAN to
a UTRAN SGSN using the S3 interface. The failure rate is compared against provisioned
Notes:
Default severity
Severity Details
Root Cause
Attempted handovers from E-UTRAN to a UTRAN SGSN via the S3 interface may fail
for any of the following reasons:
managed object
Internal MME error
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiHOfailuresToUTRANoverS3
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMAFCommunicationFailureRate
....................................................................................................................................................................................................................................
LSS_cpiMAFCommunicationFailureRate
Description
The raised alarm, cpiMAFCommunicationFailureRate, indicates meeting a threshold of
MAF communication failure rate on a per MAF service basis in the last 5 minutes. The
failure rate is calculated from the measurement count VS.TotalMsgsRcvdFromMAF and
VS.TotalMsgsSentToMAF in every interval of 5 minutes. On the MI GUI the alarm
resource will indicate which MAF service has the problem in the MAF pool.
Notes:
The alarm clears if no threshold is met in one of the subsequent intervals.
Default severity
Severity Details
Critical Alarm: CPI value > 95%
Major Alarm: 90% < CPI value <= 95%
Minor Alarm: 80% < CPI value <= 90%
Root Cause
This is a safety net alarm to provide notification in the event that MAF processing of
message traffic has significantly dropped (e.g. hung processes) and other monitoring
mechanisms have not identified and corrected the problem.
The communication issues between MIF and MAF services may also cause this alarm.

...................................................................................................................................................................................................
1 Check the overload status of the MAF service firing this alarm.
...................................................................................................................................................................................................
2 Check if there is any hung process in the MAF service firing this alarm.
...................................................................................................................................................................................................
3 If the MAF service is duplex, try to switch the active MAF service.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMAFCommunicationFailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Contact Alcatel-Lucent Technical Support if problem still persists.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionStartM3FailureRate
....................................................................................................................................................................................................................................
LSS_cpiMBMSSessionStartM3FailureRate
Description
The raised alarm LSS_cpiMBMSSessionStartM3FailureRate indicates meeting a
threshold of the MBMS Session Start M3 Failure Rate CPI, which is calculated every 5
minutes using this formula:
100 - (100 * ((VS.NbrSuccessMBMSsessionStartM3 + VS.AbortMBMSsessionStopM3)
/ VS.AttMBMSsessionStartM3))
Notes:
The thresholds are configurable on CPI GUI.
Default severity
Severity Details
Root Cause
Attempted MBMS Session Start procedures between the MME and MCEs using the M3
interface may fail for any of the following reasons:
Protocol Errors on an M3 interface with an MCE
MCE failure response
MME timeout awaiting MCE response
Internal MME resource overload or exhaustion
Internal MME error

...................................................................................................................................................................................................
1 For failures attributed to the MCE, check the MCE/eNB and network connections for
errors.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionStartM3FailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 For failures attributed to the MME, check the M3 link status and MME service status.
...................................................................................................................................................................................................
3 Check fs.log for error indications related to M3 interface procedures, contact

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionStartSmFailureRate
....................................................................................................................................................................................................................................
LSS_cpiMBMSSessionStartSmFailureRate
Description
The raised alarm LSS_cpiMBMSSessionStartSmFailureRate indicates meeting a
threshold of the MBMS Session Start Sm Failure Rate CPI, which is calculated every 5
100 - (100 * (VS.NbrSuccessMBMSsessionStartSm / VS.AttMBMSsessionStartSm))
Notes:
Default severity
Severity Details
Root Cause
Attempted MBMS Session Start procedures between MBMS-GW and the MME using the
Sm interface may fail for any of the following reasons:
iProtocol Errors on the Sm interface with the MBMS-GW
Sm link inhibited due to link lock or link disabled due to dependency on the parent
managed object
MBMS functionality disabled for the PLMN specified in the TMGI
Internal MME error

...................................................................................................................................................................................................
1 For failures attributed to the MBMS-GW, check the MBMS-GW and network for errors.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionStartSmFailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 For failures attributed to the MME, check the Sm link status and MME service status.
...................................................................................................................................................................................................
3 Check fs.log for error indications related to Sm interface procedures, contact

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionStopM3FailureRate
....................................................................................................................................................................................................................................
LSS_cpiMBMSSessionStopM3FailureRate
Description
The raised alarm LSS_cpiMBMSSessionStopM3FailureRate indicates meeting a
threshold of the MBMS Session Stop M3 Failure Rate CPI, which is calculated every 5
100 - (100 * ((VS.NbrSuccessMBMSsessionStopM3 + VS.AbortMBMSsessionStopM3) /
VS.AttMBMSsessionStopM3))
Notes:
Default severity
Severity Details
Root Cause
Attempted MBMS Session Stop procedures between the MME and MCEs using the
M3 interface may fail for any of the following reasons:
Internal MME error

...................................................................................................................................................................................................
errors.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionStopM3FailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionStopSmFailureRate
....................................................................................................................................................................................................................................
LSS_cpiMBMSSessionStopSmFailureRate
Description
The raised alarm LSS_cpiMBMSSessionStopSmFailureRate indicates meeting a
threshold of the MBMS Session Stop Sm Failure Rate CPI, which is calculated every 5
100 - (100 * (VS.NbrSuccessMBMSsessionStopSm / VS.AttMBMSsessionStopSm))
Notes:
Default severity
Severity Details
Root Cause
Attempted MBMS Session Stop procedures between MBMS-GW and the MME using the
Sm interface may fail for any of the following reasons:
Protocol Errors on the Sm interface with the MBMS-GW
managed object
MBMS bearer context not found
Internal MME error

...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionStopSmFailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionUpdateM3FailureRate
....................................................................................................................................................................................................................................
LSS_cpiMBMSSessionUpdateM3FailureRate
Description
The raised alarm LSS_cpiMBMSSessionUpdateM3FailureRate indicates meeting a
threshold of the MBMS Session Update M3 Failure Rate CPI, which is calculated every 5
100 - (100 * ((VS.NbrSuccessMBMSsessionUpdateM3 + VS.AbortMBMSsession-
StopM3) / VS.AttMBMSsessionUpdateM3))
Notes:
Default severity
Severity Details
Root Cause
Attempted MBMS Session Update procedures between the MME and MCEs using the
M3 interface may fail for any of the following reasons:
MCE failure response
MME timeout awaiting MCE response
Internal MME error

...................................................................................................................................................................................................
errors.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionUpdateM3FailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionUpdateSmFailureRate
....................................................................................................................................................................................................................................
LSS_cpiMBMSSessionUpdateSmFailureRate
Description
The raised alarm LSS_cpiMBMSSessionUpdateSmFailureRate indicates meeting a
threshold of the MBMS Session Update Sm Failure Rate CPI, which is calculated every 5
100 - (100 * (VS.NbrSuccessMBMSsessionUpdateSm / VS.AttMBMSsessionUp-
dateSm))
Notes:
Default severity
Severity Details
Root Cause
Attempted MBMS Session Update procedures between MBMS-GW and the MME using
the Sm interface may fail for any of the following reasons:
Protocol Errors on the Sm interface with the MBMS-GW
managed object
MBMS bearer context not found
Internal MME error

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMBMSSessionUpdateSmFailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafAttachFailuresSysRelated
....................................................................................................................................................................................................................................
LSS_cpiMafAttachFailuresSysRelated
Description
The raised alarm, LSS_cpiMafAttachFailuresSysRelated, indicates meeting/exceeding a
threshold of the rate of system-related failures for Attach procedures, which is calculated
every 5 minutes, using the formula:
VS.NbrAttachFailureSysRelated_sum / VS.AttAttachRequests
Notes:
Default severity
Severity Details
Root Cause
Possible reasons for failure :
Failures at the eNB elements
Failures at the SGW elements
Failures at the MME elements

...................................................................................................................................................................................................
1
Verify that the S1, S6a, and S11 links are in-service/normal, using link_cli.
Verify that there are no overload alarms on the MME
Contact Alcatel-Lucent Customer Support
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafAttachWithPGWreselection
....................................................................................................................................................................................................................................
LSS_cpiMafAttachWithPGWreselection
Description
The raised alarm cpiAttachWithPGWreselection indicates meeting a threshold of the rate
of PGW reselection during Attach procedures CPI, which is calculated every 5 minutes
using this formula:
VS.AttachWithPGWreselection/VS.AttAttachRequests
Notes:
An alarm with the same severity will be raised only once for the same CPI and
component.
The alarm will be cleared if no threshold is met in one of the following intervals.
Default severity
Severity Details
Root Cause
Timeout or a Reject received from the SGW.

...................................................................................................................................................................................................
1 Contact Alcatel-Lucent customer support.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafAttachWithSGWreselection
....................................................................................................................................................................................................................................
LSS_cpiMafAttachWithSGWreselection
Description
The raised alarm cpiAttachWithSGWreselection indicates meeting a threshold of the rate
of SGW reselection during Attach procedures CPI, which is calculated every 5 minutes
using this formula:
VS.AttachWithSGWreselection/VS.AttAttachRequests
Notes:
component.
Default severity
Severity Details
Root Cause

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafEIRfailuresS13
....................................................................................................................................................................................................................................
LSS_cpiMafEIRfailuresS13
Description
The raised alarm, LSS_cpiMafEIRfailuresS13, indicates that the value of
VS.LSS_cpiMafEIRfailuresS13 has exceeded a threshold in the last 5 minute interval.
This counter monitors the percentage of unsuccessful EquipmentCheckRequest (ECR) to
the number of ECRs attempted. The calculated percentage is compared against
provisioned thresholds for Minor, Major, and Critical alarm conditions.
Notes:
Default severity
Severity Details
Root Cause
Failure of ECR responses from the S13 EIR interface could be due any of the following
reasons:
Network problems between MME and HSS (EIR).
Errors or problems at far end HSS (EIR).
Internal errors at the MME.
Parsing/decoding errors in the ECR response.
IMEI not found in EIR DB

...................................................................................................................................................................................................
1 Verify the far end HSS (EIR) is functioning properly. Check fs.log for any ECR/ECA/S13
related errors to aid in determining the cause. Contact next level of support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafExtServiceReqFailuresSysRelated
....................................................................................................................................................................................................................................
LSS_cpiMafExtServiceReqFailuresSysRelated
Description
The raised alarm LSS_cpiMafExtServiceReqFailuresSysRelated indicates meeting a
threshold of the Extended Service Request System Related Failure CPI, which is
calculated every 5 minutes using this formula:
100 * (VS.NbrFailedExtSvcRequestsSysRelated_sum / VS.AttExtServiceRequests)
Notes:
Default severity
Severity Details
Root Cause
Failure could be due to any of the following reasons:
ENB returns UE Context Modification Failure (includes lack of resources, collision
with other procedure or protocol errors)
ENB returns Initial Context Setup Failure (includes lack of resources, collision with
other procedure or protocol errors)
ENB returns failure with cause relating to invalid/mismatched eRAB Id or mmeS1AP
Id sent by MME
MME fails to process Extended Service Request due to a system related failure on
MME
SGW failure on Modify Bearer Request during CSFB call
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafExtServiceReqFailuresSysRelated
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 Verify that S1, S6a, S11 and SGs links are Unlocked/Enabled using link_cli
...................................................................................................................................................................................................
2 Verify that there are no overload alarms on MME

...................................................................................................................................................................................................
3 Contact Customer Support

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafExtServiceRequestFailures
....................................................................................................................................................................................................................................
LSS_cpiMafExtServiceRequestFailures
Description
The raised alarm LSS_cpiMafExtServiceRequestFailures indicates meeting a threshold of
the Extended Service Request Failure CPI, which is calculated every 5 minutes using this
formula:
100 - (100 * (VS.NbrSuccessExtServiceRequests / VS.AttExtServiceRequests))
Notes:
Default severity
Severity Details
Root Cause
Extended Service Request rejected by MME due to protocol errors
For Mobile Terminated CSFB call, UE included rejection in CSFB Response IE of
Extended Service Request
Extended Service Request rejected by MME due to access restrictions (PLMN, TA,
EPS service, non-EPS service not allowed)
Extended Service Request rejected by MME due to roaming restrictions
Extended Service Request rejected by MME due to TA not available
For SGs based CSFB call, Extended Service Request rejected by MME due to TAI not
mapped to LAI or mapped to LAI not supporting CSFB
Extended Service Request rejected by MME due to UE implicitly detached
Extended Service Request rejected by MME due to problems with SGs link to MSC
Extended Service Request rejected by MME due to congestion
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafExtServiceRequestFailures
....................................................................................................................................................................................................................................
Extended Service Request aborted on MME due to collision with other procedure
pending for UE
MME did not receive UE Context Release Request from ENB after successful
processing of Extended Service Request
CSFB call failed due to MME, ENB or SGW related System Failure. For more details
see the Extended Service Request System Failures description

...................................................................................................................................................................................................
1 Verify MME provisioning data, especially PLMN, TAI-LAI-Mapping, LAI tables

...................................................................................................................................................................................................
2 Verify that S1, S6a, S11, and SGs links are Unlocked/Enabled using link_cli
...................................................................................................................................................................................................
3 Verify that there are no overload alarms on MME

...................................................................................................................................................................................................
4 Contact Customer Support

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafFailuresOverSGs
....................................................................................................................................................................................................................................
LSS_cpiMafFailuresOverSGs
Description
The raised alarm, LSS_cpiMafFailuresOverSGs, indicates meeting/exceeding a threshold
of the rate of failure for handling messages from the SGs interface, which is calculated
every 5 minutes, using the formula:
VS.NbrFailedSGsSignalingProcedures / VS.AttSGsSignalingProcedures
Notes:
Default severity
Severity Details
Root Cause
Possible reasons for failure:
Possible problems with the SGs links
Internal Failure

...................................................................................................................................................................................................
1
Verify that the SGs links are in-service/normal, using link_cli.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafHLRAuthFail
....................................................................................................................................................................................................................................
LSS_cpiMafHLRAuthFail
Description
The raised alarm, LSS_cpiMafHLRAuthFail, indicates meeting/exceeding a threshold of
the rate of failure for handling Authentication failure messages from the HLR, which is
calculated every 5 minutes, using the formula:
100 * (1 - (VS.NbrSuccessAuthRequestsHLR / VS.AttAuthRequestsHLR))
Notes:
THIS ALARM IS RESERVED FOR FUTURE USE.
Default severity
Severity Details
Root Cause
Possible problems with the Gr link
Protocol errors reported from the far end (such as unknown subscriber, unexpected
datavalue, missing data and system failure)
Internal Failure

...................................................................................................................................................................................................
1
Verify that the Gr link is in-service/normal, using link_cli.
Contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafHSSreselection
....................................................................................................................................................................................................................................
LSS_cpiMafHSSreselection
Description
The raised alarm cpiHSSreselection indicates meeting a threshold of the rate of HSS
reselection during Authentication or Update Location procedures CPI, which is calculated
every 5 minutes using this formula:
VS.HssReselectionAtt/(VS.AttAuthRequestsHSS+VS.AttUpdateLocationRequest)
Notes:
component.
Default severity
Severity Details
Root Cause
The following responses from the HSS may trigger this alarm:
Timeout on a request to HSS
HSS response code with error - TOO BUSY
HSS response code with error - RESOURCES EXCEEDED
HSS response code with error - UNABLE TO DELIVER
HSS response code with error - OUT OF SPACE

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafPDNconnWithPGWreselection
....................................................................................................................................................................................................................................
LSS_cpiMafPDNconnWithPGWreselection
Description
The raised alarm cpiPDNconnWithPGWreselection indicates meeting a threshold of the
rate of PGW reselection during PDN connectivity procedures CPI, which is calculated
VS.PdnConnPgwReselection/VS.AttPDNConnReq
Notes:
component.
Default severity
Severity Details
Root Cause

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafServiceReqFailuresSysRelated
....................................................................................................................................................................................................................................
LSS_cpiMafServiceReqFailuresSysRelated
Description
The raised alarm, LSS_cpiMafServiceReqFailuresSysRelated, indicates
meeting/exceeding a threshold of the rate of system-related failures for UE Service
Request procedures, which is calculated every 5 minutes, using the formula:
VS.NbrServiceReqFailureSysRelated_sum / VS.AttServiceRequests
Notes:
Default severity
Severity Details
Root Cause
Failures at the eNB elements
Failures at the SGW elements
Failures at the MME elements

...................................................................................................................................................................................................
1
Verify that the S1, S6a, and S11 links are in-service/normal, using link_cli.
Verify that there are no overload alarms on the MME
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafTauFailuresInterMme
....................................................................................................................................................................................................................................
LSS_cpiMafTauFailuresInterMme
Description
The raised alarm, LSS_cpiMafTauFailuresInterMme, indicates meeting/exceeding a
threshold of the rate of failure of Tracking Area Update procedures involving MME
relocation which is calculated every 5 minutes, using the formula:
(VS.TauInterMmeAtt - VS.TauInterMmeSucc) / VS.TauInterMmeAtt
Notes:
Default severity
Severity Details
Root Cause
Possible problems with the eNB or the MME
Old MME does not respond
MME is not available to provide service to the UE in the new Tracking Area

...................................................................................................................................................................................................
1
Verify that the eNB, and MME links are in-service/normal, using link_cli.
Contact Alcatel-Lucent Customer Support to determine the status of the serving eNB
and the MME groups serving the eNB that is involved in the TAU procedure
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafTauFailuresInterMmeInterSgw
....................................................................................................................................................................................................................................
LSS_cpiMafTauFailuresInterMmeInterSgw
Description
The raised alarm, LSS_cpiMafTauFailuresInterMmeInterSgw, indicates
meeting/exceeding a threshold of the rate of failure of Tracking Area Update procedures
involving MME relocation and SGW relocation which is calculated every 5 minutes,
using the formula:
(VS.TauInterMmeInterSgwAtt - VS.TauInterMmeInterSgwSucc) / VS.TauInterM-
meInterSgwAtt
Notes:
Default severity
Severity Details
Root Cause
Possible problems with the HSS, eNB, MME, or SGW
MME is not available to provide service to the UE in the new Tracking Area
RF problems may prevent the UE from sending or receiving messages
SGW is not available to provide service to the UE in the new Tracking Area
Because of SGW failure (no response from SGW or SGW reject the Create
Session/Modify Bearer Requests)
HSS failure/error response during Update Location Request
UE not allowed service due to UE subscription information

...................................................................................................................................................................................................
1 Verify that the HSS, eNB, SGW, and MME links are in-service/normal, using link_cli.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafTauFailuresInterMmeInterSgw
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Verify UE subscription information in HSS.

...................................................................................................................................................................................................
3 Contact Alcatel-Lucent Customer Support to determine the status of the serving eNB,
MME groups, and SGW Pools serving the eNB that are involved in the TAU procedure.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafTauFailuresInterSgw
....................................................................................................................................................................................................................................
LSS_cpiMafTauFailuresInterSgw
Description
The raised alarm, LSS_cpiMafTauFailuresInterSgw, indicates meeting/exceeding a
threshold of the rate of failure of Tracking Area Update procedures involving SGW
relocation, which is calculated every 5 minutes, using the formula:
(VS.TauInterSgwSucc - VS.TauInterSgwAtt) / VS.TauInterSgwAtt
Notes:
Default severity
Severity Details
Root Cause
RF problems may prevent the UE from sending or receiving messages
Possible problems with the eNB or the SGW
SGW is not available to provide service to the UE in the new Tracking Area
Because of SGW failure (no response from SGW or SGW reject the Create
Session/Modify Bearer Requests)
Internal failure
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiMafTauFailuresInterSgw
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
Verify that the eNB, and SGW links are in-service/normal, using link_cli.
Contact Alcatel-Lucent Customer Support to determine the status of the serving eNB
and the SGW Pools serving the eNB that is involved in the TAU procedure
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiNoPSHOFailuresOverSv
....................................................................................................................................................................................................................................
LSS_cpiNoPSHOFailuresOverSv
Description
The raised alarm LSS_cpiNoPSHOFailuresOverSv indicates meeting a threshold of the
Hand Down to UTRAN/GERAN via the Sv interface without PSHO Failure Rate CPI,
which is calculated every 5 minutes using this formula:
1 - ( ( VS.NbrSuccessCSHOSv + VS.NbrCSHOSvAbort_Other + VS.NbrCSHOSvAbort-
_Canceled ) / VS.AttCSHOSv )
Notes:
Default severity
Severity Details
Root Cause
attempted handovers of circuit-services only to UTRAN/GERAN via the Sv interface
may fail for any of the following reasons:
Sv interface problems - MME cannot communicate with the MSC
Handover preparation is rejected by the target UTRAN/GERAN network
UE fails to complete handover to the target radio access network due to RF conditions
Subscriber provisioning prohibits handover to UTRAN/GERAN
Internal MME error
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiNoPSHOFailuresOverSv
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 Check counters and alarms related to the Sv interface. Verify network connectivity and
proper configuration between the MME and MSC(s).
Check the target UTRAN/GERAN network for configuration problems that could
cause the handover preparation attempts to be rejected.
Check the source E-UTRAN network and target UTRAN/GERAN network for
handover failure conditions.
Check fs.log for error indications related to Sv interface procedures. Contact next
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiPSHOFailuresOverSv
....................................................................................................................................................................................................................................
LSS_cpiPSHOFailuresOverSv
Description
The raised alarm LSS_cpiPSHOFailuresOverSv indicates meeting a threshold of the
Hand Down to UTRAN/GERAN via the Sv interface with PSHO Failure Rate CPI, which
is calculated every 5 minutes using this formula:
1 - ( ( VS.NbrSuccessPSHOSv + VS.NbrPSHOSvAbort_Other + VS.NbrPSHOSvAbort-
_Canceled ) / VS.AttPSHOSv )
Notes:
Default severity
Severity Details
Root Cause
attempted SRVCC handover of circuit and packet services to UTRAN/GERAN via the Sv
interface may fail for any of the following reasons:
Sv interface problems - MME cannot communicate with the MSC
Handover preparation is rejected by the target UTRAN/GERAN network
UE fails to complete handover to the target radio access network due to RF conditions
Subscriber provisioning prohibits handover to UTRAN/GERAN
Internal MME error
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiPSHOFailuresOverSv
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 Check counters and alarms related to the Sv interface. Verify network connectivity and
proper configuration between the MME and MSC(s).
Check the target UTRAN/GERAN network for configuration problems that could
cause the handover preparation attempts to be rejected.
Check the source E-UTRAN network and target UTRAN/GERAN network for
handover failure conditions.
Check fs.log for error indications related to Sv interface procedures. Contact next
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiS3TauFailures
....................................................................................................................................................................................................................................
LSS_cpiS3TauFailures
Description
The raised alarm, LSS_cpiS3TauFailures, indicates meeting/exceeding a threshold of the
rate of failure of Tracking Area Update procedures from an SGSN to the MME over an S3
link. This alarm is calculated every 5 minutes using the formula:
(VS.TauAttS3 - VS.TauSuccS3) / VS.TauAttS3
Notes:
Default severity
CRITICAL, MAJOR, MINOR, WARNING
Severity Details
Root Cause
Possible failure reasons:
Possible problems with the eNB or the MME.
RF problems prevent UE from sending/receiving messages.
SGW is not available to provide service to the UE in the new Tracking Area.
SGSN does not respond.
Link failures to the SGSN, SGW, eNB and/or HSS.
Internal MME errors.

...................................................................................................................................................................................................
1 Verify that the eNB, SGW, HSS, and SGSN S3 links are in-service/normal, using link_cli.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiS3TauFailures
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Verify the operational status of the SGSN and that the SGSN is responding to messages
over the S3 link.
...................................................................................................................................................................................................
3 Verify the operational status of the DNS server and that the DNS entries for the SGW are
correct.
...................................................................................................................................................................................................
4 Contact Alcatel-Lucent Customer Support to determine the status of the serving eNB, the
HSS, and the SGW serving the eNB that is involved in the TAU procedure.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiS3TauFailuresInterSgw
....................................................................................................................................................................................................................................
LSS_cpiS3TauFailuresInterSgw
Description
The raised alarm, LSS_cpiS3TauFailuresInterSGW, indicates meeting/exceeding a
threshold of the rate of failure of Tracking Area Update procedures from an SGSN to the
MME over an S3 link that involves a change of serving SGW. This alarm is calculated
every 5 minutes using the formula:
(VS.TauInterSgwAttS3 - VS.TauInterSgwSuccS3) / VS.TauInterSgwAttS3
Notes:
Default severity
Severity Details
Root Cause

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiS3TauFailuresInterSgw
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
over the S3 link.
...................................................................................................................................................................................................
correct.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiS3TauFailuresIntraSGW
....................................................................................................................................................................................................................................
LSS_cpiS3TauFailuresIntraSGW
Description
The raised alarm, LSS_cpiS3TauFailuresIntraSGW, indicates meeting/exceeding a
threshold of the rate of failure of Tracking Area Update procedures from an SGSN to the
MME over an S3 link that do not involve a change of serving SGW. This alarm is
calculated every 5 minutes using the formula:
(VS.TauIntraSgwAttS3 - VS.TauIntraSgwSuccS3) / VS.TauIntraSgwAttS3
Notes:
Default severity
Severity Details
Root Cause
Invalid DNS entries for the SGW (if SGW Discovery is active/enabled).

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiS3TauFailuresIntraSGW
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
over the S3 link.
...................................................................................................................................................................................................
correct.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiStopWarnMsgDeliveryS1MMEFailureRate
....................................................................................................................................................................................................................................
LSS_cpiStopWarnMsgDeliveryS1MMEFailureRate
Description
The raised alarm LSS_cpiStopWarnMsgDeliveryS1MMEFailureRate indicates meeting a
threshold of the Stop Warning Message Delivery S1MME Failure Rate CPI, which is
100 - (100 * (VS.NbrSuccessStopWarnMsgDeliveryS1MME /
VS.AttStopWarnMsgDeliveryS1MME))
Notes:
Default severity
Severity Details
Root Cause
Possible problems with the MME.
Link failure to target eNBs.
Verify the MME_TAI table contains the correct TAIs.

...................................................................................................................................................................................................
1 Verify that the S1MME links are in-service/normal, using link_cli.

...................................................................................................................................................................................................
2 Verify the operational status of the eNBs and that the eNBs are responding to messages
over the S1MME link.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiStopWarnMsgDeliveryS1MMEFailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Contact Alcatel-Lucent Customer Support to determine the status of the eNBs that are
involved in the Stop Warning Message procedure.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiStopWarnMsgDeliverySBcFailureRate
....................................................................................................................................................................................................................................
LSS_cpiStopWarnMsgDeliverySBcFailureRate
Description
The raised alarm LSS_cpiStopWarnMsgDeliverySBcFailureRate indicates meeting a
threshold of the Stop Warning Message Delivery SBc Failure Rate CPI, which is
100 - (100 * (VS.NbrSuccessStopWarnMsgDeliverySBc / VS.AttStopWarnMsgDelivery-
SBc))
Notes:
Default severity
Severity Details
Root Cause
Possible problems with the CBC or the MME.
Link failure to the CBC.

...................................................................................................................................................................................................
1 Verify that the SBC links are in-service/normal, using link_cli.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiStopWarnMsgDeliverySBcFailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 Verify the operational status of the CBC.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Contact Alcatel-Lucent Customer Support to determine the status of the CBC and eNBs
that are involved in the Stop Warning Message procedure.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiUECapacityUsage
....................................................................................................................................................................................................................................
LSS_cpiUECapacityUsage
Description
The raised alarm, cpiUECapacityUsage, indicates meeting a threshold of a UE capacity
utilization rate on a per board basis in the last 5 minutes. The utilization rate is calculated
in every interval of 5 minutes by using this formula:
( Number of maximum registered on a board / UE capacity of a single board ) * 100%
Notes:
The alarm clears if no threshold is met in one of the subsequent intervals.
Default severity
Severity Details
Root Cause
The alarm is fired when the number of the maximum registered UEs crosses the
predefined threshold on a single board.

...................................................................................................................................................................................................
1 Check how many boards the WMM has and consider to install more boards to increase
the WMM capacity.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiWarnMsgDeliveryS1MMEFailureRate
....................................................................................................................................................................................................................................
LSS_cpiWarnMsgDeliveryS1MMEFailureRate
Description
The raised alarm LSS_cpiWarnMsgDeliveryS1MMEFailureRate indicates meeting a
threshold of the Warning Message Delivery S1MME Failure Rate CPI, which is
100 - (100 * (VS.NbrSuccessWarnMsgDeliveryS1MME /
VS.AttWarnMsgDeliveryS1MME))
Notes:
Default severity
Severity Details
Root Cause
Possible problems with the MME.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiWarnMsgDeliveryS1MMEFailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Contact Alcatel-Lucent Customer Support to determine the status of the eNBs that are
involved in the Write Replace Warning Message procedure.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiWarnMsgDeliverySBcFailureRate
....................................................................................................................................................................................................................................
LSS_cpiWarnMsgDeliverySBcFailureRate
Description
The raised alarm LSS_cpiWarnMsgDeliverySBcFailureRate indicates meeting a threshold
of the Warning Message Delivery SBc Failure Rate CPI, which is calculated every 5
100 - (100 * (VS.NbrSuccessWarnMsgDeliverySBc / VS.AttWarnMsgDeliverySBc))
Notes:
Default severity
Severity Details
Root Cause
Possible problems with the CBC or the MME.
Link failure to the CBC.

...................................................................................................................................................................................................
1 Verify that the SBC links are in-service/normal, using link_cli.

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_cpiWarnMsgDeliverySBcFailureRate
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Verify the operational status of the CBC.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Contact Alcatel-Lucent Customer Support to determine the status of the CBC and eNBs
that are involved in the Write Replace Warning Message procedure.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_dataMismatch
....................................................................................................................................................................................................................................
LSS_dataMismatch
Description
A data mismatch has been detected, which indicates that there has been an error in
provisioning. The additionalText field of the event provides the details of the data
mismatch. Currently supported data mismatches are listed in the table below:
MH_SH_PROVISIONING WMM link (S1mme, S6a, An interface profile has been

S13, SGs) associated with an SCTP
profile that indicates either
single-homed or
multi-homed, but the network
interface types (ni-types)
associated with a network
interface do not match that
configuration. For example
for SGs, the singled-homed
ni-type is SGS, and the
multi-homed ni-types are
SGS_1 and SGS_2, so if the
SCTP profile indicates
single-homed, an SGs
network interface must have
an ni-type type of SGS, and if
the SCTP profile indicates
multi-homed, an SGs
interface must have ni-types
of SGS_1 and SGS_2. The
additionalText field indicates
the type of homing
provisioned and the
inconsistency found.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
MH_PROVISIONED_IPS Link An SCTP multi-homed link

has been provisioned with
remote addresses that do not
match the addresses that were
learned from the remote end
in the INIT-ACK message.
There is either a provisioning
mistake on the WMM, or on
the remote end of the
connection. The
additionalText field of the
event will indicate the
provisioned (LCL) IP
addresses and the remote
(RMT) learned addresses
which caused the discrepancy.
The state of each IP address is
indicated after the IP address,
e.g. 1.2.3.4(STATE), where
STATE is one of; R -
reachable, U - unreachable, C
- unconfirmed.
This alarm must be manually cleared after the provisioned data is corrected.
Default severity
WARNING
Root Cause
The following table indicates the cause for the events referred to by their identifier in the
previous table:
MH_SH_PROVISIONING An SCTP profile associated with an interface

indicates multi-homing or single-homing, but
the ni-types associated with the interface do
not match the indicated type of homing.
MH_PROVISIONED_IPS The SCTP IP addresses provisioned for an
interface do not match the IP addresses learned
from the remote end in the SCTP INIT-ACK
message.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 The following table indicates the recovery procedure for the events referred to by their
identifier in the previous table:
MH_SH_PROVISIONING Correct the SCTP profile for this link type to

indicate the correct homing type (SH or MH),
or configure the correct ni-types for the link,
so that they match the SCTP profile.
MH_PROVISIONED_IPS Correct the provisioning of the locally
provisioned remote IPs to match the learned
remote IPs, or change the provisioning on the
remote end to match the locally provisioned
remote IPs.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_excessiveExternalLinksDown
....................................................................................................................................................................................................................................
LSS_excessiveExternalLinksDown
Description
An excessive number of links of a given type (e.g. s1mme, s11, etc.) are down. This is
usually due to a network connectivity problem and not the individual links between the
WMM and the external entity. Once this alarm is triggered the WMM will stop reporting
alarms and status for links of the given type. Once the network problem is resolved and
the number of links down is no longer excessive, this alarm will clear and the status of all
links of the given type will be updated. This alarm is raised when at least 100 links of a
given type are down. This alarm clears when 95 or fewer links are down.
Default severity
CRITICAL
Root Cause
The possible causes of this alarm are:
1. A large number network entities are out-of-service or undergoing initialization.
2. Packet or HeartBeat message loss due to network issues.
3. Provision data is incorrect on MME for network entities the MME communicates
with.
4. Software failure prevents communication established between MME and other
network entities.

...................................................................................................................................................................................................
1 Determine that there are no errors within the IP network.

...................................................................................................................................................................................................
2 If the network entity data is provisioned on MME, verify the data is correct.
...................................................................................................................................................................................................
3 Verify the network entity that MME fails to communicate with is in service.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_externalLinkConfigurationLimit
....................................................................................................................................................................................................................................
LSS_externalLinkConfigurationLimit
Description
The maximum number of links for a given link type has been reached. When this limit is
reached, it is not possible to create any new links of the given link type. Every 15 minutes
a check will be performed in an attempt to recover any links which have not been used or
have been disabled due to lack of far-end response. A configurable parameter, TdynMO ,
is used to control the aging algorithm for link recovery.
Default severity
MAJOR
Root Cause
This alarm is caused when there are too many link of a given type in use.

...................................................................................................................................................................................................
1 Wait at least TdynMO time interval to allow the system to recover inactive or disabled
links.
...................................................................................................................................................................................................
2 If the system does not recover any links after TdynMO time interval, contact
Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_externalLinkDown
....................................................................................................................................................................................................................................
LSS_externalLinkDown
Description
Communication between WMM and another network entity can not be established.
Default severity
CRITICAL, MAJOR
Root Cause
1. Remote network entity is out-of-service or undergoing initialization.
3. Provision data is incorrect on WMM for network entities the WMM communicates
with.
4. Software failure prevents communication established between WMM and other
network entities.

...................................................................................................................................................................................................
1 Verify the network entity that WMM fails to communicate with is in service.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 If the network entity data is provisioned on WMM, verify the data is correct.
...................................................................................................................................................................................................
4 If multiple links that terminate on the MIF (X1_1 or X2) are down, try switching MIF to
hot-standby mate.
...................................................................................................................................................................................................
5 If multiple links that terminate on the MPH (non-X1_1 and non-X2) are down, try
switching MPH to hot-standby mate.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedAttachReqsRateExceeded
....................................................................................................................................................................................................................................
LSS_failedAttachReqsRateExceeded
Description
The raised alarm, LSS_failedAttachReqsRateExceeded, indicates the value of the
VS.cpiAttachFailures measurement, monitored when failure Attach request CPI exceeded
a threshold in the last 15 minute interval. This value computes the failure rate for the UE
Attach procedure, and compares the calculation against provisioned thresholds for Minor,
Major, and Critical alarm conditions
Notes:
Default severity
Severity Details
Root Cause
Internal error
Procedure collision with ongoing HSS or SGW procedure
Invalid data in Attach Request message (includes protocol failures or invalid message
content)
UE Authentication Failure due to invalid validation of RES returned in Authentication
Response message or Authentication Failure received by UE
HSS failure in response to AIR
HSS failure in response to ULR
NAS message timeout (message include Authentication Response, Security Mode
Complete, Attach Complete)
ENB returns Initial Context Setup Failure
Timeout occurs while waiting for Initial Context Setup Response
Double S1 connection
Unexpected S1 release
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedAttachReqsRateExceeded
....................................................................................................................................................................................................................................
Bad NAS ESM Information Response
Bad NAS message in ESM container (PDN Connectivity Request, Activate Default
Bearer Response)
SGW failure in response to Create Session Request
UE returns Activate Default Bearer Reject
SGW failure in response to Modify Bearer Request

...................................................................................................................................................................................................
1
Verify that the eNB, HSS and SGW links are in-service/normal, using link_cli.
If the links look normal, and the alarm persists, contact Alcatel-Lucent Customer
Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedAuthRequestsHSSRateExceeded
....................................................................................................................................................................................................................................
LSS_failedAuthRequestsHSSRateExceeded
Description
The raised alarm, LSS_failedAuthRequestsHSSRateExceeded, indicates the value of
VS.cpiHSSauthFailures measurement, monitored when HSS failed Authentication
requests exceeded a threshold in the last 15 minute interval. This value computes the
failure rate for the Authentication procedure between the MME and the HSS, and
compares the calculation against provisioned thresholds for Minor, Major, and Critical
alarm conditions
Notes:
Default severity
MAJOR
Severity Details
Major Alarm: Rate value > 10
Root Cause
The Authentication Information Request (AIR message from the MME to the HSS for
requesting authentication vectors) failures exceeded the failure limit. The AIR could have
failed for any of the following reasons:
Internal database error
Internal error sending messages between proxies/managers
Can not send the AIR message to the HSS
The HSS did not respond
The response from the HSS was empty
The response from the HSS could not be decoded
The response from the HSS had a failure result code or experimental result code
The response from the HSS included more authentication vectors than what was
requested
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedAuthRequestsHSSRateExceeded
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 Clearance options include:

Ensure communication between the MME and HSS (ping)
If the HSS (S6a) link looks normal (using link_cli), and alarm persists, contact
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedAuthRequestsUERateExceeded
....................................................................................................................................................................................................................................
LSS_failedAuthRequestsUERateExceeded
Description
The raised alarm, LSS_failedAuthRequestsUERateExceeded, indicates the value of
VS.cpiUEauthFailures measurement, monitored when UE failed Authentication requests
exceeded a threshold in the last 15 minute interval. This value computes the failure rate
for the Authentication procedure between the MME and the UE and compares the
calculation against provisioned thresholds for Minor, Major, and Critical alarm
conditions.
Notes:
Default severity
MAJOR
Severity Details
Major Alarm: Rate value > 10
Root Cause
Internal error

...................................................................................................................................................................................................
1
Verify HSS and UE authentication data, using ueadmin_cli.
If the authentication data looks good, and the alarm persists, contact Alcatel-Lucent
Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedCrDedBearerReqsRateExceeded
....................................................................................................................................................................................................................................
LSS_failedCrDedBearerReqsRateExceeded
Description
The raised alarm, LSS_failedCrDedBearerReqsRateExceeded, indicates the value of
VS.cpiCreateDedicatedBearerFailures measurement, monitored when failure on Create
Dedicated Bearer request exceeded a threshold in the last 15 minute interval. This value
computes the failure rate for the Create Dedicated Bearer procedure, and compares the
conditions.
Notes:
Default severity
Severity Details
Root Cause
Internal error
Collision with another EMM or BSM procedure
No resource available (currently MME only supports one dedicated bearer)
Bad S11 message (Create Bearer Request)
UE returns failure on Activate Dedicated Bearer Request
ENB returns failure on E-RAB Setup Request
Timeout waiting for UE or ENB's response
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedCrDedBearerReqsRateExceeded
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedDeactDedBearerReqsRateExceeded
....................................................................................................................................................................................................................................
LSS_failedDeactDedBearerReqsRateExceeded
Description
The raised alarm, LSS_failedDeactDedBearerReqsRateExceeded, indicates the value of
VS.cpiDeactivateDedBearerFailures measurement, monitored when failure on Deactivate
computes the failure rate for the Deactivate Dedicated Bearer procedure, and compares
the calculation against provisioned thresholds for Minor, Major, and Critical alarm
conditions.
Notes:
Default severity
Severity Details
Root Cause
Internal error
Invalid data in Delete Bearer Request message (includes protocol failures or invalid
message content)
The response to the SGW could not be encoded
SGW failure on Delete Bearer Request

...................................................................................................................................................................................................
1
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedHRPDhandoverRateExceeded
....................................................................................................................................................................................................................................
LSS_failedHRPDhandoverRateExceeded
Description
The raised alarm, LSS_failedHRPDhandoverRateExceeded, indicates the value of
VS.cpiHRPDHoFailures measurement, monitored when failure on a HRPD Handover
request exceeded a threshold in the last 15 minute interval. This value computes the
failure rate for the Handover to HRPD procedure, and compares the calculation against
Notes:
Default severity
Severity Details
Root Cause
See the list of failure counters for the Handover to HRPD procedure. There are several
failure causes, each with a separate failure counter. The calculation for this alarm
implicitly uses the sum of all the failure counters for the Attach procedure.

...................................................................................................................................................................................................
1 Look at all the failure counters for the Handover to HRPD procedure in the PMC XML
files to determine if one failure cause predominates. If one is found, check User
Documentation for any remedies specific to the found cause.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedMobileTermLocRequestRateExceeded
....................................................................................................................................................................................................................................
LSS_failedMobileTermLocRequestRateExceeded
Description
The raised alarm LSS_failedMobileTermLocRequestRateExceeded indicates meeting a
threshold of the Mobile Termination Location Request Failure CPI, which is calculated
1 - ( ( VS.NbrSuccessMobileTermLocRequests + VS.AbortMobileTermLocRequest_HO
+ VS.AbortMobileTermLocRequest_MMEreloc + VS.AbortMobileTermLocRequest_O-
ther + VS.AbortMobileTermLocRequest_UEdetach ) / VS.AttMobileTermLocRequests )
Notes:
The thresholds are configurable.
Default severity
Severity Details
Root Cause
Problems with the eNB or SMLC involved in request
Incorrect provisioning of SMLC to TA
SMLC is not available to provide service
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedMobileTermLocRequestRateExceeded
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
Verify that the S1-MME and SLs links are in-service/normal, using link_cli.
Refer to the Location Based Services failure counters to get a more specific failure
reason.
Contact Alcatel-Lucent Customer Support to determine the status of the SMLC that
are involved in the LCS procedure.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedNetwrkInducedLocRequestRateExceeded
....................................................................................................................................................................................................................................
LSS_failedNetwrkInducedLocRequestRateExceeded
Description
The raised alarm LSS_failedNetwrkInducedLocRequestRateExceeded indicates meeting
a threshold of the Network Induced Location Request Failure CPI, which is calculated
1 - ( ( VS.NbrSuccessNetwrkInducedLocRequests + VS.AbortNetwrkInducedLocRe-
quest_HO + VS.AbortNetwrkInducedLocRequest_MMEreloc + VS.AbortNetwrkInduc-
edLocRequest_Other + VS.AbortNetwrkInducedLocRequest_UEdetach ) /
VS.AttNetwrkInducedLocRequests )
Notes:
The thresholds are configurable.
Default severity
Severity Details
Root Cause
Problems with the eNB or SMLC involved in request
Incorrect provisioning of SMLC to TA
SMLC is not available to provide service
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedNetwrkInducedLocRequestRateExceeded
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
Verify that the S1-MME and SLs links are in-service/normal, using link_cli.
Refer to the Location Based Services failure counters to get a more specific failure
reason.
Contact Alcatel-Lucent Customer Support to determine the status of the SMLC that
are involved in the LCS procedure.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedNumHOFwdRelocRateExceeded
....................................................................................................................................................................................................................................
LSS_failedNumHOFwdRelocRateExceeded
Description
The raised alarm, LSS_failedNumHOFwdRelocRateExceeded, indicates the value of
VS.cpiHOwMMErelocFailures_atTarget measurement, monitored when failure on
Handover request, with MME forward relocation, exceeded a threshold in the last 15
minute interval. This value computes the failure rate at the Target MME for the Handover
procedure with MME relocation, and compares the calculation against provisioned
Notes:
Default severity
Severity Details
Root Cause
See the list of failure counters for the Handover procedure with MME relocation (at the
Target MME). There are several failure causes, each with a separate failure counter. The
calculation for this alarm implicitly uses the sum of all the failure counters for the Attach
procedure.

...................................................................................................................................................................................................
1 Look at all the failure counters for the Handover procedure with MME relocation (at the
Target MME) in the PMC XML files to determine if one failure cause predominates. If
one is found, check User Documentation for any remedies specific to the found cause.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedNumHOPathSwNewSgwRateExceeded
....................................................................................................................................................................................................................................
LSS_failedNumHOPathSwNewSgwRateExceeded
Description
The raised alarm, LSS_failedNumHOPathSwNewSgwRateExceeded, indicates the value
of VS.cpiHOwSGWrelocFailures measurement, monitored when failure on Handover
Path Switch request, to a different Serving Gateway, exceeded a threshold in the last 15
minute interval. This value computes the failure rate for the Handover procedure without
MME relocation and with SGW relocation, and compares the calculation against
Notes:
Default severity
Severity Details
Root Cause
See the list of failure counters for the Handover procedure without MME relocation and
with SGW relocation. There are several failure causes, each with a separate failure
counter. The calculation for this alarm implicitly uses the sum of all the failure counters
for the Attach procedure.

...................................................................................................................................................................................................
1 Look at all the failure counters for the Handover procedure without MME relocation and
with SGW relocation in the PMC XML files to determine if one failure cause
predominates. If one is found, check User Documentation for any remedies specific to the
found cause.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedNumHOPathSwSameSgwRateExceeded
....................................................................................................................................................................................................................................
LSS_failedNumHOPathSwSameSgwRateExceeded
Description
The raised alarm, LSS_failedNumHOPathSwSameSgwRateExceeded, indicates the value
of VS.cpiHOwNoRelocFailures measurement, monitored when failure on Handover Path
Switch request, to same Serving Gateway, exceeded a threshold in the last 15 minute
interval. This value computes the failure rate for the Handover procedure without MME
relocation and without SGW relocation, and compares the calculation against provisioned
Notes:
Default severity
Severity Details
Root Cause
SGW failed to switch the S1-U downlink path to the new ENB

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedNumHORequiredRateExceeded
....................................................................................................................................................................................................................................
LSS_failedNumHORequiredRateExceeded
Description
The raised alarm, LSS_failedNumHORequiredRateExceeded, indicates the value of
VS.cpiHOwMMErelocFailures_atSource measurement, monitored when failure on
Handover request, with MME relocation, exceeded a threshold in the last 15 minute
interval. This value computes the failure rate at the source MME for the Handover
procedure with MME relocation, and compares the calculation against provisioned
Notes:
Default severity
Severity Details
Root Cause
See the list of failure counters for the Handover procedure with MME relocation (at the
Source MME). There are several failure causes, each with a separate failure counter. The
calculation for this alarm implicitly uses the sum of all the failure counters for the Attach
procedure.

...................................................................................................................................................................................................
1 Look at all the failure counters for the Handover procedure with MME relocation (at the
Source MME) in the PMC XML files to determine if one failure cause predominates. If
one is found, check User Documentation for any remedies specific to the found cause.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedS1MMEconnEstRateExceeded
....................................................................................................................................................................................................................................
LSS_failedS1MMEconnEstRateExceeded
Description
The raised alarm, LSS_failedS1MMEconnEstRateExceeded, indicates the value of
VS.cpiS1MMEconnFailures measurement, monitored when failed S1MME Connect
failure rate for the eNB connection over S1-MME, and compares the calculation against
Notes:
Default severity
Severity Details
Root Cause
PLMN and tracking area data was not provisioned correctly

...................................................................................................................................................................................................
1 Verify PLMN or TAI provisioning data, via the SAM. After validation of the data, if the
problem persists, contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedServiceReqsRateExceeded
....................................................................................................................................................................................................................................
LSS_failedServiceReqsRateExceeded
Description
The raised alarm, LSS_failedServiceReqsRateExceeded, indicates the value of
cpiServiceRequestFailures measurement, monitored when failure on Service request
for the UE Service Request procedure, and compares the calculation against provisioned
Notes:
Default severity
Severity Details
Root Cause
Internal error
Invalid data in Service Request message (includes protocol failures or invalid
message content)
NAS message timeout (message include Authentication Response or Security Mode
Complete)
SGW failure on Modify Bearer Request
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedServiceReqsRateExceeded
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 Ensure the S11 links to SGW are normal, using link_cli. If the links look normal, and
alarm persists, contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedTAURateExceeded
....................................................................................................................................................................................................................................
LSS_failedTAURateExceeded
Description
The raised alarm, LSS_failedTAURateExceeded, indicates the value of
VS.cpiTauFailures measurement, monitored when failure on Tracking Area Update
failure rate for the TAU procedure, and compares the calculation against provisioned
Notes:
Default severity
Severity Details
Root Cause
Internal error
Invalid data in Tracking Area Update Request message (includes protocol failures or
invalid message content)
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedTAURateExceeded
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedUpdBearerReqsRateExceeded
....................................................................................................................................................................................................................................
LSS_failedUpdBearerReqsRateExceeded
Description
The raised alarm, LSS_failedUpdBearerReqsRateExceeded, indicates the value of
cpiUpdateBearerFailures measurement, monitored when failure on Update Bearer request
for the Update Bearer procedure, and compares the calculation against provisioned
Notes:
Default severity
Severity Details
Root Cause
Internal error

...................................................................................................................................................................................................
1 Ensure S11 links are normal, using link_cli. If the links are normal, and the alarm persists,
contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_failedUpdDedBearerReqsRateExceeded
....................................................................................................................................................................................................................................
LSS_failedUpdDedBearerReqsRateExceeded
Description
The raised alarm, LSS_failedUpdDedBearerReqsRateExceeded, indicates the value of
VS.cpiUpdateDedicatedBearerFailures measurement, monitored when failure on Update
computes the failure rate for the Update Dedicated Bearer procedure, and compares the
conditions.
Notes:
Default severity
Severity Details
Root Cause
Internal error
Invalid data in Update Dedicated Bearer Request message (includes protocol failures
or invalid message content)
The response to the SGW could not be encoded
SGW failure on Update Dedicated Bearer Request

...................................................................................................................................................................................................
1
Verify that S11 links are normal, using link_cli. If links are normal, and the alarm
persists, contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_ggsnDnsError
....................................................................................................................................................................................................................................
LSS_ggsnDnsError
Description
GGSN DNS Selection unable to retrieve IP Address. This alarm must be manually
cleared.
Default severity
MINOR
Root Cause
WMM is unable to retrieve GGSN IP Address.

...................................................................................................................................................................................................
1 Verfiy that the GGSN IP Address is provisioned correctly on DNS server.

...................................................................................................................................................................................................
2 Manually clear the alarm.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_internalCommunicationFailure
....................................................................................................................................................................................................................................
LSS_internalCommunicationFailure
Description
Communication between active MIF member and active MAF/SAF member failed or
communications between active MIF member and active MPH member failed.
Default severity
CRITICAL, MAJOR
Root Cause
1. MPH, MIF or MAF/SAF pool has duplex failed or is undergoing initialization.
2. Software failure prevents communication establishment between MIF and MAF/SAF
or MIF and MPH.

...................................................................................................................................................................................................
1 Verfiy MPH, MIF and/or MAF/SAF have not been forced out-of-service.
...................................................................................................................................................................................................
2 If communication is lost between the MPH and the MIF and it does not come back
automatically, and MPH pool is in Active / Hot-standby state, try switching MPH to the
standby member.
...................................................................................................................................................................................................
3 If communication is lost between the MAF/SAF and the MIF and it does not come back
automatically, and MAF/SAF pool is in Active / Hot-standby state, try switching
MAF/SAF to the standby member.
...................................................................................................................................................................................................
4 If communiaction is lost between the MIF and MPH and the MIF and MAF/SAFs and it
does not come back automatically, and MIF pool is in Active / Hot-standby state, try
switching MIF to the standby member.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_ippuBusError
....................................................................................................................................................................................................................................
LSS_ippuBusError
Description
There is a bus error on the indicated host between the HSPP4 hardware (iPPU) in the
AMC slot and the host hardware.
Default severity
CRITICAL
Root Cause
List of root causes:
The HSPP4 AMC itself has failed.
The iPPU service on HSPP4 is in a transient state.
The iPPU service on HSPP4 has failed.
There is no HSPP4 AMC and a user is attempting to run the iPPU/PMB software for
SGSN.

...................................................................................................................................................................................................
1 Determine if any related alarms are also present, such as on the ESC, chassis, or board
itself. Correct those alarms first and see if this alarm clears as a result.
...................................................................................................................................................................................................
2
1. On Alcatel-Lucent 9471 WMM:
Utilize ippu_cli to print the status of the board on the OAM host.
...................................................................................................................................................................................................
3
Verify the appropriate FRUID via shelf manager is present in the given ShelfId
CardId.
...................................................................................................................................................................................................
4
Visually verify HSPP4 hardware is present in the AMC slot of the alarm indicated
with a ShelfId and cardId.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_ippuBusError
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5
On the Shelf Manager, verify the shelf and card in the alarm has an HSPP4 iPPU in
the AMC slot. If HSPP4 is not detected, attempt to powercycle the card.
...................................................................................................................................................................................................
6
the AMC slot. If HSPP4 is not detected, attempt to re-seat the card in the alarm by
ShelfId and CardId.
...................................................................................................................................................................................................
7
the AMC slot. If HSPP4 is not detected, replace the card used for this host using the
appropriate FRU procedure as necessary.
...................................................................................................................................................................................................
8
Attempt to reset the entire host (ShelfId/CardId) via appropriate CLI or MI. Before
attempting this action, verify that there is an ACTIVE or STANDBY mate present in
the system.
...................................................................................................................................................................................................
9 If the above steps do not clear the alarm, contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_ippuResourceReset
....................................................................................................................................................................................................................................
LSS_ippuResourceReset
Description
There was a software reset on the iPPU in the HSPP4 AMC or a restart by the PMB
process in the host identified by ShelfId and CardId.
Default severity
MAJOR
Root Cause
The iPPU HSPP4 software has reset.
The iPPU HSPP4 software has restarted.
The PMB process on the given host has restarted.

...................................................................................................................................................................................................
1 Determine if any related alarms are present. Correct those alarms first and see if this
alarm clears as a result.
...................................................................................................................................................................................................
2
...................................................................................................................................................................................................
3
Before attempting this action, verify that there is an ACTIVE or STANDBY mate
present in the system. Attempt to reset the entire card (shelf/slot) via appropriate CLI
interface or MI.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_liNearingCapacityLimit
....................................................................................................................................................................................................................................
LSS_liNearingCapacityLimit
Description
The number of lawful interceptions has reached 80% of MAF/SAF capacity.
Default severity
WARNING
Root Cause
1. Use of lawful interception beyond design capacity.
2. Software failure causing unnecesary interception.

...................................................................................................................................................................................................
1 Use the query option of the li_target_cli command to verify that the appropriate set of
UEs are selected for lawful interception.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_maxDurationExpiredOnHRPDhandover
....................................................................................................................................................................................................................................
LSS_maxDurationExpiredOnHRPDhandover
Description
The raised alarm, LSS_maxDurationExpiredOnHRPDhandover, indicates the value of
VS.cpiMaxDurationHRPDhandover measurement, monitored when timed out on HRPD
handover request exceeded a threshold in the last 15 minute interval. This value is the
maximum time taken to perform a Handover to HRPD.
Notes:
Default severity
MAJOR
Severity Details
Major Alarm: Timeout value > 300
Root Cause
The cause for exceeding the expected maximum cannot be determined precisely.

...................................................................................................................................................................................................
1 Check the network routers for possible network delay. When the MME is programmed to
include internal delay measurements, check these PMC values.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_mmeDnsError
....................................................................................................................................................................................................................................
LSS_mmeDnsError
Description
MME DNS Selection unable to retrieve MME IP Address associated with FQDN. This
alarm must be manually cleared.
Default severity
MINOR
Root Cause
MME is unable to retrieve MME IP Address associated with FQDN.

...................................................................................................................................................................................................
1 Verify that the FQDN is provisioned correctly in DNS server.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_noResetAckReceived
....................................................................................................................................................................................................................................
LSS_noResetAckReceived
Description
No RESET ACKNOWLEDGEMENT message was received from the RNC after the
WMM has sent and resent a RESET message.
Default severity
MINOR
Root Cause
2. Message loss due to network issues.
3. Software failure prevents communication between WMM and the RNC.

...................................................................................................................................................................................................
1 Verify the RNC that WMM fails to get the message from with is in service.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_numTOS10gtpcRateExceeded
....................................................................................................................................................................................................................................
LSS_numTOS10gtpcRateExceeded
Description
The raised alarm, LSS_numTOS10gtpcRateExceeded, indicates the value of
VS.cpiGTPcResponseTO_S10 measurement, monitored when missing replies to
S10(gtpc) request exceeded a threshold in the last 15 minute interval. This value
computes the cpiage of Response messages that are not received over S10, and compares
conditions.
Notes:
Default severity
Severity Details
Root Cause
The cause is Unknown from the measurements involved in this calculation.

...................................................................................................................................................................................................
1 Check the network routers for any problems. Check to determine if any other MME
elements are having problems.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Description
VS.cpiGTPcResponseTO_S11 measurement, monitored when missing replies to
S11(gtpc) request exceeded a threshold in the last 15 minute interval. This value
computes the cpiage of Response messages that are not received over S11, and compares
conditions.
Notes:
Default severity
Severity Details
Root Cause
Internal error
Timeout waiting for SGW response on MME's Request

...................................................................................................................................................................................................
1 Verify that S11 links are normal, using link_cli. If links are normal, and the alarm persists,
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Description
VS.numTOS3gtpcRateExceeded measurement, monitored when missing replies to
S3(gtpc) request exceeded a threshold in the last 5 minute interval. This value computes
the percentage of Response messages that are not received over S3, and compares the
conditions.
Notes:
Default severity
Severity Details
Root Cause
Internal error
Timeout waiting for SGW response on MME's Request

...................................................................................................................................................................................................
1 Verify that S3 links are normal, using link_cli. If links are normal, and the alarm persists,
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_pathAvailability
....................................................................................................................................................................................................................................
LSS_pathAvailability
Description
This alarm is raised when SCTP path becomes unavailable. The local and remote
provisioned addresses need to be checked for use of the correct 2 sub-networks provided.
If the provisioned addresses match the 2 physical subnets, and if all address provisioned
are also correct, then the physical network that carries the subnet used in the path
"unavailable" alarm needs to be investigated for trouble. The specifics of the path are
documented in the "additionalText" field of the alarm. These alarms may need to be
cleared manually: as alarms are reported when path connectivity is established, however
their contents are a function of provisioned addresses (paths) that may be wrong and
changed when the connection is down, and may no longer match with the path that was
originally alarmed.
Default severity
MINOR
Root Cause
The provisioning of the SCTP endpoints on either (i.e. IP addresses) the WMM or the
remote entity are incorrect, or the network between the endpoints is experiencing
problems.

...................................................................................................................................................................................................
1 Verify that the endpoints IP addresses on the WMM are the remote entity are provisioned
correctly.
...................................................................................................................................................................................................
2 Verify that the network between the WMM and the remote entity is functioning correctly.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_pgwDnsError
....................................................................................................................................................................................................................................
LSS_pgwDnsError
Description
MME DNS Selection unable to retrieve PGW IP Address associated with FQDN. This
Default severity
MINOR
Root Cause
MME is unable to retrieve PGW IP Address associated with FQDN.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_provisioningError
....................................................................................................................................................................................................................................
LSS_provisioningError
Description
Missing provisioning of TAI-to-LAI mapping to MSC in 2G/3G operator for SGS based
CSFB/SMS.
Default severity
WARNING
Root Cause
Missing provisioning of TAI-LAI mapping to MSC in 2G/3G operator.

...................................................................................................................................................................................................
1 Provision missing entries in TAI-LAI mapping table utilizing LAI in 2G/3G operator.
Refer to user text in alarm.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_sgsnDnsError
....................................................................................................................................................................................................................................
LSS_sgsnDnsError
Description
SGSN DNS Selection unable to retrieve SGSN IP Address associated with FQDN. This
Default severity
MINOR
Root Cause
WMM is unable to retrieve SGSN IP Address associated with FQDN.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
MME Alarms LSS_taiFqdnError
....................................................................................................................................................................................................................................
LSS_taiFqdnError
Description
MME DNS Selection unable to retrieve SGW IP Address associated with FQDN. this
Default severity
MINOR
Root Cause
MME is unable to retrieve SGW IP Address associated with FQDN.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
3 SGSN Alarms
3
Overview
Purpose
This chapter contains alarms that are specific only to the SGSN.
Contents
LSS_cdrStorageSpaceThreshold 3-3
LSS_cgfNotResponding 3-4
LSS_cgfServiceNotSupported 3-5
LSS_cgfSystemFailure 3-6
LSS_cgfVersionNotSupported 3-7
LSS_cpiGTPcResponseTOGn 3-8
LSS_cpiGTPcResponseTOS3 3-10
LSS_cpiUECapacityUsage 3-12
LSS_excessiveExternalLinksDown 3-13
LSS_externalLinkDown 3-14
LSS_ggsnDnsError 3-15
LSS_internalCommunicationFailure 3-16
LSS_ippuBusError 3-17
LSS_ippuResourceReset 3-19
LSS_liNearingCapacityLimit 3-20
LSS_msThreshold 3-21
LSS_noResetAckReceived 3-22
LSS_nseBandwidthThreshold 3-23
LSS_pathAvailability 3-24
...................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms Overview
....................................................................................................................................................................................................................................
LSS_pdpThreshold 3-25
LSS_sgsnDnsError 3-26
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_cdrStorageSpaceThreshold
....................................................................................................................................................................................................................................
LSS_cdrStorageSpaceThreshold
Description
CDRs storage space threshold reached
Default severity
MINOR, MAJOR
Root Cause
Loss of communication with the Charging Gateway

...................................................................................................................................................................................................
1 Continue to the next action only if the system does not clear the alarm.
...................................................................................................................................................................................................
2 Test the accessibility to the Charging Gateway (ping command).

...................................................................................................................................................................................................
3 Trace the route to the Charging Gateway (traceroute command).

...................................................................................................................................................................................................
4 If the problem persists, contact Alcatel-Lucent Customer Support.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_cgfNotResponding
....................................................................................................................................................................................................................................
LSS_cgfNotResponding
Description
SGSN/CGF interface: CGF not responding
Default severity
WARNING
Root Cause
Loss of communication with the Charging Gateway

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Test the accessibility to the Charging Gateway (ping command).

...................................................................................................................................................................................................
3 Trace the route to the Charging Gateway (traceroute command).

...................................................................................................................................................................................................
4 if the problem persists, contact Alcatel-Lucent Customer Support.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_cgfServiceNotSupported
....................................................................................................................................................................................................................................
LSS_cgfServiceNotSupported
Description
The Charging Gateway is not able to process the CDRs transmitted by the SGSN.
Default severity
WARNING
Root Cause
The Charging Gateway is not able to process the CDRs transmitted by the SGSN.

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_cgfSystemFailure
....................................................................................................................................................................................................................................
LSS_cgfSystemFailure
Description
SGSN/CGF interface: 'system failure' response
Default severity
WARNING
Root Cause
A problem has occurred at Charging Gateway. GTP' cause received by SGSN is System
failure.

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_cgfVersionNotSupported
....................................................................................................................................................................................................................................
LSS_cgfVersionNotSupported
Description
The version of GTP' supported by the SGSN is not supported by the Charging Gateway.
Default severity
WARNING
Root Cause
The version of GTP supported by the SGSN is not supported by the Charging Gateway.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Check GTP version at Charging Gateway.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_cpiGTPcResponseTOGn
....................................................................................................................................................................................................................................
LSS_cpiGTPcResponseTOGn
Description
The raised alarm, LSS_cpiGTPcResponseTOGn, indicates that the value of
VS.cpiGTPcResponseTOGn has exceeded a threshold in the last 15 minute interval. This
counter monitors the percentage of GTP Requests sent over a Gn interface for which no
Response is received by the WMM. The Gn interface connects the WMM with one or
more SGSNs. The calculated percentage is compared against provisioned thresholds for
Minor, Major, and Critical alarm conditions.
Notes:
Default severity
Severity Details
Root Cause
reasons:
Network problems between the WMM and the SGSN
Internal errors at the WMM

...................................................................................................................................................................................................
connectivity and proper configuration between WMM and SGSNs. If SGSNs and
one failure cause predominates, and check fs.log to determine if errors related to the Gn
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_cpiGTPcResponseTOGn
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_cpiGTPcResponseTOS3
....................................................................................................................................................................................................................................
LSS_cpiGTPcResponseTOS3
Description
The raised alarm, LSS_cpiGTPcResponseTOS3, indicates meeting a threshold of GTP
response failure rate in the last 5 minute interval. This failure rate monitors the percentage
of GTP Requests sent over an S3 interface for which no Response is received by the
MME. The S3 interface connects the MME with one or more SGSNs. The calculated
percentage is compared against provisioned thresholds for Minor, Major, and Critical
alarm conditions.
Notes:
component.
Default severity
Severity Details
Root Cause
reasons:
Network problems between the MME and the SGSN

...................................................................................................................................................................................................
connectivity and proper configuration between MME and SGSNs. If SGSNs and network
connectivity are verified, examine all the GTP failure counters to determine if one failure
cause predominates, and check fs.log to determine if errors related to the S3 interface
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_cpiGTPcResponseTOS3
....................................................................................................................................................................................................................................
have been reported. Contact next level of support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_cpiUECapacityUsage
....................................................................................................................................................................................................................................
LSS_cpiUECapacityUsage
Description
The raised alarm, cpiUECapacityUsage, indicates meeting a threshold of a UE capacity
utilization rate on a per board basis in the last 5 minutes. The utilization rate is calculated
in every interval of 5 minutes by using this formula:
( Number of maximum registered on a board / UE capacity of a single board ) * 100%
Notes:
component.
The alarm will be cleared if no threshold is met in one of the subsequent intervals.
Default severity
Severity Details
Root Cause
The alarm is fired when the number of the maximum registered UEs crosses the
predefined threshold on a single board.

...................................................................................................................................................................................................
1 Check how many boards the WMM has and consider installing more board to increase the
WMM capacity.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_excessiveExternalLinksDown
....................................................................................................................................................................................................................................
LSS_excessiveExternalLinksDown
Description
An excessive number of links of a given type (e.g. s1mme, s11, etc.) are down. This is
usually due to a network connectivity problem and not the individual links between the
WMM and the external entity. Once this alarm is triggered the WMM will stop reporting
alarms and status for links of the given type. Once the network problem is resolved and
the number of links down is no longer excessive, this alarm will clear and the status of all
links of the given type will be updated. This alarm is raised when at least 100 links of a
given type are down. This alarm clears when 95 or fewer links are down.
Default severity
CRITICAL
Root Cause
1. A large number network entities are out-of-service or undergoing initialization.
3. Provision data is incorrect on MME for network entities the MME communicates
with.
4. Software failure prevents communication established between MME and other
network entities.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 If the network entity data is provisioned on MME, verify the data is correct.
...................................................................................................................................................................................................
3 Verify the network entity that MME fails to communicate with is in service.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_externalLinkDown
....................................................................................................................................................................................................................................
LSS_externalLinkDown
Description
Communication between WMM and another network entity can not be established.
Default severity
CRITICAL, MAJOR
Root Cause
3. Provision data is incorrect on WMM for network entities the WMM communicates
with.
4. Software failure prevents communication established between WMM and other
network entities.

...................................................................................................................................................................................................
1 Verify the network entity that WMM fails to communicate with is in service.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 If the network entity data is provisioned on WMM, verify the data is correct.
...................................................................................................................................................................................................
4 If multiple links that terminate on the MIF (X1_1 or X2) are down, try switching MIF to
hot-standby mate.
...................................................................................................................................................................................................
5 If multiple links that terminate on the MPH (non-X1_1 and non-X2) are down, try
switching MPH to hot-standby mate.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_ggsnDnsError
....................................................................................................................................................................................................................................
LSS_ggsnDnsError
Description
GGSN DNS Selection unable to retrieve IP Address. This alarm must be manually
cleared.
Default severity
MINOR
Root Cause
WMM is unable to retrieve GGSN IP Address.

...................................................................................................................................................................................................
1 Verfiy that the GGSN IP Address is provisioned correctly on DNS server.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_internalCommunicationFailure
....................................................................................................................................................................................................................................
LSS_internalCommunicationFailure
Description
Communication between active MIF member and active MAF/SAF member failed or
communications between active MIF member and active MPH member failed.
Default severity
CRITICAL, MAJOR
Root Cause
1. MPH, MIF or MAF/SAF pool has duplex failed or is undergoing initialization.
2. Software failure prevents communication establishment between MIF and MAF/SAF
or MIF and MPH.

...................................................................................................................................................................................................
1 Verfiy MPH, MIF and/or MAF/SAF have not been forced out-of-service.
...................................................................................................................................................................................................
2 If communication is lost between the MPH and the MIF and it does not come back
automatically, and MPH pool is in Active / Hot-standby state, try switching MPH to the
standby member.
...................................................................................................................................................................................................
3 If communication is lost between the MAF/SAF and the MIF and it does not come back
automatically, and MAF/SAF pool is in Active / Hot-standby state, try switching
MAF/SAF to the standby member.
...................................................................................................................................................................................................
4 If communiaction is lost between the MIF and MPH and the MIF and MAFs/SAFs and it
does not come back automatically, and MIF pool is in Active / Hot-standby state, try
switching MIF to the standby member.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_ippuBusError
....................................................................................................................................................................................................................................
LSS_ippuBusError
Description
There is a bus error on the indicated host between the HSPP4 hardware (iPPU) in the
AMC slot and the host hardware.
Default severity
CRITICAL
Root Cause
The HSPP4 AMC itself has failed.
The iPPU service on HSPP4 is in a transient state.
The iPPU service on HSPP4 has failed.
There is no HSPP4 AMC and a user is attempting to run the iPPU/PMB software for
SGSN.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
2
...................................................................................................................................................................................................
3
Verify the appropriate FRUID via shelf manager is present in the given ShelfId
CardId.
...................................................................................................................................................................................................
4
Visually verify HSPP4 hardware is present in the AMC slot of the alarm indicated
with a ShelfId and cardId.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_ippuBusError
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5
the AMC slot. If HSPP4 is not detected, attempt to powercycle the card.
...................................................................................................................................................................................................
6
the AMC slot. If HSPP4 is not detected, attempt to re-seat the card in the alarm by
ShelfId and CardId.
...................................................................................................................................................................................................
7
the AMC slot. If HSPP4 is not detected, replace the card used for this host using the
...................................................................................................................................................................................................
8
Attempt to reset the entire host (ShelfId/CardId) via appropriate CLI or MI. Before
attempting this action, verify that there is an ACTIVE or STANDBY mate present in
the system.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_ippuResourceReset
....................................................................................................................................................................................................................................
LSS_ippuResourceReset
Description
There was a software reset on the iPPU in the HSPP4 AMC or a restart by the PMB
process in the host identified by ShelfId and CardId.
Default severity
MAJOR
Root Cause
The iPPU HSPP4 software has reset.
The iPPU HSPP4 software has restarted.
The PMB process on the given host has restarted.

...................................................................................................................................................................................................
1 Determine if any related alarms are present. Correct those alarms first and see if this
alarm clears as a result.
...................................................................................................................................................................................................
2
...................................................................................................................................................................................................
3
Before attempting this action, verify that there is an ACTIVE or STANDBY mate
present in the system. Attempt to reset the entire card (shelf/slot) via appropriate CLI
interface or MI.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_liNearingCapacityLimit
....................................................................................................................................................................................................................................
LSS_liNearingCapacityLimit
Description
The number of lawful interceptions has reached 80% of MAF/SAF capacity.
Default severity
WARNING
Root Cause
1. Use of lawful interception beyond design capacity.
2. Software failure causing unnecesary interception.

...................................................................................................................................................................................................
1 Use the query option of the li_target_cli command to verify that the appropriate set of
UEs are selected for lawful interception.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_msThreshold
....................................................................................................................................................................................................................................
LSS_msThreshold
Description
Number of attached MS or UE threshold reached
Default severity
MINOR, MAJOR
Root Cause
The number of UEs attached to the SGSN has reached a minor / major value. This value
is given as a percentage of the maximum number of UEs that the SGSN can attach. The
SGSN processing capacity may be undersized

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_noResetAckReceived
....................................................................................................................................................................................................................................
LSS_noResetAckReceived
Description
No RESET ACKNOWLEDGEMENT message was received from the RNC after the
WMM has sent and resent a RESET message.
Default severity
MINOR
Root Cause
2. Message loss due to network issues.
3. Software failure prevents communication between WMM and the RNC.

...................................................................................................................................................................................................
1 Verify the RNC that WMM fails to get the message from with is in service.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_nseBandwidthThreshold
....................................................................................................................................................................................................................................
LSS_nseBandwidthThreshold
Description
NSE bandwidth threshold reached
Default severity
MINOR, MAJOR
Root Cause
The NSE bandwidth has reached a minor / major value. This value is given as a
percentage of the MAX NSE

...................................................................................................................................................................................................
1 Analyze the operation context of the alarm. Determine if this alarm is structural or
conjectural.
...................................................................................................................................................................................................
2 Analyse the figures reported by the observation counters to evaluate how quick the NSE
bandwidth has increased.Depending of the result of the investigations:
...................................................................................................................................................................................................
3 If the NSE bandwidth remains over this threshold most of the time, and if alarm with
major severity also appears, upgrade of the SGSN configuration must be performed.
Please contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_pathAvailability
....................................................................................................................................................................................................................................
LSS_pathAvailability
Description
This alarm is raised when SCTP path becomes unavailable. The local and remote
provisioned addresses need to be checked for use of the correct 2 sub-networks provided.
If the provisioned addresses match the 2 physical subnets, and if all address provisioned
are also correct, then the physical network that carries the subnet used in the path
"unavailable" alarm needs to be investigated for trouble. The specifics of the path are
documented in the "additionalText" field of the alarm. These alarms may need to be
cleared manually: as alarms are reported when path connectivity is established, however
their contents are a function of provisioned addresses (paths) that may be wrong and
changed when the connection is down, and may no longer match with the path that was
originally alarmed.
Note: this alarm is cleared when the path's SCTP association changes operational state,
either from "Enabled" to "Disabled" or from "Disabled" to "Enabled". This change could
result from an administrative lock or unlock action, or a change in the collective
availability of the association's paths. Any path unreachable alarms will be cleared. If the
new association state is "Disabled", a single link/association alarm (LSS_mmeExternal-
LinkDown) will be raised.
Default severity
MAJOR
Root Cause
The provisioning of the SCTP endpoints on either (i.e. IP addresses) the WMM or the
remote entity are incorrect, or the network between the endpoints is experiencing
problems.

...................................................................................................................................................................................................
1 Verify that the endpoints IP addresses on the WMM are the remote entity are provisioned
correctly.
...................................................................................................................................................................................................
2 Verify that the network between the WMM and the remote entity is functioning correctly.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_pdpThreshold
....................................................................................................................................................................................................................................
LSS_pdpThreshold
Description
Number of activated PDP context threshold reached.
Default severity
MINOR, MAJOR
Root Cause
The number of PDP contexts that the SGSN can support has reached a minor / major
value. This value is given as a percentage of the maximum number of PDP contexts that
the SGSN can support. The SGSN processing capacity may be undersized

...................................................................................................................................................................................................
1 Analyze the operation context of the alarm. Determine if this alarm is structural or
conjectural.
...................................................................................................................................................................................................
2 Analyze the observation counters values to evaluate how quick the number of activated
PDP contexts has increased. Depending on the result of the investigations:
...................................................................................................................................................................................................
3 If the activated PDP contexts overload corresponds to a specific peak, you don't need to
perform any upgrade of the SGSN. If alarm LSS_pdpThreshold is present as major, the
activated PDP contexts overload is constant. There is a gap between the demand of PS
services and the SGSN processing capacity. You need to upgrade the SGSN
configuration. Please contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
SGSN Alarms LSS_sgsnDnsError
....................................................................................................................................................................................................................................
LSS_sgsnDnsError
Description
SGSN DNS Selection unable to retrieve SGSN IP Address associated with FQDN. This
Default severity
MINOR
Root Cause
WMM is unable to retrieve SGSN IP Address associated with FQDN.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
4 BASE_ATCA Alarms
4
Overview
Purpose
This chapter contains platform alarms that may be applicable to Alcatel-Lucent products
that utilize the ATCA.
The WMM application is built on a common platform used by many different
applications. The WMM does not use all of the capabilities of the platform and therefore,
some base ATCA alarms may not be applicable. In addition, certain functionality defined
within some alarms may also not be applicable to the WMM such as the following: CDR,
SS7, FS5K, FS GUI, NGSS, TL1, and CPSB.
Contents
ATCA_AggregatePowerSensor 4-6
ATCA_AggregateTemperatureSensor 4-7
ATCA_BoardPower 4-8
ATCA_CPLDState 4-9
ATCA_DS75Temperature 4-11
ATCA_ExhaustTemp 4-13
ATCA_FPGATemp 4-15
ATCA_FanSpeed 4-17
ATCA_FanTrayPresence 4-18
ATCA_FanTraysFRU 4-19
ATCA_FilterPresence 4-21
ATCA_I2CLocalBus 4-22
ATCA_IPMBLink 4-23
ATCA_InletTemp 4-24
...................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms Overview
....................................................................................................................................................................................................................................
ATCA_LM75Temperature 4-26
ATCA_LM83Temperature 4-28
ATCA_LMeUC75Temperature 4-30
ATCA_LMeUC75Top-Rig 4-32
ATCA_LocalTemperature 4-34
ATCA_MMCTemp 4-35
ATCA_OcteonTemperature 4-37
ATCA_OutletTemp 4-38
ATCA_PayloadCurrent 4-40
ATCA_PayloadVoltage 4-42
ATCA_PowerOk 4-44
ATCA_ShelfFRUs 4-45
ATCA_UnexpectedDeact 4-47
ATCA_m48vSensor 4-48
LSS_cardConnectionLost 4-49
LSS_cardError 4-51
LSS_cpiAlrmCritical 4-52
LSS_cpiAlrmMajor 4-53
LSS_cpiAlrmMinor 4-54
LSS_cpiAlrmWarning 4-55
LSS_cpiAsrtEsc 4-56
LSS_cpiAsrtNonEsc 4-58
LSS_cpiAsrtNonEscCritical 4-60
LSS_cpiAsrtNonEscMajor 4-62
LSS_cpiAsrtNonEscMinor 4-64
LSS_cpiAudErrCount 4-66
LSS_cpiAudManAct 4-68
LSS_cpiAudNewEvent 4-70
LSS_cpiExceptionService 4-72
LSS_cpiFileSysUsage 4-74
LSS_cpiMemAllocFail 4-75
LSS_cpiReinitServiceSelf 4-76
LSS_cpuOverload 4-78
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
LSS_databaseConnectionLost 4-79
LSS_databaseReplicationLinkDown 4-80
LSS_databaseSizeExhausted 4-81
LSS_dbHighCpuUtilization 4-82
LSS_dbOffline 4-83
LSS_dbStatusUnexpected 4-84
LSS_degradedResource 4-85
LSS_degrow 4-126
LSS_diskGoingDown 4-127
LSS_diskSector 4-128
LSS_dnsThreshold 4-129
LSS_ethernetError 4-130
LSS_ethernetLinkDown 4-131
LSS_externalConnectivity 4-133
LSS_fru 4-134
LSS_grow 4-135
LSS_hostDown 4-136
LSS_memoryOverload 4-137
LSS_nodeGroupOOS 4-138
LSS_nodeOOS 4-139
LSS_numberOfTuplesInUse 4-140
LSS_osSecInfoModificationDetected 4-141
LSS_osSecInformationMissing 4-142
LSS_osSecUnexpectedInformation 4-143
LSS_patch 4-144
LSS_pktCorruptionDetectedViaRCCLANCheck 4-145
LSS_platformCommandFailure 4-146
LSS_pmDataNotCollected 4-147
LSS_processDown 4-148
LSS_processNotStarted 4-149
LSS_remoteQueryServerFailure 4-152
LSS_remotedbLinkDown 4-153
LSS_restore 4-154
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
LSS_serviceOnewayCommunication 4-155
LSS_sheddingOverload 4-156
LSS_shmcEthernetError 4-157
LSS_simxml 4-158
LSS_softwareAllocatedResourceOverload 4-159
LSS_softwareComponentStandbyNotReady 4-160
LSS_svcdegrow 4-161
LSS_svcgrow 4-162
LSS_swVersionMismatch 4-163
LSS_tftpDownloadCorrupt 4-164
LSS_threadsExhausted 4-166
LSS_upgrade 4-167
LSS_virtualClusterDown 4-168
RALARM_Loop 4-169
RALARM_Power 4-170
SYS_BackupFailure 4-171
SYS_CPM_USERDATA_INCONSITENCY 4-172
SYS_CPM_USERDATA_RESTORED 4-173
SYS_Configuration 4-174
SYS_EventQueueCapacity 4-176
SYS_ICMPFailure 4-177
SYS_IPsecConfig 4-178
SYS_LinkDown 4-179
SYS_NotifyDisabled 4-180
SYS_NotifyLocked 4-181
SYS_RADIUS_TO_LDAP_FAILURE 4-182
SYS_ROOT_ACCESS_DENIED 4-183
SYS_ROOT_FTP_VIOLATION 4-184
SYS_ROOT_LOGIN_VIOLATION 4-185
SYS_ROOT_SSH_LOGIN_VIOLATION 4-186
SYS_SNETrapOverload 4-187
SYS_SNMPAuthenticationFailure 4-188
SYS_SNMPFailure 4-189
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
SYS_SU_TO_ROOT_FAILURE 4-190
SYS_SYSTEMTrapOverload 4-191
SYS_SetupAAAFailure 4-192
SYS_TestAlarm 4-193
SYS_ThresholdCrossed 4-194
SYS_UndiscoveredObject 4-195
SYS_WriteAAAFailure 4-196
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_AggregatePowerSensor
....................................................................................................................................................................................................................................
ATCA_AggregatePowerSensor
Description
The aggregate power sensor alarm provides a summary status of all power related
conditions adversely affecting a resource. When this alarm occurs, in most cases, there is
another power related alarm that provides more details about the exact resource power
sensor that is reporting the condition. From the MI GUI, alarms on a resource may be
retrieved by selecting the managed object for that resource and then selecting the
right-click operation to display related alarms.
Default severity
Root Cause
There is a power related problem with the resource.

...................................................................................................................................................................................................
1 Investigate all other temperature and power related alarms on the resource and follow
those alarms fault recovery procedures. Once all of these related alarms are cleared, this
alarm clears.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_AggregateTemperatureSensor
....................................................................................................................................................................................................................................
ATCA_AggregateTemperatureSensor
Description
The aggregate temperatures sensor alarm provides a summary status of all temperature
related conditions adversely affecting a resource. When this alarm occurs, in most cases,
there is another temperature related alarm that provides more details about the exact
resource temperature sensor that is reporting the condition. From the MI GUI, alarms on a
resource may be retrieved by selecting the managed object for that resource and then
selecting the right-click operation to display related alarms.
Default severity
Root Cause
There is a temperature related problem with the resource.

...................................................................................................................................................................................................
1 Investigate all other temperature and power related alarms on the resource and follow
those alarms fault recovery procedures. Once all of these related alarms are cleared, this
alarm clears.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_BoardPower
....................................................................................................................................................................................................................................
ATCA_BoardPower
Description
A board is either in the inactive or not present state. This means that the board has been
powered down.
Default severity
MAJOR
Root Cause
Possible root causes:
Blade has been powered off.
Blade has been removed from the chassis.
There is a faulty connection between the blade and the chassis.

...................................................................................................................................................................................................
1 Verify that the blade is powered on. This can be performed remotely using CLI on the
shelf manager or locally by observing specific LEDs and their status
...................................................................................................................................................................................................
2 Verify that the blade is seated correctly in the chassis. Try to re-seat the blade in the
chassis.
...................................................................................................................................................................................................
3 Replace the blade if necessary, refer to FRU procedure. Contact Alcatel-Lucent Customer
Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_CPLDState
....................................................................................................................................................................................................................................
ATCA_CPLDState
Description
This alarm indicates a change in the redundancy status of the shelf management cards.
The specific problem of the alarm contains the specific redundancy state of the shelf
management card.
Possible states are as follows:
STATE_00: The current Shelf Manager is Active with no Backup.
STATE_01: The current Shelf Manager is Active with a Backup.
STATE_02: The current Shelf Manager is a Backup.
STATE_04: The Shelf Manager is a Backup but the remote presence bit is not set.
STATE_05: The Shelf Manager is a Backup but the remote switchover request bit is
not set.
STATE_06: The Shelf Manager is a Backup but the CPLD Active bit is set.
STATE_07: The Shelf Manager is Active with a Backup but the remote presence bit is
not set.
STATE_08: The Shelf Manager is Active with a Backup but the remote healthy bit is
not set.
STATE_09: The Shelf Manager is Active with a Backup but the CPLD Active bit is
not set.
STATE_10: The local presence bit is not set for the current Shelf Manager.
STATE_11: The Shelf Manager is Active with no Backup but the remote healthy bit is
set.
STATE_12: The Shelf Manager is Active with no Backup but the remote switchover
request bit is set.
Default severity
MINOR
Root Cause
One of the shelf management cards is not present.
One of the shelf management cards is not seated appropriately.
One of the shelf management cards has a hardware problem
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_CPLDState
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 Verify that the shelf management card is inserted properly.

...................................................................................................................................................................................................
2 If the shelf management card is inserted, reseat the shelf management card
...................................................................................................................................................................................................
3 If reseating the shelf management card does not correct the problem, replace the shelf
management card
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_DS75Temperature
....................................................................................................................................................................................................................................
ATCA_DS75Temperature
Description
This alarm indicates that the AMC (Advanced Mezzanine Card) temperature monitoring
sensor has detected a threshold being crossed. By default, the thresholds are as follows:
Lower Minor Threshold not supported

Lower Major Threshold not supported
Lower Critical Threshold not supported
Upper Minor Threshold(RW) 40.000
Upper Major Threshold(RW) 60.000
Upper Critical Threshold(RW) 70.000
Positive Threshold Hysteresis 2.000
Negative Threshold Hysteresis 2.000
Default severity
MINOR, MAJOR, CRITICAL
Root Cause
Temperature of the AMC HDD has crossed a threshold.
The room or chassis air conditioning unit is defective.
The board is defective and overheating.

...................................................................................................................................................................................................
1 There is a condition in which this alarm, with minor severity, is being erroneously
reported by the hardware, so ignore any minor alarms pertaining to this sensor.
...................................................................................................................................................................................................
2 Check if there are other alarms that could explain the rise in temperature, especially fan
alarms. If there are, troubleshoot these alarms first.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_DS75Temperature
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Check that the room air conditioning system is operating properly.

...................................................................................................................................................................................................
4 Check that the fan units of the suspect chassis are operating correctly. If they are not,
replace the fan units according to the replacement procedure.
...................................................................................................................................................................................................
5 If fans are operating properly and if there is no other alarm, replace faulty FRU according
to the appropriate replacement procedure.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_ExhaustTemp
....................................................................................................................................................................................................................................
ATCA_ExhaustTemp
Description
This alarm indicates that the ASS7BF AMC (Advanced Mezzanine Card) temperature
monitoring sensor has detected a threshold being crossed. By default, the thresholds are
as follows:

Default severity
Root Cause
Temperature of the AMC SS7 has crossed a threshold.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_ExhaustTemp
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_FPGATemp
....................................................................................................................................................................................................................................
ATCA_FPGATemp
Description
This alarm indicates that the DCI AMC (Advanced Mezzanine Card) FPGA Temp
monitoring sensor has detected a threshold being crossed. This indicates there is a
problem with the die temperature of the DCI FPGA. The values for the FPGA Temp
sensor thresholds can be retrieved from the Shelf Management Card and have the
following format:
Lower Minor Threshold <value1>

Lower Major Threshold <value1>
Lower Critical Threshold <value1>
Upper Minor Threshold <value1>
Upper Major Threshold <value1>
Upper Critical ThresholdRW) <value1>
Positive Threshold Hysteresis <value1>
Negative Threshold Hysteresis <value1>
Default severity
Root Cause
Temperature of the AMC has crossed a threshold.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_FPGATemp
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_FanSpeed
....................................................................................................................................................................................................................................
ATCA_FanSpeed
Description
This alarm indicates that a fan's speed has crossed a threshold. By default, the threshold
settings are as follows:

Lower Major Threshold(RW) 492.000
Upper Minor Threshold not supported
Upper Major Threshold not supported
Upper Critical Threshold not supported
The additional text field of the alarm will indicate the fan and fan tray exhibiting the
behavior.
Default severity
MAJOR
Root Cause
One of the chassis' fan units has failed.

...................................................................................................................................................................................................
1 Replace the faulty fan unit according to the appropriate replacement procedure.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_FanTrayPresence
....................................................................................................................................................................................................................................
ATCA_FanTrayPresence
Description
This alarm indicates that one of the fan trays is not present in the chassis. The fan tray in
question will be identified in the additonalText field of the alarm.
Default severity
MAJOR
Root Cause
The fan tray is not properly seated.
The fan tray has been removed.

...................................................................................................................................................................................................
1 Insert the fan tray.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_FanTraysFRU
....................................................................................................................................................................................................................................
ATCA_FanTraysFRU
Description
This alarm indicates a problem with the fan trays.
The state of the fan tray FRU information is present in the specific problem of the alarm
and is one of the following:
STATE_00 All Fan Trays are OK.

STATE_01 Fan Trays type are different which is not an
allowed configuration.
STATE_02 Cooling parameters for the Fan Trays are not
compatible.
STATE_03 Cooling parameters for one or more of the Fan
Trays are not valid.
STATE_04 One or more of the Fan Trays up/front are
absent.
Default severity
MAJOR
Root Cause
One of the following:
1. Fan Tray types are different and not allowed by the site configuration.
2. Cooling parameters for Fan Trays are not compatible.
3. Cooling parameters for Fan Trays are not valid.
4. Fan Tray is absent.

...................................................................................................................................................................................................
1 Verify that all Fan Trays are properly seated in the chassis.
...................................................................................................................................................................................................
2 Verify that the type of Fan Trays are compatible. Contact Alcatel-Lucent Customer
Support if incompatible.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_FanTraysFRU
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Verify that the cooling parameters are set correctly. Contact Alcatel-Lucent Customer
Support to adjust parameters.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_FilterPresence
....................................................................................................................................................................................................................................
ATCA_FilterPresence
Description
A filter is not present in the chassis. The additional text field of the alarm will indicate
which filter is not present.
Default severity
MINOR
Root Cause
A filter is not present in the chassis.

...................................................................................................................................................................................................
1 Insert the filter that is not present.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_I2CLocalBus
....................................................................................................................................................................................................................................
ATCA_I2CLocalBus
Description
This alarm reports an abnormal condition in the hardware state of the I2C Local Bus.
From the I2C local Bus Monitoring point of view, the bus is divided in two parts :
internal channel: I2C Bus aboard the NBSHMC, in front of the I2C Bus MUX
external channels: I2C buses behind the I2C Bus MUX, there are 4 external channels:
channel 0: linked to ADT7462 of Fan Tray Up
channel 1: linked to ADT7462 of Fan Tray Low
channel 2: linked to Shelf EEPROM#1
channel 3: linked to Shelf EEPROM#2
Possible states of the I2C Local Bus are:
STATE_00: OK
STATE_01: internal BUS NOK
STATE_02: external channel 0 NOK
Default severity
MAJOR
Root Cause
I2C Local Bus sensor has detected a failure of the I2C bus.

...................................................................................................................................................................................................
1 If the condition does not clear, contact Alcatel-Lucent Customer Support

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_IPMBLink
....................................................................................................................................................................................................................................
ATCA_IPMBLink
Description
This alarm indicates a problem with the IPMB(Intelligent Platform Management Bus)
Link between the shelf manager and the board. This alarm may be reported by the shelf
manager for the portion of the link that it monitors, or by the board for the portion of the
link it monitors. The specific problem of the alarm will indicate the specific IPMB link
that is failing and the state of the link, which can be one of the following:
STATE_00:IPMB-A disabled, IPMB-B disabled
STATE_01:IPMB-A enabled, IPMB-B disabled
STATE_02:IPMB-A disabled, IPMB-B enabled
STATE_03:IPMB-A enabled, IPMB-B enabled
Default severity
MINOR
Root Cause
Hardware failure.
The IPMB link has been manually put in a disabled state.

...................................................................................................................................................................................................
1 If the Link has been manually disabled, try to enable the link from the active shelf
manager card with the command, "clia setipmbstate <IPMB address> [AB] 1".
...................................................................................................................................................................................................
2 If the board is reporting a link failure, replace the board.

...................................................................................................................................................................................................
3 If the shelf is reporting a link failure, replace the shelf management card.
...................................................................................................................................................................................................
4 If replacing the board and shelf management card do not solve the problem, replace the
shelf. Contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_InletTemp
....................................................................................................................................................................................................................................
ATCA_InletTemp
Description
This alarm indicates that the AMC (Advanced Mezzanine Card) Inlet Temp monitoring
sensor at the upper edge of the AMC has detected a threshold being crossed. The values
for the Inlet Temp sensor thresholds can be retrieved from the Shelf Management Card
and have the following format:

Upper Critical Threshold <value1>
Default severity
Root Cause

...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_InletTemp
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_LM75Temperature
....................................................................................................................................................................................................................................
ATCA_LM75Temperature
Description
This alarm indicates a temperature problem with a board.
The shelf management card has one LM75 sensor that monitors the temperature of the top
of the board (LM75 Temp. Up) and another that monitors the temperature of the bottom
of the board (LM75 Temp. Down). The default thresholds are as follows:
Lower Minor Threshold(RW) -56.000

Lower Major Threshold(RW) -56.000
Lower Critical Threshold(RW) -56.000
Positive Threshold Hysteresis not supported
Negative Threshold Hysteresis not supported
The non-shelf management cards have an LM75 temperature sensor (LM75 Local Temp)
that monitors the temperature of the rear side of the board. The default thresholds are as
follows:

Default severity
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Root Cause
Temperature of the board has crossed a threshold.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
ATCA_LM83Temperature
Description
This alarm indicates a temperature problem with a board. There are 5 LM83
sensors(LM83_1 Local,LM83_1 DBG,LM83_1 BASE,LM83_1 LSI,LM83_2 Local) that
monitor the temperature of the board. The default thresholds are as follows:


Default severity
Root Cause
Temperature of the board has crossed an alarmable threshold.
The shelf manager board is defective and overheating.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
6 If the problem persists, contact Alcatel-Lucent Customer Support..

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_LMeUC75Temperature
....................................................................................................................................................................................................................................
ATCA_LMeUC75Temperature
Description
This alarm indicates that the ASS7NB AMC (Advanced Mezzanine Card) temperature
as follows:

Default severity
Root Cause

...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_LMeUC75Temperature
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_LMeUC75Top-Rig
....................................................................................................................................................................................................................................
ATCA_LMeUC75Top-Rig
Description
This alarm indicates that the ASS7BN AMC (Advanced Mezzanine Card) temperature
as follows:

Default severity
Root Cause
A list of root causes:

...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_LMeUC75Top-Rig
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_LocalTemperature
....................................................................................................................................................................................................................................
ATCA_LocalTemperature
Description
This alarm indicates a temperature problem with a board.
Default severity
Root Cause

...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_MMCTemp
....................................................................................................................................................................................................................................
ATCA_MMCTemp
Description
This alarm indicates that the DCI AMC (Advanced Mezzanine Card) MMC Temp
monitoring sensor has detected a threshold being crossed. This indicates there is a
problem with the die temperature of the MMC FPGA. The values for the MMC Temp
sensor thresholds can be retrieved from the Shelf Management Card and have the
following format:

Default severity
Root Cause

...................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_MMCTemp
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_OcteonTemperature
....................................................................................................................................................................................................................................
ATCA_OcteonTemperature
Description
This alarm indicates a temperature problem with the Octeon module.
Default severity
Root Cause

...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_OutletTemp
....................................................................................................................................................................................................................................
ATCA_OutletTemp
Description
This alarm indicates that the AMC (Advanced Mezzanine Card) Outlet Temp monitoring
sensor at the lower edge of the AMC has detected a threshold being crossed. The values
for the Outlet Temp sensor thresholds can be retrieved from the Shelf Management Card
and have the following format:

Default severity
Root Cause

...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_OutletTemp
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_PayloadCurrent
....................................................................................................................................................................................................................................
ATCA_PayloadCurrent
Description
This alarm indicates a current problem on a board, resulting from the Payload Amps
sensor threshold being crossed.
The values for the Payload Amps sensor thresholds can be retrieved from the Shelf
Management Card, and have the following format:
Lower Minor Threshold(RW) <value1>

Lower Major Threshold(RW) <value2>
Lower Critical Threshold(RW) <value3>
Upper Minor Threshold(RW) <value4>
Upper Major Threshold(RW) <value5>
Upper Critical Threshold(RW) <value6>
Default severity
Root Cause
The card may have a current problem.
The power supply unit may have a problem.
The thresholds for the sensors may be incorrectly set.

...................................................................................................................................................................................................
1 Check if other cards in the chassis have a similar alarm. If this is the case, there may be a
problem with the power supply unit(s).
...................................................................................................................................................................................................
2 Replace the faulty card according to the appropriate replacement procedure.

...................................................................................................................................................................................................
3 Replace the interface unit located behind the faulty card according to the appropriate
replacement procedure.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_PayloadCurrent
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_PayloadVoltage
....................................................................................................................................................................................................................................
ATCA_PayloadVoltage
Description
This alarm indicates a voltage problem with a board.
There may be several voltage sensors present on each board (e.g. 5V, 3.3V, 12V), any of
which may be reporting a voltage problem. The Specific Problem field in the alarm will
indicate which sensor is reporting the problem. The threshold values may be retrieved
from the Shelf Management Card and have the following format:
Lower Minor Threshold(RW) <value1>

Lower Major Threshold(RW) <value2>
Lower Critical Threshold(RW) <value3>
Upper Minor Threshold(RW) <value4>
Upper Major Threshold(RW) <value5>
Upper Critical Threshold(RW) <value6>
Default severity
Root Cause
The card may have a voltage problem.
The power supply unit may have a problem.
The thresholds for the sensors may be incorrectly set.

...................................................................................................................................................................................................
1 Check if all of the cards in the chassis have the same alarm. If this is the case, replace the
power supply unit(s) according to the appropriate replacement procedure.
...................................................................................................................................................................................................
2 Replace the faulty card according to the appropriate replacement procedure.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_PayloadVoltage
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 Replace the interface unit located behind the faulty card according to the appropriate
replacement procedure.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_PowerOk
....................................................................................................................................................................................................................................
ATCA_PowerOk
Description
This alarm indicates state of power ok signal from ISPPAC.
Default severity
CRITICAL
Root Cause
The POWEROK is used to indicate that all voltages of SPM are OK, also including
D1V8_DIMM1, D1V8_DIMM2 and D1V8_DIMM3.
Any voltage issue of SPM card may lead to this alarm.

...................................................................................................................................................................................................
1 Verify that the blade is powered on.

...................................................................................................................................................................................................
2 Verify that the blade is seated correctly in the chassis. Try to re-seat the blade in the
chassis.
...................................................................................................................................................................................................
3 Replace the blade if necessary, refer to FRU procedure. Contact Alcatel-Lucent Customer
Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_ShelfFRUs
....................................................................................................................................................................................................................................
ATCA_ShelfFRUs
Description
This alarm indicates a problem with the shelf FRU information stored in the EEPROMSs
(located on the NFATCAV2 back panel and accessed via the I2C local bus). The
EEPROMS contents are validated when a shelf manager is initialized as the active shelf
manager, and periodically by the active shelf manager. The state of the shelf FRU
information is present in the specific problem of the alarm and is one of the following:
STATE_00: SHELF_FRUS_STATE_OK No problems.

STATE_01: SHELF_FRUS_STATE_INIT_0 The data is valid in both EEPROMS, but the
contents are not equal. Depending on the
configuration of EXIT_IF_NO_SHELF_FRU
(set to FALSE), the shelf manager may start
running in a non-working state, but no IPMCs
in the shelf can be powered up.
STATE_02: SHELF_FRUS_STATE_INIT_1 The data is invalid in one EEPROM. The
contents of the valid EEPROM are used to
initialize, and the invalid EEPROM is updated
to match the valid EEPROM.
STATE_03: SHELF_FRUS_STATE_FRU1_ The data is invalid in EEPROM1. The
INV contents of the valid EEPROM are used to
STATE_04: SHELF_FRUS_STATE_FRU2_ The data is invalid in EEPROM2. The
INV contents of the valid EEPROM are used to
STATE_05: SHELF_FRUS_STATE_FRU12_ The data is invalid in both EEPROMs.
INV
STATE_06: SHELF_FRUS_STATE_FRU12_ The data is valid in both EEPROMs, but they
DIF are different.
Default severity
CRITICAL, MINOR
Root Cause
The shelf FRU EEPROM data has been corrupted.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_ShelfFRUs
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 A firmware upgrade may be needed, contact Alcatel-Lucent Customer Support.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_UnexpectedDeact
....................................................................................................................................................................................................................................
ATCA_UnexpectedDeact
Description
This sensor reports unexpected deactivation (transition to INACTIVE state) origin. It is
asserted
upon transition to INACTIVE state and de-asserted upon transition to any other state.
000 none (in de-assertion event only).

100 power failure.
200 temperature protection mechanism requested
power off.
400 local CPU requested deactivation.
Default severity
CRITICAL
Root Cause
There should be additional information available to explain what caused the deactivation.
Voltage, temperature are two possibilities.

...................................................................................................................................................................................................
1 Look at sensor alarms to see why the card was deactivated and resolve underlying
problems.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms ATCA_m48vSensor
....................................................................................................................................................................................................................................
ATCA_m48vSensor
Description
This alarm indicates a problem with the -48V shelf power supply A and/or B feeds.
Default severity
MINOR, MAJOR
Root Cause
Circuit breakers tripped for power supply.
Power feed lost to chassis.

...................................................................................................................................................................................................
1 Contact the local power team.

...................................................................................................................................................................................................
2 Check the top rack power distribution unit's LED and circuit breakers. If any circuit
breakers are tripped, reset them.
...................................................................................................................................................................................................
3 If the alarm severity is MINOR, this indicates the power level has dropped to between
-48V and -41V, and may indicate the system is running on battery backup.
...................................................................................................................................................................................................
4 If both local and remote A sensors are reporting MAJOR alarms, this indicates the
problem is in the A power cable feeding the PDU.
...................................................................................................................................................................................................
5 If both local and remote B sensors are reporting MAJOR alarms, this indicates the
problem is in the B power cable feeding the PDU.
...................................................................................................................................................................................................
6 The alarm should clear once the problem is rectified. If it does not, contact Alcatel-Lucent
Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cardConnectionLost
....................................................................................................................................................................................................................................
LSS_cardConnectionLost
Description
REM detected a problem with its connectivity to a service member under its control, or a
service member has missed a heartbeat to REM.
Default severity
CRITICAL, MAJOR
Root Cause
Possible causes of this alarm are:
1. The service member has undergone an initialization or reconfiguration due to an
automatic action.
2. The communication path from REM to the service member has been lost or
interrupted.
3. REM has detected a loss of a heartbeat from the service member.

...................................................................................................................................................................................................
1 Verify the status on the service on the MI GUI. It should be "Out of Service". If it is
active, or standby hot, with its mate being active, or manually out-of-service
(unlocked/disabled/idle) then the alarm condition is not valid.
...................................................................................................................................................................................................
2 If communication to the service does not come back within several minutes (e.g. the
cardConnectionLost alarm does not clear), it may be necessary to connect to the card's
console-port to get the status of the service. Consult card specific documentation about
the console commands to obtain the card service state.
If you are not successful in connecting to the console, this could be due to either a
networking problem, or a fault in the card. If the card is inaccessible via console, it can be
recovered via the reset button, or by powercycling. Continued trouble may mean the card
is having some hardware difficulty; and Alcatel-Lucent Customer Support should be
contacted to determine the next step(s).
...................................................................................................................................................................................................
3 Try to ping the internal fixed service ip address of the service member from the host
which is running the active CNFG service. If pinging the service member from the CNFG
host succeeds, then go to Step 4; else go to Step 5.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cardConnectionLost
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 Determine if REM has a connection to the service member via the use of the netstat
command on the host which has the active CNFG service The following command gives
a list of IP addresses that REM has connected to via well-known port 20000:
netstat -a | grep 20000
Look for an "Established" connection to the service's IP address in the output of the above
command. If the service's IP address is not found in the output and this is the first time
you have visited this step, then go to Step 6. If the service's IP address is not found in the
output and this is the second time you have visited this step, then go to Step 7.
...................................................................................................................................................................................................
5 Check the IP connections from the host that has the active CNFG service member to the
switches and the routers. Check the connection to the card. If connection problems are
found, they must be fixed. One can also verify that the appropriate service IP addresses
have been plumbed and the appropriate service image has been downloaded to the card.
...................................................................................................................................................................................................
6 Try switching the CNFG service to its currently standby hot member via MI GUI.
...................................................................................................................................................................................................
7 Stop and start the CNFG service via the stopCNFG and startCNFG commands,
respectively. This will stop the REM process and restart it, among others within the
CNFG service. Once the CNFG service is active, the virtual cluster can be switched back.
Note that error recovery and provisioning ability is affected if the CNFG service is not
operational.
...................................................................................................................................................................................................
8 Restart/reload the service. This may be done via the MI GUI.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cardError
....................................................................................................................................................................................................................................
LSS_cardError
Description
This alarm indicates that a hardware diagnostic failure has been detected. Depending on
the criticality of the checks, alarms with various severities are generated.
Default severity
Root Cause
The Field Replaceable Unit (FRU) programmed data has been corrupted or was not
programmed correctly in the factory. (Minor alarm)
The hardware diagnostic results or FRU data were not retrievable from the hardware.
(Major alarm)
The hardware of the card for this host has reported a Built-in Self Test (BIST) or
Power-on Self Test (POST) diagnostic failure. (Critical alarm)

...................................................................................................................................................................................................
1 For the Critical Alarm, the card should be taken OOS and replaced.
...................................................................................................................................................................................................
2 For the Major Alarm, the card should be taken OOS and rebooted to see if the alarm
clears. If it does not clear or there are other reports from the card (such as Asserts)
reporting problems, the card should be left OOS and Alcatel-Lucent Customer Support
should be contacted.
...................................................................................................................................................................................................
3 For the Minor Alarm, contact Alcatel-Lucent Customer Support for the correction
procedure.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAlrmCritical
....................................................................................................................................................................................................................................
LSS_cpiAlrmCritical
Description
The raised alarm LSS_cpiAlrmCritical indicates the value of the VS.alrmCritical
measurement monitored by the Critical Alarms Count CPI exceeded a threshold in the last
15 minute interval.
This Performance Measurement (PM) counts the number of critical alarms issued by the
reporting resource.
Notes:
The thresholds are configurable on FSGUI CPI window.
Default severity
CRITICAL
Severity Details
Critical Alarm: CPI value > 10
Root Cause
This is a summary alarm to bring more attention to the other critical alarms being raised

...................................................................................................................................................................................................
1 Using the Maintenance Interface, examine the set of critical alarms or any other alarms
recently raised and address them.
...................................................................................................................................................................................................
2 This alarm clears automatically if the rate of critical alarm generation drops below the
threshold.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAlrmMajor
....................................................................................................................................................................................................................................
LSS_cpiAlrmMajor
Description
The raised alarm LSS_cpiAlrmMajor indicates the value of the VS.alrmMajor
measurement monitored by the Major Alarms Count CPI exceeded a threshold in the last
15 minute interval.
This Performance Measurement (PM) counts the number of major alarms issued by the
reporting resource.
Notes:
Default severity
CRITICAL
Severity Details
Root Cause
This is a summary alarm to bring more attention to the other major alarms being raised

...................................................................................................................................................................................................
1 Using the Maintenance Interface, examine the set of major alarms or any other alarms
...................................................................................................................................................................................................
2 This alarm clears automatically if the rate of major alarm generation drops below the
threshold.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAlrmMinor
....................................................................................................................................................................................................................................
LSS_cpiAlrmMinor
Description
The raised alarm LSS_cpiAlrmMinor indicates the value of the VS.alrmMinor
measurement monitored by the Minor Alarms Count CPI exceeded a threshold in the last
15 minute interval.
This Performance Measurement (PM) counts the number of minor alarms issued by the
reporting resource.
Notes:
Default severity
CRITICAL, MAJOR
Severity Details
Major Alarm: 20 < CPI value <= 30
Root Cause
This is a summary alarm to bring more attention to the other minor alarms being raised

...................................................................................................................................................................................................
1 Using the Maintenance Interface, examine the set of minor alarms or any other alarms
...................................................................................................................................................................................................
2 This alarm clears automatically if the rate of minor alarm generation drops below the
threshold.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAlrmWarning
....................................................................................................................................................................................................................................
LSS_cpiAlrmWarning
Description
The raised alarm LSS_cpiAlrmWarning indicates the value of the VS.alrmWarning
measurement monitored by the Warning Alarms Count CPI exceeded a threshold in the
last 15 minute interval.
This Performance Measurement (PM) counts the number of warning alarms issued by the
reporting resource.
Notes:
Default severity
Severity Details
Major Alarm: 25 < CPI value <= 50
Minor Alarm: 15 < CPI value <= 25
Root Cause
This is a summary alarm to bring more attention to the other warning alarms being raised

...................................................................................................................................................................................................
1 Using the Maintenance Interface, examine the set of warning alarms or any other alarms
...................................................................................................................................................................................................
2 This alarm clears automatically if the rate of warning alarm generation drops below the
threshold.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAsrtEsc
....................................................................................................................................................................................................................................
LSS_cpiAsrtEsc
Description
The raised alarm LSS_cpiAsrtEsc indicates the value of the VS.asrtESC measurement
monitored by the Escalating Asserts CPI exceeded a threshold in the last 15 minute
interval.
In software, defensive checks are placed to ensure expected inputs or boundary conditions
within routines are met. If such a check fails, an assert report is logged containing
information for the code author to debug the problem. The assert messages themselves are
not of much value to the operator.
When the problem is serious enough, such as being associated with a critical resource, an
assert that can result in escalation is used. Such asserts are tied to a leaky bucket
mechanism that measures the rate of these events. If the specified thresholds are reached,
a task restart is attempted. If that level of escalation continues to fail, then a process
initialization is done which leads to a switch-over of the service. Immediate escalation is
possible.
Notes:
Default severity
MAJOR, MINOR, WARNING
Severity Details
Major Alarm: CPI value > 20
Warning Alarm: 5 < CPI value <= 10
Root Cause
In this case, the cause of the problem is non-specific and is dependent upon the function
of the software generating the assert and the defensive check it is performing.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAsrtEsc
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 This alarm clears automatically if the rate of escalating assert generation drops below the
threshold. An automatic escalation would result in a switch over and should also drop the
rate of assert generation.
...................................................................................................................................................................................................
2 Determine if any other alarms have been recently raised on the resource reported and
address them.
...................................................................................................................................................................................................
3 Examine the recent Performance (PM) counts on the resource reported; they may suggest
more regarding this issue.
...................................................................................................................................................................................................
4 If a provisioning or configuration change was executed just before the alarm was raised,
consider that the change is causing the problem.
...................................................................................................................................................................................................
5 If a Software Update (SU) or Patch is being soaked, then this could indicate a problem
with the software delivered; immediately contact Alcatel-Lucent Customer Support.
...................................................................................................................................................................................................
6 If the PM counts indicates degradation of service and a switch over has not occurred,
switch the service to its redundant mate.
...................................................................................................................................................................................................
7 If the situation persists after a switch-over, be sure that the prior active host of the service
was removed from service and restored completely. Attempt another switch over to the
original active host for the service.
...................................................................................................................................................................................................
8 In all cases, contact customer support regarding this alarm.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAsrtNonEsc
....................................................................................................................................................................................................................................
LSS_cpiAsrtNonEsc
Description
The raised alarm LSS_cpiAsrtNonEsc indicates the value of the VS.asrtNonESC
measurement monitored by the Non-Escalating Asserts CPI exceeded a threshold in the
not of much value to the operator. Most of the time asserts are isolated events; however,
they can begin to accumulate in which case a more serious failure may be occurring for
which this alarm is bringing attention to.
Defensive checks are performed to prevent more serious outages if possible.
These asserts do not invoke any automatic recovery through escalation. A different assert
type is used for that and is monitored by the CPI called cpiAsrtEsc
Notes:
Default severity
Severity Details
Root Cause
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAsrtNonEsc
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1 This alarm clears automatically if the rate of non-escalating assert generation drops below
the threshold.
...................................................................................................................................................................................................
address them.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
6 If the PM counts indicates degradation of service, switch the service to its redundant
mate.
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAsrtNonEscCritical
....................................................................................................................................................................................................................................
LSS_cpiAsrtNonEscCritical
Description
The raised alarm LSS_cpiAsrtNonEscCritical indicates the value of the
VS.asrtNonESCCritical measurement monitored by the Critical Non-Escalating Asserts
CPI exceeded a threshold in the last 15 minute interval.
Asserts, which do not invoke any automatic recovery through escalation, are tagged with
levels of severity, in this case critical, to provide guidance to Alcatel-Lucent Customer
Support on the seriousness of the problem.
Notes:
Default severity
Severity Details
Root Cause
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAsrtNonEscCritical
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
the threshold.
...................................................................................................................................................................................................
address them.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
mate.
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAsrtNonEscMajor
....................................................................................................................................................................................................................................
LSS_cpiAsrtNonEscMajor
Description
The raised alarm LSS_cpiAsrtNonEscMajor indicates the value of the VS.asrtNonESC-
Major measurement monitored by the Major Non-Escalating Asserts CPI exceeded a
threshold in the last 15 minute interval.
levels of severity, in this case major, to provide guidance to Alcatel-Lucent Customer
Notes:
Default severity
Severity Details
Root Cause
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAsrtNonEscMajor
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
the threshold.
...................................................................................................................................................................................................
address them.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
mate.
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAsrtNonEscMinor
....................................................................................................................................................................................................................................
LSS_cpiAsrtNonEscMinor
Description
The raised alarm LSS_cpiAsrtNonEscMinor indicates the value of the VS.asrtNonESC-
Minor measurement monitored by the Minor Non-Escalating Asserts CPI exceeded a
levels of severity, in this case minor, to provide guidance to Alcatel-Lucent Customer
Notes:
Default severity
Severity Details
Root Cause
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAsrtNonEscMinor
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
the threshold.
...................................................................................................................................................................................................
address them.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
mate.
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAudErrCount
....................................................................................................................................................................................................................................
LSS_cpiAudErrCount
Description
The raised alarm LSS_cpiAudErrCount indicates the value of the VS.audErrCount
measurement monitored by the Audit Errors CPI exceeded a threshold in the last 15
minute interval. Audits run at low priority to recover lost or stuck resources. Audits
generate error reports describing any problems they find. The VS.audErrCnt measurement
reports the number of individual errors found by audits during the interval.
Notes:
Default severity
Severity Details
Root Cause
Varies depending on which audits are detecting errors. This alarm is based on the total
number of audit errors found during the interval. It is possible that all of the errors were
found by a single audit. It is also possible that many audits each found errors.

...................................................................................................................................................................................................
1 Although audits take recovery for each error they find, use the Maintenance Interface to
examine the set of audit errors reported. If this alarm recurs or is ongoing due to the same
set of audits, contact Alcatel-Lucent Customer Support. If this alarm is new and coincides
with the introduction of a software update, contact Alcatel-Lucent Customer Support
immediately.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAudErrCount
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 This alarm clears automatically if the rate of audit detected errors drops below the
threshold.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAudManAct
....................................................................................................................................................................................................................................
LSS_cpiAudManAct
Description
The raised alarm, LSS_cpiAudManAct, indicates the value of the VS.audManAct
measurement monitored by the Audit Errors Requiring Manual Action CPI exceeded a
threshold in the last 15 minute interval. Audits run at low priority to recover lost or stuck
resources. Audits generate error reports describing any problems they find.. The
VS.audManAct measurement reports the number of individual errors found by audits
during the interval that require manual action for recovery.
Notes:
Default severity
Severity Details
Root Cause
Varies depending on which audits are detecting errors. This alarm is based on the total
number of audit errors requiring manual action found during the interval. It is possible
that all of the errors were found by a single audit. It is also possible that many audits each
found errors.

...................................................................................................................................................................................................
1 Using the Maintenance Interface, examine the set of audit errors reported and address
them. Audit error reports requiring manual action should specify the actions needed to
perform recovery. If this alarm is new and coincides with the introduction of a software
update, contact Alcatel-Lucent Customer Support immediately.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAudManAct
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 This alarm clears automatically if the rate of audit detected errors requiring manual action
drops below the threshold. However, this will not happen until the required manual
recovery steps have been taken.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAudNewEvent
....................................................................................................................................................................................................................................
LSS_cpiAudNewEvent
Description
The raised alarm LSS_cpiAudNewEvent indicates the value of the VS.audNewEvent
measurement monitored by the Audit Initiated Events CPI exceeded a threshold in the last
15 minute interval. Audits run at low priority to recover lost or stuck resources. Audits
generate error reports describing any problems they find..The VS.audNewEvent
measurement reports the number of times during the interval that an audit that ran without
being part of an escalated recovery and found at least one error.
Notes:
Default severity
Severity Details
Root Cause
Routine or manually requested audits are finding errors. This alarm is based on the total
number of times audits ran and found errors rather than the number of errors found. It is
possible that each audit invocation counted only found a single error. It is also possible
that any one invocation found many errors.

...................................................................................................................................................................................................
1 Although audits take recovery for each error they find, use the Maintenance Interface to
examine the set of audit errors reported. If this alarm recurs or is ongoing due to the same
set of audits, contact Alcatel-Lucent Customer Support. If this alarm is new and coincides
with the introduction of a software update, contact Alcatel-Lucent Customer Support
immediately.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiAudNewEvent
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
2 This alarm clears automatically if the rate of audit invocations that detect errors drops
below the threshold.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiExceptionService
....................................................................................................................................................................................................................................
LSS_cpiExceptionService
Description
The raised alarm LSS_cpiExceptionService indicates the value of the VS.exceptionSer-
vice measurement monitored by the Service Exceptions CPI exceeded a threshold in the
An exception is when a resource (i.e., process) or one of its tasks (i.e., threads) performs
an illegal operation (e.g., accessing an invalid memory address). The service's execution
is halted at the point of the operation. If the fault has occurred in a task that can be
recovered by a task restart, that is attempted. Otherwise, the service itself re-initializes
which results in a switch over. An excessive number of task restarts will also escalate to a
service re-initialization.
Notes:
Default severity
Severity Details
Root Cause
Software within the service member has performed an illegal operation such as accessing
an invalid memory address

...................................................................................................................................................................................................
1 This alarm clears automatically if the rate of exceptions drops below the threshold.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiExceptionService
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
address them.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
6 If the PM counts indicates degradation of service and a switch-over has not already
occurred, switch the service to its redundant mate.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
8 If the situation persists after two or more switch-overs of the pair within the service, then
attempt to duplex fail the service.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiFileSysUsage
....................................................................................................................................................................................................................................
LSS_cpiFileSysUsage
Description
The raised alarm LSS_cpiFileSysUsage indicates the value of resource usage count
VS.fileSysUsage monitored by the File System Usage CPI exceeded a threshold in the
last 5-minute interval.
Notes:
Default severity
WARNING
Severity Details
Warning Alarm: VS.fileSysUsage > 90%
Root Cause
Disk space of the file system is occupied by data files and the file system usage reaches
the threshold.

...................................................................................................................................................................................................
1 Remove outdated and obsolete files to free the file system space.
...................................................................................................................................................................................................
2 Move the important data files to other disks to free the file system space.
...................................................................................................................................................................................................
3 When CPI alarm LSS_cpiFileSysUsage is fired for CDR host, don't remove CDR record
files (under /app1/data0/cdrdata) and PCMD record files (under /app1/data0/pcmddata).
Furthermore, double check timestamp of CDR records files under
/app1/data0/cdrdata/app2/charging/stream1/primary. If many files are older than two
PULL/PUSH intervals, then there might be CDR records file transfer issue, which should
be fixed firstly. For non-CDR record or non-PCMD record files, follow step 1 or step 2.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiMemAllocFail
....................................................................................................................................................................................................................................
LSS_cpiMemAllocFail
Description
The raised alarm, LSS_cpiMemAllocFail, indicates the value of the VS.memAllocFail
measurement monitored by the failed memory allocation attempts CPI exceeded a
Notes:
Default severity
Severity Details
Root Cause
Either the service is running over capacity or has leaked memory.

...................................................................................................................................................................................................
1 Investigate the amount of load being handled by this service and take steps to reduce it if
it is excessive. Otherwise contact Alcatel-Lucent Customer Support. If this alarm
coincides with the introduction of a software update, contact Alcatel-Lucent Customer
Support immediately.
...................................................................................................................................................................................................
2 This alarm clears automatically if the rate of memory allocation failures drops below the
threshold.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiReinitServiceSelf
....................................................................................................................................................................................................................................
LSS_cpiReinitServiceSelf
Description
The raised alarm LSS_cpiReinitServiceSelf indicates the value of the VS.reinitServiceS-
elf measurement monitored by the Automatic Service Re-initialization CPI exceeded a
Notes:
Default severity
Severity Details
Root Cause
The service member has escalated to an initialization to recover from faults

...................................................................................................................................................................................................
1 This alarm clears automatically if the rate of re-initializations drops below the threshold.
...................................................................................................................................................................................................
2 Check that a switch over has successfully occurred.

...................................................................................................................................................................................................
address them. As this is likely the result of recovery escalation, one or more of these
alarms may also be raised: LSS_cpiAsrtEsc, LSS_cpiExceptionService,
LSS_cpiRestartTask
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpiReinitServiceSelf
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
original active host for the service if that has not already occurred.
...................................................................................................................................................................................................
7 If the situation persists after two or more switch-overs of the pair within the service, then
attempt to duplex fail the service.
...................................................................................................................................................................................................
8 Attempt to power down the card providing the service and then restore it. If the problem
clears, this suggests faulty hardware.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_cpuOverload
....................................................................................................................................................................................................................................
LSS_cpuOverload
Description
This alarm indicates that the CPU utilization on a service has exceeded the threshold. The
overload could be caused by one or more of the following reasons: base overload,
per-service quota restriction overload or thread level CPU overload. The "Additional
Info" field of the alarm report will list the contributing causes. When thread level CPU
overload level changes, a corresponding profile report is also generated.
Default severity
Root Cause
Call traffic is too high with the current hardware/software configuration
Some task/process uses CPU resource improperly, for example tight loop.

...................................................................................................................................................................................................
1 Verify that no running debug or testing tool is running that uses a lot of CPU.
...................................................................................................................................................................................................
2 If CPU utilization regularly exceeds thresholds, investigate how the call traffic load can
be reduced:
Reengineer so less traffic is directed to this office or card.
If CPU utilization regularly exceeds thresholds, investigate how to re-engineer the
system so less traffic is directed to this service. If the problem persists, contact the
Alcatel-Lucent customer support team for further investigation.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_databaseConnectionLost
....................................................................................................................................................................................................................................
LSS_databaseConnectionLost
Description
This alarm can be displayed during the initiation of CNFG server (startFS or startCNFG),
when the host_manager fails to connect to the database.
If this alarm is fired from UMTS CDR host or IMS CDR host, it means that UMTS CDR
host or IMS CDR host fails to initialize database and loses connection with DB.
Default severity
CRITICAL, MAJOR
Root Cause
The database or wimdb is not running properly
If this alarm is fired from UMTS CDR host or IMS CDR host, it is caused by connection
lost between database and CDR. CDR fails to initialize database.

...................................................................................................................................................................................................
1 Stop the database and restart the database using the following commands:
stopFS
sudo RCCmachoffine -u
sudo RCCmachonline
startFS
...................................................................................................................................................................................................
2 If this alarm is fired from UMTS CDR host or IMS CDR host and not cleared, contact
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_databaseReplicationLinkDown
....................................................................................................................................................................................................................................
LSS_databaseReplicationLinkDown
Description
This alarm displays when a database replication link is down.
Default severity
MINOR
Root Cause
Internal errors in DataBlitz replication servers.

...................................................................................................................................................................................................
1 The host on one end of the bad link should be brought gracefully offline and online. Any
active services on the blade should be switched to the mate host prior to bring the host
offline. When the host is back online check replications links using "lss login, type dbcli
-R".
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_databaseSizeExhausted
....................................................................................................................................................................................................................................
LSS_databaseSizeExhausted
Description
This alarm is raised when a database approaches full capacity.
Default severity
Root Cause
A warning alarm is generated when an individual DataBlitz Database approaches full
capacity. The severity of the alarm is dictated by how close the database is to reaching
capacity. A warning alarm generates when a database is at 84% capacity, a minor alarm at
92% capacity, and a major alarm at 96% capacity.

...................................................................................................................................................................................................
1 If the alarm is a warning (84% full), the system impact on the specified database reaching
capacity should be investigated. In some instances, a database at 84% capacity is
acceptable. Contact Alcatel-Lucent Customer Support for additional details.
...................................................................................................................................................................................................
2 If the alarm becomes Major (96% full), field support should be contacted. In most cases,
steps to reduce the size of the database should be implemented. Alcatel-Lucent Customer
Support should be contacted to assist in the investigation to reduce the size of the
impacted database.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_dbHighCpuUtilization
....................................................................................................................................................................................................................................
LSS_dbHighCpuUtilization
Description
This alarm indicates very high CPU time usage by a database system process.
Default severity
MAJOR
Root Cause
This alarm is triggered when a specific database system process uses more than 80% of
the system CPU time over a 3 minute period.

...................................................................................................................................................................................................
1 The host and pid of the process are printed in the alarm. Monitor CPU usage of this pid
and contact Alcatel-Lucent Customer Support. This condition can generally be cleared by
stopping and then starting RCC VM on the affected host.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_dbOffline
....................................................................................................................................................................................................................................
LSS_dbOffline
Description
This alarm displays when the database is offline.
Default severity
CRITICAL, MINOR
Root Cause
The alarm is generated when DataBlitz server is shutting down, or when the dataBlitz
cleanup server detects datablitz server death.

...................................................................................................................................................................................................
1 Normally the alarm clears automatically when Datablitz servers recover; If this alarm
does not clear, contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_dbStatusUnexpected
....................................................................................................................................................................................................................................
LSS_dbStatusUnexpected
Description
This alarm displays when the DataBlitz database cannot be accessed.
Default severity
CRITICAL
Root Cause
The alarm is generated when DataBlitz database(s) is not accessible due to other
problems in the machine.

...................................................................................................................................................................................................
1 Normally the alarm clears automatically when Datablitz database(s) becomes accessible.
If this alarm does not clear, contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_degradedResource
....................................................................................................................................................................................................................................
LSS_degradedResource
Description
A Critical Application Resource (CAR) has reached a degraded condition that indicates
some aspect of the switch is not performing as expected. The affected service member is
indicated in the alarm by the PoolType, PoolId, and PoolMemberId.
Default severity
MAJOR
Root Cause
The root cause depends on the specific resource that is degraded. Causes are described in
the associated alarm documentation for each resource (see below).

...................................................................................................................................................................................................
1 From the alarm, determine the service member that is degraded, as shown by the
PoolType, PoolId, and PoolMemberId.
...................................................................................................................................................................................................
2 On the MI GUI, go to the Management Interface window. Under the appropriate shelf,
click Service Members. In the Service Members window, right click the appropriate
service member, and choose Display Degraded Critical Resources. A pop-up window will
display the "Resource name" for each resource that is causing the service member to be
degraded.
...................................................................................................................................................................................................
3 The following table lists the resources that exist for each service type, and the associated
alarm for each that has one. In most cases, when a resource is degraded, the associated
alarm is firing. The associated alarm documentation can be viewed by clicking the link in
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
the appropriate table below. If the associated alarm is firing, refer to its documentation to
resolve the problem. If the associated alarm is not firing, or no associated alarm is
defined, contact Alcatel-Lucent Customer Support.
Access AMMS BoolGroup accessMan- 50% Represents

manager agerCxnLost an AMMS
connections Device
Server's
connections
to the Access
Manager.
The CAR is
off normal
when at least
50% of all
the
connections,
i.e., at least 1
of 2, is
broken.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
AMMS- AMMS, BoolGroup serviceCom- 1% Represents:

H.248 tunnel H.248, IWF mCxnLost a) an active
connections AMMS
service
member's
connections
to all active
H.248
service
members, or
b) an active
H.248
service
member's
connections
to all active
AMMS
service
members.
The CAR
members are
registered on
the active
AMMSs or
the active
H.248s. For
IWF, no
members are
registered.
Each CAR
member
represents
one
AMMS-
H.248 tunnel
connection.
The CAR
member is
off normal
when its
AMMS-
H.248 tunnel
connection is
down.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
BIST all diskless, BoolSingle cardError N/A Represents

CDR, VLR whether a
Built-In Self
Test (BIST)
failure was
detected
during
initialization
of the card
that the
service
member. is
running on. It
is off normal
when there
was an error.
BSC SS7 BoolGroup baseStation- 1% Represents
Controlle- the BSC
rOOS status. Each
CAR
member
represents
one BSC.
The member
number is the
BSC index.
The CAR
members are
registered
only on the
active SS7s.
If the BSC
cannot come
into the IN
SERVICE
state, then
this CAR
member will
report off
normal.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
BSSAP SS7 BoolGroup ss7CICsChannelsOOS

1% Represents
channels the BSSAP
channel
group status.
Each CAR
member
represents
one BSSAP
channel
group. The
member
number is the
CIC trunk
group
number. The
CAR
members are
registered
only on the
active SS7s.
If the channel
OOS rate in
this channel
group
reaches 80%
(default
value), then
this CAR
member will
report off
normal.
When this
channel
group's OOS
rate goes
below 60%
(default
value), it will
report the
CAR
member as
normal.
These
thresholds
are channel
group
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary parameters4-89
9YZ-05481-0005-RKZZA Release Use pursuant to applicable agreements that can be
WM7.0.0
Issue 1 August 2013 changed on
the FS GUI.
....................................................................................................................................................................................................................................
Call control H.248, IWF BoolGroup callControl- 1% Each CAR

blocks BlockDeple- member
tion represents the
Call Control
Blocks for
one gateway.
The member
number is the
gateway ID.
(For IWF, the
IWF itself is
registered as
a member.) A
member is
off normal if
the number
of free Call
Control
Blocks for
that gateway
drops below
a threshold.
CDR FTP CDR BoolSingle ftpDown N/A Represents
push FTP transfer
of CDR
records
between
CDR and
BMD. The
CAR is off
normal when
CDR data
transfer
between
CDR and
BMD failed
with FTP
method.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
CDR host Call server BoolSingle tcpCommuni- N/A Represents

connection cationFailure the CDR host
connection
with the call
server. The
CAR is off
normal when
the
connection is
down.
CDR logger CDR BoolSingle cdrLogger- N/A Represents
connection to MateTcp- the CDR
mate Down logger
connection
with the mate
CDR logger.
The CAR is
off normal
when the
connection is
broken.
CDR Call server BoolSingle N/A N/A Represents
message CDR
queue message
queue, which
is on Call
server and
stores the
CDR
messages to
avoid CDR
record lost
when CS and
CDR
connection
broken. The
CAR is off
normal when
CDR
message
queue usage
reaches 50%.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
CDR rcvr CDR BoolSingle cdrReceiver- N/A Represents

connection to MateTcp- the CDR
mate Down receiver
connection
with the mate
CDR
receiver. The
CAR is off
normal when
the
connection is
broken.
CDR rcvr to CDR BoolSingle cdrLogger- N/A Represents
logger ReceiverTcp- the CDR
connection Down logger
connection
with the local
CDR
receiver. The
CAR is off
normal when
the
connection is
broken.
CDR SSH CDR BoolSingle scpDown N/A Represents
push SSH transfer
of CDR
records
between
CDR and
BMD. The
CAR is off
normal when
CDR data
transfer
between
CDR and
BMD failed
with SSH
method.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Channel NGSS TankGroup N/A 1% Represents

groups call blocks,
which are
members of a
channel
group. The
member
number is the
channel
group ID.
These are
defined on
the FSGUI
channel
group screen,
except for
URMF,
where a
virtual
channel
group is
assigned with
a pre-defined
number when
the port is
defined on
the SIPIA
port
configuration
screen. Each
channel
group is a
gas tank in
the CAR. A
gas tank is
off normal if
its usage is
98% or more.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Communica- MIF BoolSingle mmeInternal- N/A Represents

tion to MAF Communica- the MME
tionFailure internal
communica-
tion status on
MIF. This
CAR is off
normal when
MIF cannot
communicate
with MAF.
Communica- MAF BoolSingle mmeInternal- N/A Represents
tion to MIF Communica- the MME
tionFailure internal
communica-
tion status on
MAF. This
CAR is off
normal when
MAF cannot
communicate
with MIF.
Configura- all diskless BoolSingle nodeConfig- N/A Represents
tion Failure whether the
configuration
occurred
properly and
the
configuration
data was
received
properly and
is still in
agreement
between
active and
standby, or
active call
servers. It is
off normal
when any of
these
conditions
are not met.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
CPU all diskless BoolSingle cpuOverload N/A Represents

overload critical CPU
overload. It is
off normal
when the
service
member is in
critical CPU
overload,
which by
default is
95%.
CS VLR BoolGroup vLRHostIP- 1% Each CAR
connections connection- member
OOS represents a
connection
from the
VLR to a call
server. The
member
number is the
following
fields packed
together,
identifying
the CS: node
(16 bits),
shelf (8 bits),
host (2 bits),
slot (6 bits).
The member
is off normal
when the link
is down.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
CxnMgr MAF BoolSingle softwareAllo- N/A Represents

connections cat- preallocated
edResourceOverload resource for
Connection
Manager
software
module on
MAF. Each
MAF has its
own
Connection
Manager
resource
allocation.
This CAR is
off normal if
the
Connection
Manager
resource
usage is
above its
critical
overload
threshold.
Datablitz VLR BoolSingle N/A N/A Represents
attach the Datablitz
attach status.
It is off
normal when
VLR fails to
attach to
Datablitz.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
DPC SSN SS7 BoolGroup dpcSSNpro- 1% Represents

hibited the DPC SSN
status. Each
CAR
member
represents
one
DPC+SSN
association
status. The
member
number is
SSN (8 bits)
followed by
DPC (24
bits). The
CAR
members are
registered
only on the
active
NM(Network
Manage-
ment) SS7
Card. If one
DPC SSN
association is
in the
PROHIB-
ITED state
then this
CAR
member will
report off
normal.
When this
DPC SSN
association
comes into
the
ALLOWED
state, the
CAR
member will
report
normal.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
File system CDR BoolSingle diskSpaceEx- N/A Represents

usage hausted the usage of
disk space on
a CDR,
which stores
CDR records.
If the disk
space usage
reaches
Major
threshold
(default is
85%), the
CAR is off
normal.
Host ID VLR BoolSingle N/A N/A Represents
the VLR host
ID status. It
is off normal
when the
VLR host
doesn't have
a valid host
ID.
IMSIMapDB MIF BoolSingle softwareAllo- N/A Represents
cat- preallocated
edResourceOverload memory for
IMSIMapDB
software
module on
MIF. This
CAR is off
normal if the
IMSIMapDB
resource
usage is
above its
critical
overload
threshold.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
IN host Call server BoolSingle N/A N/A Represents

connection the IN host
connection
with the call
server. The
CAR is off
normal when
the
connection is
down.
Internal all MME BoolSingle mmeInternal- N/A Represents
MME diskless Communica- all of an
communica- tionFailure MME
tion diskless
service
member's
internal links
to other
MME
diskless
service
members.
The CAR is
off normal
when all
internal
MME
communica-
tions are
down.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Internal links all diskless BoolGroup logicalLink- 1% Represents a

Down diskless
service
member's
internal links
to other
diskless
service
members.
Each member
represents a
link between
this diskless
service
member and
another
diskless
service
member, and
the member
number is the
IP address of
the other
diskless
service
member. The
member is
off normal
when the link
is down.
IP address VLR BoolSingle N/A N/A Represents
the VLR IP
address
status. It is
off normal
when VLR
host doesn't
have a valid
IP address.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
ISUP DPC SS7 BoolGroup ss7CICsChannelsOOS

1% Represents
CICs INS the ISUP
CICs' status
of every
ISUP DPC.
Every CAR
member
represents
one ISUP
DPC's CIC
status. The
member
number is the
destination
ID. An ISUP
DPC might
own multiple
ISUP channel
groups, on
which an
alarm is fired
if the number
of bad CICs
(OOS,
blocked
status etc.,
not in
INS/GREEN
or
Equipped-
NIS/BLUE)
is greater
than the
configured
threshold on
the ISUP
channel
group. A
CAR
member is
off normal
only if all its
associated
channel
groups are
firing a major
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary alarm. 4-101
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
ISUP DPC SS7 BoolGroup N/A 1% Represents

congestion the ISUP
DPCs'
congestion
status. Every
CAR
member
represents
one ISUP
DPC's status.
The member
number is the
destination
ID. When
any
congestion
occurs on
this DPC,
like remote
congestion
(represented
as ISUP
parameter
ACL in the
ISUP release
message sent
by the
remote),
DPC
congestion,
or link
congestion,
this CAR
member will
report off
normal.
L4PPL State Call server BoolSingle l4PPLStateMachineOverload
N/A Represents
Machine L4 PPL state
machine
usage. The
CAR is off
normal if the
usage is 98%
or more.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
L4RTR Call server BoolSingle l4RTRHandleOverload

N/A Represents
handle L4 RTR
handle usage.
The CAR is
off normal if
the usage is
98% or more.
L5SSL Call server BoolSingle l5SSLInstanceOverload
N/A Represents
Instance L5 SSL state
machine
usage. The
CAR is off
normal if the
usage is 98%
or more.
Local SSN VLR BoolGroup N/A 1% This CAR
has two
members.
One member
represents the
MSC
subsystem
status, and its
member
number is 8;
the other
member
represents the
VLR
subsystem
status, and its
member
number is 7.
A member is
off normal
when the
VLR host
cannot find
the
correspond-
ing SSN
provisioned.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
M3UA SS7 BoolGroup m3uaConnectionDown

1% Represents
connections the M3UA
connection
status. Each
CAR
member
represents
status of one
M3UA
connection,
that is,
connection
between one
ASP and one
SG. The
member
number is
ASP (16 bits)
followed by
SG (16 bits).
If the ASP of
one M3UA
connection
cannot come
into ACTIVE
state or
management
blocking
state, then
this CAR
member will
report off
normal.
MCC Call server BoolSingle mccChan- N/A Represents
Channel nelOverload MCC
channel state
machine
usage. The
CAR is off
normal if the
usage is 98%
or more.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
MCC Call server BoolSingle mccConfer- N/A Represents

Conference enceOverload MCC
conference
state machine
usage. The
CAR is off
normal if the
usage is 98%
or more.
Memory all diskless BoolSingle memory- N/A Represents
overload Overload critical
memory
overload. It is
off normal
when the
service
member is in
critical
memory
overload,
which by
default is
90%.
Message H.248, IWF BoolSingle h248MessageBufferDepletion
N/A Represents
buffers the pool of
Message
Buffers. This
pool is
shared across
all gateways.
The CAR is
off normal if
the number
of free
Message
Buffers drops
below a
threshold.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Multi homed H.248, IWF BoolGroup gatewayUn- 49% Each member

GW registered represents
registrations one multi
homed
gateway. The
member
number is the
gateway ID.
Gateways
which
connect via
multi homed
SCTP are in
this group.
(For IWF, no
members are
registered.) A
member is
off normal if
its gateway is
not
registered.
This will
detect either
the inability
of the device
server to
accept
connections
or a
networking
issue.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Non CS H.248, IWF BoolGroup nonCsAd- 1% Each CAR

addressable drChan- member
channels nelDepletion represents the
non-Call
Server
Addressable
Channels for
one gateway.
The member
number is the
gateway ID.
(For IWF, the
IWF itself is
registered as
a member.) A
member is
off normal if
the number
of non-Call
Server
Addressable
Channels for
that gateway
drops below
a threshold.
PCMD FTP CDR BoolSingle ftpDown N/A Represents
push FTP transfer
of PCMD
data between
CDR and
northbound
interface.
The CAR is
off normal
when PCMD
data transfer
between
CDR and
northbound
interface
failed with
FTP method.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
PCMD SSH CDR BoolSingle scpDown N/A Represents

push SSH transfer
of PCMD
data between
CDR and
northbound
interface.
The CAR is
off normal
when PCMD
data transfer
between
CDR and
northbound
interface
failed with
SSH method.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Peer AMMS AMMS BoolGroup serviceCom- 1% Represents

connections mCxnLost an active
AMMS
service
member's
connections
to all its
active peer
AMMSs. The
CAR
members are
registered
only on the
active
AMMSs.
Each CAR
member
represents
one peer
AMMS
connection.
The CAR
member is
off normal
when its peer
AMMS
connection is
down.
PMC SS7 BoolSingle pmcDown N/A Represents
the SS7
PMC. It is
off normal
when the
PMC is
down.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
PMC SS7 TankGroup N/A 1% Represents

transmission the queues
queue for MSUs to
be sent to the
PMC. Each
member
represents the
queue for one
SS7 link. The
member
number is the
SS7 link ID.
The member
is off normal
when the
queue is at
least 98%
full.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
RANAP SS7 BoolGroup ss7CICsChannelsOOS

1% Represents
channels the RANAP
channel
group status.
Each CAR
member
represents
one RANAP
channel
group. The
member
number is the
CIC trunk
group
number. The
CAR
members are
registered
only on the
active SS7s.
If the channel
OOS rate in
this channel
group
reaches 80%
(default
value), then
this CAR
member will
report off
normal.
When this
channel
group's OOS
rate goes
below 60%
(default
value), it will
report the
CAR
member as
normal.
These
thresholds
are channel
group
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary parameters 4-111
9YZ-05481-0005-RKZZA Release Use pursuant to applicable agreements that can be
WM7.0.0
Issue 1 August 2013 changed on
the FS GUI.
....................................................................................................................................................................................................................................
Rcvr memory CDR BoolSingle N/A N/A Represents

overload CDR receiver
memory
usage. The
CAR is off
normal when
CDR receiver
memory
usage reaches
threshold
1800*1024KB.
Rcvr to CDR BoolSingle cdrPCMDRe- N/A Represents
PCMD ceiverTcp- the PCMD
logger Down logger
connection connection
with the local
CDR
receiver. The
CAR is off
normal when
the
connection is
broken.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
RNC SS7 BoolGroup radioNet- 1% Represents

workControl- the RNC
lerOOS status. Each
CAR
member
represents
one RNC.
The member
number is the
controller
index. The
CAR
members are
registered
only on the
active SS7s.
If the RNC
cannot come
into the IN
SERVICE
state, then
this CAR
member will
report off
normal.
S11 links MIF BoolGroup mmeExter- 100% Represents
nalLinkDown S11 link
status on
MME. Each
CAR
member
represents
one S11 link.
The member
number is the
link index.
The CAR
member is
off normal if
the link is
down.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
S13 links MIF BoolGroup mmeExter- 100% Represents

nalLinkDown S13 link
status on
MME. Each
CAR
member
represents
one S13 link.
The member
number is the
link index.
The CAR
member is
off normal if
the link is
down.
S1mme links MIF TankSingle mmeExter- 100% Represents
nalLinkDown the status of
all S1mme
links on
MME. The
CAR is off
normal if all
of the links
are down.
S6a links MIF BoolGroup mmeExter- 100% Represents
nalLinkDown S6a link
status on
MME. Each
CAR
member
represents
one S6a link.
The member
number is the
link index.
The CAR
member is
off normal if
the link is
down.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
SCCP SS7 BoolGroup N/A 1% Represents

connections the SCCP
connection
usage status.
Each CAR
member
represents the
SCCP
connection
usage status
for one stack.
The member
number is the
stack ID. The
CAR
members are
registered
only on the
active SS7s.
If the SCCP
connection
usage of a
stack reaches
threshold
98%, then
this CAR
member will
report off
normal.
When the
SCCP
connection
usage goes
below 95%,
the CAR
member will
report
normal.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
SCTP buffer SS7 BoolSingle sctpBuffer- N/A Represents

Exhaustion the SCTP
sending
buffer usage
status. When
SCTP
sending
buffer usage
exceeds 60%,
the CAR will
report off
normal.
When the
SCTP
association is
reset or the
SCTP
sending
buffer usage
comes down
from above
60% to
below 60%,
the CAR will
report
normal.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
SCTP SS7 BoolSingle sctpConges- N/A Represents

congestion tion the SCTP
association
congestion
status. The
CAR will
report off
normal under
following
conditions: 1)
the SCTP
acknowledg-
ment delay
exceeded 3
seconds or 2)
the data size
to be sent
exceeded the
peer's
congestion
control
window
equal to or
more than 10
times within
5 minutes.
The CAR
will report
normal under
following
conditions: 1)
there was no
SCTP
acknowledg-
ment delay
that exceeded
3 seconds in
the last 5
minutes and
2) the data
size to be
sent
exceeded the
peer's
congestion
control
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary window less 4-117
9YZ-05481-0005-RKZZA Release Use pursuant to applicable agreements than 10 times
WM7.0.0
Issue 1 August 2013 in last 5
minutes.
....................................................................................................................................................................................................................................
Service call NGSS BoolSingle srvCallLe- N/A Represents

legs gOverload service call
data. The
CAR is off
normal if the
usage is 98%
or more.
SessDist MAF BoolSingle softwareAllo- N/A Represents
buffer cat- preallocated
edResourceOverload buffer for
Session
Distributor
software
module on
MAF. Each
MAF has its
own Session
Distributor
buffer
allocation.
This CAR is
off normal if
the Session
Distributor
buffer usage
is above its
critical
overload
threshold.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Single H.248, IWF BoolGroup gatewayUn- 49% Each member

homed GW registered represents
registrations one single
homed
gateway. The
member
number is the
gateway ID.
Gateways
which
connect via
TCP or single
homed SCTP
are
considered
single
homed. (For
IWF, no
members are
registered.) A
member is
off normal if
its gateway is
not
registered.
This will
detect either
the inability
of the device
server to
accept
connections
or a
networking
issue.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
SMLC SS7 BoolGroup N/A 1% Represents

the SMLC
status. Each
CAR
member
represents
one SMLC.
The member
number is the
controller
index. The
CAR
members are
registered
only on the
active SS7s.
If the SMLC
cannot come
into the IN
SERVICE
state, then
this CAR
member will
report off
normal.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
SS7 VLR BoolGroup vLRHostIP- 1% Each member

connections connection- represents a
for network OOS connection
from the
VLR to an
SS7 for
network
traffic. The
member
number is the
following
fields packed
together,
identifying
the SS7:
node (16
bits), shelf (8
bits), host (2
bits), slot (6
bits). If the
SS7 is not
actually
being used as
a network
SS7, the link
will not be
used, but it
still exists.
The member
is off normal
when the link
is down.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
SS7 VLR BoolGroup vLRHostIP- 1% Each member

connections connection- represents a
for wireless OOS connection
from the
VLR to an
SS7 for
wireless
traffic. The
member
number is the
following
fields packed
together,
identifying
the SS7:
node (16
bits), shelf (8
bits), host (2
bits), slot (6
bits). If the
SS7 is not
actually
being used as
a wireless
SS7, the link
will not be
used, but it
still exists.
The member
is off normal
when the link
is down.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
SS7 link SS7 BoolGroup N/A 1% Each member

congestion represents the
congestion
status of an
SS7 link. The
member
number is the
SS7 link ID.
It is off
normal if the
SS7 PMC
has reported
Receive Not
Ready, or a
nonzero
congestion
level.
SS7 links SS7 BoolGroup ss7linkDown 1% Represents
SS7 links.
Each member
represents
one SS7 link.
The member
number is the
SS7 link ID.
The member
is off normal
when the link
is not service.
However,
links that are
inhibited or
manually out
of service are
ignored; they
are not
represented
as CAR
members.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
Transaction H.248, IWF BoolSingle callControl- N/A Represents

control BlockDeple- the pool of
blocks tion transaction
control
blocks
(TCBs),
which are
used to
manage
transactions
with the
gateways.
This pool is
shared across
all gateways.
There is one
pool of
Transaction
Control
Blocks
shared across
all gateways.
The CAR is
off normal if
the number
of free TCBs
drops below
a threshold.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
VLR host Call server BoolGroup vLRHostIP- 1% Each member

connection connection- represents
OOS one VLR
host
connection
with this CS.
The member
number is the
VLR host ID.
Any
lost/error/
timeout/no
response for
this VLR
host
connection
with the CS
will cause
this CAR
member to be
off normal.
VLR table MAF BoolSingle softwareAllo- N/A Represents
cat- preallocated
edResourceOverload memory for
VLR table on
MAF. Each
MAF has its
own VLR
table
resource
allocation.
This CAR is
off normal if
the VLR
table usage is
above its
critical
overload
threshold.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_degrow
....................................................................................................................................................................................................................................
LSS_degrow
Description
When performing SIM degrow procedure, failures that occur will result in the generation
of DEGROW alarm.
Default severity
MAJOR
Root Cause
Any failure related to DEGROW activities generates a DEGROW alarm.

...................................................................................................................................................................................................
1 Based on the type of failure encountered, recovery actions may vary. If the DEGROW
alarm is generated, contact Alcatel-Lucent Customer Support. Once the failure is
corrected, a resumption of the SIM procedures will automatically clear the alarm.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_diskGoingDown
....................................................................................................................................................................................................................................
LSS_diskGoingDown
Description
This alarm indicates that the Smart Monitor Tool Set (smartmontools) has determined that
the Disk Drive for this LCP Host is going down, and is predicting failure in the next 24
hours.
Default severity
Root Cause
One of the Vender specific Disk Drive Attributes has exceeded a critical threshold.

...................................................................................................................................................................................................
1 Backup Recovery actions for this LCP Host should be immediately executed.
...................................................................................................................................................................................................
2 Contact Alcatel-Lucent Customer Support immediately

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_diskSector
....................................................................................................................................................................................................................................
LSS_diskSector
Description
This alarm indicates that the Smart Monitor Tool Set (smartmontools) has determined that
the Disk Drive for this LCP Host has a bad sector.
Default severity
MAJOR
Root Cause
One or more sectors on the specified Disk Drive is corrupted.

...................................................................................................................................................................................................
1 The card reporting the problem should be replaced, following the card replacement
procedures.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_dnsThreshold
....................................................................................................................................................................................................................................
LSS_dnsThreshold
Description
This alarm indicates returned number of IP addresses in DNS query of diameter
fully-qualified domain name (FQDN) exceeds its number threshold.
Default severity
WARNING
Root Cause
If DNS returns more than 64 IPs for one FQDN, warning alarm for this FQDN is
generated.
If more than 256 IPs returned for all FQDNs, warning alarm for all FQDNs is generated.

...................................................................................................................................................................................................
1 Verify that destination FQDN is correctly provisioned on the GUI

...................................................................................................................................................................................................
2 Verify that FQDN is correctly provisioned on the external DNS server( IP addresses count
should be less than threshold value).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_ethernetError
....................................................................................................................................................................................................................................
LSS_ethernetError
Description
One of the two Ethernet Links on a Service Host has failed.
Default severity
MINOR
Root Cause
A hardware failure has occurred with the Service Host Network Interface Card (NIC), its
cabling, or the IP network.

...................................................................................................................................................................................................
1 Regardless of the cause of the Ethernet Link alarm, integrity software running on the
affected Service Host should automatically initiate a switch to redundant hardware to
ensure that the effects of the failure are minimized. The following recovery actions may,
in fact, be automatically initiated:
Service Host switch, if multiple Ethernet Links are affected
Ethernet Link switch, if a single Active Ethernet Link is affected
None, if the hardware failure affects a Standby Ethernet Link
The reason for the failure needs to be understood and corrected. It is possible that the
Service Host Ethernet Port failed, the cabling that interconnects the Ethernet Port to the
network is cut, the Routers and/or Ethernet Switches that make up the Alcatel-Lucent
SoftSwitch Network failed. Each of these possible reasons needs to be investigated and
discounted or corrected by maintenance personnel. Once corrected, the alarm is cleared.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_ethernetLinkDown
....................................................................................................................................................................................................................................
LSS_ethernetLinkDown
Description
The redundant Ethernet link has gone down on one of the diskless hosts. A link
switchover may have occurred to move communication for that host to the remaining
link, which is now simplex.
Default severity
MINOR
Root Cause
The Ethernet Switch Card (ESC) or the specific ESC port that serves this Ethernet
link on this host has failed or has been disabled. (
Alcatel-Lucent
CP 1800 only)
The chassis backplane has failed. (
Alcatel-Lucent
CP 1800 only)
The Ethernet cable from this specific faceplate port to the external Ethernet router has
failed or has been disconnected. (
Alcatel-Lucent
CP 1000 only)
The external Ethernet router serving this specific faceplate port has failed or has been
disabled. (
Alcatel-Lucent
CP 1000 only)
The Card itself has failed.
The hub, or the specific hub port that serves this Ethernet link on this host has failed
or has been disabled; The chassis backplane has failed; or the blade with the host itself
has failed (
Alcatel-Lucent
5400 LCP only)
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_ethernetLinkDown
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2
1. On Alcatel-Lucent CP 1000:
Verify that the cable from the corresponding faceplate port to the external Ethernet
router is connected and is good. Replace as necessary.
2. On other Alcatel-Lucent Products:
Verify that the ESC corresponding to this link is operational by viewing its status at
MI, and by telnet to the ESC card. Correct or replace ESC as necessary.
3. On Alcatel-Lucent 5400 LCP:
Verify that the hub corresponding to this link is operational by viewing its status at
MI, and by telnet to the hub . Correct or replace hub as necessary.
...................................................................................................................................................................................................
3
Verify that the external Ethernet router is operational. Correct or replace as necessary.
2. On other Alcatel-Lucent Products:
On the ESC verify that the Ethernet port corresponding to the card for this host is
operational. Re-enable port as necessary.
3. On Alcatel-Lucent 5400 LCP:
On the hub verify that the Ethernet port corresponding to the card for this host is
operational. Re-enable port as necessary. Replace the card used for this host using the
...................................................................................................................................................................................................
4
Replace the card used for this host using the appropriate FRU procedure.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_externalConnectivity
....................................................................................................................................................................................................................................
LSS_externalConnectivity
Description
The system detected a problem or a state change to external connectivity.
Default severity
CRITICAL, MAJOR, INFO
Root Cause
A failure or route change has occurred that adversely affects the external IP connectivity.

...................................................................................................................................................................................................
1 For INFO alarm, there is no action needed.

...................................................................................................................................................................................................
2 For MAJOR and CRITICAL alarm, verify the cable connections from both HUB cards to
customer layer 2 switches, check if the cables are plugged properly.
...................................................................................................................................................................................................
3 For MAJOR and CRITIAL alarm, verify the port status on HUB cards, the port connect to
the customer network should be in service.
...................................................................................................................................................................................................
4 For MAJOR and CRITIAL alarm, verify the individual Ethernet port status on the HUB
card for the given host with the alarm.
...................................................................................................................................................................................................
5 For the CRITIAL alarm, verify connectivity to/from each of the IPs listed in the ARP list
from the given host with the alarm.
...................................................................................................................................................................................................
6 Check the next hop reported as failing. For a BFD session verify the router has the
corresponding BFD session configured.
...................................................................................................................................................................................................
7 Contact Alcatel-Lucent Customer Support for the correction procedure if above check
cannot correct it.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_fru
....................................................................................................................................................................................................................................
LSS_fru
Description
When performing SIM fru procedure, failures that occur will result in the generation of
FRU alarm.
Default severity
MAJOR
Root Cause
Any failure related to FRU activities generates an FRU alarm.

...................................................................................................................................................................................................
1 Based on the type of failure encountered, recovery actions may vary. If the FRU alarm is
generated, contact Alcatel-Lucent Customer Support. Once the failure is corrected, a
resumption of the SIM procedures will automatically clear the alarm.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_grow
....................................................................................................................................................................................................................................
LSS_grow
Description
When performing SIM grow procedure, failures that occur will result in the generation of
GROW alarm.
Default severity
MAJOR
Root Cause
Any failure related to GROW activities generates a GROW alarm.

...................................................................................................................................................................................................
1 Based on the type of failure encountered, recovery actions may vary. If the GROW alarm
is generated, contact Alcatel-Lucent Customer Support. Once the failure is corrected, a
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_hostDown
....................................................................................................................................................................................................................................
LSS_hostDown
Description
A Service Host abnormally transitioned to an out-of-service state. (Note, this alarm will
only be generated if the mate Service Host is in-service.)
Default severity
MAJOR
Root Cause
A recurring software bug or hardware fault prevented integrity software from maintaining
an in-service Service Host state. For both causes, integrity software will eventually
escalate to a recovery action to be performed on the Service Host.

...................................................................................................................................................................................................
1 In general, the first few occurrences of the abnormal termination is automatically

recovered by integrity software on the Service Host, in which case no manual action is
necessary. When automatic recovery occurs the alarm clears automatically as well.
However, if the unexpected event causing the abnormal termination occurs at a frequent
enough rate, the Service Host can be left in a permanent Unavailable state. If in this state
the alarm will not be cleared automatically and manual action is necessary to restore the
Service Host. Bringing a Service Host software back to an In-Service state can be
initiated from the MI.
The reason for the abnormal termination needs to be determined and a fix provided.
Debugging output is sent to the MI Log File and core files are typically generated when
these conditions occur. To aid Alcatel-Lucent Customer Support in providing a fix, the
storage of the MI Log File and the collection of any core files at the time the error
occurred should be done and made available. The location of generated core files is
/var/core on the Service host that experienced the abnormal termination.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_memoryOverload
....................................................................................................................................................................................................................................
LSS_memoryOverload
Description
This alarm indicates the memory utilization on a diskless service has exceeded a
threshold or a memory allocation failure has occurred.
The current default thresholds are: Minor - 80, Major - 85, Critical - 90.
Note: for MM-SI AMMS service, the default thresholds are: Minor - 94, Major - 96,
Critical - 98.
Default severity
Root Cause
The cause can be:
Call traffic is too high with the current hardware/software configuration.
Some task manages memory resource improperly, e.g. memory leak.

...................................................................................................................................................................................................
1 If memory usage regularly exceeds thresholds, investigate how the call traffic load can be
reduced.
...................................................................................................................................................................................................
2 If it doesn't clear after step 1, contact Alcatel-Lucent Customer Support to check if there
is memory leak occurring.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_nodeGroupOOS
....................................................................................................................................................................................................................................
LSS_nodeGroupOOS
Description
This Major alarm occurs when a Node Group state enters Redundancy. This Critical
alarm occurs when a Node Group state enters Fault.
Default severity
CRITICAL, MAJOR
Root Cause
This alarm occurs when a Node Group state enters to Redundancy or Fault. The affected
Node Group can be identified in the additional text field of the alarm. The node will
become unavailable when the SIP heartbeat to the destination URI fails. Possible causes
for a SIP heartbeat failure on a node are:
1. The destination URI is out of service and is unable to respond to the SIP heartbeat.
2. An IP network problem occurs where the SIP heartbeat and/or response cannot be
delivered.
3. A local error on the network card (ESC card for CPSB platforms, HUB card for
ATCA platforms) preventing SIP connectivity to the IP network.
4. A provisioning error where invalid IP addresses are provisioned in the DNS.
5. A software error

...................................................................................................................................................................................................
1 The alarm is cleared when the node group state changed to Normal, i.e. all the nodes in
this node group enter In Service(unblocked) state.
...................................................................................................................................................................................................
2 Determine that there are no errors within the IP network. If errors exist, follow the
operating procedures to correct these errors.
...................................................................................................................................................................................................
3 Determine that the Ethernet Switch Card (ESC) is in service. If not, follow the local
operating procedures to restore the ESC to service.
...................................................................................................................................................................................................
4 Determine that the DNS is provisioned with correct IP addresses for the Destination URI.
If not, correctly provision the DNS with the correct IP addresses for the Destination URI.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_nodeOOS
....................................................................................................................................................................................................................................
LSS_nodeOOS
Description
This alarm indicates the state of a Node has changed from in-service to out-of-service.
Default severity
MAJOR
Root Cause
This alarm occurs when a Node state is changed from in-service to out-of-service. The
affected Node can be identified in the additional text field of the alarm. The node will
become unavailable when The SIP heartbeat to the destination URI failed.Possible causes
for a SIP heartbeat failure on a node are:
1. The destination URI is out of service and is unable to respond to the SIP heartbeat.
2. An IP network problem occurs where the SIP heartbeat and/or response cannot be
delivered.
3. A local error on the network card (ESC card for CPSB platforms, HUB card for
ATCA platforms) preventing SIP connectivity to the IP network.
4. A provisioning error where invalid IP addresses are provisioned in the DNS.
5. A software error

...................................................................................................................................................................................................
1 Determine if the destination URI is in service and is able to respond to the SIP heartbeat.
If not, follow the operating procedures to restore the destination URI to service.
...................................................................................................................................................................................................
2 Determine that there are no errors within the IP network. If errors exist, follow the
operating procedures to correct these errors.
...................................................................................................................................................................................................
3 Determine that the Ethernet Switch Card (ESC) is in service. If not, follow the local
operating procedures to restore the ESC to service.
...................................................................................................................................................................................................
4 Determine that the DNS is provisioned with correct IP addresses for the Destination URI.
If not, correctly provision the DNS with the correct IP addresses for the Destination URI.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_numberOfTuplesInUse
....................................................................................................................................................................................................................................
LSS_numberOfTuplesInUse
Description
The raised alarm LSS_numberOfTuplesInUse indicates that the number of tuples
currently in use in a DA (data access) table used to store dynamic database information,
has reached a threshold. The DA table in question is specified in the "Resource". The
threshold is indicated in the "Additional Information".
Notes:
A DA table can have the following thresholds:
Minor Alarm Onset
Minor Alarm Abatement
Major Alarm Onset
Major Alarm Abatement
Critical Alarm Onset
Critical Alarm Abatement
The alarm is raised (or will transition to a higher severity if already raised) if the
number of tuples in use is greater than or equal to the onset threshold for that severity
(specific to that table).
The alarm will transition to a lower severity (or clears if the current severity is minor)
if the number of tuples in use is less than or equal to the abatement threshold for that
severity (specific to that table).
Default severity
Root Cause
Possible causes are:
The office is experiencing greater traffic than it is engineered for.
A software error is preventing the tuples in the table from being idled when they are
no longer in use.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_osSecInfoModificationDetected
....................................................................................................................................................................................................................................
LSS_osSecInfoModificationDetected
Description
This alarm indicates that an unexpected modification on the security information of a host
operating system has been detected by the security audit program.
Default severity
Root Cause
List of root cause:
The file permission has been modified on a file.
The owner or content of a file has been modified.

...................................................................................................................................................................................................
1 Access MI GUI for the detailed information of this security alarm.

...................................................................................................................................................................................................
2 Investigate the problematic file identified in the additionalText string. Correct any errors
found during the investigation the problem. Contact Alcatel-Lucent Customer Support as
needed.
...................................................................................................................................................................................................
3 Once the error has been corrected, clear the alarm from the MI GUI.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_osSecInformationMissing
....................................................................................................................................................................................................................................
LSS_osSecInformationMissing
Description
This alarm indicates that the security information Golden copy of a host operating system
has been deleted. The Golden copy is the initial snapshot of the host operating system,
which is used by the security audit program to identify possible security violations of the
host operating system.
Default severity
MAJOR
Root Cause
An unauthorized removal of one or more Golden copy files has occurred.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 Investigate the problematic file identified in the additionalText string. Correct the
problem by performing a Security Audit on this host from MI GUI to re-create the Golden
copy. Contact Alcatel-Lucent Customer Support as needed.
...................................................................................................................................................................................................
3 Once the error has been corrected, clear the alarm from MI GUI.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_osSecUnexpectedInformation
....................................................................................................................................................................................................................................
LSS_osSecUnexpectedInformation
Description
This alarm indicates that security audit program has detected an unexpected program
currently running on a host.
Default severity
Root Cause
An unauthorized network service/program has been installed.

...................................................................................................................................................................................................
1 First access MI GUI for the detailed information about this security alarm. Investigation
is needed to find out how the offending service/program got installed. The alarm can be
manually cleared after removing the service/program and verifying the system integrity.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_patch
....................................................................................................................................................................................................................................
LSS_patch
Description
When performing SIM patch procedure, failures that occur will result in the generation of
PATCH alarm.
Default severity
MAJOR
Root Cause
Any failure related to PATCH activities generates a PATCH alarm.

...................................................................................................................................................................................................
1 Based on the type of failure encountered, recovery actions may vary. If the PATCH alarm
is generated, contact Alcatel-Lucent Customer Support. Once the failure is corrected, a
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_pktCorruptionDetectedViaRCCLANCheck
....................................................................................................................................................................................................................................
LSS_pktCorruptionDetectedViaRCCLANCheck
Description
The LANCHECK audit has identified corrupted packets being transmitted through the
network.
Default severity
MAJOR
Root Cause
A hardware failure has occurred with the Ethernet Switch Card (ESC), its cabling, or the
IP network.

...................................................................................................................................................................................................
1 The reason for the data corruption needs to be understood and corrected. It is possible that
the Service Host Ethernet Port failed, the cabling that interconnects the Ethernet Port to
the network is damaged, the Routers and/or Ethernet Switches that make up the
Alcatel-Lucent SoftSwitch Network failed. Each of these possible reasons needs to be
investigated and discounted or corrected by maintenance personnel. Once corrected, the
alarm is cleared.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_platformCommandFailure
....................................................................................................................................................................................................................................
LSS_platformCommandFailure
Description
This alarm indicates that a linux command started via crond has failed to execute on a
host.
Default severity
WARNING
Root Cause
The command or argument(s) invalid.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 Investigate the specific offending file identified in additionalText string and correct the
problem. Contact Alcatel-Lucent Customer Support as needed.
...................................................................................................................................................................................................
3 Once the file has been corrected, clear the alarm from MI GUI.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_pmDataNotCollected
....................................................................................................................................................................................................................................
LSS_pmDataNotCollected
Description
The raised alarm LSS_pmDataNotCollected indicates that the PM process on CNFG card
could not receive PM data from a service in an interval(5 minutes).
Notes:
An alarm with the same severity is raised only once for the same service.
The fired alarm clears if the PM data from the service could be properly collected by
PM process in the following intervals.
Default severity
MINOR
Severity Details
THE ALARM ONLY HAS MINOR SEVERITY:
Minor Alarm: PM process on CNFG card could not receive PM data from the service in
this interval.
Root Cause
PM process could not receive PM data from a service in this interval which is caused by
network congestion or card restart.

...................................................................................................................................................................................................
1 Check if the card is in the network congestion status. if it could not be pinged through,
restart the card.
...................................................................................................................................................................................................
2 Check if the card is in the init status. if yes, wait for a while.
...................................................................................................................................................................................................
3 If the above steps do not correct the problem, contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_processDown
....................................................................................................................................................................................................................................
LSS_processDown
Description
This alarm indicates that an application process that should be running has terminated.
Default severity
MAJOR
Root Cause
This alarm is usually the result of excessive software errors that have caused the recovery
software to terminate the process. Logs are generated for the errors that have occurred
and the recovery actions that have been taken. The alarm can also occur as a result of
manual activities such as initialization or switchover requests or during maintenance
activities such as software update or patch.

...................................................................................................................................................................................................
1 Recovery software should automatically recover from the abnormal or maintenance event
that has caused the process termination, without any manual involvement. The automatic
recovery will restart just that process or will reboot the card as necessary.
...................................................................................................................................................................................................
2 If the alarm does not clear or if it occurs repeatedly, contact Alcatel-Lucent Customer
Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_processNotStarted
....................................................................................................................................................................................................................................
LSS_processNotStarted
Description
The processNotStarted alarm is caused if an application process cannot be started, or one
of the following daemons has a problem starting:
ipm (on all service hosts on ATCA)
dhcpd (on MI/CNFG service host on ATCA)
dnsproxy (on SNS service host on ATCA)
pdns server (on SNS service host on ATCA)
unbound (on service host requiring resolving capabilities on ATCA)
lighttpd (on MI/CNFG service host on ATCA/CPSB)
lsnmonitor (on MI service hosts on ATCA)
sshd (on all service hosts with fixed IP address on ATCA/CPSB)
ntpd (on all service hosts on ATCA)
Default severity
CRITICAL
Root Cause
ipm - when the ipm process fails to start after trying to reboot and 3 attempts, the
ipmStartupFailure alarm is generated.
dhcpd -
dnsproxy - when the dnsproxy process fails to start after 3 attempts, the
dnsproxyStartup Failure alarm is generated.
pdns server - when the pdns process fails to start after 3 attempts, the
pdnsStartupFailure alarm is generated.
unbound - when the unbound process fails to start after 3 attempts, the
unboundStartupFailure alarm is generated.
lighttpd - when the lighttpd process fails to start after trying 3 attempts, the
lighttpdStartupFailure alarm is generated.
lsnmonitor - when the lsnmonitor process fails to start after 3 attempts, the
applStartupFailure alarm will be generated.
sshd - when the sshd process fails to start after 3 attempts, the sshdStartupFailure
alarm is generated.
ntpd - when the ntpd process fails to start after 3 attempts, the ntpdStartupFailure
alarm is generated.
Application Process - when the application process fails to start after 3 attempts, the
applStartupFailure alarm is generated.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
1
IPM: Based on the type of failure encountered, recovery actions may vary. If the
ipmStartupFailure is generated, contact
Alcatel-Lucent Customer Support
. Once the failure is corrected, the startup of the ipm process will automatically clear
the alarm.
DHCPD: Based on the type of failure encountered, recovery actions vary. If the
dhcpdStartupFailure is generated, contact
. Once the failure is correct, the startup of the dhcpd process will automatically clear
the alarm.
DNSPROXY: Based on the type of failure encountered, recovery actions may vary. If
the dnsproxyStartupFailure is generated, contact
. Once the failure is corrected, the startup of the dnsproxy process will automatically
clear the alarm.
PDNS SERVER: Based on the type of failure encountered, recovery actions may vary.
If the pdnsStartupFailure is generated, contact
. Once the failure is corrected, the startup of the pdns process will automatically clear
the alarm.
UNBOUND: Based on the type of failure encountered, recovery actions may vary. If
the unboundStartupFailure is generated, contact
. Once the failure is corrected, the startup of the unbound process will automatically
clear the alarm.
LIGHTTPD: Based on the type of failure encountered, recovery actions may vary. If
the lighttpdStartupFailure is generated, contact
. Once the failure is corrected, the startup of the lighttpd process will automatically
clear the alarm.
LSNMONITOR: Based on the type of failure encountered, recovery actions may vary.
If the applyStartupFailure is generated for lsnmonitor, contact
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
....................................................................................................................................................................................................................................
. Once the failure is corrected, the startup of the lsnmonitor process will automatically
clear the alarm.
SSHD: Based on the type of failure encountered, recovery actions may vary. If the
sshdStartupFailure is generated, contact
. Once the failure is corrected, the startup of the sshd process will automatically clear
the alarm.
NTPD: Based on the type of failure encountered, recovery actions may vary. If the
ntpdStartupFailure is generated, contact
. Once the failure is corrected, the startup of the ntpd process will automatically clear
the alarm.
Application Process: Based on the type of failure encountered, recovery actions may
vary. If the applStartupFailure is generated, contact
. Once the failure is corrected, the startup of the application process will automatically
clear the alarm.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_remoteQueryServerFailure
....................................................................................................................................................................................................................................
LSS_remoteQueryServerFailure
Description
This alarm indicates that a host has lost connection to a remote DNS/ENUM server.
Default severity
MAJOR
Root Cause
The cause of this alarm can be
The DNS server is down or resetting

...................................................................................................................................................................................................
1 The user needs to check the failed DNS server as to the nature of the server failure
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_remotedbLinkDown
....................................................................................................................................................................................................................................
LSS_remotedbLinkDown
Description
This alarm displays when the remotedb trigger function connection does not exist.
Default severity
MAJOR
Root Cause
The alarm is generated when a Service or Application cannot connect to the remote
database server on either OAM machine.

...................................................................................................................................................................................................
1 Normally the alarm clears automatically when a remote service restarts and re-connects to
the remotedb database; If this alarm does not clear, contact Alcatel-Lucent Customer
Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_restore
....................................................................................................................................................................................................................................
LSS_restore
Description
When performing SIM restore procedure, failures that occur will result in the generation
of RESTORE alarm.
Default severity
MAJOR
Root Cause
Any failure related to RESTORE activities generates a RESTORE alarm.

...................................................................................................................................................................................................
1 Based on the type of failure encountered, recovery actions may vary. If the RESTORE
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_serviceOnewayCommunication
....................................................................................................................................................................................................................................
LSS_serviceOnewayCommunication
Description
A service might have one way communication to the Redundancy Manager and possibly
other network elements.
Default severity
MINOR
Root Cause
REM will periodically send a timestamp to the service and expects that service to echo
the timestamp back in the regular heartbeat message. If the service does not echo the
timestamp back within a reasonable amount of heartbeats after the new timestamp is sent,
REM will raise the service onewayCommunication alarm.

...................................................................................................................................................................................................
1 Wait approximately 1 minute 30 seconds; if the alarm does not clear autonomously, one
will need to investigate why the alarm does not clear.
...................................................................................................................................................................................................
2 Check and see if there are other outstanding alarms on this service that might trump the
onewayCommunication alarm. Those alarms would be of type connectionLost; or any
other alarms associated to the state of the service. Other alarms would indicate that a
more severe problem exists on the service; and onewayCommunication could optionally
be cleared at this point; as the other service based alarms most likely supersede the
onewayCommunication alarm.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_sheddingOverload
....................................................................................................................................................................................................................................
LSS_sheddingOverload
Description
This alarm indicates the message shedding severity under system overload. The two
severity levels indicate the degree of shedding severity.
The types of messages/calls that are shed is specific to the application and there tends to
be additional types of messages impacted by the shedding as the severity increases.
Currently the default thresholds between Major and Critical is 70.
Default severity
CRITICAL, MAJOR
Root Cause
Call traffic is too high with the current hardware/software configuration
Some task/process uses CPU/Memory resource improperly, for example tight loop.

...................................................................................................................................................................................................
1 Verify that there is no running debug or testing tool that uses a lot of CPU/memory.
...................................................................................................................................................................................................
2 If CPU or memory utilization regularly exceeds thresholds, investigate how the call traffic
load can be reduced:
Reengineer so less traffic is directed to this office or card.
Consider replacing the overloaded card pair with higher-capacity cards.
Verify if there are enough cards to handle the expected load and add additional cards
as appropriate.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_shmcEthernetError
....................................................................................................................................................................................................................................
LSS_shmcEthernetError
Description
The Ethernet link to the Shelf Management Card (ShMC) has failed.
Default severity
MAJOR, MINOR
Root Cause
A failure has occurred with the IP network, this may be caused by a switchover or reboot
of a shelf management card.

...................................................................................................................................................................................................
1 Verify the hub port corresponding to this server by telnet to the hub card. Correct or
replace the hub as necessary.
...................................................................................................................................................................................................
2 Verify the shelf management cards are running on active/standby status by "clia
shmstatus" command on shelf management card. Correct the status as necessary.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_simxml
....................................................................................................................................................................................................................................
LSS_simxml
Description
When performing simxml procedure, failures that occur will result in the generation of
SIMXML alarm.
Default severity
MAJOR
Root Cause
Any failure related to SIMXML activities generates a SIMXML alarm.

...................................................................................................................................................................................................
1 Based on the type of failure encountered, recovery actions may vary. If the SIMXML
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_softwareAllocatedResourceOverload
....................................................................................................................................................................................................................................
LSS_softwareAllocatedResourceOverload
Description
This alarm indicates that the utilization of a pre-allocated resource by software has
exceeded thresholds. The resource could be internal buffer, data structure array, table
entries, etc.
Default severity
Root Cause
Call traffic is too high with the current hardware/software configuration.

...................................................................................................................................................................................................
1 Consider reengineering so that less traffic is directed to this service.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_softwareComponentStandbyNotReady
....................................................................................................................................................................................................................................
LSS_softwareComponentStandbyNotReady
Description
The state of the software component, Virtual Machine (VM) that is executing on the
Service Host is standby-cold or standby-cool
Default severity
MAJOR
Root Cause
VM restart may fire this alarm but should be cleared after some time since
standby-cold/standby-cool state is an intermediate state which changes from init/unavail
and changes to standby-hot state later. The timing for each VM to come up is different.
Since this alarm will fire during the NORMAL init time, it should not treat as a problem
until 10 minutes later.
Software error, e.g. required local inter-process connection lost, may cause the VM sticks
in state of standby-cold/standby-cool permanently, which is invalid state, it needs to be
repaired by office maintenance personnel.

...................................................................................................................................................................................................
1 Generally, no manual action is necessary. Integrity software on the Service Host takes
care of automatic recovery from the standby-cold/standby-cool state. When automatic
recovery occurs the alarm clears automatically as well. The timing for each VM to come
up is different. Since this alarm will fire during the NORMAL init time, it should not treat
as a problem until 10 minutes later.
If the alarm does not clear after one interval, contact Alcatel-Lucent Customer Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_svcdegrow
....................................................................................................................................................................................................................................
LSS_svcdegrow
Description
When performing SIM service degrow (svcdegrow) procedure, failures that occur will
result in the generation of SVCDEGROW alarm.
Default severity
MAJOR
Root Cause
Any failure related to SVCDEGROW activities generates a SVCDEGROW alarm.

...................................................................................................................................................................................................
1 Based on the type of failure encountered, recovery actions may vary. If the
SVCDEGROW alarm is generated, contact Alcatel-Lucent Customer Support. Once the
failure is corrected, a resumption of the SIM procedures will automatically clear the
alarm.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_svcgrow
....................................................................................................................................................................................................................................
LSS_svcgrow
Description
When performing SIM service grow (svcgrow) procedure, failures that occur will result
in the generation of SVCGROW alarm.
Default severity
MAJOR
Root Cause
Any failure related to SVCGROW activities generates a SVCGROW alarm.

...................................................................................................................................................................................................
1 Based on the type of failure encountered, recovery actions may vary. If the SVCGROW
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_swVersionMismatch
....................................................................................................................................................................................................................................
LSS_swVersionMismatch
Description
The software version running on this service member does not match the version that
should be running according to the database table IPCFG_POOL_MEMBERS, field
build_sec.
Default severity
MAJOR
Root Cause
Either a private version of a service binary was installed, or the database field was altered.

...................................................................................................................................................................................................
1 On the MI, run the "rem_adm --action version_chk --set all" command. It should show
that for this service member, build_sec disagrees between the database and the running
binary. Check whether either of them agrees with the service zip file.
...................................................................................................................................................................................................
2 If the database and zip agree, initialize the service member. Otherwise, contact
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_tftpDownloadCorrupt
....................................................................................................................................................................................................................................
LSS_tftpDownloadCorrupt
Description
This alarm can be fired due to two different problems. Alarm information is given specific
sub-section below.
1. serviceApplicationZipTransferFailure
A problem was encountered during the checking of an service's application zip file
that was transferred using TFTP from the CNFG host.
2. fileSentFailure
A problem was encountered when a file was sent from ccflLogger to BTS by GDI
Thread.
Default severity
MAJOR, CRITICAL
Severity Details
MAJOR
2. fileSentFailure
CRITICAL
Root Cause
There are several possible causes being variations of:
The service's application zip file on the configuration host is incorrect, missing, or
corrupted.
The diskless host receiving the service's application zip file via TFTP has resource
issues.
2. fileSentFailure
There are several possible causes being variations of:
The file on the CDR service is missing, incorrect or corrupted.
The configuration of CCF is missing or invalid.

...................................................................................................................................................................................................
1 A. serviceApplicationZipTransferFailure
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_tftpDownloadCorrupt
....................................................................................................................................................................................................................................
If the Additional Info field looks like TftpOpen() Failure Ret(hexadecimal error number),
IORet(hexadecimal error number), File( service application zip file name and path ), IP(
hexadecimal version of the CNFG host IP ) continue on to step 2. Otherwise, goto step 3.
...................................................................................................................................................................................................
2 Check the file name and path on the indicated CNFG host and ensure that is readable by
all. If not performing SU or Path, recover file from mate CNFG host.
...................................................................................................................................................................................................
3 reboot the host issuing the alarm

...................................................................................................................................................................................................
4 If the alarm persists. Contact the Alcatel-Lucent Customer Support

...................................................................................................................................................................................................
5 B. fileSentFailure
Check the path, port, and file name on the FS GUI(System Admin -> Local CCF).
...................................................................................................................................................................................................
6 Check the connection from CDR service to BTS.

...................................................................................................................................................................................................
7 Reboot the host issuing the alarm.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_threadsExhausted
....................................................................................................................................................................................................................................
LSS_threadsExhausted
Description
One or more critical CP Tasks have been un-responsive to regular Integrity Monitor -
IMON Heartbeats. IMON attempted to restart them and multiple restarts have escalated to
a Process Init on the Standby Card or a Switch Over to the Standby Card from the Active
Card where the target stuck task was running.
Default severity
CRITICAL
Root Cause
Task may be executing code that is possibly in an infinite loop or too CPU intensive.

...................................................................................................................................................................................................
1 NOT APPLICABLE
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_upgrade
....................................................................................................................................................................................................................................
LSS_upgrade
Description
When performing Software Upgrade (SU) related activities (which includes bkupSys and
SIM upgrade procedure), failures that occur will result in generation of SU alarm.
Default severity
MAJOR
Root Cause
Any failure related to SU activities generates an SU alarm.

...................................................................................................................................................................................................
1 Based on the type of failure encountered, recovery actions may vary. If the SU alarm is
generated, contact Alcatel-Lucent Customer Support. Once the failure is corrected, a
resume of the SIM procedures will automatically clear the alarm. For bkupSys, once the
failure is corrected re-executing bkupSys will automatically clear the alarm.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms LSS_virtualClusterDown
....................................................................................................................................................................................................................................
LSS_virtualClusterDown
Description
A Virtual Cluster spanning a pair of Service Hosts abnormally transitioned to an
out-of-service state. (Note, a Virtual Cluster is a logical grouping of a pair of Software
Components. Each Software Component executes on a separate Service Host and
typically runs Active and Standby.)
Default severity
MAJOR
Root Cause
A software bug or internal error could not gracefully handle some unexpected event and
instead terminated software abruptly on one Service Host and then the redundant Service
Host, causing a duplex failure condition.

...................................................................................................................................................................................................
1 If this alarm persists, contact Alcatel-Lucent Customer Support.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms RALARM_Loop
....................................................................................................................................................................................................................................
RALARM_Loop
Description
The alarm board provides 2 external input ports. The 2 alarm inputs are used as follows:
loop 1 - Connected to the alarm circuit-breakers (logical OR function over all the
circuit-breakers).
loop 2 - Available via a dedicated connector and can be used to connect a temperature
sensor in the cabinet.
If either of these loops are closed, a loop alarm is generated. Also, if the loops are
unavailable for monitoring, a loops unavailable alarm is generated.
See the specific problem of the alarm for which condition the alarm is detecting.
Default severity
MAJOR
Root Cause
loop 1 - Circuit breaker/fuse failure.
loop 2 - External input (e.g. temperature sensor) assertion.
loops unavailable - Loops are unavailable for monitoring.

...................................................................................................................................................................................................
1
loop 1 - Verify/replace circuit breakers/fuses.
loop 2 - Depends on what device (e.g. temperature sensor) is connected to the external
input.
loops unavailable - contact
.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms RALARM_Power
....................................................................................................................................................................................................................................
RALARM_Power
Description
This alarm indicates a problem with the -48V, A feed or B feed, power to the Power
Distribution Unit.
Default severity
MAJOR
Root Cause
Fuse pulled/failed for Power Distribution Unit.
Circuit breaker tripped/failed for Power Distribution Unit.
Power feed lost to Power Distribution Unit.

...................................................................................................................................................................................................
1 Check the Power Distribution Units LEDs, circuit breakers, fuses, and power feeds.
...................................................................................................................................................................................................
2 Replace the faulty alarm card, circuit breakers, fuses, or power feeds.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_BackupFailure
....................................................................................................................................................................................................................................
SYS_BackupFailure
Description
The backup of an SNE has failed. On the next successful backup, this alarm clears.
Default severity
MINOR
Root Cause
The MI attempted a backup on an SNE and it failed.

...................................................................................................................................................................................................
1 If the additionalText of the alarm states 'Fail to get AccessKey for ESCHost/LNG
application...', you need to set up userid/password on corresponding esc/lng in
'Configuration Management' --> 'Backup Management' --> 'Login Administration' panel
on MI GUI first.
...................................................................................................................................................................................................
2 Attempt another backup.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_CPM_USERDATA_INCONSITENCY
....................................................................................................................................................................................................................................
SYS_CPM_USERDATA_INCONSITENCY
Description
A possible CPM user data inconsistency problem has been detected on the MI.
Default severity
MINOR
Root Cause
CPM audit will check user data when doing authentication. If it finds there is anything
abnormal, it gives out a security log. And evlog can be configured to fire this alarm.

...................................................................................................................................................................................................
1 Login to active MI as root

execute "mividstat -a"
Make sure CPM is enabled and Connection Health Check is Yes.

...................................................................................................................................................................................................
2 If CPM status is OK and there is such alarm. Please contact Alcatel-Lucent Customer
Support for further support.
...................................................................................................................................................................................................
3 Once the issue is resolved, this alarm should be cleared manually from the MI GUI.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_CPM_USERDATA_RESTORED
....................................................................................................................................................................................................................................
SYS_CPM_USERDATA_RESTORED
Description
CPM audit restore user's data after it finds issue.
Default severity
MINOR
Root Cause
CPM audit will check user data when doing authentication. If it finds there is anything
abnormal, it will try to restore(only restore user lss/root/lcpadm data.) and give out a
security log. And evlog can be configured to fire this alarm.

...................................................................................................................................................................................................


...................................................................................................................................................................................................
2 If CPM status is OK and there is such alarm. Please contact Alcatel-Lucent Customer
Support for further support.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_Configuration
....................................................................................................................................................................................................................................
SYS_Configuration
Description
A possible configuration problem has been detected on the MI.
Default severity
MAJOR
Root Cause
A configuration step or procedure may have been inadvertently skipped.

...................................................................................................................................................................................................
1 If the specificProblem is MissingScheduledBackups:

Run mi_audit -a sched_backups on the active MI to get a list of the devices that do
not have a scheduled backup. For those devices, schedule a backup job using the MI GUI,
Configuration Management->Backup Management->Scheduling
Run mi_audit -a sched_backups on the active MI to clear the alarm once all
required backups are scheduled.
...................................................................................................................................................................................................
2 If the specificProblem is PMDisabled:

Run PMcontrol --master start on the active MI to enable PM collection
This will enable PM collection on the MI and automatically clear this alarm.
...................................................................................................................................................................................................
3 If the specificProblem is NTPServerNotConfigured:

Configure at least one NTP server.
Run mi_audit -a ntp_server on the active MI to clear the alarm.
...................................................................................................................................................................................................
4 If the specificProblem is NTPServerAbnormalState:

On the active MI, run ntpq -p -n to identify the current NTP peer. The IP address in
the "remote" column that is preceded by a "*" is the current peer.
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_Configuration
....................................................................................................................................................................................................................................
Run ntpconf_adm --action show_server to see the configured NTP server IP
address(es). If the current peer NTP server is not one of the configured NTP servers, the
NTP server state is considered abnormal. This condition must be resolved before the
alarm clears. Contact Alcatel-Lucent Customer Support if needed to help resolve this
condition.
Once the condition is resolved, run mi_audit -a ntp_server on the active MI to
clear the alarm.
...................................................................................................................................................................................................
5 If the specificProblem is MaintModeEnabled:

This alarm is raised when the MI is placed into maintenance mode for any maintenance
activity using the mi_maint on cmd. It clears when taken out of maintenance mode,
using the mi_maint off cmd. If for some reason the alarm does not clear and the
maintenance flag is off (verify with mi_maint status cmd), run
mi_audit -a maint_mode on the active MI to clear the alarm.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_EventQueueCapacity
....................................................................................................................................................................................................................................
SYS_EventQueueCapacity
Description
The MI event queue is nearing or has exceeded its capacity.
Default severity
MINOR, MAJOR
Root Cause
The MI event queue can grow if the MI is overloaded with a sudden bursts of traps, or
other events such as state change events, at a rate faster than it can process them.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_ICMPFailure
....................................................................................................................................................................................................................................
SYS_ICMPFailure
Description
The MI was unable to communicate to a host via its IP interface.
This alarm clears when the MI re-establishes Native Ping communications with the host.
This is attempted at each polling interval. The default polling interval is every 5 minutes.
Default severity
MAJOR
Root Cause
The ethernet cable is bad
The IP connection is bad
The IP network is congested.

...................................................................................................................................................................................................
1 Verify that the ethernet cable is connected and in working order.

...................................................................................................................................................................................................
2 Verify that the routers/switches are configured correctly.

...................................................................................................................................................................................................
3 If the problem persists over several polling cycles, contact Alcatel-Lucent Customer
Support.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_IPsecConfig
....................................................................................................................................................................................................................................
SYS_IPsecConfig
Description
Missing or obsolete SNMP Trap subnets found in the IPsec configuration file on the
MI-Agent.
Default severity
MAJOR
Root Cause
The IPsec SNMP trap subnet configuration on the MI-Agent is either missing one or more
entries, or has one or more obsolete entries.

...................................................................................................................................................................................................
1 A change to the IPsec configuration is needed. Please refer to the procedure described in
the section titled "To configure IPsec SNMP trap entries" in the "Alcatel-Lucent 5400
Linux Control Platform, Security Management" guide for the ATCA platform, or in the
"Alcatel-Lucent Control Platform 1800 OAMP" guide for the CPSB platform.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_LinkDown
....................................................................................................................................................................................................................................
SYS_LinkDown
Description
A linkDown alarm signifies that the operational status for one of the communication links
is about to enter the down state. The name/index of the interface is identified in the
specificProblem of the alarm.
Default severity
MAJOR
Root Cause
The link may be disconnected
The link may be broken
The link may be administratively down.

...................................................................................................................................................................................................
1 Verify the cabling.

...................................................................................................................................................................................................
2 Verify the far-end of the link.

...................................................................................................................................................................................................
3 If the alarm is on an external faceplate port (e.g. eth2/eth3), and the lack of connectivity
on that port is expected (cable pulled out intentionally, or other end is disconnected), this
alarm should be manually cleared on the MI GUI.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_NotifyDisabled
....................................................................................................................................................................................................................................
SYS_NotifyDisabled
Description
This alarm occurs when a user login is temporarily disabled, yet the user during this
period attempts to login with the correct userid and password. User Intervention by a
Security Administrator is not required when a user is temporarily disabled as long as no
more errored logins are attempted within fifteen minutes interval. If a user becomes
locked then an additional alarm (SYS_NotifyLocked) is generated thus Security
Administrator intervention is required.
Default severity
WARNING
Root Cause
Repeated unsuccessful login attempts by user followed by correct userid/password
attempt while the account is disabled.

...................................................................................................................................................................................................
1 Contact the user of this userid to determine if they are aware of these attempts to log onto
the system using this userid.
...................................................................................................................................................................................................
2 Determine whether any security violations occurred and report accordingly. Manually
clear this alarm from the MI Alarm Browser.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_NotifyLocked
....................................................................................................................................................................................................................................
SYS_NotifyLocked
Description
This alarm occurs when a user is locked out from being able to Log in due to repeated
consecutive login failures. User Intervention by a Security Administrator is required to
unlock the account.
Default severity
MINOR
Root Cause
Repeated unsuccessful login attempts by user

...................................................................................................................................................................................................
1 Contact the user of this userid to determine if they are aware of these attempts to log onto
the system using this userid.
...................................................................................................................................................................................................
2 Determine whether any security violations occurred and report accordingly Log onto
NavisID GUI and unlock this user's account if appropriate. Manually clear this alarm
from the MI Alarm Browser.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_RADIUS_TO_LDAP_FAILURE
....................................................................................................................................................................................................................................
SYS_RADIUS_TO_LDAP_FAILURE
Description
This alarm occurs when RADIUS fails to connect to LDAP during user authentication
attempt
Default severity
MINOR
Root Cause
The periodic simulated user authentication attempt using Centralized Password
Management infrastructure detected a possible failure or network connectivity issue.

...................................................................................................................................................................................................
1 This Alarm clears automatically when the fault condition is no longer present.
...................................................................................................................................................................................................
2 Login to active MI (ATCA) as root

Make sure Radius/LDAP Connection Health Check is Yes

...................................................................................................................................................................................................
3 Check the /var/log/auth.log for detailed information. You may also use the Security and
Audit Trail Log Viewer on the MI-agent GUI to view this log.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_ROOT_ACCESS_DENIED
....................................................................................................................................................................................................................................
SYS_ROOT_ACCESS_DENIED
Description
This alarm occurs when a user makes three attempts within a 30 minute period to log onto
the LCP hosts as root userid from a restricted domain. This alarm must be manually
cleared
Default severity
MINOR
Root Cause
Repeated attempts to log onto LCP hosts as root from restricted domain.

...................................................................................................................................................................................................
1 This Alarm should be cleared manually.

...................................................................................................................................................................................................
2 Need to find out where the user is trying to login from in order to further verify whether
this is a legitimate user.
...................................................................................................................................................................................................
3 Check the /var/log/auth.log for detailed information. You may also use the Security and
Audit Trail Log Viewer on the MI-agent GUI to view this log.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_ROOT_FTP_VIOLATION
....................................................................................................................................................................................................................................
SYS_ROOT_FTP_VIOLATION
Description
This alarm occurs when a user try to login the system three times as root with wrong
password in less 30 seconds. This alarm must be manually cleared.
Default severity
MINOR
Root Cause
Repeated unsuccessful login attempts by user.

...................................................................................................................................................................................................
1 Need to find out where is the user try to login.

...................................................................................................................................................................................................
2 Check the /var/log/auth.log for detailed information.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_ROOT_LOGIN_VIOLATION
....................................................................................................................................................................................................................................
SYS_ROOT_LOGIN_VIOLATION
Description
This alarm occurs when a user try to login the system three times as root with wrong
password in less 30 seconds. This alarm must be manually cleared.
Default severity
MINOR
Root Cause
Repeated unsuccessful login attempts by user.

...................................................................................................................................................................................................
1 Need to find out where is the user try to login.

...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_ROOT_SSH_LOGIN_VIOLATION
....................................................................................................................................................................................................................................
SYS_ROOT_SSH_LOGIN_VIOLATION
Description
This alarm occurs when a user unsuccessfully attempts to ssh as root user onto the LCP
host three times within 30 minutes. NOTE: If Disable Root SSH External Access feature
is enabled, any external ssh as root attempt to the LCP host is rejected and treated as a
login failure. This alarm must be manually cleared.
Default severity
MINOR
Root Cause
Repeated unsuccessful ssh login attempts by user root.

...................................................................................................................................................................................................
1 Need to check the /var/log/auth.log to identify the IP of the originating ssh request and
attempt to identify the user attempting access the LCP host as root userid.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
3 The alarm must be manually cleared.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_SNETrapOverload
....................................................................................................................................................................................................................................
SYS_SNETrapOverload
Description
The SNMP trap rate threshold for a particular SNE to the MI-Agent has been exceeded.
Default severity
MAJOR
Root Cause
The SNE is sending an excessive rate of SNMP traps to the MI-Agent.

...................................................................................................................................................................................................
1 Verify the sanity of the SNE to determine what is causing it to send excessive SNMP
traps to the MI-Agent.
As the cause for excessive traps can vary by instance, use standard fault detection
techniques such as viewing alarms and/or network events at the MI-Agent, visual
inspection of the SNE for external alarms and/or loose cables, and running diagnostic test
to assist in determining the cause.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_SNMPAuthenticationFailure
....................................................................................................................................................................................................................................
SYS_SNMPAuthenticationFailure
Description
Signifies that an SNE managed by the MI is the addressee of an improperly authenticated
network protocol message. SNMP community name and client authentication failures
cause the Element Manager to generate this trap.
Default severity
WARNING
Root Cause
Someone may be trying to break into an SNE via its SNMP interface.

...................................................................................................................................................................................................
1 Verify that the individual trying to access the system is a legitimate user, and that the
SNMP community strings are set correctly. This alarm may be disabled by turning off the
SNMP authentication traps on the SNE (providing the SNE supports this capability).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_SNMPFailure
....................................................................................................................................................................................................................................
SYS_SNMPFailure
Description
The MI was unable to communicate to a host via its SNMP interface.
This alarm clears when the MI re-establishes SNMP communications with the host. This
is attempted at each polling interval. The default polling interval is every 5 minutes.
Default severity
MAJOR
Root Cause
The ethernet cable is bad
The IP connection is bad
The IP network is congested.

...................................................................................................................................................................................................
1 Verify that the ethernet cable is connected and in working order.

...................................................................................................................................................................................................
2 Verify that the SNE may be ICMP-pinged over the same interface to determine whether it
is an SNMP problem or a more general IP problem.
...................................................................................................................................................................................................
3 If the problem is an IP problem, verify that the routers/switches are configured correctly.
...................................................................................................................................................................................................
4 If the problem is only an SNMP problem and persists over several polling cycles, contact
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_SU_TO_ROOT_FAILURE
....................................................................................................................................................................................................................................
SYS_SU_TO_ROOT_FAILURE
Description
This alarm occurs when a user makes three failed attempts within a 30 minute period to
su to become root userid. This alarm will occur if you entered the wrong password for
root three times during the 30 minute interval when attempting to su to root userid.
Default severity
MINOR
Root Cause
Repeated failed attempts by user to su to root.

...................................................................................................................................................................................................
1 This Alarm should be cleared manually.

...................................................................................................................................................................................................
2 Need to find out where the user is trying to login from in order to further verify whether
this is a legitimate user. Need to check the user's CLI shell history to investigate for
possible suspicious activity.
...................................................................................................................................................................................................
3 Check the /var/log/auth.log for detailed access information. Check the /var/log/bash.log to
investigate the user's cli activity. You may also use the Security and Audit Trail Log
Viewer on the MI-agent GUI to view these logs.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_SYSTEMTrapOverload
....................................................................................................................................................................................................................................
SYS_SYSTEMTrapOverload
Description
The SNMP trap rate threshold for a collection of SNEs to the MI-Agent has been
exceeded.
Default severity
MAJOR
Root Cause
A collection of SNEs is sending an excessive rate of SNMP traps to the MI-Agent.

...................................................................................................................................................................................................
1 Verify the sanity of all SNEs in the system to determine which ones are sending excessive
SNMP traps to the MI-Agent.
As the cause for excessive traps can vary by instance, use standard fault detection
techniques such as viewing alarms and/or network events at the MI-Agent, visual
inspection of the SNE for external alarms and/or loose cables, and running diagnostic test
to assist in determining the cause.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_SetupAAAFailure
....................................................................................................................................................................................................................................
SYS_SetupAAAFailure
Description
A possible CPM configuration problem has been detected on the MI.
Default severity
CRITICAL
Root Cause
CPM detects errors when trying to add/update information.

...................................................................................................................................................................................................


...................................................................................................................................................................................................
2 Check all the diskful and diskless blades are in service.

...................................................................................................................................................................................................
3 Please contact Alcatel-Lucent Customer Support for further support.

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_TestAlarm
....................................................................................................................................................................................................................................
SYS_TestAlarm
Description
This alarm is for testing only. There is no problem being reported. It is used to test the
alarm handling functionality on the MI, from creation of an alarm on the MI to
forwarding out through the MI's northbound interface. This alarm should be manually
cleared when testing is completed.
Default severity
Root Cause
There is no problem being reported. This is only a test alarm.

...................................................................................................................................................................................................
1 There is no recovery needed, as this is just a test alarm. The alarm can be cleared
manually on the MI GUI, or by running mi_testalarm -s Clear on the active MI.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_ThresholdCrossed
....................................................................................................................................................................................................................................
SYS_ThresholdCrossed
Description
The measurement data is not meeting the specified performance thresholds and the
measurement data has reported errors that may indicate loss or degradation of
functionality or capacity.
Default severity
Severity Details
THE THRESHOLDS FOR DIFFERENT SEVERITIES IS CONFIGURED IN MI GUI
Root Cause
The traffic may be too high with the current hardware/software configuration.

...................................................................................................................................................................................................
1 Pay attention to the measurement data for which the alarm is reported.
...................................................................................................................................................................................................
2 Study the state of the system to decide on a course of action.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_UndiscoveredObject
....................................................................................................................................................................................................................................
SYS_UndiscoveredObject
Description
One or more undiscovered objects have been detected on the MI.
Default severity
MAJOR
Root Cause
One or more configured or installed devices are not discovered on the MI. This could be
due to an error in the configuration data or a processing error encountered on the MI.

...................................................................................................................................................................................................
1 On the MI GUI, run Tools->Global Discovery. If this does not clear the alarm, run the
following command on the active MI host:
If specificProblem is MissingSNE:<ip address>: mi_audit -a disc_sne
If specificProblem is MissingHardware: mi_audit -a disc_hw
If specificProblem is MissingServices: mi_audit -a disc_services
If specificProblem is MissingHosts: mi_audit -a disc_hosts
Contact Alcatel-Lucent Customer Support with the alarm details and the output of the
mi_audit cmd.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
BASE_ATCA Alarms SYS_WriteAAAFailure
....................................................................................................................................................................................................................................
SYS_WriteAAAFailure
Description
CPM tools failed to create scripts that are used for pump data into blades.
Default severity
CRITICAL
Root Cause
CPM detects errors when trying to add/update information.

...................................................................................................................................................................................................
1 Login to active MI (ATCA) as root


...................................................................................................................................................................................................
2 Check all the diskful and diskless blades are in service.

...................................................................................................................................................................................................
3 Check existence and permission(Owner:root, permission:755) for the directory

/var/opt/lib/cpm/fg on active MI.
...................................................................................................................................................................................................
4 Contact Alcatel-Lucent Customer Support for further support.

...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
WM7.0.0
Issue 1 August 2013
Appendix A: Compliance
Summary
9471 WMM compliance summary

Purpose
This topic gives a summary of compliance of the 9471 WMM.
Compliance
The9471 WMM is compliant with the following specifications:
Telcordia Technologies GR-1089-CORE Sections 2, 3, 4, 5, 6, 7, 8, and 9
Telcordia Technologies GR-63-CORE Sections 2, 3, 4.0, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6,
and 4.7
...................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary A-1
WM7.0.0
Issue 1 August 2013
Compliance Summary 9471 WMM compliance summary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
A-2 Alcatel-Lucent Proprietary 9471 WMM Alarms
WM7.0.0
Issue 1 August 2013
Appendix B: References
Revision history
WM6.0.0 > WM6.0.1
Reason for Change Location

New MME Alarms: LSS_ippuBusError (p. 2-112)
LSS_ippuResourceReset (p. 2-114)
Renamed MME Alarms: The following alarms were renamed:

LSS_externalLinkDown (p. 2-85) (formally
LSS_mmeExternalLinkDown)
LSS_internalCommunicationFailure (p. 2-111) (formally
LSS_mmeInternalCommunicationFailure)
LSS_liNearingCapacityLimit (p. 2-115) (formally
LSS_mmeLiNearingCapacityLimit)
LSS_noResetAckReceived (p. 2-118) (formally
LSS_mmeNoResetAckReceived)
LSS_taiFqdnError (p. 2-126) (formally
LSS_mmeTailFqdnError)
Modified MME Alarms: LSS_pathAvailability (p. 2-122)
New SGSN Chapter Chapter 3, SGSN Alarms

Modified ATCA_BASE ATCA_FanSpeed (p. 4-17)
alarms
LSS_processNotStarted (p. 4-149)
...................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary B-1
WM7.0.0
Issue 1 August 2013
References Revision history
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
B-2 Alcatel-Lucent Proprietary 9471 WMM Alarms
WM7.0.0
Issue 1 August 2013
Index
A Alarms
alarm type, 1-2

category, 1-2
MME application, 2-1
platform, 4-1
probable cause, 1-2
severity, 1-2
SGSN, 3-1
ATCA
alarms, 4-1
.............................................................
C compliance summary, A-1
.............................................................
M MME
alarms, 2-1
.............................................................
N Network Events
severity, 1-6
.............................................................
P Platform
alarms, 4-1
.............................................................
S SGSN
alarms, 3-1
....................................................................................................................................................................................................................................
9471 WMM Alarms Alcatel-Lucent Proprietary IN-1
WM7.0.0
Issue 1 August 2013
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
IN-2 Alcatel-Lucent Proprietary 9471 WMM Alarms
WM7.0.0
Issue 1 August 2013

9YZ054810005RKZZA Vol1 9471 Wireless Mobility Manager WMM Alarm Dictionary, WM7.0.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9YZ054810005RKZZA Vol1 9471 Wireless Mobility Manager WMM Alarm Dictionary, WM7.0.0

Uploaded by

Copyright:

Available Formats

Use pursuant to applicable agreements

Alcatel-Lucent LTE Evolved Packet Core

Refer to Appendix A, Compliance Summary.

About this document

Reason for reissue ...................................................................................................................................................................... xiii

Intended audience ...................................................................................................................................................................... xiv

How to use this document ....................................................................................................................................................... xiv

Conventions used ....................................................................................................................................................................... xiv

Related information .................................................................................................................................................................... xv

How to comment ........................................................................................................................................................................ xvi

1 About alarm management

Overview ...................................................................................................................................................................................... 1-1

Alarm groups description ....................................................................................................................................................... 1-2

Network event categories description ............................................................................................................................... 1-6

Overview ...................................................................................................................................................................................... 2-1

LSS_cmasFailure ..................................................................................................................................................................... 2-4

LSS_cmasReceiveFailure ..................................................................................................................................................... 2-5

LSS_cmasSendFailure ........................................................................................................................................................... 2-6

LSS_cpiGTPcResponseTOGn ............................................................................................................................................. 2-7

LSS_cpiGTPcResponseTOS3 .............................................................................................................................................. 2-9

LSS_cpiGTPcResponseTOSv ............................................................................................................................................ 2-11

LSS_cpiHOFailuresTo3G2GOverGn ............................................................................................................................. 2-13

LSS_cpiHOfailuresFromGERANoverS3 ...................................................................................................................... 2-15

LSS_cpiHOfailuresRAUto2G3GOverS3 ...................................................................................................................... 2-19

LSS_cpiHOfailuresRAUto2G3GnewSgwOverS3 ..................................................................................................... 2-21

LSS_cpiHOfailuresRAUto2G3GsameSgwOverS3 ................................................................................................... 2-23

LSS_cpiHOfailuresToGERANoverS3 ........................................................................................................................... 2-25

LSS_cpiHOfailuresToUTRANoverS3 ........................................................................................................................... 2-27

LSS_cpiMAFCommunicationFailureRate .................................................................................................................... 2-29

LSS_cpiMBMSSessionStartM3FailureRate ................................................................................................................ 2-31

LSS_cpiMBMSSessionStartSmFailureRate ................................................................................................................. 2-33

LSS_cpiMBMSSessionStopM3FailureRate ................................................................................................................. 2-35

LSS_cpiMBMSSessionStopSmFailureRate ................................................................................................................. 2-37

LSS_cpiMBMSSessionUpdateM3FailureRate ........................................................................................................... 2-39

LSS_cpiMBMSSessionUpdateSmFailureRate ............................................................................................................ 2-41

LSS_cpiMafAttachFailuresSysRelated .......................................................................................................................... 2-43

LSS_cpiMafAttachWithPGWreselection ...................................................................................................................... 2-44

LSS_cpiMafAttachWithSGWreselection ...................................................................................................................... 2-45

LSS_cpiMafEIRfailuresS13 ............................................................................................................................................... 2-46

LSS_cpiMafExtServiceReqFailuresSysRelated ......................................................................................................... 2-47

LSS_cpiMafExtServiceRequestFailures ........................................................................................................................ 2-49

LSS_cpiMafFailuresOverSGs ........................................................................................................................................... 2-51

LSS_cpiMafHLRAuthFail .................................................................................................................................................. 2-52

LSS_cpiMafHSSreselection ............................................................................................................................................... 2-53

LSS_cpiMafPDNconnWithPGWreselection ................................................................................................................ 2-54

LSS_cpiMafServiceReqFailuresSysRelated ................................................................................................................ 2-55

LSS_cpiMafTauFailuresInterMme .................................................................................................................................. 2-56

LSS_cpiMafTauFailuresInterMmeInterSgw ................................................................................................................ 2-57

LSS_cpiMafTauFailuresInterSgw .................................................................................................................................... 2-59

LSS_cpiPSHOFailuresOverSv .......................................................................................................................................... 2-63

LSS_cpiS3TauFailures ......................................................................................................................................................... 2-65

LSS_cpiS3TauFailuresInterSgw ....................................................................................................................................... 2-67

LSS_cpiS3TauFailuresIntraSGW ..................................................................................................................................... 2-69

LSS_cpiStopWarnMsgDeliveryS1MMEFailureRate ................................................................................................ 2-71

LSS_cpiStopWarnMsgDeliverySBcFailureRate ........................................................................................................ 2-73

LSS_cpiUECapacityUsage ................................................................................................................................................. 2-75

LSS_cpiWarnMsgDeliveryS1MMEFailureRate ......................................................................................................... 2-76

LSS_cpiWarnMsgDeliverySBcFailureRate .................................................................................................................. 2-78

LSS_dataMismatch ................................................................................................................................................................ 2-80

LSS_excessiveExternalLinksDown ............................................................................................................................... 2-83

LSS_externalLinkConfigurationLimit ............................................................................................................................ 2-84

LSS_externalLinkDown ..................................................................................................................................................... 2-85

LSS_failedAttachReqsRateExceeded ............................................................................................................................. 2-86

LSS_failedAuthRequestsHSSRateExceeded ............................................................................................................... 2-88