You are on page 1of 376

NN-20500-161 Wireless Service Provider Solutions

W-CDMA
Alcatel-Lucent 9353 Management System for Femto

IPC Alarms Reference Guide


NN-20500-161 01.05/EN Standard October 2008

Wireless Service Provider Solutions

W-CDMA
Alcatel-Lucent 9353 Management System for Femto

IPC Alarms Reference Guide


Document number: Document issue: Document status: Product release: Date: NN-20500-161 01.05/EN Standard FMS2.1 October 2008

Copyright 2007-2008 Alcatel-Lucent, All Rights Reserved ALCATEL-LUCENT CONFIDENTIAL UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be regarded as uncontrolled copies. ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have received this document in error, please notify the sender and destroy it immediately. Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marks of Alcatel-Lucent, Alcatel and Lucent Technologies. All other trademarks are the property of their owners.

Alcatel-Lucent Confidential

Publication history

PUBLICATION HISTORY
SYSTEM RELEASE: FMS2.1 October 2008
Issue 01.05/EN Standard Standard up-issue

July 2008
Issue 01.04/EN Preliminary Update after internal review

March 2008
Issue 01.03/EN Preliminary Update after internal review

January 2008
Issue 01.02/EN Draft Update after internal review

November 2007
Issue 01.01/EN Draft Creation for FMS2.1

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

Table of contents

ii

1 About this publication................................................................................................................................................... 1 2 Femto Management Solution Collection Roadmap.................................................................................................... 2 3 New in this release......................................................................................................................................................... 3 4 How to use this publication...........................................................................................................................................4 5 IPC alarm descriptions.................................................................................................................................................. 7 5.1 AC alarms................................................................................................................................................................... 9 5.1.1 IPC_7016_00035 - communicationFailure......................................................................................................... 10 5.1.2 IPC_7162_00035 - softwareVersionMismatch................................................................................................... 11 5.2 Cabinet alarms..........................................................................................................................................................12 5.2.1 IPC_7071_00036 - fanOrCktBreakerFailure...................................................................................................... 13 5.2.2 ........................................................................................................................................................................... 14 5.3 CICC alarms............................................................................................................................................................. 15 5.3.1 IPC_7030_00037 - degradeGroupMemberFault................................................................................................16 5.3.2 IPC_7033_00037 - escalatingRecovery.............................................................................................................18 5.3.3 IPC_7067_00037 - failureGroupMemberFault................................................................................................... 20 5.3.4 IPC_7117_00037 - lossOfPower........................................................................................................................22 5.3.5 IPC_7118_00037 - lossOfSanity........................................................................................................................ 23 5.3.6 IPC_7119_00037 - lostCommunication..............................................................................................................24 5.3.7 IPC_7123_00037 - maintenanceMode...............................................................................................................25 5.3.8 IPC_7131_00037 - notInstalled..........................................................................................................................26 5.3.9 IPC_7133_00037 - overTemperature.................................................................................................................27 5.3.10 IPC_7134_00037 - overTemperatureInFlow.................................................................................................... 28 5.3.11 IPC_7135_00037 - overTemperatureOutFlow................................................................................................. 29 5.4 CICCBPEtherPort alarms......................................................................................................................................... 30 5.4.1 IPC_7017_00014 - communicationFailureESC1_2............................................................................................31 5.4.2 IPC_7018_00014 - communicationFailureESC1_21..........................................................................................33 5.4.3 IPC_7019_00014 - communicationFailureESC2_2............................................................................................35 5.4.4 IPC_7020_00014 - communicationFailureESC2_21..........................................................................................37 5.4.5 IPC_7104_00014 - linkFailure............................................................................................................................39 5.4.6 IPC_7156_00014 - restoreServiceFailure.......................................................................................................... 40 5.5 CICCProc alarms......................................................................................................................................................41 5.5.1 IPC_7016_00015 - communicationFailure......................................................................................................... 42 5.5.2 IPC_7021_00015 - communicationFailureLRM................................................................................................. 43 5.5.3 IPC_7023_00015 - configurationError................................................................................................................44 5.5.4 IPC_7026_00015 - cpuUsageOverload............................................................................................................. 45

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

Table of contents

iii

5.5.5 IPC_7027_00015 - criticalSoftwareFailure......................................................................................................... 46 5.5.6 IPC_7094_00015 - heartbeatFailure.................................................................................................................. 47 5.5.7 IPC_7124_00015 - memoryBlockError.............................................................................................................. 48 5.5.8 IPC_7125_00015 - memoryUsageOverload...................................................................................................... 49 5.5.9 IPC_7155_00015 - resourceFailure................................................................................................................... 50 5.5.10 IPC_7156_00015 - restoreServiceFailure........................................................................................................ 51 5.5.11 IPC_7161_00015 - softwareAssertError.......................................................................................................... 52 5.5.12 IPC_7162_00015 - softwareVersionMismatch................................................................................................. 53 5.5.13 IPC_7163_00015 - standbyMateDown............................................................................................................ 54 5.5.14 IPC_7177_00015 - switchover......................................................................................................................... 55 5.5.15 IPC_7183_00015 - vitalResourceFailure......................................................................................................... 58 5.6 ESC alarms...............................................................................................................................................................59 5.6.1 IPC_7030_00041 - degradeGroupMemberFault................................................................................................60 5.6.2 IPC_7067_00041 - failureGroupMemberFault................................................................................................... 62 5.6.3 IPC_7117_00041 - lossOfPower........................................................................................................................64 5.6.4 IPC_7118_00041 - lossOfSanity........................................................................................................................ 65 5.6.5 IPC_7119_00041 - lostCommunication..............................................................................................................66 5.6.6 IPC_7123_00041 - maintenanceMode...............................................................................................................67 5.6.7 IPC_7131_00041 - notInstalled..........................................................................................................................68 5.6.8 IPC_7133_00041 - overTemperature.................................................................................................................69 5.6.9 IPC_7162_00041 - softwareVersionMismatch................................................................................................... 70 5.7 ESCBPEtherPort alarms...........................................................................................................................................71 5.7.1 IPC_7104_00026 - linkFailure............................................................................................................................72 5.8 ESCFAEtherPort alarms...........................................................................................................................................73 5.8.1 IPC_7104_00027 - linkFailure............................................................................................................................74 5.9 ESCProc alarms....................................................................................................................................................... 75 5.9.1 IPC_7016_00028 - communicationFailure......................................................................................................... 76 5.10 ExtAlmBox alarms.................................................................................................................................................. 77 5.10.1 IPC_7016_00042 - communicationFailure....................................................................................................... 79 5.10.2 IPC_7035_00042 - externalAlarmPort1........................................................................................................... 80 5.10.3 IPC_7036_00042 - externalAlarmPort10......................................................................................................... 81 5.10.4 IPC_7037_00042 - externalAlarmPort11......................................................................................................... 82 5.10.5 IPC_7038_00042 - externalAlarmPort12......................................................................................................... 83 5.10.6 IPC_7039_00042 - externalAlarmPort13......................................................................................................... 84 5.10.7 IPC_7040_00042 - externalAlarmPort14......................................................................................................... 85

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

Table of contents

iv

5.10.8 IPC_7041_00042 - externalAlarmPort15......................................................................................................... 86 5.10.9 IPC_7042_00042 - externalAlarmPort16......................................................................................................... 87 5.10.10 IPC_7043_00042 - externalAlarmPort17....................................................................................................... 88 5.10.11 IPC_7044_00042 - externalAlarmPort18....................................................................................................... 89 5.10.12 IPC_7045_00042 - externalAlarmPort19....................................................................................................... 90 5.10.13 IPC_7046_00042 - externalAlarmPort2......................................................................................................... 91 5.10.14 IPC_7047_00042 - externalAlarmPort20....................................................................................................... 92 5.10.15 IPC_7048_00042 - externalAlarmPort21....................................................................................................... 93 5.10.16 IPC_7049_00042 - externalAlarmPort22....................................................................................................... 94 5.10.17 IPC_7050_00042 - externalAlarmPort23....................................................................................................... 95 5.10.18 IPC_7051_00042 - externalAlarmPort24....................................................................................................... 96 5.10.19 IPC_7052_00042 - externalAlarmPort25....................................................................................................... 97 5.10.20 IPC_7053_00042 - externalAlarmPort26....................................................................................................... 98 5.10.21 IPC_7054_00042 - externalAlarmPort27....................................................................................................... 99 5.10.22 IPC_7055_00042 - externalAlarmPort28..................................................................................................... 100 5.10.23 IPC_7056_00042 - externalAlarmPort29..................................................................................................... 101 5.10.24 IPC_7057_00042 - externalAlarmPort3....................................................................................................... 102 5.10.25 IPC_7058_00042 - externalAlarmPort30..................................................................................................... 103 5.10.26 IPC_7059_00042 - externalAlarmPort31..................................................................................................... 104 5.10.27 IPC_7060_00042 - externalAlarmPort32..................................................................................................... 105 5.10.28 IPC_7061_00042 - externalAlarmPort4....................................................................................................... 106 5.10.29 IPC_7062_00042 - externalAlarmPort5....................................................................................................... 107 5.10.30 IPC_7063_00042 - externalAlarmPort6....................................................................................................... 108 5.10.31 IPC_7064_00042 - externalAlarmPort7....................................................................................................... 109 5.10.32 IPC_7065_00042 - externalAlarmPort8....................................................................................................... 110 5.10.33 IPC_7066_00042 - externalAlarmPort9....................................................................................................... 111 5.11 FanTray alarms.....................................................................................................................................................112 5.11.1 IPC_7068_00044 - fan1Failure...................................................................................................................... 113 5.11.2 IPC_7069_00044 - fan2Failure...................................................................................................................... 114 5.11.3 IPC_7070_00044 - fan3Failure...................................................................................................................... 115 5.11.4 IPC_7131_00044 - notInstalled......................................................................................................................116 5.12 FBPShelf alarms...................................................................................................................................................117 5.12.1 IPC_7133_00043 - overTemperature.............................................................................................................118 5.12.2 IPC_7136_00043 - overTemperatureSensor1............................................................................................... 120 5.12.3 IPC_7137_00043 - overTemperatureSensor2............................................................................................... 121

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

Table of contents

5.12.4 IPC_7138_00043 - overTemperatureSensor3............................................................................................... 122 5.12.5 IPC_7139_00043 - overTemperatureSensor4............................................................................................... 123 5.12.6 IPC_7140_00043 - overTemperatureSensor5............................................................................................... 124 5.12.7 IPC_7141_00043 - overTemperatureSensor6............................................................................................... 125 5.12.8 IPC_7142_00043 - overTemperatureSensor7............................................................................................... 126 5.12.9 IPC_7143_00043 - overTemperatureSensor8............................................................................................... 127 5.13 GICC alarms......................................................................................................................................................... 128 5.13.1 IPC_7002_00038 - ahardwareModelDifferentFromConfigured...................................................................... 129 5.13.2 IPC_7030_00038 - degradeGroupMemberFault............................................................................................130 5.13.3 IPC_7033_00038 - escalatingRecovery.........................................................................................................132 5.13.4 IPC_7067_00038 - failureGroupMemberFault............................................................................................... 134 5.13.5 IPC_7117_00038 - lossOfPower....................................................................................................................136 5.13.6 IPC_7118_00038 - lossOfSanity.................................................................................................................... 137 5.13.7 IPC_7119_00038 - lostCommunication..........................................................................................................138 5.13.8 IPC_7123_00038 - maintenanceMode...........................................................................................................139 5.13.9 IPC_7131_00038 - notInstalled......................................................................................................................140 5.13.10 IPC_7133_00038 - overTemperature...........................................................................................................141 5.13.11 IPC_7134_00038 - overTemperatureInFlow................................................................................................ 142 5.13.12 IPC_7135_00038 - overTemperatureOutFlow............................................................................................. 143 5.14 GICCBPEtherPort alarms..................................................................................................................................... 144 5.14.1 IPC_7017_00016 - communicationFailureESC1_2........................................................................................145 5.14.2 IPC_7018_00016 - communicationFailureESC1_21......................................................................................147 5.14.3 IPC_7019_00016 - communicationFailureESC2_2........................................................................................149 5.14.4 IPC_7020_00016 - communicationFailureESC2_21......................................................................................151 5.14.5 IPC_7104_00016 - linkFailure........................................................................................................................153 5.14.6 IPC_7156_00016 - restoreServiceFailure...................................................................................................... 154 5.15 GICCFAEtherPort alarms..................................................................................................................................... 155 5.15.1 IPC_7104_00017 - linkFailure........................................................................................................................156 5.15.2 IPC_7156_00017 - restoreServiceFailure...................................................................................................... 157 5.16 GICCProc alarms..................................................................................................................................................158 5.16.1 IPC_7005_00020 - allOpticalLinksFailed....................................................................................................... 159 5.16.2 IPC_7016_00020 - communicationFailure..................................................................................................... 160 5.16.3 IPC_7021_00020 - communicationFailureLRM............................................................................................. 161 5.16.4 IPC_7023_00020 - configurationError............................................................................................................162 5.16.5 IPC_7026_00020 - cpuUsageOverload......................................................................................................... 163

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

Table of contents

vi

5.16.6 IPC_7027_00020 - criticalSoftwareFailure..................................................................................................... 164 5.16.7 IPC_7094_00020 - heartbeatFailure.............................................................................................................. 165 5.16.8 IPC_7124_00020 - memoryBlockError.......................................................................................................... 166 5.16.9 IPC_7125_00020 - memoryUsageOverload.................................................................................................. 167 5.16.10 IPC_7155_00020 - resourceFailure............................................................................................................. 168 5.16.11 IPC_7156_00020 - restoreServiceFailure.................................................................................................... 169 5.16.12 IPC_7161_00020 - softwareAssertError...................................................................................................... 170 5.16.13 IPC_7162_00020 - softwareVersionMismatch............................................................................................. 171 5.16.14 IPC_7163_00020 - standbyMateDown........................................................................................................ 172 5.16.15 IPC_7183_00020 - vitalResourceFailure..................................................................................................... 173 5.17 GICCSTM1OC3Port alarms................................................................................................................................. 174 5.17.1 IPC_7104_00021 - linkFailure........................................................................................................................175 5.17.2 IPC_7105_00021 - linkFailureAIS_L.............................................................................................................. 176 5.17.3 IPC_7106_00021 - linkFailureAIS_P..............................................................................................................177 5.17.4 IPC_7107_00021 - linkFailureLCD_P............................................................................................................ 178 5.17.5 IPC_7108_00021 - linkFailureLOF.................................................................................................................179 5.17.6 IPC_7109_00021 - linkFailureLOP_P............................................................................................................ 180 5.17.7 IPC_7110_00021 - linkFailureLOS.................................................................................................................181 5.17.8 IPC_7111_00021 - linkFailurePLM_P............................................................................................................ 182 5.17.9 IPC_7112_00021 - linkFailureRDI_L..............................................................................................................183 5.17.10 IPC_7113_00021 - linkFailureRDI_P........................................................................................................... 184 5.17.11 IPC_7156_00021 - restoreServiceFailure.................................................................................................... 185 5.18 GICCVirtualRouter alarms.................................................................................................................................... 186 5.18.1 IPC_7182_00022 - virtualGroupGICCRouterMembersFault.......................................................................... 187 5.19 IPC alarms............................................................................................................................................................ 188 5.19.1 IPC_7003_00004 - alarmDefFileCorrupt ....................................................................................................... 190 5.19.2 IPC_7004_00004 - alarmDefFileMissing........................................................................................................191 5.19.3 IPC_7013_00004 - ciccGiccConfigFileMissing.............................................................................................. 192 5.19.4 IPC_7014_00004 - cLIScriptFailed................................................................................................................ 195 5.19.5 IPC_7015_00004 - clockSourceFailure..........................................................................................................196 5.19.6 IPC_7023_00004 - configurationError............................................................................................................197 5.19.7 IPC_7025_00004 - coreFileGenerated.......................................................................................................... 198 5.19.8 IPC_7026_00004 - cpuUsageOverload......................................................................................................... 200 5.19.9 IPC_7028_00004 - dataAuditFailure.............................................................................................................. 201 5.19.10 IPC_7029_00004 - dBReplicationAuditFailure.............................................................................................202

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

Table of contents

vii

5.19.11 IPC_7030_00004 - degradeGroupMemberFault..........................................................................................205 5.19.12 IPC_7034_00004 - eventFloodConditionDetected.......................................................................................206 5.19.13 IPC_7067_00004 - failureGroupMemberFault............................................................................................. 207 5.19.14 IPC_7092_00004 - ftProcessError............................................................................................................... 208 5.19.15 IPC_7093_00004 - general_Handling_Error_Indication...............................................................................210 5.19.16 IPC_7095_00004 - hostProcessCommunicationFailure.............................................................................. 211 5.19.17 IPC_7096_00004 - hostProcessEnlistTimeout.............................................................................................213 5.19.18 IPC_7097_00004 - hostProcessFailure....................................................................................................... 215 5.19.19 IPC_7098_00004 - hostProcessRestartFailure............................................................................................ 216 5.19.20 IPC_7099_00004 - hostProcessRestartSuspended.....................................................................................217 5.19.21 IPC_7100_00004 - hostProcessTerminationFailure.................................................................................... 218 5.19.22 IPC_7101_00004 - iNITrunLevelTimeout.....................................................................................................220 5.19.23 IPC_7102_00004 - iNITterminatingTimeout................................................................................................. 222 5.19.24 IPC_7103_00004 - internal_Clock_Source_Disconnected.......................................................................... 224 5.19.25 IPC_7114_00004 - log100PercentFull......................................................................................................... 225 5.19.26 IPC_7115_00004 - log80PercentFull........................................................................................................... 226 5.19.27 IPC_7126_00004 - miscellaneous_Cause................................................................................................... 227 5.19.28 IPC_7132_00004 - oamStateControlFailure................................................................................................ 228 5.19.29 IPC_7144_00004 - perfMgr_DNMAP_INIT.................................................................................................. 230 5.19.30 IPC_7145_00004 - pmArchiveInitFailure..................................................................................................... 231 5.19.31 IPC_7146_00004 - pmCTDBImageFailure.................................................................................................. 232 5.19.32 IPC_7147_00004 - pmCTDBInitFailure........................................................................................................233 5.19.33 IPC_7148_00004 - primary_Clock_Source_Disconnected.......................................................................... 234 5.19.34 IPC_7159_00004 - secondSRSTCPEstFailure............................................................................................ 235 5.19.35 IPC_7164_00004 - suActivationFailure........................................................................................................236 5.19.36 IPC_7165_00004 - suApplyFailure.............................................................................................................. 239 5.19.37 IPC_7166_00004 - suBackoutFailure.......................................................................................................... 241 5.19.38 IPC_7167_00004 - suCommitFailure........................................................................................................... 244 5.19.39 IPC_7168_00004 - suDeApplyFailure..........................................................................................................246 5.19.40 IPC_7169_00004 - suDeleteFailure............................................................................................................. 248 5.19.41 IPC_7170_00004 - suDownloadFailure....................................................................................................... 250 5.19.42 IPC_7171_00004 - suFallbackFailure.......................................................................................................... 252 5.19.43 IPC_7172_00004 - suICCPartialUpdateFailure........................................................................................... 254 5.19.44 IPC_7173_00004 - suInfoSyncFailure......................................................................................................... 256 5.19.45 IPC_7174_00004 - suInstallFailure.............................................................................................................. 258

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

Table of contents

viii

5.19.46 IPC_7176_00004 - suStatePanicFailure...................................................................................................... 260 5.20 IuCS alarms.......................................................................................................................................................... 261 5.20.1 IPC_7154_00011 - remoteSubsystemOutOfService......................................................................................262 5.21 IuCSIP alarms.......................................................................................................................................................263 5.21.1 IPC_7121_00012 - m3uaLocalASFailure.......................................................................................................264 5.21.2 IPC_7122_00012 - m3uaRemoteASFailure...................................................................................................265 5.21.3 IPC_7154_00012 - remoteSubsystemOutOfService......................................................................................266 5.21.4 IPC_7186_00012 - overloadLevel1................................................................................................................267 5.21.5 IPC_7187_00012 - overloadLevel2................................................................................................................268 5.21.6 IPC_7188_00012 - overloadLevel3................................................................................................................269 5.22 PeerIPSP alarms.................................................................................................................................................. 270 5.22.1 IPC_7120_00030 - m3UAIPSPFailure........................................................................................................... 271 5.22.2 IPC_7158_00030 - sCTPAssociationFailure.................................................................................................. 272 5.22.3 IPC_7184_00030 - partialSCTPAssociationFailure....................................................................................... 273 5.22.4 IPC_7185_00030 - partialM3UAIPSPFailure................................................................................................. 274 5.23 PG alarms.............................................................................................................................................................275 5.23.1 IPC_7007_00045 - apsCriticalLineFailure......................................................................................................276 5.23.2 IPC_7008_00045 - apsCriticalProcessorFailure............................................................................................ 277 5.23.3 IPC_7009_00045 - apsMajorLineFailure........................................................................................................278 5.23.4 IPC_7010_00045 - apsMajorProcessorFailure.............................................................................................. 279 5.23.5 IPC_7011_00045 - apsMinorLineFailure........................................................................................................280 5.23.6 IPC_7012_00045 - apsMinorProcessorFailure.............................................................................................. 281 5.24 PSU alarms...........................................................................................................................................................282 5.24.1 IPC_7032_00039 - equipmentFailure............................................................................................................ 283 5.24.2 IPC_7133_00039 - overTemperature.............................................................................................................285 5.25 RoutingTableEntry alarms.................................................................................................................................... 286 5.25.1 IPC_7006_00005 - anextHopNotReachable.................................................................................................. 287 5.26 SB alarms............................................................................................................................................................. 288 5.26.1 IPC_7030_00040 - degradeGroupMemberFault............................................................................................289 5.26.2 IPC_7067_00040 - failureGroupMemberFault............................................................................................... 291 5.26.3 IPC_7117_00040 - lossOfPower....................................................................................................................293 5.26.4 IPC_7118_00040 - lossOfSanity.................................................................................................................... 294 5.26.5 IPC_7119_00040 - lostCommunication..........................................................................................................295 5.26.6 IPC_7123_00040 - maintenanceMode...........................................................................................................296 5.26.7 IPC_7131_00040 - notInstalled......................................................................................................................297

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

Table of contents

ix

