nn-20500-024_(9300_w-cdma_product_family_-_rnc_and_mss_poc_alarms_reference_guide)_05.06_preliminary_september2008.pdf...

NN-20500-024

Wireless Service Provider Solutions

W-CDMAAlcatel-Lucent 9300 W-CDMA Product FamilyRNC and MSS POC Alarms Reference GuideNN-20500-024 05.06/EN Preliminary September 2008

Wireless Service Provider Solutions

W-CDMAAlcatel-Lucent 9300 W-CDMA Product FamilyRNC and MSS POC Alarms Reference Guide

Document number: NN-20500-024Document issue: 05.06/ENDocument status: PreliminaryProduct release: OAM06.0Date: September 2008

Copyright © 2004-2008 Alcatel-Lucent, All Rights Reserved

ALCATEL-LUCENT CONFIDENTIAL

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "writeprotected"; it may be altered only by authorized persons. While copies may be printed, it is notrecommended. Viewing of the master electronically ensures access to the current issue. Any hardcopiestaken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property ofAlcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep allinformation contained herein confidential, shall disclose the information only to its employees with a needto know, and shall protect the information from disclosure and dissemination to third parties. Except asexpressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the informationcontained herein. If you have received this document in error, please notify the sender and destroy itimmediately.

Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and service marksof Alcatel-Lucent, Alcatel and Lucent Technologies.

The Alcatel-Lucent 9370 Radio Network Controller and the Alcatel-Lucent Point Of Concentration arebased on Nortel Multiservice Switch products. The Nortel Multiservice Data Manager is a Nortel product.

All other trademarks are the property of their owners.

PUBLICATION HISTORYSYSTEM RELEASE: OAM06.0

September 2008

Issue 05.06/EN Preliminary

Update after internal review

Resolution of CR DCTPD00075279 After "reset sh" on RNC, there is no HOL for09990001 and 09990012:

• re-introduction and update of 0999 MDM alarms

• addition of 7078 0061 and 7078 0401 alarms.

August 2008

Issue 05.05/EN Draft

Update for DR4

July 2008



Resolution of CR DCTPD00058377 Wording on section 5.33 of NN-20500-024 ismisleading (RNC_3031_29699 - ANO NODEB ALCAP SSCOP UNAVAILABLE)

April 2008


Update for Pre-DR4

April 2008



Resolution of CR DCTPD00022935 Impact of "00016573 Cnode alarm"missing in the NTP(alarm RNC_3027_29699 added)

January 2008


Update for V6.0 April-08 portfolio content

SYSTEM RELEASE: OAM05.2

Alcatel-Lucent Confidential Publication history i

Copyright © 2004-2008 Alcatel-Lucent RNC and MSS POC Alarms Reference Guide

November 2007

Issue 04.03/EN Standard

Update for DR5

Resolution of the following CRs:

• Q01749769: Alarm 7079 0100 wrong description

• Q01752612: Alarm 7079 0102 wrong description behaviour

• Q01754273: UNEXPECTED RNC MIBSTATE alarm wrong behavior

• Q01755046: Alarm 70780300 FirstCBearer wrong behavior

• Q01770802: Remedial action due to MIB state warning is unclear

• Q01782917: Remdial action change in case of OAM_37 (Cnode Synchronisationerror)

• Q01783344: Document Addition Request for CS/PS Core Double Alarm Display

September 2007



Resolution of CR Q01742534: HOL and additional text mismatch for ANO restart alarm.

August 2007


Update for OAM05.2

SYSTEM RELEASE: UMTS 5.1

August 2007


Update for OAM05.1 Post-Channel Readiness

Resolution of CR Q01726714: Severity mismacth for 00001000 alarm between HOL andGUI

July 2007


Update for UA 5.0 / OAM 5.1 Channel Readiness

Resolution of the following CRs:

• Q01546015: OAM-No help page is found about the alarm 70780204

• Q01644217: Help On Line not present for alarm 70701013

Alcatel-Lucent Confidential Publication history ii

NN-20500-024 05.06/EN Preliminary September 2008 Copyright © 2004-2008 Alcatel-Lucent

• Q01664175: ntp & HOL-bad description of impact after TMU reset

March 2007



November 2006


Update for UA 5.0 / OAM 5.1

The Publication History information for the outdated releaseshas been deleted.Document creation date: December 2004

Alcatel-Lucent Confidential Publication history iii


1 About this publication................................................................................................................................................... 1

2 UMTS Access Network Collection Roadmap...............................................................................................................3

3 New in this release.........................................................................................................................................................4

4 How to use this publication...........................................................................................................................................5

5 Control Node notifications and alarms...................................................................................................................... 10

5.1 RNC_2007_30467 - ANO OVERLOAD THRESHOLD.............................................................................................11

5.2 RNC_2028_30467 - ANO RESTART CONTEXT..................................................................................................... 12

5.3 RNC_3000_29700 - ANO OCNS FAILURE............................................................................................................. 13

5.4 RNC_3001_29696 - ANO CELL SWACT INFORMATION.......................................................................................14

5.5 RNC_3002_29700 - ANO CIBS FAILURE............................................................................................................... 15

5.6 RNC_3003_29700 - ANO DEADLOCKSTATE DETECTION...................................................................................16

5.7 RNC_3004_29755 - ANO CELL NOT HSDPA CAPABLE INFORMATION............................................................. 17

5.8 RNC_3005_29755 - ANO HSDPA CONFIGURATION FAILURE INFORMATION.................................................. 18

5.9 RNC_3006_29755 - ANO HSDPA HARDWARE RECOVERY INFORMATION...................................................... 19

5.10 RNC_3007_29700 - ANO DEGRADED CELL STATUS INFORMATION.............................................................. 20

5.11 RNC_3008_29713 - ANO CORENETWORK CS DOMAIN OVERLOAD...............................................................21

5.12 RNC_3009_29714 - ANO CORENETWORK PS DOMAIN OVERLOAD............................................................... 22

5.13 RNC_3010_29713 - ANO RNC NOTIFY CORENETWORK CS DOMAIN OVERLOAD........................................23

5.14 RNC_3011_29714 - ANO RNC NOTIFY CORENETWORK PS DOMAIN OVERLOAD........................................ 24

5.15 RNC_3012_29772 - ANO CELL E-DCH DISABLED INFORMATION....................................................................25

5.16 RNC_3013_29772 - ANO E-DCH HARDWARE RECOVERY INFORMATION..................................................... 26

5.17 RNC_3014_29772 - ANO E-DCH CONFIGURATION FAILURE INFORMATION................................................. 27

5.18 RNC_3015_29772 - ANO CELL NOT E-DCH CAPABLE INFORMATION............................................................ 28

5.19 RNC_3016_29772 - ANO EDCH WITHOUT HSDPA NOT ALLOWED INFORMATION....................................... 29

5.20 RNC_3017_29713 - ANO OUTGOING CS RANAP RESET NOT ACKNOWLEDGED..........................................30

5.21 RNC_3018_29714 - ANO OUTGOING PS RANAP RESET NOT ACKNOWLEDGED..........................................31

5.22 RNC_3019_29722 - ANO IU FAILURE.................................................................................................................. 32

5.23 RNC_3020_29722 - ANO CORE NETWORK OVERLOAD................................................................................... 33

5.24 RNC_3021_29722 - ANO RNC CONGESTION..................................................................................................... 34

5.25 RNC_3022_29722 - ANO LOCAL OVERLOAD..................................................................................................... 35

5.26 RNC_3023_29722 - ANO MANUAL CLS CELL BARRING....................................................................................36

5.27 RNC_3024_29713 - ANO SILENT IUCS DETECTED........................................................................................... 37

5.28 RNC_3025_29714 - ANO SILENT IUPS DETECTED............................................................................................38

5.29 RNC_3026_29700 - ANO NBAP SIB NEIGHBOURINGCELL LIMIT REACHED...................................................39

5.30 RNC_3027_29699 - ANO NODEB CALLS THRESHOLD CROSSED...................................................................40

Alcatel-Lucent Confidential Table of contents iv


5.31 RNC_3027_29792 - ANO ACCESS CLASS BARRING ACTIVATED BY OPERATOR.........................................41

5.32 RNC_3030_29700 - ANO CELL NOT MBMS CAPABLE INFORMATION.............................................................42

5.33 RNC_3031_29699 - ANO NODEB ALCAP SSCOP UNAVAILABLE..................................................................... 43

5.34 RNC_3032_29708 - ANO PF GPO LIMIT 80 PC REACHED.................................................................................44

5.35 RNC_3033_29708 - ANO PF GPO LIMIT 100 PC REACHED AND LOW PRIORITY COUNTERS DISABLED...45

5.36 RNC_3034_29699 - ANO NODEB IP USER PLANE FAILURE.............................................................................46

5.37 RNC_3036_29819 - ANO LIMITED SRS DATA.....................................................................................................47

5.38 RNC_3037_29819 - ANO NO SRS DATA..............................................................................................................48

5.39 RNC_3038_29820 - ANO OCNS CHANNEL FAIL INFO....................................................................................... 49

5.40 RNC_3039_29821 - ANO OCNSHSDPA FAIL INFO............................................................................................. 50

5.41 RNC_3040_29700 - ANO CELL SHUTDOWN INITIATED.................................................................................... 51

5.42 RNC_3041_29700 - ANO CELL SHUTDOWN E911 CALL DETECTED............................................................... 52

5.43 RNC_3050_29696 - ANO GENERIC ALARM........................................................................................................ 53

5.44 OAM_0013_00036 - SYSTEM RELEASE INCONSISTENT.................................................................................. 54

5.45 OAM_0014_00036 - LOSS OF SUPERVISION..................................................................................................... 55

5.46 OAM_0015_00036 - SUPERVISION INHIBITED BY OPERATOR........................................................................ 56

5.47 OAM_0026_00036 - CONFIG REPORT DECODING FAILED.............................................................................. 57

5.48 OAM_0045_00036 - THRESHOLD OVERCROSS ON RNC COUNTER.............................................................. 58

5.49 OAM_0047_00036 - MEASUREMENT FILE DECODING FAILED........................................................................59

5.50 OAM_0048_00036 - RNC MEASUREMENT FILE MISSING.................................................................................60

5.51 OAM_0049_00036 - CONNECTION FAILED TO RETRIEVE MEASUREMENT FILES........................................61

5.52 OAM_0062_00057 - THRESHOLD OVERCROSS ON POC COUNTER.............................................................. 62

5.53 OAM_0063_00057 - POC MEASUREMENT FILE DECODING FAILED............................................................... 63

5.54 OAM_0064_00057 - POC MEASUREMENT FILE DID NOT ARRIVE...................................................................64

5.55 OAM_0065_00057 - CONNECTION FAILED TO RETRIEVE MEASUREMENT FILES........................................65

5.56 OAM_0066_00057 - LOSS OF SUPERVISION..................................................................................................... 66

5.57 OAM_0067_00057 - SUPERVISION INHIBITED BY OPERATOR........................................................................ 67

5.58 OAM_0068_00057 - CONFIGURATION DE-SYNCHRONIZATION...................................................................... 68

5.59 RNC_0004_00020 - UNKNOWN SOFTWARE VERSION..................................................................................... 69

5.60 RNC_0006_00020 - STATE CHANGE TO UNLOCKED DISABLED FAILED....................................................... 70

5.61 RNC_0009_00056 - MIB NOT BUILT.....................................................................................................................71




5.65 RNC_0021_00020 - STATE CHANGE TO UNLOCKED OR LOCKED DISABLED FAILED................................. 75

Alcatel-Lucent Confidential Table of contents v


5.66 RNC_0022_00020 - STATE CHANGE TO UNLOCKED ENABLED DEGRADED.................................................76

5.67 RNC_0023_00020 - STATE CHANGE TO UNLOCKED DISABLED DEPENDENCY........................................... 77


5.69 RNC_0028_00020 - STATE CHANGE TO UNLOCKED OR LOCKED ENABLED DEGRADED...........................79


5.71 RNC_0030_00020 - STATE CHANGE TO UNLOCKED OR LOCKED DISABLED DEPENDENCY.....................81


5.73 RNC_0037_00036 - CNODE INTERNAL SYNCHRONIZATION ERROR............................................................. 83

5.74 RNC_0038_00004 - STATE CHANGE TO UNLOCKED DISABLED NOT INSTALLED........................................84






5.80 RNC_0053_00056 - UNEXPECTED RNC MIBSTATE SET TO UPDATE IN PROGRESS...................................90

5.81 RNC_0056_00056 - RNC FAMILY NOT COMPATIBLE WITH RNC ARCHITECTURE........................................ 91

5.82 RNC_0057_00056 - MIB NUMBER RECEIVED FROM NE DIFFERENT FROM MIB NUMBER STORED IN THEACTIVE VIEW..................................................................................................................................................................925.83 RNC_0058_00020 - STATE CHANGE TO DISABLED NOT INSTALLED.............................................................93

5.84 RNC_0059_00036 - UNEXPECTED RNC MIBSTATE SET TO UPDATE IN PROGRESS...................................94

5.85 RNC_0070_00056 - CONFIGURATION DE-SYNCHRONIZATION.......................................................................95

5.86 RNC_0080_00036 - STATE CHANGE TO DISABLED DUE TO MANAGEMENT OPERATION...........................96




5.90 RNC_0084_00036 - STATE CHANGE TO DISABLED DUE TO MANAGEMENT OPERATION.........................100

5.91 RNC_0085_00036 - STATE CHANGE TO DISABLE FAILED............................................................................. 101

6 Access Node, Interface Node and POC alarms.......................................................................................................102

6.1 MSS_0000_00000.................................................................................................................................................. 103

6.2 MSS_0000_00001.................................................................................................................................................. 104

6.3 MSS_0000_01000.................................................................................................................................................. 105

6.4 MSS_0000_01001.................................................................................................................................................. 106

6.5 MSS_0000_03000.................................................................................................................................................. 107

6.6 MSS_0000_03001.................................................................................................................................................. 109

6.7 MSS_0000_03002.................................................................................................................................................. 110

6.8 MSS_0000_09000.................................................................................................................................................. 111

Alcatel-Lucent Confidential Table of contents vi


6.9 MSS_0000_09001.................................................................................................................................................. 112

6.10 MSS_0000_09002................................................................................................................................................ 113

6.11 MSS_0000_09003................................................................................................................................................ 114

6.12 MSS_0999_00001................................................................................................................................................ 115

6.13 MSS_0999_00012................................................................................................................................................ 117

6.14 MSS_7000_00001................................................................................................................................................ 119

6.15 MSS_7000_00002................................................................................................................................................ 120

6.16 MSS_7000_00003................................................................................................................................................ 121

6.17 MSS_7000_00004................................................................................................................................................ 122

6.18 MSS_7000_00005................................................................................................................................................ 123

6.19 MSS_7000_00006................................................................................................................................................ 124

6.20 MSS_7000_00007................................................................................................................................................ 125

6.21 MSS_7000_00008................................................................................................................................................ 127

6.22 MSS_7000_00009................................................................................................................................................ 128

6.23 MSS_7000_00010................................................................................................................................................ 129

6.24 MSS_7000_00011................................................................................................................................................ 130

6.25 MSS_7000_00012................................................................................................................................................ 131

6.26 MSS_7000_00013................................................................................................................................................ 132

6.27 MSS_7000_00015................................................................................................................................................ 133

6.28 MSS_7000_00016................................................................................................................................................ 134

6.29 MSS_7000_00029................................................................................................................................................ 135

6.30 MSS_7000_00030................................................................................................................................................ 136

6.31 MSS_7000_00031................................................................................................................................................ 137

6.32 MSS_7000_00032................................................................................................................................................ 138

6.33 MSS_7000_00033................................................................................................................................................ 139

6.34 MSS_7000_00034................................................................................................................................................ 141

6.35 MSS_7000_00035................................................................................................................................................ 142

6.36 MSS_7000_00036................................................................................................................................................ 143

6.37 MSS_7000_00037................................................................................................................................................ 144

6.38 MSS_7000_00038................................................................................................................................................ 146

6.39 MSS_7000_00039................................................................................................................................................ 147

6.40 MSS_7000_00040................................................................................................................................................ 148

6.41 MSS_7000_00041................................................................................................................................................ 149

6.42 MSS_7000_00042................................................................................................................................................ 150

6.43 MSS_7000_00043................................................................................................................................................ 152

Alcatel-Lucent Confidential Table of contents vii


6.44 MSS_7000_00044................................................................................................................................................ 153

6.45 MSS_7002_00000................................................................................................................................................ 154

6.46 MSS_7002_00001................................................................................................................................................ 155

6.47 MSS_7002_00002................................................................................................................................................ 156

6.48 MSS_7002_00003................................................................................................................................................ 157

6.49 MSS_7002_00004................................................................................................................................................ 158

6.50 MSS_7002_00005................................................................................................................................................ 159

6.51 MSS_7002_00006................................................................................................................................................ 160

6.52 MSS_7002_00007................................................................................................................................................ 161

6.53 MSS_7002_00008................................................................................................................................................ 162

6.54 MSS_7002_00009................................................................................................................................................ 163

6.55 MSS_7002_00010................................................................................................................................................ 164

6.56 MSS_7002_00012................................................................................................................................................ 165

6.57 MSS_7002_00013................................................................................................................................................ 166

6.58 MSS_7002_00014................................................................................................................................................ 167

6.59 MSS_7002_01000................................................................................................................................................ 168

6.60 MSS_7003_00001................................................................................................................................................ 169

6.61 MSS_7003_00002................................................................................................................................................ 171

6.62 MSS_7003_00003................................................................................................................................................ 173

6.63 MSS_7003_00004................................................................................................................................................ 175

6.64 MSS_7003_00005................................................................................................................................................ 176

6.65 MSS_7003_00006................................................................................................................................................ 177

6.66 MSS_7003_00007................................................................................................................................................ 178

6.67 MSS_7003_00008................................................................................................................................................ 180

6.68 MSS_7003_00009................................................................................................................................................ 181

6.69 MSS_7003_00010................................................................................................................................................ 182

6.70 MSS_7006_00001................................................................................................................................................ 183

6.71 MSS_7006_00002................................................................................................................................................ 184

6.72 MSS_7006_00003................................................................................................................................................ 185

6.73 MSS_7006_00004................................................................................................................................................ 187

6.74 MSS_7006_00005................................................................................................................................................ 188

6.75 MSS_7006_00006................................................................................................................................................ 189

6.76 MSS_7006_00007................................................................................................................................................ 190

6.77 MSS_7006_00008................................................................................................................................................ 191

6.78 MSS_7006_00009................................................................................................................................................ 192

Alcatel-Lucent Confidential Table of contents viii


6.79 MSS_7006_00010................................................................................................................................................ 193

6.80 MSS_7006_00011................................................................................................................................................ 194

6.81 MSS_7006_00012................................................................................................................................................ 196

6.82 MSS_7006_00013................................................................................................................................................ 198

6.83 MSS_7006_00100................................................................................................................................................ 199

6.84 MSS_7006_00101................................................................................................................................................ 200

6.85 MSS_7006_00102................................................................................................................................................ 201

6.86 MSS_7006_00103................................................................................................................................................ 202

6.87 MSS_7006_00104................................................................................................................................................ 203

6.88 MSS_7006_00105................................................................................................................................................ 204

6.89 MSS_7008_01001................................................................................................................................................ 205

6.90 MSS_7008_01002................................................................................................................................................ 206

6.91 MSS_7008_01003................................................................................................................................................ 207

6.92 MSS_7008_01004................................................................................................................................................ 208

6.93 MSS_7008_01005................................................................................................................................................ 209

6.94 MSS_7008_01006................................................................................................................................................ 210

6.95 MSS_7008_01008................................................................................................................................................ 211

6.96 MSS_7008_01009................................................................................................................................................ 212

6.97 MSS_7008_01010................................................................................................................................................ 213

6.98 MSS_7008_01011................................................................................................................................................ 214

6.99 MSS_7008_01012................................................................................................................................................ 215

6.100 MSS_7008_01013.............................................................................................................................................. 216

6.101 MSS_7008_01014.............................................................................................................................................. 217

6.102 MSS_7008_01015.............................................................................................................................................. 218

6.103 MSS_7008_01016.............................................................................................................................................. 219

6.104 MSS_7008_01017.............................................................................................................................................. 220

6.105 MSS_7008_01018.............................................................................................................................................. 221

6.106 MSS_7008_01019.............................................................................................................................................. 222

6.107 MSS_7008_01020.............................................................................................................................................. 223

6.108 MSS_7008_01021.............................................................................................................................................. 224

6.109 MSS_7008_01022.............................................................................................................................................. 225

6.110 MSS_7008_01023.............................................................................................................................................. 226

6.111 MSS_7008_01024.............................................................................................................................................. 227

6.112 MSS_7011_01100.............................................................................................................................................. 228

6.113 MSS_7011_01200.............................................................................................................................................. 229

Alcatel-Lucent Confidential Table of contents ix


6.114 MSS_7011_01210.............................................................................................................................................. 230

6.115 MSS_7011_01211.............................................................................................................................................. 232

6.116 MSS_7011_01212.............................................................................................................................................. 234

6.117 MSS_7011_01213.............................................................................................................................................. 235

6.118 MSS_7011_01214.............................................................................................................................................. 236

6.119 MSS_7011_01215.............................................................................................................................................. 237

6.120 MSS_7011_01216.............................................................................................................................................. 238

6.121 MSS_7011_01400.............................................................................................................................................. 239

6.122 MSS_7011_01401.............................................................................................................................................. 240

6.123 MSS_7011_01402.............................................................................................................................................. 241

6.124 MSS_7011_01403.............................................................................................................................................. 242

6.125 MSS_7011_01404.............................................................................................................................................. 243

6.126 MSS_7011_01405.............................................................................................................................................. 244

6.127 MSS_7011_01406.............................................................................................................................................. 245

6.128 MSS_7011_01407.............................................................................................................................................. 246

6.129 MSS_7011_01500.............................................................................................................................................. 247

6.130 MSS_7011_01501.............................................................................................................................................. 248

6.131 MSS_7011_02000.............................................................................................................................................. 249

6.132 MSS_7011_02001.............................................................................................................................................. 250

6.133 MSS_7011_02002.............................................................................................................................................. 251

6.134 MSS_7011_05000.............................................................................................................................................. 252

6.135 MSS_7011_05001.............................................................................................................................................. 253

6.136 MSS_7011_05002.............................................................................................................................................. 254

6.137 MSS_7011_05003.............................................................................................................................................. 255

6.138 MSS_7011_05004.............................................................................................................................................. 256

6.139 MSS_7011_05005.............................................................................................................................................. 257

6.140 MSS_7011_05006.............................................................................................................................................. 258

6.141 MSS_7011_05007.............................................................................................................................................. 260

6.142 MSS_7011_05010.............................................................................................................................................. 261

6.143 MSS_7011_05011.............................................................................................................................................. 262

6.144 MSS_7011_05050.............................................................................................................................................. 263

6.145 MSS_7011_05051.............................................................................................................................................. 264

6.146 MSS_7011_05100.............................................................................................................................................. 265

6.147 MSS_7011_05101.............................................................................................................................................. 266

6.148 MSS_7011_05102.............................................................................................................................................. 267

Alcatel-Lucent Confidential Table of contents x


6.149 MSS_7011_05103.............................................................................................................................................. 268

6.150 MSS_7011_05104.............................................................................................................................................. 270

6.151 MSS_7011_05105.............................................................................................................................................. 271

6.152 MSS_7011_05110.............................................................................................................................................. 272

6.153 MSS_7011_05111.............................................................................................................................................. 273

6.154 MSS_7011_05112.............................................................................................................................................. 274

6.155 MSS_7011_05120.............................................................................................................................................. 275

6.156 MSS_7011_05121.............................................................................................................................................. 276

6.157 MSS_7011_05122.............................................................................................................................................. 277

6.158 MSS_7011_05130.............................................................................................................................................. 278

6.159 MSS_7011_05131.............................................................................................................................................. 279

6.160 MSS_7011_05200.............................................................................................................................................. 280

6.161 MSS_7011_05201.............................................................................................................................................. 281

6.162 MSS_7011_05202.............................................................................................................................................. 282

6.163 MSS_7011_05203.............................................................................................................................................. 283

6.164 MSS_7011_05204.............................................................................................................................................. 284

6.165 MSS_7011_05210.............................................................................................................................................. 285

6.166 MSS_7011_05211.............................................................................................................................................. 286

6.167 MSS_7011_05250.............................................................................................................................................. 287

6.168 MSS_7011_05251.............................................................................................................................................. 288

6.169 MSS_7011_05252.............................................................................................................................................. 289

6.170 MSS_7011_05253.............................................................................................................................................. 290

6.171 MSS_7011_05254.............................................................................................................................................. 291

6.172 MSS_7011_05255.............................................................................................................................................. 292

6.173 MSS_7011_05256.............................................................................................................................................. 293

6.174 MSS_7011_05260.............................................................................................................................................. 294

6.175 MSS_7011_05261.............................................................................................................................................. 295

6.176 MSS_7011_05270.............................................................................................................................................. 297

6.177 MSS_7011_05271.............................................................................................................................................. 298

6.178 MSS_7011_05272.............................................................................................................................................. 299

6.179 MSS_7011_05273.............................................................................................................................................. 300

6.180 MSS_7011_05274.............................................................................................................................................. 301

6.181 MSS_7011_05275.............................................................................................................................................. 303

6.182 MSS_7011_05276.............................................................................................................................................. 304

6.183 MSS_7011_05277.............................................................................................................................................. 305

Alcatel-Lucent Confidential Table of contents xi


6.184 MSS_7011_05278.............................................................................................................................................. 306

6.185 MSS_7011_05279.............................................................................................................................................. 307

6.186 MSS_7011_05280.............................................................................................................................................. 308

6.187 MSS_7011_05281.............................................................................................................................................. 309

6.188 MSS_7011_05290.............................................................................................................................................. 310

6.189 MSS_7011_05291.............................................................................................................................................. 311

6.190 MSS_7011_05292.............................................................................................................................................. 312

6.191 MSS_7011_05293.............................................................................................................................................. 313

6.192 MSS_7011_05294.............................................................................................................................................. 314

6.193 MSS_7011_05295.............................................................................................................................................. 315

6.194 MSS_7011_05296.............................................................................................................................................. 316

6.195 MSS_7011_05297.............................................................................................................................................. 317

6.196 MSS_7011_05300.............................................................................................................................................. 318

6.197 MSS_7011_05301.............................................................................................................................................. 319

6.198 MSS_7011_05302.............................................................................................................................................. 320

6.199 MSS_7011_05303.............................................................................................................................................. 321

6.200 MSS_7011_05304.............................................................................................................................................. 322

6.201 MSS_7011_05400.............................................................................................................................................. 323

6.202 MSS_7011_05401.............................................................................................................................................. 324

6.203 MSS_7011_05402.............................................................................................................................................. 325

6.204 MSS_7011_05403.............................................................................................................................................. 326

6.205 MSS_7011_05480.............................................................................................................................................. 327

6.206 MSS_7011_05501.............................................................................................................................................. 328

6.207 MSS_7011_05601.............................................................................................................................................. 329

6.208 MSS_7011_05602.............................................................................................................................................. 330

6.209 MSS_7011_05603.............................................................................................................................................. 331

6.210 MSS_7011_05604.............................................................................................................................................. 332

6.211 MSS_7011_05701.............................................................................................................................................. 333

6.212 MSS_7011_05702.............................................................................................................................................. 334

6.213 MSS_7011_05703.............................................................................................................................................. 335

6.214 MSS_7011_06500.............................................................................................................................................. 336

6.215 MSS_7011_06501.............................................................................................................................................. 337

6.216 MSS_7011_06600.............................................................................................................................................. 338

6.217 MSS_7011_06601.............................................................................................................................................. 339

6.218 MSS_7011_07000.............................................................................................................................................. 340

Alcatel-Lucent Confidential Table of contents xii


6.219 MSS_7011_07001.............................................................................................................................................. 341

6.220 MSS_7011_07002.............................................................................................................................................. 342

6.221 MSS_7011_07003.............................................................................................................................................. 343

6.222 MSS_7011_07004.............................................................................................................................................. 344

6.223 MSS_7011_07005.............................................................................................................................................. 345

6.224 MSS_7011_07006.............................................................................................................................................. 347

6.225 MSS_7011_07007.............................................................................................................................................. 348

6.226 MSS_7011_07500.............................................................................................................................................. 349

6.227 MSS_7011_07501.............................................................................................................................................. 350

6.228 MSS_7011_08000.............................................................................................................................................. 351

6.229 MSS_7011_09000.............................................................................................................................................. 352

6.230 MSS_7011_09001.............................................................................................................................................. 353

6.231 MSS_7012_00050.............................................................................................................................................. 354

6.232 MSS_7012_00051.............................................................................................................................................. 355

6.233 MSS_7012_00052.............................................................................................................................................. 357

6.234 MSS_7012_00053.............................................................................................................................................. 358

6.235 MSS_7012_00054.............................................................................................................................................. 359

6.236 MSS_7012_00055.............................................................................................................................................. 360

6.237 MSS_7012_00056.............................................................................................................................................. 361

6.238 MSS_7012_00057.............................................................................................................................................. 362

6.239 MSS_7012_00058.............................................................................................................................................. 363

6.240 MSS_7012_00059.............................................................................................................................................. 364

6.241 MSS_7012_00100.............................................................................................................................................. 366

6.242 MSS_7012_00101.............................................................................................................................................. 367

6.243 MSS_7012_00102.............................................................................................................................................. 368

6.244 MSS_7012_00103.............................................................................................................................................. 369

6.245 MSS_7012_00104.............................................................................................................................................. 370

6.246 MSS_7012_00105.............................................................................................................................................. 371

6.247 MSS_7012_00151.............................................................................................................................................. 372

6.248 MSS_7012_00152.............................................................................................................................................. 373

6.249 MSS_7012_00153.............................................................................................................................................. 374

6.250 MSS_7012_00154.............................................................................................................................................. 375

6.251 MSS_7012_00155.............................................................................................................................................. 376

6.252 MSS_7012_00156.............................................................................................................................................. 377

6.253 MSS_7012_00160.............................................................................................................................................. 378

Alcatel-Lucent Confidential Table of contents xiii


6.254 MSS_7012_00161.............................................................................................................................................. 379

6.255 MSS_7012_00162.............................................................................................................................................. 380

6.256 MSS_7012_00164.............................................................................................................................................. 381

6.257 MSS_7012_00165.............................................................................................................................................. 382

6.258 MSS_7012_00200.............................................................................................................................................. 383

6.259 MSS_7012_00201.............................................................................................................................................. 384

6.260 MSS_7012_00202.............................................................................................................................................. 385

6.261 MSS_7012_00203.............................................................................................................................................. 386

6.262 MSS_7012_00204.............................................................................................................................................. 388

6.263 MSS_7012_00300.............................................................................................................................................. 389

6.264 MSS_7012_00301.............................................................................................................................................. 390

6.265 MSS_7013_00000.............................................................................................................................................. 391

6.266 MSS_7013_00001.............................................................................................................................................. 392

6.267 MSS_7013_00002.............................................................................................................................................. 393

6.268 MSS_7013_00003.............................................................................................................................................. 394

6.269 MSS_7013_00004.............................................................................................................................................. 395

6.270 MSS_7013_00005.............................................................................................................................................. 396

6.271 MSS_7013_00011.............................................................................................................................................. 397

6.272 MSS_7013_00021.............................................................................................................................................. 398

6.273 MSS_7013_00022.............................................................................................................................................. 399

6.274 MSS_7014_00000.............................................................................................................................................. 400

6.275 MSS_7014_00001.............................................................................................................................................. 401

6.276 MSS_7014_00010.............................................................................................................................................. 402

6.277 MSS_7014_00011.............................................................................................................................................. 403

6.278 MSS_7015_00000.............................................................................................................................................. 404

6.279 MSS_7015_00001.............................................................................................................................................. 406

6.280 MSS_7015_00002.............................................................................................................................................. 407

6.281 MSS_7015_00010.............................................................................................................................................. 408

6.282 MSS_7015_00011.............................................................................................................................................. 409

6.283 MSS_7015_00012.............................................................................................................................................. 411

6.284 MSS_7015_00014.............................................................................................................................................. 412

6.285 MSS_7015_00015.............................................................................................................................................. 413

6.286 MSS_7015_00016.............................................................................................................................................. 414

6.287 MSS_7015_00020.............................................................................................................................................. 416

6.288 MSS_7017_01000.............................................................................................................................................. 417

Alcatel-Lucent Confidential Table of contents xiv


6.289 MSS_7017_01001.............................................................................................................................................. 418

6.290 MSS_7017_01002.............................................................................................................................................. 419

6.291 MSS_7020_00001.............................................................................................................................................. 420

6.292 MSS_7020_00002.............................................................................................................................................. 421

6.293 MSS_7021_00000.............................................................................................................................................. 422

6.294 MSS_7021_00001.............................................................................................................................................. 423

6.295 MSS_7021_00006.............................................................................................................................................. 424

6.296 MSS_7021_00008.............................................................................................................................................. 425

6.297 MSS_7021_00010.............................................................................................................................................. 426

6.298 MSS_7021_00013.............................................................................................................................................. 427

6.299 MSS_7021_00014.............................................................................................................................................. 428

6.300 MSS_7021_00015.............................................................................................................................................. 429

6.301 MSS_7021_01000.............................................................................................................................................. 430

6.302 MSS_7021_01001.............................................................................................................................................. 431

6.303 MSS_7021_01002.............................................................................................................................................. 432

6.304 MSS_7021_01003.............................................................................................................................................. 434

6.305 MSS_7021_01004.............................................................................................................................................. 436

6.306 MSS_7021_01005.............................................................................................................................................. 438

6.307 MSS_7021_01006.............................................................................................................................................. 439

6.308 MSS_7021_01007.............................................................................................................................................. 440

6.309 MSS_7021_01008.............................................................................................................................................. 441

6.310 MSS_7021_01009.............................................................................................................................................. 442

6.311 MSS_7021_0100A..............................................................................................................................................443

6.312 MSS_7021_0100B..............................................................................................................................................444

6.313 MSS_7021_0100C............................................................................................................................................. 445

6.314 MSS_7021_0100D............................................................................................................................................. 446

6.315 MSS_7021_0100E..............................................................................................................................................447

6.316 MSS_7021_01010.............................................................................................................................................. 448

6.317 MSS_7021_01011.............................................................................................................................................. 449

6.318 MSS_7021_01012.............................................................................................................................................. 450

6.319 MSS_7021_01013.............................................................................................................................................. 452

6.320 MSS_7021_01014.............................................................................................................................................. 453

6.321 MSS_7021_01015.............................................................................................................................................. 454

6.322 MSS_7021_01016.............................................................................................................................................. 455

6.323 MSS_7021_01017.............................................................................................................................................. 456

Alcatel-Lucent Confidential Table of contents xv


6.324 MSS_7021_01018.............................................................................................................................................. 457

6.325 MSS_7021_01019.............................................................................................................................................. 459

6.326 MSS_7021_01020.............................................................................................................................................. 460

6.327 MSS_7021_01021.............................................................................................................................................. 461

6.328 MSS_7021_01022.............................................................................................................................................. 463

6.329 MSS_7021_01051.............................................................................................................................................. 464

6.330 MSS_7021_01052.............................................................................................................................................. 465

6.331 MSS_7021_01053.............................................................................................................................................. 466

6.332 MSS_7021_01054.............................................................................................................................................. 467

6.333 MSS_7021_01055.............................................................................................................................................. 468

6.334 MSS_7021_01056.............................................................................................................................................. 469

6.335 MSS_7021_01057.............................................................................................................................................. 470

6.336 MSS_7021_01059.............................................................................................................................................. 471

6.337 MSS_7021_01060.............................................................................................................................................. 472

6.338 MSS_7021_01061.............................................................................................................................................. 473

6.339 MSS_7021_01100.............................................................................................................................................. 474

6.340 MSS_7021_01101.............................................................................................................................................. 475

6.341 MSS_7021_01102.............................................................................................................................................. 476

6.342 MSS_7021_01103.............................................................................................................................................. 477

6.343 MSS_7021_01104.............................................................................................................................................. 478

6.344 MSS_7021_01200.............................................................................................................................................. 479

6.345 MSS_7021_01202.............................................................................................................................................. 480

6.346 MSS_7021_01203.............................................................................................................................................. 481

6.347 MSS_7021_01204.............................................................................................................................................. 482

6.348 MSS_7021_01205.............................................................................................................................................. 483

6.349 MSS_7021_01206.............................................................................................................................................. 484

6.350 MSS_7021_01208.............................................................................................................................................. 485

6.351 MSS_7021_01209.............................................................................................................................................. 486

6.352 MSS_7021_01210.............................................................................................................................................. 487

6.353 MSS_7021_01211.............................................................................................................................................. 488

6.354 MSS_7021_01212.............................................................................................................................................. 489

6.355 MSS_7021_01213.............................................................................................................................................. 490

6.356 MSS_7021_01214.............................................................................................................................................. 491

6.357 MSS_7021_01215.............................................................................................................................................. 492

6.358 MSS_7021_02000.............................................................................................................................................. 493

Alcatel-Lucent Confidential Table of contents xvi


6.359 MSS_7021_02400.............................................................................................................................................. 494

6.360 MSS_7021_02500.............................................................................................................................................. 495

6.361 MSS_7021_02501.............................................................................................................................................. 496

6.362 MSS_7021_02502.............................................................................................................................................. 497

6.363 MSS_7021_02503.............................................................................................................................................. 498

6.364 MSS_7021_03000.............................................................................................................................................. 499

6.365 MSS_7021_04000.............................................................................................................................................. 500

6.366 MSS_7026_01000.............................................................................................................................................. 501

6.367 MSS_7026_01001.............................................................................................................................................. 502

6.368 MSS_7026_01002.............................................................................................................................................. 503

6.369 MSS_7026_02000.............................................................................................................................................. 504

6.370 MSS_7026_02002.............................................................................................................................................. 505

6.371 MSS_7026_02003.............................................................................................................................................. 506

6.372 MSS_7026_02004.............................................................................................................................................. 507

6.373 MSS_7026_03000.............................................................................................................................................. 508

6.374 MSS_7026_03001.............................................................................................................................................. 509

6.375 MSS_7026_03002.............................................................................................................................................. 510

6.376 MSS_7026_03003.............................................................................................................................................. 511

6.377 MSS_7026_03004.............................................................................................................................................. 512

6.378 MSS_7026_03005.............................................................................................................................................. 513

6.379 MSS_7026_03006.............................................................................................................................................. 514

6.380 MSS_7026_03007.............................................................................................................................................. 515

6.381 MSS_7026_04002.............................................................................................................................................. 516

6.382 MSS_7026_04004.............................................................................................................................................. 517

6.383 MSS_7026_04005.............................................................................................................................................. 518

6.384 MSS_7026_04006.............................................................................................................................................. 519

6.385 MSS_7026_04007.............................................................................................................................................. 520

6.386 MSS_7026_04008.............................................................................................................................................. 521

6.387 MSS_7026_04009.............................................................................................................................................. 522

6.388 MSS_7026_0400A..............................................................................................................................................523

6.389 MSS_7026_0400B..............................................................................................................................................524

6.390 MSS_7026_0400C............................................................................................................................................. 525

6.391 MSS_7026_0400D............................................................................................................................................. 526

6.392 MSS_7026_0400E..............................................................................................................................................527

6.393 MSS_7026_0400F..............................................................................................................................................528

Alcatel-Lucent Confidential Table of contents xvii


6.394 MSS_7026_04010.............................................................................................................................................. 529

6.395 MSS_7026_04011.............................................................................................................................................. 530

6.396 MSS_7026_04012.............................................................................................................................................. 531

6.397 MSS_7026_04013.............................................................................................................................................. 532

6.398 MSS_7026_04014.............................................................................................................................................. 533

6.399 MSS_7026_04015.............................................................................................................................................. 534

6.400 MSS_7026_05000.............................................................................................................................................. 535

6.401 MSS_7026_05001.............................................................................................................................................. 536

6.402 MSS_7026_05002.............................................................................................................................................. 537

6.403 MSS_7026_05003.............................................................................................................................................. 538

6.404 MSS_7026_05004.............................................................................................................................................. 539

6.405 MSS_7026_05005.............................................................................................................................................. 540

6.406 MSS_7026_05006.............................................................................................................................................. 541

6.407 MSS_7026_05007.............................................................................................................................................. 542

6.408 MSS_7026_05008.............................................................................................................................................. 543

6.409 MSS_7026_05009.............................................................................................................................................. 544

6.410 MSS_7026_0500A..............................................................................................................................................545

6.411 MSS_7035_00001.............................................................................................................................................. 546

6.412 MSS_7035_00002.............................................................................................................................................. 547

6.413 MSS_7039_01000.............................................................................................................................................. 548

6.414 MSS_7039_01001.............................................................................................................................................. 549

6.415 MSS_7039_01002.............................................................................................................................................. 550

6.416 MSS_7039_01003.............................................................................................................................................. 551

6.417 MSS_7039_01004.............................................................................................................................................. 552

6.418 MSS_7039_02000.............................................................................................................................................. 553

6.419 MSS_7039_02001.............................................................................................................................................. 555

6.420 MSS_7039_02003.............................................................................................................................................. 557

6.421 MSS_7039_02004.............................................................................................................................................. 559

6.422 MSS_7039_02005.............................................................................................................................................. 560

6.423 MSS_7039_02006.............................................................................................................................................. 561

6.424 MSS_7039_02007.............................................................................................................................................. 562

6.425 MSS_7039_03000.............................................................................................................................................. 563

6.426 MSS_7039_04000.............................................................................................................................................. 564

6.427 MSS_7039_04001.............................................................................................................................................. 565

6.428 MSS_7039_05000.............................................................................................................................................. 566

Alcatel-Lucent Confidential Table of contents xviii


6.429 MSS_7040_00000.............................................................................................................................................. 568

6.430 MSS_7040_00001.............................................................................................................................................. 569

6.431 MSS_7040_00002.............................................................................................................................................. 570

6.432 MSS_7041_00000.............................................................................................................................................. 571

6.433 MSS_7041_00001.............................................................................................................................................. 572

6.434 MSS_7041_00050.............................................................................................................................................. 573

6.435 MSS_7041_00051.............................................................................................................................................. 574

6.436 MSS_7041_00052.............................................................................................................................................. 575

6.437 MSS_7041_00150.............................................................................................................................................. 576

6.438 MSS_7041_00151.............................................................................................................................................. 578

6.439 MSS_7041_00200.............................................................................................................................................. 579

6.440 MSS_7041_00250.............................................................................................................................................. 580

6.441 MSS_7041_00251.............................................................................................................................................. 581

6.442 MSS_7041_00252.............................................................................................................................................. 582

6.443 MSS_7041_00253.............................................................................................................................................. 583

6.444 MSS_7041_00300.............................................................................................................................................. 584

6.445 MSS_7041_00301.............................................................................................................................................. 585

6.446 MSS_7041_00302.............................................................................................................................................. 586

6.447 MSS_7041_00400.............................................................................................................................................. 588

6.448 MSS_7041_00401.............................................................................................................................................. 589

6.449 MSS_7041_00500.............................................................................................................................................. 590

6.450 MSS_7041_00600.............................................................................................................................................. 591

6.451 MSS_7041_00601.............................................................................................................................................. 593

6.452 MSS_7041_00602.............................................................................................................................................. 595

6.453 MSS_7041_00603.............................................................................................................................................. 596

6.454 MSS_7041_00604.............................................................................................................................................. 597

6.455 MSS_7041_00605.............................................................................................................................................. 598

6.456 MSS_7041_00606.............................................................................................................................................. 599

6.457 MSS_7041_00700.............................................................................................................................................. 600

6.458 MSS_7041_00701.............................................................................................................................................. 602

6.459 MSS_7041_00703.............................................................................................................................................. 603

6.460 MSS_7041_00800.............................................................................................................................................. 604

6.461 MSS_7041_00801.............................................................................................................................................. 605

6.462 MSS_7041_00802.............................................................................................................................................. 606

6.463 MSS_7042_00001.............................................................................................................................................. 607

Alcatel-Lucent Confidential Table of contents xix


6.464 MSS_7042_00002.............................................................................................................................................. 609

6.465 MSS_7042_00003.............................................................................................................................................. 610

6.466 MSS_7042_00004.............................................................................................................................................. 611

6.467 MSS_7042_04201.............................................................................................................................................. 612

6.468 MSS_7042_04202.............................................................................................................................................. 613

6.469 MSS_7054_00100.............................................................................................................................................. 614

6.470 MSS_7054_00101.............................................................................................................................................. 615

6.471 MSS_7054_00102.............................................................................................................................................. 616

6.472 MSS_7054_00103.............................................................................................................................................. 617

6.473 MSS_7054_00104.............................................................................................................................................. 618

6.474 MSS_7054_00105.............................................................................................................................................. 619

6.475 MSS_7057_00001.............................................................................................................................................. 620

6.476 MSS_7057_00002.............................................................................................................................................. 622

6.477 MSS_7057_00003.............................................................................................................................................. 623

6.478 MSS_7057_00004.............................................................................................................................................. 624

6.479 MSS_7057_00005.............................................................................................................................................. 625

6.480 MSS_7059_00000.............................................................................................................................................. 626

6.481 MSS_7060_01000.............................................................................................................................................. 627

6.482 MSS_7060_01100.............................................................................................................................................. 629

6.483 MSS_7060_01200.............................................................................................................................................. 630

6.484 MSS_7060_01201.............................................................................................................................................. 631

6.485 MSS_7060_01300.............................................................................................................................................. 633

6.486 MSS_7060_01400.............................................................................................................................................. 634

6.487 MSS_7060_01500.............................................................................................................................................. 635

6.488 MSS_7060_01600.............................................................................................................................................. 636

6.489 MSS_7060_01700.............................................................................................................................................. 637

6.490 MSS_7060_01800.............................................................................................................................................. 638

6.491 MSS_7060_01900.............................................................................................................................................. 640

6.492 MSS_7060_02000.............................................................................................................................................. 641

6.493 MSS_7070_01000.............................................................................................................................................. 642

6.494 MSS_7070_01001.............................................................................................................................................. 643

6.495 MSS_7070_01002.............................................................................................................................................. 644

6.496 MSS_7070_01003.............................................................................................................................................. 645

6.497 MSS_7070_01004.............................................................................................................................................. 646

6.498 MSS_7070_01005.............................................................................................................................................. 647

Alcatel-Lucent Confidential Table of contents xx


6.499 MSS_7070_01006.............................................................................................................................................. 648

6.500 MSS_7070_01007.............................................................................................................................................. 649

6.501 MSS_7070_01008.............................................................................................................................................. 650

6.502 MSS_7070_01010.............................................................................................................................................. 651

6.503 MSS_7070_01011.............................................................................................................................................. 652

6.504 MSS_7070_01012.............................................................................................................................................. 653

6.505 MSS_7070_01013.............................................................................................................................................. 654

6.506 MSS_7070_01014.............................................................................................................................................. 655

6.507 MSS_7070_02001.............................................................................................................................................. 656

6.508 MSS_7070_02002.............................................................................................................................................. 657

6.509 MSS_7070_02003.............................................................................................................................................. 658

6.510 MSS_7070_02004.............................................................................................................................................. 659

6.511 MSS_7070_02005.............................................................................................................................................. 660

6.512 MSS_7070_02006.............................................................................................................................................. 661

6.513 MSS_7070_02007.............................................................................................................................................. 662

6.514 MSS_7070_02008.............................................................................................................................................. 663

6.515 MSS_7070_02011.............................................................................................................................................. 664

6.516 MSS_7070_02012.............................................................................................................................................. 665

6.517 MSS_7070_02013.............................................................................................................................................. 666

6.518 MSS_7070_02014.............................................................................................................................................. 667

6.519 MSS_7070_02015.............................................................................................................................................. 668

6.520 MSS_7070_02016.............................................................................................................................................. 669

6.521 MSS_7070_02017.............................................................................................................................................. 670

6.522 MSS_7070_02018.............................................................................................................................................. 671

6.523 MSS_7078_00050.............................................................................................................................................. 672

6.524 MSS_7078_00051.............................................................................................................................................. 673

6.525 MSS_7078_00052.............................................................................................................................................. 674

6.526 MSS_7078_00053.............................................................................................................................................. 675

6.527 MSS_7078_00054.............................................................................................................................................. 676

6.528 MSS_7078_00055.............................................................................................................................................. 677

6.529 MSS_7078_00056.............................................................................................................................................. 678

6.530 MSS_7078_00057.............................................................................................................................................. 679

6.531 MSS_7078_00058.............................................................................................................................................. 680

6.532 MSS_7078_00059.............................................................................................................................................. 681

6.533 MSS_7078_00061.............................................................................................................................................. 682

Alcatel-Lucent Confidential Table of contents xxi


6.534 MSS_7078_00100.............................................................................................................................................. 683

6.535 MSS_7078_00101.............................................................................................................................................. 684

6.536 MSS_7078_00206.............................................................................................................................................. 685

6.537 MSS_7078_00300.............................................................................................................................................. 686

6.538 MSS_7078_00400.............................................................................................................................................. 687

6.539 MSS_7078_00401.............................................................................................................................................. 688

6.540 MSS_7078_00500.............................................................................................................................................. 689

6.541 MSS_7078_00501.............................................................................................................................................. 690

6.542 MSS_7078_00502.............................................................................................................................................. 691

6.543 MSS_7079_00000.............................................................................................................................................. 692

6.544 MSS_7079_00100.............................................................................................................................................. 693

6.545 MSS_7079_00101.............................................................................................................................................. 694

6.546 MSS_7079_00102.............................................................................................................................................. 695

6.547 MSS_7079_00103.............................................................................................................................................. 697

6.548 MSS_7079_00200.............................................................................................................................................. 698

6.549 MSS_7079_00201.............................................................................................................................................. 699

6.550 MSS_7079_00202.............................................................................................................................................. 700

6.551 MSS_7079_00203.............................................................................................................................................. 701

6.552 MSS_7079_00300.............................................................................................................................................. 702

6.553 MSS_7079_00301.............................................................................................................................................. 703

Alcatel-Lucent Confidential Table of contents xxii


Figure 1 - Alarm Manager window........................................................................................................ ............. ........... 5

Alcatel-Lucent Confidential List of figures xxiii


1 About this publicationThis publication contains the list of alarms as it is presented in the WMS Network Services Platform(known as "NSP") of the Alcatel-Lucent 9370 Radio Network Controller (9370 RNC). In case of acorrective action is required, the relevant maintenance document is pointed out by this document.Alarms presented in the Operation Administration and Maintenance (OAM) are listed, as well asInterface Node, Access Node and MSS POC alarms.

Applicability

This publication applies to the OAM06.0 System Release.

Audience

This publication is intended for operations and maintenance personnel (for example, 9370 RNCon-site maintenance engineers), and those who want to know corrective maintenance principles forRNC and POC.

Prerequisites

It is recommended that readers also become familiar with the following publications:

• Alcatel-Lucent 9370 Radio Network Controller - Technical Description (NN-20500-021)

• Alcatel-Lucent 9353 Management System - System Overview (NN-20500-031)

• Alcatel-Lucent 9353 Management System - User Guide (NN-20500-032)

Related documents

Alcatel-Lucent 9370 Radio Network Controller - Maintenance Guide (NN-20500-023)

Multiservice Switch documentation:

• Nortel Multiservice Switch 15000, 20000 Hardware Installation, Maintenance, and Upgrades(241-1501-240)

• Nortel Multiservice Switch 7400 Hardware Installation, Maintenance, and Upgrades(241-7401-240)

• Nortel Multiservice Switch 6400, 7400, 15000, 20000 Alarms Reference (NN-10600-500)

How this publication is organized

The document consists of the following modules:

• New in this release

• How to use this publication

• Control Node notifications and alarms

Alcatel-Lucent Confidential 1


• Access Node, Interface Node and POC alarms

Vocabulary conventions

For a list of W-CDMA terms used in this publication, see Alcatel-Lucent 9300 W-CDMA ProductFamily - Terminology (NN-20500-002).

The RNC Network Element naming refers to the Alcatel-Lucent 9370 Radio Network Controller (9370RNC).

The POC Network Element naming stands for the MSS-based POC.



2 UMTS Access Network Collection RoadmapFor collection roadmap, see Alcatel-Lucent 9300 W-CDMA Product Family - Document CollectionOverview and Update Summary (NN-20500-050).



3 New in this releaseThe following details what is new in RNC and MSS POC Alarms Reference Guide for the OAM06.0release.

Features• Alarm code display (30639)

• WMS compliance to marketing guidelines (30714)

Other changes

For the detailed list of removed, new or modified RNC alarms in the OAM06.0 release, seeAlcatel-Lucent 9300 W-CDMA Product Family - UA06.0 / OAM06.0 Release Operational Impacts:CM, FM and PM Delta (NN-20500-052).



4 How to use this publicationThis part describes how to use this publication.

Introduction

This publication contains the alarms and notifications (referred to as alarms in the following pages)related to the Control Node. It also contains the fault number information for the Interface Node, theAccess Node and MSS POC parts of the RNC.

The general principles and messages for the 9370 RNC maintenance are described in Alcatel-Lucent9353 Management System - User Guide (NN-20500-032).

Network maintenance is based on graphical supervision of the network. It is also based on theidentification and replacement of faulty items of equipment, using alarms.

Description of a Control Node alarm sheet

To display an RNC alarm help sheet, from the Alarm Manager window, right-click the alarm row andselect the Selected Item Help command.

For the other Alarm manager options, see Alcatel-Lucent 9353 Management System - User Guide(NN-20500-032).

Figure 1 Alarm Manager window

An alarm sheet contains a description providing the short explanation of the alarm and a tabledetailing the following information:



Alarm name: the cause name of the alarm

Alarm Code The alarm code, based on thefaultCodefield as displayed in the Alarm Record Viewer.See Alarm Code format.

RNC Type • 9370 RNC

• POC

Object Class List of equipment for the alarm.

Event Type Alarm type which contains the different events.

Probable Cause Alarm type which contains the different errors.

Severity Link to the urgency of the maintenance action.

Impact Description of how the service is affected.

Reason Cause Name for the alarm.

Remedial Action List of recommended responses which corres-ponds to corrective maintenance procedures(depends on release).

Alarm Code format

The alarm code uses the faultCode field as seen in the alarm record details. It specifies the alarmtype 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 OAM, RNC or MSS

• "Alarm code" is the alarm code of the equipment type

• "MO Object Id" is the Managed Object Id of the alarmed component.

Object Class• CNode

• ControlPort

• CSCoreNetworkAccess

• dynamicDATA[ranManagedObject]

• FDDCell

• HsdpaResource

• MMS

• NeighbouringRnc

• OMU



• PSCoreNetworkAccess

• RNC

• RNCEquipment

• RncMIB

• SasAccess

• SignallingLink

• TMU

Alarm Type and Probable Cause

Alarm Type Probable Cause

communications (Comm): an alarm of thistype is mainly associated with the proceduresand/or processes required to convey informa-tion from one point to another.

• communicationsSubsystemFailure

• configurationOrCustomizationError

• remoteNodeTransmissionError

• softwareProgramAbnormallyTerminated

• underlyingResourceUnavailable

environment • equipmentMalFunction

equipment (Eqp): an alarm of this type ismainly associated with an equipment fault. • equipmentMalfunction

• fileError

• heatingOrVentilationOrCoolingSystem-Problem

• powerProblem

• Suspended Upgrade

• transmitFailure

• Upgrade State

• versionMismatch

processing error (Proc): an alarm of this typeis mainly associated with software or pro-cessing fault.

• causeOfRestartOrSwitchover

• communicationsSubsystemFailure

• configurationOrCustomizationError

• congestion

• equipmentMalFunction



• versionMismatch

quality of service (Ser): an alarm of this type • causeOfRestartOrSwitchover



Alarm Type Probable Cause

is mainly associated with degradation in thequality of a service. • communicationsProtocolError

• corruptData

• sfwrEnvironmentProblem

• softwareError


• thresholdCrossed


• unspecifiedReason

Severity

The 9370 RNC uses the following perceived severity:

• critical. This alarm classification indicates that a service affecting condition has occurred and animmediate corrective action is required.

• major. This alarm classification indicates that a service affecting condition has developed and anurgent corrective action is required.

• minor. This alarm classification indicates the existence of a non service affecting fault conditionand that corrective action will have to be taken to prevent a more serious fault.

• warning. This alarm classification indicates the detection of a potential or impendingservice-affecting fault, before any significant effects have been felt.

This alarm must be manually deleted and cleared.

• cleared. This alarm classification indicates the clearing of one or more previously reportedalarms.

• unknown.

Description of an A-Node, I-Node or POC alarm sheet

Specific RNC alarms on W-CDMA are informed according to the following template:

• [Equipment type]_[Alarm code on 4 digits (0-9)]_[MO Object Id on 5 digits (0-9)]

Alarm fault code

• Component

AP (Adjunct Processor or PCI Mezzanine Card), LP (Logical Processor), Shelf/card, rncIn, Ss7Sccp, Ss7 Mtp3, Ss7 SaalNni.

All the alarms applicable to AP or LP impact the Packet Server module.

• Severity

Critical, Major, Minor, Warning or Indeterminate.



• Status

Message, Set, Clear or Set/Clear.

• Details

What has caused the alarm to occur; what impact the alarm will have on other components or thesystem.

• Remedial action

Tells the user what to do in response to the alarm.



5 Control Node notifications and alarmsFor convenience reasons, the CC1 module refers to CC-1 or ATM_SW. The TMU module refers toTMU-R.

This section describes the alarms generated on the Control Node, in the following order:

• alarms by diagnosis,

• OAM notifications.



5.1 RNC_2007_30467 - ANO OVERLOAD THRESHOLDThis alarm indicates that the RNC has reached the Critical overload level. This alarm will be clearedonce the RNC is not in Critical overlaod level. The ANO OVERLOAD THRESHOLD alarm appearson the graphical representation of the Control Node in RNC Equipment monitor.

ANO OVERLOAD THRESHOLD

Alarm Code RNC_2007_30467

RNC Type 9370 RNC

Object Class Cn

Event Type quality of service

Probable Cause congestion

Severity MAJOR

Impact The calls may be rejected. The RNC capacity may be reduced.

Reason ANO OVERLOAD THRESHOLD

Remedial Action Maintenance action is not applicable.



5.2 RNC_2028_30467 - ANO RESTART CONTEXTThis alarm indicates that a restart message follows a module restart. The ANO RESTART CONTEXTalarm appears on the graphical representation of the Control Node in RNC Equipment monitor. In theevent that an old ANO RESTART CONTEXT warning is present in the GUI, it is cleared whenanother Control Node board restarts.

ANO RESTART CONTEXT


RNC Type 9370 RNC

Object Class Cn


Probable Cause softwareProgramAbnormallyTerminated

Severity warning

Impact Impacted module localization is defined in additionalText by modulehardware slot position. A state change alarm on this module will havealready been raised. Here is how to decode the module type: moduletype 0 corresponds to SBC. Type 1 corresponds to PMC. Type 2 cor-responds to TM. Type 0xFF is not significant.

Reason ANO RESTART CONTEXT

Remedial Action None. The module is restarting and provides some root cause details.



5.3 RNC_3000_29700 - ANO OCNS FAILUREThis alarm indicates that FDDCell is enabled, but that OCNS cannot be established or has beenreleased. The ANO OCNS FAILURE alarm appears on the notification log tool and in the AlarmManager window.

ANO OCNS FAILURE


RNC Type 9370 RNC

Object Class FddCell

Event Type communications

Probable Cause underlyingResourceUnavailable

Severity warning

Impact OCNS is used at acceptance or during trials but never after networklaunch: If FDDCell is enabled but OCNS channel cannot be estab-lished (for example, not enough NodeB resource for OCNS, radio linksetup failure, no response) then no retry is performed. RNC send oneWARNING fault event for this FDDCell. In case the radio link is broken(for example NodeB CP is lost), the RNC try to reestablish OCNS atNBAP level as soon as possible after cell setup success (FDDCell isenabled) if activation criteria is still on (WARNING is sent if reestablish-ment fails). In case the Communication CP supporting OCNS is lost(for example CEM is lost) but FDDCell is still enabled, then no retry isperformed. RNC send one WARNING fault event for this FDDCell.

Reason ANO OCNS FAILURE

Remedial Action After an OCNS failure, the FDDCell must be locked/unlocked in orderto retry (or deactivate OCNS at FDDCell level).



5.4 RNC_3001_29696 - ANO CELL SWACT INFORMATIONN/A.

ANO CELL SWACT INFORMATION


RNC Type 9370 RNC

Object Class Rnc


Probable Cause performanceDegraded

Severity warning

Impact N/A.

Reason N/A.

Remedial Action N/A.



5.5 RNC_3002_29700 - ANO CIBS FAILUREThis alarm indicates that an FDDCell is enabled, but the CIBS cannot be established on it.

ANO CIBS FAILURE


RNC Type 9370 RNC




Severity warning

Impact N/A.

Reason N/A.




5.6 RNC_3003_29700 - ANO DEADLOCKSTATE DETECTIONThis alarm indicates that a deadlock situation has been detected on an FddCell. It is raised each timethe software detects an internal error on a specific cell. The ANO DEADLOCKSTATE DETECTIONalarm appears on the graphical representation of the RNC in Equipment monitor.

ANO DEADLOCKSTATE DETECTION


RNC Type 9370 RNC



Probable Cause softwareProgramAbnormallyTerminated

Severity warning

Impact FDDCell is disabled.

Reason ANO DEADLOCKSTATE DETECTION

Remedial Action Lock/unlock FDDCell Else reset CMU Else reset RNC.



5.7 RNC_3004_29755 - ANO CELL NOT HSDPA CAPABLEINFORMATION

This alarm indicates that the HSDPA configuration has failed, since NodeB is not HSDPA capable.The ANO CELL NOT HSDPA CAPABLE INFORMATION alarm appears on the graphicalrepresentation of the FDDCell in RNC Equipment monitor.

ANO CELL NOT HSDPA CAPABLE INFORMATION


RNC Type 9370 RNC

Object Class HsdpaResource


Probable Cause equipmentMalfunction

Severity warning

Impact The related FDDCell is in an Enabled/Degraded state, and the Cell isnot HSDPA.

Reason Software or hardware failure at the NodeB level, or lack of commis-sioning at the NodeB level. When this alarm is raised, the state changeevent on the related FDDCell shall be Enabled/degraded.

Remedial Action Check board status at the NodeB level.



5.8 RNC_3005_29755 - ANO HSDPA CONFIGURATION FAILUREINFORMATION

This alarm indicates that the HSDPA configuration failed despite the NodeB is HSDPA capable. TheANO HSDPA CONFIGURATION FAILURE INFORMATION alarm appears on the graphicalrepresentation of the FDDCell in RNC Equipment monitor.

ANO HSDPA CONFIGURATION FAILURE INFORMATION


RNC Type 9370 RNC



Probable Cause configurationOrCustomizationError

Severity warning

Impact The related FDDCell is in an Enabled/Degraded state.

Reason Too much power reserved for HSDPA, or configuration failure at theNodeB level. When this alarm is raised, the state change event on therelated FDDCell shall be Enabled/degraded.

Remedial Action Check configuration of the related FDDCell.



5.9 RNC_3006_29755 - ANO HSDPA HARDWARE RECOVERYINFORMATION

This alarm indicates that the FDDCell has recovered its HSDPA hardware. The ANO HSDPAHARDWARE RECOVERY INFORMATION alarm appears on the graphical representation of theFDDCell in RNC Equipment monitor.

ANO HSDPA HARDWARE RECOVERY INFORMATION


RNC Type 9370 RNC



Probable Cause causeOfRestartOrSwitchover

Severity warning

Impact HSDPA capability is down.

Reason H-BBU started or restarted after failure. When this alarm is raised, thestate change event on the related FDDCell shall be Enabled/degraded.

Remedial Action Lock/Unlock the FddCell, in order to recover the HSDPA capability.



5.10 RNC_3007_29700 - ANO DEGRADED CELL STATUSINFORMATION

This alarm indicates that the HSDPA is not up, though it should be. The ANO DEGRADED CELLSTATUS INFORMATION alarm appears on the graphical representation of the FDDCell in RNCEquipment monitor.

ANO DEGRADED CELL STATUS INFORMATION


RNC Type 9370 RNC




Severity warning

Impact The related FDDCell is in an Enabled/Degraded state.

Reason Failure at NodeB level.

Remedial Action None.



5.11 RNC_3008_29713 - ANO CORENETWORK CS DOMAINOVERLOAD

Core network CS domain is overloaded and sends RANAP Overload Control message to RNC

ANO CORENETWORK CS DOMAIN OVERLOAD


RNC Type

Object Class CsCoreNetworkAccess


Probable Cause bandwidthReduced

Severity

Impact RNC reduces RRC Initial Direct Transfer signaling messages to theoverloaded CS domain

Reason N/A.




5.12 RNC_3009_29714 - ANO CORENETWORK PS DOMAINOVERLOAD

Core network PS domain is overloaded and sends RANAP Overload Control message to RNC

ANO CORENETWORK PS DOMAIN OVERLOAD


RNC Type

Object Class PsCoreNetworkAccess



Severity

Impact RNC reduces RRC Initial Direct Transfer signaling messages to theoverloaded PS domain

Reason N/A.




5.13 RNC_3010_29713 - ANO RNC NOTIFY CORENETWORK CSDOMAIN OVERLOAD

RNC is overloaded and sends RANAP Overload Control message to Core Network CS domain

ANO RNC NOTIFY CORENETWORK CS DOMAIN OVERLOAD


RNC Type




Severity

Impact RNC requests Core Network CS domain to reduce signaling messagesto RNC

Reason N/A.




5.14 RNC_3011_29714 - ANO RNC NOTIFY CORENETWORK PSDOMAIN OVERLOAD

RNC is overloaded and sends RANAP Overload Control message to Core Network PS domain

ANO RNC NOTIFY CORENETWORK PS DOMAIN OVERLOAD


RNC Type




Severity

Impact RNC requests Core Network PS domain to reduce signaling messagesto RNC

Reason N/A.




5.15 RNC_3012_29772 - ANO CELL E-DCH DISABLED INFORMATIONThe FDDCell E-DCH that have been configured is disabled. Node B has sent a RSI with E-DCHDisabled information. This alarm would be triggered by a RSI E-DCH_Disabled.

ANO CELL E-DCH DISABLED INFORMATION


RNC Type 9370 RNC

Object Class EdchResource


Probable Cause applicationSubsystemFailure

Severity warning

Impact N/A.

Reason N/A.

Remedial Action Wait about 5 minutes for potential automatic recovery at Node B level.At the NodeB level, check board status.



5.16 RNC_3013_29772 - ANO E-DCH HARDWARE RECOVERYINFORMATION

The FDDCell has recovered its E-DCH hardware. An operator action is necessary (Lock/Unlock onthe FddCell) in order to recover the E-DCH capability.

ANO E-DCH HARDWARE RECOVERY INFORMATION


RNC Type 9370 RNC



Probable Cause causeOfRestartOrSwitchover

Severity warning

Impact N/A.

Reason E-BBU started or re-started after failure.

Remedial Action Lock unlock of the related FDDCell.



5.17 RNC_3014_29772 - ANO E-DCH CONFIGURATION FAILUREINFORMATION

The E-DCH configuration failed despite the NodeB is E-DCH capable.

ANO E-DCH CONFIGURATION FAILURE INFORMATION


RNC Type 9370 RNC




Severity warning

Impact N/A.

Reason Too much power for E-DCH channels or configuration failure at theNodeB Level.

Remedial Action Check configuration of the related FDDCell.



5.18 RNC_3015_29772 - ANO CELL NOT E-DCH CAPABLEINFORMATION

The E-DCH configuration failed since the NodeB is not E-DCH capable.

ANO CELL NOT E-DCH CAPABLE INFORMATION


RNC Type 9370 RNC




Severity warning

Impact N/A.

Reason Software or hardware failure at the NodeB Level. It can also be a lackof commissioning at the NodeB level. This alarm would be triggered bya RSI E-DCH_not_capable.

Remedial Action At the NodeB level, check board status.



5.19 RNC_3016_29772 - ANO EDCH WITHOUT HSDPA NOT ALLOWEDINFORMATION

The E-DCH configuration has not been performed because the HSDPA resources are notconfigured.

ANO EDCH WITHOUT HSDPA NOT ALLOWED INFORMATION


RNC Type 9370 RNC




Severity warning

Impact N/A.

Reason Several causes are possible: cell is not HSDPA capable, OMC-R dis-ables HSDPA capability of the cell, configuration of HSDPA has failed.

Remedial Action Check configuration of the related FDDCell (HSDPA resource).



5.20 RNC_3017_29713 - ANO OUTGOING CS RANAP RESET NOTACKNOWLEDGED

This alarm is raised to inform the maintenance system that the RNC did not receive a RANAPRESET ACKNOWLEDGEMENT message from the CN after unsuccessful repetitions of the RANAPRESET procedure. After the unsuccessful repetitions, the RNC abandons the Ranap procedure andresume normal operation. New calls are accepted but they might be not established.

ANO OUTGOING CS RANAP RESET NOT ACKNOWLEDGED


RNC Type 9370 RNC



Probable Cause thresholdCrossed

Severity warning

Impact Some calls could be left hanging at the core network side.

Reason N/A.

Remedial Action At the CN level, check IU application (Ranap layer) status and signal-ing layers status.



5.21 RNC_3018_29714 - ANO OUTGOING PS RANAP RESET NOTACKNOWLEDGED

This alarm is raised to inform the maintenance system that the RNC did not receive a RANAPRESET ACKNOWLEDGEMENT message from the CN after unsuccessful repetitions of the RANAPRESET procedure. After the unsuccessful repetitions, the RNC abandons the Ranap procedure andresume normal operation. New calls are accepted but they might be not established.

ANO OUTGOING PS RANAP RESET NOT ACKNOWLEDGED


RNC Type 9370 RNC




Severity warning

Impact Some calls could be left hanging at the core network side.

Reason N/A.

Remedial Action At the CN level, check IU application ( Ranap layer) status and signal-ing layers status.



5.22 RNC_3019_29722 - ANO IU FAILURELoss of IU connection to the Core Network detected. Cell barring will be applied. Failure of SS7connection or Core Network may have been the reason.

ANO IU FAILURE


RNC Type 9370 RNC

Object Class RadioAccessService



Severity MAJOR

Impact All mobiles on NodeBs connected to this RNC will be barred access.

Reason N/A.

Remedial Action Recover the IU link.



5.23 RNC_3020_29722 - ANO CORE NETWORK OVERLOADClass barring beginning due to automatic detection of core network overload. Calls will be barredfrom accessing the network. Although the RNC may not be in overload, the core network is indicatingcongestion. Class barring will be set at increasing levels as congestion continues.

ANO CORE NETWORK OVERLOAD


RNC Type 9370 RNC




Severity MAJOR

Impact Some mobiles will be barred access to the RNC. The number of barredmobiles will increase if the core network remains above the definedoverload threshold.

Reason N/A.

Remedial Action Increase processing on the Core Network.



5.24 RNC_3021_29722 - ANO RNC CONGESTIONClass barring beginning due to automatic detection of RNC. Calls will be barred from accessing thenetwork. Class barring will be set as growing levels of overload congestion continues.

ANO RNC CONGESTION


RNC Type 9370 RNC




Severity MAJOR

Impact Some mobiles will be barred access to the RNC. The number of barredmobiles will increase if the RNC Overload remains above the definedoverload threshold.

Reason N/A.

Remedial Action Ensure that all RNC processing cards are viewed at the OAM side.



5.25 RNC_3022_29722 - ANO LOCAL OVERLOADClass barring beginning due to automatic detection of local overload. Calls will be barred fromaccessing network. Class barring will be set as growing levels of overload congestion continues.

ANO LOCAL OVERLOAD


RNC Type 9370 RNC




Severity MAJOR

Impact Some mobiles will be barred access to the cells on the affected CMU.The number of barred mobiles will increase if the local overload re-mains above the defined overload threshold.

Reason N/A.

Remedial Action Investigate re-parenting the cells onto other CMUs.



5.26 RNC_3023_29722 - ANO MANUAL CLS CELL BARRINGClass barring beginning due to manual activation of Class/Cell Barring. Calls will be barred fromaccessing the network. The user must manually increase the levels if needed.

ANO MANUAL CLS CELL BARRING


RNC Type 9370 RNC




Severity MAJOR

Impact Some mobiles will be barred access to the RNC. The number of barredmobiles is defined by the manual barring percentage.

Reason N/A.

Remedial Action Complete the manual increase of barring levels.



5.27 RNC_3024_29713 - ANO SILENT IUCS DETECTEDNo Iu-cs call can be set up.

ANO SILENT IUCS DETECTED


RNC Type 9370 RNC




Severity MAJOR

Impact Partial or full RNC outage.

Reason The percentage of successful call attempts in the latest Silent Iu detec-tion period is lower than the provisioned threshold. Please check theconfigured value of RadioAccessSer-vice.silentIuDetection.callAttemptThreshold and RadioAccessSer-vice.silentIuDetection.numDetectionIntervals to ensure that they arereasonable. If so, check the system.

Remedial Action Please check Iu-cs link.



5.28 RNC_3025_29714 - ANO SILENT IUPS DETECTEDNo Iu-ps call can be set up.

ANO SILENT IUPS DETECTED


RNC Type 9370 RNC




Severity MAJOR

Impact Partial or full RNC outage.

Reason The percentage of successful call attempts in the latest Silent Iu detec-tion period is lower than the provisioned threshold. Please check theconfigured value of RadioAccessSer-vice.silentIuDetection.callAttemptThreshold and RadioAccessSer-vice.silentIuDetection.numDetectionIntervals to ensure that they arereasonable. If so, check the system.

Remedial Action Please check Iu-ps link.



5.29 RNC_3026_29700 - ANO NBAP SIB NEIGHBOURINGCELL LIMITREACHED

If SIB type = SIB11 -> Too much information to be coded in SIB11: 3GPP NBAP limitation reached. IfSIB type = SIB11, it indicates a lack of or a bad mobility management for calls in idle, cell_FACH,cell_PCH and URA_PCH for this serving cell: (1)Cause=0 the neighbour cells provisioning in SIB11is truncated; (2)Cause=1 no SIB11 is broadcasted. The cell state is changed accordingly.

ANO NBAP SIB NEIGHBOURINGCELL LIMIT REACHED


RNC Type 9370 RNC




Severity warning

Impact N/A.

Reason N/A.

Remedial Action If SIB type = SIB11 -> decrease the number of neighboring cells and/orthe number of information of each neighbour cell (use default values orunset optional parameters) in order to reduce the SIB11 size.



5.30 RNC_3027_29699 - ANO NODEB CALLS THRESHOLD CROSSEDThe NodeB is overload state for manual overload control.

ANO NODEB CALLS THRESHOLD CROSSED


RNC Type

Object Class Nodeb



Severity

Impact RNC reduces RLS Setup Request message to the overload Node B.

Reason The number of RLS in the Node B is crossed over the manualOver-loadThresholdEventA. This alarm is cleared when the number of RLSin the Node B is crossed down the manualOverloadThresholdEventB.

Remedial Action RNC filters the request of RLS established which is headed to theoverloaded node B.



5.31 RNC_3027_29792 - ANO ACCESS CLASS BARRING ACTIVATEDBY OPERATOR

This alarm is raised when the operator activates the access regulation profile for a set of NodeBs.

ANO ACCESS CLASS BARRING ACTIVATED BY OPERATOR


RNC Type 9370 RNC

Object Class AccessRegulationProfile



Severity minor

Impact The operator has reduced the traffic for a group of cells based on aspecified percentage of normal calls in either the CS or PS domain orboth. The set of normal access classes (0 through 9) defined in theprofile, being barred are rotated based on the restriction interval. Whenthe timer expires, the percentage of classes is rotated to the next set ofclasses. Emergency calls (access class 10) are not impacted by thisfeature.

Reason N/A.

Remedial Action Deactivate the profile when it is needed in order to get the end of fault.



5.32 RNC_3030_29700 - ANO CELL NOT MBMS CAPABLEINFORMATION

The Cell Setup fails either because (1) The NodeB reports the cell as not MBMS capable (in NBAPAudit Response, no MICH information or MICH information with Resource Operational StateDisabled), while the RNC expects the cell to have MBMS functions available. (2) Or the NodeB failsto setup the common transport channel for MCCH (NBAP Common Transport Setup Failure withcause MICH Not Supported) (3) Or the NodeB reports the cell as no longer MBMS capable (in NBAPResource Status Indication, no MICH information or MICH information with Resource OperationalState Disabled) Probable root cause: software or hardware failure at the NodeB Level. It can also bea lack of commissioning at the NodeB level.

ANO CELL NOT MBMS CAPABLE INFORMATION


RNC Type 9370 RNC




Severity warning

Impact The cell is put in 'disabled-failed' state

Reason N/A.

Remedial Action At the RNC level, align the cell configuration with the capability of theNodeB (configure the cell in order to remove the MBMS MCCH com-mon channel.)



5.33 RNC_3031_29699 - ANO NODEB ALCAP SSCOP UNAVAILABLEThere are 2 reasons that the alarm is raised: 1. When RNC inter-working with Node B withoutALCAP interface and the ALCAP SSCOP is provisioned on RNC, the alarm is raised if the ALCAPSSCOP link is not established on RNC within 60 seconds or the link went down. The alarm is clearedif the link is connected or re-connected, or the Node B is upgraded to support ALCAP interface. 2.When RNC inter-working with Node B with ALCAP interface, there is at least one cell in the Node Bwhose cell state is changed to DISABLED/FAILED or ENABLED/DEGARDED due to the ALCAPSSCOP link availability. The alarm is cleared if the link is connected or re-connected.

ANO NODEB ALCAP SSCOP UNAVAILABLE


RNC Type 9370 RNC

Object Class Nodeb


Probable Cause communicationsProtocolError

Severity MAJOR

Impact For the upgrade procedure, the Node B upgrade from a non-ALCAPinterface to an ALCAP interface may fail.

SSCOP would not be established between Node B and RNC.

Reason ALCAP SSCOP setup failure or SSCOP link failure.

Remedial Action Check the provisioning, physical connections and ATM connections.



5.34 RNC_3032_29708 - ANO PF GPO LIMIT 80 PC REACHEDThe total number of GPO counter-location objects reaches 80 percent of the fixed limit.

ANO PF GPO LIMIT 80 PC REACHED


RNC Type 9370 RNC

Object Class PerfScanner



Severity warning

Impact N/A.

Reason Addition of more counters or cells has caused the alarm.




5.35 RNC_3033_29708 - ANO PF GPO LIMIT 100 PC REACHED ANDLOW PRIORITY COUNTERS DISABLED

The total number of GPO counter-location objects reaches 100 percent of the fixed limit. RNC maydisable some low priority counters.

ANO PF GPO LIMIT 100 PC REACHED AND LOW PRIORITY COUNTERS DISABLED


RNC Type 9370 RNC

Object Class PerfScanner



Severity minor

Impact Complete report of non-low priority counters. Incomplete report of lowpriority counters.

Reason Excessive number of counters or cells has caused the alarm.

Remedial Action Decrease the number of GPO counters, especially the cell counters oraccept the dropped low priority counters.



5.36 RNC_3034_29699 - ANO NODEB IP USER PLANE FAILUREIf NodeB has been configured to support IP Transport as an option to carry User Plane traffic, thisalarm is raised when RNC detects loss if IP connectivity to the NodeB. All the Iub User Plane trafficcarried on the IP transport is lost and new traffic cannot be setup with IP transport The alarm iscleared when IP connectivity to the NodeB is established.

ANO NODEB IP USER PLANE FAILURE


RNC Type 9370 RNC

Object Class Nodeb


Probable Cause lossOfSignal

Severity MAJOR

Impact N/A.

Reason N/A.




5.37 RNC_3036_29819 - ANO LIMITED SRS DATAThis error indicates that there are not enough GPS Satellites available to the iSMLC. This impactsthe capability to provide assistance data.

ANO LIMITED SRS DATA


RNC Type 9370 RNC

Object Class IntegratedSMLC



Severity MAJOR

Impact If insufficient amount of GPS navigation data is available, AGPS posi-tioning MIGHT fail and consequently the positioning accuracy is com-promised.

Reason Not enough GPS Satellite data is available.

Remedial Action Lock/unlock IntegratedSMLC. Contact the operator of the SRS networkif the alarm persists.



5.38 RNC_3037_29819 - ANO NO SRS DATAThe iSMLC doesn't receive GPS Navigation Data messages from the SRS over any SRS link formore than 2 hours.

ANO NO SRS DATA


RNC Type 9370 RNC

Object Class IntegratedSMLC


Probable Cause communicationsSubsystemFailure

Severity CRITICAL

Impact The network cannot provide any GPS assistance data for locationbased services using AGPS technology. AGPS positioning is NOTavailable and consequently the positioning accuracy is compromised.

Reason The SRS is down or all links to the SRS are interrupted for more than 2hours.

Remedial Action Lock/unlock IntegratedSMLC. Verify/Correct srsIp/1 and srsIp/2. If thealarm is cleared, the procedure is completed.If the alarm persists andthe alarm has been raised by several instances, for the same SRS, re-quest the operator of the SRS network to take the appropriate action. Ifthe alarm is cleared, the procedure is completed.



5.39 RNC_3038_29820 - ANO OCNS CHANNEL FAIL INFOOCNS channel failure information. This alarm is raised to indicate that the OCNS channel or channeloperation has failed. The failure could be a result of the NodeB being forced to drop an OCNSchannel or an OCNS channel operation (setup/deletion/reconfiguration) has failed.

ANO OCNS CHANNEL FAIL INFO


RNC Type 9370 RNC

Object Class Ocns

Event Type equipment

Probable Cause processorProblem

Severity warning

Impact OCNS testing not available

Reason N/A.

Remedial Action Manual operator clear is required.



5.40 RNC_3039_29821 - ANO OCNSHSDPA FAIL INFOOCNS-HSDPA cannot be established due to channel failure for unavailable resources, incorrectinput parameters , or equipment malfunctions.

ANO OCNSHSDPA FAIL INFO


RNC Type 9370 RNC

Object Class OcnsHsdpa



Severity warning

Impact OCNS-HSDPA service not available.

Reason N/A.

Remedial Action Manual operator clear is required.



5.41 RNC_3040_29700 - ANO CELL SHUTDOWN INITIATEDThis alarm is generated when the operator shutdowns the FDDCell administrative state in case of amanagement operation.

ANO CELL SHUTDOWN INITIATED


RNC Type 9370 RNC




Severity warning

Impact FDDCell becomes disabled.

Reason During the shutdown phase, FDDCell is first barred and then FDDCellpower is progressively reduced.




5.42 RNC_3041_29700 - ANO CELL SHUTDOWN E911 CALLDETECTED

FDDCell shutdown has been requested but emergency call has been detected and additional timer islaunched in order to let emergency call terminate normally .

ANO CELL SHUTDOWN E911 CALL DETECTED


RNC Type 9370 RNC




Severity warning

Impact May lead to emergency call drop.

Reason .Emergency call has been detected after SoftShutdownTimer or Cell-ShrinkStepDuration expiry




5.43 RNC_3050_29696 - ANO GENERIC ALARMThe ANO GENERIC ALARM appears in the Alarm Manager window.

ANO GENERIC ALARM


RNC Type 9370 RNC

Object Class Rnc

Event Type environment


Severity warning

Impact None

Reason An alarm is raised on any board.




5.44 OAM_0013_00036 - SYSTEM RELEASE INCONSISTENTThis alarm indicates that provisionedSystemRelease parameter (RNC object) is different fromsystemRelease parameter (C-Node object) in Configuration report.The System release inconsistentalarm (OAM_13) appears on the graphical representation of the Control Node in RNC Equipmentmonitor.

System release inconsistent

Alarm Code OAM_0013_00036

RNC Type 9370 RNC

RAN managed object RNC/RNCEquipment/Cnode

Object Class N/A


Probable Cause versionMismatch

Severity CRITICAL

Impact C-Node and OMC are desynchronized.

Reason System release inconsistent.

Remedial Action Synchronize C-Node and OMC. For more information on synchroniza-tion, refer to Smart Activation command in Alcatel-Lucent 9353 Man-agement System - User Guide (NN-20500-032).



5.45 OAM_0014_00036 - LOSS OF SUPERVISIONThis alarm indicates that there was a loss of supervision with the CNode. OAMLinkAdmState equalto unlocked and CNode.unknownStatus equal to TRUE.The Loss of supervision alarm (OAM_14)appears on the graphical representation of the Control Node in RNC Equipment monitor.

Loss of supervision


RNC Type 9370 RNC


Object Class N/A



Severity CRITICAL

Impact The state of RNC and RNC 1500 is unknown due to loss of OAM link.

Reason Loss of OAM link between OMC and C-Node.

Remedial Action Wait for recovery; otherwise, reset the OMU module. For more inform-ation, refer to the procedure on replacing the OMU module in Alcatel-Lucent 9370 Radio Network Controller - Maintenance Guide(NN-20500-023).



5.46 OAM_0015_00036 - SUPERVISION INHIBITED BY OPERATORThis alarm indicates that OAMLinkAdministrativeState parameter (RNCEquipment object) is set tolocked. This alarm indicates that the RNC is no more supervised. OAM links with the RNC areclosed.The Supervision inhibited by operator alarm (OAM_15) appears on the graphicalrepresentation of the Control Node in RNC Equipment monitor.

Supervision inhibited by operator


RNC Type 9370 RNC

RAN managed object RNC

Object Class N/A



Severity warning

Impact The RNC and RNC 1500 supervision is inhibited because the OAM-LinkAdministrativeState is locked.

Reason Supervision inhibited by operator. OAM links with the RNC and RNC1500 are closed.

Remedial Action If the RNC and RNC 1500 supervision is required, set the OAMLinkAd-ministrativeState to unlocked. For more information, refer to the pro-cedure on replacing the OMU module in Alcatel-Lucent 9370 RadioNetwork Controller - Maintenance Guide (NN-20500-023).



5.47 OAM_0026_00036 - CONFIG REPORT DECODING FAILEDThis alarm indicates that the configuration report has not been decoded. The alarm is cleared on nextconfiguration report successfully decoded.The Config Report decoding failed alarm (OAM_26)appears on the graphical representation of the Control Node in RNC Equipment monitor.

Config report decoding failed


RNC Type 9370 RNC

RAN managed object RNC/RNCEquipment/CNode

Object Class N/A

Event Type processing error

Probable Cause communicationsProtocolError

Severity CRITICAL

Impact The RNC and RNC 1500 MIB is set to not built, online SET and CRE-ATE commands are not supported.

Reason Config Report decoding failed.

Remedial Action Launch a RNC and RNC 1500 MIB build.



5.48 OAM_0045_00036 - THRESHOLD OVERCROSS ON RNCCOUNTER

The engineering teams of operators associate threshold rule sets and conditions to counters in orderto monitor overall health of the network in almost Near Time. Upon violation of these conditions theauthorized users shall be notified through e-mail, paging, or alarms of the degradation of theperformance of the network and their root causes. These thresholds are checked on the fly whenreceiving observation records coming from RNC or BTS. The Threshold overcross on RNC counteralarm (OAM_45) appears on the graphical representation of dynamicDATA[counterName] in RNCEquipment monitor.

Threshold overcross on RNC counter


RNC Type 9370 RNC

RAN managed object dynamicDATA[ranManagedObject]

Object Class N/A



Severity CRITICAL

Impact N/A

Reason Flooded alarm:dynamicDATA[yesNo]:dynamicDATA[locationID]Counter name: dynamicDATA[counterName] Counter value: dynam-icDATA[CounterValue] Threshold value: dynam-icDATA[ThresholdValue] Threshold Reference Period (min): dynam-icDATA[ThresholdReferencePeriod] obsDuration (min): dynam-icDATA[ObsDuration].

Remedial Action Check the threshold configuration.



5.49 OAM_0047_00036 - MEASUREMENT FILE DECODING FAILEDMeasurement files retrieved are corrupted or have a wrong format. This alarm is raised once for thesame condition.

Measurement file decoding failed


RNC Type NA


Object Class N/A


Probable Cause corruptData

Severity MAJOR

Impact No Measurement file available because of a Measurement file decod-ing failure.

Reason Bad data file:dynamicDATA [corruptedFileName].

Remedial Action Check if the file is present on the network element. If it is, check thatthe file properties are the same.

It is possible that an error happened during the file transfer. If the filesizes do not agree, manually transfer the files and replace the badone.



5.50 OAM_0048_00036 - RNC MEASUREMENT FILE MISSINGMeasurement files did not arrived in the expected time interval. This alarm is raised once for thesame condition.The RNC Measurement file missing alarm (OAM_48) appears on the graphicalrepresentation of dynamicDATA in RNC Equipment monitor.

RNC Measurement file missing


RNC Type 9370 RNC


Object Class N/A


Probable Cause fileError

Severity MAJOR

Impact N/A

Reason File not arrived[late file or lost file]: dynamicDATA[MissingFileName].

Remedial Action Check if the file is present on the network element. It is possible thatthe file was not transferred for some reason, or may have been gener-ated later than expected, and was not there when expected.

If the file is present on the NE, then manually transfer it for processing.



5.51 OAM_0049_00036 - CONNECTION FAILED TO RETRIEVEMEASUREMENT FILES

This alarm is generated in case of inability of performance server to retrieve the measurement files.This alarm is not an indication of connection status with the NE. This alarm is generated when theNE is down, the link is down or in case of bad userid or password. This alarm is raised once for thesame condition.The Connection failed to retrieve Measurement files alarm (OAM_49) has an objectId equals to the NE ID (that is RNC or BTSequipment). The subComponentId equals to Cnode, Inodeor Anode for the RNC, empty for the BTS.

Connection failed to retrieve Measurement files


RNC Type NA


Object Class N/A



Severity MAJOR

Impact N/A

Reason Loss of connection:dynamicDATA [connectionErrorOrLoginFailure].

Remedial Action • Ensure that the LAN connections are in service, there may be aproblem external to the NE preventing the connection from beingestablished.

• Ensure that the ftp processes are running, for some reason theprocesses may have died or been disabled.

• Ensure that the login has not changed.

• Ensure that the measurement files are present (or not) on the net-work element, there may be a maintenance action in progress, orsome other reason the files may not be accessible.

• Ensure that the network element is able to accept ftp connections.



5.52 OAM_0062_00057 - THRESHOLD OVERCROSS ON POCCOUNTER

The engineering teams of operators associate threshold rule sets and conditions to counters in orderto monitor overall health of the network in almost Near Time. Upon violation of these conditions theauthorized users shall be notified through e-mail, paging, or alarms of the degradation of theperformance of the network and their root causes. These thresholds are checked on the fly whenreceiving observation records coming from RNC or BTS

Threshold overcross on POC counter


RNC Type POC

RAN managed object POC

Object Class N/A



Severity CRITICAL

Impact N/A

Reason The engineering teams of operators associate threshold rule sets andconditions to counters in order to monitor overall health of the networkin almost Near Time. Upon violation of these conditions the authorizedusers shall be notified through e-mail, paging, or alarms of the degrad-ation of the performance of the network and their root causes. Thesethresholds are checked on the fly when receiving observation recordscoming from POC.

Remedial Action Check the threshold configuration.



5.53 OAM_0063_00057 - POC MEASUREMENT FILE DECODINGFAILED

This alarm indicates that the measurement files retrieved are corrupted or have a wrong format. Thisalarm is raised once for the same condition.

POC measurement file decoding failed


RNC Type POC


Object Class N/A



Severity MAJOR

Impact Measurement file decoding failed.

Reason Bad data file: dynamicDATA[corruptedFileName].

Remedial Action Consult next level of support.



5.54 OAM_0064_00057 - POC MEASUREMENT FILE DID NOT ARRIVEThis alarm indicates that the measurement files did not arrived in the expected time interval. Thisalarm is raised once for the same condition.

POC measurement file did not arrive


RNC Type POC


Object Class N/A


Probable Cause fileError

Severity MAJOR

Impact Measurement file missing rootCause dynamicData[FTSError].

Reason File not arrived [late file or lost file]: dynamicDATA[MissingFileName].

Remedial Action Consult next level of support.



5.55 OAM_0065_00057 - CONNECTION FAILED TO RETRIEVEMEASUREMENT FILES

This alarm is generated in case of inability of Performance server to retrieve the Measurement files.This alarm is not an indication of connection status with the NE. This alarm is generated when theNE is down, the link is down or in case of bad userid-password. This alarm is raised once for thesame condition

Connection failed to retrieve measurement files


RNC Type POC


Object Class N/A



Severity MAJOR

Impact N/A

Reason This alarm is generated in case of inability of Performance server to re-trieve the Measurement files. This alarm is not an indication of connec-tion status with the NE. This alarm is generated when the NE is down,the link is down or in case of bad userid-password. This alarm is raisedonce for the same condition.

Remedial Action • Ensure that the LAN connections are in service, there may be aproblem external to the NE preventing the connection from beingestablished.

• Ensure that the ftp processes are running, for some reason theprocesses may have died or been disabled.

• Ensure that the login has not changed.

• Ensure that the measurement files are present (or not) on the net-work element, there may be a maintenance action in progress, orsome other reason the files may not be accessible.

• Ensure that the network element is able to accept ftp connections.



5.56 OAM_0066_00057 - LOSS OF SUPERVISIONThis alarm indicates that there was a loss of supervision with the POC. OAMLinkAdmState equal tounlocked and POC.unknownStatus equal to TRUE.

Loss of supervision


RNC Type POC


Object Class N/A



Severity CRITICAL

Impact The state of POC is unknown due to loss of OAM link.

Reason Loss of OAM link between OMC and POC.

Remedial Action • Check the link between the POC and the OAM

• Check if the POC has restarted



5.57 OAM_0067_00057 - SUPERVISION INHIBITED BY OPERATORThis alarm indicates that OAMLinkAdministrativeState parameter (POC NE) is set to locked. Thisalarm indicates that the POC is no more supervised. OAM link with the POC is closed.TheSupervision inhibited by operator alarm (OAM_67) appears on the graphical representation of thePOC Equipment monitor.

Supervision inhibited by operator


RNC Type POC


Object Class N/A



Severity warning

Impact The POC supervision is inhibited because the OAMLinkAdministrat-iveState is locked.

Reason Supervision inhibited by operator. OAM link with the POC is closed.

Remedial Action If the POC supervision is required, set the OAMLinkAdministrat-iveState to unlocked.



5.58 OAM_0068_00057 - CONFIGURATION DE-SYNCHRONIZATIONThis alarm is generated when a configuration de-synchronization occurs between POC and OAMdatabase.

Configuration de-synchronization


RNC Type POC


Object Class N/A



Severity MAJOR

Impact POC CM XML Export is not aligned with current POC current configur-ation.

Reason This alarm is generated when a configuration de-synchronization oc-curs between POC and OAM database.

Remedial Action Launch manual resynchronization on the POC.



5.59 RNC_0004_00020 - UNKNOWN SOFTWARE VERSIONThis alarm indicates that runningSoftwareVersion parameter (CnodeSoftware object) contained inReport Build is different from the runningSoftwareVersion parameter stored in OMC database.TheUnknown software version alarm (OAM_4) appear son the graphical representation of the ControlNode in RNC Equipment monitor.

Unknown software version


RNC Type 9370 RNC


Object Class N/A


Probable Cause sfwrEnvironmentProblem

Severity CRITICAL

Impact None. While the C-Node upgrade is achieved in local mode (versusthe remote one from OMC), C-Node and OMC are desynchronized.

Reason Unknown software version. SoftwareVersion contained in the Report-Build not found in Software Repository Server (SRS). This case hap-pens when: C-Node,OMU, MMS disks are replaced with a new onethat contains software not stored in SRS. This case happens when theoperator has removed the software version from the SRS.

Remedial Action Restore the RNC and 1500 software on OMC. For more information onsoftware installation of Control Node, refer to the procedure on repla-cing the OMU module in Alcatel-Lucent 9370 Radio Network Controller- Maintenance Guide (NN-20500-023).



5.60 RNC_0006_00020 - STATE CHANGE TO UNLOCKED DISABLEDFAILED

This alarm indicates that operationalState parameter (TMU object) is set to disabled, thatadministrativeState parameter (TMU object) is set to unlocked and that availabilityStatus parameter(TMU object) is set to failed.The State change to disabled failed alarm (OAM_6) appears on thegraphical representation of the TMU module in RNC Equipment monitor.

State change to unlocked disabled failed


RNC Type

RAN managed object RNC/RNCEquipment/CNode/TMU

Object Class N/A



Severity MAJOR

Impact One TMU module is unavailable and the UMTS service is not possibleon FDDCell impacted. Refer to Underlying Resource Unavailable onFDDCell (state change to disable failed): OAM_21.

Reason The TMU module is not operational.

Remedial Action Wait for recovery. Otherwise, reset the OMU module or replace theTMU module. For more information, see Alcatel-Lucent 9370 RadioNetwork Controller - Maintenance Guide (NN-20500-023).



5.61 RNC_0009_00056 - MIB NOT BUILTThis alarm indicates that in Configuration report the mibState parameter (RncMIB object) is set tonotBuilt.The MIB not built alarm (OAM_9) appears on the graphical representation of the RNCMibobject in RNC Equipment monitor.

MIB not built


RNC Type 9370 RNC

RAN managed object RNC/RncMIB

Object Class N/A



Severity CRITICAL

Impact The RNC and RNC 1500 are not operational.

Reason The MIB state is not built.

Remedial Action Launch a RNC MIB build from OAM.




This alarm indicates that OSI state change has operationalState parameter (CC1 object) which is setto disabled, that administrativeState parameter (CC1 object) is set to unlocked, and thatavailabilityStatus parameter (CC1 object) is set to failed.The State change to disabled failed alarm(OAM_18) appears on the graphical representation of the CC1 module in RNC Equipment monitor.



RNC Type

RAN managed object RNC/RNCEquipment/CNode/CC1

Object Class N/A



Severity MAJOR

Impact The modules are redundant; there is no impact on the service.

Reason The CC1 module is not operational.

Remedial Action Replace the CC1 module with a new one. For more information on re-placement, refer to the procedure on replacing the CC1 module in Alc-atel-Lucent 9370 Radio Network Controller - Maintenance Guide(NN-20500-023).




This alarm indicates that OSI state change has operationalState parameter (OMU object) which isset to disabled, that administrativeState parameter (OMU object) is set to unlocked, and thatavailabilityStatus parameter (OMU object) is set to failed.The State change to disabled failed alarm(OAM_19) appears on the graphical representation of the OMU module in RNC Equipment monitor.



RNC Type

RAN managed object RNC/RNCEquipment/CNode/OMU

Object Class N/A



Severity MAJOR


Reason The OMU module is not operational.

Remedial Action Replace the OMU module with a new one. For more information on re-placement, refer to the procedure on replacing the OMU module in Alc-atel-Lucent 9370 Radio Network Controller - Maintenance Guide(NN-20500-023).




This alarm indicates that OSI state change has operationalState parameter (MMS object) which isset to disabled, that administrativeState parameter (MMS object) is set to unlocked, and thatavailabilityStatus parameter (MMS object) is set to failed.The State change to disabled failed alarm(OAM_20) appears on the graphical representation of the MMS module in RNC Equipment monitor.



RNC Type

RAN managed object RNC/RNCEquipment/CNode/dynamicDATA[OMU/MMS or MMS]

Object Class N/A



Severity MAJOR


Reason The OMU module is not operational.

Remedial Action Replace the OMU module with a new one. For more information on re-placement, refer to the procedure on replacing the MMS module in Alc-atel-Lucent 9370 Radio Network Controller - Maintenance Guide(NN-20500-023).



5.65 RNC_0021_00020 - STATE CHANGE TO UNLOCKED OR LOCKEDDISABLED FAILED

This alarm indicates that OSI state change has availabilityStatus parameter (FDDCell object) whichis set to failed and that operationalState parameter (FDDCell object) is set to disabled. This alarm isgenerated whatever the administrativeState.The State change to Disable Failed alarm (OAM_21)appears on the graphical representation of the FDDCell object in RNC Equipment monitor.

State change to unlocked or locked disabled failed


RNC Type 9370 RNC

RAN managed object RNC/NodeB/FDDCell

Object Class N/A



Severity CRITICAL

Impact UMTS service is not possible on impacted FDDCell or the FDDCell isout of order or the operator modifies the administrative state.

Reason The father NodeB has a hardware failure.




5.66 RNC_0022_00020 - STATE CHANGE TO UNLOCKED ENABLEDDEGRADED

This alarm indicates that OSI state change has availabilityStatus parameter (CsCoreNetworkAccessobject), which is set to enabled, and that operationalState parameter (CsCoreNetworkAccess object)is set to degraded.The State change to Enable Degraded alarm (OAM_22) appears on the graphicalrepresentation of the CsCoreNetworkAccess object in RNC Equipment monitor.

State change to unlocked enabled degraded


RNC Type 9370 RNC

RAN managed object RNC/CsCoreNetworkAccess

Object Class N/A



Severity CRITICAL

Impact Loss of capacity.

Reason SCCP is up and at least one (not all) of the ALCAP Routesets is downor at least one AAL2IF is down.

Remedial Action Check the transmission of Iu interface.



5.67 RNC_0023_00020 - STATE CHANGE TO UNLOCKED DISABLEDDEPENDENCY

This alarm indicates that OSI state change has availabilityStatus parameter (PsCoreNetworkAccessobject), which is set to dependency, and that operationalState parameter (PsCoreNetworkAccessobject) is set to disabled.The State change to Disable Dependency alarm (OAM_23) appears on thegraphical representation of the PsCoreNetworkAccess object in RNC Equipment monitor.

State change to unlocked disabled dependency


RNC Type 9370 RNC

RAN managed object RNC/PsCoreNetworkAccess

Object Class N/A



Severity CRITICAL

Impact UMTS PS service is not possible on the RNC and RNC 1500.

Reason Signaling Connection Control Part (SCCP) is not up or the Routeset isdisabled.





This alarm indicates that OSI state change has availabilityStatus parameter (NeighbouringRncobject) which is set to degraded and that operationalState parameter (NeighbouringRnc object) is setto enabled.The State change to Enable Degraded alarm (OAM_24) appears on the graphicalrepresentation of the NeighbouringRnc object in RNC Equipment monitor.



RNC Type 9370 RNC

RAN managed object RNC/NeighbouringRNC

Object Class N/A



Severity CRITICAL

Impact UMTS HO service is not possible between the RNC and the impactedneighbouring RNC.

Reason NeighbouringRNC is accessible, but some (not all) of the AlcapDistant-SigEntities are not accessible or some AAL2IFs are down.

Remedial Action Check the transmission of Iur interface.



5.69 RNC_0028_00020 - STATE CHANGE TO UNLOCKED OR LOCKEDENABLED DEGRADED

This alarm indicates that OSI state change has availabilityStatus parameter (FDDCell object), whichis set to degraded, and that operationalState parameter (FDDCell object) is set to enabled. Thisalarm is generated whatever the administrativeState.The State change to Enable Degraded alarm(OAM_28) appears on the graphical representation of the FDDCell object in RNC Equipmentmonitor.

State change to unlocked or locked enabled degraded


RNC Type 9370 RNC


Object Class N/A



Severity CRITICAL

Impact Loss of capacity on FDDCell. If Iux paths are locked for more than 9minutes, then the CNode may not re-establish the CTCH channels.

Reason Loss of some common channels.

Remedial Action Check the alarms on BTSEquipment object. Lock/unlock the FDDCellin order to recover the channels.




This alarm indicates that OSI state change has availabilityStatus parameter (CsCoreNetworkAccessobject) which is set to dependency and that operationalState parameter (CsCoreNetworkAccessobject) is set to disabled.The State change to Disable Dependency alarm (OAM_29) appears on thegraphical representation of the CsCoreNetworkAccess object in RNC Equipment monitor.



RNC Type 9370 RNC


Object Class N/A



Severity CRITICAL

Impact Loss of capacity.

Reason Signalling Connection Control Part (SCCP) stack is down, QAAL2stack is down, Routeset (either SCCP or ALCAP) is disabled/down, allAAL2IFs for this access are down.




5.71 RNC_0030_00020 - STATE CHANGE TO UNLOCKED OR LOCKEDDISABLED DEPENDENCY

This alarm indicates that OSI state change has availabilityStatus parameter (FDDCell object) whichis set to dependency and that operationalState parameter (FDDCell object) is set to disabled. Thisalarm is generated whatever the administrativeState.The State change to Disable Dependency alarm(OAM_30) appears on the graphical representation of the FDDCell object in RNC Equipmentmonitor.

State change to unlocked or locked disabled dependency


RNC Type 9370 RNC


Object Class N/A



Severity CRITICAL

Impact Loss of capacity on FDDCell.

Reason The father NodeB is locked by the operator. The core process handlingthe father NodeB could not be launched during the RNC and RNC1500 setup. The core process handling the father NodeB goes downdue to a TMU failure.

Remedial Action Check the alarms on iBTSEquipment object.




This alarm indicates that OSI state change has availabilityStatus parameter (NeighbouringRncobject) which is set to dependency and that operationalState parameter (NeighbouringRnc object) isset to disabled.The State change to Disable Dependency alarm (OAM_31) appears on the graphicalrepresentation of the NeighbouringRnc object in RNC Equipment monitor.



RNC Type 9370 RNC


Object Class N/A



Severity CRITICAL

Impact UMTS HO service is not possible between the RNC and the impactedneighbouring RNC.

Reason Signalling Connection Control Port (SCCP) Routeset is not accessible,or all of the AlcapDistantSidEntities are not accessible, or SCCP orQAAL2 stacks are not up, or all AAL2IFs for this access are down.

Remedial Action Check the transmission of Iur interface.



5.73 RNC_0037_00036 - CNODE INTERNAL SYNCHRONIZATIONERROR

This alarm indicates that Manage Objects (MO) are defined in the C-Node MIB, but some attributeshave partly caused the activation phase failure.The Activated synchronized with error alarm(OAM_37) appears on the graphical representation of the Control Node in RNC Equipment monitor.

Cnode internal synchronization error


RNC Type 9370 RNC


Object Class N/A


Probable Cause softwareError

Severity CRITICAL

Impact Inconsistency between OAM and RNC parameters.

Reason This alarm is generated when C-Node rejects set-online or create-on-line during C-Node applications update.

Remedial Action RGE KO (that is the failure of the synchronisation with the C-Node ap-plications) is an exceptional error case. Contact Nortel Support Ser-vices for investigation. Only they can decide what is the remedial ac-tion plan, perform or not build on the NE.



5.74 RNC_0038_00004 - STATE CHANGE TO UNLOCKED DISABLEDNOT INSTALLED

This alarm indicates that an extraction of a module is detected.The State change to disabled notinstalled alarm (OAM_38) appears on the graphical representation of the CC1 module in RNCEquipment monitor.

State change to unlocked disabled not installed


RNC Type

RAN managed object RNC/RNCEquipment/CNode/CC1

Object Class N/A



Severity MAJOR

Impact The modules are redundant. If the first module is involved, there is noimpact on the service.

Reason underlyingResourceUnavailable.

Remedial Action If the alarm occurs when extracting the CC1 module, just proceed; oth-erwise, replace the old module with a new one. For more informationon replacement, refer to the procedure on replacing the CC1 module inAlcatel-Lucent 9370 Radio Network Controller - Maintenance Guide(NN-20500-023). If a CC1 module is unplugged while the RNC is cre-ated or destroyed and recreated (rehoming or upgrade with modelchange), no alarm is generated.




This alarm indicates that an extraction of a module is detected.The State change to disabled notinstalled alarm (OAM_39) appears on the graphical representation of OMU module in RNCEquipment monitor.



RNC Type

RAN managed object RNC/RNCEquipment/CNode/OMU

Object Class N/A



Severity MAJOR



Remedial Action If the alarm occurs when you are extracting the OMU module, just pro-ceed; otherwise, replace the old module with a new one. For more in-formation on replacement, refer to the procedure on replacing theOMU module in Alcatel-Lucent 9370 Radio Network Controller - Main-tenance Guide (NN-20500-023). If an OMU module is unplugged whilethe RNC is created or destroyed and recreated (rehoming or upgradewith model change), no alarm is generated.




This alarm indicates that an extraction of a module is detected.The State change to disabled notinstalled alarm (OAM_40) appears on the graphical representation of MMS module in RNCEquipment monitor.



RNC Type

RAN managed object RNC/RNCEquipment/CNode/dynamicDATA[OMU/MMS or MMS]

Object Class N/A



Severity MAJOR



Remedial Action If the alarm occurs when extracting the MMS module, just proceed;otherwise, replace the old module with a new one. For more informa-tion on replacement, refer to the procedure on replacing the MMSmodule in Alcatel-Lucent 9370 Radio Network Controller - Mainten-ance Guide (NN-20500-023). If an MMS module is unplugged whilethe RNC is created or destroyed and recreated (rehoming or upgradewith model change), no alarm is generated.




This alarm indicates that an extraction of a module is detected.The State change to disabled notinstalled alarm (OAM_41) appears on the graphical representation of TMU module in RNCEquipment monitor.



RNC Type

RAN managed object RNC/RNCEquipment/CNode/TMU

Object Class N/A



Severity MAJOR



Remedial Action If the alarm occurs when extracting the TMU module, just proceed;otherwise, replace the old module with a new one. For more informa-tion on replacement, refer to the procedure on replacing the TMU mod-ule in Alcatel-Lucent 9370 Radio Network Controller - MaintenanceGuide (NN-20500-023). If an TMU module is unplugged while the RNCis created or destroyed and recreated (rehoming or upgrade with mod-el change), no alarm is generated.




State change on SasAccess with administrativeState set to unlocked, operationalState equal toenabled and availabilityStatus degraded.The State change to enabled degraded alarm (OAM_43)appears on the graphical representation of C-Node module in RNC Equipment monitor.



RNC Type 9370 RNC

RAN managed object RNC/SasAccess

Object Class N/A



Severity CRITICAL

Impact SAS is available, but some of the TCP connections could not be estab-lished. No TCP connections are accessible.


Remedial Action Check network transmission for Iupc link and check SAS server state.




OsiState change on SasAccess with administrativeState set to unlocked, operationalState equal todisabled and availabilityStatus dependency.The State change to disabled dependency alarm(OAM_44) appears on the graphical representation of C-Node module in RNC Equipment monitor.



RNC Type 9370 RNC


Object Class N/A



Severity CRITICAL

Impact SAS is not available.


Remedial Action Check network transmission for Iupc link and check SAS server state.



5.80 RNC_0053_00056 - UNEXPECTED RNC MIBSTATE SET TOUPDATE IN PROGRESS

This alarm is generated when the RNC sends a report build with MIBState set to update in progressinstead of built out of OMC RNC Upgrade job. The Unexpected RNC MIBState set to update inprogress alarm (OAM_53) appears on the graphical representation of C-Node in RNC Equipmentmonitor.

Unexpected RNC MIBState set to update in progress


RNC Type 9370 RNC


Object Class N/A



Severity warning

Impact CNode kept in transient state.

Reason State of the active RNC MIB is "update in progress" although no up-grade procedure is in progress on the CNode.

Remedial Action Cancel the on-going build operation at CNode level by launching a MIBRebuild command. This action forces the CNode to be back in its pre-vious nominal state.

Note that in case of a rebuild action, this alarm will be automaticallyset and cleared. This is a normal behavior, no need to trigger anycancel action.



5.81 RNC_0056_00056 - RNC FAMILY NOT COMPATIBLE WITH RNCARCHITECTURE

The provisioned RNC family is not compatible with the RNC architecture available on OAM database.

RNC family not compatible with RNC architecture


RNC Type 9370 RNC

All BTS

RAN managed object dynamicDATA[BTSEquipment or RNC]

Object Class N/A



Severity MAJOR

Impact Build operation will not be allowed.

Reason The provisioned RNC family is not compatible with the RNC architec-ture available on OAM database.

Remedial Action Import a new RNC provisioning compatible with the RNC architecture.



5.82 RNC_0057_00056 - MIB NUMBER RECEIVED FROM NEDIFFERENT 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


RNC Type 9370 RNC

RAN managed object RNC/RncMIB

Object Class N/A



Severity MAJOR

Impact MIB de-synchronization.

Reason The MIB number received from NE is different from the MIB numberstored in the active view.

Remedial Action



5.83 RNC_0058_00020 - STATE CHANGE TO DISABLED NOTINSTALLED

This alarm happens when either a BTS starts up or a BTS fault occurs with a lost local cell. In thiscase the associated FDDCell OsiState change turns into disabled not installed. This alarm isgenerated when the OMC receives an OsiState change on FDDCell with operationalState equal todisabled and availabilityStatus equal to not installed.

State change to disabled not installed


RNC Type 9370 RNC


Object Class N/A



Severity CRITICAL

Impact

Reason This alarm happens when either a BTS starts up or a BTS fault occurswith a lost local cell. In this case the associated FDDCell OsiStatechange turns into disabled not installed. This alarm is generated whenthe OMC receives an OsiState change on FDDCell with operational-State equal to disabled and availabilityStatus equal to not installed.

Remedial Action



5.84 RNC_0059_00036 - UNEXPECTED RNC MIBSTATE SET TOUPDATE IN PROGRESS

This alarm is generated when the RNC sends a report build with MIBState set to "update in progress"instead of "built" out of OMC RNC Upgrade or Online Build Job.

Unexpected RNC MIBState set to update in progress


RNC Type 9370 RNC


Object Class N/A



Severity warning

Impact CNode kept in transient state.

Reason State of the active RNC MIB is "update in progress" although no up-grade procedure is in progress on the CNode.

Remedial Action Cancel the on-going build operation at CNode level by launching a MIBRebuild command. This action forces the CNode to be back in its pre-vious nominal state.

Note that in case of a rebuild action, this alarm will be automaticallyset and cleared. This is a normal behavior, no need to trigger anycancel action.



5.85 RNC_0070_00056 - CONFIGURATION DE-SYNCHRONIZATIONThis alarm is generated when a configuration de-synchronization occurs between RNC InterfaceNode and OAM database.

Configuration de-synchronization


RNC Type RNC 1500


Object Class N/A



Severity MAJOR

Impact RNC Interface Node CM XML Export is not aligned with current RNCInterface Node current configuration.

Reason This alarm is generated when a configuration de-synchronization oc-curs between RNC Interface Node and OAM database.

Remedial Action Launch manual resynchronization on the RNC Interface Node.



5.86 RNC_0080_00036 - STATE CHANGE TO DISABLED DUE TOMANAGEMENT OPERATION

This alarms happens when the operator locks the CsCoreNetworkAccess administrative state in caseof a management operation.

State change to disabled due to management operation


RNC Type 9370 RNC


Object Class N/A



Severity minor

Impact Loss of capacity on CsCoreNetworkAccess.

Reason This alarms happens when the operator locks the CsCoreNetworkAc-cess administrative state in case of a management operation.

Remedial Action Check the CsCoreNetworkAccess administrative state.




This alarms happens when the operator locks the FDDCell administrative state in case of amanagement operation.



RNC Type 9370 RNC


Object Class N/A



Severity minor

Impact Loss of capacity on FDDCell.

Reason This alarms happens when the operator locks the FDDCell administrat-ive state in case of a management operation.

Remedial Action Check the FDDCell administrative state.




This alarms happens when the operator locks the neighbouring RNC administrative state in case of amanagement operation.



RNC Type 9370 RNC


Object Class N/A



Severity minor

Impact Loss of capacity on neighbouring RNC.

Reason This alarms happens when the operator locks the neighbouring RNCadministrative state in case of a management operation.

Remedial Action Check the neighbouring RNC administrative state.




This alarms happens when the operator locks the PsCoreNetworkAccess administrative state in caseof a management operation.



RNC Type 9370 RNC

RAN managed object RNC/PsCoreNetworkAccess

Object Class N/A



Severity minor

Impact Loss of capacity on PsCoreNetworkAccess.

Reason This alarms happens when the operator locks the PsCoreNetworkAc-cess administrative state in case of a management operation.

Remedial Action Check the PsCoreNetworkAccess administrative state.




This alarms happens when the operator locks the SAS administrative state in case of a managementoperation.



RNC Type 9370 RNC


Object Class N/A



Severity minor

Impact SAS is not available.

Reason This alarms happens when the operator locks the SAS administrativestate in case of a management operation.

Remedial Action Check the SAS administrative state.



5.91 RNC_0085_00036 - STATE CHANGE TO DISABLE FAILEDThis alarm is raised when the RNC sends to WMS a state change to Disable/Failed about the objectControlPort.

State change to Disable Failed


RNC Type 9370 RNC

RAN managed object RNC/NodeB/ControlPort

Object Class N/A



Severity MAJOR

Impact According the ControlPort type (nodeBCP,CCP), the service is nomore available for the FddCell associated to the faulty CCP, or for thewhole NodeB associated to the faulty nodeBCP.

Reason This alarm is raised when the RNC sends to WMS a state change toDisable/Failed about the object ControlPort.

Remedial Action Check the transmission alarms and the NodeB alarms to find the rootcause. When the state is not equal to Disable/Failed, the alarm iscleared.



6 Access Node, Interface Node and POC alarmsThis section describes RNC A-Node, I-Node and POC alarms.

RNC A-Node alarms are applicable to up to the UA 4.2 release; the RNC POC alarms are applicablefrom the UA 5.0 release.



6.1 MSS_0000_00000

RNC Type • POC

• 9370 RNC

Component {component_name}

Severity cleared

Status clear

Detail {component_name} = any Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent A hierarchical clear has been issued. Thisalarm clears all set alarms for componentshierarchically below this component. There isa special case when {component_name} is alogical processor (LP) component. In additionto the components hierarchically below the LP,this alarm clears all set alarms for componentsthat have specified the LP as a related com-ponent in that set alarm.

Remedial Action None



6.2 MSS_0000_00001

RNC Type • POC

• 9370 RNC


Severity cleared

Status clear

Detail A hierarchical clear has been issued. Thisalarm clears all set alarms for componentshierarchically below this component. There isa special case when {component_name} is alogical processor (LP) component. In additionto the components hierarchically below the LP,this alarm clears all set alarms for componentsthat have specified the LP as a related com-ponent in that set alarm.




6.3 MSS_0000_01000

RNC Type • POC

• 9370 RNC


Severity warning

minor

major

critical

indeterminate

cleared

Status set

clear

Detail {component_name} = any Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent that supports the lock and unlock com-mands {severity} = varies with componentWhen the status is set, the component hasgone into a locked state or a shutting downstate. The locked component is no longer per-mitted to provide service. As a result, depend-ent components may be operationally disabledas well. When the status is clear the compon-ent is unlocked. The OSI administrative stateattribute in the alarm specifies the new admin-istrative state for the component.

Remedial Action When the status is set, issue the unlock com-mand to attempt to unlock the component.When the status is clear, no remedial action isrequired.



6.4 MSS_0000_01001

RNC Type • POC

• 9370 RNC


Severity warning

minor

major

critical

indeterminate

cleared

Status set

clear

Detail {component_name} = any Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent that maintains OSI operational state{severity} = varies with the component Thecomponent has changed OSI operationalstate. When the status is set, the operationalstate has changed to disabled. When thestatus is clear, the operational state haschanged to enabled.

Remedial Action When the status is set, the remedial action isdependent on the component. For informationon individual components, see Alcatel-LucentMultiservice Switch 7400/15000/20000 Com-ponents Reference (NN10600-060). For in-formation on resolving problems, see Alcatel-Lucent Multiservice Switch 7400/15000/20000Troubleshooting (NN10600-520). When thestatus is clear, no remedial action is required.



6.5 MSS_0000_03000

RNC Type • POC

• 9370 RNC


Severity warning

minor

major

critical

indeterminate

cleared

Status set

clear

Detail {component_name} = any Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent {severity} = varies with component Whenthe status is set, the component has exceededa threshold for heap or message blocks. Whenthe status is clear, the component hasdropped below a threshold for heap or mes-sage blocks. The impact on other componentscan vary.

Remedial Action When the component name is logical pro-cessor (LP), contact Alcatel-Lucent global sup-port. If the component name is not LP then theremedial action is dependent upon the com-ponent. For information on individual compon-ents, see Alcatel-Lucent Multiservice Switch7400/15000/20000 Components Reference(NN10600-060). For information on resolvingproblems, see Alcatel-Lucent MultiserviceSwitch 7400/15000/20000 Troubleshooting(NN10600-520).



6.6 MSS_0000_03001

RNC Type • POC

• 9370 RNC


Severity warning

minor

major

critical

indeterminate

cleared

Status set

clear

Detail {component_name} = any Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent {severity} = varies with component Whenthe status is set, the component has exceededa threshold for heap/memory availability.When the status is clear, the component hasdropped below a threshold for heap/ memoryavailability. The impact on other componentscan vary.

Remedial Action When the component name is logical pro-cessor (LP), contact Alcatel-Lucent global sup-port. If the component name is not LP then theremedial action is dependent upon the com-ponent. See Alcatel-Lucent MultiserviceSwitch 7400/15000/20000 Components Refer-ence (NN10600-060), for more information onindividual components.



6.7 MSS_0000_03002

RNC Type • POC

• 9370 RNC


Severity warning

minor

major

critical

indeterminate

cleared

Status set

clear

Detail {component_name} = any Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent {severity} = varies with component Whenthe status is set, the component has exceededa threshold for message block or hardware re-source availability. When the status is clear,the component has dropped below a thresholdfor message block or hardware resource avail-ability. The impact on individual componentscan vary. Some components may issue thealarm with set status only.

Remedial Action When the component name is logical pro-cessor (LP), contact Alcatel-Lucent global sup-port. If the component name is not LP then theremedial action is dependent upon the com-ponent. See Alcatel-Lucent MultiserviceSwitch 7400/15000/20000 Components Refer-ence (NN10600-060), for more information onindividual components.



6.8 MSS_0000_09000

RNC Type • POC

• 9370 RNC


Severity indeterminate

Status message

Detail {component_name} = any Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent An internal software error has been detec-ted by a component. This alarm index is re-used by many subsystems upon detection ofvarious types and severities of internal errors.Thus, one instance of an alarm with this indexmay be totally unrelated to another instance.In some cases, it is possible that the alarmcomment text can give a hint about what hashappened. Because the circumstances whichcaused this event are unexpected, the impactcan vary on a case-by-case basis from no im-pact at all to possibly a severe impact. In thelatter case, it may be accompanied by otheralarms. The problem may or may not be repro-ducible. If the circumstances are known, thiscan greatly help in the resolution of the prob-lem.

Remedial Action Contact your local Alcatel-Lucent technicalsupport group.



6.9 MSS_0000_09001

RNC Type • POC

• 9370 RNC

Component {component_type}


Status message

Detail {component_type} = any Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent An internal software error (indicating a badstate) has been detected by a component. Theimpact on other components can vary.




6.10 MSS_0000_09002

RNC Type • POC

• 9370 RNC



Status message

Detail {component_type} = any Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent An internal software error (indicating a badfunction number) has been detected by a com-ponent. The impact on other components canvary.




6.11 MSS_0000_09003

RNC Type • POC

• 9370 RNC



Status message

Detail {component_type} = any Alcatel-LucentMultiservice Switch component An internalsoftware error (indicating a bad messagecode) has been detected by a component. Theimpact on other components can vary.




6.12 MSS_0999_00001Note: This is an MDM alarm. For information on Multiservice Data Manager-generated alarms,see Nortel Multiservice Data Manager Alarms Reference (241-6001-501).

RNC Type • POC

• 9370 RNC

Component EM/{node name}

Severity major

cleared

Status set

clear

Detail {node name} = The provisioned node name ofthe Multiservice Switch (the nodeName attrib-ute of the ModuleData component). Whenstatus is set, the Alcatel-Lucent MultiserviceData Manager (MDM) workstation has lost itsVC connection to the controlled device whosename and type is displayed by the alarm. Thecause of the failure is either problems in thecommunications links connecting MultiserviceData Manager and the controlled device, ordevice failure on the remote end. When statusis clear, the connectivity has been restored.This alarm is generated completely withinMultiservice Data Manager It is never spooledto a Multiservice Switch disk and never ap-pears on the text interface device.

Remedial Action Check the communication link connecting thenode on which Multiservice Data Managerresides and the controlled device. Also ensurethat the controlled device has not failed. If youcannot detect the problem in the communica-tion link, or physical link, or the remote-enddevice, and the problem persists, contact yourAlcatel-Lucent representative.



6.13 MSS_0999_00012Note: This is an MDM alarm. For information on Multiservice Data Manager-generated alarms,see Nortel Multiservice Data Manager Alarms Reference (241-6001-501).

RNC Type • POC

• 9370 RNC

Component EM/{component id}

Severity major

cleared

Status set

clear

Detail {component id} is the name of any Alcatel-Lu-cent Multiservice Switch component generat-ing SCNs The state of the component hasbeen changed due to a state change notifica-tion (SCN) received from the network. Whenthe status of the alarm is a set, it means thatthe SCN indicated that the component isdown, and there are no corresponding activealarms (generated by the switch) on that com-ponent to indicate that it is down. ThereforeMultiservice Data Manager created a proxyalarm to replace the missing alarm. Multiser-vice Data Manager will mark the componentOut of service. When the status of the alarm isa clear, it means that the SCN indicated thatthe component is up, and there were activealarms on that component to indicate that it isdown. Therefore Multiservice Data Managergenerates a proxy alarm to replace the miss-ing clear. Multiservice Data Manager will markthe component In service. The comment textof this alarm contains information on the SCNthat was received that triggered MultiserviceData Manager to create the proxy alarm. Thisalarm is generated completely within Multiser-vice Data Manager. It is never spooled to a



Multiservice Switch disk and never appears onthe text interface device.

Remedial Action This alarm is issued either because the SCNwas received before the alarm issued by theswitch, which would put the component in theproper state (and the proxy alarm will becleared when the real alarm is received) or be-cause the alarm issued by the switch has beenlost. Treat proxy alarms as you would treatregular alarms and use them in debugging net-work problems.



6.14 MSS_7000_00001

RNC Type • POC

• 9370 RNC

Component Prov

Severity critical

Status message

Detail Initial loading of the boot file failed because itis missing. Initial loading and initial activationhave been aborted. The control processor(CP) will still come up and allow operator login,however it has incomplete configuration dataand configured software/services have notbeen started. The /system/commit file containsthe name of the boot file. This boot file mustbe present in the /provisioning directory. If allfiles are present, then either the individual filesor the complete file system is corrupt.

Remedial Action Run disk diagnostic tests in order to provideadditional problem information. On a dual-CPsystem, if a spare CP is present, replace thedefective CP, raise a SR and return the defect-ive CP to Alcatel-Lucent. If the alarm is issuedon a single-CP system, contact your local Alc-atel-Lucent technical support group.



6.15 MSS_7000_00002

RNC Type • POC

• 9370 RNC

Component Prov

Severity minor

Status message

Detail A command from the boot file failed during ini-tial loading. Initial loading and initial activationare not aborted, they continue to completion.

Remedial Action After initial loading and initial activation com-pletes, enter provisioning mode and run se-mantic checks on the target component of thefailed command. Make required changes, ac-tivate, and commit changes.



6.16 MSS_7000_00003

RNC Type • POC

• 9370 RNC

Component Prov

Severity critical

Status message

Detail Initial loading of the boot file failed because itis corrupt. Initial loading and initial activationhave been aborted. The control processor(CP) will still come up and allow operator login,however it has incomplete configuration dataand configured software/services have notbeen started. The /system/commit file containsthe name of the boot file. This boot file mustbe present in the /provisioning directory. Ifhowever all files are present, then it is likelythat the individual files or the complete file sys-tem are corrupt.

Remedial Action Run disk diagnostic tests in order to provideadditional problem information. On a dual-CPsystem, if a spare CP is present, replace thedefective CP, raise an SR and return the de-fective one to Alcatel-Lucent. If the alarm is is-sued on a single-CP system, contact your loc-al Alcatel-Lucent technical support group.



6.17 MSS_7000_00004

RNC Type • POC

• 9370 RNC

Component Prov

Severity critical

Status message

Detail A file system error has occurred while loadinga provisioning file during initial loading. If thisoccurs during initial booting, then initial loadingand initial activation are aborted. The controlprocessor (CP) will still come up and allow op-erator login, however it has incomplete config-uration data and configured software/serviceshave not been started.

Remedial Action Run disk diagnostic tests in order to provideadditional problem information. On a dual-CPsystem, if a spare CP is present, replace thedefective CP, raise an SR and return the de-fective one to Alcatel-Lucent. If the alarm is is-sued on a single-CP system, contact your loc-al Alcatel-Lucent technical support group.



6.18 MSS_7000_00005

RNC Type • POC

• 9370 RNC

Component Prov

Severity warning

Status message

Detail A file system error occurred when attemptingto close the provisioning after loading. This willnot affect operation, unless it is occurring re-peatedly, each time a load or save commandis performed.




6.19 MSS_7000_00006

RNC Type • POC

• 9370 RNC

Component Prov

Severity critical

Status message

Detail The control processor (CP) is crashing be-cause there is an internal software corruption.Usually there are related alarms (possibly soft-ware alarms) prior to this alarm being gener-ated, which may indicate how the data wascorrupted.

Remedial Action Contact your local Alcatel-Lucent technicalsupport group. If the CP repeatedly crashesdue to this problem, replace the CP and returnthe defective CP to Alcatel-Lucent for post-mortem.



6.20 MSS_7000_00007

RNC Type • POC

• 9370 RNC

Component Prov

Severity warning

minor

major

critical

cleared

Status set

clear

Detail {severity} = warning, minor, major, critical, orcleared. Note that the severity increases every5 minutes until a "Confirm Prov" commandstarts. When an activation is completed, the7000 0007 SET alarm is generated every 5minutes, warning the operator that if a "Con-firm Prov" command is not issued to confirmthe activation, rollback will occur. With theautoConfirm attribute of the Prov componentturned ON, the activation does not need to beconfirmed. Hence, the comment text of theSET alarm is changed to: "Activation com-plete. An implicit confirmation activity will takeplace." This will be generated only once, im-mediately after the activation is completed.

Remedial Action This alarm informs the operator that activationis completed. With autoConfirm attribute of theProv component OFF, the default behavior isexpected of the operator (that is, a "ConfirmProv" command is required). With the auto-Confirm attribute turned ON, the alarm com-ment text is modified. No operator action is re-quired.



6.21 MSS_7000_00008

RNC Type • POC

• 9370 RNC

Component Prov

Severity major

Status message

Detail This alarm is issued when initial activation de-tects that the software has been patched. Thisalarm is not to be expected and will only occurwhen the software has been patched througha procedure other than the Multiservice Switchpatching mechanism. A "migration" style ofloading takes place that is much slower thanusual and as a result, the service outage timesare much greater.

Remedial Action Simply re-check, re-save and re-commit thecurrent view as required.



6.22 MSS_7000_00009

RNC Type • POC

• 9370 RNC

Component Prov

Severity major

Status message

Detail This alarm is issued when initial activation de-tects that the provisioning data is missing thecommit format. The resulting activation ismuch slower than usual and as a result, theservice outage times are much greater. Thisscenario typically occurs when migrating to anew software version.

Remedial Action Re-check, re-save, and re-commit the currentview as required.



6.23 MSS_7000_00010

RNC Type • POC

• 9370 RNC

Component {name}

Severity minor

cleared

Status set

clear

Detail {name} = any provisionable Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent This alarm is issued when the reportingcomponent cannot be updated with new provi-sioning data. This implies that the serviceprovided by the reporting component will eithernot be created or not be modified to behavewith the characteristics described in the newprovisioning data.

Remedial Action Check the provisioning of the software for thespecified component. The logicalProcessor-Type attribute of the Lp component named inthe alarm should be provisioned to the properLpt component. This Lpt component shouldhave any necessary features provisioned inthe featureList attribute. Correct any provision-ing errors and attempt re-activation. Other-wise, contact your local Alcatel-Lucent technic-al support group.



6.24 MSS_7000_00011

RNC Type • POC

• 9370 RNC

Component {name}

Severity warning

Status message

Detail {name} = any provisionable Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent This alarm is issued when an application isslow in responding to provisioning data. Itshould not be considered failed, until alarm{$elemparanum7000 0010 is issued.

Remedial Action No action is required, this is only a warning.



6.25 MSS_7000_00012

RNC Type • POC

• 9370 RNC

Component Prov

Severity warning

Status message

Detail This alarm is issued when a network manage-ment interface (NMIF) session is forced offfrom the provisioning mode by the system ad-ministrator or by the provisioning operator.

Remedial Action Contact your Alcatel-Lucent technical supportgroup.



6.26 MSS_7000_00013

RNC Type • POC

• 9370 RNC

Component Prov

Severity minor

Status message

Detail This alarm is issued during initial loading whena provisioned component contains a semantic-ally incorrect hardware link. The data of thealarm will contain the component in error. Thiscomponent will not be created on the properlogical processor.

Remedial Action After initial loading and initial activation com-pletes, enter provisioning data and run se-mantic checks on the specified component.Make the required changes, activate, andcommit the changes.



6.27 MSS_7000_00015

RNC Type • POC

• 9370 RNC

Component Prov

Severity warning

Status message

Detail This alarm is issued during initial loading whena temporary file created to save the currentview data cannot be removed from the disk.




6.28 MSS_7000_00016

RNC Type • POC

• 9370 RNC

Component Prov

Severity minor

Status message

Detail This alarm is issued when a logical processorfirst becomes active and the fast, boot-modestyle of activation fails. The system will resetthe logical processor, and use an alternativeactivation style.




6.29 MSS_7000_00029

RNC Type • POC

• 9370 RNC

Component Prov

Severity minor

Status message

Detail This alarm is issued when an error is en-countered while determining the Provisioning-System component"™s nextFileSequen-ceNumber attribute. When this alarm is issued,the nextFileSequenceNumber attribute is setto 1.

Remedial Action Run disk diagnostic tests in order to provideadditional problem information. Contact yourlocal Alcatel-Lucent technical support group.



6.30 MSS_7000_00030

RNC Type • POC

• 9370 RNC

Component Prov

Severity minor

Status message

Detail The provisioning view file has been corruptedor contains inconsistent data. This could bedue to a file system error or manual modifica-tion of the data. The component informationwill be built as part of the slow boot sequence.

Remedial Action After the next check prov, do a save prov togenerate a new provisioning file. If the problempersists, contact your Alcatel-Lucent technicalsupport group.



6.31 MSS_7000_00031

RNC Type • POC

• 9370 RNC

Component Prov

Severity warning

Status message

Detail The provisioning view file has been corruptedor contains inconsistent data. This could bedue to a file system error or manual modifica-tion of the data. The component informationwill be built as part of the slow boot sequence.

Remedial Action After the next check prov, do a save prov togenerate a new provisioning file. If the problempersists, contact your Alcatel-Lucent technicalsupport group.



6.32 MSS_7000_00032

RNC Type • POC

• 9370 RNC

Component Prov

Severity warning

Status message

Detail This alarm is issued on an initial activationwhen the fast, boot-mode style of activationcannot be used due to a problem saving com-mit-format files. Activation will proceed, butwith a slower style of activation.

Remedial Action Check for alarms indicating a problem withsaving of commit-format files or with the disk. Ifthe problem persists, contact your Alcatel-Lu-cent technical support group.



6.33 MSS_7000_00033

RNC Type • POC

• 9370 RNC

Component Prov Migration

Severity warning

critical

cleared

Status set

clear

Detail If the status is set and the severity is critical, asoftware migration activation has paused. Asoftware migration activation pauses beforeMigration-Switchover if any of the following oc-curs: a software alarm is issued on the migra-tion shelfan engineering alarm is issued on themigration shelfan application cannot achieveits expected Migration-Switchover behavior Aclear is issued after the operator enters the ap-propriate commands to either continue withthe software migration activation or to stop thesoftware migration activation. If the status isset and the severity is warning, a software mi-gration activation has started. A clear is issuedafter the software migration activation com-pletes either successfully or unsuccessfully.

Remedial Action If the status is set and the severity is warningthen no remedial action is required. Be awarethat a software migration activation has begunon this node. If the status is set and the sever-ity is critical, review the set of Migration VisibleAlarms raised during the software migrationactivation and consult the new software re-lease documentation and/or Alcatel-Lucenttechnical support to make a decision whetherto continue with the software migration activa-



tion or to perform a hitless recovery. To contin-ue with the software migration activation usethe continue provisioningSystem commandfrom within provisioning mode. To stop thesoftware migration activation through a hitlessrecovery use the stop provisioningSystemcommand from within provisioning mode.



6.34 MSS_7000_00034

RNC Type • POC

• 9370 RNC

Component Prov

Severity warning

Status message

Detail This alarm is issued when a fault condition oc-curs on the migration shelf. Text from the ori-ginal alarm generated for the fault condition onthe migration shelf is embedded within thisalarm. Typically, the fault conditions represent:a software alarman engineering alarma condi-tion which indicates that an application can notachieve its expected Migration-Switchover be-havior.

Remedial Action Refer to the alarm index within this alarm textin the new software release documentation formore information. If deemed appropriate, thesoftware migration activation can be stoppedby issuing the stop provisioningSystem com-mand while in provisioning mode.



6.35 MSS_7000_00035

RNC Type • POC

• 9370 RNC

Component {name}


Status message

Detail {name} = any provisionable Alcatel-LucentMultiservice Switch or Passport 6400 compon-ent. This alarm is raised against any compon-ent that fails to indicate whether it is ready fora Migration-Switchover. This alarm will pausea hitless software migration. This messagealarm is ONLY generated on the migrationshelf; it is reformatted and regenerated againstthe Prov Migration component.

Remedial Action The component {name} may not be ready for amigration-switchover. If deemed appropriate,the software migration activation can bestopped by issuing the stop provisioningSys-tem command while in provisioning mode. Ifthe problem persists, contact your Alcatel-Lu-cent technical support group.



6.36 MSS_7000_00036

RNC Type • POC

• 9370 RNC

Component Prov

Severity warning

minor

major

cleared

Status set

clear

Detail This alarm is raised when attribute Prov cur-rentJournal reaches 75%, 85%, and 95% of itsmaximum at warning, minor, and major sever-ity, respectively. If this attribute becomesgreater than or equal to attribute ProvmaxNumberJournalFiles, then journal log sav-ing is disabled. A clear is issued when theview is committed. This alarm is also cleared ifjournal log saving is disabled via provisioning,or if the node resets to the committed view.

Remedial Action There is no immediate impact to the node. Thenetwork operator should recommit, whichcleans up all existing journal log files. If neitherthe disaster recovery nor CP equipment pro-tection feature are wanted, the operator canalso clear this alarm by disabling journal logsaving by setting attribute Prov maxNumber-JournalFiles to none.



6.37 MSS_7000_00037

RNC Type • POC

• 9370 RNC

Component Prov

Severity critical

cleared

Status set

clear

Detail This alarm indicates that the saving of journallogs is disabled. This can be caused by the fol-lowing reasons: journaling has been enabledby provisioning and an initial commit is re-quiredjournal log save failed because the FileSystem is lockedjournal log save failed due toFile System errorthe number of journal logshas exceeded the maximuma reload activationhas occurred and a commit has not yet beendone If cpEquipmentProtection is hot, thisalarm indicates that the standby CP has lostsynchronization to the active CP. One or moreFPs and possibly the standby CP will be resetby the system if a CP switchover occurs. Thisalarm also indicates an impact to the disasterrecovery feature, since these journal log filesare required to restore the node"™s configura-tion in the case of a complete node reset orfailure. A clear is issued when the new view iscommitted. This alarm is also cleared if journallog saving is disabled by provisioning or if thenode resets to the committed view.

Remedial Action The attribute Prov journalDisabledReason canbe queried. If this attribute has the value offileSystemError, the operator should ensurethe file system is not locked. If it is locked, thefile system should be unlocked. Otherwise, the



operator should look for file system or diskalarms to determine the root cause of the fail-ure. Once the root cause is determined andfixed, the operator should recommit to clearthis alarm. For any other value of journalDis-abledReason, the operator should recommitthe current provisioning view and this will clearthe alarm. If neither the disaster recovery norCP equipment feature are wanted, the operat-or can also clear this alarm by disabling journ-al log saving by setting attribute ProvmaxNumberJournalFiles to none.



6.38 MSS_7000_00038

RNC Type • POC

• 9370 RNC

Component Prov

Severity warning

cleared

Status set

clear

Detail If the status is set, a node reset has occurredand the user can issue the restore provision-ingSystem command to restore the previouslyjournaled current view. A clear is issued whenthe restore prov command is issued, the cur-rent view is recommitted, or the activate provcommand is issued.

Remedial Action If you want to restore the previously journaledcurrent view, issue the restore prov command.This alarm merely indicates the current viewcan be restored. There is no impact if thisalarm is outstanding. The first commit or activ-ation following the node reset also clears thisalarm.



6.39 MSS_7000_00039

RNC Type • POC

• 9370 RNC

Component Prov

Severity warning

Status message

Detail This alarm indicates that a commit commandhas just successfully completed. This alarm isonly issued if the journaling is enabled.




6.40 MSS_7000_00040

RNC Type • POC

• 9370 RNC

Component Prov

Severity major

cleared

Status set

clear

Detail If the status is set, a journal log file loading er-ror has occurred and the standby CP is nolonger synchronized with the active CP. Thiscan occur in the following situations: File Sys-tem is lockedFile System errorlog file is corrup-ted A clear is issued when a commit prov is is-sued or when the journal log file that failed toload is successfully loaded on a subsequentattempt. This alarm is also cleared if the ShelfcpEquipmentProtection attribute is set to cold.

Remedial Action The operator should ensure that the file sys-tem is not locked. If it is locked, the file systemshould be unlocked. Otherwise, the operatorshould look for file system or disk alarms todetermine the root cause of the failure. Afterthe root cause is determined and fixed, the op-erator should perform a commit prov to clearthe alarm and restore standby CP synchroniz-ation. If CP equipment protection is notneeded, the operator can clear this alarm bysetting the Shelf cpEquipmentProtection attrib-ute to cold.



6.41 MSS_7000_00041

RNC Type • POC

• 9370 RNC

Component Provisioning Patch

Severity warning

critical

cleared

Status set

clear

Detail This alarm indicates a state change in theProv Patch component. If the status is set andthe severity is warning, Hitless SoftwarePatching has started. A clear is issued afterHitless Software Patching completes eithersuccessfully or unsuccessfully. If the status isset and the severity is critical, Hitless SoftwarePatching has paused. A clear is issued afterthe operator enters the appropriate commandsto either continue with the Hitless SoftwarePatching or to stop the Hitless Software Patch-ing.

Remedial Action If the status is set and the severity is warningthen no remedial action is required. Be awarethat Hitless Software Patching has begun onthis node. The alarm is generated with criticalseverity when Hitless Software Patching ispaused. When you see this alarm, make a de-cision on whether you want the Hitless Soft-ware Patching to continue or abort. To contin-ue Hitless Software Patching, issue the "contin-ue prov" command. To abort Hitless SoftwarePatching, issue "stop prov" command.



6.42 MSS_7000_00042

RNC Type • POC

• 9370 RNC

Component Prov CriticalAttributeActivation

Severity warning

critical

cleared

Status set

clear

Detail If the status is set and the severity is warning,then this alarm indicates that a critical attributeactivation has begun. If the status is set andthe severity is critical, the critical attribute ac-tivation has paused. A critical attribute activa-tion will pause if any of the following conditionsoccur: - a software alarm is generated on anupgrading card - an engineering alarm is gen-erated on an upgrading card - an applicationon an upgrading card cannot achieve its ex-pected behavior This alarm is cleared whenthe critical attribute activation terminates.

Remedial Action If the status is set and the severity is warningthen no remedial action is required. Be awarethat a hitless activation has begun on thisswitch. If the status is set and the severity iscritical, review the set of alarms relevant to theactivation and consult the applicable softwarerelease documentation and/or Alcatel-Lucenttechnical support to make a decision whetherto continue or stop the hitless activation. For ahitless software migration, the relevant alarmsare the Migration Visible Alarms raised duringthis activation. For a critical attribute activation,the relevant alarms are the alarms raised onthe cards that are being or have been activ-



ated as part of this activation. To continue withthe activation, use the continue provisioning-System command from within provisioningmode. To stop the activation through a roll-back, use the stop provisioningSystem com-mand from within provisioning mode.



6.43 MSS_7000_00043

RNC Type • POC

• 9370 RNC

Component Prov ActivationMode

Severity minor

cleared

Status set

clear

Detail If the status is set and the severity is minor,then this alarm indicates that ActivationModehitlessActivation is set to disabled. This alarmis cleared when the ActivationMode compon-ent is deleted or when the ActivationMode hit-lessActivation is set to enabled.

Remedial Action If the status is set and the severity is minor,either the ActivationMode component must bedeleted or the ActivationMode hitlessActivationmust be set to enabled.



6.44 MSS_7000_00044

RNC Type • POC

• 9370 RNC

Component Shelf Card/{x} Lp/{y}

Severity critical

cleared

Status set

clear

Detail {x}= the card number of the standby CP {y}=the logical processor number of the CP Thereare two kinds of problems will lead to thisalarm: 1. When the CP is booting up with thecommit view. The alarm will be generated ifthe commit file is inaccessible, nonexistent, orwrong. 2. When the standby CP comes tohandle the synchronization information re-ceived from the active CP. The alarm will begenerated if the commit file is inaccessible ornonexistent, or synchronization request timerexpire and the maximum number of retrieshave been reached. 3. When the commit provcommand is issued and the standby CP is un-able to load the commit view due to file corrup-tion or file system in bad state. If it occurs, theprovisioned data on standby CP will not be insync with the active CP data. The standby CPcan not work as standby and a CP switchovercan result in shelf wide outage.

Remedial Action Operator can try and save the current viewagain and then perform a commit to see if thisresolves the issue. If this fails, contact Alcatel-Lucent technical support group.



6.45 MSS_7002_00000

RNC Type • POC

• 9370 RNC

Component Shelf Bus/{instance}

Severity warning

cleared

Status set

clear

Detail {instance} = X or Y If the status is set, the mainsource of clock signals for the bus is defective.The reason is that one or more bus taps onthe bus are unable to receive clock signalsfrom the active control processor (CP). If thestatus is clear, the alarm indicates that themain source of clock signals for the bus is nolonger defective.

Remedial Action Follow the standard procedure for testing thebus and remove or replace the defectiveunit(s). See Alcatel-Lucent Multiservice Switch7400/15000/20000 Troubleshooting(NN10600-520) for details on testing the bus.



6.46 MSS_7002_00001

RNC Type • POC

• 9370 RNC

Component Shelf Bus/{instance}

Severity warning

cleared

Status set

clear

Detail {instance} = X or Y If the status is set, thestandby source of clock signals for the bus isdefective. The reason is that one or more bustaps on the bus are unable to receive clocksignals from the card at the opposite end ofthe module from the active control processor(CP). If the status is clear, the standby sourceof clock signals for the bus is no longer defect-ive.

Remedial Action Ensure that the card at the opposite end of themodule from the active CP is present and op-erational. If the alarm persists follow the stand-ard procedure for testing the bus and removeor replace the defective unit(s). See Alcatel-Lucent Multiservice Switch 7400/15000/20000Troubleshooting (NN10600-520) for details ontesting the bus.



6.47 MSS_7002_00002

RNC Type • POC

• 9370 RNC

Component Shelf FabricCard/{instance}

Severity major

cleared

Status set

clear

Detail {instance} = X or Y This alarm is issued onfabric-based shelves when the fabric card"™ssecondary control bus (SCB) is no longer ableto provide service. This can occur either be-cause the SCB is not receiving a clock signalor because at least one operational card can-not access the SCB.The control processor(CP) gets its alarms from the fabrics over thebus. When the status is clear, the fabriccard"™s SCB is no longer defective.

Remedial Action When the status is set, examine the operation-al attributes related to the secondary controlbus of the FabricCard component to determinethe cause of the alarm. If the attributes do notsatisfactorily explain the cause of the alarm,see Alcatel-Lucent Multiservice Switch7400/15000/20000 Troubleshooting(NN10600-520) for information ontroubleshooting control processor (CP) cardsand the fabric card.



6.48 MSS_7002_00003

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status message

Detail {instance} = X or Y This alarm is issued onfabric-based shelves when the FabricCardcomponent"™s temperature has increased in-side the shelf assembly to above the thresholdoperating temperature of 55 degrees Celsius.If the temperature continues to rise, the Fab-ricCard component will be removed from ser-vice by the system to avoid damage. When thefabric card temperature has returned to an ac-ceptable operating temperature (at least 2 de-grees lower than the threshold temperature),the status is clear.

Remedial Action When the status is set, ensure that the coolingunit is powered and properly inserted beforereplacing it. Ensure that the ambient temperat-ure in the room is not interfering with the sys-tem"™s ability to cool itself. If the problem per-sists, follow the standard procedure in NTPAlcatel-Lucent Multiservice Switch7400/15000/20000 Troubleshooting(NN10600-520) to test the fabric card, and re-place the defective cooling unit part or the fab-ric.



6.49 MSS_7002_00004

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {instance} = X or Y This alarm is issued onfabric-based shelves when the FabricCardcomponent"™s temperature has increased 3degrees Celsius since initial detection of fanfailure (refer to alarm {$elemparanum70120051). Failure to halt a continuing rise in tem-perature can cause a complete shelf outage.When the status is clear, the FabricCard com-ponent"™s temperature has returned to whatwas measured when the initial fan failure oc-curs.

Remedial Action When the status is set, replace the failed fanas soon as possible using the task flow to re-place cooling unit parts in Alcatel-LucentMultiservice Switch 15000/20000 Installation,Maintenance, and Upgrade - Hardware(NN10600-130) (any version since PCR 4.1).Also ensure that the ambient temperature inthe room is not interfering with the system'sability to cool itself. The fans run at high speedto briefly compensate for a fan failure or hightemperature threshold, but are not designed torun continuously at high speed for more thantwo days.



6.50 MSS_7002_00005

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = X or Y This alarm is issued onfabric-based shelves when two fabric cardsare running different versions of firmware. Al-though this condition does not cause opera-tional problems, Alcatel-Lucent Networks re-commends that you always run the same ver-sion of firmware on each fabric card, exceptduring initial testing purposes. When the statusis clear, both fabric cards are running thesame version of firmware, or the other fabriccard has been removed.

Remedial Action When the status is set, install the software ver-sion indicated by the recommendedVersion-ToInstall attribute of the FabricCard compon-ent.



6.51 MSS_7002_00006

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = X or Y This alarm is issued onfabric-based shelves when the install com-mand is interrupted by a CP switchover or oth-er disruptive event, causing fabric card loadingto be aborted. When the status is clear, thefirmware has been successfully loaded into thewriteable bank of the fabric card.

Remedial Action When the status is set, re-install the fabriccard firmware.



6.52 MSS_7002_00007

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = X or Y This alarm is issued onfabric-based shelves when a fabric card is run-ning firmware that is older than the latest avail-able version. When the status is clear, the fab-ric card is running the latest available firmwareversion.

Remedial Action When the status is set, install the software ver-sion indicated by the recommendedVersion-ToInstall attribute of the FabricCard compon-ent.



6.53 MSS_7002_00008

RNC Type • POC

• 9370 RNC

Component Shelf Card/{instance} FabricPort/{instance2}

Severity warning

Status message

Detail {instance} = X or Y {instance2} = 0 - 15 Whenthe status is set, the fabric port has changedOSI operational state to disabled and is not inservice. When the status is clear, the fabricport has changed OSI operational state to en-abled.

Remedial Action No operator action is necessary if the alarmclears within 15 minutes. If the auto-recoverymechanism has failed, follow the standard pro-cedure for testing the fabric card, or remove orreplace the defective unit(s). See Alcatel-Lu-cent Multiservice Switch 7400/15000/20000Troubleshooting (NN10600-520) and Alcatel-Lucent Multiservice Switch 15000/20000 In-stallation, Maintenance, and Upgrade - Hard-ware (NN10600-130) for information on testingand replacing the shelf card or fabric card.When the status is clear, no remedial action isrequired.



6.54 MSS_7002_00009

RNC Type • POC

• 9370 RNC

Component Shelf FabricCard/{instance} CardPort/{instance2}

Severity warning

cleared

Status set

clear

Detail {instance} = X or Y {instance2} = 0 - 15 Whenthe status is set, the card port has changedOSI operational state to disabled and is not inservice. When the status is clear, the card porthas changed OSI operational state to enabled.

Remedial Action A fabric card test can correct this failure. SeeAlcatel-Lucent Multiservice Switch7400/15000/20000 Troubleshooting(NN10600-520) for information on testing thefabric card.



6.55 MSS_7002_00010

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = X or Y The fabric auto-recoveryfailed due to one of the following reasons: Thefabric self test failed.None of the fabric portspassed the self test.

Remedial Action System action: None Operator action: Lock thefabric card, run the fabric card test, and unlockthe fabric card. If either the fabric card test orunlock fails, contact your system administrator.



6.56 MSS_7002_00012

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = X or Y One or more fabric portsfailed the self test and remained at disabledstate after the fabric unlock.

Remedial Action System action: The FabricPort auto-recoverywill recover the FabricPorts in the failed list.Operator action: None



6.57 MSS_7002_00013

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = X or Y The fabric unlock faileddue to one of the following reasons: The fabricself test failed.None of the fabric ports passedthe self test.

Remedial Action System action: None Operator action: Run thefabric card test. If the fabric card test fails, con-tact your system administrator.



6.58 MSS_7002_00014

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = X or Y One or more fabric portsfailed the self test and remained at disabledstate after the fabric auto-recovery.

Remedial Action System action: The FabricPort auto-recoverywill recover the FabricPorts in the failed list.Operator action: None



6.59 MSS_7002_01000

RNC Type • POC

• 9370 RNC

Component Shelf Card/{instance}

Severity critical

Status message

Detail {instance} = 0 - 15 This alarm indicates thatthe card is not communicating properly overthe backplane buses.

Remedial Action The active control processor (CP) attempts tocorrect the problem by re-initializing the card.If the alarm is repeated, replace the card.



6.60 MSS_7003_00001

RNC Type • POC

• 9370 RNC

Component Collector/{type} Agent/{cardnumber}

Severity major

cleared

Status set

clear

Detail {type} = accounting, alarm, log, scn, debug,trap, stats, rtStats {cardnumber} = the card onwhich the Agent resides If the status is set, adata collection system (DCS) Agent"™s queuehas reached a 75% full threshold. If the queuebecomes full then subsequent records will bediscarded. There are three possible reasonsfor this to occur. First, if there are no re-questors for this particular DCS data type thenthe records will be held in the Agent queues.Second, the provisioned queue size may beinsufficient for the amount of DCS data traffic.Thirdly, a requestor of this particular DCS datatype could be slowing or blocking the flow ofDCS records. For example, if spooling is provi-sioned to on, and the spooler is the only re-questor of data then if the spooler is locked ornot spooling because of a recoverable condi-tion detected by the file system (for example,disk full), data flow will be blocked and theagent queues will fill up. A clear is issuedwhen the queue size drops below 50% full andat least 5 minutes has elapsed since the setwas issued. This delay provides a throttlingmechanism so that bursts of records for relat-ively small queue sizes do not cause too manyalarms within a short time. The clear will indic-ate how many records were discarded (if any)



in the event that data arrived after the queuebecame 100% full.

Remedial Action If you do not wish to monitor or collect this par-ticular type of DCS data, then you may want toprovision the queue size to be zero for thisdata type. If this is done, then all records ofthis type will be discarded. Verify that thequeue size is provisioned to an adequate sizefor the expected amount of traffic. Verify thatthere are no requestors of this DCS data typeholding up the flow of records. For example, ifspooling is provisioned to on, and the spooleris locked, then unlock it. If the spooler is notspooling because of a recoverable conditiondetected by the file system, then clear the filesystem problem. For information on resolvingsuch problems, see Alcatel-Lucent Multiser-vice Switch 7400/15000/20000 Troubleshoot-ing (NN10600-520). When the status is clear,no action is required.



6.61 MSS_7003_00002

RNC Type • POC

• 9370 RNC

Component Collector/{type} Spooler

Severity major

cleared

Status set

clear

Detail {type} = accounting, alarm, log, scn, debug,stats, appl If the status is set, a DCS Spoolerhas stopped spooling records to the shadowedfile system. Typically, the reason is due to arecoverable condition detected by the file sys-tem. The file system will have issued its ownalarm(s) indicating the root cause. This DCSalarm is to indicate the effect of the file systembeing unavailable. The condition will likely af-fect other users of the file system as well. Anexample of a recoverable condition is disk full.The exact nature of the error will be displayedin the comment data field of the alarm. Thisalarm can also appear under certain abnormalconditions detected by the Spooler, usually ac-companied by other alarms, likely indicatingsome unexpected interaction with the file sys-tem. An example of such a condition is onewhere, after multiple CP switchover/failures, itis possible (but not guaranteed) for a file to beduplicated in both the /spooled/opened/{type}and /spooled/closed/{type} directories, causinga Spooler to fail. A clear is issued after recov-ering from the condition.

Remedial Action If the status is set, resolve the file system con-dition which caused this alarm to be gener-ated. You may be required to take different ac-



tions to resolve the problem depending on thestate or status of the disk or file system. If thefile system is full, clean up some files. If the filesystem is locked, unlock it by issuing the un-lock command. If the file system fails, try tocopy unprocessed spool files (for example, us-ing FTP) from the control processor and thenreplace the control processor. When a recov-erable condition is resolved, the Spooler is no-tified and it automatically tries to continuespooling. The clear is issued when the Spooleris again able to spool data to the file system. Ifyou encounter an unexpected condition, theaction may vary to some degree, but mostlikely, at some point you will have to lock andthen unlock the FileSystem component. Thiscauses all active and failed DCS Spoolers toreset. In addition, file system commands maybe needed to clean up certain files. For ex-ample, if the "duplicate file" scenario men-tioned above occurs, one would have to re-move or rename the file in the "closed" direct-ory prior to locking/unlocking the FileSystemcomponent. If you are unable to resolve thefile system condition, contact Alcatel-Lucenttechnical support group.



6.62 MSS_7003_00003

RNC Type • POC

• 9370 RNC

Component Collector/{type} Spooler

Severity warning

cleared

Status set

clear

Detail {type} = accounting, alarm, log, scn, debug,stats, appl If the status is set, then the DCSSpooler does not restrict the number of spoolfiles to the value specified in the Spooler"™smaximumNumberOfFiles attribute. This condi-tion occurs when there are more than 250 filesin the associated spool directory. At this point,it is no longer possible for the Spooler to en-force the value specified by the maximum-NumberOfFiles attribute. The condition per-sists until the number of spool files for the as-sociated {type} is less than 250, at which timea clear alarm is issued. Note: This condition isonly expected to occur in the case where themaximumNumberOfFiles attribute is provi-sioned from zero to a non-zero value. A clearis issued after recovering from the condition.

Remedial Action Reduce the number of spool files for the asso-ciated type to below 250. This can be done inone of following ways. Ensure that MDP isconfigured to retrieve the spool files and re-move them from the node. Manually removethe spool files using the Filesystem compon-ent. The relevant directory to examine andfrom which to remove files is /spooled/closed/{type}. If you are unable to re-solve the file condition, contact Alcatel-Lucent



technical support.



6.63 MSS_7003_00004

RNC Type • POC

• 9370 RNC

Component Collector/alarm Agent/{cardnumber}

Severity warning

Status message

Detail {cardnumber} = 0 - 15 (the card on which theAgent resides) The purpose of this alarm is toindicate if software alarms (that is, thosealarms with indexes 0000 9000, 0000 9001,and 0000 9002) have been discarded and tospecify how many have been discarded. Soft-ware alarms are discarded when the rate atwhich they are generated exceeds a systemdefined threshold. This throttling mechanism isin place to protect services against an excess-ive number of software alarms.

Remedial Action There is no remedial action specific to thisalarm. The presence of this alarm, however,indicates an excessive quantity of softwarealarms was generated. The remedial action,when receiving software alarms, is to contactyour local Alcatel-Lucent technical supportgroup.



6.64 MSS_7003_00005

RNC Type • POC

• 9370 RNC

Component Collector/applicationSpecific Spooler

Severity major

Status message

Detail The data collection system (DCS) Spooler forthe applicationSpecific stream is not able tosend a file closure notification to the applica-tion generating the applicationSpecific records.

Remedial Action Determine why the application generating therecords is no longer registered or is not re-sponding. Retrieve and remove the file(s) spe-cified in the alarm from the disk.



6.65 MSS_7003_00006

RNC Type • POC

• 9370 RNC

Component Collector/applicationSpecific Spooler

Severity minor

Status message

Detail The data collection system (DCS) Spooler foran applicationSpecific stream is not able tosend a file deletion notification to the applica-tion generating the applicationSpecific records.

Remedial Action Determine why the application generating therecords is no longer registered or is not re-sponding.



6.66 MSS_7003_00007

RNC Type • POC

• 9370 RNC

Component Lp/{x} Eng AAList

Severity major

cleared

Status set

clear

Detail {x} = 0 - 15 If the status is set, the active alarmlist residing on the LP has reached a 75% fullthreshold. If the list becomes full, subsequentSET alarms are not added to it. There are twopossible reasons for the list to become full:There are many SET but no matching CLRalarms issued on the given LP. The activeSET alarms are held in the active alarm listand the list gradually fills up.The provisionedsize of the list may be insufficient for theamount of the SET alarm traffic If the status isclear, the size of the active alarm list thatresides on the LP has dropped below 50% andat least five minutes has elapsed since the setwas issued. This delay provides a throttlingmechanism so that bursts of records for relat-ively small queue sizes do not cause too manyalarms within a short time. The comment textof the clear alarm indicates how many activeset alarms were discarded (if any, in the eventthat the list became 100% full) since the setwas issued. This alarm is also hierarchicallycleared when the LP on which the active alarmlist resides is cleared.

Remedial Action If you do not want to monitor or build activealarm lists, you can provision the list sizes tobe disabled, delete the ActiveAlarmServices



component, or remove the active alarm listfeature from the feature lists. If any of theseactions are done, all active alarm lists areempty. Verify that the active alarm list sizesare provisioned to an adequate size.



6.67 MSS_7003_00008

RNC Type • POC

• 9370 RNC

Component Collector/log Spooler

Severity warning

Status message

Detail This alarm is generated when spooled log filesolder than the value of the 'daysToRetainFiles'attribute of the Col/log Sp component arepurged. It indicates the number of spooled logfiles deleted.

Remedial Action No action is required, this is only a warning.



6.68 MSS_7003_00009

RNC Type • POC

• 9370 RNC

Component Col/alarm Ag/{x}

Severity major

cleared

Status set

clear

Detail {x} = 0 - 15 agent card number The set alarmis issued to indicate that the number of in-stances of an alarm (with the same componentname and NTP index) has crossed thethreshold, which has a default of 5 alarms in30 seconds. Subsequent occurrences of allalarms that cross the threshold are discarded.Each alarm is throttled for a default period of60 minutes. This alarm indicates the beginningof the alarm throttle period. The clear alarm isissued when no more alarms are beingthrottled. This alarm indicates the end of thealarm throttle period.




6.69 MSS_7003_00010

RNC Type • POC

• 9370 RNC

Component Col/alarm Ag/{x}

Severity major

Status message

Detail {x} = 0 - 15 agent card number This alarm isissued every 15 minutes during the alarmthrottling period wherever repetitive alarms arediscarded. This alarm records a summary ofalarms discarded in the last 15 minutes. Thisalarm is only generated, if at least, one alarmis discarded in the last 15 minutes.




6.70 MSS_7006_00001

RNC Type • POC

• 9370 RNC

Component Nmis {type}

Severity major

Status message

Detail {type} = Telnet, Fmip, Ftp, or Ssh An NMISconnection was attempted from an unauthor-ized IP address. The attempted connectionwas blocked. The source IP address of theconnection is shown in the comment field.

Remedial Action This alarm may appear in two general scenari-os. First, the unauthorized IP address may bea legitimate network management stationwhose IP address has not yet been provi-sioned on the node. In this case, simply provi-sion an AccessControlIpAccess componentwith the new IP address. Second, the unau-thorized IP address may represent a hostile at-tack by a hacker attempting to penetrate thenode. Your network security may bethreatened. Verify that the source IP addressis not a friendly address, or refer the alarm toyour system administrator for investigation. Itmay be possible to trace the attack to thesource computer by using the source IP ad-dress.



6.71 MSS_7006_00002

RNC Type • POC

• 9370 RNC

Component Nmis {type} Session/{n}

Severity warning

Status message

Detail {type} = Telnet, Fmip, Local, Ftp, or Ssh {n} =session number A network management inter-face system (NMIS) login failed after three in-valid user ID/password attempts. The attemp-ted session is frozen for two minutes, and thenterminated. The last user ID entered and theIP address of the node attempting the loginare shown in the comment field. Alarms raisedfor local interface do not contain IP address.

Remedial Action This alarm may appear in two general scenari-os. First, a legitimate user may have incor-rectly entered the password three successivetimes. If you can determine that the alarm wascaused by a legitimate user, the alarm may beignored. Second, a hostile password attackmay be underway by a hacker attempting topenetrate the node. Your network security maybe threatened. The two-minute session freezewill slow the password attempts. To frustratethe attack even further, consider issuing aLock command on the interface used in the at-tack, or refer the alarm to your system admin-istrator for investigation. It may be possible totrace the attack back to its source by theuserId and the IP address shown in the com-ment field.



6.72 MSS_7006_00003

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {type} = Telnet, Fmip, Local, Ftp, or Ssh {n} =session number A TCP connection into net-work management interface system (NMIS)failed, causing the session to terminate. It ispossible to identify the node whose connectionfailed by the IP address shown in the commentfield. Note that the IP address is not shown inthe alarms raised for local interface. There areseveral possible causes for this situation, allrelating to a TCP/IP read/write failure. Someare: The NMIS session was killed without us-ing the logoff command. The remote site hascrashed. The IPIVC connection has failed,causing all sessions on that IPIVC to crash.The system administrator has issued a clearcommand for an interface session. The physic-al connection of the serial cable has been lost(local interface). Alcatel-Lucent MultiserviceData Manager checks the node continually tosee if it is operational. Under severe conges-tion conditions, or if the node"™s CPU is at100% capacity, it does not send a response toMultiservice Data Manager. Multiservice DataManager then closes its side of the connec-tion, thus killing the FMIP session. If the nodeis isolated (no trunks connecting to it), the ses-sion is not registered for alarms, and the work-station has the TCP/IP keep alive option, thesession shuts down after two hours.

Remedial Action



If the alarm was raised for local interface, en-sure that the serial cable is properly connectedto the V.24 socket on the node CP.



6.73 MSS_7006_00004

RNC Type • POC

• 9370 RNC

Component Nmis Fmip

Severity warning

minor

major

critical

indeterminate

Status message

Detail {severity} = major, minor or warning An FMIPprotocol error has occurred. The alarm is typic-ally associated with a command and the re-sponse to that command contains further in-formation. The command may have failedcompletely, or have been partially executed. Amajor severity indicates software errors, whileminor and warning severity are indicative ofAlcatel-Lucent Alcatel-Lucent MultiserviceData Manager workstation/Multiservice Switchsoftware version incompatibilities. There mayexist comment text with further information.

Remedial Action Typically, the Multiservice Data Manager work-station and Multiservice Switch software arerunning incompatible versions. It may be ne-cessary to upgrade the software on the work-station. If upgrading the software does noteliminate the alarm, contact Alcatel-Lucentglobal support.



6.74 MSS_7006_00005

RNC Type • POC

• 9370 RNC

Component Nmis Ftp Prov Migration

Severity major

Status message

Detail An FTP connection to the Active CP has beenattempted from a local 127.n.n.n IP addresson one of the FPs. The connection wasblocked. The FTP connection is typically es-tablished for an eprom firmware upgrade. TheFTP connection may be blocked for two reas-ons. The node may be running low on memoryneeded to set up the FTP session, or the FTPinterface may be locked (not the case for Mi-gration CP) or busy. Refer to the commentfield for an indicated cause for blocking theconnection. Note that this alarm is issued onlyfor FTP connections from a local 127.n.n.n IPaddress on the node itself, and not from gen-eral IP addresses outside the node.

Remedial Action If the FTP interface is locked, issue the Unlockcommand to enable FTP service. If the FTP in-terface is busy because all allowable sessionsare currently occupied, try to finish an FTPsession, log off, and free it for reuse. If CPheap memory is too low, the node may have tobe re-engineered or reprovisioned to free upmore heap.



6.75 MSS_7006_00006

RNC Type • POC

• 9370 RNC

Component Nmis Fmip

Severity major

Status message

Detail Nine consecutive invalid login attempts havebeen made to establish an FMIP session. Thisis probably caused by a Alcatel-LucentMultiservice Data Manager workstation that iscontinuously trying to establish a session withan invalid userid/password. This slows downresponse time considerably on the node. TheIP address of the node trying the login anduserid for the last failed attempt are shown inthe commentData field.

Remedial Action Identify the source attempting the login andcorrect the userid/password being used orstop it from attempting to establish a session.



6.76 MSS_7006_00007

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {type} = Telnet, Fmip, Ssh, or Local {n} = ses-sion number An NMIS session is automaticallyterminated, generating this alarm, when thesession is registered for a data stream(alarms, SCNs, logs, or debug) and the recordcould not be output within 1 min 30 s.The IPaddress of the remote host is indicated in thecomment field if the alarm is raised for remoteor FMIP interface. Possible causes: The nodeis isolated (no trunks connecting to it) and theconnection not recovered within 1 min 30s.Thenetwork is extremely congested, causing thewriting of data to the network to take morethan 90 seconds.




6.77 MSS_7006_00008

RNC Type • POC

• 9370 RNC

Component Nmis {type}

Severity major

Status message

Detail {type} = Fmip This alarm is issued if a corrup-ted message is sent to NMIS, causing the ses-sion to terminate. It is possible to identify thenode whose connection failed from the IP ad-dress shown in the comment field.




6.78 MSS_7006_00009

RNC Type • POC

• 9370 RNC

Component Ac

Severity warning

Status message

Detail This alarm notifies the system that an authen-tication attempt for a user ID was successfulusing a centralized database with RADIUS,but the userID was not permitted to start asession with the node. This occurs becausethe Role VSA (vendor-specific attribute) in theAccess-Accept PDU sent from the RADIUSserver does not exist as an instance of AcRole/{string} on this node. The role name isshown in the comment text of the PDU.

Remedial Action Check the role name against the user ID onthe RADIUS server. Make sure it is spelledcorrectly on both the RADIUS server and innode provisioning.



6.79 MSS_7006_00010

RNC Type • POC

• 9370 RNC

Component Nmis Ssh

Severity warning

Status message

Detail An operator has initiated SSH server host keysgeneration.

Remedial Action No remedial action is required. SSH clientsshould be aware of server host key signaturechange as this may result in warnings from theclient software when connecting to Multiser-vice Switch after the key generation com-pletes.



6.80 MSS_7006_00011

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {type} = Telnet, Fmip, Local, Ssh {n} = Sessionnumber If the status is set, then the user, iden-tified in the comment text, has disabled thedisruptive command checks, which allows thenext issue of a disruptive command to proceedwith its associated impact. This can include anoutage to all or part of the system. The CLEARis generated in the following scenarios: Theuser issues one of the disruptive commandsidentified in the comment text, which are de-termined from the Nmis Hicc supportedCom-mands attribute. After one disruptive commandis issued, the command checks are en-abled.The user re-enables the commandchecks manually without issuing a disruptivecommand.The user session terminates (for ex-ample, user logs off prior to issuing a disrupt-ive command). If the session terminates ab-normally (for example, active CP Reset) theclear may not appear explicitly, but will becleared through the system hierarchical clearsand state-walks after CP recovery.

Remedial Action When a SET alarm is generated, it can becleared in the following ways: Issue a disrupt-ive command specified in the Nmis Hicc sup-portedCommands attribute value.Re-enablethe command checks manually without issuing



a disruptive command.Terminate the session.Ifthe SET alarm is generated by setting thecommandCheck attribute of the standby CPLocal Session and the standby CP resets, theSET alarm does not clear through the systemhierarchical clearing. The SET alarm shouldbe manually cleared.



6.81 MSS_7006_00012

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {type} = Telnet, Fmip, Local, Ssh {n} = Sessionnumber If the status is SET, then the user,identified in the comment text, has set thissession's debugCommandCheck attribute todisabled. This allows one or more subsequentdisruptive commands to proceed, each with itsassociated impact, which can include an out-age to all or part of the system. A CLEAR isgenerated in the following scenarios: The usersets this session's debugCommandCheck toenabled.The user"™s session terminates forsome reason (for example, the user logs offprior to actually issuing a disruptive com-mand). If the session terminates abnormally(for example, active CP reset), the clear maynot appear explicitly, but will be clearedthrough the system hierarchical clears andstate-walks after CP recovery.

Remedial Action When the SET is generated, it can be clearedin the following ways: Issue a disruptive com-mand specified in the Nmis Hicc supported-Commands attribute value.Set this session'sdebugCommandCheck to enabled.Terminatethe session. If the SET alarm is generated bysetting the debugCommandCheck attribute ofthe standby CP Local Session and if thestandby CP resets, the SET alarm does not



clear through the system hierarchical clear-ing.The SET alarm should be manuallycleared in this case.



6.82 MSS_7006_00013

RNC Type • POC

• 9370 RNC

Component Nmis Fmip Session/x

Severity major

Status message

Detail {x} = the FMIP session Id This alarm is issuedwhen the fast management information pro-tocol (FMIP) session receives a corrupt pro-tocol data unit (PDU), which results in a denialof service.




6.83 MSS_7006_00100

RNC Type • POC

• 9370 RNC

Component Ac Radius

Severity critical

cleared

Status set

clear

Detail This alarm occurs when attempts to authentic-ate with all RADIUS servers have failed (bytime-outs). Authentication must be possibleusing RADIUS. A clear is issued when an at-tempt to authenticate with at least one RADI-US server has succeeded.

Remedial Action Verify IP connectivity is possible from the nodeto the RADIUS server(s). This can be done us-ing the Ping command from the node and fromthe server. If connectivity is stable, determinethe average times and ensure that the value ofattribute Ac Radius timeOut is not set to time-out too soon. Verify the RADIUS server(s) withwhich the node authenticates are operational.Verify there are no network congestion issues.Use a backup user ID and password to accessthe node to troubleshoot.



6.84 MSS_7006_00101

RNC Type • POC

• 9370 RNC

Component Ac Radius Server/{n}

Severity major

Status message

Detail {n} = 0 - 1 This alarm notifies the system thatan attempt to authenticate with the specifiedRADIUS server has timed out. The IP ad-dresses of the servers with which you attemp-ted to authenticate are shown in the commenttext.

Remedial Action Verify IP connectivity is possible from the nodeto the RADIUS server. This can be done usingthe Ping command from the node and from theserver. If connectivity is stable, determine theaverage times and ensure that the value of at-tribute Ac Radius timeOut is not set to time-outtoo soon. Verify the RADIUS server with whichthe node authenticates is operational.



6.85 MSS_7006_00102

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {n} = 0 - 1 This alarm notifies the system thatan authentication attempt for a userID wassuccessful with a centralized database usingRADIUS. However the Access-Accept PDUsent from the RADIUS server is missing re-quired access permissions that authorize theuserID to start a session.

Remedial Action Verify the userID on the RADIUS server isconfigured to send back the required accesspermissions in the Vendor Specific Attributesupon successful authentication. Verify the RA-DIUS server is retrieving the access permis-sions correctly from the database. Verify thereare seven attributes being sent back to thenode.



6.86 MSS_7006_00103

RNC Type • POC

• 9370 RNC

Component Ac Radius

Severity major

Status message

Detail This alarm notifies the system that a RADIUSPDU is received with an IP address that doesnot match a RADIUS server that is currentlyprovisioned. The IP address of the server inquestion is shown in the comment text.

Remedial Action Verify the IP address in the alarm is the ad-dress of the RADIUS server. Verify the attrib-ute Ac Radius Server serverIpAddress is provi-sioned correctly with a RADIUS server that ex-ists. Verify the IP address is not from an in-truder.



6.87 MSS_7006_00104

RNC Type • POC

• 9370 RNC

Component Ac Radius

Severity major

Status message

Detail This alarm notifies the system that an unsup-ported RADIUS PDU has been received. Thesupported types are Access-Accept and Ac-cess-Reject. The known types of RADIUSPDUs that could be received are Access-Re-quest, Access-Challenge, Accounting-Re-quest, and Accounting-Response.

Remedial Action Verify the RADIUS server with which the nodeauthenticates is configured correctly. Verify theIP address provisioned on the node is uniqueand is not being used as a RADIUS server ad-dress by another NAS device. Verify an in-truder is not sending the Multiservice Switchpackets to the port 1812 or 1645.



6.88 MSS_7006_00105

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {n} = 0 - 1 This alarm notifies the system that aRADIUS PDU was received unexpectedly.There is no matching authentication requestfor this RADIUS PDU.

Remedial Action Verify the RADIUS server is not sending morethan one RADIUS PDU. Verify RADIUS PDUsare not being accidentally routed to the node.



6.89 MSS_7008_01001

RNC Type • POC

• 9370 RNC

Component Fs

Severity major

cleared

Status set

clear

Detail The file system disk space usage is above85% of its total capacity. A clear is issuedwhen the used space is below 75% of the diskcapacity.

Remedial Action Remove some files from the disk immediatelyto prevent the file system from becoming fulland to avoid the risk of lost data. The activedisk must be cleaned up immediately by doingone or more of the following: tidy the provision-ing datatidy the software filesoff-load spooleddata



6.90 MSS_7008_01002

RNC Type • POC

• 9370 RNC

Component Fs

Severity critical

cleared

Status set

clear

Detail The file system disk is 100% full. This causesservice to be affected. A clear is issued whenthe disk space usage is below 90% of the totaldisk capacity.

Remedial Action Clean up the active disk immediately by doingone or more of the following: tidy the provision-ing datatidy the software filesoff-load spooleddata



6.91 MSS_7008_01003

RNC Type • POC

• 9370 RNC

Component Fs

Severity major

Status message

Detail The root directory "/" is full. The number of dir-ectories or files in the root directory "/" hasreached the maximum allowed (112 files anddirectories).

Remedial Action Remove some files or directories in the rootdirectory. Alcatel-Lucent recommends thatfiles be placed in subdirectories rather than inthe root directory (The root directory shouldonly contain directories).



6.92 MSS_7008_01004

RNC Type • POC

• 9370 RNC

Component Fs

Severity critical

cleared

Status set

clear

Detail The file system is disabled and therefore can-not be accessed. This alarm will be clearedwhen the file system is accessible again.However, this is not likely to happen until thecontrol processor card is reset.

Remedial Action Reset the active control processor card. Thisaction is service-affecting if there is only oneCP on the shelf. The action must be done withcaution. If the problem persists, return the cardto the manufacturer. The most likely cause is abad disk.



6.93 MSS_7008_01005

RNC Type • POC

• 9370 RNC

Component Fs

Severity major

cleared

Status set

clear

Detail The synchronization of the standby disk to theactive disk has failed, the possible causes are:disks have different volume namesinsufficientstandby disk capacitystandby disk is locked ordisableddisk synchronization has failed threetimes due to heavy file system activity or otherreason. A clear is issued when the synchroniz-ation is complete.

Remedial Action Display the disk attributes and check if thevolume names are the same. If they are differ-ent, re-synchronize the two disks manually. Ifthe standby disk is locked, unlock it and re-synchronize manually. If the standby disk isdisabled, reset the standby card. If the standbydisk capacity is less than the used disk spaceon the active disk, you may have to removefiles on the active disk by issuing a tidy prov ora tidy sw command, or alternatively, you mayhave to upgrade your control processor with alarger disk. If none of the standby disk prob-lems are present, re-synchronize manually.



6.94 MSS_7008_01006

RNC Type • POC

• 9370 RNC

Component Fs

Severity major

cleared

Status set

clear

Detail The file system has too many open files.

Remedial Action Contact Alcatel-Lucent global support.



6.95 MSS_7008_01008

RNC Type • POC

• 9370 RNC

Component Fs Disk/{instance}

Severity major

cleared

Status set

clear

Detail For Alcatel-Lucent Multiservice Switch 15000and Multiservice Switch 20000:{instance} = 0,1 For Multiservice Switch 7400:{instance} = 0,15 A read/write has error occurred on the act-ive disk causing the disk to become unavail-able. If the system has a synchronizedstandby control processor (CP), the faulty diskwill have its CP rebooted.

Remedial Action No action required. If this error occurs fre-quently, run the disk tests on the faulty disk.See Alcatel-Lucent Multiservice Switch7400/15000/20000 Troubleshooting(NN10600-520) for a description of possibledisk tests.



6.96 MSS_7008_01009

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail For Alcatel-Lucent Multiservice Switch 15000and Multiservice Switch 20000:{instance} = 0,1 For Multiservice Switch 7400:{instance} = 0,15 A disk media error test has found a read/write error in the disk boot area. A clear is is-sued when the disk is replaced.

Remedial Action Return the card to the manufacturer.



6.97 MSS_7008_01010

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail For Alcatel-Lucent Multiservice Switch 15000and Multiservice Switch 20000:{instance} = 0,1 For Multiservice Switch 7400:{instance} = 0,15 A disk surface analysis test has found badclusters. They were re-mapped and thevolume has been re-initialized. This alarmclears after resetting the card.

Remedial Action Reset the card. If the problem persists returnthe card to the manufacturer.



6.98 MSS_7008_01011

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0, 15 A disk media test has founderrors. This alarm will be cleared when thedisk is fixed.

Remedial Action Run the filesystemCheck test on the faultydisk.



6.99 MSS_7008_01012

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail For Alcatel-Lucent Multiservice Switch 15000and Multiservice Switch 20000:{instance} = 0,1 For Multiservice Switch 7400:{instance} = 0,15 The file system check test has found someintegrity errors and corrected them. No data islost.

Remedial Action If the file system has a standby control pro-cessor, synchronize the file system immedi-ately.



6.100 MSS_7008_01013

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail For Alcatel-Lucent Multiservice Switch 15000and Multiservice Switch 20000:{instance} = 0,1 For Multiservice Switch 7400:{instance} = 0,15 The filesystemCheck test has found someintegrity errors and fixed them. Some data islost.

Remedial Action If the file system has a standby control pro-cessor, synchronize the file system immedi-ately.



6.101 MSS_7008_01014

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail For Alcatel-Lucent Multiservice Switch 15000and Multiservice Switch 20000:{instance} = 0,1 For Multiservice Switch 7400:{instance} = 0,15 A disk test failed to complete and the causeis unknown.

Remedial Action Reset the card and run the test again. If theproblem persists return the card to the manu-facturer.



6.102 MSS_7008_01015

RNC Type • POC

• 9370 RNC


Severity minor

Status message

Detail For Alcatel-Lucent Multiservice Switch 15000and Multiservice Switch 20000:{instance} = 0,1 For Multiservice Switch 7400:{instance} = 0,15 An operation on the standby disk did notcomplete as expected. The standby controlprocessor is rebooted and synchronizes auto-matically.

Remedial Action No action is required.



6.103 MSS_7008_01016

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail For Alcatel-Lucent Multiservice Switch 7400:{instance} = 0, 15 For Alcatel-Lucent Multiser-vice Switch 15000 and Alcatel-Lucent Multiser-vice Switch 20000: {instance} = 0, 1 A commu-nication error has occurred between the activecontrol processor and the standby control pro-cessor. The standby control processor is re-booted and synchronizes automatically.

Remedial Action No action is required. If the problem persists,contact Alcatel-Lucent global support.



6.104 MSS_7008_01017

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {instance} = 0, 15 The Disk component islocked. A clear will be issued when the disk isunlocked.

Remedial Action Unlock the Disk component.



6.105 MSS_7008_01018

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail For Alcatel-Lucent Multiservice Switch 7400:{instance} = 0, 15 For Alcatel-Lucent Multiser-vice Switch 15000 and Alcatel-Lucent Multiser-vice Switch 20000: {instance} = 0, 1 The peri-odic disk access test has not received a re-sponse from the disk. The control processorwith the failed disk is reset if it is in standbymode. If the control processor is active, a re-coverable software error is raised.

Remedial Action If the standby disk resets, the file system willre-synchronize automatically when thestandby disk becomes available. No action isrequired for the standby control processor. Forthe active control processor, manually reset ifthe disk problem persists.



6.106 MSS_7008_01019

RNC Type • POC

• 9370 RNC

Component Fs

Severity major

cleared

Status set

clear

Detail The File system is no longer synchronized forone of the following reasons: the standby diskis lockedone disk is fullthe standby disk hasbeen resetdevice can not be opened orclosedcontrolling functions can not be per-formed on device

Remedial Action Display the disk"™s attributes and check if thestandby disk is locked. If the disk is locked, un-lock it using the unlock command and re-synchronize the filesystem. If the disk is full,clean up the disk by issuing a tidy sw (for soft-ware files) or a tidy prov command (for provi-sioning data) and re-synchronize. If thestandby disk resets, no action is required. Thefilesystem re-synchronizes automatically whenthe active disk becomes available. If thedevice cannot open or close, change thedevice. If the controlling functions cannot beperformed, contact Alcatel-Lucent global sup-port.



6.107 MSS_7008_01020

RNC Type • POC

• 9370 RNC

Component Fs

Severity minor

Status message

Detail This alarm indicates that disk synchronizationhas failed due to heavy file system activity.The system will attempt to re-initiate disk syn-chronization automatically, to a maximum of 3attempts. The alarm message also indicatesthe number of synchronization attempts made.

Remedial Action If all three automatic synchronization attemptsare unsuccessful, you must initiate disk syn-chronization manually.



6.108 MSS_7008_01021

RNC Type • POC

• 9370 RNC

Component Shelf Card/{x}

Severity major

Status message

Detail {x} = 0 - 1 This alarm is raised when the CPdisk size is too small to support the provi-sioned software. If this occurs on the activeCP, the file system will be disabled until thesoftware reverts back to the previous version.If the standby CP has a small disk, it will con-tinuously crash until either the software revertsback to the previous version or the standby CPis replaced with a correct size disk.

Remedial Action Verify the CP disk size and compare it to therequired disk size for the product. If the disk istoo small replace the CP with the small diskwith another CP which has a correct disk size.



6.109 MSS_7008_01022

RNC Type • POC

• 9370 RNC

Component Fs

Severity major

Status message

Detail {x} = 0 - 1 This alarm is raised during a patchdownload that contains firmware patches, ifthe unpatched version of the firmware cannotbe found on the switch. The download is abor-ted and whatever was downloaded prior to theerror is cleaned up. The problem must be cor-rected before the patch can be downloadedagain. There are two possible causes for thisalarm: The Patch Descriptor (PD) file containsa firmware patch that is not supported on thatshelf.The shelf is missing the firmware whichshould have been downloaded as part of thebase application.

Remedial Action Check the PD file and ensure that it does notcontain a firmware patch that is not supportedon the switch. If the firmware is to be suppor-ted on the switch, redownload the base applic-ation, ensuring that the download is done forboth PPC and i960 platforms.



6.110 MSS_7008_01023

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail For Alcatel-Lucent Multiservice Switch 7400:{instance} = 0, 15 For Alcatel-Lucent Multiser-vice Switch 15000 and Alcatel-Lucent Multiser-vice Switch 20000: {instance} = 0, 1 Prior toresetting the card, there is a problem readingfrom the disk on this card. After resetting thecard, the problem files were detected and re-moved from the disk. The problem area on thedisk is no longer usable by the filesystem. In aControl Processor (CP) card, if the removedfiles were in the shadowed partition, the filesare restored when the disk is synchronizedwith the other CP's disk.

Remedial Action In a dual-CP setup, no action is required. If theproblem persists, or if there is no spare CP torestore the removed file(s), contact Alcatel-Lu-cent global support.



6.111 MSS_7008_01024

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail For Alcatel-Lucent Multiservice Switch 15000and Alcatel-Lucent Multiservice Switch 20000:{instance} = 0, 1 This alarm is not applicable toAlcatel-Lucent Multiservice Switch 7400. Thenumber of reallocated disk sectors on com-ponent Fs Disk/{instance} has crossed its ma-jor fault threshold of 900 reallocated disk sec-tors. The maximum number of sectors avail-able for reallocation is 1024. The disk is ap-proaching end of life.

Remedial Action Consider replacing the CP at the next avail-able opportunity. For information on replacinga CP, refer to the Failed CP Replacement sec-tion of Alcatel-Lucent Multiservice Switch15000/20000 Installation, Maintenance, andUpgrade - Hardware (NN10600-130). When astandby CP is removed for replacement, allalarms against the standby CP's disk arecleared.



6.112 MSS_7011_01100

RNC Type • POC

• 9370 RNC

Component For Multiservice Switch 7400: Lp/{num1} Ima/{num2}

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 113 {num3} = 0 -3 {num4} = 0 - 13 If the status is set, there areno links active in the IMA group, or there is atiming mismatch in the IMA group. If there areno links active in the IMA group, the IMA virtu-al link is not capable of carrying any usertraffic. A clear is issued when one or morelinks in the IMA group are activated, or whenthe timing mismatch no longer exists.

Remedial Action This condition is usually caused by incorrectconnection of the links or configuration of thelocal and remote IMA groups. Check that thephysical ports are properly connected at thelocal and remote ends, and that all port alarmsare clear. Examine the alarm comment textand the failureCause and remoteDefect opera-tional attributes of the IMA component to ob-tain an indication as to the cause of the prob-lem, and check the configuration of the IMAand LINK components on the local and remoteends.



6.113 MSS_7011_01200

RNC Type • POC

• 9370 RNC

Component For Multiservice Switch 7400: Lp/{num1} Ima/{num2} Lk/{num5}

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 113 {num3} = 0 -3 {num4} = 0 - 13 {num5} = 0 - 31 If the statusis set, the link is not an active member of theIMA group. The link will not be used by theIMA group for carrying any user traffic. A clearis issued when the link is activated in the IMAgroup.

Remedial Action This condition is usually caused by incorrectconnection or configuration of the link. Firstcheck that the physical port used by this link isproperly connected at the local and remoteends, and that all port alarms are clear. If theproblem persists then examine the failure-Cause and remoteDefect operational attributesof the LINK component to obtain an indicationas to the cause of the problem, and check theconfiguration of the LINK components on thelocal and remote ends.



6.114 MSS_7011_01210

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 113 {num3} = 0 -3 {num4} = 0 - 13 {num5} = 0 - 31 If the statusis set, a loss of IMA frame (LIF) alarm condi-tion has been declared. The LIF alarm condi-tion is declared when the a LIF defect has per-sisted on the link for 2.5 Â± 0.5 seconds. Aclear is issued when the LIF defect has beenabsent for 10.0 Â± 0.5 seconds. A LIF defectis declared if IMA framing has not been re-covered three IMA frame periods after the oc-currence of an out of IMA frame (OIF) anom-aly. An OIF anomaly is the occurrence of oneof the following events: a missing ICP cellaninvalid ICP celltwo consecutive errored ICPcellsa valid ICP cell at an unexpected positionA LIF defect is cleared if IMA framing hasbeen maintained for two IMA frame periods.

Remedial Action This condition is usually caused by incorrectconnection or configuration of the link. Checkthe lastOifCause operational attribute of thelink for an indication of the cause. Ensure thatthe physical port is properly connected at thelocal and remote ends, and check the config-uration of the link component on the local andremote ends.



6.115 MSS_7011_01211

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 113 {num3} = 0 -3 {num4} = 0 - 13 {num5} = 0 - 31 If the statusis set, a loss of delay synchronization (LODS)condition is present on the link. A clear is is-sued once the LODS condition is no longerpresent. A LODS condition is declared whenthe transit delay of a link being activated in theIMA group relative to the reference link in theIMA group exceeds the provisioned maximumacceptable differential delay, or when thetransit delay of a link already active in the IMAgroup relative to the reference link in the IMAgroup exceeds the provisioned maximum ac-ceptable differential delay plus one milli-second. The LODS condition is cleared whenthe transit delay of the link relative to the refer-ence link in the IMA group is within the provi-sioned maximum acceptable differential delay.

Remedial Action Check the relativeDelay operational attributeof the link to determine its differential delay. Ifan increase in the maximum differential delayacross the IMA group is acceptable, increasethe setting of the maxDiffDelay attribute of theparent IMA component. Alternatively, changingthe setting of the linkSelectionCriterion attrib-ute of the parent IMA component may result in



a different reference link for the IMA group;however, be warned that this may result in thedifferential delay becoming unacceptable forother links in the group. If the above actions donot solve the problem, replace the physical fa-cility used by this link with one that exhibits atransit delay closer to that of the reference link.



6.116 MSS_7011_01212

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 113 {num3} = 0 -3 {num4} = 0 - 13 {num5} = 0 - 31 If the statusis set, the link has been identified as beingmisconnected. A clear is issued once the mis-connection is no longer present. A link istested for misconnection during the IMA groupstart-up and link addition procedures. A link isidentified as being misconnected if the remoteend does not loop back a test pattern transmit-ted by the local end, or if the link belongs to adifferent IMA group than the one with whichthe local end has elected to stage.

Remedial Action This condition is usually caused by incorrectconnection or configuration of the link. Checkthat the physical port is properly connected atthe local and remote ends, and check the con-figuration of the LINK component on the localand remote ends.



6.117 MSS_7011_01213

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 113 {num3} = 0 -3 {num4} = 0 - 13 {num5} = 0 - 31 If the statusis set, a remote failure indicator (RFI) alarmcondition has been declared. The RFI alarmcondition is declared when a remote defect in-dicator (RDI) defect has persisted on the linkfor 2.5 Â± 0.5 seconds. A clear is issued whenthe RDI defect has been absent for 10.0 Â±0.5 seconds. An RDI defect is declared whenone of the following remote defect indicators isreceived for this link from the remote IMA:physical link defectloss of IMA frame (LIF)lossof delay synchronization (LODS) The RDI de-fect is cleared when a remote defect indicatoris no longer being received for the link fromthe remote IMA.

Remedial Action Check the remoteDefect operational attributeof the link to determine what defect indicator isbeing received from the far end. Verify the op-erational attributes at the remote end to de-termine why the defect indicator is being trans-mitted.



6.118 MSS_7011_01214

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 113 {num3} = 0 -3 {num4} = 0 - 13 {num5} = 0 - 31 If the statusis set, a fault alarm condition has been de-clared on the link. A fault alarm condition is de-clared if no ICP cells are detected on the linkduring a start-up or link addition attempt or ifan invalid IMA group ID, frame length, groupsymmetry or logical link ID is received on thelink during IMA group start-up or link addition.A clear is issued when the fault alarm condi-tion is not longer present.

Remedial Action This condition is usually caused by incorrectconnection or configuration of the link. Checkthe failureCause operational attribute of thelink to obtain an indication as to the cause ofthe problem. Ensure that the physical port isproperly connected at the local and remoteends, and check the configuration of the LINKcomponents on the local and remote ends.



6.119 MSS_7011_01215

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 113 {num3} = 0 -3 {num4} = 0 - 13 {num5} = 0 - 31 If the statusis set, the remote link has gone to the Unus-able state. A clear is issued once the remotelink is no longer in the Unusable state.

Remedial Action Check the operational attributes at the remoteend to determine why it has gone to the Unus-able state.



6.120 MSS_7011_01216

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 113 {num3} = 0 -3 {num4} = 0 - 13 {num5} = 0 - 31 If the statusis set, a protocol error alarm condition hasbeen declared on the link. A protocol erroralarm condition is declared if, during IMAgroup start-up or link addition, the link couldnot be activated within the prescribed time-outperiod, and no other failure condition has beenidentified. A clear is issued when the protocolerror condition is not longer present.

Remedial Action This condition may be caused by incorrectconfiguration of the IMA group. Verify thelinkRetryTimeout provisionable attribute of theIMA component at the local and remote ends,and check the operational attributes of the IMAand LINK components at the local and remoteends.



6.121 MSS_7011_01400

RNC Type • POC

• 9370 RNC

Component Lp/{num1} Mlfr/{num2}

Severity critical

cleared

Status set

clear

Detail {num1} = 2 - 15 {num2} = 0 - 111 If the statusis set, there is an insufficient number of links(determined by activationClass and activation-Threshold attributes under the MultiLink-FrameRelay component) in the up state. Aclear is issued when a sufficient number oflinks (determined by activationClass and activ-ationThreshold attributes under the MultiLink-FrameRelay component) are in the up state.

Remedial Action Check the state of the MultiLinkFrameRelayand Link components on local and remote en-dpoints and, if necessary, add more links tothe bundle.



6.122 MSS_7011_01401

RNC Type • POC

• 9370 RNC

Component Lp/{num1} Mlfr/{num2} Link/{num3}

Severity critical

cleared

Status set

clear

Detail {num1} = 2 - 15 {num2} = 0 - 111 {num3} = 0 -27 If the status is set, there is a bundle linkconfiguration mismatch between the expectedand the received value for the remoteName at-tribute for the bundle. A clear is issued whenthe expected value for the remoteName attrib-ute for the bundle is received.

Remedial Action Check the errorCause and remoteName attrib-utes and the configured data for the Link com-ponent. Lock and unlock the MultiLink-FrameRelay component to restart the MLFRlink integrity protocol.



6.123 MSS_7011_01402

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 2 - 15 {num2} = 0 - 111 {num3} = 0 -27 If the status is set, there is an unrecognizedOUI in a received Vendor Specific informationfield. A clear is issued when the expected OUIis received.

Remedial Action Remove the Link and add it again to Mlfr com-ponent.



6.124 MSS_7011_01403

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 2 - 15 {num2} = 0 - 111 {num3} = 0 -27 If the status is set, the link is in idle state. Aclear is issued when the link leaves the idlestate.

Remedial Action Check the cause attribute and the provisioneddata for the Link component. Lock and unlockthe MultiLinkFrameRelay component to restartthe MLFR link integrity protocol.



6.125 MSS_7011_01404

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 2 - 15 {num2} = 0 - 111 {num3} = 0 -27 If the status is set, the link is in down state.A clear is issued when the link leaves thedown state.

Remedial Action Check the cause attribute and the provisioneddata for the Link component. Lock and unlockthe MultiLinkFrameRelay component to restartthe MLFR link integrity protocol.



6.126 MSS_7011_01405

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {num1} = 2 - 15 {num2} = 0 - 111 {num3} = 0 -27 If the status is set, a loopback was detec-ted. A clear is issued when the loopback is re-moved.

Remedial Action Check if the external loopback is installed.



6.127 MSS_7011_01406

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 2 - 15 {num2} = 0 - 111 {num3} = 0 -27 If the status is set, the bundle link differen-tial delay exceeds the maximum allowed. Aclear is issued when the bundle link differentialdelay no longer exceeds the maximum al-lowed.

Remedial Action The operator may consider the increasing ofthe value of the maxDiffDelay attribute for thisbundle, based on the length of the wires andthe size of the frames between the near andfar end.



6.128 MSS_7011_01407

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 2 - 15 {num2} = 0 - 111 {num3} = 0 -27 If the status is set, there was detected anerror in the MLFR link integrity protocolbetween the near and far end. A clear is is-sued when valid MLFR link integrity protocolmessages are received.

Remedial Action Lock and unlock the MultiLinkFrameRelaycomponent to restart the MLFR link integrityprotocol.



6.129 MSS_7011_01500

RNC Type • POC

• 9370 RNC

Component Lp/{x} Lag/{y}

Severity critical

cleared

Status set

clear

Detail {x} = 2 - 15 {y} = 0 - 7 If the status is set, thereare no links active in the Link Aggregation(LAG) group. The LAG is not capable of carry-ing any user traffic. A clear is issued when oneor more links in the LAG group is/are activ-ated.

Remedial Action This condition is usually caused by incorrectconnection of the links, incorrect configurationof the local and remote end LAG groups or op-erational conditions. Check that the physicalports are properly connected at the local andremote ends, and that all port alarms are clear.Examine the alarm comment text and the fail-ureCause operational attribute of the LAGcomponent to obtain an indication as to thecause of the problem, and check the configur-ation of the LAG link components on the localand remote ends.



6.130 MSS_7011_01501

RNC Type • POC

• 9370 RNC

Component Lp/{x} Lag/{y} Link/{z}

Severity critical

cleared

Status set

clear

Detail {x} = 2 - 15 {y} = 0 - 7 {z} = 0 - 31 If the statusis set, the logical link is not active in the LinkAggregation (LAG) group. The link is not cap-able of carrying any user traffic. A clear is is-sued when the fault condition on the link clearsand the link is activated.

Remedial Action This condition is usually caused by incorrectconnection or configuration of the link. Checkthat the physical ports are properly connectedat the local and remote ends, and that all portalarms are clear. Examine the alarm commenttext and the failureCause operational attributeof the link component to obtain an indicationas to the cause of the problem, and check theconfiguration of the link components on thelocal and remote ends.



6.131 MSS_7011_02000

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type}/{num2}

Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = DS3, E3, SONET,SDH, DS1, E1, CHANNEL, V35, X21, HSSI,IMA, BridgedSonet, and Ethernet. {num2} = 0 -n, where n is 1 less than the number of portssupported on the card type When a hardwarefailure has been found by port diagnostics, theport is automatically locked and disabled bythe system. Alarm code 70112000 is raised in-dicating the card is unable to synchronize itstransmit clock to the CP"™s module clock.This may indicate an equipment malfunctionon the FP, on the backplane, or on the activeCP from which the module clock signal origin-ates. A clear is issued after running the dia-gnostics successfully.

Remedial Action Check for defective FP, backplane, or CPhardware.



6.132 MSS_7011_02001

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = V35, X21 and HSSI{num2} = 0 - n, where n is 1 less than the num-ber of ports supported on the card type used.If the status is set, the link is in a state thatrenders the port disabled. On a V35 or a X21port, if the incoming line state is not consistentwith that described in the provisionable attrib-ute readyLineState, the port is disabled. Aclear is issued when the condition has beencleared.

Remedial Action Issue the display command on the componentthat has issued the alarm to discover thecause of the problem. For a V35 or X21 port,check if the readyLineState attribute is set upas expected and verify that the cable is con-nected properly.



6.133 MSS_7011_02002

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status message

Detail {num1} = 0 - 15 {type} = DS3, E3, SONET,and SDH {num2} = 0 - n, where n is 1 lessthan the number of ports supported on thecard type The card is unable to synchronize itstransmit clock to the CP"™s module clock.This may indicate an equipment malfunctionon the FP, on the backplane, or on the activeCP from which the module clock signal origin-ates.

Remedial Action Check for defective FP, backplane, or CPhardware.



6.134 MSS_7011_05000

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type}/{num2}orLp/{num1} SDH/{num2} VC4/0 VC12/{num3} E1orLp/{num1}Sonet/{num2} Sts/{num4} Vt1dot5/{num5}DS1orLaps/{num6} {Sts}/{num4}{Vt1dot5}/{num5} DS1orLaps/{num6} {VC4/0}{VC12}/{num3} E1

Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = EDS1, EE1, DS1, andE1 {num2} = 0-n, where n is 1 less than thenumber of ports supported on the card typeused {num3} = multiple indexes 1-3, 1-7, 1-3{num4} = 0 - 3 {num5} = multiple indexes 1-7,1-4 {num6} = 0 - 15999 If the status is set, thelink has been in a Loss of Frame (LOF) statefor greater than 2 seconds. A clear is issuedwhen the LOF condition has been cleared formore than 10 seconds.

Remedial Action Check the far end for proper configuration.



6.135 MSS_7011_05001

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type}/{num2}orLp/{num1} SDH/{num2} VC4/0 VC12/{num3} E1orLp/{num1}Sonet/{num2} Sts/{num4} Vt1dot5/{num5} DS1orLaps/{num6} {Sts}/{num4} {Vt1dot5}/{num5}DS1orLaps/{num6} {VC4/0} {VC12}/{num3} E1

Severity minor

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = EDS1, EE1, DS1, andE1 {num2} = 0-n, where n is 1 less than thenumber of ports supported on the card typeused {num3} = multiple indexes 1-3, 1-7, 1-3{num4} = 0 - 3 {num5} = multiple indexes 1-7,1-4 {num6} = 0 - 15999 If the status is set,then the far end Remote Alarm Indication(RAI) defect indicators have been received.This is indicated immediately and remainspresent for a minimum of 1 second. A clear isissued when no far end RAI defect indicatorsare detected.

Remedial Action The far end is complaining about a Loss ofFrame (LOF) or Alarm Indication Signal (AIS)condition. Check that the provisioning data isconsistent on both ends of the connection.



6.136 MSS_7011_05002

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type}/{num2}orLp/{num1} SDH/{num2} VC4/0 VC12/{num3} E1orLp/{num1}Sonet/{num2} Sts/{num4} Vt1dot5/{num5} DS1orLaps/{num6} {Sts}/{num4} {Vt1dot5}/{num5}DS1orLaps/{num6} {VC4/0} {VC12}/{num3} E1

Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = EDS1, EE1, DS1, andE1 {num2} = 0-n, where n is 1 less than thenumber of ports supported on the card typeused {num3} = multiple indexes 1-3, 1-7, 1-3{num4} = 0 - 3 {num5} = multiple indexes 1-7,1-4 {num6} = 0 - 15999 If the status is set, thelink has been in an Alarm Indication Signal(AIS) state for a minimum of 2 seconds. Aclear is issued when the AIS condition hasbeen cleared for a minimum of 10 seconds.

Remedial Action The far end is complaining about Loss of Sig-nal (LOS) or the far end port is under test.Check the cabling between the two interfacesor check if there are any tests running on thefar end interface.



6.137 MSS_7011_05003

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type}/{num2}orLp/{num1} Sdh/{num2} Vc4/0 Vc12/{num3} E1orLp/{num1}Sonet/{num2} Sts/{num4} Vt1dot5/{num5}DS1orLaps/{num6} Vc4/0 Vc12/{num3}E1orLaps/{num6} Sts/{num4} Vt1dot5/{num5}DS1

Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = EDS1, EE1, DS1, andE1 {num2} = 0-n, where n is 1 less than thenumber of ports supported on the card typeused {num3} = multiple indexes 1-3, 1-7, 1-3{num4} = decimal number 0-11 {num5} = mul-tiple indexes 1-7, 1-3 {num6} = decimal num-ber 0-15999 If the status is set, the link hasbeen in an Loss of Signal (LOS) state for aminimum of 2 seconds. A clear is issued whenthe LOS condition has been cleared for a min-imum of 10 seconds.

Remedial Action Check the cabling between this port and thefar end port.



6.138 MSS_7011_05004

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type}/{num2}orLp/{num1} Sdh/{num2} Vc4/0 Vc12/{num3} E1 orLp/{num1}Sonet/{num2} Sts/{num4} Vt1dot5/{num5}DS1orLaps/{num6} Vc4/0 Vc12/{num3}E1orLaps/{num6} Sts/{num4} Vt1dot5/{num5}DS1

Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = EDS1, EE1, DS1, andE1 {num2} = 0-n, where n is 1 less than thenumber of ports supported on the card typeused {num3} = multiple indexes 1-3, 1-7, 1-3{num4} = decimal number 0-11 {num5} = mul-tiple indexes 1-7, 1-3 {num6} = decimal num-ber 0-15999 If the status is set, the link hasbeen in a Multiframe Remote Alarm Indication(RAI) state for a minimum of 2 seconds. Thefar end interface is complaining that it has lostMultiframe alignment. A clear is issued whenthe Multiframe RAI condition has been clearedfor a minimum of 10 seconds.

Remedial Action Check the configuration of both ports.



6.139 MSS_7011_05005

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type}/{num2}orLp/{num1} Sdh/{num2} Vc4/0 Vc12/{num3} E1orLp/{num1}Sonet/{num2} Sts/{num4} Vt1dot5/{num5}DslorLaps/{num6} Vc4/0 Vc12/{num3}E1orLaps/{num6} Sts/{num4} Vt1dot5/{num5}Dsl

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0-n, where n is 1less than the number of ports supported on thecard type used {num3} = multiple indexes 1-3,1-7, 1-3 {num4} = decimal number 0-11{num5} = multiple indexes 1-7, 1-3 {num6} =decimal number 0-15999 If the status is set,the link has been in a Multiframe Red state fora minimum of 2 seconds. A clear is issuedwhen the Multiframe Red condition has beencleared for a minimum of 10 seconds.

Remedial Action Check the configuration of both ports.



6.140 MSS_7011_05006

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type}/{num2}orLp/{num1} Sdh/{num2} Vc4/0 Vc12/{num3} E1orLp/{num1}Sonet/{num2} Sts/{num4} Vt1dot5/{num5}DslorLaps/{num6} Vc4/0 Vc12/{num3}E1orLaps/{num6} Sts/{num4} Vt1dot5/{num5}Dsl

Severity major

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0-n, where n is 1less than the number of ports supported on thecard type used {num3} = multiple indexes 1-3,1-7, 1-3 {num4} = decimal number 0-11{num5} = multiple indexes 1-7, 1-3 {num6} =decimal number 0-15999 If the status is set, ayellow alarm is being asserted on the port. Theyellow alarm is asserted because of voice ser-vices using this port, having connectivity prob-lems through the subnet, which could becaused by numerous reasons. A clear is is-sued when the yellow alarm is no longer beingasserted on the port. The yellow alarm is nolonger being asserted because the connectiv-ity problems of the voice services using thisport have been re-established.

Remedial Action The yellow alarm was asserted due to con-nectivity problems of the voice services usingthe port. This could be caused by two genericreasons. First, the operational state of thevoice services using the port in yellow alarmstate, should be checked to see if its enabled,



as well as the remote voice service that theyare connected to. If not, maintenance action isrequired to restore the services on the DS1/E1interface. If they are all enabled, connectivityproblems are occurring within the subnet.Trunks that carry the voice traffic through thesubnet should be investigated for problemsand rectified in order to restore connectivity ofthe voice services.



6.141 MSS_7011_05007

RNC Type • POC

• 9370 RNC

Component Lp/{num1} E1/{num2}orLp/{num1} Sdh/{num2}Vc4/{num3} Vc12/{num4} E1

Severity minor

cleared

Status set

clear

Detail {num1} = 0 - 15 {num2} = 0 - n, where n is 1less than the number of ports supported on thecard type used {num3} = 0 - n, where n de-pends on the SDH port type (0 for STM-1){num4} = multiple indexes 1-3, 1-7, 1-3 Thealarm occurs when the crc4mode of one of thetwo connected E1s is set to on, with the otherset to off. The alarm is raised and cleared im-mediately. The thresholds must be set to thesame value.

Remedial Action Check the configuration of the ports on bothends.



6.142 MSS_7011_05010

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type}/{num2}ORLp/{num1} Sdh/{num2} Vc4/0 Vc12/{num3} E1ORLp/{num1}Sonet/{num2} Sts/{num4} Vt1dot5/{num5}DS1ORLaps/{num6} Vc4/0 Vc12/{num3}E1ORLaps/{num6} Sts/{num4} Vt1dot5/{num5}DS1

Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {type} = DS1 and E1 {num2} =0-n, where n is 1 less than the number of portssupported on the card type used {num3} =multiple indexes 1-3, 1-7, 1-3 {num4} = decim-al number 0-11 {num5} = multiple indexes 1-7,1-3 {num6} = decimal number 0-15999 If thestatus is set, the link has entered an Unavail-able state. This condition is declared after 10consecutive Severely Errored Seconds (SES).A clear is issued after 10 consecutive secondsduring which no SES are counted. ForDS1/E1, a Severely Errored Second is asecond with 320 or more code violation errorevents or one or more SEF (Severely ErroredFrame) events.

Remedial Action Determine the cause of the errored secondsand fix the far end interface.



6.143 MSS_7011_05011

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {num1} = 1 - 15 {type} = DS1 and E1 {num2} =0 - n, where n is 1 less than the number ofports supported on the card type used If thestatus is set, the transmit clock for the port hasfailed as a consequence of a failure of the loc-ally generated asynchronous clock(Synchronous Residual Time Stamp (SRTS)mode. Under this condition the timing of thedata on the DS1/E1 line may not conform tothe appropriate standards. If the status isclear, the alarm indicates that the transmitclock for the port is no longer defective.

Remedial Action Follow the standard procedure for testing theFP, and if the alarm does not clear the defect-ive unit has to be replaced.



6.144 MSS_7011_05050

RNC Type • POC

• 9370 RNC

Component Lp/0 {type}/{num}

Severity warning

critical

cleared

Status set

clear

Detail {type} = EDS1 or EE1 {num} = 0 - 1 This alarmis set upon the provisioning of a BITS port ona CP card when either one or both CPs do notsupport BITS external timing. If the active CPdoes not support BITS external timing, thealarm is raised as critical. If the standby CPdoes not support BITS external timing or ifthere is no standby CP (i.e., single CP node),the alarm is raised as a warning message. Theoperational state of the port depends solely onwhether the active CP supports BITS externaltiming -- if the active CP supports BITS extern-al timing, the port is up and operational; if theactive CP does not support BITS external tim-ing, the port is disabled. The alarm is clearedwhen a card that supports BITS external tim-ing is inserted into the slot or the BITS port isdeleted.

Remedial Action Replace the card with one that supports BITSexternal timing.



6.145 MSS_7011_05051

RNC Type • POC

• 9370 RNC

Component Lp/0 Sets/{num}

Severity critical

cleared

Status set

clear

Detail {num} = 0 - 1 Severity critical/cleared for activeCP card; warning/cleared for standby CP cardThis alarm is set upon the provisioning of aSynchronous Equipment Timing Source (Sets)port on a CP card when either one or bothCPs do not support Sets. If the active CP doesnot support Sets, the alarm is raised as critical.If the standby CP does not support Sets or ifthere is no standby CP (i.e., single CP node),the alarm is raised as a warning message. Theoperational state of the port depends solely onwhether the active CP supports Sets -- if theactive CP supports Sets, the port is up and op-erational; if the active CP does not supportSets, the port is disabled. The alarm is clearedwhen a card that supports Sets is inserted intothe slot or the Sets port is deleted.

Remedial Action Replace the card with one that supports Sets.



6.146 MSS_7011_05100

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 type = DS3 andE3 If the status is set, a Loss Of Signal (LOS)condition has been present for at least 2seconds on the incoming line. An LOS condi-tion occurs when the port receives neithernegative nor positive pulses. A clear is issuedwhen no LOS condition has been detected for10 seconds.




6.147 MSS_7011_05101

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 type = DS3 andE3 If the status is set, an Loss Of Frame (LOF)condition has been present for at least 2seconds on the incoming line. An LOF condi-tion occurs when this port cannot frame to theincoming DS3 or E3 signal. A clear is issuedwhen this port has successfully framed the in-coming signal for 10 seconds. For DS3: A DS3far end SEF/AIS signal will be transmitted bythis port for the duration of the time the LOFcondition is present. For E3: In ITU-T G.751framing mode, an E3 far end SEF/AIS signalwill be transmitted by this port for the durationof the time the LOF condition is present. InITU-T G.832 framing mode, an E3 far end re-ceive failure (FERF) signal will be transmittedby this port for the duration of the time the LOFcondition is present.

Remedial Action Check the configuration of the far end port.



6.148 MSS_7011_05102

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 type = DS3 andE3 If the status is set, Alarm Indication Signal(AIS) defects have been detected for at least 2seconds on the incoming line. A clear is issuedwhen no AIS defects have been detected for10 seconds. For DS3: Receiving an AISmeans that the far end port has detected aproblem beyond it. AIS could be generated byDS3 cross-connects located between Multiser-vice Switch nodes. A DS3 far end SEF/AISsignal will be transmitted by this port for theduration of the time that AIS defects arepresent. For E3: Receiving an AIS means thatthe far end port has been put in the LOCKEDstate. In ITU-T G.751 framing mode, an E3 farend SEF/AIS signal will be transmitted by thisport for the duration of the time that AIS de-fects are present. In ITU-T G.832 framingmode, an E3 far end receive failure (FERF)signal will be transmitted by this port for theduration of the time that AIS defects arepresent.

Remedial Action Check the configuration and status of the farend port.



6.149 MSS_7011_05103

RNC Type • POC

• 9370 RNC


Severity minor

critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 {type} = DS3and E3 For DS3: When running in C-Bit Paritymode, the status is set to indicate that a farend alarm has been received over the Far EndAlarm and Control (FEAC) channel. A clear isissued when the alarm signal is no longer re-ceived over the FEAC channel. When not run-ning C-Bit Parity mode, the status is set to in-dicate that far end SEF/AIS defect indicatorshave been received for a minimum of 2seconds. A clear is issued when no far endSEF/AIS defect indicators have been detectedfor 10 seconds. For E3: In ITU-T G.751 fram-ing mode, the status is set to indicate that anE3 far end SEF/AIS signal has been receivedfor a minimum of 2 seconds. A clear is issuedwhen no far end SEF/AIS signal has been re-ceived for 10 seconds. In ITU-T G.832 framingmode, the status is set to indicate that an E3far end receive failure (FERF) signal has beenreceived for a minimum of 2 seconds. A clearis issued when no FERF signal has been re-ceived for 10 seconds.

Remedial Action Check the cabling between this port and thefar end port, and the configuration and statusof the far end port. If running in DS3 C-Bit Par-



ity mode, also check the CBIT component op-erational data.



6.150 MSS_7011_05104

RNC Type • POC

• 9370 RNC

Component Lp/{num1} DS3/{num2}

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 If the status isset, a DS3 Idle signal has been detected for aminimum of 2 seconds on the incoming line.The far end port has been locked and is notcurrently being used in operational testing. Aclear is issued when no DS3 Idle has been de-tected for 10 seconds.

Remedial Action Check the status of the far end port.



6.151 MSS_7011_05105

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 If the status isset, there is a mismatch with the CBIT paritymode between the near end port and far endport. It is probable that the near end port isprovisioned to support DS3 CBIT parity modeand the far end port is not. A clear is issuedwhen the far end port is provisioned to supportCBIT parity mode.

Remedial Action Check the configuration of the far end port tosee if DS3 CBIT parity mode is provisioned.



6.152 MSS_7011_05110

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 If the status isset, this port has received a request from thefar end to loopback the incoming DS3 signal.The far end port is currently under operationaltesting. Service on this port will be suspended.A clear is issued when this port has received arequest from the far end to stop looping the in-coming DS3 signal, or when the port is locked,or when CBIT parity mode is turned off.




6.153 MSS_7011_05111

RNC Type • POC

• 9370 RNC

Component Lp/{num1} DS3/0

Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 If the status is set, the DS3component has received a request from the farend to loopback an incoming DS1 tributary onthe DS3. The loopback request is caused bythe initiation of a remoteLoopThisTrib test atthe far end. This request can come from a C-bit Parity channel only. The affected DS1 com-ponent is taken out of service. This alarm willremain set as long as at least one DS1 tribu-tary is in loopback state. A clear is issuedwhen there are no more active DS1 loopbacksfrom the far end.

Remedial Action If the loopback is not expected, check the farend DS3/0 DS1/x Test component to see if aremoteLoopThisTrib test type is active. Theloopback can be removed at the near end bystopping the remoteLoopThisTrib test at thefar end. Alternatively, the loopback can be re-moved at the near end by Locking and thenUnlocking the affected DS1 component.



6.154 MSS_7011_05112

RNC Type • POC

• 9370 RNC

Component Lp/{num1} DS3/0

Severity minor

Status message

Detail {num1} = 1 - 15 The DS3 component receivesa tributary loopback request for an unprovi-sioned tributary or is aborting an existing DS3or DS1 cbit FEAC loopback.

Remedial Action This alarm is provided for information only.



6.155 MSS_7011_05120

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 type = DS3 andE3 If the status is set, the near end path hasentered an Unavailable state. This condition isdeclared after 10 consecutive SeverelyErrored Seconds (SESs). A clear is issuedafter 10 consecutive seconds with no SES. ForDS3: A SES is a second interval with morethan 44 Path Code Violations (parity/frame er-rors) or one or more SEF/AIS defects. For E3:In ITU-T G.751 framing mode, a SES is asecond interval with more than 22 Path CodeViolations (frame errors) or one or more SEF/AIS defects. In ITU-T G.832 framing mode, aSES is a second interval with more than 34Path Code Violations (frame errors or BIP-8errors) or one or more SEF/AIS defects.

Remedial Action Determine the cause of the errored secondsand fix the far end port.



6.156 MSS_7011_05121

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 If the status isset, the link has entered a CBIT Unavailablestate. This condition is declared after 10 con-secutive CBIT Severely Errored Seconds(CSESs). A clear is issued after 10 consecut-ive seconds with no CSES. A CSES is asecond interval with more than 44 CBIT PathCode Violations (CBIT parity errors) or one ormore SEF/AIS defects.




6.157 MSS_7011_05122

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 If the status isset, the link has entered a Far End Unavail-able state. This condition is declared after 10consecutive Far End Severely ErroredSeconds (FESESs) or when a Remote AlarmIndicator (RAI) is declared. A clear is issuedafter 10 consecutive seconds with no FESESand no RAI. A FESES is a second interval withmore than 44 Far End Code Violations(FEBEs) or one or more far end SEF/AIS de-fects. The occurrence of these events meansthat the far end does not receive properly whatthe local interface is transmitting to it.

Remedial Action Determine the cause of the far end erroredseconds and fix this port or the line between itand the far end.



6.158 MSS_7011_05130

RNC Type • POC

• 9370 RNC

Component Lp/{num1}

Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 If the status is set, one of theMultiport Aggregate Devices attached to theFP has a faulty power supply. This alarm willnot be set again if the other Multiport Aggreg-ate Devices connected to the FP develops apower supply problem. A clear is issued whenneither of the Multiport Aggregate Devices at-tached to the FP has a power supply problem.

Remedial Action Correct the problem as documented for theMultiport Aggregate Devices.



6.159 MSS_7011_05131

RNC Type • POC

• 9370 RNC

Component Lp/{num1}

Severity major

cleared

Status set

clear

Detail {num1} = 1 - 15 If the status is set, one of theMultiport Aggregate Devices attached to theFP has a link problem. Possible causes couldbe Loss of signal, Loss of framing or a re-ceived Remote Alarm Indication in the signal.This alarm will not be set again if the otherMultiport Aggregate Devices connected to theFP develops a link problem A clear is issuedwhen neither of the Multiport AggregateDevices attached to the FP has a link problem.

Remedial Action Check cabling between Multiport AggregateDevices and FP.



6.160 MSS_7011_05200

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 {type} = SON-ET and SDH If the status is set, a Loss Of Sig-nal (LOS) condition has been present for atleast 2 seconds on the incoming line, or theLOS defect is present when the criteria forLOF failure declaration have been met. De-claration of an LOS failure clears any existingLOF failure. A clear is issued when no LOScondition has been present for a minimum of10 seconds. If an LOF condition exists whenthe LOS is cleared, the LOF will be declaredimmediately. Note: An LOS condition can alsobe caused by saturating the optical receiverwith too strong a signal.

Remedial Action Check the cabling between this port and thefar end port. Verify that the strength of the sig-nal is within specifications.



6.161 MSS_7011_05201

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 {type} = SON-ET and SDH If the status is set, an Loss OfFrame (LOF) condition has been present for atleast 2 seconds on the incoming line. An LOFcondition occurs when this port cannot frameto the incoming SONET or SDH signal. A clearis issued when this port has successfullyframed the incoming signal for a minimum of10 seconds. LOF is also cleared when an LOSdefect is declared.

Remedial Action Check the configuration of the far end port andthe section statistics.



6.162 MSS_7011_05202

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 {type} = SON-ET and SDH If the status is set, Line Alarm In-dication Signal (L-AIS) defects have been de-tected for a minimum of 2 seconds on the in-coming line. The L-AIS alarm is used to alertdownstream equipment that a failure has beendetected or that the port transmitting L-AIS hasbeen locked. A clear is issued when no L-AISdefects have been detected for a minimum of10 seconds.




6.163 MSS_7011_05203

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 {type} = SON-ET and SDH If the status is set, this port is re-ceiving the Line Remote Defect Indicator(L-RDI). L-RDI is transmitted by the far endwhen it has been detecting L-AIS defects forsome period of time. A clear is issued when noL-RDI defects have been detected for 10seconds.

Remedial Action Check the cabling between this port and thefar end port, and the configuration and statusof the far end port.



6.164 MSS_7011_05204

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 {type} = SON-ET and SDH If the status is set, a Sonet/Sdhport provisioned to act as a transmit clock ref-erence has received the code "do not use forsynchronization" in the S1 byte (in the SON-ET/SDH line overhead) for 2.5 +/- 0.5seconds. A port is acting as a transmit clockreference if: it is provisioned with a clocking-Source of line, orit is provisioned with a clock-ingSource of module and is being used by theNetworkSynchronization component as clockreference. A clear is issued when the "do notuse for synchronization" code is not receivedfor 10 +/- 0.5 seconds, or when the port is nolonger provisioned to act as a transmit clockreference.

Remedial Action This alarm is caused by the far end Sonet/Sdhport is transmitting an S1 value of "do not usefor synchronization" . This is most likelycaused by a loss of synchronization to the farend port"™s provisioned transmit clockingsource. Check the provisioning and operation-al state of the far end SONET or APS equip-ment.



6.165 MSS_7011_05210

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 {type} = SON-ET and SDH If the status is set, this port hasentered an Unavailable state. This condition isdeclared at the onset of 10 consecutive LineSeverely Errored Seconds (L-SESs). A clear isissued at the onset of 10 seconds with no L-SES. A L-SES is a second interval with morethan 32 Line Code Violations (BIP-24 errors)or one or more L-AIS defects.




6.166 MSS_7011_05211

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 {type} = SON-ET or SDH If the status is set, this port hasentered a Far End Line Unavailable state. Thiscondition is declared at the onset of 10 con-secutive Far End Line Severely ErroredSeconds (FEL-SESs). A clear is issued after10 consecutive seconds with no FEL-SES. AFEL-SES is a second interval with more than32 Far End Line Code Violations (FEBE er-rors) or one or more line RDI defects. The oc-currence of these events means that the farend does not receive properly what the localinterface is transmitting to it.




6.167 MSS_7011_05250

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type1}/{num2}{type2}/0Laps/{num3} {type2}/0 orPbg/{num4}sts/0

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - n, where n is oneless than the number of ports on the card.{num3} = 0 - 15999 {num4} = 0 - 15999 {type1}= SONET or SDH {type2} = Path or STS orVC4 If the status is set, a Loss Of Pointer(LOP) condition has been present for a minim-um of 2 seconds on the incoming line. An LOPfailure indicates that the interface is no longerdetecting valid STS Payload Envelope (SPE)pointers. A clear is issued when no LOP condi-tion has been present for a minimum of 10seconds, or when an incoming P-AIS defect isdetected.




6.168 MSS_7011_05251

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - n, where n is oneless than the number of ports on the card.{num3} = 0 - 15999 {num4} = 0 - 15999 {type1}= SONET or SDH {type2} = Path or STS orVC4 If the status is set, a Path AIS (P-AIS)condition has been present for a minimum of 2seconds on the incoming line. A P-AIS signalis used to alert downstream equipment that afailure has been detected or that the Path/Sts/Vc4 component transmitting P-AIS hasbeen locked. A clear is issued when no P-AISsignal is detected for 10 seconds.




6.169 MSS_7011_05252

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - n, where n is oneless than the number of ports on the card.{num3} = 0 - 15999 {num4} = 0 - 15999 {type1}= SONET or SDH {type2} = Path or STS orVC4 If the status is set, Path RDI (P-RDI) de-fects have been detected for a minimum of 2seconds on the incoming line. The P-RDI sig-nal is used by the far end to indicate that LOPor P-AIS defects, or an LCD state have beendetected for some period of time. A clear is is-sued when no P-RDI defects have been detec-ted for 10 seconds.




6.170 MSS_7011_05253

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - n, where n is oneless than the number of ports on the card.{num3} = 0 - 15999 {num4} = 0 - 15999 {type1}= SONET or SDH {type2} = Path or STS orVC4 If the status is set, this port is receivingan unexpected Path Signal Label. The PathSignal Label is used to indicate the contentand format of the STS SPE. Expected PathSignal Labels are 0x13, the code for ATMMapping, and 0x01, the code for Equipped. Aclear is issued when the correct Path SignalLabel has been detected for 10 seconds. APath Signal Label Mismatch is not reportedwhen receiving P-AIS or LOP defects.




6.171 MSS_7011_05254

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - n, where n is oneless than the number of ports on the card.{num3} = 0 - 15999 {num4} = 0 - 15999 {type1}= SONET or SDH {type2} = Path or STS orVC4 If the status is set, this port is receivingan unexpected Path Label Mismatch. ThePath Label Mismatch is used to indicate thecontent and format of the STS SPE when thereceived C2 byte is not 0x0 and not 0x13. Theexpected Path Signal Labels are 0x13, thecode for ATM Mapping, and 0x01, the code forEquipped. A clear is issued when the correctPath Signal Label has been detected for 10seconds. A Path Label Mismatch is not repor-ted when receiving P-AIS or LOP defects.




6.172 MSS_7011_05255

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - n, where n is oneless than the number of ports on the card.{num3} = 0 - 15999 {num4} = 0 - 15999 {type1}= SONET or SDH {type2} = Path or STS orVC4 If the status is set, this port is receivingan unexpected Path Unequipped. The PathUnequipped is used to indicate the contentand format of the STS SPE when the receivedC2 byte is 0x0. The expected Path Signal La-bels are 0x13, the code for ATM Mapping, and0x01, the code for Equipped. A clear is issuedwhen the correct Path Signal Label has beendetected for 10 seconds. A Path Label Mis-match is not reported when receiving P-AIS orLOP defects.

Remedial Action Check the configuration and status of the farend port (for example, the path is not provi-sioned).



6.173 MSS_7011_05256

RNC Type • POC

• 9370 RNC

Component Lp/{num1} Sonet/{num2} Sts/{num3}, Lp/{num1} Sdh/{num2} Vc4/0, Lp/{num1} Sdh/{num2} Vc4/0 Vc12/{1-3, 1-7, 1-3}Laps/{num4}Sts/{num3}, Laps/{num4} Sdh/{num2} Vc4/0,Laps/{num4} Sdh/{num2} Vc4/0 Vc12/{1-3,1-7, 1-3}orPbg/{num4} Sts/{num3}

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - n, where n is oneless than the number of ports on the card.{num3} = 0 - 11 {num4} = 0 - 15999 If thestatus is set, the received Path Trace Identifierin the J1 or J2 byte does not match the expec-ted Path Trace. The alarm is set when the mis-match lasts for more then 2.5 sec. A clear isissued when the correct Path Trace Identifierhas been detected for 10 seconds. A P-TIM isnot reported when receiving P-AIS or LOP de-fects.

Remedial Action Check he provisioning of the Path Trace onboth ends of the connection. Check the cross-connections.



6.174 MSS_7011_05260

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type1}/{num2} {type2}/{0}|Additional (optional): Laps/{num3} {type2}/0;Pbg/{num4} sts/0; Lp/{num1} {Sonet}/{num2}{Sts}/{num5} {Vt1dot5}/{l,m}; Laps/{num3}{Sts}/{num5} {Vt1dot5}/{l,m} Additional(optional): Lp/{num1} {Sdh}/{num2} {VC4/0}{VC12}/{k,l,m}; Laps/{num3} {VC4/0}{VC12}/{k,l,m}

Severity minor

cleared

Status set

clear

Detail {k} = 1 - 3 {l} = 1 - 7 {m} = 1 - 3 {num1} = 1 - 15{num2} = 0 - n, where n is one less than thenumber of ports on the card. {num3} = 0 -15999 {num4} = 0 - 15999 {num5} = 0 - 3{type1} = SONET or SDH {type2} = Path orSTS or VC4 If the status is set, this port hasentered an Unavailable state. This condition isdeclared at the onset of 10 consecutive PathSeverely Errored Seconds (P-SESs). A clear isissued at the onset of 10 seconds with no P-SES. A P-SES is a second interval with morethan 16 Path Code Violations (BIP-8 errors) orone or more P-LOP or P-AIS defects.




6.175 MSS_7011_05261

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type1}/{num2} {type2}/{0}|Additional (optional): Laps/{num3} {type2}/0;Pbg/{num4} sts/0; Lp/{num1} {Sonet}/{num2}{Sts}/{num5} {Vt1dot5}/{l,m}; Laps/{num3}{Sts}/{num5} {Vt1dot5}/{l,m} Additional(optional): Lp/{num1} {Sdh}/{num2} {VC4/0}{VC12}/{k,l,m}; Laps/{num3} {VC4/0}{VC12}/{k,l,m}

Severity minor

cleared

Status set

clear

Detail {k} = 1 - 3 {l} = 1 - 7 {m} = 1 - 3 {num1} = 1 - 15{num2} = 0 - n, where n is one less than thenumber of ports on the card. {num3} = 0 -15999 {num4} = 0 - 15999 {num5} = 0 - 3{type1} = SONET or SDH {type2} = Path orSTS or VC4 If the status is set, this port hasentered a Far End Path Unavailable state.This condition is declared at the onset of 10consecutive Far End Path Severely ErroredSeconds (FEP-SESs). A clear is issued after10 consecutive seconds with no FEP-SES. AFEP-SES is a second interval with more than16 Far End Path Code Violations (path FEBEerrors) or one or more path RDI defects. Theoccurrence of these events means that the farend does not receive properly what the localinterface is transmitting to it.




6.176 MSS_7011_05270

RNC Type • POC

• 9370 RNC

Component {type}/{num}

Severity minor

cleared

Status set

clear

Detail {type} = Aps or Laps {num} = 0 - 15999 If thestatus is set, a Protection Switching Byte de-fect has persisted for 2.5 +/- 0.5 seconds. AProtection Switching Byte defect is declaredwhen either an inconsistent APS byte or an in-valid code is detected. An inconsistent APSbyte occurs when no three consecutive K1bytes (in the SONET/SDH line overhead) inthe last 12 successive frames are identical,starting with the last frame that contains a pre-viously consistent byte. An invalid code occurswhen the incoming K1 byte contains an un-used code, a code irrelevant to the specificswitching operation, or an invalid channelnumber, in three consecutive frames. A clearis issued when the Protection Switching Bytedefect is absent for 10 +/- 0.5 seconds.

Remedial Action This alarm indicates that the far end equip-ment may be defective. Check the provisioningand operational state of the far end SONET orAPS equipment.



6.177 MSS_7011_05271

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {type} = Aps or Laps {num} = 0 - 15999 If thestatus is set, a Channel Mismatch defect haspersisted for 2.5 +/- 0.5 seconds. A ChannelMismatch defect is declared when the channelnumber transmitted in the K1 byte (in theSONET/SDH line overhead) does not matchthe channel number received in the K2 byte for50 ms. A clear is issued when the ChannelMismatch defect is absent for 10 +/- 0.5seconds.

Remedial Action This alarm indicates that the far end equip-ment may be defective. Check the provisioningand operational state of the far end SONET orAPS equipment.



6.178 MSS_7011_05272

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {type} = Aps or Laps {num} = 0 - 15999 If thestatus is set, an APS Mode Mismatch defecthas persisted for 2.5 +/- 0.5 seconds. An APSMode Mismatch defect is declared when either(1) an Aps/Laps component (which uses for1+1 protection switching) receives an indica-tion from the far end in the received K2 byte(SONET line overhead only) that is provi-sioned for 1:n, or (2) when an Aps/Laps com-ponent provisioned for bidirectional switchingreceives an indication from the far end in thereceived K2 byte that it is provisioned for uni-directional switching. A clear is issued whenthe APS Mode Mismatch defect is absent for10 +/- 0.5 seconds.

Remedial Action Check the provisioning of the near and far endAPS systems, ensure they both use the sameprovisioned architecture (1+1) and mode(unidirectional or bidirectional).



6.179 MSS_7011_05273

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {type} = Aps or Laps {num} = 0 - 15999 If thestatus is set, a Far-End Protection-Line defecthas persisted for 2.5 +/- 0.5 seconds. A Far-End Protection-Line defect is declared whenthe Aps/Laps component receives three con-secutive K1 bytes (in the SONET/SDH lineoverhead) with the code indicating Signal Failon the protection line. A clear is issued whenthe Far-End Protection-Line defect is absentfor 10 +/- 0.5 seconds.

Remedial Action Correct the failure on the Sonet/Sdh compon-ent used as the protection line.



6.180 MSS_7011_05274

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {type} = Aps or Laps {num} = 0 - 15999 f thestatus is set, an APS request other than doNo-tRevert or noRequest (or reverseRequest inbidirectional switching), has been sent byeither the near end or the far end in the K1byte (in the SONET/SDH line overhead). Notethat if the Aps/Laps component is provisionedfor unidirectional switching the far end requestwill not be monitored and will not factor intothis alarm. The alarm's text will indicate thehighest priority request being sent by the nearor far end. Thereafter, every time the highestpriority request changes to a new value (notone of doNotRevert, noRequest or reverseRe-quest) the alarm will be reissued indicating thenew request. A clear is issued immediatelywhen the APS requests being sent by both thenear and far end change to either doNotRevertor noRequest.

Remedial Action This alarm is informational in nature, and indic-ates that there is activity on the SONET/SDHAPS channel which may restrict the Aps/Lapscomponents ability to deal with line failures. Ifthe request is a signalFail or signalDegrade,the condition should be corrected at the SON-ET/SDH level. If the request is an operatorcommand the Aps can be restored to full un-



restricted operation by clearing the command.



6.181 MSS_7011_05275

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {type} = Aps or Laps {num} = 0 - 15999 If thestatus is set, the Aps/Laps component"™snearEndRxActiveChannel has experienced asignal failure (SF). A clear is issued when theSF becomes absent from the Aps/Laps com-ponent"™s nearEndRxActiveChannel.

Remedial Action This alarm indicates that both the working andprotection line are unavailable. Check for fail-ures of the Sonet/Sdh components provi-sioned as the working and protection lines.Display the Aps/Laps component"™s opera-tional attributes and check for near and far endcommand requests which may be forcing theAps to only use one of its lines, for instancethe lockoutOfProtection command. If the re-quest is from the near end the "#clear"™ verbcan be used to clear the command. If the re-quest is from the far end the command canonly be cleared on the far end equipment.



6.182 MSS_7011_05276

RNC Type • POC

• 9370 RNC

Component Laps/{x}

Severity minor

cleared

Status set

clear

Detail {x} = 0 - 15999 If the status is set, a primarysection mismatch condition has been detec-ted. This condition occurs when the primarysection indicated in the received K2 byte doesnot equal the primary section transmitted inthe K2 byte. If this condition occurs and theprimary section transmitted in the K2 byte isset to two, the local end changes its primarysection to one and re-evaluates the position ofthe selector and the transmitted K1 byte. If thiscondition occurs and the primary section trans-mitted in the K2 byte is set to one, the alarmremains until the far end changes its channeltransmitted in the K2 byte. A clear is issuedwhen the K2 channel numbers match for 50milliseconds.

Remedial Action No action is required on the local end becausethe local software automatically swaps theprimary section if the local end does not havethe primary section as one. Check the far endconfiguration and/or support for automatichandling of primary section mismatch.



6.183 MSS_7011_05277

RNC Type • POC

• 9370 RNC

Component LpP/{lp_x}/{lp_y}

Severity warning

Status message

Detail {lp_x} = 0 - 15 {lp_y} = 0 - 15 When you usethe LAPS feature, there is a possible fifo cor-ruption which will cause traffic going throughthe crossconnect to become faulty. All Lapspairs on the 2 cards will experience pathalarms when using the traffic that is passingthrough the crossconnect. The use of lpP/X.Ycomponent is to show that the problem is onthe card pair and not only on one Laps com-ponent. This alarm is to warn the user that afault was detected and a recovery procedurewas performed. A small traffic outage({ 50ms)will occur if the traffic going through thecrossconnect is being used.

Remedial Action None. The software detects the fault and re-covers the traffic.



6.184 MSS_7011_05278

RNC Type • POC

• 9370 RNC

Component Laps/{instance}

Severity minor

cleared

Status set

clear

Detail {instance} = 0- 15999 If the status is set, theLaps component configured with the Y-Protection protocol has detected that thestandby line is unavailable. A clear is issuedwhen the standby line becomes enabled andLaps can provide protection.

Remedial Action Correct the failure on the Sonet/Sdh compon-ent used as the standby line.



6.185 MSS_7011_05279

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {instance} = 0- 15999 If the status is set, theLaps component configured with the yProtec-tion protocol has detected that the active lineis unavailable for 2.5 +/- 0.5 seconds and be-comes disabled. A clear is issued when theactive line failure has been absent for 10 +/-0.5 seconds and Laps becomes enabled.

Remedial Action Check for failures of the Sonet/Sdh compon-ents provisioned on the active lines.



6.186 MSS_7011_05280

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {instance} = 0- 15999 If the status is set, theLaps component configured with the Y-Protection protocol is indicating that the activeport is receiving RDI-L from the far-end equip-ment for 2.5 +/- 0.5 seconds. A clear is issuedwhen the RDI-L has been absent from the act-ive port for 10 +/- 0.5 seconds.

Remedial Action Check for failures of the Sonet/Sdh compon-ents provisioned on the receive side of the far-end equipment.



6.187 MSS_7011_05281

RNC Type • POC

• 9370 RNC

Component Laps/{instance} CrossConnect

Severity critical

cleared

Status set

clear

Detail {instance} = 0- 15999 There are two types forthis alarm: (1) Facility Defect: This means thatthe traffic going trough the Crossconnect (Xc)cable is faulty with either bit errors, LOS, cablepulled, or other communication problemsbetween the two cards in the Laps pair. A Fa-cility Defect alarm is raised. (2) Cable Mis-placed: This alarm would be raised when theCrossConnect cable is attached to two cardsthat are not provisioned in the Laps pair (thatis, if you provision LAPS between cards 2 and3 and you attach the cable between card 3and 4, the alarm would raise "A Cable Mis-placed" alarm). The alarm is overwritten by afacility defect alarm or cleared when the cor-rect card pairs are provisioned.

Remedial Action For a "Facility Defect" alarm, the Xc cableshould be replaced. If after replacing the cablethe error still exists, it may be a card hardwareissue and the card should be replaced. For a"Cable Misplaced" alarm, the Xc cable shouldbe inserted into the correct card pair or Lapsshould be reprovisioned with the correct cardpair.



6.188 MSS_7011_05290

RNC Type • POC

• 9370 RNC

Component Lp/{num1} Sdh/{num2} Vc4/0Vc12/{num3}orLp/{num1} Sonet/{num2} Sts/{num4} Vt1dot5/{num5}orLaps/{num6} Vc4/0Vc12/{num3}orLaps/{num6} Sts/{num4}Vt1dot5/{num5}

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0-n, where n is 1less than the number of ports supported on thecard type used {num3} = multiple indexes 1-3,1-7, 1-3 {num4} = decimal number 0-11{num5} = multiple indexes 1-7, 1-3 {num6} =decimal number 0-15999 If the status is set,Low Order Path Remote Error Indicator(LP-REI) defects have been detected for atleast 2 seconds on the incoming line. The LP-REI signal is used by the far end to indicatethat one or more BIP-2 errors have been de-tected. A clear is issued when no LP-REI de-fects have been detected for at least 10seconds.

Remedial Action Check the status of the cable. Also check thestatus of the far end port.



6.189 MSS_7011_05291

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0-n, where n is 1less than the number of ports supported on thecard type used {num3} = multiple indexes 1-3,1-7, 1-3 {num4} = decimal number 0-11{num5} = multiple indexes 1-7, 1-3 {num6} =decimal number 0-15999 If the status is set,Low Order Path Remote Failure Indicator(LP-RFI) conditions have been detected for atleast 2 seconds on the incoming line. The LP-RFI signal is used by the far end to declare afailure, which is a defect that persists beyondthe maximum time allocated to the transmis-sion system protection mechanisms. A clear isissued when no LP-RFI conditions have beendetected for 10 seconds.




6.190 MSS_7011_05292

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0-n, where n is 1less than the number of ports supported on thecard type used {num3} = multiple indexes 1-3,1-7, 1-3 {num4} = decimal number 0-11{num5} = multiple indexes 1-7, 1-3 {num6} =decimal number 0-15999 If the status is set,Low Order Path Remote Defect Indicator(LP-RDI) defects have been detected for atleast 2 seconds on the incoming line. The LP-RDI signal is used by the far end to indicatethat a connectivity defect such as Low OrderPath Unequipped (LP-UNEQ) or Low OrderPath Trace Identifier Mismatch (LP-TIM), or aserver defect such as Tributary Unit Alarm In-dication Signal (TU-AIS) or Tributary Unit Lossof Pointer (TU-LOP) has been detected. Aclear is issued when no LP-RDI detects havebeen detected for 10 seconds.

Remedial Action Check the configuration and the status of thefar end port.



6.191 MSS_7011_05293

RNC Type • POC

• 9370 RNC

Component Lp/{num1} Sdh/{num2} Vc4/0 Vc12/{num3}

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0-n, where n is 1less than the number of ports supported on thecard type used {num3} = multiple indexes 1-3,1-7, 1-3 {num4} = decimal number 0-11{num5} = multiple indexes 1-7, 1-3 {num6} =decimal number 0-15999 If the status is set,Low Order Path Alarm Indicating Signal(LP-AIS) defects have been detected for atleast 2.5 +/- 0.5 seconds on the incoming line.The LP-AIS signal indicates that an upstreamdefect has been detected. A clear is issuedwhen no LP-AIS detects have been detectedfor 10 +/- 0.5 seconds.




6.192 MSS_7011_05294

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0-n, where n is 1less than the number of ports supported on thecard type used {num3} = multiple indexes 1-3,1-7, 1-3 {num4} = decimal number 0-11{num5} = multiple indexes 1-7, 1-3 {num6} =decimal number 0-15999 If the status is set,Low Order Path Bit Interleaved Parity (BIP-2)defects have been detected for a minimum of2 seconds on the incoming line. The Low Or-der Path BIP-2 alarm is issued if the calculatedBIP-2 does not equal to the received BIP-2. Aclear is issued when no Low Order Path BIP-2detects have been detected for 10 seconds.

Remedial Action Check the status of the cable. Also check thestatus of the far end port.



6.193 MSS_7011_05295

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0-n, where n is 1less than the number of ports supported on thecard type used {num3} = multiple indexes 1-3,1-7, 1-3 {num4} = decimal number 0-11{num5} = multiple indexes 1-7, 1-3 {num6} =decimal number 0-15999 If the status is set, aTributary Unit Loss of Pointer (TU-LOP) condi-tion has been detected for a minimum of 2seconds on the incoming line. The TU-LOPsignal indicates that an invalid pointer state isdetected in the TU pointer. A clear is issuedwhen no TU-LOP detects have been detectedfor 10 seconds.




6.194 MSS_7011_05296

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0-n, where n is 1less than the number of ports supported on thecard type used {num3} = multiple indexes 1-3,1-7, 1-3 {num4} = decimal number 0-11{num5} = multiple indexes 1-7, 1-3 {num6} =decimal number 0-15999 If the status is set, aLow Order Path Unequipped (LP-UNEQ) con-dition has been detected for a minimum of 2seconds on the incoming line. The LP-UNEQsignal indicates that an unequipped defect hasbeen detected. A clear is issued when no LP-UNEQ detects have been detected for 10seconds.




6.195 MSS_7011_05297

RNC Type • POC

• 9370 RNC

Component Lp/{num1} Sdh/{num2} Vc4/0Vc12/{num3}orLaps/{num6} Vc4/0Vc12/{num3}

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0-n, where n is 1less than the number of ports supported on thecard type used {num3} = multiple indexes 1-3,1-7, 1-3 {num6} = decimal number 0-15999 Ifthe status is set, a Tributary Unit Trace Identi-fication Mismatch (TU-TIM) condition has beendetected for a minimum of 2 seconds on theincoming line. The TU-TIM signal indicatesthat the received trace identification does notmatch the provisioned value. A clear is issuedwhen no TU-TIM detects have been detectedfor 10 seconds.

Remedial Action Check the far end port to ensure that the cor-rect equipment is connected. Also check if theprovisioned value is correct.



6.196 MSS_7011_05300

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 1 type = JT2 Ifthe status is set, a Loss Of Signal (LOS) con-dition has been present for a minimum of 2seconds on the incoming line. An LOS condi-tion occurs when the port receives neithernegative nor positive pulses. A clear is issuedwhen no LOS condition has been detected for10 seconds.




6.197 MSS_7011_05301

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 1 type = JT2 Ifthe status is set, an Loss Of Frame (LOF) con-dition has been present for a minimum of 2seconds on the incoming line. An LOF condi-tion occurs when this port cannot synchronizeto the incoming JT2 frame. A clear is issuedwhen this port has successfully framed the in-coming signal for 10 seconds. Whilst the portis in the LOF alarm state, a far end RAI defectindicator is transmitted on the outgoing JT2line.




6.198 MSS_7011_05302

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 1 type = JT2 Ifthe status is set, Physical Alarm Indication Sig-nal (AISPhys) defects have been detected fora minimum of 2 consecutive seconds on theincoming line. A clear is issued when no Phys-ical AIS defects have been detected for 10consecutive seconds. Receiving an AISmeans that the far end port has lost the capab-ility to transmit valid JT2 frames or is hasentered an adminState of Locked. Whilst therxAisPhysicalAlarm is set, a far end RAI defectindicator is transmitted on the outgoing JT2line for the duration of the alarm condition.




6.199 MSS_7011_05303

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 1 type = JT2 Ifthe status is set, Payload Alarm Indication Sig-nal (AISPayld) defects have been detected fora minimum of 2 consecutive seconds on theincoming line. A clear is issued when no Pay-load AIS defects have been detected for 10consecutive seconds. Receiving a PayloadAIS means that the far end port has lost thecapability to transmit valid JT2 frame pay-loads. The Payload AIS is defined as a bit ar-ray of the frame payload in which all binarybits are set to "#1"™.




6.200 MSS_7011_05304

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 1 type = JT2 Ifthe status is set, then the far end RemoteAlarm Indication (RAI) defect indicators havebeen received. This is indicated immediatelyand remains present for a minimum of 1second. A clear is indicated when no far endRAI defect indicators are detected.

Remedial Action Check the cabling between this port and thefar end port, and the configuration and statusof the far end port.



6.201 MSS_7011_05400

RNC Type • POC

• 9370 RNC

Component Lp/{lpNumber} Ethernet/{port}

Severity critical

cleared

Status set

clear

Detail {lpNumber} = 1- 15 {port} = 0 - 7 If the status isset, the port has lost synchronization with theEthernet signal on the incoming line. Declara-tion of the Loss of Synchronization failureclears any existing Auto-negotiation or RemoteLink Failure alarms. Declaration of the alarmmay also be a result of the heartbeat signalloss. A clear is issued when synchronizationhas been acquired. The clearing of the alarmmay be delayed by up to 1 second if an inter-mittent fault is detected.

Remedial Action Check the cabling of the local and far enddevices.



6.202 MSS_7011_05401

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {lpNumber} = 1 - 15 {port} = 0 - 7 If the statusis set, the port has failed to Auto-Negotiate acommon set of capabilities with the link part-ner. A clear is issued when Auto-negotiationhas been successful or synchronization is lost.The clearing of the alarm may be delayed byup to 1 second if an intermittent fault is detec-ted.

Remedial Action Check the capability and possible configura-tion of the local and far end devices.



6.203 MSS_7011_05402

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {lpNumber} = 1- 15 {port} = 0 - 7 If the status isset, the far end device has signaled that thelink is offline. A clear is issued when the farend device signals that the link is no longeroffline or synchronization is lost. The clearingof the alarm may be delayed by up to 1second if an intermittent fault is detected.

Remedial Action Check the status of the far end device.



6.204 MSS_7011_05403

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {lpNumber} = 2- 15 {port} = 0 - 3 If the status isset, the far end device has signaled a remotelink failure. A clear will be issued when the farend device signals that the remote link failurehas cleared or synchronization is lost. Theclearing of the alarm may be delayed by up to10 seconds if an intermittent fault is detected.

Remedial Action Check the cabling of the far end device.



6.205 MSS_7011_05480

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type}/{num2} Om

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15. Is the LP number {type} =Ethernet, Sonet or SDH {num2} = 0 - n, wheren is one less than the number of ports on thecard If the status is set, the alarm may haveresulted for any of the following reasons: theType attribute does not match the optical mod-ule installed on this port. The actual opticalmodule that is installed is displayed in the at-tribute insertedType.there is an internal errorwith the devicethe inserted optical module typeor vendor is not approved A clear is issuedwhen the user provisions the attribute correctlywith the optical module. The optical module isdetermined by the operational attribute inser-tedType. In case of an internal error or vendornot allowed failure, a clear is issued when theoptical module is replaced.

Remedial Action Check the configuration of the local device orreplace the optical module if possible.



6.206 MSS_7011_05501

RNC Type • POC

• 9370 RNC

Component Lp/{num1} {type2}/{num2} {type3}/{num3}VC12/{num4} {type1}

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - n, where n is oneless than the number of ports supported on thecard type used. {num3} = 0 - n, where n de-pends on the SDH port type (0 for STM-1){num4} = multiple indexes 1-3, 1-7, 1-3 {type1}= DS3, E3, DS1 and E1. {type2} = SONET andSDH. {type3} = Path or STS or VC4 If thestatus is set, this port has been in a Loss ofCell Delineation state for Tact seconds, whereTact is the alarmActDelay attribute of theCELL component. A clear will be issued whenthe Loss of Cell Delineation state has not beenpresent for 10 consecutive seconds. For DS3and E3, in direct mapping mode, Loss of CellDelineation occurs when the interface is nolonger able to identify ATM cell boundaries. InPLCP mapping mode, a Loss of Cell Delin-eation occurs when the interface is no longerable to identify PLCP frame boundaries.

Remedial Action Check configuration of the far end port.



6.207 MSS_7011_05601

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {type} = DS3 and E3 {num2} =0 - 2 If the status is set, the link has entered aPLCP Far End Unavailable state. This condi-tion is declared upon declaration of a PLCPRAI alarm state. A clear is issued when thePLCP RAI alarm state is exited. A PLCP RAIalarm state is entered when a 10 consecutivePLCP RAI bits are high in the incoming PLCPdata stream, and cleared when 10 consecutivePLCP RAI bits are low on the incoming line, orwhen PLCP mode is disabled.

Remedial Action Check the cabling and configuration of the farend port.



6.208 MSS_7011_05602

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {type} = DS3 and E3 {num2} =0 - 2 If the status is set, the link has entered aPLCP Near End Unavailable state. This condi-tion is declared upon declaration of a PLCPLOF alarm state. A clear is issued when thePLCP LOF alarm state is exited. A PLCP LOFalarm state is entered when this port is notable to frame the incoming PLCP signal for 2seconds, and exited when the port success-fully frames the incoming PLCP signal for 10seconds, or when PLCP mode is disabled.

Remedial Action Check configuration of far end port.



6.209 MSS_7011_05603

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {num1} = 1 - 15 {type} = DS3 and E3. {num2}= 0 - 2 If the status is set, this port has entereda PLCP LOF state. A PLCP LOF state isentered when the port cannot frame to the in-coming PLCP signal for 2 seconds. A clear isissued when PLCP LOF state is exited, whichoccurs when PLCP framing is recovered for 10seconds or when PLCP is disabled. A PLCPRAI signal will be transmitted by this port forthe duration of the PLCP LOF state.

Remedial Action Check configuration of this port and the farend port.



6.210 MSS_7011_05604

RNC Type • POC

• 9370 RNC


Severity minor

major

cleared

Status set

clear

Detail {num1} = 1 - 15 {type} = DS3 and E3 {num2} =0 - 2 If the status is set, this port has entered aPLCP RAI state. A PLCP RAI state is enteredwhen the port receives ten consecutive highPLCP RAI bits on the incoming line. A clear isissued when the PLCP RAI state is exited,which occurs when the port receives ten con-secutive low PLCP RAI bits on the incomingline, or when PLCP mode is disabled. ThePLCP RAI signal will be transmitted by the farend port while it is in a PLCP LOF state.




6.211 MSS_7011_05701

RNC Type • POC

• 9370 RNC

Component Lp/{num1} E3/{num2}

Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 If the status isset, the far end port has entered a G832 Un-available state. A G832 Far End Unavailablestate is entered after 10 consecutive G832 FarEnd Severely Errored Seconds. A G832 FarEnd Severely Errored Second (FESES) iscounted during second intervals containingmore than 34 Far End Coding Violations orone or more FERF defects. A clear is issuedwhen the G832 Far End Unavailable state isexited, which occurs after 10 consecutiveseconds where no FESES are counted.




6.212 MSS_7011_05702

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 If the status isset, this port has entered an G832 UnexpectedPayload Type state. A G832 Unexpected Pay-load Type state is entered when the payloadtype in the received E3 signal fails to agreewith the expected payload type for a period of2 seconds. A clear is issued when the G832Unexpected Payload Type state is exited,which occurs when the received payload typeagrees with the expected payload type for aperiod of 10 seconds.




6.213 MSS_7011_05703

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - 2 If the status isset, this port has entered a G832 Trail TraceMismatch state. A G832 Trail Trace Mismatchstate is entered when the trail trace accesspoint identifier in the received E3 signal fails toagree with the expected trail trace accesspoint identifier for a period of 2 seconds. Aclear is issued when the G832 Trail Trace Mis-match state is exited, which occurs when thereceived trail trace access point identifieragrees with the expected trail trace accesspoint identifier for a period of 10 seconds.




6.214 MSS_7011_06500

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = V35, X21 and HSSI{num2} = 0-n, where n is 1 less than the num-ber of ports supported on the card type used Ifthe status is set, the link is in a linkMode differ-ent from the one provisioned. A clear is issuedwhen the linkMode is changed to be the sameas that provisioned.

Remedial Action Connect the port to a patch panel that is con-figured for the expected linkMode.



6.215 MSS_7011_06501

RNC Type • POC

• 9370 RNC

Component Lp/{num1} X21/{num2}

Severity warning

cleared

Status set

clear

Detail {num1} = 0 - 15 {num2} = 0 - 7 If the status isset, the physical termination configuration ofthe V.11 port is different from that specified inthe terminationRequired field of the provision-ing data. A clear is issued when the termina-tionRequired attribute is changed to be thesame as that physically configured. Note thatthe card will have to be removed from the shelffor the physical termination configuration to bechanged.

Remedial Action Check if the provisioning data is correct. If it is,remove the function processor and correct thephysical termination configuration.



6.216 MSS_7011_06600

RNC Type • POC

• 9370 RNC

Component Lp/{num1} hssi/{num2}

Severity critical

cleared

Status clear

Detail {num1}=1-15 {num2} = 0 If the status is set,this end dce has received a Local Digital Loop-back request from the dte end and enabled theloopback properly. The service and control onthis port dce will be suspended. A clear is is-sued when this end dce has received a LocalDigital Loopback request from the dte end andremoved the loopback properly, or when thisend dce has been put into the Locked statewhile handling loopback request from dte. Theservice and control on this port dce will be re-sumed after the loopback is removed.




6.217 MSS_7011_06601

RNC Type • POC

• 9370 RNC

Component Lp/{num1} hssi/{num2}

Severity major

cleared

Status clear

Detail {num1}=1-15 {num2} = 0 If the status is set,the on-board DIP switch has been closed toconvert from the DCE to DTE interface, but thecable is improperly connected or of the wrongtype. A clear is issued when the right NT nullcable is used or properly connected, or the on-board DIP switch is opened (that is, the DCEinterface is configured).

Remedial Action If the DTE configuration is selected (that is, theon-board DIP switch is closed), use the NTnull modem cable to connect with the dceproperly. If the DCE configuration is selected,set the on-board DIP switch to open positionand use the HSSI standard cable.



6.218 MSS_7011_07000

RNC Type • POC

• 9370 RNC

Component {application} Framer

Severity warning

cleared

Status set

clear

Detail {application} = Trunk/{instance} Un-ack,DpnGateway/{instance}Utp,Fruni/{instance} {instance} = a decimalvalue If the status is set, the value set in theflagsBetweenFrames attribute of the Framercomponent is not supported on this FP ver-sion. The attribute is set to 1 internally. A clearis issued if the flagsBetweenFrames attributeis set to 1.

Remedial Action Provision the flagsBetweenFrames attribute to1, or replace the FP. Consult your Alcatel-Lu-cent technical support group.



6.219 MSS_7011_07001

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {application} = Trunk/{instance} Unack,DpnGateway/{instance} Utp, Frdte/{instance},Fruni/{instance} {instance} = a decimal value Ifthe status is set, the value (crc16) set in theframeCrcType attribute of this Framer com-ponent is not recommended on this FP ver-sion. Excessive frame errors may result. Aclear is issued if the frameCrcType attribute isset to crc32 or noCrc.

Remedial Action Provision the frameCrcType attribute to crc32or noCrc, or replace the FP. Consult your Alc-atel-Lucent technical support group.



6.220 MSS_7011_07002

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {application} = Trunk/{instance} Unack{instance} = a decimal value If the status isset, the value (interrupting) set in the framing-Type attribute of this Framer component is notsupported on this FP version. Excessive errormay result. A clear is issued if the framingTypeattribute is set to hdlc.

Remedial Action Provision the framingType attribute to hdlc, orreplace the FP. Consult your Alcatel-Lucenttechnical support group.



6.221 MSS_7011_07003

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {application} = Htds/{instance} {instance} = adecimal value If the status is set, then aFramer error for the current application/servicehas been detected. Currently, the only servicethat sets this alarm is HTDS, but other applica-tions/services may use this alarm as well in thefuture. Both ends of a Transparent Data Ser-vice path must have the lineSignalTransportattribute turned on for lineSignalTransport towork. This alarm is set when the 2 ends do notmatch in this respect. Note that the transpar-ent data portion of this feature is unaffected(only the transparent modem status lead trans-port part is affected). A clear is issued if theproblem indicated has been resolved.

Remedial Action Provision the lineSignalTransport attribute tothe same value as provisioned on the otherend of the HTDS path.



6.222 MSS_7011_07004

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {application} = Htds/{instance} {instance} = adecimal value If the status is set, then aFramer error for the current application/servicehas been detected. Currently, the only servicethat sets this alarm is HTDS, but other applica-tions/services may use this alarm as well in thefuture. Incompatible VPort pathend configura-tion is detected. The Transparent Data Servicepath must be between a DCE-DTE pair for lin-eSignalTransport to work. This alarm is setwhen the 2 ends don"™t match in this respect.Note that the transparent data portion of thisfeature is unaffected (only the transparent mo-dem status lead transport part is affected). Aclear is issued if the problem indicated hasbeen resolved.

Remedial Action Reconfigure the VPort so that the operationalattribute actualLinkMode is different from thevalue on the other end of the HTDS path. Forexample, if the other end of the path is con-figured as DCE, then the local end must beconfigured as DTE. If the other end of the pathis configured as DTE, then the local end mustbe configured as DCE.



6.223 MSS_7011_07005

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {application} = Htds/{instance} {instance} = adecimal value If the status is set, then aFramer error for the current application/servicehas been detected. Currently, the only servicethat sets this alarm is HTDS, but other applica-tions/services may use this alarm as well in thefuture. Incompatible VPort pathend configura-tion is detected. Both ends of the TransparentData Service path must be of the same card-Type (for example, either both are V35 or bothare V11) for lineSignalTransport to work. At-tempting to run this feature(lineSignalTransport) on a non-Vport card (forexample, DS1, E1, and so on) will also gener-ate this alarm. This alarm is set when the 2ends don"™t match in this respect. Note thatthe transparent data portion of this feature isunaffected (only the transparent modem statuslead transport part is affected). A clear is is-sued if the problem indicated has been re-solved.

Remedial Action Make sure both ends of the Transparent DataService path are of the same card type sup-porting Transparent Modem Status Transport(that is, either both are V35 or both are V11).



6.224 MSS_7011_07006

RNC Type • POC

• 9370 RNC

Component Vs Framer

Severity major

Status message

Detail Framer service error encountered. Too manyABCD Signal changes for Voice Service. Morethen 25 ABCD changes per second or morethan 450 ABCD changes on a whole linkbasis. ABCD Signal Interpreter is disabled.The ABCD Idle signal is transmitted to theegress/nearend side. 2 seconds later, an AB-CD Seize signal is transmitted to the egress/nearend side. This seize is sent for 5 seconds,to prevent further calls from being initiated andto allow the LINK to settle down in case of atemporary noisy LINK. Following the 5 secondsettle down period, the channel re-enablesits"™ ABCD CAS signalling events.

Remedial Action An excess of ABCD CAS Signaling changesemanating from an outside source is beyondour control. The excessive signalling has beenseen to be a result of Framer Sync errors orBit errors occurring on the link. Correct linkquality.



6.225 MSS_7011_07007

RNC Type • POC

• 9370 RNC

Component Vs Framer

Severity major

Status message

Detail Framer service error encountered. Too manyABCD Signal changes for Voice Service. Morethen 25 ABCD changes per second or morethan 450 ABCD changes per second on awhole link basis. ABCD Signal Interpreter isdisabled. The ABCD Idle signal is transmittedto the egress/near-end side. 2 seconds later,an ABCD Seize signal is transmitted to theegress/near-end side. This seize is sent for 5seconds.This has a dual purpose, one is toprevent further calls to be initiated and secondto allow the LINK to settle down in case of atemporary noisy LINK. This alarm will not re-enable the Signal Interpreter such as alarm7006. This is due to the fact that it has alreadygone through 2 re-enables and the problemstill persist. To re-enable the Signal Interpret-er, LOCK then UNLOCK the Voice ServiceFramer.

Remedial Action To re-enable the Signal Interpreter, LOCKthen UNLOCK the Voice Service Framer. Anexcess of ABCD CAS Signalling changes em-anating from an outside source is beyond ourcontrol. The excessive signalling has beenseen to be a result of Framer Sync errors orBit errors occurring on the link. Correct linkquality.



6.226 MSS_7011_07500

RNC Type • POC

• 9370 RNC

Component Ppp/{num1} Mlframer

Severity critical

cleared

Status set

clear

Detail {num1} 1-65535 If the status is set, all links inthe bundle are unavailable for service. A clearis issued when the first link is available.

Remedial Action Check operational state of all Links in bundleand the osiState of the linked Chan compon-ent.



6.227 MSS_7011_07501

RNC Type • POC

• 9370 RNC

Component Ppp/{num1} Mlframer MlpppLink {num2}

Severity critical

cleared

Status set

clear

Detail {num1} 1-65535 {num2} 0-15 If the status isset then the link cannot be enabled due to acondition which either prevents the Link Con-trol Protocol (Lcp) from completing negoti-ations, or has forced it to leave Open state. Upto five such conditions may be present: poorline quality, a looped back line, change of theLcp from Open state, end point discriminatormismatch, and MRRU mismatch. A clear is-sued when the configuration matches thebundle criteria.

Remedial Action Check operational state of the link component.The alarm comment text will indicate which offive conditions has occurred and suggest re-medial action.



6.228 MSS_7011_08000

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {num1} = 1 - 15 {num2} = 0 - 2 {type} = DS3,E3, Sonet, Sdh This warning message is is-sued to let the user know that the provisioningdata that has just been activated will only beput into use when the test is terminated on thespecified component.

Remedial Action Stop the test to put the provisioning data inuse.



6.229 MSS_7011_09000

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 15 {num2} = 0 - n, where n is oneless than the number of ports supported on thecard type {type} = DS1 or E1 There are fourconditions under which this alarm is set: Real-time pool is too large in DSPInvalid reply fromDSPTimeout in getting a response from DSPstream processTimeout in accessing echocanceller DSP

Remedial Action Report problem to support. Reset cards toclear the problem. These alarms are providedfor information only.



6.230 MSS_7011_09001

RNC Type • POC

• 9370 RNC

Component Lp/{x} {port}/{n}

Severity major

Status message

Detail {x} = 1- 14. Lp instance corresponding to a1-port MVPE card. {port} = DS1 or E1, de-pending on the card type (1pDS1Mvpe or1pE1Mvpe). {n} = port instance number, al-ways 0 for 1-port MVPE cards. As the cardwas coming up, it was detected that some ofthe DSPs could not be properly initialized dueto hardware failures. The bitmask provided incomment text identifies the failed DSPs. Theservices that were supposed to use thetimeslots associated with the failed DSPs areautomatically disabled.

Remedial Action Replace the card (card number and its serialnumber are included in the alarm comment).



6.231 MSS_7012_00050

RNC Type • POC

• 9370 RNC

Component Shelf

Severity major

cleared

Status set

clear

Detail On bus-based shelves, this alarms indicatesthat a power converter has failed. On fabric-based shelves, this alarm indicates that one ofthe units related to the power supply hasfailed. This may due to any of the followingconditions: - an external AC rectifier has failed-a processor card has had a power feed failure-a breaker module has failed Once the statuschanges, it takes approximately 2 minutes forthe set or clear alarm to appear. When thestatus is clear, the power supplies functioncorrectly.

Remedial Action On bus-based shelves, replace the defectivepower converter. On fabric-based shelves, ex-amine the hardwareFailure attribute of theShelf component to determine why the alarmwas generated. If the attribute does not satis-factorily explain the cause of the alarm, seeAlcatel-Lucent Multiservice Switch7400/15000/20000 Troubleshooting(NN10600-520) for details on troubleshootinga power supply problem.



6.232 MSS_7012_00051

RNC Type • POC

• 9370 RNC

Component Shelf

Severity major

critical

cleared

Status set

clear

Detail On bus-based shelves, the set alarm is gener-ated with major severity when the cooling unithas failed. When the status is clear, the cool-ing unit functions correctly. On fabric-basedshelves, the set alarm is generated with majorseverity when one or more of the cooling unitfans have failed. If the repeatFanAlarm attrib-ute of the Shelf component is turned on, thealarm, when issued the first time, will be re-generated repeatedly every eight hours untilthe problem is cleared. The severity of thealarm is assigned as follows: - For the firstthree repetitions, the fan alarm is issued withmajor severity. The minor as well as the majoralarm module LEDs on the BIP are turned on.- At the fourth and subsequent repetitions thefan alarm severity is set to critical. The majoralarm module LED on the BIP is turned offwhile the minor as well as the critical alarmmodule LEDs on the BIP are turned on. In thecomment text section "notification:{n}" providesthe number of times the alarm has been reis-sued. This number is incremented by 1 every8 hours from the time of the first alarm. Whenthe fan alarm is cleared, the cooling unit func-tions correctly and all the BIP's LEDs that are



associated with the temperature rise areturned off. Once the alarm status changes, ittakes approximately 2 minutes for the set orclear alarm to appear.

Remedial Action When the status is set, ensure that the coolingunit is powered and working properly. If theproblem persists follow the common proced-ures of general maintenance in Alcatel-LucentMultiservice Switch 7400 Installation, Mainten-ance, and Upgrade - Hardware(NN10600-175), and Alcatel-Lucent Multiser-vice Switch 15000/20000 Installation, Mainten-ance, and Upgrade - Hardware(NN10600-130).



6.233 MSS_7012_00052

RNC Type • POC

• 9370 RNC

Component Shelf

Severity minor

major

critical

cleared

Status set

clear

Detail On bus-based shelves, the alarm is generatedwith a major severity to indicate one or moreprocessor cards have failed. On fabric-basedshelves, the alarm is generated with criticalseverity to indicate one or more processorcards have failed. The alarm is also generatedwith major severity to indicate fabric card fail-ure. The same alarm is generated with minorseverity to indicate BIP alarm circuitry failure.Once the status changes, it takes approxim-ately 2 minutes for the set or clear alarm to ap-pear.

Remedial Action Replace the defective processor/fabric cards.The light on a defective processor/fabric cardis always red.



6.234 MSS_7012_00053

RNC Type • POC

• 9370 RNC

Component Shelf

Severity major

cleared

Status set

clear

Detail On bus-based shelves, this alarm indicatesthat the terminator card has failed or the mes-sage sent from the terminator card to the CP iscorrupted. A clear is issued if the terminatorcard has sent the message to the CP success-fully. On fabric-based shelves, this alarm indic-ates that the shelf"™s MAC address card hasfailed or has been removed, or the messagesent from the MAC address card to the pro-cessor cards is corrupted. A clear is issued ifthe MAC address card has successfully sentthe message to the processor cards. Once thestatus changes, the set alarm appears onlyafter 24 hours.

Remedial Action For bus-based shelves, contact your local Alc-atel-Lucent technical support group. For fabric-based shelves, follow the standard mainten-ance procedure for testing the MAC addresscard and remove or replace the defectiveunit(s).



6.235 MSS_7012_00054

RNC Type • POC

• 9370 RNC

Component Shelf

Severity major

cleared

Status set

clear

Detail On bus-based shelves, this alarm indicatesthat the MAC addresses provided by the ter-minator card are corrupted. On fabric-basedshelves, this alarm indicates that the MAC ad-dresses provided by the shelf"™s MAC ad-dress card are corrupted, or that the MAC ad-dress card was replaced with another MACaddress card that supplies a different range ofMAC addresses. Replacement of a MAC ad-dress card on a Alcatel-Lucent MultiserviceSwitch 15000 shelf requires a careful insertionof the new card once the original card hasbeen removed. Therefore, replacing the MACaddress card is recommended as the finalchoice of remedial action after all other at-tempts to identify the root cause of the alarmhave been exhausted. When the status isclear, the MAC addresses provided by theMAC address card are no longer corrupted.

Remedial Action For bus and fabric-based shelves, contactyour local Alcatel-Lucent technical supportgroup.



6.236 MSS_7012_00055

RNC Type • POC

• 9370 RNC

Component Shelf

Severity minor

major

cleared

Status set

clear

Detail This alarm is issued when the MAC address isnot available. A minor alarm is issued if it isunavailable when the CP starts up. A majoralarm is issued if the MAC address is still un-available after 4 minutes.

Remedial Action On bus-based shelves, replace the terminatorcard. On fabric-based shelves, follow thestandard maintenance procedure for testingthe MAC address card and remove or replacethe defective unit(s).



6.237 MSS_7012_00056

RNC Type • POC

• 9370 RNC

Component Shelf

Severity major

cleared

Status set

clear

Detail On fabric-based shelves, this alarm indicatesthat a failure of the Alarm/BITS card has beendetected. The Alarm/BITS card is located atthe back of the shelf, and is responsible for thegeneration of audible and visual alarms. Whenthe status is clear, the Alarm/BITS card isfunctioning properly.

Remedial Action Follow the standard maintenance procedurefor testing the Alarm/BITS card and remove orreplace the defective unit(s).



6.238 MSS_7012_00057

RNC Type • POC

• 9370 RNC

Component Shelf

Severity major

cleared

Status set

clear

Detail On bus-based shelves, this alarm indicatesthat a power converter has failed. On fabric-based shelves, this alarm indicates that thebreaker related to the power supply Feed Ahas tripped. Once the status changes, it takesapproximately 2 minutes for the set or clearalarm to appear.When the status is clear, thepower supplies function correctly. Other re-lated alarms are 7012 0103 and 7012 0104.




6.239 MSS_7012_00058

RNC Type • POC

• 9370 RNC

Component Shelf

Severity major

cleared

Status set

clear

Detail On bus-based shelves, this alarm indicatesthat a power converter has failed. On fabric-based shelves, this alarm indicates that thebreaker related to the power supply Feed Bhas tripped. Once the status changes, it takesapproximately 2 minutes for the set or clearalarm to appear.When the status is clear, thepower supplies function correctly. Other re-lated alarms are 7012 0103 and 7012 0104.




6.240 MSS_7012_00059

RNC Type • POC

• 9370 RNC

Component Shelf

Severity critical

cleared

Status set

clear

Detail This alarm is only supported on Alcatel-LucentMultiservice Switch 15000 and MultiserviceSwitch 20000 nodes. When the shelf sensordetects a shelf temperature of 70 degreesCelsius (158 Fahrenheit), a high shelf temper-ature software alarm is generated with criticalseverity. The minor as well as the critical alarmmodule LEDs on the BIP are turned on. Thealarm clears when the shelf temperature hasreturned to a normal operating temperaturewhich is less than or equal to 68 degreesCelsius (154.4 Fahrenheit). The minor and crit-ical BIP's LEDs are turned off if no other eventhas turned them on. Once the alarm statuschanges, it takes approximately 2 minutes forthe set or clear alarm to appear.

Remedial Action When the status is set, ensure that the ambi-ent temperature in the room is within the ac-ceptable range and is not interfering with thesystem's ability to cool itself. Ensure the cool-ing unit is powered up with all fans runningand properly inserted into the frame or rack. Ifthe problem persists follow the common pro-cedures of general maintenance in Alcatel-Lu-cent Multiservice Switch 15000/20000 Installa-tion, Maintenance, and Upgrade - Hardware(NN10600-130).



6.241 MSS_7012_00100

RNC Type • POC

• 9370 RNC


Severity minor

critical

cleared

Status set

clear

Detail {instance} = 0 - 15 This alarm is issued when acard is not capable of running a logical pro-cessor (LP). A critical alarm is issued if an LPhas been configured to run on the card, or aminor alarm is issued if no LP has been con-figured to run on the card. Note that no alarmis issued if the Card component"™s cardTypeattribute has not been set.

Remedial Action No remedial action is needed if this is just atemporary condition (for example, when thecard is re-initializing itself). If the condition per-sists, check the Card component"™s availabil-ityStatus and failureCause attributes for amore specific problem cause.



6.242 MSS_7012_00101

RNC Type • POC

• 9370 RNC



Status message

Detail {instance} = 0 - 15 This alarm is issued after acard reboots. It holds some diagnostic inform-ation (in the comment data field) that specifieswhy the card went down. Several instances ofthis alarm can be generated after the card re-boots (depending on how much informationneeds to be displayed). This information is re-ferred to as Trap Data information.

Remedial Action Read the Trap Data information to determinewhy the card rebooted. If the reboot reason inthe Trap Data information does not satisfactor-ily explain the cause of the reboot, see Alcatel-Lucent Multiservice Switch 7400/15000/20000Troubleshooting (NN10600-520) for details ontroubleshooting a control processor or functionprocessor crash.



6.243 MSS_7012_00102

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = 0 - 15 This alarm is issued when aCP starts running as the active CP. It is issuedon initial power up as well as after a CPswitchover.




6.244 MSS_7012_00103

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 When the status is set on aprocessor, one of the units related to powersupply has failed. This can result from any ofthe following: the fed -48V falls to less than39.5Va processor interface module has failed,orbattery A feed failure Once the statuschanges, it takes approximately 2 minutes forthe set or clear alarm to appear. When thestatus is clear, the power supplies are func-tioning correctly. Other related alarms are7012 0057 and 7012 0058.

Remedial Action Examine the alarm record or the hardwareAl-arm attribute under the Shelf Card componentto determine which card is generating thealarm, and replace the defective power con-verter.



6.245 MSS_7012_00104

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 When the status is set on aprocessor, one of the units related to powersupply has failed. This can result from any ofthe following: the fed -48V falls to less than39.5V, ora processor interface module hasfailed.battery B feed failure Once the statuschanges, it takes approximately 2 minutes forthe set or clear alarm to appear. When thestatus is clear, the power supplies are func-tioning correctly. Other related alarms are7012 0057 and 7012 0058.

Remedial Action Examine the alarm record or the hardwareAl-arm attribute under the Shelf Card componentto determine which card is generating thealarm, and replace the defective power con-verter.



6.246 MSS_7012_00105

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {instance} = 0 - 15 This alarm is issued when acard executes a special script while booting.These scripts are usually not deployed in cus-tomer environments.

Remedial Action To clear the alarm you must remove the re-lated files and reset the card. To do this: Issuethe following command to go the bin directory,where the files are located:cd -p("system/bin" )fs Issue the following command to know whichscript files are present:ls fs To remove thescript files, issue either or both of the followingcommands, according to the result of the pre-vious command: remove -r -f -p(startup.card{instance}) fs or remove -r -f -p(startup.rom.card{instance}) fs then, reset thecard that causes the alarm: reset shelf card/{instance}.



6.247 MSS_7012_00151

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {instance} = 0 - 15 The Card component"™sprovisioned card type does not match the in-serted card"™s card type.

Remedial Action Replace the card with one of the appropriatetype, or update the Card component"™s card-Type attribute.



6.248 MSS_7012_00152

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {instance} = 0 - 15 No card is configured forthis slot (the Card component"™s cardTypeattribute has not been set), but a card ispresent in the slot.

Remedial Action Remove the card, or set the Card compon-ent"™s cardType attribute.



6.249 MSS_7012_00153

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {instance} = 0 - 15 The card cannot load itssoftware.

Remedial Action Replace the card or change the card"™s soft-ware load. The card"™s software load is de-termined by the featureList attribute of the Lo-gical Processor Type (LPT) component associ-ated with the card"™s LP.



6.250 MSS_7012_00154

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {instance} = 0 - 15 The card failed its self-testdiagnostics.

Remedial Action Replace the card.



6.251 MSS_7012_00155

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {instance} = 0 - 15 Except for enabling its ac-cess on the backplane, the card is not re-sponding.




6.252 MSS_7012_00156

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {instance} = 0 - 15 The card has a backplaneconnectivity problem.




6.253 MSS_7012_00160

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 The Card component"™sprovisioned card type does not match the in-serted card"™s card type.

Remedial Action Replace the card with one of the appropriatetype, or update the Card component"™s card-Type attribute.



6.254 MSS_7012_00161

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 The card cannot load itssoftware.

Remedial Action Replace the card or change the card"™s soft-ware load. The card s software load is determ-ined by the featureList attribute of the LogicalProcessor Type (LPT) component associatedwith the card"™s LP.



6.255 MSS_7012_00162

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 Except for enabling its ac-cess on the backplane, the card is not re-sponding.




6.256 MSS_7012_00164

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {x} = 0 - 15 This alarm is issued when the sys-tem is unable to reboot a processor card.

Remedial Action Replace the card. This alarm is not cleared bythe system and has to be manually cleared byan operator.



6.257 MSS_7012_00165

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {x} = 0 - 15 This alarm indicates that the re-quired software for this card is not available inthe base Feature Descriptor (FD) file. The fol-lowing are two possible reasons: the hardwareversion of the card is wrongthe hardware ver-sion does not have a matching sub record inthe base FD file When this alarm is raised, nomigration or patching activation is allowed. Aspart of this alarm, the card type and hardwareversion of the card is displayed.

Remedial Action If this alarm is raised, record the card type andhardware version from the alarm. Remove thecard from the shelf, otherwise, no further mi-gration or patching activation is possible. Thisalso clears the alarm. A patch can be requiredto add the missing software in the base FDfile. Contact your local Alcatel-Lucent technicalsupport group.



6.258 MSS_7012_00200

RNC Type • POC

• 9370 RNC

Component Lp/{instance}

Severity critical

cleared

Status set

clear

Detail {instance} = 0 - 15 This alarm is issued whenthe logical processor (LP) is not running. Notethat no alarm is issued if the LP is not con-figured to run on any processor card (that is,when the LP component"™s mainCard andspareCard attributes have not been set).

Remedial Action No remedial action is needed if this is just atemporary condition, for example, when the LPis re-initializing itself. If the condition persists, itis because the LP does not have a workingprocessor card to run on. Clear the problemthat is preventing the LP"™s processor cardfrom being able to run the LP.



6.259 MSS_7012_00201

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = 0 - 15 Traffic will be disrupted in{15,10 and 5} minutes caused by an LPswitchover to the spare card. A deferredswitchover has been scheduled for this LP.This message is displayed in order to notifythe operator that a traffic disruption will occurfor this LP. This message will appear threetimes, once at 15, 10 and 5 minutes, beforeswitchover occurs. Each message indicatesthe time remaining. Other related alarms are7012 0200, 7012 0101 (message alarm forcard), and 0000 0000 (hierarchical clear forLP). There are other related alarms generateddue to the impact of the active card goingdown (attribute Shelf Card standbyStatus nolonger has the value providingService) and thestandby taking over.

Remedial Action You can cancel the scheduled switchover withthe following command:switchover -cancel Lp/{instance}



6.260 MSS_7012_00202

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = 0 - 15 This alarm is issued to noti-fy the operator that a scheduled LP switchoverhas failed. A switchover was attempted for thisLP but failed for one of the following reasons,which will be specified in the alarm: A standbylogical processor is not available.A control pro-cessor software upgrade is currently in pro-gress. (CPs only).The two disks are currentlyout-of-synch. (CPs only).Provisioning data isloading on the spare CP: {A}% done. (CPsonly).

Remedial Action For each of the above reasons, respectively,the operator can perform the following: Ensurethat attribute Lp spareCardStatus is set to"available." This attribute is automatically setto "available" when the spared card is provi-sioned and running.Wait for the software up-grade to finish and then try the switchoveragain.Wait for the disks to get in synch andthen try the switchover again.Wait for the pro-visioning data to be loaded and then try theswitchover again.



6.261 MSS_7012_00203

RNC Type • POC

• 9370 RNC

Component Lp/0

Severity warning

Status message

Detail {time}: time stamp before outage. {type of out-age}: CP, module, swMigration. Active CP lasttime in service: {time} ({type of outage} out-age). This alarm is issued when an outage oc-curs. The last time that the active CP was inservice is displayed.2. A control processorsoftware upgrade is currently in progress.(CPs only)3. The two disks are currently out-of-synch. (CPs only)4. Provisioning data isloading on the spare CP: {A}% done. (CPsonly). There are three types of outages: CP,module and software migration. A CP outageindicates that a CP switchover occurred andthe FPs may have stayed up. This happenswhen the conditions for hot standby CP re-dundancy are met. A module outage indicatesthat a CP went down and the entire modulehas gone out of service. This indicates that hotstandby CP redundancy has been disabled orthat the corresponding conditions for hotstandby CP redundancy have not been met. Asoftware migration outage indicates that a soft-ware migration switchover occurred

Remedial Action No remedial action is required. This informa-tion is used off-switch to calculate the durationof the outage.2. Wait for the software upgradeto finish and then try the switchover again.3.Wait for the disks to get in synch and then trythe switchover again.4. Wait for the provision-



ing data to be loaded and then try theswitchover again.



6.262 MSS_7012_00204

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = 0 - 15 This LP cannot achieve itsexpected Migration-Switchover behavior. SeeProv Migration alarm for more details. At thestart of a software migration activation a re-sponse is generated indicating which LPs donot support the reduced service outage duringsoftware migration. This is based on opera-tional and provisionable conditions. This alarmis issued for an LP not identified in the re-sponse, whose operational conditions changeduring the software migration such that it canno longer support the reduced service outage.This alarm is issued when the FPs destined forthe migration shelf are chosen.

Remedial Action If deemed appropriate, the software migrationactivation can be stopped by issuing the stopprovisioningSystem command while in provi-sioning mode.



6.263 MSS_7012_00300

RNC Type • POC

• 9370 RNC

Component Shelf Card/{n} SparedServices

Severity warning

critical

Status message

Detail {n} = instance value of shelf card This alarmindicates that one of the standby service in-stances on the parent Card has encountered acondition which the user should be madeaware of. The standby service has likely en-countered one of the following: a software er-roran engineering/resource limit reachedanapplication-specific problem If the standby ser-vice is unable to provide standby capability asa result, the severity is critical. This degradesthe potential for a complete equipment protec-tion switchover and an alarm (also againstSparedServices) tracks the outstanding condi-tion from Alcatel-Lucent Multiservice DataManager perspective. If the condition does notaffect the ability to provide standby capability,the severity is warning. The comment text con-tains the following information about the ser-vice which initiated the alarm coming out:ComponentNameDateAndTimeActiveList-StatusPerceivedSeverityAlarmTypeProbable-CauseNTPIndexNotificationIdCommentData-FileInformation

Remedial Action Look up the NTPIndex from the Comment textand perform its remedial action.



6.264 MSS_7012_00301

RNC Type • POC

• 9370 RNC

Component Shelf Card/{n} SparedServices

Severity major

cleared

Status set

clear

Detail {n} = instance value of shelf card If the statusis set, at least one of the standby service in-stances on the parent card has been unable toprovide standby capability, thus degrading thepotential for a complete equipment protectionswitchover. A clear is issued after all standbyservice instances are once again able toprovide standby service.




6.265 MSS_7013_00000

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, availableshared memory for the logical processor (LP)has decreased below 12.5%. The LP is experi-encing an unbalanced traffic flow resulting inhigh queueing delays and shared memory de-pletion. This alarm is set to warn of impendingshared memory exhaustion. A clear is issuedwhen available shared memory for the LP hasincreased above 18.75%.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired in order to balance the flow of trafficthrough this LP, thus reducing the amount oftraffic congestion and length of queueingdelays.



6.266 MSS_7013_00001

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, availableshared memory for the logical processor (LP)has decreased below 6.25%. The LP is experi-encing an unbalanced traffic flow resulting inhigh queueing delays, and is approachingshared memory exhaustion. In the case of thecontrol processor (that is, Lp/0), the alarm in-dicates that resources are being held up onthe CP. When this condition is detected, thelargest shared memory traffic queues arepurged automatically until available sharedmemory for the LP has increased above9.39%. A clear is issued at this point.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering must beperformed to balance the flow of traffic throughthis LP and reduce the amount of traffic con-gestion and length of queueing delays.



6.267 MSS_7013_00002

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, the avail-able ingress cell-blocks from the logical pro-cessor (LP) have decreased below 20% oftotal ingress cell-blocks. Under this condition,traffic flowing across this FP may encounterhigh queueing delays. When this condition isdetected, the less priority traffic will be dis-carded first. If the congestion still persists,even higher priority traffic will be discarded.This continues until available ingress cell-blocks for the LP have increased above 25%of total ingress cell-blocks. A clear is issued atthis point. A filtering mechanism is implemen-ted such that a set/clear is issued by oneminute.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired to balance the flow of traffic through thiscard in order to reduce the amount of trafficand the length of queues.



6.268 MSS_7013_00003

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, the avail-able ingress frame-blocks from the logical pro-cessor (LP) have decreased below 20% oftotal ingress frame-blocks. Under this condi-tion, traffic flowing across this FP may en-counter high queueing delays. When this con-dition is detected, the less priority traffic will bediscarded first. If the congestion still persists,even higher priority traffic will be discarded.This continues until available ingress frame-blocks for the LP have increased above 25%of total ingress frame-blocks. A clear is issuedat this point. A filtering mechanism is imple-mented such that a set/clear is issued by oneminute.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired to balance the flow of traffic through thiscard in order to reduce the amount of trafficand the length of queues.



6.269 MSS_7013_00004

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, the avail-able egress cell-blocks from the logical pro-cessor (LP) have decreased below 20% oftotal egress cell-blocks. Under this condition,traffic flowing across this FP may encounterhigh queueing delays. When this condition isdetected, the less priority traffic will be dis-carded first. If the congestion still persists,even higher priority traffic will be discarded.This continues until available egress cell-blocks for the LP have increased above 25%of total egress cell-blocks. A clear is issued atthis point. A filtering mechanism is implemen-ted such that a set/clear is issued by oneminute.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired to balance the flow of traffic through thiscard-reducing the amount of traffic and lengthof queues.



6.270 MSS_7013_00005

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, the avail-able egress frame-blocks from the logical pro-cessor (LP) have decreased below 20% oftotal egress frame-blocks. Under this condi-tion, traffic flowing across this FP may en-counter high queueing delays. When this con-dition is detected, the less priority traffic will bediscarded first. If the congestion still persists,even higher priority traffic will be discarded.This continues until available egress frame-blocks for the LP have increased above 25%of total egress frame-blocks. A clear is issuedat this point. A filtering mechanism is imple-mented such that a set/clear is issued by oneminute.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired to balance the flow of traffic through thiscard-reducing the amount of traffic and lengthof queues.



6.271 MSS_7013_00011

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, availableshared memory for the logical processor (LP)has fallen below 25%. The LP is experiencingan unbalanced traffic flow resulting in highqueueing delays and shared memory deple-tion. This alarm is set to warn of FCI bit settingin packet header of data traffic and possiblediscard of data packets tagged as low, medi-um, and high discard priority. In the case ofthe control processor, which is Lp/0, thisalarms indicates that resources are being heldup on the CP. A clear is issued when availableshared memory for the LP has exceeded 25%after one minute.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired in order to balance the flow of trafficthrough this LP, thus reducing the amount oftraffic congestion and length of queueingdelays, and preventing discard of data traffic.In the case of the CP, determine which ser-vices are holding up resources on the CP, andtake appropriate action.



6.272 MSS_7013_00021

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, there areno more message blocks in local memory forthe logical processor (LP). Local messageblocks are used for local control messaging onthe card. The LP is experiencing an unbal-anced control message traffic flow resulting inhigh queuing delays. As long as this level ofcongestion persists, most of the lower prioritysubsequent control activities on the LP will notbe performed due to insufficient resources.One minute after the set alarm was issued, aclear will be issued if the available messageblocks have returned to normal operatinglevels. The clear alarm will also include inform-ation about how long the congestion persisted.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired. Contact your local Alcatel-Lucent tech-nical support group, if necessary.



6.273 MSS_7013_00022

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, availablemessage blocks in local memory for the logicalprocessor (LP) have decreased below 60%.Local message blocks are used for local con-trol messaging on the card. The LP is experi-encing an unbalanced control message trafficflow resulting in high queuing delays. As longas this level of congestion persists, some ofthe lower priority subsequent control activitieson the LP will not be performed due to insuffi-cient resources. Five minutes after the setalarm was issued, a clear will be issued auto-matically if the available message blocks inlocal memory have increased above 60%.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired. Contact your local Alcatel-Lucent tech-nical support group, if necessary.



6.274 MSS_7014_00000

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, availablememory for the logical processor (LP) has de-creased below a threshold of 960 Kbytes ofthe memory on a control processor and 160Kbytes of the memory on a function processor.Various systems will avoid allocating memory.A clear is issued when available memory forthe LP has increased above the clearthreshold, which is 1010 Kbytes on a controlprocessor and 180 Kbytes on a function pro-cessor.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired in order to balance the memory con-sumption of the applications on this LP. Con-tact your local Alcatel-Lucent technical supportgroup for assistance if necessary.



6.275 MSS_7014_00001

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 If the status is set, availablememory for the logical processor (LP) has de-creased below a threshold of 400 Kbytes ofthe memory on a control processor and 40Kbytes of the memory on a function processor.Only critical systems will allocate memory.This condition must be resolved quickly be-cause a total exhaustion of memory will resultin the automatic resetting of the card. A clearis issued when available memory for the LPhas increased above the clear threshold,which is 480 Kbytes on a control processorand 60 Kbytes on a function processor.

Remedial Action Frequent occurrences of this condition indicatethat re-engineering is required in order to bal-ance the memory consumption of the applica-tions on this LP. Contact your local Alcatel-Lu-cent technical support group for assistance ifnecessary.



6.276 MSS_7014_00010

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status message

Detail {instance} = 0 - 15 If the status is set, availablehigh-speed memory for the logical processor(LP) has decreased below a threshold of 8Kbytes of the memory on a processor. Varioussystems will avoid allocating high-speedmemory. A clear is issued when availablehigh-speed memory for the LP has increasedabove the clear threshold, which is 10 Kbytesof the high-speed memory on the processor.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired in order to balance the memory con-sumption of the applications on this LP. Con-tact your local Alcatel-Lucent technical supportgroup for assistance if necessary.



6.277 MSS_7014_00011

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status message

Detail {instance} = 0 - 15 If the status is set, availablehigh-speed memory for the logical processor(LP) has decreased below a threshold of 4Kbytes of the high-speed memory on a pro-cessor. Only critical systems will allocate addi-tional memory. This condition should be re-solved quickly because a total exhaustion ofmemory will result in degraded service. A clearis issued when available high-speed memoryfor the LP has increased above the clearthreshold, which is 6 Kbytes of the high-speedmemory.

Remedial Action Frequent occurrences of this condition indicatethat re-engineering is required in order to bal-ance the memory consumption of the applica-tions on this LP. Contact your local Alcatel-Lu-cent technical support group for assistance ifnecessary.



6.278 MSS_7015_00000

RNC Type • POC

• 9370 RNC

Component Time

Severity major

critical

cleared

Status set

clear

Detail Module stops time synchronization with net-work time server. The major status is set whenthe node loses synchronization with the net-work time server. This is a result of the net-work time server not responding to a Multiser-vice Switch XNTP request. Module cannotconnect to time server. A critical status is setwhen the node, after losing synchronizationwith the network time server, cannot re-synchronize with other provisioned networktime servers. Module completes time syn-chronization with network time server. A clearis issued when the node regains synchroniza-tion with the network time server; it is receivingXNTP responses from the time server.

Remedial Action Ensure the network time server is running as aproper stratum time server and is reachablefrom the node. Verify the following: the TIMEcomponent has at least one synchronizedsyncSourcethe TIME SERVER componentsare not lockedthe network time servers are upand running If all network time servers aredown, contact your local Alcatel-Lucent tech-nical support group.



6.279 MSS_7015_00001

RNC Type • POC

• 9370 RNC

Component Time

Severity warning

Status message

Detail This alarm is issued when the network timehas changed by more than one minute. Thenetwork time may change after synchronizingthe module to the network or when the operat-or sets the time manually.

Remedial Action No action is required.



6.280 MSS_7015_00002

RNC Type • POC

• 9370 RNC

Component Time

Severity major

cleared

Status set

clear

Detail If the status is set, the time difference betweenthe node UTC (moduleTime minus offset) andthe network time server is greater than 1000seconds. The synchronization status of thenode XNTP is changed to unsynchronized andthe main server is set to NULL. This allows theoperator to correct the time by setting themoduleTime manually. A clear is issued whenthe network time is corrected to within 1000seconds of the network time server.

Remedial Action Check the time of the network time serversand the time of the node, and correct the timemanually by setting the moduleTime of thenode module. After a few minutes, the nodeXNTP synchronizes with the network timeserver.



6.281 MSS_7015_00010

RNC Type • POC

• 9370 RNC

Component Time Server/{n}

Severity minor

cleared

Status set

clear

Detail {n} = 1 - 10 The Server is disabled. The statusis set when Multiservice Switch XNTP fails toregister an XNTP UDP port with vrIP at startuptime. When XNTP fails to register an XNTPUDP port with vrIP, and the ipStack of the net-work time server is provisioned to be vrIp, thenetwork time server is disabled. XNTP stopstime synchronization with the network timeserver. The Server is enabled A clear is issuedwhen XNTP successfully registers an XNTPUDP port with vrIp. XNTP starts to synchronizewith the network time server.

Remedial Action Check the status of vrIp, to see if they are run-ning correctly. Correct the errors if found.XNTP tries to register with vrIp every 10minutes until it succeeds.



6.282 MSS_7015_00011

RNC Type • POC

• 9370 RNC

Component Time Server/{n}

Severity minor

cleared

Status set

clear

Detail {n} = 1 - 10 No response from the time server,the server is idle. The status is set if Multiser-vice Switch XNTP does not receive any pack-ets from the network time server after it sends8 packets to the network time server. This maybe due to one of the following reasons: 1. Net-work error The provisioned network time serv-er does not exist, or a network error occursprevents XNTP from receiving any packetsfrom the network time server. 2. Server config-uration error The network time server"™s con-figuration prevents this module from acting asa client to synchronize its time with the net-work time server. 3. Protocol error The versionof the XNTP running on the network time serv-er is not compatible with XNTP version, so thatthe network time server does not reply to theXNTP time synchronization request. Get re-sponse from the server, the Server is active. Aclear is issued when the error(s) listed aboveare corrected, and XNTP receives responsesfrom the network time server.

Remedial Action Check the existence and connectivity of thenetwork time server and take the appropriateaction.



6.283 MSS_7015_00012

RNC Type • POC

• 9370 RNC

Component Time Sever/{n}

Severity warning

major

cleared

Status set

clear

Detail {n} = 1 - 10 Module does not communicatewith this network time server correctly. Thestatus is set when the network time server isnot selected as one of the network time syn-chronization sources, although its OSI state is"unlocked" , "enabled" and "active" . This maybe due to one of the following reasons: Thenetwork time server itself is not synchron-ized.The network time server"™s stratum ishigher than Multiservice Switch XNTP"™sstratum. Module starts to communicate withthis network time server correctly. A clear is is-sued when the above errors are corrected andthe network time server is selected as one ofthe time synchronization sources of this mod-ule.

Remedial Action Check the status, stratum, leap, and otherXNTP protocol information of XNTP runningon the network time server and correct any er-rors if found.



6.284 MSS_7015_00014

RNC Type • POC

• 9370 RNC

Component Time

Severity major

cleared

Status set

clear

Detail An alarm with status set is issued against theTime component when the times reported bytwo time servers differ by more than the provi-sioned value of the Time timeDifferenceLimitattribute. A clear alarm is issued when the dif-ference is no longer greater than this value.The Time timeDifferenceLimit attribute spe-cifies the allowed difference between the timesreported by provisioned time servers. ThetimeDifferenceLimit value is provisioned basedon the sensitivity of time dependent applica-tions and the network topology in use. An ap-plication more sensitive to time requires con-sistently close times reported by the time serv-ers. A more elaborate network topology maycause the time servers to report a wider rangeof time differences due to network delays thana simple network.

Remedial Action Check the connectivity of the network timeservers and take the appropriate action.



6.285 MSS_7015_00015

RNC Type • POC

• 9370 RNC

Component Time Server/{x}

Severity major

cleared

Status set

clear

Detail {x} = 1-10 An alarm with status set is issuedagainst a Time Server component when thestratum reported by the remote time server ex-ceeds the Time stratumLimit value. A clearalarm is issued when the reported stratum isno longer greater than this value. The TimestratumLimit attribute specifies the limit for thestratum reported by the remote time server.Stratum is an integer used by the NetworkTime Protocol to indicate the topological dis-tance between a client and a time server. Asmaller stratum value indicates a better topolo-gical distance to a time server.

Remedial Action Check the connectivity of the network timeserver and take the appropriate action.



6.286 MSS_7015_00016

RNC Type • POC

• 9370 RNC

Component Time

Severity minor

cleared

Status set

clear

Detail None. When the status is SET, the window foraccepting a leap second event has beenopened. The window for accepting a leapsecond event starts 2 minutes before the ex-pected leap second event, and ends at 23hours past the expected leap second event.When the status is CLEAR, a leap secondevent has been detected within the window orthe window has closed. In either case, post-leap seconds have been applied in the sys-tem. A leap second event is expected to occurat the end of the leap second date. A leapsecond is added or deleted at this time. If aleap second is inserted, it takes two secondsfrom 23:59:59 to 0:00:00 instead of onesecond. If a leap second is deleted, time willjump from 23:59:58 to 0:00:00 in one secondinstead of two seconds. The leap second datewould normally be on June 30 or December31. Bulletin C from the International Earth Ro-tation and Reference Systems Service(www.iers.org) announces leap seconds.

Remedial Action Monitor for the successful completion of theleap second event. If the CLEAR alarm sur-faces when the window closes, verify that theleap second date was provisioned properly. Ifit was, then the network time server should be



troubleshot. This is required in order to under-stand why the leap second event was notpropagated as expected to the MSS from thenetwork time server.



6.287 MSS_7015_00020

RNC Type • POC

• 9370 RNC

Component Time

Severity major

Status message

Detail This alarm is issued when the network timerserver daemon receives a corrupt protocoldata unit (PDU), which results in a denial ofservice.




6.288 MSS_7017_01000

RNC Type • POC

• 9370 RNC

Component NS

Severity critical

cleared

Status set

clear

Detail If the status is set, a reference has been provi-sioned and the CP is not synchronized to thereference. A clear is issued if no referencesare provisioned and the CP is currently freerunning or if the CP is synchronized to the in-coming reference.

Remedial Action The PLL algorithm should resynchronize theclock. However, if the alarm is not clearedafter an hour of being set, the clocking sourceis probably unreliable and a new clockingsource should be provisioned. If the alarm isstill not cleared after switching to the newclock source, the root cause could be otherthan the reference source (that is, it could bethe active CP, 8KHz backplane tracks, CPslot). To verify, a CP switchover is recommen-ded.



6.289 MSS_7017_01001

RNC Type • POC

• 9370 RNC

Component NS

Severity warning

Status message

Detail Indicates a change in Synchronization StatusMessage (SSM) on the Active or Standby tim-ing reference.

Remedial Action This alarm is for information only. If the refer-ence is persistently reporting a degraded SSMquality level, it may be necessary to re-engineer the network timing distribution.



6.290 MSS_7017_01002

RNC Type • POC

• 9370 RNC

Component NetworkSynchronization (NS)

Severity critical

cleared

Status set

clear

Detail This alarm is raised when hardware reports anunexpected loss of clock source for the SETSport. SETS PLL software is selecting an activereference source but hardware reports it can-not detect any valid signal for synchronization.

Remedial Action This is normal if it is temporary and cleared al-most immediately. On a clock referenceswitch, there may be a temporary loss of sig-nal before hardware can detect the newly act-ive source. If the alarm is not cleared shortlyafter it has been raised, it indicates a problemwith the SETS active reference source. It is re-commended then to provision another sourcefor the SETS port.



6.291 MSS_7020_00001

RNC Type • POC

• 9370 RNC

Component Vr/{string1} Pp/{string2}

Severity warning

Status message

Detail {string1} = name of the virtual router {string2} =name of the protocol port This alarm indicatesthat IP Accounting data could not be retrievedfrom the media specified in the alarm text with-in the expected time interval. This implies thatIP Accounting records will not be generated forthis protocolPort (Pp) component for the cur-rent collection period.

Remedial Action Frequent occurrences of this condition indicatethat re-engineering is required to balance thememory block and/or heap consumption of ap-plications on the CP and/or LPs forwardingtraffic for this Pp. Contact your local Alcatel-Lucent technical support group for assistance.



6.292 MSS_7020_00002

RNC Type • POC

• 9370 RNC

Component Rtr/{n} Vrf/{m}

Severity major

Status message

Detail { n} = Router component name {m} = Vrf com-ponent name The system has demoted thehardware data paths belonging to this Vrf as aresult of either the consumption of VROs onthe card reached 95% or an operator com-mand "set rtr/n vrf/m slu/cardNum forwM sw"has been issued.

Remedial Action It is recommended the card should be re-engineered before the minor VRO alarm is is-sued with the consumption of VROs reaching85%; the operator can re-engineer the card byselecting one of the following two options: offload the card by moving some VRFs to othercard(s), or operationally, move the hardwaredata paths on the card belonging to one ormore VRFs to software in order to free up thehardware resource.



6.293 MSS_7021_00000

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip

Severity warning

Status message

Detail {string} = name of the virtual router Lp is out ofmemory. Ip service is restarted with all the pro-visioned data. If more memory is not allocatedfor Ip, the problem may repeat. The commentdata and the operator data contains the virtualrouter identifier that owns this IP service.

Remedial Action IP has restarted because of lack of memory.To avoid similar problems in future, allocatemore memory for IP from Vr.



6.294 MSS_7021_00001

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router Ip servicefailed to be initiated in lp/{instance} due to noavailable memory in lp/{instance}.

Remedial Action Verify the provisioning related to lp/{instance}is within the supported limit, as stated in theEngineering Guidelines.



6.295 MSS_7021_00006

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip cache/{instance}

Severity major

cleared

Status set

clear

Detail {string} = name of the virtual router {instance}= an Lp number The IP cache table of the Vrcomponent has failed to allocate memory oradjust cache table size in lp/{instance}. Thisalarm is set when the IP cache table of the Vrcomponent has failed to allocate memory oradjust cache table size in lp/{instance}. Thecache table size is specified by the cacheT-ableSize attribute. A clear is issued after thecache table size is changed successfully.

Remedial Action IP service is affected only when OSI usage isidle. To avoid this problem, allocate more IPmemory.



6.296 MSS_7021_00008

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {string} = name of the virtual router FP hard-ware resource exhaustion has occurred, caus-ing the route addition to fail. The IP forwardingtable on the FP on which the virtual routerresides is not synchronized with the IP for-warding table on the CP. Even though CAS re-ports displaying the IP forwarding table mayindicate that the route exists, IP traffic may beunable to be forwarded by the FP. This alarmcan be set once per VR after resource deple-tion of any type (next hop, ecmp, route table)preventing route addition. Once resources areagain available and routes can be added suc-cessfully, the alarm is reset and will be issuedif resources are again exhausted.

Remedial Action Manually clear the alarm from Alcatel-LucentMultiservice Data Manager. Reset the FP torestart the IP service to recover from the hard-ware resource exhaustion. Choose to re-engineer the network to reduce depletion ofthe critical resource. To avoid similar prob-lems, contact Alcatel-Lucent technical support.



6.297 MSS_7021_00010

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip cache/{instance}

Severity minor

cleared

Status set

clear

Detail {string} = name of the virtual router {instance}= cache on the FP When there are excessiveIP LCM cache misses, the LCM cache is filledto exceed the threshold, raising the alarm tocaution the operator. The excessive IP LCMcache misses can be caused by bad networkconfiguration or viruses in the network.

Remedial Action Lock the VR or the port. Further diagnosis caninclude increasing the cache, however, if thereis enough cache, more tests are required. Inthat case, contact Alcatel-Lucent technicalsupport.



6.298 MSS_7021_00013

RNC Type • POC

• 9370 RNC

Component Vr/{x} Ip Cpp IsolatedDa/{ipaddress},{lpnum}Rtr/{x} Cpp IsolatedDa/{ipaddress},{lpnum}Rtr/{x} Vrf/{y} Cpp IsolatedDa/{ipaddress}, {lpnum}

Severity minor

cleared

Status set

clear

Detail {x} = name of the virtual router or router {y} =name of the vrf {ipaddress} = address of thelocal IpLogicalInterface {lpnum} = 0 - 15 TheLP for the DA that is exceeding the provi-sioned CPP flow rate is delivered as part ofthis alarm. This alarm is raised if the trafficamount on the DA within an FP has exceededthe VR flow rate provisioned. Note that thealarm is raised if any DA on any PQC FP ex-ceeds the provisioned value(s) -- it is not ag-gregate to all cards on the node. A clearedalarm will be generated once the isolationTimehas expired and the DA flow rate is below theconfigured maximum flow rate, or if the VRCPP component is manually cleared.

Remedial Action If you believe that control traffic on the givenVR was erroneously flagged, you can CLEARthe CPP component of the given VR to restoretraffic immediately. Otherwise, traffic will beginto flow again after isolationTime has elapsed.



6.299 MSS_7021_00014

RNC Type • POC

• 9370 RNC

Component Vr/{x} Ip Cpp IsolatedDa/{ipaddress},{lpnum}Rtr/{x} Cpp IsolatedDa/{ipaddress},{lpnum}Rtr/{x} Vrf/{y} Cpp IsolatedDa/{ipaddress}, {lpnum}

Severity major

cleared

Status set

clear

Detail {x} = name of the virtual router or router {y} =name of the vrf {ipaddress} = address of thelocal IpLogicalInterface {lpnum} = 0 - 15 TheLP for the DA that is exceeding the provi-sioned CPP flow rate is delivered as part ofthis alarm. This alarm is raised when the DA isbeing permanently disabled and requires oper-ator intervention to clear the problem. A DAwill be permanently disabled when the trafficamount on the DA within an FP has exceededthe VR flow rate provisioned for three consec-utive isolation periods. A cleared alarm will begenerated once the operator has cleared theDA or the CPP component.

Remedial Action If you believe that control traffic on the givenVR was erroneously flagged, you can CLEARthe CPP component of the given VR to restoretraffic immediately.



6.300 MSS_7021_00015

RNC Type • POC

• 9370 RNC

Component vr/{x} ip pmm ca/{y}

Severity major

cleared

Status set

clear

Detail {x} = vr instance {y} = proxy ca instance

Remedial Action unlock vr, if lockedunlock vr ip, if lockedunlockproxy ca, if lockedcheck that the EM PMM onthe MDM is runningensure the ip address ofthe Proxy CA matches the MDM addressen-sure the MDM has its webpkproxy certificates



6.301 MSS_7021_01000

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Ospf

Severity warning

Status message

Detail {string} = name of the virtual router An OSPFpacket has been received on a non-virtual in-terface from a router whose configurationparameters conflict with this router"™s config-uration parameters. Due to this, adjacencycannot be formed. The comment data and theoperator data has relevant information to re-solve the error. The alarm provides the follow-ing information: ospfRouterId - the originator ofthe alarm ospfIfIpAddress - the IP Address ofthe interface on which the packet was receivedospfAddressLessIf - the IfIndex of the interfaceif it is an addressless interface ospfConfigEr-rorType - type of error. Could be one of the fol-lowing: badVersion(1), areaMisMatch(2), un-knownNbmaNbr(3), unknownVirtualNbr(4), au-thTypeMismatch(5), authFailure(6), net-MaskMismatch(7), helloIntervalMismatch(8),deadIntervalMismatch(9), optionMisMatch(10)ospfPacketType - Type of OSPF Packet

Remedial Action Check the configuration of this router and therouter from which the packet was received andsolve any mismatch. The comment data andthe operator data has all the necessary inform-ation to correct this problem.



6.302 MSS_7021_01001

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router An OSPFpacket has been received on a virtual interfacefrom a router whose configuration parametersconflict with this router"™s configuration para-meters. Due to this, adjacency cannot beformed. The comment data and the operatordata has relevant information to resolve the er-ror. The alarm provides the following informa-tion: ospfRouterId - the originator of the AlarmospfVirtIfAreaId - the area to which this virtualinterface belongs to ospfVirtIfNeighbor - the IPaddress of the neighbor who generated thispacket ospfConfigErrorType - type of error.Could be one of the following: badVersion(1),areaMisMatch(2), unknownNbmaNbr(3), un-knownVirtualNbr(4), authTypeMismatch(5), au-thFailure(6), netMaskMismatch(7), helloInter-valMismatch(8), deadIntervalMismatch(9), op-tionMisMatch(10) ospfPacketType - type ofOSPF Packet

Remedial Action Check the configuration of this router and therouter from which the packet was received andsolve any mismatch. The comment data andthe operator data has all the necessary inform-ation to correct this problem.



6.303 MSS_7021_01002

RNC Type • POC

• 9370 RNC

Component Vr/{string} Pp/{ppId} IpPort logicalIf/{addr} Os-pfIfRouter/{string} Interface/{addr} OspfIf

Severity major

cleared

Status set

clear

Detail {string} = Instance string identifier of therouter/virtual router component {ppId} = Pro-tocol Port Id {addr} = IPv4 address of this inter-face If the status is set, a badly authenticatedpacket has been received on a non-virtual OS-PF Interface. The interface is identified by thealarm. One of the following conditions is true:The AuthType specified in the received packetdoes not match the provisioned AuthType forthis interface.If simple password authenticationis being used, the AuthKey information in thereceived packet does not match the provi-sioned AuthKey information for the interfaceon which the packet was received.If MD5 au-thentication is being used, the Md5Key thepacket was encoded with does not match theprovisioned Md5Key information for the inter-face on which the packet was received. Aclear is issued when 10 minutes pass withoutthe receipt of a badly authenticated packet, orif the OspfIf enters the down state, or if the Os-pfIf is locked or deleted.

Remedial Action Verify the configuration of the authenticationinformation on the neighboring OSPF router. Ifthe authentication provisioning is confirmed tobe correct, identify the source of the intrusion



using the data provided in the alarm.



6.304 MSS_7021_01003

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Ospf VirtIfEntry/{virtIfId}

Severity major

cleared

Status set

clear

Detail {string} = Instance string identifier of therouter/virtual router component {virtIfId} = Vir-tualIfEntry identifier If the status is set, a badlyauthenticated packet has been received on avirtual OSPF Interface. The virtIfEntry is identi-fied by the alarm. One of the following condi-tions is true: * The AuthType specified in thereceived packet does not match the provi-sioned AuthType for this virtIf.* If simple pass-word authentication is being used, the Au-thKey information in the received packet doesnot match the provisioned AuthKey informationfor the virtIf on which the packet was re-ceived.* If MD5 authentication is being used,the Md5Key the packet was encoded withdoes not match the provisioned Md5Key in-formation for the virtIf on which the packet wasreceived. A clear is issued when 10 minutespass without the receipt of a badly authentic-ated packet, or if the virtIf enters the downstate, or if the virtIf is locked or deleted.

Remedial Action Verify the configuration of the authenticationinformation on the neighboring OSPF router. Ifthe authentication provisioning is confirmed tobe correct, identify the source of the intrusionusing the data provided in the alarm.



6.305 MSS_7021_01004

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {string} = Instance string identifier of the virtualrouter component Number of LSAs in therouter"™s link-state database has exceededthe maximum number of external link-stateentries that can be stored. Cannot add moreLSAs until LSDB limit is increased, until then,all the new LSAs are discarded. The commentdata and the operator data has relevant in-formation to resolve the error. The alarmprovides the following information: VrId - thevirtual router to which the OSPF belongs osp-fRouterId - the originator of the Alarm osp-fExtLsdbLimit - the current value of the maxim-um number of entries allowed. Note that theospfExtLsdbLimit attribute is of criticality com-ponent level. Changing this attribute will restartOSPF with the provisioned values. This alarmis cleared when a larger value is assigned tothe ospfExtLsdbLimit attribute.

Remedial Action Set the extLsdbLimit attribute of the compon-ent given in the component name field to a lar-ger value. Until then, all the new LSAs will bediscarded. This alarm is cleared when a largervalue is assigned to the ospfExtLsdbLimit at-tribute.



6.306 MSS_7021_01005

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router Number ofLSAs in the router"™s link-state database hasexceeded ninety percent of external link-stateentries that can be stored. The comment dataand the operator data has relevant informationto resolve the error. The alarm provides thefollowing information: ospfRouterId - the origin-ator of the Alarm ospfExtLsdbLimit - the cur-rent value of the maximum number of entriesallowed. Note that the ospfExtLsdbLimit attrib-ute is of criticality component level. Changingthis attribute will restart OSPF with the provi-sioned values.

Remedial Action Set the extLsdbLimit attribute of the compon-ent given in the component name field to a lar-ger value.



6.307 MSS_7021_01006

RNC Type • POC

• 9370 RNC


Severity cleared

Status clear

Detail {string} = name of the virtual router OSPF isout of memory. OSPF service is restarted withall the provisioned data. If more memory is notallocated for IP, the problem may repeat. Thecomment data and the operator data containsthe virtual router identifier that owns this IPservice.

Remedial Action OSPF has restarted because of lack ofmemory. To avoid similar problems in future,allocate more memory for IP from Vr.



6.308 MSS_7021_01007

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Bgp

Severity major

cleared

Status set

clear

Detail {string} = name of the virtual router When thestatus is set, BGP has failed to establish atransport protocol listen port on well knownTCP port 179. Either Vr or TCP may be out ofmemory. BGP will still be able to initiate trans-port connections to configured BGP peers, butwill not be able to accept transport connec-tions from configured BGP peers. The routeridentification number of the local BGP applica-tion is included in the alarm text. When thestatus is clear, BGP has successfully estab-lished a transport protocol listen port on wellknown TCP port 179.

Remedial Action When the status is set, BGP will attempt to es-tablish the transport protocol listen port con-tinually (every 30 seconds). If the status doesnot change to clear over time, memory mayneed to be made free through provisioningchanges (either by allocating more memory forVr or by reducing the number of services beingrun by this or other instances of Vr). DisablingBGP will also change the status to clear.When the status is clear, no remedial action isrequired.



6.309 MSS_7021_01008

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Bgp Peer/{address}

Severity minor

cleared

Status set

clear

Detail {string} = name of the virtual router {address} =IP address of the BGP peer When the status isset, BGP has failed to initiate a transport pro-tocol connection to a configured BGP peer.The router identification number of the localBGP application and the IP address of thepeer to which BGP cannot connect is includedin the alarm text. When the status is clear,BGP has successfully established a transportprotocol connection to a configured BGP peer.

Remedial Action When the status is set, BGP will attempt to es-tablish the transport protocol connection con-tinually (every 120 seconds). If the status doesnot change to clear over time, ensure that theBGP peer identified in the alarm is provisionedproperly and that the remote BGP applicationis enabled and configured properly. Disablinga BGP peer will also change the status toclear. When the status is clear, no remedialaction is required.



6.310 MSS_7021_01009

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router {address} =IP address of the BGP static peer BGP hasdetected an error condition which prompted itto send a NOTIFICATION message to a BGPpeer and then close the BGP connection tothat peer. The router identification number ofthe local BGP application and the IP addressof the peer to which BGP is sending the NOTI-FICATION is included in the alarm text. Also,the error code and error subcode included inthe NOTIFICATION message are displayed.

Remedial Action The BGP static peering session will attempt tore-establish after the time interval specified inthe alarm. See RFC1771, section 4.5 for a listof the possible error codes and error sub-codes. For some error types a subsequentpeer establishment attempt may succeedwithout operator intervention. For other errortypes, operator intervention may be required,for example, a configuration error may be in-dicated.



6.311 MSS_7021_0100A

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = Instance string identifier of the Virtu-alRouter component {address} = IP address ofthe BGP peer BGP has received a NOTIFICA-TION message from a BGP peer. This BGPpeer is transitioning to the idle state. To dis-play the state of a BGP peer display the con-nectionState attribute of the Peer sub-component. The router identification number ofthe local BGP application and the IP addressof the peer which has sent the NOTIFICATIONis included in the alarm text. Also, the errorcode and error subcode included in the NOTI-FICATION message are displayed.

Remedial Action The BGP peering session has reset due tosome error or event (indicated by the errorcode and error subcode of the NOTIFICATIONmessage). The BGP peering session will at-tempt to re-establish every 120 seconds. Op-erator intervention may be required.



6.312 MSS_7021_0100B

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = Instance string identifier of the Virtu-alRouter component Two OSPF routers loc-ated in the same area have the same IP ad-dress provisioned for their OSPF interfaces.The provisioned interfaces can be up or down.Immediate action should be taken to fix thesituation as some OSPF routes will not bereachable and extra traffic generated. The in-formation provided is as follows: Duplicate IPAddress - The duplicate IP address to befixed. Found on RouterId - The first router hav-ing the duplicate IP address. Found on Router-Id - The second router having the duplicate IPaddress. Note that this alarm will be generatedevery few minutes until the problem is fixed.

Remedial Action Use the RouterId values displayed in the alarmto identify the routers that have the same pro-visioned IP address. To display the routerIdvalue of an OSPF router, display the "routerId"attribute under the Ospf sub-component.Change the provisioned IP address on one ofthe routers to eliminate IP address duplication.



6.313 MSS_7021_0100C

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = Instance string identifier of the Virtu-alRouter component {address} = IP address ofthe BGP peer This alarm is generated when aBGP speaker is configured to support ipv4Vpnon the peer, but determines that its peer sup-ports common capabilities other than ipv4Vpn.It indicates that auto discovery information willnot be exchanged over this backbone peersession although the session is establishedwith commonly supported capabilities.

Remedial Action If exchange of IP VPN auto discovery informa-tion is desired across VPN sites over thisbackbone peer session, make sure the BGPsoftware on the remote peer is upgraded tosupport Multiprotocol Extensions Capability.Moreover, the attribute addressFamily underthe Descriptor component of the remote Peermust be provisioned to include ipv4Vpn.



6.314 MSS_7021_0100D

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = Instance string identifier of the Virtu-alRouter component This alarm is generatedwhen a BGP speaker has discovered a privatetunnel endpoint IP address, through auto-discovery, which is not on the same subnet asthe local tunnel endpoint or it happens to bethe same as another private tunnel endpointthat is already discovered. As a result, the in-valid private tunnel address, together with itscorresponding public tunnel address, will notbe populated to both the MultipointStaticEnd-Point and ARP. Also, no corresponding dy-namic BGP peer will be created.

Remedial Action Check the local and remote interface of thetunnel protocol ports and ensure they are onthe same subnet and no duplicate IP ad-dresses are assigned to the interfaces. Note:Auto-discovery will rediscover remote custom-er information if, and only if, the duplicate ad-dress/netmask is fixed on the local interface ofthe tunnel protocol port (i.e. linked to the VCGthat generated the alarm). If the problem is re-solved on a remote interface, a lock/unlock ofthe local customer Vr Ip Tunnel component isrequired to restart auto-discovery.



6.315 MSS_7021_0100E

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = Instance string identifier of the Virtu-alRouter component {address} = IP address ofthe BGP peer This alarm is generated when aBGP speaker on a shared domain virtualrouter has detected that the same VPN ID isbeing used by multiple associated customervirtual routers. As a result, only one of the cus-tomer virtual routers that is provisioned withthis VPN ID participates in auto-discovery.

Remedial Action All customer virtual routers that participate inIP VPN auto-discovery and use the sameshared domain virtual router have to haveunique VPN IDs provisioned. Provision uniqueVPN IDs for those that are duplicates. Note:The VPN ID change should be done on thecustomer Vr that is currently not participatingin auto-discovery.



6.316 MSS_7021_01010

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router {address} =IP address of the BGP peer BGP has receiveda NOTIFICATION message from a BGP peerand the peer has closed the BGP connection.The router identification number of the localBGP application and the IP address of thepeer which has sent the NOTIFICATION is in-cluded in the alarm text. Also, the error codeand error subcode included in the NOTIFICA-TION message are displayed.

Remedial Action The BGP peering session will attempt to re-establish after the time interval specified in thealarm. See RFC1771, section 4.5 for a list ofthe possible error codes and error subcodes.For some error types a subsequent peer es-tablishment attempt may succeed without op-erator intervention. For other error types, oper-ator intervention may be required, for example,a configuration error may be indicated.



6.317 MSS_7021_01011

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router Two OSPFrouters located in the same area have thesame IP address provisioned for their OSPFinterfaces. The provisioned interfaces can beup or down. Immediate action should be takento fix the situation as some OSPF routes willnot be reachable and extra traffic generated.The information provided is as follows: Duplic-ate IP Address - The duplicate IP address tobe fixed. Found on RouterId - The first routerhaving the duplicate IP address. Found onRouterId - The second router having the du-plicate IP address. Note that this alarm is is-sued every few minutes until the problem isfixed.

Remedial Action Use the RouterId values displayed in the alarmto identify the routers that have the same pro-visioned IP address. To display the routerIdvalue of an OSPF router, display the "routerId"attribute under the Ospf sub-component.Change the provisioned IP address on one ofthe routers to eliminate IP address duplication.



6.318 MSS_7021_01012

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {string} = name of the virtual router {address} =IP address of the BGP peer This alarm is is-sued when a BGP speaker is configured tosupport ipv4Vpn or mbgpVpn on the peer, butdetermines that its peer supports commoncapability(ies) other than ipv4Vpn or mbg-pVpn. It indicates that auto discovery informa-tion or VPN routing information will not be ex-changed over this backbone peer session al-though the session is established with com-monly supported capability(ies). In the scen-ario where both ends do not support any com-mon capabilities, the peer session does notestablish and this alarm does not display evenif ipv4Vpn or mbgpVpn is configured. In thiscase, a BGP NOTIFICATION message (witherror code 2 and subcode 7 and containing theunsupported capability(ies)) is expected fromboth ends. The peers will retry with the samecapabilities advertisement repeatedly.

Remedial Action If exchange of the same address families"™ IPVPN information is desired across VPN sitesover this backbone peer session, make surethe BGP software on both the local and re-mote peers are upgraded to support the sameaddress families and capabilities. Moreover,the attribute addressFamily under both the loc-



al and the remote Peer Descriptor componentmust be provisioned to be the same.



6.319 MSS_7021_01013

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router This alarmis issued when a BGP speaker has discovereda private tunnel endpoint IP address, throughauto-discovery, which is not on the same sub-net as the local tunnel endpoint or it happensto be the same as another private tunnel end-point that is already discovered. As a result,the invalid private tunnel address, togetherwith its corresponding public tunnel address,will not be populated to both the Multipoint-StaticEndPoint and ARP. Also, no correspond-ing dynamic BGP peer will be created.

Remedial Action Check the local and remote interface of thetunnel protocol ports and ensure they are onthe same subnet and no duplicate IP ad-dresses are assigned to the interfaces.



6.320 MSS_7021_01014

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router This alarmis issued when a BGP speaker on a shareddomain virtual router has detected that thesame VPN ID is being used by multiple associ-ated customer virtual routers. As a result, onlyone of the customer virtual routers that is pro-visioned with this VPN ID participates in auto-discovery.

Remedial Action All customer virtual routers that participate inIP VPN auto-discovery and use the sameshared domain virtual router have to haveunique VPN IDs provisioned. Provision uniqueVPN IDs for those that are duplicates.



6.321 MSS_7021_01015

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip MBgpRtr/{string2} Vrf/{string3}

Severity warning

Status message

Detail {string} = name of the virtual router {string2} =name of the router {string3} = name of theVRF component This alarm is issued whenMBGP on the customer VR (cVR) attempts toimport/export more VPN routes than specifiedby the provisionable maximum number ofroutes allowed to be imported and exported forthat cVR. This alarm is also generated whenVRF attempts to import/export more 2547 VPNroutes than specified by the provisionablemaximum number of routes allowed to be im-ported and exported for that VRF.

Remedial Action Provision appropriate import/export policies tolimit the number of routes being imported ex-ported.



6.322 MSS_7021_01016

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {string} = name of the virtual router A uniqueLink State Identifier can not be assigned to aself-originated type 3, 5 or 7 LSA. In that case,the LSA is discarded and routing to the subnetor external address may be affected. Thisproblem can occur if there are destination ad-dresses in the network with the same networknumber but different netmask lengths. Thecomment data and the operator data have rel-evant information to resolve the error. Thealarm provides the following information: Area- The area to which the LSA belongs.LSA type- The type of the LSA.Network number - Thenetwork number of the LSA.Network mask -The network mask of the LSA.

Remedial Action Remove the duplicate network number bymodifying the network configuration or OSPFexport policy.



6.323 MSS_7021_01017

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {string} = name of the virtual router An LSA in-stalled in the OSPF Link State Database onthe Active CP/XC can not be journaled to theStandby processor because its size is toolarge. This alarm indicates that this eventcause the CP or XC to be degraded. On a CPor XC switchover, only this VR instance willforce the re-convergence of the Link Statedatabase with its OSPF neighbors.

Remedial Action Lock the VR IP OSPF component in questionand the degraded state is removed.



6.324 MSS_7021_01018

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Bgp Peer/{addr}Router/{string}Bgp Peer/{addr}

Severity major

cleared

Status set

clear

Detail {string} = Instance string identifier of therouter/virtual router component {addr} = IPv4addr of peer If the status is set, a badly au-thenticated TCP segment has been receivedfrom this BGP peer. The Md5Key the segmentwas encoded with does not match the provi-sioned Md5Key information for this BGP Peer.A clear is issued when 10 minutes passwithout the receipt of a badly authenticatedTCP segment from this BGP Peer, or if theBGP Peer is locked or deleted.

Remedial Action Verify that the BGP peers are configured withthe same key. If the keys are the same, identi-fy the source of the intrusion using the dataprovided in the alarm. Some MD5 BGP/TCPimplementations has been observed to sendunauthenticated packets when the underlyingTCP connection has dropped. Thus, this alarmmight be produced when the underlying TCPconnection drops and is re-established. Thisalarm causing condition should not persist.The authentication counters under the BGPpeer will be incrementing if the problem is amismatched key or possibly an attack.



6.325 MSS_7021_01019

RNC Type • POC

• 9370 RNC

Component Router/{x} BgpRouter/{x} Vrf/{y} BgpVr/{x} IpBgp

Severity critical

Status message

Detail {x} = name of the router/virtual router compon-ent {y} = name of the Vrf component Thisalarm is triggered when the bgpImportRoute-Limit and/or the bgpImportRouteLimitDiscardattributes, which both reside under the bgpcomponent are overstepped. The bgpIm-portRouteLimit specifies the maximum numberof bgp ipV4Unicast imported routes that will beprocessed until an alarm is generated. Thislimit is provisionable due to the requirementsunder various different network configurations.The bgpImportRouteDiscardLimit specifies themaximum number of bgp ipV4Unicast importroutes that will be processed until routes arediscarded. This limit is provisionable due to therequirements under various different networkconfigurations.

Remedial Action Decrease the number of bgp ipV4Unicast im-ported routes or changed the threshold atwhich the alarm is generated.



6.326 MSS_7021_01020

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {instance} = 0 - 15 The connection pool capa-city of the Lp has been exhausted. The VirtualMedia Interface is unable to configure connec-tions for IP Tunnel Optimization, thus IP Tun-nels using this access card will revert to no-tOptimized mode. This will reduce the numberof IP interfaces supported on the shelf.

Remedial Action If IP Tunnel Optimization is not enabled on anyIP Tunnels, this alarm may be safely ignored.This problem is typically encountered whenthe Lp/{instance} Eng Arc Ov ConnectionPool-Capacity attribute has been provisioned to alow value. Raising this value will eliminate theproblem. Four connections are required perVirtual Media Interface in alwaysUpSummarymode. Alternatively, the connection pool maybe exhausted by a large number of connec-tions on the Lp. In this case, either raise thevalue of the connectionPoolCapacity attribute,or reduce the number of connection on the Lp.



6.327 MSS_7021_01021

RNC Type • POC

• 9370 RNC

Component Vr/{y}

Severity major

Status message

Detail {string} = name of the virtual router In prepara-tion for a Hitless Software Migration, the Pro-tected Route software performed a check andfound that not all Protected Static Routes havesufficient protection to survive a Hitless Soft-ware Migration (at least one operationalNextHop destined for the Service Shelf, ANDat least one operational NextHop destined forthe Migration Shelf). The migration activationcommand is paused so that the problem canbe investigated and corrected. The migrationprocedure can then be continued or abortedby the operator via the "continue prov" and"stop prov" commands respectively. Note thatcontinuing the migration with Protected Routeshaving insufficient protection will result in largeoutages for flows using these routes.

Remedial Action Diagnose and fix the reason for the failedNextHop status, and restart the software mi-gration procedure OR, modify the provision-able migrationBehaviour of LPs within the Lp-Group configuration in order to correct theproblem of insufficient protection, or to ensurethat as many Protected Static Routes as pos-sible are operational, at least on the Service-side of the split shelf. Generally. unprotectedcards in the Service shelf will experience lessHSM outage than unprotected cards in the Mi-gration shelf; but one should note that this not



always true.



6.328 MSS_7021_01022

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Static Route/{destAddr},{destMask}, {tos}

Severity major

cleared

Status set

clear

Detail {string} = name of the virtual router {destAddr}= address of static route {destMask} = mask ofstatic route {tos} = typeOfService for staticroute All nextHops under the specified staticRoute have failed to respond to Static Heart-beat monitoring. Passport's Static Heartbeatmonitoring consists of ICMP Echo messages.A nextHop router must reply within 1 secondor the nextHop heartbeat is deemed to havefailed.

Remedial Action Diagnose the L3 connectivity issue with thenextHop routers configured for the specifiedstatic route. Ping the nextHop routers and ex-amine round-trip-delay values.



6.329 MSS_7021_01051

RNC Type • POC

• 9370 RNC

Component For Passport 6400: Vr/{string} Ip IpVrrp

Severity warning

Status message

Detail {string} = name of the virtual router TheTimeToLive field in the IP header of the re-ceived VRRP packet is not equal to 255. Thisfield is used to provide sanity check on theVRRP packet.




6.330 MSS_7021_01052

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router The Ver-sion field in the VRRP header of the receivedVRRP packet is not correct. This could becaused by using an obsolete version of soft-ware.

Remedial Action Upgrade the node with VRRP version 2 soft-ware.



6.331 MSS_7021_01053

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router The advert-isement interval timers are provisioned withdifferent values for the same VRRP on differ-ent routers.

Remedial Action Change provisioning on the routers.



6.332 MSS_7021_01054

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router Checksumof the received VRRP packet is incorrect. Net-work could be in an unstable state.




6.333 MSS_7021_01055

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router IP ad-dresses received in the VRRP packet do notmatch the locally provisioned addresses.

Remedial Action Change the provisioned IP addresses on therouters.



6.334 MSS_7021_01056

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router An un-known VRRP authentication type was receivedin the advertisement. The only authenticationtype supported by the node"™s implementa-tion is "No authentication" . This correspondsto a value of 0 in the authentication field of theVRRP advertisement.

Remedial Action Change the authentication method on the non-Multiservice Switch routers to use "No authen-tication" .



6.335 MSS_7021_01057

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Vrrp

Severity major

cleared

Status set

clear

Detail {string} = name of the virtual router This alarmis raised when the provisioned VRRP Master(provisioned priority of 255) can no longerfunction as Master. The reason may be one ofthe following: "the VRRP instance is locked""the corresponding Protocol Port is down" "thecorresponding Critical Ip Port is down" "thecorresponding interface is down"

Remedial Action If the alarm is one of the following, do the fol-lowing to clear the alarm: "the VRRP instanceis locked" - unlock the VRRP Port."the corres-ponding Protocol Port is down" - Ensure prop-er physical connectivity or a lock of the physic-al interface."the corresponding Critical Ip Portis down" - the critical IP link associated to theVRRP is down. The critical IP link maybelocked or there is a physical connectivity prob-lem."the corresponding interface is down" -check the physical connectivity of the physicallink.



6.336 MSS_7021_01059

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router This alarmoccurs when the Backup VRRP Instance hasbecome Master. This is a result of the Backupfailing to receive VRRP Advertisements fromthe Master VRRP Instance.

Remedial Action For the Backup VRRP Instance to becomeMaster, the expected Master VRRP most likelywould have lost connectivity to the LAN. Theoperator should debug to understand why thatmay have occurred.



6.337 MSS_7021_01060

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router This alarmoccurs as a result of a provisioned BackupVRRP, returning to a Backup state after beingMaster.

Remedial Action No remedial action is expected.



6.338 MSS_7021_01061

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {string} = name of the virtual router This alarmis raised when the non-provisioned VRRPMaster (provisioned priority of 255) can nolonger function as Master. The reason may beone of the following: "the VRRP instance islocked" "the corresponding Protocol Port isdown" "the corresponding Critical Ip Port isdown" "the corresponding interface is down"

Remedial Action If the alarm is one of the following, do the fol-lowing to clear the alarm: "the VRRP instanceis locked" - unlock the VRRP Port"the corres-ponding Protocol Port is down" - Ensure prop-er physical connectivity or a lock of the physic-al interface."the corresponding Critical Ip Portis down" - the critical IP link associated to theVRRP has gone down. The critical IP linkmaybe locked or there is a physical connectiv-ity problem."the corresponding interface isdown" - check the physical connectivity of thephysical link.



6.339 MSS_7021_01100

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router A changeoccurred in the state of the OSPF non-virtualneighbor. This change can either be due to aneighbor state regressing or progressing to theFull terminal state. In the case of the broad-cast or non-broadcast multi-access networks,this alarm should be generated by the desig-nated router. The information provided is: osp-fRouterId - the originator of the alarm. ospfN-brIpAddr - the IP address of the neighbor's in-terface. ospfNbrAddressLessIndex - the IfInd-ex of the interface. ospfNbrRtrId - the router idof the neighbor. ospfNbrState - the new stateof the neighbor.

Remedial Action Verify the running status of the router corres-ponding to this OSPF neighbor. The commentdata and the operator data has all the neces-sary information to correct this problem.



6.340 MSS_7021_01101

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router When arouter receives an invalid LSA (ip address isnot zero but the production of ip address andip mask is zero) from other routers, it gener-ates this alarm. We learn who generated thisinvalid LSA (from advertising router andsource ip address fields) and why it is invalid(from net address and net mask fields). Usethis information to determine if there is anymisconfiguration from the sender.

Remedial Action When the alarm is generated, an invalid LSAis received. Use the information generated bythe alarm for the invalid LSA (adv_rtr, src_ip)and the reason why it is invalid (net_addr,net_mask), to find out if there is any misconfig-uration from the sender.



6.341 MSS_7021_01102

RNC Type • POC

• 9370 RNC

Component Rtr/{x} Bgp Peer/{y}

Severity critical

Status message

Detail {x} = name of the router {y} = peerAddress ofIP address This alarm is triggered by overshooting a provisioned number of BGP Ipv4Unicast routes processed by a bgp peer. Theprovisioned values can be changed by editingthe bgpPeerRouteLimit and the bgpPeer-RouteDiscard attributes. If the alarm istriggered by the bgpPeerRouteDiscard attrib-ute, subsequent bgp routes will not be impor-ted.

Remedial Action Raise the provisioned bgpPeerRouteLimit andbgpPeerRouteDiscard attributes to allow moreroutes to be imported by the bgp peer. Other-wise, change network configuration to moreevenly distribute imported routes per bgp peer.



6.342 MSS_7021_01103

RNC Type • POC

• 9370 RNC

Component Vr/{x} Ip Opsf

Severity warning

Status message

Detail {x} - name of the Vr (VirtualRouter) {y} - nameof the rtr (Router) {z} - name of the Vrf(VpnRouteForwarder) According to RFC 2328,every OSPF router should assign unique LSIDfor each LSA that it originates. However, this isnot always true. This new alarm is to inform re-ceiving a LSA whose LSID is the same as butnet mask is different from the one in the OSPFlink state database. The alarm has no impactto the system. When the alarm is seen, thenetwork operator should look into the LSA ad-vertising router, reconfigure that router and re-move the duplicate LSID condition. For MSS,when LSAs with duplicate LSID are received, iftheir LS type and advertising router are alsothe same, only one of the LSA instances(though their masks can be different) is savedand kept in OSPF link state database.

Remedial Action When the alarm is seen, the network operatorshould look into the LSA advertising router. Ifthe advertising router is a Alcatel-Lucentdevice, contact Alcatel-Lucent technical sup-port immediately.



6.343 MSS_7021_01104

RNC Type • POC

• 9370 RNC

Component Vr/{x} ip ospf

Severity warning

cleared

Status set

clear

Detail {x} = name of the virtual router A change oc-curred in the state of the OSPF static neigh-bor. This change can either be due to a neigh-bor state regressing or progressing to Full ter-minal state. Because we only have staticneighbor provisioned on non-broadcast multi-access and point-to-multipoint networks, thisalarm is generated under these types of net-works. The following information is provided:ospfRouterId - the originator of the alarmosp-fNbrIpAddr - the IP address of the neighbor'sinterfaceospfNbrAddressLessIndex - the IfInd-ex of the interfaceospfNbrRtrId - the router idof the neighborospfNbrState - the new state ofthe neighbor

Remedial Action Verify the running status of the router corres-ponding to the OSPF static neighbor. Thecomment data and the operator data has allthe necessary information to correct the prob-lem.



6.344 MSS_7021_01200

RNC Type • POC

• 9370 RNC

Component Rtr/{rtr_id} Isis

Severity warning

Status message

Detail {rtr_id} = name of the virtual router ISIS has re-ceived a corrupted LSP packet. The LSP willbe ignored.

Remedial Action No remedial action is required.



6.345 MSS_7021_01202

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router ISIS has re-ceived a a packet with an invalid sequencenumber. This packet will be ignored.




6.346 MSS_7021_01203

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router ISIS has re-ceived a packet with a System ID length that isdifferent from the one with which it is con-figured.




6.347 MSS_7021_01204

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router ISIS has re-ceived a packet with a Maximum Area Ad-dresses field that is different from the one withwhich it is configured.




6.348 MSS_7021_01205

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router ISIS is pur-ging its own LSP from the DB.




6.349 MSS_7021_01206

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {rtr_id} = name of the virtual router The ISISLink State Database has exceeded 90% of itsLSP storage capacity.

Remedial Action Verify that the number of LSPs generated bynodes within an ISIS Level-1 area doesn"™texceed the current threshold.



6.350 MSS_7021_01208

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router Local ISIShas received its own LSP with a higher se-quence number. The sequence number of thelocal LSP will be skipped.




6.351 MSS_7021_01209

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router ISIS has re-ceived a packet with an unsupported versionnumber.




6.352 MSS_7021_01210

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router ISIS has re-ceived a packet with a supported protocol typethat is different from the one with which it isconfigured.

Remedial Action Processing.



6.353 MSS_7021_01211

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router ISIS has re-ceived a packet with an area ID type that doesnot match any of the area IDs that are suppor-ted by this router, as specified in the Rtr IsisNet components.

Remedial Action Verify that the source and local nodes are con-figured with at least one area address in com-mon.



6.354 MSS_7021_01212

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router ISIS has re-ceived a packet that is too large to propagateout of one of its interfaces.




6.355 MSS_7021_01213

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router An adja-cency state with a neighboring node haschanged.




6.356 MSS_7021_01214

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router ISIS pro-tocol activity has generated a failed request forsystem memory.

Remedial Action Allocate more memory for IP from the Rtr.



6.357 MSS_7021_01215

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {rtr_id} = name of the virtual router The ISISprotocol is configured to run on an unsuppor-ted media type.

Remedial Action Ensure all of the ISIS interfaces are configuredonly on LAN or ATM media.



6.358 MSS_7021_02000

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Rip

Severity warning

Status message

Detail {string} = name of the virtual router RIP is outof memory. RIP service is restarted with all theprovisioned data. If more memory is not alloc-ated for IP, the problem may repeat. The com-ment data and the operator data contains thevirtual router identifier that owns this IP ser-vice.

Remedial Action RIP has restarted because of lack of memory.To avoid similar problems in future, allocatemore memory for IP from Vr.



6.359 MSS_7021_02400

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Arp

Severity warning

Status message

Detail {string} = name of the virtual router The MSSreceives an inverse ARP reply when TPA(target protocol address) = 0.0.0.0 and SPA(source protocol address) = IP address of theremote end that is at fault. The TPA should notbe zero, but equal to one of the local IP logicalinterface addresses on the MSS. Otherwise,the ARP entry of the virtual router on MSS failsto be resolved.

Remedial Action To avoid this problem, make sure the remoteend is compliant with RFC 1293 or RFC 2225.



6.360 MSS_7021_02500

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Tunnel Msep/{num}

Severity warning

Status message

Detail {string} = Instance string identifier of the Virtu-alRouter component {num} = 0 - 1 DuplicateTunnel MultipointStaticEndPoint source IP ad-dresses have been provisioned.

Remedial Action Reprovision the Tunnel MultipointStaticEnd-Points so that they have unique source IP ad-dresses.



6.361 MSS_7021_02501

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Tunnel Msep/{num}

Severity warning

Status message

Detail {string} = name of the virtual router {num} = 0 -1, numeric Msep instance This alarm is issuedwhen an IP TunnelMultipointStaticEndPoint at-tempts a discovered Tunnel destination IP ad-dress (DA) that is equal to the provisionedMultipointStaticEndPoint source IP address(SA).

Remedial Action Verify that all IP Tunnel MultipointStaticEnd-Points within the same VPN have uniquesource IP addresses.



6.362 MSS_7021_02502

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string1} = name of the virtual router {string2} =name of the protocol port Duplicate TunnelMultipointStaticEndPoint source IP addresseshave been provisioned under the tunnel end-point as indicated by the 'linkToMedia' attributein the 'ProtocolPort' component.

Remedial Action Reprovision the Tunnel MultipointStaticEnd-Points so that they have unique source IP ad-dresses.



6.363 MSS_7021_02503

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string1} = name of the virtual router {string2} =name of the protocol port This alarm indicatesthat an IP tunnel endpoint as indicated by the'linkToMedia' attribute in the 'ProtocolPort'component could not be fully initialized inhardware due to hardware resource unavailab-ility. The IP tunnel endpoint remains in soft-ware, resulting in a performance degradationrestricted to this endpoint.

Remedial Action Frequent occurrences of this condition indicatethat the number of IP tunnel endpoints reques-ted to be setup in hardware on this FP ex-ceeds the hardware resources available onthis FP. Contact your local Alcatel-Lucenttechnical support group for assistance if ne-cessary.



6.364 MSS_7021_03000

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Egp

Severity warning

Status message

Detail {string} = name of the virtual router EGP is outof memory. EGP service is restarted with allthe provisioned data. If more memory is not al-located for IP, the problem may repeat. Thecomment data and the operator data containsthe virtual router identifier that owns this IPservice.

Remedial Action EGP has restarted because of lack of memory.To avoid similar problems in future, allocatemore memory for IP from Vr.



6.365 MSS_7021_04000

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {string} = name of the virtual router IP Rtm isout of memory. IP Rtm service is restarted withall the provisioned data. If more memory is notallocated for Ip, the problem may repeat. Thecomment data and the operator data containsthe virtual router identifier that owns this IPservice.

Remedial Action Ip Rtm has restarted because of lack ofmemory. To avoid similar problems in future,allocate more memory for IP from Vr.



6.366 MSS_7026_01000

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = Enet and Fi {num2} =0 - 5 When the status is set, diagnostics havedetected a fault with the hardware associatedwith this port. The comment text of the alarmwill indicate the nature of the fault. The portwill remain out of service until action is takento correct the fault. Diagnostics can be re-executed by locking and unlocking the com-ponent. A clear is issued when diagnosticshave executed successfully.

Remedial Action When the status is set, discontinue the use ofthe port. Provision and alternate port, activatethe standby card, or replace the card if pos-sible. When the status is clear, no remedial ac-tion is necessary.



6.367 MSS_7026_01001

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = Enet and Fi {num2} =0 - 5 When the status is set, diagnostics havedetected a fault with the hardware common toall ports on this card. The comment text of thealarm will indicate the nature of the fault. Thisport (and any others on the same Lp) will re-main out of service until action is taken to cor-rect the fault. Diagnostics can be re-executedby locking and unlocking the component. Aclear is issued when diagnostics have ex-ecuted successfully.

Remedial Action When the status is set, discontinue the use ofall ports on this Lp. Activate the standby card,or replace the card if possible. When thestatus is clear, no remedial action is neces-sary.



6.368 MSS_7026_01002

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {type} = Enet and Fi {num1} = 0 - 15 {num2} =0 - 5 The status is set when diagnostics havedetected an error in the hardware or softwareconfiguration of this card. The comment text ofthe alarm will indicate the nature of the fault.This can include a missing FPGA file, or amissing hardware component. The port (andany others on the same Lp) will remain out ofservice until action is taken to correct the fault.Diagnostics can be re-executed by locking andunlocking the component. A clear is issuedwhen diagnostics have executed successfully.

Remedial Action When the status is set, discontinue the use ofall ports on this Lp. If the alarm comment textindicates that a required file is missing, ensurethat the correct revision of the file is present inthe correct directory on the CP disk. If thealarm comment text indicates that a requiredhardware component is missing, activate thestandby card, or replace the card if possible.When the status is clear, no remedial action isnecessary.



6.369 MSS_7026_02000

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = Enet and Fi {num2} =0 - 5 This alarm is issued if a fundamental in-ternal operation fails during initial provisioningof the component. The comment text of thealarm should indicate the nature of the failedoperation. The alarm may be preceded by re-lated software alarms.




6.370 MSS_7026_02002

RNC Type • POC

• 9370 RNC


Severity critical

Status message

Detail {num1} = 0 - 15 {type} = Enet and Fi {num2} =0 - 5 This alarm is issued if a fundamental in-ternal operation fails during initial provisioningof the component. The comment text of thealarm should indicate the nature of the failedoperation. The alarm may be preceded by re-lated software alarms.




6.371 MSS_7026_02003

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = Enet and Fi {num2} =0 - 5 The status is set when an attempt to putthis component into service has failed becausethe LanTest subcomponent is in a manufactur-ing, design verification, or product integrity testmode. This mode can only be entered if allports on the FP are out of service, and theLanTest subcomponent associated with one ofthe ports is placed in the Manufacturing/DVT/PI test mode. This mode is not intendedfor end-user use. When the status is clear, thecomponent may be placed into service.

Remedial Action When the status is set, reset the Lp associatedwith the component. When the status is clear,no remedial action is necessary.



6.372 MSS_7026_02004

RNC Type • POC

• 9370 RNC


Severity critical

Status message

Detail {num1} = 0 - 15 {type} = Enet and Fi {num2} =0 - 5 This alarm is issued during initial provi-sioning of the component if a MAC address isnot available for the component. This can becaused by a hardware failure that interfereswith the distribution of MAC addresses to theLp. It could also be caused if another compon-ent is using the MAC address designated forthis component. If this is the case, this alarmshould be preceded by a software alarm indic-ating that a requested MAC address ID isalready in use.




6.373 MSS_7026_03000

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {num2} = 0 - 5 The status isset when the Ethernet or OamEnet componenthas detected the absence of heartbeat pulseson the twisted pair medium. The port is out ofservice and cannot receive or transmit packetsuntil this condition is cleared. This conditioncan be caused by a bad connection to the eth-ernet cable, or a bad ethernet cable. A clear isissued when heartbeat pulses are detected onthe twisted pair medium.

Remedial Action When the status is set, check the connectionbetween the ethernet port and the ethernetcable. Also check for a faulty cable. When thestatus is clear, no remedial action is required.



6.374 MSS_7026_03001

RNC Type • POC

• 9370 RNC



Status message

Detail {num1} = 0 - 15 {num2} = 0 - 5 {type} = Enet orOamEnet When the status is set, the Ethernetor OamEnet component has detected an LRCerror in a packet being transmitted. This indic-ates that the packet has been corrupted whilein the data path and discarded. This could becaused by a hardware or software failure.Since this error could potentially occur in manyframes, the rate at which the alarm is issuedmay be throttled to avoid flooding the systemwith alarms. The number of packets discardedbecause of LRC errors is included in the countof output packets discarded. The port is nottaken out of service due to this event, but ifLRC errors occur in sufficient number, per-formance will be adversely affected due to thenumber of packets being discarded.

Remedial Action Normally there is no remedial action to betaken. The error could be caused by a hard-ware failure, so running diagnostics may helpisolate the problem. If the error occurs fre-quently or for prolonged periods of time, con-tact your local Alcatel-Lucent technical supportgroup.



6.375 MSS_7026_03002

RNC Type • POC

• 9370 RNC

Component Lp/0 OamEthernet/0


Status message

Detail {num} = 0 This alarm indicates that a CPswitchover event is about to occur due to afailure of one of the initial tests performed onthe OamEthernet port. The initial tests are per-formed on the OamEthernet port prior to it be-ing put into an open and unlocked state. Thisalarm, and the subsequent switchover, dependon the provisionable attribute switchoverOn-Failure being set to enabled.

Remedial Action Check all cables leading from the affected CPEthernet port for breaks or an improper con-nection. If the problem persists the affectedCP card should be removed and replaced withone whose Ethernet port is fully functional.



6.376 MSS_7026_03003

RNC Type • POC

• 9370 RNC



Status message

Detail {num} = 0 This alarm indicates that a CPswitchover event is about to occur due to ashort or break in the line or attached to the CPEthernet port as detected by the steady statelink test. The steady state link test is per-formed on the link connected to the OamEth-ernet port once every minute to determine itsstatus. This alarm, and the subsequentswitchover, depend on the provisionable attrib-ute switchoverOnFailure being set to enabled.

Remedial Action Check all cables leading from the affected CPEthernet port for breaks or an improper con-nection.



6.377 MSS_7026_03004

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {num} = 0 This alarm is issued when theOamEthernet port is provisioned on a PM1based CP card.

Remedial Action Delete the provisioned OamEthernet port.



6.378 MSS_7026_03005

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 0 - 15 {num2} = 0 - 5 {type} = Enet orOamEnet When the status is set, the Ethernetor OamEnet component has detected the ab-sence of heartbeat pulses on the twisted pairmedium for the standby CP. The port in thestandby CP is out of service and cannot re-ceive or transmit packets until this condition iscleared. This condition can be caused by abad connection to the Ethernet cable or faultyEthernet cable. A clear is issued when heart-beat pulses are detected on the twisted pairmedium for the standby CP.

Remedial Action When the status is set, check the connectionbetween the Ethernet port and the Ethernetcable. Also check for a faulty cable. When thestatus is clear, no remedial action is neces-sary.



6.379 MSS_7026_03006

RNC Type • POC

• 9370 RNC

Component Lp/{0} OamEthernet/{0}


Status message

Detail {num} = 0 This alarm indicates that a CPswitchover attempt, due to an OamEnet failurecondition, has been suspended due to one ofthe following system conditions:File system issynchronizedCIT is loaded on the standbyFPsrun committed viewStandby port is avail-ableSoftware upgrade is not in pro-gressStandby CP is available A CP switchoverwith one of the above system conditions maycause unnecessary service outages.

Remedial Action Clear the system condition so that the CPswitchover due to the OamEnet failure canproceed. Alternatively, you can perform amanual switchover, switchover -force lp/0, ifthe outages are acceptable.



6.380 MSS_7026_03007

RNC Type • POC

• 9370 RNC

Component LP/0 OamEthernet/0

Severity critical

Status message

Detail This alarm indicates the component is about tobe disabled for one minute and then reinitial-ized, due to the following: a severe fault hasbeen detected in its periodic data path auditperformed on the active CPthe card number ofthe CP is present in the provisionable attributeShelf enhancedFaultDetectionif this is a dualCP and the component Lp/0 attribute stand-byStatus is not providingService After thecomponent is reinitialized, it can be disabledagain if the fault persists, with another issu-ance of this alarm. This cycle will continue untilthe standby CP is ready to take over, the act-ive CP is reset by an operator, or no fault isdetected in the subsequent audit.

Remedial Action If the problem persists, the affected CP cardmust be removed and replaced with onewhose Ethernet port is fully functional.



6.381 MSS_7026_04002

RNC Type • POC

• 9370 RNC

Component Fddi/{instance}

Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts When issued a connection estab-lished by this station possesses the unusualcharacteristic of connecting two PHY"™s ofthe same type. The connection doesn"™t viol-ate the connection policy on both stations in-volved so it was accepted.

Remedial Action No remedial action necessary unless the con-dition occurred unintentionally, then changecabling to correct the condition.



6.382 MSS_7026_04004

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts When this alarm is issued, a connec-tion policy violation has occurred. This meansthat the connection policy for this stationdoesn"™t allow a connection to the neighborsPHY type. The connection will ultimately beestablished or rejected depending on theneighbors connection policy.

Remedial Action When this condition occurs verify cabling ofthis station to its neighbors complies withstandard FDDI convention. If the intention is toviolate the standard FDDI convention for dualattach stations then modify the default connec-tion policy attribute(s) to allow the desired con-nection (For example: if a PHY type A to PHYtype A connection is desired modify the provi-sioning attribute acceptAA in the FDDI com-ponent to enable this connection).



6.383 MSS_7026_04005

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts When this alarm is issued, a connec-tion policy violation has been signalled by oneof this stations neighbors. This means that theconnection policy for the neighboring stationdoesn"™t allow a connection to this stationPHY type. The connection will ultimately beestablished or rejected depending on the con-nection policy of this station.

Remedial Action When this condition occurs verify cabling ofthis station to it"™s neighbors complies withstandard FDDI convention. If the intention is toviolate the standard FDDI convention for dualattach stations then modify the default connec-tion policy attribute(s) to allow the desired con-nection, (e.i. if a PHY type A to PHY type Aconnection is desired modify the provisioningattribute "acceptAA" in the FDDI component toenable this connection.). To eliminate thealarm the neighboring stations connectionpolicy must also be modified to accept thenon-standard connection.



6.384 MSS_7026_04006

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Alarm issued when PCM state ma-chine for a PHY connection that was withheldis restarted.

Remedial Action No remedial action required.



6.385 MSS_7026_04007

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Issued when the FDDI SMT"™s PCMstate machine for a particular PHY is unable toestablish a connection to its neighboring sta-tion.

Remedial Action Verify that the PHY is question is properly con-nected to another active station. This alarmcan be ignored if the users has intentionallyelected to run the FDDI ring in a wrapped con-figuration, where only one PHY is being util-ized If difficulties persist contact your local Alc-atel-Lucent technical support group.



6.386 MSS_7026_04008

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Issued after the FDDI MAC claim pro-cess, and beacon process fail. This alarm isused to signify the stuck beacon fault recoverytrace process in the SMT has been started.This alarm is issued when a fault condition hasoccurred on the FDDI ring. If this station doesnot return to an active state it may mean thatits neighbors have isolated this station as thesource of the fault and removed it from the ringby going into a wrapped configuration.




6.387 MSS_7026_04009

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Issued when the FDDI SMT"™s PCMstate machine receives a trace propagationnotification from its upstream neighbor. Seealarm 7026-4008 for description and scenariothat would cause the occurrence of this alarm.




6.388 MSS_7026_0400A

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Issued as notification of successfulcompletion of the FDDI SMT trace function.This alarm will normally be followed by thealarm 7026-000B to indicate the start of thepath test. See alarm 7026-4008 for descriptionand scenario that would cause the occurrenceof this alarm.




6.389 MSS_7026_0400B

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Notification of the start of the PATHtest. The path test is used to verify this sta-tions H/W for any problems that might effectthe operation of the FDDI ring.

Remedial Action Contact your local Alcatel-Lucent technicalsupport group if the station doesn"™t return toan active operational state, or if this alarm isfollow by the alarm 7026-400D.



6.390 MSS_7026_0400C

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Notification that the path test passedon this station. It is an indication that a prob-lem on the FDDI ring is not being caused bythis station See alarm 7026-400B for addition-al information on the path test.

Remedial Action No action required.



6.391 MSS_7026_0400D

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Notification that the path test failedon this station. It is an indication that a prob-lem on the FDDI ring could be caused by thisstation. See alarm 7026-400B for additional in-formation on the path test.




6.392 MSS_7026_0400E

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Notification that this station is invok-ing the FDDI SMT trace function. This faultisolation procedure is initiated if the claim andbeacon process performed by the MAC areunsuccessful.

Remedial Action If the station returns to an active state no ac-tion is necessary, otherwise, consult your localservice representative for assistance.



6.393 MSS_7026_0400F

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Notification the link error rate has ex-ceeded the warning threshold. Link error mon-itoring detects FDDI symbol errors in a givensample period. A rise in the error rate abovethe warning threshold may result in slightly de-graded performance of the FDDI ring.




6.394 MSS_7026_04010

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Notification the link error rate has ex-ceeded the cutoff threshold. When the errorrate reaches this level it is sufficiently criticalthat the link between the two PHY"™s experi-encing the errors is terminated to avoid severeperformance degradation of the entire ring dueto a single link. The connection will be restoredprovided the link confidence test is passedduring the physical connection signalling pro-cess.

Remedial Action If condition persists or the connection remainsdisabled contact your local Alcatel-Lucenttechnical support group.



6.395 MSS_7026_04011

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts Notification the link confidence testhas failed during the attempt to establish aconnection with the neighboring station. Thelink confidence test (LCT) is used to verify theconnection quality prior to allowing a station toparticipate in the FDDI ring.

Remedial Action Verify the cable quality and connection cleanli-ness. If problems persist contact your localAlcatel-Lucent technical support group.



6.396 MSS_7026_04012

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts

Remedial Action This condition is usually caused by local ad-ministration of MAC addresses. Contact yourlocal Alcatel-Lucent technical support group ifproblems persists.



6.397 MSS_7026_04013

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts

Remedial Action If the FDDI station fails to achieve a connec-tion delete the FDDI component and then re-activate the port. Under normal conditions theFDDI SMT should recover from this conditionwithout intervention. Contact your local Alca-tel-Lucent technical support group if problemspersist since there are numerous potentialcauses for this alarm including hardware, orsignal integrity problems.



6.398 MSS_7026_04014

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts When one of the PHY"™s experi-ences an unusual condition that generates anexcessive number of interrupts it may be dis-able to prevent side effects caused by to muchprocessing time being consumed to servicethis condition. Several conditions may causethis alarm, one would be disconnecting or con-necting cables on an active FDDI station.

Remedial Action If the FDDI station fails to establish a connec-tion after this alarm has been issued delete theFDDI component and then reactivate the port.Under normal conditions the FDDI SMT shouldrecover from this condition without interven-tion. Contact your local Alcatel-Lucent technic-al support group if problems persist with a stat-ic cable configuration since there are numer-ous additional conditions that could generatethis alarm including hardware, or signal integ-rity problems.



6.399 MSS_7026_04015

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {instance} = decimal zero for current FDDIproducts When the MAC experiences an un-usual condition that generates an excessivenumber of interrupts it may be disabled to pre-vent side effects caused by to much pro-cessing time being consumed to service thiscondition. Several conditions may cause thisalarm, one would be disconnecting or connect-ing cables on an active FDDI station.

Remedial Action If the FDDI station fails to establish a connec-tion after this alarm has been issued delete theFDDI component and then reactivate the port.Under normal conditions the FDDI SMT shouldrecover from this condition without interven-tion. Contact your local Alcatel-Lucent technic-al support group if problems persist with a stat-ic cable configuration since there are numer-ous additional conditions that could generatethis alarm including hardware, or signal integ-rity problems.



6.400 MSS_7026_05000

RNC Type • POC

• 9370 RNC

Component Lp/{num1} Tr/{num2}

Severity warning

Status message

Detail {num1} = 0 - 15 {num2} = 0 - 5 Issued when anunrecoverable error is encountered by theTMS 380.

Remedial Action If this condition is not caused by a hardwarefailure the port will recover from this without in-tervention. There are numerous additionalconditions that could generate this alarm in-cluding a hardware fault. Contact your localAlcatel-Lucent technical support group if prob-lems persist with a static cable configuration.



6.401 MSS_7026_05001

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {num1} = 0 - 15 {num2} = 0 - 5 Issued when anLRC error detected by the token ring transmithardware. This interrupt implies that a framehas been corrupted some time after being re-ceived but prior to transmission.

Remedial Action This error will cause the port to be off line for aperiod of time, but under normal conditions itwill recover without intervention. There are nu-merous additional conditions that could gener-ate this alarm including a hardware fault. Con-tact your local Alcatel-Lucent technical supportgroup if problems persist.



6.402 MSS_7026_05002

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {num1} = 0 - 15 {num2} = 0 - 5 Issued when aninvalid system request block (SRB) is en-countered by the TMS 380.

Remedial Action This error is not expected under normal condi-tions. Contact your local Alcatel-Lucent tech-nical support group if problems persist sincethis error may indicate a hardware failure.



6.403 MSS_7026_05003

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {num1} = 0 - 15 {num2} = 0 - 5 Issued whenthe station has received a removed requestMAC frame from configuration report server,that has resulted in this station withdrawingfrom the ring.

Remedial Action Modify the configuration report server to allowthis station on the ring. Attempt insertion ofthis station back into the ring by performing alock/unlock sequence on the port.



6.404 MSS_7026_05004

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {num2} = 0 - 5 When thestatus is set, the token ring component has de-tected that no other stations are present on thering. A clear is issued when another station isdetected on the ring.

Remedial Action When the status is set, verify the connection ofother cables to the MAU, and the connectionof the MAU to other MAU"™s. This alarm mayalso occur if all other stations on the ring arepowered down, or off-line for some other reas-on. When the status is clear, no remedial ac-tion is required.



6.405 MSS_7026_05005

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {num2} = 0 - 5 When thestatus is set, the token ring component has de-tected an open or short circuit in the cablebetween the adapter and the MAU. A clear isissued when the condition is no longerpresent.

Remedial Action When the status is set, verify the cable fromthe port to the MAU is securely attached to theMAU. If condition persists verify that the cableand/or the connector on the MAU is not defect-ive. When the status is clear, no remedial ac-tion is required.



6.406 MSS_7026_05006

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 0 - 15 {num2} = 0 - 5 When thestatus is set, the token ring adapter has detec-ted a loss or absence of signal, and was un-able to transmit to itself while wrapped throughits lobe at the wiring concentrator. A clear is is-sued when the condition is no longer present.

Remedial Action When the status is set, verify the cable is se-curely connected to the card. If condition per-sists verify that the cable is not defective.When the status is clear, no remedial action isrequired.



6.407 MSS_7026_05007

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {num1} = 0 - 15 {num2} = 0 - 5 Issued when anerror has been detected during the openphase of initialization. This alarm is issuedwhen conditions such as signal loss, beacon-ing, insertion failure, active monitor ring purgetime out, duplicate address, ring parameterserver not responding, or remove ring stationMAC frame received are present.

Remedial Action The remedial action for this alarm is depend-ent on the specifics provided in the alarm mes-sage. The duplicate address condition must beresolved before attempting another insertioninto the ring. If a remove MAC frame is re-ceived it must be addressed as described inalarm 7026 5003. A beacon MAC frame re-ceived during the physical insertion phasecould indicate a ring speed mismatch ispresent. Another attempt to insert the stationinto the ring can be attempted with a lock/unlock sequence on the port. Contact your loc-al Alcatel-Lucent technical support group ifproblems persist since this error may indicatea hardware failure.



6.408 MSS_7026_05008

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {num1} = 0 - 15 {num2} = 0 - 5 Issued when aninterrupt request from the adapter fails toprovide a stable status value within the allottedtime window.

Remedial Action The remedial action for this alarm to perform alock/unlock sequence on the port. This will al-low the diagnostics to verify the integrity of thehardware. If diagnostics are successful anoth-er attempt will be made to insert the station in-to the ring. Contact your local Alcatel-Lucenttechnical support group if problems persistsince this error may indicate a hardware fail-ure.



6.409 MSS_7026_05009

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {num1} = 0 - 15 {num2} = 0 - 5 Issued whenthe interrupt rate from the TMS 380 is fasterthan the processing rate for these interrupts.This message would indicate a ring that is un-stable, or experiencing a large number or ex-ceptions.

Remedial Action No remedial action is required, however it isrecommended that a lock/unlock sequence onthe port be performed to verify the integrity ofthe hardware. Contact your local Alcatel-Lu-cent technical support group if problems per-sist since this error may indicate a hardwarefailure on this station or some other station onthe ring.



6.410 MSS_7026_0500A

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {num1} = 0 - 15 {num2} = 0 - 5 Issued when afailure occurs during the TMS 380 bring updiagnostics (BUD) test. The details of the spe-cific problem are provided in the alarm mes-sage.

Remedial Action Perform a lock/unlock sequence on the port toverify a consistent failure. Contact your localAlcatel-Lucent technical support group if prob-lems persist since this error may indicate ahardware failure.



6.411 MSS_7035_00001

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {node name} = name of the node The Statist-ics Management System has detected thatregular statistics update poll for one of the ap-plications whose name is shown in the com-ment data of the alarm record was not suc-cessful after two consecutive attempts. Theresult of not being able to poll is that some ofthe statistics data is not collected properly onCP from LP"™s. Upon LP failures, statisticsdata may be lost forever. The cause of thealarm may be message excessive congestionon the module.

Remedial Action No action is required. The module will auto-matically attempt to poll same statistics againin 15 minutes. If the problem persists contactAlcatel-Lucent support.



6.412 MSS_7035_00002

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {node name} = name of the node The Statist-ics Management System has detected thatmore than one application regular statisticspolls were not successful within last poll cycle.The result of multiple application poll failures isthat the regular poll time duration had in-creased from fifteen minutes to some largervalue. The cause of the alarm may be continu-ous excessive message congestion on themodule.

Remedial Action No action is required. The module will auto-matically attempt to poll same statistics againin next poll cycle. If the problem persists con-tact Alcatel-Lucent support.



6.413 MSS_7039_01000

RNC Type • POC

• 9370 RNC

Component AtmIf/{num1}

Severity minor

cleared

Status set

clear

Detail {num1} =1 - 4095 If the status is set, the AtmIfcomponent in question has detected that thecount of associated troubled connections haschanged from zero to a non-zero. This changein state signifies that at least one of the con-nections associated with this AtmIf componenthas become troubled, where none were be-fore. A clear is issued when the count oftroubled connections associated with this At-mIf component returns to zero.

Remedial Action Display all of the Vpc, Vpt, and Vcc compon-ents associated with the AtmIf component todetermine which ones are troubled.Troubleshoot the problem in the usual manner.See Alcatel-Lucent Multiservice Switch7400/15000/20000 Fault and PerformanceManagement - ATM (NN10600-715) for detailson troubleshooting ATM connections.



6.414 MSS_7039_01001

RNC Type • POC

• 9370 RNC

Component AtmIf/{x}

Severity minor

cleared

Status set

clear

Detail AtmIf/{x} : {x} = 1-4095 AtmIf/{x} Ca Cbr/{y} :{x} = 1-4095, {y} = 0 AtmIf/{x} Ca rtVbr/{y} : {x}= 1-4095, {y} = 0 AtmIf/{x} Ca nrtVbr/{y} : {x} =1-4095, {y} = 0 AtmIf/{x} Ca Ubr/{y} : {x} =1-4095, {y} = 0 The alarm is raised if one ofthe following thresholds is crossed in a 15minutes period, the alarm is cleared if one ofthe following thresholds is not crossed in a 15minutes period: - txCellDiscardThreshold - tx-CellCbrDiscardThreshold - txCellRtVbrDis-cardThreshold - txCellNrtVbrDiscardThreshold- txCellUbrDiscardThreshold

Remedial Action If the alarm is set, it means there is a numberof outgoing cell loss occurring within thatswitch, that may caused by hardware issue orlink performance issue. Customer shall look in-to the issues.



6.415 MSS_7039_01002

RNC Type • POC

• 9370 RNC

Component AtmIf/{x}

Severity minor

cleared

Status set

clear

Detail AtmIf/{x} : {x} = 1-4095 AtmIf/{x} Ca Cbr/{y} :{x} = 1-4095, {y} = 0 AtmIf/{x} Ca rtVbr/{y} : {x}= 1-4095, {y} = 0 AtmIf/{x} Ca nrtVbr/{y} : {x} =1-4095, {y} = 0 AtmIf/{x} Ca Ubr/{y} : {x} =1-4095, {y} = 0 The alarm is raised if one ofthe following thresholds is crossed in a 15minutes period, the alarm is cleared if one ofthe following thresholds is not crossed in a 15minutes period: - txFrameDiscardThreshold -txFrameCbrDiscardThreshold - txFrameR-tVbrDiscardThreshold - txFrameNrtVbrDis-cardThreshold - txFrameUbrDiscardThreshold

Remedial Action If the alarm is set, it means there is a numberof outgoing frames loss occurring within thatswitch, that may caused by hardware issue orlink performance issue. Customer shall look in-to the issues.



6.416 MSS_7039_01003

RNC Type • POC

• 9370 RNC

Component AtmIf/{x}

Severity minor

cleared

Status set

clear

Detail AtmIf/{x} : {x} = 1-4095 AtmIf/{x} Ca Cbr/{y} :{x} = 1-4095, {y} = 0 AtmIf/{x} Ca rtVbr/{y} : {x}= 1-4095, {y} = 0 AtmIf/{x} Ca nrtVbr/{y} : {x} =1-4095, {y} = 0 AtmIf/{x} Ca Ubr/{y} : {x} =1-4095, {y} = 0 The alarm is raised if one ofthe following thresholds is crossed in a 15minutes period, the alarm is cleared if one ofthe following thresholds is not crossed in a 15minutes period: - rxCellDiscardThreshold - rx-CellCbrDiscardThreshold - rxCellRtVbrDis-cardThreshold - rxCellNrtVbrDiscardThreshold- rxCellUbrDiscardThreshold

Remedial Action If the alarm is set, it means there is a numberof incoming cells loss occurring within thatswitch, that may caused by hardware issue orlink performance issue. Customer shall look in-to the issues.



6.417 MSS_7039_01004

RNC Type • POC

• 9370 RNC

Component AtmIf/{x}

Severity minor

cleared

Status set

clear

Detail AtmIf/{x} : {x} = 1-4095 AtmIf/{x} Ca Cbr/{y} :{x} = 1-4095, {y} = 0 AtmIf/{x} Ca rtVbr/{y} : {x}= 1-4095, {y} = 0 AtmIf/{x} Ca nrtVbr/{y} : {x} =1-4095, {y} = 0 AtmIf/{x} Ca Ubr/{y} : {x} =1-4095, {y} = 0 The alarm is raised if one ofthe following thresholds is crossed in a 15minutes period, the alarm is cleared if one ofthe following thresholds is not crossed in a 15minutes period: - rxFrameDiscardThreshold -rxFrameCbrDiscardThreshold - rxFrameR-tVbrDiscardThreshold - rxFrameNrtVbrDis-cardThreshold - rxFrameUbrDiscardThreshold

Remedial Action If the alarm is set, it means there is a numberof incoming frames loss occurring within thatswitch, that may be caused by hardware issueor link performance issue. Customer shall lookinto the issues.



6.418 MSS_7039_02000

RNC Type • POC

• 9370 RNC

Component AtmIf/{num1} Vcc/{num2}{num3}AtmIf/{num1}Vpc/{num4}AtmIf/{num1} Vpt/{num5}AtmIf/{num1} Vpt/{num5} Vcc/{num3}

Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 {num3} =0 - 65535 {num4} = 1 - 4095 {num5} = 0 - 4095If the status is set, the amount of bandwidthprovisioned for the indicated connection ex-ceeds the amount of bandwidth currently avail-able. A clear is issued when the connection isable to get the bandwidth it needs or is de-leted.

Remedial Action Bandwidth is provisioned in the Vcd Tm or VpdTm subcomponent of the Vpc, Vpt, or Vcccomponents. If the alarm is caused by a con-nection associated with an AtmIf component,re-configure the bandwidth until the total provi-sioned bandwidth of all connections on this in-terface falls within the maximum bandwidthlimit that the interface can support. If the alarmis caused by a connection associated with aVpt component, re-configure the bandwidthuntil the total provisioned bandwidth of all con-nections associated with this Vpt componentfalls within the maximum bandwidth limit thatthe VPT can support. You can reduce the pro-visioned bandwidth of one or more connec-tions, delete one or more connections, or in-crease the available bandwidth of the Vpt



component.



6.419 MSS_7039_02001

RNC Type • POC

• 9370 RNC

Component AtmIf/{num1} Vcc/{num2}{num3}AtmIf/{num1}Vpc/{num4}AtmIf/{num1} Vpt/{num5} AtmIf/{num1} Vpt/{num5} Vcc/{num3}

Severity minor

Status message

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 {num3} =0 - 65535 {num4} = 1 - 4095 {num5} = 0 - 4095This alarm indicates that more connectionshave been created under this ATM interfacethan the interface is able to accept. The alarmis caused either by memory exhaustion or byexceeding the provisioned values of themaxVpcs or maxVccs attributes of the Cacomponent. The Ca component can be associ-ated with an AtmIf or a Vpt component. If theATM interface is on a spared port, one or moreconnections on the interface may not bespared. If an FP switchover occurs in thisstate, one or more of the connections may godown. This may or may not come back upafter the switchover. PORS map mode trunkscreate VCCs in order to support PORS con-nections. These connections share the avail-able connection space with ATM SVCs,SPVCs, and PVCs. ATM does not keep trackof the connection space used by PORS. IfPORS map mode trunks are consuming someof the connection space on an ATM interface,ATM may continue to attempt to set up newconnections even though the maxVccs valuehas been reached.

Remedial Action If provisioned values of the maxVpcs or



maxVccs attributes have been exceeded,either reprovision the Ca component or deleteone or more connections. If the alarm wasraised due to memory exhaustion, delete oneor more connections (or other components) toincrease available memory. If IP functionalityis not required on this card, then deallocatememory reserved for IP by setting Lp Eng FcrcPqc Ov ipRoutesPoolCapacity to zero. Verifythe operational value of both the connectionpool capacity attributes(connectionPoolAvailable added to the con-nectionPoolUsage and protectedConnection-PoolAvailable added to the protectedConnec-tionPoolUsage). If these values differ from theactive card to the associated spared card, pro-vision the Lp Eng Arc Ov connectonPoolCapa-city and/or protectedConnectionPoolCapacityaccording to the lower of the two memory ca-pacities.



6.420 MSS_7039_02003

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 {num3} =0 - 65535 {num4} = 1 - 4095 {num5} = 0 - 4095This alarm indicates that more connectionshave been created under the UBR service cat-egory than the service category is able to ac-cept (the maxVpcs and maxVccs attributes ofthe Ubr component). The UBR service cat-egory can be associated with the ATM inter-face or a virtual path terminator (VPT). If thestatus is set, the unspecified bit rate (UBR)connection provisioned exceeds the number ofUBR connections currently available. A clear isissued when the connection is able to get theconnection space it needs or is deleted.

Remedial Action Check the value of the maxVpcs and maxVccsattributes of the Ubr component. If the UBRconnection is associated with the ATM inter-face (AtmIf Ca Ubr), the values of these attrib-utes control the UBR connections for that in-terface. If the UBR connection is associatedwith a virtual path terminator (AtmIf Vpt CaUbr), the values of these attributes control theUBR connections for that VPT. Reprovisionthe Ubr component or delete one or more con-nections.



6.421 MSS_7039_02004

RNC Type • POC

• 9370 RNC

Component AtmIf/{num1} Vcc/{num2}{num3}AtmIf/{num1}Vpc/{num4}

Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 {num3} =0 - 65535 {num4} = 0 - 4095 If the status isset, the amount of bandwidth provisioned forthe indicated connection under the1pOC48SmSrPos FP exceeds 1,198,080kbits/second (OC-24). A clear is issued whenthe connection reduces its provisionable band-width to be equal to or less than 1,198,080kbits/second (OC-24) or is deleted.

Remedial Action Bandwidth is provisioned in the Vcd Tm or VpdTm subcomponent of the Vpc or Vcc compon-ents. If the alarm is raised, reconfigure thebandwidth of the connection to be equal to orless than 1,198,080 kbits/second (OC-24).



6.422 MSS_7039_02005

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 {num3} =0 - 65535 {num4} = 0 - 4095 If the status isset, the amount of bandwidth provisioned forthe indicated connection under the1pOC48SmSrPos FP exceeds the amount ofbandwidth currently available at the selectedingress card datapath. A clear is issued whenthe connection is able to get the bandwidth itneeds or is deleted.

Remedial Action Bandwidth is provisioned in the Vcd Tm or VpdTm subcomponent of the Vpc or Vcc compon-ents. If the alarm is raised, re-configure the re-ceive service labels under Vr Mpls LspGroupAtmSap ConnId Lbls from either odd to evenor even to odd values if enough bandwidth isavailable to admit this connection on the otheringress card datapath. Or you could re-configure the bandwidth until the total provi-sioned bandwidth of all connections on the se-lected ingress card datapath falls within themaximum bandwidth limit that each ingresscard datapath can support.



6.423 MSS_7039_02006

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 {num3} =0 - 65535 {num4} = 0 - 4095 If the status isset, the amount of bandwidth provisioned forthe indicated connection under the1pOC48SmSrPos FP exceeds the amount ofbandwidth currently available at the selectedegress card datapath. A clear is issued whenthe connection is able to get the bandwidth itneeds or is deleted.

Remedial Action Bandwidth is provisioned in the Vcd Tm or VpdTm subcomponent of the Vpc or Vcc compon-ents. If the alarm is raised, re-configure thetransmit service labels under Vr Mpls Lsp-Group AtmSap ConnId Lbls from either odd toeven or even to odd values if enough band-width is available to admit this connection onthe other egress card datapath. Or you couldre-configure the bandwidth until the total provi-sioned bandwidth of all connections on the se-lected egress card datapath falls within themaximum bandwidth limit that each egresscard datapath can support.



6.424 MSS_7039_02007

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 {num3} =0 - 65535 {num4} = 1 - 4095 {num5} = 0 - 4095This alarm indicates that all the traffic shapingrates have been exhausted for all of the ser-vice categories (cbr, rtvbr, nrtvbr, ubr). If thestatus is set, the connection provisioned doesnot have an available traffic shaping rate,since all of the traffic shaping rates have beenused up by the existing connections. A clear isissued when the shaping rate requested by theconnection is available.

Remedial Action Check the traffic shaping and the traffic usageparameters of the AtmIf component. Reprovi-sion the traffic shaping rate of the new connec-tion with one of the existing shaping rates, ordelete one of the existing connections that isusing one of the 32 shaping rates.



6.425 MSS_7039_03000

RNC Type • POC

• 9370 RNC

Component AtmIf/{num1} Vpt/{num2}

Severity minor

cleared

Status set

clear

Detail {num1} =1 - 4095 {num2} = 0 - 4095 If thestatus is set, the Vpt component in questionhas detected that the count of associatedtroubled connections has changed from zeroto a non-zero. This change in state signifiesthat at least one of the connections associatedwith this Vpt has become troubled, wherenone were before. A clear is issued when thecount of troubled connections associated withthis Vpt component returns to zero.

Remedial Action Display all of the Vcc components associatedwith the Vpt component to determine whichones are troubled. Troubleshoot the problemin the usual manner. See Alcatel-LucentMultiservice Switch 7400/15000/20000 Faultand Performance Management - ATM(NN10600-715) for details on troubleshootingATM connections.



6.426 MSS_7039_04000

RNC Type • POC

• 9370 RNC


Severity minor

Status message

Detail {num1} =1 - 4095 The ATM interface has de-tected one or more LRC errors over a onesecond interval. Each LRC error signifies thata potentially corrupted frame was passed tothe interface for transmission. The number ofLRC errors that occurred is included in thealarm text.

Remedial Action LRC errors may be caused either by defectivehardware somewhere in the network, or bytransient network conditions, such as the re-moval or insertion of a card, resetting of acard, enabling or disabling of a bus, running ofa bus test, or enabling or disabling of an ATMconnection. Check to see if any such transientcondition occurred around the time of thealarm; if so, correct the destabilizing condition.Continue to monitor the situation to see if addi-tional LRC error alarms occur; if this alarmcontinues to appear, or if major alarm 70394001 is raised, apply the Diagnosing LRC Er-rors procedure documented in Alcatel-LucentMultiservice Switch 7400/15000/20000 Faultand Performance Management - ATM(NN10600-715).



6.427 MSS_7039_04001

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {num1} =1 - 4095 If the status is set, the ATMinterface has detected multiple LRC errorsover a period of several seconds or more.Each LRC error signifies that a potentially cor-rupted frame was passed to the interface fortransmission. Information describing the num-ber of LRC errors detected by the ATM inter-face is included in the alarm text. A clear is is-sued when no LRC errors have been detectedby the ATM interface for at least 2.5 minutes.Information describing the number of LRC er-rors and the period over which they occurredis included in the alarm text.

Remedial Action Consult the Diagnosing LRC Errors proceduredocumented in Alcatel-Lucent MultiserviceSwitch 7400/15000/20000 Fault and Perform-ance Management - ATM (NN10600-715).



6.428 MSS_7039_05000

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 4095 This alarm is issued by aMultiservice Switch AtmInterface (AtmIf).When the status is set, the total average linkTxUtilization has exceeded the value of thecriticalTxUtilAlarmThreshold attribute for a3-minute period. When the status is clear, thetotal average link TxUtilization has sub-sequently fallen back to a level at or below thecorresponding threshold value for a 3-minuteperiod. For the ATM interface, the total aver-age link TxUtilization is calculated everyminute based on comparing the number ofcells transmitted by the interface with the avail-able link bandwidth.

Remedial Action The utilization threshold has been exceededfor at least three minutes, and depending uponthe threshold level, congestion may be occur-ring on these links. A short term action may beto move some connections off of this link androute them through another path. If this alarmcontinues to be set/cleared over a longer peri-od of time it mean that the average link utiliza-tion is increasing over time. The operatorshould therefore plan to upgrading the link to ahigher speed or add in a second parallel link.



6.429 MSS_7040_00000

RNC Type • POC

• 9370 RNC

Component Vr/{string} Sres

Severity critical

cleared

Status set

clear

Detail {string} = name of the virtual router The identi-fied SourceRouteEndStation (Sres) applicationwas unable to obtain sufficient memory to cre-ate its forwarding table object. Effect:SourceRouteEndStation will not function.

Remedial Action The problem can be corrected by allocatemore memory for the Sres process. This isdone by provisioning the Mm sresMax-HeapSpace attribute under the Vr componentto a higher value. Another way to fix this prob-lem would be to make the Sres RouteEntry ta-ble smaller. This is done by provisioning theSres routeTableNumEntries attribute under theVr component to a smaller value. Changescould also be made in other parts of the sys-tem to leave more memory forSourceRouteEndStation to use.



6.430 MSS_7040_00001

RNC Type • POC

• 9370 RNC

Component Vr/{string} Sres

Severity minor

cleared

Status set

clear

Detail {string} = name of the virtual router The identi-fied SourceRouteEndStation (Sres) applicationwas unable to obtain memory while in opera-tion. Effect: SourceRouteEndStation will con-tinue to operate but will not be able to learn asmany routes as it was provisioned to be ableto learn.

Remedial Action The problem can be corrected by allocatemore memory for the Sres process. This isdone by provisioning the Mm sresMax-HeapSpace attribute under the Vr componentto a higher value. Another solution would be tomake the Sres RouteEntry table smaller. Thisis done by provisioning the Sres routeTableN-umEntries attribute under the Vr component toa smaller value. Changes could also be madein other parts of the system to leave morememory for SourceRouteEndStation to use.



6.431 MSS_7040_00002

RNC Type • POC

• 9370 RNC


Severity minor

Status message

Detail {node name} = name of the node When theSRES feature is enabled on a certain protocolport(s), it should be included in the softwarefeature list of all LAN LPs on the shelf, in orderto allow proper routing of traffic directed to andfrom it. This alarm is issued for all LAN LPsthat do not have Sres included in their soft-ware feature list.

Remedial Action Add the SRES feature to the software featurelist of the LP indicated in the alarm.



6.432 MSS_7041_00000

RNC Type • POC

• 9370 RNC

Component Atmif/{num1} Uni

Severity warning

Status message

Detail {num1} = 1 - 4095 This alarm is issued whenthere is an address provisioned on the Uni andthe same address is registered through ILMI.The provisioned index (primary or alternate)takes precedence over the registered value. (Aregistered address is added to the primarylist.)

Remedial Action Delete the provisioned address.



6.433 MSS_7041_00001

RNC Type • POC

• 9370 RNC

Component Atmif/{num1} Uni

Severity minor

cleared

Status message

Detail {num1} = 1 - 4095 If the status is msg, thealarm that there is no MAC address availablefor the card. If the status is clear, the alarm in-dicates that the Ilmi channel is up and hasstaged.

Remedial Action The shelf that the card is on may be too oldand does not have a MAC address or the ter-mination card is faulty.



6.434 MSS_7041_00050

RNC Type • POC

• 9370 RNC

Component Atmif/{num1} Uni Ilmi

Severity major

cleared

Status set

clear

Detail {num1} = 1 - 4095 If the status is set, the alarmindicates that the ILMI channel is down. If thestatus is clear, the alarm indicates that theILMI channel is up and has staged.

Remedial Action The alarm may be generated if the VCC can-not come up, if there is a protocol error, if theother side issues a cold start, if the provision-ing is mismatched, or if communication on thelink is bad. Check the provisioning on bothends of the Uni and ensure one end is desig-nated the user side and the other end is desig-nated the network side. Check that both endsof the link are provisioned as addressEnabled.Check that the link is transmitting properly.



6.435 MSS_7041_00051

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {num1} = 1 - 4095 The alarm indicates that thelocal Uni and its peer are either both con-figured as Network or are both configured asUser.

Remedial Action Check the provisioning on both ends of the Uniand ensure one end is designated the userside and the other end is designated the net-work side.



6.436 MSS_7041_00052

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 4095 The SET alarm is generatedin the network side of the UNI interface, if ILMIis up and its operatingMode is set to address-RegEnable and the number of addresses re-gistered is zero. The CLEAR alarm is gener-ated if the ILMI goes down or at least one ad-dress is registered in the network side. Thealarm has no impact on the system or theuser.

Remedial Action When the status is SET, then it means that theuser side of the UNI interface has some prob-lems. Need to troubleshoot at the user side ofthe UNI interface. When the status is CLEAR,it means that the problem is cleared and no re-medial action is required.



6.437 MSS_7041_00150

RNC Type • POC

• 9370 RNC

Component Atmif/{num1} {atmif_type} Atmif/{num1} Vpt/{num2} {atmif_type}

Severity critical

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095{atmif_type} = Uni "or" Iisp "or" Pnni If thestatus is set, the alarm indicates that the sig-nalling channel is down. If the status is clear,the alarm indicates that the signalling channelis up.

Remedial Action If the alarm is on during the system startup, itis possible that the "side" attributes for bothends of the signalling channel may not be setproperly (i.e. both ends may have been set touser-to-user or network-to-network).the vpi/vcivalue for the signalling channel for both endsmay not be matched.one end of the signallingchannel was down and the node may requirerestarting. there are errors at the physical layeras indicated by "d -p atmif/{num1} interface"that cause the signalling channel or entire in-terface to be disabled.there are an excessivenumber of "failedConnections" under the UNIsignalling component or AAL5 errors underVCC 0.5 due to incorrect provisioning of thetraffic management parameters for the sig-nalling VCC. Verify that the values displayedby "d -p atmif/{num1} uni sig vcd" are correct.If the {atmif type} is Pnni, it is possible that theRcc channel is not up.



6.438 MSS_7041_00151

RNC Type • POC

• 9370 RNC


Severity critical

Status message

Detail {num1} = 1 - 4095 {num2} = 0 - 4095{atmif_type} = Uni "or" Iisp "or" Pnni The alarmindicates that the local Uni, Pnni or Iisp inter-face has either sent or received a restartAllmessage for all the signalled connections thatare currently active. All connections will be re-leased.

Remedial Action Check that the link is transmitting properly.Check if there are errors at the physical layeras indicated by d -p atmif/{num1} interface thatcause the loss of messages on the signallingchannel. \Check for an excessive number offailedConnections under the UNI signallingcomponent due to incorrect provisioning of thetraffic management parameters for the sig-nalling VCC. Verify that the values displayedby d -p atmif/{num1} uni sig vcd tm are correct.



6.439 MSS_7041_00200

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095{atmif_type} = Uni "or" Iisp "or" Pnni If thestatus is set, the alarm indicates that the Ilmi,signalling or Rcc channel fails to obtain a vccin the local node due to insufficient bandwidth.If the status is clear, the alarm indicates thatthe vcc for the Ilmi, signalling or Rcc channelis created successfully.

Remedial Action User can de-provision some existing PVC/SPVC to release the bandwidth back to thebandwidth pool. Or else, user can clear SVCand return the bandwidth back to the pool.SVC call setup is done by the customer equip-ment. Issuing "clear" command may not be apermanent solution. Reprovisioning of end-point equipment may be necessary.



6.440 MSS_7041_00250

RNC Type • POC

• 9370 RNC

Component Atmif/{num1} Pnni Rcc Atmif/{num1} Vpt/{num2} Pnni Rcc

Severity major

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 If thestatus is set, the alarm indicates that the Rccchannel fails to reach twoWayInside state. Ifthe status is clear, the alarm indicates that theRcc channel has either reached twoWayInsidestate or that a provisioning change it hascaused it to be deleted.

Remedial Action Verify that the Vcc for the Rcc channel is up.Verify that the far end node is in the samepeer group.



6.441 MSS_7041_00251

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 The Vccused for the Rcc channel has gone down.

Remedial Action Check that both ends of the connection are us-ing the same Vpi.Vci for the Rcc.



6.442 MSS_7041_00252

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 TheHello FSM has left the twoWayInside state.

Remedial Action Verify that the Rcc channel is up.Verify thatthe neighbor is in the same peer group.



6.443 MSS_7041_00253

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095 If thestatus is set, the alarm indicates that the HelloFSM has detected a neighbor in a differentpeer group. This prevents the link from beingused for PNNI routing. If the status is clear, thealarm indicates that the Hello FSM has detec-ted that the neighbor is now in the same peergroup. The link will now be used for PNNI rout-ing.

Remedial Action The peer group of this node and/or its neigh-bor needs to be changed in order to makethem be the same value.



6.444 MSS_7041_00300

RNC Type • POC

• 9370 RNC

Component Artg Pnni

Severity major

cleared

Status set

clear

Detail If the status is set, the alarm indicates that theconfigured node is experiencing some memorycongestion. It will no longer be included inroute calculations for call setup requests. If thestatus is clear, the alarm indicates that theconfigured node is no longer experiencingmemory congestion. It will once again be in-cluded in route calculations for call setup re-quests.

Remedial Action The configured node will periodically attemptto allocate the required memory. Once it issuccessful, the condition will be cleared.



6.445 MSS_7041_00301

RNC Type • POC

• 9370 RNC

Component Artg Pnni

Severity major

cleared

Status set

clear

Detail This alarm is issued during initial provisioningof the component if a MAC address is notavailable for the component. This can becaused by a hardware failure that interfereswith the distribution of MAC addresses.




6.446 MSS_7041_00302

RNC Type • POC

• 9370 RNC

Component Artg Pnni CfgNode/{level} Rcc

Severity major

cleared

Status set

clear

Detail {level} = level in the hierarchy This alarm is setwhen one of the following conditions occur:The node is the one initiating the SVC and theSVC integrity timer expires or the Hello stategoes out of 2-way insideThe node is the oneterminating the SVC and the SVCC establish-ment timer expires or the Hello state goes outof 2-way inside. This alarm is cleared whenone of the following conditions occur: Thealarm was previously set and the SVCC RCCHello FSM reaches 2-way insideThe RCCcomponent to the neighbor no longer exists(i.e. when there are no longer any inducing up-links between the two nodes).

Remedial Action To determine what condition is causing thealarm, display the Rcc component helloStateand the Rcc AtmCon component state attrib-utes. If the Rcc AtmCon component state isnot connected, one of the following conditionsmay be present: The SVCC RCC SVC wastorn down due to a network failure.ACTION:Look at the lastFailureCauseCode to determ-ine why the SVC was torn down.The SVC can-not be successfully established. There may bea routing problem or a delay in the notificationof uplink removal from lower levels.ACTION:Look at the lastFailureCauseCode to determ-



ine why the SVC is failing. If the Rcc AtmConcomponent state is connected and the Rcccomponent helloState is Attempt or 1-Way In-side, the following condition may be present:The SVC is up but the Hello protocol runningover the channel is stuck in Attempt state or1-way inside state. If this is the node terminat-ing the SVCC RCC and the helloState is At-tempt, it is possible that the node is waiting foran inducing uplink before starting the Helloprotocol over the channel.ACTION: If this isthe node terminating the SVCC RCC and thehelloState is Attempt, then wait a minute tosee if the condition clears.



6.447 MSS_7041_00400

RNC Type • POC

• 9370 RNC

Component Atmif/{num1} {atmif_type} Atmif/{num1} Vpt/{num2} {atmif type}

Severity warning

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095{atmif_type} = Uni "or" Iisp "or" Pnni This alarmis issued when one or more Spvc or Spvp con-nections are in troubled condition.

Remedial Action At end of each Spvc or Spvp retry period, thisalarm is cleared if none of the Spvc and Spvpconnections are in troubled condition.



6.448 MSS_7041_00401

RNC Type • POC

• 9370 RNC

Component Atmif/{num1}

Severity warning

cleared

Status set

clear

Detail {num1} = 1 - 4095 A major alarm is issuedwhen a specified path connection is changingstate and at least one specified path connec-tion is not using the primary path. A clearalarm is issued when all the specified pathconnections are using the primary path. Prob-able cause:

Remedial Action The network operator should poll the node todetermine which connection is not on theprimary path. If the connection is using a dif-ferent path than the primary path, the networkoperator can use the reconnect command toreestablish the connection to the primary pathwhen it is available.



6.449 MSS_7041_00500

RNC Type • POC

• 9370 RNC


Severity warning

cleared

Status set

clear

Detail {num1} = 1 - 4095 {num2} = 0 - 4095{atmif_type} = Uni "or" Iisp "or" Pnni If thestatus is set, one or more connections underthe given signalling interface have undergonea successful connection recovery. The alarmis only set if these connections are also sub-scribed to path optimization. A clear is issuedwhen the connections have been optimized orreleased.

Remedial Action The OPTIMIZE verb can be applied to the ArtgPnni Reroute component to trigger an optimiz-ation of the connections at the node includingthose at the alarmed interface. The triggeringof an optimization results in an attempt to op-timize the connection. The connection will onlybe rerouted if a better route is available.



6.450 MSS_7041_00600

RNC Type • POC

• 9370 RNC

Component Atmif/{num1} {atmif_type}

Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {atmif_type} = Uni "or" Iisp"or" Pnni If the status is set, one or more of theswitched connections under this ATM interfaceare not currently spared, due to a failure tocreate the connections on the standby port, ordue to a loss of synchronization of the journal-ing software. If alarm 7039 2001 is seenshortly before this alarm occurs, this alarmmay be due to a configuration error. If thisalarm is not accompanied by alarm 70392001, it may be due to a software error. If anFP switchover occurs in this state, one ormore of the connections may go down. Theymay or may not come back up after theswitchover. A clear is issued when all switchedconnections under this ATM interface areagain spared. This may be because the un-spared connections have now been success-fully created on the standby, or because theunspared connections have been deleted.

Remedial Action If the provisioned values of the maxVpcs ormaxVccs attributes have been exceeded (seealarm 7039 2001), either reprovision the Cacomponent or delete one or more connections.Otherwise, contact Alcatel-Lucent global sup-port.



6.451 MSS_7041_00601

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {atmif_type} = Uni "or" Iisp"or" Pnni If the status is set, at least one con-trol channel (Ilmi, Signalling, or Rcc) under thisATM interface is not currently spared, due to afailure to create the control channel on thestandby port, or due to a loss of synchroniza-tion of the journaling software. This alarm maybe due to a configuration error or a softwareerror. If an FP switchover occurs in this state,one or more of the control channels may godown. They may or may not come back upafter the switchover. A clear is issued when allcontrol channels under this ATM interface areagain spared. This may be because the un-spared control channel has now been suc-cessfully created on the standby, or becausethe signalling component that owns the un-spared control channels has been deleted.

Remedial Action If the available bandwidth for the ATM inter-face (Atmif/{num1} Ca poolAvailabilityBand-width) is not sufficient to meet the require-ments of all provisioned connections and thecontrol channels, the provisioned connectionsmay consume all the bandwidth on thestandby card so that the control channels can-not be created. In this case, either increasethe configured bandwidth or delete some pro-



visioned connections. Otherwise, contact Alca-tel-Lucent support.



6.452 MSS_7041_00602

RNC Type • POC

• 9370 RNC

Component ARtg Pnni Top/{level} Node/{node_id}

Severity major

Status message

Detail {level} = The hierarchy level of the originatingnode of the large PTSE {node_id} = The nodeID of the originating node of the large PTSEThis alarm is raised when a large PTSE is re-ceived from a PNNI node and is installed inthe topology database, but it failed to be journ-aled to the standby card.

Remedial Action If the originating node of the PTSE is a nodeand the violating PTSE is an address PTSE,either some of the addresses on the specifiednode must be removed or a summary addressshould be provisioned on the node to summar-ize local addresses.



6.453 MSS_7041_00603

RNC Type • POC

• 9370 RNC

Component ARtg

Severity major

Status message

Detail This alarm is raised when both the followingconditions are met: The Hot PNNI CP HitlessSoftware Migration has been started for a min-imum of 10 minutes (with attribute ARtgSpServ sparing set to enable) without complet-ing successfully.The synchronization of thespared Application Ports between the sparedactive CP and the migration active CP cannotcomplete successfully because at least one ofthe standby FPs is not inserted in the migra-tion active shelf. The alarm indicates whichcard is missing in the migration active shelf.This alarm is pausable and you can eithercomplete the Hitless Software Migration with aloss of service for the applications that arespared by that FP, or you can revert back andreplace (or insert) the missing FP.

Remedial Action There are two options: Continue provisioning,which completes the Hitless Software Migra-tion with a loss of service for the applicationsthat are spared by the missing FP.Stop provi-sioning, which stops the Hitless Software Mi-gration. You can then either add or replace themissing (not working) FP.



6.454 MSS_7041_00604

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {atmif_type} = Uni "or" Iisp"or" Pnni If the status is set, one or more of theprovisioned connections under this ATM inter-face are not currently spared, due to a failureto create the connections on the standby port,or due to a loss of synchronization of thejournaling software. If alarm 7039 2001 is seenshortly before this alarm occurs, this alarmmay be due to a configuration error. If an FPswitchover occurs in this state, one or more ofthe connections may go down. They may ormay not come back up after the switchover. Aclear is issued when all provisioned connec-tions under this ATM interface are againspared. This may be because the unsparedconnections have now been successfully cre-ated on the standby, or because the unsparedconnections have been deleted.

Remedial Action If the provisioned values of the maxVpcs ormaxVccs attributes have been exceeded (seealarm 7039 2001), either reprovision the Cacomponent or delete one or more connections.Otherwise, contact Alcatel-Lucent global sup-port.



6.455 MSS_7041_00605

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {atmif_type} = Uni "or" Iisp"or" Pnni If the status is set, one or more of thestatic addresses under this ATM interface arenot currently spared, due to a failure to createthe addresses on the standby port, or due to aloss of synchronization of the journaling soft-ware. If alarm 7039 2001 is seen shortly be-fore this alarm occurs, this alarm may be dueto a configuration error. If this alarm is not ac-companied by alarm 7039 2001, it may be dueto a software error. If an FP switchover occursin this state, one or more of the addressesmay not be present and routing problems mayoccur. The addresses may or may not be ad-ded to the routing database after theswitchover. A clear is issued when all ad-dresses under this ATM interface are againspared. This may be because the addresseshave now been successfully created on thestandby, or because the addresses have beendeleted.

Remedial Action If the problem persists, contact Alcatel-Lucentglobal support.



6.456 MSS_7041_00606

RNC Type • POC

• 9370 RNC


Severity minor

cleared

Status set

clear

Detail {num1} = 1 - 4095 {atmif_type} = Uni "or" Iisp"or" Pnni If the status is set, one or more of thePNNI PTSEs under this ATM interface are notcurrently spared, due to a failure to create thePTSEs on the standby port, or due to a loss ofsynchronization of the journaling software. Ifalarm 7039 2001 is seen shortly before thisalarm occurs, this alarm may be due to a con-figuration error. If this alarm is not accompan-ied by alarm 7039 2001, it may be due to asoftware error. If an FP switchover occurs inthis state, one or more of the addresses maynot be present and routing problems may oc-cur. The addresses may or may not be addedto the routing database after the switchover. Aclear is issued when all PNNI PTSEs underthis ATM interface are again spared. This maybe because the PTSEs have now been suc-cessfully created on the standby, or becausethe PTSEs have been deleted.

Remedial Action If the problem persists, contact Alcatel-Lucentglobal support.



6.457 MSS_7041_00700

RNC Type • POC

• 9370 RNC

Component Artg Pnni CfgNode/{x}

Severity major

cleared

Status set

clear

Detail {x} = 0 - 104 One of the following three de-scriptions will appear if this alarm is raised: 1)Duplicate Node ID problem: The same NodeID has been provisioned on two nodes adja-cent to this node. If the above is displayed, twoPNNI nodes adjacent to this node have thesame Node ID provisioned. The PNNI Neigh-bor protocol will not stage properly and thus noPNNI topology information will be able to beexchanged. This will cause call routing out-ages. 2) Duplicate Node ID problem: Thesame Node ID has been provisioned on anode within the PNNI Network. If the above isdisplayed, two PNNI nodes within the PNNInetwork have the same Node ID provisioned.The impact of this is that Flooding of PNNI To-pology information will constantly be happen-ing. 3) Duplicate Node ID problem: This nodeand an adjacent node have the same Node ID.If the above is displayed, two PNNI Neighbornodes in an Hierarchical PNNI network havethe same Node ID provisioned. PNNI Neighborprotocol will not stage properly and thus noPNNI topology information will be able to beexchanged. This will cause call routing out-ages.

Remedial Action The action required to correct this problem is



outlined in the following three scenarios: 1)Duplicate Node ID problem: The same NodeID has been provisioned on two nodes adja-cent to this node This alarm will appear on onePNNI Node. Once the PNNI node with thisalarm is detected, go to the PNNI NeighborNodes of the node. Verify the same Node ID isprovisioned under the artg pnni cfg{x} compon-ent. The operator should now provision a dif-ferent Node ID on at least one of these twoPNNI Nodes, and that is also different thanany node other in the PNNI Network. 2) Du-plicate Node ID problem: The same Node IDhas been provisioned on a node within thePNNI Network. This alarm will appear on twoor more PNNI Nodes that have the alarmraised. Once the PNNI nodes with this alarmare detected, verify the same Node ID is provi-sioned under the artg pnni cfg{x} component.The operator should now provision a differentNode ID on at least one of these two PNNINodes, and that is also different than any nodeother in the PNNI Network. 3) Duplicate NodeID problem: This node and an adjacent nodehave the same Node ID. This alarm will ap-pear on two PNNI Nodes in an HierarchicalPNNI network t hat have the alarm raised.Once the PNNI nodes with this alarm are de-tected, verify the same Node ID is provisionedunder the artg pnni cfg{x} component. The op-erator should now provision a different NodeID on at least one of these two PNNI Nodes,and that is also different than any node otherin the PNNI Network.



6.458 MSS_7041_00701

RNC Type • POC

• 9370 RNC

Component Atmif/{num1} Pnni Rcc

Severity major

cleared

Status set

clear

Detail {num1} = 1 - 4095 There is a duplicate (same)Node ID provisioned on two PNNI nodes thatare adjacent to each other (Neighbors). Theimpact of having the same Node ID provi-sioned on two PNNI neighbor nodes is that theRCC channel will not establish, blocking theflow of PNNI topology information.

Remedial Action This alarm appears on two PNNI Nodes. Oncethe two nodes with this alarm are detected,verify the same Node ID is provisioned underthe artg pnni cfg{x} component. The operatorshould now provision a different Node ID on atleast one of these two PNNI Nodes, which isalso different than any other node in the PNNINetwork.



6.459 MSS_7041_00703

RNC Type • POC

• 9370 RNC

Component Artg Pnni CfgNode/{x}

Severity minor

cleared

Status set

clear

Detail {x} = 0- 104 There is a duplicate (same) NodeName provisioned on two or more PNNI nodeswithin the PNNI network. The impact of havingthe same Node Name provisioned on two ormore PNNI nodes is that the topology informa-tion displayed on the node may not be correct.However, there will be no PNNI outages andall internal PNNI information is correct.

Remedial Action This alarm appears on two PNNI Nodes. Oncethe two or more nodes with this alarm are de-tected, verify that the same Node Name is pro-visioned under the mod component. The oper-ator should now provision a different NodeName on the PNNI Nodes that is affected, andthat is also different than any node other in thePNNI Network. Note that changing the Node-Name will cause the node to reset.



6.460 MSS_7041_00800

RNC Type • POC

• 9370 RNC

Component Artg Pnni Lrbg/{x}

Severity major

cleared

Status set

clear

Detail {x} = 1-5 This alarm indicates that the parallellinks in this load re-balancing group are notphysically connected with same remote switch.

Remedial Action Verify the physical connection for all the paral-lel links configured in the load rebalancinggroup. If they are not connected with the sameremote switch, correct the physical connection,or reconfigure the links into different load re-balancing group.



6.461 MSS_7041_00801

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {x} = 1-5 This alarm indicates that the remoteswitch, which is connected by the parallel linksin the load re-balancing group, does not sup-port load re-balancing feature.

Remedial Action Upgrade the remote node to at least PCR7.2.



6.462 MSS_7041_00802

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {x} = 1-5 This alarm indicates that at least oneparallel link in this load re-balancing group ispart of a different load re-balancing group onthe remote switch.

Remedial Action Reconfigure the links in a load re-balancinggroup so that all parallel links are part of thesame group.



6.463 MSS_7042_00001

RNC Type • POC

• 9370 RNC

Component Aal1Ces/{num1}

Severity major

cleared

Status set

clear

Detail {num1} = 1 - 16383 When dummy data hasbeen inserted continuously due to buffer un-derflow for a period equal to the cellLossInteg-rationPeriod, a loss of cells alarm will beraised. The alarm will be cleared when the buf-fer has been re-initialized (i.e. filled to its nom-inal level with valid AAL1 cells), and the ser-vice has subsequently been in operation for acontinuous period equal to ten times thecellLossIntegrationPeriod without experiencingfurther buffer underflow.

Remedial Action Buffer underflow indicates that cells are arriv-ing more slowly than expected, are being lostin the network, or are of the wrong type to beallowed into the buffer (i.e. do not conform tothe AAL1 protocol). Ensure that both ends ofthe connection are provisioned to have thesame traffic rate and that every hop in the net-work has enough bandwidth to carry the traffic.Ensure that cells which are arriving conform tothe AAL1 protocol. The AAL1 cells arriving atthe module from the ATM network are man-aged by a Vcc component under a particularAtmIf component on an ATM FP. Check theOSI states of these components to ensurethey are functioning appropriately. Check therxCell count of the Vcc component to ensure



that cells are actually arriving from the net-work. For more information see theTroubleshooting section of the ATM Core Ser-vices document.



6.464 MSS_7042_00002

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {num1} = 1 - 16383 When AAL1 processing ofreceived cells fails for 2 consecutive seconds,an AAL1 layer alarm will be raised (note thatthis includes the scenario where no cells at allhave been received). The alarm will be clearedwhen AAL1 processing of received cells re-sumes, and has been in synchronous opera-tion for 10 consecutive seconds.

Remedial Action Ensure that cells are being received (checkthe rxCells attribute is incrementing). Ensurethat the remote end system is configured togenerate AAL1 cells, and that the Aal1Ces isassociated with the relevant Vcc which is man-aging the AAL1 cells arriving from the network.Ensure the remote end system is generatingvalid AAL1 data. For example, arrange to havelocal diagnostics run at the far end. Ensurethat received cells are not being discarded dueto congestion on the module. Check the rxDis-card attribute of the relevant Vcc. Ensure thatcells are not being discarded due to noise onthe line. Check the error statistics for the phys-ical port associated with the relevant AtmIf onthe ATM FP.



6.465 MSS_7042_00003

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {num1} = 1 - 16383 When the Aep subcom-ponent of an Aal1Ces component has initiateda number of consecutive unsuccessful callsetup attempts equal to the value of the provi-sioned retryLimit, no further setups are at-tempted and this alarm is raised.

Remedial Action Check the lastSetupFailureCause in the Aepsubcomponent of the Aal1Ces and take appro-priate management action, such as reprovi-sioning. When the appropriate managementaction has been taken, issue a restart againstthe relevant Aep subcomponent to restart theautomatic connection procedure.



6.466 MSS_7042_00004

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {num1} = 0 - 15 {type} = DS3, E1, DS1, SON-ET, and SDH {num2} = 0 - n, where n is 1 lessthan the number of portssupported on the cardtype If the status is set, at least one of theCES connections associated with the physicalport has become inactive where all connec-tions were previously active. A clear is issuedwhen the number of inactive connections, as-sociated with the physical port, returns to zero.

Remedial Action Check the connectionStatus of CES connec-tions associated with the physical port. If theconnectionStatus is atmNotReady, check theATM network. If the connectionStatus is chan-nelNotReady, check the physical port or logic-al port associated with Aal1Ces. If the connec-tionStatus is atmNotConfigured, check theconfiguration of Aal1Ces subcomponent.



6.467 MSS_7042_04201

RNC Type • POC

• 9370 RNC

Component LanApplication/{la} EthernetTrunk Vcc/{vpivci}Nrp

Severity minor

Status message

Detail Additional component: LanApplication/{la} Eth-ernetTrunk Vlan/{vlan} Vpc/{vpi} Nrp {la} = theinstance of the LanApplication service on theshelf {vpi} = virtual path indicator {vci} = virtualconnection indicator The circumstances thatcaused the Ethernet Trunk peers to have dif-ferent P-bit values can be due to the followingfactors that the P-bit values are derived from:the effectiveAtmServiceCategory of the Naile-dUpRelayPoint the provisioned values underthe LanApplication UserPriorityMarking com-ponent the default UserPriorityMarking values(when the LanApplication Upm component isnot provisioned)

Remedial Action The action required is to determine the prob-able cause and modify one or more of thefactors that the P-bit value(s) are derived from.This is detailed in the Operational ProceduresChapter of the FS.



6.468 MSS_7042_04202

RNC Type • POC

• 9370 RNC

Component LanApplication/{la}

Severity minor

cleared

Status set

clear

Detail {la} = the instance of the LanApplication ser-vice on the shelf This alarm is issued when theEthernet Interface has at least one Vlan Trunkthat is offline.

Remedial Action This alarm is cleared when all the Vlan Trunksunder the Ethernet Interface are online. Theprocedures used to determine how to enableall the Vlan Trunks is detailed in the Opera-tional Procedures Chapter of the FS.



6.469 MSS_7054_00100

RNC Type • POC

• 9370 RNC

Component Shelf card/{instance}

Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 Card is not connected to asparing panel. The FP has been unable toconnect to the sparing panel either becausethe cables have been incorrectly connected ora cable fault or due to a problem with the spar-ing panel. Sets the status to major. A clear isissued when the FP successfully connects tothe sparing panel, (cable fault fixed or con-nectivity resolved) or the provisioning hasbeen changed so that the FP does not need toregister, or if a switchover occurs and the FPcomes up as the standby card.

Remedial Action Check the cable for faults or check the provi-sioning is correct and that the FP should beconnected to this sparing panel. Check theconnectivity of the cables. Check that thereare no problems with the sparing panel itself.



6.470 MSS_7054_00101

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 Card is connected to thewrong sparing panel. HSM will not work with a1ForN Sparing panel if the sparingconnectionsare not set. The FP has successfully connec-ted to a sparing panel, but it is not the correctsparing panel either because the cables havebeen incorrectly connected or there is a provi-sioning error. Sets the status to major. A clearis issued when the FP successfully connectsto the correct sparing panel, (connectivity re-solved) or the provisioning has been changedso that the error is resolved.

Remedial Action Check the provisioning is correct and that theFP is connected to the same sparing panel asits spare card. Check the connectivity of thecables.



6.471 MSS_7054_00102

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 Card is connected to thewrong sparing panel port. The card was con-nected to an incorrect port on the sparing pan-el. Sets the status to major. A clear is issuedwhen the FP registers with the correct connec-tion on the sparing panel.

Remedial Action Ensure the card is cabled to the same sparingpanel port for which it is provisioned or changethe provisioned sparing connection to matchthe sparing panel port for which it is cabled.



6.472 MSS_7054_00103

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 Sparing panel not respond-ing. This alarm is used to indicate when an FPis connected to a sparing panel but the sparingpanel is not responding. This can be due to afaulty cable connection, a firmware or hard-ware fault in the sparing panel itself. Thisalarm will be raised when either of the follow-ing occur: 1. During sparing panel monitoring,a sparing panel was detected, but failed toprovide any information to the FP.2. The spar-ing panel did not provide an acknowledgmentof an FP"™s attempt to "#grab"™ a relay. Setsthe status to "major" . A clear is issued whenthe FP receives information from the sparingpanel or gets an acknowledgment of theFP"™s attempt to "#grab"™ a relay.

Remedial Action Check the sparing panel to ensure that it isworking correctly. Check the cable connectivitybetween this shelf card and the sparing panel.



6.473 MSS_7054_00104

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 Spare card is in use. Amain FP had failed and the spare FP took overits failure. Sets the status to "major" . A clear isissued when the spare FP is released.

Remedial Action Replace the main FP if failure is due to a hard-ware problem. A switchover must be issued torelease the spare FP.



6.474 MSS_7054_00105

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = 0 - 15 Spare card is unavailable.The spare card went down or was removedfrom the shelf. This breaks the sparing func-tionality of all LPs sharing this spare card. Setsthe status to "major" . A clear is issued whenthe spare FP comes back up or is re-insertedin the shelf.

Remedial Action Re-insert the spare card in the shelf if it wasremoved. This can also be resolved by provi-sioning a new spare card. Replace the sparecard if it does not come back up.



6.475 MSS_7057_00001

RNC Type • POC

• 9370 RNC

Component DcmeLink/{instance}

Severity major

cleared

Status set

clear

Detail {instance} = instance of the DcmeLink (1-14) Ifthe status is set, the number of rejectedspeech calls has reached a predefinedthreshold over a predefined time interval. Thethreshold value and the time interval are provi-sionable attributes under the correspondingDcme component. A clear is issued when thenumber of rejected speech calls drops belowthe threshold over the subsequent time inter-val.

Remedial Action A large number of rejected speech calls indic-ate that there were no network resourcesavailable to handle these calls. This may bedue to network congestion, failure of networkresources, or misconfiguration of the preestab-lishedConnections attribute under the corres-ponding Dcme component. Verify the availabil-ity of network resources. The network may re-quire re-engineering to handle higher trafficloads. If network resources are available andthe alarm is not cleared, the value of thepreestablishedConnections attribute is too lowfor the actual call rate received from the ISCequipment. If you set the speechAlarm-Threshold attribute to 0, this alarm will not begenerated.



6.476 MSS_7057_00002

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = instance of the DcmeLink (1-14) Ifthe status is set, the number of rejected 3.1kHz calls has reached a predefined thresholdwithin a predefined time interval. The thresholdvalue and the time interval are provisionableattributes under the corresponding Dcme com-ponent. A clear is issued when the number ofrejected 3.1 kHz calls drops below thethreshold in the subsequent time interval.

Remedial Action A large number of rejected 3.1 kHz calls indic-ates that there were no network resourcesavailable to handle these calls. This may bedue to network congestion, failure of networkresources, or misconfiguration of the preestab-lishedConnections attribute under the corres-ponding Dcme component. Verify the availabil-ity of network resources. The network may re-quire re-engineering to handle higher trafficloads. If network resources are available andthe alarm is not cleared, the value of thepreestablishedConnections attribute is too lowfor the actual call rate received from the ISCequipment. If you set the 3kHzAlarmThresholdattribute to 0, this alarm will not be generated.



6.477 MSS_7057_00003

RNC Type • POC

• 9370 RNC


Severity major

cleared

Status set

clear

Detail {instance} = instance of the DcmeLink (1-14) Ifthe status is set, the number of rejected 64Kbits/s calls has reached a predefinedthreshold over a predefined time interval. Thethreshold value and the time interval are provi-sionable attributes of the corresponding Dcmecomponent. A clear is issued when the num-ber of rejected 64 Kbits/s calls drops below thethreshold in the subsequent time interval.

Remedial Action A large number of rejected 64 Kbits/s calls in-dicates that there were no network resourcesavailable to handle these calls. This may bedue to network congestion or failure of networkresources. Verify the availability of network re-sources. The network may require re-engineering to handle higher traffic loads. Ifyou set the unrestricted64kAlarmThreshold at-tribute to 0, this alarm will not be generated.



6.478 MSS_7057_00004

RNC Type • POC

• 9370 RNC


Severity critical

cleared

Status set

clear

Detail {instance} = instance of the DcmeLink (1-14) Ifthe status is set, the DcmeLink negotiationwith the far end DcmeLink component hasfailed. Either the remote and local profile attrib-utes are different or the DNAs are incorrect. Aclear is issued when the negotiation with thefar end is successful.

Remedial Action Verify the profile attributes values and theDNAs at the local and the remote end.



6.479 MSS_7057_00005

RNC Type • POC

• 9370 RNC


Severity minor

Status message

Detail {instance} = instance of the DcmeLink (1-14)This message indicates that an attempt to lockthe DcmeLink component was unsuccessful,because the vsType attribute of at least one ofthe Vs subcomponents was provisioned topermanent64kVs. Locking of this DcmeLinkdisables all of the Vs subcomponents, includ-ing the permanent64kVs type. By definition,this type of Vs component is permanent and itshould not be disabled accidentally. If youneed to lock the DcmeLink component afterthe warning is issued, follow the steps de-scribed in the Remedial action section.

Remedial Action Disable all Vs components with vsType of per-manent64kVs through the LOCK DcmeLink/{instance} Vs/{vsInstance}, then lock theDcmeLink component through the LOCKDcmeLink/{instance} command.



6.480 MSS_7059_00000

RNC Type • POC

• 9370 RNC

Component Vr/{string} Ip Nhrp

Severity major

cleared

Status set

clear

Detail {string} = name of the virtual router When thestatus is set, the number of ResCacheEntryentries used by this Nhrp component is greaterthan 95% of the provisioned maximum. If themaximum number of entries is reached, thesystem automatically releases the oldest 10%of the entries. A clear is issued when the num-ber of ResCacheEntry entries used drops be-low 85% of the provisioned maximum, after aset has been issued.

Remedial Action Provision the Nhrp component with a largermaxResCacheEntries value.



6.481 MSS_7060_01000

RNC Type • POC

• 9370 RNC

Component Lp/{x} Eng Fcrc

Severity major

cleared

Status set

clear

Detail {x} = 0 - 15 IP routes and subconnections orboth overbooking. The number of IP routingentries and/or subconnections has exhaustedthe amount of memory available. Since the Lp/{instance} Eng Fcrc Pqc Ov attributeipRoutesPoolCapacity and the LP/{instance}Eng Fcrc Ov attribute subConnectionPoolCa-pacity share the same pool of memory, it is notalways possible to guarantee the maximumvalue of both of these attributes. The alarm in-dicates the actual number of subconnectionsand/or IP routes allocated.

Remedial Action Decrease the number of IP routing entries inthe Lp/{instance} Eng Fcrc Pqc Ov attributeipRoutesPoolCapacity and/or the number ofsubconnections in the Lp/{instance} Eng FcrcOv attribute subConnectionPoolCapacity. Seteach of them to the maximum value to haveevery type of connection covered and no im-pact on FP load:"¢connCap = Lp eng Arc Con-nectionPoolCapacity = 1000 (necessary forATM-SPY use)"¢protConnCap = Lp eng ArcprotectedConnectionPoolCapacity =29696-1000 = 28696 (Iub TEG) with the ruleConnCap + protConnCap { 29696



6.482 MSS_7060_01100

RNC Type • POC

• 9370 RNC

Component Lp/{x} Eng Arc Aqm/{y}

Severity warning

cleared

Status set

clear

Detail {x} = 0 - 15 {y} = 0 - 3 The value of the txCell-MemoryUsage attribute reaches a high level(that is, the available egress cell memory blockresources reaching a low level). If the status isset, the available egress cell-blocks from thelogical processor"™s specified AQM havefallen below 20% of total egress cell-blocks.Under this condition, traffic flowing across thisAQM on this FP may encounter high queueingdelays. When this condition is detected, lowerpriority traffic is discarded first. If congestionpersists, higher priority traffic is discarded.This continues until available egress cell-blocks for the logical processor"™s AQM haveincreased above 25% of the total egress cell-blocks. A clear is issued automatically at thispoint. A filtering mechanism is implementedsuch that a set/clear is issued by one minute.

Remedial Action Frequent or prolonged occurrences of thiscondition indicate that re-engineering is re-quired to balance the flow of traffic through thiscard to reduce the amount of traffic and thelength of queues. Lower the connection poolcapacity for this AQM.



6.483 MSS_7060_01200

RNC Type • POC

• 9370 RNC

Component Lp/{x} Eng Arc Ov

Severity warning

Status message

Detail {x} = 0 - 15 The provisioned connection capa-city, the sum of the connectionPoolCapacity,protectedConnectionPoolCapacity, multicast-BranchesCapacity and protectedMcast-BranchesCapacity attributes for the Arc Ovcomponent is higher than what this particularcard can handle. No serious damage occurson the card, however the operational valuesdo not reflect provisioned values.

Remedial Action Determine the total connection capacity thecard can support by checking the Arc compon-ent and reduce the provisioned connection ca-pacity in the Arc Ov component accordingly.



6.484 MSS_7060_01201

RNC Type • POC

• 9370 RNC

Component Lp/{x} Eng Arc

Severity warning

cleared

Status set

clear

Detail {x} = 1 - 15 perVcQueueAvailable resourcesreaching a low level. If the status is set, theavailable perVc queues from the specified lo-gical processor have fallen below 10% of the32,000 total. If the available perVc queuesreaches 0, ATM perVc queued connections failto establish. A clear is issued when at least25% of the perVc queues become available. Afiltering mechanism is implemented such thata set/clear alarm pair can be issued no morethan one per minute.

Remedial Action No more than 32,000 connections can requesta perVc queue resource. The remaining con-nections must use common queuing. Whethera connection requires a perVc queue resourceis determined by the connection"™s ATM ser-vice category provisioning. A perVc queue re-source is required under either of the followingconditions: when the ATM service categoryhas the trafficShaping attribute provisioned aseither enabled or inverseUpcwhen the ATMservice category has the unshapedTrans-mitQueueing attribute provisioned as perVc Toenable common queuing on an ATM servicecategory, set the trafficShaping attribute to dis-abled and set the unshapedTransmitQueueingattribute to common.



6.485 MSS_7060_01300

RNC Type • POC

• 9370 RNC

Component Lp/{x} Eng

Severity minor

major

critical

cleared

Status set

clear

Detail {x} = 1 - 15 The status is set with critical sever-ity when hardware forwarding resource usagefor incoming IP/MPLS connections is at 99%of maximum. It is cleared when hardware for-warding resource usage drops to 98% of max-imum. The status is set with major severitywhen hardware forwarding resource usage forincoming IP/MPLS connections is at 95% ofmaximum. It is cleared when hardware for-warding resource usage drops to 94% of max-imum. The status is set with minor severitywhen hardware forwarding resource usage forincoming IP/MPLS connections is at 85% ofmaximum. It is cleared when hardware for-warding resource usage drops to 84% of max-imum.

Remedial Action Contact first level support for help with re-engineering the network to allow the resourceusage to move below a critical level. Hardwareforwarding performance is degraded when thehardware forwarding resource usage reachesthe maximum value.



6.486 MSS_7060_01400

RNC Type • POC

• 9370 RNC


Severity minor

major

critical

cleared

Status set

clear

Detail {x} = 1 - 15 The status is set with critical sever-ity when hardware forwarding resource usagefor outgoing IP/MPLS connections is at 99% ofmaximum. It is cleared when hardware for-warding resource usage drops to 98% of max-imum. The status is set with major severitywhen hardware forwarding resource usage foroutgoing IP/MPLS connections is at 95% ofmaximum. It is cleared when hardware for-warding resource usage drops to 94% of max-imum. The status is set with minor severitywhen hardware forwarding resource usage foroutgoing IP/MPLS connections is at 85% ofmaximum. It is cleared when hardware for-warding resource usage drops to 84% of max-imum.

Remedial Action Contact first level support for help with re-engineering the network to allow the resourceusage to move below a critical level. Hardwareforwarding performance is degraded when thehardware forwarding resource usage reachesthe maximum value.



6.487 MSS_7060_01500

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {x} = 1 - 15 Rule Set resources for VRIs havebeen exhausted. Some protocol ports with IPclassification may have reduced throughputperformance.

Remedial Action Frequent occurrences of this alarm indicatethat a number of filters (component Vr Ip Fil-ter), diffServ interfaces (component Vr Ip Diff-Serv), and/or policy groups (component Vr IpPg) with policies exceeds the IP classificationhardware resources available on this PQC FP.Any of the filters, diffServ interfaces, or policygroups can be assigned to either a protocolport or a virtual router. Contact your local Alca-tel-Lucent technical support group for help withre-engineering the network if necessary.



6.488 MSS_7060_01600

RNC Type • POC

• 9370 RNC


Severity warning

Status message

Detail {x} = 1 - 15 Rule Set resources for VROs havebeen exhausted. Some protocol ports as-signed with IP DSCP marking may not mark IPpackets with the expected DSCP.

Remedial Action Frequent occurrences of this alarm indicatethat a number of filters (component Vr Ip Fil-ter), diffServ interfaces (component Vr Ip Diff-Serv), and/or policy groups (component Vr IpPg) exceeds the IP classification hardware re-sources available on this PQC FP. Any of thefilters, diffServ interfaces, or policy groups canbe assigned to either a protocol port or a virtu-al router. Contact your local Alcatel-Lucenttechnical support group for help with re-engineering the network if necessary.



6.489 MSS_7060_01700

RNC Type • POC

• 9370 RNC

Component Lp/{x} Eng Rcp

Severity warning

Status message

Detail Lp/{x} {x} = 1 - 15 Lp Eng Rcp is not supportedon PQC6 version 1 FPs. Upon activation onPQC6 v1 cards, this alarm is generated towarn the user that Rcp is not supported on theHW version, and SW does not pass Rcp in-formation down to device level to avoid moreserious problems.The consequence is that theconfiguration of the FP hardware is the sameas before adding Rcp.

Remedial Action Once this alarm is seen, the user should checkthe PEC code of the FP; make sure Lp EngRcp is only added on FPs with Rcp-supportingPEC codes. Otherwise, the user should re-place the FP with a Rcp-supporting FP.



6.490 MSS_7060_01800

RNC Type • POC

• 9370 RNC


Severity minor

major

critical

cleared

Status set

clear

Detail {x} = 1 - 15 The status is set to critical severitywhen Transparent Bridge hardware resourceusage is at 99% of the total TransparentBridge hardware resource. It is cleared whenTransparent Bridge hardware resource usagedrops below 98% of the total. The status is setto major severity when Transparent Bridgehardware resource usage is at 95% of the totalTransparent Bridge hardware resource. It iscleared when Transparent Bridge hardware re-source usage drops below 94% of the total.The status is set to minor severity when Trans-parent Bridge hardware resource usage is at85% of the total Transparent Bridge hardwareresource. It is cleared when TransparentBridge hardware resource usage drops below84% of the total.

Remedial Action The number of Transparent Bridge Ports andVlans exceed the capacity of the LP. The con-nection pool resource requirements are both afunction of the number of Transparent BridgePorts and Vlans, and the number of Ports un-der the same Virtual Bridge instance. Consultthe Transparent Bridge configuration guide orcontact first-level support for help to re-



engineer the MSS.



6.491 MSS_7060_01900

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {x} = 1 - 15 This alarm is raised when the max-imum number of available Bridge Ports hasbeen exceeded on the FP.

Remedial Action The number of Bridge Ports configured on thisFP must be reduced to below the maximumnumber of Bridge Ports specified in the alarm.This is achieved by deleting Bridge Ports fromthis FP or moving Bridge Ports from this FP toother FPs. After the number of Bridge Ports onthis FP is reduced to, or below the maximumnumber specified, clear the Atm connectionsof the affected Bridge Ports to re-establish thedatapath.



6.492 MSS_7060_02000

RNC Type • POC

• 9370 RNC


Severity major

Status message

Detail {x} = 1 - 15 This alarm is raised when the max-imum number of available Bridge VLANs hasbeen exceeded on the FP.

Remedial Action The number of Bridge VLANs configured onthis FP must be reduced to below the maxim-um number of Bridge VLANs specified in thealarm. This is achieved by removingBridgeVlan components from Bridge Ports onthis FP, deleting Bridge Ports from this FP, ormoving Bridge Ports from this FP to other FPs.After the number of Bridge VLANs on this FPis reduced to, or below the maximum numberspecified, clear the Atm connections of the af-fected Bridge Ports to re-establish thedatapath.



6.493 MSS_7070_01000


Component Lp/{num1} Ap/{num2}

Severity critical

Status message

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 Whiletaking corrective action on an AP, three at-tempts to reset the processor have failed. Acard reset will be initiated by the system to re-cover this AP.

Remedial Action The card has been reset and no further actionis required from the operator. This alarm willbe cleared automatically when the LP returnsto service.



6.494 MSS_7070_01001



Severity warning

Status message

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 Thisalarm is raised when a lock command is abor-ted. The reason for aborting a lock could be:the mate of a critical entity (PMC_M, OMU, orNI) is crashed during the shutting down pro-cess; or if any of the SS7 linksets has the lastsaal-nni link left on the card

Remedial Action Only "lock -force lp/#" will lock the card



6.495 MSS_7070_01002



Severity critical

Status message

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 A desig-nated critical AP to the card becomes disabledresulting in a full card reset.

Remedial Action Full card will be reset.



6.496 MSS_7070_01003



Severity major

Status message

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 Unre-coverable error detected. The errors could be:the standby master PSFP can not SWACT be-cause applications are not ready for SWACTor the standby master is at a shutting downstate, or critical application errors that requiresall APs to be reset.

Remedial Action All the APs on the card will be passively resetand the whole shelf will be reset.



6.497 MSS_7070_01004



Severity major

cleared

Status set

clear

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 Heart-beat packet loss threshold from this AP hasbeen exceeded due to a communication failurebetween this processor and the card. An APreset is automatically initiated to recover nor-mal processor operations. If the heartbeat fail-ure is caused by a maker failure, a bus reset isautomatically initiated instead of the single APreset.

Remedial Action The affected AP/internal bus has been resetand no further action is required from the oper-ator. This alarm will be cleared automaticallywhen the AP returns to service. Note that re-setting the internal bus will also trigger the "APPassively Reset" alarm for all other functioningAP"™s on the same bus.



6.498 MSS_7070_01005



Severity major

cleared

Status set

clear

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 The LPhas lost communications with the AP. An un-known problem has caused the inter-pro-cessor heartbeat loss to exceed the prescribedthreshold and an AP reset is automatically ini-tiated to recover normal processor operations.

Remedial Action The affected AP/internal bus has been resetand no further action is required from the oper-ator. This alarm will be cleared automaticallywhen the AP returns to service.



6.499 MSS_7070_01006



Severity major

cleared

Status set

clear

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 DuringAP initialization an internal subsystem failed toinitialize properly on the local AP or when try-ing to initialize communications to slave pro-cessors. Additional information in the alarmdetails inidcates the point of failure detectedby the subsystem. An AP reset is automatic-ally initiated to recover normal processor oper-ations.

Remedial Action The affected internal bus has been reset andno further action is required from the operator.This alarm will be cleared automatically whenthe AP returns to service.



6.500 MSS_7070_01007



Severity major

cleared

Status set

clear

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 AP busreset. It can be due to failure of another AP onthe same PCI bus or the original trigger of thebus reset such as missing master pair.

Remedial Action The APs on the same bus are reset and nofurther actions is required. This alarm will becleared automatically when the APs return toservice.



6.501 MSS_7070_01008



Severity major

cleared

Status set

clear

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 Userhas invoked a manual reset on the AP or Ap-plication error detected and requires an AP re-set.

Remedial Action The AP itself is reset.



6.502 MSS_7070_01010



Severity minor

cleared

Status set

clear

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 If within5 minutes, an AP failed to initialize to a properAP role during initializion, it will stay in thepending state. An AP reset or PSFP card resetmay recover this AP from the pending state.After AP/PSFP reset, if the pending AP recov-ers, the alarm is going to be cleared by thehierarchical clear. If the AP recovers itselfwithout reset after the 5 minutes interval, aclear alarm will be issued to clear the setalarm.

Remedial Action The operator should check the provision andthe mib before reset the AP or the PSFP cardto recover.



6.503 MSS_7070_01011



Severity warning

Status message

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 This isan indication that a spared entity (PMC_M, NI,or OMU) has found that it is running without aredundant mate. This can be the result of lock-ing a card containing the spared entity or itsstandby, or a processor failure. This alarm isalso used to indicate if a SWACT hashappened by "newly Active".

Remedial Action If locking the card resulted in the generation ofthis alarm then unlocking this card should beattempted first to recover the mate. If this pro-cedure fails then the replacement of the faultycard will be necessary to recover the mate. Ifthis alarm was the result of a processor failurethen the automatic recovery of the AP will re-turn a mate to service.



6.504 MSS_7070_01012


Component Shelf Card/{num1}

Severity warning

Status message

Detail {num1} = 2 - 7, 10 - 15 This alarm is generatedwhenever there is a hostAdd "HALD-BG_HW_DEBUG" and to let the users knowthat the card is running in debug mode.

Remedial Action This is a warning to let the user know that thecard is in Hardware debug mode. Remove thehostAdd to recover.



6.505 MSS_7070_01013


Component Lp/{num1} Ap{num2}

Severity major

cleared

Status set

clear

Detail {num1} = 2 - 7, 10 - 15 {num2} = 0 - 5 On aStandby Master, a supervision timer is startedafter the card comes into service. If not all ofthe applications that registered to the ready forswact monitor are ready for swact before thetimer expries, the alarm will be raised to indic-ate that the Standby Master is not ready forswact.

Remedial Action The alarm will be cleared automatically whenall the registered applications on the StandbyMaster are ready for swact. If the alarm is notcleared for extended time, a card reset of theStandby Master should be performed. In thecase that the problem exists after the card re-set, the operator needs to contact Alcatel-Lu-cent for technical support.



6.506 MSS_7070_01014



Severity major

Status message

Detail {num1} = 0 -15 {num2} = 0 - 5 This alarm isgenearted when an AP patching applicationfailure occurs on the AP of the LP. Text fromthe original alarm generated for the failurecondition on the AP is embedded within thisalarm. Typically, the failure conditions repres-ent: patch unload failure, due to such as waitfor too long, etc. or not enough memory toload the patch or unresolved symbol conflict orpatch initialization failure.

Remedial Action The alarm is automatically followed by the re-set of the affected AP. If the failure condition iscleared by the reset, in which case the AP isback to service, no operator action is needed.If the failure condition persists, in which casethe further standard maintenance actions takeplace with cascaded hierarchical resets (suchas bus reset and card reset). If LP is finally re-jected after 3 reset attempts, the operatorneeds to manually roll back to pre-applicationcondition and report the situation to Alcatel-Lu-cent.



6.507 MSS_7070_02001



Severity major

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 ActiveMaster failure, AP will reset; CnAccCa -RmanCa reset process failed.




6.508 MSS_7070_02002



Severity major

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 StandbyMaster failure, AP will reset; CnAccCa -RmanCa reset process failed.




6.509 MSS_7070_02003



Severity major

cleared

Status set

clear

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 All TCPlinks down. This is an indication that the ActiveMaster has lost all communications with theCNode.

Remedial Action Qualified personnel should check if a link hasfailed or there is a card failure.



6.510 MSS_7070_02004



Severity minor

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 The op-erator has requested additional provisioningbe performed while the INode system is initial-izing and receiving its current path information.This operation cannot be processed at thistime and will be ignored.

Remedial Action The operator will need to delete the new incre-mental provisioning and then retry the opera-tion when the system has fully initialized.



6.511 MSS_7070_02005



Severity minor

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 TBMdoes not bind any newly provisioned path(s) ifthe path rebalancing is in progress. This alarmindicates to the craftperson that the pathdidn"™t get bound. So, it must be re-provisioned.

Remedial Action The operator will need to re-provision the path.



6.512 MSS_7070_02006



Severity warning

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 Thisalarm indicates that one or both of the trafficparameters Peak Cell Rate (PCR) and Sus-tained Cell Rate (SCR) have not been provi-sioned for an AAI2If Path. This alarm can begenerated in three different situations: Duringinitialization this alarm will be generated if theprovisioning view has an AAI2If Path linked toa PVC VCC with PCR and/or SCR set to zero.(These values are set to zero when they arenot provisioned.) The same alarm will be gen-erated when the standby master takes overafter a failure of the active master. The alarmwill be generated if a new AAI2If Path is addedwhich is linked to a PVC VCC with PCR and/orSCR set to zero.

Remedial Action The operator should provision the PCR andSCR on the associated PVC VCC.



6.513 MSS_7070_02007



Severity major

cleared

Status set

clear

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5

After a manual lock or reset, only the clearalarm is raised (no set message).

In case of overload, the set alarm is raised andchanges to clear when the APs come back tothe normal state.

The set alarm indicates that processor load oneither the AP Master or on x percentage ofAPs (current x is configured as all the APs)has exceeded the overload onset limit of critic-al. The clear alarm indicates that processorload has reduced below the onset limit oneither the AP Master or an x percentage ofAPs. This alarm also can indicate a clearing ofan alarm due to an AP master activity switchto the standby AP.

Remedial Action The operator should ensure that all APs are inservice. If some LPs or APs are not available ,the capacity of the system may be restrictedcausing this overload condition. The opeartorshould review the provisioned configuration toensure that the INode supports the networktraffic.



6.514 MSS_7070_02008



Severity major

cleared

Status set

clear

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 The crit-ical overload threshold level has been ex-ceeded/cleared on one AP.

Remedial Action The operator should ensure that all APs are inservice. If some LPs or APs are not available ,the capacity of the system may be restrictedcausing this overload condition. The opeartorshould review the provisioned configuration toensure that the INode supports the networktraffic.



6.515 MSS_7070_02011



Severity major

cleared

Status set

clear

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 This isan indication that a RAB or PMC_M (Active orStandby) is not connected to any of the TMUsor OMUs.

Remedial Action RAB or PMC_M (Active or Standby) has to bechecked for failure.



6.516 MSS_7070_02012



Severity warning

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 The RNCis using a MIB that may not be the one expec-ted by the operator. This maybe related to afailure in case of software upgrade or to a fail-ure in case of capacity increase requiring MIBupgrade.

Remedial Action The operator should investigate to make surethat the current RNC configuration is consist-ent. In most of the cases, the operator shouldhave no action to take as the alarm can be ex-plained by a previous failure. In the case of in-consistency, a new mib build or a RNC restoremaybe required.



6.517 MSS_7070_02013



Severity critical

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 The APhas failed to cleanup the resources as reques-ted by the Active master.

Remedial Action The AP is reset and no further action is re-quired.



6.518 MSS_7070_02014



Severity major

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 At regis-tration time, generate an alarm if TBM cannotregister with Iuxif.

Remedial Action N/A



6.519 MSS_7070_02015



Severity warning

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 InterfaceOut Of Service action is completed for "Interfa-ceType (IU-CS/IU-PS/IUR), InterfaceId(IuCsIfId/IuPsIfId/IurIfId, CsDomainId/PsDo-mainId/NeighbouringRncId), SCCP DPC" .

Remedial Action N/A



6.520 MSS_7070_02016



Severity warning

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 InterfaceOut Of Service action is failed for "Interface-Type (IU-CS/IU-PS/IUR), InterfaceId(IuCsIfId/IuPsIfId/IurIfId, CsDomainId/PsDo-mainId/NeighbouringRncId), SCCP DPC" .

Remedial Action N/A



6.521 MSS_7070_02017



Severity warning

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 InterfaceIn Service action is completed for "Interface-Type (IU-CS/IU-PS/IUR), InterfaceId(IuCsIfId/IuPsIfId/IurIfId, CsDomainId/PsDo-mainId/NeighbouringRncId), SCCP DPC" .

Remedial Action N/A



6.522 MSS_7070_02018



Severity warning

Status message

Detail {num1} = 2 -7, 10 - 15 {num2} = 0 - 5 InterfaceIn Service action is failed for "InterfaceType(IU-CS/IU-PS/IUR), InterfaceId(IuCsIfId/IuPsIfId/IurIfId, CsDomainId/PsDo-mainId/NeighbouringRncId), SCCP DPC" .

Remedial Action N/A



6.523 MSS_7078_00050


Component rncIn

Severity critical

cleared

Status set

clear

Detail No ATM cards in shelf.

Remedial Action This alarm will be cleared automatically whenthe first ATM card comes back.



6.524 MSS_7078_00051


Component rncIn

Severity critical

cleared

Status set

clear

Detail Both application master active and standbyfailed.

Remedial Action This alarm will be cleared automatically whenthe first PMCM comes back.



6.525 MSS_7078_00052


Component rncIn

Severity critical

cleared

Status set

clear

Detail Both application NI active and standby failed.

Remedial Action This alarm will be cleared automatically whenthe first NI comes back.



6.526 MSS_7078_00053


Component rncIn

Severity critical

cleared

Status set

clear

Detail OMU active and standby failed.

Remedial Action This alarm will be cleared automatically whenthe first OMU comes back.



6.527 MSS_7078_00054


Component rncIn

Severity major

cleared

Status set

clear

Detail CP running unspared due to missing standbyor active CP.

Remedial Action This alarm is automatically cleared when thesecond CP comes back as standby CP.



6.528 MSS_7078_00055


Component rncIn

Severity major

cleared

Status set

clear

Detail One of the ATM cards is not present.

Remedial Action This alarm will be cleared automatically whenthe second ATM card comes back as standby.



6.529 MSS_7078_00056


Component rncIn

Severity major

cleared

Status set

clear

Detail One of the Application master active orstandby is not present.

Remedial Action This alarm will be cleared automatically whenthe second PMCM comes back.



6.530 MSS_7078_00057


Component rncIn

Severity major

cleared

Status set

clear

Detail One of the application NI active or standby isnot present.

Remedial Action This alarm will be cleared automatically whenthe second NI comes back.



6.531 MSS_7078_00058


Component rncIn

Severity major

cleared

Status set

clear

Detail One of the application OMU active or standbyis not present.

Remedial Action This alarm will be cleared automatically whenthe second OMU comes back.



6.532 MSS_7078_00059


Component rncIn

Severity critical

cleared

Status set

clear

Detail This alarm indicates unsupported configura-tion. PSFP cards are not properly provisionedin the first four primary slots is one of the un-supported configurations. The others could bethe configuration of the switch is not in matchwith the hardware capability.

Remedial Action For the none-properly provisioned first fourslots, re-provision the first four slots (2,3,4,5)for PSFP cards. For the other unsupportedconfigurations for different hardware capability,check the provisioning of the card types ac-cording to the listed supported configuration,re-provision the card, the alarm will be cleared.



6.533 MSS_7078_00061


Component rncIn

Severity major

cleared

Status set

clear

Detail The provisioned rncHardwareCapability is notsupported on the running hardware.

Remedial Action Modify the rncHardwareCapability attribute tomatch the running hardware or change hard-ware to match rncHardwareCapability.



6.534 MSS_7078_00100

RNC Type

Component iSMLC

Severity minor

cleared

Status set

clear

Detail The iSMLC doesn't receive GPS NavigationData messages from the SRS using theprimary IP address. The iSMLC is releasingthe primary IP connection. In case the second-ary IP connection is provisioned, the iSMLC isswitching over to the secondary one. Other-wise it will try to re-establish the primary IPconnection. The SRS is down or the primarylink to the SRS is broken or misconfigured.

Remedial Action Verify and correct satelliteReferenceSystem/1



6.535 MSS_7078_00101

RNC Type

Component iSMLC

Severity major

cleared

Status set

clear

Detail The iSMLC doesn't receive GPS NavigationData messages over any SRS link. The com-munication to the SRS is interrupted. If this in-terruption lasts longer than 2 hours, the iSMLCis no longer able to provide assistance data. Inthat case noSrsData alarm is raised. The SRSis down or all links to the SRS are broken ormisconfigured.

Remedial Action Verify/Correct satelliteReferenceSystem/1 andsatelliteReferenceSystem/2. If the alarm iscleared, the procedure is completed. If thealarm persists and the alarm has been raisedby several instances, for the same SRS, re-quest the operator of the SRS network to takethe appropriate action. If the alarm is cleared,the procedure is completed.



6.536 MSS_7078_00206


Component AAL2IF/{x}

Severity minor

cleared

Status set

clear

Detail The alarm is set when a path is remotelyblocked. The alarm text will indicate the pathnumber and VCC id that is blocked. The alarmwill be cleared when the path is remotely un-blocked.




6.537 MSS_7078_00300


Component rncIn

Severity warning

Status set

clear

Detail The RNC has come into servie. The first C-Bearer (cell) set-up is completed successfully.

Remedial Action This alarm can only be cleared manually.



6.538 MSS_7078_00400


Component rncIn

Severity warning

cleared

Status message

Detail At least one of the provisioned Aal2If Paths inthe RNC is not spared due to an active orstandby binding failure. The alarm will becleared when all the paths are active andstandby bound successfully.




6.539 MSS_7078_00401


Component rncIn

Severity major

cleared

Status set

clear

Detail There are not enough resources available tosupport all AAL2 Paths configured.

Remedial Action Provision fewer paths or add additional PacketServer cards.



6.540 MSS_7078_00500


Component iuBc

Severity minor

cleared

Status set

clear

Detail The iuBc component is degraded. One of theTCP connection to the CBC server is not avail-able due to the iuBc Cbs CbcIp component be-ing locked or due to network problems.

Remedial Action Unlock the iuBc Cbs CbcIp component or fixthe network problem.



6.541 MSS_7078_00501


Component iuBc

Severity critical

cleared

Status set

clear

Detail The iuBc component is disabled. The compon-ent could be locked, the CbcIp subcompon-ent(s) could be locked, or the TCP connec-tions(s) to the CBC server could not be estab-lished due to a network problem.

Remedial Action Unlock the component, unlock the CbcIp sub-component(s), or fix the network problem.



6.542 MSS_7078_00502


Component iuBc cbs cbcIp/{num1}

Severity critical

cleared

Status set

clear

Detail {num1} = 1, 2 The iuBc cbs cbcIp componentis disabled. The component could be locked,or the TCP connection(s) to the CBC servercould not be established due to a networkproblem.

Remedial Action Unlock the component, or fix the network prob-lem.



6.543 MSS_7079_00000


Component Ss7 Sccp/{x}

Severity major

cleared

Status set

clear

Detail {x} = instance identifier of the SCCP When thestatus is set, all of the provisioned connectionsare consumed and are in use. This results inthe connections exhausted alarm being gener-ated by the SCCP, because an SCCP user re-quested a connection but was denied. Theconnections are from the local SCCP to the re-mote SCCP. The connection request is failedby SCCP and the connection is not estab-lished. All future connection requests will failuntil an adequate number of in-use connec-tions are relinquished. When the status isclear, a low water mark has been reached forin-use connections providing an adequate poolof connections available for use.

Remedial Action When the status is set, increase the number ofavailable connections provisioned in SCCP ordetermine why an excessive number of con-nections are being used and decrease thenumber of connection requests by SCCPusers.



6.544 MSS_7079_00100


Component Ss7 Mtp3/{x} Linkset/{y}Link/{z}

Severity major

cleared

Status set

clear

Detail {x} = MTP3 instance identifier {y} = linkset in-stance identifier {z} = link snstance identifier; z= 0 - 15 The signaling link test failed alarm isgenerated by an MTP3 Link when the Signal-ing Link Test (SLT) fails. This indicates thatthe Signaling Link Test Controller (SLTC) de-tected a bad link. Once the bad link is detec-ted, it will be restarted.

Remedial Action Monitor the bad link to ensure that the linkcomes back into service.



6.545 MSS_7079_00101


Component Ss7 Mtp3/{x} Linkset/{y}

Severity critical

cleared

Status set

clear

Detail {x} = MTP3 instance identifier {y} = linkset in-stance identifier When the status is set, a des-tination (i.e. remote MTP3) is inaccessible dueto all links in the linkset being inaccessible.The destination is inaccessible because alllinks in the linkset are either inhibited, locked,or disabled. When the status is clear, a destin-ation (i.e. remote MTP3) becomes accessibledue to one or more links in the linkset beingaccessible. The destinations is accessible be-cause an inhibited link becomes uninhibited, alocked link becomes unlocked, or a disabledlink becomes enabled.

Remedial Action When the status is set, the destination is inac-cessible due to links being inhibited, locked, ordisabled. For links inhibited or locked, uninhibitor unlock links as appropriate. Disabled linksshould be monitored to ensure the links comeback into service. When the status is clear, noremedial action is necessary.



6.546 MSS_7079_00102


Component Ss7 Mtp3/{x} Routeset/{y}Route/{z}

Severity major

cleared

Status set

clear

Detail {x} = MTP3 instance identifier {y} = routeset in-stance identifier {z} = route instance identifierWhen the status is set, the route to a destina-tion (i.e. remote MTP3) is inaccessible due toroute or linkset inaccessibility. The destinationcould be inaccessible because the route is dis-abled or a transfer prohibited managementmessage for the route is received. The destin-ation could also be inaccessible because thelinkset becomes inhibited, or disabled. Whenthe status is clear, a destination (i.e. remoteMTP3) becomes accessible due to the routeand linkset being accessible. The destinationcould be accessible when the route is enabledor a transfer allowed management messagefor that route is received. The destinationcould also be accessible because the linksetbecomes uninhibited, or enabled.

Remedial Action When the status is set, the route is inaccess-ible due to route or linkset inaccessibility. Dis-abled routes should be monitored to ensurethey come back into service. If the linkset islocked then unlock it. If the linkset is inhibitedor disabled then it should be monitored forwhen it will come back into service. When thestatus is clear, no remedial action is neces-sary.



6.547 MSS_7079_00103


Component Ss7 Mtp3/{x} Routeset/{y}

Severity critical

cleared

Status set

clear

Detail {x} = MTP3 instance identifier {y} = routeset in-stance identifier When the status is set, a des-tination (i.e. remote MTP3) is inaccessible dueto all routes in the routeset being inaccessibil-ity. The destination could be inaccessible be-cause all routes in the routeset are locked ordisabled. When the status is clear, a destina-tion (i.e. remote MTP3) becomes accessibledue to one or more routes in the routeset be-ing accessible. The destination is accessiblebecause a locked route becomes unlocked, ora disabled route becomes enaabled.

Remedial Action When the status is set, the destination is inac-cessible due to all routes in a routeset beingdisabled or routeset is locked. Disabled routesshould be monitored to ensure they comeback into service. When the status is clear, noremedial action is necessary.



6.548 MSS_7079_00200

RNC Type

Component Ss7 M3ua/{x} DestinationSignalingPoint/{y}

Severity critical

cleared

Status set

clear

Detail {x} = M3ua instance identifier, x=1 {y} = Des-tinationSignalingPoint instance identifier, y = 0- 63 This alarm is set when a destination sig-naling point becomes inaccessible due to allthe routes leading to that destination being in-accessible. This alarm is cleared when a des-tination signaling point becomes accessibledue to one or more routes leading to that des-tination being accessible.

Remedial Action When the alarm is set, the inaccessible routesshould be monitored to ensure that they comeback into service. When the alarm is cleared,no remedial action is necessary.



6.549 MSS_7079_00201

RNC Type

Component Ss7 M3ua/{x} PeerM3uaEntity/{y}

Severity critical

cleared

Status set

clear

Detail {x} = M3ua instance identifier, x=1 {y} =PeerM3uaEntity instance identifier, y = 0 - 511This alarm is set when the remote peer M3UAentity is down due to all the peer M3UA pro-cesses that serve this peer M3UA entity beingdown. This alarm is cleared when the remotepeer M3UA entity becomes active due to oneor more peer M3UA processes that serve thispeer M3UA entity being active.

Remedial Action When the alarm is set, the disabled peerM3UA processes that serve this remote peerM3UA entity should be monitored to ensurethat they come back into service. When thealarm is cleared, no remedial action is neces-sary.



6.550 MSS_7079_00202

RNC Type

Component Ss7 M3ua/{x} PeerM3uaProcess/{y}

Severity major

cleared

Status set

clear

Detail {x} = M3ua instance identifier, x=1 {y} =PeerM3uaProcess instance identifier, y = 0 -511 This alarm is set when the remote peerM3UA process is down due to all the relatedSCTP associations being closed. This alarm iscleared when the remote peer M3UA processis active due to one or more related SCTP as-sociations being established and applicationtraffic is active.

Remedial Action When the alarm is set, the closed SCTP asso-ciations that are related to this remote peerM3UA process should be monitored to ensurethat they come back into service. When thealarm is cleared, no remedial action is neces-sary.



6.551 MSS_7079_00203

RNC Type

Component Ss7 M3ua/{x} PeerM3uaProcess/{y} SctpAsso-ciation/{z}

Severity major

cleared

Status set

clear

Detail {x} = M3ua instance identifier, x=1 {y} =PeerM3uaProcess instance identifier, y = 0 -511 {z} = SctpAssociation instance identifier, z= 0 -7 This alarm is set when the SCTP asso-ciation is in closed state. An SCTP associationcould be closed due to errors during associ-ation establishment or receiving a shutdownrequest from the SCTP user. This alarm iscleared when the SCTP association is estab-lished successfully.

Remedial Action When the alarm is set, verify the health of theIP connectivity and determine what hascaused the association failure on both localand remote side. When the alarm is cleared,no remedial action is necessary.



6.552 MSS_7079_00300


Component Ss7 SaalNni/{x}

Severity major

cleared

Status set

clear

Detail {x} = SaalNNI instance identifier When thestatus is set, a condition exists on the link tothe peer that prevents alignment from complet-ing successfully. As a result, the link will notcome into service. Alignment failure could bedue to insufficcient bandwidth to support thelink or an error rate on the link that is outsideacceptable bounds. When the status is clear,alignment on the link completes successfullyas a result of increased bandwidth or the errorrate on the link comes within acceptablebounds. As a result, the link comes into ser-vice.

Remedial Action When the status is set, verify the bandwidth issufficient to support the link and increase it ifnecessary. Verify the health of the physicalconnectivity (e.g. optical link or interface).When the status is clear, no remedial action isnecessary.



6.553 MSS_7079_00301


Component Ss7 SaalNni/{x}

Severity major

Status message

Detail {x} = SaalNNI instance identifier The layer 2peer disconnect alarm is generated by SaalNniwhen a peer SaalNni releases the link and dis-connects. The disconnect occurs as a result ofthe peer SaalNni sending a release indicationto the local SallNni, which ultimately results inthe link being taken out of service.

Remedial Action Determine what incompatibility or engineeringchange has occurred at the peer SaalNni tocause it to generate a release indication.



Wireless Service Provider SolutionsW-CDMAAlcatel-Lucent 9300 W-CDMA Product FamilyRNC and MSS POC Alarms Reference Guide

Copyright © 2004-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 alteredonly by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures accessto 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 asexpressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose theinformation only to its employees with a need to know, and shall protect the information from disclosure and dissemination to thirdparties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information containedherein. 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, Alcateland Lucent Technologies.

The Alcatel-Lucent 9370 Radio Network Controller and the Alcatel-Lucent Point Of Concentration are based on Nortel MultiserviceSwitch products. The Nortel Multiservice Data Manager is a Nortel product.

All other trademarks are the property of their owners.

Document number: NN-20500-024Document issue: 05.06/ENDocument status: PreliminaryProduct Release: OAM06.0Date: September 2008

nn-20500-024_(9300_w-cdma_product_family_-_rnc_and_mss_poc_alarms_reference_guide)_05.06_preliminary_september2008.pdf...

Documents

alcatellucent rnc

lucent technologies

service marksof alcatellucent

document issue

property ofalcatellucent

en preliminaryupdate

en draftupdate

current issue