5.26.8 IPC_7133_00040 - overTemperature.............................................................................................................298 5.27 SBBPEtherPort alarms......................................................................................................................................... 299 5.27.1 IPC_7104_00023 - linkFailure........................................................................................................................300 5.28 SBClan alarms......................................................................................................................................................301 5.28.1 IPC_7104_00024 - linkFailure........................................................................................................................302 5.29 SBProc alarms......................................................................................................................................................303 5.29.1 IPC_7001_00025 - acCommunicationFailure................................................................................................ 305 5.29.2 IPC_7022_00025 - componentMissing.......................................................................................................... 306 5.29.3 IPC_7026_00025 - cpuUsageOverload......................................................................................................... 307 5.29.4 IPC_7031_00025 - diskReadTimeExceeded................................................................................................. 308 5.29.5 IPC_7072_00025 - filesystem01Full.............................................................................................................. 309 5.29.6 IPC_7073_00025 - filesystem02Full.............................................................................................................. 310 5.29.7 IPC_7074_00025 - filesystem03Full.............................................................................................................. 311 5.29.8 IPC_7075_00025 - filesystem04Full.............................................................................................................. 312 5.29.9 IPC_7076_00025 - filesystem05Full.............................................................................................................. 313 5.29.10 IPC_7077_00025 - filesystem06Full............................................................................................................ 314 5.29.11 IPC_7078_00025 - filesystem07Full............................................................................................................ 315 5.29.12 IPC_7079_00025 - filesystem08Full............................................................................................................ 316 5.29.13 IPC_7080_00025 - filesystem09Full............................................................................................................ 317 5.29.14 IPC_7081_00025 - filesystem10Full............................................................................................................ 318 5.29.15 IPC_7082_00025 - filesystem11Full............................................................................................................ 319 5.29.16 IPC_7083_00025 - filesystem12Full............................................................................................................ 320 5.29.17 IPC_7084_00025 - filesystem13Full............................................................................................................ 321 5.29.18 IPC_7085_00025 - filesystem14Full............................................................................................................ 322 5.29.19 IPC_7086_00025 - filesystem15Full............................................................................................................ 323 5.29.20 IPC_7087_00025 - filesystem16Full............................................................................................................ 324 5.29.21 IPC_7088_00025 - fLXEV_CLAN_PARENT_FAIL...................................................................................... 325 5.29.22 IPC_7089_00025 - fLXEV_NODE_FAILING................................................................................................326 5.29.23 IPC_7090_00025 - fLXEV_NODE_NOTACTIVE......................................................................................... 327 5.29.24 IPC_7091_00025 - fLXEV_SMON_NOHBEAT............................................................................................ 328 5.29.25 IPC_7116_00025 - lossOfClockSourceSync................................................................................................329 5.29.26 IPC_7125_00025 - memoryUsageOverload................................................................................................ 330 5.29.27 IPC_7130_00025 - nodeFailure................................................................................................................... 331 5.29.28 IPC_7133_00025 - overTemperature...........................................................................................................332 5.29.29 IPC_7149_00025 - processFailure...............................................................................................................333

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

Table of contents

5.29.30 IPC_7150_00025 - processFailureApplication............................................................................................. 334 5.29.31 IPC_7157_00025 - rootLoginFailure............................................................................................................ 337 5.29.32 IPC_7160_00025 - shutdownTempReached............................................................................................... 338 5.29.33 IPC_7175_00025 - sULoginFailure.............................................................................................................. 339 5.29.34 IPC_7178_00025 - temperatureOffLimits.....................................................................................................340 5.29.35 IPC_7179_00025 - userLoginFailure........................................................................................................... 341 5.29.36 IPC_7180_00025 - virtualClusterFailure...................................................................................................... 342 5.29.37 IPC_7181_00025 - virtualClusterVirtualMachineFailure.............................................................................. 343 5.30 SS7Link alarms.....................................................................................................................................................344 5.30.1 IPC_7127_00031 - mtp3LinkDown................................................................................................................ 345 5.30.2 IPC_7128_00031 - mtp3LinkRemotelyBlocked..............................................................................................346 5.30.3 IPC_7151_00031 - qsaalLinkCongested........................................................................................................347 5.31 SS7LinkSet alarms............................................................................................................................................... 348 5.31.1 IPC_7024_00032 - congestionTowardsRemoteMTP3................................................................................... 349 5.31.2 IPC_7152_00032 - remoteMTP3Unreachable............................................................................................... 350 5.31.3 IPC_7153_00032 - remoteMTP3UserUnavailable......................................................................................... 351 5.32 SS7Stack alarms.................................................................................................................................................. 352 5.32.1 IPC_7129_00033 - nniStackFailure............................................................................................................... 353 5.33 SS7StackInst alarms............................................................................................................................................ 354 5.33.1 IPC_7129_00034 - nniStackFailure............................................................................................................... 355 5.34 OAM alarms..........................................................................................................................................................356 5.34.1 OAM_0130_00201 - Loss of supervision....................................................................................................... 357 5.34.2 OAM_0131_00201 - Supervision inhibited by operator..................................................................................358 5.34.3 OAM_0132_00201 - MIB number received from NE different from MIB number stored in the active view....359 5.34.4 OAM_0133_00201 - Unexpected NE ID........................................................................................................ 360

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

List of examples

xi

Example 1 - IPC_7030_00037 - degradeGroupMemberFault............................................................................ ......... 17 Example 2 - IPC_7033_00037 - escalatingRecovery......................................................................................... ......... 19 Example 3 - IPC_7067_00037 - failureGroupMemberFault.................................................................. ............. ......... 21 Example 4 - IPC_7017_00014 - communicationFailureESC1_2 ......................................................... ............. ......... 32 Example 5 - IPC_7018_00014 - communicationFailureESC1_21 ....................................................... ............. ......... 34 Example 6 - IPC_7019_00014 - communicationFailureESC2_2 ......................................................... ............. ......... 36 Example 7 - IPC_7020_00014 - communicationFailureESC2_21 ....................................................... ............. ......... 38 Example 8 - IPC_7177_00015 - switchover.......................................................................................... ............. ......... 56 Example 9 - IPC_7030_00041 - degradeGroupMemberFault............................................................................ ......... 61 Example 10 - IPC_7067_00041 - failureGroupMemberFault................................................................ ............. ......... 63 Example 11 - IPC_7030_00038 - degradeGroupMemberFault.......................................................................... ....... 131 Example 12 - IPC_7033_00038 - escalatingRecovery....................................................................................... ....... 133 Example 13 - IPC_7067_00038 - failureGroupMemberFault................................................................ ............. ....... 135 Example 14 - IPC_7017_00016 - communicationFailureESC1_2 ....................................................... ............. ....... 146 Example 15 - IPC_7018_00016 - communicationFailureESC1_21 ..................................................... ............. ....... 148 Example 16 - IPC_7019_00016 - communicationFailureESC2_2 ....................................................... ............. ....... 150 Example 17 - IPC_7020_00016 - communicationFailureESC2_21 ..................................................... ............. ....... 152 Example 18 - IPC_7013_00004 - ciccGiccConfigFileMissing .............................................................. ............. ....... 193 Example 19 - IPC_7025_00004 - coreFileGenerated........................................................................... ............. ....... 199 Example 20 - IPC_7029_00004 - dBReplicationAuditFailure ............................................................................ ....... 203 Example 21 - IPC_7092_00004 - ftProcessError.................................................................................. ............. ....... 209 Example 22 - IPC_7095_00004 - hostProcessCommunicationFailure ................................................ ............. ....... 212 Example 23 - IPC_7096_00004 - hostProcessEnlistTimeout............................................................... ............. ....... 214 Example 24 - IPC_7100_00004 - hostProcessTerminationFailure ...................................................... ............. ....... 219 Example 25 - IPC_7101_00004 - iNITrunLevelTimeout..................................................................................... ....... 221 Example 26 - IPC_7102_00004 - iNITterminatingTimeout................................................................................. ....... 223 Example 27 - IPC_7132_00004 - oamStateControlFailure................................................................... ............. ....... 229 Example 28 - IPC_7164_00004 - suActivationFailure........................................................................................ ....... 237 Example 29 - IPC_7165_00004 - suApplyFailure................................................................................. ............. ....... 240 Example 30 - IPC_7166_00004 - suBackoutFailure............................................................................. ............. ....... 242 Example 31 - IPC_7167_00004 - suCommitFailure........................................................................................... ....... 245 Example 32 - IPC_7168_00004 - suDeApplyFailure.......................................................................................... ....... 247 Example 33 - IPC_7169_00004 - suDeleteFailure............................................................................................. ....... 249 Example 34 - IPC_7170_00004 - suDownloadFailure.......................................................................... ............. ....... 251 Example 35 - IPC_7171_00004 - suFallbackFailure.......................................................................................... ....... 253 Example 36 - IPC_7172_00004 - suICCPartialUpdateFailure ............................................................. ............. ....... 255 Example 37 - IPC_7173_00004 - suInfoSyncFailure............................................................................ ............. ....... 257 Example 38 - IPC_7174_00004 - suInstallFailure.............................................................................................. ....... 259 Example 39 - IPC_7032_00039 - equipmentFailure............................................................................. ............. ....... 284 Example 40 - IPC_7030_00040 - degradeGroupMemberFault.......................................................................... ....... 290 Example 41 - IPC_7067_00040 - failureGroupMemberFault................................................................ ............. ....... 292

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

List of examples

xii

Example 42 - IPC_7150_00025 - processFailureApplication ............................................................................ ....... 335

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

About this publication


This publication contains the alarm descriptions and maintenance actions required for the IuCS Protocol Converter (IPC).

Applicability
This publication applies to the FMS2.1 System Release.

Audience
This publication is intended for operations and maintenance personnel, and all those who want to know the principles of the IPC corrective maintenance.

Prerequisites
It is recommended that readers also become familiar with the following ALTPs: Terminology (NN-20500-002) Alcatel-Lucent 9353 Management System for Femto - User Guide (NN-20500-208)

How this publication is organized


This document describes the IPC alarms raised by the equipment, then the alarms raised by the OAM.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

Femto Management Solution Collection Roadmap


For the Femto Management Solution documentation roadmap, see Alcatel-Lucent 9353 Management System for Femto - Introduction and Documentation Guide (NN-20500-177).

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

New in this release


The following details what is new in IPC Alarms Reference Guide for release FMS2.1.

Features
34360 Fault Management support of IPC (IuCS Protocol Converter) by FMS

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

How to use this publication


This part describes how to use this publication.

Introduction
This publication contains the alarm description and refers to corrective maintenance procedures applicable to the IPC. Network maintenance is based on graphical supervision of the network. It is also based on the identification and replacement of faulty items of equipment, using the alarms.

Description of an IPC alarm sheet


To display an IPC alarm help sheet, from the Alarm Manager window, right-click the alarm row and select the Selected Item Help command. For the other Alarm manager options, see Alcatel-Lucent 9353 Management System for Femto User Guide (NN-20500-208). An alarm sheet contains a description providing the short explanation of the alarm and a table detailing the following information: Alarm name: the specific problem of the alarm Alarm Code The alarm code, based on the faultCode field as displayed in the Alarm Record Viewer. See Alarm Code format. Object Class as it appears in the Alarm Manager window Equipment Type of the alarms. Alarm type which depends on the causes of the alarm. See Alarm Type - Probable Cause. Probable cause per alarm type. See Alarm Type - Probable Cause. Urgency of the maintenance action. See Severity. Description of how the service is affected. Possible origins of the alarm. List of recommended responses which correspond to corrective maintenance procedures (depend on the release).

Object Class Equipment Type Alarm Type Probable Cause Severity Impact Reason Remedial Action

Alarm Code format

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

The alarm code uses the faultCode field as seen in the alarm record details. It specifies the alarm type according to the following generic pattern: [Equipment type]_[Alarm code on 4 digits (0-9)]_[MO Object Id on 5 digits (0-9)] where "Equipment type" is BSG, IPC or OAM "Alarm code" is the alarm code of the equipment type "MO Object Id" is the Managed Object Id of the alarmed component.

Alarm Type - Probable Cause


Alarm Type communications: an alarm of this type is mainly associated with the procedures and/or processes required to convey information from one point to another. environment: an alarm of this type is principally associated with a condition relating to an enclosure in which the equipment resides. equipment: Probable Cause communicationsProtocolError communicationsSubsystemFailure configurationOrCustomizationError degradedSignal framingError lossOfSignal remoteNodeTransmissionError enclosureDoorOpen heatingOrVentilationOrCoolingSystemProblem temperatureUnacceptable adapterError equipmentMalfunction fileError inputDeviceError powerProblem receiveFailure timingProblem transmitterFailure communicationsProtocolError configurationOrCustomizationError corruptData outOfMemory softwareProgramError

an alarm of this type is mainly associated with an equipment fault. processing error: an alarm of this type is mainly associated with software or processing fault.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

Alarm Type quality of service: an alarm of this type is mainly associated with degradation in the quality of a service. Operator

Probable Cause corruptData queueSizeExceeded Receive Problem sfwrEnvironmentProblem thresholdCrossed underlyingResourceUnavailable versionMismatch versionMismatch

Severity
The Node B uses the following perceived severity: CRITICAL: indicates that a service affecting condition has occurred and an immediate corrective action is required. MAJOR: indicates that a service affecting condition has developed and an urgent corrective action is required. minor: indicates the existence of a non-service affecting fault condition and that corrective action will have to be taken in order to prevent a more serious fault. warning: indicates the detection of a potential or impending service-affecting fault, before any significant effects have been felt.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

IPC alarm descriptions


The IPC alarms are described in the following order: AC alarms Cabinet alarms CICC alarms CICCBPEtherPort alarms CICCProc alarms ESC alarms ESCBPEtherPort alarms ESCFAEtherPort alarms ESCProc alarms ExtAlmBox alarms FanTray alarms FBPShelf alarms GICC alarms GICCBPEtherPort alarms GICCFAEtherPort alarms GICCProc alarms GICCSTM1OC3Port alarms GICCVirtualRouter alarms IPC alarms IuCS alarms IuCSIP alarms PeerIPSP alarms PG alarms PSU alarms RoutingTableEntry alarms SB alarms SBBPEtherPort alarms SBClan alarms SBProc alarms SS7Link alarms SS7LinkSet alarms

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

SS7Stack alarms SS7StackInst alarms OAM alarms

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

5.1

AC alarms
The following alarms are generated by the Alarm Card. IPC_7016_00035 - communicationFailure IPC_7162_00035 - softwareVersionMismatch

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

10

5.1.1

IPC_7016_00035 - communicationFailure

Communication to the AC board has failed. communicationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7016_00035 IPC/Cabinet/FBPShelf/AC AC equipment processorProblem CRITICAL No blade management functions available. The AC board cannot be contacted through SNMP. 1. At the FMS, if the AC is initializing, ensure that the AC restores successfully. If the alarm is cleared, the procedure is completed. 2. At the IPC, check whether the AC is present. 3. At the IPC, check whether the AC is powered on. 4. At the FMS, check if there are ESC alarms and correct ESC failures. If the alarm is cleared, the procedure is completed. 5. At the IPC, reset the AC object. If the alarm is cleared, the procedure is completed. 6. Open a SSH session to the IPC. 7. At the IPC, lock the AC object. 8. At the IPC, replace the Alarm Card. 9. At the IPC, unlock the AC object. 10 If the problem persists, contact Alcatel-Lucent customer support. .

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

11

5.1.2

IPC_7162_00035 - softwareVersionMismatch

The software version running on this processor does not match the provisioned software version softwareVersionMismatch Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7162_00035 IPC/Cabinet/FBPShelf/AC AC processing error versionMismatch MAJOR Processor may not initialize properly. The software version running on this processor does not match the provisioned software version. 1. Install the provisioned software version on the processor. 2. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

12

5.2

Cabinet alarms
The following alarms are generated by the Cabinet. IPC_7071_00036 - fanOrCktBreakerFailure

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

13

5.2.1

IPC_7071_00036 - fanOrCktBreakerFailure

A fan or circuit breaker failure has occurred. fanOrCktBreakerFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7071_00036 IPC/Cabinet Cabinet equipment equipmentMalfunction MAJOR Heating and/or power problems. equipment malfunction 1. At the IPC, verify cabinet power breakers and fans are operating. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

14

5.2.2

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

15

5.3

CICC alarms
The following alarms are generated by the Common Intelligent Carrier Card (CICC). IPC_7030_00037 - degradeGroupMemberFault IPC_7033_00037 - escalatingRecovery IPC_7067_00037 - failureGroupMemberFault IPC_7117_00037 - lossOfPower IPC_7118_00037 - lossOfSanity IPC_7119_00037 - lostCommunication IPC_7123_00037 - maintenanceMode IPC_7131_00037 - notInstalled IPC_7133_00037 - overTemperature IPC_7134_00037 - overTemperatureInFlow IPC_7135_00037 - overTemperatureOutFlow

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

16

5.3.1

IPC_7030_00037 - degradeGroupMemberFault

A member of a degrade group faulted degradeGroupMemberFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7030_00037 IPC/Cabinet/FBPShelf/CICC CICC processing error underlyingResourceUnavailable MAJOR This should cause the leader to go degraded. Probable cause is underlying resource is unavailable. Perform the following procedure to clear the degradeGroupMemberFault (IPC_7030_00037) alarm.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

17

IPC_7030_00037 - degradeGroupMemberFault Remedial action Step Action

1. At the FMS, check for alarms on the objects: CICCProc 1 or CICCProc 2 CICCBPEtherPort

If there are alarms, perform the appropriate fault clearance procedure. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

18

5.3.2

IPC_7033_00037 - escalatingRecovery

The system is escalating recovery on this unit escalatingRecovery Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7033_00037 IPC/Cabinet/FBPShelf/CICC CICC equipment equipmentMalfunction MAJOR Voice and data handling traffic handling capacity decreased. The probable cause is equipment malfunction. Perform the following procedure to clear the escalatingRecovery (IPC_7033_00037) alarm.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

19

IPC_7033_00037 - escalatingRecovery Remedial action Step Action

1. If ... the additional alarm text indicates that the unit is being reset , then ... monitor and verify that the unit recovers to a normal state. monitor and verify that the unit recovers to a normal state. check for other alarms associated with this unit (CICC_lossOfPower, CICC_lossOfSanity, CICC_lostCommunication etc) and carry out the appropriate procedure. check for other alarms associated with this unit (CICC_lossOfPower, CICC_lossOfSanity, CICC_lostCommunication etc) and carry out the appropriate procedure. CICC_lossOfPower CICC_lossOfSanity CICC_lostCommunication

the additional alarm text indicates that the unit has been powered off,

2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

20

5.3.3

IPC_7067_00037 - failureGroupMemberFault

A member of a failure group faulted failureGroupMemberFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7067_00037 IPC/Cabinet/FBPShelf/CICC CICC processing error underlyingResourceUnavailable MAJOR The CICC is not operational. The system impact depends on the root cause of the alarm. A member of a failure group faulted. Perform the following procedure to clear the failureGroupMemberFault (IPC_7067_00037) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

21

IPC_7067_00037 - failureGroupMemberFault Remedial action Step Action

1. At the FMS, check for alarms on the object: CICCProc

If there are alarms, perform the appropriate fault clearance procedure. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

22

5.3.4

IPC_7117_00037 - lossOfPower

CICC board has lost power lossOfPower Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7117_00037 IPC/Cabinet/FBPShelf/CICC CICC equipment powerProblem MAJOR No direct system impact. CICC board has lost power. 1. At the FMS, reset the CICC object. If the alarm is cleared, the procedure is completed. 2. At the IPC, check whether the CICC is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 3. At the IPC, if the CICC is inserted in the correct slot, remove and re-insert the CICC. If the alarm is cleared, the procedure is completed. 4. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

23

5.3.5

IPC_7118_00037 - lossOfSanity

Unit has lost sanity or integrity lossOfSanity Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7118_00037 IPC/Cabinet/FBPShelf/CICC CICC equipment equipmentMalfunction MAJOR The CICC is inoperative and the capacity to handle voice and data traffic decreases. The unit has lost sanity or integrity. 1. At the FMS, check if a maintenanceMode alarm is active. 2. At the IPC, check whether the CICC is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the CICC object. If the alarm is cleared, the procedure is completed. 4. Open a SSH session to the IPC. 5. At the IPC, lock the CICC object. 6. At the IPC, replace the CICC. 7. At the IPC, unlock the CICC object. If the alarm is cleared, the procedure is completed. 8. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

24

5.3.6

IPC_7119_00037 - lostCommunication

AC board lost heartbeat communication to the CICC board lostCommunication Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7119_00037 IPC/Cabinet/FBPShelf/CICC CICC communications lossOfSignal MAJOR The CICC may operate but will likely not respond to some OA&M commands, especially those entered through the CLI. The probable cause is loss of signal. 1. At the IPC, check whether the CICC is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 2. At the IPC, if the CICC is inserted in the correct slot, remove and re-insert the CICC. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the CICC object. 4. Open a SSH session to the IPC. 5. At the IPC, lock the CICC object. 6. At the IPC, replace the CICC. 7. At the IPC, unlock the CICC object. 8. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

25

5.3.7

IPC_7123_00037 - maintenanceMode

CICC board is in maintenance mode maintenanceMode Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7123_00037 IPC/Cabinet/FBPShelf/CICC CICC processing error configurationOrCustomizationError warning Alarm Card recovery for this CICC is inhibited. The probable cause is configuration or customization error. 1. At the IPC, use the maintenance terminal to put the CICC back into active mode. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

26

5.3.8

IPC_7131_00037 - notInstalled

CICC board is not installed in shelf slot notInstalled Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7131_00037 IPC/Cabinet/FBPShelf/CICC CICC equipment equipmentMalfunction MAJOR The CICC is inoperative and the capacity to handle voice and data traffic decreases. The specified CICC is physically removed from the shelf or is not correctly inserted and the Alarm Card does not detect the CICC. 1. At the IPC, if the CICC is not inserted, insert the CICC into the correct slot . If the alarm is cleared, the procedure is completed. 2. At the IPC, if the CICC is inserted in the correct slot, remove and re-insert the CICC. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the CICC object. 4. If the problem persists, contact Alcatel-Lucent customer support.

Reason

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

27

5.3.9

IPC_7133_00037 - overTemperature

The temperature is above the specified limit overTemperature Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7133_00037 IPC/Cabinet/FBPShelf/CICC CICC environment temperatureUnacceptable MAJOR Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly by replacing the card. 6. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

28

5.3.10

IPC_7134_00037 - overTemperatureInFlow

The temperature is above the specified limit overTemperatureInFlow Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7134_00037 IPC/Cabinet/FBPShelf/CICC CICC environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly by replacing the card. 6. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

29

5.3.11

IPC_7135_00037 - overTemperatureOutFlow

The temperature is above the specified limit overTemperatureOutFlow Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7135_00037 IPC/Cabinet/FBPShelf/CICC CICC environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly by replacing the card. 6. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

30

5.4

CICCBPEtherPort alarms
The following alarms are generated by the CICC Ether port. IPC_7017_00014 - communicationFailureESC1_2 IPC_7018_00014 - communicationFailureESC1_21 IPC_7019_00014 - communicationFailureESC2_2 IPC_7020_00014 - communicationFailureESC2_21 IPC_7104_00014 - linkFailure IPC_7156_00014 - restoreServiceFailure

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

31

5.4.1

IPC_7017_00014 - communicationFailureESC1_2

Communication to Shelf=1, ESC=2 has failed communicationFailureESC1_2 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7017_00014 IPC/Cabinet/FBPShelf/CICC/CICCBPEtherPort CICCBPEtherPort communications communicationsSubsystemFailure MAJOR No direct impact, the alternate fabric is used to provide Ethernet communication. However the card is now vulnerable. Possible root causes: Remedial Action ESC hardware failure CICC hardware failure Cable failures

Reason

Perform the following procedure to clear the communicationFailureESC1_2 (IPC_7017_00014) alarm.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

32

IPC_7017_00014 - communicationFailureESC1_2 Remedial action Step Action

1. If ... only one CICC on shelf 1 (not on shelf 2) reports this alarm on its BPEtherPort 0, multiple shelf 1 GICCs and CICCs report this alarm on its BPEtherPort BPEtherPort 0, only shelf 2 (and not shelf 1) GICCs and CICCs report this alarm on its BPEtherPort 0, then ... replace the CICC. replace the CICC.

replace the ESC 2 on shelf 1. replace the ESC 2 on shelf 1.

check the vertical cables that connect ESC 2 on shelf 1 with ESC 2 on shelf 2 via ESC ports 22 and 23. check the vertical cables that connect ESC 2 on shelf 1 with ESC 2 on shelf 2 via ESC ports 22 and 23. check the diagonal cables that connect ESC 2 on shelf 1 with ESC 21 on shelf 2 via ESC ports 20 and 21. check the diagonal cables that connect ESC 2 on shelf 1 with ESC 21 on shelf 2 via ESC ports 20 and 21.

GICCs and CICCs report this alarm on its BPEtherPort 1 (and not on BPEtherPort 0),

2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

33

5.4.2

IPC_7018_00014 - communicationFailureESC1_21

Communication to Shelf=1, ESC=21 has failed communicationFailureESC1_21 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7018_00014 IPC/Cabinet/FBPShelf/CICC/CICCBPEtherPort CICCBPEtherPort communications communicationsSubsystemFailure MAJOR No direct impact, the alternate fabric is used to provide Ethernet communication. However the card is now vulnerable. Possible root causes: Remedial Action ESC hardware failure CICC hardware failure Cable failures

Reason

Perform the following procedure to clear the communicationFailureESC1_21 (IPC_7018_00014) alarm.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

34

IPC_7018_00014 - communicationFailureESC1_21 Remedial action Step Action

1. If ... only one CICC on shelf 1 (not on shelf 2) reports this alarm on its BPEtherPort 1, multiple shelf 1 GICCs and CICCs report this alarm on its BPEtherPort 1, only shelf 2 (not shelf 1) GICCs and CICCs report this alarm on its BPEtherPort 0, then ... replace the CICC. replace the CICC.

replace the ESC 21 on shelf 1. replace the ESC 21 on shelf 1.

check the vertical cables that connect ESC 21 on shelf 1 with ESC 21 on shelf 2 via ESC ports 22 and 23. check the vertical cables that connect ESC 21 on shelf 1 with ESC 21 on shelf 2 via ESC ports 22 and 23.

2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

35

5.4.3

IPC_7019_00014 - communicationFailureESC2_2

Communication to Shelf=2, ESC=2 has failed communicationFailureESC2_2 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7019_00014 IPC/Cabinet/FBPShelf/CICC/CICCBPEtherPort CICCBPEtherPort communications communicationsSubsystemFailure MAJOR No direct impact, the alternate fabric is used to provide Ethernet communication. However the card is now vulnerable. Possible root causes: Remedial Action ESC hardware failure CICC hardware failure Cable failures

Reason

Perform the following procedure to clear the communicationFailureESC2_2 (IPC_7019_00014) alarm.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

36

IPC_7019_00014 - communicationFailureESC2_2 Remedial action Step Action

1. If ... only one CICC on shelf 2 (not on shelf 1) reports this alarm on its BPEtherPort 0, multiple shelf 2 GICCs and CICCs report this alarm on its BPEtherPort BPEtherPort 0, only shelf 1 (and not shelf 2) GICCs and CICCs report this alarm on its BPEtherPort 0, then ... replace the CICC. replace the CICC.

replace the ESC 2 on shelf 2. replace the ESC 2 on shelf 2.

check the vertical cables that connect ESC 2 on shelf 1 with ESC 2 on shelf 2 via ESC ports 22 and 23. check the vertical cables that connect ESC 2 on shelf 1 with ESC 2 on shelf 2 via ESC ports 22 and 23.

2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

37

5.4.4

IPC_7020_00014 - communicationFailureESC2_21

Communication to Shelf=2, ESC=21 has failed communicationFailureESC2_21 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7020_00014 IPC/Cabinet/FBPShelf/CICC/CICCBPEtherPort CICCBPEtherPort communications communicationsSubsystemFailure MAJOR No direct impact, the alternate fabric is used to provide Ethernet communication. However the card is now vulnerable. Possible root causes: Remedial Action ESC hardware failure CICC hardware failure Cable failures.

Reason

Perform the following procedure to clear the communicationFailureESC2_21 (IPC_7020_00014) alarm.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

38

IPC_7020_00014 - communicationFailureESC2_21 Remedial action Step Action

1. If ... only one CICC on shelf 2 (not on shelf 1) reports this alarm on its BPEtherPort 1, multiple shelf 2 (not shelf 1) GICCs and CICCs report this alarm on its BPEtherPort 1, only shelf 1 (not shelf 2) GICCs and CICCs report this alarm on its BPEtherPort 1, then ... replace the CICC. replace the CICC.

replace the ESC 21 on shelf 2. replace the ESC 21 on shelf 2.

check the vertical cables that connect ESC 21 on shelf 1 with ESC 21 on shelf 2 via ESC ports 22 and 23. check the vertical cables that connect ESC 21 on shelf 1 with ESC 21 on shelf 2 via ESC ports 22 and 23. check the diagonal cables that connect ESC 2 on shelf 1 with ESC 21 on shelf 2 via ESC ports 20 and 21. check the diagonal cables that connect ESC 2 on shelf 1 with ESC 21 on shelf 2 via ESC ports 20 and 21.

GICCs and CICCs report this alarm on its BPEtherPort 0 (and not on BPEtherPort 1),

2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

39

5.4.5

IPC_7104_00014 - linkFailure

A failure occured on the backplane Ether link connection linkFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7104_00014 IPC/Cabinet/FBPShelf/CICC/CICCBPEtherPort CICCBPEtherPort communications communicationsSubsystemFailure CRITICAL No communication with CICC possible. The probable cause is backplane ethernet connection failure. 1. At the IPC, remove and re-insert the CICC. If the alarm is cleared, the procedure is completed. 2. At the IPC, replace the CICC. 3. At the IPC, check the backplane. 4. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

40

5.4.6

IPC_7156_00014 - restoreServiceFailure

Request to restore service has failed restoreServiceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7156_00014 IPC/Cabinet/FBPShelf/CICC/CICCBPEtherPort CICCBPEtherPort communications communicationsSubsystemFailure MAJOR CICC not available. The probable cause is maintenance action could not be performed due to underlying software failure. 1. Open a SSH session to the IPC. 2. At the IPC, lock and unlock the CICC object. If the alarm is cleared, the procedure is completed. 3. At the IPC, replace the CICC. 4. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

41

5.5

CICCProc alarms
The following alarms are generated by the CICC processor. IPC_7016_00015 - communicationFailure IPC_7021_00015 - communicationFailureLRM IPC_7023_00015 - configurationError IPC_7026_00015 - cpuUsageOverload IPC_7027_00015 - criticalSoftwareFailure IPC_7094_00015 - heartbeatFailure IPC_7124_00015 - memoryBlockError IPC_7125_00015 - memoryUsageOverload IPC_7155_00015 - resourceFailure IPC_7156_00015 - restoreServiceFailure IPC_7161_00015 - softwareAssertError IPC_7162_00015 - softwareVersionMismatch IPC_7163_00015 - standbyMateDown IPC_7177_00015 - switchover IPC_7183_00015 - vitalResourceFailure

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

42

5.5.1

IPC_7016_00015 - communicationFailure

Communication to the CICC processor has failed communicationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7016_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc equipment processorProblem CRITICAL CICC not available. The CICC board/processor can not be contacted via SNMP. 1. At the FMS, if the CICC is initializing, ensure that the CICC restores successfully. If the alarm is cleared, the procedure is completed. 2. At the IPC, check whether the CICC is present. 3. At the IPC, check whether the CICC is powered on. 4. At the FMS, check if there are ESC alarms and correct ESC failures. If the alarm is cleared, the procedure is completed. 5. At the FMS, reset the CICC object. If the alarm is cleared, the procedure is completed. 6. Open a SSH session to the IPC. 7. At the IPC, lock the CICC object. 8. At the IPC, replace the CICC. 9. At the IPC, unlock the CICC object. 10 If the problem persists, contact Alcatel-Lucent customer support. .

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

43

5.5.2

IPC_7021_00015 - communicationFailureLRM

Communication from FMS host processor to LRM on the CICC processor has failed communicationFailureLRM Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7021_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc communications communicationsSubsystemFailure CRITICAL CICC processor is unavailable for use by call processing. Possible root causes: Remedial Action Faulty hardware Bad software image Incorrect board installed An initialization is in progress

1. If alarm has not cleared within 15 minutes, check if other boards of the same type have successfully booted, if not, verify correct software is installed successfully. 2. Execute a manual reset on the associated CICC board. 3. At the IPC, replace the board if it has previously been in service or verify the correct board was installed. 4. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

44

5.5.3

IPC_7023_00015 - configurationError

A configuration data error has been detected configurationError Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7023_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc processing error configurationOrCustomizationError MAJOR Call processing may be affected. The data was either populated incorrectly initially, or a data change was made that introduced the error. 1. Contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

45

5.5.4

IPC_7026_00015 - cpuUsageOverload

The processor is in CPU usage overload cpuUsageOverload Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7026_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc quality of service resourceAtOrNearingCapacity MAJOR Reduced throughput on the CICC. System audits will be inhibited. The threshold for CPU usage overload of the processor on the CICC is exceeded. 1. At the FMS, reduce the processing load. 2. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

46

5.5.5

IPC_7027_00015 - criticalSoftwareFailure

A critical software problem has been detected criticalSoftwareFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7027_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc processing error softwareError CRITICAL Active CICC failure: all calls are dropped Standby CICC failure: no impact Probable cause is software error. 1. At the FMS, clear any other alarm that has been reported for the same CICC object. If the alarm is cleared, the procedure is completed. 2. If the fault is reported periodically by the same CICC, open a SSH session to the IPC. 3. At the IPC, lock the CICC object. 4. At the IPC, replace the CICC. 5. At the IPC, unlock the CICC object. 6. At the FMS, manually clear the alarm. 7. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

47

5.5.6

IPC_7094_00015 - heartbeatFailure

Heartbeat communication failure has been detected between peer instances heartbeatFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7094_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc processing error softwareError MAJOR A remote CICC probably performs a reset. The system impact depends on the type of the remote CICC card: Reason Active CICC: all calls are dropped Standby CICC: no impact

Possible root causes: The remote CICC performs a reset A GICC reports that it cannot communicate with a CICC A CCC reports that it cannot communicate with a GICC

Remedial Action

1. No action required. The error will be cleared automatically after the remote CICC has been recovered. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

48

5.5.7

IPC_7124_00015 - memoryBlockError

Memory block exhaustion (MBC or CBUFFER) has been detected memoryBlockError Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7124_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc quality of service resourceAtOrNearingCapacity MAJOR Establishment of new calls may be refused. As long as the memory block error is not cleared, the TPU application (C-plane) does not accept new contexts/calls on that CICC. High load distributed to the CICC causing memory block exhaustion. The high load can be an indication that the IPC is at its capacity or is nearing its capacity and requires replanning or re-engineering. 1. Ensure that all CICC objects are unlocked and enabled at the IPC. If the alarm is cleared, the procedure is completed. 2. A network replanning may be necessary in case the capacity of the IPC is reached. 3. If the problem persists, contact Alcatel-Lucent customer support.

Reason

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

49

5.5.8

IPC_7125_00015 - memoryUsageOverload

The processor is in memory usage overload memoryUsageOverload Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7125_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc quality of service resourceAtOrNearingCapacity MAJOR Memory overload can degrade the system performance. The threshold for memory usage overload of the processor on the CICC is exceeded. 1. Contact Alcatel-Lucent customer support.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

50

5.5.9

IPC_7155_00015 - resourceFailure

A non-vital underlying platform service is unavailable or out of service resourceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7155_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc processing error underlyingResourceUnavailable minor CICC is not available for call processing. Underlying resource unavailable caused by software or hardware failure of the CICCBPEtherPort. 1. Open a SSH session to the IPC. 2. At the IPC, lock the CICC object. 3. At the IPC, replace the CICC. 4. At the IPC, unlock the CICC object. 5. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

51

5.5.10

IPC_7156_00015 - restoreServiceFailure

Request to restore service has failed. restoreServiceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7156_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc communications communicationsSubsystemFailure MAJOR CICC processor is not available. The probable cause is maintenance action could not be performed due to underlying software failure. 1. At the FMS, reset the CICC object. 2. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

52

5.5.11

IPC_7161_00015 - softwareAssertError

A software assertion error has been detected softwareAssertError Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7161_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc processing error softwareError CRITICAL Active CICC failure: all calls are dropped Standby CICC failure: no impact The probable cause is software error. 1. At the FMS, perform a reset of the CICC object to reboot the CICC. 2. At the FMS, manually clear the alarm. 3. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

53

5.5.12

IPC_7162_00015 - softwareVersionMismatch

The software version running on this processor does not match the provisioned software version softwareVersionMismatch Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7162_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc processing error versionMismatch MAJOR Processor may not initialize properly. version mismatch 1. Install the provisioned software version on the processor. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

54

5.5.13

IPC_7163_00015 - standbyMateDown

The associated standby mate processor is unavailable. standbyMateDown Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7163_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc equipment processorProblem MAJOR No redundant CICC processor available. processor problem 1. At the FMS, check the status of the CICC processor. 2. At the FMS, check the status of the ATM link. 3. At theFMS, reset the standby CICC object. 4. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

55

5.5.14

IPC_7177_00015 - switchover

A switchover to the standby Signal Processor (SP) has occurred switchover Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7177_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc processing error underlyingResourceUnavailable MAJOR When the switchover to the standby Signaling Processor occurs, all calls are dropped. When the switchover is completed, calls can be established again. If the failing Signaling Processor remains disabled after the failure, standby Signaling Processor is no longer available. The standby Signaling Processor detected that the active Signaling Processor has failed and a switchover was triggered. Perform the following procedure to clear the switchover (IPC_7177_00015) alarm.

Reason

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

56

IPC_7177_00015 - switchover Remedial action Step Action

1. At the FMS, check whether the switchover was successful and SS7 stack is started on the new Signaling Processor. Check whether calls can be established again. 2. At the FMS, check the state of the Signaling Processor that failed: If ... The state is unlocked and enabled, then ... the Signaling Processor that failed has recovered successfullythe procedure is completed. the Signaling Processor that failed has recovered successfullythe procedure is completed. the Signaling Processor that failed has recovered successfully the Signaling Processor that failed has recovered successfully the procedure is completed. the procedure is completed. replace the CICC that hosts the Signaling Processor:Open a SSH session to the IPC, lock the CICC objectAt the IPC, replace the CICC.At the FMS, reset the CICC objectAt the IPC, unlock the CICC object replace the CICC that hosts the Signaling Processor:Open a SSH session to the IPC, lock the CICC objectAt the IPC, replace the CICC.At the FMS, reset the CICC objectAt the IPC, unlock the CICC object replace the CICC that hosts the Signaling Processor: Open a SSH session to the IPC, lock the CICC object Open a SSH session to the IPC, lock the CICC object At the IPC, replace the CICC. At the IPC, replace the CICC. At the FMS, reset the CICC object At the FMS, reset the CICC object At the IPC, unlock the CICC object At the IPC, unlock the CICC object

The state is NOT unlocked and enabled,

3. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

57

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

58

5.5.15

IPC_7183_00015 - vitalResourceFailure

A vital underlying platform service is unavailable or out of service. vitalResourceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7183_00015 IPC/Cabinet/FBPShelf/CICC/CICCProc CICCProc processing error underlyingResourceUnavailable CRITICAL The CICC is not available for call processing. An underlying vital resource is unavailable caused by software or hardware failure of the CICCBPEtherPort. 1. Open a SSH session to the IPC. 2. At the IPC, lock the CICC object. 3. At the IPC, replace the CICC. 4. At the IPC, unlock the CICC object. 5. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

59

5.6

ESC alarms
The following alarms are generated by the Ethernet Switching Card (ESC). IPC_7030_00041 - degradeGroupMemberFault IPC_7067_00041 - failureGroupMemberFault IPC_7117_00041 - lossOfPower IPC_7118_00041 - lossOfSanity IPC_7119_00041 - lostCommunication IPC_7123_00041 - maintenanceMode IPC_7131_00041 - notInstalled IPC_7133_00041 - overTemperature IPC_7162_00041 - softwareVersionMismatch

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

60

5.6.1

IPC_7030_00041 - degradeGroupMemberFault

A member of a degrade group faulted degradeGroupMemberFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7030_00041 IPC/Cabinet/FBPShelf/ESC ESC processing error underlyingResourceUnavailable MAJOR The ESC is considered degraded. The system impact depends on the root cause of the alarm. underlying resource unavailable Perform the following procedure to clear the degradeGroupMemberFault (IPC_7030_00041) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

61

IPC_7030_00041 - degradeGroupMemberFault Remedial action Step Action

1. At the FMS, check for alarms on the objects: ESCBPEtherPort ESCFAEtherPort

If there are alarms, perform the appropriate fault clearance procedure. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

62

5.6.2

IPC_7067_00041 - failureGroupMemberFault

A member of a failure group faulted failureGroupMemberFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7067_00041 IPC/Cabinet/FBPShelf/ESC ESC processing error underlyingResourceUnavailable MAJOR The ESC is not operational. The system impact depends on the root cause of the alarm. Underlying resource unavailable Perform the following procedure to clear the failureGroupMemberFault (IPC_7067_00041) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

63

IPC_7067_00041 - failureGroupMemberFault Remedial action Step Action

1. At the OFMS, check for alarms on the object: ESCProc

If there are alarms, perform the appropriate fault clearance procedure. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

64

5.6.3

IPC_7117_00041 - lossOfPower

ESC board has lost power lossOfPower Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7117_00041 IPC/Cabinet/FBPShelf/ESC ESC equipment powerProblem CRITICAL This ESC can provide internal and external ethernet connectivity. The redundant ESC will take over the switching tasks. No power available at ESC. 1. At the IPC, check whether the ESC is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 2. At the IPC, if the ESC is inserted in the correct slot, remove and reinsert the ESC. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the ESC object. 4. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

65

5.6.4

IPC_7118_00041 - lossOfSanity

Unit has lost sanity or integrity lossOfSanity Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7118_00041 IPC/Cabinet/FBPShelf/ESC ESC equipment equipmentMalfunction CRITICAL None, the redundant ESC will take over the switching tasks. Equipment malfunction. 1. At the FMS, check if a maintenanceMode alarm is active. 2. At the IPC, check whether the ESC is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the ESC object. If the alarm is cleared, the procedure is completed. 4. Open a SSH session to the IPC. 5. At the IPC, lock the ESC object. 6. At the IPC, replace the ESC. 7. At the IPC, unlock the ESC object. If the alarm is cleared, the procedure is completed. 8. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

66

5.6.5

IPC_7119_00041 - lostCommunication

AC board lost heartbeat communication to the ESC board lostCommunication Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7119_00041 IPC/Cabinet/FBPShelf/ESC ESC communications lossOfSignal MAJOR None Loss of signal 1. At the IPC, check whether the ESC is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 2. At the IPC, if the ESC is inserted in the correct slot, remove and reinsert the ESC. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the ESC. 4. Open a SSH session to the IPC. 5. At the IPC, lock the ESC object. 6. At the IPC, replace the ESC. 7. At the IPC, unlock the ESC object. 8. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

67

5.6.6

IPC_7123_00041 - maintenanceMode

ESC board is in maintenance mode. maintenanceMode Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7123_00041 IPC/Cabinet/FBPShelf/ESC ESC processing error configurationOrCustomizationError warning Alarm Card recovery for the ESC is inhibited. Configuration or customization error 1. At the IPC, use the local maintenance terminal to put the ESC back into active mode. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

68

5.6.7

IPC_7131_00041 - notInstalled

ESC board is not installed in shelf slot. notInstalled Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7131_00041 IPC/Cabinet/FBPShelf/ESC ESC equipment equipmentMalfunction MAJOR None, the other ESC takes over. The specified ESC is physically removed from the shelf or is not correctly inserted and the Alarm Card does not detect the ESC. 1. At the IPC, if the ESC is not inserted, insert the ESC into the correct slot. If the alarm is cleared, the procedure is completed. 2. At the IPC, if the ESC is inserted in the correct slot, remove and reinsert the ESC. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the ESC object. 4. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

69

5.6.8

IPC_7133_00041 - overTemperature

The temperature is above the specified limit overTemperature Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7133_00041 IPC/Cabinet/FBPShelf/ESC ESC environment temperatureUnacceptable MAJOR Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly by replacing the card. 6. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

70

5.6.9

IPC_7162_00041 - softwareVersionMismatch

The software version running on this processor does not match the provisioned software version softwareVersionMismatch Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7162_00041 IPC/Cabinet/FBPShelf/ESC ESC processing error versionMismatch MAJOR

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

71

5.7

ESCBPEtherPort alarms
The following alarms are generated by the Ethernet Switching Card BackPlane Ethernet port. IPC_7104_00026 - linkFailure

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

72

5.7.1

IPC_7104_00026 - linkFailure

A failure has occurred on the backplane Ethernet link connection linkFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7104_00026 IPC/Cabinet/FBPShelf/ESC/ESCBPEtherPort ESCBPEtherPort communications communicationsSubsystemFailure MAJOR None, the other ESC takes over. Backplane ethernet connection failure, and communications subsystem failure 1. At the IPC, remove and re-insert the ESC. If the alarm is cleared, the procedure is completed. 2. At the IPC, replace the ESC. 3. At the IPC, check the backplane. 4. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

73

5.8

ESCFAEtherPort alarms
The following alarms are generated by the Ethernet Switching Card Front Access Ethernet port. IPC_7104_00027 - linkFailure

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

74

5.8.1

IPC_7104_00027 - linkFailure

A failure has occurred on the front access Ethernet link connection linkFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7104_00027 IPC/Cabinet/FBPShelf/ESC/ESCFAEtherPort ESCFAEtherPort communications communicationsSubsystemFailure MAJOR Communication over the Ethernet link connections fails. Front plane Ethernet connection failure 1. At the IPC, check the physical Ethernet link connection on the frontplate. If the alarm is cleared, the procedure is completed. 2. At the IPC, replace the ESC. 3. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

75

5.9

ESCProc alarms
The following alarms are generated by the Ethernet Switching Card processor. IPC_7016_00028 - communicationFailure

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

76

5.9.1

IPC_7016_00028 - communicationFailure

Communication to the ESC board has failed communicationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7016_00028 IPC/Cabinet/FBPShelf/ESC/ESCProc ESCProc equipment processorProblem CRITICAL No internal and external Ethernet connectivity is provided by the ESC. processor problem 1. At the FMS, if the ESC is initializing, ensure that the ESC restores successfully. If the alarm is cleared, procedure is completed. 2. At the IPC, check whether the ESC is present. 3. At the IPC, check whether the ESC is powered on. 4. At the IPC, reset the ESC. If the alarm is cleared, procedure is completed. 5. Open a SSH session to the IPC. 6. At the IPC, lock the ESC object. 7. At the IPC, replace the ESC. 8. At the IPC, unlock the ESC object. 9. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

77

5.10

ExtAlmBox alarms
The following alarms are generated by the ExtAlmBox. IPC_7016_00042 - communicationFailure IPC_7035_00042 - externalAlarmPort1 IPC_7036_00042 - externalAlarmPort10 IPC_7037_00042 - externalAlarmPort11 IPC_7038_00042 - externalAlarmPort12 IPC_7039_00042 - externalAlarmPort13 IPC_7040_00042 - externalAlarmPort14 IPC_7041_00042 - externalAlarmPort15 IPC_7042_00042 - externalAlarmPort16 IPC_7043_00042 - externalAlarmPort17 IPC_7044_00042 - externalAlarmPort18 IPC_7045_00042 - externalAlarmPort19 IPC_7046_00042 - externalAlarmPort2 IPC_7047_00042 - externalAlarmPort20 IPC_7048_00042 - externalAlarmPort21 IPC_7049_00042 - externalAlarmPort22 IPC_7050_00042 - externalAlarmPort23 IPC_7051_00042 - externalAlarmPort24 IPC_7052_00042 - externalAlarmPort25 IPC_7053_00042 - externalAlarmPort26 IPC_7054_00042 - externalAlarmPort27 IPC_7055_00042 - externalAlarmPort28 IPC_7056_00042 - externalAlarmPort29 IPC_7057_00042 - externalAlarmPort3 IPC_7058_00042 - externalAlarmPort30 IPC_7059_00042 - externalAlarmPort31 IPC_7060_00042 - externalAlarmPort32 IPC_7061_00042 - externalAlarmPort4 IPC_7062_00042 - externalAlarmPort5 IPC_7063_00042 - externalAlarmPort6 IPC_7064_00042 - externalAlarmPort7

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

78

IPC_7065_00042 - externalAlarmPort8 IPC_7066_00042 - externalAlarmPort9

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

79

5.10.1

IPC_7016_00042 - communicationFailure

A communication failure to the External Alarm Box has occurred communicationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7016_00042 IPC/ExtAlmBox ExtAlmBox equipment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

80

5.10.2

IPC_7035_00042 - externalAlarmPort1

An external alarm was generated on port 1 externalAlarmPort1 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7035_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

81

5.10.3

IPC_7036_00042 - externalAlarmPort10

An external alarm was generated on port 10 externalAlarmPort10 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7036_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

82

5.10.4

IPC_7037_00042 - externalAlarmPort11

An external alarm was generated on port 11 externalAlarmPort11 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7037_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

83

5.10.5

IPC_7038_00042 - externalAlarmPort12

An external alarm was generated on port 12 externalAlarmPort12 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7038_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

84

5.10.6

IPC_7039_00042 - externalAlarmPort13

An external alarm was generated on port 13 externalAlarmPort13 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7039_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

85

5.10.7

IPC_7040_00042 - externalAlarmPort14

An external alarm was generated on port 14 externalAlarmPort14 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7040_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

86

5.10.8

IPC_7041_00042 - externalAlarmPort15

An external alarm was generated on port 15 externalAlarmPort15 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7041_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

87

5.10.9

IPC_7042_00042 - externalAlarmPort16

An external alarm was generated on port 16 externalAlarmPort16 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7042_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

88

5.10.10

IPC_7043_00042 - externalAlarmPort17

An external alarm was generated on port 17 externalAlarmPort17 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7043_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

89

5.10.11

IPC_7044_00042 - externalAlarmPort18

An external alarm was generated on port 18 externalAlarmPort18 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7044_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

90

5.10.12

IPC_7045_00042 - externalAlarmPort19

An external alarm was generated on port 19 externalAlarmPort19 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7045_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

91

5.10.13

IPC_7046_00042 - externalAlarmPort2

An external alarm was generated on port 2 externalAlarmPort2 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7046_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

92

5.10.14

IPC_7047_00042 - externalAlarmPort20

An external alarm was generated on port 20 externalAlarmPort20 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7047_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

93

5.10.15

IPC_7048_00042 - externalAlarmPort21

An external alarm was generated on port 21 externalAlarmPort21 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7048_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

94

5.10.16

IPC_7049_00042 - externalAlarmPort22

An external alarm was generated on port 22 externalAlarmPort22 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7049_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

95

5.10.17

IPC_7050_00042 - externalAlarmPort23

An external alarm was generated on port 23 externalAlarmPort23 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7050_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

96

5.10.18

IPC_7051_00042 - externalAlarmPort24

An external alarm was generated on port 24 externalAlarmPort24 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7051_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

97

5.10.19

IPC_7052_00042 - externalAlarmPort25

An external alarm was generated on port 25 externalAlarmPort25 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7052_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

98

5.10.20

IPC_7053_00042 - externalAlarmPort26

An external alarm was generated on port 26 externalAlarmPort26 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7053_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

99

5.10.21

IPC_7054_00042 - externalAlarmPort27

An external alarm was generated on port 27 externalAlarmPort27 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7054_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

100

5.10.22

IPC_7055_00042 - externalAlarmPort28

An external alarm was generated on port 28 externalAlarmPort28 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7055_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

101

5.10.23

IPC_7056_00042 - externalAlarmPort29

An external alarm was generated on port 29 externalAlarmPort29 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7056_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

102

5.10.24

IPC_7057_00042 - externalAlarmPort3

An external alarm was generated on port 3 externalAlarmPort3 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7057_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

103

5.10.25

IPC_7058_00042 - externalAlarmPort30

An external alarm was generated on port 30 externalAlarmPort30 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7058_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

104

5.10.26

IPC_7059_00042 - externalAlarmPort31

An external alarm was generated on port 31 externalAlarmPort31 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7059_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

105

5.10.27

IPC_7060_00042 - externalAlarmPort32

An external alarm was generated on port 32 externalAlarmPort32 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7060_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

106

5.10.28

IPC_7061_00042 - externalAlarmPort4

An external alarm was generated on port 4 externalAlarmPort4 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7061_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

107

5.10.29

IPC_7062_00042 - externalAlarmPort5

An external alarm was generated on port 5 externalAlarmPort5 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7062_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

108

5.10.30

IPC_7063_00042 - externalAlarmPort6

An external alarm was generated on port 6 externalAlarmPort6 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7063_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

109

5.10.31

IPC_7064_00042 - externalAlarmPort7

An external alarm was generated on port 7 externalAlarmPort7 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7064_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

110

5.10.32

IPC_7065_00042 - externalAlarmPort8

An external alarm was generated on port 8 externalAlarmPort8 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7065_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

111

5.10.33

IPC_7066_00042 - externalAlarmPort9

An external alarm was generated on port 9 externalAlarmPort9 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7066_00042 IPC/ExtAlmBox ExtAlmBox environment equipmentMalfunction CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

112

5.11

FanTray alarms
The following alarms are generated by the FanTray. IPC_7068_00044 - fan1Failure IPC_7069_00044 - fan2Failure IPC_7070_00044 - fan3Failure IPC_7131_00044 - notInstalled

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

113

5.11.1

IPC_7068_00044 - fan1Failure

Fan #1 is not rotating at the proper speed fan1Failure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7068_00044 IPC/Cabinet/FBPShelf/FanTray FanTray environment equipmentMalfunction MAJOR No or insufficient cooling facilities available. This can lead to hardware failures because of high temperatures. Equipment malfunction 1. At the FMS, check the status of the fan tray. 2. At the IPC, inspect the fan tray and remove any object that obstructs the rotation of the fan. If the alarm is cleared, the procedure is completed. 3. At the IPC, replace the fan tray. If the alarm is cleared, the procedure is completed. 4. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

114

5.11.2

IPC_7069_00044 - fan2Failure

Fan #2 is not rotating at the proper speed fan2Failure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7069_00044 IPC/Cabinet/FBPShelf/FanTray FanTray environment equipmentMalfunction MAJOR No or insufficient cooling facilities available. This can lead to hardware failures because of high temperatures. Equipment malfunction 1. At the FMS, check the status of the fan tray. 2. At the IPC, inspect the fan tray and remove any object that obstructs the rotation of the fan. If the alarm is cleared, the procedure is completed. 3. At the IPC, replace the fan tray. If the alarm is cleared, the procedure is completed. 4. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

115

5.11.3

IPC_7070_00044 - fan3Failure

Fan #3 is not rotating at the proper speed fan3Failure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7070_00044 IPC/Cabinet/FBPShelf/FanTray FanTray environment equipmentMalfunction MAJOR No or insufficient cooling facilities available. This can lead to hardware failures because of high temperatures. Equipment malfunction 1. At the FMS, check the status of fan tray. 2. At the IPC, inspect the fan tray and remove any object that obstructs the rotation of the fan. If the alarm is cleared, the procedure is completed. 3. At the IPC, replace the fan tray. If the alarm is cleared, the procedure is completed. 4. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

116

5.11.4

IPC_7131_00044 - notInstalled

Unit is not installed in shelf notInstalled Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7131_00044 IPC/Cabinet/FBPShelf/FanTray FanTray equipment equipmentMalfunction CRITICAL No cooling facilities are available. Fan tray is not installed 1. At the IPC, install a fan tray unit. 2. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

117

5.12

FBPShelf alarms
The following alarms are generated by the FBP shelf. IPC_7133_00043 - overTemperature IPC_7136_00043 - overTemperatureSensor1 IPC_7137_00043 - overTemperatureSensor2 IPC_7138_00043 - overTemperatureSensor3 IPC_7139_00043 - overTemperatureSensor4 IPC_7140_00043 - overTemperatureSensor5 IPC_7141_00043 - overTemperatureSensor6 IPC_7142_00043 - overTemperatureSensor7 IPC_7143_00043 - overTemperatureSensor8

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

118

5.12.1

IPC_7133_00043 - overTemperature

The temperature is above the specified limitv overTemperature Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7133_00043 IPC/Cabinet/FBPShelf FBPShelf environment temperatureUnacceptable minor Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated overTemperature alarms on any individual cards using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 3. At the IPC, check for obstructions in the air flow pathways. 4. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 5. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 6. At the IPC, verify that the temperature sensors are functioning correctly. 7. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

119

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

120

5.12.2

IPC_7136_00043 - overTemperatureSensor1

The temperature is above the specified limit overTemperatureSensor1 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7136_00043 IPC/Cabinet/FBPShelf FBPShelf environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly. 6. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

121

5.12.3

IPC_7137_00043 - overTemperatureSensor2

The temperature is above the specified limit overTemperatureSensor2 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7137_00043 IPC/Cabinet/FBPShelf FBPShelf environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly. 6. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

122

5.12.4

IPC_7138_00043 - overTemperatureSensor3

The temperature is above the specified limit overTemperatureSensor3 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7138_00043 IPC/Cabinet/FBPShelf FBPShelf environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly. 6. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

123

5.12.5

IPC_7139_00043 - overTemperatureSensor4

The temperature is above the specified limit overTemperatureSensor4 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7139_00043 IPC/Cabinet/FBPShelf FBPShelf environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly. 6. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

124

5.12.6

IPC_7140_00043 - overTemperatureSensor5

The temperature is above the specified limit overTemperatureSensor5 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7140_00043 IPC/Cabinet/FBPShelf FBPShelf environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly. 6. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

125

5.12.7

IPC_7141_00043 - overTemperatureSensor6

The temperature is above the specified limit overTemperatureSensor6 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7141_00043 IPC/Cabinet/FBPShelf FBPShelf environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly. 6. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

126

5.12.8

IPC_7142_00043 - overTemperatureSensor7

The temperature is above the specified limit overTemperatureSensor7 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7142_00043 IPC/Cabinet/FBPShelf FBPShelf environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly. 6. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

127

5.12.9

IPC_7143_00043 - overTemperatureSensor8

The temperature is above the specified limit overTemperatureSensor8 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7143_00043 IPC/Cabinet/FBPShelf FBPShelf environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly. 6. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

128

5.13

GICC alarms
The following alarms are generated by the Gateway Intelligent Carrier Card (GICC). IPC_7002_00038 - ahardwareModelDifferentFromConfigured IPC_7030_00038 - degradeGroupMemberFault IPC_7033_00038 - escalatingRecovery IPC_7067_00038 - failureGroupMemberFault IPC_7117_00038 - lossOfPower IPC_7118_00038 - lossOfSanity IPC_7119_00038 - lostCommunication IPC_7123_00038 - maintenanceMode IPC_7131_00038 - notInstalled IPC_7133_00038 - overTemperature IPC_7134_00038 - overTemperatureInFlow IPC_7135_00038 - overTemperatureOutFlow

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

129

5.13.1

IPC_7002_00038 - ahardwareModelDifferentFromConfigured

The hardware model is different from the configured ahardwareModelDifferentFromConfigured Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7002_00038 IPC/Cabinet/FBPShelf/GICC GICC communications versionMismatch CRITICAL This alarm needs to be cleared manually. version mismatch 1. Check if the correct GICC hardware (GICC 1.1 or GICC 1.0) is installed in the proper slots.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

130

5.13.2

IPC_7030_00038 - degradeGroupMemberFault

A member of a degrade group faulted degradeGroupMemberFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7030_00038 IPC/Cabinet/FBPShelf/GICC GICC processing error underlyingResourceUnavailable MAJOR The GICC is considered degraded. The system impact depends on the root cause of the alarm. Underlying resource unavailable Perform the following procedure to clear the degradeGroupMemberFault (IPC_7030_00038) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

131

IPC_7030_00038 - degradeGroupMemberFault Remedial action Step Action

1. At the FMS, check for alarms on the objects: GICCSTM1OC3Port GICCFAEtherPort GICCBPEtherPort

If there are alarms, perform the appropriate fault clearance procedure. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

132

5.13.3

IPC_7033_00038 - escalatingRecovery

The system is escalating recovery on this unit escalatingRecovery Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7033_00038 IPC/Cabinet/FBPShelf/GICC GICC equipment equipmentMalfunction MAJOR None. The other GICC will take over The GICC is not responding to recovery due to software or hardware failure Perform the following procedure to clear the escalatingRecovery (IPC_7033_00038) alarm.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

133

IPC_7033_00038 - escalatingRecovery Remedial action Step Action

1. If ... the additional alarm text indicates that the unit is being reset , then ... monitor and verify that the unit recovers to a normal state. monitor and verify that the unit recovers to a normal state. check for other alarms associated with this unit (GICC_lossOfPower, GICC_lossOfSanity, GICC_lostCommunication etc) and carry out the appropriate procedure. check for other alarms associated with this unit (GICC_lossOfPower, GICC_lossOfSanity, GICC_lostCommunication etc) and carry out the appropriate procedure. GICC_lossOfPower GICC_lossOfSanity GICC_lostCommunication

the additional alarm text indicates that the unit has been powered off,

2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

134

5.13.4

IPC_7067_00038 - failureGroupMemberFault

A member of a failure group faulted failureGroupMemberFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7067_00038 IPC/Cabinet/FBPShelf/GICC GICC processing error underlyingResourceUnavailable MAJOR The GICC is not operational. The system impact depends on the root cause of the alarm. Underlying resource unavailable Perform the following procedure to clear the failureGroupMemberFault (IPC_7067_00038) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

135

IPC_7067_00038 - failureGroupMemberFault Remedial action Step Action

1. At the FMS, check for alarms on the object: GICCProc

If there are alarms, perform the appropriate fault clearance procedure. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

136

5.13.5

IPC_7117_00038 - lossOfPower

GICC board has lost power lossOfPower Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7117_00038 IPC/Cabinet/FBPShelf/GICC GICC equipment powerProblem MAJOR None. Power problem 1. At the FMS, reset the GICC object. If the alarm is cleared, the procedure is completed. 2. At the IPC, check whether the GICC is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 3. At the IPC, if the GICC is inserted in the correct slot, remove and re-insert the GICC. If the alarm is cleared, the procedure is completed. 4. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

137

5.13.6

IPC_7118_00038 - lossOfSanity

Unit has lost sanity or integrity lossOfSanity Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7118_00038 IPC/Cabinet/FBPShelf/GICC GICC equipment equipmentMalfunction MAJOR None. Equipment malfunction 1. At the FMS, check if a maintenanceMode alarm is active. 2. At the IPC, check whether the GICC is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the GICC object. If the alarm is cleared, the procedure is completed. 4. Open a SSH session to the IPC. 5. At the IPC, lock the GICC object. 6. At the IPC, replace the GICC. 7. At the IPC, unlock the GICC object. If the alarm is cleared, the procedure is completed. 8. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

138

5.13.7

IPC_7119_00038 - lostCommunication

AC board lost heartbeat communication to the GICC board lostCommunication Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7119_00038 IPC/Cabinet/FBPShelf/GICC GICC communications lossOfSignal MAJOR The GICC may operate but will likely not respond to some OA&M commands, especially those entered through the CLI. loss of signal 1. At the IPC, check whether the GICC is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 2. At the IPC, if the GICC is inserted in the correct slot, remove and re-insert the GICC. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the GICC object. 4. Open a SSH session to the IPC. 5. At the IPC, lock the GICC object. 6. At the IPC, replace the GICC. 7. At the IPC, unlock the GICC object. 8. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

139

5.13.8

IPC_7123_00038 - maintenanceMode

GICC board is in maintenance mode maintenanceMode Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7123_00038 IPC/Cabinet/FBPShelf/GICC GICC processing error configurationOrCustomizationError warning Alarm Card recovery for this GICC is inhibited. Configuration or customization error 1. At the IPC, use the maintenance terminal to put the GICC back into active mode. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

140

5.13.9

IPC_7131_00038 - notInstalled

GICC board is not installed in shelf slot notInstalled Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7131_00038 IPC/Cabinet/FBPShelf/GICC GICC equipment equipmentMalfunction MAJOR None. The specified GICC is physically removed from the shelf or is not correctly inserted and the Alarm Card does not detect the GICC. 1. At the IPC, if the GICC is not inserted, insert the GICC into the correct slot. If the alarm is cleared, the procedure is completed. 2. At the IPC, if the GICC is inserted in the correct slot, remove and re-insert the GICC. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the GICC object. 4. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

141

5.13.10

IPC_7133_00038 - overTemperature

The temperature is above the specified limit overTemperature Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7133_00038 IPC/Cabinet/FBPShelf/GICC GICC environment temperatureUnacceptable MAJOR Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly by replacing the card. 6. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

142

5.13.11

IPC_7134_00038 - overTemperatureInFlow

The temperature is above the specified limit overTemperatureInFlow Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7134_00038 IPC/Cabinet/FBPShelf/GICC GICC environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly by replacing the card. 6. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

143

5.13.12

IPC_7135_00038 - overTemperatureOutFlow

The temperature is above the specified limit overTemperatureOutFlow Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7135_00038 IPC/Cabinet/FBPShelf/GICC GICC environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Possible root causes: Remedial Action Defective circuit boards Airflow obstruction or diversion Fan or temperature sensor failure.

Reason

1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly by replacing the card. 6. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

144

5.14

GICCBPEtherPort alarms
The following alarms are generated by the GICC backplane Ethernet port . IPC_7017_00016 - communicationFailureESC1_2 IPC_7018_00016 - communicationFailureESC1_21 IPC_7019_00016 - communicationFailureESC2_2 IPC_7020_00016 - communicationFailureESC2_21 IPC_7104_00016 - linkFailure IPC_7156_00016 - restoreServiceFailure

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

145

5.14.1

IPC_7017_00016 - communicationFailureESC1_2

Communication to Shelf=1, ESC=2 has failed communicationFailureESC1_2 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7017_00016 IPC/Cabinet/FBPShelf/GICC/GICCBPEtherPort GICCBPEtherPort communications communicationsSubsystemFailure MAJOR No direct impact, the alternate fabric is used to provide Ethernet communication. However the card is now vulnerable. Communications subsystem failure Perform the following procedure to clear the communicationFailureESC1_2 (IPC_7017_00016) alarm.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

146

IPC_7017_00016 - communicationFailureESC1_2 Remedial action Step Action

1. If ... only one GICC on shelf 1 (not on shelf 2) reports this alarm on its BPEtherPort 0, multiple shelf 1 GICCs and CICCs report this alarm on its BPEtherPort BPEtherPort 0, only shelf 2 (and not shelf 1) GICCs and CICCs report this alarm on its BPEtherPort 0, then ... replace the GICC. replace the GICC.

replace the ESC 2 on shelf 1. replace the ESC 2 on shelf 1.

check the vertical cables that connect ESC 2 on shelf 1 with ESC 2 on shelf 2 via ESC ports 22 and 23. check the vertical cables that connect ESC 2 on shelf 1 with ESC 2 on shelf 2 via ESC ports 22 and 23. check the diagonal cables that connect ESC 2 on shelf 1 with ESC 21 on shelf 2 via ESC ports 20 and 21. check the diagonal cables that connect ESC 2 on shelf 1 with ESC 21 on shelf 2 via ESC ports 20 and 21.

GICCs and CICCs report this alarm on its BPEtherPort 1 (and not on BPEtherPort 0),

2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

147

5.14.2

IPC_7018_00016 - communicationFailureESC1_21

Communication to Shelf=1, ESC=21 has failed communicationFailureESC1_21 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7018_00016 IPC/Cabinet/FBPShelf/GICC/GICCBPEtherPort GICCBPEtherPort communications communicationsSubsystemFailure MAJOR No direct impact, the alternate fabric is used to provide Ethernet communication. However the card is now vulnerable. Communications subsystem failure Perform the following procedure to clear the communicationFailureESC1_21 (IPC_7018_00016) alarm.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

148

IPC_7018_00016 - communicationFailureESC1_21 Remedial action Step Action

1. If ... only one GICC on shelf 1 (not on shelf 2) reports this alarm on its BPEtherPort 1, multiple shelf 1 GICCs and CICCs report this alarm on its BPEtherPort 1, only shelf 2 (not shelf 1) GICCs and CICCs report this alarm on its BPEtherPort 0, then ... replace the GICC. replace the GICC.

replace the ESC 21 on shelf 1. replace the ESC 21 on shelf 1.

check the vertical cables that connect ESC 21 on shelf 1 with ESC 21 on shelf 2 via ESC ports 22 and 23. check the vertical cables that connect ESC 21 on shelf 1 with ESC 21 on shelf 2 via ESC ports 22 and 23.

2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

149

5.14.3

IPC_7019_00016 - communicationFailureESC2_2

Communication to Shelf=2, ESC=2 has failed communicationFailureESC2_2 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7019_00016 IPC/Cabinet/FBPShelf/GICC/GICCBPEtherPort GICCBPEtherPort communications communicationsSubsystemFailure MAJOR No direct impact, the alternate fabric is used to provide Ethernet communication. However the card is now vulnerable. Communications subsystem failure Perform the following procedure to clear the communicationFailureESC2_2 (IPC_7019_00016) alarm.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

150

IPC_7019_00016 - communicationFailureESC2_2 Remedial action Step Action

1. If ... only one GICC on shelf 2 (not on shelf 1) reports this alarm on its BPEtherPort 0, multiple shelf 2 GICCs and CICCs report this alarm on its BPEtherPort BPEtherPort 0, only shelf 1 (and not shelf 2) GICCs and CICCs report this alarm on its BPEtherPort 0, then ... replace the GICC. replace the GICC.

replace the ESC 2 on shelf 2. replace the ESC 2 on shelf 2.

check the vertical cables that connect ESC 2 on shelf 1 with ESC 2 on shelf 2 via ESC ports 22 and 23. check the vertical cables that connect ESC 2 on shelf 1 with ESC 2 on shelf 2 via ESC ports 22 and 23.

2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

151

5.14.4

IPC_7020_00016 - communicationFailureESC2_21

Communication to Shelf=2, ESC=21 has failed communicationFailureESC2_21 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7020_00016 IPC/Cabinet/FBPShelf/GICC/GICCBPEtherPort GICCBPEtherPort communications communicationsSubsystemFailure MAJOR No direct impact, the alternate fabric is used to provide Ethernet communication. However the card is now vulnerable. Communications subsystem failure Perform the following procedure to clear the communicationFailureESC2_21 (IPC_7020_00016) alarm.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

152

IPC_7020_00016 - communicationFailureESC2_21 Remedial action Step Action

1. If ... only one GICC on shelf 2 (not on shelf 1) reports this alarm on its BPEtherPort 1, multiple shelf 2 (not shelf 1) GICCs and CICCs report this alarm on its BPEtherPort 1, only shelf 1 (not shelf 2) GICCs and CICCs report this alarm on its BPEtherPort 1, then ... replace the GICC. replace the GICC.

replace the ESC 21 on shelf 2. replace the ESC 21 on shelf 2.

check the vertical cables that connect ESC 21 on shelf 1 with ESC 21 on shelf 2 via ESC ports 22 and 23. check the vertical cables that connect ESC 21 on shelf 1 with ESC 21 on shelf 2 via ESC ports 22 and 23. check the diagonal cables that connect ESC 2 on shelf 1 with ESC 21 on shelf 2 via ESC ports 20 and 21. check the diagonal cables that connect ESC 2 on shelf 1 with ESC 21 on shelf 2 via ESC ports 20 and 21.

GICCs and CICCs report this alarm on its BPEtherPort 0 (and not on BPEtherPort 1),

2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

153

5.14.5

IPC_7104_00016 - linkFailure

A failure occured on the backplane Ether link connection linkFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7104_00016 IPC/Cabinet/FBPShelf/GICC/GICCBPEtherPort GICCBPEtherPort communications communicationsSubsystemFailure CRITICAL No communication with GICC possible. Communications subsystem failure 1. At the IPC, reseat the GICC. If the alarm is cleared, the procedure is completed. 2. At the IPC, replace the GICC. 3. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

154

5.14.6

IPC_7156_00016 - restoreServiceFailure

Request to restore service has failed restoreServiceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7156_00016 IPC/Cabinet/FBPShelf/GICC/GICCBPEtherPort GICCBPEtherPort communications communicationsSubsystemFailure MAJOR GICC processor not available. Communications subsystem failure 1. At the FMS, reset the GICC object. If the alarm is cleared the procedure is completed. 2. Open a SSH session to the IPC. 3. At the IPC, lock the GICC object. 4. At the IPC, replace the GICC. 5. At the IPC, unlock the GICC object. 6. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

155

5.15

GICCFAEtherPort alarms
The following alarms are generated by the GICC front access Ethernet port. IPC_7104_00017 - linkFailure IPC_7156_00017 - restoreServiceFailure

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

156

5.15.1

IPC_7104_00017 - linkFailure

A failure has occured on the front access Ethernet link connection linkFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7104_00017 IPC/Cabinet/FBPShelf/GICC/GICCFAEtherPort GICCFAEtherPort communications communicationsSubsystemFailure CRITICAL No communication with GICC possible. Communications subsystem failure 1. At the IPC, reset the GICC. If the alarm is cleared, the procedure is completed. 2. Open a SSH session to the IPC. 3. At the IPC, lock the GICC object. 4. At the IPC, replace the GICC. 5. At the IPC, unlock the GICC object. 6. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

157

5.15.2

IPC_7156_00017 - restoreServiceFailure

Request to restore service has failed restoreServiceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7156_00017 IPC/Cabinet/FBPShelf/GICC/GICCFAEtherPort GICCFAEtherPort communications communicationsSubsystemFailure MAJOR GICC processor not available. Communications subsystem failure. 1. At the FMS, reset the GICC object. If the alarm is cleared the procedure is completed. 2. Open a SSH session to the IPC. 3. At the IPC, lock the GICC object. 4. At the IPC, replace the GICC. 5. At the IPC, unlock the GICC object. 6. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

158

5.16

GICCProc alarms
The following alarms are generated by the GICCProc. IPC_7005_00020 - allOpticalLinksFailed IPC_7016_00020 - communicationFailure IPC_7021_00020 - communicationFailureLRM IPC_7023_00020 - configurationError IPC_7026_00020 - cpuUsageOverload IPC_7027_00020 - criticalSoftwareFailure IPC_7094_00020 - heartbeatFailure IPC_7124_00020 - memoryBlockError IPC_7125_00020 - memoryUsageOverload IPC_7155_00020 - resourceFailure IPC_7156_00020 - restoreServiceFailure IPC_7161_00020 - softwareAssertError IPC_7162_00020 - softwareVersionMismatch IPC_7163_00020 - standbyMateDown IPC_7183_00020 - vitalResourceFailure

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

159

5.16.1

IPC_7005_00020 - allOpticalLinksFailed

All optical links on the GICC have failed allOpticalLinksFailed Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7005_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc communications communicationsSubsystemFailure CRITICAL No reduncancy is available for the optical links assigned to the GICC. Any optical link failure on the mated GICC will result in complete loss of communication for that link Communications subsystem failure 1. At the FMS, check for alarms on individual optical links and perform the appropriate procedures to clear them. If the alarm is cleared, the procedure is completed. 2. If there are no optical link failure alarms, but the GICC has been manually locked, unlock the GICC object. 3. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

160

5.16.2

IPC_7016_00020 - communicationFailure

Communication to the GICC processor has failed communicationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7016_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc equipment processorProblem CRITICAL GICC is not available. Processor problem 1. At the FMS, if the GICC is initializing, ensure that the GICC restores successfully. If the alarm is cleared, procedure is completed. 2. At the IPC, check whether the GICC is present. 3. At the IPC, check whether the GICC is powered on. 4. At the FMS, check if there are ESC alarms and correct ESC failures. If the alarm is cleared, the procedure is completed. 5. At the FMS, reset the GICC object. If the alarm is cleared, procedure is completed. 6. Open a SSH session to the IPC. 7. At the IPC, lock the GICC object. 8. At the IPC, replace the GICC. 9. At the IPC, unlock the GICC object. 10 If the problem persists, contact Alcatel-Lucent customer support. .

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

161

5.16.3

IPC_7021_00020 - communicationFailureLRM

Communication from FMS host processor to LRM on the GICC processor has failed communicationFailureLRM Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7021_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc communications communicationsSubsystemFailure CRITICAL GICC processor is unavailable for use by call processing. Communications subsystem failure 1. If the alarm has not cleared within 15 minutes, check if other boards of the same type have successfully booted, if not, verify correct software is installed successfully. 2. Execute a manual reset on the associated GICC board. 3. At the IPC, replace the board if it has previously been in service or verify the correct board was installed. 4. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

162

5.16.4

IPC_7023_00020 - configurationError

A configuration data error has been detected configurationError Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7023_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc processing error configurationOrCustomizationError MAJOR Call processing may be affected. The data was either populated incorrectly initially, or a data change was made that introduced the error. 1. Contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

163

5.16.5

IPC_7026_00020 - cpuUsageOverload

The processor is in CPU usage overload cpuUsageOverload Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7026_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc quality of service resourceAtOrNearingCapacity MAJOR Reduced throughput on the GICC. System audits will be inhibited. The threshold for CPU usage overload of the processor on the GICC is exceeded. 1. At the FMS, reduce the processing load. 2. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

164

5.16.6

IPC_7027_00020 - criticalSoftwareFailure

A critical software failure has occurred criticalSoftwareFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7027_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc processing error softwareError CRITICAL The GICC is not available. Some calls may be dropped. Network elements may be dropped and then recovered after a switch to the standby GICC or the recovery of the active GICC. Software error 1. At the FMS, clear any other alarm that has been reported for the same GICC object If the alarm is cleared, the procedure is completed. 2. If the fault is reported periodically by the same GICC, open a SSH session to the IPC, and lock the GICC object. 3. At the IPC, replace the GICC. 4. At the IPC, unlock the GICC object. 5. At the FMS, manually clear the alarm. 6. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

165

5.16.7

IPC_7094_00020 - heartbeatFailure

Heartbeat communication failure has been detected between peer instances heartbeatFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7094_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc processing error softwareError MAJOR A remote GICC card probably performs a reset. Software error 1. No action required. The error will be cleared automatically after the remote GICC has been recovered. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

166

5.16.8

IPC_7124_00020 - memoryBlockError

Memory block exhaustion (MBC or CBUFFER) has been detected memoryBlockError Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7124_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc quality of service resourceAtOrNearingCapacity MAJOR Establishment of new calls may be refused. As long as the memory block error is not cleared, the TPU application (C-plane) does not accept new contexts or calls on that GICC. High load distributed to the GICC causing high Message Block Chain memory load. The high load can be an indication that the IPC is at its capacity or is nearing its capacity and requires replanning or reengineering. 1. At the IPC, ensure that all GICC cards are unlocked and enabled. If the alarm is cleared, the procedure is completed. 2. A network replanning may be necessary in case the capacity of the IPC is reached. 3. If the problem persists, contact Alcatel-Lucent customer support.

Reason

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

167

5.16.9

IPC_7125_00020 - memoryUsageOverload

The processor is in memory usage overload memoryUsageOverload Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7125_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc quality of service resourceAtOrNearingCapacity MAJOR Memory overload may degrade the system performance. The threshold for memory usage overload of the processor on the GICC is exceeded. 1. Contact Alcatel-Lucent customer support.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

168

5.16.10

IPC_7155_00020 - resourceFailure

A non-vital underlying platform service is unavailable or out of service resourceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7155_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc processing error underlyingResourceUnavailable minor GICC not available for call processing. Underlying resource unavailable 1. At the FMS, reset the GICC object. If the alarm is cleared, the procedure is completed. 2. Open a SSH session to the IPC. 3. At the IPC, lock the GICC object 4. At the IPC, replace the GICC. 5. At the IPC, unlock the GICC object. 6. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

169

5.16.11

IPC_7156_00020 - restoreServiceFailure

Request to restore service has failed restoreServiceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7156_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc communications communicationsSubsystemFailure MAJOR GICC processor not available. Communications subsystem failure 1. At the FMS, reset the GICC object. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

170

5.16.12

IPC_7161_00020 - softwareAssertError

A software assert error has occurred softwareAssertError Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7161_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc processing error softwareError CRITICAL The GICC is not available. Some calls may be dropped. Network elements may be dropped and then recovered after a switch to the standby GICC or the recovery of the active GICC. Software error 1. At the FMS, perform a reset of the GICC object to reboot the GICC. 2. At the FMS, manually clear the alarm. 3. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

171

5.16.13

IPC_7162_00020 - softwareVersionMismatch

The software version running on this processor does not match the provisioned software version softwareVersionMismatch Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7162_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc processing error versionMismatch MAJOR Processor may not initialize properly. Version mismatch 1. Install the provisioned software version on the processor. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

172

5.16.14

IPC_7163_00020 - standbyMateDown

The associated standby mate processor is unavailable standbyMateDown Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7163_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc equipment processorProblem MAJOR No redundant GICC processor available. Processor problem 1. At the FMS, check the status of the OC3 ports on the associated mate GICC. If all 4 OC3 ports are alarmed and / or failed then this 'standbyMateDown' will be raised on the local GICCProc. Check also for an 'allOpticalLinksFailed' alarm on the mated GICCProc. This can also cause the current alarm This implies that no standby OC3 ports are available if one of the local ports fail. Check the PSAX and network to see if the port failure is external. If no external cause can be found proceed to step 2. 2. At the FMS, check the status of the associated mate GICC processor and the mate GICC board itself. Also, check from the IPC if the mated GICC is locked. Check for alarms or states that indicate problems with the board or processor and replace if necessary. If no problem can be found on the mate board or processor proceed to step 3. 3. At the FMS, check the status of local IPC communications, - example, look for ESC and EthernetPort alarms that might effect GICC communications. If no local communications problem can be found proceed to step 4. 4. At the FMS, reset the standby GICC. 5. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

173

5.16.15

IPC_7183_00020 - vitalResourceFailure

vital underlying platform service is unavailable or out of service vitalResourceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7183_00020 IPC/Cabinet/FBPShelf/GICC/GICCProc GICCProc processing error underlyingResourceUnavailable CRITICAL GICC not available for call processing. Calls hosted on the card or context that are hosted on that card are dropped. Underlying resource unavailable 1. At the FMS, reset the GICC object. If the alarm is cleared, the procedure is completed. 2. Open a SSH session to the IPC. 3. At the IPC, lock the GICC object. 4. At the IPC, replace the GICC. 5. At the IPC, unlock the GICC object. 6. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

174

5.17

GICCSTM1OC3Port alarms
The following alarms are generated by the GICC STM1/OC3 port. IPC_7104_00021 - linkFailure IPC_7105_00021 - linkFailureAIS_L IPC_7106_00021 - linkFailureAIS_P IPC_7107_00021 - linkFailureLCD_P IPC_7108_00021 - linkFailureLOF IPC_7109_00021 - linkFailureLOP_P IPC_7110_00021 - linkFailureLOS IPC_7111_00021 - linkFailurePLM_P IPC_7112_00021 - linkFailureRDI_L IPC_7113_00021 - linkFailureRDI_P IPC_7156_00021 - restoreServiceFailure

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

175

5.17.1

IPC_7104_00021 - linkFailure

A failure has occured on the ATM (STM1/OC3) link connection linkFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7104_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL During the switch over to the standby GICC some packets may be lost. If the standby GICC is not available the connection to the network will be lost and calls will fail. ATM link connection failure 1. At the IPC, check the ATM link connection 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

176

5.17.2

IPC_7105_00021 - linkFailureAIS_L

An Alarm Indication Signal Line (AIS-L) failure has occured on the ATM (STM1/OC3) link connection linkFailureAIS_L Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7105_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL During the switch over some packets may be lost. If the protection line is not available, the connection to the network will be lost and calls will fail. An AIS-L is an indication that the far end is out of service. An AIS-L is sent by an Section Terminating Equipment (STE) to a downstream Line Terminating Equipment (LTE) when LOS or LOF is detected on an incoming SONET section. 1. At the IPC, check the physical ATM link connection. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

177

5.17.3

IPC_7106_00021 - linkFailureAIS_P

An Alarm Indication Signal Path (AIS-P) failure has occured on the ATM (STM1/OC3) link connection linkFailureAIS_P Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7106_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL During the switch over some packets may be lost. If the protection line is not available, the connection to the network will be lost and calls will fail. Loss of communication at the remote end of the optical link. An AIS-P is an indication that the far end is out of service. An AIS-P is sent by an Line Terminating Equipment (LTE) to a downstream Path Terminating Equipment (PTE) when an LOS or LOF is detected on a upstream SONET section. 1. At the IPC, check the physical ATM link connection. If the alarm is cleared, the procedure is completed. 2. At the far end, check the physical ATM link connection. Correct problem found at the far end. If the alarm is cleared, the procedure is completed. 3. If the problem persists, contact Alcatel-Lucent customer support.

Reason

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

178

5.17.4

IPC_7107_00021 - linkFailureLCD_P

A Loss of Cell Delineation Path (LCD-P) failure has occured on the ATM (STM1/OC3) link connection linkFailureLCD_P Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7107_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL Loss of communication. The ATM cell alignment boundary in an octet stream can not be maintained. Possible root causes: Remedial Action Physical problem with the ATM link connection.

1. At the IPC, check the physical ATM link connection. 2. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

179

5.17.5

IPC_7108_00021 - linkFailureLOF

A Loss of Frame (LOF) failure has occured on the ATM (STM1/OC3) link connection linkFailureLOF Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7108_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL During the switch over some packets may be lost. If the protection line is not available, the connection to the network will be lost and calls will fail. A signal could not be detected at the interface. The cause of the problem can be at the IPC or at the far end of the connection. Both sides must be checked. Possible root causes: Remedial Action The link is not plugged in The connector is damaged The fiber is damaged The fiber is cut.

Reason

1. At the IPC, check the physical ATM link connection. If the alarm is cleared, the procedure is completed. 2. At the far end, check the physical ATM link connection. If the alarm is cleared, the procedure is completed. 3. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

180

5.17.6

IPC_7109_00021 - linkFailureLOP_P

A Loss of Pointer Path (LOP-P) failure has occured on the ATM (STM1/OC3) link connection linkFailureLOP_P Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7109_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL Payload can not be extracted from messages. During the switch over some packets may be lost. If the protection line is not available, the connection to the network will be lost and calls will fail. A valid pointer on an incoming signal can not be located. A possible provisioning problem. This failure is usually discovered upon initial provisioning. 1. At the IPC, check the ATM link provisioning data. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

181

5.17.7

IPC_7110_00021 - linkFailureLOS

A Loss of Signal (LOS) failure has occured on the ATM (STM1/OC3) link connection linkFailureLOS Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7110_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL During the switch over some packets may be lost. If the protection line is not available, the connection to the network will be lost and calls will fail. Physical problem with the ATM link connection. 1. At the IPC, check the physical ATM link connection. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

182

5.17.8

IPC_7111_00021 - linkFailurePLM_P

A Payload Label Mismatch Path (PLM-P) failure has occured on the ATM (STM1/OC3) link connection linkFailurePLM_P Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7111_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL During the switch over some packets may be lost. If the protection line is not available, the connection to the network will be lost and calls will fail. The incoming payload label does not match the expected payload label. The label is corrupted. 1. At the IPC, check the physical ATM link connection. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

183

5.17.9

IPC_7112_00021 - linkFailureRDI_L

A Remote Defect Indication Line (RDI-L) failure has occured on the ATM (STM1/OC3) link connection linkFailureRDI_L Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7112_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL The link has a problem at the remote end of the line segment. A problem at the remote end of the line segment. An RDI-L is sent upstream to a peer Line Terminating Equipment (LTE) when an AIS-L alarm or low-level defects are detected. 1. At the IPC, check the physical ATM link connection. If the alarm is cleared, the procedure is completed. 2. Correct failures at the remote end. If the alarm is cleared, the procedure is completed. 3. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

184

5.17.10

IPC_7113_00021 - linkFailureRDI_P

Remote Defect Indication Path (RDI-P) failure has occured on the ATM (STM1/OC3) link connection linkFailureRDI_P Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7113_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL The link has a problem at the remote end of the line segment. An RDI-P is an indication of a problem at the remote end of the line segment. An RDI-P is sent upstream to a peer Path Terminating Equipement (PTE) when a defect in the signal, typically an AIS-P, is detected. 1. At the IPC, check the physical ATM link connection. If the alarm is cleared, the procedure is completed. 2. At the far end, check the physical ATM link connection. Correct problem found at the far end. If the alarm is cleared, the procedure is completed. 3. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

185

5.17.11

IPC_7156_00021 - restoreServiceFailure

Request to restore service has failed restoreServiceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7156_00021 IPC/Cabinet/FBPShelf/GICC/GICCSTM1OC3Port GICCSTM1OC3Port communications communicationsSubsystemFailure CRITICAL GICC processor not available. Communications subsystem failure 1. At the FMS, reset the GICC object. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

186

5.18

GICCVirtualRouter alarms
The following alarms are generated by the GICC Virtual Router. IPC_7182_00022 - virtualGroupGICCRouterMembersFault

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

187

5.18.1

IPC_7182_00022 - virtualGroupGICCRouterMembersFault

All GICC Router members of the GICC Virtual Router virtual group faulted. virtualGroupGICCRouterMembersFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7182_00022 IPC/GICCVirtualRouter GICCVirtualRouter processing error underlyingResourceUnavailable CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

188

5.19

IPC alarms
The following alarms are generated by the IPC. IPC_7003_00004 - alarmDefFileCorrupt IPC_7004_00004 - alarmDefFileMissing IPC_7013_00004 - ciccGiccConfigFileMissing IPC_7014_00004 - cLIScriptFailed IPC_7015_00004 - clockSourceFailure IPC_7023_00004 - configurationError IPC_7025_00004 - coreFileGenerated IPC_7026_00004 - cpuUsageOverload IPC_7028_00004 - dataAuditFailure IPC_7029_00004 - dBReplicationAuditFailure IPC_7030_00004 - degradeGroupMemberFault IPC_7034_00004 - eventFloodConditionDetected IPC_7067_00004 - failureGroupMemberFault IPC_7092_00004 - ftProcessError IPC_7093_00004 - general_Handling_Error_Indication IPC_7095_00004 - hostProcessCommunicationFailure IPC_7096_00004 - hostProcessEnlistTimeout IPC_7097_00004 - hostProcessFailure IPC_7098_00004 - hostProcessRestartFailure IPC_7099_00004 - hostProcessRestartSuspended IPC_7100_00004 - hostProcessTerminationFailure IPC_7101_00004 - iNITrunLevelTimeout IPC_7102_00004 - iNITterminatingTimeout IPC_7103_00004 - internal_Clock_Source_Disconnected IPC_7114_00004 - log100PercentFull IPC_7115_00004 - log80PercentFull IPC_7126_00004 - miscellaneous_Cause IPC_7132_00004 - oamStateControlFailure IPC_7144_00004 - perfMgr_DNMAP_INIT IPC_7145_00004 - pmArchiveInitFailure IPC_7146_00004 - pmCTDBImageFailure

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

189

IPC_7147_00004 - pmCTDBInitFailure IPC_7148_00004 - primary_Clock_Source_Disconnected IPC_7159_00004 - secondSRSTCPEstFailure IPC_7164_00004 - suActivationFailure IPC_7165_00004 - suApplyFailure IPC_7166_00004 - suBackoutFailure IPC_7167_00004 - suCommitFailure IPC_7168_00004 - suDeApplyFailure IPC_7169_00004 - suDeleteFailure IPC_7170_00004 - suDownloadFailure IPC_7171_00004 - suFallbackFailure IPC_7172_00004 - suICCPartialUpdateFailure IPC_7173_00004 - suInfoSyncFailure IPC_7174_00004 - suInstallFailure IPC_7176_00004 - suStatePanicFailure

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

190

5.19.1

IPC_7003_00004 - alarmDefFileCorrupt

aLIPC_alarmDefFileCorrupt alarmDefFileCorrupt Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7003_00004 IPC IPC processing error softwareError MAJOR Changeable portions of the alarm information are not updated. The alarm definition file adf.xml data is not correctly formatted. 1. At the IPC, install an unmodified or the latest version of the adf.xml file in the directory /flx/RNCbsc/current/data. 2. At the FMS, upload the alarm definitions from the IPC. If the alarm is cleared, the procedure is completed. 3. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

191

5.19.2

IPC_7004_00004 - alarmDefFileMissing

The Alarm Definition File (ADF) could not be found alarmDefFileMissing Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7004_00004 IPC IPC processing error softwareError MAJOR Changeable portions of the alarm information are not updated (for example probable cause, perceived severity and alarm text). Software error 1. At the IPC, install an unmodified or the latest version of the adf.xml file in the directory /flx/RNCbsc/current/data. 2. At the FMS, upload the alarm definitions from the IPC. If the alarm is cleared, the procedure is completed. 3. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

192

5.19.3

IPC_7013_00004 - ciccGiccConfigFileMissing

One or more CICC/GICC configuration files are missing ciccGiccConfigFileMissing Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7013_00004 IPC IPC processing error softwareError MAJOR If a GICC or CICC is reset, it may not initialize properly. A configuration file is corrupt or deleted. Perform the following procedure to clear the ciccGiccConfigFileMissing (IPC_7013_00004) alarm.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

193

IPC_7013_00004 - ciccGiccConfigFileMissing Remedial action Step Action

1. Telnet to both OAM FMS nodes 2. Change directory to /flx/tftpboot/fbp/config 3. Verify the following configuration files exist: 4. If ... one or more files are missing, tpu.cfg plus.cfg platform.cfg

then .. Reinstall the missing configuration files from / flx/RNCtpu/current/flx/tftpboot/fbp/config Reinstall the missing configuration files from / flx/RNCtpu/current/flx/tftpboot/fbp/config / flx/RNCtpu/current/flx/tftpboot/fbp/config Reinstall all configuration files from / flx/RNCtpu/current/flx/tftpboot/fbp/configThis overwrites configuration files that may have been corrupted. Reinstall all configuration files from /flx/RNCtpu/current/flx/tftpboot/fbp/config /flx/RNCtpu/current/flx/tftpboot/fbp/config This overwrites configuration files that may have been corrupted.

all files are present,

5. After the file recovery is completed, execute a Remote View Audit from the IPC LMT (IPCCLI)Select: IPC Audits Start IPC Audit set auditType=REMOTEVIEW

If the alarm is cleared, the procedure is completed.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

194

6. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

195

5.19.4

IPC_7014_00004 - cLIScriptFailed

A CLI batch script failed cLIScriptFailed Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7014_00004 IPC IPC processing error softwareError minor None. CLI client has crashed. 1. Check additional text for details of script failure (script file name, date/time of execution) and who to contact (user id) to further check the impact of script failure. Ref Type (Feature, Requirement, etc.) Ref Value (feature#, reqmnt#, etc.) 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

196

5.19.5

IPC_7015_00004 - clockSourceFailure

IPC clock source configuration failed clockSourceFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7015_00004 IPC IPC equipment equipmentMalfunction CRITICAL Loss of configurable clock sources. Probable hardware failure. Primary, secondary and internal clock sources have failed. 1. Check why primary, secondary and internal network clock sources have failed and take the appropriate action. 2. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

197

5.19.6

IPC_7023_00004 - configurationError

IPC software component initialization failed configurationError Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7023_00004 IPC IPC processing error softwareProgramError CRITICAL Failure of call processing capsule, caused by a loss of call processing capacity. As a result, the system will attempt the software component reestablishment. Software program error 1. At the FMS, manually clear the alarm. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

198

5.19.7

IPC_7025_00004 - coreFileGenerated

A software failure on a host process has generated a core dump coreFileGenerated Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7025_00004 IPC IPC processing error softwareProgramAbnormallyTerminated minor If the process cannot run, a failover will result. As a result, limited process restarts are attempted. A host process has abnormally ended. Perform the following procedure to clear the coreFileGenerated (IPC_7025_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

199

IPC_7025_00004 - coreFileGenerated Remedial action Step Action

1. ATTENTION Perform this only if the failover does not recover the host process and the IPC is unable to process calls. Perform this only if the failover does not recover the host process and the IPC is unable to process calls.At the FMS, perform a reset type 2 on the LIPC object to reboot the IPC. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

200

5.19.8

IPC_7026_00004 - cpuUsageOverload

The IPC is in CPU usage overload cpuUsageOverload Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7026_00004 IPC IPC quality of service resourceAtOrNearingCapacity MAJOR

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

201

5.19.9

IPC_7028_00004 - dataAuditFailure

Data Audit was unable to correct data mismatch dataAuditFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7028_00004 IPC IPC processing error corruptData minor Data mismatch between OAM DB and either FWR or config files. A data mismatch that could not be corrected was detected during a data audit. 1. At the IPC, check the data audit log for details of uncorrectable data and correct the mismatch. 2. At the FMS, manually clear the alarm. 3. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

202

5.19.10

IPC_7029_00004 - dBReplicationAuditFailure

Database Replication Audit has detected an anomaly between the IPC OAM blades. dBReplicationAuditFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7029_00004 IPC IPC processing error corruptData minor The fault may lead to future software upgrade failures. Corrupt data Perform the following procedure to clear the dBReplicationAuditFailure (IPC_7029_00004) alarm.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

203

IPC_7029_00004 - dBReplicationAuditFailure Remedial action Step Action

1. If alarm is raised due to absence of any configuration file, perform the following actions: a. Login to IPC as primUser and then assume the role as primary (su-primary password: <null>) and verify that the following configuration files exist on both the OAM blades FMS01 and FMS02) of the IPC, /app2/dbzdata/current/data /site.rc, /flx/dbz/lib/sys.rc, /flx/dbz/lib/db.rc and /app2/dbzdata/current/data/fdbms.rc . If one of the files (site.rc, fdbms.rc, db.rc) is missing in one FMS blade, copy it from the other FMS blade. If sys.rc is missing, copy it from /flx/data/RNCfmscfg/ to /flx/dbz/lib directory on that blade. b. Verify that replication is enabled on both the FMS blades (check /app2/dbzdata/current/data/site.rc on each blade). If there is only one entry, replication is disabled on that blade. To enable replication: Telnet to that particular FMS blade using login as primUser Run . /flx/RNCbsc/current/data/DM.env Run /flx/RNCbsc/current/bin/updDbRepl.pl #x enable #m local_remote

2. If alarm is raised because of system command failure, check that there is sufficient space (490 Mb) available in /var/tmp/REPLAUDIT directory. To do this, login to one of the FMS in IPC as primUser and then assume role as primary (su # primary, password:<null>) and run df #k /var/tmp/REPLAUDIT | awk | #{print $4}# | grep #v "avail" If available space is less than 490 Mb, create more before the next run. 3. If FMS alarm text indicates that datablitz is down or not responding, check if any FMS is offline. To do that login to one of the FMS in IPC as primUser and then assume role as primary (su # primary, password:<null>)and use RCCcstat command to verify. If one blade is offline, bring that blade online by using /flx/RNCbsc/current/bin/RMTunlock <bladename>. 4. If alarm is raised due to data mismatch, use the following steps to recover: Login to one of the FMS in IPC as primUser and then assume role as primary (su # primary, password:<null>) Run /flx/RNCbsc/current/bin/checkdbsize to get the differences between blzsize.fms01 and blzsize.fms02 under /tmp dir. diff /tmp/blzsize.fms01 /tmp/blzsize.fms02 If output shows any differences for any of the tables, pick up that particular table name and corresponding table id from fdbms.rc file and unsubscribe that table using blzrepl #u

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

204

<table_name> <table_id> for example blzrepl #u AlarmManager 8. Subscribe the table again using blzrepl #s <table_name> <table_id>.

5. After taking any of the appropriate actions above, clear the alarm manually from alarm list and run replication audit once again on demand from LMT client on IPC.Use the following steps: Navigate to the IPCCLI menu. Select menu options 6,1,1,17 and submit (S)

6. If any one of the above actions does not solve the problem, restart the datablitz on IPC using following commands. Login to any FMS in IPC as root. datablitz #S to stop the datablitz. Wait for some time. datablitz & to start the datablitz.

On completion, return to step 5. 7. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

205

5.19.11

IPC_7030_00004 - degradeGroupMemberFault

A member of a degrade group faulted degradeGroupMemberFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7030_00004 IPC IPC processing error underlyingResourceUnavailable MAJOR The LIPC is considered degraded. Underlying resource unavailable 1. The alarm is currently not in use. If the alarm appears, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

206

5.19.12

IPC_7034_00004 - eventFloodConditionDetected

Detected an alarm or event flood condition and appropriate alarm and/or event filter is applied eventFloodConditionDetected Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7034_00004 IPC IPC equipment equipmentMalfunction CRITICAL Depends on the cause of the alarm or event storm (the trigger alarm). Storm of alarms or events has been detected at IPC which resulted in automatically applying filter to suppress them. 1. This alarm means that a storm of alarms or events has been detected at the IPC level, likely due to some hardware or network problem. Check the additional text which will contain the flood trigger and filter information. At the FMS, check for the trigger alarm and take appropriate action. For example, OC3 power loss or all optical links failed alarms may indicate network or GICC problems etc. 2. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

207

5.19.13

IPC_7067_00004 - failureGroupMemberFault

A member of a failure group faulted. failureGroupMemberFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7067_00004 IPC IPC processing error underlyingResourceUnavailable MAJOR The LIPC is not operational. Underlying resource unavailable 1. The alarm is currently not in use. If the alarm appears, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

208

5.19.14

IPC_7092_00004 - ftProcessError

A failure has occurred on a fault tolerant process ftProcessError Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action Software error Perform the following procedure to clear the ftProcessError (IPC_7092_00004) alarm. 1. Check any Environment variable file to assure that LOGCONFPATH has been set to the existing directory and with the correct permission. 2. Restart the server. 3. At the FMS, manually clear the alarm. 4. If the problem persists, contact Alcatel-Lucent customer support. 1. Check any Environment variable file to assure that LOGFILEPATH has been set to the existing directory and with the correct permission. 2. Restart the LogManager to correct the problem after the environment variable was corrected. 3. At the FMS, manually clear the alarm. 4. If the problem persists, contact Alcatel-Lucent customer support. 1. At the FMS, check the contents of the additional alarm text field and take the appropriate actions. 2. At the FMS, manually clear the alarm. 3. If the problem persists, contact Alcatel-Lucent customer support. IPC_7092_00004 IPC IPC processing error softwareError warning

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

209

IPC_7092_00004 - ftProcessError Remedial action Step Action

1. If... Then...

The additional alarm text field in the Go to procedure Fault clearance procedure for LOGalarm message indicates "LOGCON- CONFPATH. Go to procedure Fault clearance procedFPATH", ure for LOGCONFPATH. Fault clearance procedure for LOGCONFPATH The additional alarm text field in the Go to procedure Fault clearance procedure for LOGalarm message indicates "LOGFILE- FILEPATH. Go to procedure Fault clearance procedure PATH", for LOGFILEPATH. Fault clearance procedure for LOGFILEPATH The additional alarm text field in the alarm message indicates another probable cause, Go to procedure Fault clearance procedure for other probable causes. Go to procedure Fault clearance procedure for other probable causes. Fault clearance procedure for other probable causes

--End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

210

5.19.15

IPC_7093_00004 - general_Handling_Error_Indication

Error indication when there is no other appropriate error message general_Handling_Error_Indication Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7093_00004 IPC IPC processing error applicationSubsystemFailure warning Potential risk of impacting call processing. Application subsystem failure 1. At the FMS, check the root cause and take the appropriate action. 2. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

211

5.19.16

IPC_7095_00004 - hostProcessCommunicationFailure

A host process is not responding to heartbeat requests hostProcessCommunicationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7095_00004 IPC IPC processing error softwareProgramError minor If not recoverable, a failover will result. As a result, the process is terminated and restarted. The process is insane or being CPU starved. Perform the following procedure to clear the hostProcessCommunicationFailure (IPC_7095_00004) alarm.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

212

IPC_7095_00004 - hostProcessCommunicationFailure Remedial action Step Action

1. ATTENTION Perform this only if the failover does not recover the host process and the IPC is unable to process calls. Perform this only if the failover does not recover the host process and the IPC is unable to process calls.At the FMS, perform a reset type 2 on the LIPC object to reboot the IPC. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

213

5.19.17

IPC_7096_00004 - hostProcessEnlistTimeout

A host process has failed to enlist in a timely manner hostProcessEnlistTimeout Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7096_00004 IPC IPC processing error softwareProgramError minor If the process cannot run, a failover will result. As a result, the process is terminated and restarted. Software program error. Perform the following procedure to clear the hostProcessEnlistTimeout (IPC_7096_00004) alarm.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

214

IPC_7096_00004 - hostProcessEnlistTimeout Remedial action Step Action

1. ATTENTION Perform this only if the failover does not recover the host process and the IPC is unable to process calls. Perform this only if the failover does not recover the host process and the IPC is unable to process calls.At the FMS, perform a reset type 2 on the LIPC object to reboot the IPC. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

215

5.19.18

IPC_7097_00004 - hostProcessFailure

A host process has failed and is not running hostProcessFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7097_00004 IPC IPC processing error softwareProgramError minor The host process restarts automatically. A software error caused the host process to fail. 1. No action required. The process is restarted and the alarm will be cleared. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

216

5.19.19

IPC_7098_00004 - hostProcessRestartFailure

The restart of a host process has failed hostProcessRestartFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7098_00004 IPC IPC processing error softwareProgramError minor The error is escalated to RCC. As a result, the host will fail over. Missing software image to start the host process. 1. At the IPC, use the "IPC configuration data restore" procedure to restore the IPC with the backup software. 2. If the problem persists, contact Alcatel-Lucent customer support to replace the missing software image.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

217

5.19.20

IPC_7099_00004 - hostProcessRestartSuspended

The restart of a host process has been temporarily suspended hostProcessRestartSuspended Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7099_00004 IPC IPC processing error softwareProgramError MAJOR Error is escalated to RCC, as a result the host will fail over. The software image for the host process may be missing or corrupted. 1. At the IPC, use the "IPC configuration data restore" procedure to restore the IPC with the backup software. 2. If the problem persists, contact Alcatel-Lucent customer support to replace the missing or corrupted software image.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

218

5.19.21

IPC_7100_00004 - hostProcessTerminationFailure

A host process has failed to respond to a termination request hostProcessTerminationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7100_00004 IPC IPC processing error softwareProgramError minor If not recoverable, a host failover will result. As a result, the process restarts are suspended (LIPC_hostProcessRestartFailure). Software program error Perform the following procedure to clear the hostProcessTerminationFailure (IPC_7100_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

219

IPC_7100_00004 - hostProcessTerminationFailure Remedial action Step Action

1. ATTENTION Perform this only if the failover does not recover the host process and the IPC is unable to process calls. Perform this only if the failover does not recover the host process and the IPC is unable to process calls.At the FMS, perform a reset type 2 on the LIPC object to reboot the IPC. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

220

5.19.22

IPC_7101_00004 - iNITrunLevelTimeout

Process did not respond to change of run level request iNITrunLevelTimeout Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7101_00004 IPC IPC processing error softwareProgramError minor If process restarts are not successful, then the LIPC_hostProcessRestartSuspended alarm will occur. As a result, limited process restarts are attempted. The launched program will not respond to run level change. Perform the following procedure to clear the iNITrunLevelTimeout (IPC_7101_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

221

IPC_7101_00004 - iNITrunLevelTimeout Remedial action Step Action

1. ATTENTION Perform this only if the failover does not recover the host process and the IPC is unable to process calls. Perform this only if the failover does not recover the host process and the IPC is unable to process calls.At the FMS, perform a reset type 2 on the LIPC object to reboot the IPC. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

222

5.19.23

IPC_7102_00004 - iNITterminatingTimeout

Host process did not respond to termination request iNITterminatingTimeout Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7102_00004 IPC IPC processing error softwareProgramError minor If restarts are not successful, then the LIPC_hostProcessRestartSuspended alarm will occur. As a result, the termination is escalated to SIGKILL. There is a faulty signal handler or a long shutdown time. Perform the following procedure to clear the iNITterminatingTimeout (IPC_7102_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

223

IPC_7102_00004 - iNITterminatingTimeout Remedial action Step Action

1. ATTENTION Perform this only if the failover does not recover the host process and the IPC is unable to process calls. Perform this only if the failover does not recover the host process and the IPC is unable to process calls.At the FMS, perform a reset type 2 on the LIPC object to reboot the IPC. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

224

5.19.24

IPC_7103_00004 - internal_Clock_Source_Disconnected

IPC internal clock source is disconnected internal_Clock_Source_Disconnected Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7103_00004 IPC IPC equipment timingProblem CRITICAL Loss of synchronization if network clocks are not configured. Hardware failure or timing problem. 1. Make sure that the network clock is available and active. 2. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

225

5.19.25

IPC_7114_00004 - log100PercentFull

TPU log reached threshold of 100% of maxium previous log files log100PercentFull Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7114_00004 IPC IPC processing error storageCapacityProblem minor System log files will be full and the most recent one will be overwritten. Storage capacity problem 1. At the IPC, move old system logs to a different directory or delete them from the system. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

226

5.19.26

IPC_7115_00004 - log80PercentFull

TPU log reached threshold of 80% of maxium previous log files log80PercentFull Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7115_00004 IPC IPC processing error storageCapacityProblem warning System log files will be full soon, at which time the most recent one will be overwritten. Storage capacity problem 1. At the IPC, move old system logs to a different directory or delete them from the system. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

227

5.19.27

IPC_7126_00004 - miscellaneous_Cause

Miscellaneous Cause in IPC miscellaneous_Cause Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7126_00004 IPC IPC communications communicationsProtocolError minor

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

228

5.19.28

IPC_7132_00004 - oamStateControlFailure

OAM state data possibly incorrect oamStateControlFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7132_00004 IPC IPC processing error corruptData MAJOR The reporting object may not show the correct operational, administrative or availability state. Corrupt data Perform the following procedure to clear the oamStateControlFailure (IPC_7132_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

229

IPC_7132_00004 - oamStateControlFailure Remedial action Step Action

1. At the FMS, check the additional text field to find the object reporting this alarm. 2. Open a SSH session to the IPC. 3. ATTENTION Do NOT perform recovery on the LIPC object itself unless the additional text field is empty. At the IPC, lock and unlock the object that is reporting the alarm.Do NOT perform recovery on the LIPC object itself unless the additional text field is empty. 4. At the FMS, manually clear the alarm. 5. If this alarm occurs excessively, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

230

5.19.29

IPC_7144_00004 - perfMgr_DNMAP_INIT

DN mapping failed perfMgr_DNMAP_INIT Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7144_00004 IPC IPC processing error softwareError MAJOR The Performance Management (PM) server will halt. Query MEO for LIPC failed. Maybe the LIPC is not yet created. 1. At the FMS, make sure that the MEO server is functioning. If the alarm is cleared, the procedure is completed. 2. At the FMS, check whether the LIPC has been created in the database. If necessary, create an LIPC instance and restart the PM server. 3. At the FMS, manually clear the alarm. 4. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

231

5.19.30

IPC_7145_00004 - pmArchiveInitFailure

A Performance Measurement archive initialization failure has occurred pmArchiveInitFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7145_00004 IPC IPC processing error softwareError MAJOR The Performance Management (PM) server will halt. Software error 1. At the FMS, make sure that the archive directory specified in the ASRV_FILES_PATH variable is accessible. 2. Restart the PM server. 3. At the FMS, manually clear the alarm. 4. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

232

5.19.31

IPC_7146_00004 - pmCTDBImageFailure

Unable to create a Performance Measurements Counter Type Database (CTDB) image. pmCTDBImageFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7146_00004 IPC IPC processing error softwareError MAJOR The Performance Management (PM) server will halt. Cannot build the counter database from the measurement job. 1. At the FMS, check the measurement job to match the counters in the CounterTypeConf.xml. 2. At the FMS, manually clear the alarm. 3. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

233

5.19.32

IPC_7147_00004 - pmCTDBInitFailure

A Performance Measurements Counter Type Database (CTDB) initialization failure has occurred. pmCTDBInitFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7147_00004 IPC IPC processing error softwareError MAJOR The Performance Management (PM) server will halt. Software error 1. At the FMS, make sure that the environment variable ( CTDB_FILE_PATH) is set correctly. 2. Make sure that CounterTypeConf.xml file is readable. The text in the file provides more specific information to take the appropriate action. 3. At the FMS, manually clear the alarm. 4. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

234

5.19.33

IPC_7148_00004 - primary_Clock_Source_Disconnected

IPC primary clock source is disconnected primary_Clock_Source_Disconnected Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7148_00004 IPC IPC equipment receiverFailure CRITICAL Loss of synchronization depending on back-up strategy. Receiver failure. 1. Check whether loss of STM-1 traffic has also occurred and report a network failure. 2. Make sure that the primary clock source has switched to back-up. 3. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

235

5.19.34

IPC_7159_00004 - secondSRSTCPEstFailure

The SRS or the SRS Concentrator could be down or the link is broken secondSRSTCPEstFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7159_00004 IPC IPC communications communicationsSubsystemFailure MAJOR

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

236

5.19.35

IPC_7164_00004 - suActivationFailure

A Software Update activation failure has occurred suActivationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7164_00004 IPC IPC processing error softwareError CRITICAL The system may not function properly because the new software is not activated yet. Software error Perform the following procedure to clear the suActivationFailure (IPC_7164_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

237

IPC_7164_00004 - suActivationFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... Then..

The error is Go to step 3. Go to step 3. SU_Activation_System_Coord_failur e The error is SU_Activation_Operational_Failure Go to step 4. Go to step 4.

The error is Go to step 4. Go to step 4. SU_Activation_DataMigration_Failur e The error is SU_Activation_ICC_Update_Failure The error is SU_Activation_SB_Update_Failure Go to step 4. Go to step 4.

Go to step 4. Go to step 4.

3. Identify the process and try again after making sure no other process holds the permission. 4. Check the SU log (/var/spool/fm/log/logSU) and/or data migration process log(/var/spool/dm/logs) to look for any exceptions that were raised during software execution. 5. Deliver a printout of the SU log information to Alcatel-Lucent customer support. If possible, also report details of the circumstances that caused the error. 6. Prepare and fall back to the previous version of the software. 7. At the FMS, manually clear the alarm. 8. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

238

--End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

239

5.19.36

IPC_7165_00004 - suApplyFailure

A Software Update apply failure has occurred suApplyFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7165_00004 IPC IPC processing error softwareError MAJOR The system may not function properly because the new software is not activated yet. Software error Perform the following procedure to clear the suApplyFailure (IPC_7165_00004) alarm.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

240

IPC_7165_00004 - suApplyFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... The error is SU_Apply_ Operational_Failure The error is SU_Apply_Failure Then.. Go to step 3. Go to step 3.

Go to step 5. Go to step 5.

3. Check the SU log (/var/spool/fm/log/logSU) and/or data migration process log(/var/spool/dm/logs) to look for any exceptions that were raised during software execution. 4. Deliver a printout of the SU log information to Alcatel-Lucent customer support. If possible, also report details of the circumstances that caused the error. 5. Check the SUF log (/var/flx//logs/FMSsugr/latest) and/or data migration process log(/var/spool/dm/logs) to identify the problem. 6. Attempt the suApply command again. If this fails, then an suDe-Spply command is required to undo any changes made by suApply 7. At the FMS, manually clear the alarm. 8. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

241

5.19.37

IPC_7166_00004 - suBackoutFailure

A Software Update backout failure has occurred suBackoutFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7166_00004 IPC IPC processing error softwareError CRITICAL The system may not function properly because the new backout to the old software was not successful. Software error Perform the following procedure to clear the suBackoutFailure (IPC_7166_00004) alarm.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

242

IPC_7166_00004 - suBackoutFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... The error is SU_Backout_System_Coord_failure The error is SU_Backout_Operational_Failure The error is SU_Backout_DataMigration_Failure The error is SU_Backout_ESC_Update_Failure The error is SU_Backout_AC_Update_Failure The error is SU_Backout_ICC_Update_Failure The error is SU_Backout_SB_Update_Failure Then.. Go to step 3. Go to step 3.

Go to step 4. Go to step 4.

Go to step 4. Go to step 4.

Go to step 4. Go to step 4.

Go to step 6. Go to step 6.

Go to step 4. Go to step 4.

Go to step 4. Go to step 4.

3. Identify the process and try again after making sure no other process holds the permission. 4. Check the SU log (/var/spool/fm/log/logSU) and/or data migration process log(/var/spool/dm/logs) to look for any exceptions that were raised during software execution. 5. Deliver a printout of the SU log information to Alcatel-Lucent customer support. If possible, also report details of the circumstances that caused the error. 6. Prepare and fall back to the previous version of the software. 7. At the FMS, manually clear the alarm.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

243

8. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

244

5.19.38

IPC_7167_00004 - suCommitFailure

A Software Update commit failure has occurred. suCommitFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7167_00004 IPC IPC processing error softwareError MAJOR The system may not function properly because the new software is not committed yet. Software error Perform the following procedure to clear the suCommitFailure (IPC_7167_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

245

IPC_7167_00004 - suCommitFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... The error is SU_Commit_Operational_Failure The error is SU_Software_Commit_Failure Then.. Go to step 3. Go to step 3.

Go to step 4. Go to step 4.

3. Check the SU log (/var/spool/fm/log/logSU) to look for any exceptions that were raised during software download. 4. Check the SUF logs (/var/flx/logs/FMSsugr/latest) to identify the problem. 5. Check the SU logs to see if these SUF commands could be invoked on remote SBs by SU. 6. At the FMS, manually clear the alarm. 7. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

246

5.19.39

IPC_7168_00004 - suDeApplyFailure

A Software Update de-apply failure has occurred suDeApplyFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7168_00004 IPC IPC processing error softwareError MAJOR The system may not function properly because the software update de-apply request has failed. Software error Perform the following procedure to clear the suDeApplyFailure (IPC_7168_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

247

IPC_7168_00004 - suDeApplyFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... The error is SU_DeApply_Operational_Failure The error is SU_DeApply_Failure Then.. Go to step 3. Go to step 3.

Go to step 5. Go to step 5.

3. Check the SU log (/var/spool/fm/log/logSU) and/or data migration process log(/var/spool/dm/logs) to look for any exceptions that were raised during software execution. 4. Deliver a printout of the SU log information to Alcatel-Lucent customer support. If possible, also report details of the circumstances that caused the error. 5. Check the SUF log (/var/flx//logs/FMSsugr/latest) and/or data migration process log(/var/spool/dm/logs) to identify the problem. 6. Attempt the suDeApply command again. 7. At the FMS, manually clear the alarm. 8. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

248

5.19.40

IPC_7169_00004 - suDeleteFailure

A Software Update delete failure has occurred. suDeleteFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7169_00004 IPC IPC processing error softwareError MAJOR No system impact. Because the SU was not deleted, no additional disk space is created for new software updates. Software error Perform the following procedure to clear the suDeleteFailure (IPC_7169_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

249

IPC_7169_00004 - suDeleteFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... The error is SU_Delete_Operational_Failure The error is SU_Software_Delete_Failure Then.. Go to step 3. Go to step 3.

Go to step 4. Go to step 4.

3. Check the SU log (/var/spool/fm/log/logSU) to look for any exceptions that were raised during software download. 4. Check the SUF logs (/var/flx/logs/FMSsugr/latest) to identify the problem. 5. Check the SU logs to see if these SUF commands could be invoked on remote SBs by SU. 6. At the FMS, manually clear the alarm. 7. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

250

5.19.41

IPC_7170_00004 - suDownloadFailure

A Software Update download failure has occurred. suDownloadFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7170_00004 IPC IPC processing error softwareError minor The new software is not downloaded yet and the system may not function properly. Software error Perform the following procedure to clear the suDownloadFailure (IPC_7170_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

251

IPC_7170_00004 - suDownloadFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... The error is SU_Download_Operational_Failure The error is SU_Download_FTP_Failure Then.. Go to step 3. Go to step 3.

Go to step 4. Go to step 4.

The error is Go to step 5. Go to step 5. SU_Download_RemoteCopy_Failure

3. Check the SU log (/var/spool/fm/log/logSU) a to see for any exceptions that were raised during software download. 4. Check the SFTP user name and password. 5. Check whether the host names and the IP addresses of the SBs are correct. 6. At the FMS, manually clear the alarm. 7. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

252

5.19.42

IPC_7171_00004 - suFallbackFailure

A Software Update fallback failure has occurred suFallbackFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7171_00004 IPC IPC processing error softwareError CRITICAL The system may not function properly because the fallback to the old software was not successful. Software error Perform the following procedure to clear the suFallbackFailure (IPC_7171_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

253

IPC_7171_00004 - suFallbackFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... Then..

The error is Go to step 3. Go to step 3. SU_Fallback_System_Coord_failure The error is SU_Fallback_ Operational_Failure The error is SU_Fallback_ICC_Update_Failure The error is SU_Fallback_SB_Update_Failure Go to step 6. Go to step 6.

Go to step 4. Go to step 4.

Go to step 4. Go to step 4.

3. Identify the process and try again after making sure no other process holds the permission. 4. Check the SU log (/var/spool/fm/log/logSU) and/or data migration process log(/var/spool/dm/logs) to look for any exceptions that were raised during software execution. 5. Deliver a printout of the SU log information to Alcatel-Lucent customer support. If possible, also report details of the circumstances that caused the error. 6. Prepare and fall back to the previous version of the software. 7. At the FMS, manually clear the alarm. 8. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

254

5.19.43

IPC_7172_00004 - suICCPartialUpdateFailure

A Software Update ICC cluster partial update failure has occurred suICCPartialUpdateFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7172_00004 IPC IPC processing error softwareError minor The system may not function properly because the software update request has failed Software error Perform the following procedure to clear the suICCPartialUpdateFailure (IPC_7172_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

255

IPC_7172_00004 - suICCPartialUpdateFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... The error is SU_ICCPartialUpdated_Operational_Failure The error is SU_ICCPartialUpdated_Failure Then.. Go to step 3. Go to step 3.

Go to step 5. Go to step 5.

3. Check the SU log (/var/spool/fm/log/logSU) and/or data migration process log(/var/spool/dm/logs) to look for any exceptions that were raised during software execution. 4. Deliver a printout of the SU log information to Alcatel-Lucent customer support. If possible, also report details of the circumstances that caused the error. 5. Check the SUF log (/var/flx//logs/FMSsugr/latest) and/or data migration process log(/var/spool/dm/logs) to identify the problem. Also check in the SU log if the SUF commands can be invoked on on remote Solaris Blades by Software Update. 6. At the FMS, manually clear the alarm. 7. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

256

5.19.44

IPC_7173_00004 - suInfoSyncFailure

A software update Info Sync failure has occurred suInfoSyncFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7173_00004 IPC IPC processing error softwareError minor The system may not function properly because the software update info sync request has failed Software error Perform the following procedure to clear the suInfoSyncFailure (IPC_7173_00004) alarm.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

257

IPC_7173_00004 - suInfoSyncFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... Then..

The error is SU_InfoSync_Operational_Failure Go to step 3. Go to step 3. The error is SU_Infosync_Failure Go to step 5. Go to step 5.

3. Check the SU log (/var/spool/fm/log/logSU) and/or data migration process log(/var/spool/dm/logs) to look for any exceptions that were raised during software execution. 4. Deliver a printout of the SU log information to Alcatel-Lucent customer support. If possible, also report details of the circumstances that caused the error. 5. Check the SUF log (/var/flx//logs/FMSsugr/latest) and/or data migration process log(/var/spool/dm/logs) to identify the problem. Also check in the SU log if the SUF commands can be invoked on on remote Solaris Blades by Software Update. 6. Attempt the infosync command again. There may be some mismatch between the SU state file and the database 7. At the FMS, manually clear the alarm. 8. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

258

5.19.45

IPC_7174_00004 - suInstallFailure

A Software Update install failure has occurred suInstallFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7174_00004 IPC IPC processing error softwareError minor The new software is not installed yet and the system may not function properly.

Reason Remedial Action Perform the following procedure to clear the suInstallFailure (IPC_7174_00004) alarm.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

259

IPC_7174_00004 - suInstallFailure Remedial action Step Action

1. Obtain the error type using the "Retrieve IPC log files" procedure. 2. Check the error related to this alarm. If... The error is SU_Install_Operational_Failure The error is SU_Install_Failure Then.. Go to step 3. Go to step 3.

Go to step 4. Go to step 4.

3. Check the SU log (/var/spool/fm/log/logSU) to look for any exceptions that were raised during software download. 4. Check the SUF logs (/var/flx/logs/FMSsugr/latest) to identify the problem. 5. Check the SU logs to see if these SUF commands could be invoked on remote SBs by SU. 6. At the FMS, manually clear the alarm. 7. If the problem persists, contact Alcatel-Lucent customer support. --End--

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

260

5.19.46

IPC_7176_00004 - suStatePanicFailure

A Software Update state panic failure has occurred suStatePanicFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7176_00004 IPC IPC processing error softwareError CRITICAL New software could not be loaded onto the system. Software error 1. Repeat the pre-check operation and continue with the software update procedure. 2. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

261

5.20

IuCS alarms
The following alarms are generated by the IuCS. IPC_7154_00011 - remoteSubsystemOutOfService

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

262

5.20.1

IPC_7154_00011 - remoteSubsystemOutOfService

The remote subsystem has gone out of service remoteSubsystemOutOfService Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7154_00011 IPC/IuCS IuCS processing error applicationSubsystemFailure CRITICAL Existing circuit switched calls are dropped. New circuit switched calls are refused. Application subsystem failure 1. At the FMS, if "SS7_MTP3_PAUSE" is pending, react on this one. If the alarm is cleared, the procedure is completed. 2. At the FMS, check the state of the remote NE. 3. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

263

5.21

IuCSIP alarms
The following alarms are generated by the Iu-CS interface over the IP network. IPC_7121_00012 - m3uaLocalASFailure IPC_7122_00012 - m3uaRemoteASFailure IPC_7154_00012 - remoteSubsystemOutOfService IPC_7186_00012 - overloadLevel1 IPC_7187_00012 - overloadLevel2 IPC_7188_00012 - overloadLevel3

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

264

5.21.1

IPC_7121_00012 - m3uaLocalASFailure

Local Application Server has failed to comeup at M3UA Local IPSP bringup procedure failed towards the peer m3uaLocalASFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7121_00012 IPC/IuCSIP IuCSIP processing error applicationSubsystemFailure MAJOR Local IPSP bring up procedure has failed towards the peer. Possible causes is application Subsystem failure. 1. The IuCSIP_m3uaLocalASFailure alarm is automatically cleared when the M3UA ASPSM and ASPTM procedure is successfully acknowledged by the peer.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

265

5.21.2

IPC_7122_00012 - m3uaRemoteASFailure

Remote Application Server has failed to comeup at M3UARemote IPSP bringup procedure failed towards the peer. m3uaRemoteASFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7122_00012 IPC/IuCSIP IuCSIP processing error applicationSubsystemFailure MAJOR Remote IPSP bring up procedure has failed towards the peer. Probable cause is application Subsystem Failure. 1. The IuCSIP_m3uaRemoteASFailure alarm is automatically cleared when the M3UA ASPSM and ASPTM messages from the peer has successfully reached the IPC.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

266

5.21.3

IPC_7154_00012 - remoteSubsystemOutOfService

The remote subsystem has gone out of service remoteSubsystemOutOfService Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7154_00012 IPC/IuCSIP IuCSIP processing error applicationSubsystemFailure CRITICAL Existing circuit switched calls are dropped. New circuit switched calls are refused. Possible causes is application Subsystem failure. 1. The IuCSIP_remoteSubsystemOutOfService alarm is automatically cleared when the remote subsystem of SCCP (i.e. RANAP) is reachable.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

267

5.21.4

IPC_7186_00012 - overloadLevel1

The cluster is in overload level 1. No new RAB Establishments are allowed from this cluster. However, emergency calls are can be made and existing calls will continue.Signalling Processor entered into overload condition. overloadLevel1 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7186_00012 IPC/IuCSIP IuCSIP processing error resourceAtOrNearingCapacity MAJOR

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

268

5.21.5

IPC_7187_00012 - overloadLevel2

The cluster is in overload level 2. No new SCCP connections and RAB Establishments including emergency calls are allowed from this cluster. However, the existing calls can continue.Signalling Processor has entered into overload for a while or Traffic Processor has entered into overload. overloadLevel2 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7187_00012 IPC/IuCSIP IuCSIP processing error resourceAtOrNearingCapacity CRITICAL

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

269

5.21.6

IPC_7188_00012 - overloadLevel3

The cluster is in overload level 3. No new messages are allowed from this cluster. This may affect the existing calls too.Signalling Processor has entered into heavy overload condition. overloadLevel3 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7188_00012 IPC/IuCSIP IuCSIP processing error resourceAtOrNearingCapacity CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

270

5.22

PeerIPSP alarms
The following alarms are generated by the PeerIPSP. IPC_7120_00030 - m3UAIPSPFailure IPC_7158_00030 - sCTPAssociationFailure IPC_7184_00030 - partialSCTPAssociationFailure IPC_7185_00030 - partialM3UAIPSPFailure

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

271

5.22.1

IPC_7120_00030 - m3UAIPSPFailure

The M3UA IPSP procedure failed to bringup the PeerIPSP to Active State via all the IPC's local endpoints. m3UAIPSPFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7120_00030 IPC/SS7Stack/PeerIPSP PeerIPSP processing error communicationsSubsystemFailure MAJOR The state of either a local IPSP or its remote peer is changed to DOWN or INACTIVE. Communications subsystem failure. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

272

5.22.2

IPC_7158_00030 - sCTPAssociationFailure

The SCTP Association has failed towards this PeerIPSP via all the IPC's localendpoints. sCTPAssociationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7158_00030 IPC/SS7Stack/PeerIPSP PeerIPSP communications communicationsSubsystemFailure MAJOR If more than one Association is defined towards the peer, service can continue using other Association(s) but if only one Association exists the communication with the peer is down. communications Subsystem failure 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

273

5.22.3

IPC_7184_00030 - partialSCTPAssociationFailure

In distributed environment, this alarm indicates that the SCTP Association has failed towards this PeerIPSP via one of the IPC's local endpoints (i.e. SS7StackInstance). partialSCTPAssociationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7184_00030 IPC/SS7Stack/PeerIPSP PeerIPSP communications communicationsSubsystemFailure MAJOR

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

274

5.22.4

IPC_7185_00030 - partialM3UAIPSPFailure

In distributed environment, this alarm indicates that M3UA IPSP procedure failed to bringup the PeerIPSP to Active State via one of the IPC's local endpoints (i.e. SS7StackInstance). No response from the BSG for the M3UA level messages. partialM3UAIPSPFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7185_00030 IPC/SS7Stack/PeerIPSP PeerIPSP processing error communicationsSubsystemFailure MAJOR

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

275

5.23

PG alarms
The following alarms are generated by the Protect Group. IPC_7007_00045 - apsCriticalLineFailure IPC_7008_00045 - apsCriticalProcessorFailure IPC_7009_00045 - apsMajorLineFailure IPC_7010_00045 - apsMajorProcessorFailure IPC_7011_00045 - apsMinorLineFailure IPC_7012_00045 - apsMinorProcessorFailure

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

276

5.23.1

IPC_7007_00045 - apsCriticalLineFailure

A critical Automatic Protection Switching (APS) line failure has occurred apsCriticalLineFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7007_00045 IPC/PG PG processing error underlyingResourceUnavailable CRITICAL The service will be interrupted. Data cannot be received. Underlying resource unavailable 1. Open a SSH session to the IPC. 2. At the IPC, unlock the working line. 3. At the IPC, unlock the protected line. 4. Request Alcatel-Lucent customer support to clear the lockout of protection so the protected line can provide service.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

277

5.23.2

IPC_7008_00045 - apsCriticalProcessorFailure

A critical Automatic Protection Switching (APS) processor failure has occurred apsCriticalProcessorFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7008_00045 IPC/PG PG processing error underlyingResourceUnavailable CRITICAL No protocol processing can be performed. Underlying resource unavailable 1. Open a SSH session to the IPC. 2. At the IPC, unlock the working processor. 3. At the IPC, unlock the protected processor. 4. Request Alcatel-Lucent customer support to clear the lockout of protection so the protected processor can provide service.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

278

5.23.3

IPC_7009_00045 - apsMajorLineFailure

A major Automatic Protection Switching (APS) line failure has occurred apsMajorLineFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7009_00045 IPC/PG PG processing error underlyingResourceUnavailable MAJOR The service will be degraded. Data will be coming on a line that is degraded. Underlying resource unavailable 1. Open a SSH session to the IPC. 2. At the IPC, unlock the protected line. 3. At the IPC, unlock the working line. 4. Request Alcatel-Lucent customer support to clear the lockout of protection so the protected line can provide service.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

279

5.23.4

IPC_7010_00045 - apsMajorProcessorFailure

A major Automatic Protection Switching (APS) processor failure has occurred apsMajorProcessorFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7010_00045 IPC/PG PG processing error underlyingResourceUnavailable MAJOR Service will be degraded. Underlying resource unavailable 1. Open a SSH session to the IPC. 2. At the IPC, unlock the protected processor. 3. At the IPC, unlock the working processor. 4. Request Alcatel-Lucent customer support to clear the lockout of protection so the protected processor can provide service.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

280

5.23.5

IPC_7011_00045 - apsMinorLineFailure

A minor Automatic Protection Switching (APS) line failure has occurred apsMinorLineFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7011_00045 IPC/PG PG processing error underlyingResourceUnavailable minor The OC3 facility designated as protect line is prohibited from providing back-up service. It will switch to back-up line (protect line) or there will be no back-up. Underlying resource unavailable 1. Open a SSH session to the IPC. 2. At the IPC, unlock the protected line. 3. At the IPC, unlock the working line. 4. Request Alcatel-Lucent customer support to clear the lockout of protection so the protected line can provide service.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

281

5.23.6

IPC_7012_00045 - apsMinorProcessorFailure

A minor Automatic Protection Switching (APS) processor failure has occurred. apsMinorProcessorFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7012_00045 IPC/PG PG processing error underlyingResourceUnavailable minor Protocol processor designated as protect line is prohibited from providing back-up service. Underlying resource unavailable 1. At the IPC, unlock the protected processor. 2. At the IPC, unlock the working processor. 3. Request Alcatel-Lucent customer support to clear the lockout of protection so the protected processor can provide service.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

282

5.24

PSU alarms
The following alarms are generated by the Power Supply Unit . IPC_7032_00039 - equipmentFailure IPC_7133_00039 - overTemperature

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

283

5.24.1

IPC_7032_00039 - equipmentFailure

A power supply failure has been detected equipmentFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7032_00039 IPC/Cabinet/FBPShelf/PSU PSU equipment equipmentMalfunction CRITICAL The FPB shelf is powered off. Equipment malfunction Perform the following procedure to clear the equipmentFailure (IPC_7032_00039) alarm.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

284

IPC_7032_00039 - equipmentFailure Remedial action Step Action

1. At the FMS, check for circuit breaker alarms (Cabinet_fanOrCktBreakerFailure). 2. At the IPC, check if the power supply feed switch is in the ON position. 3. At the IPC, use the maintenance terminal to check if the PSU is inhibited. 4. If ... the PSU is inhibited, then ... un-inhibit the PSU.If the alarm is cleared, the procedure is completed. un-inhibit the PSU. If the alarm is cleared, the procedure is completed. inhibit and un-inhibit the PSU a few times.If the alarm is cleared, the procedure is completed. inhibit and uninhibit the PSU a few times. If the alarm is cleared, the procedure is completed.

the PSU is un-inhibited,

5. At the IPC, remove and reinsert the PSU. If the alarm is cleared, the procedure is completed. 6. At the IPC, replace the PSU. If the alarm is cleared, the procedure is completed. 7. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

285

5.24.2

IPC_7133_00039 - overTemperature

The temperature is above the specified limit. overTemperature Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7133_00039 IPC/Cabinet/FBPShelf/PSU PSU environment temperatureUnacceptable CRITICAL Increase in cabinet temperature could lead to possible component failure. Temperature unacceptable 1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly by replacing the unit. 6. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

286

5.25

RoutingTableEntry alarms
The following alarms are generated by the Routing Table. IPC_7006_00005 - anextHopNotReachable

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

287

5.25.1

IPC_7006_00005 - anextHopNotReachable

Several consecutive ARP Request messages were transmitted from the IPC; the node did notreceive an ARP response. anextHopNotReachable Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7006_00005 IPC/RoutingTableEntry RoutingTableEntry communications communicationsProtocolError CRITICAL Destination is not reachable. The link between GICC 1.1 and the router may have gone down or the router is not responding to the ARPs from GICC 1.1. Communications Protocol error 1. Check connectivity or status of the router connected to GICC 1.1.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

288

5.26

SB alarms
The following alarms are generated by the Solaris Blade . IPC_7030_00040 - degradeGroupMemberFault IPC_7067_00040 - failureGroupMemberFault IPC_7117_00040 - lossOfPower IPC_7118_00040 - lossOfSanity IPC_7119_00040 - lostCommunication IPC_7123_00040 - maintenanceMode IPC_7131_00040 - notInstalled IPC_7133_00040 - overTemperature

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

289

5.26.1

IPC_7030_00040 - degradeGroupMemberFault

A member of a degrade group faulted degradeGroupMemberFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7030_00040 IPC/Cabinet/FBPShelf/SB SB processing error underlyingResourceUnavailable MAJOR The SB is considered degraded. Underlying resource unavailable Perform the following procedure to clear the degradeGroupMemberFault (IPC_7030_00040) alarm.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

290

IPC_7030_00040 - degradeGroupMemberFault Remedial action Step Action

1. At the FMS, check for alarms on the objects: SBClan SBBPEtherPort

If there are alarms, perform the appropriate fault clearance procedure. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

291

5.26.2

IPC_7067_00040 - failureGroupMemberFault

A member of a failure group faulted failureGroupMemberFault Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7067_00040 IPC/Cabinet/FBPShelf/SB SB processing error underlyingResourceUnavailable MAJOR The SB is not operational. Underlying resource unavailable Perform the following procedure to clear the failureGroupMemberFault (IPC_7067_00040) alarm.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

292

IPC_7067_00040 - failureGroupMemberFault Remedial action Step Action

1. At the FMS, check for alarms on the object: SBProc

If there are alarms, perform the appropriate fault clearance procedure. If the alarm is cleared, the procedure is completed. 2. At the FMS, check for SBProc alarms for this SB and perform the appropriate fault clearance procedure. 3. If the problem persists, contact Alcatel-Lucent customer support. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

293

5.26.3

IPC_7117_00040 - lossOfPower

SB board has lost power lossOfPower Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7117_00040 IPC/Cabinet/FBPShelf/SB SB equipment powerProblem MAJOR None. Power problem 1. At the IPC, check whether the SB is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 2. At the IPC, if the SB is inserted in the correct slot, remove and reinsert the SB. If the alarm is cleared, the procedure is completed. 3. At the FMS, perform a reset type 1 on the SB object. 4. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

294

5.26.4

IPC_7118_00040 - lossOfSanity

Unit has lost sanity or integrity lossOfSanity Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7118_00040 IPC/Cabinet/FBPShelf/SB SB equipment equipmentMalfunction MAJOR None. Equipment malfunction 1. At the FMS, check if a maintenanceMode alarm is active. 2. At the IPC, check whether the SB is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 3. At the IPC, verify whether the healthy option is enabled. 4. At the FMS, reset the SB object. If the alarm is cleared, the procedure is completed. 5. Open a SSH session to the IPC. 6. At the IPC, lock the SB object. 7. At the IPC, replace the SB. 8. At the IPC, unlock the SB object. If the alarm is cleared, the procedure is completed. 9. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

295

5.26.5

IPC_7119_00040 - lostCommunication

AC board lost heartbeat communication to the SB board lostCommunication Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7119_00040 IPC/Cabinet/FBPShelf/SB SB communications lossOfSignal MAJOR None. Loss of signal 1. At the IPC, check if SB is inserted into correct slot and powered on. If the alarm is cleared, the procedure is completed. 2. At the IPC, if the SB is inserted in the correct slot, remove and reinsert the SB. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the SB object. 4. Open a SSH session to the IPC. 5. At the IPC, lock the SB object. 6. At the IPC, replace the SB. 7. At the IPC, unlock the SB object. 8. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

296

5.26.6

IPC_7123_00040 - maintenanceMode

SB board is in maintenance mode maintenanceMode Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7123_00040 IPC/Cabinet/FBPShelf/SB SB processing error configurationOrCustomizationError warning Alarm Card recovery for the SB is inhibited. Configuration Or customizing problem. 1. At the IPC, use the maintenance terminal to put the SB back into active mode. 2. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

297

5.26.7

IPC_7131_00040 - notInstalled

SB board is not installed in shelf slot. notInstalled Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7131_00040 IPC/Cabinet/FBPShelf/SB SB equipment equipmentMalfunction MAJOR No service from this SB. The specified SB is physically removed from the shelf or is not correctly inserted and the Alarm Card does not detect the SB. 1. At the IPC, if the SB is not inserted, insert the SB into the correct slot. If the alarm is cleared, the procedure is completed. 2. At the IPC, if the SB is inserted in the correct slot, remove and reinsert the SB. If the alarm is cleared, the procedure is completed. 3. At the FMS, reset the SB object. 4. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

298

5.26.8

IPC_7133_00040 - overTemperature

The temperature is above the specified limit overTemperature Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7133_00040 IPC/Cabinet/FBPShelf/SB SB environment temperatureUnacceptable MAJOR Increase in cabinet temperature could lead to possible component failure. Temperature unacceptable 1. At the FMS, check for and clear any associated fan alarms using the appropriate clearance procedures If the alarm is cleared, the procedure is completed. 2. At the IPC, check for obstructions in the air flow pathways. 3. At the IPC, check if the Rear Transition Module (RTM) is correctly installed. 4. At the IPC, check if any empty card slots have missing or incorrectly installed filler plates. 5. At the IPC, verify that the temperature sensors are functioning correctly by replacing the card. 6. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

299

5.27

SBBPEtherPort alarms
The following alarms are generated by the SBBPEtherPort. IPC_7104_00023 - linkFailure

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

300

5.27.1

IPC_7104_00023 - linkFailure

Minor hardware unit has failed linkFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7104_00023 IPC/Cabinet/FBPShelf/SB/SBBPEtherPort SBBPEtherPort equipment equipmentMalfunction minor Reduced FTM functionality. Equipment malfunction 1. At the IPC, replace the FTM. 2. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

301

5.28

SBClan alarms
The following alarms are generated by the SB cluster LAN object. IPC_7104_00024 - linkFailure

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

302

5.28.1

IPC_7104_00024 - linkFailure

One of the SB Cluster LAN interfaces has failed linkFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7104_00024 IPC/Cabinet/FBPShelf/SB/SBClan SBClan communications lANError minor

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

303

5.29

SBProc alarms
The following alarms are generated by the SBProc. IPC_7001_00025 - acCommunicationFailure IPC_7022_00025 - componentMissing IPC_7026_00025 - cpuUsageOverload IPC_7031_00025 - diskReadTimeExceeded IPC_7072_00025 - filesystem01Full IPC_7073_00025 - filesystem02Full IPC_7074_00025 - filesystem03Full IPC_7075_00025 - filesystem04Full IPC_7076_00025 - filesystem05Full IPC_7077_00025 - filesystem06Full IPC_7078_00025 - filesystem07Full IPC_7079_00025 - filesystem08Full IPC_7080_00025 - filesystem09Full IPC_7081_00025 - filesystem10Full IPC_7082_00025 - filesystem11Full IPC_7083_00025 - filesystem12Full IPC_7084_00025 - filesystem13Full IPC_7085_00025 - filesystem14Full IPC_7086_00025 - filesystem15Full IPC_7087_00025 - filesystem16Full IPC_7088_00025 - fLXEV_CLAN_PARENT_FAIL IPC_7089_00025 - fLXEV_NODE_FAILING IPC_7090_00025 - fLXEV_NODE_NOTACTIVE IPC_7091_00025 - fLXEV_SMON_NOHBEAT IPC_7116_00025 - lossOfClockSourceSync IPC_7125_00025 - memoryUsageOverload IPC_7130_00025 - nodeFailure IPC_7133_00025 - overTemperature IPC_7149_00025 - processFailure IPC_7150_00025 - processFailureApplication IPC_7157_00025 - rootLoginFailure

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

304

IPC_7160_00025 - shutdownTempReached IPC_7175_00025 - sULoginFailure IPC_7178_00025 - temperatureOffLimits IPC_7179_00025 - userLoginFailure IPC_7180_00025 - virtualClusterFailure IPC_7181_00025 - virtualClusterVirtualMachineFailure

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

305

5.29.1

IPC_7001_00025 - acCommunicationFailure

Communication to the Alarm Card (AC) has failed. acCommunicationFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7001_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc communications communicationsSubsystemFailure minor None, the other AC takes over. Alarm Card hardware failure. 1. At the FMS, check the status of the Alarm Card. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

306

5.29.2

IPC_7022_00025 - componentMissing

A SB component is missing componentMissing Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7022_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc equipment equipmentMalfunction minor None. Equipment malfunction. 1. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

307

5.29.3

IPC_7026_00025 - cpuUsageOverload

The processor is in CPU usage overload cpuUsageOverload Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7026_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc quality of service thresholdCrossed minor Reduced throughput on the SB. System audits will be inhibited. The threshold for CPU usage overload of the processor on the SB is exceeded. 1. At the FMS, reduce the processing load. 2. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

308

5.29.4

IPC_7031_00025 - diskReadTimeExceeded

Excessive disk read time encountered due to degraded disk diskReadTimeExceeded Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7031_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc equipment timingProblem MAJOR Could lead to FMS Blade failure & loss of call processing. Degraded disk in FMS Blade. 1. Operator should ensure that a spare FMS Blade is available 2. After one hour, if alarm still exists, the disk access failure still occurring. FMS Blade must be replaced. 3. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

309

5.29.5

IPC_7072_00025 - filesystem01Full

One of the file systems has exceeded its threshold for percentage of space used filesystem01Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7072_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

310

5.29.6

IPC_7073_00025 - filesystem02Full

One of the file systems has exceeded its threshold for percentage of space used filesystem02Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7073_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

311

5.29.7

IPC_7074_00025 - filesystem03Full

One of the file systems has exceeded its threshold for percentage of space used filesystem03Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7074_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

312

5.29.8

IPC_7075_00025 - filesystem04Full

One of the file systems has exceeded its threshold for percentage of space used filesystem04Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7075_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

313

5.29.9

IPC_7076_00025 - filesystem05Full

One of the file systems has exceeded its threshold for percentage of space used filesystem05Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7076_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

314

5.29.10

IPC_7077_00025 - filesystem06Full

One of the file systems has exceeded its threshold for percentage of space used filesystem06Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7077_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

315

5.29.11

IPC_7078_00025 - filesystem07Full

One of the file systems has exceeded its threshold for percentage of space used filesystem07Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7078_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

316

5.29.12

IPC_7079_00025 - filesystem08Full

One of the file systems has exceeded its threshold for percentage of space used filesystem08Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7079_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

317

5.29.13

IPC_7080_00025 - filesystem09Full

One of the file systems has exceeded its threshold for percentage of space used filesystem09Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7080_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

318

5.29.14

IPC_7081_00025 - filesystem10Full

One of the file systems has exceeded its threshold for percentage of space used filesystem10Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7081_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

319

5.29.15

IPC_7082_00025 - filesystem11Full

One of the file systems has exceeded its threshold for percentage of space used filesystem11Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7082_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

320

5.29.16

IPC_7083_00025 - filesystem12Full

One of the file systems has exceeded its threshold for percentage of space used filesystem12Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7083_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

321

5.29.17

IPC_7084_00025 - filesystem13Full

One of the file systems has exceeded its threshold for percentage of space used filesystem13Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7084_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

322

5.29.18

IPC_7085_00025 - filesystem14Full

One of the file systems has exceeded its threshold for percentage of space used filesystem14Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7085_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

323

5.29.19

IPC_7086_00025 - filesystem15Full

One of the file systems has exceeded its threshold for percentage of space used filesystem15Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7086_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

324

5.29.20

IPC_7087_00025 - filesystem16Full

One of the file systems has exceeded its threshold for percentage of space used filesystem16Full Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7087_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error storageCapacityProblem MAJOR None immediately, but if the space continues to fill up, there will be adverse effects on the cPSB, possibly leading to the cPSB rebooting. The file system is filling up. 1. Contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

325

5.29.21

IPC_7088_00025 - fLXEV_CLAN_PARENT_FAIL

Both of the SB Cluster LAN interfaces have failed fLXEV_CLAN_PARENT_FAIL Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7088_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc communications lANError CRITICAL The FMS will reinitialize. As a result an automatic reboot will be performed. Both cluster LAN interfaces failed. 1. At the IPC, if the automatic reboot failed, perform a manual reboot. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

326

5.29.22

IPC_7089_00025 - fLXEV_NODE_FAILING

The node is re-initializing fLXEV_NODE_FAILING Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7089_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error softwareError MAJOR The FMS is not available. Software error 1. At the FMS, wait until the SB object availability state indication 'failed' or 'degraded' has disappeared. Note: It can take some time before the SB becomes available. 2. At the FMS, perform an IPC topology and an IPC status audit. 3. At the FMS, manually clear the alarm. 4. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

327

5.29.23

IPC_7090_00025 - fLXEV_NODE_NOTACTIVE

This alarm occurs when the machine has not reached the Active state within a given amount of time fLXEV_NODE_NOTACTIVE Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7090_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc equipment equipmentMalfunction MAJOR The FMS is not available or is stuck in the RCC Standby state. Equipment malfunction 1. At the IPC, reset or power-cycle the watchdog. If the alarm is cleared, the procedure is completed. 2. At the IPC, replace the watchdog card. If the alarm is cleared, the procedure is completed. 3. At the FMS, perform a reset type 2 on the SB object to reboot the FMS. 4. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

328

5.29.24

IPC_7091_00025 - fLXEV_SMON_NOHBEAT

Infrastructure software has failed fLXEV_SMON_NOHBEAT Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7091_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error softwareProgramAbnormallyTerminated MAJOR The system cannot report some alarm and state changes. As a result, the audit process will attempt to correct any incorrect state, status and alarms. The software program has abnormally terminated. 1. At the FMS, perform a reset type 2 on the SB object to reboot the FMS. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

329

5.29.25

IPC_7116_00025 - lossOfClockSourceSync

Time synchronization has been lost with the external clock source (NTP Server). lossOfClockSourceSync Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7116_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc equipment timingProblem MAJOR The SB loses synchronization with the external clock. Cards that use this SB as NTP client, will also loose time synchronization.This means timing related functions such as timestamps are not correct or accurate anymore.also scheduled tasks ?? Possible root causes: Remedial Action External clock failure Timing problem

Reason

1. At the IPC, execute command: flxsyncdate #b 2. Check the status of the NTP server.This can be an external NTP server or SB card ? 3. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

330

5.29.26

IPC_7125_00025 - memoryUsageOverload

The processor is in memory usage overload memoryUsageOverload Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7125_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc quality of service thresholdCrossed MAJOR Memory overload may degrade the system performance. The threshold for memory usage overload of the processor on the SB is exceeded. 1. Examine all applications in memory on the overloaded SB for processes using an abnormally large amount of memory or lots of unexpected processes (e.g., a large number of user scripts). An example of a command to look at applications and their size would be: /usr/bin/ps -ef -A -opid,vsz,comm 2. Check /tmp and /var/run for unneeded files which can be cleaned up. 3. Check that the SB is equipped with 2.5 GB of memory. One way to check this is by using prtconf: /usr/sbin/prtconf | grep Memory 4. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

331

5.29.27

IPC_7130_00025 - nodeFailure

A node has failed and is in the process of reinitializing nodeFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7130_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error softwareError MAJOR The FMS is not available. Software error 1. At the FMS, wait until the SB object availability state indication 'failed' or 'degraded' has disappeared. Note: It can take some time before the SB becomes available. 2. At the FMS, perform an IPC topology and an IPC status audit. 3. At the FMS, manually clear the alarm. 4. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

332

5.29.28

IPC_7133_00025 - overTemperature

High temperature detected overTemperature Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7133_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc equipment temperatureUnacceptable MAJOR None. Temperature unacceptableDefault Warning temperature is 60 Default Critical temperature is 65Default Shutdown temperature is 70 1. Check temperature outside RNC cabinet (broken airconditioning, open doors)At the IPC, check if the airflow over the SB card or the cabinet is obstructed and if so, remove obstructions. If the alarm is cleared, the procedure is completed. 2. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

333

5.29.29

IPC_7149_00025 - processFailure

A process that is contained in one of the SB Platform VMs (CVM, NCVM, or VCVM) has failed and cannot be restarted, i.e. it has reached its process restart threshold processFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7149_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error softwareProgramAbnormallyTerminated minor The associated process is not functional. As a result, presumably the RCC will try to restart the process. Software program abnormally terminated. 1. At the FMS, perform a reset type 2 on the SB object. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

334

5.29.30

IPC_7150_00025 - processFailureApplication

An application process has terminated and cannot be recovered/restarted processFailureApplication Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7150_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error softwareProgramAbnormallyTerminated MAJOR The system function performed by this process will not occur. Software program abnormally terminated. Perform the following procedure to clear the processFailureApplication (IPC_7150_00025) alarm.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

335

IPC_7150_00025 - processFailureApplication Remedial action Step Action

1. To determine whether the process as indicated in the alarm text has since been restored, telnet into any FMS blade. Log in as root. fms01 or fms02 are preferable as these are OAM blades. 2. Run the following command: $ /flx/bin/rnccheckservers 3. Check for the following output, indicating that all processes are active AVAILABLE: xxxx UNAVAILABLE: 0 INITIALIZED: 0 RECOVERING: 0 AMW domain is completely up; all servers are AVAILABLE! Note: xxxx represents the total number of components scanned by the tool. This value is not important here and can be ignored. 4. If ... the output detailed in the previous step is displayed, indicating that the process has been restored, If any other output is displayed, then ... Go to step 8. Go to step 8.

Go to Step 5. Go to Step 5.

5. Search the output to determine whether the process identified by the alarm has an entry such as: AVAIL OAMSignalTranslator.1 OAMSignalTranslatorCapsule fms01 ACT The third entry (OAMSignalTranslatorCapsule in this case) will match the name of the software process in the alarm reportNote: There may be one or more entries for a single software process, as in this example:AVAIL SMLCProxy200.1 SMLCProxyCapsule fms01 ACT AVAIL SMLCProxy200.2 SMLCProxyCapsule fms02 STBYIf there is more than one entry matching a capsule name (SMLCProxyCapsule in this case), ALL entries must be AVAIL in order for the software process to be considered available. 6. If ... If the process is shown to be availthen ... Go to step 8. Go to step 8.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

336

If ... able (AVAIL), If the process is NOT shown to be available (AVAIL),

then ...

Go to Step 7. Go to Step 7.

7. Attempt to manually restart the process. If the problem persists, contact Alcatel-Lucent customer support. Note: If the rnccheckservers did NOT indicate all processes active and there is not a known problem explaining the failed processes or components, it may be advisable to contact Alcatel-Lucent customer support. 8. Manually clear the alarm. 9. Exit the telnet session. --End--

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

337

5.29.31

IPC_7157_00025 - rootLoginFailure

The number of failed root login attempts has exceeded a preset threshold rootLoginFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7157_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc unknown unauthorizedAccessAttempt minor None. Invalid password entered. 1. Review the security log file for suspicious access behavior. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

338

5.29.32

IPC_7160_00025 - shutdownTempReached

Shutdown temperature reached shutdownTempReached Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7160_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc equipment temperatureUnacceptable MAJOR

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

339

5.29.33

IPC_7175_00025 - sULoginFailure

The number of failed su login attempts has exceeded a preset threshold sULoginFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7175_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc unknown unauthorizedAccessAttempt minor None. Invalid user ID or password entered. 1. Review the security log file for suspicious access behavior. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

340

5.29.34

IPC_7178_00025 - temperatureOffLimits

The CPU temperature sensor has exceeded the Off-Limits threshold value. temperatureOffLimits Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason IPC_7178_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc environment temperatureUnacceptable MAJOR None. The CPU Vicinity temperature sensor on the Solaris Blade has detected a temperature that exceeds the off-limits threshold value.Default Warning temperature is 60 Default Critical temperature is 65Default Shutdown temperature is 70 1. At the IPC, check the status of the cooling system. 2. If the problem persists, contact Alcatel-Lucent customer support.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

341

5.29.35

IPC_7179_00025 - userLoginFailure

User Login Failure. Number of failed user login attempts has exceeded the limit. userLoginFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7179_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc unknown unauthorizedAccessAttempt minor None. Invalid user ID or password entered. 1. Review the security log file for suspicious access behavior. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

342

5.29.36

IPC_7180_00025 - virtualClusterFailure

One instance of a SB Platform VCVM has failed, and the other instance has either failed or has been taken offline virtualClusterFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7180_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error softwareProgramAbnormallyTerminated MAJOR The associated process is not functional. As a result, presumably the RCC will try to restart the process. Software program abnormally terminated. 1. At the FMS, perform a reset type 2 on the SB object. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

343

5.29.37

IPC_7181_00025 - virtualClusterVirtualMachineFailure

An instance of a SB Platform VCVM has failed virtualClusterVirtualMachineFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7181_00025 IPC/Cabinet/FBPShelf/SB/SBProc SBProc processing error softwareProgramAbnormallyTerminated minor The associated process is not functional. Software program abnormally terminated. 1. At the FMS, perform a reset type 2 on the SB object. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

344

5.30

SS7Link alarms
The following alarms are generated by the SS7Link. IPC_7127_00031 - mtp3LinkDown IPC_7128_00031 - mtp3LinkRemotelyBlocked IPC_7151_00031 - qsaalLinkCongested

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

345

5.30.1

IPC_7127_00031 - mtp3LinkDown

MTP3 Link is down mtp3LinkDown Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7127_00031 IPC/SS7Stack/SS7LinkSet/SS7Link SS7Link communications communicationsSubsystemFailure MAJOR Capacity is diminished, possible affecting performance. If there is more than one link in a linkset, all the traffic is now using the remaining link(s) in the linkset. Communication subsystem failure 1. Check physical connectivity or lower layer configuration. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

346

5.30.2

IPC_7128_00031 - mtp3LinkRemotelyBlocked

The peer node has blocked the traffic on this MTP3 link mtp3LinkRemotelyBlocked Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7128_00031 IPC/SS7Stack/SS7LinkSet/SS7Link SS7Link communications remoteNodeTransmissionError minor The link can not be used for traffic. This may reduce performance as all traffic is now on other link in the linkset. When the remote end unblocks the link, the alarm is cleared. Remote node transmission error 1. Check the link state of the remote end. 2. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

347

5.30.3

IPC_7151_00031 - qsaalLinkCongested

The traffic on the SSCF-NNI link has exceeded the congestion threshold qsaalLinkCongested Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact IPC_7151_00031 IPC/SS7Stack/SS7LinkSet/SS7Link SS7Link quality of service congestion minor Loss of performance. The alarm will be cleared when the traffic is reduced to below the congestion threshold. Congestion 1. Reduce traffic to below the congestion threshold for the link. 2. Add more capacity. 3. If the problem persists, contact Alcatel-Lucent customer support.

Reason Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

348

5.31

SS7LinkSet alarms
The following alarms are generated by the SS7LinkSet. IPC_7024_00032 - congestionTowardsRemoteMTP3 IPC_7152_00032 - remoteMTP3Unreachable IPC_7153_00032 - remoteMTP3UserUnavailable

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

349

5.31.1

IPC_7024_00032 - congestionTowardsRemoteMTP3

Congestion at the MTP3 layer towards the peer node, as the traffic on the signalling link is beyond the capacity congestionTowardsRemoteMTP3 Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7024_00032 IPC/SS7Stack/SS7LinkSet SS7LinkSet quality of service congestion MAJOR No new signaling connections can be setup. Congestion 1. Reduce the signaling load on the SS7 link. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

350

5.31.2

IPC_7152_00032 - remoteMTP3Unreachable

The peer node is unreachable as no MTP3 link is available in service on this interface. remoteMTP3Unreachable Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7152_00032 IPC/SS7Stack/SS7LinkSet SS7LinkSet communications communicationsSubsystemFailure CRITICAL SS7 Link not available. Communications subsystem failure 1. At the FMS, check the state of the remote NE. 2. At the FMS, check the state of the transport network. 3. At the FMS, check the route configuration. 4. If the problem persists, contact Alcatel-Lucent customer support.

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

351

5.31.3

IPC_7153_00032 - remoteMTP3UserUnavailable

The user of the MTP3 on the peer node is not available for service remoteMTP3UserUnavailable Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7153_00032 IPC/SS7Stack/SS7LinkSet SS7LinkSet communications transmitFailure MAJOR No signaling traffic on this linkset possible. Transmit failure. 1. Check the configuration of the signaling link. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

352

5.32

SS7Stack alarms
The following alarms are generated by the SS7Stack. IPC_7129_00033 - nniStackFailure

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

353

5.32.1

IPC_7129_00033 - nniStackFailure

SS7 NNI Stack bringup failure. nniStackFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7129_00033 IPC/SS7Stack SS7Stack processing error softwareError CRITICAL Signaling link not available. Software error 1. No action required. The Signaling Processor (SP) is reset and the alarm will be cleared. 2. If the problem persists, contact Alcatel-Lucent customer support.

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

354

5.33

SS7StackInst alarms
The following alarms are generated by the SS7StackInst. IPC_7129_00034 - nniStackFailure

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

355

5.33.1

IPC_7129_00034 - nniStackFailure

SS7 NNI Stack bringup failure. nniStackFailure Alarm Code Object Class Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action IPC_7129_00034 IPC/SS7Stack/SS7StackInst SS7StackInst processing error softwareError CRITICAL

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

356

5.34

OAM alarms
The following IPC alarms are generated by the OAM. OAM_0130_00201 - Loss of supervision OAM_0131_00201 - Supervision inhibited by operator OAM_0132_00201 - MIB number received from NE different from MIB number stored in the active view OAM_0133_00201 - Unexpected NE ID

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

357

5.34.1

OAM_0130_00201 - Loss of supervision

This alarm indicates that there was a loss of supervision with the IPC. OAMLinkAdmState equal to unlocked and IPC unknownStatus equal to TRUE. Loss of supervision Alarm Code RAN Managed Object Equipment Type Event Type Probable Cause Severity Impact Reason Remedial Action OAM_0130_00201 IPC N/A communications communicationsSubsystemFailure CRITICAL The state of IPC is unknown due to loss of OAM link. Loss of OAM link between OMC and IPC. No particular action is required. This notification may be required by Global Product Support for debugging purposes

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

358

5.34.2

OAM_0131_00201 - Supervision inhibited by operator

This alarm indicates that the OAMLinkAdministrativeState has been locked by an operator in order to stop communicating with a Network Equipment (in this case, the IPC). The parameter unknownStatus is automatically set to true. Supervision inhibited by operator Alarm Code RAN Managed Object Equipment Type Event Type Probable Cause Severity Impact Reason OAM_0131_00201 IPC N/A communications configurationOrCustomizationError warning The IPC supervision is inhibited. The OAMLinkAdministrativeState parameter (IPC object) is equal to locked. Find out why the OAMLinkAdministrativeState was locked in the first place. Set the OAMLinkAdministrativeState parameter (IPC object) to unlocked.

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

359

5.34.3 OAM_0132_00201 - MIB number received from NE different from MIB number stored in the active view
The MIB number received from NE is different from the MIB number stored in the active view. MIB number received from NE different from MIB number stored in the active view Alarm Code RAN Managed Object Equipment Type Event Type Probable Cause Severity Impact Reason OAM_0132_00201 IPC N/A processing error configurationOrCustomizationError MAJOR MIB de-synchronization. The MIB number received from NE is different from the MIB number stored in the active view.

Remedial Action

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Alcatel-Lucent Confidential

360

5.34.4
NA

OAM_0133_00201 - Unexpected NE ID

Unexpected NE ID Alarm Code RAN Managed Object Equipment Type Event Type Probable Cause Severity Impact Reason OAM_0133_00201 IPC N/A processing error configurationOrCustomizationError MAJOR The IPC is not managed by the FMS The IPC ID received from NE is different from the data configured at FMS . Undeclare and then declare the IPC with the correct IPC ID

Remedial Action

NN-20500-161 01.05/EN Standard October 2008

Copyright 2007-2008 Alcatel-Lucent

Alcatel-Lucent Confidential

361

Copyright 2007-2008 Alcatel-Lucent

IPC Alarms Reference Guide

Wireless Service Provider Solutions W-CDMA Alcatel-Lucent 9353 Management System for Femto IPC Alarms Reference Guide
Copyright 2007-2008 Alcatel-Lucent, All Rights Reserved ALCATEL-LUCENT CONFIDENTIAL UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be regarded as uncontrolled copies. ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have received this document in error, please notify the sender and destroy it immediately. Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marks of Alcatel-Lucent, Alcatel and Lucent Technologies. All other trademarks are the property of their owners. Document number: Document issue: Document status: Product Release: Date: NN-20500-161 01.05/EN Standard FMS2.1 October 2008

You might also like